From 3504b58715c7cc5a6a7da1f0c5b247add1819ba6 Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Tue, 18 Oct 2022 10:50:54 -0700 Subject: [PATCH 1/2] New translation batch for pt (#31829) --- translations/log/msft-pt-resets.csv | 457 +++++++++++++++++- .../about-notifications.md | 108 ++--- .../configuring-notifications.md | 22 +- .../managing-notifications-from-your-inbox.md | 171 ++++--- .../managing-your-profile-readme.md | 2 +- .../personalizing-your-profile.md | 2 +- ...utions-and-achievements-on-your-profile.md | 2 +- .../viewing-contributions-on-your-profile.md | 84 ++-- ...tributions-not-showing-up-on-my-profile.md | 93 ++-- .../index.md | 2 +- ...-collaborators-to-a-personal-repository.md | 2 +- ...an-email-address-to-your-github-account.md | 23 +- .../managing-email-preferences/index.md | 10 +- ...membering-your-github-username-or-email.md | 55 +-- .../setting-your-commit-email-address.md | 56 ++- .../changing-your-github-username.md | 83 ++-- .../managing-accessibility-settings.md | 49 +- ...fault-branch-name-for-your-repositories.md | 35 +- ...best-practices-for-leaving-your-company.md | 43 +- .../about-continuous-integration.md | 51 +- .../creating-a-composite-action.md | 72 +-- .../creating-a-docker-container-action.md | 139 +++--- .../creating-a-javascript-action.md | 10 +- .../metadata-syntax-for-github-actions.md | 18 +- .../deploying-with-github-actions.md | 91 ++-- ...ing-to-amazon-elastic-container-service.md | 6 +- .../deploying-docker-to-azure-app-service.md | 4 +- .../deploying-php-to-azure-app-service.md | 4 + ...uring-openid-connect-in-cloud-providers.md | 94 ++-- ...ncurrency-expressions-and-a-test-matrix.md | 104 ++-- .../using-the-github-cli-on-a-runner.md | 100 ++-- .../about-self-hosted-runners.md | 12 +- ...and-troubleshooting-self-hosted-runners.md | 159 +++--- .../running-scripts-before-or-after-a-job.md | 89 ++-- .../actions/learn-github-actions/contexts.md | 20 +- .../learn-github-actions/expressions.md | 6 +- .../understanding-github-actions.md | 2 +- ...oving-assigned-issues-on-project-boards.md | 60 ++- .../publishing-nodejs-packages.md | 2 +- .../automatic-token-authentication.md | 4 +- .../security-guides/encrypted-secrets.md | 2 +- .../security-hardening-for-github-actions.md | 8 +- .../about-github-hosted-runners.md | 2 +- .../using-larger-runners.md | 10 + .../events-that-trigger-workflows.md | 2 +- .../using-workflows/reusing-workflows.md | 18 +- .../storing-workflow-data-as-artifacts.md | 128 +++-- .../using-workflows/triggering-a-workflow.md | 4 +- .../workflow-commands-for-github-actions.md | 9 +- .../workflow-syntax-for-github-actions.md | 4 +- ...guring-code-scanning-for-your-appliance.md | 6 +- ...ring-secret-scanning-for-your-appliance.md | 59 +-- ...b-advanced-security-for-your-enterprise.md | 96 ++-- ...pply-chain-security-for-your-enterprise.md | 17 +- ...he-dependency-graph-for-your-enterprise.md | 47 +- ...-vulnerability-data-for-your-enterprise.md | 27 +- .../about-github-connect.md | 28 +- ...c-user-license-sync-for-your-enterprise.md | 31 +- ...enabling-dependabot-for-your-enterprise.md | 14 +- ...g-server-statistics-for-your-enterprise.md | 32 +- ...ified-contributions-for-your-enterprise.md | 43 +- ...ling-unified-search-for-your-enterprise.md | 43 +- .../configuring-github-connect/index.md | 10 +- .../managing-github-connect.md | 106 ++-- .../configuring-a-hostname.md | 36 +- ...onfiguring-an-outbound-web-proxy-server.md | 33 +- .../configuring-built-in-firewall-rules.md | 46 +- .../configuring-dns-nameservers.md | 22 +- .../configuring-tls.md | 78 +-- .../enabling-subdomain-isolation.md | 43 +- .../network-ports.md | 66 ++- ...-enterprise-server-with-a-load-balancer.md | 74 +-- .../validating-your-domain-settings.md | 20 +- .../accessing-the-administrative-shell-ssh.md | 50 +- .../accessing-the-management-console.md | 54 +-- .../command-line-utilities.md | 398 +++++++-------- .../configuring-applications.md | 26 +- .../configuring-backups-on-your-appliance.md | 22 +- .../configuring-email-for-notifications.md | 6 +- ...guring-github-pages-for-your-enterprise.md | 72 +-- ...configuring-host-keys-for-your-instance.md | 29 +- .../configuring-rate-limits.md | 6 +- ...guring-ssh-connections-to-your-instance.md | 39 +- ...the-referrer-policy-for-your-enterprise.md | 36 +- .../configuring-web-commit-signing.md | 65 +-- ...nabling-and-scheduling-maintenance-mode.md | 93 ++-- .../enabling-private-mode.md | 23 +- .../initializing-github-ae.md | 175 ++++--- ...aging-github-mobile-for-your-enterprise.md | 40 +- .../site-admin-dashboard.md | 22 +- .../troubleshooting-tls-errors.md | 56 +-- .../accessing-the-monitor-dashboard.md | 37 +- .../configuring-collectd.md | 52 +- ...ting-a-health-check-for-your-enterprise.md | 55 +-- .../monitoring-your-appliance/index.md | 10 +- .../monitoring-using-snmp.md | 118 ++--- .../recommended-alert-thresholds.md | 46 +- .../enabling-automatic-update-checks.md | 33 +- .../increasing-cpu-or-memory-resources.md | 85 ++-- .../increasing-storage-capacity.md | 62 ++- .../upgrade-requirements.md | 55 +-- .../upgrading-github-enterprise-server.md | 10 +- ...rise-server-with-github-actions-enabled.md | 8 +- ...ting-github-actions-for-your-enterprise.md | 151 +++--- .../using-a-staging-environment.md | 39 +- ...ions-with-minio-gateway-for-nas-storage.md | 43 +- ...f-hosted-runners-for-dependabot-updates.md | 77 ++- .../about-github-actions-for-enterprises.md | 4 +- ...ub-actions-for-github-enterprise-server.md | 101 ++-- ...self-hosted-runners-for-your-enterprise.md | 12 +- ...ucing-github-actions-to-your-enterprise.md | 2 +- .../about-using-actions-in-your-enterprise.md | 54 +-- ...-githubcom-actions-using-github-connect.md | 57 ++- ...manually-syncing-actions-from-githubcom.md | 68 ++- ...version-of-the-official-bundled-actions.md | 67 ++- .../identity-and-access-management/index.md | 10 +- ...bout-authentication-for-your-enterprise.md | 30 +- .../changing-authentication-methods.md | 34 +- .../managing-iam-for-your-enterprise/index.md | 17 +- ...siderations-for-external-authentication.md | 16 +- ...-accounts-single-sign-on-recovery-codes.md | 30 +- .../configuring-built-in-authentication.md | 47 +- .../disabling-unauthenticated-sign-ups.md | 26 +- .../inviting-people-to-use-your-instance.md | 23 +- .../using-cas-for-enterprise-iam/index.md | 10 +- .../using-cas-for-enterprise-iam/using-cas.md | 45 +- .../about-enterprise-managed-users.md | 57 +-- ...for-your-idps-conditional-access-policy.md | 6 +- ...uring-oidc-for-enterprise-managed-users.md | 48 +- ...le-sign-on-for-enterprise-managed-users.md | 101 ++-- ...-for-enterprise-managed-users-with-okta.md | 103 ++-- ...ovisioning-for-enterprise-managed-users.md | 74 +-- ...mberships-with-identity-provider-groups.md | 79 +-- .../migrating-from-saml-to-oidc.md | 12 +- .../using-ldap-for-enterprise-iam/index.md | 10 +- .../using-ldap.md | 221 ++++----- .../about-saml-for-enterprise-iam.md | 67 ++- ...ning-for-your-enterprise-using-azure-ad.md | 44 +- ...isioning-for-your-enterprise-using-okta.md | 153 +++--- ...saml-single-sign-on-for-your-enterprise.md | 190 ++++---- ...g-user-provisioning-for-your-enterprise.md | 82 ++-- .../enabling-encrypted-assertions.md | 61 ++- .../using-saml-for-enterprise-iam/index.md | 11 +- .../saml-configuration-reference.md | 22 +- ...n-organization-to-an-enterprise-account.md | 41 +- .../troubleshooting-saml-authentication.md | 81 ++-- .../updating-a-users-saml-nameid.md | 40 +- ...talling-github-enterprise-server-on-aws.md | 125 +++-- ...lling-github-enterprise-server-on-azure.md | 69 ++- ...erprise-server-on-google-cloud-platform.md | 87 ++-- ...thub-enterprise-server-on-openstack-kvm.md | 52 +- ...ling-github-enterprise-server-on-vmware.md | 52 +- .../setting-up-a-staging-instance.md | 4 +- .../about-server-statistics.md | 59 ++- .../exporting-server-statistics.md | 53 +- .../managing-global-webhooks.md | 111 +++-- .../audit-log-events-for-your-enterprise.md | 62 ++- ...uring-the-audit-log-for-your-enterprise.md | 66 +-- ...es-in-the-audit-log-for-your-enterprise.md | 53 +- ...aming-the-audit-log-for-your-enterprise.md | 2 +- .../admin/overview/about-data-residency.md | 17 +- .../overview/about-enterprise-accounts.md | 70 ++- .../about-github-enterprise-server.md | 107 ++-- .../content/admin/overview/system-overview.md | 179 ++++--- .../enabling-github-packages-with-aws.md | 50 +- ...github-packages-with-azure-blob-storage.md | 40 +- .../enabling-github-packages-with-minio.md | 50 +- ...ith-github-packages-for-your-enterprise.md | 48 +- ...ainer-registry-from-the-docker-registry.md | 69 ++- ...inio-storage-bucket-for-github-packages.md | 79 ++- .../about-enterprise-policies.md | 26 +- ...s-for-github-actions-in-your-enterprise.md | 6 +- ...or-security-settings-in-your-enterprise.md | 2 +- ...-management-policies-in-your-enterprise.md | 2 +- .../index.md | 1 + .../about-pre-receive-hooks.md | 32 +- .../creating-a-pre-receive-hook-script.md | 185 +++---- ...adding-organizations-to-your-enterprise.md | 88 ++-- .../adding-people-to-teams.md | 28 +- .../continuous-integration-using-jenkins.md | 14 +- .../creating-teams.md | 58 ++- ...ctor-authentication-for-an-organization.md | 69 +-- .../restoring-a-deleted-organization.md | 57 +-- ...-large-file-storage-for-your-enterprise.md | 92 ++-- ...izing-user-messages-for-your-enterprise.md | 134 ++--- .../suspending-and-unsuspending-users.md | 103 ++-- ...-a-users-saml-access-to-your-enterprise.md | 51 +- .../viewing-people-in-your-enterprise.md | 2 +- .../about-migrations.md | 66 ++- ...ing-migration-data-from-your-enterprise.md | 64 ++- .../index.md | 10 +- .../migrating-data-to-your-enterprise.md | 155 +++--- ...authentication-with-saml-single-sign-on.md | 53 +- ...-token-for-use-with-saml-single-sign-on.md | 10 +- .../about-ssh.md | 2 +- ...ng-a-new-ssh-key-to-your-github-account.md | 79 +-- .../checking-for-existing-ssh-keys.md | 35 +- ...-ssh-key-and-adding-it-to-the-ssh-agent.md | 4 +- .../testing-your-ssh-connection.md | 36 +- .../about-authentication-to-github.md | 112 ++--- .../authorizing-oauth-apps.md | 82 ++-- .../creating-a-personal-access-token.md | 145 ++++-- .../creating-a-strong-password.md | 34 +- .../index.md | 10 +- .../preventing-unauthorized-access.md | 30 +- ...moving-sensitive-data-from-a-repository.md | 122 +++-- .../reviewing-your-security-log.md | 6 +- .../reviewing-your-ssh-keys.md | 65 ++- .../sudo-mode.md | 78 ++- .../token-expiration-and-revocation.md | 50 +- ...updating-your-github-access-credentials.md | 81 ++-- .../about-commit-signature-verification.md | 4 +- ...adding-a-gpg-key-to-your-github-account.md | 71 ++- .../associating-an-email-with-your-gpg-key.md | 56 +-- .../telling-git-about-your-signing-key.md | 6 +- .../about-two-factor-authentication.md | 31 +- ...-github-using-two-factor-authentication.md | 90 ++-- .../configuring-two-factor-authentication.md | 163 ++++--- .../index.md | 10 +- ...ccount-if-you-lose-your-2fa-credentials.md | 89 ++-- .../error-agent-admitted-failure-to-sign.md | 28 +- .../error-key-already-in-use.md | 36 +- .../using-ssh-over-the-https-port.md | 28 +- .../about-billing-for-github-packages.md | 61 ++- .../about-billing-for-your-enterprise.md | 69 ++- .../about-per-user-pricing.md | 2 +- .../downgrading-your-github-subscription.md | 92 ++-- .../upgrading-your-github-subscription.md | 98 ++-- ...n-and-usage-for-your-enterprise-account.md | 44 +- ...io-subscriptions-with-github-enterprise.md | 39 +- ...io-subscriptions-with-github-enterprise.md | 73 ++- .../about-licenses-for-github-enterprise.md | 41 +- ...ding-your-license-for-github-enterprise.md | 38 +- ...new-license-to-github-enterprise-server.md | 37 +- ...ing-license-usage-for-github-enterprise.md | 74 +-- .../configuring-code-scanning.md | 2 +- .../viewing-code-scanning-logs.md | 62 ++- .../sarif-support-for-code-scanning.md | 252 +++++----- ...-codeql-code-scanning-in-your-ci-system.md | 2 +- ...onfiguring-codeql-cli-in-your-ci-system.md | 8 +- ...iguring-codeql-runner-in-your-ci-system.md | 190 ++++---- ...installing-codeql-cli-in-your-ci-system.md | 2 +- ...running-codeql-runner-in-your-ci-system.md | 128 ++--- .../about-dependabot-alerts.md | 72 +-- ...isories-in-the-github-advisory-database.md | 8 +- ...isories-in-the-github-advisory-database.md | 4 +- ...tomating-dependabot-with-github-actions.md | 4 +- ...he-detection-of-vulnerable-dependencies.md | 91 ++-- .../securing-your-organization.md | 135 +++--- .../secret-scanning/about-secret-scanning.md | 4 + .../managing-alerts-from-secret-scanning.md | 2 +- .../about-the-security-overview.md | 2 +- .../securing-accounts.md | 112 +++-- .../about-supply-chain-security.md | 4 +- .../configuring-dependency-review.md | 2 +- ...pace-to-access-a-private-image-registry.md | 8 +- ...g-encrypted-secrets-for-your-codespaces.md | 113 ++--- .../pt-BR/content/codespaces/overview.md | 2 +- ...a-prebuild-to-access-other-repositories.md | 16 +- .../about-wikis.md | 33 +- .../changing-access-permissions-for-wikis.md | 22 +- ...g-started-with-github-copilot-in-neovim.md | 69 ++- ...epository-from-github-to-github-desktop.md | 42 +- .../about-connections-to-github.md | 20 +- .../authenticating-to-github.md | 148 +++--- .../rate-limits-for-github-apps.md | 41 +- .../authorizing-oauth-apps.md | 238 ++++----- .../scopes-for-oauth-apps.md | 127 +++-- .../getting-started-with-apps/about-apps.md | 101 ++-- .../requirements-for-listing-an-app.md | 76 ++- .../security-best-practices-for-apps.md | 80 ++- ...ting-a-listing-description-for-your-app.md | 204 ++++---- ...icing-plans-for-github-marketplace-apps.md | 48 +- .../developers/overview/about-githubs-apis.md | 8 +- .../overview/managing-deploy-keys.md | 4 +- .../secret-scanning-partner-program.md | 4 +- .../guides/finding-your-discussions.md | 28 +- .../managing-categories-for-discussions.md | 92 ++-- .../managing-discussions.md | 151 +++--- ...g-makecode-arcade-with-github-classroom.md | 30 +- .../view-autograding-results.md | 32 +- .../github-extensions-and-integrations.md | 4 +- ...-to-contribute-to-open-source-on-github.md | 48 +- .../about-remote-repositories.md | 76 ++- .../caching-your-github-credentials-in-git.md | 61 ++- .../managing-remote-repositories.md | 187 ++++--- ...ing-credentials-from-the-macos-keychain.md | 38 +- ...hy-is-git-always-asking-for-my-password.md | 22 +- .../adding-locally-hosted-code-to-github.md | 154 +++--- ...a-git-repository-using-the-command-line.md | 44 +- ...rting-a-repository-with-github-importer.md | 53 +- .../about-github-advanced-security.md | 2 +- .../access-permissions-on-github.md | 51 +- .../types-of-github-accounts.md | 75 +-- .../getting-started-with-github-ae.md | 87 ++-- ...ng-started-with-github-enterprise-cloud.md | 247 +++++----- ...g-started-with-github-enterprise-server.md | 138 +++--- .../getting-started-with-github-team.md | 97 ++-- ...etting-started-with-your-github-account.md | 222 ++++----- .../get-started/quickstart/create-a-repo.md | 91 ++-- .../get-started/quickstart/fork-a-repo.md | 176 +++---- .../verifying-your-email-address.md | 75 ++- .../get-started/using-git/about-git-rebase.md | 74 ++- ...g-a-subfolder-out-into-a-new-repository.md | 62 ++- .../using-github/github-command-palette.md | 257 +++++----- .../get-started/using-github/github-mobile.md | 95 ++-- .../github-cli/github-cli/quickstart.md | 36 +- .../guides/forming-calls-with-graphql.md | 225 +++++---- .../graphql/guides/introduction-to-graphql.md | 86 ++-- .../guides/managing-enterprise-accounts.md | 133 +++-- .../about-project-boards.md | 75 ++- .../automating-projects-using-actions.md | 106 ++-- .../automating-your-project/index.md | 1 + .../using-the-api-to-manage-projects.md | 2 +- .../customizing-a-view.md | 162 ++++--- .../best-practices-for-projects.md | 87 ++-- .../adding-items-to-your-project.md | 112 +++-- .../archiving-items-from-your-project.md | 69 ++- .../about-your-organizations-news-feed.md | 27 +- ...-authentication-and-saml-single-sign-on.md | 27 +- ...embers-saml-access-to-your-organization.md | 65 ++- .../pt-BR/content/organizations/index.md | 6 +- .../index.md | 1 - ...ing-the-audit-log-for-your-organization.md | 61 ++- ...ur-organizations-installed-integrations.md | 34 -- ...ithub-app-managers-in-your-organization.md | 42 -- .../index.md | 27 -- ...hub-app-managers-from-your-organization.md | 42 -- ...rs-to-repositories-in-your-organization.md | 52 -- ...tside-collaborator-in-your-organization.md | 31 -- ...ation-member-to-an-outside-collaborator.md | 65 --- ...-collaborator-to-an-organization-member.md | 34 -- .../index.md | 37 -- ...ls-access-to-an-organization-repository.md | 58 --- ...am-access-to-an-organization-repository.md | 73 --- ...llaborators-access-to-your-organization.md | 74 --- ...borator-from-an-organization-repository.md | 69 --- .../repository-roles-for-an-organization.md | 175 ------- ...ng-base-permissions-for-an-organization.md | 45 -- ...g-people-with-access-to-your-repository.md | 58 --- .../about-ssh-certificate-authorities.md | 50 +- ...nviting-users-to-join-your-organization.md | 36 +- .../deleting-an-organization-account.md | 37 +- ...e-for-repositories-in-your-organization.md | 39 +- ...ess-management-with-saml-single-sign-on.md | 49 +- ...saml-single-sign-on-and-scim-using-okta.md | 71 +-- .../about-teams.md | 75 ++- ...-a-team-with-an-identity-provider-group.md | 105 ++-- .../about-oauth-app-access-restrictions.md | 71 --- ...roving-oauth-apps-for-your-organization.md | 31 -- ...pproved-oauth-app-for-your-organization.md | 26 - ...cess-restrictions-for-your-organization.md | 32 -- ...cess-restrictions-for-your-organization.md | 37 -- .../index.md | 28 -- .../about-permissions-for-github-packages.md | 14 +- .../connecting-a-repository-to-a-package.md | 45 +- .../deleting-and-restoring-a-package.md | 6 +- .../installing-a-package.md | 30 +- .../introduction-to-github-packages.md | 4 +- .../publishing-a-package.md | 39 +- ...nstalling-a-package-with-github-actions.md | 14 +- ...ainer-registry-from-the-docker-registry.md | 41 +- .../working-with-the-apache-maven-registry.md | 59 ++- .../working-with-the-container-registry.md | 2 +- .../working-with-the-docker-registry.md | 172 ++++--- .../working-with-the-gradle-registry.md | 104 ++-- .../working-with-the-npm-registry.md | 181 ++++--- .../working-with-the-nuget-registry.md | 102 ++-- .../working-with-the-rubygems-registry.md | 82 ++-- .../about-github-pages.md | 147 +++--- translations/pt-BR/content/pages/index.md | 11 +- ...reating-a-github-pages-site-with-jekyll.md | 91 ++-- .../about-pull-request-merges.md | 88 ++-- ...pull-request-branch-created-from-a-fork.md | 71 ++- ...ng-dependency-changes-in-a-pull-request.md | 2 +- .../working-with-forks/about-forks.md | 32 +- .../working-with-forks/syncing-a-fork.md | 66 ++- .../changing-a-commit-message.md | 79 ++- ...g-a-commit-on-behalf-of-an-organization.md | 66 ++- ...creating-a-commit-with-multiple-authors.md | 78 ++- ...sts-on-github-but-not-in-my-local-clone.md | 67 +-- ...are-my-commits-linked-to-the-wrong-user.md | 51 +- .../backing-up-a-repository.md | 45 +- .../referencing-and-citing-content.md | 40 +- .../about-merge-methods-on-github.md | 42 +- ...guring-commit-merging-for-pull-requests.md | 2 +- ...uring-commit-rebasing-for-pull-requests.md | 2 +- ...ring-commit-squashing-for-pull-requests.md | 2 +- .../configuring-pull-request-merges/index.md | 10 +- .../renaming-a-branch.md | 46 +- .../about-repositories.md | 132 ++--- .../cloning-a-repository.md | 76 +-- .../duplicating-a-repository.md | 80 ++- .../restoring-a-deleted-repository.md | 43 +- .../troubleshooting-cloning-errors.md | 115 +++-- .../about-code-owners.md | 4 +- .../licensing-a-repository.md | 114 +++-- ...mmit-signoff-policy-for-your-repository.md | 26 +- .../setting-repository-visibility.md | 81 ++-- .../adding-a-file-to-a-repository.md | 49 +- .../about-large-files-on-github.md | 12 +- .../getting-permanent-links-to-files.md | 42 +- .../working-with-non-code-files.md | 8 +- .../content/rest/activity/notifications.md | 59 ++- .../content/rest/apps/oauth-applications.md | 13 +- .../content/rest/codespaces/codespaces.md | 15 +- .../rest/enterprise-admin/admin-stats.md | 15 +- .../rest/enterprise-admin/announcement.md | 17 +- .../rest/enterprise-admin/audit-log.md | 9 +- .../content/rest/enterprise-admin/billing.md | 9 +- .../rest/enterprise-admin/global-webhooks.md | 17 +- .../content/rest/enterprise-admin/index.md | 44 +- .../content/rest/enterprise-admin/ldap.md | 13 +- .../content/rest/enterprise-admin/license.md | 15 +- .../enterprise-admin/management-console.md | 31 +- .../enterprise-admin/org-pre-receive-hooks.md | 29 +- .../content/rest/enterprise-admin/orgs.md | 15 +- .../pre-receive-environments.md | 43 +- .../enterprise-admin/pre-receive-hooks.md | 36 +- .../repo-pre-receive-hooks.md | 27 +- .../content/rest/enterprise-admin/scim.md | 5 +- .../content/rest/enterprise-admin/users.md | 15 +- translations/pt-BR/content/rest/gitignore.md | 19 +- .../rest/guides/building-a-ci-server.md | 124 +++-- .../getting-started-with-the-rest-api.md | 40 +- .../rest/guides/traversing-with-pagination.md | 143 ++++-- .../rest/guides/working-with-comments.md | 69 +-- .../content/rest/migrations/source-imports.md | 17 +- .../pt-BR/content/rest/overview/index.md | 2 + .../overview/other-authentication-methods.md | 20 +- .../overview/resources-in-the-rest-api.md | 6 +- .../content/rest/overview/troubleshooting.md | 53 +- translations/pt-BR/content/rest/packages.md | 27 +- .../pt-BR/content/rest/projects/projects.md | 11 +- translations/pt-BR/content/rest/scim.md | 47 +- .../pt-BR/content/rest/teams/team-sync.md | 19 +- .../about-searching-on-github.md | 74 ++- ...rom-your-private-enterprise-environment.md | 29 +- .../searching-for-repositories.md | 206 ++++---- .../searching-issues-and-pull-requests.md | 2 +- ...p-github-sponsors-for-your-organization.md | 2 +- ...thub-sponsors-for-your-personal-account.md | 4 +- .../providing-data-to-github-support.md | 189 ++++---- .../about-github-premium-support.md | 135 +++--- .../pt-BR/data/learning-tracks/admin.yml | 38 +- .../enterprise-server/3-1/0-rc1.yml | 24 +- .../enterprise-server/3-2/0-rc1.yml | 4 +- .../release-notes/enterprise-server/3-2/0.yml | 2 +- .../enterprise-server/3-3/0-rc1.yml | 6 +- .../release-notes/enterprise-server/3-3/0.yml | 4 +- .../enterprise-server/3-4/0-rc1.yml | 4 +- .../release-notes/enterprise-server/3-4/0.yml | 4 +- .../release-notes/enterprise-server/3-4/1.yml | 2 +- .../release-notes/enterprise-server/3-4/2.yml | 2 +- .../enterprise-server/3-5/0-rc1.yml | 2 +- .../enterprise-server/3-6/0-rc1.yml | 2 +- .../actions/about-actions-for-enterprises.md | 10 +- .../reusables/actions/cache-default-size.md | 10 +- .../actions/disabling-github-actions.md | 10 +- .../actions/enterprise-common-prereqs.md | 14 +- .../actions/enterprise-http-proxy.md | 16 +- .../actions/enterprise-marketplace-actions.md | 10 +- .../enterprise-postinstall-nextsteps.md | 12 +- .../actions/github-connect-resolution.md | 10 +- .../jobs/section-defining-outputs-for-jobs.md | 28 +- ...-runner-management-permissions-required.md | 20 +- ...self-hosted-runner-networking-to-dotcom.md | 10 +- .../self-hosted-runner-ports-protocols.md | 12 +- .../upgrade-runners-before-upgrade-ghes.md | 10 +- .../actions/workflow-template-overview.md | 12 +- .../about-committer-numbers-ghec-ghes.md | 20 +- .../apps/user-to-server-rate-limits.md | 10 +- .../audit_log/audit-log-action-categories.md | 304 +++++++----- .../branches/new-repo-default-branch.md | 10 +- .../reusables/classroom/about-autograding.md | 10 +- ...ntext-for-actions-and-third-party-tools.md | 10 +- ...enterprise-enable-code-scanning-actions.md | 10 +- .../enterprise-enable-code-scanning.md | 2 +- .../code-scanning/what-is-codeql-cli.md | 10 +- .../creating-a-codespace-in-vscode.md | 2 +- .../command_line/provide-an-access-token.md | 10 +- .../copilot/install-copilot-in-neovim.md | 11 +- .../enterprise-enable-dependabot.md | 2 +- .../data/reusables/desktop/get-an-account.md | 14 +- ...ithub-discussions-for-your-organization.md | 23 +- .../discussions/navigate-to-repo-or-org.md | 10 +- .../discussions/starting-a-discussion.md | 26 +- .../dotcom_billing/view-all-subscriptions.md | 10 +- .../dormant-user-activity.md | 52 +- .../enterprise-accounts/emu-cap-validates.md | 10 +- .../enterprise-accounts/emu-forks.md | 10 +- .../emu-permission-follow.md | 10 +- .../emu-permission-fork.md | 10 +- .../emu-permission-gist.md | 10 +- .../emu-permission-interact.md | 10 +- .../emu-permission-propose.md | 10 +- .../emu-permission-repo.md | 10 +- .../enterprise-accounts/emu-short-summary.md | 10 +- .../enterprise-accounts/oidc-gei-warning.md | 10 +- .../enterprise/apply-configuration.md | 14 +- .../data/reusables/enterprise/rate_limit.md | 10 +- .../reusables/enterprise/test-in-staging.md | 10 +- .../installing-releases.md | 2 +- .../download-package.md | 12 +- .../hardware-considerations-all-platforms.md | 38 +- .../hotpatching-explanation.md | 2 +- .../image-urls-viewable-warning.md | 10 +- .../ssh-into-instance.md | 12 +- .../dormancy-threshold.md | 10 +- .../enterprise_site_admin_settings/sign-in.md | 10 +- .../tls-downtime.md | 10 +- ...natively-enable-external-authentication.md | 10 +- .../built-in-authentication-new-accounts.md | 10 +- .../built-in-authentication.md | 10 +- ...r-usernames-for-external-authentication.md | 10 +- .../disclaimer-for-git-read-access.md | 16 +- .../reusables/files/choose-commit-email.md | 13 +- .../data/reusables/getting-started/actions.md | 10 +- .../adding-members-to-organizations.md | 10 +- .../configuring-security-features.md | 10 +- .../getting-started/creating-organizations.md | 10 +- .../enforcing-repo-management-policies.md | 10 +- .../managing-enterprise-members.md | 10 +- .../pt-BR/data/reusables/git/git-push.md | 12 +- .../large_files/storage_assets_location.md | 11 +- .../data/reusables/large_files/use_lfs_tip.md | 10 +- .../notifications/outbound_email_tip.md | 16 +- .../reusables/notifications/shared_state.md | 10 +- .../organizations/navigate-to-org.md | 10 +- .../package_registry/authenticate-packages.md | 20 +- ...uthenticate-to-container-registry-steps.md | 26 +- .../authenticate_with_pat_for_v2_registry.md | 16 +- ...ext-steps-for-packages-enterprise-setup.md | 12 +- .../package-registry-with-github-tokens.md | 10 +- .../package_registry/packages-billing.md | 10 +- .../package_registry/required-scopes.md | 10 +- .../pages/build-failure-email-server.md | 16 +- .../data/reusables/pages/emu-org-only.md | 16 +- .../projects/enable-basic-workflow.md | 38 +- .../configure_pull_request_merges_intro.md | 10 +- .../pull_requests/default_merge_option.md | 12 +- .../pull_request_merges_and_contributions.md | 14 +- .../pull_requests/rebase_and_merge_summary.md | 16 +- .../pull_requests/squash_and_merge_summary.md | 14 +- .../reusables/repositories/deploy-keys.md | 10 +- .../repositories/enable-security-alerts.md | 11 +- .../repositories/navigate-to-repo.md | 10 +- .../reusables/repositories/you-can-fork.md | 17 +- .../rest-api/dotcom-only-guide-note.md | 14 +- .../saml/about-authorized-credentials.md | 10 +- .../reusables/saml/about-linked-identities.md | 12 +- .../about-saml-access-enterprise-account.md | 10 +- .../reusables/saml/authorized-creds-info.md | 20 +- .../saml/must-authorize-linked-identity.md | 10 +- .../you-must-periodically-authenticate.md | 10 +- .../reusables/scim/enterprise-account-scim.md | 10 +- .../data/reusables/scim/supported-idps.md | 13 +- .../data/reusables/search/syntax_tips.md | 16 +- .../enterprise-enable-secret-scanning.md | 2 +- .../partner-secret-list-private-repo.md | 4 + .../secret-list-private-push-protection.md | 4 + .../shortdesc/rate_limits_github_apps.md | 10 +- .../sponsors/select-sponsorship-billing.md | 10 +- .../pt-BR/data/reusables/ssh/about-ssh.md | 10 +- .../data/reusables/ssh/key-type-support.md | 23 +- .../rsa-sha-1-connection-failure-criteria.md | 12 +- .../data/reusables/support/submit-a-ticket.md | 79 +-- .../password-authentication-deprecation.md | 10 +- .../user-settings/personal_access_tokens.md | 12 +- .../removes-personal-access-tokens.md | 10 +- translations/pt-BR/data/variables/product.yml | 52 +- 571 files changed, 12804 insertions(+), 14454 deletions(-) delete mode 100644 translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md delete mode 100644 translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md delete mode 100644 translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/index.md delete mode 100644 translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md delete mode 100644 translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md delete mode 100644 translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md delete mode 100644 translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md delete mode 100644 translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md delete mode 100644 translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/index.md delete mode 100644 translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md delete mode 100644 translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md delete mode 100644 translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md delete mode 100644 translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md delete mode 100644 translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md delete mode 100644 translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md delete mode 100644 translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md delete mode 100644 translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md delete mode 100644 translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md delete mode 100644 translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md delete mode 100644 translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md delete mode 100644 translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md delete mode 100644 translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/index.md diff --git a/translations/log/msft-pt-resets.csv b/translations/log/msft-pt-resets.csv index fd50cfa477..00d0672857 100644 --- a/translations/log/msft-pt-resets.csv +++ b/translations/log/msft-pt-resets.csv @@ -129,7 +129,29 @@ translations/pt-BR/content/issues/trying-out-the-new-projects-experience/migrati translations/pt-BR/content/issues/trying-out-the-new-projects-experience/quickstart.md,file deleted because it no longer exists in main translations/pt-BR/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md,file deleted because it no longer exists in main translations/pt-BR/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/index.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/index.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md,file deleted because it no longer exists in main translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md,file deleted because it no longer exists in main +translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/index.md,file deleted because it no longer exists in main translations/pt-BR/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md,file deleted because it no longer exists in main translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/merging-an-upstream-repository-into-your-fork.md,file deleted because it no longer exists in main translations/pt-BR/content/rest/reference/actions.md,file deleted because it no longer exists in main @@ -245,21 +267,37 @@ translations/pt-BR/data/reusables/security-center/beta.md,file deleted because i translations/pt-BR/data/reusables/server-statistics/release-phase.md,file deleted because it no longer exists in main translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md,rendering error translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md,broken liquid tags +translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,broken liquid tags translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,rendering error +translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md,broken liquid tags translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md,rendering error translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,broken liquid tags translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md,broken liquid tags translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md,broken liquid tags +translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags +translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md,broken liquid tags translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md,broken liquid tags translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,rendering error translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,rendering error translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,rendering error +translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md,broken liquid tags +translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md,broken liquid tags +translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md,broken liquid tags +translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md,broken liquid tags +translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md,broken liquid tags +translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md,broken liquid tags +translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md,broken liquid tags translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error +translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md,broken liquid tags translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md,broken liquid tags +translations/pt-BR/content/actions/automating-builds-and-tests/about-continuous-integration.md,broken liquid tags +translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md,broken liquid tags +translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md,broken liquid tags translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md,rendering error translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error translations/pt-BR/content/actions/deployment/about-deployments/about-continuous-deployment.md,rendering error +translations/pt-BR/content/actions/deployment/about-deployments/deploying-with-github-actions.md,broken liquid tags translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md,rendering error translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md,rendering error translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md,rendering error @@ -270,19 +308,25 @@ translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/d translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md,rendering error translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md,rendering error translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md,rendering error +translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md,broken liquid tags translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md,broken liquid tags +translations/pt-BR/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md,broken liquid tags +translations/pt-BR/content/actions/examples/using-the-github-cli-on-a-runner.md,broken liquid tags translations/pt-BR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,rendering error translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,rendering error translations/pt-BR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md,rendering error translations/pt-BR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md,broken liquid tags translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md,rendering error +translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,broken liquid tags translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md,rendering error +translations/pt-BR/content/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job.md,broken liquid tags translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md,rendering error translations/pt-BR/content/actions/learn-github-actions/contexts.md,rendering error translations/pt-BR/content/actions/learn-github-actions/environment-variables.md,rendering error translations/pt-BR/content/actions/learn-github-actions/expressions.md,rendering error translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md,broken liquid tags translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md,rendering error +translations/pt-BR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,broken liquid tags translations/pt-BR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,broken liquid tags translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md,broken liquid tags translations/pt-BR/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error @@ -300,51 +344,193 @@ translations/pt-BR/content/actions/using-workflows/creating-starter-workflows-fo translations/pt-BR/content/actions/using-workflows/events-that-trigger-workflows.md,rendering error translations/pt-BR/content/actions/using-workflows/reusing-workflows.md,rendering error translations/pt-BR/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md,rendering error +translations/pt-BR/content/actions/using-workflows/storing-workflow-data-as-artifacts.md,broken liquid tags translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md,rendering error translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md,rendering error translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md,rendering error translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,broken liquid tags +translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md,broken liquid tags +translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,broken liquid tags translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md,broken liquid tags translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md,rendering error +translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-github-connect/index.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-github-connect/managing-github-connect.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-tls.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-network-settings/network-ports.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-applications.md,broken liquid tags translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,broken liquid tags translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md,broken liquid tags translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,rendering error +translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,broken liquid tags translations/pt-BR/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md,broken liquid tags translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags +translations/pt-BR/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,broken liquid tags +translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,broken liquid tags +translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,broken liquid tags +translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/index.md,broken liquid tags +translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md,broken liquid tags +translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md,broken liquid tags +translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md,broken liquid tags +translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,broken liquid tags +translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,broken liquid tags +translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md,broken liquid tags translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md,broken liquid tags +translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,broken liquid tags +translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md,broken liquid tags +translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md,broken liquid tags translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md,rendering error +translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md,broken liquid tags translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md,rendering error translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md,rendering error +translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md,broken liquid tags +translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md,broken liquid tags +translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/index.md,broken liquid tags translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md,broken liquid tags translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md,rendering error +translations/pt-BR/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,broken liquid tags translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,broken liquid tags translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md,broken liquid tags translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-for-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/index.md,broken liquid tags translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md,broken liquid tags +translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md,broken liquid tags +translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md,broken liquid tags +translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md,broken liquid tags +translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md,broken liquid tags +translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md,broken liquid tags +translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md,broken liquid tags translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md,broken liquid tags +translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md,broken liquid tags +translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,broken liquid tags +translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,broken liquid tags translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md,rendering error translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md,rendering error +translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md,broken liquid tags translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md,broken liquid tags translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md,rendering error +translations/pt-BR/content/admin/overview/about-data-residency.md,broken liquid tags +translations/pt-BR/content/admin/overview/about-enterprise-accounts.md,broken liquid tags +translations/pt-BR/content/admin/overview/about-github-enterprise-server.md,broken liquid tags translations/pt-BR/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/overview/system-overview.md,broken liquid tags +translations/pt-BR/content/admin/packages/enabling-github-packages-with-aws.md,broken liquid tags +translations/pt-BR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md,broken liquid tags +translations/pt-BR/content/admin/packages/enabling-github-packages-with-minio.md,broken liquid tags +translations/pt-BR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md,broken liquid tags +translations/pt-BR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md,broken liquid tags +translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md,broken liquid tags translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,broken liquid tags translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md,broken liquid tags translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md,broken liquid tags +translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,broken liquid tags +translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md,broken liquid tags +translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md,broken liquid tags +translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,broken liquid tags +translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md,broken liquid tags +translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md,broken liquid tags +translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,broken liquid tags +translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md,broken liquid tags translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md,rendering error +translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md,broken liquid tags +translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,broken liquid tags +translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md,broken liquid tags +translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,broken liquid tags +translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md,broken liquid tags translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md,rendering error translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md,rendering error translations/pt-BR/content/authentication/connecting-to-github-with-ssh/about-ssh.md,broken liquid tags +translations/pt-BR/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md,broken liquid tags +translations/pt-BR/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md,broken liquid tags translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error +translations/pt-BR/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md,broken liquid tags +translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,broken liquid tags +translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md,broken liquid tags +translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,broken liquid tags +translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,broken liquid tags +translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/index.md,broken liquid tags +translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,broken liquid tags +translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,broken liquid tags translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,rendering error +translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md,broken liquid tags +translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md,broken liquid tags +translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md,broken liquid tags +translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md,broken liquid tags translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,rendering error +translations/pt-BR/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md,broken liquid tags +translations/pt-BR/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md,broken liquid tags translations/pt-BR/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md,rendering error translations/pt-BR/content/authentication/managing-commit-signature-verification/index.md,broken liquid tags translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-commits.md,broken liquid tags translations/pt-BR/content/authentication/managing-commit-signature-verification/signing-tags.md,broken liquid tags translations/pt-BR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md,broken liquid tags +translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,broken liquid tags +translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,broken liquid tags +translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md,broken liquid tags +translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,broken liquid tags +translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,broken liquid tags translations/pt-BR/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md,broken liquid tags +translations/pt-BR/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,broken liquid tags +translations/pt-BR/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,broken liquid tags +translations/pt-BR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md,broken liquid tags translations/pt-BR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md,broken liquid tags translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,broken liquid tags translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error @@ -354,8 +540,19 @@ translations/pt-BR/content/billing/managing-billing-for-github-codespaces/managi translations/pt-BR/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md,broken liquid tags translations/pt-BR/content/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot.md,broken liquid tags translations/pt-BR/content/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription.md,broken liquid tags +translations/pt-BR/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md,broken liquid tags +translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md,broken liquid tags translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md,rendering error translations/pt-BR/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md,broken liquid tags +translations/pt-BR/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md,broken liquid tags +translations/pt-BR/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,broken liquid tags +translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md,broken liquid tags +translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md,broken liquid tags +translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md,broken liquid tags +translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,broken liquid tags +translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,broken liquid tags +translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,broken liquid tags +translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,broken liquid tags translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,rendering error translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,rendering error @@ -366,10 +563,15 @@ translations/pt-BR/content/code-security/code-scanning/automatically-scanning-yo translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md,rendering error translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md,rendering error translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md,rendering error +translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,broken liquid tags translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,rendering error +translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md,broken liquid tags translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md,rendering error translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,rendering error +translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,broken liquid tags translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags +translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,broken liquid tags +translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md,broken liquid tags translations/pt-BR/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md,rendering error translations/pt-BR/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md,rendering error translations/pt-BR/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md,broken liquid tags @@ -381,7 +583,9 @@ translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/c translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md,rendering error translations/pt-BR/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md,rendering error translations/pt-BR/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md,rendering error +translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md,broken liquid tags translations/pt-BR/content/code-security/getting-started/github-security-features.md,rendering error +translations/pt-BR/content/code-security/getting-started/securing-your-organization.md,broken liquid tags translations/pt-BR/content/code-security/getting-started/securing-your-repository.md,rendering error translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md,rendering error translations/pt-BR/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md,rendering error @@ -392,6 +596,7 @@ translations/pt-BR/content/code-security/secret-scanning/pushing-a-branch-blocke translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md,rendering error translations/pt-BR/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md,rendering error translations/pt-BR/content/code-security/security-overview/viewing-the-security-overview.md,rendering error +translations/pt-BR/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md,broken liquid tags translations/pt-BR/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md,rendering error translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md,rendering error translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md,rendering error @@ -427,6 +632,7 @@ translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/ translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md,broken liquid tags translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md,broken liquid tags translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces.md,broken liquid tags +translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md,broken liquid tags translations/pt-BR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md,broken liquid tags translations/pt-BR/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md,broken liquid tags translations/pt-BR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md,broken liquid tags @@ -449,19 +655,33 @@ translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-dotfiles-f translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-prebuilds.md,broken liquid tags translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-your-connection-to-github-codespaces.md,broken liquid tags translations/pt-BR/content/codespaces/troubleshooting/working-with-support-for-github-codespaces.md,broken liquid tags +translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md,broken liquid tags +translations/pt-BR/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,broken liquid tags translations/pt-BR/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,broken liquid tags translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md,broken liquid tags +translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md,broken liquid tags translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md,broken liquid tags translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md,broken liquid tags translations/pt-BR/content/copilot/quickstart.md,broken liquid tags +translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,broken liquid tags translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags +translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md,broken liquid tags +translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,broken liquid tags translations/pt-BR/content/developers/apps/building-github-apps/authenticating-with-github-apps.md,rendering error translations/pt-BR/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md,rendering error +translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,broken liquid tags +translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md,broken liquid tags +translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md,broken liquid tags +translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md,broken liquid tags translations/pt-BR/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md,broken liquid tags translations/pt-BR/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md,rendering error translations/pt-BR/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md,rendering error translations/pt-BR/content/developers/apps/guides/using-the-github-api-in-your-app.md,rendering error +translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,broken liquid tags +translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md,broken liquid tags +translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,broken liquid tags +translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,broken liquid tags translations/pt-BR/content/developers/overview/about-githubs-apis.md,broken liquid tags translations/pt-BR/content/developers/overview/managing-deploy-keys.md,broken liquid tags translations/pt-BR/content/developers/overview/secret-scanning-partner-program.md,broken liquid tags @@ -469,104 +689,215 @@ translations/pt-BR/content/developers/webhooks-and-events/events/issue-event-typ translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,rendering error translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md,broken liquid tags translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md,broken liquid tags +translations/pt-BR/content/discussions/guides/finding-your-discussions.md,broken liquid tags +translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,broken liquid tags +translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-discussions.md,broken liquid tags translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student.md,broken liquid tags translations/pt-BR/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/glossary.md,broken liquid tags +translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,broken liquid tags translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,broken liquid tags translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md,broken liquid tags +translations/pt-BR/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,broken liquid tags translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,broken liquid tags translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,broken liquid tags translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,broken liquid tags translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,broken liquid tags +translations/pt-BR/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,broken liquid tags translations/pt-BR/content/get-started/exploring-projects-on-github/following-organizations.md,broken liquid tags +translations/pt-BR/content/get-started/getting-started-with-git/about-remote-repositories.md,broken liquid tags translations/pt-BR/content/get-started/getting-started-with-git/associating-text-editors-with-git.md,broken liquid tags +translations/pt-BR/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md,broken liquid tags +translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md,broken liquid tags +translations/pt-BR/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,broken liquid tags +translations/pt-BR/content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md,broken liquid tags +translations/pt-BR/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md,broken liquid tags +translations/pt-BR/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md,broken liquid tags +translations/pt-BR/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md,broken liquid tags translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md,rendering error +translations/pt-BR/content/get-started/learning-about-github/access-permissions-on-github.md,broken liquid tags +translations/pt-BR/content/get-started/learning-about-github/types-of-github-accounts.md,broken liquid tags +translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md,broken liquid tags +translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,broken liquid tags +translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md,broken liquid tags +translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md,broken liquid tags +translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md,broken liquid tags translations/pt-BR/content/get-started/quickstart/be-social.md,broken liquid tags translations/pt-BR/content/get-started/quickstart/communicating-on-github.md,broken liquid tags +translations/pt-BR/content/get-started/quickstart/create-a-repo.md,broken liquid tags +translations/pt-BR/content/get-started/quickstart/fork-a-repo.md,broken liquid tags translations/pt-BR/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags translations/pt-BR/content/get-started/quickstart/github-glossary.md,rendering error +translations/pt-BR/content/get-started/signing-up-for-github/verifying-your-email-address.md,broken liquid tags +translations/pt-BR/content/get-started/using-git/about-git-rebase.md,broken liquid tags +translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md,broken liquid tags +translations/pt-BR/content/get-started/using-github/github-command-palette.md,broken liquid tags +translations/pt-BR/content/get-started/using-github/github-mobile.md,broken liquid tags translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md,rendering error translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md,broken liquid tags translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md,rendering error translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md,broken liquid tags translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md,broken liquid tags translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md,rendering error +translations/pt-BR/content/github-cli/github-cli/quickstart.md,broken liquid tags +translations/pt-BR/content/graphql/guides/forming-calls-with-graphql.md,broken liquid tags +translations/pt-BR/content/graphql/guides/introduction-to-graphql.md,broken liquid tags +translations/pt-BR/content/graphql/guides/managing-enterprise-accounts.md,broken liquid tags translations/pt-BR/content/graphql/guides/migrating-from-rest-to-graphql.md,broken liquid tags translations/pt-BR/content/graphql/overview/about-the-graphql-api.md,rendering error +translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md,broken liquid tags +translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md,broken liquid tags translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md,broken liquid tags +translations/pt-BR/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md,broken liquid tags +translations/pt-BR/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md,broken liquid tags +translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md,broken liquid tags +translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md,broken liquid tags translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md,broken liquid tags translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md,broken liquid tags translations/pt-BR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md,rendering error translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error +translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,broken liquid tags +translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,broken liquid tags +translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,broken liquid tags translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md,rendering error translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,rendering error -translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md,rendering error translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md,rendering error -translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md,rendering error -translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md,rendering error -translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md,rendering error -translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md,rendering error -translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md,rendering error -translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md,rendering error +translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md,broken liquid tags +translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,broken liquid tags translations/pt-BR/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md,broken liquid tags +translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md,broken liquid tags translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md,rendering error translations/pt-BR/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md,rendering error translations/pt-BR/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md,rendering error +translations/pt-BR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,broken liquid tags translations/pt-BR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error +translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md,broken liquid tags +translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,broken liquid tags +translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md,rendering error -translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md,broken liquid tags -translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md,broken liquid tags +translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md,broken liquid tags translations/pt-BR/content/packages/learn-github-packages/about-permissions-for-github-packages.md,rendering error translations/pt-BR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md,rendering error +translations/pt-BR/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md,broken liquid tags translations/pt-BR/content/packages/learn-github-packages/deleting-and-restoring-a-package.md,rendering error +translations/pt-BR/content/packages/learn-github-packages/installing-a-package.md,broken liquid tags translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md,rendering error +translations/pt-BR/content/packages/learn-github-packages/publishing-a-package.md,broken liquid tags translations/pt-BR/content/packages/learn-github-packages/viewing-packages.md,rendering error translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,rendering error +translations/pt-BR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md,broken liquid tags +translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,broken liquid tags translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,rendering error +translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md,broken liquid tags +translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md,broken liquid tags +translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md,broken liquid tags +translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md,broken liquid tags +translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md,broken liquid tags translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,rendering error +translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md,broken liquid tags translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md,rendering error +translations/pt-BR/content/pages/index.md,broken liquid tags +translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md,broken liquid tags translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,broken liquid tags +translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md,broken liquid tags translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md,broken liquid tags +translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,broken liquid tags translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md,rendering error translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md,rendering error translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md,rendering error translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,rendering error +translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md,broken liquid tags +translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md,broken liquid tags +translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,broken liquid tags +translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,broken liquid tags +translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,broken liquid tags +translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,broken liquid tags +translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md,broken liquid tags translations/pt-BR/content/repositories/archiving-a-github-repository/archiving-repositories.md,rendering error +translations/pt-BR/content/repositories/archiving-a-github-repository/backing-up-a-repository.md,broken liquid tags +translations/pt-BR/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md,broken liquid tags +translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md,broken liquid tags translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md,rendering error translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md,rendering error translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md,rendering error +translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md,broken liquid tags translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md,rendering error translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md,rendering error translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md,rendering error translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md,rendering error translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md,rendering error translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md,rendering error +translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,broken liquid tags +translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md,broken liquid tags +translations/pt-BR/content/repositories/creating-and-managing-repositories/cloning-a-repository.md,broken liquid tags +translations/pt-BR/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md,broken liquid tags +translations/pt-BR/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md,broken liquid tags translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,rendering error +translations/pt-BR/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,broken liquid tags translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md,rendering error translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md,rendering error +translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,broken liquid tags translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,rendering error translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md,rendering error translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md,rendering error translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md,rendering error +translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md,broken liquid tags +translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,broken liquid tags translations/pt-BR/content/repositories/releasing-projects-on-github/about-releases.md,rendering error translations/pt-BR/content/repositories/releasing-projects-on-github/comparing-releases.md,rendering error translations/pt-BR/content/repositories/releasing-projects-on-github/linking-to-releases.md,rendering error translations/pt-BR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error +translations/pt-BR/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,broken liquid tags translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,broken liquid tags +translations/pt-BR/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,broken liquid tags translations/pt-BR/content/repositories/working-with-files/using-files/working-with-non-code-files.md,rendering error +translations/pt-BR/content/rest/activity/notifications.md,broken liquid tags +translations/pt-BR/content/rest/apps/oauth-applications.md,broken liquid tags +translations/pt-BR/content/rest/codespaces/codespaces.md,broken liquid tags translations/pt-BR/content/rest/dependabot/index.md,broken liquid tags +translations/pt-BR/content/rest/enterprise-admin/admin-stats.md,broken liquid tags +translations/pt-BR/content/rest/enterprise-admin/announcement.md,broken liquid tags +translations/pt-BR/content/rest/enterprise-admin/audit-log.md,broken liquid tags +translations/pt-BR/content/rest/enterprise-admin/billing.md,broken liquid tags +translations/pt-BR/content/rest/enterprise-admin/global-webhooks.md,broken liquid tags +translations/pt-BR/content/rest/enterprise-admin/index.md,broken liquid tags +translations/pt-BR/content/rest/enterprise-admin/ldap.md,broken liquid tags +translations/pt-BR/content/rest/enterprise-admin/license.md,broken liquid tags +translations/pt-BR/content/rest/enterprise-admin/management-console.md,broken liquid tags +translations/pt-BR/content/rest/enterprise-admin/org-pre-receive-hooks.md,broken liquid tags +translations/pt-BR/content/rest/enterprise-admin/orgs.md,broken liquid tags +translations/pt-BR/content/rest/enterprise-admin/pre-receive-environments.md,broken liquid tags +translations/pt-BR/content/rest/enterprise-admin/pre-receive-hooks.md,broken liquid tags +translations/pt-BR/content/rest/enterprise-admin/repo-pre-receive-hooks.md,broken liquid tags translations/pt-BR/content/rest/enterprise-admin/scim.md,broken liquid tags +translations/pt-BR/content/rest/enterprise-admin/users.md,broken liquid tags +translations/pt-BR/content/rest/gitignore.md,broken liquid tags +translations/pt-BR/content/rest/guides/building-a-ci-server.md,broken liquid tags translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md,broken liquid tags +translations/pt-BR/content/rest/guides/traversing-with-pagination.md,broken liquid tags +translations/pt-BR/content/rest/guides/working-with-comments.md,broken liquid tags +translations/pt-BR/content/rest/migrations/source-imports.md,broken liquid tags translations/pt-BR/content/rest/overview/other-authentication-methods.md,broken liquid tags translations/pt-BR/content/rest/overview/permissions-required-for-github-apps.md,rendering error translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md,broken liquid tags +translations/pt-BR/content/rest/overview/troubleshooting.md,broken liquid tags +translations/pt-BR/content/rest/packages.md,broken liquid tags +translations/pt-BR/content/rest/projects/projects.md,broken liquid tags translations/pt-BR/content/rest/repos/lfs.md,broken liquid tags +translations/pt-BR/content/rest/scim.md,broken liquid tags +translations/pt-BR/content/rest/teams/team-sync.md,broken liquid tags +translations/pt-BR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md,broken liquid tags +translations/pt-BR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,broken liquid tags +translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md,broken liquid tags translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md,rendering error translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md,broken liquid tags translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,broken liquid tags translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,broken liquid tags +translations/pt-BR/content/support/contacting-github-support/providing-data-to-github-support.md,broken liquid tags +translations/pt-BR/content/support/learning-about-github-support/about-github-premium-support.md,broken liquid tags translations/pt-BR/content/support/learning-about-github-support/about-github-support.md,rendering error translations/pt-BR/data/glossaries/external.yml,broken liquid tags +translations/pt-BR/data/learning-tracks/admin.yml,broken liquid tags translations/pt-BR/data/release-notes/enterprise-server/2-20/13.yml,broken liquid tags translations/pt-BR/data/release-notes/enterprise-server/2-20/15.yml,rendering error translations/pt-BR/data/release-notes/enterprise-server/2-21/17.yml,rendering error @@ -584,6 +915,7 @@ translations/pt-BR/data/release-notes/enterprise-server/3-0/1.yml,rendering erro translations/pt-BR/data/release-notes/enterprise-server/3-0/2.yml,rendering error translations/pt-BR/data/release-notes/enterprise-server/3-0/22.yml,broken liquid tags translations/pt-BR/data/release-notes/enterprise-server/3-0/3.yml,rendering error +translations/pt-BR/data/release-notes/enterprise-server/3-1/0-rc1.yml,broken liquid tags translations/pt-BR/data/release-notes/enterprise-server/3-1/0.yml,rendering error translations/pt-BR/data/release-notes/enterprise-server/3-1/1.yml,rendering error translations/pt-BR/data/release-notes/enterprise-server/3-1/14.yml,broken liquid tags @@ -618,11 +950,20 @@ translations/pt-BR/data/release-notes/enterprise-server/3-4/8.yml,rendering erro translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml,rendering error translations/pt-BR/data/release-notes/enterprise-server/3-5/4.yml,rendering error translations/pt-BR/data/release-notes/enterprise-server/3-6/0-rc1.yml,rendering error +translations/pt-BR/data/reusables/actions/about-actions-for-enterprises.md,broken liquid tags translations/pt-BR/data/reusables/actions/actions-audit-events-workflow.md,rendering error translations/pt-BR/data/reusables/actions/actions-billing.md,broken liquid tags translations/pt-BR/data/reusables/actions/actions-do-not-trigger-workflows.md,broken liquid tags +translations/pt-BR/data/reusables/actions/cache-default-size.md,broken liquid tags translations/pt-BR/data/reusables/actions/create-runner-group.md,rendering error +translations/pt-BR/data/reusables/actions/disabling-github-actions.md,broken liquid tags +translations/pt-BR/data/reusables/actions/enterprise-common-prereqs.md,broken liquid tags +translations/pt-BR/data/reusables/actions/enterprise-http-proxy.md,broken liquid tags +translations/pt-BR/data/reusables/actions/enterprise-marketplace-actions.md,broken liquid tags +translations/pt-BR/data/reusables/actions/enterprise-postinstall-nextsteps.md,broken liquid tags +translations/pt-BR/data/reusables/actions/github-connect-resolution.md,broken liquid tags translations/pt-BR/data/reusables/actions/ip-allow-list-self-hosted-runners.md,broken liquid tags +translations/pt-BR/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md,broken liquid tags translations/pt-BR/data/reusables/actions/jobs/section-running-jobs-in-a-container.md,broken liquid tags translations/pt-BR/data/reusables/actions/ref_name-description.md,broken liquid tags translations/pt-BR/data/reusables/actions/reusable-workflow-artifacts.md,rendering error @@ -630,28 +971,41 @@ translations/pt-BR/data/reusables/actions/reusable-workflow-calling-syntax.md,re translations/pt-BR/data/reusables/actions/reusable-workflows.md,rendering error translations/pt-BR/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md,rendering error translations/pt-BR/data/reusables/actions/self-hosted-runner-add-to-enterprise.md,rendering error +translations/pt-BR/data/reusables/actions/self-hosted-runner-management-permissions-required.md,broken liquid tags +translations/pt-BR/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md,broken liquid tags +translations/pt-BR/data/reusables/actions/self-hosted-runner-ports-protocols.md,broken liquid tags translations/pt-BR/data/reusables/actions/settings-ui/settings-actions-general.md,rendering error translations/pt-BR/data/reusables/actions/settings-ui/settings-actions-runner-groups.md,rendering error translations/pt-BR/data/reusables/actions/settings-ui/settings-actions-runners.md,rendering error translations/pt-BR/data/reusables/actions/sidebar-secret.md,rendering error +translations/pt-BR/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md,broken liquid tags translations/pt-BR/data/reusables/actions/usage-workflow-run-time.md,rendering error translations/pt-BR/data/reusables/actions/workflow-basic-example-and-explanation.md,broken liquid tags translations/pt-BR/data/reusables/actions/workflow-dispatch-inputs.md,rendering error +translations/pt-BR/data/reusables/actions/workflow-template-overview.md,broken liquid tags +translations/pt-BR/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md,broken liquid tags translations/pt-BR/data/reusables/advanced-security/about-ghas-organization-policy.md,broken liquid tags translations/pt-BR/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md,rendering error translations/pt-BR/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md,rendering error translations/pt-BR/data/reusables/advanced-security/secret-scanning-push-protection-org.md,broken liquid tags +translations/pt-BR/data/reusables/apps/user-to-server-rate-limits.md,broken liquid tags +translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md,broken liquid tags translations/pt-BR/data/reusables/audit_log/audit-log-events-workflows.md,rendering error translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md,rendering error translations/pt-BR/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md,rendering error +translations/pt-BR/data/reusables/branches/new-repo-default-branch.md,broken liquid tags +translations/pt-BR/data/reusables/classroom/about-autograding.md,broken liquid tags translations/pt-BR/data/reusables/code-scanning/analyze-go.md,broken liquid tags translations/pt-BR/data/reusables/code-scanning/autobuild-add-build-steps.md,broken liquid tags +translations/pt-BR/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags translations/pt-BR/data/reusables/code-scanning/codeql-languages-bullets.md,rendering error translations/pt-BR/data/reusables/code-scanning/codeql-languages-keywords.md,rendering error +translations/pt-BR/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md,broken liquid tags translations/pt-BR/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags translations/pt-BR/data/reusables/code-scanning/example-configuration-files.md,broken liquid tags translations/pt-BR/data/reusables/code-scanning/licensing-note.md,broken liquid tags translations/pt-BR/data/reusables/code-scanning/run-additional-queries.md,broken liquid tags +translations/pt-BR/data/reusables/code-scanning/what-is-codeql-cli.md,broken liquid tags translations/pt-BR/data/reusables/codespaces/codespaces-api-beta-note.md,broken liquid tags translations/pt-BR/data/reusables/codespaces/codespaces-spending-limit-requirement.md,broken liquid tags translations/pt-BR/data/reusables/codespaces/creating-a-codespace-in-vscode.md,broken liquid tags @@ -664,57 +1018,141 @@ translations/pt-BR/data/reusables/codespaces/rebuild-command.md,broken liquid ta translations/pt-BR/data/reusables/codespaces/secrets-on-start.md,broken liquid tags translations/pt-BR/data/reusables/codespaces/use-chrome.md,broken liquid tags translations/pt-BR/data/reusables/codespaces/your-codespaces-procedure-step.md,broken liquid tags +translations/pt-BR/data/reusables/command_line/provide-an-access-token.md,broken liquid tags +translations/pt-BR/data/reusables/copilot/install-copilot-in-neovim.md,broken liquid tags translations/pt-BR/data/reusables/dependabot/beta-security-and-version-updates.md,rendering error translations/pt-BR/data/reusables/dependabot/default-dependencies-allow-ignore.md,broken liquid tags translations/pt-BR/data/reusables/dependabot/enabling-disabling-dependency-graph-private-repo.md,rendering error translations/pt-BR/data/reusables/dependabot/enterprise-enable-dependabot.md,rendering error +translations/pt-BR/data/reusables/desktop/get-an-account.md,broken liquid tags +translations/pt-BR/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md,broken liquid tags +translations/pt-BR/data/reusables/discussions/navigate-to-repo-or-org.md,broken liquid tags +translations/pt-BR/data/reusables/discussions/starting-a-discussion.md,broken liquid tags translations/pt-BR/data/reusables/dotcom_billing/actions-packages-report-download-org-account.md,broken liquid tags +translations/pt-BR/data/reusables/dotcom_billing/view-all-subscriptions.md,broken liquid tags translations/pt-BR/data/reusables/education/submit-application.md,broken liquid tags translations/pt-BR/data/reusables/enterprise-accounts/actions-packages-report-download-enterprise-accounts.md,broken liquid tags translations/pt-BR/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise-accounts/dormant-user-activity.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise-accounts/emu-cap-validates.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise-accounts/emu-forks.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-follow.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-fork.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-gist.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-interact.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-propose.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-repo.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise-accounts/emu-short-summary.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise-accounts/oidc-gei-warning.md,broken liquid tags translations/pt-BR/data/reusables/enterprise-accounts/security-tab.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise/apply-configuration.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise/rate_limit.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise/test-in-staging.md,broken liquid tags translations/pt-BR/data/reusables/enterprise_enterprise_support/installing-releases.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise_installation/download-package.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md,broken liquid tags translations/pt-BR/data/reusables/enterprise_installation/hotpatching-explanation.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise_installation/image-urls-viewable-warning.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise_installation/ssh-into-instance.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise_site_admin_settings/sign-in.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise_site_admin_settings/tls-downtime.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise_user_management/built-in-authentication.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md,broken liquid tags +translations/pt-BR/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,broken liquid tags +translations/pt-BR/data/reusables/files/choose-commit-email.md,broken liquid tags translations/pt-BR/data/reusables/gated-features/code-scanning.md,broken liquid tags translations/pt-BR/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags translations/pt-BR/data/reusables/gated-features/dependency-vulnerable-calls.md,rendering error translations/pt-BR/data/reusables/gated-features/secret-scanning-partner.md,rendering error translations/pt-BR/data/reusables/gated-features/secret-scanning.md,rendering error +translations/pt-BR/data/reusables/getting-started/actions.md,broken liquid tags +translations/pt-BR/data/reusables/getting-started/adding-members-to-organizations.md,broken liquid tags +translations/pt-BR/data/reusables/getting-started/configuring-security-features.md,broken liquid tags +translations/pt-BR/data/reusables/getting-started/creating-organizations.md,broken liquid tags +translations/pt-BR/data/reusables/getting-started/enforcing-repo-management-policies.md,broken liquid tags translations/pt-BR/data/reusables/getting-started/enterprise-advanced-security.md,broken liquid tags +translations/pt-BR/data/reusables/getting-started/managing-enterprise-members.md,broken liquid tags +translations/pt-BR/data/reusables/git/git-push.md,broken liquid tags translations/pt-BR/data/reusables/identity-and-permissions/ip-allow-lists-enable.md,broken liquid tags translations/pt-BR/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md,broken liquid tags +translations/pt-BR/data/reusables/large_files/storage_assets_location.md,broken liquid tags +translations/pt-BR/data/reusables/large_files/use_lfs_tip.md,broken liquid tags translations/pt-BR/data/reusables/notifications-v2/custom-notification-types.md,broken liquid tags +translations/pt-BR/data/reusables/notifications/outbound_email_tip.md,broken liquid tags +translations/pt-BR/data/reusables/notifications/shared_state.md,broken liquid tags translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-options.md,rendering error translations/pt-BR/data/reusables/organizations/billing_plans.md,rendering error translations/pt-BR/data/reusables/organizations/github-apps-settings-sidebar.md,rendering error translations/pt-BR/data/reusables/organizations/member-privileges.md,rendering error +translations/pt-BR/data/reusables/organizations/navigate-to-org.md,broken liquid tags translations/pt-BR/data/reusables/organizations/repository-defaults.md,rendering error translations/pt-BR/data/reusables/organizations/security-and-analysis.md,rendering error translations/pt-BR/data/reusables/organizations/security.md,rendering error translations/pt-BR/data/reusables/organizations/teams_sidebar.md,rendering error translations/pt-BR/data/reusables/organizations/verified-domains.md,rendering error +translations/pt-BR/data/reusables/package_registry/authenticate-packages.md,broken liquid tags +translations/pt-BR/data/reusables/package_registry/authenticate-to-container-registry-steps.md,broken liquid tags +translations/pt-BR/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md,broken liquid tags +translations/pt-BR/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,broken liquid tags +translations/pt-BR/data/reusables/package_registry/package-registry-with-github-tokens.md,broken liquid tags +translations/pt-BR/data/reusables/package_registry/packages-billing.md,broken liquid tags +translations/pt-BR/data/reusables/package_registry/required-scopes.md,broken liquid tags +translations/pt-BR/data/reusables/pages/build-failure-email-server.md,broken liquid tags +translations/pt-BR/data/reusables/pages/emu-org-only.md,broken liquid tags translations/pt-BR/data/reusables/pages/sidebar-pages.md,rendering error +translations/pt-BR/data/reusables/projects/enable-basic-workflow.md,broken liquid tags +translations/pt-BR/data/reusables/pull_requests/configure_pull_request_merges_intro.md,broken liquid tags +translations/pt-BR/data/reusables/pull_requests/default_merge_option.md,broken liquid tags translations/pt-BR/data/reusables/pull_requests/merge-queue-beta.md,broken liquid tags +translations/pt-BR/data/reusables/pull_requests/pull_request_merges_and_contributions.md,broken liquid tags +translations/pt-BR/data/reusables/pull_requests/rebase_and_merge_summary.md,broken liquid tags translations/pt-BR/data/reusables/pull_requests/resolving-conversations.md,broken liquid tags +translations/pt-BR/data/reusables/pull_requests/squash_and_merge_summary.md,broken liquid tags translations/pt-BR/data/reusables/release-notes/ghas-3.4-secret-scanning-known-issue.md,rendering error translations/pt-BR/data/reusables/repositories/changed-files.md,broken liquid tags +translations/pt-BR/data/reusables/repositories/deploy-keys.md,broken liquid tags +translations/pt-BR/data/reusables/repositories/enable-security-alerts.md,broken liquid tags translations/pt-BR/data/reusables/repositories/navigate-to-code-security-and-analysis.md,rendering error translations/pt-BR/data/reusables/repositories/navigate-to-commit-page.md,broken liquid tags +translations/pt-BR/data/reusables/repositories/navigate-to-repo.md,broken liquid tags translations/pt-BR/data/reusables/repositories/repository-branches.md,rendering error translations/pt-BR/data/reusables/repositories/sidebar-notifications.md,rendering error translations/pt-BR/data/reusables/repositories/suggest-changes.md,broken liquid tags +translations/pt-BR/data/reusables/repositories/you-can-fork.md,broken liquid tags +translations/pt-BR/data/reusables/rest-api/dotcom-only-guide-note.md,broken liquid tags +translations/pt-BR/data/reusables/saml/about-authorized-credentials.md,broken liquid tags +translations/pt-BR/data/reusables/saml/about-linked-identities.md,broken liquid tags +translations/pt-BR/data/reusables/saml/about-saml-access-enterprise-account.md,broken liquid tags +translations/pt-BR/data/reusables/saml/authorized-creds-info.md,broken liquid tags +translations/pt-BR/data/reusables/saml/must-authorize-linked-identity.md,broken liquid tags +translations/pt-BR/data/reusables/saml/you-must-periodically-authenticate.md,broken liquid tags +translations/pt-BR/data/reusables/scim/enterprise-account-scim.md,broken liquid tags +translations/pt-BR/data/reusables/scim/supported-idps.md,broken liquid tags +translations/pt-BR/data/reusables/search/syntax_tips.md,broken liquid tags translations/pt-BR/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md,broken liquid tags translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md,rendering error translations/pt-BR/data/reusables/secret-scanning/push-protection-web-ui-choice.md,broken liquid tags translations/pt-BR/data/reusables/secret-scanning/secret-list-private-push-protection.md,rendering error translations/pt-BR/data/reusables/security-overview/permissions.md,rendering error +translations/pt-BR/data/reusables/shortdesc/rate_limits_github_apps.md,broken liquid tags +translations/pt-BR/data/reusables/sponsors/select-sponsorship-billing.md,broken liquid tags +translations/pt-BR/data/reusables/ssh/about-ssh.md,broken liquid tags +translations/pt-BR/data/reusables/ssh/key-type-support.md,broken liquid tags +translations/pt-BR/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md,broken liquid tags translations/pt-BR/data/reusables/support/help_resources.md,rendering error +translations/pt-BR/data/reusables/support/submit-a-ticket.md,broken liquid tags translations/pt-BR/data/reusables/user-settings/access_applications.md,rendering error translations/pt-BR/data/reusables/user-settings/account_settings.md,rendering error translations/pt-BR/data/reusables/user-settings/appearance-settings.md,rendering error translations/pt-BR/data/reusables/user-settings/developer_settings.md,rendering error translations/pt-BR/data/reusables/user-settings/emails.md,rendering error translations/pt-BR/data/reusables/user-settings/organizations.md,rendering error +translations/pt-BR/data/reusables/user-settings/password-authentication-deprecation.md,broken liquid tags +translations/pt-BR/data/reusables/user-settings/personal_access_tokens.md,broken liquid tags +translations/pt-BR/data/reusables/user-settings/removes-personal-access-tokens.md,broken liquid tags translations/pt-BR/data/reusables/user-settings/repo-tab.md,rendering error translations/pt-BR/data/reusables/user-settings/saved_replies.md,rendering error translations/pt-BR/data/reusables/user-settings/security-analysis.md,rendering error @@ -726,3 +1164,4 @@ translations/pt-BR/data/reusables/webhooks/repository_vulnerability_alert_short_ translations/pt-BR/data/reusables/webhooks/workflow_run_properties.md,broken liquid tags translations/pt-BR/data/variables/migrations.yml,broken liquid tags translations/pt-BR/data/variables/notifications.yml,broken liquid tags +translations/pt-BR/data/variables/product.yml,broken liquid tags diff --git a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md index 1dee48d757..18798d0d6f 100644 --- a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md +++ b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md @@ -1,6 +1,6 @@ --- -title: Sobre notificações -intro: 'Notificações fornecem atualizações sobre a atividade no {% data variables.product.product_location %} que você assinou. Você pode usar a caixa de entrada de notificações para personalizar, fazer triagem e gerenciar atualizações.' +title: About notifications +intro: 'Notifications provide updates about the activity on {% data variables.location.product_location %} that you''ve subscribed to. You can use the notifications inbox to customize, triage, and manage your updates.' redirect_from: - /articles/notifications - /articles/about-notifications @@ -14,90 +14,86 @@ versions: ghec: '*' topics: - Notifications -ms.openlocfilehash: 87034df88eb94c1d880806f01cb8748ed555a284 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147432021' --- -## Notificações e assinaturas -Você pode optar por receber atualizações contínuas sobre atividades específicas no {% data variables.product.product_location %} por meio de uma assinatura. As notificações são atualizações que você recebe para atividades específicas que você assinou. +## Notifications and subscriptions -### Opções de Assinatura +You can choose to receive ongoing updates about specific activity on {% data variables.location.product_location %} through a subscription. Notifications are updates that you receive for specific activity that you are subscribed to. -Você pode optar por assinar notificações para: -- Uma conversa em um problema específico, pull request ou gist. -- Todas as atividades em um repositório ou em uma discussão em equipe. -- Atividade CI, como o status de fluxos de trabalho nos repositórios configurados com {% data variables.product.prodname_actions %}. -- Repositório {% data reusables.notifications-v2.custom-notification-types %} (se habilitado). +### Subscription options -Você também pode optar por assistir automaticamente todos os repositórios aos quais você tem acesso de push, exceto as bifurcações. Você pode inspecionar qualquer outro repositório ao qual tem acesso manualmente clicando em **Inspecionar**. +You can choose to subscribe to notifications for: +- A conversation in a specific issue, pull request, or gist. +- All activity in a repository or team discussion. +- CI activity, such as the status of workflows in repositories set up with {% data variables.product.prodname_actions %}. +- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled). -Se não estiver mais interessado em uma conversa, cancele a assinatura dela, deixe de acompanhar ou personalize os tipos de notificações que você receberá no futuro. Por exemplo, se você não quiser mais receber notificações de um repositório específico, clique em **Cancelar assinatura**. Para obter mais informações, confira "[Como gerenciar suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)". +You can also choose to automatically watch all repositories that you have push access to, except forks. You can watch any other repository you have access to manually by clicking **Watch**. -### Assinaturas padrão +If you're no longer interested in a conversation, you can unsubscribe, unwatch, or customize the types of notifications you'll receive in the future. For example, if you no longer want to receive notifications from a particular repository, you can click **Unsubscribe**. For more information, see "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." -Em geral, você é automaticamente inscrito em conversas por padrão quando você tem: -- Visualização automática não desabilitada de repositórios ou equipes às quais você se afiliou em suas configurações de notificação. Essa configuração é habilitada por padrão. -- Responsabilização por um problema ou uma pull request. -- A abertura de uma pull request, um problema ou tenha criado um post de discussão em equipe. -- Comentários em uma thread. -- Se inscreveu em uma conversa manualmente clicando em **Inspecionar** ou **Inscrever-se**. -- Teve seu nome de usuário @mentioned. -- Alteração do estado de uma thread, como por exemplo, fechando um problema ou mesclando uma pull request. -- Teve uma equipe da qual você é membro @mentioned. +### Default subscriptions -Por padrão, você também inspeciona automaticamente todos os repositórios que você cria e são pertencentes à sua conta pessoal. +In general, you are automatically subscribed to conversations by default when you have: +- Not disabled automatic watching for repositories or teams you've joined in your notification settings. This setting is enabled by default. +- Been assigned to an issue or pull request. +- Opened a pull request, issue, or created a team discussion post. +- Commented on a thread. +- Subscribed to a thread manually by clicking **Watch** or **Subscribe**. +- Had your username @mentioned. +- Changed the state of a thread, such as by closing an issue or merging a pull request. +- Had a team you're a member of @mentioned. -Para cancelar a assinatura de conversas às quais você está inscrito automaticamente, altere as configurações de notificação, cancele a assinatura ou a inspeção da atividade diretamente no {% data variables.product.product_location %}. Para obter mais informações, confira "[Como gerenciar suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)". +By default, you also automatically watch all repositories that you create and are owned by your personal account. -## Personalizando notificações e assinaturas +To unsubscribe from conversations you're automatically subscribed to, you can change your notification settings or directly unsubscribe or unwatch activity on {% data variables.location.product_location %}. For more information, see "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." -Você pode optar por ver suas notificações por meio da caixa de entrada de notificações em [https://github.com/notifications](https://github.com/notifications){% ifversion fpt or ghes or ghec %} e no aplicativo {% data variables.product.prodname_mobile %}{% endif %}, pelo email ou por alguma combinação dessas opções. +## Customizing notifications and subscriptions -Para personalizar os tipos de atualizações que você gostaria de receber e para onde enviar essas atualizações, configure suas configurações de notificação. Para obter mais informações, confira "[Como configurar notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)". +You can choose to view your notifications through the notifications inbox at [https://github.com/notifications](https://github.com/notifications){% ifversion fpt or ghes or ghec %} and in the {% data variables.product.prodname_mobile %} app{% endif %}, through your email, or some combination of these options. -Para manter suas assinaturas gerenciáveis, revise suas assinaturas e os repositórios inspecionados e cancele sua assinatura conforme necessário. Para obter mais informações, confira "[Como gerenciar assinaturas para a atividade no GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)". +To customize the types of updates you'd like to receive and where to send those updates, configure your notification settings. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)." -Para personalizar como você gostaria de receber atualizações de pull requests ou problemas específicos, é possível configurar suas preferências dentro do problema ou da pull request. Para obter mais informações, confira "[Como fazer a triagem de uma só notificação](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)". +To keep your subscriptions manageable, review your subscriptions and watched repositories and unsubscribe as needed. For more information, see "[Managing subscriptions for activity on GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)." -{% ifversion fpt or ghes or ghec %} Você pode personalizar e agendar notificações por push no aplicativo {% data variables.product.prodname_mobile %}. Para obter mais informações, confira "[Como configurar notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#managing-your-notification-settings-with-github-mobile)". +To customize how you'd like to receive updates for specific pull requests or issues, you can configure your preferences within the issue or pull request. For more information, see "[Triaging a single notification](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)." + +{% ifversion fpt or ghes or ghec %} +You can customize and schedule push notifications in the {% data variables.product.prodname_mobile %} app. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#managing-your-notification-settings-with-github-mobile)." {% endif %} -## Motivos para receber notificações +## Reasons for receiving notifications -Sua caixa de entrada está configurada com filtros padrão, que representam as razões mais comuns para que as pessoas precisem acompanhar suas notificações. Para obter mais informações sobre filtros de caixa de entrada, confira "[Como gerenciar notificações na sua caixa de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#default-notification-filters)". +Your inbox is configured with default filters, which represent the most common reasons that people need to follow-up on their notifications. For more information about inbox filters, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#default-notification-filters)." -Sua caixa de entrada mostra os `reasons` pelos quais você está recebendo notificações como um rótulo. +Your inbox shows the `reasons` you're receiving notifications as a label. -![Etiquetas de razões na caixa de entrada](/assets/images/help/notifications-v2/reasons-as-labels-in-inbox.png) +![Reasons labels in inbox](/assets/images/help/notifications-v2/reasons-as-labels-in-inbox.png) -Você pode filtrar sua caixa de entrada pelo motivo pelo qual está inscrito nas notificações. Por exemplo, para ver apenas as solicitações de pull em que alguém solicitou sua revisão, use o filtro de consulta `review-requested`. +You can filter your inbox by the reason you're subscribed to notifications. For example, to only see pull requests where someone requested your review, you can use the `review-requested` query filter. -![Filtrar notificações por revisar razão solicitada](/assets/images/help/notifications-v2/review-requested-reason.png) +![Filter notifications by review requested reason](/assets/images/help/notifications-v2/review-requested-reason.png) -Se você configurou as notificações para serem enviadas por e-mail e acredita que está recebendo notificações que não pertencem a você, considere a resolução de problemas com cabeçalhos de e-mail, que mostram o destinatário pretendido. Para obter mais informações, confira "[Como configurar notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)". +If you've configured notifications to be sent by email and believe you're receiving notifications that don't belong to you, consider troubleshooting with email headers, which show the intended recipient. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)." -## Fazendo a triagem de notificações da sua caixa de entrada +## Triaging notifications from your inbox -Para gerenciar suas notificações efetivamente, você pode fazer a triagem de sua caixa de entrada com opções para: -- Remova uma notificação da caixa de entrada com **Concluído**. Revise as notificações **concluídas** em um só lugar clicando em **Concluídas** na barra lateral ou usando a consulta `is:done`. -- Marcar uma notificação como lida ou não lida. -- **Salve** uma notificação para revisão posterior. As notificações **salvas** são sinalizadas na caixa de entrada. Revise as notificações **salvas** em um só lugar na barra lateral clicando em **Salvas** ou usando a consulta `is:saved`. -- Cancelar automaticamente esta notificação e atualizações futuras desta conversa. Cancelar inscrição também remove a notificação da sua caixa de entrada. Se você cancelar a inscrição de uma conversa e alguém menciona seu nome de usuário ou uma equipe para a qual você está recebendo atualizações, então você começará a receber notificações desta conversa novamente. +To effectively manage your notifications, you can triage your inbox with options to: +- Remove a notification from the inbox with **Done**. You can review **Done** notifications all in one place by clicking **Done** in the sidebar or by using the query `is:done`. +- Mark a notification as read or unread. +- **Save** a notification for later review. **Saved** notifications are flagged in your inbox. You can review **Saved** notifications all in one place in the sidebar by clicking **Saved** or by using the query `is:saved`. +- Automatically unsubscribe from this notification and future updates from this conversation. Unsubscribing also removes the notification from your inbox. If you unsubscribe from a conversation and someone mentions your username or a team you're on that you're receiving updates for, then you will start to receive notifications from this conversation again. -Em sua caixa de entrada, você também pode fazer triagem de várias notificações de uma só vez. Para obter mais informações, confira "[Como gerenciar notificações na sua caixa de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)". +From your inbox you can also triage multiple notifications at once. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)." -## Personalizando sua caixa de entrada de notificações +## Customizing your notifications inbox -Para se concentrar em um grupo de notificações na caixa de entrada no {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} ou no {% data variables.product.prodname_mobile %}{% endif %}, crie filtros personalizados. Por exemplo, você pode criar um filtro personalizado para um projeto de código aberto para o qual contribui e somente visualizar notificações para esse repositório em que você é mencionado. Para obter mais informações, confira "[Como gerenciar notificações na sua caixa de entrada](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)". Para obter mais exemplos de como fazer a triagem do fluxo de trabalho, confira "[Como personalizar um fluxo de trabalho para fazer a triagem das suas notificações](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)". +To focus on a group of notifications in your inbox on {% data variables.location.product_location %}{% ifversion fpt or ghes or ghec %} or {% data variables.product.prodname_mobile %}{% endif %}, you can create custom filters. For example, you can create a custom filter for an open source project you contribute to and only see notifications for that repository in which you are mentioned. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)." For more examples of how to customize your triaging workflow, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)." -## Política de retenção de notificações +## Notification retention policy -As notificações que não estão marcadas como **Salvas** são mantidas por cinco meses. As notificações marcadas como **Salvas** são mantidas por tempo indeterminado. Se sua notificação salva tiver mais de 5 meses e você não salvá-la, a notificação desaparecerá da sua caixa de entrada em um dia. +Notifications that are not marked as **Saved** are kept for 5 months. Notifications marked as **Saved** are kept indefinitely. If your saved notification is older than 5 months and you unsave it, the notification will disappear from your inbox within a day. -## Comentários e suporte +## Feedback and support -Se você tiver comentários ou solicitações de recursos para notificações, use uma discussão da [{% data variables.product.prodname_github_community %}](https://github.com/orgs/community/discussions/categories/general). +If you have feedback or feature requests for notifications, use a [{% data variables.product.prodname_github_community %} discussion](https://github.com/orgs/community/discussions/categories/general). diff --git a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md index f0ec8c75e9..ee9ed4f6aa 100644 --- a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md +++ b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md @@ -26,11 +26,11 @@ topics: ## Notification delivery options -You can receive notifications for activity on {% data variables.product.product_location %} in the following locations. +You can receive notifications for activity on {% data variables.location.product_location %} in the following locations. - - The notifications inbox in the {% data variables.product.product_location %} web interface{% ifversion fpt or ghes or ghec %} - - The notifications inbox on {% data variables.product.prodname_mobile %}, which syncs with the inbox on {% data variables.product.product_location %}{% endif %} - - An email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} and {% data variables.product.prodname_mobile %}{% endif %} + - The notifications inbox in the {% data variables.location.product_location %} web interface{% ifversion fpt or ghes or ghec %} + - The notifications inbox on {% data variables.product.prodname_mobile %}, which syncs with the inbox on {% data variables.location.product_location %}{% endif %} + - An email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.location.product_location %}{% ifversion fpt or ghes or ghec %} and {% data variables.product.prodname_mobile %}{% endif %} {% ifversion fpt or ghes or ghec %} {% data reusables.notifications-v2.notifications-inbox-required-setting %} For more information, see "[Choosing your notification settings](#choosing-your-notification-settings)." @@ -40,12 +40,12 @@ You can receive notifications for activity on {% data variables.product.product_ ### Benefits of the notifications inbox -The notifications inbox on {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} and {% data variables.product.prodname_mobile %}{% endif %} includes triaging options designed specifically for your {% data variables.product.prodname_dotcom %} notifications flow, including options to: +The notifications inbox on {% data variables.location.product_location %}{% ifversion fpt or ghes or ghec %} and {% data variables.product.prodname_mobile %}{% endif %} includes triaging options designed specifically for your {% data variables.product.prodname_dotcom %} notifications flow, including options to: - Triage multiple notifications at once. - Mark completed notifications as **Done** and remove them from your inbox. To view all of your notifications marked as **Done**, use the `is:done` query. - Save a notification to review later. Saved notifications are flagged in your inbox and kept indefinitely. To view all of your saved notifications, use the `is:saved` query. - Unsubscribe and remove a notification from your inbox. - - Preview the issue, pull request, or team discussion where the notification originates on {% data variables.product.product_location %} from within the notifications inbox. + - Preview the issue, pull request, or team discussion where the notification originates on {% data variables.location.product_location %} from within the notifications inbox. - See one of the latest reasons you're receiving a notification from your inbox with a `reasons` label. - Create custom filters to focus on different notifications when you want. - Group notifications in your inbox by repository or date to get a quick overview with less context switching @@ -85,7 +85,7 @@ Anytime you comment in a conversation or when someone @mentions your username, y {% else %} -For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_location %}{% ifversion ghes %} and {% data variables.product.prodname_mobile %}{% endif %}. For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)." +For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.location.product_location %}{% ifversion ghes %} and {% data variables.product.prodname_mobile %}{% endif %}. For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)." ![Screenshot of participating and watching notifications options](/assets/images/help/notifications-v2/participating-and-watching-options.png){% endif %} @@ -103,7 +103,7 @@ If you do not enable watching or participating notifications for web{% ifversion ## Customizing your email notifications -After enabling email notifications, {% data variables.product.product_location %} will send notifications to you as multipart emails that contain both HTML and plain text copies of the content. Email notification content includes any Markdown, @mentions, emojis, hash-links, and more, that appear in the original content on {% data variables.product.product_location %}. If you only want to see the text in the email, you can configure your email client to display the plain text copy only. +After enabling email notifications, {% data variables.location.product_location %} will send notifications to you as multipart emails that contain both HTML and plain text copies of the content. Email notification content includes any Markdown, @mentions, emojis, hash-links, and more, that appear in the original content on {% data variables.location.product_location %}. If you only want to see the text in the email, you can configure your email client to display the plain text copy only. {% data reusables.notifications.outbound_email_tip %} @@ -117,7 +117,7 @@ If you're using Gmail, you can click a button beside the notification email to v {% endif %} -Choose a default email address where you want to send updates for conversations you're participating in or watching. You can also specify which activity on {% data variables.product.product_location %} you want to receive updates for using your default email address. For example, choose whether you want updates to your default email from: +Choose a default email address where you want to send updates for conversations you're participating in or watching. You can also specify which activity on {% data variables.location.product_location %} you want to receive updates for using your default email address. For example, choose whether you want updates to your default email from: - Comments on issues and pull requests. - Pull request reviews. - Pull request pushes. @@ -131,11 +131,11 @@ You can also send notifications for a specific repository to an email address. F ## Filtering email notifications -Each email notification that {% data variables.product.product_location %} sends contains header information. The header information in every email is consistent, so you can use it in your email client to filter or forward all {% data variables.product.prodname_dotcom %} notifications, or certain types of {% data variables.product.prodname_dotcom %} notifications. +Each email notification that {% data variables.location.product_location %} sends contains header information. The header information in every email is consistent, so you can use it in your email client to filter or forward all {% data variables.product.prodname_dotcom %} notifications, or certain types of {% data variables.product.prodname_dotcom %} notifications. If you believe you're receiving notifications that don't belong to you, examine the `X-GitHub-Recipient` and `X-GitHub-Recipient-Address` headers. These headers show who the intended recipient is. Depending on your email setup, you may receive notifications intended for another user. -Email notifications from {% data variables.product.product_location %} contain the following header information: +Email notifications from {% data variables.location.product_location %} contain the following header information: | Header | Information | | --- | --- | diff --git a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md index 3b20224fa6..ba60987068 100644 --- a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md +++ b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md @@ -1,6 +1,6 @@ --- -title: Gerenciamento de notificações da sua caixa de entrada -intro: 'Use sua caixa de entrada para fazer triagem e sincronizar rapidamente as notificações no email{% ifversion fpt or ghes or ghec %} e no dispositivo móvel{% endif %}.' +title: Managing notifications from your inbox +intro: 'Use your inbox to quickly triage and sync your notifications across email{% ifversion fpt or ghes or ghec %} and mobile{% endif %}.' redirect_from: - /articles/marking-notifications-as-read - /articles/saving-notifications-for-later @@ -14,102 +14,98 @@ versions: topics: - Notifications shortTitle: Manage from your inbox -ms.openlocfilehash: 83aa9ce53f68636e299c3a83fe8d06dd189d5d6c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147060455' --- -## Sobre sua caixa de entrada -{% ifversion fpt or ghes or ghec %} {% data reusables.notifications-v2.notifications-inbox-required-setting %} Para obter mais informações, confira "[Configurar notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)". +## About your inbox + +{% ifversion fpt or ghes or ghec %} +{% data reusables.notifications-v2.notifications-inbox-required-setting %} For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)." {% endif %} -Para acessar a caixa de entrada de notificações, no canto superior direito de qualquer página, clique em {% octicon "bell" aria-label="The notifications bell" %}. +To access your notifications inbox, in the upper-right corner of any page, click {% octicon "bell" aria-label="The notifications bell" %}. - ![Notificação indicando mensagens não lidas](/assets/images/help/notifications/notifications_general_existence_indicator.png) + ![Notification indicating any unread message](/assets/images/help/notifications/notifications_general_existence_indicator.png) -Sua caixa de entrada mostra todas as notificações que você não assinou ou marcou como **Concluído.** Você pode personalizar sua caixa de entrada para se adequar melhor ao fluxo de trabalho usando filtros, exibindo todas ou apenas notificações não lidas e agrupando suas notificações para obter uma visão geral rápida. +Your inbox shows all of the notifications that you haven't unsubscribed to or marked as **Done.** You can customize your inbox to best suit your workflow using filters, viewing all or just unread notifications, and grouping your notifications to get a quick overview. - ![visualização da caixa de entrada](/assets/images/help/notifications-v2/inbox-view.png) + ![inbox view](/assets/images/help/notifications-v2/inbox-view.png) -Por padrão, sua caixa de entrada mostrará notificações lidas e não lidas. Para ver apenas notificações não lidas, clique em **Não ler** ou use a consulta `is:unread`. +By default, your inbox will show read and unread notifications. To only see unread notifications, click **Unread** or use the `is:unread` query. - ![visualização da caixa de entrada não lida](/assets/images/help/notifications-v2/unread-inbox-view.png) + ![unread inbox view](/assets/images/help/notifications-v2/unread-inbox-view.png) -## Opções de triagem +## Triaging options -Você tem várias opções para fazer triagem de notificações a partir de sua caixa de entrada. +You have several options for triaging notifications from your inbox. -| Opções de triagem | Descrição | +| Triaging option | Description | |-----------------|-------------| -| Salvar | Salva a sua notificação para revisão posterior. Para salvar uma notificação à direita da notificação, clique em {% octicon "bookmark" aria-label="The bookmark icon" %}.

As notificações salvas são mantidas por tempo indeterminado e podem ser exibidas com um clique em **Salvas** na barra lateral ou com a consulta `is:saved`. Se sua notificação salva tiver mais de 5 meses e tornar-se não salva, a notificação desaparecerá da sua caixa de entrada em um dia. | -| Concluído | Marca uma notificação como concluída e remove a notificação da sua caixa de entrada. Você pode ver todas as notificações concluídas clicando em **Concluído** na barra lateral ou com a consulta `is:done`. As notificações marcadas como **Concluídas** são salvas por cinco meses. -| Cancelar assinatura | Remove automaticamente a notificação da sua caixa de entrada e cancela a assinatura da conversa até que você seja @mentioned (mencionado), uma equipe em que você está seja@mentioned ou você seja solicitado a fazer a revisão. -| Ler | Marca uma notificação como lida. Para exibir apenas notificações de leitura na caixa de entrada, use a consulta `is:read`. Essa consulta não inclui notificações marcadas como **Concluídas**. -| Não lido | Marca uma notificação como não lida. Para exibir apenas notificações não lidas em sua caixa de entrada, use a consulta `is:unread`. | +| Save | Saves your notification for later review. To save a notification, to the right of the notification, click {% octicon "bookmark" aria-label="The bookmark icon" %}.

Saved notifications are kept indefinitely and can be viewed by clicking **Saved** in the sidebar or with the `is:saved` query. If your saved notification is older than 5 months and becomes unsaved, the notification will disappear from your inbox within a day. | +| Done | Marks a notification as completed and removes the notification from your inbox. You can see all completed notifications by clicking **Done** in the sidebar or with the `is:done` query. Notifications marked as **Done** are saved for 5 months. +| Unsubscribe | Automatically removes the notification from your inbox and unsubscribes you from the conversation until you are @mentioned, a team you're on is @mentioned, or you're requested for review. +| Read | Marks a notification as read. To only view read notifications in your inbox, use the `is:read` query. This query doesn't include notifications marked as **Done**. +| Unread | Marks notification as unread. To only view unread notifications in your inbox, use the `is:unread` query. | -Para ver os atalhos de teclado disponíveis, confira "[Atalhos de teclado](/github/getting-started-with-github/keyboard-shortcuts#notifications)". +To see the available keyboard shortcuts, see "[Keyboard Shortcuts](/github/getting-started-with-github/keyboard-shortcuts#notifications)." -Antes de escolher uma opção de triagem, primeiro você pode pré-visualizar os detalhes da sua notificação e investigar. Para obter mais informações, confira "[Como fazer a triagem de uma só notificação](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification)". +Before choosing a triage option, you can preview your notification's details first and investigate. For more information, see "[Triaging a single notification](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification)." -## Fazer triagem de várias notificações ao mesmo tempo +## Triaging multiple notifications at the same time -Para fazer a triagem de várias notificações ao mesmo tempo, selecione as notificações relevantes e use a lista suspensa {% octicon "kebab-horizontal" aria-label="The edit icon" %} para escolher uma opção de triagem. +To triage multiple notifications at once, select the relevant notifications and use the {% octicon "kebab-horizontal" aria-label="The edit icon" %} drop-down to choose a triage option. -![Menu suspenso com opções de triagem e notificações selecionadas](/assets/images/help/notifications-v2/triage-multiple-notifications-together.png) +![Drop-down menu with triage options and selected notifications](/assets/images/help/notifications-v2/triage-multiple-notifications-together.png) -## Filtros de notificação padrão +## Default notification filters -Por padrão, sua caixa de entrada tem filtros para quando você é atribuído, participando de um thread, solicitado a examinar uma solicitação de pull ou quando seu nome de usuário é @mentioned diretamente ou uma equipe da qual você é membro seja @mentioned. +By default, your inbox has filters for when you are assigned, participating in a thread, requested to review a pull request, or when your username is @mentioned directly or a team you're a member of is @mentioned. - ![Filtros personalizados padrão](/assets/images/help/notifications-v2/default-filters.png) + ![Default custom filters](/assets/images/help/notifications-v2/default-filters.png) -## Personalizando sua caixa de entrada com filtros personalizados +## Customizing your inbox with custom filters -Você pode adicionar até 15 dos seus próprios filtros personalizados. +You can add up to 15 of your own custom filters. {% data reusables.notifications.access_notifications %} -2. Para abrir as configurações de filtro, na barra lateral esquerda, ao lado de "Filtros", clique em {% octicon "gear" aria-label="The Gear icon" %}. +2. To open the filter settings, in the left sidebar, next to "Filters", click {% octicon "gear" aria-label="The Gear icon" %}. {% tip %} - **Dica:** você pode visualizar rapidamente os resultados da caixa de entrada de um filtro criando uma consulta no modo de exibição de caixa de entrada e clicando em **Salvar**, o que abre as configurações de filtro personalizadas. + **Tip:** You can quickly preview a filter's inbox results by creating a query in your inbox view and clicking **Save**, which opens the custom filter settings. {% endtip %} -3. Adicione um nome para seu filtro e uma consulta de filtro. Por exemplo, para ver apenas as notificações de um repositório específico, você pode criar um filtro usando a consulta `repo:octocat/open-source-project-name reason:participating`. Você também pode adicionar emojis com um teclado de emojis nativo. Para obter uma lista de consultas de pesquisa com suporte, confira "[Consultas com suporte para filtros personalizados](#supported-queries-for-custom-filters)". +3. Add a name for your filter and a filter query. For example, to only see notifications for a specific repository, you can create a filter using the query `repo:octocat/open-source-project-name reason:participating`. You can also add emojis with a native emoji keyboard. For a list of supported search queries, see "[Supported queries for custom filters](#supported-queries-for-custom-filters)." - ![Exemplo de filtro personalizado](/assets/images/help/notifications-v2/custom-filter-example.png) + ![Custom filter example](/assets/images/help/notifications-v2/custom-filter-example.png) -4. Clique em **Criar**. +4. Click **Create**. -## Limitações de filtro personalizadas +## Custom filter limitations -Filtros personalizados atualmente não suportam: - - Pesquisa de texto completo em sua caixa de entrada, incluindo busca de pull request ou títulos de problema. - - Distinção entre os filtros de consulta `is:issue`, `is:pr` e `is:pull-request`. Essas consultas retornarão problemas e pull requests. - - Criando mais de 15 filtros personalizados. - - Alterando os filtros padrão ou sua ordenação. - - [Exclusão](/github/searching-for-information-on-github/understanding-the-search-syntax#exclude-certain-results) de pesquisa usando `NOT` ou `-QUALIFIER`. +Custom filters do not currently support: + - Full text search in your inbox, including searching for pull request or issue titles. + - Distinguishing between the `is:issue`, `is:pr`, and `is:pull-request` query filters. These queries will return both issues and pull requests. + - Creating more than 15 custom filters. + - Changing the default filters or their order. + - Search [exclusion](/github/searching-for-information-on-github/understanding-the-search-syntax#exclude-certain-results) using `NOT` or `-QUALIFIER`. -## Consultas suportadas para filtros personalizados +## Supported queries for custom filters -Estes são os tipos de filtros que você pode usar: - - Filtrar por repositório com `repo:` - - Filtrar por tipo de discussão com `is:` - - Filtrar por motivo de notificação com `reason:`{% ifversion fpt or ghec %} - - Filtrar por autor de notificação com `author:` - - Filtrar por organização com `org:`{% endif %} +These are the types of filters that you can use: + - Filter by repository with `repo:` + - Filter by discussion type with `is:` + - Filter by notification reason with `reason:`{% ifversion fpt or ghec %} + - Filter by notification author with `author:` + - Filter by organization with `org:`{% endif %} -### Consultas `repo:` com suporte +### Supported `repo:` queries -Para adicionar um filtro `repo:`, você deve incluir o proprietário do repositório na consulta: `repo:owner/repository`. Um proprietário é a organização ou o usuário que possui o ativo de {% data variables.product.prodname_dotcom %} que aciona a notificação. Por exemplo, `repo:octo-org/octo-repo` mostrará notificações disparadas no repositório octo-repo dentro da organização octo-org. +To add a `repo:` filter, you must include the owner of the repository in the query: `repo:owner/repository`. An owner is the organization or the user who owns the {% data variables.product.prodname_dotcom %} asset that triggers the notification. For example, `repo:octo-org/octo-repo` will show notifications triggered in the octo-repo repository within the octo-org organization. -### Consultas `is:` com suporte +### Supported `is:` queries -Para filtrar notificações para atividades específicas no {% data variables.product.product_location %}, você pode usar a consulta `is`. Por exemplo, para ver apenas as atualizações de convite do repositório, use `is:repository-invitation`{% ifversion not ghae %} e para ver somente {% data variables.product.prodname_dependabot_alerts %}, use `is:repository-vulnerability-alert`{% endif %}. +To filter notifications for specific activity on {% data variables.location.product_location %}, you can use the `is` query. For example, to only see repository invitation updates, use `is:repository-invitation`{% ifversion not ghae %}, and to only see {% data variables.product.prodname_dependabot_alerts %}, use `is:repository-vulnerability-alert`{% endif %}. - `is:check-suite` - `is:commit` @@ -122,63 +118,64 @@ Para filtrar notificações para atividades específicas no {% data variables.pr - `is:team-discussion`{% ifversion fpt or ghec %} - `is:discussion`{% endif %} -Para obter informações de como reduzir notificações desnecessárias de {% data variables.product.prodname_dependabot_alerts %}, veja "[Como configurar notificações para o {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)". +For information about reducing noise from notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)." -Você também pode usar a consulta `is:` para descrever como a notificação passou pela triagem. +You can also use the `is:` query to describe how the notification was triaged. - `is:saved` - `is:done` - `is:unread` - `is:read` -### Consultas `reason:` com suporte +### Supported `reason:` queries -Para filtrar as notificações por que você recebeu uma atualização, você pode usar a consulta `reason:`. Por exemplo, para ver as notificações quando você (ou uma equipe em que você está) é solicitado a examinar uma solicitação de pull, use `reason:review-requested`. Para obter mais informações, confira "[Sobre as notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)". +To filter notifications by why you've received an update, you can use the `reason:` query. For example, to see notifications when you (or a team you're on) is requested to review a pull request, use `reason:review-requested`. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)." -| Consulta | Descrição | +| Query | Description | |-----------------|-------------| -| `reason:assign` | Quando houver uma atualização em um problema ou numa pull request que você tenha sido designado responsável. -| `reason:author` | Quando você abriu uma pull request ou um problema e houve uma atualização ou novo comentário. -| `reason:comment`| Quando você comentou em um problema, numa pull request ou numa discussão em equipe. -| `reason:participating` | Quando você tiver comentado em um problema, solicitação de pull ou discussão de equipe ou tiver sido @mentioned (mencionado). -| `reason:invitation` | Quando você for convidado para uma equipe, organização ou repositório. -| `reason:manual` | Ao clicar em **Assinar** em um problema ou solicitação de pull que você ainda não foi inscrito. -| `reason:mention` | Você foi diretamente @mentioned. -| `reason:review-requested` | Você ou uma equipe da qual é integrante é solicitado a revisar uma pull request. -| `reason:security-alert` | Quando um alerta de segurança é emitido para um repositório. -| `reason:state-change` | Quando o estado de uma pull request ou um problema é alterado. Por exemplo, um problema é fechado ou uma pull request é mesclada. -| `reason:team-mention` | Quando uma equipe da qual você é membro é @mentioned. -| `reason:ci-activity` | Quando um repositório tem uma atualização de CI, como um novo status de execução de fluxo de trabalho. +| `reason:assign` | When there's an update on an issue or pull request you've been assigned to. +| `reason:author` | When you opened a pull request or issue and there has been an update or new comment. +| `reason:comment`| When you commented on an issue, pull request, or team discussion. +| `reason:participating` | When you have commented on an issue, pull request, or team discussion or you have been @mentioned. +| `reason:invitation` | When you're invited to a team, organization, or repository. +| `reason:manual` | When you click **Subscribe** on an issue or pull request you weren't already subscribed to. +| `reason:mention` | You were directly @mentioned. +| `reason:review-requested` | You or a team you're on have been requested to review a pull request. +| `reason:security-alert` | When a security alert is issued for a repository. +| `reason:state-change` | When the state of a pull request or issue is changed. For example, an issue is closed or a pull request is merged. +| `reason:team-mention` | When a team you're a member of is @mentioned. +| `reason:ci-activity` | When a repository has a CI update, such as a new workflow run status. {% ifversion fpt or ghec %} -### Consultas `author:` com suporte +### Supported `author:` queries -Para filtrar notificações por usuário, você pode usar a consulta `author:`. Um autor é o autor original da corrente (problema, pull request, discussões gist, e assim por diante) referente ao qual você está sendo notificado. Por exemplo, para ver as notificações para threads criados pelo usuário Octocat, use `author:octocat`. +To filter notifications by user, you can use the `author:` query. An author is the original author of the thread (issue, pull request, gist, discussions, and so on) for which you are being notified. For example, to see notifications for threads created by the Octocat user, use `author:octocat`. -### Consultas `org:` com suporte +### Supported `org:` queries -Para filtrar notificações por organização, você pode usar a consulta `org`. A organização que você precisa especificar na consulta é a organização do repositório, para a qual você está sendo notificado em {% data variables.product.prodname_dotcom %}. Esta consulta é útil se você pertencer a várias organizações e desejar ver as notificações para uma organização específica. +To filter notifications by organization, you can use the `org` query. The organization you need to specify in the query is the organization of the repository for which you are being notified on {% data variables.product.prodname_dotcom %}. This query is useful if you belong to several organizations, and want to see notifications for a specific organization. -Por exemplo, para ver as notificações da organização octo-org, use `org:octo-org`. +For example, to see notifications from the octo-org organization, use `org:octo-org`. {% endif %} -## Filtros personalizados de {% data variables.product.prodname_dependabot %} +## {% data variables.product.prodname_dependabot %} custom filters -{% ifversion fpt or ghec or ghes > 3.2 %} Se você usar {% data variables.product.prodname_dependabot %} para manter suas dependências atualizadas, poderá usar e salvar esses filtros personalizados: -- `is:repository_vulnerability_alert` para mostrar notificações para {% data variables.product.prodname_dependabot_alerts %}. -- `reason:security_alert` para mostrar notificações para {% data variables.product.prodname_dependabot_alerts %} e solicitações de pull de atualização de segurança. -- `author:app/dependabot` para mostrar notificações geradas por {% data variables.product.prodname_dependabot %}. Isto inclui {% data variables.product.prodname_dependabot_alerts %}, pull requests para atualizações de segurança e pull requests para atualizações de versão. +{% ifversion fpt or ghec or ghes > 3.2 %} +If you use {% data variables.product.prodname_dependabot %} to keep your dependencies up-to-date, you can use and save these custom filters: +- `is:repository_vulnerability_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %}. +- `reason:security_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %} and security update pull requests. +- `author:app/dependabot` to show notifications generated by {% data variables.product.prodname_dependabot %}. This includes {% data variables.product.prodname_dependabot_alerts %}, security update pull requests, and version update pull requests. -Para obter mais informações sobre {% data variables.product.prodname_dependabot %}, confira "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)". +For more information about {% data variables.product.prodname_dependabot %}, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." {% endif %} {% ifversion ghes < 3.3 or ghae %} -Se você usa o {% data variables.product.prodname_dependabot %} para saber sobre dependências não seguras, use e salve estes filtros personalizados para ver as notificações do {% data variables.product.prodname_dependabot_alerts %}: +If you use {% data variables.product.prodname_dependabot %} to tell you about insecure dependencies, you can use and save these custom filters to show notifications for {% data variables.product.prodname_dependabot_alerts %}: - `is:repository_vulnerability_alert` - `reason:security_alert` -Para obter mais informações sobre {% data variables.product.prodname_dependabot %}, confira "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". +For more information about {% data variables.product.prodname_dependabot %}, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." {% endif %} diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md index c0511693a3..b7f02b36e0 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md @@ -14,7 +14,7 @@ shortTitle: Your profile README --- ## About your profile README -You can share information about yourself with the community on {% data variables.product.product_location %} by creating a profile README. {% data variables.product.prodname_dotcom %} shows your profile README at the top of your profile page. +You can share information about yourself with the community on {% data variables.location.product_location %} by creating a profile README. {% data variables.product.prodname_dotcom %} shows your profile README at the top of your profile page. You decide what information to include in your profile README, so you have full control over how you present yourself on {% data variables.product.prodname_dotcom %}. Here are some examples of information that visitors may find interesting, fun, or useful in your profile README. diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md index 850fdd4282..e8a2772e9f 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md @@ -59,7 +59,7 @@ You can change the name that is displayed on your profile. This name may also be {% ifversion fpt or ghec %} {% note %} -**Note:** If you're a member of an {% data variables.product.prodname_emu_enterprise %}, any changes to your profile name must be made through your identity provider instead of {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} +**Note:** If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, any changes to your profile name must be made through your identity provider instead of {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} {% endnote %} {% endif %} diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md index fa7327e5cf..e88e940a1c 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md @@ -20,7 +20,7 @@ If you publicize your private contributions, people without access to the privat {% note %} -**Note:** {% ifversion fpt or ghes or ghec %}On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, public contributions on your profile are visible {% ifversion fpt or ghec %}to anyone in the world who can access {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}only to other users of {% data variables.product.product_location%}{% endif %}.{% elsif ghae %}On {% data variables.product.prodname_ghe_managed %}, only other members of your enterprise can see the contributions on your profile.{% endif %} +**Note:** {% ifversion fpt or ghes or ghec %}On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, public contributions on your profile are visible {% ifversion fpt or ghec %}to anyone in the world who can access {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}only to other users of {% data variables.location.product_location%}{% endif %}.{% elsif ghae %}On {% data variables.product.prodname_ghe_managed %}, only other members of your enterprise can see the contributions on your profile.{% endif %} {% endnote %} diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md index 44cb56aba4..5581d21cd0 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md @@ -1,6 +1,6 @@ --- -title: Exibir contribuições no perfil -intro: 'Seu perfil do {% data variables.product.product_name %} mostra {% ifversion fpt or ghes or ghec %}os repositórios fixados, as Conquistas e{% endif %} um gráfico das contribuições no repositório no último ano.' +title: Viewing contributions on your profile +intro: 'Your {% data variables.product.product_name %} profile shows off {% ifversion fpt or ghes or ghec %}your pinned repositories, Achievements, and{% endif %} a graph of your repository contributions over the past year.' redirect_from: - /articles/viewing-contributions - /articles/viewing-contributions-on-your-profile-page @@ -15,89 +15,83 @@ versions: topics: - Profiles shortTitle: View contributions -ms.openlocfilehash: 81b2242e0c7a07d8941375d044cacc65ca8dd56d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147079397' --- -{% ifversion fpt or ghes or ghec %}O grafo de contribuições e as Conquistas mostram a atividade em repositórios públicos. {% endif %}Você pode optar por mostrar a atividade tanto de {% ifversion fpt or ghes or ghec %}repositórios públicos quanto {% endif %}de privados, com detalhes específicos da sua atividade em repositórios privados anônimos. Para obter mais informações, confira "[Como divulgar ou ocultar suas contribuições privadas no seu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)". +{% ifversion fpt or ghes or ghec %}Your contribution graph and Achievements show activity from public repositories. {% endif %}You can choose to show activity from {% ifversion fpt or ghes or ghec %}both public and {% endif %}private repositories, with specific details of your activity in private repositories anonymized. For more information, see "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)." {% note %} -**Observação:** os commits só serão exibidos no seu gráfico de contribuições se o endereço de email que você usou para criar os commits estiver conectado à sua conta do {% data variables.product.product_name %}. Para obter mais informações, confira "[Por que minhas contribuições não aparecem no meu perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)" +**Note:** Commits will only appear on your contributions graph if the email address you used to author the commits is connected to your account on {% data variables.product.product_name %}. For more information, see "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)" {% endnote %} -## O que conta como contribuição +## What counts as a contribution -Na sua página de perfil, determinadas ações contam como contribuições: +On your profile page, certain actions count as contributions: -- Como fazer commit no branch `gh-pages` ou no branch padrão de um repositório -- Abrir um problema -- Abrir uma discussão -- Responder a uma discussão -- Propor uma pull request -- Como enviar uma revisão de solicitação de pull{% ifversion ghes or ghae %} -- Como cocriar commits no branch `gh-pages` ou no branch padrão de um repositório{% endif %} +- Committing to a repository's default branch or `gh-pages` branch +- Opening an issue +- Opening a discussion +- Answering a discussion +- Proposing a pull request +- Submitting a pull request review{% ifversion ghes or ghae %} +- Co-authoring commits in a repository's default branch or `gh-pages` branch{% endif %} {% data reusables.pull_requests.pull_request_merges_and_contributions %} -## Repositórios populares +## Popular repositories -Esta seção exibe os repositórios com a maioria dos inspetores. {% ifversion fpt or ghes or ghec %} Depois que você [fixar repositórios no seu perfil](/articles/pinning-repositories-to-your-profile), esta seção será alterada para "Repositórios fixados".{% endif %} +This section displays your repositories with the most watchers. {% ifversion fpt or ghes or ghec %}Once you [pin repositories to your profile](/articles/pinning-repositories-to-your-profile), this section will change to "Pinned repositories."{% endif %} -![Repositórios populares](/assets/images/help/profile/profile_popular_repositories.png) +![Popular repositories](/assets/images/help/profile/profile_popular_repositories.png) {% ifversion fpt or ghes or ghec %} -## Repositórios fixos +## Pinned repositories -Esta seção exibe até seis repositórios públicos e pode incluir tanto repositórios pertencentes a você como aqueles com os quais você contribuiu. Para ver detalhes importantes com facilidade sobre os repositórios que você escolheu colocar em destaque, cada repositório desta seção inclui um resumo do trabalho que está sendo feito, o número de [estrelas](/articles/saving-repositories-with-stars/) que ele recebeu e a principal linguagem de programação usada nele. Para obter mais informações, confira "[Como fixar repositórios no seu perfil](/articles/pinning-repositories-to-your-profile)". +This section displays up to six public repositories and can include your repositories as well as repositories you've contributed to. To easily see important details about the repositories you've chosen to feature, each repository in this section includes a summary of the work being done, the number of [stars](/articles/saving-repositories-with-stars/) the repository has received, and the main programming language used in the repository. For more information, see "[Pinning repositories to your profile](/articles/pinning-repositories-to-your-profile)." -![Repositórios fixos](/assets/images/help/profile/profile_pinned_repositories.png) +![Pinned repositories](/assets/images/help/profile/profile_pinned_repositories.png) {% endif %} -## Calendário de contribuições +## Contributions calendar -O calendário de contribuições mostra sua atividade de contribuição. +Your contributions calendar shows your contribution activity. -### Exibir contribuições de horários específicos +### Viewing contributions from specific times -- Clique no quadrado de um dia para mostrar as contribuições feitas durante esse período de 24 horas. -- Pressione *SHIFT* e clique no quadrado de outro dia para mostrar as contribuições feitas durante esse intervalo de tempo. +- Click on a day's square to show the contributions made during that 24-hour period. +- Press *Shift* and click on another day's square to show contributions made during that time span. {% note %} -**Observação:** só é possível selecionar um intervalo de até um mês no calendário de contribuições. Se você selecionar um período maior, será exibido apenas um mês de contribuições. +**Note:** You can select up to a one-month range on your contributions calendar. If you select a larger time span, we will only display one month of contributions. {% endnote %} -![Gráfico de contribuição](/assets/images/help/profile/contributions_graph.png) +![Your contributions graph](/assets/images/help/profile/contributions_graph.png) -### Como são calculados os horários de evento de contribuição +### How contribution event times are calculated -Os registros de data e hora são calculados de forma diferente para commits e pull requests: -- Os **commits** usam as informações de fuso horário do carimbo de data/hora do commit. Para obter mais informações, confira "[Solução de problemas de commits na sua linha do tempo](/articles/troubleshooting-commits-on-your-timeline)". -- As **solicitações de pull** e os **problemas** em aberto no {% data variables.product.product_name %} usam o fuso horário do navegador. Aqueles abertos por meio da API usam o carimbo de data/hora ou o fuso horário [especificado na chamada à API](https://developer.github.com/changes/2014-03-04-timezone-handling-changes). +Timestamps are calculated differently for commits and pull requests: +- **Commits** use the time zone information in the commit timestamp. For more information, see "[Troubleshooting commits on your timeline](/articles/troubleshooting-commits-on-your-timeline)." +- **Pull requests** and **issues** opened on {% data variables.product.product_name %} use your browser's time zone. Those opened via the API use the timestamp or time zone [specified in the API call](https://developer.github.com/changes/2014-03-04-timezone-handling-changes). -## Visão geral de atividade +## Activity overview -{% data reusables.profile.activity-overview-summary %} Para obter mais informações, confira "[Como mostrar uma visão geral da sua atividade no seu perfil](/articles/showing-an-overview-of-your-activity-on-your-profile)". +{% data reusables.profile.activity-overview-summary %} For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)." -![Seção Visão geral de atividade no perfil](/assets/images/help/profile/activity-overview-section.png) +![Activity overview section on profile](/assets/images/help/profile/activity-overview-section.png) -As organizações retratadas na visão geral da atividade são priorizadas de acordo com a forma como você está ativo na organização. Se você @mention uma organização na biografia do seu perfil e for membro dela, essa organização será priorizada na visão geral da atividade. Para obter mais informações, confira "[Como mencionar pessoas e equipes](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)" ou "[Como adicionar uma biografia ao seu perfil](/articles/adding-a-bio-to-your-profile/)". +The organizations featured in the activity overview are prioritized according to how active you are in the organization. If you @mention an organization in your profile bio, and you’re an organization member, then that organization is prioritized first in the activity overview. For more information, see "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)" or "[Adding a bio to your profile](/articles/adding-a-bio-to-your-profile/)." -## Atividade de contribuição +## Contribution activity -A seção de atividade de contribuição contém uma linha do tempo detalhada do seu trabalho, incluindo commits feitos exclusivamente por você ou em coautoria, solicitações de pull que você propôs e problemas que você abriu. Você pode ver suas contribuições ao longo do tempo clicando em **Mostrar mais atividade** na parte inferior da atividade de contribuição ou clicando no ano de interesse no lado direito da página. Momentos importantes, como a data em que você ingressou na organização, propôs sua primeira pull request ou abriu um problema relevante, são realçados na atividade de contribuição. Se você não conseguir ver determinados eventos na sua linha do tempo, verifique se ainda tem acesso à organização ou ao repositório em que o evento aconteceu +The contribution activity section includes a detailed timeline of your work, including commits you've made or co-authored, pull requests you've proposed, and issues you've opened. You can see your contributions over time by either clicking **Show more activity** at the bottom of your contribution activity or by clicking the year you're interested in viewing on the right side of the page. Important moments, like the date you joined an organization, proposed your first pull request, or opened a high-profile issue, are highlighted in your contribution activity. If you can't see certain events in your timeline, check to make sure you still have access to the organization or repository where the event happened. -![Filtro de hora de atividade de contribuição](/assets/images/help/profile/contributions_activity_time_filter.png) +![Contribution activity time filter](/assets/images/help/profile/contributions_activity_time_filter.png) -## Como ver as contribuições do {% data variables.product.prodname_enterprise %} no {% data variables.product.prodname_dotcom_the_website %} +## Viewing contributions from {% data variables.product.prodname_enterprise %} on {% data variables.product.prodname_dotcom_the_website %} -Se você usar o {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} ou o {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} e o proprietário da sua empresa habilitar as {% data variables.product.prodname_unified_contributions %}, você poderá enviar contribuições corporativas por meio do seu perfil do {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, confira "[Como enviar contribuições corporativas para o seu perfil do {% data variables.product.prodname_dotcom_the_website %}](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)". +If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and your enterprise owner enables {% data variables.enterprise.prodname_unified_contributions %}, you can send enterprise contribution counts from to your {% data variables.product.prodname_dotcom_the_website %} profile. For more information, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)." diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md index 8d2f214b4b..3e24053ec8 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md @@ -1,6 +1,6 @@ --- -title: Por que minhas contribuições não aparecem no meu perfil? -intro: Entenda os motivos comuns que as contribuições podem não ter no seu gráfico de contribuição. +title: Why are my contributions not showing up on my profile? +intro: Learn common reasons that contributions may be missing from your contributions graph. redirect_from: - /articles/why-are-my-contributions-not-showing-up-on-my-profile - /github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile @@ -14,54 +14,49 @@ versions: topics: - Profiles shortTitle: Missing contributions -ms.openlocfilehash: c1f4c9481a5e3ac9328b353ced826c982e1160e7 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147079394' --- -## Sobre o seu gráfico de contribuição -Seu gráfico de contribuições de perfil é um registro de contribuições que você fez para repositórios {% ifversion ghae %}pertencentes a{% else %}em{% endif %} {% data variables.product.product_location %}. As contribuições recebem registros de data e hora de acordo com o UTC (Coordinated Universal Time, Horário universal coordenado), e não com o fuso horário local. As contribuições só serão contabilizadas se atenderem a determinados critérios. Em alguns casos, pode ser necessário recriar o gráfico para que as contribuições sejam exibidas. +## About your contribution graph -Se você faz parte de uma organização que usa o logon único SAML (SSO), você não poderá ver a atividade de contribuição da organização em seu perfil se não tiver uma sessão SSO ativa. As pessoas que visualizarem o seu perfil de fora da sua organização verão a atividade de contribuição anônima de sua atividade de contribuição para sua organização. +Your profile contributions graph is a record of contributions you've made to repositories {% ifversion ghae %}owned by{% else %}on{% endif %} {% data variables.location.product_location %}. Contributions are timestamped according to Coordinated Universal Time (UTC) rather than your local time zone. Contributions are only counted if they meet certain criteria. In some cases, we may need to rebuild your graph in order for contributions to appear. -## Contribuições que são contabilizadas +If you are part of an organization that uses SAML single sign-on (SSO), you won’t be able to see contribution activity from the organization on your profile if you do not have an active SSO session. People viewing your profile from outside your organization will see anonymized contribution activity of your contribution activity for your organization. -### Problemas, pull requests e discussões +## Contributions that are counted -Os problemas, pull requests e discussões aparecerão no gráfico de contribuição se estiverem abertos em um repositório autônomo, não em uma bifurcação. +### Issues, pull requests and discussions -### Confirmações -Os commits serão exibidos no seu grafo de contribuições se eles atenderem a **todas** as seguintes condições: -- O endereço de e-mail usado para os commits está associado à sua conta no {% data variables.product.product_location %}. -- Os commits foram criados em um repositório autônomo, e não em uma bifurcação. -- Os commits foram criados: - - No branch-padrão do repositório - - No branch `gh-pages` (para repositórios com sites de projeto) +Issues, pull requests and discussions will appear on your contribution graph if they were opened in a standalone repository, not a fork. -Para obter mais informações sobre sites de projeto, confira "[Sobre o {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)". +### Commits +Commits will appear on your contributions graph if they meet **all** of the following conditions: +- The email address used for the commits is associated with your account on {% data variables.location.product_location %}. +- The commits were made in a standalone repository, not a fork. +- The commits were made: + - In the repository's default branch + - In the `gh-pages` branch (for repositories with project sites) -**Pelo menos, uma** das seguintes condições precisa ser verdadeira: -- Você é um colaborador no repositório ou um integrante da organização que possui o repositório. -- Você bifurcou o repositório. -- Você abriu uma pull request ou um problema no repositório. -- Você marcou o repositório como favorito. +For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." -## Motivos comuns para as contribuições não serem contabilizadas +In addition, **at least one** of the following must be true: +- You are a collaborator on the repository or are a member of the organization that owns the repository. +- You have forked the repository. +- You have opened a pull request or issue in the repository. +- You have starred the repository. + +## Common reasons that contributions are not counted {% data reusables.pull_requests.pull_request_merges_and_contributions %} -### O commit foi criado menos de 24 horas atrás +### Commit was made less than 24 hours ago -Depois de fazer um commit que atenda aos requisitos para ser contabilizado como contribuição, talvez você precise aguardar até 24 horas para que a contribuição seja exibida no gráfico de contribuições. +After making a commit that meets the requirements to count as a contribution, you may need to wait for up to 24 hours to see the contribution appear on your contributions graph. -### Seu e-mail de confirmação do Git local não está conectado à sua conta +### Your local Git commit email isn't connected to your account -Os commits precisam ser feitos com um endereço de email que esteja conectado à sua conta do {% data variables.product.product_location %}{% ifversion fpt or ghec %} ou ao endereço de email `noreply` fornecido pelo {% data variables.product.prodname_dotcom %} a você nas configurações de email,{% endif %} a fim de serem exibidos no seu grafo de contribuições.{% ifversion fpt or ghec %} Para obter mais informações sobre os endereços de email `noreply`, confira "[Como definir seu endereço de email de commit](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#about-commit-email-addresses)".{% endif %} +Commits must be made with an email address that is connected to your account on {% data variables.location.product_location %}{% ifversion fpt or ghec %}, or the {% data variables.product.prodname_dotcom %}-provided `noreply` email address provided to you in your email settings,{% endif %} in order to appear on your contributions graph.{% ifversion fpt or ghec %} For more information about `noreply` email addresses, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#about-commit-email-addresses)."{% endif %} -Verifique o endereço de email usado para um commit adicionando `.patch` ao final de uma URL de commit, por exemplo, https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch: +You can check the email address used for a commit by adding `.patch` to the end of a commit URL, e.g. https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch: ``` From 67c0afc1da354d8571f51b6f0af8f2794117fd10 Mon Sep 17 00:00:00 2001 @@ -70,37 +65,37 @@ Date: Sun, 27 Apr 2014 15:36:39 +0530 Subject: [PATCH] updated index for better welcome message ``` -O endereço de email do campo `From:` é o endereço definido nas [definições de configuração do Git local](/articles/set-up-git). Neste exemplo, o endereço de email usado para o commit é `octocat@nowhere.com`. +The email address in the `From:` field is the address that was set in the [local git config settings](/articles/set-up-git). In this example, the email address used for the commit is `octocat@nowhere.com`. -Se o endereço de e-mail usado para o commit não estiver conectado à sua conta em {% data variables.product.product_location %}, {% ifversion ghae %}altere o endereço de e-mail usado para criar commits no Git. Para obter mais informações, confira "[Como configurar seu endereço de email de commit](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)".{% else %}você precisa [adicionar o endereço de email](/articles/adding-an-email-address-to-your-github-account) à sua conta do {% data variables.product.product_location %}. Seu gráfico de contribuições será reconstruído automaticamente quando você adicionar o novo endereço.{% endif %} +If the email address used for the commit is not connected to your account on {% data variables.location.product_location %}, {% ifversion ghae %}change the email address used to author commits in Git. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %}you must [add the email address](/articles/adding-an-email-address-to-your-github-account) to your account on {% data variables.location.product_location %}. Your contributions graph will be rebuilt automatically when you add the new address.{% endif %} {% warning %} -**Aviso**: endereços de email genéricos, como `jane@computer.local`, não podem ser adicionados às contas do {% data variables.product.prodname_dotcom %}. Se você usar esse e-mail para os commits, eles não serão vinculados ao seu perfil do {% data variables.product.prodname_dotcom %} e não serão exibidos no gráfico de contribuições. +**Warning**: Generic email addresses, such as `jane@computer.local`, cannot be added to {% data variables.product.prodname_dotcom %} accounts. If you use such an email for your commits, the commits will not be linked to your {% data variables.product.prodname_dotcom %} profile and will not show up in your contribution graph. {% endwarning %} -### O commit não foi feito no branch padrão ou `gh-pages` +### Commit was not made in the default or `gh-pages` branch -Os commits só serão considerados se forem feitos no branch padrão ou no branch `gh-pages` (para repositórios com sites de projeto). Para obter mais informações, confira "[Sobre o {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)". +Commits are only counted if they are made in the default branch or the `gh-pages` branch (for repositories with project sites). For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." -Se os commits estiverem em um branch não padrão ou que não sejam o `gh-pages` e você quiser que eles sejam considerados como contribuições, siga um destes procedimentos: -- [Abra uma solicitação de pull](/articles/creating-a-pull-request) para que as alterações sejam mescladas no branch padrão ou no branch `gh-pages`. -- [Altere o branch padrão](/github/administering-a-repository/changing-the-default-branch) do repositório. +If your commits are in a non-default or non-`gh-pages` branch and you'd like them to count toward your contributions, you will need to do one of the following: +- [Open a pull request](/articles/creating-a-pull-request) to have your changes merged into the default branch or the `gh-pages` branch. +- [Change the default branch](/github/administering-a-repository/changing-the-default-branch) of the repository. {% warning %} -**Aviso**: a alteração do branch padrão do repositório vai alterá-lo para todos os colaboradores do repositório. Faça isso apenas se quiser que o novo branch se torne a base de todos os futuros commits e pull requests a serem criados. +**Warning**: Changing the default branch of the repository will change it for all repository collaborators. Only do this if you want the new branch to become the base against which all future pull requests and commits will be made. {% endwarning %} -### O commit foi criado em uma bifurcação +### Commit was made in a fork -Os commits criados em uma bifurcação não são contabilizados para suas contribuições. Para isso, é preciso que você siga estes procedimentos: -- [Abra uma solicitação de pull](/articles/creating-a-pull-request) para que as alterações sejam mescladas no repositório pai. -- Para separar a bifurcação e transformá-la em um repositório autônomo no {% data variables.product.product_location %}, entre em contato com o {% data variables.contact.contact_support %}. Se a bifurcação tiver bifurcações próprias, informe o {% data variables.contact.contact_support %} se as bifurcações devem mover-se com o repositório para uma nova rede ou se devem permanecer na rede atual. Para obter mais informações, confira "[Sobre os forks](/articles/about-forks/)". +Commits made in a fork will not count toward your contributions. To make them count, you must do one of the following: +- [Open a pull request](/articles/creating-a-pull-request) to have your changes merged into the parent repository. +- To detach the fork and turn it into a standalone repository on {% data variables.location.product_location %}, contact {% data variables.contact.contact_support %}. If the fork has forks of its own, let {% data variables.contact.contact_support %} know if the forks should move with your repository into a new network or remain in the current network. For more information, see "[About forks](/articles/about-forks/)." -## Leitura adicional +## Further reading -- "[Como publicar ou ocultar contribuições privadas no seu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" -- "[Como ver as contribuições na página do seu perfil](/articles/viewing-contributions-on-your-profile-page)" +- "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" +- "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)" diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md index 6c35133ec7..63b2860091 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md @@ -1,6 +1,6 @@ --- title: Setting up and managing your personal account on GitHub -intro: You can manage settings for your personal account on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}, including email preferences, access to personal repositories, and organization memberships. You can also manage the account itself. +intro: You can manage settings for your personal account on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}, including email preferences, access to personal repositories, and organization memberships. You can also manage the account itself. shortTitle: Personal accounts redirect_from: - /categories/setting-up-and-managing-your-github-user-account diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md index 8a8d6ef9a6..cd599dfdc0 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md @@ -25,7 +25,7 @@ Repositories owned by an organization can grant more granular access. For more i {% ifversion fpt or ghec %} -If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you can only invite other members of your enterprise to collaborate with you. {% data reusables.enterprise-accounts.emu-more-info-account %} +If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you can only invite other members of your enterprise to collaborate with you. {% data reusables.enterprise-accounts.emu-more-info-account %} {% note %} diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md index 9da0f39d0c..0d8d4fd6b1 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md @@ -1,6 +1,6 @@ --- -title: Adicionar endereço de e-mail à sua conta do GitHub -intro: 'O {% data variables.product.product_name %} permite adicionar quantos endereços de e-mail você desejar à sua conta. Se você definir um endereço de e-mail na configuração do seu Git local, será necessário adicioná-lo às definições da sua conta de modo a conectar os commits à conta. Para obter mais informações o endereço de email e os commits, confira "[Como definir seu endereço de email de commit](/articles/setting-your-commit-email-address/)".' +title: Adding an email address to your GitHub account +intro: '{% data variables.product.product_name %} allows you to add as many email addresses to your account as you like. If you set an email address in your local Git configuration, you will need to add it to your account settings in order to connect your commits to your account. For more information about your email address and commits, see "[Setting your commit email address](/articles/setting-your-commit-email-address/)."' redirect_from: - /articles/adding-an-email-address-to-your-github-account - /github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account @@ -14,27 +14,24 @@ topics: - Accounts - Notifications shortTitle: Add an email address -ms.openlocfilehash: 082326d96da4b36d1f29830491223ce9b649a15d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145164556' --- {% ifversion fpt or ghec %} {% note %} -**Observações**: +**Notes**: - {% data reusables.user-settings.no-verification-disposable-emails %} - - Se você for integrante de um {% data variables.product.prodname_emu_enterprise %}, você não poderá fazer alterações no seu endereço de e-mail em {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} + - If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you cannot make changes to your email address on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} {% endnote %} {% endif %} -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.emails %} {% data reusables.user-settings.add_and_verify_email %} {% data reusables.user-settings.select_primary_email %} +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.emails %} +{% data reusables.user-settings.add_and_verify_email %} +{% data reusables.user-settings.select_primary_email %} -## Leitura adicional +## Further reading -- "[Como gerenciar as preferências de email](/articles/managing-email-preferences/)" +- "[Managing email preferences](/articles/managing-email-preferences/)" diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md index 584c2f2f70..a45d2f7f77 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md @@ -1,6 +1,6 @@ --- -title: Gerenciar preferências de e-mail -intro: 'Você pode adicionar ou alterar os endereços de e-mail associados à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Também é possível gerenciar os e-mails que você recebe do {% data variables.product.product_name %}.' +title: Managing email preferences +intro: 'You can add or change the email addresses associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. You can also manage emails you receive from {% data variables.product.product_name %}.' redirect_from: - /categories/managing-email-preferences - /articles/managing-email-preferences @@ -24,11 +24,5 @@ children: - /types-of-emails-github-sends - /managing-marketing-emails-from-github shortTitle: Manage email preferences -ms.openlocfilehash: 8295d9884f7b2a9bfdef329f693c6492db636a61 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145164580' --- diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md index f3aa105107..d8d8d78c24 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md @@ -1,6 +1,6 @@ --- -title: Lembrar o nome de usuário ou e-mail do GitHub -intro: 'Faz tempo que você não faz login no {% data variables.product.product_location %}? Se sim, bem-vindo de volta! Se você não lembrar do nome de usuário para sua conta pessoal em {% data variables.product.product_name %}, siga estas etapas para recuperá-lo.' +title: Remembering your GitHub username or email +intro: 'Are you signing in to {% data variables.location.product_location %} for the first time in a while? If so, welcome back! If you can''t remember the username for your personal account on {% data variables.product.product_name %}, you can try these methods for remembering it.' redirect_from: - /articles/oh-noes-i-ve-forgotten-my-username-email - /articles/oh-noes-i-ve-forgotten-my-username-or-email @@ -16,66 +16,61 @@ topics: - Accounts - Notifications shortTitle: Find your username or email -ms.openlocfilehash: e65ba973a5ca7865aa642ce5d64f8efa0a996742 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145164643' --- {% mac %} -## Usuários do {% data variables.product.prodname_desktop %} +## {% data variables.product.prodname_desktop %} users -1. No menu **GitHub Desktop**, clique em **Preferências**. -2. Na janela Preferences (Preferências), faça o seguinte: - - Para ver o nome de usuário do {% data variables.product.product_name %}, clique em **Contas**. - - Para ver seu email do Git, clique em **Git**. Observe que esse email não tem a garantia de ser [seu email principal do {% data variables.product.product_name %}](/articles/changing-your-primary-email-address). +1. In the **GitHub Desktop** menu, click **Preferences**. +2. In the Preferences window, verify the following: + - To view your {% data variables.product.product_name %} username, click **Accounts**. + - To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address). {% endmac %} {% windows %} -## Usuários do {% data variables.product.prodname_desktop %} +## {% data variables.product.prodname_desktop %} users -1. No menu **Arquivo**, clique em **Opções**. -2. Na janela Options (Opções), faça o seguinte: - - Para ver o nome de usuário do {% data variables.product.product_name %}, clique em **Contas**. - - Para ver seu email do Git, clique em **Git**. Observe que esse email não tem a garantia de ser [seu email principal do {% data variables.product.product_name %}](/articles/changing-your-primary-email-address). +1. In the **File** menu, click **Options**. +2. In the Options window, verify the following: + - To view your {% data variables.product.product_name %} username, click **Accounts**. + - To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address). {% endwindows %} -## Como localizar seu nome de usuário na configuração de `user.name` +## Finding your username in your `user.name` configuration -Durante a configuração, você pode ter [definido seu nome de usuário no Git](/github/getting-started-with-github/setting-your-username-in-git). Em caso afirmativo, você poderá revisar o valor dessa configuração: +During set up, you may have [set your username in Git](/github/getting-started-with-github/setting-your-username-in-git). If so, you can review the value of this configuration setting: ```shell $ git config user.name # View the setting -YOUR_USERNAME +YOUR_USERNAME ``` -## Encontrar o nome de usuário na URL de repositórios remote +## Finding your username in the URL of remote repositories -Se você tiver cópias locais de repositórios pessoais criados ou bifurcados, poderá consultar a URL do repositório remote. +If you have any local copies of personal repositories you have created or forked, you can check the URL of the remote repository. {% tip %} -**Dica**: esse método só funcionará se você tiver um repositório original ou um fork próprio do repositório de outra pessoa. Se você clonar o repositório de outra pessoa, o nome de usuário da pessoa será exibido, não o seu. De forma similar, os repositórios da organização exibirão o nome da organização, não um usuário específico na URL remoto. +**Tip**: This method only works if you have an original repository or your own fork of someone else's repository. If you clone someone else's repository, their username will show instead of yours. Similarly, organization repositories will show the name of the organization instead of a particular user in the remote URL. {% endtip %} ```shell -$ cd YOUR_REPOSITORY +$ cd YOUR_REPOSITORY # Change directories to the initialized Git repository $ git remote -v -origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (fetch) -origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (push) +origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (fetch) +origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (push) ``` -Seu nome de usuário é o que vem imediatamente após o `https://{% data variables.command_line.backticks %}/`. +Your user name is what immediately follows the `https://{% data variables.command_line.backticks %}/`. {% ifversion fpt or ghec %} -## Leitura adicional +## Further reading -- "[Como verificar seu endereço de email](/articles/verifying-your-email-address)" {% endif %} +- "[Verifying your email address](/articles/verifying-your-email-address)" +{% endif %} diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md index 8adec77a0b..660ceca3bd 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md @@ -1,6 +1,6 @@ --- -title: Configurar o endereço de e-mail do commit -intro: 'Você pode definir o endereço de email usado para criar commits no {% data variables.product.product_location %} e no computador.' +title: Setting your commit email address +intro: 'You can set the email address that is used to author commits on {% data variables.location.product_location %} and on your computer.' redirect_from: - /articles/keeping-your-email-address-private - /articles/setting-your-commit-email-address-on-github @@ -22,63 +22,61 @@ topics: - Accounts - Notifications shortTitle: Set commit email address -ms.openlocfilehash: 76b0af2a1afa776281434c36cf33fa0e082c2c56 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '146338946' --- -## Sobre os endereços de e-mail do commit +## About commit email addresses -{% data variables.product.prodname_dotcom %} utiliza seu endereço de e-mail de commit para associar commits à sua conta em {% data variables.product.product_location %}. Você pode escolher o endereço de e-mail que será associado aos commits cujo push é feito usando a linha de comando e às operações do Git baseadas na web executadas. +{% data variables.product.prodname_dotcom %} uses your commit email address to associate commits with your account on {% data variables.location.product_location %}. You can choose the email address that will be associated with the commits you push from the command line as well as web-based Git operations you make. -Para operações com base na web do Git, você pode definir seu endereço de e-mail de commit em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Para commits cujo push é feito usando a linha de comando, você pode configurar o endereço de e-mail do commmit no Git. +For web-based Git operations, you can set your commit email address on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For commits you push from the command line, you can set your commit email address in Git. -{% ifversion fpt or ghec %} Todos os commits feitos antes da alteração do endereço de email de commit ainda estão associadas ao seu endereço de email anterior.{% else %}Depois de alterar o endereço de email de commit no {% data variables.product.product_name %}, por padrão, o novo endereço de email ficará visível em todas as suas futuras operações do Git baseadas na Web. Os commits feitos antes da alteração do endereço de e-mail do commit continuarão associados ao endereço de e-mail anterior.{% endif %} +{% ifversion fpt or ghec %}Any commits you made prior to changing your commit email address are still associated with your previous email address.{% else %}After changing your commit email address on {% data variables.product.product_name %}, the new email address will be visible in all of your future web-based Git operations by default. Any commits you made prior to changing your commit email address are still associated with your previous email address.{% endif %} {% ifversion fpt or ghec %} {% note %} -**Observação**: {% data reusables.user-settings.no-verification-disposable-emails %} +**Note**: {% data reusables.user-settings.no-verification-disposable-emails %} {% endnote %} {% endif %} -{% ifversion fpt or ghec %}Caso deseje manter seu endereço de email pessoal privado, use um endereço de email `noreply` do {% data variables.product.product_name %} como seu endereço de email de commit. Para usar seu endereço de email `noreply` para os commits enviados por push na linha de comando, use esse endereço de email ao definir seu endereço de email de commit no Git. Para usar seu endereço `noreply` para operações do Git baseadas na Web, defina seu endereço de email de commit no GitHub e escolha **manter meu endereço de email privado**. +{% ifversion fpt or ghec %}If you'd like to keep your personal email address private, you can use a `noreply` email address from {% data variables.product.product_name %} as your commit email address. To use your `noreply` email address for commits you push from the command line, use that email address when you set your commit email address in Git. To use your `noreply` address for web-based Git operations, set your commit email address on GitHub and choose to **Keep my email address private**. -Você também pode optar por bloquear os commits cujo push é feito usando a linha de comando que expõem seu endereço de e-mail pessoal. Para obter mais informações, confira "[Como bloquear pushes da linha de comando que expõem seu email pessoal](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)".{% endif %} +You can also choose to block commits you push from the command line that expose your personal email address. For more information, see "[Blocking command line pushes that expose your personal email](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)."{% endif %} -Para garantir que os commits sejam atribuídos a você e apareçam no seu grafo de contribuições, use um endereço de email conectado à sua conta do {% data variables.product.product_location %}{% ifversion fpt or ghec %} ou o endereço de email `noreply` fornecido para você nas configurações de email{% endif %}. {% ifversion not ghae %}Para obter mais informações, confira "[Como adicionar um endereço de email à sua conta do {% data variables.product.prodname_dotcom %}](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)".{% endif %} +To ensure that commits are attributed to you and appear in your contributions graph, use an email address that is connected to your account on {% data variables.location.product_location %}{% ifversion fpt or ghec %}, or the `noreply` email address provided to you in your email settings{% endif %}. {% ifversion not ghae %}For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)."{% endif %} {% ifversion fpt or ghec %} {% note %} -**Observação:** se você criou sua conta no {% data variables.product.product_location %} _após_ 18 de julho de 2017, seu endereço de email `noreply` para o {% data variables.product.product_name %} é um número de ID de sete dígitos e seu nome de usuário está no formato ID+username@users.noreply.github.com. Se você criou sua conta no {% data variables.product.product_location %} _antes_ de 18 de julho de 2017, seu endereço de email `noreply` do {% data variables.product.product_name %} é username@users.noreply.github.com. Você pode obter um endereço de email `noreply` baseado em ID do {% data variables.product.product_name %} selecionando (ou desmarcando e selecionando de novo) **Manter meu endereço de email privado** nas configurações de email. +**Note:** If you created your account on {% data variables.location.product_location %} _after_ July 18, 2017, your `noreply` email address for {% data variables.product.product_name %} is a seven-digit ID number and your username in the form of ID+USERNAME@users.noreply.github.com. If you created your account on {% data variables.location.product_location %} _prior to_ July 18, 2017, your `noreply` email address from {% data variables.product.product_name %} is USERNAME@users.noreply.github.com. You can get an ID-based `noreply` email address for {% data variables.product.product_name %} by selecting (or deselecting and reselecting) **Keep my email address private** in your email settings. {% endnote %} -Se você usar seu endereço de email `noreply` do {% data variables.product.product_name %} para fazer commits e [alterar seu nome de usuário](/articles/changing-your-github-username), esses commits não serão associados à sua conta do {% data variables.product.product_location %}. Isso não se aplicará se você estiver usando o endereço `noreply` baseado em ID do {% data variables.product.product_name %}. Para obter mais informações, confira "[Como alterar seu nome de usuário do {% data variables.product.prodname_dotcom %}](/articles/changing-your-github-username)".{% endif %} +If you use your `noreply` email address for {% data variables.product.product_name %} to make commits and then [change your username](/articles/changing-your-github-username), those commits will not be associated with your account on {% data variables.location.product_location %}. This does not apply if you're using the ID-based `noreply` address from {% data variables.product.product_name %}. For more information, see "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username)."{% endif %} -## Configurar o endereço de e-mail do commit no {% data variables.product.prodname_dotcom %} +## Setting your commit email address on {% data variables.product.prodname_dotcom %} {% data reusables.files.commit-author-email-options %} -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.emails %} {% data reusables.user-settings.add_and_verify_email %} {% data reusables.user-settings.select_primary_email %}{% ifversion fpt or ghec %} {% data reusables.user-settings.keeping_your_email_address_private %}{% endif %} +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.emails %} +{% data reusables.user-settings.add_and_verify_email %} +{% data reusables.user-settings.select_primary_email %}{% ifversion fpt or ghec %} +{% data reusables.user-settings.keeping_your_email_address_private %}{% endif %} -## Configurar o endereço de e-mail do commit no Git +## Setting your commit email address in Git -Use o comando `git config` para alterar o endereço de email associado aos commits do Git. O novo endereço de email definido ficará visível nos commits futuros que você enviar por push para o {% data variables.product.product_location %} na linha de comando. Os commits feitos antes da alteração do endereço de e-mail do commit continuarão associados ao endereço de e-mail anterior. +You can use the `git config` command to change the email address you associate with your Git commits. The new email address you set will be visible in any future commits you push to {% data variables.location.product_location %} from the command line. Any commits you made prior to changing your commit email address are still associated with your previous email address. -### Configurar o endereço de e-mail para todos os repositórios no computador +### Setting your email address for every repository on your computer {% data reusables.command_line.open_the_multi_os_terminal %} 2. {% data reusables.user-settings.set_your_email_address_in_git %} ```shell - $ git config --global user.email "email@example.com" + $ git config --global user.email "YOUR_EMAIL" ``` 3. {% data reusables.user-settings.confirm_git_email_address_correct %} ```shell @@ -87,17 +85,17 @@ Use o comando `git config` para alterar o endereço de email associado aos commi ``` 4. {% data reusables.user-settings.link_email_with_your_account %} -### Configurar o endereço de e-mail para um repositório específico +### Setting your email address for a single repository -{% data variables.product.product_name %} usa o endereço de e-mail definido na sua configuração local do Git para associar commits enviados por push a partir da linha de comando para sua conta em {% data variables.product.product_location %}. +{% data variables.product.product_name %} uses the email address set in your local Git configuration to associate commits pushed from the command line with your account on {% data variables.location.product_location %}. -Você pode alterar o endereço de e-mail associado aos commits feitos em um repositório específico. Isso sobrescreverá as definições de configuração global do Git no repositório em questão, mas não afetará nenhum outro repositório. +You can change the email address associated with commits you make in a single repository. This will override your global Git configuration settings in this one repository, but will not affect any other repositories. {% data reusables.command_line.open_the_multi_os_terminal %} -2. Altere o diretório de trabalho atual para o repositório local no qual deseja configurar o endereço de e-mail associado aos commits do Git. +2. Change the current working directory to the local repository where you want to configure the email address that you associate with your Git commits. 3. {% data reusables.user-settings.set_your_email_address_in_git %} ```shell - $ git config user.email "email@example.com" + $ git config user.email "YOUR_EMAIL" ``` 4. {% data reusables.user-settings.confirm_git_email_address_correct %} ```shell diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md index 51451cc868..aad324c45b 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md @@ -1,6 +1,6 @@ --- -title: Alterar seu nome de usuário do GitHub -intro: 'Você pode alterar o nome de usuário da sua conta em {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %} se sua instância usar autenticação integrada{% endif %}.' +title: Changing your GitHub username +intro: 'You can change the username for your account on {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.location.product_location %} if your instance uses built-in authentication{% endif %}.' redirect_from: - /articles/how-to-change-your-username - /articles/changing-your-github-user-name @@ -17,24 +17,19 @@ versions: topics: - Accounts shortTitle: Change your username -ms.openlocfilehash: 28f4d0ea1a16fed0e44f34312abfd507e2f991b7 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145164630' --- + {% ifversion ghec or ghes %} {% note %} {% ifversion ghec %} -**Observação**: os membros de um {% data variables.product.prodname_emu_enterprise %} não podem alterar os nomes de usuário. O administrador do IdP da empresa controla seu nome de usuário para {% data variables.product.product_name %}. Para obter mais informações, confira "[Sobre as {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)". +**Note**: Members of an {% data variables.enterprise.prodname_emu_enterprise %} cannot change usernames. Your enterprise's IdP administrator controls your username for {% data variables.product.product_name %}. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." {% elsif ghes %} -**Observação**: se você entrar no {% data variables.product.product_location %} com as credenciais do LDAP ou do SSO (logon único), somente o administrador local poderá alterar seu nome de usuário. Para obter mais informações sobre os métodos de autenticação do {% data variables.product.product_name %}, confira "[Autenticação de usuários no {% data variables.product.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)". +**Note**: If you sign into {% data variables.location.product_location %} with LDAP credentials or single sign-on (SSO), only your local administrator can change your username. For more information about authentication methods for {% data variables.product.product_name %}, see "[Authenticating users for {% data variables.location.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)." {% endif %} @@ -42,55 +37,61 @@ ms.locfileid: '145164630' {% endif %} -## Sobre alterações no nome de usuário +## About username changes -Você pode alterar seu nome de usuário para outro nome de usuário que não esteja em uso no momento.{% ifversion fpt or ghec %} Se o nome de usuário desejado não estiver disponível, considere outros nomes ou variações exclusivas. Usar um número, hífen ou uma ortografia alternativa pode ajudar você a encontrar um nome de usuário semelhante que ainda está disponível. +You can change your username to another username that is not currently in use.{% ifversion fpt or ghec %} If the username you want is not available, consider other names or unique variations. Using a number, hyphen, or an alternative spelling might help you find a similar username that's still available. -Se você for o proprietário de uma marca do nome de usuário, encontre mais informações sobre como fazer uma reclamação de marca em nossa página [Política de marca](/free-pro-team@latest/github/site-policy/github-trademark-policy). +If you hold a trademark for the username, you can find more information about making a trademark complaint on our [Trademark Policy](/free-pro-team@latest/github/site-policy/github-trademark-policy) page. -Se você não tiver uma marca registrada para o nome, você poderá escolher outro nome de usuário ou manter seu nome de usuário atual. O {% data variables.contact.github_support %} não pode liberar o nome de usuário indisponível para você. Para obter mais informações, confira "[Como alterar seu nome de usuário](#changing-your-username)".{% endif %} +If you do not hold a trademark for the name, you can choose another username or keep your current username. {% data variables.contact.github_support %} cannot release the unavailable username for you. For more information, see "[Changing your username](#changing-your-username)."{% endif %} -Depois de alterar seu nome de usuário, o nome antigo será disponibilizado para reivindicação por qualquer pessoa. A maioria das referências aos seus repositórios sob o nome de usuário antigo muda automaticamente para o novo nome de usuário. No entanto, alguns links para seu perfil não são redirecionados automaticamente. +After changing your username, your old username becomes available for anyone else to claim. Most references to your repositories under the old username automatically change to the new username. However, some links to your profile won't automatically redirect. -O {% data variables.product.product_name %} não pode configurar redirecionamentos para: -- [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) usando seu nome de usuário antigo -- Links para [gists](/articles/creating-gists) que incluem seu nome de usuário antigo +{% data variables.product.product_name %} cannot set up redirects for: +- [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) using your old username +- Links to [gists](/articles/creating-gists) that include your old username {% ifversion fpt or ghec %} -Se você for integrante de um {% data variables.product.prodname_emu_enterprise %}, não será possível alterar seu nome de usuário. {% data reusables.enterprise-accounts.emu-more-info-account %} +If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you cannot make changes to your username. {% data reusables.enterprise-accounts.emu-more-info-account %} {% endif %} -## Referências de repositório +## Repository references -Após alteração do nome de usuário, o {% data variables.product.product_name %} redirecionará automaticamente as referências para os repositórios. -- Os links da web para repositórios existentes continuarão funcionando. Esse processo pode demorar alguns minutos para ser concluído após a alteração. -- A linha de comando que faz push dos clones do repositório local para as URLs de controle do remote continuarão funcionando. +After you change your username, {% data variables.product.product_name %} will automatically redirect references to your repositories. +- Web links to your existing repositories will continue to work. This can take a few minutes to complete after you make the change. +- Command line pushes from your local repository clones to the old remote tracking URLs will continue to work. -Se o novo proprietário do seu antigo nome de usuário criar um repositório com o mesmo nome do seu repositório, isso substituirá a entrada de redirecionamento e o seu redirecionamento para de funcionar. Por conta dessa possibilidade, é recomendável atualizar todas as URLs existentes do repositório remote após alteração do seu nome de usuário. Para obter mais informações, confira "[Como gerenciar repositórios remotos](/github/getting-started-with-github/managing-remote-repositories)". +If the new owner of your old username creates a repository with the same name as your repository, that will override the redirect entry and your redirect will stop working. Because of this possibility, we recommend you update all existing remote repository URLs after changing your username. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." -## Links para a página de perfil anterior +## Links to your previous profile page -Depois que você alterar seu nome de usuário, os links para sua página de perfil anterior, como `https://{% data variables.command_line.backticks %}/previoususername`, retornarão um erro 404. Recomendamos atualizar todos os links para a sua conta em {% data variables.product.product_location %} a partir de outro lugar{% ifversion fpt or ghec %}, como seu LinkedIn ou perfil do Twitter{% endif %}. +After changing your username, links to your previous profile page, such as `https://{% data variables.command_line.backticks %}/previoususername`, will return a 404 error. We recommend updating any links to your account on {% data variables.location.product_location %} from elsewhere{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profile{% endif %}. -## Seus commits no Git +## Your Git commits -{% ifversion fpt or ghec %}Os commits do Git associados ao endereço de email `noreply` fornecido pelo {% data variables.product.product_name %} não serão atribuídas ao novo nome de usuário e não serão exibidos no seu grafo de contribuições.{% endif %} Se os commits do Git estiverem associados a outro endereço de email que você [adicionou à sua conta do GitHub](/articles/adding-an-email-address-to-your-github-account), {% ifversion fpt or ghec %}incluindo o endereço de email `noreply` baseado em ID fornecido pelo {% data variables.product.product_name %}, {% endif %}eles continuarão sendo atribuídos a você e serão exibidos no seu grafo de contribuições depois que você tiver alterado seu nome de usuário. Para obter mais informações sobre como definir seu endereço de email, confira "[Como definir seu endereço de email de commit](/articles/setting-your-commit-email-address)". +{% ifversion fpt or ghec %}Git commits that were associated with your {% data variables.product.product_name %}-provided `noreply` email address won't be attributed to your new username and won't appear in your contributions graph.{% endif %} If your Git commits are associated with another email address you've [added to your GitHub account](/articles/adding-an-email-address-to-your-github-account), {% ifversion fpt or ghec %}including the ID-based {% data variables.product.product_name %}-provided `noreply` email address, {% endif %}they'll continue to be attributed to you and appear in your contributions graph after you've changed your username. For more information on setting your email address, see "[Setting your commit email address](/articles/setting-your-commit-email-address)." -## Alterar nome de usuário +## Your gists -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.account_settings %} -3. Na seção "Alterar nome de usuário", clique em **Alterar nome de usuário**. - ![Botão Alterar nome de usuário](/assets/images/help/settings/settings-change-username.png){% ifversion fpt or ghec %} -4. Leia os avisos sobre a mudança de seu nome de usuário. Se você ainda quiser alterar seu nome de usuário, clique em **Entendi. Vamos alterar meu nome de usuário**. - ![Botão de aviso Alterar Nome de Usuário](/assets/images/help/settings/settings-change-username-warning-button.png) -5. Digite um novo nome de usuário. - ![Campo Novo nome de usuário](/assets/images/help/settings/settings-change-username-enter-new-username.png) -6. Se o nome de usuário escolhido estiver disponível, clique em **Alterar meu nome de usuário**. Se o nome que você escolheu estiver indisponível, tente um nome de usuário diferente ou uma das sugestões que aparecem. - ![Botão de aviso Alterar Nome de Usuário](/assets/images/help/settings/settings-change-my-username-button.png) {% endif %} +After changing your username, the URLs to any public or secret gists will also change and previous links to these will return a 404 error. We recommend updating the links to these gists anywhere you may have shared them. -## Leitura adicional +## Changing your username -- "[Por que meus commits estão vinculados ao usuário errado?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)"{% ifversion fpt or ghec %} -- "[Política de nome de usuário do {% data variables.product.prodname_dotcom %}](/free-pro-team@latest/github/site-policy/github-username-policy)"{% endif %} +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.account_settings %} +3. In the "Change username" section, click **Change username**. + ![Change Username button](/assets/images/help/settings/settings-change-username.png){% ifversion fpt or ghec %} +4. Read the warnings about changing your username. If you still want to change your username, click **I understand, let's change my username**. + ![Change Username warning button](/assets/images/help/settings/settings-change-username-warning-button.png) +5. Type a new username. + ![New username field](/assets/images/help/settings/settings-change-username-enter-new-username.png) +6. If the username you've chosen is available, click **Change my username**. If the username you've chosen is unavailable, you can try a different username or one of the suggestions you see. + ![Change Username warning button](/assets/images/help/settings/settings-change-my-username-button.png) +{% endif %} + +## Further reading + +- "[Why are my commits linked to the wrong user?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)"{% ifversion fpt or ghec %} +- "[{% data variables.product.prodname_dotcom %} Username Policy](/free-pro-team@latest/github/site-policy/github-username-policy)"{% endif %} diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md index 1f60927a6f..20771e8187 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md @@ -1,54 +1,51 @@ --- -title: Gerenciando configurações de acessibilidade +title: Managing accessibility settings shortTitle: Manage accessibility settings -intro: 'A interface do usuário do {% data variables.product.product_name %} pode se adaptar às suas necessidades motoras, cognitivas, de visão, audição ou aprendizado.' +intro: "{% data variables.product.product_name %}'s user interface can adapt to your vision, hearing, motor, cognitive, or learning needs." versions: feature: keyboard-shortcut-accessibility-setting redirect_from: - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings type: how_to miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: d4811368ab825f0b24864283f8be54672f72a787 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147614316' --- -## Sobre as configurações de acessibilidade -Para criar uma experiência sobre {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} que atenda as suas necessidades, você pode personalizar a interface do usuário. As configurações de acessibilidade podem ser essenciais para pessoas com deficiência, mas podem ser úteis para qualquer pessoa. Por exemplo, a personalização de atalhos de teclado é essencial para pessoas que navegam usando o controle de voz, mas podem ser úteis para qualquer pessoa quando um atalho de teclado para dados {% data variables.product.product_name %} entra em conflito com outro atalho de aplicativo. +## About accessibility settings -## Gerenciando configurações de acessibilidade +To create an experience on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} that fits your needs, you can customize the user interface. Accessibility settings can be essential for people with disabilities, but can be useful to anyone. For example, customization of keyboard shortcuts is essential to people who navigate using voice control, but can be useful to anyone when a keyboard shortcut for {% data variables.product.product_name %} clashes with another application shortcut. -Você pode decidir se deseja usar alguns ou todos os atalhos de teclado no {% ifversion fpt or ghec %}{% data variables.product.product_location %}{% elsif ghes or ghae %}site do {% data variables.product.product_location %}{% endif %} e pode controlar a exibição de imagens animadas. +## Managing accessibility settings -### Como gerenciar atalhos de teclado +You can decide whether you want to use some or all keyboard shortcuts on {% ifversion fpt or ghec %}{% data variables.location.product_location %}{% elsif ghes or ghae %}the website for {% data variables.location.product_location %}{% endif %}, and you can control the display of animated images. -Você pode executar ações no site do {% data variables.product.product_name %}, usando o teclado sozinho. Atalhos de teclado podem ser úteis para economizar tempo, mas podem ser ativados acidentalmente ou interferir na tecnologia adaptativa. +### Managing keyboard shortcuts -Por padrão, todos os atalhos de teclado são habilitados em {% data variables.product.product_name %}. Para obter mais informações, confira "[Atalhos de teclado](/get-started/using-github/keyboard-shortcuts)". +You can perform actions across the {% data variables.product.product_name %} website by using your keyboard alone. Keyboard shortcuts can be useful to save time, but can be activated accidentally or interfere with assistive technology. -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.accessibility_settings %} -1. Em "Atalhos de teclado", gerencie as configurações dos atalhos de teclado. +By default, all keyboard shortcuts are enabled on {% data variables.product.product_name %}. For more information, see "[Keyboard shortcuts](/get-started/using-github/keyboard-shortcuts)." - - Para desabilitar teclas de atalho que não usam teclas modificadoras, como Control ou Comando, em "Geral", desmarque a opção **Teclas de caractere**. - - Se você desabilitar as chaves de caractere, ainda poderá disparar atalhos para o navegador da Web e ainda poderá disparar atalhos para {% data variables.product.product_name %} que usam uma tecla modificadora. +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.accessibility_settings %} +1. Under "Keyboard shortcuts", manage settings for your keyboard shortcuts. + + - To disable shortcut keys that don't use modifiers keys like Control or Command, under "General", deselect **Character keys**. + - If you disable character keys, you may still be able to trigger shortcuts for your web browser, and you can still trigger shortcuts for {% data variables.product.product_name %} that use a modifier key. {%- ifversion command-palette %} - - Para personalizar os atalhos de teclado para disparar a paleta de comandos, em "Paleta de comandos", use os menus suspensos para escolher um atalho de teclado. Para obter mais informações, confira "[Paleta de comandos do {% data variables.product.company_short %}](/get-started/using-github/github-command-palette)." + - To customize the keyboard shortcuts for triggering the command palette, under "Command palette", use the drop-down menus to choose a keyboard shortcut. For more information, see "[{% data variables.product.company_short %} Command Palette](/get-started/using-github/github-command-palette)." {%- endif %} {% ifversion motion-management %} -### Como gerenciar o movimento +### Managing motion -Você pode controlar como {% data variables.product.product_name %} exibe imagens _.gif_ animadas. +You can control how {% data variables.product.product_name %} displays animated _.gif_ images. -Por padrão, {% data variables.product.product_name %} sincroniza-se com a sua preferência de nível do sistema para reduzir o movimento. Para obter mais informações, confira a documentação ou as configurações do seu sistema operacional. +By default, {% data variables.product.product_name %} syncs with your system-level preference for reduced motion. For more information, see the documentation or settings for your operating system. -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.accessibility_settings %} -1. Em "Movimento", gerencie as configurações de movimento. +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.accessibility_settings %} +1. Under "Motion", manage settings for motion. - - Para controlar como {% data variables.product.product_name %} exibe imagens animadas, em "Reprodução automática de imagens animadas", selecione **Sincronizar com o sistema**, **Habilitado** ou **Desabilitado**. + - To control how {% data variables.product.product_name %} displays animated images, under "Autoplay animated images", select **Sync with system**, **Enabled**, or **Disabled**. {% endif %} diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md index c2d389b7ce..25c69e1a94 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md @@ -1,6 +1,6 @@ --- -title: Gerenciar o nome do branch-padrão para seus repositórios -intro: 'Você pode definir os novos repositórios para nome do branch-padrão que você criar em {% data variables.product.product_location %}.' +title: Managing the default branch name for your repositories +intro: 'You can set the default branch name for new repositories that you create on {% data variables.location.product_location %}.' versions: fpt: '*' ghes: '*' @@ -13,29 +13,24 @@ redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories shortTitle: Manage default branch name -ms.openlocfilehash: a3943f32860f55becaa840f7ca40c13ba87b5ce2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145193759' --- -## Sobre o gerenciamento do nome do brancc-padrão +## About management of the default branch name -Ao criar um novo repositório em {% data variables.product.product_location %}, o repositório conterá um branch, que será o branch-padrão. Você pode alterar o nome que {% data variables.product.product_name %} usa para o branch-padrão em novos repositórios que você criar. Para obter mais informações sobre o branch padrão, confira "[Sobre os branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)". +When you create a new repository on {% data variables.location.product_location %}, the repository contains one branch, which is the default branch. You can change the name that {% data variables.product.product_name %} uses for the default branch in new repositories you create. For more information about the default branch, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)." {% data reusables.branches.change-default-branch %} -## Definir o nome do branch-padrão +## Setting the default branch name -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.repo-tab %} -3. Em "Branch padrão do repositório", clique em **Alterar o nome do branch padrão agora**. - ![Botão Substituir](/assets/images/help/settings/repo-default-name-button.png) -4. Digite o nome-padrão que você gostaria de usar para novos branches. - ![Caixa de texto usada para inserir o nome padrão](/assets/images/help/settings/repo-default-name-text.png) -5. Clique em **Atualizar**. - ![Botão Atualizar](/assets/images/help/settings/repo-default-name-update.png) +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.repo-tab %} +3. Under "Repository default branch", click **Change default branch name now**. + ![Override button](/assets/images/help/settings/repo-default-name-button.png) +4. Type the default name that you would like to use for new branches. + ![Text box for entering default name](/assets/images/help/settings/repo-default-name-text.png) +5. Click **Update**. + ![Update button](/assets/images/help/settings/repo-default-name-update.png) -## Leitura adicional +## Further reading -- "[Como gerenciar o nome do branch padrão para repositórios na sua organização](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)" +- "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)" diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md index 705b738067..aedaff2bc8 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md @@ -1,6 +1,6 @@ --- -title: Práticas recomendadas para deixar a empresa -intro: 'Se você usa sua conta de usuário no {% data variables.product.product_name %} com finalidade pessoal e profissional, considere algumas práticas ao sair da empresa ou da organização.' +title: Best practices for leaving your company +intro: 'If you use your account on {% data variables.product.product_name %} for both personal and work purposes, there are a few things to keep in mind when you leave your company or organization.' redirect_from: - /articles/best-practices-for-leaving-your-company - /github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company @@ -13,36 +13,31 @@ versions: topics: - Accounts shortTitle: Leaving your company -ms.openlocfilehash: c288584891981eab7ffe4204e2028b0e70cf1d08 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147687081' --- -Antes de sair da empresa, não se esqueça de atualizar as seguintes informações em sua conta pessoal: -- Cancele a verificação do endereço de email da sua empresa [excluindo-o nas configurações de Email](/articles/changing-your-primary-email-address). Você pode adicioná-lo novamente sem verificação para manter os commits associados vinculados à sua conta. -- [Altere o endereço de email principal](/articles/changing-your-primary-email-address) do email da sua empresa para o seu email pessoal. -- [Verifique o novo endereço de email principal](/articles/verifying-your-email-address). -- [Altere seu nome de usuário do GitHub](/articles/changing-your-github-username) para remover qualquer referência à sua empresa ou organização, se necessário. -- Se você habilitou a 2FA (autenticação de dois fatores) para sua conta pessoal, verifique se você (não sua empresa) controla o método de autenticação 2FA configurado. Para obter mais informações, confira "[Como configurar a autenticação de dois fatores](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)". +Before you leave your company, make sure you update the following information in your personal account: -## Saída das organizações +- Unverify your company email address by [deleting it in your Email settings](/articles/changing-your-primary-email-address). You can then re-add it without verifying to keep any associated commits linked to your account. +- [Change your primary email address](/articles/changing-your-primary-email-address) from your company email to your personal email. +- [Verify your new primary email address](/articles/verifying-your-email-address). +- [Change your GitHub username](/articles/changing-your-github-username) to remove any references to your company or organization, if necessary. +- If you've enabled two-factor (2FA) authentication for your personal account, make sure that you (not your company) control the 2FA authentication method you have configured. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)." -Se você estiver trabalhando com repositórios que pertencem a uma organização, o ideal será [se remover como membro da organização](/articles/removing-yourself-from-an-organization). Observe que, se você for o proprietário da organização, primeiro, deverá [transferir a propriedade da organização](/articles/transferring-organization-ownership) para outra pessoa. +## Leaving organizations -A menos que você esteja usando um {% data variables.product.prodname_managed_user %}, você poderá acessar sua conta pessoal, mesmo após sair da organização. Para obter mais informações sobre {% data variables.product.prodname_emus %}, confira "[Sobre {% data variables.product.prodname_emus %}]({% ifversion not ghec%}/enterprise-cloud@latest{% endif %}/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users){% ifversion not ghec %}" na documentação do {% data variables.product.prodname_ghe_cloud %}.{% else %}."{% endif %} +If you've been working with repositories that belong to an organization, you'll want to [remove yourself as a member of the organization](/articles/removing-yourself-from-an-organization). Note that if you are the organization owner, you should first [transfer ownership of the organization](/articles/transferring-organization-ownership) to another person. -## Remover associações profissionais a repositórios pessoais +Unless you're using a {% data variables.enterprise.prodname_managed_user %}, you'll still be able to access your personal account, even after leaving the organization. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}]({% ifversion not ghec%}/enterprise-cloud@latest{% endif %}/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} -Se você estiver colaborando profissionalmente com outra pessoa em repositórios que pertencem a sua conta pessoal, o ideal será [remover sua função como colaborador](/articles/removing-yourself-from-a-collaborator-s-repository) desses repositórios. +## Removing professional associations with personal repositories -- [Pare de inspecionar os repositórios](https://github.com/watching) relacionados ao seu trabalho. Você não desejará mais receber essas notificações! -- [Transfira os repositórios dos quais você é o proprietário](/articles/how-to-transfer-a-repository) e nos quais outras pessoas talvez precisem continuar trabalhando depois que você sair deles. -- [Exclua os forks que pertencem a você](/articles/deleting-a-repository) relacionados ao trabalho que você estava fazendo. Não se preocupe, excluir uma bifurcação não exclui o repositório upstream. -- Exclua cópias locais de suas bifurcações que possam existir no seu computador: +If you've been collaborating professionally with another person on repositories that belong to their personal account, you'll want to [remove yourself as a collaborator](/articles/removing-yourself-from-a-collaborator-s-repository) from those repositories. + +- [Stop watching repositories](https://github.com/watching) related to your work. You won't want those notifications anymore! +- [Transfer repositories you own](/articles/how-to-transfer-a-repository) that others may need to continue working on after you leave. +- [Delete forks that belong to you](/articles/deleting-a-repository) that are related to the work you were doing. Don't worry, deleting a fork doesn't delete the upstream repository. +- Delete local copies of your forks that may exist on your computer: ```shell -$ rm -rf work_directory +$ rm -rf WORK_DIRECTORY ``` diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/about-continuous-integration.md b/translations/pt-BR/content/actions/automating-builds-and-tests/about-continuous-integration.md index 8e356c734b..eed83fb6ff 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/about-continuous-integration.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/about-continuous-integration.md @@ -1,6 +1,6 @@ --- -title: Sobre integração contínua -intro: 'Você pode criar fluxos de trabalho de integração contínua (CI) personalizados diretamente no repositório do {% data variables.product.prodname_dotcom %} com o {% data variables.product.prodname_actions %}.' +title: About continuous integration +intro: 'You can create custom continuous integration (CI) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.' redirect_from: - /articles/about-continuous-integration - /github/automating-your-workflow-with-github-actions/about-continuous-integration @@ -16,48 +16,45 @@ type: overview topics: - CI shortTitle: Continuous integration -ms.openlocfilehash: 26b9088133ad561900d06a0c885d6b06b9b55861 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147880658' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## Sobre integração contínua +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} -A integração contínua (CI, Continuous Integration) é uma prática de software que exige commits frequentes de códigos para 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. +## About continuous integration -Ao fazer commit do seu repositório, você pode continuamente compilar e testar o código para garantir que o commit não insira erros. Seus testes podem incluir linters de código (que verificam formatação de estilo), verificações de segurança, cobertura de código, testes funcionais e outras verificações personalizadas. +Continuous integration (CI) is a software practice that requires frequently committing code to a shared repository. Committing code more often detects 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. -Para compilar e testar seu código, é necessário usar um servidor. Você pode criar e testar atualizações no local antes de fazer push do código para um repositório, ou pode usar um servidor de CI que verifica os novos commits de código em um repositório. +When you commit code to your repository, you can continuously build and test the code to make sure that the commit doesn't introduce errors. Your tests can include code linters (which check style formatting), security checks, code coverage, functional tests, and other custom checks. -## Sobre integração contínua usando {% data variables.product.prodname_actions %} +Building and testing your code requires a server. You can build and test updates locally before pushing code to a repository, or you can use a CI server that checks for new code commits in a repository. -{% ifversion ghae %}A CI que usa o {% data variables.product.prodname_actions %} oferece fluxos de trabalho que podem compilar o código no repositório e executar os testes. Os fluxos de trabalho podem ser executados em sistemas de executores que você hospeda. Para obter mais informações, confira "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)". -{% else %} CI que usa {% data variables.product.prodname_actions %} oferece fluxos de trabalho que podem criar o código no seu repositório e executar seus testes. Os fluxos de trabalho podem ser executados em máquinas virtuais hospedadas em {% data variables.product.prodname_dotcom %} ou em máquinas que você mesmo pode hospedar. Para obter mais informações, confira "[Sobre os executores hospedados no {% data variables.product.prodname_dotcom %}](/actions/using-github-hosted-runners/about-github-hosted-runners)" e "[Sobre os executores auto-hospedados](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)". +## About continuous integration using {% data variables.product.prodname_actions %} + +{% ifversion ghae %}CI using {% data variables.product.prodname_actions %} offers workflows that can build the code in your repository and run your tests. Workflows can run on runner systems that you host. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." +{% else %} CI using {% data variables.product.prodname_actions %} offers workflows that can build the code in your repository and run your tests. Workflows can run on {% data variables.product.prodname_dotcom %}-hosted virtual machines, or on machines that you host yourself. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and "[About self-hosted runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)." {% endif %} -Você pode configurar seu fluxo de trabalho de CI para ser executado quando ocorrer um evento do {% data variables.product.prodname_dotcom %} (por exemplo, quando o novo código é enviado por push para o repositório), de acordo com um agendamento definido ou quando um evento externo ocorre usando o webhook de expedição do repositório. +You can configure your CI workflow to run when a {% data variables.product.prodname_dotcom %} event occurs (for example, when new code is pushed to your repository), on a set schedule, or when an external event occurs using the repository dispatch webhook. -{% data variables.product.product_name %} executa seus testes de CI e fornece os resultados de cada teste no pull request para que você possa ver se a mudança no seu branch introduz um erro. Quando todos os testes de CI em um fluxo de trabalho forem aprovados, as alterações que passaram por push estarão prontas para a revisão de um integrante da equipe ou para o merge. Se algum teste falhar, uma de suas alterações pode ter causado a falha. +{% data variables.product.product_name %} runs your CI tests and provides the results of each test in the pull request, so you can see whether the change in your branch introduces an error. When all CI tests in a workflow pass, the changes you pushed are ready to be reviewed by a team member or merged. When a test fails, one of your changes may have caused the failure. -Ao configurar o CI no seu repositório, {% data variables.product.product_name %} analisa o código no seu repositório e recomenda fluxos de trabalho CI baseados no idioma e na estrutura do seu repositório. Por exemplo, se você usar o [Node.js](https://nodejs.org/en/), o {% data variables.product.product_name %} vai sugerir um fluxo de trabalho inicial que instala os pacotes do Node.js e executa os testes. Você pode usar o fluxo de trabalho inicial de CI sugerido por {% data variables.product.product_name %}, personalizar o fluxo de trabalho inicial sugerido ou criar o seu próprio arquivo de fluxo de trabalho personalizado para executar seus testes de CI. +When you set up CI in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends CI workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a starter workflow that installs your Node.js packages and runs your tests. You can use the CI starter workflow suggested by {% data variables.product.product_name %}, customize the suggested starter workflow, or create your own custom workflow file to run your CI tests. -![Captura de tela de fluxos de trabalho iniciais de integração contínua sugeridos](/assets/images/help/repository/ci-with-actions-template-picker.png) +![Screenshot of suggested continuous integration starter workflows](/assets/images/help/repository/ci-with-actions-template-picker.png) -Além de ajudá-lo a configurar fluxos de trabalho de CI para seu projeto, você pode usar {% data variables.product.prodname_actions %} para criar fluxos de trabalho ao longo de todo o ciclo de vida de desenvolvimento do software. Por exemplo, você pode usar ações para implantar, criar pacotes ou lançar uma versão do seu projeto. Para obter mais informações, confira "[Sobre o {% data variables.product.prodname_actions %}](/articles/about-github-actions)". +In addition to helping you set up CI workflows for your project, you can use {% data variables.product.prodname_actions %} to create workflows across the full software development life cycle. For example, you can use actions to deploy, package, or release your project. For more information, see "[About {% data variables.product.prodname_actions %}](/articles/about-github-actions)." -Para obter uma definição de termos comuns, confira "[Conceitos principais do {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)". +For a definition of common terms, see "[Core concepts for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)." -## Fluxo de trabalho inicial +## Starter workflow -{% data variables.product.product_name %} oferece fluxo de trabalho inicial de CI para uma série de linguagens e estruturas. +{% data variables.product.product_name %} offers CI starter workflow for a variety of languages and frameworks. -Navegue pela lista completa de fluxos de trabalho iniciais de CI oferecida pelo {% data variables.product.company_short %} no {% ifversion fpt or ghec %}repositório [actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci){% else %} repositório `actions/starter-workflows` do {% data variables.product.product_location %}{% endif %}. +Browse the complete list of CI starter workflow offered by {% data variables.product.company_short %} in the {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) repository{% else %} `actions/starter-workflows` repository on {% data variables.location.product_location %}{% endif %}. -## Leitura adicional +## Further reading {% ifversion fpt or ghec %} -- "[Como gerenciar a cobrança do {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)" {% endif %} +- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)" +{% endif %} diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md index a19e2f232b..382e81006b 100644 --- a/translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md +++ b/translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md @@ -1,6 +1,7 @@ --- -title: Criar uma ação composta -intro: 'Neste guia, você aprenderá a criar uma ação composta.' +title: Creating a composite action +shortTitle: Create a composite action +intro: 'In this guide, you''ll learn how to build a composite action.' redirect_from: - /actions/creating-actions/creating-a-composite-run-steps-action versions: @@ -11,62 +12,58 @@ versions: type: tutorial topics: - Action development -shortTitle: Composite action -ms.openlocfilehash: fae29972e9ce4a19485e2f13ed2ff80b589a1a0a -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145083688' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## Introdução +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} -Neste guia, você aprenderá os componentes básicos necessários para criar e usar uma ação composta empacotada. Para manter o foco deste guia nos componentes necessários para empacotar a ação, a funcionalidade do código da ação é mínima. A ação imprime "Hello World" e "Goodbye", ou, se você fornecer um nome personalizado, imprimirá "Hello [who-to-greet]" e "Goodbye". A ação também mapeia um número aleatório para a variável de saída `random-number` e executa um script chamado `goodbye.sh`. +## Introduction -Ao concluir este projeto, você entenderá como criar a sua própria ação composta e testá-la em um fluxo de trabalho. +In this guide, you'll learn about the basic components needed to create and use a packaged composite action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" and then "Goodbye", or if you provide a custom name, it prints "Hello [who-to-greet]" and then "Goodbye". The action also maps a random number to the `random-number` output variable, and runs a script named `goodbye.sh`. + +Once you complete this project, you should understand how to build your own composite action and test it in a workflow. {% data reusables.actions.context-injection-warning %} -## Pré-requisitos +## Prerequisites -Antes de começar, você criará um repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. +Before you begin, you'll create a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. -1. Crie um repositório público novo no {% data variables.product.product_location %}. Você pode escolher qualquer nome de repositório ou usar o exemplo de `hello-world-composite-action` a seguir. É possível adicionar esses arquivos após push do projeto no {% data variables.product.product_name %}. Para obter mais informações, confira "[Criar um repositório](/articles/creating-a-new-repository)". +1. Create a new public repository on {% data variables.location.product_location %}. You can choose any repository name, or use the following `hello-world-composite-action` example. You can add these files after your project has been pushed to {% data variables.product.product_name %}. For more information, see "[Create a new repository](/articles/creating-a-new-repository)." -1. Clone o repositório para seu computador. Para obter mais informações, confira "[Como clonar um repositório](/articles/cloning-a-repository)". +1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)." -1. No seu terminal, mude os diretórios para seu novo repositório. +1. From your terminal, change directories into your new repository. ```shell cd hello-world-composite-action ``` -2. No repositório `hello-world-composite-action`, crie um arquivo chamado `goodbye.sh` e adicione o seguinte código de exemplo: +2. In the `hello-world-composite-action` repository, create a new file called `goodbye.sh`, and add the following example code: ```bash echo "Goodbye" ``` -3. No terminal, torne `goodbye.sh` executável. +3. From your terminal, make `goodbye.sh` executable. ```shell chmod +x goodbye.sh ``` -1. Ainda no terminal, faça check-in do arquivo `goodbye.sh`. +1. From your terminal, check in your `goodbye.sh` file. ```shell git add goodbye.sh git commit -m "Add goodbye script" git push ``` -## Criar um arquivo de metadados de ação +## Creating an action metadata file -1. No repositório `hello-world-composite-action`, crie um arquivo chamado `action.yml` e adicione o código de exemplo a seguir. Para obter mais informações sobre essa sintaxe, confira "[`runs` para uma ação composta](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-actions)". +1. In the `hello-world-composite-action` repository, create a new file called `action.yml` and add the following example code. For more information about this syntax, see "[`runs` for a composite actions](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-actions)". - {% raw %} **action.yml** + {% raw %} + **action.yml** ```yaml name: 'Hello World' description: 'Greet someone' @@ -84,21 +81,26 @@ Antes de começar, você criará um repositório em {% ifversion ghae %}{% data steps: - run: echo Hello ${{ inputs.who-to-greet }}. shell: bash - - id: random-number-generator + - id: random-number-generator{% endraw %} +{%- ifversion actions-save-state-set-output-envs %} + run: echo "random-number=$(echo $RANDOM)" >> $GITHUB_OUTPUT +{%- else %} run: echo "::set-output name=random-number::$(echo $RANDOM)" +{%- endif %}{% raw %} shell: bash - run: echo "${{ github.action_path }}" >> $GITHUB_PATH - shell: bash + shell: bash - run: goodbye.sh shell: bash ``` - {% endraw %} Esse arquivo define a entrada `who-to-greet`, mapeia o número gerado aleatoriamente para a variável de saída `random-number` e executa o script `goodbye.sh`. Também informa ao executor como executar a ação composta. + {% endraw %} + This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, and runs the `goodbye.sh` script. It also tells the runner how to execute the composite action. - Para obter mais informações sobre como gerenciar saídas, confira "[`outputs` para uma ação composta](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)". + For more information about managing outputs, see "[`outputs` for a composite action](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)". - Para obter mais informações sobre como usar `github.action_path`, confira "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)". + For more information about how to use `github.action_path`, see "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)". -1. No terminal, faça check-in do arquivo `action.yml`. +1. From your terminal, check in your `action.yml` file. ```shell git add action.yml @@ -106,18 +108,18 @@ Antes de começar, você criará um repositório em {% ifversion ghae %}{% data git push ``` -1. No seu terminal, adicione uma tag. Este exemplo usa uma tag chamada `v1`. Para obter mais informações, confira "[Sobre as ações](/actions/creating-actions/about-actions#using-release-management-for-actions)". +1. From your terminal, add a tag. This example uses a tag called `v1`. For more information, see "[About actions](/actions/creating-actions/about-actions#using-release-management-for-actions)." ```shell git tag -a -m "Description of this release" v1 git push --follow-tags ``` -## Testar sua ação em um fluxo de trabalho +## Testing out your action in a workflow -O código de fluxo de trabalho a seguir usa a ação olá, mundo concluída criada em "[Como criar um arquivo de metadados de ação](/actions/creating-actions/creating-a-composite-action#creating-an-action-metadata-file)". +The following workflow code uses the completed hello world action that you made in "[Creating an action metadata file](/actions/creating-actions/creating-a-composite-action#creating-an-action-metadata-file)". -Copie o código de fluxo de trabalho em um arquivo `.github/workflows/main.yml` em outro repositório, mas substitua `actions/hello-world-composite-action@v1` pelo repositório e pela tag que você criou. Você também pode substituir a entrada `who-to-greet` pelo seu nome. +Copy the workflow code into a `.github/workflows/main.yml` file in another repository, but replace `actions/hello-world-composite-action@v1` with the repository and tag you created. You can also replace the `who-to-greet` input with your name. **.github/workflows/main.yml** ```yaml @@ -137,4 +139,4 @@ jobs: shell: bash ``` -No repositório, clique na guia **Ações** e selecione a execução mais recente do fluxo de trabalho. A saída deve incluir: "Hello Mona the Octocat", o resultado do script "Goodbye" e um número aleatório. +From your repository, click the **Actions** tab, and select the latest workflow run. The output should include: "Hello Mona the Octocat", the result of the "Goodbye" script, and a random number. diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md index 0c94e6f3d0..6ea8fbe52c 100644 --- a/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md @@ -1,6 +1,7 @@ --- -title: Criando uma ação de contêiner do Docker -intro: 'Este guia apresenta as etapas mínimas exigidas para criar uma ação de contêiner Docker. ' +title: Creating a Docker container action +shortTitle: Create a Docker container action +intro: 'This guide shows you the minimal steps required to build a Docker container action. ' redirect_from: - /articles/creating-a-docker-container-action - /github/automating-your-workflow-with-github-actions/creating-a-docker-container-action @@ -15,50 +16,47 @@ type: tutorial topics: - Action development - Docker -shortTitle: Docker container action -ms.openlocfilehash: f22b361f25f406dfdb1233f4d9ce62f2b6b919dc -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147518781' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## Introdução +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} -Neste guia, você aprenderá os componentes básicos necessários para criar e usar uma ação do contêiner Docker empacotado. Para manter o foco deste guia nos componentes necessários para empacotar a ação, a funcionalidade do código da ação é mínima. A ação imprime "Olá, mundo" nos registros ou "Olá, [who-to-greet]", se você fornecer um nome personalizado. +## Introduction -Ao terminar esse projeto, você entenderá como criar sua própria ação de contêiner Docker e poderá testá-la em um fluxo de trabalho. +In this guide, you'll learn about the basic components needed to create and use a packaged Docker container action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" in the logs or "Hello [who-to-greet]" if you provide a custom name. + +Once you complete this project, you should understand how to build your own Docker container action and test it in a workflow. {% data reusables.actions.self-hosted-runner-reqs-docker %} {% data reusables.actions.context-injection-warning %} -## Pré-requisitos +## Prerequisites -Pode ser útil ter um entendimento básico das variáveis do ambiente {% data variables.product.prodname_actions %} e do sistema de arquivo do contêiner Docker: +You may find it helpful to have a basic understanding of {% data variables.product.prodname_actions %} environment variables and the Docker container filesystem: -- "[Como usar variáveis de ambiente](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" {% ifversion ghae %} -- "[Sistema de arquivos do contêiner do Docker](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)". -{% else %} -- "[Sobre executores hospedados no {% data variables.product.prodname_dotcom %}](/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem)" {% endif %} +- "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" +{% ifversion ghae %} +- "[Docker container filesystem](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)." +{% else %} +- "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem)" +{% endif %} -Antes de começar, você deverá criar um repositório de {% data variables.product.prodname_dotcom %}. +Before you begin, you'll need to create a {% data variables.product.prodname_dotcom %} repository. -1. Crie um repositório novo no {% data variables.product.product_location %}. Você pode escolher qualquer nome para o repositório ou usar "hello-world-docker-action", como nesse exemplo. Para obter mais informações, confira "[Criar um repositório](/articles/creating-a-new-repository)". +1. Create a new repository on {% data variables.location.product_location %}. You can choose any repository name or use "hello-world-docker-action" like this example. For more information, see "[Create a new repository](/articles/creating-a-new-repository)." -1. Clone o repositório para seu computador. Para obter mais informações, confira "[Como clonar um repositório](/articles/cloning-a-repository)". +1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)." -1. No seu terminal, mude os diretórios para seu novo repositório. +1. From your terminal, change directories into your new repository. ```shell{:copy} cd hello-world-docker-action ``` -## Criar um arquivo Docker +## Creating a Dockerfile -No diretório `hello-world-docker-action`, crie um arquivo `Dockerfile`. Verifique se o seu nome de arquivo está em maiúsculas corretamente (use um `D` maiúsculo, mas não um `f` maiúsculo) se estiver tendo problemas. Para obter mais informações, confira "[Suporte do Dockerfile para o {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions)". +In your new `hello-world-docker-action` directory, create a new `Dockerfile` file. Make sure that your filename is capitalized correctly (use a capital `D` but not a capital `f`) if you're having issues. For more information, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions)." **Dockerfile** ```Dockerfile{:copy} @@ -72,11 +70,12 @@ COPY entrypoint.sh /entrypoint.sh ENTRYPOINT ["/entrypoint.sh"] ``` -## Criar um arquivo de metadados de ação +## Creating an action metadata file -Crie um arquivo `action.yml` no diretório `hello-world-docker-action` que você criou acima. Para obter mais informações, confira "[Sintaxe de metadados do {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions)". +Create a new `action.yml` file in the `hello-world-docker-action` directory you created above. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions)." -{% raw %} **action.yml** +{% raw %} +**action.yml** ```yaml{:copy} # action.yml name: 'Hello World' @@ -97,19 +96,19 @@ runs: ``` {% endraw %} -Esses metadados definem uma entrada `who-to-greet` e um parâmetro de saída `time`. Para transmitir entradas para o contêiner do Docker, você deve declarar a entrada usando `inputs` e transmitir a entrada na palavra-chave `args`. Tudo o que você inclui em `args` é transmitido para o contêiner, mas para ter uma melhor capacidade de descoberta para os usuários da sua ação, recomendamos o uso de entradas. +This metadata defines one `who-to-greet` input and one `time` output parameter. To pass inputs to the Docker container, you should declare the input using `inputs` and pass the input in the `args` keyword. Everything you include in `args` is passed to the container, but for better discoverability for users of your action, we recommended using inputs. -O {% data variables.product.prodname_dotcom %} criará uma imagem com base no `Dockerfile` e executará comandos em um novo contêiner usando essa imagem. +{% data variables.product.prodname_dotcom %} will build an image from your `Dockerfile`, and run commands in a new container using this image. -## Gravar um código de ação +## Writing the action code -Você pode escolher qualquer imagem Docker de base e, portanto, qualquer linguagem para sua ação. O exemplo de script de shell a seguir usa a variável de entrada `who-to-greet` para imprimir "Olá, [quem deve ser saudado]" no arquivo de log. +You can choose any base Docker image and, therefore, any language for your action. The following shell script example uses the `who-to-greet` input variable to print "Hello [who-to-greet]" in the log file. -Na sequência, o script obtém a hora atual e a configura como uma variável de saída que pode ser usada pelas ações executadas posteriormente em um trabalho. Para que o {% data variables.product.prodname_dotcom %} reconheça variáveis de saída, você precisa usar um comando de fluxo de trabalho em uma sintaxe específica: `echo "::set-output name=::"`. Para obter mais informações, confira "[Comandos do fluxo de trabalho do {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions#setting-an-output-parameter)". +Next, the script gets the current time and sets it as an output variable that actions running later in a job can use. In order for {% data variables.product.prodname_dotcom %} to recognize output variables, you must {% ifversion actions-save-state-set-output-envs %}write them to the `$GITHUB_OUTPUT` environment file: `echo "=" >> $GITHUB_OUTPUT`{% else %}use a workflow command in a specific syntax: `echo "::set-output name=::"`{% endif %}. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions#setting-an-output-parameter)." -1. Crie um arquivo `entrypoint.sh` no diretório `hello-world-docker-action`. +1. Create a new `entrypoint.sh` file in the `hello-world-docker-action` directory. -1. Adicione o código a seguir ao arquivo `entrypoint.sh`. +1. Add the following code to your `entrypoint.sh` file. **entrypoint.sh** ```shell{:copy} @@ -117,30 +116,43 @@ Na sequência, o script obtém a hora atual e a configura como uma variável de echo "Hello $1" time=$(date) +{%- ifversion actions-save-state-set-output-envs %} + echo "time=$time" >> $GITHUB_OUTPUT +{%- else %} echo "::set-output name=time::$time" +{%- endif %} ``` - Se `entrypoint.sh` for executado sem erros, o status da ação será definido como `success`. Você também pode definir explicitamente códigos de saída no código de ação para fornecer o status de uma ação. Para obter mais informações, confira "[Como configurar códigos de saída para ações](/actions/creating-actions/setting-exit-codes-for-actions)". + If `entrypoint.sh` executes without any errors, the action's status is set to `success`. You can also explicitly set exit codes in your action's code to provide an action's status. For more information, see "[Setting exit codes for actions](/actions/creating-actions/setting-exit-codes-for-actions)." -1. Torne seu arquivo `entrypoint.sh` executável executando o comando a seguir no sistema. + +1. Make your `entrypoint.sh` file executable. Git provides a way to explicitly change the permission mode of a file so that it doesn’t get reset every time there is a clone/fork. ```shell{:copy} - $ chmod +x entrypoint.sh + $ git update-index --chmod=+x entrypoint.sh ``` -## Criar README +1. Optionally, to check the permission mode of the file in the git index, run the following command. -Para que as pessoas saibam como usar sua ação, você pode criar um arquivo README. Um arquivo README é útil quando você planeja compartilhar publicamente sua ação, mas também é uma ótima maneira de lembrá-lo ou sua equipe sobre como usar a ação. + ```shell{:copy} + $ git ls-files --stage entrypoint.sh + ``` -No diretório `hello-world-docker-action`, crie um arquivo `README.md` que especifica as seguintes informações: + An output like `100755 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 0 entrypoint.sh` means the file has the executable permission. In this example, `755` denotes the executable permission. -- Uma descrição detalhada do que a ação faz. -- Argumentos de entrada e saída obrigatórios. -- Argumentos de entrada e saída opcionais. -- Segredos usados pela ação. -- Variáveis de ambiente que a ação usa. -- Um exemplo de como usar sua ação em um fluxo de trabalho. +## Creating a README -**LEIAME.md** +To let people know how to use your action, you can create a README file. A README is most helpful when you plan to share your action publicly, but is also a great way to remind you or your team how to use the action. + +In your `hello-world-docker-action` directory, create a `README.md` file that specifies the following information: + +- A detailed description of what the action does. +- Required input and output arguments. +- Optional input and output arguments. +- Secrets the action uses. +- Environment variables the action uses. +- An example of how to use your action in a workflow. + +**README.md** ```markdown{:copy} # Hello world docker action @@ -160,16 +172,16 @@ The time we greeted you. ## Example usage -uses: actions/hello-world-docker-action@v1 +uses: actions/hello-world-docker-action@{% ifversion actions-save-state-set-output-envs %}v2{% else %}v1{% endif %} with: who-to-greet: 'Mona the Octocat' ``` -## Faça commit, tag e push da sua ação para {% data variables.product.product_name %} +## Commit, tag, and push your action to {% data variables.product.product_name %} -No terminal, faça commit dos arquivos `action.yml`, `entrypoint.sh`, `Dockerfile` e `README.md`. +From your terminal, commit your `action.yml`, `entrypoint.sh`, `Dockerfile`, and `README.md` files. -Adicionar uma tag da versão para versões da sua ação é considerada uma prática recomendada. Para obter mais informações sobre o controle de versão da ação, confira "[Sobre as ações](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)". +It's best practice to also add a version tag for releases of your action. For more information on versioning your action, see "[About actions](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)." ```shell{:copy} git add action.yml entrypoint.sh Dockerfile README.md @@ -178,17 +190,17 @@ git tag -a -m "My first action release" v1 git push --follow-tags ``` -## Testar sua ação em um fluxo de trabalho +## Testing out your action in a workflow -Agora você está pronto para testar sua ação em um fluxo de trabalho. Quando uma ação está em um repositório privado, ela só pode ser usada em fluxos de trabalho no mesmo repositório. As ações públicas podem ser usadas por fluxos de trabalho em qualquer repositório. +Now you're ready to test your action out in a workflow. When an action is in a private repository, the action can only be used in workflows in the same repository. Public actions can be used by workflows in any repository. {% data reusables.actions.enterprise-marketplace-actions %} -### Exemplo usando uma ação pública +### Example using a public action -O código de fluxo de trabalho a seguir usa a ação _hello world_ concluída no repositório público [`actions/hello-world-docker-action`](https://github.com/actions/hello-world-docker-action). Copie o código de exemplo de fluxo de trabalho a seguir em um arquivo `.github/workflows/main.yml`, mas substitua o `actions/hello-world-docker-action` pelo nome do repositório e da ação. Você também pode substituir a entrada `who-to-greet` pelo seu nome. {% ifversion fpt or ghec %}As ações públicas podem ser usadas mesmo se não forem publicadas em {% data variables.product.prodname_marketplace %}. Para obter mais informações, confira "[Como publicar uma ação](/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action)". {% endif %} +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. Copy the following workflow example code into a `.github/workflows/main.yml` file, but replace the `actions/hello-world-docker-action` with your repository and action name. You can also replace the `who-to-greet` input with your name. {% ifversion fpt or ghec %}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 %} -{% raw %} **.github/workflows/main.yml** +**.github/workflows/main.yml** ```yaml{:copy} on: [push] @@ -199,18 +211,17 @@ jobs: steps: - name: Hello world action step id: hello - uses: actions/hello-world-docker-action@v1 + uses: actions/hello-world-docker-action{% ifversion actions-save-state-set-output-envs %}v2{% else %}v1{% endif %} with: who-to-greet: 'Mona the Octocat' # Use the output from the `hello` step - name: Get the output time - run: echo "The time was ${{ steps.hello.outputs.time }}" + run: echo "The time was {% raw %}${{ steps.hello.outputs.time }}"{% endraw %} ``` -{% endraw %} -### Exemplo usando uma ação privada +### Example using a private action -Copie o código de exemplo de fluxo de trabalho a seguir para um arquivo `.github/workflows/main.yml` no repositório da ação. Você também pode substituir a entrada `who-to-greet` pelo seu nome. {% ifversion fpt or ghec %}Esta ação privada não pode ser publicada em {% data variables.product.prodname_marketplace %}, e só pode ser usada neste repositório.{% endif %} +Copy the following example workflow code into a `.github/workflows/main.yml` file in your action's repository. You can also replace the `who-to-greet` input with your name. {% ifversion fpt or ghec %}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** ```yaml{:copy} @@ -235,7 +246,7 @@ jobs: run: echo "The time was {% raw %}${{ steps.hello.outputs.time }}"{% endraw %} ``` -No repositório, clique na guia **Ações** e selecione a execução mais recente do fluxo de trabalho. Em **Trabalhos** ou no grafo de visualização, clique em **Um trabalho para dizer olá**. Você verá "Olá, Mona, o Octocat" ou o nome usado para a entrada `who-to-greet` e o carimbo de data/hora impresso no log. +From your repository, click the **Actions** tab, and select the latest workflow run. Under **Jobs** or in the visualization graph, click **A job to say hello**. You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log. -![Uma captura de tela de sua ação em um fluxo de trabalho](/assets/images/help/repository/docker-action-workflow-run-updated.png) +![A screenshot of using your action in a workflow](/assets/images/help/repository/docker-action-workflow-run-updated.png) diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md index 66fc48555f..5a1ea071a9 100644 --- a/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md @@ -41,7 +41,7 @@ Before you begin, you'll need to download Node.js and create a public {% data va {% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}https://nodejs.org/en/download/{% else %}https://nodejs.org/en/download/releases/{% endif %} -1. Create a new public repository on {% data variables.product.product_location %} and call it "hello-world-javascript-action". For more information, see "[Create a new repository](/articles/creating-a-new-repository)." +1. Create a new public repository on {% data variables.location.product_location %} and call it "hello-world-javascript-action". For more information, see "[Create a new repository](/articles/creating-a-new-repository)." 1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)." @@ -141,29 +141,31 @@ In your `hello-world-javascript-action` directory, create a `README.md` file tha - Environment variables the action uses. - An example of how to use your action in a workflow. -```markdown{:copy} +````markdown{:copy} # Hello world javascript action This action prints "Hello World" or "Hello" + the name of a person to greet to the log. ## Inputs -## `who-to-greet` +### `who-to-greet` **Required** The name of the person to greet. Default `"World"`. ## Outputs -## `time` +### `time` The time we greeted you. ## Example usage +```yaml uses: actions/hello-world-javascript-action@v1.1 with: who-to-greet: 'Mona the Octocat' ``` +```` ## Commit, tag, and push your action to GitHub diff --git a/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md index 58a58b0664..5409856a9d 100644 --- a/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -58,7 +58,7 @@ inputs: When you specify an input in a workflow file or use a default input value, {% data variables.product.prodname_dotcom %} creates an environment variable for the input with the name `INPUT_`. The environment variable created converts input names to uppercase letters and replaces spaces with `_` characters. -If the action is written using a [composite](/actions/creating-actions/creating-a-composite-action), then it will not automatically get `INPUT_`. If the conversion doesn't occur, you can change these inputs manually. +If the action is written using a [composite](/actions/creating-actions/creating-a-composite-action), then it will not automatically get `INPUT_`. If the conversion doesn't occur, you can change these inputs manually. To access the environment variable in a Docker container action, you must pass the input using the `args` keyword in the action metadata file. For more information about the action metadata file for Docker container actions, see "[Creating a Docker container action](/articles/creating-a-docker-container-action#creating-an-action-metadata-file)." @@ -125,8 +125,12 @@ outputs: runs: using: "composite" steps: - - id: random-number-generator + - id: random-number-generator{% endraw %} +{%- ifversion actions-save-state-set-output-envs %} + run: echo "random-id=$(echo $RANDOM)" >> $GITHUB_OUTPUT +{%- else %} run: echo "::set-output name=random-id::$(echo $RANDOM)" +{%- endif %}{% raw %} shell: bash ``` {% endraw %} @@ -155,7 +159,7 @@ runs: ### `runs.using` -**Required** The runtime used to execute the code specified in [`main`](#runsmain). +**Required** The runtime used to execute the code specified in [`main`](#runsmain). - Use `node12` for Node.js v12.{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %} - Use `node16` for Node.js v16.{% endif %} @@ -365,7 +369,7 @@ runs: with: first_name: Mona middle_name: The - last_name: Octocat + last_name: Octocat ``` {% endif %} @@ -481,7 +485,7 @@ runs: ```yaml branding: - icon: 'award' + icon: 'award' color: 'green' ``` @@ -522,9 +526,9 @@ The name of the v4.28.0 [Feather](https://feathericons.com/) icon to use. Brand Here is an exhaustive list of all currently supported icons: - diff --git a/translations/pt-BR/content/actions/deployment/about-deployments/deploying-with-github-actions.md b/translations/pt-BR/content/actions/deployment/about-deployments/deploying-with-github-actions.md index 8d7300ca0c..31f3680e14 100644 --- a/translations/pt-BR/content/actions/deployment/about-deployments/deploying-with-github-actions.md +++ b/translations/pt-BR/content/actions/deployment/about-deployments/deploying-with-github-actions.md @@ -1,6 +1,6 @@ --- -title: Implantando com GitHub Actions -intro: Aprenda a controlar imolantações com funcionalidades como ambientes e simultaneidade. +title: Deploying with GitHub Actions +intro: Learn how to control deployments with features like environments and concurrency. versions: fpt: '*' ghes: '*' @@ -12,38 +12,34 @@ redirect_from: topics: - CD shortTitle: Deploy with GitHub Actions -ms.openlocfilehash: 533d85d83bea53d34af3d8b9a47d0d4426ea4bc6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145179181' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## Introdução +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} -{% data variables.product.prodname_actions %} oferece funcionalidades que permitem que você controle implantações. Você pode: +## Introduction -- Acionar fluxos de trabalho com uma série de eventos. -- Configurar ambientes para definir regras antes que um trabalho possa prosseguir e limitar o acesso a segredos. -- Usar a simultaneidade para controlar o número de implantações em execução por vês. +{% data variables.product.prodname_actions %} offers features that let you control deployments. You can: -Para obter mais informações sobre a implantação contínua, confira "[Sobre a implantação contínua](/actions/deployment/about-continuous-deployment)". +- Trigger workflows with a variety of events. +- Configure environments to set rules before a job can proceed and to limit access to secrets. +- Use concurrency to control the number of deployments running at a time. -## Pré-requisitos +For more information about continuous deployment, see "[About continuous deployment](/actions/deployment/about-continuous-deployment)." -Você deve estar familiarizado com a sintaxe de {% data variables.product.prodname_actions %}. Para obter mais informações, confira "[Aprenda a usar o {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". +## Prerequisites -## Acionando a sua implantação +You should be familiar with the syntax for {% data variables.product.prodname_actions %}. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." -Você pode usar uma série de eventos para acionar seu fluxo de trabalho de implantação. Algumas das opções mais comuns são: `pull_request`, `push` e `workflow_dispatch`. +## Triggering your deployment -Por exemplo, um fluxo de trabalho com os seguintes gatilhos é executado sempre que: +You can use a variety of events to trigger your deployment workflow. Some of the most common are: `pull_request`, `push`, and `workflow_dispatch`. -- Há um push para o branch `main`. -- Uma solicitação de pull direcionada ao branch `main` é aberta, sincronizada ou reaberta. -- Alguém a aciona manualmente. +For example, a workflow with the following triggers runs whenever: + +- There is a push to the `main` branch. +- A pull request targeting the `main` branch is opened, synchronized, or reopened. +- Someone manually triggers it. ```yaml on: @@ -56,23 +52,23 @@ on: workflow_dispatch: ``` -Para obter mais informações, confira "[Eventos que disparam fluxos de trabalho](/actions/reference/events-that-trigger-workflows)". +For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)." -## Usar ambientes +## Using environments {% data reusables.actions.about-environments %} -## Usando simultaneidade +## Using concurrency -A moeda garante que apenas um único trabalho ou fluxo de trabalho que usa o mesmo grupo de concorrência seja executado de cada vez. Você pode usar a concorrência para que um ambiente tenha, no máximo, uma implantação em andamento e uma implantação pendente por vez. +Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. You can use concurrency so that an environment has a maximum of one deployment in progress and one deployment pending at a time. {% note %} -**Observação:** `concurrency` e `environment` não estão conectados. O valor da simultaneidade pode ser qualquer regra; não precisa ser o nome de um ambiente. Além disso, se outro fluxo de trabalho usar o mesmo ambiente, mas não especificar a equivalência, esse fluxo de trabalho não estará sujeito a nenhuma regra de simultaneidade. +**Note:** `concurrency` and `environment` are not connected. The concurrency value can be any string; it does not need to be an environment name. Additionally, if another workflow uses the same environment but does not specify concurrency, that workflow will not be subject to any concurrency rules. {% endnote %} -Por exemplo, quando o fluxo de trabalho a seguir for executado, ele será colocado em pausa com o status `pending` se qualquer trabalho ou fluxo de trabalho que usa o grupo de simultaneidade `production` estiver em andamento. Ele também cancelará qualquer trabalho ou fluxo de trabalho que use o grupo de simultaneidade `production` e que tenha o status `pending`. Isso significa que haverá, no máximo, um trabalho ou um fluxo de trabalho em execução e um pendente que usa o grupo de simultaneidade `production`. +For example, when the following workflow runs, it will be paused with the status `pending` if any job or workflow that uses the `production` concurrency group is in progress. It will also cancel any job or workflow that uses the `production` concurrency group and has the status `pending`. This means that there will be a maximum of one running and one pending job or workflow in that uses the `production` concurrency group. ```yaml name: Deployment @@ -93,7 +89,7 @@ jobs: # ...deployment-specific steps ``` -Você também pode especificar simultaneidade no nível do trabalho. Isso permitirá que outros trabalhos no fluxo de trabalho continuem mesmo que o trabalho simultâneo esteja `pending`. +You can also specify concurrency at the job level. This will allow other jobs in the workflow to proceed even if the concurrent job is `pending`. ```yaml name: Deployment @@ -113,7 +109,7 @@ jobs: # ...deployment-specific steps ``` -Use também `cancel-in-progress` para cancelar qualquer trabalho ou fluxo de trabalho em execução no mesmo grupo de simultaneidade. +You can also use `cancel-in-progress` to cancel any currently running job or workflow in the same concurrency group. ```yaml name: Deployment @@ -136,41 +132,42 @@ jobs: # ...deployment-specific steps ``` -Para obter diretrizes sobre como escrever etapas específicas à implantação, confira "[Como encontrar exemplos de implantação](#finding-deployment-examples)". +For guidance on writing deployment-specific steps, see "[Finding deployment examples](#finding-deployment-examples)." -## Exibir o histórico de implantações +## Viewing deployment history -Quando um fluxo de trabalho de {% data variables.product.prodname_actions %} é implantado em um ambiente, o ambiente é exibido na página principal do repositório. Para obter mais informações sobre como ver implantações em ambientes, confira "[Como ver o histórico de implantações](/developers/overview/viewing-deployment-history)". +When a {% data variables.product.prodname_actions %} workflow deploys to an environment, the environment is displayed on the main page of the repository. For more information about viewing deployments to environments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)." -## Monitoramento de fluxo de trabalho +## Monitoring workflow runs -Cada execução de fluxo de trabalho gera um gráfico em tempo real que ilustra o progresso da execução. Você pode usar este gráfico para monitorar e depurar implantações. Para obter mais informações, confira "[Como usar o grafo de visualização](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)". +Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug deployments. For more information see, "[Using the visualization graph](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)." -Você também pode visualizar os registros de cada execução do fluxo de trabalho e o histórico de execuções do fluxo de trabalho. Para obter mais informações, confira "[Como ver o histórico de execução do fluxo de trabalho](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)". +You can also view the logs of each workflow run and the history of workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." -## Rastreando implantações por meio de aplicativos +## Tracking deployments through apps -{% ifversion fpt or ghec %} Se a sua conta pessoal ou de organização no {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} estiver integrada ao Microsoft Teams ou ao Slack, você poderá acompanhar as implantações que usam ambientes por meio do Microsoft Teams ou do Slack. Por exemplo, você pode receber notificações por meio do aplicativo quando uma implantação estiver pendente de aprovação, quando uma implantação for aprovada, ou quando o status de implantação for alterado. Para obter mais informações sobre como integrar o Microsoft Teams ou o Slack, confira "[Extensões e integrações do GitHub](/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations#team-communication-tools)". +{% ifversion fpt or ghec %} +If your personal account or organization on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} is integrated with Microsoft Teams or Slack, you can track deployments that use environments through Microsoft Teams or Slack. For example, you can receive notifications through the app when a deployment is pending approval, when a deployment is approved, or when the deployment status changes. For more information about integrating Microsoft Teams or Slack, see "[GitHub extensions and integrations](/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations#team-communication-tools)." {% endif %} -Você também pode criar um aplicativo que usa webhooks de status de implantação e implantação para rastrear implantações. {% data reusables.actions.environment-deployment-event %} Para obter mais informações, confira "[Aplicativos](/developers/apps)" e "[Eventos e cargas de webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)". +You can also build an app that uses deployment and deployment status webhooks to track deployments. {% data reusables.actions.environment-deployment-event %} For more information, see "[Apps](/developers/apps)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)." {% ifversion fpt or ghes or ghec %} -## Escolher um executor +## Choosing a runner -Você pode executar seu fluxo de trabalho de implantação em executores hospedados no {% data variables.product.company_short %} ou em executores auto-hospedados. O tráfego dos executores hospedados no {% data variables.product.company_short %} pode vir de uma [ampla variedade de endereços de rede](/rest/reference/meta#get-github-meta-information). Se você está fazendo a implantação em um ambiente interno e a empresa restringe o tráfego externo em redes privadas, os fluxos de trabalho do {% data variables.product.prodname_actions %} em execução nos executores hospedados no {% data variables.product.company_short %} podem não conseguir se comunicar com os serviços ou recursos internos. Para superar isso, você pode hospedar seus próprios executores. Para obter mais informações, confira "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" e "[Sobre os executores hospedados no GitHub](/actions/using-github-hosted-runners/about-github-hosted-runners)". +You can run your deployment workflow on {% data variables.product.company_short %}-hosted runners or on self-hosted runners. Traffic from {% data variables.product.company_short %}-hosted runners can come from a [wide range of network addresses](/rest/reference/meta#get-github-meta-information). If you are deploying to an internal environment and your company restricts external traffic into private networks, {% data variables.product.prodname_actions %} workflows running on {% data variables.product.company_short %}-hosted runners may not be able to communicate with your internal services or resources. To overcome this, you can host your own runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[About GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)." {% endif %} -## Exibindo um selo de status +## Displaying a status badge -Você pode usar um selo de status para exibir o status do seu fluxo de trabalho de implantação. {% data reusables.repositories.actions-workflow-status-badge-intro %} +You can use a status badge to display the status of your deployment workflow. {% data reusables.repositories.actions-workflow-status-badge-intro %} -Para obter mais informações, confira "[Como adicionar uma notificação de status do fluxo de trabalho](/actions/managing-workflow-runs/adding-a-workflow-status-badge)". +For more information, see "[Adding a workflow status badge](/actions/managing-workflow-runs/adding-a-workflow-status-badge)." -## Procurando exemplos de implantação +## Finding deployment examples -Este artigo mostrou as funcionalidades de {% data variables.product.prodname_actions %} que você pode adicionar aos seus fluxos de trabalho de implantação. +This article demonstrated features of {% data variables.product.prodname_actions %} that you can add to your deployment workflows. {% data reusables.actions.cd-templates-actions %} diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md index 42292165d2..abc8392e96 100644 --- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md +++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md @@ -143,8 +143,12 @@ jobs: # push it to ECR so that it can # be deployed to ECS. docker build -t $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG . - docker push $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG + docker push $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG{% endraw %} +{%- ifversion actions-save-state-set-output-envs %} + echo "image=$ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG" >> $GITHUB_OUTPUT +{%- else %} echo "::set-output name=image::$ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG" +{%- endif %}{% raw %} - name: Fill in the new image ID in the Amazon ECS task definition id: task-def diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md index c857ecebd0..29abd3f106 100644 --- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md +++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md @@ -55,9 +55,9 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you 1. Set registry credentials for your web app. - Create a personal access token with the `repo` and `read:packages` scopes. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." + Create a {% data variables.product.pat_v1 %} with the `repo` and `read:packages` scopes. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - Set `DOCKER_REGISTRY_SERVER_URL` to `https://ghcr.io`, `DOCKER_REGISTRY_SERVER_USERNAME` to the GitHub username or organization that owns the repository, and `DOCKER_REGISTRY_SERVER_PASSWORD` to your personal access token from above. This will give your web app credentials so it can pull the container image after your workflow pushes a newly built image to the registry. You can do this with the following Azure CLI command: + Set `DOCKER_REGISTRY_SERVER_URL` to `https://ghcr.io`, `DOCKER_REGISTRY_SERVER_USERNAME` to the GitHub username or organization that owns the repository, and `DOCKER_REGISTRY_SERVER_PASSWORD` to your {% data variables.product.pat_generic %} from above. This will give your web app credentials so it can pull the container image after your workflow pushes a newly built image to the registry. You can do this with the following Azure CLI command: ```shell az webapp config appsettings set \ diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md index 882844a780..ff5236a5ca 100644 --- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md +++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md @@ -102,7 +102,11 @@ jobs: id: composer-cache if: steps.check_files.outputs.files_exists == 'true' run: | +{%- ifversion actions-save-state-set-output-envs %} + echo "dir=$(composer config cache-files-dir)" >> $GITHUB_OUTPUT +{%- else %} echo "::set-output name=dir::$(composer config cache-files-dir)" +{%- endif %} - name: Set up dependency caching for faster installs uses: {% data reusables.actions.action-cache %} diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md index 23a3f85bba..42683676cd 100644 --- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md +++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md @@ -1,7 +1,7 @@ --- -title: Configurando OpenID Connect em provedores da nuvem -shortTitle: Configuring OpenID Connect in cloud providers -intro: Use o OpenID Connect dentro de seus fluxos de trabalho para efetuar a autenticação com provedores de nuvem. +title: Configuring OpenID Connect in cloud providers +shortTitle: OpenID Connect in cloud providers +intro: Use OpenID Connect within your workflows to authenticate with cloud providers. miniTocMaxHeadingLevel: 3 versions: fpt: '*' @@ -10,58 +10,54 @@ versions: type: tutorial topics: - Security -ms.openlocfilehash: 5f23d33f9f8199acfd78e105531b2b07fbf60c27 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145065593' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## Visão geral +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} -O OpenID Connect (OIDC) permite que os seus fluxos de trabalho de {% data variables.product.prodname_actions %} acessem recursos no seu provedor da nuvem, sem ter que armazenar qualquer credencial como segredos de {% data variables.product.prodname_dotcom %} de longa duração. +## Overview -Para usar o OIDC, você primeiro precisará configurar seu provedor de nuvem para confiar no OIDC de {% data variables.product.prodname_dotcom %} como uma identidade federada e, em seguida, atualizar seus fluxos de trabalho para efetuar a autenticação usando tokens. +OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in your cloud provider, without having to store any credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. -## Pré-requisitos +To use OIDC, you will first need to configure your cloud provider to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and must then update your workflows to authenticate using tokens. + +## Prerequisites {% data reusables.actions.oidc-link-to-intro %} {% data reusables.actions.oidc-security-notice %} -## Atualizar o seu fluxo de trabalho de {% data variables.product.prodname_actions %} +## Updating your {% data variables.product.prodname_actions %} workflow -Para atualizar seus fluxos de trabalho para o OIDC, você deverá fazer duas alterações no seu YAML: -1. Adicionar configurações de permissões para o token. -2. Use a ação oficial do seu provedor de nuvem para trocar o token OIDC (JWT) por um token de acesso em nuvem. +To update your workflows for OIDC, you will need to make two changes to your YAML: +1. Add permissions settings for the token. +2. Use the official action from your cloud provider to exchange the OIDC token (JWT) for a cloud access token. -Se seu provedor de nuvem ainda não oferece uma ação oficial, você pode atualizar seus fluxos de trabalho para executar essas etapas manualmente. +If your cloud provider doesn't yet offer an official action, you can update your workflows to perform these steps manually. -### Adicionando configurações de permissões +### Adding permissions settings - {% data reusables.actions.oidc-permissions-token %} + {% data reusables.actions.oidc-permissions-token %} -### Usando ações oficiais +### Using official actions -Se seu provedor de nuvem criou uma ação oficial para usar o OIDC com {% data variables.product.prodname_actions %}, isso permitirá que você troque o token OIDC por um token de acesso facilmente. Em seguida, você pode atualizar seus fluxos de trabalho para usar este token ao acessar recursos da nuvem. +If your cloud provider has created an official action for using OIDC with {% data variables.product.prodname_actions %}, it will allow you to easily exchange the OIDC token for an access token. You can then update your workflows to use this token when accessing cloud resources. -## Usando ações personalizadas +## Using custom actions -Se seu provedor de nuvem não tiver uma ação oficial, ou se você preferir criar scripts personalizados, você poderá solicitar manualmente o token web do JSON (JWT) do provedor OIDC de {% data variables.product.prodname_dotcom %}. +If your cloud provider doesn't have an official action, or if you prefer to create custom scripts, you can manually request the JSON Web Token (JWT) from {% data variables.product.prodname_dotcom %}'s OIDC provider. -Se você não estiver usando uma ação oficial, então {% data variables.product.prodname_dotcom %} recomenda que você use o kit de ferramentas principal das Ações. Como alternativa, você pode usar as seguintes variáveis de ambiente para recuperar o token: `ACTIONS_RUNTIME_TOKEN` e `ACTIONS_ID_TOKEN_REQUEST_URL`. +If you're not using an official action, then {% data variables.product.prodname_dotcom %} recommends that you use the Actions core toolkit. Alternatively, you can use the following environment variables to retrieve the token: `ACTIONS_RUNTIME_TOKEN`, `ACTIONS_ID_TOKEN_REQUEST_URL`. -Para atualizar seus fluxos de trabalho usando esta abordagem, você deverá fazer três alterações no seu YAML: +To update your workflows using this approach, you will need to make three changes to your YAML: -1. Adicionar configurações de permissões para o token. -2. Adicione o código que solicita o token OIDC do provedor OIDC de {% data variables.product.prodname_dotcom %}. -3. Adicione um código que troque o token OIDC com seu provedor de nuvem por um token de acesso. +1. Add permissions settings for the token. +2. Add code that requests the OIDC token from {% data variables.product.prodname_dotcom %}'s OIDC provider. +3. Add code that exchanges the OIDC token with your cloud provider for an access token. -### Solicitando o JWT que usa a o kit de ferramentas principal das Ações +### Requesting the JWT using the Actions core toolkit -O exemplo a seguir demonstra como usar `actions/github-script` com o kit de ferramentas `core` para solicitar o JWT do provedor OIDC do {% data variables.product.prodname_dotcom %}. Para obter mais informações, confira "[Como adicionar pacotes do kit de ferramentas de ações](/actions/creating-actions/creating-a-javascript-action#adding-actions-toolkit-packages)". +The following example demonstrates how to use `actions/github-script` with the `core` toolkit to request the JWT from {% data variables.product.prodname_dotcom %}'s OIDC provider. For more information, see "[Adding actions toolkit packages](/actions/creating-actions/creating-a-javascript-action#adding-actions-toolkit-packages)." ```yaml jobs: @@ -77,17 +73,17 @@ jobs: with: script: | const coredemo = require('@actions/core') - let id_token = await coredemo.getIDToken() - coredemo.setOutput('id_token', id_token) + let id_token = await coredemo.getIDToken() + coredemo.setOutput('id_token', id_token) ``` -### Solicitando o JWT que usa variáveis de ambiente +### Requesting the JWT using environment variables -O exemplo a seguir demonstra como usar variáveis de ambiente para solicitar um token web do JSON. +The following example demonstrates how to use enviroment variables to request a JSON Web Token. -Para seu trabalho de implantação, você precisará definir as configurações de token usando `actions/github-script` com o kit de ferramentas `core`. Para obter mais informações, confira "[Como adicionar pacotes do kit de ferramentas de ações](/actions/creating-actions/creating-a-javascript-action#adding-actions-toolkit-packages)". +For your deployment job, you will need to define the token settings, using `actions/github-script` with the `core` toolkit. For more information, see "[Adding actions toolkit packages](/actions/creating-actions/creating-a-javascript-action#adding-actions-toolkit-packages)." -Por exemplo: +For example: ```yaml jobs: @@ -106,7 +102,7 @@ jobs: core.setOutput('IDTOKENURL', runtimeUrl.trim()) ``` -Em seguida, use `curl` para recuperar um JWT do provedor OIDC do {% data variables.product.prodname_dotcom %}. Por exemplo: +You can then use `curl` to retrieve a JWT from the {% data variables.product.prodname_dotcom %} OIDC provider. For example: ```yaml - run: | @@ -119,19 +115,23 @@ Em seguida, use `curl` para recuperar um JWT do provedor OIDC do {% data variabl fi } jwtd $IDTOKEN +{%- ifversion actions-save-state-set-output-envs %} + echo "idToken=${IDTOKEN}" >> $GITHUB_OUTPUT +{%- else %} echo "::set-output name=idToken::${IDTOKEN}" +{%- endif %} id: tokenid ``` -### Obtendo o token de acesso do provedor da nuvem +### Getting the access token from the cloud provider -Você precisará apresentar o token web JSON do OIDC para seu provedor de nuvem a fim de obter um token de acesso. +You will need to present the OIDC JSON web token to your cloud provider in order to obtain an access token. -Para cada implantação, seus fluxos de trabalho devem usar ações de login em nuvem (ou scripts personalizados) que buscam o token do OIDC e o apresentam ao seu provedor de nuvem. O provedor da nuvem valida as reivindicações no token; se for bem sucedido, ele fornece um token de acesso à nuvem que está disponível apenas para a execução do trabalho. O token de acesso fornecido pode ser usado por ações subsequentes no trabalho para conectar-se à nuvem e fazer a implantação nos seus recursos. +For each deployment, your workflows must use cloud login actions (or custom scripts) that fetch the OIDC token and present it to your cloud provider. The cloud provider then validates the claims in the token; if successful, it provides a cloud access token that is available only to that job run. The provided access token can then be used by subsequent actions in the job to connect to the cloud and deploy to its resources. -As etapas para trocar o token do OIDC por um token de acesso irão variar para cada provedor de nuvem. - -### Acessando recursos no seu provedor da nuvem +The steps for exchanging the OIDC token for an access token will vary for each cloud provider. -Depois de obter o token de acesso, você pode usar as ações específicas da nuvem ou scripts para efetuar a autenticação no provedor da nuvem e fazer a implantação nos seus recursos. Essas etapas podem ser diferentes para cada provedor da nuvem. -Além disso, o tempo de expiração padrão desse token de acesso pode variar entre as nuvens e pode ser configurável no lado do provedor de nuvem. +### Accessing resources in your cloud provider + +Once you've obtained the access token, you can use specific cloud actions or scripts to authenticate to the cloud provider and deploy to its resources. These steps could differ for each cloud provider. +In addition, the default expiration time of this access token could vary between each cloud and can be configurable at the cloud provider's side. diff --git a/translations/pt-BR/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md b/translations/pt-BR/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md index 7fad9277ef..3a4f73c6f2 100644 --- a/translations/pt-BR/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md +++ b/translations/pt-BR/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md @@ -1,7 +1,7 @@ --- -title: 'Como usar simultaneidade, expressões e uma matriz de teste' -shortTitle: 'Using concurrency, expressions, and a test matrix' -intro: 'Como usar recursos avançados do {% data variables.product.prodname_actions %} para CI (integração contínua).' +title: 'Using concurrency, expressions, and a test matrix' +shortTitle: 'Use concurrency, expressions, and a test matrix' +intro: 'How to use advanced {% data variables.product.prodname_actions %} features for continuous integration (CI).' versions: fpt: '*' ghes: '>= 3.5' @@ -10,32 +10,38 @@ versions: type: how_to topics: - Workflows -ms.openlocfilehash: f4edac59fdbcc8f8825a51e25b737b94b17128b0 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147496577' --- + {% data reusables.actions.enterprise-github-hosted-runners %} -## Visão geral de exemplo +## Example overview -{% data reusables.actions.example-workflow-intro-ci %} Quando esse fluxo de trabalho é disparado, ele testa o código usando uma matriz de combinações de teste com `npm test`. +{% data reusables.actions.example-workflow-intro-ci %} When this workflow is triggered, it tests your code using a matrix of test combinations with `npm test`. {% data reusables.actions.example-diagram-intro %} -![Diagrama de visão geral das etapas do fluxo de trabalho](/assets/images/help/images/overview-actions-using-concurrency-expressions-and-a-test-matrix.png) +![Overview diagram of workflow steps](/assets/images/help/images/overview-actions-using-concurrency-expressions-and-a-test-matrix.png) -## Recursos usados neste exemplo +## Features used in this example {% data reusables.actions.example-table-intro %} -| **Recurso** | **Implementação** | +| **Feature** | **Implementation** | | --- | --- | -{% data reusables.actions.workflow-dispatch-table-entry %} {% data reusables.actions.pull-request-table-entry %} {% data reusables.actions.cron-table-entry %} {% data reusables.actions.permissions-table-entry %} {% data reusables.actions.concurrency-table-entry %} | Como executar o trabalho em diferentes executores, dependendo do repositório: | [`runs-on`](/actions/using-jobs/choosing-the-runner-for-a-job)| {% data reusables.actions.if-conditions-table-entry %} | Como usar uma matriz para criar diferentes configurações de teste: | [`matrix`](/actions/using-jobs/using-a-build-matrix-for-your-jobs)| {% data reusables.actions.checkout-action-table-entry %} {% data reusables.actions.setup-node-table-entry %} | Como armazenar dependências em cache: | [`actions/cache`](/actions/advanced-guides/caching-dependencies-to-speed-up-workflows)| | Como executar testes no executor: | `npm test`| +{% data reusables.actions.workflow-dispatch-table-entry %} +{% data reusables.actions.pull-request-table-entry %} +{% data reusables.actions.cron-table-entry %} +{% data reusables.actions.permissions-table-entry %} +{% data reusables.actions.concurrency-table-entry %} +| Running the job on different runners, depending on the repository: | [`runs-on`](/actions/using-jobs/choosing-the-runner-for-a-job)| +{% data reusables.actions.if-conditions-table-entry %} +| Using a matrix to create different test configurations: | [`matrix`](/actions/using-jobs/using-a-build-matrix-for-your-jobs)| +{% data reusables.actions.checkout-action-table-entry %} +{% data reusables.actions.setup-node-table-entry %} +| Caching dependencies: | [`actions/cache`](/actions/advanced-guides/caching-dependencies-to-speed-up-workflows)| +| Running tests on the runner: | `npm test`| -## Fluxo de trabalho de exemplo +## Example workflow {% data reusables.actions.example-docs-engineering-intro %} [`test.yml`](https://github.com/github/docs/blob/main/.github/workflows/test.yml). @@ -106,7 +112,7 @@ jobs: # NOT clone them initially and instead, include them manually # only for the test groups that we know need the files. lfs: {% raw %}${{ matrix.test-group == 'content' }}{% endraw %} - # Enables cloning the Early Access repo later with the relevant PAT + # Enables cloning the Early Access repo later with the relevant {% data variables.product.pat_generic %} persist-credentials: 'false' - name: Figure out which docs-early-access branch to checkout, if internal repo @@ -205,15 +211,15 @@ jobs:
-## Compreendendo o exemplo +## Understanding the example - {% data reusables.actions.example-explanation-table-intro %} + {% data reusables.actions.example-explanation-table-intro %} - - + + @@ -238,7 +244,7 @@ on: @@ -250,7 +256,7 @@ A palavra-chave `on` permite definir os eventos que são disparados quando o flu @@ -262,7 +268,7 @@ Adicione o evento `workflow_dispatch` se você quiser a capacidade de executar m @@ -276,7 +282,7 @@ Adicione o evento `pull_request` para que o fluxo de trabalho seja executado aut @@ -290,7 +296,7 @@ permissions: @@ -304,7 +310,7 @@ concurrency: @@ -316,7 +322,7 @@ Cria um grupo de simultaneidade para eventos específicos e usa o operador `||` @@ -328,7 +334,7 @@ jobs: @@ -340,7 +346,7 @@ Agrupa todos os trabalhos executados no arquivo de fluxo de trabalho. @@ -352,7 +358,7 @@ Define um trabalho com a ID `test` que é armazenada na chave `jobs`. @@ -364,7 +370,7 @@ Configura o trabalho a ser executado em um executor hospedado no {% data variabl @@ -375,7 +381,7 @@ Define o número máximo de minutos para permitir que o trabalho seja executado ``` @@ -387,7 +393,7 @@ Define o número máximo de minutos para permitir que o trabalho seja executado @@ -410,7 +416,7 @@ A configuração de `fail-fast` como `false` impede que o {% data variables.prod @@ -422,7 +428,7 @@ Cria uma matriz chamada `test-group`, com uma matriz de grupos de teste. Esses v @@ -438,7 +444,7 @@ Agrupa todas as etapas que serão executadas durante o trabalho `test`. Cada tra @@ -478,7 +484,7 @@ A palavra-chave `uses` informa que o trabalho deve recuperar a ação chamada `a @@ -497,7 +503,7 @@ Se o repositório atual for o `github/docs-internal`, esta etapa usará a ação @@ -527,7 +533,7 @@ Se o repositório atual for o `github/docs-internal`, esta etapa usará a palavr @@ -546,7 +552,7 @@ Esta etapa executa um comando para fazer check-out de objetos LFS do repositóri @@ -560,7 +566,7 @@ Esta etapa usa a ação `trilom/file-changes-action` para reunir os arquivos alt @@ -576,7 +582,7 @@ Esta etapa executa um comando do shell que usa uma saída da etapa anterior para @@ -589,7 +595,7 @@ Essa etapa usa a ação `actions/setup-node` para instalar a versão especificad @@ -605,7 +611,7 @@ Esta etapa executa o comando do shell `npm ci` para instalar os pacotes de softw @@ -618,7 +624,7 @@ Esta etapa usa a ação `actions/cache` para armazenar em cache o build Next.js, @@ -634,12 +640,12 @@ Esta etapa executa o script de build.
CódigoExplicaçãoCodeExplanation
-A palavra-chave `on` permite definir os eventos que são disparados quando o fluxo de trabalho é executado. Você pode definir vários eventos aqui. Para obter mais informações, confira "[Como disparar um fluxo de trabalho](/actions/using-workflows/triggering-a-workflow#using-events-to-trigger-workflows)". +The `on` keyword lets you define the events that trigger when the workflow is run. You can define multiple events here. For more information, see "[Triggering a workflow](/actions/using-workflows/triggering-a-workflow#using-events-to-trigger-workflows)."
-Adicione o evento `workflow_dispatch` se você quiser a capacidade de executar manualmente esse fluxo de trabalho na interface do usuário. Para obter mais informações, confira [`workflow_dispatch`](/actions/reference/events-that-trigger-workflows#workflow_dispatch). +Add the `workflow_dispatch` event if you want to be able to manually run this workflow in the UI. For more information, see [`workflow_dispatch`](/actions/reference/events-that-trigger-workflows#workflow_dispatch).
-Adicione o evento `pull_request` para que o fluxo de trabalho seja executado automaticamente sempre que uma solicitação de pull for criada ou atualizada. Para obter mais informações, confira [`pull_request`](/actions/using-workflows/events-that-trigger-workflows#pull_request). +Add the `pull_request` event, so that the workflow runs automatically every time a pull request is created or updated. For more information, see [`pull_request`](/actions/using-workflows/events-that-trigger-workflows#pull_request).
-Adicione o evento `push` para que o fluxo de trabalho seja executado automaticamente sempre que um commit for enviado por push a um branch que corresponda ao filtro `main`. Para obter mais informações, confira [`push`](/actions/using-workflows/events-that-trigger-workflows#push). +Add the `push` event, so that the workflow runs automatically every time a commit is pushed to a branch matching the filter `main`. For more information, see [`push`](/actions/using-workflows/events-that-trigger-workflows#push).
-Modifica as permissões padrão concedidas a `GITHUB_TOKEN`. Isso variará dependendo das necessidades do fluxo de trabalho. Para obter mais informações, confira "[Como atribuir permissões a trabalhos](/actions/using-jobs/assigning-permissions-to-jobs)". +Modifies the default permissions granted to `GITHUB_TOKEN`. This will vary depending on the needs of your workflow. For more information, see "[Assigning permissions to jobs](/actions/using-jobs/assigning-permissions-to-jobs)."
-Cria um grupo de simultaneidade para eventos específicos e usa o operador `||` para definir valores de fallback. Para mais informações, confira "[Como usar a simultaneidade](/actions/using-jobs/using-concurrency)". +Creates a concurrency group for specific events, and uses the `||` operator to define fallback values. For more information, see "[Using concurrency](/actions/using-jobs/using-concurrency)."
-Cancela todos os trabalhos ou fluxos de trabalho em execução no mesmo grupo de simultaneidade. +Cancels any currently running job or workflow in the same concurrency group.
-Agrupa todos os trabalhos executados no arquivo de fluxo de trabalho. +Groups together all the jobs that run in the workflow file.
-Define um trabalho com a ID `test` que é armazenada na chave `jobs`. +Defines a job with the ID `test` that is stored within the `jobs` key.
-Configura o trabalho a ser executado em um executor hospedado no {% data variables.product.prodname_dotcom %} ou um executor auto-hospedado, dependendo do repositório que executa o fluxo de trabalho. Neste exemplo, o trabalho será executado em um executor auto-hospedado se o repositório for chamado `docs-internal` e estiver dentro da organização `github`. Se o repositório não corresponder a esse caminho, ele será executado em um executor `ubuntu-latest` hospedado no {% data variables.product.prodname_dotcom %}. Para obter mais informações sobre essas opções, confira "[Como escolher o executor para um trabalho](/actions/using-jobs/choosing-the-runner-for-a-job)". +Configures the job to run on a {% data variables.product.prodname_dotcom %}-hosted runner or a self-hosted runner, depending on the repository running the workflow. In this example, the job will run on a self-hosted runner if the repository is named `docs-internal` and is within the `github` organization. If the repository doesn't match this path, then it will run on an `ubuntu-latest` runner hosted by {% data variables.product.prodname_dotcom %}. For more information on these options see "[Choosing the runner for a job](/actions/using-jobs/choosing-the-runner-for-a-job)."
-Define o número máximo de minutos para permitir que o trabalho seja executado antes de ser cancelado automaticamente. Para obter mais informações, confira [`timeout-minutes`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes). +Sets the maximum number of minutes to let the job run before it is automatically canceled. For more information, see [`timeout-minutes`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes).
- Esta seção define a matriz de build dos trabalhos. + This section defines the build matrix for your jobs.
-A configuração de `fail-fast` como `false` impede que o {% data variables.product.prodname_dotcom %} cancele todos os trabalhos em andamento quando algum trabalho da matriz falhar. +Setting `fail-fast` to `false` prevents {% data variables.product.prodname_dotcom %} from cancelling all in-progress jobs if any matrix job fails.
-Cria uma matriz chamada `test-group`, com uma matriz de grupos de teste. Esses valores correspondem aos nomes dos grupos de teste que serão executados por `npm test`. +Creates a matrix named `test-group`, with an array of test groups. These values match the names of test groups that will be run by `npm test`.
-Agrupa todas as etapas que serão executadas durante o trabalho `test`. Cada trabalho em um fluxo de trabalho tem a própria seção `steps`. +Groups together all the steps that will run as part of the `test` job. Each job in a workflow has its own `steps` section.
-A palavra-chave `uses` informa que o trabalho deve recuperar a ação chamada `actions/checkout`. Esta é uma ação que verifica seu repositório e o faz o download do runner, permitindo que você execute ações contra seu código (como, por exemplo, ferramentas de teste). Você deve usar a ação de checkout sempre que o fluxo de trabalho for executado no código do repositório ou você estiver usando uma ação definida no repositório. Algumas opções extras são fornecidas para a ação usando a chave `with`. +The `uses` keyword tells the job to retrieve the action named `actions/checkout`. This is an action that checks out your repository and downloads it to the runner, allowing you to run actions against your code (such as testing tools). You must use the checkout action any time your workflow will run against the repository's code or you are using an action defined in the repository. Some extra options are provided to the action using the `with` key.
-Se o repositório atual for o `github/docs-internal`, esta etapa usará a ação `actions/github-script` para executar um script e verificar se há um branch chamado `docs-early-access`. +If the current repository is the `github/docs-internal` repository, this step uses the `actions/github-script` action to run a script to check if there is a branch called `docs-early-access`.
-Se o repositório atual for o `github/docs-internal`, esta etapa verificará o branch do `github/docs-early-access` que foi identificado na etapa anterior. +If the current repository is the `github/docs-internal` repository, this step checks out the branch from the `github/docs-early-access` that was identified in the previous step.
@@ -514,7 +520,7 @@ Se o repositório atual for o `github/docs-internal`, esta etapa verificará o b -Se o repositório atual for o `github/docs-internal`, esta etapa usará a palavra-chave `run` para executar comandos do shell para mover as pastas do repositório `docs-early-access` para as pastas do repositório principal. +If the current repository is the `github/docs-internal` repository, this step uses the `run` keyword to execute shell commands to move the `docs-early-access` repository's folders into the main repository's folders.
-Esta etapa executa um comando para fazer check-out de objetos LFS do repositório. +This step runs a command to check out LFS objects from the repository.
-Esta etapa usa a ação `trilom/file-changes-action` para reunir os arquivos alterados na solicitação de pull, para que eles possam ser analisados na próxima etapa. Este exemplo é fixado a uma versão específica da ação, usando o SHA `a6ca26c14274c33b15e6499323aac178af06ad4b`. +This step uses the `trilom/file-changes-action` action to gather the files changed in the pull request, so they can be analyzed in the next step. This example is pinned to a specific version of the action, using the `a6ca26c14274c33b15e6499323aac178af06ad4b` SHA.
-Esta etapa executa um comando do shell que usa uma saída da etapa anterior para criar um arquivo contendo a lista de arquivos alterados na solicitação de pull. +This step runs a shell command that uses an output from the previous step to create a file containing the list of files changed in the pull request.
-Essa etapa usa a ação `actions/setup-node` para instalar a versão especificada do pacote de software `node` no executor, o que permite que você acesse o comando `npm`. +This step uses the `actions/setup-node` action to install the specified version of the `node` software package on the runner, which gives you access to the `npm` command.
-Esta etapa executa o comando do shell `npm ci` para instalar os pacotes de software npm do projeto. +This step runs the `npm ci` shell command to install the npm software packages for the project.
-Esta etapa usa a ação `actions/cache` para armazenar em cache o build Next.js, para que o fluxo de trabalho tente recuperar um cache do build e não recriá-lo do zero sempre. Para obter mais informações, confira "[Como armazenar dependências em cache para acelerar os fluxos de trabalho](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)". +This step uses the `actions/cache` action to cache the Next.js build, so that the workflow will attempt to retrieve a cache of the build, and not rebuild it from scratch every time. For more information, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)."
-Esta etapa executa o script de build. +This step runs the build script.
-Esta etapa executa os testes usando `npm test`e a matriz de teste fornece um valor diferente de {% raw %}`${{ matrix.test-group }}`{% endraw %} para cada trabalho na matriz. Ela usa a variável de ambiente `DIFF_FILE` para saber quais arquivos foram alterados e usa a variável de ambiente `CHANGELOG_CACHE_FILE_PATH` para o arquivo de cache do changelog. +This step runs the tests using `npm test`, and the test matrix provides a different value for {% raw %}`${{ matrix.test-group }}`{% endraw %} for each job in the matrix. It uses the `DIFF_FILE` environment variable to know which files have changed, and uses the `CHANGELOG_CACHE_FILE_PATH` environment variable for the changelog cache file.
-## Próximas etapas +## Next steps {% data reusables.actions.learning-actions %} diff --git a/translations/pt-BR/content/actions/examples/using-the-github-cli-on-a-runner.md b/translations/pt-BR/content/actions/examples/using-the-github-cli-on-a-runner.md index 829842d5f7..351014a933 100644 --- a/translations/pt-BR/content/actions/examples/using-the-github-cli-on-a-runner.md +++ b/translations/pt-BR/content/actions/examples/using-the-github-cli-on-a-runner.md @@ -1,7 +1,7 @@ --- -title: Usando a CLI do GitHub em um executor -shortTitle: Using the GitHub CLI on a runner -intro: 'Como usar recursos avançados do {% data variables.product.prodname_actions %} para CI (integração contínua).' +title: Using the GitHub CLI on a runner +shortTitle: Use the GitHub CLI on a runner +intro: 'How to use advanced {% data variables.product.prodname_actions %} features for continuous integration (CI).' versions: fpt: '*' ghes: '> 3.1' @@ -10,32 +10,38 @@ versions: type: how_to topics: - Workflows -ms.openlocfilehash: cd731804c1e1c0c36ca95a30c6b7e9e074de030b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146749534' --- + {% data reusables.actions.enterprise-github-hosted-runners %} -## Visão geral de exemplo +## Example overview -{% data reusables.actions.example-workflow-intro-ci %} Quando esse fluxo de trabalho é disparado, ele executa automaticamente um script que verifica se o site {% data variables.product.prodname_dotcom %} Docs tem links desfeitos. Quando são encontrados links desfeitos, o fluxo de trabalho usa a CLI do {% data variables.product.prodname_dotcom %} para criar um problema do {% data variables.product.prodname_dotcom %} com os detalhes. +{% data reusables.actions.example-workflow-intro-ci %} When this workflow is triggered, it automatically runs a script that checks whether the {% data variables.product.prodname_dotcom %} Docs site has any broken links. If any broken links are found, the workflow uses the {% data variables.product.prodname_dotcom %} CLI to create a {% data variables.product.prodname_dotcom %} issue with the details. {% data reusables.actions.example-diagram-intro %} -![Diagrama de visão geral das etapas do fluxo de trabalho](/assets/images/help/images/overview-actions-using-cli-ci-example.png) +![Overview diagram of workflow steps](/assets/images/help/images/overview-actions-using-cli-ci-example.png) -## Recursos usados neste exemplo +## Features used in this example {% data reusables.actions.example-table-intro %} -| **Recurso** | **Implementação** | +| **Feature** | **Implementation** | | --- | --- | -{% data reusables.actions.cron-table-entry %} {% data reusables.actions.permissions-table-entry %} {% data reusables.actions.if-conditions-table-entry %} {% data reusables.actions.secrets-table-entry %} {% data reusables.actions.checkout-action-table-entry %} {% data reusables.actions.setup-node-table-entry %} | Como usar uma ação de terceiros: | [`peter-evans/create-issue-from-file`](https://github.com/peter-evans/create-issue-from-file)| | Como executar comandos do shell no executor: | [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) | | Como executar um script no executor: | Como usar `script/check-english-links.js` | | Como gerar um arquivo de saída: | Como direcionar a saída usando o operador `>` | | Como verificar se há problemas usando a {% data variables.product.prodname_cli %}: | [`gh issue list`](https://cli.github.com/manual/gh_issue_list) | | Como comentar em um problema usando a {% data variables.product.prodname_cli %}: | [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) | +{% data reusables.actions.cron-table-entry %} +{% data reusables.actions.permissions-table-entry %} +{% data reusables.actions.if-conditions-table-entry %} +{% data reusables.actions.secrets-table-entry %} +{% data reusables.actions.checkout-action-table-entry %} +{% data reusables.actions.setup-node-table-entry %} +| Using a third-party action: | [`peter-evans/create-issue-from-file`](https://github.com/peter-evans/create-issue-from-file)| +| Running shell commands on the runner: | [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) | +| Running a script on the runner: | Using `script/check-english-links.js` | +| Generating an output file: | Piping the output using the `>` operator | +| Checking for existing issues using {% data variables.product.prodname_cli %}: | [`gh issue list`](https://cli.github.com/manual/gh_issue_list) | +| Commenting on an issue using {% data variables.product.prodname_cli %}: | [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) | -## Fluxo de trabalho de exemplo +## Example workflow {% data reusables.actions.example-docs-engineering-intro %} [`check-all-english-links.yml`](https://github.com/github/docs/blob/main/.github/workflows/check-all-english-links.yml). @@ -103,7 +109,11 @@ jobs: - if: {% raw %}${{ failure() }}{% endraw %} name: Get title for issue id: check +{%- ifversion actions-save-state-set-output-envs %} + run: echo "title=$(head -1 broken_links.md)" >> $GITHUB_OUTPUT +{%- else %} run: echo "::set-output name=title::$(head -1 broken_links.md)" +{%- endif %} - if: {% raw %}${{ failure() }}{% endraw %} name: Create issue from file id: broken-link-report @@ -168,15 +178,15 @@ jobs: -## Compreendendo o exemplo +## Understanding the example {% data reusables.actions.example-explanation-table-intro %} - - + + @@ -204,10 +214,10 @@ on: @@ -221,7 +231,7 @@ permissions: @@ -233,7 +243,7 @@ jobs: @@ -246,7 +256,7 @@ Agrupa todos os trabalhos executados no arquivo de fluxo de trabalho. @@ -258,7 +268,7 @@ if: github.repository == 'github/docs-internal' @@ -270,7 +280,7 @@ runs-on: ubuntu-latest @@ -286,7 +296,7 @@ Configura o trabalho a ser executado em um executor do Ubuntu Linux. Isto signif @@ -298,7 +308,7 @@ Cria variáveis de ambiente personalizadas e redefine a variável interna `GITHU @@ -311,7 +321,7 @@ Agrupa todas as etapas que serão executadas durante o trabalho `check_all_engli @@ -327,7 +337,7 @@ A palavra-chave `uses` informa que o trabalho deve recuperar a ação chamada `a @@ -342,7 +352,7 @@ Essa etapa usa a ação `actions/setup-node` para instalar a versão especificad @@ -356,7 +366,7 @@ A palavra-chave `run` instrui o trabalho a executar um comando no executor. Ness @@ -366,12 +376,16 @@ Esse comando `run` executa um script que é armazenado no repositório em `scrip - if: {% raw %}${{ failure() }}{% endraw %} name: Get title for issue id: check +{%- ifversion actions-save-state-set-output-envs %} + run: echo "title=$(head -1 broken_links.md)" >> $GITHUB_OUTPUT +{%- else %} run: echo "::set-output name=title::$(head -1 broken_links.md)" +{%- endif %} ``` @@ -393,7 +407,7 @@ Se o script `check-english-links.js` detectar links desfeitos e retornar um stat @@ -421,9 +435,9 @@ Usa a ação `peter-evans/create-issue-from-file` para criar um problema do {% d @@ -441,7 +455,7 @@ Depois, [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) é @@ -462,16 +476,16 @@ Se um problema de uma execução anterior estiver aberto e atribuído a alguém,
CódigoExplicaçãoCodeExplanation
-Define `workflow_dispatch` e `scheduled` como gatilhos para o fluxo de trabalho: +Defines the `workflow_dispatch` and `scheduled` as triggers for the workflow: -* O `workflow_dispatch` permite executar manualmente esse fluxo de trabalho por meio da interface do usuário. Para obter mais informações, confira [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch). -* O evento `schedule` permite que você use a sintaxe `cron` para definir um intervalo regular para disparar automaticamente o fluxo de trabalho. Para obter mais informações, confira [`schedule`](/actions/reference/events-that-trigger-workflows#schedule). +* The `workflow_dispatch` lets you manually run this workflow from the UI. For more information, see [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch). +* The `schedule` event lets you use `cron` syntax to define a regular interval for automatically triggering the workflow. For more information, see [`schedule`](/actions/reference/events-that-trigger-workflows#schedule).
-Modifica as permissões padrão concedidas a `GITHUB_TOKEN`. Isso variará dependendo das necessidades do fluxo de trabalho. Para obter mais informações, confira "[Como atribuir permissões a trabalhos](/actions/using-jobs/assigning-permissions-to-jobs)". +Modifies the default permissions granted to `GITHUB_TOKEN`. This will vary depending on the needs of your workflow. For more information, see "[Assigning permissions to jobs](/actions/using-jobs/assigning-permissions-to-jobs)."
-Agrupa todos os trabalhos executados no arquivo de fluxo de trabalho. +Groups together all the jobs that run in the workflow file.
-Define um trabalho com a ID `check_all_english_links` e o nome `Check all links`, armazenados dentro da chave `jobs`. +Defines a job with the ID `check_all_english_links`, and the name `Check all links`, that is stored within the `jobs` key.
-O trabalho `check_all_english_links` só será executado se o repositório chamar `docs-internal` e estiver dentro da organização `github`. Caso contrário, o trabalho será marcado como _ignorado_. +Only run the `check_all_english_links` job if the repository is named `docs-internal` and is within the `github` organization. Otherwise, the job is marked as _skipped_.
-Configura o trabalho a ser executado em um executor do Ubuntu Linux. Isto significa que o trabalho será executado em uma nova máquina virtual hospedada pelo {% data variables.product.prodname_dotcom %}. Para ver exemplos de sintaxe que usam outros executores, confira "[Sintaxe de fluxo de trabalho do {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)". +Configures the job to run on an Ubuntu Linux runner. This means that the job will execute on a fresh virtual machine hosted by {% data variables.product.prodname_dotcom %}. For syntax examples using other runners, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
-Cria variáveis de ambiente personalizadas e redefine a variável interna `GITHUB_TOKEN` para usar um [segredo](/actions/security-guides/encrypted-secrets) personalizado. Essas variáveis serão referenciadas mais tarde no fluxo de trabalho. +Creates custom environment variables, and redefines the built-in `GITHUB_TOKEN` variable to use a custom [secret](/actions/security-guides/encrypted-secrets). These variables will be referenced later in the workflow.
-Agrupa todas as etapas que serão executadas durante o trabalho `check_all_english_links`. Cada trabalho no fluxo de trabalho tem a própria seção `steps`. +Groups together all the steps that will run as part of the `check_all_english_links` job. Each job in the workflow has its own `steps` section.
-A palavra-chave `uses` informa que o trabalho deve recuperar a ação chamada `actions/checkout`. Esta é uma ação que verifica seu repositório e o faz o download do runner, permitindo que você execute ações contra seu código (como, por exemplo, ferramentas de teste). Você deve usar a ação de checkout sempre que o fluxo de trabalho for executado no código do repositório ou você estiver usando uma ação definida no repositório. +The `uses` keyword tells the job to retrieve the action named `actions/checkout`. This is an action that checks out your repository and downloads it to the runner, allowing you to run actions against your code (such as testing tools). You must use the checkout action any time your workflow will run against the repository's code or you are using an action defined in the repository.
-Essa etapa usa a ação `actions/setup-node` para instalar a versão especificada do pacote de software `node` no executor, o que permite que você acesse o comando `npm`. +This step uses the `actions/setup-node` action to install the specified version of the `node` software package on the runner, which gives you access to the `npm` command.
-A palavra-chave `run` instrui o trabalho a executar um comando no executor. Nesse caso, os comandos `npm ci` e `npm run build` são executados como etapas separadas para instalar e compilar o aplicativo Node.js no repositório. +The `run` keyword tells the job to execute a command on the runner. In this case, the `npm ci` and `npm run build` commands are run as separate steps to install and build the Node.js application in the repository.
-Esse comando `run` executa um script que é armazenado no repositório em `script/check-english-links.js` e direciona a saída para um arquivo chamado `broken_links.md`. +This `run` command executes a script that is stored in the repository at `script/check-english-links.js`, and pipes the output to a file called `broken_links.md`.
-Se o script `check-english-links.js` detectar links desfeitos e retornar um status de saída diferente de zero (falha), use um [comando de fluxo de trabalho](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter) para definir uma saída que tenha o valor da primeira linha do arquivo `broken_links.md` (usado na próxima etapa). +If the `check-english-links.js` script detects broken links and returns a non-zero (failure) exit status, then use a [workflow command](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter) to set an output that has the value of the first line of the `broken_links.md` file (this is used the next step).
-Usa a ação `peter-evans/create-issue-from-file` para criar um problema do {% data variables.product.prodname_dotcom %}. Este exemplo é fixado a uma versão específica da ação, usando o SHA `b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e`. +Uses the `peter-evans/create-issue-from-file` action to create a new {% data variables.product.prodname_dotcom %} issue. This example is pinned to a specific version of the action, using the `b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e` SHA.
-Usa [`gh issue list`](https://cli.github.com/manual/gh_issue_list) para localizar o problema que já foi criado de execuções anteriores. O [alias](https://cli.github.com/manual/gh_alias_set) `gh list-reports` é usado para simplificar o processamento nas próximas etapas. Para obter a URL do problema, a expressão `jq` processa a saída JSON resultante. +Uses [`gh issue list`](https://cli.github.com/manual/gh_issue_list) to locate the previously created issue from earlier runs. This is [aliased](https://cli.github.com/manual/gh_alias_set) to `gh list-reports` for simpler processing in later steps. To get the issue URL, the `jq` expression processes the resulting JSON output. -Depois, [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) é usado para adicionar um comentário ao novo problema vinculado ao anterior. +[`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) is then used to add a comment to the new issue that links to the previous one.
-Se um problema de uma execução anterior estiver aberto e atribuído a alguém, use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) para adicionar um comentário com um link para o novo problema. +If an issue from a previous run is open and assigned to someone, then use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) to add a comment with a link to the new issue.
-Se um problema de uma execução anterior estiver aberto e não estiver atribuído a ninguém: +If an issue from a previous run is open and is not assigned to anyone, then: -* Use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) para adicionar um comentário com um link para o novo problema. -* Use [`gh issue close`](https://cli.github.com/manual/gh_issue_close) para fechar o problema antigo. -* Use [`gh issue edit`](https://cli.github.com/manual/gh_issue_edit) para editar o problema antigo a fim de removê-lo de um quadro de projeto do {% data variables.product.prodname_dotcom %}. +* Use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) to add a comment with a link to the new issue. +* Use [`gh issue close`](https://cli.github.com/manual/gh_issue_close) to close the old issue. +* Use [`gh issue edit`](https://cli.github.com/manual/gh_issue_edit) to edit the old issue to remove it from a specific {% data variables.product.prodname_dotcom %} project board.
-## Próximas etapas +## Next steps {% data reusables.actions.learning-actions %} 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 79bbe18b9c..f66ea675e4 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 @@ -17,7 +17,7 @@ type: overview ## About self-hosted runners -A self-hosted runner is a system that you deploy and manage to execute jobs from {% data variables.product.prodname_actions %} on {% ifversion ghae or ghec %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For more information about {% data variables.product.prodname_actions %}, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions){% ifversion fpt %}."{% elsif ghec or ghes or ghae %}" and "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."{% endif %} +A self-hosted runner is a system that you deploy and manage to execute jobs from {% data variables.product.prodname_actions %} on {% ifversion ghae or ghec %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For more information about {% data variables.product.prodname_actions %}, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions){% ifversion fpt %}."{% elsif ghec or ghes or ghae %}" and "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."{% endif %} {% data reusables.actions.self-hosted-runner-description %} {% data reusables.actions.self-hosted-runner-locations %} @@ -143,14 +143,14 @@ The self-hosted runner connects to {% data variables.product.product_name %} to {% data reusables.actions.self-hosted-runner-ports-protocols %} {% ifversion fpt or ghec %} -Since the self-hosted runner opens a connection to {% data variables.product.product_location %}, you do not need to allow {% data variables.product.prodname_dotcom %} to make inbound connections to your self-hosted runner. +Since the self-hosted runner opens a connection to {% data variables.location.product_location %}, you do not need to allow {% data variables.product.prodname_dotcom %} to make inbound connections to your self-hosted runner. {% elsif ghes or ghae %} -Only an outbound connection from the runner to {% data variables.product.product_location %} is required. There is no need for an inbound connection from {% data variables.product.product_location %} to the runner. +Only an outbound connection from the runner to {% data variables.location.product_location %} is required. There is no need for an inbound connection from {% data variables.location.product_location %} to the runner. {%- endif %} {% ifversion ghes %} -{% data variables.product.product_name %} must accept inbound connections from your runners over {% ifversion ghes %}HTTP(S){% else %}HTTPS{% endif %} at {% data variables.product.product_location %}'s hostname and API subdomain, and your runners must allow outbound connections over {% ifversion ghes %}HTTP(S){% else %}HTTPS{% endif %} to {% data variables.product.product_location %}'s hostname and API subdomain. +{% data variables.product.product_name %} must accept inbound connections from your runners over {% ifversion ghes %}HTTP(S){% else %}HTTPS{% endif %} at {% data variables.location.product_location %}'s hostname and API subdomain, and your runners must allow outbound connections over {% ifversion ghes %}HTTP(S){% else %}HTTPS{% endif %} to {% data variables.location.product_location %}'s hostname and API subdomain. {% elsif ghae %} @@ -217,7 +217,7 @@ If you use an IP address allow list for your {% data variables.product.prodname_ {% else %} -{% ifversion ghes %}Self-hosted runners do not require any external internet access in order to function. As a result, you can use network routing to direct communication between the self-hosted runner and {% data variables.product.product_location %}. For example, you can assign a private IP address to your self-hosted runner and configure routing to send traffic to {% data variables.product.product_location %}, with no need for traffic to traverse a public network.{% endif %} +{% ifversion ghes %}Self-hosted runners do not require any external internet access in order to function. As a result, you can use network routing to direct communication between the self-hosted runner and {% data variables.location.product_location %}. For example, you can assign a private IP address to your self-hosted runner and configure routing to send traffic to {% data variables.location.product_location %}, with no need for traffic to traverse a public network.{% endif %} {% endif %} @@ -233,7 +233,7 @@ For more information about troubleshooting common network connectivity issues, s ## Communication between self-hosted runners and {% data variables.product.prodname_dotcom_the_website %} -Self-hosted runners do not need to connect to {% data variables.product.prodname_dotcom_the_website %} unless you have enabled automatic access to {% data variables.product.prodname_dotcom_the_website %} actions for {% data variables.product.product_location %}. For more information, see "[About using actions in your enterprise](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)." +Self-hosted runners do not need to connect to {% data variables.product.prodname_dotcom_the_website %} unless you have enabled automatic access to {% data variables.product.prodname_dotcom_the_website %} actions for {% data variables.location.product_location %}. For more information, see "[About using actions in your enterprise](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)." If you have enabled automatic access to {% data variables.product.prodname_dotcom_the_website %} actions, then the self-hosted runner will connect directly to {% data variables.product.prodname_dotcom_the_website %} to download actions. You must ensure that the machine has the appropriate network access to communicate with the {% data variables.product.prodname_dotcom %} URLs listed below. diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md index 7ef4f6bfeb..0e597853c7 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md @@ -1,6 +1,6 @@ --- -title: Monitorar e solucionar problemas de executores auto-hospedados -intro: Você pode monitorar seus executores auto-hospedados para visualizar sua atividade e diagnosticar problemas comuns. +title: Monitoring and troubleshooting self-hosted runners +intro: You can monitor your self-hosted runners to view their activity and diagnose common issues. redirect_from: - /actions/hosting-your-own-runners/checking-the-status-of-self-hosted-runners - /github/automating-your-workflow-with-github-actions/checking-the-status-of-self-hosted-runners @@ -11,117 +11,119 @@ versions: ghae: '*' ghec: '*' type: tutorial +miniTocMaxHeadingLevel: 3 defaultPlatform: linux shortTitle: Monitor & troubleshoot -ms.openlocfilehash: 57ca9cad51c1936171fcadd73497cf313dd86dd7 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147065631' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## Como verificar o status de um executor auto-hospedado +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## Checking the status of a self-hosted runner {% data reusables.actions.self-hosted-runner-management-permissions-required %} -{% data reusables.actions.self-hosted-runner-navigate-repo-and-org %} {% data reusables.organizations.settings-sidebar-actions-runners %} -1. Em "Executores", você pode ver uma lista de executores registrados, incluindo o nome, etiqueta e status do executor. +{% data reusables.actions.self-hosted-runner-navigate-repo-and-org %} +{% data reusables.organizations.settings-sidebar-actions-runners %} +1. Under "Runners", you can view a list of registered runners, including the runner's name, labels, and status. - O status pode ser um dos seguintes: + The status can be one of the following: - * **Ocioso**: o executor está conectado ao {% data variables.product.product_name %} e está pronto para executar trabalhos. - * **Ativo**: o executor está executando um trabalho no momento. - * **Offline**: o executor não está conectado ao {% data variables.product.product_name %}. Isto pode ser porque a máquina está off-line, o aplicativo do executor auto-hospedado não está funcionando na máquina, ou o aplicativo do executor auto-hospedado não pode comunicar-se com {% data variables.product.product_name %}. + * **Idle**: The runner is connected to {% data variables.product.product_name %} and is ready to execute jobs. + * **Active**: The runner is currently executing a job. + * **Offline**: The runner is not connected to {% data variables.product.product_name %}. This could be because the machine is offline, the self-hosted runner application is not running on the machine, or the self-hosted runner application cannot communicate with {% data variables.product.product_name %}. -## Solução de problemas da conectividade de rede +## Troubleshooting network connectivity -### Verificando conectividade de rede do executor auto-hospedado +### Checking self-hosted runner network connectivity -Use o script `run` do aplicativo do executor auto-hospedado com o parâmetro `--check` para verificar se um executor auto-hospedado pode acessar todos os serviços de rede necessários no {% data variables.product.product_location %}. +You can use the self-hosted runner application's `run` script with the `--check` parameter to check that a self-hosted runner can access all required network services on {% data variables.location.product_location %}. -Além de `--check`, você precisa fornecer dois argumentos para o script: +In addition to `--check`, you must provide two arguments to the script: -* `--url` pela URL para o repositório do repositório, da organização ou da empresa do {% data variables.product.company_short %}. Por exemplo, `--url https://github.com/octo-org/octo-repo`. -* `--pat` pelo valor de um token de acesso pessoal, que precisa ter o escopo `workflow`. Por exemplo, `--pat ghp_abcd1234`. Para obter mais informações, confira "[Como criar um token de acesso pessoal](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)". +* `--url` with the URL to your {% data variables.product.company_short %} repository, organization, or enterprise. For example, `--url https://github.com/octo-org/octo-repo`. +* `--pat` with the value of a {% data variables.product.pat_v1 %}, which must have the `workflow` scope{% ifversion pat-v2%}, or a {% data variables.product.pat_v2 %} with workflows read and write access {% endif %}. For example, `--pat ghp_abcd1234`. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." -Por exemplo: +For example: {% mac %} {% data reusables.actions.self-hosted-runner-check-mac-linux %} -{% endmac %} {% linux %} +{% endmac %} +{% linux %} {% data reusables.actions.self-hosted-runner-check-mac-linux %} -{% endlinux %} {% windows %} +{% endlinux %} +{% windows %} ```shell -run.cmd --check --url https://github.com/octo-org/octo-repo --pat ghp_abcd1234 +run.cmd --check --url https://github.com/YOUR-ORG/YOUR-REPO --pat GHP_ABCD1234 ``` {% endwindows %} -O script testa cada serviço e gera um `PASS` ou um `FAIL` para cada um. Se você tiver alguma verificação com falha, você pode ver mais detalhes sobre o problema no arquivo de registro para a verificação. Os arquivos de log estão localizados no diretório `_diag` em que você instalou o aplicativo do executor, e o caminho do arquivo de log para cada verificação é mostrado na saída do console do script. +The script tests each service, and outputs either a `PASS` or `FAIL` for each one. If you have any failing checks, you can see more details on the problem in the log file for the check. The log files are located in the `_diag` directory where you installed the runner application, and the path of the log file for each check is shown in the console output of the script. -Se você tiver alguma verificação com falha, você deve também verificar se a sua máquina de executores auto-hospedada cumpre todos os requisitos de comunicação. Para obter mais informações, confira "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-requirements)". +If you have any failing checks, you should also verify that your self-hosted runner machine meets all the communication requirements. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-requirements)." -### Desabilitando verificação de certificado TLS -{% ifversion ghes %} Por padrão, o aplicativo do executor auto-hospedado verifica o certificado TLS do {% data variables.product.product_name %}. Se o seu {% data variables.product.product_name %} tiver um certificado autoassinado ou emitido internamente, você deverá desabilitar a verificação de certificado TLS para fins de teste. -{% else %} Por padrão, o aplicativo do executor auto-hospedado verifica o certificado TLS do {% data variables.product.product_name %}. Se você encontrar problemas de rede, você deverá desabilitar a verificação de certificado TLS para fins de teste. +### Disabling TLS certificate verification +{% ifversion ghes %} +By default, the self-hosted runner application verifies the TLS certificate for {% data variables.product.product_name %}. If your {% data variables.product.product_name %} has a self-signed or internally-issued certificate, you may wish to disable TLS certificate verification for testing purposes. +{% else %} +By default, the self-hosted runner application verifies the TLS certificate for {% data variables.product.product_name %}. If you encounter network problems, you may wish to disable TLS certificate verification for testing purposes. {% endif %} -Para desabilitar a verificação de certificação TLS no aplicativo do executor auto-hospedado, defina a variável de ambiente `GITHUB_ACTIONS_RUNNER_TLS_NO_VERIFY` como `1` antes de configurar e executar o aplicativo do executor auto-hospedado. +To disable TLS certification verification in the self-hosted runner application, set the `GITHUB_ACTIONS_RUNNER_TLS_NO_VERIFY` environment variable to `1` before configuring and running the self-hosted runner application. ```shell export GITHUB_ACTIONS_RUNNER_TLS_NO_VERIFY=1 -./config.sh --url https://github.com/octo-org/octo-repo --token +./config.sh --url https://github.com/YOUR-ORG/YOUR-REPO --token ./run.sh ``` {% warning %} -**Aviso**: não recomendamos desabilitar a verificação do TLS, pois o TLS fornece privacidade e integridade de dados entre o aplicativo do executor auto-hospedado e o {% data variables.product.product_name %}. Recomendamos que você instale o certificado {% data variables.product.product_name %} no armazenamento de certificados do sistema operacional para o seu executor auto-hospedado. Para orientação sobre como instalar o certificado de {% data variables.product.product_name %}, verifique junti ao seu fornecedor de sistema operacional. +**Warning**: Disabling TLS verification is not recommended since TLS provides privacy and data integrity between the self-hosted runner application and {% data variables.product.product_name %}. We recommend that you install the {% data variables.product.product_name %} certificate in the operating system certificate store for your self-hosted runner. For guidance on how to install the {% data variables.product.product_name %} certificate, check with your operating system vendor. {% endwarning %} -## Revisar os arquivos de registro do aplicativo do executor auto-hospedado +## Reviewing the self-hosted runner application log files -Você pode monitorar o status do aplicativo do executor auto-hospedado e suas atividades. Os arquivos de log são mantidos no diretório `_diag` em que você instalou o aplicativo do executor, e um novo log é gerado sempre que o aplicativo é iniciado. O nome do arquivo começa com *Runner_* e é seguido de um carimbo de data/hora UTC da inicialização do aplicativo. +You can monitor the status of the self-hosted runner application and its activities. Log files are kept in the `_diag` directory where you installed the runner application, and a new log is generated each time the application is started. The filename begins with *Runner_*, and is followed by a UTC timestamp of when the application was started. -Para obter logs detalhados sobre as execuções do trabalho de fluxo de trabalho, confira a próxima seção que descreve os arquivos *Worker_* . +For detailed logs on workflow job executions, see the next section describing the *Worker_* files. -## Revisar o arquivo de registro de um trabalho +## Reviewing a job's log file -O aplicativo do executor auto-hospedado cria um arquivo de registro detalhado para cada trabalho que processa. Esses arquivos são armazenados no diretório `_diag` em que você instalou o aplicativo do executor, e o nome do arquivo começa com *Worker_* . +The self-hosted runner application creates a detailed log file for each job that it processes. These files are stored in the `_diag` directory where you installed the runner application, and the filename begins with *Worker_*. {% linux %} -## Usar journalctl para verificar o serviço do aplicativo do executor auto-hospedado +## Using journalctl to check the self-hosted runner application service -Para executores auto-hospedados baseados em Linux que executam o aplicativo usando um serviço, use `journalctl` para monitorar sua atividade em tempo real. O serviço padrão baseado em sistema usa a seguinte convenção de nomenclatura: `actions.runner.-..service`. Esse nome será truncado se exceder 80 caracteres, ou seja, a maneira preferencial de localizar o nome do serviço é verificando o arquivo _.service_. Por exemplo: +For Linux-based self-hosted runners running the application using a service, you can use `journalctl` to monitor their real-time activity. The default systemd-based service uses the following naming convention: `actions.runner.-..service`. This name is truncated if it exceeds 80 characters, so the preferred way of finding the service's name is by checking the _.service_ file. For example: ```shell $ cat ~/actions-runner/.service actions.runner.octo-org-octo-repo.runner01.service ``` -Se isso falhar devido ao serviço que está sendo instalado em outro lugar, você poderá encontrar o nome do serviço na lista de serviços em execução. Por exemplo, na maioria dos sistemas Linux, você pode usar o comando `systemctl`: +If this fails due to the service being installed elsewhere, you can find the service name in the list of running services. For example, on most Linux systems you can use the `systemctl` command: ```shell $ systemctl --type=service | grep actions.runner actions.runner.octo-org-octo-repo.hostname.service loaded active running GitHub Actions Runner (octo-org-octo-repo.hostname) ``` -Use `journalctl` para monitorar a atividade em tempo real do executor auto-hospedado: +You can use `journalctl` to monitor the real-time activity of the self-hosted runner: ```shell $ sudo journalctl -u actions.runner.octo-org-octo-repo.runner01.service -f ``` -Neste exemplo de saída, você pode ver `runner01` ser iniciado, receber um trabalho chamado `testAction` e exibir o status resultante: +In this example output, you can see `runner01` start, receive a job named `testAction`, and then display the resulting status: ```shell Feb 11 14:57:07 runner01 runsvc.sh[962]: Starting Runner listener with startup type: service @@ -133,23 +135,23 @@ Feb 11 16:06:54 runner01 runsvc.sh[962]: 2020-02-11 16:06:54Z: Running job: test Feb 11 16:07:10 runner01 runsvc.sh[962]: 2020-02-11 16:07:10Z: Job testAction completed with result: Succeeded ``` -Para ver a configuração `systemd`, localize o arquivo de serviço aqui: `/etc/systemd/system/actions.runner.-..service`. -Se você desejar personalizar o serviço de aplicação do executor auto-hospedado, não modifique esse arquivo diretamente. Siga as instruções descritas em "[Como configurar o aplicativo do executor auto-hospedado como um serviço](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service)". +To view the `systemd` configuration, you can locate the service file here: `/etc/systemd/system/actions.runner.-..service`. +If you want to customize the self-hosted runner application service, do not directly modify this file. Follow the instructions described in "[Configuring the self-hosted runner application as a service](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service)." {% endlinux %} {% mac %} -## Como usar `launchd` para verificar o serviço de aplicativo do executor auto-hospedado +## Using `launchd` to check the self-hosted runner application service -Para executores auto-hospedados baseados em macOS que executam o aplicativo como um serviço, use `launchctl` para monitorar sua atividade em tempo real. O serviço padrão baseado em inicialização usa a seguinte convenção de nomenclatura: `actions.runner.-.`. Esse nome será truncado se exceder 80 caracteres, ou seja, a maneira preferencial de localizar o nome do serviço é verificando o arquivo _.service_ no diretório do executor: +For macOS-based self-hosted runners running the application as a service, you can use `launchctl` to monitor their real-time activity. The default launchd-based service uses the following naming convention: `actions.runner.-.`. This name is truncated if it exceeds 80 characters, so the preferred way of finding the service's name is by checking the _.service_ file in the runner directory: ```shell % cat ~/actions-runner/.service /Users/exampleUsername/Library/LaunchAgents/actions.runner.octo-org-octo-repo.runner01.plist ``` -O script `svc.sh` usa `launchctl` para verificar se o aplicativo está em execução. Por exemplo: +The `svc.sh` script uses `launchctl` to check whether the application is running. For example: ```shell $ ./svc.sh status @@ -159,25 +161,25 @@ Started: 379 0 actions.runner.example.runner01 ``` -A saída resultante inclui a ID do processo e o nome do serviço `launchd` do aplicativo. +The resulting output includes the process ID and the name of the application’s `launchd` service. -Para ver a configuração `launchd`, localize o arquivo de serviço aqui: `/Users/exampleUsername/Library/LaunchAgents/actions.runner...service`. -Se você desejar personalizar o serviço de aplicação do executor auto-hospedado, não modifique esse arquivo diretamente. Siga as instruções descritas em "[Como configurar o aplicativo do executor auto-hospedado como um serviço](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service-1)". +To view the `launchd` configuration, you can locate the service file here: `/Users/exampleUsername/Library/LaunchAgents/actions.runner...service`. +If you want to customize the self-hosted runner application service, do not directly modify this file. Follow the instructions described in "[Configuring the self-hosted runner application as a service](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service-1)." {% endmac %} {% windows %} -## Usar PowerShell para verificar o serviço do aplicativo do executor auto-hospedado +## Using PowerShell to check the self-hosted runner application service -Para executores auto-hospedados baseados no Windows que executam o aplicativo como um serviço, você pode usar o PowerShell para monitorar suas atividades em tempo real. O serviço usa a convenção de nomenclatura `GitHub Actions Runner (-.)`. Você também pode encontrar o nome do serviço verificando o arquivo _.service_ no diretório do executor: +For Windows-based self-hosted runners running the application as a service, you can use PowerShell to monitor their real-time activity. The service uses the naming convention `GitHub Actions Runner (-.)`. You can also find the service's name by checking the _.service_ file in the runner directory: ```shell PS C:\actions-runner> Get-Content .service actions.runner.octo-org-octo-repo.runner01.service ``` -Veja o status do executor no aplicativo _Serviços_ do Windows (`services.msc`). Você também pode usar o PowerShell para verificar se o serviço está sendo executado: +You can view the status of the runner in the Windows _Services_ application (`services.msc`). You can also use PowerShell to check whether the service is running: ```shell PS C:\actions-runner> Get-Service "actions.runner.octo-org-octo-repo.runner01.service" | Select-Object Name, Status @@ -186,7 +188,7 @@ Name Status actions.runner.octo-org-octo-repo.runner01.service Running ``` -Você pode usar o PowerShell para verificar a atividade recente do executor auto-hospedado. Neste exemplo de saída, você pode ver o aplicativo ser iniciado, receber um trabalho chamado `testAction` e exibir o status resultante: +You can use PowerShell to check the recent activity of the self-hosted runner. In this example output, you can see the application start, receive a job named `testAction`, and then display the resulting status: ```shell PS C:\actions-runner> Get-EventLog -LogName Application -Source ActionsRunnerService @@ -205,34 +207,34 @@ PS C:\actions-runner> Get-EventLog -LogName Application -Source ActionsRunnerSer {% endwindows %} -## Monitorar o processo de atualização automática +## Monitoring the automatic update process -Recomendamos que você verifique regularmente o processo de atualização automática, uma vez que o executor auto-hospedado não será capaz de processar os trabalhos se estiver abaixo de um determinado limite de versão. O aplicativo do executor auto-hospedado atualiza-se, mas mas observe que este processo não inclui atualizações do sistema operacional ou de outro software. Será necessário que você gerencie essas atualizações separadamente. +We recommend that you regularly check the automatic update process, as the self-hosted runner will not be able to process jobs if it falls below a certain version threshold. The self-hosted runner application automatically updates itself, but note that this process does not include any updates to the operating system or other software; you will need to separately manage these updates. -Veja as atividades de atualização nos arquivos de log *Runner_* . Por exemplo: +You can view the update activities in the *Runner_* log files. For example: ```shell [Feb 12 12:37:07 INFO SelfUpdater] An update is available. ``` -Além disso, encontre mais informações nos arquivos de log _SelfUpdate_ localizados no diretório `_diag` em que você instalou o aplicativo do executor. +In addition, you can find more information in the _SelfUpdate_ log files located in the `_diag` directory where you installed the runner application. {% linux %} -## Resolução de problemas de contêineres em executores auto-hospedados +## Troubleshooting containers in self-hosted runners -### Verificar se o Docker está instalado +### Checking that Docker is installed -Se seus trabalhos exigirem contêineres, o executor auto-hospedado deverá ser baseado no Linux e deverá ter o Docker instalado. Verifique se o seu executor auto-hospedado tem o Docker instalado e se o serviço está em execução. +If your jobs require containers, then the self-hosted runner must be Linux-based and needs to have Docker installed. Check that your self-hosted runner has Docker installed and that the service is running. -Use `systemctl` para verificar o status do serviço: +You can use `systemctl` to check the service status: ```shell $ sudo systemctl is-active docker.service active ``` -Se o Docker não estiver instalado, ações dependentes irão falhar com as seguintes mensagens de erro: +If Docker is not installed, then dependent actions will fail with the following errors: ```shell [2020-02-13 16:56:10Z INFO DockerCommandManager] Which: 'docker' @@ -240,15 +242,15 @@ Se o Docker não estiver instalado, ações dependentes irão falhar com as segu [2020-02-13 16:56:10Z ERR StepsRunner] Caught exception from step: System.IO.FileNotFoundException: File not found: 'docker' ``` -### Verificar as permissões do Docker +### Checking the Docker permissions -Se seu trabalho falhar com o seguinte erro: +If your job fails with the following error: ```shell dial unix /var/run/docker.sock: connect: permission denied ``` -Verifique se a conta de serviço do executor auto-hospedado tem permissão para usar o serviço do Docker. Identifique essa conta verificando a configuração do executor auto-hospedado em `systemd`. Por exemplo: +Check that the self-hosted runner's service account has permission to use the Docker service. You can identify this account by checking the configuration of the self-hosted runner in `systemd`. For example: ```shell $ sudo systemctl show -p User actions.runner.octo-org-octo-repo.runner01.service @@ -258,9 +260,26 @@ User=runner-user {% endlinux %} {% ifversion ghes %} -## Resolvendo executores que estão offline após uma atualização de {% data variables.product.product_location %} +## Resolving runners that are offline after an upgrade of {% data variables.location.product_location %} {% data reusables.actions.upgrade-runners-before-upgrade-ghes %} -Se os executores estiverem offline por esse motivo, atualize-os manualmente. Para saber mais, confira as instruções de instalação para [a versão mais recente](https://github.com/actions/runner/releases/latest) no repositório ações/executor. +If your runners are offline for this reason, manually update the runners. For more information, see the installation instructions for [the latest release](https://github.com/actions/runner/releases/latest) in the actions/runner repository. {% endif %} + +### Checking which Docker engine is installed on the runner + +If your build fails with the following error: + +```shell +Error: Input required and not supplied: java-version +``` + +Check which Docker engine is installed on your self-hosted runner. To pass the inputs of an action into the Docker container, the runner uses environment variables that might contain dashes as part of their names. The action may not able to get the inputs if the Docker engine is not a binary executable, but is instead a shell wrapper or a link (for example, a Docker engine installed on Linux using `snap`). To address this error, configure your self-hosted runner to use a different Docker engine. + +To check if your Docker engine was installed using `snap`, use the `which` command. In the following example, the Docker engine was installed using `snap`: + +```shell +$ which docker +/snap/bin/docker +``` diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job.md b/translations/pt-BR/content/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job.md index d774ab7d10..ec7997a3c2 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job.md @@ -1,81 +1,76 @@ --- -title: Como executar scripts antes ou depois de um trabalho -intro: 'Os scripts podem ser executado automaticamente em um executor autohospedado, diretamente antes ou depois de um trabalho.' +title: Running scripts before or after a job +intro: 'Scripts can automatically execute on a self-hosted runner, directly before or after a job.' versions: feature: job-hooks-for-runners type: tutorial miniTocMaxHeadingLevel: 3 shortTitle: Run a script before or after a job -ms.openlocfilehash: 11b2f63cd70c5276f0626a6016593553d1bedd0c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147067647' --- -{% note %} - -**Observação**: atualmente, esse recurso está em versão beta e sujeito a alterações. - -{% endnote %} - -## Sobre os scripts pré e pós-trabalho - -Você pode executar scripts automaticamente em um executor auto-hospedado, antes da execução de um trabalho ou após a conclusão da execução dele. Use esses scripts para dar suporte aos requisitos do trabalho, como a criação ou a destruição de um ambiente de executor ou a limpeza de diretórios. Use também esses scripts para acompanhar a telemetria de como os executores são usados. - -Os scripts personalizados são disparados automaticamente quando uma variável de ambiente específica é definida no executor: a variável de ambiente precisa conter o caminho absoluto para o script. Para obter mais informações, confira "[Como disparar os scripts](#triggering-the-scripts)" abaixo. - -Há suporte para as seguintes linguagens de script: - -- **Bash**: usa `bash` e pode usar `sh` como alternativa. É executado com a execução de `-e {pathtofile}`. -- **PowerShell**: usa `pwsh` e pode usar `powershell` como alternativa. É executado com a execução de `-command \". '{pathtofile}'\"`. - -## Como escrever os scripts - -Seus scripts personalizados podem usar os seguintes recursos: - -- **Variáveis de ambiente**: os scripts têm acesso às variáveis de ambiente padrão. O conteúdo completo do evento de webhook pode ser encontrado em `GITHUB_EVENT_PATH`. Para obter mais informações, confira "[Variáveis de ambiente](/actions/learn-github-actions/environment-variables#default-environment-variables)". -- **Comandos de fluxo de trabalho**: os scripts podem usar comandos de fluxo de trabalho. Para obter mais informações, confira ["Comandos de fluxo de trabalho do {% data variables.product.prodname_actions %}"](/actions/using-workflows/workflow-commands-for-github-actions), com exceção de `save-state` e `set-output`, que não são compatíveis nesses scripts. Os scripts também podem usar arquivos de ambiente. Para obter mais informações, confira [Arquivos de ambiente](/actions/using-workflows/workflow-commands-for-github-actions#environment-files). {% note %} -**Observação**: evite usar os scripts para gerar informações confidenciais para o console, pois qualquer pessoa com acesso de leitura no repositório poderá ver a saída nos logs da interface do usuário. +**Note**: This feature is currently in beta and is subject to change. {% endnote %} -### Como tratar os códigos de saída +## About pre- and post-job scripts -Para scripts de pré-trabalho, o código de saída `0` indica que o script foi concluído com sucesso e o trabalho continuará sendo executado. Se houver outro código de saída, o trabalho não será executado e será marcado como com falha. Para ver os resultados dos scripts de pré-trabalho, verifique se há entradas `Set up runner` nos logs. Para obter mais informações sobre como verificar os logs, confira "[Como ver os logs para diagnosticar falhas](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)". +You can automatically execute scripts on a self-hosted runner, either before a job runs, or after a job finishes running. You could use these scripts to support the job's requirements, such as building or tearing down a runner environment, or cleaning out directories. You could also use these scripts to track telemetry of how your runners are used. -Não há suporte para a configuração [`continue-on-error`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idcontinue-on-error) para uso por esses scripts. +The custom scripts are automatically triggered when a specific environment variable is set on the runner; the environment variable must contain the absolute path to the script. For more information, see "[Triggering the scripts](#triggering-the-scripts)" below. -## Como disparar os scripts +The following scripting languages are supported: -Os scripts personalizados precisam estar localizados no executor, mas não precisam ser armazenados no diretório do aplicativo `actions-runner`. Os scripts são executados no contexto de segurança da conta de serviço que executa o serviço de executor. +- **Bash**: Uses `bash` and can fallback to `sh`. Executes by running `-e {pathtofile}`. +- **PowerShell**: Uses `pwsh` and can fallback to `powershell`. Executes by running `-command \". '{pathtofile}'\"`. + +## Writing the scripts + +Your custom scripts can use the following features: + +- **Environment variables**: Scripts have access to the default environment variables. The full webhook event payload can be found in `GITHUB_EVENT_PATH`. For more information, see "[Environment variables](/actions/learn-github-actions/environment-variables#default-environment-variables)." +- **Workflow commands**: Scripts can use workflow commands. For more information, see ["Workflow commands for {% data variables.product.prodname_actions %}"](/actions/using-workflows/workflow-commands-for-github-actions){% ifversion actions-save-state-set-output-envs %}{% else %}, with the exception of `save-state` and `set-output`, which are not supported by these scripts{% endif %}. Scripts can also use environment files. For more information, see [Environment files](/actions/using-workflows/workflow-commands-for-github-actions#environment-files). {% note %} -**Observação**: os scripts disparados são processados de maneira síncrona, ou seja, bloquearão a execução do trabalho enquanto estiverem em execução. +**Note**: Avoid using your scripts to output sensitive information to the console, as anyone with read access to the repository might be able to see the output in the UI logs. {% endnote %} -Os scripts são executados automaticamente quando o executor tem as seguintes variáveis de ambiente que contêm um caminho absoluto para o script: -- `ACTIONS_RUNNER_HOOK_JOB_STARTED`: o script definido nessa variável de ambiente é disparado quando um trabalho é atribuído a um executor, mas antes do trabalho começar a ser executado. -- `ACTIONS_RUNNER_HOOK_JOB_COMPLETED`: o script definido nessa variável de ambiente é disparado após o processamento do trabalho. +### Handling exit codes -Para definir essas variáveis de ambiente, você pode adicioná-las ao sistema operacional ou adicioná-las a um arquivo chamado `.env` no diretório do aplicativo do executor auto-hospedado. Por exemplo, a seguinte entrada `.env` fará com que o executor execute automaticamente um script chamado `cleanup_script.sh` antes da execução de cada trabalho: +For pre-job scripts, exit code `0` indicates that the script completed successfully, and the job will then proceed to run. If there is any other exit code, the job will not run and will be marked as failed. To see the results of your pre-job scripts, check the logs for `Set up runner` entries. For more information on checking the logs, see "[Viewing logs to diagnose failures](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)." + +The [`continue-on-error`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idcontinue-on-error) setting is not supported for use by these scripts. + +## Triggering the scripts + +The custom scripts must be located on the runner, but should not be stored in the `actions-runner` application directory. The scripts are executed in the security context of the service account that's running the runner service. + +{% note %} + +**Note**: The triggered scripts are processed synchronously, so they will block job execution while they are running. + +{% endnote %} + +The scripts are automatically executed when the runner has the following environment variables containing an absolute path to the script: +- `ACTIONS_RUNNER_HOOK_JOB_STARTED`: The script defined in this environment variable is triggered when a job has been assigned to a runner, but before the job starts running. +- `ACTIONS_RUNNER_HOOK_JOB_COMPLETED`: The script defined in this environment variable is triggered after the job has finished processing. + +To set these environment variables, you can either add them to the operating system, or add them to a file named `.env` within the self-hosted runner application directory. For example, the following `.env` entry will have the runner automatically run a script named `cleanup_script.sh` before each job runs: ```bash ACTIONS_RUNNER_HOOK_JOB_STARTED=/cleanup_script.sh ``` -## Solução de problemas +## Troubleshooting -### Sem configuração de tempo limite +### No timeout setting -Atualmente, não há nenhuma configuração de tempo limite disponível para os scripts executados por `ACTIONS_RUNNER_HOOK_JOB_STARTED` ou `ACTIONS_RUNNER_HOOK_JOB_COMPLETED`. Como resultado, você pode considerar a adição de tratamento do tempo limite ao script. +There is currently no timeout setting available for scripts executed by `ACTIONS_RUNNER_HOOK_JOB_STARTED` or `ACTIONS_RUNNER_HOOK_JOB_COMPLETED`. As a result, you could consider adding timeout handling to your script. -### Como examinar o log de execução do fluxo de trabalho +### Reviewing the workflow run log -Para confirmar se os scripts estão em execução, você pode revisar os logs desse trabalho. Os scripts serão listados em etapas separadas para `Set up runner` ou `Complete runner`, dependendo do variável de ambiente que dispara o script. Para obter mais informações sobre como verificar os logs, confira "[Como ver os logs para diagnosticar falhas](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)". +To confirm whether your scripts are executing, you can review the logs for that job. The scripts will be listed within separate steps for either `Set up runner` or `Complete runner`, depending on which environment variable is triggering the script. For more information on checking the logs, see "[Viewing logs to diagnose failures](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)." diff --git a/translations/pt-BR/content/actions/learn-github-actions/contexts.md b/translations/pt-BR/content/actions/learn-github-actions/contexts.md index 2f4ce65742..2629ad6dba 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/contexts.md +++ b/translations/pt-BR/content/actions/learn-github-actions/contexts.md @@ -469,10 +469,18 @@ jobs: output1: ${{ steps.step1.outputs.firstword }} output2: ${{ steps.step2.outputs.secondword }} steps: - - id: step1 + - id: step1{% endraw %} +{%- ifversion actions-save-state-set-output-envs %} + run: echo "firstword=hello" >> $GITHUB_OUTPUT +{%- else %} run: echo "::set-output name=firstword::hello" - - id: step2 +{%- endif %}{% raw %} + - id: step2{% endraw %} +{%- ifversion actions-save-state-set-output-envs %} + run: echo "secondword=world" >> $GITHUB_OUTPUT +{%- else %} run: echo "::set-output name=secondword::world" +{%- endif %}{% raw %} ``` {% endraw %} @@ -526,7 +534,11 @@ jobs: uses: {% data reusables.actions.action-checkout %} - name: Generate 0 or 1 id: generate_number +{%- ifversion actions-save-state-set-output-envs %} + run: echo "random_number=$(($RANDOM % 2))" >> $GITHUB_OUTPUT +{%- else %} run: echo "::set-output name=random_number::$(($RANDOM % 2))" +{%- endif %} - name: Pass or fail run: | if [[ {% raw %}${{ steps.generate_number.outputs.random_number }}{% endraw %} == 0 ]]; then exit 0; else exit 1; fi @@ -772,7 +784,11 @@ jobs: id: build_step run: | ./build +{%- ifversion actions-save-state-set-output-envs %} + echo "build_id=$BUILD_ID" >> $GITHUB_OUTPUT +{%- else %} echo "::set-output name=build_id::$BUILD_ID" +{%- endif %} deploy: needs: build runs-on: ubuntu-latest diff --git a/translations/pt-BR/content/actions/learn-github-actions/expressions.md b/translations/pt-BR/content/actions/learn-github-actions/expressions.md index d5d302ff5c..0bf64804d3 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/expressions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/expressions.md @@ -223,8 +223,12 @@ jobs: outputs: matrix: ${{ steps.set-matrix.outputs.matrix }} steps: - - id: set-matrix + - id: set-matrix{% endraw %} +{%- ifversion actions-save-state-set-output-envs %} + run: echo "matrix={\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}" >> $GITHUB_OUTPUT +{%- else %} run: echo "::set-output name=matrix::{\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}" +{%- endif %}{% raw %} job2: needs: job1 runs-on: ubuntu-latest diff --git a/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md index da677ef353..c839f81150 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md @@ -33,7 +33,7 @@ topics: {% elsif ghes or ghae %} -You must host your own Linux, Windows, or macOS virtual machines to run workflows for {% data variables.product.product_location %}. {% data reusables.actions.self-hosted-runner-locations %} +You must host your own Linux, Windows, or macOS virtual machines to run workflows for {% data variables.location.product_location %}. {% data reusables.actions.self-hosted-runner-locations %} {% endif %} diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md index 3fafe4c06b..84c4fdbf19 100644 --- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md +++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md @@ -1,6 +1,6 @@ --- -title: Transferir problemas atribuídos em quadros de projeto -intro: 'Você pode usar {% data variables.product.prodname_actions %} para transferir automaticamente um problema para uma coluna específica no quadro de um projeto quando o problema for atribuído.' +title: Moving assigned issues on project boards +intro: 'You can use {% data variables.product.prodname_actions %} to automatically move an issue to a specific column on a project board when the issue is assigned.' redirect_from: - /actions/guides/moving-assigned-issues-on-project-boards versions: @@ -13,27 +13,23 @@ topics: - Workflows - Project management shortTitle: Move assigned issues -ms.openlocfilehash: 88cec7ca6f2e7774fb29407b0b3ee14dc7041067 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147410456' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## Introdução +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} -Este tutorial demonstra como usar a [ação `alex-page/github-project-automation-plus`](https://github.com/marketplace/actions/github-project-automation) para mover automaticamente um problema para uma coluna específica em um quadro de projetos quando o problema é atribuído. Por exemplo, quando um problema é atribuído, você pode movê-lo para a coluna `In Progress` do quadro de projetos. +## Introduction -No tutorial, primeiro, você criará um arquivo de fluxo de trabalho que usa a [ação `alex-page/github-project-automation-plus`](https://github.com/marketplace/actions/github-project-automation). Então, você personalizará o fluxo de trabalho para atender às suas necessidades. +This tutorial demonstrates how to use the [`alex-page/github-project-automation-plus` action](https://github.com/marketplace/actions/github-project-automation) to automatically move an issue to a specific column on a project board when the issue is assigned. For example, when an issue is assigned, you can move it into the `In Progress` column your project board. -## Criar o fluxo de trabalho +In the tutorial, you will first make a workflow file that uses the [`alex-page/github-project-automation-plus` action](https://github.com/marketplace/actions/github-project-automation). Then, you will customize the workflow to suit your needs. + +## Creating the workflow 1. {% data reusables.actions.choose-repo %} -2. No seu repositório, escolha um quadro de projeto. Você pode usar um projeto existente ou criar um novo projeto. Para obter mais informações sobre como criar um projeto, confira "[Como criar um quadro de projetos](/github/managing-your-work-on-github/creating-a-project-board)". +2. In your repository, choose a project board. You can use an existing project, or you can create a new project. For more information about creating a project, see "[Creating a project board](/github/managing-your-work-on-github/creating-a-project-board)." 3. {% data reusables.actions.make-workflow-file %} -4. Copie o seguinte conteúdo YAML para o arquivo do fluxo de trabalho. +4. Copy the following YAML contents into your workflow file. ```yaml{:copy} {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %} @@ -56,28 +52,28 @@ No tutorial, primeiro, você criará um arquivo de fluxo de trabalho que usa a [ repo-token: {% raw %}${{ secrets.PERSONAL_ACCESS_TOKEN }}{% endraw %} ``` -5. Personalize os parâmetros no seu arquivo do fluxo de trabalho: - - Altere o valor de `project` para o nome do quadro de projetos. Se você tiver várias quadros de projetos com o mesmo nome, a ação `alex-page/github-project-automation-plus` funcionará em todos os projetos com o nome especificado. - - Altere o valor de `column` para o nome da coluna para a qual deseja mover os problemas quando eles forem atribuídos. - - Altere o valor de `repo-token`: - 1. Crie um token de acesso pessoal com o escopo `repo`. Para obter mais informações, confira "[Como criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)". - 1. Armazene este token de acesso pessoal como um segredo no seu repositório. Para obter mais informações sobre como armazenar segredos, confira "[Segredos criptografados](/actions/reference/encrypted-secrets)". - 1. No arquivo de fluxo de trabalho, substitua `PERSONAL_ACCESS_TOKEN` pelo nome do segredo. +5. Customize the parameters in your workflow file: + - Change the value for `project` to the name of your project board. If you have multiple project boards with the same name, the `alex-page/github-project-automation-plus` action will act on all projects with the specified name. + - Change the value for `column` to the name of the column where you want issues to move when they are assigned. + - Change the value for `repo-token`: + 1. Create a {% data variables.product.pat_v1 %} with the `repo` scope. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." + 1. Store this {% data variables.product.pat_generic %} as a secret in your repository. For more information about storing secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)." + 1. In your workflow file, replace `PERSONAL_ACCESS_TOKEN` with the name of your secret. 6. {% data reusables.actions.commit-workflow %} -## Testar o fluxo de trabalho +## Testing the workflow -Sempre que um problema no seu repositório for atribuído, o problema será transferido para a coluna do quadro de projeto especificado. Se o problema não estiver já no quadro de projeto, ele será adicionado ao quadro de projeto. +Whenever an issue in your repository is assigned, the issue will be moved to the specified project board column. If the issue is not already on the project board, it will be added to the project board. -Se o repositório pertencer ao usuário, a ação `alex-page/github-project-automation-plus` funcionará em todos os projetos do seu repositório ou da conta pessoal que têm o nome e a coluna do projeto especificados. Da mesma forma, se o repositório pertencer a uma organização, a ação atuará sobre todos os projetos do seu repositório ou organização que têm o nome e a coluna especificados. +If your repository is user-owned, the `alex-page/github-project-automation-plus` action will act on all projects in your repository or personal account that have the specified project name and column. Likewise, if your repository is organization-owned, the action will act on all projects in your repository or organization that have the specified project name and column. -Teste seu fluxo de trabalho atribuindo um problema no seu repositório. +Test your workflow by assigning an issue in your repository. -1. Abra um problema no seu repositório. Para obter mais informações, confira "[Como criar um problema](/github/managing-your-work-on-github/creating-an-issue)". -2. Atribuir o problema. Para obter mais informações, confira "[Como atribuir problemas e solicitações de pull a outros usuários do GitHub](/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users)". -3. Para ver a execução do fluxo de trabalho que atribui o problema acionado, visualize o histórico da execução do fluxo de trabalho. Para obter mais informações, confira "[Como ver o histórico de execução do fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history)". -4. Quando o fluxo de trabalho é concluído, o problema que você atribuiu deverá ser adicionado à coluna do quadro de projeto especificado. +1. Open an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)." +2. Assign the issue. For more information, see "[Assigning issues and pull requests to other GitHub users](/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users)." +3. To see the workflow run that assigning the issue triggered, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." +4. When the workflow completes, the issue that you assigned should be added to the specified project board column. -## Próximas etapas +## Next steps -- Para descobrir outras coisas que você pode fazer com a ação `alex-page/github-project-automation-plus`, como excluir ou arquivar cartões de projeto, acesse a [documentação da ação `alex-page/github-project-automation-plus`](https://github.com/marketplace/actions/github-project-automation). +- To learn more about additional things you can do with the `alex-page/github-project-automation-plus` action, like deleting or archiving project cards, visit the [`alex-page/github-project-automation-plus` action documentation](https://github.com/marketplace/actions/github-project-automation). diff --git a/translations/pt-BR/content/actions/publishing-packages/publishing-nodejs-packages.md b/translations/pt-BR/content/actions/publishing-packages/publishing-nodejs-packages.md index 908764eb17..34ccc87811 100644 --- a/translations/pt-BR/content/actions/publishing-packages/publishing-nodejs-packages.md +++ b/translations/pt-BR/content/actions/publishing-packages/publishing-nodejs-packages.md @@ -115,7 +115,7 @@ If you do provide the `repository` key in your *package.json* file, then the rep To perform authenticated operations against the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN`. {% data reusables.actions.github-token-permissions %} -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)." +If you want to publish your package to a different repository, you must use a {% data variables.product.pat_v1 %} that has permission to write to packages in the destination repository. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)." ### Example workflow diff --git a/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md b/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md index 34239bf6e5..a7a52992a7 100644 --- a/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md +++ b/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md @@ -117,9 +117,9 @@ The permissions for the `GITHUB_TOKEN` are initially set to the default setting ### Granting additional permissions -If you need a token that requires permissions that aren't available in the `GITHUB_TOKEN`, you can create a personal access token and set it as a secret in your repository: +If you need a token that requires permissions that aren't available in the `GITHUB_TOKEN`, you can create a {% data variables.product.pat_generic %} and set it as a secret in your repository: -1. Use or create a token with the appropriate permissions for that repository. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +1. Use or create a token with the appropriate permissions for that repository. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." 1. Add the token as a secret in your workflow's repository, and refer to it using the {%raw%}`${{ secrets.SECRET_NAME }}`{% endraw %} syntax. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." ### Further reading diff --git a/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md b/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md index e678c2474c..cd8cf7b99a 100644 --- a/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md +++ b/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md @@ -60,7 +60,7 @@ You can also manage secrets using the REST API. For more information, see "[Secr ### Limiting credential permissions -When generating credentials, we recommend that you grant the minimum permissions possible. For example, instead of using personal credentials, use [deploy keys](/developers/overview/managing-deploy-keys#deploy-keys) or a service account. Consider granting read-only permissions if that's all that is needed, and limit access as much as possible. When generating a personal access token (PAT), select the fewest scopes necessary. +When generating credentials, we recommend that you grant the minimum permissions possible. For example, instead of using personal credentials, use [deploy keys](/developers/overview/managing-deploy-keys#deploy-keys) or a service account. Consider granting read-only permissions if that's all that is needed, and limit access as much as possible. When generating a {% data variables.product.pat_v1 %}, select the fewest scopes necessary.{% ifversion pat-v2 %} When generating a {% data variables.product.pat_v2 %}, select the minimum repository access required.{% endif %} {% note %} diff --git a/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md index 9b7fb1a826..5a18705739 100644 --- a/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md @@ -261,11 +261,11 @@ This list describes the recommended approaches for accessing repository data wit - Note that deploy keys can only clone and push to the repository using Git, and cannot be used to interact with the REST or GraphQL API, so they may not be appropriate for your requirements. 3. **{% data variables.product.prodname_github_app %} tokens** - {% data variables.product.prodname_github_apps %} can be installed on select repositories, and even have granular permissions on the resources within them. You could create a {% data variables.product.prodname_github_app %} internal to your organization, install it on the repositories you need access to within your workflow, and authenticate as the installation within your workflow to access those repositories. -4. **Personal access tokens** - - You should never use personal access tokens from your own account. These tokens grant access to all repositories within the organizations that you have access to, as well as all personal repositories in your personal account. This indirectly grants broad access to all write-access users of the repository the workflow is in. In addition, if you later leave an organization, workflows using this token will immediately break, and debugging this issue can be challenging. - - If a personal access token is used, it should be one that was generated for a new account that is only granted access to the specific repositories that are needed for the workflow. Note that this approach is not scalable and should be avoided in favor of alternatives, such as deploy keys. +4. **{% data variables.product.pat_generic %}s** + - You should never use a {% data variables.product.pat_v1 %}. These tokens grant access to all repositories within the organizations that you have access to, as well as all personal repositories in your personal account. This indirectly grants broad access to all write-access users of the repository the workflow is in. + - If you do use a {% data variables.product.pat_generic %}, you should never use a {% data variables.product.pat_generic %} from your own account. If you later leave an organization, workflows using this token will immediately break, and debugging this issue can be challenging. Instead, you should use a {% ifversion pat-v2%}{% data variables.product.pat_v2 %}s{% else %}{% data variables.product.pat_generic %}s{% endif %} for a new account that belongs to your organization and that is only granted access to the specific repositories that are needed for the workflow. Note that this approach is not scalable and should be avoided in favor of alternatives, such as deploy keys. 5. **SSH keys on a personal account** - - Workflows should never use the SSH keys on a personal account. Similar to personal access tokens, they grant read/write permissions to all of your personal repositories as well as all the repositories you have access to through organization membership. This indirectly grants broad access to all write-access users of the repository the workflow is in. If you're intending to use an SSH key because you only need to perform repository clones or pushes, and do not need to interact with public APIs, then you should use individual deploy keys instead. + - Workflows should never use the SSH keys on a personal account. Similar to {% data variables.product.pat_v1_plural %}, they grant read/write permissions to all of your personal repositories as well as all the repositories you have access to through organization membership. This indirectly grants broad access to all write-access users of the repository the workflow is in. If you're intending to use an SSH key because you only need to perform repository clones or pushes, and do not need to interact with public APIs, then you should use individual deploy keys instead. ## Hardening for self-hosted runners diff --git a/translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index 16defd8a7e..d47babe64e 100644 --- a/translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -90,7 +90,7 @@ While the job runs, the logs and output can be viewed in the {% data variables.p {% note %} -**Note**: {% data variables.product.prodname_dotcom %} also offers {% data variables.actions.hosted_runner %}s, which are available in larger configurations. For more information, see "[Using {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/using-larger-runners)." +**Note**: {% data variables.product.prodname_dotcom %} also offers {% data variables.actions.hosted_runner %}s, which are available in larger configurations. For more information, see "[Machine specs for {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/using-larger-runners#machine-specs-for-larger-runners)." {% endnote %} {% endif %} diff --git a/translations/pt-BR/content/actions/using-github-hosted-runners/using-larger-runners.md b/translations/pt-BR/content/actions/using-github-hosted-runners/using-larger-runners.md index e3251b78a6..d4f33140a6 100644 --- a/translations/pt-BR/content/actions/using-github-hosted-runners/using-larger-runners.md +++ b/translations/pt-BR/content/actions/using-github-hosted-runners/using-larger-runners.md @@ -14,6 +14,16 @@ In addition to the [standard {% data variables.product.prodname_dotcom %}-hosted When you add a {% data variables.actions.hosted_runner %} to an organization, you are defining a type of machine from a selection of available hardware specifications and operating system images. {% data variables.product.prodname_dotcom %} will then create multiple instances of this runner that scale up and down to match the job demands of your organization, based on the autoscaling limits you define. +## Machine specs for {% data variables.actions.hosted_runner %}s + +|Size (vcpu) | Memory (GB) | Storage (SSD) | +| ------------- | ------------- | ------------- | +|4 cores | 16 RAM | 150 GB| +| 8 cores | 32 RAM | 300 GB | +|16 cores| 64 RAM | 600 GB | +|32 cores| 128 RAM| 1200 GB| +|64 cores| 256 RAM | 2040 GB| + ## Architectural overview of {% data variables.actions.hosted_runner %}s The {% data variables.actions.hosted_runner %}s are managed at the organization level, where they are arranged into groups that can contain multiple instances of the runner. They can also be created at the enterprise level and shared with organizations in the hierarchy. Once you've created a group, you can then add a runner to the group and update your workflows to target the label assigned to the {% data variables.actions.hosted_runner %}. You can also control which repositories are permitted to send jobs to the group for processing. For more information about groups, see "[Controlling access to {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/controlling-access-to-larger-runners)." diff --git a/translations/pt-BR/content/actions/using-workflows/events-that-trigger-workflows.md b/translations/pt-BR/content/actions/using-workflows/events-that-trigger-workflows.md index 52a8fc5cf1..fa4f441d04 100644 --- a/translations/pt-BR/content/actions/using-workflows/events-that-trigger-workflows.md +++ b/translations/pt-BR/content/actions/using-workflows/events-that-trigger-workflows.md @@ -1264,7 +1264,7 @@ on: workflow_call | Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | | ------------------ | ------------ | ------------ | ------------------| -| [workflow_dispatch](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#workflow_dispatch) | n/a | Last commit on the `GITHUB_REF` branch | Branch that received dispatch | +| [workflow_dispatch](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#workflow_dispatch) | n/a | Last commit on the `GITHUB_REF` branch or tag | Branch or tag that received dispatch | To manually trigger a workflow, use the `workflow_dispatch` event. You can manually trigger a workflow run using the {% data variables.product.product_name %} API, {% data variables.product.prodname_cli %}, or {% data variables.product.product_name %} browser interface. For more information, see "[Manually running a workflow](/actions/managing-workflow-runs/manually-running-a-workflow)." diff --git a/translations/pt-BR/content/actions/using-workflows/reusing-workflows.md b/translations/pt-BR/content/actions/using-workflows/reusing-workflows.md index 016cb10829..7186ebf265 100644 --- a/translations/pt-BR/content/actions/using-workflows/reusing-workflows.md +++ b/translations/pt-BR/content/actions/using-workflows/reusing-workflows.md @@ -76,7 +76,7 @@ Called workflows that are owned by the same user or organization{% ifversion ghe ## Limitations {% ifversion nested-reusable-workflow %} -* You can connect up to four levels of workflows. For more information, see "[Calling a nested reusable workflow](#calling-a-nested-reusable-workflow)." +* You can connect up to four levels of workflows. For more information, see "[Nesting reusable workflows](#nesting-reusable-workflows)." {% else %} * Reusable workflows can't call other reusable workflows. {% endif %} @@ -115,7 +115,7 @@ You can define inputs and secrets, which can be passed from the caller workflow {% endraw %} For details of the syntax for defining inputs and secrets, see [`on.workflow_call.inputs`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callinputs) and [`on.workflow_call.secrets`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callsecrets). {% ifversion actions-inherit-secrets-reusable-workflows %} -1. In the reusable workflow, reference the input or secret that you defined in the `on` key in the previous step. +1. In the reusable workflow, reference the input or secret that you defined in the `on` key in the previous step. {% note %} @@ -338,7 +338,7 @@ For information on how to use the API to determine which workflow files were inv A reusable workflow may generate data that you want to use in the caller workflow. To use these outputs, you must specify them as the outputs of the reusable workflow.{% ifversion actions-reusable-workflow-matrix %} -If a reusable workflow that sets an output is executed with a matrix strategy, the output will be the output set by the last successful completing reusable workflow of the matrix which actually sets a value. +If a reusable workflow that sets an output is executed with a matrix strategy, the output will be the output set by the last successful completing reusable workflow of the matrix which actually sets a value. That means if the last successful completing reusable workflow sets an empty string for its output, and the second last successful completing reusable workflow sets an actual value for its output, the output will contain the value of the second last completing reusable workflow.{% endif %} The following reusable workflow has a single job containing two steps. In each of these steps we set a single word as the output: "hello" and "world." In the `outputs` section of the job, we map these step outputs to job outputs called: `output1` and `output2`. In the `on.workflow_call.outputs` section we then define two outputs for the workflow itself, one called `firstword` which we map to `output1`, and one called `secondword` which we map to `output2`. @@ -367,10 +367,18 @@ jobs: output1: ${{ steps.step1.outputs.firstword }} output2: ${{ steps.step2.outputs.secondword }} steps: - - id: step1 + - id: step1{% endraw %} +{%- ifversion actions-save-state-set-output-envs %} + run: echo "firstword=hello" >> $GITHUB_OUTPUT +{%- else %} run: echo "::set-output name=firstword::hello" - - id: step2 +{%- endif %}{% raw %} + - id: step2{% endraw %} +{%- ifversion actions-save-state-set-output-envs %} + run: echo "secondword=world" >> $GITHUB_OUTPUT +{%- else %} run: echo "::set-output name=secondword::world" +{%- endif %}{% raw %} ``` {% endraw %} diff --git a/translations/pt-BR/content/actions/using-workflows/storing-workflow-data-as-artifacts.md b/translations/pt-BR/content/actions/using-workflows/storing-workflow-data-as-artifacts.md index 573f2dd254..0be100e2ea 100644 --- a/translations/pt-BR/content/actions/using-workflows/storing-workflow-data-as-artifacts.md +++ b/translations/pt-BR/content/actions/using-workflows/storing-workflow-data-as-artifacts.md @@ -1,7 +1,7 @@ --- -title: Armazenar dados do fluxo de trabalho como artefatos -shortTitle: Storing workflow artifacts -intro: Artefatos permitem que você compartilhe dados entre trabalhos em um fluxo e armazene dados quando o fluxo de trabalho estiver concluído. +title: Storing workflow data as artifacts +shortTitle: Store artifacts +intro: Artifacts allow you to share data between jobs in a workflow and store data once that workflow has completed. redirect_from: - /articles/persisting-workflow-data-using-artifacts - /github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts @@ -17,68 +17,64 @@ versions: type: tutorial topics: - Workflows -ms.openlocfilehash: d23b62f1e77fd08fd798f4fb1af9f44e4d1b1123 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146179732' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## Sobre artefatos de fluxos de trabalho +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} -Os artefatos permitem que você persista com os dados após um trabalho ter sido concluído e compartilhe os dados com outro trabalho no mesmo fluxo de trabalho. Um artefato é um arquivo ou uma coleção de arquivos produzidos durante a execução de um fluxo de trabalho. Por exemplo, você pode usar artefatos para salvar a sua criação e testar a saída após uma conclusão da execução do fluxo de trabalho. {% data reusables.actions.reusable-workflow-artifacts %} +## About workflow artifacts -{% data reusables.actions.artifact-log-retention-statement %} O período de retenção para uma solicitação de pull é reiniciado sempre que alguém efetua push de um novo commit para a solicitação de pull. +Artifacts allow you to persist data after a job has completed, and share that data with another job in the same workflow. An artifact is a file or collection of files produced during a workflow run. For example, you can use artifacts to save your build and test output after a workflow run has ended. {% data reusables.actions.reusable-workflow-artifacts %} -Esses são alguns dos artefatos comuns cujo upload você pode fazer: +{% data reusables.actions.artifact-log-retention-statement %} The retention period for a pull request restarts each time someone pushes a new commit to the pull request. -- Arquivos de log e descartes de memória; -- Resultados de testes, falhas e capturas de tela; -- Arquivos binários ou comprimidos -- Resultados de teste de estresse e resultados de cobertura do código. +These are some of the common artifacts that you can upload: + +- Log files and core dumps +- Test results, failures, and screenshots +- Binary or compressed files +- Stress test performance output and code coverage results {% ifversion fpt or ghec %} -Armazenar artefatos consome espaço de armazenamento em {% data variables.product.product_name %}. {% data reusables.actions.actions-billing %} Para obter mais informações, confira "[Como gerenciar a cobrança do {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)". +Storing artifacts uses storage space on {% data variables.product.product_name %}. {% data reusables.actions.actions-billing %} For more information, see "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)." {% else %} -Os artefatos consomem espaço de armazenamento no bloco externo que está configurado para {% data variables.product.prodname_actions %} em {% data variables.product.product_location %}. +Artifacts consume storage space on the external blob storage that is configured for {% data variables.product.prodname_actions %} on {% data variables.location.product_location %}. {% endif %} -Faz-se o upload dos artefatos durante a execução de um fluxo de trabalho e você pode visualizar o nome e o tamanho do artefato na UI. Quando se faz o download de um artefato usando a UI {% data variables.product.product_name %}, todos os arquivos cujo upload foi feito individualmente como parte do get do artefato zipado em um arquivo único. Isso significa que a cobrança é calculada com base no tamanho do artefato subido e não com base no tamanho do arquivo zip. +Artifacts are uploaded during a workflow run, and you can view an artifact's name and size in the UI. When an artifact is downloaded using the {% data variables.product.product_name %} UI, all files that were individually uploaded as part of the artifact get zipped together into a single file. This means that billing is calculated based on the size of the uploaded artifact and not the size of the zip file. -O {% data variables.product.product_name %} fornece duas ações que você pode usar para fazer upload e baixar artefatos de compilação. Para obter mais informações, confira as ações {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) e [download-artifact](https://github.com/actions/download-artifact){% else %} ações `actions/upload-artifact` e `download-artifact` do {% data variables.product.product_location %}{% endif %}. +{% data variables.product.product_name %} provides two actions that you can use to upload and download build artifacts. For more information, see the {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) and [download-artifact](https://github.com/actions/download-artifact) actions{% else %} `actions/upload-artifact` and `download-artifact` actions on {% data variables.location.product_location %}{% endif %}. -Para compartilhar dados entre trabalhos: +To share data between jobs: -* **Upload de arquivos**: dê um nome ao arquivo carregado e carregue os dados antes da conclusão do trabalho. -* **Download de arquivos**: só é possível baixar artefatos que foram carregados na mesma execução de fluxo de trabalho. Ao fazer o download de um arquivo, você pode fazer referenciá-lo pelo nome. +* **Uploading files**: Give the uploaded file a name and upload the data before the job ends. +* **Downloading files**: You can only download artifacts that were uploaded during the same workflow run. When you download a file, you can reference it by name. -As etapas de um trabalho compartilham o mesmo ambiente na máquina executora, mas são executados em seus próprios processos individuais. Para transmitir dados entre etapas de um trabalho, você pode usar entradas e saídas. Para obter mais informações sobre entradas e saídas, confira "[Sintaxe de metadados do {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions)". +The steps of a job share the same environment on the runner machine, but run in their own individual processes. To pass data between steps in a job, you can use inputs and outputs. For more information about inputs and outputs, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions)." {% ifversion actions-caching %} {% data reusables.actions.comparing-artifacts-caching %} -Para obter mais informações sobre dependência em cache, confira "[Como armazenar dependências em cache para acelerar os fluxos de trabalho](/actions/using-workflows/caching-dependencies-to-speed-up-workflows#comparing-artifacts-and-dependency-caching)". +For more information on dependency caching, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows#comparing-artifacts-and-dependency-caching)." {% endif %} -## Fazer upload da compilação e testar artefatos +## Uploading build and test artifacts -Você pode criar um fluxo de trabalho de integração contínua (CI) para criar e testar o seu código. Para obter mais informações sobre como usar o {% data variables.product.prodname_actions %} para executar a CI, confira "[Sobre a integração contínua](/articles/about-continuous-integration)". +You can create a continuous integration (CI) workflow to build and test your code. For more information about using {% data variables.product.prodname_actions %} to perform CI, see "[About continuous integration](/articles/about-continuous-integration)." -A saída da compilação e teste de seu código muitas vezes produz arquivos que podem ser usados para depurar falhas em testes e códigos de produção que você pode implantar. É possível configurar um fluxo de trabalho para compilar e testar o código com push no repositório e relatar um status de sucesso ou falha. Você pode fazer upload da saída de compilação e teste para usar em implantações, para depurar falhas e testes com falhas e visualizar a cobertura do conjunto de teste. +The output of building and testing your code often produces files you can use to debug test failures and production code that you can deploy. You can configure a workflow to build and test the code pushed to your repository and report a success or failure status. You can upload the build and test output to use for deployments, debugging failed tests or crashes, and viewing test suite coverage. -Use a ação `upload-artifact` para carregar artefatos. Ao fazer o upload de um artefato, você pode especificar um arquivo ou diretório único, ou vários arquivos ou diretórios. Você também pode excluir certos arquivos ou diretórios e usar padrões coringa. Recomendamos que você forneça um nome para um artefato, mas se nenhum nome for fornecido, `artifact` será usado como o nome padrão. Para obter mais informações sobre a sintaxe, confira a ação {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact){% else %} ação `actions/upload-artifact` no {% data variables.product.product_location %}{% endif %}. +You can use the `upload-artifact` action to upload artifacts. When uploading an artifact, you can specify a single file or directory, or multiple files or directories. You can also exclude certain files or directories, and use wildcard patterns. We recommend that you provide a name for an artifact, but if no name is provided then `artifact` will be used as the default name. For more information on syntax, see the {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) action{% else %} `actions/upload-artifact` action on {% data variables.location.product_location %}{% endif %}. -### Exemplo +### Example -Por exemplo, o seu repositório ou um aplicativo web pode conter arquivos SASS e TypeScript que você deve converter para CSS e JavaScript. Pressupondo que a sua configuração de build gere os arquivos compilados no diretório `dist`, você implantará os arquivos no diretório `dist` no seu servidor de aplicativos Web se todos os testes forem concluídos com sucesso. +For example, your repository or a web application might contain SASS and TypeScript files that you must convert to CSS and JavaScript. Assuming your build configuration outputs the compiled files in the `dist` directory, you would deploy the files in the `dist` directory to your web application server if all tests completed successfully. ``` |-- hello-world (repository) @@ -92,9 +88,9 @@ Por exemplo, o seu repositório ou um aplicativo web pode conter arquivos SASS e | ``` -Este exemplo mostra como criar um fluxo de trabalho para um projeto do Node.js que compila o código no diretório `src` e executa os testes no diretório `tests`. Você pode pressupor que a execução `npm test` produza um relatório de cobertura de código chamado `code-coverage.html` armazenado no diretório `output/test/`. +This example shows you how to create a workflow for a Node.js project that builds the code in the `src` directory and runs the tests in the `tests` directory. You can assume that running `npm test` produces a code coverage report named `code-coverage.html` stored in the `output/test/` directory. -O fluxo de trabalho carrega os artefatos de produção no diretório `dist`, mas exclui os arquivos markdown. Ele também carrega o relatório `code-coverage.html` como outro artefato. +The workflow uploads the production artifacts in the `dist` directory, but excludes any markdown files. It also uploads the `code-coverage.html` report as another artifact. ```yaml{:copy} name: Node CI @@ -126,9 +122,9 @@ jobs: path: output/test/code-coverage.html ``` -## Configurar um período de retenção do artefato personalizado +## Configuring a custom artifact retention period -Você pode definir um período de retenção personalizado para artefatos individuais criados por um fluxo de trabalho. Ao usar um fluxo de trabalho para criar um artefato, você pode usar `retention-days` com a ação `upload-artifact`. Este exemplo demonstra como definir um período de retenção personalizado de cinco dias para o artefato chamado `my-artifact`: +You can define a custom retention period for individual artifacts created by a workflow. When using a workflow to create a new artifact, you can use `retention-days` with the `upload-artifact` action. This example demonstrates how to set a custom retention period of 5 days for the artifact named `my-artifact`: ```yaml{:copy} - name: 'Upload Artifact' @@ -139,25 +135,25 @@ Você pode definir um período de retenção personalizado para artefatos indivi retention-days: 5 ``` -O valor `retention-days` não pode exceder o limite de retenção definido pelo repositório, pela organização ou pela empresa. +The `retention-days` value cannot exceed the retention limit set by the repository, organization, or enterprise. -## Fazer o download ou excluir artefatos +## Downloading or deleting artifacts -Durante a execução de um fluxo de trabalho, você pode usar a ação [`download-artifact`](https://github.com/actions/download-artifact) para baixar os artefatos que foram previamente carregados na mesma execução de fluxo de trabalho. +During a workflow run, you can use the [`download-artifact`](https://github.com/actions/download-artifact) action to download artifacts that were previously uploaded in the same workflow run. -Após a conclusão da execução de um fluxo de trabalho, você pode fazer o download ou excluir artefatos em {% data variables.product.prodname_dotcom %} ou usar a API REST. Para obter mais informações, confira "[Como baixar artefatos de fluxo de trabalho](/actions/managing-workflow-runs/downloading-workflow-artifacts)", "[Como remover artefatos de fluxo de trabalho](/actions/managing-workflow-runs/removing-workflow-artifacts)" e a "[API REST de Artefatos](/rest/reference/actions#artifacts)". +After a workflow run has been completed, you can download or delete artifacts on {% data variables.product.prodname_dotcom %} or using the REST API. For more information, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)," "[Removing workflow artifacts](/actions/managing-workflow-runs/removing-workflow-artifacts)," and the "[Artifacts REST API](/rest/reference/actions#artifacts)." -### Fazer o download dos artefatos durante a execução de um fluxo de trabalho +### Downloading artifacts during a workflow run -A ação [`actions/download-artifact`](https://github.com/actions/download-artifact) pode ser usada para baixar artefatos já carregados durante uma execução de fluxo de trabalho. +The [`actions/download-artifact`](https://github.com/actions/download-artifact) action can be used to download previously uploaded artifacts during a workflow run. {% note %} -**Observação:** só é possível baixar artefatos em um fluxo de trabalho que foram carregados na mesma execução de fluxo de trabalho. +**Note:** You can only download artifacts in a workflow that were uploaded during the same workflow run. {% endnote %} -Especifique o nome de um artefato para fazer o download de um artefato individual. Se você carregar um artefato sem especificar um nome, o nome padrão será `artifact`. +Specify an artifact's name to download an individual artifact. If you uploaded an artifact without specifying a name, the default name is `artifact`. ```yaml - name: Download a single artifact @@ -166,37 +162,37 @@ Especifique o nome de um artefato para fazer o download de um artefato individua name: my-artifact ``` -Você também pode baixar todos os artefatos em uma execução de fluxo de trabalho sem especificar um nome. Isso pode ser útil se você estiver trabalhando com muitos artefatos. +You can also download all artifacts in a workflow run by not specifying a name. This can be useful if you are working with lots of artifacts. ```yaml - name: Download all workflow run artifacts uses: {% data reusables.actions.action-download-artifact %} ``` -Se você fizer o download de todos os artefatos da execução de um fluxo de trabalho, será criado um diretório para cada artefato usando seu nome. +If you download all workflow run's artifacts, a directory for each artifact is created using its name. -Para obter mais informações sobre a sintaxe, confira a ação {% ifversion fpt or ghec %}[actions/download-artifact](https://github.com/actions/download-artifact){% else %} ação `actions/download-artifact` no {% data variables.product.product_location %}{% endif %}. +For more information on syntax, see the {% ifversion fpt or ghec %}[actions/download-artifact](https://github.com/actions/download-artifact) action{% else %} `actions/download-artifact` action on {% data variables.location.product_location %}{% endif %}. -## Passando dados entre trabalhos em um fluxo de trabalho +## Passing data between jobs in a workflow -Use as ações `upload-artifact` e `download-artifact` para compartilhar dados entre trabalhos em um fluxo de trabalho. Este exemplo de fluxo de trabalho ilustra como transmitir dados entre trabalhos em um mesmo fluxo. Para obter mais informações, confira as ações {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) e [download-artifact](https://github.com/actions/download-artifact){% else %} ações `actions/upload-artifact` e `download-artifact` do {% data variables.product.product_location %}{% endif %}. +You can use the `upload-artifact` and `download-artifact` actions to share data between jobs in a workflow. This example workflow illustrates how to pass data between jobs in the same workflow. For more information, see the {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) and [download-artifact](https://github.com/actions/download-artifact) actions{% else %} `actions/upload-artifact` and `download-artifact` actions on {% data variables.location.product_location %}{% endif %}. -Os trabalhos que são dependentes de artefatos de um trabalho anterior devem aguardar a finalização do trabalho dependente. Esse fluxo de trabalho usa a palavra-chave `needs` para garantir que `job_1`, `job_2` e `job_3` sejam executados sequencialmente. Por exemplo, `job_2` exige o `job_1` usando a sintaxe `needs: job_1`. +Jobs that are dependent on a previous job's artifacts must wait for the dependent job to complete successfully. This workflow uses the `needs` keyword to ensure that `job_1`, `job_2`, and `job_3` run sequentially. For example, `job_2` requires `job_1` using the `needs: job_1` syntax. -O Job 1 (Trabalho 1) executa estas etapas: -- Faz um cálculo matemático e salva o resultado em um arquivo de texto chamado `math-homework.txt`. -- Usa a ação `upload-artifact` para carregar o arquivo `math-homework.txt` com o nome de artefato `homework`. +Job 1 performs these steps: +- Performs a math calculation and saves the result to a text file called `math-homework.txt`. +- Uses the `upload-artifact` action to upload the `math-homework.txt` file with the artifact name `homework`. -O Job 2 (Trabalho 2) usa o resultado do trabalho anterior: -- Baixa o artefato `homework` carregado no trabalho anterior. Por padrão, a ação `download-artifact` baixa artefatos no diretório do workspace no qual a etapa está sendo executada. Use o parâmetro de entrada `path` para especificar outro diretório de download. -- Lê o valor do arquivo `math-homework.txt`, faz um cálculo matemático e salva o resultado em `math-homework.txt` novamente, substituindo o conteúdo. -- Carrega o arquivo `math-homework.txt`. Este upload sobrescreve o artefato carregado anteriormente porque compartilham o mesmo nome. +Job 2 uses the result in the previous job: +- Downloads the `homework` artifact uploaded in the previous job. By default, the `download-artifact` action downloads artifacts to the workspace directory that the step is executing in. You can use the `path` input parameter to specify a different download directory. +- Reads the value in the `math-homework.txt` file, performs a math calculation, and saves the result to `math-homework.txt` again, overwriting its contents. +- Uploads the `math-homework.txt` file. This upload overwrites the previously uploaded artifact because they share the same name. -O Job 3 (Trabalho 3) mostra o resultado carregado no trabalho anterior: -- Baixa o artefato `homework`. -- Imprime o resultado da operação matemática no log. +Job 3 displays the result uploaded in the previous job: +- Downloads the `homework` artifact. +- Prints the result of the math equation to the log. -A operação matemática completa feita nesse exemplo de fluxo de trabalho é `(3 + 7) x 9 = 90`. +The full math operation performed in this workflow example is `(3 + 7) x 9 = 90`. ```yaml{:copy} name: Share data between jobs @@ -252,13 +248,13 @@ jobs: echo The result is $value ``` -A execução do fluxo de trabalho arquivará quaisquer artefatos gerados por ele. Para obter mais informações sobre como baixar os artefatos arquivados, confira "[Como baixar os artefatos de fluxo de trabalho](/actions/managing-workflow-runs/downloading-workflow-artifacts)". -![Fluxo de trabalho que transmite dados entre trabalhos para fazer cálculos matemáticos](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) +The workflow run will archive any artifacts that it generated. For more information on downloading archived artifacts, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)." +![Workflow that passes data between jobs to perform math](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) {% ifversion fpt or ghec %} -## Leitura adicional +## Further reading -- "[Como gerenciar a cobrança do {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)". +- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)". {% endif %} diff --git a/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md b/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md index c0c7429ee7..8e4adb430f 100644 --- a/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md +++ b/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md @@ -36,9 +36,9 @@ The following steps occur to trigger a workflow run: {% data reusables.actions.actions-do-not-trigger-workflows %} For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)." -If you do want to trigger a workflow from within a workflow run, you can use a personal access token instead of `GITHUB_TOKEN` to trigger events that require a token. You'll need to create a personal access token and store it as a secret. To minimize your {% data variables.product.prodname_actions %} usage costs, ensure that you don't create recursive or unintended workflow runs. For more information about creating a personal access token, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about storing a personal access token as a secret, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)." +If you do want to trigger a workflow from within a workflow run, you can use a {% data variables.product.pat_generic %} instead of `GITHUB_TOKEN` to trigger events that require a token. You'll need to create a {% data variables.product.pat_generic %} and store it as a secret. To minimize your {% data variables.product.prodname_actions %} usage costs, ensure that you don't create recursive or unintended workflow runs. For more information about creating a {% data variables.product.pat_generic %}, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about storing a {% data variables.product.pat_generic %} as a secret, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)." -For example, the following workflow uses a personal access token (stored as a secret called `MY_TOKEN`) to add a label to an issue via {% data variables.product.prodname_cli %}. Any workflows that run when a label is added will run once this step is performed. +For example, the following workflow uses a {% data variables.product.pat_generic %} (stored as a secret called `MY_TOKEN`) to add a label to an issue via {% data variables.product.prodname_cli %}. Any workflows that run when a label is added will run once this step is performed. ```yaml on: diff --git a/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md b/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md index 60e836a70a..190fb29822 100644 --- a/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md +++ b/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md @@ -148,12 +148,12 @@ The following table shows which toolkit functions are available within a workflo | `core.getState` | Accessible using environment variable `STATE_{NAME}` | | `core.isDebug` | Accessible using environment variable `RUNNER_DEBUG` | {%- ifversion actions-job-summaries %} -| `core.summary` | Accessible using environment variable `GITHUB_STEP_SUMMARY` | +| `core.summary` | Accessible using environment file `GITHUB_STEP_SUMMARY` | {%- endif %} -| `core.saveState` | {% ifversion actions-save-state-set-output-envs %}Accessible using environment variable `GITHUB_STATE`{% else %}`save-state`{% endif %} | +| `core.saveState` | {% ifversion actions-save-state-set-output-envs %}Accessible using environment file `GITHUB_STATE`{% else %}`save-state`{% endif %} | | `core.setCommandEcho` | `echo` | | `core.setFailed` | Used as a shortcut for `::error` and `exit 1` | -| `core.setOutput` | {% ifversion actions-save-state-set-output-envs %}Accessible using environment variable `GITHUB_OUTPUT`{% else %}`set-output`{% endif %} | +| `core.setOutput` | {% ifversion actions-save-state-set-output-envs %}Accessible using environment file `GITHUB_OUTPUT`{% else %}`set-output`{% endif %} | | `core.setSecret` | `add-mask` | | `core.startGroup` | `group` | | `core.warning` | `warning` | @@ -481,6 +481,7 @@ jobs: {% endpowershell %} +{% ifversion actions-save-state-set-output-envs %}{% else %} ## Echoing command outputs Enables or disables echoing of workflow commands. For example, if you use the `set-output` command in a workflow, it sets an output parameter but the workflow run's log does not show the command itself. If you enable command echoing, then the log shows the command, such as `::set-output name={name}::{value}`. @@ -542,6 +543,8 @@ The example above prints the following lines to the log: ``` Only the second `set-output` and `echo` workflow commands are included in the log because command echoing was only enabled when they were run. Even though it is not always echoed, the output parameter is set in all cases. + +{% endif %} ## Sending values to the pre and post actions diff --git a/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md index 405e998caf..5c778a85ca 100644 --- a/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md +++ b/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md @@ -115,7 +115,7 @@ For more information, see "[Reusing workflows](/actions/learn-github-actions/reu #### `on.workflow_call.inputs..type` -Required if input is defined for the `on.workflow_call` keyword. The value of this parameter is a string specifying the data type of the input. This must be one of: `boolean`, `number`, `string` or `choice`. +Required if input is defined for the `on.workflow_call` keyword. The value of this parameter is a string specifying the data type of the input. This must be one of: `boolean`, `number`, or `string`. ### `on.workflow_call.outputs` @@ -497,7 +497,7 @@ jobs: #### Example: Using an action inside a different private repository than the workflow -Your workflow must checkout the private repository and reference the action locally. Generate a personal access token and add the token as an encrypted secret. 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)." +Your workflow must checkout the private repository and reference the action locally. Generate a {% data variables.product.pat_generic %} and add the token as an encrypted secret. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)." Replace `PERSONAL_ACCESS_TOKEN` in the example with the name of your secret. diff --git a/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md b/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md index 468b95f2c7..c984aebcab 100644 --- a/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md +++ b/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md @@ -1,7 +1,7 @@ --- title: Configuring code scanning for your appliance shortTitle: Configuring code scanning -intro: 'You can enable, configure and disable {% data variables.product.prodname_code_scanning %} for {% data variables.product.product_location %}. {% data variables.product.prodname_code_scanning_capc %} allows users to scan code for vulnerabilities and errors.' +intro: 'You can enable, configure and disable {% data variables.product.prodname_code_scanning %} for {% data variables.location.product_location %}. {% data variables.product.prodname_code_scanning_capc %} allows users to scan code for vulnerabilities and errors.' product: '{% data reusables.gated-features.code-scanning %}' miniTocMaxHeadingLevel: 3 redirect_from: @@ -24,7 +24,7 @@ topics: {% data reusables.code-scanning.about-code-scanning %} -You can configure {% data variables.product.prodname_code_scanning %} to run {% data variables.product.prodname_codeql %} analysis and third-party analysis. {% data variables.product.prodname_code_scanning_capc %} also supports running analysis natively using {% data variables.product.prodname_actions %} or externally using existing CI/CD infrastructure. The table below summarizes all the options available to users when you configure {% data variables.product.product_location %} to allow {% data variables.product.prodname_code_scanning %} using actions. +You can configure {% data variables.product.prodname_code_scanning %} to run {% data variables.product.prodname_codeql %} analysis and third-party analysis. {% data variables.product.prodname_code_scanning_capc %} also supports running analysis natively using {% data variables.product.prodname_actions %} or externally using existing CI/CD infrastructure. The table below summarizes all the options available to users when you configure {% data variables.location.product_location %} to allow {% data variables.product.prodname_code_scanning %} using actions. {% data reusables.code-scanning.enabling-options %} @@ -74,7 +74,7 @@ If you set up the {% data variables.product.prodname_codeql %} action sync tool, ### Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %} 1. If you want to download action workflows on demand from {% data variables.product.prodname_dotcom_the_website %}, you need to enable {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling {% data variables.product.prodname_github_connect %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud#enabling-github-connect)." -2. You'll also need to enable {% data variables.product.prodname_actions %} for {% data variables.product.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." +2. You'll also need to enable {% data variables.product.prodname_actions %} for {% data variables.location.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." 3. The next step is to configure access to actions on {% data variables.product.prodname_dotcom_the_website %} using {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." 4. Add a self-hosted runner to your repository, organization, or enterprise account. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." diff --git a/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md b/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md index 981a8e2f20..291f6f4906 100644 --- a/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md +++ b/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md @@ -1,7 +1,7 @@ --- -title: Configurar a varredura de segredo para o seu dispositivo +title: Configuring secret scanning for your appliance shortTitle: Configuring secret scanning -intro: 'Você pode habilitar, configurar e desabilitar {% data variables.product.prodname_secret_scanning %} para {% data variables.product.product_location %}. {% data variables.product.prodname_secret_scanning_caps %} permite aos usuários fazer a varredura de códigos para os segredos que se confirmaram acidentalmente.' +intro: 'You can enable, configure, and disable {% data variables.product.prodname_secret_scanning %} for {% data variables.location.product_location %}. {% data variables.product.prodname_secret_scanning_caps %} allows users to scan code for accidentally committed secrets.' product: '{% data reusables.gated-features.secret-scanning %}' miniTocMaxHeadingLevel: 3 redirect_from: @@ -15,58 +15,59 @@ topics: - Enterprise - Secret scanning - Security -ms.openlocfilehash: c44d724293b970ff3075deb1befb2f0eae427d5c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147066318' --- + {% data reusables.secret-scanning.beta %} -## Sobre a {% data variables.product.prodname_secret_scanning %} +## About {% data variables.product.prodname_secret_scanning %} -Se alguém verificar um segredo com um padrão conhecido em um repositório, {% data variables.product.prodname_secret_scanning %} irá pegar o segredo conforme o check-in e ajudará você a mitigar o impacto da fuga. Os administradores do repositório são notificados sobre qualquer submissão que contém um segredo e podem visualizar rapidamente todos os segredos detectados na aba Segurança do repositório. Para obter mais informações, confira "[Sobre a {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)". +If someone checks a secret with a known pattern into a repository, {% data variables.product.prodname_secret_scanning %} catches the secret as it's checked in, and helps you mitigate the impact of the leak. Repository administrators are notified about any commit that contains a secret, and they can quickly view all detected secrets in the Security tab for the repository. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)." -## Verificando se a sua licença inclui {% data variables.product.prodname_GH_advanced_security %} +## Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %} {% data reusables.advanced-security.check-for-ghas-license %} -## Pré-requisitos para {% data variables.product.prodname_secret_scanning %} +## Prerequisites for {% data variables.product.prodname_secret_scanning %} -- O sinalizador de CPU [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Extensões SIMD de Streaming Suplementar 3) precisa ser habilitado na VM/KVM que executa o {% data variables.product.product_location %}. +- The [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Supplemental Streaming SIMD Extensions 3) CPU flag needs to be enabled on the VM/KVM that runs {% data variables.location.product_location %}. -- Uma licença do {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghes %} (confira "[Sobre a cobrança do {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)"){% endif %} +- A license for {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghes %} (see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)"){% endif %} -- A {% data variables.product.prodname_secret_scanning_caps %} habilitada no console de gerenciamento (confira "[Como habilitar o {% data variables.product.prodname_GH_advanced_security %} para sua empresa](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)") +- {% data variables.product.prodname_secret_scanning_caps %} enabled in the management console (see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)") -### Verificar suporte para o sinalizador SSSE3 nos seus vCPUs +### Checking support for the SSSE3 flag on your vCPUs -O conjunto de instruções das SSSE3 é necessário porque o {% data variables.product.prodname_secret_scanning %} alavanca o padrão acelerado de hardware que corresponde para encontrar possíveis credenciais confirmadas com os seus repositórios de {% data variables.product.prodname_dotcom %}. SSSE3 está habilitado para a maioria das CPUs modernas. Você pode verificar se o SSSE3 está habilitado para oa vCPUs disponíveis para sua instância de {% data variables.product.prodname_ghe_server %}. +The SSSE3 set of instructions is required because {% data variables.product.prodname_secret_scanning %} leverages hardware accelerated pattern matching to find potential credentials committed to your {% data variables.product.prodname_dotcom %} repositories. SSSE3 is enabled for most modern CPUs. You can check whether SSSE3 is enabled for the vCPUs available to your {% data variables.product.prodname_ghe_server %} instance. -1. Conecte ao shell administrativo para sua instância de {% data variables.product.prodname_ghe_server %}. Para obter mais informações, confira "[Como acessar o shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)". -2. Insira o seguinte comando: +1. Connect to the administrative shell for your {% data variables.product.prodname_ghe_server %} instance. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." +2. Enter the following command: ```shell grep -iE '^flags.*ssse3' /proc/cpuinfo >/dev/null | echo $? ``` - Se isso retornar o valor `0`, isso significará que o sinalizador SSSE3 está disponível e habilitado. Agora você pode habilitar {% data variables.product.prodname_secret_scanning %} para {% data variables.product.product_location %}. Para obter mais informações, confira "[Como habilitar a {% data variables.product.prodname_secret_scanning %}](#enabling-secret-scanning)" abaixo. + If this returns the value `0`, it means that the SSSE3 flag is available and enabled. You can now enable {% data variables.product.prodname_secret_scanning %} for {% data variables.location.product_location %}. For more information, see "[Enabling {% data variables.product.prodname_secret_scanning %}](#enabling-secret-scanning)" below. - Se isso não retornar `0`, o SSSE3 não estará habilitado na VM/KVM. Você precisa consultar a documentação do hardware/hipervisor sobre como habilitar o sinalizador ou disponibilizá-lo para VMs convidados. + If this doesn't return `0`, SSSE3 is not enabled on your VM/KVM. You need to refer to the documentation of the hardware/hypervisor on how to enable the flag, or make it available to guest VMs. -## Como habilitar a {% data variables.product.prodname_secret_scanning %} +## Enabling {% data variables.product.prodname_secret_scanning %} {% data reusables.enterprise_management_console.enable-disable-security-features %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.advanced-security-tab %} -1. Em "Segurança", clique em **{% data variables.product.prodname_secret_scanning_caps %}** . -![Caixa de seleção usada para habilitar ou desabilitar a {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Under "Security," click **{% data variables.product.prodname_secret_scanning_caps %}**. +![Checkbox to enable or disable {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} -## Como desabilitar a {% data variables.product.prodname_secret_scanning %} +## Disabling {% data variables.product.prodname_secret_scanning %} {% data reusables.enterprise_management_console.enable-disable-security-features %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.advanced-security-tab %} -1. Em "Segurança", desmarque **{% data variables.product.prodname_secret_scanning_caps %}** . -![Caixa de seleção usada para habilitar ou desabilitar a {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Under "Security," unselect **{% data variables.product.prodname_secret_scanning_caps %}**. +![Checkbox to enable or disable {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md b/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md index e5f473d740..73832aee06 100644 --- a/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Como habilitar a Segurança Avançada do GitHub para sua empresa +title: Enabling GitHub Advanced Security for your enterprise shortTitle: Enabling GitHub Advanced Security -intro: 'É possível configurar o {% data variables.product.product_name %} para incluir o {% data variables.product.prodname_GH_advanced_security %}. Isso fornece recursos extras que ajudam os usuários a encontrar e corrigir problemas de segurança em seu código.' +intro: 'You can configure {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code.' product: '{% data reusables.gated-features.ghas %}' redirect_from: - /admin/advanced-security/enabling-github-advanced-security-for-your-enterprise @@ -14,72 +14,79 @@ topics: - Enterprise - Secret scanning - Security -ms.openlocfilehash: bc516af0c0788eeafe1b833c5627e471982e1c05 -ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147875525' --- -## Sobre habilitar {% data variables.product.prodname_GH_advanced_security %} + +## About enabling {% data variables.product.prodname_GH_advanced_security %} {% data reusables.advanced-security.ghas-helps-developers %} -{% ifversion ghes %} Quando você habilita o {% data variables.product.prodname_GH_advanced_security %} para sua empresa, os administradores de repositório em todas as organizações podem habilitar os recursos, a menos que você configure uma política para restringir o acesso. Para obter mais informações, confira "[Como impor políticas à {% data variables.product.prodname_advanced_security %} na sua empresa](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)". -{% else %} Quando você habilita o {% data variables.product.prodname_GH_advanced_security %} para sua empresa, os administradores de repositório em todas as organizações podem habilitar os recursos. {% endif %} - -{% ifversion ghes %} Para obter diretrizes sobre uma implantação em fases do GitHub Advanced Security, confira "[Introdução à adoção do GitHub Advanced Security em escala](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale)". +{% ifversion ghes %} +When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features unless you set up a policy to restrict access. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)." +{% else %} +When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features. {% endif %} -## Verificando se a sua licença inclui {% data variables.product.prodname_GH_advanced_security %} +{% ifversion ghes %} +For guidance on a phased deployment of GitHub Advanced Security, see "[Introduction to adopting GitHub Advanced Security at scale](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale)." +{% endif %} -{% ifversion ghes %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -1. Se sua licença incluir {% data variables.product.prodname_GH_advanced_security %}, a página de licença incluirá uma seção que mostra os detalhes do uso atual. -![Seção {% data variables.product.prodname_GH_advanced_security %} da licença Enterprise](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png) {% endif %} +## Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %} -## Pré-requisitos para habilitar {% data variables.product.prodname_GH_advanced_security %} +{% ifversion ghes %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.license-tab %} +1. If your license includes {% data variables.product.prodname_GH_advanced_security %}, the license page includes a section showing details of current usage. +![{% data variables.product.prodname_GH_advanced_security %} section of Enterprise license](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png) +{% endif %} -1. Faça upgrade da sua licença do {% data variables.product.product_name %} para incluir o {% data variables.product.prodname_GH_advanced_security %}.{% ifversion ghes %} Para obter informações sobre licenciamento, confira "[Sobre a cobrança do {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)".{% endif %} -2. Faça o download do novo arquivo de licença. Para obter mais informações, confira "[Como baixar sua licença do {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)". -3. Faça o upload do novo arquivo de licença para {% data variables.product.product_location %}. Para obter mais informações, confira "[Como carregar uma nova licença do {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)".{% ifversion ghes %} -4. Revise os pré-requisitos para as funcionalidades que você pretende habilitar. +## Prerequisites for enabling {% data variables.product.prodname_GH_advanced_security %} - - {% data variables.product.prodname_code_scanning_capc %}, confira "[Como configurar a {% data variables.product.prodname_code_scanning %} para seu dispositivo](/admin/advanced-security/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)". - - {% data variables.product.prodname_secret_scanning_caps %}, confira "[Como configurar a {% data variables.product.prodname_secret_scanning %} para seu dispositivo](/admin/advanced-security/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)".{% endif %} - - {% data variables.product.prodname_dependabot %}, confira "[Como habilitar o {% data variables.product.prodname_dependabot %} para sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)". +1. Upgrade your license for {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}.{% ifversion ghes %} For information about licensing, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% endif %} +2. Download the new license file. For more information, see "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)." +3. Upload the new license file to {% data variables.location.product_location %}. For more information, see "[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% ifversion ghes %} +4. Review the prerequisites for the features you plan to enable. -## Habilitar e desabilitar funcionalidades de {% data variables.product.prodname_GH_advanced_security %} + - {% data variables.product.prodname_code_scanning_capc %}, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)." + - {% data variables.product.prodname_secret_scanning_caps %}, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/admin/advanced-security/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)."{% endif %} + - {% data variables.product.prodname_dependabot %}, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." + +## Enabling and disabling {% data variables.product.prodname_GH_advanced_security %} features {% data reusables.enterprise_management_console.enable-disable-security-features %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.advanced-security-tab %}{% ifversion ghes %} -1. Em "Segurança", marque os recursos que deseja habilitar e desmarque os que deseja desabilitar. -{% ifversion ghes %}![Caixa de seleção para habilitar ou desabilitar recursos do {% data variables.product.prodname_advanced_security %}](/assets/images/enterprise/3.2/management-console/enable-security-checkboxes.png){% else %}![Caixa de seleção para habilitar ou desabilitar recursos do {% data variables.product.prodname_advanced_security %}](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png){% endif %}{% else %} -1. Em "{% data variables.product.prodname_advanced_security %}", clique em **{% data variables.product.prodname_code_scanning_capc %}** . -![Caixa de seleção usada para habilitar ou desabilitar a {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/enable-code-scanning-checkbox.png){% endif %} {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %}{% ifversion ghes %} +1. Under "Security," select the features that you want to enable and deselect any features you want to disable. +{% ifversion ghes %}![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/3.2/management-console/enable-security-checkboxes.png){% else %}![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png){% endif %}{% else %} +1. Under "{% data variables.product.prodname_advanced_security %}," click **{% data variables.product.prodname_code_scanning_capc %}**. +![Checkbox to enable or disable {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/enable-code-scanning-checkbox.png){% endif %} +{% data reusables.enterprise_management_console.save-settings %} -Quando {% data variables.product.product_name %} terminar de reiniciar, você estará pronto para definir todas as funcionalidades adicionais necessárias para recursos recém-habilitados. Para obter mais informações, confira "[Como configurar a {% data variables.product.prodname_code_scanning %} para seu dispositivo](/admin/advanced-security/configuring-code-scanning-for-your-appliance)". +When {% data variables.product.product_name %} has finished restarting, you're ready to set up any additional resources required for newly enabled features. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance)." -## Habilitar ou desabilitar as funcionalidades de {% data variables.product.prodname_GH_advanced_security %} por meio do shell administrativo (SSH) +## Enabling or disabling {% data variables.product.prodname_GH_advanced_security %} features via the administrative shell (SSH) -Você pode habilitar ou desabilitar as funcionalidades programaticamente em {% data variables.product.product_location %}. Para obter mais informações sobre o shell administrativo e os utilitários de linha de comando do {% data variables.product.prodname_ghe_server %}, confira "[Como acessar o shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" e "[Utilitários de linha de comando](/admin/configuration/command-line-utilities#ghe-config)". +You can enable or disable features programmatically on {% data variables.location.product_location %}. For more information about the administrative shell and command-line utilities for {% data variables.product.prodname_ghe_server %}, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[Command-line utilities](/admin/configuration/command-line-utilities#ghe-config)." -Por exemplo, você pode habilitar qualquer recurso de {% data variables.product.prodname_GH_advanced_security %} com as suas ferramentas de código de infraestrutura ao implantar uma instância para preparação ou recuperação de desastres. +For example, you can enable any {% data variables.product.prodname_GH_advanced_security %} feature with your infrastructure-as-code tooling when you deploy an instance for staging or disaster recovery. -1. Entre com o SSH no {% data variables.product.product_location %}. -1. Habilitar funcionalidades para {% data variables.product.prodname_GH_advanced_security %}. +1. SSH into {% data variables.location.product_location %}. +1. Enable features for {% data variables.product.prodname_GH_advanced_security %}. - - Para habilitar {% data variables.product.prodname_code_scanning_capc %}, digite os comandos a seguir. + - To enable {% data variables.product.prodname_code_scanning_capc %}, enter the following commands. ```shell ghe-config app.minio.enabled true ghe-config app.code-scanning.enabled true ``` - - Para habilitar {% data variables.product.prodname_secret_scanning_caps %}, digite o comando a seguir. + - To enable {% data variables.product.prodname_secret_scanning_caps %}, enter the following command. ```shell ghe-config app.secret-scanning.enabled true ``` - - Para habilitar o grafo de dependência, insira {% ifversion ghes %}o comando{% else %}os comandos{% endif %} a seguir. - {% ifversion ghes %}```shell ghe-config app.dependency-graph.enabled true + - To enable the dependency graph, enter the following {% ifversion ghes %}command{% else %}commands{% endif %}. + {% ifversion ghes %}```shell + ghe-config app.dependency-graph.enabled true ``` {% else %}```shell ghe-config app.github.dependency-graph-enabled true @@ -92,12 +99,13 @@ Por exemplo, você pode habilitar qualquer recurso de {% data variables.product. ghe-config app.minio.enabled false ghe-config app.code-scanning.enabled false ``` - - Para desabilitar {% data variables.product.prodname_secret_scanning %}, digite o seguinte comando. + - To disable {% data variables.product.prodname_secret_scanning %}, enter the following command. ```shell ghe-config app.secret-scanning.enabled false ``` - - Para desabilitar o grafo de dependência, insira {% ifversion ghes %}o comando{% else %}os comandos{% endif %} a seguir. - {% ifversion ghes %}```shell ghe-config app.dependency-graph.enabled false + - To disable the dependency graph, enter the following {% ifversion ghes %}command{% else %}commands{% endif %}. + {% ifversion ghes %}```shell + ghe-config app.dependency-graph.enabled false ``` {% else %}```shell ghe-config app.github.dependency-graph-enabled false diff --git a/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md b/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md index 1a8e9d20e5..ee72a7d813 100644 --- a/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Sobre a segurança da cadeia de suprimento da sua empresa -intro: Você pode habilitar recursos que ajudam seus desenvolvedores a entender e atualizar as dependências das quais o código do seu projeto depende. +title: About supply chain security for your enterprise +intro: You can enable features that help your developers understand and update the dependencies their code relies on. shortTitle: About supply chain security permissions: '' versions: @@ -11,15 +11,10 @@ topics: - Enterprise - Security - Dependency graph -ms.openlocfilehash: f99085f6c484869623a81c7585216aca936929e1 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145096008' --- -Você pode permitir que os usuários identifiquem as dependências dos projetos {% ifversion ghes %}habilitando{% elsif ghae %}usando{% endif %} o grafo de dependência para o {% data variables.product.product_location %}. Para obter mais informações, confira "{% ifversion ghes %}[Como habilitar o grafo de dependência para sua empresa](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise){% elsif ghae %}[Sobre o grafo de dependência](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph){% endif %}". -Você também pode permitir que os usuários do {% data variables.product.product_location %} encontrem e corrijam vulnerabilidades nas dependências do código habilitando os {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} e as {% data variables.product.prodname_dependabot_updates %}{% endif %}. Para obter mais informações, confira "[Como habilitar o {% data variables.product.prodname_dependabot %} para sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)". +You can allow users to identify their projects' dependencies by {% ifversion ghes %}enabling{% elsif ghae %}using{% endif %} the dependency graph for {% data variables.location.product_location %}. For more information, see "{% ifversion ghes %}[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise){% elsif ghae %}[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph){% endif %}." -Depois de habilitar o {% data variables.product.prodname_dependabot_alerts %}, você poderá ver os dados da vulnerabilidade de {% data variables.product.prodname_advisory_database %} em {% data variables.product.product_location %} e sincronizar manualmente os dados. Para obter mais informações, confira "[Como ver os dados de vulnerabilidade da sua empresa](/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise)". +You can also allow users on {% data variables.location.product_location %} to find and fix vulnerabilities in their code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." + +After you enable {% data variables.product.prodname_dependabot_alerts %}, you can view vulnerability data from the {% data variables.product.prodname_advisory_database %} on {% data variables.location.product_location %} and manually sync the data. For more information, see "[Viewing the vulnerability data for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise)." diff --git a/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md b/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md index 6a09b3c3d8..d4d24029d2 100644 --- a/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Habilitando o gráfico de dependências para a sua empresa -intro: Você pode permitir que os usuários identifiquem as dependências dos seus projetos habilitando o gráfico de dependências. +title: Enabling the dependency graph for your enterprise +intro: You can allow users to identify their projects' dependencies by enabling the dependency graph. shortTitle: Enable dependency graph permissions: Site administrators can enable the dependency graph. versions: @@ -10,34 +10,37 @@ topics: - Enterprise - Security - Dependency graph -ms.openlocfilehash: 6d4ba1a4e69c557a359bb0e99b02d92ff5fb99e0 -ms.sourcegitcommit: dc42bb4a4826b414751ffa9eed38962c3e3fea8e -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 07/13/2022 -ms.locfileid: '147062279' --- -## Sobre o gráfico de dependências -{% data reusables.dependabot.about-the-dependency-graph %} Para obter mais informações, confira "[Sobre o grafo de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" +## About the dependency graph -Depois de habilitar o grafo de dependência da empresa, você pode habilitar o {% data variables.product.prodname_dependabot %} para detectar as dependências vulneráveis no repositório{% ifversion ghes > 3.2 %} e corrigir as vulnerabilidades automaticamente{% endif %}. Para obter mais informações, confira "[Como habilitar o {% data variables.product.prodname_dependabot %} para sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)". +{% data reusables.dependabot.about-the-dependency-graph %} For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" -{% ifversion ghes %} Você pode habilitar o grafo de dependência por meio do {% data variables.enterprise.management_console %} ou do shell administrativo. Recomendamos usar o {% data variables.enterprise.management_console %}, a menos que {% data variables.product.product_location %} use clustering. +After you enable the dependency graph for your enterprise, you can enable {% data variables.product.prodname_dependabot %} to detect insecure dependencies in your repository{% ifversion ghes > 3.2 %} and automatically fix the vulnerabilities{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." -## Habilitando o gráfico de dependências por meio do {% data variables.enterprise.management_console %} +{% ifversion ghes %} +You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend using the {% data variables.enterprise.management_console %} unless {% data variables.location.product_location %} uses clustering. -Se o seu {% data variables.product.product_location %} usar clustering, você não poderá habilitar o gráfico de dependências com o {% data variables.enterprise.management_console %} e deverá usar o shell administrativo. Para obter mais informações, confira "[Como habilitar o grafo de dependência por meio do shell administrativo](#enabling-the-dependency-graph-via-the-administrative-shell)". +## Enabling the dependency graph via the {% data variables.enterprise.management_console %} -{% data reusables.enterprise_site_admin_settings.sign-in %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.advanced-security-tab %} -1. Em "Segurança", clique em **Grafo de dependência**. -![Caixa de seleção usada para habilitar ou desabilitar o grafo de dependência](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png) {% data reusables.enterprise_management_console.save-settings %} -1. Clique em **Acessar sua instância**. +If {% data variables.location.product_location %} uses clustering, you cannot enable the dependency graph with the {% data variables.enterprise.management_console %} and must use the administrative shell instead. For more information, see "[Enabling the dependency graph via the administrative shell](#enabling-the-dependency-graph-via-the-administrative-shell)." -## Habilitando o gráfico de dependências por meio do shell administrativo +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Under "Security," click **Dependency graph**. +![Checkbox to enable or disable the dependency graph](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} +1. Click **Visit your instance**. -{% endif %} {% data reusables.enterprise_site_admin_settings.sign-in %} -1. No shell administrativo, habilite o grafo de dependência no {% data variables.product.product_location %}: {% ifversion ghes %}```shell ghe-config app.dependency-graph.enabled true +## Enabling the dependency graph via the administrative shell + +{% endif %} +{% data reusables.enterprise_site_admin_settings.sign-in %} +1. In the administrative shell, enable the dependency graph on {% data variables.location.product_location %}: + {% ifversion ghes %}```shell + ghe-config app.dependency-graph.enabled true ``` {% else %}```shell ghe-config app.github.dependency-graph-enabled true @@ -52,4 +55,4 @@ Se o seu {% data variables.product.product_location %} usar clustering, você n ```shell $ ghe-config-apply ``` -3. Volte para o {% data variables.product.prodname_ghe_server %}. +3. Return to {% data variables.product.prodname_ghe_server %}. diff --git a/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md b/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md index d8c59147c6..b20b4c62a4 100644 --- a/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md @@ -1,8 +1,8 @@ --- -title: Visualizando os dados de vulnerabilidade para a sua empresa -intro: 'Você pode visualizar os dados de vulnerabilidades a partir de {% data variables.product.prodname_advisory_database %} em {% data variables.product.product_location %}.' +title: Viewing the vulnerability data for your enterprise +intro: 'You can view vulnerability data from the {% data variables.product.prodname_advisory_database %} on {% data variables.location.product_location %}.' shortTitle: View vulnerability data -permissions: 'Site administrators can view vulnerability data on {% data variables.product.product_location %}.' +permissions: 'Site administrators can view vulnerability data on {% data variables.location.product_location %}.' versions: ghes: '*' ghae: '*' @@ -11,22 +11,17 @@ topics: - Enterprise - Security - Dependency graph -ms.openlocfilehash: a9217f4cff35a675d87833e3fdad37ac9fe10665 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145094041' --- -Se {% data variables.product.prodname_dependabot_alerts %} estiver habilitado para a sua empresa, você poderá visualizar todas as vulnerabilidades que foram baixadas para {% data variables.product.product_location %} de {% data variables.product.prodname_advisory_database %}. -Você pode sincronizar manualmente dados de vulnerabilidade de {% data variables.product.prodname_dotcom_the_website %} para atualizar a lista. +If {% data variables.product.prodname_dependabot_alerts %} are enabled for your enterprise, you can view all vulnerabilities that were downloaded to {% data variables.location.product_location %} from the {% data variables.product.prodname_advisory_database %}. -Antes de ver os dados da vulnerabilidade, você deverá habilitar {% data variables.product.prodname_dependabot_alerts %}. Para obter mais informações, confira "[Como habilitar o {% data variables.product.prodname_dependabot %} para sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)". +You can manually sync vulnerability data from {% data variables.product.prodname_dotcom_the_website %} to update the list. + +Before you can view vulnerability data, you must enable {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% data reusables.enterprise_site_admin_settings.access-settings %} -2. Na barra lateral esquerda, clique em **Vulnerabilidades**. - ![Guia Vulnerabilidades na barra lateral de administração do site](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png) -3. Para sincronizar dados de vulnerabilidade, clique em **Sincronizar Vulnerabilidades agora**. - ![Botão Sincronizar vulnerabilidades agora](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png) +2. In the left sidebar, click **Vulnerabilities**. + ![Vulnerabilities tab in the site admin sidebar](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png) +3. To sync vulnerability data, click **Sync Vulnerabilities now**. + ![Sync vulnerabilities now button](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png) diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md index 4b900f7f44..4b26af2b8e 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md @@ -13,28 +13,28 @@ miniTocMaxHeadingLevel: 3 ## About {% data variables.product.prodname_github_connect %} -{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by allowing {% data variables.product.product_location %} to benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}. +{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by allowing {% data variables.location.product_location %} to benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}. -{% data variables.product.prodname_github_connect %} does not open {% data variables.product.product_location %} to the public internet. None of your enterprise's private data is exposed to {% data variables.product.prodname_dotcom_the_website %} users. Instead, {% data variables.product.prodname_github_connect %} transmits only the limited data needed for the individual features you choose to enable. Unless you enable license sync, no personal data is transmitted by {% data variables.product.prodname_github_connect %}. For more information about what data is transmitted by {% data variables.product.prodname_github_connect %}, see "[Data transmission for {% data variables.product.prodname_github_connect %}](#data-transmission-for-github-connect)." +{% data variables.product.prodname_github_connect %} does not open {% data variables.location.product_location %} to the public internet. None of your enterprise's private data is exposed to {% data variables.product.prodname_dotcom_the_website %} users. Instead, {% data variables.product.prodname_github_connect %} transmits only the limited data needed for the individual features you choose to enable. Unless you enable license sync, no personal data is transmitted by {% data variables.product.prodname_github_connect %}. For more information about what data is transmitted by {% data variables.product.prodname_github_connect %}, see "[Data transmission for {% data variables.product.prodname_github_connect %}](#data-transmission-for-github-connect)." Enabling {% data variables.product.prodname_github_connect %} will not allow {% data variables.product.prodname_dotcom_the_website %} users to make changes to {% data variables.product.product_name %}. -To enable {% data variables.product.prodname_github_connect %}, you configure a connection between {% data variables.product.product_location %} and an organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that uses {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)." +To enable {% data variables.product.prodname_github_connect %}, you configure a connection between {% data variables.location.product_location %} and an organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that uses {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)." After enabling {% data variables.product.prodname_github_connect %}, you will be able to enable features such as {% ifversion ghes %}automatic user license sync and {% endif %}{% data variables.product.prodname_dependabot_alerts %}. For more information about all of the features available, see "[{% data variables.product.prodname_github_connect %} features](#github-connect-features)." ## {% data variables.product.prodname_github_connect %} features -After you configure the connection between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %}, you can enable individual features of {% data variables.product.prodname_github_connect %} for your enterprise. +After you configure the connection between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %}, you can enable individual features of {% data variables.product.prodname_github_connect %} for your enterprise. Feature | Description | More information | ------- | ----------- | ---------------- |{% ifversion ghes %} -Automatic user license sync | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae %} +Automatic user license sync | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.location.product_location %} to {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae %} {% data variables.product.prodname_dependabot %} | Allow users to find and fix vulnerabilities in code dependencies. | "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %} {% data variables.product.prodname_dotcom_the_website %} actions | Allow users to use actions from {% data variables.product.prodname_dotcom_the_website %} in workflow files. | "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% ifversion server-statistics %} {% data variables.product.prodname_server_statistics %} | Analyze your own aggregate data from GitHub Enterprise Server, and help us improve GitHub products. | "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %} -Unified search | Allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.product.product_location %}. | "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" -Unified contributions | Allow users to include anonymized contribution counts for their work on {% data variables.product.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}. | "[Enabling {% data variables.product.prodname_unified_contributions %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)" +Unified search | Allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.location.product_location %}. | "[Enabling {% data variables.enterprise.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" +Unified contributions | Allow users to include anonymized contribution counts for their work on {% data variables.location.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}. | "[Enabling {% data variables.enterprise.prodname_unified_contributions %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)" ## Data transmission for {% data variables.product.prodname_github_connect %} @@ -53,17 +53,17 @@ When you enable {% data variables.product.prodname_github_connect %} or specific - The public key portion of your {% data variables.product.prodname_ghe_server %} license - A hash of your {% data variables.product.prodname_ghe_server %} license - The customer name on your {% data variables.product.prodname_ghe_server %} license -- The version of {% data variables.product.product_location_enterprise %}{% endif %} -- The hostname of {% data variables.product.product_location %} -- The organization or enterprise account on {% data variables.product.prodname_ghe_cloud %} that's connected to {% data variables.product.product_location %} -- The authentication token that's used by {% data variables.product.product_location %} to make requests to {% data variables.product.prodname_ghe_cloud %} -- If Transport Layer Security (TLS) is enabled and configured on {% data variables.product.product_location %}{% ifversion ghes %} -- The {% data variables.product.prodname_github_connect %} features that are enabled on {% data variables.product.product_location %}, and the date and time of enablement{% endif %} +- The version of {% data variables.location.product_location_enterprise %}{% endif %} +- The hostname of {% data variables.location.product_location %} +- The organization or enterprise account on {% data variables.product.prodname_ghe_cloud %} that's connected to {% data variables.location.product_location %} +- The authentication token that's used by {% data variables.location.product_location %} to make requests to {% data variables.product.prodname_ghe_cloud %} +- If Transport Layer Security (TLS) is enabled and configured on {% data variables.location.product_location %}{% ifversion ghes %} +- The {% data variables.product.prodname_github_connect %} features that are enabled on {% data variables.location.product_location %}, and the date and time of enablement{% endif %} - The dormancy threshold for your enterprise - The number of dormant users for your enterprise - A count of license-consuming seats, which does not include suspended users -{% data variables.product.prodname_github_connect %} syncs the above connection data between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %} weekly, from the day and approximate time that {% data variables.product.prodname_github_connect %} was enabled. +{% data variables.product.prodname_github_connect %} syncs the above connection data between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %} weekly, from the day and approximate time that {% data variables.product.prodname_github_connect %} was enabled. ### Data transmitted by individual features of {% data variables.product.prodname_github_connect %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md index 9e043a958a..4f4bff2a29 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Habilitando a sincronização automática de licença de usuário para sua empresa -intro: 'Você pode gerenciar o uso da licença entre os seus ambientes de {% data variables.product.prodname_enterprise %} sincronizando automaticamente as licenças de usuário de {% data variables.product.product_location %} com {% data variables.product.prodname_ghe_cloud %}.' +title: Enabling automatic user license sync for your enterprise +intro: 'You can manage license usage across your {% data variables.product.prodname_enterprise %} environments by automatically syncing user licenses from {% data variables.location.product_location %} to {% data variables.product.prodname_ghe_cloud %}.' redirect_from: - /enterprise/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud - /enterprise/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud @@ -16,33 +16,28 @@ topics: - GitHub Connect - Licensing shortTitle: Automatic user license sync -ms.openlocfilehash: eb0216dcdb629e96ef83de2eea8a7d7b6660a171 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145910556' --- -## Sobre a sincronização automática de licenças +## About automatic license synchronization {% data reusables.enterprise-licensing.unique-user-licensing-model %} -{% data reusables.enterprise-licensing.about-license-sync %} Para obter mais informações, confira "[Sobre {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect#data-transmission-for-github-connect)". +{% data reusables.enterprise-licensing.about-license-sync %} For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect#data-transmission-for-github-connect)." -Se você habilitar a sincronização automática de licença do usuário em sua empresa, o {% data variables.product.prodname_github_connect %} sincronizará automaticamente o uso de licenças entre o {% data variables.product.prodname_ghe_server %} e o {% data variables.product.prodname_ghe_cloud %} semanalmente.{% ifversion ghes > 3.4 %} Você também pode sincronizar seus dados de licença a qualquer momento fora da sincronização semanal automática, disparando manualmente um trabalho de sincronização de licença. Para obter mais informações, confira "[Disparando um trabalho de sincronização de licenças](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud#triggering-a-license-sync-job)".{% endif %} +If you enable automatic user license sync for your enterprise, {% data variables.product.prodname_github_connect %} will automatically synchronize license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} weekly.{% ifversion ghes > 3.4 %} You can also synchronize your license data at any time outside of the automatic weekly sync, by manually triggering a license sync job. For more information, see "[Triggering a license sync job](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud#triggering-a-license-sync-job)."{% endif %} -Se você usar várias instâncias de {% data variables.product.prodname_ghe_server %}, você pode habilitar a sincronização automática de licença entre cada uma de suas instâncias e a mesma organização ou conta corporativa em {% data variables.product.prodname_ghe_cloud %}. +If you use multiple {% data variables.product.prodname_ghe_server %} instances, you can enable automatic license sync between each of your instances and the same organization or enterprise account on {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise-licensing.view-consumed-licenses %} -Você também pode fazer upload manualmente das informações de licença do usuário do {% data variables.product.prodname_ghe_server %} para o {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, confira "[Sincronizando o uso de licenças entre o {% data variables.product.prodname_ghe_server %} e o {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)". +You can also manually upload {% data variables.product.prodname_ghe_server %} user license information to {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)." {% data reusables.enterprise-licensing.verified-domains-license-sync %} -## Habilitar a sincronização de licenças +## Enabling license synchronization -Antes de habilitar a sincronização de licença em {% data variables.product.product_location %}, você deverá habilitar {% data variables.product.prodname_github_connect %}. Para obter mais informações, confira "[Como gerenciar o {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)". +Before enabling license synchronization on {% data variables.location.product_location %}, you must enable {% data variables.product.prodname_github_connect %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)." -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %} -1. Em "O servidor pode sincronizar a contagem e o uso de licenças de usuários", use o menu suspenso e selecione **Habilitado**. - ![Menu suspenso para habilitar a sincronização automática de licenças de usuários](/assets/images/enterprise/site-admin-settings/enable-user-license-drop-down.png) +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.github-connect-tab %} +1. Under "Server can sync user license count and usage", use the drop-down menu and select **Enabled**. + ![Drop-down menu to enable automatic user license sync](/assets/images/enterprise/site-admin-settings/enable-user-license-drop-down.png) diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md index 65a19be5d0..8fa01e4e0d 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md @@ -1,6 +1,6 @@ --- title: Enabling Dependabot for your enterprise -intro: 'You can allow users of {% data variables.product.product_location %} to find and fix vulnerabilities in code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}.' +intro: 'You can allow users of {% data variables.location.product_location %} to find and fix vulnerabilities in code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}.' miniTocMaxHeadingLevel: 3 shortTitle: Dependabot redirect_from: @@ -26,14 +26,14 @@ topics: ## About {% data variables.product.prodname_dependabot %} for {% data variables.product.product_name %} -{% data variables.product.prodname_dependabot %} helps users of {% data variables.product.product_location %} find and fix vulnerabilities in their dependencies.{% ifversion ghes > 3.2 %} You can enable {% data variables.product.prodname_dependabot_alerts %} to notify users about vulnerable dependencies and {% data variables.product.prodname_dependabot_updates %} to fix the vulnerabilities and keep dependencies updated to the latest version. +{% data variables.product.prodname_dependabot %} helps users of {% data variables.location.product_location %} find and fix vulnerabilities in their dependencies.{% ifversion ghes > 3.2 %} You can enable {% data variables.product.prodname_dependabot_alerts %} to notify users about vulnerable dependencies and {% data variables.product.prodname_dependabot_updates %} to fix the vulnerabilities and keep dependencies updated to the latest version. ### About {% data variables.product.prodname_dependabot_alerts %} {% endif %} {% data reusables.dependabot.dependabot-alerts-beta %} -With {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dotcom %} identifies insecure dependencies in repositories and creates alerts on {% data variables.product.product_location %}, using data from the {% data variables.product.prodname_advisory_database %} and the dependency graph service. +With {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dotcom %} identifies insecure dependencies in repositories and creates alerts on {% data variables.location.product_location %}, using data from the {% data variables.product.prodname_advisory_database %} and the dependency graph service. {% data reusables.repositories.tracks-vulnerabilities %} @@ -43,20 +43,20 @@ You can also choose to manually sync vulnerability data at any time. For more in {% note %} -**Note:** When you enable {% data variables.product.prodname_dependabot_alerts %}, no code or information about code from {% data variables.product.product_location %} is uploaded to {% data variables.product.prodname_dotcom_the_website %}. +**Note:** When you enable {% data variables.product.prodname_dependabot_alerts %}, no code or information about code from {% data variables.location.product_location %} is uploaded to {% data variables.product.prodname_dotcom_the_website %}. {% endnote %} -When {% data variables.product.product_location %} receives information about a vulnerability, it identifies repositories in {% data variables.product.product_location %} that use the affected version of the dependency and generates {% data variables.product.prodname_dependabot_alerts %}. You can choose whether or not to notify users automatically about new {% data variables.product.prodname_dependabot_alerts %}. +When {% data variables.location.product_location %} receives information about a vulnerability, it identifies repositories in {% data variables.location.product_location %} that use the affected version of the dependency and generates {% data variables.product.prodname_dependabot_alerts %}. You can choose whether or not to notify users automatically about new {% data variables.product.prodname_dependabot_alerts %}. -For repositories with {% data variables.product.prodname_dependabot_alerts %} enabled, scanning is triggered on any push to the default branch that contains a manifest file or lock file. Additionally, when a new vulnerability record is added to {% data variables.product.product_location %}, {% data variables.product.product_name %} scans all existing repositories on {% data variables.product.product_location %} and generates alerts for any repository that is vulnerable. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +For repositories with {% data variables.product.prodname_dependabot_alerts %} enabled, scanning is triggered on any push to the default branch that contains a manifest file or lock file. Additionally, when a new vulnerability record is added to {% data variables.location.product_location %}, {% data variables.product.product_name %} scans all existing repositories on {% data variables.location.product_location %} and generates alerts for any repository that is vulnerable. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." {% ifversion ghes > 3.2 %} ### About {% data variables.product.prodname_dependabot_updates %} {% data reusables.dependabot.beta-security-and-version-updates %} -After you enable {% data variables.product.prodname_dependabot_alerts %}, you can choose to enable {% data variables.product.prodname_dependabot_updates %}. When {% data variables.product.prodname_dependabot_updates %} are enabled for {% data variables.product.product_location %}, users can configure repositories so that their dependencies are updated and kept secure automatically. +After you enable {% data variables.product.prodname_dependabot_alerts %}, you can choose to enable {% data variables.product.prodname_dependabot_updates %}. When {% data variables.product.prodname_dependabot_updates %} are enabled for {% data variables.location.product_location %}, users can configure repositories so that their dependencies are updated and kept secure automatically. {% note %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md index 9909eaa022..e42ff2fafe 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Habilitar estatísticas de servidor para sua empresa -intro: 'Você pode analisar os seus dados de agregação do {% data variables.product.prodname_ghe_server %} e nos ajudar a aprimorar os produtos {% data variables.product.company_short %} habilitando o {% data variables.product.prodname_server_statistics %}.' +title: Enabling Server Statistics for your enterprise +intro: 'You can analyze your own aggregate data from {% data variables.product.prodname_ghe_server %} and help us improve {% data variables.product.company_short %} products by enabling {% data variables.product.prodname_server_statistics %}.' versions: feature: server-statistics redirect_from: @@ -8,27 +8,23 @@ redirect_from: topics: - Enterprise shortTitle: Server Statistics -ms.openlocfilehash: badfdb8abfbe468768ef9a32e183f67633915b54 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147409000' --- -## Sobre {% data variables.product.prodname_server_statistics %} -O {% data variables.product.prodname_server_statistics %} coleta dados de uso agregados do {% data variables.product.product_location %}, que você pode usar para antecipar melhor as necessidades de sua organização, entender como sua equipe funciona e mostrar o valor obtido do {% data variables.product.prodname_ghe_server %}. +## About {% data variables.product.prodname_server_statistics %} -O {% data variables.product.prodname_server_statistics %} coleta apenas determinadas métricas de agregação em repositórios, problemas, solicitações de pull e outros recursos. Conteúdo do {% data variables.product.prodname_dotcom %}, como código, problemas, comentários ou conteúdo de solicitação de pull, não é coletado. Para obter mais informações, confira "[Sobre {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)". +{% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.location.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. -Ao habilitar {% data variables.product.prodname_server_statistics %}, você também está ajudando a melhorar o {% data variables.product.company_short %}. Os dados agregados que você fornecerá nos ajudam a entender como nossos clientes estão usando o {% data variables.product.prodname_dotcom %}e tomar decisões de produto melhores e mais informadas, beneficiando você. +{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features.{% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)." -## Habilitar {% data variables.product.prodname_server_statistics %} +By enabling {% data variables.product.prodname_server_statistics %}, you are also helping to improve {% data variables.product.company_short %}. The aggregated data you will provide helps us understand how our customers are using {% data variables.product.prodname_dotcom %}, and make better and more informed product decisions, ultimately benefiting you. -Antes de habilitar {% data variables.product.prodname_server_statistics %}, você deve primeiro conectar sua instância do {% data variables.product.prodname_ghe_server %} ao {% data variables.product.prodname_dotcom_the_website %} por meio do {% data variables.product.prodname_github_connect %}. Para obter mais informações, confira "[Como conectar o {% data variables.product.prodname_ghe_server %} ao {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@3.1/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)". +## Enabling {% data variables.product.prodname_server_statistics %} -Você pode desabilitar {% data variables.product.prodname_server_statistics %} do {% data variables.product.prodname_ghe_server %} a qualquer momento. +Before you can enable {% data variables.product.prodname_server_statistics %}, you must first connect your {% data variables.product.prodname_ghe_server %} instance to {% data variables.product.prodname_dotcom_the_website %} through {% data variables.product.prodname_github_connect %}. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@3.1/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)." -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %} -4. Em "Compartilhar estatísticas do servidor com GitHub.com", selecione o menu suspenso e clique em **Habilitado** ou **Desabilitado**. - ![Captura de tela do menu suspenso de {% data variables.product.prodname_server_statistics %} com opções desabilitadas ou habilitadas](/assets/images/help/server-statistics/server-statistics-enable-disable-options.png) +You can disable {% data variables.product.prodname_server_statistics %} from {% data variables.product.prodname_ghe_server %} at any time. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.github-connect-tab %} +4. Under "Share server statistics with GitHub.com", select the dropdown menu and click **Enabled** or **Disabled**. + ![Screenshot of {% data variables.product.prodname_server_statistics %} drop-down menu with disabled or enabled options](/assets/images/help/server-statistics/server-statistics-enable-disable-options.png) diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md index e3b726e5f5..e9c67f0fcd 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Habilitando contribuições unificadas para a sua empresa +title: Enabling unified contributions for your enterprise shortTitle: Unified contributions -intro: 'Você pode permitir que os usuários incluam o número de contribuições anonimizadas pelo trabalho deles em {% data variables.product.product_location %} nos seus gráficos de contribuição em {% data variables.product.prodname_dotcom_the_website %}.' +intro: 'You can allow users to include anonymized contribution counts for their work on {% data variables.location.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}.' redirect_from: - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-and-github-com - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-github-com @@ -11,7 +11,7 @@ redirect_from: - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-contributions-between-github-enterprise-server-and-githubcom - /admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom -permissions: 'Enterprise owners can enable unified contributions between {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.' +permissions: 'Enterprise owners can enable unified contributions between {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.' versions: ghes: '*' ghae: '*' @@ -19,37 +19,36 @@ type: how_to topics: - Enterprise - GitHub Connect -ms.openlocfilehash: af07f30a8f164f6bec3d3c0f44c77181f1e8db7b -ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147875468' --- + {% data reusables.github-connect.beta %} -## Sobre contribuições unificadas +## About unified contributions -Como proprietário de uma empresa, você pode permitir que os usuários finais enviem contagens de contribuições anônimas pelo trabalho deles de {% data variables.product.product_location %} para seu gráfico de contribuição de {% data variables.product.prodname_dotcom_the_website %}. +As an enterprise owner, you can allow end users to send anonymized contribution counts for their work from {% data variables.location.product_location %} to their {% data variables.product.prodname_dotcom_the_website %} contribution graph. -Após habilitar {% data variables.product.prodname_unified_contributions %}, antes que os usuários individuais possam enviar contagens de contribuição de {% data variables.product.product_location %} para {% data variables.product.prodname_dotcom_the_website %}, cada usuário também deverá conectar sua conta de usuário em {% data variables.product.product_name %} com uma conta pessoal em {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, confira "[Como enviar contribuições corporativas para o seu perfil do {% data variables.product.prodname_dotcom_the_website %}](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)". +After you enable {% data variables.enterprise.prodname_unified_contributions %}, before individual users can send contribution counts from {% data variables.location.product_location %} to {% data variables.product.prodname_dotcom_the_website %}, each user must also connect their user account on {% data variables.product.product_name %} with a personal account on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)." {% data reusables.github-connect.sync-frequency %} -Se o proprietário da empresa desabilitar a funcionalidade ou usuários individuais optarem por não conectar a contagem de contribuição de {% data variables.product.product_name %} será excluída em {% data variables.product.prodname_dotcom_the_website %}. Se o usuário reconectar os perfis após desabilitá-los, as contagens de contribuição dos últimos 90 dias serão restauradas. +If the enterprise owner disables the functionality or individual users opt out of the connection, the contribution counts from {% data variables.product.product_name %} will be deleted on {% data variables.product.prodname_dotcom_the_website %}. If the user reconnects their profiles after disabling them, the contribution counts for the past 90 days are restored. -O {% data variables.product.product_name %} **só** envia a contagem e a origem da contribuição ({% data variables.product.product_name %}) para os usuários conectados. Nenhuma informação sobre a contribuição ou sobre como ela foi feita é enviada. +{% data variables.product.product_name %} **only** sends the contribution count and source ({% data variables.product.product_name %}) for connected users. It does not send any information about the contribution or how it was made. -## Habilitando contribuições unificadas +## Enabling unified contributions -Antes de habilitar {% data variables.product.prodname_unified_contributions %} em {% data variables.product.product_location %}, você deverá habilitar {% data variables.product.prodname_github_connect %}. Para obter mais informações, confira "[Como gerenciar o {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)". +Before enabling {% data variables.enterprise.prodname_unified_contributions %} on {% data variables.location.product_location %}, you must enable {% data variables.product.prodname_github_connect %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)." -{% ifversion ghes %} {% data reusables.github-connect.access-dotcom-and-enterprise %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.business %} {% data reusables.enterprise-accounts.github-connect-tab %}{% else %} -1. Entre no {% data variables.product.product_location %} e no {% data variables.product.prodname_dotcom_the_website %}. +{% ifversion ghes %} +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.business %} +{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} -1. Em "Os usuários podem compartilhar contagens de contribuições para o {% data variables.product.prodname_dotcom_the_website %}", clique em **Solicitar acesso**. - ![Opção Solicitar acesso às contribuições unificadas](/assets/images/enterprise/site-admin-settings/dotcom-ghe-connection-request-access.png){% ifversion ghes %} -2. [Entre](https://enterprise.github.com/login) no site do {% data variables.product.prodname_ghe_server %} para receber instruções adicionais. +1. Under "Users can share contribution counts to {% data variables.product.prodname_dotcom_the_website %}", click **Request access**. + ![Request access to unified contributions option](/assets/images/enterprise/site-admin-settings/dotcom-ghe-connection-request-access.png){% ifversion ghes %} +2. [Sign in](https://enterprise.github.com/login) to the {% data variables.product.prodname_ghe_server %} site to receive further instructions. -Ao solicitar acesso, podemos redirecioná-lo para o site {% data variables.product.prodname_ghe_server %} para verificar os termos de serviço atuais. +When you request access, we may redirect you to the {% data variables.product.prodname_ghe_server %} site to check your current terms of service. {% endif %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md index e3a6d84a44..196fc8b6b8 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Habilitando a pesquisa unificada para a sua empresa +title: Enabling unified search for your enterprise shortTitle: Unified search -intro: 'Você pode permitir que os usuários incluam repositórios em {% data variables.product.prodname_dotcom_the_website %} nos resultados de pesquisa quando pesquisarem em {% data variables.product.product_location %}.' +intro: 'You can allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.location.product_location %}.' redirect_from: - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-and-github-com - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-github-com @@ -20,35 +20,34 @@ topics: - Enterprise - GitHub Connect - GitHub search -ms.openlocfilehash: 0270600113cb3b341b38e6f55d7108798d523ebb -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145094038' --- -## Sobre o {% data variables.product.prodname_unified_search %} + +## About {% data variables.enterprise.prodname_unified_search %} {% data reusables.github-connect.beta %} -Ao habilitar a pesquisa unificada, os usuários podem ver os resultados de pesquisa de conteúdo em {% data variables.product.prodname_dotcom_the_website %} quando pesquisarem em {% data variables.product.product_location %}{% ifversion ghae %} em {% data variables.product.prodname_ghe_managed %}{% endif %}. +When you enable unified search, users can view search results from content on {% data variables.product.prodname_dotcom_the_website %} when searching from {% data variables.location.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}. -Você pode optar por permitir resultados de pesquisa para repositórios públicos em {% data variables.product.prodname_dotcom_the_website %} e você pode optar separadamente por permitir resultados de pesquisa para repositórios privados em {% data variables.product.prodname_ghe_cloud %}. Se você habilitar a pesquisa unificada para repositórios privados, os usuários só poderão pesquisar repositórios privados aos quais eles têm acesso e que são propriedade da organização conectada ou da conta corporativa. Para obter mais informações, confira "[Sobre a pesquisa no {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)". +You can choose to allow search results for public repositories on {% data variables.product.prodname_dotcom_the_website %}, and you can separately choose to allow search results for private repositories on {% data variables.product.prodname_ghe_cloud %}. If you enable unified search for private repositories, users can only search private repositories that they have access to and that are owned by the connected organization or enterprise account. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)." -Os usuários nunca poderão pesquisar em {% data variables.product.product_location %} a partir de {% data variables.product.prodname_dotcom_the_website %}, mesmo se tiverem acesso aos dois ambientes. +Users will never be able to search {% data variables.location.product_location %} from {% data variables.product.prodname_dotcom_the_website %}, even if they have access to both environments. -Depois que você habilitar a pesquisa unificada do {% data variables.product.product_location %}, para os usuários individuais poderem ver os resultados da pesquisa em repositórios privados no {% data variables.product.prodname_dotcom_the_website %} no {% data variables.product.product_location %}, cada usuário também deverá conectar a conta de usuário em {% data variables.product.product_name %} a uma conta pessoal no {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, confira "[Como habilitar a pesquisa de repositório do {% data variables.product.prodname_dotcom_the_website %} na sua conta da empresa privada](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)". +After you enable unified search for {% data variables.location.product_location %}, before individual users can see search results from private repositories on {% data variables.product.prodname_dotcom_the_website %} in {% data variables.location.product_location %}, each user must also connect their user account on {% data variables.product.product_name %} with a user account on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search in your private enterprise account](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." -A pesquisa via APIs REST e GraphQL não inclui resultados do {% data variables.product.prodname_dotcom_the_website %}. Não há suporte para a pesquisa avançada e a pesquisa de wikis no {% data variables.product.prodname_dotcom_the_website %}. +Searching via the REST and GraphQL APIs does not include {% data variables.product.prodname_dotcom_the_website %} search results. Advanced search and searching for wikis in {% data variables.product.prodname_dotcom_the_website %} are not supported. -## Como habilitar o {% data variables.product.prodname_unified_search %} +## Enabling {% data variables.enterprise.prodname_unified_search %} -Antes de você poder habilitar {% data variables.product.prodname_unified_search %}, você deverá habilitar {% data variables.product.prodname_github_connect %}. Para obter mais informações, confira "[Como gerenciar o {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)". +Before you can enable {% data variables.enterprise.prodname_unified_search %}, you must enable {% data variables.product.prodname_github_connect %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)." -{% ifversion ghes %} {% data reusables.github-connect.access-dotcom-and-enterprise %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.business %} {% data reusables.enterprise-accounts.github-connect-tab %}{% else %} -1. Entre no {% data variables.product.product_location %} e no {% data variables.product.prodname_dotcom_the_website %}. +{% ifversion ghes %} +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.business %} +{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. Sign into {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} -1. Em "Os usuários podem pesquisar o {% data variables.product.prodname_dotcom_the_website %}", use o menu suspenso e clique em **Habilitado**. - ![Habilitar a opção de pesquisa no menu suspenso de pesquisa no GitHub.com](/assets/images/enterprise/site-admin-settings/github-dotcom-enable-search.png) -1. Opcionalmente, em "Os usuários podem pesquisar repositórios privados no {% data variables.product.prodname_dotcom_the_website %}", use o menu suspenso e clique em **Habilitado**. - ![Habilitar a opção de pesquisa em repositórios privados no menu suspenso de pesquisa no GitHub.com](/assets/images/enterprise/site-admin-settings/enable-private-search.png) +1. Under "Users can search {% data variables.product.prodname_dotcom_the_website %}", use the drop-down menu and click **Enabled**. + ![Enable search option in the search GitHub.com drop-down menu](/assets/images/enterprise/site-admin-settings/github-dotcom-enable-search.png) +1. Optionally, under "Users can search private repositories on {% data variables.product.prodname_dotcom_the_website %}", use the drop-down menu and click **Enabled**. + ![Enable private repositories search option in the search GitHub.com drop-down menu](/assets/images/enterprise/site-admin-settings/enable-private-search.png) diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/index.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/index.md index 21f6c78e39..f0cbe3aeab 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/index.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/index.md @@ -1,6 +1,6 @@ --- -title: Configurando o GitHub Connect -intro: 'Com {% data variables.product.prodname_github_connect %}, você pode acessar funcionalidades e fluxos de trabalho adicionais conectando {% data variables.product.product_location %} a {% data variables.product.prodname_ghe_cloud %}.' +title: Configuring GitHub Connect +intro: 'With {% data variables.product.prodname_github_connect %}, you can access additional features and workflows by connecting {% data variables.location.product_location %} to {% data variables.product.prodname_ghe_cloud %}.' redirect_from: - /enterprise/admin/developer-workflow/connecting-github-enterprise-to-github-com - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-and-github-com @@ -25,11 +25,5 @@ children: - /enabling-unified-search-for-your-enterprise - /enabling-unified-contributions-for-your-enterprise shortTitle: GitHub Connect -ms.openlocfilehash: 6d0be48b952a7bb9abb5c439b5ab276e0b886ec8 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145095999' --- diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/managing-github-connect.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/managing-github-connect.md index 92a67d19c8..113d5f293b 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/managing-github-connect.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/managing-github-connect.md @@ -1,7 +1,7 @@ --- -title: Gerenciando o GitHub Connect +title: Managing GitHub Connect shortTitle: Manage GitHub Connect -intro: 'Você pode habilitar {% data variables.product.prodname_github_connect %} para acessar funcionalidades adicionais e fluxos de trabalho para {% data variables.product.product_location %}.' +intro: 'You can enable {% data variables.product.prodname_github_connect %} to access additional features and workflows for {% data variables.location.product_location %}.' redirect_from: - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com @@ -20,63 +20,69 @@ topics: - GitHub Connect - Infrastructure - Networking -ms.openlocfilehash: 0dea06870a1bc7bc951580acf3d83a9d2f0984c2 -ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/12/2022 -ms.locfileid: '146332453' --- + {% data reusables.github-connect.beta %} -## Sobre o {% data variables.product.prodname_github_connect %} +## About {% data variables.product.prodname_github_connect %} -Você pode acessar funcionalidades e fluxos de trabalho adicionais em {% data variables.product.product_location %}, habilitando o {% data variables.product.prodname_github_connect %}. Para obter mais informações, confira "[Sobre o {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)". +You can access additional features and workflows on {% data variables.location.product_location %} by enabling {% data variables.product.prodname_github_connect %}. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)." -Ao habilitar {% data variables.product.prodname_github_connect %}, você configura uma conexão entre {% data variables.product.product_location %} e uma conta de organização ou empresa em {% data variables.product.prodname_ghe_cloud %}. A habilitação de {% data variables.product.prodname_github_connect %} cria um {% data variables.product.prodname_github_app %} pertencente à organização ou conta corporativa em {% data variables.product.prodname_ghe_cloud %}. O {% data variables.product.product_name %} usa as credenciais do {% data variables.product.prodname_github_app %} para fazer solicitações ao {% data variables.product.prodname_ghe_cloud %}. - -{% ifversion ghes %}O {% data variables.product.prodname_ghe_server %} armazena as credenciais dos {% data variables.product.prodname_github_app %}. As credenciais a seguir serão replicadas em todos os nós em um ambiente de alta disponibilidade ou de agrupamento e armazenadas em qualquer backup, incluindo instantâneos criados por {% data variables.product.prodname_enterprise_backup_utilities %}. -- Um token de autenticação válido por uma hora; -- Uma chave privada, que é usada para gerar um novo token de autenticação {% endif %} - -## Pré-requisitos - -Para usar {% data variables.product.prodname_github_connect %}, você deve ter uma conta corporativa em {% data variables.product.prodname_dotcom_the_website %} que use {% data variables.product.prodname_ghe_cloud %}. Você pode já ter {% data variables.product.prodname_ghe_cloud %} incluído no seu plano. {% data reusables.enterprise.link-to-ghec-trial %} - -{% ifversion ghes %} Se a sua conta corporativa ou de organização do {% data variables.product.prodname_dotcom_the_website %} usar listas de IP permitidos, você precisará adicionar o endereço IP ou a rede para o {% data variables.product.product_location %} à lista de IP permitidos no {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, confira "[Como gerenciar endereços IP permitidos para sua organização](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)" e "[Como impor políticas para configurações de segurança na sua empresa](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)" na documentação do {% data variables.product.prodname_ghe_cloud %}. - -Para configurar uma conexão, sua configuração de proxy precisa permitir a conectividade com `github.com`, `api.github.com` e `uploads.github.com`. Para obter mais informações, confira "[Como configurar um servidor proxy Web de saída](/enterprise/admin/guides/installation/configuring-an-outbound-web-proxy-server)". -{% endif %} - -## Habilitar o {% data variables.product.prodname_github_connect %} - -Os proprietários corporativos que também são proprietários da conta de uma organização ou empresa que usa {% data variables.product.prodname_ghe_cloud %} podem habilitar {% data variables.product.prodname_github_connect %}. - -Se você estiver conectando {% data variables.product.product_location %} a uma organização em {% data variables.product.prodname_ghe_cloud %} que não seja propriedade de uma conta corporativa você deveverá efetuar o login em {% data variables.product.prodname_dotcom_the_website %} como proprietário da organização. - -Se você estiver conectando {% data variables.product.product_location %} a uma organização em {% data variables.product.prodname_ghe_cloud %} que pertence a uma conta corporativa ou a uma própria conta corporativa, você deveverá efetuar o login em {% data variables.product.prodname_dotcom_the_website %} como proprietário de uma empresa. +When you enable {% data variables.product.prodname_github_connect %}, you configure a connection between {% data variables.location.product_location %} and an organization or enterprise account on {% data variables.product.prodname_ghe_cloud %}. Enabling {% data variables.product.prodname_github_connect %} creates a {% data variables.product.prodname_github_app %} owned by the organization or enterprise account on {% data variables.product.prodname_ghe_cloud %}. {% data variables.product.product_name %} uses the {% data variables.product.prodname_github_app %}'s credentials to make requests to {% data variables.product.prodname_ghe_cloud %}. {% ifversion ghes %} -1. Entre no {% data variables.product.product_location %} e no {% data variables.product.prodname_dotcom_the_website %}. -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %}{% else %} -1. Entre no {% data variables.product.product_location %} e no {% data variables.product.prodname_dotcom_the_website %}. +{% data variables.product.prodname_ghe_server %} stores credentials from the {% data variables.product.prodname_github_app %}. The following credentials will be replicated to all nodes in a high availability or cluster environment, and stored in any backups, including snapshots created by {% data variables.product.prodname_enterprise_backup_utilities %}. +- An authentication token, which is valid for one hour +- A private key, which is used to generate a new authentication token +{% endif %} + +## Prerequisites + +To use {% data variables.product.prodname_github_connect %}, you must have an organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that uses {% data variables.product.prodname_ghe_cloud %}. You may already have {% data variables.product.prodname_ghe_cloud %} included in your plan. {% data reusables.enterprise.link-to-ghec-trial %} + +{% ifversion ghes %} +If your organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} uses IP allow lists, you must add the IP address or network for {% data variables.location.product_location %} to your IP allow list on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Managing allowed IP addresses for your organization](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)" and "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)" in the {% data variables.product.prodname_ghe_cloud %} documentation. + +To configure a connection, your proxy configuration must allow connectivity to `github.com`, `api.github.com`, and `uploads.github.com`. For more information, see "[Configuring an outbound web proxy server](/enterprise/admin/guides/installation/configuring-an-outbound-web-proxy-server)." +{% endif %} + +## Enabling {% data variables.product.prodname_github_connect %} + +Enterprise owners who are also owners of an organization or enterprise account that uses {% data variables.product.prodname_ghe_cloud %} can enable {% data variables.product.prodname_github_connect %}. + +If you're connecting {% data variables.location.product_location %} to an organization on {% data variables.product.prodname_ghe_cloud %} that is not owned by an enterprise account, you must sign into {% data variables.product.prodname_dotcom_the_website %} as an organization owner. + +If you're connecting {% data variables.location.product_location %} to an organization on {% data variables.product.prodname_ghe_cloud %} that is owned by an enterprise account or to an enterprise account itself, you must sign into {% data variables.product.prodname_dotcom_the_website %} as an enterprise owner. + +{% ifversion ghes %} +1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} -1. Em "O {% data variables.product.prodname_github_connect %} ainda não está habilitado", clique em **Habilitar o {% data variables.product.prodname_github_connect %}** . Ao clicar em **Habilitar o {% data variables.product.prodname_github_connect %}** , você concorda com os "Termos de Produtos e Recursos Adicionais do {% data variables.product.prodname_dotcom %}". -{% ifversion ghes %} ![Botão Habilitar o GitHub Connect](/assets/images/enterprise/business-accounts/enable-github-connect-button.png){% else %} ![Botão Habilitar o GitHub Connect](/assets/images/enterprise/github-ae/enable-github-connect-button.png) {% endif %} -1. Ao lado da conta corporativa ou de organização que deseja conectar, clique em **Conectar**. - ![Botão Conectar ao lado de uma conta corporativa ou de empresa](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png) +1. Under "{% data variables.product.prodname_github_connect %} is not enabled yet", click **Enable {% data variables.product.prodname_github_connect %}**. By clicking **Enable {% data variables.product.prodname_github_connect %}**, you agree to the "{% data variables.product.prodname_dotcom %} Terms for Additional Products and Features." +{% ifversion ghes %} + ![Enable GitHub Connect button](/assets/images/enterprise/business-accounts/enable-github-connect-button.png){% else %} + ![Enable GitHub Connect button](/assets/images/enterprise/github-ae/enable-github-connect-button.png) +{% endif %} +1. Next to the enterprise account or organization you'd like to connect, click **Connect**. + ![Connect button next to an enterprise account or business](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png) -## Como desabilitar o {% data variables.product.prodname_github_connect %} +## Disabling {% data variables.product.prodname_github_connect %} -Os proprietários das empresas podem desabilitar {% data variables.product.prodname_github_connect %}. +Enterprise owners can disable {% data variables.product.prodname_github_connect %}. -Ao se desconectar do {% data variables.product.prodname_ghe_cloud %}, o {% data variables.product.prodname_github_app %} do {% data variables.product.prodname_github_connect %} é excluído da sua conta corporativa ou organização e as credenciais armazenadas na {% data variables.product.product_location %} são excluídas. +When you disconnect from {% data variables.product.prodname_ghe_cloud %}, the {% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} is deleted from your enterprise account or organization and credentials stored on {% data variables.location.product_location %} are deleted. -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %} -1. Ao lado da conta corporativa ou de organização que deseja desconectar, clique em **Desabilitar o {% data variables.product.prodname_github_connect %}** . -{% ifversion ghes %} ![Botão Desabilitar o GitHub Connect ao lado de uma conta corporativa ou de um nome de organização](/assets/images/enterprise/business-accounts/disable-github-connect-button.png) -1. Leia as informações sobre como desconectar e clique em **Desabilitar o {% data variables.product.prodname_github_connect %}** . - ![Caixa de diálogo modal com informações de aviso sobre a desconexão e botão de confirmação](/assets/images/enterprise/business-accounts/confirm-disable-github-connect.png) -{% else %} ![Botão Desabilitar o GitHub Connect ao lado de uma conta corporativa ou de um nome de organização](/assets/images/enterprise/github-ae/disable-github-connect-button.png) -1. Leia as informações sobre como desconectar e clique em **Desabilitar o {% data variables.product.prodname_github_connect %}** . - ![Caixa de diálogo modal com informações de aviso sobre a desconexão e botão de confirmação](/assets/images/enterprise/github-ae/confirm-disable-github-connect.png) {% endif %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.github-connect-tab %} +1. Next to the enterprise account or organization you'd like to disconnect, click **Disable {% data variables.product.prodname_github_connect %}**. +{% ifversion ghes %} + ![Disable GitHub Connect button next to an enterprise account or organization name](/assets/images/enterprise/business-accounts/disable-github-connect-button.png) +1. Read the information about disconnecting and click **Disable {% data variables.product.prodname_github_connect %}**. + ![Modal with warning information about disconnecting and confirmation button](/assets/images/enterprise/business-accounts/confirm-disable-github-connect.png) +{% else %} + ![Disable GitHub Connect button next to an enterprise account or organization name](/assets/images/enterprise/github-ae/disable-github-connect-button.png) +1. Read the information about disconnecting and click **Disable {% data variables.product.prodname_github_connect %}**. + ![Modal with warning information about disconnecting and confirmation button](/assets/images/enterprise/github-ae/confirm-disable-github-connect.png) +{% endif %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md index db26703189..3d37a2c2dc 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md +++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md @@ -1,6 +1,6 @@ --- -title: Configurar nome de host -intro: 'Em vez de usar um endereço IP codificado, é recomendável definir um nome de host para o seu appliance.' +title: Configuring a hostname +intro: We recommend setting a hostname for your appliance instead of using a hard-coded IP address. redirect_from: - /enterprise/admin/guides/installation/configuring-hostnames - /enterprise/admin/installation/configuring-a-hostname @@ -13,27 +13,27 @@ topics: - Enterprise - Fundamentals - Infrastructure -ms.openlocfilehash: 120827f8eca8061d90d397a7e2a21d46ae33f243 -ms.sourcegitcommit: dc42bb4a4826b414751ffa9eed38962c3e3fea8e -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 07/13/2022 -ms.locfileid: '146681314' --- -Se você configurar um nome do host em vez de um endereço IP embutido em código, poderá alterar o hardware físico em que o {% data variables.product.product_location %} é executado sem afetar os usuários nem o software cliente. +If you configure a hostname instead of a hard-coded IP address, you will be able to change the physical hardware that {% data variables.location.product_location %} runs on without affecting users or client software. -A configuração do nome de host no {% data variables.enterprise.management_console %} deve ser definida como um nome de domínio totalmente qualificado (FQDN) que seja resolvido na internet ou dentro da sua rede interna. Por exemplo, sua configuração de nome do host pode ser `github.companyname.com.` na Web, e as solicitações de API redirecionarão automaticamente para o nome do host configurado no {% data variables.enterprise.management_console %}. Observe que `localhost` não é uma configuração de nome de host válida. +The hostname setting in the {% data variables.enterprise.management_console %} should be set to an appropriate fully qualified domain name (FQDN) which is resolvable on the internet or within your internal network. For example, your hostname setting could be `github.companyname.com.` Web and API requests will automatically redirect to the hostname configured in the {% data variables.enterprise.management_console %}. Note that `localhost` is not a valid hostname setting. -Depois de configurar um nome do host, você pode habilitar o isolamento de subdomínio para aumentar ainda mais a segurança do {% data variables.product.product_location %}. Para obter mais informações, confira "[Como habilitar o isolamento de subdomínio](/enterprise/admin/guides/installation/enabling-subdomain-isolation/)". +Hostnames must be less than 63 characters in length per [Section 2.3.4 of the Domain Names Specification RFC](https://datatracker.ietf.org/doc/html/rfc1035#section-2.3.4). -Para obter mais informações sobre os tipos de nomes do host compatíveis, confira a [Seção 2.1 do RFC HTTP](https://tools.ietf.org/html/rfc1123#section-2). +After you configure a hostname, you can enable subdomain isolation to further increase the security of {% data variables.location.product_location %}. For more information, see "[Enabling subdomain isolation](/enterprise/admin/guides/installation/enabling-subdomain-isolation/)." + +For more information on the supported hostname types, see [Section 2.1 of the HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2). {% data reusables.enterprise_installation.changing-hostname-not-supported %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.hostname-menu-item %} -4. Digite o nome do host que deseja definir para o {% data variables.product.product_location %}. - ![Campo usado para definir um nome do host](/assets/images/enterprise/management-console/hostname-field.png) -5. Para testar as configurações de DNS e SSL para o novo nome do host, clique em **Testar configurações de domínio**. - ![Botão Testar configurações de domínio](/assets/images/enterprise/management-console/test-domain-settings.png) {% data reusables.enterprise_management_console.test-domain-settings-failure %} {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.hostname-menu-item %} +4. Type the hostname you'd like to set for {% data variables.location.product_location %}. + ![Field for setting a hostname](/assets/images/enterprise/management-console/hostname-field.png) +5. To test the DNS and SSL settings for the new hostname, click **Test domain settings**. + ![Test domain settings button](/assets/images/enterprise/management-console/test-domain-settings.png) +{% data reusables.enterprise_management_console.test-domain-settings-failure %} +{% data reusables.enterprise_management_console.save-settings %} -Para ajudar a atenuar várias vulnerabilidades de cross-site scripting, recomendamos que você habilite o isolamento de subdomínio para o {% data variables.product.product_location %} depois de configurar um nome do host. Para obter mais informações, confira "[Como habilitar o isolamento de subdomínio](/enterprise/admin/guides/installation/enabling-subdomain-isolation/)". +To help mitigate various cross-site scripting vulnerabilities, we recommend that you enable subdomain isolation for {% data variables.location.product_location %} after you configure a hostname. For more information, see "[Enabling subdomain isolation](/enterprise/admin/guides/installation/enabling-subdomain-isolation/)." diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md index 6205343d48..0bf9da396a 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md +++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md @@ -1,6 +1,6 @@ --- -title: Configurando um servidor proxy Web de saída -intro: 'Um servidor proxy fornece um nível adicional de segurança para o {% data variables.product.product_location %}.' +title: Configuring an outbound web proxy server +intro: 'A proxy server provides an additional level of security for {% data variables.location.product_location %}.' redirect_from: - /enterprise/admin/guides/installation/configuring-a-proxy-server - /enterprise/admin/installation/configuring-an-outbound-web-proxy-server @@ -15,32 +15,29 @@ topics: - Infrastructure - Networking shortTitle: Configure an outbound proxy -ms.openlocfilehash: 4285f24dd45d127efec4ace66729bf6fd1f188c5 -ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147875481' --- -## Sobre proxies com {% data variables.product.product_name %} -Quando um servidor proxy está habilitado para o {% data variables.product.product_location %}, as mensagens de saída enviadas pelo {% data variables.product.prodname_ghe_server %} são enviadas pela primeira vez por meio do servidor proxy, a menos que o host de destino seja adicionado como uma exclusão de proxy HTTP. Os tipos de mensagens de saída incluem webhooks de saída, pacotes para upload e fetch de avatares herdados. A URL do servidor proxy é o protocolo, o domínio ou o endereço IP, além do número da porta, por exemplo, `http://127.0.0.1:8123`. +## About proxies with {% data variables.product.product_name %} + +When a proxy server is enabled for {% data variables.location.product_location %}, outbound messages sent by {% data variables.product.prodname_ghe_server %} are first sent through the proxy server, unless the destination host is added as an HTTP proxy exclusion. Types of outbound messages include outgoing webhooks, uploading bundles, and fetching legacy avatars. The proxy server's URL is the protocol, domain or IP address, plus the port number, for example `http://127.0.0.1:8123`. {% note %} -**Observação:** para conectar o {% data variables.product.product_location %} ao {% data variables.product.prodname_dotcom_the_website %}, a configuração de proxy precisa permitir a conectividade a `github.com` e a `api.github.com`. Para obter mais informações, confira "[Como conectar sua conta corporativa ao {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)". +**Note:** To connect {% data variables.location.product_location %} to {% data variables.product.prodname_dotcom_the_website %}, your proxy configuration must allow connectivity to `github.com` and `api.github.com`. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." {% endnote %} -{% data reusables.actions.proxy-considerations %} Para obter mais informações sobre como usar o {% data variables.product.prodname_actions %} com o {% data variables.product.prodname_ghe_server %}, confira "[Introdução ao {% data variables.product.prodname_actions %} para o {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)". +{% data reusables.actions.proxy-considerations %} For more information about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)." -## Configurando um servidor proxy Web de saída +## Configuring an outbound web proxy server -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} -1. Em **Servidor Proxy HTTP**, digite a URL do servidor proxy. - ![Campo usado para digitar a URL do Servidor Proxy HTTP](/assets/images/enterprise/management-console/http-proxy-field.png) +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +1. Under **HTTP Proxy Server**, type the URL of your proxy server. + ![Field to type the HTTP Proxy Server URL](/assets/images/enterprise/management-console/http-proxy-field.png) -5. Opcionalmente, em **Exclusão de Proxy HTTP**, digite todos os hosts que não exigem acesso de proxy, separando os hosts com vírgulas. Para excluir todos os hosts em um domínio da exigência do acesso de proxy, use `.` como um prefixo curinga. Por exemplo: `.octo-org.tentacle` - ![campo para digitar as exclusões de proxy HTTP](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) +5. Optionally, under **HTTP Proxy Exclusion**, type any hosts that do not require proxy access, separating hosts with commas. To exclude all hosts in a domain from requiring proxy access, you can use `.` as a wildcard prefix. For example: `.octo-org.tentacle` + ![Field to type any HTTP Proxy Exclusions](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md index 1c1487963d..7a0088680e 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md +++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md @@ -1,6 +1,6 @@ --- -title: Configurar regras de firewall integrado -intro: 'É possível exibir as regras padrão de firewall e personalizar outras regras da {% data variables.product.product_location %}.' +title: Configuring built-in firewall rules +intro: 'You can view default firewall rules and customize rules for {% data variables.location.product_location %}.' redirect_from: - /enterprise/admin/guides/installation/configuring-firewall-settings - /enterprise/admin/installation/configuring-built-in-firewall-rules @@ -15,25 +15,19 @@ topics: - Infrastructure - Networking shortTitle: Configure firewall rules -ms.openlocfilehash: 7492f69c6b334847229c76f7462beaabbc4154a2 -ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145095996' --- -## Sobre o firewall do {% data variables.product.product_location %} +## About {% data variables.location.product_location %}'s firewall -O {% data variables.product.prodname_ghe_server %} usa o Uncomplicated Firewall (UFW) do Ubuntu no appliance virtual. Para obter mais informações, confira "[UFW](https://help.ubuntu.com/community/UFW)" na documentação do Ubuntu. O {% data variables.product.prodname_ghe_server %} atualiza automaticamente a lista de desbloqueio de firewall dos serviços permitidos em cada versão. +{% data variables.product.prodname_ghe_server %} uses Ubuntu's Uncomplicated Firewall (UFW) on the virtual appliance. For more information see "[UFW](https://help.ubuntu.com/community/UFW)" in the Ubuntu documentation. {% data variables.product.prodname_ghe_server %} automatically updates the firewall allowlist of allowed services with each release. -Depois da instalação do {% data variables.product.prodname_ghe_server %}, todas as portas de rede necessárias ficam abertas automaticamente para aceitar conexões. Cada porta não necessária é configurada automaticamente como `deny`, e a política de saída padrão é configurada como `allow`. O acompanhamento com estado está habilitado para novas conexões. Normalmente, são pacotes de rede com o conjunto de bits `SYN`. Para obter mais informações, confira "[Portas de rede](/enterprise/admin/guides/installation/network-ports)". +After you install {% data variables.product.prodname_ghe_server %}, all required network ports are automatically opened to accept connections. Every non-required port is automatically configured as `deny`, and the default outgoing policy is configured as `allow`. Stateful tracking is enabled for any new connections; these are typically network packets with the `SYN` bit set. For more information, see "[Network ports](/enterprise/admin/guides/installation/network-ports)." -O firewall UFW também abre várias outras portas necessárias para o funcionamento adequado do {% data variables.product.prodname_ghe_server %}. Para obter mais informações sobre o conjunto de regras do UFW, confira [o LEIAME do UFW](https://bazaar.launchpad.net/~jdstrand/ufw/0.30-oneiric/view/head:/README#L213). +The UFW firewall also opens several other ports that are required for {% data variables.product.prodname_ghe_server %} to operate properly. For more information on the UFW rule set, see [the UFW README](https://bazaar.launchpad.net/~jdstrand/ufw/0.30-oneiric/view/head:/README#L213). -## Exibir as regras padrão de firewall +## Viewing the default firewall rules {% data reusables.enterprise_installation.ssh-into-instance %} -2. Para ver as regras de firewall padrão, use o comando `sudo ufw status`. Você deverá ver uma saída semelhante à esta: +2. To view the default firewall rules, use the `sudo ufw status` command. You should see output similar to this: ```shell $ sudo ufw status > Status: active @@ -61,46 +55,46 @@ O firewall UFW também abre várias outras portas necessárias para o funcioname > ghe-9418 (v6) ALLOW Anywhere (v6) ``` -## Adicionar regras personalizadas de firewall +## Adding custom firewall rules {% warning %} -**Aviso:** antes de adicionar regras de firewall personalizadas, faça backup das regras atuais caso precise fazer a redefinição para um estado de trabalho conhecido. Se você não conseguir acessar o servidor, entre em contato com o {% data variables.contact.contact_ent_support %} para reconfigurar as regras originais do firewall. Restaurar as regras originais gera tempo de inatividade no servidor. +**Warning:** Before you add custom firewall rules, back up your current rules in case you need to reset to a known working state. If you're locked out of your server, contact {% data variables.contact.contact_ent_support %} to reconfigure the original firewall rules. Restoring the original firewall rules involves downtime for your server. {% endwarning %} -1. Configure uma regra personalizada de firewall. -2. Verifique o status de cada nova regra com o comando `status numbered`. +1. Configure a custom firewall rule. +2. Check the status of each new rule with the `status numbered` command. ```shell $ sudo ufw status numbered ``` -3. Para fazer backup das regras de firewall personalizadas, use o comando `cp` para mover as regras para um novo arquivo. +3. To back up your custom firewall rules, use the `cp`command to move the rules to a new file. ```shell $ sudo cp -r /etc/ufw ~/ufw.backup ``` -Depois de fazer o upgrade do {% data variables.product.product_location %}, você precisará aplicar as regras de firewall personalizadas novamente. Para isso, é recomendável criar um script. +After you upgrade {% data variables.location.product_location %}, you must reapply your custom firewall rules. We recommend that you create a script to reapply your firewall custom rules. -## Restaurar as regras padrão de firewall +## Restoring the default firewall rules -Se a alteração das regras do firewall ocasionar erros, você poderá redefinir as regras originais no backup. +If something goes wrong after you change the firewall rules, you can reset the rules from your original backup. {% warning %} -**Aviso:** se você não fez backup das regras originais antes de fazer alterações no firewall, entre em contato com o {% data variables.contact.contact_ent_support %} para obter mais assistência. +**Warning:** If you didn't back up the original rules before making changes to the firewall, contact {% data variables.contact.contact_ent_support %} for further assistance. {% endwarning %} {% data reusables.enterprise_installation.ssh-into-instance %} -2. Para restaurar as regras de backup anteriores, copie-as de novo para o firewall com o comando `cp`. +2. To restore the previous backup rules, copy them back to the firewall with the `cp` command. ```shell $ sudo cp -f ~/ufw.backup/*rules /etc/ufw ``` -3. Reinicie o firewall com o comando `systemctl`. +3. Restart the firewall with the `systemctl` command. ```shell $ sudo systemctl restart ufw ``` -4. Confirme se as regras estão de volta aos padrões com o comando `ufw status`. +4. Confirm that the rules are back to their defaults with the `ufw status` command. ```shell $ sudo ufw status > Status: active diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md index 7a9351f858..04ddd6fa9e 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md +++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md @@ -1,6 +1,6 @@ --- -title: Configurar servidores de nomes DNS -intro: 'O {% data variables.product.prodname_ghe_server %} usa o protocolo de configuração dinâmica de host (DHCP) para configurações de DNS quando as concessões de DHCP fornecem servidores de nomes. Se os servidores de nomes não forem fornecidos por uma concessão do protocolo DHCP, ou caso você precise usar configurações DNS específicas, será possível especificá-los manualmente.' +title: Configuring DNS nameservers +intro: '{% data variables.product.prodname_ghe_server %} uses the dynamic host configuration protocol (DHCP) for DNS settings when DHCP leases provide nameservers. If nameservers are not provided by a dynamic host configuration protocol (DHCP) lease, or if you need to use specific DNS settings, you can specify the nameservers manually.' redirect_from: - /enterprise/admin/guides/installation/about-dns-nameservers - /enterprise/admin/installation/configuring-dns-nameservers @@ -15,34 +15,28 @@ topics: - Infrastructure - Networking shortTitle: Configure DNS servers -ms.openlocfilehash: b01dc25b9002bf1feb672bbce597c8046b93f12f -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147419710' --- -Os servidores de nomes especificados precisam resolver o nome do host do {% data variables.product.product_location %}. +The nameservers you specify must resolve {% data variables.location.product_location %}'s hostname. {% data reusables.enterprise_installation.changing-hostname-not-supported %} -## Configurar servidores de nomes usando o console de máquina virtual +## Configuring nameservers using the virtual machine console {% data reusables.enterprise_installation.open-vm-console-start %} -2. Configure os servidores de nomes da sua instância. +2. Configure nameservers for your instance. {% data reusables.enterprise_installation.vm-console-done %} -## Configurar servidores de nomes usando o shell administrativo +## Configuring nameservers using the administrative shell {% data reusables.enterprise_installation.ssh-into-instance %} -2. Para editar seus nomes de servidores, use o comando `ghe-setup-network` no modo visual. Para obter mais informações, confira "[Utilitários de linha de comando](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-setup-network)". +2. To edit your nameservers, use the `ghe-setup-network` command in visual mode. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-setup-network)." ```shell ghe-setup-network -v ``` -5. Para adicionar as suas novas entradas de nameserver para {% data variables.product.product_location %}, execute o seguinte: +5. To add your new nameserver entries to {% data variables.location.product_location %}, run the following: ```shell sudo service resolvconf restart diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-tls.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-tls.md index dc32d66f74..bebfbb14fe 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-tls.md +++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-tls.md @@ -1,6 +1,6 @@ --- -title: Configurar o TLS -intro: 'Você pode configurar o protocolo TLS na {% data variables.product.product_location %} para poder usar certificados assinados por uma autoridade de certificação confiável.' +title: Configuring TLS +intro: 'You can configure Transport Layer Security (TLS) on {% data variables.location.product_location %} so that you can use a certificate that is signed by a trusted certificate authority.' redirect_from: - /enterprise/admin/articles/ssl-configuration - /enterprise/admin/guides/installation/about-tls @@ -16,68 +16,70 @@ topics: - Infrastructure - Networking - Security -ms.openlocfilehash: c11f78b69f5b251a63c0796d46bca4d6c926f002 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146682330' --- -## Sobre o protocolo Transport Layer Security +## About Transport Layer Security -O TLS, protocolo que substituiu o SSL, fica habilitado e configurado com um certificado autoassinado quando o {% data variables.product.prodname_ghe_server %} é iniciado pela primeira vez. Como os certificados autoassinados não são considerados confiáveis por navegadores da web e clientes Git, esses clientes reportarão avisos de certificados até você desabilitar o TLS ou fazer upload de um certificado assinado por uma autoridade confiável, como o Let's Encrypt. +TLS, which replaced SSL, is enabled and configured with a self-signed certificate when {% data variables.product.prodname_ghe_server %} is started for the first time. As self-signed certificates are not trusted by web browsers and Git clients, these clients will report certificate warnings until you disable TLS or upload a certificate signed by a trusted authority, such as Let's Encrypt. -O appliance do {% data variables.product.prodname_ghe_server %} enviará os headers de HTTP Strict Transport Security quando o SSL for habilitado. Desabilitar o TLS fará os usuários perderem o acesso ao appliance, pois seus navegadores não permitirão o downgrade de protocolo para HTTP. Para obter mais informações, confira "[HSTS (HTTP Strict Transport Security)](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)" na Wikipédia. +The {% data variables.product.prodname_ghe_server %} appliance will send HTTP Strict Transport Security headers when SSL is enabled. Disabling TLS will cause users to lose access to the appliance, because their browsers will not allow a protocol downgrade to HTTP. For more information, see "[HTTP Strict Transport Security (HSTS)](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)" on Wikipedia. {% data reusables.enterprise_installation.terminating-tls %} -Para permitir o uso do FIDO U2F para autenticação de dois fatores, você deve habilitar o TLS na sua instância. Para obter mais informações, confira "[Como configurar a autenticação de dois fatores](/articles/configuring-two-factor-authentication)". +To allow users to use FIDO U2F for two-factor authentication, you must enable TLS for your instance. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)." -## Pré-requisitos +## Prerequisites -Para usar o TLS em produção, você deve ter um certificado em formato PEM não criptografado assinado por uma autoridade de certificação confiável. +To use TLS in production, you must have a certificate in an unencrypted PEM format signed by a trusted certificate authority. -Seu certificado também precisará ter nomes alternativos da entidade configurados para os subdomínios listados em "[Como habilitar o isolamento de subdomínio](/enterprise/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)" e precisará incluir a cadeia de certificados completa se tiver sido assinada por uma autoridade de certificação intermediária. Para obter mais informações, confira "[Nome alternativo da entidade](http://en.wikipedia.org/wiki/SubjectAltName)" na Wikipédia. +Your certificate will also need Subject Alternative Names configured for the subdomains listed in "[Enabling subdomain isolation](/enterprise/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)" and will need to include the full certificate chain if it has been signed by an intermediate certificate authority. For more information, see "[Subject Alternative Name](http://en.wikipedia.org/wiki/SubjectAltName)" on Wikipedia. -Você pode gerar uma CSR (solicitação de assinatura de certificado) para sua instância usando o comando `ghe-ssl-generate-csr`. Para obter mais informações, confira "[Utilitários de linha de comando](/enterprise/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)". +You can generate a certificate signing request (CSR) for your instance using the `ghe-ssl-generate-csr` command. For more information, see "[Command-line utilities](/enterprise/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)." -A chave precisa ser uma chave RSA e não pode ter uma frase secreta. Para obter mais informações, confira "[Como remover a frase secreta do arquivo de chave](/admin/guides/installation/troubleshooting-ssl-errors#removing-the-passphrase-from-your-key-file)". +Your key must be an RSA key and must not have a passphrase. For more information, see "[Removing the passphrase from your key file](/admin/guides/installation/troubleshooting-ssl-errors#removing-the-passphrase-from-your-key-file)". -## Fazer upload de um certificado TLS personalizado +## Uploading a custom TLS certificate {% data reusables.enterprise_site_admin_settings.tls-downtime %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} {% data reusables.enterprise_management_console.select-tls-only %} -4. Em "TLS Protocol support" (Suporte ao protocolo TLS), selecione os protocolos que deseja permitir. - ![Botões com opções para escolha de protocolos TLS](/assets/images/enterprise/management-console/tls-protocol-support.png) -5. Em "Certificado", clique em **Escolher Arquivo** para escolher um certificado TLS ou uma cadeia de certificados (no formato PEM) para instalação. Em geral, esse arquivo terá uma extensão *.pem*, *.crt* ou *.cer*. - ![Botão usado para localizar o arquivo de certificado TLS](/assets/images/enterprise/management-console/install-tls-certificate.png) -6. Em "Chave não criptografada", clique em **Escolher Arquivo** para escolher uma chave RSA (no formato PEM) para instalação. Em geral, esse arquivo terá uma extensão *.key*. - ![Botão usado para localizar o arquivo de chave TLS](/assets/images/enterprise/management-console/install-tls-key.png) +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +{% data reusables.enterprise_management_console.select-tls-only %} +4. Under "TLS Protocol support", select the protocols you want to allow. + ![Radio buttons with options to choose TLS protocols](/assets/images/enterprise/management-console/tls-protocol-support.png) +5. Under "Certificate", click **Choose File** to choose a TLS certificate or certificate chain (in PEM format) to install. This file will usually have a *.pem*, *.crt*, or *.cer* extension. + ![Button to find TLS certificate file](/assets/images/enterprise/management-console/install-tls-certificate.png) +6. Under "Unencrypted key", click **Choose File** to choose an RSA key (in PEM format) to install. This file will usually have a *.key* extension. + ![Button to find TLS key file](/assets/images/enterprise/management-console/install-tls-key.png) {% data reusables.enterprise_management_console.save-settings %} -## Sobre o suporte Let's Encrypt +## About Let's Encrypt support -Let's Encrypt é uma autoridade de certificação pública que emite certificados TLS gratuitos, automatizados e reconhecidos como confiáveis pelos navegadores usando o protocolo ACME. Você pode obter e renovar automaticamente os certificados Let's Encrypt no seu appliance sem depender de manutenção manual. +Let's Encrypt is a public certificate authority that issues free, automated TLS certificates that are trusted by browsers using the ACME protocol. You can automatically obtain and renew Let's Encrypt certificates on your appliance without any required manual maintenance. {% data reusables.enterprise_installation.lets-encrypt-prerequisites %} -Quando você habilitar a automação do gerenciamento de certificados TLS usando o Let's Encrypt, o {% data variables.product.product_location %} entrará em contato com os servidores do Let's Encrypt para obter um certificado. Para renovar um certificado, os servidores do Let's Encrypt devem validar o controle do nome de domínio configurado com solicitações HTTP de entrada. +When you enable automation of TLS certificate management using Let's Encrypt, {% data variables.location.product_location %} will contact the Let's Encrypt servers to obtain a certificate. To renew a certificate, Let's Encrypt servers must validate control of the configured domain name with inbound HTTP requests. -Use também o utilitário de linha de comando `ghe-ssl-acme` no {% data variables.product.product_location %} para gerar automaticamente um certificado Let's Encrypt. Para obter mais informações, confira "[Utilitários de linha de comando](/enterprise/admin/guides/installation/command-line-utilities#ghe-ssl-acme)". +You can also use the `ghe-ssl-acme` command line utility on {% data variables.location.product_location %} to automatically generate a Let's Encrypt certificate. For more information, see "[Command-line utilities](/enterprise/admin/guides/installation/command-line-utilities#ghe-ssl-acme)." -## Configurar o TLS usando Let's Encrypt +## Configuring TLS using Let's Encrypt {% data reusables.enterprise_installation.lets-encrypt-prerequisites %} {% data reusables.enterprise_site_admin_settings.tls-downtime %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} {% data reusables.enterprise_management_console.select-tls-only %} -5. Selecione **Habilitar a automação do gerenciamento de certificados TLS usando o Let's Encrypt**. - ![Caixa de seleção usada para habilitar o Let's Encrypt](/assets/images/enterprise/management-console/lets-encrypt-checkbox.png) {% data reusables.enterprise_management_console.save-settings %} {% data reusables.enterprise_management_console.privacy %} -7. Clique em **Solicitar certificado TLS**. - ![Botão Solicitar certificado TSL](/assets/images/enterprise/management-console/request-tls-button.png) -8. Espere o "Status" mudar de "INICIADO" para "Concluído". - ![Status do Let's Encrypt](/assets/images/enterprise/management-console/lets-encrypt-status.png) -9. Clique em **Salvar configuração**. +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +{% data reusables.enterprise_management_console.select-tls-only %} +5. Select **Enable automation of TLS certificate management using Let's Encrypt**. + ![Checkbox to enable Let's Encrypt](/assets/images/enterprise/management-console/lets-encrypt-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_management_console.privacy %} +7. Click **Request TLS certificate**. + ![Request TLS certificate button](/assets/images/enterprise/management-console/request-tls-button.png) +8. Wait for the "Status" to change from "STARTED" to "DONE". + ![Let's Encrypt status](/assets/images/enterprise/management-console/lets-encrypt-status.png) +9. Click **Save configuration**. diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md index 1203bf07b0..e1dcf2af52 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md +++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md @@ -1,6 +1,6 @@ --- -title: Habilitar isolamento de subdomínio -intro: 'É possível configurar o isolamento de subdomínio para separar com segurança o conteúdo enviado pelo usuário de outras partes do seu appliance do {% data variables.product.prodname_ghe_server %}.' +title: Enabling subdomain isolation +intro: 'You can set up subdomain isolation to securely separate user-supplied content from other portions of your {% data variables.product.prodname_ghe_server %} appliance.' redirect_from: - /enterprise/admin/guides/installation/about-subdomain-isolation - /enterprise/admin/installation/enabling-subdomain-isolation @@ -16,20 +16,14 @@ topics: - Networking - Security shortTitle: Enable subdomain isolation -ms.openlocfilehash: ec7b04f845d0ec44c3234ece0194d4396df54892 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146332549' --- -## Sobre isolamento de subdomínio +## About subdomain isolation -O isolamento de subdomínios reduz os problemas de script entre sites e outras vulnerabilidades relacionadas. Para obter mais informações, confira "[Cross-site scripting](http://en.wikipedia.org/wiki/Cross-site_scripting)" na Wikipédia. Recomendamos fortemente habilitar o isolamento de subdomínio no {% data variables.product.product_location %}. +Subdomain isolation mitigates cross-site scripting and other related vulnerabilities. For more information, see "[Cross-site scripting](http://en.wikipedia.org/wiki/Cross-site_scripting)" on Wikipedia. We highly recommend that you enable subdomain isolation on {% data variables.location.product_location %}. -Quando o isolamento do subdomínio está ativado, o {% data variables.product.prodname_ghe_server %} substitui vários caminhos pelos subdomínios. Depois que você habilitar o isolamento de subdomínio, as tentativas de acessar os caminhos anteriores para um conteúdo fornecido pelo usuário, como `http(s)://HOSTNAME/raw/`, podem retornar erros `404`. +When subdomain isolation is enabled, {% data variables.product.prodname_ghe_server %} replaces several paths with subdomains. After enabling subdomain isolation, attempts to access the previous paths for some user-supplied content, such as `http(s)://HOSTNAME/raw/`, may return `404` errors. -| Caminho sem isolamento de subdomínio | Caminho com isolamento de subdomínio | +| Path without subdomain isolation | Path with subdomain isolation | | --- | --- | | `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | | `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | @@ -46,24 +40,27 @@ Quando o isolamento do subdomínio está ativado, o {% data variables.product.pr | `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %}{% ifversion ghes > 3.4 %} -| Sem suporte | `https://containers.HOSTNAME/` |{% endif %} +| Not supported | `https://containers.HOSTNAME/` |{% endif %} -## Pré-requisitos +## Prerequisites {% data reusables.enterprise_installation.disable-github-pages-warning %} -Antes de habilitar o isolamento de subdomínio, você deve definir as configurações de rede do novo domínio. +Before you enable subdomain isolation, you must configure your network settings for your new domain. -- Em vez de um endereço IP, especifique um nome de domínio válido como nome de host. Para obter mais informações, confira "[Como configurar um nome do host](/enterprise/admin/guides/installation/configuring-a-hostname)". +- Specify a valid domain name as your hostname, instead of an IP address. For more information, see "[Configuring a hostname](/enterprise/admin/guides/installation/configuring-a-hostname)." {% data reusables.enterprise_installation.changing-hostname-not-supported %} -- Configure um registro curinga do Sistema de Nomes de Domínio (DNS) ou registros DNS individuais para os subdomínios listados acima. Recomendamos criar um registro A para `*.HOSTNAME` que aponte para o endereço IP do servidor, de modo que você não precise criar vários registros para cada subdomínio. -- Obtenha um certificado TLS curinga para `*.HOSTNAME` com um SAN (nome alternativo da entidade) para `HOSTNAME` e o domínio curinga `*.HOSTNAME`. Por exemplo, se o nome do host for `github.octoinc.com`, obtenha um certificado com o valor de Nome Comum definido como `*.github.octoinc.com` e um valor SAN definido como `github.octoinc.com` e `*.github.octoinc.com`. -- Habilite o TLS no appliance. Para obter mais informações, confira "[Como configurar o TLS](/enterprise/admin/guides/installation/configuring-tls/)". +- Set up a wildcard Domain Name System (DNS) record or individual DNS records for the subdomains listed above. We recommend creating an A record for `*.HOSTNAME` that points to your server's IP address so you don't have to create multiple records for each subdomain. +- Get a wildcard Transport Layer Security (TLS) certificate for `*.HOSTNAME` with a Subject Alternative Name (SAN) for both `HOSTNAME` and the wildcard domain `*.HOSTNAME`. For example, if your hostname is `github.octoinc.com`, get a certificate with the Common Name value set to `*.github.octoinc.com` and a SAN value set to both `github.octoinc.com` and `*.github.octoinc.com`. +- Enable TLS on your appliance. For more information, see "[Configuring TLS](/enterprise/admin/guides/installation/configuring-tls/)." -## Habilitar isolamento de subdomínio +## Enabling subdomain isolation -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.hostname-menu-item %} -4. Selecione **Isolamento de subdomínio (recomendado)** . - ![Caixa de seleção usada para habilitar o isolamento de subdomínio](/assets/images/enterprise/management-console/subdomain-isolation.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.hostname-menu-item %} +4. Select **Subdomain isolation (recommended)**. + ![Checkbox to enable subdomain isolation](/assets/images/enterprise/management-console/subdomain-isolation.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/network-ports.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/network-ports.md index b4d872da98..576fc56eeb 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/network-ports.md +++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/network-ports.md @@ -1,5 +1,5 @@ --- -title: Portas de rede +title: Network ports redirect_from: - /enterprise/admin/articles/configuring-firewalls - /enterprise/admin/articles/firewall @@ -8,7 +8,7 @@ redirect_from: - /enterprise/admin/installation/network-ports - /enterprise/admin/configuration/network-ports - /admin/configuration/network-ports -intro: 'Abra as portas de rede seletivamente com base nos serviços que você precisa expor para administradores, usuários finais e suporte por e-mail.' +intro: 'Open network ports selectively based on the network services you need to expose for administrators, end users, and email support.' versions: ghes: '*' type: reference @@ -17,58 +17,52 @@ topics: - Infrastructure - Networking - Security -ms.openlocfilehash: eab2bed3f07c3e9e7ebad900047c1aa74a1d0bc1 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145095987' --- -## Portas administrativas +## Administrative ports -Algumas portas administrativas são obrigatórias para configurar o {% data variables.product.product_location %} e executar determinados recursos. Não é preciso haver portas administrativas para os usuários finais aproveitarem os recursos básicos do aplicativo. +Some administrative ports are required to configure {% data variables.location.product_location %} and run certain features. Administrative ports are not required for basic application use by end users. -| Porta | Serviço | Descrição | +| Port | Service | Description | |---|---|---| -| 8443 | HTTPS | {% data variables.enterprise.management_console %} seguro na web. Obrigatória para instalação e configuração básicas. | -| 8080 | HTTP | {% data variables.enterprise.management_console %} de texto simples na web. Não é obrigatória, a menos que o TSL seja desabilitado manualmente. | -| 122 | SSH | Acesso de shell ao {% data variables.product.product_location %}. Obrigatório para estar aberto a conexões de entrada entre todos os nós em uma configuração de alta disponibilidade. A porta SSH padrão (22) é dedicada ao tráfego de rede de aplicativos Git e SSH. | -| 1194/UDP | VPN | Túnel de rede de réplica segura na configuração de alta disponibilidade. Obrigatório estar aberto para a comunicação entre todos os nós da configuração.| -| 123/UDP| NTP | Obrigatória para operações de protocolo de tempo. | -| 161/UDP | SNMP | Obrigatória para operações de protocolo de monitoramento de rede. | +| 8443 | HTTPS | Secure web-based {% data variables.enterprise.management_console %}. Required for basic installation and configuration. | +| 8080 | HTTP | Plain-text web-based {% data variables.enterprise.management_console %}. Not required unless TLS is disabled manually. | +| 122 | SSH | Shell access for {% data variables.location.product_location %}. Required to be open to incoming connections between all nodes in a high availability configuration. The default SSH port (22) is dedicated to Git and SSH application network traffic. | +| 1194/UDP | VPN | Secure replication network tunnel in high availability configuration. Required to be open for communication between all nodes in the configuration.| +| 123/UDP| NTP | Required for time protocol operation. | +| 161/UDP | SNMP | Required for network monitoring protocol operation. | -## Portas de aplicativo para usuários finais +## Application ports for end users -As portas de aplicativo fornecem aplicativos da web e acesso dos usuários finais ao Git. +Application ports provide web application and Git access for end users. -| Porta | Serviço | Descrição | +| Port | Service | Description | |---|---|---| -| 443 | HTTPS | Acesso ao aplicativo da web e ao Git por HTTPS. | -| 80 | HTTP | Acesso ao aplicativo da web. Todas as solicitações são redirecionadas para a porta HTTPS se o TLS estiver configurado. | -| 22 | SSH | Acesso ao Git por SSH. Compatível com operações de clonagem, fetch e push em repositórios públicos e privados. | -| 9418 | Git | A porta do protocolo Git é compatível com operações de clonagem e fetch em repositórios públicos com comunicação de rede não criptografada. {% data reusables.enterprise_installation.when-9418-necessary %} | +| 443 | HTTPS | Access to the web application and Git over HTTPS. | +| 80 | HTTP | Access to the web application. All requests are redirected to the HTTPS port if TLS is configured. | +| 22 | SSH | Access to Git over SSH. Supports clone, fetch, and push operations to public and private repositories. | +| 9418 | Git | Git protocol port supports clone and fetch operations to public repositories with unencrypted network communication. {% data reusables.enterprise_installation.when-9418-necessary %} | {% data reusables.enterprise_installation.terminating-tls %} -## Portas de e-mail +## Email ports -As portas de e-mail devem estar acessíveis diretamente ou via retransmissão para oferecer suporte de e-mail aos usuários finais. +Email ports must be accessible directly or via relay for inbound email support for end users. -| Porta | Serviço | Descrição | +| Port | Service | Description | |---|---|---| -| 25 | SMTP | Suporte a SMTP com criptografia (STARTTLS). | +| 25 | SMTP | Support for SMTP with encryption (STARTTLS). | -## Portas de {% data variables.product.prodname_actions %} +## {% data variables.product.prodname_actions %} ports -As portas de {% data variables.product.prodname_actions %} devem poder ser acessadas por executores auto-hospedados para se conectar a {% data variables.product.product_location %}. Para obter mais informações, confira "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-server)". +{% data variables.product.prodname_actions %} ports must be accessible for self-hosted runners to connect to {% data variables.location.product_location %}. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-server)." -| Porta | Serviço | Descrição | +| Port | Service | Description | |---|---|---| -| 443 | HTTPS | Os executores auto-hospedados conectam a {% data variables.product.product_location %} para receber atividades de trabalho e fazer o download das novas versões do aplicativo do executor. Obrigatório se TLS estiver configurado. -| 80 | HTTP | Os executores auto-hospedados conectam a {% data variables.product.product_location %} para receber atividades de trabalho e fazer o download das novas versões do aplicativo do executor. Obrigatório se TLS não estiver configurado. +| 443 | HTTPS | Self-hosted runners connect to {% data variables.location.product_location %} to receive job assignments and to download new versions of the runner application. Required if TLS is configured. +| 80 | HTTP | Self-hosted runners connect to {% data variables.location.product_location %} to receive job assignments and to download new versions of the runner application. Required if TLS is not configured. -Se você habilitar o acesso automático a ações de {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_actions %} sempre irá pesquisar uma ação em {% data variables.product.product_location %} primeiro, por meio dessas portas, antes de verificar {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, confira "[Como habilitar o acesso automático às ações do {% data variables.product.prodname_dotcom_the_website %} usando o {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#about-resolution-for-actions-using-github-connect)". +If you enable automatic access to {% data variables.product.prodname_dotcom_the_website %} actions, {% data variables.product.prodname_actions %} will always search for an action on {% data variables.location.product_location %} first, via these ports, before checking {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#about-resolution-for-actions-using-github-connect)." -## Leitura adicional +## Further reading -- "[Como configurar o TLS](/admin/configuration/configuring-network-settings/configuring-tls)" +- "[Configuring TLS](/admin/configuration/configuring-network-settings/configuring-tls)" diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md index c6670a6fa6..955ed62c25 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md +++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md @@ -1,6 +1,6 @@ --- -title: Usar o GitHub Enterprise Server com balanceador de carga -intro: 'Use um balanceador de carga na frente de uma única instância {% data variables.product.prodname_ghe_server %} ou um par de instâncias em uma configuração de alta disponibilidade.' +title: Using GitHub Enterprise Server with a load balancer +intro: 'Use a load balancer in front of a single {% data variables.product.prodname_ghe_server %} instance or a pair of instances in a High Availability configuration.' redirect_from: - /enterprise/admin/guides/installation/using-github-enterprise-with-a-load-balancer - /enterprise/admin/installation/using-github-enterprise-server-with-a-load-balancer @@ -15,22 +15,17 @@ topics: - Infrastructure - Networking shortTitle: Use a load balancer -ms.openlocfilehash: dcbd1261d127e48140f6b6843ef4ec3c35fb84f4 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147167312' --- -## Sobre balanceadores de carga + +## About load balancers {% data reusables.enterprise_clustering.load_balancer_intro %} {% data reusables.enterprise_clustering.load_balancer_dns %} -## Informações de conexão do cliente +## Handling client connection information -Como as conexões do cliente com o {% data variables.product.prodname_ghe_server %} vêm do balanceador de carga, pode ocorrer a perda do endereço IP do cliente. +Because client connections to {% data variables.product.prodname_ghe_server %} come from the load balancer, the client IP address can be lost. {% data reusables.enterprise_clustering.proxy_preference %} @@ -38,63 +33,70 @@ Como as conexões do cliente com o {% data variables.product.prodname_ghe_server {% data reusables.enterprise_installation.terminating-tls %} -### Como habilitar o suporte ao protocolo PROXY no {% data variables.product.product_location %} +### Enabling PROXY protocol support on {% data variables.location.product_location %} -É altamente recomendável ativar o suporte ao protocolo PROXY para sua instância e o balanceador de carga. Use as instruções do fornecedor para habilitar o protocolo PROXY no balanceador de carga. Para obter mais informações, confira a [documentação do protocolo PROXY](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt). +We strongly recommend enabling PROXY protocol support for both your instance and the load balancer. Use the instructions provided by your vendor to enable the PROXY protocol on your load balancer. For more information, see [the PROXY protocol documentation](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt). {% data reusables.enterprise_installation.proxy-incompatible-with-aws-nlbs %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} -3. Em **Balanceadores de carga externos**, selecione **Habilitar suporte para o protocolo PROXY**. -![Caixa de seleção usada para habilitar o suporte para o protocolo PROXY](/assets/images/enterprise/management-console/enable-proxy.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +3. Under **External load balancers**, select **Enable support for PROXY protocol**. +![Checkbox to enable support for PROXY protocol](/assets/images/enterprise/management-console/enable-proxy.png) +{% data reusables.enterprise_management_console.save-settings %} {% data reusables.enterprise_clustering.proxy_protocol_ports %} -### Como habilitar o suporte a X-Forwarded-For no {% data variables.product.product_location %} +### Enabling X-Forwarded-For support on {% data variables.location.product_location %} {% data reusables.enterprise_clustering.x-forwarded-for %} {% warning %} -**Aviso**: se você configurar o suporte do `X-Forwarded-For` no {% data variables.product.product_location %} e balanceador de carga, talvez não consiga se conectar ao {% data variables.enterprise.management_console %}. Para ver mais informações, confira "[Erro: "Sua sessão expirou" para conexões com os dados {% data variables.enterprise.management_console %}](/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer#error-your-session-has-expired-for-connections-to-the-management-console)". +**Warning**: If you configure `X-Forwarded-For` support on {% data variables.location.product_location %} and load balancer, you may not be able to connect to the {% data variables.enterprise.management_console %}. For more information, see "[Error: "Your session has expired" for connections to the {% data variables.enterprise.management_console %}](/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer#error-your-session-has-expired-for-connections-to-the-management-console)." {% endwarning %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} -3. Em **Balanceadores de carga externos**, selecione **Permitir cabeçalho HTTP X-Forwarded-For**. -![Caixa de seleção usada para permitir o cabeçalho HTTP X-Forwarded-For](/assets/images/enterprise/management-console/allow-xff.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +3. Under **External load balancers**, select **Allow HTTP X-Forwarded-For header**. +![Checkbox to allow the HTTP X-Forwarded-For header](/assets/images/enterprise/management-console/allow-xff.png) +{% data reusables.enterprise_management_console.save-settings %} {% data reusables.enterprise_clustering.without_proxy_protocol_ports %} -## Configurar verificações de integridade +## Configuring health checks -As verificações de integridade permitem que um balanceador de carga pare de enviar tráfego para um nó que não responde em caso de falha na verificação pré-configurada do nó em questão. Se a instância estiver offline devido a manutenção ou falha inesperada, o balanceador de carga poderá exibir uma página de status. Em configurações de alta disponibilidade (HA), é possível usar balanceadores de carga como parte da estratégia de failover. No entanto, não há suporte para failover automático de pares de HA. Você deve promover manualmente a instância de réplica antes que ela comece a atender às solicitações. Para obter mais informações, confira "[Como configurar o {% data variables.product.prodname_ghe_server %} para alta disponibilidade](/enterprise/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)". +Health checks allow a load balancer to stop sending traffic to a node that is not responding if a pre-configured check fails on that node. If the instance is offline due to maintenance or unexpected failure, the load balancer can display a status page. In a High Availability (HA) configuration, a load balancer can be used as part of a failover strategy. However, automatic failover of HA pairs is not supported. You must manually promote the replica instance before it will begin serving requests. For more information, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/enterprise/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)." -{% data reusables.enterprise_clustering.health_checks %} {% data reusables.enterprise_site_admin_settings.maintenance-mode-status %} +{% data reusables.enterprise_clustering.health_checks %} +{% data reusables.enterprise_site_admin_settings.maintenance-mode-status %} -## Solução de problemas de conectividade por meio de um balanceador de carga +## Troubleshooting connectivity through a load balancer -Se você não conseguiu se conectar aos serviços do {% data variables.product.product_location %} por meio de um balanceador de carga, examine as informações a seguir para solucionar o problema. +If you cannot connect to services on {% data variables.location.product_location %} through a load balancer, you can review the following information to troubleshoot the problem. {% note %} -**Observação**: sempre teste as alterações na sua infraestrutura de rede e na configuração da instância em um ambiente de preparo. Para obter mais informações, confira "[Como configurar uma instância de preparo](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)". +**Note**: Always test changes to your network infrastructure and instance configuration in a staging environment. For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)." {% endnote %} -### Erro: "Sua sessão expirou" para conexões com {% data variables.enterprise.management_console %} +### Error: "Your session has expired" for connections to the {% data variables.enterprise.management_console %} -Se você habilitar o suporte para o cabeçalho `X-Forwarded-For` em sua instância e balanceador de carga, talvez não consiga acessar o {% data variables.enterprise.management_console %} de sua instância. Para ver mais informações sobre o {% data variables.enterprise.management_console %} e portas exigidas nas conexões, confira "[Como acessar o console de gerenciamento](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)" e "[Portas de rede](/admin/configuration/configuring-network-settings/network-ports)". +If you enable support for the `X-Forwarded-For` header on your instance and load balancer, you may not be able to access your instance's {% data variables.enterprise.management_console %}. For more information about the {% data variables.enterprise.management_console %} and ports required for connections, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)" and "[Network ports](/admin/configuration/configuring-network-settings/network-ports)." -Se {% data variables.product.product_location %} indicar que sua sessão expirou quando você se conectar a {% data variables.enterprise.management_console %} por meio de um balanceador de carga, tente uma das seguintes configurações em seu balanceador de carga. +If {% data variables.location.product_location %} indicates that your session has expired when you connect to the {% data variables.enterprise.management_console %} through a load balancer, try one of the following configurations on your load balancer. -- Desabilite os cabeçalhos de `X-Forwarded-For` para conexões com sua instância nas portas 8080 e 8443. -- Configure o balanceador de carga para operar na Camada 4 e use o protocolo PROXY em vez de `X-Forwarded-For` para passagem de endereços IP do cliente. Para saber mais, confira "[Habilitar o suporte ao protocolo PROXY no {% data variables.product.product_location %}](#enabling-proxy-protocol-support-on-your-github-enterprise-server-instance)". +- Disable `X-Forwarded-For` headers for connections to your instance on ports 8080 and 8443. +- Configure your load balancer to operate on Layer 4, and use the PROXY protocol instead of `X-Forwarded-For` for passthrough of client IP addresses. For more information, see "[Enabling PROXY protocol support on {% data variables.location.product_location %}](#enabling-proxy-protocol-support-on-your-github-enterprise-server-instance)." -Para ver mais informações, confira a documentação do balanceador de carga. +For more information, refer to the documentation for your load balancer. -### Atualizações dinâmicas de problemas e verificações que não funcionam +### Live updates to issues and check runs not working -Quando {% data variables.product.product_location %} é acessado por meio de um balanceador de carga ou proxy reverso, as atualizações dinâmicas esperadas, como novos comentários sobre problemas e alterações nos selos de notificação ou saída de execução de verificação, podem não ser exibidas até que a página seja atualizada. Isso é mais comum quando o proxy reverso ou o balanceador de carga está sendo executado em um modo de camada 7 ou não oferece suporte ao protocolo [websocket](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API) necessário. +When {% data variables.location.product_location %} is accessed via a load balancer or reverse proxy, expected live updates, such as new comments on issues and changes in notification badges or check run output, may not display until the page is refreshed. This is most common when the reverse proxy or load balancer is running in a layer 7 mode or does not support the required [websocket](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API) protocol. -Para habilitar atualizações dinâmicas, talvez seja necessário reconfigurar o balanceador de carga ou o proxy. Para ver mais informações, confira a documentação do balanceador de carga. +To enable live updates, you may need to reconfigure the load balancer or proxy. For more information, refer to the documentation for your load balancer. diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md index 23c025c656..50ed3a2fa2 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md +++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md @@ -1,6 +1,6 @@ --- -title: Validar configurações de domínio -intro: 'Antes de inicializar o {% data variables.product.product_location %} pela primeira vez, verifique se as configurações de domínio estão configuradas corretamente.' +title: Validating your domain settings +intro: 'Ensure that your domain settings are properly configured before booting up {% data variables.location.product_location %} for the first time.' redirect_from: - /enterprise/admin/installation/validating-your-domain-settings - /enterprise/admin/configuration/validating-your-domain-settings @@ -14,13 +14,11 @@ topics: - Infrastructure - Networking shortTitle: Validate domain settings -ms.openlocfilehash: 113f7b3d3f335e73627cebf90a91cbf326c40c99 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145095984' --- -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.hostname-menu-item %} -4. Para testar as configurações de DNS e de SSL do dispositivo, clique em **Testar configurações de domínio**. - ![Botão Testar configurações de domínio](/assets/images/enterprise/management-console/test-domain-settings.png) {% data reusables.enterprise_management_console.test-domain-settings-failure %} {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.hostname-menu-item %} +4. To test your appliance's DNS and SSL settings, click **Test domain settings**. + ![Test domain settings button](/assets/images/enterprise/management-console/test-domain-settings.png) +{% data reusables.enterprise_management_console.test-domain-settings-failure %} +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md index e96f21e4a9..46eaace76c 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md @@ -1,5 +1,5 @@ --- -title: Acesar o shell administrativo (SSH) +title: Accessing the administrative shell (SSH) redirect_from: - /enterprise/admin/articles/ssh-access - /enterprise/admin/articles/adding-an-ssh-key-for-shell-access @@ -20,34 +20,30 @@ topics: - Fundamentals - SSH shortTitle: Access the admin shell (SSH) -ms.openlocfilehash: 8d8b9cd71a436c0874355b1bdd53ba2e400660a0 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145095983' --- -## Sobre o acesso ao shell administrativo +## About administrative shell access -Se tiver acesso por SSH ao shell administrativo, você poderá executar os utilitários de linha de comando do {% data variables.product.prodname_ghe_server %}. O acesso SSH também é útil para solucionar problemas, fazer backups e configurar a replicação. O acesso a SSH administrativa é gerenciado separadamente do acesso SSH do Git e fica acessível apenas pela porta 122. +If you have SSH access to the administrative shell, you can run {% data variables.product.prodname_ghe_server %}'s command line utilities. SSH access is also useful for troubleshooting, running backups, and configuring replication. Administrative SSH access is managed separately from Git SSH access and is accessible only via port 122. -## Habilitar o acesso ao shell administrativo por SSH +## Enabling access to the administrative shell via SSH -Para habilitar o acesso a SSH administrativa, você deve adicionar sua chave pública SSH à lista de chaves autorizadas da instância. +To enable administrative SSH access, you must add your SSH public key to your instance's list of authorized keys. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)." {% tip %} -**Dica:** as alterações nas chaves SSH autorizadas entram em vigor imediatamente. +**Tip:** Changes to authorized SSH keys take effect immediately. {% endtip %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} -3. Em "Acesso SSH", cole a chave na caixa de texto e clique em **Adicionar chave**. - ![Caixa de texto e botão usados para adicionar uma chave SSH](/assets/images/enterprise/settings/add-authorized-ssh-key-admin-shell.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +3. Under "SSH access", paste your key into the text box, then click **Add key**. + ![Text box and button for adding an SSH key](/assets/images/enterprise/settings/add-authorized-ssh-key-admin-shell.png) +{% data reusables.enterprise_management_console.save-settings %} -## Conectar-se ao shell administrativo por SSH +## Connecting to the administrative shell over SSH -Depois de adicionar sua chave SSH à lista, conecte-se à instância via SSH como o usuário `admin` na porta 122. +After you've added your SSH key to the list, connect to the instance over SSH as the `admin` user on port 122. ```shell $ ssh -p 122 admin@github.example.com @@ -55,29 +51,29 @@ Last login: Sun Nov 9 07:53:29 2014 from 169.254.1.1 admin@github-example-com:~$ █ ``` -### Solucionar problemas de conectividade com SSH +### Troubleshooting SSH connection problems -Se você encontrar o erro `Permission denied (publickey)` ao tentar se conectar ao {% data variables.product.product_location %} via SSH, confirme se está se conectando pela porta 122. Talvez seja necessário especificar explicitamente a chave SSH privada em uso. +If you encounter the `Permission denied (publickey)` error when you try to connect to {% data variables.location.product_location %} via SSH, confirm that you are connecting over port 122. You may need to explicitly specify which private SSH key to use. -Para especificar uma chave SSH privada usando a linha de comando, execute `ssh` com o argumento `-i`. +To specify a private SSH key using the command line, run `ssh` with the `-i` argument. ```shell -ssh -i /path/to/ghe_private_key -p 122 admin@hostname +ssh -i /path/to/ghe_private_key -p 122 admin@HOSTNAME ``` -Você também pode especificar uma chave SSH privada usando o arquivo de configuração SSH (`~/.ssh/config`). +You can also specify a private SSH key using the SSH configuration file (`~/.ssh/config`). ```shell -Host hostname +Host HOSTNAME IdentityFile /path/to/ghe_private_key User admin Port 122 ``` -## Acesar o shell administrativo usando o console local +## Accessing the administrative shell using the local console -Em uma situação de emergência, se o acesso por SSH estiver indisponível, você poderá acessar o shell administrativo localmente. Entre como o usuário `admin` e use a senha estabelecida durante a configuração inicial do {% data variables.product.prodname_ghe_server %}. +In an emergency situation, for example if SSH is unavailable, you can access the administrative shell locally. Sign in as the `admin` user and use the password established during initial setup of {% data variables.product.prodname_ghe_server %}. -## Limitações de acesso ao shell administrativo +## Access limitations for the administrative shell -O acesso ao shell administrativo é permitido apenas para solucionar problemas e executar procedimentos de operações documentadas. Modificar arquivos de aplicativos e sistemas, executar programas ou instalar pacotes de software não compatíveis pode anular seu contrato de suporte. Entre em contato com o {% data variables.contact.contact_ent_support %} em caso de perguntas sobre as atividades permitidas pelo contrato. +Administrative shell access is permitted for troubleshooting and performing documented operations procedures only. Modifying system and application files, running programs, or installing unsupported software packages may void your support contract. Please contact {% data variables.contact.contact_ent_support %} if you have a question about the activities allowed by your support contract. diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md index c30cc77043..83da0eb50e 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md @@ -1,5 +1,5 @@ --- -title: Acessar o console de gerenciamento +title: Accessing the management console intro: '{% data reusables.enterprise_site_admin_settings.about-the-management-console %}' redirect_from: - /enterprise/admin/articles/about-the-management-console @@ -18,52 +18,48 @@ topics: - Enterprise - Fundamentals shortTitle: Access the management console -ms.openlocfilehash: 3ddf8deb75c72679fc3e446127fc43ae6f5de4d3 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146332373' --- -## Sobre o {% data variables.enterprise.management_console %} +## About the {% data variables.enterprise.management_console %} -Use o {% data variables.enterprise.management_console %} para atividades administrativas básicas: -- **Configuração inicial**: siga o processo de instalação inicial ao iniciar o {% data variables.product.product_location %} acessando o endereço IP do {% data variables.product.product_location %} no navegador. -- **Definição das configurações básicas da sua instância**: configure o DNS, o nome do host, o SSL, a autenticação do usuário, o email, os serviços de monitoramento e o encaminhamento de log na página Configurações. -- **Agendamento das janelas de manutenção**: coloque o {% data variables.product.product_location %} offline ao executar a manutenção usando o {% data variables.enterprise.management_console %} ou o shell administrativo. -- **Solução de problemas**: gere um pacote de suporte ou veja informações de diagnóstico de alto nível. -- **Gerenciamento de licenças**: veja ou atualize sua licença do {% data variables.product.prodname_enterprise %}. +Use the {% data variables.enterprise.management_console %} for basic administrative activities: +- **Initial setup**: Walk through the initial setup process when first launching {% data variables.location.product_location %} by visiting {% data variables.location.product_location %}'s IP address in your browser. +- **Configuring basic settings for your instance**: Configure DNS, hostname, SSL, user authentication, email, monitoring services, and log forwarding on the Settings page. +- **Scheduling maintenance windows**: Take {% data variables.location.product_location %} offline while performing maintenance using the {% data variables.enterprise.management_console %} or administrative shell. +- **Troubleshooting**: Generate a support bundle or view high level diagnostic information. +- **License management**: View or update your {% data variables.product.prodname_enterprise %} license. -Você sempre pode acessar o {% data variables.enterprise.management_console %} usando o endereço IP do {% data variables.product.product_location %}, mesmo quando a instância está no modo de manutenção ou há uma falha de aplicativo crítica ou um erro no nome do host ou na configuração do SSL. +You can always reach the {% data variables.enterprise.management_console %} using {% data variables.location.product_location %}'s IP address, even when the instance is in maintenance mode, or there is a critical application failure or hostname or SSL misconfiguration. -Para acessar o {% data variables.enterprise.management_console %}, você precisa usar a senha de administrador estabelecida durante a instalação inicial do {% data variables.product.product_location %}. Você também deve poder se conectar ao host da máquina virtual na porta 8443. Se tiver problemas para chegar ao {% data variables.enterprise.management_console %}, verifique as configurações intermediárias de firewall e grupo de segurança. +To access the {% data variables.enterprise.management_console %}, you must use the administrator password established during initial setup of {% data variables.location.product_location %}. You must also be able to connect to the virtual machine host on port 8443. If you're having trouble reaching the {% data variables.enterprise.management_console %}, please check intermediate firewall and security group configurations. -O hash de senha do {% data variables.enterprise.management_console %} é armazenado em `/data/user/common/secrets.conf`, e esse arquivo é sincronizado automaticamente do dispositivo primário com todas as réplicas de alta disponibilidade. Qualquer alteração na senha principal será automaticamente replicada em réplicas de alta disponibilidade. Para obter mais informações sobre alta disponibilidade, confira "[Sobre a configuração de alta disponibilidade](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration)". +The {% data variables.enterprise.management_console %} password hash is stored in `/data/user/common/secrets.conf`, and that file is automatically synced from the primary appliance to any high-availability replicas. Any change to the primary's password will automatically be replicated to high-availability replicas. For more information about high availability, see "[About high availability configuration](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration)." -## Acessar o {% data variables.enterprise.management_console %} como administrador do site +## Accessing the {% data variables.enterprise.management_console %} as a site administrator -A primeira vez que você acessar o {% data variables.enterprise.management_console %} como administrador do site, você deve enviar seu arquivo de licença do {% data variables.product.prodname_enterprise %} para efetuar a autenticação no aplicativo. Para obter mais informações, confira "[Como gerenciar sua licença do {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)". +The first time that you access the {% data variables.enterprise.management_console %} as a site administrator, you must upload your {% data variables.product.prodname_enterprise %} license file to authenticate into the app. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)." -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.type-management-console-password %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.type-management-console-password %} -## Acessar o {% data variables.enterprise.management_console %} como usuário não autenticado +## Accessing the {% data variables.enterprise.management_console %} as an unauthenticated user -1. Acesse essa URL no navegador, substituindo `hostname` pelo nome do host ou pelo endereço IP real do {% data variables.product.prodname_ghe_server %}: +1. Visit this URL in your browser, replacing `hostname` with your actual {% data variables.product.prodname_ghe_server %} hostname or IP address: ```shell http(s)://HOSTNAME/setup ``` {% data reusables.enterprise_management_console.type-management-console-password %} -## Desbloquear o {% data variables.enterprise.management_console %} após tentativas de login com falha +## Unlocking the {% data variables.enterprise.management_console %} after failed login attempts -O {% data variables.enterprise.management_console %} trava após dez tentativas de login com falha em um período de dez minutos. Antes de tentar novamente, aguarde o desbloqueio automático da tela de login, que ocorrerá após um período de dez minutos. A contagem é redefinida depois do login bem-sucedido. +The {% data variables.enterprise.management_console %} locks after ten failed login attempts are made in the span of ten minutes. You must wait for the login screen to automatically unlock before attempting to log in again. The login screen automatically unlocks as soon as the previous ten minute period contains fewer than ten failed login attempts. The counter resets after a successful login occurs. -Para desbloquear imediatamente o {% data variables.enterprise.management_console %}, use o comando `ghe-reactivate-admin-login` por meio do shell administrativo. Para obter mais informações, confira "[Utilitários de linha de comando](/enterprise/admin/guides/installation/command-line-utilities#ghe-reactivate-admin-login)" e "[Como acessar o shell administrativo (SSH)](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/)". +To immediately unlock the {% data variables.enterprise.management_console %}, use the `ghe-reactivate-admin-login` command via the administrative shell. For more information, see "[Command line utilities](/enterprise/admin/guides/installation/command-line-utilities#ghe-reactivate-admin-login)" and "[Accessing the administrative shell (SSH)](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/)." -## Solução de problemas de conexões com falha no {% data variables.enterprise.management_console %} +## Troubleshooting failed connections to the {% data variables.enterprise.management_console %} -Se você não puder se conectar ao {% data variables.enterprise.management_console %} no {% data variables.product.product_location %}, examine as informações a seguir para solucionar o problema. +If you cannot connect to the {% data variables.enterprise.management_console %} on {% data variables.location.product_location %}, you can review the following information to troubleshoot the problem. -### Erro: "Sua sessão expirou" de conexões por meio de um balanceador de carga +### Error: "Your session has expired" for connections through a load balancer -Se você acessar o {% data variables.product.product_location %} por meio de um balanceador de carga e as conexões com o {% data variables.enterprise.management_console %} falharem com uma mensagem de que a sessão expirou, talvez seja necessário reconfigurar o balanceador de carga. Para obter mais informações, confira "[Como usar o {% data variables.product.product_name %} com um balanceador de carga](/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer#error-your-session-has-expired-for-connections-to-the-management-console)". +If you access {% data variables.location.product_location %} through a load balancer and connections to the {% data variables.enterprise.management_console %} fail with a message that your session has expired, you may need to reconfigure your load balancer. For more information, see "[Using {% data variables.product.product_name %} with a load balancer](/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer#error-your-session-has-expired-for-connections-to-the-management-console)." diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md index 767556fe6c..f6ad7b034e 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md @@ -1,6 +1,6 @@ --- -title: Utilitários de linha de comando -intro: 'O {% data variables.product.prodname_ghe_server %} tem uma série de utilitários que ajudam a resolver problemas específicos ou a executar determinadas tarefas.' +title: Command-line utilities +intro: '{% data variables.product.prodname_ghe_server %} includes a variety of utilities to help resolve particular problems or perform specific tasks.' redirect_from: - /enterprise/admin/articles/viewing-all-services - /enterprise/admin/articles/command-line-utilities @@ -14,20 +14,14 @@ type: reference topics: - Enterprise - SSH -ms.openlocfilehash: 2518f6636428d92f526debfa94b086e7ce596a85 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147648268' --- -Depois de entrar como usuário administrador com SSH, você pode executar esses comandos de qualquer lugar na VM. Para obter mais informações, confira "[Como acessar o shell administrativo (SSH)](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/)". +You can execute these commands from anywhere on the VM after signing in as an SSH admin user. For more information, see "[Accessing the administrative shell (SSH)](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/)." -## Geral +## General ### ghe-announce -Este utilitário insere um banner no topo de cada página do {% data variables.product.prodname_enterprise %}. Você pode usá-lo para enviar uma comunicação a todos os usuários. +This utility sets a banner at the top of every {% data variables.product.prodname_enterprise %} page. You can use it to broadcast a message to your users. ```shell # Sets a message that's visible to everyone @@ -38,7 +32,8 @@ $ ghe-announce -u > Removed the announcement message ``` -{% ifversion ghe-announce-dismiss %} Para permitir que cada usuário ignore o anúncio por conta própria, use o sinalizador `-d`. +{% ifversion ghe-announce-dismiss %} +To allow each user to dismiss the announcement for themselves, use the `-d` flag. ```shell # Sets a user-dismissible message that's visible to everyone $ ghe-announce -d -s MESSAGE @@ -49,7 +44,8 @@ $ ghe-announce -u ``` {% endif %} -{% ifversion ghes %} Você também pode definir um banner de anúncio usando as configurações da empresa no {% data variables.product.product_name %}. Para obter mais informações, confira "[Como personalizar as mensagens de usuário na sua instância](/enterprise/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)". +{% ifversion ghes %} +You can also set an announcement banner using the enterprise settings on {% data variables.product.product_name %}. For more information, see "[Customizing user messages on your instance](/enterprise/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)." {% endif %} {% ifversion ghes %} @@ -57,34 +53,34 @@ $ ghe-announce -u ### ghe-aqueduct -Este utilitário exibe informações sobre trabalhos em segundo plano, ativos e em fila. Ele fornece os mesmos números de contagem de trabalhos que a barra de estatísticas de administração, na parte superior de todas as páginas. +This utility displays information on background jobs, both active and in the queue. It provides the same job count numbers as the admin stats bar at the top of every page. -Este utilitário pode ajudar a identificar se o servidor de Aqueduct está tendo problemas no processamento de trabalhos em segundo plano. Qualquer dos seguintes cenários pode indicar um problema com o Aqueduct: +This utility can help identify whether the Aqueduct server is having problems processing background jobs. Any of the following scenarios might be indicative of a problem with Aqueduct: -* O número de trabalhos em segundo plano está aumentando, e os trabalhos ativos continuam iguais. -* Os feeds de evento não estão sendo atualizados. -* Webhooks não estão sendo acionados. -* A interface web não atualiza após um push do Git. +* The number of background jobs is increasing, while the active jobs remain the same. +* The event feeds are not updating. +* Webhooks are not being triggered. +* The web interface is not updating after a Git push. -Se você suspeitar que o Aqueduct tem uma falha, entre em contato com {% data variables.contact.contact_ent_support %} para obter ajuda. +If you suspect Aqueduct is failing, contact {% data variables.contact.contact_ent_support %} for help. -Com este comando, também é possível pausar ou retomar trabalhos na fila. +With this command, you can also pause or resume jobs in the queue. ```shell $ ghe-aqueduct status # lists queues and the number of currently queued jobs for all queues -$ ghe-aqueduct queue_depth --queue QUEUE +$ ghe-aqueduct queue_depth --queue QUEUE # lists the number of currently queued jobs for the specified queue -$ ghe-aqueduct pause --queue QUEUE +$ ghe-aqueduct pause --queue QUEUE # pauses the specified queue -$ ghe-aqueduct resume --queue QUEUE +$ ghe-aqueduct resume --queue QUEUE # resumes the specified queue ``` {% endif %} ### ghe-check-disk-usage -Este utilitário verifica se há arquivos grandes ou arquivos excluídos no disco, mas que ainda têm identificadores abertos. Deve ser executado para liberar espaço na partição raiz. +This utility checks the disk for large files or files that have been deleted but still have open file handles. This should be run when you're trying to free up space on the root partition. ```shell ghe-check-disk-usage @@ -92,18 +88,18 @@ ghe-check-disk-usage ### ghe-cleanup-caches -Este utilitário limpa uma série de caches que podem vir a ocupar espaço extra em disco no volume raiz. Se você perceber que o uso do espaço em disco do volume raiz aumenta muito ao longo do tempo, talvez seja uma boa ideia executar este utilitário e verificar se ele ajuda a reduzir o uso geral. +This utility cleans up a variety of caches that might potentially take up extra disk space on the root volume. If you find your root volume disk space usage increasing notably over time it would be a good idea to run this utility to see if it helps reduce overall usage. ```shell ghe-cleanup-caches ``` ### ghe-cleanup-settings -Este utilitário apaga todas as configurações do {% data variables.enterprise.management_console %}. +This utility wipes all existing {% data variables.enterprise.management_console %} settings. {% tip %} -**Dica**: {% data reusables.enterprise_enterprise_support.support_will_ask_you_to_run_command %} +**Tip**: {% data reusables.enterprise_enterprise_support.support_will_ask_you_to_run_command %} {% endtip %} @@ -113,35 +109,36 @@ ghe-cleanup-settings ### ghe-config -Com este utilitário, você pode recuperar e modificar as definições de configuração da {% data variables.product.product_location %}. +With this utility, you can both retrieve and modify the configuration settings of {% data variables.location.product_location %}. ```shell -$ ghe-config core.github-hostname +$ ghe-config core.github-hostname # Gets the configuration value of `core.github-hostname` -$ ghe-config core.github-hostname 'example.com' -# Sets the configuration value of `core.github-hostname` to `example.com` +$ ghe-config core.github-hostname URL +# Sets the configuration value of `core.github-hostname` to the specified URL $ ghe-config -l # Lists all the configuration values ``` -Permite encontrar o UUID (identificador universalmente exclusivo) do seu nó em `cluster.conf`. +Allows you to find the universally unique identifier (UUID) of your node in `cluster.conf`. ```shell - $ ghe-config HOSTNAME.uuid + $ ghe-config HOSTNAME.uuid ``` -{% ifversion ghes %} Permite isentar uma lista de usuários dos limites de taxa da API REST. Um limite rígido de 120.000 solicitações ainda será aplicado a esses usuários. Para obter mais informações, confira "[Recursos da API REST](/rest/overview/resources-in-the-rest-api#rate-limiting)". +{% ifversion ghes %} +Allows you to exempt a list of users from REST API rate limits. A hard limit of 120,000 requests will still apply to these users. For more information, see "[Resources in the REST API](/rest/overview/resources-in-the-rest-api#rate-limiting)." ``` shell -$ ghe-config app.github.rate-limiting-exempt-users "hubot github-actions" +$ ghe-config app.github.rate-limiting-exempt-users "HUBOT GITHUB-ACTIONS" # Exempts the users hubot and github-actions from rate limits ``` {% endif %} ### ghe-config-apply -Este utilitário aplica configurações do {% data variables.enterprise.management_console %}, recarrega os serviços do sistema, prepara um dispositivo de armazenamento, recarrega os serviços de aplicativos e executa as migrações pendentes de banco de dados. Isso é equivalente a clicar em **Salvar configurações** na interface do usuário da Web do {% data variables.enterprise.management_console %} ou a enviar uma solicitação POST [ao ponto de extremidade `/setup/api/configure`](/enterprise/user/rest/reference/enterprise-admin#management-console). +This utility applies {% data variables.enterprise.management_console %} settings, reloads system services, prepares a storage device, reloads application services, and runs any pending database migrations. It is equivalent to clicking **Save settings** in the {% data variables.enterprise.management_console %}'s web UI or to sending a POST request to [the `/setup/api/configure` endpoint](/enterprise/user/rest/reference/enterprise-admin#management-console). -É provável que você não precise executar essa ação manualmente, mas é possível fazer isso caso você queira automatizar o processo de salvar suas configurações via SSH. +You will probably never need to run this manually, but it's available if you want to automate the process of saving your settings via SSH. ```shell ghe-config-apply @@ -149,7 +146,7 @@ ghe-config-apply ### ghe-console -Este utilitário abre o console do GitHub Rails no appliance do {% data variables.product.prodname_enterprise %}. {% data reusables.command_line.use_with_support_only %} +This utility opens the GitHub Rails console on your {% data variables.product.prodname_enterprise %} appliance. {% data reusables.command_line.use_with_support_only %} ```shell ghe-console @@ -157,16 +154,16 @@ ghe-console ### ghe-dbconsole -Este utilitário abre uma sessão do banco de dados MySQL no appliance do {% data variables.product.prodname_enterprise %}. {% data reusables.command_line.use_with_support_only %} +This utility opens a MySQL database session on your {% data variables.product.prodname_enterprise %} appliance. {% data reusables.command_line.use_with_support_only %} ```shell ghe-dbconsole ``` ### ghe-es-index-status -Este utilitário retorna um resumo dos índices do Elasticsearch no formato CSV. +This utility returns a summary of Elasticsearch indexes in CSV format. -Imprima um resumo do índice com uma linha de cabeçalho em `STDOUT`: +Print an index summary with a header row to `STDOUT`: ```shell $ ghe-es-index-status -do > warning: parser/current is loading parser/ruby23, which recognizes @@ -185,7 +182,7 @@ $ ghe-es-index-status -do > wikis-4,true,true,true,true,100.0,2613dec44bd14e14577803ac1f9e4b7e07a7c234 ``` -Imprima um resumo do índice e encaminhe os resultados para `column` a fim de facilitar a leitura: +Print an index summary and pipe results to `column` for readability: ```shell $ ghe-es-index-status -do | column -ts, @@ -207,7 +204,7 @@ $ ghe-es-index-status -do | column -ts, ### ghe-legacy-github-services-report -Este utilitário lista os repositórios no appliance que usam o {% data variables.product.prodname_dotcom %} Services, um método de integração que será descontinuado em 1 de outubro de 2018. Os usuários do seu appliance podem ter configurado o {% data variables.product.prodname_dotcom %} Services para criar notificações de pushes em determinados repositórios. Para obter mais informações, confira "[Comunicado sobre a reprovação do {% data variables.product.prodname_dotcom %} Services](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)" no {% data variables.product.prodname_blog %} ou "[Substituição do {% data variables.product.prodname_dotcom %} Services](/developers/overview/replacing-github-services)". Para saber mais sobre este comando ou ver opções adicionais, use o sinalizador `-h`. +This utility lists repositories on your appliance that use {% data variables.product.prodname_dotcom %} Services, an integration method that will be discontinued on October 1, 2018. Users on your appliance may have set up {% data variables.product.prodname_dotcom %} Services to create notifications for pushes to certain repositories. For more information, see "[Announcing the deprecation of {% data variables.product.prodname_dotcom %} Services](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)" on {% data variables.product.prodname_blog %} or "[Replacing {% data variables.product.prodname_dotcom %} Services](/developers/overview/replacing-github-services)." For more information about this command or for additional options, use the `-h` flag. ```shell ghe-legacy-github-services-report @@ -216,7 +213,7 @@ ghe-legacy-github-services-report ### ghe-logs-tail -Este utilitário permite registrar todos os arquivos de log relevantes da sua instalação. Você pode passar as opções para limitar os logs a conjuntos específicos. Para consultar opções adicionais, use o sinalizador -h. +This utility lets you tail log all relevant log files from your installation. You can pass options in to limit the logs to specific sets. Use the -h flag for additional options. ```shell ghe-logs-tail @@ -224,7 +221,7 @@ ghe-logs-tail ### ghe-maintenance -Este utilitário permite controlar o estado do modo de manutenção da instalação. Ele foi desenvolvido para uso principalmente nos bastidores do {% data variables.enterprise.management_console %}, mas também pode ser usado diretamente. Para obter mais informações, confira "[Como habilitar e agendar o modo de manutenção](/admin/guides/installation/enabling-and-scheduling-maintenance-mode)". +This utility allows you to control the state of the installation's maintenance mode. It's designed to be used primarily by the {% data variables.enterprise.management_console %} behind-the-scenes, but it can be used directly. For more information, see "[Enabling and scheduling maintenance mode](/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." ```shell ghe-maintenance -h @@ -232,7 +229,7 @@ ghe-maintenance -h ### ghe-motd -Este utilitário exibe novamente a mensagem do dia (MOTD) que os administradores veem quando acessam a instância através do shell administrativo. A saída contém uma visão geral do estado da instância. +This utility re-displays the message of the day (MOTD) that administrators see when accessing the instance via the administrative shell. The output contains an overview of the instance's state. ```shell ghe-motd @@ -240,44 +237,44 @@ ghe-motd ### ghe-nwo -Este utilitário retorna o nome e o proprietário de um repositório com base no ID do repositório. +This utility returns a repository's name and owner based on the repository ID. ```shell -ghe-nwo REPOSITORY_ID +ghe-nwo REPOSITORY_ID ``` ### ghe-org-admin-promote -Use este comando para conceder privilégios de proprietário da organização a usuários com privilégios de administrador do site no appliance ou a qualquer usuário em uma única organização. Você deve especificar um usuário e/ou organização. O comando `ghe-org-admin-promote` sempre solicitará a confirmação antes da execução, a menos que você use o sinalizador `-y` para ignorar a confirmação. +Use this command to give organization owner privileges to users with site admin privileges on the appliance, or to give organization owner privileges to any single user in a single organization. You must specify a user and/or an organization. The `ghe-org-admin-promote` command will always ask for confirmation before running unless you use the `-y` flag to bypass the confirmation. -É possível usar estas opções com o utilitário: +You can use these options with the utility: -- O sinalizador `-u` especifica um nome de usuário. Use este sinalizador para conceder privilégios de proprietário da organização a um usuário. Omita o sinalizador `-u` para promover todos os administradores do site à organização especificada. -- O sinalizador `-o` especifica uma organização. Use este sinalizador para conceder privilégios de proprietário em uma organização. Omita o sinalizador `-o` para conceder permissões de proprietário em todas as organizações a um administrador do site especificado. -- O sinalizador `-a` concede privilégios de proprietário em todas as organizações a todos os administradores do site. -- O sinalizador `-y` ignora a confirmação manual. +- The `-u` flag specifies a username. Use this flag to give organization owner privileges to a specific user. Omit the `-u` flag to promote all site admins to the specified organization. +- The `-o` flag specifies an organization. Use this flag to give owner privileges in a specific organization. Omit the `-o` flag to give owner permissions in all organizations to the specified site admin. +- The `-a` flag gives owner privileges in all organizations to all site admins. +- The `-y` flag bypasses the manual confirmation. -Este utilitário não pode promover um administrador externo a proprietário de todas as organizações. Você pode promover uma conta de usuário comum a administrador do site com [ghe-user-promote](#ghe-user-promote). +This utility cannot promote a non-site admin to be an owner of all organizations. You can promote an ordinary user account to a site admin with [ghe-user-promote](#ghe-user-promote). -Conceder privilégios de proprietário da organização em uma organização específica para um administrador específico do site +Give organization owner privileges in a specific organization to a specific site admin ```shell -ghe-org-admin-promote -u USERNAME -o ORGANIZATION +ghe-org-admin-promote -u USERNAME -o ORGANIZATION ``` -Conceder privilégios de proprietário da organização a um administrador do site em todas as organizações +Give organization owner privileges in all organizations to a specific site admin ```shell -ghe-org-admin-promote -u USERNAME +ghe-org-admin-promote -u USERNAME ``` -Conceder privilégios de proprietário da organização a todos os administradores do site em uma organização específica +Give organization owner privileges in a specific organization to all site admins ```shell -ghe-org-admin-promote -o ORGANIZATION +ghe-org-admin-promote -o ORGANIZATION ``` -Conceder privilégios de proprietário da organização a todos os administradores do site em todas as organizações +Give organization owner privileges in all organizations to all site admins ```shell ghe-org-admin-promote -a @@ -285,7 +282,7 @@ ghe-org-admin-promote -a ### ghe-reactivate-admin-login -Use este comando para desbloquear imediatamente o {% data variables.enterprise.management_console %} após 10 tentativas de login com falha no período de 10 minutos. +Use this command to immediately unlock the {% data variables.enterprise.management_console %} after 10 failed login attempts in the span of 10 minutes. ```shell $ ghe-reactivate-admin-login @@ -294,26 +291,26 @@ $ ghe-reactivate-admin-login ### ghe-saml-mapping-csv -Este utilitário pode ajudar a mapear os registros SAML. +This utility can help map SAML records. -Para criar um arquivo CSV contendo todo o mapeamento SAML para os seus usuários do {% data variables.product.product_name %}: +To create a CSV file containing all the SAML mapping for your {% data variables.product.product_name %} users: ```shell $ ghe-saml-mapping-csv -d ``` -Para executar uma execução seca de atualização de mapeamentos SAML com novos valores: +To perform a dry run of updating SAML mappings with new values: ```shell $ ghe-saml-mapping-csv -u -n -f /path/to/file ``` -Para atualizar os mapeamentos SAML com novos valores: +To update SAML mappings with new values: ```shell $ ghe-saml-mapping-csv -u -f /path/to/file ``` ### ghe-service-list -Este utilitário lista todos os serviços iniciados ou parados (em execução ou em espera) no appliance. +This utility lists all of the services that have been started or stopped (are running or waiting) on your appliance. ```shell $ ghe-service-list @@ -340,7 +337,7 @@ stop/waiting ### ghe-set-password -Com `ghe-set-password`, você pode definir uma nova senha para se autenticar no [{% data variables.enterprise.management_console %}](/enterprise/admin/guides/installation/accessing-the-management-console). +With `ghe-set-password`, you can set a new password to authenticate into the [{% data variables.enterprise.management_console %}](/enterprise/admin/guides/installation/accessing-the-management-console). ```shell ghe-set-password @@ -348,31 +345,31 @@ ghe-set-password ### ghe-setup-network -Esse utilitário permite que você configure o adaptador de rede primário. +This utility allows you to configure the primary network interface. -Para inserir o modo visual, que orientará você nas configurações de rede: +To enter visual mode, which will guide you through configuration of network settings: ```shell $ ghe-setup-network -v ``` -Para consultar opções adicionais, use o sinalizador -h. +Use the -h flag for additional options. ### ghe-ssh-check-host-keys -Este utilitário verifica as chaves do host SSH atuais para identificar chaves vazadas conhecidas. +This utility checks the existing SSH host keys against the list of known leaked SSH host keys. ```shell $ ghe-ssh-check-host-keys ``` -Se for encontrada uma chave de host vazada, o utilitário sairá com o status `1` e a seguinte mensagem: +If a leaked host key is found the utility exits with status `1` and a message: ```shell > One or more of your SSH host keys were found in the blacklist. > Please reset your host keys using ghe-ssh-roll-host-keys. ``` -Se não forem encontradas chaves de host vazadas, o utilitário sairá com o status `0` e a seguinte mensagem: +If a leaked host key was not found, the utility exits with status `0` and a message: ```shell > The SSH host keys were not found in the SSH host key blacklist. > No additional steps are needed/recommended at this time. @@ -380,7 +377,7 @@ Se não forem encontradas chaves de host vazadas, o utilitário sairá com o sta ### ghe-ssh-roll-host-keys -Este utilitário acumula as chaves do host SSH e as substitui por chaves recém-geradas. +This utility rolls the SSH host keys and replaces them with newly generated keys. ```shell $ sudo ghe-ssh-roll-host-keys @@ -394,7 +391,7 @@ existing keys in /etc/ssh/ssh_host_* and generate new ones. [y/N] ### ghe-ssh-weak-fingerprints -Este utilitário retorna um relatório de chaves SSH fracas conhecidas armazenadas no appliance do {% data variables.product.prodname_enterprise %}. Você também pode revogar as chaves do usuário como uma ação em lote. O utilitário relatará as chaves fracas do sistema, que você precisará revogar manualmente no [{% data variables.enterprise.management_console %}](/enterprise/admin/guides/installation/accessing-the-management-console). +This utility returns a report of known weak SSH keys stored on the {% data variables.product.prodname_enterprise %} appliance. You can optionally revoke user keys as a bulk action. The utility will report weak system keys, which you must manually revoke in the [{% data variables.enterprise.management_console %}](/enterprise/admin/guides/installation/accessing-the-management-console). ```shell # Print a report of weak user and system SSH keys @@ -406,9 +403,9 @@ $ ghe-ssh-weak-fingerprints --revoke ### ghe-ssl-acme -Este utilitário permite instalar um certificado Let's Encrypt no seu appliance do {% data variables.product.prodname_enterprise %}. Para obter mais informações, confira "[Como configurar o TLS](/enterprise/admin/guides/installation/configuring-tls)". +This utility allows you to install a Let's Encrypt certificate on your {% data variables.product.prodname_enterprise %} appliance. For more information, see "[Configuring TLS](/enterprise/admin/guides/installation/configuring-tls)." -Use o sinalizador `-x` para remover a configuração ACME. +You can use the `-x` flag to remove the ACME configuration. ```shell ghe-ssl-acme -e @@ -416,11 +413,11 @@ ghe-ssl-acme -e ### ghe-ssl-ca-certificate-install -Este utilitário permite instalar um certificado CA personalizado de raiz no seu appliance do {% data variables.product.prodname_enterprise %}. O certificado deve estar no formato PEM. Além disso, se o provedor de certificado incluir vários certificados de AC em um só arquivo, você precisará separá-los em arquivos que serão transmitidos individualmente para `ghe-ssl-ca-certificate-install`. +This utility allows you to install a custom root CA certificate on your {% data variables.product.prodname_enterprise %} server. The certificate must be in PEM format. Furthermore, if your certificate provider includes multiple CA certificates in a single file, you must separate them into individual files that you then pass to `ghe-ssl-ca-certificate-install` one at a time. -Execute este utilitário para adicionar uma cadeia de certificados para verificação de assinatura de commits S/MIME. Para obter mais informações, confira "[Sobre a verificação de assinatura de commit](/enterprise/user/articles/about-commit-signature-verification/)". +Run this utility to add a certificate chain for S/MIME commit signature verification. For more information, see "[About commit signature verification](/enterprise/user/articles/about-commit-signature-verification/)." -Execute este utilitário quando a {% data variables.product.product_location %} não conseguir se conectar a outro servidor por estar usando um certificado SSL autoassinado ou um certificado SSL para o qual não há o pacote da AC necessário. Uma forma de confirmar isso é executar `openssl s_client -connect host:port -verify 0 -CApath /etc/ssl/certs` na {% data variables.product.product_location %}. Se o certificado SSL do servidor remoto puder ser verificado, a `SSL-Session` terá um código de retorno igual a 0, conforme mostrado abaixo. +Run this utility when {% data variables.location.product_location %} is unable to connect to another server because the latter is using a self-signed SSL certificate or an SSL certificate for which it doesn't provide the necessary CA bundle. One way to confirm this is to run `openssl s_client -connect host:port -verify 0 -CApath /etc/ssl/certs` from {% data variables.location.product_location %}. If the remote server's SSL certificate can be verified, your `SSL-Session` should have a return code of 0, as shown below. ``` SSL-Session: @@ -435,7 +432,7 @@ SSL-Session: Verify return code: 0 (ok) ``` -Por outro lado, se o certificado SSL do servidor remoto *não* puder ser verificado, a `SSL-Session` terá um código de retorno diferente de zero: +If, on the other hand, the remote server's SSL certificate can *not* be verified, your `SSL-Session` should have a nonzero return code: ``` SSL-Session: @@ -450,19 +447,19 @@ SSL-Session: Verify return code: 27 (certificate not trusted) ``` -É possível usar estas opções adicionais com o utilitário: -- O sinalizador `-r` permite desinstalar um Certificado de Autoridade de Certificação. -- O sinalizador `-h` exibe mais informações de uso. +You can use these additional options with the utility: +- The `-r` flag allows you to uninstall a CA certificate. +- The `-h` flag displays more usage information. ```shell -ghe-ssl-ca-certificate-install -c /path/to/certificate +ghe-ssl-ca-certificate-install -c CERTIFICATE_PATH ``` ### ghe-ssl-certificate-setup -Este utilitário permite atualizar um certificado SSL para {% data variables.product.product_location %}. +This utility allows you to update an SSL certificate for {% data variables.location.product_location %}. -Para saber mais sobre este comando ou ver opções adicionais, use o sinalizador `-h`. +For more information about this command or for additional options, use the `-h` flag. ```shell ghe-ssl-certificate-setup @@ -470,9 +467,9 @@ ghe-ssl-certificate-setup ### ghe-ssl-generate-csr -Com este utilitário, você pode gerar uma chave privada e uma solicitação de assinatura de certificado (CSR, Certificate Signing Request) a ser compartilhada com uma autoridade certificada comercial ou privada para obter um certificado válido na sua instância. Para obter mais informações, confira "[Como configurar o TLS](/enterprise/admin/guides/installation/configuring-tls)". +This utility allows you to generate a private key and certificate signing request (CSR), which you can share with a commercial or private certificate authority to get a valid certificate to use with your instance. For more information, see "[Configuring TLS](/enterprise/admin/guides/installation/configuring-tls)." -Para saber mais sobre este comando ou ver opções adicionais, use o sinalizador `-h`. +For more information about this command or for additional options, use the `-h` flag. ```shell ghe-ssl-generate-csr @@ -480,7 +477,7 @@ ghe-ssl-generate-csr ### ghe-storage-extend -Algumas plataformas exigem este script para aumentar o volume de usuários. Para obter mais informações, confira "[Como aumentar a capacidade de armazenamento](/enterprise/admin/guides/installation/increasing-storage-capacity/)". +Some platforms require this script to expand the user volume. For more information, see "[Increasing Storage Capacity](/enterprise/admin/guides/installation/increasing-storage-capacity/)". ```shell $ ghe-storage-extend @@ -488,7 +485,7 @@ $ ghe-storage-extend ### ghe-version -Este utilitário imprime a versão, a plataforma e a compilação de {% data variables.product.product_location %}. +This utility prints the version, platform, and build of {% data variables.location.product_location %}. ```shell $ ghe-version @@ -496,31 +493,33 @@ $ ghe-version ### ghe-webhook-logs -Este utilitário retorna logs de entrega de webhook para os administradores revisarem e identificarem problemas. +This utility returns webhook delivery logs for administrators to review and identify any issues. ```shell ghe-webhook-logs ``` -Para mostrar todas as entregas de gancho com falha no último dia: {% ifversion ghes %} +To show all failed hook deliveries in the past day: +{% ifversion ghes %} ```shell -ghe-webhook-logs -f -a YYYY-MM-DD +ghe-webhook-logs -f -a YYYY-MM-DD ``` -O formato de data deve ser `YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` ou `YYYY-MM-DD HH:MM:SS (+/-) HH:M`. +The date format should be `YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS`, or `YYYY-MM-DD HH:MM:SS (+/-) HH:M`. {% else %} ```shell -ghe-webhook-logs -f -a YYYYMMDD +ghe-webhook-logs -f -a YYYYMMDD ``` {% endif %} -Para mostrar a carga total do gancho, o resultado e as exceções da entrega: {% ifversion ghes %} +To show the full hook payload, result, and any exceptions for the delivery: +{% ifversion ghes %} ```shell -ghe-webhook-logs -g delivery-guid +ghe-webhook-logs -g DELIVERY_GUID ``` {% else %} ```shell -ghe-webhook-logs -g delivery-guid -v +ghe-webhook-logs -g DELIVERY_GUID -v ``` {% endif %} @@ -528,7 +527,7 @@ ghe-webhook-logs -g delivery-guid -v ### ghe-cluster-status -Verifique a saúde dos seus nós e serviços em uma implantação de clustering de {% data variables.product.prodname_ghe_server %}. +Check the health of your nodes and services in a cluster deployment of {% data variables.product.prodname_ghe_server %}. ```shell $ ghe-cluster-status @@ -536,34 +535,34 @@ $ ghe-cluster-status ### ghe-cluster-support-bundle -Este utilitário cria um pacote de suporte tarball com logs importantes de cada nó em configurações de replicação geográfica ou de cluster. +This utility creates a support bundle tarball containing important logs from each of the nodes in either a Geo-replication or Clustering configuration. -Por padrão, o comando cria o tarball em */tmp*, mas você também pode executar `cat` no tarball para `STDOUT` a fim de facilitar o streaming via SSH. Isso é útil caso a interface da Web não responda ou caso o download de um pacote de suporte de */setup/support* não funcione. Você precisa usar este comando caso deseje gerar um pacote *estendido*, contendo logs mais antigos. Também é possível usá-lo para fazer upload do pacote de suporte de cluster diretamente para o suporte do {% data variables.product.prodname_enterprise %}. +By default, the command creates the tarball in */tmp*, but you can also have it `cat` the tarball to `STDOUT` for easy streaming over SSH. This is helpful in the case where the web UI is unresponsive or downloading a support bundle from */setup/support* doesn't work. You must use this command if you want to generate an *extended* bundle, containing older logs. You can also use this command to upload the cluster support bundle directly to {% data variables.product.prodname_enterprise %} support. -Para criar um pacote padrão: +To create a standard bundle: ```shell -$ ssh -p 122 admin@hostname -- 'ghe-cluster-support-bundle -o' > cluster-support-bundle.tgz +$ ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -o' > cluster-support-bundle.tgz ``` -Para criar um pacote estendido: +To create an extended bundle: ```shell -$ ssh -p 122 admin@hostname -- 'ghe-cluster-support-bundle -x -o' > cluster-support-bundle.tgz +$ ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -x -o' > cluster-support-bundle.tgz ``` -Para enviar um pacote para {% data variables.contact.github_support %}: +To send a bundle to {% data variables.contact.github_support %}: ```shell -$ ssh -p 122 admin@hostname -- 'ghe-cluster-support-bundle -u' +$ ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -u' ``` -Para enviar um pacote para {% data variables.contact.github_support %} e associar o pacote a um tíquete: +To send a bundle to {% data variables.contact.github_support %} and associate the bundle with a ticket: ```shell -$ ssh -p 122 admin@hostname -- 'ghe-cluster-support-bundle -t ticket-id' +$ ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -t TICKET_ID' ``` {% ifversion ghes %} ### ghe-cluster-failover -Falha ao sair de nós de cluster ativos para nós de cluster passivo. Para obter mais informações, confira "[Como iniciar um failover no cluster de réplica](/enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster)". +Fail over from active cluster nodes to passive cluster nodes. For more information, see "[Initiating a failover to your replica cluster](/enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster)." ```shell ghe-cluster-failover @@ -572,61 +571,61 @@ ghe-cluster-failover ### ghe-dpages -Este utilitário permite que você gerencie o servidor distribuído {% data variables.product.prodname_pages %}. +This utility allows you to manage the distributed {% data variables.product.prodname_pages %} server. ```shell ghe-dpages ``` -Para mostrar um resumo da localização e saúde do repositório: +To show a summary of repository location and health: ```shell ghe-dpages status ``` -Para evacuar um serviço de armazenamento {% data variables.product.prodname_pages %} antes de evacuar um nó de cluster: +To evacuate a {% data variables.product.prodname_pages %} storage service before evacuating a cluster node: ```shell -ghe-dpages evacuate pages-server-UUID +ghe-dpages evacuate pages-server-UUID ``` ### ghe-spokes -Este utilitário permite gerenciar as três cópias de cada repositório nos servidores distribuídos do git. +This utility allows you to manage the three copies of each repository on the distributed git servers. ```shell ghe-spokes ``` -Para mostrar um resumo da localização e saúde do repositório: +To show a summary of repository location and health: ```shell ghe-spokes status ``` -Para mostrar os servidores em que o repositório está armazenado: +To show the servers in which the repository is stored: ```shell ghe-spokes route ``` -Para evacuar os serviços de armazenamento em um nó de cluster: +To evacuate storage services on a cluster node: ```shell -ghe-spokes server evacuate git-server-UUID +ghe-spokes server evacuate git-server-UUID ``` ### ghe-storage -Este utilitário permite remover todos os serviços de armazenamento antes de remover um nó de cluster. +This utility allows you to evacuate all storage services before evacuating a cluster node. ```shell -ghe-storage evacuate storage-server-UUID +ghe-storage evacuate storage-server-UUID ``` ## Git ### ghe-btop -Uma interface do tipo `top` para as operações atuais do Git. +A `top`-like interface for current Git operations. ```shell ghe-btop [ | --help | --usage ] @@ -634,7 +633,7 @@ ghe-btop [ | --help | --usage ] #### ghe-governor -Este utilitário ajuda a analisar o tráfego do Git. Ele consulta arquivos de dados do _Governor_, localizados em `/data/user/gitmon`. {% data variables.product.company_short %} mantém uma hora de dados por arquivo, retidos por duas semanas. Para obter mais informações, confira [Como analisar o tráfego do Git usando o Governor](https://github.community/t/analyzing-git-traffic-using-governor/13516) no {% data variables.product.prodname_github_community %}. +This utility helps to analyze Git traffic. It queries _Governor_ data files, located under `/data/user/gitmon`. {% data variables.product.company_short %} holds one hour of data per file, retained for two weeks. For more information, see [Analyzing Git traffic using Governor](https://github.community/t/analyzing-git-traffic-using-governor/13516) in {% data variables.product.prodname_github_community %}. ```bash ghe-governor [options] @@ -659,33 +658,33 @@ Try ghe-governor --help for more information on the arguments each ### ghe-repo -Este utilitário permite alterar para o diretório de um repositório e abrir um shell interativo como o usuário do `git`. Você pode fazer a inspeção ou a manutenção manual de um repositório usando comandos como `git-*` ou `git-nw-*`. +This utility allows you to change to a repository's directory and open an interactive shell as the `git` user. You can perform manual inspection or maintenance of a repository via commands like `git-*` or `git-nw-*`. ```shell -ghe-repo username/reponame +ghe-repo USERNAME/REPONAME ``` ### ghe-repo-gc -Este utilitário reempacota manualmente uma rede de repositórios para otimizar o armazenamento do pacote. Se você tem um repositório muito grande, esse comando pode ajudar a reduzir o tamanho. O {% data variables.product.prodname_enterprise %} executa automaticamente este comando durante toda a sua interação com uma rede de repositórios. +This utility manually repackages a repository network to optimize pack storage. If you have a large repository, running this command may help reduce its overall size. {% data variables.product.prodname_enterprise %} automatically runs this command throughout your interaction with a repository network. -Adicione o argumento opcional `--prune` para remover objetos do Git inacessíveis que não são referenciados em um branch, uma marca ou em nenhuma outra referência. Isso é particularmente útil para remover de imediato as [informações confidenciais já eliminadas](/enterprise/user/articles/remove-sensitive-data/). +You can add the optional `--prune` argument to remove unreachable Git objects that aren't referenced from a branch, tag, or any other ref. This is particularly useful for immediately removing [previously expunged sensitive information](/enterprise/user/articles/remove-sensitive-data/). {% warning %} -**Aviso**: para usar o argumento `--prune` para remover objetos Git inacessíveis, coloque o {% data variables.product.product_location %} no modo de manutenção ou verifique se todos os repositórios da mesma rede de repositórios estão bloqueados. Para obter mais informações, confira "[Como habilitar e agendar o modo de manutenção](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)". +**Warning**: Before using the `--prune` argument to remove unreachable Git objects, put {% data variables.location.product_location %} into maintenance mode, or ensure all repositories within the same repository network are locked. For more information, see "[Enabling and scheduling maintenance mode](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)." {% endwarning %} ```shell -ghe-repo-gc username/reponame +ghe-repo-gc USERNAME/REPONAME ``` ## {% data variables.product.prodname_actions %} ### ghe-actions-check -Este utilitário verifica se todos os serviços para {% data variables.product.prodname_actions %} são saudáveis. Para obter mais informações, confira "[Introdução ao {% data variables.product.prodname_actions %} para {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server)" e "[Solução de problemas do {% data variables.product.prodname_actions %} para sua empresa](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise)". +This utility checks that all services for {% data variables.product.prodname_actions %} are healthy. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server)" and "[Troubleshooting {% data variables.product.prodname_actions %} for your enterprise](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise)." ```shell ghe-actions-check @@ -693,70 +692,70 @@ ghe-actions-check ### ghe-actions-precheck -Este utilitário testa a configuração de armazenamento do blob para {% data variables.product.prodname_actions %} em {% data variables.product.product_location %}. Você pode usar o utilitário para verificar sua configuração de armazenamento antes de habilitar o {% data variables.product.prodname_actions %} para sua instância. +This utility tests the blob storage configuration for {% data variables.product.prodname_actions %} on {% data variables.location.product_location %}. You can use the utility to verify your storage configuration before you enable {% data variables.product.prodname_actions %} for your instance. -Para obter mais informações sobre a configuração do {% data variables.product.prodname_actions %}, confira "[Introdução ao {% data variables.product.prodname_actions %} para {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server)". +For more information about the configuration of {% data variables.product.prodname_actions %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server)." ```shell -ghe-actions-precheck -p [provider] -cs ["connectionstring"] +ghe-actions-precheck -p [PROVIDER] -cs ["CONNECTION-STRING"] ``` -Se o sistema de armazenamento estiver configurado corretamente, você verá a seguinte saída. +If your storage system is configured correctly, you'll see the following output. ``` All Storage tests passed ``` -## Importação e exportação +## Import and export ### ghe-migrator -O `ghe-migrator` é uma ferramenta de alta fidelidade que ajuda a fazer migrações de uma instância do GitHub para outra. Você pode consolidar suas instâncias ou mover a organização, os usuários, as equipes e os repositórios do GitHub.com para o {% data variables.product.prodname_enterprise %}. +`ghe-migrator` is a hi-fidelity tool to help you migrate from one GitHub instance to another. You can consolidate your instances or move your organization, users, teams, and repositories from GitHub.com to {% data variables.product.prodname_enterprise %}. -Para obter mais informações, confira nossos guias sobre [como migrar dados na sua empresa](/enterprise/admin/user-management/migrating-data-to-and-from-your-enterprise/). +For more information, please see our guides on [migrating data to and from your enterprise](/enterprise/admin/user-management/migrating-data-to-and-from-your-enterprise/). ### git-import-detect -Em uma URL, detecta qual tipo de sistema de gerenciamento de controle de origem está na outra extremidade. Provavelmente esse processo já é conhecido nas importações manuais, mas pode ser muito útil em scripts automatizados. +Given a URL, detect which type of source control management system is at the other end. During a manual import this is likely already known, but this can be very useful in automated scripts. ```shell git-import-detect ``` ### git-import-hg-raw -Este utilitário importa um repositório Mercurial para este repositório Git. Para obter mais informações, confira "[Como importar dados de sistemas de controle de versão de terceiros](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)". +This utility imports a Mercurial repository to this Git repository. For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)." ```shell git-import-hg-raw ``` ### git-import-svn-raw -Este utilitário importa histórico do Subversion e dados de arquivos para um branch do Git. Trata-se de uma cópia direta da árvore, ignorando qualquer distinção de trunk ou branch. Para obter mais informações, confira "[Como importar dados de sistemas de controle de versão de terceiros](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)". +This utility imports Subversion history and file data into a Git branch. This is a straight copy of the tree, ignoring any trunk or branch distinction. For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)." ```shell git-import-svn-raw ``` ### git-import-tfs-raw -Este utilitário faz a importação a partir do Controle de Versão da Fundação da Equipe (TFVC). Para obter mais informações, confira "[Como importar dados de sistemas de controle de versão de terceiros](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)". +This utility imports from Team Foundation Version Control (TFVC). For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)." ```shell git-import-tfs-raw ``` ### git-import-rewrite -Este utilitário reescreve o repositório importado. Isso dá a você a oportunidade de renomear autores e, para o Subversion e TFVC, produz branches Git baseados em pastas. Para obter mais informações, confira "[Como importar dados de sistemas de controle de versão de terceiros](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)". +This utility rewrites the imported repository. This gives you a chance to rename authors and, for Subversion and TFVC, produces Git branches based on folders. For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)." ```shell git-import-rewrite ``` {% ifversion ghes > 3.3 %} -## Segurança +## Security ### ghe-find-insecure-git-operations -Esse utilitário pesquisa os logs da instância e identifica as operações do Git por SSH que usam algoritmos inseguros ou funções de hash, incluindo criptografias DSA, RSA-SHA-1, HMAC-SHA-1 e CBC. Você pode usar a saída para dar suporte à transição de cada cliente para uma conexão SSH mais segura. Para obter mais informações, confira [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server){% ifversion ghes < 3.6 %}.{% elsif ghes > 3.5 %} e "[Como configurar conexões SSH cmo a sua instância](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)."{% endif %} +This utility searches your instance's logs and identifies Git operations over SSH that use insecure algorithms or hash functions, including DSA, RSA-SHA-1, HMAC-SHA-1, and CBC ciphers. You can use the output to support each client's transition to a more secure SSH connection. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server){% ifversion ghes < 3.6 %}.{% elsif ghes > 3.5 %} and "[Configuring SSH connections to your instance](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)."{% endif %} ```shell ghe-find-insecure-git-operations @@ -764,13 +763,13 @@ ghe-find-insecure-git-operations {% endif %} -## Suporte +## Support ### ghe-diagnostics -Este utilitário faz uma série de verificações e reúne informações sobre a instalação que você pode enviar ao suporte para ajudar a diagnosticar problemas. +This utility performs a variety of checks and gathers information about your installation that you can send to support to help diagnose problems you're having. -No momento, a saída do utilitário é semelhante ao download das informações de diagnóstico no {% data variables.enterprise.management_console %}, mas ele pode ter melhorias adicionais ao longo do tempo que não estão disponíveis na interface da web. Para obter mais informações, confira "[Como criar e compartilhar arquivos de diagnóstico](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-diagnostic-files)". +Currently, this utility's output is similar to downloading the diagnostics info in the {% data variables.enterprise.management_console %}, but may have additional improvements added to it over time that aren't available in the web UI. For more information, see "[Creating and sharing diagnostic files](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-diagnostic-files)." ```shell ghe-diagnostics @@ -778,104 +777,105 @@ ghe-diagnostics ### ghe-support-bundle -{% data reusables.enterprise_enterprise_support.use_ghe_cluster_support_bundle %} Este utilitário cria um pacote de suporte tarball com logs importantes da sua instância. +{% data reusables.enterprise_enterprise_support.use_ghe_cluster_support_bundle %} +This utility creates a support bundle tarball containing important logs from your instance. -Por padrão, o comando cria o tarball em */tmp*, mas você também pode executar `cat` no tarball para `STDOUT` a fim de facilitar o streaming via SSH. Isso é útil caso a interface da Web não responda ou caso o download de um pacote de suporte de */setup/support* não funcione. Você precisa usar este comando caso deseje gerar um pacote *estendido*, contendo logs mais antigos. Também é possível usá-lo para fazer upload do pacote de suporte diretamente para o suporte do {% data variables.product.prodname_enterprise %}. +By default, the command creates the tarball in */tmp*, but you can also have it `cat` the tarball to `STDOUT` for easy streaming over SSH. This is helpful in the case where the web UI is unresponsive or downloading a support bundle from */setup/support* doesn't work. You must use this command if you want to generate an *extended* bundle, containing older logs. You can also use this command to upload the support bundle directly to {% data variables.product.prodname_enterprise %} support. -Para criar um pacote padrão: +To create a standard bundle: ```shell -$ ssh -p 122 admin@hostname -- 'ghe-support-bundle -o' > support-bundle.tgz +$ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -o' > support-bundle.tgz ``` -Para criar um pacote estendido: +To create an extended bundle: ```shell -$ ssh -p 122 admin@hostname -- 'ghe-support-bundle -x -o' > support-bundle.tgz +$ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -x -o' > support-bundle.tgz ``` -Para enviar um pacote para {% data variables.contact.github_support %}: +To send a bundle to {% data variables.contact.github_support %}: ```shell -$ ssh -p 122 admin@hostname -- 'ghe-support-bundle -u' +$ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -u' ``` -Para enviar um pacote para {% data variables.contact.github_support %} e associar o pacote a um tíquete: +To send a bundle to {% data variables.contact.github_support %} and associate the bundle with a ticket: ```shell -$ ssh -p 122 admin@hostname -- 'ghe-support-bundle -t ticket-id' +$ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -t TICKET_ID' ``` ### ghe-support-upload -Este utilitário envia informações do seu appliance para o suporte do {% data variables.product.prodname_enterprise %}. Você pode especificar um arquivo local ou fornecer um fluxo de até 100 MB de dados por meio de `STDIN`. Os dados carregados também podem ser associados a um tíquete de suporte. +This utility sends information from your appliance to {% data variables.product.prodname_enterprise %} support. You can either specify a local file, or provide a stream of up to 100MB of data via `STDIN`. The uploaded data can optionally be associated with a support ticket. -Para enviar um arquivo para {% data variables.contact.github_support %} e associar o arquivo a um tíquete: +To send a file to {% data variables.contact.github_support %} and associate the file with a ticket: ```shell -ghe-support-upload -f path/to/your/file -t ticket-id +ghe-support-upload -f FILE_PATH -t TICKET_ID ``` -Para carregar dados por meio de `STDIN` e associá-los a um tíquete: +To upload data via `STDIN` and associating the data with a ticket: ```shell -ghe-repl-status -vv | ghe-support-upload -t ticket-id -d "Verbose Replication Status" +ghe-repl-status -vv | ghe-support-upload -t TICKET_ID -d "Verbose Replication Status" ``` -Neste exemplo, `ghe-repl-status -vv` envia informações de status detalhadas em um dispositivo de réplica. Substitua `ghe-repl-status -vv` pelos dados específicos que deseja transmitir para `STDIN` e `Verbose Replication Status` por uma breve descrição dos dados. {% data reusables.enterprise_enterprise_support.support_will_ask_you_to_run_command %} +In this example, `ghe-repl-status -vv` sends verbose status information from a replica appliance. You should replace `ghe-repl-status -vv` with the specific data you'd like to stream to `STDIN`, and `Verbose Replication Status` with a brief description of the data. {% data reusables.enterprise_enterprise_support.support_will_ask_you_to_run_command %} -## Atualização do {% data variables.product.prodname_ghe_server %} +## Upgrading {% data variables.product.prodname_ghe_server %} ### ghe-upgrade -Este utilitário instala ou verifica um pacote de atualização. Também é possível usá-lo para voltar a uma versão de patch em casos de falha ou interrupção de uma atualização. Para obter mais informações, confira "[Como atualizar o {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)". +This utility installs or verifies an upgrade package. You can also use this utility to roll back a patch release if an upgrade fails or is interrupted. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)." -Para verificar um pacote de atualização: +To verify an upgrade package: ```shell -ghe-upgrade --verify UPGRADE-PACKAGE-FILENAME +ghe-upgrade --verify UPGRADE-PACKAGE-FILENAME ``` -Para instalar um pacote de atualização: +To install an upgrade package: ```shell -ghe-upgrade UPGRADE-PACKAGE-FILENAME +ghe-upgrade UPGRADE-PACKAGE-FILENAME ``` {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %} ### ghe-upgrade-scheduler -Este utilitário gerencia a instalação programada de pacotes de atualização. Você pode exibir, criar ou remover instalações programadas. Crie as programações usando expressões cron. Para obter mais informações, confira a [entrada do Cron na Wikipédia](https://en.wikipedia.org/wiki/Cron#Overview). +This utility manages scheduled installation of upgrade packages. You can show, create new, or remove scheduled installations. You must create schedules using cron expressions. For more information, see the [Cron Wikipedia entry](https://en.wikipedia.org/wiki/Cron#Overview). -Para agendar uma nova instalação para um pacote: +To schedule a new installation for a package: ```shell -$ ghe-upgrade-scheduler -c "0 2 15 12 *" UPGRADE-PACKAGE-FILENAME +$ ghe-upgrade-scheduler -c "0 2 15 12 *" UPGRADE-PACKAGE-FILENAME ``` -Para exibir instalações programadas para um pacote: +To show scheduled installations for a package: ```shell -$ ghe-upgrade-scheduler -s UPGRADE PACKAGE FILENAME -> 0 2 15 12 * /usr/local/bin/ghe-upgrade -y -s UPGRADE-PACKAGE-FILENAME > /data/user/common/UPGRADE-PACKAGE-FILENAME.log 2>&1 +$ ghe-upgrade-scheduler -s UPGRADE PACKAGE FILENAME +> 0 2 15 12 * /usr/local/bin/ghe-upgrade -y -s UPGRADE-PACKAGE-FILENAME > /data/user/common/UPGRADE-PACKAGE-FILENAME.log 2>&1 ``` -Para remover instalações programadas para um pacote: +To remove scheduled installations for a package: ```shell -$ ghe-upgrade-scheduler -r UPGRADE PACKAGE FILENAME +$ ghe-upgrade-scheduler -r UPGRADE PACKAGE FILENAME ``` ### ghe-update-check -Este utilitário verificará se uma nova versão do patch do {% data variables.product.prodname_enterprise %} está disponível. Se estiver e se houver espaço disponível na sua instância, ele baixará o pacote. Por padrão, ele é salvo em */var/lib/ghe-updates*. Em seguida, um administrador pode [executar a atualização](/enterprise/admin/guides/installation/updating-the-virtual-machine-and-physical-resources/). +This utility will check to see if a new patch release of {% data variables.product.prodname_enterprise %} is available. If it is, and if space is available on your instance, it will download the package. By default, it's saved to */var/lib/ghe-updates*. An administrator can then [perform the upgrade](/enterprise/admin/guides/installation/updating-the-virtual-machine-and-physical-resources/). -Um arquivo contendo o status do download fica disponível em */var/lib/ghe-updates/ghe-update-check.status*. +A file containing the status of the download is available at */var/lib/ghe-updates/ghe-update-check.status*. -Para verificar a última versão do {% data variables.product.prodname_enterprise %}, use a opção `-i`. +To check for the latest {% data variables.product.prodname_enterprise %} release, use the `-i` switch. ```shell -$ ssh -p 122 admin@hostname -- 'ghe-update-check' +$ ssh -p 122 admin@HOSTNAME -- 'ghe-update-check' ``` -## Gerenciamento de Usuários +## User management ### ghe-license-usage -Este utilitário exporta uma lista de usuários da instalação em formato JSON. Se sua instância estiver conectada ao {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} usa essa informação para reportar informações de licenciamento ao {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, confira "[Como conectar sua conta corporativa ao {% data variables.product.prodname_ghe_cloud %} ](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)". +This utility exports a list of the installation's users in JSON format. If your instance is connected to {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} uses this information for reporting licensing information to {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %} ](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." -Por padrão, a lista de usuários no arquivo JSON resultante é criptografada. Use o sinalizador `-h` para ver mais opções. +By default, the list of users in the resulting JSON file is encrypted. Use the `-h` flag for more options. ```shell ghe-license-usage @@ -883,15 +883,15 @@ ghe-license-usage ### ghe-org-membership-update -Este utilitário aplicará a configuração padrão de visibilidade da associação da organização a todos os integrantes da sua instância. Para obter mais informações, confira "[Como configurar a visibilidade da associação à organização](/enterprise/admin/guides/user-management/configuring-visibility-for-organization-membership)". As opções de configuração são `public` ou `private`. +This utility will enforce the default organization membership visibility setting on all members in your instance. For more information, see "[Configuring visibility for organization membership](/enterprise/admin/guides/user-management/configuring-visibility-for-organization-membership)." Setting options are `public` or `private`. ```shell -ghe-org-membership-update --visibility=SETTING +ghe-org-membership-update --visibility=SETTING ``` ### `ghe-user-csv` -Este utilitário exporta uma lista de todos os usuários na instalação em formato CSV. O arquivo CSV inclui o endereço de email, o tipo de usuário (por exemplo, administrador, usuário), a quantidade de repositórios, chaves SSH e associações a uma organização, o último endereço IP registrado etc. Use o sinalizador `-h` para ver mais opções. +This utility exports a list of all the users in the installation into CSV format. The CSV file includes the email address, which type of user they are (e.g., admin, user), how many repositories they have, how many SSH keys, how many organization memberships, last logged IP address, etc. Use the `-h` flag for more options. ```shell ghe-user-csv -o > users.csv @@ -899,32 +899,32 @@ ghe-user-csv -o > users.csv ### ghe-user-demote -Este utilitário rebaixa o usuário especificado do status de administrador para o status de usuário regular. Recomendamos usar a interface do usuário da Web para executar esta ação, mas forneça esse utilitário em caso de erro na execução do utilitário `ghe-user-promote` e se você precisar rebaixar um usuário novamente por meio da CLI. +This utility demotes the specified user from admin status to that of a regular user. We recommend using the web UI to perform this action, but provide this utility in case the `ghe-user-promote` utility is run in error and you need to demote a user again from the CLI. ```shell -ghe-user-demote some-user-name +ghe-user-demote USERNAME ``` ### ghe-user-promote -Este utilitário promove a conta de usuário especificada a administrador do site. +This utility promotes the specified user account to a site administrator. ```shell -ghe-user-promote some-user-name +ghe-user-promote USERNAME ``` ### ghe-user-suspend -Este utilitário suspende o usuário especificado, impedindo-o de fazer login, push ou pull nos seus repositórios. +This utility suspends the specified user, preventing them from logging in, pushing, or pulling from your repositories. ```shell -ghe-user-suspend some-user-name +ghe-user-suspend USERNAME ``` ### ghe-user-unsuspend -Este utilitário cancela a suspensão do usuário especificado, liberando o acesso para fazer login, push ou pull nos seus repositórios. +This utility unsuspends the specified user, granting them access to login, push, and pull from your repositories. ```shell -ghe-user-unsuspend some-user-name +ghe-user-unsuspend USERNAME ``` diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-applications.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-applications.md index 6ee966c63d..07a9b2af5d 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-applications.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-applications.md @@ -1,6 +1,6 @@ --- -title: Configurando aplicativos -intro: 'É possível definir as configurações de aplicativos internos para o {% data variables.product.product_location %}.' +title: Configuring applications +intro: 'You can configure internal application settings for {% data variables.location.product_location %}.' redirect_from: - /enterprise/admin/installation/configuring-applications - /enterprise/admin/configuration/configuring-applications @@ -11,19 +11,15 @@ type: how_to topics: - Enterprise - Fundamentals -ms.openlocfilehash: bcc51bdabb5dc0b5ecdd4f77db9246a60c8df496 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145095980' --- -## Ajustar cache de imagem +## Adjusting image caching -Você pode escolher por quanto tempo a {% data variables.product.product_location %} armazena avatares em cache. Ao aumentar o tempo do cache, você aumenta o tempo que o avatar do usuário levará para carregar. Configurar o tempo de cache com um valor muito baixo pode sobrecarregar os processos de trabalho da {% data variables.product.product_location %}. +You can choose the amount of time that {% data variables.location.product_location %} caches avatars. When you increase the cache time, you increase the amount of time a user's avatar will take to load. Configuring the cache time with too low a value can overload {% data variables.location.product_location %} work processes. -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} -3. Na barra lateral esquerda, clique em **Aplicativos**. -![Guia Applications (Aplicativos) na barra lateral Settings (Configurações)](/assets/images/enterprise/management-console/sidebar-applications.png) -4. Em "Avatar image cache time (seconds)" (Tempo de cache para imagem do avatar [segundos]), digite por quantos segundos você gostaria que a {% data variables.product.product_location %} armazenasse as imagens do avatar em cache. -![Campo de formulário de cache de imagem de avatar](/assets/images/enterprise/management-console/add-image-caching-value-field.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +3. In the left sidebar, click **Applications**. +![Applications tab in the settings sidebar](/assets/images/enterprise/management-console/sidebar-applications.png) +4. Under "Avatar image cache time (seconds)", type the number of seconds that you would like {% data variables.location.product_location %} to cache avatar images. +![Avatar image caching form field](/assets/images/enterprise/management-console/add-image-caching-value-field.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md index 82d3255404..a8fecf4017 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md @@ -14,7 +14,7 @@ redirect_from: - /enterprise/admin/installation/configuring-backups-on-your-appliance - /enterprise/admin/configuration/configuring-backups-on-your-appliance - /admin/configuration/configuring-backups-on-your-appliance -intro: 'As part of a disaster recovery plan, you can protect production data on {% data variables.product.product_location %} by configuring automated backups.' +intro: 'As part of a disaster recovery plan, you can protect production data on {% data variables.location.product_location %} by configuring automated backups.' versions: ghes: '*' type: how_to @@ -26,7 +26,7 @@ topics: --- ## About {% data variables.product.prodname_enterprise_backup_utilities %} -{% data variables.product.prodname_enterprise_backup_utilities %} is a backup system you install on a separate host, which takes backup snapshots of {% data variables.product.product_location %} at regular intervals over a secure SSH network connection. You can use a snapshot to restore an existing {% data variables.product.prodname_ghe_server %} instance to a previous state from the backup host. +{% data variables.product.prodname_enterprise_backup_utilities %} is a backup system you install on a separate host, which takes backup snapshots of {% data variables.location.product_location %} at regular intervals over a secure SSH network connection. You can use a snapshot to restore an existing {% data variables.product.prodname_ghe_server %} instance to a previous state from the backup host. Only data added since the last snapshot will transfer over the network and occupy additional physical storage space. To minimize performance impact, backups are performed online under the lowest CPU/IO priority. You do not need to schedule a maintenance window to perform a backup. @@ -36,11 +36,11 @@ For more detailed information on features, requirements, and advanced usage, see ## Prerequisites -To use {% data variables.product.prodname_enterprise_backup_utilities %}, you must have a Linux or Unix host system separate from {% data variables.product.product_location %}. +To use {% data variables.product.prodname_enterprise_backup_utilities %}, you must have a Linux or Unix host system separate from {% data variables.location.product_location %}. You can also integrate {% data variables.product.prodname_enterprise_backup_utilities %} into an existing environment for long-term permanent storage of critical data. -We recommend that the backup host and {% data variables.product.product_location %} be geographically distant from each other. This ensures that backups are available for recovery in the event of a major disaster or network outage at the primary site. +We recommend that the backup host and {% data variables.location.product_location %} be geographically distant from each other. This ensures that backups are available for recovery in the event of a major disaster or network outage at the primary site. Physical storage requirements will vary based on Git repository disk usage and expected growth patterns: @@ -89,14 +89,14 @@ Backup snapshots are written to the disk path set by the `GHE_DATA_DIR` data dir {% note %} - **Note:** If {% data variables.product.product_location %} is deployed as a cluster or in a high availability configuration using a load balancer, the `GHE_HOSTNAME` can be the load balancer hostname, as long as it allows SSH access (on port 122) to {% data variables.product.product_location %}. + **Note:** If {% data variables.location.product_location %} is deployed as a cluster or in a high availability configuration using a load balancer, the `GHE_HOSTNAME` can be the load balancer hostname, as long as it allows SSH access (on port 122) to {% data variables.location.product_location %}. To ensure a recovered appliance is immediately available, perform backups targeting the primary instance even in a geo-replication configuration. {% endnote %} 1. Set the `GHE_DATA_DIR` value to the filesystem location where you want to store backup snapshots. We recommend choosing a location on the same filesystem as your backup host, but outside of where you cloned the Git repository in step 1. 1. To grant your backup host access to your instance, open your primary instance's settings page at `http(s)://HOSTNAME/setup/settings` and add the backup host's SSH key to the list of authorized SSH keys. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh#enabling-access-to-the-administrative-shell-via-ssh)." -1. On your backup host, verify SSH connectivity with {% data variables.product.product_location %} with the `ghe-host-check` command. +1. On your backup host, verify SSH connectivity with {% data variables.location.product_location %} with the `ghe-host-check` command. ```shell ./bin/ghe-host-check @@ -111,7 +111,7 @@ For more information on advanced usage, see the [{% data variables.product.prodn ## Upgrading {% data variables.product.prodname_enterprise_backup_utilities %} -When upgrading {% data variables.product.prodname_enterprise_backup_utilities %}, you must choose a release that will work with your current version of {% data variables.product.product_name %}. Your installation of {% data variables.product.prodname_enterprise_backup_utilities %} must be at least the same version as {% data variables.product.product_location %}, and cannot be more than two versions ahead. For more information, see [{% data variables.product.prodname_ghe_server %} version requirements](https://github.com/github/backup-utils/blob/master/docs/requirements.md#github-enterprise-server-version-requirements) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation. +When upgrading {% data variables.product.prodname_enterprise_backup_utilities %}, you must choose a release that will work with your current version of {% data variables.product.product_name %}. Your installation of {% data variables.product.prodname_enterprise_backup_utilities %} must be at least the same version as {% data variables.location.product_location %}, and cannot be more than two versions ahead. For more information, see [{% data variables.product.prodname_ghe_server %} version requirements](https://github.com/github/backup-utils/blob/master/docs/requirements.md#github-enterprise-server-version-requirements) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation. You can upgrade {% data variables.product.prodname_enterprise_backup_utilities %} in a Git repository by fetching and checking out the latest changes. Alternatively, if you don't use a Git repository for your installation, you can extract a new archive into place, or you can change your approach to use a Git repository instead. @@ -198,24 +198,24 @@ If backup attempts overlap, the `ghe-backup` command will abort with an error me ## Restoring a backup -In the event of prolonged outage or catastrophic event at the primary site, you can restore {% data variables.product.product_location %} by provisioning another {% data variables.product.prodname_enterprise %} appliance and performing a restore from the backup host. You must add the backup host's SSH key to the target {% data variables.product.prodname_enterprise %} appliance as an authorized SSH key before restoring an appliance. +In the event of prolonged outage or catastrophic event at the primary site, you can restore {% data variables.location.product_location %} by provisioning another {% data variables.product.prodname_enterprise %} appliance and performing a restore from the backup host. You must add the backup host's SSH key to the target {% data variables.product.prodname_enterprise %} appliance as an authorized SSH key before restoring an appliance. {% note %} -**Note:** When performing backup restores to {% data variables.product.product_location %}, the same version supportability rules apply. You can only restore data from at most two feature releases behind. +**Note:** When performing backup restores to {% data variables.location.product_location %}, the same version supportability rules apply. You can only restore data from at most two feature releases behind. For example, if you take a backup from {% data variables.product.product_name %} 3.0.x, you can restore the backup to a {% data variables.product.product_name %} 3.2.x instance. You cannot restore data from a backup of {% data variables.product.product_name %} 2.22.x to an instance running 3.2.x, because that would be three jumps between versions (2.22 to 3.0 to 3.1 to 3.2). You would first need to restore to an instance running 3.1.x, and then upgrade to 3.2.x. {% endnote %} -To restore {% data variables.product.product_location %} from the last successful snapshot, use the `ghe-restore` command. +To restore {% data variables.location.product_location %} from the last successful snapshot, use the `ghe-restore` command. {% note %} **Note:** Prior to restoring a backup, ensure: - Maintenance mode is enabled on the primary instance and all active processes have completed. For more information, see "[Enabling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)." - Replication is stopped on all replicas in high availability configurations. For more information, see the `ghe-repl-stop` command in "[About high availability configuration](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration#ghe-repl-stop)." -- If {% data variables.product.product_location %} has {% data variables.product.prodname_actions %} enabled, you must first configure the {% data variables.product.prodname_actions %} external storage provider on the replacement appliance. For more information, see "[Backing up and restoring {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %} enabled](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)." +- If {% data variables.location.product_location %} has {% data variables.product.prodname_actions %} enabled, you must first configure the {% data variables.product.prodname_actions %} external storage provider on the replacement appliance. For more information, see "[Backing up and restoring {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %} enabled](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)." {% endnote %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md index bc73631e43..d91bc49e77 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md @@ -1,6 +1,6 @@ --- title: Configuring email for notifications -intro: 'To make it easy for users to respond quickly to activity on {% data variables.product.product_name %}, you can configure {% data variables.product.product_location %} to send email notifications for issue, pull request, and commit comments.' +intro: 'To make it easy for users to respond quickly to activity on {% data variables.product.product_name %}, you can configure {% data variables.location.product_location %} to send email notifications for issue, pull request, and commit comments.' redirect_from: - /enterprise/admin/guides/installation/email-configuration - /enterprise/admin/articles/configuring-email @@ -159,7 +159,7 @@ This log shows that the appliance: * The `login` authentication type was performed (`<- "AUTH LOGIN\r\n"`). * The SMTP Server rejected the authentication as invalid (`-> "535-5.7.1 Username and Password not accepted.`). -### Check {% data variables.product.product_location %} logs +### Check {% data variables.location.product_location %} logs If you need to verify that your inbound email is functioning, there are two log files that you can examine on your instance: To verify that */var/log/mail.log* and */var/log/mail-replies/metroplex.log*. @@ -193,7 +193,7 @@ In order to properly process inbound emails, you must configure a valid A Record ### Check firewall or AWS Security Group settings -If {% data variables.product.product_location %} is behind a firewall or is being served through an AWS Security Group, make sure port 25 is open to all mail servers that send emails to `reply@reply.[hostname]`. +If {% data variables.location.product_location %} is behind a firewall or is being served through an AWS Security Group, make sure port 25 is open to all mail servers that send emails to `reply@reply.[hostname]`. ### Contact support {% ifversion ghes %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md index e43fd6e4ce..13c0a766fb 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Configurar o GitHub Pages para a sua empresa -intro: 'Você pode habilitar ou desabilitar {% data variables.product.prodname_pages %} para a sua empresa{% ifversion ghes %} e escolher se deseja tornar os sites acessíveis ao público{% endif %}.' +title: Configuring GitHub Pages for your enterprise +intro: 'You can enable or disable {% data variables.product.prodname_pages %} for your enterprise{% ifversion ghes %} and choose whether to make sites publicly accessible{% endif %}.' redirect_from: - /enterprise/admin/guides/installation/disabling-github-enterprise-pages - /enterprise/admin/guides/installation/configuring-github-enterprise-pages @@ -17,68 +17,76 @@ topics: - Enterprise - Pages shortTitle: Configure GitHub Pages -ms.openlocfilehash: 1cb2bd78f006bfd86a3f0a2e42db4fcf2cea3b73 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145094018' --- + {% ifversion ghes %} -## Habilitar sites públicos para {% data variables.product.prodname_pages %} +## Enabling public sites for {% data variables.product.prodname_pages %} -Se o modo privado for habilitado na sua empresa, o público não poderá acessar sites de {% data variables.product.prodname_pages %} hospedados pela sua empresa, a menos que você habilite os sites públicos. +If private mode is enabled on your enterprise, the public cannot access {% data variables.product.prodname_pages %} sites hosted by your enterprise unless you enable public sites. {% warning %} -**Aviso:** se você habilitar sites públicos no {% data variables.product.prodname_pages %}, todos os sites de cada repositório na sua empresa estará acessível ao público. +**Warning:** If you enable public sites for {% data variables.product.prodname_pages %}, every site in every repository on your enterprise will be accessible to the public. {% endwarning %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.pages-tab %} -4. Selecione **Páginas Públicas**. - ![Caixa de seleção usada para habilitar Páginas Públicas](/assets/images/enterprise/management-console/public-pages-checkbox.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.pages-tab %} +4. Select **Public Pages**. + ![Checkbox to enable Public Pages](/assets/images/enterprise/management-console/public-pages-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} -## Desabilitar {% data variables.product.prodname_pages %} para a sua empresa +## Disabling {% data variables.product.prodname_pages %} for your enterprise -Se o isolamento de subdomínio estiver desabilitado para sua empresa, você também deverá desabilitar {% data variables.product.prodname_pages %} para se proteger de possíveis vulnerabilidades de segurança. Para obter mais informações, confira "[Como habilitar o isolamento de subdomínio](/admin/configuration/enabling-subdomain-isolation)". +If subdomain isolation is disabled for your enterprise, you should also disable {% data variables.product.prodname_pages %} to protect yourself from potential security vulnerabilities. For more information, see "[Enabling subdomain isolation](/admin/configuration/enabling-subdomain-isolation)." -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.pages-tab %} -1. Desmarque **Habilitar o Pages**. - ![Caixa de seleção usada para desabilitar o {% data variables.product.prodname_pages %}](/assets/images/enterprise/management-console/pages-select-button.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.pages-tab %} +1. Unselect **Enable Pages**. + ![Checkbox to disable {% data variables.product.prodname_pages %}](/assets/images/enterprise/management-console/pages-select-button.png) +{% data reusables.enterprise_management_console.save-settings %} {% endif %} {% ifversion ghae %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.pages-tab %} -1. Em "Políticas do Pages", desmarque **Habilitar o {% data variables.product.prodname_pages %}** . - ![Caixa de seleção usada para desabilitar o {% data variables.product.prodname_pages %}](/assets/images/enterprise/business-accounts/enable-github-pages-checkbox.png) {% data reusables.enterprise-accounts.pages-policies-save %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.pages-tab %} +1. Under "Pages policies", deselect **Enable {% data variables.product.prodname_pages %}**. + ![Checkbox to disable {% data variables.product.prodname_pages %}](/assets/images/enterprise/business-accounts/enable-github-pages-checkbox.png) +{% data reusables.enterprise-accounts.pages-policies-save %} {% endif %} {% ifversion ghes > 3.4 %} -## Como configurar cabeçalhos de resposta do {% data variables.product.prodname_pages %} para sua empresa +## Configuring {% data variables.product.prodname_pages %} response headers for your enterprise -Você pode adicionar ou substituir cabeçalhos de resposta dos sites do {% data variables.product.prodname_pages %} hospedados pelo {% data variables.product.product_location %}. +You can add or override response headers for {% data variables.product.prodname_pages %} sites hosted by {% data variables.location.product_location %}. {% warning %} -**Aviso:** verifique se os cabeçalhos de resposta estão configurados corretamente antes de salvá-los. Configurações incorretas podem afetar negativamente a segurança do {% data variables.product.product_location %}. +**Warning:** Ensure that your response headers are properly configured before saving. Improper configurations may negatively impact the security of {% data variables.location.product_location %}. {% endwarning %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.pages-tab %} -1. Digite as configurações de cabeçalhos e clique em **Adicionar cabeçalhos**. - - No campo **Nome do Cabeçalho HTTP**, digite o nome do cabeçalho. O nome do cabeçalho deve ter menos de 128 caracteres. - - No campo **Valor do Cabeçalho HTTP**, digite o valor do cabeçalho. O valor do cabeçalho deve ter menos de 300 caracteres. -![Os campos de valor e nome do cabeçalho de resposta do {% data variables.product.prodname_pages %} no {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/pages-override-header-section.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.pages-tab %} +1. Type the headers settings, then click **Add headers**. + - In the **Http Header Name** field, type the header name. The length of header name should less than 128 characters. + - In the **Http Header Value** field, type the header value. The length of header value should less than 300 characters. +![The {% data variables.product.prodname_pages %} response header name and value fields in the {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/pages-override-header-section.png) +{% data reusables.enterprise_management_console.save-settings %} {% endif %} {% ifversion ghes %} -## Leitura adicional +## Further reading -- "[Como habilitar o modo privado](/admin/configuration/enabling-private-mode)" {% endif %} +- "[Enabling private mode](/admin/configuration/enabling-private-mode)" +{% endif %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md index ad8c5c6f4c..0930d0297d 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md @@ -1,8 +1,8 @@ --- -title: Como configurar chaves de host para sua instância +title: Configuring host keys for your instance shortTitle: Configure host keys -intro: 'Você pode aumentar a segurança de {% data variables.product.product_location %} configurando os algoritmos que a sua instância usa para gerar e anunciar chaves de host para conexões SSH de entrada.' -permissions: 'Site administrators can configure the host keys for a {% data variables.product.product_name %} instance.' +intro: 'You can increase the security of {% data variables.location.product_location %} by configuring the algorithms that your instance uses to generate and advertise host keys for incoming SSH connections.' +permissions: "Site administrators can configure the host keys for a {% data variables.product.product_name %} instance." versions: ghes: '>= 3.6' type: how_to @@ -13,38 +13,33 @@ topics: - Networking - Security - SSH -ms.openlocfilehash: d7ab49b814500ac2c35fa65f82c0fb480122ed1b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147410690' --- -## Sobre chaves de host para sua instância -Os servidores que aceitam conexões SSH anunciam uma ou mais chaves de host criptográficas para identificar com segurança o servidor para clientes SSH. Para confirmar a identidade do servidor durante a inicialização de uma conexão, os clientes armazenam e verificam a chave de host. Para obter mais informações, confira [SSH Host Key - What, Why, How](https://ssh.com/academy/ssh/host-key) no site da SSH Academy. +## About host keys for your instance + +Servers that accept SSH connections advertise one or more cryptographic host keys to securely identify the server to SSH clients. To confirm the server's identity during the initialization of a connection, clients store and verify the host key. For more information, see [SSH Host Key - What, Why, How](https://ssh.com/academy/ssh/host-key) on the SSH Academy website. {% data reusables.enterprise.about-ssh-ports %} -Por padrão, {% data variables.product.product_location %} gera e anuncia chaves de host com a rotação de chaves de host em estilo OpenSSH. Para aumentar a segurança do SSH em seu ambiente, você pode habilitar algoritmos adicionais para a geração de chaves de host. +By default, {% data variables.location.product_location %} generates and advertises host keys with OpenSSH-style host key rotation. To increase the security of SSH in your environment, you can enable additional algorithms for the generation of host keys. {% note %} -**Observação**: se você habilitar algoritmos de chave de host adicionais, os clientes que não usam o OpenSSH para conexões SSH poderão receber avisos durante a conexão ou não se conectarem por inteiro. Algumas implementações de SSH podem ignorar algoritmos sem suporte e fazer fallback para um algoritmo diferente. Se o cliente não der suporte a fallback, a conexão falhará. Por exemplo, a biblioteca SSH para Go não dá suporte a fallback para um algoritmo diferente. +**Note**: If you enable additional host key algorithms, clients that do not use OpenSSH for SSH connections may experience warnings during connection, or fail to connect entirely. Some SSH implementations can ignore unsupported algorithms and fall back to a different algorithm. If the client does not support fallback, the connection will fail. For example, the SSH library for Go does not support fallback to a different algorithm. {% endnote %} -## Como gerenciar uma chave de host Ed25519 +## Managing an Ed25519 host key -Para aprimorar a segurança dos clientes que se conectam a {% data variables.product.product_location %}, você pode habilitar a geração e o anúncio de uma chave de host Ed25519. Ed25519 é imune a alguns ataques que visam algoritmos de assinatura mais antigos, sem comprometer a velocidade. Os clientes SSH mais antigos podem não dar suporte ao Ed25519. Por padrão, as instâncias {% data variables.product.product_name %} não geram nem anunciam uma chave de host Ed25519. Para obter mais informações, confira [o site do Ed25519](https://ed25519.cr.yp.to). +To improve security for clients that connect to {% data variables.location.product_location %}, you can enable the generation and advertisement of an Ed25519 host key. Ed25519 is immune to some attacks that target older signature algorithms, without sacrificing speed. Older SSH clients may not support Ed25519. By default, {% data variables.product.product_name %} instances do not generate or advertise an Ed25519 host key. For more information, see [the Ed25519 website](https://ed25519.cr.yp.to). {% data reusables.enterprise_installation.ssh-into-instance %} -1. Para habilitar a geração e o anúncio da chave de host Ed25519, insira o comando a seguir. +1. To enable generation and advertisement of the Ed25519 host key, enter the following command. ```shell ghe-config app.babeld.host-key-ed25519 true ``` -1. Opcionalmente, insira o comando a seguir para desabilitar a geração e o anúncio da chave de host Ed25519. +1. Optionally, enter the following command to disable generation and advertisement of the Ed25519 host key. ```shell ghe-config app.babeld.host-key-ed25519 false diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md index 56837a896b..a3a2e28ce7 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md @@ -36,7 +36,7 @@ You can exempt a list of users from API rate limits using the `ghe-config` utili ## Enabling secondary rate limits -Setting secondary rate limits protects the overall level of service on {% data variables.product.product_location %}. +Setting secondary rate limits protects the overall level of service on {% data variables.location.product_location %}. {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} @@ -76,13 +76,13 @@ You can apply a rate limit to {% data variables.product.prodname_actions %} work ### About rate limits for {% data variables.product.prodname_actions %} -Your {% data variables.product.product_name %} instance assigns each {% data variables.product.prodname_actions %} workflow job to a runner. If your instance cannot immediately assign a job to an available runner, the job will wait in a queue until a runner is available. If {% data variables.product.prodname_actions %} experiences sustained high load, the queue can back up, and the performance of {% data variables.product.product_location %} may degrade. +Your {% data variables.product.product_name %} instance assigns each {% data variables.product.prodname_actions %} workflow job to a runner. If your instance cannot immediately assign a job to an available runner, the job will wait in a queue until a runner is available. If {% data variables.product.prodname_actions %} experiences sustained high load, the queue can back up, and the performance of {% data variables.location.product_location %} may degrade. To avoid this performance degradation, you can configure a rate limit for {% data variables.product.prodname_actions %}. This rate limit is expressed in job runs per minute. {% data variables.product.product_name %} calculates and applies the rate limit for the sum total of all job runs on the instance. If runs exceed the rate limit, additional runs will fail instead of entering the queue. The following error will appear in the run's annotations. > You've exceeded the rate limit for workflow run requests. Please wait before retrying the run. -An appropriate rate limit protects {% data variables.product.product_location %} from abnormal usage of {% data variables.product.prodname_actions %} without interfering with day-to-day operations. The exact threshold depends on your instance's available resources and overall load profile. For more information about the hardware requirements for {% data variables.product.prodname_actions %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-requirements)." +An appropriate rate limit protects {% data variables.location.product_location %} from abnormal usage of {% data variables.product.prodname_actions %} without interfering with day-to-day operations. The exact threshold depends on your instance's available resources and overall load profile. For more information about the hardware requirements for {% data variables.product.prodname_actions %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-requirements)." By default, the rate limit for {% data variables.product.prodname_actions %} is disabled. Because {% data variables.product.product_name %} can handle temporary spikes in usage without performance degradation, this rate limit is intended to protect against sustained high load. We recommend leaving the rate limit disabled unless you are experiencing performance problems. In some cases, {% data variables.contact.github_support %} may recommend that you enable a rate limit for {% data variables.product.prodname_actions %}. diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md index a9f6b3ac17..c76cd8b27b 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md @@ -1,8 +1,8 @@ --- -title: Como configurar conexões SSH para sua instância +title: Configuring SSH connections to your instance shortTitle: Configure SSH connections -intro: 'Você pode aumentar a segurança de {% data variables.product.product_location %} configurando os algoritmos SSH que os clientes podem usar para estabelecer uma conexão.' -permissions: 'Site administrators can configure SSH connections to a {% data variables.product.product_name %} instance.' +intro: 'You can increase the security of {% data variables.location.product_location %} by configuring the SSH algorithms that clients can use to establish a connection.' +permissions: "Site administrators can configure SSH connections to a {% data variables.product.product_name %} instance." versions: ghes: '>= 3.6' type: how_to @@ -13,43 +13,38 @@ topics: - Networking - Security - SSH -ms.openlocfilehash: cf884172028d5419a0cf5287b4a108ee7ca52c12 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147409728' --- -## Sobre conexões SSH para sua instância + +## About SSH connections to your instance {% data reusables.enterprise.about-ssh-ports %} -Para acomodar os clientes SSH em seu ambiente, você pode configurar os tipos de conexões que {% data variables.product.product_location %} aceitará. +To accommodate the SSH clients in your environment, you can configure the types of connections that {% data variables.location.product_location %} will accept. -## Como configurar conexões SSH com chaves RSA +## Configuring SSH connections with RSA keys -Quando os usuários executam operações Git em {% data variables.product.product_location %} por SSH pela porta 22, o cliente pode se autenticar com uma chave RSA. O cliente pode assinar a tentativa usando a função de hash SHA-1. Nesse contexto, a função de hash SHA-1 não é mais segura. Para obter mais informações, confira [SHA-1](https://en.wikipedia.org/wiki/SHA-1) na Wikipédia. +When users perform Git operations on {% data variables.location.product_location %} via SSH over port 22, the client can authenticate with an RSA key. The client may sign the attempt using the SHA-1 hash function. In this context, the SHA-1 hash function is no longer secure. For more information, see [SHA-1](https://en.wikipedia.org/wiki/SHA-1) on Wikipedia. -Por padrão{% ifversion ghes < 3.7 %} em {% data variables.product.product_name %} 3.6 e versões posteriores{% endif %}, as conexões SSH que satisfazem as **duas** condições a seguir falharão. +By default{% ifversion ghes < 3.7 %} on {% data variables.product.product_name %} 3.6 and later{% endif %}, SSH connections that satisfy **both** of the following conditions will fail. {% data reusables.ssh.rsa-sha-1-connection-failure-criteria %} -Você pode ajustar a data de corte. Se o usuário tiver carregado a chave RSA antes da data de corte, o cliente poderá continuar se conectando com êxito usando SHA-1, desde que a chave permaneça válida. Como alternativa, você poderá rejeitar todas as conexões SSH autenticadas com uma chave RSA se o cliente assinar a conexão usando a função de hash SHA-1. +You can adjust the cutoff date. If the user uploaded the RSA key before the cutoff date, the client can continue to connect successfuly using SHA-1 as long as the key remains valid. Alternatively, you can reject all SSH connections authenticated with an RSA key if the client signs the connection using the SHA-1 hash function. -Independentemente da configuração escolhida para sua instância, os clientes podem continuar a se conectar usando qualquer chave RSA assinada com uma função de hash SHA-2. +Regardless of the setting you choose for your instance, clients can continue to connect using any RSA key signed with a SHA-2 hash function. -Se você usar uma autoridade de certificação SSH, as conexões falharão se a data `valid_after` do certificado ocorrer após a data de corte. Para obter mais informações, confira "[Sobre as autoridades de certificado SSH](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)". +If you use an SSH certificate authority, connections will fail if the certificate's `valid_after` date is after the cutoff date. For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)." -Para obter mais informações, confira [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server). +For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server). {% data reusables.enterprise_installation.ssh-into-instance %} -1. Audite os logs da sua instância para conexões que usam algoritmos não seguros ou funções de hash usando o utilitário `ghe-find-insecure-git-operations`. Para obter mais informações, confira "[Utilitários de linha de comando](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-find-insecure-git-operations)". -1. Para configurar uma data de corte após a qual {% data variables.product.product_location %} negará conexões de clientes que usam uma chave RSA carregada após a data se a conexão for assinada pela função de hash SHA-1, insira o comando a seguir. Substitua _**RFC-3399-UTC-TIMESTAMP**_ por um carimbo de data/hora UTC RFC 3399 UTC válido. Por exemplo, o valor padrão, 1º de agosto de 2022, seria representado como `2022-08-01T00:00:00Z`. Para obter mais informações, confira [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) no site do IETF. +1. Audit your instance's logs for connections that use unsecure algorithms or hash functions using the `ghe-find-insecure-git-operations` utility. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-find-insecure-git-operations)." +1. To configure a cutoff date after which {% data variables.location.product_location %} will deny connections from clients that use an RSA key uploaded after the date if the connection is signed by the SHA-1 hash function, enter the following command. Replace _**RFC-3399-UTC-TIMESTAMP**_ with a valid RFC 3399 UTC timestamp. For example, the default value, August 1, 2022, would be represented as `2022-08-01T00:00:00Z`. For more information, see [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) on the IETF website.
-   $ ghe-config app.gitauth.rsa-sha1 RFC-3339-UTC-TIMESTAMP
+   $ ghe-config app.gitauth.rsa-sha1 RFC-3339-UTC-TIMESTAMP
    
-1. Como alternativa, para desabilitar completamente as conexões SSH usando chaves RSA assinadas com a função de hash SHA-1, insira o comando a seguir. +1. Alternatively, to completely disable SSH connections using RSA keys that are signed with the SHA-1 hash function, enter the following command. ```shell ghe-config app.gitauth.rsa-sha1 false diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md index b0463ba2ef..ef1314f097 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Configurar a política de indicação para a sua empresa +title: Configuring the referrer policy for your enterprise shortTitle: Configure referrer policy -intro: 'Você pode aumentar a privacidade do {% data variables.product.product_location %} configurando a política para solicitações de origem cruzada.' +intro: 'You can increase the privacy of {% data variables.location.product_location %} by configuring the policy for cross-origin requests.' versions: ghes: '*' type: how_to @@ -10,33 +10,29 @@ topics: - Networking - Privacy - Security -ms.openlocfilehash: 4824e938e044a89e9d0e534564214c6a46ba44da -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147066487' --- -## Sobre a política de indicação para a sua empresa -A política de referência controla a informação que {% data variables.product.product_name %} transmite em cabeçalhos HTTP quando alguém visita um link de {% data variables.product.product_location %} para um site externo. +## About the referrer policy for your enterprise -Por padrão, quando um usuário do {% data variables.product.product_location %} acessa um link de outro site por meio de um arquivo ou de um comentário na sua instância, a solicitação inclui o nome do host da sua instância em texto sem formatação no cabeçalho `Referer`. Se o link levar a um site externo, o proprietário do site poderá ler o nome de host da sua instância em solicitações ou arquivos de registro. +The referrer policy controls the information that {% data variables.product.product_name %} transmits in HTTP headers when someone visits a link from {% data variables.location.product_location %} to an external site. -Você pode controlar as informações que {% data variables.product.product_name %} envia quando um usuário acessa um link da sua instância. +By default, when a user on {% data variables.location.product_location %} visits a link to another site from a file or comment on your instance, the request includes the hostname for your instance in plain text within the `Referer` header. If the link leads to an external website, the owner of the website could read the hostname for your instance in requests or log files. -## Como habilitar a política de referenciador `same-origin` +You can control the information that {% data variables.product.product_name %} sends when a user visits a link from your instance. -Você pode habilitar a política de referenciador `same-origin` para instruir os navegadores modernos a excluir o nome do host do {% data variables.product.product_location %} nas solicitações para sites externos. A configuração aplica-se a todos os links da interface web na sua instância. Por padrão, o {% data variables.product.product_name %} usa as políticas de referenciador `origin-when-cross-origin` e `strict-origin-when-cross-origin`, o que significa que o nome do host da instância será exibido nas solicitações HTTP e HTTPS para sites externos. +## Enabling the `same-origin` referrer policy + +You can enable the `same-origin` referrer policy to instruct modern browsers to exclude the hostname for {% data variables.location.product_location %} from requests to external websites. The setting applies to all links from the web interface on your instance. By default, {% data variables.product.product_name %} uses the `origin-when-cross-origin` and `strict-origin-when-cross-origin` referrer policies, which means your instance's hostname will appear in HTTP and HTTPS requests to external websites. {% note %} -**Observação**: a alteração da política de referenciador `same-origin` pode afetar os sites externos que esperam um nome do host nos cabeçalhos HTTP de uma solicitação. +**Note**: Changing the referrer policy to `same-origin` can affect external sites that expect a hostname in the HTTP headers for a request. {% endnote %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} -1. Em "Política do Referenciador do Agente de Usuário", selecione **Habilitar a mesma política de referenciador de mesma origem para todas as organizações**. - ![Caixa de seleção usada para habilitar a política de referenciador de mesma origem](/assets/images/enterprise/settings/referrer-policy-checkbox.png) -1. Clique em **Salvar**. - ![Botão Salvar para habilitar a política de referenciador de mesma origem](/assets/images/enterprise/settings/referrer-policy-save-button.png) +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +1. Under "User Agent Referrer Policy", select **Enable same origin referrer policy for all organizations**. + ![Checkbox for enabling same origin referrer policy](/assets/images/enterprise/settings/referrer-policy-checkbox.png) +1. Click **Save**. + ![Save button for enabling same origin referrer policy](/assets/images/enterprise/settings/referrer-policy-save-button.png) diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md index 07a642c608..37a73bf097 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md @@ -1,7 +1,7 @@ --- -title: Configurar a assinatura de commit da Web +title: Configuring web commit signing shortTitle: Configure web commit signing -intro: 'Você pode habilitar a assinatura automática de commits feitos na interface da Web do {% data variables.product.product_name %}.' +intro: 'You can enable auto-signing of commits made in the web interface of {% data variables.product.product_name %}.' versions: ghes: '>=3.5' type: how_to @@ -11,62 +11,67 @@ topics: - Fundamentals - Identity - Security -permissions: 'Site administrators can configure web commit signing for {% data variables.product.product_location %}.' -ms.openlocfilehash: 759b158235e5727b474441d10b33016b58277c7f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147068031' +permissions: 'Site administrators can configure web commit signing for {% data variables.location.product_location %}.' --- -## Sobre a assinatura de commit da Web -Se você ativar a assinatura de commit da Web, {% data variables.product.product_name %} usará automaticamente o GPG para assinar as commits que os usuários fizerem na interface da Web de {% data variables.product.product_location %}. Os commits assinados por {% data variables.product.product_name %} terão um status verificado. Para obter mais informações, confira "[Sobre a verificação de assinatura de commit](/authentication/managing-commit-signature-verification/about-commit-signature-verification)". +## About web commit signing -Você pode habilitar a assinatura de commit da Web, alternar a chave privada usada para a assinatura de commit da Web e desabilitar a assinatura de commit da Web. +If you enable web commit signing, {% data variables.product.product_name %} will automatically use GPG to sign commits users make on the web interface of {% data variables.location.product_location %}. Commits signed by {% data variables.product.product_name %} will have a verified status. For more information, see "[About commit signature verification](/authentication/managing-commit-signature-verification/about-commit-signature-verification)." -## Habilitar a assinatura de commit da Web +You can enable web commit signing, rotate the private key used for web commit signing, and disable web commit signing. + +## Enabling web commit signing {% data reusables.enterprise_site_admin_settings.create-pgp-key-web-commit-signing %} - - Se você tiver um endereço de email sem resposta definido em {% data variables.enterprise.management_console %}, use esse endereço de email. Caso contrário, use qualquer endereço de email, como `web-flow@my-company.com`. O endereço de email não precisa ser válido. -{% data reusables.enterprise_site_admin_settings.pgp-key-no-passphrase %} {% data reusables.enterprise_site_admin_settings.pgp-key-env-variable %} {% data reusables.enterprise_site_admin_settings.update-commit-signing-service %} -1. Habilite a assinatura de commit da Web. + - Use `web-flow` as the username. If `web-flow` is unavailable or unusable, use any new unique username. Use this username throughout the following steps in this article. + - If you have a no-reply email address defined in the {% data variables.enterprise.management_console %}, use that email address. If not, use any email address, such as `web-flow@my-company.com`. The email address does not need to be valid. +{% data reusables.enterprise_site_admin_settings.pgp-key-no-passphrase %} +{% data reusables.enterprise_site_admin_settings.pgp-key-env-variable %} +{% data reusables.enterprise_site_admin_settings.update-commit-signing-service %} +1. Enable web commit signing. ```bash{:copy} ghe-config app.github.web-commit-signing-enabled true ``` -1. Aplique a configuração e aguarde a conclusão da execução da configuração. +1. Apply the configuration, then wait for the configuration run to complete. ```bash{:copy} ghe-config-apply ``` -1. Crie um novo usuário em {% data variables.product.product_location %} por meio de autenticação integrada ou autenticação externa. Para obter mais informações, confira "[Sobre a autenticação para sua empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)". - - O nome de usuário precisa ser `web-flow`. - - O endereço de email do usuário deve ser o mesmo endereço que você usou para a chave PGP. {% data reusables.enterprise_site_admin_settings.add-key-to-web-flow-user %} {% data reusables.enterprise_site_admin_settings.email-settings %} -1. Em "Endereço de email sem resposta", digite o mesmo endereço de email usado para a chave PGP. +1. Create a new user on {% data variables.location.product_location %} via built-in authentication or external authentication. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)." + - The user's username must be the same username you used when creating the PGP key in step 1 above, for example, `web-flow`. + - The user's email address must be the same address you used when creating the PGP key. +{% data reusables.enterprise_site_admin_settings.add-key-to-web-flow-user %} +{% data reusables.enterprise_site_admin_settings.email-settings %} +1. Under "No-reply email address", type the same email address you used when creating the PGP key. {% note %} - **Observação:** O campo "Endereço de email sem resposta" só será exibido se você tiver ativado o email para {% data variables.product.product_location %}. Para obter mais informações, confira "[Como configurar o email para notificações](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications#configuring-smtp-for-your-enterprise)". + **Note:** The "No-reply email address" field will only be displayed if you've enabled email for {% data variables.location.product_location %}. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications#configuring-smtp-for-your-enterprise)." - {% endnote %} {% data reusables.enterprise_management_console.save-settings %} + {% endnote %} +{% data reusables.enterprise_management_console.save-settings %} -## Girar a chave privada usada para assinatura de commit da Web +## Rotating the private key used for web commit signing {% data reusables.enterprise_site_admin_settings.create-pgp-key-web-commit-signing %} - - Use o endereço de email sem resposta definido em {% data variables.enterprise.management_console %}, que deve ser igual ao endereço de email do usuário `web-flow`. -{% data reusables.enterprise_site_admin_settings.pgp-key-no-passphrase %} {% data reusables.enterprise_site_admin_settings.pgp-key-env-variable %} {% data reusables.enterprise_site_admin_settings.update-commit-signing-service %} {% data reusables.enterprise_site_admin_settings.add-key-to-web-flow-user %} + - Use the web commit signing user's username, for example, `web-flow`. + - Use the no-reply email address defined in the {% data variables.enterprise.management_console %}, which should be the same as the email address of the web commit signing user, for example, `web-flow`. +{% data reusables.enterprise_site_admin_settings.pgp-key-no-passphrase %} +{% data reusables.enterprise_site_admin_settings.pgp-key-env-variable %} +{% data reusables.enterprise_site_admin_settings.update-commit-signing-service %} +{% data reusables.enterprise_site_admin_settings.add-key-to-web-flow-user %} -## Desabilitar a assinatura de commit da Web +## Disabling web commit signing -Você pode desabilitar a assinatura de commit da Web para {% data variables.product.product_location %}. +You can disable web commit signing for {% data variables.location.product_location %}. -1. No shell administrativo, execute o comando a seguir. +1. In the administrative shell, run the following command. ```bash{:copy} ghe-config app.github.web-commit-signing-enabled false ``` -1. Aplicar a configuração. +1. Apply the configuration. ```bash{:copy} ghe-config-apply diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md index f58e69e013..fd5a8111b5 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md @@ -1,6 +1,6 @@ --- -title: Habilitar e programar o modo de manutenção -intro: 'Alguns procedimentos de manutenção padrão, como atualizar {% data variables.product.product_location %} ou restaurar backups, exigem que a instância seja colocada offline para uso normal.' +title: Enabling and scheduling maintenance mode +intro: 'Some standard maintenance procedures, such as upgrading {% data variables.location.product_location %} or restoring backups, require the instance to be taken offline for normal use.' redirect_from: - /enterprise/admin/maintenance-mode - /enterprise/admin/categories/maintenance-mode @@ -20,80 +20,77 @@ topics: - Maintenance - Upgrades shortTitle: Configure maintenance mode -ms.openlocfilehash: 45ac412b1ae13e69d710c4dd93072143f6ffa502 -ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '146331765' --- -## Sobre o modo de manutenção +## About maintenance mode -Alguns tipos de operações exigem que você coloque o {% data variables.product.product_location %} offline e no modo de manutenção: -- Atualizar para uma nova versão do {% data variables.product.prodname_ghe_server %}; -- Aumentar a capacidade dos recursos de CPU, memória ou armazenamento alocados na máquina virtual; -- Migrar dados de uma máquina virtual para outra; -- Restaurar dados de um instantâneo do {% data variables.product.prodname_enterprise_backup_utilities %}; -- Solucionar determinados tipos de problemas graves no aplicativo. +Some types of operations require that you take {% data variables.location.product_location %} offline and put it into maintenance mode: +- Upgrading to a new version of {% data variables.product.prodname_ghe_server %} +- Increasing CPU, memory, or storage resources allocated to the virtual machine +- Migrating data from one virtual machine to another +- Restoring data from a {% data variables.product.prodname_enterprise_backup_utilities %} snapshot +- Troubleshooting certain types of critical application issues -É recomendável programar um período de manutenção de no mínimo 30 minutos para que os usuários tenham tempo de se preparar. Quando houver um período de manutenção programado, todos os usuários verão um banner ao acessar o site. +We recommend that you schedule a maintenance window for at least 30 minutes in the future to give users time to prepare. When a maintenance window is scheduled, all users will see a banner when accessing the site. -![Banner para usuário final sobre manutenção programada](/assets/images/enterprise/maintenance/maintenance-scheduled.png) +![End user banner about scheduled maintenance](/assets/images/enterprise/maintenance/maintenance-scheduled.png) -Quando a instância estiver em modo de manutenção, todos os acessos regulares por HTTP e Git serão recusados. Operações de fetch, clonagem e push também são rejeitadas, e uma mensagem de erro indicará que o site está temporariamente indisponível. Em configurações de alta disponibilidade, a replicação do Git será colocada em pausa. Os trabalhos com GitHub Actions não serão executados. O acesso ao site por navegador levará a uma página de manutenção. +When the instance is in maintenance mode, all normal HTTP and Git access is refused. Git fetch, clone, and push operations are also rejected with an error message indicating that the site is temporarily unavailable. In high availability configurations, Git replication will be paused. GitHub Actions jobs will not be executed. Visiting the site in a browser results in a maintenance page. -![Tela inicial do modo de manutenção](/assets/images/enterprise/maintenance/maintenance-mode-maintenance-page.png) +![The maintenance mode splash screen](/assets/images/enterprise/maintenance/maintenance-mode-maintenance-page.png) {% ifversion ip-exception-list %} -Você pode executar a validação inicial de sua operação de manutenção configurando uma lista de exceções de IP para permitir o acesso ao {% data variables.product.product_location %} somente dos endereços IP e intervalos fornecidos. As tentativas de acessar o {% data variables.product.product_location %} de endereços IP não especificados na lista de exceções de IP receberão uma resposta consistente com as enviadas quando a instância estiver no modo de manutenção. +You can perform initial validation of your maintenance operation by configuring an IP exception list to allow access to {% data variables.location.product_location %} from only the IP addresses and ranges provided. Attempts to access {% data variables.location.product_location %} from IP addresses not specified on the IP exception list will receive a response consistent with those sent when the instance is in maintenance mode. {% endif %} -## Habilitar o modo de manutenção imediatamente ou programar um período de manutenção mais tarde +## Enabling maintenance mode immediately or scheduling a maintenance window for a later time -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} -2. Na parte superior do {% data variables.enterprise.management_console %}, clique em **Manutenção**. - ![Guia Manutenção](/assets/images/enterprise/management-console/maintenance-tab.png) -3. Em "Enable and schedule" (Habilitar e programar), decida se você quer habilitar o modo de manutenção imediatamente ou programar um período de manutenção depois. - - Para habilitar o modo de manutenção imediatamente, use o menu suspenso e clique em **Agora**. - ![Menu suspenso com a opção para habilitar o modo de manutenção agora selecionado](/assets/images/enterprise/maintenance/enable-maintenance-mode-now.png) - - Para programar um período de manutenção depois, use o menu suspenso e clique no horário em que você pretende iniciar o período de manutenção. - ![Menu suspenso com a opção para habilitar o modo de manutenção em duas horas selecionado](/assets/images/enterprise/maintenance/schedule-maintenance-mode-two-hours.png) -4. Selecione **Habilitar modo de manutenção**. - ![Caixa de seleção usada para habilitar ou agendar o modo de manutenção](/assets/images/enterprise/maintenance/enable-maintenance-mode-checkbox.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +2. At the top of the {% data variables.enterprise.management_console %}, click **Maintenance**. + ![Maintenance tab](/assets/images/enterprise/management-console/maintenance-tab.png) +3. Under "Enable and schedule", decide whether to enable maintenance mode immediately or to schedule a maintenance window for a future time. + - To enable maintenance mode immediately, use the drop-down menu and click **now**. + ![Drop-down menu with the option to enable maintenance mode now selected](/assets/images/enterprise/maintenance/enable-maintenance-mode-now.png) + - To schedule a maintenance window for a future time, use the drop-down menu and click a start time. + ![Drop-down menu with the option to schedule a maintenance window in two hours selected](/assets/images/enterprise/maintenance/schedule-maintenance-mode-two-hours.png) +4. Select **Enable maintenance mode**. + ![Checkbox for enabling or scheduling maintenance mode](/assets/images/enterprise/maintenance/enable-maintenance-mode-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} {% ifversion ip-exception-list %} -## Validando alterações no modo de manutenção usando a lista de exceções de IP +## Validating changes in maintenance mode using the IP exception list -A lista de exceções de IP fornece acesso controlado e restrito ao {% data variables.product.product_location %}, ideal para validação inicial da integridade do servidor após uma operação de manutenção. Depois de habilitada, o {% data variables.product.product_location %} será retirado do modo de manutenção e ficará disponível somente para os endereços IP configurados. A caixa de seleção do modo de manutenção será atualizada para refletir a alteração no estado. +The IP exception list provides controlled and restricted access to {% data variables.location.product_location %}, which is ideal for initial validation of server health following a maintenance operation. Once enabled, {% data variables.location.product_location %} will be taken out of maintenance mode and available only to the configured IP addresses. The maintenance mode checkbox will be updated to reflect the change in state. -Se você reabilitar o modo de manutenção, a lista de exceções de IP será desabilitada e o {% data variables.product.product_location %} retornará ao modo de manutenção. Se você simplesmente desabilitar a lista de exceções de IP, o {% data variables.product.product_location %} retornará à operação normal. +If you re-enable maintenance mode, the IP exception list will be disabled and {% data variables.location.product_location %} will return to maintenance mode. If you just disable the IP exception list, {% data variables.location.product_location %} will return to normal operation. -Você também pode usar um utilitário de linha de comando para configurar a lista de exceções de IP. Para obter mais informações, confira "[Utilitários de linha de comando](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-maintenance)" e "[Como acessar o shell administrativo (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)". +You can also use a command-line utility to configure the IP exception list. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-maintenance)" and "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} -1. Na parte superior do {% data variables.enterprise.management_console %}, clique em **Manutenção** e confirme se o modo de manutenção já está habilitado. - ![Guia Manutenção](/assets/images/enterprise/management-console/maintenance-tab.png) -1. Selecione **Habilitar lista de exceções de IP**. - ![Caixa de seleção para habilitar a lista de exceções de IP](/assets/images/enterprise/maintenance/enable-ip-exception-list.png) -1. Na caixa de texto, digite uma lista válida de endereços IP separados por espaço ou blocos CIDR que devem ter permissão para acessar o {% data variables.product.product_location %}. - ![campo preenchido com endereços IP](/assets/images/enterprise/maintenance/ip-exception-list-ip-addresses.png) -1. Clique em **Salvar**. -![depois que a lista de exceções de IP tiver sido salva](/assets/images/enterprise/maintenance/ip-exception-save.png) +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +1. At the top of the {% data variables.enterprise.management_console %}, click **Maintenance**, and confirm maintenance mode is already enabled. + ![Maintenance tab](/assets/images/enterprise/management-console/maintenance-tab.png) +1. Select **Enable IP exception list**. + ![Checkbox for enabling ip exception list](/assets/images/enterprise/maintenance/enable-ip-exception-list.png) +1. In the text box, type a valid list of space-separated IP addresses or CIDR blocks that should be allowed to access {% data variables.location.product_location %}. + ![completed field for IP addresses](/assets/images/enterprise/maintenance/ip-exception-list-ip-addresses.png) +1. Click **Save**. +![after IP excetpion list has saved](/assets/images/enterprise/maintenance/ip-exception-save.png) {% endif %} -## Programar o modo de manutenção com a {% data variables.product.prodname_enterprise_api %} +## Scheduling maintenance mode with the {% data variables.product.prodname_enterprise_api %} -Você pode programar o modo de manutenção para horas ou datas diferentes na {% data variables.product.prodname_enterprise_api %}. Para obter mais informações, confira "[Console de Gerenciamento](/enterprise/user/rest/reference/enterprise-admin#enable-or-disable-maintenance-mode)". +You can schedule maintenance for different times or dates with the {% data variables.product.prodname_enterprise_api %}. For more information, see "[Management Console](/enterprise/user/rest/reference/enterprise-admin#enable-or-disable-maintenance-mode)." -## Habilitar ou desabilitar o modo de manutenção para todos os nós do cluster +## Enabling or disabling maintenance mode for all nodes in a cluster -Com o utilitário `ghe-cluster-maintenance`, você pode definir o modo de manutenção para cada nó em um cluster ou cancelar a definição dele. +With the `ghe-cluster-maintenance` utility, you can set or unset maintenance mode for every node in a cluster. ```shell $ ghe-cluster-maintenance -h diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md index c585b64cea..e0f3bb8c8f 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md @@ -1,6 +1,6 @@ --- -title: Habilitar o modo privado -intro: 'No modo privado, o {% data variables.product.prodname_ghe_server %} exige que todos os usuários façam login para acessar a instalação.' +title: Enabling private mode +intro: 'In private mode, {% data variables.product.prodname_ghe_server %} requires every user to sign in to access the installation.' redirect_from: - /enterprise/admin/articles/private-mode - /enterprise/admin/guides/installation/security @@ -20,19 +20,16 @@ topics: - Networking - Privacy - Security -ms.openlocfilehash: 99488886b1da5b07c2ddb5d7054c10957f6c573b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146332781' --- -Você precisará habilitar o modo privado se o {% data variables.product.product_location %} estiver acessível publicamente pela Internet. No modo privado, os usuários não podem clonar repositórios de maneira anônima por meio do `git://`. Se a autenticação integrada também estiver habilitada, o administrador deverá convidar novos usuários para criar uma conta na instância. Para obter mais informações, veja "[Configurar a autenticação interna](/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication)". +You must enable private mode if {% data variables.location.product_location %} is publicly accessible over the Internet. In private mode, users cannot anonymously clone repositories over `git://`. If built-in authentication is also enabled, an administrator must invite new users to create an account on the instance. For more information, see "[Configuring built-in authentication](/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication)." {% data reusables.enterprise_installation.image-urls-viewable-warning %} -Com o modo privado habilitado, você pode permitir operações do Git não autenticadas (e qualquer pessoa com acesso de rede no {% data variables.product.product_location %}) para ler o código de um repositório público na sua instância com o acesso de leitura anônimo do Git habilitado. Para obter mais informações, confira "[Como permitir que os administradores habilitem o acesso de leitura anônimo do Git em repositórios públicos](/enterprise/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)". +With private mode enabled, you can allow unauthenticated Git operations (and anyone with network access to {% data variables.location.product_location %}) to read a public repository's code on your instance with anonymous Git read access enabled. For more information, see "[Allowing admins to enable anonymous Git read access to public repositories](/enterprise/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)." -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} -4. Selecione **Modo privado**. - ![Caixa de seleção usada para habilitar o modo privado](/assets/images/enterprise/management-console/private-mode-checkbox.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +4. Select **Private mode**. + ![Checkbox for enabling private mode](/assets/images/enterprise/management-console/private-mode-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md index ec8801f23a..5b582d0630 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md @@ -1,6 +1,6 @@ --- -title: Inicializar o GitHub AE -intro: 'Para deixar a sua empresa pronta para uso, você pode definir a configuração inicial de {% data variables.product.product_name %}.' +title: Initializing GitHub AE +intro: 'To get your enterprise ready to use, you can complete the initial configuration of {% data variables.product.product_name %}.' versions: ghae: '*' type: how_to @@ -9,128 +9,123 @@ topics: redirect_from: - /admin/configuration/initializing-github-ae - /enterprise-server@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae -ms.openlocfilehash: f7d53e727fc7cbc58743a62d9c9d755cb799dbef -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147400351' --- -## Sobre a inicialização +## About initialization -Antes de inicializar sua empresa, você deve comprar {% data variables.product.product_name %}. Para mais informações, entre em contato com {% data variables.contact.contact_enterprise_sales %}. +Before you can initialize your enterprise, you must purchase {% data variables.product.product_name %}. For more information, contact {% data variables.contact.contact_enterprise_sales %}. -{% data reusables.github-ae.initialize-enterprise %} Certifique-se de que as informações fornecidas correspondem às informações do proprietário corporativo desejado no IdP. Para obter mais informações sobre proprietários de empresas, confira "[Funções em uma empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)". +{% data reusables.github-ae.initialize-enterprise %} Make sure the information you provide matches the intended enterprise owner's information in the IdP. For more information about enterprise owners, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)." {% note %} -**Observações**: +**Notes**: -- Se a senha inicial para {% data variables.product.prodname_ghe_managed %} expirar antes de a inicialização ser concluída, você pode solicitar uma redefinição de senha a qualquer momento do seu e-mail de convite. +- If the initial password for {% data variables.product.prodname_ghe_managed %} expires before you finish initialization, you can request a password reset at any time from your invitation email. -- Armazene o nome de usuário e senha inicial para {% data variables.product.prodname_ghe_managed %} de forma segura em um gerenciador de senhas. {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} +- Store the initial username and password for {% data variables.product.prodname_ghe_managed %} securely in a password manager. {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} {% endnote %} -Durante a inicialização, o proprietário da empresa irá nomear a sua empresa, configurar o SAML SSO, criar políticas para todas as organizações da sua empresa e configurar um contato de suporte para seus usuários. +During initialization, the enterprise owner will name your enterprise, configure SAML SSO, create policies for all organizations in your enterprise, and configure a support contact for your users. -## Pré-requisitos +## Prerequisites -Para começar a inicialização, você receberá um e-mail de convite de {% data variables.product.company_short %}. Antes de configurar {% data variables.product.prodname_ghe_managed %}, revise os pré-requisitos a seguir. +To begin initialization, you will receive an invitation email from {% data variables.product.company_short %}. Before you configure {% data variables.product.prodname_ghe_managed %}, review the following prerequisites. -1. Para inicializar {% data variables.product.product_location %}, você deve ter um provedor de identidade (IdP) SAML. {% data reusables.saml.ae-uses-saml-sso %} Para conectar seu IdP à sua empresa durante a inicialização, você deve ter a URL do ID da Entidade do seu IdP (SSO), a URL do ID do Emissor e o certificado de assinatura pública (codificado em Base64). Para obter mais informações, confira "[Sobre o gerenciamento de identidades e acesso da sua empresa](/admin/authentication/about-identity-and-access-management-for-your-enterprise)". +1. To initialize {% data variables.location.product_location %}, you must have a SAML identity provider (IdP). {% data reusables.saml.ae-uses-saml-sso %} To connect your IdP to your enterprise during initialization, you should have your IdP's Entity ID (SSO) URL, Issuer ID URL, and public signing certificate (Base64-encoded). For more information, see "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)." {% note %} - **Observação**: {% data reusables.saml.create-a-machine-user %} + **Note**: {% data reusables.saml.create-a-machine-user %} {% endnote %} 2. {% data reusables.saml.assert-the-administrator-attribute %} -## Efetuar login e nomear a sua empresa +## Signing in and naming your enterprise -1. Siga as instruções no seu e-mail de boas-vindas para chegar à sua empresa. -2. Digite suas credenciais em "Alterar senha" e clique em **Alterar senha**. -3. Em "Que nome deseja dar à sua conta corporativa?", insira o nome da empresa e clique em **Salvar e continuar**. - ![Botão "Salvar e continuar" de nomeação de uma empresa](/assets/images/enterprise/configuration/ae-enterprise-configuration.png) +1. Follow the instructions in your welcome email to reach your enterprise. +2. Type your credentials under "Change password", then click **Change password**. +3. Under "What would you like your enterprise account to be named?", type the enterprise's name, then click **Save and continue**. + !["Save and continue" button for naming an enterprise](/assets/images/enterprise/configuration/ae-enterprise-configuration.png) -## Conectar o seu IdP à sua empresa +## Connecting your IdP to your enterprise -Para configurar a autenticação para {% data variables.product.product_name %}, você deve fornecer os detalhes do seu IdP SAML para {% data variables.product.product_name %}. {% data variables.product.company_short %} recomenda usar o Azure AD como seu IdP. Para obter mais informações, confira "[Como configurar a autenticação e o provisionamento com seu provedor de identidade](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)". +To configure authentication for {% data variables.product.product_name %}, you must provide {% data variables.product.product_name %} with the details for your SAML IdP. {% data variables.product.company_short %} recommends using Azure AD as your IdP. For more information, see "[Configuring authentication and provisioning with your identity provider](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)." -1. À direita de "Configurar seu provedor de identidade", clique em **Configurar**. - ![Botão "Configurar" para configuração do IdP](/assets/images/enterprise/configuration/ae-idp-configure.png) -1. Em "URL de logon", copie e cole a URL no seu IdP do SAML. - ![Campo de texto referente à URL de logon do IdP do SAML](/assets/images/enterprise/configuration/ae-idp-sign-on-url.png) -1. Em "Emissor", copie e cole a URL do emissor para o seu IdP do SAML. - ![Campo de texto referente à URL do emissor do IdP do SAML](/assets/images/enterprise/configuration/ae-idp-issuer-url.png) -1. Em "Certificado público, copie e cole o certificado público no seu IdP do SAML. - ![Campo de texto referente ao certificado público do IdP do SAML](/assets/images/enterprise/configuration/ae-idp-public-certificate.png) -1. Clique em **Testar configuração do SAML** para garantir que as informações inseridas estejam corretas. - ![Botão "Testar configuração do SAML"](/assets/images/enterprise/configuration/ae-test-saml-configuration.png) -1. Clique em **Salvar**. - ![Botão "Salvar" para configuração do IdP](/assets/images/enterprise/configuration/ae-save.png) +1. To the right of "Set up your identity provider", click **Configure**. + !["Configure" button for IdP configuration](/assets/images/enterprise/configuration/ae-idp-configure.png) +1. Under "Sign on URL", copy and paste the URL for your SAML IdP. + ![Text field for SAML IdP's sign-on URL](/assets/images/enterprise/configuration/ae-idp-sign-on-url.png) +1. Under "Issuer", copy and paste the issuer URL for your SAML IdP. + ![Text field for SAML IdP's issuer URL](/assets/images/enterprise/configuration/ae-idp-issuer-url.png) +1. Under "Public certificate", copy and paste the public certificate for your SAML IdP. + ![Text field for SAML IdP's public certificate](/assets/images/enterprise/configuration/ae-idp-public-certificate.png) +1. Click **Test SAML configuration** to ensure that the information you've entered is correct. + !["Test SAML configuration" button](/assets/images/enterprise/configuration/ae-test-saml-configuration.png) +1. Click **Save**. + !["Save" button for IdP configuration](/assets/images/enterprise/configuration/ae-save.png) -## Configurar as suas políticas empresariais +## Setting your enterprise policies -A configuração de políticas definirá limitações para o gerenciamento do repositório e da organização para a sua empresa. Elas podem ser reconfiguradas após o processo de inicialização. +Configuring policies will set limitations for repository and organization management for your enterprise. These can be reconfigured after the initialization process. -1. À direita de "Definir as políticas corporativas", clique em **Configurar**. - ![Botão "Configurar" para configuração de políticas](/assets/images/enterprise/configuration/ae-policies-configure.png) -2. Em "Permissões padrão de repositórios" use o menu suspenso e clique em um nível padrão de permissões para repositórios da sua empresa. Se uma pessoa tem várias possibilidades de acesso a uma organização, individualmente, por meio de uma equipe ou como integrante da organização, o nível de permissão mais alto substitui todos os níveis de permissão inferiores. Opcionalmente, para permitir que as organizações na sua empresa definam permissões de repositório padrão próprias, clique em **Sem política** - ![Menu suspenso de opções de permissões de repositório padrão](/assets/images/enterprise/configuration/ae-repository-permissions-menu.png) -3. Em "Criação de repositório", escolha se deseja permitir que os integrantes criem repositórios. Opcionalmente, para permitir que as organizações na empresa definam permissões, clique em **Sem política**. - ![Botão "Os membros podem criar repositórios" da configuração de políticas corporativas](/assets/images/enterprise/configuration/ae-repository-creation-permissions.png) -4. Na "Bifurcação do repositório", escolha se deseja permitir a bifurcação de repositórios privados ou internos. Opcionalmente, para permitir que as organizações na sua empresa definam permissões, clique em **Sem política** - ![Menu suspenso de opções de permissões de criação de forks no repositório](/assets/images/enterprise/configuration/ae-repository-forking-menu.png) -5. Em "Convites do repositório", escolha se os integrantes ou proprietários ou da organização podem convidar colaboradores para repositórios. Opcionalmente, para permitir que as organizações na sua empresa definam permissões, clique em **Sem política** - ![Menu suspenso de opções de permissões de convite no repositório](/assets/images/enterprise/configuration/ae-repository-invitations-menu.png) -6. Em "Visibilidade padrão do repositório", use o menu suspenso e clique na configuração de visibilidade padrão para novos repositórios. - ![Menu suspenso de opções de visibilidade do repositório padrão](/assets/images/enterprise/configuration/ae-repository-visibility-menu.png) -7. Em "Os usuários podem criar organizações", use o menu suspenso para habilitar ou desabilitar o acesso à criação da organização para os integrantes da empresa. - ![Menu suspenso de opções de permissão de criação de organização](/assets/images/enterprise/configuration/ae-organization-creation-permissions-menu.png) -8. Em "Pushes forçados", use o menu suspenso e escolha se deseja permitir ou bloquear pushes forçados. - ![Menu suspenso de opções de configuração de pushes forçados](/assets/images/enterprise/configuration/ae-force-pushes-configuration-menu.png) -9. Em "Acesso SSH ao Git", use o menu suspenso e escolha se deseja habilitar o acesso SSH ao Git para todos os repositórios da empresa. - ![Menu suspenso de opções de acesso SSH ao Git](/assets/images/enterprise/configuration/ae-git-ssh-access-menu.png) -10. Clique em **Salvar** - ![botão "Salvar" da configuração de políticas corporativas](/assets/images/enterprise/configuration/ae-save.png) -11. Opcionalmente, para redefinir todas as seleções, clique em "Redefinir para as políticas padrão". - ![Link para redefinir todas as políticas padrão](/assets/images/enterprise/configuration/ae-reset-default-options.png) +1. To the right of "Set your enterprise policies", click **Configure**. + !["Configure" button for policies configuration](/assets/images/enterprise/configuration/ae-policies-configure.png) +2. Under "Default Repository Permissions", use the drop-down menu and click a default permissions level for repositories in your enterprise. If a person has multiple avenues of access to an organization, either individually, through a team, or as an organization member, the highest permission level overrides any lower permission levels. Optionally, to allow organizations within your enterprise to set their default repository permissions, click **No policy** + ![Drop-down menu for default repository permissions options](/assets/images/enterprise/configuration/ae-repository-permissions-menu.png) +3. Under "Repository creation", choose whether you want to allow members to create repositories. Optionally, to allow organizations within your enterprise to set permissions, click **No policy**. + !["Members can create repositories" button for enterprise policies configuration](/assets/images/enterprise/configuration/ae-repository-creation-permissions.png) +4. Under "Repository forking", choose whether to allow forking of private and internal repositories. Optionally, to allow organizations within your enterprise to set permissions, click **No policy** + ![Drop-down menu for repository forking permissions options](/assets/images/enterprise/configuration/ae-repository-forking-menu.png) +5. Under "Repository invitations", choose whether members or organization owners can invite collaborators to repositories. Optionally, to allow organizations within your enterprise to set permissions, click **No policy** + ![Drop-down menu for repository invitation permissions options](/assets/images/enterprise/configuration/ae-repository-invitations-menu.png) +6. Under "Default repository visibility", use the drop-down menu and click the default visibility setting for new repositories. + ![Drop-down menu for default repository visibility options](/assets/images/enterprise/configuration/ae-repository-visibility-menu.png) +7. Under "Users can create organizations", use the drop-down menu to enable or disable organization creation access for members of the enterprise. + ![Drop-down menu for organization creation permissions options](/assets/images/enterprise/configuration/ae-organization-creation-permissions-menu.png) +8. Under "Force pushes", use the drop-down menu and choose whether to allow or block force pushes. + ![Drop-down menu for force pushes configuration options](/assets/images/enterprise/configuration/ae-force-pushes-configuration-menu.png) +9. Under "Git SSH access", use the drop-down menu and choose whether to enable Git SSH access for all repositories in the enterprise. + ![Drop-down menu for Git SSH access options](/assets/images/enterprise/configuration/ae-git-ssh-access-menu.png) +10. Click **Save** + !["Save" button for enterprise policies configuration](/assets/images/enterprise/configuration/ae-save.png) +11. Optionally, to reset all selections, click "Reset to default policies". + ![Link to reset all default policies](/assets/images/enterprise/configuration/ae-reset-default-options.png) -## Configurar seu contato de suporte interno +## Setting your internal support contact -Você pode configurar o método que os seus usuários usarão para entrar em contato com sua equipe de suporte interno. Isto pode ser reconfigurado após o processo de inicialização. +You can configure the method your users will use to contact your internal support team. This can be reconfigured after the initialization process. -1. À direita de "Contato de suporte interno", clique em **Configurar**. - ![Botão "Configurar" da configuração do contato de suporte interno](/assets/images/enterprise/configuration/ae-support-configure.png) -2. Em "Contato de suporte interno, selecione o método para os usuários da sua empresa contactar o suporte, por meio de um URL ou endereço de e-mail. Em seguida, digite as informações de contato de suporte. - ![Campo de texto referente à URL de contato de suporte interno](/assets/images/enterprise/configuration/ae-support-link-url.png) -3. Clique em **Salvar**. - ![Botão "Salvar" da configuração de contato de suporte da empresa](/assets/images/enterprise/configuration/ae-save.png) +1. To the right of "Internal support contact", click **Configure**. + !["Configure" button for internal support contact configuration](/assets/images/enterprise/configuration/ae-support-configure.png) +2. Under "Internal support contact", select the method for users of your enterprise to contact support, through a URL or an e-mail address. Then, type the support contact information. + ![Text field for internal support contact URL](/assets/images/enterprise/configuration/ae-support-link-url.png) +3. Click **Save**. + !["Save" button for enterprise support contact configuration](/assets/images/enterprise/configuration/ae-save.png) -## Definir as suas configurações de e-mail +## Setting your email settings -Uma vez inicializado, você poderá reconfigurar qualquer configuração após o processo de inicialização. Para obter mais informações, confira "[Como configurar o email para notificações](/admin/configuration/configuring-email-for-notifications)". +Once this is initialized, you can reconfigure any settings after the initialization process. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-email-for-notifications)." -1. À direita de "Definir configurações de email", clique em **Configurar**. - ![Botão "Configurar" da configuração de definições de email](/assets/images/enterprise/configuration/ae-email-configure.png) -2. Selecione **Habilitar email**. Isto habilitará e-mails de saída e de entrada. No entanto, para que o e-mail de entrada funcione, você também deverá definir as suas configurações de DNS. Para obter mais informações, confira "[Como definir as configurações de DNS e de firewall para permitir emails de entrada](/admin/configuration/configuring-email-for-notifications#configuring-dns-and-firewall-settings-to-allow-incoming-emails)". - ![Caixa de seleção "Habilitar" da definição das configurações de email](/assets/images/enterprise/configuration/ae-enable-email-configure.png) -3. Defina as suas configurações de servidor de e-mail: - - No campo **Endereço do servidor**, digite o endereço do servidor SMTP. - - No campo **Porta**, digite a porta que o servidor SMTP usa para enviar emails. - - No campo **Domínio**, digite o nome de domínio que o servidor SMTP enviará com a resposta HELO, se houver. - - No menu suspenso **Autenticação**, escolha o tipo de criptografia usado pelo servidor SMTP. - - No campo **Endereço de email no-reply**, digite o endereço de email a ser usado nos campos De e Para em todos os emails de notificação. +1. To the right of "Configure email settings", click **Configure**. + !["Configure" button for email settings configuration](/assets/images/enterprise/configuration/ae-email-configure.png) +2. Select **Enable email**. This will enable both outbound and inbound email, however, for inbound email to work you will also need to configure your DNS settings. For more information, see "[Configuring DNS and firewall + settings to allow incoming emails](/admin/configuration/configuring-email-for-notifications#configuring-dns-and-firewall-settings-to-allow-incoming-emails)." + !["Enable" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-enable-email-configure.png) +3. Complete your email server settings: + - In the **Server address** field, type the address of your SMTP server. + - In the **Port** field, type the port that your SMTP server uses to send email. + - In the **Domain** field, type the domain name that your SMTP server will send with a HELO response, if any. + - In the **Authentication** dropdown, choose the type of encryption used by your SMTP server. + - In the **No-reply email address** field, type the email address to use in the From and To fields for all notification emails. -4. Caso deseje descartar todos os emails recebidos destinados ao endereço de email no-reply, selecione **Descartar emails recebidos no endereço de email no-reply**. - ![Caixa de seleção "Descartar" da definição das configurações de email](/assets/images/enterprise/configuration/ae-discard-email.png) -5. Clique em **Configurações de email de teste**. - ![Botão "Configurações de email de teste" da definição das configurações de email](/assets/images/enterprise/configuration/ae-test-email.png) -6. Em "Enviar email de teste para", digite o endereço de email para o qual deseja enviar um email de teste e clique em **Enviar email de teste**. - ![Botão "Enviar email de teste" da definição de configurações de email](/assets/images/enterprise/configuration/ae-send-test-email.png) -7. Clique em **Salvar**. - ![Botão "Salvar" da configuração de contato de suporte da empresa](/assets/images/enterprise/configuration/ae-save.png) +4. If you want to discard all incoming emails that are addressed to the no-reply email address, select **Discard email addressed to the no-reply email address**. + !["Discard" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-discard-email.png) +5. Click **Test email settings**. + !["Test email settings" button for email settings configuration](/assets/images/enterprise/configuration/ae-test-email.png) +6. Under "Send test email to," type the email address where you want to send a test email, then click **Send test email**. + !["Send test email" button for email settings configuration](/assets/images/enterprise/configuration/ae-send-test-email.png) +7. Click **Save**. + !["Save" button for enterprise support contact configuration](/assets/images/enterprise/configuration/ae-save.png) diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md index 6367f73175..d288949214 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Gerenciando o GitHub Mobile para a sua empresa -intro: 'Você pode decidir se as pessoas podem usar o {% data variables.product.prodname_mobile %} para se conectar ao {% data variables.product.product_location %}.' +title: Managing GitHub Mobile for your enterprise +intro: 'You can decide whether people can use {% data variables.product.prodname_mobile %} to connect to {% data variables.location.product_location %}.' permissions: 'Enterprise owners can manage {% data variables.product.prodname_mobile %} for a {% data variables.product.product_name %} instance.' versions: ghes: '*' @@ -12,29 +12,29 @@ redirect_from: - /admin/configuration/configuring-your-enterprise/managing-github-for-mobile-for-your-enterprise - /admin/configuration/managing-github-for-mobile-for-your-enterprise shortTitle: Manage GitHub Mobile -ms.openlocfilehash: f46673c16611a7f1ced6d0476c6ad3d79807f6d9 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147062263' --- -## Sobre o {% data variables.product.prodname_mobile %} -O {% data variables.product.prodname_mobile %} permite que as pessoas façam a triagem, colaborem e gerenciem o trabalho no {% data variables.product.product_location %} em um dispositivo móvel após a autenticação bem-sucedida. {% data reusables.mobile.about-mobile %} Para obter mais informações, confira "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)". +## About {% data variables.product.prodname_mobile %} -Você pode permitir ou impedir que os membros corporativos usem o {% data variables.product.prodname_mobile %} para se autenticarem no {% data variables.product.product_location %} e acessar os dados da sua empresa. Por padrão, o {% data variables.product.prodname_mobile %} está {% ifversion ghes > 3.3 %} habilitado para pessoas que usam o {% data variables.product.product_location %}.{% else %} não está habilitado para pessoas que usam o {% data variables.product.product_location %}. Para permitir a conexão com a sua instância com o {% data variables.product.prodname_mobile %}, você precisa habilitar o recurso na instância.{% endif %} +{% data variables.product.prodname_mobile %} allows people to triage, collaborate, and manage work on {% data variables.location.product_location %} from a mobile device after successful authentication. {% data reusables.mobile.about-mobile %} For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)." -{% ifversion ghes < 3.6 %} {% note %} +You can allow or disallow people from using {% data variables.product.prodname_mobile %} to authenticate to {% data variables.location.product_location %} and access your instance's data. By default, {% data variables.product.prodname_mobile %} is{% ifversion ghes > 3.3 %} enabled for people who use {% data variables.location.product_location %}.{% else %} not enabled for people who use {% data variables.location.product_location %}. To allow connection to your instance with {% data variables.product.prodname_mobile %}, you must enable the feature for your instance.{% endif %} -**Observação:** se você fizer upgrade para o {% data variables.product.prodname_ghe_server %} 3.4.0 ou posterior e não tiver desabilitado nem habilitado o {% data variables.product.prodname_mobile %}, o {% data variables.product.prodname_mobile %} estará habilitado por padrão. Se você desabilitar ou habilitar o {% data variables.product.prodname_mobile %} na sua instância, sua preferência será preservada após o upgrade. Para obter mais informações sobre como fazer upgrade da sua instância, confira "[Como fazer upgrade do {% data variables.product.product_name %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)". +{% ifversion ghes < 3.6 %} +{% note %} -{% endnote %} {% endif %} +**Note:** If you upgrade to {% data variables.product.prodname_ghe_server %} 3.4.0 or later and have not previously disabled or enabled {% data variables.product.prodname_mobile %}, {% data variables.product.prodname_mobile %} will be enabled by default. If you previously disabled or enabled {% data variables.product.prodname_mobile %} for your instance, your preference will be preserved upon upgrade. For more information about upgrading your instance, see "[Upgrading {% data variables.product.product_name %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." -## Habilitar ou desabilitar {% data variables.product.prodname_mobile %} +{% endnote %} +{% endif %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.type-management-console-password %} -1. Na barra lateral esquerda, clique em **Mobile**. - !["Mobile" na barra lateral esquerda do console de gerenciamento do {% data variables.product.prodname_ghe_server %}](/assets/images/enterprise/management-console/click-mobile.png) -1. Em "GitHub Mobile", marque ou desmarque a opção **Habilitar o GitHub Mobile Apps**. - ![Caixa de seleção "Habilitar o GitHub Mobile Apps" no console de gerenciamento do {% data variables.product.prodname_ghe_server %}](/assets/images/enterprise/management-console/select-enable-github-mobile-apps.png) {% data reusables.enterprise_management_console.save-settings %} +## Enabling or disabling {% data variables.product.prodname_mobile %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.type-management-console-password %} +1. In the left sidebar, click **Mobile**. + !["Mobile" in the left sidebar for the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/click-mobile.png) +1. Under "GitHub Mobile", select or deselect **Enable GitHub Mobile Apps**. + ![Checkbox for "Enable GitHub Mobile Apps" in the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/select-enable-github-mobile-apps.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md index ea742e0fc5..7d3c7e3665 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md @@ -51,7 +51,7 @@ For more information on audit logging in general, see "[About the audit log for ## Reports -If you need to get information on the users, organizations, and repositories in {% data variables.product.product_location %}, you would ordinarily fetch JSON data through the [GitHub API](/rest). Unfortunately, the API may not provide all of the data that you want and it requires a bit of technical expertise to use. The site admin dashboard offers a **Reports** section as an alternative, making it easy for you to download CSV reports with most of the information that you are likely to need for users, organizations, and repositories. +If you need to get information on the users, organizations, and repositories in {% data variables.location.product_location %}, you would ordinarily fetch JSON data through the [GitHub API](/rest). Unfortunately, the API may not provide all of the data that you want and it requires a bit of technical expertise to use. The site admin dashboard offers a **Reports** section as an alternative, making it easy for you to download CSV reports with most of the information that you are likely to need for users, organizations, and repositories. Specifically, you can download CSV reports that list @@ -62,7 +62,7 @@ Specifically, you can download CSV reports that list - all organizations - all repositories -You can also access these reports programmatically via standard HTTP authentication with a site admin account. You must use a personal access token with the `site_admin` scope. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +You can also access these reports programmatically via standard HTTP authentication with a site admin account. You must use a {% data variables.product.pat_v1 %} with the `site_admin` scope. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." For example, here is how you would download the "all users" report using cURL: @@ -164,7 +164,7 @@ You can create a new index, or you can click on an existing index in the list to - Start a new index repair job. - Enable or disable index repair jobs. -A progress bar shows the current status of a repair job across background workers. The bar is the percentage difference of the repair offset with the highest record ID in the database. You can ignore the value shown in the progress bar after a repair job has completed. The progress bar shows the difference between the repair offset and the highest record ID in the database, and will decrease as more repositories are added to {% data variables.product.product_location %} even though those repositories are actually indexed. +A progress bar shows the current status of a repair job across background workers. The bar is the percentage difference of the repair offset with the highest record ID in the database. You can ignore the value shown in the progress bar after a repair job has completed. The progress bar shows the difference between the repair offset and the highest record ID in the database, and will decrease as more repositories are added to {% data variables.location.product_location %} even though those repositories are actually indexed. To minimize the effects on I/O performance and reduce the chances of operations timing out, run the repair job during off-peak hours. As the job reconciles the search index with database and Git repository data, one CPU will be used. Monitor your system's load averages and CPU usage with a utility like `top`. If you don't notice any significant increase in resource consumption, it should also be safe to run an index repair job during peak hours. @@ -177,7 +177,7 @@ This allows you to enable or disable both search and index operations on source {% endif %} ## Reserved logins -Certain words are reserved for internal use in {% data variables.product.product_location %}, which means that these words cannot be used as usernames. +Certain words are reserved for internal use in {% data variables.location.product_location %}, which means that these words cannot be used as usernames. For example, the following words are reserved, among others: @@ -216,7 +216,7 @@ Refer to this section of the site admin dashboard to manage organizations, peopl ## Repositories -This is a list of the repositories on {% data variables.product.product_location %}. You can click on a repository name and access functions for administering the repository. +This is a list of the repositories on {% data variables.location.product_location %}. You can click on a repository name and access functions for administering the repository. - [Blocking force pushes to a repository](/enterprise/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) - [Configuring {% data variables.large_files.product_name_long %}](/enterprise/admin/guides/installation/configuring-git-large-file-storage/#configuring-git-large-file-storage-for-an-individual-repository) @@ -224,21 +224,21 @@ This is a list of the repositories on {% data variables.product.product_location ## All users -Here you can see all of the users on {% data variables.product.product_location %}, and [initiate an SSH key audit](/enterprise/admin/guides/user-management/auditing-ssh-keys). +Here you can see all of the users on {% data variables.location.product_location %}, and [initiate an SSH key audit](/enterprise/admin/guides/user-management/auditing-ssh-keys). ## Site admins -Here you can see all of the administrators on {% data variables.product.product_location %}, and [initiate an SSH key audit](/enterprise/admin/guides/user-management/auditing-ssh-keys). +Here you can see all of the administrators on {% data variables.location.product_location %}, and [initiate an SSH key audit](/enterprise/admin/guides/user-management/auditing-ssh-keys). ## Dormant users {% ifversion ghes %} -Here you can see and [suspend](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users) all of the inactive users on {% data variables.product.product_location %}. A user account is considered to be inactive ("dormant") when it: +Here you can see and [suspend](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users) all of the inactive users on {% data variables.location.product_location %}. A user account is considered to be inactive ("dormant") when it: {% endif %} {% ifversion ghae %} -Here you can see and suspend all of the inactive users on {% data variables.product.product_location %}. A user account is considered to be inactive ("dormant") when it: +Here you can see and suspend all of the inactive users on {% data variables.location.product_location %}. A user account is considered to be inactive ("dormant") when it: {% endif %} -- Has existed for longer than the dormancy threshold that's set for {% data variables.product.product_location %}. +- Has existed for longer than the dormancy threshold that's set for {% data variables.location.product_location %}. - Has not generated any activity within that time period. - Is not a site administrator. @@ -246,4 +246,4 @@ Here you can see and suspend all of the inactive users on {% data variables.prod ## Suspended users -Here you can see all of the users who have been suspended on {% data variables.product.product_location %}, and [initiate an SSH key audit](/enterprise/admin/guides/user-management/auditing-ssh-keys). +Here you can see all of the users who have been suspended on {% data variables.location.product_location %}, and [initiate an SSH key audit](/enterprise/admin/guides/user-management/auditing-ssh-keys). diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md index 3327bd91ab..eca1544cea 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md @@ -1,6 +1,6 @@ --- -title: Solução de problemas relacionados a erros do TLS -intro: 'Se você tiver problemas relacionados ao TLS com seu dispositivo, veja o que fazer para resolvê-los.' +title: Troubleshooting TLS errors +intro: 'If you run into TLS issues with your appliance, you can take actions to resolve them.' redirect_from: - /enterprise/admin/articles/troubleshooting-ssl-errors - /enterprise/admin/categories/dns-ssl-and-subdomain-configuration @@ -19,74 +19,68 @@ topics: - Security - Troubleshooting shortTitle: Troubleshoot TLS errors -ms.openlocfilehash: 855737f89f0380333b1f37c26d512c889f2ee786 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147881248' --- -## Remover a frase secreta do arquivo de chave +## Removing the passphrase from your key file -Se você tiver uma máquina Linux com OpenSSL instalado, será possível remover a frase secreta. +If you have a Linux machine with OpenSSL installed, you can remove your passphrase. -1. Renomeie seu arquivo de chave original. +1. Rename your original key file. ```shell $ mv yourdomain.key yourdomain.key.orig ``` -2. Gere uma nova chave SSH sem frase secreta. +2. Generate a new key without a passphrase. ```shell $ openssl rsa -in yourdomain.key.orig -out yourdomain.key ``` -A senha da chave será solicitada quando você executar esse comando. +You'll be prompted for the key's passphrase when you run this command. -Para obter mais informações sobre o OpenSSL, confira a [documentação do OpenSSL](https://www.openssl.org/docs/). +For more information about OpenSSL, see [OpenSSL's documentation](https://www.openssl.org/docs/). -## Converter a chave ou o certificado TLS em formato PEM +## Converting your TLS certificate or key into PEM format -Se você tiver o OpenSSL instalado, converta sua chave no formato PEM usando o comando `openssl`. Por exemplo, você pode converter uma chave do formato DER para o formato PEM. +If you have OpenSSL installed, you can convert your key into PEM format by using the `openssl` command. For example, you can convert a key from DER format into PEM format. ```shell $ openssl rsa -in yourdomain.der -inform DER -out yourdomain.key -outform PEM ``` -Se não tiver, você pode usar a ferramenta SSL Converter para converter seu certificado em formato PEM. Para obter mais informações, confira a [documentação da ferramenta SSL Converter](https://www.sslshopper.com/ssl-converter.html). +Otherwise, you can use the SSL Converter tool to convert your certificate into the PEM format. For more information, see the [SSL Converter tool's documentation](https://www.sslshopper.com/ssl-converter.html). -## Instalação parada após upload de chave +## Unresponsive installation after uploading a key -Se o {% data variables.product.product_location %} não responder após o upload de uma chave TLS, [entre em contato com o Suporte do {% data variables.product.prodname_enterprise %}](https://enterprise.github.com/support) e forneça detalhes específicos, incluindo uma cópia do certificado TLS. Verifique se sua chave privada **não está** incluída. +If {% data variables.location.product_location %} is unresponsive after uploading an TLS key, please [contact {% data variables.product.prodname_enterprise %} Support](https://enterprise.github.com/support) with specific details, including a copy of your TLS certificate. Ensure that your private key **is not** included. -## Erros de validade de certificado +## Certificate validity errors -Se não for possível verificar a validade de um certificado TLS, clientes como navegadores da Web e Gits de linha de comando exibirão uma mensagem de erro. Isso costuma acontecer com certificados autoassinados e certificados de "raiz encadeada" emitidos a partir de um certificado raiz intermediário não reconhecido pelo cliente. +Clients such as web browsers and command-line Git will display an error message if they cannot verify the validity of an TLS certificate. This often occurs with self-signed certificates as well as "chained root" certificates issued from an intermediate root certificate that is not recognized by the client. -Se você estiver usando um certificado assinado por uma autoridade de certificação (CA), o arquivo de certificado que você carregar no {% data variables.product.prodname_ghe_server %} deverá incluir uma cadeia de certificados com o certificado raiz da autoridade certificada em questão. Para criar esse arquivo, concatene toda a sua cadeia de certificados (ou "pacote de certificados") até o fim, garantindo que o certificado principal com o nome de host seja o primeiro. Na maioria dos sistemas, fazer isso é possível com um comando semelhante ao seguinte: +If you are using a certificate signed by a certificate authority (CA), the certificate file that you upload to {% data variables.product.prodname_ghe_server %} must include a certificate chain with that CA's root certificate. To create such a file, concatenate your entire certificate chain (or "certificate bundle") onto the end of your certificate, ensuring that the principal certificate with your hostname comes first. On most systems you can do this with a command similar to: ```shell $ cat yourdomain.com.crt bundle-certificates.crt > yourdomain.combined.crt ``` -Você deve conseguir baixar um pacote de certificados (por exemplo, `bundle-certificates.crt`) da autoridade de certificação ou do fornecedor de TLS. +You should be able to download a certificate bundle (for example, `bundle-certificates.crt`) from your certificate authority or TLS vendor. -## Instalar certificados raiz de autoridade de certificação (CA) autoassinada ou não confiável +## Installing self-signed or untrusted certificate authority (CA) root certificates -Se o seu appliance do {% data variables.product.prodname_ghe_server %} interage na rede com outras máquinas que usam certificados autoassinados ou não confiáveis, será necessário importar o certificado raiz da CA de assinatura para o armazenamento geral do sistema a fim de acessar esses sistemas por HTTPS. +If your {% data variables.product.prodname_ghe_server %} appliance interacts with other machines on your network that use a self-signed or untrusted certificate, you will need to import the signing CA's root certificate into the system-wide certificate store in order to access those systems over HTTPS. -1. Obtenha o certificado raiz da autoridade de certificação local e verifique se ele está no formato PEM. -2. Copie o arquivo para o seu appliance do {% data variables.product.prodname_ghe_server %} via SSH como usuário "admin" na porta 122. +1. Obtain the CA's root certificate from your local certificate authority and ensure it is in PEM format. +2. Copy the file to your {% data variables.product.prodname_ghe_server %} appliance over SSH as the "admin" user on port 122. ```shell $ scp -P 122 rootCA.crt admin@HOSTNAME:/home/admin ``` -3. Conecte-se ao shell administrativo do {% data variables.product.prodname_ghe_server %} via SSH como usuário "admin" na porta 122. +3. Connect to the {% data variables.product.prodname_ghe_server %} administrative shell over SSH as the "admin" user on port 122. ```shell $ ssh -p 122 admin@HOSTNAME ``` -4. Importe o certificado no armazenamento geral do sistema. +4. Import the certificate into the system-wide certificate store. ```shell $ ghe-ssl-ca-certificate-install -c rootCA.crt ``` -## Atualizar um certificado TLS +## Updating a TLS certificate -Com o utilitário de linha de comando `ghe-ssl-certificate-setup`, é possível gerar um certificado autoassinado ou atualizar um certificado TLS existente para o {% data variables.product.product_location %}. Para obter mais informações, confira "[Utilitários de linha de comando](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-ssl-ca-certificate-setup)". +You can generate a new self-signed certificate or update an existing TLS certificate for {% data variables.location.product_location %} with the `ghe-ssl-certificate-setup` command line utility. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-ssl-ca-certificate-setup)." diff --git a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md index 74a3f48255..c2f149719e 100644 --- a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md +++ b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md @@ -1,6 +1,6 @@ --- -title: Acessar o painel de monitoramento -intro: 'O {% data variables.product.prodname_ghe_server %} inclui um painel de monitoramento baseado na web que exibe os dados de histórico do seu appliance do {% data variables.product.prodname_ghe_server %}, como uso de CPU e armazenamento, tempos de resposta de aplicativos e autenticação, e informações gerais sobre a integridade do sistema.' +title: Accessing the monitor dashboard +intro: '{% data variables.product.prodname_ghe_server %} includes a web-based monitoring dashboard that displays historical data about your {% data variables.product.prodname_ghe_server %} appliance, such as CPU and storage usage, application and authentication response times, and general system health.' redirect_from: - /enterprise/admin/installation/accessing-the-monitor-dashboard - /enterprise/admin/enterprise-management/accessing-the-monitor-dashboard @@ -15,33 +15,28 @@ topics: - Monitoring - Performance shortTitle: Access the monitor dashboard -ms.openlocfilehash: b529369813635a8cafe5f7c7ac6fc04af39001f5 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146332365' --- -## Acessar o painel de monitoramento +## Accessing the monitor dashboard -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} -2. Na parte superior da página, clique em **Monitoramento**. -![Link para o Painel de monitoramento](/assets/images/enterprise/management-console/monitor-dash-link.png) +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +2. At the top of the page, click **Monitor**. +![The Monitor Dashboard link](/assets/images/enterprise/management-console/monitor-dash-link.png) -## Resolver problemas comuns de alocação de recursos no appliance +## Troubleshooting common resource allocation problems on your appliance {% note %} -**Observação**: fazer sondagens regularmente no {% data variables.product.product_location %} com integração contínua (CI) ou servidores de build poderá causar um ataque de negação de serviço e gerar problemas. Portanto, recomendamos o uso de webhooks para fazer push das atualizações. Para obter mais informações, confira "[Sobre os webhooks](/enterprise/user/articles/about-webhooks/)". +**Note**: Because regularly polling {% data variables.location.product_location %} with continuous integration (CI) or build servers can effectively cause a denial of service attack that results in problems, we recommend using webhooks to push updates. For more information, see "[About webhooks](/enterprise/user/articles/about-webhooks/)". {% endnote %} -Use o painel de monitoramento para se manter a par da integridade dos recursos do seu appliance e decidir como corrigir os problemas de uso excessivo. +Use the monitor dashboard to stay informed on your appliance's resource health and make decisions on how to fix high usage issues. -| Problema | Possíveis causas | Recomendações | +| Problem | Possible cause(s) | Recommendations | | -------- | ----------------- | --------------- | -| Alto uso da CPU | Contenção da VM por outros serviços ou programas executados no mesmo host | Se possível, reconfigure outros serviços ou programas para usar menos recursos de CPU. Para aumentar o total de recursos de CPU para a VM, confira "[Como aumentar os recursos de CPU ou memória](/enterprise/admin/guides/installation/increasing-cpu-or-memory-resources/)". | -| Alto uso da memória | Contenção da VM por outros serviços ou programas executados no mesmo host | Se possível, reconfigure outros serviços ou programas para usar menos memória. Para aumentar a memória total disponível na VM, confira "[Como aumentar os recursos de CPU ou memória](/enterprise/admin/guides/installation/increasing-cpu-or-memory-resources/)". | -| Pouco espaço em disco | Consumo do espaço em disco por arquivos grandes binários ou de log | Se possível, hospede os arquivos binários grandes em outro servidor e compacte ou arquive os arquivos de log. Se necessário, aumente o espaço em disco na VM seguindo as etapas para sua plataforma em "[Aumentar a capacidade de armazenamento](/enterprise/admin/guides/installation/increasing-storage-capacity/)". | -| Tempos de resposta maiores do que o comum | Costuma ser causado por um dos problemas acima | Identifique e corrija os problema subjacentes. Se os tempos de resposta continuarem altos, entre em contato com o {% data variables.contact.contact_ent_support %}. | -| Altos índices de erro | Problemas de software | Entre em contato com o {% data variables.contact.contact_ent_support %} e inclua seu pacote de suporte. Para obter mais informações, confira "[Como fornecer dados para o Suporte do {% data variables.product.prodname_enterprise %}](/enterprise/{{ currentVersion}}/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-support-bundles)". | +| High CPU usage | VM contention from other services or programs running on the same host | If possible, reconfigure other services or programs to use fewer CPU resources. To increase total CPU resources for the VM, see "[Increasing CPU or memory resources](/enterprise/admin/guides/installation/increasing-cpu-or-memory-resources/)." | +| High memory usage | VM contention from other services or programs running on the same host | If possible, reconfigure other services or programs to use less memory. To increase the total memory available on the VM, see "[Increasing CPU or memory resources](/enterprise/admin/guides/installation/increasing-cpu-or-memory-resources/)." | +| Low disk space availability | Large binaries or log files consuming disk space | If possible, host large binaries on a separate server, and compress or archive log files. If necessary, increase disk space on the VM by following the steps for your platform in "[Increasing storage capacity](/enterprise/admin/guides/installation/increasing-storage-capacity/)." | +| Higher than usual response times | Often caused by one of the above issues | Identify and fix the underlying issues. If response times remain high, contact {% data variables.contact.contact_ent_support %}. | +| Elevated error rates | Software issues | Contact {% data variables.contact.contact_ent_support %} and include your support bundle. For more information, see "[Providing data to {% data variables.product.prodname_enterprise %} Support](/enterprise/{{ currentVersion}}/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-support-bundles)." | diff --git a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md index d48f13ef6c..0c216af47e 100644 --- a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md +++ b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md @@ -1,6 +1,6 @@ --- -title: Configurar collectd -intro: 'O {% data variables.product.prodname_enterprise %} pode coletar dados com `collectd` e enviá-los a um servidor externo `collectd`. Reunimos um conjunto padrão de dados e outras métricas, como uso de CPU, consumo de memória e disco, tráfego e erros da interface de rede e carga geral da VM.' +title: Configuring collectd +intro: '{% data variables.product.prodname_enterprise %} can gather data with `collectd` and send it to an external `collectd` server. Among other metrics, we gather a standard set of data such as CPU utilization, memory and disk consumption, network interface traffic and errors, and the VM''s overall load.' redirect_from: - /enterprise/admin/installation/configuring-collectd - /enterprise/admin/articles/configuring-collectd @@ -15,21 +15,15 @@ topics: - Infrastructure - Monitoring - Performance -ms.openlocfilehash: f63eb940681be3131a470a7786e134550fdba152 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145095928' --- -## Configurar um servidor externo do `collectd` +## Set up an external `collectd` server -Se você ainda não tiver configurado um servidor externo do `collectd`, precisará fazer isso antes de habilitar o encaminhamento do `collectd` no {% data variables.product.product_location %}. O servidor do `collectd` precisa executar o `collectd` versão 5.x ou superior. +If you haven't already set up an external `collectd` server, you will need to do so before enabling `collectd` forwarding on {% data variables.location.product_location %}. Your `collectd` server must be running `collectd` version 5.x or higher. -1. Faça logon no servidor do `collectd`. -2. Crie ou edite o arquivo de configuração `collectd` para carregar o plug-in de rede e preencher as diretivas de servidor e porta com os valores adequados. Na maioria das distribuições, isso está localizado em `/etc/collectd/collectd.conf` +1. Log into your `collectd` server. +2. Create or edit the `collectd` configuration file to load the network plugin and populate the server and port directives with the proper values. On most distributions, this is located at `/etc/collectd/collectd.conf` -Um exemplo de *collectd.conf* para executar um servidor do `collectd`: +An example *collectd.conf* to run a `collectd` server: LoadPlugin network ... @@ -38,32 +32,34 @@ Um exemplo de *collectd.conf* para executar um servidor do `collectd`: Listen "0.0.0.0" "25826" -## Habilitar o encaminhamento collectd no {% data variables.product.prodname_enterprise %} +## Enable collectd forwarding on {% data variables.product.prodname_enterprise %} -Por padrão, o encaminhamento do `collectd` está desabilitado no {% data variables.product.prodname_enterprise %}. Siga as etapas abaixo para habilitar e configurar o encaminhamento do `collectd`: +By default, `collectd` forwarding is disabled on {% data variables.product.prodname_enterprise %}. Follow the steps below to enable and configure `collectd` forwarding: -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} -1. Abaixo das configurações de encaminhamento de log, selecione **Habilitar encaminhamento do collectd**. -1. No campo **Endereço do servidor**, digite o endereço do servidor do `collectd` para o qual deseja encaminhar as estatísticas do dispositivo do {% data variables.product.prodname_enterprise %}. -1. No campo **Porta**, digite a porta usada para se conectar ao servidor do `collectd`. (o padrão é 25826). -1. No menu suspenso **Configuração de criptografia**, selecione o nível de segurança de comunicações com o servidor do `collectd`. (Nenhum, pacotes assinados ou pacotes criptografados).{% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +1. Below the log forwarding settings, select **Enable collectd forwarding**. +1. In the **Server address** field, type the address of the `collectd` server to which you'd like to forward {% data variables.product.prodname_enterprise %} appliance statistics. +1. In the **Port** field, type the port used to connect to the `collectd` server. (Defaults to 25826) +1. In the **Cryptographic setup** dropdown menu, select the security level of communications with the `collectd` server. (None, signed packets, or encrypted packets.) +{% data reusables.enterprise_management_console.save-settings %} -## Como exportar os dados do collectd com `ghe-export-graphs` +## Exporting collectd data with `ghe-export-graphs` -A ferramenta de linha de comando `ghe-export-graphs` exportará os dados que o `collectd` armazena em bancos de dados RRD. Esse comando transforma os dados em XML e os exporta em um só tarball (`.tgz`). +The command-line tool `ghe-export-graphs` will export the data that `collectd` stores in RRD databases. This command turns the data into XML and exports it into a single tarball (`.tgz`). -Seu uso principal é fornecer à equipe do {% data variables.contact.contact_ent_support %} dados sobre o desempenho de uma VM sem que seja necessário baixar um pacote de suporte completo. Ele não deve ser incluído nas exportações de backup regulares e não há contrapartida de importação. Se você entrar em contato com o {% data variables.contact.contact_ent_support %} para fins de solução de problemas, esses dados podem ser solicitados. +Its primary use is to provide the {% data variables.contact.contact_ent_support %} team with data about a VM's performance, without the need for downloading a full Support Bundle. It shouldn't be included in your regular backup exports and there is no import counterpart. If you contact {% data variables.contact.contact_ent_support %}, we may ask for this data to assist with troubleshooting. -### Uso +### Usage ```shell ssh -p 122 admin@[hostname] -- 'ghe-export-graphs' && scp -P 122 admin@[hostname]:~/graphs.tar.gz . ``` -## Solução de problemas +## Troubleshooting -### Central do servidor collectd não recebe dados +### Central collectd server receives no data -O {% data variables.product.prodname_enterprise %} é fornecido com o `collectd` versão 5.x. O `collectd` 5.x não é compatível com versões anteriores da série de versões 4.x. Seu servidor central do `collectd` precisa ter, no mínimo, a versão 5.x para aceitar dados enviados do {% data variables.product.product_location %}. +{% data variables.product.prodname_enterprise %} ships with `collectd` version 5.x. `collectd` 5.x is not backwards compatible with the 4.x release series. Your central `collectd` server needs to be at least version 5.x to accept data sent from {% data variables.location.product_location %}. -Em caso de dúvidas ou perguntas, entre em contato com o {% data variables.contact.contact_ent_support %}. +For help with further questions or issues, contact {% data variables.contact.contact_ent_support %}. diff --git a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md index adccfd3b47..436c8127ba 100644 --- a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Gerando uma verificação de integridade para sua empresa -intro: 'Você pode obter informações sobre integridade geral e do Git e solicitações de API de {% data variables.product.product_location %} gerando uma verificação de integridade.' +title: Generating a Health Check for your enterprise +intro: 'You can gain insight into the general health and Git and API requests of {% data variables.location.product_location %} by generating a Health Check.' versions: ghes: '*' type: how_to @@ -11,53 +11,48 @@ topics: - Monitoring - Performance product: '{% data reusables.gated-features.generated-health-checks %}' -ms.openlocfilehash: f02fc61f050fc01a69f9fafe2dcdc95d91322dfa -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146460018' --- + {% note %} -**Observação:** atualmente, a geração de uma verificação de integridade está em versão beta no {% data variables.product.prodname_ghe_server %} e sujeita a alterações. +**Note:** Generating a Health Check is currently in beta for {% data variables.product.prodname_ghe_server %} and subject to change. {% endnote %} -## Sobre as verificações de integridade geradas +## About generated Health Checks -Você pode criar um pacote de suporte para {% data variables.product.product_location %} que contém um monte de dados, como diagnósticos e arquivos de registro. Para ajudar a analisar e interpretar esses dados, você pode gerar uma verificação de integridade. Para obter mais informações sobre os pacotes de suporte, confira "[Como fornecer dados para o {% data variables.contact.github_support %}](/support/contacting-github-support/providing-data-to-github-support#creating-and-sharing-support-bundles)". +You can create a support bundle for {% data variables.location.product_location %} that contains a lot of data, such as diagnostics and log files. To help analyze and interpret this data, you can generate a Health Check. For more information about support bundles, see "[Providing data to {% data variables.contact.github_support %}](/support/contacting-github-support/providing-data-to-github-support#creating-and-sharing-support-bundles)." -Uma verificação de integridade fornece as seguintes informações sobre {% data variables.product.product_location %}. -- Insights sobre a integridade geral de {% data variables.product.product_location %}, como o status de atualização, armazenamento e o consumo da estação da licença -- Uma seção de segurança que foca no isolamento do subdomínio e autenticação do usuário -- Análise de solicitações do Git, com detalhes sobre repositórios mais movimentados e usuários do Git -- Análise das solicitações de API, incluindo os tempos mais movimentados, pontos de extremidade mais solicitados e as chamadas mais ativas +A Health Check provides the following information about {% data variables.location.product_location %}. +- Insights into the general health of {% data variables.location.product_location %}, such as upgrade status, storage, and license seat consumption +- A security section, which focuses on subdomain isolation and user authentication +- Analysis of Git requests, with details about the busiest repositories and Git users +- Analysis of API requests, including the busiest times, most frequently requested endpoints, and most active callers -Se você quiser gerar uma Verificação de Integridade para o {% data variables.product.prodname_ghe_cloud %}, entre em contato com o {% data variables.contact.github_support %}. Para obter mais informações, confira "[Como criar um tíquete de suporte](/support/contacting-github-support/creating-a-support-ticket)". +If you want to generate a Health Check for {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.github_support %}. For more information, see "[Creating a support ticket](/support/contacting-github-support/creating-a-support-ticket)." -## Gerando uma verificação de integridade +## Generating a Health Check -Antes de gerar uma verificação de integridade, você deve criar um pacote de suporte. Para obter mais informações, confira "[Como fornecer dados para o {% data variables.contact.github_support %}](/support/contacting-github-support/providing-data-to-github-support#creating-and-sharing-support-bundles)". +Before you can generate a Health Check, you must create a support bundle. For more information, see "[Providing data to {% data variables.contact.github_support %}](/support/contacting-github-support/providing-data-to-github-support#creating-and-sharing-support-bundles)." -1. Navegue até o [{% data variables.contact.support_portal %}](https://support.github.com/). -2. No canto superior direito da página, clique em **Premium**. +1. Navigate to the [{% data variables.contact.support_portal %}](https://support.github.com/). +2. In the upper-right corner of the page, click **Premium**. - ![Captura de tela do link "Premium" no cabeçalho Portal de Suporte do GitHub.](/assets/images/enterprise/support/support-portal-header-premium.png) + ![Screenshot of the "Premium" link in the GitHub Support Portal header.](/assets/images/enterprise/support/support-portal-header-premium.png) -3. À direita de **Verificações de Integridade**, clique em **Solicitar Verificação de Integridade**. +3. To the right of **Health Checks**, click **Request Health Check**. - ![Captura de tela do botão "Solicitar Verificação de Integridade".](/assets/images/enterprise/support/support-portal-request-health-check.png) + ![Screenshot of the "Request Health Check" button.](/assets/images/enterprise/support/support-portal-request-health-check.png) -4. Em "Selecionar uma conta corporativa", selecione o menu suspenso e clique em uma conta empresarial. +4. Under "Select an enterprise account", select the dropdown menu and click an enterprise account. - ![Captura de tela do menu suspenso "Conta corporativa".](/assets/images/enterprise/support/health-check-dialog-ea.png) + ![Screenshot of the "enterprise account" dropdown menu.](/assets/images/enterprise/support/health-check-dialog-ea.png) -5. Em "Carregar um pacote de suporte", clique em **Escolher Arquivo** e escolha um arquivo para carregá-lo. Em seguida, clique em **Solicitar Verificação de Integridade**. +5. Under "Upload a support bundle", click **Chose File** and choose a file to upload. Then, click **Request Health Check**. - ![Captura de tela dos botões "Escolher arquivo" e "Solicitar Verificação de Integridade".](/assets/images/enterprise/support/health-check-dialog-choose-file.png) + ![Screenshot of the "Choose file" and "Request Health Check" buttons.](/assets/images/enterprise/support/health-check-dialog-choose-file.png) -Após solicitar uma verificação de integridade, será agendado um trabalho para gerar a verificação de integridade. Após várias horas em um dia, a verificação de saúde gerada aparecerá na seção "Verificação de integridade" do {% data variables.contact.support_portal %}. +After you request a Health Check, a job is scheduled to generate the Health Check. After several hours to one day, the generated Health Check will appear in the "Health Checks" section of the {% data variables.contact.support_portal %}. -![Captura de tela da seção Verificações de Integridadedo {% data variables.contact.support_portal %}.](/assets/images/enterprise/support/support-portal-health-checks-section.png) +![Screenshot of the Health Checks section of the {% data variables.contact.support_portal %}.](/assets/images/enterprise/support/support-portal-health-checks-section.png) diff --git a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/index.md b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/index.md index ea87bb30b4..fb441b33e9 100644 --- a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/index.md +++ b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/index.md @@ -1,6 +1,6 @@ --- -title: Monitorar seu dispositivo -intro: 'Com o aumento do uso do {% data variables.product.product_location %} ao longo do tempo, a utilização de recursos do sistema, como CPU, memória e armazenamento, também aumenta. Você pode configurar o monitoramento e os alertas para identificar os possíveis problemas antes que eles impactem negativamente o desempenho ou a disponibilidade do aplicativo.' +title: Monitoring your appliance +intro: 'As use of {% data variables.location.product_location %} increases over time, the utilization of system resources, like CPU, memory, and storage will also increase. You can configure monitoring and alerting so that you''re aware of potential issues before they become critical enough to negatively impact application performance or availability.' redirect_from: - /enterprise/admin/guides/installation/system-resource-monitoring-and-alerting - /enterprise/admin/guides/installation/monitoring-your-github-enterprise-appliance @@ -18,11 +18,5 @@ children: - /monitoring-using-snmp - /about-system-logs - /generating-a-health-check-for-your-enterprise -ms.openlocfilehash: 3232d21371c2ad18ff8a4ebc8dcf7ea603d152ac -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145094989' --- diff --git a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md index ccd8efcab0..9c3f478189 100644 --- a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md +++ b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md @@ -1,6 +1,6 @@ --- -title: Monitorar usando SNMP -intro: 'O {% data variables.product.prodname_enterprise %} fornece dados sobre o uso de disco, CPU, memória e muito mais no SNMP.' +title: Monitoring using SNMP +intro: '{% data variables.product.prodname_enterprise %} provides data on disk usage, CPU utilization, memory usage, and more over SNMP.' redirect_from: - /enterprise/admin/installation/monitoring-using-snmp - /enterprise/admin/articles/monitoring-using-snmp @@ -14,104 +14,108 @@ topics: - Infrastructure - Monitoring - Performance -ms.openlocfilehash: 0f156d2939cbc83e3b0a72bbc1cbaf72f0c886d7 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145179149' --- -O SNMP é um padrão comum para monitorar dispositivos em uma rede. Recomendamos expressamente habilitar o SNMP para que você possa monitorar a integridade do {% data variables.product.product_location %} e saber quando adicionar mais memória, armazenamento ou potência do processador ao computador host. +SNMP is a common standard for monitoring devices over a network. We strongly recommend enabling SNMP so you can monitor the health of {% data variables.location.product_location %} and know when to add more memory, storage, or processor power to the host machine. -O {% data variables.product.prodname_enterprise %} tem uma instalação SNMP padrão, ou seja, você pode aproveitar os [vários plug-ins](https://www.monitoring-plugins.org/doc/man/check_snmp.html) disponíveis para o Nagios ou para qualquer outro sistema de monitoramento. +{% data variables.product.prodname_enterprise %} has a standard SNMP installation, so you can take advantage of the [many plugins](https://www.monitoring-plugins.org/doc/man/check_snmp.html) available for Nagios or for any other monitoring system. -## Configurar SMTP v2c +## Configuring SNMP v2c -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.access-monitoring %} {% data reusables.enterprise_management_console.enable-snmp %} -4. No campo **Cadeia de caracteres da comunidade**, insira uma nova cadeia de caracteres da comunidade. Se ele for deixado em branco, `public` será usado como padrão. -![Campo usado para adicionar a cadeia de caracteres da comunidade](/assets/images/enterprise/management-console/community-string.png) {% data reusables.enterprise_management_console.save-settings %} -5. Teste a configuração SNMP executando o seguinte comando em uma estação de trabalho separada com suporte a SNMP na rede: +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.access-monitoring %} +{% data reusables.enterprise_management_console.enable-snmp %} +4. In the **Community string** field, enter a new community string. If left blank, this defaults to `public`. +![Field to add the community string](/assets/images/enterprise/management-console/community-string.png) +{% data reusables.enterprise_management_console.save-settings %} +5. Test your SNMP configuration by running the following command on a separate workstation with SNMP support in your network: ```shell # community-string is your community string # hostname is the IP or domain of your Enterprise instance - $ snmpget -v 2c -c community-string -O e hostname hrSystemDate.0 + $ snmpget -v 2c -c COMMUNITY-STRING -O e HOSTNAME hrSystemDate.0 ``` -Isso retornará a hora do sistema no host do {% data variables.product.product_location %}. +This should return the system time on {% data variables.location.product_location %} host. -## Segurança baseada no usuário +## User-based security -Se habilitar o SNMP v3, você poderá aproveitar o aumento da segurança baseada no usuário por meio do User Security Model (USM). É possível especificar um nível de segurança para cada usuário: -- `noAuthNoPriv`: esse nível de segurança não fornece autenticação nem privacidade. -- `authNoPriv`: esse nível de segurança fornece autenticação, mas sem privacidade. Para consultar o appliance, você precisará de nome de usuário e senha (com pelo menos oito caracteres). As informações são enviadas sem criptografia, de modo semelhante ao SNMPv2. O protocolo de autenticação pode ser MD5 ou SHA, e o padrão é SHA. -- `authPriv`: esse nível de segurança fornece autenticação com privacidade. A autenticação (com senha de no mínimo oito caracteres) é necessária, e as respostas são criptografadas. Não é necessário usar uma senha de privacidade, mas, se houver, ela deve ter no mínimo oito caracteres. Se não houver senha de privacidade, a senha de autenticação será usada. O protocolo de privacidade pode ser DES ou AES, e o padrão é AES. +If you enable SNMP v3, you can take advantage of increased user based security through the User Security Model (USM). For each unique user, you can specify a security level: +- `noAuthNoPriv`: This security level provides no authentication and no privacy. +- `authNoPriv`: This security level provides authentication but no privacy. To query the appliance you'll need a username and password (that must be at least eight characters long). Information is sent without encryption, similar to SNMPv2. The authentication protocol can be either MD5 or SHA and defaults to SHA. +- `authPriv`: This security level provides authentication with privacy. Authentication, including a minimum eight-character authentication password, is required and responses are encrypted. A privacy password is not required, but if provided it must be at least eight characters long. If a privacy password isn't provided, the authentication password is used. The privacy protocol can be either DES or AES and defaults to AES. -## Configurar usuários para o SNMP v3 +## Configuring users for SNMP v3 -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.access-monitoring %} {% data reusables.enterprise_management_console.enable-snmp %} -4. Selecione **SNMP v3**. -![Botão usado para habilitar o SNMP v3](/assets/images/enterprise/management-console/enable-snmpv3.png) -5. Em "Username" (Nome de usuário), digite o nome exclusivo do seu usuário SNMP v3. -![Campo usado para digitar o nome de usuário do SNMP v3](/assets/images/enterprise/management-console/snmpv3-username.png) -6. No menu suspenso **Nível de segurança**, clique no nível de segurança do seu usuário do SNMP v3. -![Menu suspenso para o nível de segurança do usuário do SNMP v3](/assets/images/enterprise/management-console/snmpv3-securitylevel.png) -7. Para usuários do SNMP v3 com o nível de segurança `authnopriv`: ![Configurações para o nível de segurança authnopriv](/assets/images/enterprise/management-console/snmpv3-authnopriv.png) +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.access-monitoring %} +{% data reusables.enterprise_management_console.enable-snmp %} +4. Select **SNMP v3**. +![Button to enable SNMP v3](/assets/images/enterprise/management-console/enable-snmpv3.png) +5. In "Username", type the unique username of your SNMP v3 user. +![Field to type the SNMP v3 username](/assets/images/enterprise/management-console/snmpv3-username.png) +6. In the **Security Level** dropdown menu, click the security level for your SNMP v3 user. +![Dropdown menu for the SNMP v3 user's security level](/assets/images/enterprise/management-console/snmpv3-securitylevel.png) +7. For SNMP v3 users with the `authnopriv` security level: + ![Settings for the authnopriv security level](/assets/images/enterprise/management-console/snmpv3-authnopriv.png) - {% data reusables.enterprise_management_console.authentication-password %} - {% data reusables.enterprise_management_console.authentication-protocol %} -8. Para os usuários do SNMP v3 com o nível de segurança `authpriv`: ![Configurações para o nível de segurança authpriv](/assets/images/enterprise/management-console/snmpv3-authpriv.png) +8. For SNMP v3 users with the `authpriv` security level: + ![Settings for the authpriv security level](/assets/images/enterprise/management-console/snmpv3-authpriv.png) - {% data reusables.enterprise_management_console.authentication-password %} - {% data reusables.enterprise_management_console.authentication-protocol %} - - Como alternativa, em "Privacy password" (senha de privacidade), digite a senha de privacidade. - - No lado direito de "Senha de privacidade", no menu suspenso **Protocolo**, clique no protocolo de autenticação que deseja usar. -9. Clique em **Adicionar usuário**. -![Botão usado para adicionar o usuário do SNMP v3](/assets/images/enterprise/management-console/snmpv3-adduser.png) {% data reusables.enterprise_management_console.save-settings %} + - Optionally, in "Privacy password", type the privacy password. + - On the right side of "Privacy password", in the **Protocol** dropdown menu, click the privacy protocol method you want to use. +9. Click **Add user**. +![Button to add SNMP v3 user](/assets/images/enterprise/management-console/snmpv3-adduser.png) +{% data reusables.enterprise_management_console.save-settings %} -#### Consultar dados SNMP +#### Querying SNMP data -As informações de hardware e software do appliance estão disponíveis no SNMP v3. Devido à falta de criptografia e privacidade para os níveis de segurança `noAuthNoPriv` e `authNoPriv`, excluímos a tabela `hrSWRun` (1.3.6.1.2.1.25.4) dos relatórios resultantes do SNMP. Incluímos essa tabela se você usa o nível de segurança `authPriv`. Para obter mais informações, confira a "[Documentação de referência de OID](https://oidref.com/1.3.6.1.2.1.25.4)". +Both hardware and software-level information about your appliance is available with SNMP v3. Due to the lack of encryption and privacy for the `noAuthNoPriv` and `authNoPriv` security levels, we exclude the `hrSWRun` table (1.3.6.1.2.1.25.4) from the resulting SNMP reports. We include this table if you're using the `authPriv` security level. For more information, see the "[OID reference documentation](https://oidref.com/1.3.6.1.2.1.25.4)." -Com o SNMP v2c, ficam disponíveis somente as informações em nível de hardware. Os aplicativos e serviços no {% data variables.product.prodname_enterprise %} não têm OIDs configurados para reportar métricas. Vários MIBs estão disponíveis, que você pode ver executando `snmpwalk` em uma estação de trabalho separada com suporte a SNMP na sua rede: +With SNMP v2c, only hardware-level information about your appliance is available. The applications and services within {% data variables.product.prodname_enterprise %} do not have OIDs configured to report metrics. Several MIBs are available, which you can see by running `snmpwalk` on a separate workstation with SNMP support in your network: ```shell # community-string is your community string # hostname is the IP or domain of your Enterprise instance -$ snmpwalk -v 2c -c community-string -O e hostname +$ snmpwalk -v 2c -c COMMUNITY-STRING -O e HOSTNAME ``` -Dos MIBs disponíveis para o SNMP, o mais útil é `HOST-RESOURCES-MIB` (1.3.6.1.2.1.25). Consulte a tabela a seguir para ver objetos importantes dessa MIB: +Of the available MIBs for SNMP, the most useful is `HOST-RESOURCES-MIB` (1.3.6.1.2.1.25). See the table below for some important objects in this MIB: -| Nome | OID | Descrição | +| Name | OID | Description | | ---- | --- | ----------- | -| hrSystemDate.2 | 1.3.6.1.2.1.25.1.2 | A noção dos hosts de data e hora locais de um dia. | -| hrSystemUptime.0 | 1.3.6.1.2.1.25.1.1.0 | Tempo transcorrido desde a última inicialização do host. | -| hrMemorySize.0 | 1.3.6.1.2.1.25.2.2.0 | Quantidade de RAM no host. | -| hrSystemProcesses.0 | 1.3.6.1.2.1.25.1.6.0 | Número de contextos de processo carregados ou em execução no host. | -| hrStorageUsed.1 | 1.3.6.1.2.1.25.2.3.1.6.1 | Quantidade de espaço de armazenamento consumido no host, em hrStorageAllocationUnits. | -| hrStorageAllocationUnits.1 | 1.3.6.1.2.1.25.2.3.1.4.1 | Tamanho em bytes de um hrStorageAllocationUnit. | +| hrSystemDate.2 | 1.3.6.1.2.1.25.1.2 | The hosts notion of the local date and time of day. | +| hrSystemUptime.0 | 1.3.6.1.2.1.25.1.1.0 | How long it's been since the host was last initialized. | +| hrMemorySize.0 | 1.3.6.1.2.1.25.2.2.0 | The amount of RAM on the host. | +| hrSystemProcesses.0 | 1.3.6.1.2.1.25.1.6.0 | The number of process contexts currently loaded or running on the host. | +| hrStorageUsed.1 | 1.3.6.1.2.1.25.2.3.1.6.1 | The amount of storage space consumed on the host, in hrStorageAllocationUnits. | +| hrStorageAllocationUnits.1 | 1.3.6.1.2.1.25.2.3.1.4.1 | The size, in bytes, of an hrStorageAllocationUnit | -Por exemplo, para consultar `hrMemorySize` com o SNMP v3, execute o seguinte comando em uma estação de trabalho separada com suporte a SNMP na sua rede: +For example, to query for `hrMemorySize` with SNMP v3, run the following command on a separate workstation with SNMP support in your network: ```shell # username is the unique username of your SNMP v3 user # auth password is the authentication password # privacy password is the privacy password # hostname is the IP or domain of your Enterprise instance -$ snmpget -v 3 -u username -l authPriv \ - -A "auth password" -a SHA \ - -X "privacy password" -x AES \ - -O e hostname HOST-RESOURCES-MIB::hrMemorySize.0 +$ snmpget -v 3 -u USERNAME -l authPriv \ + -A "AUTH PASSWORD" -a SHA \ + -X "PRIVACY PASSWORD" -x AES \ + -O e HOSTNAME HOST-RESOURCES-MIB::hrMemorySize.0 ``` -Com o SNMP v2c, para consultar `hrMemorySize`, execute o seguinte comando em uma estação de trabalho separada com suporte a SNMP na sua rede: +With SNMP v2c, to query for `hrMemorySize`, run the following command on a separate workstation with SNMP support in your network: ```shell # community-string is your community string # hostname is the IP or domain of your Enterprise instance -snmpget -v 2c -c community-string hostname HOST-RESOURCES-MIB::hrMemorySize.0 +snmpget -v 2c -c COMMUNITY-STRING HOSTNAME HOST-RESOURCES-MIB::hrMemorySize.0 ``` {% tip %} -**Observação:** para evitar o vazamento de informações sobre serviços em execução no dispositivo, excluímos a tabela `hrSWRun` (1.3.6.1.2.1.25.4) dos relatórios resultantes do SNMP, a menos que você esteja usando o nível de segurança `authPriv` com o SNMP v3. Se você estiver usando o nível de segurança `authPriv`, incluiremos a tabela `hrSWRun`. +**Note:** To prevent leaking information about services running on your appliance, we exclude the `hrSWRun` table (1.3.6.1.2.1.25.4) from the resulting SNMP reports unless you're using the `authPriv` security level with SNMP v3. If you're using the `authPriv` security level, we include the `hrSWRun` table. {% endtip %} -Para obter mais informações sobre os mapeamentos de OID para atributos comuns do sistema no SNMP, confira "[OID do SNMP do Linux para CPU, memória e estatísticas de disco](http://www.linux-admins.net/2012/02/linux-snmp-oids-for-cpumemory-and-disk.html)". +For more information on OID mappings for common system attributes in SNMP, see "[Linux SNMP OID’s for CPU, Memory and Disk Statistics](http://www.linux-admins.net/2012/02/linux-snmp-oids-for-cpumemory-and-disk.html)". diff --git a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md index 6285cb208c..48672a0695 100644 --- a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md +++ b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md @@ -1,6 +1,6 @@ --- -title: Limites de alerta recomendados -intro: 'É possível configurar um alerta para receber notificações sobre os problemas de recursos do sistema antes que eles afetem o desempenho do appliance do {% data variables.product.prodname_ghe_server %}.' +title: Recommended alert thresholds +intro: 'You can configure an alert to notify you of system resource issues before they affect your {% data variables.product.prodname_ghe_server %} appliance''s performance.' redirect_from: - /enterprise/admin/guides/installation/about-recommended-alert-thresholds - /enterprise/admin/installation/about-recommended-alert-thresholds @@ -17,42 +17,36 @@ topics: - Performance - Storage shortTitle: Recommended alert thresholds -ms.openlocfilehash: 73adc62a8a322666e08da01a76568c16ed18458c -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145093982' --- -## Monitorar o armazenamento +## Monitoring storage -É recomendável monitorar seus dispositivos de armazenamento raiz e de usuário, bem como configurar um alerta com valores que definam um tempo de resposta longo quando o espaço em disco disponível estiver baixo. +We recommend that you monitor both the root and user storage devices and configure an alert with values that allow for ample response time when available disk space is low. -| Severidade | Limite | +| Severity | Threshold | | -------- | --------- | -| **Aviso** | Uso do disco excede 70% do total disponível. | -| **Crítico** | Uso do disco excede 85% do total disponível. | +| **Warning** | Disk use exceeds 70% of total available | +| **Critical** | Disk use exceeds 85% of total available | -Você pode ajustar esses valores com base na quantidade de armazenamento total alocada, nos padrões históricos de crescimento e no tempo esperado de resposta. Recomendamos a superalocação dos recursos de armazenamento para permitir o crescimento e evitar o tempo de inatividade necessário para alocar armazenamento adicional. +You can adjust these values based on the total amount of storage allocated, historical growth patterns, and expected time to respond. We recommend over-allocating storage resources to allow for growth and prevent the downtime required to allocate additional storage. -## Monitoramento de CPU e uso médio de carga +## Monitoring CPU and load average usage -Embora seja normal haver oscilação no uso de CPU conforme as operações do Git, é recomendável configurar um alerta para identificar usos de CPU altos demais, já que os picos prolongados podem indicar provisionamento insuficiente da sua instância. Recomendamos monitorar a média de carga do sistema a cada quinze minutos para valores próximos ou superiores ao número de núcleos de CPU alocados à máquina virtual. +Although it is normal for CPU usage to fluctuate based on resource-intense Git operations, we recommend configuring an alert for abnormally high CPU utilization, as prolonged spikes can mean your instance is under-provisioned. We recommend monitoring the fifteen-minute system load average for values nearing or exceeding the number of CPU cores allocated to the virtual machine. -| Severidade | Limite | +| Severity | Threshold | | -------- | --------- | -| **Aviso** | Média de carga de quinze minutos excede 1x núcleos de CPU. | -| **Crítico** | Média de carga de quinze minutos excede 2x núcleos de CPU. | +| **Warning** | Fifteen minute load average exceeds 1x CPU cores | +| **Critical** | Fifteen minute load average exceeds 2x CPU cores | -Também é recomendável monitorar o tempo de "roubo" da virtualização para garantir que outras máquinas virtuais em execução no mesmo sistema host não usem todos os recursos da instância. +We also recommend that you monitor virtualization "steal" time to ensure that other virtual machines running on the same host system are not using all of the instance's resources. -## Monitorar o uso de memória +## Monitoring memory usage -A quantidade de memória física alocada ao {% data variables.product.product_location %} pode ter um grande impacto no desempenho geral e na capacidade de resposta do aplicativo. O sistema é projetado para fazer uso intenso do cache de disco do kernel a fim de acelerar as operações do Git. Recomendamos que o conjunto de trabalho RSS normal caiba em 50% do total de RAM disponível no uso máximo. +The amount of physical memory allocated to {% data variables.location.product_location %} can have a large impact on overall performance and application responsiveness. The system is designed to make heavy use of the kernel disk cache to speed up Git operations. We recommend that the normal RSS working set fit within 50% of total available RAM at peak usage. -| Severidade | Limite | +| Severity | Threshold | | -------- | --------- | -| **Aviso** | Uso de RSS sustentado excede 50% do total de memória disponível. | -| **Crítico** | Uso de RSS sustentado excede 70% do total de memória disponível. | +| **Warning** | Sustained RSS usage exceeds 50% of total available memory | +| **Critical** | Sustained RSS usage exceeds 70% of total available memory | -Se a memória estiver esgotada, o killer OOM do kernel tentará liberar recursos de memória eliminando à força os processos de aplicativos pesados da RAM, o que pode causar a interrupção do serviço. É recomendável alocar mais memória do que o necessário para a máquina virtual no curso normal das operações. +If memory is exhausted, the kernel OOM killer will attempt to free memory resources by forcibly killing RAM heavy application processes, which could result in a disruption of service. We recommend allocating more memory to the virtual machine than is required in the normal course of operations. diff --git a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md index f2899dc6b6..645c354107 100644 --- a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md +++ b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md @@ -1,6 +1,6 @@ --- -title: Verificações de atualizações automáticas -intro: 'É possível habilitar as verificações de atualizações automáticas para que a {% data variables.product.product_location %} verifique e baixe as últimas versões do {% data variables.product.prodname_ghe_server %}.' +title: Enabling automatic update checks +intro: 'You can enable automatic update checks so that {% data variables.location.product_location %} checks for and downloads the latest {% data variables.product.prodname_ghe_server %} release.' redirect_from: - /enterprise/admin/installation/enabling-automatic-update-checks - /enterprise/admin/enterprise-management/enabling-automatic-update-checks @@ -12,31 +12,28 @@ topics: - Enterprise - Upgrades shortTitle: Enable automatic update checks -ms.openlocfilehash: c566dc54958cc7d4f26a9279ea3bf8a76aafa636 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146331885' --- -Quando um pacote de upgrade for baixado automaticamente para o {% data variables.product.product_location %}, você receberá uma mensagem informando que pode fazer o upgrade do {% data variables.product.prodname_ghe_server %}. Os pacotes são baixados no diretório `/var/lib/ghe-updates` do {% data variables.product.product_location %}. Para obter mais informações, confira "[Como atualizar o {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server)". +When an upgrade package is automatically downloaded for {% data variables.location.product_location %}, you'll receive a message letting you know you can upgrade {% data variables.product.prodname_ghe_server %}. Packages download to the `/var/lib/ghe-updates` directory on {% data variables.location.product_location %}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server)." -Se um patch dinâmico estiver disponível para um upgrade, o `.hpkg` será baixado automaticamente. No console de gerenciamento, você pode instalar o hotpatch imediatamente ou agendar a instalação para outro período. Para obter mais informações, confira "[Como fazer upgrade com um patch dinâmico](/enterprise/admin/guides/installation/upgrading-github-enterprise-server#upgrading-with-a-hotpatch)". +If a hotpatch is available for an upgrade, the `.hpkg` will download automatically. In the management console you can choose to install the hotpatch immediately or schedule installation for a later time. For more information, see "[Upgrading with a hotpatch](/enterprise/admin/guides/installation/upgrading-github-enterprise-server#upgrading-with-a-hotpatch)." {% tip %} -**Dica:** para habilitar as verificações de atualização automática, o {% data variables.product.product_location %} precisa conseguir se conectar a `https://github-enterprise.s3.amazonaws.com`. +**Tip:** To enable automatic update checks, {% data variables.location.product_location %} must be able to connect to `https://github-enterprise.s3.amazonaws.com`. {% endtip %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.updates-tab %} -4. Clique em **Sim, verificar automaticamente se há atualizações**. -![Botão usado para habilitar atualizações as automáticas](/assets/images/enterprise/management-console/enable_updates_button.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.updates-tab %} +4. Click **Yes, automatically check for updates**. +![Button for enabling automatic updates](/assets/images/enterprise/management-console/enable_updates_button.png) +{% data reusables.enterprise_management_console.save-settings %} -Para ver se a sua instância está atualizada, verifique o banner na guia Updates (Atualizações). +To see if your instance is up-to-date, check the banner on the Updates tab. -![Banner indicativo da versão do GitHub Enterprise Server](/assets/images/enterprise/management-console/up-to-date-banner.png) +![Banner indicating your release of GitHub Enterprise Server](/assets/images/enterprise/management-console/up-to-date-banner.png) -Em **Logs**, você pode ver o status da verificação de atualização mais recente. +Under **Logs**, you can see the status of the most recent update check. -![Logs para atualização](/assets/images/enterprise/management-console/update-log.png) +![Logs for update](/assets/images/enterprise/management-console/update-log.png) diff --git a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md index 9dc45f6c01..884c2a3d88 100644 --- a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md +++ b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md @@ -1,6 +1,6 @@ --- -title: Aprimorar os recursos de CPU ou memória -intro: 'Se houver lentidão das operações na {% data variables.product.prodname_ghe_server %}, pode ser necessário adicionar recursos de CPU ou memória.' +title: Increasing CPU or memory resources +intro: 'You can increase the CPU or memory resources for a {% data variables.product.prodname_ghe_server %} instance.' redirect_from: - /enterprise/admin/installation/increasing-cpu-or-memory-resources - /enterprise/admin/enterprise-management/increasing-cpu-or-memory-resources @@ -13,104 +13,99 @@ topics: - Infrastructure - Performance shortTitle: Increase CPU or memory -ms.openlocfilehash: 1ac89694cf374cca1ba47f228f881dc4a5fd405f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146331861' --- {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %} {% note %} -**Observação:** antes de aumentar os recursos de CPU ou memória, coloque sua instância no modo de manutenção.{% ifversion ip-exception-list %} Você pode validar as alterações configurando uma lista de exceções de IP para permitir o acesso de endereços IP especificados. {% endif %} Para obter mais informações, confira "[Como habilitar e agendar o modo de manutenção](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)". +**Note:** Before increasing CPU or memory resources, put your instance in maintenance mode.{% ifversion ip-exception-list %} You can validate changes by configuring an IP exception list to allow access from specified IP addresses. {% endif %} For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." {% endnote %} -## Adicionar recursos de CPU ou memória para AWS +## Adding CPU or memory resources for AWS {% note %} -**Observação:** para adicionar recursos de CPU ou memória à AWS, você deve saber usar o console de gerenciamento da AWS ou a interface da linha de comando da `aws ec2` para gerenciar instâncias do EC2. Para obter informações e detalhes sobre como usar as ferramentas da AWS de sua preferência para executar o redimensionamento, consulte a documentação da AWS sobre o [redimensionamento de uma instância com backup do Amazon EBS](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html). +**Note:** To add CPU or memory resources for AWS, you must be familiar with using either the AWS management console or the `aws ec2` command line interface to manage EC2 instances. For background and details on using the AWS tools of your choice to perform the resize, see the AWS documentation on [resizing an Amazon EBS-backed instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html). {% endnote %} -### Considerações de redimensionamento +### Resizing considerations -Para aumentar recursos de CPU ou memória do {% data variables.product.product_location %}, examine as seguintes recomendações: +Before increasing CPU or memory resources for {% data variables.location.product_location %}, review the following recommendations. -- **Escale sua memória com CPUs**. {% data reusables.enterprise_installation.increasing-cpus-req %} -- **Atribua um endereço IP Elástico à instância**. Se não houver IP elástica atribuída, você terá que ajustar os registros DNS A do seu host do {% data variables.product.prodname_ghe_server %} após o reinício para explicar a alteração no endereço IP público. Depois que a instância for reiniciada, a IP elástica (EIP) será automaticamente mantida se a instância for iniciada em uma VPC. Se a instância for iniciada no EC2-Classic, a IP elástica deverá ser associada outra vez manualmente. +- **Scale your memory with CPUs**. {% data reusables.enterprise_installation.increasing-cpus-req %} +- **Assign an Elastic IP address to the instance**. If you haven't assigned an Elastic IP to your instance, you'll have to adjust the DNS A records for your {% data variables.product.prodname_ghe_server %} host after the restart to account for the change in public IP address. Once your instance restarts, the instance keeps the Elastic IP if you launched the instance in a virtual private cloud (VPC). If you create the instance in an EC2-Classic network, you must manually reassign the Elastic IP to the instance. -### Tipos de instância do AWS compatíveis +### Supported AWS instance types -É necessário determinar o tipo de instância para a qual você pretende atualizar com base nas especificações de CPU/memória. +You need to determine the instance type you would like to upgrade to based on CPU/memory specifications. {% data reusables.enterprise_installation.warning-on-scaling %} {% data reusables.enterprise_installation.aws-instance-recommendation %} -### Redimensionar para o AWS +### Resizing for AWS {% note %} -**Observação:** para instâncias iniciadas no EC2-Classic, anote o endereço IP Elástico associado à instância e a ID da instância. Depois de reiniciar a instância, reassocie o endereço IP elástico. +**Note:** For instances launched in EC2-Classic, write down both the Elastic IP address associated with the instance and the instance's ID. Once you restart the instance, re-associate the Elastic IP address. {% endnote %} -Não é possível adicionar recursos de CPU ou memória a uma instância atual do AWS/EC2. Faça o seguinte: +It's not possible to add CPU or memory resources to an existing AWS/EC2 instance. Instead, you must: -1. Pare a instância; -2. Altere o tipo de instância. -3. Inicie a instância. +1. Stop the instance. +2. Change the instance type. +3. Start the instance. {% data reusables.enterprise_installation.configuration-recognized %} -## Adicionar recursos de CPU ou memória ao Microsoft Azure +## Adding CPU or memory resources on Microsoft Azure {% note %} -**Observação:** para adicionar recursos de CPU ou memória no Microsoft Azure, você deve estar familiarizado com o uso do Portal Azure, da Azure CLI ou do Azure Powershell para gerenciar as instâncias de VM. Para obter informações e detalhes sobre como usar as ferramentas do Azure de sua preferência para executar o redimensionamento, confira a documentação do Azure sobre [como alterar o tamanho de uma máquina virtual](https://docs.microsoft.com/en-us/azure/virtual-machines/resize-vm). +**Note:** To add CPU or memory resources in Microsoft Azure, you must be familiar with using either the Azure Portal, Azure CLI or Azure PowerShell to manage VM instances. For background and details on using the Azure tools of your choice to perform the resize, please refer to the Azure documentation on [changing the size of a virtual machine](https://docs.microsoft.com/en-us/azure/virtual-machines/resize-vm). {% endnote %} -### Considerações de redimensionamento +### Resizing considerations -Para aumentar recursos de CPU ou memória do {% data variables.product.product_location %}, examine as seguintes recomendações: +Before increasing CPU or memory resources for {% data variables.location.product_location %}, review the following recommendations. -- **Escale sua memória com CPUs**. {% data reusables.enterprise_installation.increasing-cpus-req %} -- **Atribua um endereço IP estático à instância**. Se você não atribuiu um IP estático à instância, você deve ter que ajustar os registros DNS A para o seu host de {% data variables.product.prodname_ghe_server %} após a reinicialização da conta para alterar o endereço IP. +- **Scale your memory with CPUs**. {% data reusables.enterprise_installation.increasing-cpus-req %} +- **Assign a static IP address to the instance**. If you haven't assigned a static IP to your instance, you might have to adjust the DNS A records for your {% data variables.product.prodname_ghe_server %} host after the restart to account for the change in IP address. -### Tamanhos compatíveis da instância do Microsoft Azure +### Supported Microsoft Azure instance sizes -É necessário determinar tamanho da instância para a qual você pretende atualizar com base nas especificações de CPU/memória. +You need to determine the instance size you would like to upgrade to based on CPU/memory specifications. {% data reusables.enterprise_installation.warning-on-scaling %} {% data reusables.enterprise_installation.azure-instance-recommendation %} -### Redimensionamento para o Microsoft Azure +### Resizing for Microsoft Azure -Você pode dimensionar a VM alterando o tamanho da VM. Alterar o tamanho dele fará com que ele seja reiniciado. Em alguns casos, você deverá desalocar a VM primeiro. Isso pode acontecer se o novo tamanho não estiver disponível no cluster de hardware que hospeda atualmente a VM. +You can scale the VM up by changing the VM size. Changing its size will cause it to be restarted. In some cases, you must deallocate the VM first. This can happen if the new size is not available on the hardware cluster that is currently hosting the VM. -1. Consulte a documentação do Azure sobre [como alterar o tamanho de uma máquina virtual](https://docs.microsoft.com/en-us/azure/virtual-machines/resize-vm) para as etapas necessárias. +1. Refer to the Azure documentation on [changing the size of a virtual machine](https://docs.microsoft.com/en-us/azure/virtual-machines/resize-vm) for the required steps. {% data reusables.enterprise_installation.configuration-recognized %} -## Adicionar recursos de CPU ou memória para OpenStack KVM +## Adding CPU or memory resources for OpenStack KVM -Não é possível adicionar recursos de CPU ou memória a uma instância atual do OpenStack KVM. Faça o seguinte: +It's not possible to add CPU or memory resources to an existing OpenStack KVM instance. Instead, you must: -1. Tire um instantâneo da instância atual; -2. Pare a instância; -3. Selecione um novo tipo de instância que tenha os recursos de CPU e/ou memória desejados. +1. Take a snapshot of the current instance. +2. Stop the instance. +3. Select a new instance flavor that has the desired CPU and/or memory resources. -## Adicionar recursos de memória ou CPU para VMware +## Adding CPU or memory resources for VMware {% data reusables.enterprise_installation.increasing-cpus-req %} -1. Use o cliente vSphere para conexão com o host VMware ESXi. -2. Desligue a {% data variables.product.product_location %}. -3. Selecione a máquina virtual e clique em **Editar Configurações**. -4. Em "Hardware", ajuste a CPU e/ou os recursos de memória alocados à máquina virtual, conforme necessário: ![recursos de configuração do VMware](/assets/images/enterprise/vmware/vsphere-hardware-tab.png) -5. Para iniciar a máquina virtual, clique em **OK**. +1. Use the vSphere Client to connect to the VMware ESXi host. +2. Shut down {% data variables.location.product_location %}. +3. Select the virtual machine and click **Edit Settings**. +4. Under "Hardware", adjust the CPU and/or memory resources allocated to the virtual machine as needed: +![VMware setup resources](/assets/images/enterprise/vmware/vsphere-hardware-tab.png) +5. To start the virtual machine, click **OK**. {% data reusables.enterprise_installation.configuration-recognized %} diff --git a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md index ca2c27b2fd..e55e7cb44d 100644 --- a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md +++ b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md @@ -1,6 +1,6 @@ --- -title: Aumentar a capacidade de armazenamento -intro: 'Você pode aumentar ou alterar a quantidade de armazenamento disponível para repositórios, bancos de dados, índices de pesquisa e outros dados persistentes de aplicativo no Git.' +title: Increasing storage capacity +intro: 'You can increase or change the amount of storage available for Git repositories, databases, search indexes, and other persistent application data.' redirect_from: - /enterprise/admin/installation/increasing-storage-capacity - /enterprise/admin/enterprise-management/increasing-storage-capacity @@ -14,86 +14,80 @@ topics: - Performance - Storage shortTitle: Increase storage capacity -ms.openlocfilehash: b6542e1f43ce4111358de3940c8e46dea2afd5d5 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147881119' --- {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %} -À medida que mais usuários ingressam em {% data variables.product.product_location %}, talvez seja necessário redimensionar o volume de armazenamento. Consulte a documentação da sua plataforma de virtualização para obter informações sobre como fazer isso. +As more users join {% data variables.location.product_location %}, you may need to resize your storage volume. Refer to the documentation for your virtualization platform for information on resizing storage. -## Requisitos e recomendações +## Requirements and recommendations {% note %} -**Observação:** para redimensionar um volume de armazenamento, coloque a instância no modo de manutenção.{% ifversion ip-exception-list %} Você pode validar as alterações ao configurar uma lista de exceções de IP para permitir o acesso de endereços IP especificados. {% endif %} Para obter mais informações, confira "[Como habilitar e agendar o modo de manutenção](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)". +**Note:** Before resizing any storage volume, put your instance in maintenance mode.{% ifversion ip-exception-list %} You can validate changes by configuring an IP exception list to allow access from specified IP addresses. {% endif %} For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." {% endnote %} -### Requisitos mínimos +### Minimum requirements {% data reusables.enterprise_installation.hardware-rec-table %} -## Aumentar o tamanho da partição de dados +## Increasing the data partition size -1. Redimensione o disco de volume de usuário existente usando as ferramentas da plataforma de virtualização. +1. Resize the existing user volume disk using your virtualization platform's tools. {% data reusables.enterprise_installation.ssh-into-instance %} -3. Deixe o appliance em modo de manutenção. Para obter mais informações, confira "[Como habilitar e agendar o modo de manutenção](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)". -4. Reinicie o dispositivo para detectar a alocação do novo armazenamento. +3. Put the appliance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." +4. Reboot the appliance to detect the new storage allocation: ```shell $ sudo reboot ``` -5. Execute o comando `ghe-storage-extend` para expandir o sistema de arquivos de `/data/user`: +5. Run the `ghe-storage-extend` command to expand the `/data/user` filesystem: ```shell $ ghe-storage-extend ``` -## Aumentar o tamanho da partição de dados raiz usando um novo appliance +## Increasing the root partition size using a new appliance -1. Configure uma nova instância do {% data variables.product.prodname_ghe_server %} com um disco raiz maior usando a mesma versão do appliance atual. Para obter mais informações, confira "[Como configurar uma instância do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance)". -2. Desligue o dispositivo atual: +1. Set up a new {% data variables.product.prodname_ghe_server %} instance with a larger root disk using the same version as your current appliance. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance)." +2. Shut down the current appliance: ```shell $ sudo poweroff ``` -3. Desvincule o disco de dados do appliance atual usando as ferramentas da plataforma de virtualização. -4. Vincule o disco de dados ao novo appliance com o disco raiz maior. +3. Detach the data disk from the current appliance using your virtualization platform's tools. +4. Attach the data disk to the new appliance with the larger root disk. -## Aumentar o tamanho da partição de dados raiz usando um appliance existente +## Increasing the root partition size using an existing appliance {% warning %} -**Aviso:** antes de aumentar o tamanho da partição raiz, você deverá colocar sua instância no modo de manutenção. Para obter mais informações, confira "[Como habilitar e agendar o modo de manutenção](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)". +**Warning:** Before increasing the root partition size, you must put your instance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." {% endwarning %} -1. Vincule o novo disco ao appliance do {% data variables.product.prodname_ghe_server %}. -1. Execute o comando `lsblk` para identificar o nome do dispositivo do novo disco. -1. Execute o comando `parted` para formatar o disco, substituindo o nome do dispositivo por `/dev/xvdg`: +1. Attach a new disk to your {% data variables.product.prodname_ghe_server %} appliance. +1. Run the `lsblk` command to identify the new disk's device name. +1. Run the `parted` command to format the disk, substituting your device name for `/dev/xvdg`: ```shell $ sudo parted /dev/xvdg mklabel msdos $ sudo parted /dev/xvdg mkpart primary ext4 0% 50% $ sudo parted /dev/xvdg mkpart primary ext4 50% 100% ``` -1. Para parar a replicação, execute o comando `ghe-repl-stop`. +1. To stop replication, run the `ghe-repl-stop` command. ```shell $ ghe-repl-stop ``` -1. Execute o comando `ghe-upgrade` para instalar um pacote completo específico da plataforma no disco recém-particionado. Um pacote de atualização de hotpatch universal, como `github-enterprise-2.11.9.hpkg`, não funcionará conforme o esperado. Depois que o comando `ghe-upgrade` for concluído, os serviços do aplicativo serão encerrados automaticamente. +1. Run the `ghe-upgrade` command to install a full, platform specific package to the newly partitioned disk. A universal hotpatch upgrade package, such as `github-enterprise-2.11.9.hpkg`, will not work as expected. After the `ghe-upgrade` command completes, application services will automatically terminate. ```shell $ ghe-upgrade PACKAGE-NAME.pkg -s -t /dev/xvdg1 ``` -1. Desligue o dispositivo: +1. Shut down the appliance: ```shell $ sudo poweroff ``` -1. No hipervisor, remova o disco raiz antigo e vincule o novo disco raiz no mesmo local do antigo. -1. Inicie o dispositivo. -1. Certifique-se de que os serviços do sistema estejam funcionando corretamente, depois liberar o modo de manutenção. Para obter mais informações, confira "[Como habilitar e agendar o modo de manutenção](/admin/guides/installation/enabling-and-scheduling-maintenance-mode)". +1. In the hypervisor, remove the old root disk and attach the new root disk at the same location as the old root disk. +1. Start the appliance. +1. Ensure system services are functioning correctly, then release maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." -Se seu dispositivo estiver configurado para alta disponibilidade ou replicação geográfica, lembre-se de iniciar a replicação em cada nó de réplica usando `ghe-repl-start` após a atualização do armazenamento em todos os nós. +If your appliance is configured for high-availability or geo-replication, remember to start replication on each replica node using `ghe-repl-start` after the storage on all nodes has been upgraded. diff --git a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md index fdd396c0ce..24cfb85f46 100644 --- a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md +++ b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md @@ -1,6 +1,6 @@ --- -title: Requisitos de atualização -intro: 'Antes de atualizar o {% data variables.product.prodname_ghe_server %}, veja as recomendações e requisitos a seguir para planejar sua estratégia de atualização.' +title: Upgrade requirements +intro: 'Before upgrading {% data variables.product.prodname_ghe_server %}, review these recommendations and requirements to plan your upgrade strategy.' redirect_from: - /enterprise/admin/installation/upgrade-requirements - /enterprise/admin/guides/installation/finding-the-current-github-enterprise-release @@ -13,46 +13,41 @@ type: reference topics: - Enterprise - Upgrades -ms.openlocfilehash: 5b2aae044f2f5198bbd96669221936658d9464a6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147065183' --- {% note %} -**Observações:** {% ifversion ghes < 3.3 %}– Recursos como o {% data variables.product.prodname_actions %}, o {% data variables.product.prodname_registry %}, o {% data variables.product.prodname_mobile %} e o {% data variables.product.prodname_GH_advanced_security %} estão disponíveis no {% data variables.product.prodname_ghe_server %} 3.0 ou superior. É altamente recomendável que você faça a atualização para versão 3.0 ou posterior para aproveitar as atualizações críticas de segurança, correções de erros e melhorias de recursos.{% endif %} -- Os pacotes de upgrade estão disponíveis em [enterprise.github.com](https://enterprise.github.com/releases) para as versões compatíveis. Verifique a disponibilidade dos pacotes de atualização necessários para concluir a atualização. Se um pacote não estiver disponível, entre em contato com o {% data variables.contact.contact_ent_support %} para obter assistência. -- Se você estiver usando o Clustering do {% data variables.product.prodname_ghe_server %}, confira "[Como fazer upgrade de um cluster](/enterprise/admin/guides/clustering/upgrading-a-cluster/)" no Guia de Clustering do {% data variables.product.prodname_ghe_server %} para obter instruções específicas exclusivas sobre o clustering. -- As notas de versão do {% data variables.product.prodname_ghe_server %} mostram uma lista abrangente dos novos recursos de cada versão do {% data variables.product.prodname_ghe_server %}. Para obter mais informações, confira a [página de versões](https://enterprise.github.com/releases). +**Notes:** +{% ifversion ghes < 3.3 %}- Features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, {% data variables.product.prodname_mobile %} and {% data variables.product.prodname_GH_advanced_security %} are available on {% data variables.product.prodname_ghe_server %} 3.0 or higher. We highly recommend upgrading to 3.0 or later releases to take advantage of critical security updates, bug fixes and feature enhancements.{% endif %} +- Upgrade packages are available at [enterprise.github.com](https://enterprise.github.com/releases) for supported versions. Verify the availability of the upgrade packages you will need to complete the upgrade. If a package is not available, contact {% data variables.contact.contact_ent_support %} for assistance. +- If you're using {% data variables.product.prodname_ghe_server %} Clustering, see "[Upgrading a cluster](/enterprise/admin/guides/clustering/upgrading-a-cluster/)" in the {% data variables.product.prodname_ghe_server %} Clustering Guide for specific instructions unique to clustering. +- The release notes for {% data variables.product.prodname_ghe_server %} provide a comprehensive list of new features for every version of {% data variables.product.prodname_ghe_server %}. For more information, see the [releases page](https://enterprise.github.com/releases). {% endnote %} -## Recomendações +## Recommendations -- Inclua o mínimo possível de atualizações no seu processo. Por exemplo, em vez de atualizar do {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} para o {{ enterpriseServerReleases.supported[1] }} e depois para o {{ enterpriseServerReleases.latest }}, atualize do {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} para o {{ enterpriseServerReleases.latest }}. Use o [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) para localizar o caminho de upgrade começando na sua versão atual. -- Se a versão estiver muito desatualizada, atualize o {% data variables.product.product_location %} para a versão mais atual disponível a cada etapa do processo de upgrade. Ao usar a versão mais recente em cada atualização, você pode aproveitar as melhorias de desempenho e as correções de erros. Por exemplo, você poderia atualizar do {% data variables.product.prodname_enterprise %} 2.7 para o 2.8 e depois para o 2.10. No entanto, atualizar do {% data variables.product.prodname_enterprise %} 2.7 para o 2.9 e depois para o 2.10 usa uma versão mais recente na segunda etapa. -- Ao atualizar, use a versão mais recente do patch. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} -- Use uma instância de preparo para testar as etapas da atualização. Para obter mais informações, confira "[Como configurar uma instância de preparo](/enterprise/admin/guides/installation/setting-up-a-staging-instance/)". -- Ao executar várias atualizações, espere pelo menos 24 horas entre atualizações de recursos para permitir que as migrações de dados e as tarefas de atualização executadas em segundo plano sejam totalmente concluídas. -- Tire um instantâneo antes de atualizar sua máquina virtual. Para obter mais informações, confira "[Como criar um instantâneo](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server#taking-a-snapshot)". -- Certifique-se de ter um backup recente e da sua instância. Para obter mais informações, confira o [arquivo LEIAME.md do {% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme). +- Include as few upgrades as possible in your upgrade process. For example, instead of upgrading from {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} to {{ enterpriseServerReleases.supported[1] }} to {{ enterpriseServerReleases.latest }}, you could upgrade from {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} to {{ enterpriseServerReleases.latest }}. Use the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version. +- If you’re several versions behind, upgrade {% data variables.location.product_location %} as far forward as possible with each step of your upgrade process. Using the latest version possible on each upgrade allows you to take advantage of performance improvements and bug fixes. For example, you could upgrade from {% data variables.product.prodname_enterprise %} 2.7 to 2.8 to 2.10, but upgrading from {% data variables.product.prodname_enterprise %} 2.7 to 2.9 to 2.10 uses a later version in the second step. +- Use the latest patch release when upgrading. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} +- Use a staging instance to test the upgrade steps. For more information, see "[Setting up a staging instance](/enterprise/admin/guides/installation/setting-up-a-staging-instance/)." +- When running multiple upgrades, wait at least 24 hours between feature upgrades to allow data migrations and upgrade tasks running in the background to fully complete. +- Take a snapshot before upgrading your virtual machine. For more information, see "[Taking a snapshot](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server#taking-a-snapshot)." +- Ensure you have a recent, successful backup of your instance. For more information, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README.md file](https://github.com/github/backup-utils#readme). -## Requisitos +## Requirements -- Você precisa fazer upgrade de uma versão de recurso que esteja **no máximo** duas versões atrás. Por exemplo, ao atualizar para o {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.latest }}, você deve estar nas versões {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[1] }} ou {{ enterpriseServerReleases.supported[2] }}. -- Ao fazer a atualização com um pacote de atualização, agende um período de manutenção para usuários finais de {% data variables.product.prodname_ghe_server %}. +- You must upgrade from a feature release that's **at most** two releases behind. For example, to upgrade to {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.latest }}, you must be on {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[1] }} or {{ enterpriseServerReleases.supported[2] }}. +- When upgrading using an upgrade package, schedule a maintenance window for {% data variables.product.prodname_ghe_server %} end users. - {% data reusables.enterprise_installation.hotpatching-explanation %} -- Um hotpatch pode causar tempo de inatividade se os serviços afetados (como kernel, MySQL ou Elasticsearch) exigirem reinicialização da VM ou do serviço. Você receberá uma notificação quando/se a reinicialização for necessária. Será possível reinicializar em outro momento. -- Procure disponibilizar um armazenamento adicional na raiz durante a atualização, já que o hotpatching instala várias versões de alguns serviços até a conclusão da atualização. Caso não haja espaço suficiente, você receberá uma notificação das verificações preliminares. -- Ao atualizar pelo hotpatching, sua instância não pode ficar carregada demais (isso pode afetar o processo). -- A atualização do {% data variables.product.prodname_ghe_server %} 2.17 migra seus logs de auditoria do Elasticsearch para o MySQL. Além disso, essa migração aumenta a quantidade de tempo e espaço em disco necessários para restaurar um instantâneo. Antes de migrar, verifique o número de bytes nos índices de log de auditoria do Elasticsearch com este comando: +- A hotpatch may require downtime if the affected services (like kernel, MySQL, or Elasticsearch) require a VM reboot or a service restart. You'll be notified when a reboot or restart is required. You can complete the reboot or restart at a later time. +- Additional root storage must be available when upgrading through hotpatching, as it installs multiple versions of certain services until the upgrade is complete. Pre-flight checks will notify you if you don't have enough root disk storage. +- When upgrading through hotpatching, your instance cannot be too heavily loaded, as it may impact the hotpatching process. +- Upgrading to {% data variables.product.prodname_ghe_server %} 2.17 migrates your audit logs from Elasticsearch to MySQL. This migration also increases the amount of time and disk space it takes to restore a snapshot. Before migrating, check the number of bytes in your Elasticsearch audit log indices with this command: ``` shell curl -s http://localhost:9201/audit_log/_stats/store | jq ._all.primaries.store.size_in_bytes ``` -Use o número para estimar o espaço em disco necessário para os logs de auditoria do MySQL. O script também monitora seu espaço livre em disco durante o andamento da importação. Monitorar esse número é útil principalmente se o espaço livre em disco estiver próximo da quantidade de espaço em disco necessária para a migração. +Use the number to estimate the amount of disk space the MySQL audit logs will need. The script also monitors your free disk space while the import is in progress. Monitoring this number is especially useful if your free disk space is close to the amount of disk space necessary for migration. -## Próximas etapas +## Next steps -Após ler essas recomendações e requisitos, você poderá atualizar para o {% data variables.product.prodname_ghe_server %}. Para obter mais informações, confira "[Como atualizar o {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)". +After reviewing these recommendations and requirements, you can upgrade {% data variables.product.prodname_ghe_server %}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)." diff --git a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md index 590bf709b2..c1c8100472 100644 --- a/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md +++ b/translations/pt-BR/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md @@ -32,11 +32,11 @@ shortTitle: Upgrading GHES {% note %} - **Note:** Your {% data variables.product.prodname_enterprise_backup_utilities %} version needs to be the same version as, or at most two versions ahead of, {% data variables.product.product_location %}. For more information, see "[Upgrading GitHub Enterprise Server Backup Utilities](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance#upgrading-github-enterprise-server-backup-utilities)." + **Note:** Your {% data variables.product.prodname_enterprise_backup_utilities %} version needs to be the same version as, or at most two versions ahead of, {% data variables.location.product_location %}. For more information, see "[Upgrading GitHub Enterprise Server Backup Utilities](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance#upgrading-github-enterprise-server-backup-utilities)." {% endnote %} -1. If {% data variables.product.product_location %} uses ephemeral self-hosted runners for {% data variables.product.prodname_actions %} and you've disabled automatic updates, upgrade your runners to the version of the runner application that your upgraded instance will run. +1. If {% data variables.location.product_location %} uses ephemeral self-hosted runners for {% data variables.product.prodname_actions %} and you've disabled automatic updates, upgrade your runners to the version of the runner application that your upgraded instance will run. 1. If you are upgrading using an upgrade package, schedule a maintenance window for {% data variables.product.prodname_ghe_server %} end users. If you are using a hotpatch, maintenance mode is not required. {% note %} @@ -84,7 +84,7 @@ Using the {% data variables.enterprise.management_console %}, you can install a **{% ifversion ghes %}Notes{% else %}Note{% endif %}**: {% ifversion ghes %} -- If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. +- If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. - {% endif %}Installing a hotpatch using the {% data variables.enterprise.management_console %} is not available in clustered environments. To install a hotpatch in a clustered environment, see "[Upgrading a cluster](/enterprise/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)." @@ -184,7 +184,7 @@ While you can use a hotpatch to upgrade to the latest patch release within a fea {% ifversion ip-exception-list %} 1. Optionally, to validate the upgrade, configure an IP exception list to allow access to a specified list of IP addresses. For more information, see "[Validating changes in maintenance mode using the IP exception list](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)." {% endif %} -7. For single appliance upgrades, disable maintenance mode so users can use {% data variables.product.product_location %}. +7. For single appliance upgrades, disable maintenance mode so users can use {% data variables.location.product_location %}. {% note %} @@ -239,7 +239,7 @@ Appliances configured for high-availability and geo-replication use replica inst - If you have upgraded each node to {% data variables.product.product_name %} 3.6.0 or later and started replication, but `git replication is behind the primary` continues to appear after 45 minutes, contact {% data variables.contact.enterprise_support %}. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)." {%- endif %} - {% ifversion ghes = 3.4 or ghes = 3.5 or ghes = 3.6 %}Otherwise, if{% else %}If{% endif %} `ghe-repl-status` did not return `OK`, contact {% data variables.contact.enterprise_support %}. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)." -6. When you have completed upgrading the last replica, and the resync is complete, disable maintenance mode so users can use {% data variables.product.product_location %}. +6. When you have completed upgrading the last replica, and the resync is complete, disable maintenance mode so users can use {% data variables.location.product_location %}. ## Restoring from a failed upgrade diff --git a/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md index bd71918b12..986fa1a462 100644 --- a/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md +++ b/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md @@ -1,7 +1,7 @@ --- title: Backing up and restoring GitHub Enterprise Server with GitHub Actions enabled shortTitle: Backing up and restoring -intro: 'To restore a backup of {% data variables.product.product_location %} when {% data variables.product.prodname_actions %} is enabled, you must configure {% data variables.product.prodname_actions %} before restoring the backup with {% data variables.product.prodname_enterprise_backup_utilities %}.' +intro: 'To restore a backup of {% data variables.location.product_location %} when {% data variables.product.prodname_actions %} is enabled, you must configure {% data variables.product.prodname_actions %} before restoring the backup with {% data variables.product.prodname_enterprise_backup_utilities %}.' versions: ghes: '*' type: how_to @@ -16,13 +16,13 @@ redirect_from: ## About backups of {% data variables.product.product_name %} when using {% data variables.product.prodname_actions %} -You can use {% data variables.product.prodname_enterprise_backup_utilities %} to back up and restore the data and configuration for {% data variables.product.product_location %} to a new instance. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-backups-on-your-appliance)." +You can use {% data variables.product.prodname_enterprise_backup_utilities %} to back up and restore the data and configuration for {% data variables.location.product_location %} to a new instance. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-backups-on-your-appliance)." However, not all the data for {% data variables.product.prodname_actions %} is included in these backups. {% data reusables.actions.enterprise-storage-ha-backups %} ## Restoring a backup of {% data variables.product.product_name %} when {% data variables.product.prodname_actions %} is enabled -To restore a backup of {% data variables.product.product_location %} with {% data variables.product.prodname_actions %}, you must manually configure network settings and external storage on the destination instance before you restore your backup from {% data variables.product.prodname_enterprise_backup_utilities %}. +To restore a backup of {% data variables.location.product_location %} with {% data variables.product.prodname_actions %}, you must manually configure network settings and external storage on the destination instance before you restore your backup from {% data variables.product.prodname_enterprise_backup_utilities %}. 1. Confirm that the source instance is offline. 1. Manually configure network settings on the replacement {% data variables.product.prodname_ghe_server %} instance. Network settings are excluded from the backup snapshot, and are not overwritten by `ghe-restore`. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)." @@ -41,4 +41,4 @@ To restore a backup of {% data variables.product.product_location %} with {% dat ``` {% data reusables.actions.apply-configuration-and-enable %} 1. After {% data variables.product.prodname_actions %} is configured and enabled, to restore the rest of the data from the backup, use the `ghe-restore` command. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)." -1. Re-register your self-hosted runners on the destination instance. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." +1. Re-register your self-hosted runners on the destination instance. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." \ No newline at end of file diff --git a/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md index 86af66abf4..c38c209a49 100644 --- a/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Solucionar problemas no GitHub Actions para a sua empresa -intro: 'Solucionar problemas comuns que ocorrem ao usar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %}.' +title: Troubleshooting GitHub Actions for your enterprise +intro: 'Troubleshooting common issues that occur when using {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' permissions: 'Site administrators can troubleshoot {% data variables.product.prodname_actions %} issues and modify {% data variables.product.prodname_ghe_server %} configurations.' versions: ghes: '*' @@ -12,79 +12,74 @@ topics: redirect_from: - /admin/github-actions/troubleshooting-github-actions-for-your-enterprise shortTitle: Troubleshoot GitHub Actions -ms.openlocfilehash: ff78e1b68664d5eb0931bb98d325e22ae0c458f3 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145094987' --- -## Verificando a saúde de {% data variables.product.prodname_actions %} -Verifique a integridade do {% data variables.product.prodname_actions %} no {% data variables.product.product_location %} com o utilitário de linha de comando `ghe-actions-check`. Para obter mais informações, confira "[Utilitários de linha de comando](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-actions-check)" e "[Como acessar o shell administrativo (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)". +## Checking the health of {% data variables.product.prodname_actions %} -## Configurar executores auto-hospedados ao usar um certificado autoassinado por {% data variables.product.prodname_ghe_server %} +You can check the health of {% data variables.product.prodname_actions %} on {% data variables.location.product_location %} with the `ghe-actions-check` command-line utility. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-actions-check)" and "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." -{% data reusables.actions.enterprise-self-signed-cert %} Para obter mais informações, confira "[Como configurar o TLS](/admin/configuration/configuring-tls)". +## Configuring self-hosted runners when using a self-signed certificate for {% data variables.product.prodname_ghe_server %} -### Instalar o certificado na máquina do executor +{% data reusables.actions.enterprise-self-signed-cert %} For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." -Para um executor auto-hospedado conectar-se a um {% data variables.product.prodname_ghe_server %} usando um certificado autoassinado, você deverá instalar o certificado na máquina do executor para que a conexão seja mais rígida. +### Installing the certificate on the runner machine -Para as etapas necessárias para instalar um certificado, consulte a documentação do sistema operacional do seu executor. +For a self-hosted runner to connect to a {% data variables.product.prodname_ghe_server %} using a self-signed certificate, you must install the certificate on the runner machine so that the connection is security hardened. -### Configurar o Node.JS para usar o certificado +For the steps required to install a certificate, refer to the documentation for your runner's operating system. -A maioria das ações são escritas em JavaScript e são executadas usando Node.js, que não usa o armazenamento de certificados do sistema operacional. Para que o aplicativo do executor auto-hospedado use o certificado, você precisa definir a variável de ambiente `NODE_EXTRA_CA_CERTS` no computador do executor. +### Configuring Node.JS to use the certificate -Defina a variável de ambiente como uma variável de ambiente do sistema ou declare-a em um arquivo chamado _.env_ no diretório do aplicativo do executor auto-hospedado. +Most actions are written in JavaScript and run using Node.js, which does not use the operating system certificate store. For the self-hosted runner application to use the certificate, you must set the `NODE_EXTRA_CA_CERTS` environment variable on the runner machine. -Por exemplo: +You can set the environment variable as a system environment variable, or declare it in a file named _.env_ in the self-hosted runner application directory. + +For example: ```shell NODE_EXTRA_CA_CERTS=/usr/share/ca-certificates/extra/mycertfile.crt ``` -As variáveis de ambiente são lidas quando o aplicativo do executor auto-hospedado é iniciado. Portanto, você deve definir a variável de ambiente antes de configurar ou iniciar o aplicativo do executor auto-hospedado. Se a sua configuração de certificado for alterada, você deverá reiniciar o aplicativo do executor auto-hospedado. +Environment variables are read when the self-hosted runner application starts, so you must set the environment variable before configuring or starting the self-hosted runner application. If your certificate configuration changes, you must restart the self-hosted runner application. -### Configurar contêineres do Docker para usar o certificado +### Configuring Docker containers to use the certificate -Se você usa ações do contêiner do Docker ou contêineres de serviço nos seus fluxos de trabalho, você também deverá instalar o certificado na sua imagem do Docker, além de definir a variável de ambiente acima. +If you use Docker container actions or service containers in your workflows, you might also need to install the certificate in your Docker image in addition to setting the above environment variable. -## Configurar as definições de proxy HTTP para {% data variables.product.prodname_actions %} +## Configuring HTTP proxy settings for {% data variables.product.prodname_actions %} {% data reusables.actions.enterprise-http-proxy %} -Se essas configurações não estiverem definidas corretamente, você poderá receber erros como `Resource unexpectedly moved to https://` ao definir ou alterar sua configuração do {% data variables.product.prodname_actions %}. +If these settings aren't correctly configured, you might receive errors like `Resource unexpectedly moved to https://` when setting or changing your {% data variables.product.prodname_actions %} configuration. -## Os executores não se conectam a {% data variables.product.prodname_ghe_server %} com um novo nome de host +## Runners not connecting to {% data variables.product.prodname_ghe_server %} with a new hostname {% data reusables.enterprise_installation.changing-hostname-not-supported %} -Se você implantar {% data variables.product.prodname_ghe_server %} no seu ambiente com um novo nome de host e o antigo nome de host não resolver mais a sua instância, os executores auto-hospedados não conseguirão conectar-se ao nome de host antigo e não executarão nenhum trabalho. +If you deploy {% data variables.product.prodname_ghe_server %} in your environment with a new hostname and the old hostname no longer resolves to your instance, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs. -Você precisará atualizar a configuração dos seus executores auto-hospedados para usar o novo nome de host para {% data variables.product.product_location %}. Cada executor auto-hospedado exigirá um dos seguintes procedimentos: +You will need to update the configuration of your self-hosted runners to use the new hostname for {% data variables.location.product_location %}. Each self-hosted runner will require one of the following procedures: -* No diretório do aplicativo do executor auto-hospedado, edite os arquivos `.runner` e `.credentials` para substituir todas as menções do nome do host antigo pelo novo nome do host. Em seguida, reinicie o aplicativo do executor auto-hospedado. -* Remova o executor de {% data variables.product.prodname_ghe_server %} usando a interface do usuário e adicione-o novamente. Para obter mais informações, confira "[Como remover executores auto-hospedados](/actions/hosting-your-own-runners/removing-self-hosted-runners)" e "[Como adicionar executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)". +* In the self-hosted runner application directory, edit the `.runner` and `.credentials` files to replace all mentions of the old hostname with the new hostname, then restart the self-hosted runner application. +* Remove the runner from {% data variables.product.prodname_ghe_server %} using the UI, and re-add it. For more information, see "[Removing self-hosted runners](/actions/hosting-your-own-runners/removing-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." -## Trabalhos travados e limites de CPU e de memória das {% data variables.product.prodname_actions %} +## Stuck jobs and {% data variables.product.prodname_actions %} memory and CPU limits -{% data variables.product.prodname_actions %} é composto de vários serviços em execução em {% data variables.product.product_location %}. Por padrão, esses serviços são configurados com limites padrão de CPU e memória que devem funcionar para a maioria das instâncias. No entanto, usuários assíduos de {% data variables.product.prodname_actions %} talvez precisem para ajustar essas configurações. +{% data variables.product.prodname_actions %} is composed of multiple services running on {% data variables.location.product_location %}. By default, these services are set up with default CPU and memory limits that should work for most instances. However, heavy users of {% data variables.product.prodname_actions %} might need to adjust these settings. -É possível que você atinja o limite de CPU ou memória se você notar que os trabalhos não estão sendo iniciados (ainda que existam executores inativos), ou se o progresso do trabalho não estiver sendo atualizado ou alterando na interface do usuário. +You may be hitting the CPU or memory limits if you notice that jobs are not starting (even though there are idle runners), or if the job's progress is not updating or changing in the UI. -### 1. Verificar o uso total da CPU e de memória no console de gerenciamento +### 1. Check the overall CPU and memory usage in the management console -Acesse o console de gerenciamento e use o painel do monitor para inspecionar os gráficos gerais de CPU e memória em "Saúde do Sistema". Para obter mais informações, confira "[Como acessar o painel do monitor](/admin/enterprise-management/accessing-the-monitor-dashboard)". +Access the management console and use the monitor dashboard to inspect the overall CPU and memory graphs under "System Health". For more information, see "[Accessing the monitor dashboard](/admin/enterprise-management/accessing-the-monitor-dashboard)." -Se o uso geral de "Saúde do Sistema" da CPU estiver próximo a 100% ou não houver mais memória livre, {% data variables.product.product_location %} será executado na capacidade e precisará ser dimensionado. Para obter mais informações, confira "[Como aumentar os recursos de CPU ou de memória](/admin/enterprise-management/increasing-cpu-or-memory-resources)". +If the overall "System Health" CPU usage is close to 100%, or there is no free memory left, then {% data variables.location.product_location %} is running at capacity and needs to be scaled up. For more information, see "[Increasing CPU or memory resources](/admin/enterprise-management/increasing-cpu-or-memory-resources)." -### 2. Verificar o uso da CPU e de memória dos trabalhos do Nomad no console de gerenciamento +### 2. Check the Nomad Jobs CPU and memory usage in the management console -Se a "Saúde do Sistema" para o uso total da CPU e da memória estiver OK, acesse a seção "Trabalhos Normad" na parte inferior do painel e observe os gráficos "Valor porcentual da CPU" e "Uso da memória". +If the overall "System Health" CPU and memory usage is OK, scroll down the monitor dashboard page to the "Nomad Jobs" section, and look at the "CPU Percent Value" and "Memory Usage" graphs. -Cada seção nesses gráficos corresponde a um serviço. Para os serviços de {% data variables.product.prodname_actions %}, busque: +Each plot in these graphs corresponds to one service. For {% data variables.product.prodname_actions %} services, look for: * `mps_frontend` * `mps_backend` @@ -93,18 +88,18 @@ Cada seção nesses gráficos corresponde a um serviço. Para os serviços de {% * `actions_frontend` * `actions_backend` -Se qualquer um destes serviços estiver em ou perto de 100% de utilização da CPU ou se a memória estiver próxima do seu limite (2 GB por padrão), talvez seja necessário aumentar a atribuição de recursos para estes serviços. Tome nota de quais dos serviços acima estão no ou próximo do seu limite. +If any of these services are at or near 100% CPU utilization, or the memory is near their limit (2 GB by default), then the resource allocation for these services might need increasing. Take note of which of the above services are at or near their limit. -### 3. Aumentar a alocação de recurso para serviços no limite +### 3. Increase the resource allocation for services at their limit -1. Efetue o login no shell administrativo usando SSH. Para obter mais informações, confira "[Como acessar o shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)". -1. Execute o comando a seguir para ver quais recursos estão disponíveis para alocação: +1. Log in to the administrative shell using SSH. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." +1. Run the following command to see what resources are available for allocation: ```shell nomad node status -self ``` - Na saída, encontre a seção "Recursos alocados". Ele é semelhante ao exemplo a seguir: + In the output, find the "Allocated Resources" section. It looks similar to the following example: ``` Allocated Resources @@ -112,25 +107,25 @@ Se qualquer um destes serviços estiver em ou perto de 100% de utilização da C 7740/49600 MHZ 23 GiB/32 GiB 4.4 GiB/7.9 GiB ``` - Para a CPU e a memória, isso mostra a quantidade alocada ao **total** de **todos** os serviços (o valor à esquerda) e a quantidade que está disponível (o valor à direita). No exemplo acima, há 23 GiB de memória alocado para um total de 32 GiB. Isto significa que há 9 GiB de memória disponíveis para atribuição. + For CPU and memory, this shows how much is allocated to the **total** of **all** services (the left value) and how much is available (the right value). In the example above, there is 23 GiB of memory allocated out of 32 GiB total. This means there is 9 GiB of memory available for allocation. {% warning %} - **Aviso:** tenha cuidado para não alocar mais do que o total de recursos disponíveis ou os serviços não poderão ser iniciados. + **Warning:** Be careful not to allocate more than the total available resources, or services will fail to start. {% endwarning %} -1. Altere o diretório para `/etc/consul-templates/etc/nomad-jobs/actions`: +1. Change directory to `/etc/consul-templates/etc/nomad-jobs/actions`: ```shell cd /etc/consul-templates/etc/nomad-jobs/actions ``` - Neste diretório existem três arquivos que correspondem aos serviços de {% data variables.product.prodname_actions %} descritos anteriormente: + In this directory there are three files that correspond to the {% data variables.product.prodname_actions %} services from above: * `mps.hcl.ctmpl` * `token.hcl.ctmpl` * `actions.hcl.ctmpl` -1. Para os serviços que você identificou que precisam de ajuste, abra o arquivo correspondente e localize o grupo `resources` que se parece com o seguinte: +1. For the services that you identified that need adjustment, open the corresponding file and locate the `resources` group that looks like the following: ``` resources { @@ -142,9 +137,9 @@ Se qualquer um destes serviços estiver em ou perto de 100% de utilização da C } ``` - Os valores estão em MHz para recursos de CPU e em MB para recursos de memória. + The values are in MHz for CPU resources, and MB for memory resources. - Por exemplo, para aumentar os limites de recursos no exemplo acima para 1 GHz para a CPU e 4 GB de memória, altere-os para: + For example, to increase the resource limits in the above example to 1 GHz for the CPU and 4 GB of memory, change it to: ``` resources { @@ -155,39 +150,39 @@ Se qualquer um destes serviços estiver em ou perto de 100% de utilização da C } } ``` -1. Salve e feche o arquivo. -1. Execute `ghe-config-apply` para aplicar as alterações. +1. Save and exit the file. +1. Run `ghe-config-apply` to apply the changes. - Ao executar `ghe-config-apply`, se você observar uma saída como `Failed to run nomad job '/etc/nomad-jobs/.hcl'`, a alteração provavelmente terá recursos de CPU ou de memória alocados em excesso. Se isso acontecer, edite os arquivos de configuração novamente, reduza a CPU ou a memória alocada e execute `ghe-config-apply` novamente. -1. Depois que a configuração for aplicada, execute `ghe-actions-check` para verificar se os serviços do {% data variables.product.prodname_actions %} estão funcionando. + When running `ghe-config-apply`, if you see output like `Failed to run nomad job '/etc/nomad-jobs/.hcl'`, then the change has likely over-allocated CPU or memory resources. If this happens, edit the configuration files again and lower the allocated CPU or memory, then re-run `ghe-config-apply`. +1. After the configuration is applied, run `ghe-actions-check` to verify that the {% data variables.product.prodname_actions %} services are operational. {% ifversion fpt or ghec or ghes > 3.2 %} -## Solucionar problemas de falhas quando {% data variables.product.prodname_dependabot %} dispara fluxos de trabalho existentes +## Troubleshooting failures when {% data variables.product.prodname_dependabot %} triggers existing workflows {% data reusables.dependabot.beta-security-and-version-updates %} -Após configurar as atualizações de {% data variables.product.prodname_dependabot %} para {% data variables.product.product_location %}, você pode ver falhas quando os fluxos de trabalho existentes são acionados por eventos de {% data variables.product.prodname_dependabot %}. +After you set up {% data variables.product.prodname_dependabot %} updates for {% data variables.location.product_location %}, you may see failures when existing workflows are triggered by {% data variables.product.prodname_dependabot %} events. -Por padrão, as execuções de fluxo de trabalho do {% data variables.product.prodname_actions %} disparadas pelo {% data variables.product.prodname_dependabot %} dos eventos `push`, `pull_request`, `pull_request_review` ou `pull_request_review_comment` são tratados como se eles fossem abertos de um fork do repositório. Ao contrário dos fluxos de trabalho disparados por outros atores, isso significa que eles recebem o `GITHUB_TOKEN` somente leitura e não têm acesso a nenhum segredo que esteja normalmente disponível. Isso fará com que quaisquer fluxos de trabalho que tentam gravar no repositório falhem quando forem acionados por {% data variables.product.prodname_dependabot %}. +By default, {% data variables.product.prodname_actions %} workflow runs that are triggered by {% data variables.product.prodname_dependabot %} from `push`, `pull_request`, `pull_request_review`, or `pull_request_review_comment` events are treated as if they were opened from a repository fork. Unlike workflows triggered by other actors, this means they receive a read-only `GITHUB_TOKEN` and do not have access to any secrets that are normally available. This will cause any workflows that attempt to write to the repository to fail when they are triggered by {% data variables.product.prodname_dependabot %}. -Há três maneiras de resolver este problema: +There are three ways to resolve this problem: -1. Você pode atualizar seus fluxos de trabalho para que não sejam mais disparados pelo {% data variables.product.prodname_dependabot %} usando uma expressão como: `if: github.actor != 'dependabot[bot]'`. Para obter mais informações, confira "[Expressões](/actions/learn-github-actions/expressions)". -2. Modifique seus fluxos de trabalho para usar um processo de duas etapas que inclui `pull_request_target` que não tem essas limitações. Para obter mais informações, confira "[Como automatizar o {% data variables.product.prodname_dependabot %} com o {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions#responding-to-events)". -3. Forneça fluxos de trabalho disparados pelo acesso do {% data variables.product.prodname_dependabot %} aos segredos e permita que o termo `permissions` aumente o escopo padrão do `GITHUB_TOKEN`. Para obter mais informações, confira "[Como fornecer fluxos de trabalho disparados pelo acesso do {% data variables.product.prodname_dependabot %} aos segredos e às permissões aumentadas](#providing-workflows-triggered-by-dependabot-access-to-secrets-and-increased-permissions)" abaixo. +1. You can update your workflows so that they are no longer triggered by {% data variables.product.prodname_dependabot %} using an expression like: `if: github.actor != 'dependabot[bot]'`. For more information, see "[Expressions](/actions/learn-github-actions/expressions)." +2. You can modify your workflows to use a two-step process that includes `pull_request_target` which does not have these limitations. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions#responding-to-events)." +3. You can provide workflows triggered by {% data variables.product.prodname_dependabot %} access to secrets and allow the `permissions` term to increase the default scope of the `GITHUB_TOKEN`. For more information, see "[Providing workflows triggered by{% data variables.product.prodname_dependabot %} access to secrets and increased permissions](#providing-workflows-triggered-by-dependabot-access-to-secrets-and-increased-permissions)" below. -### Fornecendo fluxos de trabalho acionados pelo acesso de {% data variables.product.prodname_dependabot %} a segredos e permissões ampliadas +### Providing workflows triggered by {% data variables.product.prodname_dependabot %} access to secrets and increased permissions -1. Efetue o login no shell administrativo usando SSH. Para obter mais informações, confira "[Como acessar o shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)". -1. Para remover as limitações dos fluxos de trabalho acionados por {% data variables.product.prodname_dependabot %} em {% data variables.product.product_location %}, use o seguinte comando. +1. Log in to the administrative shell using SSH. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." +1. To remove the limitations on workflows triggered by {% data variables.product.prodname_dependabot %} on {% data variables.location.product_location %}, use the following command. ``` shell $ ghe-config app.actions.disable-dependabot-enforcement true ``` -1. Aplicar a configuração. +1. Apply the configuration. ```shell $ ghe-config-apply ``` -1. Volte para o {% data variables.product.prodname_ghe_server %}. +1. Return to {% data variables.product.prodname_ghe_server %}. {% endif %} @@ -195,38 +190,38 @@ Há três maneiras de resolver este problema: -## Solucionando problemas das ações agrupadas em {% data variables.product.prodname_actions %} +## Troubleshooting bundled actions in {% data variables.product.prodname_actions %} -Se você receber o erro a seguir ao instalar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %}, você poderá resolver o problema instalando as ações oficiais empacotadas e os fluxos de trabalho iniciais. +If you receive the following error when installing {% data variables.product.prodname_actions %} in {% data variables.product.prodname_ghe_server %}, you can resolve the problem by installing the official bundled actions and starter workflows. ```shell A part of the Actions setup had problems and needs an administrator to resolve. ``` -Para instalar as ações oficiais empacotadas e fluxos de trabalho iniciais dentro de uma organização designada em {% data variables.product.prodname_ghe_server %}, siga este procedimento. +To install the official bundled actions and starter workflows within a designated organization in {% data variables.product.prodname_ghe_server %}, follow this procedure. -1. Identifique uma organização que armazenará as ações oficiais agrupadas e os fluxos de trabalho iniciais. Você pode criar uma nova organização ou reutilizar uma já existente. - - Para criar uma organização, confira "[Como criar uma organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". - - Para obter assistência com a escolha de um nome para esta organização, confira "[Nomes reservados](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#reserved-names)". +1. Identify an organization that will store the official bundled actions and starter worflows. You can create a new organization or reuse an existing one. + - To create a new organization, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." + - For assistance with choosing a name for this organization, see "[Reserved Names](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#reserved-names)." -1. Efetue o login no shell administrativo usando SSH. Para obter mais informações, confira "[Como acessar o shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)". -1. Para designar sua organização como o local para armazenar as ações agrupadas, use o comando `ghe-config`, substituindo `ORGANIZATION` pelo nome da sua organização. +1. Log in to the administrative shell using SSH. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." +1. To designate your organization as the location to store the bundled actions, use the `ghe-config` command, replacing `ORGANIZATION` with the name of your organization. ```shell $ ghe-config app.actions.actions-org ORGANIZATION ``` - e: + and: ```shell $ ghe-config app.actions.github-org ORGANIZATION ``` -1. Para adicionar as ações empacotadas à sua organização, cancele a definição do SHA. +1. To add the bundled actions to your organization, unset the SHA. ```shell $ ghe-config --unset 'app.actions.actions-repos-sha1sum' ``` -1. Aplicar a configuração. +1. Apply the configuration. ```shell $ ghe-config-apply ``` -Depois de concluir essas etapas, retome a configuração do {% data variables.product.prodname_actions %} em "[Como gerenciar as permissões de acesso do GitHub Actions na sua empresa](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#managing-access-permissions-for-github-actions-in-your-enterprise)". +After you've completed these steps, you can resume configuring {% data variables.product.prodname_actions %} at "[Managing access permissions for GitHub Actions in your enterprise](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#managing-access-permissions-for-github-actions-in-your-enterprise)." {% endif %} diff --git a/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md b/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md index d13c7533b3..c9f9e75ca4 100644 --- a/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md +++ b/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md @@ -1,6 +1,6 @@ --- -title: Usar um ambiente de preparo -intro: 'Aprenda a usar {% data variables.product.prodname_actions %} com instâncias de preparo de {% data variables.product.prodname_ghe_server %}.' +title: Using a staging environment +intro: 'Learn about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %} staging instances.' versions: ghes: '*' type: how_to @@ -12,46 +12,41 @@ topics: redirect_from: - /admin/github-actions/using-a-staging-environment shortTitle: Use staging environment -ms.openlocfilehash: 3d244d25aae5a6e21b4db1cd04352343d6650975 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145095912' --- -## Sobre ambientes de preparo para {% data variables.product.product_name %} -Pode ser útil ter um ambiente de preparo ou de teste para {% data variables.product.product_location %} para que você possa testar atualizações ou novas funcionalidades antes de implementá-las no seu ambiente de produção. Para obter mais informações, confira "[Como configurar uma instância de preparo](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)". +## About staging environments for {% data variables.product.product_name %} -## Usar um ambiente de preparo com {% data variables.product.prodname_actions %} +It can be useful to have a staging or testing environment for {% data variables.location.product_location %}, so that you can test updates or new features before implementing them in your production environment. For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)." -Uma maneira comum de criar o ambiente de preparo é restaurar um backup da sua instância de produção {% data variables.product.product_name %} para uma nova máquina virtual no ambiente de preparo. Se você usa uma instância de preparo e planeja testar a funcionalidade do {% data variables.product.prodname_actions %}, examine a configuração de armazenamento no ambiente de preparo. +## Using a staging environment with {% data variables.product.prodname_actions %} -Depois de restaurar um backup do {% data variables.product.prodname_ghe_server %} para a instância de preparo, se você tentar exibir logs ou artefatos do {% data variables.product.prodname_actions %} existentes de fluxo de trabalho em sua instância de preparo, verá erros `404`, pois esses dados estarão ausentes do local de armazenamento de preparo. Para contornar os erros `404`, você pode copiar dados da produção para usar em seu ambiente de preparo. +A common way to create the staging environment is to restore a backup of your production {% data variables.product.product_name %} instance to a new virtual machine in the staging environment. If you use a staging instance and plan to test {% data variables.product.prodname_actions %} functionality, you should review your storage configuration in the staging environment. -### Configurando o armazenamento +After you restore a {% data variables.product.prodname_ghe_server %} backup to the staging instance, if you try to view logs or artifacts from existing {% data variables.product.prodname_actions %} workflow runs on your staging instance, you will see `404` errors, because this data will be missing from your staging storage location. To work around the `404` errors, you can copy data from production to use in your staging environment. -Ao configurar um ambiente de preparo que inclua uma instância do {% data variables.product.product_name %} com o {% data variables.product.prodname_actions %} habilitado, você deve usar uma configuração de armazenamento externo para o armazenamento do {% data variables.product.prodname_actions %} diferente do ambiente de produção. +### Configuring storage + +When you set up a staging environment that includes a {% data variables.product.product_name %} instance with {% data variables.product.prodname_actions %} enabled, you must use a different external storage configuration for {% data variables.product.prodname_actions %} storage than your production environment. {% warning %} -**Aviso**: se você não alterar a configuração de armazenamento, sua instância de preparo poderá gravar no mesmo armazenamento externo que você usa para produção, o que pode resultar em perda de dados. +**Warning**: If you don't change the storage configuration, your staging instance may be able to write to the same external storage that you use for production, which could result in loss of data. {% endwarning %} -Para obter mais informações sobre a configuração de armazenamento para {% data variables.product.prodname_actions %}, confira "[Introdução ao {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#enabling-github-actions-with-your-storage-provider)". +For more information about storage configuration for {% data variables.product.prodname_actions %}, 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-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#enabling-github-actions-with-your-storage-provider)." -### Copiar arquivos da produção para o preparo +### Copying files from production to staging -Para espelhar com mais precisão seu ambiente de produção, você pode copiar arquivos do local de armazenamento de produção do {% data variables.product.prodname_actions %} para o local de armazenamento de preparo. +To more accurately mirror your production environment, you can optionally copy files from your production storage location for {% data variables.product.prodname_actions %} to the staging storage location. -* Para uma conta de armazenamento do Azure, você pode usar [`azcopy`](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs#copy-all-containers-directories-and-blobs-to-another-storage-account). Por exemplo: +* For an Azure storage account, you can use [`azcopy`](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs#copy-all-containers-directories-and-blobs-to-another-storage-account). For example: ```shell azcopy copy 'https://SOURCE-STORAGE-ACCOUNT-NAME.blob.core.windows.net/SAS-TOKEN' 'https://DESTINATION-STORAGE-ACCOUNT-NAME.blob.core.windows.net/' --recursive ``` -* Para buckets do Amazon S3, você pode usar [`aws s3 sync`](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html). Por exemplo: +* For Amazon S3 buckets, you can use [`aws s3 sync`](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html). For example: ```shell - aws s3 sync s3://SOURCE-BUCKET s3://DESTINATION-BUCKET + aws s3 sync s3://SOURCE-BUCKET s3://DESTINATION-BUCKET ``` diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md index 5a139d0d8d..be47b2ae56 100644 --- a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md +++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md @@ -1,6 +1,6 @@ --- -title: Habilitar o GitHub Actions com MinIO Gateway para armazenamento NAS -intro: 'Você pode habilitar {% data variables.product.prodname_actions %} no {% data variables.product.prodname_ghe_server %} e usar o Gateway MinIO para armazenamento NAS para armazenar dados gerados por execuções de fluxo de trabalho.' +title: Enabling GitHub Actions with MinIO Gateway for NAS storage +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use MinIO Gateway for NAS storage to store data generated by workflow runs.' permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' versions: ghes: '*' @@ -13,35 +13,36 @@ topics: redirect_from: - /admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage shortTitle: MinIO Gateway for NAS storage -ms.openlocfilehash: 9fced80eb2a486ffae44d21f3fad278a933eb92d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146682306' --- + {% data reusables.actions.minio-gateways-removal %} -## Pré-requisitos +## Prerequisites -Antes de habilitar {% data variables.product.prodname_actions %}, certifique-se de que você realizou os seguintes passos: +Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: -* Para evitar contenção de recursos no dispositivo, recomendamos que o MinIO seja hospedado separadamente de {% data variables.product.product_location %}. -* Crie seu bucket para armazenar dados de fluxo de trabalho. {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %} +* To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.location.product_location %}. +* Create your bucket for storing workflow data. {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %} {% data reusables.actions.enterprise-common-prereqs %} -## Habilitar {% data variables.product.prodname_actions %} com MinIO Gateway para armazenamento NAS +## Enabling {% data variables.product.prodname_actions %} with MinIO Gateway for NAS storage -{% data reusables.enterprise_installation.ssh-into-instance %} {% data reusables.actions.perform-blob-storage-precheck %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.actions %} {% data reusables.actions.enterprise-enable-checkbox %} -1. Em "Armazenamento de Logs e Artefatos", selecione **Amazon S3** e insira os detalhes do bucket de armazenamento: +{% data reusables.enterprise_installation.ssh-into-instance %} +{% data reusables.actions.perform-blob-storage-precheck %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details: - * **URL de Serviço da AWS**: a URL para o serviço do MinIO. Por exemplo, `https://my-minio.example:9000`. - * **Bucket da AWS S3**: o nome do bucket S3. - * **Chave de Acesso da AWS S3** e **Chave Secreta da AWS S3**: o `MINIO_ACCESS_KEY` e o `MINIO_SECRET_KEY` usado para sua instância do MinIO. + * **AWS Service URL**: The URL to your MinIO service. For example, `https://my-minio.example:9000`. + * **AWS S3 Bucket**: The name of your S3 bucket. + * **AWS S3 Access Key** and **AWS S3 Secret Key**: The `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` used for your MinIO instance. - ![Botão de opção para selecionar o Amazon S3 Storage e os campos para a configuração do MinIO](/assets/images/enterprise/management-console/actions-minio-s3-storage.png) -1. Em "Armazenamento de Logs e Artefatos", selecione **Forçar estilo de caminho**. - ![Caixa de seleção de Forçar estilo de caminho](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) {% data reusables.enterprise_management_console.save-settings %} + ![Radio button for selecting Amazon S3 Storage and fields for MinIO configuration](/assets/images/enterprise/management-console/actions-minio-s3-storage.png) +1. Under "Artifact & Log Storage", select **Force path style**. + ![Checkbox to Force path style](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) +{% data reusables.enterprise_management_console.save-settings %} {% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md index a89c04e820..dec9d74057 100644 --- a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md +++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md @@ -1,6 +1,6 @@ --- -title: Gerenciando executores auto-hospedados para atualizações de Dependabot na sua empresa -intro: 'Você pode criar executores dedicados para {% data variables.product.product_location %} que {% data variables.product.prodname_dependabot %} usa para criar pull requests a fim de ajudar a proteger e manter as dependências usadas em repositórios da sua empresa.' +title: Managing self-hosted runners for Dependabot updates on your enterprise +intro: 'You can create dedicated runners for {% data variables.location.product_location %} that {% data variables.product.prodname_dependabot %} uses to create pull requests to help secure and maintain the dependencies used in repositories on your enterprise.' redirect_from: - /admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates allowTitleToDifferFromFilename: true @@ -13,47 +13,44 @@ topics: - Dependabot - Dependencies shortTitle: Dependabot updates -ms.openlocfilehash: 68fa6772ea2312f3cc0440d76808ee6816eead8e -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146681066' --- + {% data reusables.dependabot.beta-security-and-version-updates %} -## Sobre executores auto-hospedados para {% data variables.product.prodname_dependabot_updates %} +## About self-hosted runners for {% data variables.product.prodname_dependabot_updates %} -Você pode ajudar os usuários de {% data variables.product.product_location %} a criar e manter o código seguro, configurando as atualizações de segurança e versão de {% data variables.product.prodname_dependabot %}. Com {% data variables.product.prodname_dependabot_updates %}, os desenvolvedores podem configurar repositórios para que suas dependências sejam atualizadas e mantidas seguras automaticamente. Para obter mais informações, confira "[Como habilitar o {% data variables.product.prodname_dependabot %} para sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)". +You can help users of {% data variables.location.product_location %} to create and maintain secure code by setting up {% data variables.product.prodname_dependabot %} security and version updates. With {% data variables.product.prodname_dependabot_updates %}, developers can configure repositories so that their dependencies are updated and kept secure automatically. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." -Para usar {% data variables.product.prodname_dependabot_updates %} em {% data variables.product.product_location %}, você deve configurar runnexecutores ers auto-hospedados para criar os pull requests que atualizarão dependências. +To use {% data variables.product.prodname_dependabot_updates %} on {% data variables.location.product_location %}, you must configure self-hosted runners to create the pull requests that will update dependencies. -## Pré-requisitos +## Prerequisites -{% ifversion dependabot-updates-github-connect %} A configuração de executores auto-hospedados é apenas uma etapa no meio do processo para habilitar {% data variables.product.prodname_dependabot_updates %}. Há várias etapas que você deve seguir antes dessas etapas, incluindo a configuração de {% data variables.product.product_location %} para usar {% data variables.product.prodname_actions %} com corredores auto-hospedados. Para obter mais informações, confira "[Como habilitar o {% data variables.product.prodname_dependabot %} para sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)". -{% else %} Antes de configurar os executores auto-hospedados para as {% data variables.product.prodname_dependabot_updates %}, você precisa: +{% ifversion dependabot-updates-github-connect %} +Configuring self-hosted runners is only one step in the middle of the process for enabling {% data variables.product.prodname_dependabot_updates %}. There are several steps you must follow before these steps, including configuring {% data variables.location.product_location %} to use {% data variables.product.prodname_actions %} with self-hosted runners. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." +{% else %} +Before you configure self-hosted runners for {% data variables.product.prodname_dependabot_updates %}, you must: -- Configurar {% data variables.product.product_location %} para usar {% data variables.product.prodname_actions %} com executores auto-hospedados. Para obter mais informações, confira "[Introdução ao {% data variables.product.prodname_actions %} para GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)". -- Habilite {% data variables.product.prodname_dependabot_alerts %} para sua empresa. Para obter mais informações, confira "[Como habilitar o {% data variables.product.prodname_dependabot %} para sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)". +- Configure {% data variables.location.product_location %} to use {% data variables.product.prodname_actions %} with self-hosted runners. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)." +- Enable {% data variables.product.prodname_dependabot_alerts %} for your enterprise. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% endif %} -## Configurando executores auto-hospedados para {% data variables.product.prodname_dependabot_updates %} +## Configuring self-hosted runners for {% data variables.product.prodname_dependabot_updates %} -Depois de configurar {% data variables.product.product_location %} para usar {% data variables.product.prodname_actions %}, você deverá adicionar executores auto-hospedados para {% data variables.product.prodname_dependabot_updates %}. +After you configure {% data variables.location.product_location %} to use {% data variables.product.prodname_actions %}, you need to add self-hosted runners for {% data variables.product.prodname_dependabot_updates %}. -### Requisitos do sistema para executores de {% data variables.product.prodname_dependabot %} +### System requirements for {% data variables.product.prodname_dependabot %} runners -Qualquer VM que você usar para executores de {% data variables.product.prodname_dependabot %} deve atender aos requisitos para executores auto-hospedados. Além disso, eles têm de cumprir os seguintes requisitos. +Any VM that you use for {% data variables.product.prodname_dependabot %} runners must meet the requirements for self-hosted runners. In addition, they must meet the following requirements. -- Sistema operacional Linux{% ifversion ghes < 3.5 %} -- Git instalado{% endif %} -- Docker instalado com acesso para os usuários do executor: - - Recomendamos instalar o Docker no modo sem raiz e configurar os executores para acessar o Docker sem privilégios `root`. - - Como alternativa, instale o Docker e dê aos usuários do executor privilégios elevados para executar o Docker. +- Linux operating system{% ifversion ghes < 3.5 %} +- Git installed{% endif %} +- Docker installed with access for the runner users: + - We recommend installing Docker in rootless mode and configuring the runners to access Docker without `root` privileges. + - Alternatively, install Docker and give the runner users raised privileges to run Docker. -Os requisitos de CPU e memória dependerão do número de executores simultâneos que você implanta em uma determinada VM. Como orientação, criamos de forma bem-sucedida 20 executores em uma única máquina CPU de 8 GB, mas, em última análise, seus requisitos de CPU e memória dependerão fortemente da atualização dos repositórios. Alguns ecossistemas exigirão mais recursos do que outros. +The CPU and memory requirements will depend on the number of concurrent runners you deploy on a given VM. As guidance, we have successfully set up 20 runners on a single 2 CPU 8GB machine, but ultimately, your CPU and memory requirements will heavily depend on the repositories being updated. Some ecosystems will require more resources than others. -Se você especificar mais de 14 executores simultâneos em uma VM, também precisará atualizar a configuração `/etc/docker/daemon.json` do Docker para aumentar o número padrão de redes que o Docker pode criar. +If you specify more than 14 concurrent runners on a VM, you must also update the Docker `/etc/docker/daemon.json` configuration to increase the default number of networks Docker can create. ``` { @@ -63,23 +60,23 @@ Se você especificar mais de 14 executores simultâneos em uma VM, também preci } ``` -### Requisitos da rede para executores de {% data variables.product.prodname_dependabot %} +### Network requirements for {% data variables.product.prodname_dependabot %} runners -Os executores de {% data variables.product.prodname_dependabot %} exigem acesso à internet pública, {% data variables.product.prodname_dotcom_the_website %} e a todos os registros internos que serão usados nas atualizações de {% data variables.product.prodname_dependabot %}. Para minimizar o risco para sua rede interna, você deve limitar o acesso da Máquina Virtual (VM) à sua rede interna. Isto reduz o potencial de danos nos sistemas internos se um executor fizer o download de uma dependência capturada. +{% data variables.product.prodname_dependabot %} runners require access to the public internet, {% data variables.product.prodname_dotcom_the_website %}, and any internal registries that will be used in {% data variables.product.prodname_dependabot %} updates. To minimize the risk to your internal network, you should limit access from the Virtual Machine (VM) to your internal network. This reduces the potential for damage to internal systems if a runner were to download a hijacked dependency. -### Adicionando executores auto-hospedados para atualizações de {% data variables.product.prodname_dependabot %} +### Adding self-hosted runners for {% data variables.product.prodname_dependabot %} updates -1. Provisionamento de executores auto-hospedados no nível da conta do repositório, organização ou empresa. Para obter mais informações, confira "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" e "[Como adicionar executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)". +1. Provision self-hosted runners, at the repository, organization, or enterprise account level. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." -2. Configure os executores auto-hospedados com os requisitos descritos acima. Por exemplo, em uma VM que executa o Ubuntu 20.04:{% ifversion ghes < 3.5 %} +2. Set up the self-hosted runners with the requirements described above. For example, on a VM running Ubuntu 20.04 you would:{% ifversion ghes < 3.5 %} - - Verifique se o Git está instalado: `command -v git`{% endif %} - - Instale o Docker e certifique-se de que os usuários do executor tenham acesso ao Docker. Para obter mais informações, consulte a documentação do Docker. - - [Instalar o mecanismo do Docker no Ubuntu](https://docs.docker.com/engine/install/ubuntu/) - - Abordagem recomendada: [executar o daemon do Docker como um usuário não raiz (modo sem raiz)](https://docs.docker.com/engine/security/rootless/) - - Abordagem alternativa: [gerenciar o Docker como um usuário não raiz](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) - - Verifique se os executores têm acesso à internet pública e só podem acessar as redes internas de que {% data variables.product.prodname_dependabot %} precisa. + - Verify that Git is installed: `command -v git`{% endif %} + - Install Docker and ensure that the runner users have access to Docker. For more information, see the Docker documentation. + - [Install Docker Engine on Ubuntu](https://docs.docker.com/engine/install/ubuntu/) + - Recommended approach: [Run the Docker daemon as a non-root user (Rootless mode)](https://docs.docker.com/engine/security/rootless/) + - Alternative approach: [Manage Docker as a non-root user](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) + - Verify that the runners have access to the public internet and can only access the internal networks that {% data variables.product.prodname_dependabot %} needs. -3. Atribua um rótulo `dependabot` a cada executor que deseja que o {% data variables.product.prodname_dependabot %} use. Para obter mais informações, confira "[Como usar rótulos com executores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners#assigning-a-label-to-a-self-hosted-runner)". +3. Assign a `dependabot` label to each runner you want {% data variables.product.prodname_dependabot %} to use. For more information, see "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners#assigning-a-label-to-a-self-hosted-runner)." -4. Opcionalmente, habilite os fluxos de trabalho acionados por {% data variables.product.prodname_dependabot %} para usar permissões além das permissões somente leitura e ter acesso a todos os segredos que estão normalmente disponíveis. Para obter mais informações, confira "[Solução de problemas do {% data variables.product.prodname_actions %} para sua empresa](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise#enabling-workflows-triggered-by-dependabot-access-to-dependabot-secrets-and-increased-permissions)". +4. Optionally, enable workflows triggered by {% data variables.product.prodname_dependabot %} to use more than read-only permissions and to have access to any secrets that are normally available. For more information, see "[Troubleshooting {% data variables.product.prodname_actions %} for your enterprise](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise#enabling-workflows-triggered-by-dependabot-access-to-dependabot-secrets-and-increased-permissions)." diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md index 53143aafdb..c8553798a2 100644 --- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md @@ -33,7 +33,7 @@ topics: {% data variables.product.prodname_actions %} helps your team work faster at scale. When large repositories start using {% data variables.product.prodname_actions %}, teams merge significantly more pull requests per day, and the pull requests are merged significantly faster. For more information, see "[Writing and shipping code faster](https://octoverse.github.com/writing-code-faster/#scale-through-automation)" in the State of the Octoverse. -You can create your own unique automations, or you can use and adapt workflows from our ecosystem of over 10,000 actions built by industry leaders and the open source community. {% ifversion ghec %}For more information, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."{% else %}You can restrict your developers to using actions that exist on {% data variables.product.product_location %}, or you can allow your developers to access actions on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About using actions in your enterprise](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)."{% endif %} +You can create your own unique automations, or you can use and adapt workflows from our ecosystem of over 10,000 actions built by industry leaders and the open source community. {% ifversion ghec %}For more information, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."{% else %}You can restrict your developers to using actions that exist on {% data variables.location.product_location %}, or you can allow your developers to access actions on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About using actions in your enterprise](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)."{% endif %} {% data variables.product.prodname_actions %} is developer friendly, because it's integrated directly into the familiar {% data variables.product.product_name %} experience. @@ -50,7 +50,7 @@ You can create your own unique automations, or you can use and adapt workflows f {% data reusables.actions.migrating-enterprise %} {% ifversion ghes %} -{% data reusables.actions.ghes-actions-not-enabled-by-default %} After you finish planning, you can follow the instructions for enabling {% data variables.product.prodname_actions %}. For example, you may need to upgrade the CPU and memory resources for {% data variables.product.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server)." +{% data reusables.actions.ghes-actions-not-enabled-by-default %} After you finish planning, you can follow the instructions for enabling {% data variables.product.prodname_actions %}. For example, you may need to upgrade the CPU and memory resources for {% data variables.location.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server)." {% else %} After you finish planning, you can follow the instructions for getting started with {% data variables.product.prodname_actions %}. For more information, see {% ifversion ghec %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_cloud %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud)."{% elsif ghae %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)."{% endif %} diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md index b033e2fe21..babd01f28f 100644 --- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md @@ -1,7 +1,7 @@ --- -title: Primeiros passos com o GitHub Actions para o GitHub Enterprise Server +title: Getting started with GitHub Actions for GitHub Enterprise Server shortTitle: Get started -intro: 'Saiba mais sobre como habilitar e configurar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %} pela primeira vez.' +intro: 'Learn about enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} for the first time.' permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' redirect_from: - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage @@ -14,45 +14,39 @@ type: how_to topics: - Actions - Enterprise -ms.openlocfilehash: 886f057de3893ae10dbddda6c1ee03d428511677 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147580572' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## Sobre o {% data variables.product.prodname_actions %} no {% data variables.product.prodname_ghe_server %} +## About {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} -Este artigo explica como os administradores do site podem configurar {% data variables.product.prodname_ghe_server %} para usar {% data variables.product.prodname_actions %}. +This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}. {% data reusables.enterprise.upgrade-ghes-for-actions %} -{% data reusables.actions.ghes-actions-not-enabled-by-default %} Você deberá determinar se a sua instância possui recursos adequados de CPU e memória para lidar com a carga do {% data variables.product.prodname_actions %} sem causar perda de desempenho e possivelmente aumentar esses recursos. Você também deverá decidir qual provedor de armazenamento usará para o armazenamento de blobs necessário para armazenar os artefatos{% ifversion actions-caching %} e caches{% endif %} gerados pelas execuções de fluxo de trabalho. Em seguida, você irá habilitar {% data variables.product.prodname_actions %} para a sua empresa, gerenciar permissões de acesso e adicionar executores auto-hospedados para executar fluxos de trabalho. +{% data reusables.actions.ghes-actions-not-enabled-by-default %} You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from {% data variables.product.prodname_actions %} without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts{% ifversion actions-caching %} and caches{% endif %} generated by workflow runs. Then, you'll enable {% data variables.product.prodname_actions %} for your enterprise, manage access permissions, and add self-hosted runners to run workflows. {% data reusables.actions.introducing-enterprise %} {% data reusables.actions.migrating-enterprise %} -## Revisar os requisitos de hardware +## Review hardware requirements {%- ifversion ghes < 3.6 %} -Os recursos de CPU e memória disponíveis para {% data variables.product.product_location %} determinam o número de trabalhos que podem ser executados simultaneamente sem perda de desempenho. {% data reusables.actions.minimum-hardware %} +The CPU and memory resources available to {% data variables.location.product_location %} determine the number of jobs that can be run concurrently without performance loss. {% data reusables.actions.minimum-hardware %} -O pico de trabalhos simultâneos rodando sem perda de desempenho depende de fatores como duração do trabalho, uso de artefatos, número de repositórios em execução de ações, e quanto outro trabalho sua instância está fazendo não relacionado a ações. Os testes internos no GitHub demonstraram os objetivos de desempenho a seguir para o GitHub Enterprise Server em uma série de configurações de CPU e memória: +The peak quantity of concurrent jobs running without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations: {% endif %} {%- ifversion ghes > 3.5 %} -Os recursos de CPU e memória disponíveis para {% data variables.product.product_location %} determinam o número de executores que podem ser configurados sem perda de desempenho. {% data reusables.actions.minimum-hardware %} +The CPU and memory resources available to {% data variables.location.product_location %} determine the number of runners that can be configured without performance loss. {% data reusables.actions.minimum-hardware %} -A quantidade máxima de executores conectados sem perda de desempenho depende de fatores como duração do trabalho, uso de artefatos, número de repositórios executando ações e quantos outros trabalhos sua instância está realizando não relacionados a ações. Os testes internos no GitHub demonstraram os objetivos de desempenho a seguir para o GitHub Enterprise Server em uma série de configurações de CPU e memória: +The peak quantity of connected runners without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations: {% endif %} @@ -60,7 +54,7 @@ A quantidade máxima de executores conectados sem perda de desempenho depende de {% data reusables.actions.hardware-requirements-3.2 %} -A simultaneidade máxima foi medida usando vários repositórios, a duração do trabalho de aproximadamente dez minutos e o upload de artefato de 10 MB. Você pode ter um desempenho diferente dependendo dos níveis gerais de atividade na sua instância. +Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. {%- endif %} @@ -68,7 +62,7 @@ A simultaneidade máxima foi medida usando vários repositórios, a duração do {% data reusables.actions.hardware-requirements-3.3 %} -A simultaneidade máxima foi medida usando vários repositórios, a duração do trabalho de aproximadamente dez minutos e o upload de artefato de 10 MB. Você pode ter um desempenho diferente dependendo dos níveis gerais de atividade na sua instância. +Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. {%- endif %} @@ -76,7 +70,7 @@ A simultaneidade máxima foi medida usando vários repositórios, a duração do {% data reusables.actions.hardware-requirements-3.4 %} -A simultaneidade máxima foi medida usando vários repositórios, a duração do trabalho de aproximadamente dez minutos e o upload de artefato de 10 MB. Você pode ter um desempenho diferente dependendo dos níveis gerais de atividade na sua instância. +Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. {%- endif %} @@ -84,11 +78,11 @@ A simultaneidade máxima foi medida usando vários repositórios, a duração do {% data reusables.actions.hardware-requirements-3.5 %} -Simultaneidade máxima medida pelo {% data variables.product.company_short %} usando vários repositórios, a duração do trabalho de aproximadamente 10 minutos e uploads de artefato de 10 MB. Você pode ter um desempenho diferente dependendo dos níveis gerais de atividade na sua instância. +{% data variables.product.company_short %} measured maximum concurrency using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. {% note %} -**Observação:** a partir do {% data variables.product.prodname_ghe_server %} 3.5, os testes internos da {% data variables.product.company_short %} usam CPUs de terceira geração para refletir melhor uma configuração típica do cliente. Essa alteração na CPU representa uma pequena parte das alterações nas metas de desempenho nesta versão do {% data variables.product.prodname_ghe_server %}. +**Note:** Beginning with {% data variables.product.prodname_ghe_server %} 3.5, {% data variables.product.company_short %}'s internal testing uses 3rd generation CPUs to better reflect a typical customer configuration. This change in CPU represents a small portion of the changes to performance targets in this version of {% data variables.product.prodname_ghe_server %}. {% endnote %} @@ -99,20 +93,21 @@ Simultaneidade máxima medida pelo {% data variables.product.company_short %} us {% data reusables.actions.hardware-requirements-3.6 %} -{% data variables.product.company_short %} mediu o máximo de executores conectados usando vários repositórios, duração do trabalho de aproximadamente 10 minutos e uploads de artefatos de 10 MB. Você pode ter um desempenho diferente dependendo dos níveis gerais de atividade na sua instância. +{% data variables.product.company_short %} measured maximum connected runners using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. {% note %} -**Observações:** +**Notes:** -- Começando com o {% data variables.product.prodname_ghe_server %} 3.6, o {% data variables.product.company_short %} documenta executores conectados em oposição a trabalhos simultâneos. Os executores conectados representam o maior número de executores que você pode conectar e esperar utilizar. Também deve ser observado que conectar mais executores que o esperado pode afetar negativamente o desempenho. +- Beginning with {% data variables.product.prodname_ghe_server %} 3.6, {% data variables.product.company_short %} documents connected runners as opposed to concurrent jobs. Connected runners represents the most runners you can connect and expect to utilize. It should also be noted that connecting more runners than you can expect to utilize can negatively impact performance. -- Começando com o {% data variables.product.prodname_ghe_server %} 3.5, os testes internos da {% data variables.product.company_short %} usam CPUs de terceira geração para refletir melhor uma configuração típica do cliente. Essa alteração na CPU representa uma pequena parte das alterações nas metas de desempenho nesta versão do {% data variables.product.prodname_ghe_server %}. -{% endnote %} {%- endif %} +- Beginning with {% data variables.product.prodname_ghe_server %} 3.5, {% data variables.product.company_short %}'s internal testing uses 3rd generation CPUs to better reflect a typical customer configuration. This change in CPU represents a small portion of the changes to performance targets in this version of {% data variables.product.prodname_ghe_server %}. +{% endnote %} +{%- endif %} -Se você planeja habilitar {% data variables.product.prodname_actions %} para os usuários de uma instância existente, revise os níveis de atividade para usuários e automações na instância e garanta que você tenha fornecido CPU e memória adequadas para seus usuários. Para obter mais informações sobre como monitorar a capacidade e o desempenho do {% data variables.product.prodname_ghe_server %}, confira "[Como monitorar seu dispositivo](/admin/enterprise-management/monitoring-your-appliance)". +If you plan to enable {% data variables.product.prodname_actions %} for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. For more information about monitoring the capacity and performance of {% data variables.product.prodname_ghe_server %}, see "[Monitoring your appliance](/admin/enterprise-management/monitoring-your-appliance)." -Para obter mais informações sobre os requisitos mínimos de hardware para {% data variables.product.product_location %}, consulte as considerações sobre hardware para a plataforma da sua instância. +For more information about minimum hardware requirements for {% data variables.location.product_location %}, 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) @@ -126,66 +121,66 @@ Para obter mais informações sobre os requisitos mínimos de hardware para {% d {% ifversion ghes > 3.4 %} -Opcionalmente, você pode limitar o consumo de recursos em {% data variables.product.product_location %} ao configurar um limite de taxa para {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Configuração de limites de taxas](/admin/configuration/configuring-your-enterprise/configuring-rate-limits#configuring-rate-limits-for-github-actions)". +Optionally, you can limit resource consumption on {% data variables.location.product_location %} by configuring a rate limit for {% data variables.product.prodname_actions %}. For more information, see "[Configuring rate limits](/admin/configuration/configuring-your-enterprise/configuring-rate-limits#configuring-rate-limits-for-github-actions)." {% endif %} -## Requisitos de armazenamento externo +## External storage requirements -Para habilitar o {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %}, você deve ter acesso ao armazenamento externo do blob. +To enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}, you must have access to external blob storage. -O {% data variables.product.prodname_actions %} usa o armazenamento de blobs para armazenar os dados gerados pelas execuções de fluxo de trabalho, como logs de fluxo de trabalho{% ifversion actions-caching %}, caches{% endif %} e artefatos de build carregados pelo usuário. A quantidade de armazenamento necessária depende do seu uso de {% data variables.product.prodname_actions %}. Somente uma única configuração de armazenamento externo é compatível, e você não pode usar vários provedores de armazenamento ao mesmo tempo. +{% data variables.product.prodname_actions %} uses blob storage to store data generated by workflow runs, such as workflow logs{% ifversion actions-caching %}, caches,{% endif %} and user-uploaded build artifacts. The amount of storage required depends on your usage of {% data variables.product.prodname_actions %}. Only a single external storage configuration is supported, and you can't use multiple storage providers at the same time. -{% data variables.product.prodname_actions %} é compatível com estes provedores de armazenamento: +{% data variables.product.prodname_actions %} supports these storage providers: -* Armazenamento de Blobs do Azure +* Azure Blob storage * Amazon S3 -* MinIO Gateway compatível com S3 para NAS +* S3-compatible MinIO Gateway for NAS {% note %} -**Observação:** esses são os únicos provedores de armazenamento aos quais o {% data variables.product.company_short %} dá suporte e pode fornecer assistência. Outros provedores de armazenamento compatíveis com a API do S3 provavelmente não funcionarão devido a diferenças em relação à API do S3. [Fale conosco](https://support.github.com/contact) para solicitar suporte para provedores de armazenamento adicionais. +**Note:** These are the only storage providers that {% data variables.product.company_short %} supports and can provide assistance with. Other S3 API-compatible storage providers are unlikely to work due to differences from the S3 API. [Contact us](https://support.github.com/contact) to request support for additional storage providers. {% endnote %} {% data reusables.actions.minio-gateways-removal %} -Antes de habilitar o {% data variables.product.prodname_actions %}, teste sua configuração de armazenamento no shell administrativo com o utilitário `ghe-actions-precheck`. Para obter mais informações, confira "[Utilitários de linha de comando](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-actions-check)" e "[Como acessar o shell administrativo (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)". +Before you enable {% data variables.product.prodname_actions %}, you can test your storage configuration from the administrative shell with the `ghe-actions-precheck` utility. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-actions-check)" and "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." -## Considerações de rede +## Networking considerations -{% data reusables.actions.proxy-considerations %} Para obter mais informações sobre como usar um proxy com o {% data variables.product.prodname_ghe_server %}, confira "[Como configurar um servidor proxy Web de saída](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)". +{% data reusables.actions.proxy-considerations %} For more information about using a proxy with {% data variables.product.prodname_ghe_server %}, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)." {% ifversion ghes %} -## Habilitar {% data variables.product.prodname_actions %} com o seu provedor de armazenamento +## Enabling {% data variables.product.prodname_actions %} with your storage provider -Siga um dos procedimentos abaixo para habilitar {% data variables.product.prodname_actions %} com o seu provedor de armazenamento escolhido: +Follow one of the procedures below to enable {% data variables.product.prodname_actions %} with your chosen storage provider: -* [Como habilitar o GitHub Actions com o Armazenamento de Blobs do Azure](/admin/github-actions/enabling-github-actions-with-azure-blob-storage) -* [Como habilitar o GitHub Actions com armazenamento do Amazon S3](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage) -* [Como habilitar o GitHub Actions com o Gateway do MinIO para o armazenamento NAS](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage) +* [Enabling GitHub Actions with Azure Blob storage](/admin/github-actions/enabling-github-actions-with-azure-blob-storage) +* [Enabling GitHub Actions with Amazon S3 storage](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage) +* [Enabling GitHub Actions with MinIO Gateway for NAS storage](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage) -## Gerenciar as permissões de acesso para {% data variables.product.prodname_actions %} na sua empres +## Managing access permissions for {% data variables.product.prodname_actions %} in your enterprise -Você pode usar políticas para gerenciar o acesso a {% data variables.product.prodname_actions %}. Para obter mais informações, confira "[Como impor políticas do GitHub Actions na sua empresa](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)". +You can use policies to manage access to {% data variables.product.prodname_actions %}. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." -## Adicionar executores auto-hospedados +## Adding self-hosted runners {% data reusables.actions.enterprise-github-hosted-runners %} -Para executar fluxos de trabalho de {% data variables.product.prodname_actions %}, você deve adicionar executores auto-hospedados. Você pode adicionar executores auto-hospedados nos níveis da empresa, organização ou repositório. Para obter mais informações, confira "[Como adicionar executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)". +To run {% data variables.product.prodname_actions %} workflows, you need to add self-hosted runners. You can add self-hosted runners at the enterprise, organization, or repository levels. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." -## Gerenciar quais ações podem ser usadas na sua empresa +## Managing which actions can be used in your enterprise -Você pode controlar quais ações os usuários têm permissão para usar na sua empresa. Isso inclui a configuração de {% data variables.product.prodname_github_connect %} para acesso automático às ações de {% data variables.product.prodname_dotcom_the_website %}, ou a sincronização manual das ações de {% data variables.product.prodname_dotcom_the_website %}. +You can control which actions your users are allowed to use in your enterprise. This includes setting up {% data variables.product.prodname_github_connect %} for automatic access to actions from {% data variables.product.prodname_dotcom_the_website %}, or manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}. -Para obter mais informações, confira "[Sobre como usar ações na sua empresa](/admin/github-actions/about-using-actions-in-your-enterprise)". +For more information, see "[About using actions in your enterprise](/admin/github-actions/about-using-actions-in-your-enterprise)." {% data reusables.actions.general-security-hardening %} {% endif %} -## Nomes reservados +## Reserved names -Quando você habilita o {% data variables.product.prodname_actions %} para sua empresa, duas organizações são criadas: `github` e `actions`. Se a sua empresa já usar o nome da organização `github`, `github-org` (ou `github-github-org` se `github-org` também estiver em uso) será usado. Se a sua empresa já usar o nome da organização `actions`, `github-actions` (ou `github-actions-org` se `github-actions` também estiver em uso) será usado. Uma vez que as ações são habilitadas, você não poderá usar mais esses nomes. +When you enable {% data variables.product.prodname_actions %} for your enterprise, two organizations are created: `github` and `actions`. If your enterprise already uses the `github` organization name, `github-org` (or `github-github-org` if `github-org` is also in use) will be used instead. If your enterprise already uses the `actions` organization name, `github-actions` (or `github-actions-org` if `github-actions` is also in use) will be used instead. Once actions is enabled, you won't be able to use these names anymore. diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md index 2e27bf07bd..8fc4c6c049 100644 --- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md @@ -18,7 +18,7 @@ topics: {% data reusables.actions.about-actions-for-enterprises %} For more information, see "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)." -With {% data variables.product.prodname_actions %}, developers can write and combine individual tasks called actions to create custom workflows. {% ifversion ghes or ghae %}To enable {% data variables.product.prodname_actions %} for {% ifversion ghae %}your enterprise{% elsif ghes %} {% data variables.product.product_location %}{% endif %}, you must host at least one machine to execute jobs.{% endif %} {% ifversion ghec %}You can host your own runner machine to execute jobs, and this{% elsif ghes or ghae %}This{% endif %} machine is called a self-hosted runner. {% data reusables.actions.self-hosted-runner-locations %} {% data reusables.actions.self-hosted-runner-architecture %} {% ifversion ghec %}All{% elsif ghes or ghae %}Self-hosted{% endif %} runners can run Linux, Windows, or macOS. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." +With {% data variables.product.prodname_actions %}, developers can write and combine individual tasks called actions to create custom workflows. {% ifversion ghes or ghae %}To enable {% data variables.product.prodname_actions %} for {% ifversion ghae %}your enterprise{% elsif ghes %} {% data variables.location.product_location %}{% endif %}, you must host at least one machine to execute jobs.{% endif %} {% ifversion ghec %}You can host your own runner machine to execute jobs, and this{% elsif ghes or ghae %}This{% endif %} machine is called a self-hosted runner. {% data reusables.actions.self-hosted-runner-locations %} {% data reusables.actions.self-hosted-runner-architecture %} {% ifversion ghec %}All{% elsif ghes or ghae %}Self-hosted{% endif %} runners can run Linux, Windows, or macOS. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." {% ifversion ghec %} @@ -38,7 +38,7 @@ This guide shows you how to apply a centralized management approach to self-host You'll also find additional information about how to monitor and secure your self-hosted runners,{% ifversion ghes or ghae %} how to access actions from {% data variables.product.prodname_dotcom_the_website %},{% endif %} and how to customize the software on your runner machines. -After you finish the guide, {% ifversion ghec or ghae %}members of your enterprise{% elsif ghes %}users of {% data variables.product.product_location %}{% endif %} will be able to run workflow jobs from {% data variables.product.prodname_actions %} on a self-hosted runner machine. +After you finish the guide, {% ifversion ghec or ghae %}members of your enterprise{% elsif ghes %}users of {% data variables.location.product_location %}{% endif %} will be able to run workflow jobs from {% data variables.product.prodname_actions %} on a self-hosted runner machine. ## Prerequisites @@ -48,7 +48,7 @@ After you finish the guide, {% ifversion ghec or ghae %}members of your enterpri ## 1. Configure policies for {% data variables.product.prodname_actions %} -First, enable {% data variables.product.prodname_actions %} for all organizations, and configure a policy to restrict the actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} that can run {% ifversion ghec or ghae%}within your enterprise on {% data variables.product.product_name %}{% elsif ghes %}on {% data variables.product.product_location %}{% endif %}. Optionally, organization owners can further restrict these policies for each organization. +First, enable {% data variables.product.prodname_actions %} for all organizations, and configure a policy to restrict the actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} that can run {% ifversion ghec or ghae%}within your enterprise on {% data variables.product.product_name %}{% elsif ghes %}on {% data variables.location.product_location %}{% endif %}. Optionally, organization owners can further restrict these policies for each organization. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} @@ -65,11 +65,11 @@ First, enable {% data variables.product.prodname_actions %} for all organization {%- endif %} 1. Click **Save**. -You can configure additional policies to restrict the actions available to {% ifversion ghec or ghae %}enterprise members{% elsif ghes %}users of {% data variables.product.product_location %}{% endif %}. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#allowing-select-actions-to-run)." +You can configure additional policies to restrict the actions available to {% ifversion ghec or ghae %}enterprise members{% elsif ghes %}users of {% data variables.location.product_location %}{% endif %}. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#allowing-select-actions-to-run)." ## 2. Deploy the self-hosted runner for your enterprise -Next, add a self-hosted runner to your enterprise. {% data variables.product.product_name %} will guide you through installation of the necessary software on the runner machine. After you deploy the runner, you can verify connectivity between the runner machine and {%ifversion ghec or ghae %}your enterprise{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. +Next, add a self-hosted runner to your enterprise. {% data variables.product.product_name %} will guide you through installation of the necessary software on the runner machine. After you deploy the runner, you can verify connectivity between the runner machine and {%ifversion ghec or ghae %}your enterprise{% elsif ghes %}{% data variables.location.product_location %}{% endif %}. ### Adding the self-hosted runner @@ -126,7 +126,7 @@ For more information, see "[Managing access to self-hosted runners using groups] ## 5. Automatically scale your self-hosted runners -Optionally, you can build custom tooling to automatically scale the self-hosted runners for {% ifversion ghec or ghae %}your enterprise{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. For example, your tooling can respond to webhook events from {% data variables.product.product_location %} to automatically scale a cluster of runner machines. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)." +Optionally, you can build custom tooling to automatically scale the self-hosted runners for {% ifversion ghec or ghae %}your enterprise{% elsif ghes %}{% data variables.location.product_location %}{% endif %}. For example, your tooling can respond to webhook events from {% data variables.location.product_location %} to automatically scale a cluster of runner machines. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)." {% endif %} diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md index d8de55e3fa..8ac0a99e29 100644 --- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md @@ -91,7 +91,7 @@ You should plan for how you'll manage the resources required to use {% data vari {% ifversion ghes %} ### Hardware requirements -You may need to upgrade the CPU and memory resources for {% data variables.product.product_location %} to handle the load from {% data variables.product.prodname_actions %} without causing performance loss. 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-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-requirements)." +You may need to upgrade the CPU and memory resources for {% data variables.location.product_location %} to handle the load from {% data variables.product.prodname_actions %} without causing performance loss. 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-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-requirements)." {% endif %} ### Runners diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md index cbf2baa4d8..8aa85ea18f 100644 --- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Sobre como usar ações na sua empresa -intro: 'O {% data variables.product.product_name %} inclui a maioria das ações criadas pelo {% data variables.product.prodname_dotcom %} e tem opções para permitir o acesso a outras ações do {% data variables.product.prodname_dotcom_the_website %} e do {% data variables.product.prodname_marketplace %}.' +title: About using actions in your enterprise +intro: '{% data variables.product.product_name %} includes most {% data variables.product.prodname_dotcom %}-authored actions, and has options for enabling access to other actions from {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_marketplace %}.' redirect_from: - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server - /admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server @@ -14,63 +14,61 @@ topics: - Actions - Enterprise shortTitle: About actions in your enterprise -ms.openlocfilehash: 2e18b932548aa7ad9b65c090b6a5418762bcb501 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146139005' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## Sobre ações em {% data variables.product.product_name %} +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} -Os fluxos de trabalho do {% data variables.product.prodname_actions %} podem usar _ações_, que são tarefas individuais que podem ser combinadas para criar trabalhos e personalizar seu fluxo de trabalho. Você pode criar suas próprias ações ou usar e personalizar ações compartilhadas pela comunidade {% data variables.product.prodname_dotcom %}. +## About actions on {% data variables.product.product_name %} -{% data reusables.actions.enterprise-no-internet-actions %} Você pode restringir seus desenvolvedores a usar ações que são armazenadas em {% data variables.product.product_location %}, o que inclui a maioria das ações oficiais de criadas por {% data variables.product.company_short %}, bem como quaisquer ações que seus desenvolvedores criarem. Como alternativa, para permitir que seus desenvolvedores se beneficiem de todo o ecossistema de ações criadas pelos líderes do setor e pela comunidade de código aberto você pode configurar o acesso a outras ações a partir de {% data variables.product.prodname_dotcom_the_website %}. +{% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the {% data variables.product.prodname_dotcom %} community. -Recomendamos permitir acesso automático a todas as ações de {% data variables.product.prodname_dotcom_the_website %}. {% ifversion ghes %}No entanto, isso exige que {% data variables.product.product_name %} faça conexões de saída para {% data variables.product.prodname_dotcom_the_website %}. Se você não quiser permitir essas conexões ou{% else %}Se{% endif %} se você quiser ter maior controle sobre quais ações são usadas em sua empresa, você pode sincronizar manualmente ações específicas de {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.actions.enterprise-no-internet-actions %} You can restrict your developers to using actions that are stored on {% data variables.location.product_location %}, which includes most official {% data variables.product.company_short %}-authored actions, as well as any actions your developers create. Alternatively, to allow your developers to benefit from the full ecosystem of actions built by industry leaders and the open source community, you can configure access to other actions from {% data variables.product.prodname_dotcom_the_website %}. -## Ações oficiais agrupadas com a sua instância corporativa +We recommend allowing automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %}. {% ifversion ghes %}However, this does require {% data variables.product.product_name %} to make outbound connections to {% data variables.product.prodname_dotcom_the_website %}. If you don't want to allow these connections, or{% else %}If{% endif %} you want to have greater control over which actions are used on your enterprise, you can manually sync specific actions from {% data variables.product.prodname_dotcom_the_website %}. + +## Official actions bundled with your enterprise instance {% data reusables.actions.actions-bundled-with-ghes %} -As acções oficiais agrupadas incluem, entre outras, as listadas a seguir. +The bundled official actions include the following, among others. - `actions/checkout` - `actions/upload-artifact` - `actions/download-artifact` - `actions/labeler` -- Várias ações `actions/setup-` +- Various `actions/setup-` actions -Para ver todas as ações oficiais incluídas na sua instância corporativa, navegue até a organização `actions` na sua instância: https://HOSTNAME/actions. +To see all the official actions included on your enterprise instance, browse to the `actions` organization on your instance: https://HOSTNAME/actions. -Não há conexão necessária entre {% data variables.product.product_location %} e {% data variables.product.prodname_dotcom_the_website %} para usar essas ações. +There is no connection required between {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %} to use these actions. -Cada ação é um repositório na organização `actions`, e cada repositório de ações inclui as tags, os branches e os SHAs de commit necessários que seus fluxos de trabalho podem usar para referenciar a ação. Para obter informações sobre como atualizar as ações oficiais empacotadas, confira "[Como usar a última versão das ações empacotadas oficiais](/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions)". +Each action is a repository in the `actions` organization, and each action repository includes the necessary tags, branches, and commit SHAs that your workflows can use to reference the action. For information on how to update the bundled official actions, see "[Using the latest version of the official bundled actions](/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions)." {% note %} -**Observações:** -- Quando as ações de instalação (como `actions/setup-LANGUAGE`) são usadas no {% data variables.product.product_name %} com executores auto-hospedados, talvez seja necessário configurar o cache de ferramentas nos executores que não têm acesso à Internet. Para obter mais informações, confira "[Como configurar o cache de ferramentas em executores auto-hospedados sem acesso à Internet](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)". -- Quando o {% data variables.product.product_name %} é atualizado, as ações em pacote são substituídas automaticamente por versões padrão no pacote de atualização. +**Notes:** +- When using setup actions (such as `actions/setup-LANGUAGE`) on {% data variables.product.product_name %} with self-hosted runners, you might need to set up the tools cache on runners that do not have internet access. For more information, see "[Setting up the tool cache on self-hosted runners without internet access](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)." +- When {% data variables.product.product_name %} is updated, bundled actions are automatically replaced with default versions in the upgrade package. {% endnote %} -## Configurar o acesso a ações no {% data variables.product.prodname_dotcom_the_website %} +## Configuring access to actions on {% data variables.product.prodname_dotcom_the_website %} {% data reusables.actions.access-actions-on-dotcom %} -A abordagem recomendada é habilitar o acesso automático para todas as ações a partir de {% data variables.product.prodname_dotcom_the_website %}. Faça isso usando o {% data variables.product.prodname_github_connect %} para integrar o {% data variables.product.product_name %} ao {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, confira "[Como habilitar o acesso automático às ações do {% data variables.product.prodname_dotcom_the_website %} usando o {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". +The recommended approach is to enable automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %}. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". -{% ifversion ghes %} {% note %} +{% ifversion ghes %} +{% note %} -**Observação:** para configurar o acesso às ações do {% data variables.product.prodname_dotcom_the_website %}, você precisa configurar o {% data variables.product.product_location %} para usar o {% data variables.product.prodname_actions %}. Para obter mais informações, confira "[Introdução ao {% data variables.product.prodname_actions %} para GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)". +**Note:** Before you can configure access to actions on {% data variables.product.prodname_dotcom_the_website %}, you must configure {% data variables.location.product_location %} to use {% data variables.product.prodname_actions %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)." -{% endnote %} {% endif %} +{% endnote %} +{% endif %} {% data reusables.actions.self-hosted-runner-networking-to-dotcom %} {% data reusables.actions.enterprise-limit-actions-use %} -Como alternativa, se você quiser ter um controle mais rigoroso sobre as ações que são permitidas na sua empresa ou não quiser permitir conexões de saída com o {% data variables.product.prodname_dotcom_the_website %}, baixe e sincronize as ações manualmente na sua instância corporativa usando a ferramenta `actions-sync`. Para obter mais informações, confira "[Como sincronizar as ações manualmente no {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)". +Alternatively, if you want stricter control over which actions are allowed in your enterprise, or you do not want to allow outbound connections to {% data variables.product.prodname_dotcom_the_website %}, you can manually download and sync actions onto your enterprise instance using the `actions-sync` tool. For more information, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)." diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index 69033078df..709907e154 100644 --- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -1,6 +1,6 @@ --- -title: Habilitar o acesso automático a GitHub.com usando o GitHub Connect -intro: 'Para permitir que {% data variables.product.prodname_actions %} na sua empresa use ações a partir de {% data variables.product.prodname_dotcom_the_website %}, você pode conectar a sua instância corporativa a {% data variables.product.prodname_ghe_cloud %}.' +title: Enabling automatic access to GitHub.com actions using GitHub Connect +intro: 'To allow {% data variables.product.prodname_actions %} in your enterprise to use actions from {% data variables.product.prodname_dotcom_the_website %}, you can connect your enterprise instance to {% data variables.product.prodname_ghe_cloud %}.' permissions: 'Enterprise owners can enable access to all {% data variables.product.prodname_dotcom_the_website %} actions.' redirect_from: - /enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect @@ -14,60 +14,57 @@ topics: - Enterprise - GitHub Connect shortTitle: Use GitHub Connect for actions -ms.openlocfilehash: 85942d047f8bce5c2f58e8f92148b5fb85f5d871 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145095896' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## Sobre o acesso automático a ações de {% data variables.product.prodname_dotcom_the_website %} +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} -Por padrão, os fluxos de trabalho de {% data variables.product.prodname_actions %} no {% data variables.product.product_name %} não podem usar ações diretamente do {% data variables.product.prodname_dotcom_the_website %} ou [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). Para tornar todas as ações de {% data variables.product.prodname_dotcom_the_website %} disponíveis na sua instância corporativa, você pode usar {% data variables.product.prodname_github_connect %} para integrar o {% data variables.product.product_name %} ao {% data variables.product.prodname_ghe_cloud %}. +## About automatic access to {% data variables.product.prodname_dotcom_the_website %} actions + +By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.product_name %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can use {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. {% data reusables.actions.self-hosted-runner-networking-to-dotcom %} -Como alternativa, se você quiser ter um controle mais rigoroso sobre as ações que são permitidas na sua empresa, faça o download e sincronize manualmente as ações na instância da sua empresa usando a ferramenta `actions-sync`. Para obter mais informações, confira "[Como sincronizar as ações manualmente no {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)". +Alternatively, if you want stricter control over which actions are allowed in your enterprise, you can manually download and sync actions onto your enterprise instance using the `actions-sync` tool. For more information, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)." -## Sobre resolução para ações usando {% data variables.product.prodname_github_connect %} +## About resolution for actions using {% data variables.product.prodname_github_connect %} {% data reusables.actions.github-connect-resolution %} -Se um usuário tiver criado uma organização e um repositório em sua empresa, que corresponde a uma organização e nome do repositório em {% data variables.product.prodname_dotcom_the_website %}, o repositório da sua empresa será usado em vez do repositório de {% data variables.product.prodname_dotcom_the_website %}. {% ifversion ghes < 3.3 or ghae %}Um usuário mal intencionado poderia aproveitar esse comportamento para executar um código como parte de um fluxo de trabalho{% else %}Para obter mais informações, confira "[Desativação automática de namespaces para ações acessadas no {% data variables.product.prodname_dotcom_the_website%}](#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)". +If a user has already created an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom_the_website %}, the repository on your enterprise will be used instead of the {% data variables.product.prodname_dotcom_the_website %} repository. {% ifversion ghes < 3.3 or ghae %}A malicious user could take advantage of this behavior to run code as part of a workflow{% else %}For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." {% endif %} -## Habilitar o acesso automático a todas as ações de {% data variables.product.prodname_dotcom_the_website %} +## Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions -Antes de permitir o acesso a todas as ações de {% data variables.product.prodname_dotcom_the_website %} para sua empresa, você deve {% ifversion ghes %}: -- Configure {% data variables.product.product_location %} para usar {% data variables.product.prodname_actions %}. Para obter mais informações, confira "[Introdução ao {% data variables.product.prodname_actions %} para GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)". -- Habilitar {% else %} habilitar{% endif %} {% data variables.product.prodname_github_connect %}. Para obter mais informações, confira "[Como gerenciar o {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)". +Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} for your enterprise, you must{% ifversion ghes %}: +- Configure {% data variables.location.product_location %} to use {% data variables.product.prodname_actions %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)." +- Enable{% else %} enable{% endif %} {% data variables.product.prodname_github_connect %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)." -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %} -1. Em "Usuários podem utilizar ações do GitHub.com em execuções de fluxo de trabalho", use o menu suspenso e selecione **Habilitado**. - ![Menu suspenso para ações do GitHub.com em execuções do fluxos de trabalho](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png) +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.github-connect-tab %} +1. Under "Users can utilize actions from GitHub.com in workflow runs", use the drop-down menu and select **Enabled**. + ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png) 1. {% data reusables.actions.enterprise-limit-actions-use %} {% ifversion ghes > 3.2 or ghae %} -## Retirada automática de namespaces para ações acessadas em {% data variables.product.prodname_dotcom_the_website %} +## Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %} -Ao habilitar {% data variables.product.prodname_github_connect %}, os usuários não verão nenhuma alteração no comportamento para fluxos de trabalho existentes porque {% data variables.product.prodname_actions %} procura {% data variables.product.product_location %} para cada ação antes de voltar a {% data variables.product.prodname_dotcom_the_website%}. Isso garante que todas as versões personalizadas de ações que a sua empresa criou sejam usadas em preferência para suas contrapartes em {% data variables.product.prodname_dotcom_the_website%}. +When you enable {% data variables.product.prodname_github_connect %}, users see no change in behavior for existing workflows because {% data variables.product.prodname_actions %} searches {% data variables.location.product_location %} for each action before falling back to {% data variables.product.prodname_dotcom_the_website%}. This ensures that any custom versions of actions your enterprise has created are used in preference to their counterparts on {% data variables.product.prodname_dotcom_the_website%}. -A desativação automática de namespaces para ações acessadas em {% data variables.product.prodname_dotcom_the_website %} bloqueia o potencial de um ataque de um intermediário por um usuário malicioso com acesso a {% data variables.product.product_location %}. Quando uma ação em {% data variables.product.prodname_dotcom_the_website %} é usada pela primeira vez, esse namespace fica desativado em {% data variables.product.product_location %}. Isso bloqueia qualquer usuário que criar uma organização e repositório na sua empresa que corresponda a essa organização e nome do repositório em {% data variables.product.prodname_dotcom_the_website %}. Isso garante que, quando um fluxo de trabalho é executado, a ação pretendida é sempre executada. +Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %} blocks the potential for a man-in-the-middle attack by a malicious user with access to {% data variables.location.product_location %}. When an action on {% data variables.product.prodname_dotcom_the_website %} is used for the first time, that namespace is retired in {% data variables.location.product_location %}. This blocks any user creating an organization and repository in your enterprise that matches that organization and repository name on {% data variables.product.prodname_dotcom_the_website %}. This ensures that when a workflow runs, the intended action is always run. -Depois de usar uma ação de {% data variables.product.prodname_dotcom_the_website %}, se você deseja criar uma ação em {% data variables.product.product_location %} com o mesmo nome, primeiro você precisa tornar o namespace para a organização e repositório disponíveis. +After using an action from {% data variables.product.prodname_dotcom_the_website %}, if you want to create an action in {% data variables.location.product_location %} with the same name, first you need to make the namespace for that organization and repository available. {% data reusables.enterprise_site_admin_settings.access-settings %} -2. Na barra lateral à esquerda, em **Administrador do site**, clique em **Namespaces desativados**. -3. Localize o namespace que você quer usar no {% data variables.product.product_location %} e clique em **Cancelar desativação**. - ![Cancelar desativação do namespace](/assets/images/enterprise/site-admin-settings/unretire-namespace.png) -4. Acesse a organização relevante e crie um novo repositório. +2. In the left sidebar, under **Site admin** click **Retired namespaces**. +3. Locate the namespace that you want use in {% data variables.location.product_location %} and click **Unretire**. + ![Unretire namespace](/assets/images/enterprise/site-admin-settings/unretire-namespace.png) +4. Go to the relevant organization and create a new repository. {% tip %} - **Dica:** quando você cancelar a desativação de um namespace, sempre crie o novo repositório com esse nome o mais rápido possível. Se um fluxo de trabalho chamar a ação associada em {% data variables.product.prodname_dotcom_the_website %} antes de criar o repositório local, o namespace será desativado novamente. Para ações usadas em fluxos de trabalho frequentemente, você pode considerar que um namespace foi desativado novamente antes de ter tempo para criar o repositório local. Neste caso, você pode desabilitar temporariamente os fluxos de trabalho relevantes até criar o novo repositório. + **Tip:** When you unretire a namespace, always create the new repository with that name as soon as possible. If a workflow calls the associated action on {% data variables.product.prodname_dotcom_the_website %} before you create the local repository, the namespace will be retired again. For actions used in workflows that run frequently, you may find that a namespace is retired again before you have time to create the local repository. In this case, you can temporarily disable the relevant workflows until you have created the new repository. {% endtip %} diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md index 446b302b29..e44a1c5cf1 100644 --- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md +++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md @@ -1,6 +1,6 @@ --- -title: Sincronizar ações do GitHub.com manualmente -intro: 'Para usuários que precisam acessar as ações a partir de {% data variables.product.prodname_dotcom_the_website %}, você pode sincronizar ações específicas para sua empresa.' +title: Manually syncing actions from GitHub.com +intro: 'For users that need access to actions from {% data variables.product.prodname_dotcom_the_website %}, you can sync specific actions to your enterprise.' redirect_from: - /enterprise/admin/github-actions/manually-syncing-actions-from-githubcom - /admin/github-actions/manually-syncing-actions-from-githubcom @@ -12,53 +12,51 @@ topics: - Actions - Enterprise shortTitle: Manually sync actions -ms.openlocfilehash: f4116663e510da9b7551e4a9050dd4ba838ed7c6 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145095894' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.enterprise-no-internet-actions %} {% ifversion ghes or ghae %} -A abordagem recomendada de habilitar o acesso a ações a partir de {% data variables.product.prodname_dotcom_the_website %} é permitir o acesso automático para todas as ações. Faça isso usando o {% data variables.product.prodname_github_connect %} para integrar o {% data variables.product.product_name %} ao {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, confira "[Como habilitar o acesso automático às ações do {% data variables.product.prodname_dotcom_the_website %} usando o {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". +The recommended approach of enabling access to actions from {% data variables.product.prodname_dotcom_the_website %} is to enable automatic access to all actions. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." -No entanto, se você quiser um controle mais rigoroso sobre quais as ações são permitidas na sua empresa, você{% else %}Você{% endif %} poderá seguir este guia para usar a ferramenta de código aberto [`actions-sync`](https://github.com/actions/actions-sync) do {% data variables.product.company_short %} para sincronizar repositórios de ações individuais do {% data variables.product.prodname_dotcom_the_website %} para a sua empresa. +However, if you want stricter control over which actions are allowed in your enterprise, you{% else %}You{% endif %} can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise. -## Sobre a ferramenta `actions-sync` +## About the `actions-sync` tool -A ferramenta `actions-sync` deve ser executada em um computador que possa acessar a API do {% data variables.product.prodname_dotcom_the_website %} e a API da instância do {% data variables.product.product_name %}. A máquina não precisa estar conectada a ambos ao mesmo tempo. +The `actions-sync` tool must be run on a machine that can access the {% data variables.product.prodname_dotcom_the_website %} API and your {% data variables.product.product_name %} instance's API. The machine doesn't need to be connected to both at the same time. -Se o computador tiver acesso a ambos os sistemas ao mesmo tempo, você poderá fazer a sincronização com um único comando `actions-sync sync`. Se você só puder acessar um sistema por vez, use os comandos `actions-sync pull` e `push`. +If your machine has access to both systems at the same time, you can do the sync with a single `actions-sync sync` command. If you can only access one system at a time, you can use the `actions-sync pull` and `push` commands. -A ferramenta `actions-sync` só pode baixar ações de {% data variables.product.prodname_dotcom_the_website %} armazenados em repositórios públicos. +The `actions-sync` tool can only download actions from {% data variables.product.prodname_dotcom_the_website %} that are stored in public repositories. -{% ifversion ghes > 3.2 or ghae %} {% note %} +{% ifversion ghes > 3.2 or ghae %} +{% note %} -**Nota:** a ferramenta `actions-sync` destina-se ao uso em sistemas em que o {% data variables.product.prodname_github_connect %} não está habilitado. Se você executar a ferramenta em um sistema com {% data variables.product.prodname_github_connect %} habilitado, poderá ver o erro `The repository has been retired and cannot be reused`. Isso indica que um fluxo de trabalho usou essa ação diretamente em {% data variables.product.prodname_dotcom_the_website %} e o namespace está desativado em {% data variables.product.product_location %}. Para obter mais informações, confira "[Desativação automática de namespaces para as ações acessadas no {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)". +**Note:** The `actions-sync` tool is intended for use in systems where {% data variables.product.prodname_github_connect %} is not enabled. If you run the tool on a system with {% data variables.product.prodname_github_connect %} enabled, you may see the error `The repository has been retired and cannot be reused`. This indicates that a workflow has used that action directly on {% data variables.product.prodname_dotcom_the_website %} and the namespace is retired on {% data variables.location.product_location %}. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." -{% endnote %} {% endif %} +{% endnote %} +{% endif %} -## Pré-requisitos +## Prerequisites -* Antes de usar a ferramenta `actions-sync`, você deve garantir que todas as organizações de destino já existam em sua empresa. O exemplo a seguir demonstra como sincronizar ações com uma organização chamada `synced-actions`. Para obter mais informações, confira "[Como criar uma organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". -* Você deve criar um token de acesso pessoal (PAT) na sua empresa que pode criar e gravar em repositórios nas organizações de destino. Para obter mais informações, confira "[Como criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)".{% ifversion ghes %} -* Se você quiser sincronizar as ações empacotadas na organização `actions` no {% data variables.product.product_location %}, deverá ser um proprietário da organização `actions`. +* Before using the `actions-sync` tool, you must ensure that all destination organizations already exist in your enterprise. The following example demonstrates how to sync actions to an organization named `synced-actions`. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." +* You must create a {% data variables.product.pat_generic %} on your enterprise that can create and write to repositories in the destination organizations. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."{% ifversion ghes %} +* If you want to sync the bundled actions in the `actions` organization on {% data variables.location.product_location %}, you must be an owner of the `actions` organization. {% note %} - **Observação**: Por padrão, os administradores do site não são proprietários da organização `actions`empacotada. + **Note:** By default, even site administrators are not owners of the bundled `actions` organization. {% endnote %} - Os administradores do site podem usar o comando `ghe-org-admin-promote` no shell administrativo para promover um usuário para ser um proprietário da organização empacotada `actions`. Para obter mais informações, confira "[Como acessar o shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" e "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)". + Site administrators can use the `ghe-org-admin-promote` command in the administrative shell to promote a user to be an owner of the bundled `actions` organization. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)." ```shell - ghe-org-admin-promote -u USERNAME -o actions + ghe-org-admin-promote -u USERNAME -o actions ```{% endif %} ## Example: Using the `actions-sync` tool @@ -83,20 +81,20 @@ This example demonstrates using the `actions-sync` tool to sync an individual ac --repo-name "actions/stale:synced-actions/actions-stale" ``` - O comando acima usa os seguintes argumentos: + The above command uses the following arguments: - * `--cache-dir`: o diretório de cache no computador que executa o comando. - * `--destination-token`: um token de acesso pessoal para a instância corporativa de destino. - * `--destination-url`: a URL da instância corporativa de destino. - * `--repo-name`: o repositório de ação a ser sincronizado. Ele usa o formato de `owner/repository:destination_owner/destination_repository`. + * `--cache-dir`: The cache directory on the machine running the command. + * `--destination-token`: A {% data variables.product.pat_generic %} for the destination enterprise instance. + * `--destination-url`: The URL of the destination enterprise instance. + * `--repo-name`: The action repository to sync. This takes the format of `owner/repository:destination_owner/destination_repository`. - * O exemplo acima sincroniza o repositório [`actions/stale`](https://github.com/actions/stale) com o repositório `synced-actions/actions-stale` na instância da empresa de destino. Você deve criar a organização nomeada `synced-actions` em sua empresa antes de executar o comando acima. - * Se você omitir `:destination_owner/destination_repository`, a ferramenta usará o nome original do proprietário e do repositório da sua empresa. Antes de executar o comando, você deve criar uma nova organização em sua empresa que corresponda ao nome da ação do proprietário. Considere usar uma organização central para armazenar as ações sincronizadas na sua empresa, uma vez que isso significa que você não precisará criar várias novas organizações se sincronizar ações de diferentes proprietários. - * Você pode sincronizar várias ações substituindo o parâmetro `--repo-name` por `--repo-name-list` ou `--repo-name-list-file`. Para obter mais informações, veja o [README `actions-sync`](https://github.com/actions/actions-sync#actions-sync). -1. Depois que o repositório de ação for criado na sua empresa, as pessoas da sua empresa poderão usar o repositório de destino para fazer referência à ação nos fluxos de trabalho. Para o exemplo da ação mostrado acima: + * The above example syncs the [`actions/stale`](https://github.com/actions/stale) repository to the `synced-actions/actions-stale` repository on the destination enterprise instance. You must create the organization named `synced-actions` in your enterprise before running the above command. + * If you omit `:destination_owner/destination_repository`, the tool uses the original owner and repository name for your enterprise. Before running the command, you must create a new organization in your enterprise that matches the owner name of the action. Consider using a central organization to store the synced actions in your enterprise, as this means you will not need to create multiple new organizations if you sync actions from different owners. + * You can sync multiple actions by replacing the `--repo-name` parameter with `--repo-name-list` or `--repo-name-list-file`. For more information, see the [`actions-sync` README](https://github.com/actions/actions-sync#actions-sync). +1. After the action repository is created in your enterprise, people in your enterprise can use the destination repository to reference the action in their workflows. For the example action shown above: ```yaml uses: synced-actions/actions-stale@v1 ``` - Para obter mais informações, confira "[Sintaxe de fluxo de trabalho do GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsuses)". + For more information, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsuses)." diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md index 34fcddb3d9..c75e4e6eef 100644 --- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md +++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md @@ -1,6 +1,6 @@ --- -title: Usar a versão mais recente das ações agrupadas oficialmente -intro: 'Você pode atualizar as ações que estão empacotadas com a sua empresa ou usar ações diretamente a partir de {% data variables.product.prodname_dotcom_the_website %}.' +title: Using the latest version of the official bundled actions +intro: 'You can update the actions that are bundled with your enterprise, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.' versions: ghes: '*' ghae: '*' @@ -12,48 +12,45 @@ topics: redirect_from: - /admin/github-actions/using-the-latest-version-of-the-official-bundled-actions shortTitle: Use the latest bundled actions -ms.openlocfilehash: 3243199ad7f5d216a351ddc2db7a4e6afed66c9b -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145095893' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} -A instância da sua empresa inclui uma série de ações integradas que podem ser usadas nos seus fluxos de trabalho. Para obter mais informações sobre as ações empacotadas, confira "[Ações oficiais empacotadas com sua instância corporativa](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)". +Your enterprise instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see "[Official actions bundled with your enterprise instance](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)." -Essas ações empacotadas são um instantâneo pontual das ações oficiais encontradas em https://github.com/actions. Portanto, pode haver versões mais recentes dessas ações disponíveis. Use a ferramenta `actions-sync` para atualizar essas ações ou configure o {% data variables.product.prodname_github_connect %} para permitir o acesso às ações mais recentes no {% data variables.product.prodname_dotcom_the_website %}. Essas opções são descritas nas seções a seguir. +These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions, so there may be newer versions of these actions available. You can use the `actions-sync` tool to update these actions, or you can configure {% data variables.product.prodname_github_connect %} to allow access to the latest actions on {% data variables.product.prodname_dotcom_the_website %}. These options are described in the following sections. -## Como usar `actions-sync` para atualizar as ações empacotadas +## Using `actions-sync` to update the bundled actions -Para atualizar as ações empacotadas, use a ferramenta `actions-sync` para atualizar o instantâneo. Para obter mais informações sobre como usar `actions-sync`, confira "[Como sincronizar ações do {% data variables.product.prodname_dotcom_the_website %} manualmente](/admin/github-actions/manually-syncing-actions-from-githubcom)". +To update the bundled actions, you can use the `actions-sync` tool to update the snapshot. For more information on using `actions-sync`, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)." -## Usar {% data variables.product.prodname_github_connect %} para acessar as últimas ações +## Using {% data variables.product.prodname_github_connect %} to access the latest actions -Você pode usar {% data variables.product.prodname_github_connect %} para permitir que {% data variables.product.product_name %} use ações a partir do {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, confira "[Como habilitar o acesso automático às ações do {% data variables.product.prodname_dotcom_the_website %} usando o {% data variables.product.prodname_github_connect %}](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". +You can use {% data variables.product.prodname_github_connect %} to allow {% data variables.product.product_name %} to use actions from {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." -Depois que o {% data variables.product.prodname_github_connect %} estiver configurado, você poderá usar a última versão de uma ação excluindo o repositório local na organização `actions` na sua instância. Por exemplo, se a sua instância corporativa estiver usando a `v1` da ação `actions/checkout` e você precisar usar `{% data reusables.actions.action-checkout %}`, o que não está disponível na instância corporativa, execute as seguintes etapas para usar a última ação `checkout` do {% data variables.product.prodname_dotcom_the_website %}: +Once {% data variables.product.prodname_github_connect %} is configured, you can use the latest version of an action by deleting its local repository in the `actions` organization on your instance. For example, if your enterprise instance is using `v1` of the `actions/checkout` action, and you need to use `{% data reusables.actions.action-checkout %}` which isn't available on your enterprise instance, perform the following steps to be able to use the latest `checkout` action from {% data variables.product.prodname_dotcom_the_website %}: -1. Em uma conta de proprietário da empresa no {% data variables.product.product_name %}, procure o repositório que deseja excluir da organização *actions* (neste exemplo, `checkout`). -1. Por padrão, os administradores do site não são proprietários da organização *actions* empacotada. Para obter o acesso necessário para excluir o repositório `checkout`, você precisa usar as ferramentas de administração do site. Clique em {% octicon "rocket" aria-label="The rocket ship" %} no canto superior direito de qualquer página do repositório. - ![Ícone de foguete para acessar as configurações de administração do site](/assets/images/enterprise/site-admin-settings/access-new-settings.png) -1. Clique em {% octicon "shield-lock" %} **Segurança** para ter a visão geral de segurança do repositório. - ![Cabeçalho de segurança do repositório](/assets/images/enterprise/site-admin-settings/access-repo-security-info.png) -1. Em "Acesso privilegiado", clique em **Desbloquear**. - ![Botão Desbloquear](/assets/images/enterprise/site-admin-settings/unlock-priviledged-repo-access.png) -1. Em **Motivo**, digite um motivo para desbloquear o repositório e clique em **Desbloquear**. - ![Diálogo de confirmação](/assets/images/enterprise/site-admin-settings/confirm-unlock-repo-access.png) -1. Agora que o repositório está desbloqueado, você pode sair das páginas de administração do site e excluir o repositório dentro da organização `actions`. Na parte superior da página, clique no nome do repositório, neste exemplo, **checkout**, para voltar à página de resumo. - ![Link para o nome do repositório](/assets/images/enterprise/site-admin-settings/display-repository-admin-summary.png) -1. Em "Informações do repositório", clique em **Exibir código** para sair das páginas de administração do site e ver o repositório `checkout`. -1. Exclua o repositório `checkout` dentro da organização `actions`. Para obter informações sobre como excluir um repositório, confira "[Como excluir um repositório](/github/administering-a-repository/deleting-a-repository)". - ![Ver link de código](/assets/images/enterprise/site-admin-settings/exit-admin-page-for-repository.png) -1. Configure o YAML do fluxo de trabalho para usar `{% data reusables.actions.action-checkout %}`. -1. Sempre que o fluxo de trabalho for executado, o executor usará a versão especificada de `actions/checkout` do {% data variables.product.prodname_dotcom_the_website %}. +1. From an enterprise owner account on {% data variables.product.product_name %}, navigate to the repository you want to delete from the *actions* organization (in this example `checkout`). +1. By default, site administrators are not owners of the bundled *actions* organization. To get the access required to delete the `checkout` repository, you must use the site admin tools. Click {% octicon "rocket" aria-label="The rocket ship" %} in the upper-right corner of any page in that repository. + ![Rocketship icon for accessing site admin settings](/assets/images/enterprise/site-admin-settings/access-new-settings.png) +1. Click {% octicon "shield-lock" %} **Security** to see the security overview for the repository. + ![Security header the repository](/assets/images/enterprise/site-admin-settings/access-repo-security-info.png) +1. Under "Privileged access", click **Unlock**. + ![Unlock button](/assets/images/enterprise/site-admin-settings/unlock-priviledged-repo-access.png) +1. Under **Reason**, type a reason for unlocking the repository, then click **Unlock**. + ![Confirmation dialog](/assets/images/enterprise/site-admin-settings/confirm-unlock-repo-access.png) +1. Now that the repository is unlocked, you can leave the site admin pages and delete the repository within the `actions` organization. At the top of the page, click the repository name, in this example **checkout**, to return to the summary page. + ![Repository name link](/assets/images/enterprise/site-admin-settings/display-repository-admin-summary.png) +1. Under "Repository info", click **View code** to leave the site admin pages and display the `checkout` repository. +1. Delete the `checkout` repository within the `actions` organization. For information on how to delete a repository, see "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)." + ![View code link](/assets/images/enterprise/site-admin-settings/exit-admin-page-for-repository.png) +1. Configure your workflow's YAML to use `{% data reusables.actions.action-checkout %}`. +1. Each time your workflow runs, the runner will use the specified version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}. - {% ifversion ghes > 3.2 or ghae %} {% note %} + {% ifversion ghes > 3.2 or ghae %} + {% note %} - **Observação:** na primeira vez que a ação `checkout` é usada no {% data variables.product.prodname_dotcom_the_website %}, o namespace `actions/checkout` é desativado automaticamente no {% data variables.product.product_location %}. Se você quiser reverter para uma cópia local da ação, primeiro você precisará remover o namespace da desativação. Para obter mais informações, confira "[Desativação automática de namespaces para as ações acessadas no {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)". + **Note:** The first time the `checkout` action is used from {% data variables.product.prodname_dotcom_the_website %}, the `actions/checkout` namespace is automatically retired on {% data variables.location.product_location %}. If you ever want to revert to using a local copy of the action, you first need to remove the namespace from retirement. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." - {% endnote %} {% endif %} + {% endnote %} + {% endif %} diff --git a/translations/pt-BR/content/admin/identity-and-access-management/index.md b/translations/pt-BR/content/admin/identity-and-access-management/index.md index a665dc92fb..477ee3ba03 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/index.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/index.md @@ -1,6 +1,6 @@ --- -title: Gerenciamento de identidade e de acesso -intro: 'Você pode configurar como as pessoas acessam {% ifversion ghec or ghae %}sua empresa no {% data variables.product.product_name %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.' +title: Identity and access management +intro: 'You can configure how people access {% ifversion ghec or ghae %}your enterprise on {% data variables.product.product_name %}{% elsif ghes %}{% data variables.location.product_location %}{% endif %}.' redirect_from: - /enterprise/admin/authentication - /admin/authentication @@ -21,11 +21,5 @@ children: - /using-saml-for-enterprise-iam - /using-enterprise-managed-users-for-iam - /managing-recovery-codes-for-your-enterprise -ms.openlocfilehash: 8c7a364ba6310617452626901c5859ef54cd2b47 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147882808' --- diff --git a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md index 0ad52e007b..3466c75d14 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md @@ -1,7 +1,7 @@ --- title: About authentication for your enterprise shortTitle: About authentication -intro: 'You {% ifversion ghae %}must configure SAML single sign-on (SSO) so people can{% else %}can choose how people{% endif %} authenticate to access {% ifversion ghec %}your enterprise''s resources on {% data variables.product.product_name %}{% elsif ghes %}{% data variables.product.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %}.' +intro: 'You {% ifversion ghae %}must configure SAML single sign-on (SSO) so people can{% else %}can choose how people{% endif %} authenticate to access {% ifversion ghec %}your enterprise''s resources on {% data variables.product.product_name %}{% elsif ghes %}{% data variables.location.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %}.' versions: ghec: '*' ghes: '*' @@ -29,23 +29,23 @@ After learning more about these options, to determine which method is best for y The following options are available for account management and authentication on {% data variables.product.product_name %}. -- [Authentication through {% data variables.product.product_location %}](#authentication-through-githubcom) -- [Authentication through {% data variables.product.product_location %} with additional SAML access restriction](#authentication-through-githubcom-with-additional-saml-access-restriction) +- [Authentication through {% data variables.location.product_location %}](#authentication-through-githubcom) +- [Authentication through {% data variables.location.product_location %} with additional SAML access restriction](#authentication-through-githubcom-with-additional-saml-access-restriction) - [Authentication with {% data variables.product.prodname_emus %} and federation](#authentication-with-enterprise-managed-users-and-federation) -### Authentication through {% data variables.product.product_location %} +### Authentication through {% data variables.location.product_location %} -By default, each member must create a personal account on {% data variables.product.product_location %}. You grant access to your enterprise, and the member can access your enterprise's resources after signing into the account on {% data variables.product.product_location %}. The member manages the account, and can contribute to other enterprises, organizations, and repositories on {% data variables.product.product_location %}. +By default, each member must create a personal account on {% data variables.location.product_location %}. You grant access to your enterprise, and the member can access your enterprise's resources after signing into the account on {% data variables.location.product_location %}. The member manages the account, and can contribute to other enterprises, organizations, and repositories on {% data variables.location.product_location %}. -### Authentication through {% data variables.product.product_location %} with additional SAML access restriction +### Authentication through {% data variables.location.product_location %} with additional SAML access restriction -If you configure additional SAML access restriction, each member must create and manage a personal account on {% data variables.product.product_location %}. You grant access to your enterprise, and the member can access your enterprise's resources after both signing into the account on {% data variables.product.product_location %} and successfully authenticating with your SAML identity provider (IdP). The member can contribute to other enterprises, organizations, and repositories on {% data variables.product.product_location %} using their personal account. For more information about requiring SAML authentication for all access your enterprise's resources, see "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)." +If you configure additional SAML access restriction, each member must create and manage a personal account on {% data variables.location.product_location %}. You grant access to your enterprise, and the member can access your enterprise's resources after both signing into the account on {% data variables.location.product_location %} and successfully authenticating with your SAML identity provider (IdP). The member can contribute to other enterprises, organizations, and repositories on {% data variables.location.product_location %} using their personal account. For more information about requiring SAML authentication for all access your enterprise's resources, see "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)." If you use a standalone organization with {% data variables.product.product_name %}, or if you don't want to use SAML authentication for every organization in your enterprise, you can configure SAML for an individual organization. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." ### Authentication with {% data variables.product.prodname_emus %} and federation -If you need more control of the accounts for your enterprise members on {% data variables.product.product_location %}, you can use {% data variables.product.prodname_emus %}. With {% data variables.product.prodname_emus %}, you provision and manage accounts for your enterprise members on {% data variables.product.product_location %} using your IdP. Each member signs into an account that you create, and your enterprise manages the account. Contributions to the rest of {% data variables.product.prodname_dotcom_the_website %} are restricted. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)." +If you need more control of the accounts for your enterprise members on {% data variables.location.product_location %}, you can use {% data variables.product.prodname_emus %}. With {% data variables.product.prodname_emus %}, you provision and manage accounts for your enterprise members on {% data variables.location.product_location %} using your IdP. Each member signs into an account that you create, and your enterprise manages the account. Contributions to the rest of {% data variables.product.prodname_dotcom_the_website %} are restricted. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)." ## Identifying the best authentication method for your enterprise @@ -76,29 +76,29 @@ You can use {% data variables.product.prodname_emus %} with an unsupported IdP o ### Do your developers work in public repositories, gists, or {% data variables.product.prodname_pages %} sites? -To prevent enterprise members from accidentally leaking corporate-owned content to the public on {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_emus %} imposes strong restrictions on what users can do. For example, {% data variables.product.prodname_managed_users %} cannot create public repositories, gists of any visibility, or {% data variables.product.prodname_pages %} sites that are visible outside the enterprise. For a full list of restrictions, see "[Abilities and restrictions of {% data variables.product.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-users)." +To prevent enterprise members from accidentally leaking corporate-owned content to the public on {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_emus %} imposes strong restrictions on what users can do. For example, {% data variables.enterprise.prodname_managed_users %} cannot create public repositories, gists of any visibility, or {% data variables.product.prodname_pages %} sites that are visible outside the enterprise. For a full list of restrictions, see "[Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-users)." These restrictions are unacceptable for some enterprises. To determine whether {% data variables.product.prodname_emus %} will work for you, review the restrictions with your developers, and confirm whether any of the restrictions will hinder your existing workflows. If so, SAML SSO may be a better choice for your enterprise. ### Do your developers rely on collaboration outside of your enterprise? -{% data variables.product.prodname_managed_users_caps %} can only contribute to repositories within your enterprise. If your developers must contribute to both repositories within and outside of your enterprise, including private repositories, {% data variables.product.prodname_emus %} may not be right for your enterprise. SAML SSO may be a better solution. +{% data variables.enterprise.prodname_managed_users_caps %} can only contribute to repositories within your enterprise. If your developers must contribute to both repositories within and outside of your enterprise, including private repositories, {% data variables.product.prodname_emus %} may not be right for your enterprise. SAML SSO may be a better solution. -Some companies maintain repositories within an existing enterprise using SAML SSO on {% data variables.product.product_location %}, and also create an {% data variables.product.prodname_emu_enterprise %}. Developers who contribute to repositories owned by both enterprises from a single workstation must switch between the accounts on {% data variables.product.product_location %} within a single browser, or use a different browser for each account. The developer may also need to customize the workstation's Git configuration to accommodate the two accounts. The complexity of this workflow can increase the risk of mistakenly leaking internal code to the public. +Some companies maintain repositories within an existing enterprise using SAML SSO on {% data variables.location.product_location %}, and also create an {% data variables.enterprise.prodname_emu_enterprise %}. Developers who contribute to repositories owned by both enterprises from a single workstation must switch between the accounts on {% data variables.location.product_location %} within a single browser, or use a different browser for each account. The developer may also need to customize the workstation's Git configuration to accommodate the two accounts. The complexity of this workflow can increase the risk of mistakenly leaking internal code to the public. -If you decide to create an {% data variables.product.prodname_emu_enterprise %} but require that developers contribute to resources outside of the enterprise from a single workstation, you can provide support for switching between the accounts in a developer's local Git configuration. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#supporting-developers-with-multiple-user-accounts-on-githubcom)." +If you decide to create an {% data variables.enterprise.prodname_emu_enterprise %} but require that developers contribute to resources outside of the enterprise from a single workstation, you can provide support for switching between the accounts in a developer's local Git configuration. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#supporting-developers-with-multiple-user-accounts-on-githubcom)." ### Does your enterprise rely on outside collaborators? With SAML SSO, you can give access to specific repositories to people who are not members of your IdP's directory, by using the outside collaborator role. This can be especially useful for collaborators that are external to your business, such as contractors. For more information, see "[Adding outside collaborators to repositories in your organization](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." -With {% data variables.product.prodname_emus %}, the outside collaborator role does not exist. Your enterprise's resources can only be accessed by {% data variables.product.prodname_managed_users %}, which are always provisioned by your IdP. To give external collaborators access to your enterprise, you would have to use guest accounts in your IdP. If you're interested in {% data variables.product.prodname_emus %}, confirm with your developers whether this will hinder any of their existing workflows. If so, SAML SSO may be a better solution. +With {% data variables.product.prodname_emus %}, the outside collaborator role does not exist. Your enterprise's resources can only be accessed by {% data variables.enterprise.prodname_managed_users %}, which are always provisioned by your IdP. To give external collaborators access to your enterprise, you would have to use guest accounts in your IdP. If you're interested in {% data variables.product.prodname_emus %}, confirm with your developers whether this will hinder any of their existing workflows. If so, SAML SSO may be a better solution. ### Can your enterprise tolerate migration costs? If your enterprise is new to {% data variables.product.prodname_dotcom_the_website %}, SAML SSO and {% data variables.product.prodname_emus %} are equally easy to adopt. -If you're already using {% data variables.product.prodname_dotcom_the_website %} with developers managing their own user accounts, adopting {% data variables.product.prodname_emus %} requires migrating to a new enterprise account. For more information, see "[About enterprises with {% data variables.product.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#about-enterprises-with-managed-users)." +If you're already using {% data variables.product.prodname_dotcom_the_website %} with developers managing their own user accounts, adopting {% data variables.product.prodname_emus %} requires migrating to a new enterprise account. For more information, see "[About enterprises with {% data variables.enterprise.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#about-enterprises-with-managed-users)." Although {% data variables.product.prodname_emus %} is free, the migration process may require time or cost from your team. Confirm that this migration process is acceptable to your business and your developers. If not, SAML SSO may be the better choice for you. @@ -119,7 +119,7 @@ The following authentication methods are available for {% data variables.product ### External authentication -If you use an external directory or identity provider (IdP) to centralize access to multiple web applications, you may be able to configure external authentication for {% data variables.product.product_location %}. For more information, see the following. +If you use an external directory or identity provider (IdP) to centralize access to multiple web applications, you may be able to configure external authentication for {% data variables.location.product_location %}. For more information, see the following. - "[Using CAS for enterprise IAM](/admin/identity-and-access-management/using-cas-for-enterprise-iam)" - "[Using LDAP for enterprise IAM](/admin/identity-and-access-management/using-ldap-for-enterprise-iam)" diff --git a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md index 40a98fb552..85b2acf6bd 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md @@ -1,6 +1,6 @@ --- -title: Alterando os métodos de autenticação -intro: 'A qualquer momento, você pode alterar a forma como o {% data variables.product.prodname_ghe_server %} se autentica com as contas existentes.' +title: Changing authentication methods +intro: 'You can change the way {% data variables.product.prodname_ghe_server %} authenticates with your existing accounts at any time.' redirect_from: - /enterprise/admin/user-management/changing-authentication-methods - /enterprise/admin/authentication/changing-authentication-methods @@ -16,33 +16,27 @@ topics: - Enterprise - Identity shortTitle: Change authentication methods -ms.openlocfilehash: 074c4fe8784d3ea7b8ada6b532e680384571facf -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147882688' --- -As contas de usuário do {% data variables.product.product_location %} são preservadas quando você altera o método de autenticação, e os usuários continuarão fazendo logon na mesma conta, desde que não haja alteração nos nomes de usuários. +User accounts on {% data variables.location.product_location %} are preserved when you change the authentication method and users will continue to log into the same account as long as their username doesn't change. -Se o novo método de autenticação alterar nomes de usuários, serão criadas novas contas. Como administrador, você pode renomear os usuários por meio das configurações de administração do site ou usando [a API de Administração do Usuário](/rest/reference/enterprise-admin#update-the-username-for-a-user). +If the new method of authentication changes usernames, new accounts will be created. As an administrator, you can rename users through the site admin settings or by using [the User Administration API](/rest/reference/enterprise-admin#update-the-username-for-a-user). -Veja outras questões que você deve manter em mente: +Other issues you should take into consideration include: -* **Senhas:** se você mudar para usar a autenticação interna na sua instância, os usuários precisarão [definir uma senha](/enterprise/user/articles/how-can-i-reset-my-password/) após a conclusão da alteração. +* **Passwords:** If you switch to using built-in authentication for your instance, users must [set a password](/enterprise/user/articles/how-can-i-reset-my-password/) after the change is completed. -* **Administradores do site:** os privilégios administrativos são [controlados pelo provedor de identidade quando você usa o SAML](/enterprise/admin/guides/user-management/using-saml/#saml-attributes) e pode ser [controlado pela associação a um grupo ao usar o LDAP](/enterprise/admin/authentication/using-ldap#configuring-ldap-with-your-github-enterprise-server-instance). +* **Site administrators:** Administrative privileges are [controlled by your identity provider when you use SAML](/enterprise/admin/guides/user-management/using-saml/#saml-attributes) and can be [controlled by group membership when you use LDAP](/enterprise/admin/authentication/using-ldap#configuring-ldap-with-your-github-enterprise-server-instance). -* **Associação a uma equipe:** somente o LDAP permite [controlar a associação a uma equipe](/enterprise/admin/authentication/using-ldap#configuring-ldap-with-your-github-enterprise-server-instance) no servidor de diretório. +* **Team membership:** Only LDAP lets you [control team membership](/enterprise/admin/authentication/using-ldap#configuring-ldap-with-your-github-enterprise-server-instance) from your directory server. -* **Suspensão do usuário:** quando você usa o LDAP para se autenticar, o acesso ao {% data variables.product.prodname_ghe_server %} pode ser controlado por meio de _grupos restritos_. Depois de alternar para o LDAP, se os grupos restritos estiverem configurados, os usuários que não estiverem nesses grupos serão suspensos. A suspensão ocorrerá quando eles fizerem login ou durante a próxima sincronização LDAP. +* **User suspension:** When you use LDAP to authenticate, access to {% data variables.product.prodname_ghe_server %} can be controlled via _restricted groups_. After switching to LDAP, if restricted groups are configured, existing users who are not in one of those groups will be suspended. Suspension will occur either when they log in or during the next LDAP Sync. -* **Associação a um grupo:** quando você usa o LDAP para se autenticar, os [usuários são suspensos e têm a suspensão cancelada automaticamente](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users) com base na associação a um grupo restrita e no status da conta com o Active Directory. +* **Group membership:** When you use LDAP to authenticate, users are automatically [suspended and unsuspended](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users) based on restricted group membership and account status with Active Directory. -* **Autenticação do Git:** o SAML e o CAS só dão suporte à autenticação do Git via HTTP ou HTTPS com um [token de acesso pessoal](/articles/creating-an-access-token-for-command-line-use). Não há suporte para a autenticação de senha em HTTP ou HTTPS. O LDAP dá suporte à autenticação do Git baseada em senha por padrão, mas recomendamos [desabilitar esse método](/enterprise/admin/authentication/using-ldap#disabling-password-authentication-for-git-operations) e forçar a autenticação por meio de um token de acesso pessoal ou de uma chave SSH. +* **Git authentication:** SAML and CAS only supports Git authentication over HTTP or HTTPS using a [{% data variables.product.pat_generic %}](/articles/creating-an-access-token-for-command-line-use). Password authentication over HTTP or HTTPS is not supported. LDAP supports password-based Git authentication by default, but we recommend that you [disable that method](/enterprise/admin/authentication/using-ldap#disabling-password-authentication-for-git-operations) and force authentication via a {% data variables.product.pat_generic %} or SSH key. -* **Autenticação de API:** o SAML e o CAS só dão suporte à autenticação de API com um [token de acesso pessoal](/articles/creating-an-access-token-for-command-line-use). Não há suporte para a autenticação básica. +* **API authentication:** SAML and CAS only supports API authentication using a [{% data variables.product.pat_generic %}](/articles/creating-an-access-token-for-command-line-use). Basic authentication is not supported. -* **Autenticação de dois fatores:** {% data reusables.enterprise_user_management.external_auth_disables_2fa %} +* **Two-factor authentication:** {% data reusables.enterprise_user_management.external_auth_disables_2fa %} -* **Autenticação de fallback para usuários sem conta em seu provedor de autenticação externo:** você pode convidar usuários a se autenticar em {% data variables.product.product_location %} sem adicioná-los ao seu provedor de identidade. Para obter mais informações, confira "[Como permitir a autenticação interna para usuários fora do seu provedor](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)". +* **Fallback authentication for users with no account on your external authentication provider:** You can invite users to authenticate to {% data variables.location.product_location %} without adding them to your identity provider. For more information, see "[Allowing built-in authentication for users outside your provider](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)." diff --git a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md index 6329bfccef..f43f417986 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md @@ -1,9 +1,12 @@ --- -title: Gerenciando o IAM da sua empresa +title: Managing IAM for your enterprise intro: | - {%- ifversion ghec %} Você pode convidar contas pessoais existentes em {% data variables.product.product_location %} para serem membros de sua empresa e, opcionalmente, habilitar o SSO (logon único) de SAML para gerenciar o acesso centralmente. Como alternativa, você pode usar {% data variables.product.prodname_emus %} com SSO de SAML para criar e controlar as contas de seus membros corporativos. - {%- elsif ghes %} Você pode usar a autenticação integrada do {% data variables.product.product_name %} ou pode gerenciar centralmente a autenticação e o acesso à sua instância com CAS, LDAP ou SAML. - {%- elsif ghae %} Você deve usar o SSO (logon único) de SAML para gerenciar centralmente a autenticação e o acesso à sua empresa em {% data variables.product.product_name %}. Opcionalmente, você pode usar o SCIM (Sistema de Gerenciamento de Usuários entre Domínios) para provisionar automaticamente contas e acesso em {% data variables.product.product_name %} ao fazer alterações em seu IdP (provedor de identidade). + {%- ifversion ghec %} + You can invite existing personal accounts on {% data variables.location.product_location %} to be members of your enterprise, and you can optionally enable SAML single sign-on (SSO) to centrally manage access. Alternatively, you can use {% data variables.product.prodname_emus %} with SAML SSO to create and control the accounts of your enterprise members. + {%- elsif ghes %} + You can use {% data variables.product.product_name %}'s built-in authentication, or you can centrally manage authentication and access to your instance with CAS, LDAP, or SAML. + {%- elsif ghae %} + You must use SAML single sign-on (SSO) to centrally manage authentication and access to your enterprise on {% data variables.product.product_name %}. Optionally, you can use System for Cross-domain Identity Management (SCIM) to automatically provision accounts and access on {% data variables.product.product_name %} when you make changes on your identity provider (IdP). {%- endif %} redirect_from: - /enterprise/admin/categories/authentication @@ -29,11 +32,5 @@ children: - /allowing-built-in-authentication-for-users-outside-your-provider - /troubleshooting-identity-and-access-management-for-your-enterprise shortTitle: Manage IAM for your enterprise -ms.openlocfilehash: 0af30fe07928336fd93ba3b17fd1efff0b64e354 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147718002' --- diff --git a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md index 822f11384e..2eaaa11272 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md @@ -30,7 +30,7 @@ topics: You can configure external authentication for {% data variables.product.product_name %} using CAS, LDAP, or SAML. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#authentication-methods-for-github-enterprise-server)." -When you use external authentication, {% data variables.product.product_location %} automatically creates a username for each person when the person signs into {% data variables.product.product_location %} through your external authentication system for the first time. +When you use external authentication, {% data variables.location.product_location %} automatically creates a username for each person when the person signs into {% data variables.location.product_location %} through your external authentication system for the first time. {% elsif ghec %} @@ -45,11 +45,11 @@ If you use an enterprise with {% data variables.product.prodname_emus %}, member {% endif %} {% ifversion ghec %} -## About usernames for {% data variables.product.prodname_managed_users %} +## About usernames for {% data variables.enterprise.prodname_managed_users %} -When your {% data variables.product.prodname_emu_enterprise %} is created, you will choose a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} The setup user who configures SAML SSO has a username in the format of **@SHORT-CODE_admin**. +When your {% data variables.enterprise.prodname_emu_enterprise %} is created, you will choose a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} The setup user who configures SAML SSO has a username in the format of **@SHORT-CODE_admin**. -When you provision a new user from your identity provider, the new {% data variables.product.prodname_managed_user %} will have a {% data variables.product.prodname_dotcom %} username in the format of **@IDP-USERNAME_SHORT-CODE**. The IDP-USERNAME component is formed by normalizing the SCIM `userName` attribute value sent from the IdP. +When you provision a new user from your identity provider, the new {% data variables.enterprise.prodname_managed_user %} will have a {% data variables.product.prodname_dotcom %} username in the format of **@IDP-USERNAME_SHORT-CODE**. The IDP-USERNAME component is formed by normalizing the SCIM `userName` attribute value sent from the IdP. | Identity provider | {% data variables.product.prodname_dotcom %} username | |-----------------------------------|----------------------| @@ -100,7 +100,7 @@ When you configure SAML authentication, {% data variables.product.product_name % {% ifversion not ghec %} ### About username normalization with SAML -{% ifversion ghes %}If you configure SAML authentication for {% data variables.product.product_location %}, {% endif %}{% data variables.product.product_name %} determines each person's username by one of the following assertions in the SAML response, ordered by descending priority. +{% ifversion ghes %}If you configure SAML authentication for {% data variables.location.product_location %}, {% endif %}{% data variables.product.product_name %} determines each person's username by one of the following assertions in the SAML response, ordered by descending priority. 1. The custom `username` attribute, if defined and present 1. An `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name` assertion, if present @@ -109,12 +109,12 @@ When you configure SAML authentication, {% data variables.product.product_name % {% data variables.product.product_name %} requires the `NameID` element even if other attributes are present. For more information, see "[SAML configuration reference](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-attributes)." -{% data variables.product.product_name %} creates a mapping between the `NameID` from the IdP and the username {% ifversion ghae %}in{% else %}on{% endif %} {% data variables.product.product_location %}, so the `NameID` should be persistent, unique, and not subject to change for the lifecycle of the user. +{% data variables.product.product_name %} creates a mapping between the `NameID` from the IdP and the username {% ifversion ghae %}in{% else %}on{% endif %} {% data variables.location.product_location %}, so the `NameID` should be persistent, unique, and not subject to change for the lifecycle of the user. {% ifversion ghes %} {% note %} -**Note**: If the `NameID` for a user does change on the IdP, the person will see an error message when signing into {% data variables.product.product_location %}. To restore the person's access, you'll need to update the user account's `NameID` mapping. For more information, see "[Updating a user's SAML `NameID`](/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid)." +**Note**: If the `NameID` for a user does change on the IdP, the person will see an error message when signing into {% data variables.location.product_location %}. To restore the person's access, you'll need to update the user account's `NameID` mapping. For more information, see "[Updating a user's SAML `NameID`](/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid)." {% endnote %} {% endif %} @@ -125,7 +125,7 @@ When you configure SAML authentication, {% data variables.product.product_name % When a new user is being provisioned, if the user's normalized username conflicts with an existing user in the enterprise, the provisioning attempt will fail with a `409` error. -To resolve this problem, you must make a change in your IdP so that the normalized usernames will be unique. If you cannot change the identifier that's being normalized, you can change the attribute mapping for the `userName` attribute. If you change the attribute mapping, usernames of existing {% data variables.product.prodname_managed_users %} will be updated, but nothing else about the accounts will change, including activity history. +To resolve this problem, you must make a change in your IdP so that the normalized usernames will be unique. If you cannot change the identifier that's being normalized, you can change the attribute mapping for the `userName` attribute. If you change the attribute mapping, usernames of existing {% data variables.enterprise.prodname_managed_users %} will be updated, but nothing else about the accounts will change, including activity history. {% note %} diff --git a/translations/pt-BR/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md b/translations/pt-BR/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md index 7261d31642..48536e3ec9 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md @@ -1,7 +1,7 @@ --- -title: Como fazer o download dos códigos de recuperação de logon único da conta empresarial +title: Downloading your enterprise account's single sign-on recovery codes shortTitle: Download recovery codes -intro: 'Para garantir que você possa acessar o {% data variables.product.product_name %} se o IdP (provedor de identidade) não estiver disponível, faça o download dos códigos de recuperação do SSO (logon único) do SAML da conta empresarial.' +intro: 'To ensure that you can access {% data variables.product.product_name %} if your identity provider (IdP) is unavailable, you should download your enterprise account''s single sign-on (SSO) recovery codes.' versions: ghec: '*' type: how_to @@ -13,27 +13,25 @@ topics: redirect_from: - /admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-saml-single-sign-on-recovery-codes permissions: Enterprise owners can download the SSO recovery codes for the enterprise account. -ms.openlocfilehash: 82f44654b18a36d2fb29797fe8b6e0426785522b -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147063591' --- -Caso seu IdP esteja indisponível, você pode usar um código de recuperação para efetuar o login e acessar seu negócio em {% data variables.product.product_location %}. Para obter mais informações, confira "[Como acessar sua conta corporativa se o seu provedor de identidade não estiver disponível](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/accessing-your-enterprise-account-if-your-identity-provider-is-unavailable)". -Se você não salvou os códigos de recuperação quando configurou o SSO do SAML, ainda poderá acessá-los nas configurações da empresa. +In the event that your IdP is unavailable, you can use a recovery code to sign in and access your enterprise on {% data variables.location.product_location %}. For more information, see "[Accessing your enterprise account if your identity provider is unavailable](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/accessing-your-enterprise-account-if-your-identity-provider-is-unavailable)." + +If you did not save your recovery codes when you configured SSO, you can still access the codes from your enterprise's settings. -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} -1. Em{% ifversion oidc-for-emu %} either{% endif %} "Exigir a autenticação do SAML"{% ifversion oidc-for-emu %} ou Exigir a autenticação do OIDC"{% endif %}, clique em **Salvar os códigos de recuperação**.{% ifversion oidc-for-emu %} {% note %} +1. Under{% ifversion oidc-for-emu %} either{% endif %} "Require SAML authentication"{% ifversion oidc-for-emu %} or "Require OIDC authentication"{% endif %}, click **Save your recovery codes**.{% ifversion oidc-for-emu %} + {% note %} - **Observação:** o SSO do OIDC só está disponível para {% data variables.product.prodname_emus %}. Para obter mais informações, confira "[Sobre os Usuários Gerenciados Corporativos](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)". + **Note:** OIDC SSO is only available for {% data variables.product.prodname_emus %}. For more information, see "[About Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)." {% endnote %}{% endif %} - ![Captura de tela do botão usado para testar a configuração do SAML antes da imposição](/assets/images/help/enterprises/saml-recovery-codes-link.png) -1. Para salvar os códigos de recuperação, clique em **Baixar**, **Imprimir** ou **Copiar**. - ![Captura de tela dos botões usados para baixar, imprimir ou copiar os códigos de recuperação](/assets/images/help/saml/saml_recovery_code_options.png) + ![Screenshot of the button to test SAML configuration before enforcing](/assets/images/help/enterprises/saml-recovery-codes-link.png) +1. To save your recovery codes, click **Download**, **Print**, or **Copy**. + ![Screenshot of the buttons to download, print, or copy your recovery codes](/assets/images/help/saml/saml_recovery_code_options.png) diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md b/translations/pt-BR/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md index 0c0584bbb8..50f7970f7e 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md @@ -1,6 +1,6 @@ --- -title: Configurar a autenticação integrada -intro: 'Quando você usa o método de autenticação padrão, todos os detalhes de autenticação são armazenados no {% data variables.product.product_location %}.' +title: Configuring built-in authentication +intro: 'When you use the default authentication method, all authentication details are stored on {% data variables.location.product_location %}.' permissions: 'Site administrators can configure authentication for a {% data variables.product.product_name %} instance.' redirect_from: - /enterprise/admin/user-management/using-built-in-authentication @@ -17,42 +17,41 @@ topics: - Enterprise - Identity shortTitle: Configure built-in authentication -ms.openlocfilehash: 6fbcd68efc953b5a32139a6907975e6918976860 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717810' --- -## Sobre a autenticação integrada -Por padrão, {% data variables.product.product_name %} usa autenticação integrada. Cada pessoa cria uma conta de usuário em {% data variables.product.product_location %} a partir de um convite ou inscrevendo-se e autentica com as credenciais da conta para acessar sua instância. Sua instância de {% data variables.product.product_name %} armazena as informações de autenticação da conta. +## About built-in authentication -Você pode impedir que pessoas não autenticadas criem novas contas de usuário em sua instância. Para obter mais informações, confira "[Desativar inscrições não autenticadas](/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups)". +By default, {% data variables.product.product_name %} uses built-in authentication. Each person creates a user account on {% data variables.location.product_location %} from an invitation or by signing up, and then authenticates with the credentials for the account to access your instance. Your {% data variables.product.product_name %} instance stores the authentication information for the account. + +You can prevent unauthenticated people from creating new user accounts on your instance. For more information, see "[Disabling unauthenticated sign-ups](/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups)." {% data reusables.enterprise_user_management.alternatively-enable-external-authentication %} -## Configurar a autenticação integrada +## Configuring built-in authentication -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.authentication %} -4. Selecione **Autenticação interna**. -![Opção Selecionar autenticação interna](/assets/images/enterprise/management-console/built-in-auth-select.png) +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.authentication %} +4. Select **Built in authentication**. +![Select built-in authentication option](/assets/images/enterprise/management-console/built-in-auth-select.png) -{% data reusables.enterprise_user_management.two_factor_auth_header %} {% data reusables.enterprise_user_management.2fa_is_available %} +{% data reusables.enterprise_user_management.two_factor_auth_header %} +{% data reusables.enterprise_user_management.2fa_is_available %} -## Criando a sua conta +## Creating your account -Uma vez que sua instância foi criada, você deverá criar a sua própria conta de administrador. +Once your instance has been created, you'll need to create your own admin account. -1. Na página "Criar Conta de Administrador" em `http(s)://[hostname]/join`, escolha seu nome de usuário, a senha e o endereço de email e clique em **Criar uma conta**. -![Criar Conta de Administrador](/assets/images/enterprise/site-admin-settings/create-first-admin-acct.png) {% data reusables.enterprise_site_admin_settings.sign-in %} +1. On the "Create Admin Account" page at `http(s)://[hostname]/join`, choose your username, password, and email address, then click **Create an account**. +![Create Admin Account](/assets/images/enterprise/site-admin-settings/create-first-admin-acct.png) +{% data reusables.enterprise_site_admin_settings.sign-in %} -## Próximas etapas +## Next steps -Depois de configurar a autenticação integrada e criar sua conta administrativa, você pode convidar pessoas para criar contas e usar sua instância. Para obter mais informações, confira "[Convidar pessoas para usar sua instância](/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance)". +After you configure built-in authentication and create your administrative account, you can invite people to create accounts and use your instance. For more information, see "[Inviting people to use your instance](/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance)." -## Leitura adicional +## Further reading -- "[Como configurar notificações por email](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)" +- "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)" diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md b/translations/pt-BR/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md index 2ba8940e7c..040dd977c6 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md @@ -1,5 +1,5 @@ --- -title: Desabilitar assinaturas não autenticadas +title: Disabling unauthenticated sign-ups redirect_from: - /enterprise/admin/articles/disabling-sign-ups - /enterprise/admin/user-management/disabling-unauthenticated-sign-ups @@ -7,7 +7,7 @@ redirect_from: - /admin/authentication/disabling-unauthenticated-sign-ups - /enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups - /admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups -intro: 'Se você estiver usando a autenticação interna do {% data variables.product.product_location %}, poderá impedir que pessoas não autenticadas criem contas de usuário em sua instância.' +intro: 'If you''re using built-in authentication for {% data variables.location.product_location %}, you can block unauthenticated people from creating new user accounts on your instance.' permissions: 'Site administrators can disable unauthenticated sign-ups on a {% data variables.product.product_name %} instance.' versions: ghes: '*' @@ -18,21 +18,19 @@ topics: - Enterprise - Identity shortTitle: Block unauthenticated sign-up -ms.openlocfilehash: 063da3aa1e73501d05251e40d7afcb271833afaf -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147065376' --- -## Sobre inscrição não autenticada -{% data reusables.enterprise_user_management.built-in-authentication-new-accounts %} {% data reusables.enterprise_user_management.unauthenticated-sign-ups %} Você pode desabilitar inscrições não autenticadas e exigir um convite para criar uma conta de usuário em sua instância. +## About unauthenticated sign-ups + +{% data reusables.enterprise_user_management.built-in-authentication-new-accounts %} {% data reusables.enterprise_user_management.unauthenticated-sign-ups %} You can disable unauthenticated sign-ups and require an invitation to create a new user account on your instance. {% data reusables.enterprise_user_management.alternatively-enable-external-authentication %} -## Desabilitar assinaturas não autenticadas +## Disabling unauthenticated sign-ups -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} -3. Desmarque **Habilitar a inscrição**. -![Caixa de seleção Habilitar inscrição](/assets/images/enterprise/management-console/enable-sign-up.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +3. Unselect **Enable sign-up**. +![Enable sign-up checkbox](/assets/images/enterprise/management-console/enable-sign-up.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md b/translations/pt-BR/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md index 957543a01a..826da0bc57 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md @@ -1,6 +1,6 @@ --- -title: Convidar pessoas para usar sua instância -intro: 'Ao usar a autenticação interna do {% data variables.product.product_name %}, você pode convidar pessoas por endereço de email para criar uma conta de usuário na sua instância.' +title: Inviting people to use your instance +intro: 'When you use built-in authentication for {% data variables.product.product_name %}, you can invite people by email address to create a user account on your instance.' versions: ghes: '*' permissions: 'Enterprise owners can invite people to create a user account on a {% data variables.product.product_name %} instance.' @@ -11,23 +11,20 @@ topics: - Enterprise - Identity shortTitle: Invite people -ms.openlocfilehash: d7ccb5e06f297a11ba97fa41d8250821909e5e3d -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717794' --- -## Sobre convites para usuários novos + +## About invitations for new users {% data reusables.enterprise_user_management.built-in-authentication-new-accounts %} {% data reusables.enterprise_user_management.unauthenticated-sign-ups %} -Você pode desabilitar inscrições não autenticadas e exigir um convite para criar uma conta de usuário em sua instância. Para saber mais, confira "[Desabilitar inscrição não autenticada](/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups)". +You can disable unauthenticated sign-ups and require an invitation to create a new user account on your instance. For more information, see "[Disabling unauthenticated sign-ups](/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups)." {% data reusables.enterprise_user_management.alternatively-enable-external-authentication %} -## Convidar pessoas para criar uma conta de usuário +## Inviting people to create a user account -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.invite-user-sidebar-tab %} {% data reusables.enterprise_site_admin_settings.invite-user-reset-link %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.invite-user-sidebar-tab %} +{% data reusables.enterprise_site_admin_settings.invite-user-reset-link %} -Se você habilitou o email para notificações em {% data variables.product.product_location %}, sua instância enviará o convite para o endereço de email fornecido. Para obter mais informações, confira "[Como configurar o email para notificações](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)". +If you've configured email for notifications on {% data variables.location.product_location %}, your instance will send the invitation to the provided email address. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)." diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md b/translations/pt-BR/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md index 06b02306fe..eb31c71027 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md @@ -1,16 +1,10 @@ --- -title: Usar o CAS para IAM empresarial +title: Using CAS for enterprise IAM shortTitle: CAS for enterprise IAM -intro: 'Você pode gerenciar as contas centralmente e acessar {% data variables.product.product_location %} ao integrar-se ao seu IdP (provedor de identidade) da CAS existente.' +intro: 'You can centrally manage accounts and access to {% data variables.location.product_location %} by integrating with your existing CAS identity provider (IdP).' versions: ghes: '*' children: - /using-cas -ms.openlocfilehash: cc611feeed0f22033ed0c92883b3f95afe41ea92 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145095874' --- diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md b/translations/pt-BR/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md index 0610f81781..80a7879125 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md @@ -1,5 +1,5 @@ --- -title: Usar CAS +title: Using CAS redirect_from: - /enterprise/admin/articles/configuring-cas-authentication - /enterprise/admin/articles/about-cas-authentication @@ -8,7 +8,7 @@ redirect_from: - /admin/authentication/using-cas - /enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas - /admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-cas -intro: 'Se você usar o CAS (Serviço de Autenticação Central) para centralizar o acesso a vários aplicativos Web, poderá integrar o {% data variables.product.product_name %} configurando a autenticação do CAS para sua instância.' +intro: 'If you use Central Authentication Service (CAS) to centralize access to multiple web applications, you can integrate {% data variables.product.product_name %} by configuring CAS authentication for your instance.' versions: ghes: '*' type: how_to @@ -18,42 +18,39 @@ topics: - Enterprise - Identity - SSO -ms.openlocfilehash: 4bd9c8baf32ab09c593a251ca4f1cb698e075501 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147884274' --- -## Sobre a autenticação do CAS no {% data variables.product.product_name %} -O CAS é um protocolo de SSO (logon único) que centraliza a autenticação em vários aplicativos Web. Para obter mais informações, confira "[Central Authentication Service](https://en.wikipedia.org/wiki/Central_Authentication_Service)" no Wikipédia. +## About CAS authentication for {% data variables.product.product_name %} -Depois de configurar o CAS, as pessoas que usam o {% data variables.product.product_location %} devem usar um token de acesso pessoal para autenticar solicitações de API ou Git por HTTP(S). As credenciais do CAS não podem ser usadas para autenticar essas solicitações. Para obter mais informações, confira "[Como criar um token de acesso pessoal](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)". +CAS is a single sign-on (SSO) protocol that centralizes authentication to multiple web applications. For more information, see "[Central Authentication Service](https://en.wikipedia.org/wiki/Central_Authentication_Service)" on Wikipedia. -Se você configurar o CAS, as pessoas com contas em seu IdP (provedor de identidade) não consumirão uma licença de usuário até que a pessoa entre no {% data variables.product.product_location %}. +After you configure CAS, people who use {% data variables.location.product_location %} must use a {% data variables.product.pat_generic %} to authenticate API or Git requests over HTTP(S). CAS credentials cannot be used to authenticate these requests. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." + +If you configure CAS, people with accounts on your identity provider (IdP) do not consume a user license until the person signs into {% data variables.location.product_location %}. {% data reusables.enterprise_user_management.built-in-authentication %} -## Considerações de nome de usuário no CAS +## Username considerations with CAS -{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} Para obter mais informações, veja "[Considerações de nome de usuário para autenticação externa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)". +{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)." -## Atributos CAS +## CAS attributes -Os atributos a seguir estão disponíveis. +The following attributes are available. -| Nome do atributo | Tipo | Descrição | +| Attribute name | Type | Description | |--------------------------|----------|-------------| -| `username` | Obrigatório | Nome do usuário no {% data variables.product.prodname_ghe_server %}. | +| `username` | Required | The {% data variables.product.prodname_ghe_server %} username. | -## Configurar o CAS +## Configuring CAS -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.authentication %} -3. Selecione **CAS**. +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.authentication %} +3. Select **CAS**. - ![Captura de tela da seleção do CAS para autenticação](/assets/images/enterprise/management-console/cas-select.png) + ![Screenshot of selection of CAS for authentication](/assets/images/enterprise/management-console/cas-select.png) 4. {% data reusables.enterprise_user_management.built-in-authentication-option %} - ![Captura de tela da opção de autenticação interna de fallback do CAS](/assets/images/enterprise/management-console/cas-built-in-authentication.png) -5. No campo **URL do Servidor**, digite a URL completa do servidor CAS. Se o servidor CAS usar um certificado que não pode ser validado pelo {% data variables.product.prodname_ghe_server %}, use o comando `ghe-ssl-ca-certificate-install` para instalá-lo como um certificado confiável. Para obter mais informações, confira "[Utilitários de linha de comando](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-ssl-ca-certificate-install)". + ![Screenshot of of fallback built-in authentication option for CAS](/assets/images/enterprise/management-console/cas-built-in-authentication.png) +5. In the **Server URL** field, type the full URL of your CAS server. If your CAS server uses a certificate that can't be validated by {% data variables.product.prodname_ghe_server %}, you can use the `ghe-ssl-ca-certificate-install` command to install it as a trusted certificate. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-ssl-ca-certificate-install)." diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md b/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md index 1444925cd5..90a11171f2 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md @@ -22,9 +22,9 @@ topics: With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access for the user accounts from your IdP. -In your IdP, you can give each {% data variables.product.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.product.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.product.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." +In your IdP, you can give each {% data variables.enterprise.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.enterprise.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.enterprise.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." -Organization membership can be managed manually, or you can update membership automatically as {% data variables.product.prodname_managed_users %} are added to IdP groups that are connected to teams within the organization. When a {% data variables.product.prodname_managed_user %} is manually added to an organization, unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization. For more information about managing organization and team membership automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)." +Organization membership can be managed manually, or you can update membership automatically as {% data variables.enterprise.prodname_managed_users %} are added to IdP groups that are connected to teams within the organization. When a {% data variables.enterprise.prodname_managed_user %} is manually added to an organization, unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization. For more information about managing organization and team membership automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)." {% ifversion oidc-for-emu %} @@ -32,11 +32,11 @@ Organization membership can be managed manually, or you can update membership au {% endif %} -You can grant {% data variables.product.prodname_managed_users %} access to and the ability to contribute to repositories within your enterprise, but {% data variables.product.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. For more information, see "[Abilities and restrictions of {% data variables.product.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users)." +You can grant {% data variables.enterprise.prodname_managed_users %} access to and the ability to contribute to repositories within your enterprise, but {% data variables.enterprise.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. For more information, see "[Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users)." -The usernames of your enterprise's {% data variables.product.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)." +The usernames of your enterprise's {% data variables.enterprise.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)." -Enterprise owners can audit all of the {% data variables.product.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}. For more information, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise)." +Enterprise owners can audit all of the {% data variables.enterprise.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}. For more information, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise)." To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. For more information about creating this account, see "[About enterprises with managed users](#about-enterprises-with-managed-users)." @@ -60,24 +60,25 @@ To use {% data variables.product.prodname_emus %}, you need a separate type of e {% endif %} -## Abilities and restrictions of {% data variables.product.prodname_managed_users %} +## Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %} -{% data variables.product.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.product.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. These visibility and access restrictions for users and content apply to all requests, including API requests. +{% data variables.enterprise.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.enterprise.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. These visibility and access restrictions for users and content apply to all requests, including API requests. -* {% data variables.product.prodname_managed_users_caps %} cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.product.prodname_managed_users %} be invited to other enterprises. +* {% data variables.enterprise.prodname_managed_users_caps %} cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.enterprise.prodname_managed_users %} be invited to other enterprises. * Outside collaborators are not supported by {% data variables.product.prodname_emus %}. -* {% data variables.product.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise. -* {% data variables.product.prodname_managed_users_caps %} can view all public repositories on {% data variables.product.prodname_dotcom_the_website %}, but cannot push code to repositories outside of the enterprise. -* {% data variables.product.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise. -* {% data variables.product.prodname_managed_users_caps %} cannot follow users outside of the enterprise. -* {% data variables.product.prodname_managed_users_caps %} cannot create gists or comment on gists. -* {% data variables.product.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts. -* Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.product.prodname_managed_user %} to collaborate. -* You can choose whether {% data variables.product.prodname_managed_users %} are able to create repositories owned by their user accounts. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)." -* If you allow {% data variables.product.prodname_managed_users %} to create repositories owned by their user accounts, they can only own private repositories and can only invite other enterprise members to collaborate on their user-owned repositories. +* {% data variables.enterprise.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise. +* {% data variables.enterprise.prodname_managed_users_caps %} can view all public repositories on {% data variables.product.prodname_dotcom_the_website %}, but cannot push code to repositories outside of the enterprise. +* {% data variables.enterprise.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise. +* {% data variables.enterprise.prodname_managed_users_caps %} cannot follow users outside of the enterprise. +* {% data variables.enterprise.prodname_managed_users_caps %} cannot create gists or comment on gists. +* {% data variables.enterprise.prodname_managed_users_caps %} cannot create starter workflows for {% data variables.product.prodname_actions %}. +* {% data variables.enterprise.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts. +* Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.enterprise.prodname_managed_user %} to collaborate. +* You can choose whether {% data variables.enterprise.prodname_managed_users %} are able to create repositories owned by their user accounts. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)." +* If you allow {% data variables.enterprise.prodname_managed_users %} to create repositories owned by their user accounts, they can only own private repositories and can only invite other enterprise members to collaborate on their user-owned repositories. * {% data reusables.enterprise-accounts.emu-forks %} -* Only private and internal repositories can be created in organizations owned by an {% data variables.product.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings. -* {% data variables.product.prodname_managed_users_caps %} are limited in their use of {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)." +* Only private and internal repositories can be created in organizations owned by an {% data variables.enterprise.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings. +* {% data variables.enterprise.prodname_managed_users_caps %} are limited in their use of {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)." ## Getting started with {% data variables.product.prodname_emus %} @@ -85,7 +86,7 @@ Before your developers can use {% data variables.product.prodname_ghe_cloud %} w 1. To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. To try out {% data variables.product.prodname_emus %} or to discuss options for migrating from your existing enterprise, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). - Your contact on the GitHub Sales team will work with you to create your new {% data variables.product.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)." + Your contact on the GitHub Sales team will work with you to create your new {% data variables.enterprise.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)." 2. After we create your enterprise, you will receive an email from {% data variables.product.prodname_dotcom %} inviting you to choose a password for your enterprise's setup user, which will be the first owner in the enterprise. Use an incognito or private browsing window when setting the password. The setup user is only used to configure single sign-on and SCIM provisioning integration for the enterprise. It will no longer have access to administer the enterprise account once SSO is successfully enabled. The setup user's username is your enterprise's shortcode suffixed with `_admin`. @@ -112,17 +113,17 @@ Before your developers can use {% data variables.product.prodname_ghe_cloud %} w 5. Once authentication and provisioning are configured, you can start provisioning members and managing teams. For more information, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)." -If members of your enterprise must use one workstation to contribute to repositories on {% data variables.product.product_location %} from both a {% data variables.product.prodname_managed_user %} and a personal account, you can provide support. For more information, see "[Supporting developers with multiple user accounts on {% data variables.product.prodname_dotcom_the_website %}](#supporting-developers-with-multiple-user-accounts-on-githubcom)." +If members of your enterprise must use one workstation to contribute to repositories on {% data variables.location.product_location %} from both a {% data variables.enterprise.prodname_managed_user %} and a personal account, you can provide support. For more information, see "[Supporting developers with multiple user accounts on {% data variables.product.prodname_dotcom_the_website %}](#supporting-developers-with-multiple-user-accounts-on-githubcom)." -## Authenticating as a {% data variables.product.prodname_managed_user %} +## Authenticating as a {% data variables.enterprise.prodname_managed_user %} -{% data variables.product.prodname_managed_users_caps %} must authenticate through their identity provider. To authenticate, a {% data variables.product.prodname_managed_user %} can visit their IdP application portal or use the login page on {% data variables.product.prodname_dotcom_the_website %}. +{% data variables.enterprise.prodname_managed_users_caps %} must authenticate through their identity provider. To authenticate, a {% data variables.enterprise.prodname_managed_user %} can visit their IdP application portal or use the login page on {% data variables.product.prodname_dotcom_the_website %}. By default, when an unauthenticated user attempts to access an enterprise that uses {% data variables.product.prodname_emus %}, {% data variables.product.company_short %} displays a 404 error. An enterprise owner can optionally enable automatic redirects to single sign-on (SSO) instead of the 404. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)." {% data reusables.enterprise-accounts.about-recovery-codes %} For more information, see "[Managing recovery codes for your enterprise](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)." -### Authenticating as a {% data variables.product.prodname_managed_user %} via {% data variables.product.prodname_dotcom_the_website %} +### Authenticating as a {% data variables.enterprise.prodname_managed_user %} via {% data variables.product.prodname_dotcom_the_website %} 1. Navigate to [https://github.com/login](https://github.com/login). 1. In the "Username or email address" text box, enter your username including the underscore and short code. @@ -137,10 +138,10 @@ By default, when an unauthenticated user attempts to access an enterprise that u A conflict may occur when provisioning users if the unique parts of the identifier provided by your IdP are removed during normalization. {% data reusables.enterprise-accounts.emu-only-emails-within-the-enterprise-can-conflict %} If you're unable to provision a user due to a username conflict, you should modify the username provided by your IdP. For more information, see "[Resolving username conflicts](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-conflicts)." -The profile name and email address of a {% data variables.product.prodname_managed_user %} is also provided by the IdP. {% data variables.product.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}, and the IdP can only provide a single email address. +The profile name and email address of a {% data variables.enterprise.prodname_managed_user %} is also provided by the IdP. {% data variables.enterprise.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}, and the IdP can only provide a single email address. -## Supporting developers with multiple user accounts on {% data variables.product.product_location %} +## Supporting developers with multiple user accounts on {% data variables.location.product_location %} -People on your team may need to contribute to resources on {% data variables.product.product_location %} that are outside of your {% data variables.product.prodname_emu_enterprise %}. For example, you may wish to maintain a separate enterprise for your company's open source projects. Because a {% data variables.product.prodname_managed_user %} cannot contribute to public resources, users will need to maintain a separate, personal account for this work. +People on your team may need to contribute to resources on {% data variables.location.product_location %} that are outside of your {% data variables.enterprise.prodname_emu_enterprise %}. For example, you may wish to maintain a separate enterprise for your company's open source projects. Because a {% data variables.enterprise.prodname_managed_user %} cannot contribute to public resources, users will need to maintain a separate, personal account for this work. -People who must contribute from two user accounts on {% data variables.product.product_location %} using one workstation can configure Git to simplify the process. For more information, see "[Managing multiple accounts](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)." +People who must contribute from two user accounts on {% data variables.location.product_location %} using one workstation can configure Git to simplify the process. For more information, see "[Managing multiple accounts](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)." diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md b/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md index 28d9c00c89..74dd43ee44 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md @@ -18,7 +18,7 @@ topics: {% data reusables.enterprise-accounts.emu-cap-validates %} -CAP support is enabled automatically for any {% data variables.product.prodname_emu_enterprise %} that enables OIDC SSO and cannot be disabled. {% data variables.product.prodname_dotcom %} enforces your IdP's IP conditions but not device compliance conditions. +CAP support is enabled automatically for any {% data variables.enterprise.prodname_emu_enterprise %} that enables OIDC SSO and cannot be disabled. {% data variables.product.prodname_dotcom %} enforces your IdP's IP conditions but not device compliance conditions. For more information about using OIDC with {% data variables.product.prodname_emus %}, see "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)" and "[Migrating from SAML to OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)." @@ -36,9 +36,9 @@ For more information about using OIDC with {% data variables.product.prodname_em ### {% data variables.product.prodname_actions %} -Actions that use a personal access token will likely be blocked by your IdP's CAP. We recommend that personal access tokens are created by a service account which is then exempted from IP controls in your IdP's CAP. +Actions that use a {% data variables.product.pat_generic %} will likely be blocked by your IdP's CAP. We recommend that {% data variables.product.pat_generic %}s are created by a service account which is then exempted from IP controls in your IdP's CAP. -If you're unable to use a service account, another option for unblocking actions that use personal access tokens is to allow the IP ranges used by {% data variables.product.prodname_actions %}. For more information, see "[About GitHub's IP addresses](/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses)." +If you're unable to use a service account, another option for unblocking actions that use {% data variables.product.pat_generic %}s is to allow the IP ranges used by {% data variables.product.prodname_actions %}. For more information, see "[About GitHub's IP addresses](/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses)." ### {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md b/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md index ead517a68a..66e9c9d84f 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md @@ -1,7 +1,7 @@ --- -title: Como configurar o OIDC para usuários empresariais gerenciados +title: Configuring OIDC for Enterprise Managed Users shortTitle: OIDC for managed users -intro: 'Você pode gerenciar automaticamente o acesso à conta empresarial no {% data variables.product.prodname_dotcom %} configurando o SSO (logon único) do OIDC (OpenID Connect) e habilitar o suporte para a CAP (política de acesso condicional) do IdP.' +intro: 'You can automatically manage access to your enterprise account on {% data variables.product.prodname_dotcom %} by configuring OpenID Connect (OIDC) single sign-on (SSO) and enable support for your IdP''s Conditional Access Policy (CAP).' product: '{% data reusables.gated-features.emus %}' versions: feature: oidc-for-emu @@ -10,42 +10,40 @@ topics: - Authentication - Enterprise - SSO -ms.openlocfilehash: d52626ad035d957a7908e07e81d12824b9601ee5 -ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147061775' --- + {% data reusables.enterprise-accounts.oidc-beta-notice %} -## Sobre o OIDC para usuários empresariais gerenciados +## About OIDC for Enterprise Managed Users -Com {% data variables.product.prodname_emus %}, sua empresa usa o IdP (provedor de identidade) para autenticar todos os membros. Você pode usar o OIDC (OpenID Connect) para gerenciar a autenticação do {% data variables.product.prodname_emu_enterprise %}. A habilitação do SSO do OIDC é um processo de configuração de um clique com certificados gerenciados pelo {% data variables.product.prodname_dotcom %} e pelo IdP. +With {% data variables.product.prodname_emus %}, your enterprise uses your identity provider (IdP) to authenticate all members. You can use OpenID Connect (OIDC) to manage authentication for your {% data variables.enterprise.prodname_emu_enterprise %}. Enabling OIDC SSO is a one-click setup process with certificates managed by {% data variables.product.prodname_dotcom %} and your IdP. -{% data reusables.enterprise-accounts.emu-cap-validates %} Para obter mais informações, confira "[Sobre o suporte à política de acesso condicional do IdP](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)". +{% data reusables.enterprise-accounts.emu-cap-validates %} For more information, see "[About support for your IdP's Conditional Access Policy](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)." -Você pode ajustar o tempo de vida de uma sessão e a frequência em que um {% data variables.product.prodname_managed_user %} precisa ser reautenticado no IdP alterando a propriedade de política de tempo de vida dos tokens de ID emitidos para o {% data variables.product.prodname_dotcom %} pelo IdP. O tempo de vida padrão é de uma hora. Para obter mais informações, confira "[Tempos de vida de token configuráveis na plataforma de identidade da Microsoft](https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-lifetimes)" na documentação do Azure AD. +You can adjust the lifetime of a session, and how often a {% data variables.enterprise.prodname_managed_user %} needs to reauthenticate with your IdP, by changing the lifetime policy property of the ID tokens issued for {% data variables.product.prodname_dotcom %} from your IdP. The default lifetime is one hour. For more information, see "[Configurable token lifetimes in the Microsoft identity platform](https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-lifetimes)" in the Azure AD documentation. -Se você usa o SSO do SAML para autenticação no momento, mas gostaria de usar o OIDC e se beneficiar do suporte ao CAP, siga o caminho da migração. Para obter mais informações, confira "[Como migrar do SAML para o OICD](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)". +If you currently use SAML SSO for authentication and would prefer to use OIDC and benefit from CAP support, you can follow a migration path. For more information, see "[Migrating from SAML to OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)." {% data reusables.enterprise-accounts.oidc-gei-warning %} -## Suporte do provedor de identidade +## Identity provider support -O suporte ao OIDC está em versão beta pública e disponível para clientes que usam o Azure AD (Azure Active Directory). +Support for OIDC is in public beta and available for customers using Azure Active Directory (Azure AD). -Cada locatário do Azure AD pode dar suporte a apenas uma integração do OIDC com {% data variables.product.prodname_emus %}. Se você quiser conectar o Azure AD a mais de uma empresa no {% data variables.product.prodname_dotcom %}, use o SAML. Para saber mais, confira "[Como configurar o logon único do SAML para {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users)". +Each Azure AD tenant can support only one OIDC integration with {% data variables.product.prodname_emus %}. If you want to connect Azure AD to more than one enterprise on {% data variables.product.prodname_dotcom %}, use SAML instead. For more information, see "[Configuring SAML single sign-on for {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users)." -## Como configurar o OIDC para usuários empresariais gerenciados +## Configuring OIDC for Enterprise Managed Users -1. Entre no {% data variables.product.prodname_dotcom_the_website %} como o usuário de instalação para sua nova empresa com o nome de usuário **@SHORT-CODE_admin**. -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} -1. Selecione **Exigir logon único do OIDC**. - ![Captura de tela mostrando a caixa de seleção "Exigir logon único do OIDC"](/assets/images/help/enterprises/require-oidc.png) -1. Para continuar a instalação e ser redirecionado ao Azure AD, clique em **Salvar**. -{% data reusables.enterprise-accounts.emu-azure-admin-consent %} {% data reusables.enterprise-accounts.download-recovery-codes %} +1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@SHORT-CODE_admin**. +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +1. Select **Require OIDC single sign-on**. + ![Screenshot showing the "Require OIDC single sign-on" checkbox](/assets/images/help/enterprises/require-oidc.png) +1. To continue setup and be redirected to Azure AD, click **Save**. +{% data reusables.enterprise-accounts.emu-azure-admin-consent %} +{% data reusables.enterprise-accounts.download-recovery-codes %} -## Habilitando provisionamento +## Enabling provisioning -Depois que você habilitar o SSO do OIDC, habilite o provisionamento. Para obter mais informações, confira "[Como configurar o provisionamento do SCIM para os usuários gerenciados corporativos](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)". +After you enable OIDC SSO, enable provisioning. For more information, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)." diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md b/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md index 3cbc6464d2..fe4dde3d44 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md @@ -1,7 +1,7 @@ --- -title: Configurar o logon único SAML para usuários gerenciados pela empresa +title: Configuring SAML single sign-on for Enterprise Managed Users shortTitle: SAML for managed users -intro: 'Pode gerenciar automaticamente o acesso à sua conta corporativa em {% data variables.product.prodname_dotcom %} configurando o logon único SAML (SSO) da Linguagem de Markup de Declaração de Segurança.' +intro: 'You can automatically manage access to your enterprise account on {% data variables.product.prodname_dotcom %} by configuring Security Assertion Markup Language (SAML) single sign-on (SSO).' product: '{% data reusables.gated-features.emus %}' redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users @@ -15,34 +15,29 @@ topics: - Authentication - Enterprise - SSO -ms.openlocfilehash: 8464afda7b87f23d7466851901536668c4440944 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145955487' --- -## Sobre o logon único SAML para {% data variables.product.prodname_emus %} -Com {% data variables.product.prodname_emus %}, a sua empresa usa o SAML SSO para autenticar todos os integrantes. Ao invés de efetuar o login em {% data variables.product.prodname_dotcom %} com um nome de usuário e senha {% data variables.product.prodname_dotcom %}, os integrantes da sua empresa efetuarão o login por meio do seu IdP. +## About SAML single sign-on for {% data variables.product.prodname_emus %} -{% data variables.product.prodname_emus %} é compatível com os seguintes IdPs: +With {% data variables.product.prodname_emus %}, your enterprise uses SAML SSO to authenticate all members. Instead of signing in to {% data variables.product.prodname_dotcom %} with a {% data variables.product.prodname_dotcom %} username and password, members of your enterprise will sign in through your IdP. + +{% data variables.product.prodname_emus %} supports the following IdPs: {% data reusables.enterprise-accounts.emu-supported-idps %} -Depois de configurar o SAM SSO, recomendamos armazenar seus códigos de recuperação para que você possa recuperar o acesso à sua empresa no caso de o seu provedor de identidade não estar disponível. +After you configure SAML SSO, we recommend storing your recovery codes so you can recover access to your enterprise in the event that your identity provider is unavailable. {% note %} -**Observação:** quando o SSO do SAML está habilitado, a única configuração que você pode atualizar no {% data variables.product.prodname_dotcom %} para a configuração do SAML existente é o certificado SAML. Se você precisar atualizar o URL de login ou o emissor, primeiro desabilite o SAML SSO e, em seguida, redefina o SAML SSO com as novas configurações. +**Note:** When SAML SSO is enabled, the only setting you can update on {% data variables.product.prodname_dotcom %} for your existing SAML configuration is the SAML certificate. If you need to update the Sign on URL or Issuer, you must first disable SAML SSO and then reconfigure SAML SSO with the new settings. {% endnote %} -## Configurando o logon único da SAML para {% data variables.product.prodname_emus %} +## Configuring SAML single sign-on for {% data variables.product.prodname_emus %} -Para configurar o SAML SSO para o seu {% data variables.product.prodname_emu_enterprise %}, configure um aplicativo no seu IdP e, em seguida, configure a sua empresa no GitHub.com. Depois de configurar o SAML SSO, você poderá configurar o provisionamento de usuários. +To configure SAML SSO for your {% data variables.enterprise.prodname_emu_enterprise %}, you must configure an application on your IdP and then configure your enterprise on GitHub.com. After you configure SAML SSO, you can configure user provisioning. -Para instalar e configurar o aplicativo {% data variables.product.prodname_emu_idp_application %} no seu IdP, você deve ter acesso a de inquilino e acesso administrativo em um IdP compatível. +To install and configure the {% data variables.product.prodname_emu_idp_application %} application on your IdP, you must have a tenant and administrative access on a supported IdP. {% note %} @@ -50,71 +45,73 @@ Para instalar e configurar o aplicativo {% data variables.product.prodname_emu_i {% endnote %} -1. [Como configurar seu provedor de identidade](#configuring-your-identity-provider) -2. [Configurar a sua empresa](#configuring-your-enterprise) -3. [Habilitando provisionamento](#enabling-provisioning) +1. [Configuring your identity provider](#configuring-your-identity-provider) +2. [Configuring your enterprise](#configuring-your-enterprise) +3. [Enabling provisioning](#enabling-provisioning) -### Configurando seu provedor de identidade +### Configuring your identity provider -Para configurar seu IdP, siga as instruções fornecidas para configurar o aplicativo de {% data variables.product.prodname_emu_idp_application %} no seu IdP. +To configure your IdP, follow the instructions they provide for configuring the {% data variables.product.prodname_emu_idp_application %} application on your IdP. -1. Para instalar o aplicativo {% data variables.product.prodname_emu_idp_application %}, clique no link para acessar o seu IdP abaixo: +1. To install the {% data variables.product.prodname_emu_idp_application %} application, click the link for your IdP below: - - [Aplicativo do {% data variables.product.prodname_emu_idp_application %} no Azure Active Directory](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/aad.githubenterprisemanageduser?tab=Overview) - - [Aplicativo do {% data variables.product.prodname_emu_idp_application %} no Okta](https://www.okta.com/integrations/github-enterprise-managed-user) + - [{% data variables.product.prodname_emu_idp_application %} application on Azure Active Directory](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/aad.githubenterprisemanageduser?tab=Overview) + - [{% data variables.product.prodname_emu_idp_application %} application on Okta](https://www.okta.com/integrations/github-enterprise-managed-user) -1. Para configurar o aplicativo de {% data variables.product.prodname_emu_idp_application %} e seu IdP, clique no link abaixo e siga as instruções fornecidas pelo seu IdP: +1. To configure the {% data variables.product.prodname_emu_idp_application %} application and your IdP, click the link below and follow the instructions provided by your IdP: - - [Tutorial do Azure Active Directory sobre o {% data variables.product.prodname_emus %}](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-tutorial) - - [Documentação do Okta sobre o {% data variables.product.prodname_emus %}](https://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-GitHub-Enterprise-Managed-User.html) + - [Azure Active Directory tutorial for {% data variables.product.prodname_emus %}](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-tutorial) + - [Okta documentation for {% data variables.product.prodname_emus %}](https://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-GitHub-Enterprise-Managed-User.html) -1. Dessa forma, você pode testar e configurar a sua empresa, atribuir a si mesmo ou o usuário que irá configurar o SAML SSO em {% data variables.product.prodname_dotcom %} para a o aplicativo de {% data variables.product.prodname_emu_idp_application %} no seu IdP. +1. So you can test and configure your enterprise, assign yourself or the user that will be configuring SAML SSO on {% data variables.product.prodname_dotcom %} to the {% data variables.product.prodname_emu_idp_application %} application on your IdP. -1. Para permitir que você continue configurando sua empresa em {% data variables.product.prodname_dotcom %}, localize e observe as informações a seguir do aplicativo que você instalou no seu IdP: +1. To enable you to continue configuring your enterprise on {% data variables.product.prodname_dotcom %}, locate and note the following information from the application you installed on your IdP: - | Valor | Outros nomes | Descrição | + | Value | Other names | Description | | :- | :- | :- | - | IdP Sign-On URL | Login URL, IdP URL | URL do aplicativo no seu IdP | - | IdP Identifier URL | Emissor | Identificador de o IdP para prestadores de serviço para autenticação do SAML | - | Certificado de assinatura, codificado em Base64 | Certificado público | Certificado público que o IdP usa para assinar solicitações de autenticação | + | IdP Sign-On URL | Login URL, IdP URL | Application's URL on your IdP | + | IdP Identifier URL | Issuer | IdP's identifier to service providers for SAML authentication | + | Signing certificate, Base64-encoded | Public certificate | Public certificate that IdP uses to sign authentication requests | -### Configurar a sua empresa +### Configuring your enterprise -Após instalar e configurar o aplicativo de {% data variables.product.prodname_emu_idp_application %} no seu provedor de identidade, você poderá configurar a sua empresa. +After you install and configure the {% data variables.product.prodname_emu_idp_application %} application on your identity provider, you can configure your enterprise. -1. Entre no {% data variables.product.prodname_dotcom_the_website %} como o usuário de instalação para sua nova empresa com o nome de usuário **@SHORT-CODE_admin**. +1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@SHORT-CODE_admin**. -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} -1. Em "Logon único do SAML", selecione **Exigir autenticação SAML**. - ![Caixa de seleção usada para habilitar o SSO do SAML](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) +1. Under "SAML single sign-on", select **Require SAML authentication**. + ![Checkbox for enabling SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) -1. Na **URL de Logon**, digite o ponto de extremidade HTTPS do IdP para solicitações de logon único que você anotou ao configurar o IdP. -![Campo referente à URL para a qual os membros serão encaminhados após a entrada](/assets/images/help/saml/saml_sign_on_url_business.png) +1. Under **Sign on URL**, type the HTTPS endpoint of your IdP for single sign-on requests that you noted while configuring your IdP. +![Field for the URL that members will be forwarded to when signing in](/assets/images/help/saml/saml_sign_on_url_business.png) -1. No **Emissor**, digite a URL do emissor do SAML que você anotou ao configurar o IdP para verificar a autenticidade das mensagens enviadas. -![Campo referente ao nome do emissor do SAML](/assets/images/help/saml/saml_issuer.png) +1. Under **Issuer**, type your SAML issuer URL that you noted while configuring your IdP, to verify the authenticity of sent messages. +![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png) -1. Em **Certificado Público**, cole o certificado que você anotou ao configurar seu IdP para verificar as respostas SAML. -![Campo referente ao certificado público do provedor de identidade](/assets/images/help/saml/saml_public_certificate.png) +1. Under **Public Certificate**, paste the certificate that you noted while configuring your IdP, to verify SAML responses. +![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png) -1. Para verificar a integridade das solicitações do emissor do SAML, clique em {% octicon "pencil" aria-label="The edit icon" %}. Em seguida, no menu suspenso "Método de assinatura" e "Método de resumo", escolha o algoritmo de hashing usado pelo seu emissor do SAML. -![Menus suspensos dos algoritmos de hash Método de Assinatura e Método de resumo usados pelo emissor do SAML](/assets/images/help/saml/saml_hashing_method.png) +1. To verify the integrity of the requests from your SAML issuer, click {% octicon "pencil" aria-label="The edit icon" %}. Then, in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. +![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png) -1. Antes de habilitar o SSO do SAML para sua empresa, a fim de garantir que as informações inseridas estejam corretas, clique em **Testar configuração do SAML**. ![Botão usado para testar a configuração do SAML antes da imposição](/assets/images/help/saml/saml_test.png) +1. Before enabling SAML SSO for your enterprise, to ensure that the information you've entered is correct, click **Test SAML configuration**. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png) -1. Clique em **Salvar**. +1. Click **Save**. {% note %} - **Observação:** quando você precisar do SSO do SAML para sua empresa, o usuário de instalação não terá mais acesso à empresa, mas permanecerá conectado ao GitHub. Apenas {% data variables.product.prodname_managed_users %} provisionados pelo seu IdP terão acesso à empresa. + **Note:** When you require SAML SSO for your enterprise, the setup user will no longer have access to the enterprise but will remain signed in to GitHub. Only {% data variables.enterprise.prodname_managed_users %} provisioned by your IdP will have access to the enterprise. {% endnote %} {% data reusables.enterprise-accounts.download-recovery-codes %} -### Habilitando provisionamento +### Enabling provisioning -Depois que você habilitar o SAML SSO, habilite o provisionamento. Para obter mais informações, confira "[Como configurar o provisionamento do SCIM para os usuários gerenciados corporativos](//admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)". +After you enable SAML SSO, enable provisioning. For more information, see "[Configuring SCIM provisioning for enterprise managed users](//admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)." diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md b/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md index bd37d18a42..dddd160ff4 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md @@ -1,7 +1,7 @@ --- -title: Configurando o provisionamento do SCIM para usuários gerenciados pela empresa com Okta +title: Configuring SCIM provisioning for Enterprise Managed Users with Okta shortTitle: Set up provisioning with Okta -intro: Você pode fornecer novos usuários e gerenciar os integrantes da sua empresa e das equipes usando o Okta como seu provedor de identidade. +intro: You can provision new users and manage their membership of your enterprise and teams using Okta as your identity provider. product: '{% data reusables.gated-features.emus %}' versions: ghec: '*' @@ -17,86 +17,81 @@ topics: - Authentication - Enterprise - SSO -ms.openlocfilehash: 11cfbf1b5d5a3e23b3d911375aa8ba6826d48817 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147444932' --- -## Sobre o provisionamento com Okta -Você pode usar {% data variables.product.prodname_emus %} com o Okta como seu provedor de identidade para fornecer novas contas, gerenciar a associação da empresa e gerenciar as associações das equipes para as organizações na sua empresa. Para obter mais informações sobre o provisionamento dos {% data variables.product.prodname_emus %}, confira "[Como configurar o provisionamento do SCIM para usuários gerenciados corporativos](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)". +## About provisioning with Okta -Antes de configurar o provisionamento com o Okta, você deverá configurar o logon único SAML. Para obter mais informações, confira "[Como configurar o logon único do SAML para os Usuários Gerenciados Corporativos](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)". +You can use {% data variables.product.prodname_emus %} with Okta as your identity provider to provision new accounts, manage enterprise membership, and manage team memberships for organizations in your enterprise. For more information about provisioning for {% data variables.product.prodname_emus %}, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)." -Para configurar o provisionamento com o Okta, você deverá definir o nome da sua empresa no aplicativo {% data variables.product.prodname_emu_idp_application %} e inserir o token de acesso pessoal do seu usuário. Em seguida, você poderá começar a provisionar usuários no Okta. +Before you can configure provisioning with Okta, you must configure SAML single-sign on. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)." -## Recursos compatíveis +To configure provisioning with Okta, you must set your enterprise's name in the {% data variables.product.prodname_emu_idp_application %} application and enter your setup user's {% data variables.product.pat_generic %}. You can then start provisioning users in Okta. -{% data variables.product.prodname_emus %} é compatível com muitas funcionalidades no Okta. +## Supported features -| Recurso | Descrição | +{% data variables.product.prodname_emus %} supports many provisioning features in Okta. + +| Feature | Description | | --- | --- | -| Fazer push de novos usuários | Os usuários atribuídos ao aplicativo de {% data variables.product.prodname_emu_idp_application %} no Okta são automaticamente criados na empresa em {% data variables.product.product_name %}. | -| Fazer push da atualização do perfil | As atualizações feitas no perfil do usuário no Okta serão enviadas por push para {% data variables.product.product_name %}. | -| Grupos de Push | Os grupos no Okta atribuídos ao aplicativo de {% data variables.product.prodname_emu_idp_application %} como os Grupos Push são criados automaticamente na empresa em {% data variables.product.product_name %}. | -| Fazer push de desativações de usuário | Cancelar a atribuição do usuário do aplicativo de {% data variables.product.prodname_emu_idp_application %} no Okta irá desabilitar o usuário em {% data variables.product.product_name %}. O usuário não poderá efetuar o login, mas as informações do usuário serão mantidas. | -| Reativar usuários | Os Usuários do Okta cujas contas do Okta são reativadas e atribuídas de volta ao aplicativo de {% data variables.product.prodname_emu_idp_application %} serão habilitados. | +| Push New Users | Users that are assigned to the {% data variables.product.prodname_emu_idp_application %} application in Okta are automatically created in the enterprise on {% data variables.product.product_name %}. | +| Push Profile Update | Updates made to the user's profile in Okta will be pushed to {% data variables.product.product_name %}. | +| Push Groups | Groups in Okta that are assigned to the {% data variables.product.prodname_emu_idp_application %} application as Push Groups are automatically created in the enterprise on {% data variables.product.product_name %}. | +| Push User Deactivation | Unassigning the user from the {% data variables.product.prodname_emu_idp_application %} application in Okta will disable the user on {% data variables.product.product_name %}. The user will not be able to sign in, but the user's information is maintained. | +| Reactivate Users | Users in Okta whose Okta accounts are reactivated and who are assigned back to the {% data variables.product.prodname_emu_idp_application %} application will be enabled. | {% note %} -**Observação:** os {% data variables.product.prodname_emus %} não dão suporte a modificações em nomes de usuário. +**Note:** {% data variables.product.prodname_emus %} does not support modifications to usernames. {% endnote %} -## Configurando o nome da sua empresa +## Setting your enterprise name -Após a criação do seu {% data variables.product.prodname_emu_enterprise %}, você poderá começar a configurar o provisionamento definindo o nome da sua empresa no Okta. +After your {% data variables.enterprise.prodname_emu_enterprise %} has been created, you can begin to configure provisioning by setting your enterprise name in Okta. -1. Acesse o seu aplicativo de{% data variables.product.prodname_emu_idp_application %} no Okta. -1. Clique na guia **Logon**. -1. Para fazer alterações, clique em **Editar**. -1. Em "Configurações Avançadas de Login", na caixa de texto "Nome da empresa", digite o nome da sua empresa. Por exemplo, se você acessar sua empresa em `https://github.com/enterprises/octoinc`, o nome da empresa será "octoinc". -![Captura de tela do campo Nome da Empresa no Okta](/assets/images/help/enterprises/okta-emu-enterprise-name.png) -1. Para salvar o nome da empresa, clique em **Salvar**. +1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta. +1. Click the **Sign On** tab. +1. To make changes, click **Edit**. +1. Under "Advanced Sign-on Settings", in the "Enterprise Name" text box, type your enterprise name. For example, if you access your enterprise at `https://github.com/enterprises/octoinc`, your enterprise name would be "octoinc". +![Screenshot of the Enterprise Name field on Okta](/assets/images/help/enterprises/okta-emu-enterprise-name.png) +1. To save your enterprise name, click **Save**. -## Configurando o provisionamento +## Configuring provisioning -Após definir o nome da sua empresa, você poderá prosseguir para definir as configurações de provisionamento. +After setting your enterprise name, you can proceed to configure provisioning settings. -Para configurar o provisionamento, o usuário de instalação com o nome de usuário **@SHORT-CODE_admin** precisará fornecer um token de acesso pessoal com o escopo **admin:enterprise**. Para obter mais informações sobre como criar um token, confira "[Como criar um token de acesso pessoal](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)". +To configure provisioning, the setup user with the **@SHORT-CODE_admin** username will need to provide a {% data variables.product.pat_v1 %} with the **admin:enterprise** scope. For more information on creating a new token, see "[Creating a {% data variables.product.pat_generic %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)." -1. Acesse o seu aplicativo de{% data variables.product.prodname_emu_idp_application %} no Okta. -1. Clique o **provisionamento** guia. -1. No menu de configurações, clique em **Integração**. -1. Para fazer alterações, clique em **Editar**. -1. Selecione **Habilitar integração de API**. -1. No campo "Token de API", insira o token de acesso pessoal com o escopo **admin:enterprise** pertencente ao usuário de instalação. -![Captura de tela que mostra o campo Token de API no Okta](/assets/images/help/enterprises/okta-emu-token.png) -1. Clique em **Testar Credenciais da API**. Se o teste for bem sucedido, será exibida uma mensagem de verificação na parte superior da tela. -1. Para salvar o token, clique em **Salvar**. -1. No menu de configurações, clique em **No Aplicativo**. -![Captura de tela que mostra o item de menu No Aplicativo no Okta](/assets/images/help/enterprises/okta-emu-to-app-menu.png) -1. À direita de "Provisionamento no Aplicativo", para permitir que as alterações sejam feitas, clique em **Editar**. -1. Selecione **Habilitar** para **Criar Usuários**, **Atualizar Atributos de Usuário** e **Desativar Usuários**. -![Captura de tela que mostra as opções de provisionamento no Okta](/assets/images/help/enterprises/okta-emu-provisioning-to-app.png) -1. Para concluir a configuração do provisionamento, clique em **Salvar**. +1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta. +1. Click the **Provisioning** tab. +1. In the settings menu, click **Integration**. +1. To make changes, click **Edit**. +1. Select **Enable API integration**. +1. In the "API Token" field, enter the {% data variables.product.pat_v1 %} with the **admin:enterprise** scope belonging to the setup user. +![Screenshot showing the API Token field on Okta](/assets/images/help/enterprises/okta-emu-token.png) +1. Click **Test API Credentials**. If the test is successful, a verification message will appear at the top of the screen. +1. To save the token, click **Save**. +1. In the settings menu, click **To App**. +![Screenshot showing the To App menu item on Okta](/assets/images/help/enterprises/okta-emu-to-app-menu.png) +1. To the right of "Provisioning to App", to allow changes to be made, click **Edit**. +1. Select **Enable** for **Create Users**, **Update User Attributes**, and **Deactivate Users**. +![Screenshot showing provisioning options on Okta](/assets/images/help/enterprises/okta-emu-provisioning-to-app.png) +1. To finish configuring provisioning, click **Save**. -## Atribuindo usuários e grupos +## Assigning users and groups -Depois de configurar o SAML SSO e o provisionamento, você poderá fornecer novos usuários no {% data variables.product.prodname_dotcom_the_website %} atribuindo usuários ao aplicativo de {% data variables.product.prodname_emu_idp_application %}. +After you have configured SAML SSO and provisioning, you will be able provision new users on {% data variables.product.prodname_dotcom_the_website %} by assigning users to the {% data variables.product.prodname_emu_idp_application %} application. {% data reusables.scim.emu-scim-rate-limit %} -Você também pode gerenciar automaticamente a associação da organização ao atribuir grupos ao aplicativo e adicioná-los à aba "Grupos de Push" no Okta. Quando o grupo for provisionado com sucesso, ele estará disponível para conectar-se a equipes das organizações da empresa. Para obter mais informações sobre como gerenciar equipes, confira "[Como gerenciar associações à equipe com grupos de provedores de identidade](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)". +You can also automatically manage organization membership by assigning groups to the application and adding them to the "Push Groups" tab in Okta. When the group is provisioned successfully, it will be available to connect to teams in the enterprise's organizations. For more information about managing teams, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)." -Ao atribuir aos usuários, você poderá usar o atributo "Funções" no aplicativo de {% data variables.product.prodname_emu_idp_application %} para definir a função de um usuário na sua empresa em {% data variables.product.product_name %}. Para obter mais informações sobre funções, confira "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)". +When assigning users, you can use the "Roles" attribute in the {% data variables.product.prodname_emu_idp_application %} application to set a user's role in your enterprise on {% data variables.product.product_name %}. For more information on roles, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)." -![Captura de tela que mostra as opções da função para o usuário provisionado do Okta](/assets/images/help/enterprises/okta-emu-user-role.png) +![Screenshot showing the role options for provisioned user on Okta](/assets/images/help/enterprises/okta-emu-user-role.png) -## Desprovisionar usuários e grupos +## Deprovisioning users and groups -Para remover um usuário ou grupo de {% data variables.product.product_name %}, remova o usuário ou o grupo da guia "Atribuições" e da guia "Grupos de push" no Okta. Para usuários, verifique se o usuário foi removido de todos os grupos na guia "Grupos de Push". +To remove a user or group from {% data variables.product.product_name %}, remove the user or group from both the "Assignments" tab and the "Push groups" tab in Okta. For users, make sure the user is removed from all groups in the "Push Groups" tab. diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md b/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md index 38a0c1c1fd..af0d546dab 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md @@ -1,7 +1,7 @@ --- -title: Configurando o provisionamento de SCIM para usuários gerenciados pela empresa +title: Configuring SCIM provisioning for Enterprise Managed Users shortTitle: Provisioning managed users -intro: Você pode configurar seu provedor de identidade para fornecer novos usuários e gerenciar seus integrantes na sua empresa e equipes. +intro: You can configure your identity provider to provision new users and manage their membership in your enterprise and teams. product: '{% data reusables.gated-features.emus %}' redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users @@ -13,58 +13,60 @@ versions: topics: - Accounts - Enterprise -ms.openlocfilehash: 3ce59680c100004496e761d2a93adc9e9cae0a22 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147881494' --- -## Sobre o provisionamento para {% data variables.product.prodname_emus %} -Você deve configurar o provisionamento para {% data variables.product.prodname_emus %} a fim de criar, gerenciar e desativar contas de usuário para os integrantes da sua empresa. Ao configurar o provisionamento para {% data variables.product.prodname_emus %}, os usuários atribuídos ao aplicativo de {% data variables.product.prodname_emu_idp_application %} no seu provedor de identidade serão provisionados como novas contas de usuário em {% data variables.product.prodname_dotcom %} por meio do SCIM e os usuários serão adicionados à sua empresa. +## About provisioning for {% data variables.product.prodname_emus %} -Quando você atualiza as informações associadas à identidade de um usuário no IdP, seu IdP atualiza a conta do usuário em GitHub.com. Quando você cancela a atribuição do usuário do aplicativo ao {% data variables.product.prodname_emu_idp_application %} ou desativa a conta de um usuário no IdP, o IdP se comunica com o {% data variables.product.prodname_dotcom %} para invalidar as sessões e desabilitar a conta do membro. As informações da conta desativada serão mantidas e seu nome de usuário será alterado para hash do seu nome de usuário original com o código curto anexado. Se você reatribuir um usuário para o aplicativo {% data variables.product.prodname_emu_idp_application %} ou reativar sua conta no seu IdP, a conta de {% data variables.product.prodname_managed_user %} em {% data variables.product.prodname_dotcom %} será reativada e o nome de usuário restaurado. +You must configure provisioning for {% data variables.product.prodname_emus %} to create, manage, and deactivate user accounts for your enterprise members. When you configure provisioning for {% data variables.product.prodname_emus %}, users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your identity provider are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} via SCIM, and the users are added to your enterprise. -Os grupos no seu IdP podem ser usados para gerenciar a participação de equipe nas organizações de sua empresa, permitindo que você configure o acesso e as permissões do repositório por meio do seu IdP. Para obter mais informações, confira "[Como gerenciar associações à equipe com grupos de provedores de identidade](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)". +When you update information associated with a user's identity on your IdP, your IdP will update the user's account on GitHub.com. When you unassign the user from the {% data variables.product.prodname_emu_idp_application %} application or deactivate a user's account on your IdP, your IdP will communicate with {% data variables.product.prodname_dotcom %} to invalidate any sessions and disable the member's account. The disabled account's information is maintained and their username is changed to a hash of their original username with the short code appended. If you reassign a user to the {% data variables.product.prodname_emu_idp_application %} application or reactivate their account on your IdP, the {% data variables.enterprise.prodname_managed_user %} account on {% data variables.product.prodname_dotcom %} will be reactivated and username restored. -## Pré-requisitos +Groups in your IdP can be used to manage team membership within your enterprise's organizations, allowing you to configure repository access and permissions through your IdP. For more information, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)." -Para configurar o provisionamento de {% data variables.product.prodname_emus %}, você precisa configurar o logon único do SAML{% ifversion oidc-for-emu %} ou do OIDC{% endif %}. {% ifversion oidc-for-emu %} +## Prerequisites -- Para obter mais informações sobre como configurar o OIDC, confira "[Como configurar o OIDC para usuários empresariais gerenciados](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)" -- {% endif %}Para obter mais informações, confira "[Como configurar o logon único do SAML para usuários empresariais gerenciados](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)". +Before you can configure provisioning for {% data variables.product.prodname_emus %}, you must configure SAML{% ifversion oidc-for-emu %} or OIDC{% endif %} single-sign on. {% ifversion oidc-for-emu %} -## Criando um token de acesso pessoal +- For more information on configuring OIDC, see "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)" +- {% endif %}For information on configuring SAML, see "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)." -Para configurar o provisionamento para o {% data variables.product.prodname_emu_enterprise %}, você precisa ter um token de acesso pessoal com o escopo **admin:enterprise** que pertença ao usuário da instalação. +## Creating a {% data variables.product.pat_generic %} + +To configure provisioning for your {% data variables.enterprise.prodname_emu_enterprise %}, you need a {% data variables.product.pat_v1 %} with the **admin:enterprise** scope that belongs to the setup user. {% warning %} -**Aviso:** se o token vencer ou um usuário provisionado criar o token, o provisionamento do SCIM poderá parar de funcionar inesperadamente. Certifique-se de criar o token enquanto estiver conectado como usuário de configuração e que o vencimento do token esteja definido como "Sem vencimento". +**Warning:** If the token expires or a provisioned user creates the token, SCIM provisioning may unexpectedly stop working. Make sure that you create the token while signed in as the setup user and that the token expiration is set to "No expiration". {% endwarning %} -1. Entre no {% data variables.product.prodname_dotcom_the_website %} como o usuário de instalação para sua nova empresa com o nome de usuário **@SHORT-CODE_admin**. -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.personal_access_tokens %} {% data reusables.user-settings.generate_new_token %} -1. Em **Observação**, dê ao token um nome descritivo. - ![Captura de tela que mostra o nome do token](/assets/images/help/enterprises/emu-pat-name.png) -1. Selecione o menu suspenso **Validade** e clique em **Sem data de validade**. - ![Captura de tela que mostra a validade do token definida como sem validade](/assets/images/help/enterprises/emu-pat-no-expiration.png) -1. Selecione o escopo **admin:enterprise**. - ![Captura de tela que mostra o escopo admin:enterprise](/assets/images/help/enterprises/enterprise-pat-scope.png) -1. Clique em **Gerar token**. - ![Botão Gerar token](/assets/images/help/settings/generate_token.png) -1. Para copiar o token para a área de transferência, clique no {% octicon "paste" aria-label="The copy icon" %}. - ![Token recém-criado](/assets/images/help/settings/personal_access_tokens.png) -2. Para salvar o token para usar mais tarde, armazene o novo token de forma segura em um gerenciador de senhas. +1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@SHORT-CODE_admin**. +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.personal_access_tokens %} +{% data reusables.user-settings.generate_new_token %} +1. Under **Note**, give your token a descriptive name. + ![Screenshot showing the token's name](/assets/images/help/enterprises/emu-pat-name.png) +1. Select the **Expiration** drop-down menu, then click **No expiration**. + ![Screenshot showing token expiration set to no expiration](/assets/images/help/enterprises/emu-pat-no-expiration.png) +1. Select the **admin:enterprise** scope. + ![Screenshot showing the admin:enterprise scope](/assets/images/help/enterprises/enterprise-pat-scope.png) +1. Click **Generate token**. + ![Generate token button](/assets/images/help/settings/generate_token.png) +1. To copy the token to your clipboard, click the {% octicon "paste" aria-label="The copy icon" %}. + ![Newly created token](/assets/images/help/settings/personal_access_tokens.png) +2. To save the token for use later, store the new token securely in a password manager. -## Configurando provisionamento para {% data variables.product.prodname_emus %} +## Configuring provisioning for {% data variables.product.prodname_emus %} -Depois de criar seu token de acesso pessoal e armazená-lo com segurança, você pode configurar o provisionamento no seu provedor de identidade. +After creating your {% data variables.product.pat_generic %} and storing it securely, you can configure provisioning on your identity provider. {% data reusables.scim.emu-scim-rate-limit %} -Para configurar o provisionamento, clique no link apropriado na tabela abaixo. +To configure provisioning, follow the appropriate link from the table below. -| Provedor de identidade | Método SSO | Mais informações | |---|---|---|{% ifversion oidc-for-emu %} | Azure AD | OIDC | [Tutorial: como configurar o GitHub Enterprise Managed User (OIDC) para provisionamento automático de usuários](https://docs.microsoft.com/azure/active-directory/saas-apps/github-enterprise-managed-user-oidc-provisioning-tutorial) na documentação do Azure AD |{% endif %} | Azure AD | SAML | [Tutorial: como configurar o GitHub Enterprise Managed User para provisionamento automático de usuários](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-provisioning-tutorial) na documentação do Azure AD | | Okta | SAML | [Como configurar o provisionamento do SCIM para usuários empresariais gerenciados com o Okta](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users-with-okta) | +| Identity provider | SSO method | More information | +|---|---|---|{% ifversion oidc-for-emu %} +| Azure AD | OIDC | [Tutorial: Configure GitHub Enterprise Managed User (OIDC) for automatic user provisioning](https://docs.microsoft.com/azure/active-directory/saas-apps/github-enterprise-managed-user-oidc-provisioning-tutorial) in the Azure AD documentation |{% endif %} +| Azure AD | SAML | [Tutorial: Configure GitHub Enterprise Managed User for automatic user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-provisioning-tutorial) in the Azure AD documentation | +| Okta | SAML | [Configuring SCIM provisioning for Enterprise Managed Users with Okta](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users-with-okta) | diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md b/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md index 0e6c15bd79..e7306b64c7 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md @@ -1,7 +1,7 @@ --- -title: Gerenciando associações de equipes com grupos de provedores de identidade +title: Managing team memberships with identity provider groups shortTitle: Manage teams with your IdP -intro: 'Você pode gerenciar a associação à equipe em {% data variables.product.product_name %} por meio do seu provedor de identidade (IdP) conectando os grupos do IdP ao seu {% data variables.product.prodname_emu_enterprise %}.' +intro: 'You can manage team membership on {% data variables.product.product_name %} through your identity provider (IdP) by connecting IdP groups with your {% data variables.enterprise.prodname_emu_enterprise %}.' product: '{% data reusables.gated-features.emus %}' redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups @@ -16,64 +16,67 @@ topics: - Enterprise - SSO - Teams -ms.openlocfilehash: 2ac4eed05fdac627f0846c11f3b9a03be3c693a0 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145955512' --- -## Sobre o gerenciamento da equipe com {% data variables.product.prodname_emus %} -Com {% data variables.product.prodname_emus %}, você pode gerenciar a participação em equipe dentro da sua empresa por meio do seu IdP. Quando conectar uma equipe de uma das organizações da sua empresa a um grupo do IdP as alterações nos integrantes do grupo do IdP serão refletidas na sua empresa automaticamente, reduzindo a necessidade de atualizações manuais e scripts personalizados. +## About team management with {% data variables.product.prodname_emus %} -Quando uma alteração em um grupo do IdP ou uma nova conexão de equipe faz com que {% data variables.product.prodname_managed_user %} entre em uma equipe em uma organização da qual já não faz parte, o {% data variables.product.prodname_managed_user %} será adicionado à organização automaticamente. Os proprietários da organização também podem gerenciar a associação da organização manualmente. Ao desconectar um grupo de uma equipe, usuários que se tornaram integrantes da organização por da associação da equipe são removidos da organização se uma associação não lhes for atribuída na organização por outros meios. +With {% data variables.product.prodname_emus %}, you can manage team membership within your enterprise through your IdP. When you connect a team in one of your enterprise's organizations to an IdP group, changes to membership from the IdP group are reflected in your enterprise automatically, reducing the need for manual updates and custom scripts. -É possível conectar uma equipe da sua empresa a um grupo de IdP. Você pode atribuir o mesmo grupo do IdP a várias equipes na sua empresa. +When a change to an IdP group or a new team connection results in a {% data variables.enterprise.prodname_managed_user %} joining a team in an organization they were not already a member of, the {% data variables.enterprise.prodname_managed_user %} will automatically be added to the organization. Organization owners can also manage organization membership manually. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization if they are not assigned membership in the organization by any other means. -Se você estiver conectando uma equipe existente a um grupo de IdP, primeiro você deverá remover todos os integrantes que foram adicionados manualmente. Depois de conectar uma equipe da sua empresa a um grupo do IdP, o administrador do IdP deverá realizar as alterações na associação da equipe por meio do provedor de identidade. Você não pode gerenciar a associação da equipe em {% data variables.product.prodname_dotcom_the_website %}. +You can connect a team in your enterprise to one IdP group. You can assign the same IdP group to multiple teams in your enterprise. -Quando o integrante do grupo mudar no seu IdP, este enviará uma solicitação de SCIM com alterações para {% data variables.product.prodname_dotcom_the_website %} de acordo com o cronograma determinado pelo seu IdP. Portanto, é possível que a alteração não seja imediata. Qualquer solicitação que altere a equipe de equipe ou associação da organização será registrada no log de auditoria como alterações feitas pela conta usada para configurar provisionamento do usuário. +If you are connecting an existing team to an IdP group, you must first remove any members that were added manually. After you connect a team in your enterprise to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.prodname_dotcom_the_website %}. -As quipes conectadas a grupos de IdP não podem ser equipes principais de outras equipes nem uma equipe secundária de outra equipe. Se a equipe que você deseja conectar a um grupo de IdP for uma equipe principal ou secundária recmendamos criar uma nova equipe ou remover a relação aninhada que faças da sua equipe uma equipe principal. +When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.prodname_dotcom_the_website %} according to the schedule determined by your IdP, so change may not be immediate. Any requests that change team or organization membership will register in the audit log as changes made by the account used to configure user provisioning. -Para gerenciar o acesso ao repositório para qualquer equipe do seu negócio, incluindo equipes conectadas a um grupo de IdP, você deverá fazer alterações em {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, confira "[Como gerenciar o acesso da equipe a um repositório da organização](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)". +Teams connected to IdP groups cannot be parents of other teams nor a child of another team. If the team you want to connect to an IdP group is a parent or child team, we recommend creating a new team or removing the nested relationships that make your team a parent team. -## Criando uma nova equipe conectada a um grupo de IdP +To manage repository access for any team in your enterprise, including teams connected to an IdP group, you must make changes on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)". -Qualquer integrante de uma organização pode criar uma nova equipe e conectar a equipe a um grupo de IdP. +## Creating a new team connected to an IdP group -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.new_team %} {% data reusables.organizations.team_name %} {% data reusables.organizations.team_description %} -1. Para conectar uma equipe, selecione o menu suspenso "Grupos de Fornecedores de Identidade" e clique na equipe que você deseja se conectar. - ![Menu suspenso usado para escolher grupos de provedores de identidade](/assets/images/help/teams/choose-an-idp-group.png) {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create_team %} +Any member of an organization can create a new team and connect the team to an IdP group. -## Gerenciando a conexão entre uma equipe existente e um grupo de IdP +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.new_team %} +{% data reusables.organizations.team_name %} +{% data reusables.organizations.team_description %} +1. To connect a team, select the "Identity Provider Groups" drop-down menu and click the team you want to connect. + ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png) +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create_team %} -Os proprietários da organização e mantenedores de equipe podem gerenciar a conexão existente entre um grupo de IdP e uma equipe. +## Managing the connection between an existing team and an IdP group + +Organization owners and team maintainers can manage the existing connection between an IdP group and a team. {% note %} -**Observação**: para conectar uma equipe existente no {% data variables.product.prodname_dotcom_the_website %} a um grupo de IdP pela primeira vez, todos os membros da equipe no {% data variables.product.prodname_dotcom_the_website %} devem primeiro ser removidos. Para obter mais informações, confira "[Como remover membros da organização de uma equipe](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)". +**Note**: Before you connect an existing team on {% data variables.product.prodname_dotcom_the_website %} to an IdP group for the first time, all members of the team on {% data variables.product.prodname_dotcom_the_website %} must first be removed. For more information, see "[Removing organization members from a team](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)." {% endnote %} {% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %} -1. Opcionalmente, em "Grupo de Provedores de Identidade", à direita do grupo do IdP que deseja desconectar, clique em {% octicon "x" aria-label="X symbol" %}. - ![Cancelar a seleção de um grupo de IdP conectado da equipe do GitHub](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png) -1. Para conectar um grupo de IdP, em "Grupo de Fornecedores de Identidade", selecione o menu suspenso e clique em um grupo de provedores de identidade da lista. - ![Menu suspenso usado para escolher o grupo de provedores de identidade](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png) -1. Clique em **Salvar alterações**. +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +1. Optionally, under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. + ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png) +1. To connect an IdP group, under "Identity Provider Group", select the drop-down menu, and click an identity provider group from the list. + ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png) +1. Click **Save changes**. -## Visualizando grupos de IdP, associações de grupo e equipes conectadas +## Viewing IdP groups, group membership, and connected teams -Você pode revisar uma lista de grupos de IdP, ver todas as equipes conectadas a um grupo de IdP, e ver a associação de cada grupo IdP no {% data variables.product.product_name %}. Você deve editar a associação de um grupo no seu IdP. +You can review a list of IdP groups, see any teams connected to an IdP group, and see the membership of each IdP group on {% data variables.product.product_name %}. You must edit the membership for a group on your IdP. {% data reusables.enterprise-accounts.access-enterprise %} -1. Para revisar uma lista de grupos de IdP, na barra lateral esquerda, clique em {% octicon "key" aria-label="The key icon" %} **Provedor de Identidade**. - ![Captura de tela mostrando a guia "Provedor de identidade" na barra lateral da empresa](/assets/images/help/enterprises/enterprise-account-identity-provider-tab.png) -2. Para ver os integrantes e equipes conectados a um grupo do IdP, clique no nome do grupo. - ![Captura de tela que mostra a lista de grupos de IdP; o nome do grupo está destacado](/assets/images/help/enterprises/select-idp-group.png) -4. Para ver as equipes conectadas ao grupo de IdP, clique em **Equipes**. - ![Captura de tela mostrando o botão "Equipes"](/assets/images/help/enterprises/idp-groups-team-switcher.png) +1. To review a list of IdP groups, in the left sidebar, click {% octicon "key" aria-label="The key icon" %} **Identity provider**. + ![Screenshot showing "Identity provider" tab in enterprise sidebar](/assets/images/help/enterprises/enterprise-account-identity-provider-tab.png) +2. To see the members and teams connected to an IdP group, click the group's name. + ![Screenshot showing list of IdP groups, the group name is highlighted](/assets/images/help/enterprises/select-idp-group.png) +4. To view the teams connected to the IdP group, click **Teams**. + ![Screenshot showing the "Teams" button](/assets/images/help/enterprises/idp-groups-team-switcher.png) diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md b/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md index f6e7cb1071..1d10031b84 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md @@ -1,7 +1,7 @@ --- title: Migrating from SAML to OIDC shortTitle: Migrating from SAML to OIDC -intro: 'If you''re using SAML to authenticate members in your {% data variables.product.prodname_emu_enterprise %}, you can migrate to OpenID Connect (OIDC) and benefit from support for your IdP''s Conditional Access Policy.' +intro: 'If you''re using SAML to authenticate members in your {% data variables.enterprise.prodname_emu_enterprise %}, you can migrate to OpenID Connect (OIDC) and benefit from support for your IdP''s Conditional Access Policy.' product: '{% data reusables.gated-features.emus %}' versions: feature: oidc-for-emu @@ -14,11 +14,11 @@ topics: {% data reusables.enterprise-accounts.oidc-beta-notice %} -## About migrating your {% data variables.product.prodname_emu_enterprise %} from SAML to OIDC +## About migrating your {% data variables.enterprise.prodname_emu_enterprise %} from SAML to OIDC -If your {% data variables.product.prodname_emu_enterprise %} uses SAML SSO to authenticate with Azure Active Directory (Azure AD), you can migrate to OIDC. {% data reusables.enterprise-accounts.emu-cap-validates %} +If your {% data variables.enterprise.prodname_emu_enterprise %} uses SAML SSO to authenticate with Azure Active Directory (Azure AD), you can migrate to OIDC. {% data reusables.enterprise-accounts.emu-cap-validates %} -When you migrate from SAML to OIDC, {% data variables.product.prodname_managed_users %} and groups that were previously provisioned for SAML but are not provisioned by the {% data variables.product.prodname_emu_idp_oidc_application %} application will have "(SAML)" appended to their display names. +When you migrate from SAML to OIDC, {% data variables.enterprise.prodname_managed_users %} and groups that were previously provisioned for SAML but are not provisioned by the {% data variables.product.prodname_emu_idp_oidc_application %} application will have "(SAML)" appended to their display names. If you're new to {% data variables.product.prodname_emus %} and haven't yet configured authentication for your enterprise, you do not need to migrate and can set up OIDC single sign-on immediately. For more information, see "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)." @@ -47,11 +47,11 @@ If you're new to {% data variables.product.prodname_emus %} and haven't yet conf ![Screenshot showing the "Configure with Azure" button](/assets/images/help/enterprises/saml-to-oidc-button.png) 1. Read both warnings and click to continue. {% data reusables.enterprise-accounts.emu-azure-admin-consent %} -1. In a new tab or window, while signed in as the setup user on {% data variables.product.prodname_dotcom_the_website %}, create a personal access token with the **admin:enterprise** scope and **no expiration** and copy it to your clipboard. For more information about creating a new token, see "[Creating a personal access token](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)." +1. In a new tab or window, while signed in as the setup user on {% data variables.product.prodname_dotcom_the_website %}, create a {% data variables.product.pat_v1 %} with the **admin:enterprise** scope and **no expiration** and copy it to your clipboard. For more information about creating a new token, see "[Creating a {% data variables.product.pat_generic %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)." 1. In the settings for the {% data variables.product.prodname_emu_idp_oidc_application %} application in Azure Portal, under "Tenant URL", type `https://api.github.com/scim/v2/enterprises/YOUR_ENTERPRISE`, replacing YOUR_ENTERPRISE with the name of your enterprise account. For example, if your enterprise account's URL is `https://github.com/enterprises/octo-corp`, the name of the enterprise account is `octo-corp`. -1. Under "Secret token", paste the personal access token with the **admin:enterprise** scope that you created earlier. +1. Under "Secret token", paste the {% data variables.product.pat_v1 %} with the **admin:enterprise** scope that you created earlier. 1. To test the configuration, click **Test Connection**. 1. To save your changes, at the top of the form, click **Save**. 1. In Azure Portal, copy the users and groups from the old {% data variables.product.prodname_emu_idp_application %} application to the new {% data variables.product.prodname_emu_idp_oidc_application %} application. diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md b/translations/pt-BR/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md index 1fb68f38a2..67af5b8586 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md @@ -1,16 +1,10 @@ --- -title: Usar o LDAP para IAM empresarial +title: Using LDAP for enterprise IAM shortTitle: LDAP for enterprise IAM -intro: 'Você pode gerenciar contas centralmente e acessar {% data variables.product.product_location %} ao integrar-se ao diretório LDAP existente.' +intro: 'You can centrally manage accounts and access to {% data variables.location.product_location %} by integrating with your existing LDAP directory.' versions: ghes: '*' children: - /using-ldap -ms.openlocfilehash: 40145a8d9c4905731eef2d710171ffae7872ecea -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717802' --- diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md b/translations/pt-BR/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md index fd950eb43b..1054fee109 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md @@ -1,5 +1,5 @@ --- -title: Usando o LDAP +title: Using LDAP redirect_from: - /enterprise/admin/articles/configuring-ldap-authentication - /enterprise/admin/articles/about-ldap-authentication @@ -11,7 +11,7 @@ redirect_from: - /admin/authentication/using-ldap - /enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap - /admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap -intro: 'Se você usa o protocolo LDAP para centralizar o acesso entre aplicativos, integre o {% data variables.product.product_name %} configurando a autenticação LDAP para sua instância.' +intro: 'If you use Lightweight Directory Access Protocol (LDAP) to centralize access across applications, you can integrate {% data variables.product.product_name %} by configuring LDAP authentication for your instance.' versions: ghes: '*' type: how_to @@ -20,191 +20,194 @@ topics: - Authentication - Enterprise - Identity -ms.openlocfilehash: bed91adf09819869204f40b1a9e09c63925904ff -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147062991' --- -## Sobre a autenticação do LDAP no {% data variables.product.product_name %} -O LDAP é um protocolo de aplicativo popular para acesso e manutenção dos serviços de informações de diretório, além de ser um dos protocolos mais comuns para integração de software de terceiros a diretórios de usuários em grandes empresas. Para obter mais informações, confira "[Lightweight Directory Access Protocol](https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol)" na Wikipédia. +## About LDAP authentication for {% data variables.product.product_name %} -Se você usar um diretório do LDAP para autenticação centralizada, poderá configurar a autenticação do LDAP para as pessoas que usam o {% data variables.product.product_location %}. +LDAP is a popular application protocol for access and maintenance of directory information services, and is one of the most common protocols for integration of third-party software with large company user directories. For more information, see "[Lightweight Directory Access Protocol](https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol)" on Wikipedia. + +If you use an LDAP directory for centralized authentication, you can configure LDAP authentication for the people who use {% data variables.location.product_location %}. {% data reusables.enterprise_user_management.built-in-authentication %} -## Serviços LDAP compatíveis +## Supported LDAP services -O {% data variables.product.prodname_ghe_server %} se integra aos seguintes serviços LDAP: +{% data variables.product.prodname_ghe_server %} integrates with these LDAP services: * Active Directory -* FreeIPA; +* FreeIPA * Oracle Directory Server Enterprise Edition * OpenLDAP -* Abrir Diretório -* 389-ds. +* Open Directory +* 389-ds -## Considerações de nome de usuário no LDAP +## Username considerations with LDAP -{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} Para obter mais informações, veja "[Considerações de nome de usuário para autenticação externa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)". +{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)." -## Como configurar o LDAP com o {% data variables.product.product_location %} +## Configuring LDAP with {% data variables.location.product_location %} -Depois que você configurar o LDAP, os usuários poderão acessar a instância com as credenciais LDAP. Quando os usuários acessarem pela primeira vez, seus nomes de perfil, endereços de e-mail e chaves SSH serão definidos com os atributos LDAP do diretório. +After you configure LDAP, users will be able to sign into your instance with their LDAP credentials. When users sign in for the first time, their profile names, email addresses, and SSH keys will be set with the LDAP attributes from your directory. -Quando você configurar o acesso LDAP dos usuários pelo {% data variables.enterprise.management_console %}, suas licenças de usuário não serão usadas até que o primeiro usuário faça login na sua instância. No entanto, se você criar uma conta manualmente usando as configurações de administrador do site, a licença do usuário é imediatamente contabilizada. +When you configure LDAP access for users via the {% data variables.enterprise.management_console %}, your user licenses aren't used until the first time a user signs in to your instance. However, if you create an account manually using site admin settings, the user license is immediately accounted for. {% warning %} -**Aviso:** antes de configurar o LDAP no {% data variables.product.product_location %}, verifique se o serviço LDAP dá suporte a resultados paginados. +**Warning:** Before configuring LDAP on {% data variables.location.product_location %}, make sure that your LDAP service supports paged results. {% endwarning %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.authentication %} -3. Em "Autenticação", selecione **LDAP**. -![Seleção do LDAP](/assets/images/enterprise/management-console/ldap-select.png) -4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Selecionar caixa de autenticação integrada](/assets/images/enterprise/management-console/ldap-built-in-authentication.png) -5. Defina as configurações. +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.authentication %} +3. Under "Authentication", select **LDAP**. +![LDAP select](/assets/images/enterprise/management-console/ldap-select.png) +4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Select LDAP built-in authentication checkbox](/assets/images/enterprise/management-console/ldap-built-in-authentication.png) +5. Add your configuration settings. -## Atributos LDAP -Use estes atributos para concluir a configuração do LDAP no {% data variables.product.product_location %}. +## LDAP attributes +Use these attributes to finish configuring LDAP for {% data variables.location.product_location %}. -| Nome do atributo | Tipo | Descrição | +| Attribute name | Type | Description | |--------------------------|----------|-------------| -| `Host` | Obrigatório | O host do LDAP, por exemplo, `ldap.example.com` ou `10.0.0.30`. Se o nome do host só está disponível na rede interna, talvez seja necessário configurar o DNS do {% data variables.product.product_location %} primeiro para que ele possa resolver o nome do host usando os servidores de nomes internos. | -| `Port` | Obrigatório | Porta em que os serviços de host LDAP estão escutando. Por exemplo: 389 e 636 (para LDAPS). | -| `Encryption` | Obrigatório | Método de criptografia usado para proteger as comunicações com o servidor LDAP. Por exemplo, básico (sem criptografia), SSL/LDAPS (criptografia desde o início) e StartTLS (atualizar para comunicação com criptografia no momento da conexão). | -| `Domain search user` | Opcional | O usuário do LDAP que procura outros usuários que efetuam o login para permitir a autenticação. Em geral, é uma conta de serviço criada especificamente para integrações de terceiros. Use um nome totalmente qualificado, como `cn=Administrator,cn=Users,dc=Example,dc=com`. Com o Active Directory, use também a sintaxe `[DOMAIN]\[USERNAME]` (por exemplo, `WINDOWS\Administrator`) para o usuário de pesquisa de domínio com o Active Directory. | -| `Domain search password` | Opcional | Senha do usuário de pesquisa de domínio. | -| `Administrators group` | Opcional | Ao fazerem login no seu appliance, os usuários deste grupo são promovidos a administradores do site. Se você não configurar um grupo de administradores LDAP, a primeira conta de usuário LDAP que acessar seu appliance será automaticamente promovida a administrador do site. | -| `Domain base` | Obrigatório | O DN (`Distinguished Name`) totalmente qualificado de uma subárvore do LDAP na qual você deseja pesquisar usuários e grupos. Você pode adicionar quantos quiser, mas cada grupo deve ser definido na mesma base de domínio que os usuários pertencentes a ele. Se você especificar grupos de usuários restritos, somente os usuários pertencentes a esses grupos estarão no escopo. É recomendável especificar o nível superior da sua árvore de diretórios LDAP como base de domínio e usar grupos de usuários restritos para controlar o acesso. | -| `Restricted user groups` | Opcional | Se especificados, somente os usuários desses grupos poderão efetuar login. Você só precisa especificar os nomes comuns (CNs, Common Names) dos grupos e adicionar quantos grupos quiser. Se nenhum grupo for especificado, *todos* os usuários no escopo da base de domínio especificada poderão entrar na sua instância do {% data variables.product.prodname_ghe_server %}. | -| `User ID` | Obrigatório | Atributo LDAP que identifica o usuário LDAP que tenta fazer a autenticação. Quando houver mapeamento estabelecido, os usuários poderão alterar seus nomes de usuário no {% data variables.product.prodname_ghe_server %}. Esse campo deve ser `sAMAccountName` para a maioria das instalações do Active Directory, mas pode ser `uid` para outras soluções de LDAP, como o OpenLDAP. O valor padrão é `uid`. | -| `Profile name` | Opcional | Nome exibido na págin de perfil do usuário no {% data variables.product.prodname_ghe_server %}. Se a Sincronização LDAP estiver habilitada, os usuários poderão alterar seus nomes de perfil. | -| `Emails` | Opcional | Endereço de e-mail para a conta de usuário no {% data variables.product.prodname_ghe_server %}. | -| `SSH keys` | Opcional | Chaves SSH públicas vinculadas à conta de um usuário no {% data variables.product.prodname_ghe_server %}. As chaves devem estar no formato OpenSSH. | -| `GPG keys` | Opcional | Chaves GPG vinculadas à conta de um usuário no {% data variables.product.prodname_ghe_server %}. | -| `Disable LDAP authentication for Git operations` | Opcional |Se selecionado, [desativa](#disabling-password-authentication-for-git-operations) a capacidade dos usuários de usar senhas do LDAP para autenticar operações do Git. | -| `Enable LDAP certificate verification` | Opcional |Se selecionado, [ativa](#enabling-ldap-certificate-verification) a verificação de certificado LDAP. | -| `Synchronization` | Opcional |Se selecionado, [ativa](#enabling-ldap-sync) a Sincronização LDAP. | +| `Host` | Required | The LDAP host, e.g. `ldap.example.com` or `10.0.0.30`. If the hostname is only available from your internal network, you may need to configure {% data variables.location.product_location %}'s DNS first so it can resolve the hostname using your internal nameservers. | +| `Port` | Required | The port the host's LDAP services are listening on. Examples include: 389 and 636 (for LDAPS). | +| `Encryption` | Required | The encryption method used to secure communications to the LDAP server. Examples include plain (no encryption), SSL/LDAPS (encrypted from the start), and StartTLS (upgrade to encrypted communication once connected). | +| `Domain search user` | Optional | The LDAP user that looks up other users that sign in, to allow authentication. This is typically a service account created specifically for third-party integrations. Use a fully qualified name, such as `cn=Administrator,cn=Users,dc=Example,dc=com`. With Active Directory, you can also use the `[DOMAIN]\[USERNAME]` syntax (e.g. `WINDOWS\Administrator`) for the domain search user with Active Directory. | +| `Domain search password` | Optional | The password for the domain search user. | +| `Administrators group` | Optional | Users in this group are promoted to site administrators when signing into your appliance. If you don't configure an LDAP Administrators group, the first LDAP user account that signs into your appliance will be automatically promoted to a site administrator. | +| `Domain base` | Required | The fully qualified `Distinguished Name` (DN) of an LDAP subtree you want to search for users and groups. You can add as many as you like; however, each group must be defined in the same domain base as the users that belong to it. If you specify restricted user groups, only users that belong to those groups will be in scope. We recommend that you specify the top level of your LDAP directory tree as your domain base and use restricted user groups to control access. | +| `Restricted user groups` | Optional | If specified, only users in these groups will be allowed to log in. You only need to specify the common names (CNs) of the groups, and you can add as many groups as you like. If no groups are specified, *all* users within the scope of the specified domain base will be able to sign in to your {% data variables.product.prodname_ghe_server %} instance. | +| `User ID` | Required | The LDAP attribute that identifies the LDAP user who attempts authentication. Once a mapping is established, users may change their {% data variables.product.prodname_ghe_server %} usernames. This field should be `sAMAccountName` for most Active Directory installations, but it may be `uid` for other LDAP solutions, such as OpenLDAP. The default value is `uid`. | +| `Profile name` | Optional | The name that will appear on the user's {% data variables.product.prodname_ghe_server %} profile page. Unless LDAP Sync is enabled, users may change their profile names. | +| `Emails` | Optional | The email addresses for a user's {% data variables.product.prodname_ghe_server %} account. | +| `SSH keys` | Optional | The public SSH keys attached to a user's {% data variables.product.prodname_ghe_server %} account. The keys must be in OpenSSH format. | +| `GPG keys` | Optional | The GPG keys attached to a user's {% data variables.product.prodname_ghe_server %} account. | +| `Disable LDAP authentication for Git operations` | Optional |If selected, [turns off](#disabling-password-authentication-for-git-operations) users' ability to use LDAP passwords to authenticate Git operations. | +| `Enable LDAP certificate verification` | Optional |If selected, [turns on](#enabling-ldap-certificate-verification) LDAP certificate verification. | +| `Synchronization` | Optional |If selected, [turns on](#enabling-ldap-sync) LDAP Sync. | -### Desabilitar autenticação de senha nas operações no Git +### Disabling password authentication for Git operations -Selecione **Desabilitar autenticação de nome de usuário e senha para operações do Git** nas configurações do LDAP para impor o uso de tokens de acesso pessoal ou chaves SSH para acesso ao Git, o que pode ajudar a impedir que o seu servidor fique sobrecarregado por solicitações de autenticação LDAP. Essa configuração é recomendável porque servidores LDAP com resposta lenta, especialmente combinados a um grande número de solicitações devido à sondagem, são uma causa comum de interrupções e problemas de desempenho. +Select **Disable username and password authentication for Git operations** in your LDAP settings to enforce use of {% data variables.product.pat_generic %}s or SSH keys for Git access, which can help prevent your server from being overloaded by LDAP authentication requests. We recommend this setting because a slow-responding LDAP server, especially combined with a large number of requests due to polling, is a frequent source of performance issues and outages. -![Desabilitar autenticação de senha LDAP na caixa de seleção do Git](/assets/images/enterprise/management-console/ldap-disable-password-auth-for-git.png) +![Disable LDAP password auth for Git check box](/assets/images/enterprise/management-console/ldap-disable-password-auth-for-git.png) -Quando essa opção for selecionada, se um usuário tentar usar uma senha para operações Git por meio da linha de comando, ele receberá a mensagem de erro `Password authentication is not allowed for Git operations. You must use a personal access token.` +When this option is selected, if a user tries to use a password for Git operations via the command line, they will receive an error message that says, `Password authentication is not allowed for Git operations. You must use a {% data variables.product.pat_generic %}.` -### Habilitar verificação certificada LDAP +### Enabling LDAP certificate verification -Selecione **Habilitar a verificação de certificado LDAP** nas configurações do LDAP para validar o certificado do servidor LDAP usado com o TLS. +Select **Enable LDAP certificate verification** in your LDAP settings to validate the LDAP server certificate you use with TLS. -![Caixa de seleção de verificação certificada LDAP](/assets/images/enterprise/management-console/ldap-enable-certificate-verification.png) +![LDAP certificate verification box](/assets/images/enterprise/management-console/ldap-enable-certificate-verification.png) -Quando esta opção estiver selecionada, o certificado será validado para garantir o seguinte: -- Se o certificado contiver ao menos um nome alternativo da entidade (SAN, Subject Alternative Name), um dos SANs deve corresponder ao nome do host LDAP. Do contrário, o nome comum (CN) corresponderá ao nome de host LDAP. -- O certificado não expirou. -- O certificado deve estar assinado por uma autoridade de certificação (CA, Certificate Authority) confiável. +When this option is selected, the certificate is validated to make sure: +- If the certificate contains at least one Subject Alternative Name (SAN), one of the SANs matches the LDAP hostname. Otherwise, the Common Name (CN) matches the LDAP hostname. +- The certificate is not expired. +- The certificate is signed by a trusted certificate authority (CA). -### Habilitar a Sincronização LDAP +### Enabling LDAP Sync {% note %} -**Observação:** as equipes que usam a Sincronização LDAP estão limitadas a, no máximo, 1.499 membros. +**Note:** Teams using LDAP Sync are limited to a maximum 1499 members. {% endnote %} -A Sincronização LDAP permite sincronizar os usuários do {% data variables.product.prodname_ghe_server %} e a associação da equipe nos seus grupos LDAP estabelecidos. Assim, é possível estabelecer o controle de acesso baseado em função para os usuários do seu servidor LDAP, em vez de fazer isso manualmente no {% data variables.product.prodname_ghe_server %}. Para obter mais informações, confira "[Como criar equipes](/enterprise/admin/guides/user-management/creating-teams#creating-teams-with-ldap-sync-enabled)". +LDAP Sync lets you synchronize {% data variables.product.prodname_ghe_server %} users and team membership against your established LDAP groups. This lets you establish role-based access control for users from your LDAP server instead of manually within {% data variables.product.prodname_ghe_server %}. For more information, see "[Creating teams](/enterprise/admin/guides/user-management/creating-teams#creating-teams-with-ldap-sync-enabled)." -Para habilitar a Sincronização LDAP, nas configurações do LDAP, selecione **Sincronizar Emails**, **Sincronizar Chaves SSH** ou **Sincronizar Chaves GPG**. +To enable LDAP Sync, in your LDAP settings, select **Synchronize Emails**, **Synchronize SSH Keys**, or **Synchronize GPG Keys** . -![Caixa de seleção de sincronização](/assets/images/enterprise/management-console/ldap-synchronize.png) +![Synchronization check box](/assets/images/enterprise/management-console/ldap-synchronize.png) -Depois que você habilitar a sincronização LDAP, um trabalho de sincronização será executado no período especificado para fazer as seguintes operações em cada conta de usuário: +After you enable LDAP sync, a synchronization job will run at the specified time interval to perform the following operations on each user account: -- Se você tiver permitido a autenticação integrada para usuários de fora do provedor de identidade e o usuário estiver usando a autenticação integrada, vá para o próximo usuário. -- Se não houver mapeamento LDAP para o usuário, tente mapeá-lo para uma entrada LDAP no diretório. Se não for possível mapear o usuário para uma entrada LDAP, suspenda o usuário em questão e passe para o seguinte. -- Se houver um mapeamento LDAP e a entrada LDAP correspondente no diretório estiver ausente, suspenda o usuário e passe para o seguinte. -- Se a entrada LDAP correspondente tiver sido marcada como desativada e o usuário ainda não estiver suspenso, suspenda o usuário e passe para o seguinte. -- Se a entrada LDAP correspondente não estiver marcada como desabilitada, o usuário estiver suspenso e a opção _Reativar usuários suspensos_ estiver habilitada no Centro de Administração, cancele a suspensão do usuário. -- Se um ou mais grupos restritos de usuários estiverem configurados na instância e a entrada do LDAP correspondente não for em um desses grupos, suspenda o usuário. -- Se um ou mais grupos de usuários restritos estiverem configurados na instância, a entrada LDAP correspondente estiver em um desses grupos e a opção _Reativar usuários suspensos_ estiver habilitada no Centro de Administração, cancele a suspensão do usuário. -- Se a entrada LDAP correspondente incluir um atributo `name`, atualize o nome do perfil do usuário. -- Se a entrada LDAP correspondente estiver no grupo de administradores, promova o usuário a administrador do site. -- Se a entrada LDAP correspondente não estiver no grupo de administradores, rebaixe o usuário para uma conta regular. -- Se um campo LDAP User (Usuário LDAP) estiver definido para e-mails, sincronize as configurações de e-mail do usuário com a entrada LDAP. Defina a primeira entrada `mail` do LDAP como o email primário. -- Se um campo LDAP User (Usuário LDAP) estiver definido para chaves SSH públicas, sincronize as chaves SSH públicas do usuário com a entrada LDAP. -- Se um campo LDAP User (Usuário LDAP) estiver definido para chaves GPG públicas, sincronize as chaves GPG públicas do usuário com a entrada LDAP. +- If you've allowed built-in authentication for users outside your identity provider, and the user is using built-in authentication, move on to the next user. +- If no LDAP mapping exists for the user, try to map the user to an LDAP entry in the directory. If the user cannot be mapped to an LDAP entry, suspend the user and move on to the next user. +- If there is an LDAP mapping and the corresponding LDAP entry in the directory is missing, suspend the user and move on to the next user. +- If the corresponding LDAP entry has been marked as disabled and the user is not already suspended, suspend the user and move on to the next user. +- If the corresponding LDAP entry is not marked as disabled, and the user is suspended, and _Reactivate suspended users_ is enabled in the Admin Center, unsuspend the user. +- If one or more restricted user groups are configured on the instance and the corresponding LDAP entry is not in one of these groups, suspend the user. +- If one or more restricted user groups are configured on the instance, the corresponding LDAP entry is in one of these groups, and _Reactivate suspended users_ is enabled in the Admin Center, unsuspend the user. +- If the corresponding LDAP entry includes a `name` attribute, update the user's profile name. +- If the corresponding LDAP entry is in the Administrators group, promote the user to site administrator. +- If the corresponding LDAP entry is not in the Administrators group, demote the user to a normal account. +- If an LDAP User field is defined for emails, synchronize the user's email settings with the LDAP entry. Set the first LDAP `mail` entry as the primary email. +- If an LDAP User field is defined for SSH public keys, synchronize the user's public SSH keys with the LDAP entry. +- If an LDAP User field is defined for GPG keys, synchronize the user's GPG keys with the LDAP entry. {% note %} -**Observação**: as entradas LDAP só poderão ser marcadas como desabilitadas se você usar o Active Directory e o atributo `userAccountControl` estiver presente e sinalizado com `ACCOUNTDISABLE`. Algumas variações do Active Directory, como o AD LDS e o ADAM, não dão suporte ao atributo `userAccountControl`. +**Note**: LDAP entries can only be marked as disabled if you use Active Directory and the `userAccountControl` attribute is present and flagged with `ACCOUNTDISABLE`. Some variations of Active Directory, such as AD LDS and ADAM, don't support the `userAccountControl` attribute. {% endnote %} -Um trabalho de sincronização também será executado no período especificado para fazer as seguintes operações em cada equipe mapeada para um grupo LDAP: +A synchronization job will also run at the specified time interval to perform the following operations on each team that has been mapped to an LDAP group: -- Se um grupo LDAP correspondente de uma equipe tiver sido removido, remova todos os integrantes da equipe. -- Se as entradas do integrante LDAP tiverem sido removidas do grupo LDAP, remova os usuários correspondentes da equipe. Se o usuário não for mais integrante de qualquer equipe na organização, remova o usuário da organização. Se o usuário perder o acesso a qualquer repositórios, exclua todas as bifurcações privadas que ele possa ter nesses repositórios. -- Se as entradas do integrante LDAP tiverem sido adicionadas ao grupo LDAP, adicione os usuários correspondentes à equipe. Se o usuário recuperar o acesso a quaisquer repositórios, restaure todas as bifurcações privadas dos repositórios que foram excluídos porque o usuário perdeu o acesso nos últimos 90 dias. +- If a team's corresponding LDAP group has been removed, remove all members from the team. +- If LDAP member entries have been removed from the LDAP group, remove the corresponding users from the team. If the user is no longer a member of any team in the organization, remove the user from the organization. If the user loses access to any repositories as a result, delete any private forks the user has of those repositories. +- If LDAP member entries have been added to the LDAP group, add the corresponding users to the team. If the user regains access to any repositories as a result, restore any private forks of the repositories that were deleted because the user lost access in the past 90 days. {% data reusables.enterprise_user_management.ldap-sync-nested-teams %} {% warning %} -**Aviso de segurança:** +**Security Warning:** -Quando a Sincronização LDAP está ativada, os administradores do site e os proprietários da organização podem pesquisar grupos no diretório LDAP aos quais pretendem mapear a equipe. +When LDAP Sync is enabled, site admins and organization owners can search the LDAP directory for groups to map the team to. -Esse procedimento pode resultar na divulgação de informações confidenciais da organização para contratados ou outros usuários sem privilégios, inclusive: +This has the potential to disclose sensitive organizational information to contractors or other unprivileged users, including: -- A existência de grupos de LDAP específicos visíveis para o *usuário de pesquisa de domínio*. -- Integrantes do grupo LDAP que tenham contas de usuário no {% data variables.product.prodname_ghe_server %}, divulgadas ao criar uma equipe sincronizada com o grupo LDAP. +- The existence of specific LDAP Groups visible to the *Domain search user*. +- Members of the LDAP group who have {% data variables.product.prodname_ghe_server %} user accounts, which is disclosed when creating a team synced with that LDAP group. -Se a divulgação dessas informações não for desejada, sua empresa ou sua organização deverá restringir as permissões do *Usuário de pesquisa de domínio* configurado no console de administração. Caso não seja possível fazer essa restrição, entre em contato com o {% data variables.contact.contact_ent_support %}. +If disclosing such information is not desired, your company or organization should restrict the permissions of the configured *Domain search user* in the admin console. If such restriction isn't possible, contact {% data variables.contact.contact_ent_support %}. {% endwarning %} -### Classes de grupo de objeto LDAP compatíveis +### Supported LDAP group object classes -O {% data variables.product.prodname_ghe_server %} é compatível com as seguintes classes de grupo de objeto LDAP. Os grupos podem ser aninhados. +{% data variables.product.prodname_ghe_server %} supports these LDAP group object classes. Groups can be nested. - `group` - `groupOfNames` - `groupOfUniqueNames` - `posixGroup` -## Exibir e criar usuários LDAP +## Viewing and creating LDAP users -É possível exibir a lista completa de usuários LDAP que têm acesso à sua instância, e você também pode provisionar novos usuários. +You can view the full list of LDAP users who have access to your instance and provision new users. -{% data reusables.enterprise_site_admin_settings.sign-in %} {% data reusables.enterprise_site_admin_settings.access-settings %} -3. Na barra lateral esquerda, clique em **Usuários do LDAP**. -![Guia Usuários do LDAP](/assets/images/enterprise/site-admin-settings/ldap-users-tab.png) -4. Para pesquisar um usuário, digite um nome de usuário completo ou parcial e clique em **Pesquisar**. Os usuários serão exibidos nos resultados da pesquisa. Se não houver um usuário, clique em **Criar** para provisionar a nova conta de usuário. -![Pesquisa do LDAP](/assets/images/enterprise/site-admin-settings/ldap-users-search.jpg) +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +3. In the left sidebar, click **LDAP users**. +![LDAP users tab](/assets/images/enterprise/site-admin-settings/ldap-users-tab.png) +4. To search for a user, type a full or partial username and click **Search**. Existing users will be displayed in search results. If a user doesn’t exist, click **Create** to provision the new user account. +![LDAP search](/assets/images/enterprise/site-admin-settings/ldap-users-search.jpg) -## Atualizar contas LDAP +## Updating LDAP accounts -A menos que a [Sincronização LDAP esteja habilitada](#enabling-ldap-sync), as alterações nas contas LDAP não serão sincronizadas automaticamente com o {% data variables.product.prodname_ghe_server %}. +Unless [LDAP Sync is enabled](#enabling-ldap-sync), changes to LDAP accounts are not automatically synchronized with {% data variables.product.prodname_ghe_server %}. -* Para usar um novo grupo de administradores LDAP, os usuários devem ser promovidos e rebaixados manualmente no {% data variables.product.prodname_ghe_server %} a fim de refletir as mudanças no LDAP. -* Para adicionar ou remover contas LDAP em grupos de administradores LDAP, [promova ou rebaixe as contas no {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/user-management/promoting-or-demoting-a-site-administrator). -* Para remover contas LDAP, [suspenda as contas do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users). +* To use a new LDAP admin group, users must be manually promoted and demoted on {% data variables.product.prodname_ghe_server %} to reflect changes in LDAP. +* To add or remove LDAP accounts in LDAP admin groups, [promote or demote the accounts on {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/user-management/promoting-or-demoting-a-site-administrator). +* To remove LDAP accounts, [suspend the {% data variables.product.prodname_ghe_server %} accounts](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users). -### Sincronizar contas LDAP manualmente +### Manually syncing LDAP accounts -{% data reusables.enterprise_site_admin_settings.sign-in %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.search-user %} {% data reusables.enterprise_site_admin_settings.click-user %} {% data reusables.enterprise_site_admin_settings.admin-top-tab %} {% data reusables.enterprise_site_admin_settings.admin-tab %} -5. Em "LDAP", clique em **Sincronizar agora** para atualizar manualmente a conta com os dados do servidor LDAP. -![Botão Sincronizar LDAP agora](/assets/images/enterprise/site-admin-settings/ldap-sync-now-button.png) +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.search-user %} +{% data reusables.enterprise_site_admin_settings.click-user %} +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +5. Under "LDAP," click **Sync now** to manually update the account with data from your LDAP server. +![LDAP sync now button](/assets/images/enterprise/site-admin-settings/ldap-sync-now-button.png) -Você também pode [usar a API para disparar uma sincronização manual](/enterprise/user/rest/reference/enterprise-admin#ldap). +You can also [use the API to trigger a manual sync](/enterprise/user/rest/reference/enterprise-admin#ldap). -## Como revogar o acesso ao {% data variables.product.product_location %} +## Revoking access to {% data variables.location.product_location %} -Se a [Sincronização LDAP estiver habilitada](#enabling-ldap-sync), a remoção das credenciais LDAP de um usuário suspenderá a conta dele após a próxima execução da sincronização. +If [LDAP Sync is enabled](#enabling-ldap-sync), removing a user's LDAP credentials will suspend their account after the next synchronization run. -Se a Sincronização LDAP **não** estiver habilitada, você precisará suspender manualmente a conta do {% data variables.product.prodname_ghe_server %} depois de remover as credenciais LDAP. Para obter mais informações, confira "[Como suspender e cancelar a suspensão de usuários](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users)". +If LDAP Sync is **not** enabled, you must manually suspend the {% data variables.product.prodname_ghe_server %} account after you remove the LDAP credentials. For more information, see "[Suspending and unsuspending users](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users)". diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md index c283f5c1d1..6bbe5ad199 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md @@ -1,7 +1,7 @@ --- -title: Sobre SAML para IAM empresarial +title: About SAML for enterprise IAM shortTitle: About SAML for IAM -intro: 'Você pode usar o SSO (logon único) do SAML {% ifversion ghae %}e o SCIM (Sistema de Gerenciamento de Usuários entre Domínios) {% endif %}para gerenciar de modo centralizado o acesso {% ifversion ghec %}a organizações pertencentes à sua empresa no {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}para {% data variables.product.product_location %}{% elsif ghae %}para {% data variables.product.product_location %}{% endif %}.' +intro: 'You can use SAML single sign-on (SSO) {% ifversion ghae %}and System for Cross-domain Identity Management (SCIM) {% endif %}to centrally manage access {% ifversion ghec %}to organizations owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}to {% data variables.location.product_location %}{% elsif ghae %}to {% data variables.location.product_location %}{% endif %}.' versions: ghec: '*' ghes: '*' @@ -22,46 +22,41 @@ redirect_from: - /admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise - /admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise - /admin/identity-and-access-management/using-saml-for-enterprise-iam/about-identity-and-access-management-for-your-enterprise -ms.openlocfilehash: 5a29e3a22e611e6a8a8dcfec75b2f6537a50f08a -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147650394' --- -## Sobre o SSO do SAML para {% ifversion ghec or ghae %}sua empresa em {% endif %}{% ifversion ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} + +## About SAML SSO for {% ifversion ghec or ghae %}your enterprise on {% endif %}{% ifversion ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} {% ifversion ghec %} -Se os membros da empresa gerenciam as próprias contas de usuário no {% data variables.product.product_location %}, você pode configurar a autenticação do SAML como uma restrição de acesso adicional da empresa ou organização. {% data reusables.saml.dotcom-saml-explanation %} +If your enterprise members manage their own user accounts on {% data variables.location.product_location %}, you can configure SAML authentication as an additional access restriction for your enterprise or organization. {% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.saml-accounts %} -{% data reusables.saml.about-saml-enterprise-accounts %} Para obter mais informações, confira "[Como configurar o logon único do SAML para sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)". +{% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)." -Como alternativa, você pode provisionar e gerenciar as contas dos membros da empresa com {% data variables.product.prodname_emus %}. Como ajuda para determinar qual é a melhor opção para sua empresa, o SSO do SAML ou {% data variables.product.prodname_emus %}, confira "[Sobre a autenticação para sua empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)". +Alternatively, you can provision and manage the accounts of your enterprise members with {% data variables.product.prodname_emus %}. To help you determine whether SAML SSO or {% data variables.product.prodname_emus %} is better for your enterprise, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)." -{% data reusables.enterprise-accounts.about-recovery-codes %} Para obter mais informações, confira "[Como gerenciar códigos de recuperação para sua empresa](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)". +{% data reusables.enterprise-accounts.about-recovery-codes %} For more information, see "[Managing recovery codes for your enterprise](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)." -Depois de habilitar o SSO do SAML, dependendo do IdP que você usar, você poderá habilitar as funcionalidades adicionais de gerenciamento de identidade e acesso. +After you enable SAML SSO, depending on the IdP you use, you may be able to enable additional identity and access management features. -Se você usar o Azure AD como seu IDP, você poderá usar a sincronização de equipe para gerenciar a associação de equipe em cada organização. {% data reusables.identity-and-permissions.about-team-sync %} Para obter mais informações, confira "[Como gerenciar a sincronização da equipe para organizações na sua conta corporativa](/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)". +If you use Azure AD as your IDP, you can use team synchronization to manage team membership within each organization. {% data reusables.identity-and-permissions.about-team-sync %} For more information, see "[Managing team synchronization for organizations in your enterprise account](/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)." {% note %} -**Observação:** você não poderá usar o SCIM no nível da empresa, a menos que sua empresa esteja habilitada para {% data variables.product.prodname_emus %}. +**Note:** You cannot use SCIM at the enterprise level unless your enterprise is enabled for {% data variables.product.prodname_emus %}. {% endnote %} -{% data reusables.saml.switching-from-org-to-enterprise %} Para obter mais informações, confira "[Como alternar a configuração do SAML de uma organização para uma conta corporativa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)". +{% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." {% elsif ghes %} -O SAML SSO permite que as pessoas efetuem a autenticação e acessem {% data variables.product.product_location %} por meio de um sistema externo para gerenciamento de identidades. +SAML SSO allows people to authenticate and access {% data variables.location.product_location %} through an external system for identity management. -O SAML é um padrão baseado em XML para autenticação e autorização. Ao configurar o SAML para {% data variables.product.product_location %}, o sistema externo para autenticação é chamado de provedor de identidade (IdP). Sua instância atua como um provedor de serviço (SP) do SAML. Para obter mais informações sobre o padrão SAML, consulte [Security Assertion Markup Language](https://en.wikipedia.org/wiki/Security_Assertion_Markup_Language) na Wikipédia. +SAML is an XML-based standard for authentication and authorization. When you configure SAML for {% data variables.location.product_location %}, the external system for authentication is called an identity provider (IdP). Your instance acts as a SAML service provider (SP). For more information about the SAML standard, see [Security Assertion Markup Language](https://en.wikipedia.org/wiki/Security_Assertion_Markup_Language) on Wikipedia. -Para obter mais informações sobre a configuração do SSO do SAML para o {% data variables.product.product_name %}, consulte "[Como configurar o logon único do SAML para sua empresa](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise)". +For more information about the configuration of SAML SSO on {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise)." {% data reusables.saml.saml-ghes-account-revocation %} @@ -73,24 +68,24 @@ Para obter mais informações sobre a configuração do SSO do SAML para o {% da {% data reusables.saml.ae-uses-saml-sso %} {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} -Após configurar o aplicativo para {% data variables.product.product_name %} no seu provedor de identidade (IdP), você poderá fornecer acesso ao {% data variables.product.product_location %}, atribuindo o aplicativo a usuários e grupos no seu IdP. Para obter mais informações sobre o SSO do SAML para o {% data variables.product.product_name %}, confira "[Como configurar o logon único do SAML para sua empresa](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)". +After you configure the application for {% data variables.product.product_name %} on your identity provider (IdP), you can provision access to {% data variables.location.product_location %} by assigning the application to users and groups on your IdP. For more information about SAML SSO for {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)." -{% data reusables.scim.after-you-configure-saml %} Para obter mais informações, confira "[Como configurar o provisionamento de usuário para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". +{% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." -Para saber como configurar a autenticação e o provisionamento de usuário para o {% data variables.product.product_location %} com seu IdP específico, confira "[Como configurar a autenticação e o provisionamento com seu provedor de identidade](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)". +To learn how to configure both authentication and user provisioning for {% data variables.location.product_location %} with your specific IdP, see "[Configuring authentication and provisioning with your identity provider](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)." {% endif %} -## IdPs compatíveis +## Supported IdPs {% ifversion ghec %} -Nós testamos e oferecemos compatibilidade oficial os seguintes IdPs. Para o SSO do SAML, oferecemos suporte limitado a todos os provedores de identidade que implementam o padrão SAML 2.0. Para obter mais informações, confira o [wiki do SAML](https://wiki.oasis-open.org/security) no site do OASIS. +We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website. -IdP | SAML | Sincronização de equipe | +IdP | SAML | Team synchronization | --- | :--: | :-------: | -Serviços de Federação do Active Directory (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | -Active Directory do Azure (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label="The check icon" %} | +Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | +Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label="The check icon" %} | Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | | OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | @@ -102,7 +97,7 @@ Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% ifversion ghes > 3.3 %} -Se oseu IdP oferecer suporte a declarações criptografadas, você poderá configurar asserções criptografadas no {% data variables.product.product_name %} para aumentar a segurança durante o processo de autenticação. +If your IdP supports encrypted assertions, you can configure encrypted assertions on {% data variables.product.product_name %} for increased security during the authentication process. {% endif %} @@ -110,7 +105,7 @@ Se oseu IdP oferecer suporte a declarações criptografadas, você poderá confi {% elsif ghae %} -Os seguintes IdPs são oficialmente compatíveis com a integração a {% data variables.product.prodname_ghe_managed %}. +The following IdPs are officially supported for integration with {% data variables.product.prodname_ghe_managed %}. {% data reusables.saml.okta-ae-sso-beta %} @@ -120,14 +115,14 @@ Os seguintes IdPs são oficialmente compatíveis com a integração a {% data va {% ifversion ghae %} -## Mapeando equipes de {% data variables.product.prodname_ghe_managed %} com grupos do Okta +## Mapping {% data variables.product.prodname_ghe_managed %} teams to Okta groups -Se usar o Okta como seu IdP, você poderá mapear seus grupos Okta para as equipes em {% data variables.product.product_name %}. Para obter mais informações, confira "[Como mapear grupos do Okta para equipes](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)". +If you use Okta as your IdP, you can map your Okta groups to teams on {% data variables.product.product_name %}. For more information, see "[Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." {% endif %} -## Leitura adicional +## Further reading -- [Wiki do SAML](https://wiki.oasis-open.org/security) no site do OASIS -- [Sistema de Gerenciamento de Usuários entre Domínios: protocolo (RFC 7644)](https://tools.ietf.org/html/rfc7644) no site do IETF{% ifversion ghae %} -- [Como restringir o tráfego de rede para sua empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise){% endif %} +- [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website +- [System for Cross-domain Identity Management: Protocol (RFC 7644)](https://tools.ietf.org/html/rfc7644) on the IETF website{% ifversion ghae %} +- [Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise){% endif %} diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md index e68ac248db..8775694a20 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md @@ -1,7 +1,7 @@ --- -title: Configurar a autenticação e provisionamento para sua empresa usando o Azure AD +title: Configuring authentication and provisioning for your enterprise using Azure AD shortTitle: Configure with Azure AD -intro: 'Você pode usar um inquilino no Azure Active Directory (Azure AD) como um provedor de identidade (IdP) para gerenciar centralizadamente autenticação e provisionamento de usuário para {% data variables.product.product_location %}.' +intro: 'You can use a tenant in Azure Active Directory (Azure AD) as an identity provider (IdP) to centrally manage authentication and user provisioning for {% data variables.location.product_location %}.' permissions: 'Enterprise owners can configure authentication and provisioning for an enterprise on {% data variables.product.product_name %}.' versions: ghae: '*' @@ -16,48 +16,42 @@ redirect_from: - /admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad - /admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad - /admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad -ms.openlocfilehash: 6374081e3a0d71238b0ebd84e64575da55ea8e61 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145094945' --- -## Sobre autenticação e provisionamento de usuário com Azure AD +## About authentication and user provisioning with Azure AD -O Azure Active Directory (Azure AD) é um serviço da Microsoft que permite gerenciar centralmente as contas de usuários e acessar aplicativos da web. Para obter mais informações, confira [O que é o Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) no Microsoft Docs. +Azure Active Directory (Azure AD) is a service from Microsoft that allows you to centrally manage user accounts and access to web applications. For more information, see [What is Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) in the Microsoft Docs. -Para gerenciar identidade e acesso para {% data variables.product.product_name %}, você pode usar um inquilino no Azure AD como um IdP de SAML para autenticação. Você também pode configurar o Azure AD para fornecer contas automaticamente e acessar a associação com o SCIM, que permite criar usuários de {% data variables.product.prodname_ghe_managed %} e gerenciar os membros da equipe e da organização do seu inquilino do Azure AD. +To manage identity and access for {% data variables.product.product_name %}, you can use an Azure AD tenant as a SAML IdP for authentication. You can also configure Azure AD to automatically provision accounts and access membership with SCIM, which allows you to create {% data variables.product.prodname_ghe_managed %} users and manage team and organization membership from your Azure AD tenant. -Após habilitar o SAML SSO e SCIM durante {% data variables.product.prodname_ghe_managed %} usando Azure AD, você pode realizar o seguinte no seu inquilino do Azure AD. +After you enable SAML SSO and SCIM for {% data variables.product.prodname_ghe_managed %} using Azure AD, you can accomplish the following from your Azure AD tenant. -* Atribua o aplicativo de {% data variables.product.prodname_ghe_managed %} no Azure AD a uma conta de usuário para criar e conceder acesso automaticamente a uma conta de usuário correspondente em {% data variables.product.product_name %}. -* Desatribua o aplicativo de {% data variables.product.prodname_ghe_managed %} para uma conta de usuário no Azure AD para desabilitar a conta de usuário correspondente em {% data variables.product.product_name %}. -* Atribua o aplicativo {% data variables.product.prodname_ghe_managed %} a um grupo IdP no Azure AD para criar automaticamente e conceder acesso a contas de usuário em {% data variables.product.product_name %} para todos os integrantes do grupo IdP. Além disso, o grupo IdP está disponível em {% data variables.product.prodname_ghe_managed %} para conexão com uma equipe e sua organização principal. -* Desatribua o aplicativo de {% data variables.product.prodname_ghe_managed %} de um grupo de IdP para desativar as contas de usuário de {% data variables.product.product_name %} de todos os usuários de IdP que tiveram acesso somente através desse grupo de IdP e remova os usuários da organização principal. O grupo IdP será desconectado de qualquer equipe em {% data variables.product.product_name %}. +* Assign the {% data variables.product.prodname_ghe_managed %} application on Azure AD to a user account to automatically create and grant access to a corresponding user account on {% data variables.product.product_name %}. +* Unassign the {% data variables.product.prodname_ghe_managed %} application to a user account on Azure AD to deactivate the corresponding user account on {% data variables.product.product_name %}. +* Assign the {% data variables.product.prodname_ghe_managed %} application to an IdP group on Azure AD to automatically create and grant access to user accounts on {% data variables.product.product_name %} for all members of the IdP group. In addition, the IdP group is available on {% data variables.product.prodname_ghe_managed %} for connection to a team and its parent organization. +* Unassign the {% data variables.product.prodname_ghe_managed %} application from an IdP group to deactivate the {% data variables.product.product_name %} user accounts of all IdP users who had access only through that IdP group and remove the users from the parent organization. The IdP group will be disconnected from any teams on {% data variables.product.product_name %}. -Para obter mais informações sobre como gerenciar a identidade e o acesso para sua empresa no {% data variables.product.product_location %}, confira "[Como gerenciar a identidade e o acesso para sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise)". Para obter mais informações sobre como sincronizar equipes com grupos de IdP, confira "[Como sincronizar uma equipe com um grupo de provedores de identidade](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)". +For more information about managing identity and access for your enterprise on {% data variables.location.product_location %}, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." For more information about synchronizing teams with IdP groups, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." -## Pré-requisitos +## Prerequisites -Para configurar o provisionamento de autenticação e usuário para {% data variables.product.product_name %} usando o Azure AD, você deve ter uma conta do Azure AD e um inquilino. Para obter mais informações, confira o [site do Azure AD](https://azure.microsoft.com/free/active-directory) e o [Guia de Início Rápido: Criar um locatário do Azure Active Directory](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant) no Microsoft Docs. +To configure authentication and user provisioning for {% data variables.product.product_name %} using Azure AD, you must have an Azure AD account and tenant. For more information, see the [Azure AD website](https://azure.microsoft.com/free/active-directory) and [Quickstart: Create an Azure Active Directory tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant) in the Microsoft Docs. -{% data reusables.saml.assert-the-administrator-attribute %} Para obter mais informações sobre como incluir o atributo `administrator` na declaração SAML do Azure AD, confira [Como personalizar declarações emitidas no token SAML para aplicativos empresariais](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization) no Microsoft Docs. +{% data reusables.saml.assert-the-administrator-attribute %} For more information about including the `administrator` attribute in the SAML claim from Azure AD, see [How to: customize claims issued in the SAML token for enterprise applications](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization) in the Microsoft Docs. {% data reusables.saml.create-a-machine-user %} -## Configurar autenticação e provisionamento de usuário com Azure AD +## Configuring authentication and user provisioning with Azure AD {% ifversion ghae %} -1. No Azure AD, adicione {% data variables.product.ae_azure_ad_app_link %} ao seu inquilino e configure logon único. Para obter mais informações, confira [Tutorial: Integração do SSO (logon único) do Azure Active Directory ao {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) no Microsoft Docs. +1. In Azure AD, add {% data variables.product.ae_azure_ad_app_link %} to your tenant and configure single sign-on. For more information, see [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs. -1. Em {% data variables.product.prodname_ghe_managed %}, insira os detalhes para o seu inquilino do Azure AD. +1. In {% data variables.product.prodname_ghe_managed %}, enter the details for your Azure AD tenant. - {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} - - Se você já configurou SSO de SAML para {% data variables.product.product_location %} usando outro IdP e você deseja usar o Azure AD, você pode editar a sua configuração. Para obter mais informações, confira "[Como configurar o logon único do SAML para sua empresa](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise#editing-the-saml-sso-configuration)". + - If you've already configured SAML SSO for {% data variables.location.product_location %} using another IdP and you want to use Azure AD instead, you can edit your configuration. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise#editing-the-saml-sso-configuration)." -1. Habilitar provisionamento do usuário em {% data variables.product.product_name %} e configurar provisionamento do usuário no Azure AD. Para obter mais informações, confira "[Como configurar o provisionamento de usuário para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)". +1. Enable user provisioning in {% data variables.product.product_name %} and configure user provisioning in Azure AD. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)." {% endif %} diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md index fc9bfd6e39..e0b7437cad 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md @@ -1,7 +1,7 @@ --- -title: Configurar autenticação e provisionamento para sua empresa usando o Okta +title: Configuring authentication and provisioning for your enterprise using Okta shortTitle: Configure with Okta -intro: 'Você pode usar o Okta como um provedor de identidade (IdP) para gerenciar centralmente o provisionamento de autenticação e usuário para {% data variables.product.prodname_ghe_managed %}.' +intro: 'You can use Okta as an identity provider (IdP) to centrally manage authentication and user provisioning for {% data variables.product.prodname_ghe_managed %}.' permissions: 'Enterprise owners can configure authentication and provisioning for {% data variables.product.prodname_ghe_managed %}.' versions: ghae: '*' @@ -16,143 +16,144 @@ topics: - Identity - SSO miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 824554d1e35131e1e44f816e6fac3b40803db46d -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145093959' --- + {% data reusables.saml.okta-ae-sso-beta %} -## Sobre SAML e SCIM com Okta +## About SAML and SCIM with Okta -Você pode usar Okta como um Provedor de Identidade (IdP) para {% data variables.product.prodname_ghe_managed %}, o que permite aos usuários do Okta efetuem o login em {% data variables.product.prodname_ghe_managed %} usando suas credenciais do Okta. +You can use Okta as an Identity Provider (IdP) for {% data variables.product.prodname_ghe_managed %}, which allows your Okta users to sign in to {% data variables.product.prodname_ghe_managed %} using their Okta credentials. -Para usar Okta como seu IdP para {% data variables.product.prodname_ghe_managed %}, você pode adicionar o aplicativo {% data variables.product.prodname_ghe_managed %} ao Okta, configurar o Okta como seu IdP em {% data variables.product.prodname_ghe_managed %} e fornecer acesso aos seus usuários e grupos da Okta. +To use Okta as your IdP for {% data variables.product.prodname_ghe_managed %}, you can add the {% data variables.product.prodname_ghe_managed %} app to Okta, configure Okta as your IdP in {% data variables.product.prodname_ghe_managed %}, and provision access for your Okta users and groups. -Os recursos de provisionamento a seguir estão disponíveis para todos os usuários do Okta que você atribuir ao seu aplicativo de {% data variables.product.prodname_ghe_managed %}. +The following provisioning features are available for all Okta users that you assign to your {% data variables.product.prodname_ghe_managed %} application. -| Recurso | Descrição | +| Feature | Description | | --- | --- | -| Fazer push de novos usuários | Ao criar um novo usuário no Okta, o usuário é adicionado a {% data variables.product.prodname_ghe_managed %}. | -| Fazer push de desativações de usuário | Ao desativar um usuário no Okta, ele irá suspender o usuário da sua empresa em {% data variables.product.prodname_ghe_managed %}. | -| Fazer push das atualização de perfil | Ao atualizar o perfil de um usuário no Okta, ele irá atualizar os metadados para a associação de usuários na sua empresa em {% data variables.product.prodname_ghe_managed %}. | -| Reativar usuários | Ao reativar um usuário no Okta, ele cancelará a suspensão do usuário na sua empresa em {% data variables.product.prodname_ghe_managed %}. | +| Push New Users | When you create a new user in Okta, the user is added to {% data variables.product.prodname_ghe_managed %}. | +| Push User Deactivation | When you deactivate a user in Okta, it will suspend the user from your enterprise on {% data variables.product.prodname_ghe_managed %}. | +| Push Profile Updates | When you update a user's profile in Okta, it will update the metadata for the user's membership in your enterprise on {% data variables.product.prodname_ghe_managed %}. | +| Reactivate Users | When you reactivate a user in Okta, it will unsuspend the user in your enterprise on {% data variables.product.prodname_ghe_managed %}. | -## Como adicionar o aplicativo do {% data variables.product.prodname_ghe_managed %} no Okta +## Adding the {% data variables.product.prodname_ghe_managed %} application in Okta {% data reusables.saml.okta-ae-applications-menu %} -1. Clique em **Navegar pelo Catálogo de Aplicativos** +1. Click **Browse App Catalog** - !["Navegar pelo Catálogo de Aplicativos"](/assets/images/help/saml/okta-ae-browse-app-catalog.png) + !["Browse App Catalog"](/assets/images/help/saml/okta-ae-browse-app-catalog.png) -1. No campo de pesquisa, digite "GitHub AE" e clique no **GitHub AE** nos resultados. +1. In the search field, type "GitHub AE", then click **GitHub AE** in the results. - !["Resultado da pesquisa"](/assets/images/help/saml/okta-ae-search.png) + !["Search result"](/assets/images/help/saml/okta-ae-search.png) -1. Clique em **Adicionar**. +1. Click **Add**. - !["Adicionar aplicativo do GitHub AE"](/assets/images/help/saml/okta-ae-add-github-ae.png) + !["Add GitHub AE app"](/assets/images/help/saml/okta-ae-add-github-ae.png) -1. Para "URL de base", digite a URL da empresa em {% data variables.product.prodname_ghe_managed %}. +1. For "Base URL", type the URL of your enterprise on {% data variables.product.prodname_ghe_managed %}. - !["Configurar a URL base"](/assets/images/help/saml/okta-ae-configure-base-url.png) + !["Configure Base URL"](/assets/images/help/saml/okta-ae-configure-base-url.png) -1. Clique em **Concluído**. +1. Click **Done**. -## Habilitando o SAML SSO para {% data variables.product.prodname_ghe_managed %} +## Enabling SAML SSO for {% data variables.product.prodname_ghe_managed %} -Para habilitar o logon único (SSO) para {% data variables.product.prodname_ghe_managed %}, você deverá configurar {% data variables.product.prodname_ghe_managed %} para usar a URL de login, a URL do expedidor e o certificado público fornecido pelo Okta. Você pode encontrar esses detalhes no aplicativo "GitHub AE". +To enable single sign-on (SSO) for {% data variables.product.prodname_ghe_managed %}, you must configure {% data variables.product.prodname_ghe_managed %} to use the sign-on URL, issuer URL, and public certificate provided by Okta. You can find locate these details in the "GitHub AE" app. -{% data reusables.saml.okta-ae-applications-menu %} {% data reusables.saml.okta-ae-configure-app %} -1. Clique em **Entrar**. +{% data reusables.saml.okta-ae-applications-menu %} +{% data reusables.saml.okta-ae-configure-app %} +1. Click **Sign On**. - ![Guia de iniciar sessão](/assets/images/help/saml/okta-ae-sign-on-tab.png) + ![Sign On tab](/assets/images/help/saml/okta-ae-sign-on-tab.png) -1. Clique em **Exibir Instruções de Instalação**. +1. Click **View Setup Instructions**. - ![Guia de iniciar sessão](/assets/images/help/saml/okta-ae-view-setup-instructions.png) + ![Sign On tab](/assets/images/help/saml/okta-ae-view-setup-instructions.png) -1. Anote os detalhes da "URL de início de sessão", "Emissor" e "Certificado público". -1. Use os detalhes para habilitar o SAML SSO para a sua empresa em {% data variables.product.prodname_ghe_managed %}. Para obter mais informações, confira "[Como configurar o logon único do SAML para sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)". +1. Take note of the "Sign on URL", "Issuer", and "Public certificate" details. +1. Use the details to enable SAML SSO for your enterprise on {% data variables.product.prodname_ghe_managed %}. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)." {% note %} -**Observação:** para testar sua configuração do SAML no {% data variables.product.prodname_ghe_managed %}, sua conta de usuário do Okta precisa ser atribuída ao aplicativo do {% data variables.product.prodname_ghe_managed %}. +**Note:** To test your SAML configuration from {% data variables.product.prodname_ghe_managed %}, your Okta user account must be assigned to the {% data variables.product.prodname_ghe_managed %} app. {% endnote %} -## Habilitando a integração da API +## Enabling API integration -O aplicativo "GitHub AE" no Okta usa a API de {% data variables.product.product_name %} para interagir com a sua empresa para SCIM e SSO. Este procedimento explica como habilitar e testar o acesso à API, configurando o Okta com um token de acesso pessoal para {% data variables.product.prodname_ghe_managed %}. +The "GitHub AE" app in Okta uses the {% data variables.product.product_name %} API to interact with your enterprise for SCIM and SSO. This procedure explains how to enable and test access to the API by configuring Okta with a {% data variables.product.pat_generic %} for {% data variables.product.prodname_ghe_managed %}. -1. No {% data variables.product.prodname_ghe_managed %}, gere um token de acesso pessoal com o escopo `admin:enterprise`. Para obter mais informações, confira "[Como criar um token de acesso pessoal](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)". -{% data reusables.saml.okta-ae-applications-menu %} {% data reusables.saml.okta-ae-configure-app %} {% data reusables.saml.okta-ae-provisioning-tab %} -1. Clique em **Configurar Integração de API**. +1. In {% data variables.product.prodname_ghe_managed %}, generate a {% data variables.product.pat_v1 %} with the `admin:enterprise` scope. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)". +{% data reusables.saml.okta-ae-applications-menu %} +{% data reusables.saml.okta-ae-configure-app %} +{% data reusables.saml.okta-ae-provisioning-tab %} +1. Click **Configure API Integration**. -1. Selecione **Habilitar integração de API**. +1. Select **Enable API integration**. - ![Habilitar a integração da API](/assets/images/help/saml/okta-ae-enable-api-integration.png) + ![Enable API integration](/assets/images/help/saml/okta-ae-enable-api-integration.png) -1. Para "Token da API", digite o token de acesso pessoal de {% data variables.product.prodname_ghe_managed %} que você gerou anteriormente. +1. For "API Token", type the {% data variables.product.prodname_ghe_managed %} {% data variables.product.pat_generic %} you generated previously. -1. Clique em **Testar Credenciais da API**. +1. Click **Test API Credentials**. {% note %} -**Observação:** se `Error authenticating: No results for users returned` for exibido, confirme se você habilitou o SSO para o {% data variables.product.prodname_ghe_managed %}. Para obter mais informações, confira "[Como habilitar o SSO do SAML para o {% data variables.product.prodname_ghe_managed %}](#enabling-saml-sso-for-github-ae)". +**Note:** If you see `Error authenticating: No results for users returned`, confirm that you have enabled SSO for {% data variables.product.prodname_ghe_managed %}. For more information see "[Enabling SAML SSO for {% data variables.product.prodname_ghe_managed %}](#enabling-saml-sso-for-github-ae)." {% endnote %} -## Definindo as configurações de provisionamento do SCIM +## Configuring SCIM provisioning settings -Este procedimento demonstra como definir as configurações do SCIM para o provisionamento do Okta. Essas configurações definem quais recursos serão usados ao provisionar automaticamente as contas de usuário do Okta para {% data variables.product.prodname_ghe_managed %}. +This procedure demonstrates how to configure the SCIM settings for Okta provisioning. These settings define which features will be used when automatically provisioning Okta user accounts to {% data variables.product.prodname_ghe_managed %}. -{% data reusables.saml.okta-ae-applications-menu %} {% data reusables.saml.okta-ae-configure-app %} {% data reusables.saml.okta-ae-provisioning-tab %} -1. Em "Configurações", clique em **No Aplicativo**. +{% data reusables.saml.okta-ae-applications-menu %} +{% data reusables.saml.okta-ae-configure-app %} +{% data reusables.saml.okta-ae-provisioning-tab %} +1. Under "Settings", click **To App**. - ![Configurações de "No Aplicativo"](/assets/images/help/saml/okta-ae-to-app-settings.png) + !["To App" settings](/assets/images/help/saml/okta-ae-to-app-settings.png) -1. À direita de "Provisionamento no Aplicativo", clique em **Editar**. -1. À direita de "Criar Usuários", selecione **Habilitar**. -1. À direita de "Atualizar Atributos do Usuário", selecione **Habilitar**. -1. À direita de "Desativar Usuários", selecione **Habilitar**. -1. Clique em **Salvar**. +1. To the right of "Provisioning to App", click **Edit**. +1. To the right of "Create Users", select **Enable**. +1. To the right of "Update User Attributes", select **Enable**. +1. To the right of "Deactivate Users", select **Enable**. +1. Click **Save**. -## Permitir que usuários e grupos do Okta acessem {% data variables.product.prodname_ghe_managed %} +## Allowing Okta users and groups to access {% data variables.product.prodname_ghe_managed %} -Você pode fornecer acesso a {% data variables.product.product_name %} para os usuários individuais do Okta, ou para grupos inteiros. +You can provision access to {% data variables.product.product_name %} for your individual Okta users, or for entire groups. -### Provisionando acesso para usuários do Okta +### Provisioning access for Okta users -Antes que seus usuários do Okta possam usar suas credenciais para efetuar o login em {% data variables.product.prodname_ghe_managed %}, você deverá atribuir os usuários ao aplicativo "GitHub AE" no Okta. +Before your Okta users can use their credentials to sign in to {% data variables.product.prodname_ghe_managed %}, you must assign the users to the "GitHub AE" app in Okta. -{% data reusables.saml.okta-ae-applications-menu %} {% data reusables.saml.okta-ae-configure-app %} +{% data reusables.saml.okta-ae-applications-menu %} +{% data reusables.saml.okta-ae-configure-app %} -1. Clique em **Atribuições**. +1. Click **Assignments**. - ![Aba de atribuições](/assets/images/help/saml/okta-ae-assignments-tab.png) + ![Assignments tab](/assets/images/help/saml/okta-ae-assignments-tab.png) -1. Selecione o menu Atribuir menu suspenso e clique em **Atribuir a Pessoas**. +1. Select the Assign drop-down menu and click **Assign to People**. - ![Botão "Atribuir a Pessoas"](/assets/images/help/saml/okta-ae-assign-to-people.png) + !["Assign to People" button](/assets/images/help/saml/okta-ae-assign-to-people.png) -1. À direita da conta de usuário necessária, clique em **Atribuir**. +1. To the right of the required user account, click **Assign**. - ![Lista de usuários](/assets/images/help/saml/okta-ae-assign-user.png) + ![List of users](/assets/images/help/saml/okta-ae-assign-user.png) -1. À direita de "Função", clique em uma função para o usuário e clique em **Salvar e voltar**. +1. To the right of "Role", click a role for the user, then click **Save and go back**. - ![Seleção de função](/assets/images/help/saml/okta-ae-assign-role.png) + ![Role selection](/assets/images/help/saml/okta-ae-assign-role.png) -1. Clique em **Concluído**. +1. Click **Done**. -### Provisionando acesso para grupos do Okta +### Provisioning access for Okta groups -Você pode mapear o seu grupo do Okta para uma equipe em {% data variables.product.prodname_ghe_managed %}. Os integrantes do grupo do Okta irão tornar-se automaticamente integrantes da equipe de {% data variables.product.prodname_ghe_managed %} mapeada. Para obter mais informações, confira "[Como mapear grupos do Okta para equipes](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)". +You can map your Okta group to a team in {% data variables.product.prodname_ghe_managed %}. Members of the Okta group will then automatically become members of the mapped {% data variables.product.prodname_ghe_managed %} team. For more information, see "[Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." -## Leitura adicional +## Further reading -- [Noções básicas sobre o SAML](https://developer.okta.com/docs/concepts/saml/) na documentação do Okta. -- [Noções básicas sobre o SCIM](https://developer.okta.com/docs/concepts/scim/) na documentação do Okta. +- [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) in the Okta documentation. +- [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) in the Okta documentation. diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md index 1ab2f0b7df..5f0283606c 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Configurar o logon único SAML para sua empresa +title: Configuring SAML single sign-on for your enterprise shortTitle: Configure SAML SSO -intro: 'Você pode controlar e proteger o acesso a {% ifversion ghec %}recursos, como repositórios, problemas e solicitações de pull nas organizações da empresa{% elsif ghes %}{% data variables.product.product_location %}{% elsif ghae %}sua empresa no {% data variables.product.prodname_ghe_managed %}{% endif %} com a {% ifversion ghec %}imposição{% elsif ghes or ghae %}configuração{% endif %} do SSO (logon único) do SAML por meio do IdP (provedor de identidade).' +intro: 'You can control and secure access to {% ifversion ghec %}resources like repositories, issues, and pull requests within your enterprise''s organizations{% elsif ghes %}{% data variables.location.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.prodname_ghe_managed %}{% endif %} by {% ifversion ghec %}enforcing{% elsif ghes or ghae %}configuring{% endif %} SAML single sign-on (SSO) through your identity provider (IdP).' permissions: '{% ifversion ghes %}Site administrators{% elsif ghec or ghae %}Enterprise owners{% endif %} can configure SAML SSO for {% ifversion ghec or ghae %}an enterprise on {% data variables.product.product_name %}{% elsif ghes %}a {% data variables.product.product_name %} instance{% endif %}.' versions: ghec: '*' @@ -21,16 +21,11 @@ redirect_from: - /github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account - /admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise - /admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise -ms.openlocfilehash: a53a82ca88bb13b4e8fbb6ec5b2f2cd513f7b6a4 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147526827' --- + {% data reusables.enterprise-accounts.emu-saml-note %} -## Sobre o SAML SSO +## About SAML SSO {% ifversion ghec %} @@ -38,11 +33,11 @@ ms.locfileid: '147526827' {% data reusables.saml.saml-accounts %} -Para obter mais informações, confira "[Sobre o gerenciamento de identidades e acesso com o logon único do SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)". +For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." {% data reusables.saml.about-saml-enterprise-accounts %} -{% data reusables.saml.about-saml-access-enterprise-account %} Para obter mais informações, confira "[Como ver e gerenciar o acesso do SAML de um usuário à sua conta corporativa](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)". +{% data reusables.saml.about-saml-access-enterprise-account %} For more information, see "[Viewing and managing a user's SAML access to your enterprise account](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)." {% data reusables.saml.saml-disabled-linked-identities-removed %} @@ -50,9 +45,9 @@ Para obter mais informações, confira "[Sobre o gerenciamento de identidades e {% elsif ghes or ghae %} -O SAML SSO permite que você controle centralmente e proteja o acesso ao {% data variables.product.product_location %} a partir do seu IdP SAML. Quando um usuário não autenticado visita {% data variables.product.product_location %} em um navegador, {% data variables.product.product_name %} redirecionará o usuário para seu IdP do SAML para efetuar a autenticação. Depois que o usuário efetua a autenticação com sucesso com uma conta no IdP, o usuário do IdP redireciona o usuário de volta para {% data variables.product.product_location %}. {% data variables.product.product_name %} valida a resposta do seu IdP e, em seguida, concede acesso ao usuário. +SAML SSO allows you to centrally control and secure access to {% data variables.location.product_location %} from your SAML IdP. When an unauthenticated user visits {% data variables.location.product_location %} in a browser, {% data variables.product.product_name %} will redirect the user to your SAML IdP to authenticate. After the user successfully authenticates with an account on the IdP, the IdP redirects the user back to {% data variables.location.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access to the user. -Depois que um usuário efetua a autenticação com sucesso no seu IdP, a sessão do SAML do usuário para {% data variables.product.product_location %} fica ativa no navegador por 24 horas. Depois de 24 horas, o usuário deve efetuar a autenticação novamente com o seu IdP. +After a user successfully authenticates on your IdP, the user's SAML session for {% data variables.location.product_location %} is active in the browser for 24 hours. After 24 hours, the user must authenticate again with your IdP. {% data reusables.saml.saml-ghes-account-revocation %} @@ -60,166 +55,176 @@ Depois que um usuário efetua a autenticação com sucesso no seu IdP, a sessão {% data reusables.saml.assert-the-administrator-attribute %} -{% data reusables.scim.after-you-configure-saml %} Para obter mais informações, confira "[Como configurar o provisionamento de usuário para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". +{% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." {% endif %} {% endif %} -## Provedores de identidade compatíveis +## Supported identity providers {% data reusables.saml.saml-supported-idps %} {% ifversion ghec %} -## Considerações de nome de usuário no SAML +## Username considerations with SAML -{% ifversion ghec %} Se você usar {% data variables.product.prodname_emus %}, {% endif %}{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} Para obter mais informações, confira "[Considerações de nome de usuário para autenticação externa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)". +{% ifversion ghec %}If you use {% data variables.product.prodname_emus %}, {% endif %}{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)." -## Aplicar o logon único SAML para organizações na sua conta corporativa +## Enforcing SAML single-sign on for organizations in your enterprise account {% note %} -**Observações:** +**Notes:** -- Ao aplicar o logon único SAML SSO para sua empresa, a configuração corporativa substituirá todas as configurações do SAML existentes no nível da organização. {% data reusables.saml.switching-from-org-to-enterprise %} Para obter mais informações, confira "[Como alternar a configuração do SAML de uma organização para uma conta corporativa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)". -- Ao aplicar o SAML SSO para uma organização, {% data variables.product.company_short %} removerá todos os integrantes da organização que não tenham efetuado a autenticação com sucesso com seu IdP do SAML. Ao exigir o SAML SSO para a sua empresa, {% data variables.product.company_short %} não irá remover os integrantes da empresa que não tenham efetuado a autenticação com sucesso com o IdP do SAML. Na próxima vez que um integrante acessar os recursos da empresa, ele deverá efetuar a autenticação com o seu IdP do SAML. +- When you enforce SAML SSO for your enterprise, the enterprise configuration will override any existing organization-level SAML configurations. {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." +- When you enforce SAML SSO for an organization, {% data variables.product.company_short %} removes any members of the organization that have not authenticated successfully with your SAML IdP. When you require SAML SSO for your enterprise, {% data variables.product.company_short %} does not remove members of the enterprise that have not authenticated successfully with your SAML IdP. The next time a member accesses the enterprise's resources, the member must authenticate with your SAML IdP. {% endnote %} -Para obter informações mais detalhadas sobre como habilitar o SAML usando o Okta, confira "[Como configurar o logon único do SAML para sua conta corporativa usando o Okta](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)". +For more detailed information about how to enable SAML using Okta, see "[Configuring SAML single sign-on for your enterprise account using Okta](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)." -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} 4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. Em "Logon único do SAML", selecione **Exigir autenticação SAML**. - ![Caixa de seleção para habilitar o SSO do SAML](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) -6. No campo **URL de Logon**, digite o ponto de extremidade HTTPS do IdP para solicitações de logon único. Esse valor está disponível na configuração do IdP. -![Campo referente à URL para a qual os membros serão encaminhados após a entrada](/assets/images/help/saml/saml_sign_on_url_business.png) -7. Opcionalmente, no campo **Emissor**, digite a URL do emissor do SAML para verificar a autenticidade das mensagens enviadas. -![Campo referente ao nome do emissor do SAML](/assets/images/help/saml/saml_issuer.png) -8. Em **Certificado Público**, cole um certificado para verificar as respostas do SAML. -![Campo referente ao certificado público do provedor de identidade](/assets/images/help/saml/saml_public_certificate.png) -9. Para verificar a integridade das solicitações do emissor do SAML, clique em {% octicon "pencil" aria-label="The edit icon" %}. Em seguida, no menu suspenso "Método de assinatura" e "Método de resumo", escolha o algoritmo de hashing usado pelo seu emissor do SAML. -![Menus suspensos dos algoritmos de hash Método de Assinatura e Método de resumo usados pelo emissor do SAML](/assets/images/help/saml/saml_hashing_method.png) -10. Antes de habilitar o SSO do SAML para sua empresa, clique em **Testar configuração do SAML** para garantir que as informações que você inseriu estão corretas. ![Botão usado para testar a configuração do SAML antes da imposição](/assets/images/help/saml/saml_test.png) -11. Clique em **Salvar**. +5. Under "SAML single sign-on", select **Require SAML authentication**. + ![Checkbox for enabling SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) +6. In the **Sign on URL** field, type the HTTPS endpoint of your IdP for single sign-on requests. This value is available in your IdP configuration. +![Field for the URL that members will be forwarded to when signing in](/assets/images/help/saml/saml_sign_on_url_business.png) +7. Optionally, in the **Issuer** field, type your SAML issuer URL to verify the authenticity of sent messages. +![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png) +8. Under **Public Certificate**, paste a certificate to verify SAML responses. +![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png) +9. To verify the integrity of the requests from your SAML issuer, click {% octicon "pencil" aria-label="The edit icon" %}. Then in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. +![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png) +10. Before enabling SAML SSO for your enterprise, click **Test SAML configuration** to ensure that the information you've entered is correct. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png) +11. Click **Save**. {% data reusables.enterprise-accounts.download-recovery-codes %} {% elsif ghes %} -## Configurando o SAML SSO +## Configuring SAML SSO -Você pode habilitar ou desabilitar a autenticação do SAML para {% data variables.product.product_location %} ou você pode editar uma configuração existente. Você pode ver e editar as configurações de autenticação do {% data variables.product.product_name %} no console de gerenciamento. Para obter mais informações, confira "[Como acessar o console de gerenciamento](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)". +You can enable or disable SAML authentication for {% data variables.location.product_location %}, or you can edit an existing configuration. You can view and edit authentication settings for {% data variables.product.product_name %} in the management console. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)." {% note %} -**Observação**: {% data reusables.enterprise.test-in-staging %} +**Note**: {% data reusables.enterprise.test-in-staging %} {% endnote %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.authentication %} -1. Selecione **SAML**. +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.authentication %} +1. Select **SAML**. - ![Captura de tela da opção para habilitar a autenticação SAML no console de gerenciamento](/assets/images/enterprise/management-console/auth-select-saml.png) + ![Screenshot of option to enable SAML authentication in management console](/assets/images/enterprise/management-console/auth-select-saml.png) 1. {% data reusables.enterprise_user_management.built-in-authentication-option %} - ![Captura de tela da opção para habilitar a autenticação integrada fora do IdP do SAML](/assets/images/enterprise/management-console/saml-built-in-authentication.png) -1. Opcionalmente, para habilitar o SSO de resposta não solicitado, selecione **SSO iniciado pelo IdP**. Por padrão, o {% data variables.product.prodname_ghe_server %} responderá a uma solicitação iniciada pelo IdP (provedor de identidade) não solicitada com uma `AuthnRequest`. + ![Screenshot of option to enable built-in authentication outside of SAML IdP](/assets/images/enterprise/management-console/saml-built-in-authentication.png) +1. Optionally, to enable unsolicited response SSO, select **IdP initiated SSO**. By default, {% data variables.product.prodname_ghe_server %} will reply to an unsolicited Identity Provider (IdP) initiated request with an `AuthnRequest` back to the IdP. - ![Captura de tela da opção para habilitar resposta não solicitada iniciada pelo IdP](/assets/images/enterprise/management-console/saml-idp-sso.png) + ![Screenshot of option to enable IdP-initiated unsolicited response](/assets/images/enterprise/management-console/saml-idp-sso.png) {% tip %} - **Observação**: recomendamos manter esse valor **desmarcado**. Você **só** deverá habilitar esse recurso na rara ocasião em que a implementação do SAML não der suporte ao SSO iniciado pelo provedor de serviços e quando recomendado pelo {% data variables.contact.enterprise_support %}. + **Note**: We recommend keeping this value **unselected**. You should enable this feature **only** in the rare instance that your SAML implementation does not support service provider initiated SSO, and when advised by {% data variables.contact.enterprise_support %}. {% endtip %} -1. Selecione **Desabilitar rebaixamento/promoção do administrador** se **não** quiser que o provedor do SAML determine direitos de administrador para os usuários na {% data variables.product.product_location %}. +1. Select **Disable administrator demotion/promotion** if you **do not** want your SAML provider to determine administrator rights for users on {% data variables.location.product_location %}. - ![Captura de tela da opção para habilitar a opção para respeitar o atributo do "administrador" do IdP a fim de habilitar ou desabilitar direitos administrativos](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png) {%- ifversion ghes > 3.3 %} -1. Opcionalmente, para permitir que a {% data variables.product.product_location %} receba declarações criptografadas do IdP do SAML, selecione **Exigir declarações criptografadas**. Você deve garantir que seu IdP é compatível com declarações e que a criptografia e os métodos de transporte principais no console de gerenciamento correspondem aos valores configurados no seu IdP. Você também deve fornecer o certificado público de {% data variables.product.product_location %} ao seu IdP. Para obter mais informações, confira "[Como habilitar declarações criptografadas](/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions)". + ![Screenshot of option to enable option to respect the "administrator" attribute from the IdP to enable or disable administrative rights](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png) +{%- ifversion ghes > 3.3 %} +1. Optionally, to allow {% data variables.location.product_location %} to receive encrypted assertions from your SAML IdP, select **Require encrypted assertions**. You must ensure that your IdP supports encrypted assertions and that the encryption and key transport methods in the management console match the values configured on your IdP. You must also provide {% data variables.location.product_location %}'s public certificate to your IdP. For more information, see "[Enabling encrypted assertions](/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions)." - ![Captura de tela da caixa de seleção "Habilitar declarações criptografadas" na seção "Autenticação" do console de gerenciamento](/assets/images/help/saml/management-console-enable-encrypted-assertions.png) {%- endif %} -1. No campo **URL de logon**, digite o ponto de extremidade HTTP ou HTTPS do IdP para solicitações de logon único. Esse valor é fornecido pela configuração do IdP. Se o host só está disponível na sua rede interna, talvez seja necessário [configurar a {% data variables.product.product_location %} para usar servidores de nomes internos](/enterprise/admin/guides/installation/configuring-dns-nameservers/). + ![Screenshot of "Enable encrypted assertions" checkbox within management console's "Authentication" section](/assets/images/help/saml/management-console-enable-encrypted-assertions.png) +{%- endif %} +1. In the **Single sign-on URL** field, type the HTTP or HTTPS endpoint on your IdP for single sign-on requests. This value is provided by your IdP configuration. If the host is only available from your internal network, you may need to [configure {% data variables.location.product_location %} to use internal nameservers](/enterprise/admin/guides/installation/configuring-dns-nameservers/). - ![Captura de tela do campo de texto para a URL de acesso único](/assets/images/enterprise/management-console/saml-single-sign-url.png) -1. Opcionalmente, no campo **Emissor**, digite o nome do emissor do SAML. Fazer isso verifica a autenticidade das mensagens enviadas para {% data variables.product.product_location %}. + ![Screenshot of text field for single sign-on URL](/assets/images/enterprise/management-console/saml-single-sign-url.png) +1. Optionally, in the **Issuer** field, type your SAML issuer's name. This verifies the authenticity of messages sent to {% data variables.location.product_location %}. - ![Screenshot do campo de texto para a URL do emissor do SAML](/assets/images/enterprise/management-console/saml-issuer.png) -1. Nos menus suspensos **Método de Assinatura** e **Método de Hash**, escolha o algoritmo de hash usado pelo emissor do SAML para verificar a integridade das solicitações da {% data variables.product.product_location %}. Especifique o formato com o menu suspenso **Formato de Identificador de Nome**. + ![Screenshot of text field for SAML issuer URL](/assets/images/enterprise/management-console/saml-issuer.png) +1. In the **Signature Method** and **Digest Method** drop-down menus, choose the hashing algorithm used by your SAML issuer to verify the integrity of the requests from {% data variables.location.product_location %}. Specify the format with the **Name Identifier Format** drop-down menu. - ![Captura de tela dos menus suspensos para selecionar a assinatura e o método de resumo](/assets/images/enterprise/management-console/saml-method.png) -1. Em **Certificado de verificação**, clique em **Escolher Arquivo** e escolha um certificado para validar as respostas do SAML do IdP. + ![Screenshot of drop-down menus to select signature and digest method](/assets/images/enterprise/management-console/saml-method.png) +1. Under **Verification certificate**, click **Choose File** and choose a certificate to validate SAML responses from the IdP. - ![Captura de tela do botão para fazer o upload do certificado de validação do IdP](/assets/images/enterprise/management-console/saml-verification-cert.png) -1. Modifique os nomes do atributo SAML para corresponder ao IdP, se necessário, ou aceite os nomes padrão. + ![Screenshot of button for uploading validation certificate from IdP](/assets/images/enterprise/management-console/saml-verification-cert.png) +1. Modify the SAML attribute names to match your IdP if needed, or accept the default names. - ![Captura de tela dos campos para inserir atributos adicionais do SAML](/assets/images/enterprise/management-console/saml-attributes.png) + ![Screenshot of fields for entering additional SAML attributes](/assets/images/enterprise/management-console/saml-attributes.png) {% elsif ghae %} -## Habilitar o SAML SSO +## Enabling SAML SSO {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} -Os seguintes IdPs fornecem documentação sobre a configuração de do SAML SSO para {% data variables.product.product_name %}. Se seu IdP não estiver listado, entre em contato com seu IdP para solicitar suporte para {% data variables.product.product_name %}. +The following IdPs provide documentation about configuring SAML SSO for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}. - | IdP | Mais informações | + | IdP | More information | | :- | :- | - | Azure AD | "[Configurar a autenticação e o provisionamento para sua empresa usando o Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)" | -| Okta | "[Configurar autenticação e provisionamento para sua empresa usando o Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)" | + | Azure AD | "[Configuring authentication and provisioning for your enterprise using Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)" | +| Okta | "[Configuring authentication and provisioning for your enterprise using Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)" | -Durante a inicialização do {% data variables.product.product_name %}, você deve configurar o {% data variables.product.product_name %} como um SP (provedor de serviço) do SAML no seu IdP. Você deve inserir vários valores únicos no seu IdP para configurar {% data variables.product.product_name %} como um SP válido. Para obter mais informações, confira "[Referência de configuração do SAML](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-metadata)". +During initialization for {% data variables.product.product_name %}, you must configure {% data variables.product.product_name %} as a SAML service provider (SP) on your IdP. You must enter several unique values on your IdP to configure {% data variables.product.product_name %} as a valid SP. For more information, see "[SAML configuration reference](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-metadata)." -## Editar a configuração SAML SSO +## Editing the SAML SSO configuration -Se os detalhes para o seu IdP forem alterados, você deverá editar a configuração SAML SSO para o {% data variables.product.product_location %}. Por exemplo, se o certificado de seu IdP expirar, você poderá editar o valor para o certificado público. +If the details for your IdP change, you'll need to edit the SAML SSO configuration for {% data variables.location.product_location %}. For example, if the certificate for your IdP expires, you can edit the value for the public certificate. {% ifversion ghae %} {% note %} -**Observação**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} +**Note**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} {% endnote %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} -1. Em "logon único SAML", digite os novos detalhes para o seu IdP. - ![Campos de entrada de texto com detalhes do IdP para configuração do SSO do SAML para uma empresa](/assets/images/help/saml/ae-edit-idp-details.png) -1. Opcionalmente, clique em {% octicon "pencil" aria-label="The edit icon" %} para configurar uma nova assinatura ou método de resumo. - ![Ícone de edição para alterar a assinatura e o método de resumo](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest.png) +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +1. Under "SAML single sign-on", type the new details for your IdP. + ![Text entry fields with IdP details for SAML SSO configuration for an enterprise](/assets/images/help/saml/ae-edit-idp-details.png) +1. Optionally, click {% octicon "pencil" aria-label="The edit icon" %} to configure a new signature or digest method. + ![Edit icon for changing signature and digest method](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest.png) - - Use os menus suspensos e escolha a nova assinatura ou o método de resumo. - ![Menus suspensos para escolha de uma nova assinatura ou um método de resumo](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png) -1. Para garantir que as informações inseridas estão corretas, clique em **Testar configuração do SAML**. - ![Botão "Testar configuração do SAML"](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png) -1. Clique em **Salvar**. - ![Botão "Salvar" da configuração de SSO do SAML](/assets/images/help/saml/ae-edit-idp-details-save.png) -1. Opcionalmente, para provisionar e desprovisionar contas de usuário automaticamente para {% data variables.product.product_location %}, reconfigure o provisionamento de usuário com SCIM. Para obter mais informações, confira "[Como configurar o provisionamento de usuário para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". + - Use the drop-down menus and choose the new signature or digest method. + ![Drop-down menus for choosing a new signature or digest method](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png) +1. To ensure that the information you've entered is correct, click **Test SAML configuration**. + !["Test SAML configuration" button](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png) +1. Click **Save**. + !["Save" button for SAML SSO configuration](/assets/images/help/saml/ae-edit-idp-details-save.png) +1. Optionally, to automatically provision and deprovision user accounts for {% data variables.location.product_location %}, reconfigure user provisioning with SCIM. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." {% endif %} {% ifversion ghae %} -## Desabilitar SAML SSO +## Disabling SAML SSO {% warning %} -**Aviso**: se você desabilitar o SSO do SAML do {% data variables.product.product_location %}, os usuários sem sessões SSO do SAML existentes não poderão entrar no {% data variables.product.product_location %}. As sessões SAML SSO em {% data variables.product.product_location %} terminam após 24 horas. +**Warning**: If you disable SAML SSO for {% data variables.location.product_location %}, users without existing SAML SSO sessions cannot sign into {% data variables.location.product_location %}. SAML SSO sessions on {% data variables.location.product_location %} end after 24 hours. {% endwarning %} {% note %} -**Observação**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} +**Note**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} {% endnote %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} -1. Em "Logon único do SAML", desmarque **Habilitar autenticação SAML**. - ![Caixa de seleção para "Habilitar autenticação SAML"](/assets/images/help/saml/ae-saml-disabled.png) -1. Para desabilitar o SSO do SAML e exigir o logon com a conta de usuário interna que você criou durante a inicialização, clique em **Salvar**. - ![Botão "Salvar" da configuração de SSO do SAML](/assets/images/help/saml/ae-saml-disabled-save.png) +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +1. Under "SAML single sign-on", unselect **Enable SAML authentication**. + ![Checkbox for "Enable SAML authentication"](/assets/images/help/saml/ae-saml-disabled.png) +1. To disable SAML SSO and require signing in with the built-in user account you created during initialization, click **Save**. + !["Save" button for SAML SSO configuration](/assets/images/help/saml/ae-saml-disabled-save.png) {% endif %} @@ -227,10 +232,13 @@ Se os detalhes para o seu IdP forem alterados, você deverá editar a configura {% ifversion ghec or ghes %} -## Leitura adicional +## Further reading {%- ifversion ghec %} -- "[Gerenciar o logon único do SAML em sua organização](/organizations/managing-saml-single-sign-on-for-your-organization)" {%- endif %} {%- ifversion ghes %} -- "[Promover ou rebaixar um administrador do site](/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator)" {%- endif %} +- "[Managing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization)" +{%- endif %} +{%- ifversion ghes %} +- "[Promoting or demoting a site administrator](/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator)" +{%- endif %} {% endif %} diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-for-your-enterprise.md b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-for-your-enterprise.md index aa67114c34..0118676666 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Configurar o provisionamento do usuário para a sua empresa +title: Configuring user provisioning for your enterprise shortTitle: Configure user provisioning -intro: 'Você pode configurar o Sistema para Gerenciamento de Identidades entre Domínios (SCIM) para sua empresa, que automaticamente fornece contas de usuário em {% data variables.product.product_location %} quando você atribuir o aplicativo para {% data variables.product.product_location %} a um usuário no seu provedor de identidade (IdP).' +intro: 'You can configure System for Cross-domain Identity Management (SCIM) for your enterprise, which automatically provisions user accounts on {% data variables.location.product_location %} when you assign the application for {% data variables.location.product_location %} to a user on your identity provider (IdP).' permissions: 'Enterprise owners can configure user provisioning for an enterprise on {% data variables.product.product_name %}.' versions: ghae: '*' @@ -15,73 +15,71 @@ topics: redirect_from: - /admin/authentication/configuring-user-provisioning-for-your-enterprise - /admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-user-provisioning-for-your-enterprise -ms.openlocfilehash: c76cf3a3245b272fc61db68470e7a34796a89e42 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145093958' --- -## Sobre provisionamento de usuários para sua empresa +## About user provisioning for your enterprise -{% data reusables.saml.ae-uses-saml-sso %} Para obter mais informações, confira "[Como configurar o logon único do SAML para sua empresa](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)". +{% data reusables.saml.ae-uses-saml-sso %} For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)." -Você pode configurar o provisionamento de usuário com SCIM para criar ou suspender automaticamente contas de usuário e conceder acesso para {% data variables.product.product_name %} ao atribuir ou cancelar a atribuição do aplicativo em seu IdP. Para obter mais informações sobre o SCIM, confira [Sistema de Gerenciamento de Usuários entre Domínios: protocolo (RFC 7644)](https://tools.ietf.org/html/rfc7644) no site do IETF. +You can configure user provisioning with SCIM to automatically create or suspend user accounts and grant access for {% data variables.product.product_name %} when you assign or unassign the application on your IdP. For more information about SCIM, see [System for Cross-domain Identity Management: Protocol (RFC 7644)](https://tools.ietf.org/html/rfc7644) on the IETF website. -Se você não configurar o provisionamento de usuários com SCIM, seu IdP não se comunicará com {% data variables.product.product_name %} automaticamente quando você atribuir ou cancelar a atribuição do aplicativo a um usuário. Sem SCIM, {% data variables.product.product_name %} cria uma conta de usuário usando o provisionamento SAML Just-in-Time (JIT) na primeira vez que alguém navega para {% data variables.product.product_name %} e faz login autenticando por meio de seu IdP. +If you do not configure user provisioning with SCIM, your IdP will not communicate with {% data variables.product.product_name %} automatically when you assign or unassign the application to a user. Without SCIM, {% data variables.product.product_name %} creates a user account using SAML Just-in-Time (JIT) provisioning the first time someone navigates to {% data variables.product.product_name %} and signs in by authenticating through your IdP. -A configuração do provisionamento permite que o seu IdP se comunique com {% data variables.product.product_location %} quando você atribuir ou cancela a atribuição do aplicativo para {% data variables.product.product_name %} a um usuário no seu IdP. Ao atribuir o aplicativo, seu IdP pedirá que {% data variables.product.product_location %} crie uma conta e enviar um e-mail de integração para o usuário. Ao desatribuir o aplicativo, o seu IdP irá comunicar-se com {% data variables.product.product_name %} para invalidar quaisquer sessões de SAML e desabilitar a conta do integrante. +Configuring provisioning allows your IdP to communicate with {% data variables.location.product_location %} when you assign or unassign the application for {% data variables.product.product_name %} to a user on your IdP. When you assign the application, your IdP will prompt {% data variables.location.product_location %} to create an account and send an onboarding email to the user. When you unassign the application, your IdP will communicate with {% data variables.product.product_name %} to invalidate any SAML sessions and disable the member's account. -Para configurar o provisionamento para o seu negócio, você deve habilitar o provisionamento em {% data variables.product.product_name %} e, em seguida, instalar e configurar um aplicativo de provisionamento no seu IdP. +To configure provisioning for your enterprise, you must enable provisioning on {% data variables.product.product_name %}, then install and configure a provisioning application on your IdP. -O aplicativo de provisionamento no seu IdP comunica-se com {% data variables.product.product_name %} através da nossa API de SCIM para empresas. Para obter mais informações, confira "[Administração do GitHub Enterprise](/rest/reference/enterprise-admin#scim)" na documentação da API REST do {% data variables.product.prodname_dotcom %}. +The provisioning application on your IdP communicates with {% data variables.product.product_name %} via our SCIM API for enterprises. For more information, see "[GitHub Enterprise administration](/rest/reference/enterprise-admin#scim)" in the {% data variables.product.prodname_dotcom %} REST API documentation. -## Provedores de identidade compatíveis +## Supported identity providers -Os seguintes IdPs são compatíveis com SSO com {% data variables.product.prodname_ghe_managed %}: +The following IdPs are supported for SSO with {% data variables.product.prodname_ghe_managed %}: {% data reusables.saml.okta-ae-sso-beta %} {% data reusables.github-ae.saml-idp-table %} -Para IdPs compatíveis com o mapeamento de equipe, você pode atribuir ou desatribuir o aplicativo de {% data variables.product.product_name %} para grupos de usuários do seu IdP. Estes grupos são disponibilizados para os proprietários da organização e mantenedores de equipe em {% data variables.product.product_location %} para mapear para equipes de {% data variables.product.product_name %}. Para obter mais informações, confira "[Como mapear grupos do Okta para equipes](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)". +For IdPs that support team mapping, you can assign or unassign the application for {% data variables.product.product_name %} to groups of users in your IdP. These groups are then available to organization owners and team maintainers in {% data variables.location.product_location %} to map to {% data variables.product.product_name %} teams. For more information, see "[Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." -## Pré-requisitos +## Prerequisites -Para prover e desprover automaticamente o acesso a {% data variables.product.product_location %} a partir do seu IdP, primeiro você deve configurar o SSO de SAML ao inicializar {% data variables.product.product_name %}. Para obter mais informações, confira "[Como inicializar o {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)". +To automatically provision and deprovision access to {% data variables.location.product_location %} from your IdP, you must first configure SAML SSO when you initialize {% data variables.product.product_name %}. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)." -Você deve ter acesso administrativo no seu IdP para configurar o aplicativo para o provisionamento do usuário para {% data variables.product.product_name %}. +You must have administrative access on your IdP to configure the application for user provisioning for {% data variables.product.product_name %}. -## Habilitar provisionamento de usuários para a sua empresa +## Enabling user provisioning for your enterprise -1. Enquanto estiver conectado ao {% data variables.product.product_location %} como um proprietário da empresa, crie um token de acesso pessoal com o escopo **admin:enterprise**. Para obter mais informações, confira "[Como criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)". +1. While signed into {% data variables.location.product_location %} as an enterprise owner, create a {% data variables.product.pat_v1 %} with **admin:enterprise** scope. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." {% note %} - **Observações**: - - Para criar o token de acesso pessoal, recomendamos usar a conta para o primeiro proprietário da empresa criado durante a inicialização. Para obter mais informações, confira "[Como inicializar o {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)". - - Você precisará deste token de acesso pessoal para configurar o aplicativo para o SCIM no seu IdP. Armazene o token com segurança em um gerenciador de senhas até que você precise do token novamente posteriormente nestas instruções. + **Notes**: + - To create the {% data variables.product.pat_generic %}, we recommend using the account for the first enterprise owner that you created during initialization. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)." + - You'll need this {% data variables.product.pat_generic %} to configure the application for SCIM on your IdP. Store the token securely in a password manager until you need the token again later in these instructions. - {% endnote %} {% warning %} + {% endnote %} + {% warning %} - **Aviso**: se a conta de usuário do proprietário da empresa que cria o token de acesso pessoal for desativada ou desprovisionada, o IdP não provisionará nem desprovisionará automaticamente as contas de usuário da sua empresa. Outro proprietário da empresa deve criar um novo token de acesso pessoal e reconfigurar o provisionamento no IdP. + **Warning**: If the user account for the enterprise owner who creates the {% data variables.product.pat_generic %} is deactivated or deprovisioned, your IdP will no longer provision and deprovision user accounts for your enterprise automatically. Another enterprise owner must create a new {% data variables.product.pat_generic %} and reconfigure provisioning on the IdP. - {% endwarning %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} -1. Em "Provisionamento de Usuário do SCIM", selecione **Exigir provisionamento de usuário do SCIM**. - ![Caixa de seleção usada para "Exigir provisionamento de usuário do SCIM" nas configurações de segurança da empresa](/assets/images/help/enterprises/settings-require-scim-user-provisioning.png) -1. Clique em **Salvar**. - ![Botão Salvar em "Exigir provisionamento de usuário do SCIM" nas configurações de segurança da empresa](/assets/images/help/enterprises/settings-scim-save.png) -1. Configurar provisionamento de usuário no aplicativo para {% data variables.product.product_name %} no seu IdP. + {% endwarning %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +1. Under "SCIM User Provisioning", select **Require SCIM user provisioning**. + ![Checkbox for "Require SCIM user provisioning" within enterprise security settings](/assets/images/help/enterprises/settings-require-scim-user-provisioning.png) +1. Click **Save**. + ![Save button under "Require SCIM user provisioning" within enterprise security settings](/assets/images/help/enterprises/settings-scim-save.png) +1. Configure user provisioning in the application for {% data variables.product.product_name %} on your IdP. - Os seguintes IdPs fornecem documentação sobre configuração de provisionamento para {% data variables.product.product_name %}. Se seu IdP não estiver listado, entre em contato com seu IdP para solicitar suporte para {% data variables.product.product_name %}. + The following IdPs provide documentation about configuring provisioning for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}. - | IdP | Mais informações | + | IdP | More information | | :- | :- | - | Azure AD | [Tutorial: Configurar o {% data variables.product.prodname_ghe_managed %} para o provisionamento automático de usuário](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial) no Microsoft Docs. Para configurar o Azure AD para o {% data variables.product.prodname_ghe_managed %}, confira "[Como configurar a autenticação e o provisionamento para sua empresa usando o Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)".| -| Okta | (beta) Para configurar o Okta para o {% data variables.product.prodname_ghe_managed %}, confira "[Como configurar a autenticação e o provisionamento para sua empresa usando o Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)".| + | Azure AD | [Tutorial: Configure {% data variables.product.prodname_ghe_managed %} for automatic user provisioning](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial) in the Microsoft Docs. To configure Azure AD for {% data variables.product.prodname_ghe_managed %}, see "[Configuring authentication and provisioning for your enterprise using Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)."| +| Okta | (beta) To configure Okta for {% data variables.product.prodname_ghe_managed %}, see "[Configuring authentication and provisioning for your enterprise using Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)."| - O aplicativo no seu IdP exige dois valores para provisionar ou desprovisionar contas de usuário em {% data variables.product.product_location %}. + The application on your IdP requires two values to provision or deprovision user accounts on {% data variables.location.product_location %}. - | Valor | Outros nomes | Descrição | Exemplo | + | Value | Other names | Description | Example | | :- | :- | :- | :- | - | URL | URL do Locatário | URL para a API de provisionamento SCIM para a sua empresa em {% data variables.product.prodname_ghe_managed %} | {% data variables.product.api_url_pre %}/scim/v2 | - | Segredo compartilhado | Token de acesso pessoal, token secreto | Token para aplicativo no seu IdP para executar tarefas de provisionamento em nome do proprietário de uma empresa | Token de acesso pessoal que você criou no passo 1 | + | URL | Tenant URL | URL to the SCIM provisioning API for your enterprise on {% data variables.product.prodname_ghe_managed %} | {% data variables.product.api_url_pre %}/scim/v2 | + | Shared secret | {% data variables.product.pat_generic_caps %}, secret token | Token for application on your IdP to perform provisioning tasks on behalf of an enterprise owner | {% data variables.product.pat_generic_caps %} you created in step 1 | diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md index 2016da67ee..83a3c87b14 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md @@ -1,7 +1,7 @@ --- -title: Habilitando declarações criptografadas +title: Enabling encrypted assertions shortTitle: Enable encrypted assertions -intro: 'Você pode aprimorar a segurança do {% data variables.product.product_location %} com o SSO (logon único) do SAML criptografando as mensagens enviadas pelo IdP (provedor de identidade) SAML.' +intro: 'You can improve {% data variables.location.product_location %}''s security with SAML single sign-on (SSO) by encrypting the messages that your SAML identity provider (IdP) sends.' permissions: 'Site administrators can configure encrypted assertions for a {% data variables.product.product_name %} instance.' versions: ghes: '> 3.3' @@ -13,51 +13,48 @@ topics: - Identity - Security - SSO -ms.openlocfilehash: ecb60a4398993155fa7498f26e7628660e88e54a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147063775' --- -## Sobre declarações criptografadas -Se o seu IdP dá suporte a declarações criptografadas, você pode configurar asserções criptografadas no {% data variables.product.product_name %} para aumentar a segurança durante o processo de autenticação. +## About encrypted assertions -## Pré-requisitos +If your IdP support encryption of assertions, you can configure encrypted assertions on {% data variables.product.product_name %} for increased security during the authentication process. -Para habilitar declarações criptografadas para autenticação para {% data variables.product.product_name %}, você deve configurar a autenticação SAML e seu IdP deve dar suporte a declarações criptografadas. +## Prerequisites -## Habilitando declarações criptografadas +To enable encrypted assertions for authentication to {% data variables.product.product_name %}, you must configure SAML authentication, and your IdP must support encrypted assertions. -Para habilitar declarações criptografadas, você deve fornecer o certificado público de {% data variables.product.product_location %} ao seu IdP e definir as configurações de criptografia que correspondem ao seu IdP. +## Enabling encrypted assertions + +To enable encrypted assertions, you must provide {% data variables.location.product_location %}'s public certificate to your IdP, and configure encryption settings that match your IdP. {% note %} -**Observação**: {% data reusables.enterprise.test-in-staging %} +**Note**: {% data reusables.enterprise.test-in-staging %} {% endnote %} -1. Opcionalmente, habilite a depuração do SAML. A depuração do SAML registra entradas detalhadas no registro de autenticação de {% data variables.product.product_name %} e pode ajudar você a solucionar problemas com falha nas tentativas de autenticação. Para saber mais, confira "[Solução de problemas de autenticação SAML](/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication#configuring-saml-debugging)". -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.authentication %} -1. Selecione **Exigir declarações criptografadas**. +1. Optionally, enable SAML debugging. SAML debugging records verbose entries in {% data variables.product.product_name %}'s authentication log, and may help you troubleshoot failed authentication attempts. For more information, see "[Troubleshooting SAML authentication](/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication#configuring-saml-debugging)." +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.authentication %} +1. Select **Require encrypted assertions**. - ![Captura de tela da caixa de seleção "Habilitar declarações criptografadas" na seção "Autenticação" do console de gerenciamento](/assets/images/help/saml/management-console-enable-encrypted-assertions.png) -1. À direita do "Certificado de Criptografia", clique em **Baixar** para salvar uma cópia do certificado público da {% data variables.product.product_location %} no computador local. + ![Screenshot of "Enable encrypted assertions" checkbox within management console's "Authentication" section](/assets/images/help/saml/management-console-enable-encrypted-assertions.png) +1. To the right of "Encryption Certificate", click **Download** to save a copy of {% data variables.location.product_location %}'s public certificate on your local machine. - ![Captura de tela do botão "Baixar" do certificado público para declarações criptografadas](/assets/images/help/saml/management-console-encrypted-assertions-download-certificate.png) -1. Efetue o login no seu IdP do SAML como administrador. -1. No aplicativo para {% data variables.product.product_location %}, habilite as declarações criptografadas. - - Observe o método de criptografia e o método de transporte principal. - - Forneça o certificado público que você baixou na etapa 7. -1. Retorne ao console de gerenciamento em {% data variables.product.product_location %}. -1. À direita de "Método de criptografia", selecione o método de criptografia para seu IdP a partir da etapa 9. + ![Screenshot of "Download" button for public certificate for encrypted assertions](/assets/images/help/saml/management-console-encrypted-assertions-download-certificate.png) +1. Sign into your SAML IdP as an administrator. +1. In the application for {% data variables.location.product_location %}, enable encrypted assertions. + - Note the encryption method and key transport method. + - Provide the public certificate you downloaded in step 7. +1. Return to the management console on {% data variables.location.product_location %}. +1. To the right of "Encryption Method", select the encryption method for your IdP from step 9. - ![Captura de tela de "Método de Criptografia" para declarações criptografadas](/assets/images/help/saml/management-console-encrypted-assertions-encryption-method.png) -1. À direita do "Principal método de transporte", selecione o principal método de transporte para seu IdP da etapa 9. + ![Screenshot of "Encryption Method" for encrypted assertions](/assets/images/help/saml/management-console-encrypted-assertions-encryption-method.png) +1. To the right of "Key Transport Method", select the key transport method for your IdP from step 9. - ![Captura de tela de "Principal Método de Transporte" para declarações criptografadas](/assets/images/help/saml/management-console-encrypted-assertions-key-transport-method.png) -1. Clique em **Salvar alterações**. + ![Screenshot of "Key Transport Method" for encrypted assertions](/assets/images/help/saml/management-console-encrypted-assertions-key-transport-method.png) +1. Click **Save settings**. {% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %} -Se você habilitou a depuração do SAML para testar a autenticação com declarações criptografadas, desabilite a depuração do SAML quando terminar o teste. Para saber mais, confira "[Solução de problemas de autenticação SAML](/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication#configuring-saml-debugging)". +If you enabled SAML debugging to test authentication with encrypted assertions, disable SAML debugging when you're done testing. For more information, see "[Troubleshooting SAML authentication](/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication#configuring-saml-debugging)." diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/index.md b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/index.md index dbd066eedc..9dfcee6f4c 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/index.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/index.md @@ -1,7 +1,7 @@ --- -title: Usar SAML para IAM empresarial +title: Using SAML for enterprise IAM shortTitle: SAML for enterprise IAM -intro: 'Você pode gerenciar centralmente {% ifversion ghes or ghae %}contas e {% endif %}acesso a {% ifversion ghes %}{% data variables.product.product_location %}{% elsif ghae %}sua empresa{% elsif ghec %}recursos da sua empresa{% endif %} com logon único (SSO) SAML{% ifversion ghec or ghae %} e Sistema de Gerenciamento de Usuários entre Domínios (SCIM){% endif %}.' +intro: 'You can centrally manage {% ifversion ghes or ghae %}accounts and {% endif %}access to {% ifversion ghes %}{% data variables.location.product_location %}{% elsif ghae %}your enterprise{% elsif ghec %}your enterprise''s resources{% endif %} with SAML single sign-on (SSO){% ifversion ghec or ghae %} and System for Cross-domain Identity Management (SCIM){% endif %}.' versions: ghec: '*' ghes: '*' @@ -32,11 +32,6 @@ children: - /updating-a-users-saml-nameid - /switching-your-saml-configuration-from-an-organization-to-an-enterprise-account - /troubleshooting-saml-authentication -ms.openlocfilehash: 4258d753035ce174cb0f45f186b2b99c9ce1752b -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145095871' --- + {% data reusables.enterprise-accounts.emu-saml-note %} diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md index d17cfa8c89..a7575e8ea9 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md @@ -1,7 +1,7 @@ --- title: SAML configuration reference shortTitle: SAML reference -intro: 'You can see SAML metadata for {% ifversion ghec %}your organization or enterprise on {% data variables.product.product_name %}{% elsif ghes %}{% data variables.product.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %}, and you can learn more about available SAML attributes and response requirements.' +intro: 'You can see SAML metadata for {% ifversion ghec %}your organization or enterprise on {% data variables.product.product_name %}{% elsif ghes %}{% data variables.location.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %}, and you can learn more about available SAML attributes and response requirements.' versions: ghec: '*' ghes: '*' @@ -17,7 +17,7 @@ topics: ## About SAML configuration -To use SAML single sign-on (SSO) for authentication to {% data variables.product.product_name %}, you must configure both your external SAML identity provider (IdP) and {% ifversion ghes %}{% data variables.product.product_location %}{% elsif ghec %}your enterprise or organization on {% data variables.product.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %}. In a SAML configuration, {% data variables.product.product_name %} functions as a SAML service provider (SP). +To use SAML single sign-on (SSO) for authentication to {% data variables.product.product_name %}, you must configure both your external SAML identity provider (IdP) and {% ifversion ghes %}{% data variables.location.product_location %}{% elsif ghec %}your enterprise or organization on {% data variables.location.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %}. In a SAML configuration, {% data variables.product.product_name %} functions as a SAML service provider (SP). You must enter unique values from your SAML IdP when configuring SAML SSO for {% data variables.product.product_name %}, and you must also enter unique values from {% data variables.product.product_name %} on your IdP. For more information about the configuration of SAML SSO for {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise){% ifversion ghes or ghae %}{% elsif ghec %}" or "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization){% endif %}." @@ -31,27 +31,27 @@ The SP metadata for {% data variables.product.product_name %} is available for e You can configure SAML SSO for an individual organization in your enterprise. You can also configure SAML SSO for an organization if you use an individual organization on {% data variables.product.product_name %} and do not use an enterprise account. For more information, see "[Managing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization)." -The SP metadata for an organization on {% data variables.product.product_location %} is available at `https://github.com/orgs/ORGANIZATION/saml/metadata`, where **ORGANIZATION** is the name of your organization on {% data variables.product.product_location %}. +The SP metadata for an organization on {% data variables.location.product_location %} is available at `https://github.com/orgs/ORGANIZATION/saml/metadata`, where **ORGANIZATION** is the name of your organization on {% data variables.location.product_location %}. | Value | Other names | Description | Example | | :- | :- | :- | :- | -| SP Entity ID | SP URL, audience restriction | The top-level URL for your organization on {% data variables.product.product_location %} | `https://github.com/orgs/ORGANIZATION` | +| SP Entity ID | SP URL, audience restriction | The top-level URL for your organization on {% data variables.location.product_location %} | `https://github.com/orgs/ORGANIZATION` | | SP Assertion Consumer Service (ACS) URL | Reply, recipient, or destination URL | URL where IdP sends SAML responses | `https://github.com/orgs/ORGANIZATION/saml/consume` | | SP Single Sign-On (SSO) URL | | URL where IdP begins SSO | `https://github.com/orgs/ORGANIZATION/saml/sso` | ### Enterprises -The SP metadata for an enterprise on {% data variables.product.product_location %} is available at `https://github.com/enterprises/ENTERPRISE/saml/metadata`, where **ENTERPRISE** is the name of your enterprise on {% data variables.product.product_location %}. +The SP metadata for an enterprise on {% data variables.location.product_location %} is available at `https://github.com/enterprises/ENTERPRISE/saml/metadata`, where **ENTERPRISE** is the name of your enterprise on {% data variables.location.product_location %}. | Value | Other names | Description | Example | | :- | :- | :- | :- | -| SP Entity ID | SP URL, audience restriction | The top-level URL for your enterprise on {% data variables.product.product_location %} | `https://github.com/enterprises/ENTERPRISE` | +| SP Entity ID | SP URL, audience restriction | The top-level URL for your enterprise on {% data variables.location.product_location %} | `https://github.com/enterprises/ENTERPRISE` | | SP Assertion Consumer Service (ACS) URL | Reply, recipient, or destination URL | URL where IdP sends SAML responses | `https://github.com/enterprises/ENTERPRISE/saml/consume` | | SP Single Sign-On (SSO) URL | | URL where IdP begins SSO | `https://github.com/enterprises/ENTERPRISE/saml/sso` | {% elsif ghes %} -The SP metadata for {% data variables.product.product_location %} is available at `http(s)://HOSTNAME/saml/metadata`, where **HOSTNAME** is the hostname for your instance. {% data variables.product.product_name %} uses the `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST` binding. +The SP metadata for {% data variables.location.product_location %} is available at `http(s)://HOSTNAME/saml/metadata`, where **HOSTNAME** is the hostname for your instance. {% data variables.product.product_name %} uses the `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST` binding. | Value | Other names | Description | Example | | :- | :- | :- | :- | @@ -78,10 +78,10 @@ The following SAML attributes are available for {% data variables.product.produc | Name | Required? | Description | | :- | :- | :- | | `NameID` | Yes | A persistent user identifier. Any persistent name identifier format may be used. {% ifversion ghec %}If you use an enterprise with {% data variables.product.prodname_emus %}, {% endif %}{% data variables.product.product_name %} will normalize the `NameID` element to use as a username unless one of the alternative assertions is provided. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."

{% note %}**Note:** It's important to use a human-readable, persistent identifier. Using a transient identifier format like `urn:oasis:names:tc:SAML:2.0:nameid-format:transient` will result in re-linking of accounts on every sign-in, which can be detrimental to authorization management.{% endnote %} | -| `SessionNotOnOrAfter` | No | The date that {% data variables.product.product_name %} invalidates the associated session. After invalidation, the person must authenticate once again to access {% ifversion ghec or ghae %}your enterprise's resources{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. For more information, see "[Session duration and timeout](#session-duration-and-timeout)." | +| `SessionNotOnOrAfter` | No | The date that {% data variables.product.product_name %} invalidates the associated session. After invalidation, the person must authenticate once again to access {% ifversion ghec or ghae %}your enterprise's resources{% elsif ghes %}{% data variables.location.product_location %}{% endif %}. For more information, see "[Session duration and timeout](#session-duration-and-timeout)." | {%- ifversion ghes or ghae %} | `administrator` | No | When the value is `true`, {% data variables.product.product_name %} will automatically promote the user to be a {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %}. Setting this attribute to anything but `true` will result in demotion, as long as the value is not blank. Omitting this attribute or leaving the value blank will not change the role of the user. | -| `username` | No | The username for {% data variables.product.product_location %}. | +| `username` | No | The username for {% data variables.location.product_location %}. | {%- endif %} | `full_name` | No | {% ifversion ghec %}If you configure SAML SSO for an enterprise and you use {% data variables.product.prodname_emus %}, the{% else %}The{% endif %} full name of the user to display on the user's profile page. | | `emails` | No | The email addresses for the user.{% ifversion ghes or ghae %} You can specify more than one address.{% endif %}{% ifversion ghec or ghes %} If you sync license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_github_connect %} uses `emails` to identify unique users across products. For more information, see "[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."{% endif %} | @@ -102,7 +102,7 @@ To specify more than one value for an attribute, use multiple `` element on the root response document and match the ACS URL only when the root response document is signed. If your IdP signs the assertion, {% data variables.product.product_name %} will ignore the assertion. -- Your IdP must always provide the `` element as part of the `` element. The value must match your `EntityId` for {% data variables.product.product_name %}.{% ifversion ghes or ghae %} This value is the URL where you access {% data variables.product.product_location %}, such as {% ifversion ghes %}`http(s)://HOSTNAME`{% elsif ghae %}`https://SUBDOMAIN.githubenterprise.com`, `https://SUBDOMAIN.github.us`, or `https://SUBDOMAIN.ghe.com`{% endif %}.{% endif %} +- Your IdP must always provide the `` element as part of the `` element. The value must match your `EntityId` for {% data variables.product.product_name %}.{% ifversion ghes or ghae %} This value is the URL where you access {% data variables.location.product_location %}, such as {% ifversion ghes %}`http(s)://HOSTNAME`{% elsif ghae %}`https://SUBDOMAIN.githubenterprise.com`, `https://SUBDOMAIN.github.us`, or `https://SUBDOMAIN.ghe.com`{% endif %}.{% endif %} {%- ifversion ghec %} - If you configure SAML for an organization, this value is `https://github.com/orgs/ORGANIZATION`. @@ -132,7 +132,7 @@ To specify more than one value for an attribute, use multiple `ENCODED OUTPUT +$ base64 --decode ENCODED_OUTPUT ``` -## Erro: "Outro usuário já possui a conta" +## Error: "Another user already owns the account" -Quando um usuário entra no {% data variables.product.product_location %} pela primeira vez com a autenticação SAML, o {% data variables.product.product_name %} cria uma conta de usuário na instância e mapeia a `NameID` do SAML para a conta. +When a user signs into {% data variables.location.product_location %} for the first time with SAML authentication, {% data variables.product.product_name %} creates a user account on the instance and maps the SAML `NameID` to the account. -Quando o usuário se conecta novamente, o {% data variables.product.prodname_ghe_server %} compara o mapeamento da `NameID` da conta com a resposta do IdP. Se a `NameID` na resposta do IdP não corresponder mais à `NameID` esperada pelo {% data variables.product.product_name %} para o usuário, ocorrerá uma falha na entrada. O usuário receberá a seguinte mensagem. +When the user signs in again, {% data variables.product.prodname_ghe_server %} compares the account's `NameID` mapping to the IdP's response. If the `NameID` in the IdP's response no longer matches the `NameID` that {% data variables.product.product_name %} expects for the user, the sign-in will fail. The user will see the following message. -> Outro usuário já possui a conta. Solicite ao administrador que verifique o registro de autenticação. +> Another user already owns the account. Please have your administrator check the authentication log. -De modo geral, a mensagem indica que o nome de usuário ou endereço de email da pessoa foi alterado no IdP. Verifique se o mapeamento da `NameID` da conta do usuário no {% data variables.product.prodname_ghe_server %} corresponde à `NameID` do usuário no IdP. Para obter mais informações, confira "[Como atualizar a `NameID` do SAML de um usuário](/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid)". +The message typically indicates that the person's username or email address has changed on the IdP. Ensure that the `NameID` mapping for the user account on {% data variables.product.prodname_ghe_server %} matches the user's `NameID` on your IdP. For more information, see "[Updating a user's SAML `NameID`](/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid)." -## Se a resposta SAML não estiver assinada ou se a assinatura não corresponder ao conteúdo, o log de autenticação mostrará a seguinte mensagem de erro: +## Error: Recipient in SAML response was blank or not valid -Se o `Recipient` não corresponder à URL do ACS na {% data variables.product.product_location %}, uma das duas mensagens de erro a seguir será exibido no log de autenticação quando um usuário tentar se autenticar. +If the `Recipient` does not match the ACS URL for {% data variables.location.product_location %}, one of the following two error messages will appear in the authentication log when a user attempts to authenticate. ``` Recipient in the SAML response must not be blank. @@ -84,29 +81,31 @@ Recipient in the SAML response must not be blank. Recipient in the SAML response was not valid. ``` -Lembre-se de definir o valor de `Recipient` no IdP como a URL completa do ACS da {% data variables.product.product_location %}. Por exemplo, `https://ghe.corp.example.com/saml/consume`. +Ensure that you set the value for `Recipient` on your IdP to the full ACS URL for {% data variables.location.product_location %}. For example, `https://ghe.corp.example.com/saml/consume`. -## Erro: "Resposta do SAML não foi assinada ou foi modificada" +## Error: "SAML Response is not signed or has been modified" -Se seu IdP não assinar a resposta do SAML ou a assinatura não corresponder ao conteúdo, será exibida a seguinte mensagem de erro no registro de autenticação. +If your IdP does not sign the SAML response, or the signature does not match the contents, the following error message will appear in the authentication log. ``` SAML Response is not signed or has been modified. ``` -Verifique se você configurou as declarações assinadas para o aplicativo do {% data variables.product.product_name %} no seu IdP. +Ensure that you configure signed assertions for the {% data variables.product.product_name %} application on your IdP. -## Erro: "Audiência é inválida" ou "Nenhuma declaração encontrada" +## Error: "Audience is invalid" or "No assertion found" -Se a resposta do IdP tiver um valor ausente ou incorreto para `Audience`, a mensagem de erro a seguir será exibida no log de autenticação. +If the IdP's response has a missing or incorrect value for `Audience`, the following error message will appear in the authentication log. ``` Audience is invalid. Audience attribute does not match https://YOUR-INSTANCE-URL ``` -Lembre-se de definir o valor de `Audience` no IdP como a `EntityId` do {% data variables.product.product_location %}, que é a URL completa da sua instância. Por exemplo, `https://ghe.corp.example.com`. +Ensure that you set the value for `Audience` on your IdP to the `EntityId` for {% data variables.location.product_location %}, which is the full URL to your instance. For example, `https://ghe.corp.example.com`. {% endif %} {% data reusables.saml.current-time-earlier-than-notbefore-condition %} -{% ifversion ghec %} {% data reusables.saml.authentication-loop %} {% endif %} +{% ifversion ghec %} +{% data reusables.saml.authentication-loop %} +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md index 4b4c150c9f..65bdad9b8c 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md @@ -1,7 +1,7 @@ --- -title: Como atualizar a NameID do SAML de um usuário +title: Updating a user's SAML NameID shortTitle: Update SAML NameID -intro: 'Quando um `NameID` da conta muda em seu provedor de identidade (IdP) e a pessoa não puder mais {% ifversion ghes or ghae %}entrar no {% data variables.product.product_location %}{% elsif ghec %}e autenticar para acessar os recursos da sua empresa{% endif %}, você deverá {% ifversion ghec %}entrar em contato com o Suporte do {% data variables.product.company_short %} ou revogar a identidade vinculada da pessoa{% elsif ghes %}atualizar o mapeamento do `NameID` no {% data variables.product.product_location %}{% elsif ghae %}contatar o Suporte do {% data variables.product.company_short %}{% endif %}.' +intro: 'When an account''s `NameID` changes on your identity provider (IdP) and the person can no longer {% ifversion ghes or ghae %}sign into {% data variables.location.product_location %}{% elsif ghec %}authenticate to access your enterprise''s resources{% endif %}, you must {% ifversion ghec %}either contact {% data variables.product.company_short %} Support or revoke the person''s linked identity{% elsif ghes %}update the `NameID` mapping on {% data variables.location.product_location %}{% elsif ghae %}contact {% data variables.product.company_short %} Support{% endif %}.' versions: ghes: '*' type: how_to @@ -11,29 +11,25 @@ topics: - Enterprise - Identity - SSO -ms.openlocfilehash: 7a151143219fc0885861beedb69a2608983c5588 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717898' --- -## Sobre as atualizações da `NameID` do SAML dos usuários -Em algumas situações, pode ser necessário atualizar valores associados à conta de uma pessoa no IdP do SAML. Se esse identificador também for o `NameID` que você usa para autenticação no {% data variables.product.product_name %}, você deverá atualizar o mapeamento `NameID` em sua instância para que a pessoa continue a se autenticar com êxito. Para obter mais informações, confira "[Considerações de nome de usuário para autenticação externa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)". +## About updates to users' SAML `NameID` -## Como atualizar a `NameID` do SAML de um usuário +In some situations, you may need to update values associated with a person's account on your SAML IdP. If that identifier is also the `NameID` that you use for authentication on {% data variables.product.product_name %}, you must update the `NameID` mapping on your instance so the person can continue to authenticate successfully. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)." -Proprietários da empresa podem atualizar o `NameID` do SAML de um usuário em uma instância do {% data variables.product.product_name %}. +## Updating a user's SAML `NameID` + +Enterprise owners can update a user's SAML `NameID` on a {% data variables.product.product_name %} instance. {% data reusables.enterprise_site_admin_settings.access-settings %} -2. Na barra lateral esquerda, clique em **Todos os usuários**. - ![Barra lateral "Todos os usuários" nas configurações de administrador do site](/assets/images/enterprise/site-admin-settings/all-users.png) -3. Na lista de usuários, clique no nome de usuário para o qual deseja atualizar o mapeamento da `NameID`. - ![Nome de usuário na lista de contas de usuário da instância](/assets/images/enterprise/site-admin-settings/all-users-click-username.png) {% data reusables.enterprise_site_admin_settings.security-tab %} -5. À direita de "Atualizar NameID do SAML", clique em **Editar**. - ![Botão "Editar" em "Autenticação SAML" e à direita de "Atualizar NameID do SAML"](/assets/images/enterprise/site-admin-settings/update-saml-nameid-edit.png) -6. No campo "NameID", digite a nova `NameID` para o usuário. - ![Campo "NameID" na caixa de diálogo modal com a NameID digitada](/assets/images/enterprise/site-admin-settings/update-saml-nameid-field-in-modal.png) -7. Clique em **Atualizar NameID**. - ![Botão "Atualizar NameID" com o valor da NameID atualizada na caixa de diálogo modal](/assets/images/enterprise/site-admin-settings/update-saml-nameid-update.png) +2. In the left sidebar, click **All users**. + !["All users" sidebar item in site administrator settings](/assets/images/enterprise/site-admin-settings/all-users.png) +3. In the list of users, click the username you'd like to update the `NameID` mapping for. + ![Username in list of instance user accounts](/assets/images/enterprise/site-admin-settings/all-users-click-username.png) +{% data reusables.enterprise_site_admin_settings.security-tab %} +5. To the right of "Update SAML NameID", click **Edit** . + !["Edit" button under "SAML authentication" and to the right of "Update SAML NameID"](/assets/images/enterprise/site-admin-settings/update-saml-nameid-edit.png) +6. In the "NameID" field, type the new `NameID` for the user. + !["NameID" field in modal dialog with NameID typed](/assets/images/enterprise/site-admin-settings/update-saml-nameid-field-in-modal.png) +7. Click **Update NameID**. + !["Update NameID" button under updated NameID value within modal](/assets/images/enterprise/site-admin-settings/update-saml-nameid-update.png) diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md index b27accdeff..e45d5484e8 100644 --- a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md +++ b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md @@ -1,6 +1,6 @@ --- -title: Instalar o GitHub Enterprise Server no AWS -intro: 'Para instalar o {% data variables.product.prodname_ghe_server %} no Amazon Web Services (AWS), você deve iniciar uma instância do Amazon Elastic Compute Cloud (EC2) e, em seguida, criar e vincular um volume de dados separado do Amazon Elastic Block Store (EBS).' +title: Installing GitHub Enterprise Server on AWS +intro: 'To install {% data variables.product.prodname_ghe_server %} on Amazon Web Services (AWS), you must launch an Amazon Elastic Compute Cloud (EC2) instance and create and attach a separate Amazon Elastic Block Store (EBS) data volume.' redirect_from: - /enterprise/admin/guides/installation/installing-github-enterprise-on-aws - /enterprise/admin/installation/installing-github-enterprise-server-on-aws @@ -14,136 +14,133 @@ topics: - Infrastructure - Set up shortTitle: Install on AWS -ms.openlocfilehash: f91f2337cc13690d0476c836a15ec72a5c0685cb -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147875569' --- -## Pré-requisitos +## Prerequisites - {% data reusables.enterprise_installation.software-license %} -- Você deve ter uma conta do AWS que possa iniciar instâncias do EC2 e criar volumes EBS. Para obter mais informações, confira o [site da Amazon Web Services](https://aws.amazon.com/). -- A maioria das ações necessárias para iniciar o {% data variables.product.product_location %} também pode ser executada por meio do console de gerenciamento da AWS. No entanto, é recomendável instalar a interface da linha de comando (CLI) do AWS para a configuração inicial. Veja abaixo alguns exemplos de uso da CLI do AWS. Para obter mais informações, confira os guias da Amazon "[Como trabalhar com o Console de Gerenciamento da AWS](http://docs.aws.amazon.com/awsconsolehelpdocs/latest/gsg/getting-started.html)" e "[O que é a interface de linha de comando da AWS](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html)". +- You must have an AWS account capable of launching EC2 instances and creating EBS volumes. For more information, see the [Amazon Web Services website](https://aws.amazon.com/). +- Most actions needed to launch {% data variables.location.product_location %} may also be performed using the AWS management console. However, we recommend installing the AWS command line interface (CLI) for initial setup. Examples using the AWS CLI are included below. For more information, see Amazon's guides "[Working with the AWS Management Console](http://docs.aws.amazon.com/awsconsolehelpdocs/latest/gsg/getting-started.html)" and "[What is the AWS Command Line Interface](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html)." {% note %} -**Observação:** no momento, o {% data variables.product.prodname_ghe_server %} não dá suporte ao uso da API de Metadados do Amazon IDMSv2. +**Note:** At this time {% data variables.product.prodname_ghe_server %} does not support the use of the Amazon IDMSv2 Metadata API. {% endnote %} -Para usar este guia, você deve conhecer os seguintes conceitos do AWS: +This guide assumes you are familiar with the following AWS concepts: - - [Como iniciar instâncias do EC2](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/LaunchingAndUsingInstances.html) - - [Gerenciar volumes do EBS](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html) - - [Como usar grupos de segurança](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html) (para gerenciar o acesso à rede na sua instância) - - [EIP (Endereços IP elásticos)](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html) (altamente recomendado para ambientes de produção) - - [EC2 e nuvem virtual privada](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html) (se você pretende iniciá-la em uma nuvem virtual privada) - - [Preços da AWS](https://aws.amazon.com/pricing/) (para calcular e gerenciar os custos) + - [Launching EC2 Instances](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/LaunchingAndUsingInstances.html) + - [Managing EBS Volumes](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html) + - [Using Security Groups](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html) (For managing network access to your instance) + - [Elastic IP Addresses (EIP)](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html) (Strongly recommended for production environments) + - [EC2 and Virtual Private Cloud](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html) (If you plan to launch into a Virtual Private Cloud) + - [AWS Pricing](https://aws.amazon.com/pricing/) (For calculating and managing costs) -Para ter uma visão geral de arquitetura, confira o "[Diagrama de Arquitetura da AWS para implantação do GitHub Enterprise Server](/assets/images/installing-github-enterprise-server-on-aws.png)". +For an architectural overview, see the "[AWS Architecture Diagram for Deploying GitHub Enterprise Server](/assets/images/installing-github-enterprise-server-on-aws.png)". -Este guia recomenda o princípio do menor privilégio ao configurar {% data variables.product.product_location %} no AWS. Para obter mais informações, veja a [documentação do IAM (Gerenciamento de Identidades e Acesso) da AWS](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege). +This guide recommends the principle of least privilege when setting up {% data variables.location.product_location %} on AWS. For more information, refer to the [AWS Identity and Access Management (IAM) documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege). -## Considerações sobre hardware +## Hardware considerations {% data reusables.enterprise_installation.hardware-considerations-all-platforms %} -## Determinar o tipo de instância +## Determining the instance type -Antes de lançar {% data variables.product.product_location %} no AWS, você deverá determinar o tipo de máquina que melhor se adequa às necessidades da sua organização. Para revisar os requisitos mínimos do {% data variables.product.product_name %}, confira "[Requisitos mínimos](#minimum-requirements)". +Before launching {% data variables.location.product_location %} on AWS, you'll need to determine the machine type that best fits the needs of your organization. To review the minimum requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)." {% data reusables.enterprise_installation.warning-on-scaling %} {% data reusables.enterprise_installation.aws-instance-recommendation %} -## Selecionar a AMI do {% data variables.product.prodname_ghe_server %} +## Selecting the {% data variables.product.prodname_ghe_server %} AMI -É possível selecionar uma Amazon Machine Image (AMI) para o {% data variables.product.prodname_ghe_server %} usando o portal do {% data variables.product.prodname_ghe_server %} na CLI do AWS. +You can select an Amazon Machine Image (AMI) for {% data variables.product.prodname_ghe_server %} using the {% data variables.product.prodname_ghe_server %} portal or the AWS CLI. -As AMIs para o {% data variables.product.prodname_ghe_server %} estão disponíveis na região (EUA-Leste e EUA-Oeste) do AWS GovCloud. Com isso, os clientes dos EUA com requisitos regulamentares específicos podem executar o {% data variables.product.prodname_ghe_server %} em um ambiente em nuvem de conformidade federal. Para obter mais informações sobre a conformidade da AWS com os padrões federais e outros, confira a [página do GovCloud (US) da AWS](http://aws.amazon.com/govcloud-us/) e a [página de conformidade da AWS](https://aws.amazon.com/compliance/). +AMIs for {% data variables.product.prodname_ghe_server %} are available in the AWS GovCloud (US-East and US-West) region. This allows US customers with specific regulatory requirements to run {% data variables.product.prodname_ghe_server %} in a federally compliant cloud environment. For more information on AWS's compliance with federal and other standards, see [AWS's GovCloud (US) page](http://aws.amazon.com/govcloud-us/) and [AWS's compliance page](https://aws.amazon.com/compliance/). -### Usar o portal do {% data variables.product.prodname_ghe_server %} para selecionar uma AMI +### Using the {% data variables.product.prodname_ghe_server %} portal to select an AMI {% data reusables.enterprise_installation.download-appliance %} -3. Em "{% data variables.product.prodname_dotcom %} na Nuvem", selecione o menu suspenso "Selecionar sua plataforma" e clique na **Amazon Web Services**. -4. Escolha o menu suspenso "Selecionar sua região da AWS" e clique na região desejada. -5. Anote a ID da AMI. +3. Under "{% data variables.product.prodname_dotcom %} in the Cloud", select the "Select your platform" dropdown menu, and click **Amazon Web Services**. +4. Select the "Select your AWS region" drop-down menu, and click your desired region. +5. Take note of the AMI ID that is displayed. -### Usar a CLI do AWS para selecionar uma AMI +### Using the AWS CLI to select an AMI -1. Usando a CLI da AWS, obtenha uma lista de imagens do {% data variables.product.prodname_ghe_server %} publicadas pelas IDs do proprietário da AWS do {% data variables.product.prodname_dotcom %} (`025577942450` para GovCloud e `895557238572` para outras regiões). Para obter mais informações, confira "[describe-images](http://docs.aws.amazon.com/cli/latest/reference/ec2/describe-images.html)" na documentação da AWS. +1. Using the AWS CLI, get a list of {% data variables.product.prodname_ghe_server %} images published by {% data variables.product.prodname_dotcom %}'s AWS owner IDs (`025577942450` for GovCloud, and `895557238572` for other regions). For more information, see "[describe-images](http://docs.aws.amazon.com/cli/latest/reference/ec2/describe-images.html)" in the AWS documentation. ```shell aws ec2 describe-images \ - --owners OWNER ID \ + --owners OWNER_ID \ --query 'sort_by(Images,&Name)[*].{Name:Name,ImageID:ImageId}' \ --output=text ``` -2. Anote a ID da AMI para a imagem mais recente do {% data variables.product.prodname_ghe_server %}. +2. Take note of the AMI ID for the latest {% data variables.product.prodname_ghe_server %} image. -## Criação de um grupo de segurança +## Creating a security group -Se estiver configurando a AMI pela primeira vez, você terá que criar um grupo de segurança e adicionar uma nova regra de grupo de segurança para cada porta na tabela abaixo. Para obter mais informações, confira o guia da AWS "[Como usar grupos de segurança](http://docs.aws.amazon.com/cli/latest/userguide/cli-ec2-sg.html)". +If you're setting up your AMI for the first time, you will need to create a security group and add a new security group rule for each port in the table below. For more information, see the AWS guide "[Using Security Groups](http://docs.aws.amazon.com/cli/latest/userguide/cli-ec2-sg.html)." -1. Usando a CLI do AWS, crie um grupo de segurança. Para obter mais informações, confira "[create-security-group](http://docs.aws.amazon.com/cli/latest/reference/ec2/create-security-group.html)" na documentação da AWS. +1. Using the AWS CLI, create a new security group. For more information, see "[create-security-group](http://docs.aws.amazon.com/cli/latest/reference/ec2/create-security-group.html)" in the AWS documentation. ```shell - $ aws ec2 create-security-group --group-name SECURITY_GROUP_NAME --description "SECURITY GROUP DESCRIPTION" + $ aws ec2 create-security-group --group-name SECURITY_GROUP_NAME --description "SECURITY GROUP DESCRIPTION" ``` -2. Anote a ID do grupo de segurança (`sg-xxxxxxxx`) do grupo de segurança recém-criado. +2. Take note of the security group ID (`sg-xxxxxxxx`) of your newly created security group. -3. Crie uma regra de grupo de segurança para cada porta da tabela abaixo. Para obter mais informações, confira "[authorize-security-group-ingress](http://docs.aws.amazon.com/cli/latest/reference/ec2/authorize-security-group-ingress.html)" na documentação da AWS. +3. Create a security group rule for each of the ports in the table below. For more information, see "[authorize-security-group-ingress](http://docs.aws.amazon.com/cli/latest/reference/ec2/authorize-security-group-ingress.html)" in the AWS documentation. ```shell - $ aws ec2 authorize-security-group-ingress --group-id SECURITY_GROUP_ID --protocol PROTOCOL --port PORT_NUMBER --cidr SOURCE IP RANGE + $ aws ec2 authorize-security-group-ingress --group-id SECURITY_GROUP_ID --protocol PROTOCOL --port PORT_NUMBER --cidr SOURCE IP RANGE ``` - Esta tabela identifica o uso de cada porta. + This table identifies what each port is used for. {% data reusables.enterprise_installation.necessary_ports %} -## Criar a instância do {% data variables.product.prodname_ghe_server %} +## Creating the {% data variables.product.prodname_ghe_server %} instance -Para criar a instância, você deve iniciar uma instância EC2 com sua AMI do {% data variables.product.prodname_ghe_server %} e vincular um volume de armazenamento adicional aos dados da sua instância. Para obter mais informações, confira "[Considerações sobre hardware](#hardware-considerations)". +To create the instance, you'll need to launch an EC2 instance with your {% data variables.product.prodname_ghe_server %} AMI and attach an additional storage volume for your instance data. For more information, see "[Hardware considerations](#hardware-considerations)." {% note %} -**Observação:** você pode criptografar o disco de dados para obter um nível extra de segurança e garantir que todos os dados gravados na sua instância estejam protegidos. Usar discos criptografados gera um leve impacto no desempenho. Se você decidir criptografar o volume, recomendaremos expressamente fazer isso **antes** de iniciar a instância pela primeira vez. -Para obter mais informações, confira o [guia da Amazon sobre a criptografia EBS](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html). +**Note:** You can encrypt the data disk to gain an extra level of security and ensure that any data you write to your instance is protected. There is a slight performance impact when using encrypted disks. If you decide to encrypt your volume, we strongly recommend doing so **before** starting your instance for the first time. + For more information, see the [Amazon guide on EBS encryption](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html). {% endnote %} {% warning %} -**Aviso:** se você decidir habilitar a criptografia depois de configurar sua instância, precisará migrar seus dados para o volume criptografado, o que vai gerar algum tempo de inatividade para os usuários. +**Warning:** If you decide to enable encryption after you've configured your instance, you will need to migrate your data to the encrypted volume, which will incur some downtime for your users. {% endwarning %} -### Iniciar uma instância do EC2 +### Launching an EC2 instance -Na CLI do AWS, inicie uma instância do EC2 usando sua AMI e o grupo de segurança que você criou. Vincule um novo dispositivo de bloqueio para uso como volume de armazenamento dos dados da sua instância e configure o tamanho com base na contagem de licença de usuário. Para obter mais informações, confira "[run-instances](http://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html)" na documentação da AWS. +In the AWS CLI, launch an EC2 instance using your AMI and the security group you created. Attach a new block device to use as a storage volume for your instance data, and configure the size based on your user license count. For more information, see "[run-instances](http://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html)" in the AWS documentation. ```shell aws ec2 run-instances \ - --security-group-ids SECURITY_GROUP_ID \ - --instance-type INSTANCE_TYPE \ - --image-id AMI_ID \ - --block-device-mappings '[{"DeviceName":"/dev/xvdf","Ebs":{"VolumeSize":SIZE,"VolumeType":"TYPE"}}]' \ - --region REGION \ + --security-group-ids SECURITY_GROUP_ID \ + --instance-type INSTANCE_TYPE \ + --image-id AMI_ID \ + --block-device-mappings '[{"DeviceName":"/dev/xvdf","Ebs":{"VolumeSize":SIZE,"VolumeType":"TYPE"}}]' \ + --region REGION \ --ebs-optimized ``` -### Alocar uma IP elástica e associá-la com a instância +### Allocating an Elastic IP and associating it with the instance -Se for uma instância de produção, é recomendável alocar uma IP Elástica (EIP) e associá-la à instância antes de seguir para a configuração do {% data variables.product.prodname_ghe_server %}. Caso contrário, o endereço IP público da instância não será retido após a reinicialização da instância. Para obter mais informações, confira "[Como alocar um endereço IP elástico](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-allocating)" e "[Como associar um endereço IP elástico a uma instância em execução](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-associating)" na documentação da Amazon. +If this is a production instance, we strongly recommend allocating an Elastic IP (EIP) and associating it with the instance before proceeding to {% data variables.product.prodname_ghe_server %} configuration. Otherwise, the public IP address of the instance will not be retained after instance restarts. For more information, see "[Allocating an Elastic IP Address](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-allocating)" and "[Associating an Elastic IP Address with a Running Instance](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-associating)" in the Amazon documentation. -As instâncias primária e de réplica devem receber EIPs separados nas configurações de alta disponibilidade de produção. Para obter mais informações, confira "[Como configurar o {% data variables.product.prodname_ghe_server %} para alta disponibilidade](/enterprise/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)". +Both primary and replica instances should be assigned separate EIPs in production High Availability configurations. For more information, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/enterprise/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)." -## Configurar a instância do {% data variables.product.prodname_ghe_server %} +## Configuring the {% data variables.product.prodname_ghe_server %} instance -{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} {% data reusables.enterprise_installation.upload-a-license-file %} {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obter mais informações, confira "[Como configurar o dispositivo do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)". -{% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} +{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} +{% data reusables.enterprise_installation.upload-a-license-file %} +{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." +{% data reusables.enterprise_installation.instance-will-restart-automatically %} +{% data reusables.enterprise_installation.visit-your-instance %} -## Leitura adicional +## Further reading -- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %} -- "[Sobre os upgrades para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %} +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md index d3db1e6c6b..a23d4e9069 100644 --- a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md +++ b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md @@ -1,6 +1,6 @@ --- -title: Instalar o GitHub Enterprise Server no Azure -intro: 'Para instalar o {% data variables.product.prodname_ghe_server %} no Azure, você deve implantar em uma instância com otimização de memória que dê suporte ao armazenamento premium.' +title: Installing GitHub Enterprise Server on Azure +intro: 'To install {% data variables.product.prodname_ghe_server %} on Azure, you must deploy onto a memory-optimized instance that supports premium storage.' redirect_from: - /enterprise/admin/guides/installation/installing-github-enterprise-on-azure - /enterprise/admin/installation/installing-github-enterprise-server-on-azure @@ -14,80 +14,74 @@ topics: - Infrastructure - Set up shortTitle: Install on Azure -ms.openlocfilehash: 52c435b01e830968eaf81dc411727ea2bacabd2d -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145093946' --- -Você pode implantar o {% data variables.product.prodname_ghe_server %} no Azure global ou Azure Government. +You can deploy {% data variables.product.prodname_ghe_server %} on global Azure or Azure Government. -## Pré-requisitos +## Prerequisites - {% data reusables.enterprise_installation.software-license %} -- Você deve ter uma conta do Azure que permita provisionar novas máquinas. Para obter mais informações, acesse o [site do Microsoft Azure](https://azure.microsoft.com). -- A maioria das ações necessárias para iniciar sua máquina virtual (VM) também pode ser executada pelo Portal do Azure. No entanto, é recomendável instalar a interface da linha de comando (CLI) do Azure para a configuração inicial. Veja abaixo alguns exemplos de uso da CLI do Azure 2.0. Para obter mais informações, confira o guia do Azure "[Instalação da CLI 2.0 do Azure](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)". +- You must have an Azure account capable of provisioning new machines. For more information, see the [Microsoft Azure website](https://azure.microsoft.com). +- Most actions needed to launch your virtual machine (VM) may also be performed using the Azure Portal. However, we recommend installing the Azure command line interface (CLI) for initial setup. Examples using the Azure CLI 2.0 are included below. For more information, see Azure's guide "[Install Azure CLI 2.0](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)." -## Considerações sobre hardware +## Hardware considerations {% data reusables.enterprise_installation.hardware-considerations-all-platforms %} -## Determinar o tipo de máquina virtual +## Determining the virtual machine type -Antes de lançar {% data variables.product.product_location %} no Azure, você deverá determinar o tipo de máquina que melhor atende às necessidades da sua organização. Para obter mais informações sobre computadores com otimização de memória, confira "[Tamanhos de máquina virtual otimizados para memória](https://docs.microsoft.com/en-gb/azure/virtual-machines/sizes-memory)" na documentação Microsoft Azure. Para examinar os requisitos mínimos de recursos para dados para {% data variables.product.product_name %}, confira "[Requisitos mínimos](#minimum-requirements)". +Before launching {% data variables.location.product_location %} on Azure, you'll need to determine the machine type that best fits the needs of your organization. For more information about memory optimized machines, see "[Memory optimized virtual machine sizes](https://docs.microsoft.com/en-gb/azure/virtual-machines/sizes-memory)" in the Microsoft Azure documentation. To review the minimum resource requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)." {% data reusables.enterprise_installation.warning-on-scaling %} {% data reusables.enterprise_installation.azure-instance-recommendation %} -## Criar a instância da máquina virtual do {% data variables.product.prodname_ghe_server %} +## Creating the {% data variables.product.prodname_ghe_server %} virtual machine {% data reusables.enterprise_installation.create-ghe-instance %} -1. Localize a imagem mais recente do appliance do {% data variables.product.prodname_ghe_server %}. Para obter mais informações sobre o comando `vm image list`, confira "[`az vm image list`](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)" na documentação da Microsoft. +1. Find the most recent {% data variables.product.prodname_ghe_server %} appliance image. For more information about the `vm image list` command, see "[`az vm image list`](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)" in the Microsoft documentation. ```shell $ az vm image list --all -f GitHub-Enterprise | grep '"urn":' | sort -V ``` -2. Crie uma VM usando a imagem do appliance. Para obter mais informações, confira "[`az vm create`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_create)" na documentação da Microsoft. +2. Create a new VM using the appliance image you found. For more information, see "[`az vm create`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_create)" in the Microsoft documentation. - Veja as opções de nome da VM, grupo de recursos, tamanho da VM, nome da região preferida do Azure, nome da da imagem de VM do appliance que você listou na etapa anterior e o SKU de armazenamento para Premium. Para obter mais informações sobre grupos de recursos, confira "[Grupos de recursos](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview#resource-groups)" na documentação da Microsoft. + Pass in options for the name of your VM, the resource group, the size of your VM, the name of your preferred Azure region, the name of the appliance image VM you listed in the previous step, and the storage SKU for premium storage. For more information about resource groups, see "[Resource groups](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview#resource-groups)" in the Microsoft documentation. ```shell - $ az vm create -n VM_NAME -g RESOURCE_GROUP --size VM_SIZE -l REGION --image APPLIANCE_IMAGE_NAME --storage-sku Premium_LRS + $ az vm create -n VM_NAME -g RESOURCE_GROUP --size VM_SIZE -l REGION --image APPLIANCE_IMAGE_NAME --storage-sku Premium_LRS ``` -3. Defina as configurações de segurança na VM para abrir as portas necessárias. Para obter mais informações, confira "[`az vm open-port`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)" na documentação da Microsoft. A tabela abaixo descreve cada porta para determinar quais portas você precisa abrir. +3. Configure the security settings on your VM to open up required ports. For more information, see "[`az vm open-port`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)" in the Microsoft documentation. See the table below for a description of each port to determine what ports you need to open. ```shell - $ az vm open-port -n VM_NAME -g RESOURCE_GROUP --port PORT_NUMBER + $ az vm open-port -n VM_NAME -g RESOURCE_GROUP --port PORT_NUMBER ``` - Esta tabela identifica o uso de cada porta. + This table identifies what each port is used for. {% data reusables.enterprise_installation.necessary_ports %} -4. Crie e anexe um novo disco de dados não criptografado à VM e configure o tamanho com base na sua contagem de licenças do usuário. Para obter mais informações, confira "[`az vm disk attach`](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" na documentação da Microsoft. +4. Create and attach a new unencrypted data disk to the VM, and configure the size based on your user license count. For more information, see "[`az vm disk attach`](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" in the Microsoft documentation. - Transmita as opções de nome da VM (por exemplo, `ghe-acme-corp`), o grupo de recursos, o SKU de armazenamento premium, o tamanho do disco (por exemplo, `100`) e um nome para o VHD resultante. + Pass in options for the name of your VM (for example, `ghe-acme-corp`), the resource group, the premium storage SKU, the size of the disk (for example, `200`), and a name for the resulting VHD. ```shell - $ az vm disk attach --vm-name VM_NAME -g RESOURCE_GROUP --sku Premium_LRS --new -z SIZE_IN_GB --name ghe-data.vhd --caching ReadWrite + $ az vm disk attach --vm-name VM_NAME -g RESOURCE_GROUP --sku Premium_LRS --new -z SIZE_IN_GB --name ghe-data.vhd --caching ReadWrite ``` {% note %} - **Observação:** para que as instâncias de não produção tenham uma taxa de transferência de E/S suficiente, o tamanho mínimo recomendado do disco é de 40 GiB com o cache de leitura/gravação habilitado (`--caching ReadWrite`). + **Note:** For non-production instances to have sufficient I/O throughput, the recommended minimum disk size is 150 GiB with read/write cache enabled (`--caching ReadWrite`). {% endnote %} -## Configurar a máquina virtual do {% data variables.product.prodname_ghe_server %} +## Configuring the {% data variables.product.prodname_ghe_server %} virtual machine -1. Antes de configurar a VM, você deve aguardar a entrada no status ReadyRole. Verifique o status da VM com o comando `vm list`. Para obter mais informações, confira "[`az vm list`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_list)" na documentação da Microsoft. +1. Before configuring the VM, you must wait for it to enter ReadyRole status. Check the status of the VM with the `vm list` command. For more information, see "[`az vm list`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_list)" in the Microsoft documentation. ```shell - $ az vm list -d -g RESOURCE_GROUP -o table + $ az vm list -d -g RESOURCE_GROUP -o table > Name ResourceGroup PowerState PublicIps Fqdns Location Zones > ------ --------------- ------------ ------------ ------- ---------- ------- > VM_NAME RESOURCE_GROUP VM running 40.76.79.202 eastus @@ -95,14 +89,17 @@ Antes de lançar {% data variables.product.product_location %} no Azure, você d ``` {% note %} - **Observação:** o Azure não cria automaticamente uma entrada FQDNS para a VM. Para obter mais informações, confira o guia do Azure sobre como "[Criar um nome de domínio totalmente qualificado no portal do Azure para uma VM do Linux](https://docs.microsoft.com/azure/virtual-machines/linux/portal-create-fqdn)". + **Note:** Azure does not automatically create a FQDNS entry for the VM. For more information, see Azure's guide on how to "[Create a fully qualified domain name in the Azure portal for a Linux VM](https://docs.microsoft.com/azure/virtual-machines/linux/portal-create-fqdn)." {% endnote %} - {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} {% data reusables.enterprise_installation.upload-a-license-file %} {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obter mais informações, confira "[Como configurar o dispositivo do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)". - {% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} + {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} + {% data reusables.enterprise_installation.upload-a-license-file %} + {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." + {% data reusables.enterprise_installation.instance-will-restart-automatically %} + {% data reusables.enterprise_installation.visit-your-instance %} -## Leitura adicional +## Further reading -- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %} -- "[Sobre os upgrades para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %} +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md index c2a7f30c8a..b60a736ab4 100644 --- a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md +++ b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md @@ -1,6 +1,6 @@ --- -title: Instalar o GitHub Enterprise Server no Google Cloud Platform -intro: 'Para instalar o {% data variables.product.prodname_ghe_server %} no Google Cloud Platform, você deve fazer a implantação em um tipo de máquina compatível e usar um disco padrão persistente ou SSD persistente.' +title: Installing GitHub Enterprise Server on Google Cloud Platform +intro: 'To install {% data variables.product.prodname_ghe_server %} on Google Cloud Platform, you must deploy onto a supported machine type and use a persistent standard disk or a persistent SSD.' redirect_from: - /enterprise/admin/guides/installation/installing-github-enterprise-on-google-cloud-platform - /enterprise/admin/installation/installing-github-enterprise-server-on-google-cloud-platform @@ -14,91 +14,88 @@ topics: - Infrastructure - Set up shortTitle: Install on GCP -ms.openlocfilehash: 0fffebece94753365e1b98f014f0514cdef4f98a -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145094930' --- -## Pré-requisitos +## Prerequisites - {% data reusables.enterprise_installation.software-license %} -- É preciso ter uma conta do Google Cloud Platform que possa iniciar instâncias de máquina virtual (VM) do Google Compute Engine (GCE). Para obter mais informações, consulte o [site do Google Cloud Platform](https://cloud.google.com/) e a [Documentação do Google Cloud Platform](https://cloud.google.com/docs/). -- A maioria das ações necessárias para iniciar sua instância também pode ser executada usando o [Console do Google Cloud Platform](https://cloud.google.com/compute/docs/console). No entanto, é recomendável instalar a ferramenta de linha de comando gcloud compute para a configuração inicial. Veja abaixo alguns exemplos de uso da ferramenta de linha de comando gcloud compute. Para obter mais informações, consulte o guia de instalação e configuração do "[gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/)" na documentação do Google. +- You must have a Google Cloud Platform account capable of launching Google Compute Engine (GCE) virtual machine (VM) instances. For more information, see the [Google Cloud Platform website](https://cloud.google.com/) and the [Google Cloud Platform Documentation](https://cloud.google.com/docs/). +- Most actions needed to launch your instance may also be performed using the [Google Cloud Platform Console](https://cloud.google.com/compute/docs/console). However, we recommend installing the gcloud compute command-line tool for initial setup. Examples using the gcloud compute command-line tool are included below. For more information, see the "[gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/)" installation and setup guide in the Google documentation. -## Considerações sobre hardware +## Hardware considerations {% data reusables.enterprise_installation.hardware-considerations-all-platforms %} -## Determinar o tipo de máquina +## Determining the machine type -Antes de iniciar o {% data variables.product.product_location %} no Google Cloud Platform, você precisará determinar o melhor tipo de computador para as necessidades da sua organização. Para revisar os requisitos mínimos do {% data variables.product.product_name %}, confira "[Requisitos mínimos](#minimum-requirements)". +Before launching {% data variables.location.product_location %} on Google Cloud Platform, you'll need to determine the machine type that best fits the needs of your organization. To review the minimum requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)." {% data reusables.enterprise_installation.warning-on-scaling %} -{% data variables.product.company_short %} recomenda uma máquina de uso geral e de alta memória para {% data variables.product.prodname_ghe_server %}. Para obter mais informações, consulte "[Tipos de computador](https://cloud.google.com/compute/docs/machine-types#n2_high-memory_machine_types)" na documentação do Google Compute Engine. +{% data variables.product.company_short %} recommends a general-purpose, high-memory machine for {% data variables.product.prodname_ghe_server %}. For more information, see "[Machine types](https://cloud.google.com/compute/docs/machine-types#n2_high-memory_machine_types)" in the Google Compute Engine documentation. -## Selecionar a imagem do {% data variables.product.prodname_ghe_server %} +## Selecting the {% data variables.product.prodname_ghe_server %} image -1. Usando a ferramenta de linha de comando [gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/), liste as imagens públicas de {% data variables.product.prodname_ghe_server %}: +1. Using the [gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/) command-line tool, list the public {% data variables.product.prodname_ghe_server %} images: ```shell $ gcloud compute images list --project github-enterprise-public --no-standard-images ``` -2. Anote o nome da imagem GCE mais recente do {% data variables.product.prodname_ghe_server %}. +2. Take note of the image name for the latest GCE image of {% data variables.product.prodname_ghe_server %}. -## Configurar o firewall +## Configuring the firewall -Máquinas virtuais GCE são criadas como integrantes de uma rede que tem um firewall. Na rede associada à VM do {% data variables.product.prodname_ghe_server %}, você terá que configurar o firewall para permitir as portas necessárias da tabela abaixo. Para obter mais informações sobre regras de firewall no Google Cloud Platform, consulte o guia do Google "[Visão geral das regras de firewall](https://cloud.google.com/vpc/docs/firewalls)". +GCE virtual machines are created as a member of a network, which has a firewall. For the network associated with the {% data variables.product.prodname_ghe_server %} VM, you'll need to configure the firewall to allow the required ports listed in the table below. For more information about firewall rules on Google Cloud Platform, see the Google guide "[Firewall Rules Overview](https://cloud.google.com/vpc/docs/firewalls)." -1. Usando a ferramenta de linha de comando gcloud compute, crie a rede. Para obter mais informações, consulte "[gcloud compute networks create](https://cloud.google.com/sdk/gcloud/reference/compute/networks/create)" na documentação do Google. +1. Using the gcloud compute command-line tool, create the network. For more information, see "[gcloud compute networks create](https://cloud.google.com/sdk/gcloud/reference/compute/networks/create)" in the Google documentation. ```shell - $ gcloud compute networks create NETWORK-NAME --subnet-mode auto + $ gcloud compute networks create NETWORK-NAME --subnet-mode auto ``` -2. Crie uma regra de firewall para cada porta da tabela abaixo. Para obter mais informações, consulte "[gcloud compute firewall-rules](https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/)" na documentação do Google. +2. Create a firewall rule for each of the ports in the table below. For more information, see "[gcloud compute firewall-rules](https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/)" in the Google documentation. ```shell - $ gcloud compute firewall-rules create RULE-NAME \ - --network NETWORK-NAME \ + $ gcloud compute firewall-rules create RULE-NAME \ + --network NETWORK-NAME \ --allow tcp:22,tcp:25,tcp:80,tcp:122,udp:161,tcp:443,udp:1194,tcp:8080,tcp:8443,tcp:9418,icmp ``` - Esta tabela identifica as portas necessárias e o uso de cada uma delas. + This table identifies the required ports and what each port is used for. {% data reusables.enterprise_installation.necessary_ports %} -## Alocar uma IP estática e associá-la com a VM +## Allocating a static IP and assigning it to the VM -Se você estiver trabalhando com um appliance de produção, é altamente recomendável reservar um endereço IP externo estático e atribuí-lo à VM do {% data variables.product.prodname_ghe_server %}. Caso contrário, o endereço IP público da VM não será retido após a reinicialização. Para obter mais informações, consulte o guia do Google "[Como reservar um endereço IP externo estático](https://cloud.google.com/compute/docs/configure-instance-ip-addresses)". +If this is a production appliance, we strongly recommend reserving a static external IP address and assigning it to the {% data variables.product.prodname_ghe_server %} VM. Otherwise, the public IP address of the VM will not be retained after restarts. For more information, see the Google guide "[Reserving a Static External IP Address](https://cloud.google.com/compute/docs/configure-instance-ip-addresses)." -Nas configurações de alta disponibilidade de produção, os appliances primário e réplica devem receber endereços IP estáticos separados. +In production High Availability configurations, both primary and replica appliances should be assigned separate static IP addresses. -## Criar a instância do {% data variables.product.prodname_ghe_server %} +## Creating the {% data variables.product.prodname_ghe_server %} instance -Para criar a instância do {% data variables.product.prodname_ghe_server %}, você deve criar uma instância do GCE com a imagem do {% data variables.product.prodname_ghe_server %} e vincular um volume de armazenamento adicional aos dados da sua instância. Para obter mais informações, confira "[Considerações sobre hardware](#hardware-considerations)". +To create the {% data variables.product.prodname_ghe_server %} instance, you'll need to create a GCE instance with your {% data variables.product.prodname_ghe_server %} image and attach an additional storage volume for your instance data. For more information, see "[Hardware considerations](#hardware-considerations)." -1. Usando a ferramenta de linha de comando gcloud compute, crie um disco de dados para usar como volume de armazenamento para os dados da sua instância e configure o tamanho com base na contagem de licenças de usuário. Para obter mais informações, consulte "[gcloud compute disks create](https://cloud.google.com/sdk/gcloud/reference/compute/disks/create)" na documentação do Google. +1. Using the gcloud compute command-line tool, create a data disk to use as an attached storage volume for your instance data, and configure the size based on your user license count. For more information, see "[gcloud compute disks create](https://cloud.google.com/sdk/gcloud/reference/compute/disks/create)" in the Google documentation. ```shell - $ gcloud compute disks create DATA-DISK-NAME --size DATA-DISK-SIZE --type DATA-DISK-TYPE --zone ZONE + $ gcloud compute disks create DATA-DISK-NAME --size DATA-DISK-SIZE --type DATA-DISK-TYPE --zone ZONE ``` -2. Em seguida, crie uma instância usando o nome da imagem selecionada do {% data variables.product.prodname_ghe_server %} e vincule o disco de dados. Para obter mais informações, consulte "[gcloud compute instances create](https://cloud.google.com/sdk/gcloud/reference/compute/instances/create)" na documentação do Google. +2. Then create an instance using the name of the {% data variables.product.prodname_ghe_server %} image you selected, and attach the data disk. For more information, see "[gcloud compute instances create](https://cloud.google.com/sdk/gcloud/reference/compute/instances/create)" in the Google documentation. ```shell - $ gcloud compute instances create INSTANCE-NAME \ + $ gcloud compute instances create INSTANCE-NAME \ --machine-type n1-standard-8 \ - --image GITHUB-ENTERPRISE-IMAGE-NAME \ - --disk name=DATA-DISK-NAME \ + --image GITHUB-ENTERPRISE-IMAGE-NAME \ + --disk name=DATA-DISK-NAME \ --metadata serial-port-enable=1 \ - --zone ZONE \ - --network NETWORK-NAME \ + --zone ZONE \ + --network NETWORK-NAME \ --image-project github-enterprise-public ``` -## Configurar a instância +## Configuring the instance -{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} {% data reusables.enterprise_installation.upload-a-license-file %} {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obter mais informações, confira "[Como configurar o dispositivo do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)". -{% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} +{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} +{% data reusables.enterprise_installation.upload-a-license-file %} +{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." +{% data reusables.enterprise_installation.instance-will-restart-automatically %} +{% data reusables.enterprise_installation.visit-your-instance %} -## Leitura adicional +## Further reading -- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %} -- "[Sobre os upgrades para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %} +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md index 6ffd527a07..3381721392 100644 --- a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md +++ b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md @@ -1,6 +1,6 @@ --- -title: Instalar o GitHub Enterprise Server no OpenStack KVM -intro: 'Para instalar o {% data variables.product.prodname_ghe_server %} no OpenStack KVM, você deve ter acesso ao OpenStack e baixar a imagem QCOW2 do {% data variables.product.prodname_ghe_server %}.' +title: Installing GitHub Enterprise Server on OpenStack KVM +intro: 'To install {% data variables.product.prodname_ghe_server %} on OpenStack KVM, you must have OpenStack access and download the {% data variables.product.prodname_ghe_server %} QCOW2 image.' redirect_from: - /enterprise/admin/guides/installation/installing-github-enterprise-on-openstack-kvm - /enterprise/admin/installation/installing-github-enterprise-server-on-openstack-kvm @@ -14,46 +14,44 @@ topics: - Infrastructure - Set up shortTitle: Install on OpenStack -ms.openlocfilehash: 105201d2759b333d297278aa7fe32a9544c68839 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147884952' --- -## Pré-requisitos +## Prerequisites - {% data reusables.enterprise_installation.software-license %} -- Você deve ter acesso a uma instalação do OpenStack Horizon, a interface de usuário baseada na web para os serviços do OpenStack. Para obter mais informações, confira a [documentação do Horizon](https://docs.openstack.org/horizon/latest/). +- You must have access to an installation of OpenStack Horizon, the web-based user interface to OpenStack services. For more information, see the [Horizon documentation](https://docs.openstack.org/horizon/latest/). -## Considerações sobre hardware +## Hardware considerations {% data reusables.enterprise_installation.hardware-considerations-all-platforms %} -## Baixar a imagem do {% data variables.product.prodname_ghe_server %} +## Downloading the {% data variables.product.prodname_ghe_server %} image -{% data reusables.enterprise_installation.download-license %} {% data reusables.enterprise_installation.download-appliance %} -4. Em "{% data variables.product.prodname_dotcom %} local", selecione o menu suspenso "Selecionar seu hipervisor" e clique em **OpenStack KVM (QCOW2)** . -5. Clique em **Baixar para a KVM do OpenStack (QCOW2)** . +{% data reusables.enterprise_installation.download-license %} +{% data reusables.enterprise_installation.download-appliance %} +4. Under "{% data variables.product.prodname_dotcom %} On-premises", select the "Select your hypervisor" dropdown menu and click **OpenStack KVM (QCOW2)**. +5. Click **Download for OpenStack KVM (QCOW2)**. -## Criar a instância do {% data variables.product.prodname_ghe_server %} +## Creating the {% data variables.product.prodname_ghe_server %} instance {% data reusables.enterprise_installation.create-ghe-instance %} -1. No OpenStack Horizon, faça upload da imagem do {% data variables.product.prodname_ghe_server %} que você baixou. Para obter instruções, confira a seção "Carregar uma imagem" do guia do OpenStack "[Carregar e gerenciar imagens](https://docs.openstack.org/horizon/latest/user/manage-images.html)". -{% data reusables.enterprise_installation.create-attached-storage-volume %} Para obter instruções, confira o guia do OpenStack "[Criar e gerenciar volumes](https://docs.openstack.org/horizon/latest/user/manage-volumes.html)". -3. Crie um grupo de segurança e adicione uma nova regra de grupo de segurança para cada porta na tabela abaixo. Para obter instruções, confira o guia do OpenStack "[Configurar o acesso e a segurança para as instâncias](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html)". +1. In OpenStack Horizon, upload the {% data variables.product.prodname_ghe_server %} image you downloaded. For instructions, see the "Upload an image" section of the OpenStack guide "[Upload and manage images](https://docs.openstack.org/horizon/latest/user/manage-images.html)." +{% data reusables.enterprise_installation.create-attached-storage-volume %} For instructions, see the OpenStack guide "[Create and manage volumes](https://docs.openstack.org/horizon/latest/user/manage-volumes.html)." +3. Create a security group, and add a new security group rule for each port in the table below. For instructions, see the OpenStack guide "[Configure access and security for instances](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html)." {% data reusables.enterprise_installation.necessary_ports %} -4. Você também pode associar um IP flutuante à instância. Dependendo da sua configuração do OpenStack, talvez seja necessário alocar um IP flutuante para o projeto e associá-lo à instância. Entre em contato com o administrador do sistema para determinar se esse é o seu caso. Para obter mais informações, confira "[Alocar um endereço IP flutuante para uma instância](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html#allocate-a-floating-ip-address-to-an-instance)" na documentação do OpenStack. -5. Inicie o {% data variables.product.product_location %} usando a imagem, o volume de dados e o grupo de segurança criados nas etapas anteriores. Para obter instruções, confira o guia do OpenStack "[Iniciar e gerenciar instâncias](https://docs.openstack.org/horizon/latest/user/launch-instances.html)". +4. Optionally, associate a floating IP to the instance. Depending on your OpenStack setup, you may need to allocate a floating IP to the project and associate it to the instance. Contact your system administrator to determine if this is the case for you. For more information, see "[Allocate a floating IP address to an instance](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html#allocate-a-floating-ip-address-to-an-instance)" in the OpenStack documentation. +5. Launch {% data variables.location.product_location %} using the image, data volume, and security group created in the previous steps. For instructions, see the OpenStack guide "[Launch and manage instances](https://docs.openstack.org/horizon/latest/user/launch-instances.html)." -## Configurar a instância do {% data variables.product.prodname_ghe_server %} +## Configuring the {% data variables.product.prodname_ghe_server %} instance -{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} {% data reusables.enterprise_installation.upload-a-license-file %} {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obter mais informações, confira "[Como configurar o dispositivo do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)". -{% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} +{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} +{% data reusables.enterprise_installation.upload-a-license-file %} +{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." +{% data reusables.enterprise_installation.instance-will-restart-automatically %} +{% data reusables.enterprise_installation.visit-your-instance %} -## Leitura adicional +## Further reading -- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %} -- "[Sobre os upgrades para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %} +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md index f46409473a..5c82bae468 100644 --- a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md +++ b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md @@ -1,6 +1,6 @@ --- -title: Instalar o GitHub Enterprise Server no VMware -intro: 'Para instalar o {% data variables.product.prodname_ghe_server %} no VMware, você deve fazer o download do cliente do VMware vSphere e, em seguida, fazer o download e implantar o software do {% data variables.product.prodname_ghe_server %}.' +title: Installing GitHub Enterprise Server on VMware +intro: 'To install {% data variables.product.prodname_ghe_server %} on VMware, you must download the VMware vSphere client, and then download and deploy the {% data variables.product.prodname_ghe_server %} software.' redirect_from: - /enterprise/admin/articles/getting-started-with-vmware - /enterprise/admin/articles/installing-vmware-tools @@ -17,44 +17,42 @@ topics: - Infrastructure - Set up shortTitle: Install on VMware -ms.openlocfilehash: f9e81c624f93c7478eed04b65b3ef43a69ef9291 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147859407' --- -## Pré-requisitos +## Prerequisites - {% data reusables.enterprise_installation.software-license %} -- Você precisa ter um Hipervisor VMware vSphere ESXi aplicado a um computador bare-metal que executará os {% data variables.product.product_location %}s. Damos suporte às versões 5.5 a 6.7 para o {% data variables.product.prodname_ghe_server %} 3.4 e versões anteriores. O ESX versão 7.0 é compatível com {% data variables.product.prodname_ghe_server %} 3.5 e versões posteriores. O Hpervisor ESXi é grátis e não inclui o Servidor vCenter (opcional). Para obter mais informações, confira a [documentação do VMware ESXi](https://www.vmware.com/products/esxi-and-esx.html). -- Você precisará de acesso a um cliente vSphere. Se tiver o servidor vCenter, você poderá usar o cliente vSphere Web. Para obter mais informações, confira o guia do VMware "[Fazer logon no vCenter Server usando o cliente Web do vSphere](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-CE128B59-E236-45FF-9976-D134DADC8178.html)". +- You must have a VMware vSphere ESXi Hypervisor, applied to a bare metal machine that will run {% data variables.location.product_location %}s. We support versions 5.5 through 6.7 for {% data variables.product.prodname_ghe_server %} 3.4 and earlier. ESX version 7.0 is supported for {% data variables.product.prodname_ghe_server %} 3.5 and later. The ESXi Hypervisor is free and does not include the (optional) vCenter Server. For more information, see [the VMware ESXi documentation](https://www.vmware.com/products/esxi-and-esx.html). +- You will need access to a vSphere Client. If you have vCenter Server you can use the vSphere Web Client. For more information, see the VMware guide "[Log in to vCenter Server by Using the vSphere Web Client](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-CE128B59-E236-45FF-9976-D134DADC8178.html)." -## Considerações sobre hardware +## Hardware considerations {% data reusables.enterprise_installation.hardware-considerations-all-platforms %} -## Baixar a imagem do {% data variables.product.prodname_ghe_server %} +## Downloading the {% data variables.product.prodname_ghe_server %} image -{% data reusables.enterprise_installation.download-license %} {% data reusables.enterprise_installation.download-appliance %} -4. Em "{% data variables.product.prodname_dotcom %} local", selecione o menu suspenso "Selecionar seu hipervisor" e clique em **VMware ESXi/vSphere (OVA)** . -5. Clique em **Baixar para VMware ESXi/vSphere (OVA)** . +{% data reusables.enterprise_installation.download-license %} +{% data reusables.enterprise_installation.download-appliance %} +4. Under "{% data variables.product.prodname_dotcom %} On-premises", select the "Select your hypervisor" dropdown menu and click **VMware ESXi/vSphere (OVA)**. +5. Click **Download for VMware ESXi/vSphere (OVA)**. -## Criar a instância do {% data variables.product.prodname_ghe_server %} +## Creating the {% data variables.product.prodname_ghe_server %} instance {% data reusables.enterprise_installation.create-ghe-instance %} -1. Usando o cliente vSphere Windows ou vCenter Web, importe a imagem do {% data variables.product.prodname_ghe_server %} que você baixou. Para obter instruções, confira o guia do VMware "[Implantar um modelo OVF ou OVA](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-17BEDA21-43F6-41F4-8FB2-E01D275FE9B4.html)". - - Ao selecionar um armazenamento de dados, escolha um que tenha espaço suficiente para hospedar os discos da VM. Para ver as especificações mínimas de hardware recomendadas para o tamanho da instância, confira "[Considerações sobre hardware](#hardware-considerations)". Recomendamos um provisionamento robusto com lazy zeroing. - - Mantenha a caixa **Ligar após implantação** desmarcada, pois você precisará adicionar um volume de armazenamento anexado aos dados do repositório após o provisionamento da VM. -{% data reusables.enterprise_installation.create-attached-storage-volume %} Para obter instruções, confira o guia do VMware "[Adicionar um novo disco rígido a uma máquina virtual](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-F4917C61-3D24-4DB9-B347-B5722A84368C.html)". +1. Using the vSphere Windows Client or the vCenter Web Client, import the {% data variables.product.prodname_ghe_server %} image you downloaded. For instructions, see the VMware guide "[Deploy an OVF or OVA Template](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-17BEDA21-43F6-41F4-8FB2-E01D275FE9B4.html)." + - When selecting a datastore, choose one with sufficient space to host the VM's disks. For the minimum hardware specifications recommended for your instance size, see "[Hardware considerations](#hardware-considerations)." We recommend thick provisioning with lazy zeroing. + - Leave the **Power on after deployment** box unchecked, as you will need to add an attached storage volume for your repository data after provisioning the VM. +{% data reusables.enterprise_installation.create-attached-storage-volume %} For instructions, see the VMware guide "[Add a New Hard Disk to a Virtual Machine](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-F4917C61-3D24-4DB9-B347-B5722A84368C.html)." -## Configurar a instância do {% data variables.product.prodname_ghe_server %} +## Configuring the {% data variables.product.prodname_ghe_server %} instance -{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} {% data reusables.enterprise_installation.upload-a-license-file %} {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} Para obter mais informações, confira "[Como configurar o dispositivo do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)". -{% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} +{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} +{% data reusables.enterprise_installation.upload-a-license-file %} +{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." +{% data reusables.enterprise_installation.instance-will-restart-automatically %} +{% data reusables.enterprise_installation.visit-your-instance %} -## Leitura adicional +## Further reading -- "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %} -- "[Sobre os upgrades para novas versões](/admin/overview/about-upgrades-to-new-releases)"{% endif %} +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md index 9445e64621..ecfcde73e0 100644 --- a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md +++ b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md @@ -17,7 +17,7 @@ miniTocMaxHeadingLevel: 3 ## About staging instances -{% data variables.product.company_short %} recommends that you set up a separate environment to test backups, updates, or changes to the configuration for {% data variables.product.product_location %}. This environment, which you should isolate from your production systems, is called a staging environment. +{% data variables.product.company_short %} recommends that you set up a separate environment to test backups, updates, or changes to the configuration for {% data variables.location.product_location %}. This environment, which you should isolate from your production systems, is called a staging environment. For example, to protect against loss of data, you can regularly validate the backup of your production instance. You can regularly restore the backup of your production data to a separate {% data variables.product.product_name %} instance in a staging environment. On this staging instance, you could also test the upgrade to the latest feature release of {% data variables.product.product_name %}. @@ -136,7 +136,7 @@ To access the staging instance using the same hostname, update your local hosts {% note %} -**Note**: Your staging instance must be accessible from the same hostname as your production instance. Changing the hostname for {% data variables.product.product_location %} is not supported. For more information, see "[Configuring a hostname](/admin/configuration/configuring-network-settings/configuring-a-hostname)." +**Note**: Your staging instance must be accessible from the same hostname as your production instance. Changing the hostname for {% data variables.location.product_location %} is not supported. For more information, see "[Configuring a hostname](/admin/configuration/configuring-network-settings/configuring-a-hostname)." {% endnote %} diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md index 54994a0159..8dca96d496 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md @@ -1,6 +1,6 @@ --- -title: Sobre estatísticas do servidor -intro: 'Você pode usar {% data variables.product.prodname_server_statistics %} para analisar seus próprios dados agregados do {% data variables.product.prodname_ghe_server %} e nos ajudar a melhorar os produtos {% data variables.product.company_short %}.' +title: About Server Statistics +intro: 'You can use {% data variables.product.prodname_server_statistics %} to analyze your own aggregate data from {% data variables.product.prodname_ghe_server %}, and help us improve {% data variables.product.company_short %} products.' versions: feature: server-statistics permissions: 'Enterprise owners can enable {% data variables.product.prodname_server_statistics %}.' @@ -8,54 +8,49 @@ redirect_from: - /early-access/github/analyze-how-your-team-works-with-server-statistics/about-server-statistics topics: - Enterprise -ms.openlocfilehash: c71cab38c096d5984a5136147b6dbc75e794c173 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147409320' --- -## Sobre os benefícios de {% data variables.product.prodname_server_statistics %} -As {% data variables.product.prodname_server_statistics %} podem ajudar você a prever as necessidades de sua organização, entender como sua equipe trabalha e mostrar o valor obtido do {% data variables.product.prodname_ghe_server %}. +## About the benefits of {% data variables.product.prodname_server_statistics %} -Depois de habilitadas, as {% data variables.product.prodname_server_statistics %} coleta dados agregados sobre quanto determinados recursos estão sendo usados em sua instância ao longo do tempo. Ao contrário de outros pontos de extremidade da [API Admin Stats](/rest/reference/enterprise-admin#admin-stats), que só retornam dados do dia anterior, as {% data variables.product.prodname_server_statistics %} fornecem dados históricos de todas as métricas de {% data variables.product.prodname_server_statistics %} coletadas desde o dia em que você habilitou o recurso. Para obter mais informações, confira "[Como habilitar {% data variables.product.prodname_server_statistics %} para sua empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)". +{% data variables.product.prodname_server_statistics %} can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. -Ao habilitar {% data variables.product.prodname_server_statistics %}, você está ajudando a criar um {% data variables.product.prodname_dotcom %} melhor. Os dados agregados que você fornecerá nos fornecerão insights sobre como o {% data variables.product.prodname_dotcom %} adiciona valor aos nossos clientes. Essas informações permitem que {% data variables.product.company_short %} tome decisões melhores e mais informadas sobre produtos, beneficiando você. +Once enabled, {% data variables.product.prodname_server_statistics %} collects aggregate data on how much certain features are used on your instance over time. Unlike other [Admin Stats API](/rest/reference/enterprise-admin#admin-stats) endpoints, which only return data for the last day, {% data variables.product.prodname_server_statistics %} provides historical data of all {% data variables.product.prodname_server_statistics %} metrics collected since the day you enabled the feature. For more information, see "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." -## Sobre a segurança de dados +When you enable {% data variables.product.prodname_server_statistics %}, you're helping to build a better {% data variables.product.prodname_dotcom %}. The aggregated data you'll provide gives us insights into how {% data variables.product.prodname_dotcom %} adds value to our customers. This information allows {% data variables.product.company_short %} to make better and more informed product decisions, ultimately benefiting you. -Respeitamos seus dados. Nunca transmitiremos dados do {% data variables.product.product_location %} a menos que você primeiro nos tenha dado permissão para fazê-lo. +## About data security -Não coletamos dados pessoais. Também não coletamos nenhum conteúdo do {% data variables.product.company_short %}, como código, problemas, comentários ou conteúdo de solicitação de pull. +We respect your data. We will never transmit data from {% data variables.location.product_location %} unless you have first given us permission to do so. -Somente proprietários da conta corporativa ou organização conectada ao {% data variables.product.prodname_ghe_cloud %} podem acessar os dados. +We collect no personal data. We also don't collect any {% data variables.product.company_short %} content, such as code, issues, comments, or pull request content. -Somente determinadas métricas de agregação são coletadas em repositórios, problemas, solicitações de pull e outros recursos. Para ver a lista de métricas de agregação coletadas, confira "[Dados coletados de {% data variables.product.prodname_server_statistics %}](#server-statistics-data-collected)". +Only owners of the connected enterprise account or organization on {% data variables.product.prodname_ghe_cloud %} can access the data. -As atualizações nas métricas coletadas ocorrerão em versões futuras do {% data variables.product.prodname_ghe_server %} e serão descritas nas [notas sobre a versão do {% data variables.product.prodname_ghe_server %}](/admin/release-notes). Além disso, atualizaremos este artigo com todas as atualizações de métricas. +Only certain aggregate metrics are collected on repositories, issues, pull requests, and other features. To see the list of aggregate metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](#server-statistics-data-collected)." -Para uma melhor compreensão de como armazenamos e protegemos dados de {% data variables.product.prodname_server_statistics %} dados, confira "[Segurança do GitHub](https://github.com/security)". +Any updates to the collected metrics will happen in future feature releases of {% data variables.product.prodname_ghe_server %} and will be described in the [{% data variables.product.prodname_ghe_server %} release notes](/admin/release-notes). In addition, we will update this article with all metric updates. -### Sobre retenção e exclusão de dados +For a better understanding of how we store and secure {% data variables.product.prodname_server_statistics %} data, see "[GitHub Security](https://github.com/security)." -O {% data variables.product.company_short %} coleta dados de {% data variables.product.prodname_server_statistics %} enquanto sua licença do {% data variables.product.prodname_ghe_server %} estiver ativa e o recurso {% data variables.product.prodname_server_statistics %} habilitado. +### About data retention and deletion -Se você quiser excluir seus dados, poderá fazer isso entrando em contato com o Suporte do GitHub, seu representante de conta do {% data variables.product.prodname_dotcom %} ou seu Gerente de Sucesso do Cliente. Geralmente, excluímos dados no período de tempo especificado em nossa política de privacidade. Para obter mais informações, confira [ declaração de privacidade do {% data variables.product.company_short %}](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#data-retention-and-deletion-of-data) na documentação do {% data variables.product.prodname_dotcom_the_website %}. +{% data variables.product.company_short %} collects {% data variables.product.prodname_server_statistics %} data for as long as your {% data variables.product.prodname_ghe_server %} license is active and the {% data variables.product.prodname_server_statistics %} feature is enabled. -### Sobre a portabilidade de dados +If you would like to delete your data, you may do so by contacting GitHub Support, your {% data variables.product.prodname_dotcom %} account representative, or your Customer Success Manager. Generally, we delete data in the timeframe specified in our privacy statement. For more information, see [{% data variables.product.company_short %}'s privacy statement](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#data-retention-and-deletion-of-data) in the {% data variables.product.prodname_dotcom_the_website %} documentation. -Como proprietário da organização ou proprietário da empresa no {% data variables.product.prodname_ghe_cloud %}, você pode acessar {% data variables.product.prodname_server_statistics %} exportando os dados em um arquivo CSV ou JSON ou por meio da API REST de {% data variables.product.prodname_server_statistics %}. Para obter mais informações, confira "[Como solicitar {% data variables.product.prodname_server_statistics %} usando a API REST](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)" ou "[Como exportar {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics)". +### About data portability -## Sobre desabilitar a coleta de dados +As an organization owner or enterprise owner on {% data variables.product.prodname_ghe_cloud %}, you can access {% data variables.product.prodname_server_statistics %} data by exporting the data in a CSV or JSON file or through the {% data variables.product.prodname_server_statistics %} REST API. For more information, see "[Requesting {% data variables.product.prodname_server_statistics %} using the REST API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)" or "[Exporting {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics)." -Você pode desabilitar o recurso {% data variables.product.prodname_server_statistics %} a qualquer momento. Para obter mais informações, confira "[Como habilitar {% data variables.product.prodname_server_statistics %} para sua empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)". +## About disabling data collection -## Dados coletados de {% data variables.product.prodname_server_statistics %} +You can disable the {% data variables.product.prodname_server_statistics %} feature at any time. For more information, see "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." -Depois de habilitar {% data variables.product.prodname_server_statistics %}, as métricas serão coletadas por meio de um trabalho diário executado no {% data variables.product.product_location %}. As métricas de agregação são armazenadas em sua conta da organização ou da empresa no {% data variables.product.prodname_ghe_cloud %} e não são armazenadas no {% data variables.product.product_location %}. +## {% data variables.product.prodname_server_statistics %} data collected -As seguintes métricas de agregação serão coletadas e transmitidas diariamente e representam as contagens totais do dia: +After you enable {% data variables.product.prodname_server_statistics %}, metrics are collected through a daily job that runs on {% data variables.location.product_location %}. The aggregate metrics are stored on your organization or enterprise account on {% data variables.product.prodname_ghe_cloud %} and are not stored on {% data variables.location.product_location %}. + +The following aggregate metrics will be collected and transmitted on a daily basis and represent the total counts for the day: - `active_hooks` - `admin_users` - `closed_issues` @@ -98,8 +93,8 @@ As seguintes métricas de agregação serão coletadas e transmitidas diariament - `total_wikis` - `unmergeable_pulls` -## Exemplo de conteúdo do {% data variables.product.prodname_server_statistics %} +## {% data variables.product.prodname_server_statistics %} payload example -Para ver um exemplo do conteúdo de resposta para a API de {% data variables.product.prodname_server_statistics %}, confira "[Como solicitar {% data variables.product.prodname_server_statistics %} usando a API REST](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)". +To see an example of the response payload for the {% data variables.product.prodname_server_statistics %} API, see "[Requesting {% data variables.product.prodname_server_statistics %} using the REST API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)." -Para ver uma lista dos dados coletados, confira "[Dados coletados de {% data variables.product.prodname_server_statistics %}](#server-statistics-data-collected)". +To see a list of the data collected, see "[{% data variables.product.prodname_server_statistics %} data collected](#server-statistics-data-collected)." diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md index b5d9a78568..7c27d61f40 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md @@ -1,52 +1,47 @@ --- -title: Exportar estatísticas do servidor +title: Exporting Server Statistics shortTitle: Export Server Statistics -intro: 'Você pode usar suas próprias ferramentas para analisar o uso do seu {% data variables.product.prodname_ghe_server %} ao longo do tempo baixando as métricas do {% data variables.product.prodname_server_statistics %} em um arquivo CSV ou JSON.' +intro: 'You can use your own tools to analyze your {% data variables.product.prodname_ghe_server %} usage over time by downloading your {% data variables.product.prodname_server_statistics %} metrics in a CSV or JSON file.' versions: feature: server-statistics redirect_from: - /early-access/github/analyze-how-your-team-works-with-server-statistics/exploring-server-statistics -ms.openlocfilehash: 4e8fa1d040303ec569d11a8a41708ede10b3e76e -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147718162' --- -Você pode baixar até os últimos 365 dias de dados de {% data variables.product.prodname_server_statistics %} em um arquivo CSV ou JSON. Esses dados, que incluem métricas de agregação em repositórios, problemas e solicitações de pull, podem ajudá-lo a antecipar as necessidades de sua organização, entender como sua equipe trabalha e mostrar o valor obtido do {% data variables.product.prodname_ghe_server %}. -Antes de baixar esses dados, você precisa habilitar {% data variables.product.prodname_server_statistics %}. Para obter mais informações, confira "[Como habilitar {% data variables.product.prodname_server_statistics %} em sua empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)". +You can download up to the last 365 days of {% data variables.product.prodname_server_statistics %} data in a CSV or JSON file. This data, which includes aggregate metrics on repositories, issues, and pull requests, can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. -Para visualizar as métricas disponíveis para download, confira "[Sobre {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)." +Before you can download this data, you must enable {% data variables.product.prodname_server_statistics %}. For more information, see "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." -Para baixar essas métricas, você deve ser proprietário de uma empresa ou proprietário de organização em {% data variables.product.prodname_ghe_cloud %}. - - Se {% data variables.product.product_location %} estiver conectado a uma conta corporativa em {% data variables.product.prodname_ghe_cloud %}, confira "[ Baixar métricas de sua conta corporativa](#downloading-metrics-from-your-enterprise-account)". - - Se {% data variables.product.product_location %} estiver conectado a uma organização em {% data variables.product.prodname_ghe_cloud %}, confira "[Baixar métricas de sua organização](#downloading-metrics-from-your-organization)". +To preview the metrics available to download, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)." -Para saber mais sobre {% data variables.product.prodname_github_connect %}, confira "[Sobre o {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)." +To download these metrics, you must be an enterprise owner or organization owner on {% data variables.product.prodname_ghe_cloud %}. + - If {% data variables.location.product_location %} is connected to an enterprise account on {% data variables.product.prodname_ghe_cloud %}, see "[Downloading metrics from your enterprise account](#downloading-metrics-from-your-enterprise-account)." + - If {% data variables.location.product_location %} is connected to an organization on {% data variables.product.prodname_ghe_cloud %}, see "[Downloading metrics from your organization](#downloading-metrics-from-your-organization)." -## Baixar métricas de sua conta corporativa +To learn more about {% data variables.product.prodname_github_connect %}, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)." -1. No canto superior direito do {% data variables.product.prodname_ghe_cloud %} clique na foto do seu perfil e clique em **Suas empresas**. - ![Menu suspenso com a opção "Suas empresas"](/assets/images/help/enterprises/enterprise-admin-account-settings.png) +## Downloading metrics from your enterprise account -2. Ao lado da conta corporativa desejada, clique **em Configurações**. - ![Botão Configurações ao lado da conta de administrador da empresa](/assets/images/help/enterprises/enterprise-admin-account-settings-button.png) +1. In the top-right corner of {% data variables.product.prodname_ghe_cloud %}, click your profile photo, then click **Your enterprises**. + ![Drop down menu with "Your enterprises" option](/assets/images/help/enterprises/enterprise-admin-account-settings.png) -3. À esquerda, clique em **GitHub Connect**. - ![Opção GitHub Connect na conta de administrador da empresa](/assets/images//help/enterprises/enterprise-admin-github-connect.png) +2. Next to your desired enterprise account, click **Settings**. + ![Settings button next to Enterprise admin account](/assets/images/help/enterprises/enterprise-admin-account-settings-button.png) + +3. On the left, click **GitHub Connect**. + ![GitHub Connect option under enterprise admin account](/assets/images//help/enterprises/enterprise-admin-github-connect.png) {% data reusables.server-statistics.csv-download %} -## Baixar métricas de sua organização +## Downloading metrics from your organization -1. No canto superior direito do {% data variables.product.prodname_ghe_cloud %} clique na foto do seu perfil e clique em **Suas organizações**. - ![Menu suspenso com a opção "Suas organizações"](/assets/images/help/enterprises/github-enterprise-cloud-organizations.png) +1. In the top-right corner of {% data variables.product.prodname_ghe_cloud %}, click your profile photo, then click **Your organizations**. + ![Drop down menu with "Your organizations" option](/assets/images/help/enterprises/github-enterprise-cloud-organizations.png) -2. Na lista de organizações, ao lado da organização que está conectada a {% data variables.product.product_location %}, clique em **Configurações**. - ![Botão Configurações ao lado da organização {% data variables.product.prodname_ghe_cloud %}](/assets/images/help/enterprises/settings-for-ghec-org.png) +2. In the list of organizations, next to the organization that's connected to {% data variables.location.product_location %}, click **Settings**. + ![Settings button next to {% data variables.product.prodname_ghe_cloud %} organization](/assets/images/help/enterprises/settings-for-ghec-org.png) -3. À esquerda, clique em **GitHub Connect**. - ![Opção GitHub Connect na barra lateral esquerda das configurações da conta da organização](/assets/images/help/enterprises/github-connect-option-for-ghec-org.png) +3. On the left, click **GitHub Connect**. + ![GitHub Connect option in an organization account settings left sidebar](/assets/images/help/enterprises/github-connect-option-for-ghec-org.png) {% data reusables.server-statistics.csv-download %} diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md index 3b8a255e65..b52e938922 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md @@ -1,7 +1,7 @@ --- -title: Gerenciar webhooks globais +title: Managing global webhooks shortTitle: Manage global webhooks -intro: Você pode configurar webhooks globais para notificar servidores web externos quando os eventos ocorrerem na sua empresa. +intro: You can configure global webhooks to notify external web servers when events occur within your enterprise. permissions: Enterprise owners can manage global webhooks for an enterprise account. redirect_from: - /enterprise/admin/user-management/about-global-webhooks @@ -22,72 +22,79 @@ type: how_to topics: - Enterprise - Webhooks -ms.openlocfilehash: 751a6dc55b9d1aded22a8225f4bf7d058aa32b77 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145095854' --- -## Sobre webhooks globais -Você pode usar webhooks globais para notificar um servidor web externo quando os eventos ocorrerem dentro de sua empresa. Você pode configurar o servidor para receber a carga do webhook e, em seguida, executar um aplicativo ou código que monitora, responde ou aplica regras para gestão de usuários e organizações para a sua empresa. Para obter mais informações, confira "[Webhooks](/developers/webhooks-and-events/webhooks)". +## About global webhooks -Por exemplo, você pode configurar {% data variables.product.product_location %} para enviar um webhook quando alguém criar, excluir ou modificar um repositório ou organização dentro da sua empresa. Você pode configurar o servidor para executar automaticamente uma tarefa depois de receber o webhook. +You can use global webhooks to notify an external web server when events occur within your enterprise. You can configure the server to receive the webhook's payload, then run an application or code that monitors, responds to, or enforces rules for user and organization management for your enterprise. For more information, see "[Webhooks](/developers/webhooks-and-events/webhooks)." -![Lista de webhooks globais](/assets/images/enterprise/site-admin-settings/list-of-global-webhooks.png) +For example, you can configure {% data variables.location.product_location %} to send a webhook when someone creates, deletes, or modifies a repository or organization within your enterprise. You can configure the server to automatically perform a task after receiving the webhook. + +![List of global webhooks](/assets/images/enterprise/site-admin-settings/list-of-global-webhooks.png) {% data reusables.enterprise_user_management.manage-global-webhooks-api %} -## Adicionar um webhook global +## Adding a global webhook -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.hooks-tab %} -5. Clique em **Adicionar webhook**. - ![Botão Adicionar webhook na página Webhooks na central de administração](/assets/images/enterprise/site-admin-settings/add-global-webhook-button.png) -6. Digite a URL em que você gostaria de receber cargas. - ![Campo usado para digitar a URL de conteúdo](/assets/images/enterprise/site-admin-settings/add-global-webhook-payload-url.png) -7. Opcionalmente, use o menu suspenso **Tipo de conteúdo** e clique em um formato de conteúdo. - ![Menu suspenso com opções de tipo de conteúdo da listagem](/assets/images/enterprise/site-admin-settings/add-global-webhook-content-type-dropdown.png) -8. Opcionalmente, no campo **Segredo**, digite uma cadeia de caracteres a ser usada como uma chave `secret`. - ![Campo usado para digitar uma cadeia de caracteres para usá-la como uma chave secreta](/assets/images/enterprise/site-admin-settings/add-global-webhook-secret.png) -9. Opcionalmente, se a URL de conteúdo for HTTPS e você não quiser que o {% data variables.product.prodname_ghe_server %} para verificar os certificados SSL ao fornecer o conteúdo, selecione **Desabilitar a verificação SSL**. Leia as informações sobre a verificação SSL e clique em **Entendi que meus webhooks podem não estar seguros**. - ![Caixa de seleção usada para desabilitar a verificação SSL](/assets/images/enterprise/site-admin-settings/add-global-webhook-disable-ssl-button.png) +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +5. Click **Add webhook**. + ![Add webhook button on Webhooks page in Admin center](/assets/images/enterprise/site-admin-settings/add-global-webhook-button.png) +6. Type the URL where you'd like to receive payloads. + ![Field to type a payload URL](/assets/images/enterprise/site-admin-settings/add-global-webhook-payload-url.png) +7. Optionally, use the **Content type** drop-down menu, and click a payload format. + ![Drop-down menu listing content type options](/assets/images/enterprise/site-admin-settings/add-global-webhook-content-type-dropdown.png) +8. Optionally, in the **Secret** field, type a string to use as a `secret` key. + ![Field to type a string to use as a secret key](/assets/images/enterprise/site-admin-settings/add-global-webhook-secret.png) +9. Optionally, if your payload URL is HTTPS and you would not like {% data variables.product.prodname_ghe_server %} to verify SSL certificates when delivering payloads, select **Disable SSL verification**. Read the information about SSL verification, then click **I understand my webhooks may not be secure**. + ![Checkbox for disabling SSL verification](/assets/images/enterprise/site-admin-settings/add-global-webhook-disable-ssl-button.png) {% warning %} - **Aviso:** a verificação SSL ajuda a garantir que o conteúdo do gancho seja entregue com segurança. Não é recomendável desabilitar a verificação SSL. + **Warning:** SSL verification helps ensure that hook payloads are delivered securely. We do not recommend disabling SSL verification. {% endwarning %} -10. Decida se você quer que o webhook seja acionado para todos os eventos ou somente para determinados eventos. - ![Botões com opções de receber conteúdo de todos os eventos ou de eventos específicos](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-events.png) - - Para cada evento, selecione **Enviar-me tudo**. - - Para escolher eventos específicos, selecione **Deixe-me selecionar eventos individuais**. -11. Se você escolher eventos individuais, selecione os eventos que acionarão o webhook. - {% ifversion ghec %} ![Caixas de seleção para eventos de webhook global individual](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events.png) {% elsif ghes or ghae %} ![Caixas de seleção para eventos de webhook global individual](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events-ghes-and-ae.png) {% endif %} -12. Confirme se a caixa de seleção **Ativa** está marcada. - ![Caixa de seleção Ativo marcada](/assets/images/help/business-accounts/webhook-active.png) -13. Clique em **Adicionar webhook**. +10. Decide if you'd like this webhook to trigger for every event or for selected events. + ![Radio buttons with options to receive payloads for every event or selected events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-events.png) + - For every event, select **Send me everything**. + - To choose specific events, select **Let me select individual events**. +11. If you chose to select individual events, select the events that will trigger the webhook. + {% ifversion ghec %} + ![Checkboxes for individual global webhook events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events.png) + {% elsif ghes or ghae %} + ![Checkboxes for individual global webhook events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events-ghes-and-ae.png) + {% endif %} +12. Confirm that the **Active** checkbox is selected. + ![Selected Active checkbox](/assets/images/help/business-accounts/webhook-active.png) +13. Click **Add webhook**. -## Editar um webhook global +## Editing a global webhook -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.hooks-tab %} -5. Ao lado do webhook que deseja editar, clique em **Editar**. - ![Botão Editar ao lado de um webhook](/assets/images/enterprise/site-admin-settings/edit-global-webhook-button.png) -6. Atualize as configurações do webhook. -7. Clique em **Atualizar webhook**. +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +5. Next to the webhook you'd like to edit, click **Edit**. + ![Edit button next to a webhook](/assets/images/enterprise/site-admin-settings/edit-global-webhook-button.png) +6. Update the webhook's settings. +7. Click **Update webhook**. -## Excluir um webhook global +## Deleting a global webhook -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.hooks-tab %} -5. Ao lado do webhook que deseja excluir, clique em **Excluir**. - ![Botão Excluir ao lado de um webhook](/assets/images/enterprise/site-admin-settings/delete-global-webhook-button.png) -6. Leia as informações sobre como excluir um webhook e clique em **Sim, excluir webhook**. - ![Caixa pop-up com informações de aviso e botão usado para confirmar a exclusão do webhook](/assets/images/enterprise/site-admin-settings/confirm-delete-global-webhook.png) +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +5. Next to the webhook you'd like to delete, click **Delete**. + ![Delete button next to a webhook](/assets/images/enterprise/site-admin-settings/delete-global-webhook-button.png) +6. Read the information about deleting a webhook, then click **Yes, delete webhook**. + ![Pop-up box with warning information and button to confirm deleting the webhook](/assets/images/enterprise/site-admin-settings/confirm-delete-global-webhook.png) -## Exibir respostas e entregas recentes +## Viewing recent deliveries and responses -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.hooks-tab %} -5. Na lista de webhooks, clique no webhook em que você gostaria de ver entregas. - ![Lista de webhooks com links para visualizar cada webhook](/assets/images/enterprise/site-admin-settings/click-global-webhook.png) -6. Em "Recent deliveries" (Entregas recentes), clique em uma entrega para ver detalhes. - ![Lista das entregas recentes do webhook com links para visualizar os detalhes](/assets/images/enterprise/site-admin-settings/global-webhooks-recent-deliveries.png) +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +5. In the list of webhooks, click the webhook for which you'd like to see deliveries. + ![List of webhooks with links to view each webhook](/assets/images/enterprise/site-admin-settings/click-global-webhook.png) +6. Under "Recent deliveries", click a delivery to view details. + ![List of the webhook's recent deliveries with links to view details](/assets/images/enterprise/site-admin-settings/global-webhooks-recent-deliveries.png) diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md index 2da60940c7..863a314cec 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md @@ -28,7 +28,7 @@ topics: The scope of the events that appear in your enterprise's audit log depend on whether your enterprise uses {% data variables.product.prodname_emus %}. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)." - If your enterprise does not use {% data variables.product.prodname_emus %}, the audit log only includes events related to the enterprise account and the organizations within the enterprise account, which are listed in this article. -- If your enterprise uses {% data variables.product.prodname_emus %}, the audit log also includes user events for {% data variables.product.prodname_managed_users %}, such as each time the user logs in to {% data variables.product.product_name %}. For a list of these events, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log#security-log-actions)." +- If your enterprise uses {% data variables.product.prodname_emus %}, the audit log also includes user events for {% data variables.enterprise.prodname_managed_users %}, such as each time the user logs in to {% data variables.product.product_name %}. For a list of these events, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log#security-log-actions)." {% endif %} {%- ifversion fpt or ghec %} @@ -159,6 +159,32 @@ The scope of the events that appear in your enterprise's audit log depend on whe | `business.update_saml_provider_settings` | The SAML single sign-on provider settings for an enterprise were updated. {%- endif %} +{% ifversion code-security-audit-log-events %} + +## `business_advanced_security` category actions + +| Action | Description +|--------|------------- +| `business_advanced_security.disabled` | {% data variables.product.prodname_GH_advanced_security %} was disabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_advanced_security.enabled` | {% data variables.product.prodname_GH_advanced_security %} was enabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_advanced_security.disabled_for_new_repos` | {% data variables.product.prodname_GH_advanced_security %} was disabled for new repositories in your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_advanced_security.enabled_for_new_repos` | {% data variables.product.prodname_GH_advanced_security %} was enabled for new repositories in your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." + +{% endif %} + +{% ifversion code-security-audit-log-events %} + +## `business_secret_scanning` category actions + +| Action | Description +|--------|------------- +| `business_secret_scanning.disable` | {% data variables.product.prodname_secret_scanning_caps %} was disabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_secret_scanning.enable` | {% data variables.product.prodname_secret_scanning_caps %} was enabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_secret_scanning.disabled_for_new_repos` | {% data variables.product.prodname_secret_scanning_caps %} was disabled for new repositories in your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_secret_scanning.enabled_for_new_repos` | {% data variables.product.prodname_secret_scanning_caps %} was enabled for new repositories in your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." + +{% endif %} + {%- ifversion secret-scanning-audit-log-custom-patterns %} ## `business_secret_scanning_custom_pattern` category actions @@ -169,6 +195,31 @@ Action | Description | `business_secret_scanning_custom_pattern.update` | Changes to an enterprise-level custom pattern are saved for secret scanning. {%- endif %} +{% ifversion code-security-audit-log-events %} + +## `business_secret_scanning_push_protection` category actions + +| Action | Description +|--------|------------- +| `business_secret_scanning_push_protection.disable` | Push protection for {% data variables.product.prodname_secret_scanning %} was disabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_secret_scanning_push_protection.enable` | Push protection for {% data variables.product.prodname_secret_scanning %} was enabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_secret_scanning_push_protection.disabled_for_new_repos` | Push protection for {% data variables.product.prodname_secret_scanning %} was disabled for new repositories in your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_secret_scanning_push_protection.enabled_for_new_repos` | Push protection for {% data variables.product.prodname_secret_scanning %} was enabled for new repositories in your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." + +{% endif %} + +{% ifversion code-security-audit-log-events %} + +## `business_secret_scanning_push_protection_custom_message` category actions + +| Action | Description +|--------|------------- +| `business_secret_scanning_push_protection_custom_message.disable` | The custom message triggered by an attempted push to a push-protected repository was disabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_secret_scanning_push_protection_custom_message.enable` | The custom message triggered by an attempted push to a push-protected repository was enabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_secret_scanning_push_protection_custom_message.update` | The custom message triggered by an attempted push to a push-protected repository was updated for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." + +{% endif %} + ## `checks` category actions | Action | Description @@ -436,7 +487,7 @@ Before you'll see `git` category actions, you must enable Git events in the audi | `integration.revoke_all_tokens` | All user tokens for an integration were requested to be revoked. | `integration.revoke_tokens` | Token(s) for an integration were revoked. -## `integration_installation`category actions +## `integration_installation` category actions | Action | Description |--------|------------- @@ -573,7 +624,7 @@ Before you'll see `git` category actions, you must enable Git events in the audi | Action | Description |--------|------------- -`oauth_access.create` | An [OAuth access token][] was generated for a user account. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." +`oauth_access.create` | An [OAuth access token][] was generated for a user account. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." `oauth_access.destroy` | An [OAuth access token][] was deleted from a user account. [OAuth access token]: /developers/apps/building-oauth-apps/authorizing-oauth-apps @@ -717,6 +768,11 @@ Before you'll see `git` category actions, you must enable Git events in the audi {%- ifversion fpt or ghec %} | `org.runner_group_visiblity_updated` | The visibility of a self-hosted runner group was updated via the REST API. For more information, see "[Update a self-hosted runner group for an organization](/rest/reference/actions#update-a-self-hosted-runner-group-for-an-organization)." {%- endif %} +{%- ifversion code-security-audit-log-events %} +| `org.secret_scanning_push_protection_custom_message_disabled` | The custom message triggered by an attempted push to a push-protected repository was disabled for your organization. For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#enabling-secret-scanning-as-a-push-protection-for-an-organization)." +| `org.secret_scanning_push_protection_custom_message_enabled` | The custom message triggered by an attempted push to a push-protected repository was enabled for your organization. For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#enabling-secret-scanning-as-a-push-protection-for-an-organization)." +| `org.secret_scanning_push_protection_custom_message_updated` | The custom message triggered by an attempted push to a push-protected repository was updated for your organization. For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#enabling-secret-scanning-as-a-push-protection-for-an-organization)." +{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `org.secret_scanning_push_protection_disable` | An organization owner or administrator disabled push protection for secret scanning. For more information, see "[Protecting pushes with secret scanning](/enterprise-cloud@latest/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." | `org.secret_scanning_push_protection_enable` | An organization owner or administrator enabled push protection for secret scanning. diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md index 57f7c84f2b..0bcdaf5744 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md @@ -1,8 +1,8 @@ --- -title: Configurando o log de auditoria da sua empresa -intro: Você pode definir as configurações do log de auditoria da sua empresa. +title: Configuring the audit log for your enterprise +intro: "You can configure settings for your enterprise's audit log." shortTitle: Configure audit logs -permissions: Enterprise owners can configure the audit log. +permissions: 'Enterprise owners can configure the audit log.' versions: feature: audit-data-retention-tab type: how_to @@ -10,45 +10,47 @@ topics: - Auditing - Enterprise - Logging -ms.openlocfilehash: 79bf5f2ae2f1b2762ea32a6bef85b04e9cf95739 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424845' --- -## Sobre a configuração do log de auditoria -Você pode configurar um período de retenção para dados de log de auditoria e ver os detalhes do armazenamento de índice. +## About audit log configuration -{% ifversion enable-git-events %} Depois de configurar um período de retenção, você pode habilitar ou desabilitar eventos relacionados ao Git de aparecerem no log de auditoria. -{% endif %} - -## Configurando um período de retenção para dados de log de auditoria - -Você pode configurar um período de retenção para dados de log de auditoria para {% data variables.product.product_location %}. Os dados que excederem o período configurado serão removidos permanentemente do disco. - -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} {% data reusables.audit_log.audit-data-retention-tab %} -1. Em "Definir configurações de retenção de log de auditoria", selecione o menu suspenso e clique em um período de retenção. - - ![Captura de tela do menu suspenso para configurações de retenção de log de auditoria](/assets/images/help/enterprises/audit-log-retention-dropdown.png) -1. Clique em **Salvar**. +You can configure a retention period for audit log data and see index storage details. {% ifversion enable-git-events %} -## Gerenciando eventos Git no log de auditoria +After you configure a retention period, you can enable or disable Git-related events from appearing in the audit log. +{% endif %} -Você pode habilitar ou desabilitar eventos relacionados ao Git, como `git.clone` e `git.push`, de aparecer em seu log de auditoria. Para obter uma lista dos eventos Git que são registrados, confira "[Auditar eventos de log para sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)". +## Configuring a retention period for audit log data -Se você habilitar os eventos Git, devido ao grande número de eventos Git registrados, recomendamos monitorar o armazenamento de arquivos da sua instância e examinar suas configurações de alerta relacionadas. Para obter mais informações, confira "[Monitorar o armazenamento](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)". +You can configure a retention period for audit log data for {% data variables.location.product_location %}. Data that exceeds the period you configure will be permanently removed from disk. -Para habilitar eventos Git no log de auditoria, configure um período de retenção para dados de log de auditoria que não sejam "infinitos". Para obter mais informações, confira "[Configurar um período de retenção para dados de log de auditoria](#configuring-a-retention-period-for-audit-log-data)". +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.audit-log-tab %} +{% data reusables.audit_log.audit-data-retention-tab %} +1. Under "Configure audit log retention settings", select the dropdown menu and click a retention period. + + ![Screenshot of the dropdown menu for audit log retention settings](/assets/images/help/enterprises/audit-log-retention-dropdown.png) +1. Click **Save**. + +{% ifversion enable-git-events %} +## Managing Git events in the audit log + +You can enable or disable Git-related events, such as `git.clone` and `git.push`, from appearing in your audit log. For a list of the Git events are are logged, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)." + +If you do enable Git events, due to the large number of Git events that are logged, we recommend monitoring your instance's file storage and reviewing your related alert configurations. For more information, see "[Monitoring storage](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)." + +Before you can enable Git events in the audit log, you must configure a retention period for audit log data other than "infinite." For more information, see "[Configuring a retention period for audit log data](#configuring-a-retention-period-for-audit-log-data)." {% data reusables.audit_log.git-events-not-in-search-results %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} {% data reusables.audit_log.audit-data-retention-tab %} -1. Em "Aceitação de evento Git", marque ou desmarque **Habilitar eventos Git no log de auditoria**. +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.audit-log-tab %} +{% data reusables.audit_log.audit-data-retention-tab %} +1. Under "Git event opt-in", select or deselect **Enable git events in the audit-log**. - ![Captura de tela da caixa de seleção para habilitar eventos Git no log de auditoria](/assets/images/help/enterprises/enable-git-events-checkbox.png) -1. Clique em **Salvar**. + ![Screenshot of the checkbox to enable Git events in the audit log](/assets/images/help/enterprises/enable-git-events-checkbox.png) +1. Click **Save**. -{% endif %} +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md index c8d4d1bb80..540bbcda05 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Exibir endereços IP no log de auditoria da sua empresa -intro: Você pode exibir o endereço IP de origem para eventos no log de auditoria da sua empresa. +title: Displaying IP addresses in the audit log for your enterprise +intro: You can display the source IP address for events in your enterprise's audit log. shortTitle: IP addresses in audit log permissions: Enterprise owners can display IP addresses in the audit log for an enterprise. versions: @@ -12,44 +12,41 @@ topics: - Logging - Networking - Security -ms.openlocfilehash: 7dad3642866b637432442591d8e5714e3db6f59f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147508072' --- -## Sobre a exibição de endereços IP no log de auditoria -Por padrão, o {% data variables.product.product_name %} não exibe o endereço IP de origem para eventos no log de auditoria da sua empresa. Opcionalmente, para garantir a conformidade e responder a ameaças, você pode exibir o endereço IP completo associado ao ator responsável por cada evento. Normalmente, os atores são usuários, mas também podem ser aplicativos ou integrações. +## About display of IP addresses in the audit log -Você é responsável por cumprir todas as obrigações legais que acompanham a exibição ou o armazenamento de endereços IP exibidos no log de auditoria da sua empresa. +By default, {% data variables.product.product_name %} does not display the source IP address for events in your enterprise's audit log. Optionally, to ensure compliance and respond to threats, you can display the full IP address associated with the actor responsible for each event. Actors are typically users, but can also be apps or integrations. -Se você optar por exibir endereços IP, eles só aparecerão no log de auditoria da sua empresa. Os endereços IP não serão exibidos para eventos nos logs de auditoria de organizações individuais pertencentes à sua empresa. Para obter mais informações sobre os logs de auditoria da sua organização, confira "[Como revisar o log de auditoria para sua organização](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)". +You are responsible for meeting any legal obligations that accompany the viewing or storage of IP addresses displayed within your enterprise's audit log. -Você pode exibir endereços IP no log de auditoria independentemente do método de autenticação usado para sua empresa no {% data variables.product.product_location %}. Para obter mais informações, consulte "[Sobre a autenticação para sua empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)". +If you choose to display IP addresses, the IP addresses only appear in your enterprise's audit log. IP addresses will not appear for events in the audit logs for individual organizations owned by your enterprise. For more information about organization audit logs, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)." -Quando qualquer pessoa cria uma conta no {% data variables.product.product_location %}, a pessoa concorda com a coleta de informações básicas do {% data variables.product.company_short %} sobre conexões com serviços do {% data variables.product.company_short %}, incluindo o endereço IP de origem. Para obter mais informações, confira "[Política de Privacidade do GitHub](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#usage-information)". +You can display IP addresses in the audit log regardless of which authentication method you use for your enterprise on {% data variables.location.product_location %}. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)." -## Eventos que exibem endereços IP no log de auditoria +When anyone creates an account on {% data variables.location.product_location %}, the person agrees to {% data variables.product.company_short %}'s collection of basic information about connections to {% data variables.product.company_short %}'s services, including source IP address. For more information, see "[GitHub Privacy Statement](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#usage-information)." -O {% data variables.product.product_name %} exibe um endereço IP no log de auditoria quando um membro da empresa interage com um recurso pertencente à sua empresa ou a uma organização em sua empresa. Por exemplo, você verá um endereço IP para eventos auditados envolvendo um repositório interno ou privado pertencente a uma organização em sua empresa ou recursos associados a esses repositórios, como um problema, uma solicitação de pull, uma ação ou um projeto. +## Events that display IP addresses in the audit log -Se os membros da sua empresa acessarem o {% data variables.product.product_location %} com contas pessoais que eles gerenciam, porque você não usa o {% data variables.product.prodname_emus %}, o {% data variables.product.product_name %} não exibirá um evento ou endereço IP no log de auditoria para as ações a seguir. +{% data variables.product.product_name %} displays an IP address in the audit log when a member of the enterprise interacts with a resource owned by your enterprise or an organization in your enterprise. For example, you will see an IP address for audited events involving an internal or private repository owned by an organization in your enterprise, or resources associated with those repositories, such as an issue, pull request, action, or project. + +If members of your enterprise access {% data variables.location.product_location %} with personal accounts that they manage, because you do not use {% data variables.product.prodname_emus %}, {% data variables.product.product_name %} does not display an event or IP address in the audit log for the following actions. -- Autenticação no {% data variables.product.product_location %} -- Interações com um recurso pertencente à conta pessoal, incluindo repositório, gist ou projeto -- Interações com um repositório público de propriedade de uma organização em sua empresa +- Authentication to {% data variables.location.product_location %} +- Interactions with a resource owned by the personal account, including a repository, gist, or project +- Interactions with a public repository owned by an organization in your enterprise -## Habilitar a exibição de endereços IP no log de auditoria +## Enabling display of IP addresses in the audit log -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} -1. Em "Log de auditoria", clique em **Divulgação do IP de origem**. +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.audit-log-tab %} +1. Under "Audit log", click **Source IP disclosure**. - ![Captura de tela da guia "Divulgação do IP de origem"](/assets/images/help/enterprises/audit-log-source-ip-disclosure-tab.png) -1. Em "Divulgar endereços IP de ator nos logs de auditoria", selecione **Habilitar divulgação do IP de origem**. + ![Screenshot of "Source IP disclosure" tab](/assets/images/help/enterprises/audit-log-source-ip-disclosure-tab.png) +1. Under "Disclose actor IP addresses in audit logs", select **Enable source IP disclosure**. - ![Captura de tela da caixa de seleção para habilitar a exibição de endereços IP nos logs de auditoria](/assets/images/help/enterprises/audit-log-enable-source-ip-disclosure-checkbox.png) -1. Clique em **Save** (Salvar). + ![Screenshot of checkbox to enable display of IP addresses in audit logs](/assets/images/help/enterprises/audit-log-enable-source-ip-disclosure-checkbox.png) +1. Click **Save**. -Depois de habilitar o recurso, você poderá acessar o log de auditoria para exibir eventos que incluem endereços IP. Para obter mais informações, confira "[Como acessar o log de auditoria da sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)". +After you enable the feature, you can access the audit log to view events that include IP addresses. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)." diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md index 643a2ff328..7ef4d78ae4 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md @@ -311,7 +311,7 @@ To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint you must ma {% ifversion pause-audit-log-stream %} ## Pausing audit log streaming -Pausing the stream allows you to perform maintenance on the receiving application without losing audit data. Audit logs are stored for up to seven days on {% data variables.product.product_location %} and are then exported when you unpause the stream. +Pausing the stream allows you to perform maintenance on the receiving application without losing audit data. Audit logs are stored for up to seven days on {% data variables.location.product_location %} and are then exported when you unpause the stream. {% ifversion streaming-datadog %} Datadog only accepts logs from up to 18 hours in the past. If you pause a stream to a Datadog endpoint for more than 18 hours, you risk losing logs that Datadog won't accept after you resume streaming. diff --git a/translations/pt-BR/content/admin/overview/about-data-residency.md b/translations/pt-BR/content/admin/overview/about-data-residency.md index 9b63ba07f6..1147142dd9 100644 --- a/translations/pt-BR/content/admin/overview/about-data-residency.md +++ b/translations/pt-BR/content/admin/overview/about-data-residency.md @@ -1,21 +1,16 @@ --- -title: Sobre a residência de dados -intro: 'Você pode escolher a localidade onde {% data variables.product.product_name %} armazena todos os dados de clientes da sua empresa.' +title: About data residency +intro: 'You can choose the geography where {% data variables.product.product_name %} stores all customer data for your enterprise.' versions: ghae: '*' type: overview topics: - Enterprise - Fundamentals -ms.openlocfilehash: b182073799b1f45b697bef47a4314644bc8a52b1 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145094600' --- -{% data reusables.github-ae.github-ae-enables-you %} Você pode escolher a localidade onde você armazena todos os dados do cliente para {% data variables.product.product_location %}, e os integrantes da sua empresa poderão acessar {% data variables.product.product_name %} de qualquer lugar do mundo. -Ao criar a sua empresa, você pode informar {% data variables.contact.contact_enterprise_sales %} onde armazenar os dados dos seus clientes. {% data variables.product.company_short %} não armazenará nem transferirá nenhum dos dados da sua empresa para fora da localidade escolhida. +{% data reusables.github-ae.github-ae-enables-you %} You can choose the geography where you store all the customer data for {% data variables.location.product_location %}, and members of your enterprise can access {% data variables.product.product_name %} from anywhere in the world. -Para obter mais informações sobre a localidade disponível, entre em contato com {% data variables.contact.contact_enterprise_sales %}. +When creating your enterprise, you can tell {% data variables.contact.contact_enterprise_sales %} where to store your customer data. {% data variables.product.company_short %} will not store or move any of your enterprise's data outside of the geography you choose. + +For more information about the available geographies, contact {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md index 91fda8eae9..feb02861bf 100644 --- a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md +++ b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md @@ -1,6 +1,6 @@ --- -title: Sobre contas corporativas -intro: 'Com {% data variables.product.product_name %}, você pode usar uma conta corporativa para {% ifversion ghec %}habilitar a colaboração entre suas organizações, ao mesmo tempo em que oferece{% elsif ghes or ghae %}give{% endif %} aos administradores um único ponto de visibilidade e gestão.' +title: About enterprise accounts +intro: 'With {% data variables.product.product_name %}, you can use an enterprise account to {% ifversion ghec %}enable collaboration between your organizations, while giving{% elsif ghes or ghae %}give{% endif %} administrators a single point of visibility and management.' redirect_from: - /articles/about-github-business-accounts - /articles/about-enterprise-accounts @@ -18,87 +18,83 @@ topics: - Accounts - Enterprise - Fundamentals -ms.openlocfilehash: 3233b52c1710c07dbd09644f7b38b7da697075c1 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147526651' --- -## Sobre contas corporativas em {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% else %}{% data variables.product.product_name %}{% endif %} + +## About enterprise accounts on {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% else %}{% data variables.product.product_name %}{% endif %} {% ifversion ghec %} -Sua conta corporativa no {% data variables.product.prodname_dotcom_the_website %} permite que você gerencie múltiplas organizações. Sua conta corporativa deve ter um manipulador, como uma conta de usuário ou organizacional no {% data variables.product.prodname_dotcom %}. +Your enterprise account on {% data variables.product.prodname_dotcom_the_website %} allows you to manage multiple organizations. Your enterprise account must have a handle, like an organization or user account on {% data variables.product.prodname_dotcom %}. {% elsif ghes or ghae %} -A conta corporativa em {% ifversion ghes %}{% data variables.product.product_location_enterprise %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} permite que você gerencie as organizações{% ifversion ghes %} em{% elsif ghae %} pertencentes à{% endif %} sua instância {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% elsif ghae %}empresa{% endif %}. +The enterprise account on {% ifversion ghes %}{% data variables.location.product_location_enterprise %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} allows you to manage the organizations{% ifversion ghes %} on{% elsif ghae %} owned by{% endif %} your {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} instance{% elsif ghae %}enterprise{% endif %}. {% endif %} -As organizações são contas compartilhadas em que os integrantes da empresa podem colaborar em muitos projetos de uma só vez. Os proprietários da organização podem gerenciar o acesso aos dados e projetos da organização, com recursos sofisticados de segurança e administrativos. Para obter mais informações, confira "[Sobre as organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)". +Organizations are shared accounts where enterprise members can collaborate across many projects at once. Organization owners can manage access to the organization's data and projects with sophisticated security and administrative features. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." -{% ifversion ghec %} Os proprietários de empresas podem convidar organizações existentes para ingressar em sua conta corporativa ou criar novas organizações nas configurações corporativas. Para obter mais informações, confira "[Como adicionar organizações à sua empresa](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)". +{% ifversion ghec %} +Enterprise owners can invite existing organizations to join your enterprise account, or create new organizations in the enterprise settings. For more information, see "[Adding organizations to your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)." {% endif %} -Sua conta corporativa permite que você gerencie e aplique políticas para todas as organizações pertencentes à empresa. {% data reusables.enterprise.about-policies %} Para ver mais informações, confira "[Sobre políticas corporativas](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)". +Your enterprise account allows you to manage and enforce policies for all the organizations owned by the enterprise. {% data reusables.enterprise.about-policies %} For more information, see "[About enterprise policies](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)." {% ifversion ghec %} -{% data reusables.enterprise.create-an-enterprise-account %} Para obter mais informações, confira "[Como criar uma conta corporativa](/admin/overview/creating-an-enterprise-account)". +{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)." {% endif %} -## Sobre a administração da conta corporativa +## About administration of your enterprise account {% ifversion ghes or ghae %} -Na sua conta corporativa em {% ifversion ghae %}{% data variables.product.product_name %}{% elsif ghes %}uma instância de {% data variables.product.prodname_ghe_server %}{% endif %}, os administradores podem visualizar{% ifversion remove-enterprise-members %} e gerenciar{% endif %} membros corporativos{% ifversion enterprise-owner-join-org %}, gerenciar seus próprios integrantes em organizações pertencentes à empresa,{% endif %} e gerenciar o seguinte para a instância da {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% elsif ghae %}empresa em {% data variables.product.prodname_ghe_managed %}{% endif %}. +From your enterprise account on {% ifversion ghae %}{% data variables.product.product_name %}{% elsif ghes %}a {% data variables.product.prodname_ghe_server %} instance{% endif %}, administrators can view{% ifversion remove-enterprise-members %} and manage{% endif %} enterprise membership{% ifversion enterprise-owner-join-org %}, manage their own membership in organizations owned by the enterprise,{% endif %} and manage the following for the {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} instance{% elsif ghae %}enterprise on {% data variables.product.prodname_ghe_managed %}{% endif %}. {% ifversion ghes %} -- Uso da licença{% endif %} -- Segurança ({% ifversion ghae %}logon único, listas de permissão de IP, {% endif %}autoridades de certificação SSH, autenticação de dois fatores) -- Políticas corporativas para organizações pertencentes à conta corporativa +- License usage{% endif %} +- Security ({% ifversion ghae %}single sign-on, IP allow lists, {% endif %}SSH certificate authorities, two-factor authentication) +- Enterprise policies for organizations owned by the enterprise account {% endif %} {% ifversion ghes %} -### Sobre a administração da conta corporativa em {% data variables.product.prodname_ghe_cloud %} +### About administration of your enterprise account on {% data variables.product.prodname_ghe_cloud %} {% endif %} -{% ifversion ghec or ghes %}Ao experimentar ou comprar {% data variables.product.prodname_enterprise %}, você também pode{% ifversion ghes %}{% endif %} criar uma conta corporativa para {% data variables.product.prodname_ghe_cloud %} em {% data variables.product.prodname_dotcom_the_website %}. Os administradores da conta corporativa em {% data variables.product.prodname_dotcom_the_website %} podem ver {% ifversion remove-enterprise-members %} e gerenciar{% endif %} a associação corporativa{% ifversion enterprise-owner-join-org %}, gerenciar seus próprios integrantes em organizações pertencentes à empresa,{% endif %} e gerencia o seguinte para a conta corporativa{% ifversion ghes %} em {% data variables.product.prodname_dotcom_the_website %}{% endif %}. +{% ifversion ghec or ghes %}When you try or purchase {% data variables.product.prodname_enterprise %}, you can{% ifversion ghes %} also{% endif %} create an enterprise account for {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_dotcom_the_website %}. Administrators for the enterprise account on {% data variables.product.prodname_dotcom_the_website %} can view {% ifversion remove-enterprise-members %} and manage{% endif %} enterprise membership{% ifversion enterprise-owner-join-org %}, manage their own membership in organizations owned by the enterprise,{% endif %} and manage the following for the enterprise account{% ifversion ghes %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %}. -- Cobrança e uso (serviços em {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_GH_advanced_security %}, licenças de usuários) -- Segurança (logon único, listas de permissão de IP, autoridades de certificação SSH, autenticação de dois fatores) -- Políticas corporativas para organizações pertencentes à conta corporativa +- Billing and usage (services on {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_GH_advanced_security %}, user licenses) +- Security (single sign-on, IP allow lists, SSH certificate authorities, two-factor authentication) +- Enterprise policies for organizations owned by the enterprise account -Se você usar {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_server %}, você também pode gerenciar o seguinte para {% data variables.product.prodname_ghe_server %} na sua conta corporativa em {% data variables.product.prodname_dotcom_the_website %}. +If you use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}, you can also manage the following for {% data variables.product.prodname_ghe_server %} from your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. -- Cobrança e uso para instâncias de {% data variables.product.prodname_ghe_server %} -- Solicitações e compartilhamento de pacote de suporte com {% data variables.contact.enterprise_support %} +- Billing and usage for {% data variables.product.prodname_ghe_server %} instances +- Requests and support bundle sharing with {% data variables.contact.enterprise_support %} -Você também pode conectar a conta corporativa em {% data variables.product.product_location_enterprise %} à sua conta corporativa em {% data variables.product.prodname_dotcom_the_website %} para ver os detalhes de uso da licença para sua assinatura {% data variables.product.prodname_enterprise %} de {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, confira {% ifversion ghec %}"[Como sincronizar o uso da licença entre o {% data variables.product.prodname_ghe_server %} e o {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" na documentação do {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}"[Como sincronizar o uso da licença entre o {% data variables.product.prodname_ghe_server %} e o {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)".{% endif %} +You can also connect the enterprise account on {% data variables.location.product_location_enterprise %} to your enterprise account on {% data variables.product.prodname_dotcom_the_website %} to see license usage details for your {% data variables.product.prodname_enterprise %} subscription from {% data variables.product.prodname_dotcom_the_website %}. For more information, see {% ifversion ghec %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."{% endif %} -Para obter mais informações sobre as diferenças entre o {% data variables.product.prodname_ghe_cloud %} e o {% data variables.product.prodname_ghe_server %}, confira "[Produtos do {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/githubs-products)". {% data reusables.enterprise-accounts.to-upgrade-or-get-started %} +For more information about the differences between {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}, see "[{% data variables.product.prodname_dotcom %}'s products](/get-started/learning-about-github/githubs-products)." {% data reusables.enterprise-accounts.to-upgrade-or-get-started %} {% endif %} -## Sobre a cobrança para a sua conta corporativa +## About billing for your enterprise account -A conta corporativa inclui o custo mensal para cada integrante da sua empresa. A conta inclui {% ifversion ghec %}todas as licenças pagas em organizações fora da sua conta corporativa, assinaturas de aplicativos em {% data variables.product.prodname_marketplace %}, {% endif %}{% ifversion ghec or ghae %}serviços adicionais pagos pela empresa{% ifversion ghec %} como pacotes de dados de {% data variables.large_files.product_name_long %},{% endif %} e{% endif %} de uso para {% data variables.product.prodname_GH_advanced_security %}. +The bill for your enterprise account includes the monthly cost for each member of your enterprise. The bill includes {% ifversion ghec %}any paid licenses in organizations outside of your enterprise account, subscriptions to apps in {% data variables.product.prodname_marketplace %}, {% endif %}{% ifversion ghec or ghae %}additional paid services for your enterprise{% ifversion ghec %} like data packs for {% data variables.large_files.product_name_long %},{% endif %} and{% endif %} usage for {% data variables.product.prodname_GH_advanced_security %}. {% ifversion ghec %} -Para obter mais informações sobre a cobrança da sua assinatura do {% data variables.product.prodname_ghe_cloud %}, confira "[Como ver a assinatura e o uso da sua conta corporativa](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" e "[Sobre a cobrança para sua empresa](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)". +For more information about billing for your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" and "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)." {% elsif ghes %} {% data reusables.enterprise-accounts.enterprise-accounts-billing %} -Para obter mais informações sobre a cobrança do {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% else %}{% data variables.product.product_name %}{% endif %}, confira "[Sobre a cobrança para sua empresa](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)". +For more information about billing for {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% else %}{% data variables.product.product_name %}{% endif %}, see "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)." {% endif %} @@ -106,10 +102,10 @@ Para obter mais informações sobre a cobrança do {% ifversion ghec %}{% data v {% ifversion ghec %} -O {% data variables.product.prodname_enterprise %} oferece duas opções de implantação. Além de {% data variables.product.prodname_ghe_cloud %}, você pode usar {% data variables.product.prodname_ghe_server %} para hospedar o trabalho de desenvolvimento da sua empresa no centro de dados ou no provedor de nuvem compatível. {% endif %}Os proprietários de empresas em {% data variables.product.prodname_dotcom_the_website %} podem usar uma conta corporativa para gerenciar pagamentos e licenciamento para instâncias de {% data variables.product.prodname_ghe_server %}. Para obter mais informações, confira "[Produtos do {% data variables.product.company_short %}](/get-started/learning-about-github/githubs-products#github-enterprise)" e "[Como gerenciar sua licença do {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)". +{% data variables.product.prodname_enterprise %} offers two deployment options. In addition to {% data variables.product.prodname_ghe_cloud %}, you can use {% data variables.product.prodname_ghe_server %} to host development work for your enterprise in your data center or supported cloud provider. {% endif %}Enterprise owners on {% data variables.product.prodname_dotcom_the_website %} can use an enterprise account to manage payment and licensing for {% data variables.product.prodname_ghe_server %} instances. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products#github-enterprise)" and "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)." {% endif %} -## Leitura adicional +## Further reading -- "[Contas Enterprise](/graphql/guides/managing-enterprise-accounts)" na documentação da API do GraphQL +- "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)" in the GraphQL API documentation diff --git a/translations/pt-BR/content/admin/overview/about-github-enterprise-server.md b/translations/pt-BR/content/admin/overview/about-github-enterprise-server.md index 31463957b5..c3b54b8acf 100644 --- a/translations/pt-BR/content/admin/overview/about-github-enterprise-server.md +++ b/translations/pt-BR/content/admin/overview/about-github-enterprise-server.md @@ -1,104 +1,99 @@ --- -title: Sobre o GitHub Enterprise Server -intro: '{% data variables.product.product_name %} é uma plataforma de desenvolvimento de software que você pode hospedar em um ambiente privado.' +title: About GitHub Enterprise Server +intro: '{% data variables.product.product_name %} is a software development platform that you can host in a private environment.' versions: ghes: '*' type: overview topics: - Enterprise - Fundamentals -ms.openlocfilehash: 2622e3708cc31b24fe39929da68ba5dc8e864d88 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147875686' --- -## Sobre o {% data variables.product.product_name %} -{% data reusables.enterprise.ghes-is-a-self-hosted-platform %} Sua equipe pode usar o {% data variables.product.product_name %} para criar e enviar software usando controle de versão Git, APIs avançadas, ferramentas de produtividade e colaboração e integrações. Os desenvolvedores familiarizados com {% data variables.product.prodname_dotcom_the_website %} podem integrar e contribuir diretamente usando recursos e fluxos de trabalho familiares. {% data reusables.enterprise.about-github-for-enterprises %} +## About {% data variables.product.product_name %} + +{% data reusables.enterprise.ghes-is-a-self-hosted-platform %} Your team can use {% data variables.product.product_name %} to build and ship software using Git version control, powerful APIs, productivity and collaboration tools, and integrations. Developers familiar with {% data variables.product.prodname_dotcom_the_website %} can onboard and contribute seamlessly using familiar features and workflows. {% data reusables.enterprise.about-github-for-enterprises %} {% data reusables.enterprise.ghes-runs-on-your-infrastructure %} -{% data reusables.enterprise.github-distributes-ghes %} Para obter mais informações, confira "[Visão geral do sistema](/admin/overview/system-overview)". +{% data reusables.enterprise.github-distributes-ghes %} For more information, see "[System overview](/admin/overview/system-overview)." -Você pode optar por implantar o {% data variables.product.product_name %} no local ou em um ambiente de nuvem com suporte. +You can choose to deploy {% data variables.product.product_name %} on premises, or to a supported cloud environment. -## Ambientes com suporte para implantação +## Supported environments for deployment -Você pode implantar o {% data variables.product.product_name %} em um hipervisor de virtualização no datacenter local ou em um serviço de nuvem pública. +You can deploy {% data variables.product.product_name %} to a virtualization hypervisor within your on-premises datacenter, or to a public cloud service. -O {% data variables.product.company_short %} dá suporte aos hipervisores de virtualização a seguir para implantação local. +{% data variables.product.company_short %} supports the following virtualization hypervisors for on-premises deployment. - Microsoft Hyper-V - OpenStack KVM - VMware ESXi -{% data variables.product.company_short %} dá suporte aos serviços para implantação em nuvem a seguir. +{% data variables.product.company_short %} supports the following services for cloud deployment. -- AWS (Amazon Web Services) -- GCP (Google Cloud Platform) +- Amazon Web Services (AWS) +- Google Cloud Platform (GCP) - Microsoft Azure -Para obter mais informações, confira "[Como configurar uma instância do {% data variables.product.prodname_ghe_server %}](/admin/installation/setting-up-a-github-enterprise-server-instance)". +For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)." -## Sobre versões e atualizações +## About releases and upgrades -{% data reusables.enterprise.constantly-improving %} Você é responsável por atualizações de sua instância. Para obter mais informações, confira "[Versões do {% data variables.product.product_name %}](/admin/all-releases)". +{% data reusables.enterprise.constantly-improving %} You are responsible for upgrades to your instance. For more information, see "[{% data variables.product.product_name %} releases](/admin/all-releases)." -## Sobre a administração +## About administration -Você pode configurar e monitorar o {% data variables.product.product_name %} por meio de navegador, acesso administrativo de SSH e APIs REST ou GraphQL. O {% data variables.product.company_short %} descobriu que as pessoas com experiência de administração do Linux são mais bem-sucedidas com a implantação e a manutenção do {% data variables.product.product_name %}. +You can configure and monitor {% data variables.product.product_name %} via browser, administrative SSH access, and REST or GraphQL APIs. {% data variables.product.company_short %} has found that people with Linux administration experience are more successful with the deployment and maintainance of {% data variables.product.product_name %}. -Você pode fornecer a determinados funcionários acesso administrativo ao {% data variables.product.product_name %}, para que eles possam definir a autenticação externa, configurar a instância para atender às necessidades do desenvolvedor e monitorar a atividade e o desempenho da instância. Para garantir a conformidade com regras de negócios ou restrições regulatórias, os administradores podem configurar políticas que controlam como as pessoas usam o {% data variables.product.product_location %}. Para obter mais informações, consulte os seguintes artigos. +You can give certain employees administrative access to {% data variables.product.product_name %}, so they can set up external authentication, configure the instance to meet developer needs, and monitor the instance's activity and performance. To ensure compliance with business rules or regulatory restrictions, administrators can configure policies that control how people use {% data variables.location.product_location %}. For more information, see the following articles. -- "[Sobre a autenticação para sua empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)" -- "[Como configurar sua empresa](/admin/configuration/configuring-your-enterprise)" -- "[Sobre a API do {% data variables.product.prodname_enterprise %}](/admin/overview/about-the-github-enterprise-api)" -- "[Como monitorar o seu dispositivo](/admin/enterprise-management/monitoring-your-appliance)" -- "[Como monitorar a atividade em sua empresa](/admin/monitoring-activity-in-your-enterprise)" -- "[Sobre as políticas empresariais](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)" +- "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)" +- "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)" +- "[About the {% data variables.product.prodname_enterprise %} API](/admin/overview/about-the-github-enterprise-api)" +- "[Monitoring your appliance](/admin/enterprise-management/monitoring-your-appliance)" +- "[Monitoring activity in your enterprise](/admin/monitoring-activity-in-your-enterprise)" +- "[About enterprise policies](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)" -## Sobre recursos opcionais +## About optional features -Você pode configurar recursos opcionais para o {% data variables.product.product_name %} que melhoram o ciclo de vida de desenvolvimento de software para sua empresa. +You can configure optional features for {% data variables.product.product_name %} that improve the software development lifecycle for your enterprise. -| Recurso | Descrição | Mais informações | +| Feature | Description | More information | | :- | :- | :- | -| {% data variables.product.prodname_actions %} | Automatizar fluxos de trabalho de CI/CD e desenvolvimento | "[Sobre o {% data variables.product.prodname_actions %} para empresas](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)" | -| {% data variables.product.prodname_github_connect %} | Aproveite o poder do {% data variables.product.prodname_dotcom_the_website %} de maneiras limitadas | "[Sobre o {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)" | -| {% data variables.product.prodname_GH_advanced_security %} | Melhorar a segurança e a qualidade do código | "[Sobre o {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)" | -| {% data variables.product.prodname_registry %} | Hospedar pacotes de software para sua empresa | "[Introdução ao {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)" | +| {% data variables.product.prodname_actions %} | Automate CI/CD and development workflows | "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)" | +| {% data variables.product.prodname_github_connect %} | Benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways | "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)" | +| {% data variables.product.prodname_GH_advanced_security %} | Improve code security and quality | "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)" | +| {% data variables.product.prodname_registry %} | Host software packages for your enterprise | "[Introduction to {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)" | -## Sobre topologias de implantação +## About deployment topologies -Por padrão, o {% data variables.product.product_name %} é executado como uma instância autônoma. Você pode aumentar a confiabilidade e o desempenho do {% data variables.product.product_name %} usando uma topologia diferente para sua implantação. +By default, {% data variables.product.product_name %} runs as a standalone instance. You can increase the reliability and performance of {% data variables.product.product_name %} by using a different topology for your deployment. -- Para atenuar o impacto das falhas do sistema ou da rede, você poderá implantar uma instância de réplica passiva. Durante uma interrupção que afeta sua instância primária, você pode fazer failover manualmente para a instância de réplica. Para obter mais informações, confira "[Sobre a configuração de alta disponibilidade](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration)". -- Você pode configurar várias réplicas ativas para melhorar o desempenho de desenvolvedores geograficamente distantes da instância primária. Para obter mais informações, consulte "[Sobre a replicação geográfica](/admin/enterprise-management/configuring-high-availability/about-geo-replication)". -- Algumas empresas com dezenas de milhares de desenvolvedores podem se beneficiar de uma configuração de cluster que é dimensionada horizontalmente em vez de verticalmente. Para obter mais informações, confira "[Sobre o clustering](/admin/enterprise-management/configuring-clustering/about-clustering)". +- To mitigate the impact of system or network failures, you can deploy a passive replica instance. During an outage that affects your primary instance, you can manually fail over to the replica instance. For more information, see "[About high availability configuration](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration)." +- You can configure multiple active replicas to improve performance for developers who are geographically distant from your primary instance. For more information, see "[About geo-replication](/admin/enterprise-management/configuring-high-availability/about-geo-replication)." +- Some enterprises with tens of thousands of developers may benefit from a cluster configuration that scales horizontally instead of vertically. For more information, see "[About clustering](/admin/enterprise-management/configuring-clustering/about-clustering)." -## Sobre backups e recuperação de desastre +## About backups and disaster recovery -Para proteger contra perda de dados ou interrupções de serviço para seus desenvolvedores, o {% data variables.product.company_short %} recomenda fortemente que você estabeleça um plano para recuperação de desastre. Você pode fazer backup da configuração da instância e dos dados do usuário implantando e configurando um sistema de host Linux ou Unix com o {% data variables.product.prodname_enterprise_backup_utilities %}. Para obter mais informações, confira "[Como configurar backups no seu dispositivo](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)". +To safeguard against data loss or service disruptions for your developers, {% data variables.product.company_short %} strongly recommends that you establish a plan for disaster recovery. You can back up your instance's configuration and user data by deploying and configuring a Linux or Unix host system with {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)." -Além disso, você pode configurar uma instância de réplica passiva para a qual fazer failover em caso de falha no sistema ou na rede. Para saber mais, confira "[Sobre topologias de implantação](#about-deployment-topologies)". +Additionally, you can configure a passive replica instance to fail over to in the event of a system or network failure. For more information, see "[About deployment topologies](#about-deployment-topologies)." -## Sobre a documentação +## About documentation -A documentação para administradores e usuários do {% data variables.product.product_name %} está disponível neste site, {% data variables.product.prodname_docs %}. +Documentation for both administrators and users of {% data variables.product.product_name %} is available on this site, {% data variables.product.prodname_docs %}. -- [Documentação do administrador da empresa](/admin) -- [Documentação do usuário](/) +- [Enterprise administrator documentation](/admin) +- [User documentation](/) -Diferentes versões do {% data variables.product.product_name %} são refletidas separadamente na documentação sobre o {% data variables.product.prodname_docs %}. Para obter mais informações, confira "[Sobre as versões do {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)". +Different versions of {% data variables.product.product_name %} are reflected separately in the documentation on {% data variables.product.prodname_docs %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." -## Experimentar o {% data variables.product.product_name %} +## Trying {% data variables.product.product_name %} -Você pode se inscrever para uma avaliação gratuita de 45 dias do {% data variables.product.product_name %}. Para obter mais informações, confira "[Como configurar uma avaliação do {% data variables.product.prodname_ghe_server %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server)". +You can sign up for a free, 45-day trial of {% data variables.product.product_name %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server)." -## Leitura adicional +## Further reading -- "[Introdução ao {% data variables.product.product_name %}](/get-started/onboarding/getting-started-with-github-enterprise-server)" -- "[Sobre o {% data variables.contact.github_support %}](/support/learning-about-github-support/about-github-support)" -- [ {% data variables.product.prodname_roadmap %} ]( {% data variables.product.prodname_roadmap_link %} ) no repositório `github/roadmap` +- "[Getting started with {% data variables.product.product_name %}](/get-started/onboarding/getting-started-with-github-enterprise-server)" +- "[About {% data variables.contact.github_support %}](/support/learning-about-github-support/about-github-support)" +- [ {% data variables.product.prodname_roadmap %} ]( {% data variables.product.prodname_roadmap_link %} ) in the `github/roadmap` repository diff --git a/translations/pt-BR/content/admin/overview/system-overview.md b/translations/pt-BR/content/admin/overview/system-overview.md index 340f3751bc..c1e59ff959 100644 --- a/translations/pt-BR/content/admin/overview/system-overview.md +++ b/translations/pt-BR/content/admin/overview/system-overview.md @@ -1,6 +1,6 @@ --- -title: Visão geral do sistema -intro: 'Saiba mais sobre os dados internos, a funcionalidade e a segurança do sistema do {% data variables.product.product_name %}.' +title: System overview +intro: 'Learn more about {% data variables.product.product_name %}''s system internals, functionality, and security.' redirect_from: - /enterprise/admin/installation/system-overview - /enterprise/admin/overview/system-overview @@ -13,160 +13,155 @@ topics: - Infrastructure - Security - Storage -ms.openlocfilehash: 656d68b267b4a739812b10e9409609f61cacdd5e -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147066935' --- -## Sobre o {% data variables.product.product_name %} -{% data reusables.enterprise.ghes-is-a-self-hosted-platform %} {% data reusables.enterprise.github-distributes-ghes %} Para obter mais informações, confira "[Sobre {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server)." +## About {% data variables.product.product_name %} -## Arquitetura de armazenamento +{% data reusables.enterprise.ghes-is-a-self-hosted-platform %} {% data reusables.enterprise.github-distributes-ghes %} For more information, see "[About {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server)." -O {% data variables.product.product_name %} exige dois volumes de armazenamento: um montado no caminho do *sistema de arquivos raiz* (`/`) e o outro no caminho do *sistema de arquivos do usuário* (`/data/user`). Essa arquitetura simplifica os procedimentos de atualização, reversão e recuperação separando o ambiente do software em execução dos dados persistentes do aplicativo. +## Storage architecture -O sistema de arquivos raiz está incluído na imagem da máquina distribuída. Ele contém o sistema operacional de base e o ambiente de aplicativo {% data variables.product.product_name %}. O sistema de arquivos raiz deve ser tratado como efêmero. Todos os dados no sistema de arquivos raiz serão substituídos nas atualizações futuras do {% data variables.product.product_name %}. +{% data variables.product.product_name %} requires two storage volumes, one mounted to the *root filesystem* path (`/`) and the other to the *user filesystem* path (`/data/user`). This architecture simplifies the upgrade, rollback, and recovery procedures by separating the running software environment from persistent application data. -O volume do armazenamento raiz é dividido em duas partições de tamanho igual. Uma das partições será montada como o sistema de arquivos raiz (`/`). A outra partição só será montada durante upgrades e reversões de upgrades como `/mnt/upgrade`, para facilitar as reversões, se necessário. Por exemplo, se for alocado um volume raiz de 200 GB, haverá 100 GB alocados no sistema de arquivos raiz e 100 GB reservados para atualizações e reversões. +The root filesystem is included in the distributed machine image. It contains the base operating system and the {% data variables.product.product_name %} application environment. The root filesystem should be treated as ephemeral. Any data on the root filesystem will be replaced when upgrading to future {% data variables.product.product_name %} releases. -O sistema de arquivos raiz contém arquivos que armazenam as informações a seguir. Esta lista não é exaustiva. +The root storage volume is split into two equally-sized partitions. One of the partitions will be mounted as the root filesystem (`/`). The other partition is only mounted during upgrades and rollbacks of upgrades as `/mnt/upgrade`, to facilitate easier rollbacks if necessary. For example, if a 200GB root volume is allocated, there will be 100GB allocated to the root filesystem and 100GB reserved for the upgrades and rollbacks. -- Certificados de CA (autoridade de certificação) personalizados (no `/usr/local/share/ca-certificates*`) -- Configurações de rede personalizadas; -- Configurações de firewall personalizadas; -- O estado da replicação. +The root filesystem contains files that store the following information. This list is not exhaustive. -O sistema de arquivos do usuário contém arquivos que armazenam dados e configuração a seguir. Esta lista não é exaustiva. +- Custom certificate authority (CA) certificates (in `/usr/local/share/ca-certificates*`) +- Custom networking configurations +- Custom firewall configurations +- The replication state -- Repositórios do Git; -- Bancos de dados -- Pesquisar índices -- Conteúdo publicado nos sites do {% data variables.product.prodname_pages %}; -- Arquivos grandes do {% data variables.large_files.product_name_long %}; -- Ambientes de hook pre-receive. +The user filesystem contains files that store following configuration and data. This list is not exhaustive. -## Topologias de implantação +- Git repositories +- Databases +- Search indexes +- Content published on {% data variables.product.prodname_pages %} sites +- Large files from {% data variables.large_files.product_name_long %} +- Pre-receive hook environments -Você pode implantar {% data variables.product.product_name %} em uma variedade de topologias, como um par de alta disponibilidade. Para obter mais informações, confira "[Sobre o {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server#about-deployment-topologies)." +## Deployment topologies -## Retenção de dados e redundância de datacenter +You can deploy {% data variables.product.product_name %} in a variety of topologies, such as a high availability pair. For more information, see "[About {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server#about-deployment-topologies)." + +## Data retention and datacenter redundancy {% warning %} -**Aviso**: antes de usar o {% data variables.product.product_name %} em um ambiente de produção, é altamente recomendável configurar backups e um plano de recuperação de desastres. +**Warning**: Before using {% data variables.product.product_name %} in a production environment, we strongly recommend you set up backups and a disaster recovery plan. {% endwarning %} -O {% data variables.product.product_name %} inclui suporte para backups online e incrementais com o {% data variables.product.prodname_enterprise_backup_utilities %}. Você pode obter instantâneos incrementais em um link de rede seguro (porta administrativa SSH) por longas distâncias para fins de armazenamento externo ou geograficamente disperso. Em caso de desastre no datacenter primário, é possível restaurar instantâneos pela rede em uma instância recém-provisionado no momento da recuperação. +{% data variables.product.product_name %} includes support for online and incremental backups with {% data variables.product.prodname_enterprise_backup_utilities %}. You can take incremental snapshots over a secure network link (the SSH administrative port) over long distances for off-site or geographically dispersed storage. You can restore snapshots over the network into a newly provisioned instance at time of recovery in case of disaster at the primary datacenter. -Além dos backups de rede, os instantâneos de volumes de armazenamento do usuário no AWS (EBS) e no VMware serão compatíveis enquanto a instância estiver offline ou em modo de manutenção. Se os requisitos de nível de serviço permitirem manutenção offline regular, os instantâneos de volumes regulares podem ser usados como alternativa de baixo custo e complexidade aos backups de rede com o {% data variables.product.prodname_enterprise_backup_utilities %}. +In addition to network backups, both AWS (EBS) and VMware disk snapshots of the user storage volumes are supported while the instance is offline or in maintenance mode. Regular volume snapshots can be used as a low-cost, low-complexity alternative to network backups with {% data variables.product.prodname_enterprise_backup_utilities %} if your service level requirements allow for regular offline maintenance. -Para obter mais informações, confira "[Como configurar backups no seu dispositivo](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)". +For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)." -## Segurança +## Security {% data reusables.enterprise.ghes-runs-on-your-infrastructure %} -O {% data variables.product.product_name %} também apresenta outros recursos de segurança. +{% data variables.product.product_name %} also includes additional security features. -- [Sistema operacional, software e patches](#operating-system-software-and-patches) -- [Segurança de rede](#network-security) -- [Segurança de aplicativo](#application-security) -- [Serviços externos e acesso ao suporte](#external-services-and-support-access) -- [Comunicação criptografada](#encrypted-communication) -- [Usuários e permissões de acesso](#users-and-access-permissions) -- [Autenticação](#authentication) -- [Log de auditoria e acesso](#audit-and-access-logging) +- [Operating system, software, and patches](#operating-system-software-and-patches) +- [Network security](#network-security) +- [Application security](#application-security) +- [External services and support access](#external-services-and-support-access) +- [Encrypted communication](#encrypted-communication) +- [Users and access permissions](#users-and-access-permissions) +- [Authentication](#authentication) +- [Audit and access logging](#audit-and-access-logging) -### Sistema operacional, software e patches +### Operating system, software, and patches -O {% data variables.product.product_name %} executa um sistema operacional Linux personalizado somente com os aplicativos e serviços necessários. O {% data variables.product.company_short %} distribui patches do sistema operacional central da instância como parte do ciclo padrão de versões do produto. Os patches tratam de problemas de segurança não críticos, funcionalidade e estabilidade do {% data variables.product.product_name %}. O {% data variables.product.company_short %} também oferece patches de segurança críticos, conforme necessário e fora do ciclo regular de versões. +{% data variables.product.product_name %} runs a customized Linux operating system with only the necessary applications and services. {% data variables.product.company_short %} distributes patches for the instance's core operating system as part of its standard product release cycle. Patches address functionality, stability, and non-critical security issues for {% data variables.product.product_name %}. {% data variables.product.company_short %} also provides critical security patches as needed outside of the regular release cycle. -O {% data variables.product.product_name %} é fornecido como um dispositivo, e muitos dos pacotes do sistema operacional são modificados em comparação com a distribuição habitual do Debian. Não há suporte para modificar o sistema operacional subjacente por esse motivo (incluindo upgrades do sistema operacional), que está alinhado ao [contrato de licença e suporte do {% data variables.product.prodname_ghe_server %}](https://enterprise.github.com/license), na seção 11.3 Exclusões. +{% data variables.product.product_name %} is provided as an appliance, and many of the operating system packages are modified compared to the usual Debian distribution. We do not support modifying the underlying operating system for this reason (including operating system upgrades), which is aligned with the [{% data variables.product.prodname_ghe_server %} license and support agreement](https://enterprise.github.com/license), under section 11.3 Exclusions. -Atualmente, o sistema operacional base para {% data variables.product.product_name %} é Debian 9 (Stretch), que recebe suporte de acordo com o programa Suporte de Longo Prazo Debian. Há planos para mudar para um sistema operacional base mais novo antes do final do período Debian LTS para o Stretch. +Currently, the base operating system for {% data variables.product.product_name %} is Debian 9 (Stretch), which receives support under the Debian Long Term Support program. There are plans to move to a newer base operating system before the end of the Debian LTS period for Stretch. -As atualizações regulares de patch são liberadas na página de [versões](https://enterprise.github.com/releases) do {% data variables.product.product_name %}, e a página de [notas sobre a versão](/admin/release-notes) fornece mais informações. De modo geral, estas atualizações contêm caminhos de segurança do fornecedor a montante e do projeto depois de terem sido testadas e de qualidade aprovadas pela nossa equipe de engenharia. Pode haver um pequeno atraso entre o lançamento da atualização upstream e o teste e empacotamento de uma versão futura de atualização de {% data variables.product.product_name %}. +Regular patch updates are released on the {% data variables.product.product_name %} [releases](https://enterprise.github.com/releases) page, and the [release notes](/admin/release-notes) page provides more information. These patches typically contain upstream vendor and project security patches after they've been tested and quality approved by our engineering team. There can be a slight time delay from when the upstream update is released to when it's tested and bundled in an upcoming {% data variables.product.product_name %} patch release. -### Segurança de rede +### Network security -O firewall interno do {% data variables.product.product_name %} restringe o acesso de rede aos serviços da instância. Apenas os serviços necessários para o funcionamento do appliance estão disponíveis na rede. Para obter mais informações, confira "[Portas de rede](/admin/configuration/configuring-network-settings/network-ports)". +{% data variables.product.product_name %}'s internal firewall restricts network access to the instance's services. Only services necessary for the appliance to function are available over the network. For more information, see "[Network ports](/admin/configuration/configuring-network-settings/network-ports)." -### Segurança do aplicativo +### Application security -A equipe de segurança de aplicativos do {% data variables.product.company_short %} trabalha em tempo integral na avaliação de vulnerabilidades, testes de invasão e revisão de códigos dos produtos do {% data variables.product.company_short %} e também do {% data variables.product.product_name %}. O {% data variables.product.company_short %} também contrata empresas de segurança externas para fornecer avaliações específicas dos produtos do {% data variables.product.company_short %}. +{% data variables.product.company_short %}'s application security team focuses full-time on vulnerability assessment, penetration testing, and code review for {% data variables.product.company_short %} products, including {% data variables.product.product_name %}. {% data variables.product.company_short %} also contracts with outside security firms to provide point-in-time security assessments of {% data variables.product.company_short %} products. -### Serviços externos e acesso ao suporte +### External services and support access -O {% data variables.product.product_name %} pode operar sem acessos de saída da sua rede para serviços externos. Alternativamente, você pode habilitar a integração com serviços externos de correio eletrônico, monitoramento externo e encaminhamento de logs. Para obter mais informações, confira "[Como configurar o email para notificações](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)", "[Como configurar o monitoramento externo](/admin/enterprise-management/monitoring-your-appliance/setting-up-external-monitoring)" e "[Encaminhamento de log](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)". +{% data variables.product.product_name %} can operate without any egress access from your network to outside services. You can optionally enable integration with external services for email delivery, external monitoring, and log forwarding. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)," "[Setting up external monitoring](/admin/enterprise-management/monitoring-your-appliance/setting-up-external-monitoring)," and "[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)." -Você pode levantar e enviar dados de soluções de problemas para o {% data variables.contact.github_support %}. Para obter mais informações, confira "[Como fornecer dados para o {% data variables.contact.github_support %}](/support/contacting-github-support/providing-data-to-github-support)". +You can manually collect and send troubleshooting data to {% data variables.contact.github_support %}. For more information, see "[Providing data to {% data variables.contact.github_support %}](/support/contacting-github-support/providing-data-to-github-support)." -### Comunicação criptografada +### Encrypted communication -O {% data variables.product.company_short %} desenvolveu o {% data variables.product.product_name %} para ser executado atrás do firewall corporativo. Para garantir a comunicação com fio, incentivamos que o Transport Layer Security (TLS) seja habilitado. O {% data variables.product.product_name %} é compatível com certificados TLS comerciais de 2048 bits ou mais para tráfego HTTPS. Para obter mais informações, confira "[Como configurar o TLS](/admin/configuration/configuring-network-settings/configuring-tls)". +{% data variables.product.company_short %} designs {% data variables.product.product_name %} to run behind your corporate firewall. To secure communication over the wire, we encourage you to enable Transport Layer Security (TLS). {% data variables.product.product_name %} supports 2048-bit and higher commercial TLS certificates for HTTPS traffic. For more information, see "[Configuring TLS](/admin/configuration/configuring-network-settings/configuring-tls)." -Por padrão, a instância também fornece acesso Secure Shell (SSH) para acesso a repositórios com o Git e para finalidades administrativas. Para obter mais informações, confira "[Sobre o SSH](/authentication/connecting-to-github-with-ssh/about-ssh)" e "[Como acessar o shell administrativo (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)". +By default, the instance also offers Secure Shell (SSH) access for both repository access using Git and administrative purposes. For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)" and "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." {% ifversion ghes > 3.3 %} -Se você configurar a autenticação do SAML para {% data variables.product.product_location %}, você poderá habilitar as declarações criptografadas entre a instância e o seu IdP do SAML. Para obter mais informações, confira "[Como usar o SAML](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml#enabling-encrypted-assertions)". +If you configure SAML authentication for {% data variables.location.product_location %}, you can enable encrypted assertions between the instance and your SAML IdP. For more information, see "[Using SAML](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml#enabling-encrypted-assertions)." {% endif %} -### Usuários e permissões de acesso +### Users and access permissions -O {% data variables.product.product_name %} fornece três tipos de contas. +{% data variables.product.product_name %} provides three types of accounts. -- A conta de usuário do Linux `admin` tem acesso controlado ao sistema operacional subjacente, incluindo o sistema de arquivos direto e o acesso ao banco de dados. Um número reduzido de administradores deve ter acesso a essa conta, o que pode ser feito por SSH. Para obter mais informações, confira "[Como acessar o shell administrativo (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)". -- As contas de usuários no aplicativo web da instância têm acesso total aos seus próprios dados e quaisquer dados que outros usuários ou organizações permitirem explicitamente. -- Administradores de site no aplicativo Web da instância são contas de usuários que podem gerenciar configurações de alto nível dos aplicativos Web e da instância, configurações de contas de usuários e organização e dados de repositório. +- The `admin` Linux user account has controlled access to the underlying operating system, including direct filesystem and database access. A small set of trusted administrators should have access to this account, which they can access over SSH. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." +- User accounts in the instance's web application have full access to their own data and any data that other users or organizations explicitly grant. +- Site administrators in the instance's web application are user accounts that can manage high-level web application and instance settings, user and organization account settings, and repository data. -Para obter mais informações sobre as permissões de usuário do {% data variables.product.product_name %}, confira "[Permissões de acesso no {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/access-permissions-on-github)." +For more information about {% data variables.product.product_name %}'s user permissions, see "[Access permissions on {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/access-permissions-on-github)." -### Autenticação +### Authentication -O {% data variables.product.product_name %} oferece quatro métodos de autenticação. +{% data variables.product.product_name %} provides four authentication methods. -- A autenticação com chave pública SSH oferece acesso a repositórios usando Git e acesso shell administrativo. Para obter mais informações, confira "[Sobre o SSH](/authentication/connecting-to-github-with-ssh/about-ssh)" e "[Como acessar o shell administrativo (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)". -- A autenticação de nome de usuário e senha com cookies HTTP oferece acesso ao aplicativo web e gerenciamento de sessão, com autenticação de dois fatores (2FA) opcional. Para obter mais informações, confira "[Como usar a autenticação interna](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication)". -- Autenticações LDAP, SAML ou CAS externas usando um serviço LDAP, provedor de identidade (IdP) SAML ou outros serviços compatíveis fornecem acesso ao aplicativo web. Para obter mais informações, confira "[Como gerenciar o IAM para sua empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise)". -- Tokens OAuth e de acesso pessoal oferecem acesso a dados de repositórios e APIs Git para clientes e serviços externos. Para obter mais informações, confira "[Como criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)". +- SSH public key authentication provides both repository access using Git and administrative shell access. For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)" and "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." +- Username and password authentication with HTTP cookies provides web application access and session management, with optional two-factor authentication (2FA). For more information, see "[Using built-in authentication](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication)." +- External LDAP, SAML, or CAS authentication using an LDAP service, SAML Identity Provider (IdP), or other compatible service provides access to the web application. For more information, see "[Managing IAM for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise)." +- OAuth and {% data variables.product.pat_generic %}s provide access to Git repository data and APIs for both external clients and services. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." -### Log de auditoria e acesso +### Audit and access logging -O {% data variables.product.product_name %} armazena logs do sistema operacional tradicional e de aplicativos. O aplicativo também grava logs de auditoria e segurança detalhados, que são armazenados permanentemente pelo {% data variables.product.product_name %}. Você pode encaminhar os dois tipos de logs em tempo real para vários destinos por meio do protocolo `syslog-ng`. Para obter mais informações, confira "[Sobre o log de auditoria para sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)" e "[Encaminhamento de log](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)." +{% data variables.product.product_name %} stores both traditional operating system and application logs. The application also writes detailed auditing and security logs, which {% data variables.product.product_name %} stores permanently. You can forward both types of logs in real time to multiple destinations via the `syslog-ng` protocol. For more information, see "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)" and "[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)." -Logs de acesso e auditoria contêm informações como as seguintes. +Access and audit logs include information like the following. -#### Logs de acesso +#### Access logs -- Logs de servidor web completos para acessos ao navegador e API -- Logs completos para acesso aos dados do repositório no Git, HTTPS e protocolos SSH -- Logs de acesso administrativo em HTTPS e SSH +- Full web server logs for both browser and API access +- Full logs for access to repository data over Git, HTTPS, and SSH protocols +- Administrative access logs over HTTPS and SSH -#### Logs de auditoria +#### Audit logs -- Login de usuários, redefinição de senhas, solicitações 2FA, alteração de configurações de e-mails e alterações em aplicativos e APIs autorizados -- Ações de administrador do site, como desbloqueio de contas de usuários e repositórios -- Eventos de push do repositório, concessão de acesso, transferências e renomeações -- Alterações nos integrantes da organização, incluindo criação e exclusão de equipes +- User logins, password resets, 2FA requests, email setting changes, and changes to authorized applications and APIs +- Site administrator actions, such as unlocking user accounts and repositories +- Repository push events, access grants, transfers, and renames +- Organization membership changes, including team creation and destruction -## Dependências de código aberto para o {% data variables.product.product_name %} +## Open source dependencies for {% data variables.product.product_name %} -Você pode ver uma lista completa de dependências na versão de sua instância do {% data variables.product.product_name %}, bem como a licença de cada projeto, em `http(s)://HOSTNAME/site/credits`. +You can see a complete list of dependencies in your instance's version of {% data variables.product.product_name %}, as well as each project's license, at `http(s)://HOSTNAME/site/credits`. -Os tarballs e uma lista completa de dependências e metadados associados estão disponíveis na sua instância. +Tarballs with a full list of dependencies and associated metadata are available on your instance. -- Para dependências comuns a todas as plataformas, em `/usr/local/share/enterprise/dependencies--base.tar.gz` -- Para dependências específicas de uma plataforma, em `/usr/local/share/enterprise/dependencies--.tar.gz` +- For dependencies common to all platforms, at `/usr/local/share/enterprise/dependencies--base.tar.gz` +- For dependencies specific to a platform, at `/usr/local/share/enterprise/dependencies--.tar.gz` -Os tarballs também estão disponíveis, com uma lista completa de dependências e metadados, em `https://enterprise.github.com/releases//download.html`. +Tarballs are also available, with a full list of dependencies and metadata, at `https://enterprise.github.com/releases//download.html`. -## Leitura adicional +## Further reading -- "[Como configurar uma avaliação do {% data variables.product.prodname_ghe_server %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server)" -- "[Como configurar uma instância do {% data variables.product.prodname_ghe_server %}](/admin/installation/setting-up-a-github-enterprise-server-instance)" +- "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server)" +- "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)" diff --git a/translations/pt-BR/content/admin/packages/enabling-github-packages-with-aws.md b/translations/pt-BR/content/admin/packages/enabling-github-packages-with-aws.md index 5db52e9aec..a60407369d 100644 --- a/translations/pt-BR/content/admin/packages/enabling-github-packages-with-aws.md +++ b/translations/pt-BR/content/admin/packages/enabling-github-packages-with-aws.md @@ -1,6 +1,6 @@ --- -title: Habilitar o GitHub Packeges com AWS -intro: 'Configure {% data variables.product.prodname_registry %} com AWS como seu armazenamento externo.' +title: Enabling GitHub Packages with AWS +intro: 'Set up {% data variables.product.prodname_registry %} with AWS as your external storage.' versions: ghes: '*' type: tutorial @@ -10,27 +10,22 @@ topics: - Packages - Packages shortTitle: Enable Packages with AWS -ms.openlocfilehash: 185373657cad88bc0a45e48eb5835abdf394f9ce -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145094908' --- + {% warning %} -**Avisos:** -- É fundamental que você configure todas as políticas de acesso restritivas necessárias para o seu bucket de armazenamento, porque {% data variables.product.company_short %} não aplica permissões específicas de objeto ou listas de controle de acesso adicionais (ACLs) à sua configuração do bucket de armazenamento. Por exemplo, se o seu bucket for público, os dados do bucket poderão ser acessados por meio da internet pública. Para obter mais informações, confira "[Como configurar permissões de acesso de objeto e bucket](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/set-permissions.html)" na documentação da AWS. -- Recomendamos usar um bucket dedicado para {% data variables.product.prodname_registry %}, separar do bucket que você usa para o armazenamento de {% data variables.product.prodname_actions %}. -- Certifique-se de configurar o bucket que você vai querer usar no futuro. Não recomendamos alterar seu armazenamento depois de começar a usar {% data variables.product.prodname_registry %}. +**Warnings:** +- It is critical that you configure any restrictive access policies you need for your storage bucket, because {% data variables.product.company_short %} does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible to the public internet. For more information, see "[Setting bucket and object access permissions](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/set-permissions.html)" in the AWS Documentation. +- We recommend using a dedicated bucket for {% data variables.product.prodname_registry %}, separate from the bucket you use for {% data variables.product.prodname_actions %} storage. +- Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}. {% endwarning %} -## Pré-requisitos +## Prerequisites -Antes de poder habilitar e configurar {% data variables.product.prodname_registry %} em {% data variables.product.product_location_enterprise %}, você precisa preparar o bucket do seu armazenamento do AWS. Para preparar o bucket de armazenamento da AWS, recomendamos consultar a documentação oficial da AWS na [documentação da AWS](https://docs.aws.amazon.com/index.html). +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your AWS storage bucket. To prepare your AWS storage bucket, we recommend consulting the official AWS docs at [AWS Documentation](https://docs.aws.amazon.com/index.html). -Certifique-se de que o seu ID da sua chave e o segredo de acesso do AWS tenham as permissões a seguir: +Ensure your AWS access key ID and secret have the following permissions: - `s3:PutObject` - `s3:GetObject` - `s3:ListBucketMultipartUploads` @@ -39,23 +34,28 @@ Certifique-se de que o seu ID da sua chave e o segredo de acesso do AWS tenham a - `s3:DeleteObject` - `s3:ListBucket` -## Habilitar {% data variables.product.prodname_registry %} com armazenamento externo do AWS +## Enabling {% data variables.product.prodname_registry %} with AWS external storage -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} {% ifversion ghes %} -1. Em "Armazenamento de Pacotes", selecione **Amazon S3** e insira os detalhes do bucket de armazenamento: - - **URL de Serviço da AWS:** A URL de serviço do bucket. Por exemplo, se o bucket S3 foi criado na `us-west-2 region`, esse valor deve ser `https://s3.us-west-2.amazonaws.com`. +1. Under "Packages Storage", select **Amazon S3** and enter your storage bucket's details: + - **AWS Service URL:** The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2 region`, this value should be `https://s3.us-west-2.amazonaws.com`. - Para obter mais informações, confira "[Pontos de extremidade de serviço da AWS](https://docs.aws.amazon.com/general/latest/gr/rande.html)" na documentação da AWS. + For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation. - - **Bucket da AWS S3:** o nome do bucket S3 dedicado ao {% data variables.product.prodname_registry %}. - - **Chave de Acesso da AWS S3** e **Chave Secreta da AWS S3**: a ID da chave de acesso e a chave secreta da AWS para acessar seu bucket. + - **AWS S3 Bucket:** The name of your S3 bucket dedicated to {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key to access your bucket. - Para obter mais informações sobre como gerenciar chaves de acesso da AWS, confira a "[Documentação de gerenciamento de identidades e acesso da AWS](https://docs.aws.amazon.com/iam/index.html)". + For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." - ![Caixas de entrada usadas para os detalhes do bucket da S3 AWS](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) {% endif %} {% data reusables.enterprise_management_console.save-settings %} + ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) +{% endif %} +{% data reusables.enterprise_management_console.save-settings %} -## Próximas etapas +## Next steps {% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/pt-BR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/pt-BR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md index b1deb7e759..a1a74dd1f4 100644 --- a/translations/pt-BR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md +++ b/translations/pt-BR/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md @@ -1,6 +1,6 @@ --- -title: Habilitar o GitHub Packages com o Azure Blob Storage -intro: 'Configure o {% data variables.product.prodname_registry %} com o Azure Blob Storage como seu armazenamento externo.' +title: Enabling GitHub Packages with Azure Blob Storage +intro: 'Set up {% data variables.product.prodname_registry %} with Azure Blob Storage as your external storage.' versions: ghes: '*' type: tutorial @@ -9,41 +9,39 @@ topics: - Packages - Storage shortTitle: Enable Packages with Azure -ms.openlocfilehash: ff9f7cc0e001a639cf5222ade02a6dabd57a3c47 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145095836' --- + {% warning %} -**Avisos:** -- É fundamental que você defina as políticas de acesso restritivas necessárias para o seu bucket de armazenamento, porque {% data variables.product.company_short %} não aplica permissões específicas de objeto ou listas de controle de acesso adicionais (ACLs) à sua configuração do bucket de armazenamento. Por exemplo, se você tornar o seu bucket público, os dados no bucket poderão ser acessados através da Internet pública. -- Recomendamos usar um bucket dedicado para {% data variables.product.prodname_registry %}, separar do bucket que você usa para o armazenamento de {% data variables.product.prodname_actions %}. -- Certifique-se de configurar o bucket que você vai querer usar no futuro. Não recomendamos alterar seu armazenamento depois de começar a usar {% data variables.product.prodname_registry %}. +**Warnings:** +- It is critical that you set the restrictive access policies you need for your storage bucket, because {% data variables.product.company_short %} does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible on the public internet. +- We recommend using a dedicated bucket for {% data variables.product.prodname_registry %}, separate from the bucket you use for {% data variables.product.prodname_actions %} storage. +- Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}. {% endwarning %} -## Pré-requisitos +## Prerequisites -Antes de poder habilitar e configurar {% data variables.product.prodname_registry %} em {% data variables.product.product_location_enterprise %}, você precisa preparar o bucket do seu Azure Blob Storage. Para preparar o bucket de armazenamento de Blobs do Azure, recomendamos consultar a documentação oficial do Armazenamento de Blobs do Azure no [site oficial da documentação do Armazenamento de Blobs do Azure](https://docs.microsoft.com/en-us/azure/storage/blobs/). +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your Azure Blob storage bucket. To prepare your Azure Blob storage bucket, we recommend consulting the official Azure Blob storage docs at the official [Azure Blob Storage documentation site](https://docs.microsoft.com/en-us/azure/storage/blobs/). -## Habilitar {% data variables.product.prodname_registry %} com o Azure Blob Storage +## Enabling {% data variables.product.prodname_registry %} with Azure Blob Storage -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %} -1. Em "Pacotes de Armazenamento", selecione **Armazenamento de Blobs do Azure** e insira o nome do contêiner do Azure para o bucket de armazenamento de pacotes e a cadeia de conexão. - ![Nome do contêiner do Armazenamento de Blobs do Azure e caixas da cadeia de conexão](/assets/images/help/package-registry/azure-blob-storage-settings.png) +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string. + ![Azure Blob storage container name and connection string boxes](/assets/images/help/package-registry/azure-blob-storage-settings.png) {% note %} - **Observação:** você pode encontrar sua Cadeia de Conexão do Azure navegando até o menu Chave de Acesso em sua conta de armazenamento do Azure. - No momento, não há suporte para o uso de um Token SAS ou URL SAS como cadeia de conexão. + **Note:** You can find your Azure Connection String by navigating to the Access Key menu in your Azure storage account. + Usage of a SAS Token or SAS URL as connection string is not currently supported. {% endnote %} {% data reusables.enterprise_management_console.save-settings %} -## Próximas etapas +## Next steps {% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/pt-BR/content/admin/packages/enabling-github-packages-with-minio.md b/translations/pt-BR/content/admin/packages/enabling-github-packages-with-minio.md index 98e64a1aaa..0fa9b47390 100644 --- a/translations/pt-BR/content/admin/packages/enabling-github-packages-with-minio.md +++ b/translations/pt-BR/content/admin/packages/enabling-github-packages-with-minio.md @@ -1,6 +1,6 @@ --- -title: Habilitar o GitHub Packeges com o MinIO -intro: 'Configure {% data variables.product.prodname_registry %} com o MinIO como seu armazenamento externo.' +title: Enabling GitHub Packages with MinIO +intro: 'Set up {% data variables.product.prodname_registry %} with MinIO as your external storage.' versions: ghes: '*' type: tutorial @@ -9,27 +9,22 @@ topics: - Packages - Storage shortTitle: Enable Packages with MinIO -ms.openlocfilehash: 2e7d76ee696dfbcd2369c577ef2d2ee803a09638 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145094907' --- + {% warning %} -**Avisos:** -- É fundamental que você defina as políticas de acesso restritivas necessárias para o seu bucket de armazenamento, porque {% data variables.product.company_short %} não aplica permissões específicas de objeto ou listas de controle de acesso adicionais (ACLs) à sua configuração do bucket de armazenamento. Por exemplo, se você tornar o seu bucket público, os dados no bucket poderão ser acessados através da Internet pública. -- Recomendamos usar um bucket dedicado para {% data variables.product.prodname_registry %}, separar do bucket que você usa para o armazenamento de {% data variables.product.prodname_actions %}. -- Certifique-se de configurar o bucket que você vai querer usar no futuro. Não recomendamos alterar seu armazenamento depois de começar a usar {% data variables.product.prodname_registry %}. +**Warnings:** +- It is critical that you set the restrictive access policies you need for your storage bucket, because {% data variables.product.company_short %} does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible on the public internet. +- We recommend using a dedicated bucket for {% data variables.product.prodname_registry %}, separate from the bucket you use for {% data variables.product.prodname_actions %} storage. +- Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}. {% endwarning %} -## Pré-requisitos +## Prerequisites -Antes de poder habilitar e configurar {% data variables.product.prodname_registry %} em {% data variables.product.product_location_enterprise %}, você precisa preparar seu grupo de armazenamento do MinIO. Para ajudar você a configurar rapidamente um bucket do MinIO e navegar pelas opções de personalização do MinIO, confira o "[Guia de início rápido para configurar o bucket de armazenamento do MinIO para o {% data variables.product.prodname_registry %}](/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages)". +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your MinIO storage bucket. To help you quickly set up a MinIO bucket and navigate MinIO's customization options, see the "[Quickstart for configuring your MinIO storage bucket for {% data variables.product.prodname_registry %}](/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages)." -Certifique-se de que que o seu ID da chave de acesso e o segredo de armazenamento externo do MinIO tenham essas permissões: +Ensure your MinIO external storage access key ID and secret have these permissions: - `s3:PutObject` - `s3:GetObject` - `s3:ListBucketMultipartUploads` @@ -38,21 +33,26 @@ Certifique-se de que que o seu ID da chave de acesso e o segredo de armazenament - `s3:DeleteObject` - `s3:ListBucket` -## Habilitar {% data variables.product.prodname_registry %} com armazenamento externo do MinIO +## Enabling {% data variables.product.prodname_registry %} with MinIO external storage -Embora o MinIO atualmente não apareça na interface do usuário em "Armazenamento de Pacote", ele ainda é compatível com {% data variables.product.prodname_registry %} em {% data variables.product.prodname_enterprise %}. Além disso, observe que o armazenamento de objetos do MinIO é compatível com a API do S3 e você pode inserir detalhes do bucket do MinIO no lugar dos detalhes do AWS S3. +Although MinIO does not currently appear in the user interface under "Package Storage", MinIO is still supported by {% data variables.product.prodname_registry %} on {% data variables.product.prodname_enterprise %}. Also, note that MinIO's object storage is compatible with the S3 API and you can enter MinIO's bucket details in place of AWS S3 details. -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} {% ifversion ghes %} -1. Em "Armazenamento de Pacotes", selecione **Amazon S3**. -1. Insira os detalhes do seu bucket de armazenamento do MinIO nas configurações de armazenamento do AWS. - - **URL de Serviço da AWS:** a URL de hospedagem do bucket do MinIO. - - **Bucket da AWS S3:** o nome do bucket do MinIO compatível com a S3 dedicado ao {% data variables.product.prodname_registry %}. - - **Chave de Acesso da AWS S3** e **Chave Secreta da AWS S3**: insira a ID da chave de acesso e a chave secreta do MinIO para acessar o bucket. +1. Under "Packages Storage", select **Amazon S3**. +1. Enter your MinIO storage bucket's details in the AWS storage settings. + - **AWS Service URL:** The hosting URL for your MinIO bucket. + - **AWS S3 Bucket:** The name of your S3-compatible MinIO bucket dedicated to {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** and **AWS S3 Secret Key**: Enter the MinIO access key ID and secret key to access your bucket. - ![Caixas de entrada usadas para os detalhes do bucket da S3 AWS](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) {% endif %} {% data reusables.enterprise_management_console.save-settings %} + ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) +{% endif %} +{% data reusables.enterprise_management_console.save-settings %} -## Próximas etapas +## Next steps {% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/pt-BR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/pt-BR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md index 1bf7f668b5..43a79f9653 100644 --- a/translations/pt-BR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Primeiros passos com o GitHub Packages para a sua empresa +title: Getting started with GitHub Packages for your enterprise shortTitle: Getting started with GitHub Packages -intro: 'Você pode começar a usar {% data variables.product.prodname_registry %} em {% data variables.product.product_location %} habilitando o recurso, configurando armazenamento de terceiros, configurando os ecossistemas que você deseja que sejam compatíveis e atualizando seu certificado TLS.' +intro: 'You can start using {% data variables.product.prodname_registry %} on {% data variables.location.product_location %} by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate.' redirect_from: - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise - /admin/packages/enabling-github-packages-for-your-enterprise @@ -11,46 +11,42 @@ type: how_to topics: - Enterprise - Packages -ms.openlocfilehash: 2389eba768a8b2f865165b43dde0e1b6381c6ae7 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '146199959' --- + + {% data reusables.package_registry.packages-cluster-support %} -## Passo 1: Verifique se {% data variables.product.prodname_registry %} está disponível para a sua empresa +## Step 1: Check whether {% data variables.product.prodname_registry %} is available for your enterprise -{% data variables.product.prodname_registry %} está disponível em {% data variables.product.prodname_ghe_server %} 3.0 ou superior. Se você estiver usando uma versão anterior do {% data variables.product.prodname_ghe_server %}, você deverá fazer a atualização para usar {% data variables.product.prodname_registry %}. Para obter mais informações sobre como fazer upgrade da sua instância do {% data variables.product.prodname_ghe_server %}, confira "[Sobre os upgrades para novas versões](/admin/overview/about-upgrades-to-new-releases)". -## Etapa 2: Habilitar o {% data variables.product.prodname_registry %} e configurar o armazenamento externo +{% data variables.product.prodname_registry %} is available in {% data variables.product.prodname_ghe_server %} 3.0 or higher. If you're using an earlier version of {% data variables.product.prodname_ghe_server %}, you'll have to upgrade to use {% data variables.product.prodname_registry %}. For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)." +## Step 2: Enable {% data variables.product.prodname_registry %} and configure external storage -{% data variables.product.prodname_registry %} em {% data variables.product.prodname_ghe_server %} usa armazenamento externo de blob para armazenar seus pacotes. +{% data variables.product.prodname_registry %} on {% data variables.product.prodname_ghe_server %} uses external blob storage to store your packages. -Depois de habilitar {% data variables.product.prodname_registry %} para {% data variables.product.product_location %}, você deverá preparar seu bucket de armazenamento de terceiros. A quantidade de armazenamento necessária depende do seu uso de {% data variables.product.prodname_registry %}, e as diretrizes de configuração podem variar de acordo com o provedor de armazenamento. +After enabling {% data variables.product.prodname_registry %} for {% data variables.location.product_location %}, you'll need to prepare your third-party storage bucket. The amount of storage required depends on your usage of {% data variables.product.prodname_registry %}, and the setup guidelines can vary by storage provider. -Provedores de armazenamento externos compatíveis +Supported external storage providers - Amazon Web Services (AWS) S3 {% ifversion ghes %} - Azure Blob Storage {% endif %} - MinIO -Para habilitar {% data variables.product.prodname_registry %} e configurar o armazenamento de terceiros, consulte: - - "[Como habilitar os Pacotes do GitHub com a AWS](/admin/packages/enabling-github-packages-with-aws)"{% ifversion ghes %} - - "[Como habilitar os Pacotes do GitHub com o Armazenamento de Blobs do Azure](/admin/packages/enabling-github-packages-with-azure-blob-storage)"{% endif %} - - "[Como habilitar os Pacotes do GitHub com o MinIO](/admin/packages/enabling-github-packages-with-minio)" +To enable {% data variables.product.prodname_registry %} and configure third-party storage, see: + - "[Enabling GitHub Packages with AWS](/admin/packages/enabling-github-packages-with-aws)"{% ifversion ghes %} + - "[Enabling GitHub Packages with Azure Blob Storage](/admin/packages/enabling-github-packages-with-azure-blob-storage)"{% endif %} + - "[Enabling GitHub Packages with MinIO](/admin/packages/enabling-github-packages-with-minio)" -## Etapa 3: Especificar os ecossistemas de pacotes que serão compatíveis com a sua instância +## Step 3: Specify the package ecosystems to support on your instance -Escolha quais ecossistemas de pacote você gostaria de habilitar, desabilitar ou definir como somente leitura no seu {% data variables.product.product_location %}. As opções disponíveis são {% ifversion ghes > 3.4 %}{% data variables.product.prodname_container_registry %}, {% endif %}Docker, RubyGems, npm, Apache Maven, Gradle ou NuGet. Para obter mais informações, confira "[Como configurar o suporte ao ecossistema de pacotes para sua empresa](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)". +Choose which package ecosystems you'd like to enable, disable, or set to read-only on {% data variables.location.product_location %}. Available options are {% ifversion ghes > 3.4 %}{% data variables.product.prodname_container_registry %}, {% endif %}Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. For more information, see "[Configuring package ecosystem support for your enterprise](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." -## Etapa 4: Verificar se você tem um certificado TLS para a URL do host do pacote, se necessário +## Step 4: Ensure you have a TLS certificate for your package host URL, if needed -Se o isolamento de subdomínio estiver habilitado para o {% data variables.product.product_location %}, você precisará criar e carregar um certificado TLS que permita a URL do host do pacote para cada ecossistema que deseja usar, como `{% data reusables.package_registry.container-registry-hostname %}`. Verifique se cada URL do host do pacote inclui `https://`. +If subdomain isolation is enabled for {% data variables.location.product_location %}, you will need to create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as `{% data reusables.package_registry.container-registry-hostname %}`. Make sure each package host URL includes `https://`. - Você pode criar o certificado manualmente ou usar _Let's Encrypt_. Se você já usa o _Let's Encrypt_, solicite um novo certificado TLS depois de habilitar o {% data variables.product.prodname_registry %}. Para obter mais informações sobre as URLs do host do pacote, confira "[Como habilitar o isolamento de subdomínio](/enterprise/admin/configuration/enabling-subdomain-isolation)". Para obter mais informações sobre como carregar certificados TLS no {% data variables.product.product_name %}, confira "[Como configurar o TLS](/enterprise/admin/configuration/configuring-tls)". + You can create the certificate manually, or you can use _Let's Encrypt_. If you already use _Let's Encrypt_, you must request a new TLS certificate after enabling {% data variables.product.prodname_registry %}. For more information about package host URLs, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)." For more information about uploading TLS certificates to {% data variables.product.product_name %}, see "[Configuring TLS](/enterprise/admin/configuration/configuring-tls)." -## Etapa 5: Verificar e renomear nomes reservados +## Step 5: Check for and rename reserved names -Se você quiser usar o ecossistema do Docker com isolamento de subdomínio desabilitado, primeiro **renomeie** qualquer usuário ou organização chamada `v2` na {% data variables.product.product_location %}, e depois habilite o suporte ao ecossistema do Docker no {% data variables.enterprise.management_console %}. O Docker usa o nome de conta `v2` para gerenciar conflitos de caminho com a API do Docker. Depois que o suporte ao registro do Docker estiver habilitado, você não poderá mais usar esse nome. +If you want to use the Docker ecosystem with subdomain isolation disabled, you **must** first rename any user or organization named `v2` on {% data variables.location.product_location %}, prior to enabling Docker ecosystem support in the {% data variables.enterprise.management_console %}. Docker uses a `v2` account name to manage path conflicts with the Docker API, and once Docker registry support is enabled, you won't be able to use this name anymore. -Você pode ver uma lista completa de logons reservados para uso interno acessando a página "Logons reservados" no painel do administrador do site. Para obter mais informações, confira "[Palavras-chave reservadas](/admin/configuration/configuring-your-enterprise/site-admin-dashboard#reserved-logins)". +You can view a full list of logins reserved for internal use by navigating to the "Reserved logins" page in the Site admin dashboard. For more information, see "[Reserved logins](/admin/configuration/configuring-your-enterprise/site-admin-dashboard#reserved-logins)." diff --git a/translations/pt-BR/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md b/translations/pt-BR/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md index de2a7d69aa..9305406cc8 100644 --- a/translations/pt-BR/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md +++ b/translations/pt-BR/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md @@ -1,78 +1,77 @@ --- -title: Como migrar sua empresa para o registro de contêiner do Registro do Docker -intro: 'Você pode migrar imagens do Docker armazenadas anteriormente no registro do Docker em {% data variables.product.product_location %} para {% data variables.product.prodname_container_registry %}.' +title: Migrating your enterprise to the Container registry from the Docker registry +intro: 'You can migrate Docker images previously stored in the Docker registry on {% data variables.location.product_location %} to the {% data variables.product.prodname_container_registry %}.' product: '{% data reusables.gated-features.packages %}' -permissions: 'Enterprise owners can migrate Docker images to the {% data variables.product.prodname_container_registry %}.' +permissions: "Enterprise owners can migrate Docker images to the {% data variables.product.prodname_container_registry %}." versions: - feature: docker-ghcr-enterprise-migration + feature: 'docker-ghcr-enterprise-migration' shortTitle: Migrate to Container registry topics: - Containers - Docker - Migration -ms.openlocfilehash: b4fd99bad9d9ae68354d01a9bd80ebec89e0918b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147578663' --- + {% data reusables.package_registry.container-registry-ghes-beta %} -## Sobre o {% data variables.product.prodname_container_registry %} +## About the {% data variables.product.prodname_container_registry %} -{% data reusables.package_registry.container-registry-benefits %} Para obter mais informações, confira "[Como trabalhar com {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)." +{% data reusables.package_registry.container-registry-benefits %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)." -Para obter mais informações sobre como configurar o {% data variables.product.prodname_registry %} para o {% data variables.product.product_location %}, confira "[Introdução ao {% data variables.product.prodname_registry %} para sua empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)". +For more information about configuring {% data variables.product.prodname_registry %} for {% data variables.location.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." -## Sobre a migração do Registro do Docker +## About migration from the Docker registry -{% data reusables.package_registry.container-registry-replaces-docker-registry %} Se o Registro do Docker em {% data variables.product.product_location %} contiver imagens, você precisará migrar manualmente as imagens para {% data variables.product.prodname_container_registry %}. +{% data reusables.package_registry.container-registry-replaces-docker-registry %} If the Docker registry on {% data variables.location.product_location %} contains images, you must manually migrate the images to the {% data variables.product.prodname_container_registry %}. {% ifversion ghes %} {% note %} -**Observação**: {% data reusables.package_registry.container-registry-ghes-migration-availability %} +**Note**: {% data reusables.package_registry.container-registry-ghes-migration-availability %} {% endnote %} {% endif %} -{% data reusables.package_registry.container-registry-migration-namespaces %} Para obter mais informações sobre o impacto da migração para {% data variables.product.prodname_container_registry %}, confira "[Fazer migração para {% data variables.product.prodname_container_registry %} do Registro do Docker](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry#about-migration-from-the-docker-registry)." +{% data reusables.package_registry.container-registry-migration-namespaces %} For more information about the impact of migration to the {% data variables.product.prodname_container_registry %}, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry#about-migration-from-the-docker-registry)." -## Migrar organizações para {% data variables.product.prodname_container_registry %} +## Migrating organizations to the {% data variables.product.prodname_container_registry %} -Você pode iniciar uma migração de todas as imagens do Docker de suas organizações para {% data variables.product.prodname_container_registry %}. A duração da operação de migração depende do número total de imagens a serem migradas e da carga geral na {% ifversion ghes %}sua instância{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. Após uma migração bem-sucedida, {% data variables.product.product_name %} exibirá um resumo, e todos os uploads futuros de imagens do Docker usarão o {% data variables.product.prodname_container_registry %}. +You can start a migration of all your organizations' Docker images to the {% data variables.product.prodname_container_registry %}. The duration of the migration operation depends on the total number of images to migrate, and the overall load on {% ifversion ghes %}your instance{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. After a successful migration, {% data variables.product.product_name %} will display a summary, and all future uploads of Docker images will use the {% data variables.product.prodname_container_registry %}. -Se {% ifversion ghes %}um administrador do site{% elsif ghae %}um proprietário de empresa{% endif %} tiver configurado notificações por e-mail para {% data variables.product.product_location %}, você receberá um e-mail após a conclusão da migração. Para obter mais informações, confira "[Como configurar o email para notificações](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)". +If {% ifversion ghes %}a site administrator{% elsif ghae %}an enterprise owner{% endif %} has configured email notifications for {% data variables.location.product_location %}, you will receive an email after the migration is complete. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)." {% note %} -**{% ifversion ghes %}Observações{% elsif ghae %}Note{% endif %}** : +**{% ifversion ghes %}Notes{% elsif ghae %}Note{% endif %}**: {%- ifversion ghes %} -- Durante a migração, o uso de CPU e memória para sua instância aumentará. Para garantir o desempenho da instância dos seus usuários, {% data variables.product.company_short %} recomenda que você inicie uma migração durante um período de atividade reduzida. -{%- endif %} {% ifversion ghes %}– {% endif %}Durante a migração, não modifique as configurações da sua empresa{% ifversion ghes %} nem execute `ghe-config-apply` de uma sessão SSH administrativa{% endif %}. {% ifversion ghes %}Essas ações vão disparar uma execução de configuração, que podem reiniciar serviços e {% elsif ghae %}Modificar essas configurações{% endif %} pode interromper a migração. +- During the migration, the CPU and memory usage for your instance will increase. To ensure the performance of the instance for your users, {% data variables.product.company_short %} recommends that you begin a migration during a period of reduced activity. +{%- endif %} +{% ifversion ghes %}- {% endif %}During the migration, do not modify settings for your enterprise{% ifversion ghes %} or run `ghe-config-apply` from an administrative SSH session{% endif %}. {% ifversion ghes %}These actions will trigger a configuration run, which can restart services and {% elsif ghae %}Modifying these settings {% endif %} may interrupt the migration. {%- ifversion ghes %} -- Após a migração, a pressão de armazenamento em sua instância aumentará devido à duplicação de arquivos de imagem no Registro do Docker e a {% data variables.product.prodname_container_registry %}. Uma versão futura de {% data variables.product.product_name %} removerá os arquivos duplicados quando todas as migrações estiverem concluídas. +- After the migration, storage pressure on your instance will increase due to the duplication of image files in the Docker registry and the {% data variables.product.prodname_container_registry %}. A future release of {% data variables.product.product_name %} will remove the duplicated files when all migrations are complete. -Para obter mais informações sobre o monitoramento do desempenho e do armazenamento de {% data variables.product.product_location %}, confira "[Como acessar o painel do monitor](/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard)." +For more information about monitoring the performance and storage of {% data variables.location.product_location %}, see "[Accessing the monitor dashboard](/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard)." {% endif %} {% endnote %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} -1. Na barra lateral esquerda, clique em **Pacotes**. -1. À direita do número de pacotes a serem migrados, clique em **Iniciar migração**. Durante a migração, {% data variables.product.product_name %} exibirá o andamento nesta página. +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +1. In the left sidebar, click **Packages**. +1. To the right of the number of packages to migrate, click **Start migration**. During the migration, {% data variables.product.product_name %} will display progress on this page. -Após a conclusão da migração, a página exibirá os resultados. Se uma migração falhar, a página mostrará as organizações que têm o pacote que causou a falha. +After the migration completes, the page will display the results. If a migration fails, the page will show the organizations that own the package that caused the failure. -## Executar novamente uma migração de organização com falha +## Re-running a failed organization migration -Antes da migração, se um usuário tiver criado um pacote no {% data variables.product.prodname_container_registry %} que tem um nome idêntico a um pacote existente no Registro do Docker, a migração falhará. +Prior to migration, if a user has created a package in the {% data variables.product.prodname_container_registry %} that has an identical name to an existing package in the Docker registry, the migration will fail. -1. Exclua o contêiner afetado no {% data variables.product.prodname_container_registry %}. Para obter mais informações, confira "[Como excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package#deleting-a-version-of-an-organization-scoped-package-on-github)". -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.packages-tab %} -1. À direita do número de pacotes a serem migrados, clique em **Executar migração novamente**. Durante a migração, {% data variables.product.product_name %} exibirá o andamento nesta página. -1. Se a migração falhar novamente, comece da etapa 1 e execute novamente a migração. +1. Delete the affected container in the {% data variables.product.prodname_container_registry %}. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package#deleting-a-version-of-an-organization-scoped-package-on-github)." +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.packages-tab %} +1. To the right of the number of packages to migrate, click **Re-run migration**. During the migration, {% data variables.product.product_name %} will display progress on this page. +1. If the migration fails again, start from step 1 and re-run the migration. diff --git a/translations/pt-BR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/pt-BR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md index a7695d664e..443b6038e1 100644 --- a/translations/pt-BR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md +++ b/translations/pt-BR/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md @@ -1,6 +1,6 @@ --- -title: Guia de início rápido para configurar o seu bucket de armazenamento de MinIO para o GitHub Packages -intro: 'Configure seu bucket de armazenamento do MinIO personalizado para uso com {% data variables.product.prodname_registry %}.' +title: Quickstart for configuring your MinIO storage bucket for GitHub Packages +intro: 'Configure your custom MinIO storage bucket for use with {% data variables.product.prodname_registry %}.' versions: ghes: '*' type: quick_start @@ -9,57 +9,52 @@ topics: - Enterprise - Storage shortTitle: Quickstart for MinIO -ms.openlocfilehash: 5e3da768643c3979380d3fb205518a7053c7360b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146688970' --- + {% data reusables.package_registry.packages-ghes-release-stage %} -Antes de poder habilitar e configurar {% data variables.product.prodname_registry %} em {% data variables.product.product_location_enterprise %}, você deverá preparar sua solução de armazenamento de terceiros. +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your third-party storage solution. -O MinIO oferece armazenamento de objetos com suporte para a API S3 e {% data variables.product.prodname_registry %} na sua empresa. +MinIO offers object storage with support for the S3 API and {% data variables.product.prodname_registry %} on your enterprise. -Este início rápido mostra como configurar o MinIO usando o Docker para uso com {% data variables.product.prodname_registry %}. No entanto, você tem outras opções para gerenciar o MinIO além do Docker. Para obter mais informações sobre o MinIO, confira a [documentação oficial do MinIO](https://docs.min.io/). +This quickstart shows you how to set up MinIO using Docker for use with {% data variables.product.prodname_registry %} but you have other options for managing MinIO besides Docker. For more information about MinIO, see the official [MinIO docs](https://docs.min.io/). -## 1. Escolher um modo do MinIO para suas necessidades +## 1. Choose a MinIO mode for your needs -| Modo MinIO | Otimizado para | Infraestrutura de armazenamento necessária | +| MinIO mode | Optimized for | Storage infrastructure required | |----|----|----| -| MinIO independente (em um único host) | Configuração rápida | N/D | -| MinIO como um gateway NAS | NAS (Armazenamento de rede)| Dispositivos NAS | -| MinIO agrupado (também denominado MinIO Distribuído)| Segurança de dados | Servidores de armazenamento em execução em um cluster | +| Standalone MinIO (on a single host) | Fast setup | N/A | +| MinIO as a NAS gateway | NAS (Network-attached storage)| NAS devices | +| Clustered MinIO (also called Distributed MinIO)| Data security | Storage servers running in a cluster | -Para obter mais informações sobre suas opções, confira a [documentação oficial do MinIO](https://docs.min.io/). +For more information about your options, see the official [MinIO docs](https://docs.min.io/). {% warning %} -**Aviso**: o MinIO anunciou a remoção de Gateways MinIO. A partir de 1º de junho de 2022, as correções de bug e o suporte para a implementação atual do Gateway do MinIO NAS estarão disponíveis somente para clientes pagos por meio de seu contrato de suporte LTS. Para continuar usando Gateways MinIO com {% data variables.product.prodname_registry %}, recomendamos migrar para o suporte do MinIO LTS. Para saber mais, confira a [remoção agendada do Gateway do MinIO para GCS, Azure, HDFS](https://github.com/minio/minio/issues/14331) no repositório minio/minio. +**Warning**: MinIO has announced removal of MinIO Gateways. Starting June 1st, 2022, support and bug fixes for the current MinIO NAS Gateway implementation will only be available for paid customers via their LTS support contract. If you want to continue using MinIO Gateways with {% data variables.product.prodname_registry %}, we recommend moving to MinIO LTS support. For more information, see [Scheduled removal of MinIO Gateway for GCS, Azure, HDFS](https://github.com/minio/minio/issues/14331) in the minio/minio repository. -Outros modos do MinIO permanecerão disponíveis com suporte padrão. +Other modes of MinIO remain available with standard support. {% endwarning %} -## 2. Instalar, executar e entrar no MinIO +## 2. Install, run, and sign in to MinIO -1. Configure suas variáveis de ambiente preferidas para o MinIO. +1. Set up your preferred environment variables for MinIO. - Estes exemplos usam `MINIO_DIR`: + These examples use `MINIO_DIR`: ```shell $ export MINIO_DIR=$(pwd)/minio $ mkdir -p $MINIO_DIR ``` -2. Instalar MinIO. +2. Install MinIO. ```shell $ docker pull minio/minio ``` - Para obter mais informações, confira o "[Guia de Início Rápido do MinIO](https://docs.min.io/docs/minio-quickstart-guide)" oficial. + For more information, see the official "[MinIO Quickstart Guide](https://docs.min.io/docs/minio-quickstart-guide)." -3. Efetue o login no MinIO usando sua chave e segredo de acesso do MinIO. +3. Sign in to MinIO using your MinIO access key and secret. {% linux %} ```shell @@ -77,16 +72,16 @@ Outros modos do MinIO permanecerão disponíveis com suporte padrão. ``` {% endmac %} - Você pode acessar suas chaves do MinIO usando as variáveis de ambiente: + You can access your MinIO keys using the environment variables: ```shell $ echo $MINIO_ACCESS_KEY $ echo $MINIO_SECRET_KEY ``` -4. Execute o MinIO no modo escolhido. +4. Run MinIO in your chosen mode. - * Execute o MinIO usando Docker em um único host: + * Run MinIO using Docker on a single host: ```shell $ docker run -p 9000:9000 \ @@ -96,11 +91,11 @@ Outros modos do MinIO permanecerão disponíveis com suporte padrão. minio/minio server /data ``` - Para obter mais informações, confira "[Guia de Início Rápido do MinIO no Docker](https://docs.min.io/docs/minio-docker-quickstart-guide.html)". + For more information, see "[MinIO Docker Quickstart guide](https://docs.min.io/docs/minio-docker-quickstart-guide.html)." - * Executar o MinIO usando Docker como um gateway NAS: + * Run MinIO using Docker as a NAS gateway: - Esta configuração é útil para implantações em que já existe um NAS que você deseja usar como armazenamento de backup para {% data variables.product.prodname_registry %}. + This setup is useful for deployments where there is already a NAS you want to use as the backup storage for {% data variables.product.prodname_registry %}. ```shell $ docker run -p 9000:9000 \ @@ -110,40 +105,40 @@ Outros modos do MinIO permanecerão disponíveis com suporte padrão. minio/minio gateway nas /data ``` - * Executar o MinIO usando Docker como um cluster. Esta implantação do MinIO usa vários hosts e a codificação de eliminação do MinIO para uma proteção de dados mais forte. Para executar o MinIO em um modo de cluster, confira o "[Guia de início rápido do MinIO distribuído](https://docs.min.io/docs/distributed-minio-quickstart-guide.html)". + * Run MinIO using Docker as a cluster. This MinIO deployment uses several hosts and MinIO's erasure coding for the strongest data protection. To run MinIO in a cluster mode, see the "[Distributed MinIO Quickstart Guide](https://docs.min.io/docs/distributed-minio-quickstart-guide.html)." -## 3. Criar seu bucket do MinIO para o {% data variables.product.prodname_registry %} +## 3. Create your MinIO bucket for {% data variables.product.prodname_registry %} -1. Instalar o cliente do MinIO. +1. Install the MinIO client. ```shell $ docker pull minio/mc ``` -2. Criar um bucket com uma URL de host que {% data variables.product.prodname_ghe_server %} pode acessar. +2. Create a bucket with a host URL that {% data variables.product.prodname_ghe_server %} can access. - * Exemplo de implantação local: + * Local deployments example: ```shell $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @localhost:9000" - $ docker run minio/mc BUCKET-NAME + $ docker run minio/mc BUCKET-NAME ``` - Este exemplo pode ser usado para MinIO independente ou MinIO como um gateway NAS. + This example can be used for MinIO standalone or MinIO as a NAS gateway. - * Exemplo de implantações agrupadas: + * Clustered deployments example: ```shell $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @minioclustername.example.com:9000" $ docker run minio/mc mb packages ``` -## Próximas etapas +## Next steps -Para concluir a configuração de armazenamento para {% data variables.product.prodname_registry %}, você precisará copiar a URL de armazenamento do MinIO: +To finish configuring storage for {% data variables.product.prodname_registry %}, you'll need to copy the MinIO storage URL: ``` echo "http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY}@minioclustername.example.com:9000" ``` -Para ver as próximas etapas, confira "[Como habilitar o {% data variables.product.prodname_registry %} com o MinIO](/admin/packages/enabling-github-packages-with-minio)". +For the next steps, see "[Enabling {% data variables.product.prodname_registry %} with MinIO](/admin/packages/enabling-github-packages-with-minio)." diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md index 1ddb6ddcf6..15cdbd6559 100644 --- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md +++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md @@ -1,6 +1,6 @@ --- -title: Sobre as políticas empresariais -intro: 'Com as políticas empresariais, você pode gerenciar as políticas de todas as organizações pertencentes à empresa.' +title: About enterprise policies +intro: 'With enterprise policies, you can manage the policies for all the organizations owned by your enterprise.' versions: ghec: '*' ghes: '*' @@ -9,26 +9,22 @@ type: overview topics: - Enterprise - Policies -ms.openlocfilehash: d452a6f24b3108b915e20b673ebd317a409ac8ae -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147718114' --- -Como ajuda para impor regras de negócios e conformidade regulatória, as políticas oferecem um ponto único de gerenciamento para todas as organizações pertencentes a uma conta empresarial. + +To help you enforce business rules and regulatory compliance, policies provide a single point of management for all the organizations owned by an enterprise account. {% data reusables.enterprise.about-policies %} -Por exemplo, com a política "Permissões base", você pode permitir que os proprietários de organização configurem a política "Permissões base" para as respectivas organizações ou impor um nível de permissões base específico, como "Leitura", a todas as organizações da empresa. +For example, with the "Base permissions" policy, you can allow organization owners to configure the "Base permissions" policy for their organization, or you can enforce a specific base permissions level, such as "Read", for all organizations within the enterprise. -Por padrão, nenhuma política empresarial é imposta. Para identificar as políticas que devem ser impostas a fim de atender aos requisitos exclusivos da empresa, recomendamos examinar todas as políticas disponíveis na conta empresarial, começando com as políticas de gerenciamento de repositório. Para obter mais informações, confira "[Como impor políticas de gerenciamento de repositório na empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)". +By default, no enterprise policies are enforced. To identify policies that should be enforced to meet the unique requirements of your business, we recommend reviewing all the available policies in your enterprise account, starting with repository management policies. For more information, see "[Enforcing repository management polices in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)." -Enquanto você estiver configurando políticas empresariais, como ajuda para entender o impacto da alteração de cada política, você pode ver as configurações atuais das organizações pertencentes à empresa. +While you're configuring enterprise policies, to help you understand the impact of changing each policy, you can view the current configurations for the organizations owned by your enterprise. -{% ifversion ghes %} Outra maneira de impor padrões na empresa é usar ganchos de pré-recebimento, que são scripts executados no {% data variables.product.product_location %} para implementar verificações de qualidade. Para obter mais informações, confira "[Como impor uma política com ganchos de pré-recebimento](/admin/policies/enforcing-policy-with-pre-receive-hooks)". +{% ifversion ghes %} +Another way to enforce standards within your enterprise is to use pre-receive hooks, which are scripts that run on {% data variables.location.product_location %} to implement quality checks. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)." {% endif %} -## Leitura adicional +## Further reading -- "[Sobre as contas corporativas](/admin/overview/about-enterprise-accounts)" +- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)" diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md index 573f4583b1..82c8463b34 100644 --- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md @@ -32,7 +32,7 @@ shortTitle: GitHub Actions policies {% data variables.product.prodname_actions %} helps members of your enterprise automate software development workflows on {% data variables.product.product_name %}. For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)." -{% ifversion ghes %}If you enable {% data variables.product.prodname_actions %}, any{% else %}Any{% endif %} organization on {% data variables.product.product_location %} can use {% data variables.product.prodname_actions %}. You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} use {% data variables.product.prodname_actions %}. By default, organization owners can manage how members use {% data variables.product.prodname_actions %}. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)." +{% ifversion ghes %}If you enable {% data variables.product.prodname_actions %}, any{% else %}Any{% endif %} organization on {% data variables.location.product_location %} can use {% data variables.product.prodname_actions %}. You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} use {% data variables.product.prodname_actions %}. By default, organization owners can manage how members use {% data variables.product.prodname_actions %}. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)." ## Enforcing a policy to restrict the use of {% data variables.product.prodname_actions %} in your enterprise @@ -48,7 +48,7 @@ You can choose to disable {% data variables.product.prodname_actions %} for all {%- ifversion ghes or ghae %} {% note %} - **Note:** To enable access to public actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %}, you must first configure {% data variables.product.product_location %} to connect to {% data variables.product.prodname_dotcom_the_website %}. 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)." + **Note:** To enable access to public actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %}, you must first configure {% data variables.location.product_location %} to connect to {% data variables.product.prodname_dotcom_the_website %}. 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)." {% endnote %} {%- endif %} @@ -86,7 +86,7 @@ You can choose to disable {% data variables.product.prodname_actions %} for all ## Enforcing a policy for fork pull requests in your enterprise -You can enforce policies to control how {% data variables.product.prodname_actions %} behaves for {% data variables.product.product_location %} when members of your enterprise{% ifversion ghec %} or outside collaborators{% endif %} run workflows from forks. +You can enforce policies to control how {% data variables.product.prodname_actions %} behaves for {% data variables.location.product_location %} when members of your enterprise{% ifversion ghec %} or outside collaborators{% endif %} run workflows from forks. {% ifversion ghec %} diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md index 8a3ff71aa6..bedf7001c2 100644 --- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md @@ -183,7 +183,7 @@ To prevent confusion from your developers, you can change this behavior so that {% note %} -**Note:** If a user is signed in to their personal account when they attempt to access any of your enterprise's resources, they'll be automatically signed out and redirected to SSO to sign in to their {% data variables.product.prodname_managed_user %}. For more information, see "[Managing multiple accounts](/enterprise-cloud@latest/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)." +**Note:** If a user is signed in to their personal account when they attempt to access any of your enterprise's resources, they'll be automatically signed out and redirected to SSO to sign in to their {% data variables.enterprise.prodname_managed_user %}. For more information, see "[Managing multiple accounts](/enterprise-cloud@latest/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)." {% endnote %} diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md index 5ec3ef3506..991873cdca 100644 --- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md @@ -304,7 +304,7 @@ You can override the default inherited settings by configuring the settings for {% data reusables.enterprise_user_management.disclaimer-for-git-read-access %} -If you have [enabled private mode](/enterprise/admin/configuration/enabling-private-mode) for {% data variables.product.product_location %}, you can allow repository administrators to enable anonymous Git read access to public repositories. +If you have [enabled private mode](/enterprise/admin/configuration/enabling-private-mode) for {% data variables.location.product_location %}, you can allow repository administrators to enable anonymous Git read access to public repositories. Enabling anonymous Git read access allows users to bypass authentication for custom tools on your enterprise. When you or a repository administrator enable this access setting for a repository, unauthenticated Git operations (and anyone with network access to {% data variables.product.product_name %}) will have read access to the repository without authentication. diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/index.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/index.md index 558ee0d5b4..243364f19b 100644 --- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/index.md +++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/index.md @@ -22,6 +22,7 @@ children: - /enforcing-policies-for-dependency-insights-in-your-enterprise - /enforcing-policies-for-github-actions-in-your-enterprise - /enforcing-policies-for-code-security-and-analysis-for-your-enterprise + - /enforcing-policies-for-personal-access-tokens-in-your-enterprise shortTitle: Enforce policies ms.openlocfilehash: 045831c9b6e9632db2f7743f2cf30d965ee3c327 ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 diff --git a/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md b/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md index 6d5dfd606b..d72c609a0d 100644 --- a/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md +++ b/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md @@ -1,6 +1,6 @@ --- -title: Sobre hooks pre-receive -intro: '*Hooks pre-receive* são scripts executados no dispositivo do {% data variables.product.prodname_ghe_server %} que você pode usar para implementar verificações de qualidade.' +title: About pre-receive hooks +intro: '*Pre-receive hooks* are scripts that run on the {% data variables.product.prodname_ghe_server %} appliance that you can use to implement quality checks.' redirect_from: - /enterprise/admin/developer-workflow/about-pre-receive-hooks - /enterprise/admin/policies/about-pre-receive-hooks @@ -12,26 +12,20 @@ topics: - Enterprise - Policies - Pre-receive hooks -ms.openlocfilehash: a62d5391f9733c4a79ea8ba5d5f8f0d821d47d5c -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145093928' --- -Quando ocorre um push, cada script é executado em um ambiente isolado e pode executar verificações no conteúdo do push. Os scripts farão o push ser aceito se o status de saída for 0, ou farão o push ser rejeitado se o status de saída for diferente de zero. +When a push occurs, each script runs in an isolated environment and can perform checks on the content of the push. The scripts will cause the push to be accepted if the exit status is 0, or rejected if the exit status is non-zero. -## Cenários de uso -Use os hooks pre-receive para cumprir com as regras corporativas, aplicar a conformidade regulamentar e evitar certos erros comuns. +## Usage scenarios +Use pre-receive hooks to satisfy business rules, enforce regulatory compliance, and prevent certain common mistakes. -Exemplos de uso dos hooks pre-receive: +Examples of how you can use pre-receive hooks: -- Exigir que as mensagens de commit sigam determinado padrão ou formato, como incluir um número de ticket válido ou ter um tamanho especificado; -- Bloquear um branch ou repositório rejeitando todos os pushes; -- Evitar a inclusão de dados confidenciais no repositório bloqueando palavras-chave, padrões ou tipos de arquivos. -- Evitar que o autor da pull request faça merge em suas próprias alterações. +- Require commit messages to follow a specific pattern or format, such as including a valid ticket number or being over a certain length. +- Lock a branch or repository by rejecting all pushes. +- Prevent sensitive data from being added to the repository by blocking keywords, patterns or file types. +- Prevent a PR author from merging their own changes. -## Fluxos de trabalho e impacto no desempenho -O impacto para os desenvolvedores e seus fluxos de trabalho pode ser significativo e deve ser considerado atentamente. Hooks pre-receive baseados nas demandas corporativas e implementados com cuidado trarão mais benefícios para a organização como um todo. +## Impact on performance and workflows +Impact to developers and their workflows can be significant and must be considered carefully. Pre-receive hooks that are based on business needs and implemented thoughtfully will provide the most benefit to the organization as a whole. -Os ganchos de pré-recebimento podem ter efeitos indesejados no desempenho do {% data variables.product.product_location %}, devendo ser implementados e analisados com atenção. +Pre-receive hooks can have unintended effects on the performance of {% data variables.location.product_location %} and should be carefully implemented and reviewed. diff --git a/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md b/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md index 9f04f3bd51..90a4866503 100644 --- a/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md +++ b/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md @@ -1,6 +1,6 @@ --- -title: Criar um script de hook pre-receive -intro: Use os scripts de hooks pre-receive a fim de criar requisitos para aceitar ou rejeitar um push com base no conteúdo. +title: Creating a pre-receive hook script +intro: Use pre-receive hook scripts to create requirements for accepting or rejecting a push based on the contents. miniTocMaxHeadingLevel: 3 redirect_from: - /enterprise/admin/developer-workflow/creating-a-pre-receive-hook-script @@ -14,138 +14,145 @@ topics: - Policies - Pre-receive hooks shortTitle: Pre-receive hook scripts -ms.openlocfilehash: 3d01ba3d5d189e65cbd2b4589af9072571837944 -ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '146332349' --- -Veja exemplos de ganchos de pré-recebimento do {% data variables.product.prodname_ghe_server %} no [repositório `github/platform-samples`](https://github.com/github/platform-samples/tree/master/pre-receive-hooks). +You can see examples of pre-receive hooks for {% data variables.product.prodname_ghe_server %} in the [`github/platform-samples` repository](https://github.com/github/platform-samples/tree/master/pre-receive-hooks). -## Gravar um script de hook pre-receive -Um script de hook pre-receive é executado em um ambiente de hook pre-receive em {% data variables.product.product_location %}. Ao criar um script de hook pre-receive, considere a entrada, saída, estado de saída e variáveis de ambiente disponíveis. +## Writing a pre-receive hook script +A pre-receive hook script executes in a pre-receive hook environment on {% data variables.location.product_location %}. When you create a pre-receive hook script, consider the available input, output, exit status, and environment variables. -### Entrada (`stdin`) -Depois que um push ocorrer e antes que qualquer referência seja atualizada para o repositório remoto, o processo `git-receive-pack` no {% data variables.product.product_location %} invocará o script do gancho de pré-recebimento. A entrada padrão para o script, `stdin`, é uma cadeia de caracteres que contém uma linha para cada referência a ser atualizada. Cada linha contém o nome antigo do objeto para ref, o novo nome do objeto para o ref e o nome completo do ref. +### Input (`stdin`) +After a push occurs and before any refs are updated for the remote repository, the `git-receive-pack` process on {% data variables.location.product_location %} invokes the pre-receive hook script. Standard input for the script, `stdin`, is a string containing a line for each ref to update. Each line contains the old object name for the ref, the new object name for the ref, and the full name of the ref. ``` SP SP LF ``` -Essa frase representa os argumentos a seguir. +This string represents the following arguments. -| Argumento | Descrição | +| Argument | Description | | :------------- | :------------- | -| `` | Nome do objeto antigo armazenado na referência.
Quando você cria uma referência, o valor é 40 zeros. | -| `` | Novo nome de objeto a ser armazenado na referência.
Quando você exclui uma referência, o valor é 40 zeros. | -| `` | O nome completo da ref. | +| `` | Old object name stored in the ref.
When you create a new ref, the value is 40 zeroes. | +| `` | New object name to be stored in the ref.
When you delete a ref, the value is 40 zeroes. | +| `` | The full name of the ref. | -Para obter mais informações sobre `git-receive-pack`, confira "[git-receive-pack](https://git-scm.com/docs/git-receive-pack)" na documentação do Git. Para obter mais informações sobre as referências, confira "[Referências do Git](https://git-scm.com/book/en/v2/Git-Internals-Git-References)" em *Pro Git*. +For more information about `git-receive-pack`, see "[git-receive-pack](https://git-scm.com/docs/git-receive-pack)" in the Git documentation. For more information about refs, see "[Git References](https://git-scm.com/book/en/v2/Git-Internals-Git-References)" in *Pro Git*. -### Saída (`stdout`) +### Output (`stdout`) -A saída padrão do script, `stdout`, é transmitida novamente para o cliente. As instruções `echo` ficarão visíveis para o usuário na linha de comando ou na interface do usuário. +The standard output for the script, `stdout`, is passed back to the client. Any `echo` statements will be visible to the user on the command line or in the user interface. -### Status da saída +### Exit status -O status de saída de um script pre-receive determina se o push será aceito. +The exit status of a pre-receive script determines if the push will be accepted. -| Valor de status de saída | Ação | +| Exit-status value | Action | | :- | :- | -| 0 | O push será aceito. | -| diferente de zero | O push será rejeitado. | +| 0 | The push will be accepted. | +| non-zero | The push will be rejected. | -### Variáveis de ambiente +### Environment variables -Além da entrada padrão para o script de gancho de pré-recebimento, `stdin`, o {% data variables.product.prodname_ghe_server %} disponibiliza as variáveis a seguir no ambiente do Bash para a execução do script. Para obter mais informações sobre o `stdin` do script de gancho de pré-recebimento, confira "[Entrada (`stdin`)](#input-stdin)". +In addition to the standard input for your pre-receive hook script, `stdin`, {% data variables.product.prodname_ghe_server %} makes the following variables available in the Bash environment for your script's execution. For more information about `stdin` for your pre-receive hook script, see "[Input (`stdin`)](#input-stdin)." -Diferentes variáveis de ambiente estão disponíveis para o seu script de hook pre-receive dependendo do que acionar o script. +Different environment variables are available to your pre-receive hook script depending on what triggers the script to run. -- [Sempre disponível](#always-available) -- [Disponível para pushes por meio da interface da Web ou da API](#available-for-pushes-from-the-web-interface-or-api) -- [Disponível para mesclagem de solicitação de pull](#available-for-pull-request-merges) -- [Disponível para pushes que usam a autenticação SSH](#available-for-pushes-using-ssh-authentication) +- [Always available](#always-available) +- [Available for pushes from the web interface or API](#available-for-pushes-from-the-web-interface-or-api) +- [Available for pull request merges](#available-for-pull-request-merges) +- [Available for pushes using SSH authentication](#available-for-pushes-using-ssh-authentication) -#### Sempre disponível +#### Always available -As seguintes variáveis estão sempre disponíveis no ambiente de do hook pre-receive. +The following variables are always available in the pre-receive hook environment. -| Variável | Descrição | Valor de exemplo | +| Variable | Description | Example value | | :- | :- | :- | -|
$GIT_DIR
| Caminho para o repositório remoto na instância | /data/user/repositories/a/ab/
a1/b2/34/100001234/1234.git | -|
$GIT_PUSH_OPTION_COUNT
| O número de opções de push enviadas pelo cliente com `--push-option`. Para obter mais informações, confira "[git-push](https://git-scm.com/docs/git-push#Documentation/git-push.txt---push-optionltoptiongt)" na documentação do Git. | 1 | -|
$GIT\_PUSH\_OPTION\_N
| Quando _N_ for um número inteiro que começa no 0, essa variável conterá a cadeia de caracteres da opção de push enviada pelo cliente. A primeira opção enviada é armazenada em `GIT_PUSH_OPTION_0`, a segunda opção enviada é armazenada em `GIT_PUSH_OPTION_1` etc. Para obter mais informações sobre as opções de push, confira "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" na documentação do Git. | abcd |{% ifversion ghes %} -|
$GIT_USER_AGENT
| String de usuário-agente enviada pelo cliente Git que realizou push das alterações | git/2.0.0{% endif %} -|
$GITHUB_REPO_NAME
| Nome do repositório que está sendo atualizado no formato _NOME_/_PROPRIETÁRIO_ | octo-org/hello-enterprise | -|
$GITHUB_REPO_PUBLIC
| Booleano público, que representa se o repositório está sendo atualizado |
  • true: A visibilidade do repositório é pública
  • false: A visibilidade do repositório é privada ou interna
-|
$GITHUB_USER_IP
| Endereço IP do cliente que iniciou o push | 192.0.2.1 | -|
$GITHUB_USER_LOGIN
| Nome de usuário para a conta que iniciou o push | octocat | +|
$GIT_DIR
| Path to the remote repository on the instance | /data/user/repositories/a/ab/
a1/b2/34/100001234/1234.git | +|
$GIT_PUSH_OPTION_COUNT
| The number of push options that were sent by the client with `--push-option`. For more information, see "[git-push](https://git-scm.com/docs/git-push#Documentation/git-push.txt---push-optionltoptiongt)" in the Git documentation. | 1 | +|
$GIT\_PUSH\_OPTION\_N
| Where _N_ is an integer starting at 0, this variable contains the push option string that was sent by the client. The first option that was sent is stored in `GIT_PUSH_OPTION_0`, the second option that was sent is stored in `GIT_PUSH_OPTION_1`, and so on. For more information about push options, see "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" in the Git documentation. | abcd |{% ifversion ghes %} +|
$GIT_USER_AGENT
| User-agent string sent by the Git client that pushed the changes | git/2.0.0{% endif %} +|
$GITHUB_REPO_NAME
| Name of the repository being updated in _NAME_/_OWNER_ format | octo-org/hello-enterprise | +|
$GITHUB_REPO_PUBLIC
| Boolean representing whether the repository being updated is public |
  • true: Repository's visibility is public
  • false: Repository's visibility is private or internal
+|
$GITHUB_USER_IP
| IP address of client that initiated the push | 192.0.2.1 | +|
$GITHUB_USER_LOGIN
| Username for account that initiated the push | octocat | -#### Disponível para pushes a partir da interface web ou API +#### Available for pushes from the web interface or API -A variável `$GITHUB_VIA` ficará disponível no ambiente do gancho de pré-recebimento quando for feita a atualização de referência que dispara o gancho por meio da interface da Web ou da API do {% data variables.product.prodname_ghe_server %}. O valor descreve a ação que atualizou o ref. +The `$GITHUB_VIA` variable is available in the pre-receive hook environment when the ref update that triggers the hook occurs via either the web interface or the API for {% data variables.product.prodname_ghe_server %}. The value describes the action that updated the ref. -| Valor | Ação | Mais informações | +| Value | Action | More information | | :- | :- | :- | -|
auto-merge deployment api
| Merge automático do branch base através de uma implantação criada com a API | "[Criar uma implantação](/rest/reference/deployments#create-a-deployment)" na documentação da API REST | -|
blob#save
| Mudar para o conteúdo de um arquivo na interface web | "[Como editar arquivos](/repositories/working-with-files/managing-files/editing-files)" | -|
branch merge api
| Merge de um branch através da API | "[Mesclar um branch](/rest/reference/branches#merge-a-branch)" na documentação da API REST | -|
branches page delete button
| Exclusão de um branch na interface web | "[Como criar e excluir branches no seu repositório](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" | -|
git refs create api
| Criação de um ref através da API | "[Banco de dados do Git](/rest/reference/git#create-a-reference)" na documentação da API REST | -|
git refs delete api
| Exclusão de uma ref através da API | "[Banco de dados do Git](/rest/reference/git#delete-a-reference)" na documentação da API REST | -|
git refs update api
| Atualização de um ref através da API | "[Banco de dados do Git](/rest/reference/git#update-a-reference)" na documentação da API REST | -|
git repo contents api
| Mudança no conteúdo de um arquivo através da API | "[Criar ou atualizar o conteúdo do arquivo](/rest/reference/repos#create-or-update-file-contents)" na documentação da API REST | -{%- ifversion ghes %} | `merge ` | Mesclagem de uma solicitação de pull usando a mesclagem automática | "[Mesclar uma solicitação de pull automaticamente](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)" | {%- endif %} |
merge base into head
| Atualização do branch do tópico com base no branch base quando o branch base exigir verificações de status rígidas (por meio de **Atualizar branch** em uma solicitação de pull, por exemplo) | "[Sobre os branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" | |
pull request branch delete button
| Exclusão de um branch do tópico de uma solicitação de pull na interface da Web | "[Como excluir e restaurar branches em uma solicitação de pull](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#deleting-a-branch-used-for-a-pull-request)" | |
pull request branch undo button
| Restauração de um branch do tópico com base em uma solicitação de pull na interface da Web | "[Como excluir e restaurar branches em uma solicitação de pull](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#restoring-a-deleted-branch)" | |
pull request merge api
| Mesclagem de uma solicitação de pull por meio da API | "[Pulls](/rest/reference/pulls#merge-a-pull-request)" na documentação da API REST | |
pull request merge button
| Mesclagem de uma solicitação de pull na interface da Web | "[Como mesclar uma solicitação de pull](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request#merging-a-pull-request-on-github)" | |
pull request revert button
| Reversão de uma solicitação de pull | "[Como reverter uma solicitação de pull](/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request)" | |
releases delete button
| Exclusão de uma versão | "[Como gerenciar as versões em um repositório](/github/administering-a-repository/managing-releases-in-a-repository#deleting-a-release)" | |
stafftools branch restore
| Restauração de um branch por meio do painel de administração do site | "[Painel de administração do site](/admin/configuration/site-admin-dashboard#repositories)" | |
tag create api
| Criação de uma marca por meio da API | "[Banco de dados do Git](/rest/reference/git#create-a-tag-object)" na documentação da API REST | |
slumlord (#SHA)
| Commit por meio do Subversion | "[Suporte para clientes do Subversion](/github/importing-your-projects-to-github/support-for-subversion-clients#making-commits-to-subversion)" | |
web branch create
| Criação de um branch por meio da interface da Web | "[Como criar e excluir branches no seu repositório](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)" | +|
auto-merge deployment api
| Automatic merge of the base branch via a deployment created with the API | "[Create a deployment](/rest/reference/deployments#create-a-deployment)" in the REST API documentation | +|
blob#save
| Change to a file's contents in the web interface | "[Editing files](/repositories/working-with-files/managing-files/editing-files)" | +|
branch merge api
| Merge of a branch via the API | "[Merge a branch](/rest/reference/branches#merge-a-branch)" in the REST API documentation | +|
branches page delete button
| Deletion of a branch in the web interface | "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" | +|
git refs create api
| Creation of a ref via the API | "[Git database](/rest/reference/git#create-a-reference)" in the REST API documentation | +|
git refs delete api
| Deletion of a ref via the API | "[Git database](/rest/reference/git#delete-a-reference)" in the REST API documentation | +|
git refs update api
| Update of a ref via the API | "[Git database](/rest/reference/git#update-a-reference)" in the REST API documentation | +|
git repo contents api
| Change to a file's contents via the API | "[Create or update file contents](/rest/reference/repos#create-or-update-file-contents)" in the REST API documentation | +{%- ifversion ghes %} +| `merge ` | Merge of a pull request using auto-merge | "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)" | +{%- endif %} +|
merge base into head
| Update of the topic branch from the base branch when the base branch requires strict status checks (via **Update branch** in a pull request, for example) | "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" | +|
pull request branch delete button
| Deletion of a topic branch from a pull request in the web interface | "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#deleting-a-branch-used-for-a-pull-request)" | +|
pull request branch undo button
| Restoration of a topic branch from a pull request in the web interface | "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#restoring-a-deleted-branch)" | +|
pull request merge api
| Merge of a pull request via the API | "[Pulls](/rest/reference/pulls#merge-a-pull-request)" in the REST API documentation | +|
pull request merge button
| Merge of a pull request in the web interface | "[Merging a pull request](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request#merging-a-pull-request-on-github)" | +|
pull request revert button
| Revert of a pull request | "[Reverting a pull request](/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request)" | +|
releases delete button
| Deletion of a release | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#deleting-a-release)" | +|
stafftools branch restore
| Restoration of a branch from the site admin dashboard | "[Site admin dashboard](/admin/configuration/site-admin-dashboard#repositories)" | +|
tag create api
| Creation of a tag via the API | "[Git database](/rest/reference/git#create-a-tag-object)" in the REST API documentation | +|
slumlord (#SHA)
| Commit via Subversion | "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients#making-commits-to-subversion)" | +|
web branch create
| Creation of a branch via the web interface | "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)" | -#### Disponível para merge de pull request +#### Available for pull request merges -As variáveis a seguir estão disponíveis no ambiente de hook pre-receive quando o push que aciona o hook é um push devido ao merge de um pull request. +The following variables are available in the pre-receive hook environment when the push that triggers the hook is a push due to the merge of a pull request. -| Variável | Descrição | Valor de exemplo | +| Variable | Description | Example value | | :- | :- | :- | -|
$GITHUB_PULL_REQUEST_AUTHOR_LOGIN
| Nome de usuário da conta que criou o pull request | octocat | -|
$GITHUB_PULL_REQUEST_HEAD
| O nome do branch do tópico da solicitação de pull, no formato `USERNAME:BRANCH` | octocat:fix-bug | -|
$GITHUB_PULL_REQUEST_BASE
| O nome do branch base da solicitação de pull, no formato `USERNAME:BRANCH` | octocat:main | +|
$GITHUB_PULL_REQUEST_AUTHOR_LOGIN
| Username of account that authored the pull request | octocat | +|
$GITHUB_PULL_REQUEST_HEAD
| The name of the pull request's topic branch, in the format `USERNAME:BRANCH` | octocat:fix-bug | +|
$GITHUB_PULL_REQUEST_BASE
| The name of the pull request's base branch, in the format `USERNAME:BRANCH` | octocat:main | -#### Disponível para pushes que usam autenticação SSH +#### Available for pushes using SSH authentication -| Variável | Descrição | Valor de exemplo | +| Variable | Description | Example value | | :- | :- | :- | -|
$GITHUB_PUBLIC_KEY_FINGERPRINT
| A impressão digital da chave pública para o usuário que fez push das alterações | a1:b2:c3:d4:e5:f6:g7:h8:i9:j0:k1:l2:m3:n4:o5:p6 | +|
$GITHUB_PUBLIC_KEY_FINGERPRINT
| The public key fingerprint for the user who pushed the changes | a1:b2:c3:d4:e5:f6:g7:h8:i9:j0:k1:l2:m3:n4:o5:p6 | -## Configurar permissões e fazer push de um hook pre-receive para o {% data variables.product.prodname_ghe_server %} +## Setting permissions and pushing a pre-receive hook to {% data variables.product.prodname_ghe_server %} -Um script de hook pre-receive está contido em um repositório em {% data variables.product.product_location %}. O administrador do site deve considerar as permissões do repositório e garantir que somente os usuários adequados tenham acesso. +A pre-receive hook script is contained in a repository on {% data variables.location.product_location %}. A site administrator must take into consideration the repository permissions and ensure that only the appropriate users have access. -Recomendamos consolidar os hooks em um único repositório. Se o repositório do gancho consolidado for público, o `README.md` poderá ser usado para explicar a imposição das políticas. Além disso, é possível aceitar contribuições via pull request. No entanto, os hooks pre-receive só podem ser adicionados pelo branch padrão. Em fluxos de trabalho de teste, devem ser usados forks do repositório com a devida configuração. +We recommend consolidating hooks to a single repository. If the consolidated hook repository is public, the `README.md` can be used to explain policy enforcements. Also, contributions can be accepted via pull requests. However, pre-receive hooks can only be added from the default branch. For a testing workflow, forks of the repository with configuration should be used. -1. Para usuários de Mac, certifique-se de que os scripts tenham estas permissões de execução: +1. For Mac users, ensure the scripts have execute permissions: ```shell - $ sudo chmod +x SCRIPT_FILE.sh + $ sudo chmod +x SCRIPT_FILE.sh ``` - Para usuários de Windows, certifique-se de que os scripts tenham estas permissões de execução: + For Windows users, ensure the scripts have execute permissions: ```shell - git update-index --chmod=+x SCRIPT_FILE.sh + git update-index --chmod=+x SCRIPT_FILE.sh ``` -2. Faça o commit e push para o repositório designado para os hooks pre-receive em {% data variables.product.product_location %}. +2. Commit and push to the designated repository for pre-receive hooks on {% data variables.location.product_location %}. ```shell - $ git commit -m "YOUR COMMIT MESSAGE" + $ git commit -m "YOUR COMMIT MESSAGE" $ git push ``` -3. [Crie o gancho de pré-recebimento](/enterprise/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance/#creating-pre-receive-hooks) na instância do {% data variables.product.prodname_ghe_server %}. +3. [Create the pre-receive hook](/enterprise/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance/#creating-pre-receive-hooks) on the {% data variables.product.prodname_ghe_server %} instance. -## Testar scripts pre-receive no local -Você pode testar um script do hook pre-receive localmente antes de criá-lo ou atualizá-lo em {% data variables.product.product_location %}. Uma forma de fazer isso é criar um ambiente Docker local para funcionar como repositório remoto que pode executar o hook pre-receive. +## Testing pre-receive scripts locally +You can test a pre-receive hook script locally before you create or update it on {% data variables.location.product_location %}. One method is to create a local Docker environment to act as a remote repository that can execute the pre-receive hook. {% data reusables.linux.ensure-docker %} -2. Crie um arquivo chamado `Dockerfile.dev` contendo: +2. Create a file called `Dockerfile.dev` containing: ```dockerfile FROM gliderlabs/alpine:3.3 @@ -167,7 +174,7 @@ Você pode testar um script do hook pre-receive localmente antes de criá-lo ou CMD ["/usr/sbin/sshd", "-D"] ``` -3. Crie um script de pré-recebimento de teste chamado `always_reject.sh`. Este exemplo de script rejeitará todos os pushes, o que é importante para bloquear um repositório: +3. Create a test pre-receive script called `always_reject.sh`. This example script will reject all pushes, which is useful for locking a repository: ``` #!/usr/bin/env bash @@ -176,13 +183,13 @@ Você pode testar um script do hook pre-receive localmente antes de criá-lo ou exit 1 ``` -4. Verifique se os scripts `always_reject.sh` têm permissões de execução: +4. Ensure the `always_reject.sh` scripts has execute permissions: ```shell $ chmod +x always_reject.sh ``` -5. No diretório que contém `Dockerfile.dev`, compile uma imagem: +5. From the directory containing `Dockerfile.dev`, build an image: ```shell $ docker build -f Dockerfile.dev -t pre-receive.dev . @@ -205,32 +212,32 @@ Você pode testar um script do hook pre-receive localmente antes de criá-lo ou > Successfully built dd8610c24f82 ``` -6. Execute um contêiner de dados que contenha uma chave SSH gerada: +6. Run a data container that contains a generated SSH key: ```shell $ docker run --name data pre-receive.dev /bin/true ``` -7. Copie o gancho de pré-recebimento de teste `always_reject.sh` para o contêiner de dados: +7. Copy the test pre-receive hook `always_reject.sh` into the data container: ```shell $ docker cp always_reject.sh data:/home/git/test.git/hooks/pre-receive ``` -8. Execute um contêiner de aplicativo que executa `sshd` e executa o gancho. Anote o ID do contêiner: +8. Run an application container that runs `sshd` and executes the hook. Take note of the container id that is returned: ```shell $ docker run -d -p 52311:22 --volumes-from data pre-receive.dev > 7f888bc700b8d23405dbcaf039e6c71d486793cad7d8ae4dd184f4a47000bc58 ``` -9. Copie a chave SSH gerada do contêiner de dados para a máquina local: +9. Copy the generated SSH key from the data container to the local machine: ```shell $ docker cp data:/home/git/.ssh/id_ed25519 . ``` -10. Modifique o repositório remoto de um repositório de teste e efetue push para o repositório `test.git` no contêiner do Docker. Este exemplo usa `git@github.com:octocat/Hello-World.git`, mas você poderá usar qualquer repositório que desejar. Este exemplo pressupõe que a sua máquina local (127.0.0.1) está vinculando a porta 52311, mas você pode usar outro endereço IP se o docker estiver sendo executado em uma máquina remota. +10. Modify the remote of a test repository and push to the `test.git` repo within the Docker container. This example uses `git@github.com:octocat/Hello-World.git` but you can use any repository you want. This example assumes your local machine (127.0.0.1) is binding port 52311, but you can use a different IP address if docker is running on a remote machine. ```shell $ git clone git@github.com:octocat/Hello-World.git @@ -249,7 +256,7 @@ Você pode testar um script do hook pre-receive localmente antes de criá-lo ou > error: failed to push some refs to 'git@192.168.99.100:test.git' ``` - Observe que o push foi rejeitado após a execução do hook pre-receive e o eco da saída do script. + Notice that the push was rejected after executing the pre-receive hook and echoing the output from the script. -## Leitura adicional - - "[Como personalizar o Git – Um exemplo de política imposta pelo Git](https://git-scm.com/book/en/v2/Customizing-Git-An-Example-Git-Enforced-Policy)" do *site do Pro Git* +## Further reading + - "[Customizing Git - An Example Git-Enforced Policy](https://git-scm.com/book/en/v2/Customizing-Git-An-Example-Git-Enforced-Policy)" from the *Pro Git website* diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md index 0a7cf2b487..96b0308009 100644 --- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Adicionando organizações à sua empresa -intro: É possível criar novas organizações ou convidar organizações existentes para gerenciar dentro da sua empresa. +title: Adding organizations to your enterprise +intro: You can create new organizations or invite existing organizations to manage within your enterprise. redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account - /articles/adding-organizations-to-your-enterprise-account @@ -15,63 +15,59 @@ topics: - Organizations shortTitle: Add organizations permissions: Enterprise owners can add organizations to an enterprise. -ms.openlocfilehash: 09e4fa9c1b33f50e35f6088eb671b90df4a5eda3 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147573350' --- -## Sobre a adição de organizações à sua conta corporativa -Sua conta corporativa pode ser proprietária de organizações. Os integrantes da sua empresa podem colaborar em projetos relacionados dentro de uma organização. Para obter mais informações, confira "[Sobre as organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)". +## About addition of organizations to your enterprise account -Você pode adicionar organizações à sua conta corporativa. Se você não usar {% data variables.product.prodname_emus %}, poderá adicionar organizações existentes em {% data variables.product.product_location %} à sua empresa. Você não pode adicionar uma organização existente de um {% data variables.product.prodname_emu_enterprise %} a uma empresa diferente. +Your enterprise account can own organizations. Members of your enterprise can collaborate across related projects within an organization. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." -{% data reusables.enterprise.create-an-enterprise-account %} Para obter mais informações, confira "[Como criar uma conta corporativa](/admin/overview/creating-an-enterprise-account)". +You can add new organizations to your enterprise account. If you do not use {% data variables.product.prodname_emus %}, you can add existing organizations on {% data variables.location.product_location %} to your enterprise. You cannot add an existing organization from an {% data variables.enterprise.prodname_emu_enterprise %} to a different enterprise. -Depois de adicionar uma organização existente à sua empresa, os recursos da organização permanecerão acessíveis aos membros nas mesmas URLs e as alterações a seguir serão aplicadas. +{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)." -- Os membros da organização se tornarão membros da empresa, e {% data variables.product.company_short %} cobrará a conta corporativa pelo uso da organização. Você precisa garantir que a conta corporativa tenha licenças suficientes para acomodar eventuais novos membros. Para obter mais informações, confira "[Sobre a cobrança para a empresa](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)". -- Os proprietários empresariais podem gerenciar a própria função dentro da organização. Para obter mais informações, confira "[Como gerenciar sua função em uma organização pertencente à sua empresa](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)". -- Todas as políticas aplicadas à empresa serão aplicadas à organização. Para obter mais informações, confira "[Sobre as políticas empresariais](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)." -- Se o SSO do SAML estiver configurado para a conta corporativa, a configuração SAML da empresa se aplicará à organização. Se a organização tiver usado o SSO do SAML, a configuração da conta corporativa substituirá a configuração da organização. O SCIM não está disponível para contas corporativas, portanto, o SCIM será desabilitado para a organização. Para obter mais informações, confira "[Configurar o logon único do SAML para sua empresa](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise)" e "[Alternar sua configuração do SAML de uma organização para uma conta corporativa](/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)". -- Se o SSO do SAML foi configurado para a organização, os PATs (tokens de acesso pessoal) existentes dos membros ou chaves SSH que foram autorizados a acessar os recursos da organização serão autorizados a acessar os mesmos recursos. Para acessar organizações adicionais pertencentes à empresa, os membros precisam autorizar o PAT ou a chave. Para obter mais informações, confira "[Como autorizar um token de acesso pessoal para uso com o logon único do SAML](/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" e "[Como autorizar uma chave SSH para uso com o logon único do SAML](/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)". -- Se a organização estava conectada a {% data variables.product.prodname_ghe_server %} ou {% data variables.product.prodname_ghe_managed %} usando {% data variables.product.prodname_github_connect %}, a adição da organização a uma empresa não atualiza a conexão. Os recursos de {% data variables.product.prodname_github_connect %} não funcionarão mais para a organização. Para continuar usando o {% data variables.product.prodname_github_connect %}, você precisa desabilitar e habilitar novamente o recurso. Para obter mais informações, consulte os seguintes artigos. +After you add an existing organization to your enterprise, the organization's resources remain accessible to members at the same URLs, and the following changes will apply. - - "[Gerenciando {% data variables.product.prodname_github_connect %}](/enterprise-server@latest/admin/configuration/configuring-github-connect/managing-github-connect)" na documentação {% data variables.product.prodname_ghe_server %} - - "[Gerenciando {% data variables.product.prodname_github_connect %}](/github-ae@latest/admin/configuration/configuring-github-connect/managing-github-connect)" na documentação {% data variables.product.prodname_ghe_managed %} -- Se a organização usou dados de aplicativos do {% data variables.product.prodname_marketplace %}, a organização pode continuar a usar os aplicativos, mas precisa pagar o fornecedor diretamente. Para obter mais informações, contate o fornecedor do aplicativo. +- The organization's members will become members of the enterprise, and {% data variables.product.company_short %} will bill the enterprise account for the organization's usage. You must ensure that the enterprise account has enough licenses to accommodate any new members. For more information, see "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)." +- Enterprise owners can manage their role within the organization. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)." +- Any policies applied to the enterprise will apply to the organization. For more information, see "[About enterprise policies](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)." +- If SAML SSO is configured for the enterprise account, the enterprise's SAML configuration will apply to the organization. If the organization used SAML SSO, the enterprise account's configuration will replace the organization's configuration. SCIM is not available for enterprise accounts, so SCIM will be disabled for the organization. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise)" and "[Switching your SAML configuration from an organization to an enterprise account](/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." +- If SAML SSO was configured for the organization, members' existing {% data variables.product.pat_generic %} or SSH keys that were authorized to access the organization's resources will be authorized to access the same resources. To access additional organizations owned by the enterprise, members must authorize the {% data variables.product.pat_generic %} or key. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." +- If the organization was connected to {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %} using {% data variables.product.prodname_github_connect %}, adding the organization to an enterprise will not update the connection. {% data variables.product.prodname_github_connect %} features will no longer function for the organization. To continue using {% data variables.product.prodname_github_connect %}, you must disable and re-enable the feature. For more information, see the following articles. -## Criar uma organização em sua conta corporativa + - "[Managing {% data variables.product.prodname_github_connect %}](/enterprise-server@latest/admin/configuration/configuring-github-connect/managing-github-connect)" in the {% data variables.product.prodname_ghe_server %} documentation + - "[Managing {% data variables.product.prodname_github_connect %}](/github-ae@latest/admin/configuration/configuring-github-connect/managing-github-connect)" in the {% data variables.product.prodname_ghe_managed %} documentation +- If the organization used billed {% data variables.product.prodname_marketplace %} apps, the organization can continue to use the apps, but must pay the vendor directly. For more information, contact the app's vendor. +- Any coupons will be removed from the organization. To reapply the coupon, [contact our sales team](https://github.com/enterprise/contact). -Novas organizações que você cria nas configurações de sua conta corporativa são incluídas na assinatura da conta corporativa do {% data variables.product.prodname_ghe_cloud %}. +## Creating an organization in your enterprise account -Os proprietários da empresa que criam uma organização pertencente à conta corporativa automaticamente se tornam proprietários da organização. Para obter mais informações sobre os proprietários da organização, confira "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)". +New organizations you create within your enterprise account settings are included in your enterprise account's {% data variables.product.prodname_ghe_cloud %} subscription. + +Enterprise owners who create an organization owned by the enterprise account automatically become organization owners. For more information about organization owners, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." {% data reusables.enterprise-accounts.access-enterprise %} -2. Na guia **Organizações**, acima da lista de organizações, clique em **Nova organização**. - ![Botão Nova organização](/assets/images/help/business-accounts/enterprise-account-add-org.png) -3. Em "Organization name" (Nome da organização), digite um nome para sua organização. - ![Campo usado para digitar o nome de uma nova organização](/assets/images/help/business-accounts/new-organization-name-field.png) -4. Clique em **Criar organização**. -5. Em "Convidar proprietários", digite o nome de usuário de uma pessoa que deseja convidar para se tornar um proprietário da organização e clique em **Convidar**. - ![Campo de pesquisa do proprietário da organização e botão Convidar](/assets/images/help/business-accounts/invite-org-owner.png) -6. Clique em **Concluir**. +2. On the **Organizations** tab, above the list of organizations, click **New organization**. + ![New organization button](/assets/images/help/business-accounts/enterprise-account-add-org.png) +3. Under "Organization name", type a name for your organization. + ![Field to type a new organization name](/assets/images/help/business-accounts/new-organization-name-field.png) +4. Click **Create organization**. +5. Under "Invite owners", type the username of a person you'd like to invite to become an organization owner, then click **Invite**. + ![Organization owner search field and Invite button](/assets/images/help/business-accounts/invite-org-owner.png) +6. Click **Finish**. -## Convidar uma organização para se juntar-se à sua conta corporativa +## Inviting an organization to join your enterprise account -Os proprietários corporativos podem convidar organizações existentes para juntar-se à sua conta corporativa. Se a organização que deseja convidar já pertence a outra empresa, você não poderá enviar um convite até que a empresa anterior desista da propriedade da organização. Para obter mais informações, confira "[Como remover uma organização da sua empresa](/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise)". +Enterprise owners can invite existing organizations to join their enterprise account. If the organization you want to invite is already owned by another enterprise, you will not be able to issue an invitation until the previous enterprise gives up ownership of the organization. For more information, see "[Removing an organization from your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise)." {% data reusables.enterprise-accounts.access-enterprise %} -2. Na guia **Organizações**, acima da lista de organizações, clique **em Convidar organização**. -![Convidar organização](/assets/images/help/business-accounts/enterprise-account-invite-organization.png) -3. Em "Organização", comece a digitar o nome da organização que deseja convidar e selecione-a quando aparecer na lista suspensa. -![Pesquisa de organização](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png) -4. Clique em **Convidar organização**. -5. Os proprietários da organização receberão um e-mail convidando-os para participar da empresa. Pelo menos um proprietário deverá aceitar o convite antes que o processo possa continuar. Você pode cancelar ou reenviar o convite a qualquer momento antes que um proprietário o aprove. -![Cancelar ou reenviar](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png) -6. Uma vez que o proprietário da organização tenha aprovado o convite, você poderá ver o seu estado na lista de convites pendentes. -![Convite pendente](/assets/images/help/business-accounts/enterprise-account-pending.png) -7. Clique em **Aprovar** para concluir a transferência ou em **Cancelar** para cancelá-la. -![Aprovar convite](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png) +2. On the **Organizations** tab, above the list of organizations, click **Invite organization**. +![Invite organization](/assets/images/help/business-accounts/enterprise-account-invite-organization.png) +3. Under "Organization name", start typing the name of the organization you want to invite and select it when it appears in the drop-down list. +![Search for organization](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png) +4. Click **Invite organization**. +5. The organization owners will receive an email inviting them to join the enterprise. At least one owner needs to accept the invitation before the process can continue. You can cancel or resend the invitation at any time before an owner approves it. +![Cancel or resend](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png) +6. Once an organization owner has approved the invitation, you can view its status in the list of pending invitations. +![Pending invitation](/assets/images/help/business-accounts/enterprise-account-pending.png) +7. Click **Approve** to complete the transfer, or **Cancel** to cancel it. +![Approve invitation](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png) diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md index 20770954ca..d4be251522 100644 --- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md +++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md @@ -1,12 +1,12 @@ --- -title: Como adicionar pessoas a equipes +title: Adding people to teams redirect_from: - /enterprise/admin/articles/adding-teams - /enterprise/admin/articles/adding-or-inviting-people-to-teams - /enterprise/admin/guides/user-management/adding-or-inviting-people-to-teams - /enterprise/admin/user-management/adding-people-to-teams - /admin/user-management/adding-people-to-teams -intro: 'Após a criação de uma equipe, os administradores da organização podem adicionar usuários da {% data variables.product.product_location %} e determinar quais repositórios eles poderão acessar.' +intro: 'Once a team has been created, organization admins can add users from {% data variables.location.product_location %} to the team and determine which repositories they have access to.' versions: ghes: '*' ghae: '*' @@ -16,28 +16,26 @@ topics: - Enterprise - Teams - User account -ms.openlocfilehash: 1246641db416630d0faed75821078618a4399eb8 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147884250' --- -Cada equipe tem suas [permissões de acesso definidas individualmente para repositórios pertencentes à sua organização](/articles/permission-levels-for-an-organization). +Each team has its own individually defined [access permissions for repositories owned by your organization](/articles/permission-levels-for-an-organization). -- Integrantes com função de Proprietário podem adicionar ou remover os integrantes atuais de todas as equipes da organização. -- Integrantes de equipes que concedem permissões de administrador só podem modificar a participação e as permissões de repositórios de sua própria equipe. +- Members with the owner role can add or remove existing organization members from all teams. +- Members of teams that give admin permissions can only modify team membership and repositories for that team. -## Configurar uma equipe +## Setting up a team -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.invite_to_team %} {% data reusables.organizations.review-team-repository-access %} +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.invite_to_team %} +{% data reusables.organizations.review-team-repository-access %} {% ifversion ghes %} -## Mapear equipes para grupos LDAP (em instâncias com sincronização LDAP para autenticação de usuários) +## Mapping teams to LDAP groups (for instances using LDAP Sync for user authentication) {% data reusables.enterprise_management_console.badge_indicator %} -Para adicionar um novo integrante a uma equipe sincronizada com um grupo LDAP, adicione o usuário como integrante do grupo LDAP ou entre em contato com o administrador do LDAP. +To add a new member to a team synced to an LDAP group, add the user as a member of the LDAP group, or contact your LDAP administrator. {% endif %} diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md index f6995a06ea..859fe38bc4 100644 --- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md +++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md @@ -1,6 +1,6 @@ --- -title: Integração contínua usando o Jenkins -intro: 'Você pode acionar automaticamente tarefas de criação em um servidor Jenkins quando houver pushes para um repositório na {% data variables.product.product_location %}.' +title: Continuous integration using Jenkins +intro: 'You can automatically trigger build jobs on a Jenkins server when pushes are made to a repository in {% data variables.location.product_location %}.' redirect_from: - /enterprise/admin/developer-workflow/continuous-integration-using-jenkins - /enterprise/admin/user-management/continuous-integration-using-jenkins @@ -13,13 +13,7 @@ topics: - CI - Enterprise shortTitle: CI using Jenkins -ms.openlocfilehash: dacb99db402d0d06aa4a3c4248e1fcabfd2d085d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145094585' --- -## Requisitos +## Requirements -- Siga nosso white paper "[Guia prático de CI com o Jenkins e o GitHub](https://resources.github.com/whitepapers/practical-guide-to-CI-with-Jenkins-and-GitHub/)" para obter instruções passo a passo sobre como disparar trabalhos de build automaticamente em um servidor do Jenkins quando forem efetuados pushes em um repositório do {% data variables.product.product_location %}. +- Follow our white paper "[Practical guide to CI with Jenkins and GitHub](https://resources.github.com/whitepapers/practical-guide-to-CI-with-Jenkins-and-GitHub/)" to get step by step instructions on how you can automatically trigger build jobs on a Jenkins server when pushes are made to a repository in {% data variables.location.product_location %}. diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md index fb8448ad36..d87b91370c 100644 --- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md +++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md @@ -1,6 +1,6 @@ --- -title: Como criar equipes -intro: 'As organizações usam as equipes para criar grupos de integrantes e controlar o acesso aos repositórios. Os integrantes da equipe podem receber permissões de leitura, gravação ou administração em determinados repositórios.' +title: Creating teams +intro: 'Teams give organizations the ability to create groups of members and control access to repositories. Team members can be granted read, write, or admin permissions to specific repositories.' redirect_from: - /enterprise/admin/user-management/creating-teams - /admin/user-management/creating-teams @@ -13,47 +13,55 @@ topics: - Enterprise - Teams - User account -ms.openlocfilehash: 83db75485e7967941fdcd3ab651e638aa1eabb3f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146332333' --- -As equipes são essenciais para vários recursos de colaboração do {% data variables.product.prodname_dotcom %}, como as @mentions da equipe, que chamam a atenção dos integrantes envolvidos em alguma questão específica. Para obter mais informações, confira "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)". +Teams are central to many of {% data variables.product.prodname_dotcom %}'s collaborative features, such as team @mentions to notify appropriate parties that you'd like to request their input or attention. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." -Uma equipe pode representar um grupo dentro da empresa ou incluir pessoas com determinados interesses ou experiências. Por exemplo, uma equipe de especialistas em acessibilidade da {% data variables.product.product_location %} pode envolver pessoas de vários departamentos. As equipes podem representar interesses funcionais que complementam a hierarquia das divisões de uma empresa. +A team can represent a group within your company or include people with certain interests or expertise. For example, a team of accessibility experts on {% data variables.location.product_location %} could comprise of people from several different departments. Teams can represent functional concerns that complement a company's existing divisional hierarchy. -As organizações podem criar vários níveis de equipes aninhadas para refletir a estrutura hierárquica de uma empresa ou grupo. Para obter mais informações, confira "[Sobre as equipes](/enterprise/user/articles/about-teams/#nested-teams)". +Organizations can create multiple levels of nested teams to reflect a company or group's hierarchy structure. For more information, see "[About teams](/enterprise/user/articles/about-teams/#nested-teams)." -## Criar equipes +## Creating a team -Fazer uma combinação prudente de equipes é uma forma poderosa de controlar o acesso ao repositório. Por exemplo, se a sua organização permitir que somente a equipe de engenharia da versão faça push do código para o branch padrão de qualquer repositório, você poderia conceder permissões de **administrador** aos repositórios da organização somente à equipe de engenharia, enquanto todas as outras equipes teriam permissão de **leitura**. +A prudent combination of teams is a powerful way to control repository access. For example, if your organization allows only your release engineering team to push code to the default branch of any repository, you could give only the release engineering team **admin** permissions to your organization's repositories and give all other teams **read** permissions. -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.new_team %} {% data reusables.organizations.team_name %} {% data reusables.organizations.team_description %} {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create-team-choose-parent %} {% data reusables.organizations.create_team %} +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.new_team %} +{% data reusables.organizations.team_name %} +{% data reusables.organizations.team_description %} +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create-team-choose-parent %} +{% data reusables.organizations.create_team %} {% ifversion ghes %} -## Criar equipes com a Sincronização LDAP habilitada +## Creating teams with LDAP Sync enabled -Instâncias que usam o LDAP para fazer autenticação de usuários podem usar a Sincronização LDAP para gerenciar os integrantes de uma equipe. Definir o **DN** (Nome Diferenciado) do grupo no campo **Grupo LDAP** mapeará uma equipe para um grupo LDAP em seu servidor LDAP. Se você usar a Sincronização LDAP para gerenciar os integrantes de uma equipe, não será possível gerenciar a sua equipe na {% data variables.product.product_location %}. Quando a Sincronização LDAP estiver habilitada, a equipe mapeada sincronizará seus integrantes em segundo plano e periodicamente no intervalo configurado. Para obter mais informações, confira "[Como habilitar a Sincronização LDAP](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync)". +Instances using LDAP for user authentication can use LDAP Sync to manage a team's members. Setting the group's **Distinguished Name** (DN) in the **LDAP group** field will map a team to an LDAP group on your LDAP server. If you use LDAP Sync to manage a team's members, you won't be able to manage your team within {% data variables.location.product_location %}. The mapped team will sync its members in the background and periodically at the interval configured when LDAP Sync is enabled. For more information, see "[Enabling LDAP Sync](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync)." -Você deve ser um administrador do site e um proprietário da organização para criar uma equipe com a sincronização LDAP habilitada. +You must be a site admin and an organization owner to create a team with LDAP sync enabled. {% data reusables.enterprise_user_management.ldap-sync-nested-teams %} {% warning %} -**Observações:** -- A Sincronização LDAP gerencia somente a lista de integrantes da equipe. Você deve gerenciar os repositórios e permissões da equipe pelo {% data variables.product.prodname_ghe_server %}. -- Se um grupo LDAP mapeado para um DN for removido, por exemplo, se o grupo LDAP for excluído, todos os integrantes serão removidos da equipe sincronizada do {% data variables.product.prodname_ghe_server %}. Para corrigir isso, mapeie a equipe para um novo DN, adicione os membros da equipe novamente e [sincronize manualmente o mapeamento](/enterprise/admin/authentication/using-ldap#manually-syncing-ldap-accounts). -- Quando a Sincronização LDAP estiver ativada, se uma pessoa for removida de um repositório, ela perderá o acesso. No entanto, suas bifurcações não serão excluídas. Se a pessoa for adicionada a uma equipe e tiver acesso ao repositório original da organização dentro de três meses, seu acesso às bifurcações será restaurado automaticamente na sincronização seguinte. +**Notes:** +- LDAP Sync only manages the team's member list. You must manage the team's repositories and permissions from within {% data variables.product.prodname_ghe_server %}. +- If an LDAP group mapping to a DN is removed, such as if the LDAP group is deleted, then every member is removed from the synced {% data variables.product.prodname_ghe_server %} team. To fix this, map the team to a new DN, add the team members back, and [manually sync the mapping](/enterprise/admin/authentication/using-ldap#manually-syncing-ldap-accounts). +- When LDAP Sync is enabled, if a person is removed from a repository, they will lose access but their forks will not be deleted. If the person is added to a team with access to the original organization repository within three months, their access to the forks will be automatically restored on the next sync. {% endwarning %} -1. Confirme se a [Sincronização LDAP está habilitada](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync). -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.new_team %} {% data reusables.organizations.team_name %} -6. Pesquise um DN do grupo do LDAP ao qual a equipe será mapeada. Se você não souber o DN, digite o nome do grupo do LDAP. O {% data variables.product.prodname_ghe_server %} vai buscar correspondências e preenchimentos automáticos. -![Mapeamento para o DN do grupo LDAP](/assets/images/enterprise/orgs-and-teams/ldap-group-mapping.png) {% data reusables.organizations.team_description %} {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create-team-choose-parent %} {% data reusables.organizations.create_team %} +1. Ensure that [LDAP Sync is enabled](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync). +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.new_team %} +{% data reusables.organizations.team_name %} +6. Search for an LDAP group's DN to map the team to. If you don't know the DN, type the LDAP group's name. {% data variables.product.prodname_ghe_server %} will search for and autocomplete any matches. +![Mapping to the LDAP group DN](/assets/images/enterprise/orgs-and-teams/ldap-group-mapping.png) +{% data reusables.organizations.team_description %} +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create-team-choose-parent %} +{% data reusables.organizations.create_team %} {% endif %} diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md index 2d538ca965..103d51e4a9 100644 --- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md +++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md @@ -1,6 +1,6 @@ --- -title: Exigir autenticação de dois fatores na organização -intro: Você pode exigir que integrantes da organização e colaboradores externos habilitem a autenticação de dois fatores em suas contas pessoais para dificultar o acesso de elementos mal-intencionados a repositórios e configurações da organização. +title: Requiring two-factor authentication for an organization +intro: 'You can require organization members and outside collaborators to enable two-factor authentication for their personal accounts in an organization, making it harder for malicious actors to access an organization''s repositories and settings.' redirect_from: - /enterprise/admin/user-management/requiring-two-factor-authentication-for-an-organization - /admin/user-management/requiring-two-factor-authentication-for-an-organization @@ -14,58 +14,59 @@ topics: - Policies - Security shortTitle: Require 2FA -ms.openlocfilehash: 2f7fe986cf3b13a171f85da9d5fdb74eeed0d648 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146331637' --- -Ao usar o LDAP ou autenticação integrada, a autenticação de dois fatores será compatível em {% data variables.product.product_location %}. Os administradores da organização podem exigir que os integrantes habilitem a autenticação de dois fatores. +When using LDAP or built-in authentication, two-factor authentication is supported on {% data variables.location.product_location %}. Organization administrators can require members to have two-factor authentication enabled. {% data reusables.enterprise_user_management.external_auth_disables_2fa %} -Para obter mais informações, confira "[Sobre a autenticação de dois fatores](/github/authenticating-to-github/about-two-factor-authentication)". +For more information, see "[About two-factor authentication](/github/authenticating-to-github/about-two-factor-authentication)." -## Requisitos para exigir a autenticação de dois fatores +## Requirements for enforcing two-factor authentication -Para exigir que os membros da organização e os colaboradores externos usem a 2FA, você precisa [habilitar a autenticação de dois fatores](/enterprise/user/articles/securing-your-account-with-two-factor-authentication-2fa/) na sua conta pessoal. +Before you can require organization members and outside collaborators to use 2FA, you must [enable two-factor authentication](/enterprise/user/articles/securing-your-account-with-two-factor-authentication-2fa/) for your own personal account. {% warning %} -**Avisos:** +**Warnings:** -- Se você exigir autenticação de dois fatores, os integrantes e colaboradores externos (incluindo contas bot) que não utilizem 2FA serão removidos da organização e perderão acesso aos repositórios dela, inclusive às bifurcações de repositórios privados. Se eles habilitarem a 2FA na conta pessoal em até três meses após terem sido removidos da organização, você poderá [restabelecer os privilégios e as configurações de acesso deles](/enterprise/user/articles/reinstating-a-former-member-of-your-organization). -- Se a 2FA for obrigatória, integrantes da organização ou colaboradores externos que a desabilitarem serão automaticamente removidos da organização. -- Se você for o único proprietário de uma organização que exige autenticação de dois fatores, não poderá desabilitar a 2FA na sua conta pessoal sem desabilitar a autenticação de dois fatores obrigatória na organização. +- When your require two-factor authentication, members and outside collaborators (including bot accounts) who do not use 2FA will be removed from the organization and lose access to its repositories, including their forks of private repositories. If they enable 2FA for their personal account within three months of being removed from the organization, you can [reinstate their access privileges and settings](/enterprise/user/articles/reinstating-a-former-member-of-your-organization). +- When 2FA is required, organization members or outside collaborators who disable 2FA will automatically be removed from the organization. +- If you're the sole owner of an organization that requires two-factor authentication, you won't be able to disable 2FA for your personal account without disabling required two-factor authentication for the organization. {% endwarning %} -Antes de exigir o uso da autenticação de dois fatores, é recomendável notificar os integrantes da organização e os colaboradores externos, pedindo que eles configurem 2FA nas contas deles. Você pode [ver se os membros e os colaboradores externos já usam a 2FA](/enterprise/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled) na guia Pessoas de uma organização. +Before you require use of two-factor authentication, we recommend notifying organization members and outside collaborators and asking them to set up 2FA for their accounts. You can [see if members and outside collaborators already use 2FA](/enterprise/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled) on an organization's People tab. -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %} {% data reusables.organizations.require_two_factor_authentication %} {% data reusables.organizations.removed_outside_collaborators %} +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +{% data reusables.organizations.security %} +{% data reusables.organizations.require_two_factor_authentication %} +{% data reusables.organizations.removed_outside_collaborators %} -## Exibir pessoas removidas da organização +## Viewing people who were removed from your organization -Para ver as pessoas que foram removidas automaticamente da sua organização devido a não conformidade quando você exigiu a autenticação de dois fatores, [pesquise o log de auditoria](/enterprise/admin/guides/installation/searching-the-audit-log/) usando `reason:two_factor_requirement_non_compliance` no campo de pesquisa. +To view people who were automatically removed from your organization for non-compliance when you required two-factor authentication, you can [search the audit log](/enterprise/admin/guides/installation/searching-the-audit-log/) using `reason:two_factor_requirement_non_compliance` in the search field. -{% data reusables.audit_log.octicon_icon %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.audit_log.audit_log_sidebar_for_site_admins %} -4. Insira a consulta de pesquisa usando `reason:two_factor_requirement_non_compliance`. - ![Evento de log de auditoria das ferramentas de equipe que mostra um usuário removido devido a não conformidade com a 2FA](/assets/images/help/2fa/2fa_noncompliance_stafftools_audit_log_search.png) Para restringir a pesquisa a: - - Membros das organizações removidos, insira `action:org.remove_member AND reason:two_factor_requirement_non_compliance` - - Colaboradores externos removidos, insira `action:org.remove_outside_collaborator AND reason:two_factor_requirement_non_compliance` +{% data reusables.audit_log.octicon_icon %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.audit_log.audit_log_sidebar_for_site_admins %} +4. Enter your search query using `reason:two_factor_requirement_non_compliance`. + ![Staff tools audit log event showing a user removed for 2FA non-compliance](/assets/images/help/2fa/2fa_noncompliance_stafftools_audit_log_search.png) + To narrow your search for: + - Organizations members removed, enter `action:org.remove_member AND reason:two_factor_requirement_non_compliance` + - Outside collaborators removed, enter `action:org.remove_outside_collaborator AND reason:two_factor_requirement_non_compliance` - Também é possível ver as pessoas removidas de determinada organização usando o nome da organização na pesquisa: + You can also view people removed from a particular organization by using the organization name in your search: - `org:octo-org AND reason:two_factor_requirement_non_compliance` -5. Clique em **Pesquisar**. +5. Click **Search**. -## Ajudar integrantes e colaboradores externos removidos a voltarem à organização +## Helping removed members and outside collaborators rejoin your organization -Se algum integrante ou colaborador externo for removido da organização quando você habilitar o uso obrigatório da autenticação de dois fatores, o integrante/colaborador receberá um e-mail informando que foi removido. Para solicitar acesso à sua organização, o integrante/colaborador deverá ativar a 2FA na conta pessoal e entrar em contato com o proprietário de uma organização. +If any members or outside collaborators are removed from the organization when you enable required use of two-factor authentication, they'll receive an email notifying them that they've been removed. They should then enable 2FA for their personal account, and contact an organization owner to request access to your organization. -## Leitura adicional +## Further reading -- "[Como ver se os usuários na sua organização têm a 2FA habilitada](/enterprise/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)" -- "[Como proteger sua conta com a 2FA (autenticação de dois fatores)](/enterprise/user/articles/securing-your-account-with-two-factor-authentication-2fa)" -- "[Como restabelecer um ex-membro da sua organização](/enterprise/user/articles/reinstating-a-former-member-of-your-organization)" -- "[Como restabelecer o acesso de um ex-colaborador externo à sua organização](/enterprise/user/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)" +- "[Viewing whether users in your organization have 2FA enabled](/enterprise/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)" +- "[Securing your account with two-factor authentication (2FA)](/enterprise/user/articles/securing-your-account-with-two-factor-authentication-2fa)" +- "[Reinstating a former member of your organization](/enterprise/user/articles/reinstating-a-former-member-of-your-organization)" +- "[Reinstating a former outside collaborator's access to your organization](/enterprise/user/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)" diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md index 426e0b72ad..d30c176041 100644 --- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md +++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md @@ -1,6 +1,6 @@ --- -title: Restaurando uma organização excluída -intro: 'Você pode restaurar parcialmente uma organização que foi anteriormente excluída em {% data variables.product.product_location %}.' +title: Restoring a deleted organization +intro: 'You can partially restore an organization that was previously deleted on {% data variables.location.product_location %}.' versions: ghes: '*' type: how_to @@ -10,49 +10,44 @@ topics: - Organizations shortTitle: Restore organization permissions: 'Site administers can restore an organization on {% data variables.product.product_name %}.' -ms.openlocfilehash: 1963b1e55a9c8047c19bafd087162caa8d5085f2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147063751' --- -## Sobre a restauração da organização -Use o painel de administração do site para restaurar uma organização que foi excluída no {% data variables.product.product_location %}, desde que os índices do Elasticsearch do log de auditoria contenham os dados do evento `org.delete`. +## About organization restoration -Imediatamente após restaurar uma organização, ela não será exatamente a mesma que era antes da exclusão. Você tem que restaurar manualmente os repositórios que pertenciam à organização. Para obter mais informações, confira "[Como restaurar um repositório excluído](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)". +You can use the site admin dashboard to restore an organization that was previously deleted on {% data variables.location.product_location %}, as long as the audit log Elasticsearch indices contain the data for the `org.delete` event. -Você também pode utilizar o log de auditoria para ajudar você a readicionar as equipes manualmente e os integrantes da organização. Para obter mais informações, confira "[Como restaurar membros e equipes](#restoring-members-and-teams)". +Immediately after you restore an organization, the organization will not be exactly the same as it was prior to the deletion. You'll have to manually restore any repositories that were owned by the organization. For more information, see "[Restoring a deleted repository](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)." -## Restaurando uma organização +You can also use the audit log to help you manually re-add teams and organization members. For more information, see "[Restoring members and teams](#restoring-members-and-teams)." + +## Restoring an organization {% data reusables.enterprise_site_admin_settings.access-settings %} -1. Em "Pesquisar usuários, organizações, empresas, equipes, repositórios, gists e aplicativos", pesquise pela organização. +1. Under "Search users, organizations, enterprises, teams, repositories, gists, and applications", search for the organization. - ![Captura de tela do campo de busca e botão Pesquisar](/assets/images/enterprise/stafftools/search-field.png) + ![Screenshot of the search field and Search button](/assets/images/enterprise/stafftools/search-field.png) -1. Em "Contas excluídas", à direita da organização que deseja restaurar, selecione o menu suspenso {% octicon "kebab-horizontal" aria-label="The edit icon" %} e clique em **Recriar**. +1. Under "Deleted accounts", to the right of the organization you want to restore, select the {% octicon "kebab-horizontal" aria-label="The edit icon" %} dropdown menu, then click **Recreate**. - ![Captura de tela do menu suspenso para uma organização excluída](/assets/images/enterprise/stafftools/recreate-organization.png) + ![Screenshot of the dropdown menu for a deleted organization](/assets/images/enterprise/stafftools/recreate-organization.png) -## Restaurando integrantes e equipes +## Restoring members and teams -Você pode usar o log de auditoria para encontrar uma lista dos integrantes e equipes anteriores da organização e, em seguida, recriá-los manualmente. Para obter mais informações sobre como usar o log de auditoria, confira "[Como auditar os usuários em toda a empresa](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise)". +You can use the audit log to find a list of the previous members and teams of the organization, then recreate them manually. For more information about using the audit log, see "[Auditing users across your enterprise](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise)." -Em todas as frases de pesquisa abaixo, substitua ORGANIZAÇÃO pelo nome da organização e EQUIPE pelo nome da equipe. +In all the search phrases below, replace ORGANIZATION with the name of the organization and TEAM with the name of the team. -### Restaurando integrantes da organização +### Restoring organization members -1. Para localizar todos os usuários que foram adicionados e removidos da organização, pesquise `action:org.add_member org:ORGANIZATION` e `action:org.remove_member org:ORGANIZATION` no log de auditoria. -1. Adicione manualmente à organização cada usuário que ainda deve ser um integrante. Para obter mais informações, confira "[Como adicionar pessoas à sua organização](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)". +1. To find all users who were added to and removed from the organization, search the audit log for `action:org.add_member org:ORGANIZATION` and `action:org.remove_member org:ORGANIZATION`. +1. Manually add to the organization each user that should still be a member. For more information, see "[Adding people to your organization](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)." -### Restaurando equipes +### Restoring teams -1. Para localizar cada nome de equipe, pesquise `action:team.create org:ORGANIZATION` no log de auditoria. -1. Recrie a equipe manualmente. Para obter mais informações, confira "[Como criar uma equipe](/organizations/organizing-members-into-teams/creating-a-team)". -1. Para localizar os membros que foram adicionados a cada equipe, pesquise `action:team.add_member team:"ORGANIZATION/TEAM"`. -1. Adicionar manualmente os integrantes da equipe. Para obter mais informações, confira "[Como adicionar membros da organização a uma equipe](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)". -1. Para localizar os repositórios aos quais a equipe recebeu acesso, pesquise `action:team.add_repository team:"ORGANIZATION/TEAM"`. -1. Para localizar o nível de acesso que a equipe recebeu para cada repositório, pesquise `action:team.update_repository_permission team:"ORGANIZATION/TEAM"`. -1. Dê acesso manual à equipe novamente. Para obter mais informações, confira "[Como gerenciar o acesso da equipe a um repositório da organização](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)". +1. To find each team name, search the audit log for `action:team.create org:ORGANIZATION`. +1. Manually recreate the team. For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)." +1. To find the members that have been added to each team, search for `action:team.add_member team:"ORGANIZATION/TEAM"`. +1. Manually re-add the team members. For more information, see "[Adding organization members to a team](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)." +1. To find the repositories that the team was granted access to, search for `action:team.add_repository team:"ORGANIZATION/TEAM"`. +1. To find the access level that the team was granted for each repository, search for `action:team.update_repository_permission team:"ORGANIZATION/TEAM"`. +1. Manually give the team access again. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)." diff --git a/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md index 60cc8f84c9..c8f5a68291 100644 --- a/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md @@ -1,5 +1,5 @@ --- -title: Configurar o Large File Storage do Git para a sua sempresa +title: Configuring Git Large File Storage for your enterprise intro: '{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %}' redirect_from: - /enterprise/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise @@ -23,93 +23,105 @@ topics: - LFS - Storage shortTitle: Configure Git LFS -ms.openlocfilehash: d6364bc1d45643ebb3dc1c46cec467515fd4da55 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145094580' --- -## Sobre o {% data variables.large_files.product_name_long %} +## About {% data variables.large_files.product_name_long %} -{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %} Você pode usar {% data variables.large_files.product_name_long %} com um único repositório, todos os seus repositórios pessoais ou organizacionais, ou com cada repositório na sua empresa. Antes de habilitar {% data variables.large_files.product_name_short %} para repositórios ou organizações específicos, você deve habilitar {% data variables.large_files.product_name_short %} para a sua empresa. +{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %} You can use {% data variables.large_files.product_name_long %} with a single repository, all of your personal or organization repositories, or with every repository in your enterprise. Before you can enable {% data variables.large_files.product_name_short %} for specific repositories or organizations, you need to enable {% data variables.large_files.product_name_short %} for your enterprise. -{% data reusables.large_files.storage_assets_location %} {% data reusables.large_files.rejected_pushes %} +{% data reusables.large_files.storage_assets_location %} +{% data reusables.large_files.rejected_pushes %} -Para obter mais informações, confira "[Sobre o {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)", "[Como fazer o controle de versão de arquivos grandes](/enterprise/user/articles/versioning-large-files/)" e o [site de projeto do {% data variables.large_files.product_name_long %}](https://git-lfs.github.com/). +For more information, see "[About {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)", "[Versioning large files](/enterprise/user/articles/versioning-large-files/)," and the [{% data variables.large_files.product_name_long %} project site](https://git-lfs.github.com/). {% data reusables.large_files.can-include-lfs-objects-archives %} -## Configurar {% data variables.large_files.product_name_long %} para a sua empresa +## Configuring {% data variables.large_files.product_name_long %} for your enterprise -{% data reusables.enterprise-accounts.access-enterprise %} {% ifversion ghes or ghae %} {% data reusables.enterprise-accounts.policies-tab %} {% else %} {% data reusables.enterprise-accounts.settings-tab %} {% endif %} {% data reusables.enterprise-accounts.options-tab %} -4. Em "Acesso ao {% data variables.large_files.product_name_short %}", use o menu suspenso e clique em **Habilitado** ou **Desabilitado**. -![Acesso ao Git LFS](/assets/images/enterprise/site-admin-settings/git-lfs-admin-center.png) +{% data reusables.enterprise-accounts.access-enterprise %} +{% ifversion ghes or ghae %} +{% data reusables.enterprise-accounts.policies-tab %} +{% else %} +{% data reusables.enterprise-accounts.settings-tab %} +{% endif %} +{% data reusables.enterprise-accounts.options-tab %} +4. Under "{% data variables.large_files.product_name_short %} access", use the drop-down menu, and click **Enabled** or **Disabled**. +![Git LFS Access](/assets/images/enterprise/site-admin-settings/git-lfs-admin-center.png) -## Configurar o {% data variables.large_files.product_name_long %} em um repositório específico +## Configuring {% data variables.large_files.product_name_long %} for an individual repository {% data reusables.enterprise_site_admin_settings.override-policy %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.repository-search %} {% data reusables.enterprise_site_admin_settings.click-repo %} {% data reusables.enterprise_site_admin_settings.admin-top-tab %} {% data reusables.enterprise_site_admin_settings.admin-tab %} {% data reusables.enterprise_site_admin_settings.git-lfs-toggle %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.repository-search %} +{% data reusables.enterprise_site_admin_settings.click-repo %} +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +{% data reusables.enterprise_site_admin_settings.git-lfs-toggle %} -## Configurar o {% data variables.large_files.product_name_long %} para cada repositório pertencente a uma conta ou organização +## Configuring {% data variables.large_files.product_name_long %} for every repository owned by a user account or organization -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.search-user-or-org %} {% data reusables.enterprise_site_admin_settings.click-user-or-org %} {% data reusables.enterprise_site_admin_settings.admin-top-tab %} {% data reusables.enterprise_site_admin_settings.admin-tab %} {% data reusables.enterprise_site_admin_settings.git-lfs-toggle %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.search-user-or-org %} +{% data reusables.enterprise_site_admin_settings.click-user-or-org %} +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +{% data reusables.enterprise_site_admin_settings.git-lfs-toggle %} {% ifversion ghes %} -## Configurar o Git Large File Storage para uso em servidores de terceiros +## Configuring Git Large File Storage to use a third party server -{% data reusables.large_files.storage_assets_location %} {% data reusables.large_files.rejected_pushes %} +{% data reusables.large_files.storage_assets_location %} +{% data reusables.large_files.rejected_pushes %} -1. Desabilite {% data variables.large_files.product_name_short %} em {% data variables.product.product_location %}. Para obter mais informações, confira "[Como configurar o {% data variables.large_files.product_name_long %} para sua empresa](#configuring-git-large-file-storage-for-your-enterprise)". +1. Disable {% data variables.large_files.product_name_short %} on {% data variables.location.product_location %}. For more information, see "[Configuring {% data variables.large_files.product_name_long %} for your enterprise](#configuring-git-large-file-storage-for-your-enterprise)." -2. Crie um arquivo de configuração do {% data variables.large_files.product_name_short %} que aponte para o servidor de terceiros. +2. Create a {% data variables.large_files.product_name_short %} configuration file that points to the third party server. ```shell # Show default configuration $ git lfs env > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c) > git version 2.7.4 (Apple Git-66)   - > Endpoint=https://GITHUB-ENTERPRISE-HOST/path/to/repo/info/lfs (auth=basic) + > Endpoint=https://GITHUB-ENTERPRISE-HOST/path/to/repo/info/lfs (auth=basic)   # Create .lfsconfig that points to third party server. - $ git config -f .lfsconfig remote.origin.lfsurl https://THIRD-PARTY-LFS-SERVER/path/to/repo + $ git config -f .lfsconfig remote.origin.lfsurl https://THIRD-PARTY-LFS-SERVER/path/to/repo $ git lfs env > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c) > git version 2.7.4 (Apple Git-66)   - > Endpoint=https://THIRD-PARTY-LFS-SERVER/path/to/repo/info/lfs (auth=none) + > Endpoint=https://THIRD-PARTY-LFS-SERVER/path/to/repo/info/lfs (auth=none)   # Show the contents of .lfsconfig $ cat .lfsconfig [remote "origin"] - lfsurl = https://THIRD-PARTY-LFS-SERVER/path/to/repo + lfsurl = https://THIRD-PARTY-LFS-SERVER/path/to/repo ``` -3. Para manter a mesma configuração do {% data variables.large_files.product_name_short %} para todos os usuários, faça commit de um arquivo `.lfsconfig` personalizado no repositório. +3. To keep the same {% data variables.large_files.product_name_short %} configuration for each user, commit a custom `.lfsconfig` file to the repository. ```shell $ git add .lfsconfig $ git commit -m "Adding LFS config file" ``` -3. Migre qualquer ativo do {% data variables.large_files.product_name_short %}. Para obter mais informações, confira "[Como migrar para outro servidor do {% data variables.large_files.product_name_long %}](#migrating-to-a-different-git-large-file-storage-server)". +3. Migrate any existing {% data variables.large_files.product_name_short %} assets. For more information, see "[Migrating to a different {% data variables.large_files.product_name_long %} server](#migrating-to-a-different-git-large-file-storage-server)." -## Migrar para outro servidor do Git Large File Storage +## Migrating to a different Git Large File Storage server -Antes de migrar para outro servidor do {% data variables.large_files.product_name_long %}, configure o {% data variables.large_files.product_name_short %} para usar um servidor de terceiros. Para obter mais informações, confira "[Como configurar o {% data variables.large_files.product_name_long %} para usar um servidor de terceiros](#configuring-git-large-file-storage-to-use-a-third-party-server)". +Before migrating to a different {% data variables.large_files.product_name_long %} server, you must configure {% data variables.large_files.product_name_short %} to use a third party server. For more information, see "[Configuring {% data variables.large_files.product_name_long %} to use a third party server](#configuring-git-large-file-storage-to-use-a-third-party-server)." -1. Configure o repositório com outro remote. +1. Configure the repository with a second remote. ```shell - $ git remote add NEW-REMOTE https://NEW-REMOTE-HOSTNAME/path/to/repo + $ git remote add NEW-REMOTE https://NEW-REMOTE-HOSTNAME/path/to/repo   $ git lfs env > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c) > git version 2.7.4 (Apple Git-66)   - > Endpoint=https://GITHUB-ENTERPRISE-HOST/path/to/repo/info/lfs (auth=basic) - > Endpoint (NEW-REMOTE)=https://NEW-REMOTE-HOSTNAME/path/to/repo/info/lfs (auth=none) + > Endpoint=https://GITHUB-ENTERPRISE-HOST/path/to/repo/info/lfs (auth=basic) + > Endpoint (NEW-REMOTE)=https://NEW-REMOTE-HOSTNAME/path/to/repo/info/lfs (auth=none) ``` -2. Faça fetch de todos os objetos do remote antigo. +2. Fetch all objects from the old remote. ```shell $ git lfs fetch origin --all > Scanning for all objects ever referenced... @@ -118,9 +130,9 @@ Antes de migrar para outro servidor do {% data variables.large_files.product_nam > Git LFS: (16 of 16 files) 48.71 MB / 48.85 MB ``` -3. Faça push de todos os objetos para o remote novo. +3. Push all objects to the new remote. ```shell - $ git lfs push NEW-REMOTE --all + $ git lfs push NEW-REMOTE --all > Scanning for all objects ever referenced... > ✔ 16 objects found > Pushing objects... @@ -128,6 +140,6 @@ Antes de migrar para outro servidor do {% data variables.large_files.product_nam ``` {% endif %} -## Leitura adicional +## Further reading -- [Site de projeto do {% data variables.large_files.product_name_long %}](https://git-lfs.github.com/) +- [{% data variables.large_files.product_name_long %} project site](https://git-lfs.github.com/) diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md index b574daf7bd..08a8461a70 100644 --- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md @@ -1,12 +1,12 @@ --- -title: Personalizar mensagens de usuário para sua empresa +title: Customizing user messages for your enterprise shortTitle: Customizing user messages redirect_from: - /enterprise/admin/user-management/creating-a-custom-sign-in-message - /enterprise/admin/user-management/customizing-user-messages-on-your-instance - /admin/user-management/customizing-user-messages-on-your-instance - /admin/user-management/customizing-user-messages-for-your-enterprise -intro: 'Você pode criar mensagens personalizadas que os usuários verão em {% data variables.product.product_location %}.' +intro: 'You can create custom messages that users will see on {% data variables.location.product_location %}.' versions: ghes: '*' ghae: '*' @@ -14,96 +14,112 @@ type: how_to topics: - Enterprise - Maintenance -ms.openlocfilehash: 08cd547cd79b1e731f439688f02b475db8db4d1d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147052053' --- -## Sobre mensagens de usuário +## About user messages -Existem vários tipos de mensagens de usuário. -- Mensagens exibidas na página {% ifversion ghes %}de entrada ou {% endif %}de saída{% ifversion ghes or ghae %} -- Mensagens obrigatórias, que aparecem uma vez em uma janela pop-up que deve ser ignorada{% endif %}{% ifversion ghes or ghae %} -- Banners de anúncios, que aparecem na parte superior de cada página{% endif %} +There are several types of user messages. +- Messages that appear on the {% ifversion ghes %}sign in or {% endif %}sign out page{% ifversion ghes or ghae %} +- Mandatory messages, which appear once in a pop-up window that must be dismissed{% endif %}{% ifversion ghes or ghae %} +- Announcement banners, which appear at the top of every page{% endif %} -{% ifversion ghes %} {% note %} +{% ifversion ghes %} +{% note %} -**Observação:** se você estiver usando o SAML para autenticação, a página de entrada será apresentada pelo provedor de identidade e não poderá ser personalizada por meio do {% data variables.product.prodname_ghe_server %}. +**Note:** If you are using SAML for authentication, the sign in page is presented by your identity provider and is not customizable via {% data variables.product.prodname_ghe_server %}. {% endnote %} -Você pode usar markdown para formatar sua mensagem. Para obter mais informações, confira "[Sobre a gravação e a formatação no {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/)". +You can use Markdown to format your message. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/)." -## Criar mensagem personalizada de login +## Creating a custom sign in message -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. {% ifversion ghes %}À direita de{% else %}Em{% endif %} "Página de entrada", clique em **Adicionar mensagem** ou **Editar mensagem**. -![{% ifversion ghes %}Botão Adicionar{% else %}Editar{% endif %} mensagem](/assets/images/enterprise/site-admin-settings/edit-message.png) -6. Em **Mensagem de entrada**, digite a mensagem que deseja mostrar aos usuários. -![Mensagem de entrada](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% ifversion ghes %} {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![Botão Visualizar](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png) -8. Revise a mensagem renderizada. -![Mensagem de entrada renderizada](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png) {% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %}{% endif %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +5. {% ifversion ghes %}To the right of{% else %}Under{% endif %} "Sign in page", click **Add message** or **Edit message**. +![{% ifversion ghes %}Add{% else %}Edit{% endif %} message button](/assets/images/enterprise/site-admin-settings/edit-message.png) +6. Under **Sign in message**, type the message you'd like users to see. +![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% ifversion ghes %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} +{% data reusables.enterprise_site_admin_settings.click-preview %} + ![Preview button](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png) +8. Review the rendered message. +![Sign in message rendered](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png) +{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} +{% endif %} -## Criar mensagem personalizada de logout +## Creating a custom sign out message -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. {% ifversion ghes or ghae %} À direita de{% else %}Em{% endif %} "Página de Saída", clique em **Adicionar mensagem** ou **Editar mensagem**. -![Botão Adicionar mensagem](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) -6. Em **Mensagem de saída**, digite a mensagem que você deseja mostrar aos usuários. -![Assinar a mensagem two_factor_auth_header](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% ifversion ghes or ghae %} {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![Botão Visualizar](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png) -8. Revise a mensagem renderizada. -![Mensagem de saída renderizada](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png) {% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +5. {% ifversion ghes or ghae %}To the right of{% else %}Under{% endif %} "Sign out page", click **Add message** or **Edit message**. +![Add message button](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) +6. Under **Sign out message**, type the message you'd like users to see. +![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% ifversion ghes or ghae %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} +{% data reusables.enterprise_site_admin_settings.click-preview %} + ![Preview button](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png) +8. Review the rendered message. +![Sign out message rendered](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png) +{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} {% ifversion ghes or ghae %} -## Criar uma mensagem obrigatória +## Creating a mandatory message -Você pode criar uma mensagem obrigatória que {% data variables.product.product_name %} mostrará a todos os usuários na primeira vez que efetuarem o login depois de salvar a mensagem. A mensagem aparece em uma janela pop-up que o usuário deve ignorar antes que o usuário possa usar o {% data variables.product.product_location %}. +You can create a mandatory message that {% data variables.product.product_name %} will show to all users the first time they sign in after you save the message. The message appears in a pop-up window that the user must dismiss before the user can use {% data variables.location.product_location %}. -As mensagens obrigatórias têm uma série de usos. +Mandatory messages have a variety of uses. -- Fornecer informações de integração para novos funcionários -- Contar para os usuários como obter ajuda com {% data variables.product.product_location %} -- Garantir que todos os usuários leiam seus termos de serviço para usar {% data variables.product.product_location %} +- Providing onboarding information for new employees +- Telling users how to get help with {% data variables.location.product_location %} +- Ensuring that all users read your terms of service for using {% data variables.location.product_location %} -Se você incluir caixas de seleção de Markdown na mensagem, todas as caixas de seleção deverão ser selecionadas antes de o usuário poder ignorar a mensagem. Por exemplo, se você incluir seus termos de serviço na mensagem obrigatória, você poderá exigir que cada usuário marque uma caixa de seleção para confirmar que o usuário leu os termos. +If you include Markdown checkboxes in the message, all checkboxes must be selected before the user can dismiss the message. For example, if you include your terms of service in the mandatory message, you can require that each user selects a checkbox to confirm the user has read the terms. -Cada vez que um usuário vê uma mensagem obrigatória, um evento de log de auditoria é criado. O evento inclui a versão da mensagem que o usuário visualizou. Para obter mais informações, confira "[Eventos de log de auditoria para sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)". +Each time a user sees a mandatory message, an audit log event is created. The event includes the version of the message that the user saw. For more information see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)." {% note %} -**Observação:** se você alterar a mensagem obrigatória do {% data variables.product.product_location %}, os usuários que já reconheceram a mensagem não verão a nova mensagem. +**Note:** If you change the mandatory message for {% data variables.location.product_location %}, users who have already acknowledged the message will not see the new message. {% endnote %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -1. À direita de "Mensagem obrigatória", clique em **Adicionar mensagem**. - ![Botão Adicionar mensagem obrigatória](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) -1. Em "Mensagem obrigatória", na caixa de texto, digite sua mensagem. - ![Caixa de texto Mensagem obrigatória](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) {% data reusables.enterprise_site_admin_settings.message-preview-save %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +1. To the right of "Mandatory message", click **Add message**. + ![Add mandatory message button](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) +1. Under "Mandatory message", in the text box, type your message. + ![Mandatory message text box](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) +{% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %} {% ifversion ghes or ghae %} -## Criar um banner de anúncio global +## Creating a global announcement banner -Você pode definir um banner de anúncio global para ser exibido para todos os usuários na parte superior de cada página. +You can set a global announcement banner to be displayed to all users at the top of every page. -{% ifversion ghae or ghes %} Você também pode definir uma faixa de comunicado{% ifversion ghes %} no shell administrativo usando um utilitário de linha de comando ou{% endif %} usando a API. Para obter mais informações, confira {% ifversion ghes %}"[Utilitários de linha de comando](/enterprise/admin/configuration/command-line-utilities#ghe-announce)" e {% endif %}"[Administração do {% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#announcements)". +{% ifversion ghae or ghes %} +You can also set an announcement banner{% ifversion ghes %} in the administrative shell using a command line utility or{% endif %} using the API. For more information, see {% ifversion ghes %}"[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)" and {% endif %}"[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)." {% else %} -Você também pode definir um banner de anúncio no shell administrativo usando um utilitário de linha de comando. Para obter mais informações, confira "[Utilitários de linha de comando](/enterprise/admin/configuration/command-line-utilities#ghe-announce)". +You can also set an announcement banner in the administrative shell using a command line utility. For more information, see "[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)." {% endif %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -1. {% ifversion ghes or ghae %} À direita de{% else %}Em {% endif %} "Comunicado", clique em **Adicionar comunicado**. - ![Botão Adicionar comunicado](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) -1. Em "Anúncio", no campo de texto, digite o anúncio que deseja exibir em um banner. - ![Campo de texto usado para inserir o comunicado](/assets/images/enterprise/site-admin-settings/announcement-text-field.png) -1. Opcionalmente, em "Expira em", selecione o menu suspenso do calendário e clique em uma data de validade. - ![Menu suspenso de calendário para escolher a data de validade](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png){% ifversion ghe-announce-dismiss %} -1. Opcionalmente, para permitir que cada usuário ignore o comunicado, selecione **Usuário que pode ignorar**. +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +1. {% ifversion ghes or ghae %}To the right of{% else %}Under{% endif %} "Announcement", click **Add announcement**. + ![Add announcement button](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) +1. Under "Announcement", in the text field, type the announcement you want displayed in a banner. + ![Text field to enter announcement](/assets/images/enterprise/site-admin-settings/announcement-text-field.png) +1. Optionally, under "Expires on", select the calendar drop-down menu and click an expiration date. + ![Calendar drop-down menu to choose expiration date](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png){% ifversion ghe-announce-dismiss %} +1. Optionally, to allow each user to dismiss the announcement, select **User dismissible**. - ![Captura de tela da caixa de seleção "Usuário que pode ignorar"](/assets/images/enterprise/site-admin-settings/user-dismissible-checkbox.png){% endif %} {% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %} + ![Screenshot of the "User dismissible" checkbox](/assets/images/enterprise/site-admin-settings/user-dismissible-checkbox.png){% endif %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %} +{% endif %} diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md index d907e577ff..46f9801fb1 100644 --- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md +++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md @@ -1,5 +1,5 @@ --- -title: Suspender e cancelar a suspensão de usuários +title: Suspending and unsuspending users redirect_from: - /enterprise/admin/articles/suspending-a-user - /enterprise/admin/articles/unsuspending-a-user @@ -8,7 +8,7 @@ redirect_from: - /enterprise/admin/articles/suspending-and-unsuspending-users - /enterprise/admin/user-management/suspending-and-unsuspending-users - /admin/user-management/suspending-and-unsuspending-users -intro: 'Se um usuário sair da empresa ou mudar para outro departamento, você deverá remover ou modificar a forma como ele acessa a {% data variables.product.product_location %}.' +intro: 'If a user leaves or moves to a different part of the company, you should remove or modify their ability to access {% data variables.location.product_location %}.' versions: ghes: '*' type: how_to @@ -18,16 +18,10 @@ topics: - Security - User account shortTitle: Manage user suspension -ms.openlocfilehash: d888678438f62fb585dac1cab4905ff02d8eb824 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146331901' --- -Se funcionários saírem da empresa, você poderá suspender suas contas do {% data variables.product.prodname_ghe_server %} para disponibilizar licenças de usuário em sua licença {% data variables.product.prodname_enterprise %}, embora os problemas, comentários, repositórios, gists e outros dados que eles criaram continuem existindo. Usuários suspensos não podem entrar na sua instância nem fazer push ou pull de códigos. +If employees leave the company, you can suspend their {% data variables.product.prodname_ghe_server %} accounts to open up user licenses in your {% data variables.product.prodname_enterprise %} license while preserving the issues, comments, repositories, gists, and other data they created. Suspended users cannot sign into your instance, nor can they push or pull code. -Quando você suspende um usuário, a alteração entra em vigor na mesma hora e o usuário não recebe notificações a respeito. Se tentar fazer pull ou push em um repositório, o usuário receberá este erro: +When you suspend a user, the change takes effect immediately with no notification to the user. If the user attempts to pull or push to a repository, they'll receive this error: ```shell $ git clone git@[hostname]:john-doe/test-repo.git @@ -36,65 +30,74 @@ ERROR: Your account is suspended. Please check with your installation administra fatal: The remote end hung up unexpectedly ``` -Antes de suspender os administradores do site, você deve rebaixá-los para usuários regulares. Para obter mais informações, confira "[Como promover ou rebaixar um administrador do site](/enterprise/admin/user-management/promoting-or-demoting-a-site-administrator)". +Before suspending site administrators, you must demote them to regular users. For more information, see "[Promoting or demoting a site administrator](/enterprise/admin/user-management/promoting-or-demoting-a-site-administrator)." {% tip %} -**Observação:** se a [Sincronização LDAP estiver habilitada](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync) para o {% data variables.product.product_location %}, os usuários serão suspensos automaticamente quando forem removidos do servidor de diretório LDAP. Quando a Sincronização LDAP estiver habilitada para a sua instância, os métodos normais de suspensão do usuário ficarão desabilitados. +**Note:** If [LDAP Sync is enabled](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync) for {% data variables.location.product_location %}, users are automatically suspended when they're removed from the LDAP directory server. When LDAP Sync is enabled for your instance, normal user suspension methods are disabled. {% endtip %} -## Suspender usuários pelo painel de administração de usuários - -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.search-user %} {% data reusables.enterprise_site_admin_settings.click-user %} {% data reusables.enterprise_site_admin_settings.admin-top-tab %} {% data reusables.enterprise_site_admin_settings.admin-tab %} -5. Em "Suspensão da conta", na caixa vermelha Zona de Perigo, clique em **Suspender**. -![Botão Suspender](/assets/images/enterprise/site-admin-settings/suspend.png) -6. Informe um motivo para a suspensão do usuário. -![Motivo da suspensão](/assets/images/enterprise/site-admin-settings/suspend-reason.png) - -## Cancelar a suspensão de usuários pelo painel de administração de usuários - -Assim como na suspensão, o cancelamento da suspensão de um usuário ocorre na mesma hora. O usuário não receberá notificações. +## Suspending a user from the user admin dashboard {% data reusables.enterprise_site_admin_settings.access-settings %} -3. Na barra lateral esquerda, clique em **Usuários suspensos**. -![Guia Usuários suspensos](/assets/images/enterprise/site-admin-settings/user/suspended-users-tab.png) -2. Clique no nome da conta de usuário que você deseja suspender. -![Usuário suspenso](/assets/images/enterprise/site-admin-settings/user/suspended-user.png) {% data reusables.enterprise_site_admin_settings.admin-top-tab %} {% data reusables.enterprise_site_admin_settings.admin-tab %} -4. Em "Suspensão da conta", na caixa vermelha Zona de Perigo, clique em **Cancelar suspensão**. -![Botão Cancelar suspensão](/assets/images/enterprise/site-admin-settings/unsuspend.png) -5. Informe um motivo para o cancelamento da suspensão do usuário. -![Motivo do cancelamento da suspensão](/assets/images/enterprise/site-admin-settings/unsuspend-reason.png) +{% data reusables.enterprise_site_admin_settings.search-user %} +{% data reusables.enterprise_site_admin_settings.click-user %} +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +5. Under "Account suspension," in the red Danger Zone box, click **Suspend**. +![Suspend button](/assets/images/enterprise/site-admin-settings/suspend.png) +6. Provide a reason to suspend the user. +![Suspend reason](/assets/images/enterprise/site-admin-settings/suspend-reason.png) -## Suspender usuários pela linha de comando +## Unsuspending a user from the user admin dashboard + +As when suspending a user, unsuspending a user takes effect immediately. The user will not be notified. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +3. In the left sidebar, click **Suspended users**. +![Suspended users tab](/assets/images/enterprise/site-admin-settings/user/suspended-users-tab.png) +2. Click the name of the user account that you would like to unsuspend. +![Suspended user](/assets/images/enterprise/site-admin-settings/user/suspended-user.png) +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +4. Under "Account suspension," in the red Danger Zone box, click **Unsuspend**. +![Unsuspend button](/assets/images/enterprise/site-admin-settings/unsuspend.png) +5. Provide a reason to unsuspend the user. +![Unsuspend reason](/assets/images/enterprise/site-admin-settings/unsuspend-reason.png) + +## Suspending a user from the command line {% data reusables.enterprise_installation.ssh-into-instance %} -2. Execute [ghe-user-suspend](/enterprise/admin/guides/installation/command-line-utilities#ghe-user-suspend) com o nome de usuário a ser suspenso. +2. Run [ghe-user-suspend](/enterprise/admin/guides/installation/command-line-utilities#ghe-user-suspend) with the username to suspend. ```shell - $ ghe-user-suspend username + $ ghe-user-suspend USERNAME ``` -## Criar mensagem personalizada para usuários suspensos +## Creating a custom message for suspended users -É possível criar uma mensagem personalizada que os usuários suspensos verão ao tentar fazer login. +You can create a custom message that suspended users will see when attempting to sign in. -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. Clique em **Adicionar mensagem**. -![Adicionar mensagem](/assets/images/enterprise/site-admin-settings/add-message.png) -6. Digite sua mensagem na caixa de **Mensagem para o usuário suspenso**. Você pode digitar Markdown ou usar a barra de ferramentas Markdown para estilizar a mensagem. -![Mensagem para o usuário suspenso](/assets/images/enterprise/site-admin-settings/suspended-user-message.png) -7. Clique no botão **Visualizar** no campo **Mensagem para o usuário suspenso** para ver a mensagem renderizada. -![botão Visualizar](/assets/images/enterprise/site-admin-settings/suspended-user-message-preview-button.png) -8. Revise a mensagem renderizada. -![Mensagem para o usuário suspenso renderizada](/assets/images/enterprise/site-admin-settings/suspended-user-message-rendered.png) {% data reusables.enterprise_site_admin_settings.save-changes %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +5. Click **Add message**. +![Add message](/assets/images/enterprise/site-admin-settings/add-message.png) +6. Type your message into the **Suspended user message** box. You can type Markdown, or use the Markdown toolbar to style your message. +![Suspended user message](/assets/images/enterprise/site-admin-settings/suspended-user-message.png) +7. Click the **Preview** button under the **Suspended user message** field to see the rendered message. +![Preview button](/assets/images/enterprise/site-admin-settings/suspended-user-message-preview-button.png) +8. Review the rendered message. +![Suspended user message rendered](/assets/images/enterprise/site-admin-settings/suspended-user-message-rendered.png) +{% data reusables.enterprise_site_admin_settings.save-changes %} -## Cancelar a suspensão de usuários pela linha de comando +## Unsuspending a user from the command line {% data reusables.enterprise_installation.ssh-into-instance %} -2. Execute [ghe-user-unsuspend](/enterprise/admin/guides/installation/command-line-utilities#ghe-user-unsuspend) com o nome de usuário para cancelar a suspensão dele. +2. Run [ghe-user-unsuspend](/enterprise/admin/guides/installation/command-line-utilities#ghe-user-unsuspend) with the username to unsuspend. ```shell - $ ghe-user-unsuspend username + $ ghe-user-unsuspend USERNAME ``` -## Leitura adicional -- "[Suspender um usuário](/rest/reference/enterprise-admin#suspend-a-user)" +## Further reading +- "[Suspend a user](/rest/reference/enterprise-admin#suspend-a-user)" diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md index 860261add4..39a210fec7 100644 --- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Visualizar e gerenciar o acesso SAML de um usuário à sua empresa -intro: 'Você pode visualizar e revogar a identidade vinculada de um integrante da empresa, as sessões ativas e as credenciais autorizadas.' +title: Viewing and managing a user's SAML access to your enterprise +intro: 'You can view and revoke an enterprise member''s linked identity, active sessions, and authorized credentials.' permissions: Enterprise owners can view and manage a member's SAML access to an organization. redirect_from: - /github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account @@ -12,39 +12,50 @@ versions: topics: - Enterprise shortTitle: View & manage SAML access -ms.openlocfilehash: 25c706f5aff79f65adf4968546a9a8123794f583 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145094851' --- -## Sobre o acesso de SAML à sua conta corporativa +## About SAML access to your enterprise account -Ao habilitar o logon único do SAML para a conta corporativa, cada integrante da empresa poderá vincular sua identidade externa ao seu provedor de identidade (IdP) à sua conta existente em {% data variables.product.product_location %}. {% data reusables.saml.about-saml-access-enterprise-account %} +When you enable SAML single sign-on for your enterprise account, each enterprise member can link their external identity on your identity provider (IdP) to their existing account on {% data variables.location.product_location %}. {% data reusables.saml.about-saml-access-enterprise-account %} -Se sua empresa usar {% data variables.product.prodname_emus %}, seus integrantes usarão contas fornecidas por meio de seu IdP. {% data variables.product.prodname_managed_users_caps %} não usará a sua conta de usuário existente em {% data variables.product.product_name %}. Para obter mais informações, confira "[Sobre as {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)". +If your enterprise is uses {% data variables.product.prodname_emus %}, your members will use accounts provisioned through your IdP. {% data variables.enterprise.prodname_managed_users_caps %} will not use their existing user account on {% data variables.product.product_name %}. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." -## Visualizar e revogar uma identidade vinculada +## Viewing and revoking a linked identity {% data reusables.saml.about-linked-identities %} -Se o a sua empresa usar {% data variables.product.prodname_emus %}, você não poderá cancelar o provisionamento ou remover contas de usuário da empresa em {% data variables.product.product_name %}. Todas as alterações necessárias a fazer no {% data variables.product.prodname_managed_users %} da sua empresa devem ser feitas por meio do seu IdP. +If your enterprise uses {% data variables.product.prodname_emus %}, you will not be able to deprovision or remove user accounts from the enterprise on {% data variables.product.product_name %}. Any changes you need to make to your enterprise's {% data variables.enterprise.prodname_managed_users %} should be made through your IdP. {% data reusables.identity-and-permissions.revoking-identity-team-sync %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} {% data reusables.saml.click-person-revoke-identity %} {% data reusables.saml.saml-identity-linked %} {% data reusables.saml.view-sso-identity %} {% data reusables.saml.revoke-sso-identity %} {% data reusables.saml.confirm-revoke-identity %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.people-tab %} +{% data reusables.saml.click-person-revoke-identity %} +{% data reusables.saml.saml-identity-linked %} +{% data reusables.saml.view-sso-identity %} +{% data reusables.saml.revoke-sso-identity %} +{% data reusables.saml.confirm-revoke-identity %} -## Visualizar e revogar uma sessão ativa de SAML +## Viewing and revoking an active SAML session -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} {% data reusables.saml.click-person-revoke-session %} {% data reusables.saml.saml-identity-linked %} {% data reusables.saml.view-saml-sessions %} {% data reusables.saml.revoke-saml-session %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.people-tab %} +{% data reusables.saml.click-person-revoke-session %} +{% data reusables.saml.saml-identity-linked %} +{% data reusables.saml.view-saml-sessions %} +{% data reusables.saml.revoke-saml-session %} -## Visualizar e revogar credenciais autorizadas +## Viewing and revoking authorized credentials {% data reusables.saml.about-authorized-credentials %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} {% data reusables.saml.click-person-revoke-credentials %} {% data reusables.saml.saml-identity-linked %} {% data reusables.saml.view-authorized-credentials %} {% data reusables.saml.revoke-authorized-credentials %} {% data reusables.saml.confirm-revoke-credentials %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.people-tab %} +{% data reusables.saml.click-person-revoke-credentials %} +{% data reusables.saml.saml-identity-linked %} +{% data reusables.saml.view-authorized-credentials %} +{% data reusables.saml.revoke-authorized-credentials %} +{% data reusables.saml.confirm-revoke-credentials %} -## Leitura adicional +## Further reading -- "[Como ver e gerenciar o acesso do SAML de um membro à sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" +- "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md index 0514107389..0596124afa 100644 --- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md @@ -114,7 +114,7 @@ If you use {% data variables.product.prodname_vss_ghe %}, the list of pending in ![Screenshot of the "Members", "Administrators", and "Outside collaborators" tabs](/assets/images/help/enterprises/pending-invitations-type-tabs.png) -## Viewing suspended members in an {% data variables.product.prodname_emu_enterprise %} +## Viewing suspended members in an {% data variables.enterprise.prodname_emu_enterprise %} If your enterprise uses {% data variables.product.prodname_emus %}, you can also view suspended users. Suspended users are members who have been deprovisioned after being unassigned from the {% data variables.product.prodname_emu_idp_application %} application or deleted from the identity provider. For more information, see "[About Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users)." diff --git a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md index 5990e1b1ee..f0f6adac03 100644 --- a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md +++ b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md @@ -1,6 +1,6 @@ --- -title: Sobre migrações -intro: 'Migração é o processo de transferência de dados de um local de *origem* (organização do {% data variables.product.prodname_dotcom_the_website %} ou uma instância do {% data variables.product.prodname_ghe_server %}) para uma instância de *destino* do {% data variables.product.prodname_ghe_server %}. É possível usar as migrações para transferir os dados ao alterar plataformas ou atualizar o hardware na sua instância.' +title: About migrations +intro: 'A migration is the process of transferring data from a *source* location (either a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance. Migrations can be used to transfer your data when changing platforms or upgrading hardware on your instance.' redirect_from: - /enterprise/admin/migrations/about-migrations - /enterprise/admin/user-management/about-migrations @@ -11,47 +11,41 @@ type: overview topics: - Enterprise - Migration -ms.openlocfilehash: accb9c62655f8825077a00e05a93182b36cd6e8d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147541180' --- -## Tipos de migrações +## Types of migrations -Você pode fazer três tipos de migração: +There are three types of migrations you can perform: -- Migração de uma instância do {% data variables.product.prodname_ghe_server %} para outra do {% data variables.product.prodname_ghe_server %}: você pode migrar qualquer número de repositórios pertencentes a qualquer usuário ou organização na instância. Para executar a migração, você deve ter acesso de administrador do site a ambas as instâncias. -- Migração de uma organização do {% data variables.product.prodname_dotcom_the_website %} para uma instância do {% data variables.product.prodname_ghe_server %}: você pode migrar qualquer número de repositórios pertencentes à organização. Antes de executar uma migração, você precisa ter [acesso administrativo](/enterprise/user/articles/permission-levels-for-an-organization/) na organização do {% data variables.product.prodname_dotcom_the_website %} e acesso de administrador do site na instância de destino. -- As *execuções de avaliação* são migrações que importam dados para uma [instância de preparo](/enterprise/admin/guides/installation/setting-up-a-staging-instance/). Elas podem ser úteis para ver o que *aconteceria* se uma migração fosse aplicada ao {% data variables.product.product_location %}. **Recomendamos fortemente que você execute uma execução de avaliação em uma instância de preparo antes de importar dados para sua instância de produção.** +- A migration from a {% data variables.product.prodname_ghe_server %} instance to another {% data variables.product.prodname_ghe_server %} instance. You can migrate any number of repositories owned by any user or organization on the instance. Before performing a migration, you must have site administrator access to both instances. +- A migration from a {% data variables.product.prodname_dotcom_the_website %} organization to a {% data variables.product.prodname_ghe_server %} instance. You can migrate any number of repositories owned by the organization. Before performing a migration, you must have [administrative access](/enterprise/user/articles/permission-levels-for-an-organization/) to the {% data variables.product.prodname_dotcom_the_website %} organization as well as site administrator access to the target instance. +- *Trial runs* are migrations that import data to a [staging instance](/enterprise/admin/guides/installation/setting-up-a-staging-instance/). These can be useful to see what *would* happen if a migration were applied to {% data variables.location.product_location %}. **We strongly recommend that you perform a trial run on a staging instance before importing data to your production instance.** -## Dados migrados +## Migrated data -Durante uma migração, tudo gira em torno do repositório. A maioria dos dados associados ao repositório pode ser migrada. Por exemplo, um repositório em uma organização migrará o repositório *e* a organização, bem como todos os usuários, as equipes, os problemas e as solicitações de pull associadas ao repositório. +In a migration, everything revolves around a repository. Most data associated with a repository can be migrated. For example, a repository within an organization will migrate the repository *and* the organization, as well as any users, teams, issues, and pull requests associated with the repository. -Os itens na tabela abaixo podem ser migrados com um repositório. Os itens não mostrados na lista de dados migrados não podem ser migrados, incluindo os ativos do {% data variables.large_files.product_name_short %}. +The items in the table below can be migrated with a repository. Any items not shown in the list of migrated data can not be migrated, including {% data variables.large_files.product_name_short %} assets. {% data reusables.enterprise_migrations.fork-persistence %} -| Dados associados a um repositório migrado | Observações | +| Data associated with a migrated repository | Notes | |---------------------------------------------|--------| -| Usuários | As **@mentions** aos usuários são rescritas para corresponderem ao destino. -| Organizações | Os nomes e detalhes das organizações são migrados. -| Repositórios | Links para árvores, blobs, commits e linhas do Git são rescritas para corresponder ao destino. O migrador segue no máximo três redirecionamentos de repositório. Repositórios internos são migrados como repositórios privados. O status de arquivo morto não está definido. -| Wikis | Todos os dados da wiki são migrados. -| Teams | As **@mentions** às equipes são rescritas para corresponderem ao destino. -| Marcos | Os registros de data e hora são preservados. -| Quadros de projeto | Os quadros de projeto associados ao repositório e à organização proprietária do repositório são migrados. -| Problemas | As referências a problemas e os registros de data e hora são preservados. -| Comentários dos problemas | As referências cruzadas aos comentários são rescritas para a instância de destino. -| Solicitações de pull | As referências cruzadas a pull requests são rescritas para corresponder ao destino. Os registros de data e hora são preservados. -| Revisões de pull request | As revisões de pull request e os dados associados são migrados. -| Comentários das revisões de pull request | As referências cruzadas aos comentários são rescritas para a instância de destino. Os registros de data e hora são preservados. -| Comentários de commit | As referências cruzadas aos comentários são rescritas para a instância de destino. Os registros de data e hora são preservados. -| Versões | Todos os dados das versões são migrados. -| Ações feitas em problemas ou em pull requests | São preservadas todas as modificações em problemas ou pull requests, como atribuir usuários, renomear títulos e modificar etiquetas, bem como os registros de data e hora de cada ação. -| Anexos de arquivo | Os [anexos de arquivo em problemas e solicitações de pull](/articles/file-attachments-on-issues-and-pull-requests) são migrados. Você pode desabilitar essa opção como parte da migração. -| Webhooks | Somente os webhooks ativos são migrados. -| Chaves de implantação de repositório | As chaves de implantação de repositório são migradas. -| Branches protegidos | As configurações de branches protegidos e os dados associados são migrados. +| Users | **@mentions** of users are rewritten to match the target. +| Organizations | An organization's name and details are migrated. +| Repositories | Links to Git trees, blobs, commits, and lines are rewritten to match the target. The migrator follows a maximum of three repository redirects. Internal repositories are migrated as private repositories. Archive status is unset. +| Wikis | All wiki data is migrated. +| Teams | **@mentions** of teams are rewritten to match the target. +| Milestones | Timestamps are preserved. +| Project boards | Project boards associated with the repository and with the organization that owns the repository are migrated. +| Issues | Issue references and timestamps are preserved. +| Issue comments | Cross-references to comments are rewritten for the target instance. +| Pull requests | Cross-references to pull requests are rewritten to match the target. Timestamps are preserved. +| Pull request reviews | Pull request reviews and associated data are migrated. +| Pull request review comments | Cross-references to comments are rewritten for the target instance. Timestamps are preserved. +| Commit comments | Cross-references to comments are rewritten for the target instance. Timestamps are preserved. +| Releases | All releases data is migrated. +| Actions taken on pull requests or issues | All modifications to pull requests or issues, such as assigning users, renaming titles, and modifying labels are preserved, along with timestamps for each action. +| File attachments | [File attachments on issues and pull requests](/articles/file-attachments-on-issues-and-pull-requests) are migrated. You can choose to disable this as part of the migration. +| Webhooks | Only active webhooks are migrated. +| Repository deploy keys | Repository deploy keys are migrated. +| Protected branches | Protected branch settings and associated data are migrated. diff --git a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md index 812f647e44..857f19fd91 100644 --- a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Exportar dados de migração da sua empresa -intro: 'Para alterar as plataformas ou mover de uma instância de teste para uma instância de produção você pode exportar os dados de migração de uma instância do {% data variables.product.prodname_ghe_server %} preparando a instância, bloqueando os repositórios e gerando um arquivo de migração.' +title: Exporting migration data from your enterprise +intro: 'To change platforms or move from a trial instance to a production instance, you can export migration data from a {% data variables.product.prodname_ghe_server %} instance by preparing the instance, locking the repositories, and generating a migration archive.' redirect_from: - /enterprise/admin/guides/migrations/exporting-migration-data-from-github-enterprise - /enterprise/admin/migrations/exporting-migration-data-from-github-enterprise-server @@ -18,49 +18,43 @@ topics: - Enterprise - Migration shortTitle: Export from your enterprise -ms.openlocfilehash: 5bff2e21a493cc35448d68daf87aa87ed82a8a28 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145094849' --- -## Preparar a instância de origem de {% data variables.product.prodname_ghe_server %} +## Preparing the {% data variables.product.prodname_ghe_server %} source instance -1. Verifique se você é administrador do site na origem do {% data variables.product.prodname_ghe_server %}. A melhor maneira de fazer isso é verificar se você pode [entrar na instância com o SSH](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/). +1. Verify that you are a site administrator on the {% data variables.product.prodname_ghe_server %} source. The best way to do this is to verify that you can [SSH into the instance](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/). -2. {% data reusables.enterprise_migrations.token-generation %} na instância de origem do {% data variables.product.prodname_ghe_server %}. +2. {% data reusables.enterprise_migrations.token-generation %} on the {% data variables.product.prodname_ghe_server %} source instance. {% data reusables.enterprise_migrations.make-a-list %} -## Exportar os repositórios de origem de {% data variables.product.prodname_ghe_server %} +## Exporting the {% data variables.product.prodname_ghe_server %} source repositories {% data reusables.enterprise_migrations.locking-repositories %} {% data reusables.enterprise_installation.ssh-into-instance %} -2. Para preparar um repositório para exportação, use o comando `ghe-migrator add` com a URL do repositório: - * Se estiver bloqueando o repositório, acrescente `--lock` ao comando. Se estiver executando uma execução de avaliação, `--lock` não será necessário. +2. To prepare a repository for export, use the `ghe-migrator add` command with the repository's URL: + * If you're locking the repository, append the command with `--lock`. If you're performing a trial run, `--lock` is not needed. ```shell - $ ghe-migrator add https://hostname/username/reponame --lock + $ ghe-migrator add https://HOSTNAME/USERNAME/REPO-NAME --lock ``` - * Você pode excluir anexos de arquivo acrescentando `--exclude_attachments` ao comando. {% data reusables.enterprise_migrations.exclude-file-attachments %} - * Para preparar a exportação de vários repositórios de uma só vez, crie um arquivo de texto listando cada URL do repositório em uma linha separada e execute o comando `ghe-migrator add` com o sinalizador `-i` e o caminho para seu arquivo de texto. + * You can exclude file attachments by appending `--exclude_attachments` to the command. {% data reusables.enterprise_migrations.exclude-file-attachments %} + * To prepare multiple repositories at once for export, create a text file listing each repository URL on a separate line, and run the `ghe-migrator add` command with the `-i` flag and the path to your text file. ```shell - $ ghe-migrator add -i PATH/TO/YOUR/REPOSITORY_URLS.txt + $ ghe-migrator add -i PATH/TO/YOUR/REPOSITORY_URL.txt ``` -3. Quando solicitado, informe seu nome de usuário do {% data variables.product.prodname_ghe_server %}: +3. When prompted, enter your {% data variables.product.prodname_ghe_server %} username: ```shell Enter username authorized for migration: admin ``` -4. Quando precisar fornecer um token de acesso pessoal, insira o token de acesso criado em "[Como preparar a instância de origem do {% data variables.product.prodname_ghe_server %}](#preparing-the-github-enterprise-server-source-instance)": +4. When prompted for a {% data variables.product.pat_generic %}, enter the access token you created in "[Preparing the {% data variables.product.prodname_ghe_server %} source instance](#preparing-the-github-enterprise-server-source-instance)": ```shell - Enter personal access token: ************** + Enter {% data variables.product.pat_generic %}: ************** ``` -5. Após a conclusão do `ghe-migrator add`, ele imprimirá o "GUID de Migração" exclusivo gerado para identificar a exportação e uma lista dos recursos adicionados à exportação. Você usará o GUID de Migração gerado nas etapas seguintes `ghe-migrator add` e `ghe-migrator export` para informar o `ghe-migrator` para continuar operando na mesma exportação. +5. When `ghe-migrator add` has finished it will print the unique "Migration GUID" that it generated to identify this export as well as a list of the resources that were added to the export. You will use the Migration GUID that it generated in subsequent `ghe-migrator add` and `ghe-migrator export` steps to tell `ghe-migrator` to continue operating on the same export. ```shell > 101 models added to export - > Migration GUID: example-migration-guid + > Migration GUID: EXAMPLE-MIGRATION-GUID > Number of records in this migration: > users | 5 > organizations | 1 @@ -79,33 +73,33 @@ ms.locfileid: '145094849' > attachments | 4 > projects | 2 ``` - Sempre que você adicionar um novo repositório com o GUID de Migração atual, ele atualizará a exportação atual. Se você executar `ghe-migrator add` novamente sem o GUID de Migração, ele vai iniciar uma nova exportação e gerar um novo GUID de Migração. **Não reutilize o GUID de Migração gerado durante uma exportação quando você começar a preparar a migração para importação**. + Each time you add a new repository with an existing Migration GUID it will update the existing export. If you run `ghe-migrator add` again without a Migration GUID it will start a new export and generate a new Migration GUID. **Do not re-use the Migration GUID generated during an export when you start preparing your migration for import**. -3. Se você bloqueou o repositório de origem, use o comando `ghe-migrator target_url` para personalizar uma mensagem de bloqueio na página do repositório que está vinculada ao novo local do repositório. Informe a URL do repositório de origem, a URL do repositório de destino e o GUID de Migração da Etapa 5: +3. If you locked the source repository, you can use the `ghe-migrator target_url` command to set a custom lock message on the repository page that links to the repository's new location. Pass the source repository URL, the target repository URL, and the Migration GUID from Step 5: ```shell - $ ghe-migrator target_url https://hostname/username/reponame https://target_hostname/target_username/target_reponame -g MIGRATION_GUID + $ ghe-migrator target_url https://HOSTNAME/USERNAME/REPO-NAME https://TARGET-HOSTNAME/TARGET-USER-NAME/TARGET-REPO-NAME -g MIGRATION-GUID ``` -6. Para adicionar mais repositórios à mesma exportação, use o comando `ghe-migrator add` com o sinalizador `-g`. Informe a nova URL do repositório e o GUID de Migração da Etapa 5: +6. To add more repositories to the same export, use the `ghe-migrator add` command with the `-g` flag. You'll pass in the new repository URL and the Migration GUID from Step 5: ```shell - $ ghe-migrator add https://hostname/username/other_reponame -g MIGRATION_GUID --lock + $ ghe-migrator add https://HOSTNAME/USERNAME/OTHER-REPO-NAME -g MIGRATION-GUID --lock ``` -7. Quando terminar de adicionar repositórios, gere o arquivo de migração usando o comando `ghe-migrator export` com o sinalizador `-g` e o GUID de Migração da Etapa 5: +7. When you've finished adding repositories, generate the migration archive using the `ghe-migrator export` command with the `-g` flag and the Migration GUID from Step 5: ```shell - $ ghe-migrator export -g MIGRATION_GUID - > Archive saved to: /data/github/current/tmp/MIGRATION_GUID.tar.gz + $ ghe-migrator export -g MIGRATION-GUID + > Archive saved to: /data/github/current/tmp/MIGRATION-GUID.tar.gz ``` * {% data reusables.enterprise_migrations.specify-staging-path %} -8. Feche a conexão com o {% data variables.product.product_location %}: +8. Close the connection to {% data variables.location.product_location %}: ```shell $ exit > logout - > Connection to hostname closed. + > Connection to HOSTNAME closed. ``` -9. Copie o arquivo de migração para o computador usando o comando [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp). O arquivo terá o nome do GUID de Migração: +9. Copy the migration archive to your computer using the [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) command. The archive file will be named with the Migration GUID: ```shell - $ scp -P 122 admin@hostname:/data/github/current/tmp/MIGRATION_GUID.tar.gz ~/Desktop + $ scp -P 122 admin@HOSTNAME:/data/github/current/tmp/MIGRATION-GUID.tar.gz ~/Desktop ``` {% data reusables.enterprise_migrations.ready-to-import-migrations %} diff --git a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md index f549d8cdce..ac34326e09 100644 --- a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md +++ b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md @@ -1,6 +1,6 @@ --- -title: Migrar dados para e da sua empresa -intro: 'É possível exportar dados de usuário, organização e repositório do {% data variables.product.prodname_ghe_server %} ou do {% data variables.product.prodname_dotcom_the_website %}, e depois importá-los no {% data variables.product.product_location %}.' +title: Migrating data to and from your enterprise +intro: 'You can export user, organization, and repository data from {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_dotcom_the_website %}, then import that data into {% data variables.location.product_location %}.' redirect_from: - /enterprise/admin/articles/moving-a-repository-from-github-com-to-github-enterprise - /enterprise/admin/categories/migrations-and-upgrades @@ -18,11 +18,5 @@ children: - /migrating-data-to-your-enterprise - /importing-data-from-third-party-version-control-systems shortTitle: Migration for an enterprise -ms.openlocfilehash: 1f08da59c2b9330f2230f8377230132bc2a57704 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145094848' --- diff --git a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md index 4643e92fed..b19fb060b4 100644 --- a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Migrar dados para a sua empresa -intro: 'Após gerar um arquivo de migração, você poderá importar os dados para a sua instância de destino do {% data variables.product.prodname_ghe_server %}. Antes de aplicar as alterações permanentemente na instância de destino, será possível revisá-las para resolver possíveis conflitos.' +title: Migrating data to your enterprise +intro: 'After generating a migration archive, you can import the data to your target {% data variables.product.prodname_ghe_server %} instance. You''ll be able to review changes for potential conflicts before permanently applying the changes to your target instance.' redirect_from: - /enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise - /enterprise/admin/migrations/applying-the-imported-data-on-github-enterprise-server @@ -19,27 +19,21 @@ topics: - Enterprise - Migration shortTitle: Import to your enterprise -ms.openlocfilehash: 19bd9e1e8cee072e8a8f00861e2d8f876b5b8450 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717666' --- -## Aplicar os dados importados em {% data variables.product.prodname_ghe_server %} +## Applying the imported data on {% data variables.product.prodname_ghe_server %} -Antes de migrar dados para sua empresa, você deve preparar os dados e resolver quaisquer conflitos. Para obter mais informações, confira "[Como se preparar para migrar dados para sua empresa](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)". +Before you can migrate data to your enterprise, you must prepare the data and resolve any conflicts. For more information, see "[Preparing to migrate data to your enterprise](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)." -Depois de preparar os dados e os conflitos de resolução, você poderá aplicar os dados importados em {% data variables.product.product_name %}. +After you prepare the data and resolve conflicts, you can apply the imported data on {% data variables.product.product_name %}. {% data reusables.enterprise_installation.ssh-into-target-instance %} -2. Usando o comando `ghe-migrator import`, inicie o processo de importação. Você precisará de: - * Seu Migration GUID. Para obter mais informações, confira "[Como se preparar para migrar dados para sua empresa](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)". - * Seu token de acesso pessoal para autenticação. O token de acesso pessoal que você usa é apenas para autenticação como administrador do site e não requer nenhum escopo específico. Para obter mais informações, confira "[Como criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)". +2. Using the `ghe-migrator import` command, start the import process. You'll need: + * Your Migration GUID. For more information, see "[Preparing to migrate data to your enterprise](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)." + * Your {% data variables.product.pat_generic %} for authentication. The {% data variables.product.pat_generic %} that you use is only for authentication as a site administrator, and does not require any specific scope{% ifversion pat-v2 %} or permissions{% endif %}. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." ```shell - $ ghe-migrator import /home/admin/MIGRATION_GUID.tar.gz -g MIGRATION_GUID -u username -p TOKEN + $ ghe-migrator import /home/admin/MIGRATION-GUID.tar.gz -g MIGRATION-GUID -u USERNAME -p TOKEN > Starting GitHub::Migrator > Import 100% complete / @@ -47,110 +41,113 @@ Depois de preparar os dados e os conflitos de resolução, você poderá aplicar * {% data reusables.enterprise_migrations.specify-staging-path %} -## Revisar dados de migração +## Reviewing migration data -Por padrão, `ghe-migrator audit` retorna todos os registros. Também é possível filtrar os registros por: +By default, `ghe-migrator audit` returns every record. It also allows you to filter records by: - * Tipos de registro; - * Estado de registro. + * The types of records. + * The state of the records. -Os tipos de registros correspondem aos encontrados nos [dados migrados](/enterprise/admin/guides/migrations/about-migrations/#migrated-data). +The record types match those found in the [migrated data](/enterprise/admin/guides/migrations/about-migrations/#migrated-data). -## Filtros por tipo de registro +## Record type filters -| Tipo de registro | Nome do filtro | +| Record type | Filter name | |-----------------------|--------| -| Usuários | `user` -| Organizações | `organization` -| Repositórios | `repository` +| Users | `user` +| Organizations | `organization` +| Repositories | `repository` | Teams | `team` -| Marcos | `milestone` -| Quadros de projeto | `project` -| Problemas | `issue` -| Comentários dos problemas | `issue_comment` -| Solicitações de pull | `pull_request` -| Revisões de pull request | `pull_request_review` -| Comentários de commit | `commit_comment` -| Comentários das revisões de pull request | `pull_request_review_comment` -| Versões | `release` -| Ações feitas em problemas ou em pull requests | `issue_event` -| Branches protegidos | `protected_branch` +| Milestones | `milestone` +| Project boards | `project` +| Issues | `issue` +| Issue comments | `issue_comment` +| Pull requests | `pull_request` +| Pull request reviews | `pull_request_review` +| Commit comments | `commit_comment` +| Pull request review comments | `pull_request_review_comment` +| Releases | `release` +| Actions taken on pull requests or issues | `issue_event` +| Protected branches | `protected_branch` -## Filtros por estado de registro +## Record state filters -| Estado de registro | Descrição | +| Record state | Description | |-----------------|----------------| -| `export` | O registro será exportado. | -| `import` | O registro será importado. | -| `map` | O registro será mapeado. | -| `rename` | O registro será renomeado. | -| `merge` | O registro passará por merge. | -| `exported` | O registro foi exportado com êxito. | -| `imported` | O registro foi importado com êxito. | -| `mapped` | O registro foi mapeado com êxito. | -| `renamed` | O registro foi renomeado com êxito. | -| `merged` | O registro passou por merge com êxito. | -| `failed_export` | Houve falha ao exportar o registro. | -| `failed_import` | Houve falha ao importar o registro. | -| `failed_map` | Houve falha ao mapear o registro. | -| `failed_rename` | Houve falha ao renomear o registro. | -| `failed_merge` | Houve falha ao fazer merge no registro. | +| `export` | The record will be exported. | +| `import` | The record will be imported. | +| `map` | The record will be mapped. | +| `rename` | The record will be renamed. | +| `merge` | The record will be merged. | +| `exported` | The record was successfully exported. | +| `imported` | The record was successfully imported. | +| `mapped` | The record was successfully mapped. | +| `renamed` | The record was successfully renamed. | +| `merged` | The record was successfully merged. | +| `failed_export` | The record failed to export. | +| `failed_import` | The record failed to be imported. | +| `failed_map` | The record failed to be mapped. | +| `failed_rename` | The record failed to be renamed. | +| `failed_merge` | The record failed to be merged. | -## Filtrar registros auditados +## Filtering audited records -Com o comando `ghe-migrator audit`, você pode filtrar os registros com base no tipo usando o sinalizador `-m`. Da mesma forma, você pode filtrar o estado de importação usando o sinalizador `-s`. O comando se parece com o seguinte: +With the `ghe-migrator audit` command, you can filter based on the record type using the `-m` flag. Similarly, you can filter on the import state using the `-s` flag. The command looks like this: ```shell -$ ghe-migrator audit -m RECORD_TYPE -s STATE -g MIGRATION_GUID +$ ghe-migrator audit -m RECORD_TYPE -s STATE -g MIGRATION-GUID ``` -Por exemplo, para visualizar todas as organizações e equipes importadas com êxito, você digitaria: +For example, to view every successfully imported organization and team, you would enter: ```shell -$ ghe-migrator audit -m organization,team -s mapped,renamed -g MIGRATION_GUID +$ ghe-migrator audit -m organization,team -s mapped,renamed -g MIGRATION-GUID > model_name,source_url,target_url,state > organization,https://gh.source/octo-org/,https://ghe.target/octo-org/,renamed ``` -**Recomendamos fortemente auditar todas as importações com falha.** Para fazer isso, você vai inserir: +**We strongly recommend auditing every import that failed.** To do that, you will enter: ```shell -$ ghe-migrator audit -s failed_import,failed_map,failed_rename,failed_merge -g MIGRATION_GUID +$ ghe-migrator audit -s failed_import,failed_map,failed_rename,failed_merge -g MIGRATION-GUID > model_name,source_url,target_url,state > user,https://gh.source/octocat,https://gh.target/octocat,failed > repository,https://gh.source/octo-org/octo-project,https://ghe.target/octo-org/octo-project,failed ``` -Em caso de problemas com falhas na importação, entre em contato com o {% data variables.contact.contact_ent_support %}. +If you have any concerns about failed imports, contact {% data variables.contact.contact_ent_support %}. -## Concluir a importação em {% data variables.product.prodname_ghe_server %} +## Completing the import on {% data variables.product.prodname_ghe_server %} -Depois que sua migração for aplicada à sua instância de destino e você tiver revisado a migração, você desbloqueará os repositórios e os excluirá da fonte. Antes de excluir os dados da origem, é recomendável aguardar cerca de duas semanas para garantir o funcionamento adequado de todos os procedimentos. +After your migration is applied to your target instance and you have reviewed the migration, you''ll unlock the repositories and delete them off the source. Before deleting your source data we recommend waiting around two weeks to ensure that everything is functioning as expected. -## Desbloquear repositórios na instância de destino +## Unlocking repositories on the target instance -{% data reusables.enterprise_installation.ssh-into-instance %} {% data reusables.enterprise_migrations.unlocking-on-instances %} +{% data reusables.enterprise_installation.ssh-into-instance %} +{% data reusables.enterprise_migrations.unlocking-on-instances %} -## Desbloquear repositórios na origem +## Unlocking repositories on the source -### Desbloquear repositórios de uma organização no {% data variables.product.prodname_dotcom_the_website %} +### Unlocking repositories from an organization on {% data variables.product.prodname_dotcom_the_website %} + +To unlock the repositories on a {% data variables.product.prodname_dotcom_the_website %} organization, you'll send a `DELETE` request to [the migration unlock endpoint](/free-pro-team@latest/rest/migrations#unlock-an-organization-repository). You'll need: + * Your access token for authentication + * The unique `id` of the migration + * The name of the repository to unlock -Para desbloquear os repositórios em uma organização do {% data variables.product.prodname_dotcom_the_website %}, você enviará uma solicitação `DELETE` para o [ponto de extremidade de desbloqueio da migração](/free-pro-team@latest/rest/migrations#unlock-an-organization-repository). Você precisará de: - * Token de acesso para autenticação; - * A `id` exclusiva da migração - * Nome do repositório a ser desbloqueado. ```shell -curl -H "Authorization: Bearer GITHUB_ACCESS_TOKEN" -X DELETE \ +curl -H "Authorization: Bearer GITHUB_ACCESS_TOKEN" -X DELETE \ -H "Accept: application/vnd.github.wyandotte-preview+json" \ - https://api.github.com/orgs/orgname/migrations/id/repos/repo_name/lock + https://api.github.com/orgs/ORG-NAME/migrations/ID/repos/REPO_NAME/lock ``` -### Excluir repositórios de uma organização no {% data variables.product.prodname_dotcom_the_website %} +### Deleting repositories from an organization on {% data variables.product.prodname_dotcom_the_website %} -Depois de desbloquear os repositórios da organização do {% data variables.product.prodname_dotcom_the_website %}, você deve excluir todos os repositórios já migrados usando [o ponto de extremidade de exclusão do repositório](/rest/repos/#delete-a-repository). Você precisará do token de acesso para autenticação: +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/repos/#delete-a-repository). You'll need your access token for authentication: ```shell -curl -H "Authorization: Bearer GITHUB_ACCESS_TOKEN" -X DELETE \ - https://api.github.com/repos/orgname/repo_name +curl -H "Authorization: Bearer GITHUB_ACCESS_TOKEN" -X DELETE \ + https://api.github.com/repos/ORG-NAME/REPO_NAME ``` -### Desbloquear repositórios de uma instância do {% data variables.product.prodname_ghe_server %} +### Unlocking repositories from a {% data variables.product.prodname_ghe_server %} instance -{% data reusables.enterprise_installation.ssh-into-instance %} {% data reusables.enterprise_migrations.unlocking-on-instances %} +{% data reusables.enterprise_installation.ssh-into-instance %} +{% data reusables.enterprise_migrations.unlocking-on-instances %} diff --git a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md index f15ecef26d..c0787f5ae1 100644 --- a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- -title: Sobre a autenticação com logon único de SAML -intro: 'Você pode acessar {% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %}uma organização que usa logon único (SSO) SAML{% endif %} autenticando {% ifversion ghae %}com logon único (SSO) SAML {% endif %}por meio de um provedor de identidade (IdP).' +title: About authentication with SAML single sign-on +intro: 'You can access {% ifversion ghae %}{% data variables.location.product_location %}{% elsif ghec %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% ifversion ghae %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).' redirect_from: - /articles/about-authentication-with-saml-single-sign-on - /github/authenticating-to-github/about-authentication-with-saml-single-sign-on @@ -11,65 +11,60 @@ versions: topics: - SSO shortTitle: SAML single sign-on -ms.openlocfilehash: 7fb15bab585093a618f9c082d340c2fe66d67df7 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147527907' --- -## Sobre autenticação com SSO do SAML +## About authentication with SAML SSO {% ifversion ghae %} -O SAML SSO permite que um proprietário corporativo realize o controle central e proteja o acesso para {% data variables.product.product_name %} a partir de um IdP do SAML. Ao acessar {% data variables.product.product_location %} em um navegador, {% data variables.product.product_name %} irá redirecioná-lo para seu IdP para efetuar a autenticação. Depois de concluir a autenticação com sucesso com uma conta no IdP, este irá redirecionar você de volta para {% data variables.product.product_location %}. {% data variables.product.product_name %} valida a resposta do seu IpD e, em seguida, concede acesso. +SAML SSO allows an enterprise owner to centrally control and secure access to {% data variables.product.product_name %} from a SAML IdP. When you visit {% data variables.location.product_location %} in a browser, {% data variables.product.product_name %} will redirect you to your IdP to authenticate. After you successfully authenticate with an account on the IdP, the IdP redirects you back to {% data variables.location.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access. {% data reusables.saml.you-must-periodically-authenticate %} -Se você não puder acessar {% data variables.product.product_name %}, entre em contato com o proprietário da empresa local ou administrador para {% data variables.product.product_name %}. Talvez você possa localizar as informações de contato da sua empresa clicando em **Suporte** na parte inferior de qualquer página no {% data variables.product.product_name %}. {% data variables.product.company_short %} e {% data variables.contact.github_support %} não têm acesso ao seu IdP e não podem solucionar problemas de autenticação. +If you can't access {% data variables.product.product_name %}, contact your local enterprise owner or administrator for {% data variables.product.product_name %}. You may be able to locate contact information for your enterprise by clicking **Support** at the bottom of any page on {% data variables.product.product_name %}. {% data variables.product.company_short %} and {% data variables.contact.github_support %} do not have access to your IdP, and cannot troubleshoot authentication problems. {% endif %} {% ifversion fpt or ghec %} -{% data reusables.saml.dotcom-saml-explanation %} Os proprietários da organização podem convidar sua conta pessoal no {% data variables.product.prodname_dotcom %} para ingressar na organização deles que usa o SSO do SAML, o que permitirá a você colaborar com a organização e manter sua identidade e colaborações existentes no {% data variables.product.prodname_dotcom %}. +{% data reusables.saml.dotcom-saml-explanation %} Organization owners can invite your personal account on {% data variables.product.prodname_dotcom %} to join their organization that uses SAML SSO, which allows you to contribute to the organization and retain your existing identity and contributions on {% data variables.product.prodname_dotcom %}. -Se você for integrante de um {% data variables.product.prodname_emu_enterprise %}, você usará uma nova conta que lhe será fornecida e controlada pela sua empresa. {% data reusables.enterprise-accounts.emu-more-info-account %} +If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you will instead use a new account that is provisioned for you and controlled by your enterprise. {% data reusables.enterprise-accounts.emu-more-info-account %} -Ao acessar os recursos privados dentro de uma organização que usa o SSO SAML, o {% data variables.product.prodname_dotcom %} vai redirecionar você para o SAML IdP da organização para que você efetue a autenticação. Depois de efetuar a autenticação com sucesso com sua conta no IdP, este irá redirecionar você de volta para {% data variables.product.prodname_dotcom %}, onde você poderá acessar os recursos da organização. +When you access private resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to {% data variables.product.prodname_dotcom %}, where you can access the organization's resources. {% data reusables.saml.outside-collaborators-exemption %} -Se você efetuou a autenticação recentemente com o IdP SAML da sua organização no navegador, você estará automaticamente autorizado ao acessar uma organização do {% data variables.product.prodname_dotcom %} que usa SAML SSO. Se não tiver efetuado a autenticação recentemente com o IdP SAML da sua organização no navegador, você deverá efetuar a autenticação no SAML IdP antes de acessar a organização. +If you have recently authenticated with your organization's SAML IdP in your browser, you are automatically authorized when you access a {% data variables.product.prodname_dotcom %} organization that uses SAML SSO. If you haven't recently authenticated with your organization's SAML IdP in your browser, you must authenticate at the SAML IdP before you can access the organization. {% data reusables.saml.you-must-periodically-authenticate %} -## Identidades SAML vinculadas +## Linked SAML identities -Quando você se autenticar com sua conta IdP e retornar para {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_dotcom %} registrará um link na organização ou empresa entre sua conta pessoal do {% data variables.product.prodname_dotcom %} e a identidade SAML na qual você se conectou. Essa identidade vinculada é usada para validar sua associação nessa organização e, dependendo de sua organização ou configuração empresarial, também é usada para determinar de quais organizações e equipes você também é membro. Cada conta do {% data variables.product.prodname_dotcom %} pode ser vinculada a exatamente uma identidade SAML por organização. Da mesma forma, cada identidade SAML pode ser vinculada a exatamente uma conta do {% data variables.product.prodname_dotcom %} em uma organização. +When you authenticate with your IdP account and return to {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_dotcom %} will record a link in the organization or enterprise between your {% data variables.product.prodname_dotcom %} personal account and the SAML identity you signed into. This linked identity is used to validate your membership in that organization, and depending on your organization or enterprise setup, is also used to determine which organizations and teams you're a member of as well. Each {% data variables.product.prodname_dotcom %} account can be linked to exactly one SAML identity per organization. Likewise, each SAML identity can be linked to exactly one {% data variables.product.prodname_dotcom %} account in an organization. -Se você entrar com uma identidade SAML que já esteja vinculada a outra conta do {% data variables.product.prodname_dotcom %}, receberá uma mensagem de erro indicando que você não pode entrar com essa identidade SAML. Essa situação poderá ocorrer se você estiver tentando usar uma nova conta do {% data variables.product.prodname_dotcom %} para trabalhar dentro da sua organização. Se você não pretende usar essa identidade SAML com essa conta do {% data variables.product.prodname_dotcom %}, precisará sair dessa identidade SAML e repetir o logon SAML. Se você quiser usar essa identidade SAML com sua conta do {% data variables.product.prodname_dotcom %}, precisará pedir ao administrador para desvincular sua identidade SAML de sua conta antiga, para que possa vinculá-la à sua nova conta. Dependendo da configuração da sua organização ou empresa, o administrador também pode precisar reatribuir sua identidade em seu provedor SAML. Para obter mais informações, confira "[Como exibir e gerenciar o acesso SAML de um membro à sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)". +If you sign in with a SAML identity that is already linked to another {% data variables.product.prodname_dotcom %} account, you will receive an error message indicating that you cannot sign in with that SAML identity. This situation can occur if you are attempting to use a new {% data variables.product.prodname_dotcom %} account to work inside of your organization. If you didn't intend to use that SAML identity with that {% data variables.product.prodname_dotcom %} account, then you'll need to sign out of that SAML identity and then repeat the SAML login. If you do want to use that SAML identity with your {% data variables.product.prodname_dotcom %} account, you'll need to ask your admin to unlink your SAML identity from your old account, so that you can link it to your new account. Depending on the setup of your organization or enterprise, your admin may also need to reassign your identity within your SAML provider. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)." -Se a identidade SAML com a qual você se conecta não corresponder à identidade SAML que está vinculada atualmente à sua conta do {% data variables.product.prodname_dotcom %}, você receberá um aviso de que está prestes a vincular novamente sua conta. Como sua identidade SAML é usada para controlar o acesso e a associação de equipe, continuar com a nova identidade SAML poderá fazer com que você perca o acesso a equipes e organizações dentro de {% data variables.product.prodname_dotcom %}. Continue apenas se souber que deve usar essa nova identidade SAML para autenticação no futuro. +If the SAML identity you sign in with does not match the SAML identity that is currently linked to your {% data variables.product.prodname_dotcom %} account, you'll receive a warning that you are about to relink your account. Because your SAML identity is used to govern access and team membership, continuing with the new SAML identity can cause you to lose access to teams and organizations inside of {% data variables.product.prodname_dotcom %}. Only continue if you know that you're supposed to use that new SAML identity for authentication in the future. -## Como autorizar PATs e chaves SSH com SSO SAML +## Authorizing {% data variables.product.pat_generic %}s and SSH keys with SAML SSO -Para usar a API ou o Git na linha de comando de modo a acessar conteúdo protegido em uma organização que usa SAML SSO, você precisará usar um token de acesso pessoal autorizado por HTTPS ou uma chave SSH autorizada. +To use the API or Git on the command line to access protected content in an organization that uses SAML SSO, you will need to use an authorized {% data variables.product.pat_generic %} over HTTPS or an authorized SSH key. -Na falta de um token de acesso pessoal ou uma chave SSH, você poderá criar um token de acesso pessoal para a linha de comando ou gerar uma nova chave SSH. Para obter mais informações, confira "[Como criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)" ou "[Como gerar uma nova chave SSH e adicioná-la ao ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". +If you don't have a {% data variables.product.pat_generic %} or an SSH key, you can create a {% data variables.product.pat_generic %} for the command line or generate a new SSH key. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)" or "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." -Para usar um token novo ou existente de acesso pessoal ou chave SSH com uma organização que usa ou impõe o SSO do SAML, você precisará autorizar o token ou autorizar a chave SSH para uso com uma organização de SSO do SAML. Para obter mais informações, confira "[Como autorizar um token de acesso pessoal para uso com o logon único do SAML](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" ou "[Como autorizar uma chave SSH para uso com o logon único do SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)". +To use a new or existing {% data variables.product.pat_generic %} or SSH key with an organization that uses or enforces SAML SSO, you will need to authorize the token or authorize the SSH key for use with a SAML SSO organization. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." -## Sobre o {% data variables.product.prodname_oauth_apps %}, {% data variables.product.prodname_github_apps %} e SSO do SAML +## About {% data variables.product.prodname_oauth_apps %}, {% data variables.product.prodname_github_apps %}, and SAML SSO -Você deverá ter uma sessão do SAML ativa sempre que autorizar um {% data variables.product.prodname_oauth_app %} ou {% data variables.product.prodname_github_app %} a acessar uma organização que use ou aplique o SSO do SAML. Você pode criar uma sessão do SAML ativa ao acessar `https://github.com/orgs/ORGANIZATION-NAME/sso` no navegador. +You must have an active SAML session each time you authorize an {% data variables.product.prodname_oauth_app %} or {% data variables.product.prodname_github_app %} to access an organization that uses or enforces SAML SSO. You can create an active SAML session by navigating to `https://github.com/orgs/ORGANIZATION-NAME/sso` in your browser. -Depois que um proprietário da empresa ou organização habilitar ou impuser o SSO do SAML a uma organização e, depois que se autenticar via SAML pela primeira vez, você deverá reautorizar todos os {% data variables.product.prodname_oauth_apps %} ou {% data variables.product.prodname_github_apps %} autorizados anteriormente para acessar a organização. +After an enterprise or organization owner enables or enforces SAML SSO for an organization, and after you authenticate via SAML for the first time, you must reauthorize any {% data variables.product.prodname_oauth_apps %} or {% data variables.product.prodname_github_apps %} that you previously authorized to access the organization. -Para ver os {% data variables.product.prodname_oauth_apps %} que você autorizou, visite sua [página dos {% data variables.product.prodname_oauth_apps %}](https://github.com/settings/applications). Para ver os {% data variables.product.prodname_github_apps %} que você autorizou, visite sua [página dos {% data variables.product.prodname_github_apps %}](https://github.com/settings/apps/authorizations). +To see the {% data variables.product.prodname_oauth_apps %} you've authorized, visit your [{% data variables.product.prodname_oauth_apps %} page](https://github.com/settings/applications). To see the {% data variables.product.prodname_github_apps %} you've authorized, visit your [{% data variables.product.prodname_github_apps %} page](https://github.com/settings/apps/authorizations). {% endif %} -## Leitura adicional +## Further reading -{% ifversion ghec %}– "[Sobre o gerenciamento de identidades e acesso com o logon único do SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} {% ifversion ghae %}– "[Sobre o gerenciamento de identidades e acesso para sua empresa](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} +{% ifversion ghec %}- "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} +{% ifversion ghae %}- "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} diff --git a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md index 5dc56f5acf..cc1537e412 100644 --- a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- title: Authorizing a personal access token for use with SAML single sign-on -intro: 'To use a personal access token with an organization that uses SAML single sign-on (SSO), you must first authorize the token.' +intro: 'To use a {% data variables.product.pat_v1 %} with an organization that uses SAML single sign-on (SSO), you must first authorize the token.' redirect_from: - /articles/authorizing-a-personal-access-token-for-use-with-a-saml-single-sign-on-organization - /articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on @@ -10,9 +10,9 @@ versions: ghec: '*' topics: - SSO -shortTitle: PAT with SAML +shortTitle: '{% data variables.product.pat_generic_caps %} with SAML' --- -You can authorize an existing personal access token, or [create a new personal access token](/github/authenticating-to-github/creating-a-personal-access-token) and then authorize it. +You must authorize your {% data variables.product.pat_v1 %} after creation before the token can access an organization that uses SAML single sign-on (SSO). For more information about creating a new {% data variables.product.pat_v1 %}, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."{% ifversion pat-v2 %} {% data variables.product.pat_v2_caps %}s are authorized during token creation, before access to the organization is granted.{% endif %} {% data reusables.saml.must-authorize-linked-identity %} @@ -23,11 +23,11 @@ You can authorize an existing personal access token, or [create a new personal a {% data reusables.user-settings.personal_access_tokens %} 3. Next to the token you'd like to authorize, click **Configure SSO**. {% data reusables.saml.authenticate-with-saml-at-least-once %} - ![Screenshot of the dropdown menu to configure SSO for a personal access token](/assets/images/help/settings/sso-allowlist-button.png) + ![Screenshot of the dropdown menu to configure SSO for a {% data variables.product.pat_v1 %}](/assets/images/help/settings/sso-allowlist-button.png) 4. To the right of the organization you'd like to authorize the token for, click **Authorize**. ![Token authorize button](/assets/images/help/settings/token-authorize-button.png) ## Further reading -- "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)" +- "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)" - "[About authentication with SAML single sign-on](/articles/about-authentication-with-saml-single-sign-on)" diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/about-ssh.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/about-ssh.md index 53b7c7225e..547784b6ad 100644 --- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/about-ssh.md +++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/about-ssh.md @@ -1,6 +1,6 @@ --- title: About SSH -intro: 'Using the SSH protocol, you can connect and authenticate to remote servers and services. With SSH keys, you can connect to {% data variables.product.product_name %} without supplying your username and personal access token at each visit.{% ifversion ssh-commit-verification %} You can also use an SSH key to sign commits.{% endif %}' +intro: 'Using the SSH protocol, you can connect and authenticate to remote servers and services. With SSH keys, you can connect to {% data variables.product.product_name %} without supplying your username and {% data variables.product.pat_generic %} at each visit.{% ifversion ssh-commit-verification %} You can also use an SSH key to sign commits.{% endif %}' redirect_from: - /articles/about-ssh - /github/authenticating-to-github/about-ssh diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md index 2541492d63..1e7cde5e8d 100644 --- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md +++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md @@ -1,6 +1,6 @@ --- -title: Adicionar uma nova chave SSH à sua conta do GitHub -intro: 'Para configurar sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} para usar sua chave SSH nova (ou existente) chave SSH, você também deverá adicionar a chave à sua conta.' +title: Adding a new SSH key to your GitHub account +intro: 'To configure your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} to use your new (or existing) SSH key, you''ll also need to add the key to your account.' redirect_from: - /articles/adding-a-new-ssh-key-to-your-github-account - /github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account @@ -13,47 +13,53 @@ versions: topics: - SSH shortTitle: Add a new SSH key -ms.openlocfilehash: 041d72c2cf48d6d5b8ce0e6b609b0982b54f2e97 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147653303' --- -## Sobre a adição de chaves SSH à sua conta -{% data reusables.ssh.about-ssh %} Para obter mais informações, confira "[Sobre o SSH](/authentication/connecting-to-github-with-ssh/about-ssh)." +## About addition of SSH keys to your account -{% ifversion ssh-commit-verification %} Você também pode usar SSH para assinar confirmações e marcas. Para obter mais informações sobre como assinar uma confirmação, confira "[Sobre a verificação de assinaturas de confirmação](/articles/about-commit-signature-verification)".{% endif %} +{% data reusables.ssh.about-ssh %} For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)." -Depois de gerar um par de chaves SSH, você precisa adicionar a chave pública a {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} para habilitar o acesso SSH para sua conta. +{% ifversion ssh-commit-verification %}You can also use SSH to sign commits and tags. For more information about commit signing, see "[About commit signature verification](/articles/about-commit-signature-verification)."{% endif %} -## Pré-requisitos +After you generate an SSH key pair, you must add the public key to {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable SSH access for your account. -Antes de adicionar uma nova chave SSH à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, conclua as etapas a seguir. +## Prerequisites -1. Verifique se há chaves SSH existentes. Para obter mais informações, confira "[Como verificar se há chaves SSH existentes](/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys)". -1. Gere uma nova chave SSH e adicione-a ao agente SSH do computador. Para obter mais informações, confira "[Como gerar uma nova chave SSH e adicioná-la ao ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". +Before adding a new SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, complete the following steps. -## Como adicionar uma nova chave SSH à sua conta +1. Check for existing SSH keys. For more information, see "[Checking for existing SSH keys](/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys)." +1. Generate a new SSH key and add it to your machine's SSH agent. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." -Depois de adicionar uma nova chave SSH de autenticação à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, você poderá reconfigurar qualquer repositório local para usar SSH. Para obter mais informações, confira "[Como alternar URLs remotas de HTTPS para SSH](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-https-to-ssh)". +## Adding a new SSH key to your account + +After adding a new SSH authentication key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, you can reconfigure any local repositories to use SSH. For more information, see "[Switching remote URLs from HTTPS to SSH](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-https-to-ssh)." {% data reusables.ssh.key-type-support %} {% webui %} -{% data reusables.gpg.copy-ssh-public-key %} {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.ssh %} -4. Clique em **Nova chave SSH** ou **Adicionar chave SSH**. -{% ifversion ssh-commit-verification %} ![Botão da chave SSH](/assets/images/help/settings/ssh-add-ssh-key-with-auth.png) {% else %} ![Botão da chave SSH](/assets/images/help/settings/ssh-add-ssh-key.png) {% endif %} -5. No campo "Title" (Título), adicione uma etiqueta descritiva para a nova chave. Por exemplo, se estiver usando um laptop pessoal, você poderá chamar essa chave de "Laptop pessoal". +{% data reusables.gpg.copy-ssh-public-key %} +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.ssh %} +4. Click **New SSH key** or **Add SSH key**. {% ifversion ssh-commit-verification %} -6. Selecione o tipo de chave: autenticação ou assinatura. Para obter mais informações sobre a assinatura de confirmações, confira "[Sobre a verificação de assinaturas de confirmação](/articles/about-commit-signature-verification)". + ![SSH Key button](/assets/images/help/settings/ssh-add-ssh-key-with-auth.png) +{% else %} + ![SSH Key button](/assets/images/help/settings/ssh-add-ssh-key.png) {% endif %} -7. Cole sua chave no campo "Key" (Chave). -{% ifversion ssh-commit-verification %} ![O campo da chave](/assets/images/help/settings/ssh-key-paste-with-type.png) {% else %} ![O campo da chave](/assets/images/help/settings/ssh-key-paste.png) {% endif %} -8. Clique em **Adicionar chave SSH**. - ![Botão Adicionar chave](/assets/images/help/settings/ssh-add-key.png) {% data reusables.user-settings.sudo-mode-popup %} +5. In the "Title" field, add a descriptive label for the new key. For example, if you're using a personal laptop, you might call this key "Personal laptop". +{% ifversion ssh-commit-verification %} +6. Select the type of key, either authentication or signing. For more information about commit signing, see "[About commit signature verification](/articles/about-commit-signature-verification)." +{% endif %} +7. Paste your key into the "Key" field. +{% ifversion ssh-commit-verification %} + ![The key field](/assets/images/help/settings/ssh-key-paste-with-type.png) +{% else %} + ![The key field](/assets/images/help/settings/ssh-key-paste.png) +{% endif %} +8. Click **Add SSH key**. + ![The Add key button](/assets/images/help/settings/ssh-add-key.png) +{% data reusables.user-settings.sudo-mode-popup %} {% endwebui %} @@ -61,23 +67,23 @@ Depois de adicionar uma nova chave SSH de autenticação à sua conta em {% ifve {% data reusables.cli.cli-learn-more %} -Antes de poder usar o {% data variables.product.prodname_cli %} para adicionar uma chave SSH à sua conta, você deve efetuar a autenticação no {% data variables.product.prodname_cli %}. Para obter mais informações, confira "[`gh auth login`](https://cli.github.com/manual/gh_auth_login)" na documentação da {% data variables.product.prodname_cli %}. +Before you can use the {% data variables.product.prodname_cli %} to add an SSH key to your account, you must authenticate to the {% data variables.product.prodname_cli %}. For more information, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login) in the {% data variables.product.prodname_cli %} documentation. -{% ifversion ssh-commit-verification %} No momento, você só pode usar {% data variables.product.prodname_cli %} para adicionar chaves de autenticação SSH, não é possível adicionar chaves de assinatura SSH.{% endif %} +{% ifversion ssh-commit-verification %}At present, you can only use {% data variables.product.prodname_cli %} to add SSH authentication keys, you cannot add SSH signing keys.{% endif %} -Para adicionar uma chave de autenticação SSH à sua conta do GitHub, use o subcomando `ssh-key add` especificando a chave pública. +To add an SSH authentication key to your GitHub account, use the `ssh-key add` subcommand, specifying your public key. ```shell -gh ssh-key add key-file +gh ssh-key add KEY-FILE ``` -Para incluir um título para a nova chave, use o sinalizador `-t` ou `--title`. +To include a title for the new key, use the `-t` or `--title` flag. ```shell -gh ssh-key add key-file --title "personal laptop" +gh ssh-key add KEY-FILE --title "personal laptop" ``` -Se você gerou sua chave SSH seguindo as instruções descritas em "[Como gerar uma nova chave SSH](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)", adicione a chave à sua conta com este comando. +If you generated your SSH key by following the instructions in "[Generating a new SSH key](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)", you can add the key to your account with this command. ```shell gh ssh-key add ~/.ssh/id_ed25519.pub @@ -86,6 +92,7 @@ gh ssh-key add ~/.ssh/id_ed25519.pub {% endcli %} {% ifversion fpt or ghec %} -## Leitura adicional +## Further reading -- "[Como autorizar uma chave SSH para uso com o logon único do SAML](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)" {% endif %} +- "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)" +{% endif %} diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md index c23fc6a31a..e840701467 100644 --- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md +++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md @@ -1,6 +1,6 @@ --- -title: Verificar se há chaves SSH -intro: 'Antes de gerar uma chave SSH, você pode verificar se há outras chaves SSH.' +title: Checking for existing SSH keys +intro: 'Before you generate an SSH key, you can check to see if you have any existing SSH keys.' redirect_from: - /articles/checking-for-existing-ssh-keys - /github/authenticating-to-github/checking-for-existing-ssh-keys @@ -13,46 +13,41 @@ versions: topics: - SSH shortTitle: Check for existing SSH key -ms.openlocfilehash: 4487e44b1cbba7038364e92f3194d5c3c06c505b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147409104' --- -## Sobre chaves SSH -Você pode usar o SSH para executar operações do Git em repositórios em {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. Para obter mais informações, confira "[Sobre o SSH](/authentication/connecting-to-github-with-ssh/about-ssh)". +## About SSH keys -Se você tiver uma chave SSH existente, poderá usar a chave para autenticar as operações do Git por SSH. +You can use SSH to perform Git operations in repositories on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)." -## Verificar se há chaves SSH +If you have an existing SSH key, you can use the key to authenticate Git operations over SSH. -Antes de gerar uma nova chave SSH, verifique se há chaves existentes no computador local. +## Checking for existing SSH keys + +Before you generate a new SSH key, you should check your local machine for existing keys. {% data reusables.ssh.key-type-support %} {% data reusables.command_line.open_the_multi_os_terminal %} -2. Insira `ls -al ~/.ssh` para ver se as chaves SSH existentes estão presentes. +2. Enter `ls -al ~/.ssh` to see if existing SSH keys are present. ```shell $ ls -al ~/.ssh # Lists the files in your .ssh directory, if they exist ``` -3. Verifique a listagem do diretório para verificar se você já tem uma chave SSH pública. Por padrão, {% ifversion ghae %}o nome de arquivo de uma chave pública compatível para o {% data variables.product.product_name %} é *id_rsa.pub*.{% else %}os nomes de arquivos de chaves públicas compatíveis para o {% data variables.product.product_name %} são um dos mostrados a seguir. +3. Check the directory listing to see if you already have a public SSH key. By default, the {% ifversion ghae %}filename of a supported public key for {% data variables.product.product_name %} is *id_rsa.pub*.{% else %}filenames of supported public keys for {% data variables.product.product_name %} are one of the following. - *id_rsa.pub* - *id_ecdsa.pub* - *id_ed25519.pub*{% endif %} {% tip %} - **Dica**: se você receber um erro indicando que *~/.ssh* não existe, você não terá um par de chaves SSH existente no local padrão. Você pode criar um novo par de chaves SSH na próxima etapa. + **Tip**: If you receive an error that *~/.ssh* doesn't exist, you do not have an existing SSH key pair in the default location. You can create a new SSH key pair in the next step. {% endtip %} -4. Gere uma nova chave SSH ou faça o upload de uma chave existente. - - Se você não tem um par de chave pública e privada compatível ou não deseja usar nenhum que esteja disponível, gere uma nova chave SSH. - - Se um par de chaves pública e privada existente estiver listado (por exemplo, *id_rsa.pub* e *id_rsa*) que você deseja usar para se conectar ao {% data variables.product.product_name %}, você poderá adicionar a chave ao ssh-agent. +4. Either generate a new SSH key or upload an existing key. + - If you don't have a supported public and private key pair, or don't wish to use any that are available, generate a new SSH key. + - If you see an existing public and private key pair listed (for example, *id_rsa.pub* and *id_rsa*) that you would like to use to connect to {% data variables.product.product_name %}, you can add the key to the ssh-agent. - Para obter mais informações sobre a geração de uma nova chave SSH ou a adição de uma chave existente ao ssh-agent, confira "[Como gerar uma nova chave SSH e adicioná-la ao ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". + For more information about generation of a new SSH key or addition of an existing key to the ssh-agent, see "[Generating a new SSH key and adding it to the ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md index 870e5fd520..e6c655b322 100644 --- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md +++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md @@ -29,11 +29,11 @@ If you want to use a hardware security key to authenticate to {% data variables. ## Generating a new SSH key -You can generate a new SSH key on your local machine. After you generate the key, you can add the key to your account on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable authentication for Git operations over SSH. +You can generate a new SSH key on your local machine. After you generate the key, you can add the key to your account on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable authentication for Git operations over SSH. {% ifversion ghes %} -If you are a site administrator for {% data variables.product.product_location %}, you can use the same key to grant yourself administrative SSH access to the instance. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." +If you are a site administrator for {% data variables.location.product_location %}, you can use the same key to grant yourself administrative SSH access to the instance. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." {% endif %} diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md index a9380a3409..a97d7da6c6 100644 --- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md +++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md @@ -1,6 +1,6 @@ --- -title: Testar a conexão SSH -intro: 'Depois de configurar sua chave SSH e adicioná-la à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, você poderá testar a sua conexão.' +title: Testing your SSH connection +intro: 'After you''ve set up your SSH key and added it to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, you can test your connection.' redirect_from: - /articles/testing-your-ssh-connection - /github/authenticating-to-github/testing-your-ssh-connection @@ -13,28 +13,22 @@ versions: topics: - SSH shortTitle: Test your SSH connection -ms.openlocfilehash: 7724c5939b319748f270db2f190a6df825b0bb4f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146338970' --- -Antes de testar a conexão SSH, é recomendável que você tenha: -- [Verificado se há chaves SSH existentes](/articles/checking-for-existing-ssh-keys) -- [Gerado uma nova chave SSH](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) -- [Adicionado uma nova chave SSH à sua conta do GitHub](/articles/adding-a-new-ssh-key-to-your-github-account) +Before testing your SSH connection, you should have: +- [Checked for existing SSH keys](/articles/checking-for-existing-ssh-keys) +- [Generated a new SSH key](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) +- [Added a new SSH key to your GitHub account](/articles/adding-a-new-ssh-key-to-your-github-account) -Quando você testar a conexão, precisará autenticar essa ação usando sua senha, que é a frase secreta da chave SSH que você criou anteriormente. Para obter mais informações sobre como trabalhar com frases secretas da chave SSH, confira ["Como trabalhar com frases secretas da chave SSH"](/articles/working-with-ssh-key-passphrases). +When you test your connection, you'll need to authenticate this action using your password, which is the SSH key passphrase you created earlier. For more information on working with SSH key passphrases, see ["Working with SSH key passphrases"](/articles/working-with-ssh-key-passphrases). {% data reusables.command_line.open_the_multi_os_terminal %} -2. Insira o seguinte: +2. Enter the following: ```shell $ ssh -T git@{% data variables.command_line.codeblock %} # Attempts to ssh to {% data variables.product.product_name %} ``` - Você poderá receber um aviso como este: + You may see a warning like this: ```shell > The authenticity of host '{% data variables.command_line.codeblock %} (IP ADDRESS)' can't be established. @@ -42,15 +36,15 @@ Quando você testar a conexão, precisará autenticar essa ação usando sua sen > Are you sure you want to continue connecting (yes/no)? ``` -3. Verifique se a impressão digital na mensagem que você vê corresponde à {% ifversion fpt or ghec %}[impressão digital de chave pública do {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/githubs-ssh-key-fingerprints){% else %} impressão digital de chave pública da sua empresa{% endif %}. Se isso acontecer, digite `yes`: +3. Verify that the fingerprint in the message you see matches {% ifversion fpt or ghec %}[{% data variables.product.prodname_dotcom %}'s public key fingerprint](/github/authenticating-to-github/githubs-ssh-key-fingerprints){% else %} your enterprise's public key fingerprint{% endif %}. If it does, then type `yes`: ```shell - > Hi username! You've successfully authenticated, but GitHub does not + > Hi USERNAME! You've successfully authenticated, but GitHub does not > provide shell access. ``` {% linux %} - Você verá esta mensagem de erro: + You may see this error message: ```shell ... Agent admitted failure to sign using the key. @@ -58,14 +52,14 @@ Quando você testar a conexão, precisará autenticar essa ação usando sua sen Permission denied (publickey). ``` - Esse é um problema conhecido com determinadas distribuições Linux. Para obter mais informações, confira ["Erro: Agente com falha ao entrar"](/articles/error-agent-admitted-failure-to-sign). + This is a known problem with certain Linux distributions. For more information, see ["Error: Agent admitted failure to sign"](/articles/error-agent-admitted-failure-to-sign). {% endlinux %} {% note %} - **Observação:** o comando remoto deve sair com o código 1. + **Note:** The remote command should exit with code 1. {% endnote %} -4. Verifique se a mensagem resultante contém seu nome de usuário. Se você receber a mensagem "Permissão negada", confira ["Erro: Permissão negada (chave pública)"](/articles/error-permission-denied-publickey). +4. Verify that the resulting message contains your username. If you receive a "permission denied" message, see ["Error: Permission denied (publickey)"](/articles/error-permission-denied-publickey). diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md index 333489dfd5..0eefcc7612 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md @@ -1,6 +1,6 @@ --- -title: Sobre a autenticação no GitHub -intro: 'Você pode acessar com segurança os recursos da sua conta efetuando a autenticação no {% data variables.product.product_name %} e usando credenciais diferentes dependendo de onde você efetua a autenticação.' +title: About authentication to GitHub +intro: 'You can securely access your account''s resources by authenticating to {% data variables.product.product_name %}, using different credentials depending on where you authenticate.' versions: fpt: '*' ghes: '*' @@ -13,107 +13,101 @@ redirect_from: - /github/authenticating-to-github/about-authentication-to-github - /github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github shortTitle: Authentication to GitHub -ms.openlocfilehash: d40d3e18c75c2e5d8f16ebbb4fd9b6fdf03e2a73 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147718090' --- -## Sobre autenticação no {% data variables.product.prodname_dotcom %} +## About authentication to {% data variables.product.prodname_dotcom %} -Para manter sua conta segura, você precisa se autenticar antes de acessar{% ifversion not ghae %} alguns{% endif %} recursos do {% data variables.product.product_name %}. Ao efetuar a autenticação em {% data variables.product.product_name %}, você fornece ou confirma credenciais que são exclusivas que provam quem você declara ser. +To keep your account secure, you must authenticate before you can access{% ifversion not ghae %} certain{% endif %} resources on {% data variables.product.product_name %}. When you authenticate to {% data variables.product.product_name %}, you supply or confirm credentials that are unique to you to prove that you are exactly who you declare to be. -Você pode acessar seus recursos em {% data variables.product.product_name %} de várias formas: no navegador, por meio do {% data variables.product.prodname_desktop %} ou outro aplicativo da área de trabalho, com a API ou por meio da linha de comando. Cada forma de acessar o {% data variables.product.product_name %} é compatível com diferentes modos de autenticação. +You can access your resources in {% data variables.product.product_name %} in a variety of ways: in the browser, via {% data variables.product.prodname_desktop %} or another desktop application, with the API, or via the command line. Each way of accessing {% data variables.product.product_name %} supports different modes of authentication. {%- ifversion not fpt %} -- Seu IdP (provedor de identidade){% endif %}{% ifversion not ghae %} -- O nome de usuário e a senha com autenticação de dois fatores{% endif %} -- Token de acesso pessoal -- Chave SSH +- Your identity provider (IdP){% endif %}{% ifversion not ghae %} +- Username and password with two-factor authentication{% endif %} +- {% data variables.product.pat_generic_caps %} +- SSH key -## Efetuar a autenticação no seu navegador +## Authenticating in your browser {% ifversion ghae %} -Você pode se autenticar no {% data variables.product.product_name %} no navegador usando o IdP. Para obter mais informações, confira "[Sobre a autenticação com o logon único do SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)". +You can authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)." {% else %} {% ifversion fpt or ghec %} -Se você for um integrante de um {% data variables.product.prodname_emu_enterprise %}, você irá efetuar a autenticação em {% data variables.product.product_name %} no seu navegador usando seu IdP. Para obter mais informações, confira "[Autenticação como um usuário gerenciado](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" na documentação do {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %} +If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you will authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[Authenticating as a managed user](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} -Se você não for integrante de um {% data variables.product.prodname_emu_enterprise %}, você efetuará a autenticação usando seu nome de usuário e senha do {% data variables.product.prodname_dotcom_the_website %}. Você também pode usar a autenticação de dois fatores e o logon único do SAML, que podem ser exigidos por proprietários da organização e da empresa. +If you're not a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you will authenticate using your {% data variables.product.prodname_dotcom_the_website %} username and password. You may also use two-factor authentication and SAML single sign-on, which can be required by organization and enterprise owners. {% else %} -Você pode efetuar a autenticação no {% data variables.product.product_name %} no seu navegador de diferentes formas. +You can authenticate to {% data variables.product.product_name %} in your browser in a number of ways. {% endif %} -- **Somente nome de usuário e senha** - - Você criará uma senha ao criar sua conta no {% data variables.product.product_name %}. Recomendamos que você use um gerenciador de senhas para gerar uma senha aleatória e única. Para obter mais informações, confira "[Como criar uma senha forte](/github/authenticating-to-github/creating-a-strong-password)". {% ifversion fpt or ghec %} - - Se você não tiver habilitado a 2FA, o {% data variables.product.product_name %} solicitará verificação adicional quando você entrar pela primeira vez usando um dispositivo não reconhecido, como um novo perfil de navegador, um navegador em que os cookies foram excluídos ou um novo computador. +- **Username and password only** + - You'll create a password when you create your account on {% data variables.product.product_name %}. We recommend that you use a password manager to generate a random and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/creating-a-strong-password)."{% ifversion fpt or ghec %} + - If you have not enabled 2FA, {% data variables.product.product_name %} will ask for additional verification when you first sign in from an unrecognized device, such as a new browser profile, a browser where the cookies have been deleted, or a new computer. - Depois de fornecer seu nome de usuário e senha, você será solicitado a fornecer um código de verificação que enviaremos por email. Se você tiver o aplicativo {% data variables.product.prodname_mobile %} instalado, você receberá uma notificação lá. Para obter mais informações, consulte "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)".{% endif %} -- **2FA (autenticação de dois fatores)** (recomendado) - - Se você habilitar a 2FA, depois de inserir com êxito seu nome de usuário e senha, também solicitaremos que você forneça um código gerado por um aplicativo TOTP (Senhas Avulsas por Tempo Limitado) em seu dispositivo móvel{% ifversion fpt or ghec %} ou enviado como uma mensagem de texto (SMS){% endif %}. Para obter mais informações, confira "[Como acessar o {% data variables.product.prodname_dotcom %} usando a autenticação de dois fatores](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)". - - Além da autenticação com um aplicativo TOTP{% ifversion fpt or ghec %} ou uma mensagem de texto{% endif %}, você tem a opção de adicionar um método alternativo de autenticação com {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} ou{% endif %} uma chave de segurança usando WebAuthn. Para obter mais informações, confira {% ifversion fpt or ghec %}"[Como configurar a autenticação de dois fatores com o {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" e {% endif %}"[Como configurar a autenticação de dois fatores usando uma chave de segurança](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)". {% ifversion ghes %} -- **Autenticação externa** - - O administrador do site pode configurar o {% data variables.product.product_location %} para usar uma autenticação externa em vez de um nome de usuário e senha. Para obter mais informações, confira "[Métodos de autenticação externa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)". {% endif %} {% ifversion fpt or ghec %} -- **Logon único do SAML** - - Para acessar recursos pertencentes a uma organização ou conta corporativa que use o logon único do SAML, talvez seja necessário se autenticar também por meio de um IdP. Para obter mais informações, confira "[Sobre a autenticação com o logon único do SAML](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}" na documentação do {% data variables.product.prodname_ghe_cloud %}{% else %}".{% endif %}{% endif %} + After providing your username and password, you will be asked to provide a verification code that we will send to you via email. If you have the {% data variables.product.prodname_mobile %} application installed, you'll receive a notification there instead. For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)."{% endif %} +- **Two-factor authentication (2FA)** (recommended) + - If you enable 2FA, after you successfully enter your username and password, we'll also prompt you to provide a code that's generated by a time-based one time password (TOTP) application on your mobile device{% ifversion fpt or ghec %} or sent as a text message (SMS){% endif %}. For more information, see "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)." + - In addition to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}, you can optionally add an alternative method of authentication with {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} or{% endif %} a security key using WebAuthn. For more information, see {% ifversion fpt or ghec %}"[Configuring two-factor authentication with {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" and {% endif %}"[Configuring two-factor authentication using a security key](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."{% ifversion ghes %} +- **External authentication** + - Your site administrator may configure {% data variables.location.product_location %} to use external authentication instead of a username and password. For more information, see "[External authentication methods](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)."{% endif %}{% ifversion fpt or ghec %} +- **SAML single sign-on** + - Before you can access resources owned by an organization or enterprise account that uses SAML single sign-on, you may need to also authenticate through an IdP. For more information, see "[About authentication with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} {% endif %} -## Efetuar a autenticação com {% data variables.product.prodname_desktop %} -Você pode efetuar a autenticação com o {% data variables.product.prodname_desktop %} usando seu navegador. Para obter mais informações, confira "[Autenticação no {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)". +## Authenticating with {% data variables.product.prodname_desktop %} +You can authenticate with {% data variables.product.prodname_desktop %} using your browser. For more information, see "[Authenticating to {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)." -## Efetuar a autenticação com a API +## Authenticating with the API -Você pode efetuar a autenticação com a API de diferentes formas. +You can authenticate with the API in different ways. -- **Tokens de acesso pessoal** - - Em algumas situações, como, por exemplo, testes, você pode usar um token de acesso pessoal para acessar a API. Usar um token de acesso pessoal permite que você revogue o acesso a qualquer momento. Para obter mais informações, confira "[Como criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)". -- **Fluxo do aplicativo web** - - Para aplicativos OAuth em produção, você deve efetuar a autenticação usando o fluxo do aplicativo web. Para obter mais informações, confira "[Como autorizar aplicativos OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)". -- **Aplicativos GitHub** - - Para aplicativos GitHub em produção, você deve efetuar a autenticação em nome da instalação do aplicativo. Para obter mais informações, confira "[Autenticação com os {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/authenticating-with-github-apps/)". +- **{% data variables.product.pat_generic_caps %}s** + - In limited situations, such as testing, you can use a {% data variables.product.pat_generic %} to access the API. Using a {% data variables.product.pat_generic %} enables you to revoke access at any time. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." +- **Web application flow** + - For OAuth Apps in production, you should authenticate using the web application flow. For more information, see "[Authorizing OAuth Apps](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)." +- **GitHub Apps** + - For GitHub Apps in production, you should authenticate on behalf of the app installation. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/authenticating-with-github-apps/)." -## Efetuando a autenticação com a linha de comando +## Authenticating with the command line -Você pode acessar repositórios no {% data variables.product.product_name %} pela linha de comando de duas maneiras, HTTPS e SSH. Ambos têm uma maneira diferente de efetuar a autenticação. O método de autenticação é determinado com base na escolha de uma URL remota de HTTPS ou SSH quando você clonar o repositório. Para obter mais informações sobre o modo de acesso, confira "[Sobre os repositórios remotos](/github/getting-started-with-github/about-remote-repositories)". +You can access repositories on {% data variables.product.product_name %} from the command line in two ways, HTTPS and SSH, and both have a different way of authenticating. The method of authenticating is determined based on whether you choose an HTTPS or SSH remote URL when you clone the repository. For more information about which way to access, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)." ### HTTPS -Você pode trabalhar com todos os repositórios no {% data variables.product.product_name %} por meio de HTTPS, mesmo que você esteja atrás de um firewall ou proxy. +You can work with all repositories on {% data variables.product.product_name %} over HTTPS, even if you are behind a firewall or proxy. -Se você fizer a autenticação com {% data variables.product.prodname_cli %}, você poderá efetuar a autenticação com um token de acesso pessoal ou por meio do navegador web. Para obter mais informações sobre como se autenticar com a {% data variables.product.prodname_cli %}, confira [`gh auth login`](https://cli.github.com/manual/gh_auth_login). +If you authenticate with {% data variables.product.prodname_cli %}, you can either authenticate with a {% data variables.product.pat_generic %} or via the web browser. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). -Se você efetuar a autenticação sem {% data variables.product.prodname_cli %}, você deverá efetuar a autenticação com um token de acesso pessoal. {% data reusables.user-settings.password-authentication-deprecation %} Sempre que você usar o Git para se autenticar no {% data variables.product.product_name %}, precisará inserir suas credenciais para se autenticar no {% data variables.product.product_name %}, a menos que você armazene em cache com um [auxiliar de credencial](/github/getting-started-with-github/caching-your-github-credentials-in-git). +If you authenticate without {% data variables.product.prodname_cli %}, you must authenticate with a {% data variables.product.pat_generic %}. {% data reusables.user-settings.password-authentication-deprecation %} Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your credentials to authenticate with {% data variables.product.product_name %}, unless you cache them with a [credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git). ### SSH -Você pode trabalhar com todos os repositórios no {% data variables.product.product_name %} por meio de SSH, embora os firewalls e proxys possam se recusar a permitir conexões de SSH. +You can work with all repositories on {% data variables.product.product_name %} over SSH, although firewalls and proxies might refuse to allow SSH connections. -Se você efetuar a autenticação com {% data variables.product.prodname_cli %}, a CLI encontrará chaves públicas SSH no seu computador e solicitará que você selecione uma para upload. Se {% data variables.product.prodname_cli %} não encontrar uma chave pública SSH para o upload, ele poderá gerar um novo SSH público/privado e fazer o upload da chave pública para a sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Em seguida, você pode efetuar a autenticação com um token de acesso pessoal ou por meio do navegador web. Para obter mais informações sobre como se autenticar com a {% data variables.product.prodname_cli %}, confira [`gh auth login`](https://cli.github.com/manual/gh_auth_login). +If you authenticate with {% data variables.product.prodname_cli %}, the CLI will find SSH public keys on your machine and will prompt you to select one for upload. If {% data variables.product.prodname_cli %} does not find a SSH public key for upload, it can generate a new SSH public/private keypair and upload the public key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. Then, you can either authenticate with a {% data variables.product.pat_generic %} or via the web browser. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). -Se você efetuar a autenticação sem {% data variables.product.prodname_cli %}, você deverá gerar um conjunto de chaves pública/privada no seu computador local e adicionar a chave pública à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Para obter mais informações, confira "[Como gerar uma nova chave SSH e adicioná-la ao ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". Sempre que você usar o Git para se autenticar no {% data variables.product.product_name %}, precisará inserir sua frase secreta de chave SSH, a menos que tenha [armazenado a chave](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent). +If you authenticate without {% data variables.product.prodname_cli %}, you will need to generate an SSH public/private keypair on your local machine and add the public key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your SSH key passphrase, unless you've [stored the key](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent). {% ifversion fpt or ghec %} -### Autorizando para logon único SAML +### Authorizing for SAML single sign-on -Para usar um token de acesso pessoal ou uma chave SSH para acessar os recursos que pertencem a uma organização que usa o logon único do SAML, você também deve autorizar o token pessoal ou a chave SSH. Para obter mais informações, confira "[Como autorizar um token de acesso pessoal para uso com o logon único do SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" ou "[Como autorizar uma chave SSH para uso com o logon único do SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" na documentação do {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}{% endif %} +To use a {% data variables.product.pat_generic %} or SSH key to access resources owned by an organization that uses SAML single sign-on, you must also authorize the personal token or SSH key. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} -## Formatos de token de {% data variables.product.company_short %} +## {% data variables.product.company_short %}'s token formats -{% data variables.product.company_short %} emite tokens que começam com um prefixo para indicar o tipo do token. +{% data variables.product.company_short %} issues tokens that begin with a prefix to indicate the token's type. -| Tipo de token | Prefixo | Mais informações | +| Token type | Prefix | More information | | :- | :- | :- | -| Token de acesso pessoal | `ghp_` | "[Como criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)" | -| token de acesso OAuth | `gho_` | "[Como autorizar {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)" | -| Token de usuário para servidor para um {% data variables.product.prodname_github_app %} | `ghu_` | "[Como identificar e autorizar usuários do {% data variables.product.prodname_github_apps %}](/developers/apps/identifying-and-authorizing-users-for-github-apps)" | -| Token de servidor para usuário para {% data variables.product.prodname_github_app %} | `ghs_` | "[Autenticação com os {% data variables.product.prodname_github_apps %}](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)" | -| Atualizar token para um {% data variables.product.prodname_github_app %} | `ghr_` | "[Como atualizar tokens de acesso de usuário para servidor](/developers/apps/refreshing-user-to-server-access-tokens)" | +| {% data variables.product.pat_generic_caps %} | `ghp_` | "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)" | +| OAuth access token | `gho_` | "[Authorizing {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)" | +| User-to-server token for a {% data variables.product.prodname_github_app %} | `ghu_` | "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/developers/apps/identifying-and-authorizing-users-for-github-apps)" | +| Server-to-server token for a {% data variables.product.prodname_github_app %} | `ghs_` | "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)" | +| Refresh token for a {% data variables.product.prodname_github_app %} | `ghr_` | "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)" | diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md index 649fcc4134..9eaad2d5c4 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md @@ -1,6 +1,6 @@ --- -title: Autorizando Aplicativos OAuth -intro: 'Você pode conectar sua identidade do {% data variables.product.product_name %} a aplicativos de terceiros usando o OAuth. Ao autorizar um {% data variables.product.prodname_oauth_app %}, você deve ter certeza de que se trata de um aplicativo confiável, examinar por quem ele foi desenvolvido e analisar os tipos de informação que o aplicativo quer acessar.' +title: Authorizing OAuth Apps +intro: 'You can connect your {% data variables.product.product_name %} identity to third-party applications using OAuth. When authorizing an {% data variables.product.prodname_oauth_app %}, you should ensure you trust the application, review who it''s developed by, and review the kinds of information the application wants to access.' redirect_from: - /articles/authorizing-oauth-apps - /github/authenticating-to-github/authorizing-oauth-apps @@ -13,95 +13,89 @@ versions: topics: - Identity - Access management -ms.openlocfilehash: a6205e33d29170c7ff72ad6f6d6ede45c0145ef6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147423161' --- -Quando um {% data variables.product.prodname_oauth_app %} quer identificá-lo pela sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, você verá uma página com as informações de contato do desenvolvedor do aplicativo e uma lista dos dados específicos que estão sendo solicitados. +When an {% data variables.product.prodname_oauth_app %} wants to identify you by your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, you'll see a page with the app's developer contact information and a list of the specific data that's being requested. {% ifversion fpt or ghec %} {% tip %} -**Dica:** você precisa [verificar seu endereço de email](/articles/verifying-your-email-address) antes de autorizar um {% data variables.product.prodname_oauth_app %}. +**Tip:** You must [verify your email address](/articles/verifying-your-email-address) before you can authorize an {% data variables.product.prodname_oauth_app %}. {% endtip %} {% endif %} -## Acesso do {% data variables.product.prodname_oauth_app %} +## {% data variables.product.prodname_oauth_app %} access -Os {% data variables.product.prodname_oauth_apps %} podem ter acesso de *leitura* ou de *gravação* nos dados do {% data variables.product.product_name %}. +{% data variables.product.prodname_oauth_apps %} can have *read* or *write* access to your {% data variables.product.product_name %} data. -- O **acesso de leitura** só permite que um aplicativo *visualize* seus dados. -- O **acesso de gravação** permite que um aplicativo *altere* seus dados. +- **Read access** only allows an app to *look at* your data. +- **Write access** allows an app to *change* your data. {% tip %} -**Dica:** {% data reusables.user-settings.review_oauth_tokens_tip %} +**Tip:** {% data reusables.user-settings.review_oauth_tokens_tip %} {% endtip %} -### Sobre os escopos do OAuth +### About OAuth scopes -Os *escopos* são grupos de permissões nomeados que um {% data variables.product.prodname_oauth_app %} pode solicitar para acessar dados públicos e privados. +*Scopes* are named groups of permissions that an {% data variables.product.prodname_oauth_app %} can request to access both public and non-public data. -Quando quiser usar um {% data variables.product.prodname_oauth_app %} que se integre ao {% data variables.product.product_name %}, esse app permitirá que você saiba qual tipo de acesso aos seus dados será necessário. Se você conceder acesso ao app, este poderá executar ações em seu nome, como ler ou modificar os dados. Por exemplo, se você quiser usar um aplicativo que solicite o escopo de `user:email`, o aplicativo terá acesso somente leitura aos seus endereços de email privados. Para obter mais informações, confira "[Sobre os escopos dos {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)". +When you want to use an {% data variables.product.prodname_oauth_app %} that integrates with {% data variables.product.product_name %}, that app lets you know what type of access to your data will be required. If you grant access to the app, then the app will be able to perform actions on your behalf, such as reading or modifying data. For example, if you want to use an app that requests `user:email` scope, the app will have read-only access to your private email addresses. For more information, see "[About scopes for {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)." {% tip %} -**Observação:** atualmente, não é possível definir o escopo do acesso ao código-fonte como somente leitura. +**Note:** Currently, you can't scope source code access to read-only. {% endtip %} {% data reusables.apps.oauth-token-limit %} -### Tipos de dados solicitados +### Types of requested data -{% data variables.product.prodname_oauth_apps %} pode solicitar vários tipos de dados. +{% data variables.product.prodname_oauth_apps %} can request several types of data. -| Tipo de dados | Descrição | +| Type of data | Description | | --- | --- | -| Status do commit | Você pode conceder acesso para um app relatar seu status de commit. O acesso ao status do commit permite que os apps determinem se uma compilação foi bem-sucedida em relação a um commit específico. Os apps não terão acesso ao seu código, mas poderão ler e gravar informações de status em relação a um commit específico. | -| Implantações | O acesso ao status da implantação permite que os apps determinem se uma implantação foi bem-sucedida em relação a um commit específico para repositórios públicos e privados. Os apps não terão acesso ao seu código. | -| Gists | O acesso de [gist](https://gist.github.com) permite que os aplicativos leiam ou gravem conteúdo dos seus gists públicos e secretos. | -| Ganchos | O acesso de [webhooks](/webhooks) permite que os aplicativos leiam ou gravem configurações de gancho nos repositórios que você gerencia. | -| Notificações | O acesso à notificação permite que os apps leiam as notificações do {% data variables.product.product_name %}, como comentários sobre problemas ou pull requests. No entanto, os apps continuam sem poder acessar nada nos repositórios. | -| Organizações e equipes | O acesso às organizações e equipes permite que os apps acessem e gerenciem a associação à organização e à equipe. | -| Dados pessoais do usuário | Os dados do usuário incluem informações encontradas no seu perfil de usuário, como nome, endereço de e-mail e localização. | -| Repositórios | As informações de repositório incluem os nomes dos contribuidores, os branches que você criou e os arquivos reais dentro do repositório. Os apps podem solicitar acesso para repositórios públicos ou privados em um nível amplo de usuário. | -| Exclusão de repositório | Os apps podem solicitar a exclusão de repositórios que você administra, mas não terão acesso ao seu código. |{% ifversion projects-oauth-scope %} -| Projetos | Acesso {% data variables.projects.projects_v2 %} de usuário e da organização. Os aplicativos podem solicitar acesso de leitura/gravação ou somente leitura. |{% endif %} +| Commit status | You can grant access for an app to report your commit status. Commit status access allows apps to determine if a build is a successful against a specific commit. Apps won't have access to your code, but they can read and write status information against a specific commit. | +| Deployments | Deployment status access allows apps to determine if a deployment is successful against a specific commit for public and private repositories. Apps won't have access to your code. | +| Gists | [Gist](https://gist.github.com) access allows apps to read or write to both your public and secret Gists. | +| Hooks | [Webhooks](/webhooks) access allows apps to read or write hook configurations on repositories you manage. | +| Notifications | Notification access allows apps to read your {% data variables.product.product_name %} notifications, such as comments on issues and pull requests. However, apps remain unable to access anything in your repositories. | +| Organizations and teams | Organization and teams access allows apps to access and manage organization and team membership. | +| Personal user data | User data includes information found in your user profile, like your name, e-mail address, and location. | +| Repositories | Repository information includes the names of contributors, the branches you've created, and the actual files within your repository. Apps can request access for either public or private repositories on a user-wide level. | +| Repository delete | Apps can request to delete repositories that you administer, but they won't have access to your code. |{% ifversion projects-oauth-scope %} +| Projects | Access to user and organization {% data variables.projects.projects_v2 %}. Apps can request either read/write or read only access. |{% endif %} -## Solicitar permissões atualizadas +## Requesting updated permissions -Quando {% data variables.product.prodname_oauth_apps %} solicitar novas permissões de acesso, você será notificado sobre as diferenças entre as permissões atuais e as novas permissões. +When {% data variables.product.prodname_oauth_apps %} request new access permissions, they will notify you of the differences between their current permissions and the new permissions. {% ifversion fpt or ghec %} -## {% data variables.product.prodname_oauth_apps %} e organizações +## {% data variables.product.prodname_oauth_apps %} and organizations -Quando você autoriza {% data variables.product.prodname_oauth_app %} para sua conta pessoal, também verá como essa autorização afetará cada organização da qual você é membro. +When you authorize an {% data variables.product.prodname_oauth_app %} for your personal account, you'll also see how the authorization will affect each organization you're a member of. -- **Para as organizações *com* restrições de acesso do {% data variables.product.prodname_oauth_app %}, você pode solicitar que os administradores da organização aprovem o aplicativo para uso nessa organização.** Se a organização não aprovar o aplicativo, o aplicativo só poderá acessar os recursos públicos da organização. Se você for um administrador da organização, poderá [aprovar o aplicativo](/articles/approving-oauth-apps-for-your-organization) por conta própria. +- **For organizations *with* {% data variables.product.prodname_oauth_app %} access restrictions, you can request that organization admins approve the application for use in that organization.** If the organization does not approve the application, then the application will only be able to access the organization's public resources. If you're an organization admin, you can [approve the application](/articles/approving-oauth-apps-for-your-organization) yourself. -- **Para as organizações *sem* restrições de acesso do {% data variables.product.prodname_oauth_app %}, o aplicativo será autorizado automaticamente para acesso aos recursos dessa organização.** Por esse motivo, você deve ter cuidado com quais {% data variables.product.prodname_oauth_apps %} você aprova para acesso aos recursos da sua conta pessoal, bem como a todos os recursos da organização. +- **For organizations *without* {% data variables.product.prodname_oauth_app %} access restrictions, the application will automatically be authorized for access to that organization's resources.** For this reason, you should be careful about which {% data variables.product.prodname_oauth_apps %} you approve for access to your personal account resources as well as any organization resources. -Se você pertence a alguma organização que force o logon único SAML, você deve ter uma sessão de SAML ativa para cada organização toda cada vez que autorizar um {% data variables.product.prodname_oauth_app %}. +If you belong to any organizations that enforce SAML single sign-on, you must have an active SAML session for each organization each time you authorize an {% data variables.product.prodname_oauth_app %}. {% note %} -**Observação:** se você está encontrando erros de autenticação em uma organização que impõe o logon único do SAML, talvez seja necessário revogar o Aplicativo OAuth na [página de configurações da sua conta](https://github.com/settings/applications) e repetir o fluxo de autenticação para autorizar o aplicativo de novo. +**Note:** If you are encountering errors authenticating to an organization that enforces SAML single sign-on, you may need to revoke the OAuth App from your [account settings page](https://github.com/settings/applications) and repeat the authentication flow to reauthorize the app. {% endnote %} -## Leitura adicional +## Further reading -- "[Sobre as restrições de acesso do {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)" -- "[Como autorizar Aplicativos do GitHub](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)" -- "[Suporte ao {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-support)" +- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)" +- "[Authorizing GitHub Apps](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)" +- "[{% data variables.product.prodname_marketplace %} support](/articles/github-marketplace-support)" {% endif %} diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md index 1fe1504849..88febb34fe 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md @@ -1,6 +1,6 @@ --- -title: Criando um token de acesso pessoal -intro: Você pode criar um token de acesso pessoal para usar no lugar de uma senha com a linha de comando ou com a API. +title: Creating a personal access token +intro: You can create a {% data variables.product.pat_generic %} to use in place of a password with the command line or with the API. redirect_from: - /articles/creating-an-oauth-token-for-command-line-use - /articles/creating-an-access-token-for-command-line-use @@ -17,60 +17,131 @@ versions: topics: - Identity - Access management -shortTitle: Create a PAT -ms.openlocfilehash: 437e06ba2fdf82252702106600ac6da73ee4c792 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147064423' +shortTitle: Create a {% data variables.product.pat_generic %} --- -{% note %} -**Observações:** +{% warning %} -- se você usar a {% data variables.product.prodname_cli %} para se autenticar no {% data variables.product.product_name %} na linha de comando, ignore a geração de um token de acesso pessoal e se autentique pelo navegador da Web. Para obter mais informações sobre como se autenticar com a {% data variables.product.prodname_cli %}, confira [`gh auth login`](https://cli.github.com/manual/gh_auth_login). -- [O Gerenciador de Credenciais do Git](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md) é uma alternativa segura e multiplataforma ao uso de PATs (tokens de acesso pessoal) e elimina a necessidade de gerenciar o escopo e a validade do PAT. Para obter instruções de instalação, confira [Baixar e instalar](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md#download-and-install) no repositório GitCredentialManager/git-credential-manager. +**Warning**: Treat your access tokens like passwords. -{% endnote %} +To access {% data variables.product.company_short %} from the command line, consider using {% data variables.product.prodname_cli %} or [Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md) instead of creating a {% data variables.product.pat_generic %}. -Os PATs (tokens de acesso pessoal) são uma alternativa ao uso de senhas para autenticação no {% data variables.product.product_name %} ao usar a [API do GitHub](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) ou a [linha de comando](#using-a-token-on-the-command-line). +When using a {% data variables.product.pat_generic %} in a script, consider storing your token as a secret and running your script through {% data variables.product.prodname_actions %}. For more information, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."{%- ifversion ghec or fpt %} You can also store your token as a {% data variables.product.prodname_codespaces %} secret and run your script in {% data variables.product.prodname_codespaces %}. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."{% endif %} -{% ifversion fpt or ghec %}Caso deseje usar um PAT para acessar os recursos pertencentes a uma organização que usa o SSO do SAML, você precisa autorizar o PAT. Para obter mais informações, confira "[Sobre a autenticação com o logon único do SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" e "[Como autorizar um token de acesso pessoal para uso com o logon único do SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" na documentação do {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}{% endif %} +If these options are not possible, consider using another service such as [the 1Password CLI](https://developer.1password.com/docs/cli/secret-references/) to store your token securely. + +{% endwarning %} + +## About {% data variables.product.pat_generic %}s + +{% data variables.product.pat_generic_caps %} are an alternative to using passwords for authentication to {% data variables.product.product_name %} when using the [GitHub API](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) or the [command line](#using-a-token-on-the-command-line). {% data variables.product.pat_generic_caps %}s are intended to access {% data variables.product.company_short %} resources on behalf of yourself. To access resources on behalf of an organization, or for long-lived integrations, you should use a {% data variables.product.prodname_github_app %}. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)." + +{% ifversion pat-v2 %} + +{% data variables.product.company_short %} currently supports two types of {% data variables.product.pat_generic %}s: {% data variables.product.pat_v2 %}s and {% data variables.product.pat_v1_plural %}. {% data variables.product.company_short %} recommends that you use {% data variables.product.pat_v2 %}s instead of {% data variables.product.pat_v1_plural %} whenever possible. {% data variables.product.pat_v2_caps %}s have several security advantages over {% data variables.product.pat_v1_plural %}: + +- Each token can only access resources owned by a single user or organization. +- Each token can only access specific repositories. +- Each token is granted specific permissions, which offer more control than the scopes granted to {% data variables.product.pat_v1_plural %}. +- Each token must have an expiration date. +- Organization owners can require approval for any {% data variables.product.pat_v2 %}s that can access resources in the organization.{% ifversion ghec or ghes or ghae %} +- Enterprise owners can require approval for any {% data variables.product.pat_v2 %}s that can access resources in organizations owned by the enterprise.{% endif %} + +Additionally, organization owners can restrict the access of {% data variables.product.pat_v1 %} to their organization{% ifversion ghec or ghes or ghae %}, and enterprise owners can restrict the access of {% data variables.product.pat_v1 %} to the enterprise or organizations owned by the enterprise{% endif %}. + +{% data reusables.user-settings.patv2-limitations %} + +{% endif %} {% ifversion fpt or ghec %}{% data reusables.user-settings.removes-personal-access-tokens %}{% endif %} -Um token com nenhum escopo atribuído só pode acessar informações públicas. Para usar seu token para acessar os repositórios na linha de comando, selecione `repo`. Para obter mais informações, confira "[Escopos disponíveis](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)". +{% ifversion pat-v2 %} -## Criar um token +## Creating a {% data variables.product.pat_v2 %} -{% ifversion fpt or ghec %}1. [Verifique seu endereço de email](/github/getting-started-with-github/verifying-your-email-address), caso ele ainda não tenha sido verificado.{% endif %} {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.personal_access_tokens %} {% data reusables.user-settings.generate_new_token %} -5. Dê ao seu token um nome descritivo. - ![Campo de descrição do token](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae or ghec %} -6. Para dar uma validade ao token, selecione o menu suspenso **Validade** e clique em um padrão ou use o seletor de calendário. - ![Campo de validade do token](/assets/images/help/settings/token_expiration.png){% endif %} -7. Selecione os escopos, ou as permissões, aos quais deseja conceder esse token. Para usar o token para acessar os repositórios na linha de comando, selecione **repositório**. - {% ifversion fpt or ghes or ghec %} ![Seleção de escopos de token](/assets/images/help/settings/token_scopes.gif) {% elsif ghae %} ![Seleção de escopos de token](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png) {% endif %} -8. Clique em **Gerar token**. - ![Botão Gerar token](/assets/images/help/settings/generate_token.png) {% ifversion fpt or ghec %} ![Token recém-criado](/assets/images/help/settings/personal_access_tokens.png) {% elsif ghes or ghae %} ![Token recém-criado](/assets/images/help/settings/personal_access_tokens_ghe.png) {% else %} ![Token recém-criado](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png) {% endif %} {% warning %} +{% note %} - **Aviso:** trate seus tokens como senhas e mantenha-os em segredo. Ao trabalhar com a API, use tokens como variáveis de ambiente em vez de embuti-los em código nos seus programas. +**Note**: {% data reusables.user-settings.pat-v2-beta %} - {% endwarning %} +{% endnote %} -{% ifversion fpt or ghec %}9. Para usar seu token para efetuar a autenticação em uma organização que usa o logon único SAML, autorize o token. Para obter mais informações, confira "[Como autorizar um token de acesso pessoal para uso com o logon único do SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" na documentação do {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}{% endif %} +{% ifversion fpt or ghec %}1. [Verify your email address](/github/getting-started-with-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %} +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Fine-grained tokens**. +1. Click **Generate new token**. +1. Optionally, under **Token name**, enter a name for the token. +1. Under **Expiration**, select an expiration for the token. +1. Optionally, under **Description**, add a note to describe the purpose of the token. +1. Under **Resource owner**, select a resource owner. The token will only be able to access resources owned by the selected resource owner. Organizations that you are a member of will not appear unless the organization opted in to {% data variables.product.pat_v2 %}s. For more information, see "[Setting a {% data variables.product.pat_generic %} policy for your organization](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization)."{% ifversion ghec or ghae %} You may be required to perform SAML single sign-on (SSO) if the selected organization requires it and you do not already have an active SAML session.{% endif %} +1. Optionally, if the resource owner is an organization that requires approval for {% data variables.product.pat_v2 %}s, below the resource owner, in the box, enter a justification for the request. +1. Under **Repository access**, select which repositories you want the token to access. You should choose the minimal repository access that meets your needs. Tokens always include read-only access to all public repositories on GitHub. +1. If you selected **Only select repositories** in the previous step, under the **Selected repositories** dropdown, select the repositories that you want the token to access. +1. Under **Permissions**, select which permissions to grant the token. Depending on which resource owner and which repository access you specified, there are repository, organization, and account permissions. You should choose the minimal permissions necessary for your needs. For more information about what permissions are required for each REST API operation, see "[Permissions required for {% data variables.product.pat_v2 %}s](/rest/overview/permissions-required-for-fine-grained-personal-access-tokens)." +1. Click **Generate token**. -## Usar um token na linha de comando +If you selected an organization as the resource owner and the organization requires approval for {% data variables.product.pat_v2 %}s, then your token will be marked as `pending` until it is reviewed by an organization administrator. Your token will only be able to read public resources until it is approved. If you are an owner of the organization, your request is automatically approved. For more information, see "[Reviewing and revoking {% data variables.product.pat_generic %}s in your organization](/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization)". + +{% endif %} + +## Creating a {% data variables.product.pat_v1 %} + +{% ifversion pat-v2 %} + +{% note %} + +**Note**: Organization owners can restrict the access of {% data variables.product.pat_v1 %} to their organization. If you try to use a {% data variables.product.pat_v1 %} to access resources in an organization that has disabled {% data variables.product.pat_v1 %} access, your request will fail with a 403 response. Instead, you must use a {% data variables.product.prodname_github_app %}, {% data variables.product.prodname_oauth_app %}, or {% data variables.product.pat_v2 %}. + +{% endnote %} + +{% endif %} + +{% ifversion pat-v2 %} + +{% warning %} + +**Note**: Your {% data variables.product.pat_v1 %} can access every repository that you can access. {% data variables.product.company_short %} recommends that you use {% data variables.product.pat_v2 %}s instead, which you can restrict to specific repositories. {% data variables.product.pat_v2_caps %}s also enable you to specify fine-grained permissions instead of broad scopes. + +{% endwarning %} + +{% endif %} + +{% ifversion fpt or ghec %}1. [Verify your email address](/github/getting-started-with-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %} +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% ifversion pat-v2 %}1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Tokens (classic)**.{% else %}{% data reusables.user-settings.personal_access_tokens %}{% endif %} +{% ifversion pat-v2%}1. Select **Generate new token**, then click **Generate new token (classic)**.{% else %}{% data reusables.user-settings.generate_new_token %}{% endif %} +5. Give your token a descriptive name. + ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae or ghec %} +6. To give your token an expiration, select the **Expiration** drop-down menu, then click a default or use the calendar picker. + ![Token expiration field](/assets/images/help/settings/token_expiration.png){% endif %} +7. Select the scopes you'd like to grant this token. To use your token to access repositories from the command line, select **repo**. A token with no assigned scopes can only access public information. For more information, see "[Available scopes](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)". + {% ifversion fpt or ghes or ghec %} + ![Selecting token scopes](/assets/images/help/settings/token_scopes.gif) + {% elsif ghae %} + ![Selecting token scopes](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png) + {% endif %} +8. Click **Generate token**. + ![Generate token button](/assets/images/help/settings/generate_token.png) + {% ifversion fpt or ghec %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens.png) + {% elsif ghes or ghae %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe.png) + {% else %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png){% endif %}{% ifversion fpt or ghec %} +1. To use your token to access resources owned by an organization that uses SAML single sign-on, authorize the token. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} + +## Using a token on the command line {% data reusables.command_line.providing-token-as-password %} -Os tokens de acesso pessoais podem ser usados apenas para operações Git HTTPS. Se o repositório usar uma URL remota SSH, você precisará [alternar o repositório remoto de SSH para HTTPS](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-ssh-to-https). +{% data variables.product.pat_generic_caps %}s can only be used for HTTPS Git operations. If your repository uses an SSH remote URL, you will need to [switch the remote from SSH to HTTPS](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-ssh-to-https). -Se não for solicitado a informar seu nome de usuário e a senha, suas credenciais poderão ser armazenadas em cache no seu computador. Você pode [atualizar suas credenciais no conjunto de chaves](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain) para substituir sua senha antiga pelo token. +If you are not prompted for your username and password, your credentials may be cached on your computer. You can [update your credentials in the Keychain](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain) to replace your old password with the token. -Em vez de inserir manualmente seu PAT para cada operação de HTTPS do Git, você pode armazenar seu PAT com um cliente Git. O Git irá armazenar temporariamente as suas credenciais na memória até que um intervalo de expiração tenha passado. Você também pode armazenar o token em um arquivo de texto simples que o Git pode ler antes de cada solicitação. Para obter mais informações, confira "[Como armazenar em cache suas credenciais do {% data variables.product.prodname_dotcom %} no Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)". +Instead of manually entering your {% data variables.product.pat_generic %} for every HTTPS Git operation, you can cache your {% data variables.product.pat_generic %} with a Git client. Git will temporarily store your credentials in memory until an expiry interval has passed. You can also store the token in a plain text file that Git can read before every request. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)." -## Leitura adicional +## Further reading -- "[Sobre a autenticação no GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %} -- "[Expiração e revogação de um token](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} +- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %} +- "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md index c97931021c..758beda311 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md @@ -1,6 +1,6 @@ --- -title: Criar uma senha forte -intro: 'Proteja sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} com uma senha forte e única usando um gerenciador de senhas.' +title: Creating a strong password +intro: 'Secure your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} with a strong and unique password using a password manager.' redirect_from: - /articles/what-is-a-strong-password - /articles/creating-a-strong-password @@ -14,31 +14,25 @@ topics: - Identity - Access management shortTitle: Create a strong password -ms.openlocfilehash: 97473f9b04c8d033471f89cac9a0b0d08bebcba3 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145083633' --- -Você deve escolher ou gerar uma senha para a sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} que seja pelo menos: -- {% ifversion ghes %}Sete{% else %}Oito{% endif %} caracteres, se ele incluir um número e uma letra minúscula, ou -- 15 caracteres em qualquer combinação +You must choose or generate a password for your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} that is at least: +- {% ifversion ghes %}Seven{% else %}Eight{% endif %} characters long, if it includes a number and a lowercase letter, or +- 15 characters long with any combination of characters -Para manter sua conta protegida, é recomendável seguir estas práticas recomendadas: -- Use um gerenciador de senhas como o [LastPass](https://lastpass.com/) ou o [1Password](https://1password.com/) para gerar uma senha de, no mínimo, 15 caracteres. -- Gere uma senha exclusiva para o {% data variables.product.product_name %}. Se você usar sua senha {% data variables.product.product_name %} em outro lugar e o serviço estiver comprometido, os invasores ou outros atores maliciosos poderiam usar essa informação para acessar sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. +To keep your account secure, we recommend you follow these best practices: +- Use a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/), to generate a password of at least 15 characters. +- Generate a unique password for {% data variables.product.product_name %}. If you use your {% data variables.product.product_name %} password elsewhere and that service is compromised, then attackers or other malicious actors could use that information to access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. -- Configure a autenticação de dois fatores para sua conta pessoal. Para obter mais informações, confira "[Sobre a autenticação de dois fatores](/articles/about-two-factor-authentication)". -- Nunca compartilhe sua senha, mesmo com um possível colaborador. Cada pessoa deve usar a própria conta pessoal no {% data variables.product.product_name %}. Para obter mais informações sobre as formas de colaboração, confira: "[Como convidar colaboradores para um repositório pessoal](/articles/inviting-collaborators-to-a-personal-repository)", "[Sobre os modelos de desenvolvimento colaborativos](/articles/about-collaborative-development-models/)" ou "[Como colaborar com grupos em organizações](/organizations/collaborating-with-groups-in-organizations/)". +- Configure two-factor authentication for your personal account. For more information, see "[About two-factor authentication](/articles/about-two-factor-authentication)." +- Never share your password, even with a potential collaborator. Each person should use their own personal account on {% data variables.product.product_name %}. For more information on ways to collaborate, see: "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)," "[About collaborative development models](/articles/about-collaborative-development-models/)," or "[Collaborating with groups in organizations](/organizations/collaborating-with-groups-in-organizations/)." {% data reusables.repositories.blocked-passwords %} -Você só pode usar sua senha para entrar no {% data variables.product.product_name %} usando seu navegador. Ao efetuar a autenticação no {% data variables.product.product_name %} de outra forma, como, por exemplo, linha de comando ou API, você deve usar outras credenciais. Para obter mais informações, confira "[Sobre a autenticação no {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)". +You can only use your password to log on to {% data variables.product.product_name %} using your browser. When you authenticate to {% data variables.product.product_name %} with other means, such as the command line or API, you should use other credentials. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)." {% ifversion fpt or ghec %}{% data reusables.user-settings.password-authentication-deprecation %}{% endif %} -## Leitura adicional +## Further reading -- "[Como armazenar em cache suas credenciais do {% data variables.product.product_name %} no Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)" -- "[Como manter sua conta e seus dados seguros](/articles/keeping-your-account-and-data-secure/)" +- "[Caching your {% data variables.product.product_name %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)" +- "[Keeping your account and data secure](/articles/keeping-your-account-and-data-secure/)" diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/index.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/index.md index 94187c2bc3..3e202cd327 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/index.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/index.md @@ -1,6 +1,6 @@ --- -title: Proteger sua conta e dados -intro: 'Para proteger suas informações pessoais, você deve manter a sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} e todos os dados associados à sua conta protegidos.' +title: Keeping your account and data secure +intro: 'To protect your personal information, you should keep both your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} and any associated data secure.' redirect_from: - /articles/keeping-your-account-and-data-secure - /github/authenticating-to-github/keeping-your-account-and-data-secure @@ -33,11 +33,5 @@ children: - /sudo-mode - /preventing-unauthorized-access shortTitle: Account security -ms.openlocfilehash: 39ccc832d4584952bc03cd484cfe72080ccfaa18 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145083631' --- diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md index 67b78ff696..a0bcd546ee 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md @@ -1,6 +1,6 @@ --- -title: Impedir acesso não autorizado -intro: 'Você pode receber alertas sobre incidentes de segurança na mídia, como a descoberta do [bug Heartbleed](http://heartbleed.com/), ou seu computador pode ser roubado enquanto você está conectado ao {% data variables.product.product_location %}. Em casos assim, alterar a sua senha previne acessos futuros indesejados em sua conta e projetos.' +title: Preventing unauthorized access +intro: 'You may be alerted to a security incident in the media, such as the discovery of the [Heartbleed bug](http://heartbleed.com/), or your computer could be stolen while you''re signed in to {% data variables.location.product_location %}. In such cases, changing your password prevents any unintended future access to your account and projects.' redirect_from: - /articles/preventing-unauthorized-access - /github/authenticating-to-github/preventing-unauthorized-access @@ -13,24 +13,18 @@ topics: - Identity - Access management shortTitle: Unauthorized access -ms.openlocfilehash: 2b7a29ad3df05ef758c82330f24fe7568e137130 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145083629' --- -O {% data variables.product.product_name %} solicita uma senha para executar ações confidenciais, como adicionar novas chaves SSH, autorizar aplicativos ou modificar os integrantes da equipe. +{% data variables.product.product_name %} requires a password to perform sensitive actions, such as adding new SSH keys, authorizing applications, or modifying team members. -Depois de alterar sua senha, você deve executar estas ações para confirmar que sua conta está segura: +After changing your password, you should perform these actions to make sure that your account is secure: -- [Habilite a autenticação de dois fatores](/articles/about-two-factor-authentication) na sua conta para que o acesso exija mais do que apenas uma senha. -- [Revise suas chaves SSH](/articles/reviewing-your-ssh-keys), [chaves de implantação](/articles/reviewing-your-deploy-keys) e [integrações autorizadas](/articles/reviewing-your-authorized-integrations) e revogue o acesso não autorizado ou desconhecido nas configurações de SSH e Aplicativos. +- [Enable two-factor authentication](/articles/about-two-factor-authentication) on your account so that access requires more than just a password. +- [Review your SSH keys](/articles/reviewing-your-ssh-keys), [deploy keys](/articles/reviewing-your-deploy-keys), and [authorized integrations](/articles/reviewing-your-authorized-integrations) and revoke unauthorized or unfamiliar access in your SSH and Applications settings. {% ifversion fpt or ghec %} -- [Verifique todos os seus endereços de email](/articles/verifying-your-email-address). Se um invasor adicionou o endereço de e-mail dele à sua conta, isso pode permitir que ele force uma reinicialização de senha indesejada. +- [Verify all your email addresses](/articles/verifying-your-email-address). If an attacker added their email address to your account, it could allow them to force an unintended password reset. {% endif %} -- [Revise o log de segurança da sua conta](/github/authenticating-to-github/reviewing-your-security-log). O histórico apresenta uma uma visão geral sobre várias configurações feitas em seus repositórios. Por exemplo, você pode confirmar que nenhum repositório privado se tornou público ou foi transferido. -- [Revise os webhooks](/articles/creating-webhooks) nos seus repositórios. Os webhooks podem permitir que um invasor intercepte pushes feitos em seu repositório. -- [Garanta que nenhuma nova chave de implantação](/guides/managing-deploy-keys/#deploy-keys) seja criada. Isso poderia habilitar o acesso de servidores externos em seus projetos. -- Revise os commits recentes feitos em seus repositórios. -- Revise a lista de colaboradores de cada repositório. +- [Review your account's security log](/github/authenticating-to-github/reviewing-your-security-log). This provides an overview on various configurations made to your repositories. For example, you can ensure that no private repositories were turned public, or that no repositories were transferred. +- [Review the webhooks](/articles/creating-webhooks) on your repositories. Webhooks could allow an attacker to intercept pushes made to your repository. +- [Make sure that no new deploy keys](/guides/managing-deploy-keys/#deploy-keys) were created. This could enable outside servers access to your projects. +- Review recent commits made to your repositories. +- Review the list of collaborators for each repository. diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md index 1150f65113..1f4dc55b3f 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md @@ -1,6 +1,6 @@ --- -title: Remover dados confidenciais de um repositório -intro: 'Se você fizer commit de dados confidenciais, como uma senha ou chave SSH em um repositório Git, poderá removê-los do histórico. Para remover completamente arquivos indesejados do histórico de um repositório, você pode usar a ferramenta `git filter-repo` ou a ferramenta de código aberto BFG Repo-Cleaner.' +title: Removing sensitive data from a repository +intro: 'If you commit sensitive data, such as a password or SSH key into a Git repository, you can remove it from the history. To entirely remove unwanted files from a repository''s history you can use either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool.' redirect_from: - /remove-sensitive-data - /removing-sensitive-data @@ -17,88 +17,86 @@ topics: - Identity - Access management shortTitle: Remove sensitive data -ms.openlocfilehash: 4c93f372f1d537fd94f06e66986e53d6641923d2 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145083627' --- -A ferramenta `git filter-repo` e o BFG Repo-Cleaner reescrevem o histórico do repositório, o que altera os SHAs dos commits existentes alterados por você e todos os commits dependentes. Os SHAs de commits alterados podem afetar as solicitações de pull abertas no repositório. Recomendamos mesclar ou fechar todas as solicitações de pull abertas antes de remover arquivos do repositório. +The `git filter-repo` tool and the BFG Repo-Cleaner rewrite your repository's history, which changes the SHAs for existing commits that you alter and any dependent commits. Changed commit SHAs may affect open pull requests in your repository. We recommend merging or closing all open pull requests before removing files from your repository. -Você pode remover o arquivo do último commit com `git rm`. Para obter informações sobre como remover um arquivo que foi adicionado com o commit mais recente, confira "[Sobre arquivos grandes no {% data variables.product.prodname_dotcom %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github#removing-files-from-a-repositorys-history)". +You can remove the file from the latest commit with `git rm`. For information on removing a file that was added with the latest commit, see "[About large files on {% data variables.product.prodname_dotcom %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github#removing-files-from-a-repositorys-history)." {% warning %} -**Aviso**: este artigo diz a você como tornar commits com dados confidenciais inacessíveis a partir de quaisquer branches ou tags do seu repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. No entanto, esses commits talvez ainda possam ser acessados em clones ou bifurcações do repositório diretamente por meio de hashes SHA-1 em visualizações em cache no {% data variables.product.product_name %} e por meio de qualquer pull request que faça referência a eles. Não é possível remover dados confidenciais dos clones ou bifurcações de usuários do seu repositório, mas você pode remover permanentemente as visualizações e referências em cache para os dados confidenciais em pull requests no {% data variables.product.product_name %} entrando em contato com {% data variables.contact.contact_support %}. +**Warning**: This article tells you how to make commits with sensitive data unreachable from any branches or tags in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. However, those commits may still be accessible in any clones or forks of your repository, directly via their SHA-1 hashes in cached views on {% data variables.product.product_name %}, and through any pull requests that reference them. You cannot remove sensitive data from other users' clones of your repository, but you can permanently remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %} by contacting {% data variables.contact.contact_support %}. -**Depois de efetuar push de um commit para o {% data variables.product.product_name %}, você deverá considerar todos os dados confidenciais no commit comprometido.** Se você tiver efetuado commit de uma senha, altere-a. Se tiver feito commit de uma chave, crie outra. A remoção dos dados comprometidos não resolve sua exposição inicial, especialmente em clones ou bifurcações existentes do seu repositório. Considere essas limitações ao tomar a decisão de reescrever a história do repositório. +If the commit that introduced the sensitive data exists in any forks of your repository, it will continue to be accessible, unless the fork owner removes the sensitive data from their fork or deletes the fork entirely. + +Once you have pushed a commit to {% data variables.product.product_name %}, you should consider any sensitive data in the commit compromised. If you have committed a password, you should change it. If you have committed a key, generate a new one. Removing the compromised data doesn't resolve its initial exposure, especially in existing clones or forks of your repository. + +Consider these limitations in your decision to rewrite your repository's history. {% endwarning %} -## Remover um arquivo do histórico do repositório +## Purging a file from your repository's history -Você pode limpar um arquivo do histórico do repositório usando a ferramenta `git filter-repo` ou a ferramenta de código aberto BFG Repo-Cleaner. +You can purge a file from your repository's history using either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool. -### Usar o BFG +### Using the BFG -O [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) é uma ferramenta criada e mantida pela comunidade de código aberto. Ele fornece uma alternativa mais rápida e simples ao `git filter-branch` para remover dados indesejados. +The [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) is a tool that's built and maintained by the open source community. It provides a faster, simpler alternative to `git filter-branch` for removing unwanted data. -Por exemplo: para remover o arquivo com dados confidenciais sem alterar o commit mais recente, execute: +For example, to remove your file with sensitive data and leave your latest commit untouched, run: ```shell -$ bfg --delete-files YOUR-FILE-WITH-SENSITIVE-DATA +$ bfg --delete-files YOUR-FILE-WITH-SENSITIVE-DATA ``` -Para substituir todo o texto listado em `passwords.txt` em todas as ocorrências no histórico do repositório, execute: +To replace all text listed in `passwords.txt` wherever it can be found in your repository's history, run: ```shell $ bfg --replace-text passwords.txt ``` -Depois que os dados confidenciais são removidos, você deve fazer push forçado das suas alterações para {% data variables.product.product_name %}. Fazer push forçado reescreve o histórico do repositório, o que remove dados confidenciais do histórico de commit. Se você fizer push forçado, isso poderá pode sobrescrever commits nos quais outras pessoas basearam o seu trabalho. +After the sensitive data is removed, you must force push your changes to {% data variables.product.product_name %}. Force pushing rewrites the repository history, which removes sensitive data from the commit history. If you force push, it may overwrite commits that other people have based their work on. ```shell $ git push --force ``` -Confira a documentação do [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) para obter instruções completas de uso e download. +See the [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/)'s documentation for full usage and download instructions. -### Usando arquivo git filter-repo +### Using git filter-repo {% warning %} -**Aviso:** se você executar `git filter-repo` após fazer stash das alterações, não poderá recuperar as alterações com outros comandos de stash. Antes de executar `git filter-repo`, é recomendado cancelar o stash das alterações feitas. Para cancelar o stash do último conjunto de alterações com stash, execute `git stash show -p | git apply -R`. Para obter mais informações, confira [Ferramentas do Git – Stash e limpeza](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning). +**Warning:** If you run `git filter-repo` after stashing changes, you won't be able to retrieve your changes with other stash commands. Before running `git filter-repo`, we recommend unstashing any changes you've made. To unstash the last set of changes you've stashed, run `git stash show -p | git apply -R`. For more information, see [Git Tools - Stashing and Cleaning](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning). {% endwarning %} -Para ilustrar como o `git filter-repo` funciona, mostraremos como remover o arquivo que contém dados confidenciais do histórico do repositório e adicioná-lo ao `.gitignore` para garantir que ele não sofra um novo commit acidental. +To illustrate how `git filter-repo` works, we'll show you how to remove your file with sensitive data from the history of your repository and add it to `.gitignore` to ensure that it is not accidentally re-committed. -1. Instale a última versão da ferramenta [git filter-repo](https://github.com/newren/git-filter-repo). Você pode instalar o `git-filter-repo` manualmente ou usando um gerenciador de pacotes. Por exemplo, para instalar a ferramenta com HomeBrew, use o comando `brew install`. +1. Install the latest release of the [git filter-repo](https://github.com/newren/git-filter-repo) tool. You can install `git-filter-repo` manually or by using a package manager. For example, to install the tool with HomeBrew, use the `brew install` command. ``` brew install git-filter-repo ``` - Para obter mais informações, confira [*INSTALL.md*](https://github.com/newren/git-filter-repo/blob/main/INSTALL.md) no repositório `newren/git-filter-repo`. + For more information, see [*INSTALL.md*](https://github.com/newren/git-filter-repo/blob/main/INSTALL.md) in the `newren/git-filter-repo` repository. -2. Se você ainda não tem uma cópia local do repositório que contém dados confidenciais no histórico, [clone o repositório](/articles/cloning-a-repository/) no computador local. +2. If you don't already have a local copy of your repository with sensitive data in its history, [clone the repository](/articles/cloning-a-repository/) to your local computer. ```shell - $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY - > Initialized empty Git repository in /Users/YOUR-FILE-PATH/YOUR-REPOSITORY/.git/ + $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY + > Initialized empty Git repository in /Users/YOUR-FILE-PATH/YOUR-REPOSITORY/.git/ > remote: Counting objects: 1301, done. > remote: Compressing objects: 100% (769/769), done. > remote: Total 1301 (delta 724), reused 910 (delta 522) > Receiving objects: 100% (1301/1301), 164.39 KiB, done. > Resolving deltas: 100% (724/724), done. ``` -3. Navegue até o diretório de trabalho do repositório. +3. Navigate into the repository's working directory. ```shell - $ cd YOUR-REPOSITORY + $ cd YOUR-REPOSITORY ``` -4. Execute o comando a seguir, substituindo `PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA` pelo **caminho para o arquivo que deseja remover, não apenas o nome do arquivo**. Esses argumentos vão: - - Forçar o Git a processar todo o histórico de cada branch e marca, mas não fazer check-out - - Remover o arquivo especificado, bem como todos os commits vazios gerados como resultado - - Remova algumas configurações, como a URL remota, armazenada no arquivo *.git/config*. É interessante fazer backup desse arquivo antes para que ele possa ser restaurado mais tarde. - - **Substituir as marcas existentes** +4. Run the following command, replacing `PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA` with the **path to the file you want to remove, not just its filename**. These arguments will: + - Force Git to process, but not check out, the entire history of every branch and tag + - Remove the specified file, as well as any empty commits generated as a result + - Remove some configurations, such as the remote URL, stored in the *.git/config* file. You may want to back up this file in advance for restoration later. + - **Overwrite your existing tags** ```shell $ git filter-repo --invert-paths --path PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA Parsed 197 commits @@ -116,21 +114,21 @@ Para ilustrar como o `git filter-repo` funciona, mostraremos como remover o arqu {% note %} - **Observação:** se o arquivo com os dados confidenciais costumava estar em qualquer outro caminho (porque foi movido ou renomeado), você também precisa executar esse comando nesses caminhos. + **Note:** If the file with sensitive data used to exist at any other paths (because it was moved or renamed), you must run this command on those paths, as well. {% endnote %} -5. Adicione o arquivo que contém dados confidenciais ao `.gitignore` para garantir que ele não sofra um novo commit acidental. +5. Add your file with sensitive data to `.gitignore` to ensure that you don't accidentally commit it again. ```shell - $ echo "YOUR-FILE-WITH-SENSITIVE-DATA" >> .gitignore + $ echo "YOUR-FILE-WITH-SENSITIVE-DATA" >> .gitignore $ git add .gitignore - $ git commit -m "Add YOUR-FILE-WITH-SENSITIVE-DATA to .gitignore" - > [main 051452f] Add YOUR-FILE-WITH-SENSITIVE-DATA to .gitignore + $ git commit -m "Add YOUR-FILE-WITH-SENSITIVE-DATA to .gitignore" + > [main 051452f] Add YOUR-FILE-WITH-SENSITIVE-DATA to .gitignore > 1 files changed, 1 insertions(+), 0 deletions(-) ``` -6. Verifique se você removeu tudo o que queria do histórico do repositório e se foi feito check-out de todos os branches. -7. Quando estiver satisfeito com o estado do repositório, faça pushes forçados das alterações locais para substituir o repositório no {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, bem como todos os branches para os quais você efetuou push: É necessário um push forçado para remover dados confidenciais do seu histórico de commit. +6. Double-check that you've removed everything you wanted to from your repository's history, and that all of your branches are checked out. +7. Once you're happy with the state of your repository, force-push your local changes to overwrite your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, as well as all the branches you've pushed up. A force push is required to remove sensitive data from your commit history. ```shell $ git push origin --force --all > Counting objects: 1074, done. @@ -138,10 +136,10 @@ Para ilustrar como o `git filter-repo` funciona, mostraremos como remover o arqu > Compressing objects: 100% (677/677), done. > Writing objects: 100% (1058/1058), 148.85 KiB, done. > Total 1058 (delta 590), reused 602 (delta 378) - > To https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY.git + > To https://{% data variables.command_line.codeblock %}/YOUR-USERNAME.YOUR-REPOSITORY.git > + 48dc599...051452f main -> main (forced update) ``` -8. Para remover o arquivo confidencial das [versões marcadas](/articles/about-releases), você também precisará forçar o push das marcas do Git: +8. In order to remove the sensitive file from [your tagged releases](/articles/about-releases), you'll also need to force-push against your Git tags: ```shell $ git push origin --force --tags > Counting objects: 321, done. @@ -149,19 +147,19 @@ Para ilustrar como o `git filter-repo` funciona, mostraremos como remover o arqu > Compressing objects: 100% (166/166), done. > Writing objects: 100% (321/321), 331.74 KiB | 0 bytes/s, done. > Total 321 (delta 124), reused 269 (delta 108) - > To https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY.git + > To https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY.git > + 48dc599...051452f main -> main (forced update) ``` -## Remover completamente os dados de {% data variables.product.prodname_dotcom %} +## Fully removing the data from {% data variables.product.prodname_dotcom %} -Depois de usar a ferramenta BFG ou `git filter-repo` para remover os dados confidenciais e efetuar push das alterações para o {% data variables.product.product_name %}, você precisa executar mais algumas etapas para remover por completo os dados do {% data variables.product.product_name %}. +After using either the BFG tool or `git filter-repo` to remove the sensitive data and pushing your changes to {% data variables.product.product_name %}, you must take a few more steps to fully remove the data from {% data variables.product.product_name %}. -1. Entre em contato com o {% data variables.contact.contact_support %} e solicite a remoção das visualizações em cache e das referências aos dados confidenciais em pull requests no {% data variables.product.product_name %}. Forneça o nome do repositório e/ou um link para a confirmação que você precisa remover. {% ifversion ghes %} Para obter mais informações sobre como os administradores de site podem remover objetos Git inacessíveis, confira "[Utilitários de linha de comando](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-repo-gc)". {% endif %} +1. Contact {% data variables.contact.contact_support %}, asking them to remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %}. Please provide the name of the repository and/or a link to the commit you need removed.{% ifversion ghes %} For more information about how site administrators can remove unreachable Git objects, see "[Command line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-repo-gc)."{% endif %} -2. Diga aos colaboradores para [trocar a base](https://git-scm.com/book/en/Git-Branching-Rebasing) (*não* fazer a mesclagem) dos branches que eles criaram fora do histórico do repositório antigo (afetado). Um commit de merge poderia reintroduzir o histórico antigo completo (ou parte dele) que você acabou de se dar ao trabalho de corrigir. +2. Tell your collaborators to [rebase](https://git-scm.com/book/en/Git-Branching-Rebasing), *not* merge, any branches they created off of your old (tainted) repository history. One merge commit could reintroduce some or all of the tainted history that you just went to the trouble of purging. -3. Depois que algum tempo tiver passado e você estiver confiante de que a ferramenta BFG/`git filter-repo` não teve efeitos colaterais não intencionais, force todos os objetos no repositório local a serem desreferenciados e faça a coleta de lixo com os seguintes comandos (usando o Git 1.8.5 ou mais recente): +3. After some time has passed and you're confident that the BFG tool / `git filter-repo` had no unintended side effects, you can force all objects in your local repository to be dereferenced and garbage collected with the following commands (using Git 1.8.5 or newer): ```shell $ git for-each-ref --format="delete %(refname)" refs/original | git update-ref --stdin $ git reflog expire --expire=now --all @@ -174,21 +172,21 @@ Depois de usar a ferramenta BFG ou `git filter-repo` para remover os dados confi ``` {% note %} - **Observação:** faça isso também enviando por push o histórico filtrado para um repositório novo ou vazio e fazendo um clone novo do {% data variables.product.product_name %}. + **Note:** You can also achieve this by pushing your filtered history to a new or empty repository and then making a fresh clone from {% data variables.product.product_name %}. {% endnote %} -## Evitar commits acidentais no futuro +## Avoiding accidental commits in the future -Há alguns truques simples para evitar fazer commit de coisas não desejadas: +There are a few simple tricks to avoid committing things you don't want committed: -- Use um programa visual como o [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) ou o [gitk](https://git-scm.com/docs/gitk) para fazer commit das alterações. Nos programas visuais, geralmente é mais fácil ver exatamente quais arquivos serão adicionados, excluídos e modificados em cada commit. -- Evite os comandos catch-all `git add .` e `git commit -a` na linha de comando: use `git add filename` e `git rm filename` para preparar os arquivos individualmente. -- Use `git add --interactive` para revisar e preparar alterações individualmente em cada arquivo. -- Use `git diff --cached` para revisar as alterações que você preparou para commit. Essa é a comparação exata que `git commit` produzirá, desde que você não use o sinalizador `-a`. +- Use a visual program like [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) or [gitk](https://git-scm.com/docs/gitk) to commit changes. Visual programs generally make it easier to see exactly which files will be added, deleted, and modified with each commit. +- Avoid the catch-all commands `git add .` and `git commit -a` on the command line—use `git add filename` and `git rm filename` to individually stage files, instead. +- Use `git add --interactive` to individually review and stage changes within each file. +- Use `git diff --cached` to review the changes that you have staged for commit. This is the exact diff that `git commit` will produce as long as you don't use the `-a` flag. -## Leitura adicional +## Further reading -- [Página de manual do `git filter-repo`](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html) -- [Pro Git: Ferramentas do Git – Reescrita do histórico](https://git-scm.com/book/en/Git-Tools-Rewriting-History) -- "[Sobre a verificação de segredos](/code-security/secret-security/about-secret-scanning)" +- [`git filter-repo` man page](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html) +- [Pro Git: Git Tools - Rewriting History](https://git-scm.com/book/en/Git-Tools-Rewriting-History) +- "[About Secret scanning](/code-security/secret-security/about-secret-scanning)" diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md index a0f830267b..dfbb52b360 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md @@ -144,8 +144,8 @@ An overview of some of the most common actions that are recorded as events in th | Action | Description |------------------|------------------- -| `create` | Triggered when you [add a new public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/adding-a-new-ssh-key-to-your-github-account). -| `delete` | Triggered when you [remove a public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/reviewing-your-ssh-keys). +| `create` | Triggered when you [add a new public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}](/articles/adding-a-new-ssh-key-to-your-github-account). +| `delete` | Triggered when you [remove a public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}](/articles/reviewing-your-ssh-keys). ### `repo` category actions @@ -242,7 +242,7 @@ An overview of some of the most common actions that are recorded as events in th | `change_password` | Triggered when you change your password. | `forgot_password` | Triggered when you ask for [a password reset](/articles/how-can-i-reset-my-password).{% endif %} | `hide_private_contributions_count` | Triggered when you [hide private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile). -| `login` | Triggered when you log in to {% data variables.product.product_location %}.{% ifversion ghes or ghae %} +| `login` | Triggered when you log in to {% data variables.location.product_location %}.{% ifversion ghes or ghae %} `mandatory_message_viewed` | Triggered when you view a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %} | `failed_login` | Triggered when you failed to log in successfully. | `remove_email` | Triggered when you remove an email address. diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md index 33fb2a8d3c..65491b5760 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md @@ -1,6 +1,6 @@ --- -title: Revisar suas chaves SSH -intro: 'Para manter suas credenciais seguras, você deve regularmente auditar as suas chaves SSH, chaves de implantação e revisar os aplicativos autorizados que acessam a sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.' +title: Reviewing your SSH keys +intro: 'To keep your credentials secure, you should regularly audit your SSH keys, deploy keys, and review authorized applications that access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}.' redirect_from: - /articles/keeping-your-application-access-tokens-safe - /articles/keeping-your-ssh-keys-and-application-access-tokens-safe @@ -15,97 +15,94 @@ versions: topics: - Identity - Access management -ms.openlocfilehash: 4f15ea8fd56994de4d9b30c21e6afb081e20a327 -ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147875484' --- -Você pode excluir chaves SSH não autorizadas (ou potencialmente comprometidas) para evitar que invasores tenham acesso aos seus repositórios. Você também pode aprovar as chaves SSh que são válidas. +You can delete unauthorized (or possibly compromised) SSH keys to ensure that an attacker no longer has access to your repositories. You can also approve existing SSH keys that are valid. {% mac %} -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.ssh %} -3. Na página das chaves SSH, anote as chaves SSH associadas à sua conta. Para aquelas que você não reconhece ou que estão desatualizadas, clique em **Excluir**. Se houver chaves SSH válidas que você deseja manter, clique em **Aprovar**. - ![Lista de chaves SSH](/assets/images/help/settings/settings-ssh-key-review.png) +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.ssh %} +3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**. + ![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png) {% tip %} - **Observação:** se você estiver auditando suas chaves SSH devido a uma operação do Git sem êxito, a chave não verificada que causou o [erro de auditoria de chave SSH](/articles/error-we-re-doing-an-ssh-key-audit) será realçada na lista de chaves SSH. + **Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys. {% endtip %} -4. Abra o terminal. +4. Open Terminal. {% data reusables.command_line.start_ssh_agent %} -6. Encontre e anote a impressão digital da chave pública. +6. Find and take a note of your public key fingerprint. ```shell $ ssh-add -l -E sha256 - > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) + > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) ``` -7. As chaves SSH no {% data variables.product.product_name %} *devem* corresponder às chaves do computador. +7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer. {% endmac %} {% windows %} -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.ssh %} -3. Na página das chaves SSH, anote as chaves SSH associadas à sua conta. Para aquelas que você não reconhece ou que estão desatualizadas, clique em **Excluir**. Se houver chaves SSH válidas que você deseja manter, clique em **Aprovar**. - ![Lista de chaves SSH](/assets/images/help/settings/settings-ssh-key-review.png) +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.ssh %} +3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**. + ![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png) {% tip %} - **Observação:** se você estiver auditando suas chaves SSH devido a uma operação do Git sem êxito, a chave não verificada que causou o [erro de auditoria de chave SSH](/articles/error-we-re-doing-an-ssh-key-audit) será realçada na lista de chaves SSH. + **Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys. {% endtip %} -4. Abra o Git Bash. +4. Open Git Bash. 5. {% data reusables.desktop.windows_git_bash_turn_on_ssh_agent %} {% data reusables.desktop.windows_git_for_windows_turn_on_ssh_agent %} -6. Encontre e anote a impressão digital da chave pública. +6. Find and take a note of your public key fingerprint. ```shell $ ssh-add -l -E sha256 - > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) + > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) ``` -7. As chaves SSH no {% data variables.product.product_name %} *devem* corresponder às chaves do computador. +7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer. {% endwindows %} {% linux %} -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.ssh %} -3. Na página das chaves SSH, anote as chaves SSH associadas à sua conta. Para aquelas que você não reconhece ou que estão desatualizadas, clique em **Excluir**. Se houver chaves SSH válidas que você deseja manter, clique em **Aprovar**. - ![Lista de chaves SSH](/assets/images/help/settings/settings-ssh-key-review.png) +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.ssh %} +3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**. + ![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png) {% tip %} - **Observação:** se você estiver auditando suas chaves SSH devido a uma operação do Git sem êxito, a chave não verificada que causou o [erro de auditoria de chave SSH](/articles/error-we-re-doing-an-ssh-key-audit) será realçada na lista de chaves SSH. + **Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys. {% endtip %} -4. Abra o terminal. +4. Open Terminal. {% data reusables.command_line.start_ssh_agent %} -6. Encontre e anote a impressão digital da chave pública. +6. Find and take a note of your public key fingerprint. ```shell $ ssh-add -l -E sha256 - > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) + > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) ``` -7. As chaves SSH no {% data variables.product.product_name %} *devem* corresponder às chaves do computador. +7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer. {% endlinux %} {% warning %} -**Aviso**: se você receber uma chave SSH com a qual não esteja familiarizado no {% data variables.product.product_name %}, exclua-a imediatamente e entre em contato com o {% data variables.contact.contact_support %} para obter mais ajuda. Uma chave pública desconhecida pode indicar um possível problema de segurança. +**Warning**: If you see an SSH key you're not familiar with on {% data variables.product.product_name %}, delete it immediately and contact {% data variables.contact.contact_support %} for further help. An unidentified public key may indicate a possible security concern. {% endwarning %} diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md index 5875a88a80..25cebe2a85 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md @@ -1,6 +1,6 @@ --- -title: Modo sudo -intro: 'Para confirmar o acesso à sua conta antes de executar uma ação potencialmente confidencial, {% data variables.product.product_location %} solicita a autenticação.' +title: Sudo mode +intro: 'To confirm access to your account before you perform a potentially sensitive action, {% data variables.location.product_location %} prompts for authentication.' redirect_from: - /articles/sudo-mode - /github/authenticating-to-github/sudo-mode @@ -13,83 +13,81 @@ miniTocMaxHeadingLevel: 3 topics: - Identity - Access management -ms.openlocfilehash: 909552ff2252e14430050541da5f6bae582f66b3 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147540823' --- -## Sobre o modo sudo -Para manter a segurança de sua conta ao executar uma ação potencialmente confidencial em {% data variables.product.product_location %}, você precisa autenticar mesmo que já esteja conectado. Por exemplo, {% data variables.product.company_short %} considera as ações a seguir confidenciais porque cada ação pode permitir que uma nova pessoa ou sistema acesse sua conta. +## About sudo mode -- Modificação de um endereço de email associado -- Autorização de um aplicativo de terceiros -- Adição de uma nova chave SSH +To maintain the security of your account when you perform a potentially sensitive action on {% data variables.location.product_location %}, you must authenticate even though you're already signed in. For example, {% data variables.product.company_short %} considers the following actions sensitive because each action could allow a new person or system to access your account. -Depois de se autenticar para executar uma ação confidencial, sua sessão estará temporariamente no "modo sudo". No modo sudo, você pode executar ações confidenciais sem autenticação. {% data variables.product.product_name %} aguardará algumas horas antes de solicitar a autenticação novamente. Durante esse tempo, qualquer ação confidencial que você executar redefinirá o temporizador. +- Modification of an associated email address +- Authorization of a third-party application +- Addition of a new SSH key + +After you authenticate to perform a sensitive action, your session is temporarily in "sudo mode." In sudo mode, you can perform sensitive actions without authentication. {% data variables.product.product_name %} will wait a few hours before prompting you for authentication again. During this time, any sensitive action that you perform will reset the timer. {% ifversion ghes %} {% note %} -**Observação**: se {% data variables.product.product_location %} usar um método de autenticação externa como CAS ou SSO de SAML, você não receberá prompts para entrar no modo sudo. Para mais informações, entre em contato com o administrador do site. +**Note**: If {% data variables.location.product_location %} uses an external authentication method like CAS or SAML SSO, you will not receive prompts to enter sudo mode. For more information, contact your site administrator. {% endnote %} {% endif %} -"sudo" é uma referência a um programa em sistemas Unix, em que o nome é uma abreviação de "**su** peruser **do**" (superusuário executa). Para obter mais informações, confira [sudo](https://wikipedia.org/wiki/Sudo) na Wikipédia. +"sudo" is a reference to a program on Unix systems, where the name is short for "**su**peruser **do**." For more information, see [sudo](https://wikipedia.org/wiki/Sudo) on Wikipedia. -## Como confirmar o acesso para o modo sudo +## Confirming access for sudo mode -Para confirmar o acesso ao modo sudo, você {% ifversion totp-and-mobile-sudo-challenge %}pode{% else %}precisa{% endif %} se autenticar com a sua senha.{% ifversion totp-and-mobile-sudo-challenge %} Opcionalmente, você pode usar um método de autenticação diferente, como {% ifversion fpt or ghec %}uma chave de segurança, {% data variables.product.prodname_mobile %}ou um código 2FA{% elsif ghes %}uma chave de segurança ou um código 2FA{% endif %}.{% endif %} +To confirm access for sudo mode, you {% ifversion totp-and-mobile-sudo-challenge %}can{% else %}must{% endif %} authenticate with your password.{% ifversion totp-and-mobile-sudo-challenge %} Optionally, you can use a different authentication method, like {% ifversion fpt or ghec %}a security key, {% data variables.product.prodname_mobile %}, or a 2FA code{% elsif ghes %}a security key or a 2FA code{% endif %}.{% endif %} {%- ifversion totp-and-mobile-sudo-challenge %} -- [Como confirmar o acesso usando uma chave de segurança](#confirming-access-using-a-security-key) {%- ifversion fpt or ghec %} -- [Como confirmar o acesso usando o GitHub Mobile](#confirming-access-using-github-mobile) {%- endif %} -- [Como confirmar o acesso usando um código 2FA](#confirming-access-using-a-2fa-code) -- [Como confirmar o acesso usando sua senha](#confirming-access-using-your-password) {%- endif %} +- [Confirming access using a security key](#confirming-access-using-a-security-key) +{%- ifversion fpt or ghec %} +- [Confirming access using GitHub Mobile](#confirming-access-using-github-mobile) +{%- endif %} +- [Confirming access using a 2FA code](#confirming-access-using-a-2fa-code) +- [Confirming access using your password](#confirming-access-using-your-password) +{%- endif %} {% ifversion totp-and-mobile-sudo-challenge %} -### Como confirmar o acesso usando uma chave de segurança +### Confirming access using a security key -Você precisa configurar a 2FA (autenticação de dois fatores) para sua conta usando uma chave de segurança para confirmar o acesso à sua conta para o modo sudo usando a chave de segurança. Para obter mais informações, confira "[Como configurar a autenticação de dois fatores](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)". +You must configure two-factor authentication (2FA) for your account using a security key to confirm access to your account for sudo mode using the security key. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)." -Quando solicitado a autenticar para o modo sudo, clique em **Usar chave de segurança** e siga os prompts. +When prompted to authenticate for sudo mode, click **Use security key**, then follow the prompts. -![Captura de tela da opção Chave de segurança para o modo sudo](/assets/images/help/settings/sudo_mode_prompt_security_key.png) +![Screenshot of security key option for sudo mode](/assets/images/help/settings/sudo_mode_prompt_security_key.png) {% ifversion fpt or ghec %} -### Como confirmar o acesso usando {% data variables.product.prodname_mobile %} +### Confirming access using {% data variables.product.prodname_mobile %} -Você precisa instalar e entrar em {% data variables.product.prodname_mobile %} para confirmar o acesso à sua conta para o modo sudo usando o aplicativo. Para obter mais informações, confira "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)". +You must install and sign into {% data variables.product.prodname_mobile %} to confirm access to your account for sudo mode using the app. For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)." -1. Quando solicitado a autenticar para o modo sudo, clique em **Usar o GitHub Mobile**. +1. When prompted to authenticate for sudo mode, click **Use GitHub Mobile**. - ![Captura de tela da opção {% data variables.product.prodname_mobile %} do modo sudo](/assets/images/help/settings/sudo_mode_prompt_github_mobile_prompt.png) -1. Abra {% data variables.product.prodname_mobile %}. {% data variables.product.prodname_mobile %} exibirá números que você precisa inserir em {% data variables.product.product_location %} para aprovar a solicitação. + ![Screenshot of {% data variables.product.prodname_mobile %} option for sudo mode](/assets/images/help/settings/sudo_mode_prompt_github_mobile_prompt.png) +1. Open {% data variables.product.prodname_mobile %}. {% data variables.product.prodname_mobile %} will display numbers that you must enter on {% data variables.location.product_location %} to approve the request. - ![Captura de tela dos números de {% data variables.product.prodname_mobile %} a serem inseridos em {% data variables.product.product_name %} para aprovar o acesso ao modo sudo](/assets/images/help/settings/sudo_mode_prompt_github_mobile.png) -1. Em {% data variables.product.product_name %}, digite os números exibidos em {% data variables.product.prodname_mobile %}. + ![Screenshot of numbers from {% data variables.product.prodname_mobile %} to enter on {% data variables.product.product_name %} to approve sudo mode access](/assets/images/help/settings/sudo_mode_prompt_github_mobile.png) +1. On {% data variables.product.product_name %}, type the numbers displayed in {% data variables.product.prodname_mobile %}. {% endif %} -### Como confirmar o acesso usando um código 2FA +### Confirming access using a 2FA code -Você precisa configurar a 2FA usando um aplicativo móvel TOTP{% ifversion fpt or ghec %} ou mensagens de texto{% endif %} para confirmar o acesso à sua conta para o modo sudo usando um código 2FA. Para obter mais informações, confira "[Como configurar a autenticação de dois fatores](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)". +You must configure 2FA using a TOTP mobile app{% ifversion fpt or ghec %} or text messages{% endif %} to confirm access to your account for sudo mode using a 2FA code. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)." -Quando solicitado a autenticar para o modo sudo, digite o código de autenticação do aplicativo móvel TOTP%{% ifversion fpt or ghec %} ou da mensagem SMS,{% endif %} e clique em **Verificar**. +When prompted to authenticate for sudo mode, type the authentication code from your TOTP mobile app{% ifversion fpt or ghec %} or the text message{% endif %}, then click **Verify**. -![Captura de tela do prompt de código 2FA para o modo sudo](/assets/images/help/settings/sudo_mode_prompt_2fa_code.png) +![Screenshot of 2FA code prompt for sudo mode](/assets/images/help/settings/sudo_mode_prompt_2fa_code.png) -### Como confirmar o acesso usando sua senha +### Confirming access using your password {% endif %} -Quando solicitado a autenticar para o modo sudo, digite sua senha e clique em **Confirmar**. +When prompted to authenticate for sudo mode, type your password, then click **Confirm**. -![Captura de tela do prompt de senha para o modo sudo](/assets/images/help/settings/sudo_mode_prompt_password.png) +![Screenshot of password prompt for sudo mode](/assets/images/help/settings/sudo_mode_prompt_password.png) diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md index eda07cf62a..7dae72fd34 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md @@ -1,6 +1,6 @@ --- -title: Vencimento e revogação de token -intro: 'Seus tokens podem vencer e também podem ser revogados por você, pelos aplicativos que você autorizou e pelo próprio {% data variables.product.product_name %}.' +title: Token expiration and revocation +intro: 'Your tokens can expire and can also be revoked by you, applications you have authorized, and {% data variables.product.product_name %} itself.' versions: fpt: '*' ghes: '*' @@ -12,59 +12,55 @@ topics: shortTitle: Token expiration redirect_from: - /github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation -ms.openlocfilehash: aa1d8902fc120aa616b8a3355f1add21a482d99e -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145083612' --- -Quando um token {% ifversion fpt or ghae or ghes > 3.2 or ghec %}tiver vencido ou {% endif %} tiver sido revogado, ele não poderá mais ser usado para autenticar solicitações do Git e da API. Não é possível restaurar um token vencido ou revogado, você ou o aplicativo deverá criar um novo token. -Este artigo explica os possíveis motivos pelos quais seu token {% data variables.product.product_name %} pode ser revogado ou vencido. +When a token {% ifversion fpt or ghae or ghes > 3.2 or ghec %}has expired or {% endif %} has been revoked, it can no longer be used to authenticate Git and API requests. It is not possible to restore an expired or revoked token, you or the application will need to create a new token. + +This article explains the possible reasons your {% data variables.product.product_name %} token might be revoked or expire. {% note %} -**Observação:** quando um token de acesso pessoal ou um token OAuth vence ou é revogado, talvez você veja uma ação `oauth_authorization.destroy` no log de segurança. Para obter mais informações, confira "[Como revisar o log de segurança](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-security-log)". +**Note:** When a {% data variables.product.pat_generic %} or OAuth token expires or is revoked, you may see an `oauth_authorization.destroy` action in your security log. For more information, see "[Reviewing your security log](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-security-log)." {% endnote %} {% ifversion fpt or ghae or ghes > 3.2 or ghec %} -## Token revogado após atingir sua data de validade +## Token revoked after reaching its expiration date -Ao criar um token de acesso pessoal, recomendamos que você defina uma data de vencimento para o seu token. Ao alcançar a data de vencimento do seu token, este será automaticamente revogado. Para obter mais informações, confira "[Como criar um token de acesso pessoal](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)". +When you create a {% data variables.product.pat_generic %}, we recommend that you set an expiration for your token. Upon reaching your token's expiration date, the token is automatically revoked. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." {% endif %} {% ifversion fpt or ghec %} -## Token revogado quando enviado por push para um repositório público ou gist público +## Token revoked when pushed to a public repository or public gist -Se um token do OAuth válido, um token de {% data variables.product.prodname_github_app %} ou o token de acesso pessoal é receber push para um repositório público ou gist, o token será revogado automaticamente. +If a valid OAuth token, {% data variables.product.prodname_github_app %} token, or {% data variables.product.pat_generic %} is pushed to a public repository or public gist, the token will be automatically revoked. + +OAuth tokens and personal {% data variables.product.pat_v1_plural %} pushed to public repositories and public gists will only be revoked if the token has scopes.{% ifversion pat-v2 %} {% data variables.product.pat_v2_caps %}s will always be revoked.{% endif %} -Os tokens OAuth e os tokens de acesso pessoal enviados para repositórios públicos e gists públicos só serão revogados se o token tiver escopos. {% endif %} {% ifversion fpt or ghec %} -## Token vencido devido à falta de uso +## Token expired due to lack of use -{% data variables.product.product_name %} irá revogar automaticamente um token OAuth ou um token de acesso pessoal quando o token não for usado em um ano. +{% data variables.product.product_name %} will automatically revoke an OAuth token or {% data variables.product.pat_generic %} when the token hasn't been used in one year. {% endif %} -## Token revogado pelo usuário +## Token revoked by the user -Você pode revogar a sua autorização de um {% data variables.product.prodname_github_app %} ou {% data variables.product.prodname_oauth_app %} a partir das configurações da sua conta que irão revogar todos tokens associados ao aplicativo. Para obter mais informações, confira "[Como revisar suas integrações autorizadas](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)" e "[Como revisar seus aplicativos autorizados (OAuth)](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth)". +You can revoke your authorization of a {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %} from your account settings which will revoke any tokens associated with the app. For more information, see "[Reviewing your authorized integrations](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)" and "[Reviewing your authorized applications (OAuth)](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth)." -Depois que uma autorização for revogada, todos os tokens associados à autorização também serão revogados. Para autorizar novamente um aplicativo, siga as instruções do aplicativo de terceiros ou do site para conectar sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} novamente. +Once an authorization is revoked, any tokens associated with the authorization will be revoked as well. To re-authorize an application, follow the instructions from the third-party application or website to connect your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} again. -## Token revogado por {% data variables.product.prodname_oauth_app %} +## Token revoked by the {% data variables.product.prodname_oauth_app %} -O proprietário de um {% data variables.product.prodname_oauth_app %} pode revogar a autorização de uma conta do seu aplicativo. Isso também irá revogar todos os tokens associados à autorização. Para obter mais informações sobre como revogar autorizações do seu aplicativo OAuth, confira "[Excluir uma autorização de aplicativo](/rest/reference/apps#delete-an-app-authorization)". +The owner of an {% data variables.product.prodname_oauth_app %} can revoke an account's authorization of their app, this will also revoke any tokens associated with the authorization. For more information about revoking authorizations of your OAuth app, see "[Delete an app authorization](/rest/reference/apps#delete-an-app-authorization)." -Proprietários de {% data variables.product.prodname_oauth_app %} também podem revogar tokens individuais associados a uma autorização. Para obter mais informações sobre como revogar tokens individuais para seu aplicativo OAuth, veja "[Excluir um token de aplicativo](/rest/apps/oauth-applications#delete-an-app-token)". +{% data variables.product.prodname_oauth_app %} owners can also revoke individual tokens associated with an authorization. For more information about revoking individual tokens for your OAuth app, see "[Delete an app token](/rest/apps/oauth-applications#delete-an-app-token)". -## Token revogado devido ao excesso de tokens para um {% data variables.product.prodname_oauth_app %} com o mesmo escopo +## Token revoked due to excess of tokens for an {% data variables.product.prodname_oauth_app %} with the same scope {% data reusables.apps.oauth-token-limit %} -## Token de usuário revogado devido à configuração de {% data variables.product.prodname_github_app %} +## User token revoked due to {% data variables.product.prodname_github_app %} configuration -Por padrão, os tokens de usuário para servidor criados por um {% data variables.product.prodname_github_app %} vencerão após oito horas. Os proprietários de {% data variables.product.prodname_github_apps %} podem configurar seus aplicativos para que os tokens de usuário para servidor não vençam. Para obter mais informações sobre como o comportamento dos tokens de usuário para servidor do Aplicativo do {% data variables.product.prodname_dotcom %}, confira "[Como ativar recursos opcionais para aplicativos](/developers/apps/getting-started-with-apps/activating-optional-features-for-apps)". +User-to-server tokens created by a {% data variables.product.prodname_github_app %} will expire after eight hours by default. Owners of {% data variables.product.prodname_github_apps %} can configure their apps so that user-to-server tokens do not expire. For more information about changing how your {% data variables.product.prodname_dotcom %} App's user-to-server tokens behave, see "[Activating optional features for apps](/developers/apps/getting-started-with-apps/activating-optional-features-for-apps)." diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md index 4fc1ca7021..12e35114b2 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md @@ -1,6 +1,6 @@ --- -title: Atualizar credenciais de acesso do GitHub -intro: 'As credenciais do {% data variables.product.product_name %} incluem{% ifversion not ghae %} não só sua senha, mas também{% endif %} os tokens de acesso, chaves SSH e tokens de API do aplicativo que você usa para se comunicar com {% data variables.product.product_name %}. Se houver necessidade, você mesmo pode redefinir todas essas credenciais de acesso.' +title: Updating your GitHub access credentials +intro: '{% data variables.product.product_name %} credentials include{% ifversion not ghae %} not only your password, but also{% endif %} the access tokens, SSH keys, and application API tokens you use to communicate with {% data variables.product.product_name %}. Should you have the need, you can reset all of these access credentials yourself.' redirect_from: - /articles/rolling-your-credentials - /articles/how-can-i-reset-my-password @@ -16,74 +16,73 @@ topics: - Identity - Access management shortTitle: Update access credentials -ms.openlocfilehash: 650c0027b679690def6d1c77d727a87b8688b889 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147508413' --- {% ifversion not ghae %} -## Solicitar uma nova senha +## Requesting a new password -1. Para solicitar uma nova senha, acesse {% ifversion fpt or ghec %} https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}. -2. Insira o endereço de email associado à sua conta do {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} e clique em **Enviar email de redefinição de senha.** O email será enviado para o endereço de email de backup se você tiver um configurado. - ![Caixa de diálogo usada para solicitar o email de redefinição de senha](/assets/images/help/settings/password-recovery-email-request.png) -3. Nós enviaremos por e-mail um link para você redefinir sua senha. Clique nele em até 3 horas após o recebimento do e-mail. Se você não receber o e-mail com o link, verifique sua pasta de spam. -4. Se você tiver habilitado a autenticação de dois fatores, será solicitado que você crie suas credenciais de 2FA: {% ifversion fpt or ghec %} - * Se você tiver {% data variables.product.prodname_mobile %}, receberá uma notificação por push para verificar sua identidade. Abra a notificação por push ou o aplicativo {% data variables.product.prodname_mobile %} e digite o código de dois dígitos mostrado na página de redefinição de senha em seu navegador. - ![Prompt de autenticação {% data variables.product.prodname_mobile %} de dois fatores](/assets/images/help/2fa/2fa-mobile-challenge-password-reset.png) - * Para pular o uso da verificação do GitHub Mobile, clique em **Inserir autenticação de dois fatores ou código de recuperação**. - ![Prompt de autenticação de dois fatores do GitHub Mobile em {% data variables.product.product_name %} com "Inserir autenticação de dois fatores ou código de recuperação" realçado](/assets/images/help/2fa/2fa-github-mobile-password-reset.png) {% endif %} - * Digite o código de autenticação ou um dos códigos de recuperação e clique em **Verificar**. - ![Prompt da autenticação de dois fatores](/assets/images/help/2fa/2fa-password-reset.png) - * Se você adicionou uma chave de segurança à sua conta, clique em **Usar chave de segurança** em vez de digitar um código de autenticação. +1. To request a new password, visit {% ifversion fpt or ghec %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}. +2. Enter the email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then click **Send password reset email.** The email will be sent to the backup email address if you have one configured. + ![Password reset email request dialog](/assets/images/help/settings/password-recovery-email-request.png) +3. We'll email you a link that will allow you to reset your password. You must click on this link within 3 hours of receiving the email. If you didn't receive an email from us, make sure to check your spam folder. +4. If you have enabled two-factor authentication, you will be prompted for your 2FA credentials: +{% ifversion fpt or ghec %} + * If you have {% data variables.product.prodname_mobile %}, you will be sent a push notification to verify your identity. Open the push notification or the {% data variables.product.prodname_mobile %} app and enter the two-digit code shown to you on the password reset page in your browser. + ![Two-factor {% data variables.product.prodname_mobile %} authentication prompt](/assets/images/help/2fa/2fa-mobile-challenge-password-reset.png) + * To skip using GitHub Mobile to verify, click **Enter two-factor authentication or recovery code**. + ![Two-factor GitHub Mobile authentication prompt on {% data variables.product.product_name %} with "Enter two-factor authentication or recovery code" highlighted](/assets/images/help/2fa/2fa-github-mobile-password-reset.png) +{% endif %} + * Type your authentication code or one of your recovery codes and click **Verify**. + ![Two-factor authentication prompt](/assets/images/help/2fa/2fa-password-reset.png) + * If you have added a security key to your account, click **Use security key** instead of typing an authentication code. {% ifversion fpt or ghec %} - * Se você tiver configurado [dados {% data variables.product.prodname_mobile %}](https://github.com/mobile), clique em **Autenticar com o GitHub Mobile** . + * If you have set up [{% data variables.product.prodname_mobile %}](https://github.com/mobile), click **Authenticate with GitHub Mobile** instead. {% endif %} -5. Digite uma nova senha, confirme a nova senha e clique em **Alterar senha**. Para obter ajuda para criar uma senha forte, confira "[Como criar uma senha forte](/articles/creating-a-strong-password)". - {% ifversion fpt or ghec %}![Caixa de Recuperação de senha](/assets/images/help/settings/password-recovery-page.png){% else %} ![Caixa de Recuperação de senha](/assets/images/enterprise/settings/password-recovery-page.png){% endif %} +5. Type a new password, confirm your new password, and click **Change password**. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)." + {% ifversion fpt or ghec %}![Password recovery box](/assets/images/help/settings/password-recovery-page.png){% else %} + ![Password recovery box](/assets/images/enterprise/settings/password-recovery-page.png){% endif %} {% tip %} -Para evitar perder sua senha no futuro, sugerimos usar um gerenciador de senhas seguro, como o [LastPass](https://lastpass.com/) ou o [1Password](https://1password.com/). +To avoid losing your password in the future, we suggest using a secure password manager, like [LastPass](https://lastpass.com/) or [1Password](https://1password.com/). {% endtip %} -## Alterar uma senha existente +## Changing an existing password {% data reusables.repositories.blocked-passwords %} -1. {% data variables.product.signin_link %} para o {% data variables.product.product_name %}. -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security %} -4. Em "Change password" (Alterar senha), insira a senha antiga, digite uma nova senha forte e confirme a nova senha. Para obter ajuda para criar uma senha forte, confira "[Como criar uma senha forte](/articles/creating-a-strong-password)" -5. Clique em **Atualizar senha**. +1. {% data variables.product.signin_link %} to {% data variables.product.product_name %}. +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.security %} +4. Under "Change password", type your old password, a strong new password, and confirm your new password. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)" +5. Click **Update password**. {% tip %} -Para maior segurança, além de alterar a senha, habilite também a autenticação de dois fatores. Confira [Sobre a autenticação de dois fatores](/articles/about-two-factor-authentication) para obter mais detalhes. +For greater security, enable two-factor authentication in addition to changing your password. See [About two-factor authentication](/articles/about-two-factor-authentication) for more details. -{% endtip %} {% endif %} -## Atualizar tokens de acesso +{% endtip %} +{% endif %} +## Updating your access tokens -Confira "[Como revisar suas integrações autorizadas](/articles/reviewing-your-authorized-integrations)" para obter instruções sobre como revisar e excluir tokens de acesso. Para gerar novos tokens de acesso, confira "[Como criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)". +See "[Reviewing your authorized integrations](/articles/reviewing-your-authorized-integrations)" for instructions on reviewing and deleting access tokens. To generate new access tokens, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." {% ifversion not ghae %} -Se você redefiniu sua senha da conta e também gostaria de disparar um logout do aplicativo {% data variables.product.prodname_mobile %}, revogue a sua autorização do aplicativo OAuth do "GitHub iOS" ou "GitHub Android". Isso removerá todas as instâncias do aplicativo {% data variables.product.prodname_mobile %} associado à sua conta. Para obter mais informações, confira "[Como revisar suas integrações autorizadas](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)". +If you have reset your account password and would also like to trigger a sign-out from the {% data variables.product.prodname_mobile %} app, you can revoke your authorization of the "GitHub iOS" or "GitHub Android" OAuth App. This will sign out all instances of the {% data variables.product.prodname_mobile %} app associated with your account. For additional information, see "[Reviewing your authorized integrations](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)." {% endif %} -## Atualizar chaves SSH +## Updating your SSH keys -Confira "[Como revisar suas chaves SSH](/articles/reviewing-your-ssh-keys)" para obter instruções sobre como revisar e excluir chaves SSH. Para gerar e adicionar novas chaves SSH, confira "[Como gerar uma chave SSH](/articles/generating-an-ssh-key)". +See "[Reviewing your SSH keys](/articles/reviewing-your-ssh-keys)" for instructions on reviewing and deleting SSH keys. To generate and add new SSH keys, see "[Generating an SSH key](/articles/generating-an-ssh-key)." -## Redefinir tokens da API +## Resetting API tokens -Se você tiver algum aplicativo registrado no {% data variables.product.product_name %}, talvez precise redefinir os tokens OAuth dele. Para obter mais informações, confira o ponto de extremidade "[Redefinir uma autorização](/rest/reference/apps#reset-an-authorization)". +If you have any applications registered with {% data variables.product.product_name %}, you'll want to reset their OAuth tokens. For more information, see the "[Reset an authorization](/rest/reference/apps#reset-an-authorization)" endpoint. {% ifversion not ghae %} -## Impedir acesso não autorizado +## Preventing unauthorized access -Para obter mais dicas sobre como proteger sua conta e impedir o acesso não autorizado, confira "[Como impedir o acesso não autorizado](/articles/preventing-unauthorized-access)". +For more tips on securing your account and preventing unauthorized access, see "[Preventing unauthorized access](/articles/preventing-unauthorized-access)." {% endif %} diff --git a/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md index b2287d3a5e..4f526c28c2 100644 --- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md +++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md @@ -73,7 +73,7 @@ You can optionally choose to have {% data variables.product.prodname_dotcom %} G You can use GPG to sign commits with a GPG key that you generate yourself. -{% data variables.product.product_name %} uses OpenPGP libraries to confirm that your locally signed commits and tags are cryptographically verifiable against a public key you have added to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. +{% data variables.product.product_name %} uses OpenPGP libraries to confirm that your locally signed commits and tags are cryptographically verifiable against a public key you have added to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. To sign commits using GPG and have those commits verified on {% data variables.product.product_name %}, follow these steps: @@ -90,7 +90,7 @@ To sign commits using GPG and have those commits verified on {% data variables.p You can use SSH to sign commits with an SSH public key that you generate yourself. If you already use an SSH key to authenticate with {% data variables.product.product_name %}, you can also upload that same key again for use as a signing key. There's no limit on the number of signing keys you can add to your account. -{% data variables.product.product_name %} uses [ssh_data](https://github.com/github/ssh_data), an open source Ruby library, to confirm that your locally signed commits and tags are cryptographically verifiable against a public key you have added to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. +{% data variables.product.product_name %} uses [ssh_data](https://github.com/github/ssh_data), an open source Ruby library, to confirm that your locally signed commits and tags are cryptographically verifiable against a public key you have added to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. {% data reusables.gpg.ssh-git-version %} diff --git a/translations/pt-BR/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md index 172bc717fa..febbc304fa 100644 --- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md +++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md @@ -1,6 +1,6 @@ --- -title: Como adicionar uma chave GPG a uma conta do GitHub -intro: 'Para configurar a sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} para usar sua chave GPG nova (ou existente), você também precisará da chave para a sua conta.' +title: Adding a GPG key to your GitHub account +intro: 'To configure your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} to use your new (or existing) GPG key, you''ll also need the key to your account.' redirect_from: - /articles/adding-a-gpg-key-to-your-github-account - /github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account @@ -19,55 +19,54 @@ topics: - Identity - Access management shortTitle: Add a GPG key -ms.openlocfilehash: db832d4e02ea5f19303b3178fb669967238e661b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147369334' --- -## Sobre a adição de chaves GPG à sua conta -Para assinar confirmações associadas à sua conta no {% data variables.product.product_name %}, adicione uma chave GPG pública à sua conta pessoal. Antes de realizar a adição, verifique se há chaves existentes. Se não houver, gere e copie uma nova chave. Para saber mais, confira "[Verificar se há chaves GPG existentes](/articles/checking-for-existing-gpg-keys)" e "[Gerar uma chave GPG](/articles/generating-a-new-gpg-key)". +## About addition of GPG keys to your account -É possível adicionar várias chaves públicas à sua conta no {% data variables.product.product_name %}. As confirmações assinadas por qualquer uma das chaves privadas correspondentes serão mostradas conforme verificado. Se você remover uma chave pública, todas as confirmações assinadas pela chave privada correspondente não serão mais exibidas como verificadas. +To sign commits associated with your account on {% data variables.product.product_name %}, you can add a public GPG key to your personal account. Before you add a key, you should check for existing keys. If you don't find any existing keys, you can generate and copy a new key. For more information, see "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)" and "[Generating a new GPG key](/articles/generating-a-new-gpg-key)." -{% ifversion upload-expired-or-revoked-gpg-key %} Para verificar o maior número possível de confirmações, adicione chaves expiradas e revogadas. Se a chave atender a todos os outros requisitos de verificação, as confirmações assinadas anteriormente por qualquer uma das chaves privadas correspondentes serão mostradas como verificadas e indicarão que a chave de assinatura expirou ou foi revogada. +You can add multiple public keys to your account on {% data variables.product.product_name %}. Commits signed by any of the corresponding private keys will show as verified. If you remove a public key, any commits signed by the corresponding private key will no longer show as verified. -![Uma confirmação verificada com uma chave que expirou](/assets/images/help/settings/gpg-verified-with-expired-key.png) {% endif %} +{% ifversion upload-expired-or-revoked-gpg-key %} +To verify as many of your commits as possible, you can add expired and revoked keys. If the key meets all other verification requirements, commits that were previously signed by any of the corresponding private keys will show as verified and indicate that their signing key is expired or revoked. + +![A verified commit whose key expired](/assets/images/help/settings/gpg-verified-with-expired-key.png) +{% endif %} {% data reusables.gpg.supported-gpg-key-algorithms %} -Ao verificar uma assinatura, o {% data variables.product.product_name %} a extrai e tenta analisar a ID de chave associada. Em seguida, essa ID de chave é correspondida com as chaves adicionadas ao {% data variables.product.product_name %}. Não será possível verificar suas assinaturas até que uma chave GPG seja adicionada ao {% data variables.product.product_name %}. +When verifying a signature, {% data variables.product.product_name %} extracts the signature and attempts to parse its key ID. The key ID is then matched with keys added to {% data variables.product.product_name %}. Until a matching GPG key is added to {% data variables.product.product_name %}, it cannot verify your signatures. -## Adicionar uma chave GPG +## Adding a GPG key -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.ssh %} -3. Clique em **Nova chave GPG**. - ![Botão Chave GPG](/assets/images/help/settings/gpg-add-gpg-key.png) -4. No campo "Chave", cole a chave GPG que você copiou ao [gerar a chave GPG](/articles/generating-a-new-gpg-key). - ![O campo de chave](/assets/images/help/settings/gpg-key-paste.png) -5. Clique em **Adicionar chave GPG**. - ![O botão Adicionar chave](/assets/images/help/settings/gpg-add-key.png) -6. Para confirmar a ação, insira sua senha do {% data variables.product.product_name %}. +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.ssh %} +3. Click **New GPG key**. + ![GPG Key button](/assets/images/help/settings/gpg-add-gpg-key.png) +4. In the "Key" field, paste the GPG key you copied when you [generated your GPG key](/articles/generating-a-new-gpg-key). + ![The key field](/assets/images/help/settings/gpg-key-paste.png) +5. Click **Add GPG key**. + ![The Add key button](/assets/images/help/settings/gpg-add-key.png) +6. To confirm the action, enter your {% data variables.product.product_name %} password. -{% ifversion upload-expired-or-revoked-gpg-key %} {% else %} -## Atualizar uma chave GPG expirada +{% ifversion upload-expired-or-revoked-gpg-key %} +{% else %} +## Updating an expired GPG key -Ao verificar uma assinatura, o {% data variables.product.product_name %} confere se a chave foi revogada ou está expirada. Caso a chave de assinatura tenha sido revogada ou esteja expirada, o {% data variables.product.product_name %} não poderá verificar as assinaturas. +When verifying a signature, {% data variables.product.product_name %} checks that the key is not revoked or expired. If your signing key is revoked or expired, {% data variables.product.product_name %} cannot verify your signatures. -Se sua chave tiver expirado, [atualize a expiração](https://www.gnupg.org/gph/en/manual.html#AEN329), exporte a nova chave, exclua a chave expirada da conta no {% data variables.product.product_name %} e adicione a nova chave à conta, conforme descrito acima. As tags e os commits anteriores serão exibidos como verificados, desde que a chave atenda a todos os outros requisitos de verificação. +If your key is expired, you must [update its expiration](https://www.gnupg.org/gph/en/manual.html#AEN329), export the new key, delete the expired key in your account on {% data variables.product.product_name %}, and add the new key to your account as described above. Your previous commits and tags will show as verified, as long as the key meets all other verification requirements. -Se a chave foi revogada, use a chave principal ou outra chave que não tenha sido revogada para assinar os commits. +If your key is revoked, use the primary key or another key that is not revoked to sign your commits. -Se a chave for inválida, você não usar outra chave válida no conjunto de chaves e ainda gerar uma nova chave GPG com um novo conjunto de credenciais, os commits feitos com a chave revogada ou expirada continuarão sendo exibidos como não verificados. Além disso, as novas credenciais não poderão assinar novamente ou verificar marcas e confirmações antigas. +If your key is invalid and you don't use another valid key in your key set, but instead generate a new GPG key with a new set of credentials, then your commits made with the revoked or expired key will continue to show as unverified. Also, your new credentials will not be able to re-sign or verify your old commits and tags. {% endif %} -## Leitura adicional +## Further reading -- "[Como verificar se há chaves GPG existentes](/articles/checking-for-existing-gpg-keys)" -- "[Como gerar uma nova chave GPG](/articles/generating-a-new-gpg-key)" -- "[Como informar sua chave de assinatura ao Git](/articles/telling-git-about-your-signing-key)" -- "[Como associar um email à sua chave GPG](/articles/associating-an-email-with-your-gpg-key)" -- "[Como assinar commits e tags usando chaves GPG](/articles/signing-commits-and-tags-using-gpg)" -- "[Sobre a verificação da assinatura de commit](/articles/about-commit-signature-verification)" +- "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)" +- "[Generating a new GPG key](/articles/generating-a-new-gpg-key)" +- "[Telling Git about your signing key](/articles/telling-git-about-your-signing-key)" +- "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)" +- "[Signing commits and tags using GPG keys](/articles/signing-commits-and-tags-using-gpg)" +- "[About commit signature verification](/articles/about-commit-signature-verification)" diff --git a/translations/pt-BR/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md index 2e8713ae59..3c92549eb7 100644 --- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md +++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md @@ -1,6 +1,6 @@ --- -title: Associar um e-mail à chave GPG -intro: 'Sua chave GPG deve ser associada a um e-mail verificado do {% data variables.product.product_name %} que corresponda à identidade do committer.' +title: Associating an email with your GPG key +intro: 'Your GPG key must be associated with a {% data variables.product.product_name %} verified email that matches your committer identity.' redirect_from: - /articles/associating-an-email-with-your-gpg-key - /github/authenticating-to-github/associating-an-email-with-your-gpg-key @@ -14,53 +14,49 @@ topics: - Identity - Access management shortTitle: Associate email with GPG key -ms.openlocfilehash: d36c053e1df0c329fb8d4607b1338c49414e76de -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147369278' --- {% note %} -Se você estiver usando uma chave GPG que corresponde à sua identidade do autor do submissão e ao endereço de e-mail verificado associado à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, você poderá começar a assinar commits e tags. +If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags. {% endnote %} -{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} -4. Insira `gpg --edit-key GPG key ID`, substituindo a ID da chave GPG que deseja usar. No seguinte exemplo, a ID da chave GPG é `3AA5C34371567BD2`: +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.gpg.list-keys-with-note %} +{% data reusables.gpg.copy-gpg-key-id %} +4. Enter `gpg --edit-key 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 --edit-key 3AA5C34371567BD2 + $ gpg --edit-key 3AA5C34371567BD2 ``` -5. Insira `gpg> adduid` para adicionar os detalhes da ID do usuário. +5. Enter `gpg> adduid` to add the user ID details. ```shell $ gpg> adduid ``` -6. Siga as solicitações para fornecer seu nome verdadeiro, endereço de e-mail e quaisquer comentários. Você pode modificar as entradas escolhendo `N`, `C` ou `E`. {% data reusables.gpg.private-email %} {% ifversion fpt or ghec %} Para obter mais informações, confira "[Como definir seu endereço de email de commit](/articles/setting-your-commit-email-address)".{% endif %} +6. Follow the prompts to supply your real name, email address, and any comments. You can modify your entries by choosing `N`, `C`, or `E`. {% data reusables.gpg.private-email %} {% ifversion fpt or ghec %} For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)."{% endif %} ```shell - Real Name: Octocat - Email address: octocat@github.com - Comment: GitHub key + Real Name: OCTOCAT + Email address: "octocat@github.com" + Comment: GITHUB-KEY Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? ``` -7. Insira `O` para confirmar as seleções. -8. Insira a frase secreta da sua chave. -9. Insira `gpg> save` para salvar as alterações +7. Enter `O` to confirm your selections. +8. Enter your key's passphrase. +9. Enter `gpg> save` to save the changes ```shell $ gpg> save ``` -10. Insira `gpg --armor --export GPG key ID`, substituindo a ID da chave GPG que deseja usar. No seguinte exemplo, a ID da chave GPG é `3AA5C34371567BD2`: +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 + $ gpg --armor --export 3AA5C34371567BD2 # Prints the GPG key, in ASCII armor format ``` -11. Carregue a chave GPG [adicionando-a à sua conta do GitHub](/articles/adding-a-gpg-key-to-your-github-account). +11. Upload the GPG key by [adding it to your GitHub account](/articles/adding-a-gpg-key-to-your-github-account). -## Leitura adicional +## Further reading -- "[Como verificar se há chaves GPG existentes](/articles/checking-for-existing-gpg-keys)" -- "[Como gerar uma nova chave GPG](/articles/generating-a-new-gpg-key)" -- "[Como usar um endereço de email verificado na chave GPG](/articles/using-a-verified-email-address-in-your-gpg-key)" -- "[Como adicionar uma chave GPG a uma conta do GitHub](/articles/adding-a-gpg-key-to-your-github-account)" -- "[Como assinar commits](/articles/signing-commits)" -- "[Como assinar tags](/articles/signing-tags)" +- "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)" +- "[Generating a new GPG key](/articles/generating-a-new-gpg-key)" +- "[Using a verified email address in your GPG key](/articles/using-a-verified-email-address-in-your-gpg-key)" +- "[Adding a GPG key to your GitHub account](/articles/adding-a-gpg-key-to-your-github-account)" +- "[Signing commits](/articles/signing-commits)" +- "[Signing tags](/articles/signing-tags)" diff --git a/translations/pt-BR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md index 6e9972c33c..504536da90 100644 --- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md +++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md @@ -20,7 +20,7 @@ shortTitle: Tell Git your signing key ## Telling Git about your GPG key -If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags. +If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags. {% note %} @@ -58,7 +58,7 @@ If you have multiple GPG keys, you need to tell Git which one to use. ## Telling Git about your GPG key -If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags. +If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags. {% note %} @@ -80,7 +80,7 @@ If you have multiple GPG keys, you need to tell Git which one to use. ## Telling Git about your GPG key -If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags. +If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags. {% note %} diff --git a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md index 6c590c735b..66084e4142 100644 --- a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md +++ b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md @@ -1,6 +1,6 @@ --- -title: Sobre a autenticação de dois fatores -intro: '{% data reusables.two_fa.about-2fa %} Com 2FA, você deve efetuar o login com seu nome de usuário e senha e fornecer outra forma de autenticação que você conheça ou tenha acesso.' +title: About two-factor authentication +intro: '{% data reusables.two_fa.about-2fa %} With 2FA, you have to log in with your username and password and provide another form of authentication that only you know or have access to.' redirect_from: - /articles/about-two-factor-authentication - /github/authenticating-to-github/about-two-factor-authentication @@ -12,42 +12,37 @@ versions: topics: - 2FA shortTitle: About 2FA -ms.openlocfilehash: f4b15aeeece76ce5e5afe915e0e0bc4893c4dbb6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145083590' --- -Para o {% data variables.product.product_name %}, a segunda forma de autenticação é um código gerado por um aplicativo no seu dispositivo móvel{% ifversion fpt or ghec %} ou enviado como um SMS (mensagem de texto){% endif %}. Após habilitar a 2FA, {% data variables.product.product_name %} irá gerar um código de autenticação sempre que alguém tenta entrar na sua conta em {% data variables.product.product_location %}. A única maneira com a qual alguém poderá entrar na sua conta é se souber a sua senha e tiver acesso ao código de autenticação no seu telefone. +For {% data variables.product.product_name %}, the second form of authentication is a code that's generated by an application on your mobile device{% ifversion fpt or ghec %} or sent as a text message (SMS){% endif %}. After you enable 2FA, {% data variables.product.product_name %} generates an authentication code any time someone attempts to sign into your account on {% data variables.location.product_location %}. The only way someone can sign into your account is if they know both your password and have access to the authentication code on your phone. {% data reusables.two_fa.after-2fa-add-security-key %} -{% ifversion fpt or ghec %} Além das chaves de segurança, você também pode usar o {% data variables.product.prodname_mobile %} para a 2FA depois de configurar um aplicativo móvel TOTP ou mensagens de texto. O {% data variables.product.prodname_mobile %} usa criptografia de chave pública para proteger sua conta, permitindo que você use qualquer dispositivo móvel que usou para entrar no {% data variables.product.prodname_mobile %} como segundo fator. +{% ifversion fpt or ghec %} +In addition to security keys, you can also use {% data variables.product.prodname_mobile %} for 2FA after configuring a TOTP mobile app or text messages. {% data variables.product.prodname_mobile %} uses public-key cryptography to secure your account, allowing you to use any mobile device that you've used to sign in to {% data variables.product.prodname_mobile %} as your second factor. {% endif %} -Você também pode configurar métodos de recuperação adicionais, caso você o acesso às suas credenciais de autenticação de dois fatores. Para obter mais informações sobre como configurar a 2FA, confira "[Como configurar a autenticação de dois fatores](/articles/configuring-two-factor-authentication)" e "[Como configurar métodos de recuperação da autenticação de dois fatores](/articles/configuring-two-factor-authentication-recovery-methods)". +You can also configure additional recovery methods in case you lose access to your two-factor authentication credentials. For more information on setting up 2FA, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)" and "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)." -Pedimos **fortemente** que você habilite a 2FA para a segurança da sua conta, não apenas no {% data variables.product.product_name %}, mas em outros sites e aplicativos que dão suporte à 2FA. Você pode habilitar o 2FA para acessar {% data variables.product.product_name %} e {% data variables.product.prodname_desktop %}. +We **strongly** urge you to enable 2FA for the safety of your account, not only on {% data variables.product.product_name %}, but on other websites and apps that support 2FA. You can enable 2FA to access {% data variables.product.product_name %} and {% data variables.product.prodname_desktop %}. -Para obter mais informações, confira "[Como acessar o {% data variables.product.prodname_dotcom %} usando a autenticação de dois fatores](/articles/accessing-github-using-two-factor-authentication)". +For more information, see "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)." -## Códigos de recuperação da autenticação de dois fatores +## Two-factor authentication recovery codes -{% data reusables.two_fa.about-recovery-codes %} Para obter mais informações, confira "[Como recuperar sua conta se você perder suas credenciais de 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)". +{% data reusables.two_fa.about-recovery-codes %} For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)." {% ifversion fpt or ghec %} {% warning %} -**Aviso**: {% data reusables.two_fa.support-may-not-help %} Para obter mais informações, confira "[Como recuperar sua conta se você perder suas credenciais de 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)". +**Warning**: {% data reusables.two_fa.support-may-not-help %} For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)." {% endwarning %} {% endif %} -## Exigindo a autenticação de dois fatores na sua organização +## Requiring two-factor authentication in your organization -Os proprietários da organização podem exigir que os membros da organização{% ifversion fpt or ghec %}, os gerentes de cobrança{% endif %} e os colaboradores externos usem a autenticação de dois fatores para proteger as contas pessoais. Para obter mais informações, confira "[Como exigir a autenticação de dois fatores na sua organização](/articles/requiring-two-factor-authentication-in-your-organization)". +Organization owners can require that organization members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators use two-factor authentication to secure their personal accounts. For more information, see "[Requiring two-factor authentication in your organization](/articles/requiring-two-factor-authentication-in-your-organization)." {% data reusables.two_fa.auth_methods_2fa %} diff --git a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md index af5bcb0e0a..a79e1f0801 100644 --- a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md +++ b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md @@ -1,6 +1,6 @@ --- -title: Acessar o GitHub usando a autenticação de dois fatores -intro: 'Com a 2FA habilitada, será solicitado que você forneça seu código de autenticação de 2FA, bem como sua senha, ao iniciar a sessão no {% data variables.product.product_name %}.' +title: Accessing GitHub using two-factor authentication +intro: 'With 2FA enabled, you''ll be asked to provide your 2FA authentication code, as well as your password, when you sign in to {% data variables.product.product_name %}.' redirect_from: - /articles/providing-your-2fa-security-code - /articles/providing-your-2fa-authentication-code @@ -15,89 +15,83 @@ versions: topics: - 2FA shortTitle: Access GitHub with 2FA -ms.openlocfilehash: 244cc4b45165cbc327729fd6d1c5ac519a6a6d7a -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145083588' --- -Com a autenticação de dois fatores habilitada, você deverá fornecer um código de autenticação ao acessar {% data variables.product.product_name %} por meio do seu navegador. Se você acessar {% data variables.product.product_name %} usando outros métodos, como, por exemplo, a API ou a linha de comando, você deverá usar uma forma alternativa de autenticação. Para obter mais informações, confira "[Sobre a autenticação no {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)". +With two-factor authentication enabled, you'll need to provide an authentication code when accessing {% data variables.product.product_name %} through your browser. If you access {% data variables.product.product_name %} using other methods, such as the API or the command line, you'll need to use an alternative form of authentication. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)." -## Fornecer um código 2FA ao entrar no site +## Providing a 2FA code when signing in to the website -Depois de entrar no {% data variables.product.product_name %} usando sua senha, você precisará fornecer um código de autenticação de {% ifversion fpt or ghec %}uma mensagem de texto ou{% endif %} do seu aplicativo TOTP. +After you sign in to {% data variables.product.product_name %} using your password, you'll be prompted to provide an authentication code from {% ifversion fpt or ghec %}a text message or{% endif %} your TOTP app. -O {% data variables.product.product_name %} solicitará seu código de autenticação 2FA novamente apenas se você se desconectar, for usar um novo dispositivo ou a sessão expirar. +{% data variables.product.product_name %} will only ask you to provide your 2FA authentication code again if you've logged out, are using a new device, or your session expires. -### Gerar um código por meio de um aplicativo TOTP +### Generating a code through a TOTP application -Se você optar por configurar a autenticação de dois fatores usando um aplicativo TOTP no smartphone, será possível gerar um código de autenticação para o {% data variables.product.product_name %} a qualquer momento. Na maioria das vezes, apenas iniciar o aplicativo gera um novo código. Você deve consultar a documentação do seu aplicativo para obter instruções específicas. +If you chose to set up two-factor authentication using a TOTP application on your smartphone, you can generate an authentication code for {% data variables.product.product_name %} at any time. In most cases, just launching the application will generate a new code. You should refer to your application's documentation for specific instructions. -Em caso de exclusão do aplicativo móvel após configuração da autenticação de dois fatores, será preciso fornecer seu código de recuperação para obter acesso à sua conta. Para obter mais informações, confira "[Como recuperar sua conta se você perder suas credenciais de autenticação de dois fatores](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" +If you delete the mobile application after configuring two-factor authentication, you'll need to provide your recovery code to get access to your account. For more information, see "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" {% ifversion fpt or ghec %} -### Receber uma mensagem de texto +### Receiving a text message -Se você configurar a autenticação de dois fatores por meio de mensagens de texto, o {% data variables.product.product_name %} enviará uma mensagem de texto com seu código de autenticação. +If you set up two-factor authentication via text messages, {% data variables.product.product_name %} will send you a text message with your authentication code. -### Verificando com {% data variables.product.prodname_mobile %} +### Verifying with {% data variables.product.prodname_mobile %} -Se você tiver instalado e conectado a {% data variables.product.prodname_mobile %}, você poderá optar por efetuar a autenticação com {% data variables.product.prodname_mobile %} para autenticação de dois fatores. +If you have installed and signed in to {% data variables.product.prodname_mobile %}, you may choose to authenticate with {% data variables.product.prodname_mobile %} for two-factor authentication. -1. Efetue o login em {% data variables.product.product_name %} com seu navegador, usando seu nome de usuário e senha. -2. Se você adicionou uma chave de segurança à sua conta, primeiro será solicitado que você insira e use uma chave de segurança. Para ignorar o uso de uma chave de segurança, clique em **Autenticar-se com o {% data variables.product.prodname_mobile %}** . - ![Desafio da autenticação de dois fatores no {% data variables.product.product_name %} com "Autenticar-se com o {% data variables.product.prodname_mobile %}" realçado](/assets/images/help/2fa/2fa-select-mobile.png) -3. {% data variables.product.product_name %} irá enviar uma notificação por push para verificar a sua tentativa de login. Abrir a notificação push ou abrir o aplicativo de {% data variables.product.prodname_mobile %} irá exibir um aviso que pedirá que você aprove ou rejeite esta tentativa de login. +1. Sign in to {% data variables.product.product_name %} with your browser, using your username and password. +2. If you have added a security key to your account, you'll first be prompted to insert and use a security key. To skip using a security key, click **Authenticate with {% data variables.product.prodname_mobile %}**. + ![Two-factor authentication challenge on {% data variables.product.product_name %} with "Authenticate with {% data variables.product.prodname_mobile %}" highlighted](/assets/images/help/2fa/2fa-select-mobile.png) +3. {% data variables.product.product_name %} will send you a push notification to verify your sign in attempt. Opening the push notification or opening the {% data variables.product.prodname_mobile %} app will display a prompt, asking you to approve or reject this sign in attempt. {% note %} - **Observação**: esse prompt pode exigir que você insira um número de dois dígitos exibido no navegador no qual você está entrando. + **Note**: This prompt may require you to enter a two-digit number displayed within the browser you are signing in to. {% endnote %} - ![{% data variables.product.prodname_mobile %} exige uma entrada de dois dígitos em duas etapas](/assets/images/help/2fa/2fa-mobile-number-challenge.png) + ![Two-factor authentication challenge with {% data variables.product.prodname_mobile %} requiring a two-digit input](/assets/images/help/2fa/2fa-mobile-number-challenge.png) - - Ao aprovar a tentativa de login usando {% data variables.product.prodname_mobile %}, seu navegador concluirá a tentativa de login automaticamente. - - Rejeitar a tentativa de login na tentativa impedirá que a autenticação seja concluída. Para obter mais informações, confira "[Como manter sua conta e seus dados seguros](/authentication/keeping-your-account-and-data-secure)". + - Upon approving the login attempt using {% data variables.product.prodname_mobile %}, your browser will complete the sign in attempt automatically. + - Rejecting the sign in attempt will prevent the authentication from finishing. For more information, see "[Keeping your account and data secure](/authentication/keeping-your-account-and-data-secure)." {% endif %} -## Usar a autenticação de dois fatores com a linha de comando +## Using two-factor authentication with the command line -Depois de habilitar a 2FA, você não usará mais sua senha para acessar {% data variables.product.product_name %} na linha de comando. Em vez disso, use o Git Credential Manager, um token de acesso pessoal ou uma chave SSH. +After you've enabled 2FA, you will no longer use your password to access {% data variables.product.product_name %} on the command line. Instead, use Git Credential Manager, a {% data variables.product.pat_generic %}, or an SSH key. -### Autenticação na linha de comando usando o Git Credential Manager +### Authenticating on the command line using Git Credential Manager -[O Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md) é um auxiliar de credencial do git seguro que é executado em Windows, macOS e Linux. Para obter mais informações sobre auxiliares de credenciais do Git, confira [Evitar repetições](https://git-scm.com/docs/gitcredentials#_avoiding_repetition) no livro Pro Git. +[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md) is a secure Git credential helper that runs on Windows, macOS, and Linux. For more information about Git credential helpers, see [Avoiding repetition](https://git-scm.com/docs/gitcredentials#_avoiding_repetition) in the Pro Git book. -As instruções de instalação variam de acordo com o sistema operacional do computador. Para obter mais informações, confira [Baixar e instalar](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md#download-and-install) no repositório GitCredentialManager/git-credential-manager. +Setup instructions vary based on your computer's operating system. For more information, see [Download and install](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md#download-and-install) in the GitCredentialManager/git-credential-manager repository. -### Autenticar na linha de comando usando HTTPS +### Authenticating on the command line using HTTPS -Após habilitação da 2FA, você deverá criar um token de acesso pessoal a ser usado como uma senha ao autenticar no {% data variables.product.product_name %} na linha de comando usando URLs HTTPS. +After you've enabled 2FA, you must create a {% data variables.product.pat_generic %} to use as a password when authenticating to {% data variables.product.product_name %} on the command line using HTTPS URLs. -Ao ser solicitado a fornecer um nome de usuário e uma senha na linha de comando, use seu nome de usuário no {% data variables.product.product_name %} e o token de acesso pessoal. O prompt da linha de comando não especificará que você deve inserir seu token de acesso pessoal quando solicitar sua senha. +When prompted for a username and password on the command line, use your {% data variables.product.product_name %} username and {% data variables.product.pat_generic %}. The command line prompt won't specify that you should enter your {% data variables.product.pat_generic %} when it asks for your password. -Para obter mais informações, confira "[Como criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)". +For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." -### Autenticar na linha de comando usando SSH +### Authenticating on the command line using SSH -Habilitar a 2FA não altera como você faz a autenticação no {% data variables.product.product_name %} na linha de comando usando URLs SSH. Para obter mais informações sobre como configurar e usar uma chave SSH, confira "[Como se conectar ao {% data variables.product.prodname_dotcom %} com o SSH](/articles/connecting-to-github-with-ssh/)". +Enabling 2FA doesn't change how you authenticate to {% data variables.product.product_name %} on the command line using SSH URLs. For more information about setting up and using an SSH key, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/articles/connecting-to-github-with-ssh/)." -## Usar a autenticação de dois fatores para acessar um repositório usando o Subversion +## Using two-factor authentication to access a repository using Subversion -Quando você acessa um repositório via Subversion, é preciso fornecer um token de acesso pessoal no lugar de digitar sua senha. Para obter mais informações, confira "[Como criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)". +When you access a repository via Subversion, you must provide a {% data variables.product.pat_generic %} instead of entering your password. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." -## Solução de problemas +## Troubleshooting -Em caso de perda de acesso às suas credenciais de autenticação de dois fatores, você poderá usar seus códigos de recuperação ou outro método de recuperação (se houver um configurado) para obter acesso novamente à sua conta. Para obter mais informações, confira "[Como recuperar sua conta se você perder suas credenciais de 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)". +If you lose access to your two-factor authentication credentials, you can use your recovery codes or another recovery method (if you've set one up) to regain access to your account. For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)." -Se a autenticação falhar várias vezes, talvez seja conveniente sincronizar o relógio do seu telefone com o provedor móvel. Muitas vezes, isso envolve verificar a opção "Set automatically" (Definir automaticamente) no relógio do seu telefone, em vez de fornecer seu próprio fuso horário. +If your authentication fails several times, you may wish to synchronize your phone's clock with your mobile provider. Often, this involves checking the "Set automatically" option on your phone's clock, rather than providing your own time zone. -## Leitura adicional +## Further reading -- "[Sobre a autenticação de dois fatores](/articles/about-two-factor-authentication)" -- "[Como configurar a autenticação de dois fatores](/articles/configuring-two-factor-authentication)" -- "[Como configurar métodos de recuperação da autenticação de dois fatores](/articles/configuring-two-factor-authentication-recovery-methods)" -- "[Como recuperar sua conta se você perder suas credenciais de autenticação de dois fatores](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" +- "[About two-factor authentication](/articles/about-two-factor-authentication)" +- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)" +- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)" +- "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" diff --git a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md index e50acb2f1c..ec06abf702 100644 --- a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md +++ b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md @@ -1,6 +1,6 @@ --- -title: Configurar a autenticação de dois fatores -intro: Você pode escolher entre várias opções de adicionar uma segunda fonte de autenticação à sua conta. +title: Configuring two-factor authentication +intro: You can choose among multiple options to add a second source of authentication to your account. redirect_from: - /articles/configuring-two-factor-authentication-via-a-totp-mobile-app - /articles/configuring-two-factor-authentication-via-text-message @@ -15,34 +15,28 @@ versions: topics: - 2FA shortTitle: Configure 2FA -ms.openlocfilehash: e7d6f4e9518bdd7ef7012e996f8ad72179711949 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147063559' --- -Você pode configurar a autenticação de dois fatores usando um aplicativo móvel{% ifversion fpt or ghec %} ou por mensagem de texto{% endif %}. Também é possível adicionar uma chave de segurança. +You can configure two-factor authentication using a mobile app{% ifversion fpt or ghec %} or via text message{% endif %}. You can also add a security key. -Recomendamos expressamente usar um aplicativo TOTP (Senhas Avulsas por Tempo Limitado) para configurar a 2FA.{% ifversion fpt or ghec %} Os aplicativos TOTP são mais confiáveis do que o SMS, especialmente para locais fora dos Estados Unidos.{% endif %} Os aplicativos TOTP são suporte ao backup seguro dos seus códigos de autenticação na nuvem e podem ser restaurados caso você perca o acesso ao seu dispositivo. +We strongly recommend using a time-based one-time password (TOTP) application to configure 2FA.{% ifversion fpt or ghec %} TOTP applications are more reliable than SMS, especially for locations outside the United States.{% endif %} TOTP apps support the secure backup of your authentication codes in the cloud and can be restored if you lose access to your device. {% warning %} -**Aviso:** -- Se você for membro{% ifversion fpt or ghec %}, gerente de cobrança{% endif %} ou colaborador externo de um repositório privado em uma organização que exige a autenticação de dois fatores, precisará deixar a organização para desabilitar a 2FA no {% data variables.product.product_location %}. -- Ao desabilitar a 2FA, você perderá acesso automaticamente à organização e a qualquer bifurcação privada que tenha dos repositórios privados da organização. Para recuperar o acesso à organização e às bifurcações, reabilite a autenticação de dois fatores e entre em contato com um proprietário da organização. +**Warning:** +- If you're a member{% ifversion fpt or ghec %}, billing manager,{% endif %} or outside collaborator to a private repository of an organization that requires two-factor authentication, you must leave the organization before you can disable 2FA on {% data variables.location.product_location %}. +- If you disable 2FA, you will automatically lose access to the organization and any private forks you have of the organization's private repositories. To regain access to the organization and your forks, re-enable two-factor authentication and contact an organization owner. {% endwarning %} {% ifversion fpt or ghec %} -Um membro de uma {% data variables.product.prodname_emu_enterprise %} não pode configurar a 2FA para a respectiva conta do {% data variables.product.prodname_managed_user %}, a menos que esteja conectado como o usuário de configuração. Para usuários que não sejam o usuário de configuração, um administrador precisa configurar a 2FA no IdP (provedor de identidade). +If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you cannot configure 2FA for your {% data variables.enterprise.prodname_managed_user %} account unless you're signed in as the setup user. For users other than the setup user, an administrator must configure 2FA on your identity provider (IdP). {% endif %} -## Configurar a autenticação de dois fatores usando um app móvel TOTP +## Configuring two-factor authentication using a TOTP mobile app -Um aplicativo de senhas avulsas por tempo limitado (TOTP, Time-based One-Time Password) gera automaticamente um código de autenticação que é alterado após um determinado período. É recomendável usar apps TOTP baseados na nuvem, como: +A time-based one-time password (TOTP) application automatically generates an authentication code that changes after a certain period of time. We recommend using cloud-based TOTP apps such as: - [1Password](https://support.1password.com/one-time-passwords/) - [Authy](https://authy.com/guides/github/) - [LastPass Authenticator](https://lastpass.com/auth/) @@ -50,99 +44,112 @@ Um aplicativo de senhas avulsas por tempo limitado (TOTP, Time-based One-Time Pa {% tip %} -**Dica:** para configurar a autenticação via TOTP em vários dispositivos, durante a configuração, digitalize o código QR usando todos os dispositivos ao mesmo tempo. Se a 2FA já estiver habilitada e você desejar adicionar outro dispositivo, será necessário reconfigurar a 2FA nas configurações de segurança. +**Tip**: To configure authentication via TOTP on multiple devices, during setup, scan the QR code using each device at the same time. If 2FA is already enabled and you want to add another device, you must re-configure 2FA from your security settings. {% endtip %} -1. Baixe um app TOTP. -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security %} {% data reusables.two_fa.enable-two-factor-authentication %} {%- ifversion fpt or ghec or ghes %} -5. Em "Autenticação de dois fatores", selecione **Configurar usando um aplicativo** e clique em **Continuar**. -6. Em "Verificação de autenticação", siga um dos passos abaixo: - - Faça a leitura do código QR com o app do dispositivo móvel. Após a leitura, o app exibirá um código de seis dígitos que pode ser inserido no {% data variables.product.product_name %}. - - Se você não puder digitalizar o código QR, clique em **Insira este código de texto** para ver um código que pode ser inserido manualmente no aplicativo TOTP. - ![Clique em Insira este código](/assets/images/help/2fa/2fa_wizard_app_click_code.png) -7. O aplicativo móvel TOTP salva a sua conta em {% data variables.product.product_location %} e gera um novo código de autenticação a cada poucos segundos. Em {% data variables.product.product_name %}, digite o código no campo em "Insira o código de seis dígitos no aplicativo". Se os códigos de recuperação não forem exibidos automaticamente, clique em **Continuar**. -![Campo Inserir código do TOTP](/assets/images/help/2fa/2fa_wizard_app_enter_code.png) {% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %} {%- else %} -5. Na página Autenticação de dois fatores, selecione **Configurar usando um aplicativo**. -6. Salve seus códigos de recuperação em um local seguro. Seus códigos de recuperação podem ajudar você a ter acesso novamente à sua conta no caso de perda do acesso. - - Para salvar os códigos de recuperação no dispositivo, clique em **Baixar**. - - Para salvar uma cópia impressa dos códigos de recuperação, clique em **Imprimir**. - - Para copiar os códigos de recuperação para armazenamento em um gerenciador de senhas, clique em **Copiar**. - ![Lista de códigos de recuperação com opção para baixar, imprimir ou copiar os códigos](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png) -7. Depois de salvar seus códigos de recuperação de dois fatores, clique em **Avançar**. -8. Na página de autenticação de dois fatores, siga um destes procedimentos: - - Faça a leitura do código QR com o app do dispositivo móvel. Após a leitura, o app exibirá um código de seis dígitos que pode ser inserido no {% data variables.product.product_name %}. - - Se você não puder digitalizar o código QR, clique em **Insira este código de texto** para ver um código que pode ser copiado e inserido manualmente no {% data variables.product.product_name %}. - ![Clique em Insira este código](/assets/images/help/2fa/totp-click-enter-code.png) -9. O aplicativo móvel TOTP salva a sua conta em {% data variables.product.product_location %} e gera um novo código de autenticação a cada poucos segundos. Na página da 2FA do {% data variables.product.product_name %}, digite o código e clique em **Habilitar**. - ![Campo Habilitar TOTP](/assets/images/help/2fa/totp-enter-code.png) {%- endif %} {% data reusables.two_fa.test_2fa_immediately %} +1. Download a TOTP app. +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.security %} +{% data reusables.two_fa.enable-two-factor-authentication %} +{%- ifversion fpt or ghec or ghes %} +5. Under "Two-factor authentication", select **Set up using an app** and click **Continue**. +6. Under "Authentication verification", do one of the following: + - Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}. + - If you can't scan the QR code, click **enter this text code** to see a code that you can manually enter in your TOTP app instead. + ![Click enter this code](/assets/images/help/2fa/2fa_wizard_app_click_code.png) +7. The TOTP mobile application saves your account on {% data variables.location.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code from the application". If your recovery codes are not automatically displayed, click **Continue**. +![TOTP enter code field](/assets/images/help/2fa/2fa_wizard_app_enter_code.png) +{% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %} +{%- else %} +5. On the Two-factor authentication page, click **Set up using an app**. +6. Save your recovery codes in a safe place. Your recovery codes can help you get back into your account if you lose access. + - To save your recovery codes on your device, click **Download**. + - To save a hard copy of your recovery codes, click **Print**. + - To copy your recovery codes for storage in a password manager, click **Copy**. + ![List of recovery codes with option to download, print, or copy the codes](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png) +7. After saving your two-factor recovery codes, click **Next**. +8. On the Two-factor authentication page, do one of the following: + - Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}. + - If you can't scan the QR code, click **enter this text code** to see a code you can copy and manually enter on {% data variables.product.product_name %} instead. + ![Click enter this code](/assets/images/help/2fa/totp-click-enter-code.png) +9. The TOTP mobile application saves your account on {% data variables.location.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, on the 2FA page, type the code and click **Enable**. + ![TOTP Enable field](/assets/images/help/2fa/totp-enter-code.png) +{%- endif %} +{% data reusables.two_fa.test_2fa_immediately %} {% ifversion fpt or ghec %} -## Configurar a autenticação de dois fatores usando mensagens de texto +## Configuring two-factor authentication using text messages -Se não for possível autenticar usando um app móvel TOTP, você pode autenticar usando mensagens SMS. Também é possível fornecer um segundo número para um dispositivo de fallback. Se você perder acesso ao dispositivo principal e aos códigos de recuperação, um número de SMS de backup pode ajudar a acessar a sua conta. +If you're unable to authenticate using a TOTP mobile app, you can authenticate using SMS messages. You can also provide a second number for a fallback device. If you lose access to both your primary device and your recovery codes, a backup SMS number can get you back in to your account. -Antes de usar esse método, certifique-se de que é possível receber mensagens de texto. Pode ser que as operadores apliquem taxas. +Before using this method, be sure that you can receive text messages. Carrier rates may apply. {% warning %} -**Aviso:** **recomendamos expressamente** usar um aplicativo TOTP para a autenticação de dois fatores em vez de SMS. O {% data variables.product.product_name %} não permite enviar mensagens SMS a telefones de todos os países. Antes de configurar a autenticação por mensagem de texto, veja a lista de países onde o {% data variables.product.product_name %} aceita a autenticação por SMS. Para obter mais informações, confira "[Países em que há suporte para a autenticação por SMS](/articles/countries-where-sms-authentication-is-supported)". +**Warning:** We **strongly recommend** using a TOTP application for two-factor authentication instead of SMS. {% data variables.product.product_name %} doesn't support sending SMS messages to phones in every country. Before configuring authentication via text message, review the list of countries where {% data variables.product.product_name %} supports authentication via SMS. For more information, see "[Countries where SMS authentication is supported](/articles/countries-where-sms-authentication-is-supported)". {% endwarning %} -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security %} {% data reusables.two_fa.enable-two-factor-authentication %} -4. Em "Autenticação de dois fatores", selecione **Configurar usando SMS** e clique em **Continuar**. -5. Em "Verificação de autenticação", selecione o código do seu país e digite seu número de telefone celular, incluindo o código de área. Quando as informações estiverem corretas, clique em **Enviar código de autenticação**. +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.security %} +{% data reusables.two_fa.enable-two-factor-authentication %} +4. Under "Two-factor authentication", select **Set up using SMS** and click **Continue**. +5. Under "Authentication verification", select your country code and type your mobile phone number, including the area code. When your information is correct, click **Send authentication code**. - ![Tela de SMS da 2FA](/assets/images/help/2fa/2fa_wizard_sms_send.png) + ![2FA SMS screen](/assets/images/help/2fa/2fa_wizard_sms_send.png) -6. Você receberá uma mensagem de texto com um código de segurança. No {% data variables.product.product_name %}, insira o código no campo em "Insira o código de seis dígitos enviado para o seu telefone" e clique em **Continuar**. +6. You'll receive a text message with a security code. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code sent to your phone" and click **Continue**. - ![Campo Continuar do SMS para a 2FA](/assets/images/help/2fa/2fa_wizard_sms_enter_code.png) {% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %} {% data reusables.two_fa.test_2fa_immediately %} + ![2FA SMS continue field](/assets/images/help/2fa/2fa_wizard_sms_enter_code.png) +{% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %} +{% data reusables.two_fa.test_2fa_immediately %} {% endif %} -## Configurar a autenticação de dois fatores usando uma chave de segurança +## Configuring two-factor authentication using a security key {% data reusables.two_fa.after-2fa-add-security-key %} -Na maioria dos dispositivos e navegadores, você pode usar uma chave de segurança física por USB ou NFC. Alguns navegadores podem usar um leitor de impressões digitais, reconhecimento facial ou senha/PIN no seu dispositivo como chave de segurança. +On most devices and browsers, you can use a physical security key over USB or NFC. Some browsers can use the fingerprint reader, facial recognition, or password/PIN on your device as a security key. -A autenticação com uma chave de segurança é *secundária* à autenticação com um aplicativo TOTP{% ifversion fpt or ghec %} ou uma mensagem de texto{% endif %}. Se você perder sua chave de segurança, você poderá usar o código do seu telefone para entrar. +Authentication with a security key is *secondary* to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}. If you lose your security key, you'll still be able to use your phone's code to sign in. -1. Você já precisa ter configurado a 2FA usando um aplicativo móvel TOTP{% ifversion fpt or ghec %} ou por SMS{% endif %}. -2. Certifique-se de que você tem uma chave de segurança compatível com o WebAuthn inserido em seu computador. -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security %} -5. Ao lado de "Chaves de segurança", clique em **Adicionar**. - ![Opção Adicionar chaves de segurança](/assets/images/help/2fa/add-security-keys-option.png) -6. Em "Chaves de segurança", clique em **Registrar nova chave de segurança**. - ![Como registrar uma nova chave de segurança](/assets/images/help/2fa/security-key-register.png) -7. Digite um apelido para a chave de segurança e clique em **Adicionar**. - ![Como fornecer um apelido para uma chave de segurança](/assets/images/help/2fa/security-key-nickname.png) -8. Ative a chave de segurança seguindo as orientações na documentação da sua chave de segurança. - ![Solicitação de chave de segurança](/assets/images/help/2fa/security-key-prompt.png) -9. Verifique se você baixou e pode acessar os códigos de recuperação. Se ainda não os baixou ou se deseja gerar outro conjunto de códigos, baixe seus códigos e salve-os em um local seguro. Caso perca o acesso à sua conta, é possível usar os códigos de recuperação para voltar a ela. Para obter mais informações, confira "[Como recuperar sua conta se você perder suas credenciais de 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)". - ![Botão Baixar códigos de recuperação](/assets/images/help/2fa/2fa-recover-during-setup.png) {% data reusables.two_fa.test_2fa_immediately %} +1. You must have already configured 2FA via a TOTP mobile app{% ifversion fpt or ghec %} or via SMS{% endif %}. +2. Ensure that you have a WebAuthn compatible security key inserted into your computer. +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.security %} +5. Next to "Security keys", click **Add**. + ![Add security keys option](/assets/images/help/2fa/add-security-keys-option.png) +6. Under "Security keys", click **Register new security key**. + ![Registering a new security key](/assets/images/help/2fa/security-key-register.png) +7. Type a nickname for the security key, then click **Add**. + ![Providing a nickname for a security key](/assets/images/help/2fa/security-key-nickname.png) +8. Activate your security key, following your security key's documentation. + ![Prompt for a security key](/assets/images/help/2fa/security-key-prompt.png) +9. Confirm that you've downloaded and can access your recovery codes. If you haven't already, or if you'd like to generate another set of codes, download your codes and save them in a safe place. If you lose access to your account, you can use your recovery codes to get back into your account. For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)." + ![Download recovery codes button](/assets/images/help/2fa/2fa-recover-during-setup.png) +{% data reusables.two_fa.test_2fa_immediately %} {% ifversion fpt or ghec %} -## Configurando a autenticação de dois fatores usando {% data variables.product.prodname_mobile %} +## Configuring two-factor authentication using {% data variables.product.prodname_mobile %} -Você pode usar {% data variables.product.prodname_mobile %} para 2FA ao efetuar o login na sua conta {% data variables.product.prodname_dotcom %} em um navegador web. A 2FA com o {% data variables.product.prodname_mobile %} não depende do TOTP e usa criptografia de chave pública para proteger sua conta. +You can use {% data variables.product.prodname_mobile %} for 2FA when signing into your {% data variables.product.prodname_dotcom %} account in a web browser. 2FA with {% data variables.product.prodname_mobile %} does not rely on TOTP, and instead uses public-key cryptography to secure your account. -Depois que você tiver configurado um aplicativo TOTP ou SMS, você também poderá usar {% data variables.product.prodname_mobile %} para efetuar a autenticação. Se, posteriormente, você não tiver mais acesso a {% data variables.product.prodname_mobile %}, você ainda poderá usar as chaves de segurança ou aplicativos TOTP para efetuar o login. +Once you have configured a TOTP application, or SMS, you can also use {% data variables.product.prodname_mobile %} to authenticate. If, in the future, you no longer have access to {% data variables.product.prodname_mobile %}, you will still be able to use security keys or TOTP applications to sign in. -1. Você deve ter configurado a 2FA por meio de um aplicativo móvel TOTP ou via SMS. -2. Instale o [{% data variables.product.prodname_mobile %}](https://github.com/mobile). -3. Efetue o login na sua conta de {% data variables.product.product_name %} em {% data variables.product.prodname_mobile %}. +1. You must have already configured 2FA via a TOTP mobile app or via SMS. +2. Install [{% data variables.product.prodname_mobile %}](https://github.com/mobile). +3. Sign in to your {% data variables.product.product_name %} account from {% data variables.product.prodname_mobile %}. -Após o login, você poderá usar o seu dispositivo para 2FA. +After signing in, you can now use your device for 2FA. {% endif %} -## Leitura adicional +## Further reading -- "[Sobre a autenticação de dois fatores](/articles/about-two-factor-authentication)" -- "[Como configurar métodos de recuperação da autenticação de dois fatores](/articles/configuring-two-factor-authentication-recovery-methods)" -- "[Como acessar o {% data variables.product.prodname_dotcom %} usando a autenticação de dois fatores](/articles/accessing-github-using-two-factor-authentication)" -- "[Como recuperar sua conta se você perder suas credenciais de 2FA](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" -- "[Como criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)" +- "[About two-factor authentication](/articles/about-two-factor-authentication)" +- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)" +- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)" +- "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" +- "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)" diff --git a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md index 2efd25b165..ee314edd92 100644 --- a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md +++ b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md @@ -1,6 +1,6 @@ --- -title: Proteger sua conta com a autenticação de dois fatores (2FA) -intro: 'Você pode configurar sua conta no {% data variables.product.product_location %} para exigir um código de autenticação além da sua senha quando você efetuar o login.' +title: Securing your account with two-factor authentication (2FA) +intro: 'You can set up your account on {% data variables.location.product_location %} to require an authentication code in addition to your password when you sign in.' redirect_from: - /categories/84/articles - /categories/two-factor-authentication-2fa @@ -22,11 +22,5 @@ children: - /countries-where-sms-authentication-is-supported - /disabling-two-factor-authentication-for-your-personal-account shortTitle: Secure your account with 2FA -ms.openlocfilehash: 886af1b083719e4381fcc30fcd4855507d718889 -ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145083572' --- diff --git a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md index 573bb0ae91..6c4ac89dc0 100644 --- a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md +++ b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md @@ -1,6 +1,6 @@ --- -title: Recuperar sua conta ao perder as credenciais 2FA -intro: 'Se você perder acesso às suas credenciais de autenticação de dois fatores, você poderá usar seus códigos de recuperação ou outra opção de recuperação, para recuperar o acesso à sua conta.' +title: Recovering your account if you lose your 2FA credentials +intro: 'If you lose access to your two-factor authentication credentials, you can use your recovery codes, or another recovery option, to regain access to your account.' redirect_from: - /articles/recovering-your-account-if-you-lost-your-2fa-credentials - /articles/authenticating-with-an-account-recovery-token @@ -14,18 +14,12 @@ versions: topics: - 2FA shortTitle: Recover an account with 2FA -ms.openlocfilehash: 1a93d77d4da76a6efbc96ba5d80d0fe7e800c08a -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145083573' --- {% ifversion fpt or ghec %} {% warning %} -**Avisos**: +**Warnings**: - {% data reusables.two_fa.support-may-not-help %} @@ -33,83 +27,84 @@ ms.locfileid: '145083573' {% endif %} -## Usar um código de recuperação da autenticação de dois fatores +## Using a two-factor authentication recovery code -Use um dos códigos de recuperação para obter acesso automaticamente à sua conta. Seus códigos de recuperação podem estar salvos em um gerenciador de senhas ou na pasta de downloads do seu computador. O nome de arquivo padrão para códigos de recuperação é `github-recovery-codes.txt`. Para obter mais informações sobre códigos de recuperação, confira "[Como configurar métodos de recuperação da autenticação de dois fatores](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)". +Use one of your recovery codes to automatically regain entry into your account. You may have saved your recovery codes to a password manager or your computer's downloads folder. The default filename for recovery codes is `github-recovery-codes.txt`. For more information about recovery codes, see "[Configuring two-factor authentication recovery methods](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)." -1. Digite seu nome de usuário e senha para solicitar autenticação. +1. Type your username and password to prompt authentication. {% warning %} - **Aviso**: {% data reusables.accounts.you-must-know-your-password %} + **Warning**: {% data reusables.accounts.you-must-know-your-password %} {% endwarning %} {% ifversion fpt or ghec %} -1. Em "Tendo problemas?", clique em **Usar um código de recuperação ou solicitar uma redefinição**. +1. Under "Having problems?", click **Use a recovery code or request a reset**. - ![Captura de tela do link usado para usar um código de recuperação](/assets/images/help/2fa/2fa-recovery-code-link.png) {%- else %} -1. Na página 2FA, em "Não está com seu telefone?", clique em **Inserir um código de recuperação de dois fatores**. + ![Screenshot of link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png) +{%- else %} +1. On the 2FA page, under "Don't have your phone?", click **Enter a two-factor recovery code**. - ![Captura de tela do link para usar um código de recuperação](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %} -1. Digite um dos códigos de recuperação e clique em **Verificar**. + ![Screenshot of link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %} +1. Type one of your recovery codes, then click **Verify**. - ![Campo para digitar um código de recuperação e botão Verify (Verificar)](/assets/images/help/2fa/2fa-type-verify-recovery-code.png) + ![Field to type a recovery code and Verify button](/assets/images/help/2fa/2fa-type-verify-recovery-code.png) {% ifversion fpt or ghec %} -## Autenticar com um número de telefone alternativo +## Authenticating with a fallback number -Se você perder o acesso ao seu aplicativo TOTP principal ou número de telefone, é possível fornecer um código de autenticação de dois fatores enviado para seu número de telefone alternativo e conseguir acessar automaticamente sua conta. +If you lose access to your primary TOTP app or phone number, you can provide a two-factor authentication code sent to your fallback number to automatically regain access to your account. {% endif %} -## Autenticar com uma chave de segurança +## Authenticating with a security key -Se você configurou a autenticação de dois fatores com uma chave de segurança, você pode usar a chave de segurança como método de autenticação secundário para reaver automaticamente o acesso à sua conta. Para obter mais informações, confira "[Como configurar a autenticação de dois fatores](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)". +If you configured two-factor authentication using a security key, you can use your security key as a secondary authentication method to automatically regain access to your account. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)." {% ifversion fpt or ghec %} -## Efetuar a autenticação com um dispositivo verificado, token SSH ou token de acesso pessoal +## Authenticating with a verified device, SSH token, or {% data variables.product.pat_generic %} -Se você souber a sua senha para {% data variables.product.product_location %}, mas não tiver credenciais de autenticação de dois fatores ou seus códigos de recuperação de autenticação em de dois fatores, você poderá receber por e-mail uma senha única para começar o processo de verificação e recuperar o acesso à sua conta. +If you know your password for {% data variables.location.product_location %} but don't have the two-factor authentication credentials or your two-factor authentication recovery codes, you can have a one-time password sent to your verified email address to begin the verification process and regain access to your account. {% note %} -**Observação**: por motivos de segurança, a recuperação do acesso à sua conta pela autenticação com uma senha avulsa pode levar até três dias úteis. {% data variables.product.company_short %} não analisará solicitações adicionais enviadas nesse tempo. +**Note**: For security reasons, regaining access to your account by authenticating with a one-time password can take up to three business days. {% data variables.product.company_short %} will not review additional requests submitted during this time. {% endnote %} -Você pode usar as suas credenciais de autenticação de dois fatores ou os códigos de recuperação de dois fatores para recuperar o acesso à sua conta a qualquer momento no período de espera de 3 a 5 dias. +You can use your two-factor authentication credentials or two-factor authentication recovery codes to regain access to your account anytime during the 3-5 day waiting period. -1. Digite seu nome de usuário e senha para solicitar autenticação. +1. Type your username and password to prompt authentication. {% warning %} - **Aviso**: {% data reusables.accounts.you-must-know-your-password %} + **Warning**: {% data reusables.accounts.you-must-know-your-password %} {% endwarning %} -1. Em "Tendo problemas?", clique em **Usar um código de recuperação ou solicitar uma redefinição**. +1. Under "Having problems?", click **Use a recovery code or request a reset**. - ![Captura de tela do link se você não tiver seu dispositivo 2FA ou códigos de recuperação](/assets/images/help/2fa/no-access-link.png) -1. À direita de "Bloqueado?", clique em **Tentar recuperar sua conta**. + ![Screenshot of link if you don't have your 2fa device or recovery codes](/assets/images/help/2fa/no-access-link.png) +1. To the right of "Locked out?", click **Try recovering your account**. - ![Captura de tela do link para tentar recuperar sua conta](/assets/images/help/2fa/try-recovering-your-account-link.png) -1. Clique em **Entendi. Começar** para solicitar uma redefinição das configurações de autenticação. + ![Screenshot of link to try recovering your account](/assets/images/help/2fa/try-recovering-your-account-link.png) +1. Click **I understand, get started** to request a reset of your authentication settings. - ![Captura de tela do botão para iniciar a redefinição das configurações de autenticação](/assets/images/help/2fa/reset-auth-settings.png) -1. Clique em **Enviar senha avulsa** para enviar uma senha avulsa a todos os endereços qualificados associados à sua conta. Apenas e-mails verificados são elegíveis para a recuperação de conta. Se você restringiu as redefinições de senha para seus endereços primários e/ou de backup, esses endereços são os únicos elegíveis para a recuperação de conta. + ![Screenshot of button to start reset of authentication settings](/assets/images/help/2fa/reset-auth-settings.png) +1. Click **Send one-time password** to send a one-time password to all eligible addresses associated with your account. Only verified emails are eligible for account recovery. If you've restricted password resets to your primary and/or backup addresses, these addresses are the only addresses eligible for account recovery. - ![Captura de tela do botão para enviar uma senha única](/assets/images/help/2fa/send-one-time-password.png) -1. Em "Única senha", digite a senha temporária do endereço e-mail de recuperação {% data variables.product.prodname_dotcom %} enviada. + ![Screenshot of button to send one-time password](/assets/images/help/2fa/send-one-time-password.png) +1. Under "One-time password", type the temporary password from the recovery email {% data variables.product.prodname_dotcom %} sent. - ![Captura de tela do campo para digitar senha única](/assets/images/help/2fa/one-time-password-field.png) -1. Clique em **Verificar endereço de email**. + ![Screenshot of field to type one-time password](/assets/images/help/2fa/one-time-password-field.png) +1. Click **Verify email address**. - ![Captura de tela do botão para verificar o endereço de e-mail](/assets/images/help/2fa/verify-email-address.png) -1. Escolha um fator de verificação alternativo. - - Se você já usou seu dispositivo atual para fazer logon nessa conta antes e deseja usar o dispositivo para verificação, clique em **Verificar com este dispositivo**. - - Se você já tiver configurado uma chave SSH nessa conta e quiser usar a chave SSH para verificação, clique em **Chave SSH**. - - Se você já configurou um token de acesso pessoal e deseja usar o token de acesso pessoal para verificação, clique em **Token de acesso pessoal**. + ![Screenshot of button to verify email address](/assets/images/help/2fa/verify-email-address.png) +1. Choose an alternative verification factor. + - If you've used your current device to log into this account before and would like to use the device for verification, click **Verify with this device**. + - If you've previously set up an SSH key on this account and would like to use the SSH key for verification, click **SSH key**. + - If you've previously set up a {% data variables.product.pat_generic %} and would like to use the {% data variables.product.pat_generic %} for verification, click **{% data variables.product.pat_generic_caps %}**. - ![Captura de tela de botões para verificação alternativa](/assets/images/help/2fa/alt-verifications.png) -1. Um integrante de {% data variables.contact.github_support %} irá revisar a sua solicitação e enviar um e-mail para você em três dias úteis. Se a sua solicitação for aprovada, você receberá um link para concluir o processo de recuperação de conta. Se sua solicitação for negada, o e-mail incluirá uma forma de entrar em contato com o suporte para esclarecer outras dúvidas. + ![Screenshot of buttons for alternative verification](/assets/images/help/2fa/alt-verifications.png) +1. A member of {% data variables.contact.github_support %} will review your request and email you within three business days. If your request is approved, you'll receive a link to complete your account recovery process. If your request is denied, the email will include a way to contact support with any additional questions. {% endif %} diff --git a/translations/pt-BR/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md b/translations/pt-BR/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md index 87fb5ba3dc..d134f687e9 100644 --- a/translations/pt-BR/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md +++ b/translations/pt-BR/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md @@ -1,6 +1,6 @@ --- -title: 'Erro: agente com falha ao entrar' -intro: 'Em circunstâncias raras, conectar-se ao {% data variables.product.product_name %} via SSH no Linux produz o erro `"Agent admitted failure to sign using the key"`. Siga estas etapas para resolver o problema.' +title: 'Error: Agent admitted failure to sign' +intro: 'In rare circumstances, connecting to {% data variables.product.product_name %} via SSH on Linux produces the error `"Agent admitted failure to sign using the key"`. Follow these steps to resolve the problem.' redirect_from: - /articles/error-agent-admitted-failure-to-sign-using-the-key - /articles/error-agent-admitted-failure-to-sign @@ -14,14 +14,8 @@ versions: topics: - SSH shortTitle: Agent failure to sign -ms.openlocfilehash: eceb783df61b403a6b94b8eda84be62e63aa5ead -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145083557' --- -Ao tentar se conectar via SSH ao {% data variables.product.product_location %} em um computador Linux, você poderá receber a seguinte mensagem: +When trying to SSH into {% data variables.location.product_location %} on a Linux computer, you may see the following message in your terminal: ```shell $ ssh -vT git@{% data variables.command_line.codeblock %} @@ -31,28 +25,28 @@ $ ssh -vT git@{% data variables.command_line.codeblock %} > Permission denied (publickey). ``` -Para obter mais detalhes, confira este relatório de problemas. +For more details, see this issue report. -## Resolução +## Resolution -Corrija esse erro carregando suas chaves no agente SSH com `ssh-add`: +You should be able to fix this error by loading your keys into your SSH agent with `ssh-add`: ```shell # start the ssh-agent in the background $ eval "$(ssh-agent -s)" > Agent pid 59566 $ ssh-add -> Enter passphrase for /home/you/.ssh/id_rsa: [tippy tap] -> Identity added: /home/you/.ssh/id_rsa (/home/you/.ssh/id_rsa) +> Enter passphrase for /home/YOU/.ssh/id_rsa: [tippy tap] +> Identity added: /home/YOU/.ssh/id_rsa (/home/YOU/.ssh/id_rsa) ``` -Se a sua chave não tiver o nome de arquivo padrão (`/.ssh/id_rsa`), você precisará transmitir esse caminho para `ssh-add`: +If your key does not have the default filename (`/.ssh/id_rsa`), you'll have to pass that path to `ssh-add`: ```shell # start the ssh-agent in the background $ eval "$(ssh-agent -s)" > Agent pid 59566 $ ssh-add ~/.ssh/my_other_key -> Enter passphrase for /home/you/.ssh/my_other_key: [tappity tap tap] -> Identity added: /home/you/.ssh/my_other_key (/home/you/.ssh/my_other_key) +> Enter passphrase for /home/YOU/.ssh/my_other_key: [tappity tap tap] +> Identity added: /home/YOU/.ssh/my_other_key (/home/YOU/.ssh/my_other_key) ``` diff --git a/translations/pt-BR/content/authentication/troubleshooting-ssh/error-key-already-in-use.md b/translations/pt-BR/content/authentication/troubleshooting-ssh/error-key-already-in-use.md index 4176334d55..315f4701b6 100644 --- a/translations/pt-BR/content/authentication/troubleshooting-ssh/error-key-already-in-use.md +++ b/translations/pt-BR/content/authentication/troubleshooting-ssh/error-key-already-in-use.md @@ -1,6 +1,6 @@ --- -title: 'Erro: chave em uso' -intro: 'Este erro ocorre quando você tenta [adicionar uma chave](/articles/adding-a-new-ssh-key-to-your-github-account) que já foi adicionada a outra conta ou repositório.' +title: 'Error: Key already in use' +intro: 'This error occurs when you try to [add a key](/articles/adding-a-new-ssh-key-to-your-github-account) that''s already been added to another account or repository.' redirect_from: - /articles/error-key-already-in-use - /github/authenticating-to-github/error-key-already-in-use @@ -12,39 +12,33 @@ versions: ghec: '*' topics: - SSH -ms.openlocfilehash: d202de2efe05951fe829a8198b20831fc15bbd72 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145083554' --- -## Descobrir onde a chave foi usada +## Finding where the key has been used -Para determinar o local em que a chave já foi usada, abra um terminal e digite o comando `ssh`. Use o sinalizador `-i` para fornecer o caminho para a chave que deseja verificar: +To determine where the key has already been used, open a terminal and type the `ssh` command. Use the `-i` flag to provide the path to the key you want to check: ```shell -$ ssh -T -ai ~/.ssh/id_rsa git@{% data variables.command_line.codeblock %} -# Connect to {% data variables.product.product_location %} using a specific ssh key -> Hi username! You've successfully authenticated, but GitHub does not +$ ssh -T -ai ~/.ssh/id_rsa git@{% data variables.command_line.codeblock %} +# Connect to {% data variables.location.product_location %} using a specific ssh key +> Hi USERNAME! You've successfully authenticated, but GitHub does not > provide shell access. ``` -O *nome de usuário* na resposta é a conta do {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} à qual a chave está anexada no momento. Se a resposta se parece com "nome de usuário/repositório", a chave foi anexada a um repositório como uma [*chave de implantação*](/guides/managing-deploy-keys#deploy-keys). +The *username* in the response is the account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} that the key is currently attached to. If the response looks something like "username/repo", the key has been attached to a repository as a [*deploy key*](/guides/managing-deploy-keys#deploy-keys). -Para forçar o SSH a usar apenas a chave fornecida na linha de comando, use `-o` para adicionar a opção `IdentitiesOnly=yes`: +To force SSH to use only the key provided on the command line, use `-o` to add the `IdentitiesOnly=yes` option: ```shell -$ ssh -v -o "IdentitiesOnly=yes" -i ~/.ssh/id_rsa git@{% data variables.command_line.codeblock %} +$ ssh -v -o "IdentitiesOnly=yes" -i ~/.ssh/id_rsa git@{% data variables.command_line.codeblock %} ``` -## Corrigir o problema +## Fixing the issue -Para resolver o problema, primeiro, remova a chave da outra conta ou do outro repositório e [adicione-a à sua conta](/articles/adding-a-new-ssh-key-to-your-github-account). +To resolve the issue, first remove the key from the other account or repository and then [add it to your account](/articles/adding-a-new-ssh-key-to-your-github-account). -Se você não tiver permissões para transferir a chave e não puder entrar em contato com um usuário que consiga fazer isso, remova as chaves e [gere outras](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent). +If you don't have permissions to transfer the key, and can't contact a user who does, remove the keypair and [generate a brand new one](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent). -## Chaves de implantação +## Deploy keys -Depois que uma chave tiver sido vinculada a um repositório como uma chave de implantação, ela não poderá ser usada em outro repositório. Se estiver encontrando esse erro ao configurar chaves de implantação, confira "[Como gerenciar chaves de implantação](/guides/managing-deploy-keys)". +Once a key has been attached to one repository as a deploy key, it cannot be used on another repository. If you're running into this error while setting up deploy keys, see "[Managing deploy keys](/guides/managing-deploy-keys)." diff --git a/translations/pt-BR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/translations/pt-BR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md index 8bbd685fb8..9f094aa659 100644 --- a/translations/pt-BR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md +++ b/translations/pt-BR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md @@ -1,6 +1,6 @@ --- -title: Usar SSH na porta HTTPS -intro: 'Às vezes, os firewalls se recusam a permitir conexões SSH completamente. Se usar [clonagem de HTTPS com armazenamento de credenciais em cache](/github/getting-started-with-github/caching-your-github-credentials-in-git) não for uma opção, experimente clonar usando uma conexão SSH na porta HTTPS. A maioria das regras de firewall deve permitir isso, mas o servidores proxy podem interferir.' +title: Using SSH over the HTTPS port +intro: 'Sometimes, firewalls refuse to allow SSH connections entirely. If using [HTTPS cloning with credential caching](/github/getting-started-with-github/caching-your-github-credentials-in-git) is not an option, you can attempt to clone using an SSH connection made over the HTTPS port. Most firewall rules should allow this, but proxy servers may interfere.' redirect_from: - /articles/using-ssh-over-the-https-port - /github/authenticating-to-github/using-ssh-over-the-https-port @@ -11,34 +11,28 @@ versions: topics: - SSH shortTitle: Use SSH over HTTPS port -ms.openlocfilehash: 47bdb96fac65d9432dfc54f671366d1b6c153556 -ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147883398' --- {% tip %} -**Usuários {% data variables.product.prodname_ghe_server %}** : acessar {% data variables.product.prodname_ghe_server %} via SSH por porta HTTPS atualmente não tem suporte. +**{% data variables.product.prodname_ghe_server %} users**: Accessing {% data variables.product.prodname_ghe_server %} via SSH over the HTTPS port is currently not supported. {% endtip %} -Para testar se o SSH na porta HTTPS é possível, execute este comando SSH: +To test if SSH over the HTTPS port is possible, run this SSH command: ```shell $ ssh -T -p 443 git@ssh.github.com -> Hi username! You've successfully authenticated, but GitHub does not +> Hi USERNAME! You've successfully authenticated, but GitHub does not > provide shell access. ``` -Se deu certo, ótimo! Caso contrário, talvez seja necessário [seguir nosso guia de solução de problemas](/articles/error-permission-denied-publickey). +If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey). -## Habilitar conexões SSH por HTTPS +## Enabling SSH connections over HTTPS -Se você conseguir fazer SSH para `git@ssh.{% data variables.command_line.backticks %}` por meio da porta 443, você poderá substituir as configurações SSH para forçar qualquer conexão ao {% data variables.product.product_location %} a ser executada nesse servidor e nessa porta. +If you are able to SSH into `git@ssh.{% data variables.command_line.backticks %}` over port 443, you can override your SSH settings to force any connection to {% data variables.location.product_location %} to run through that server and port. -Para definir isso em seu arquivo de configuração SSH, edite o arquivo em `~/.ssh/config` e adicione esta seção: +To set this in your SSH configuration file, edit the file at `~/.ssh/config`, and add this section: ``` Host {% data variables.command_line.codeblock %} @@ -47,10 +41,10 @@ Port 443 User git ``` -Para testar se funciona, conecte-se mais uma vez ao {% data variables.product.product_location %}: +You can test that this works by connecting once more to {% data variables.location.product_location %}: ```shell $ ssh -T git@{% data variables.command_line.codeblock %} -> Hi username! You've successfully authenticated, but GitHub does not +> Hi USERNAME! You've successfully authenticated, but GitHub does not > provide shell access. ``` diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md b/translations/pt-BR/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md index e75fd6ca2c..dcdfa5e6df 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md +++ b/translations/pt-BR/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md @@ -1,6 +1,6 @@ --- -title: Sobre a cobrança de pacotes do GitHub -intro: 'Se você quiser usar {% data variables.product.prodname_registry %} além do armazenamento ou transferência de dados incluídos em sua conta, você será cobrado pelo uso adicional.' +title: About billing for GitHub Packages +intro: 'If you want to use {% data variables.product.prodname_registry %} beyond the storage or data transfer included in your account, you will be billed for additional usage.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages @@ -13,72 +13,67 @@ topics: - Packages - Spending limits shortTitle: About billing -ms.openlocfilehash: e75b13f2422ac407264381a4637e763608bc9657 -ms.sourcegitcommit: 58db85219d094c2fb752117361e21eb49965d6ad -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 08/15/2022 -ms.locfileid: '147576986' --- -## Sobre a cobrança do {% data variables.product.prodname_registry %} +## About billing for {% data variables.product.prodname_registry %} {% data reusables.package_registry.packages-billing %} -{% data reusables.package_registry.packages-spending-limit-brief %} Para obter mais informações, confira "[Sobre os limites de gastos](#about-spending-limits)". +{% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)." {% note %} -**Atualização de cobrança para o armazenamento de imagens de contêiner:** o período de uso gratuito para o armazenamento de imagens de contêiner e a largura de banda para o {% data variables.product.prodname_container_registry %} foi estendido. Se estiver usando {% data variables.product.prodname_container_registry %}, você será informado com pelo menos um mês antes de começar a cobrar e receberá uma estimativa de quanto espera pagar. Para obter mais informações sobre o {% data variables.product.prodname_container_registry %}, confira "[Como trabalhar com o registro de contêiner](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)". +**Billing update for container image storage:** The period of free use for container image storage and bandwidth for the {% data variables.product.prodname_container_registry %} has been extended. If you are using {% data variables.product.prodname_container_registry %} you'll be informed at least one month in advance of billing commencing and you'll be given an estimate of how much you should expect to pay. For more information about the {% data variables.product.prodname_container_registry %}, see "[Working with the Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)." {% endnote %} -{% ifversion ghec %} Se você comprou o {% data variables.product.prodname_enterprise %} por meio de um Contrato Enterprise da Microsoft, conecte sua ID de Assinatura do Azure à sua conta corporativa para habilitar e pagar pelo uso do {% data variables.product.prodname_registry %} além dos valores, incluindo com a sua conta. Para obter mais informações, confira "[Como conectar uma assinatura do Azure à sua empresa](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)". +{% ifversion ghec %} +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](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)." {% endif %} -A transferência de dados é reiniciada todos os meses, mas o uso do armazenamento não. +Data transfer resets every month, while storage usage does not. -Produto | Armazenamento | Transferência de dados (por mês) +Product | Storage | Data transfer (per month) ------- | ------- | --------- -{% data variables.product.prodname_free_user %} | 500MB | 1 GB +{% data variables.product.prodname_free_user %} | 500MB | 1GB {% data variables.product.prodname_pro %} | 2GB | 10GB -{% data variables.product.prodname_free_team %} para organizações | 500MB | 1 GB | +{% data variables.product.prodname_free_team %} for organizations | 500MB | 1GB | {% data variables.product.prodname_team %} | 2GB | 10GB {% data variables.product.prodname_ghe_cloud %} | 50GB | 100GB -Todos os dados transferidos, quando acionados por {% data variables.product.prodname_actions %}, e os dados transferidos de qualquer fonte são gratuitos. Determinamos que você está baixando pacotes usando o {% data variables.product.prodname_actions %} ao fazer logon no {% data variables.product.prodname_registry %} usando um `GITHUB_TOKEN`. +All data transferred out, when triggered by {% data variables.product.prodname_actions %}, and data transferred in from any source is free. We determine you are downloading packages using {% data variables.product.prodname_actions %} when you log in to {% data variables.product.prodname_registry %} using a `GITHUB_TOKEN`. -||Hospedado|Auto-hospedado| +||Hosted|Self-Hosted| |-|-|-| -|Acesso por meio de um `GITHUB_TOKEN`|Gratuita|Gratuita| -|Acesso usando um token de acesso pessoal|Gratuita|$| +|Access using a `GITHUB_TOKEN`|Free|Free| +|Access using a {% data variables.product.pat_generic %}|Free|$| -O uso do armazenamento é compartilhado com artefatos de construção produzidos por {% data variables.product.prodname_actions %} para repositórios de sua conta. Para obter mais informações, confira "[Sobre a cobrança do {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)". +Storage usage is shared with build artifacts produced by {% data variables.product.prodname_actions %} for repositories owned by your account. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)." -O {% data variables.product.prodname_dotcom %} cobra o uso da conta que possui o repositório onde o pacote é publicado. Se o uso da sua conta ultrapassar esses limites e você definir um limite de gastos acima de US$ 0, você pagará US$ 0,25 por GB de armazenamento por dia e US$ 0,50 por GB de transferência de dados. +{% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where the package is published. If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and $0.50 USD per GB of data transfer. -Por exemplo, se sua organização usa {% data variables.product.prodname_team %}, permite gastos ilimitados, usa 150GB de armazenamento, e possui 50GB de transferência de dados durante um mês, a organização teria excessos de 148GB para armazenamento e 40GB para transferência de dados para esse mês. O excedente de armazenamento custaria US$ 0,25 por GB por dia ou US$ 37. O excesso para transferência de dados custaria US$ 0,50 ou US$ 20 por GB. +For example, if your organization uses {% data variables.product.prodname_team %}, allows unlimited spending, uses 150GB of storage, and has 50GB of data transfer out during a month, the organization would have overages of 148GB for storage and 40GB for data transfer for that month. The storage overage would cost $0.008 USD per GB per day or approximately $37 USD for a 31-day month. The overage for data transfer would cost $0.50 USD per GB or $20 USD. {% data reusables.dotcom_billing.pricing_calculator.pricing_cal_packages %} -No final do mês, {% data variables.product.prodname_dotcom %} arredonda sua transferência de dados para o GB mais próximo. +At the end of the month, {% data variables.product.prodname_dotcom %} rounds your data transfer to the nearest GB. -O {% data variables.product.prodname_dotcom %} calcula seu uso do armazenamento para cada mês com base no uso por hora durante aquele mês. Por exemplo, se durante o mês de março você utilizar 3 GB em 10 dias e 12 GB nos 21 dias subsequentes, o uso do armazenamento será de: +{% data variables.product.prodname_dotcom %} calculates your storage usage for each month based on hourly usage during that month. For example, if you use 3 GB of storage for 10 days of March and 12 GB for 21 days of March, your storage usage would be: -- 3 GB x 10 dias x (24 horas por dia) = 720 GB-Horas -- 12 GB x 21 dias x (24 horas por dia) = 6,048 GB-Horas -- 720 GB-Horas + 6.048 GB-Horas = 6.768 GB-Horas -- 6\.768 GB-Horas / (744 horas por mês) = 9,0967 GB-Meses +- 3 GB x 10 days x (24 hours per day) = 720 GB-Hours +- 12 GB x 21 days x (24 hours per day) = 6,048 GB-Hours +- 720 GB-Hours + 6,048 GB-Hours = 6,768 GB-Hours +- 6,768 GB-Hours / (744 hours per month) = 9.0967 GB-Months -No final do mês, {% data variables.product.prodname_dotcom %} arredonda seu armazenamento para o MB mais próximo. Portanto, seu uso de armazenamento em março seria de 9,097 GB. +At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB. Therefore, your storage usage for March would be 9.097 GB. -Se uso de {% data variables.product.prodname_registry %} compartilha a data de cobrança, o método de pagamento e o recibo que já existem para sua conta. {% data reusables.dotcom_billing.view-all-subscriptions %} +Your {% data variables.product.prodname_registry %} usage shares your account's existing billing date, payment method, and receipt. {% data reusables.dotcom_billing.view-all-subscriptions %} {% data reusables.user-settings.context_switcher %} -## Sobre limites de gastos +## About spending limits {% data reusables.package_registry.packages-spending-limit-detailed %} -Para obter informações sobre como gerenciar e alterar o limite de gastos da sua conta, confira "[Como gerenciar seu limite de gastos do {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages)". +For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages)." {% data reusables.dotcom_billing.actions-packages-unpaid-account %} diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md index 6d6199853c..8193a24ee4 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md +++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: Sobre a cobrança para a sua empresa -intro: 'Você pode visualizar as informações de cobrança da empresa{% ifversion ghec or ghes %} conta corporativa em {% data variables.product.prodname_dotcom_the_website %}{% endif %}.' +title: About billing for your enterprise +intro: 'You can view billing information for your enterprise{% ifversion ghec or ghes %} account on {% data variables.product.prodname_dotcom_the_website %}{% endif %}.' redirect_from: - /admin/overview/managing-billing-for-your-enterprise - /enterprise/admin/installation/managing-billing-for-github-enterprise @@ -14,69 +14,68 @@ type: overview topics: - Enterprise shortTitle: Billing for your enterprise -ms.openlocfilehash: 1b048c16293b7183636bc383ca926c4e5c7f0bd2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147573406' --- -## Sobre a cobrança para a sua empresa + +## About billing for your enterprise {% ifversion ghae %} -{% data reusables.github-ae.about-billing %} Uma vez por dia, {% data variables.product.prodname_dotcom %} contará o número de usuários com uma licença para sua empresa. {% data variables.product.company_short %} efetua a cobrança para cada usuário licenciado independentemente de o usuário estar conectado a {% data variables.product.prodname_ghe_managed %} nesse dia. +{% data reusables.github-ae.about-billing %} Once per day, {% data variables.product.prodname_dotcom %} will count the number of users with a license for your enterprise. {% data variables.product.company_short %} bills you for each licensed user regardless of whether the user logged into {% data variables.product.prodname_ghe_managed %} that day. -Para regiões comerciais, o preço por usuário por dia é de $ 1,2580645161. Por meses de 31 dias, o custo mensal para cada usuário é de $ 39. Nos meses com menos dias, o custo mensal é menor. Cada mês de cobrança começa em um horário fixo no primeiro dia do mês do calendário. +For commercial regions, the price per user per day is $1.2580645161. For 31-day months, the monthly cost for each user is $39. For months with fewer days, the monthly cost is lower. Each billing month begins at a fixed time on the first day of the calendar month. -Se você adicionar um usuário licenciado no meio do mês, esse usuário será incluído apenas na contagem dos dias em que tem uma licença. Ao remover um usuário licenciado, esse usuário permanecerá na contagem até o final desse mês. Portanto, se você adicionar um usuário durante o mês ou depois remover o usuário no mesmo mês, o usuário será incluído na contagem a partir do dia em que o usuário foi adicionado até o final do mês. Não há custos adicionais se você adicionar novamente um usuário no mesmo mês em que o usuário foi removido. +If you add a licensed user mid-month, that user will only be included in the count for the days they have a license. When you remove a licensed user, that user will remain in the count until the end of that month. Therefore, if you add a user mid-month and later remove the user in the same month, the user will be included in the count from the day the user was added through the end of the month. There is no additional cost if you re-add a user during the same month the user was removed. -Por exemplo, aqui estão os custos para os usuários com licenças em datas diferentes. +For example, here are the costs for users with licenses on different dates. -Usuário | Datas de licença | Dias contados | Custo +User | License dates | Counted days | Cost ---- | ------------ | ------- | ----- -@octocat | 1 de Janeiro - 31 de Janeiro | 31 | US$ 39 -@robocat | 1 de fevereiro - 28 de fevereiro | 28 | $ 35,23 -@devtocat | 15 de Janeiro - 31 de Janeiro | 17 | $ 21,39 -@doctocat | 1 de Janeiro - 15 de Janeiro | 31 | US$ 39 -@prodocat | 7 de Janeiro - 15 de Janeiro | 25 | $ 31,45 -@monalisa | 1º de janeiro – 7 de janeiro
15 de Janeiro - 31 de Janeiro | 31 | US$ 39 +@octocat | January 1 - January 31 | 31 | $39 +@robocat | February 1 - February 28 | 28 | $35.23 +@devtocat | January 15 - January 31 | 17 | $21.39 +@doctocat | January 1 - January 15 | 31 | $39 +@prodocat | January 7 - January 15 | 25 | $31.45 +@monalisa | January 1 - January 7,
January 15 - January 31 | 31 | $39 -{% data variables.product.prodname_ghe_managed %} tem uma instância mínima de 500 usuários. {% data variables.product.company_short %} cobra de você um mínimo de 500 usuários por instância, mesmo que haja menos de 500 usuários com uma licença nesse dia. +{% data variables.product.prodname_ghe_managed %} has a 500-user minimum per instance. {% data variables.product.company_short %} bills you for a minimum of 500 users per instance, even if there are fewer than 500 users with a license that day. -Veja seu uso atual no [portal da conta do Azure](https://portal.azure.com). +You can see your current usage in your [Azure account portal](https://portal.azure.com). {% elsif ghec or ghes %} {% ifversion ghec %} -Quando você usa uma conta corporativa em {% data variables.product.product_location %}, a conta corporativa é o ponto central para toda a cobrança em sua empresa, incluindo as organizações que sua empresa possui. +When you use an enterprise account on {% data variables.location.product_location %}, the enterprise account is the central point for all billing within your enterprise, including the organizations that your enterprise owns. -Se você usar {% data variables.product.product_name %} com uma organização individual e ainda não tiver uma conta corporativa, crie uma conta corporativa e adicione a sua organização. Para obter mais informações, confira "[Com criar uma conta empresarial](/admin/overview/creating-an-enterprise-account)". +If you use {% data variables.product.product_name %} with an individual organization and do not yet have an enterprise account, you create an enterprise account and add your organization. For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)." -{% data variables.product.company_short %} cobra mensalmente o número total de licenças de estação para sua conta corporativa, bem como quaisquer serviços adicionais que você usa com {% data variables.product.prodname_ghe_cloud %}, como minutos de {% data variables.product.prodname_actions %}. Se você usar uma organização autônoma em {% data variables.product.product_name %}, será cobrado no nível da organização por todo o uso. Para obter mais informações sobre as estações de licença da sua conta, confira "[Sobre preços por usuário](/billing/managing-billing-for-your-github-account/about-per-user-pricing)". +{% data variables.product.company_short %} bills monthly for the total number of licensed seats for your enterprise account, as well as any additional services you use with {% data variables.product.prodname_ghe_cloud %}, such as {% data variables.product.prodname_actions %} minutes. If you use a standalone organization on {% data variables.product.product_name %}, you'll be billed at the organization level for all usage. For more information your bill's license seats, see "[About per-user pricing](/billing/managing-billing-for-your-github-account/about-per-user-pricing)." {% elsif ghes %} -Cada usuário em {% data variables.product.product_location %} consome uma estação na sua licença. {% data variables.product.company_short %} faz a cobrança mensal no número total de estações consumidas na sua licença. +Each user on {% data variables.location.product_location %} consumes a seat on your license. {% data variables.product.company_short %} bills monthly for the total number of seats consumed on your license. {% endif %} -{% ifversion ghec %}Para clientes do {% data variables.product.prodname_ghe_cloud %} com uma conta corporativa, {% data variables.product.company_short %} a cobrança ocorre na conta corporativa em {% data variables.product.prodname_dotcom_the_website %}. Para clientes com fatura, cada{% elsif ghes %}Para clientes com fatura {% data variables.product.prodname_enterprise %}, {% data variables.product.company_short %} a cobrança ocorre na conta corporativa em {% data variables.product.prodname_dotcom_the_website %}. Cada{% endif %} fatura inclui uma única cobrança de fatura para todos os seus serviços de {% data variables.product.prodname_dotcom_the_website %} pagos e as instâncias de qualquer {% data variables.product.prodname_ghe_server %}. Para mais informações sobre {% ifversion ghes %} licenciamento, uso e faturas{% elsif ghec %}uso e faturas{% endif %}, confira o seguinte{% ifversion ghes %} na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}.{% endif %} +{% ifversion ghec %}For {% data variables.product.prodname_ghe_cloud %} customers with an enterprise account, {% data variables.product.company_short %} bills through your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. For invoiced customers, each{% elsif ghes %}For invoiced {% data variables.product.prodname_enterprise %} customers, {% data variables.product.company_short %} bills through an enterprise account on {% data variables.product.prodname_dotcom_the_website %}. Each{% endif %} invoice includes a single bill charge for all of your paid {% data variables.product.prodname_dotcom_the_website %} services and any {% data variables.product.prodname_ghe_server %} instances. For more information about {% ifversion ghes %}licensing, usage, and invoices{% elsif ghec %}usage and invoices{% endif %}, see the following{% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} {%- ifversion ghes %} -- "[Sobre os preços por usuário](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/about-per-user-pricing)" {%- endif %} -- "[Como ver a assinatura e o uso da sua conta corporativa]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" -- "[Como gerenciar faturas da sua empresa]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise)" +- "[About per-user pricing](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/about-per-user-pricing)" +{%- endif %} +- "[Viewing the subscription and usage for your enterprise account]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" +- "[Managing invoices for your enterprise]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise)" -Os administradores da conta corporativa em {% data variables.product.prodname_dotcom_the_website %} podem acessar e gerenciar a cobrança da empresa. Para obter mais informações, confira "[Funções em uma empresa]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise){% ifversion ghec %}".{% elsif ghes %}" na documentação do {% data variables.product.prodname_ghe_cloud %}.{% endif %} +Administrators for your enterprise account on {% data variables.product.prodname_dotcom_the_website %} can access and manage billing for the enterprise. For more information, see "[Roles in an enterprise]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise){% ifversion ghec %}."{% elsif ghes %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %} -{% ifversion ghec %} {% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} Para obter mais informações, confira "[Como conectar uma assinatura do Azure à sua empresa](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)". +{% ifversion ghec %} +{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)." {% endif %} -{% ifversion ghes %} {% data reusables.billing.ghes-with-no-enterprise-account %} {% endif %} +{% ifversion ghes %} +{% data reusables.billing.ghes-with-no-enterprise-account %} +{% endif %} {% endif %} -## Leitura adicional +## Further reading -- "[Sobre as contas corporativas](/admin/overview/about-enterprise-accounts)" +- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)" diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md index 0253200ccb..5f06513eaa 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md +++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md @@ -86,7 +86,7 @@ In addition to licensed seats, your bill may include other charges, such as {% d {% data variables.product.company_short %} does not bill for any of the following accounts: -- {% data variables.product.prodname_managed_users_caps %} that are suspended +- {% data variables.enterprise.prodname_managed_users_caps %} that are suspended - Enterprise owners who are not a member or owner of at least one organization in the enterprise - Enterprise billing managers - Billing managers for individual organizations diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md index 3148d33eb7..a78c974347 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md +++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md @@ -1,6 +1,6 @@ --- -title: Fazer downgrade da sua assinatura do GitHub -intro: 'Você pode fazer o downgrade da assinatura para qualquer tipo de conta em {% data variables.product.product_location %} a qualquer momento.' +title: Downgrading your GitHub subscription +intro: 'You can downgrade the subscription for any type of account on {% data variables.location.product_location %} at any time.' redirect_from: - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription - /articles/downgrading-your-personal-account-s-billing-plan @@ -27,80 +27,76 @@ topics: - Repositories - User account shortTitle: Downgrade subscription -ms.openlocfilehash: b709c94090c1f79bfd8e16cc7df2c943d64b5aa7 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145083467' --- -## Rebaixando sua assinatura {% data variables.product.product_name %} +## Downgrading your {% data variables.product.product_name %} subscription -Quando você faz o downgrade (rebaixa) a assinatura da sua conta pessoal ou organização, as alterações de preços e recursos da conta fazem efeito a partir da próxima data de faturamento. Alterações em sua conta pessoal paga ou assinatura de organização não afetam assinaturas ou pagamentos para outros recursos pagos {% data variables.product.prodname_dotcom %}. Para obter mais informações, confira "[Como a atualização ou o downgrade afetam o processo de cobrança?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)". +When you downgrade your personal account or organization's subscription, pricing and account feature changes take effect on your next billing date. Changes to your paid personal account or organization subscription does not affect subscriptions or payments for other paid {% data variables.product.prodname_dotcom %} features. For more information, see "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)." -## Fazer o downgrade da assinatura da sua conta pessoal +## Downgrading your personal account's subscription -Se você fizer o downgrade da sua conta pessoal de {% data variables.product.prodname_pro %} para {% data variables.product.prodname_free_user %}, a conta perderá o acesso a ferramentas avançadas de revisão de código em repositórios privados. {% data reusables.gated-features.more-info %} +If you downgrade your personal account from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, the account will lose access to advanced code review tools on private repositories. {% data reusables.gated-features.more-info %} -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.billing_plans %} -1. Em "Plano atual", use o menu suspenso **Editar** e clique em **Fazer Downgrade para Gratuito**. - ![Botão Fazer Downgrade para Gratuito](/assets/images/help/billing/downgrade-to-free.png) -5. Leia as informações sobre os recursos aos quais sua conta pessoal não terá mais acesso na próxima data de cobrança e clique em **Entendi. Continuar com o downgrade**. - ![Botão Continuar com o downgrade](/assets/images/help/billing/continue-with-downgrade.png) +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.billing_plans %} +1. Under "Current plan", use the **Edit** drop-down and click **Downgrade to Free**. + ![Downgrade to free button](/assets/images/help/billing/downgrade-to-free.png) +5. Read the information about the features your personal account will no longer have access to on your next billing date, then click **I understand. Continue with downgrade**. + ![Continue with downgrade button](/assets/images/help/billing/continue-with-downgrade.png) -Se você tiver publicado um site do {% data variables.product.prodname_pages %} em um repositório privado e adicionado um domínio personalizado, remova ou atualize seus registros DNS antes de fazer downgrade do {% data variables.product.prodname_pro %} para {% data variables.product.prodname_free_user %}, a fim de evitar o risco de uma aquisição de domínio. Para obter mais informações, confira "[Como gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". +If you published a {% data variables.product.prodname_pages %} site in a private repository and added a custom domain, remove or update your DNS records before downgrading from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, 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)." -## Rebaixando a assinatura da sua organização +## Downgrading your organization's subscription {% data reusables.dotcom_billing.org-billing-perms %} -Se você fizer o downgrade da sua organização de {% data variables.product.prodname_team %} para {% data variables.product.prodname_free_team %}, para uma organização, a conta perderá o acesso a ferramentas avançadas de colaboração e gerenciamento para equipes. +If you downgrade your organization from {% data variables.product.prodname_team %} to {% data variables.product.prodname_free_team %} for an organization, the account will lose access to advanced collaboration and management tools for teams. -Se você fizer o downgrade da sua organização de {% data variables.product.prodname_ghe_cloud %} para {% data variables.product.prodname_team %} ou {% data variables.product.prodname_free_team %}, a conta perderá o acesso a controles avançados de segurança, conformidade e implantação. {% data reusables.gated-features.more-info %} +If you downgrade your organization from {% data variables.product.prodname_ghe_cloud %} to {% data variables.product.prodname_team %} or {% data variables.product.prodname_free_team %}, the account will lose access to advanced security, compliance, and deployment controls. {% data reusables.gated-features.more-info %} {% note %} -**Observação:** se você estiver avaliando o {% data variables.product.prodname_ghe_cloud %} e não comprar o {% data variables.product.prodname_enterprise %} antes do término da avaliação, será feito o downgrade automático da sua organização para o {% data variables.product.prodname_free_team %} ou para o {% data variables.product.prodname_team %}. Para obter mais informações, confira "[Como configurar uma avaliação do {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)". +**Note:** If you're currently trialing {% data variables.product.prodname_ghe_cloud %}, and you don't purchase {% data variables.product.prodname_enterprise %} before the trial ends, your organization will be automatically downgraded to {% data variables.product.prodname_free_team %} or {% data variables.product.prodname_team %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)." {% endnote %} {% data reusables.organizations.billing-settings %} -1. Em "Plano atual", use o menu suspenso **Editar** e clique na opção de downgrade desejada. - ![Botão Fazer downgrade](/assets/images/help/billing/downgrade-option-button.png) {% data reusables.dotcom_billing.confirm_cancel_org_plan %} +1. Under "Current plan", use the **Edit** drop-down and click the downgrade option you want. + ![Downgrade button](/assets/images/help/billing/downgrade-option-button.png) +{% data reusables.dotcom_billing.confirm_cancel_org_plan %} -## Fazer downgrade da assinatura de uma organização com o preço antigo por repositório +## Downgrading an organization's subscription with legacy per-repository pricing {% data reusables.dotcom_billing.org-billing-perms %} -{% data reusables.dotcom_billing.switch-legacy-billing %} Para obter mais informações, confira "[Como alternar sua organização do preço por repositório para o preço por usuário](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)". +{% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[Switching your organization from per-repository to per-user pricing](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)." {% data reusables.organizations.billing-settings %} -5. Em "Assinaturas", selecione o menu suspenso "Editar" e clique em **Editar plano**. - ![Menu suspenso Editar plano](/assets/images/help/billing/edit-plan-dropdown.png) -1. Em "Cobrança/Planos", ao lado do plano que deseja alterar, clique em **Fazer downgrade**. - ![Botão Fazer downgrade](/assets/images/help/billing/downgrade-plan-option-button.png) -1. Insira o motivo pelo qual você está fazendo downgrade da sua conta e clique em **Fazer downgrade do plano**. - ![Caixa de texto usada para o motivo do downgrade e botão Fazer downgrade](/assets/images/help/billing/downgrade-plan-button.png) +5. Under "Subscriptions", select the "Edit" drop-down, and click **Edit plan**. + ![Edit Plan dropdown](/assets/images/help/billing/edit-plan-dropdown.png) +1. Under "Billing/Plans", next to the plan you want to change, click **Downgrade**. + ![Downgrade button](/assets/images/help/billing/downgrade-plan-option-button.png) +1. Enter the reason you're downgrading your account, then click **Downgrade plan**. + ![Text box for downgrade reason and downgrade button](/assets/images/help/billing/downgrade-plan-button.png) -## Remover estações pagas da sua organização +## Removing paid seats from your organization -Para reduzir o número de estações pagas usadas pela sua organização, remova integrantes dela ou converta integrantes em colaboradores externos e conceda a eles acesso somente a repositórios públicos. Para obter mais informações, consulte: -- "[Como remover um membro da organização](/articles/removing-a-member-from-your-organization)" -- "[Como converter um membro da organização em um colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" -- "[Como gerenciar o acesso de uma pessoa a um repositório da organização](/articles/managing-an-individual-s-access-to-an-organization-repository)" +To reduce the number of paid seats your organization uses, you can remove members from your organization or convert members to outside collaborators and give them access to only public repositories. For more information, see: +- "[Removing a member from your organization](/articles/removing-a-member-from-your-organization)" +- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)" +- "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)" {% data reusables.organizations.billing-settings %} -1. Em "Plano atual", use o menu suspenso **Editar** e clique em **Remover estações**. - ![Menu suspenso usado para remover estações](/assets/images/help/billing/remove-seats-dropdown.png) -1. Em "Remove seats" (Remover estações), selecione o número de estações em que você deseja fazer downgrade. - ![opção para remover estações](/assets/images/help/billing/remove-seats-amount.png) -1. Revise as informações sobre o novo pagamento na próxima data de cobrança e clique em **Remover estações**. - ![botão Remover estações](/assets/images/help/billing/remove-seats-button.png) +1. Under "Current plan", use the **Edit** drop-down and click **Remove seats**. + ![remove seats dropdown](/assets/images/help/billing/remove-seats-dropdown.png) +1. Under "Remove seats", select the number of seats you'd like to downgrade to. + ![remove seats option](/assets/images/help/billing/remove-seats-amount.png) +1. Review the information about your new payment on your next billing date, then click **Remove seats**. + ![remove seats button](/assets/images/help/billing/remove-seats-button.png) -## Leitura adicional +## Further reading -- "[Produtos do {% data variables.product.prodname_dotcom %}](/articles/github-s-products)" -- "[Como o upgrade ou o downgrade afetam o processo de cobrança?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)" -- "[Sobre a cobrança do {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)". -- "[Sobre os preços por usuário](/articles/about-per-user-pricing)" +- "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)" +- "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)" +- "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)." +- "[About per-user pricing](/articles/about-per-user-pricing)" diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md index e50155b004..9d40ff9312 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md +++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md @@ -1,6 +1,6 @@ --- -title: Atualizar sua assinatura do GitHub -intro: 'Você pode atualizar a assinatura para qualquer tipo de conta em {% data variables.product.product_location %} a qualquer momento.' +title: Upgrading your GitHub subscription +intro: 'You can upgrade the subscription for any type of account on {% data variables.location.product_location %} at any time.' miniTocMaxHeadingLevel: 3 redirect_from: - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription @@ -30,69 +30,83 @@ topics: - Upgrades - User account shortTitle: Upgrade your subscription -ms.openlocfilehash: 47426fa211521a166738c5a9bb00edddfc2556f2 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145083453' --- -## Sobre atualizações da assinatura + +## About subscription upgrades {% data reusables.accounts.accounts-billed-separately %} -Ao atualizar a assinatura de uma conta, a atualização altera as funcionalidades pagas disponíveis apenas para essa conta, e não as outras contas que você usa. +When you upgrade the subscription for an account, the upgrade changes the paid features available for that account only, and not any other accounts you use. -## Atualizar a assinatura da sua conta pessoal +## Upgrading your personal account's subscription -Você pode atualizar sua conta pessoal de {% data variables.product.prodname_free_user %} para {% data variables.product.prodname_pro %} para ter ferramentas avançadas de revisão de código em repositórios privados pertencentes à sua conta pessoal. A atualização de sua conta pessoal não afeta nenhuma organização que você possa gerenciar ou repositórios pertencentes a essas organizações. {% data reusables.gated-features.more-info %} +You can upgrade your personal account from {% data variables.product.prodname_free_user %} to {% data variables.product.prodname_pro %} to get advanced code review tools on private repositories owned by your personal account. Upgrading your personal account does not affect any organizations you may manage or repositories owned by those organizations. {% data reusables.gated-features.more-info %} -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.billing_plans %} -1. Ao lado de "Plano atual", clique em **Fazer upgrade**. - ![Botão Fazer upgrade](/assets/images/help/billing/settings_billing_user_upgrade.png) -2. Em "Pro" na página "Comparar planos", clique em **Fazer upgrade para o Pro**. -{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} {% data reusables.dotcom_billing.show-plan-details %} {% data reusables.dotcom_billing.enter-billing-info %} {% data reusables.dotcom_billing.enter-payment-info %} {% data reusables.dotcom_billing.finish_upgrade %} +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.billing_plans %} +1. Next to "Current plan", click **Upgrade**. + ![Upgrade button](/assets/images/help/billing/settings_billing_user_upgrade.png) +2. Under "Pro" on the "Compare plans" page, click **Upgrade to Pro**. +{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} +{% data reusables.dotcom_billing.show-plan-details %} +{% data reusables.dotcom_billing.enter-billing-info %} +{% data reusables.dotcom_billing.enter-payment-info %} +{% data reusables.dotcom_billing.finish_upgrade %} -## Gerenciando a assinatura da organização +## Managing your organization's subscription -Você pode atualizar a assinatura da sua organização para um produto diferente, adicionar estações ao produto existente ou mudar de preços por repositório para preços por usuário. +You can upgrade your organization's subscription to a different product, add seats to your existing product, or switch from per-repository to per-user pricing. -### Atualizar a assinatura da organização +### Upgrading your organization's subscription -Você pode atualizar sua organização de {% data variables.product.prodname_free_team %} para uma organização para {% data variables.product.prodname_team %} para acessar ferramentas avançadas de gerenciamento e colaboração para equipes ou atualizar sua organização para o {% data variables.product.prodname_ghe_cloud %} para obter controles adicionais de segurança, conformidade e implantação. A atualização de uma organização não afeta sua conta pessoal ou repositórios pertencentes à sua conta pessoal. {% data reusables.gated-features.more-info-org-products %} +You can upgrade your organization from {% data variables.product.prodname_free_team %} for an organization to {% data variables.product.prodname_team %} to access advanced collaboration and management tools for teams, or upgrade your organization to {% data variables.product.prodname_ghe_cloud %} for additional security, compliance, and deployment controls. Upgrading an organization does not affect your personal account or repositories owned by your personal account. {% data reusables.gated-features.more-info-org-products %} {% data reusables.dotcom_billing.org-billing-perms %} -{% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.upgrade_org %} {% data reusables.dotcom_billing.choose_org_plan %} {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} {% data reusables.dotcom_billing.show-plan-details %} {% data reusables.dotcom_billing.enter-payment-info %} {% data reusables.dotcom_billing.owned_by_business %} {% data reusables.dotcom_billing.finish_upgrade %} +{% data reusables.organizations.billing-settings %} +{% data reusables.dotcom_billing.upgrade_org %} +{% data reusables.dotcom_billing.choose_org_plan %} +{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} +{% data reusables.dotcom_billing.show-plan-details %} +{% data reusables.dotcom_billing.enter-payment-info %} +{% data reusables.dotcom_billing.owned_by_business %} +{% data reusables.dotcom_billing.finish_upgrade %} -### Próximas etapas para organizações que usam o {% data variables.product.prodname_ghe_cloud %} +### Next steps for organizations using {% data variables.product.prodname_ghe_cloud %} -Se você tiver atualizado sua organização para o {% data variables.product.prodname_ghe_cloud %}, você poderá configurar a identidade e a gestão de acesso para a sua organização. Para obter mais informações, confira "[Como gerenciar o logon único do SAML para sua organização](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization){% ifversion fpt %}" na documentação do {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %} +If you upgraded your organization to {% data variables.product.prodname_ghe_cloud %}, you can set up identity and access management for your organization. For more information, see "[Managing SAML single sign-on for your organization](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} -Caso queira usar uma conta corporativa com o {% data variables.product.prodname_ghe_cloud %}, entre em contato com {% data variables.contact.contact_enterprise_sales %}. Para obter mais informações, confira "[Sobre as contas corporativas](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}" na documentação do {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %} +If you'd like to use an enterprise account with {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} -### Adicionar estações à organização +### Adding seats to your organization -Se você quiser que outros usuários tenham acesso aos repositórios privados da organização {% data variables.product.prodname_team %}, você poderá comprar mais estações a qualquer momento. - -{% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.add-seats %} {% data reusables.dotcom_billing.number-of-seats %} {% data reusables.dotcom_billing.confirm-add-seats %} - -### Trocar o plano de cobrança da organização de preços por repositório para por usuário - -{% data reusables.dotcom_billing.switch-legacy-billing %} Para obter mais informações, confira "[Sobre os preços por usuário](/articles/about-per-user-pricing)". +If you'd like additional users to have access to your {% data variables.product.prodname_team %} organization's private repositories, you can purchase more seats anytime. {% data reusables.organizations.billing-settings %} -5. À direita do nome do plano, use o menu suspenso **Editar** e selecione **Editar plano**. - ![Menu suspenso Editar](/assets/images/help/billing/per-user-upgrade-button.png) -6. À direita de "Ferramentas avançadas para equipes", clique em **Fazer upgrade agora**. - ![Botão Fazer upgrade agora](/assets/images/help/billing/per-user-upgrade-now-button.png) {% data reusables.dotcom_billing.choose_org_plan %} {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} {% data reusables.dotcom_billing.owned_by_business %} {% data reusables.dotcom_billing.finish_upgrade %} +{% data reusables.dotcom_billing.add-seats %} +{% data reusables.dotcom_billing.number-of-seats %} +{% data reusables.dotcom_billing.confirm-add-seats %} -## Solucionar problemas de erro 500 ao atualizar +### Switching your organization from per-repository to per-user pricing + +{% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." + +{% data reusables.organizations.billing-settings %} +5. To the right of your plan name, use the **Edit** drop-down menu, and select **Edit plan**. + ![Edit drop-down menu](/assets/images/help/billing/per-user-upgrade-button.png) +6. To the right of "Advanced tools for teams", click **Upgrade now**. + ![Upgrade now button](/assets/images/help/billing/per-user-upgrade-now-button.png) +{% data reusables.dotcom_billing.choose_org_plan %} +{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} +{% data reusables.dotcom_billing.owned_by_business %} +{% data reusables.dotcom_billing.finish_upgrade %} + +## Troubleshooting a 500 error when upgrading {% data reusables.dotcom_billing.500-error %} -## Leitura adicional +## Further reading -- "[Produtos do {% data variables.product.prodname_dotcom %}](/articles/github-s-products)" -- "[Como o upgrade ou o downgrade afetam o processo de cobrança?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)" -- "[Sobre a cobrança do {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)". +- "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)" +- "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)" +- "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)." diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md index 5c000533a5..aba1e9288f 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -1,6 +1,6 @@ --- -title: Exibir assinatura e uso da conta corporativa -intro: 'Você pode ver a assinatura atual {% ifversion ghec %}, {% endif %}o uso da licença{% ifversion ghec %}as faturas, o histórico de pagamentos e outras informações de cobrança{% endif %} da {% ifversion ghec %}conta empresarial{% elsif ghes %}{% data variables.product.product_location_enterprise %}{% endif %}.' +title: Viewing the subscription and usage for your enterprise account +intro: 'You can view the current {% ifversion ghec %}subscription, {% endif %}license usage{% ifversion ghec %}, invoices, payment history, and other billing information{% endif %} for {% ifversion ghec %}your enterprise account{% elsif ghes %}{% data variables.location.product_location_enterprise %}{% endif %}.' permissions: 'Enterprise owners {% ifversion ghec %}and billing managers {% endif %}can access and manage all billing settings for enterprise accounts.' redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account @@ -13,42 +13,42 @@ versions: topics: - Enterprise shortTitle: View subscription & usage -ms.openlocfilehash: 503f870542180cfe9ae088a161370b9370d36f1c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145189635' --- -## Sobre a cobrança de contas corporativas -Você pode ter uma visão geral da {% ifversion ghec %}assinatura e do uso pago{% elsif ghes %}da licença{% endif %} da {% ifversion ghec %}sua{% elsif ghes %}da{% endif %} conta empresarial no {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.{% ifversion ghec %} {% data reusables.enterprise.create-an-enterprise-account %} Para obter mais informações, confira "[Como criar uma conta empresarial](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)".{% endif %} +## About billing for enterprise accounts -Para {% data variables.product.prodname_enterprise %} clientes faturados{% ifversion ghes %} que usam {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_server %}{% endif %}, cada fatura inclui as informações sobre os serviços cobrados para todos os produtos. Por exemplo, além do uso do {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, você pode ter um uso do {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghec %}, {% elsif ghes %}. Você também pode ter uso em {% data variables.product.prodname_dotcom_the_website %}, como {% endif %}licenças pagas em organizações fora da conta corporativa, pacotes de dados para {% data variables.large_files.product_name_long %}ou assinaturas de aplicativos em {% data variables.product.prodname_marketplace %}. Para obter mais informações sobre faturas, confira "[Como gerenciar faturas para sua empresa]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise){% ifversion ghec %}".{% elsif ghes %}" na documentação do {% data variables.product.prodname_dotcom_the_website %}.{% endif %} +You can view an overview of {% ifversion ghec %}your subscription and paid{% elsif ghes %}the license{% endif %} usage for {% ifversion ghec %}your{% elsif ghes %}the{% endif %} enterprise account on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.location.product_location %}{% endif %}.{% ifversion ghec %} {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)."{% endif %} + +For invoiced {% data variables.product.prodname_enterprise %} customers{% ifversion ghes %} who use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}{% endif %}, each invoice includes details about billed services for all products. For example, in addition to your usage for {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, you may have usage for {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghec %}, {% elsif ghes %}. You may also have usage on {% data variables.product.prodname_dotcom_the_website %}, like {% endif %}paid licenses in organizations outside of your enterprise account, data packs for {% data variables.large_files.product_name_long %}, or subscriptions to apps in {% data variables.product.prodname_marketplace %}. For more information about invoices, see "[Managing invoices for your enterprise]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise){% ifversion ghec %}."{% elsif ghes %}" in the {% data variables.product.prodname_dotcom_the_website %} documentation.{% endif %} {% ifversion ghec %} -Além dos proprietários da empresa, os gerentes de cobrança podem visualizar a assinatura e o uso da sua conta corporativa. Para obter mais informações, confira "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise#billing-manager)" e "[Como convidar pessoas para gerenciar sua empresa](/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)". +In addition to enterprise owners, billing managers can view the subscription and usage for your enterprise account. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise#billing-manager)" and "[Inviting people to manage your enterprise](/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)." -{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} Para obter mais informações, confira "[Como conectar uma assinatura do Azure à sua empresa](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)". +{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)." {% endif %} {% ifversion ghes %} -Caso deseje ter uma visão geral da sua assinatura e uso do {% data variables.product.prodname_enterprise %} e de todos os serviços relacionados no {% data variables.product.prodname_dotcom_the_website %}, confira "[Como ver a assinatura e o uso da sua conta corporativa](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" na documentação do {% data variables.product.prodname_ghe_cloud %}. +If you want to view an overview of your subscription and usage for {% data variables.product.prodname_enterprise %} and any related services on {% data variables.product.prodname_dotcom_the_website %}, see "[Viewing the subscription and usage for your enterprise account](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" in the {% data variables.product.prodname_ghe_cloud %} documentation. {% endif %} -## Exibir assinatura e uso da conta corporativa +## Viewing the subscription and usage for your enterprise account -Você pode visualizar a assinatura e o uso para a sua empresa e fazer o download de um arquivo com detalhes da licença. +You can view the subscription and usage for your enterprise and download a file with license details. {% data reusables.billing.license-statuses %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -1. Em "Licenças de usuário", exiba o total de licenças, o número de licenças consumidas e a data de vencimento da sua assinatura. - {% ifversion ghec %}![Informações de licença e assinatura nas configurações de cobrança da empresa](/assets/images/help/business-accounts/billing-license-info.png){% else %} ![Informações de licença e assinatura nas configurações de cobrança da empresa](/assets/images/enterprise/enterprise-server/enterprise-server-billing-license-info.png){% endif %} -1. Opcionalmente, para ver os detalhes sobre o uso da licença ou baixar um arquivo {% ifversion ghec %}CSV{% elsif ghes %}JSON{% endif %} com os detalhes da licença{% ifversion ghec %}, à direita de "Licenças de Usuário"{% endif %}, clique em **Exibir {% ifversion ghec %}detalhes{% elsif ghes %}usuários{% endif %}** ou {% ifversion ghec %}{% octicon "download" aria-label="The download icon" %}{% elsif ghes %}**Exportar uso da licença**{% endif %}.{% ifversion ghec %} ![Botão "Exibir detalhes" e botão com o ícone de download à direita de "Licenças de Usuário"](/assets/images/help/business-accounts/billing-license-info-click-view-details-or-download.png){% endif %}{% ifversion ghec %} -1. Opcionalmente, para ver os detalhes de uso de outros recursos, na barra lateral esquerda, clique em **Cobrança**. - ![Guia Cobrança na barra lateral das configurações da conta corporativa](/assets/images/help/business-accounts/settings-billing-tab.png) {% endif %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.license-tab %} +1. Under "User licenses", view your total licenses, number of consumed licenses, and your subscription expiration date. + {% ifversion ghec %}![License and subscription information in enterprise billing settings](/assets/images/help/business-accounts/billing-license-info.png){% else %} + ![License and subscription information in enterprise billing settings](/assets/images/enterprise/enterprise-server/enterprise-server-billing-license-info.png){% endif %} +1. Optionally, to view details for license usage or download a {% ifversion ghec %}CSV{% elsif ghes %}JSON{% endif %} file with license details{% ifversion ghec %}, to the right of "User Licenses"{% endif %}, click **View {% ifversion ghec %}details{% elsif ghes %}users{% endif %}** or {% ifversion ghec %}{% octicon "download" aria-label="The download icon" %}{% elsif ghes %}**Export license usage**{% endif %}.{% ifversion ghec %} + !["View details" button and button with download icon to the right of "User Licenses"](/assets/images/help/business-accounts/billing-license-info-click-view-details-or-download.png){% endif %}{% ifversion ghec %} +1. Optionally, to view usage details for other features, in the left sidebar, click **Billing**. + ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) +{% endif %} diff --git a/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md b/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md index 5068b38b31..af80bbb3a1 100644 --- a/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md +++ b/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md @@ -1,6 +1,6 @@ --- -title: Sobre as assinaturas do Visual Studio com GitHub Enterprise -intro: 'Você pode fornecer assinantes de {% data variables.product.prodname_vs %} na sua equipe acesso a {% data variables.product.prodname_enterprise %} com uma oferta combinada da Microsoft.' +title: About Visual Studio subscriptions with GitHub Enterprise +intro: 'You can give {% data variables.product.prodname_vs %} subscribers on your team access to {% data variables.product.prodname_enterprise %} with a combined offering from Microsoft.' redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/managing-licenses-for-visual-studio-subscription-with-github-enterprise - /github/setting-up-and-managing-your-enterprise/managing-licenses-for-the-github-enterprise-and-visual-studio-bundle @@ -17,40 +17,35 @@ topics: - Enterprise - Licensing shortTitle: About -ms.openlocfilehash: d3adb998cb3413387766753a4dcdbee033df6506 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147052253' --- -## Sobre o {% data variables.product.prodname_vss_ghe %} -{% data reusables.enterprise-accounts.vss-ghe-description %} {% data variables.product.prodname_vss_ghe %} está disponível na Microsoft nos termos do Contrato corporativo da Microsoft. Para obter mais informações, confira [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/) no site do {% data variables.product.prodname_vs %}. +## About {% data variables.product.prodname_vss_ghe %} -Para usar a parte da licença de {% data variables.product.prodname_enterprise %}, a conta pessoal de cada assinante no {% data variables.product.prodname_dotcom_the_website %} deve ser ou tornar-se integrante de uma organização de propriedade da sua empresa em {% data variables.product.prodname_dotcom_the_website %}. Para isso, os proprietários da organização podem convidar novos integrantes para uma organização por e-mail. O assinante pode aceitar o convite com uma conta pessoal existente em {% data variables.product.prodname_dotcom_the_website %} ou criar uma nova conta. +{% data reusables.enterprise-accounts.vss-ghe-description %} {% data variables.product.prodname_vss_ghe %} is available from Microsoft under the terms of the Microsoft Enterprise Agreement. For more information, see [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/) on the {% data variables.product.prodname_vs %} website. -Para obter mais informações sobre a instalação do {% data variables.product.prodname_vss_ghe %}, confira "[Como configurar o {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise)". +To use the {% data variables.product.prodname_enterprise %} portion of the license, each subscriber's personal account on {% data variables.product.prodname_dotcom_the_website %} must be or become a member of an organization owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}. To accomplish this, organization owners can invite new members to an organization by email address. The subscriber can accept the invitation with an existing personal account on {% data variables.product.prodname_dotcom_the_website %} or create a new account. -## Sobre as licenças do {% data variables.product.prodname_vss_ghe %} +For more information about the setup of {% data variables.product.prodname_vss_ghe %}, see "[Setting up {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise)." -Depois de atribuir uma licença de {% data variables.product.prodname_vss_ghe %} a um assinante, o integrante usará a parte {% data variables.product.prodname_enterprise %} da licença, juntando-se a uma organização na sua empresa com uma conta pessoal no {% data variables.product.prodname_dotcom_the_website %}. Se o endereço de email verificado da conta pessoal de um integrante empresarial no {% data variables.product.prodname_dotcom_the_website %} corresponder ao nome UPN de um assinante da conta do {% data variables.product.prodname_vs %}, o assinante do {% data variables.product.prodname_vs %} consumirá automaticamente uma licença do {% data variables.product.prodname_vss_ghe %}. +## About licenses for {% data variables.product.prodname_vss_ghe %} -A quantidade total de suas licenças para a sua empresa em {% data variables.product.prodname_dotcom %} é a soma de qualquer licença padrão de {% data variables.product.prodname_enterprise %} e o número de licenças de assinatura {% data variables.product.prodname_vs %} que incluem acesso a {% data variables.product.prodname_dotcom %}. Se a conta pessoal de um integrante corporativo não corresponde ao endereço de email de um assinante de {% data variables.product.prodname_vs %}, a licença que a conta pessoal consome não estará disponível para um assinante de {% data variables.product.prodname_vs %}. +After you assign a license for {% data variables.product.prodname_vss_ghe %} to a subscriber, the subscriber will use the {% data variables.product.prodname_enterprise %} portion of the license by joining an organization in your enterprise with a personal account on {% data variables.product.prodname_dotcom_the_website %}. If the verified email address for the personal account of an enterprise member on {% data variables.product.prodname_dotcom_the_website %} matches the User Primary Name (UPN) for a subscriber to your {% data variables.product.prodname_vs %} account, the {% data variables.product.prodname_vs %} subscriber will automatically consume one license for {% data variables.product.prodname_vss_ghe %}. -Para obter mais informações sobre o {% data variables.product.prodname_enterprise %}, confira "[Produtos do {% data variables.product.company_short %}](/github/getting-started-with-github/githubs-products#github-enterprise)". Para obter mais informações sobre as contas do {% data variables.product.prodname_dotcom_the_website %}, confira "[Tipos de contas do {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/types-of-github-accounts)". +The total quantity of your licenses for your enterprise on {% data variables.product.prodname_dotcom %} is the sum of any standard {% data variables.product.prodname_enterprise %} licenses and the number of {% data variables.product.prodname_vs %} subscription licenses that include access to {% data variables.product.prodname_dotcom %}. If the personal account for an enterprise member does not correspond with the email address for a {% data variables.product.prodname_vs %} subscriber, the license that the personal account consumes is unavailable for a {% data variables.product.prodname_vs %} subscriber. -Você pode visualizar o número de licenças de {% data variables.product.prodname_enterprise %} disponíveis para a sua empresa em {% data variables.product.product_location %}. A lista de convites pendentes inclui assinantes que ainda não são integrantes de pelo menos uma organização na sua empresa. Para obter mais informações, confira "[Como ver a assinatura e o uso da sua conta corporativa](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" e "[Como ver as pessoas da sua empresa](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-and-outside-collaborators)". +For more information about {% data variables.product.prodname_enterprise %}, see "[{% data variables.product.company_short %}'s products](/github/getting-started-with-github/githubs-products#github-enterprise)." For more information about accounts on {% data variables.product.prodname_dotcom_the_website %}, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/github/getting-started-with-github/types-of-github-accounts)." + +You can view the number of {% data variables.product.prodname_enterprise %} licenses available to your enterprise on {% data variables.location.product_location %}. The list of pending invitations includes subscribers who are not yet members of at least one organization in your enterprise. For more information, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" and "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-and-outside-collaborators)." {% tip %} -**Dica**: se você baixar um arquivo CSV com o uso de licença da sua empresa na etapa 6 de "[Como ver a assinatura e o uso da sua conta corporativa](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account#viewing-the-subscription-and-usage-for-your-enterprise-account)", isso indicará que os membros com um valor ausente nas colunas "Nome" ou "Perfil" ainda não aceitaram um convite para ingressar em uma organização na empresa. +**Tip**: If you download a CSV file with your enterprise's license usage in step 6 of "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account#viewing-the-subscription-and-usage-for-your-enterprise-account)," any members with a missing value for the "Name" or "Profile" columns have not yet accepted an invitation to join an organization within the enterprise. {% endtip %} -Você também pode ver convites pendentes de {% data variables.product.prodname_enterprise %} para inscritos em {% data variables.product.prodname_vss_admin_portal_with_url %}. +You can also see pending {% data variables.product.prodname_enterprise %} invitations to subscribers in {% data variables.product.prodname_vss_admin_portal_with_url %}. -## Leitura adicional +## Further reading -- [Assinaturas do {% data variables.product.prodname_vs %} com o {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/visualstudio/subscriptions/access-github) no Microsoft Docs -- [Usar o {% data variables.product.prodname_vs %} ou o {% data variables.product.prodname_vscode %} para implantar aplicativos do {% data variables.product.prodname_dotcom %}](https://docs.microsoft.com/en-us/azure/developer/github/deploy-with-visual-studio) no Microsoft Docs +- [{% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/visualstudio/subscriptions/access-github) in Microsoft Docs +- [Use {% data variables.product.prodname_vs %} or {% data variables.product.prodname_vscode %} to deploy apps from {% data variables.product.prodname_dotcom %}](https://docs.microsoft.com/en-us/azure/developer/github/deploy-with-visual-studio) in Microsoft Docs diff --git a/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md b/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md index 2f6b7a980e..41af3a41ef 100644 --- a/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md +++ b/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md @@ -1,6 +1,6 @@ --- -title: Configurando as assinaturas do Visual Studio com o GitHub Enterprise -intro: 'A assinatura da sua equipe para {% data variables.product.prodname_vs %} também pode fornecer acesso a {% data variables.product.prodname_enterprise %}.' +title: Setting up Visual Studio subscriptions with GitHub Enterprise +intro: 'Your team''s subscription to {% data variables.product.prodname_vs %} can also provide access to {% data variables.product.prodname_enterprise %}.' versions: ghec: '*' type: how_to @@ -8,67 +8,64 @@ topics: - Enterprise - Licensing shortTitle: Set up -ms.openlocfilehash: 644a106a749a8c8324b6a3e83dcaa72c8ad878b1 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717954' --- -## Sobre a configuração de {% data variables.product.prodname_vss_ghe %} -{% data reusables.enterprise-accounts.vss-ghe-description %} Para obter mais informações, confira "[Sobre o {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise)". +## About setup of {% data variables.product.prodname_vss_ghe %} -Este guia mostra como a sua equipe pode obter assinantes licenciados de {% data variables.product.prodname_vs %} e dar os primeiros passos com {% data variables.product.prodname_enterprise %}. +{% data reusables.enterprise-accounts.vss-ghe-description %} For more information, see "[About {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise)." -Se preferir assistir a um vídeo, assista a [Como configurar suas licenças do {% data variables.product.prodname_enterprise %} com as assinaturas do {% data variables.product.prodname_vs %}](https://www.youtube.com/watch?v=P_zBgp_BE_I) no canal do Microsoft Visual Studio no YouTube. +This guide shows you how your team can get {% data variables.product.prodname_vs %} subscribers licensed and started with {% data variables.product.prodname_enterprise %}. -## Funções para {% data variables.product.prodname_vss_ghe %} +If you prefer video, you can watch [Setting up your {% data variables.product.prodname_enterprise %} licenses with {% data variables.product.prodname_vs %} subscriptions](https://www.youtube.com/watch?v=P_zBgp_BE_I) on +Microsoft Visual Studio's YouTube channel. -Antes de configurar {% data variables.product.prodname_vss_ghe %}, é importante entender as funções para esta oferta combinada. +## Roles for {% data variables.product.prodname_vss_ghe %} -| Função | Serviço | Descrição | Mais informações | +Before setting up {% data variables.product.prodname_vss_ghe %}, it's important to understand the roles for this combined offering. + +| Role | Service | Description | More information | | :- | :- | :- | :- | -| **Administrador de assinaturas** | Assinatura de {% data variables.product.prodname_vs %} | Pessoa que atribui licenças para a assinatura de {% data variables.product.prodname_vs %} | [Visão geral das responsabilidades do administrador](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) no Microsoft Docs | -| **Assinante** | Assinatura de {% data variables.product.prodname_vs %} | Pessoa que usa uma licença para assinatura de {% data variables.product.prodname_vs %} | [Documentação das Assinaturas do Visual Studio](https://docs.microsoft.com/en-us/visualstudio/subscriptions/) no Microsoft Docs | -| **Proprietário da empresa** | {% data variables.product.prodname_dotcom %} | Pessoa que tem uma conta pessoal que é administrador de uma empresa em {% data variables.product.product_location %} | "[Funções em uma empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)" | -| **Proprietário da organização** | {% data variables.product.prodname_dotcom %} | Pessoa que tem uma conta pessoal que é proprietário de uma organização na empresa da sua equipe em {% data variables.product.product_location %} | "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners)" | -| **Membro da empresa** | {% data variables.product.prodname_dotcom %} | Pessoa que tem uma conta pessoal que é integrante de uma empresa em {% data variables.product.product_location %} | "[Funções em uma empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members)" | +| **Subscriptions admin** | {% data variables.product.prodname_vs %} subscription | Person who assigns licenses for {% data variables.product.prodname_vs %} subscription | [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs | +| **Subscriber** | {% data variables.product.prodname_vs %} subscription | Person who uses a license for {% data variables.product.prodname_vs %} subscription | [Visual Studio Subscriptions documentation](https://docs.microsoft.com/en-us/visualstudio/subscriptions/) in Microsoft Docs | +| **Enterprise owner** | {% data variables.product.prodname_dotcom %} | Person who has a personal account that's an administrator of an enterprise on {% data variables.location.product_location %} | "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)" | +| **Organization owner** | {% data variables.product.prodname_dotcom %} | Person who has a personal account that's an owner of an organization in your team's enterprise on {% data variables.location.product_location %} | "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners)" | +| **Enterprise member** | {% data variables.product.prodname_dotcom %} | Person who has a personal account that's a member of an enterprise on {% data variables.location.product_location %} | "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members)" | -## Pré-requisitos +## Prerequisites -- A assinatura da sua equipe de {% data variables.product.prodname_vs %} deve incluir {% data variables.product.prodname_enterprise %}. Para obter mais informações, confira [Assinaturas e benefícios do {% data variables.product.prodname_vs %}](https://visualstudio.microsoft.com/subscriptions/) no site do {% data variables.product.prodname_vs %} e [Visão geral das responsabilidades do administrador](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) no Microsoft Docs. +- Your team's {% data variables.product.prodname_vs %} subscription must include {% data variables.product.prodname_enterprise %}. For more information, see [{% data variables.product.prodname_vs %} Subscriptions and Benefits](https://visualstudio.microsoft.com/subscriptions/) on the {% data variables.product.prodname_vs %} website and + [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs. - - A sua equipe deve ter uma empresa em {% data variables.product.product_location %}. Se você não tiver certeza se sua equipe tem uma empresa, entre em contato com o administrador de {% data variables.product.prodname_dotcom %}. Se você não iver certeza de quem na sua equipe é responsável por {% data variables.product.prodname_dotcom %}, entre em contato com {% data variables.contact.contact_enterprise_sales %}. Para obter mais informações, confira "[Sobre as contas corporativas](/admin/overview/about-enterprise-accounts)". + - Your team must have an enterprise on {% data variables.location.product_location %}. If you're not sure whether your team has an enterprise, contact your {% data variables.product.prodname_dotcom %} administrator. If you're not sure who on your team is responsible for {% data variables.product.prodname_dotcom %}, contact {% data variables.contact.contact_enterprise_sales %}. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)." -## Como configurar o {% data variables.product.prodname_vss_ghe %} +## Setting up {% data variables.product.prodname_vss_ghe %} -Para configurar {% data variables.product.prodname_vss_ghe %}, os integrantes da sua equipe deverão concluir as tarefas a seguir. +To set up {% data variables.product.prodname_vss_ghe %}, members of your team must complete the following tasks. -Uma pessoa pode ser capaz de concluir as tarefas porque a pessoa tem todas as funções, mas você pode precisar coordenar as tarefas com várias pessoas. Para obter mais informações, confira "[Funções do {% data variables.product.prodname_vss_ghe %}](#roles-for-visual-studio-subscriptions-with-github-enterprise)". +One person may be able to complete the tasks because the person has all of the roles, but you may need to coordinate the tasks with multiple people. For more information, see "[Roles for {% data variables.product.prodname_vss_ghe %}](#roles-for-visual-studio-subscriptions-with-github-enterprise)." -1. O proprietário de uma empresa deve criar pelo menos uma organização na sua empresa em {% data variables.product.product_location %}. Para obter mais informações, confira "[Como adicionar organizações à sua empresa](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)". +1. An enterprise owner must create at least one organization in your enterprise on {% data variables.location.product_location %}. For more information, see "[Adding organizations to your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)." -1. O administrador da assinatura deve atribuir uma licença para {% data variables.product.prodname_vs %} para um assinante em {% data variables.product.prodname_vss_admin_portal_with_url %}. Para obter mais informações, confira [Visão geral do Portal do Administrador das Assinaturas do {% data variables.product.prodname_vs %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/using-admin-portal) e [Atribuir licenças do {% data variables.product.prodname_vs %} no Portal de Administração das Assinaturas do {% data variables.product.prodname_vs %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-license) no Microsoft Docs. +1. The subscription admin must assign a license for {% data variables.product.prodname_vs %} to a subscriber in {% data variables.product.prodname_vss_admin_portal_with_url %}. For more information, see [Overview of the {% data variables.product.prodname_vs %} Subscriptions Administrator Portal](https://docs.microsoft.com/en-us/visualstudio/subscriptions/using-admin-portal) and [Assign {% data variables.product.prodname_vs %} Licenses in the {% data variables.product.prodname_vs %} Subscriptions Administration Portal](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-license) in Microsoft Docs. -1. Opcionalmente, se o administrador da assinatura atribuiu licenças aos assinantes em {% data variables.product.prodname_vs %} antes de adicionar {% data variables.product.prodname_enterprise %} à assinatura, o administrador da assinatura poderá mover os assinantes para as ofertas combinadas no portal de administração de {% data variables.product.prodname_vs %}. Para obter mais informações, confira [Gerenciar as assinaturas do {% data variables.product.prodname_vs %} com o {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-github#moving-to-visual-studio-with-github-enterprise) no Microsoft Docs. +1. Optionally, if the subscription admin assigned licenses to subscribers in {% data variables.product.prodname_vs %} before adding {% data variables.product.prodname_enterprise %} to the subscription, the subscription admin can move the subscribers to the combined offering in the {% data variables.product.prodname_vs %} administration portal. For more information, see [Manage {% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-github#moving-to-visual-studio-with-github-enterprise) in Microsoft Docs. -1. Se o administrador da assinatura não tiver desabilitado as notificações por e-mail, o assinante receberá dois e-mails de confirmação. Para obter mais informações, confira [Assinaturas do {% data variables.product.prodname_vs %} com o {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/access-github#what-is-the-visual-studio-subscription-with-github-enterprise-setup-process) no Microsoft Docs. +1. If the subscription admin has not disabled email notifications, the subscriber will receive two confirmation emails. For more information, see [{% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/access-github#what-is-the-visual-studio-subscription-with-github-enterprise-setup-process) in Microsoft Docs. -1. O proprietário de uma organização deve convidar o integrante para a organização no {% data variables.product.product_location %} a partir da etapa 1. O assinante pode aceitar o convite com uma conta pessoal existente em {% data variables.product.prodname_dotcom_the_website %} ou criar uma nova conta. Depois que o assinante aderir à organização, o assinante torna-se um integrante da empresa. Para obter mais informações, confira "[Como convidar usuários para ingressar na sua organização](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)". +1. An organization owner must invite the subscriber to the organization on {% data variables.location.product_location %} from step 1. The subscriber can accept the invitation with an existing personal account on {% data variables.product.prodname_dotcom_the_website %} or create a new account. After the subscriber joins the organization, the subscriber becomes an enterprise member. For more information, see "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)." {% tip %} - **Dicas**: + **Tips**: - - Embora não seja necessário, recomendamos que o proprietário da organização envie um convite para o mesmo endereço de e-mail usado para o nome primário do usuário do assinante (UPN). Quando o endereço de e-mail em {% data variables.product.product_location %} corresponder ao UPN do assinante, você poderá garantir que outra empresa não reivindique a licença do assinante. - - Se o assinante aceitar o convite para a organização com uma conta pessoal existente em {% data variables.product.product_location %}, recomendamos que o assinante adicione o endereço de e-mail que ele usa para {% data variables.product.prodname_vs %} à sua conta pessoal em {% data variables.product.product_location %}. Para obter mais informações, confira "[Como adicionar um endereço de email à sua conta do {% data variables.product.prodname_dotcom %}](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account)". - - Se o proprietário da organização tiver de convidar um grande número de assinantes, um script poderá agilizar o processo. Para obter mais informações, confira [o exemplo de script do PowerShell](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1) no repositório `github/platform-samples`. + - While not required, we recommend that the organization owner sends an invitation to the same email address used for the subscriber's User Primary Name (UPN). When the email address on {% data variables.location.product_location %} matches the subscriber's UPN, you can ensure that another enterprise does not claim the subscriber's license. + - If the subscriber accepts the invitation to the organization with an existing personal account on {% data variables.location.product_location %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their personal account on {% data variables.location.product_location %}. For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account)." + - If the organization owner must invite a large number of subscribers, a script may make the process faster. For more information, see [the sample PowerShell script](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1) in the `github/platform-samples` repository. {% endtip %} -Depois de {% data variables.product.prodname_vss_ghe %} ser definido para assinantes da sua equipe, os proprietários da empresa poderão revisar as informações de licenciamento em {% data variables.product.product_location %}. Para obter mais informações, confira "[Como ver a assinatura e o uso da sua conta corporativa](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)". +After {% data variables.product.prodname_vss_ghe %} is set up for subscribers on your team, enterprise owners can review licensing information on {% data variables.location.product_location %}. For more information, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)." -## Leitura adicional +## Further reading -- "[Introdução ao {% data variables.product.prodname_ghe_cloud %}](/get-started/onboarding/getting-started-with-github-enterprise-cloud)" +- "[Getting started with {% data variables.product.prodname_ghe_cloud %}](/get-started/onboarding/getting-started-with-github-enterprise-cloud)" diff --git a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md index c657eead52..2a8b764350 100644 --- a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md +++ b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md @@ -1,6 +1,6 @@ --- -title: Sobre licenças para o GitHub Enterprise -intro: '{% ifversion ghec %}Se você implantar {% data variables.product.prodname_ghe_server %} além de usar {% data variables.product.prodname_ghe_cloud %}, você{% else %}Você{% endif %} poderá sincronizar o uso de sua licença entre implementações de {% ifversion ghes %} {% data variables.product.prodname_enterprise %}{% endif %} e usar um arquivo de licença para desbloquear cada instância {% data variables.product.prodname_ghe_server %}.' +title: About licenses for GitHub Enterprise +intro: '{% ifversion ghec %}If you deploy {% data variables.product.prodname_ghe_server %} in addition to using {% data variables.product.prodname_ghe_cloud %}, you{% else %}You{% endif %} can synchronize your license usage between{% ifversion ghes %} {% data variables.product.prodname_enterprise %}{% endif %} deployments, and use a license file to unlock each {% data variables.product.prodname_ghe_server %} instance.' versions: ghec: '*' ghes: '*' @@ -9,41 +9,36 @@ topics: - Enterprise - Licensing shortTitle: About licenses -ms.openlocfilehash: eb904ed497df785cfefa25cee7a5cb1fe5acfaa0 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145910508' --- -## Sobre o licenciamento de {% data variables.product.prodname_enterprise %} + +## About licensing for {% data variables.product.prodname_enterprise %} {% data reusables.enterprise.about-deployment-methods %} {% data reusables.enterprise-licensing.unique-user-licensing-model %} -Para garantir que o mesmo usuário não esteja consumindo mais de uma licença para várias implantações empresariais, você pode sincronizar o uso de licença entre as implantações {% data variables.product.prodname_ghe_server %} e {% data variables.product.prodname_ghe_cloud %}. +To ensure the same user isn't consuming more than one license for multiple enterprise deployments, you can synchronize license usage between your {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} deployments. -Para usar uma instância de {% data variables.product.prodname_ghe_server %}, você deve carregar um arquivo de licença que o {% data variables.product.company_short %} fornece quando você compra, renova ou adiciona licenças de usuário a {% data variables.product.prodname_enterprise %}. +In order to use a {% data variables.product.prodname_ghe_server %} instance, you must upload a license file that {% data variables.product.company_short %} provides when you purchase, renew, or add user licenses to {% data variables.product.prodname_enterprise %}. -## Sobre a sincronização do uso da licença para {% data variables.product.prodname_enterprise %} +## About synchronization of license usage for {% data variables.product.prodname_enterprise %} -{% data reusables.enterprise-licensing.about-license-sync %} Para mais informações, confira "[Como sincronizar o uso da licença entre {% data variables.product.prodname_ghe_server %} e {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)". +{% data reusables.enterprise-licensing.about-license-sync %} For more information, see "[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)." -## Sobre os arquivos de licença para {% data variables.product.prodname_enterprise %} +## About license files for {% data variables.product.prodname_enterprise %} -Quando você compra ou renova o {% data variables.product.prodname_enterprise %}, o {% data variables.product.company_short %} fornece um arquivo de licença {% ifversion ghec %}para suas implantações do {% data variables.product.prodname_ghe_server %}{% elsif ghes %}para o {% data variables.product.product_location_enterprise %}{% endif %}. O arquivo de uma licença tem uma data de validade e controla o número de pessoas que podem usar {% data variables.product.product_location_enterprise %}. Após fazer o download e instalar o {% data variables.product.prodname_ghe_server %}, você deverá fazer o upload do arquivo de licença para desbloquear o aplicativo para você usar. +When you purchase or renew {% data variables.product.prodname_enterprise %}, {% data variables.product.company_short %} provides a license file {% ifversion ghec %}for your deployments of {% data variables.product.prodname_ghe_server %}{% elsif ghes %}for {% data variables.location.product_location_enterprise %}{% endif %}. A license file has an expiration date and controls the number of people who can use {% data variables.location.product_location_enterprise %}. After you download and install {% data variables.product.prodname_ghe_server %}, you must upload the license file to unlock the application for you to use. -Para obter mais informações sobre como baixar o arquivo de licença, confira "[Como baixar sua licença do {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)". +For more information about downloading your license file, see "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)." -Para obter mais informações sobre como carregar seu arquivo de licença, confira {% ifversion ghec %}"[Como carregar uma nova licença do {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" na documentação do {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}"[Como carregar uma nova licença do {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)".{% endif %} +For more information about uploading your license file, see {% ifversion ghec %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% endif %} -Se sua licença vencer, você não poderá acessar {% data variables.product.prodname_ghe_server %} por meio de um navegador ou Git. Se necessário, você poderá usar os utilitários de linha de comando para fazer backup de todos os seus dados. Para obter mais informações, confira {% ifversion ghec %}"[Como configurar backups no seu dispositivo]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/guides/installation/configuring-backups-on-your-appliance)" na documentação do {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}"[Como configurar backups no seu dispositivo](/admin/guides/installation/configuring-backups-on-your-appliance)". {% endif %} +If your license expires, you won't be able to access {% data variables.product.prodname_ghe_server %} via a web browser or Git. If needed, you will be able to use command-line utilities to back up all your data. For more information, see {% ifversion ghec %}"[Configuring backups on your appliance]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/guides/installation/configuring-backups-on-your-appliance)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Configuring backups on your appliance](/admin/guides/installation/configuring-backups-on-your-appliance)." {% endif %} -Se você tiver alguma dúvida sobre a renovação da sua licença, contate {% data variables.contact.contact_enterprise_sales %}. +If you have any questions about renewing your license, contact {% data variables.contact.contact_enterprise_sales %}. -## Leitura adicional +## Further reading -- "[Sobre a cobrança para sua empresa](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)" -- Site [Versões do {% data variables.product.prodname_enterprise %}](https://enterprise.github.com/releases/) -- "[Como configurar uma instância do {% data variables.product.prodname_ghe_server %}]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/installation/setting-up-a-github-enterprise-server-instance)" +- "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)" +- [{% data variables.product.prodname_enterprise %} Releases](https://enterprise.github.com/releases/) website +- "[Setting up a {% data variables.product.prodname_ghe_server %} instance]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/installation/setting-up-a-github-enterprise-server-instance)" diff --git a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md index 5d5a88a117..9e67e9dfa4 100644 --- a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md +++ b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md @@ -1,6 +1,6 @@ --- -title: Fazendo o download da sua licença para o GitHub Enterprise -intro: 'Você pode fazer o download de uma cópia do arquivo da sua licença para {% data variables.product.prodname_ghe_server %}.' +title: Downloading your license for GitHub Enterprise +intro: 'You can download a copy of your license file for {% data variables.product.prodname_ghe_server %}.' permissions: 'Enterprise owners can download license files for {% data variables.product.prodname_ghe_server %}.' versions: ghec: '*' @@ -10,33 +10,29 @@ topics: - Enterprise - Licensing shortTitle: Download your license -ms.openlocfilehash: eed588e2580558280e2e11639f0904b5f9fcf118 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145083419' --- -## Sobre os arquivos de licença para {% data variables.product.prodname_enterprise %} -Após comprar ou atualizar uma licença para {% data variables.product.prodname_enterprise %} de {% data variables.contact.contact_enterprise_sales %}, você deverá fazer o download do arquivo da sua nova licença. Para obter mais informações sobre licenças do {% data variables.product.prodname_enterprise %}, confira "[Sobre as licenças do {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)". +## About license files for {% data variables.product.prodname_enterprise %} + +After you purchase or upgrade a license for {% data variables.product.prodname_enterprise %} from {% data variables.contact.contact_enterprise_sales %}, you must download your new license file. For more information about licenses for {% data variables.product.prodname_enterprise %}, see "[About licenses for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)." {% data reusables.enterprise-licensing.contact-sales-for-renewals-or-seats %} -## Fazer o download da sua licença de {% data variables.product.prodname_dotcom_the_website %} +## Downloading your license from {% data variables.product.prodname_dotcom_the_website %} -Você deve ter uma conta corporativa em {% data variables.product.prodname_dotcom_the_website %} para fazer o download da sua licença em {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, confira "[Sobre as contas corporativas](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion ghes %}" na documentação do {% data variables.product.prodname_ghe_cloud %}.{% elsif ghec %}".{% endif %} +You must have an enterprise account on {% data variables.product.prodname_dotcom_the_website %} to download your license from {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion ghes %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% elsif ghec %}."{% endif %} -{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} -1. Na barra lateral esquerda, clique em **Licenciamento do Enterprise**. - ![Guia "Licenciamento do Enterprise" na barra lateral das configurações da conta corporativa](/assets/images/help/enterprises/enterprise-licensing-tab.png) -1. Em "Instâncias do Enterprise Server", clique em {% octicon "download" aria-label="The download icon" %} para baixar o arquivo de licença. - ![Baixar licença do GitHub Enterprise Server](/assets/images/help/business-accounts/download-ghes-license.png) +{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} +{% data reusables.enterprise-accounts.settings-tab %} +1. In the left sidebar, click **Enterprise licensing**. + !["Enterprise licensing" tab in the enterprise account settings sidebar](/assets/images/help/enterprises/enterprise-licensing-tab.png) +1. Under "Enterprise Server Instances", click {% octicon "download" aria-label="The download icon" %} to download your license file. + ![Download GitHub Enterprise Server license](/assets/images/help/business-accounts/download-ghes-license.png) -Depois de fazer o download do arquivo da sua licença, você poderá enviar o arquivo para {% data variables.product.product_location_enterprise %} para validar seu aplicativo. Para obter mais informações, confira {% ifversion ghec %}"[Como carregar uma nova licença do {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" na documentação do {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}"[Como carregar uma nova licença do {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)".{% endif %} +After you download your license file, you can upload the file to {% data variables.location.product_location_enterprise %} to validate your application. For more information, see {% ifversion ghec %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% endif %} -## Fazer o download da sua licença se você não tiver uma conta corporativa em {% data variables.product.prodname_dotcom_the_website %} +## Downloading your license if you don't have an enterprise account on {% data variables.product.prodname_dotcom_the_website %} -Caso você não tenha uma conta corporativa do {% data variables.product.prodname_dotcom_the_website %}, ou não tenha certeza, talvez consiga baixar a licença do {% data variables.product.prodname_ghe_server %} no [site do {% data variables.product.prodname_enterprise %}](https://enterprise.github.com/download). +If you do not have an enterprise account on {% data variables.product.prodname_dotcom_the_website %}, or if you're not sure, you may be able to download your {% data variables.product.prodname_ghe_server %} license from the [{% data variables.product.prodname_enterprise %} website](https://enterprise.github.com/download). -Em caso de dúvidas sobre o download da sua licença, entre em contato com {% data variables.contact.contact_enterprise_sales %}. +If you have any questions about downloading your license, contact {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md index 437013070a..e66cfc6dd6 100644 --- a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md +++ b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md @@ -1,6 +1,6 @@ --- -title: Fazer o upload uma nova licença para o GitHub Enterprise Server -intro: 'Você pode fazer o upload do arquivo da sua licença para {% data variables.product.prodname_enterprise %} para {% data variables.product.product_location_enterprise %} a fim de validar seu aplicativo.' +title: Uploading a new license to GitHub Enterprise Server +intro: 'You can upload your license file for {% data variables.product.prodname_enterprise %} to {% data variables.location.product_location_enterprise %} to validate your application.' versions: ghes: '*' type: how_to @@ -8,33 +8,30 @@ topics: - Enterprise - Licensing shortTitle: Upload a new license -ms.openlocfilehash: 184206b210289e062e83e237acaa853bb80470c1 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145083414' --- -## Sobre os arquivos de licença para {% data variables.product.prodname_enterprise %} -Após comprar ou atualizar uma licença para {% data variables.product.prodname_enterprise %} de {% data variables.contact.contact_enterprise_sales %}, você deverá fazer o upload do novo arquivo de licença para {% data variables.product.product_location_enterprise %} para desbloquear suas novas licenças de usuário. Para obter mais informações sobre as licenças do {% data variables.product.product_name %}, confira "[Sobre as licenças do {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)" e "[Como baixar sua licença do {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)". +## About license files for {% data variables.product.prodname_enterprise %} + +After you purchase or upgrade a license for {% data variables.product.prodname_enterprise %} from {% data variables.contact.contact_enterprise_sales %}, you must upload the new license file to {% data variables.location.product_location_enterprise %} to unlock your new user licenses. For more information about licenses for {% data variables.product.product_name %}, see "[About licenses for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)" and "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)." {% data reusables.enterprise-licensing.contact-sales-for-renewals-or-seats %} -## Fazendo o upload da sua licença para {% data variables.product.product_location_enterprise %} +## Uploading your license to {% data variables.location.product_location_enterprise %} {% warning %} -**Aviso:** a atualização da sua licença gera uma pequena quantidade de tempo de inatividade no {% data variables.product.product_location %}. +**Warning:** Updating your license causes a small amount of downtime for {% data variables.location.product_location %}. {% endwarning %} -1. Entre no {% data variables.product.product_location_enterprise %} como administrador do site. -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -1. Em "Links rápidos", clique em **Atualizar licença**. - ![Link Atualizar licença](/assets/images/enterprise/business-accounts/update-license-link.png) -1. Para selecionar sua licença, clique em **Arquivo de licença** ou arraste o arquivo de licença para **Arquivo de licença**. - ![Upload do arquivo de licença](/assets/images/enterprise/management-console/upload-license.png) -1. Clique em **Carregar**. - ![Início do upload](/assets/images/enterprise/management-console/begin-upload.png) +1. Sign into {% data variables.location.product_location_enterprise %} as a site administrator. +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.license-tab %} +1. Under "Quick links", click **Update license**. + ![Update license link](/assets/images/enterprise/business-accounts/update-license-link.png) +1. To select your license, click **License file**, or drag your license file onto **License file**. + ![Upload license file](/assets/images/enterprise/management-console/upload-license.png) +1. Click **Upload**. + ![Begin upload](/assets/images/enterprise/management-console/begin-upload.png) diff --git a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md index ffc4a76cb9..452c276d23 100644 --- a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md +++ b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md @@ -1,6 +1,6 @@ --- -title: Visualizando o uso da licença para o GitHub Enterprise -intro: 'Você pode ver o uso de licença na empresa no {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.' +title: Viewing license usage for GitHub Enterprise +intro: 'You can view license usage for your enterprise on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.location.product_location %}{% endif %}.' permissions: 'Enterprise owners can view license usage for {% data variables.product.prodname_enterprise %}.' versions: ghec: '*' @@ -10,59 +10,59 @@ topics: - Enterprise - Licensing shortTitle: View license usage -ms.openlocfilehash: 7f3c3c6e65928601d01ac17139928af6ceedf354 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147572613' --- -## Sobre o uso da licença para {% data variables.product.prodname_enterprise %} -Você pode visualizar o uso da licença para {% data variables.product.product_name %} em {% data variables.product.product_location %}. +## About license usage for {% data variables.product.prodname_enterprise %} -Se você usar o {% data variables.product.prodname_ghe_cloud %} e o {% data variables.product.prodname_ghe_server %} e sincronizar o uso da licença entre os produtos, poderá ver o uso da licença dos dois no {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações sobre sincronização de licenças, confira "[Sincronizando o uso de licenças entre o {% data variables.product.prodname_ghe_server %} e o {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)". +You can view license usage for {% data variables.product.product_name %} on {% data variables.location.product_location %}. + +If you use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} and sync license usage between the products, you can view license usage for both on {% data variables.product.prodname_dotcom_the_website %}. For more information about license sync, see "[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)." {% ifversion ghes %} -Para obter mais informações sobre a exibição do uso de licença no {% data variables.product.prodname_dotcom_the_website %} e identificar quando a ocorreu a última sincronização de licença, confira "[Como ver o uso de licença do {% data variables.product.prodname_enterprise %}](/enterprise-cloud@latest/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise)" na documentação do {% data variables.product.prodname_ghe_cloud %}. +For more information about viewing license usage on {% data variables.product.prodname_dotcom_the_website %} and identifying when the last license sync occurred, see "[Viewing license usage for {% data variables.product.prodname_enterprise %}](/enterprise-cloud@latest/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise)" in the {% data variables.product.prodname_ghe_cloud %} documentation. {% endif %} -Você também pode usar a API REST para retornar dados de licenças consumidas e o status do trabalho de sincronização de licenças. Para obter mais informações, confira "[Administração do GitHub Enterprise](/enterprise-cloud@latest/rest/enterprise-admin/license)" na documentação da API REST. +You can also use the REST API to return consumed licenses data and the status of the license sync job. For more information, see "[GitHub Enterprise administration](/enterprise-cloud@latest/rest/enterprise-admin/license)" in the REST API documentation. -Para saber mais sobre os dados de licença associados à conta empresarial e como o número de estações de usuário consumidas é calculado, confira "[Como solucionar problemas de uso de licença do GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)". +To learn more about the license data associated with your enterprise account and how the number of consumed user seats are calculated, see "[Troubleshooting license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)." -## Como ver o uso da licença do {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %} +## Viewing license usage on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.location.product_location %}{% endif %} -Você pode visualizar o uso da licença para a sua empresa e fazer o download de um arquivo com detalhes da licença. Se você não estiver vendo as contagens de licença esperadas neste relatório, é possível que o endereço de email da assinatura do {% data variables.product.prodname_vs %} e o endereço de email do {% data variables.product.prodname_dotcom_the_website %} atribuído ao assinante não sejam exatamente iguais. Para obter mais informações, confira "[Como solucionar problemas de uso de licença do GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)". +You can view the license usage for your enterprise and download a file with license details. If you're not seeing expected license counts in this report, it's possible that the subscriber’s assigned {% data variables.product.prodname_vs %} subscription email address and {% data variables.product.prodname_dotcom_the_website %} email address aren't exactly the same. For further information, see "[Troubleshooting license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)." {% ifversion ghec %} -{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} -1. Na barra lateral esquerda, clique em **Licenciamento do Enterprise**. - ![Guia "Licenciamento do Enterprise" na barra lateral das configurações da conta corporativa](/assets/images/help/enterprises/enterprise-licensing-tab.png) -1. Revise sua licença atual de {% data variables.product.prodname_enterprise %}, bem como licenças de usuário consumidas e disponíveis. - - Para baixar o relatório de licença consumida como um arquivo CSV, no canto superior direito, clique em {% octicon "download" aria-label="The download icon" %}. Para obter mais informações de como examinar os dados nesse relatório, confira "[Como solucionar problemas de uso de licença do GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)". - - Se sua licença incluir {% data variables.product.prodname_GH_advanced_security %}, você poderá revisar o uso total de estações. Para obter mais informações, confira "[Como ver seu uso do {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)". +{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} +{% data reusables.enterprise-accounts.settings-tab %} +1. In the left sidebar, click **Enterprise licensing**. + !["Enterprise licensing" tab in the enterprise account settings sidebar](/assets/images/help/enterprises/enterprise-licensing-tab.png) +1. Review your current {% data variables.product.prodname_enterprise %} license, as well as consumed and available user licenses. + - To download the consumed license report as a CSV file, in the top right, click {% octicon "download" aria-label="The download icon" %}. For more information about reviewing the data in this report, see "[Troubleshooting license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)." + - If your license includes {% data variables.product.prodname_GH_advanced_security %}, you can review your total seat use. For more information, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)." {% elsif ghes %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -1. Revise sua licença atual do {% data variables.product.prodname_enterprise %}, bem como as licenças de usuário consumidas e disponíveis.{% ifversion ghes %} - - Para baixar o relatório de licença consumida como um arquivo JSON, no canto superior direito em "Links rápidos", clique em **Exportar o uso de licença**. Para obter mais informações de como examinar os dados nesse relatório, confira "[Como solucionar problemas de uso de licença do GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)". - - Se sua licença incluir {% data variables.product.prodname_GH_advanced_security %}, você poderá revisar o uso total de estações, bem como o detalhamento por organização dos committers. Para obter mais informações, confira "[Como gerenciar o {% data variables.product.prodname_GH_advanced_security %} para sua empresa](/admin/advanced-security)".{% endif %} - -{% endif %} {% ifversion ghec %} -## Como ver a última data de sincronização de licença - -{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} -1. Na barra lateral esquerda, clique em **Licenciamento do Enterprise**. - ![Guia "Licenciamento do Enterprise" na barra lateral das configurações da conta corporativa](/assets/images/help/enterprises/enterprise-licensing-tab.png) -1. Para identificar quando ocorreu a última sincronização de licença, em "Instâncias do Enterprise Server", procure carimbos de data/hora ao lado de eventos de uso carregados ou sincronizados. - - "Uso do servidor carregado" indica que o uso de licença entre ambientes foi atualizado manualmente quando um arquivo de licença do {% data variables.product.prodname_ghe_server %} foi carregado. - - "Uso do servidor {% data variables.product.prodname_github_connect %} sincronizado" indica que o uso de licença entre ambientes foi atualizado automaticamente. - - "Uso do servidor {% data variables.product.prodname_github_connect %} nunca sincronizado" indica que o {% data variables.product.prodname_github_connect %} está configurado, mas o uso de licença entre ambientes nunca foi atualizado com êxito. +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.license-tab %} +1. Review your current {% data variables.product.prodname_enterprise %} license, as well as consumed and available user licenses.{% ifversion ghes %} + - To download the consumed license report as a JSON file, in the top right under "Quick links", choose **Export license usage**. For more information about reviewing the data in this report, see "[Troubleshooting license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)." + - If your license includes {% data variables.product.prodname_GH_advanced_security %}, you can review your total seat use as well as a per-organization breakdown of committers. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security)."{% endif %} + +{% endif %} +{% ifversion ghec %} +## Viewing the last license sync date + +{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} +{% data reusables.enterprise-accounts.settings-tab %} +1. In the left sidebar, click **Enterprise licensing**. + !["Enterprise licensing" tab in the enterprise account settings sidebar](/assets/images/help/enterprises/enterprise-licensing-tab.png) +1. To identify when the last license sync occurred, under "Enterprise Server instances", look for timestamps next to usage uploaded or synced events. + - "Server usage uploaded" indicates license usage between environments was manually updated when a {% data variables.product.prodname_ghe_server %} license file was uploaded. + - "{% data variables.product.prodname_github_connect %} server usage synced" indicates license usage between environments was automatically updated. + - "{% data variables.product.prodname_github_connect %} server usage never synced" indicates that {% data variables.product.prodname_github_connect %} is configured, but license usage between environments has never updated successfully. {% endif %} diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md index 4dca5936e8..e7a4e2b032 100644 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md +++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md @@ -351,7 +351,7 @@ If your workflow uses packs that are published on a {% data variables.product.pr {% endraw %} ``` -The package patterns in the registries list are examined in order, so you should generally place the most specific package patterns first. The values for `token` must be a personal access token generated by the GitHub instance you are downloading from with the `read:packages` permission. +The package patterns in the registries list are examined in order, so you should generally place the most specific package patterns first. The values for `token` must be a {% data variables.product.pat_v1 %} generated by the GitHub instance you are downloading from with the `read:packages` permission. Notice the `|` after the `registries` property name. This is important since {% data variables.product.prodname_actions %} inputs can only accept strings. Using the `|` converts the subsequent text to a string, which is parsed later by the {% data reusables.actions.action-codeql-action-init %} action. diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md index 9ccc35879e..2066a0a5cc 100644 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md +++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md @@ -1,6 +1,6 @@ --- -title: Visualizar os registros de varredura de código -intro: 'Você pode visualizar a saída gerada durante a análise {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_location %}.' +title: Viewing code scanning logs +intro: 'You can view the output generated during {% data variables.product.prodname_code_scanning %} analysis in {% data variables.location.product_location %}.' product: '{% data reusables.gated-features.code-scanning %}' permissions: 'If you have write permissions to a repository, you can view the {% data variables.product.prodname_code_scanning %} logs for that repository.' miniTocMaxHeadingLevel: 4 @@ -14,73 +14,69 @@ versions: topics: - Security shortTitle: View code scanning logs -ms.openlocfilehash: e4f4c3e601540e02c01bbe3761a11528a746a519 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147444626' --- -{% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} -## Sobre sua configuração de {% data variables.product.prodname_code_scanning %} +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} -Você pode usar uma série de ferramentas para configurar {% data variables.product.prodname_code_scanning %} no seu repositório. Para obter mais informações, confira "[Como configurar a {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#options-for-setting-up-code-scanning)". +## About your {% data variables.product.prodname_code_scanning %} setup -A informação de registro e diagnóstico disponível para você depende do método que você usa para {% data variables.product.prodname_code_scanning %} no repositório. Você pode verificar o tipo da {% data variables.product.prodname_code_scanning %} que você está usando na guia **Segurança** do repositório usando o menu suspenso **Ferramenta** na lista de alertas. Para obter mais informações, confira "[Como gerenciar alertas da {% data variables.product.prodname_code_scanning %} do seu repositório](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)". +You can use a variety of tools to set up {% data variables.product.prodname_code_scanning %} in your repository. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#options-for-setting-up-code-scanning)." -## Sobre análise e informações de diagnóstico +The log and diagnostic information available to you depends on the method you use for {% data variables.product.prodname_code_scanning %} in your repository. You can check the type of {% data variables.product.prodname_code_scanning %} you're using in the **Security** tab of your repository, by using the **Tool** drop-down menu in the alert list. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." -Você pode visualizar as análises e informações de diagnóstico para {% data variables.product.prodname_code_scanning %} executar usando as análises de {% data variables.product.prodname_codeql %} em {% data variables.product.prodname_dotcom %}. +## About analysis and diagnostic information -As informações de **análise** são mostradas para a análise mais recente em um cabeçalho na parte superior da lista de alertas. Para obter mais informações, confira "[Como gerenciar alertas de verificação de código do seu repositório](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)". +You can see analysis and diagnostic information for {% data variables.product.prodname_code_scanning %} run using {% data variables.product.prodname_codeql %} analysis on {% data variables.product.prodname_dotcom %}. -As informações de **diagnóstico** são exibidas nos logs de fluxo de trabalho da Ação e consistem em métricas de resumo e diagnóstico do extrator. Para obter informações sobre como acessar os logs da {% data variables.product.prodname_code_scanning %} no {% data variables.product.prodname_dotcom %}, confira "[Como ver a saída de log da {% data variables.product.prodname_code_scanning %}](#viewing-the-logging-output-from-code-scanning)" abaixo. +**Analysis** information is shown for the most recent analysis in a header at the top of the list of alerts. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." -Se você estiver utilizando o {% data variables.product.prodname_codeql_cli %} fora de {% data variables.product.prodname_dotcom %}, você verá informações de diagnóstico na saída gerada durante a análise do banco de dados. Estas informações também estão incluídas nos resultados do SARIF que você enviou para {% data variables.product.prodname_dotcom %} com os resultados de {% data variables.product.prodname_code_scanning %}. +**Diagnostic** information is displayed in the Action workflow logs and consists of summary metrics and extractor diagnostics. For information about accessing {% data variables.product.prodname_code_scanning %} logs on {% data variables.product.prodname_dotcom %}, see "[Viewing the logging output from {% data variables.product.prodname_code_scanning %}](#viewing-the-logging-output-from-code-scanning)" below. -Para obter informações sobre a {% data variables.product.prodname_codeql_cli %}, confira "[Como configurar o {% data variables.product.prodname_codeql_cli %} no seu sistema de CI](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)". +If you're using the {% data variables.product.prodname_codeql_cli %} outside {% data variables.product.prodname_dotcom %}, you'll see diagnostic information in the output generated during database analysis. This information is also included in the SARIF results file you upload to {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_code_scanning %} results. -### Sobre métricas resumidas +For information about the {% data variables.product.prodname_codeql_cli %}, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)." + +### About summary metrics {% data reusables.code-scanning.summary-metrics %} -### Sobre diagnósticos de extração de código-fonte de {% data variables.product.prodname_codeql %} +### About {% data variables.product.prodname_codeql %} source code extraction diagnostics {% data reusables.code-scanning.extractor-diagnostics %} {% ifversion codeql-action-debug-logging %} -Você pode ver informações detalhadas sobre os erros e avisos do extrator do {% data variables.product.prodname_codeql %} que ocorreram durante a criação do banco de dados habilitando o registro em log de depuração. Para obter mais informações, confira "[Solucionar problemas do fluxo de trabalho do CodeQL](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow#creating-codeql-debugging-artifacts-by-re-running-jobs-with-debug-logging-enabled)." +You can see more detailed information about {% data variables.product.prodname_codeql %} extractor errors and warnings that occurred during database creation by enabling debug logging. For more information, see "[Troubleshooting the CodeQL workflow](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow#creating-codeql-debugging-artifacts-by-re-running-jobs-with-debug-logging-enabled)." {% endif %} -## Visualizar a saída do registro de {% data variables.product.prodname_code_scanning %} +## Viewing the logging output from {% data variables.product.prodname_code_scanning %} -Esta seção aplica-se à execução de {% data variables.product.prodname_code_scanning %} usando {% data variables.product.prodname_actions %} ({% data variables.product.prodname_codeql %} ou terceiros). +This section applies to {% data variables.product.prodname_code_scanning %} run using {% data variables.product.prodname_actions %} ({% data variables.product.prodname_codeql %} or third-party). -Depois de configurar o {% data variables.product.prodname_code_scanning %} para o seu repositório, você poderá inspecionar a saída das ações conforme forem executadas. +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. + 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. - ![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) + ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/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. Click the entry for the {% data variables.product.prodname_code_scanning %} workflow. -2. Clique no nome do trabalho à esquerda. Por exemplo, **Analisar (LANGUAGE)** . +2. Click the job name on the left. For example, **Analyze (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) + ![Log output from the {% data variables.product.prodname_code_scanning %} workflow](/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. Review the logging output from the actions in this workflow as they run. -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, confira "[Como gerenciar alertas da {% data variables.product.prodname_code_scanning %} do seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)". +1. Once all jobs are complete, you can view the details of any {% data variables.product.prodname_code_scanning %} alerts that were identified. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." {% note %} -**Observação:** se você gerou uma solicitação de pull para adicionar o fluxo de trabalho da {% data variables.product.prodname_code_scanning %} ao repositório, os alertas da solicitação de pull só são exibidos diretamente na página da {% data variables.product.prodname_code_scanning_capc %} quando a solicitação de pull é mesclada. Se algum alerta for encontrado, você poderá vê-los antes da mesclagem da solicitação de pull clicando no link **_n_ alertas encontrados** no banner da página da {% data variables.product.prodname_code_scanning_capc %}. +**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. -![Clique no link "n alertas encontrados"](/assets/images/help/repository/code-scanning-alerts-found-link.png) +![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) {% endnote %} diff --git a/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md index 2863d3fd47..12b421a65d 100644 --- a/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -1,7 +1,7 @@ --- -title: Suporte SARIF para a varredura de código +title: SARIF support for code scanning shortTitle: SARIF support -intro: 'Para exibir resultados de uma ferramenta de análise estática de terceiros em seu repositório em {% data variables.product.prodname_dotcom %}, você precisará de seus resultados armazenados em um arquivo SARIF que dê suporte a um subconjunto específico do esquema JSON SARIF 2.1.0 para dados {% data variables.product.prodname_code_scanning %}. Se você usar o mecanismo de análise estática padrão do {% data variables.product.prodname_codeql %}, os resultados aparecerão automaticamente no seu repositório no {% data variables.product.prodname_dotcom %}.' +intro: 'To display results from a third-party static analysis tool in your repository on {% data variables.product.prodname_dotcom %}, you''ll need your results stored in a SARIF file that supports a specific subset of the SARIF 2.1.0 JSON schema for {% data variables.product.prodname_code_scanning %}. If you use the default {% data variables.product.prodname_codeql %} static analysis engine, then your results will display in your repository on {% data variables.product.prodname_dotcom %} automatically.' product: '{% data reusables.gated-features.code-scanning %}' miniTocMaxHeadingLevel: 3 redirect_from: @@ -20,74 +20,70 @@ topics: - Code scanning - Integration - SARIF -ms.openlocfilehash: 96af3047cee774ce2ed865f127a21d33614ad2d9 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147785399' --- + + {% data reusables.code-scanning.beta %} -## Sobre o suporte SARIF +## About SARIF support -O SARIF (Static Analysis Results Interchange Format) é um [Padrão do OASIS](https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html) que define um formato de arquivo de saída. O padrão SARIF é usado para simplificar como as ferramentas de análise estáticas compartilham seus resultados. O {% data variables.product.prodname_code_scanning_capc %} é compatível com um subconjunto do esquema SARIF 2.1.0 JSON. +SARIF (Static Analysis Results Interchange Format) is an [OASIS Standard](https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html) that defines an output file format. The SARIF standard is used to streamline how static analysis tools share their results. {% data variables.product.prodname_code_scanning_capc %} supports a subset of the SARIF 2.1.0 JSON schema. -Para fazer o upload de um arquivo SARIF a partir de um mecanismo de análise de código estático de terceiros, você deverá garantir que os arquivos carregados usem a versão SARIF 2.1.0. {% data variables.product.prodname_dotcom %} analisará o arquivo SARIF e mostrará alertas utilizando os resultados no seu repositório como parte da experiência de {% data variables.product.prodname_code_scanning %}. Para obter mais informações, confira "[Como carregar um arquivo SARIF no {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github)". Para obter mais informações sobre o esquema JSON SARIF 2.1.0, confira [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/CommitteeSpecifications/2.1.0/sarif-schema-2.1.0.json). +To upload a SARIF file from a third-party static code analysis engine, you'll need to ensure that uploaded files use the SARIF 2.1.0 version. {% data variables.product.prodname_dotcom %} will parse the SARIF file and show alerts using the results in your repository as a part of the {% data variables.product.prodname_code_scanning %} experience. For more information, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github)." For more information about the SARIF 2.1.0 JSON schema, see [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/CommitteeSpecifications/2.1.0/sarif-schema-2.1.0.json). -Se você estiver usando {% data variables.product.prodname_actions %} com {% data variables.product.prodname_codeql_workflow %}{% ifversion codeql-runner-supported %}, usando o {% data variables.product.prodname_codeql_runner %},{% endif %}ou usando o {% data variables.product.prodname_codeql_cli %}, os resultados de {% data variables.product.prodname_code_scanning %} irão usar automaticamente o subconjunto do SARIF 2.1.0. Para obter mais informações, confira "[Como configurar a {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)"{% ifversion codeql-runner-supported %}, "[Como executar o {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)" {% endif %} ou "[Como instalar a CLI do CodeQL no seu sistema de CI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)". +If you're using {% data variables.product.prodname_actions %} with the {% data variables.product.prodname_codeql_workflow %}{% ifversion codeql-runner-supported %}, using the {% data variables.product.prodname_codeql_runner %},{% endif %} or using the {% data variables.product.prodname_codeql_cli %}, then the {% data variables.product.prodname_code_scanning %} results will automatically use the supported subset of SARIF 2.1.0. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)"{% ifversion codeql-runner-supported %}, "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)",{% endif %} or "[Installing CodeQL CLI in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)." -Você pode fazer o upload de vários arquivos SARIF para o mesmo commit e exibir os dados de cada arquivo como resultado de {% data variables.product.prodname_code_scanning %}. Ao fazer o upload de vários arquivos SARIF para um commit, você deverá indicar uma "categoria" para cada análise. A forma de especificar uma categoria varia de acordo com o método de análise: -- Usando a {% data variables.product.prodname_codeql_cli %} diretamente, transmita o argumento `--sarif-category` para o comando `codeql database analyze` ao gerar arquivos SARIF. Para obter mais informações, confira "[Como configurar a CLI do CodeQL no seu sistema de CI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#about-generating-code-scanning-results-with-codeql-cli)". -- Usando o {% data variables.product.prodname_actions %} com `codeql-action/analyze`, a categoria será definida automaticamente com base no nome do fluxo de trabalho e em qualquer variável de matriz (geralmente, `language`). Substitua isso especificando uma entrada `category` para a ação, que é útil quando você analisa diferentes seções de um monorrepositório em um fluxo de trabalho individual. -- Usando o {% data variables.product.prodname_actions %} para carregar os resultados de outras ferramentas de análise estática, você precisará especificar uma entrada `category` se carregar mais de um arquivo de resultados para a mesma ferramenta em um fluxo de trabalho. Para obter mais informações, confira "[Como carregar uma análise da {% data variables.product.prodname_code_scanning %} com o {% data variables.product.prodname_actions %}](/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions).". -- Se não estiver usando nenhuma dessas abordagens, especifique uma `runAutomationDetails.id` exclusiva em cada arquivo SARIF para upload. Para obter mais informações sobre os valores dessa propriedade, confira o [objeto `runAutomationDetails`](#runautomationdetails-object) abaixo. +You can upload multiple SARIF files for the same commit, and display the data from each file as {% data variables.product.prodname_code_scanning %} results. When you upload multiple SARIF files for a commit, you must indicate a "category" for each analysis. The way to specify a category varies according to the analysis method: +- Using the {% data variables.product.prodname_codeql_cli %} directly, pass the `--sarif-category` argument to the `codeql database analyze` command when you generate SARIF files. For more information, see "[Configuring CodeQL CLI in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#about-generating-code-scanning-results-with-codeql-cli)." +- Using {% data variables.product.prodname_actions %} with `codeql-action/analyze`, the category is set automatically from the workflow name and any matrix variables (typically, `language`). You can override this by specifying a `category` input for the action, which is useful when you analyze different sections of a mono-repository in a single workflow. +- Using {% data variables.product.prodname_actions %} to upload results from other static analysis tools, then you must specify a `category` input if you upload more than one file of results for the same tool in one workflow. For more information, see "[Uploading a {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_actions %}](/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)." +- If you are not using either of these approaches, you must specify a unique `runAutomationDetails.id` in each SARIF file to upload. For more information about this property, see [`runAutomationDetails` object](#runautomationdetails-object) below. -Se você fizer o upload de um segundo arquivo SARIF para um commit com a mesma categoria e a partir da mesma ferramenta, os resultados anteriores serão substituídos. No entanto, se você tentar fazer o upload de vários arquivos SARIF para a mesma ferramenta e categoria em um único fluxo de trabalho de {% data variables.product.prodname_actions %}, a configuração incorreta será detectada e a execução falhará. +If you upload a second SARIF file for a commit with the same category and from the same tool, the earlier results are overwritten. However, if you try to upload multiple SARIF files for the same tool and category in a single {% data variables.product.prodname_actions %} workflow run, the misconfiguration is detected and the run will fail. -{% data variables.product.prodname_dotcom %} usa propriedades no arquivo SARIF para exibir alertas. Por exemplo, a `shortDescription` e a `fullDescription` são exibidas na parte superior de um alerta da {% data variables.product.prodname_code_scanning %}. O `location` permite que o {% data variables.product.prodname_dotcom %} mostre as anotações no seu arquivo de código. Para obter mais informações, confira "[Como gerenciar alertas da {% data variables.product.prodname_code_scanning %} do seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)". +{% data variables.product.prodname_dotcom %} uses properties in the SARIF file to display alerts. For example, the `shortDescription` and `fullDescription` appear at the top of a {% data variables.product.prodname_code_scanning %} alert. The `location` allows {% data variables.product.prodname_dotcom %} to show annotations in your code file. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)." -Se estiver familiarizado com o SARIF e quiser saber mais, confira o repositório [`SARIF tutorials`](https://github.com/microsoft/sarif-tutorials) da Microsoft. +If you're new to SARIF and want to learn more, see Microsoft's [`SARIF tutorials`](https://github.com/microsoft/sarif-tutorials) repository. -## Como fornecer dados para acompanhar os alertas {% data variables.product.prodname_code_scanning %} em todas as execuções +## Providing data to track {% data variables.product.prodname_code_scanning %} alerts across runs -Cada vez que os resultados de uma nova verificação de código são carregados, os resultados são processados e os alertas são adicionados ao repositório. Para evitar alertas duplicados para o mesmo problema, {% data variables.product.prodname_code_scanning %} usa impressões digitais para corresponder aos resultados em várias execuções, para que apareçam apenas uma vez na última execução do ramo selecionado. Isto torna possível combinar alertas com a linha de código correta quando os arquivos são editados. O `ruleID` de um resultado deve ser o mesmo em toda a análise. +Each time the results of a new code scan are uploaded, the results are processed and alerts are added to the repository. To prevent duplicate alerts for the same problem, {% data variables.product.prodname_code_scanning %} uses fingerprints to match results across various runs so they only appear once in the latest run for the selected branch. This makes it possible to match alerts to the correct line of code when files are edited. The `ruleID` for a result has to be the same across analysis. -### Como relatar caminhos de arquivo consistentes +### Reporting consistent filepaths -O caminho do arquivo precisa ser consistente entre as execuções para habilitar a computação de uma impressão digital estável. Se os caminhos de arquivo forem diferentes para o mesmo resultado, sempre que houver uma nova análise, um novo alerta será criado e o antigo será fechado. Isso causará vários alertas para o mesmo resultado. +The filepath has to be consistent across the runs to enable a computation of a stable fingerprint. If the filepaths differ for the same result, each time there is a new analysis a new alert will be created, and the old one will be closed. This will cause having multiple alerts for the same result. -### Como incluir dados para geração de impressão digital +### Including data for fingerprint generation -O {% data variables.product.prodname_dotcom %} usa a propriedade `partialFingerprints` no padrão OASIS para detectar quando dois resultados são logicamente idênticos. Para obter mais informações, confira a entrada "[propriedade partialFingerprints](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" na documentação do OASIS. +{% data variables.product.prodname_dotcom %} uses the `partialFingerprints` property in the OASIS standard to detect when two results are logically identical. For more information, see the "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" entry in the OASIS documentation. -Os arquivos SARIF criados pelo {% data variables.product.prodname_codeql_workflow %}, {% ifversion codeql-runner-supported %} que usam o {% data variables.product.prodname_codeql_runner %}, {% endif %}ou que usam {% data variables.product.prodname_codeql_cli %} incluem dados de impressão digital. Se você carregar um arquivo SARIF usando a ação `upload-sarif` e esses dados estiverem ausentes, o {% data variables.product.prodname_dotcom %} tentará preencher o campo `partialFingerprints` usando os arquivos de origem. Para obter mais informações sobre como carregar resultados, confira "[Como carregar um arquivo SARIF no {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)". +SARIF files created by the {% data variables.product.prodname_codeql_workflow %}, {% ifversion codeql-runner-supported %}using the {% data variables.product.prodname_codeql_runner %}, {% endif %}or using the {% data variables.product.prodname_codeql_cli %} include fingerprint data. If you upload a SARIF file using the `upload-sarif` action and this data is missing, {% data variables.product.prodname_dotcom %} attempts to populate the `partialFingerprints` field from the source files. For more information about uploading results, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)." -Se você carregar um arquivo SARIF sem dados de impressão digital usando o ponto de extremidade de API `/code-scanning/sarifs`, os alertas da {% data variables.product.prodname_code_scanning %} serão processados e exibidos, mas os usuários poderão ver alertas duplicados. Para evitar ver alertas duplicados, calcule dados de impressão digital e preencha a propriedade `partialFingerprints` antes de carregar o arquivo SARIF. Você pode achar o script usado pela ação `upload-sarif` um ponto de partida útil: https://github.com/github/codeql-action/blob/main/src/fingerprints.ts. Para obter mais informações sobre a API, confira "[Carregar uma análise como dados SARIF](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)". +If you upload a SARIF file without fingerprint data using the `/code-scanning/sarifs` API endpoint, the {% data variables.product.prodname_code_scanning %} alerts will be processed and displayed, but users may see duplicate alerts. To avoid seeing duplicate alerts, you should calculate fingerprint data and populate the `partialFingerprints` property before you upload the SARIF file. You may find the script that the `upload-sarif` action uses a helpful starting point: https://github.com/github/codeql-action/blob/main/src/fingerprints.ts. For more information about the API, see "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)." -## Noções básicas sobre regras e resultados +## Understanding rules and results -Os arquivos SARIF dão suporte a regras e resultados. As informações armazenadas nesses elementos são semelhantes, mas têm propósitos diferentes. +SARIF files support both rules and results. The information stored in these elements is similar but serves different purposes. -- As regras são uma matriz de objetos `reportingDescriptor` que estão incluídos no objeto `toolComponent`. Nele, são armazenados detalhes das regras que são executadas durante a análise. As informações nesses objetos devem ser alteradas com pouca frequência, geralmente quando você atualiza a ferramenta. +- Rules are an array of `reportingDescriptor` objects that are included in the `toolComponent` object. This is where you store details of the rules that are run during analysis. Information in these objects should change infrequently, typically when you update the tool. -- Os resultados são armazenados como uma série de objetos `result` sob `results` no objeto `run`. Cada objeto `result` contém detalhes de um alerta na base de código. Dentro do objeto `results`, você pode fazer referência à regra que detectou o alerta. +- Results are stored as a series of `result` objects under `results` in the `run` object. Each `result` object contains details for one alert in the codebase. Within the `results` object, you can reference the rule that detected the alert. -Ao comparar arquivos SARIF gerados pela análise de diferentes bases de código com a mesma ferramenta e regras, verá diferenças nos resultados das análises, mas não nas regras. +When you compare SARIF files generated by analyzing different codebases with the same tool and rules, you should see differences in the results of the analyses but not in the rules. -## Como especificar a raiz para arquivos de origem +## Specifying the root for source files -{% data variables.product.prodname_code_scanning_capc %} interpreta os resultados relatados com os caminhos relativos baseados na raiz do repositório analisado. Se um resultado contiver um URI absoluto, ele será convertido em um URI relativo. Em seguida, o URI relativo pode ser correspondido com um arquivo confirmado no repositório. +{% data variables.product.prodname_code_scanning_capc %} interprets results that are reported with relative paths as relative to the root of the repository analyzed. If a result contains an absolute URI, the URI is converted to a relative URI. The relative URI can then be matched against a file committed to the repository. -Você pode fornecer a raiz de origem para conversão de URIs absolutos em relativos de uma das maneiras a seguir. +You can provide the source root for conversion from absolute to relative URIs in one of the following ways. -- Entrada [`checkout_path`](https://github.com/github/codeql-action/blob/c2c0a2908e95769d01b907f9930050ecb5cf050d/analyze/action.yml#L44-L47) para a ação `github/codeql-action/analyze` -- Parâmetro `checkout_uri` para o ponto de extremidade da API de upload de SARIF. Para obter mais informações, confira "[{% data variables.product.prodname_code_scanning_capc %}](/rest/code-scanning#upload-an-analysis-as-sarif-data)" na documentação da API REST -- Propriedade [`invocation.workingDirectory.uri`](https://docs.oasis-open.org/sarif/sarif/v2.1.0/csprd01/sarif-v2.1.0-csprd01.html#_Toc9244365) no arquivo SARIF +- [`checkout_path`](https://github.com/github/codeql-action/blob/c2c0a2908e95769d01b907f9930050ecb5cf050d/analyze/action.yml#L44-L47) input to the `github/codeql-action/analyze` action +- `checkout_uri` parameter to the SARIF upload API endpoint. For more information, see "[{% data variables.product.prodname_code_scanning_capc %}](/rest/code-scanning#upload-an-analysis-as-sarif-data)" in the REST API documentation +- [`invocation.workingDirectory.uri`](https://docs.oasis-open.org/sarif/sarif/v2.1.0/csprd01/sarif-v2.1.0-csprd01.html#_Toc9244365) property in the SARIF file -Se você fornecer uma raiz de origem, qualquer local de um artefato especificado usando um URI absoluto deverá usar o mesmo esquema de URI. Se houver uma incompatibilidade entre o esquema de URI para a raiz de origem e um ou mais URIs absolutos, o upload será rejeitado. +If you provide a source root, any location of an artifact specified using an absolute URI must use the same URI scheme. If there is a mismatch between the URI scheme for the source root and one or more of the absolute URIs, the upload is rejected. -Por exemplo, um arquivo SARIF é carregado usando uma raiz de origem de `file:///github/workspace`. +For example, a SARIF file is uploaded using a source root of `file:///github/workspace`. ``` # Conversion of absolute URIs to relative URIs for location artifacts @@ -96,155 +92,155 @@ file:///github/workspace/src/main.go -> src/main.go file:///tmp/go-build/tmp.go -> file:///tmp/go-build/tmp.go ``` -O arquivo é carregado com êxito, pois ambos os URIs absolutos usam o mesmo esquema de URI que a raiz de origem. +The file is successfully uploaded as both absolute URIs use the same URI scheme as the source root. -## Validar seu arquivo SARIF +## Validating your SARIF file -Você pode marcar um arquivo SARIF compatível com {% data variables.product.prodname_code_scanning %} testando-o com as regras de ingestão de {% data variables.product.prodname_dotcom %}. Para obter mais informações, acesse o [validador de SARIF da Microsoft](https://sarifweb.azurewebsites.net/). +You can check a SARIF file is compatible with {% data variables.product.prodname_code_scanning %} by testing it against the {% data variables.product.prodname_dotcom %} ingestion rules. For more information, visit the [Microsoft SARIF validator](https://sarifweb.azurewebsites.net/). {% data reusables.code-scanning.upload-sarif-alert-limit %} -## Propriedades compatíveis do arquivo de saída SARIF +## Supported SARIF output file properties -Se você usar um mecanismo de análise de código diferente de {% data variables.product.prodname_codeql %}, você poderá revisar as propriedades do SARIF compatíveis para otimizar como seus resultados de análise aparecerão em {% data variables.product.prodname_dotcom %}. +If you use a code analysis engine other than {% data variables.product.prodname_codeql %}, you can review the supported SARIF properties to optimize how your analysis results will appear on {% data variables.product.prodname_dotcom %}. {% note %} -**Observação:** você deve fornecer um valor explícito para qualquer propriedade marcada como "obrigatória". Não há suporte para cadeias de caracteres vazias em propriedades obrigatórias. +**Note:** You must supply an explicit value for any property marked as "required". The empty string is not supported for required properties. {% endnote %} -É possível fazer o upload de qualquer arquivo de saída SARIF 2.1.0 válido, no entanto, {% data variables.product.prodname_code_scanning %} usará apenas as seguintes propriedades compatíveis. +Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.product.prodname_code_scanning %} will only use the following supported properties. -### Objeto `sarifLog` +### `sarifLog` object -| Nome | Descrição | +| Name | Description | |----|----| -| `$schema` | **Necessário.** O URI do esquema SARIF JSON para a versão 2.1.0. Por exemplo, `https://json.schemastore.org/sarif-2.1.0.json`. | -| `version` | **Necessário.** A {% data variables.product.prodname_code_scanning_capc %} só dá suporte à versão SARIF `2.1.0`. -| `runs[]` | **Necessário.** Um arquivo SARIF contém uma matriz de uma ou mais execuções. Cada execução representa uma execução única de uma ferramenta de análise. Para obter mais informações sobre uma `run`, confira o [objeto `run`](#run-object). +| `$schema` | **Required.** The URI of the SARIF JSON schema for version 2.1.0. For example, `https://json.schemastore.org/sarif-2.1.0.json`. | +| `version` | **Required.** {% data variables.product.prodname_code_scanning_capc %} only supports SARIF version `2.1.0`. +| `runs[]` | **Required.** A SARIF file contains an array of one or more runs. Each run represents a single run of an analysis tool. For more information about a `run`, see the [`run` object](#run-object). -### Objeto `run` +### `run` object -A {% data variables.product.prodname_code_scanning_capc %} usa o objeto `run` para filtrar os resultados por ferramenta e fornecer informações sobre a fonte de um resultado. O objeto `run` contém o objeto `tool.driver` de componentes da ferramenta, que contém informações sobre a ferramenta que gerou os resultados. Cada `run` pode ter resultados apenas para uma ferramenta de análise. +{% data variables.product.prodname_code_scanning_capc %} uses the `run` object to filter results by tool and provide information about the source of a result. The `run` object contains the `tool.driver` tool component object, which contains information about the tool that generated the results. Each `run` can only have results for one analysis tool. -| Nome | Descrição | +| Name | Description | |----|----| -| `tool.driver` | **Necessário.** Um objeto `toolComponent` que descreve a ferramenta de análise. Para obter mais informações, confira o [objeto `toolComponent`](#toolcomponent-object). | -| `tool.extensions[]` | **Opcional.** Uma matriz de objetos `toolComponent` que representam plug-ins ou extensões usadas pela ferramenta durante a análise. Para obter mais informações, confira o [objeto `toolComponent`](#toolcomponent-object). | -| `invocation.workingDirectory.uri` | **Opcional.** Esse campo é usado somente quando `checkout_uri` (somente API de upload de SARIF) ou `checkout_path` (somente % data variables.product.prodname_actions %}) não são fornecidos. O valor é usado para converter URIs absolutos usados em [objetos `physicalLocation`](#physicallocation-object) em URIs relativos. Para obter mais informações, confira "[Como especificar a raiz para arquivos de origem](#specifying-the-root-for-source-files)".| -| `results[]` | **Necessário.** Os resultados da ferramenta de análise. {% data variables.product.prodname_code_scanning_capc %} exibe os resultados em {% data variables.product.prodname_dotcom %}. Para obter mais informações, confira o [objeto `result`](#result-object). +| `tool.driver` | **Required.** A `toolComponent` object that describes the analysis tool. For more information, see the [`toolComponent` object](#toolcomponent-object). | +| `tool.extensions[]` | **Optional.** An array of `toolComponent` objects that represent any plugins or extensions used by the tool during analysis. For more information, see the [`toolComponent` object](#toolcomponent-object). | +| `invocation.workingDirectory.uri` | **Optional.** This field is used only when `checkout_uri` (SARIF upload API only) or `checkout_path` ({% data variables.product.prodname_actions %} only) are not provided. The value is used to convert absolute URIs used in [`physicalLocation` objects](#physicallocation-object) to relative URIs. For more information, see "[Specifying the root for source files](#specifying-the-root-for-source-files)."| +| `results[]` | **Required.** The results of the analysis tool. {% data variables.product.prodname_code_scanning_capc %} displays the results on {% data variables.product.prodname_dotcom %}. For more information, see the [`result` object](#result-object). -### Objeto `toolComponent` +### `toolComponent` object -| Nome | Descrição | +| Name | Description | |----|----| -| `name` | **Necessário.** O nome da ferramenta de análise. {% data variables.product.prodname_code_scanning_capc %} exibe o nome em {% data variables.product.prodname_dotcom %} para permitir que você filtre resultados por ferramenta. | -| `version` | **Opcional.** A versão da ferramenta de análise. O {% data variables.product.prodname_code_scanning_capc %} usa o número da versão para fazer o monitoramento quando os resultados podem ter mudado devido a uma mudança na versão da ferramenta em vez de uma mudança no código que está sendo analisado. Se o arquivo SARIF incluir o campo `semanticVersion`, `version` não será usado pela {% data variables.product.prodname_code_scanning %}. | -| `semanticVersion` | **Opcional.** A versão da ferramenta de análise, especificada pelo formato Versionamento Semântico 2.0. O {% data variables.product.prodname_code_scanning_capc %} usa o número da versão para fazer o monitoramento quando os resultados podem ter mudado devido a uma mudança na versão da ferramenta em vez de uma mudança no código que está sendo analisado. Se o arquivo SARIF incluir o campo `semanticVersion`, `version` não será usado pela {% data variables.product.prodname_code_scanning %}. Para obter mais informações, confira "[Versionamento Semântico 2.0.0](https://semver.org/)" na documentação do Versionamento Semântico. | -| `rules[]` | **Necessário.** A matriz de objetos `reportingDescriptor` que representa as regras. A ferramenta de análise usa regras para encontrar problemas no código que está sendo analisado. Para obter mais informações, confira o [objeto `reportingDescriptor`](#reportingdescriptor-object). | +| `name` | **Required.** The name of the analysis tool. {% data variables.product.prodname_code_scanning_capc %} displays the name on {% data variables.product.prodname_dotcom %} to allow you to filter results by tool. | +| `version` | **Optional.** The version of the analysis tool. {% data variables.product.prodname_code_scanning_capc %} uses the version number to track when results may have changed due to a tool version change rather than a change in the code being analyzed. If the SARIF file includes the `semanticVersion` field, `version` is not used by {% data variables.product.prodname_code_scanning %}. | +| `semanticVersion` | **Optional.** The version of the analysis tool, specified by the Semantic Versioning 2.0 format. {% data variables.product.prodname_code_scanning_capc %} uses the version number to track when results may have changed due to a tool version change rather than a change in the code being analyzed. If the SARIF file includes the `semanticVersion` field, `version` is not used by {% data variables.product.prodname_code_scanning %}. For more information, see "[Semantic Versioning 2.0.0](https://semver.org/)" in the Semantic Versioning documentation. | +| `rules[]` | **Required.** An array of `reportingDescriptor` objects that represent rules. The analysis tool uses rules to find problems in the code being analyzed. For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). | -### Objeto `reportingDescriptor` +### `reportingDescriptor` object -Nele, são armazenados detalhes das regras que são executadas durante a análise. As informações nesses objetos devem ser alteradas com pouca frequência, geralmente quando você atualiza a ferramenta. Para obter mais informações, consulte "[Noções básicas sobre regras e resultados](#understanding-rules-and-results)" acima. +This is where you store details of the rules that are run during analysis. Information in these objects should change infrequently, typically when you update the tool. For more information, see "[Understanding rules and results](#understanding-rules-and-results)" above. -| Nome | Descrição | +| Name | Description | |----|----| -| `id` | **Necessário.** Um identificador exclusivo para a regra. A `id` é referenciada com base em outras partes do arquivo SARIF e pode ser usada pela {% data variables.product.prodname_code_scanning %} para exibir URLs no {% data variables.product.prodname_dotcom %}. | -| `name` | **Opcional.** O nome da regra. {% data variables.product.prodname_code_scanning_capc %} exibe o nome para permitir que os resultados sejam filtrados pela regra em {% data variables.product.prodname_dotcom %}. | -| `shortDescription.text` | **Necessário.** Uma descrição concisa da regra. {% data variables.product.prodname_code_scanning_capc %} exibe a breve descrição em {% data variables.product.prodname_dotcom %} ao lado dos resultados associados. -| `fullDescription.text` | **Necessário.** Descrição da regra. {% data variables.product.prodname_code_scanning_capc %} exibe a descrição completa em {% data variables.product.prodname_dotcom %} ao lado dos resultados associados. O número máximo de caracteres é 1000. -| `defaultConfiguration.level` | **Opcional.** Nível de gravidade padrão da regra. {% data variables.product.prodname_code_scanning_capc %} usa níveis de gravidade para ajudar você a entender quão crítico é o resultado para uma determinada regra. Esse valor pode ser substituído pelo atributo `level` no objeto `result`. Para obter mais informações, confira o [objeto `result`](#result-object). Padrão: `warning`. -| `help.text` | **Necessário.** Documentação da regra usando o formato de texto. O {% data variables.product.prodname_code_scanning_capc %} exibe essa documentação de ajuda ao lado dos resultados associados. -| `help.markdown` | **Recomendado.** Documentação da regra usando o formato Markdown. O {% data variables.product.prodname_code_scanning_capc %} exibe essa documentação de ajuda ao lado dos resultados associados. Quando `help.markdown` está disponível, ele é exibido em vez de `help.text`. -| `properties.tags[]` | **Opcional.** Uma matriz de cadeias de caracteres. A {% data variables.product.prodname_code_scanning_capc %} usa `tags` para permitir que você filtre os resultados no {% data variables.product.prodname_dotcom %}. Por exemplo, é possível filtrar todos os resultados que têm a marca `security`. -| `properties.precision` | **Recomendado.** Uma cadeia de caracteres que indica a frequência com que os resultados indicados por essa regra são verdadeiros. Por exemplo, se uma regra tem uma alta taxa conhecida de falsos-positivos, a precisão deve ser `low`. O {% data variables.product.prodname_code_scanning_capc %} ordena os resultados por precisão no {% data variables.product.prodname_dotcom %}, de modo que os resultados com o `level` mais alto e a `precision` mais alta sejam mostrados primeiro. Pode ser `very-high`, `high`, `medium` ou `low`. -| `properties.problem.severity` | **Recomendado.** Uma cadeia de caracteres que indica o nível de gravidade de todos os alertas gerados por uma consulta que não é de segurança. Isso, com a propriedade `properties.precision`, determina se os resultados são exibidos por padrão no {% data variables.product.prodname_dotcom %}, de modo que os resultados com a `problem.severity` mais alta e a `precision` mais alta sejam mostrados primeiro. Pode ser `error`, `warning` ou `recommendation`. -| `properties.security-severity` | **Recomendado.** Uma cadeia de caracteres que representa uma pontuação que indica o nível de gravidade, entre 0,0 e 10,0, de consultas de segurança (`@tags` inclui `security`). Isso, com a propriedade `properties.precision`, determina se os resultados são exibidos por padrão no {% data variables.product.prodname_dotcom %}, de modo que os resultados com a `security-severity` mais alta e a `precision` mais alta sejam mostrados primeiro. A {% data variables.product.prodname_code_scanning_capc %} converte as pontuações numéricas da seguinte maneira: uma pontuação acima de 9,0 é `critical`, de 7,0 a 8,9 é `high`, de 4,0 a 6,9 é `medium` e 3,9 ou menos é `low`. +| `id` | **Required.** A unique identifier for the rule. The `id` is referenced from other parts of the SARIF file and may be used by {% data variables.product.prodname_code_scanning %} to display URLs on {% data variables.product.prodname_dotcom %}. | +| `name` | **Optional.** The name of the rule. {% data variables.product.prodname_code_scanning_capc %} displays the name to allow results to be filtered by rule on {% data variables.product.prodname_dotcom %}. | +| `shortDescription.text` | **Required.** A concise description of the rule. {% data variables.product.prodname_code_scanning_capc %} displays the short description on {% data variables.product.prodname_dotcom %} next to the associated results. +| `fullDescription.text` | **Required.** A description of the rule. {% data variables.product.prodname_code_scanning_capc %} displays the full description on {% data variables.product.prodname_dotcom %} next to the associated results. The max number of characters is limited to 1000. +| `defaultConfiguration.level` | **Optional.** Default severity level of the rule. {% data variables.product.prodname_code_scanning_capc %} uses severity levels to help you understand how critical the result is for a given rule. This value can be overridden by the `level` attribute in the `result` object. For more information, see the [`result` object](#result-object). Default: `warning`. +| `help.text` | **Required.** Documentation for the rule using text format. {% data variables.product.prodname_code_scanning_capc %} displays this help documentation next to the associated results. +| `help.markdown` | **Recommended.** Documentation for the rule using Markdown format. {% data variables.product.prodname_code_scanning_capc %} displays this help documentation next to the associated results. When `help.markdown` is available, it is displayed instead of `help.text`. +| `properties.tags[]` | **Optional.** An array of strings. {% data variables.product.prodname_code_scanning_capc %} uses `tags` to allow you to filter results on {% data variables.product.prodname_dotcom %}. For example, it is possible to filter to all results that have the tag `security`. +| `properties.precision` | **Recommended.** A string that indicates how often the results indicated by this rule are true. For example, if a rule has a known high false-positive rate, the precision should be `low`. {% data variables.product.prodname_code_scanning_capc %} orders results by precision on {% data variables.product.prodname_dotcom %} so that the results with the highest `level`, and highest `precision` are shown first. Can be one of: `very-high`, `high`, `medium`, or `low`. +| `properties.problem.severity` | **Recommended.** A string that indicates the level of severity of any alerts generated by a non-security query. This, with the `properties.precision` property, determines whether the results are displayed by default on {% data variables.product.prodname_dotcom %} so that the results with the highest `problem.severity`, and highest `precision` are shown first. Can be one of: `error`, `warning`, or `recommendation`. +| `properties.security-severity` | **Recommended.** A string representing a score that indicates the level of severity, between 0.0 and 10.0, for security queries (`@tags` includes `security`). This, with the `properties.precision` property, determines whether the results are displayed by default on {% data variables.product.prodname_dotcom %} so that the results with the highest `security-severity`, and highest `precision` are shown first. {% data variables.product.prodname_code_scanning_capc %} translates numerical scores as follows: over 9.0 is `critical`, 7.0 to 8.9 is `high`, 4.0 to 6.9 is `medium` and 3.9 or less is `low`. -### Objeto `result` +### `result` object -Cada objeto `result` contém detalhes de um alerta na base de código. Dentro do objeto `results`, você pode fazer referência à regra que detectou o alerta. Para obter mais informações, consulte "[Noções básicas sobre regras e resultados](#understanding-rules-and-results)" acima. +Each `result` object contains details for one alert in the codebase. Within the `results` object, you can reference the rule that detected the alert. For more information, see "[Understanding rules and results](#understanding-rules-and-results)" above. {% data reusables.code-scanning.upload-sarif-alert-limit %} -| Nome | Descrição | +| Name | Description | |----|----| -| `ruleId`| **Opcional.** O identificador exclusivo da regra (`reportingDescriptor.id`). Para obter mais informações, confira o [objeto `reportingDescriptor`](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} usa o identificador da regra para filtrar os resultados por regra em {% data variables.product.prodname_dotcom %}. -| `ruleIndex`| **Opcional.** O índice da regra associada (objeto `reportingDescriptor`) na matriz `rules` de componentes da ferramenta. Para obter mais informações, confira o [objeto `run`](#run-object). O intervalo permitido para essa propriedade 0 a 2^63 - 1. -| `rule`| **Opcional.** Uma referência usada para localizar a regra (descritor de relatório) para esse resultado. Para obter mais informações, confira o [objeto `reportingDescriptor`](#reportingdescriptor-object). -| `level`| **Opcional.** A gravidade do resultado. Esse nível sobrepõe a severidade-padrão definida pela regra. {% data variables.product.prodname_code_scanning_capc %} usa o nível para filtrar resultados por gravidade em {% data variables.product.prodname_dotcom %}. -| `message.text`| **Necessário.** Uma mensagem que descreve o resultado. {% data variables.product.prodname_code_scanning_capc %} exibe o texto da mensagem como o título do resultado. Apenas a primeira frase da mensagem será exibida quando o espaço visível for limitado. -| `locations[]`| **Necessário.** O conjunto de locais em que o resultado foi detectado até, no máximo, dez. Só um local deve ser incluído, a não ser que o problema só possa ser corrigido fazendo uma alteração em cada local especificado. **Observação:** Pelo menos, um local é necessário para a {% data variables.product.prodname_code_scanning %} exibir um resultado. {% data variables.product.prodname_code_scanning_capc %} usará essa propriedade para decidir qual arquivo fazer anotações com o resultado. Apenas o primeiro valor desse array é usado. Todos os outros valores são ignorados. -| `partialFingerprints`| **Necessário.** Um conjunto de cadeias de caracteres usadas para acompanhar a identidade exclusiva do resultado. A {% data variables.product.prodname_code_scanning_capc %} usa `partialFingerprints` para identificar com precisão quais resultados são iguais em todos os commits e branches. A {% data variables.product.prodname_code_scanning_capc %} tentará usar `partialFingerprints`, se houver. Se você estiver carregando arquivos SARIF de terceiros com a `upload-action`, a ação criará `partialFingerprints` para você quando eles não estiverem incluídos no arquivo SARIF. Para obter mais informações, confira "[Como fornecer dados para rastrear alertas de exame de código nas execuções](#providing-data-to-track-code-scanning-alerts-across-runs)". **Observação:** o {% data variables.product.prodname_code_scanning_capc %} só usa o `primaryLocationLineHash`. -| `codeFlows[].threadFlows[].locations[]`| **Opcional.** Uma matriz de objetos `location` 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, confira o [objeto `location`](#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, confira o [objeto `location`](#location-object). +| `ruleId`| **Optional.** The unique identifier of the rule (`reportingDescriptor.id`). For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} uses the rule identifier to filter results by rule on {% data variables.product.prodname_dotcom %}. +| `ruleIndex`| **Optional.** The index of the associated rule (`reportingDescriptor` object) in the tool component `rules` array. For more information, see the [`run` object](#run-object). The allowed range for this property 0 to 2^63 - 1. +| `rule`| **Optional.** A reference used to locate the rule (reporting descriptor) for this result. For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). +| `level`| **Optional.** The severity of the result. This level overrides the default severity defined by the rule. {% data variables.product.prodname_code_scanning_capc %} uses the level to filter results by severity on {% data variables.product.prodname_dotcom %}. +| `message.text`| **Required.** A message that describes the result. {% data variables.product.prodname_code_scanning_capc %} displays the message text as the title of the result. Only the first sentence of the message will be displayed when visible space is limited. +| `locations[]`| **Required.** The set of locations where the result was detected up to a maximum of 10. Only one location should be included unless the problem can only be corrected by making a change at every specified location. **Note:** At least one location is required for {% data variables.product.prodname_code_scanning %} to display a result. {% data variables.product.prodname_code_scanning_capc %} will use this property to decide which file to annotate with the result. Only the first value of this array is used. All other values are ignored. +| `partialFingerprints`| **Required.** A set of strings used to track the unique identity of the result. {% data variables.product.prodname_code_scanning_capc %} uses `partialFingerprints` to accurately identify which results are the same across commits and branches. {% data variables.product.prodname_code_scanning_capc %} will attempt to use `partialFingerprints` if they exist. If you are uploading third-party SARIF files with the `upload-action`, the action will create `partialFingerprints` for you when they are not included in the SARIF file. For more information, see "[Providing data to track code scanning alerts across runs](#providing-data-to-track-code-scanning-alerts-across-runs)." **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). -### Objeto `location` +### `location` object -Um local dentro de um artefato de programação, como, por exemplo, um arquivo no repositório ou um arquivo gerado durante uma criação. +A location within a programming artifact, such as a file in the repository or a file that was generated during a build. -| Nome | Descrição | +| Name | Description | |----|----| -| `location.id` | **Opcional.** Um identificador exclusivo que distingue esse local de todos os outros locais em um só objeto de resultado. O intervalo permitido para essa propriedade 0 a 2^63 - 1. -| `location.physicalLocation` | **Necessário.** Identifica o artefato e a região. Para obter mais informações, confira [`physicalLocation`](#physicallocation-object). -| `location.message.text` | **Opcional.** Uma mensagem relevante à localização. +| `location.id` | **Optional.** A unique identifier that distinguishes this location from all other locations within a single result object. The allowed range for this property 0 to 2^63 - 1. +| `location.physicalLocation` | **Required.** Identifies the artifact and region. For more information, see the [`physicalLocation`](#physicallocation-object). +| `location.message.text` | **Optional.** A message relevant to the location. -### Objeto `physicalLocation` +### `physicalLocation` object -| Nome | Descrição | +| Name | Description | |----|----| -| `artifactLocation.uri`| **Necessário.** Um URI que indica o local de um artefato, geralmente um arquivo no repositório ou gerado durante um build. Para obter os melhores resultados, recomendamos que esse seja um caminho relativo da raiz do repositório GitHub que está sendo analisado. Por exemplo, `src/main.js`. Para obter mais informações sobre URIs de artefato, confira "[Como especificar a raiz para arquivos de origem](#specifying-the-root-for-source-files)".| -| `region.startLine` | **Necessário.** O número de linha do primeiro caractere na região. -| `region.startColumn` | **Necessário.** O número da coluna do primeiro caractere na região. -| `region.endLine` | **Necessário.** O número de linha do último caractere na região. -| `region.endColumn` | **Necessário.** O número da coluna do caractere após o final da região. +| `artifactLocation.uri`| **Required.** A URI indicating the location of an artifact, usually a file either in the repository or generated during a build. For the best results we recommend that this is a relative path from the root of the GitHub repository being analyzed. For example, `src/main.js`. For more information about artifact URIs, see "[Specifying the root for source files](#specifying-the-root-for-source-files)."| +| `region.startLine` | **Required.** The line number of the first character in the region. +| `region.startColumn` | **Required.** The column number of the first character in the region. +| `region.endLine` | **Required.** The line number of the last character in the region. +| `region.endColumn` | **Required.** The column number of the character following the end of the region. -### Objeto `runAutomationDetails` +### `runAutomationDetails` object -O objeto `runAutomationDetails` contém informações que especificam a identidade de uma execução. +The `runAutomationDetails` object contains information that specifies the identity of a run. {% note %} -**Observação:** `runAutomationDetails` é um objeto SARIF v2.1.0. Se você estiver usando {% data variables.product.prodname_codeql_cli %}, você poderá especificar a versão do SARIF a ser usada. O objeto equivalente a `runAutomationDetails` é `.automationId` para o SARIF v1 e `.automationLogicalId` para o SARIF v2. +**Note:** `runAutomationDetails` is a SARIF v2.1.0 object. If you're using the {% data variables.product.prodname_codeql_cli %}, you can specify the version of SARIF to use. The equivalent object to `runAutomationDetails` is `.automationId` for SARIF v1 and `.automationLogicalId` for SARIF v2. {% endnote %} -| Nome | Descrição | +| Name | Description | |----|----| -| `id`| **Opcional.** Uma cadeia de caracteres que identifica a categoria da análise e a ID de execução. Use se você quiser fazer upload de vários arquivos SARIF para a mesma ferramenta e commit, mas executado em diferentes idiomas ou diferentes partes do código. | +| `id`| **Optional.** A string that identifies the category of the analysis and the run ID. Use if you want to upload multiple SARIF files for the same tool and commit, but performed on different languages or different parts of the code. | -O uso do objeto `runAutomationDetails` é opcional. +The use of the `runAutomationDetails` object is optional. -O campo `id` pode incluir uma categoria de análise e uma ID de execução. Não usamos a parte da ID de execução do campo `id`, mas a armazenamos. +The `id` field can include an analysis category and a run ID. We don't use the run ID part of the `id` field, but we store it. -Use a categoria para distinguir entre múltiplas análises para a mesma ferramenta ou commit, mas executada em diferentes linguagens ou partes diferentes do código. Use o ID de execução para identificar a execução específica da análise, como a data em que a análise foi executada. +Use the category to distinguish between multiple analyses for the same tool or commit, but performed on different languages or different parts of the code. Use the run ID to identify the specific run of the analysis, such as the date the analysis was run. -`id` é interpretado como `category/run-id`. Se a `id` não contiver nenhuma barra (`/`), a cadeia de caracteres inteira será a `run_id` e a `category` ficará vazia. Caso contrário, a `category` será tudo na cadeia de caracteres até a última barra, e a `run_id` será tudo após ela. +`id` is interpreted as `category/run-id`. If the `id` contains no forward slash (`/`), then the entire string is the `run_id` and the `category` is empty. Otherwise, `category` is everything in the string until the last forward slash, and `run_id` is everything after. | `id` | category | `run_id` | |----|----|----| -| my-analysis/tool1/2021-02-01 | my-analysis/tool1 | 01/02/2021 -| my-analysis/tool1/ | my-analysis/tool1 | _sem `run-id`_ -| my-analysis for tool1 | _sem categoria_ | my-analysis for tool1 +| my-analysis/tool1/2021-02-01 | my-analysis/tool1 | 2021-02-01 +| my-analysis/tool1/ | my-analysis/tool1 | _no `run-id`_ +| my-analysis for tool1 | _no category_ | my-analysis for tool1 -- A execução com uma `id` igual a "my-analysis/tool1/2021-02-01" pertence à categoria "my-analysis/tool1". Provavelmente, esta é a execução de 2 de fevereiro de 2021. -- A execução com uma `id` igual a "my-analysis/tool1/" pertence à categoria "my-analysis/tool1", mas não é distinta das outras execuções nessa categoria. -- A execução cuja `id` é "my-analysis for tool1" tem um identificador único, mas não pode ser inferida como pertencente a nenhuma categoria. +- The run with an `id` of "my-analysis/tool1/2021-02-01" belongs to the category "my-analysis/tool1". Presumably, this is the run from February 2, 2021. +- The run with an `id` of "my-analysis/tool1/" belongs to the category "my-analysis/tool1" but is not distinguished from other runs in that category. +- The run whose `id` is "my-analysis for tool1 " has a unique identifier but cannot be inferred to belong to any category. -Para obter mais informações sobre o objeto `runAutomationDetails` e o campo `id`, confira o [objeto runAutomationDetails](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012479) na documentação do OASIS. +For more information about the `runAutomationDetails` object and the `id` field, see [runAutomationDetails object](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012479) in the OASIS documentation. -Observe que o resto dos campos compatíveis são ignorados. +Note that the rest of the supported fields are ignored. -## Exemplos de arquivos de saída SARIF +## SARIF output file examples -Estes exemplos de arquivos de saída SARIF mostram as propriedades compatíveis e os valores de exemplo. +These example SARIF output files show supported properties and example values. -### Exemplo com as propriedades mínimas necessárias +### Example with minimum required properties -Este arquivo de saída SARIF tem exemplo de valores para mostrar as propriedades mínimas necessárias para que os resultados de {% data variables.product.prodname_code_scanning %} funcionem conforme esperado. Se você remover qualquer propriedade, omitir valores ou usar uma cadeia de caracteres vazia, esses dados não serão exibidos corretamente ou serão sincronizados em {% data variables.product.prodname_dotcom %}. +This SARIF output file has example values to show the minimum required properties for {% data variables.product.prodname_code_scanning %} results to work as expected. If you remove any properties, omit values, or use an empty string, this data will not be displayed correctly or sync on {% data variables.product.prodname_dotcom %}. ```json { @@ -300,9 +296,9 @@ Este arquivo de saída SARIF tem exemplo de valores para mostrar as propriedades } ``` -### Exemplo que mostra todas as propriedades compatíveis como SARIF +### Example showing all supported SARIF properties -Este arquivo de saída SARIF tem valores de exemplo para mostrar todas as propriedades do SARIF compatíveis com {% data variables.product.prodname_code_scanning %}. +This SARIF output file has example values to show all supported SARIF properties for {% data variables.product.prodname_code_scanning %}. ```json { diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md index 2f4203d676..370ce281d8 100644 --- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md +++ b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md @@ -1,7 +1,7 @@ --- title: About CodeQL code scanning in your CI system shortTitle: Code scanning in your CI -intro: 'You can analyze your code with {% data variables.product.prodname_codeql %} in a third-party continuous integration system and upload the results to {% data variables.product.product_location %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.' +intro: 'You can analyze your code with {% data variables.product.prodname_codeql %} in a third-party continuous integration system and upload the results to {% data variables.location.product_location %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.' product: '{% data reusables.gated-features.code-scanning %}' versions: fpt: '*' diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md index 36eea83bc0..1a0e74ad50 100644 --- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md +++ b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md @@ -187,7 +187,7 @@ $ codeql database analyze /codeql-dbs/example-repo \ {% data reusables.code-scanning.upload-sarif-alert-limit %} -Before you can upload results to {% data variables.product.product_name %}, you must determine the best way to pass the {% data variables.product.prodname_github_app %} or personal access token you created earlier to the {% data variables.product.prodname_codeql_cli %} (see [Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system#generating-a-token-for-authentication-with-github)). We recommend that you review your CI system's guidance on the secure use of a secret store. The {% data variables.product.prodname_codeql_cli %} supports: +Before you can upload results to {% data variables.product.product_name %}, you must determine the best way to pass the {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} you created earlier to the {% data variables.product.prodname_codeql_cli %} (see [Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system#generating-a-token-for-authentication-with-github)). We recommend that you review your CI system's guidance on the secure use of a secret store. The {% data variables.product.prodname_codeql_cli %} supports: - Passing the token to the CLI via standard input using the `--github-auth-stdin` option (recommended). - Saving the secret in the environment variable `GITHUB_TOKEN` and running the CLI without including the `--github-auth-stdin` option. @@ -207,7 +207,7 @@ When you have decided on the most secure and reliable method for your CI server, | `--commit` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the full SHA of the commit you analyzed. | `--sarif` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the SARIF file to load.{% ifversion ghes or ghae %} | `--github-url` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the URL for {% data variables.product.product_name %}.{% endif %} -| `--github-auth-stdin` | | Optional. Use to pass the CLI the {% data variables.product.prodname_github_app %} or personal access token created for authentication with {% data variables.product.company_short %}'s REST API via standard input. This is not needed if the command has access to a `GITHUB_TOKEN` environment variable set with this token. +| `--github-auth-stdin` | | Optional. Use to pass the CLI the {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} created for authentication with {% data variables.product.company_short %}'s REST API via standard input. This is not needed if the command has access to a `GITHUB_TOKEN` environment variable set with this token. For more information, see [github upload-results](https://codeql.github.com/docs/codeql-cli/manual/github-upload-results/) in the documentation for the {% data variables.product.prodname_codeql_cli %}. @@ -231,12 +231,12 @@ There is no output from this command unless the upload was unsuccessful. The com The {% data variables.product.prodname_codeql_cli %} bundle includes queries that are maintained by {% data variables.product.company_short %} experts, security researchers, and community contributors. If you want to run queries developed by other organizations, {% data variables.product.prodname_codeql %} query packs provide an efficient and reliable way to download and run queries. For more information, see "[About code scanning with CodeQL](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)." -Before you can use a {% data variables.product.prodname_codeql %} pack to analyze a database, you must download any packages you require from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}. This can be done either by using the `--download` flag as part of the `codeql database analyze` command. If a package is not publicly available, you will need to use a {% data variables.product.prodname_github_app %} or personal access token to authenticate. For more information and an example, see "[Uploading results to {% data variables.product.product_name %}](#uploading-results-to-github)" above. +Before you can use a {% data variables.product.prodname_codeql %} pack to analyze a database, you must download any packages you require from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}. This can be done either by using the `--download` flag as part of the `codeql database analyze` command. If a package is not publicly available, you will need to use a {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} to authenticate. For more information and an example, see "[Uploading results to {% data variables.product.product_name %}](#uploading-results-to-github)" above. | Option | Required | Usage | |--------|:--------:|-----| | `` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the scope and name of one or more CodeQL query packs to download using a comma-separated list. Optionally, include the version to download and unzip. By default the latest version of this pack is downloaded. Optionally, include a path to a query, directory, or query suite to run. If no path is included, then run the default queries of this pack. | -| `--github-auth-stdin` | | Optional. Pass the {% data variables.product.prodname_github_app %} or personal access token created for authentication with {% data variables.product.company_short %}'s REST API to the CLI via standard input. This is not needed if the command has access to a `GITHUB_TOKEN` environment variable set with this token. +| `--github-auth-stdin` | | Optional. Pass the {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} created for authentication with {% data variables.product.company_short %}'s REST API to the CLI via standard input. This is not needed if the command has access to a `GITHUB_TOKEN` environment variable set with this token. ### Basic example diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md index ff9280d755..e9d72e176b 100644 --- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md +++ b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md @@ -1,7 +1,7 @@ --- -title: Configurar o executor do CodeQL no seu sistema de CI +title: Configuring CodeQL runner in your CI system shortTitle: Configure CodeQL runner -intro: 'Você pode configurar como o {% data variables.product.prodname_codeql_runner %} faz a varredura do código no seu projeto e faz o upload dos resultados para o {% data variables.product.prodname_dotcom %}.' +intro: 'You can configure how the {% data variables.product.prodname_codeql_runner %} scans the code in your project and uploads the results to {% data variables.product.prodname_dotcom %}.' product: '{% data reusables.gated-features.code-scanning %}' miniTocMaxHeadingLevel: 3 redirect_from: @@ -24,35 +24,33 @@ topics: - C/C++ - C# - Java -ms.openlocfilehash: 4a1f114fa605f90ee4ccc82dcd30007f1ad17623 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147060887' --- -{% data reusables.code-scanning.deprecation-codeql-runner %} {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} -## Sobre a configuração de {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} no seu sistema de CI -Para integrar {% data variables.product.prodname_code_scanning %} ao seu sistema de CI, você pode usar o {% data variables.product.prodname_codeql_runner %}. Para obter mais informações, confira "[Como executar o {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)". +{% data reusables.code-scanning.deprecation-codeql-runner %} +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning %} -De modo geral, você invoca o {% data variables.product.prodname_codeql_runner %} da seguinte forma. +## About configuring {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system + +To integrate {% data variables.product.prodname_code_scanning %} into your CI system, you can use the {% data variables.product.prodname_codeql_runner %}. For more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)." + +In general, you invoke the {% data variables.product.prodname_codeql_runner %} as follows. ```shell $ /path/to-runner/codeql-runner-OS ``` -`/path/to-runner/` depende do local em que você baixou o {% data variables.product.prodname_codeql_runner %} no seu sistema de CI. `codeql-runner-OS` depende do sistema operacional usado. -Há três versões do {% data variables.product.prodname_codeql_runner %}, `codeql-runner-linux`, `codeql-runner-macos` e `codeql-runner-win`, para os sistemas Linux, macOS e Windows, respectivamente. +`/path/to-runner/` depends on where you've downloaded the {% data variables.product.prodname_codeql_runner %} on your CI system. `codeql-runner-OS` depends on the operating system you use. +There are three versions of the {% data variables.product.prodname_codeql_runner %}, `codeql-runner-linux`, `codeql-runner-macos`, and `codeql-runner-win`, for Linux, macOS, and Windows systems respectively. -Para personalizar a maneira como o {% data variables.product.prodname_codeql_runner %} verifica o código, use sinalizadores, como `--languages` e `--queries`, ou especifique configurações personalizadas em um arquivo de configuração separado. +To customize the way the {% data variables.product.prodname_codeql_runner %} scans your code, you can use flags, such as `--languages` and `--queries`, or you can specify custom settings in a separate configuration file. -## Fazer a varredura de pull requests +## Scanning pull requests -A varredura de código sempre que uma pull request é criada impede que os desenvolvedores introduzam novas vulnerabilidades e erros no código. +Scanning code whenever a pull request is created prevents developers from introducing new vulnerabilities and errors into the code. -Para verificar uma solicitação de pull, execute o comando `analyze` e use o sinalizador `--ref` para especificar a solicitação de pull. A referência é `refs/pull//head` ou `refs/pull//merge`, dependendo se você fez check-out do commit HEAD do branch de solicitação de pull ou de um commit de mesclagem com o branch base. +To scan a pull request, run the `analyze` command and use the `--ref` flag to specify the pull request. The reference is `refs/pull//head` or `refs/pull//merge`, depending on whether you have checked out the HEAD commit of the pull request branch or a merge commit with the base branch. ```shell $ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge @@ -60,50 +58,50 @@ $ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge {% note %} -**Observação:** se você analisar o código com uma ferramenta de terceiros e desejar que os resultados seja exibidos como verificações de solicitação de pull, execute o comando `upload` e use o sinalizador `--ref` para especificar a solicitação de pull em vez do branch. A referência é `refs/pull//head` ou `refs/pull//merge`. +**Note**: If you analyze code with a third-party tool and want the results to appear as pull request checks, you must run the `upload` command and use the `--ref` flag to specify the pull request instead of the branch. The reference is `refs/pull//head` or `refs/pull//merge`. {% endnote %} -## Sobrescrever a detecção automática de linguagem +## Overriding automatic language detection -O {% data variables.product.prodname_codeql_runner %} detecta e faz a varredura automática do código escrito nas linguagens compatíveis. +The {% data variables.product.prodname_codeql_runner %} automatically detects and scans code written in the supported languages. {% data reusables.code-scanning.codeql-languages-bullets %} {% data reusables.code-scanning.specify-language-to-analyze %} -Para substituir a detecção automática de linguagem, execute o comando `init` com o sinalizador `--languages`, seguido de uma lista de palavras-chave de linguagem separada por vírgula. As palavras-chave para os idiomas compatíveis são {% data reusables.code-scanning.codeql-languages-keywords %}. +To override automatic language detection, run the `init` command with the `--languages` flag, followed by a comma-separated list of language keywords. The keywords for the supported languages are {% data reusables.code-scanning.codeql-languages-keywords %}. ```shell $ /path/to-runner/codeql-runner-linux init --languages cpp,java ``` -## Executar consultas adicionais +## Running additional queries {% data reusables.code-scanning.run-additional-queries %} {% data reusables.code-scanning.codeql-query-suites-explanation %} -Para adicionar uma ou mais consultas, transmita uma lista separada por vírgula de caminhos para o sinalizador `--queries` do comando `init`. Você também pode especificar consultas adicionais em um arquivo de configuração. +To add one or more queries, pass a comma-separated list of paths to the `--queries` flag of the `init` command. You can also specify additional queries in a configuration file. -Se você também estiver usando um arquivo de configuração para as configurações personalizadas e estiver especificando consultas adicionais com o sinalizador `--queries`, o {% data variables.product.prodname_codeql_runner %} usará as consultas adicionais especificadas com o sinalizador `--queries` em vez de qualquer um no arquivo de configuração. -Se desejar executar o conjunto combinado de consultas adicionais especificadas com o sinalizador e no arquivo de configuração, adicione o símbolo `+` como prefixo ao valor transmitido para `--queries`. -Para obter mais informações, confira "[Como usar um arquivo de configuração personalizado](#using-a-custom-configuration-file)". +If you also are using a configuration file for custom settings, and you are also specifying additional queries with the `--queries` flag, the {% data variables.product.prodname_codeql_runner %} uses the additional queries specified with the `--queries` flag instead of any in the configuration file. +If you want to run the combined set of additional queries specified with the flag and in the configuration file, prefix the value passed to `--queries` with the `+` symbol. +For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)." -No exemplo a seguir,. o símbolo `+` garante que o {% data variables.product.prodname_codeql_runner %} usará as consultas adicionais com todas as consultas especificadas no arquivo de configuração referenciado. +In the following example, the `+` symbol ensures that the {% data variables.product.prodname_codeql_runner %} uses the additional queries together with any queries specified in the referenced configuration file. ```shell $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml --queries +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main ``` -## Usando um arquivo de configuração personalizado +## Using a custom configuration file -Em vez de passar informações adicionais para os comandos de {% data variables.product.prodname_codeql_runner %}, você pode especificar configurações personalizadas em um arquivo de configuração separado. +Instead of passing additional information to the {% data variables.product.prodname_codeql_runner %} commands, you can specify custom settings in a separate configuration file. -O arquivo de configuração é um arquivo YAML. Ele usa uma sintaxe semelhante à sintaxe do fluxo de trabalho do {% data variables.product.prodname_actions %}, conforme ilustrado nos exemplos abaixo. Para obter mais informações, confira "[Sintaxe de fluxo de trabalho do {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)". +The configuration file is a YAML file. It uses syntax similar to the workflow syntax for {% data variables.product.prodname_actions %}, as illustrated in the examples below. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)." -Use o sinalizador `--config-file` do comando `init` para especificar o arquivo de configuração. O valor de `--config-file` é o caminho para o arquivo de configuração que você deseja usar. Este exemplo carrega o arquivo de configuração _.github/codeql/codeql-config.yml_. +Use the `--config-file` flag of the `init` command to specify the configuration file. The value of `--config-file` is the path to the configuration file that you want to use. This example loads the configuration file _.github/codeql/codeql-config.yml_. ```shell $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml @@ -111,108 +109,108 @@ $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-c {% data reusables.code-scanning.custom-configuration-file %} -### Exemplo de arquivos de configuração +### Example configuration files {% data reusables.code-scanning.example-configuration-files %} -## Configurar o {% data variables.product.prodname_code_scanning %} para linguagens compiladas +## Configuring {% data variables.product.prodname_code_scanning %} for compiled languages -Para as linguagens compiladas C/C++, C#, e Java, o {% data variables.product.prodname_codeql %} constrói o código antes de analisá-lo. {% data reusables.code-scanning.analyze-go %} +For the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} builds the code before analyzing it. {% data reusables.code-scanning.analyze-go %} -Para muitos sistemas de criação comuns, o {% data variables.product.prodname_codeql_runner %} pode construir o código automaticamente. Para tentar compilar o código automaticamente, execute `autobuild` entre as etapas `init` e `analyze`. Observe que, se seu repositório precisar de uma versão específica de uma ferramenta de criação, primeiro você precisará instalar a ferramenta de criação manualmente. +For many common build systems, the {% data variables.product.prodname_codeql_runner %} can build the code automatically. To attempt to build the code automatically, run `autobuild` between the `init` and `analyze` steps. Note that if your repository requires a specific version of a build tool, you may need to install the build tool manually first. -O processo `autobuild` só tentará compilar _uma_ linguagem compilada para um repositório. A linguagem selecionada automaticamente para análise é a linguagem com mais arquivos. Caso deseje escolher uma linguagem explicitamente, use o sinalizador `--language` do comando `autobuild`. +The `autobuild` process only ever attempts to build _one_ compiled language for a repository. The language automatically selected for analysis is the language with the most files. If you want to choose a language explicitly, use the `--language` flag of the `autobuild` command. ```shell $ /path/to-runner/codeql-runner-linux autobuild --language csharp ``` -Se o comando `autobuild` não puder compilar o código, execute as etapas de build por conta própria, entre as etapas `init` e `analyze`. Para obter mais informações, confira "[Como executar o {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/running-codeql-runner-in-your-ci-system#compiled-language-example)". +If the `autobuild` command can't build your code, you can run the build steps yourself, between the `init` and `analyze` steps. For more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system#compiled-language-example)." -## Como carregar dados da {% data variables.product.prodname_code_scanning %} no {% data variables.product.prodname_dotcom %} +## Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %} -Por padrão, o {% data variables.product.prodname_codeql_runner %} carrega os resultados da {% data variables.product.prodname_code_scanning %} quando você executa o comando `analyze`. Você também pode carregar arquivos SARIF separadamente usando o comando `upload`. +By default, the {% data variables.product.prodname_codeql_runner %} uploads results from {% data variables.product.prodname_code_scanning %} when you run the `analyze` command. You can also upload SARIF files separately, by using the `upload` command. -Depois de enviar os dados, o {% data variables.product.prodname_dotcom %} exibirá os alertas no seu repositório. -- Se você os carregou em uma solicitação de pull, por exemplo `--ref refs/pull/42/merge` ou `--ref refs/pull/42/head`, os resultados serão exibidos como alertas em uma verificação de solicitação de pull. Para obter mais informações, confira "[Como fazer a triagem de alertas de verificação de código em solicitações de pull](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)". -- Se você os carregou em um branch, por exemplo, `--ref refs/heads/my-branch`, os resultados serão exibidos na guia **Segurança** do repositório. Para obter mais informações, confira "[Como gerenciar alertas de verificação de código do seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)". +Once you've uploaded the data, {% data variables.product.prodname_dotcom %} displays the alerts in your repository. +- If you uploaded to a pull request, for example `--ref refs/pull/42/merge` or `--ref refs/pull/42/head`, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." +- If you uploaded to a branch, for example `--ref refs/heads/my-branch`, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." -## Comando de referência de {% data variables.product.prodname_codeql_runner %} +## {% data variables.product.prodname_codeql_runner %} command reference -O {% data variables.product.prodname_codeql_runner %} é compatível os seguintes comandos e sinalizadores. +The {% data variables.product.prodname_codeql_runner %} supports the following commands and flags. ### `init` -Inicializa o {% data variables.product.prodname_codeql_runner %} e cria um banco de dados de {% data variables.product.prodname_codeql %} para cada linguagem a ser analisada. +Initializes the {% data variables.product.prodname_codeql_runner %} and creates a {% data variables.product.prodname_codeql %} database for each language to be analyzed. -| Sinalizador | Obrigatório | Valor de entrada | +| Flag | Required | Input value | | ---- |:--------:| ----------- | -| `--repository` | ✓ | Nome do repositório a ser inicializado. | -| `--github-url` | ✓ | URL da instância do {% data variables.product.prodname_dotcom %} onde seu repositório está hospedado. | -| `--github-auth-stdin` | ✓ | Leia o token de {% data variables.product.prodname_github_apps %} ou token de acesso pessoal da entrada padrão. | -| `--languages` | | Lista de linguagens para análise separada por vírgulas. Por padrão, o {% data variables.product.prodname_codeql_runner %} detecta e analisa todas as linguagens compatíveis no repositório. | -| `--queries` | | Lista separada por vírgulas de consultas adicionais a serem executadas, além do conjunto-padrão de consultas de segurança. Isso substitui a configuração `queries` no arquivo de configuração personalizado. | -| `--config-file` | | Caminho para o arquivo de configuração personalizado. | -| `--codeql-path` | | Caminho para uma cópia do CLI de {% data variables.product.prodname_codeql %} executável a ser usado. Por padrão, o {% data variables.product.prodname_codeql_runner %} faz o download de uma cópia. | -| `--temp-dir` | | Diretório onde os arquivos temporários são armazenados. O padrão é `./codeql-runner`. | -| `--tools-dir` | | Diretório onde as ferramentas de {% data variables.product.prodname_codeql %} e outros arquivos são armazenados entre as execuções. O padrão é um subdiretório do diretório home. | -| `--checkout-path` | | O caminho para o checkout do seu repositório. O padrão é o diretório de trabalho atual. | -| `--debug` | | Nenhum. Imprime mais resultados verbose. | -| `--trace-process-name` | | Avançado, apenas para Windows. Nome do processo em que um rastreador do Windows deste processo é injetado. | -| `--trace-process-level` | | Avançado, apenas para Windows. Número de níveis acima do processo principal em que um rastreador do Windows deste processo é injetado. | -| `-h`, `--help` | | Nenhum. Exibe ajuda para o comando. | +| `--repository` | ✓ | Name of the repository to initialize. | +| `--github-url` | ✓ | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted. | +| `--github-auth-stdin` | ✓ | Read the {% data variables.product.prodname_github_apps %} token or {% data variables.product.pat_generic %} from standard input. | +| `--languages` | | Comma-separated list of languages to analyze. By default, the {% data variables.product.prodname_codeql_runner %} detects and analyzes all supported languages in the repository. | +| `--queries` | | Comma-separated list of additional queries to run, in addition to the default suite of security queries. This overrides the `queries` setting in the custom configuration file. | +| `--config-file` | | Path to custom configuration file. | +| `--codeql-path` | | Path to a copy of the {% data variables.product.prodname_codeql %} CLI executable to use. By default, the {% data variables.product.prodname_codeql_runner %} downloads a copy. | +| `--temp-dir` | | Directory where temporary files are stored. The default is `./codeql-runner`. | +| `--tools-dir` | | Directory where {% data variables.product.prodname_codeql %} tools and other files are stored between runs. The default is a subdirectory of the home directory. | +| `--checkout-path` | | The path to the checkout of your repository. The default is the current working directory. | +| `--debug` | | None. Prints more verbose output. | +| `--trace-process-name` | | Advanced, Windows only. Name of the process where a Windows tracer of this process is injected. | +| `--trace-process-level` | | Advanced, Windows only. Number of levels up of the parent process where a Windows tracer of this process is injected. | +| `-h`, `--help` | | None. Displays help for the command. | ### `autobuild` -Tenta construir o código para as linguagens compiladas C/C++, C# e Java. Para essas linguagens, {% data variables.product.prodname_codeql %} cria o código antes de analisá-lo. Execute `autobuild` entre as etapas `init` e `analyze`. +Attempts to build the code for the compiled languages C/C++, C#, and Java. For those languages, {% data variables.product.prodname_codeql %} builds the code before analyzing it. Run `autobuild` between the `init` and `analyze` steps. -| Sinalizador | Obrigatório | Valor de entrada | +| Flag | Required | Input value | | ---- |:--------:| ----------- | -| `--language` | | A linguagem a ser criada. Por padrão, o {% data variables.product.prodname_codeql_runner %} cria a linguagem compilada com mais arquivos. | -| `--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. | +| `--language` | | The language to build. By default, the {% data variables.product.prodname_codeql_runner %} builds the compiled language with the most files. | +| `--temp-dir` | | Directory where temporary files are stored. The default is `./codeql-runner`. | +| `--debug` | | None. Prints more verbose output. | +| `-h`, `--help` | | None. Displays help for the command. | ### `analyze` -Analisa o código nos bancos de dados do {% data variables.product.prodname_codeql %} e carrega os resultados no {% data variables.product.product_name %}. +Analyzes the code in the {% data variables.product.prodname_codeql %} databases and uploads results to {% data variables.product.product_name %}. -| Sinalizador | Obrigatório | Valor de entrada | +| Flag | Required | Input value | | ---- |:--------:| ----------- | -| `--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 a ser analisada, por exemplo, `refs/heads/main` ou `refs/pull/42/merge`. No Git ou no Jenkins, isso corresponde ao valor de `git symbolic-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-stdin` | ✓ | Leia o token de {% data variables.product.prodname_github_apps %} ou token de acesso pessoal da entrada padrão. | -| `--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 %} carregue os resultados no {% data variables.product.product_name %}. | -| `--output-dir` | | Diretório onde os arquivos SARIF de saída são armazenados. O padrão está no diretório de arquivos temporários. | -| `--ram` | | A quantidade de memória a ser usada ao executar consultas. O padrão é usar toda a memória disponível. | -| `--no-add-snippets` | | Nenhum. Exclui snippets de código da saída de SARIF. | -| `--category` | | A categoria a incluir no arquivo de resultados SARIF para esta análise. Uma categoria pode ser usada para distinguir várias análises para a mesma ferramenta e commit, mas executado em diferentes linguagens ou diferentes partes do código. Esse valor será exibido como a propriedade `.automationDetails.id` no SARIF v2.1.0. | -| `--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. | +| `--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` or `refs/pull/42/merge`. In Git or 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-stdin` | ✓ | Read the {% data variables.product.prodname_github_apps %} token or {% data variables.product.pat_generic %} from standard input. | +| `--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_name %}. | +| `--output-dir` | | Directory where the output SARIF files are stored. The default is in the directory of temporary files. | +| `--ram` | | Amount of memory to use when running queries. The default is to use all available memory. | +| `--no-add-snippets` | | None. Excludes code snippets from the SARIF output. | +| `--category` | | Category to include in the SARIF results file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the `.automationDetails.id` property in SARIF v2.1.0. | +| `--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. | ### `upload` -Carrega arquivos SARIF no {% data variables.product.product_name %}. +Uploads SARIF files to {% data variables.product.product_name %}. {% note %} -**Observação**: se você analisar o código com o executor do CodeQL, o comando `analyze` carregará os resultados SARIF por padrão. Use o comando `upload` para carregar os resultados SARIF que foram gerados por outras ferramentas. +**Note**: If you analyze code with the CodeQL runner, the `analyze` command uploads SARIF results by default. You can use the `upload` command to upload SARIF results that were generated by other tools. {% endnote %} -| Sinalizador | Obrigatório | Valor de entrada | +| Flag | Required | Input value | | ---- |:--------:| ----------- | -| `--sarif-file` | ✓ | O arquivo SARIF a ser subido ou um diretório que contém vários arquivos SARIF. | -| `--repository` | ✓ | Nome do repositório que foi analisado. | -| `--commit` | ✓ | SHA do commit que foi 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 que foi analisada, por exemplo, `refs/heads/main` ou `refs/pull/42/merge`. No Git ou no Jenkins, isso corresponde ao valor de `git symbolic-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-stdin` | ✓ | Leia o token de {% data variables.product.prodname_github_apps %} ou token de acesso pessoal da entrada padrão. | -| `--checkout-path` | | O caminho para o checkout do seu repositório. O padrão é o diretório de trabalho atual. | -| `--debug` | | Nenhum. Imprime mais resultados verbose. | -| `-h`, `--help` | | Nenhum. Exibe ajuda para o comando. | +| `--sarif-file` | ✓ | SARIF file to upload, or a directory containing multiple SARIF files. | +| `--repository` | ✓ | Name of the repository that was analyzed. | +| `--commit` | ✓ | SHA of the commit that was analyzed. In Git and in Azure DevOps, this corresponds to the value of `git rev-parse HEAD`. In Jenkins, this corresponds to `$GIT_COMMIT`. | +| `--ref` | ✓ | Name of the reference that was analyzed, for example `refs/heads/main` or `refs/pull/42/merge`. In Git or 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-stdin` | ✓ | Read the {% data variables.product.prodname_github_apps %} token or {% data variables.product.pat_generic %} from standard input. | +| `--checkout-path` | | The path to the checkout of your repository. The default is the current working directory. | +| `--debug` | | None. Prints more verbose output. | +| `-h`, `--help` | | None. Displays help for the command. | diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md index 28ef5c6e85..8ad9bee420 100644 --- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md +++ b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md @@ -112,7 +112,7 @@ You should check that the output contains the expected languages and also that t ## Generating a token for authentication with {% data variables.product.product_name %} -Each CI server needs a {% data variables.product.prodname_github_app %} or personal access token for the {% data variables.product.prodname_codeql_cli %} to use to upload results to {% data variables.product.product_name %}. You must use an access token or a {% data variables.product.prodname_github_app %} with the `security_events` write permission. If CI servers already use a token with this scope to checkout repositories from {% data variables.product.product_name %}, you could potentially allow the {% data variables.product.prodname_codeql_cli %} to use the same token. Otherwise, you should create a new token with the `security_events` write permission and add this to the CI system's secret store. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +Each CI server needs a {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} for the {% data variables.product.prodname_codeql_cli %} to use to upload results to {% data variables.product.product_name %}. You must use an access token or a {% data variables.product.prodname_github_app %} with the `security_events` write permission. If CI servers already use a token with this scope to checkout repositories from {% data variables.product.product_name %}, you could potentially allow the {% data variables.product.prodname_codeql_cli %} to use the same token. Otherwise, you should create a new token with the `security_events` write permission and add this to the CI system's secret store. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." ## Next steps diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md index 533b2eefef..a2056c24bf 100644 --- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md +++ b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md @@ -1,7 +1,7 @@ --- -title: Executando um executor de CodeQL no seu sistema de CI +title: Running CodeQL runner in your CI system shortTitle: Run CodeQL runner -intro: 'Você pode usar {% data variables.product.prodname_codeql_runner %} para executar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} em um sistema de integração contínua de terceiros.' +intro: 'You can use the {% data variables.product.prodname_codeql_runner %} to perform {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in a third-party continuous integration system.' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system @@ -24,102 +24,102 @@ topics: - Integration - CI - SARIF -ms.openlocfilehash: c4803ff75aa157bc89dc2bfa776c03b3a1cf305a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146178676' --- + {% ifversion codeql-runner-supported %} -{% data reusables.code-scanning.deprecation-codeql-runner %} {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} +{% data reusables.code-scanning.deprecation-codeql-runner %} +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning %} -## Sobre o {% data variables.product.prodname_codeql_runner %} +## About the {% data variables.product.prodname_codeql_runner %} -O {% data variables.product.prodname_codeql_runner %} é uma ferramenta que você pode usar para executar {% data variables.product.prodname_code_scanning %} no código que você está processando em um sistema de integração contínua de terceiros (CI). {% data reusables.code-scanning.about-code-scanning %} Para obter informações, confira "[Sobre a {% data variables.product.prodname_code_scanning %} com o {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)". +The {% data variables.product.prodname_codeql_runner %} is a tool you can use to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." -Em muitos casos, é mais fácil configurar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} usando {% data variables.product.prodname_codeql_cli %} diretamente no seu sistema de CI. +In many cases it is easier to set up {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_cli %} directly in your CI system. -Como alternativa, você pode usar {% data variables.product.prodname_actions %} para executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_name %}. Para obter informações, confira "[Como configurar a {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)". +Alternatively, you can use {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %}. For information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/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 sistema de terceiros e chama o executor para analisar o código e carregar os resultados no {% data variables.product.product_name %}. Estes resultados são exibidos como alertas do {% data variables.product.prodname_code_scanning %} no repositório. +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_name %}. These results are displayed as {% data variables.product.prodname_code_scanning %} alerts in the repository. {% note %} -**Observação:** {% ifversion fpt or ghec %} -* O {% data variables.product.prodname_codeql_runner %} usa o CLI de {% data variables.product.prodname_codeql %} para analisar o código e, portanto, tem as mesmas condições da licença. É grátis usar em repositórios públicos que são mantidos no {% data variables.product.prodname_dotcom_the_website %}, e disponíveis para uso em repositórios privados que são propriedade de clientes com uma licença do {% data variables.product.prodname_advanced_security %}. Para obter informações, confira "[Termos e condições do {% data variables.product.product_name %} {% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql/license)" e "[CLI do {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)". +**Note:** +{% ifversion fpt or ghec %} +* The {% data variables.product.prodname_codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. It's free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." {% else %} -* O {% data variables.product.prodname_codeql_runner %} está disponível para os clientes com uma licença de {% data variables.product.prodname_advanced_security %}. -{% endif %} {% ifversion ghae %} -* O {% data variables.product.prodname_codeql_runner %} não deve ser confundido com o CLI de {% data variables.product.prodname_codeql %}. A CLI de {% data variables.product.prodname_codeql %} é uma interface de linha de comando que permite que você crie bancos de dados de {% data variables.product.prodname_codeql %} para pesquisa de segurança e executar consultas de {% data variables.product.prodname_codeql %}. -Para obter mais informações, confira "[{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/)". -{% endif %} {% endnote %} +* The {% data variables.product.prodname_codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license. +{% endif %} +{% ifversion ghae %} +* The {% data variables.product.prodname_codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is a command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries. +For more information, see "[{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/)." +{% endif %} +{% endnote %} -## Fazer o download do {% data variables.product.prodname_codeql_runner %} +## Downloading the {% data variables.product.prodname_codeql_runner %} -Baixe o {% data variables.product.prodname_codeql_runner %} em https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases. Em alguns sistemas operacionais, talvez você precise alterar as permissões para o arquivo baixado antes de executá-lo. +You can download the {% data variables.product.prodname_codeql_runner %} from https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it. -No Linux: +On Linux: ```shell chmod +x codeql-runner-linux ``` -No macOS: +On macOS: ```shell chmod +x codeql-runner-macos sudo xattr -d com.apple.quarantine codeql-runner-macos ``` -No Windows, o arquivo `codeql-runner-win.exe` geralmente não exige nenhuma alteração nas permissões. +On Windows, the `codeql-runner-win.exe` file usually requires no change to permissions. -## Adicionar {% data variables.product.prodname_codeql_runner %} ao seu sistema de CI +## Adding the {% data variables.product.prodname_codeql_runner %} to your CI system -Após fazer o download de {% data variables.product.prodname_codeql_runner %} e verificar se pode ser executado, você deverá disponibilizar o executor para cada servidor de CI que você pretende usar para {% data variables.product.prodname_code_scanning %}. Por exemplo, você pode configurar cada servidor para que copie o executor de um local central interno. Como alternativa, você poderia usar a API REST para obter o executor diretamente do {% data variables.product.prodname_dotcom %}, por exemplo: +Once you download the {% data variables.product.prodname_codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from {% data variables.product.prodname_dotcom %}, for example: ```shell -wget https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux +wget https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux chmod +x codeql-runner-linux ``` -Além disso, cada servidor de CI também precisa: +In addition to this, each CI server also needs: -- Um {% data variables.product.prodname_github_app %} ou o token de acesso pessoal do {% data variables.product.prodname_codeql_runner %} a ser usado. Você precisa usar um token de acesso com o escopo `repo` ou um {% data variables.product.prodname_github_app %} com a permissão de gravação em `security_events` e permissões de leitura em `metadata` e em `contents`. Para obter informações, confira "[Como criar {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" e "[Como criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)". -- Acesso ao pacote de {% data variables.product.prodname_codeql %} associado a esta versão do {% data variables.product.prodname_codeql_runner %}. Este pacote contém consultas e bibliotecas necessárias para a análise de {% data variables.product.prodname_codeql %} mais o CLI de {% data variables.product.prodname_codeql %}, que é usado internamente pelo executor. Para obter informações, confira "[CLI do {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/)". +- A {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} for the {% data variables.product.prodname_codeql_runner %} to use. You must use an access token with the `repo` scope, or a {% data variables.product.prodname_github_app %} with the `security_events` write permission, and `metadata` and `contents` read permissions. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." +- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.product.prodname_codeql_runner %}. This package contains queries and libraries needed for {% data variables.product.prodname_codeql %} analysis, plus the {% data variables.product.prodname_codeql %} CLI, which is used internally by the runner. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." -As opções para fornecer acesso ao pacote de{% data variables.product.prodname_codeql %} são: +The options for providing access to the {% data variables.product.prodname_codeql %} bundle are: -1. Permita que os servidores de CI acessem https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action para que o {% data variables.product.prodname_codeql_runner %} possa baixar o pacote automaticamente. -1. Baixe/extraia manualmente o pacote, armazene-o com outros recursos centrais e use o sinalizador `--codeql-path` para especificar o local do pacote em chamadas para inicializar o {% data variables.product.prodname_codeql_runner %}. +1. Allow the CI servers access to https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action so that the {% data variables.product.prodname_codeql_runner %} can download the bundle automatically. +1. Manually download/extract the bundle, store it with other central resources, and use the `--codeql-path` flag to specify the location of the bundle in calls to initialize the {% data variables.product.prodname_codeql_runner %}. -## Chamar {% data variables.product.prodname_codeql_runner %} +## Calling the {% data variables.product.prodname_codeql_runner %} -Você deve chamar {% data variables.product.prodname_codeql_runner %} no local de checkout do repositório que deseja analisar. Os dois comandos principais são: +You should call the {% data variables.product.prodname_codeql_runner %} from the checkout location of the repository you want to analyze. The two main commands are: -1. `init`, necessário para inicializar o executor e criar um banco de dados do {% data variables.product.prodname_codeql %} para cada linguagem a ser analisada. Estas bases de dados são preenchidas e analisadas por comandos subsequentes. -1. `analyze`, necessário para preencher os bancos de dados do {% data variables.product.prodname_codeql %}, analisá-los e carregar os resultados no {% data variables.product.product_name %}. +1. `init` required to initialize the runner and create a {% data variables.product.prodname_codeql %} database for each language to be analyzed. These databases are populated and analyzed by subsequent commands. +1. `analyze` required to populate the {% data variables.product.prodname_codeql %} databases, analyze them, and upload results to {% data variables.product.product_name %}. -Para os dois comandos, você precisa especificar a URL do {% data variables.product.product_name %}, o *OWNER/NAME* do repositório e os {% data variables.product.prodname_github_apps %} ou o token de acesso pessoal a serem usados para autenticação. Você também precisa especificar o local do pacote do CodeQL, a menos que o servidor de CI tenha acesso para baixá-lo diretamente do repositório `github/codeql-action`. +For both commands, you must specify the URL of {% data variables.product.product_name %}, the repository *OWNER/NAME*, and the {% data variables.product.prodname_github_apps %} or {% data variables.product.pat_generic %} to use for authentication. You also need to specify the location of the CodeQL bundle, unless the CI server has access to download it directly from the `github/codeql-action` repository. -Você pode configurar o local em que o {% data variables.product.prodname_codeql_runner %} armazena o pacote do CodeQL para análise futura em um servidor usando o sinalizador `--tools-dir` e o local em que ele armazena os arquivos temporários durante a análise usando `--temp-dir`. +You can configure where the {% data variables.product.prodname_codeql_runner %} stores the CodeQL bundle for future analysis on a server using the `--tools-dir` flag and where it stores temporary files during analysis using `--temp-dir`. -Para ver a referência de linha de comando do executor, use o sinalizador `-h`. Por exemplo, para listar todos os comandos, execute `codeql-runner-OS -h`, ou para listar todos os sinalizadores disponíveis para o comando `init`, execute `codeql-runner-OS init -h` (em que `OS` varia de acordo com o executável que está sendo usado). Para obter mais informações, confira "[Como configurar a {% data variables.product.prodname_code_scanning %} no seu sistema de CI](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system#codeql-runner-command-reference)". +To view the command-line reference for the runner, use the `-h` flag. For example, to list all commands run: `codeql-runner-OS -h`, or to list all the flags available for the `init` command run: `codeql-runner-OS init -h` (where `OS` varies according to the executable that you are using). For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system#codeql-runner-command-reference)." {% data reusables.code-scanning.upload-sarif-alert-limit %} -### Exemplo básico +### Basic example -Este exemplo executa a análise do {% data variables.product.prodname_codeql %} em um servidor de CI do Linux para o repositório `octo-org/example-repo` hospedado em `{% data variables.command_line.git_url_example %}`. O processo é muito simples porque o repositório contém apenas linguagens que podem ser analisadas diretamente pelo {% data variables.product.prodname_codeql %}, sem ser criado (ou seja, Go, JavaScript, Python e TypeScript). +This example runs {% data variables.product.prodname_codeql %} analysis on a Linux CI server for the `octo-org/example-repo` repository hosted on `{% data variables.command_line.git_url_example %}`. The process is very simple because the repository contains only languages that can be analyzed by {% data variables.product.prodname_codeql %} directly, without being built (that is, Go, JavaScript, Python, and TypeScript). -Neste exemplo, o servidor tem acesso para baixar o pacote do {% data variables.product.prodname_codeql %} diretamente do repositório `github/codeql-action`, ou seja, não é necessário usar o sinalizador `--codeql-path`. +In this example, the server has access to download the {% data variables.product.prodname_codeql %} bundle directly from the `github/codeql-action` repository, so there is no need to use the `--codeql-path` flag. -1. Confira o repositório a ser analisado. -1. Mova para o diretório para o local onde o repositório está reservado. -1. Inicialize {% data variables.product.prodname_codeql_runner %} e crie banco de dados do {% data variables.product.prodname_codeql %} para as linguagens detectadas. +1. Check out the repository to analyze. +1. Move into the directory where the repository is checked out. +1. Initialize the {% data variables.product.prodname_codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected. ```shell $ echo "$TOKEN" | /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo @@ -131,13 +131,13 @@ Neste exemplo, o servidor tem acesso para baixar o pacote do {% data variables.p {% data reusables.code-scanning.codeql-runner-analyze-example %} -### Exemplo de linguagem compilada +### Compiled language example -Este exemplo é semelhante ao exemplo anterior. No entanto, desta vez, o repositório tem o código em C/C++, C# ou Java. Para criar um banco de dados de {% data variables.product.prodname_codeql %} para essas linguagens, o CLI precisa monitorar a criação. No final do processo de inicialização, o executor informa o comando que você precisa configurar o ambiente antes de criar o código. Você precisa executar esse comando antes de chamar o processo normal de build de CI e executar o comando `analyze`. +This example is similar to the previous example, however this time the repository has code in C/C++, C#, or Java. To create a {% data variables.product.prodname_codeql %} database for these languages, the CLI needs to monitor the build. At the end of the initialization process, the runner reports the command you need to set up the environment before building the code. You need to run this command, before calling the normal CI build process, and then running the `analyze` command. -1. Confira o repositório a ser analisado. -1. Mova para o diretório para o local onde o repositório está reservado. -1. Inicialize {% data variables.product.prodname_codeql_runner %} e crie banco de dados do {% data variables.product.prodname_codeql %} para as linguagens detectadas. +1. Check out the repository to analyze. +1. Move into the directory where the repository is checked out. +1. Initialize the {% data variables.product.prodname_codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected. ```shell $ echo "$TOKEN" | /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2 --github-url {% data variables.command_line.git_url_example %} --github-auth-stdin @@ -148,37 +148,37 @@ Este exemplo é semelhante ao exemplo anterior. No entanto, desta vez, o reposit Please export these variables to future processes so that CodeQL can monitor the build, for example by running ". /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh". ``` -1. Obtenha o script gerado pela ação `init` para configurar o ambiente para monitorar o build. Observe o ponto e espaço principal no seguinte trecho do código. +1. Source the script generated by the `init` action to set up the environment to monitor the build. Note the leading dot and space in the following code snippet. ```shell $ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh ``` -1. Crie o código. No macOS, você precisa adicionar a variável de ambiente `$CODEQL_RUNNER` como prefixo ao comando de build. Para obter mais informações, confira "[Solução de problemas do {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)". +1. Build the code. On macOS, you need to prefix the build command with the environment variable `$CODEQL_RUNNER`. For more information, see "[Troubleshooting {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)." {% data reusables.code-scanning.codeql-runner-analyze-example %} {% note %} -**Observação:** se você usar um build conteinerizado, precisará executar o {% data variables.product.prodname_codeql_runner %} no contêiner em que a tarefa de build ocorre. +**Note:** If you use a containerized build, you need to run the {% data variables.product.prodname_codeql_runner %} in the container where your build task takes place. {% endnote %} -## Leitura adicional +## Further reading -- "[Como configurar o {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)" -- "[Solução de problemas do {% data variables.product.prodname_codeql_runner %} no seu sistema de CI](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system)" +- "[Configuring {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)" +- "[Troubleshooting {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system)" {% else %} -## Sobre o {% data variables.product.prodname_codeql_runner %} +## About the {% data variables.product.prodname_codeql_runner %} -O {% data variables.product.prodname_codeql_runner %} foi descontinuado. A versão 2.7.6 da [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-cli-binaries/releases) tem paridade completa de recursos. +The {% data variables.product.prodname_codeql_runner %} has been deprecated. [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-cli-binaries/releases) version 2.7.6 has complete feature parity. -Para obter informações sobre como migrar para a {% data variables.product.prodname_codeql_cli %}, confira "[Como migrar do executor do CodeQL para a CLI do CodeQL](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)". +For information on migrating to {% data variables.product.prodname_codeql_cli %}, see "[Migrating from the CodeQL runner to CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)." -## Leitura adicional +## Further reading -- [Reprovação do executor do CodeQL](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/) no blog do GitHub +- [CodeQL runner deprecation](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/) in the GitHub Blog {% endif %} diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md index c85f5f85e8..fa3ad2ded3 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md @@ -1,6 +1,6 @@ --- -title: Sobre alertas do Dependabot -intro: 'O {% data variables.product.product_name %} envia {% data variables.product.prodname_dependabot_alerts %} quando detectamos que o repositório usa uma dependência vulnerável{% ifversion GH-advisory-db-supports-malware %} ou um malware{% endif %}.' +title: About Dependabot alerts +intro: '{% data variables.product.product_name %} sends {% data variables.product.prodname_dependabot_alerts %} when we detect that your repository uses a vulnerable dependency{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}.' redirect_from: - /articles/about-security-alerts-for-vulnerable-dependencies - /github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies @@ -20,87 +20,87 @@ topics: - Repositories - Dependencies shortTitle: Dependabot alerts -ms.openlocfilehash: 4a1e85a620465247dcd63e8ce9c88c99a0af31fd -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147526731' --- -## Sobre {% data variables.product.prodname_dependabot_alerts %} +## About {% data variables.product.prodname_dependabot_alerts %} -{% ifversion GH-advisory-db-supports-malware %} {% data reusables.advisory-database.beta-malware-advisories %} {% endif %} +{% ifversion GH-advisory-db-supports-malware %} +{% data reusables.advisory-database.beta-malware-advisories %} +{% endif %} -Os {% data variables.product.prodname_dependabot_alerts %} informam que o código depende de um pacote que não é seguro. +{% data variables.product.prodname_dependabot_alerts %} tell you that your code depends on a package that is insecure. -Quando o código depende de um pacote que tem uma vulnerabilidade de segurança, isso pode causar uma série de problemas para o projeto ou para as pessoas que o usam. Você deve atualizar o pacote para uma versão segura o quanto antes.{% ifversion GH-advisory-db-supports-malware %} Se o código usar malware, você precisará substituir o pacote por uma alternativa segura.{% endif %} +If your code depends on a package with a security vulnerability, this can cause a range of problems for your project or the people who use it. You should upgrade to a secure version of the package as soon as possible.{% ifversion GH-advisory-db-supports-malware %} If your code uses malware, you need to replace the package with a secure alternative.{% endif %} {% data reusables.security-advisory.link-browsing-advisory-db %} -## Detecção de dependências não seguras +## Detection of insecure dependencies {% data reusables.dependabot.dependabot-alerts-beta %} -O {% data variables.product.prodname_dependabot %} faz uma verificação para detectar dependências não seguras e envia {% data variables.product.prodname_dependabot_alerts %} quando: +{% data variables.product.prodname_dependabot %} performs a scan to detect insecure dependencies, and sends {% data variables.product.prodname_dependabot_alerts %} when: {% ifversion fpt or ghec %} -- Uma nova vulnerabilidade é adicionada ao {% data variables.product.prodname_advisory_database %}. Para obter mais informações, confira "[Procurar avisos de segurança no {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database)".{% else %} -- Novos dados de consultoria são sincronizados com o {% data variables.product.product_location %} a cada hora por meio do {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %} {% note %} +- A new advisory is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database)."{% else %} +- New advisory data is synchronized to {% data variables.location.product_location %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %} + {% note %} - **Observação:** apenas as consultorias que foram revisadas pelo {% data variables.product.company_short %} vão disparar {% data variables.product.prodname_dependabot_alerts %}. + **Note:** Only advisories that have been reviewed by {% data variables.product.company_short %} will trigger {% data variables.product.prodname_dependabot_alerts %}. {% endnote %} -- Quanto o grafo de dependência de um repositório é alterado. Por exemplo, quando um colaborador efetua push de um commit para alterar os pacotes ou as versões dependentes{% ifversion fpt or ghec %} ou quando o código de uma das dependências é alterado{% endif %}. Para obter mais informações, confira "[Sobre o grafo de dependência](/code-security/supply-chain-security/about-the-dependency-graph)". +- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% ifversion fpt or ghec %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/code-security/supply-chain-security/about-the-dependency-graph)." {% data reusables.repositories.dependency-review %} -Para obter uma lista dos ecossistemas nos quais o {% data variables.product.product_name %} detecta dependências não seguras, confira "[Ecossistemas de pacotes com suporte](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)". +For a list of the ecosystems that {% data variables.product.product_name %} detects insecure dependencies in, see "[Supported package ecosystems](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." {% note %} -**Observação:** é importante manter seus arquivos de manifesto e de bloqueio atualizados. Se o grafo de dependência não refletir corretamente as dependências e versões atuais, você poderá perder alertas sobre dependências não seguras que forem usadas. Você também pode receber alertas de dependências que você já não usa. +**Note:** It is important to keep your manifest and lock files up to date. If the dependency graph doesn't accurately reflect your current dependencies and versions, then you could miss alerts for insecure dependencies that you use. You may also get alerts for dependencies that you no longer use. {% endnote %} -## Configuração de {% data variables.product.prodname_dependabot_alerts %} +## Configuration of {% data variables.product.prodname_dependabot_alerts %} {% data reusables.repositories.enable-security-alerts %} -{% ifversion fpt or ghec %}O {% data variables.product.prodname_dotcom %} detecta dependências vulneráveis e malware em repositórios _públicos_ e exibe o grafo de dependência, mas não gera {% data variables.product.prodname_dependabot_alerts %} por padrão. Proprietários de repositórios ou pessoas com acesso de administrador podem habilitar {% data variables.product.prodname_dependabot_alerts %} para repositórios públicos. Os proprietários de repositórios privados ou pessoas com acesso de administrador, podem habilitar o {% data variables.product.prodname_dependabot_alerts %} ativando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para seus repositórios. +{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies and malware in _public_ repositories and displays the dependency graph, but does not generate {% data variables.product.prodname_dependabot_alerts %} by default. Repository owners or people with admin access can enable {% data variables.product.prodname_dependabot_alerts %} for public repositories. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. -Você também pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} em todos os repositórios pertencentes à sua conta de usuário ou de organização. Para obter mais informações, confira "[Como configurar {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts)." +You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Configuring {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts)." -Para obter informações sobre os requisitos de acesso para ações relacionadas aos {% data variables.product.prodname_dependabot_alerts %}, confira "[Funções de repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#access-requirements-for-security-features)". +For information about access requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#access-requirements-for-security-features)." -O {% data variables.product.product_name %} começa a gerar o grafo de dependência imediatamente e gera alertas sobre dependências não seguras assim que elas são identificadas. O gráfico geralmente é preenchido em minutos, mas isso pode levar mais tempo para repositórios com muitas dependências. Para obter mais informações, confira "[Como gerenciar configurações de uso de dados para seu repositório privado](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)". +{% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any insecure dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)." {% endif %} -Quando o {% data variables.product.product_name %} identifica uma dependência vulnerável{% ifversion GH-advisory-db-supports-malware %} ou um malware{% endif %}, geramos um alerta do {% data variables.product.prodname_dependabot %} e o exibimos {% ifversion fpt or ghec or ghes %} na guia Segurança do repositório e{% endif %} no grafo de dependência do repositório. O alerta inclui {% ifversion fpt or ghec or ghes %}um link para o arquivo afetado no projeto e {% endif %}informações sobre uma versão corrigida. {% data variables.product.product_name %} também pode notificar os mantenedores dos repositórios afetados sobre o novo alerta de acordo com as suas preferências de notificação. Para obter mais informações, confira "[Como configurar notificações para o {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)". +When {% data variables.product.product_name %} identifies a vulnerable dependency{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}, we generate a {% data variables.product.prodname_dependabot %} alert and display it {% ifversion fpt or ghec or ghes %} on the Security tab for the repository and{% endif %} in the repository's dependency graph. The alert includes {% ifversion fpt or ghec or ghes %}a link to the affected file in the project, and {% endif %}information about a fixed version. {% data variables.product.product_name %} may also notify the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)." -{% ifversion fpt or ghec or ghes > 3.2 %} Para os repositórios em que as {% data variables.product.prodname_dependabot_security_updates %} estão habilitadas, o alerta também poderá conter um link para uma solicitação de pull a fim de atualizar o arquivo de manifesto ou de bloqueio para a versão mínima que resolve a vulnerabilidade. Para obter mais informações, confira "[Sobre as {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)". +{% ifversion fpt or ghec or ghes > 3.2 %} +For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." {% endif %} {% warning %} -**Observação**: os recursos de segurança do {% data variables.product.product_name %} não afirmam que capturam todas as vulnerabilidades{% ifversion GH-advisory-db-supports-malware %} e malwares{% endif %}. Mantemos ativamente um {% data variables.product.prodname_advisory_database %} e geramos alertas com as informações mais atualizadas. No entanto, não podemos capturar tudo nem informar sobre vulnerabilidades conhecidas em um período garantido. Esses recursos não substituem a análise humana de cada dependência em busca de possíveis vulnerabilidades ou outros problemas. Portanto, recomendamos que você busque serviços de segurança ou realize uma análise de dependências completa sempre que necessário. +**Note**: {% data variables.product.product_name %}'s security features do not claim to catch all vulnerabilities{% ifversion GH-advisory-db-supports-malware %} and malware{% endif %}. We actively maintain {% data variables.product.prodname_advisory_database %} and generate alerts with the most up-to-date information. However, we cannot catch everything or tell you about known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough dependency review when necessary. {% endwarning %} -## Acesso a {% data variables.product.prodname_dependabot_alerts %} +## Access to {% data variables.product.prodname_dependabot_alerts %} -É possível ver todos os alertas que afetam determinado projeto{% ifversion fpt or ghec %} na guia Segurança do repositório ou{% endif %} no grafo de dependência do repositório. Para saber mais, confira "[Como exibir e atualizar {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)". +You can see all of the alerts that affect a particular project{% ifversion fpt or ghec %} on the repository's Security tab or{% endif %} in the repository's dependency graph. For more information, see "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)." -Por padrão, notificamos as pessoas com permissões de administrador nos repositórios afetados sobre os novos {% data variables.product.prodname_dependabot_alerts %}. {% ifversion fpt or ghec %}O {% data variables.product.product_name %} nunca divulga publicamente as dependências não seguras de nenhum repositório. Você também pode tornar o {% data variables.product.prodname_dependabot_alerts %} visível para outras pessoas ou equipes que trabalham com repositórios pertencentes a você ou para os quais tem permissões de administrador. Para obter mais informações, confira "[Como gerenciar as configurações de segurança e de análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". +By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}. {% ifversion fpt or ghec %}{% data variables.product.product_name %} never publicly discloses insecure dependencies for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working with repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." {% endif %} -{% data reusables.notifications.vulnerable-dependency-notification-enable %} {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %} Para obter mais informações, confira "[Como configurar notificações para {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)". +{% data reusables.notifications.vulnerable-dependency-notification-enable %} +{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %} For more information, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)." -Você também pode ver todos os {% data variables.product.prodname_dependabot_alerts %} que correspondem a uma vulnerabilidade específica no {% data variables.product.prodname_advisory_database %}. {% data reusables.security-advisory.link-browsing-advisory-db %} +You can also see all the {% data variables.product.prodname_dependabot_alerts %} that correspond to a particular advisory in the {% data variables.product.prodname_advisory_database %}. {% data reusables.security-advisory.link-browsing-advisory-db %} {% ifversion fpt or ghec or ghes > 3.2 %} -## Leitura adicional +## Further reading -- "[Sobre as {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" -- "[Como exibir e atualizar {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% endif %} {% ifversion fpt or ghec %}─ "[Privacidade no {% data variables.product.prodname_dotcom %}](/get-started/privacy-on-github)"{% endif %} +- "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% endif %} +{% ifversion fpt or ghec %}- "[Privacy on {% data variables.product.prodname_dotcom %}](/get-started/privacy-on-github)"{% endif %} diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md index 00c92688af..663dc63e1b 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md @@ -149,9 +149,9 @@ For any {% data variables.product.company_short %}-reviewed advisory in the {% d 5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name. {% ifversion security-advisories-ghes-ghae %} -## Accessing the local advisory database on {% data variables.product.product_location %} +## Accessing the local advisory database on {% data variables.location.product_location %} -If your site administrator has enabled {% data variables.product.prodname_github_connect %} for {% data variables.product.product_location %}, you can also browse reviewed advisories locally. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)". +If your site administrator has enabled {% data variables.product.prodname_github_connect %} for {% data variables.location.product_location %}, you can also browse reviewed advisories locally. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)". You can use your local advisory database to check whether a specific security vulnerability is included, and therefore whether you'd get alerts for vulnerable dependencies. You can also view any vulnerable repositories. @@ -165,9 +165,9 @@ You can use your local advisory database to check whether a specific security vu {% endnote %} 3. Click an advisory to view details.{% ifversion GH-advisory-db-supports-malware %} By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. To show malware advisories, use `type:malware` in the search bar.{% endif %} -You can also suggest improvements to any advisory directly from your local advisory database. For more information, see "[Editing advisories from {% data variables.product.product_location %}](/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database#editing-advisories-from-your-github-enterprise-server-instance)". +You can also suggest improvements to any advisory directly from your local advisory database. For more information, see "[Editing advisories from {% data variables.location.product_location %}](/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database#editing-advisories-from-your-github-enterprise-server-instance)". -### Viewing vulnerable repositories for {% data variables.product.product_location %} +### Viewing vulnerable repositories for {% data variables.location.product_location %} {% data reusables.repositories.enable-security-alerts %} diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md index 2a8eaeb186..688f003461 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md @@ -43,9 +43,9 @@ Only repository owners and administrators can edit repository-level security adv You can also open a pull request directly on an advisory file in the [github/advisory-database](https://github.com/github/advisory-database) repository. For more information, see the [contribution guidelines](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md). {% ifversion security-advisories-ghes-ghae %} -## Editing advisories from {% data variables.product.product_location %} +## Editing advisories from {% data variables.location.product_location %} -If you have {% data variables.product.prodname_github_connect %} enabled for {% data variables.product.product_location %}, you will be able to see advisories by adding `/advisories` to the instance url. +If you have {% data variables.product.prodname_github_connect %} enabled for {% data variables.location.product_location %}, you will be able to see advisories by adding `/advisories` to the instance url. 1. Navigate to `https://HOSTNAME/advisories`. 2. Select the security advisory you would like to contribute to. diff --git a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md index b6cf7bad95..4d727384fd 100644 --- a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md +++ b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md @@ -115,7 +115,7 @@ jobs: {% note %} -**Note:** Your site administrator can override these restrictions for {% data variables.product.product_location %}. For more information, see "[Troubleshooting {% data variables.product.prodname_actions %} for your enterprise](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise#troubleshooting-failures-when-dependabot-triggers-existing-workflows)." +**Note:** Your site administrator can override these restrictions for {% data variables.location.product_location %}. For more information, see "[Troubleshooting {% data variables.product.prodname_actions %} for your enterprise](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise#troubleshooting-failures-when-dependabot-triggers-existing-workflows)." If the restrictions are removed, when a workflow is triggered by {% data variables.product.prodname_dependabot %} it will have access to {% data variables.product.prodname_actions %} secrets and can use the `permissions` term to increase the default scope of the `GITHUB_TOKEN` from read-only access. You can ignore the specific steps in the "Handling `pull_request` events" and "Handling `push` events" sections, as it no longer applies. @@ -245,7 +245,7 @@ Here are several common scenarios that can be automated using {% data variables. {% note %} -**Note:** If your site administrator has overridden restrictions for {% data variables.product.prodname_dependabot %} on {% data variables.product.product_location %}, you can use `pull_request` instead of `pull_request_target` in the following workflows. +**Note:** If your site administrator has overridden restrictions for {% data variables.product.prodname_dependabot %} on {% data variables.location.product_location %}, you can use `pull_request` instead of `pull_request_target` in the following workflows. {% endnote %} diff --git a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md index b237676f40..7974d9e6ee 100644 --- a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -1,6 +1,6 @@ --- -title: Solução de problemas de detecção de dependências vulneráveis -intro: 'Se as informações sobre dependências relatadas por {% data variables.product.product_name %} não são o que você esperava, há uma série de pontos a considerar, e várias coisas que você pode verificar.' +title: Troubleshooting the detection of vulnerable dependencies +intro: 'If the dependency information reported by {% data variables.product.product_name %} is not what you expected, there are a number of points to consider, and various things you can check.' shortTitle: Troubleshoot vulnerability detection redirect_from: - /github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies @@ -22,81 +22,78 @@ topics: - Vulnerabilities - CVEs - Repositories -ms.openlocfilehash: 50e63a273d1bd787c2c324d3ceed9a8d31b64c9e -ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147883414' --- -{% data reusables.dependabot.beta-security-and-version-updates %} {% data reusables.dependabot.result-discrepancy %} -## Por que algumas dependências parecem estar faltando? +{% data reusables.dependabot.beta-security-and-version-updates %} +{% data reusables.dependabot.result-discrepancy %} -O {% data variables.product.prodname_dotcom %} gera e exibe dados de dependência de maneira diferente de outras ferramentas. Consequentemente, se você usou outra ferramenta para identificar dependências, quase certamente verá resultados diferentes. Considere o seguinte: +## Why do some dependencies seem to be missing? -* O {% data variables.product.prodname_advisory_database %} é uma das fontes de dados que o {% data variables.product.prodname_dotcom %} usa para identificar dependências vulneráveis {% ifversion GH-advisory-db-supports-malware %} e malware{% endif %}. Ele é um banco de dados coletado gratuito, que contém de avisos de segurança de ecossistemas de pacotes comuns no {% data variables.product.prodname_dotcom %}. Inclui tanto dados relatados diretamente para {% data variables.product.prodname_dotcom %} de {% data variables.product.prodname_security_advisories %} quanto os feeds oficiais e as fontes comunitárias. Estes dados são revisados e curados por {% data variables.product.prodname_dotcom %} para garantir que informações falsas ou não acionáveis não sejam compartilhadas com a comunidade de desenvolvimento. {% data reusables.security-advisory.link-browsing-advisory-db %} -* O gráfico de dependências analisa todos os arquivos conhecidos de manifesto de pacote no repositório de um usuário. Por exemplo, para o npm, ele analisará o arquivo _package-lock.json_. Ele constrói um gráfico de todas as dependências do repositório e dependências públicas. Isso acontece quando você habilita o gráfico de dependências e quando alguém faz push para o branch-padrão, e inclui commits que fazem alterações em um formato de manifesto compatível. Para obter mais informações, confira "[Sobre o grafo de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" e "[Solução de problemas do grafo de dependência](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)". -* O {% data variables.product.prodname_dependabot %} examina qualquer push, para o branch padrão, que contém um arquivo de manifesto. Quando um novo aviso é adicionado, ele verifica todos os repositórios existentes e gera um alerta para cada repositório afetado. Os {% data variables.product.prodname_dependabot_alerts %} são agregados no nível do repositório, não é criado um alerta para cada aviso. Para obter mais informações, confira "[Sobre os {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)". -* {% ifversion fpt or ghec or ghes > 3.2 %}As {% data variables.product.prodname_dependabot_security_updates %} são disparadas quando você recebe um alerta sobre uma dependência vulnerável no seu repositório. Sempre que possível, {% data variables.product.prodname_dependabot %} cria um pull request no repositório para atualizar a dependência vulnerável à versão mínima segura necessária para evitar a vulnerabilidade. Para obter mais informações, confira "[Sobre as {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" e "[Solução de problemas de erros do {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)". +{% data variables.product.prodname_dotcom %} generates and displays dependency data differently than other tools. Consequently, if you've been using another tool to identify dependencies you will almost certainly see different results. Consider the following: + +* {% data variables.product.prodname_advisory_database %} is one of the data sources that {% data variables.product.prodname_dotcom %} uses to identify vulnerable dependencies{% ifversion GH-advisory-db-supports-malware %} and malware{% endif %}. It's a free, curated database of security advisories for common package ecosystems on {% data variables.product.prodname_dotcom %}. It includes both data reported directly to {% data variables.product.prodname_dotcom %} from {% data variables.product.prodname_security_advisories %}, as well as official feeds and community sources. This data is reviewed and curated by {% data variables.product.prodname_dotcom %} to ensure that false or unactionable information is not shared with the development community. {% data reusables.security-advisory.link-browsing-advisory-db %} +* The dependency graph parses all known package manifest files in a user’s repository. For example, for npm it will parse the _package-lock.json_ file. It constructs a graph of all of the repository’s dependencies and public dependents. This happens when you enable the dependency graph and when anyone pushes to the default branch, and it includes commits that makes changes to a supported manifest format. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" and "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)." +* {% data variables.product.prodname_dependabot %} scans any push, to the default branch, that contains a manifest file. When a new advisory is added, it scans all existing repositories and generates an alert for each repository that is affected. {% data variables.product.prodname_dependabot_alerts %} are aggregated at the repository level, rather than creating one alert per advisory. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." +* {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)." - {% endif %}O {% data variables.product.prodname_dependabot %} não verifica os repositórios com agendamento, mas somente quando algo muda. Por exemplo, uma verificação é disparada quando uma nova dependência é adicionada (o {% data variables.product.prodname_dotcom %} verifica isso em cada push) ou quando um novo aviso é adicionado ao banco de dados{% ifversion ghes or ghae %} e sincronizado com o {% data variables.product.product_location %}{% endif %}. Para obter mais informações, confira "[Sobre os {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-insecure-dependencies)". + {% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new advisory is added to the database{% ifversion ghes or ghae %} and synchronized to {% data variables.location.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-insecure-dependencies)." -## Os {% data variables.product.prodname_dependabot_alerts %} só estão relacionados a dependências não seguras nos manifestos e arquivos de bloqueio? +## Do {% data variables.product.prodname_dependabot_alerts %} only relate to insecure dependencies in manifests and lockfiles? -Os {% data variables.product.prodname_dependabot_alerts %} aconselham você com relação a dependências que você deve atualizar, incluindo dependências transitivas, em que a versão pode ser determinada a partir de um manifesto ou de um arquivo de bloqueio. {% ifversion fpt or ghec or ghes > 3.2 %}As {% data variables.product.prodname_dependabot_security_updates %} sugerem apenas uma alteração em que o {% data variables.product.prodname_dependabot %} pode "corrigir" diretamente a dependência, ou seja, quando elas são: -* Dependências diretas, que são definidas explicitamente em um manifesto ou arquivo de bloqueio -* Dependências transitórias declaradas em um arquivo de bloqueio{% endif %} +{% data variables.product.prodname_dependabot_alerts %} advise you about dependencies you should update, including transitive dependencies, where the version can be determined from a manifest or a lockfile. {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} only suggest a change where {% data variables.product.prodname_dependabot %} can directly "fix" the dependency, that is, when these are: +* Direct dependencies explicitly declared in a manifest or lockfile +* Transitive dependencies declared in a lockfile{% endif %} -**Verificação**: a vulnerabilidade não capturada é de um componente que não está especificado no manifesto ou no arquivo de bloqueio do repositório? +**Check**: Is the uncaught vulnerability for a component that's not specified in the repository's manifest or lockfile? -## Por que não recebo {% data variables.product.prodname_dependabot_alerts %} de alguns ecossistemas? +## Why don't I get {% data variables.product.prodname_dependabot_alerts %} for some ecosystems? -Há suporte para {% data variables.product.prodname_dependabot_alerts %} em um conjunto de ecossistemas em que podemos fornecer dados acionáveis e de alta qualidade. Os avisos coletados no {% data variables.product.prodname_advisory_database %}, o grafo de dependência, {% ifversion fpt or ghec %}{% data variables.product.prodname_dependabot %} as atualizações de segurança, {% endif %}e os {% data variables.product.prodname_dependabot_alerts %} são fornecidos para vários ecossistemas, incluindo o Maven do Java, o npm do JavaScript e o YARN, NuGet do .NET, o pip do Python, RubyGems do Ruby e o Composer do PHP. Nós continuaremos a adicionar suporte para mais ecossistemas ao longo do tempo. Para ter uma visão geral dos ecossistemas de pacote aos quais damos suporte, confira "[Sobre o grafo de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)". +{% data variables.product.prodname_dependabot_alerts %} are supported for a set of ecosystems where we can provide high-quality, actionable data. Curated advisories in the {% data variables.product.prodname_advisory_database %}, the dependency graph, {% ifversion fpt or ghec %}{% data variables.product.prodname_dependabot %} security updates, {% endif %}and {% data variables.product.prodname_dependabot_alerts %} are provided for several ecosystems, including Java’s Maven, JavaScript’s npm and Yarn, .NET’s NuGet, Python’s pip, Ruby's RubyGems, and PHP’s Composer. We'll continue to add support for more ecosystems over time. For an overview of the package ecosystems that we support, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." -Vale a pena observar que podem existir avisos de segurança para outros ecossistemas. As informações em um aviso de segurança não examinado são fornecidas pelos mantenedores de um determinado repositório. Esses dados não são coletados pelo {% data variables.product.prodname_dotcom %}. {% data reusables.security-advisory.link-browsing-advisory-db %} +It's worth noting that security advisories may exist for other ecosystems. The information in an unreviewed security advisory is provided by the maintainers of a particular repository. This data is not curated by {% data variables.product.prodname_dotcom %}. {% data reusables.security-advisory.link-browsing-advisory-db %} -**Verificação**: a vulnerabilidade não capturada se aplica a um ecossistema sem suporte? +**Check**: Does the uncaught vulnerability apply to an unsupported ecosystem? -## Há quantos anos o {% data variables.product.prodname_dependabot %} gera alertas para vulnerabilidades conhecidas? +## Does {% data variables.product.prodname_dependabot %} generate alerts for vulnerabilities that have been known for many years? -O {% data variables.product.prodname_advisory_database %} foi lançado em novembro de 2019 e preenchido inicialmente com avisos de riscos de segurança nos ecossistemas com suporte encontrados a partir de 2017. Ao adicionar CVEs ao banco de dados, priorizamos a curadoria de CVEs mais recentes e CVEs que afetam versões mais recentes do software. +The {% data variables.product.prodname_advisory_database %} was launched in November 2019, and initially back-filled to include advisories for security risks in the supported ecosystems, starting from 2017. When adding CVEs to the database, we prioritize curating newer CVEs, and CVEs affecting newer versions of software. -Algumas informações sobre vulnerabilidades mais antigas estão disponíveis, especialmente quando estes CVEs estão particularmente disseminados. No entanto algumas vulnerabilidades antigas não estão incluídas no {% data variables.product.prodname_advisory_database %}. Se houver uma vulnerabilidade antiga específica que você precisar incluir no banco de dados, entre em contato com {% data variables.contact.contact_support %}. +Some information on older vulnerabilities is available, especially where these CVEs are particularly widespread, however some old vulnerabilities are not included in the {% data variables.product.prodname_advisory_database %}. If there's a specific old vulnerability that you need to be included in the database, contact {% data variables.contact.contact_support %}. -**Verificação**: a vulnerabilidade não capturada tem uma data de publicação anterior a 2017 no National Vulnerability Database? +**Check**: Does the uncaught vulnerability have a publish date earlier than 2017 in the National Vulnerability Database? -## Por que o {% data variables.product.prodname_advisory_database %} usa um subconjunto de dados de vulnerabilidade publicada? +## Why does {% data variables.product.prodname_advisory_database %} use a subset of published vulnerability data? -Algumas ferramentas de terceiros usam dados de CVE não descurados que não são verificados ou filtrados por um ser humano. Isto significa que os CVEs com erros de etiqueta ou de gravidade, ou outros problemas de qualidade, gerarão alertas mais frequentes, mais ruidosos e menos úteis. +Some third-party tools use uncurated CVE data that isn't checked or filtered by a human. This means that CVEs with tagging or severity errors, or other quality issues, will cause more frequent, more noisy, and less useful alerts. -Como o {% data variables.product.prodname_dependabot %} usa os dados coletados no {% data variables.product.prodname_advisory_database %}, o volume de alertas pode ser menor, mas os alertas recebidos serão precisos e relevantes. +Since {% data variables.product.prodname_dependabot %} uses curated data in the {% data variables.product.prodname_advisory_database %}, the volume of alerts may be lower, but the alerts you do receive will be accurate and relevant. {% ifversion fpt or ghec %} -## Cada dependência não segura gera um alerta separado? +## Does each insecure dependency generate a separate alert? -Quando uma dependência tem várias vulnerabilidades, gera-se um alerta para cada vulnerabilidade no nível da consultoria mais manifesto. +When a dependency has multiple vulnerabilities, an alert is generated for each vulnerability at the level of advisory plus manifest. -![Captura de tela da aba de {% data variables.product.prodname_dependabot_alerts %} que mostra dois alertas do mesmo pacote com manifestos diferentes.](/assets/images/help/repository/dependabot-alerts-view.png) +![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing two alerts from the same package with different manifests.](/assets/images/help/repository/dependabot-alerts-view.png) -O legado de {% data variables.product.prodname_dependabot_alerts %} foi agrupado em um único alerta agregado com todas as vulnerabilidades para a mesma dependência. Se você acessar um link para um alerta de legadode {% data variables.product.prodname_dependabot %}, você será redirecionado para a aba de {% data variables.product.prodname_dependabot_alerts %} filtrada para exibir vulnerabilidades para esse pacote e manifesto dependente. +Legacy {% data variables.product.prodname_dependabot_alerts %} were grouped into a single aggregated alert with all the vulnerabilities for the same dependency. If you navigate to a link to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to the {% data variables.product.prodname_dependabot_alerts %} tab filtered to display vulnerabilities for that dependent package and manifest. -![Captura de tela da aba {% data variables.product.prodname_dependabot_alerts %} que mostra os alertas filtrados da navegação até um alerta de legado de {% data variables.product.prodname_dependabot %}.](/assets/images/help/repository/legacy-dependabot-alerts-view.png) +![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing the filtered alerts from navigating to a legacy {% data variables.product.prodname_dependabot %} alert.](/assets/images/help/repository/legacy-dependabot-alerts-view.png) -A contagem de {% data variables.product.prodname_dependabot_alerts %} em {% data variables.product.prodname_dotcom %} mostra um total para o número de alertas, que é o número de vulnerabilidades, não o número de dependências. +The {% data variables.product.prodname_dependabot_alerts %} count in {% data variables.product.prodname_dotcom %} shows a total for the number of alerts, which is the number of vulnerabilities, not the number of dependencies. -**Verificação**: se houver uma discrepância nos totais que você está vendo, verifique se não está comparando números de alertas com números de dependências. Também verifique se você está visualizando todos os alertas e não um subconjunto de alertas filtrados. +**Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with dependency numbers. Also check that you are viewing all alerts and not a subset of filtered alerts. {% endif %} {% ifversion fpt or ghec or ghes > 3.2 %} -## O Dependabot pode ignorar dependências específicas? +## Can Dependabot ignore specific dependencies? -Você pode configurar o {% data variables.product.prodname_dependabot %} para ignorar dependências específicas no arquivo de configuração, o que impedirá atualizações de segurança e de versão para essas dependências. Se você quiser usar apenas atualizações de segurança, substitua o comportamento padrão usando um arquivo de configuração. Para obter mais informações, confira "[Como substituir o comportamento padrão com um arquivo de configuração](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates#overriding-the-default-behavior-with-a-configuration-file)" para impedir que as atualizações de versão sejam ativadas. Para obter informações de como ignorar dependências, confira "[`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore)". {% endif %} +You can configure {% data variables.product.prodname_dependabot %} to ignore specific dependencies in the configuration file, which will prevent security and version updates for those dependencies. If you only wish to use security updates, you will need to override the default behavior with a configuration file. For more information, see "[Overriding the default behavior with a configuration file](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates#overriding-the-default-behavior-with-a-configuration-file)" to prevent version updates from being activated. For information about ignoring dependencies, see "[`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore)." +{% endif %} -## Leitura adicional +## Further reading -- "[Sobre os {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" -- "[Como ver e atualizar {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" -- "[Como gerenciar as configurações de segurança e de análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" -- "[Solução de problemas do grafo de dependência](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)"{% ifversion fpt or ghec or ghes > 3.2 %} -- "[Solução de problemas de erros do {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} +- "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" +- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" +- "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)"{% ifversion fpt or ghec or ghes > 3.2 %} +- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} diff --git a/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md b/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md index ab943e736a..e00a81e612 100644 --- a/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md +++ b/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md @@ -1,6 +1,6 @@ --- -title: Como proteger sua organização -intro: 'Você pode usar uma série de funcionalidades de {% data variables.product.prodname_dotcom %} para ajudar a manter a sua organização protegida.' +title: Securing your organization +intro: 'You can use a number of {% data variables.product.prodname_dotcom %} features to help keep your organization secure.' permissions: Organization owners can configure organization security settings. versions: fpt: '*' @@ -14,123 +14,124 @@ topics: - Vulnerabilities - Advanced Security shortTitle: Secure your organization -ms.openlocfilehash: 5ffc3393e751e4b0f24d9a59e644af7a3200f460 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147526835' --- -## Introdução -Este guia mostra como configurar os recursos de segurança de uma organização. As necessidades de segurança da sua organização são únicas e pode ser que você não precise habilitar todas as funcionalidades de segurança. Para obter mais informações, confira "[Recursos de segurança do {% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)". + +## Introduction +This guide shows you how to configure security features for an organization. Your organization's security needs are unique and you may not need to enable every security feature. For more information, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)." {% data reusables.advanced-security.security-feature-availability %} -## Gerenciando o acesso à sua organização +## Managing access to your organization -Você pode usar as funções para controlar as ações que as pessoas podem tomar na sua organização. {% ifversion security-managers %}Por exemplo, você pode atribuir a função de gerente de segurança a uma equipe para dar a ela a capacidade de gerenciar as configurações de segurança em toda a organização, bem como o acesso de leitura em todos os repositórios.{% endif %} Para obter mais informações, confira "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)". +You can use roles to control what actions people can take in your organization. {% ifversion security-managers %}For example, you can assign the security manager role to a team to give them the ability to manage security settings across your organization, as well as read access to all repositories.{% endif %} For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." {% ifversion fpt or ghes or ghec %} -## Criando uma política de segurança padrão +## Creating a default security policy -Você pode criar uma política de segurança padrão que será exibida em qualquer repositório público da organização que não tenha sua própria política de segurança. Para obter mais informações, confira "[Como criar um arquivo padrão de integridade da comunidade](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)". +You can create a default security policy that will display in any of your organization's public repositories that do not have their own security policy. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." {% endif %} -## Gerenciar {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependências +## Managing {% data variables.product.prodname_dependabot_alerts %} and the dependency graph -{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detecta vulnerabilidades em repositórios públicos e exibe o gráfico de dependências. Você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} para todos os repositórios públicos pertencentes à sua organização. Você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependência de todos os repositórios privados da sua organização. +{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and displays the dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all public repositories owned by your organization. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all private repositories owned by your organization. -1. Clique na foto do seu perfil e clique em **Organizações**. -2. Clique em **Configurações** ao lado da sua organização. -3. Clique em **Segurança e análise**. -4. Clique em **Habilitar tudo** ou em **Desabilitar tudo** ao lado do recurso que deseja gerenciar. -5. Opcionalmente, selecione **Habilitar automaticamente para novos repositórios**. +1. Click your profile photo, then click **Organizations**. +2. Click **Settings** next to your organization. +3. Click **Security & analysis**. +4. Click **Enable all** or **Disable all** next to the feature that you want to manage. +5. Optionally, select **Automatically enable for new repositories**. {% endif %} -{% data reusables.dependabot.dependabot-alerts-beta %} {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} +{% data reusables.dependabot.dependabot-alerts-beta %} +{% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} -Para obter mais informações, confira "[Sobre os {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)", "[Como explorar as dependências de um repositório](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" e "[Como gerenciar as configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". +For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)," "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)," and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -## Gerenciando revisão de dependências +## Managing dependency review -A revisão de dependências é um recurso de {% data variables.product.prodname_advanced_security %} que permite visualizar alterações de dependência em pull requests antes de serem mesclados nos seus repositórios. Para obter mais informações, confira "[Sobre a revisão de dependência](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)". +Dependency review is an {% data variables.product.prodname_advanced_security %} feature that lets you visualize dependency changes in pull requests before they are merged into your repositories. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)." -{% ifversion fpt or ghec %}A revisão de Dependência já está habilitada para todos os repositórios públicos. {% ifversion fpt %}As organizações que usam {% data variables.product.prodname_ghe_cloud %} com {% data variables.product.prodname_advanced_security %} podem habilitar a revisão de dependências adicionalmente para repositórios privados e internos. Para obter mais informações, confira a [documentação do {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/code-security/getting-started/securing-your-organization#managing-dependency-review). {% endif %}{% endif %}{% ifversion ghec %}Para repositórios privados e internos pertencentes a uma organização, você pode habilitar a revisão de dependência, habilitando o gráfico de dependências e habilitando {% data variables.product.prodname_advanced_security %} (veja abaixo). {% elsif ghes or ghae %}A revisão de dependência está disponível quando o gráfico de dependências estiver habilitado para {% data variables.product.product_location %} e você habilitar {% data variables.product.prodname_advanced_security %} para a organização (veja abaixo).{% endif %} +{% ifversion fpt or ghec %}Dependency review is already enabled for all public repositories. {% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable dependency review for private and internal repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-organization#managing-dependency-review). {% endif %}{% endif %}{% ifversion ghec %}For private and internal repositories that are owned by an organization, you can enable dependency review by enabling the dependency graph and enabling {% data variables.product.prodname_advanced_security %} (see below). +{% elsif ghes or ghae %}Dependency review is available when dependency graph is enabled for {% data variables.location.product_location %} and you enable {% data variables.product.prodname_advanced_security %} for the organization (see below).{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %} -## Gerenciar {% data variables.product.prodname_dependabot_security_updates %} +## Managing {% data variables.product.prodname_dependabot_security_updates %} -Para qualquer repositório que usar {% data variables.product.prodname_dependabot_alerts %}, você pode habilitar {% data variables.product.prodname_dependabot_security_updates %} para abrir pull requests com atualizações de segurança quando forem detectadas vulnerabilidades. Você também pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_security_updates %} para todos os repositórios da sua organização. +For any repository that uses {% data variables.product.prodname_dependabot_alerts %}, you can enable {% data variables.product.prodname_dependabot_security_updates %} to raise pull requests with security updates when vulnerabilities are detected. You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories across your organization. -1. Clique na foto do seu perfil e clique em **Organizações**. -2. Clique em **Configurações** ao lado da sua organização. -3. Clique em **Segurança e análise**. -4. Clique em **Habilitar tudo** ou em **Desabilitar tudo** ao lado das {% data variables.product.prodname_dependabot_security_updates %}. -5. Opcionalmente, selecione **Habilitar automaticamente para novos repositórios**. +1. Click your profile photo, then click **Organizations**. +2. Click **Settings** next to your organization. +3. Click **Security & analysis**. +4. Click **Enable all** or **Disable all** next to {% data variables.product.prodname_dependabot_security_updates %}. +5. Optionally, select **Automatically enable for new repositories**. -Para obter mais informações, confira "[Sobre as {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-dependabot-security-updates)" e "[Como gerenciar as configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". +For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-dependabot-security-updates)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -## Gerenciar {% data variables.product.prodname_dependabot_version_updates %} +## Managing {% data variables.product.prodname_dependabot_version_updates %} -Você pode habilitar {% data variables.product.prodname_dependabot %} para aumentar automaticamente os pull requests para manter suas dependências atualizadas. Para obter mais informações, confira "[Sobre as {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates)". +You can enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates)." -Para habilitar as {% data variables.product.prodname_dependabot_version_updates %}, crie um arquivo de configuração *dependabot.yml*. Para obter mais informações, confira "[Como configurar as atualizações de versão do {% data variables.product.prodname_dependabot %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)". +To enable {% data variables.product.prodname_dependabot_version_updates %}, you must create a *dependabot.yml* configuration file. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)." {% endif %} {% ifversion ghes or ghae or ghec %} -## Gerenciar {% data variables.product.prodname_GH_advanced_security %} +## Managing {% data variables.product.prodname_GH_advanced_security %} -{% ifversion ghes or ghec %} Se a sua {% ifversion ghec %}organização pertencer a uma empresa que {% else %}empresa{% endif %} tem uma licença do {% data variables.product.prodname_advanced_security %}, você pode habilitar ou desabilitar recursos do {% data variables.product.prodname_advanced_security %}. -{% elsif ghae %} Você pode habilitar ou desabilitar recursos do {% data variables.product.prodname_advanced_security %}. +{% ifversion ghes or ghec %} +If your {% ifversion ghec %}organization is owned by an enterprise that{% else %}enterprise{% endif %} has an {% data variables.product.prodname_advanced_security %} license, you can enable or disable {% data variables.product.prodname_advanced_security %} features. +{% elsif ghae %} +You can enable or disable {% data variables.product.prodname_advanced_security %} features. {% endif %} -1. Clique na foto do seu perfil e clique em **Organizações**. -2. Clique em **Configurações** ao lado da sua organização. -3. Clique em **Segurança e análise**. -4. Clique em **Habilitar tudo** ou em **Desabilitar tudo** ao lado do {% data variables.product.prodname_GH_advanced_security %}. -5. Opcionalmente, selecione **Habilitar automaticamente para novos repositórios privados**. +1. Click your profile photo, then click **Organizations**. +2. Click **Settings** next to your organization. +3. Click **Security & analysis**. +4. Click **Enable all** or **Disable all** next to {% data variables.product.prodname_GH_advanced_security %}. +5. Optionally, select **Automatically enable for new private repositories**. -Para obter mais informações, confira "[Sobre o {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)" e "[Como gerenciar as configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". +For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% endif %} -## Configurar o {% data variables.product.prodname_secret_scanning %} +## Configuring {% data variables.product.prodname_secret_scanning %} -{% data variables.product.prodname_secret_scanning_caps %} é um recurso de {% data variables.product.prodname_advanced_security %} que digitaliza repositórios com relação aos segredos que são armazenados de forma insegura. +{% data variables.product.prodname_secret_scanning_caps %} is an {% data variables.product.prodname_advanced_security %} feature that scans repositories for secrets that are insecurely stored. -{% ifversion fpt or ghec %}{% data variables.product.prodname_secret_scanning_caps %} já está habilitado para todos os repositórios públicos. As organizações que usam o {% data variables.product.prodname_ghe_cloud %} com o {% data variables.product.prodname_advanced_security %} também podem habilitar a {% data variables.product.prodname_secret_scanning %} em repositórios privados e internos.{% endif %} {% ifversion fpt %}Para obter mais informações, confira a [documentação do {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/code-security/getting-started/securing-your-organization#configuring-secret-scanning). {% endif %} +{% ifversion fpt or ghec %}{% data variables.product.prodname_secret_scanning_caps %} is already enabled for all public repositories. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable {% data variables.product.prodname_secret_scanning %} for private and internal repositories.{% endif %} {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-organization#configuring-secret-scanning). {% endif %} -{% ifversion ghes or ghae %}{% data variables.product.prodname_secret_scanning_caps %} está disponível se a sua empresa usa {% data variables.product.prodname_advanced_security %}.{% endif %} +{% ifversion ghes or ghae %}{% data variables.product.prodname_secret_scanning_caps %} is available if your enterprise uses {% data variables.product.prodname_advanced_security %}.{% endif %} -{% ifversion not fpt %} Você pode habilitar ou desabilitar a {% data variables.product.prodname_secret_scanning %} para todos os repositórios na sua organização que tenham o {% data variables.product.prodname_advanced_security %} habilitado. +{% ifversion not fpt %} +You can enable or disable {% data variables.product.prodname_secret_scanning %} for all repositories across your organization that have {% data variables.product.prodname_advanced_security %} enabled. -1. Clique na foto do seu perfil e clique em **Organizações**. -2. Clique em **Configurações** ao lado da sua organização. -3. Clique em **Segurança e análise**. -4. Clique em **Habilitar tudo** ou **Desabilitar tudo** ao lado da {% data variables.product.prodname_secret_scanning_caps %} (somente os repositórios do {% data variables.product.prodname_GH_advanced_security %}). -5. Opcionalmente, selecione **Habilitar automaticamente para repositórios privados adicionados ao {% data variables.product.prodname_advanced_security %}** . +1. Click your profile photo, then click **Organizations**. +2. Click **Settings** next to your organization. +3. Click **Security & analysis**. +4. Click **Enable all** or **Disable all** next to {% data variables.product.prodname_secret_scanning_caps %} ({% data variables.product.prodname_GH_advanced_security %} repositories only). +5. Optionally, select **Automatically enable for private repositories added to {% data variables.product.prodname_advanced_security %}**. -Para obter mais informações, confira "[Como gerenciar as configurações de segurança e de análise da sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". +For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% endif %} -## Como configurar a {% data variables.product.prodname_code_scanning %} +## Configuring {% data variables.product.prodname_code_scanning %} -{% data variables.product.prodname_code_scanning_capc %} é um recurso de {% data variables.product.prodname_advanced_security %} que digitaliza código para vulnerabilidades e erros de segurança +{% data variables.product.prodname_code_scanning_capc %} is an {% data variables.product.prodname_advanced_security %} feature that scans code for security vulnerabilities and errors. -{% ifversion fpt or ghec %}{% data variables.product.prodname_code_scanning_capc %} já disponível para todos os repositórios públicos. As organizações que usam {% data variables.product.prodname_ghe_cloud %} com {% data variables.product.prodname_advanced_security %} podem adicionalmente usar {% data variables.product.prodname_code_scanning %} para repositórios privados ou internos.{% else %}{% data variables.product.prodname_code_scanning_capc %} está disponível se sua empresa usar {% data variables.product.prodname_advanced_security %}.{% endif %} +{% ifversion fpt or ghec %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally use {% data variables.product.prodname_code_scanning %} for private and internal repositories.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if your enterprise uses {% data variables.product.prodname_advanced_security %}.{% endif %} -{% data variables.product.prodname_code_scanning_capc %} está configurado no nível do repositório. Para obter mais informações, confira "[Como configurar a {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)". +{% data variables.product.prodname_code_scanning_capc %} is configured at the repository level. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)." -## Próximas etapas -Você pode visualizar e gerenciar alertas de funcionalidades de segurança para resolver dependências e vulnerabilidades no seu código. Para saber mais, confira {% ifversion fpt or ghes or ghec %} "[Como exibir e atualizar {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Como gerenciar solicitações de pull para atualizações de dependência](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Como gerenciar a {% data variables.product.prodname_code_scanning %} do repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)" e "[Como gerenciar os alertas da {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)". +## Next steps +You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." -{% ifversion fpt or ghec %}Se você tiver uma vulnerabilidade de segurança, você poderá criar uma consultoria de segurança para discutir em privado e corrigir a vulnerabilidade. Para obter mais informações, confira "[Sobre as {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" e "[Como criar uma consultoria de segurança](/code-security/security-advisories/creating-a-security-advisory)". +{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)." {% endif %} -{% ifversion ghes or ghec or ghae %}Você{% elsif fpt %}As organizações que usam o {% data variables.product.prodname_ghe_cloud %}{% endif %} podem ver, filtrar e classificar os alertas de segurança de repositórios pertencentes à organização {% ifversion ghes or ghec or ghae %}sua{% elsif fpt %}delas{% endif %} na visão geral de segurança. Para obter mais informações, confira{% ifversion ghes or ghec or ghae %} "[Sobre a visão geral de segurança](/code-security/security-overview/about-the-security-overview)".{% elsif fpt %} "[Sobre a visão geral de segurança](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" na documentação do {% data variables.product.prodname_ghe_cloud %}.{% endif %} +{% ifversion ghes or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes or ghec or ghae %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %} {% ifversion ghec %} -## Leitura adicional +## Further reading -"[Como acessar relatórios de conformidade da sua organização](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization)" {% endif %} +"[Accessing compliance reports for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization)" +{% endif %} diff --git a/translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md b/translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md index 519e8b2ba2..b9dce9457c 100644 --- a/translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md +++ b/translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md @@ -74,6 +74,10 @@ If you're a repository administrator you can enable {% data variables.product.pr {% ifversion ghes or ghae or ghec %}You can also define custom {% data variables.product.prodname_secret_scanning %} patterns for a repository, organization, or enterprise. For more information, see "[Defining custom patterns for {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)." {% endif %} + +{% ifversion secret-scanning-ghas-store-tokens %} +{% data variables.product.company_short %} stores detected secrets using symmetric encryption, both in transit and at rest.{% endif %}{% ifversion ghes > 3.7 %} To rotate the encryption keys used for storing the detected secrets, you can contact {% data variables.contact.contact_ent_support %}.{% endif %} + ### About {% data variables.product.prodname_secret_scanning %} alerts When you enable {% data variables.product.prodname_secret_scanning %} for a repository or push commits to a repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of those commits for secrets that match patterns defined by service providers{% ifversion ghes or ghae or ghec %} and any custom patterns defined in your enterprise, organization, or repository{% endif %}. {% ifversion secret-scanning-backfills %}{% data variables.product.prodname_dotcom %} also periodically runs a scan of all historical content in repositories with {% data variables.product.prodname_secret_scanning %} enabled.{% endif%} diff --git a/translations/pt-BR/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md b/translations/pt-BR/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md index 188283b50a..72be0fcd50 100644 --- a/translations/pt-BR/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md +++ b/translations/pt-BR/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md @@ -68,7 +68,7 @@ shortTitle: Manage secret alerts Once a secret has been committed to a repository, you should consider the secret compromised. {% data variables.product.prodname_dotcom %} recommends the following actions for compromised secrets: -- For a compromised {% data variables.product.prodname_dotcom %} personal access token, delete the compromised token, create a new token, and update any services that use the old token. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)." +- For a compromised {% data variables.product.prodname_dotcom %} {% data variables.product.pat_generic %}, delete the compromised token, create a new token, and update any services that use the old token. For more information, see "[Creating a {% data variables.product.pat_generic %} for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)." - For all other secrets, first verify that the secret committed to {% data variables.product.product_name %} is valid. If so, create a new secret, update any services that use the old secret, and then delete the old secret. {% ifversion ghec %} diff --git a/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md b/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md index 1d531390f5..69e55a8adc 100644 --- a/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md +++ b/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md @@ -43,7 +43,7 @@ In the security overview, you can view, sort, and filter alerts to understand th {% ifversion security-overview-views %} -In the security overview, there are dedicated views for each type of security alert, such as Dependabot, code scanning, and secret scanning alerts. You can use these views to limit your analysis to a specific set of alerts, and narrow the results further with a range of filters specific to each view. For example, in the secret scanning alert view, you can use the `Secret type` filter to view only secret scanning alerts for a specific secret, like a GitHub Personal Access Token. At the repository level, you can use the security overview to assess the specific repository's current security status, and configure any additional security features not yet in use on the repository. +In the security overview, there are dedicated views for each type of security alert, such as Dependabot, code scanning, and secret scanning alerts. You can use these views to limit your analysis to a specific set of alerts, and narrow the results further with a range of filters specific to each view. For example, in the secret scanning alert view, you can use the `Secret type` filter to view only secret scanning alerts for a specific secret, like a GitHub {% data variables.product.pat_generic %}. At the repository level, you can use the security overview to assess the specific repository's current security status, and configure any additional security features not yet in use on the repository. {% endif %} diff --git a/translations/pt-BR/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md b/translations/pt-BR/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md index c8267e27a6..d16b736502 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md @@ -1,8 +1,8 @@ --- -title: Melhores práticas para proteger contas +title: Best practices for securing accounts shortTitle: Securing accounts allowTitleToDifferFromFilename: true -intro: Orientação sobre como proteger as contas com acesso à cadeia de suprimentos de software. +intro: Guidance on how to protect accounts with access to your software supply chain. versions: fpt: '*' ghec: '*' @@ -15,117 +15,123 @@ topics: - SSH - Security - Accounts -ms.openlocfilehash: 4225b80d139462fd64e440947c1eba9adb817294 -ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147883406' --- -## Sobre este guia +## About this guide -Este guia descreve as mudanças de maior impacto que você pode fazer para aumentar a segurança da conta. Cada seção descreve uma alteração que você pode fazer em seus processos para melhorar a segurança. As mudanças de maior impacto estão listadas primeiro. +This guide describes the highest impact changes you can make to increase account security. Each section outlines a change you can make to your processes to improve the security. The highest impact changes are listed first. -## Qual o risco? +## What's the risk? -A segurança da conta é fundamental para a segurança da sua cadeia de suprimento. Se um invasor conseguir tomar a sua conta em {% data variables.product.product_name %}, ele poderá fazer alterações maliciosas no seu código ou no processo de compilação. Dessa forma, seu primeiro objetivo deve ser dificultar que alguém tome a sua conta e as contas de outros usuários de {% ifversion ghes %}{% else %}integrantes{% endif %} da {% ifversion fpt %}sua organização{% elsif ghec or ghae %}sua organização ou empresa{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. +Account security is fundamental to the security of your supply chain. If an attacker can take over your account on {% data variables.product.product_name %}, they can then make malicious changes to your code or build process. So your first goal should be to make it difficult for someone to take over your account and the accounts of other {% ifversion ghes %}users{% else %}members{% endif %} of {% ifversion fpt %}your organization{% elsif ghec or ghae %}your organization or enterprise{% elsif ghes %}{% data variables.location.product_location %}{% endif %}. {% ifversion ghec or ghes %} -## Centralizar autenticação +## Centralize authentication {% endif %} -{% ifversion ghec %} Se você é proprietário de uma empresa ou uma organização, configure a autenticação centralizada com o SAML. Embora você possa adicionar ou remover integrantes manualmente, é mais simples e mais seguro configurar um logon único (SSO) e SCIM entre {% data variables.product.product_name %} e seu provedor de identidade (IdP) SAML. Isso também simplifica o processo de autenticação para todos os integrantes da sua empresa. +{% ifversion ghec %} +If you're an enterprise or organization owner, you can configure centralized authentication with SAML. While you can add or remove members manually, it's simpler and more secure to set up single sign-on (SSO) and SCIM between {% data variables.product.product_name %} and your SAML identity provider (IdP). This also simplifies the authentication process for all members of your enterprise. -Você pode configurar a autenticação SAML para uma conta corporativa ou da organização. Com o SAML, você pode conceder acesso às contas pessoais dos integrantes da sua empresa ou organização no {% data variables.product.product_location %} por meio do seu IdP, ou você pode criar e controlar as contas que pertencem à sua empresa usando {% data variables.product.prodname_emus %}. Para obter mais informações, confira "[Sobre a autenticação em sua empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)". +You can configure SAML authentication for an enterprise or organization account. With SAML, you can grant access to the personal accounts of members of your enterprise or organization on {% data variables.location.product_location %} through your IdP, or you can create and control the accounts that belong to your enterprise by using {% data variables.product.prodname_emus %}. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)." -Depois de configurar a autenticação do SAML, quando os integrantes solicitarem acesso aos seus recursos, eles serão direcionados para o seu fluxo de SSO para garantir que sejam reconhecidos pelo seu IdP. Se não forem reconhecidos, o seu pedido será recusado. +After you configure SAML authentication, when members request access to your resources, they'll be directed to your SSO flow to ensure they are still recognized by your IdP. If they are unrecognized, their request is declined. -Alguns IdPs são compatíveis com um protocolo denominado SCIM, que pode prover ou desprovisionar automaticamente o acesso em {% data variables.product.product_name %} quando você fizer alterações no seu IdP. Com o SCIM, você pode simplificar a administração à medida que a sua equipe cresce, e você pode revogar rapidamente o acesso às contas. O SCIM está disponível para organizações individuais em {% data variables.product.product_name %}, ou para empresas que usam {% data variables.product.prodname_emus %}. Para obter mais informações, confira "[Sobre o SCIM para organizações](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)". +Some IdPs support a protocol called SCIM, which can automatically provision or deprovision access on {% data variables.product.product_name %} when you make changes on your IdP. With SCIM, you can simplify administration as your team grows, and you can quickly revoke access to accounts. SCIM is available for individual organizations on {% data variables.product.product_name %}, or for enterprises that use {% data variables.product.prodname_emus %}. For more information, see "[About SCIM for organizations](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)." {% endif %} -{% ifversion ghes %} Se você é o administrador do site do {% data variables.product.product_location %}, simplifique a experiência de logon para os usuários escolhendo um método de autenticação que se conecta ao seu IdP (provedor de identidade) existente, como o CAS, o SAML ou o LDAP. Isso significa que eles não precisam mais lembrar de uma senha adicional para {% data variables.product.prodname_dotcom %}. +{% ifversion ghes %} +If you're the site administrator for {% data variables.location.product_location %}, you can simplify the login experience for users by choosing an authentication method that connects with your existing identity provider (IdP), like CAS, SAML, or LDAP. This means that they no longer need to remember an extra password for {% data variables.product.prodname_dotcom %}. -Alguns métodos de autenticação também são compatíveis com a comunicação de informações adicionais para {% data variables.product.product_name %}, por exemplo, de quais grupos o usuário é integrante ou sincronizando chaves criptográficas para o usuário. Esta é uma excelente maneira de simplificar a sua administração à medida que a sua organização cresce. +Some authentication methods also support communicating additional information to {% data variables.product.product_name %}, for example, what groups the user is a member of, or synchronizing cryptographic keys for the user. This is a great way to simplify your administration as your organization grows. -Para obter mais informações sobre os métodos de autenticação disponíveis para {% data variables.product.product_name %}, confira "[Sobre a autenticação em sua empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)." +For more information about the authentication methods available for {% data variables.product.product_name %}, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)." {% endif %} -## Configurar autenticação de dois fatores +## Configure two-factor authentication -A melhor maneira de melhorar a segurança da {% ifversion fpt %}sua conta pessoal{% elsif ghes %}sua conta pessoal ou {% data variables.product.product_location %}{% elsif ghec %}suas contas{% elsif ghae %}sua empresa em {% data variables.product.product_name %}{% endif %} é configurar a autenticação de dois fatores (2FA){% ifversion ghae %} no seu provedor de identidade SAML (IdP){% endif %}. As senhas por si só podem ser comprometidas por serem adivinhadas, por serem reutilizadas em outro local que foi comprometido, ou por engenharia social, como phishing. A 2FA dificulta muito mais o comprometimento das suas contas, mesmo que um invasor tenha sua senha. +The best way to improve the security of {% ifversion fpt %}your personal account{% elsif ghes %}your personal account or {% data variables.location.product_location %}{% elsif ghec %}your accounts{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %} is to configure two-factor authentication (2FA){% ifversion ghae %} on your SAML identity provider (IdP){% endif %}. Passwords by themselves can be compromised by being guessable, by being reused on another site that's been compromised, or by social engineering, like phishing. 2FA makes it much more difficult for your accounts to be compromised, even if an attacker has your password. {% ifversion not ghae %} -{% ifversion ghec %} Se você é o proprietário de uma empresa, configure uma política que exija a 2FA para todas as organizações pertencentes à sua empresa. +{% ifversion ghec %} +If you're an enterprise owner, you may be able to configure a policy to require 2FA for all organizations owned by your enterprise. {% endif %} -{% ifversion ghes %} Se você é o administrador do site do {% data variables.product.product_location %}, talvez possa configurar a 2FA para todos os usuários da sua instância. A disponibilidade de 2FA no {% data variables.product.product_name %} depende do método de autenticação que você usa. Para obter mais informações, confira "[Centralizar a autenticação do usuário](#centralize-user-authentication)". +{% ifversion ghes %} +If you're the site administrator for {% data variables.location.product_location %}, you may be able to configure 2FA for all users of your instance. The availability of 2FA on {% data variables.product.product_name %} depends on the authentication method that you use. For more information, see "[Centralize user authentication](#centralize-user-authentication)." {% endif %} -Se você for um proprietário da organização, {% ifversion fpt %}pode{% else %}poderá{% endif %} exigir que todos os integrantes da organização habilitem a 2FA. +If you're an organization owner, then you {% ifversion fpt %}can{% else %}may be able to{% endif %} require that all members of the organization enable 2FA. {% ifversion ghec or ghes %} -### Configure sua conta corporativa +### Configure your enterprise account -Os proprietários da empresa podem exigir a autenticação 2FA para todos os {% ifversion ghes %}usuários de{% elsif ghec %}integrantes da{% endif %} a instância {% ifversion ghes %}{% elsif ghec %}empresa{% endif %}. A disponibilidade das políticas de 2FA em {% data variables.product.product_name %} depende de como {% ifversion ghes %}usuários{% else %}integrantes{% endif %} efetuam a autenticação para acessar sua {% ifversion ghes %}instância{% elsif ghec %}recursos da empresa{% endif %}. +Enterprise owners may be able to require 2FA for all {% ifversion ghes %}users on{% elsif ghec %}members of{% endif %} the {% ifversion ghes %}instance{% elsif ghec %}enterprise{% endif %}. The availability of 2FA policies on {% data variables.product.product_name %} depends on how {% ifversion ghes %}users{% else %}members{% endif %} authenticate to access your {% ifversion ghes %}instance{% elsif ghec %}enterprise's resources{% endif %}. {% ifversion ghes %} -- Se você entrar no {% data variables.product.product_location %} por meio de um IdP externo usando o SSO do CAS ou do SAML, {% elsif ghec %} se a sua empresa usar o {% data variables.product.prodname_emus %} ou a autenticação SAML for imposta para sua empresa, você {%- endif %} não poderá configurar a 2FA no {% data variables.product.product_name %}. Alguém com acesso administrativo ao seu IdP deve configurar a autenticação 2FA para o IdP. +- If you sign into {% data variables.location.product_location %} through an external IdP using CAS or SAML SSO, you +{% elsif ghec %} +If your enterprise uses {% data variables.product.prodname_emus %} or SAML authentication is enforced for your enterprise, you +{%- endif %} cannot configure 2FA on {% data variables.product.product_name %}. Someone with administrative access to your IdP must configure 2FA for the IdP. {% ifversion ghes %} -- Se você entrar em {% data variables.product.product_location %} por meio de um diretório LDAP externo, você poderá exigir a autenticação 2FA para sua empresa em {% data variables.product.product_name %}. Se você permitir a autenticação integrada para usuários fora do seu diretório, os usuários individuais poderão habilitar a autenticação 2FA, mas você não poderá exigir a autenticação 2FA para sua empresa. +- If you sign into {% data variables.location.product_location %} through an external LDAP directory, you can require 2FA for your enterprise on {% data variables.product.product_name %}. If you allow built-in authentication for users outside of your directory, individual users can enable 2FA, but you cannot require 2FA for your enterprise. {% endif %} -Para obter mais informações, confira {% ifversion ghec %}"[Sobre o gerenciamento de identidades e acesso para sua empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)" e {% endif %}"[Como impor políticas para configurações de segurança na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#requiring-two-factor-authentication-for-organizations-in-your-enterprise)". +For more information, see {% ifversion ghec %}"[About identity and access management for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)" and {% endif %}"[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#requiring-two-factor-authentication-for-organizations-in-your-enterprise)." {% endif %} -### Configure a sua conta pessoal +### Configure your personal account -{% ifversion ghec or ghes %} {% note %} +{% ifversion ghec or ghes %} +{% note %} -**Observação**: dependendo do método de autenticação que {% ifversion ghec %}o proprietário de uma empresa{% elsif ghes %}um administrador do site{% endif %} tenha configurado para {% ifversion ghec %}sua empresa na {% endif %}{% data variables.product.product_location %}, talvez você não consiga habilitar a autenticação 2FA na sua conta pessoal. +**Note**: Depending on the authentication method that {% ifversion ghec %}an enterprise owner{% elsif ghes %}a site administrator{% endif %} has configured for {% ifversion ghec %}your enterprise on {% endif %}{% data variables.location.product_location %}, you may not be able to enable 2FA for your personal account. -{% endnote %} {% endif %} +{% endnote %} +{% endif %} -{% data variables.product.product_name %} é compatível com várias opções para 2FA e embora qualquer um seja melhor do que nada, a opção mais segura é WebAuthn. A WebAuthn requer uma chave de segurança de hardware ou um dispositivo que o suporte por meio de coisas como Windows Hello ou Mac TouchID. É possível, apesar de ser difícil, fazer phish de outras formas de 2FA (por exemplo, quando alguém pede para ler a sua senha de um único dígito). No entanto, o WebAuthn não é passível de phishing, porque o escopo de domínio está incorporado no protocolo, o que impede que credenciais de um site representando uma página de login sejam usadas em {% data variables.product.product_name %}. +{% data variables.product.product_name %} supports several options for 2FA, and while any of them is better than nothing, the most secure option is WebAuthn. WebAuthn requires either a hardware security key or a device that supports it through things like Windows Hello or Mac TouchID. It's possible, although difficult, to phish other forms of 2FA (for example, someone asking you to read them your 6 digit one-time password). However WebAuthn isn't phishable, because domain scoping is built into the protocol, which prevents credentials from a website impersonating a login page from being used on {% data variables.product.product_name %}. -Ao definir a autenticação de 2FA, você deve sempre fazer o download dos códigos de recuperação e definir mais de um fator. Isso garante que o acesso à sua conta não depende de um único dispositivo. Para obter mais informações, confira "[Como configurar a autenticação de dois fatores](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)", "[Como configurar métodos de recuperação da autenticação de dois fatores](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods)" e [Chaves de segurança de hardware personalizada com o GitHub](https://thegithubshop.com/products/github-branded-yubikey) na loja do GitHub. +When you set up 2FA, you should always download the recovery codes and set up more than one factor. This ensures that access to your account doesn't depend on a single device. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)," "[Configuring two-factor authentication recovery methods](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods)," and [GitHub Branded hardware security keys](https://thegithubshop.com/products/github-branded-yubikey) in the GitHub shop. -### Configurar a conta da sua organização +### Configure your organization account -{% ifversion ghec or ghes %} {% note %} +{% ifversion ghec or ghes %} +{% note %} -**Observação**: dependendo do método de autenticação que {% ifversion ghec %}o proprietário de uma empresa{% elsif ghes %}um administrador do site{% endif %} tenha configurado para {% ifversion ghec %}sua empresa na {% endif %}{% data variables.product.product_location %}, talvez você não consiga exigir a autenticação 2FA para sua organização. +**Note**: Depending on the authentication method that {% ifversion ghec %}an enterprise owner{% elsif ghes %}a site administrator{% endif %} has configured for {% ifversion ghec %}your enterprise on {% endif %}{% data variables.location.product_location %}, you may not be able to require 2FA for your organization. -{% endnote %} {% endif %} +{% endnote %} +{% endif %} -Se você for proprietário de uma organização, você poderá ver quais usuários não estão habilitados com 2FA, poderá ajudá-los a configurá-la e, em seguida, exigir a autenticação 2FA para sua organização. Para guiar você nesse processo, consulte: +If you're an organization owner, you can see which users don't have 2FA enabled, help them get set up, and then require 2FA for your organization. To guide you through that process, see: -1. "[Como ver se os usuários na sua organização têm a 2FA habilitada](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled)" -2. "[Como se preparar para exigir a autenticação de dois fatores na sua organização](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/preparing-to-require-two-factor-authentication-in-your-organization)" -3. "[Como exigir a autenticação de dois fatores na sua organização](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization)" +1. "[Viewing whether users in your organization have 2FA enabled](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled)" +2. "[Preparing to require two-factor authentication in your organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/preparing-to-require-two-factor-authentication-in-your-organization)" +3. "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization)" {% endif %} -## Conectar a {% data variables.product.product_name %} usando chaves SSH +## Connect to {% data variables.product.product_name %} using SSH keys -Existem outras maneiras de interagir com {% data variables.product.product_name %} além de entrar no site {% ifversion ghae %} por meio do IdP{% endif %}. Muitas pessoas autorizam o código que enviam por push para {% data variables.product.prodname_dotcom %} com uma chave privada SSH. Para obter mais informações, confira "[Sobre o SSH](/authentication/connecting-to-github-with-ssh/about-ssh)". +There are other ways to interact with {% data variables.product.product_name %} beyond signing into the website{% ifversion ghae %} via your IdP{% endif %}. Many people authorize the code they push to {% data variables.product.prodname_dotcom %} with an SSH private key. For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)." -Assim como {% ifversion ghae %}a senha da conta do IdP{% else %}a senha da sua conta{% endif %}, se um invasor conseguir obter sua chave SSH privada, ele poderá representar você e enviar um código malicioso por push a qualquer repositório ao qual você tenha acesso de gravação. Se você armazenar sua chave SSH privada em um disco, é uma boa ideia protegê-la com uma senha. Para obter mais informações, confira "[Como trabalhar com frases secretas de chave SSH](/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases)". +Just like {% ifversion ghae %}the password for your IdP account{% else %}your account password{% endif %}, if an attacker were able to get your SSH private key, they could impersonate you and push malicious code to any repository you have write access for. If you store your SSH private key on a disk drive, it's a good idea to protect it with a passphrase. For more information, see "[Working with SSH key passphrases](/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases)." -Outra opção é gerar chaves SSH em uma chave de segurança de hardware. Você pode usar a mesma chave que você está usando no 2FA. É muito difícil comprometer as chaves de segurança de hardware remotamente, porque a chave SSH privada permanece no hardware e não pode ser acessada diretamente por meio do software. Para obter mais informações, confira "[Como gerar uma nova chave SSH para uma chave de segurança de hardware](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)". +Another option is to generate SSH keys on a hardware security key. You could use the same key you're using for 2FA. Hardware security keys are very difficult to compromise remotely, because the private SSH key remains on the hardware, and is not directly accessible from software. For more information, see "[Generating a new SSH key for a hardware security key](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)." -{% ifversion ghec or ghes or ghae %} As chaves SSH com suporte de hardware são bastante seguras, mas a exigência de hardware pode não funcionar para algumas organizações. Uma abordagem alternativa é usar chaves SSH válidas por um curto período de tempo. Mesmo que a chave privada seja comprometida, ela não poderá ser explorada por muito tempo. Este é o conceito por trás da execução da sua própria autoridade de certificação SSH. Embora essa abordagem fornece a você um grande controle sobre como os usuários efetuam a autenticação e também vem com a responsabilidade da própria manutenção de uma autoridade certificada de SSH. Para obter mais informações, confira "[Sobre as autoridades de certificado SSH](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)". +{% ifversion ghec or ghes or ghae %} +Hardware-backed SSH keys are quite secure, but the hardware requirement might not work for some organizations. An alternative approach is to use SSH keys that are only valid for a short period of time, so even if the private key is compromised it can't be exploited for very long. This is the concept behind running your own SSH certificate authority. While this approach gives you a lot of control over how users authenticate, it also comes with the responsibility of maintaining an SSH certificate authority yourself. For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)." {% endif %} -## Próximas etapas +## Next steps -- "[Como proteger sua cadeia de fornecedores de ponta a ponta](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)" +- "[Securing your end-to-end supply chain](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)" -- "[Melhores práticas para proteger o código na sua cadeia de fornecedores](/code-security/supply-chain-security/end-to-end-supply-chain/securing-code)" +- "[Best practices for securing code in your supply chain](/code-security/supply-chain-security/end-to-end-supply-chain/securing-code)" -- "[Melhores práticas para proteger seu sistema de build](/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds)" +- "[Best practices for securing your build system](/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds)" diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md index c5c6fdf15f..33e8c19950 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md @@ -111,7 +111,7 @@ The term "{% data variables.product.prodname_dependabot %}" encompasses the foll - {% data variables.product.prodname_dependabot %} performs a scan to detect insecure dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when: {% ifversion fpt or ghec %} - A new advisory is added to the {% data variables.product.prodname_advisory_database %}.{% else %} - - New advisory data is synchronized to {% data variables.product.product_location %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %} + - New advisory data is synchronized to {% data variables.location.product_location %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %} - The dependency graph for the repository changes. - {% data variables.product.prodname_dependabot_alerts %} are displayed {% ifversion fpt or ghec or ghes %} on the **Security** tab for the repository and{% endif %} in the repository's dependency graph. The alert includes {% ifversion fpt or ghec or ghes %}a link to the affected file in the project, and {% endif %}information about a fixed version. @@ -164,7 +164,7 @@ Any repository type: {% ifversion ghes or ghae %} - **Dependency graph** and **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. Both features are configured at an enterprise level by the enterprise owner. For more information, see {% ifversion ghes %}"[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)" and {% endif %}"[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." -- **Dependency review**—available when dependency graph is enabled for {% data variables.product.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)." +- **Dependency review**—available when dependency graph is enabled for {% data variables.location.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)." {% endif %} {% ifversion ghes > 3.2 %} - **{% data variables.product.prodname_dependabot_security_updates %}**—not enabled by default. You can enable {% data variables.product.prodname_dependabot_security_updates %} for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)." diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md index 5abdb8b0d4..06bb91f769 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md @@ -38,7 +38,7 @@ Dependency review is included in {% data variables.product.product_name %} for p {% elsif ghes or ghae %} -Dependency review is available when dependency graph is enabled for {% data variables.product.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository.{% ifversion ghes %} For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)."{% endif %} +Dependency review is available when dependency graph is enabled for {% data variables.location.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository.{% ifversion ghes %} For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)."{% endif %} ### Checking if the dependency graph is enabled diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md index f8ef3037ef..40094b5db2 100644 --- a/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md +++ b/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md @@ -30,7 +30,7 @@ If you publish a container image to {% data variables.packages.prodname_ghcr_or_ By default, when you publish a container image to {% data variables.packages.prodname_ghcr_or_npm_registry %}, the image inherits the access setting of the repository from which the image was published. For example, if the repository is public, the image is also public. If the repository is private, the image is also private, but is accessible from the repository. -This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.packages.prodname_ghcr_or_npm_registry %} using a Personal Access Token (PAT). +This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.packages.prodname_ghcr_or_npm_registry %} using a % data variables.product.pat_generic %}. If the **Inherit access from repo** option was not selected when the image was published, you can manually add the repository to the published container image's access controls. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#inheriting-access-for-a-container-image-from-a-repository)." @@ -46,13 +46,13 @@ If you want to allow a subset of an organization's repositories to access a cont ### Publishing a container image from a codespace -Seamless access from a codespace to {% data variables.packages.prodname_ghcr_or_npm_registry %} is limited to pulling container images. If you want to publish a container image from inside a codespace, you must use a personal access token (PAT) with the `write:packages` scope. +Seamless access from a codespace to {% data variables.packages.prodname_ghcr_or_npm_registry %} is limited to pulling container images. If you want to publish a container image from inside a codespace, you must use a {% data variables.product.pat_v1 %} with the `write:packages` scope. We recommend publishing images via {% data variables.product.prodname_actions %}. For more information, see "[Publishing Docker images](/actions/publishing-packages/publishing-docker-images)" and "[Publishing Node.js packages](/actions/publishing-packages/publishing-nodejs-packages)." ## Accessing images stored in other container registries -If you are accessing a container image from a registry that isn't {% data variables.packages.prodname_ghcr_or_npm_registry %}, {% data variables.product.prodname_github_codespaces %} checks for the presence of three secrets, which define the server name, username, and personal access token (PAT) for a container registry. If these secrets are found, {% data variables.product.prodname_github_codespaces %} will make the registry available inside your codespace. +If you are accessing a container image from a registry that isn't {% data variables.packages.prodname_ghcr_or_npm_registry %}, {% data variables.product.prodname_github_codespaces %} checks for the presence of three secrets, which define the server name, username, and {% data variables.product.pat_generic %} for a container registry. If these secrets are found, {% data variables.product.prodname_github_codespaces %} will make the registry available inside your codespace. - `<*>_CONTAINER_REGISTRY_SERVER` - `<*>_CONTAINER_REGISTRY_USER` @@ -71,7 +71,7 @@ For a private image registry in Azure, you could create the following secrets: ``` ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io ACR_CONTAINER_REGISTRY_USER = acr-user-here -ACR_CONTAINER_REGISTRY_PASSWORD = +ACR_CONTAINER_REGISTRY_PASSWORD = ``` For information on common image registries, see "[Common image registry servers](#common-image-registry-servers)." Note that accessing AWS Elastic Container Registry (ECR) is different. diff --git a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md index ea54d820ae..253b3ea97e 100644 --- a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md +++ b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md @@ -1,6 +1,6 @@ --- -title: Gerenciar segredos criptografados para seus codespaces -intro: 'Você pode armazenar informações confidenciais, como tokens, que você deseja acessar nos seus codespaces por meio de variáveis de ambiente.' +title: Managing encrypted secrets for your codespaces +intro: 'You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -15,84 +15,89 @@ topics: - Security - Secret store shortTitle: Encrypted secrets -ms.openlocfilehash: 6951acb82614d35e3394a2af8e58fc8f8442ab3a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147419790' --- -## Sobre os segredos criptografados para os {% data variables.product.prodname_github_codespaces %} -Você pode adicionar segredos criptografados a sua conta pessoal que deseja usar nos seus codespaces. Por exemplo, você pode querer armazenar e acessar as seguintes informações confidenciais como segredos criptografados. + -- Tokens de acesso pessoal para os serviços da nuvem -- Entidades de serviço -- Identificadores da assinatura -- [Credenciais de um registro de imagens privado](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry) -Você pode escolher quais repositórios devem ter acesso a cada segredo. Em seguida, você pode usar o segredo em qualquer código que criar para um repositório que tiver acesso ao segredo. +## About encrypted secrets for {% data variables.product.prodname_github_codespaces %} + +You can add encrypted secrets to your personal account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets. + +- {% data variables.product.pat_generic %}s to cloud services +- Service principals +- Subscription identifiers +- [Credentials for a private image registry](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry) + +You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret. {% data reusables.codespaces.secrets-on-start %} -### Nomeando segredos +### Naming secrets -{% data reusables.codespaces.secrets-naming %} Por exemplo, um segredo criado no nível do repositório deve ter um nome exclusivo nesse repositório. +{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository. {% data reusables.codespaces.secret-precedence %} -### Limites para segredos +### Limits for secrets -Você pode armazenar até 100 segredos para {% data variables.product.prodname_github_codespaces %}. +You can store up to 100 secrets for {% data variables.product.prodname_github_codespaces %}. -Os segredos são limitados a 64 kB. +Secrets are limited to 64 KB in size. -## Adicionar um segredo +## Adding a secret -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.codespaces-tab %} -1. À direita de "Segredos de codespaces", clique em **Novo segredo**. - ![Botão "Novo segredo"](/assets/images/help/settings/codespaces-new-secret-button.png) -1. Em "Nome", digite um nome para seu segredo. - ![Caixa de texto "Nome"](/assets/images/help/settings/codespaces-secret-name-field.png) {% data reusables.user-settings.codespaces-secret-value %} {% data reusables.user-settings.codespaces-secret-repository-access %} -1. Clique em **Adicionar segredo**. +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.codespaces-tab %} +1. To the right of "Codespaces secrets", click **New secret**. + !["New secret" button](/assets/images/help/settings/codespaces-new-secret-button.png) +1. Under "Name", type a name for your secret. + !["Name" text box](/assets/images/help/settings/codespaces-secret-name-field.png) +{% data reusables.user-settings.codespaces-secret-value %} +{% data reusables.user-settings.codespaces-secret-repository-access %} +1. Click **Add secret**. -## Editar um segredo +## Editing a secret -Você pode atualizar o valor de um segredo existente, bem como alterar quais repositórios podem acessar um segredo. +You can update the value of an existing secret, and you can change which repositories can access a secret. -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.codespaces-tab %} -1. Em "Segredos de codespaces", à direita do segredo que você deseja editar, clique em **Atualizar**. - ![Botão "Atualizar"](/assets/images/help/settings/codespaces-secret-update-button.png) -1. Em "Valor", clique em **Inserir um novo valor**. - ![Link "Inserir um novo valor"](/assets/images/help/settings/codespaces-secret-update-value-text.png) {% data reusables.user-settings.codespaces-secret-value %} {% data reusables.user-settings.codespaces-secret-repository-access %} -1. Opcionalmente, para remover o acesso do segredo a um repositório, desmarque o repositório. - ![Caixas de seleção para remover o acesso aos repositórios](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) -1. Clique em **Salvar alterações**. +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.codespaces-tab %} +1. Under "Codespaces secrets", to the right of the secret you want to edit, click **Update**. + !["Update" button](/assets/images/help/settings/codespaces-secret-update-button.png) +1. Under "Value", click **enter a new value**. + !["enter a new value" link](/assets/images/help/settings/codespaces-secret-update-value-text.png) +{% data reusables.user-settings.codespaces-secret-value %} +{% data reusables.user-settings.codespaces-secret-repository-access %} +1. Optionally, to remove the secret's access to a repository, deselect the repository. + ![Checkboxes to remove access to repositories](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) +1. Click **Save changes**. -## Excluir um segredo +## Deleting a secret -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.codespaces-tab %} -1. Em "Segredos de codespaces", à direita do segredo que você deseja excluir, clique em **Excluir**. - ![Botão "Excluir"](/assets/images/help/settings/codespaces-secret-delete-button.png) -1. Leia o aviso e clique em **OK**. - ![Confirmação para excluir um segredo](/assets/images/help/settings/codespaces-secret-delete-warning.png) +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.codespaces-tab %} +1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. + !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png) +1. Read the warning, then click **OK**. + ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png) -## Usando segredos +## Using secrets -Um segredo é exportado como uma variável de ambiente para a sessão de terminal do usuário. +A secret is exported as an environment variable into the user's terminal session. - ![Exibir o valor de um segredo exportado no terminal](/assets/images/help/codespaces/exported-codespace-secret.png) + ![Displaying the value of an exported secret in the terminal](/assets/images/help/codespaces/exported-codespace-secret.png) -Você pode usar segredos em um codespace depois que o codespace for criado e estiver em execução. Por exemplo, um segredo pode ser usado: +You can use secrets in a codespace after the codespace is built and is running. For example, a secret can be used: -* Ao iniciar um aplicativo do terminal integrado ou da sessão SSH. -* Dentro de um script de ciclo de vida do contêiner de desenvolvimento executado após a execução do codespace. Para obter mais informações sobre scripts de ciclo de vida do contêiner de desenvolvimento, confira a documentação sobre contêineres de desenvolvimento: [Especificação](https://containers.dev/implementors/json_reference/#lifecycle-scripts). +* When launching an application from the integrated terminal or ssh session. +* Within a dev container lifecycle script that is run after the codespace is running. For more information about dev container lifecycle scripts, see the documentation on containers.dev: [Specification](https://containers.dev/implementors/json_reference/#lifecycle-scripts). -Os segredos do codespace não podem ser usados durante: +Codespace secrets cannot be used during: -* O tempo de build do codespace (ou seja, em um Dockerfile ou ponto de entrada personalizado). -* Em um recurso de contêiner de desenvolvimento. Para obter mais informações, confira o atributo `features` na documentação sobre contêineres de desenvolvimento: [Especificação](https://containers.dev/implementors/json_reference/#general-properties). +* Codespace build time (that is, within a Dockerfile or custom entry point). +* Within a dev container feature. For more information, see the `features` attribute in the documentation on containers.dev: [Specification](https://containers.dev/implementors/json_reference/#general-properties). -## Leitura adicional +## Further reading -- "[Como gerenciar segredos criptografados do repositório e da organização para o {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces)" +- "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces)" diff --git a/translations/pt-BR/content/codespaces/overview.md b/translations/pt-BR/content/codespaces/overview.md index 1a6ee65780..b193cde66d 100644 --- a/translations/pt-BR/content/codespaces/overview.md +++ b/translations/pt-BR/content/codespaces/overview.md @@ -22,7 +22,7 @@ topics: A codespace is a development environment that's hosted in the cloud. You can customize your project for {% data variables.product.prodname_github_codespaces %} by committing [configuration files](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project) to your repository (often known as Configuration-as-Code), which creates a repeatable codespace configuration for all users of your project. -{% data variables.product.prodname_github_codespaces %} run on a variety of VM-based compute options hosted by {% data variables.product.product_location %}, which you can configure from 2 core machines up to 32 core machines. You can connect to your codespaces from the browser or locally using {% data variables.product.prodname_vscode %}. +{% data variables.product.prodname_github_codespaces %} run on a variety of VM-based compute options hosted by {% data variables.location.product_location %}, which you can configure from 2 core machines up to 32 core machines. You can connect to your codespaces from the browser or locally using {% data variables.product.prodname_vscode %}. ![A diagram showing how {% data variables.product.prodname_github_codespaces %} works](/assets/images/help/codespaces/codespaces-diagram.png) diff --git a/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md b/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md index ff49dcf7ed..f9f02988d3 100644 --- a/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md +++ b/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md @@ -29,33 +29,33 @@ When you create or edit a prebuild configuration for a `devcontainer.json` file ## Allowing a prebuild write access external resources -If your project requires write access to resources, or if the external resources reside in a repository with a different owner to the repository for which you are creating a prebuild configuration, you can use a personal access token (PAT) to grant this access. +If your project requires write access to resources, or if the external resources reside in a repository with a different owner to the repository for which you are creating a prebuild configuration, you can use a {% data variables.product.pat_generic %} to grant this access. -You will need to create a new personal account and then use this account to create a PAT with the appropriate scopes. +You will need to create a new personal account and then use this account to create a {% data variables.product.pat_v1 %} with the appropriate scopes. 1. Create a new personal account on {% data variables.product.prodname_dotcom %}. {% warning %} - **Warning**: Although you can generate the PAT using your existing personal account, we strongly recommend creating a new account with access only to the target repositories required for your scenario. This is because the access token's `repository` permission grants access to all of the repositories that the account has access to. For more information, see "[Signing up for a new GitHub account](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)" and "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#considering-cross-repository-access)." + **Warning**: Although you can generate the {% data variables.product.pat_v1 %} using your existing personal account, we strongly recommend creating a new account with access only to the target repositories required for your scenario. This is because the access token's `repository` permission grants access to all of the repositories that the account has access to. For more information, see "[Signing up for a new GitHub account](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)" and "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#considering-cross-repository-access)." {% endwarning %} 1. Give the new account read access to the required repositories. For more information, see "[Managing an individual's access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)." -1. While signed into the new account, create a PAT with the `repo` scope. Optionally, if the prebuild will need to download packages from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, also select the `read:packages` scope. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." +1. While signed into the new account, create a {% data variables.product.pat_v1 %} with the `repo` scope. Optionally, if the prebuild will need to download packages from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, also select the `read:packages` scope. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - !['repo' and 'packages' scopes selected for a PAT](/assets/images/help/codespaces/prebuilds-select-scopes.png) + !['repo' and 'packages' scopes selected for a {% data variables.product.pat_v1 %}](/assets/images/help/codespaces/prebuilds-select-scopes.png) If the prebuild will use a package from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, you will need to either grant the new account access to the package or configure the package to inherit the access permissions of the repository you are prebuilding. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)." -{% ifversion ghec %}1. Authorize the token for use with SAML single sign-on (SSO), so that it can access repositories that are owned by organizations with SSO enabled. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)." +{% ifversion ghec %}1. Authorize the token for use with SAML single sign-on (SSO), so that it can access repositories that are owned by organizations with SSO enabled. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)." - ![The button to configure SSO for a PAT](/assets/images/help/codespaces/configure-SSO-for-PAT.png) + ![The button to configure SSO for a {% data variables.product.pat_v1 %}](/assets/images/help/codespaces/configure-SSO-for-PAT.png) {% endif %} 1. Copy the token string. You will assign this to a {% data variables.product.prodname_codespaces %} repository secret. 1. Sign back into the account that has admin access to the repository. 1. In the repository for which you want to create {% data variables.product.prodname_github_codespaces %} prebuilds, create a new {% data variables.product.prodname_codespaces %} repository secret called `CODESPACES_PREBUILD_TOKEN`, giving it the value of the token you created and copied. For more information, see "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-a-repository)." -The PAT will be used for all subsequent prebuilds created for your repository. Unlike other {% data variables.product.prodname_codespaces %} repository secrets, the `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and will not be available to use in codespaces created from your repository. +The {% data variables.product.pat_generic %} will be used for all subsequent prebuilds created for your repository. Unlike other {% data variables.product.prodname_codespaces %} repository secrets, the `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and will not be available to use in codespaces created from your repository. ## Further reading diff --git a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md index 3dd56a78c9..24a9ff072b 100644 --- a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md +++ b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md @@ -1,6 +1,6 @@ --- -title: Sobre wikis -intro: Você pode hospedar a documentação para seu repositório em um wiki para que outras pessoas possam usar e contribuir com seu projeto. +title: About wikis +intro: 'You can host documentation for your repository in a wiki, so that others can use and contribute to your project.' redirect_from: - /articles/about-github-wikis - /articles/about-wikis @@ -13,33 +13,28 @@ versions: ghec: '*' topics: - Community -ms.openlocfilehash: 94800761c60bb984745e582e2c9691e294e7a90d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147529620' --- -Todos os repositórios em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} são equipados com uma seção para a documentação de hospedagem denominada wiki. Você pode usar o wiki do repositório para compartilhar conteúdo longo sobre seu projeto, por exemplo, como usá-lo, como ele foi projetado ou seus princípios básicos. Um arquivo README informa rapidamente o que seu projeto pode fazer, enquanto você pode usar um wiki para fornecer documentação adicional. Para obter mais informações, confira "[Sobre os arquivos LEIAME](/articles/about-readmes)". -Com wikis, é possível gravar conteúdo assim como em qualquer outro lugar no {% data variables.product.product_name %}. Para obter mais informações, confira "[Introdução à escrita e à formatação no {% data variables.product.prodname_dotcom %}](/articles/getting-started-with-writing-and-formatting-on-github)". Usamos [nossa biblioteca de marcação de código aberto](https://github.com/github/markup) para converter diferentes formatos em HTML, de modo que você possa optar por escrever seu aplicativo em Markdown ou em qualquer outro formato com suporte. +Every repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} comes equipped with a section for hosting documentation, called a wiki. You can use your repository's wiki to share long-form content about your project, such as how to use it, how you designed it, or its core principles. A README file quickly tells what your project can do, while you can use a wiki to provide additional documentation. For more information, see "[About READMEs](/articles/about-readmes)." + +With wikis, you can write content just like everywhere else on {% data variables.product.product_name %}. For more information, see "[Getting started with writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/getting-started-with-writing-and-formatting-on-github)." We use [our open-source Markup library](https://github.com/github/markup) to convert different formats into HTML, so you can choose to write in Markdown or any other supported format. {% data reusables.getting-started.math-and-diagrams %} -{% ifversion fpt or ghes or ghec %}Se você criar um wiki em um repositório público, o wiki estará disponível para {% ifversion ghes %}qualquer pessoa com acesso ao {% data variables.product.product_location %}{% else %}o público{% endif %}. {% endif %}Se você criar um wiki em um repositório privado{% ifversion ghec or ghes %} ou interno,{% endif %} apenas {% ifversion fpt or ghes or ghec %}as pessoas{% elsif ghae %}integrantes da empresa{% endif %} com acesso ao repositório poderão acessar o wiki. Para obter mais informações, confira "[Como configurar a visibilidade do repositório](/articles/setting-repository-visibility)". +{% ifversion fpt or ghes or ghec %}If you create a wiki in a public repository, the wiki is available to {% ifversion ghes %}anyone with access to {% data variables.location.product_location %}{% else %}the public{% endif %}. {% endif %}If you create a wiki in a private{% ifversion ghec or ghes %} or internal{% endif %} repository, only {% ifversion fpt or ghes or ghec %}people{% elsif ghae %}enterprise members{% endif %} with access to the repository can access the wiki. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)." -Você pode editar wikis diretamente no {% data variables.product.product_name %} ou editar arquivos wiki localmente. Por padrão, somente as pessoas com acesso de gravação ao repositório podem fazer alterações no wikis, embora você possa permitir que todos em {% data variables.product.product_location %} contribuam para um wiki em {% ifversion ghae %}um repositório interno{% else %}público{% endif %}. Para saber mais, confira "[Como alterar as permissões de acesso para wikis](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis)". +You can edit wikis directly on {% data variables.product.product_name %}, or you can edit wiki files locally. By default, only people with write access to your repository can make changes to wikis, although you can allow everyone on {% data variables.location.product_location %} to contribute to a wiki in {% ifversion ghae %}an internal{% else %}a public{% endif %} repository. For more information, see "[Changing access permissions for wikis](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis)." {% note %} -**Observação:** os mecanismos de pesquisa não indexarão o conteúdo dos wikis. Para indexar seu conteúdo nos mecanismos de pesquisa, use o [{% data variables.product.prodname_pages %}](/pages) em um repositório público. +**Note:** Search engines will not index the contents of wikis. To have your content indexed by search engines, you can use [{% data variables.product.prodname_pages %}](/pages) in a public repository. {% endnote %} -## Leitura adicional +## Further reading -- "[Como adicionar ou editar páginas do wiki](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)" -- "[Como criar um rodapé ou um barra lateral no wiki](/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki)" -- "[Como editar o conteúdo do wiki](/communities/documenting-your-project-with-wikis/editing-wiki-content)" -- "[Como ver o histórico de alterações de um wiki](/articles/viewing-a-wiki-s-history-of-changes)" -- "[Pesquisa em wikis](/search-github/searching-on-github/searching-wikis)" +- "[Adding or editing wiki pages](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)" +- "[Creating a footer or sidebar for your wiki](/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki)" +- "[Editing wiki content](/communities/documenting-your-project-with-wikis/editing-wiki-content)" +- "[Viewing a wiki's history of changes](/articles/viewing-a-wiki-s-history-of-changes)" +- "[Searching wikis](/search-github/searching-on-github/searching-wikis)" diff --git a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md index d0d956f038..1601243f86 100644 --- a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md +++ b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md @@ -1,6 +1,6 @@ --- -title: Alterar as permissões de acesso para wikis -intro: 'Somente os colaboradores do repositório podem editar o wiki de {% ifversion fpt or ghec or ghes %}público{% endif %} por padrão, mas você pode permitir que qualquer pessoa com uma conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} edite seu wiki.' +title: Changing access permissions for wikis +intro: 'Only repository collaborators can edit a {% ifversion fpt or ghec or ghes %}public{% endif %} repository''s wiki by default, but you can allow anyone with an account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} to edit your wiki.' product: '{% data reusables.gated-features.wikis %}' redirect_from: - /articles/changing-access-permissions-for-wikis @@ -13,17 +13,13 @@ versions: topics: - Community shortTitle: Change access permissions -ms.openlocfilehash: 51a9ec690f0bdad1be302592091565b65e5f9b9b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145084136' --- -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -3. Em Recursos, desmarque a opção **Restringir edições somente aos colaboradores**. - ![Edição de restrição do wiki](/assets/images/help/wiki/wiki_restrict_editing.png) -## Leitura adicional +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. Under Features, unselect **Restrict edits to collaborators only**. + ![Wiki restrict editing](/assets/images/help/wiki/wiki_restrict_editing.png) -- "[Como desabilitar wikis](/communities/documenting-your-project-with-wikis/disabling-wikis)" +## Further reading + +- "[Disabling wikis](/communities/documenting-your-project-with-wikis/disabling-wikis)" diff --git a/translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md b/translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md index eb67e13b8a..d2ee747226 100644 --- a/translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md +++ b/translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md @@ -1,45 +1,37 @@ --- -title: Introdução ao GitHub Copilot no Neovim +title: Getting started with GitHub Copilot in Neovim shortTitle: Neovim product: '{% data reusables.gated-features.copilot %}' -intro: 'Saiba como instalar o {% data variables.product.prodname_copilot %} no Neovim e passar a ver sugestões enquanto escreve comentários e códigos.' +intro: 'Learn how to install {% data variables.product.prodname_copilot %} in Neovim, and start seeing suggestions as you write comments and code.' versions: feature: copilot topics: - Copilot -ms.openlocfilehash: 8884d3ac0ae6fecdc75def792e2b3d4157537498 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147079477' --- -## Sobre o {% data variables.product.prodname_copilot %} e o Neovim + +## About {% data variables.product.prodname_copilot %} and Neovim {% data reusables.copilot.procedural-intro %} -Usando o Neovim, você pode ver e incorporar sugestões do {% data variables.product.prodname_copilot %} diretamente no editor. +If you use a Neovim, you can view and incorporate suggestions from {% data variables.product.prodname_copilot %} directly within the editor. -## Pré-requisitos +## Prerequisites -Para usar o {% data variables.product.prodname_copilot %} no Neovim, você precisa ter o Neovim e o Node.js versão 17 ou inferior instalados. Para obter mais informações, confira a [documentação do Neovim](https://neovim.io/doc/) e o [site do Node.js](https://nodejs.org/en/). +- To use {% data variables.product.prodname_copilot %} you must have an active {% data variables.product.prodname_copilot %} subscription. For more information, see "[About billing for {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)." -## Como instalar a extensão do Neovim +- To use {% data variables.product.prodname_copilot %} in Neovim you must have Neovim and Node.js version 17 or below installed. For more information, see the [Neovim documentation](https://neovim.io/doc/) and the [Node.js website](https://nodejs.org/en/). + +## Installing the Neovim extension {% mac %} {% data reusables.copilot.install-copilot-in-neovim %} - - Para instalar o plug-in do {% data variables.product.prodname_copilot %} diretamente, você precisa saber onde o Neovim armazena plug-ins. Para instalar o plug-in, insira o comando a seguir no terminal. + - To install {% data variables.product.prodname_copilot %} with Neovim's built-in plugin manager, enter the following command in Terminal. - ``` - git clone https://github.com/github/copilot.vim \ - PATH/TO/NEOVIM/PLUGINS/copilot.vim - ``` -1. Para configurar o {% data variables.product.prodname_copilot %}, abra o Neovim e insira o comando a seguir. + git clone https://github.com/github/copilot.vim \ + ~/.config/nvim/pack/github/start/copilot.vim - ``` - :Copilot setup - ``` +{% data reusables.copilot.config-enable-copilot-in-neovim %} {% endmac %} @@ -47,16 +39,12 @@ Para usar o {% data variables.product.prodname_copilot %} no Neovim, você preci {% windows %} {% data reusables.copilot.install-copilot-in-neovim %} - - Para instalar o plug-in do {% data variables.product.prodname_copilot %} diretamente, você precisa saber onde o Neovim armazena plug-ins. Para instalar o plug-in, insira o comando a seguir no Git Bash. + - To install {% data variables.product.prodname_copilot %} with Neovim's built-in plugin manager, enter the following command in Git Bash. - ``` - git clone https://github.com/github/copilot.vim \ - ~/.config/PATH/TO/YOUR/NEOVIM/CONFIG/FILE/copilot.vim -1. To configure {% data variables.product.prodname_copilot %}, open Neovim and enter the following command. + git clone https://github.com/github/copilot.vim.git ` + $HOME/AppData/Local/nvim/pack/github/start/copilot.vim - ``` - :Copilot setup - ``` +{% data reusables.copilot.config-enable-copilot-in-neovim %} {% endwindows %} @@ -64,25 +52,22 @@ Para usar o {% data variables.product.prodname_copilot %} no Neovim, você preci {% linux %} {% data reusables.copilot.install-copilot-in-neovim %} - - To install the {% data variables.product.prodname_copilot %} plugin directly, you must know where Neovim stores plugins. To install the plugin, enter the following command in Git Bash. + - To install {% data variables.product.prodname_copilot %} with Neovim's built-in plugin manager, enter the following command: - ``` - git clone https://github.com/github/copilot.vim \ - ~/.config/PATH/TO/YOUR/NEOVIM/CONFIG/FILE/copilot.vim - ``` -1. To configure {% data variables.product.prodname_copilot %}, open Neovim and enter the following command. + git clone https://github.com/github/copilot.vim \ + ~/.config/nvim/pack/github/start/copilot.vim + +{% data reusables.copilot.config-enable-copilot-in-neovim %} - ``` - :Copilot setup - ``` {% endlinux %} ## Learning to use {% data variables.product.prodname_copilot %} in Neovim For guidance on using {% data variables.product.prodname_copilot %} in Neovim, you can view the plugin documentation. To see the documentation, open Neovim and run the following command. -``` -:help copilot -``` + + ``` + :help copilot + ``` ## Further reading diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md index e087c5799b..a73f507945 100644 --- a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md +++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md @@ -1,57 +1,53 @@ --- -title: Clonar um repositório do GitHub para o GitHub Desktop -intro: 'É possível usar o {% data variables.product.prodname_dotcom %} a fim de clonar repositórios remote para o {% data variables.product.prodname_desktop %}.' +title: Cloning a repository from GitHub to GitHub Desktop +intro: 'You can use {% data variables.product.prodname_dotcom %} to clone remote repositories to {% data variables.product.prodname_desktop %}.' redirect_from: - /desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop - /desktop/contributing-and-collaborating-using-github-desktop/cloning-a-repository-from-github-to-github-desktop versions: fpt: '*' shortTitle: Clone a GitHub repo -ms.openlocfilehash: ba4ddcc8c3d95454ab06cac0293162e2fe01fe32 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145095190' --- {% tip %} -**Dica:** use também o {% data variables.product.prodname_desktop %} para clonar repositórios existentes no {% data variables.product.prodname_dotcom %}. Para obter mais informações, confira "[Como clonar um repositório do {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)". +**Tip:** You also can use {% data variables.product.prodname_desktop %} to clone repositories that exist on {% data variables.product.prodname_dotcom %}. For more information, see "[Cloning a repository from {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)." {% endtip %} {% mac %} -1. Entre no {% data variables.product.product_location %} e no {% data variables.product.prodname_desktop %} antes de começar a clonar. -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.open-with-github-desktop %} -5. Clique em **Escolher…** e, usando a janela Localizador, procure um caminho local em que deseja clonar o repositório. -![Botão Escolher na guia URL](/assets/images/help/desktop/clone-choose-button-url-mac.png) +1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_desktop %} before you start to clone. +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.open-with-github-desktop %} +5. Click **Choose...** and, using the Finder window, navigate to a local path where you want to clone the repository. +![The choose button on the URL tab](/assets/images/help/desktop/clone-choose-button-url-mac.png) {% note %} - **Observação:** se o repositório estiver configurado para usar o LFS, você precisará inicializar o {% data variables.large_files.product_name_short %}. + **Note:** If the repository is configured to use LFS, you will be prompted to initialize {% data variables.large_files.product_name_short %}. {% endnote %} -5. Clique em **Clonar**. -![Botão Clonar na guia URL](/assets/images/help/desktop/clone-button-url-mac.png) +5. Click **Clone**. +![The clone button on the URL tab](/assets/images/help/desktop/clone-button-url-mac.png) {% endmac %} {% windows %} -1. Entre no {% data variables.product.product_location %} e no {% data variables.product.prodname_desktop %} antes de começar a clonar. -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.open-with-github-desktop %} -5. Clique em **Escolher…** e, usando o Windows Explorer, procure um caminho local em que deseja clonar o repositório. -![Botão Escolher](/assets/images/help/desktop/clone-choose-button-url-win.png) +1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_desktop %} before you start to clone. +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.open-with-github-desktop %} +5. 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-url-win.png) {% note %} - **Observação:** se o repositório estiver configurado para usar o LFS, você precisará inicializar o {% data variables.large_files.product_name_short %}. + **Note:** If the repository is configured to use LFS, you will be prompted to initialize {% data variables.large_files.product_name_short %}. {% endnote %} -5. Clique em **Clonar**. -![Botão Clonar](/assets/images/help/desktop/clone-button-url-win.png) +5. Click **Clone**. +![The clone button](/assets/images/help/desktop/clone-button-url-win.png) {% endwindows %} diff --git a/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md b/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md index 01f3b58a86..b550521342 100644 --- a/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md +++ b/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md @@ -1,24 +1,18 @@ --- -title: Sobre conexões com o GitHub -intro: '{% data variables.product.prodname_desktop %} usa HTTPS para trocar dados de forma segura com {% data variables.product.prodname_dotcom %}.' +title: About connections to GitHub +intro: '{% data variables.product.prodname_desktop %} uses HTTPS to securely exchange data with {% data variables.product.prodname_dotcom %}.' redirect_from: - /desktop/getting-started-with-github-desktop/about-connections-to-github - /desktop/installing-and-configuring-github-desktop/about-connections-to-github versions: fpt: '*' shortTitle: About connections -ms.openlocfilehash: 94f1e7db78504a115b233f17485f1b12299a1e11 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145095145' --- -{% data variables.product.prodname_desktop %} conecta-se a {% data variables.product.prodname_dotcom %} quando você pull, push, clona e bifurca os repositórios remotos. Para se conectar a {% data variables.product.prodname_dotcom %} a partir de {% data variables.product.prodname_desktop %}, você deve autenticar sua conta. Para obter mais informações, confira "[Autenticação no {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)". +{% data variables.product.prodname_desktop %} connects to {% data variables.product.prodname_dotcom %} when you pull from, push to, clone, and fork remote repositories. To connect to {% data variables.product.prodname_dotcom %} from {% data variables.product.prodname_desktop %}, you must authenticate your account. For more information, see "[Authenticating to {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)." -Depois de se autenticar no {% data variables.product.prodname_dotcom %}, você poderá se conectar a repositórios remotos com o {% data variables.product.prodname_desktop %}. O {% data variables.product.prodname_desktop %} armazena suas credenciais (nome de usuário e senha ou token de acesso pessoal) e usa as credenciais para autenticar cada conexão ao repositório remoto. +After you authenticate to {% data variables.product.prodname_dotcom %}, you can connect to remote repositories with {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} caches your credentials (username and password or {% data variables.product.pat_generic %}) and uses the credentials to authenticate for each connection to the remote repository. -{% data variables.product.prodname_desktop %} se conecta ao {% data variables.product.prodname_dotcom %} usando HTTPS. Se você usar o {% data variables.product.prodname_desktop %} para acessar repositórios que foram clonados usando SSH, você poderá encontrar erros. Para se conectar a um repositório que foi clonado usando SSH, altere as URLs do remote. Para obter mais informações, confira "[Como gerenciar repositórios remotos](/github/getting-started-with-github/managing-remote-repositories)". +{% data variables.product.prodname_desktop %} connects to {% data variables.product.prodname_dotcom %} using HTTPS. If you use {% data variables.product.prodname_desktop %} to access repositories that were cloned using SSH, you may encounter errors. To connect to a repository that was cloned using SSH, change the remote's URLs. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." -## Leitura adicional -- "[Como clonar repositórios e criar fork deles no GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop)" +## Further reading +- "[Cloning and forking repositories from GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop)" diff --git a/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md b/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md index 9640145eee..220f7b85da 100644 --- a/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md +++ b/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md @@ -1,120 +1,126 @@ --- -title: Autenticação no GitHub +title: Authenticating to GitHub shortTitle: Authentication -intro: 'Você pode acessar com segurança os recursos da sua conta em {% data variables.product.prodname_desktop %} através da autenticação no {% data variables.product.prodname_dotcom %}.' +intro: 'You can securely access your account''s resources on {% data variables.product.prodname_desktop %} by authenticating to {% data variables.product.prodname_dotcom %}.' redirect_from: - /desktop/getting-started-with-github-desktop/authenticating-to-github-using-the-browser - /desktop/getting-started-with-github-desktop/authenticating-to-github - /desktop/installing-and-configuring-github-desktop/authenticating-to-github versions: fpt: '*' -ms.openlocfilehash: e88d59a03d876b23d8eb72aae7324db64981096f -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145095137' --- -## Sobre autenticação +## About authentication -Para manter sua conta segura, você deve autenticar antes de usar o {% data variables.product.prodname_desktop %} para acessar os recursos no {% data variables.product.prodname_dotcom %}. +To keep your account secure, you must authenticate before you can use {% data variables.product.prodname_desktop %} to access resources on {% data variables.product.prodname_dotcom %}. -Antes de autenticar, {% data reusables.desktop.get-an-account %} +Before you authenticate, {% data reusables.desktop.get-an-account %} {% mac %} -## Autenticando uma conta no {% data variables.product.prodname_dotcom %} +## Authenticating an account on {% data variables.product.prodname_dotcom %} -{% data reusables.desktop.mac-select-desktop-menu %} {% data reusables.desktop.mac-select-accounts %} -3. À direita de "{% data variables.product.prodname_dotcom_the_website %}", clique em **Entrar**. - ![O botão Entrar do GitHub](/assets/images/help/desktop/mac-sign-in-github.png) {% data reusables.desktop.sign-in-browser %} +{% data reusables.desktop.mac-select-desktop-menu %} +{% data reusables.desktop.mac-select-accounts %} +3. To the right of "{% data variables.product.prodname_dotcom_the_website %}," click **Sign In**. + ![The Sign In button for GitHub](/assets/images/help/desktop/mac-sign-in-github.png) +{% data reusables.desktop.sign-in-browser %} -{% data reusables.desktop.authenticate-in-browser %} {% data reusables.desktop.2fa-in-browser %} -7. Depois que o {% data variables.product.prodname_dotcom %} autenticar sua conta, siga as instruções para retornar a {% data variables.product.prodname_desktop %}. +{% data reusables.desktop.authenticate-in-browser %} +{% data reusables.desktop.2fa-in-browser %} +7. After {% data variables.product.prodname_dotcom %} authenticates your account, follow the prompts to return to {% data variables.product.prodname_desktop %}. -## Autenticando uma conta no {% data variables.product.prodname_ghe_server %} +## Authenticating an account on {% data variables.product.prodname_ghe_server %} -{% data reusables.desktop.mac-select-desktop-menu %} {% data reusables.desktop.mac-select-accounts %} {% data reusables.desktop.choose-product-authenticate %} -4. Para adicionar uma conta no {% data variables.product.product_location_enterprise %}, digite a URL da sua instância em "Endereço da empresa" e clique em **Continuar**. - ![Botão Entrar do GitHub Enterprise](/assets/images/help/desktop/mac-sign-in-button-enterprise.png) {% data reusables.desktop.sign-in-browser %} -1. Para autenticar na conta do {% data variables.product.product_location_enterprise %}, digite as credenciais da sua conta e clique em **Entrar**. - ![O botão Entrar do {% data variables.product.prodname_ghe_server %} no navegador](/assets/images/help/desktop/enterprise-sign-in-button-browser.png) +{% data reusables.desktop.mac-select-desktop-menu %} +{% data reusables.desktop.mac-select-accounts %} +{% data reusables.desktop.choose-product-authenticate %} +4. To add an account on {% data variables.location.product_location_enterprise %}, type the URL for your instance under "Enterprise address," then click **Continue**. + ![The Sign In button for GitHub Enterprise](/assets/images/help/desktop/mac-sign-in-button-enterprise.png) +{% data reusables.desktop.sign-in-browser %} +1. To authenticate to {% data variables.location.product_location_enterprise %} account, type your account credentials and click **Sign in**. + ![The Sign In button for {% data variables.product.prodname_ghe_server %} in browser](/assets/images/help/desktop/enterprise-sign-in-button-browser.png) - Como alternativa, se você já estava logado no{% data variables.product.product_location_enterprise %}, siga as instruções para retornar ao {% data variables.product.prodname_desktop %} para finalizar a autenticação. + Alternatively, if you were already signed in to {% data variables.location.product_location_enterprise %} account, follow the prompts to return to {% data variables.product.prodname_desktop %} to finish authenticating. {% endmac %} {% windows %} -## Autenticando uma conta no {% data variables.product.prodname_dotcom %} +## Authenticating an account on {% data variables.product.prodname_dotcom %} -{% data reusables.desktop.windows-choose-options %} {% data reusables.desktop.windows-select-accounts %} -3. À direita de "GitHub.com", clique em **Entrar**. - ![O botão Entrar do GitHub](/assets/images/help/desktop/windows-sign-in-github.png) {% data reusables.desktop.sign-in-browser %} +{% data reusables.desktop.windows-choose-options %} +{% data reusables.desktop.windows-select-accounts %} +3. To the right of "GitHub.com," click **Sign in**. + ![The Sign In button for GitHub](/assets/images/help/desktop/windows-sign-in-github.png) +{% data reusables.desktop.sign-in-browser %} {% data reusables.user-settings.password-authentication-deprecation-desktop %} -{% data reusables.desktop.authenticate-in-browser %} {% data reusables.desktop.2fa-in-browser %} -7. Depois que o {% data variables.product.prodname_dotcom %} autenticar sua conta, siga as instruções para retornar a {% data variables.product.prodname_desktop %}. +{% data reusables.desktop.authenticate-in-browser %} +{% data reusables.desktop.2fa-in-browser %} +7. After {% data variables.product.prodname_dotcom %} authenticates your account, follow the prompts to return to {% data variables.product.prodname_desktop %}. -## Autenticando uma conta no {% data variables.product.prodname_enterprise %} +## Authenticating an account on {% data variables.product.prodname_enterprise %} -{% data reusables.desktop.windows-choose-options %} {% data reusables.desktop.windows-select-accounts %} {% data reusables.desktop.choose-product-authenticate %} -4. Para adicionar uma conta do {% data variables.product.prodname_enterprise %}, digite suas credenciais em "Endereço da empresa" e clique em **Continuar**. - ![Botão Entrar do GitHub Enterprise](/assets/images/help/desktop/windows-sign-in-button-enterprise.png) {% data reusables.desktop.retrieve-2fa %} +{% data reusables.desktop.windows-choose-options %} +{% data reusables.desktop.windows-select-accounts %} +{% data reusables.desktop.choose-product-authenticate %} +4. To add a {% data variables.product.prodname_enterprise %} account, type your credentials under "Enterprise address," then click **Continue**. + ![The Sign In button for GitHub Enterprise](/assets/images/help/desktop/windows-sign-in-button-enterprise.png) +{% data reusables.desktop.retrieve-2fa %} {% endwindows %} -## Solucionando problemas de autenticação +## Troubleshooting authentication issues -Se o {% data variables.product.prodname_desktop %} encontrar um erro de autenticação, você pode usar mensagens de erro para solucionar problemas. +If {% data variables.product.prodname_desktop %} encounters an authentication error, you can use error messages to troubleshoot. -Se você encontrar um erro de autenticação, primeiro tente sair e entrar novamente em sua conta no {% data variables.product.prodname_desktop %}. +If you encounter an authentication error, first try signing out and signing back in to your account on {% data variables.product.prodname_desktop %}. -Para alguns erros, {% data variables.product.prodname_desktop %} enviará a você uma mensagem de erro. Se você não receber a mensagem, ou caso queira encontrar mais informações sobre qualquer erro, visualize os arquivos de log de {% data variables.product.prodname_desktop %} usando as seguintes etapas. +For some errors, {% data variables.product.prodname_desktop %} will prompt you with an error message. If you are not prompted, or to find more information about any error, view the {% data variables.product.prodname_desktop %} log files by using the following steps. {% mac %} -1. Use o menu suspenso **Ajuda** e clique em **Mostrar Logs no Localizador**. - ![Botão Mostrar Logs no Localizador](/assets/images/help/desktop/mac-show-logs.png) -2. Selecione o arquivo de log a partir da data em que você encontrou o erro de autenticação. +1. Use the **Help** drop-down menu and click **Show Logs in Finder**. + ![The Show Logs in Finder button](/assets/images/help/desktop/mac-show-logs.png) +2. Select the log file from the date when you encountered the authentication error. {% endmac %} {% windows %} -1. Use o menu suspenso **Ajuda** e clique em **Mostrar Logs no Explorer**. - ![Botão Mostrar Logs no Explorer](/assets/images/help/desktop/windows-show-logs.png) -2. Selecione o arquivo de log a partir da data em que você encontrou o erro de autenticação. +1. Use the **Help** drop-down menu and click **Show Logs in Explorer**. + ![The Show Logs in Explorer button](/assets/images/help/desktop/windows-show-logs.png) +2. Select the log file from the date when you encountered the authentication error. {% endwindows %} -Revise abaixo as informações de solução de problemas para a mensagem de erro que você encontrar. +Review the troubleshooting information below for the error message that you encounter. -### Credenciais inválidas +### Bad credentials ```shell Error: Bad credentials ``` -Este erro significa que há um problema com suas credenciais da conta armazenada. +This error means that there is an issue with your stored account credentials. -Para solucionar problemas, saia da sua conta no {% data variables.product.prodname_desktop %} e entre novamente. +To troubleshoot, sign out of your account on {% data variables.product.prodname_desktop %} and then sign back in. -### Token vazio +### Empty token ```shell -info: [ui] [AppStore.withAuthenticatingUser] account found for repository: node - (empty token) +info: [ui] [AppStore.withAuthenticatingUser] account found for repository: node - USERNAME (empty token) ``` -Este erro significa que {% data variables.product.prodname_desktop %} não foi possível encontrar o token de acesso que ele criou no keychain do sistema. +This error means that {% data variables.product.prodname_desktop %} is unable to find the access token that it created in the system keychain. -Para solucionar problemas, saia da sua conta no {% data variables.product.prodname_desktop %} e entre novamente. +To troubleshoot, sign out of your account on {% data variables.product.prodname_desktop %} and then sign back in. -### Repositório não encontrado +### Repository not found ```shell fatal: repository 'https://github.com//.git' not found @@ -122,11 +128,11 @@ fatal: repository 'https://github.com//.git' not found (The error was parsed as 8: The repository does not seem to exist anymore. You may not have access, or it may have been deleted or renamed.) ``` -Este erro significa que você não tem permissão para acessar o repositório que está tentando clonar. +This error means that you do not have permission to access the repository that you are trying to clone. -Para solucionar problemas, entre em contato com a pessoa da sua organização que administra as permissões. +To troubleshoot, contact the person in your organization who administers permissions. -### Não foi possível ler a partir do repositório remoto +### Could not read from remote repository ```shell git@github.com: Permission denied (publickey). @@ -135,11 +141,11 @@ fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. ``` -Este erro significa que você não tem uma chave SSH válida configurada. +This error means that you do not have a valid SSH key set up. -Para solução de problemas, confira "[Como gerar uma nova chave SSH e adicioná-la ao agente SSH](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". +To troubleshoot, see "[Generating a new SSH key and adding it to the SSH agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." -### Falha ao clonar +### Failed to clone ```shell fatal: clone of 'git@github.com:/' into submodule path '' failed @@ -151,34 +157,34 @@ Please make sure you have the correct access rights and the repository exists. ``` -Este erro significa que, ou o repositório que você está tentando clonar tem submódulos aos quais você não tem acesso, ou você não tem uma chave SSH válida configurada. +This error means that either the repository that you are trying to clone has submodules that you do not have access to or you do not have a valid SSH key set up. -Se você não tem acesso aos submódulos, resolva problemas entrando em contato com a pessoa que administra permissões para o repositório. +If you do not have access to the submodules, troubleshoot by contacting the person who administers permissions for the repository. -Se você não tiver uma chave SSH válida configurada, confira "[Como gerar uma nova chave SSH e adicioná-la ao agente SSH](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". +If you do not have a valid SSH key set up, see "[Generating a new SSH key and adding it to the SSH agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." {% windows %} -### Não foi possível ler a resposta do AskPass +### Unable to read AskPass response ```shell error: unable to read askpass response from '/Users//GitHub Desktop.app/Contents/Resources/app/static/ask-pass-trampoline.sh' fatal: could not read Username for 'https://github.com': terminal prompts disabled ``` -Este erro pode ser causado por vários eventos. +This error can be caused by multiple events. -Se as entradas `Command Processor` do Registro forem modificadas, o {% data variables.product.prodname_desktop %} responderá com o erro `Authentication failed`. Para verificar se estas entradas de registro foram modificadas, siga estas etapas. +If the `Command Processor` registry entries are modified, {% data variables.product.prodname_desktop %} will respond with an `Authentication failed` error. To check if these registry entries have been modified, follow these steps. -1. Abra o Editor do Registro (`regedit.exe`) e procure os locais a seguir. +1. Open the Registry Editor (`regedit.exe`) and navigate to the following locations. `HKEY_CURRENT_USER\Software\Microsoft\Command Processor\` `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor\` -2. Verifique se há um valor `Autorun` em um desses locais. -3. Se houver um valor `Autorun`, exclua-o. +2. Check to see if there is an `Autorun` value in either location. +3. If there is an `Autorun` value, delete it. -Se o seu nome de usuário do Windows tiver caracteres Unicode estendidos, isso pode causar um erro de resposta do AskPass. Para solucionar problemas, crie uma nova conta de usuário do Windows e migre seus arquivos para essa conta. Para obter mais informações, confira "[Criar uma conta de usuário no Windows](https://support.microsoft.com/en-us/help/13951/windows-create-user-account)" na documentação da Microsoft. +If your Windows username has extended Unicode characters, it may cause an AskPass response error. To troubleshoot, create a new Windows user account and migrate your files to that account. For more information, see "[Create a user account in Windows](https://support.microsoft.com/en-us/help/13951/windows-create-user-account)" in the Microsoft documentation. {% endwindows %} -## Leitura adicional -- "[Sobre a autenticação no GitHub](/github/authenticating-to-github/about-authentication-to-github)" +## Further reading +- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)" diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md b/translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md index a3046f4027..8f7e7bdec0 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md @@ -1,5 +1,5 @@ --- -title: Limites de taxa para aplicativos GitHub +title: Rate limits for GitHub Apps intro: '{% data reusables.shortdesc.rate_limits_github_apps %}' redirect_from: - /early-access/integrations/rate-limits @@ -15,62 +15,57 @@ versions: topics: - GitHub Apps shortTitle: Rate limits -ms.openlocfilehash: fd2c9a92c6603a6e64ec17b614f46baf2370c98b -ms.sourcegitcommit: d243bbae4ce3c849695b5bc9221e705ee5a4a64f -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 07/12/2022 -ms.locfileid: '147081125' --- + {% data reusables.enterprise.rate_limit %} {% data reusables.rest-api.always-check-your-limit %} {% ifversion ghec or fpt %} -## Sobre os limites de taxa para os aplicativos +## About rate limits for apps -Os limites de taxa para {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %} dependem do plano para a organização onde você instalar o aplicativo. Para obter mais informações, confira "[Produtos do {% data variables.product.company_short %}](/get-started/learning-about-github/githubs-products)" e "[Tipos de contas do {% data variables.product.company_short %}](/get-started/learning-about-github/types-of-github-accounts#organization-accounts)". +Rate limits for {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} depend on the plan for the organization where you install the application. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)" and "[Types of {% data variables.product.company_short %} accounts](/get-started/learning-about-github/types-of-github-accounts#organization-accounts)." {% endif %} -## Solicitações de servidor para servidor +## Server-to-server requests {% ifversion ghec or fpt %} -### Limites de taxa padrão de servidor para servidor para {% data variables.product.prodname_dotcom_the_website %} +### Default server-to-server rate limits for {% data variables.product.prodname_dotcom_the_website %} {% endif %} -{% data variables.product.prodname_github_apps %} que faz os pedidos do servidor para servidor usa o limite mínimo da taxa de instalação de 5.000 solicitações por hora. Se um aplicativo estiver instalado em uma organização com mais de 20 usuários, ele receberá outras 50 solicitações por hora para cada usuário. As instalações com mais de 20 repositórios recebem outras 50 solicitações por hora para cada repositório. O limite de taxa máximo para uma instalação é de 12.500 solicitações por hora. +{% data variables.product.prodname_github_apps %} making server-to-server requests use the installation's minimum rate limit of 5,000 requests per hour. If an application is installed on an organization with more than 20 users, the application receives another 50 requests per hour for each user. Installations that have more than 20 repositories receive another 50 requests per hour for each repository. The maximum rate limit for an installation is 12,500 requests per hour. {% ifversion fpt or ghec %} -### Limites de taxa de servidor para servidor para {% data variables.product.prodname_ghe_cloud %} +### Server-to-server rate limits for {% data variables.product.prodname_ghe_cloud %} {% endif %} {% ifversion fpt or ghec %} -{% data variables.product.prodname_github_apps %} que estão instalados em uma organização ou um repositório dentro de uma empresa no {% data variables.product.product_location %} estão sujeitos a um limite de 15.000 solicitações por hora. +{% data variables.product.prodname_github_apps %} that are installed on an organization within an enterprise on {% data variables.location.product_location %} are subject to a limit of 15,000 requests per hour per organization that has installed the app. {% endif %} -## Solicitações de usuário para servidor +## User-to-server requests -{% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %} também podem agir em nome de um usuário, fazendo solicitações de usuário para servidor depois que o usuário autorizar o aplicativo. Para obter mais informações, confira "[Como autorizar os {% data variables.product.prodname_github_apps %}](/authentication/keeping-your-account-and-data-secure/authorizing-github-apps)" e "[Como autorizar os {% data variables.product.prodname_oauth_apps %}](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)". +{% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} can also act on behalf of a user, making user-to-server requests after the user authorizes the app. For more information, see "[Authorizing {% data variables.product.prodname_github_apps %}](/authentication/keeping-your-account-and-data-secure/authorizing-github-apps)" and "[Authorizing {% data variables.product.prodname_oauth_apps %}](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)." -As solicitações de usuário para servidor de {% data variables.product.prodname_oauth_apps %} são autenticadas com um token OAuth. As solicitações de usuário para servidor de {% data variables.product.prodname_github_apps %} são autenticadas com um token OAuth ou um token de acesso do usuário expirado. Para obter mais informações, confira "[Como identificar e autorizar usuários para os {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#identifying-and-authorizing-users-for-github-apps)" e "[Como autorizar os {% data variables.product.prodname_oauth_apps %}](/developers/apps/building-oauth-apps/authorizing-oauth-apps)". +User-to-server requests from {% data variables.product.prodname_oauth_apps %} are authenticated with an OAuth token. User-to-server requests from {% data variables.product.prodname_github_apps %} are authenticated with either an OAuth token or an expiring user access token. For more information, see "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#identifying-and-authorizing-users-for-github-apps)" and "[Authorizing {% data variables.product.prodname_oauth_apps %}](/developers/apps/building-oauth-apps/authorizing-oauth-apps)." {% ifversion fpt or ghec %} -### Limites de taxa padrão de usuário para servidor para {% data variables.product.prodname_dotcom_the_website %} +### Default user-to-server rate limits for {% data variables.product.prodname_dotcom_the_website %} {% endif %} {% ifversion ghec %} -Os limites de taxa para as solicitações de servidor para servidor feitas por {% data variables.product.prodname_github_apps %} dependem de onde o aplicativo está instalado. Se o aplicativo estiver instalado em organizações ou repositórios pertencentes a uma empresa em {% data variables.product.product_location %}, a taxa é mais alta do que para instalações fora de uma empresa. +The rate limits for user-to-server requests made by {% data variables.product.prodname_github_apps %} depend on where the app is installed. If the app is installed on organizations or repositories owned by an enterprise on {% data variables.location.product_location %}, then the rate is higher than for installations outside an enterprise. {% endif %} @@ -78,13 +73,13 @@ Os limites de taxa para as solicitações de servidor para servidor feitas por { {% ifversion fpt or ghec %} -### Limites de taxa padrão de usuário para servidor para {% data variables.product.prodname_ghe_cloud %} +### User-to-server rate limits for {% data variables.product.prodname_ghe_cloud %} {% data reusables.apps.user-to-server-rate-limits-ghec %} {% endif %} -## Leitura adicional +## Further reading -- "[Limitação de taxa](/rest/overview/resources-in-the-rest-api#rate-limiting)" na documentação da API REST -- "[Limitações de recursos](/graphql/overview/resource-limitations)" na documentação da API do GraphQL +- "[Rate limiting](/rest/overview/resources-in-the-rest-api#rate-limiting)" in the REST API documentation +- "[Resource limitations](/graphql/overview/resource-limitations)" in the GraphQL API documentation diff --git a/translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md index 0ee7787bc9..9ed610b338 100644 --- a/translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md +++ b/translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md @@ -1,5 +1,5 @@ --- -title: Autorizando Aplicativos OAuth +title: Authorizing OAuth Apps intro: '{% data reusables.shortdesc.authorizing_oauth_apps %}' redirect_from: - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-authorization-options-for-oauth-apps @@ -16,73 +16,67 @@ versions: ghec: '*' topics: - OAuth Apps -ms.openlocfilehash: 10aa111156377c08f0dc4ad0210cf8ad30b8a3ac -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717786' --- -A implementação do OAuth feita pelo {% data variables.product.product_name %} dá suporte ao [tipo de concessão de código de autorização](https://tools.ietf.org/html/rfc6749#section-4.1) padrão e à [Concessão de Autorização de Dispositivo](https://tools.ietf.org/html/rfc8628) OAuth 2.0 para aplicativos que não têm acesso a um navegador da Web. +{% data variables.product.product_name %}'s OAuth implementation supports the standard [authorization code grant type](https://tools.ietf.org/html/rfc6749#section-4.1) and the OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628) for apps that don't have access to a web browser. -Caso deseje ignorar a autorização do seu aplicativo da forma padrão, como no teste do aplicativo, use o [fluxo de aplicativo não Web](#non-web-application-flow). +If you want to skip authorizing your app in the standard way, such as when testing your app, you can use the [non-web application flow](#non-web-application-flow). -Para autorizar o seu aplicativo OAuth, considere qual fluxo de autorização melhor se adequa ao seu aplicativo. +To authorize your OAuth app, consider which authorization flow best fits your app. -- [Fluxo de aplicativo Web](#web-application-flow): usado para autorizar usuários em aplicativos OAuth padrão executados no navegador. (Não há suporte para o [tipo de concessão implícita](https://tools.ietf.org/html/rfc6749#section-4.2)). -- [fluxo de dispositivo](#device-flow): usado para aplicativos sem periféricos, como ferramentas da CLI. +- [web application flow](#web-application-flow): Used to authorize users for standard OAuth apps that run in the browser. (The [implicit grant type](https://tools.ietf.org/html/rfc6749#section-4.2) is not supported.) +- [device flow](#device-flow): Used for headless apps, such as CLI tools. -## Fluxo do aplicativo web +## Web application flow {% note %} -**Observação:** se você estiver criando um Aplicativo do GitHub, ainda poderá usar o fluxo de aplicativo Web OAuth, mas a configuração traz algumas diferenças importantes. Confira "[Como identificar e autorizar usuários nos Aplicativos do GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" para obter mais informações. +**Note:** If you are building a GitHub App, you can still use the OAuth web application flow, but the setup has some important differences. See "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information. {% endnote %} -O fluxo do aplicativo web para autorizar os usuários para seu aplicativo é: +The web application flow to authorize users for your app is: -1. Os usuários são redirecionados para solicitar sua identidade do GitHub -2. Os usuários são redirecionados de volta para o seu site pelo GitHub -3. Seu aplicativo acessa a API com o token de acesso do usuário +1. Users are redirected to request their GitHub identity +2. Users are redirected back to your site by GitHub +3. Your app accesses the API with the user's access token -### 1. Solicitar a identidade do GitHub de um usuário +### 1. Request a user's GitHub identity GET {% data variables.product.oauth_host_code %}/login/oauth/authorize -Quando seu Aplicativo do GitHub especifica um parâmetro `login`, ele mostra um prompt para os usuários com uma conta específica que eles podem usar para se conectarem e autorizar seu aplicativo. +When your GitHub App specifies a `login` parameter, it prompts users with a specific account they can use for signing in and authorizing your app. -#### Parâmetros +#### Parameters -Nome | Tipo | Descrição +Name | Type | Description -----|------|-------------- -`client_id`|`string` | **Obrigatório**. A ID do cliente recebida do GitHub quando você {% ifversion fpt or ghec %}[o registrou](https://github.com/settings/applications/new){% else %}o registrou{% endif %}. -`redirect_uri`|`string` | A URL no seu aplicativo para o qual os usuários serão enviados após a autorização. Veja detalhes abaixo sobre as [URLs de redirecionamento](#redirect-urls). -`login` | `string` | Sugere uma conta específica para iniciar a sessão e autorizar o aplicativo. -`scope`|`string` | Uma lista de [escopos](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/) delimitada por espaço. Caso ela não seja fornecida, o `scope` usa como padrão uma lista vazia para os usuários que não autorizaram nenhum escopo no aplicativo. Para usuários que têm escopos autorizados para o aplicativo, a página de autorização OAuth com a lista de escopos não será exibida para o usuário. Em vez disso, esta etapa do fluxo será concluída automaticamente com o conjunto de escopos que o usuário autorizou para o aplicativo. Por exemplo, se um usuário já executou o fluxo da Web duas vezes e autorizou um token com o escopo `user` e outro token com o escopo `repo`, um terceiro fluxo da Web que não fornece um `scope` recebe um token com o escopo `user` e `repo`. +`client_id`|`string` | **Required**. The client ID you received from GitHub when you {% ifversion fpt or ghec %}[registered](https://github.com/settings/applications/new){% else %}registered{% endif %}. +`redirect_uri`|`string` | The URL in your application where users will be sent after authorization. See details below about [redirect urls](#redirect-urls). +`login` | `string` | Suggests a specific account to use for signing in and authorizing the app. +`scope`|`string` | A space-delimited list of [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). If not provided, `scope` defaults to an empty list for users that have not authorized any scopes for the application. For users who have authorized scopes for the application, the user won't be shown the OAuth authorization page with the list of scopes. Instead, this step of the flow will automatically complete with the set of scopes the user has authorized for the application. For example, if a user has already performed the web flow twice and has authorized one token with `user` scope and another token with `repo` scope, a third web flow that does not provide a `scope` will receive a token with `user` and `repo` scope. `state` | `string` | {% data reusables.apps.state_description %} -`allow_signup`|`string` | Independentemente de os usuários serem autenticados, eles receberão uma opção para inscrever-se no GitHub durante o fluxo do OAuth. O padrão é `true`. Use `false` quando uma política proibir inscrições. +`allow_signup`|`string` | Whether or not unauthenticated users will be offered an option to sign up for GitHub during the OAuth flow. The default is `true`. Use `false` when a policy prohibits signups. -### 2. Os usuários são redirecionados para seu site pelo GitHub +### 2. Users are redirected back to your site by GitHub -Se o usuário aceitar sua solicitação, o {% data variables.product.product_name %} o redirecionará novamente para seu site com um `code` temporário em um parâmetro de código, bem como o estado que você forneceu na etapa anterior em um parâmetro `state`. O código temporário irá expirar após 10 minutos. Se os estados não corresponderem, significa que uma terceira criou a solicitação, e você deverá abortar o processo. +If the user accepts your request, {% data variables.product.product_name %} redirects back to your site with a temporary `code` in a code parameter as well as the state you provided in the previous step in a `state` parameter. The temporary code will expire after 10 minutes. If the states don't match, then a third party created the request, and you should abort the process. -Troque este `code` por um token de acesso: +Exchange this `code` for an access token: POST {% data variables.product.oauth_host_code %}/login/oauth/access_token -#### Parâmetros +#### Parameters -Nome | Tipo | Descrição +Name | Type | Description -----|------|-------------- -`client_id` | `string` | **Necessário.** A ID do cliente que você recebeu do {% data variables.product.product_name %} referente ao seu {% data variables.product.prodname_oauth_app %}. -`client_secret` | `string` | **Necessário.** O segredo do cliente que você recebeu do {% data variables.product.product_name %} referente ao seu {% data variables.product.prodname_oauth_app %}. -`code` | `string` | **Necessário.** O código que você recebeu como resposta à Etapa 1. -`redirect_uri` | `string` | A URL do seu aplicativo para onde os usuários são enviados após a autorização. +`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}. +`client_secret` | `string` | **Required.** The client secret you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}. +`code` | `string` | **Required.** The code you received as a response to Step 1. +`redirect_uri` | `string` | The URL in your application where users are sent after authorization. -#### Resposta +#### Response -Por padrão, a resposta assume o seguinte formato: +By default, the response takes the following form: ``` access_token=gho_16C7e42F292c6912E7710c838347Ae178B4a&scope=repo%2Cgist&token_type=bearer @@ -108,57 +102,57 @@ Accept: application/xml ``` -### 3. Usar o token de acesso para acessar a API +### 3. Use the access token to access the API -O token de acesso permite que você faça solicitações para a API em nome de um usuário. +The access token allows you to make requests to the API on a behalf of a user. Authorization: Bearer OAUTH-TOKEN GET {% data variables.product.api_url_code %}/user -Por exemplo, no cURL você pode definir o cabeçalho de autorização da seguinte forma: +For example, in curl you can set the Authorization header like this: ```shell curl -H "Authorization: Bearer OAUTH-TOKEN" {% data variables.product.api_url_pre %}/user ``` -## Fluxo de dispositivo +## Device flow {% note %} -**Observação:** o fluxo do dispositivo está em versão beta pública e sujeito a alterações. +**Note:** The device flow is in public beta and subject to change. {% endnote %} -O fluxo de dispositivos permite que você autorize usuários para um aplicativo sem cabeçalho, como uma ferramenta de CLI ou um gerenciador de credenciais do Git. +The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager. {% ifversion device-flow-is-opt-in %} -Antes de usar o fluxo do dispositivo para autorizar e identificar usuários, primeiro habilite-o nas configurações do aplicativo. Para obter mais informações sobre como habilitar o fluxo de dispositivo no seu aplicativo, confira "[Como modificar um Aplicativo OAuth](/developers/apps/managing-oauth-apps/modifying-an-oauth-app)" para Aplicativos OAuth e "[Como modificar um Aplicativo do GitHub](/developers/apps/managing-github-apps/modifying-a-github-app)" para Aplicativos do GitHub. +Before you can use the device flow to authorize and identify users, you must first enable it in your app's settings. For more information about enabling the device flow in your app, see "[Modifying an OAuth App](/developers/apps/managing-oauth-apps/modifying-an-oauth-app)" for OAuth Apps and "[Modifying a GitHub App](/developers/apps/managing-github-apps/modifying-a-github-app)" for GitHub Apps. {% endif %} -### Visão geral do fluxo do dispositivo +### Overview of the device flow -1. O seu aplicativo solicita o dispositivo e o código de verificação do usuário e obtém a URL de autorização em que o usuário digitará o código de verificação do usuário. -2. O aplicativo solicita que o usuário insira um código de verificação em {% data variables.product.device_authorization_url %}. -3. O aplicativo pesquisa status de autenticação do usuário. Uma vez que o usuário tenha autorizado o dispositivo, o aplicativo poderá fazer chamadas de API com um novo token de acesso. +1. Your app requests device and user verification codes and gets the authorization URL where the user will enter the user verification code. +2. The app prompts the user to enter a user verification code at {% data variables.product.device_authorization_url %}. +3. The app polls for the user authentication status. Once the user has authorized the device, the app will be able to make API calls with a new access token. -### Passo 1: O aplicativo solicita o dispositivo e os códigos de verificação de usuário do GitHub +### Step 1: App requests the device and user verification codes from GitHub POST {% data variables.product.oauth_host_code %}/login/device/code -O seu aplicativo deve solicitar um código de verificação e uma URL de verificação que o aplicativo usará para solicitar que o usuário seja autenticado na próxima etapa. Essa solicitação também retorna um código de verificação de dispositivo que o aplicativo deve usar para receber um token de acesso e verificar o status da autenticação do usuário. +Your app must request a user verification code and verification URL that the app will use to prompt the user to authenticate in the next step. This request also returns a device verification code that the app must use to receive an access token and check the status of user authentication. -#### Parâmetros de Entrada +#### Input Parameters -Nome | Tipo | Descrição +Name | Type | Description -----|------|-------------- -`client_id` | `string` | **Necessário.** A ID do cliente que você recebeu do {% data variables.product.product_name %} para seu aplicativo. -`scope` | `string` | O escopo ao qual o seu aplicativo está solicitando acesso. +`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your app. +`scope` | `string` | The scope that your app is requesting access to. -#### Resposta +#### Response -Por padrão, a resposta assume o seguinte formato: +By default, the response takes the following form: ``` device_code=3584d83530557fdd1f46af8289938c8ef79f9dc5&expires_in=900&interval=5&user_code=WDJB-MJHT&verification_uri=https%3A%2F%{% data variables.product.product_url %}%2Flogin%2Fdevice @@ -188,43 +182,43 @@ Accept: application/xml ``` -#### Parâmetros de resposta +#### Response parameters -Nome | Tipo | Descrição +Name | Type | Description -----|------|-------------- -`device_code` | `string` | O código de verificação do dispositivo tem 40 caracteres e é usado para verificar o dispositivo. -`user_code` | `string` | O código de verificação do usuário é exibido no dispositivo para que o usuário possa inserir o código no navegador. Este código tem 8 caracteres com um hífen no meio. -`verification_uri` | `string` | A URL de verificação em que os usuários devem inserir o `user_code`: {% data variables.product.device_authorization_url %}. -`expires_in` | `integer`| O número de segundos antes que o `device_code` e o `user_code` expirem. O padrão é 900 segundos ou 15 minutos. -`interval` | `integer` | O número mínimo de segundos que precisa transcorrer para que você possa fazer uma nova solicitação de token de acesso (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) a fim de concluir a autorização do dispositivo. Por exemplo, se o intervalo for 5, você não poderá fazer uma nova solicitação a partir de 5 segundos. Se você fizer mais de uma solicitação em cinco segundos, atingirá o limite de taxa e receberá o erro `slow_down`. +`device_code` | `string` | The device verification code is 40 characters and used to verify the device. +`user_code` | `string` | The user verification code is displayed on the device so the user can enter the code in a browser. This code is 8 characters with a hyphen in the middle. +`verification_uri` | `string` | The verification URL where users need to enter the `user_code`: {% data variables.product.device_authorization_url %}. +`expires_in` | `integer`| The number of seconds before the `device_code` and `user_code` expire. The default is 900 seconds or 15 minutes. +`interval` | `integer` | The minimum number of seconds that must pass before you can make a new access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) to complete the device authorization. For example, if the interval is 5, then you cannot make a new request until 5 seconds pass. If you make more than one request over 5 seconds, then you will hit the rate limit and receive a `slow_down` error. -### Passo 2: Solicite ao usuário que insira o código do usuário em um navegador +### Step 2: Prompt the user to enter the user code in a browser -O seu dispositivo mostrará o código de verificação do usuário e solicitará que o usuário insira o código em {% data variables.product.device_authorization_url %}. +Your device will show the user verification code and prompt the user to enter the code at {% data variables.product.device_authorization_url %}. - ![Campo para digitar o código de verificação do usuário exibido no seu dispositivo](/assets/images/github-apps/device_authorization_page_for_user_code.png) + ![Field to enter the user verification code displayed on your device](/assets/images/github-apps/device_authorization_page_for_user_code.png) -### Passo 3: O aplicativo solicita que o GitHub verifique se o usuário autorizou o dispositivo +### Step 3: App polls GitHub to check if the user authorized the device POST {% data variables.product.oauth_host_code %}/login/oauth/access_token -Seu aplicativo fará solicitações de autorização de dispositivo que sondam `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`, até que os códigos de usuário e de dispositivo expirem ou o usuário autorize o aplicativo com sucesso com um código de usuário válido. O aplicativo precisa usar o `interval` mínimo de sondagem recuperado na etapa 1 para evitar erros de limite de taxa. Para obter mais informações, confira "[Limites de taxa para o fluxo de dispositivo](#rate-limits-for-the-device-flow)". +Your app will make device authorization requests that poll `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`, until the device and user codes expire or the user has successfully authorized the app with a valid user code. The app must use the minimum polling `interval` retrieved in step 1 to avoid rate limit errors. For more information, see "[Rate limits for the device flow](#rate-limits-for-the-device-flow)." -O usuário deve inserir um código válido em de 15 minutos (ou 900 segundos). Após 15 minutos, você precisará solicitar um novo código de autorização do dispositivo com `POST {% data variables.product.oauth_host_code %}/login/device/code`. +The user must enter a valid code within 15 minutes (or 900 seconds). After 15 minutes, you will need to request a new device authorization code with `POST {% data variables.product.oauth_host_code %}/login/device/code`. -Uma vez que o usuário tenha autorizado, o aplicativo receberá um token de acesso que poderá ser usado para fazer solicitações para a API em nome de um usuário. +Once the user has authorized, the app will receive an access token that can be used to make requests to the API on behalf of a user. -#### Parâmetros de entrada +#### Input parameters -Nome | Tipo | Descrição +Name | Type | Description -----|------|-------------- -`client_id` | `string` | **Necessário.** A ID do cliente que você recebeu do {% data variables.product.product_name %} referente ao seu {% data variables.product.prodname_oauth_app %}. -`device_code` | `string` | **Necessário.** O código de verificação do dispositivo que você recebeu da solicitação `POST {% data variables.product.oauth_host_code %}/login/device/code`. -`grant_type` | `string` | **Necessário.** O tipo de concessão precisa ser `urn:ietf:params:oauth:grant-type:device_code`. +`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}. +`device_code` | `string` | **Required.** The device verification code you received from the `POST {% data variables.product.oauth_host_code %}/login/device/code` request. +`grant_type` | `string` | **Required.** The grant type must be `urn:ietf:params:oauth:grant-type:device_code`. -#### Resposta +#### Response -Por padrão, a resposta assume o seguinte formato: +By default, the response takes the following form: ``` access_token=gho_16C7e42F292c6912E7710c838347Ae178B4a&token_type=bearer&scope=repo%2Cgist @@ -250,76 +244,88 @@ Accept: application/xml ``` -### Limites de taxa para o fluxo do dispositivo +### Rate limits for the device flow -Quando um usuário envia o código de verificação no navegador, há um limite de taxa de 50 envios por hora por aplicativo. +When a user submits the verification code on the browser, there is a rate limit of 50 submissions in an hour per application. -Se você fizer mais de uma solicitação de token de acesso (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) dentro do período mínimo necessário entre solicitações (ou `interval`), atingirá o limite de taxa e receberá a resposta de erro `slow_down`. A resposta de erro `slow_down` adiciona cinco segundos ao último `interval`. Para obter mais informações, confira os [Erros do fluxo de dispositivo](#errors-for-the-device-flow). +If you make more than one access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) within the required minimum timeframe between requests (or `interval`), you'll hit the rate limit and receive a `slow_down` error response. The `slow_down` error response adds 5 seconds to the last `interval`. For more information, see the [Errors for the device flow](#errors-for-the-device-flow). -### Códigos de erro para o fluxo do dispositivo +### Error codes for the device flow -| Código do erro | Descrição | +| Error code | Description | |----|----| -| `authorization_pending`| Este erro ocorre quando a solicitação de autorização está pendente e o usuário ainda não inseriu o código do usuário. É esperado que o aplicativo continue sondando a solicitação `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` sem exceder o [`interval`](#response-parameters), o que exige um número mínimo de segundos entre cada solicitação. | -| `slow_down` | Quando você recebe o erro `slow_down`, cinco segundos extras são adicionados ao `interval` ou ao período mínimo necessário entre as solicitações por meio de `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. Por exemplo, se o intervalo inicial exigir, pelo menos, cinco segundos entre as solicitações e você receber a resposta de erro `slow_down`, você precisará aguardar, no mínimo, dez segundos antes de fazer uma nova solicitação para um token de acesso OAuth. A resposta de erro inclui o novo `interval` que você precisa usar. -| `expired_token` | Se o código do dispositivo expirar, você verá o erro `token_expired`. Você deve fazer uma nova solicitação para um código de dispositivo. -| `unsupported_grant_type` | O tipo de concessão precisa ser `urn:ietf:params:oauth:grant-type:device_code` e precisa ser incluído como um parâmetro de entrada quando a solicitação de token OAuth `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` é sondada. -| `incorrect_client_credentials` | Para o fluxo do dispositivo, você deve passar o ID de cliente do aplicativo, que pode ser encontrado na página de configurações do aplicativo. O `client_secret` não é necessário para o fluxo de dispositivo. -| `incorrect_device_code` | O device_code fornecido não é válido. -| `access_denied` | Quando um usuário clicar em Cancelar durante o processo de autorização, você receberá o erro `access_denied` e o usuário não poderá usar o código de verificação novamente.{% ifversion device-flow-is-opt-in %} -| `device_flow_disabled` | O fluxo do dispositivo não foi habilitado nas configurações do aplicativo. Para obter mais informações, confira "[Fluxo de dispositivo](#device-flow)".{% endif %} +| `authorization_pending`| This error occurs when the authorization request is pending and the user hasn't entered the user code yet. The app is expected to keep polling the `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` request without exceeding the [`interval`](#response-parameters), which requires a minimum number of seconds between each request. | +| `slow_down` | When you receive the `slow_down` error, 5 extra seconds are added to the minimum `interval` or timeframe required between your requests using `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. For example, if the starting interval required at least 5 seconds between requests and you get a `slow_down` error response, you must now wait a minimum of 10 seconds before making a new request for an OAuth access token. The error response includes the new `interval` that you must use. +| `expired_token` | If the device code expired, then you will see the `token_expired` error. You must make a new request for a device code. +| `unsupported_grant_type` | The grant type must be `urn:ietf:params:oauth:grant-type:device_code` and included as an input parameter when you poll the OAuth token request `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. +| `incorrect_client_credentials` | For the device flow, you must pass your app's client ID, which you can find on your app settings page. The `client_secret` is not needed for the device flow. +| `incorrect_device_code` | The device_code provided is not valid. +| `access_denied` | When a user clicks cancel during the authorization process, you'll receive a `access_denied` error and the user won't be able to use the verification code again.{% ifversion device-flow-is-opt-in %} +| `device_flow_disabled` | Device flow has not been enabled in the app's settings. For more information, see "[Device flow](#device-flow)."{% endif %} -Para obter mais informações, confira a "[Concessão de Autorização de Dispositivo OAuth 2.0](https://tools.ietf.org/html/rfc8628#section-3.5)". +For more information, see the "[OAuth 2.0 Device Authorization Grant](https://tools.ietf.org/html/rfc8628#section-3.5)." -## Fluxo do aplicativo que não são da web +## Non-Web application flow -A autenticação que não é da web está disponível para situações limitadas como testes. Se necessário, use a [Autenticação Básica](/rest/overview/other-authentication-methods#basic-authentication) para criar um token de acesso pessoal usando a [página Configurações de tokens de acesso pessoal](/articles/creating-an-access-token-for-command-line-use). Essa técnica permite ao usuário revogar o acesso a qualquer momento. +Non-web authentication is available for limited situations like testing. If you need to, you can use [Basic Authentication](/rest/overview/other-authentication-methods#basic-authentication) to create a {% data variables.product.pat_generic %} using your [{% data variables.product.pat_generic %}s settings page](/articles/creating-an-access-token-for-command-line-use). This technique enables the user to revoke access at any time. -{% ifversion fpt or ghes or ghec %} {% note %} +{% ifversion fpt or ghes or ghec %} +{% note %} -**Observação:** ao usar o fluxo de aplicativo não Web para criar um token OAuth2, verifique se você entendeu como [usar a autenticação de dois fatores](/rest/overview/other-authentication-methods#working-with-two-factor-authentication) se você ou os usuários têm a autenticação de dois fatores habilitada. +**Note:** When using the non-web application flow to create an OAuth2 token, make sure to understand how to [work with +two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication) if +you or your users have two-factor authentication enabled. -{% endnote %} {% endif %} +{% endnote %} +{% endif %} -## URLs de redirecionamento +## Redirect URLs -O `redirect_uri` é opcional. Se ignorado, o GitHub redirecionará os usuários para a URL de retorno de chamada definida nas configurações do Aplicativo OAuth. Se fornecido, o host e a porta da URL de redirecionamento precisará exatamente corresponder à URL de retorno de chamada. O caminho da URL de redirecionamento precisa referenciar um subdiretório da URL de retorno de chamada. +The `redirect_uri` parameter is optional. If left out, GitHub will +redirect users to the callback URL configured in the OAuth Application +settings. If provided, the redirect URL's host (excluding sub-domains) and port must exactly +match the callback URL. The redirect URL's path must reference a +subdirectory of the callback URL. CALLBACK: http://example.com/path GOOD: http://example.com/path GOOD: http://example.com/path/subdir/other + GOOD: http://oauth.example.com/path + GOOD: http://oauth.example.com/path/subdir/other BAD: http://example.com/bar BAD: http://example.com/ BAD: http://example.com:8080/path BAD: http://oauth.example.com:8080/path BAD: http://example.org -### URLs de redirecionamento do Localhost +### Loopback redirect urls -O parâmetro opcional `redirect_uri` também pode ser usado para URLs do localhost. Se o aplicativo especificar uma URL do localhost e uma porta, após a autorização, os usuários do aplicativo serão redirecionados para a URL e porta fornecidas. O `redirect_uri` não precisa corresponder à porta especificada na URL de retorno de chamada do aplicativo. +The optional `redirect_uri` parameter can also be used for loopback URLs. If the application specifies a loopback URL and a port, then after authorizing the application users will be redirected to the provided URL and port. The `redirect_uri` does not need to match the port specified in the callback URL for the app. -Para a URL de retorno de chamada `http://127.0.0.1/path`, use este `redirect_uri`: +For the `http://127.0.0.1/path` callback URL, you can use this `redirect_uri`: ``` http://127.0.0.1:1234/path ``` -## Criar vários tokens para aplicativos OAuth +Note that OAuth RFC [recommends not to use `localhost`](https://datatracker.ietf.org/doc/html/rfc8252#section-7.3), but instead to use loopback literal `127.0.0.1` or IPv6 `::1`. -Você pode criar vários tokens para uma combinação de usuário/aplicativo/escopo para criar tokens para casos de uso específicos. +## Creating multiple tokens for OAuth Apps -Isso é útil se o seu aplicativo OAuth for compatível com um fluxo de trabalho que usa o GitHub para iniciar sessão e exigir apenas informações básicas do usuário. Outro fluxo de trabalho pode exigir acesso aos repositórios privados de um usuário. Ao usar vários tokens, o seu aplicativo OAuth pode realizar o fluxo web para cada caso, solicitando apenas os escopos necessários. Se um usuário usar apenas seu aplicativo para iniciar a sessão, ele nunca será obrigado a conceder acesso do aplicativo OAuth aos seus repositórios privados. +You can create multiple tokens for a user/application/scope combination to create tokens for specific use cases. + +This is useful if your OAuth App supports one workflow that uses GitHub for sign-in and only requires basic user information. Another workflow may require access to a user's private repositories. Using multiple tokens, your OAuth App can perform the web flow for each use case, requesting only the scopes needed. If a user only uses your application to sign in, they are never required to grant your OAuth App access to their private repositories. {% data reusables.apps.oauth-token-limit %} {% data reusables.apps.deletes_ssh_keys %} -## Direcionar os usuários para revisar seus acessos +## Directing users to review their access -Você pode vincular informações sobre a autorização de um aplicativo OAuth para que os usuários possam revisar e revogar as autorizações do seu aplicativo. +You can link to authorization information for an OAuth App so that users can review and revoke their application authorizations. -Para criar esse link, você precisará da `client_id` dos Aplicativos OAuth que recebeu do GitHub quando registrou o aplicativo. +To build this link, you'll need your OAuth Apps `client_id` that you received from GitHub when you registered the application. ``` {% data variables.product.oauth_host_code %}/settings/connections/applications/:client_id @@ -327,17 +333,17 @@ Para criar esse link, você precisará da `client_id` dos Aplicativos OAuth que {% tip %} -**Dica:** para saber mais sobre os recursos que o Aplicativo OAuth pode acessar para um usuário, confira "[Como descobrir recursos para um usuário](/rest/guides/discovering-resources-for-a-user)". +**Tip:** To learn more about the resources that your OAuth App can access for a user, see "[Discovering resources for a user](/rest/guides/discovering-resources-for-a-user)." {% endtip %} -## Solução de problemas +## Troubleshooting -* "[Solução de problemas de erros de solicitação de autorização](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)" -* "[Solução de problemas de erros de solicitação de token de acesso do Aplicativo OAuth](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)" -* "[Erros de fluxo de dispositivo](#error-codes-for-the-device-flow)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %} -* "[Expiração e revogação de um token](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} +* "[Troubleshooting authorization request errors](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)" +* "[Troubleshooting OAuth App access token request errors](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)" +* "[Device flow errors](#error-codes-for-the-device-flow)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %} +* "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} -## Leitura adicional +## Further reading -- "[Sobre a autenticação no {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)" +- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)" diff --git a/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md b/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md index 9c2913c32f..cca12402c8 100644 --- a/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md +++ b/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md @@ -1,5 +1,5 @@ --- -title: Escopos para aplicativos OAuth +title: Scopes for OAuth Apps intro: '{% data reusables.shortdesc.understanding_scopes_for_oauth_apps %}' redirect_from: - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps @@ -13,24 +13,18 @@ versions: ghec: '*' topics: - OAuth Apps -ms.openlocfilehash: e7d943c95dc3d8fea6e025cbae8c5b65f9ccf864 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717938' --- -Ao configurar um aplicativo OAuth no GitHub, os escopos solicitados são exibidos para o usuário no formulário de autorização. +When setting up an OAuth App on GitHub, requested scopes are displayed to the user on the authorization form. {% note %} -**Observação:** se você estiver criando um Aplicativo no GitHub, não precisará fornecer escopos na sua solicitação de autorização. Para obter mais informações sobre isso, confira "[Como identificar e autorizar usuários para Aplicativos do GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". +**Note:** If you're building a GitHub App, you don’t need to provide scopes in your authorization request. For more on this, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." {% endnote %} -Se seu {% data variables.product.prodname_oauth_app %} não tiver acesso a um navegador, como uma ferramenta de CLI, você não precisará especificar um escopo para que os usuários efetuem a autenticação no seu aplicativo. Para obter mais informações, confira "[Como autorizar Aplicativos OAuth](/developers/apps/authorizing-oauth-apps#device-flow)". +If your {% data variables.product.prodname_oauth_app %} doesn't have access to a browser, such as a CLI tool, then you don't need to specify a scope for users to authenticate to your app. For more information, see "[Authorizing OAuth apps](/developers/apps/authorizing-oauth-apps#device-flow)." -Verifique os cabeçalhos para ver quais escopos do OAuth você tem e o que a ação da API aceita: +Check headers to see what OAuth scopes you have, and what the API action accepts: ```shell $ curl -H "Authorization: Bearer OAUTH-TOKEN" {% data variables.product.api_url_pre %}/users/codertocat -I @@ -39,40 +33,58 @@ X-OAuth-Scopes: repo, user X-Accepted-OAuth-Scopes: user ``` -* `X-OAuth-Scopes` lista os escopos autorizados pelo token. -* `X-Accepted-OAuth-Scopes` lista os escopos verificados pela ação. +* `X-OAuth-Scopes` lists the scopes your token has authorized. +* `X-Accepted-OAuth-Scopes` lists the scopes that the action checks for. -## Escopos disponíveis +## Available scopes -Nome   Descrição ----- ----------- {% ifversion not ghae %} **`(no scope)`**   Concede acesso somente leitura a informações públicas (incluindo informações de perfil do usuário, informações do repositório e gists){% endif %}{% ifversion ghes or ghae %} **`site_admin`**   Concede aos administradores do site acesso aos pontos de extremidade da API de Administração do [{% data variables.product.prodname_ghe_server %}](/rest/reference/enterprise-admin).{% endif %} **`repo`**   Concede acesso completo a repositórios públicos{% ifversion ghec or ghes or ghae %}, internos{% endif %} e privados, incluindo acesso de leitura e gravação a códigos, status de commit, convites de repositório, colaboradores, status de implantação e webhooks de repositório. **Observação**: além dos recursos relacionados ao repositório, o escopo do `repo` também concede acesso para gerenciar recursos de propriedade da organização, incluindo projetos, convites, associações de equipe e webhooks. Esse escopo também concede a capacidade de gerenciar projetos pertencentes aos usuários. - `repo:status`| Permite o acesso de leitura/gravação para fazer commit de status em {% ifversion fpt %}repositórios públicos e privados{% elsif ghec or ghes %}público, privados e internos{% elsif ghae %}privados e internos{% endif %}. Esse escopo só é necessário para permitir a outros usuários ou serviços acesso aos status de commit de repositórios privados *sem* permitir acesso ao código. - `repo_deployment`| Permite o acesso aos [status de implantação](/rest/reference/repos#deployments) de repositórios {% ifversion not ghae %}públicos{% else %}internos{% endif %} e privados. Esse escopo só é necessário para permitir a outros usuários ou serviços acesso aos status de implantação *sem* permitir acesso ao código.{% ifversion not ghae %}  `public_repo`| Limita o acesso aos repositórios públicos. Isso inclui acesso de leitura/gravação em código, status de commit, projetos de repositório, colaboradores e status de implantação de repositórios e organizações públicos. Também é necessário para os repositórios públicos marcados com estrela.{% endif %}  `repo:invite` | Permite a capacidade de aceitação/recusa de convites para colaboração em um repositório. Esse escopo só é necessário para permitir a outros usuários ou serviços acesso a convites *sem* permitir acesso ao código.{% ifversion fpt or ghes or ghec %}  `security_events` | Permite:
acesso de leitura e gravação a eventos de segurança na [API de {% data variables.product.prodname_code_scanning %}](/rest/reference/code-scanning) {%- ifversion ghec %}
acesso de leitura e gravação a eventos de segurança na [API de {% data variables.product.prodname_secret_scanning %}](/rest/reference/secret-scanning){%- endif %}
Esse escopo só é necessário para permitir a outros usuários ou serviços acesso a eventos de segurança *sem* permitir acesso ao código.{% endif %} **`admin:repo_hook`** | Permite o acesso de leitura, gravação, ping e exclusão a ganchos de repositório em repositórios {% ifversion fpt %}públicos ou privados{% elsif ghec or ghes %}públicos, privados ou internos{% elsif ghae %}privados ou internos{% endif %}. Os escopos do `repo` {% ifversion fpt or ghec or ghes %}e do `public_repo` permitem{% else %}O escopo deles permite{% endif %} o acesso completo aos repositórios, incluindo ganchos de repositório. Use o escopo `admin:repo_hook` para limitar o acesso apenas aos ganchos de repositório. - `write:repo_hook` | Permite o acesso de leitura, gravação e ping aos ganchos em repositórios {% ifversion fpt %}públicos ou privados{% elsif ghec or ghes %}públicos, privados ou internos{% elsif ghae %}privados ou internos{% endif %}. - `read:repo_hook`| Permite o acesso de leitura e ping aos ganchos em repositórios {% ifversion fpt %}públicos ou privados{% elsif ghec or ghes %}públicos, privados ou internos{% elsif ghae %}privados ou internos{% endif %}. -**`admin:org`** | Gerencia por completo a organização e as respectivas equipes, projetos e associações. - `write:org`| Acesso de leitura e gravação à associação à organização, aos projetos da organização e à associação à equipe. - `read:org`| Acesso somente leitura à associação à organização, aos projetos da organização e à associação à equipe. -**`admin:public_key`** | Gerenciar por completo as chaves públicas. - `write:public_key`| Criar, listar e ver detalhes das chaves públicas. - `read:public_key`| Listar e ver detalhes das chaves públicas. -**`admin:org_hook`** | Permite o acesso de leitura, gravação, ping e exclusão de ganchos da organização. **Observação:** os tokens OAuth só poderão executar essas ações nos ganchos da organização que foram criados pelo Aplicativo OAuth. Os tokens de acesso pessoal só poderão realizar essas ações nos hooks da organização criados por um usuário. -**`gist`** | Permite o acesso de gravação nos gists. -**`notifications`** | Permite:
* o acesso de leitura às notificações de um usuário
* acesso de marcação como lido em threads
* acesso de inspeção e cancelamento de inspeção em um repositório e
* acesso de leitura, gravação e exclusão em assinaturas de thread. -**`user`** | Permite o acesso de leitura/gravação apenas nas informações do perfil. Observe que esse escopo inclui `user:email` e `user:follow`. - `read:user`| Permite o acesso para ler as informações do perfil de um usuário. - `user:email`| Permite o acesso de leitura nos endereços de email de um usuário. - `user:follow`| Permite acesso para seguir ou deixar de seguir outros usuários.{% ifversion projects-oauth-scope %} **`project`** | Permite acesso de leitura/gravação a {% data variables.projects.projects_v2 %} de usuário e da organização (beta). - `read:project`| Permite acesso somente leitura a {% data variables.projects.projects_v2 %} de usuário e da organização (beta).{% endif %} **`delete_repo`** | Permite acesso para excluir repositórios administráveis. -**`write:discussion`** | Permite o acesso de leitura e gravação para discussões em equipe. - `read:discussion` | Permite o acesso de leitura para discussões em equipe. -**`write:packages`** | Concede acesso ao para fazer o upload ou publicação de um pacote no {% data variables.product.prodname_registry %}. Para obter mais informações, confira "[Como publicar um pacote](/github/managing-packages-with-github-packages/publishing-a-package)". -**`read:packages`** | Permite o acesso para baixar ou instalar pacotes do {% data variables.product.prodname_registry %}. Para obter mais informações, confira "[Como instalar um pacote](/github/managing-packages-with-github-packages/installing-a-package)". -**`delete:packages`** | Permite o acesso para excluir pacotes do {% data variables.product.prodname_registry %}. Para obter mais informações, confira "[Como excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package)". -**`admin:gpg_key`** | Gerenciar completamente as chaves GPG. - `write:gpg_key`| Criar, listar e ver detalhes das chaves GPG. - `read:gpg_key`| Listar e ver detalhes das chaves GPG.{% ifversion fpt or ghec %} **`codespace`** | Permite a capacidade de criar e gerenciar codespaces. Os codespaces podem expor um GITHUB_TOKEN que pode ter um conjunto diferente de escopos. Para obter mais informações, confira "[Segurança nos {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/security-in-github-codespaces#authentication)".{% endif %} **`workflow`** | Concede a capacidade de adicionar e atualizar arquivos de fluxo de trabalho do {% data variables.product.prodname_actions %}. Os arquivos do fluxo de trabalho podem ser confirmados sem este escopo se o mesmo arquivo (com o mesmo caminho e conteúdo) existir em outro branch no mesmo repositório. Os arquivos de fluxo de trabalho podem expor o `GITHUB_TOKEN` que pode ter um conjunto diferente de escopos. Para obter informações, confira "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."{% ifversion not fpt %} **`admin:enterprise`** | Fornece controle completo de funcionalidade corporativo. Para obter mais informações, confira "[Gerenciar contas corporativas](/graphql/guides/managing-enterprise-accounts)" na documentação da API do GraphQL.

Inclui `manage_runners:enterprise`{% ifversion ghec or ghes > 3.3 %}, `manage_billing:enterprise`,{% endif %} e `read:enterprise`.  `manage_runners:enterprise` | Fornece controle total sobre os corredores auto-hospedados dentro da empresa. Para obter mais informações, confira "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)". {% ifversion ghec or ghes > 3.3 %}  `manage_billing:enterprise` | Leia e grave dados de cobrança corporativos. Para obter mais informações, confira "[Cobrança](/rest/billing)" na documentação da API REST. {% endif %}  `read:enterprise` | Ler todos os dados em um perfil corporativo. Não inclui dados de perfil de membros corporativos ou organizações.{% endif %} {% note %} +Name | Description +-----|-----------|{% ifversion not ghae %} +**`(no scope)`** | Grants read-only access to public information (including user profile info, repository info, and gists){% endif %}{% ifversion ghes or ghae %} +**`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/rest/reference/enterprise-admin).{% endif %} +**`repo`** | Grants full access to public{% ifversion ghec or ghes or ghae %}, internal,{% endif %} and private repositories including read and write access to code, commit statuses, repository invitations, collaborators, deployment statuses, and repository webhooks. **Note**: In addition to repository related resources, the `repo` scope also grants access to manage organization-owned resources including projects, invitations, team memberships and webhooks. This scope also grants the ability to manage projects owned by users. + `repo:status`| Grants read/write access to commit statuses in {% ifversion fpt %}public and private{% elsif ghec or ghes %}public, private, and internal{% elsif ghae %}private and internal{% endif %} repositories. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code. + `repo_deployment`| Grants access to [deployment statuses](/rest/reference/repos#deployments) for {% ifversion not ghae %}public{% else %}internal{% endif %} and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code.{% ifversion not ghae %} + `public_repo`| Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories.{% endif %} + `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% ifversion fpt or ghes or ghec %} + `security_events` | Grants:
read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning) {%- ifversion ghec %}
read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning){%- endif %}
This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %} +**`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories. The `repo` {% ifversion fpt or ghec or ghes %}and `public_repo` scopes grant{% else %}scope grants{% endif %} full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks. + `write:repo_hook` | Grants read, write, and ping access to hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories. + `read:repo_hook`| Grants read and ping access to hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories. +**`admin:org`** | Fully manage the organization and its teams, projects, and memberships. + `write:org`| Read and write access to organization membership, organization projects, and team membership. + `read:org`| Read-only access to organization membership, organization projects, and team membership. +**`admin:public_key`** | Fully manage public keys. + `write:public_key`| Create, list, and view details for public keys. + `read:public_key`| List and view details for public keys. +**`admin:org_hook`** | Grants read, write, ping, and delete access to organization hooks. **Note:** OAuth tokens will only be able to perform these actions on organization hooks which were created by the OAuth App. {% data variables.product.pat_generic_caps %}s will only be able to perform these actions on organization hooks created by a user. +**`gist`** | Grants write access to gists. +**`notifications`** | Grants:
* read access to a user's notifications
* mark as read access to threads
* watch and unwatch access to a repository, and
* read, write, and delete access to thread subscriptions. +**`user`** | Grants read/write access to profile info only. Note that this scope includes `user:email` and `user:follow`. + `read:user`| Grants access to read a user's profile data. + `user:email`| Grants read access to a user's email addresses. + `user:follow`| Grants access to follow or unfollow other users.{% ifversion projects-oauth-scope %} +**`project`** | Grants read/write access to user and organization {% data variables.projects.projects_v2 %}. + `read:project`| Grants read only access to user and organization {% data variables.projects.projects_v2 %}.{% endif %} +**`delete_repo`** | Grants access to delete adminable repositories. +**`write:discussion`** | Allows read and write access for team discussions. + `read:discussion` | Allows read access for team discussions. +**`write:packages`** | Grants access to upload or publish a package in {% data variables.product.prodname_registry %}. For more information, see "[Publishing a package](/github/managing-packages-with-github-packages/publishing-a-package)". +**`read:packages`** | Grants access to download or install packages from {% data variables.product.prodname_registry %}. For more information, see "[Installing a package](/github/managing-packages-with-github-packages/installing-a-package)". +**`delete:packages`** | Grants access to delete packages from {% data variables.product.prodname_registry %}. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." +**`admin:gpg_key`** | Fully manage GPG keys. + `write:gpg_key`| Create, list, and view details for GPG keys. + `read:gpg_key`| List and view details for GPG keys.{% ifversion fpt or ghec %} +**`codespace`** | Grants the ability to create and manage codespaces. Codespaces can expose a GITHUB_TOKEN which may have a different set of scopes. For more information, see "[Security in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/security-in-github-codespaces#authentication)."{% endif %} +**`workflow`** | Grants the ability to add and update {% data variables.product.prodname_actions %} workflow files. Workflow files can be committed without this scope if the same file (with both the same path and contents) exists on another branch in the same repository. Workflow files can expose `GITHUB_TOKEN` which may have a different set of scopes. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."{% ifversion not fpt %} +**`admin:enterprise`** | Gives full control of enterprise functionality. For more information, see "[Managing enterprise accounts](/graphql/guides/managing-enterprise-accounts)" in the GraphQL API documentation.

Includes `manage_runners:enterprise`{% ifversion ghec or ghes > 3.3 %}, `manage_billing:enterprise`,{% endif %} and `read:enterprise`. + `manage_runners:enterprise` | Gives full control over self-hosted runners within the enterprise. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." {% ifversion ghec or ghes > 3.3 %} + `manage_billing:enterprise` | Read and write enterprise billing data. For more information, see "[Billing](/rest/billing)" in the REST API documentation. {% endif %} + `read:enterprise` | Read all data on an enterprise profile. Does not include profile data of enterprise members or organizations.{% endif %} +{% note %} -**Observação:** seu Aplicativo OAuth pode solicitar os escopos no redirecionamento inicial. Você pode especificar vários escopos separando-os com um espaço usando `%20`: +**Note:** Your OAuth App can request the scopes in the initial redirection. You +can specify multiple scopes by separating them with a space using `%20`: https://github.com/login/oauth/authorize? client_id=...& @@ -80,18 +92,31 @@ Nome   Descrição ----- ----------- {% ifversion not ghae %} **`(no scope {% endnote %} -## Escopos solicitados e escopos concedidos +## Requested scopes and granted scopes -O atributo `scope` lista os escopos anexados ao token que foram concedido pelo usuário. Normalmente, estes escopos são idênticos aos que você solicitou. -No entanto, os usuários podem editar os respectivos escopos, permitindo, efetivamente, ao seu aplicativo menos acesso do que você solicitou originalmente. Além disso, os usuários podem editar os escopos do token depois que o fluxo do OAuth for concluído. -Você deve estar ciente dessa possibilidade e ajustar o comportamento do seu aplicativo de acordo. +The `scope` attribute lists scopes attached to the token that were granted by +the user. Normally, these scopes will be identical to what you requested. +However, users can edit their scopes, effectively +granting your application less access than you originally requested. Also, users +can edit token scopes after the OAuth flow is completed. +You should be aware of this possibility and adjust your application's behavior +accordingly. -É importante lidar com casos de erro em que um usuário opta por permitir menos acesso do que você solicitou originalmente. Por exemplo, os aplicativos podem alertar ou comunicar os usuários de que eles terão a funcionalidade reduzida ou não poderão realizar algumas ações. +It's important to handle error cases where a user chooses to grant you +less access than you originally requested. For example, applications can warn +or otherwise communicate with their users that they will see reduced +functionality or be unable to perform some actions. -Além disso, os aplicativos sempre podem enviar os usuários novamente por meio do fluxo para obter permissão adicional, mas não se esqueça de que os usuários sempre podem recusar isso. +Also, applications can always send users back through the flow again to get +additional permission, but don’t forget that users can always say no. -Confira o [guia Conceitos básicos sobre autenticação](/guides/basics-of-authentication/), que fornece dicas sobre como lidar com escopos de token modificáveis. +Check out the [Basics of Authentication guide](/guides/basics-of-authentication/), which +provides tips on handling modifiable token scopes. -## Escopos normalizados +## Normalized scopes -Quando vários escopos são solicitados, o token é salvo com uma lista normalizada de escopos, descartando aqueles que estão implicitamente incluídos pelo escopo solicitado. Por exemplo, a solicitação de `user,gist,user:email` resultará em um token somente com os escopos `user` e `gist`, pois o acesso permitido com o escopo `user:email` está incluído no escopo `user`. +When requesting multiple scopes, the token is saved with a normalized list +of scopes, discarding those that are implicitly included by another requested +scope. For example, requesting `user,gist,user:email` will result in a +token with `user` and `gist` scopes only since the access granted with +`user:email` scope is included in the `user` scope. diff --git a/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md b/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md index 377915f8fb..166ace7868 100644 --- a/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md +++ b/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md @@ -1,6 +1,6 @@ --- -title: Sobre o aplicativo -intro: 'Você pode criar integrações com as APIs de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} para adicionar flexibilidade e reduzir o atrito no seu próprio fluxo de trabalho.{% ifversion fpt or ghec %} Você também pode compartilhar integrações com outras pessoas em [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).{% endif %}' +title: About apps +intro: 'You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs to add flexibility and reduce friction in your own workflow.{% ifversion fpt or ghec %} You can also share integrations with others on [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).{% endif %}' redirect_from: - /apps/building-integrationssetting-up-a-new-integration - /apps/building-integrations @@ -14,98 +14,93 @@ versions: ghec: '*' topics: - GitHub Apps -ms.openlocfilehash: 9f8c392906f494b41aaa216ef5f6b58f7968f32a -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145084018' --- -Os aplicativos no {% data variables.product.prodname_dotcom %} permitem que você automatize e melhore seu fluxo de trabalho. Crie aplicativos para aprimorar seu fluxo de trabalho.{% ifversion fpt or ghec %} Você também pode compartilhar ou vender aplicativos no [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). Para saber como listar um aplicativo no {% data variables.product.prodname_marketplace %}, confira "[Introdução ao GitHub Marketplace](/marketplace/getting-started/)".{% endif %} +Apps on {% data variables.product.prodname_dotcom %} allow you to automate and improve your workflow. You can build apps to improve your workflow.{% ifversion fpt or ghec %} You can also share or sell apps in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). To learn how to list an app on {% data variables.product.prodname_marketplace %}, see "[Getting started with GitHub Marketplace](/marketplace/getting-started/)."{% endif %} -{% data reusables.marketplace.github_apps_preferred %}, mas o GitHub é compatível com {% data variables.product.prodname_oauth_apps %} e {% data variables.product.prodname_github_apps %}. Para obter informações sobre como escolher um tipo de aplicativo, confira "[Diferenças entre Aplicativos do GitHub e Aplicativos OAuth](/developers/apps/differences-between-github-apps-and-oauth-apps)". +{% data reusables.marketplace.github_apps_preferred %}, but GitHub supports both {% data variables.product.prodname_oauth_apps %} and {% data variables.product.prodname_github_apps %}. For information on choosing a type of app, see "[Differences between GitHub Apps and OAuth Apps](/developers/apps/differences-between-github-apps-and-oauth-apps)." {% data reusables.apps.general-apps-restrictions %} -Para ver um passo a passo do processo de criação de um {% data variables.product.prodname_github_app %}, confira "[Como criar seu primeiro {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)". +For a walkthrough of the process of building a {% data variables.product.prodname_github_app %}, see "[Building Your First {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)." -## Sobre os {% data variables.product.prodname_github_apps %} +## About {% data variables.product.prodname_github_apps %} -{% data variables.product.prodname_github_apps %} são atores de primeira classe no GitHub. Um {% data variables.product.prodname_github_app %} age em seu próprio nome, tomando ações por meio da API diretamente usando sua própria identidade, o que significa que você não precisa manter um bot ou conta de serviço como um usuário separado. +{% data variables.product.prodname_github_apps %} are first-class actors within GitHub. A {% data variables.product.prodname_github_app %} acts on its own behalf, taking actions via the API directly using its own identity, which means you don't need to maintain a bot or service account as a separate user. -O {% data variables.product.prodname_github_apps %} pode ser instalado diretamente em organizações e contas pessoais e conceder acesso a repositórios específicos. Eles vêm com webhooks integrados e permissões específicas e restritas. Ao configurar o {% data variables.product.prodname_github_app %}, você pode selecionar os repositórios que deseja que ele acesse. Por exemplo, você pode configurar um aplicativo chamado `MyGitHub` que grava os problemas no repositório `octocat` e _apenas_ no repositório `octocat`. Para instalar um {% data variables.product.prodname_github_app %}, você deve ser o proprietário de uma organização ou ter permissões de administrador em um repositório. +{% data variables.product.prodname_github_apps %} can be installed directly on organizations and personal accounts and granted access to specific repositories. They come with built-in webhooks and narrow, specific permissions. When you set up your {% data variables.product.prodname_github_app %}, you can select the repositories you want it to access. For example, you can set up an app called `MyGitHub` that writes issues in the `octocat` repository and _only_ the `octocat` repository. To install a {% data variables.product.prodname_github_app %}, you must be an organization owner or have admin permissions in a repository. {% data reusables.apps.app_manager_role %} -{% data variables.product.prodname_github_apps %} são aplicativos que devem ser hospedados em algum lugar. Para ver instruções passo a passo que abrangem servidores e hospedagem, confira "[Como criar seu primeiro {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)". +{% data variables.product.prodname_github_apps %} are applications that need to be hosted somewhere. For step-by-step instructions that cover servers and hosting, see "[Building Your First {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)." -Para melhorar seu fluxo de trabalho, você pode criar um {% data variables.product.prodname_github_app %} que contém vários scripts ou um aplicativo inteiro e, em seguida, conectar esse aplicativo a muitas outras ferramentas. Por exemplo, você pode conectar {% data variables.product.prodname_github_apps %} ao GitHub, Slack, ou a outros aplicativos que você pode ter, programas de e-mail ou outras APIs. +To improve your workflow, you can create a {% data variables.product.prodname_github_app %} that contains multiple scripts or an entire application, and then connect that app to many other tools. For example, you can connect {% data variables.product.prodname_github_apps %} to GitHub, Slack, other in-house apps you may have, email programs, or other APIs. -Tenha isso em mente ao criar {% data variables.product.prodname_github_apps %}: +Keep these ideas in mind when creating {% data variables.product.prodname_github_apps %}: {% ifversion fpt or ghec %} * {% data reusables.apps.maximum-github-apps-allowed %} {% endif %} -* Um {% data variables.product.prodname_github_app %} deve executar ações independentemente de um usuário (a menos que o aplicativo esteja usando um token [de usuário para servidor](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests)). {% data reusables.apps.expiring_user_authorization_tokens %} +* A {% data variables.product.prodname_github_app %} should take actions independent of a user (unless the app is using a [user-to-server](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests) token). {% data reusables.apps.expiring_user_authorization_tokens %} -* Certifique-se de que o {% data variables.product.prodname_github_app %} integre repositórios específicos. -* O {% data variables.product.prodname_github_app %} deve conectar-se a uma conta pessoal ou organização. -* Não espere que o {% data variables.product.prodname_github_app %} saiba e faça tudo o que um usuário pode fazer. -* Não use {% data variables.product.prodname_github_app %}, se você precisa apenas de um serviço de "Login com GitHub". Mas um {% data variables.product.prodname_github_app %} pode usar um [fluxo de identificação do usuário](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) para fazer logon dos usuários _e_ executar outras tarefas. -* Não crie um {% data variables.product.prodname_github_app %} se você _quiser apenas_ atuar como um usuário do GitHub e fazer tudo o que o usuário pode fazer.{% ifversion fpt or ghec %} +* Make sure the {% data variables.product.prodname_github_app %} integrates with specific repositories. +* The {% data variables.product.prodname_github_app %} should connect to a personal account or an organization. +* Don't expect the {% data variables.product.prodname_github_app %} to know and do everything a user can. +* Don't use a {% data variables.product.prodname_github_app %} if you just need a "Login with GitHub" service. But a {% data variables.product.prodname_github_app %} can use a [user identification flow](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) to log users in _and_ do other things. +* Don't build a {% data variables.product.prodname_github_app %} if you _only_ want to act as a GitHub user and do everything that user can do.{% ifversion fpt or ghec %} * {% data reusables.apps.general-apps-restrictions %}{% endif %} -Para começar a desenvolver {% data variables.product.prodname_github_apps %}, comece com "[Como criar um {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/)".{% ifversion fpt or ghec %} Para saber como usar os Manifestos do {% data variables.product.prodname_github_app %}, que permitem que as pessoas criem {% data variables.product.prodname_github_apps %} pré-configurados, confira "[Como criar {% data variables.product.prodname_github_apps %} com base em um manifesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/)".{% endif %} +To begin developing {% data variables.product.prodname_github_apps %}, start with "[Creating a {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/)."{% ifversion fpt or ghec %} To learn how to use {% data variables.product.prodname_github_app %} Manifests, which allow people to create preconfigured {% data variables.product.prodname_github_apps %}, see "[Creating {% data variables.product.prodname_github_apps %} from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)."{% endif %} -## Sobre {% data variables.product.prodname_oauth_apps %} +## About {% data variables.product.prodname_oauth_apps %} -OAuth2 é um protocolo que permite que os aplicativos externos solicitem autorização para detalhes privados na conta {% data variables.product.prodname_dotcom %} de um usuário sem acessar sua senha. Isto é preferido em relação à autenticação básica, porque os tokens podem ser limitados a tipos específicos de dados e podem ser revogados pelos usuários a qualquer momento. +OAuth2 is a protocol that lets external applications request authorization to private details in a user's {% data variables.product.prodname_dotcom %} account without accessing their password. This is preferred over Basic Authentication because tokens can be limited to specific types of data and can be revoked by users at any time. {% data reusables.apps.deletes_ssh_keys %} -Um {% data variables.product.prodname_oauth_app %} usa {% data variables.product.prodname_dotcom %} como um provedor de identidade para efetuar a autenticação como o usuário que concede acesso ao aplicativo. Isso significa que, quando um usuário permite acesso ao {% data variables.product.prodname_oauth_app %}, ele concede permissões a _todos_ os repositórios aos quais ele tem acesso na conta e a todas as organizações às quais ele pertence que não bloquearam o acesso de terceiros. +An {% data variables.product.prodname_oauth_app %} uses {% data variables.product.prodname_dotcom %} as an identity provider to authenticate as the user who grants access to the app. This means when a user grants an {% data variables.product.prodname_oauth_app %} access, they grant permissions to _all_ repositories they have access to in their account, and also to any organizations they belong to that haven't blocked third-party access. -Construir um {% data variables.product.prodname_oauth_app %} é uma boa opção se você estiver criando processos mais complexos do que um simples script pode gerenciar. Note que {% data variables.product.prodname_oauth_apps %} são aplicativos que precisam ser hospedados em algum lugar. +Building an {% data variables.product.prodname_oauth_app %} is a good option if you are creating more complex processes than a simple script can handle. Note that {% data variables.product.prodname_oauth_apps %} are applications that need to be hosted somewhere. -Tenha isso em mente ao criar {% data variables.product.prodname_oauth_apps %}: +Keep these ideas in mind when creating {% data variables.product.prodname_oauth_apps %}: {% ifversion fpt or ghec %} * {% data reusables.apps.maximum-oauth-apps-allowed %} {% endif %} -* Um {% data variables.product.prodname_oauth_app %} deve sempre atuar como o usuário autenticado {% data variables.product.prodname_dotcom %} em todo o {% data variables.product.prodname_dotcom %} (por exemplo, ao fornecer notificações de usuário). -* Um {% data variables.product.prodname_oauth_app %} pode ser usado como um provedor de identidade, habilitando um "Login com {% data variables.product.prodname_dotcom %}" para o usuário autenticado. -* Não crie um {% data variables.product.prodname_oauth_app %}, se desejar que seu aplicativo atue em um único repositório. Com o escopo `repo` do OAuth, os {% data variables.product.prodname_oauth_apps %} podem atuar em _todos_ os repositórios do usuário autenticado. -* Não crie um {% data variables.product.prodname_oauth_app %} para atuar como um aplicativo para sua equipe ou empresa. {% data variables.product.prodname_oauth_apps %} efetua a autenticação como um usuário único. Portanto se uma pessoa criar um {% data variables.product.prodname_oauth_app %} para uma empresa usar e, posteriormente, sair da empresa, ninguém mais terá acesso.{% ifversion fpt or ghec %} +* An {% data variables.product.prodname_oauth_app %} should always act as the authenticated {% data variables.product.prodname_dotcom %} user across all of {% data variables.product.prodname_dotcom %} (for example, when providing user notifications). +* An {% data variables.product.prodname_oauth_app %} can be used as an identity provider by enabling a "Login with {% data variables.product.prodname_dotcom %}" for the authenticated user. +* Don't build an {% data variables.product.prodname_oauth_app %} if you want your application to act on a single repository. With the `repo` OAuth scope, {% data variables.product.prodname_oauth_apps %} can act on _all_ of the authenticated user's repositories. +* Don't build an {% data variables.product.prodname_oauth_app %} to act as an application for your team or company. {% data variables.product.prodname_oauth_apps %} authenticate as a single user, so if one person creates an {% data variables.product.prodname_oauth_app %} for a company to use, and then they leave the company, no one else will have access to it.{% ifversion fpt or ghec %} * {% data reusables.apps.oauth-apps-restrictions %}{% endif %} -Para obter mais informações sobre os {% data variables.product.prodname_oauth_apps %}, confira "[Como criar um {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" e "[Como registrar seu aplicativo](/rest/guides/basics-of-authentication#registering-your-app)". +For more on {% data variables.product.prodname_oauth_apps %}, see "[Creating an {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" and "[Registering your app](/rest/guides/basics-of-authentication#registering-your-app)." -## Tokens de acesso pessoal +## {% data variables.product.pat_generic_caps %}s -Um [token de acesso pessoal](/articles/creating-a-personal-access-token-for-the-command-line/) é uma cadeia de caracteres que funciona de maneira semelhante a um [token OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/), no qual você pode especificar as permissões por meio de [escopos](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). Um token de acesso pessoal também é semelhante a uma senha, mas você pode ter muitos delas e você pode revogar o acesso a cada uma a qualquer momento. +A [{% data variables.product.pat_generic %}](/articles/creating-a-personal-access-token-for-the-command-line/) is a string of characters that functions similarly to an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/) in that you can specify its permissions via [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). A {% data variables.product.pat_generic %} is also similar to a password, but you can have many of them and you can revoke access to each one at any time. -Como exemplo, você pode habilitar um token de acesso pessoal para escrever em seus repositórios. Se você executar um comando do cURL ou escrever um script que [crie um problema](/rest/reference/issues#create-an-issue) no seu repositório, transmitirá o token de acesso pessoal para autenticação. Você pode armazenar o token de acesso pessoal como uma variável de ambiente para evitar ter de digitá-lo toda vez que você usá-lo. +As an example, you can enable a {% data variables.product.pat_generic %} to write to your repositories. If then you run a cURL command or write a script that [creates an issue](/rest/reference/issues#create-an-issue) in your repository, you would pass the {% data variables.product.pat_generic %} to authenticate. You can store the {% data variables.product.pat_generic %} as an environment variable to avoid typing it every time you use it. -Tenha em mente essas ideias ao usar os tokens de acesso pessoais: +Keep these ideas in mind when using {% data variables.product.pat_generic %}s: -* Lembre-se de usar este token para representar apenas você. -* Você pode realizar solicitações de cURL únicas. -* Você pode executar scripts pessoais. -* Não configure um script para toda a sua equipe ou empresa usá-lo. -* Não configure uma conta pessoal compartilhada para funcionar como um usuário bot.{% ifversion fpt or ghes > 3.2 or ghae or ghec %} -* Defina um vencimento para os seus tokens de acesso pessoais para ajudar a manter suas informações seguras.{% endif %} +* Remember to use this token to represent yourself only. +* You can perform one-off cURL requests. +* You can run personal scripts. +* Don't set up a script for your whole team or company to use. +* Don't set up a shared personal account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae or ghec %} +* Grant your token the minimal privileges it needs. +* Set an expiration for your {% data variables.product.pat_generic %}s, to help keep your information secure.{% endif %} -## Determinar qual integração criar +## Determining which integration to build -Antes de começar a criar integrações, você deverá determinar a melhor maneira de acessar autenticar e interagir com as APIs de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}. A imagem a seguir oferece algumas perguntas de segurança ao decidir se usa tokens de acesso pessoais, {% data variables.product.prodname_github_apps %}ou {% data variables.product.prodname_oauth_apps %} para sua integração. +Before you get started creating integrations, you need to determine the best way to access, authenticate, and interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs. The following image offers some questions to ask yourself when deciding whether to use {% data variables.product.pat_generic %}s, {% data variables.product.prodname_github_apps %}, or {% data variables.product.prodname_oauth_apps %} for your integration. -![Introdução ao fluxo de perguntas dos aplicativos](/assets/images/intro-to-apps-flow.png) +![Intro to apps question flow](/assets/images/intro-to-apps-flow.png) -Considere estas perguntas sobre como sua integração deve se comportar e o que é necessário para ter acesso: +Consider these questions about how your integration needs to behave and what it needs to access: -* A minha integração funcionará apenas como eu ou será mais como um aplicativo? -* Quero que ela aja independentemente de mim com sua própria entidade? -* Ela irá acessar tudo o que eu puder acessar ou eu quero limitar seu acesso? -* É simples ou complexo? Por exemplo, tokens de acesso pessoal são bons para scripts simples e cURLs, enquanto um {% data variables.product.prodname_oauth_app %} pode lidar com scripts mais complexos. +* Will my integration act only as me, or will it act more like an application? +* Do I want it to act independently of me as its own entity? +* Will it access everything that I can access, or do I want to limit its access? +* Is it simple or complex? For example, {% data variables.product.pat_generic %}s are good for simple scripts and cURLs, whereas an {% data variables.product.prodname_oauth_app %} can handle more complex scripting. -## Solicitar suporte +## Requesting support {% data reusables.support.help_resources %} diff --git a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md index e6316d1291..6653241592 100644 --- a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md +++ b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md @@ -1,6 +1,6 @@ --- -title: Requisitos para listar um aplicativo -intro: 'Os aplicativos em {% data variables.product.prodname_marketplace %} devem atender aos requisitos definidos nessa página antes que o anúncio possa ser publicado.' +title: Requirements for listing an app +intro: 'Apps on {% data variables.product.prodname_marketplace %} must meet the requirements outlined on this page before the listing can be published.' redirect_from: - /apps/adding-integrations/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace - /apps/marketplace/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace @@ -15,72 +15,66 @@ versions: topics: - Marketplace shortTitle: Listing requirements -ms.openlocfilehash: 58112d935a77119325dab4ad72c87561d0c00e47 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145083967' --- -Os requisitos para a anunciar um aplicativo em {% data variables.product.prodname_marketplace %} variam de acordo com o fato de você desejar oferecer um aplicativo grátis ou pago. +The requirements for listing an app on {% data variables.product.prodname_marketplace %} vary according to whether you want to offer a free or a paid app. -## Requisitos para todos os anúncios de {% data variables.product.prodname_marketplace %} +## Requirements for all {% data variables.product.prodname_marketplace %} listings -Todos os anúncios em {% data variables.product.prodname_marketplace %} devem ser para ferramentas que fornecem valor à comunidade de {% data variables.product.product_name %}. Ao enviar sua listagem para publicação, você precisa ler e aceitar os termos do "[Contrato de Desenvolvedor do {% data variables.product.prodname_marketplace %}](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)". +All listings on {% data variables.product.prodname_marketplace %} should be for tools that provide value to the {% data variables.product.product_name %} community. When you submit your listing for publication, you must read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)." -### Requisitos de experiência do usuário para todos os aplicativos +### User experience requirements for all apps -Todos os anúncios devem atender aos requisitos a seguir, independentemente de serem para um aplicativo grátis ou pago. +All listings should meet the following requirements, regardless of whether they are for a free or paid app. -- Os anúncios não devem persuadir ativamente os usuários para fora de {% data variables.product.product_name %}. -- Os anúncios devem incluir informações de contato válidas para o editor. -- Os anúncios devem ter uma descrição relevante do aplicativo. -- Os anúncios devem especificar um plano de preços. -- Os aplicativos devem fornecer valor aos clientes e integrar-se à plataforma de alguma forma além da autenticação. -- Os aplicativos devem estar disponíveis publicamente em {% data variables.product.prodname_marketplace %} e não podem estar na versão beta ou disponíveis apenas por convite. -- Os aplicativos devem ter eventos webhook configurados para notificar o editor de qualquer alteração do plano ou cancelamentos usando a API de {% data variables.product.prodname_marketplace %} Para obter mais informações, confira "[Como usar a API do {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". +- Listings must not actively persuade users away from {% data variables.product.product_name %}. +- Listings must include valid contact information for the publisher. +- Listings must have a relevant description of the application. +- Listings must specify a pricing plan. +- Apps must provide value to customers and integrate with the platform in some way beyond authentication. +- Apps must be publicly available in {% data variables.product.prodname_marketplace %} and cannot be in beta or available by invite only. +- Apps must have webhook events set up to notify the publisher of any plan changes or cancellations using the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -Para obter mais informações sobre como fornecer uma ótima experiência do cliente, confira "[Melhores práticas de experiência do cliente para aplicativos](/developers/github-marketplace/customer-experience-best-practices-for-apps)". +For more information on providing a good customer experience, see "[Customer experience best practices for apps](/developers/github-marketplace/customer-experience-best-practices-for-apps)." -### Requisitos da marca e anúncios para todos os aplicativos +### Brand and listing requirements for all apps -- Os aplicativos que usam logotipos do GitHub precisam seguir as diretrizes de {% data variables.product.company_short %}. Para obter mais informações, confira "[Logotipos e uso do {% data variables.product.company_short %}](https://github.com/logos)". -- Os aplicativos precisam ter um logotipo, um cartão de recurso e imagens de captura de tela que atendam às recomendações fornecidas em "[Como escrever descrições de listagem do {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)". -- As listagens devem incluir descrições bem escritas e sem erros gramaticais. Para obter diretrizes sobre como escrever sua listagem, confira "[Como escrever descrições de listagem do {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)". +- Apps that use GitHub logos must follow the {% data variables.product.company_short %} guidelines. For more information, see "[{% data variables.product.company_short %} Logos and Usage](https://github.com/logos)." +- Apps must have a logo, feature card, and screenshots images that meet the recommendations provided in "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)." +- Listings must include descriptions that are well written and free of grammatical errors. For guidance in writing your listing, see "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)." -Para proteger seus clientes, recomendamos que siga as práticas recomendadas em matéria de segurança. Para obter mais informações, confira "[Melhores práticas de segurança para aplicativos](/developers/github-marketplace/security-best-practices-for-apps)". +To protect your customers, we recommend that you also follow security best practices. For more information, see "[Security best practices for apps](/developers/github-marketplace/security-best-practices-for-apps)." -## Considerações para aplicativos gratuitos +## Considerations for free apps {% data reusables.marketplace.free-apps-encouraged %} -## Requisitos para aplicativos pagos +## Requirements for paid apps -Para publicar um plano pago para o seu aplicativo em {% data variables.product.prodname_marketplace %}, seu aplicativo deverá pertencer a uma organização que seja um publicador verificado. Para obter mais informações sobre o processo de verificação ou a transferência da propriedade do seu aplicativo, confira "[Como solicitar a verificação de editor para sua organização](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)". +To publish a paid plan for your app on {% data variables.product.prodname_marketplace %}, your app must be owned by an organization that is a verified publisher. For more information about the verification process or transferring ownership of your app, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)." -Se seu aplicativo já está publicado e você é um editor verificado, você poderá publicar um novo plano pago no editor do plano de preços. Para obter informações, confira "[Como definir planos de preços para sua listagem](/developers/github-marketplace/setting-pricing-plans-for-your-listing)". +If your app is already published and you're a verified publisher, then you can publish a new paid plan from the pricing plan editor. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)." -Para publicar um aplicativo pago (ou um aplicativo que ofereça um plano pago), você também deve atender aos seguintes requisitos: +To publish a paid app (or an app that offers a paid plan), you must also meet the following requirements: -- {% data variables.product.prodname_github_apps %} deve ter no mínimo 100 instalações. -- {% data variables.product.prodname_oauth_apps %} deve ter no mínimo 200 usuários. -- Todos os aplicativos pagos devem lidar com eventos de compra de {% data variables.product.prodname_marketplace %} para novas compras, atualizações, downgrades, cancelamentos e testes grátis. Para obter mais informações, confira "[Requisitos de cobrança para aplicativos pagos](#billing-requirements-for-paid-apps)" abaixo. +- {% data variables.product.prodname_github_apps %} should have a minimum of 100 installations. +- {% data variables.product.prodname_oauth_apps %} should have a minimum of 200 users. +- All paid apps must handle {% data variables.product.prodname_marketplace %} purchase events for new purchases, upgrades, downgrades, cancellations, and free trials. For more information, see "[Billing requirements for paid apps](#billing-requirements-for-paid-apps)" below. -Quando estiver pronto para publicar o aplicativo em {% data variables.product.prodname_marketplace %}, você deverá solicitar a verificação para o anúncio do aplicativo. +When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the app listing. {% note %} -**Observação:** {% data reusables.marketplace.app-transfer-to-org-for-verification %} Para obter informações sobre como transferir um aplicativo para uma organização, confira: "[Como enviar sua listagem para publicação](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)". +**Note:** {% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to transfer an app to an organization, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." {% endnote %} -## Requisitos de cobrança para aplicativos pagos +## Billing requirements for paid apps -Seu aplicativo não precisa gerenciar pagamentos, mas precisa usar eventos de compra de {% data variables.product.prodname_marketplace %} para gerenciar novas compras, atualizações, downgrades, cancelamentos e testes grátis. Para obter informações sobre como integrar esses eventos ao seu aplicativo, confira "[Como usar a API do {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". +Your app does not need to handle payments but does need to use {% data variables.product.prodname_marketplace %} purchase events to manage new purchases, upgrades, downgrades, cancellations, and free trials. For information about how integrate these events into your app, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -Usar a API de cobrança do GitHub permite aos clientes comprar um aplicativo sem sair do GitHub e pagar o serviço com o método de pagamento já anexado à sua conta em {% data variables.product.product_location %}. +Using GitHub's billing API allows customers to purchase an app without leaving GitHub and to pay for the service with the payment method already attached to their account on {% data variables.location.product_location %}. -- Os aplicativos devem ser compatíveis tanto com a cobrança anual quanto mensal para as compras de suas assinaturas pagas. -- As listagens podem oferecer qualquer combinação de planos grátis e pagos. Os planos grátis são opcionais, porém incentivados. Para obter mais informações sobre como criar um plano de preços, confira "[Como definir um plano de preços da listagem do {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)". +- Apps must support both monthly and annual billing for paid subscriptions purchases. +- Listings may offer any combination of free and paid plans. Free plans are optional but encouraged. For more information, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)." diff --git a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md index 3ea37905b3..f5da9567b4 100644 --- a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md +++ b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md @@ -1,6 +1,6 @@ --- -title: Práticas de segurança recomendadas para aplicativos -intro: 'Diretrizes para a preparação de um aplicativo seguro para compartilhar em {% data variables.product.prodname_marketplace %}.' +title: Security best practices for apps +intro: 'Guidelines for preparing a secure app to share on {% data variables.product.prodname_marketplace %}.' redirect_from: - /apps/marketplace/getting-started/security-review-process - /marketplace/getting-started/security-review-process @@ -12,58 +12,52 @@ versions: ghec: '*' topics: - Marketplace -ms.openlocfilehash: aaff313f73b74ba28f765050a8f993a9dddea1be -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145083962' --- -Se você seguir estas práticas recomendadas, elas ajudarão você a oferecer uma experiência de usuário segura. +If you follow these best practices it will help you to provide a secure user experience. -## Autorização, autenticação e controle de acesso +## Authorization, authentication, and access control -Recomendamos criar um aplicativo GitHub em vez de um aplicativo OAuth. {% data reusables.marketplace.github_apps_preferred %}. Confira "[Diferenças entre Aplicativos do GitHub e Aplicativos OAuth](/apps/differences-between-apps/)" para obter mais detalhes. -- Os aplicativos devem usar o princípio do menor privilégio e devem solicitar apenas os escopos do OAuth e as permissões do aplicativo GitHub de que o aplicativo precisa para realizar suas funcionalidades pretendidas. Para obter mais informações, confira [Princípio de privilégios mínimos](https://en.wikipedia.org/wiki/Principle_of_least_privilege) na Wikipédia. -- Os aplicativos devem fornecer aos clientes uma forma de excluir sua conta, sem ter de enviar um e-mail ou ligar para uma pessoa de suporte. -- Os aplicativos não devem compartilhar tokens entre diferentes implementações do aplicativo. Por exemplo, um aplicativo para computador deve ter um token separado de um aplicativo baseado na web. Os tokens individuais permitem que cada aplicativo solicite o acesso necessário aos recursos do GitHub separadamente. -- Crie seu aplicativo com diferentes funções de usuário, dependendo da funcionalidade necessária para cada tipo de usuário. Por exemplo, um usuário-padrão não deve ter acesso à funcionalidade de administração, e os gerentes de cobrança podem não precisar de acesso push ao código de repositório. -- Os aplicativos não devem compartilhar contas de serviço como, por exemplo, e-mail ou serviços de banco de dados para gerenciar seu serviço de SaaS. -- Todos os serviços usados no seu aplicativo devem ter credenciais de login e senha exclusivas. -- O acesso privilegiado de administrador à infraestrutura de hospedagem de produção deve ser concedido apenas a engenheiros e funcionários com funções administrativas. -- Os aplicativos não devem usar tokens de acesso pessoal para autenticação e devem ser autenticados como um [Aplicativo OAuth](/apps/about-apps/#about-oauth-apps) ou um [Aplicativo do GitHub](/apps/about-apps/#about-github-apps): - - Os Aplicativos OAuth devem ser autenticados com um [token OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/). - - Os Aplicativos do GitHub devem ser autenticados com um [JWT (Token Web JSON)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app), um [token OAuth](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) ou um [token de acesso de instalação](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). +We recommend creating a GitHub App rather than an OAuth App. {% data reusables.marketplace.github_apps_preferred %}. See "[Differences between GitHub Apps and OAuth Apps](/apps/differences-between-apps/)" for more details. +- Apps should use the principle of least privilege and should only request the OAuth scopes and GitHub App permissions that the app needs to perform its intended functionality. For more information, see [Principle of least privilege](https://en.wikipedia.org/wiki/Principle_of_least_privilege) in Wikipedia. +- Apps should provide customers with a way to delete their account, without having to email or call a support person. +- Apps should not share tokens between different implementations of the app. For example, a desktop app should have a separate token from a web-based app. Individual tokens allow each app to request the access needed for GitHub resources separately. +- Design your app with different user roles, depending on the functionality needed by each type of user. For example, a standard user should not have access to admin functionality, and billing managers might not need push access to repository code. +- Apps should not share service accounts such as email or database services to manage your SaaS service. +- All services used in your app should have unique login and password credentials. +- Admin privilege access to the production hosting infrastructure should only be given to engineers and employees with administrative duties. +- Apps should not use {% data variables.product.pat_generic %}s to authenticate and should authenticate as an [OAuth App](/apps/about-apps/#about-oauth-apps) or a [GitHub App](/apps/about-apps/#about-github-apps): + - OAuth Apps should authenticate using an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/). + - GitHub Apps should authenticate using either a [JSON Web Token (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app), [OAuth token](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/), or [installation access token](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). -## Proteção de dados +## Data protection -- Os aplicativos devem criptografar dados transferidos para internet pública usando HTTPS, com um certificado TLS válido ou SSH para o Git. -- Os aplicativos devem armazenar com segurança o ID do cliente e as chaves secretas do cliente. Recomendamos armazená-las como [variáveis de ambiente](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables). -- Os aplicativos devem excluir todos os dados do usuário no prazo de 30 dias após receber uma solicitação do usuário ou dentro de 30 dias após o fim da relação jurídica do usuário com o GitHub. -- Aplicativos não devem exigir que o usuário forneça sua senha do GitHub. -- Os aplicativos devem criptografar tokens, IDs de clientes e segredos de clientes. +- Apps should encrypt data transferred over the public internet using HTTPS, with a valid TLS certificate, or SSH for Git. +- Apps should store client ID and client secret keys securely. We recommend storing them as [environmental variables](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables). +- Apps should delete all GitHub user data within 30 days of receiving a request from the user, or within 30 days of the end of the user's legal relationship with GitHub. +- Apps should not require the user to provide their GitHub password. +- Apps should encrypt tokens, client IDs, and client secrets. -## Log e monitoramento +## Logging and monitoring -Os aplicativos devem ter capacidade de registro e monitoramento. Os registros dos aplicativos devem ser mantidos pelo menos 30 dias e arquivados pelo menos um ano. -Um log de segurança deve incluir: +Apps should have logging and monitoring capabilities. App logs should be retained for at least 30 days and archived for at least one year. +A security log should include: -- Eventos de autenticação e autorização -- Alterações na configuração do serviço -- Leitura e gravação de objetos -- Todas as alterações de permissão do usuário e de grupo -- Elevação do papel para administrador -- Marca de tempo consistente para cada evento -- Usuários de origem, endereços IP e/ou nomes de host para todas as ações registradas +- Authentication and authorization events +- Service configuration changes +- Object reads and writes +- All user and group permission changes +- Elevation of role to admin +- Consistent timestamping for each event +- Source users, IP addresses, and/or hostnames for all logged actions -## Fluxo de trabalho de resposta a incidentes +## Incident response workflow -Para oferecer uma experiência segura aos usuários, você deve ter um plano de resposta de incidente claro em vigor antes de anunciar o seu aplicativo. Recomendamos ter uma equipe de resposta a incidentes de segurança e operações na sua empresa, em vez de usar um fornecedor terceiro. Você deve ter a capacidade de notificar {% data variables.product.product_name %} no prazo de 24 horas após a confirmação de um incidente. +To provide a secure experience for users, you should have a clear incident response plan in place before listing your app. We recommend having a security and operations incident response team in your company rather than using a third-party vendor. You should have the capability to notify {% data variables.product.product_name %} within 24 hours of a confirmed incident. -Para ver um exemplo de um fluxo de trabalho de resposta a incidentes, confira a "Política de Resposta a Violação de Dados" no [site do SANS Institute](https://www.sans.org/information-security-policy/). Um documento breve com medidas claras a serem tomadas em caso de incidente é mais valioso do que um modelo político moroso. +For an example of an incident response workflow, see the "Data Breach Response Policy" on the [SANS Institute website](https://www.sans.org/information-security-policy/). A short document with clear steps to take in the event of an incident is more valuable than a lengthy policy template. -## Gerenciamento de vulnerabilidades e fluxo de trabalho de patch +## Vulnerability management and patching workflow -Você deveria realizar varreduras regulares de vulnerabilidades de infraestrutura de produção. Você deve classificar os resultados de verificações de vulnerabilidades e definir um período de tempo no qual você concorda em remediar a vulnerabilidade. +You should conduct regular vulnerability scans of production infrastructure. You should triage the results of vulnerability scans and define a period of time in which you agree to remediate the vulnerability. -Se você não estiver pronto para criar um programa completo de gerenciamento de vulnerabilidades, é importante começar criando um processo de patching. Para obter diretrizes sobre como criar uma política de gerenciamento de patch, confira o artigo "[Estabelecer uma política de gerenciamento de patch](https://www.techrepublic.com/article/establish-a-patch-management-policy-87756/)" do TechRepublic. +If you are not ready to set up a full vulnerability management program, it's useful to start by creating a patching process. For guidance in creating a patch management policy, see this TechRepublic article "[Establish a patch management policy](https://www.techrepublic.com/article/establish-a-patch-management-policy-87756/)." diff --git a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md index 55766f5cd5..0725eb52ca 100644 --- a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md +++ b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md @@ -1,6 +1,6 @@ --- -title: Escrever uma descrição da listagem para o seu aplicativo -intro: 'Para [listar seu aplicativo](/marketplace/listing-on-github-marketplace/) no {% data variables.product.prodname_marketplace %}, você precisará escrever as descrições dele e fornecer imagens que sigam as diretrizes do GitHub.' +title: Writing a listing description for your app +intro: 'To [list your app](/marketplace/listing-on-github-marketplace/) in the {% data variables.product.prodname_marketplace %}, you''ll need to write descriptions of your app and provide images that follow GitHub''s guidelines.' redirect_from: - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-writing-github-app-descriptions - /apps/marketplace/creating-and-submitting-your-app-for-approval/writing-github-app-descriptions @@ -17,186 +17,180 @@ versions: topics: - Marketplace shortTitle: Write listing descriptions -ms.openlocfilehash: f29e049529801011d25d2723c5851b56d7a8bb92 -ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '146139253' --- -Estas são as diretrizes sobre os campos que você precisará preencher na seção **Descrição da listagem** da listagem de rascunho. +Here are guidelines about the fields you'll need to fill out in the **Listing description** section of your draft listing. -## Nomenclatura e links +## Naming and links -### Nome da listagem +### Listing name -O nome da listagem será exibido na [home page do {% data variables.product.prodname_marketplace %}](https://github.com/marketplace). O nome é limitado a 255 caracteres e pode ser diferente do nome do seu aplicativo. Seu anúncio não pode ter o mesmo nome de uma conta existente em {% data variables.product.product_location %}, a menos que o nome seja o seu próprio usuário ou nome de organização. +Your listing's name will appear on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace). The name is limited to 255 characters and can be different from your app's name. Your listing cannot have the same name as an existing account on {% data variables.location.product_location %}, unless the name is your own user or organization name. -### Descrição muito curta +### Very short description -A comunidade verá a descrição "muito curta" abaixo do nome do aplicativo na [home page do {% data variables.product.prodname_marketplace %}](https://github.com/marketplace). +The community will see the "very short" description under your app's name on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace). -![Descrição curta do aplicativo em {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_short_description.png) +![{% data variables.product.prodname_marketplace %} app short description](/assets/images/marketplace/marketplace_short_description.png) -#### Comprimento +#### Length -Recomendamos manter descrições curtas para com 40 a 80 caracteres. Embora você possa usar mais caracteres, as descrições concisas são mais fáceis para os clientes ler e entender rapidamente. +We recommend keeping short descriptions to 40-80 characters. Although you are allowed to use more characters, concise descriptions are easier for customers to read and understand quickly. -#### Conteúdo +#### Content -- Descreva as funcionalidades do aplicativo. Não use este espaço para uma chamada para ação. Por exemplo: +- Describe the app’s functionality. Don't use this space for a call to action. For example: - **O QUE FAZER:** gerenciamento leve de projetos para problemas do GitHub + **DO:** Lightweight project management for GitHub issues - **O QUE NÃO FAZER:** gerenciar seus projetos e problemas no GitHub + **DON'T:** Manage your projects and issues on GitHub - **Dica:** adicione um "s" ao final do verbo em uma chamada à ação para transformá-lo em uma descrição aceitável: _gerencia seus projetos e problemas no GitHub_ + **Tip:** Add an "s" to the end of the verb in a call to action to turn it into an acceptable description: _Manages your projects and issues on GitHub_ -- Não repita o nome do aplicativo na descrição. +- Don’t repeat the app’s name in the description. - **O QUE FAZER:** uma ferramenta de integração contínua nativa de contêiner + **DO:** A container-native continuous integration tool - **O QUE NÃO FAZER:** o Skycap é uma ferramenta de integração contínua nativa de contêiner + **DON'T:** Skycap is a container-native continuous integration tool -#### Formatação +#### Formatting -- Use sempre letras maiúsculas na frase. Use maiúscula somente para a primeira letra e para substantivos próprios. +- Always use sentence-case capitalization. Only capitalize the first letter and proper nouns. -- Não use pontuação no final da sua descrição curta. As descrições curtas não devem incluir frases completas e definitivamente não devem incluir mais de uma frase. +- Don't use punctuation at the end of your short description. Short descriptions should not include complete sentences, and definitely should not include more than one sentence. -- Use maiúscula apenas para os substantivos próprios. Por exemplo: +- Only capitalize proper nouns. For example: - **O QUE FAZER:** automação de entrega com um clique para desenvolvedores da Web + **DO:** One-click delivery automation for web developers - **O QUE NÃO FAZER:** automação de entrega com um clique para desenvolvedores da Web + **DON'T:** One-click delivery automation for Web Developers -- Sempre use uma [vírgula de série](https://en.wikipedia.org/wiki/Serial_comma) em listas. +- Always use a [serial comma](https://en.wikipedia.org/wiki/Serial_comma) in lists. -- Evite referir-se à comunidade do GitHub como "usuários". +- Avoid referring to the GitHub community as "users." - **O QUE FAZER:** crie problemas automaticamente para as pessoas na sua organização + **DO:** Create issues automatically for people in your organization - **O QUE NÃO FAZER:** crie problemas automaticamente para os usuários de uma organização + **DON'T:** Create issues automatically for an organization's users -- Evite acrônimos, a menos que estejam conhecidos (como, por exemplo, API). Por exemplo: +- Avoid acronyms unless they’re well established (such as API). For example: - **O QUE FAZER:** painéis de tarefas Agile, estimativas e relatórios sem sair do GitHub + **DO:** Agile task boards, estimates, and reports without leaving GitHub - **O QUE NÃO FAZER:** painéis de tarefas Agile, estimativas e relatórios sem sair da interface do usuário do GitHub + **DON'T:** Agile task boards, estimates, and reports without leaving GitHub’s UI -### Categorias +### Categories -Os aplicativos em {% data variables.product.prodname_marketplace %} podem ser exibidos por categoria. Selecione a categoria que melhor descreve a funcionalidade principal do aplicativo no menu suspenso **Categoria principal** e, opcionalmente, selecione uma **Categoria secundária** adequada ao aplicativo. +Apps in {% data variables.product.prodname_marketplace %} can be displayed by category. Select the category that best describes the main functionality of your app in the **Primary category** dropdown, and optionally select a **Secondary category** that fits your app. -### Idiomas com suporte +### Supported languages -Se o seu aplicativo só funciona com idiomas específicos, selecione até 10 linguagens de programação com as quais o seu aplicativo é compatível. Esses idiomas são exibidos na página de listagem do {% data variables.product.prodname_marketplace %} do seu aplicativo. Esse campo é opcional. +If your app only works with specific languages, select up to 10 programming languages that your app supports. These languages are displayed on your app's {% data variables.product.prodname_marketplace %} listing page. This field is optional. -### Listar URLs +### Listing URLs -**URLs necessárias** -* **URL de suporte ao cliente:** a URL de uma página da Web à qual os clientes acessarão quando tiverem dúvidas referentes ao suporte técnico, ao produto ou à conta. -* **URL da política de privacidade:** a página da Web que exibe a política de privacidade do aplicativo. -* **URL de instalação:** esse campo é mostrado somente para Aplicativos OAuth. (Os Aplicativos do GitHub não usam essa URL porque usam a URL de Instalação opcional da página de configurações do Aplicativo do GitHub). Quando um cliente comprar seu Aplicativo OAuth, o GitHub o redirecionará para a URL de instalação após a instalação do aplicativo. Você precisará redirecionar os clientes para `https://github.com/login/oauth/authorize` a fim de iniciar o fluxo de autorização do OAuth. Confira "[Novas compras para Aplicativos OAuth](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" para obter mais detalhes. Ignore este campo se você estiver listando um aplicativo GitHub. +**Required URLs** +* **Customer support URL:** The URL of a web page that your customers will go to when they have technical support, product, or account inquiries. +* **Privacy policy URL:** The web page that displays your app's privacy policy. +* **Installation URL:** This field is shown for OAuth Apps only. (GitHub Apps don't use this URL because they use the optional Setup URL from the GitHub App's settings page instead.) When a customer purchases your OAuth App, GitHub will redirect customers to the installation URL after they install the app. You will need to redirect customers to `https://github.com/login/oauth/authorize` to begin the OAuth authorization flow. See "[New purchases for OAuth Apps](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" for more details. Skip this field if you're listing a GitHub App. -**URLs opcionais** -* **URL da empresa:** um link para o site da sua empresa. -* **URL de status:** um link para uma página da Web que exibe o status do aplicativo. As páginas de status podem incluir relatórios de incidente atuais e em forma de histórico, status do tempo de atividade do aplicativo, bem como manutenção programada. -* **URL da documentação:** um link para a documentação que ensina os clientes a usar o aplicativo. +**Optional URLs** +* **Company URL:** A link to your company's website. +* **Status URL:** A link to a web page that displays the status of your app. Status pages can include current and historical incident reports, web application uptime status, and scheduled maintenance. +* **Documentation URL:** A link to documentation that teaches customers how to use your app. -## Logotipo e cartão de recurso +## Logo and feature card -{% data variables.product.prodname_marketplace %} exibe todas as listagens com um logotipo quadrado dentro de um selo circular para distinguir visualmente os aplicativos. +{% data variables.product.prodname_marketplace %} displays all listings with a square logo image inside a circular badge to visually distinguish apps. -![Imagens e logotipo do GitHub Marketplace](/assets/images/marketplace/marketplace-logo-and-badge.png) +![GitHub Marketplace logo and badge images](/assets/images/marketplace/marketplace-logo-and-badge.png) -Um cartão de recursos consiste do logotipo, nome e uma imagem de fundo personalizada do seu aplicativo que capta a personalidade da sua marca. O {% data variables.product.prodname_marketplace %} exibirá esse cartão se o seu aplicativo for um dos quatro aplicativos em destaque aleatórios na parte superior da [home page](https://github.com/marketplace). A descrição muito curta de cada aplicativo é exibida abaixo de seu cartão de recursos. +A feature card consists of your app's logo, name, and a custom background image that captures your brand personality. {% data variables.product.prodname_marketplace %} displays this card if your app is one of the four randomly featured apps at the top of the [homepage](https://github.com/marketplace). Each app's very short description is displayed below its feature card. -![Cartão de recurso](/assets/images/marketplace/marketplace_feature_card.png) +![Feature card](/assets/images/marketplace/marketplace_feature_card.png) -À medida que você faz o upload das imagens e seleciona as cores, sua listagem de rascunho do {% data variables.product.prodname_marketplace %} exibirá uma prévia do seu logotipo e do seu cartão de recurso. +As you upload images and select colors, your {% data variables.product.prodname_marketplace %} draft listing will display a preview of your logo and feature card. -#### Diretrizes para logotipos +#### Guidelines for logos -Você deve enviar uma imagem personalizada para o logotipo. Escolha uma cor de fundo para o selo. +You must upload a custom image for the logo. For the badge, choose a background color. -- Faça upload de uma imagem do logotipo com, pelo menos, 200 pixels x 200 pixels para que seu logotipo não tenha que ser dimensionado quando a sua listagem for publicada. -- Os logotipos serão cortados em um quadrado. Recomendamos fazer o upload de um arquivo de imagem quadrada com seu logotipo no centro. -- Para obter o melhor resultado, faça o upload de uma imagem de logotipo com um fundo transparente. -- Para dar a aparência de um selo perfeito, escolha uma cor de fundo para o selo que corresponda à cor de fundo (ou transparência) da imagem do seu logotipo. -- Evite usar imagens do logotipo com palavras ou texto. Os logotipos com texto não são bem dimensionados em telas pequenas. +- Upload a logo image that is at least 200 pixels x 200 pixels so your logo won't have to be upscaled when your listing is published. +- Logos will be cropped to a square. We recommend uploading a square image file with your logo in the center. +- For best results, upload a logo image with a transparent background. +- To give the appearance of a seamless badge, choose a badge background color that matches the background color (or transparency) of your logo image. +- Avoid using logo images with words or text in them. Logos with text do not scale well on small screens. -#### Diretrizes para cartões de recurso +#### Guidelines for feature cards -Você deve enviar uma imagem de fundo personalizada para o cartão de recurso. Para o nome do aplicativo, escolha uma cor do texto. +You must upload a custom background image for the feature card. For the app's name, choose a text color. -- Use um padrão ou textura na sua imagem de fundo para dar ao seu cartão uma identidade visual e ajudá-lo a destacar-se com relação ao fundo escuro da página inicial do {% data variables.product.prodname_marketplace %}. Os cartões de recursos devem capturar a personalidade da sua marca. -- A iImagem de fundo mede 965 pixels x 482 pixels (largura x altura). -- Escolha uma cor de texto para o nome do aplicativo que aparece claramente sobre a imagem de fundo. +- Use a pattern or texture in your background image to give your card a visual identity and help it stand out against the dark background of the {% data variables.product.prodname_marketplace %} homepage. Feature cards should capture your app's brand personality. +- Background image measures 965 pixels x 482 pixels (width x height). +- Choose a text color for your app's name that shows up clearly over the background image. -## Detalhes da listagem +## Listing details -Para acessar a página inicial do seu aplicativo, clique no nome do aplicativo na página inicial ou na página de categoria do {% data variables.product.prodname_marketplace %}. A página de destino exibe uma descrição mais longa do aplicativo, que inclui duas partes: uma "Descrição introdutória" e uma "Descrição detalhada". +To get to your app's landing page, click your app's name from the {% data variables.product.prodname_marketplace %} homepage or category page. The landing page displays a longer description of the app, which includes two parts: an "Introductory description" and a "Detailed description." -A sua "Descrição introdutória" é exibida no topo da página inicial {% data variables.product.prodname_marketplace %} do seu aplicativo. +Your "Introductory description" is displayed at the top of your app's {% data variables.product.prodname_marketplace %} landing page. -![Descrição introdutória do {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_intro_description.png) +![{% data variables.product.prodname_marketplace %} introductory description](/assets/images/marketplace/marketplace_intro_description.png) -Se você clicar em **Ler mais…** , a "Descrição detalhada" será exibida. +Clicking **Read more...**, displays the "Detailed description." -![Descrição detalhada do {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_detailed_description.png) +![{% data variables.product.prodname_marketplace %} detailed description](/assets/images/marketplace/marketplace_detailed_description.png) -Siga estas instruções para escrever estas descrições. +Follow these guidelines for writing these descriptions. -### Comprimento +### Length -Recomendamos escrever um resumo de uma a duas frases de alto nível entre 150-250 caracteres no campo "Descrição introdutória" obrigatório ao [listar seu aplicativo](/marketplace/listing-on-github-marketplace/). Embora seja permitido o uso de mais caracteres, os resumos concisos são mais fáceis de ler e entender pelos clientes rapidamente. +We recommend writing a 1-2 sentence high-level summary between 150-250 characters in the required "Introductory description" field when [listing your app](/marketplace/listing-on-github-marketplace/). Although you are allowed to use more characters, concise summaries are easier for customers to read and understand quickly. -Você pode adicionar mais informações ao campo opcional "Descrição detalhada". Você verá essa descrição ao clicar em **Ler mais…** abaixo da descrição introdutória na página de aterrissagem do seu aplicativo. Uma descrição detalhada consiste em três a cinco [propostas de valor](https://en.wikipedia.org/wiki/Value_proposition), com uma a duas frases descrevendo cada uma delas. Você pode usar até 1.000 caracteres para essa descrição. +You can add more information in the optional "Detailed description" field. You see this description when you click **Read more...** below the introductory description on your app's landing page. A detailed description consists of 3-5 [value propositions](https://en.wikipedia.org/wiki/Value_proposition), with 1-2 sentences describing each one. You can use up to 1,000 characters for this description. -### Conteúdo +### Content -- Sempre comece descrições introdutórias com o nome do seu aplicativo. +- Always begin introductory descriptions with your app's name. -- Sempre escreva as descrições e as propostas de valores usando a voz ativa. +- Always write descriptions and value propositions using the active voice. -### Formatação +### Formatting -- Sempre use as letras maiúsculas adequadamente nas frases dos títulos para as propostas de valor. Use maiúscula somente para a primeira letra e para substantivos próprios. +- Always use sentence-case capitalization in value proposition titles. Only capitalize the first letter and proper nouns. -- Use pontos nas suas descrições. Evite pontos de exclamação. +- Use periods in your descriptions. Avoid exclamation marks. -- Não use pontuação no final dos títulos da sua proposição de valor. Títulos de proposição de valor não devem incluir frases completas,e não devem incluir mais de uma frase. +- Don't use punctuation at the end of your value proposition titles. Value proposition titles should not include complete sentences, and should not include more than one sentence. -- Para cada proposta de valor, inclua um título seguido de um parágrafo de descrição. Formate o título como um [cabeçalho de nível três](/articles/basic-writing-and-formatting-syntax/#headings) usando o Markdown. Por exemplo: +- For each value proposition, include a title followed by a paragraph of description. Format the title as a [level-three header](/articles/basic-writing-and-formatting-syntax/#headings) using Markdown. For example: - ### Aprenda as habilidades de que você precisa + ### Learn the skills you need - Com o GitHub Skills, você pode aprender a usar o GitHub, se comunicar de modo mais efetivo usando Markdown, gerenciar conflitos de mesclagem, entre outras coisas. + GitHub Skills can help you learn how to use GitHub, communicate more effectively with Markdown, handle merge conflicts, and more. -- Use maiúscula apenas para os substantivos próprios. +- Only capitalize proper nouns. -- Sempre use a [vírgula de série](https://en.wikipedia.org/wiki/Serial_comma) em listas. +- Always use the [serial comma](https://en.wikipedia.org/wiki/Serial_comma) in lists. -- Evite referir-se à comunidade do GitHub como "usuários". +- Avoid referring to the GitHub community as "users." - **O QUE FAZER:** crie problemas automaticamente para as pessoas na sua organização + **DO:** Create issues automatically for people in your organization - **O QUE NÃO FAZER:** crie problemas automaticamente para os usuários de uma organização + **DON'T:** Create issues automatically for an organization's users -- Evite acrônimos, a menos que estejam conhecidos (como, por exemplo, API). +- Avoid acronyms unless they’re well established (such as API). -## Capturas de tela dos produtos +## Product screenshots -Você pode enviar até cinco imagens de captura de tela do seu aplicativo para ser exibidas na página inicial do seu aplicativo. Adicione uma legenda opcional para cada captura de tela para fornecer contexto. Após enviar suas capturas de tela, você pode arrastá-las para a ordem que você deseja que sejam exibidas na página inicial. +You can upload up to five screenshot images of your app to display on your app's landing page. Add an optional caption to each screenshot to provide context. After you upload your screenshots, you can drag them into the order you want them to be displayed on the landing page. -### Diretrizes para capturas de tela +### Guidelines for screenshots -- As imagens devem ser de alta resolução (pelo menos 1200 px de largura). -- Todas as imagens devem ter a mesma altura e largura (proporção de aspecto) para evitar pular páginas quando as pessoas clicam de uma imagem para a seguinte. -- Mostre a maior quantidade possível de interface de usuário para que as pessoas possam ver o que seu aplicativo faz. -- Ao capturar telas do seu app em um navegador, inclua apenas o conteúdo na janela de exibição. Evite incluir a barra de endereço, barra de título ou ícones da barra de ferramentas, que não são bem dimensionados para tamanhos de tela menores. -- O GitHub exibe as capturas de tela das quais você fizer o upload em uma caixa na página inicial do seu aplicativo. Portanto, você não precisa adicionar caixas ou bordas ao redor de suas capturas de tela. -- As legendas são mais eficazes quando são curtas e ágeis. +- Images must be of high resolution (at least 1200px wide). +- All images must be the same height and width (aspect ratio) to avoid page jumps when people click from one image to the next. +- Show as much of the user interface as possible so people can see what your app does. +- When taking screenshots of your app in a browser, only include the content in the display window. Avoid including the address bar, title bar, or toolbar icons, which do not scale well to smaller screen sizes. +- GitHub displays the screenshots you upload in a box on your app's landing page, so you don't need to add boxes or borders around your screenshots. +- Captions are most effective when they are short and snappy. -![Imagem de captura de tela do GitHub Marketplace](/assets/images/marketplace/marketplace-screenshots.png) +![GitHub Marketplace screenshot image](/assets/images/marketplace/marketplace-screenshots.png) diff --git a/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md b/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md index 89d6724d97..39aa90ed6b 100644 --- a/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md +++ b/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md @@ -1,6 +1,6 @@ --- -title: Planos de preços para aplicativos do GitHub Marketplace -intro: 'Os planos de preços permitem que você forneça ao seu aplicativo diferentes níveis de serviço ou recursos. Você pode oferecer até 10 planos de preços na sua listagem do {% data variables.product.prodname_marketplace %}.' +title: Pricing plans for GitHub Marketplace apps +intro: 'Pricing plans allow you to provide your app with different levels of service or resources. You can offer up to 10 pricing plans in your {% data variables.product.prodname_marketplace %} listing.' redirect_from: - /apps/marketplace/selling-your-app/github-marketplace-pricing-plans - /marketplace/selling-your-app/github-marketplace-pricing-plans @@ -11,55 +11,49 @@ versions: topics: - Marketplace shortTitle: Pricing plans for apps -ms.openlocfilehash: e1ab751c26e59ec42e16dc7d9e5c0118dedffbde -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147875559' --- -Os planos de preços de {% data variables.product.prodname_marketplace %} podem ser grátis, fixos ou por unidade. Os preços são definidos, exibidos e processados em dólares. Os planos pagos são restritos a aplicativos publicados por editores verificados. Para obter mais informações sobre como se tornar um fornecedor verificado, confira "[Como solicitar a verificação de fornecedor para sua organização](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)". +{% data variables.product.prodname_marketplace %} pricing plans can be free, flat rate, or per-unit. Prices are set, displayed, and processed in US dollars. Paid plans are restricted to apps published by verified publishers. For more information about becoming a verified publisher, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)." -Os clientes compram seu aplicativo usando um método de pagamento anexado à sua conta em {% data variables.product.product_location %}, sem ter que sair de {% data variables.product.prodname_dotcom_the_website %}. Você não precisa escrever um código para realizar transações de cobrança, mas deverá gerenciar eventos da API de {% data variables.product.prodname_marketplace %}. Para obter mais informações, confira "[Como usar a API do {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". +Customers purchase your app using a payment method attached to their account on {% data variables.location.product_location %}, without having to leave {% data variables.product.prodname_dotcom_the_website %}. You don't have to write code to perform billing transactions, but you will have to handle events from the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -Se o aplicativo que você está listando no {% data variables.product.prodname_marketplace %} tiver várias opções de plano, você poderá definir os planos de preços correspondentes. Por exemplo, se o app tiver duas opções de plano, um plano de código aberto e um plano profissional, você poderá criar um plano de preços grátis para o seu plano de código aberto e um plano de preço fixo para o seu plano profissional. Cada listagem do {% data variables.product.prodname_marketplace %} deve ter um preço anual e um preço mensal para todos os planos listados. +If the app you're listing on {% data variables.product.prodname_marketplace %} has multiple plan options, you can set up corresponding pricing plans. For example, if your app has two plan options, an open source plan and a pro plan, you can set up a free pricing plan for your open source plan and a flat pricing plan for your pro plan. Each {% data variables.product.prodname_marketplace %} listing must have an annual and a monthly price for every plan that's listed. -Para obter mais informações sobre como criar um plano de preços, confira "[Como definir um plano de preços de listagem do {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)". +For more information on how to create a pricing plan, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)." {% data reusables.marketplace.free-plan-note %} -## Tipos de planos de preços +## Types of pricing plans -### Planos de preços grátis +### Free pricing plans {% data reusables.marketplace.free-apps-encouraged %} -Planos grátis são completamente grátis para os usuários. Se você configurar um plano de preços grátis, você não poderá cobrar os usuários que escolherem o plano de preços grátis para o uso do seu aplicativo. Você pode criar planos grátis e pagos para a sua listagem. +Free plans are completely free for users. If you set up a free pricing plan, you cannot charge users that choose the free pricing plan for the use of your app. You can create both free and paid plans for your listing. -Todos os aplicativos precisam gerenciar eventos para novas compras e cancelamentos. Os aplicativos que só têm planos grátis não precisam gerenciar eventos para testes, atualizações e downgrades grátis. Para obter mais informações, confira: "[Como usar a API do {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". +All apps need to handle events for new purchases and cancellations. Apps that only have free plans do not need to handle events for free trials, upgrades, and downgrades. For more information, see: "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -Se você adicionar um plano pago a um aplicativo que já esteja listado em {% data variables.product.prodname_marketplace %} como um serviço grátis, você precisará solicitar verificação para o aplicativo e passar pela integração financeira. +If you add a paid plan to an app that you've already listed in {% data variables.product.prodname_marketplace %} as a free service, you'll need to request verification for the app and go through financial onboarding. -### Planos de preços pagos +### Paid pricing plans -Existem dois tipos de planos de preços pagos: +There are two types of paid pricing plan: -- Os planos de preços fixos cobram uma taxa definida mensalmente e anualmente. +- Flat rate pricing plans charge a set fee on a monthly and yearly basis. -- Os planos de preços por unidade cobram uma taxa definida mensalmente ou anualmente para uma unidade que você especificar. Uma "unidade" pode ser qualquer coisa que você deseje (por exemplo, um usuário, estação ou pessoa). +- Per-unit pricing plans charge a set fee on either a monthly or yearly basis for a unit that you specify. A "unit" can be anything you'd like (for example, a user, seat, or person). -Você também pode oferecer testes grátis. Eles fornecem gratuitamente testes de 14 dias referentes aos aplicativos OAuth ou GitHub para os clientes. Ao configurar um plano de preços do Marketplace você poderá selecionar a opção de fornecer um teste gratuito para planos de taxa fixa ou por unidade de preços +You may also want to offer free trials. These provide free, 14-day trials of OAuth or GitHub Apps to customers. When you set up a Marketplace pricing plan, you can select the option to provide a free trial for flat-rate or per-unit pricing plans. -## Avaliações gratuitas +## Free trials -Os clientes podem iniciar uma avaliação gratuita para qualquer plano pago de um anúncio do Marketplace que inclui testes grátis. No entanto, os clientes não podem criar mais de um teste grátis por produto no marketplace. +Customers can start a free trial for any paid plan on a Marketplace listing that includes free trials. However, customers cannot create more than one free trial per marketplace product. -Os testes gratuitos têm uma duração fixa de 14 dias. Os clientes são notificados 4 dias antes do final do período de teste (no 11o dia do teste grátis) de que seu plano será atualizado. No final do teste grátis, os clientes serão inscritos automaticamente no plano que estão testando, caso não efetuem o cancelamento. +Free trials have a fixed length of 14 days. Customers are notified 4 days before the end of their trial period (on day 11 of the free trial) that their plan will be upgraded. At the end of a free trial, customers will be auto-enrolled into the plan they are trialing if they do not cancel. -Para obter mais informações, confira: "[Como lidar com novas compras e avaliações gratuitas](/developers/github-marketplace/handling-new-purchases-and-free-trials/)". +For more information, see: "[Handling new purchases and free trials](/developers/github-marketplace/handling-new-purchases-and-free-trials/)." {% note %} -**Observação:** o GitHub espera que você exclua todos os dados particulares do cliente no prazo de 30 dias após o cancelamento da avaliação, a contar do recebimento do evento de cancelamento. +**Note:** GitHub expects you to delete any private customer data within 30 days of a cancelled trial, beginning at the receipt of the cancellation event. {% endnote %} diff --git a/translations/pt-BR/content/developers/overview/about-githubs-apis.md b/translations/pt-BR/content/developers/overview/about-githubs-apis.md index 0911a23156..dbaa547ee2 100644 --- a/translations/pt-BR/content/developers/overview/about-githubs-apis.md +++ b/translations/pt-BR/content/developers/overview/about-githubs-apis.md @@ -18,9 +18,9 @@ topics: {% data variables.product.company_short %} provides two APIs: a REST API and a GraphQL API. You can interact with both APIs using {% data variables.product.prodname_cli %}, curl, the official Octokit libraries, and third party libraries. Occasionally, a feature may be supported on one API but not the other. -You should choose the API that best aligns with your needs and that you are most comfortable using. This article discusses the benefits of each API. +You should use the API that best aligns with your needs and that you are most comfortable using. You don't need to exclusively use one API over the other. Node IDs let you move between the REST API and GraphQL API. For more information, see "[Using global node IDs](/graphql/guides/using-global-node-ids)." -For more information about the GraphQL API, see [the GraphQL documentation](/graphql). For more information about the REST API, see [the REST documentation](/rest). +This article discusses the benefits of each API. For more information about the GraphQL API, see "[About the GraphQL API](/graphql/overview/about-the-graphql-api)." For more information about the REST API, see [the REST documentation](/rest). ## Choosing the GraphQL API @@ -79,7 +79,3 @@ mutation { } } ``` - -## Choosing both - -You don't need to exclusively use one API over the other. Node IDs let you move between the REST API and GraphQL API. For more information, see "[Using global node IDs](/graphql/guides/using-global-node-ids)." diff --git a/translations/pt-BR/content/developers/overview/managing-deploy-keys.md b/translations/pt-BR/content/developers/overview/managing-deploy-keys.md index 45e840a023..9f838c2051 100644 --- a/translations/pt-BR/content/developers/overview/managing-deploy-keys.md +++ b/translations/pt-BR/content/developers/overview/managing-deploy-keys.md @@ -61,7 +61,7 @@ If you don't want to use SSH keys, you can use HTTPS with OAuth tokens. #### Setup -See [our guide on creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token). +See [our guide on creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token). ## Deploy keys @@ -151,7 +151,7 @@ Since GitHub Apps are a first class actor on {% data variables.product.product_ ## Machine users -If your server needs to access multiple repositories, you can create a new account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} and attach an SSH key that will be used exclusively for automation. Since this account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team). +If your server needs to access multiple repositories, you can create a new account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} and attach an SSH key that will be used exclusively for automation. Since this account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team). {% ifversion fpt or ghec %} diff --git a/translations/pt-BR/content/developers/overview/secret-scanning-partner-program.md b/translations/pt-BR/content/developers/overview/secret-scanning-partner-program.md index 6f888275c8..dfbff80a06 100644 --- a/translations/pt-BR/content/developers/overview/secret-scanning-partner-program.md +++ b/translations/pt-BR/content/developers/overview/secret-scanning-partner-program.md @@ -110,7 +110,7 @@ key to use based on the value of `GITHUB-PUBLIC-KEY-IDENTIFIER`. {% note %} -**Note**: When you send a request to the public key endpoint above, you may hit rate limits. To avoid hitting rate limits, you can use a personal access token (no scopes required) as suggested in the samples below, or use a conditional request. For more information, see "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#conditional-requests)." +**Note**: When you send a request to the public key endpoint above, you may hit rate limits. To avoid hitting rate limits, you can use a {% data variables.product.pat_v1 %} (no scopes required){% ifversion pat-v2 %} or a {% data variables.product.pat_v2 %} (only the automatic public repositories read access required){% endif %} as suggested in the samples below, or use a conditional request. For more information, see "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#conditional-requests)." {% endnote %} @@ -149,7 +149,7 @@ HzZFI03Exwz8Lh/tCfL3YxwMdLjB+bMznsanlhK0RwcGP3IDb34kQDIo3Q== {% endnote %} The following code snippets demonstrate how you could perform signature validation. -The code examples assume you've set an environment variable called `GITHUB_PRODUCTION_TOKEN` with a generated [personal access token](https://github.com/settings/tokens) (PAT) to avoid hitting rate limits. The PAT does not need any scopes/permissions. +The code examples assume you've set an environment variable called `GITHUB_PRODUCTION_TOKEN` with a generated [{% data variables.product.pat_generic %}](https://github.com/settings/tokens) to avoid hitting rate limits. The {% data variables.product.pat_generic %} does not need any scopes/permissions. **Validation sample in Go** ```golang diff --git a/translations/pt-BR/content/discussions/guides/finding-your-discussions.md b/translations/pt-BR/content/discussions/guides/finding-your-discussions.md index 0cdd8c6112..5cf3819504 100644 --- a/translations/pt-BR/content/discussions/guides/finding-your-discussions.md +++ b/translations/pt-BR/content/discussions/guides/finding-your-discussions.md @@ -1,26 +1,22 @@ --- -title: Encontrar suas discussões -intro: É possível acessar facilmente todas as discussões que você criou ou participou. +title: Finding your discussions +intro: You can easily access every discussion you've created or participated in. versions: feature: discussions shortTitle: Find discussions redirect_from: - /discussions/guides/finding-discussions-across-multiple-repositories -ms.openlocfilehash: cef92d2d042ece7feeeb0364244a70520f12966d -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147883268' --- -## Encontrar discussões -1. No canto superior direito do {% data variables.product.product_location %}, clique na foto do seu perfil e em **Suas discussões**. - !["Suas discussões" no menu suspenso da foto de perfil no {% data variables.product.product_name %}](/assets/images/help/discussions/your-discussions.png) -1. Alterne entre **Criadas** e **Comentadas** para ver as discussões que você criou ou das quais participou. -## Leitura adicional +## Finding discussions -- "[Pesquisa de discussões](/search-github/searching-on-github/searching-discussions)" -- "[Sobre as discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" -- "[Como gerenciar as discussões da sua comunidade](/discussions/managing-discussions-for-your-community)" +1. In the top-right corner of {% data variables.location.product_location %}, click your profile photo, then click **Your discussions**. + !["Your discussions" in drop-down menu for profile photo on {% data variables.product.product_name %}](/assets/images/help/discussions/your-discussions.png) +1. Toggle between **Created** and **Commented** to see the discussions you've created or participated in. + +## Further reading + +- "[Searching discussions](/search-github/searching-on-github/searching-discussions)" +- "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" +- "[Managing discussions for your community](/discussions/managing-discussions-for-your-community)" diff --git a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md index ec3471a8c1..bd69c78cb1 100644 --- a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md +++ b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md @@ -1,70 +1,68 @@ --- -title: Gerenciar categorias para discussões -intro: Você pode categorizar as discussões para organizar conversas para integrantes da sua comunidade e você pode escolher um formato para cada categoria. +title: Managing categories for discussions +intro: 'You can categorize discussions to organize conversations for your community members, and you can choose a format for each category.' permissions: Repository administrators and people with write or greater access to a repository can manage categories for discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage categories for discussions in the organization. versions: feature: discussions shortTitle: Manage categories redirect_from: - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository -ms.openlocfilehash: e16d25ad2bb72f4aea9b441529cb8e9a7a0fee48 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147410464' --- -## Sobre categorias para discussões + + +## About categories for discussions {% data reusables.discussions.about-discussions %} {% data reusables.discussions.about-categories-and-formats %} {% data reusables.discussions.about-announcement-format %} -Cada categoria deve ter um nome e um pareamento de emojis únicos e pode ser acompanhada de uma descrição detalhada que informa o seu propósito. As categorias ajudam os mantenedores a organizar como as conversas são arquivadas e podem ser personalizadas para ajudar a distinguir as categorias que são perguntas e respostas ou conversas mais abertas. {% data reusables.discussions.repository-category-limit %} Para obter mais informações, confira "[Sobre as discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)". +Each category must have a unique name and emoji pairing, and can be accompanied by a detailed description stating its purpose. Categories help maintainers organize how conversations are filed and are customizable to help distinguish categories that are Q&A or more open-ended conversations. {% data reusables.discussions.repository-category-limit %} For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." -## Categorias-padrão +## Default categories -| Categoria | Finalidade | Formatar | +| Category | Purpose | Format | | :- | :- | :- | -| 📣 Comunicados | Atualizações e notícias de mantenedores do projeto | Anúncio | -| #️⃣ Geral | Tudo que for relevante para o projeto | Discussão aberta | -|💡 Ideias | Ideias para alterar ou melhorar o projeto | Discussão aberta | -| 🗳 Pesquisas | Pesquisas com várias opções para a comunidade votar e discutir | Pesquisas | -| 🙏 Perguntas e respostas | Perguntas para a comunidade responder, com um formato de pergunta/resposta | Pergunta e resposta | -| 🙌 Mostrar e contar | Criações, experimentos ou testes relevantes para o projeto | Discussão aberta | +| 📣 Announcements | Updates and news from project maintainers | Announcement | +| #️⃣ General | Anything and everything relevant to the project | Open-ended discussion | +|💡 Ideas | Ideas to change or improve the project | Open-ended discussion | +| 🗳 Polls | Polls with multiple options for the community to vote for and discuss | Polls | +| 🙏 Q&A | Questions for the community to answer, with a question/answer format | Question and Answer | +| 🙌 Show and tell | Creations, experiments, or tests relevant to the project | Open-ended discussion | -## Criar categoria +## Creating a category -1. Em {% data variables.product.product_location %}, navegue até a página principal do repositório ou organização em que você deseja criar uma categoria. -{% data reusables.discussions.discussions-tab %} {% data reusables.discussions.edit-categories %} -1. Clique em **Nova categoria**. - ![Botão "Nova categoria" acima da lista de categorias de discussão de um repositório](/assets/images/help/discussions/click-new-category-button.png) -1. Edite o emoji, título, descrição e formato de discussão para a categoria. Para obter mais informações sobre os formatos de discussão, confira "[Sobre as discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)". - ![Emoji, título, descrição e formato de discussão para a nova categoria](/assets/images/help/discussions/edit-category-details.png) -1. Clique em **Criar**. - ![Botão "Criar" para nova categoria](/assets/images/help/discussions/new-category-click-create-button.png) - -## Editar uma categoria - -Você pode editar uma categoria para alterar o emoji, título, descrição e formato da discussão. - -1. Em {% data variables.product.product_location %}, navegue até a página principal do repositório ou organização em que você deseja editar uma categoria. +1. On {% data variables.location.product_location %}, navigate to the main page of the repository or organization where you want to create a category. {% data reusables.discussions.discussions-tab %} -1. À direita de uma categoria na lista, clique em {% octicon "pencil" aria-label="The pencil icon" %}. - ![Botão Editar à direita da categoria na lista de categorias de um repositório](/assets/images/help/discussions/click-edit-for-category.png) -1. {% data reusables.discussions.edit-category-details %} ![Edição de emoji, título, descrição e formato de discussão para a categoria existente](/assets/images/help/discussions/edit-existing-category-details.png) -1. Clique em **Salvar alterações**. - ![Botão "Salvar alterações" para a categoria existente](/assets/images/help/discussions/existing-category-click-save-changes-button.png) +{% data reusables.discussions.edit-categories %} +1. Click **New category**. + !["New category" button above list of discussion categories for a repository](/assets/images/help/discussions/click-new-category-button.png) +1. Edit the emoji, title, description, and discussion format for the category. For more information about discussion formats, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." + ![Emoji, title, description, and discussion format for new category](/assets/images/help/discussions/edit-category-details.png) +1. Click **Create**. + !["Create" button for new category](/assets/images/help/discussions/new-category-click-create-button.png) -## Excluir uma categoria +## Editing a category -Ao você excluir uma categoria, {% data variables.product.product_name %} moverá todas as discussões da categoria excluída para uma categoria existente que você escolher. +You can edit a category to change the category's emoji, title, description, and discussion format. -1. Em {% data variables.product.product_location %}, navegue até a página principal do repositório ou organização em que você deseja excluir uma categoria. +1. On {% data variables.location.product_location %}, navigate to the main page of the repository or organization where you want to edit a category. {% data reusables.discussions.discussions-tab %} -1. À direita de uma categoria na lista, clique em {% octicon "trash" aria-label="The trash icon" %}. - ![Botão da lixeira à direita da categoria na lista de categorias de um repositório](/assets/images/help/discussions/click-delete-for-category.png) -1. Use o menu suspenso e escolha uma nova categoria para qualquer discussão na categoria que você está excluindo. - ![Menu suspenso usado para escolher uma nova categoria ao excluir uma categoria existente](/assets/images/help/discussions/choose-new-category.png) -1. Clique em **Excluir e Mover**. - ![Menu suspenso usado para escolher uma nova categoria ao excluir uma categoria existente](/assets/images/help/discussions/click-delete-and-move-button.png) +1. To the right of a category in the list, click {% octicon "pencil" aria-label="The pencil icon" %}. + ![Edit button to the right of category in list of categories for a repository](/assets/images/help/discussions/click-edit-for-category.png) +1. {% data reusables.discussions.edit-category-details %} + ![Editing emoji, title, description, and discussion format for existing category](/assets/images/help/discussions/edit-existing-category-details.png) +1. Click **Save changes**. + !["Save changes" button for existing category](/assets/images/help/discussions/existing-category-click-save-changes-button.png) + +## Deleting a category + +When you delete a category, {% data variables.product.product_name %} will move all discussions in the deleted category to an existing category that you choose. + +1. On {% data variables.location.product_location %}, navigate to the main page of the repository or organization where you want to delete a category. +{% data reusables.discussions.discussions-tab %} +1. To the right of a category in the list, click {% octicon "trash" aria-label="The trash icon" %}. + ![Trash button to the right of category in list of categories for a repository](/assets/images/help/discussions/click-delete-for-category.png) +1. Use the drop-down menu, and choose a new category for any discussions in the category you're deleting. + ![Drop-down menu for choosing new category when deleting an existing category](/assets/images/help/discussions/choose-new-category.png) +1. Click **Delete & Move**. + ![Drop-down menu for choosing new category when deleting an existing category](/assets/images/help/discussions/click-delete-and-move-button.png) diff --git a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-discussions.md b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-discussions.md index 9e60c2ac88..2c45e9104d 100644 --- a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-discussions.md +++ b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-discussions.md @@ -1,109 +1,118 @@ --- -title: Gerenciando discussões -intro: 'Você pode categorizar, destacar e transferir ou excluir as discussões.' +title: Managing discussions +intro: 'You can categorize, spotlight, transfer, or delete the discussions.' permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage discussions in the organization. versions: feature: discussions shortTitle: Manage discussions redirect_from: - /discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository -ms.openlocfilehash: 95e806959eef023fd05e91a43f9269c98b5db052 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147786211' --- -## Sobre o gerenciamento de discussões -{% data reusables.discussions.about-discussions %} Para obter mais informações sobre as discussões, confira "[Sobre as discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". -Os proprietários da organização podem escolher as permissões necessárias para criar uma discussão em repositórios pertencentes à organização. Da mesma forma, para escolher as permissões necessárias para criar uma discussão da organização, os proprietários da organização podem alterar as permissões necessárias no repositório de origem. Para obter mais informações, confira "[Como gerenciar a criação de discussões para repositórios na sua organização](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)". +## About management of discussions -Como mantenedor de discussões, você pode criar recursos da comunidade para incentivar discussões alinhadas com o objetivo geral do projeto e manter um fórum aberto amigável para os colaboradores. Criar{% ifversion fpt or ghec %} um código de conduta ou{% endif %} diretrizes de contribuição para os colaboradores a seguir ajudará a facilitar um fórum colaborativo e produtivo. Para obter mais informações sobre como criar recursos da comunidade, confira{% ifversion fpt or ghec %} "[Como adicionar um código de conduta ao seu projeto](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" e{% endif %} "[Como definir diretrizes para colaboradores do repositório](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)". +{% data reusables.discussions.about-discussions %} For more information about discussions, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." -Quando uma discussão fornece uma ideia ou um erro que está pronto para ser trabalhado, você pode criar um novo problema a partir de uma discussão. Para obter mais informações, confira "[Como criar um problema](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)". +Organization owners can choose the permissions required to create a discussion in repositories owned by the organization. Similarly, to choose the permissions required to create an organization discussion, organization owners can change the permissions required in the source repository. For more information, see "[Managing discussion creation for repositories in your organization](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)." -Para obter mais informações sobre como facilitar uma discussão útil, confira "[Como moderar comentários e conversas](/communities/moderating-comments-and-conversations)". +As a discussions maintainer, you can create community resources to encourage discussions that are aligned with the overall project goal and maintain a friendly open forum for collaborators. Creating{% ifversion fpt or ghec %} a code of conduct or{% endif %} contribution guidelines for collaborators to follow will help facilitate a collaborative and productive forum. For more information on creating community resources, see{% ifversion fpt or ghec %} "[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)," and{% endif %} "[Setting guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)." + +When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)." + +For more information on facilitating a healthy discussion, see "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)." {% data reusables.discussions.you-can-label-discussions %} -## Pré-requisitos +## Prerequisites -Para gerenciar as discussões em um repositório, {% data variables.product.prodname_discussions %} deve estar habilitado para o repositório. Para obter mais informações, confira "[Como habilitar ou desabilitar o {% data variables.product.prodname_discussions %} para um repositório](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)". +To manage discussions in a repository, {% data variables.product.prodname_discussions %} must be enabled for the repository. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." -Para gerenciar as discussões em uma organização, o {% data variables.product.prodname_discussions %} deve estar habilitado na organização. Para obter mais informações, confira "[Como habilitar ou desabilitar o {% data variables.product.prodname_discussions %} em uma organização](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)". +To manage discussions in an organization, {% data variables.product.prodname_discussions %} must be enabled for the organization. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)." -## Alterar a categoria para uma discussão +## Changing the category for a discussion -Você pode categorizar discussões para ajudar os integrantes da comunidade a encontrar discussões relacionadas. Para obter mais informações, confira "[Gerenciar categorias para discussões](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)". +You can categorize discussions to help community members find related discussions. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)." -Você também pode mover a discussão para uma categoria diferente. Não é possível mover uma discussão para ou da categoria de votação. +You can also move a discussion to a different category. It's not possible to move a discussion to or from the polls category. -{% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. Na barra lateral direita, à direita da "Categoria", clique em {% octicon "gear" aria-label="The gear icon" %}. - !["Categoria" com o ícone de engrenagem](/assets/images/help/discussions/category-in-sidebar.png) -1. Clique em uma categoria. - ![Menu suspenso "Alterar categoria"](/assets/images/help/discussions/change-category-drop-down.png) +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, to the right of "Category", click {% octicon "gear" aria-label="The gear icon" %}. + !["Category" with gear icon](/assets/images/help/discussions/category-in-sidebar.png) +1. Click a category. + !["Change category" drop-down menu](/assets/images/help/discussions/change-category-drop-down.png) -## Fixar uma discussão +## Pinning a discussion -Você pode fixar até quatro discussões importantes acima da lista de discussões do repositório ou da organização. +You can pin up to four important discussions above the list of discussions for the repository or organization. -{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. Na barra lateral direita, clique em {% octicon "pin" aria-label="The pin icon" %} **Fixar discussão**. - !["Fixar discussão" na barra lateral direita da discussão](/assets/images/help/discussions/click-pin-discussion.png) -1. Opcionalmente, personalize a aparência da discussão fixada. - ![Opções de personalização para uma discussão fixa](/assets/images/help/discussions/customize-pinned-discussion.png) -1. Clique em **Fixar discussão**. - ![Botão "Fixar discussão" nas opções de personalização da discussão fixa](/assets/images/help/discussions/click-pin-discussion-button.png) +{% data reusables.discussions.navigate-to-repo-or-org %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**. + !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-pin-discussion.png) +1. Optionally, customize the look of the pinned discussion. + ![Customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png) +1. Click **Pin discussion**. + !["Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png) -## Editar uma discussão fixada +## Editing a pinned discussion -Editar uma discussão fixada não irá alterar a categoria da discussão. Para obter mais informações, confira "[Gerenciar categorias para discussões](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)". +Editing a pinned discussion will not change the discussion's category. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)." -{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. Na barra lateral direita, clique em {% octicon "pencil" aria-label="The pencil icon" %} **Editar discussão fixa**. - !["Editar discussão fixa" na barra lateral direita da discussão](/assets/images/help/discussions/click-edit-pinned-discussion.png) -1. Personalize a aparência da discussão fixada. - ![Opções de personalização para uma discussão fixa](/assets/images/help/discussions/customize-pinned-discussion.png) -1. Clique em **Fixar discussão**. - ![Botão "Fixar discussão" nas opções de personalização da discussão fixa](/assets/images/help/discussions/click-pin-discussion-button.png) +{% data reusables.discussions.navigate-to-repo-or-org %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**. + !["Edit pinned discussion" in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png) +1. Customize the look of the pinned discussion. + ![Customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png) +1. Click **Pin discussion**. + !["Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png) -## Desafixar uma discussão +## Unpinning a discussion -{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. Na barra lateral direita, clique em {% octicon "pin" aria-label="The pin icon" %} **Desafixar discussão**. - !["Desafixar discussão" na barra lateral direita da discussão](/assets/images/help/discussions/click-unpin-discussion.png) -1. Leia o aviso e clique em **Desafixar discussão**. - ![Botão "Desafixar discussão" abaixo do aviso na caixa de diálogo modal](/assets/images/help/discussions/click-unpin-discussion-button.png) +{% data reusables.discussions.navigate-to-repo-or-org %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**. + !["Unpin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-unpin-discussion.png) +1. Read the warning, then click **Unpin discussion**. + !["Unpin discussion" button beneath warning in modal](/assets/images/help/discussions/click-unpin-discussion-button.png) -## Transferir uma discussão +## Transferring a discussion -Para transferir uma discussão, você precisa ter permissão de criar discussões no repositório, em que você deseja transferir a discussão. Se você quiser transferir uma discussão para uma organização, deverá ter permissões para criar discussões no repositório de origem das discussões da organização. Você somente pode transferir discussões entre repositórios pertencentes à mesma conta de usuário ou organização. Você não pode transferir uma discussão de um repositório privado{% ifversion ghec or ghes %} ou interno{% endif %} para um repositório público. +To transfer a discussion, you must have permissions to create discussions in the repository where you want to transfer the discussion. If you want to transfer a discussion to an organization, you must have permissions to create discussions in the source repository for the organization's discussions. You can only transfer discussions between repositories owned by the same user or organization account. You can't transfer a discussion from a private{% ifversion ghec or ghes %} or internal{% endif %} repository to a public repository. -{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. Na barra lateral direita, clique em {% octicon "arrow-right" aria-label="The right arrow icon" %} **Transferir discussão**. - !["Transferir discussão" na barra lateral direita da discussão](/assets/images/help/discussions/click-transfer-discussion.png) -1. Selecione o menu suspenso **Escolher um repositório** e clique no repositório para o qual deseja transferir a discussão. Se você quiser transferir uma discussão para uma organização, escolha o repositório de origem das discussões da organização. - ![Menu suspenso "Escolher um repositório", campo de pesquisa "Localizar um repositório" e repositório na lista](/assets/images/help/discussions/use-choose-a-repository-drop-down.png) -1. Clique em **Transferir discussão**. - ![Botão "Transferir discussão"](/assets/images/help/discussions/click-transfer-discussion-button.png) +{% data reusables.discussions.navigate-to-repo-or-org %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} **Transfer discussion**. + !["Transfer discussion" in right sidebar for discussion](/assets/images/help/discussions/click-transfer-discussion.png) +1. Select the **Choose a repository** drop-down, and click the repository you want to transfer the discussion to. If you want to transfer a discussion to an organization, choose the source repository for the organization's discussions. + !["Choose a repository" drop-down, "Find a repository" search field, and repository in list](/assets/images/help/discussions/use-choose-a-repository-drop-down.png) +1. Click **Transfer discussion**. + !["Transfer discussion" button](/assets/images/help/discussions/click-transfer-discussion-button.png) -## Excluir uma discussão +## Deleting a discussion -{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. Na barra lateral direita, clique em {% octicon "trash" aria-label="The trash arrow icon" %} **Excluir discussão**. - !["Excluir discussão" na barra lateral direita da discussão](/assets/images/help/discussions/click-delete-discussion.png) -1. Leia o aviso e clique em **Excluir esta discussão**. - ![Botão "Excluir esta discussão" abaixo do aviso na caixa de diálogo modal](/assets/images/help/discussions/click-delete-this-discussion-button.png) +{% data reusables.discussions.navigate-to-repo-or-org %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**. + !["Delete discussion" in right sidebar for discussion](/assets/images/help/discussions/click-delete-discussion.png) +1. Read the warning, then click **Delete this discussion**. + !["Delete this discussion" button beneath warning in modal](/assets/images/help/discussions/click-delete-this-discussion-button.png) -## Converter problemas com base em etiquetas +## Converting issues based on labels -Você pode converter todos as etiquetas com a mesma etiqueta para discussões em massa. Os problemas futuros com essa etiqueta também serão automaticamente convertidos em discussão e categoria que você configurar. +You can convert all issues with the same label to discussions in bulk. Future issues with this label will also automatically convert to the discussion and category you configure. -1. No {% data variables.product.product_location %}, navegue até a página principal do repositório ou, para discussões da organização, o repositório de origem. -{% data reusables.repositories.sidebar-issues %} {% data reusables.project-management.labels %} -1. Ao lado do rótulo que deseja converter em problemas, clique em **Converter problemas**. -1. Selecione o menu suspenso **Escolher uma categoria** e clique em uma categoria para ver a discussão. -1. Clique em **Entendi. Converter este problema em uma discussão**. +1. On {% data variables.location.product_location %}, navigate to the main page of the repository or, for organization discussions, the source repository. +{% data reusables.repositories.sidebar-issues %} +{% data reusables.project-management.labels %} +1. Next to the label you want to convert to issues, click **Convert issues**. +1. Select the **Choose a category** drop-down menu, and click a category for your discussion. +1. Click **I understand, convert this issue to a discussion**. diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md index 443a03b162..4272e08f49 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md @@ -1,37 +1,31 @@ --- -title: Sobre o uso de MakeCode Arcade com GitHub Classroom +title: About using MakeCode Arcade with GitHub Classroom shortTitle: About using MakeCode Arcade -intro: 'Você pode configurar o MakeCode Arcade como o IDE online para atribuições em {% data variables.product.prodname_classroom %}.' +intro: 'You can configure MakeCode Arcade as the online IDE for assignments in {% data variables.product.prodname_classroom %}.' versions: fpt: '*' redirect_from: - /education/manage-coursework-with-github-classroom/student-experience-makecode - /education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom -ms.openlocfilehash: f4786f67c7a9d0444e92d3c5560f4d86b6a0af7d -ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/12/2022 -ms.locfileid: '145095692' --- -## Sobre o MakeCode Arcade +## About MakeCode Arcade -O MakeCode Arcade é um ambiente de desenvolvimento integrado on-line (IDE) para o desenvolvimento de jogos retrô arcade que usa a programação de blocos de arrastar e soltar e JavaScript. Os alunos podem escrever, editar, executar, testar e depurar códigos em um navegador com o MakeCode Arcade. Para obter mais informações sobre os IDEs e o {% data variables.product.prodname_classroom %}, confira "[Integrar o {% data variables.product.prodname_classroom %} a um IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)". +MakeCode Arcade is an online integrated development environment (IDE) for developing retro arcade games using drag-and-drop block programming and JavaScript. Students can write, edit, run, test, and debug code in a browser with MakeCode Arcade. For more information about IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)." {% data reusables.classroom.readme-contains-button-for-online-ide %} -A primeira vez que o aluno clica no botão para acessar o MakeCode Arcade, o aluno deve entrar no MakeCode Arcade 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 tarefas, totalmente configurado no MakeCode Arcade. +The first time the student clicks the button to visit MakeCode Arcade, the student must sign into MakeCode Arcade 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 MakeCode Arcade. -Para obter mais informações sobre como trabalhar no MakeCode Arcade, confira o [Tour pelo MakeCode Arcade](https://arcade.makecode.com/ide-tour) e a [documentação](https://arcade.makecode.com/docs) no site do MakeCode Arcade. +For more information about working on MakeCode Arcade, see the [MakeCode Arcade Tour](https://arcade.makecode.com/ide-tour) and [documentation](https://arcade.makecode.com/docs) on the MakeCode Arcade website. -O MakeCode Arcade não é compatível com a edição de multijogador para atividades em grupo. Em vez disso, os alunos podem colaborar com os recursos do Git e de {% data variables.product.product_name %} como branches e pull requests. +MakeCode Arcade does not support multiplayer-editing for group assignments. Instead, students can collaborate with Git and {% data variables.product.product_name %} features like branches and pull requests. -## Sobre o envio das atividades com o MakeCode Arcade +## About submission of assignments with MakeCode Arcade -Por padrão, o MakeCode Arcade está configurado para realizar push no repositório de atividade em {% data variables.product.product_location %}. Após fazer progresso em uma atividade com MakeCode Arcade, os alunos devem fazer push das alterações para {% data variables.product.product_location %} usando o botão {% octicon "mark-github" aria-label="The GitHub mark" %}{% octicon "arrow-up" aria-label="The up arrow icon" %} na parte inferior da tela. +By default, MakeCode Arcade is configured to push to the assignment repository on {% data variables.location.product_location %}. After making progress on an assignment with MakeCode Arcade, students should push changes to {% data variables.location.product_location %} using the {% octicon "mark-github" aria-label="The GitHub mark" %}{% octicon "arrow-up" aria-label="The up arrow icon" %} button at the bottom of the screen. -![Funcionalidade de controle de versão MakeCode Arcade](/assets/images/help/classroom/ide-makecode-arcade-version-control-button.png) +![MakeCode Arcade version control functionality](/assets/images/help/classroom/ide-makecode-arcade-version-control-button.png) -## Leitura adicional +## Further reading -- "[Sobre os arquivos LEIAME](/github/creating-cloning-and-archiving-repositories/about-readmes)" +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md index 1e7a9849c8..7e93c63392 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md @@ -1,36 +1,30 @@ --- -title: Visualizar resultados da avaliação automática -intro: Você pode ver os resultados da avaliação automática dentro do repositório para sua atividade. +title: View autograding results +intro: You can see results from autograding within the repository for your assignment. versions: fpt: '*' redirect_from: - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-students - /education/manage-coursework-with-github-classroom/view-autograding-results -ms.openlocfilehash: ea4de9b0122e39f5ecb4d960d4f0ee8c94ba2ee5 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145095686' --- -## Sobre a avaliação automática +## About autograding -Seu professor pode configurar testes que verificam automaticamente seu trabalho quando você faz push para um repositório de atividades em {% data variables.product.product_location %}. +Your teacher can configure tests that automatically check your work when you push to an assignment repository on {% data variables.location.product_location %}. -Se você é um aluno e seu instrutor configurou a avaliação automática para sua atribuição em {% data variables.product.prodname_classroom %}, você encontrará os resultados dos testes de avaliação automática no repositório da atividade. Se todos os testes tiverem êxito para um commit, você verá um sinal verde. Se qualquer teste falhar em um commit, você verá um X vermelho. Você pode ver os registros detalhados clicando na marca verde ou X vermelho. +If you're a student and your instructor has configured autograding for your assignment in {% data variables.product.prodname_classroom %}, you'll find autograding test results throughout your assignment repository. If all tests succeed for a commit, you'll see a green checkmark. If any tests fail for a commit, you'll see a red X. You can see detailed logs by clicking the green checkmark or red X. -## Visualizar resultados de avaliação automática para um repositório de atividade +## Viewing autograding results for an assignment repository -{% data variables.product.prodname_classroom %} usa {% data variables.product.prodname_actions %} para executar testes de avaliação automática. Para obter mais informações sobre como ver os logs para um teste de avaliação automática, confira "[Como usar os logs de execução de fluxo de trabalho](/actions/managing-workflow-runs/using-workflow-run-logs#viewing-logs-to-diagnose-failures)". +{% data variables.product.prodname_classroom %} uses {% data variables.product.prodname_actions %} to run autograding tests. For more information about viewing the logs for an autograding test, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs#viewing-logs-to-diagnose-failures)." -A guia **Ações** mostra o histórico completo das execuções de teste. +The **Actions** tab shows the full history of test runs. -![Guia "Ações" com "Todos os fluxos de trabalho" selecionado](/assets/images/help/classroom/autograding-actions-tab.png) +!["Actions" tab with "All workflows" selected](/assets/images/help/classroom/autograding-actions-tab.png) -Você pode clicar em uma execução de teste específico para revisar o resultado do registro, como erros de compilação e falhas de teste. +You can click a specific test run to review log output, like compilation errors and test failures. -![Os logs dos resultados do teste do "Fluxo de trabalho de avaliação automática do {% data variables.product.prodname_classroom %}" no {% data variables.product.prodname_actions %} ](/assets/images/help/classroom/autograding-actions-logs.png) +![The "{% data variables.product.prodname_classroom %} Autograding Workflow" test results logs in {% data variables.product.prodname_actions %} ](/assets/images/help/classroom/autograding-actions-logs.png) -## Leitura adicional +## Further reading -- "[Sobre as verificações de status](/github/collaborating-with-issues-and-pull-requests/about-status-checks)" +- "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)" diff --git a/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md index 463ad45f8b..1963647dc6 100644 --- a/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md +++ b/translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md @@ -29,7 +29,7 @@ With the {% data variables.product.prodname_dotcom %} for {% data variables.prod ## Project management tools -You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party project management tools, such as Jira. +You can integrate your personal or organization account on {% data variables.location.product_location %} with third-party project management tools, such as Jira. ### Jira Cloud and {% data variables.product.product_name %}.com integration @@ -37,7 +37,7 @@ You can integrate Jira Cloud with your personal or organization account to scan ## Team communication tools -You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party team communication tools, such as Slack or Microsoft Teams. +You can integrate your personal or organization account on {% data variables.location.product_location %} with third-party team communication tools, such as Slack or Microsoft Teams. ### Slack and {% data variables.product.product_name %} integration diff --git a/translations/pt-BR/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/pt-BR/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md index 2d673e4f08..d46262cbb0 100644 --- a/translations/pt-BR/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md +++ b/translations/pt-BR/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md @@ -1,6 +1,6 @@ --- -title: Encontrando maneiras de contribuir com o código aberto no GitHub -intro: 'Você pode encontrar maneiras de contribuir para projetos de código aberto em {% data variables.product.product_location %} que são relevantes para você.' +title: Finding ways to contribute to open source on GitHub +intro: 'You can find ways to contribute to open source projects on {% data variables.location.product_location %} that are relevant to you.' permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}' redirect_from: - /articles/where-can-i-find-open-source-projects-to-work-on @@ -17,46 +17,40 @@ versions: topics: - Open Source shortTitle: Contribute to open source -ms.openlocfilehash: 434927bb3fd1f6816cf76b82a949a4b3369acba9 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145095668' --- -## Descobrir projetos relevantes +## Discovering relevant projects -Se houver um tópico específico de seu interesse, acesse `github.com/topics/`. Por exemplo, se você estiver interessado em machine learning, encontre projetos relevantes e bons primeiros problemas acessando https://github.com/topics/machine-learning. Navegue por tópicos populares acessando [Tópicos](https://github.com/topics). Você também pode procurar repositórios que correspondam a um tópico do seu interesse. Para obter mais informações, confira "[Pesquisa em repositórios](/search-github/searching-on-github/searching-for-repositories#search-by-topic)". +If there's a particular topic that interests you, visit `github.com/topics/`. For example, if you are interested in machine learning, you can find relevant projects and good first issues by visiting https://github.com/topics/machine-learning. You can browse popular topics by visiting [Topics](https://github.com/topics). You can also search for repositories that match a topic you're interested in. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)." -Se você estiver ativo no {% data variables.product.product_location %}, poderá encontrar recomendações personalizadas para projetos e bons primeiros problemas com base nas suas contribuições passadas, na estrelas e em outras atividades em [Explorar](https://github.com/explore). Você também pode se inscrever no boletim informativo Explorar para receber e-mails sobre oportunidades de contribuir para {% data variables.product.product_name %} com base em seus interesses. Para se inscrever, confira [Boletim informativo por email Explorar](https://github.com/explore/subscribe). +If you've been active on {% data variables.location.product_location %}, you can find personalized recommendations for projects and good first issues based on your past contributions, stars, and other activities in [Explore](https://github.com/explore). You can also sign up for the Explore newsletter to receive emails about opportunities to contribute to {% data variables.product.product_name %} based on your interests. To sign up, see [Explore email newsletter](https://github.com/explore/subscribe). -Acompanhe as atividades recentes dos repositórios que você acompanha, bem como das pessoas e organizações que você segue, com seu painel pessoal. Para obter mais informações, confira "[Sobre seu painel pessoal](/articles/about-your-personal-dashboard)". +Keep up with recent activity from repositories you watch, as well as people and organizations you follow, with your personal dashboard. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)." {% data reusables.support.ask-and-answer-forum %} -## Encontrando bons problemas iniciais +## Finding good first issues -Se você já souber em qual projeto deseja trabalhar, encontre problemas para iniciantes nesse repositório acessando `github.com///contribute`. Por exemplo, você pode encontrar maneiras de fazer sua primeira contribuição com `electron/electron` em https://github.com/electron/electron/contribute. +If you already know what project you want to work on, you can find beginner-friendly issues in that repository by visiting `github.com///contribute`. For an example, you can find ways to make your first contribution to `electron/electron` at https://github.com/electron/electron/contribute. -## Abrir um problema +## Opening an issue -Se você encontrar um erro em um projeto de código aberto, verifique se o erro já foi informado. Se o erro não foi informado, você pode abrir um problema para relatar o erro de acordo com as diretrizes de contribuição do projeto. +If you encounter a bug in an open source project, check if the bug has already been reported. If the bug has not been reported, you can open an issue to report the bug according to the project's contribution guidelines. -## Validando um problema ou pull request +## Validating an issue or pull request -Existem várias maneiras de contribuir para projetos de código aberto. +There are a variety of ways that you can contribute to open source projects. -### Reproduzindo um erro relatado -Você pode contribuir para um projeto de código aberto validando um problema ou adicionando um contexto adicional a um problema existente. +### Reproducing a reported bug +You can contribute to an open source project by validating an issue or adding additional context to an existing issue. -### Testando um pull request -Você pode contribuir para um projeto de código aberto, fazendo o merge de um pull request na sua cópia local do projeto e testando as alterações. Adicione o resultado do seu teste em um comentário no pull request. +### Testing a pull request +You can contribute to an open source project by merging a pull request into your local copy of the project and testing the changes. Add the outcome of your testing in a comment on the pull request. -### Atualizando problemas -Você pode contribuir para um projeto de código aberto, incluindo informações adicionais para problemas existentes. +### Updating issues +You can contribute to an open source project by adding additional information to existing issues. -## Leitura adicional +## Further reading -- "[Como classificar seu repositório com tópicos](/articles/classifying-your-repository-with-topics)" -- "[Sobre o painel da sua organização](/articles/about-your-organization-dashboard)" +- "[Classifying your repository with topics](/articles/classifying-your-repository-with-topics)" +- "[About your organization dashboard](/articles/about-your-organization-dashboard)" diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/about-remote-repositories.md b/translations/pt-BR/content/get-started/getting-started-with-git/about-remote-repositories.md index fc8202a3dd..9f811b3086 100644 --- a/translations/pt-BR/content/get-started/getting-started-with-git/about-remote-repositories.md +++ b/translations/pt-BR/content/get-started/getting-started-with-git/about-remote-repositories.md @@ -1,5 +1,5 @@ --- -title: Sobre repositórios remote +title: About remote repositories redirect_from: - /articles/working-when-github-goes-down - /articles/sharing-repositories-without-github @@ -10,91 +10,85 @@ redirect_from: - /github/using-git/about-remote-repositories - /github/getting-started-with-github/about-remote-repositories - /github/getting-started-with-github/getting-started-with-git/about-remote-repositories -intro: 'A abordagem colaborativa do GitHub para o desenvolvimento depende da publicação de commits do seu repositório local para {% data variables.product.product_name %} para que outras pessoas visualizem, façam buscas e atualizações.' +intro: 'GitHub''s collaborative approach to development depends on publishing commits from your local repository to {% data variables.product.product_name %} for other people to view, fetch, and update.' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' -ms.openlocfilehash: 3b328831e09b62dce320ce2c230151e15d1b430b -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145093816' --- -## Sobre repositórios remote +## About remote repositories -Uma URL remota é outra forma de o Git dizer "o lugar onde seu código é armazenado". A URL poderia ser seu repositório no GitHub, ou a bifurcação de outro usuário, ou até mesmo em um servidor totalmente diferente. +A remote URL is Git's fancy way of saying "the place where your code is stored." That URL could be your repository on GitHub, or another user's fork, or even on a completely different server. -Você pode fazer push apenas de dois tipos de endereço URL: +You can only push to two types of URL addresses: -* Uma URL HTTPS como `https://{% data variables.command_line.backticks %}/user/repo.git` -* Uma URL SSH como `git@{% data variables.command_line.backticks %}:user/repo.git` +* An HTTPS URL like `https://{% data variables.command_line.backticks %}/user/repo.git` +* An SSH URL, like `git@{% data variables.command_line.backticks %}:user/repo.git` -O Git associa uma URL remota a um nome, e o repositório remoto padrão geralmente é chamado `origin`. +Git associates a remote URL with a name, and your default remote is usually called `origin`. -## Criar repositórios remotos +## Creating remote repositories -Use o comando `git remote add` para corresponder uma URL remota com um nome. -Por exemplo, você digitaria o seguinte na linha de comando: +You can use the `git remote add` command to match a remote URL with a name. +For example, you'd type the following in the command line: ```shell -git remote add origin <REMOTE_URL> +git remote add origin <REMOTE_URL> ``` -Isso associa o nome `origin` à `REMOTE_URL`. +This associates the name `origin` with the `REMOTE_URL`. -Use o comando `git remote set-url` para [alterar a URL de um repositório remoto](/github/getting-started-with-github/managing-remote-repositories). +You can use the command `git remote set-url` to [change a remote's URL](/github/getting-started-with-github/managing-remote-repositories). -## Escolher uma URL para o seu repositório remoto +## Choosing a URL for your remote repository -Existem várias maneiras de clonar repositórios disponíveis no {% data variables.product.product_location %}. +There are several ways to clone repositories available on {% data variables.location.product_location %}. -Quando você visualiza um repositório conectado à sua conta, as URLs que podem ser usadas para clonar o projeto no computador ficam disponíveis abaixo dos detalhes do repositório. +When you view a repository while signed in to your account, the URLs you can use to clone the project onto your computer are available below the repository details. -Para obter informações sobre como definir ou alterar a URL remota, confira "[Como gerenciar repositórios remotos](/github/getting-started-with-github/managing-remote-repositories)". +For information on setting or changing your remote URL, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." -## Clonando com as URLs de HTTPS +## Cloning with HTTPS URLs -As URLs de clone `https://` estão disponíveis em todos os repositórios, independentemente da visibilidade. As URLs de clone `https://` funcionam mesmo que você esteja protegido por um firewall ou um proxy. +The `https://` clone URLs are available on all repositories, regardless of visibility. `https://` clone URLs work even if you are behind a firewall or proxy. -Quando você usar `git clone`, `git fetch`, `git pull` ou `git push` em um repositório remoto usando URLs HTTPS na linha de comando, o Git solicitará seu nome de usuário e sua senha do {% data variables.product.product_name %}. {% data reusables.user-settings.password-authentication-deprecation %} +When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using HTTPS URLs on the command line, Git will ask for your {% data variables.product.product_name %} username and password. {% data reusables.user-settings.password-authentication-deprecation %} {% data reusables.command_line.provide-an-access-token %} {% tip %} -**Dicas**: -- Você pode usar um auxiliar de credenciais para que o Git se lembre de suas credenciais de {% data variables.product.prodname_dotcom %} toda vez que falar com {% data variables.product.prodname_dotcom %}. Para obter mais informações, confira "[Como armazenar em cache suas credenciais do {% data variables.product.prodname_dotcom %} no Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)". -- Para clonar um repositório sem se autenticar no {% data variables.product.product_name %} na linha de comando, use o {% data variables.product.prodname_desktop %} para a clonagem. Para obter mais informações, confira "[Como clonar um repositório do {% data variables.product.prodname_dotcom %} no {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)". +**Tips**: +- You can use a credential helper so Git will remember your {% data variables.product.prodname_dotcom %} credentials every time it talks to {% data variables.product.prodname_dotcom %}. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)." +- To clone a repository without authenticating to {% data variables.product.product_name %} on the command line, you can use {% data variables.product.prodname_desktop %} to clone instead. For more information, see "[Cloning a repository from {% data variables.product.prodname_dotcom %} to {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)." {% endtip %} - {% ifversion fpt or ghec %}Se você prefere usar o SSH mas não consegue se conectar pela porta 22, use o SSH pela porta HTTPS. Para obter mais informações, confira "[Como usar o SSH na porta HTTPS](/github/authenticating-to-github/using-ssh-over-the-https-port)".{% endif %} + {% ifversion fpt or ghec %}If you'd rather use SSH but cannot connect over port 22, you might be able to use SSH over the HTTPS port. For more information, see "[Using SSH over the HTTPS port](/github/authenticating-to-github/using-ssh-over-the-https-port)."{% endif %} -## Clonar com URLs de SSH +## Cloning with SSH URLs -As URLs de SSH fornecem acesso a um repositório do Git via SSH, um protocolo seguro. Para usar estas URLs, gere um par de chaves SSH no computador e adicione a chave **pública** à sua conta do {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Para obter mais informações, confira "[Como se conectar ao {% data variables.product.prodname_dotcom %} com o SSH](/github/authenticating-to-github/connecting-to-github-with-ssh)". +SSH URLs provide access to a Git repository via SSH, a secure protocol. To use these URLs, you must generate an SSH keypair on your computer and add the **public** key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For more information, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/github/authenticating-to-github/connecting-to-github-with-ssh)." -Quando você usar `git clone`, `git fetch`, `git pull`ou `git push` em um repositório remoto usando URLs SSH, precisará inserir uma senha e fornecer sua frase secreta de chave SSH. Para obter mais informações, confira "[Como trabalhar com frases secretas de chave SSH](/github/authenticating-to-github/working-with-ssh-key-passphrases)". +When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using SSH URLs, you'll be prompted for a password and must provide your SSH key passphrase. For more information, see "[Working with SSH key passphrases](/github/authenticating-to-github/working-with-ssh-key-passphrases)." -{% ifversion fpt or ghec %}Se você estiver acessando uma organização que usa o SSO (logon único) do SAML, precisará autorizar sua chave SSH a acessar a organização antes de realizar a autenticação. Para obter mais informações, confira "[Sobre a autenticação com o logon único do SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" e "[Como autorizar uma chave SSH para uso com o logon único do SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" na documentação do {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}{% endif %} +{% ifversion fpt or ghec %}If you are accessing an organization that uses SAML single sign-on (SSO), you must authorize your SSH key to access the organization before you authenticate. For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} {% tip %} -**Dica**: use uma URL com SSH para clonar um repositório no computador ou como uma forma segura de implantar seu código em servidores de produção. Você também pode usar o encaminhamento de agente SSH com o seu script de implantação para evitar o gerenciamento de chaves no servidor. Para obter mais informações, confira "[Como usar o encaminhamento do agente SSH](/developers/overview/using-ssh-agent-forwarding)". +**Tip**: You can use an SSH URL to clone a repository to your computer, or as a secure way of deploying your code to production servers. You can also use SSH agent forwarding with your deploy script to avoid managing keys on the server. For more information, see "[Using SSH Agent Forwarding](/developers/overview/using-ssh-agent-forwarding)." {% endtip %} -## Clonar com {% data variables.product.prodname_cli %} +## Cloning with {% data variables.product.prodname_cli %} -Você também pode instalar o {% data variables.product.prodname_cli %} para usar os fluxos de trabalho do {% data variables.product.product_name %} no seu terminal. Para obter mais informações, confira "[Sobre a {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)". +You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} workflows in your terminal. For more information, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." {% ifversion not ghae %} -## Clonar com o Subversion +## Cloning with Subversion -Use também um cliente do [Subversion](https://subversion.apache.org/) para acessar qualquer repositório no {% data variables.product.prodname_dotcom %}. O Subversion oferece um conjunto de recursos diferente do Git. Para obter mais informações, confira "[Quais são as diferenças entre o Subversion e o Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)" +You can also use a [Subversion](https://subversion.apache.org/) client to access any repository on {% data variables.product.prodname_dotcom %}. Subversion offers a different feature set than Git. For more information, see "[What are the differences between Subversion and Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)" -Você também pode acessar repositórios no {% data variables.product.prodname_dotcom %} a partir de clientes do Subversion. Para obter mais informações, confira "[Suporte para clientes do Subversion](/github/importing-your-projects-to-github/support-for-subversion-clients)". +You can also access repositories on {% data variables.product.prodname_dotcom %} from Subversion clients. For more information, see "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients)." {% endif %} diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md b/translations/pt-BR/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md index ebd7137835..a32b554c10 100644 --- a/translations/pt-BR/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md +++ b/translations/pt-BR/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md @@ -1,5 +1,5 @@ --- -title: Armazenar suas credenciais do GitHub no Git +title: Caching your GitHub credentials in Git redirect_from: - /firewalls-and-proxies - /articles/caching-your-github-password-in-git @@ -7,82 +7,77 @@ redirect_from: - /github/using-git/caching-your-github-credentials-in-git - /github/getting-started-with-github/caching-your-github-credentials-in-git - /github/getting-started-with-github/getting-started-with-git/caching-your-github-credentials-in-git -intro: 'Se você estiver [clonando repositórios do {% data variables.product.product_name %} usando HTTPS](/github/getting-started-with-github/about-remote-repositories), recomendamos você usar o {% data variables.product.prodname_cli %} ou o Git Credential Manager (GCM) para lembrar suas credenciais.' +intro: 'If you''re [cloning {% data variables.product.product_name %} repositories using HTTPS](/github/getting-started-with-github/about-remote-repositories), we recommend you use {% data variables.product.prodname_cli %} or Git Credential Manager (GCM) to remember your credentials.' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' shortTitle: Caching credentials -ms.openlocfilehash: 203eed949beb3c1ada9c4c099cbaf214aac0c4f7 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145093815' --- + {% tip %} -**Dica:** se você clonar repositórios do {% data variables.product.product_name %} usando SSH, poderá efetuar a autenticação usando uma chave SSH em vez de usar outras credenciais. Para obter informações sobre como configurar uma conexão SSH, confira "[Como gerar uma chave SSH](/articles/generating-an-ssh-key)". +**Tip:** If you clone {% data variables.product.product_name %} repositories using SSH, then you can authenticate using an SSH key instead of using other credentials. For information about setting up an SSH connection, see "[Generating an SSH Key](/articles/generating-an-ssh-key)." {% endtip %} ## {% data variables.product.prodname_cli %} -O {% data variables.product.prodname_cli %} armazenará automaticamente suas credenciais do Git para você escolher `HTTPS` como protocolo preferido para operações Git e responder "sim" ao prompt que perguntará se você gostaria de efetuar a autenticação no Git com a suas credenciais do {% data variables.product.product_name %}. +{% data variables.product.prodname_cli %} will automatically store your Git credentials for you when you choose `HTTPS` as your preferred protocol for Git operations and answer "yes" to the prompt asking if you would like to authenticate to Git with your {% data variables.product.product_name %} credentials. -1. [Instale](https://github.com/cli/cli#installation) a {% data variables.product.prodname_cli %} no macOS, no Windows ou no Linux. -2. Na linha de comando, insira `gh auth login` e siga os prompts. - - Quando solicitado o protocolo preferido para operações Git, selecione `HTTPS`. - - Quando perguntado se você deseja se autenticar no Git com suas credenciais do {% data variables.product.product_name %}, insira `Y`. +1. [Install](https://github.com/cli/cli#installation) {% data variables.product.prodname_cli %} on macOS, Windows, or Linux. +2. In the command line, enter `gh auth login`, then follow the prompts. + - When prompted for your preferred protocol for Git operations, select `HTTPS`. + - When asked if you would like to authenticate to Git with your {% data variables.product.product_name %} credentials, enter `Y`. -Para obter mais informações sobre como se autenticar com a {% data variables.product.prodname_cli %}, confira [`gh auth login`](https://cli.github.com/manual/gh_auth_login). +For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). -## Gerenciador de credenciais do Git +## Git Credential Manager -O [GCM](https://github.com/GitCredentialManager/git-credential-manager) (Gerenciador de Credenciais do Git) é outra maneira de armazenar suas credenciais com segurança e conectar-se ao GitHub via HTTPS. Com o GCM, você não precisa [criar nem armazenar manualmente um PAT](/github/authenticating-to-github/creating-a-personal-access-token), pois o GCM gerencia a autenticação em seu nome, incluindo a 2FA (autenticação de dois fatores). +[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager) (GCM) is another way to store your credentials securely and connect to GitHub over HTTPS. With GCM, you don't have to manually [create and store a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token), as GCM manages authentication on your behalf, including 2FA (two-factor authentication). {% mac %} -1. Instale o Git usando o [Homebrew](https://brew.sh/): +1. Install Git using [Homebrew](https://brew.sh/): ```shell $ brew install git ``` -2. Instale GCM usando o Homebrew: +2. Install GCM using Homebrew: ```shell $ brew tap microsoft/git $ brew install --cask git-credential-manager-core ``` - No MacOS, você não precisa executar a `git config` porque o GCM configura automaticamente o Git para você. + For MacOS, you don't need to run `git config` because GCM automatically configures Git for you. {% data reusables.gcm-core.next-time-you-clone %} -Após a autenticação ser concluída com sucesso, suas credenciais serão armazenadas no keychain do macOS e serão usadas toda vez que você clonar uma URL de HTTPS. O Git não exigirá que você digite suas credenciais na linha de comando novamente, a menos que você altere suas credenciais. +Once you've authenticated successfully, your credentials are stored in the macOS keychain and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials. {% endmac %} {% windows %} -1. Instale o Git para o Windows, que inclui GCM. Para obter mais informações, confira "[Git para versões Windows](https://github.com/git-for-windows/git/releases/latest)" nas respectivas [página de versões](https://github.com/git-for-windows/git/releases/latest). +1. Install Git for Windows, which includes GCM. For more information, see "[Git for Windows releases](https://github.com/git-for-windows/git/releases/latest)" from its [releases page](https://github.com/git-for-windows/git/releases/latest). -Recomenda-se instalar sempre a versão mais recente. No mínimo, instale a versão 2.29 ou superior, que é a primeira versão que oferece suporte do OAuth para o GitHub. +We recommend always installing the latest version. At a minimum, install version 2.29 or higher, which is the first version offering OAuth support for GitHub. {% data reusables.gcm-core.next-time-you-clone %} -Depois de efetuar a autenticação com sucesso, as suas credenciais serão armazenadas no gerenciador de credenciais do Windows e serão usadas toda vez que você clonar uma URL de HTTPS. O Git não exigirá que você digite suas credenciais na linha de comando novamente, a menos que você altere suas credenciais. +Once you've authenticated successfully, your credentials are stored in the Windows credential manager and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials.
{% warning %} -**Aviso:** as versões mais antigas do Git para Windows vieram com o Administrador de Credenciais do Git para Windows. Este produto antigo não é mais compatível e não pode se conectar ao GitHub via OAuth. Recomendamos que você atualize para [a versão mais recente do Git para Windows](https://github.com/git-for-windows/git/releases/latest). +**Warning:** Older versions of Git for Windows came with Git Credential Manager for Windows. This older product is no longer supported and cannot connect to GitHub via OAuth. We recommend you upgrade to [the latest version of Git for Windows](https://github.com/git-for-windows/git/releases/latest). {% endwarning %} {% warning %} -**Aviso:** se você armazenou em cache credenciais incorretas ou desatualizadas no Gerenciador de Credencial para Windows, o Git não terá acesso ao {% data variables.product.product_name %}. Para redefinir as suas credenciais armazenadas em cache para que o Git peça para inserir suas credenciais, acesse o Gerenciador de Credenciais no Painel de Controle do Windows em Contas de Usuário > Gerenciador de Credenciais. Procure a entrada de {% data variables.product.product_name %} e exclua-a. +**Warning:** If you cached incorrect or outdated credentials in Credential Manager for Windows, Git will fail to access {% data variables.product.product_name %}. To reset your cached credentials so that Git prompts you to enter your credentials, access the Credential Manager in the Windows Control Panel under User Accounts > Credential Manager. Look for the {% data variables.product.product_name %} entry and delete it. {% endwarning %} @@ -90,22 +85,22 @@ Depois de efetuar a autenticação com sucesso, as suas credenciais serão armaz {% linux %} -Para Linux, instale o Git e o GCM e, em seguida, configure o Git para usar o GCM. +For Linux, install Git and GCM, then configure Git to use GCM. -1. Instale o Git a partir do sistema de pacotes da sua distribuição. As instruções vão variar dependendo da versão do Linux que você executar. +1. Install Git from your distro's packaging system. Instructions will vary depending on the flavor of Linux you run. -2. Install o GCM. Veja as [instruções no repositório do GCM](https://github.com/GitCredentialManager/git-credential-manager#linux-install-instructions), pois elas são diferentes, de acordo com a variante do Linux executada. +2. Install GCM. See the [instructions in the GCM repo](https://github.com/GitCredentialManager/git-credential-manager#linux-install-instructions), as they'll vary depending on the flavor of Linux you run. -3. Configurar o Git para usar o GCM. Há várias lojas de apoio que você pode escolher. Portanto, consulte a documentação de do GCM para concluir a sua configuração. Para obter mais informações, confira "[GCM Linux](https://aka.ms/gcmcore-linuxcredstores)". +3. Configure Git to use GCM. There are several backing stores that you may choose from, so see the GCM docs to complete your setup. For more information, see "[GCM Linux](https://aka.ms/gcmcore-linuxcredstores)." {% data reusables.gcm-core.next-time-you-clone %} -Depois de autenticado com sucesso, as suas credenciais serão armazenadas no seu sistema e serão usadas toda vez que você clonar uma URL de HTTPS. O Git não exigirá que você digite suas credenciais na linha de comando novamente, a menos que você altere suas credenciais. +Once you've authenticated successfully, your credentials are stored on your system and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials. -Para obter mais opções para armazenar suas credenciais no Linux, confira [Armazenamento de Credencial](https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage) no Pro Git. +For more options for storing your credentials on Linux, see [Credential Storage](https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage) in Pro Git. {% endlinux %}
-Para obter mais informações ou relatar problemas com o GCM, veja os documentos oficiais do GCM em "[Gerenciador de Credenciais do Git](https://github.com/GitCredentialManager/git-credential-manager)". +For more information or to report issues with GCM, see the official GCM docs at "[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager)." diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md b/translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md index 0603cc1f64..b10cb2025a 100644 --- a/translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md +++ b/translations/pt-BR/content/get-started/getting-started-with-git/managing-remote-repositories.md @@ -1,6 +1,6 @@ --- -title: Gerenciar repositórios remote -intro: 'Aprenda a trabalhar com seus repositórios locais no seu computador e repositórios remotos hospedados no {% data variables.product.product_name %}.' +title: Managing remote repositories +intro: 'Learn to work with your local repositories on your computer and remote repositories hosted on {% data variables.product.product_name %}.' redirect_from: - /categories/18/articles - /remotes @@ -24,221 +24,216 @@ versions: ghae: '*' ghec: '*' shortTitle: Manage remote repositories -ms.openlocfilehash: 413e1f8fca1991ea198e28daab9d8507668d4f29 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145126733' --- -## Adicionar um repositório remoto +## Adding a remote repository -Para adicionar um novo controle remoto, use o comando `git remote add` no terminal, no diretório em que o repositório está armazenado. +To add a new remote, use the `git remote add` command on the terminal, in the directory your repository is stored at. -O comando `git remote add` usa dois argumentos: -* Um nome de repositório remoto, por exemplo, `origin` -* Uma URL remota, por exemplo, `https://{% data variables.command_line.backticks %}/user/repo.git` +The `git remote add` command takes two arguments: +* A remote name, for example, `origin` +* A remote URL, for example, `https://{% data variables.command_line.backticks %}/user/repo.git` -Por exemplo: +For example: ```shell -$ git remote add origin https://{% data variables.command_line.codeblock %}/user/repo.git +$ git remote add origin https://{% data variables.command_line.codeblock %}/USER/REPO>.git # Set a new remote $ git remote -v # Verify new remote -> origin https://{% data variables.command_line.codeblock %}/user/repo.git (fetch) -> origin https://{% data variables.command_line.codeblock %}/user/repo.git (push) +> origin https://{% data variables.command_line.codeblock %}/USER/REPO.git (fetch) +> origin https://{% data variables.command_line.codeblock %}/USER/REPO.git (push) ``` -Para obter mais informações sobre qual URL usar, confira "[Sobre repositórios remotos](/github/getting-started-with-github/about-remote-repositories)". +For more information on which URL to use, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)." -### Solução de problemas: A origem remota já existe +### Troubleshooting: Remote origin already exists -Esse erro significa que você tentou adicionar um remoto com um nome que já existe no repositório local. +This error means you've tried to add a remote with a name that already exists in your local repository. ```shell $ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git > fatal: remote origin already exists. ``` -Para corrigir isso, você pode: -* Usar um nome diferente para o novo remoto -* Renomeie o repositório remoto existente antes de adicionar o novo repositório remoto. Para obter mais informações, confira "[Renomear um repositório remoto](#renaming-a-remote-repository)" abaixo. -* Exclua o repositório remoto existente antes de adicionar o novo repositório remoto. Para obter mais informações, confira "[Remover um repositório remoto](#removing-a-remote-repository)" abaixo. +To fix this, you can: +* Use a different name for the new remote. +* Rename the existing remote repository before you add the new remote. For more information, see "[Renaming a remote repository](#renaming-a-remote-repository)" below. +* Delete the existing remote repository before you add the new remote. For more information, see "[Removing a remote repository](#removing-a-remote-repository)" below. -## Alterar a URL de um repositório remoto +## Changing a remote repository's URL -O comando `git remote set-url` altera uma URL do repositório remoto existente. +The `git remote set-url` command changes an existing remote repository URL. {% tip %} -**Dica:** Para obter informações sobre a diferença entre URLs HTTPS e SSH, confira "[Sobre repositórios remotos](/github/getting-started-with-github/about-remote-repositories)". +**Tip:** For information on the difference between HTTPS and SSH URLs, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)." {% endtip %} -O comando `git remote set-url` usa dois argumentos: +The `git remote set-url` command takes two arguments: -* Um nome remote existente. Por exemplo, `origin` ou `upstream` são duas opções comuns. -* Uma nova URL para o remote. Por exemplo: - * Se estiver atualizando para usar HTTPS, a URL poderá ser parecida com esta: +* An existing remote name. For example, `origin` or `upstream` are two common choices. +* A new URL for the remote. For example: + * If you're updating to use HTTPS, your URL might look like: ```shell -https://{% data variables.command_line.backticks %}/USERNAME/REPOSITORY.git +https://{% data variables.command_line.backticks %}/USERNAME/REPOSITORY.git ``` - * Se estiver atualizando para usar SSH, a URL poderá ser parecida com esta: + * If you're updating to use SSH, your URL might look like: ```shell -git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git +git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git ``` -### Alternar URLs remotes de SSH para HTTPS +### Switching remote URLs from SSH to HTTPS {% data reusables.command_line.open_the_multi_os_terminal %} -2. Altere o diretório de trabalho atual para seu projeto local. -3. Liste seus remotes existentes para obter o nome do remote que deseja alterar. +2. Change the current working directory to your local project. +3. List your existing remotes in order to get the name of the remote you want to change. ```shell $ git remote -v - > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (fetch) - > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (push) + > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (fetch) + > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (push) ``` -4. Altere a URL do repositório remoto do SSH para HTTPS com o comando `git remote set-url`. +4. Change your remote's URL from SSH to HTTPS with the `git remote set-url` command. ```shell - $ git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git + $ git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git ``` -5. Verifique se o URL remote foi alterado. +5. Verify that the remote URL has changed. ```shell $ git remote -v # Verify new remote URL - > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (push) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (push) ``` -Na próxima vez que você usar `git fetch`, `git pull` ou `git push` para o repositório remoto, deverá fornecer seu nome de usuário e senha do GitHub. {% data reusables.user-settings.password-authentication-deprecation %} +The next time you `git fetch`, `git pull`, or `git push` to the remote repository, you'll be asked for your GitHub username and password. {% data reusables.user-settings.password-authentication-deprecation %} -Você pode [usar um auxiliar de credencial](/github/getting-started-with-github/caching-your-github-credentials-in-git) para que o Git se lembre do nome de usuário do GitHub e do token de acesso pessoal toda vez que ele se comunicar com o GitHub. +You can [use a credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git) so Git will remember your GitHub username and {% data variables.product.pat_generic %} every time it talks to GitHub. -### Mudar as URLs remotas de HTTPS para SSH +### Switching remote URLs from HTTPS to SSH {% data reusables.command_line.open_the_multi_os_terminal %} -2. Altere o diretório de trabalho atual para seu projeto local. -3. Liste seus remotes existentes para obter o nome do remote que deseja alterar. +2. Change the current working directory to your local project. +3. List your existing remotes in order to get the name of the remote you want to change. ```shell $ git remote -v - > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (push) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (push) ``` -4. Altere a URL do seu remoto de HTTPS para SSH com o comando `git remote set-url`. +4. Change your remote's URL from HTTPS to SSH with the `git remote set-url` command. ```shell - $ git remote set-url origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git + $ git remote set-url origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git ``` -5. Verifique se o URL remote foi alterado. +5. Verify that the remote URL has changed. ```shell $ git remote -v # Verify new remote URL - > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (fetch) - > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (push) + > origin git@{% data variables.command_line.codeblock %}: USERNAME/REPOSITORY.git (fetch) + > origin git@{% data variables.command_line.codeblock %}: USERNAME/REPOSITORY.git (push) ``` -### Solução de problemas: Não há tal '[name]' remoto ' +### Troubleshooting: No such remote '[name]' -Este erro informa que o remote que você tentou alterar não existe: +This error means that the remote you tried to change doesn't exist: ```shell $ git remote set-url sofake https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife > fatal: No such remote 'sofake' ``` -Verifique se você inseriu corretamente o nome do remote. +Check that you've correctly typed the remote name. -## Renomear um repositório remoto +## Renaming a remote repository -Use o comando `git remote rename` para renomear um remoto existente. +Use the `git remote rename` command to rename an existing remote. -O comando `git remote rename` usa dois argumentos: -* Um nome remoto existente, por exemplo, `origin` -* Um novo nome para o remoto, por exemplo, `destination` +The `git remote rename` command takes two arguments: +* An existing remote name, for example, `origin` +* A new name for the remote, for example, `destination` -## Exemplo +## Example -Esses exemplos pressupõem que você esteja [clonando usando HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), o que é recomendado. +These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended. ```shell $ git remote -v # View existing remotes -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) $ git remote rename origin destination # Change remote name from 'origin' to 'destination' $ git remote -v # Verify remote's new name -> destination https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) -> destination https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) +> destination https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) +> destination https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) ``` -### Solução de problemas: Não foi possível renomear a seção de configuração 'remote.[old name]' para 'remote.[new name]' +### Troubleshooting: Could not rename config section 'remote.[old name]' to 'remote.[new name]' -Este erro significa que o nome remoto antigo digitado não existe. +This error means that the old remote name you typed doesn't exist. -Você pode verificar quais remotos existem atualmente com o comando `git remote -v`: +You can check which remotes currently exist with the `git remote -v` command: ```shell $ git remote -v # View existing remotes -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) ``` -### Solução de problemas: Já existe um [new name] remoto +### Troubleshooting: Remote [new name] already exists -Esse erro informa que o nome de remote que você deseja usar já existe. Para resolver isso, use um nome remoto diferente ou renomeie o remoto original. +This error means that the remote name you want to use already exists. To solve this, either use a different remote name, or rename the original remote. -## Remover um repositório remoto +## Removing a remote repository -Use o comando `git remote rm` para remover uma URL remota do repositório. +Use the `git remote rm` command to remove a remote URL from your repository. -O comando `git remote rm` usa um argumento: -* Um nome de repositório remoto, por exemplo, `destination` +The `git remote rm` command takes one argument: +* A remote name, for example, `destination` -A remoção do URL remoto do repositório apenas desvincula os repositórios locais e remotos. Isso não exclui o repositório remoto. +Removing the remote URL from your repository only unlinks the local and remote repositories. It does not delete the remote repository. -## Exemplo +## Example -Esses exemplos pressupõem que você esteja [clonando usando HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), o que é recomendado. +These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended. ```shell $ git remote -v # View current remotes -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) -> destination https://{% data variables.command_line.codeblock %}/FORKER/REPOSITORY.git (fetch) -> destination https://{% data variables.command_line.codeblock %}/FORKER/REPOSITORY.git (push) +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) +> destination https://{% data variables.command_line.codeblock %}/FORKER/REPOSITORY.git (fetch) +> destination https://{% data variables.command_line.codeblock %}/FORKER/REPOSITORY.git (push) $ git remote rm destination # Remove remote $ git remote -v # Verify it's gone -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) +> origin https://{% data variables.command_line.codeblock %}/ OWNER/REPOSITORY.git (fetch) +> origin https://{% data variables.command_line.codeblock %}/ OWNER/REPOSITORY.git (push) ``` {% warning %} -**Observação**: `git remote rm` não exclui o repositório remoto do servidor. Ele simplesmente remove o remoto e suas referências do repositório local. +**Note**: `git remote rm` does not delete the remote repository from the server. It simply +removes the remote and its references from your local repository. {% endwarning %} -### Solução de problemas: Não foi possível remover a seção 'remote.[name]' +### Troubleshooting: Could not remove config section 'remote.[name]' -Esse erro informa que o remote que você tentou excluir não existe: +This error means that the remote you tried to delete doesn't exist: ```shell $ git remote rm sofake > error: Could not remove config section 'remote.sofake' ``` -Verifique se você inseriu corretamente o nome do remote. +Check that you've correctly typed the remote name. -## Leitura adicional +## Further reading -- "[Como trabalhar com repositórios remotos" do livro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) +- "[Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md b/translations/pt-BR/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md index ce6afd34b9..507b7c8f52 100644 --- a/translations/pt-BR/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md +++ b/translations/pt-BR/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md @@ -1,6 +1,6 @@ --- -title: Atualizar credenciais da keychain OSX -intro: 'Você precisará atualizar suas credenciais salvas no auxiliar `git-credential-osxkeychain` se alterar seu{% ifversion not ghae %} nome de usuário, senha ou{% endif %} token de acesso pessoal no {% data variables.product.product_name %}.' +title: Updating credentials from the macOS Keychain +intro: 'You''ll need to update your saved credentials in the `git-credential-osxkeychain` helper if you change your{% ifversion not ghae %} username, password, or{% endif %} {% data variables.product.pat_generic %} on {% data variables.product.product_name %}.' redirect_from: - /articles/updating-credentials-from-the-osx-keychain - /github/using-git/updating-credentials-from-the-osx-keychain @@ -13,44 +13,38 @@ versions: ghae: '*' ghec: '*' shortTitle: macOS Keychain credentials -ms.openlocfilehash: ce2e225bcff1aca0c034e564fe3233e5f9cb68d2 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145126726' --- {% tip %} -**Observação:** a atualização de credenciais por meio do conjunto de chaves do macOS só se aplica aos usuários que configuraram manualmente um PAT usando o auxiliar `osxkeychain` interno do macOS. +**Note:** Updating credentials from the macOS Keychain only applies to users who manually configured a {% data variables.product.pat_generic %} using the `osxkeychain` helper that is built-in to macOS. -Recomendamos [configurar o SSH](/articles/generating-an-ssh-key) ou atualizar para o [GCM](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) (Gerenciador de Credenciais do Git). O GCM pode gerenciar a autenticação em seu nome (sem PATs manuais), incluindo a 2FA (autenticação de dois fatores). +We recommend you either [configure SSH](/articles/generating-an-ssh-key) or upgrade to the [Git Credential Manager](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) (GCM) instead. GCM can manage authentication on your behalf (no more manual {% data variables.product.pat_generic %}s) including 2FA (two-factor auth). {% endtip %} {% data reusables.user-settings.password-authentication-deprecation %} -## Atualizar credenciais pelo Keychain Access +## Updating your credentials via Keychain Access -1. Clique no ícone do Spotlight (lente ampliada) no lado direito da barra de menu. Digite `Keychain access` e pressione a tecla ENTER para iniciar o aplicativo. - ![Barra de pesquisa do Spotlight](/assets/images/help/setup/keychain-access.png) -2. Em Acesso ao Conjunto de Chaves, pesquise **{% data variables.command_line.backticks %}** . -3. Localize a entrada "senha da Internet" para `{% data variables.command_line.backticks %}`. -4. Edite ou exclua a entrada de acordo. +1. Click on the Spotlight icon (magnifying glass) on the right side of the menu bar. Type `Keychain access` then press the Enter key to launch the app. + ![Spotlight Search bar](/assets/images/help/setup/keychain-access.png) +2. In Keychain Access, search for **{% data variables.command_line.backticks %}**. +3. Find the "internet password" entry for `{% data variables.command_line.backticks %}`. +4. Edit or delete the entry accordingly. -## Excluir credenciais pela linha de comando +## Deleting your credentials via the command line -Através da linha de comando, você pode usar o auxiliar de credenciais diretamente para apagar a entrada de keychain. +Through the command line, you can use the credential helper directly to erase the keychain entry. ```shell $ git credential-osxkeychain erase host={% data variables.command_line.codeblock %} protocol=https -> [Press Return] +> [Press Return] ``` -Se isso for bem-sucedido, nada será impresso. Para testar se ele funciona, tente clonar um repositório privado do {% data variables.product.product_location %}. Se for solicitada uma senha, significa que a entrada da keychain foi excluída. +If it's successful, nothing will print out. To test that it works, try and clone a private repository from {% data variables.location.product_location %}. If you are prompted for a password, the keychain entry was deleted. -## Leitura adicional +## Further reading -- "[Como armazenar em cache suas credenciais do {% data variables.product.prodname_dotcom %} no Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)" +- "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)" diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md b/translations/pt-BR/content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md index ccee2bd490..284df7ffb1 100644 --- a/translations/pt-BR/content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md +++ b/translations/pt-BR/content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md @@ -1,6 +1,6 @@ --- -title: Por que o Git sempre solicita a minha senha? -intro: 'Se o Git solicita um nome de usuário e uma senha toda vez que você tenta interagir com o GitHub, provavelmente isso quer dizer que você está usando a URL de clone de HTTPS do seu repositório.' +title: Why is Git always asking for my password? +intro: 'If Git prompts you for a username and password every time you try to interact with GitHub, you''re probably using the HTTPS clone URL for your repository.' redirect_from: - /articles/why-is-git-always-asking-for-my-password - /github/using-git/why-is-git-always-asking-for-my-password @@ -12,21 +12,15 @@ versions: ghae: '*' ghec: '*' shortTitle: Git passwords -ms.openlocfilehash: 06a8cf617072075f39a880ec58173e7cfbc5bc8a -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145126724' --- -Usar uma URL remota do tipo HTTPS tem algumas vantagens em comparação com o uso de SSH. É mais fácil configurar do que SSH e geralmente funciona por meio de firewalls e proxies rigorosos. No entanto, ele também pede que você insira suas credenciais de {% data variables.product.product_name %} sempre que você fizer pull ou push de um repositório. +Using an HTTPS remote URL has some advantages compared with using SSH. It's easier to set up than SSH, and usually works through strict firewalls and proxies. However, it also prompts you to enter your {% data variables.product.product_name %} credentials every time you pull or push a repository. {% data reusables.user-settings.password-authentication-deprecation %} -Você pode evitar que a sua senha seja solicitada configurando o Git para [armazenar credenciais em cache](/github/getting-started-with-github/caching-your-github-credentials-in-git) para você. Uma vez que você configurado o armazenamento de credenciais, o Git usa automaticamente seu token de acesso pessoal armazenado quando você extrai ou faz push de um repositório usando HTTPS. +You can avoid being prompted for your password by configuring Git to [cache your credentials](/github/getting-started-with-github/caching-your-github-credentials-in-git) for you. Once you've configured credential caching, Git automatically uses your cached {% data variables.product.pat_generic %} when you pull or push a repository using HTTPS. -## Leitura adicional +## Further reading -- "[Sobre repositórios remotos](/github/getting-started-with-github/about-remote-repositories)". -- "[Sobre a autenticação no {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)" -- "[Adicionar sua chave SSH ao ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)" +- "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)." +- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)" +- "[Adding your SSH key to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)" diff --git a/translations/pt-BR/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md b/translations/pt-BR/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md index fc03134cdc..d42181b790 100644 --- a/translations/pt-BR/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md +++ b/translations/pt-BR/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md @@ -1,6 +1,6 @@ --- -title: Adicionando o código localmente hospedado no GitHub -intro: 'Aprenda a adicionar código-fonte ou repositórios existentes em {% data variables.product.product_name %} pela linha de comando usando {% data variables.product.prodname_cli %} ou Comandos do Git. Em seguida, compartilhe seu código e convide outras pessoas a trabalhar com você.' +title: Adding locally hosted code to GitHub +intro: 'Learn how to add existing source code or repositories to {% data variables.product.product_name %} from the command line using {% data variables.product.prodname_cli %} or Git Commands. Then, share your code and invite others to work with you.' redirect_from: - /articles/add-an-existing-project-to-github - /articles/adding-an-existing-project-to-github-using-the-command-line @@ -13,79 +13,85 @@ versions: ghae: '*' ghec: '*' shortTitle: Add locally hosted code -ms.openlocfilehash: 5dc22ef9d8b5f11618bc90414c9d94fcdfe50462 -ms.sourcegitcommit: 22d665055b1bee7a5df630385e734e3a149fc720 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 07/13/2022 -ms.locfileid: '145126721' --- -## Sobre a adição do código-fonte existente para {% data variables.product.product_name %} -Se você tiver código-fonte ou repositórios armazenados localmente no computador ou em uma rede privada, você poderá adicioná-los a {% data variables.product.product_name %}, digitando comandos em um terminal. Você pode fazer isso digitando comandos do Git diretamente ou usando {% data variables.product.prodname_cli %}. +## About adding existing source code to {% data variables.product.product_name %} -A {% data variables.product.prodname_cli %} é uma ferramenta de código aberto para uso do {% data variables.product.prodname_dotcom %} na linha de comando do computador. {% data variables.product.prodname_cli %} pode simplificar o processo de adicionar um projeto existente a {% data variables.product.product_name %} usando a linha de comando. Para saber mais sobre a {% data variables.product.prodname_cli %}, confira "[Sobre a {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)". +If you have existing source code or repositories stored locally on your computer or private network you can add them to {% data variables.product.product_name %} by typing commands in a terminal. You can do this by typing Git commands directly, or by using {% data variables.product.prodname_cli %}. + +{% data variables.product.prodname_cli %} is an open source tool for using {% data variables.product.prodname_dotcom %} from your computer's command line. {% data variables.product.prodname_cli %} can simplify the process of adding an existing project to {% data variables.product.product_name %} using the command line. To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." {% tip %} -**Dica:** se estiver mais familiarizado com uma interface de usuário de apontar e clicar, tente adicionar seu projeto com o {% data variables.product.prodname_desktop %}. Para obter mais informações, confira "[Adicionando um repositório do computador local ao GitHub Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop)" na *Ajuda do {% data variables.product.prodname_desktop %}* . +**Tip:** If you're most comfortable with a point-and-click user interface, try adding your project with {% data variables.product.prodname_desktop %}. For more information, see "[Adding a repository from your local computer to GitHub Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop)" in the *{% data variables.product.prodname_desktop %} Help*. {% endtip %} {% data reusables.repositories.sensitive-info-warning %} -## Adicionando um repositório local para {% data variables.product.product_name %} com {% data variables.product.prodname_cli %} +## Adding a local repository to {% data variables.product.product_name %} with {% data variables.product.prodname_cli %} -1. Na linha de comando, acesse o diretório raiz do seu projeto. -1. Inicialize o diretório local como um repositório Git. +1. In the command line, navigate to the root directory of your project. +1. Initialize the local directory as a Git repository. ```shell git init -b main ``` -1. Faça o teste e commit de todos os arquivos do seu projeto +1. Stage and commit all the files in your project. ```shell git add . && git commit -m "initial commit" ``` -1. Para criar um repositório para seu projeto no GitHub, use o subcomando `gh repo create`. Quando solicitado, selecione **Efetuar push de um repositório local existente para o GitHub** e digite o nome desejado para o repositório. Caso você deseje que o seu projeto pertença a uma organização em vez da sua conta de usuário, especifique o nome da organização e o nome do projeto com `organization-name/project-name`. +1. To create a repository for your project on GitHub, use the `gh repo create` subcommand. When prompted, select **Push an existing local repository to GitHub** and enter the desired name for your repository. If you want your project to belong to an organization instead of your user account, specify the organization name and project name with `organization-name/project-name`. -1. Siga as instruções interativas. Para adicionar o controle remoto e fazer push do repositório, confirme sim quando solicitado para adicionar o controle remoto e enviar os commits para o branch atual. +1. Follow the interactive prompts. To add the remote and push the repository, confirm yes when asked to add the remote and push the commits to the current branch. -1. Como alternativa, para ignorar todos os prompts, forneça o caminho para o repositório com o sinalizador `--source` e passe um sinalizador de visibilidade (`--public`, `--private` ou `--internal`). Por exemplo, `gh repo create --source=. --public`. Especifique um repositório remoto com o sinalizador `--remote`. Para enviar seus commits por push, passe o sinalizador `--push`. Para obter mais informações sobre os possíveis argumentos, confira o [manual da CLI do GitHub](https://cli.github.com/manual/gh_repo_create). +1. Alternatively, to skip all the prompts, supply the path to the repository with the `--source` flag and pass a visibility flag (`--public`, `--private`, or `--internal`). For example, `gh repo create --source=. --public`. Specify a remote with the `--remote` flag. To push your commits, pass the `--push` flag. For more information about possible arguments, see the [GitHub CLI manual](https://cli.github.com/manual/gh_repo_create). -## Adicionando um repositório local para {% data variables.product.product_name %} usando o Git +## Adding a local repository to {% data variables.product.product_name %} using Git {% mac %} -1. [Crie um repositório](/repositories/creating-and-managing-repositories/creating-a-new-repository) no {% data variables.product.product_location %}. Para evitar erros, não inicialize o novo repositório com *README*, licença nem arquivos `gitignore`. É possível adicionar esses arquivos após push do projeto no {% data variables.product.product_name %}. - ![Lista suspensa Criar Repositório](/assets/images/help/repository/repo-create.png) {% data reusables.command_line.open_the_multi_os_terminal %} -3. Altere o diretório de trabalho atual para seu projeto local. -4. Inicialize o diretório local como um repositório Git. - ```shell - $ git init -b main - ``` -5. Adicione os arquivos ao novo repositório local. Isso faz stage deles para o primeiro commit. +1. [Create a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository) on {% data variables.location.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}. + ![Create New Repository drop-down](/assets/images/help/repository/repo-create.png) +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Change the current working directory to your local project. +4. Use the `init` command to initialize the local directory as a Git repository. By default, the initial branch is called `master`. + + If you’re using Git 2.28.0 or a later version, you can set the name of the default branch using `-b`. + + ``` shell + $ git init -b main + ``` + + If you’re using Git 2.27.1 or an earlier version, you can set the name of the default branch using `&& git symbolic-ref HEAD refs/heads/main`. + + ``` shell + $ git init && git symbolic-ref HEAD refs/heads/main + ``` +5. Add the files in your new local repository. This stages them for the first commit. + ```shell $ git add . # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %} ``` -6. Faça commit dos arquivos com stage em seu repositório local. +6. Commit the files that you've staged in your local repository. ```shell $ git commit -m "First commit" # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %} ``` -7. Na parte superior do seu repositório na página de Configuração Rápida de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, clique em {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar a URL do repositório remoto. - ![Campo Copiar URL do repositório remoto](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) -8. No Terminal, [adicione a URL do repositório remoto](/github/getting-started-with-github/managing-remote-repositories) em que o repositório local será enviado por push. +7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL. + ![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) +8. In Terminal, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed. ```shell - $ git remote add origin <REMOTE_URL> + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL ``` -9. [Efetue push das alterações](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) no repositório local para o {% data variables.product.product_location %}. +9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.location.product_location %}. ```shell $ git push -u origin main # Pushes the changes in your local repository up to the remote repository you specified as the origin @@ -95,33 +101,43 @@ A {% data variables.product.prodname_cli %} é uma ferramenta de código aberto {% windows %} -1. [Crie um repositório](/articles/creating-a-new-repository) no {% data variables.product.product_location %}. Para evitar erros, não inicialize o novo repositório com *README*, licença nem arquivos `gitignore`. É possível adicionar esses arquivos após push do projeto no {% data variables.product.product_name %}. - ![Lista suspensa Criar Repositório](/assets/images/help/repository/repo-create.png) {% data reusables.command_line.open_the_multi_os_terminal %} -3. Altere o diretório de trabalho atual para seu projeto local. -4. Inicialize o diretório local como um repositório Git. - ```shell - $ git init -b main - ``` -5. Adicione os arquivos ao novo repositório local. Isso faz stage deles para o primeiro commit. +1. [Create a new repository](/articles/creating-a-new-repository) on {% data variables.location.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}. + ![Create New Repository drop-down](/assets/images/help/repository/repo-create.png) +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Change the current working directory to your local project. +4. Use the `init` command to initialize the local directory as a Git repository. By default, the initial branch is called `master`. + + If you’re using Git 2.28.0 or a later version, you can set the name of the default branch using `-b`. + + ``` shell + $ git init -b main + ``` + + If you’re using Git 2.27.1 or an earlier version, you can set the name of the default branch using `&& git symbolic-ref HEAD refs/heads/main`. + + ``` shell + $ git init && git symbolic-ref HEAD refs/heads/main + ``` +5. Add the files in your new local repository. This stages them for the first commit. ```shell $ git add . # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %} ``` -6. Faça commit dos arquivos com stage em seu repositório local. +6. Commit the files that you've staged in your local repository. ```shell $ git commit -m "First commit" # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %} ``` -7. Na parte superior do seu repositório na página de Configuração Rápida de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, clique em {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar a URL do repositório remoto. - ![Campo Copiar URL do repositório remoto](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) -8. No Prompt de comando, [adicione a URL do repositório remoto](/github/getting-started-with-github/managing-remote-repositories) em que o repositório local será enviado por push. +7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL. + ![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) +8. In the Command prompt, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed. ```shell - $ git remote add origin <REMOTE_URL> + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL ``` -9. [Efetue push das alterações](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) no repositório local para o {% data variables.product.product_location %}. +9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.location.product_location %}. ```shell $ git push origin main # Pushes the changes in your local repository up to the remote repository you specified as the origin @@ -131,33 +147,43 @@ A {% data variables.product.prodname_cli %} é uma ferramenta de código aberto {% linux %} -1. [Crie um repositório](/articles/creating-a-new-repository) no {% data variables.product.product_location %}. Para evitar erros, não inicialize o novo repositório com *README*, licença nem arquivos `gitignore`. É possível adicionar esses arquivos após push do projeto no {% data variables.product.product_name %}. - ![Lista suspensa Criar Repositório](/assets/images/help/repository/repo-create.png) {% data reusables.command_line.open_the_multi_os_terminal %} -3. Altere o diretório de trabalho atual para seu projeto local. -4. Inicialize o diretório local como um repositório Git. - ```shell - $ git init -b main - ``` -5. Adicione os arquivos ao novo repositório local. Isso faz stage deles para o primeiro commit. +1. [Create a new repository](/articles/creating-a-new-repository) on {% data variables.location.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}. + ![Create New Repository drop-down](/assets/images/help/repository/repo-create.png) +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Change the current working directory to your local project. +4. Use the `init` command to initialize the local directory as a Git repository. By default, the initial branch is called `master`. + + If you’re using Git 2.28.0 or a later version, you can set the name of the default branch using `-b`. + + ``` shell + $ git init -b main + ``` + + If you’re using Git 2.27.1 or an earlier version, you can set the name of the default branch using `&& git symbolic-ref HEAD refs/heads/main`. + + ``` shell + $ git init && git symbolic-ref HEAD refs/heads/main + ``` +5. Add the files in your new local repository. This stages them for the first commit. ```shell $ git add . # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %} ``` -6. Faça commit dos arquivos com stage em seu repositório local. +6. Commit the files that you've staged in your local repository. ```shell $ git commit -m "First commit" # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %} ``` -7. Na parte superior do seu repositório na página de Configuração Rápida de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, clique em {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar a URL do repositório remoto. - ![Campo Copiar URL do repositório remoto](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) -8. No Terminal, [adicione a URL do repositório remoto](/github/getting-started-with-github/managing-remote-repositories) em que o repositório local será enviado por push. +7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL. + ![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) +8. In Terminal, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed. ```shell - $ git remote add origin <REMOTE_URL> + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL ``` -9. [Efetue push das alterações](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) no repositório local para o {% data variables.product.product_location %}. +9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.location.product_location %}. ```shell $ git push origin main # Pushes the changes in your local repository up to the remote repository you specified as the origin @@ -165,6 +191,6 @@ A {% data variables.product.prodname_cli %} é uma ferramenta de código aberto {% endlinux %} -## Leitura adicional +## Further reading -- "[Como adicionar um arquivo a um repositório](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)" +- "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)" diff --git a/translations/pt-BR/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md b/translations/pt-BR/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md index cf939a77a4..c25bdf5f5c 100644 --- a/translations/pt-BR/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md +++ b/translations/pt-BR/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md @@ -1,6 +1,6 @@ --- -title: Importar um repositório Git usando a linha de comando -intro: '{% ifversion fpt %}Se o [GitHub Importer](/articles/importing-a-repository-with-github-importer) não for adequado aos seus propósitos, como quando o código existente está hospedado em uma rede privada, recomendamos que a importação seja feita usando a linha de comando.{% else %}A importação de projetos do Git usando a linha de comando é indicada quando o código existente está hospedado em uma rede privada.{% endif %}' +title: Importing a Git repository using the command line +intro: '{% ifversion fpt %}If [GitHub Importer](/articles/importing-a-repository-with-github-importer) is not suitable for your purposes, such as if your existing code is hosted on a private network, then we recommend importing using the command line.{% else %}Importing Git projects using the command line is suitable when your existing code is hosted on a private network.{% endif %}' redirect_from: - /articles/importing-a-git-repository-using-the-command-line - /github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line @@ -11,43 +11,37 @@ versions: ghae: '*' ghec: '*' shortTitle: Import repo locally -ms.openlocfilehash: bd3a5e5ffca38250a74851444f6cac4cbb06eb53 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145126720' --- -Antes de iniciar, certifique-se de que sabe: +Before you start, make sure you know: -- Seu nome de usuário {% data variables.product.product_name %} -- A URL de clone para o repositório externo, como `https://external-host.com/user/repo.git` ou `git://external-host.com/user/repo.git` (talvez com um `user@` na frente do nome de domínio `external-host.com`) +- Your {% data variables.product.product_name %} username +- The clone URL for the external repository, such as `https://external-host.com/user/repo.git` or `git://external-host.com/user/repo.git` (perhaps with a `user@` in front of the `external-host.com` domain name) {% tip %} -Como demonstração, usaremos: +For purposes of demonstration, we'll use: -- Uma conta externa chamada **extuser** -- Um host do Git externo chamado `https://external-host.com` -- Uma conta pessoal do {% data variables.product.product_name %} chamada **ghuser** -- Um repositório no {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} chamado **repo.git** +- An external account named **extuser** +- An external Git host named `https://external-host.com` +- A {% data variables.product.product_name %} personal account named **ghuser** +- A repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} named **repo.git** {% endtip %} -1. [Crie um repositório no {% data variables.product.product_name %}](/articles/creating-a-new-repository). Você importará o repositório Git externo para este novo repositório. -2. Na linha de comando, faça um clone "vazio" do repositório usando a URL clone externo. Isso criará uma cópia integral dos dados, mas sem um diretório de trabalho para editar arquivos, e garantirá uma exportação limpa e recente de todos os dados antigos. +1. [Create a new repository on {% data variables.product.product_name %}](/articles/creating-a-new-repository). You'll import your external Git repository to this new repository. +2. On the command line, make a "bare" clone of the repository using the external clone URL. This creates a full copy of the data, but without a working directory for editing files, and ensures a clean, fresh export of all the old data. ```shell - $ git clone --bare https://external-host.com/extuser/repo.git + $ git clone --bare https://external-host.com/EXTUSER/REPO.git # Makes a bare clone of the external repository in a local directory ``` -3. Faça o push do repositório clonado localmente em {% data variables.product.product_name %} usando a opção "mirror" (espelho), que assegura que todas as referências, como branches e tags, são copiadas para o repositório importado. +3. Push the locally cloned repository to {% data variables.product.product_name %} using the "mirror" option, which ensures that all references, such as branches and tags, are copied to the imported repository. ```shell - $ cd repo.git - $ git push --mirror https://{% data variables.command_line.codeblock %}/ghuser/repo.git - # Pushes the mirror to the new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} + $ cd REPO.git + $ git push --mirror https://{% data variables.command_line.codeblock %}/USER/REPO.git + # Pushes the mirror to the new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} ``` -4. Remova o repositório local temporário. +4. Remove the temporary local repository. ```shell $ cd .. - $ rm -rf repo.git + $ rm -rf REPO.git ``` diff --git a/translations/pt-BR/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md b/translations/pt-BR/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md index 7a975b441c..ab8be9b319 100644 --- a/translations/pt-BR/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md +++ b/translations/pt-BR/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md @@ -1,6 +1,6 @@ --- -title: Importar um repositório usando o Importador do GitHub -intro: 'Caso tenha um projeto hospedado em outro sistema de controle de versão, é possível importá-lo automaticamente para o GitHub usando a ferramenta Importador do GitHub.' +title: Importing a repository with GitHub Importer +intro: 'If you have a project hosted on another version control system, you can automatically import it to GitHub using the GitHub Importer tool.' redirect_from: - /articles/importing-from-other-version-control-systems-to-github - /articles/importing-a-repository-with-github-importer @@ -10,42 +10,37 @@ versions: fpt: '*' ghec: '*' shortTitle: Use GitHub Importer -ms.openlocfilehash: 09b03d2c2c62cf5812f35a3d5b3379c2d0c8e33e -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145911196' --- {% tip %} -**Dica:** o Importador do GitHub não é adequado para todas as importações. Por exemplo, se o código existente está hospedado em uma rede privada, sua ferramenta não conseguirá acessá-lo. Nesses casos, recomendamos [importá-lo usando a linha de comando](/articles/importing-a-git-repository-using-the-command-line) para repositórios Git ou uma [ferramenta de migração de código-fonte](/articles/source-code-migration-tools) externa para projetos importados de outros sistemas de controle de versão. +**Tip:** GitHub Importer is not suitable for all imports. For example, if your existing code is hosted on a private network, our tool won't be able to access it. In these cases, we recommend [importing using the command line](/articles/importing-a-git-repository-using-the-command-line) for Git repositories or an external [source code migration tool](/articles/source-code-migration-tools) for projects imported from other version control systems. {% endtip %} -Se você quiser combinar os commits de seu repositório com as contas pessoais GitHub do autor durante a importação, garanta que cada contribuidor de seu repositório tem uma conta GitHub antes de você começar a importação. +If you'd like to match the commits in your repository to the authors' GitHub personal accounts during the import, make sure every contributor to your repository has a GitHub account before you begin the import. {% data reusables.repositories.repo-size-limit %} -1. No canto superior direito de qualquer página, clique em {% octicon "plus" aria-label="Plus symbol" %} e clique em **Importar repositório**. -![Opção Importar repositório no menu Novo repositório](/assets/images/help/importer/import-repository.png) -2. Embaixo de "Your old repository's clone URL" (URL clone de seu antigo repositório), digite a URL do projeto que quer importar. -![Campo de texto da URL do repositório importado](/assets/images/help/importer/import-url.png) -3. Escolha sua conta pessoal ou uma organização para ser proprietária do repositório e digite um nome para o repositório no GitHub. -![Menu Proprietário do repositório e campo Nome do repositório](/assets/images/help/importer/import-repo-owner-name.png) -4. Especifique se o novo repositório deve ser *público* ou *privado*. Para obter mais informações, confira "[Como configurar a visibilidade do repositório](/articles/setting-repository-visibility)". -![Botões de opção Repositório público ou privado](/assets/images/help/importer/import-public-or-private.png) -5. Revise as informações inseridas e clique em **Iniciar importação**. -![Botão Iniciar importação](/assets/images/help/importer/begin-import-button.png) -6. Se seu projeto antigo exigir credenciais, digite suas informações de login para esse projeto e clique em **Enviar**. Se o SSO do SAML ou 2FA estiverem habilitados para sua conta de usuário no projeto antigo, insira um token de acesso pessoal com permissões de leitura de repositório no campo "Senha" em vez de sua senha. -![Formulário de senha e botão Enviar para projetos protegidos por senha](/assets/images/help/importer/submit-old-credentials-importer.png) -7. Se houver vários projetos hospedados na URL de clone do seu projeto antigo, escolha o projeto que deseja importar e clique em **Enviar**. -![Lista de projetos para importação e botão Enviar](/assets/images/help/importer/choose-project-importer.png) -8. Se o projeto contiver arquivos maiores que 100 MB, escolha se deseja importar os arquivos grandes usando o [Git Large File Storage](/articles/versioning-large-files) e clique em **Continuar**. -![Menu do Git Large File Storage e botão Continuar](/assets/images/help/importer/select-gitlfs-importer.png) +1. In the upper-right corner of any page, click {% octicon "plus" aria-label="Plus symbol" %}, and then click **Import repository**. +![Import repository option in new repository menu](/assets/images/help/importer/import-repository.png) +2. Under "Your old repository's clone URL", type the URL of the project you want to import. +![Text field for URL of imported repository](/assets/images/help/importer/import-url.png) +3. Choose your personal account or an organization to own the repository, then type a name for the repository on GitHub. +![Repository owner menu and repository name field](/assets/images/help/importer/import-repo-owner-name.png) +4. Specify whether the new repository should be *public* or *private*. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)." +![Public or private repository radio buttons](/assets/images/help/importer/import-public-or-private.png) +5. Review the information you entered, then click **Begin import**. +![Begin import button](/assets/images/help/importer/begin-import-button.png) +6. If your old project requires credentials, type your login information for that project, then click **Submit**. +If SAML SSO or 2FA are enabled for your user account on the old project, enter a {% data variables.product.pat_generic %} with repository read permissions in the "Password" field instead of your password. +![Password form and Submit button for password-protected project](/assets/images/help/importer/submit-old-credentials-importer.png) +7. If there are multiple projects hosted at your old project's clone URL, choose the project you'd like to import, then click **Submit**. +![List of projects to import and Submit button](/assets/images/help/importer/choose-project-importer.png) +8. If your project contains files larger than 100 MB, choose whether to import the large files using [Git Large File Storage](/articles/versioning-large-files), then click **Continue**. +![Git Large File Storage menu and Continue button](/assets/images/help/importer/select-gitlfs-importer.png) -Você receberá um e-mail quando o repositório for totalmente importado. +You'll receive an email when the repository has been completely imported. -## Leitura adicional +## Further reading -- "[Como atualizar a atribuição de autor de commit com o Importador do GitHub](/articles/updating-commit-author-attribution-with-github-importer)" +- "[Updating commit author attribution with GitHub Importer](/articles/updating-commit-author-attribution-with-github-importer)" diff --git a/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md index d0d20d47d6..401194125d 100644 --- a/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md +++ b/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md @@ -62,7 +62,7 @@ To learn about what you need to know to plan your {% data variables.product.prod ## Enabling {% data variables.product.prodname_advanced_security %} features {%- ifversion ghes %} -The site administrator must enable {% data variables.product.prodname_advanced_security %} for {% data variables.product.product_location %} before you can use these features. For more information, see "[Configuring Advanced Security features](/admin/configuration/configuring-advanced-security-features). +The site administrator must enable {% data variables.product.prodname_advanced_security %} for {% data variables.location.product_location %} before you can use these features. For more information, see "[Configuring Advanced Security features](/admin/configuration/configuring-advanced-security-features). Once your system is set up, you can enable and disable these features at the organization or repository level. diff --git a/translations/pt-BR/content/get-started/learning-about-github/access-permissions-on-github.md b/translations/pt-BR/content/get-started/learning-about-github/access-permissions-on-github.md index 18485e36e3..8967160362 100644 --- a/translations/pt-BR/content/get-started/learning-about-github/access-permissions-on-github.md +++ b/translations/pt-BR/content/get-started/learning-about-github/access-permissions-on-github.md @@ -1,5 +1,5 @@ --- -title: Permissões de acesso no GitHub +title: Access permissions on GitHub redirect_from: - /articles/needs-to-be-written-what-can-the-different-types-of-org-team-permissions-do - /articles/what-are-the-different-types-of-team-permissions @@ -7,7 +7,7 @@ redirect_from: - /articles/access-permissions-on-github - /github/getting-started-with-github/access-permissions-on-github - /github/getting-started-with-github/learning-about-github/access-permissions-on-github -intro: 'Com as funções, você pode controlar quem tem acesso às suas contas e recursos em {% data variables.product.product_name %} bem como o nível de acesso de cada pessoa.' +intro: 'With roles, you can control who has access to your accounts and resources on {% data variables.product.product_name %} and the level of access each person has.' versions: fpt: '*' ghes: '*' @@ -17,41 +17,40 @@ topics: - Permissions - Accounts shortTitle: Access permissions -ms.openlocfilehash: 32db1949cbc110559023f719682caed0319aae9e -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145126695' --- -## Sobre as permissões de acesso em {% data variables.product.prodname_dotcom %} + +## About access permissions on {% data variables.product.prodname_dotcom %} {% data reusables.organizations.about-roles %} -As funções funcionam de forma diferente para diferentes tipos de contas. Para obter mais informações sobre contas, confira "[Tipos de contas do {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)". +Roles work differently for different types of accounts. For more information about accounts, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)." -## Contas pessoais +## Personal accounts -Um repositório pertencente a uma conta pessoal tem dois níveis de permissão: *proprietário do repositório* e *colaboradores*. Para obter mais informações, confira "[Níveis de permissão para um repositório da conta pessoal](/articles/permission-levels-for-a-user-account-repository)". +A repository owned by a personal account has two permission levels: the *repository owner* and *collaborators*. For more information, see "[Permission levels for a personal account repository](/articles/permission-levels-for-a-user-account-repository)." -## Contas da organização +## Organization accounts -Os membros da organização podem ter as funções *proprietário*{% ifversion fpt or ghec %}, *gerente de cobrança* {% endif %} ou *membro*. Os proprietários têm acesso administrativo completo à sua organização{% ifversion fpt or ghec %}, enquanto os gerentes de cobrança podem gerenciar as configurações de cobrança{% endif %}. O integrante é a função padrão de todos os outros. Você pode gerenciar as permissões de acesso para vários integrantes por vez com equipes. Para obter mais informações, consulte: -- "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" -- "[Permissões de quadro de projetos para uma organização](/articles/project-board-permissions-for-an-organization)" -- "[Funções de repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" -- "[Sobre as equipes](/articles/about-teams)" +Organization members can have *owner*{% ifversion fpt or ghec %}, *billing manager*,{% endif %} or *member* roles. Owners have complete administrative access to your organization{% ifversion fpt or ghec %}, while billing managers can manage billing settings{% endif %}. Member is the default role for everyone else. You can manage access permissions for multiple members at a time with teams. For more information, see: +- "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" +- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" +- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" +- "[About teams](/articles/about-teams)" -## Conta corporativa +## Enterprise accounts -{% ifversion fpt %} {% data reusables.gated-features.enterprise-accounts %} +{% ifversion fpt %} +{% data reusables.gated-features.enterprise-accounts %} -Para obter mais informações sobre as permissões para contas corporativas, confira [a documentação do {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/get-started/learning-about-github/access-permissions-on-github). -{% else %} Os *proprietários da empresa* têm poder final sobre a conta corporativa e podem executar todas as ações na conta corporativa.{% ifversion ghec or ghes %} Os *gerentes de cobrança* podem gerenciar as configurações de cobrança da sua conta corporativa.{% endif %} Os membros e os colaboradores externos de organizações pertencentes à sua conta corporativa são automaticamente membros da conta corporativa, embora não tenham acesso à própria conta corporativa ou às configurações dela. Para obter mais informações, confira "[Funções em uma empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)". +For more information about permissions for enterprise accounts, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/access-permissions-on-github). +{% else %} +*Enterprise owners* have ultimate power over the enterprise account and can take every action in the enterprise account.{% ifversion ghec or ghes %} *Billing managers* can manage your enterprise account's billing settings.{% endif %} Members and outside collaborators of organizations owned by your enterprise account are automatically members of the enterprise account, although they have no access to the enterprise account itself or its settings. For more information, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)." -{% ifversion ghec %} Se uma empresa usar os {% data variables.product.prodname_emus %}, os membros serão provisionados como novas contas pessoais no {% data variables.product.prodname_dotcom %} e serão totalmente gerenciados pelo provedor de identidade. O {% data variables.product.prodname_managed_users %} tem acesso somente leitura a repositórios que não fazem parte da sua empresa e não podem interagir com usuários que não são também integrantes da empresa. Nas organizações pertencentes à empresa, é possível conceder ao {% data variables.product.prodname_managed_users %} os mesmos níveis de acesso granular disponíveis para organizações regulares. Para obter mais informações, confira "[Sobre as {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)". -{% endif %} {% endif %} +{% ifversion ghec %} +If an enterprise uses {% data variables.product.prodname_emus %}, members are provisioned as new personal accounts on {% data variables.product.prodname_dotcom %} and are fully managed by the identity provider. The {% data variables.enterprise.prodname_managed_users %} have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the {% data variables.enterprise.prodname_managed_users %} can be granted the same granular access levels available for regular organizations. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." +{% endif %} +{% endif %} -## Leitura adicional +## Further reading -- "[Tipos de contas do {% data variables.product.prodname_dotcom %}](/articles/types-of-github-accounts)" +- "[Types of {% data variables.product.prodname_dotcom %} accounts](/articles/types-of-github-accounts)" diff --git a/translations/pt-BR/content/get-started/learning-about-github/types-of-github-accounts.md b/translations/pt-BR/content/get-started/learning-about-github/types-of-github-accounts.md index 43a13f104f..70b4afd8f5 100644 --- a/translations/pt-BR/content/get-started/learning-about-github/types-of-github-accounts.md +++ b/translations/pt-BR/content/get-started/learning-about-github/types-of-github-accounts.md @@ -1,6 +1,6 @@ --- -title: Tipos de contas do GitHub -intro: 'As contas em {% data variables.product.product_name %} permitem que você organize e controle o acesso ao código.' +title: Types of GitHub accounts +intro: 'Accounts on {% data variables.product.product_name %} allow you to organize and control access to code.' redirect_from: - /manage-multiple-clients - /managing-clients @@ -20,69 +20,70 @@ topics: - Mobile - Desktop - Security -ms.openlocfilehash: 9316fcb8b069b0b596c89d10ac1f89d86f1a62b7 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145126683' --- -## Sobre as contas em {% data variables.product.product_name %} -Com {% data variables.product.product_name %}, você pode armazenar e colaborar no código. As contas permitem que você organize e controle o acesso a esse código. Existem três tipos de contas em {% data variables.product.product_name %}. -- Contas pessoais -- Contas da organização -- Conta corporativa +## About accounts on {% data variables.product.product_name %} -Todas as pessoas que usam {% data variables.product.product_name %} efetuam o login em uma conta pessoal. A conta de uma organização melhora a colaboração entre várias contas pessoais, e {% ifversion fpt or ghec %}uma conta corporativa{% else %}a conta corporativa do {% data variables.product.product_location %}{% endif %} permite o gerenciamento central de múltiplas organizações. +With {% data variables.product.product_name %}, you can store and collaborate on code. Accounts allow you to organize and control access to that code. There are three types of accounts on {% data variables.product.product_name %}. +- Personal accounts +- Organization accounts +- Enterprise accounts -## Contas pessoais +Every person who uses {% data variables.product.product_name %} signs into a personal account. An organization account enhances collaboration between multiple personal accounts, and {% ifversion fpt or ghec %}an enterprise account{% else %}the enterprise account for {% data variables.location.product_location %}{% endif %} allows central management of multiple organizations. -Todas as pessoas que usam {% data variables.product.product_location %} efetuam o login em uma conta pessoal. A sua conta pessoal é sua identidade em {% data variables.product.product_location %} e tem um nome de usuário e perfil. Por exemplo, confira o [ perfil de @octocat](https://github.com/octocat). +## Personal accounts -A sua conta pessoal pode ter recursos próprios, como repositórios, pacotes e projetos. Sempre que você tomar qualquer ação em {% data variables.product.product_location %}, como criar um problema ou revisar um pull request, a ação é atribuída à sua conta pessoal. +Every person who uses {% data variables.location.product_location %} signs into a personal account. Your personal account is your identity on {% data variables.location.product_location %} and has a username and profile. For example, see [@octocat's profile](https://github.com/octocat). -{% ifversion fpt or ghec %}Cada conta pessoal usa {% data variables.product.prodname_free_user %} ou {% data variables.product.prodname_pro %}. Todas as contas pessoais podem ter um número ilimitado de repositórios públicos e privados, com um número ilimitado de colaboradores nesses repositórios. Se você usar {% data variables.product.prodname_free_user %}, os repositórios privados pertencentes à sua conta pessoal terão um conjunto de recursos limitado. Você pode fazer a atualização para {% data variables.product.prodname_pro %} para obter um conjunto completo de recursos para repositórios privados. Para obter mais informações, confira "[Produtos do {% data variables.product.prodname_dotcom %}](/articles/githubs-products)". {% else %}Você pode criar um número ilimitado de repositórios pertencentes à sua conta pessoal, com um número ilimitado de colaboradores nesses repositórios.{% endif %} +Your personal account can own resources such as repositories, packages, and projects. Any time you take any action on {% data variables.location.product_location %}, such as creating an issue or reviewing a pull request, the action is attributed to your personal account. + +{% ifversion fpt or ghec %}Each personal account uses either {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %}. All personal accounts can own an unlimited number of public and private repositories, with an unlimited number of collaborators on those repositories. If you use {% data variables.product.prodname_free_user %}, private repositories owned by your personal account have a limited feature set. You can upgrade to {% data variables.product.prodname_pro %} to get a full feature set for private repositories. For more information, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)." {% else %}You can create an unlimited number of repositories owned by your personal account, with an unlimited number of collaborators on those repositories.{% endif %} {% tip %} -**Dica**: as contas pessoais são destinadas a pessoas, mas você pode criar contas para automatizar a atividade no {% data variables.product.product_name %}. Este tipo de conta é denominado usuário de máquina. Por exemplo, você pode criar uma conta de usuário de máquina para automatizar os fluxos de trabalho da integração contínua (CI). +**Tip**: Personal accounts are intended for humans, but you can create accounts to automate activity on {% data variables.product.product_name %}. This type of account is called a machine user. For example, you can create a machine user account to automate continuous integration (CI) workflows. {% endtip %} -{% ifversion fpt or ghec %} A maioria das pessoas usará uma conta pessoal para todo o trabalho no {% data variables.product.prodname_dotcom_the_website %}, incluindo projetos de código aberto e emprego remunerado. Se você está usando atualmente mais de uma conta pessoal criada por você, sugerimos que você combine as contas. Para obter mais informações, confira "[Como mesclar várias contas pessoais](/articles/merging-multiple-user-accounts)". +{% ifversion fpt or ghec %} +Most people will use one personal account for all their work on {% data variables.product.prodname_dotcom_the_website %}, including both open source projects and paid employment. If you're currently using more than one personal account that you created for yourself, we suggest combining the accounts. For more information, see "[Merging multiple personal accounts](/articles/merging-multiple-user-accounts)." {% endif %} -## Contas da organização +## Organization accounts -As organizações são contas partilhadas, onde um número ilimitado de pessoas pode colaborar em muitos projetos de uma só vez. +Organizations are shared accounts where an unlimited number of people can collaborate across many projects at once. -Como as contas pessoais, as organizações podem ter recursos próprios, como repositórios, pacotes e projetos. No entanto, você não pode iniciar sessão em uma organização. Em vez disso, cada pessoa assina sua própria conta pessoal e todas as ações que a pessoa toma sobre os recursos da organização são atribuídas à sua conta pessoal. Cada conta pessoal pode ser um integrante de múltiplas organizações. +Like personal accounts, organizations can own resources such as repositories, packages, and projects. However, you cannot sign into an organization. Instead, each person signs into their own personal account, and any actions the person takes on organization resources are attributed to their personal account. Each personal account can be a member of multiple organizations. -As contas pessoais dentro de uma organização podem receber diferentes funções na organização, que concedem diferentes níveis de acesso à organização e aos seus dados. Todos os integrantes podem colaborar entre si em repositórios e projetos, mas apenas os proprietários da organização e os gerentes de segurança podem gerenciar as configurações da organização e controlar o acesso aos dados da organização, com funcionalidades administrativas e de segurança sofisticadas. Para obter mais informações, confira "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" e "[Como manter sua organização segura](/organizations/keeping-your-organization-secure)". +The personal accounts within an organization can be given different roles in the organization, which grant different levels of access to the organization and its data. All members can collaborate with each other in repositories and projects, but only organization owners and security managers can manage the settings for the organization and control access to the organization's data with sophisticated security and administrative features. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" and "[Keeping your organization secure](/organizations/keeping-your-organization-secure)." -![Diagrama mostrando que os usuários devem efetuar o login na sua conta pessoal para acessar os recursos de uma organização](/assets/images/help/overview/sign-in-pattern.png) +![Diagram showing that users must sign in to their personal account to access an organization's resources](/assets/images/help/overview/sign-in-pattern.png) -{% ifversion fpt or ghec %} Mesmo que você seja membro de uma organização que usa o logon único do SAML, você ainda entrará na sua conta pessoal no {% data variables.product.prodname_dotcom_the_website %}, e essa conta pessoal será vinculada à sua identidade no IdP (provedor de identidade) da sua organização. Para obter mais informações, confira "[Sobre a autenticação com o logon único do SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}" na documentação do {% data variables.product.prodname_ghe_cloud %}{% else %}".{% endif %} +{% ifversion fpt or ghec %} +Even if you're a member of an organization that uses SAML single sign-on, you will still sign into your own personal account on {% data variables.product.prodname_dotcom_the_website %}, and that personal account will be linked to your identity in your organization's identity provider (IdP). For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation{% else %}."{% endif %} -No entanto, se você for integrante de uma empresa que usa {% data variables.product.prodname_emus %}, em vez de usar uma conta pessoal que você criou, uma nova conta será provisionada para você pelo IdP da empresa. Para acessar qualquer organização pertencente a essa empresa, você deverá efetuar a autenticação usando o IdP ao invés de um nome de usuário e senha de {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, confira "[Sobre os {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" na documentação do {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %} {% endif %} +However, if you're a member of an enterprise that uses {% data variables.product.prodname_emus %}, instead of using a personal account that you created, a new account will be provisioned for you by the enterprise's IdP. To access any organizations owned by that enterprise, you must authenticate using their IdP instead of a {% data variables.product.prodname_dotcom_the_website %} username and password. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} +{% endif %} -Você também pode criar subgrupos aninhados de integrantes da organização denominados equipes para refletir a estrutura do seu grupo e simplificar o gerenciamento de acesso. Para obter mais informações, confira "[Sobre as equipes](/organizations/organizing-members-into-teams/about-teams)". +You can also create nested sub-groups of organization members called teams, to reflect your group's structure and simplify access management. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)." {% data reusables.organizations.organization-plans %} -Para obter mais informações sobre todos os recursos das organizações, confira "[Sobre as organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)". +For more information about all the features of organizations, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." -## Conta corporativa +## Enterprise accounts -{% ifversion fpt %} O {% data variables.product.prodname_ghe_cloud %} e o {% data variables.product.prodname_ghe_server %} incluem contas corporativas, que permitem que os administradores gerenciem centralmente a política e a cobrança de várias organizações e habilitem o innersourcing entre as organizações. Para obter mais informações, confira "[Sobre as contas corporativas](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)" na documentação do {% data variables.product.prodname_ghe_cloud %}. -{% elsif ghec %} As contas corporativas permitem o gerenciamento de política central e a cobrança de várias organizações. Você pode usar a conta corporativa para gerenciar centralmente a política e a cobrança. Ao contrário das organizações, as contas corporativas não podem ter recursos próprios, como repositórios, pacotes ou projetos. Esses recursos são propriedade de organizações dentro da conta corporativa. Para obter mais informações, confira "[Sobre as contas corporativas](/admin/overview/about-enterprise-accounts)". -{% elsif ghes or ghae %} Sua conta corporativa é uma coleção de todas as organizações {% ifversion ghae %}pertencentes a{% elsif ghes %}no{% endif %} {% data variables.product.product_location %}. Você pode usar a conta corporativa para gerenciar centralmente a política e a cobrança. Ao contrário das organizações, as contas corporativas não podem ter recursos próprios, como repositórios, pacotes ou projetos. Esses recursos são propriedade de organizações dentro da conta corporativa. Para obter mais informações, confira "[Sobre as contas corporativas](/admin/overview/about-enterprise-accounts)". +{% ifversion fpt %} +{% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} include enterprise accounts, which allow administrators to centrally manage policy and billing for multiple organizations and enable innersourcing between the organizations. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)" in the {% data variables.product.prodname_ghe_cloud %} documentation. +{% elsif ghec %} +Enterprise accounts allow central policy management and billing for multiple organizations. You can use your enterprise account to centrally manage policy and billing. Unlike organizations, enterprise accounts cannot directly own resources like repositories, packages, or projects. These resources are owned by organizations within the enterprise account instead. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)." +{% elsif ghes or ghae %} +Your enterprise account is a collection of all the organizations {% ifversion ghae %}owned by{% elsif ghes %}on{% endif %} {% data variables.location.product_location %}. You can use your enterprise account to centrally manage policy and billing. Unlike organizations, enterprise accounts cannot directly own resources like repositories, packages, or projects. These resources are owned by organizations within the enterprise account instead. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)." {% endif %} -## Leitura adicional +## Further reading {% ifversion fpt or ghec %} -- "[Como se inscrever em uma nova conta do {% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account)"{% endif %} -- "[Como criar uma conta de organização](/articles/creating-a-new-organization-account)" -- Vídeo [Como organizar pessoas para uma colaboração de sucesso](https://vimeo.com/333786093) em Recursos do {% data variables.product.company_short %} +- "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)"{% endif %} +- "[Creating a new organization account](/articles/creating-a-new-organization-account)" +- [Organizing people for successful collaboration](https://vimeo.com/333786093) video in {% data variables.product.company_short %} Resources diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md index 8982dce7c7..0717b20b76 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md @@ -1,88 +1,83 @@ --- -title: Introdução ao GitHub AE -intro: 'Comece a configurar {% data variables.product.product_name %} para {% data variables.product.product_location %}.' +title: Getting started with GitHub AE +intro: 'Get started with setting up and configuring {% data variables.product.product_name %} for {% data variables.location.product_location %}.' versions: ghae: '*' -ms.openlocfilehash: e83b868b6cd204b7a96f40b7287c017eec90096f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147389968' --- -Este guia irá ajudar você a configurar e gerenciar as configurações para {% data variables.product.product_location %} em {% data variables.product.product_name %} como proprietário corporativo. Para saber mais sobre o {% data variables.product.product_name %}, confira "[Sobre o {% data variables.product.prodname_ghe_managed %}](/admin/overview/about-github-ae)". -## Parte 1: Configurando {% data variables.product.product_name %} -Para dar os primeiros passos com {% data variables.product.product_name %}, você pode criar a conta corporativa, inicializar {% data variables.product.product_name %}, configurar uma lista de permissões de IP, configurar a autenticação e provisionamento de usuário e gerenciar a cobrança para {% data variables.product.product_location %}. +This guide will walk you through setting up, configuring, and managing settings for {% data variables.location.product_location %} on {% data variables.product.product_name %} as an enterprise owner. For more information about {% data variables.product.product_name %}, see "[About {% data variables.product.prodname_ghe_managed %}](/admin/overview/about-github-ae)." -### 1. Como criar sua conta corporativa do {% data variables.product.product_name %} -Primeiro você precisará comprar {% data variables.product.product_name %}. Para obter mais informações, entre em contato com a [equipe de Vendas do {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact). +## Part 1: Setting up {% data variables.product.product_name %} +To get started with {% data variables.product.product_name %}, you can create your enterprise account, initialize {% data variables.product.product_name %}, configure an IP allow list, configure user authentication and provisioning, and manage billing for {% data variables.location.product_location %}. + +### 1. Creating your {% data variables.product.product_name %} enterprise account +You will first need to purchase {% data variables.product.product_name %}. For more information, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). {% data reusables.github-ae.initialize-enterprise %} -### 2. Como inicializar o {% data variables.product.product_name %} -Depois de {% data variables.product.company_short %} criar a conta do proprietário para {% data variables.product.product_location %} em {% data variables.product.product_name %}, você receberá um e-mail para efetuar o login e e concluir a inicialização. Durante a inicialização, você, como o proprietário da empresa, irá nomear {% data variables.product.product_location %}, configurar o SAML SSO, criar políticas para todas as organizações em {% data variables.product.product_location %} e configurar um contato de suporte para os integrantes da empresa. Para obter mais informações, confira "[Como inicializar o {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)". +### 2. Initializing {% data variables.product.product_name %} +After {% data variables.product.company_short %} creates the owner account for {% data variables.location.product_location %} on {% data variables.product.product_name %}, you will receive an email to sign in and complete the initialization. During initialization, you, as the enterprise owner, will name {% data variables.location.product_location %}, configure SAML SSO, create policies for all organizations in {% data variables.location.product_location %}, and configure a support contact for your enterprise members. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)." -### 3. Como restringir o tráfego de rede -É possível configurar uma lista de permissões para endereços IP específicos para restringir o acesso a ativos pertencentes a organizações na sua conta corporativa. Para obter mais informações, confira "[Como restringir o tráfego de rede para sua empresa](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)". +### 3. Restricting network traffic +You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)." -### 4. Como gerenciar a identidade e o acesso do {% data variables.product.product_location %} -Você pode gerenciar centralmente o acesso a {% data variables.product.product_location %} em {% data variables.product.product_name %} a partir de um provedor de identidade (IdP) usando o logon único SAML (SSO) para autenticação de usuário e o sistema para gerenciamento de identidade de domínio cruzado (SCIM) para provisionamento de usuários. Depois de configurar o provisionamento, você poderá atribuir ou remover usuários para o aplicativo a partir do IdP, criando ou desabilitando as contas de usuários na empresa. Para obter mais informações, confira "[Sobre o gerenciamento de identidades e acesso da sua empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)". +### 4. Managing identity and access for {% data variables.location.product_location %} +You can centrally manage access to {% data variables.location.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. For more information, see "[About identity and access management for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)." -### 5. Como gerenciar a cobrança do {% data variables.product.product_location %} -Os proprietários da assinatura de {% data variables.product.product_location %} em {% data variables.product.product_name %} podem ver informações de cobrança para {% data variables.product.product_name %} no portal do Azure. Para obter mais informações, confira "[Como gerenciar a cobrança para sua empresa](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)". +### 5. Managing billing for {% data variables.location.product_location %} +Owners of the subscription for {% data variables.location.product_location %} on {% data variables.product.product_name %} can view billing details for {% data variables.product.product_name %} in the Azure portal. For more information, see "[Managing billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)." -## Parte 2: Organização e gestão dos integrantes da empresa -Como proprietário corporativo de {% data variables.product.product_name %}, você pode gerenciar as configurações nos níveis do usuário, repositório, equipe e organização. Você pode gerenciar os integrantes de {% data variables.product.product_location %}, criar e gerenciar organizações, definir políticas para o gerenciamento do repositório e criar e gerenciar equipes. +## Part 2: Organizing and managing enterprise members +As an enterprise owner for {% data variables.product.product_name %}, you can manage settings on user, repository, team, and organization levels. You can manage members of {% data variables.location.product_location %}, create and manage organizations, set policies for repository management, and create and manage teams. -### 1. Como gerenciar membros do {% data variables.product.product_location %} +### 1. Managing members of {% data variables.location.product_location %} {% data reusables.getting-started.managing-enterprise-members %} -### 2. Como criar organizações +### 2. Creating organizations {% data reusables.getting-started.creating-organizations %} -### 3. Como adicionar membros a organizações +### 3. Adding members to organizations {% data reusables.getting-started.adding-members-to-organizations %} -### 4. Como criar equipes +### 4. Creating teams {% data reusables.getting-started.creating-teams %} -### 5. Como definir níveis de permissões para a organização e para o repositório +### 5. Setting organization and repository permission levels {% data reusables.getting-started.setting-org-and-repo-permissions %} -### 6. Como impor políticas de gerenciamento do repositório +### 6. Enforcing repository management policies {% data reusables.getting-started.enforcing-repo-management-policies %} -## Parte 3: Criando com segurança -Para aumentar a segurança de {% data variables.product.product_location %}, você pode monitorar {% data variables.product.product_location %} e configurar as funcionalidades de segurança e análise das suas organizações. +## Part 3: Building securely +To increase the security of {% data variables.location.product_location %}, you can monitor {% data variables.location.product_location %} and configure security and analysis features for your organizations. -### 1. Como monitorar o {% data variables.product.product_location %} -Você pode monitorar {% data variables.product.product_location %} com o seu painel de atividade e log de auditoria. Para obter mais informações, confira "[Como monitorar a atividade na sua empresa](/admin/monitoring-activity-in-your-enterprise)". +### 1. Monitoring {% data variables.location.product_location %} +You can monitor {% data variables.location.product_location %} with your activity dashboard and audit logging. For more information, see "[Monitoring activity in your enterprise](/admin/monitoring-activity-in-your-enterprise)." -### 2. Como configurar os recursos de segurança para suas organizações +### 2. Configuring security features for your organizations {% data reusables.getting-started.configuring-security-features %} -## Parte 4: Personalizando e automatizando o trabalho em {% data variables.product.product_location %} -Você pode personalizar e automatizar o trabalho em organizações em {% data variables.product.product_location %} com a API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, {% data variables.product.prodname_actions %} e {% data variables.product.prodname_pages %}. +## Part 4: Customizing and automating work on {% data variables.location.product_location %} +You can customize and automate work in organizations in {% data variables.location.product_location %} with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, and {% data variables.product.prodname_pages %}. -### 1. Como usar a API do {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} +### 1. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API {% data reusables.getting-started.api %} -### 2. Como criar {% data variables.product.prodname_actions %} +### 2. Building {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -Para obter mais informações sobre como habilitar e configurar o {% data variables.product.prodname_actions %} para o {% data variables.product.product_name %}, confira "[Introdução ao {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)". +For more information on enabling and configuring {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)." -### 3. Como usar o {% data variables.product.prodname_pages %} +### 3. Using {% data variables.product.prodname_pages %} {% data reusables.getting-started.github-pages-enterprise %} -## Parte 5: Usando o aprendizado de {% data variables.product.prodname_dotcom %} e os recursos de suporte -Os integrantes da sua empresa podem aprender mais sobre Git e {% data variables.product.prodname_dotcom %} com nossos recursos de aprendizado. e você pode obter o suporte de que precisa com o Suporte do Enterprise de {% data variables.product.prodname_dotcom %}. +## Part 5: Using {% data variables.product.prodname_dotcom %}'s learning and support resources +Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need with {% data variables.product.prodname_dotcom %} Enterprise Support. -### 1. Leitura sobre o {% data variables.product.product_name %} no {% data variables.product.prodname_docs %} -Você pode ler a documentação que reflete as funcionalidades disponíveis com {% data variables.product.prodname_ghe_managed %}. Para obter mais informações, confira "[Sobre as versões do {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)". +### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %} +You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_managed %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." -### 2. Aprendizagem com o {% data variables.product.prodname_learning %} +### 2. Learning with {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning-enterprise %} -### 3. Como trabalhar com o Suporte Enterprise do {% data variables.product.prodname_dotcom %} +### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support {% data reusables.getting-started.contact-support-enterprise %} diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index f325a7abe5..8d918c17ca 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -1,223 +1,218 @@ --- -title: Introdução ao GitHub Enterprise Cloud -intro: 'Comece a criar e gerenciar sua organização ou conta corporativa de {% data variables.product.prodname_ghe_cloud %}.' +title: Getting started with GitHub Enterprise Cloud +intro: 'Get started with setting up and managing your {% data variables.product.prodname_ghe_cloud %} organization or enterprise account.' versions: fpt: '*' ghec: '*' -ms.openlocfilehash: 249c89ad65bf9a9fc0140b8fb48e7bd0530ff594 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147389960' --- -Este guia irá ajudar você a configurar e gerenciar sua conta de {% data variables.product.prodname_ghe_cloud %} como uma organização ou proprietário da empresa. + +This guide will walk you through setting up, configuring and managing your {% data variables.product.prodname_ghe_cloud %} account as an organization or enterprise owner. {% data reusables.enterprise.ghec-cta-button %} -## Parte 1: Escolhendo o seu tipo de conta +## Part 1: Choosing your account type -{% data variables.product.prodname_dotcom %} fornece dois tipos de produtos corporativos: +{% data variables.product.prodname_dotcom %} provides two types of Enterprise products: - **{% data variables.product.prodname_ghe_cloud %}** - **{% data variables.product.prodname_ghe_server %}** -A principal diferença entre os produtos é que {% data variables.product.prodname_ghe_cloud %} é hospedado por {% data variables.product.prodname_dotcom %}, enquanto {% data variables.product.prodname_ghe_server %} é auto-hospedado. +The main difference between the products is that {% data variables.product.prodname_ghe_cloud %} is hosted by {% data variables.product.prodname_dotcom %}, while {% data variables.product.prodname_ghe_server %} is self-hosted. {% data reusables.enterprise.about-github-for-enterprises %} -Com {% data variables.product.prodname_ghe_cloud %}, você tem a opção de usar {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %} +With {% data variables.product.prodname_ghe_cloud %}, you have the option of using {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %} -Você optar por deixar seus integrantes criarem e gerenciarem suas próprias contas pessoais, há dois tipos de contas que você pode usar com {% data variables.product.prodname_ghe_cloud %}: +If you choose to let your members create and manage their own personal accounts instead, there are two types of accounts you can use with {% data variables.product.prodname_ghe_cloud %}: -- Uma conta de organização única -- Uma conta corporativa que contém várias organizações +- A single organization account +- An enterprise account that contains multiple organizations -### 1. Compreensão das diferenças entre uma conta de organização e uma conta corporativa +### 1. Understanding the differences between an organization account and enterprise account -As contas da organização e da empresa estão disponíveis com {% data variables.product.prodname_ghe_cloud %}. Uma organização é uma conta compartilhada em que grupos de pessoas podem colaborar em vários projetos de uma só vez, e os proprietários e administradores podem gerenciar o acesso a dados e projetos. Uma conta corporativa permite a colaboração entre várias organizações e permite que os proprietários gerenciem centralmente a política, cobrança e segurança dessas organizações. Para obter mais informações sobre as diferenças, confira "[Organizações e contas corporativas](/organizations/collaborating-with-groups-in-organizations/about-organizations#organizations-and-enterprise-accounts)". +Both organization and enterprise accounts are available with {% data variables.product.prodname_ghe_cloud %}. An organization is a shared account where groups of people can collaborate across many projects at once, and owners and administrators can manage access to data and projects. An enterprise account enables collaboration between multiple organizations, and allows owners to centrally manage policy, billing and security for these organizations. For more information on the differences, see "[Organizations and enterprise accounts](/organizations/collaborating-with-groups-in-organizations/about-organizations#organizations-and-enterprise-accounts)." -Se você escolher uma conta corporativa, tenha em mente que algumas políticas só podem ser definidas no nível organizacional, enquanto outras podem ser aplicadas a todas as organizações de uma empresa. +If you choose an enterprise account, keep in mind that some policies can be set only at an organization level, while others can be enforced for all organizations in an enterprise. -Depois de escolher o tipo de conta que você desejar, você poderá continuar a criar a sua conta. Em cada uma das seções deste guia, acesse a seção de organização única ou conta corporativa com base no seu tipo de conta. +Once you choose the account type you would like, you can proceed to setting up your account. In each of the sections in this guide, proceed to either the single organization or enterprise account section based on your account type. -## Parte 2: Configurando a sua conta -Para começar com {% data variables.product.prodname_ghe_cloud %}, você deverá criar sua conta organizativa ou corporativa e configurar e ver as configurações de cobrança, assinaturas e uso. -### Como criar uma conta de organização única com {% data variables.product.prodname_ghe_cloud %} +## Part 2: Setting up your account +To get started with {% data variables.product.prodname_ghe_cloud %}, you will want to create your organization or enterprise account and set up and view billing settings, subscriptions and usage. +### Setting up a single organization account with {% data variables.product.prodname_ghe_cloud %} -#### 1. Sobre as organizações -As organizações são contas compartilhadas, onde grupos de pessoas podem colaborar em vários projetos de uma vez. Com o {% data variables.product.prodname_ghe_cloud %}, os proprietários e administradores podem gerenciar sua organização com autenticação e gestão de usuário sofisticada, bem como com opções de segurança e suporte escaladas. Para obter mais informações, confira "[Sobre as organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)". -#### 2. Como criar ou atualizar a conta de uma organização +#### 1. About organizations +Organizations are shared accounts where groups of people can collaborate across many projects at once. With {% data variables.product.prodname_ghe_cloud %}, owners and administrators can manage their organization with sophisticated user authentication and management, as well as escalated support and security options. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." +#### 2. Creating or upgrading an organization account -Para usar a conta de uma organização com {% data variables.product.prodname_ghe_cloud %}, primeiro você precisará criar uma organização. Quando solicitado para escolher um plano, selecione "Enterprise". Para obter mais informações, confira "[Como criar uma organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". +To use an organization account with {% data variables.product.prodname_ghe_cloud %}, you will first need to create an organization. When prompted to choose a plan, select "Enterprise". For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." -Como alternativa, se você tiver uma conta de organização existente que deseja atualizar, siga as etapas descritas em "[Como atualizar sua assinatura do {% data variables.product.prodname_dotcom %}](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)". -#### 3. Configuração e gerenciamento de cobrança +Alternatively, if you have an existing organization account that you would like to upgrade, follow the steps in "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)." +#### 3. Setting up and managing billing -Ao optar por usar uma conta de organização com o {% data variables.product.prodname_ghe_cloud %}, primeiro, você terá acesso a uma [avaliação de 30 dias](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud). Se você não comprar {% data variables.product.prodname_enterprise %} ou {% data variables.product.prodname_team %} antes do seu período de teste terminar, a sua organização será rebaixada para {% data variables.product.prodname_free_user %} e você perderá acesso a quaisquer ferramentas avançadas e recursos que sejam incluídos apenas com produtos pagos. Para obter mais informações, confira "[Término da avaliação](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)". +When you choose to use an organization account with {% data variables.product.prodname_ghe_cloud %}, you'll first have access to a [30-day trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud). If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_user %} and lose access to any advanced tooling and features that are only included with paid products. For more information, see "[Finishing your trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)." -A página de configurações de cobrança da sua organização permite que você gerencie configurações como seu método de pagamento e ciclo de cobrança, exiba informações sobre sua assinatura e faça a atualização do seu armazenamento e minutos de {% data variables.product.prodname_actions %}. Para obter mais informações sobre como gerenciar as configurações de cobrança, confira "[Como gerenciar as configurações de cobrança do {% data variables.product.prodname_dotcom %}](/billing/managing-your-github-billing-settings)". +Your organization's billing settings page allows you to manage settings like your payment method and billing cycle, view information about your subscription, and upgrade your storage and {% data variables.product.prodname_actions %} minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)." -Apenas os membros da organização com a função *proprietário* ou *gerente de cobrança* podem acessar ou alterar as configurações de cobrança da sua organização. Um gerente de cobrança é um usuário que gerencia as configurações de cobrança para sua organização e não usa uma licença paga na assinatura da sua organização. Para obter mais informações sobre como adicionar um gerente de cobrança à sua organização, confira "[Como adicionar um gerente de cobrança à sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)". +Only organization members with the *owner* or *billing manager* role can access or change billing settings for your organization. A billing manager is a user who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)." -### Configurando uma conta corporativa com {% data variables.product.prodname_ghe_cloud %} +### Setting up an enterprise account with {% data variables.product.prodname_ghe_cloud %} -#### 1. Sobre as contas corporativas +#### 1. About enterprise accounts -Uma conta corporativa permite que você gerencie centralmente as políticas e configurações para várias organizações {% data variables.product.prodname_dotcom %}, incluindo acesso de integrantes, cobrança e uso e segurança. Para obter mais informações, confira "[Sobre as contas corporativas](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)". +An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)." -#### 2. Como criar uma conta empresarial +#### 2. Creating an enterpise account - Os clientes do {% data variables.product.prodname_ghe_cloud %} que pagam por fatura podem criar uma conta empresarial diretamente com o {% data variables.product.prodname_dotcom %}. Para obter mais informações, confira "[Com criar uma conta empresarial](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)". + {% data variables.product.prodname_ghe_cloud %} customers paying by invoice can create an enterprise account directly through {% data variables.product.prodname_dotcom %}. For more information, see "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)." - Os clientes do {% data variables.product.prodname_ghe_cloud %} que não pagam por fatura podem entrar em contato com a [equipe de vendas do {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact) para criar uma conta empresarial para você. + {% data variables.product.prodname_ghe_cloud %} customers not currently paying by invoice can contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact) to create an enterprise account for you. -#### 3. Como adicionar organizações à conta empresarial +#### 3. Adding organizations to your enterprise account -É possível criar novas organizações para serem gerenciadas em sua conta corporativa. Para obter mais informações, confira "[Como adicionar organizações à sua empresa](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)". +You can create new organizations to manage within your enterprise account. For more information, see "[Adding organizations to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)." -Entre em contato com o seu representante da conta de vendas de {% data variables.product.prodname_dotcom %} se você quiser transferir uma organização existente para a sua conta corporativa. -#### 4. Como ver a assinatura e o uso da conta empresarial -Você pode visualizar a sua assinatura atual, uso da licença, faturas, histórico de pagamentos e outras informações de cobrança para sua conta corporativa a qualquer momento. Os proprietários da empresa e os gerentes de cobrança podem acessar e gerenciar as configurações de cobrança para contas corporativas. Para obter mais informações, confira "[Como ver a assinatura e o uso da sua conta corporativa](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)". +Contact your {% data variables.product.prodname_dotcom %} sales account representative if you want to transfer an existing organization to your enterprise account. +#### 4. Viewing the subscription and usage for your enterprise account +You can view your current subscription, license usage, invoices, payment history, and other billing information for your enterprise account at any time. Both enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Viewing the subscription and usage for your enterprise account](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)." -## Parte 3: Gerenciando seus integrantes e equipes da empresa com {% data variables.product.prodname_ghe_cloud %} +## Part 3: Managing your organization or enterprise members and teams with {% data variables.product.prodname_ghe_cloud %} -### Gerenciando integrantes e equipes na sua organização -Você pode definir permissões e funções dos integrantes, criar e gerenciar equipes e conceder acesso a repositórios na sua organização. -#### 1. Como gerenciar os membros da sua organização +### Managing members and teams in your organization +You can set permissions and member roles, create and manage teams, and give people access to repositories in your organization. +#### 1. Managing members of your organization {% data reusables.getting-started.managing-org-members %} -#### 2. Permissões e funções da organização +#### 2. Organization permissions and roles {% data reusables.getting-started.org-permissions-and-roles %} -#### 3. Sobre as equipes e como criá-las +#### 3. About and creating teams {% data reusables.getting-started.about-and-creating-teams %} -#### 4. Como gerenciar as configurações da equipe +#### 4. Managing team settings {% data reusables.getting-started.managing-team-settings %} -#### 5. Como fornecer às pessoas e às equipes acesso a repositórios, quadros de projetos e aplicativos +#### 5. Giving people and teams access to repositories, project boards and apps {% data reusables.getting-started.giving-access-to-repositories-projects-apps %} -### Gerenciando integrantes de uma conta corporativa -O gerenciamento dos integrantes de uma empresa é separado da gestão dos integrantes ou equipes em uma organização. É importante notar que os proprietários ou administradores da empresa não podem acessar as configurações a nível da organização ou gerenciar integrantes de organizações na sua empresa, a não ser que sejam proprietários de uma organização. Para obter mais informações, confira a seção acima: "[Como gerenciar membros e equipes na sua organização](#managing-members-and-teams-in-your-organization)". +### Managing members of an enterprise account +Managing members of an enterprise is separate from managing members or teams in an organization. It is important to note that enterprise owners or administrators cannot access organization-level settings or manage members for organizations in their enterprise unless they are made an organization owner. For more information, see the above section, "[Managing members and teams in your organization](#managing-members-and-teams-in-your-organization)." -Se sua empresa usar {% data variables.product.prodname_emus %}, seus integrantes serão totalmente gerenciados por meio de seu provedor de identidade. As funções de adicionar integrantes, fazer alterações na sua associação e atribuir cargos são geranciadas usando seu IdP. Para obter mais informações, confira "[Sobre as {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)". +If your enterprise uses {% data variables.product.prodname_emus %}, your members are fully managed through your identity provider. Adding members, making changes to their membership, and assigning roles is all managed using your IdP. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." -Se a sua empresa não usar {% data variables.product.prodname_emus %}, siga as etapas abaixo. +If your enterprise does not use {% data variables.product.prodname_emus %}, follow the steps below. -#### 1. Como atribuir funções em uma empresa -Por padrão, todas as pessoas em uma empresa são integrantes da empresa. Além disso, há funções administrativas, que incluem o proprietário da empresa e o gerente de cobrança, que têm diferentes níveis de acesso às configurações e dados da empresa. Para obter mais informações, confira "[Funções em uma empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)". -#### 2. Como convidar pessoas para gerenciar sua empresa -Você pode convidar pessoas para gerenciar a sua empresa como, por exemplo, proprietários corporativos ou gerentes de cobrança, bem como remover aqueles que não precisam mais de acesso. Para obter mais informações, confira "[Como convidar pessoas para gerenciar sua empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)". +#### 1. Assigning roles in an enterprise +By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. For more information, see "[Roles in an enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)." +#### 2. Inviting people to manage your enterprise +You can invite people to manage your enterprise as enterprise owners or billing managers, as well as remove those who no longer need access. For more information, see "[Inviting people to manage your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)." -Você também pode conceder aos integrandes da empresa a capacidade de gerenciar tíquetes de suporte no portal de suporte. Para obter mais informações, confira "[Como gerenciar os direitos de suporte para sua empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)". -#### 3. Como ver os funcionários da sua empresa -Para auditoria ao acesso a recursos pertencentes à empresa ou ao uso da licença de usuário, você pode ver todos os administradores corporativos, integrantes da empresa e colaboradores externos da sua empresa. Você pode ver as organizações às quais um integrante pertence e os repositórios específicos aos quais um colaborador externo tem acesso. Para obter mais informações, confira "[Como ver os funcionários da sua empresa](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)". +You can also grant enterprise members the ability to manage support tickets in the support portal. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)." +#### 3. Viewing people in your enterprise +To audit access to enterprise-owned resources or user license usage, you can view every enterprise administrator, enterprise member, and outside collaborator in your enterprise. You can see the organizations that a member belongs to and the specific repositories that an outside collaborator has access to. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)." -## Parte 4: Gerenciando a segurança com {% data variables.product.prodname_ghe_cloud %} +## Part 4: Managing security with {% data variables.product.prodname_ghe_cloud %} -* [Como gerenciar a segurança de uma organização individual](#managing-security-for-a-single-organization) -* [Como gerenciar a segurança de uma {% data variables.product.prodname_emu_enterprise %}](#managing-security-for-an-enterprise-with-managed-users) -* [Como gerenciar a segurança de uma conta corporativa sem {% data variables.product.prodname_managed_users %}](#managing-security-for-an-enterprise-account-without-managed-users) +* [Managing security for a single organization](#managing-security-for-a-single-organization) +* [Managing security for an {% data variables.enterprise.prodname_emu_enterprise %}](#managing-security-for-an-enterprise-with-managed-users) +* [Managing security for an enterprise account without {% data variables.enterprise.prodname_managed_users %}](#managing-security-for-an-enterprise-account-without-managed-users) -### Gerenciando a segurança de uma única organização -Você pode ajudar a manter sua organização segura exigindo autenticação de dois fatores, configurando recursos de segurança, revisando o log de auditoria e as integrações da sua organização e habilitando a sincronização de equipe e logon único SAML. -#### 1. Como exigir a autenticação de dois fatores +### Managing security for a single organization +You can help keep your organization secure by requiring two-factor authentication, configuring security features, reviewing your organization's audit log and integrations, and enabling SAML single sign-on and team synchronization. +#### 1. Requiring two-factor authentication {% data reusables.getting-started.requiring-2fa %} -#### 2. Como configurar recursos de segurança para sua organização +#### 2. Configuring security features for your organization {% data reusables.getting-started.configuring-security-features %} -#### 3. Como revisar o log de auditoria e as integrações da sua organização +#### 3. Reviewing your organization's audit log and integrations {% data reusables.getting-started.reviewing-org-audit-log-and-integrations %} -#### 4. Como habilitar e impor o logon único do SAML para sua organização -Se você gerenciar seus aplicativos e as identidades dos integrantes da sua organização com um provedor de identidade (IdP), você poderá configurar logon único SAML (SSO) para controlar e proteger o acesso aos recursos da organização, como repositórios, problemas e pull requests. Quando os integrantes da sua organização acessam os recursos da organização que usam o SAML SSO, {% data variables.product.prodname_dotcom %} irá redirecioná-los para o seu dispositivo para autenticação. Para obter mais informações, confira "[Sobre o gerenciamento de identidades e acesso com o logon único do SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)". +#### 4. Enabling and enforcing SAML single sign-on for your organization +If you manage your applications and the identities of your organization members with an identity provider (IdP), you can configure SAML single-sign-on (SSO) to control and secure access to organization resources like repositories, issues and pull requests. When members of your organization access organization resources that use SAML SSO, {% data variables.product.prodname_dotcom %} will redirect them to your IdP to authenticate. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." -Os proprietários da organização podem optar por habilitar e desabilitar, mas não implementar, habilitar e aplicar o SAML SSO. Para obter mais informações, confira "[Como habilitar e testar o logon único do SAML para sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)" e "[Como impor o logon único do SAML para sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)". -#### 5. Como gerenciar a sincronização da equipe para sua organização -Os proprietários da organização podem habilitar a sincronização de equipes entre o seu provedor de identidade (IdP) e {% data variables.product.prodname_dotcom %} para permitir que os proprietários da organização e mantenedores de equipes conectem equipes na sua organização aos grupos do IdP. Para obter mais informações, confira "[Como gerenciar a sincronização da equipe para sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)". +Organization owners can choose to disable, enable but not enforce, or enable and enforce SAML SSO. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)" and "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)." +#### 5. Managing team synchronization for your organization +Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)." -### Gerenciando a segurança de {% data variables.product.prodname_emu_enterprise %} +### Managing security for an {% data variables.enterprise.prodname_emu_enterprise %} -Com {% data variables.product.prodname_emus %}, o acesso e a identidade são gerenciados centralmente por meio do seu provedor de identidade. A autenticação de dois fatores e outros requisitos de login devem ser habilitados e aplicados no seu IdP. +With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP. -#### 1. Como habilitar o logon único do SAML e o provisionamento na sua {% data variables.product.prodname_emu_enterprise %} +#### 1. Enabling and SAML single sign-on and provisioning in your {% data variables.enterprise.prodname_emu_enterprise %} -Em um {% data variables.product.prodname_emu_enterprise %}, todos os integrantes são provisionados e gerenciados pelo seu provedor de identidade. Você deve habilitar o provisionamento SAML SSO e SCIM antes de começar a usar a sua empresa. Para obter mais informações sobre como configurar o SSO do SAML e o provisionamento para uma {% data variables.product.prodname_emu_enterprise %}, confira "[Como configurar o logon único do SAML para Usuários Gerenciados Enterprise](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)". +In an {% data variables.enterprise.prodname_emu_enterprise %}, all members are provisioned and managed by your identity provider. You must enable SAML SSO and SCIM provisioning before you can start using your enterprise. For more information on configuring SAML SSO and provisioning for an {% data variables.enterprise.prodname_emu_enterprise %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." -#### 2. Como gerenciar equipes na sua {% data variables.product.prodname_emu_enterprise %} com o provedor de identidade +#### 2. Managing teams in your {% data variables.enterprise.prodname_emu_enterprise %} with your identity provider -Você pode conectar as equipes das suas organizações a grupos de segurança do seu provedor de identidade, gerenciar integrantes das suas equipes e acesso aos repositórios por meio do seu IdP. Para obter mais informações, confira "[Como gerenciar associações à equipe com grupos de provedores de identidade](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)". +You can connect teams in your organizations to security groups in your identity provider, managing membership of your teams and access to repositories through your IdP. For more information, see "[Managing team memberships with identity provider groups](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." -#### 3. Como gerenciar os endereços IP permitidos para organizações na sua {% data variables.product.prodname_emu_enterprise %} +#### 3. Managing allowed IP addresses for organizations in your {% data variables.enterprise.prodname_emu_enterprise %} -Você pode configurar uma lista de permissões para endereços IP específicos para restringir o acesso a ativos pertencentes a organizações no seu {% data variables.product.prodname_emu_enterprise %}. Para obter mais informações, confira "[Como impor políticas para configurações de segurança na sua empresa](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)". +You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your {% data variables.enterprise.prodname_emu_enterprise %}. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)." -#### 4. Como impor políticas para recursos do Advanced Security na sua {% data variables.product.prodname_emu_enterprise %} +#### 4. Enforcing policies for Advanced Security features in your {% data variables.enterprise.prodname_emu_enterprise %} {% data reusables.getting-started.enterprise-advanced-security %} -### Gerenciando a segurança de uma conta corporativa sem {% data variables.product.prodname_managed_users %} -Para gerenciar a segurança da sua empresa, você pode exigir autenticação de dois fatores, gerenciar endereços IP permitidos, habilitar o logon único SAML e a sincronização de equipes no nível corporativo e inscrever-se aplicar as funcionalidades do GitHub Advanced Security. +### Managing security for an enterprise account without {% data variables.enterprise.prodname_managed_users %} +To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features. -#### 1. Como exigir a autenticação de dois fatores e gerenciar os endereços IP permitidos para organizações na sua conta corporativa -Os proprietários corporativos podem exigir que integrantes da organização, gerentes de cobrança e colaboradores externos em todas as organizações pertencentes a uma conta corporativa usem autenticação de dois fatores para proteger suas contas pessoais. Antes de fazer isso, recomendamos que você notifique todas as pessoas que têm acesso a organizações da sua empresa. Você também pode configurar uma lista de permissões para endereços IP específicos para restringir o acesso a ativos pertencentes a organizações na sua conta corporativa. +#### 1. Requiring two-factor authentication and managing allowed IP addresses for organizations in your enterprise account +Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise account use two-factor authentication to secure their personal accounts. Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. -Para obter mais informações sobre como impor a autenticação de dois fatores e as listas de endereços IP permitidos, confira "[Como impor políticas para configurações de segurança na sua empresa](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)". -#### 2. Como habilitar e impor o logon único do SAML para organizações na sua conta corporativa -Você pode gerenciar centralmente o acesso aos recursos da sua empresa, a associação à organização e a associação à equipe usando seu IdP e o logon único SAML (SSO). Os proprietários corporativos podem habilitar o SAML SSO em todas as organizações pertencentes a uma conta corporativa. Para obter mais informações, confira "[Sobre o gerenciamento de identidades e acesso da sua empresa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)". +For more information on enforcing two-factor authentication and allowed IP address lists, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)." +#### 2. Enabling and enforcing SAML single sign-on for organizations in your enterprise account +You can centrally manage access to your enterprise's resources, organization membership and team membership using your IdP and SAM single sign-on (SSO). Enterprise owners can enable SAML SSO across all organizations owned by an enterprise account. For more information, see "[About identity and access management for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)." -#### 3. Como gerenciar a sincronização da equipe -Você pode habilitar e gerenciar a simulação de equipes entre um provedor de identidade (IdP) e {% data variables.product.prodname_dotcom %} para permitir que as organizações pertencentes à sua conta corporativa gerenciem a associação de equipes com grupos IdP. Para obter mais informações, confira "[Como gerenciar a sincronização da equipe para organizações na sua conta corporativa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)". +#### 3. Managing team synchronization +You can enable and manage team synchronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. For more information, see "[Managing team synchronization for organizations in your enterprise account](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)." -#### 4. Como impor políticas para recursos do Advanced Security na sua conta corporativa +#### 4. Enforcing policies for Advanced Security features in your enterprise account {% data reusables.getting-started.enterprise-advanced-security %} -## Parte 5: Gerenciar políticas e configurações da organização e do nível empresarial +## Part 5: Managing organization and enterprise level policies and settings -### Gerenciando configurações para uma única organização -Para gerenciar e moderar sua organização, você pode definir políticas da organização, gerenciar permissões para alterações de repositórios e usar arquivos de saúde da comunidade no nível da organização. -#### 1. Como gerenciar as políticas da organização +### Managing settings for a single organization +To manage and moderate your organization, you can set organization policies, manage permissions for repository changes, and use organization-level community health files. +#### 1. Managing organization policies {% data reusables.getting-started.managing-org-policies %} -#### 2. Como gerenciar as alterações do repositório +#### 2. Managing repository changes {% data reusables.getting-started.managing-repo-changes %} -#### 3. Como usar os arquivos de integridade da comunidade na organização e as ferramentas de moderação +#### 3. Using organization-level community health files and moderation tools {% data reusables.getting-started.using-org-community-files-and-moderation-tools %} -### Gerenciando as configurações para uma conta corporativa -Para gerenciar e moderar sua empresa, você pode definir políticas para organizações dentro da empresa, visualizar logs de auditoria, configurar webhooks e restringir notificações de e-mail. -#### 1. Como gerenciar políticas para organizações na sua conta corporativa +### Managing settings for an enterprise account +To manage and moderate your enterprise, you can set policies for organizations within the enterprise, view audit logs, configure webhooks, and restrict email notifications. +#### 1. Managing policies for organizations in your enterprise account -Você pode optar por aplicar várias políticas para todas as organizações pertencentes à sua empresa, ou escolher permitir que essas políticas sejam definidas em cada organização. Os tipos de políticas que você pode aplicar incluem gerenciamento de repositórios, quadro de projetos e políticas de equipe. Para obter mais informações, confira "[Como definir políticas para sua empresa](/enterprise-cloud@latest/admin/policies)". -#### 2. Como exibir logs de auditoria, configurar webhooks e restringir notificações por email para sua empresa -Você pode visualizar as ações de todas as organizações pertencentes à sua conta corporativa no log de auditoria da empresa. Você também pode configurar webhooks para receber eventos de organizações pertencentes à sua conta corporativa. Para obter mais informações, confira "[Como revisar os logs de auditoria da sua empresa](/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)" e "[Como monitorar sua empresa](/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise)". +You can choose to enforce a number of policies for all organizations owned by your enterprise, or choose to allow these policies to be set in each organization. Types of policies you can enforce include repository management, project board, and team policies. For more information, see "[Setting policies for your enterprise](/enterprise-cloud@latest/admin/policies)." +#### 2. Viewing audit logs, configuring webhooks, and restricting email notifications for your enterprise +You can view actions from all of the organizations owned by your enterprise account in the enterprise audit log. You can also configure webhooks to receive events from organizations owned by your enterprise account. For more information, see "[Reviewing audit logs for your enterprise](/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)" and "[Monitoring your enterprise](/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise)." -Você também pode restringir as notificações de e-mail da conta corporativa para que os integrantes da empresa só possam usar um endereço de e-mail em um domínio verificado ou aprovado para receber notificações. Para obter mais informações, confira "[Como restringir notificações por email para sua empresa](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)". +You can also restrict email notifications for your enterprise account so that enterprise members can only use an email address in a verified or approved domain to receive notifications. For more information, see "[Restricting email notifications for your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)." -## Parte 6: Personalizar e automatizar o trabalho da sua organização ou empresa em {% data variables.product.prodname_dotcom %} -Os integrantes da sua organização ou empresa podem usar ferramentas a partir da API de {% data variables.product.prodname_marketplace %}, a {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} e das funcionalidades de {% data variables.product.product_name %} existentes para personalizar e automatizar seu trabalho. +## Part 6: Customizing and automating your organization or enterprise's work on {% data variables.product.prodname_dotcom %} +Members of your organization or enterprise can use tools from the {% data variables.product.prodname_marketplace %}, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, and existing {% data variables.product.product_name %} features to customize and automate your work. -### 1. Como usar o {% data variables.product.prodname_marketplace %} +### 1. Using {% data variables.product.prodname_marketplace %} {% data reusables.getting-started.marketplace %} -### 2. Como usar a API do {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} +### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API {% data reusables.getting-started.api %} -### 3. Como criar {% data variables.product.prodname_actions %} +### 3. Building {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -### 4. Como publicar e gerenciar o {% data variables.product.prodname_registry %} +### 4. Publishing and managing {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} -### 5. Como usar o {% data variables.product.prodname_pages %} -O {% data variables.product.prodname_pages %} é um serviço de hospedagem de site estático que usa arquivos HTML, CSS e JavaScript diretamente de um repositório e publica um site. Você pode gerenciar a publicação de sites de {% data variables.product.prodname_pages %} no nível da organização. Para obter mais informações, confira "[Como gerenciar a publicação de sites do {% data variables.product.prodname_pages %} para sua organização](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" e "[Sobre o {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)". -## Parte 7: Participando da comunidade de {% data variables.product.prodname_dotcom %} +### 5. Using {% data variables.product.prodname_pages %} +{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository and publishes a website. You can manage the publication of {% data variables.product.prodname_pages %} sites at the organization level. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" and "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)." +## Part 7: Participating in {% data variables.product.prodname_dotcom %}'s community -Os integrantes da sua organização ou empresa podem usar os recursos de aprendizado e suporte do GitHub para obter a ajuda de que precisam. Você também pode apoiar a comunidade de código aberto. +Members of your organization or enterprise can use GitHub's learning and support resources to get the help they need. You can also support the open source community. -### 1. Leitura sobre o {% data variables.product.prodname_ghe_cloud %} no {% data variables.product.prodname_docs %} -Você pode ler a documentação que reflete as funcionalidades disponíveis com {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, confira "[Sobre as versões do {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)". +### 1. Reading about {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_docs %} +You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." -### 2. Aprendizagem com o {% data variables.product.prodname_learning %} -Os membros da sua organização ou da sua empresa podem aprender novas habilidades realizando projetos divertidos e realistas no seu repositório do GitHub com o [{% data variables.product.prodname_learning %}](https://skills.github.com/). Cada curso é uma lição prática criada pela comunidade do GitHub e ensinada por um bot amigável. +### 2. Learning with {% data variables.product.prodname_learning %} +Members of your organization or enterprise can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://skills.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by a friendly bot. -Para obter mais informações, confira "[Git e recursos de aprendizagem do {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)". -### 3. Como apoiar a comunidade de código aberto +For more information, see "[Git and {% data variables.product.prodname_dotcom %} learning resources](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)." +### 3. Supporting the open source community {% data reusables.getting-started.sponsors %} -### 4. Como entrar em contato com o {% data variables.contact.github_support %} +### 4. Contacting {% data variables.contact.github_support %} {% data reusables.getting-started.contact-support %} -{% data variables.product.prodname_ghe_cloud %} permite que você envie solicitações de suporte prioritárias com um tempo de resposta de oito horas. Para obter mais informações, confira "[Suporte do {% data variables.product.prodname_ghe_cloud %}](/github/working-with-github-support/github-enterprise-cloud-support)". +{% data variables.product.prodname_ghe_cloud %} allows you to submit priority support requests with a target eight-hour response time. For more information, see "[{% data variables.product.prodname_ghe_cloud %} support](/github/working-with-github-support/github-enterprise-cloud-support)." diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md index f48288b3fe..5f749b66af 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md @@ -1,130 +1,126 @@ --- -title: Introdução ao GitHub Enterprise Server -intro: 'Comece a configurar e gerenciar {% data variables.product.product_location %}.' +title: Getting started with GitHub Enterprise Server +intro: 'Get started with setting up and managing {% data variables.location.product_location %}.' versions: ghes: '*' -ms.openlocfilehash: 01ed16fd08a57e96270ed1cc577784ba52a15dbf -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146454266' --- -Este guia irá ajudar você a configurar e gerenciar {% data variables.product.product_location %} como administrador da empresa. -{% data variables.product.company_short %} oferece duas maneiras de implantar {% data variables.product.prodname_enterprise %}. +This guide will walk you through setting up, configuring and managing {% data variables.location.product_location %} as an enterprise administrator. + +{% data variables.product.company_short %} provides two ways to deploy {% data variables.product.prodname_enterprise %}. - **{% data variables.product.prodname_ghe_cloud %}** - **{% data variables.product.prodname_ghe_server %}** -{% data variables.product.company_short %} hospeda {% data variables.product.prodname_ghe_cloud %}. Você pode implantar e hospedar {% data variables.product.prodname_ghe_server %} no seu próprio centro de dados ou em um provedor da nuvem compatível. +{% data variables.product.company_short %} hosts {% data variables.product.prodname_ghe_cloud %}. You can deploy and host {% data variables.product.prodname_ghe_server %} in your own datacenter or a supported cloud provider. -Para obter mais informações sobre o {% data variables.product.product_name %}, confira "[Sobre o {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server)". +For more information about {% data variables.product.product_name %}, see "[About {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server)." -## Parte 1: Como instalar o {% data variables.product.product_name %} -Para começar com {% data variables.product.product_name %}, você deverá criar a conta corporativa, instalar a instância, usar o Console de Gerenciamento para configuração inicial, configurar a sua instância e gerenciar a cobrança. -### 1. Como criar sua conta corporativa -Antes de instalar o {% data variables.product.product_name %}, você pode criar uma conta corporativa no {% data variables.product.prodname_dotcom_the_website %} entrando em contato com a [equipe de vendas do {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact). Uma conta corporativa em {% data variables.product.prodname_dotcom_the_website %} é útil para a cobrança e para recursos compartilhados com o {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}. Para obter mais informações, confira "[Sobre as contas corporativas](/admin/overview/about-enterprise-accounts)". -### 2. Como instalar o {% data variables.product.product_name %} -Para começar com {% data variables.product.product_name %}, você deverá instalar o dispositivo em uma plataforma de virtualização de sua escolha. Para obter mais informações, confira "[Como configurar uma instância do {% data variables.product.prodname_ghe_server %}](/admin/installation/setting-up-a-github-enterprise-server-instance)". +## Part 1: Installing {% data variables.product.product_name %} +To get started with {% data variables.product.product_name %}, you will need to create your enterprise account, install the instance, use the Management Console for initial setup, configure your instance, and manage billing. +### 1. Creating your enterprise account +Before you install {% data variables.product.product_name %}, you can create an enterprise account on {% data variables.product.prodname_dotcom_the_website %} by contacting [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). An enterprise account on {% data variables.product.prodname_dotcom_the_website %} is useful for billing and for shared features with {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)." +### 2. Installing {% data variables.product.product_name %} +To get started with {% data variables.product.product_name %}, you will need to install the appliance on a virtualization platform of your choice. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)." -### 3. Como usar o Console de Gerenciamento -Você usará o Console de Gerenciamento para apresentar o processo de configuração inicial ao iniciar {% data variables.product.product_location %}. Você também pode usar o Console de Gerenciamento para gerenciar configurações de instância, como licença, domínio, autenticação e TLS. Para obter mais informações, confira "[Como acessar o console de gerenciamento](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)". +### 3. Using the Management Console +You will use the Management Console to walk through the initial setup process when first launching {% data variables.location.product_location %}. You can also use the Management Console to manage instance settings such as the license, domain, authentication, and TLS. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)." -### 4. Como configurar o {% data variables.product.product_location %} -Além do console de gerenciamento, você pode usar o painel de administração do site e o shell administrativo (SSH) para gerenciar {% data variables.product.product_location %}. Por exemplo, você pode configurar aplicativos e limites de taxa, ver relatórios, usar utilitários de linha de comando. Para obter mais informações, confira "[Como configurar sua empresa](/admin/configuration/configuring-your-enterprise)". +### 4. Configuring {% data variables.location.product_location %} +In addition to the Management Console, you can use the site admin dashboard and the administrative shell (SSH) to manage {% data variables.location.product_location %}. For example, you can configure applications and rate limits, view reports, use command-line utilities. For more information, see "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)." -Você pode usar as configurações de rede padrão usadas por {% data variables.product.product_name %} por meio do protocolo de configuração do host dinâmico (DHCP) ou você também pode definir as configurações de rede usando o console de máquina virtual. Você também pode configurar um servidor proxy ou regras de firewall. Para obter mais informações, confira "[Como definir as configurações de rede](/admin/configuration/configuring-network-settings)". +You can use the default network settings used by {% data variables.product.product_name %} via the dynamic host configuration protocol (DHCP), or you can also configure the network settings using the virtual machine console. You can also configure a proxy server or firewall rules. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)." -### 5. Como configurar a alta disponibilidade -Você pode configurar {% data variables.product.product_location %} para alta disponibilidade a fim de minimizar o impacto de falhas de hardware e falhas de rede. Para obter mais informações, confira "[Como configurar a alta disponibilidade](/admin/enterprise-management/configuring-high-availability)". +### 5. Configuring high availability +You can configure {% data variables.location.product_location %} for high availability to minimize the impact of hardware failures and network outages. For more information, see "[Configuring high availability](/admin/enterprise-management/configuring-high-availability)." -### 6. Como configurar uma instância de preparo -Você pode configurar uma instância de preparo para testar modificações, planejar a recuperação de desastres e testar atualizações antes de aplicá-las a {% data variables.product.product_location %}. Para obter mais informações, confira "[Como configurar uma instância de preparo](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)". +### 6. Setting up a staging instance +You can set up a staging instance to test modifications, plan for disaster recovery, and try out updates before applying them to {% data variables.location.product_location %}. For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)." -### 7. Como designar backups e recuperação de desastre -Para proteger seus dados de produção, você pode configurar backups automatizados de {% data variables.product.product_location %} com {% data variables.product.prodname_enterprise_backup_utilities %}. Para obter mais informações, confira "[Como configurar backups no seu dispositivo](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)". +### 7. Designating backups and disaster recovery +To protect your production data, you can configure automated backups of {% data variables.location.product_location %} with {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)." -### 8. Como gerenciar a cobrança para sua empresa -A cobrança para todas as organizações e instâncias de {% data variables.product.product_name %} conectadas à sua conta corporativa é agregada em uma única taxa de cobrança para todos os seus serviços pagos de {% data variables.product.prodname_dotcom %}.com. Proprietários corporativos e gerentes de cobrança podem acessar e gerenciar as configurações de cobrança relativas a contas corporativas. Para obter mais informações, confira "[Como gerenciar a cobrança para sua empresa](/admin/overview/managing-billing-for-your-enterprise)". +### 8. Managing billing for your enterprise +Billing for all the organizations and {% data variables.product.product_name %} instances connected to your enterprise account is aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom %}.com services. Enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." -## Parte 2: Organização e gerenciamento da sua equipe -Como proprietário corporativo ou administrador, você pode gerenciar configurações em níveis de usuário, repositório, equipe e organização. É possível gerenciar os integrantes da sua empresa, criar e gerenciar organizações, definir políticas para a gestão do repositório e criar e gerenciar as equipes. +## Part 2: Organizing and managing your team +As an enterprise owner or administrator, you can manage settings on user, repository, team and organization levels. You can manage members of your enterprise, create and manage organizations, set policies for repository management, and create and manage teams. -### 1. Como gerenciar membros do {% data variables.product.product_location %} +### 1. Managing members of {% data variables.location.product_location %} {% data reusables.getting-started.managing-enterprise-members %} -### 2. Como criar organizações +### 2. Creating organizations {% data reusables.getting-started.creating-organizations %} -### 3. Como adicionar membros a organizações +### 3. Adding members to organizations {% data reusables.getting-started.adding-members-to-organizations %} -### 4. Como criar equipes +### 4. Creating teams {% data reusables.getting-started.creating-teams %} -### 5. Como definir níveis de permissões para a organização e para o repositório +### 5. Setting organization and repository permission levels {% data reusables.getting-started.setting-org-and-repo-permissions %} -### 6. Como impor políticas de gerenciamento do repositório +### 6. Enforcing repository management policies {% data reusables.getting-started.enforcing-repo-management-policies %} -## Parte 3: Criando com segurança -Para aumentar a segurança de {% data variables.product.product_location %}, você pode configurar a autenticação para integrantes da empresa, usar ferramentas e registro de auditoria para manter a conformidade, configurar recursos de segurança e análise para as suas organizações e, opcionalmente, habilitar {% data variables.product.prodname_GH_advanced_security %}. -### 1. Como autenticar os membros da empresa -Você pode usar o método de autenticação interno do {% data variables.product.product_name %} ou você pode escolher entre um provedor de autenticação externo como o CAS, LDAP, ou SAML, para integrar suas contas existentes e gerenciar centralmente o acesso do usuário ao {% data variables.product.product_location %}. Para obter mais informações, confira "[Sobre a autenticação em sua empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)". +## Part 3: Building securely +To increase the security of {% data variables.location.product_location %}, you can configure authentication for enterprise members, use tools and audit logging to stay in compliance, configure security and analysis features for your organizations, and optionally enable {% data variables.product.prodname_GH_advanced_security %}. +### 1. Authenticating enterprise members +You can use {% data variables.product.product_name %}'s built-in authentication method, or you can choose between an external authentication provider, such as CAS, LDAP, or SAML, to integrate your existing accounts and centrally manage user access to {% data variables.location.product_location %}. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)." -Você também pode exigir autenticação de dois fatores para cada uma de suas organizações. Para obter mais informações, confira "[Como exigir a autenticação de dois fatores para uma organização](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)". +You can also require two-factor authentication for each of your organizations. For more information, see "[Requiring two factor authentication for an organization](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)." -### 2. Como manter a conformidade -Você pode implementar verificações de status necessárias e realizar verificações de commit para fazer cumprir os padrões de conformidade da sua organização e automatizar os fluxos de trabalho de conformidade. Você também pode usar o log de auditoria para sua organização revisar as ações executadas pela sua equipe. Para obter mais informações, confira "[Impor uma política com ganchos de pré-recebimento](/admin/policies/enforcing-policy-with-pre-receive-hooks)" e "[Sobre o log de auditoria da sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)". +### 2. Staying in compliance +You can implement required status checks and commit verifications to enforce your organization's compliance standards and automate compliance workflows. You can also use the audit log for your organization to review actions performed by your team. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)" and "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)." {% ifversion ghes %} -### 3. Como configurar os recursos de segurança para suas organizações -{% data reusables.getting-started.configuring-security-features %} {% endif %} - -{% ifversion ghes %} -### 4. Como habilitar recursos do {% data variables.product.prodname_GH_advanced_security %} -Você pode atualizar sua licença do {% data variables.product.product_name %} para incluir {% data variables.product.prodname_GH_advanced_security %}. Isso fornece funcionalidades extras que ajudam os usuários a encontrar e corrigir problemas de segurança no seu código como, por exemplo, digitalização de código e segredo. Para obter mais informações, confira "[{% data variables.product.prodname_GH_advanced_security %} para sua empresa](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)". +### 3. Configuring security features for your organizations +{% data reusables.getting-started.configuring-security-features %} {% endif %} -## Parte 4: Personalizando e automatizando o trabalho da sua empresa em {% data variables.product.prodname_dotcom %} -Você pode personalizar e automatizar o trabalho em organizações na sua empresa com a API de {% data variables.product.prodname_dotcom %} e {% data variables.product.prodname_oauth_apps %}, {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} e {% data variables.product.prodname_pages %}. +{% ifversion ghes %} +### 4. Enabling {% data variables.product.prodname_GH_advanced_security %} features +You can upgrade your {% data variables.product.product_name %} license to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code, such as code and secret scanning. For more information, see "[{% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)." +{% endif %} -### 1. Como criar {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %} -Você pode criar integrações com a API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} como, por exemplo, {% data variables.product.prodname_github_apps %} ou {% data variables.product.prodname_oauth_apps %}, para uso em organizações da empresa para complementar e ampliar seus fluxos de trabalho. Para obter mais informações, confira "[Sobre os aplicativos](/developers/apps/getting-started-with-apps/about-apps)". -### 2. Como usar a API do {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} +## Part 4: Customizing and automating your enterprise's work on {% data variables.product.prodname_dotcom %} +You can customize and automate work in organizations in your enterprise with {% data variables.product.prodname_dotcom %} and {% data variables.product.prodname_oauth_apps %}, {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} , and {% data variables.product.prodname_pages %}. + +### 1. Building {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} +You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)." +### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API {% data reusables.getting-started.api %} {% ifversion ghes %} -### 3. Como criar {% data variables.product.prodname_actions %} +### 3. Building {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -Para obter mais informações sobre como habilitar e configurar o {% data variables.product.prodname_actions %} no {% data variables.product.product_name %}, confira "[Introdução ao {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)". +For more information on enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)." -### 4. Como publicar e gerenciar o {% data variables.product.prodname_registry %} +### 4. Publishing and managing {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} -Para obter mais informações sobre como habilitar e configurar o {% data variables.product.prodname_registry %} para o {% data variables.product.product_location %}, confira "[Introdução ao {% data variables.product.prodname_registry %} para sua empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)". +For more information on enabling and configuring {% data variables.product.prodname_registry %} for {% data variables.location.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." {% endif %} -### 5. Como usar o {% data variables.product.prodname_pages %} +### 5. Using {% data variables.product.prodname_pages %} {% data reusables.getting-started.github-pages-enterprise %} -## Parte 5: Conectando com outros recursos de {% data variables.product.prodname_dotcom %} -Você pode usar {% data variables.product.prodname_github_connect %} para compartilhar recursos. +## Part 5: Connecting with other {% data variables.product.prodname_dotcom %} resources +You can use {% data variables.product.prodname_github_connect %} to share resources. -Se você for o proprietário de uma instância de {% data variables.product.product_name %} e uma organização ou conta corporativa de {% data variables.product.prodname_ghe_cloud %}, você poderá habilitar {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} permite que você compartilhe fluxos de trabalho específicos e recursos entre {% data variables.product.product_location %} e {% data variables.product.prodname_ghe_cloud %}, como pesquisa unificada e contribuições. Para obter mais informações, confira "[Como conectar o {% data variables.product.prodname_ghe_server %} ao {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)". +If you are the owner of both a {% data variables.product.product_name %} instance and a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account, you can enable {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} allows you to share specific workflows and features between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %}, such as unified search and contributions. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)." -## Parte 6: Usando o aprendizado de {% data variables.product.prodname_dotcom %} e o suporte recursos -Os membros da sua empresa podem aprender mais sobre o Git e {% data variables.product.prodname_dotcom %} com os nossos recursos de aprendizagem. e você pode obter o suporte de que precisa ao configurar e gerenciar {% data variables.product.product_location %} com o suporte do enterprise de {% data variables.product.prodname_dotcom %}. +## Part 6: Using {% data variables.product.prodname_dotcom %}'s learning and support resources +Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need when setting up and managing {% data variables.location.product_location %} with {% data variables.product.prodname_dotcom %} Enterprise Support. -### 1. Leitura sobre o {% data variables.product.product_name %} no {% data variables.product.prodname_docs %} +### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %} -Você pode ler a documentação que reflete as funcionalidades disponíveis com {% data variables.product.prodname_ghe_server %}. Para obter mais informações, confira "[Sobre as versões do {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)". +You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_server %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." -### 2. Aprendizagem com o {% data variables.product.prodname_learning %} +### 2. Learning with {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning-enterprise %} -### 3. Como trabalhar com o Suporte Enterprise do {% data variables.product.prodname_dotcom %} +### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support {% data reusables.getting-started.contact-support-enterprise %} diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md index d7a89269e2..0f9f02a3ef 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md @@ -1,104 +1,99 @@ --- -title: Introdução ao GitHub Team -intro: 'Com grupos de {% data variables.product.prodname_team %}, as pessoas podem colaborar em vários projetos ao mesmo tempo na conta de uma organização.' +title: Getting started with GitHub Team +intro: 'With {% data variables.product.prodname_team %} groups of people can collaborate across many projects at the same time in an organization account.' versions: fpt: '*' -ms.openlocfilehash: 46b5376b72ce30f7c526f693f2adb9253853cf1d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146139157' --- -Este guia irá ajudar você a configurar e gerenciar sua conta {% data variables.product.prodname_team %} como proprietário da organização. -## Parte 1: Configurar sua conta em {% data variables.product.product_location %} -Como primeiros passos para começar com {% data variables.product.prodname_team %}, você deverá criar uma conta pessoal ou entrar na sua conta existente no {% data variables.product.prodname_dotcom %}, criar uma organização e configurar a cobrança. +This guide will walk you through setting up, configuring and managing your {% data variables.product.prodname_team %} account as an organization owner. -### 1. Sobre as organizações -As organizações são contas compartilhadas nas quais as empresas e os projetos de software livre podem colaborar com vários projetos ao mesmo tempo. Os proprietários e os administradores podem gerenciar o acesso de membros aos dados e projetos da organização com recursos administrativos e de segurança sofisticados. Para obter mais informações sobre os recursos das organizações, confira "[Sobre as organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations#terms-of-service-and-data-protection-for-organizations)". +## Part 1: Configuring your account on {% data variables.location.product_location %} +As the first steps in starting with {% data variables.product.prodname_team %}, you will need to create a personal account or log into your existing account on {% data variables.product.prodname_dotcom %}, create an organization, and set up billing. -### 2. Como criar uma organização e se inscrever no {% data variables.product.prodname_team %} -Para criar uma organização, você deverá criar uma conta pessoal ou efetuar o logon na sua conta existente no {% data variables.product.product_location %}. Para obter mais informações, confira "[Como se inscrever em uma nova conta do {% data variables.product.prodname_dotcom %}](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)". +### 1. About organizations +Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features. For more information on the features of organizations, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations#terms-of-service-and-data-protection-for-organizations)." -Uma vez que a sua conta pessoal estiver configurada, você poderá criar uma organização e escolher um plano. Aqui é onde você pode escolher uma assinatura de {% data variables.product.prodname_team %} para a sua organização. Para obter mais informações, confira "[Como criar uma organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". +### 2. Creating an organization and signing up for {% data variables.product.prodname_team %} +Before creating an organization, you will need to create a personal account or log in to your existing account on {% data variables.location.product_location %}. For more information, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)." -### 3. Como gerenciar a cobrança para uma organização -Você deve gerenciar as configurações de cobrança, método de pagamento e produtos pagos para cada uma das suas contas pessoais e organizações separadamente. Você pode alternar entre as configurações para a suas diferentes contas usando o alternador de contexto nas suas configurações. Para obter mais informações, confira "[Como alternar entre as configurações de suas diferentes contas](/billing/managing-your-github-billing-settings/about-billing-on-github#switching-between-settings-for-your-different-accounts)". +Once your personal account is set up, you can create an organization and pick a plan. This is where you can choose a {% data variables.product.prodname_team %} subscription for your organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." -A página de configurações de cobrança da sua organização permite que você gerencie configurações como seu método de pagamento, ciclo de cobrança e e-mail de cobrança, ou visualize informações como a sua assinatura, data de faturamento e histórico de pagamento. Você também pode ver e fazer a atualização do seu armazenamento e dos minutos do GitHub Action. Para obter mais informações sobre como gerenciar as configurações de cobrança, confira "[Como gerenciar as configurações de cobrança do {% data variables.product.prodname_dotcom %}](/billing/managing-your-github-billing-settings)". +### 3. Managing billing for an organization +You must manage billing settings, payment method, and paid features and products for each of your personal accounts and organizations separately. You can switch between settings for your different accounts using the context switcher in your settings. For more information, see "[Switching between settings for your different accounts](/billing/managing-your-github-billing-settings/about-billing-on-github#switching-between-settings-for-your-different-accounts)." -Apenas os membros da organização com a função *proprietário* ou *gerente de cobrança* podem acessar ou alterar as configurações de cobrança da sua organização. Um gerente de cobrança é um usuário que gerencia as configurações de cobrança para sua organização e não usa uma licença paga na assinatura da sua organização. Para obter mais informações sobre como adicionar um gerente de cobrança à sua organização, confira "[Como adicionar um gerente de cobrança à sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)". +Your organization's billing settings page allows you to manage settings like your payment method, billing cycle and billing email, or view information such as your subscription, billing date and payment history. You can also view and upgrade your storage and GitHub Actions minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)." + +Only organization members with the *owner* or *billing manager* role can access or change billing settings for your organization. A billing manager is someone who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)." -## Parte 2: Adicionar integrantes e criar equipes -Depois de criar a sua organização, você poderá convidar integrantes e definir permissões e funções. Você também pode criar diferentes níveis de equipes e definir níveis personalizados de permissões para repositórios da sua organização, quadros de projetos e aplicativos. +## Part 2: Adding members and setting up teams +After creating your organization, you can invite members and set permissions and roles. You can also create different levels of teams and set customized levels of permissions for your organization's repositories, project boards, and apps. -### 1. Como gerenciar os membros da sua organização +### 1. Managing members of your organization {% data reusables.getting-started.managing-org-members %} -### 2. Permissões e funções da organização +### 2. Organization permissions and roles {% data reusables.getting-started.org-permissions-and-roles %} -### 3. Sobre as equipes e como criá-las +### 3. About and creating teams {% data reusables.getting-started.about-and-creating-teams %} -### 4. Como gerenciar as configurações da equipe +### 4. Managing team settings {% data reusables.getting-started.managing-team-settings %} -### 5. Como fornecer às pessoas e às equipes acesso a repositórios, quadros de projetos e aplicativos +### 5. Giving people and teams access to repositories, project boards and apps {% data reusables.getting-started.giving-access-to-repositories-projects-apps %} -## Parte 3: Gerenciando a segurança da sua organização -Você pode ajudar a tornar sua organização mais segura ao recomendar ou exigir a autenticação de dois fatores para os integrantes da sua organização, configurando as funcionalidades de segurança e revisando o log de auditoria e integrações da sua organização. +## Part 3: Managing security for your organization +You can help to make your organization more secure by recommending or requiring two-factor authentication for your organization members, configuring security features, and reviewing your organization's audit log and integrations. -### 1. Como exigir a autenticação de dois fatores +### 1. Requiring two-factor authentication {% data reusables.getting-started.requiring-2fa %} -### 2. Como configurar recursos de segurança para sua organização +### 2. Configuring security features for your organization {% data reusables.getting-started.configuring-security-features %} -### 3. Como revisar o log de auditoria e as integrações da sua organização +### 3. Reviewing your organization's audit log and integrations {% data reusables.getting-started.reviewing-org-audit-log-and-integrations %} -## Parte 4: Definindo as políticas no nível da organização -### 1. Como gerenciar as políticas da organização +## Part 4: Setting organization level policies +### 1. Managing organization policies {% data reusables.getting-started.managing-org-policies %} -### 2. Como gerenciar as alterações do repositório +### 2. Managing repository changes {% data reusables.getting-started.managing-repo-changes %} -### 3. Como usar os arquivos de integridade da comunidade na organização e as ferramentas de moderação +### 3. Using organization-level community health files and moderation tools {% data reusables.getting-started.using-org-community-files-and-moderation-tools %} -## Parte 5: Personalizando e automatizando seu trabalho em {% data variables.product.product_name %} +## Part 5: Customizing and automating your work on {% data variables.product.product_name %} {% data reusables.getting-started.customizing-and-automating %} -### 1. Como usar o {% data variables.product.prodname_marketplace %} +### 1. Using {% data variables.product.prodname_marketplace %} {% data reusables.getting-started.marketplace %} -### 2. Como usar a API do {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} +### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API {% data reusables.getting-started.api %} -### 3. Como criar {% data variables.product.prodname_actions %} +### 3. Building {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -### 4. Como publicar e gerenciar o {% data variables.product.prodname_registry %} +### 4. Publishing and managing {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} -## Parte 6: Participando da comunidade de {% data variables.product.prodname_dotcom %} +## Part 6: Participating in {% data variables.product.prodname_dotcom %}'s community {% data reusables.getting-started.participating-in-community %} -### 1. Como contribuir para projetos de código aberto +### 1. Contributing to open source projects {% data reusables.getting-started.open-source-projects %} -### 2. Como interagir com o {% data variables.product.prodname_gcf %} +### 2. Interacting with the {% data variables.product.prodname_gcf %} {% data reusables.support.ask-and-answer-forum %} -### 3. Leitura sobre o {% data variables.product.prodname_team %} no {% data variables.product.prodname_docs %} -Você pode ler a documentação que reflete as funcionalidades disponíveis com {% data variables.product.prodname_team %}. Para obter mais informações, confira "[Sobre as versões do {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)". +### 3. Reading about {% data variables.product.prodname_team %} on {% data variables.product.prodname_docs %} +You can read documentation that reflects the features available with {% data variables.product.prodname_team %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." -### 4. Aprendizagem com o {% data variables.product.prodname_learning %} +### 4. Learning with {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning %} -### 5. Como apoiar a comunidade de código aberto +### 5. Supporting the open source community {% data reusables.getting-started.sponsors %} -### 6. Como entrar em contato com o {% data variables.contact.github_support %} +### 6. Contacting {% data variables.contact.github_support %} {% data reusables.getting-started.contact-support %} -## Leitura adicional +## Further reading -- "[Introdução à sua conta do GitHub](/get-started/onboarding/getting-started-with-your-github-account)" +- "[Getting started with your GitHub account](/get-started/onboarding/getting-started-with-your-github-account)" diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md index 0ae6850a21..9fe0d1f65c 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md @@ -1,199 +1,203 @@ --- -title: Introdução à sua conta do GitHub -intro: 'Com uma conta pessoal no {% data variables.product.prodname_dotcom %}, você pode importar ou criar repositórios, colaborar com outras pessoas e se conectar com a comunidade do {% data variables.product.prodname_dotcom %}.' +title: Getting started with your GitHub account +intro: 'With a personal account on {% data variables.product.prodname_dotcom %}, you can import or create repositories, collaborate with others, and connect with the {% data variables.product.prodname_dotcom %} community.' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' -ms.openlocfilehash: 38d23c1a1b5021a681aedff8813daad751905d8a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147408913' --- -Este guia descreverá a configuração da sua conta do {% data variables.product.company_short %} e uma introdução aos recursos de colaboração e comunidade do {% data variables.product.product_name %}. -## Parte 1: Configurando sua conta de {% data variables.product.prodname_dotcom %} +This guide will walk you through setting up your {% data variables.product.company_short %} account and getting started with {% data variables.product.product_name %}'s features for collaboration and community. -{% ifversion fpt or ghec %} As primeiras etapas para começar a usar o {% data variables.product.product_name %} são criar uma conta, escolher um produto que se adapte melhor às suas necessidades, confirmar seu email, configurar a autenticação de dois fatores e ver seu perfil. -{% elsif ghes %} As primeiras etapas para começar a usar o {% data variables.product.product_name %} são acessar sua conta, configurar a autenticação de dois fatores e ver seu perfil. -{% elsif ghae %} As primeiras etapas para começar a usar o {% data variables.product.product_name %} são acessar sua conta e ver seu perfil. -{% endif %} - -{% ifversion fpt or ghec %}Há vários tipos de contas no {% data variables.product.prodname_dotcom %}. {% endif %} Toda pessoa que usar {% data variables.product.product_name %} terá sua conta pessoal e poderá fazer parte de várias organizações e equipes. A sua conta pessoal é sua identidade em {% data variables.product.product_location %} e representa você como indivíduo. +## Part 1: Configuring your {% data variables.product.prodname_dotcom %} account {% ifversion fpt or ghec %} -### 1. Como criar uma conta -Para se inscrever em uma conta na {% data variables.product.product_location %}, acesse https://github.com/ e siga os prompts. +The first steps in starting with {% data variables.product.product_name %} are to create an account, choose a product that fits your needs best, verify your email, set up two-factor authentication, and view your profile. +{% elsif ghes %} +The first steps in starting with {% data variables.product.product_name %} are to access your account, set up two-factor authentication, and view your profile. +{% elsif ghae %} +The first steps in starting with {% data variables.product.product_name %} are to access your account and view your profile. +{% endif %} -Para manter a sua conta de {% data variables.product.prodname_dotcom %} segura, você deverá usar uma senha forte e exclusiva. Para obter mais informações, confira "[Como criar uma senha forte](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)". +{% ifversion fpt or ghec %}There are several types of accounts on {% data variables.product.prodname_dotcom %}. {% endif %} Every person who uses {% data variables.product.product_name %} has their own personal account, which can be part of multiple organizations and teams. Your personal account is your identity on {% data variables.location.product_location %} and represents you as an individual. -### 2. Como escolher seu produto do {% data variables.product.prodname_dotcom %} -Você pode escolher {% data variables.product.prodname_free_user %} ou {% data variables.product.prodname_pro %} para obter acesso a diferentes recursos da sua conta pessoal. Você pode fazer a atualização a qualquer momento se não tiver certeza qual o produto você deseja. +{% ifversion fpt or ghec %} +### 1. Creating an account +To sign up for an account on {% data variables.location.product_location %}, navigate to https://github.com/ and follow the prompts. -Para obter mais informações sobre todos os planos do {% data variables.product.prodname_dotcom %}, confira "[Produtos do {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/githubs-products)". +To keep your {% data variables.product.prodname_dotcom %} account secure you should use a strong and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)." -### 3. Como confirmar seu endereço de email -Para garantir que você possa utilizar todos os recursos do seu plano de {% data variables.product.product_name %}, verifique o seu endereço de e-mail após inscrever-se em uma nova conta. Para obter mais informações, confira "[Como confirmar seu endereço de email](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)". +### 2. Choosing your {% data variables.product.prodname_dotcom %} product +You can choose {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %} to get access to different features for your personal account. You can upgrade at any time if you are unsure at first which product you want. + +For more information on all of {% data variables.product.prodname_dotcom %}'s plans, see "[{% data variables.product.prodname_dotcom %}'s products](/get-started/learning-about-github/githubs-products)." + +### 3. Verifying your email address +To ensure you can use all the features in your {% data variables.product.product_name %} plan, verify your email address after signing up for a new account. For more information, see "[Verifying your email address](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)." {% endif %} {% ifversion ghes %} -### 1. Como acessar sua conta -O administrador da sua instância de {% data variables.product.product_name %} irá notificar você sobre como efetuar a autenticação e acessar a sua conta. O processo varia dependendo do modo de autenticação que eles configuraram para a instância. +### 1. Accessing your account +The administrator of your {% data variables.product.product_name %} instance will notify you about how to authenticate and access your account. The process varies depending on the authentication mode they have configured for the instance. {% endif %} {% ifversion ghae %} -### 1. Como acessar sua conta -Você receberá uma notificação por e-mail assim que o proprietário corporativo de {% data variables.product.product_name %} tiver configurado a sua conta permitindo que você efetue a autenticação com o logon único SAML (SSO) e acesse sua conta. +### 1. Accessing your account +You will receive an email notification once your enterprise owner for {% data variables.product.product_name %} has set up your account, allowing you to authenticate with SAML single sign-on (SSO) and access your account. {% endif %} {% ifversion fpt or ghes or ghec %} -### {% ifversion fpt or ghec %}4.{% else %}2.{% endif %} Como configurar a autenticação de dois fatores -A autenticação de dois fatores, ou 2FA, é uma camada extra de segurança usada no logon em sites ou apps. É altamente recomendável que você configure a 2FA para a segurança da sua conta. Para obter mais informações, confira "[Sobre a autenticação de dois fatores](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)". +### {% ifversion fpt or ghec %}4.{% else %}2.{% endif %} Configuring two-factor authentication +Two-factor authentication, or 2FA, is an extra layer of security used when logging into websites or apps. We strongly urge you to configure 2FA for the safety of your account. For more information, see "[About two-factor authentication](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)." {% endif %} -### {% ifversion fpt or ghec %}5.{% elsif ghes %}3.{% else %}2.{% endif %} Como ver seu perfil e seu grafo de contribuição do {% data variables.product.prodname_dotcom %} -Seu perfil do {% data variables.product.prodname_dotcom %} conta às pessoas a história do seu trabalho por meio dos repositórios e dos gists que você fixou, as associações à organização que você optou por divulgar, as contribuições que você fez e os projetos que você criou. Para obter mais informações, confira "[Sobre seu perfil](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile)" e "[Como ver as contribuições no seu perfil](/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile)". +### {% ifversion fpt or ghec %}5.{% elsif ghes %}3.{% else %}2.{% endif %} Viewing your {% data variables.product.prodname_dotcom %} profile and contribution graph +Your {% data variables.product.prodname_dotcom %} profile tells people the story of your work through the repositories and gists you've pinned, the organization memberships you've chosen to publicize, the contributions you've made, and the projects you've created. For more information, see "[About your profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile)" and "[Viewing contributions on your profile](/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile)." -## Parte 2: Usando ferramentas e processos de {% data variables.product.product_name %} -Para usar {% data variables.product.product_name %} da melhor forma, você deverá configurar o Git. O Git é responsável por tudo relacionado ao {% data variables.product.prodname_dotcom %} que acontece localmente no computador. Para colaborar de forma efetiva em {% data variables.product.product_name %}, você escreverá em problemas e pull requests usando o Markdown enriquecido de {% data variables.product.prodname_dotcom %}. +## Part 2: Using {% data variables.product.product_name %}'s tools and processes +To best use {% data variables.product.product_name %}, you'll need to set up Git. Git is responsible for everything {% data variables.product.prodname_dotcom %}-related that happens locally on your computer. To effectively collaborate on {% data variables.product.product_name %}, you'll write in issues and pull requests using {% data variables.product.prodname_dotcom %} Flavored Markdown. -### 1. Como aprender a usar o Git -A abordagem colaborativa do {% data variables.product.prodname_dotcom %} para o desenvolvimento depende da publicação dos commits do repositório local para {% data variables.product.product_name %} para que outras pessoas vejam, busquem e atualizem outras pessoas que usam o Git. Para obter mais informações sobre o Git, confira o guia "[Manual do Git](https://guides.github.com/introduction/git-handbook/)". Para obter mais informações sobre como o Git é usado no {% data variables.product.product_name %}, confira "[Fluxo do {% data variables.product.prodname_dotcom %}](/get-started/quickstart/github-flow)". -### 2. Como configurar o Git -Se você planeja usar o Git localmente no seu computador, por meio da linha de comando, editor de IDE ou texto, você deverá instalar e configurar o Git. Para obter mais informações, confira "[Configurar o Git](/get-started/quickstart/set-up-git)". +### 1. Learning Git +{% data variables.product.prodname_dotcom %}'s collaborative approach to development depends on publishing commits from your local repository to {% data variables.product.product_name %} for other people to view, fetch, and update using Git. For more information about Git, see the "[Git Handbook](https://guides.github.com/introduction/git-handbook/)" guide. For more information about how Git is used on {% data variables.product.product_name %}, see "[{% data variables.product.prodname_dotcom %} flow](/get-started/quickstart/github-flow)." +### 2. Setting up Git +If you plan to use Git locally on your computer, whether through the command line, an IDE or text editor, you will need to install and set up Git. For more information, see "[Set up Git](/get-started/quickstart/set-up-git)." -Se você preferir usar uma interface visual, você poderá fazer o download e usar {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} vem empacotado com o Git. Portanto não há a necessidade de instalar o Git separadamente. Para obter mais informações, confira "[Introdução ao {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)". +If you prefer to use a visual interface, you can download and use {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} comes packaged with Git, so there is no need to install Git separately. For more information, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)." -Depois de instalar o Git, você poderá conectar-se aos repositórios de {% data variables.product.product_name %} a partir do seu computador local, independentemente de ser o seu próprio repositório ou a bifurcação de outro usuário. Ao conectar-se a a um repositório no {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} do Git, você deveá efetuar a autenticação com {% data variables.product.product_name %} usando HTTPS ou SSH. Para obter mais informações, confira "[Sobre os repositórios remotos](/get-started/getting-started-with-git/about-remote-repositories)". +Once you install Git, you can connect to {% data variables.product.product_name %} repositories from your local computer, whether your own repository or another user's fork. When you connect to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} from Git, you'll need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH. For more information, see "[About remote repositories](/get-started/getting-started-with-git/about-remote-repositories)." -### 3. Como escolher como interagir com o {% data variables.product.product_name %} -Todos têm seu próprio fluxo de trabalho único para interagir com {% data variables.product.prodname_dotcom %}; as interfaces e métodos que você usa dependem da sua preferência e do que funciona melhor para as suas necessidades. +### 3. Choosing how to interact with {% data variables.product.product_name %} +Everyone has their own unique workflow for interacting with {% data variables.product.prodname_dotcom %}; the interfaces and methods you use depend on your preference and what works best for your needs. -Para obter mais informações sobre como se autenticar no {% data variables.product.product_name %} com cada um desses métodos, confira "[Sobre a autenticação no {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github)". +For more information about how to authenticate to {% data variables.product.product_name %} with each of these methods, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github)." -| **Método** | **Descrição** | **Casos de uso** | +| **Method** | **Description** | **Use cases** | | ------------- | ------------- | ------------- | -| Acesse {% data variables.product.prodname_dotcom_the_website %} | Se você não precisar trabalhar com arquivos localmente, {% data variables.product.product_name %} permite que você realize a maioria das ações relacionadas ao Gits diretamente no navegador, da criação e bifurcação de repositórios até a edição de arquivos e abertura de pull requests.| Esse método é útil se você quiser uma interface visual e precisar fazer mudanças rápidas e simples que não requerem trabalho local. | -| {% data variables.product.prodname_desktop %} | O {% data variables.product.prodname_desktop %} amplia e simplifica o fluxo de trabalho no {% data variables.product.prodname_dotcom_the_website %} com uma interface visual, em vez de comandos de texto na linha de comando. Para obter mais informações sobre como começar a usar o {% data variables.product.prodname_desktop %}, confira "[Introdução ao {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)". | Este método é melhor se você precisa ou deseja trabalhar com arquivos localmente, mas preferir usar uma interface visual para usar o Git e interagir com {% data variables.product.product_name %}. | -| Editor de IDE ou de texto | Você pode definir um editor de texto padrão, como o [Atom](https://atom.io/) ou o [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/), para abrir e editar seus arquivos com o Git, usar extensões e ver a estrutura do projeto. Para obter mais informações, confira "[Como associar editores de texto ao Git](/github/using-git/associating-text-editors-with-git)". | Isto é conveniente se você estiver trabalhando com arquivos e projetos mais complexos e quiser ter tudo em um só lugar, uma vez que os editores de texto ou IDEs muitas vezes permitem que você acesse diretamente a linha de comando no editor. | -| Linha de comando, com ou sem {% data variables.product.prodname_cli %} | Para o controle e personalização mais granulares de como você usa o Git e interage com {% data variables.product.product_name %}, você pode usar a linha de comando. Para obter mais informações sobre como usar comandos do Git, confira "[Folha de referências do Git](/github/getting-started-with-github/quickstart/git-cheatsheet)".

A {% data variables.product.prodname_cli %} é uma ferramenta de linha de comando separada que pode ser instalada para exibir solicitações de pull, problemas, {% data variables.product.prodname_actions %} e outros recursos do {% data variables.product.prodname_dotcom %} no terminal, para que você possa fazer todo o seu trabalho em um só lugar. Para obter mais informações, confira "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)". | Isto é muito conveniente se você já estiver trabalhando na linha de comando, o que permite que você evite mudar o contexto, ou se você estiver mais confortável usando a linha de comando. | -| {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} tem uma API REST e uma API do GraphQL que você pode usar para interagir com {% data variables.product.product_name %}. Para obter mais informações, confira "[Introdução à API](/github/extending-github/getting-started-with-the-api)". | A API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} seria muito útil se você quisesse automatizar tarefas comuns, fazer backup dos seus dados ou criar integrações que estendem {% data variables.product.prodname_dotcom %}. | -### 4. Gravação no {% data variables.product.product_name %} -Para deixar sua comunicação clara e organizada nos problemas e pull requests, você pode usar o Markdown enriquecido {% data variables.product.prodname_dotcom %} para formatação, que combina uma sintaxe fácil de ler e fácil de escrever com algumas funcionalidades personalizadas. Para obter mais informações, confira "[Sobre a gravação e a formatação no {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)". +| Browse to {% data variables.product.prodname_dotcom_the_website %} | If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete most Git-related actions directly in the browser, from creating and forking repositories to editing files and opening pull requests.| This method is useful if you want a visual interface and need to do quick, simple changes that don't require working locally. | +| {% data variables.product.prodname_desktop %} | {% data variables.product.prodname_desktop %} extends and simplifies your {% data variables.product.prodname_dotcom_the_website %} workflow, using a visual interface instead of text commands on the command line. For more information on getting started with {% data variables.product.prodname_desktop %}, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)." | This method is best if you need or want to work with files locally, but prefer using a visual interface to use Git and interact with {% data variables.product.product_name %}. | +| IDE or text editor | You can set a default text editor like [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. For more information, see "[Associating text editors with Git](/github/using-git/associating-text-editors-with-git)." | This is convenient if you are working with more complex files and projects and want everything in one place, since text editors or IDEs often allow you to directly access the command line in the editor. | +| Command line, with or without {% data variables.product.prodname_cli %} | For the most granular control and customization of how you use Git and interact with {% data variables.product.product_name %}, you can use the command line. For more information on using Git commands, see "[Git cheatsheet](/github/getting-started-with-github/quickstart/git-cheatsheet)."

{% data variables.product.prodname_cli %} is a separate command-line tool you can install that brings pull requests, issues, {% data variables.product.prodname_actions %}, and other {% data variables.product.prodname_dotcom %} features to your terminal, so you can do all your work in one place. For more information, see "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)." | This is most convenient if you are already working from the command line, allowing you to avoid switching context, or if you are more comfortable using the command line. | +| {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} has a REST API and GraphQL API that you can use to interact with {% data variables.product.product_name %}. For more information, see "[Getting started with the API](/github/extending-github/getting-started-with-the-api)." | The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API would be most helpful if you wanted to automate common tasks, back up your data, or create integrations that extend {% data variables.product.prodname_dotcom %}. | +### 4. Writing on {% data variables.product.product_name %} +To make your communication clear and organized in issues and pull requests, you can use {% data variables.product.prodname_dotcom %} Flavored Markdown for formatting, which combines an easy-to-read, easy-to-write syntax with some custom functionality. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)." -Aprenda a usar o {% data variables.product.prodname_dotcom %} Flavored Markdown no curso "[Comunicação usando Markdown](https://github.com/skills/communicate-using-markdown)" no {% data variables.product.prodname_learning %}. +You can learn {% data variables.product.prodname_dotcom %} Flavored Markdown with the "[Communicate using Markdown](https://github.com/skills/communicate-using-markdown)" course on {% data variables.product.prodname_learning %}. -### 5. Pesquisa no {% data variables.product.product_name %} -Nossa pesquisa integrada permite que você encontre o que você está procurando entre os muitos repositórios, usuários e linhas de código em {% data variables.product.product_name %}. Você pode pesquisar globalmente em todos os {% data variables.product.product_name %} ou limitar sua pesquisa a um repositório ou organização em particular. Para obter mais informações sobre os tipos de pesquisas que você pode fazer no {% data variables.product.product_name %}, confira "[Sobre a pesquisa no {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github)". +### 5. Searching on {% data variables.product.product_name %} +Our integrated search allows you to find what you are looking for among the many repositories, users and lines of code on {% data variables.product.product_name %}. You can search globally across all of {% data variables.product.product_name %} or limit your search to a particular repository or organization. For more information about the types of searches you can do on {% data variables.product.product_name %}, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github)." -Nossa sintaxe de pesquisa permite que você construa consultas usando qualificadores para especificar o que você deseja pesquisar. Para obter mais informações sobre a sintaxe de pesquisa a ser usada na pesquisa, confira "[Pesquisa no {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/searching-on-github)". +Our search syntax allows you to construct queries using qualifiers to specify what you want to search for. For more information on the search syntax to use in search, see "[Searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/searching-on-github)." -### 6. Como gerenciar arquivos no {% data variables.product.product_name %} -Com {% data variables.product.product_name %}, você pode criar, editar, mover e excluir arquivos no seu repositório ou em qualquer repositório ao qual você tenha acesso de gravação. Você também pode acompanhar o histórico de alterações de um arquvo linha por linha. Para obter mais informações, confira "[Como gerenciar arquivos no {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/managing-files-on-github)". +### 6. Managing files on {% data variables.product.product_name %} +With {% data variables.product.product_name %}, you can create, edit, move and delete files in your repository or any repository you have write access to. You can also track the history of changes in a file line by line. For more information, see "[Managing files on {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/managing-files-on-github)." -## Parte 3: Colaborando em {% data variables.product.product_name %} -Qualquer quantidade de pessoas pode trabalhar juntas nos repositórios de {% data variables.product.product_name %}. É possível configurar configurações, criar quadros de projetos e gerenciar suas notificações para incentivar uma colaboração eficaz. +## Part 3: Collaborating on {% data variables.product.product_name %} +Any number of people can work together in repositories across {% data variables.product.product_name %}. You can configure settings, create project boards, and manage your notifications to encourage effective collaboration. -### 1. Como trabalhar com repositórios +### 1. Working with repositories -#### Criar um repositório -Um repositório é como uma pasta para seu projeto. Você pode ter qualquer número de repositórios públicos e privados na sua conta pessoal. Os repositórios podem conter pastas e arquivos, imagens, vídeos, planilhas e conjuntos de dados, bem como o histórico de revisão para todos os arquivos no repositório. Para obter mais informações, confira "[Sobre os repositórios](/github/creating-cloning-and-archiving-repositories/about-repositories)". +#### Creating a repository +A repository is like a folder for your project. You can have any number of public and private repositories in your personal account. Repositories can contain folders and files, images, videos, spreadsheets, and data sets, as well as the revision history for all files in the repository. For more information, see "[About repositories](/github/creating-cloning-and-archiving-repositories/about-repositories)." -Ao criar um novo repositório, você deverá inicializar o repositório com um arquivo README para que as pessoas conheçam o seu projeto. Para obter mais informações, confira "[Como criar um repositório](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)". +When you create a new repository, you should initialize the repository with a README file to let people know about your project. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)." -#### Clonar um repositório -Você pode clonar um repositório existente a partir de {% data variables.product.product_name %} para o seu computador local, facilitando a adição ou remoção dos arquivos, correção de conflitos de merge ou realização de commits complexos. A clonagem de um repositório extrai uma cópia completa de todos os dados do repositório que o {% data variables.product.prodname_dotcom %} tem nesse momento, incluindo todas as versões de cada arquivo e pasta do projeto. Para obter mais informações, confira "[Como clonar um repositório](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)". +#### Cloning a repository +You can clone an existing repository from {% data variables.product.product_name %} to your local computer, making it easier to add or remove files, fix merge conflicts, or make complex commits. Cloning a repository pulls down a full copy of all the repository data that {% data variables.product.prodname_dotcom %} has at that point in time, including all versions of every file and folder for the project. For more information, see "[Cloning a repository](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)." -#### Bifurcar um repositório -Uma bifurcação é uma cópia de um repositório que você gerencia, em que todas as alterações que você fizer não afetarão o repositório original a menos que você envie um pull request para o proprietário do projeto. O uso mais comum das bifurcações são propostas de mudanças no projeto de alguma outra pessoa ou o uso do projeto de outra pessoa como ponto de partida para sua própria ideia. Para obter mais informações, confira "[Como trabalhar com forks](/github/collaborating-with-pull-requests/working-with-forks)". -### 2. Como importar seus projetos -Se você tiver projetos existentes que deseja mover para {% data variables.product.product_name %}, você poderá importar projetos usando o Importador de {% data variables.product.prodname_dotcom %}, a linha de comando ou as ferramentas externas de migração. Para obter mais informações, confira "[Como importar o código-fonte para o {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github)". +#### Forking a repository +A fork is a copy of a repository that you manage, where any changes you make will not affect the original repository unless you submit a pull request to the project owner. Most commonly, forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea. For more information, see "[Working with forks](/github/collaborating-with-pull-requests/working-with-forks)." +### 2. Importing your projects +If you have existing projects you'd like to move over to {% data variables.product.product_name %} you can import projects using the {% data variables.product.prodname_dotcom %} Importer, the command line, or external migration tools. For more information, see "[Importing source code to {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github)." -### 3. Como gerenciar colaboradores e permissões -Você pode colaborar em seu projeto com outras pessoas usando os problemas, as pull requests e os quadros de projeto do repositório. Você pode convidar outras pessoas para seu repositório como colaboradores na guia **Colaboradores** nas configurações do repositório. Para obter mais informações, confira "[Como convidar colaboradores para um repositório pessoal](/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)". +### 3. Managing collaborators and permissions +You can collaborate on your project with others using your repository's issues, pull requests, and project boards. You can invite other people to your repository as collaborators from the **Collaborators** tab in the repository settings. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)." -Você é o proprietário de qualquer repositório que você cria na sua conta pessoal e você tem controle total sobre repositório. Os colaboradores têm acesso de gravação ao seu repositório, limitando o que eles têm permissão para fazer. Para obter mais informações, confira "[Níveis de permissão para um repositório da conta pessoal](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)". +You are the owner of any repository you create in your personal account and have full control of the repository. Collaborators have write access to your repository, limiting what they have permission to do. For more information, see "[Permission levels for a personal account repository](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)." -### 4. Como gerenciar as configurações do repositório -Como proprietário de um repositório, você pode configurar diversas configurações, incluindo a visibilidade do repositório, tópicos e a pré-visualização das mídias sociais. Para obter mais informações, confira "[Como gerenciar as configurações do repositório](/github/administering-a-repository/managing-repository-settings)". +### 4. Managing repository settings +As the owner of a repository you can configure several settings, including the repository's visibility, topics, and social media preview. For more information, see "[Managing repository settings](/github/administering-a-repository/managing-repository-settings)." -### 5. Como configurar seu projeto para contribuições úteis -{% ifversion fpt or ghec %} Para incentivar os colaboradores do seu repositório, você precisa ter uma comunidade que incentive as pessoas a usar, contribuir e divulgar seu projeto. Para obter mais informações, confira "[Como criar comunidades receptivas](https://opensource.guide/building-community/)" nos Guias de Código Aberto. +### 5. Setting up your project for healthy contributions +{% ifversion fpt or ghec %} +To encourage collaborators in your repository, you need a community that encourages people to use, contribute to, and evangelize your project. For more information, see "[Building Welcoming Communities](https://opensource.guide/building-community/)" in the Open Source Guides. -Ao adicionar arquivos como diretrizes de contribuição, um código de conduta e uma licença para o repositório é possível criar um ambiente em que seja mais fácil para os colaboradores fazerem contribuições úteis e significativas. Para obter mais informações, confira "[Como configurar seu projeto para contribuições úteis](/communities/setting-up-your-project-for-healthy-contributions)". -{% endif %} {% ifversion ghes or ghae %} Adicionando arquivos como diretrizes de contribuição, um código de conduta e recursos de suporte ao seu repositório, você pode criar um ambiente em que seja mais fácil para os colaboradores fazerem contribuições significativas e úteis. Para obter mais informações, confira "[Como configurar seu projeto para contribuições úteis](/communities/setting-up-your-project-for-healthy-contributions)". +By adding files like contributing guidelines, a code of conduct, and a license to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)." +{% endif %} +{% ifversion ghes or ghae %} +By adding files like contributing guidelines, a code of conduct, and support resources to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)." {% endif %} -### 6. Como usar os quadros de projetos e os Problemas do GitHub -Você pode usar os problemas do GitHub para organizar seu trabalho com problemas e pull requests, bem como gerenciar seu fluxo de trabalho com quadros de projetos. Para obter mais informações, confira "[Sobre os problemas](/issues/tracking-your-work-with-issues/about-issues)" e "[Sobre os quadros de projetos](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)". +### 6. Using GitHub Issues and project boards +You can use GitHub Issues to organize your work with issues and pull requests and manage your workflow with project boards. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)" and "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." -### 7. Como gerenciar notificações -As notificações fornecem atualizações sobre as atividades do {% data variables.product.prodname_dotcom %} nas quais você se inscreveu ou participou. Se não estiver mais interessado em uma conversa, cancele a assinatura dela, deixe de acompanhar ou personalize os tipos de notificações que você receberá no futuro. Para obter mais informações, confira "[Sobre as notificações](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)". +### 7. Managing notifications +Notifications provide updates about the activity on {% data variables.product.prodname_dotcom %} you've subscribed to or participated in. If you're no longer interested in a conversation, you can unsubscribe, unwatch, or customize the types of notifications you'll receive in the future. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." -### 8. Como trabalhar com o {% data variables.product.prodname_pages %} -Você pode usar {% data variables.product.prodname_pages %} para criar e hospedar um site diretamente a partir de um repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Para obter mais informações, confira "[Sobre o {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)". +### 8. Working with {% data variables.product.prodname_pages %} +You can use {% data variables.product.prodname_pages %} to create and host a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)." {% ifversion discussions %} -### 9. Como usar as {% data variables.product.prodname_discussions %} -Você pode habilitar {% data variables.product.prodname_discussions %} para o repositório ajudar a criar uma comunidade em torno do seu projeto. Mantenedores, colaboradores e visitantes podem usar discussões para compartilhar anúncios, fazer e responder a perguntas e participar de conversas sobre objetivos. Para obter mais informações, confira "[Sobre as discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". +### 9. Using {% data variables.product.prodname_discussions %} +You can enable {% data variables.product.prodname_discussions %} for your repository to help build a community around your project. Maintainers, contributors and visitors can use discussions to share announcements, ask and answer questions, and participate in conversations around goals. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." {% endif %} -## Parte 4: Personalizando e automatizando seu trabalho em {% data variables.product.product_name %} +## Part 4: Customizing and automating your work on {% data variables.product.product_name %} {% data reusables.getting-started.customizing-and-automating %} {% ifversion fpt or ghec %} -### 1. Como usar o {% data variables.product.prodname_marketplace %} -{% data reusables.getting-started.marketplace %} {% endif %} -### {% ifversion fpt or ghec %}2.{% else %}1.{% endif %} Usando o {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}API{% endif %} +### 1. Using {% data variables.product.prodname_marketplace %} +{% data reusables.getting-started.marketplace %} +{% endif %} +### {% ifversion fpt or ghec %}2.{% else %}1.{% endif %} Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API {% data reusables.getting-started.api %} -### {% ifversion fpt or ghec %}3.{% else %}2.{% endif %} Como criar {% data variables.product.prodname_actions %} +### {% ifversion fpt or ghec %}3.{% else %}2.{% endif %} Building {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -### {% ifversion fpt or ghec %}4.{% else %}3.{% endif %} Como publicar e gerenciar o {% data variables.product.prodname_registry %} +### {% ifversion fpt or ghec %}4.{% else %}3.{% endif %} Publishing and managing {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} -## Parte 5: Criando com segurança em {% data variables.product.product_name %} -{% data variables.product.product_name %} tem uma variedade de recursos de segurança que ajudam a manter códigos e segredos seguros nos repositórios. Algumas funcionalidades estão disponíveis para todos os repositórios, enquanto outras estão disponíveis apenas para repositórios públicos e repositórios com uma licença de {% data variables.product.prodname_GH_advanced_security %}. Para ter uma visão geral dos recursos de segurança do {% data variables.product.product_name %}, confira "[Recursos de segurança do {% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)". +## Part 5: Building securely on {% data variables.product.product_name %} +{% data variables.product.product_name %} has a variety of security features that help keep code and secrets secure in repositories. Some features are available for all repositories, while others are only available for public repositories and repositories with a {% data variables.product.prodname_GH_advanced_security %} license. For an overview of {% data variables.product.product_name %} security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)." -### 1. Como proteger seu repositório -Como administrador do repositório, você pode proteger os seus repositórios definindo as configurações de segurança do repositório. Elas incluem o gerenciamento de acesso ao seu repositório, a definição de uma política de segurança e o gerenciamento de dependências. Para repositórios públicos e para repositórios privados pertencentes a organizações em que o {% data variables.product.prodname_GH_advanced_security %} está habilitado, você também pode configurar o código e a digitalização de segredos para identificar automaticamente vulnerabilidades e garantir que os tokens e chaves não sejam expostos. +### 1. Securing your repository +As a repository administrator, you can secure your repositories by configuring repository security settings. These include managing access to your repository, setting a security policy, and managing dependencies. For public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled, you can also configure code and secret scanning to automatically identify vulnerabilities and ensure tokens and keys are not exposed. -Para obter mais informações sobre as etapas que você pode executar para proteger seus repositórios, confira "[Como proteger seu repositório](/code-security/getting-started/securing-your-repository)". +For more information on steps you can take to secure your repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository)." {% ifversion fpt or ghec %} -### 2. Como gerenciar suas dependências -Uma grande parte da criação é manter as dependências do seu projeto para garantir que todos os pacotes e aplicativos dos quais você depende estejam atualizados e seguros. Você pode gerenciar as dependências do seu repositório em {% data variables.product.product_name %}, explorando o gráfico de dependências para o seu repositório, usando o Dependabot para aumentar automaticamente os pull requests para manter as suas dependências atualizadas e receber alertas de dependência e atualizações de segurança para dependências vulneráveis. +### 2. Managing your dependencies +A large part of building securely is maintaining your project's dependencies to ensure that all packages and applications you depend on are updated and secure. You can manage your repository's dependencies on {% data variables.product.product_name %} by exploring the dependency graph for your repository, using Dependabot to automatically raise pull requests to keep your dependencies up-to-date, and receiving Dependabot alerts and security updates for vulnerable dependencies. -Para obter mais informações, confira "[Como proteger sua cadeia de fornecedores de software](/code-security/supply-chain-security)". +For more information, see "[Securing your software supply chain](/code-security/supply-chain-security)." {% endif %} -## Parte 6: Participando da comunidade de {% data variables.product.prodname_dotcom %} +## Part 6: Participating in {% data variables.product.prodname_dotcom %}'s community {% data reusables.getting-started.participating-in-community %} -### 1. Como contribuir para projetos de código aberto +### 1. Contributing to open source projects {% data reusables.getting-started.open-source-projects %} -### 2. Como interagir com o {% data variables.product.prodname_gcf %} +### 2. Interacting with {% data variables.product.prodname_gcf %} {% data reusables.support.ask-and-answer-forum %} -### 3. Leitura sobre o {% data variables.product.product_name %} no {% data variables.product.prodname_docs %} +### 3. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %} {% data reusables.docs.you-can-read-docs-for-your-product %} -### 4. Aprendizagem com o {% data variables.product.prodname_learning %} +### 4. Learning with {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning %} {% ifversion fpt or ghec %} -### 5. Como apoiar a comunidade de código aberto +### 5. Supporting the open source community {% data reusables.getting-started.sponsors %} -### 6. Como entrar em contato com o {% data variables.contact.github_support %} +### 6. Contacting {% data variables.contact.github_support %} {% data reusables.getting-started.contact-support %} {% ifversion fpt %} -## Leitura adicional -- "[Introdução à {% data variables.product.prodname_team %}](/get-started/onboarding/getting-started-with-github-team)" {% endif %} {% endif %} +## Further reading +- "[Getting started with {% data variables.product.prodname_team %}](/get-started/onboarding/getting-started-with-github-team)" +{% endif %} +{% endif %} diff --git a/translations/pt-BR/content/get-started/quickstart/create-a-repo.md b/translations/pt-BR/content/get-started/quickstart/create-a-repo.md index d160163c58..06048bb4fd 100644 --- a/translations/pt-BR/content/get-started/quickstart/create-a-repo.md +++ b/translations/pt-BR/content/get-started/quickstart/create-a-repo.md @@ -1,11 +1,11 @@ --- -title: Criar um repositório +title: Create a repo redirect_from: - /create-a-repo - /articles/create-a-repo - /github/getting-started-with-github/create-a-repo - /github/getting-started-with-github/quickstart/create-a-repo -intro: 'Para colocar seu projeto no {% data variables.product.prodname_dotcom %}, você precisará criar um repositório no qual ele residirá.' +intro: 'To put your project up on {% data variables.product.prodname_dotcom %}, you will need to create a repository for it to live in.' versions: fpt: '*' ghes: '*' @@ -16,22 +16,16 @@ topics: - Issues - Notifications - Accounts -ms.openlocfilehash: 66db99def4463929236197fdc4903f82bfc1cbe2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146682289' --- -## Criar um repositório +## Create a repository {% ifversion fpt or ghec %} -Você pode armazenar uma variedade de projetos nos repositórios do {% data variables.product.prodname_dotcom %}, incluindo projetos de código aberto. Com os projetos de código aberto, você pode compartilhar o código para tornar um software melhor e mais confiável. Você pode usar repositórios para colaborar com outras pessoas e acompanhar seu trabalho. Para obter mais informações, confira "[Sobre os repositórios](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)". Para saber mais sobre projetos de código aberto, visite [OpenSource.org](https://opensource.org/about). +You can store a variety of projects in {% data variables.product.prodname_dotcom %} repositories, including open source projects. With open source projects, you can share code to make better, more reliable software. You can use repositories to collaborate with others and track your work. For more information, see "[About repositories](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)." To learn more about open source projects, visit [OpenSource.org](https://opensource.org/about). {% elsif ghes or ghae %} -Você pode armazenar uma série de projetos em repositórios de {% data variables.product.product_name %}, incluindo projetos de innersource. Com o innersource, você pode compartilhar código para criar um software melhor e mais confiável. Para obter mais informações sobre o InnerSource, confira o white paper "[Uma introdução ao InnerSource](https://resources.github.com/whitepapers/introduction-to-innersource/)" do {% data variables.product.company_short %}. +You can store a variety of projects in {% data variables.product.product_name %} repositories, including innersource projects. With innersource, you can share code to make better, more reliable software. For more information on innersource, see {% data variables.product.company_short %}'s white paper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)." {% endif %} @@ -39,10 +33,10 @@ Você pode armazenar uma série de projetos em repositórios de {% data variable {% note %} -**Observações:** -- você pode criar repositórios públicos para um projeto de código aberto. Ao criar seu repositório público, lembre-se de incluir um [arquivo de licença](https://choosealicense.com/) que determina como deseja que o seu projeto seja compartilhado com outras pessoas. {% data reusables.open-source.open-source-guide-repositories %} +**Notes:** +- You can create public repositories for an open source project. When creating your public repository, make sure to include a [license file](https://choosealicense.com/) that determines how you want your project to be shared with others. {% data reusables.open-source.open-source-guide-repositories %} - {% data reusables.open-source.open-source-learning %} -- Você também pode adicionar arquivos de integridade da comunidade aos seus repositórios para definir diretrizes sobre como contribuir, manter seus repositórios seguros e muito mais. Para obter mais informações, confira "[Como criar um arquivo padrão de integridade da comunidade](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)". +- You can also add community health files to your repositories, to set guidelines on how to contribute, keep your repositories safe, and much more. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." {% endnote %} @@ -51,12 +45,15 @@ Você pode armazenar uma série de projetos em repositórios de {% data variable {% webui %} {% data reusables.repositories.create_new %} -2. Digite um nome breve e memorável para o repositório. Por exemplo, "olá mundo". - ![Campo usado para inserir um nome de repositório](/assets/images/help/repository/create-repository-name.png) -3. Opcionalmente, adicione uma descrição do repositório. Por exemplo, "Meu primeiro repositório no {% data variables.product.product_name %}". - ![Campo usado para inserir uma descrição do repositório](/assets/images/help/repository/create-repository-desc.png) {% data reusables.repositories.choose-repo-visibility %} {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %} +2. Type a short, memorable name for your repository. For example, "hello-world". + ![Field for entering a repository name](/assets/images/help/repository/create-repository-name.png) +3. Optionally, add a description of your repository. For example, "My first repository on {% data variables.product.product_name %}." + ![Field for entering a repository description](/assets/images/help/repository/create-repository-desc.png) +{% data reusables.repositories.choose-repo-visibility %} +{% data reusables.repositories.initialize-with-readme %} +{% data reusables.repositories.create-repo %} -Parabéns! Você criou com sucesso seu primeiro repositório e o inicializou com um arquivo *LEIAME*. +Congratulations! You've successfully created your first repository, and initialized it with a *README* file. {% endwebui %} @@ -64,47 +61,51 @@ Parabéns! Você criou com sucesso seu primeiro repositório e o inicializou com {% data reusables.cli.cli-learn-more %} -1. Na linha de comando, acesse o diretório onde você gostaria de criar um clone local do seu novo projeto. -2. Para criar um repositório para seu projeto, use o subcomando `gh repo create`. Quando solicitado, selecione **Criar um repositório no GitHub do zero** e insira o nome do novo projeto. Caso você deseje que o seu projeto pertença a uma organização em vez da sua conta pessoal, especifique o nome da organização e o nome do projeto com `organization-name/project-name`. -3. Siga as instruções interativas. Para clonar o repositório localmente, marque sim quando perguntarem se você deseja clonar o diretório do projeto remoto. -4. Como alternativa, para ignorar os prompts, forneça o nome do repositório e um sinalizador de visibilidade (`--public`, `--private` ou `--internal`). Por exemplo, `gh repo create project-name --public`. Para clonar o repositório localmente, transmita o sinalizador `--clone`. Para obter mais informações sobre os possíveis argumentos, confira o [manual da CLI do GitHub](https://cli.github.com/manual/gh_repo_create). +1. In the command line, navigate to the directory where you would like to create a local clone of your new project. +2. To create a repository for your project, use the `gh repo create` subcommand. When prompted, select **Create a new repository on GitHub from scratch** and enter the name of your new project. If you want your project to belong to an organization instead of to your personal account, specify the organization name and project name with `organization-name/project-name`. +3. Follow the interactive prompts. To clone the repository locally, confirm yes when asked if you would like to clone the remote project directory. +4. Alternatively, to skip the prompts supply the repository name and a visibility flag (`--public`, `--private`, or `--internal`). For example, `gh repo create project-name --public`. To clone the repository locally, pass the `--clone` flag. For more information about possible arguments, see the [GitHub CLI manual](https://cli.github.com/manual/gh_repo_create). {% endcli %} -## Fazer commit da primeira alteração +## Commit your first change {% webui %} -Um *[commit](/articles/github-glossary#commit)* é como um instantâneo de todos os arquivos do seu projeto em determinado momento. +A *[commit](/articles/github-glossary#commit)* is like a snapshot of all the files in your project at a particular point in time. -Na criação do repositório, você o inicializou com um arquivo *LEIAME*. Os arquivos *LEIAME* são um ótimo lugar para descrever o projeto com mais detalhes ou adicionar alguma documentação (por exemplo, como instalar ou usar o projeto). O conteúdo do arquivo *LEIAME* é mostrado automaticamente na página inicial do repositório. +When you created your new repository, you initialized it with a *README* file. *README* files are a great place to describe your project in more detail, or add some documentation such as how to install or use your project. The contents of your *README* file are automatically shown on the front page of your repository. -Vamos fazer commit de uma alteração no arquivo *README*. +Let's commit a change to the *README* file. -1. Na lista de arquivos do repositório, clique em ***README.md***. - ![Arquivo README na lista de arquivos](/assets/images/help/repository/create-commit-open-readme.png) -2. Acima do conteúdo do arquivo, clique em {% octicon "pencil" aria-label="The edit icon" %}. -3. Na guia **Editar arquivo**, digite algumas informações sobre você mesmo. - ![Novo conteúdo no arquivo](/assets/images/help/repository/edit-readme-light.png) {% data reusables.files.preview_change %} -5. Revise as alterações feitas no arquivo. Você verá o novo conteúdo em verde. - ![Exibição de visualização de arquivo](/assets/images/help/repository/create-commit-review.png) {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} +1. In your repository's list of files, click ***README.md***. + ![README file in file list](/assets/images/help/repository/create-commit-open-readme.png) +2. Above the file's content, click {% octicon "pencil" aria-label="The edit icon" %}. +3. On the **Edit file** tab, type some information about yourself. + ![New content in file](/assets/images/help/repository/edit-readme-light.png) +{% data reusables.files.preview_change %} +5. Review the changes you made to the file. You will see the new content in green. + ![File preview view](/assets/images/help/repository/create-commit-review.png) +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} {% endwebui %} {% cli %} -Agora que você criou um projeto, você pode começar a fazer commit das alterações. +Now that you have created a project, you can start committing changes. -Os arquivos *LEIAME* são um ótimo lugar para descrever o projeto com mais detalhes ou adicionar alguma documentação (por exemplo, como instalar ou usar o projeto). O conteúdo do arquivo *LEIAME* é mostrado automaticamente na página inicial do repositório. Siga estas etapas para adicionar um arquivo *README*. +*README* files are a great place to describe your project in more detail, or add some documentation such as how to install or use your project. The contents of your *README* file are automatically shown on the front page of your repository. Follow these steps to add a *README* file. -1. Na linha de comando, acesse o diretório raiz do seu novo projeto. (Esse diretório foi criado quando você executou o comando `gh repo create`). -1. Crie um arquivo *README* com algumas informações sobre o projeto. +1. In the command line, navigate to the root directory of your new project. (This directory was created when you ran the `gh repo create` command.) +1. Create a *README* file with some information about the project. ```shell echo "info about this project" >> README.md ``` -1. Insira `git status`. Você verá que tem um arquivo `README.md` não controlado. +1. Enter `git status`. You will see that you have an untracked `README.md` file. ```shell $ git status @@ -116,13 +117,13 @@ Os arquivos *LEIAME* são um ótimo lugar para descrever o projeto com mais deta nothing added to commit but untracked files present (use "git add" to track) ``` -1. Stage e commit do arquivo. +1. Stage and commit the file. ```shell git add README.md && git commit -m "Add README" ``` -1. Faça push das alterações para seu branch. +1. Push the changes to your branch. ```shell git push --set-upstream origin HEAD @@ -130,17 +131,17 @@ Os arquivos *LEIAME* são um ótimo lugar para descrever o projeto com mais deta {% endcli %} -## Próximas etapas +## Next steps -Você acabou de criar um repositório, incluindo um arquivo *README*, e seu primeiro commit no {% data variables.product.product_location %}. +You have now created a repository, including a *README* file, and created your first commit on {% data variables.location.product_location %}. {% webui %} -* Você já pode clonar um repositório do {% data variables.product.prodname_dotcom %} para criar uma cópia local no computador. A partir do seu repositório local, você pode fazer commit e criar um pull request para atualizar as alterações no repositório upstream. Para obter mais informações, confira "[Como clonar um repositório](/github/creating-cloning-and-archiving-repositories/cloning-a-repository)" e "[Configurar o Git](/articles/set-up-git)". +* You can now clone a {% data variables.product.prodname_dotcom %} repository to create a local copy on your computer. From your local repository you can commit, and create a pull request to update the changes in the upstream repository. For more information, see "[Cloning a repository](/github/creating-cloning-and-archiving-repositories/cloning-a-repository)" and "[Set up Git](/articles/set-up-git)." {% endwebui %} -* Encontre projetos e repositórios interessantes no {% data variables.product.prodname_dotcom %} e faça alterações neles criando um fork do repositório. {% data reusables.getting-started.fork-a-repository %} +* You can find interesting projects and repositories on {% data variables.product.prodname_dotcom %} and make changes to them by creating a fork of the repository. {% data reusables.getting-started.fork-a-repository %} * {% data reusables.getting-started.being-social %} diff --git a/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md b/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md index 3f0963e30d..ad5ed4621b 100644 --- a/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md +++ b/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md @@ -1,12 +1,12 @@ --- -title: Bifurcar um repositório +title: Fork a repo redirect_from: - /fork-a-repo - /forking - /articles/fork-a-repo - /github/getting-started-with-github/fork-a-repo - /github/getting-started-with-github/quickstart/fork-a-repo -intro: Um fork é uma cópia de um repositório. Bifurcar um repositório permite que você faça experiências à vontade sem comprometer o projeto original. +intro: A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project. permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}' versions: fpt: '*' @@ -18,67 +18,61 @@ topics: - Issues - Notifications - Accounts -ms.openlocfilehash: b6f98f30c67f14fab1da3658e42e8eba67f5f50c -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717570' --- -## Sobre bifurcações +## About forks -O uso mais comum das bifurcações é propor alterações no projeto de outra pessoa no qual você não tem acesso de gravação ou usar o projeto de outra pessoa como ponto de partida para uma ideia própria. Você pode bifurcar um repositório para criar uma cópia do repositório e fazer alterações sem afetar o repositório upstream. Para obter mais informações, confira "[Como trabalhar com forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)". +Most commonly, forks are used to either propose changes to someone else's project to which you do not have write access, or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)." -### Proponha mudanças no projeto de outra pessoa +### Propose changes to someone else's project -Por exemplo, você pode usar bifurcações para propor alterações relacionadas à correção de um bug. Em vez de registrar um erro encontrado, você pode: +For example, you can use forks to propose changes related to fixing a bug. Rather than logging an issue for a bug you have found, you can: -- Crie fork do repositório. -- Fazer a correção. -- Enviar um pull request ao proprietário do projeto. +- Fork the repository. +- Make the fix. +- Submit a pull request to the project owner. -### Use o projeto de outra pessoa como ponto de partida para sua própria ideia. +### Use someone else's project as a starting point for your own idea. -O software de código aberto baseia-se na ideia de que ao compartilhar códigos, podemos criar softwares melhores e mais confiáveis. Para obter mais informações, confira "[Sobre a Open Source Initiative](https://opensource.org/about)" na Open Source Initiative. +Open source software is based on the idea that by sharing code, we can make better, more reliable software. For more information, see the "[About the Open Source Initiative](https://opensource.org/about)" on the Open Source Initiative. -Para obter mais informações sobre como aplicar os princípios de código aberto ao trabalho de desenvolvimento da sua organização no {% data variables.product.product_location %}, confira o white paper "[Uma introdução ao InnerSource](https://resources.github.com/whitepapers/introduction-to-innersource/)" do {% data variables.product.prodname_dotcom %}". +For more information about applying open source principles to your organization's development work on {% data variables.location.product_location %}, see {% data variables.product.prodname_dotcom %}'s white paper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)." {% ifversion fpt or ghes or ghec %} -Ao criar um repositório público a partir de uma bifurcação do projeto de outra pessoa, confirme que incluiu um arquivo de licença que estabelece como você quer que seu projeto seja compartilhado com outros. Para obter mais informações, confira "[Escolher uma licença de código aberto](https://choosealicense.com/)" em choosealicense.com. +When creating your public repository from a fork of someone's project, make sure to include a license file that determines how you want your project to be shared with others. For more information, see "[Choose an open source license](https://choosealicense.com/)" at choosealicense.com. {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning %} {% endif %} -## Pré-requisitos +## Prerequisites -Caso ainda não tenha feito isso, primeiro, [configure o Git](/articles/set-up-git). Não se esqueça de [configurar também a autenticação no {% data variables.product.product_location %} por meio do Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git). +If you have not yet, you should first [set up Git](/articles/set-up-git). Don't forget to [set up authentication to {% data variables.location.product_location %} from Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git) as well. -## Bifurcar um repositório +## Forking a repository {% webui %} -Você pode bifurcar um projeto para propor alterações no repositório upstream ou original. Nesse caso, uma boa prática é sincronizar regularmente sua bifurcação com o repositório upstream. Para isso, é necessário usar Git na linha de comando. Você pode praticar a configuração do repositório upstream usando o mesmo repositório [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) do qual acabou de criar um fork. +You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked. -1. No {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navegue até o repositório [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife). -2. No canto superior direito da página, clique em **Criar Fork**. - ![Botão Criar Fork](/assets/images/help/repository/fork_button.png) -3. Selecione um proprietário para o repositório bifurcado. - ![Criar uma página de bifurcação com a lista suspensa do proprietário enfatizada](/assets/images/help/repository/fork-choose-owner.png) -4. Por padrão, as bifurcações são nomeadas da mesma forma que os respectivos repositórios pai. Você pode alterar o nome da bifurcação para distingui-la ainda mais. - ![Criar uma página de bifurcação com o campo do nome do repositório enfatizado](/assets/images/help/repository/fork-choose-repo-name.png) -5. Como opção, adicione uma descrição da bifurcação. - ![Criar uma página de bifurcação com o campo de descrição enfatizado](/assets/images/help/repository/fork-description.png) -6. Escolha se deseja copiar apenas o branch padrão ou todos os branches para a nova bifurcação. Para muitos cenários de bifurcação, como contribuir para projetos de código aberto, você só precisa copiar o branch padrão. Por padrão, somente o branch padrão é copiado. - ![Opção para copiar apenas o branch padrão](/assets/images/help/repository/copy-default-branch-only.png) -7. Clique em **Criar bifurcação**. - ![Botão Criar bifurcação enfatizado](/assets/images/help/repository/fork-create-button.png) +1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository. +2. In the top-right corner of the page, click **Fork**. + ![Fork button](/assets/images/help/repository/fork_button.png) +3. Select an owner for the forked repository. + ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png) +4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further. + ![Create a new fork page with repository name field emphasized](/assets/images/help/repository/fork-choose-repo-name.png) +5. Optionally, add a description of your fork. + ![Create a new fork page with description field emphasized](/assets/images/help/repository/fork-description.png) +6. Choose whether to copy only the default branch or all branches to the new fork. For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. By default, only the default branch is copied. + ![Option to copy only the default branch](/assets/images/help/repository/copy-default-branch-only.png) +7. Click **Create fork**. + ![Emphasized create fork button](/assets/images/help/repository/fork-create-button.png) {% note %} -**Observação:** se você quiser copiar branches adicionais do repositório pai, poderá fazê-lo na página **Branches**. Para obter mais informações, confira "[Criar e excluir branches no seu repositório](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)".{% endnote %} +**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %} {% endwebui %} @@ -86,38 +80,41 @@ Você pode bifurcar um projeto para propor alterações no repositório upstream {% data reusables.cli.cli-learn-more %} -Para criar um fork de um repositório, use o subcomando `gh repo fork`. +To create a fork of a repository, use the `gh repo fork` subcommand. ```shell -gh repo fork repository +gh repo fork REPOSITORY ``` -Para criar o fork em uma organização, use o sinalizador `--org`. +To create the fork in an organization, use the `--org` flag. ```shell -gh repo fork repository --org "octo-org" +gh repo fork REPOSITORY --org "octo-org" ``` {% endcli %} -{% desktop %} {% enddesktop %} +{% desktop %} +{% enddesktop %} -## Clonando o seu repositório bifurcado +## Cloning your forked repository -Agora, você tem uma bifurcação do repositório Spoon-Knife, mas você não tem os arquivos desse repositório localmente no seu computador. +Right now, you have a fork of the Spoon-Knife repository, but you do not have the files in that repository locally on your computer. {% webui %} -1. No {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navegue até o **seu fork** do repositório Spoon-Knife. -{% data reusables.repositories.copy-clone-url %} {% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.change-current-directory-clone %} -4. Digite `git clone` e cole a URL já copiada. Ela terá esta aparência, com seu nome de usuário do {% data variables.product.product_name %} em vez de `YOUR-USERNAME`: +1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to **your fork** of the Spoon-Knife repository. +{% data reusables.repositories.copy-clone-url %} +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.command_line.change-current-directory-clone %} +4. Type `git clone`, and then paste the URL you copied earlier. It will look like this, with your {% data variables.product.product_name %} username instead of `YOUR-USERNAME`: ```shell - $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife + $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife ``` -5. Pressione **Enter**. Seu clone local estará criado. +5. Press **Enter**. Your local clone will be created. ```shell - $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife + $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife > Cloning into `Spoon-Knife`... > remote: Counting objects: 10, done. > remote: Compressing objects: 100% (8/8), done. @@ -131,55 +128,60 @@ Agora, você tem uma bifurcação do repositório Spoon-Knife, mas você não te {% data reusables.cli.cli-learn-more %} -Para criar um clone do fork, use o sinalizador `--clone`. +To create a clone of your fork, use the `--clone` flag. ```shell -gh repo fork repository --clone=true +gh repo fork REPOSITORY --clone=true ``` {% endcli %} {% desktop %} -{% 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.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 %} {% enddesktop %} -## Configurar o Git para sincronizar a bifurcação com o repositório original +## Configuring Git to sync your fork with the original repository -Ao bifurcar um projeto para propor mudanças no repositório original, é possível configurar o Git para fazer pull de alterações do repositório original ou upstream no clone local de sua bifurcação. +When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork. {% webui %} -1. No {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navegue até o repositório [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife). -{% data reusables.repositories.copy-clone-url %} {% data reusables.command_line.open_the_multi_os_terminal %} -4. Mude os diretórios para a localidade da bifurcação que você clonou. - - Para acessar o diretório base, digite apenas `cd` sem nenhum outro texto. - - Para listar os arquivos e as pastas do diretório atual, digite `ls`. - - Para entrar em um dos diretórios listados, digite `cd your_listed_directory`. - - Para subir um diretório, digite `cd ..`. -5. Digite `git remote -v` e pressione **Enter**. Você verá o repositório remoto atual configurado para sua bifurcação. +1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository. +{% data reusables.repositories.copy-clone-url %} +{% data reusables.command_line.open_the_multi_os_terminal %} +4. Change directories to the location of the fork you cloned. + - To go to your home directory, type just `cd` with no other text. + - To list the files and folders in your current directory, type `ls`. + - To go into one of your listed directories, type `cd your_listed_directory`. + - To go up one directory, type `cd ..`. +5. Type `git remote -v` and press **Enter**. You will see the current configured remote repository for your fork. ```shell $ git remote -v - > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) ``` -6. Digite `git remote add upstream`, cole a URL copiada na Etapa 3 e pressione **Enter**. Ele terá a seguinte aparência: +6. Type `git remote add upstream`, and then paste the URL you copied in Step 3 and press **Enter**. It will look like this: ```shell $ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/Spoon-Knife.git ``` -7. Para verificar o novo repositório upstream especificado para a bifurcação, digite `git remote -v` novamente. Você verá a URL do fork como `origin` e a URL do repositório original como `upstream`. +7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`. ```shell $ git remote -v - > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) - > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (fetch) - > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (push) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/ YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ ORIGINAL_REPOSITORY.git (fetch) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ ORIGINAL_REPOSITORY.git (push) ``` -Agora é possível manter a bifurcação sincronizada com o repositório upstream usando apenas alguns comandos Git. Para obter mais informações, confira "[Como sincronizar um fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)". +Now, you can keep your fork synced with the upstream repository with a few Git commands. For more information, see "[Syncing a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)." {% endwebui %} @@ -187,41 +189,41 @@ Agora é possível manter a bifurcação sincronizada com o repositório upstrea {% data reusables.cli.cli-learn-more %} -Para configurar um repositório remoto para o repositório com fork, use o sinalizador `--remote`. +To configure a remote repository for the forked repository, use the `--remote` flag. ```shell -gh repo fork repository --remote=true +gh repo fork REPOSITORY --remote=true ``` -Para especificar o nome do repositório remoto, use o sinalizador `--remote-name`. +To specify the remote repository's name, use the `--remote-name` flag. ```shell -gh repo fork repository --remote-name "main-remote-repo" +gh repo fork REPOSITORY --remote-name "main-remote-repo" ``` {% endcli %} -### Editando uma bifurcação +### Editing a fork -Você pode fazer alterações em uma bifurcação, incluindo: +You can make any changes to a fork, including: -- **Como criar branches:** os [*branches*](/articles/creating-and-deleting-branches-within-your-repository/) permitem que você crie recursos ou teste ideias sem colocar seu projeto principal em risco. -- **Como abrir solicitações de pull:** se você espera contribuir novamente para o repositório original, envie uma solicitação ao autor original para efetuar pull do fork no repositório enviando uma [solicitação de pull](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests). +- **Creating branches:** [*Branches*](/articles/creating-and-deleting-branches-within-your-repository/) allow you to build new features or test out ideas without putting your main project at risk. +- **Opening pull requests:** If you are hoping to contribute back to the original repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests). -## Localize outro repositório para bifurcar -Bifurque um repositório para começar a contribuir com um projeto. {% data reusables.repositories.you-can-fork %} +## Find another repository to fork +Fork a repository to start contributing to a project. {% data reusables.repositories.you-can-fork %} -{% ifversion fpt or ghec %}Procure [Explorar](https://github.com/explore) para encontrar projetos e começar a contribuir nos repositórios de código aberto. Para obter mais informações, confira "[Como encontrar maneiras de contribuir com o código aberto no {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)". +{% ifversion fpt or ghec %}You can browse [Explore](https://github.com/explore) to find projects and start contributing to open source repositories. For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)." {% endif %} -## Próximas etapas +## Next Steps -Você já bifurcou um repositório, treinou clonar sua bifurcação e configurou um repositório upstream. +You have now forked a repository, practiced cloning your fork, and configured an upstream repository. -* Para obter mais informações sobre como clonar a bifurcação e sincronizar as alterações em um repositório bifurcado usando o seu computador, confira "[Configurar o Git](/articles/set-up-git)". +* For more information about cloning the fork and syncing the changes in a forked repository from your computer, see "[Set up Git](/articles/set-up-git)." -* Você também pode criar um novo repositório onde você pode colocar todos os seus projetos e compartilhar o código em {% data variables.product.prodname_dotcom %}. {% data reusables.getting-started.create-a-repository %}" +* You can also create a new repository where you can put all your projects and share the code on {% data variables.product.prodname_dotcom %}. {% data reusables.getting-started.create-a-repository %}" * {% data reusables.getting-started.being-social %} diff --git a/translations/pt-BR/content/get-started/signing-up-for-github/verifying-your-email-address.md b/translations/pt-BR/content/get-started/signing-up-for-github/verifying-your-email-address.md index cd0b567428..64e0ef6f88 100644 --- a/translations/pt-BR/content/get-started/signing-up-for-github/verifying-your-email-address.md +++ b/translations/pt-BR/content/get-started/signing-up-for-github/verifying-your-email-address.md @@ -1,6 +1,6 @@ --- -title: Verificar endereço de e-mail -intro: 'A verificação do endereço de e-mail principal garante segurança reforçada, permite que a equipe do {% data variables.product.prodname_dotcom %} auxilie melhor caso você esqueça sua senha e fornece acesso a mais recursos no {% data variables.product.prodname_dotcom %}.' +title: Verifying your email address +intro: 'Verifying your primary email address ensures strengthened security, allows {% data variables.product.prodname_dotcom %} staff to better assist you if you forget your password, and gives you access to more features on {% data variables.product.prodname_dotcom %}.' redirect_from: - /articles/troubleshooting-email-verification - /articles/setting-up-email-verification @@ -13,64 +13,59 @@ versions: topics: - Accounts shortTitle: Verify your email address -ms.openlocfilehash: 75c455907ab0cc89f1ba8b30d6fa1d37f2d9798f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145101343' --- -## Sobre a verificação de e-mail +## About email verification -Você pode verificar seu endereço de e-mail depois de se inscrever em uma nova conta ou ao adicionar um novo endereço de e-mail. Se um endereço de e-mail não puder ser entregue ou retornar, ele será considerado como não verificado. +You can verify your email address after signing up for a new account, or when you add a new email address. If an email address is undeliverable or bouncing, it will be unverified. -Se você não verificar seu endereço de e-mail, não poderá: - - Criar ou bifurcar repositórios - - Criar problemas ou pull requests - - Fazer comentários sobre problemas, pull request ou commits - - Autorizar aplicativos do {% data variables.product.prodname_oauth_app %} - - Gerar tokens de acesso pessoais - - Receber notificações de e-mail - - Marcar repositórios com estrela - - Criar ou atualizar quadros de projeto, inclusive adicionando cartões - - Criar ou atualizar gists - - Criar ou usar o {% data variables.product.prodname_actions %} - - Patrocine desenvolvedores com {% data variables.product.prodname_sponsors %} +If you do not verify your email address, you will not be able to: + - Create or fork repositories + - Create issues or pull requests + - Comment on issues, pull requests, or commits + - Authorize {% data variables.product.prodname_oauth_app %} applications + - Generate {% data variables.product.pat_generic %}s + - Receive email notifications + - Star repositories + - Create or update project boards, including adding cards + - Create or update gists + - Create or use {% data variables.product.prodname_actions %} + - Sponsor developers with {% data variables.product.prodname_sponsors %} {% warning %} -**Avisos**: +**Warnings**: - {% data reusables.user-settings.no-verification-disposable-emails %} - {% data reusables.user-settings.verify-org-approved-email-domain %} {% endwarning %} -## Verificar endereço de e-mail +## Verifying your email address -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.emails %} -1. No seu endereço de email, clique em **Reenviar email de verificação**. - ![Link Reenviar email de verificação](/assets/images/help/settings/email-verify-button.png) -4. O {% data variables.product.prodname_dotcom %} enviará a você um e-mail com um link. Clicando nesse link, você será redirecionado para o painel do {% data variables.product.prodname_dotcom %} e verá um banner de confirmação. - ![Faixa confirmando que o seu email foi verificado](/assets/images/help/settings/email-verification-confirmation-banner.png) +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.emails %} +1. Under your email address, click **Resend verification email**. + ![Resend verification email link](/assets/images/help/settings/email-verify-button.png) +4. {% data variables.product.prodname_dotcom %} will send you an email with a link in it. After you click that link, you'll be taken to your {% data variables.product.prodname_dotcom %} dashboard and see a confirmation banner. + ![Banner confirming that your email was verified](/assets/images/help/settings/email-verification-confirmation-banner.png) -## Resolver problemas na verificação de e-mail +## Troubleshooting email verification -### Não é possível enviar verificação de e-mail +### Unable to send verification email {% data reusables.user-settings.no-verification-disposable-emails %} -### Página de erro depois de clicar no link de verificação +### Error page after clicking verification link -O link de verificação expira após 24 horas. Se você não verificar seu e-mail dentro de 24 horas, poderá solicitar outro link de verificação de e-mail. Para obter mais informações, confira "[Como confirmar seu endereço de email](/articles/verifying-your-email-address)". +The verification link expires after 24 hours. If you don't verify your email within 24 hours, you can request another email verification link. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)." -Se você clicar no link no e-mail de confirmação dentro de 24 horas e você for direcionado a uma página de erro, você deve garantir que está conectado à conta correta em {% data variables.product.product_location %}. +If you click on the link in the confirmation email within 24 hours and you are directed to an error page, you should ensure that you're signed into the correct account on {% data variables.location.product_location %}. -1. {% data variables.product.signout_link %} da sua conta pessoal em {% data variables.product.product_location %}. -2. Saia e reinicie o navegador. -3. {% data variables.product.signin_link %} para a sua conta pessoal em {% data variables.product.product_location %}. -4. Clique no link de verificação no e-mail que enviamos para você. +1. {% data variables.product.signout_link %} of your personal account on {% data variables.location.product_location %}. +2. Quit and restart your browser. +3. {% data variables.product.signin_link %} to your personal account on {% data variables.location.product_location %}. +4. Click on the verification link in the email we sent you. -## Leitura adicional +## Further reading -- "[Como alterar seu endereço de email principal](/articles/changing-your-primary-email-address)" +- "[Changing your primary email address](/articles/changing-your-primary-email-address)" diff --git a/translations/pt-BR/content/get-started/using-git/about-git-rebase.md b/translations/pt-BR/content/get-started/using-git/about-git-rebase.md index e631462ac6..07389b8bb1 100644 --- a/translations/pt-BR/content/get-started/using-git/about-git-rebase.md +++ b/translations/pt-BR/content/get-started/using-git/about-git-rebase.md @@ -1,5 +1,5 @@ --- -title: Sobre a troca de base do Git +title: About Git rebase redirect_from: - /rebase - /articles/interactive-rebase @@ -7,74 +7,68 @@ redirect_from: - /github/using-git/about-git-rebase - /github/getting-started-with-github/about-git-rebase - /github/getting-started-with-github/using-git/about-git-rebase -intro: 'O comando `git rebase` permite alterar com facilidade uma variedade de commits, modificando o histórico do seu repositório. É possível reordenar, editar ou combinar commits por squash.' +intro: 'The `git rebase` command allows you to easily change a series of commits, modifying the history of your repository. You can reorder, edit, or squash commits together.' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' -ms.openlocfilehash: 5ffa3cbb1fcb6c8c37e56e434b08018582a0ff2b -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145094795' --- -Normalmente, você usará `git rebase` para: +Typically, you would use `git rebase` to: -* Editar mensagens anteriores do commit -* Combinar vários commits em um -* Excluir ou reverter commits que não são mais necessários +* Edit previous commit messages +* Combine multiple commits into one +* Delete or revert commits that are no longer necessary {% warning %} -**Aviso**: como a alteração do seu histórico de commits pode dificultar as coisas para todos os outros que usam o repositório, é considerada uma prática inadequada fazer a troca de base de commits quando você já efetuou push deles para um repositório. Para saber como trocar a base com segurança no {% data variables.product.product_location %}, confira "[Sobre as mesclagens de solicitação de pull](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)". +**Warning**: Because changing your commit history can make things difficult for everyone else using the repository, it's considered bad practice to rebase commits when you've already pushed to a repository. To learn how to safely rebase on {% data variables.location.product_location %}, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)." {% endwarning %} -## Fazer rebase de commits em um branch +## Rebasing commits against a branch -Para fazer rebase de todos os commits entre outro branch e o estado do branch atual, você pode inserir o seguinte comando no shell (ou o prompt de comando para Windows, ou o terminal para Mac e Linux): +To rebase all the commits between another branch and the current branch state, you can enter the following command in your shell (either the command prompt for Windows, or the terminal for Mac and Linux): ```shell -$ git rebase --interactive other_branch_name +$ git rebase --interactive OTHER-BRANCH-NAME ``` -## Fazer rebase de commits em um momento específico +## Rebasing commits against a point in time -Para fazer rebase dos últimos commits em seu branch atual, você pode inserir o seguindo comando no shell: +To rebase the last few commits in your current branch, you can enter the following command in your shell: ```shell $ git rebase --interactive HEAD~7 ``` -## Comandos disponíveis ao fazer rebase +## Commands available while rebasing -Há seis comandos disponíveis para fazer rebase: +There are six commands available while rebasing:
pick
-
pick significa simplesmente que o commit está incluído. A reorganização da ordem dos comandos pick altera a ordem dos commits quando a troca de base está em andamento. Se você optar por não incluir um commit, será preciso excluir a linha toda.
+
pick simply means that the commit is included. Rearranging the order of the pick commands changes the order of the commits when the rebase is underway. If you choose not to include a commit, you should delete the entire line.
reword
-
O comando reword é semelhante a pick, mas depois que você usá-lo, o processo de troca de base será colocado em pausa e dará a você a chance de alterar a mensagem de commit. As alterações feitas pelo commit não são afetadas.
+
The reword command is similar to pick, but after you use it, the rebase process will pause and give you a chance to alter the commit message. Any changes made by the commit are not affected.
edit
-
Se você optar por edit um commit, terá a chance de alterar o commit, o que significa que pode adicionar ou alterar o commit por completo. Também é possível fazer mais commits antes de continuar com o rebase. Isso permite que você divida um commit grande em commits menores ou remova alterações equivocadas feitas em um commit.
+
If you choose to edit a commit, you'll be given the chance to amend the commit, meaning that you can add or change the commit entirely. You can also make more commits before you continue the rebase. This allows you to split a large commit into smaller ones, or, remove erroneous changes made in a commit.
squash
-
Esse comando permite combinar dois ou mais commits em um único commit. Um commit é combinado por squash no commit acima dele. O Git permite que você grave uma nova mensagem do commit descrevendo ambas as alterações.
+
This command lets you combine two or more commits into a single commit. A commit is squashed into the commit above it. Git gives you the chance to write a new commit message describing both changes.
fixup
-
Isso é semelhante a squash, mas o commit a ser mesclado tem a mensagem descartada. O commit simplesmente sofre merge no commit acima dele, e a mensagem do commit anterior é usado para descrever ambas as alterações.
+
This is similar to squash, but the commit to be merged has its message discarded. The commit is simply merged into the commit above it, and the earlier commit's message is used to describe both changes.
exec
-
Permite que você execute comandos de shell arbitrários em um commit.
+
This lets you run arbitrary shell commands against a commit.
-## Um exemplo de uso de `git rebase` +## An example of using `git rebase` -Independentemente do comando usado, o Git iniciará [o editor de texto padrão](/github/getting-started-with-github/associating-text-editors-with-git) e abrirá um arquivo que fornece detalhes dos commits no intervalo escolhido. Esse arquivo é parecido com este: +No matter which command you use, Git will launch [your default text editor](/github/getting-started-with-github/associating-text-editors-with-git) and open a file that details the commits in the range you've chosen. That file looks something like this: ``` pick 1fc6c95 Patch A @@ -100,18 +94,18 @@ pick 7b36971 something to move before patch B # ``` -Ao dividir essas informações, de cima para baixo, observamos que: +Breaking this information, from top to bottom, we see that: -- Sete commits são listados, o que indica que houve sete alterações entre nosso ponto de partida e o estado do nosso branch atual. -- Os commits escolhidos para rebase são classificados na ordem das alterações mais antigas (no topo) para as mais recentes (na base). -- Cada linha lista um comando (por padrão, `pick`), o SHA do commit e a mensagem de commit. Todo o procedimento `git rebase` gira em torno da manipulação dessas três colunas. As alterações feitas tem a *base trocada* no repositório. -- Após os commits, o Git informa o intervalo de commits com o qual estamos trabalhando (`41a72e6..7b36971`). -- Por fim, o Git fornece alguma ajuda informando a você os comandos que estão disponíveis ao fazer rebase dos commits. +- Seven commits are listed, which indicates that there were seven changes between our starting point and our current branch state. +- The commits you chose to rebase are sorted in the order of the oldest changes (at the top) to the newest changes (at the bottom). +- Each line lists a command (by default, `pick`), the commit SHA, and the commit message. The entire `git rebase` procedure centers around your manipulation of these three columns. The changes you make are *rebased* onto your repository. +- After the commits, Git tells you the range of commits we're working with (`41a72e6..7b36971`). +- Finally, Git gives some help by telling you the commands that are available to you when rebasing commits. -## Leitura adicional +## Further reading -- "[Como usar a troca de base do Git](/articles/using-git-rebase)" -- [O capítulo "Ramificação do Git" do _livro Pro Git_](https://git-scm.com/book/en/Git-Branching-Rebasing) -- [O capítulo "Troca de base interativa" do _livro Pro Git_](https://git-scm.com/book/en/Git-Tools-Rewriting-History#_changing_multiple) -- "[Mesclagem squash de commits com a troca de base](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)" -- "[Como sincronizar seu branch](/desktop/contributing-to-projects/syncing-your-branch)" na documentação do {% data variables.product.prodname_desktop %} +- "[Using Git rebase](/articles/using-git-rebase)" +- [The "Git Branching" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Branching-Rebasing) +- [The "Interactive Rebasing" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Tools-Rewriting-History#_changing_multiple) +- "[Squashing commits with rebase](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)" +- "[Syncing your branch](/desktop/contributing-to-projects/syncing-your-branch)" in the {% data variables.product.prodname_desktop %} documentation diff --git a/translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md index 36ec57ec0f..672cc12698 100644 --- a/translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md +++ b/translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md @@ -1,49 +1,43 @@ --- -title: Dividir uma subpasta em um novo repositório +title: Splitting a subfolder out into a new repository redirect_from: - /articles/splitting-a-subpath-out-into-a-new-repository - /articles/splitting-a-subfolder-out-into-a-new-repository - /github/using-git/splitting-a-subfolder-out-into-a-new-repository - /github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository - /github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository -intro: Você pode transformar uma pasta em um repositório do Git repository em um novo repositório. +intro: You can turn a folder within a Git repository into a brand new repository. versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' shortTitle: Splitting a subfolder -ms.openlocfilehash: 21467b459f1e7af1dd28e5b7a20c962786aed2b5 -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147875562' --- -Se você criar um clone do repositório, não perderá nenhuma alteração ou histórico do Git quando dividir uma pasta e criar um repositório separado. +If you create a new clone of the repository, you won't lose any of your Git history or changes when you split a folder into a separate repository. {% data reusables.command_line.open_the_multi_os_terminal %} -2. Altere o diretório de trabalho atual para o local em que deseja criar o novo repositório. +2. Change the current working directory to the location where you want to create your new repository. -4. Clone o repositório que contém a subpasta. +4. Clone the repository that contains the subfolder. ```shell - $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME + $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME ``` -4. Altere o diretório de trabalho atual para o repositório clonado. +4. Change the current working directory to your cloned repository. ```shell - $ cd REPOSITORY-NAME + $ cd REPOSITORY-NAME ``` -5. Para filtrar a subpasta do restante dos arquivos no repositório, execute [`git filter-repo`](https://github.com/newren/git-filter-repo), fornecendo estas informações: - - `FOLDER-NAME`: a pasta dentro do seu projeto onde você deseja criar um repositório separado. +5. To filter out the subfolder from the rest of the files in the repository, run [`git filter-repo`](https://github.com/newren/git-filter-repo), supplying this information: + - `FOLDER-NAME`: The folder within your project where you'd like to create a separate repository. {% windows %} {% tip %} - **Dica:** usuários do Windows devem usar `/` para delimitar pastas. + **Tip:** Windows users should use `/` to delimit folders. {% endtip %} @@ -53,44 +47,44 @@ Se você criar um clone do repositório, não perderá nenhuma alteração ou hi $ git filter-repo --path FOLDER-NAME1/ --path FOLDER-NAME2/ # Filter the specified branch in your directory and remove empty commits > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89) - > Ref 'refs/heads/BRANCH-NAME' was rewritten + > Ref 'refs/heads/BRANCH-NAME' was rewritten ``` - Agora o repositório deve conter apenas os arquivos que estava(m) na(s) subpasta(s). + The repository should now only contain the files that were in your subfolder(s). -6. [Crie um repositório](/articles/creating-a-new-repository/) no {% data variables.product.product_name %}. +6. [Create a new repository](/articles/creating-a-new-repository/) on {% data variables.product.product_name %}. -7. Na parte superior do seu novo repositório na página de Configuração Rápida de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, clique em {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar a URL do repositório remoto. - - ![Campo Copy remote repository URL (Copiar URL do repositório remote)](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) +7. At the top of your new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL. + + ![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) {% tip %} - **Dica:** Para obter informações sobre a diferença entre URLs HTTPS e SSH, confira "[Sobre repositórios remotos](/github/getting-started-with-github/about-remote-repositories)". + **Tip:** For information on the difference between HTTPS and SSH URLs, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)." {% endtip %} -8. Verifique o nome remoto do repositório. Por exemplo, `origin` ou `upstream` são duas opções comuns. +8. Check the existing remote name for your repository. For example, `origin` or `upstream` are two common choices. ```shell $ git remote -v - > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (push) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (push) ``` -9. Configure uma nova URL remota para o novo repositório usando o nome e a URL do repositório remote copiados na etapa 7. +9. Set up a new remote URL for your new repository using the existing remote name and the remote repository URL you copied in step 7. ```shell - git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git + git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git ``` -10. Verifique se a URL remota mudou com o nome do novo repositório. +10. Verify that the remote URL has changed with your new repository name. ```shell $ git remote -v # Verify new remote URL - > origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (push) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (push) ``` -11. Faça push das alterações para o novo repositório no {% data variables.product.product_name %}. +11. Push your changes to the new repository on {% data variables.product.product_name %}. ```shell - git push -u origin BRANCH-NAME + git push -u origin BRANCH-NAME ``` diff --git a/translations/pt-BR/content/get-started/using-github/github-command-palette.md b/translations/pt-BR/content/get-started/using-github/github-command-palette.md index 3e647c3be7..d5a12c7c75 100644 --- a/translations/pt-BR/content/get-started/using-github/github-command-palette.md +++ b/translations/pt-BR/content/get-started/using-github/github-command-palette.md @@ -1,234 +1,229 @@ --- -title: Paleta de comando do GitHub -intro: 'Use a paleta de comandos em {% data variables.product.product_name %} para navegar, pesquisar e executar comandos diretamente do seu teclado.' +title: GitHub Command Palette +intro: 'Use the command palette in {% data variables.product.product_name %} to navigate, search, and run commands directly from your keyboard.' versions: feature: command-palette shortTitle: GitHub Command Palette -ms.openlocfilehash: 1b9b8ecfa5e8824bcf7032c51250238ff5f8e8a7 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147423137' --- + {% data reusables.command-palette.beta-note %} -## Sobre a {% data variables.product.prodname_command_palette %} +## About the {% data variables.product.prodname_command_palette %} -Você pode navegar, pesquisar e executar comandos em {% data variables.product.product_name %} com o {% data variables.product.prodname_command_palette %}. A paleta de comandos é uma forma personalizada de mostrar sugestões com base no seu contexto atual e nos recursos que você usou recentemente. Você pode abrir a paleta de comandos com um atalho de teclado de qualquer lugar em {% data variables.product.product_name %}, que economiza tempo e mantém as mãos no teclado. +You can navigate, search, and run commands on {% data variables.product.product_name %} with the {% data variables.product.prodname_command_palette %}. The command palette is an on-demand way to show suggestions based on your current context and resources you've used recently. You can open the command palette with a keyboard shortcut from anywhere on {% data variables.product.product_name %}, which saves you time and keeps your hands on the keyboard. -### Navegação rápida +### Fast navigation -Ao abrir a paleta de comandos, as sugestões são otimizadas para facilitar o acesso de qualquer lugar em um repositório, uma conta pessoal, ou uma organização para páginas de nível superior, como a página Problemas. Se o local que você deseja não estiver listado, comece a digitar o nome ou número para a localização refinar as sugestões. +When you open the command palette, the suggestions are optimized to give you easy access from anywhere in a repository, personal account, or organization to top-level pages like the Issues page. If the location you want isn't listed, start entering the name or number for the location to refine the suggestions. -![Sugestões da paleta de comandos](/assets/images/help/command-palette/command-palette-navigation-repo-default.png) +![Command palette repository suggestions](/assets/images/help/command-palette/command-palette-navigation-repo-default.png) -### Acesso fácil aos comandos +### Easy access to commands -A capacidade de executar comandos diretamente do seu teclado, sem navegar por meio de uma série de menus pode alterar a forma como você usa {% data variables.product.prodname_dotcom %}. Por exemplo, você pode alternar temas com algumas teclas pressionadas, facilitando a alternância entre temas à medida que as suas necessidades forem mudando. +The ability to run commands directly from your keyboard, without navigating through a series of menus, may change the way you use {% data variables.product.prodname_dotcom %}. For example, you can switch themes with a few keystrokes, making it easy to toggle between themes as your needs change. -![Alterar tema da paleta de comandos](/assets/images/help/command-palette/command-palette-command-change-theme.png) +![Command palette change theme](/assets/images/help/command-palette/command-palette-command-change-theme.png) -## Como abrir a {% data variables.product.prodname_command_palette %} +## Opening the {% data variables.product.prodname_command_palette %} -Abra a paleta de comandos usando um dos seguintes atalhos padrão do teclado: -- Windows e Linux: CTRL+K ou CTRL+Alt+K -- Mac: Comando+K ou Comando+Opção+K +Open the command palette using one of the following default keyboard shortcuts: +- Windows and Linux: Ctrl+K or Ctrl+Alt+K +- Mac: Command+K or Command+Option+K -Você pode personalizar os atalhos de teclado usados para abrir a paleta de comandos na [seção Acessibilidade](https://github.com/settings/accessibility) das configurações do usuário. Para obter mais informações, confira "[Como personalizar seus atalhos de teclado da {% data variables.product.prodname_command_palette %}](#customizing-your-github-command-palette-keyboard-shortcuts)". +You can customize the keyboard shortcuts you use to open the command palette in the [Accessibility section](https://github.com/settings/accessibility) of your user settings. For more information, see "[Customizing your {% data variables.product.prodname_command_palette %} keyboard shortcuts](#customizing-your-github-command-palette-keyboard-shortcuts)." -Quando você abrir a paleta de comandos, ela mostra sua localização no canto superior esquerdo e a usa como o escopo de sugestões (por exemplo, a organização `mashed-avocado`). +When you open the command palette, it shows your location at the top left and uses it as the scope for suggestions (for example, the `mashed-avocado` organization). -![Lançamento da paleta de comando](/assets/images/help/command-palette/command-palette-launch.png) +![Command palette launch](/assets/images/help/command-palette/command-palette-launch.png) {% note %} -**Observações:** -- Se você estiver editando um texto Markdown, abra a paleta de comandos com CTRL+Alt+K (Windows e Linux) ou Command+Option+K (Mac).{% ifversion projects-v2 %} -- Se você estiver trabalhando em um {% data variables.projects.project_v2 %}, uma paleta de comandos específica do projeto será exibida. Para obter mais informações, confira "[Personalizar uma exibição](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)".{% endif %} +**Notes:** +- If you are editing Markdown text, open the command palette with Ctrl+Alt+K (Windows and Linux) or Command+Option+K (Mac).{% ifversion projects-v2 %} +- If you are working on a {% data variables.projects.project_v2 %}, a project-specific command palette is displayed instead. For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)."{% endif %} {% endnote %} -### Personalizando seus atalhos de teclado de {% data variables.product.prodname_command_palette %} +### Customizing your {% data variables.product.prodname_command_palette %} keyboard shortcuts -Os atalhos de teclado padrão usados para abrir a paleta de comandos podem entrar em conflito com os atalhos de teclado padrão do sistema operacional e do navegador. Você tem a opção de personalizar os atalhos de teclado na [seção Acessibilidade](https://github.com/settings/accessibility) das configurações da conta. Nas configurações da paleta de comandos, você pode personalizar os atalhos de teclado para abrir a paleta de comandos em modo de pesquisa e modo de comando. +The default keyboard shortcuts used to open the command palette may conflict with your default OS and browser keyboard shortcuts. You have the option to customize your keyboard shortcuts in the [Accessibility section](https://github.com/settings/accessibility) of your account settings. In the command palette settings, you can customize the keyboard shortcuts for opening the command palette in both search mode and command mode. -![Configurações de atalho da paleta de teclado](/assets/images/help/command-palette/command-palette-keyboard-shortcut-settings.png) -## Navegando com {% data variables.product.prodname_command_palette %} +![Command palette keyboard shortcut settings](/assets/images/help/command-palette/command-palette-keyboard-shortcut-settings.png) +## Navigating with the {% data variables.product.prodname_command_palette %} -Você pode usar a paleta de comandos para navegar para qualquer página que você tenha acesso em {% data variables.product.product_name %}. +You can use the command palette to navigate to any page that you have access to on {% data variables.product.product_name %}. {% data reusables.command-palette.open-palette %} -2. Comece a digitar o caminho para o qual você deseja navegar. As sugestões na paleta de comandos são alteradas para corresponder ao seu texto. +2. Start typing the path you want to navigate to. The suggestions in the command palette change to match your text. - ![Escopo atual da paleta de navegação](/assets/images/help/command-palette/command-palette-navigation-current-scope.png) + ![Command palette navigation current scope](/assets/images/help/command-palette/command-palette-navigation-current-scope.png) {% data reusables.command-palette.change-scope %} - Você também pode usar teclas pressionadas para restringir a sua pesquisa. Para obter mais informações, confira "[Funções de pressionamento de tecla](#keystroke-functions)". + You can also use keystrokes to narrow your search. For more information, see "[Keystroke functions](#keystroke-functions)." -4. Termine de inserir no caminho ou use as teclas de seta para destacar o caminho que você deseja a partir da lista de sugestões. +4. Finish entering the path, or use the arrow keys to highlight the path you want from the list of suggestions. -5. Use ENTER para ir para o local escolhido. Como alternativa, use CTRL+ENTER (Windows e Linux) ou Comando+ENTER (Mac) para abrir o local em uma nova guia do navegador. +5. Use Enter to jump to your chosen location. Alternatively, use Ctrl+Enter (Windows and Linux) or Command+Enter (Mac) to open the location in a new browser tab. -## Pesquisando com {% data variables.product.prodname_command_palette %} +## Searching with the {% data variables.product.prodname_command_palette %} -Você pode usar a paleta de comandos para pesquisar qualquer coisa em {% data variables.product.product_location %}. +You can use the command palette to search for anything on {% data variables.location.product_location %}. {% data reusables.command-palette.open-palette %} {% data reusables.command-palette.change-scope %} -3. Opcionalmente, use teclas pressionadas para encontrar tipos específicos de recursos: +3. Optionally, use keystrokes to find specific types of resource: - - # Pesquisar problemas, solicitações de pull, discussões e projetos - - ! Pesquisar projetos - - @ Pesquisar usuários, organizações e repositórios - - / Pesquisar arquivos no escopo de um repositório + - # Search for issues, pull requests, discussions, and projects + - ! Search for projects + - @ Search for users, organizations, and repositories + - / Search for files within a repository scope - ![Arquivos de pesquisa da paleta de comando](/assets/images/help/command-palette/command-palette-search-files.png) + ![Command palette search files](/assets/images/help/command-palette/command-palette-search-files.png) -4. Comece a inserir seus termos de pesquisa. A paleta de comandos irá oferecer um intervalo de pesquisas sugeridas com base no seu escopo de pesquisa. +4. Begin entering your search terms. The command palette will offer you a range of suggested searches based on your search scope. {% tip %} - Você também pode usar a sintaxe completa da pesquisa integrada de {% data variables.product.prodname_dotcom %} dentro da paleta de comando. Para obter mais informações, confira "[Como fazer pesquisas de informações no {% data variables.product.prodname_dotcom %}](/search-github)". + You can also use the full syntax of {% data variables.product.prodname_dotcom %}'s integrated search within the command palette. For more information, see "[Searching for information on {% data variables.product.prodname_dotcom %}](/search-github)." {% endtip %} -5. Use as teclas de direção para realçar o resultado da pesquisa desejado e ENTER para ir ao local escolhido. Como alternativa, use CTRL+ENTER (Windows e Linux) ou Comando+ENTER (Mac) para abrir o local em uma nova guia do navegador. +5. Use the arrow keys to highlight the search result you want and use Enter to jump to your chosen location. Alternatively, use Ctrl+Enter (Windows and Linux) or Command+Enter (Mac) to open the location in a new browser tab. -## Executando comandos a partir de {% data variables.product.prodname_command_palette %} +## Running commands from the {% data variables.product.prodname_command_palette %} -Você pode usar o {% data variables.product.prodname_command_palette %} para executar comandos. Por exemplo, você pode criar um novo repositório ou problema ou alterar seu tema. Quando você executa um comando, o local para sua ação é determinado pela página subjacente ou pelo escopo mostrado na paleta de comandos. +You can use the {% data variables.product.prodname_command_palette %} to run commands. For example, you can create a new repository or issue, or change your theme. When you run a command, the location for its action is determined by either the underlying page or the scope shown in the command palette. -- Os comandos de pull request e problemas sempre são executados na página subjacente. -- Os comandos de alto nível, por exemplo, comandos de repositório, são executados no escopo exibido na paleta de comandos. +- Pull request and issue commands always run on the underlying page. +- Higher-level commands, for example, repository commands, run in the scope shown in the command palette. -Para ver uma lista completa de comandos compatíveis, confira "[Referência da {% data variables.product.prodname_command_palette %}](#github-command-palette-reference)". +For a full list of supported commands, see "[{% data variables.product.prodname_command_palette %} reference](#github-command-palette-reference)." -1. Os atalhos de teclado padrão usados para abrir a paleta de comandos no modo de comando são CTRL+SHIFT+K (Windows e Linux) ou Comando+SHIFT+K (Mac). Se você já tiver a paleta de comandos aberta, pressione > para alternar para o modo de comando. {% data variables.product.prodname_dotcom %} sugere comandos baseados na sua localização. +1. The default keyboard shortcuts to open the command palette in command mode are Ctrl+Shift+K (Windows and Linux) or Command+Shift+K (Mac). If you already have the command palette open, press > to switch to command mode. {% data variables.product.prodname_dotcom %} suggests commands based on your location. - ![Modo de comando da paleta de comando](/assets/images/help/command-palette/command-palette-command-mode.png) + ![Command palette command mode](/assets/images/help/command-palette/command-palette-command-mode.png) {% data reusables.command-palette.change-scope %} -3. Se o comando que você deseja não for exibido, verifique seu escopo e, em seguida, comece a digitar o nome do comando na caixa de texto. +3. If the command you want is not displayed, check your scope then start entering the command name in the text box. -4. Use as teclas de direção para realçar o comando desejado e ENTER para executá-lo. +4. Use the arrow keys to highlight the command you want and use Enter to run it. -## Fechando a paleta de comandos +## Closing the command palette -Quando a paleta de comando está ativa, você pode usar um dos seguintes atalhos de teclado para fechar a paleta de comandos: +When the command palette is active, you can use one of the following keyboard shortcuts to close the command palette: -- Modo de pesquisa e navegação: Esc ou CTRL+K (Windows e Linux) Comando+K (Mac) -- Modo de comando: Esc ou CTRL+SHIFT+K (Windows e Linux) Comando+SHIFT+K (Mac) +- Search and navigation mode: Esc or Ctrl+K (Windows and Linux) Command+K (Mac) +- Command mode: Esc or Ctrl+Shift+K (Windows and Linux) Command+Shift+K (Mac) -Se você tiver personalizado os atalhos da paleta de comandos nas configurações de acessibilidade, seus atalhos de teclado personalizados serão usados tanto para abrir quanto para fechar a paleta de comandos. +If you have customized the command palette keyboard shortcuts in the Accessibility settings, your customized keyboard shortcuts will be used for both opening and closing the command palette. -## Referência de {% data variables.product.prodname_command_palette %} +## {% data variables.product.prodname_command_palette %} reference -### Funções de keystrokes +### Keystroke functions -Essas keystrokes estão disponíveis quando a paleta de comandos está nos modos de navegação e pesquisa, isto é, elas não estão disponíveis no modo de comando. +These keystrokes are available when the command palette is in navigation and search modes, that is, they are not available in command mode. -| Teclas | Função | +| Keystroke | Function | | :- | :- | -|>| Entre no modo de comando. Para obter mais informações, confira "[Como executar comandos na {% data variables.product.prodname_command_palette %}](#running-commands-from-the-github-command-palette)". | -|#| Pesquisa problemas, pull requests, discussões e projetos. Para obter mais informações, confira "[Como fazer pesquisas com a {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)".| -|@| Pesquisa usuários, organizações e repositórios. Para obter mais informações, confira "[Como fazer pesquisas com a {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)".| -|/| Pesquisar arquivos dentro de um escopo ou repositórios do repositório dentro do escopo da organização. Para obter mais informações, confira "[Como fazer pesquisas com a {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)". | -|!| Pesquisar apenas projetos. Para obter mais informações, confira "[Como fazer pesquisas com a {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)".| -|CTRL+C ou Comando+C| Copiar URL de pesquisa ou navegação para o resultado destacado na área de transferência.| -|Enter| Pule para o resultado destacado ou execute o comando destacado.| -|CTRL+ENTER ou Comando+ENTER| Abra o resultado da pesquisa ou navegação destacada em uma nova aba do navegador.| -|?| Exibir ajuda na paleta de comandos.| +|>| Enter command mode. For more information, see "[Running commands from the {% data variables.product.prodname_command_palette %}](#running-commands-from-the-github-command-palette)." | +|#| Search for issues, pull requests, discussions, and projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."| +|@| Search for users, organizations, and repositories. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."| +|/| Search for files within a repository scope or repositories within an organization scope. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." | +|!| Search just for projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."| +|Ctrl+C or Command+C| Copy the search or navigation URL for the highlighted result to the clipboard.| +|Enter| Jump to the highlighted result or run the highlighted command.| +|Ctrl+Enter or Command+Enter| Open the highlighted search or navigation result in a new brower tab.| +|?| Display help within the command palette.| -### Comandos globais +### Global commands -Estes comandos estão disponíveis em todos os escopos. +These commands are available from all scopes. -| Comando | Comportamento| +| Command | Behavior| | :- | :- | :- | -|`Import repository`|Criar um novo repositório importando um projeto de outro sistema de controle de versão. Para obter mais informações, confira "[Como importar um repositório com o importador do GitHub](/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)". | -|`New gist`|Abra um novo gist. Para obter mais informações, confira "[Como criar um gist](/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)". | -|`New organization`|Criar uma nova organização Para obter mais informações, confira "[Como criar uma organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". | -|`New project`|Criar um novo quadro de projeto. Para obter mais informações, confira "[Como criar um projeto](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project)". | -|`New repository`|Criar um novo repositório a partir do zero. Para obter mais informações, confira "[Como criar um repositório](/repositories/creating-and-managing-repositories/creating-a-new-repository)". | -|`Switch theme to `|Mude diretamente para um tema diferente para a interface do usuário. Para obter mais informações, confira "[Como gerenciar suas configurações de tema](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings)". | +|`Import repository`|Create a new repository by importing a project from another version control system. For more information, see "[Importing a repository with GitHub importer](/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)." | +|`New gist`|Open a new gist. For more information, see "[Creating a gist](/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)." | +|`New organization`|Create a new organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." | +|`New project`|Create a new project board. For more information, see "[Creating a project](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project)." | +|`New repository`|Create a new repository from scratch. For more information, see "[Creating a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository)." | +|`Switch theme to `|Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings)." | -### Comandos da organização +### Organization commands -Esses comandos estão disponíveis somente dentro do escopo de uma organização. +These commands are available only within the scope of an organization. -| Comando | Comportamento| +| Command | Behavior| | :- | :- | -| `New team`| Crie uma nova equipe na organização atual. Para obter mais informações, confira "[Como criar uma equipe](/organizations/organizing-members-into-teams/creating-a-team)". +| `New team`| Create a new team in the current organization. For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)." -### Comandos do repositório +### Repository commands -A maioria desses comandos está disponível apenas na página inicial do repositório. Se um comando também estiver disponível em outras páginas, isso será mencionado na coluna de comportamento. +Most of these commands are available only on the home page of the repository. If a command is also available on other pages, this is noted in the behavior column. -| Comando | Comportamento| +| Command | Behavior| | :- | :- | -|`Clone repository: `|Copie a URL necessária para clonar o repositório usando {% data variables.product.prodname_cli %}, HTTP ou SSH para a área de transferência. Para obter mais informações, confira "[Como clonar um repositório](/repositories/creating-and-managing-repositories/cloning-a-repository)".| -|`New discussion`|Criar uma nova discussão no repositório. Para obter mais informações, confira "[Como criar um repositório](/discussions/quickstart#creating-a-new-discussion)".| -|`New file`|Criar um novo arquivo a partir de qualquer página no repositório. Para obter mais informações, confira "[Como adicionar um arquivo a um repositório](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)". -|`New issue`|Abra um novo problema de qualquer página no repositório. Para obter mais informações, confira "[Como criar um problema](/issues/tracking-your-work-with-issues/creating-an-issue)".| -|`Open in new codespace`|Criar e abrir um codespace para este repositório. Para obter mais informações, confira "[Como criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace)".| -|`Open in github.dev editor`|Abra o repositório atual no editor github.dev. Para obter mais informações, confira "[Como abrir o editor baseado na Web](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)".| +|`Clone repository: `|Copy the URL needed to clone the repository using {% data variables.product.prodname_cli %}, HTTPS, or SSH to the clipboard. For more information, see "[Cloning a repository](/repositories/creating-and-managing-repositories/cloning-a-repository)."| +|`New discussion`|Create a new discussion in the repository. For more information, see "[Creating a new discussion](/discussions/quickstart#creating-a-new-discussion)."| +|`New file`|Create a new file from any page in the repository. For more information, see "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)." +|`New issue`|Open a new issue from any page in the repository. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue)."| +|`Open in new codespace`|Create and open a codespace for this repository. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."| +|`Open in github.dev editor`|Open the current repository in the github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)."| -### Comandos de arquivos +### File commands -Estes comandos só estão disponíveis quando você abre a paleta de comandos a partir de um arquivo em um repositório. +These commands are available only when you open the command palette from a file in a repository. -| Comando | Comportamento| +| Command | Behavior| | :- | :- | -|`Copy permalink`|Crie um link para o arquivo que inclui o atual commit SHA e copie o link para a área de transferência. Para obter mais informações, confira "[Como obter links permanentes para arquivos](/repositories/working-with-files/using-files/getting-permanent-links-to-files#press-y-to-permalink-to-a-file-in-a-specific-commit)". -|`Open in github.dev editor`|Abra o arquivo exibido atualmente no editor github.dev. Para obter mais informações, confira "[Como abrir o editor baseado na Web](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)".| +|`Copy permalink`|Create a link to the file that includes the current commit SHA and copy the link to the clipboard. For more information, see "[Getting permanent links to files](/repositories/working-with-files/using-files/getting-permanent-links-to-files#press-y-to-permalink-to-a-file-in-a-specific-commit)." +|`Open in github.dev editor`|Open the currently displayed file in github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)."| -### Comandos de discussão +### Discussion commands -Estes comandos só estão disponíveis quando você abre a paleta de comandos em uma discussão. Eles atuam na sua página atual e não são afetados pelo escopo definido na paleta de comando. +These commands are available only when you open the command palette from a discussion. They act on your current page and are not affected by the scope set in the command palette. -| Comando | Comportamento| +| Command | Behavior| | :- | :- | -|`Delete discussion...`|Excluir permanentemente a discussão. Para obter mais informações, confira "[Gerenciar discussões](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion)". -|`Edit discussion body`|Abra o texto principal da discussão que está pronto para edição. -|`Subscribe`/`unsubscribe`|Opte por participar ou não receber notificações de adições à discussão. Para obter mais informações, confira "[Sobre as notificações](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)". -|`Transfer discussion...`|Mover a discussão para um repositório diferente. Para obter mais informações, confira "[Gerenciar discussões](/discussions/managing-discussions-for-your-community/managing-discussions#transferring-a-discussion)". +|`Delete discussion...`|Permanently delete the discussion. For more information, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion)." +|`Edit discussion body`|Open the main body of the discussion ready for editing. +|`Subscribe`/`unsubscribe`|Opt in or out of notifications for additions to the discussion. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." +|`Transfer discussion...`|Move the discussion to a different repository. For more information, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions#transferring-a-discussion)." -### Comandos de problemas +### Issue commands -Estes comandos estão disponíveis somente quando você abre a paleta de comandos em um problema. Eles atuam na sua página atual e não são afetados pelo escopo definido na paleta de comando. +These commands are available only when you open the command palette from an issue. They act on your current page and are not affected by the scope set in the command palette. -| Comando | Comportamento| +| Command | Behavior| | :- | :- | -|`Close`/`reopen issue`|Fechar ou reabrir o problema atual. Para obter mais informações, confira "[Sobre os problemas](/issues/tracking-your-work-with-issues/about-issues)".| -|`Convert issue to discussion...`|Converter o problema atual em uma discussão. Para obter mais informações, confira "[Como moderar discussões](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)". -|`Delete issue...`|Exclua o problema atual. Para obter mais informações, confira "[Como excluir um problema](/issues/tracking-your-work-with-issues/deleting-an-issue)".| -|`Edit issue body`|Abra o texto principal do problema que está pronto para edição. -|`Edit issue title`|Abra o título do problema que está pronto para edição. -|`Lock issue`|Limitar novos comentários a usuários com acesso de gravação ao repositório. Para obter mais informações, confira "[Como bloquear conversas](/communities/moderating-comments-and-conversations/locking-conversations)". -|`Pin`/`unpin issue`|Altere se o problema é exibido ou não na seção de problemas fixados para o repositório. Para obter mais informações, confira "[Como fixar um problema no seu repositório](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)".| -|`Subscribe`/`unsubscribe`|Opte por partiricpar ou não receber notificações de alterações nesse problema. Para obter mais informações, confira "[Sobre as notificações](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)". -|`Transfer issue...`|Transferir o problema para outro repositório. Para obter mais informações, confira "[Como transferir um problema para outro repositório](/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)".| +|`Close`/`reopen issue`|Close or reopen the current issue. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)."| +|`Convert issue to discussion...`|Convert the current issue into a discussion. For more information, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)." +|`Delete issue...`|Delete the current issue. For more information, see "[Deleting an issue](/issues/tracking-your-work-with-issues/deleting-an-issue)."| +|`Edit issue body`|Open the main body of the issue ready for editing. +|`Edit issue title`|Open the title of the issue ready for editing. +|`Lock issue`|Limit new comments to users with write access to the repository. For more information, see "[Locking conversations](/communities/moderating-comments-and-conversations/locking-conversations)." +|`Pin`/`unpin issue`|Change whether or not the issue is shown in the pinned issues section for the repository. For more information, see "[Pinning an issue to your repository](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)."| +|`Subscribe`/`unsubscribe`|Opt in or out of notifications for changes to this issue. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." +|`Transfer issue...`|Transfer the issue to another repository. For more information, see "[Transferring an issue to another repository](/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)."| -### Comandos de pull request +### Pull request commands -Estes comandos só estão disponíveis quando você abre a paleta de comandos a partir de um pull request. Eles atuam na sua página atual e não são afetados pelo escopo definido na paleta de comando. +These commands are available only when you open the command palette from a pull request. They act on your current page and are not affected by the scope set in the command palette. -| Comando | Comportamento| +| Command | Behavior| | :- | :- | -|`Close`/`reopen pull request`|Feche ou reabra o pull request atual. Para obter mais informações, confira "[Sobre as solicitações de pull](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)".| -|`Convert to draft`/`Mark pull request as ready for review`|Altere o estado do pull request para mostrá-lo como pronto ou não pronto para revisão. Para obter mais informações, confira "[Como alterar o estado de uma solicitação de pull](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)".| -|`Copy current branch name`| Adicione o nome do branch principal ao pull request na área de transferência. -|`Edit pull request body`|Abra o texto principal do pull request que está pronto para edição. -|`Edit pull request title`|Abra o título do pull request que está pronto para edição. -|`Open in new codespace`|Crie e abra um codespace para o branch principal do pull request. Para obter mais informações, confira "[Como criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". -|`Subscribe`/`unsubscribe`|Opte por receber ou não receber notificações para alterações desse pull request. Para obter mais informações, confira "[Sobre as notificações](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)". -|`Update current branch`|Atualize o branch principal do pull request com alterações do branch base. Isso só está disponível para pull requests que apontam para o branch padrão do repositório. Para obter mais informações, confira "[Sobre os branches](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)".| +|`Close`/`reopen pull request`|Close or reopen the current pull request. For more information, see "[About pull requests](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."| +|`Convert to draft`/`Mark pull request as ready for review`|Change the state of the pull request to show it as ready, or not ready, for review. For more information, see "[Changing the state of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)."| +|`Copy current branch name`| Add the name of the head branch for the pull request to the clipboard. +|`Edit pull request body`|Open the main body of the pull request ready for editing. +|`Edit pull request title`|Open the title of the pull request ready for editing. +|`Open in new codespace`|Create and open a codespace for the head branch of the pull request. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)." +|`Subscribe`/`unsubscribe`|Opt in or out of notifications for changes to this pull request. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." +|`Update current branch`|Update the head branch of the pull request with changes from the base branch. This is available only for pull requests that target the default branch of the repository. For more information, see "[About branches](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)."| diff --git a/translations/pt-BR/content/get-started/using-github/github-mobile.md b/translations/pt-BR/content/get-started/using-github/github-mobile.md index f82af74711..74cd8e8b2a 100644 --- a/translations/pt-BR/content/get-started/using-github/github-mobile.md +++ b/translations/pt-BR/content/get-started/using-github/github-mobile.md @@ -1,6 +1,6 @@ --- title: GitHub Mobile -intro: 'Faça triagem, colabore e gerencie seu trabalho no {% data variables.product.product_name %} do seu dispositivo móvel.' +intro: 'Triage, collaborate, and manage your work on {% data variables.product.product_name %} from your mobile device.' versions: fpt: '*' ghes: '*' @@ -11,87 +11,84 @@ redirect_from: - /get-started/using-github/github-for-mobile - /github/getting-started-with-github/github-for-mobile - /github/getting-started-with-github/using-github/github-for-mobile -ms.openlocfilehash: a9af0848fdc26c5efd3dfb2d00076e3af5fb00bc -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147508445' --- -## Sobre o {% data variables.product.prodname_mobile %} + +## About {% data variables.product.prodname_mobile %} {% data reusables.mobile.about-mobile %} -O {% data variables.product.prodname_mobile %} oferece a você uma forma de realizar trabalhos de alto impacto no {% data variables.product.product_name %} rapidamente e em qualquer lugar. O {% data variables.product.prodname_mobile %} é uma forma segura e confiável de acessar seus dados do {% data variables.product.product_name %} por meio de um aplicativo cliente interno e confiável. +{% data variables.product.prodname_mobile %} gives you a way to do high-impact work on {% data variables.product.product_name %} quickly and from anywhere. {% data variables.product.prodname_mobile %} is a safe and secure way to access your {% data variables.product.product_name %} data through a trusted, first-party client application. -Com o {% data variables.product.prodname_mobile %} você pode: +With {% data variables.product.prodname_mobile %} you can: -- Gerenciar, fazer triagem e limpar notificações -- Leia, analisar e colaborar em problemas e pull requests -- Pesquisar, navegar e interagir com usuários, repositórios e organizações -- Receber uma notificação por push quando alguém mencionar seu nome de usuário {% ifversion fpt or ghec %}– Proteger sua conta do GitHub.com com a autenticação de dois fatores -- Verificar as tentativas de entrada em dispositivos não reconhecidos{% endif %} +- Manage, triage, and clear notifications +- Read, review, and collaborate on issues and pull requests +- Edit files in pull requests +- Search for, browse, and interact with users, repositories, and organizations +- Receive a push notification when someone mentions your username +{% ifversion fpt or ghec %}- Secure your GitHub.com account with two-factor authentication +- Verify your sign in attempts on unrecognized devices{% endif %} -Para obter mais informações sobre as notificações do {% data variables.product.prodname_mobile %}, confira "[Como configurar notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)". +For more information about notifications for {% data variables.product.prodname_mobile %}, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)." -{% ifversion fpt or ghec %}– Para obter mais informações sobre autenticação de dois fatores usando {% data variables.product.prodname_mobile %}, veja "[Configurando {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile) e [Autenticação usando {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication##verifying-with-github-mobile)". {% endif %} +{% ifversion fpt or ghec %}- For more information on two-factor authentication using {% data variables.product.prodname_mobile %}, see "[Configuring {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile) and [Authenticating using {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication##verifying-with-github-mobile)." {% endif %} -## Como instalar o {% data variables.product.prodname_mobile %} +## Installing {% data variables.product.prodname_mobile %} -Para instalar o {% data variables.product.prodname_mobile %} para Android ou iOS, confira [{% data variables.product.prodname_mobile %}](https://github.com/mobile). +To install {% data variables.product.prodname_mobile %} for Android or iOS, see [{% data variables.product.prodname_mobile %}](https://github.com/mobile). -## Gerenciamento de contas +## Managing accounts -Você pode estar conectado simultaneamente em um celular com uma conta pessoal no {% data variables.product.prodname_dotcom_the_website %} e com uma conta pessoal no {% data variables.product.prodname_ghe_server %}. Para obter mais informações sobre nossos diferentes produtos, confira "[Produtos do {% data variables.product.company_short %}](/get-started/learning-about-github/githubs-products)". +You can be simultaneously signed into mobile with one personal account on {% data variables.product.prodname_dotcom_the_website %} and one personal account on {% data variables.product.prodname_ghe_server %}. For more information about our different products, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)." {% data reusables.mobile.push-notifications-on-ghes %} -{% data variables.product.prodname_mobile %} pode não funcionar com a sua empresa se for necessário acessar sua empresa através da VPN. +{% data variables.product.prodname_mobile %} may not work with your enterprise if you're required to access your enterprise over VPN. -### Pré-requisitos +### Prerequisites -Você precisa instalar {% data variables.product.prodname_mobile %} 1.4 ou superior no seu dispositivo para usar {% data variables.product.prodname_mobile %} com {% data variables.product.prodname_ghe_server %}. +You must install {% data variables.product.prodname_mobile %} 1.4 or later on your device to use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}. -Para usar {% data variables.product.prodname_mobile %} com {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} deve ser a versão 3.0 ou superior, e o proprietário da empresa deverá habilitar o suporte móvel para a sua empresa. Para obter mais informações, confira {% ifversion ghes %}"[Notas sobre a versão](/enterprise-server/admin/release-notes)" e {% endif %}"[Como gerenciar o {% data variables.product.prodname_mobile %} para sua empresa]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}" na documentação do {% data variables.product.prodname_ghe_server %}.{% else %}".{% endif %} +To use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, {% data variables.location.product_location %} must be version 3.0 or greater, and your enterprise owner must enable mobile support for your enterprise. For more information, see {% ifversion ghes %}"[Release notes](/enterprise-server/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %} -Durante o beta do {% data variables.product.prodname_mobile %} com o {% data variables.product.prodname_ghe_server %}, você deve estar conectado com uma conta pessoal no {% data variables.product.prodname_dotcom_the_website %}. +During the beta for {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, you must be signed in with a personal account on {% data variables.product.prodname_dotcom_the_website %}. -### Adicionar, alternar ou encerrar a sessão das contas +### Adding, switching, or signing out of accounts -Você pode se conectar no dispositivo móvel com uma conta pessoal no {% data variables.product.prodname_ghe_server %}. Na parte inferior do aplicativo, mantenha pressionado {% octicon "person" aria-label="The person icon" %} **Perfil** e toque em {% octicon "plus" aria-label="The plus icon" %} **Adicionar Conta Corporativa**. Siga as instruções para efetuar o login. +You can sign into mobile with a personal account on {% data variables.product.prodname_ghe_server %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account**. Follow the prompts to sign in. -Depois de efetuar o logon no dispositivo móvel com uma conta pessoal no {% data variables.product.prodname_ghe_server %}, você poderá alternar entre a conta e a sua conta no {% data variables.product.prodname_dotcom_the_website %}. Na parte inferior do aplicativo, mantenha pressionado {% octicon "person" aria-label="The person icon" %} **Perfil** e toque na conta para a qual deseja mudar. +After you sign into mobile with a personal account on {% data variables.product.prodname_ghe_server %}, you can switch between the account and your account on {% data variables.product.prodname_dotcom_the_website %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap the account you want to switch to. -Caso não precise mais acessar os dados da sua conta pessoal do {% data variables.product.prodname_ghe_server %} no {% data variables.product.prodname_mobile %}, saia da conta. Na parte inferior do aplicativo, mantenha pressionado {% octicon "person" aria-label="The person icon" %} **Perfil**, deslize o dedo para a esquerda na conta para sair e toque em **Sair**. +If you no longer need to access data for your personal account on {% data variables.product.prodname_ghe_server %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**. -## Idiomas compatíveis com {% data variables.product.prodname_mobile %} +## Supported languages for {% data variables.product.prodname_mobile %} -{% data variables.product.prodname_mobile %} está disponível nos seguintes idiomas. +{% data variables.product.prodname_mobile %} is available in the following languages. -- Inglês -- Japonês -- Português (Brasil) -- Chinês simplificado -- Espanhol +- English +- Japanese +- Brazilian Portuguese +- Simplified Chinese +- Spanish -Se você configurar o idioma do seu dispositivo para um idioma compatível, {% data variables.product.prodname_mobile %} será o idioma-padrão. Altere o idioma do {% data variables.product.prodname_mobile %} no menu **Configurações** do {% data variables.product.prodname_mobile %}. +If you configure the language on your device to a supported language, {% data variables.product.prodname_mobile %} will default to the language. You can change the language for {% data variables.product.prodname_mobile %} in {% data variables.product.prodname_mobile %}'s **Settings** menu. -## Gerenciando links universais para {% data variables.product.prodname_mobile %} no iOS +## Managing Universal Links for {% data variables.product.prodname_mobile %} on iOS -{% data variables.product.prodname_mobile %} ativa automaticamente o Universal Links para iOS. Quando você clica em qualquer link {% data variables.product.product_name %}, a URL de destino vai abrir em {% data variables.product.prodname_mobile %} em vez do Safari. Para obter mais informações, confira [Links Universais](https://developer.apple.com/ios/universal-links/) no site do Desenvolvedor da Apple. +{% data variables.product.prodname_mobile %} automatically enables Universal Links for iOS. When you tap any {% data variables.product.product_name %} link, the destination URL will open in {% data variables.product.prodname_mobile %} instead of Safari. For more information, see [Universal Links](https://developer.apple.com/ios/universal-links/) on the Apple Developer site. -Para desabilitar os Links Universais, mantenha pressionado qualquer link do {% data variables.product.product_name %} e toque em **Abrir**. Toda vez que você tocar em um link do {% data variables.product.product_name %} no futuro, a URL de destino será aberta no Safari em vez de no {% data variables.product.prodname_mobile %}. +To disable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open**. Every time you tap a {% data variables.product.product_name %} link in the future, the destination URL will open in Safari instead of {% data variables.product.prodname_mobile %}. -Para habilitar novamente os Links Universais, mantenha pressionado qualquer link do {% data variables.product.product_name %} e toque em **Abrir no {% data variables.product.prodname_dotcom %}** . +To re-enable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open in {% data variables.product.prodname_dotcom %}**. -## Compartilhando feedback +## Sharing feedback -Você pode enviar solicitações de recursos ou outros comentários para{% data variables.product.prodname_mobile %} em [{% data variables.product.prodname_github_community %}](https://github.com/orgs/community/discussions/categories/mobile). +You can submit feature requests or other feedback for {% data variables.product.prodname_mobile %} on [{% data variables.product.prodname_github_community %}](https://github.com/orgs/community/discussions/categories/mobile). -## Desativando versões beta para iOS +## Opting out of beta releases for iOS -Se você estiver testando uma versão beta do {% data variables.product.prodname_mobile %} para iOS usando TestFlight, você pode deixar a versão beta a qualquer momento. +If you're testing a beta release of {% data variables.product.prodname_mobile %} for iOS using TestFlight, you can leave the beta at any time. -1. Em seu dispositivo iOS, abra o app TestFlight. -2. Em "Aplicativos", toque em **{% data variables.product.prodname_dotcom %}** . -3. Na parte inferior da página, toque em **Parar Teste**. +1. On your iOS device, open the TestFlight app. +2. Under "Apps", tap **{% data variables.product.prodname_dotcom %}**. +3. At the bottom of the page, tap **Stop Testing**. diff --git a/translations/pt-BR/content/github-cli/github-cli/quickstart.md b/translations/pt-BR/content/github-cli/github-cli/quickstart.md index 1b4b3bbb2e..4b77a522cb 100644 --- a/translations/pt-BR/content/github-cli/github-cli/quickstart.md +++ b/translations/pt-BR/content/github-cli/github-cli/quickstart.md @@ -1,6 +1,6 @@ --- -title: Início rápido da CLI do GitHub -intro: 'Comece a usar {% data variables.product.prodname_cli %} para trabalhar com {% data variables.product.company_short %} na linha de comando.' +title: GitHub CLI quickstart +intro: 'Start using {% data variables.product.prodname_cli %} to work with {% data variables.product.company_short %} in the command line.' versions: fpt: '*' ghes: '*' @@ -11,41 +11,37 @@ topics: type: overview allowTitleToDifferFromFilename: true shortTitle: Quickstart -ms.openlocfilehash: 004f848e973aa66d19b9de6b922d65dba76f1aea -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145065531' --- -## Sobre a {% data variables.product.prodname_cli %} + +## About {% data variables.product.prodname_cli %} {% data reusables.cli.about-cli %} -## Introdução +## Getting started -1. [Instale](https://github.com/cli/cli#installation) a {% data variables.product.prodname_cli %} no macOS, no Windows ou no Linux. -1. Na linha de comando, efetue a aitenticação em {% data variables.product.company_short %}. +1. [Install](https://github.com/cli/cli#installation) {% data variables.product.prodname_cli %} on macOS, Windows, or Linux. +1. In the command line, authenticate to {% data variables.product.company_short %}. ```shell gh auth login ``` - {% ifversion not fpt or ghec %} Para se autenticar no {% data variables.product.product_location %}, use o sinalizador `--hostname`. + {% ifversion not fpt or ghec %} + To authenticate to {% data variables.location.product_location %}, use the `--hostname` flag. ```shell - gh auth login --hostname hostname + gh auth login --hostname HOSTNAME ``` {% endif %} -1. Comece a trabalhar com {% data variables.product.company_short %} na linha de comando. Por exemplo, encontre um problema para trabalhar com `gh issue status` ou `gh issue list --assignee @me`. Crie uma solicitação de pull com `gh pr create`. Revise uma solicitação de pull com `gh pr checkout`, `gh pr diff` e `gh pr review`. +1. Start working with {% data variables.product.company_short %} in the command line. For example, find an issue to work on with `gh issue status` or `gh issue list --assignee @me`. Create a pull request with `gh pr create`. Review a pull request with `gh pr checkout`, `gh pr diff` and `gh pr review`. -## Próximas etapas +## Next steps -- Diga a {% data variables.product.prodname_cli %} qual editor de texto usar para comandos que abram um editor de texto. Por exemplo, insira `gh config set editor "code -w"` para definir seu editor de texto preferido como o {% data variables.product.prodname_vscode %}. Para obter mais informações, confira [`gh config set`](https://cli.github.com/manual/gh_config_set). +- Tell {% data variables.product.prodname_cli %} which text editor to use for commands that open a text editor. For example, enter `gh config set editor "code -w"` to set your preferred text editor to {% data variables.product.prodname_vscode %}. For more information, see [`gh config set`](https://cli.github.com/manual/gh_config_set). -- Defina aliases para comandos que você executa com frequência. Por exemplo, se você executar `gh alias set prd "pr create --draft"`, poderá executar `gh prd` para abrir rapidamente uma solicitação de pull de rascunho. Para obter mais informações, confira [`gh alias`](https://cli.github.com/manual/gh_alias). +- Define aliases for commands that you commonly run. For example, if you run `gh alias set prd "pr create --draft"`, you will then be able to run `gh prd` to quickly open a draft pull request. For more information, see [`gh alias`](https://cli.github.com/manual/gh_alias). -- Crie ou adicione comandos personalizados com extensões de {% data variables.product.prodname_cli %}. Para obter mais informações, confira "[Como usar extensões da {% data variables.product.prodname_cli %}](/github-cli/github-cli/using-github-cli-extensions) e "[Como criar extensões da {% data variables.product.prodname_cli %}](/github-cli/github-cli/creating-github-cli-extensions)". +- Create or add custom commands with {% data variables.product.prodname_cli %} extensions. For more information, see "[Using {% data variables.product.prodname_cli %} extensions](/github-cli/github-cli/using-github-cli-extensions)" and "[Creating {% data variables.product.prodname_cli %} extensions](/github-cli/github-cli/creating-github-cli-extensions)." -- Para obter mais informações sobre todos os comandos que você pode executar com a {% data variables.product.prodname_cli %}, confira "[Referência da {% data variables.product.prodname_cli %}](/github-cli/github-cli/github-cli-reference)". +- For more information about all of the commands that you can run with {% data variables.product.prodname_cli %}, see "[{% data variables.product.prodname_cli %} reference](/github-cli/github-cli/github-cli-reference)." diff --git a/translations/pt-BR/content/graphql/guides/forming-calls-with-graphql.md b/translations/pt-BR/content/graphql/guides/forming-calls-with-graphql.md index 35d83a943e..51259302ab 100644 --- a/translations/pt-BR/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/pt-BR/content/graphql/guides/forming-calls-with-graphql.md @@ -1,6 +1,6 @@ --- -title: Realizar chamadas com o GraphQL -intro: 'Aprenda a efetuar a autenticação da a API do GraphQL e, em seguida, aprenda a criar e executar consultas e mutações.' +title: Forming calls with GraphQL +intro: 'Learn how to authenticate to the GraphQL API, then learn how to create and run queries and mutations.' redirect_from: - /v4/guides/forming-calls - /graphql/guides/forming-calls @@ -12,26 +12,23 @@ versions: topics: - API shortTitle: Form calls with GraphQL -ms.openlocfilehash: b3778872cad120f64f2fdbc238f2319bdd758513 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147527891' --- -## Autenticar com o GraphQL -Para comunicar-se com o servidor GraphQL, você precisará de um token do OAuth com os escopos corretos. +## Authenticating with GraphQL -Siga as etapas descritas em "[Como criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)" para criar um token. Os escopos de que você precisa dependem do tipo de dados que você está tentando solicitar. Por exemplo, selecione os escopos do **Usuário** para solicitar dados do usuário. Caso precise ter acesso às informações do repositório, selecione os escopos do **Repositório** apropriados. +{% data reusables.user-settings.graphql-classic-pat-only %} + +To communicate with the GraphQL server, you'll need a {% data variables.product.pat_generic %} with the right scopes. + +Follow the steps in "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)" to create a token. The scopes you require depends on the type of data you're trying to request. For example, select the **User** scopes to request user data. If you need access to repository information, select the appropriate **Repository** scopes. {% ifversion fpt or ghec %} -Para fazer a correspondência do comportamento do [GraphQL Explorer](/graphql/guides/using-the-explorer), solicite os seguintes escopos: +To match the behavior of the [GraphQL Explorer](/graphql/guides/using-the-explorer), request the following scopes: {% else %} -Recomendam-se os escopos a seguir: +The following scopes are recommended: {% endif %} @@ -48,26 +45,26 @@ read:enterprise read:gpg_key ``` -A API envia uma notificação se um recurso precisar de um escopo específico. +The API notifies you if a resource requires a specific scope. -## O ponto final do GraphQL +## The GraphQL endpoint -A API REST tem inúmeros pontos finais; a API do GraphQL tem um único ponto final: +The REST API has numerous endpoints; the GraphQL API has a single endpoint:
{% data variables.product.graphql_url_pre %}
-O ponto de final permanece constante, independentemente da operação que você realizar. +The endpoint remains constant no matter what operation you perform. -## Comunicação com o GraphQL +## Communicating with GraphQL -Como as operações do GraphQL consistem em várias linhas de JSON, o GitHub recomenda o uso do [Explorer](/graphql/guides/using-the-explorer) para fazer chamadas ao GraphQL. Você também pode usar a cURL ou qualquer outra biblioteca com linguagem HTTP. +Because GraphQL operations consist of multiline JSON, GitHub recommends using the [Explorer](/graphql/guides/using-the-explorer) to make GraphQL calls. You can also use cURL or any other HTTP-speaking library. -Na REST, os [verbos HTTP](/rest#http-verbs) determinam a operação executada. No GraphQL, você fornecerá um texto codificado por JSON se estiver realizando uma consulta ou uma mutação. Portanto, o verbo HTTP é `POST`. A exceção a isso é uma [consulta de introspecção](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api), que é um `GET` simples para o ponto de extremidade. Para obter mais informações sobre uma comparação entre o GraphQL e a REST, confira "[Migração da REST para o GraphQL](/graphql/guides/migrating-from-rest-to-graphql)". +In REST, [HTTP verbs](/rest#http-verbs) determine the operation performed. In GraphQL, you'll provide a JSON-encoded body whether you're performing a query or a mutation, so the HTTP verb is `POST`. The exception is an [introspection query](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api), which is a simple `GET` to the endpoint. For more information on GraphQL versus REST, see "[Migrating from REST to GraphQL](/graphql/guides/migrating-from-rest-to-graphql)." -Para consultar o GraphQL usando o cURL, faça uma solicitação `POST` com um conteúdo JSON. O conteúdo precisa conter uma cadeia de caracteres chamada `query`: +To query GraphQL using cURL, make a `POST` request with a JSON payload. The payload must contain a string called `query`: ```shell -curl -H "Authorization: bearer token" -X POST -d " \ +curl -H "Authorization: bearer TOKEN" -X POST -d " \ { \ \"query\": \"query { viewer { login }}\" \ } \ @@ -76,63 +73,63 @@ curl -H "Authorization: bearer token" -X POST -d " \ {% tip %} -**Observação**: o valor da cadeia de caracteres `"query"` precisa fazer o escape de caracteres de nova linha ou o esquema não o analisará corretamente. Para o corpo de `POST`, use aspas duplas externas e aspas duplas internas com escape. +**Note**: The string value of `"query"` must escape newline characters or the schema will not parse it correctly. For the `POST` body, use outer double quotes and escaped inner double quotes. {% endtip %} -### Sobre consultas e operações de mutação +### About query and mutation operations -Os dois tipos de operações permitidas na API do GraphQL do GitHub são _consultas_ e _mutações_. Comparando o GraphQL com a REST, as consultas operam como solicitações `GET`, enquanto as mutações operam como `POST`/`PATCH`/`DELETE`. O [nome da mutação](/graphql/reference/mutations) determina a modificação que é executada. +The two types of allowed operations in GitHub's GraphQL API are _queries_ and _mutations_. Comparing GraphQL to REST, queries operate like `GET` requests, while mutations operate like `POST`/`PATCH`/`DELETE`. The [mutation name](/graphql/reference/mutations) determines which modification is executed. -Para obter informações sobre a limitação de taxa, confira "[Limitações de recursos do GraphQL](/graphql/overview/resource-limitations)". +For information about rate limiting, see "[GraphQL resource limitations](/graphql/overview/resource-limitations)." -As consultas e mutações compartilham formas semelhantes, com algumas diferenças importantes. +Queries and mutations share similar forms, with some important differences. -### Sobre consultas +### About queries -As consultas do GraphQL retornam apenas os dados especificados. Para formar uma consulta, você precisa especificar [campos dentro de campos](/graphql/guides/introduction-to-graphql#field) (também conhecido como _subcampos aninhados_) até retornar apenas [escalares](/graphql/reference/scalars). +GraphQL queries return only the data you specify. To form a query, you must specify [fields within fields](/graphql/guides/introduction-to-graphql#field) (also known as _nested subfields_) until you return only [scalars](/graphql/reference/scalars). -As consultas são estruturadas da seguinte forma: +Queries are structured like this:
query {
-  JSON objects to return
+  JSON-OBJECT-TO-RETURN
 }
-Para ver um exemplo do mundo real, confira "[Exemplo de consulta](#example-query)". +For a real-world example, see "[Example query](#example-query)." -### Sobre as mutações +### About mutations -Para formar uma mutação, você deve especificar três coisas: +To form a mutation, you must specify three things: -1. _Nome da mutação_. O tipo de modificação que você deseja realizar. -2. _Objeto de entrada_. Os dados que você deseja enviar para o servidor, compostos de _campos de entrada_. Passe-o como um argumento para o nome de mutação. -3. _Objeto de conteúdo_. Os dados que você deseja retornar do servidor, compostos de _campos de retorno_. Passe-o como o texto do nome da mutação. +1. _Mutation name_. The type of modification you want to perform. +2. _Input object_. The data you want to send to the server, composed of _input fields_. Pass it as an argument to the mutation name. +3. _Payload object_. The data you want to return from the server, composed of _return fields_. Pass it as the body of the mutation name. -As mutações são estruturadas da seguinte forma: +Mutations are structured like this:
mutation {
-  mutationName(input: {MutationNameInput!}) {
-    MutationNamePayload
+  MUTATION-NAME(input: {MUTATION-NAME-INPUT!}) {
+    MUTATION-NAME-PAYLOAD
   }
 }
-O objeto de entrada deste exemplo é `MutationNameInput`, e o objeto de conteúdo é `MutationNamePayload`. +The input object in this example is `MutationNameInput`, and the payload object is `MutationNamePayload`. -Na referência de [mutações](/graphql/reference/mutations), os _campos de entrada_ listados são o que você transmite como o objeto de entrada. Os _campos de retorno_ listados são o que você transmite como o objeto de conteúdo. +In the [mutations](/graphql/reference/mutations) reference, the listed _input fields_ are what you pass as the input object. The listed _return fields_ are what you pass as the payload object. -Para ver um exemplo do mundo real, confira "[Exemplo de mutação](#example-mutation)". +For a real-world example, see "[Example mutation](#example-mutation)." -## Trabalhar com variáveis +## Working with variables -As [variáveis](https://graphql.github.io/learn/queries/#variables) podem tornar as consultas mais dinâmicas e eficientes, além de reduzir a complexidade ao transmitir objetos de entrada de mutação. +[Variables](https://graphql.github.io/learn/queries/#variables) can make queries more dynamic and powerful, and they can reduce complexity when passing mutation input objects. {% note %} -**Observação**: se você estiver usando o Explorer, insira variáveis no [painel Variáveis de Consulta](/graphql/guides/using-the-explorer#using-the-variable-pane) separadas e não inclua a palavra `variables` antes do objeto JSON. +**Note**: If you're using the Explorer, make sure to enter variables in the separate [Query Variables pane](/graphql/guides/using-the-explorer#using-the-variable-pane), and do not include the word `variables` before the JSON object. {% endnote %} -Aqui está um exemplo de consulta com uma única variável: +Here's an example query with a single variable: ```graphql query($number_of_repos:Int!) { @@ -150,9 +147,9 @@ variables { } ``` -Existem três etapas para usar variáveis: +There are three steps to using variables: -1. Defina a variável fora da operação em um objeto `variables`: +1. Define the variable outside the operation in a `variables` object: ```graphql variables { @@ -160,33 +157,33 @@ Existem três etapas para usar variáveis: } ``` - O objeto deve ser um JSON válido. Esse exemplo mostra um tipo de variável `Int` simples, mas é possível definir tipos de variáveis mais complexos, como objetos de entrada. Você também pode definir diversas variáveis aqui. + The object must be valid JSON. This example shows a simple `Int` variable type, but it's possible to define more complex variable types, such as input objects. You can also define multiple variables here. -2. Passe a variável para a operação como argumento: +2. Pass the variable to the operation as an argument: ```graphql query($number_of_repos:Int!){ ``` - O argumento é um par chave-valor, em que a chave é o _nome_ que começa com `$` (por exemplo, `$number_of_repos`), e o valor é o _tipo_ (por exemplo, `Int`). Adicione um `!` para indicar se o tipo é obrigatório. Se você definiu diversas variáveis, inclua-as aqui como múltiplos argumentos. + The argument is a key-value pair, where the key is the _name_ starting with `$` (e.g., `$number_of_repos`), and the value is the _type_ (e.g., `Int`). Add a `!` to indicate whether the type is required. If you've defined multiple variables, include them here as multiple arguments. -3. Use a variável dentro da operação: +3. Use the variable within the operation: ```graphql repositories(last: $number_of_repos) { ``` - Neste exemplo, substituímos a variável pelo número de repositórios a ser recuperados. Especificamos um tipo na etapa 2, porque o GraphQL impõe uma digitação forte. + In this example, we substitute the variable for the number of repositories to retrieve. We specify a type in step 2 because GraphQL enforces strong typing. -Este processo torna o argumento da consulta dinâmico. Agora, podemos simplesmente alterar o valor no objeto `variables` e manter o restante da consulta inalterado. +This process makes the query argument dynamic. We can now simply change the value in the `variables` object and keep the rest of the query the same. -O uso de variáveis como argumentos permite que você atualize os valores dinamicamente no objeto `variables` sem alterar a consulta. +Using variables as arguments lets you dynamically update values in the `variables` object without changing the query. -## Consulta de exemplo +## Example query -Vamos analisar uma questão mais complexa e colocar essas informações no contexto. +Let's walk through a more complex query and put this information in context. -A seguinte consulta faz uma pesquisa no repositório `octocat/Hello-World`, encontra os 20 problemas fechados mais recentes e retorna o título, a URL e os cinco primeiros rótulos de cada problema: +The following query looks up the `octocat/Hello-World` repository, finds the 20 most recent closed issues, and returns each issue's title, URL, and first 5 labels: ```graphql query { @@ -210,35 +207,35 @@ query { } ``` -Observando a composição linha por linha: +Looking at the composition line by line: * `query {` - Como queremos ler os dados do servidor e não modificá-los, `query` é a operação raiz. (Se você não especificar uma operação, `query` também será o padrão). + Because we want to read data from the server, not modify it, `query` is the root operation. (If you don't specify an operation, `query` is also the default.) * `repository(owner:"octocat", name:"Hello-World") {` - Para iniciar a consulta, queremos encontrar um objeto [`repository`](/graphql/reference/objects#repository). A validação de esquema indica que esse objeto exige um `owner` e um argumento `name`. + To begin the query, we want to find a [`repository`](/graphql/reference/objects#repository) object. The schema validation indicates this object requires an `owner` and a `name` argument. * `issues(last:20, states:CLOSED) {` - Para responder por todos os problemas no repositório, chamamos o objeto `issues`. (_Podemos_ consultar um só `issue` em um `repository`, mas, para isso, precisaremos saber o número do problema que queremos retornar e fornecê-lo como um argumento). + To account for all issues in the repository, we call the `issues` object. (We _could_ query a single `issue` on a `repository`, but that would require us to know the number of the issue we want to return and provide it as an argument.) - Alguns detalhes sobre o objeto `issues`: + Some details about the `issues` object: - - A [documentação](/graphql/reference/objects#repository) nos informa que esse objeto tem o tipo `IssueConnection`. - - A validação de esquema indica que esse objeto exige um número de resultados `last` ou `first` como argumento, ou seja, fornecemos `20`. - - A [documentação](/graphql/reference/objects#repository) também nos informa que esse objeto aceita um argumento `states`, que é uma enumeração [`IssueState`](/graphql/reference/enums#issuestate) que aceita valores `OPEN` ou `CLOSED`. Para localizar apenas os problemas fechados, damos à chave `states` um valor igual a `CLOSED`. + - The [docs](/graphql/reference/objects#repository) tell us this object has the type `IssueConnection`. + - Schema validation indicates this object requires a `last` or `first` number of results as an argument, so we provide `20`. + - The [docs](/graphql/reference/objects#repository) also tell us this object accepts a `states` argument, which is an [`IssueState`](/graphql/reference/enums#issuestate) enum that accepts `OPEN` or `CLOSED` values. To find only closed issues, we give the `states` key a value of `CLOSED`. * `edges {` - Sabemos que `issues` é uma conexão porque ela tem o tipo `IssueConnection`. Para recuperar dados sobre problemas individuais, precisamos acessar o nó por meio de `edges`. + We know `issues` is a connection because it has the `IssueConnection` type. To retrieve data about individual issues, we have to access the node via `edges`. * `node {` - Aqui, recuperamos o nó no fim da borda. A [documentação de `IssueConnection`](/graphql/reference/objects#issueconnection) indica que o nó no final do tipo `IssueConnection` é um objeto `Issue`. + Here we retrieve the node at the end of the edge. The [`IssueConnection` docs](/graphql/reference/objects#issueconnection) indicate the node at the end of the `IssueConnection` type is an `Issue` object. -* Agora que sabemos que estamos recuperando um objeto `Issue`, podemos dar uma olhada na [documentação](/graphql/reference/objects#issue) e especificar os campos que queremos retornar: +* Now that we know we're retrieving an `Issue` object, we can look at the [docs](/graphql/reference/objects#issue) and specify the fields we want to return: ```graphql title @@ -252,18 +249,18 @@ Observando a composição linha por linha: } ``` - Aqui, especificamos os campos `title`, `url` e `labels` do objeto `Issue`. + Here we specify the `title`, `url`, and `labels` fields of the `Issue` object. - O campo `labels` tem o tipo [`LabelConnection`](/graphql/reference/objects#labelconnection). Assim como acontece com o objeto `issues`, como `labels` é uma conexão, precisamos percorrer as bordas até um nó conectado: o objeto `label`. No nó, podemos especificar os campos de objeto `label` que queremos retornar, nesse caso, `name`. + The `labels` field has the type [`LabelConnection`](/graphql/reference/objects#labelconnection). As with the `issues` object, because `labels` is a connection, we must travel its edges to a connected node: the `label` object. At the node, we can specify the `label` object fields we want to return, in this case, `name`. -Observe que a execução dessa consulta no repositório {% ifversion not ghae %}público{% endif %} `Hello-World` do Octocat não retornará muitos rótulos. Tente executá-la em um dos seus próprios repositórios que usam etiquetas, e provavelmente você verá uma diferença. +You may notice that running this query on the Octocat's {% ifversion not ghae %}public{% endif %} `Hello-World` repository won't return many labels. Try running it on one of your own repositories that does use labels, and you'll likely see a difference. -## Exemplo de mutação +## Example mutation -De modo geral, as mutações exigem informações que você só pode encontrar ao realizar primeiro uma consulta. Este exemplo mostra duas operações: +Mutations often require information that you can only find out by performing a query first. This example shows two operations: -1. Uma consulta para obter um ID do problema. -2. Uma mutação para adicionar uma reação de emojis ao problema. +1. A query to get an issue ID. +2. A mutation to add an emoji reaction to the issue. ```graphql query FindIssueID { @@ -288,81 +285,81 @@ mutation AddReactionToIssue { {% tip %} -Embora você possa incluir uma consulta e uma mutação na mesma janela do Explorer, se você der nomes a elas (`FindIssueID` e `AddReactionToIssue`, neste exemplo), as operações serão executadas como chamadas separadas para o ponto de extremidade do GraphQL. Não é possível realizar uma consulta junto com uma mutação ou vice-versa. +Although you can include a query and a mutation in the same Explorer window if you give them names (`FindIssueID` and `AddReactionToIssue` in this example), the operations will be executed as separate calls to the GraphQL endpoint. It's not possible to perform a query at the same time as a mutation, or vice versa. {% endtip %} -Vamos analisar o exemplo. A tarefa parece simples: adicione uma reação emoji a um problema. +Let's walk through the example. The task sounds simple: add an emoji reaction to an issue. -Então, como é que sabemos começar com uma consulta? Ainda não sabemos. +So how do we know to begin with a query? We don't, yet. -Uma vez que desejamos modificar os dados no servidor (anexar um emoji a um problema), começamos procurando uma mutação útil no esquema. A documentação de referência mostra a mutação [`addReaction`](/graphql/reference/mutations#addreaction), com esta descrição: `Adds a reaction to a subject.` Perfeito! +Because we want to modify data on the server (attach an emoji to an issue), we begin by searching the schema for a helpful mutation. The reference docs show the [`addReaction`](/graphql/reference/mutations#addreaction) mutation, with this description: `Adds a reaction to a subject.` Perfect! -A documentação para a lista de mutação lista três campos de entrada: +The docs for the mutation list three input fields: * `clientMutationId` (`String`) * `subjectId` (`ID!`) * `content` (`ReactionContent!`) -Os `!`s indicam que `subjectId` e `content` são campos obrigatórios. Um `content` obrigatório faz sentido: desejamos adicionar uma reação e, portanto, precisamos especificar o emoji que deve ser usado. +The `!`s indicate that `subjectId` and `content` are required fields. A required `content` makes sense: we want to add a reaction, so we'll need to specify which emoji to use. -Mas por que `subjectId` é obrigatório? Isso ocorre porque a `subjectId` é a única maneira de identificar a _qual_ problema de _qual_ repositório é preciso reagir. +But why is `subjectId` required? It's because the `subjectId` is the only way to identify _which_ issue in _which_ repository to react to. -É por isso que começamos este exemplo com uma consulta: para obter a `ID`. +This is why we start this example with a query: to get the `ID`. -Vamos examinar a consulta linha por linha: +Let's examine the query line by line: * `query FindIssueID {` - Aqui, estamos executando uma consulta e a nomeamos `FindIssueID`. Observe que nomear uma consulta é opcional; nós damos um nome aqui para que possamos incluí-la na mesma janela do explorador que a mutação. + Here we're performing a query, and we name it `FindIssueID`. Note that naming a query is optional; we give it a name here so that we can include it in same Explorer window as the mutation. * `repository(owner:"octocat", name:"Hello-World") {` - Especificamos o repositório consultando o objeto `repository` e transmitindo os argumentos `owner` e `name`. + We specify the repository by querying the `repository` object and passing `owner` and `name` arguments. * `issue(number:349) {` - Especificamos o problema ao qual é preciso reagir consultando o objeto `issue` e transmitindo um argumento `number`. + We specify the issue to react to by querying the `issue` object and passing a `number` argument. * `id` - É nesse ponto que recuperamos a `id` de `https://github.com/octocat/Hello-World/issues/349` para transmiti-la como a `subjectId`. + This is where we retrieve the `id` of `https://github.com/octocat/Hello-World/issues/349` to pass as the `subjectId`. -Quando executamos a consulta, obtemos a `id`: `MDU6SXNzdWUyMzEzOTE1NTE=` +When we run the query, we get the `id`: `MDU6SXNzdWUyMzEzOTE1NTE=` {% tip %} -**Observação**: a `id` retornada na consulta é o valor que transmitiremos como a `subjectID` na mutação. Nem a documentação nem a introspecção do esquema indicará essa relação; você precisará entender os conceitos por trás dos nomes para descobrir isso. +**Note**: The `id` returned in the query is the value we'll pass as the `subjectID` in the mutation. Neither the docs nor schema introspection will indicate this relationship; you'll need to understand the concepts behind the names to figure this out. {% endtip %} -Com a identificação conhecida, podemos prosseguir com a mutação: +With the ID known, we can proceed with the mutation: * `mutation AddReactionToIssue {` - Aqui, estamos executando uma mutação e a nomeamos `AddReactionToIssue`. Tal como nas consultas, nomear uma mutação é opcional; aqui, damos um nome para que possamos incluí-la na mesma janela do explorador que a consulta. + Here we're performing a mutation, and we name it `AddReactionToIssue`. As with queries, naming a mutation is optional; we give it a name here so we can include it in the same Explorer window as the query. * `addReaction(input:{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}) {` - Vamos examinar essa linha: + Let's examine this line: - - `addReaction` é o nome da mutação. - - `input` é a chave de argumento obrigatória. Isso sempre será `input` para uma mutação. - - `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}` é o valor de argumento obrigatório. Isso sempre será um [objeto de entrada](/graphql/reference/input-objects) (daí as chaves) composto por campos de entrada (`subjectId` e `content`, neste caso) para uma mutação. + - `addReaction` is the name of the mutation. + - `input` is the required argument key. This will always be `input` for a mutation. + - `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}` is the required argument value. This will always be an [input object](/graphql/reference/input-objects) (hence the curly braces) composed of input fields (`subjectId` and `content` in this case) for a mutation. - Como sabemos qual o valor usar para o conteúdo? A [documentação de `addReaction`](/graphql/reference/mutations#addreaction) nos informa que o campo `content` tem o tipo [`ReactionContent`](/graphql/reference/enums#reactioncontent), que é uma [enumeração](/graphql/reference/enums), porque só há suporte para algumas reações com emojis nos problemas do GitHub. Estes são os valores permitidos para reações (observe que alguns valores diferem de seus nomes de emojis correspondentes): + How do we know which value to use for the content? The [`addReaction` docs](/graphql/reference/mutations#addreaction) tell us the `content` field has the type [`ReactionContent`](/graphql/reference/enums#reactioncontent), which is an [enum](/graphql/reference/enums) because only certain emoji reactions are supported on GitHub issues. These are the allowed values for reactions (note some values differ from their corresponding emoji names): {% data reusables.repositories.reaction_list %} -* O resto da chamada é composto pelo objeto da carga. Aqui é onde especificamos os dados que desejamos que o servidor retorne depois de termos efetuado a mutação. Essas linhas são provenientes da [documentação de `addReaction`](/graphql/reference/mutations#addreaction), que são três campos de retorno possíveis: +* The rest of the call is composed of the payload object. This is where we specify the data we want the server to return after we've performed the mutation. These lines come from the [`addReaction` docs](/graphql/reference/mutations#addreaction), which three possible return fields: - `clientMutationId` (`String`) - `reaction` (`Reaction!`) - `subject` (`Reactable!`) - Neste exemplo, retornamos os dois campos obrigatórios (`reaction` e `subject`), ambos com subcampos obrigatórios (`content` e `id`, respectivamente). + In this example, we return the two required fields (`reaction` and `subject`), both of which have required subfields (respectively, `content` and `id`). -Ao executarmos a mutação, esta é a resposta: +When we run the mutation, this is the response: ```json { @@ -379,9 +376,9 @@ Ao executarmos a mutação, esta é a resposta: } ``` -É isso! Confira sua [reação ao problema](https://github.com/octocat/Hello-World/issues/349) posicionando o cursor sobre o :tada: para encontrar seu nome de usuário. +That's it! Check out your [reaction to the issue](https://github.com/octocat/Hello-World/issues/349) by hovering over the :tada: to find your username. -Observação final: quando você passa vários campos em um objeto de entrada, a sintaxe pode ficar pesada. Pode ser útil mover os campos para uma [variável](#working-with-variables). Veja como você poderia reescrever a mutação original usando uma variável: +One final note: when you pass multiple fields in an input object, the syntax can get unwieldy. Moving the fields into a [variable](#working-with-variables) can help. Here's how you could rewrite the original mutation using a variable: ```graphql mutation($myVar:AddReactionInput!) { @@ -404,19 +401,19 @@ variables { {% note %} -Você poderá observar que o valor do campo `content` no exemplo anterior (em que ele é usado diretamente na mutação) não tem aspas em torno de `HOORAY`, mas tem aspas quando usado na variável. Há um motivo para isso: -* Quando você usa `content` diretamente na mutação, o esquema espera que o valor seja do tipo [`ReactionContent`](/graphql/reference/enums#reactioncontent), que é uma _enumeração_, não uma cadeia de caracteres. A validação de esquema causará um erro se você adicionar aspas no valor do enum, já que as aspas são reservadas para strings. -* Ao usar `content` em uma variável, a seção de variáveis precisa ser um JSON válido. Portanto, as aspas são obrigatórias. A validação de esquema interpreta corretamente o tipo `ReactionContent` quando a variável é transmitida para a mutação durante a execução. +You may notice that the `content` field value in the earlier example (where it's used directly in the mutation) does not have quotes around `HOORAY`, but it does have quotes when used in the variable. There's a reason for this: +* When you use `content` directly in the mutation, the schema expects the value to be of type [`ReactionContent`](/graphql/reference/enums#reactioncontent), which is an _enum_, not a string. Schema validation will throw an error if you add quotes around the enum value, as quotes are reserved for strings. +* When you use `content` in a variable, the variables section must be valid JSON, so the quotes are required. Schema validation correctly interprets the `ReactionContent` type when the variable is passed into the mutation during execution. -Para obter mais informações sobre a diferença entre enumerações e cadeias de caracteres, confira a [especificação oficial do GraphQL](https://graphql.github.io/graphql-spec/June2018/#sec-Enums). +For more information on the difference between enums and strings, see the [official GraphQL spec](https://graphql.github.io/graphql-spec/June2018/#sec-Enums). {% endnote %} -## Leitura adicional +## Further reading -Há _muito_ mais que você pode fazer ao formar chamadas do GraphQL. Aqui estão alguns lugares para procurar a seguir: +There is a _lot_ more you can do when forming GraphQL calls. Here are some places to look next: -* [Paginação](https://graphql.org/learn/pagination/) -* [Fragmentos](https://graphql.org/learn/queries/#fragments) -* [Fragmentos embutidos](https://graphql.org/learn/queries/#inline-fragments) -* [Diretivas](https://graphql.org/learn/queries/#directives) +* [Pagination](https://graphql.org/learn/pagination/) +* [Fragments](https://graphql.org/learn/queries/#fragments) +* [Inline fragments](https://graphql.org/learn/queries/#inline-fragments) +* [Directives](https://graphql.org/learn/queries/#directives) diff --git a/translations/pt-BR/content/graphql/guides/introduction-to-graphql.md b/translations/pt-BR/content/graphql/guides/introduction-to-graphql.md index 60f21df1ae..8459cf109f 100644 --- a/translations/pt-BR/content/graphql/guides/introduction-to-graphql.md +++ b/translations/pt-BR/content/graphql/guides/introduction-to-graphql.md @@ -1,6 +1,6 @@ --- -title: Introdução ao GraphQL -intro: Aprenda terminologia e conceitos úteis para usar a API do GraphQL do GitHub. +title: Introduction to GraphQL +intro: Learn useful terminology and concepts for using the GitHub GraphQL API. redirect_from: - /v4/guides/intro-to-graphql - /graphql/guides/intro-to-graphql @@ -11,40 +11,36 @@ versions: ghae: '*' topics: - API -ms.openlocfilehash: abc74dfd4aa65035405fd956c6438a487381284b -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145065509' --- -## Terminologia do GraphQL -A API do GraphQL do GitHub representa uma mudança estrutural e conceitual API REST do GitHub. Provavelmente, você encontrará uma nova terminologia na [documentação de referência](/graphql) da API do GraphQL. +## GraphQL terminology -## Esquema +The GitHub GraphQL API represents an architectural and conceptual shift from the GitHub REST API. You will likely encounter some new terminology in the GraphQL API [reference docs](/graphql). -Um esquema define um sistema de tipos da API do GraphQL. Ele descreve o conjunto completo de dados possíveis (objetos, campos, relações, tudo) que um cliente pode acessar. As chamadas do cliente são [validadas](https://graphql.github.io/learn/validation/) e [executadas](https://graphql.github.io/learn/execution/) no esquema. Um cliente pode encontrar informações sobre o esquema por meio da [introspecção](#discovering-the-graphql-api). Um esquema reside no servidor da API do GraphQL. Para obter mais informações, confira "[Como descobrir a API do GraphQL](#discovering-the-graphql-api)". +## Schema -## Campo +A schema defines a GraphQL API's type system. It describes the complete set of possible data (objects, fields, relationships, everything) that a client can access. Calls from the client are [validated](https://graphql.github.io/learn/validation/) and [executed](https://graphql.github.io/learn/execution/) against the schema. A client can find information about the schema via [introspection](#discovering-the-graphql-api). A schema resides on the GraphQL API server. For more information, see "[Discovering the GraphQL API](#discovering-the-graphql-api)." -Um campo é uma unidade de dados que você pode recuperar de um objeto. Como indica a [documentação oficial do GraphQL](https://graphql.github.io/learn/schema/): "A linguagem de consulta GraphQL trata basicamente da seleção de campos em objetos". +## Field -A [especificação oficial](https://graphql.github.io/graphql-spec/June2018/#sec-Language.Fields) também traz informações sobre os campos: +A field is a unit of data you can retrieve from an object. As the [official GraphQL docs](https://graphql.github.io/learn/schema/) say: +"The GraphQL query language is basically about selecting fields on objects." -> Todas as operações do GraphQL devem especificar suas seleções para os campos que retornam valores escalares a fim de garantir uma resposta de forma não ambígua. +The [official spec](https://graphql.github.io/graphql-spec/June2018/#sec-Language.Fields) also says about fields: -Isso significa que se você tentar retornar um campo que não é escalar, a validação do esquema causará um erro. Você deve adicionar subcampos aninhados até que todos os campos retornam escalares. +> All GraphQL operations must specify their selections down to fields which return scalar values to ensure an unambiguously shaped response. -## Argumento +This means that if you try to return a field that is not a scalar, schema validation will throw an error. You must add nested subfields until all fields return scalars. -Um argumento é um conjunto de pares de chave-valor anexados a um campo específico. Alguns campos exigem um argumento. As [mutações](/graphql/guides/forming-calls-with-graphql#about-mutations) exigem um objeto de entrada como argumento. +## Argument -## Implementação +An argument is a set of key-value pairs attached to a specific field. Some fields require an argument. [Mutations](/graphql/guides/forming-calls-with-graphql#about-mutations) require an input object as an argument. -Um esquema do GraphQL pode usar o termo _implementos_ para definir como um objeto herda de uma [interface](/graphql/reference/interfaces). +## Implementation -Veja um exemplo inventado de um esquema que define a interface `X` e o objeto `Y`: +A GraphQL schema may use the term _implements_ to define how an object inherits from an [interface](/graphql/reference/interfaces). + +Here's a contrived example of a schema that defines interface `X` and object `Y`: ``` interface X { @@ -59,33 +55,33 @@ type Y implements X { } ``` -Isso significa que o objeto `Y` exige os mesmos campos/argumentos/tipos de retorno da interface `X`, adicionando novos campos específicos ao objeto `Y`. (O `!` significa que o campo é obrigatório). +This means object `Y` requires the same fields/arguments/return types that interface `X` does, while adding new fields specific to object `Y`. (The `!` means the field is required.) -Na documentação de referência, você descobrirá que: +In the reference docs, you'll find that: -* Cada [objeto](/graphql/reference/objects) lista as interfaces _das quais ela herda_ em **Implementos**. +* Each [object](/graphql/reference/objects) lists the interface(s) _from which it inherits_ under **Implements**. -* Cada [interface](/graphql/reference/interfaces) lista os objetos _que herdam dele_ em **Implementações**. +* Each [interface](/graphql/reference/interfaces) lists the objects _that inherit from it_ under **Implementations**. -## Conexão +## Connection -As conexões permitem que você consulte objetos relacionados às consultas como parte da mesma chamada. Com as conexões, você pode usar uma única chamada do GraphQL quando você teria que usar várias chamadas para uma API REST. Para obter mais informações, confira "[Como migrar da REST para o GraphQL](/graphql/guides/migrating-from-rest-to-graphql)". +Connections let you query related objects as part of the same call. With connections, you can use a single GraphQL call where you would have to use multiple calls to a REST API. For more information, see "[Migrating from REST to GraphQL](/graphql/guides/migrating-from-rest-to-graphql)." -É útil imaginar um gráfico: pontos conectados por linhas. Os pontos são nós e as linhas são bordas. Uma conexão define uma relação entre os nós. +It's helpful to picture a graph: dots connected by lines. The dots are nodes, the lines are edges. A connection defines a relationship between nodes. -## Microsoft Edge +## Edge -As bordas representam conexões entre os nós. Quando você consulta uma conexão, você atravessa suas bordas para chegar a seus nós. Cada campo `edges` tem um campo `node` e um campo `cursor`. Os cursores são usados para [paginação](https://graphql.github.io/learn/pagination/). +Edges represent connections between nodes. When you query a connection, you traverse its edges to get to its nodes. Every `edges` field has a `node` field and a `cursor` field. Cursors are used for [pagination](https://graphql.github.io/learn/pagination/). -## Nó +## Node -_Nó_ é um termo genérico para um objeto. Você pode procurar um nó diretamente pode acessar nós relacionados através de uma conexão. Se você especificar um `node` que não retorna um [escalar](/graphql/reference/scalars), precisará incluir subcampos até que todos os campos retornem escalares. Para obter informações sobre como acessar IDs de nó por meio da API REST e usá-las em consultas GraphQL, confira "[Como usar IDs de nó global](/graphql/guides/using-global-node-ids)". +_Node_ is a generic term for an object. You can look up a node directly, or you can access related nodes via a connection. If you specify a `node` that does not return a [scalar](/graphql/reference/scalars), you must include subfields until all fields return scalars. For information on accessing node IDs via the REST API and using them in GraphQL queries, see "[Using Global Node IDs](/graphql/guides/using-global-node-ids)." -## Descobrindo a API do GraphQL +## Discovering the GraphQL API -O GraphQL é [introspectivo](https://graphql.github.io/learn/introspection/). Isso significa que você pode consultar um esquema do GraphQL para obter informações sobre ele. +GraphQL is [introspective](https://graphql.github.io/learn/introspection/). This means you can query a GraphQL schema for details about itself. -* Consulte `__schema` para listar todos os tipos definidos no esquema e obter detalhes sobre cada um: +* Query `__schema` to list all types defined in the schema and get details about each: ```graphql query { @@ -102,7 +98,7 @@ O GraphQL é [introspectivo](https://graphql.github.io/learn/introspection/). Is } ``` -* Consulte `__type` para obter detalhes sobre qualquer tipo: +* Query `__type` to get details about any type: ```graphql query { @@ -117,31 +113,31 @@ O GraphQL é [introspectivo](https://graphql.github.io/learn/introspection/). Is } ``` -* Você também pode executar uma _consulta de introspecção_ do esquema por meio de uma solicitação `GET`: +* You can also run an _introspection query_ of the schema via a `GET` request: ```shell - $ curl -H "Authorization: bearer token" {% data variables.product.graphql_url_pre %} + $ curl -H "Authorization: bearer TOKEN" {% data variables.product.graphql_url_pre %} ``` {% note %} - **Observação**: se você receber a resposta `"message": "Bad credentials"` ou `401 Unauthorized`, verifique se está usando um token válido. Para obter mais informações, confira "[Como criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)". + **Note**: If you get the response `"message": "Bad credentials"` or `401 Unauthorized`, check that you are using a valid token. The GraphQL API only supports authentication using a {% data variables.product.pat_v1 %}. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." {% endnote %} - Os resultados estão no JSON,. Portanto, recomendamos que sejam impressos para facilitar a leitura e pesquisa. Use uma ferramenta de linha de comando como o [jq](https://stedolan.github.io/jq/) ou encaminhe os resultados a `python -m json.tool` para essa finalidade. + The results are in JSON, so we recommend pretty-printing them for easier reading and searching. You can use a command-line tool like [jq](https://stedolan.github.io/jq/) or pipe the results into `python -m json.tool` for this purpose. - Como alternativa, você pode transmitir o tipo de mídia `idl` para retornar os resultados no formato IDL, que é uma versão condensada do esquema: + Alternatively, you can pass the `idl` media type to return the results in IDL format, which is a condensed version of the schema: ```shell - $ curl -H "Authorization: bearer token" -H "Accept: application/vnd.github.v4.idl" \ + $ curl -H "Authorization: bearer TOKEN" -H "Accept: application/vnd.github.v4.idl" \ {% data variables.product.graphql_url_pre %} ``` {% note %} - **Observação**: a consulta de introspecção é provavelmente a única solicitação `GET` que você executará no GraphQL. Se você estiver transmitindo um corpo, o método de solicitação do GraphQL será `POST`, seja uma consulta ou uma mutação. + **Note**: The introspection query is probably the only `GET` request you'll run in GraphQL. If you're passing a body, the GraphQL request method is `POST`, whether it's a query or a mutation. {% endnote %} - Para obter mais informações sobre como executar consultas, confira "[Como formar chamadas com o GraphQL](/graphql/guides/forming-calls-with-graphql)". + For more information about performing queries, see "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." diff --git a/translations/pt-BR/content/graphql/guides/managing-enterprise-accounts.md b/translations/pt-BR/content/graphql/guides/managing-enterprise-accounts.md index 14642c4a4b..6c5a8fa020 100644 --- a/translations/pt-BR/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/pt-BR/content/graphql/guides/managing-enterprise-accounts.md @@ -1,6 +1,6 @@ --- -title: Gerenciar contas corporativas -intro: Você pode gerenciar sua conta corporativa e as organizações detêm com a API do GraphQL. +title: Managing enterprise accounts +intro: You can manage your enterprise account and the organizations it owns with the GraphQL API. redirect_from: - /v4/guides/managing-enterprise-accounts versions: @@ -10,99 +10,96 @@ versions: topics: - API shortTitle: Manage enterprise accounts -ms.openlocfilehash: bdfcca52766b85406df12b597822d5a5a596f26b -ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/12/2022 -ms.locfileid: '145065507' --- -## Sobre o gerenciamento de contas corporativas com o GraphQL -Para ajudá-lo a monitorar e fazer alterações nas suas organizações e manter a conformidade, você pode usar a API de Contas corporativas e a API de log de auditoria, que estão disponíveis apenas como APIs do GraphQL. +## About managing enterprise accounts with GraphQL -Os pontos finais da conta corporativa funcionam tanto para o GitHub Enterprise Cloud quanto para o GitHub Enterprise Server. +To help you monitor and make changes in your organizations and maintain compliance, you can use the Enterprise Accounts API and the Audit Log API, which are only available as GraphQL APIs. -O GraphQL permite que você solicite e retorne apenas os dados especificados. Por exemplo, você pode criar uma consulta GraphQL ou solicitar informações para ver todos os novos membros da organização adicionados à sua organização. Ou você pode fazer uma mutação ou alteração para convidar um administrador para sua conta corporativa. +The enterprise account endpoints work for both GitHub Enterprise Cloud and for GitHub Enterprise Server. -Com a API do Log de Auditoria, você pode monitorar quando alguém: -- Acessa as configurações de sua organização ou repositório. -- Altera as permissões. -- Adiciona ou remove usuários em uma organização, repositório ou equipe. -- Promove os usuários a administrador. -- Altera as permissões de um aplicativo GitHub. +GraphQL allows you to request and return just the data you specify. For example, you can create a GraphQL query, or request for information, to see all the new organization members added to your organization. Or you can make a mutation, or change, to invite an administrator to your enterprise account. -A API do Log de Auditoria permite que você mantenha cópias dos dados do log de auditoria. Para consultas feitas com a API do Log de Auditoria, a resposta do GraphQL pode incluir dados de 90 a 120 dias. Para ver uma lista dos campos disponíveis na API de Log de Auditoria, confira a "[interface do AuditEntry](/graphql/reference/interfaces#auditentry/)". +With the Audit Log API, you can monitor when someone: +- Accesses your organization or repository settings. +- Changes permissions. +- Adds or removes users in an organization, repository, or team. +- Promotes users to admin. +- Changes permissions of a GitHub App. -Com a API de Contas corporativas, você pode: -- Listar e revisar todas as organizações e repositórios que pertencem à conta corporativa. -- Alterar configurações da conta empresarial. -- Configurar políticas para configurações na conta corporativa e em suas organizações. -- Convidar os administradores para a sua conta corporativa. -- Criar novas organizações na sua conta corporativa. +The Audit Log API enables you to keep copies of your audit log data. For queries made with the Audit Log API, the GraphQL response can include data for up to 90 to 120 days. For a list of the fields available with the Audit Log API, see the "[AuditEntry interface](/graphql/reference/interfaces#auditentry/)." -Para ver uma lista dos campos disponíveis na API de Contas Enterprise, confira "[Campos e tipos do GraphQL para a API de Contas Enterprise](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)". +With the Enterprise Accounts API, you can: +- List and review all of the organizations and repositories that belong to your enterprise account. +- Change Enterprise account settings. +- Configure policies for settings on your enterprise account and its organizations. +- Invite administrators to your enterprise account. +- Create new organizations in your enterprise account. -## Primeiros passos usando o GraphQL para contas corporativas +For a list of the fields available with the Enterprise Accounts API, see "[GraphQL fields and types for the Enterprise account API](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)." -Siga estes passos para começar a usar o GraphQL para gerenciar as suas contas corporativas: - - Efetuando a autenticação com um token de acesso pessoal - - Escolher um cliente do GraphQL ou usar o Explorador do GraphQL - - Configurar a o Insomnia para usar a API do GraphQL +## Getting started using GraphQL for enterprise accounts -Para ver alguns exemplos de consultas, confira "[Um exemplo de consulta que usa a API de Contas Enterprise](#an-example-query-using-the-enterprise-accounts-api)". +Follow these steps to get started using GraphQL to manage your enterprise accounts: + - Authenticating with a {% data variables.product.pat_generic %} + - Choosing a GraphQL client or using the GraphQL Explorer + - Setting up Insomnia to use the GraphQL API -### 1. Autenticar-se com seu token de acesso pessoal +For some example queries, see "[An example query using the Enterprise Accounts API](#an-example-query-using-the-enterprise-accounts-api)." -1. Para efetuar a autenticação com o GraphQL, você precisa gerar um token de acesso pessoal (PAT) a partir das configurações do desenvolvedor. Para obter mais informações, confira "[Como criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)". +### 1. Authenticate with your {% data variables.product.pat_generic %} -2. Conceda permissões de administrador e controle total ao seu token de acesso pessoal para as áreas do GHES que você gostaria de acessar. Para obter a permissão total para repositórios privados, organizações, equipes, dados de usuário e acesso aos dados de cobrança da empresa e de perfil, recomendamos que você selecione estes escopos para o seu token de acesso pessoal: +{% data reusables.user-settings.graphql-classic-pat-only %} + +1. To authenticate with GraphQL, you need to generate a {% data variables.product.pat_generic %} from developer settings. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." + +2. Grant admin and full control permissions to your {% data variables.product.pat_generic %} for areas of GHES you'd like to access. For full permission to private repositories, organizations, teams, user data, and access to enterprise billing and profile data, we recommend you select these scopes for your {% data variables.product.pat_generic %}: - `repo` - `admin:org` - `user` - `admin:enterprise` - Os escopos específicos da conta corporativa são: - - `admin:enterprise`: fornece controle total das empresas (inclui {% ifversion ghes > 3.2 or ghae or ghec %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` e `read:enterprise`) - - `manage_billing:enterprise`: lê e grava dados de cobrança da empresa.{% ifversion ghes > 3.2 or ghae %} - - `manage_runners:enterprise`: acesso para gerenciar executores da empresa e grupos de executores do GitHub Actions.{% endif %} - - `read:enterprise`: lê os dados de perfil da empresa. + The enterprise account specific scopes are: + - `admin:enterprise`: Gives full control of enterprises (includes {% ifversion ghes > 3.2 or ghae or ghec %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` and `read:enterprise`) + - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes > 3.2 or ghae %} + - `manage_runners:enterprise`: Access to manage GitHub Actions enterprise runners and runner-groups.{% endif %} + - `read:enterprise`: Read enterprise profile data. -3. Copie seu token de acesso pessoal e guarde-o em um lugar seguro até adicioná-lo ao seu cliente do GraphQL. +3. Copy your {% data variables.product.pat_generic %} and keep it in a secure place until you add it to your GraphQL client. -### 2. Escolher um cliente do GraphQL +### 2. Choose a GraphQL client -Recomendamos que você use o GraphiQL ou outro cliente autônomo do GraphQL que permite configurar a URL de base. +We recommend you use GraphiQL or another standalone GraphQL client that lets you configure the base URL. -Você também pode considerar o uso destes clientes do GraphQL: +You may also consider using these GraphQL clients: - [Insomnia](https://support.insomnia.rest/article/176-graphql-queries) - [GraphiQL](https://www.gatsbyjs.org/docs/running-queries-with-graphiql/) - [Postman](https://learning.getpostman.com/docs/postman/sending_api_requests/graphql/) -As próximas etapas usarão o Insomnia. +The next steps will use Insomnia. -### 3. Como configurar o Insomnia para usar a API do GraphQL no GitHub com as contas corporativas +### 3. Setting up Insomnia to use the GitHub GraphQL API with enterprise accounts -1. Adicione a URL base e `POST` o método ao cliente do GraphQL. Ao usar o GraphQL para solicitar informações (consultas), alterar informações (mutações) ou transferir dados usando a API do GitHub, o método HTTP padrão é `POST` e a URL base segue esta sintaxe: - - Para sua instância corporativa: `https:///api/graphql` - - Para o GitHub Enterprise Cloud: `https://api.github.com/graphql` +1. Add the base url and `POST` method to your GraphQL client. When using GraphQL to request information (queries), change information (mutations), or transfer data using the GitHub API, the default HTTP method is `POST` and the base url follows this syntax: + - For your enterprise instance: `https:///api/graphql` + - For GitHub Enterprise Cloud: `https://api.github.com/graphql` -2. Para se autenticar, abra o menu de opções de autenticação e selecione **Token de portador**. Em seguida, adicione seu token de acesso pessoal que você copiou anteriormente. +2. To authenticate, open the authentication options menu and select **Bearer token**. Next, add your {% data variables.product.pat_generic %} that you copied earlier. - ![Opções de permissão para o token de acesso pessoal](/assets/images/developer/graphql/insomnia-base-url-and-pat.png) + ![Permissions options for {% data variables.product.pat_generic %}](/assets/images/developer/graphql/insomnia-base-url-and-pat.png) - ![Opções de permissão para o token de acesso pessoal](/assets/images/developer/graphql/insomnia-bearer-token-option.png) + ![Permissions options for {% data variables.product.pat_generic %}](/assets/images/developer/graphql/insomnia-bearer-token-option.png) -3. Incluir informações do header. - - Adicione `Content-Type` como o cabeçalho e `application/json` como o valor. - ![Cabeçalho padrão](/assets/images/developer/graphql/json-content-type-header.png) - ![Cabeçalho com valor de visualização para a API de Log de Auditoria](/assets/images/developer/graphql/preview-header-for-2.18.png) +3. Include header information. + - Add `Content-Type` as the header and `application/json` as the value. + ![Standard header](/assets/images/developer/graphql/json-content-type-header.png) + ![Header with preview value for the Audit Log API](/assets/images/developer/graphql/preview-header-for-2.18.png) -Agora você está pronto para começar a fazer consultas. +Now you are ready to start making queries. -## Um exemplo e consulta usando a API de Contas corporativas +## An example query using the Enterprise Accounts API -Esta consulta do GraphQL solicita o número total de repositórios {% ifversion not ghae %}`public`{% else %}`private`{% endif %} em cada uma das organizações do seu dispositivo usando a API de Contas Enterprise. Para personalizar essa consulta, substitua `` pelo identificador da sua conta corporativa. Por exemplo, se a sua conta corporativa estiver localizada em `https://github.com/enterprises/octo-enterprise`, substitua `` por `octo-enterprise`. +This GraphQL query requests the total number of {% ifversion not ghae %}`public`{% else %}`private`{% endif %} repositories in each of your appliance's organizations using the Enterprise Accounts API. To customize this query, replace `` with the handle for your enterprise account. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `` with `octo-enterprise`. {% ifversion not ghae %} @@ -169,7 +166,7 @@ variables { ``` {% endif %} -O próximo exemplo de consulta GraphQL mostra como é complexo recuperar o número de repositórios {% ifversion not ghae %}`public`{% else %}`private`{% endif %} em cada organização sem usar a API de Contas Enterprise. Observe que a API de Contas corporativas do GraphQL simplificou esta tarefa para empresas, pois você só precisa personalizar uma única variável. Para personalizar essa consulta, substitua `` e `` etc. pelos nomes da organização na sua instância. +The next GraphQL query example shows how challenging it is to retrieve the number of {% ifversion not ghae %}`public`{% else %}`private`{% endif %} repositories in each organization without using the Enterprise Account API. Notice that the GraphQL Enterprise Accounts API has made this task simpler for enterprises since you only need to customize a single variable. To customize this query, replace `` and ``, etc. with the organization names on your instance. {% ifversion not ghae %} ```graphql @@ -217,7 +214,7 @@ fragment repositories on Organization { ``` {% endif %} -## Consulte cada organização separadamente +## Query each organization separately {% ifversion not ghae %} @@ -265,7 +262,7 @@ fragment repositories on Organization { {% endif %} -Esta consulta do GraphQL solicita as últimas 5 entradas de registro para uma organização corporativa. Para personalizar essa consulta, substitua `` e ``. +This GraphQL query requests the last 5 log entries for an enterprise organization. To customize this query, replace `` and ``. ```graphql { @@ -291,13 +288,13 @@ Esta consulta do GraphQL solicita as últimas 5 entradas de registro para uma or } ``` -Para obter mais informações sobre como começar a usar o GraphQL, confira "[Introdução ao GraphQL](/graphql/guides/introduction-to-graphql)" e "[Como formar chamadas com o GraphQL](/graphql/guides/forming-calls-with-graphql)". +For more information about getting started with GraphQL, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)" and "[Forming Calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." -## Campos e tipos do GraphQL para a API de Contas corporativas +## GraphQL fields and types for the Enterprise Accounts API -Aqui está uma visão geral das novas consultas, mutações e tipos definidos por esquema disponíveis para uso com a API de Contas corporativas. +Here's an overview of the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API. -Para obter mais detalhes sobre as novas consultas, as mutações e os tipos definidos por esquema disponíveis para uso na API de Contas Enterprise, confira a barra lateral com definições detalhadas do GraphQL de qualquer [página de referência do GraphQL](/graphql). +For more details about the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API, see the sidebar with detailed GraphQL definitions from any [GraphQL reference page](/graphql). -Você pode acessar a documentação de referência de no explorador do GraphQL no GitHub. Para obter mais informações, confira "[Como usar o Explorer](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)". -Para obter outras informações, como detalhes de autenticação e limite de taxa, confira os [guias](/graphql/guides). +You can access the reference docs from within the GraphQL explorer on GitHub. For more information, see "[Using the explorer](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)." +For other information, such as authentication and rate limit details, check out the [guides](/graphql/guides). diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md index a6456930a1..aa83f058df 100644 --- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md +++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md @@ -1,79 +1,74 @@ --- -title: 'Sobre {% data variables.product.prodname_projects_v1 %}' -intro: 'Os {% data variables.product.prodname_projects_v1_caps %} no {% data variables.product.product_name %} ajudam você a organizar e priorizar seu trabalho. É possível criar {% data variables.projects.projects_v1_boards %} para trabalho de recurso específico, roteiros abrangentes ou, até mesmo, listas de verificação de versão. Com os {% data variables.product.prodname_projects_v1 %}, você tem a flexibilidade de criar fluxos de trabalho personalizados que atendam às suas necessidades.' +title: About {% data variables.product.prodname_projects_v1 %} +intro: '{% data variables.product.prodname_projects_v1_caps %} on {% data variables.product.product_name %} help you organize and prioritize your work. You can create {% data variables.projects.projects_v1_boards %} for specific feature work, comprehensive roadmaps, or even release checklists. With {% data variables.product.prodname_projects_v1 %}, you have the flexibility to create customized workflows that suit your needs.' redirect_from: - /github/managing-your-work-on-github/managing-project-boards/about-project-boards - /articles/about-projects - /articles/about-project-boards - /github/managing-your-work-on-github/about-project-boards versions: - feature: projects-v1 + feature: "projects-v1" topics: - Pull requests allowTitleToDifferFromFilename: true -ms.openlocfilehash: 5ec81cf456ddca503e58ca6703ae3372875bd62c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147614236' --- + {% data reusables.projects.project_boards_old %} -Os {% data variables.projects.projects_v1_boards_caps %} são compostos por problemas, solicitações de pull e observações que são categorizados como cartões nas colunas de sua escolha. É possível arrastar e soltar ou usar atalhos de teclado para reordenar cartões em uma coluna, mover cartões de coluna para coluna e alterar a ordem das colunas. +{% data variables.projects.projects_v1_boards_caps %} are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. You can drag and drop or use keyboard shortcuts to reorder cards within a column, move cards from column to column, and change the order of columns. -Os cartões de {% data variables.projects.projects_v1_board_caps %} contêm metadados relevantes para problemas e solicitações de pull, como etiquetas, destinatários, o status e quem os abriu. {% data reusables.project-management.edit-in-project %} +{% data variables.projects.projects_v1_board_caps %} cards contain relevant metadata for issues and pull requests, like labels, assignees, the status, and who opened it. {% data reusables.project-management.edit-in-project %} -Você pode criar anotações dentro de colunas para servirem de lembretes de tarefas, referências a problemas e solicitações de pull de qualquer repositório no {% data variables.product.product_location %} ou para adicionar informações relacionadas ao {% data variables.projects.projects_v1_board %}. É possível criar um cartão de referência para outro {% data variables.projects.projects_v1_board %} adicionando um link a uma observação. Se a observação não for suficiente para suas necessidades, você poderá convertê-la em um problema. Para obter mais informações sobre como converter observações em problemas, confira "[Adicionar observações a um {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)". +You can create notes within columns to serve as task reminders, references to issues and pull requests from any repository on {% data variables.location.product_location %}, or to add information related to the {% data variables.projects.projects_v1_board %}. You can create a reference card for another {% data variables.projects.projects_v1_board %} by adding a link to a note. If the note isn't sufficient for your needs, you can convert it to an issue. For more information on converting notes to issues, see "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)." -Tipos de quadros de projeto: +Types of project boards: -- Um **{% data variables.projects.projects_v1_board %} pertencente a usuário** pode conter problemas e solicitações de pull de qualquer repositório pessoal. -- Um **{% data variables.projects.projects_v1_board %} em toda a organização** pode conter problemas e solicitações de pull de qualquer repositório que pertença a uma organização. {% data reusables.project-management.link-repos-to-project-board %} Para obter mais informações, confira "[Vincular um repositório a um {% data variables.product.prodname_project_v1 %}](/articles/linking-a-repository-to-a-project-board)". -- Um **{% data variables.projects.projects_v1_board %} de repositório** tem como escopo problemas e solicitações de pull em um só repositório. Eles também podem incluir observações que fazem referência a problemas e pull requests em outros repositórios. +- **User-owned {% data variables.projects.projects_v1_board %}** can contain issues and pull requests from any personal repository. +- **Organization-wide {% data variables.projects.projects_v1_board %}** can contain issues and pull requests from any repository that belongs to an organization. {% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a {% data variables.product.prodname_project_v1 %}](/articles/linking-a-repository-to-a-project-board)." +- **Repository {% data variables.projects.projects_v1_board %}** are scoped to issues and pull requests within a single repository. They can also include notes that reference issues and pull requests in other repositories. -## Criar e exibir {% data variables.projects.projects_v1_boards %} +## Creating and viewing {% data variables.projects.projects_v1_boards %} -Para criar um {% data variables.projects.projects_v1_board %} para sua organização, você precisa ser um membro da organização. Proprietários de organizações e pessoas com permissões de administrador do {% data variables.projects.projects_v1_board %} podem personalizar o acesso ao {% data variables.projects.projects_v1_board %}. +To create a {% data variables.projects.projects_v1_board %} for your organization, you must be an organization member. Organization owners and people with {% data variables.projects.projects_v1_board %} admin permissions can customize access to the {% data variables.projects.projects_v1_board %}. {% ifversion classic-project-visibility-permissions %}{% data reusables.projects.owners-can-limit-visibility-permissions %}{% endif %} -Se um {% data variables.projects.projects_v1_board %} pertencente à organização incluir problemas ou solicitações de pull de um repositório que você não tem permissão para exibir, o cartão será redigido. Para obter mais informações, confira "[Permissões {% data variables.product.prodname_project_v1_caps %} para uma organização](/articles/project-board-permissions-for-an-organization)". +If an organization-owned {% data variables.projects.projects_v1_board %} includes issues or pull requests from a repository that you don't have permission to view, the card will be redacted. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." -A exibição da atividade mostra o histórico recente do {% data variables.projects.projects_v1_board %}, como cartões que alguém criou ou moveu entre colunas. Para acessar a exibição de atividade, clique em **Menu** e role a página para baixo. +The activity view shows the {% data variables.projects.projects_v1_board %}'s recent history, such as cards someone created or moved between columns. To access the activity view, click **Menu** and scroll down. -Para localizar cartões específicos em um {% data variables.projects.projects_v1_board %} ou exibir um subconjunto dos cartões, você pode filtrar cartões do {% data variables.projects.projects_v1_board %}. Para obter mais informações, confira "[Filtrar cartões em um {% data variables.product.prodname_project_v1 %}](/articles/filtering-cards-on-a-project-board)". +To find specific cards on a {% data variables.projects.projects_v1_board %} or view a subset of the cards, you can filter {% data variables.projects.projects_v1_board %} cards. For more information, see "[Filtering cards on a {% data variables.product.prodname_project_v1 %}](/articles/filtering-cards-on-a-project-board)." -Para simplificar o fluxo de trabalho e manter as tarefas concluídas fora do seu {% data variables.projects.projects_v1_board %}, você pode arquivar cartões. Para obter mais informações, confira "[Arquivar cartões em um {% data variables.product.prodname_project_v1 %}](/articles/archiving-cards-on-a-project-board)". +To simplify your workflow and keep completed tasks off your {% data variables.projects.projects_v1_board %}, you can archive cards. For more information, see "[Archiving cards on a {% data variables.product.prodname_project_v1 %}](/articles/archiving-cards-on-a-project-board)." -Se você tiver concluído todas as suas tarefas do {% data variables.projects.projects_v1_board %} ou não precisar mais usar o {% data variables.projects.projects_v1_board %}, será possível fechar o {% data variables.projects.projects_v1_board %}. Para obter mais informações, confira "[Fechar um {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)". +If you've completed all of your {% data variables.projects.projects_v1_board %} tasks or no longer need to use your {% data variables.projects.projects_v1_board %}, you can close the {% data variables.projects.projects_v1_board %}. For more information, see "[Closing a {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)." -Se preferir acompanhar seu trabalho de uma forma diferente, você também poderá [desabilitar os {% data variables.projects.projects_v1_boards %} em um repositório](/articles/disabling-project-boards-in-a-repository) ou [desabilitar os {% data variables.projects.projects_v1_boards %} em sua organização](/articles/disabling-project-boards-in-your-organization). +You can also [disable {% data variables.projects.projects_v1_boards %} in a repository](/articles/disabling-project-boards-in-a-repository) or [disable {% data variables.projects.projects_v1_boards %} in your organization](/articles/disabling-project-boards-in-your-organization), if you prefer to track your work in a different way. {% data reusables.project-management.project-board-import-with-api %} -## Modelos de {% data variables.projects.projects_v1_boards %} +## Templates for {% data variables.projects.projects_v1_boards %} -Você pode usar modelos para configurar rapidamente um novo {% data variables.projects.projects_v1_board %}. Quando você usa um modelo para criar um {% data variables.projects.projects_v1_board %}, seu novo quadro incluirá colunas, bem como cartões com dicas de uso dos {% data variables.product.prodname_projects_v1 %}. Você também pode escolher um modelo com automação já configurada. +You can use templates to quickly set up a new {% data variables.projects.projects_v1_board %}. When you use a template to create a {% data variables.projects.projects_v1_board %}, your new board will include columns as well as cards with tips for using {% data variables.product.prodname_projects_v1 %}. You can also choose a template with automation already configured. -| Modelo | Descrição | +| Template | Description | | --- | --- | -| Kanban básico | Rastreie tarefas com colunas To do (Pendentes), In progress (Em andamento) e Done (Concluídas) | -| Kanban automatizado | Cartões são movidos automaticamente entre as colunas To do (Pendentes), In progress (Em andamento) e Done (Concluídas) | -| Kanban automatizado com revisão | Cartões são movidos automaticamente entre as colunas To do (Pendentes), In progress (Em andamento) e Done (Concluídos), com gatilhos adicionais para status de revisão de pull request | -| Triagem de erros | Faça a triagem e priorize erros com as colunas To do (Pendentes), High priority (Prioridade alta), Low priority (Prioridade baixa) e Closed (Fechados) | +| Basic kanban | Track your tasks with To do, In progress, and Done columns | +| Automated kanban | Cards automatically move between To do, In progress, and Done columns | +| Automated kanban with review | Cards automatically move between To do, In progress, and Done columns, with additional triggers for pull request review status | +| Bug triage | Triage and prioritize bugs with To do, High priority, Low priority, and Closed columns | -Para obter mais informações sobre automação de {% data variables.product.prodname_projects_v1 %}, confira "[Sobre automação de {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)". +For more information on automation for {% data variables.product.prodname_projects_v1 %}, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)." -![{% data variables.product.prodname_project_v1 %} com modelo Kanban básico](/assets/images/help/projects/project-board-basic-kanban-template.png) +![{% data variables.product.prodname_project_v1 %} with basic kanban template](/assets/images/help/projects/project-board-basic-kanban-template.png) {% data reusables.project-management.copy-project-boards %} -## Leitura adicional +## Further reading -- "[Criar um {% data variables.product.prodname_project_v1 %}](/articles/creating-a-project-board)" -- "[Editar um {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)"{% ifversion fpt or ghec %} -- "[Copiar um {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board)"{% endif %} -- "[Adicionar problemas e solicitações de pull a um {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)" -- "[Permissões de {% data variables.product.prodname_project_v1_caps %} para uma organização](/articles/project-board-permissions-for-an-organization)" -- "[Atalhos de teclado](/articles/keyboard-shortcuts/#project-boards)" +- "[Creating a {% data variables.product.prodname_project_v1 %}](/articles/creating-a-project-board)" +- "[Editing a {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)"{% ifversion fpt or ghec %} +- "[Copying a {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board)"{% endif %} +- "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)" +- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)" +- "[Keyboard shortcuts](/articles/keyboard-shortcuts/#project-boards)" diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md index 146a26f9db..3b0e137b23 100644 --- a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md +++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md @@ -1,58 +1,54 @@ --- -title: 'Automatizar {% data variables.product.prodname_projects_v2 %} usando ações' -shortTitle: Automating with Actions -intro: 'Você pode usar o {% data variables.product.prodname_actions %} para automatizar projetos.' +title: 'Automating {% data variables.product.prodname_projects_v2 %} using Actions' +shortTitle: 'Automating with Actions' +intro: 'You can use {% data variables.product.prodname_actions %} to automate your projects.' miniTocMaxHeadingLevel: 3 versions: - feature: projects-v2 + feature: "projects-v2" redirect_from: - /issues/trying-out-the-new-projects-experience/automating-projects type: tutorial topics: - Projects allowTitleToDifferFromFilename: true -ms.openlocfilehash: 7c1d37f43653204eba7f3bf4c1b9b5ab6b01db51 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147423767' --- -## Fluxos de trabalho {% data variables.product.prodname_actions %} -Esta seção demonstra como usar a API do GraphQL e {% data variables.product.prodname_actions %} para adicionar um pull request a um projeto da organização. No exemplo de fluxos de trabalho, quando o pull request é marcado como "pronto para revisão", uma nova tarefa é adicionada ao projeto com um campo "Status" definido como "Todo", e a data atual é adicionada a um campo personalizado "Data de postagem". -Você pode copiar um dos fluxos de trabalho abaixo e modificá-lo conforme descrito na tabela abaixo para atender às suas necessidades. +## {% data variables.product.prodname_actions %} workflows -Um projeto pode incluir vários repositórios, mas um fluxo de trabalho é específico para um repositório. Adicione o fluxo de trabalho a cada repositório que deseja acompanhar no projeto. Para obter mais informações sobre como criar arquivos de fluxo de trabalho, confira "[Guia de início rápido do {% data variables.product.prodname_actions %}](/actions/quickstart)". +This section demonstrates how to use the GraphQL API and {% data variables.product.prodname_actions %} to add a pull request to an organization project. In the example workflows, when the pull request is marked as "ready for review", a new task is added to the project with a "Status" field set to "Todo", and the current date is added to a custom "Date posted" field. -Este artigo pressupõe que você tem um entendimento básico de {% data variables.product.prodname_actions %}. Para obter mais informações sobre o {% data variables.product.prodname_actions %}, confira "[{% data variables.product.prodname_actions %}](/actions)". +You can copy one of the workflows below and modify it as described in the table below to meet your needs. -Para obter mais informações sobre outras alterações que você pode fazer no seu projeto por meio da API, confira "[Como usar a API para gerenciar projetos](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)". +A project can span multiple repositories, but a workflow is specific to a repository. Add the workflow to each repository that you want your project to track. For more information about creating workflow files, see "[Quickstart for {% data variables.product.prodname_actions %}](/actions/quickstart)." -Você também pode querer usar o fluxo de trabalho de **ações/adicionar ao projeto**, que é mantido pelo {% data variables.product.company_short %} e adicionará o problema ou a solicitação de pull atual ao projeto especificado. Para obter mais informações, confira o repositório de [ações/adicionar ao projeto](https://github.com/actions/add-to-project) e o LEIAME. +This article assumes that you have a basic understanding of {% data variables.product.prodname_actions %}. For more information about {% data variables.product.prodname_actions %}, see "[{% data variables.product.prodname_actions %}](/actions)." + +For more information about other changes you can make to your project through the API, see "[Using the API to manage projects](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)." + +You may also want to use the **actions/add-to-project** workflow, which is maintained by {% data variables.product.company_short %} and will add the current issue or pull request to the project specified. For more information, see the [actions/add-to-project](https://github.com/actions/add-to-project) repository and README. {% note %} -**Observação:** o `GITHUB_TOKEN` tem escopo para o nível do repositório e não pode acessar {% data variables.projects.projects_v2 %}. Para acessar {% data variables.projects.projects_v2 %}, você pode criar um {% data variables.product.prodname_github_app %} (recomendado para projetos de organização) ou um token de acesso pessoal (recomendado para projetos de usuários). Exemplos de fluxo de trabalho para ambas as abordagens são mostrados abaixo. +**Note:** `GITHUB_TOKEN` is scoped to the repository level and cannot access {% data variables.projects.projects_v2 %}. To access {% data variables.projects.projects_v2 %} you can either create a {% data variables.product.prodname_github_app %} (recommended for organization projects) or a {% data variables.product.pat_generic %} (recommended for user projects). Workflow examples for both approaches are shown below. {% endnote %} -### Exemplo de fluxo de trabalho que efetua a autenticação com um {% data variables.product.prodname_github_app %} +### Example workflow authenticating with a {% data variables.product.prodname_github_app %} -1. Crie um {% data variables.product.prodname_github_app %} ou escolha um {% data variables.product.prodname_github_app %} existente pertencente à sua organização. Para obter mais informações, confira "[Como criar um {% data variables.product.prodname_github_app %}](/developers/apps/building-github-apps/creating-a-github-app)". -2. Dê as suas permissões de leitura e gravação de {% data variables.product.prodname_github_app %} para projetos de organização. Para obter mais informações, confira "[Como editar as permissões de um {% data variables.product.prodname_github_app %}](/developers/apps/managing-github-apps/editing-a-github-apps-permissions)". +1. Create a {% data variables.product.prodname_github_app %} or choose an existing {% data variables.product.prodname_github_app %} owned by your organization. For more information, see "[Creating a {% data variables.product.prodname_github_app %}](/developers/apps/building-github-apps/creating-a-github-app)." +2. Give your {% data variables.product.prodname_github_app %} read and write permissions to organization projects. For more information, see "[Editing a {% data variables.product.prodname_github_app %}'s permissions](/developers/apps/managing-github-apps/editing-a-github-apps-permissions)." {% note %} - **Observação:** você pode controlar a permissão do aplicativo em projetos da organização e do repositório. Você deve dar permissão de leitura e gravação de projetos de organização; a permissão de leitura e gravação para projetos de repositório não será suficiente. + **Note:** You can control your app's permission to organization projects and to repository projects. You must give permission to read and write organization projects; permission to read and write repository projects will not be sufficient. {% endnote %} -3. Instale o {% data variables.product.prodname_github_app %} na sua organização. Instale-o em todos os repositórios que o seu projeto precisa acessar. Para obter mais informações, confira "[Como instalar os {% data variables.product.prodname_github_apps %}](/developers/apps/managing-github-apps/installing-github-apps#installing-your-private-github-app-on-your-repository)". -4. Armazene o ID do seu {% data variables.product.prodname_github_app %} como um segredo no seu repositório ou organização. No fluxo de trabalho a seguir, substitua `APP_ID` pelo nome do segredo. Você pode encontrar o ID do seu aplicativo na página de configurações do seu aplicativo ou por meio da API do aplicativo. Para obter mais informações, confira "[Aplicativos](/rest/reference/apps#get-an-app)". -5. Gerar uma chave privada para o seu aplicativo. Armazene o conteúdo do arquivo resultante como um segredo no seu repositório ou organização. (Armazene todo o conteúdo do arquivo, incluindo `-----BEGIN RSA PRIVATE KEY-----` e `-----END RSA PRIVATE KEY-----`). No fluxo de trabalho a seguir, substitua `APP_PEM` pelo nome do segredo. Para obter mais informações, confira "[Autenticação com os {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#generating-a-private-key)". -6. No fluxo de trabalho a seguir, substitua `YOUR_ORGANIZATION` pelo nome da sua organização. Por exemplo, `octo-org`. Substitua `YOUR_PROJECT_NUMBER` pelo número do projeto. Para encontrar o número do projeto, consulte a URL do projeto. Por exemplo, `https://github.com/orgs/octo-org/projects/5` tem o número de projeto 5. +3. Install the {% data variables.product.prodname_github_app %} in your organization. Install it for all repositories that your project needs to access. For more information, see "[Installing {% data variables.product.prodname_github_apps %}](/developers/apps/managing-github-apps/installing-github-apps#installing-your-private-github-app-on-your-repository)." +4. Store your {% data variables.product.prodname_github_app %}'s ID as a secret in your repository or organization. In the following workflow, replace `APP_ID` with the name of the secret. You can find your app ID on the settings page for your app or through the App API. For more information, see "[Apps](/rest/reference/apps#get-an-app)." +5. Generate a private key for your app. Store the contents of the resulting file as a secret in your repository or organization. (Store the entire contents of the file, including `-----BEGIN RSA PRIVATE KEY-----` and `-----END RSA PRIVATE KEY-----`.) In the following workflow, replace `APP_PEM` with the name of the secret. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#generating-a-private-key)." +6. In the following workflow, replace `YOUR_ORGANIZATION` with the name of your organization. For example, `octo-org`. Replace `YOUR_PROJECT_NUMBER` with your project number. To find the project number, look at the project URL. For example, `https://github.com/orgs/octo-org/projects/5` has a project number of 5. ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -171,11 +167,11 @@ jobs: ``` -### Exemplo de fluxo de trabalho que efetua a autenticação com um token de acesso pessoal +### Example workflow authenticating with a {% data variables.product.pat_generic %} -1. Crie um token de acesso pessoal com os escopos `project` e `repo`. Para obter mais informações, confira "[Como criar um token de acesso pessoal](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)". -2. Salve o token de acesso pessoal como um segredo no seu repositório ou organização. -3. No fluxo de trabalho a seguir, substitua `YOUR_TOKEN` pelo nome do segredo. Substitua `YOUR_ORGANIZATION` pelo nome da sua organização. Por exemplo, `octo-org`. Substitua `YOUR_PROJECT_NUMBER` pelo número do projeto. Para encontrar o número do projeto, consulte a URL do projeto. Por exemplo, `https://github.com/orgs/octo-org/projects/5` tem o número de projeto 5. +1. Create a {% data variables.product.pat_v1 %} with the `project` and `repo` scopes. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." +2. Save the {% data variables.product.pat_generic %} as a secret in your repository or organization. +3. In the following workflow, replace `YOUR_TOKEN` with the name of the secret. Replace `YOUR_ORGANIZATION` with the name of your organization. For example, `octo-org`. Replace `YOUR_PROJECT_NUMBER` with your project number. To find the project number, look at the project URL. For example, `https://github.com/orgs/octo-org/projects/5` has a project number of 5. ```yaml{:copy} name: Add PR to project @@ -283,9 +279,9 @@ jobs: ``` -### Explicação do fluxo de trabalho +### Workflow explanation -A tabela a seguir explica as seções dos fluxos de trabalho de exemplo e mostra como adaptar os fluxos de trabalho para seu próprio uso. +The following table explains sections of the example workflows and shows you how to adapt the workflows for your own use. @@ -301,7 +297,7 @@ on: @@ -321,13 +317,13 @@ Este fluxo de trabalho é executado sempre que um pull request no repositório f @@ -343,7 +339,7 @@ env: PROJECT_NUMBER: YOUR_PROJECT_NUMBER ``` -Token de acesso de pessoal: +{% data variables.product.pat_generic_caps %}: ```yaml env: @@ -354,16 +350,16 @@ env: @@ -399,9 +395,9 @@ gh api graphql -f query=' @@ -417,12 +413,12 @@ echo 'TODO_OPTION_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select @@ -437,7 +433,7 @@ env: PR_ID: {% raw %}${{ github.event.pull_request.node_id }}{% endraw %} ``` -Token de acesso de pessoal: +{% data variables.product.pat_generic_caps %}: ```yaml env: @@ -447,7 +443,7 @@ env: @@ -468,7 +464,7 @@ item_id="$( gh api graphql -f query=' @@ -481,7 +477,7 @@ echo 'ITEM_ID='$item_id >> $GITHUB_ENV @@ -494,7 +490,7 @@ echo "DATE=$(date +"%Y-%m-%d")" >> $GITHUB_ENV @@ -508,7 +504,7 @@ env: GITHUB_TOKEN: {% raw %}${{ steps.generate_token.outputs.token }}{% endraw %} ``` -Token de acesso de pessoal: +{% data variables.product.pat_generic_caps %}: ```yaml env: @@ -517,7 +513,7 @@ env: @@ -564,7 +560,7 @@ gh api graphql -f query=' diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md index ffe33c1704..eefcafeb6d 100644 --- a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md +++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md @@ -11,6 +11,7 @@ children: - /using-the-built-in-automations - /using-the-api-to-manage-projects - /automating-projects-using-actions + - /archiving-items-automatically allowTitleToDifferFromFilename: true ms.openlocfilehash: 6c9777a65125f574e4a2cd05a7177448606f8348 ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md index 8c6927581a..afb973e02b 100644 --- a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md +++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md @@ -21,7 +21,7 @@ This article demonstrates how to use the GraphQL API to manage a project. For mo {% curl %} -In all of the following cURL examples, replace `TOKEN` with a token that has the `read:project` scope (for queries) or `project` scope (for queries and mutations). The token can be a personal access token for a user or an installation access token for a {% data variables.product.prodname_github_app %}. For more information about creating a personal access token, see "[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about creating an installation access token for a {% data variables.product.prodname_github_app %}, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-a-github-app)." +In all of the following cURL examples, replace `TOKEN` with a token that has the `read:project` scope (for queries) or `project` scope (for queries and mutations). The token can be a {% data variables.product.pat_v1 %} for a user or an installation access token for a {% data variables.product.prodname_github_app %}. For more information about creating a {% data variables.product.pat_generic %}, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about creating an installation access token for a {% data variables.product.prodname_github_app %}, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-a-github-app)." {% endcurl %} diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md index e8aa80a742..1929b511b2 100644 --- a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md +++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md @@ -1,118 +1,150 @@ --- -title: Personalizar uma exibição -intro: 'Exiba as informações de que você precisa no seu projeto com alterações de layout, agrupamento e classificação.' +title: 'Customizing a view' +intro: 'Display the information you need by changing the layout, grouping, sorting in your project.' miniTocMaxHeadingLevel: 3 versions: - feature: projects-v2 + feature: "projects-v2" redirect_from: - /issues/trying-out-the-new-projects-experience/customizing-your-project-views type: tutorial topics: - Projects -ms.openlocfilehash: 962a20daac125cdec5510daf3d792e0aaf6a194b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147423837' --- -## Alterando o layout do projeto -Você pode visualizar o seu projeto como uma tabela ou como um quadro. + +## Changing the project layout + +You can view your project as a table or as a board. {% data reusables.projects.open-view-menu %} -1. Em "Layout", clique em **Tabela** ou **Quadro**. - ![Captura de tela mostrando a opção Layout](/assets/images/help/projects-v2/table-or-board.png) +1. Under "Layout", click either **Table** or **Board**. + ![Screenshot showing layout option](/assets/images/help/projects-v2/table-or-board.png) -Como alternativa, abra a paleta de comandos do projeto pressionando {% data variables.projects.command-palette-shortcut %} e comece a digitar "Mudar layout". +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Switch layout." -## Exibindo e ocultando campos +## Showing and hiding fields -Você pode mostrar ou ocultar um campo específico. +You can show or hide a specific field. {% data reusables.projects.open-view-menu %} -1. Em "Configuração", clique em {% octicon "note" aria-label="the note icon" %} e na lista dos campos mostrados no momento. - ![Captura de tela mostrando a opção Mostrar e ocultar campos de menu](/assets/images/help/projects-v2/show-hide-fields-menu-item.png) -1. Marque ou desmarque os campos que você deseja mostrar ou ocultar. - ![Captura de tela mostrando o menu Mostrar e ocultar campos](/assets/images/help/projects-v2/show-hide-fields.png) +1. Under "Configuration", click {% octicon "note" aria-label="the note icon" %} and the list of currently shown fields. + ![Screenshot showing show and hide fields menu option](/assets/images/help/projects-v2/show-hide-fields-menu-item.png) +1. Select or deselect the fields you want to show or hide. + ![Screenshot showing show and hide fields menu](/assets/images/help/projects-v2/show-hide-fields.png) -Você também pode ocultar campos individuais no modo de exibição de tabela. +You can also hide individual fields in table view. -1. Ao lado do campo que você deseja ocultar, clique em {% octicon "kebab-horizontal" aria-label="the kebab icon" %}. - ![Captura de tela mostrando o ícone do menu de campo](/assets/images/help/projects-v2/modify-field-menu.png) -1. Clique em {% octicon "eye-closed" aria-label="the eye closed icon" %} **Ocultar campo**. - ![Captura de tela mostrando a opção Ocultar menu de campo](/assets/images/help/projects-v2/hide-field-via-menu.png) +1. Next to the field you want to hide, click {% octicon "kebab-horizontal" aria-label="the kebab icon" %}. + ![Screenshot showing field menu icon](/assets/images/help/projects-v2/modify-field-menu.png) +1. Click {% octicon "eye-closed" aria-label="the eye closed icon" %} **Hide field**. + ![Screenshot showing hide field menu option](/assets/images/help/projects-v2/hide-field-via-menu.png) -Como alternativa, abra a paleta de comandos do projeto pressionando {% data variables.projects.command-palette-shortcut %} e comece a digitar "mostrar", "ocultar" ou o nome do campo. +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "show", "hide", or the name of the field. -## Reordenando campos +## Reordering fields -No layout de tabela, você pode alterar a ordem dos campos. +In table layout, you can change the order of fields. -1. Clique no cabeçalho do campo. - ![Captura de tela mostrando o cabeçalho do campo](/assets/images/help/projects-v2/select-field-header.png) -2. Ao continuar a clicar, arraste o campo para a localização necessária. +1. Click the field header. + ![Screenshot showing the field header](/assets/images/help/projects-v2/select-field-header.png) +2. While continuing to click, drag the field to the required location. -## Reordenando linhas +## Reordering rows -No layout da tabela, você pode alterar a ordem das linhas. +In table layout, you can change the order of rows. -1. Clique no número no início da linha. - ![Captura de tela mostrando o número da linha](/assets/images/help/projects-v2/select-row-number.png) -2. Ao continuar a clicar, arraste a linha para a localização necessária. +1. Click the number at the start of the row. + ![Screenshot showing the row number](/assets/images/help/projects-v2/select-row-number.png) +2. While continuing to click, drag the row to the required location. -## Ordenação por valores do campo +## Sorting by field values -No layout de tabela, você pode classificar itens por um valor de campo. +In table layout, you can sort items by a field value. {% note %} -**Observação:** quando uma tabela é classificada, não é possível reordenar as linhas manualmente. +**Note:** When a table is sorted, you cannot manually reorder rows. {% endnote %} {% data reusables.projects.open-view-menu %} -1. Clique em **Classificar**. - ![Captura de tela mostrando o item de menu Classificar](/assets/images/help/projects-v2/sort-menu-item.png) -1. Selecione o campo pelo qual deseja classificar. - ![Captura de tela mostrando o menu Classificar](/assets/images/help/projects-v2/sort-menu.png) -2. Como opção, para alterar o sentido da classificação, clique em {% octicon "sort-desc" aria-label="the sort icon" %}. - ![Captura de tela mostrando a opção Ordem de classificação](/assets/images/help/projects-v2/sort-order.png) -3. Como alternativa, para remover uma classificação, clique em {% octicon "x" aria-label="the x icon" %} **Sem classificação** na parte inferior da lista. - ![Captura de tela mostrando "Sem classificação"](/assets/images/help/projects-v2/no-sorting.png) +1. Click **Sort**. + ![Screenshot showing the sort menu item](/assets/images/help/projects-v2/sort-menu-item.png) +1. Click the field you want to sort by. + ![Screenshot showing the sort menu](/assets/images/help/projects-v2/sort-menu.png) +2. Optionally, to change the direction of the sort, click {% octicon "sort-desc" aria-label="the sort icon" %}. + ![Screenshot showing sort order option](/assets/images/help/projects-v2/sort-order.png) +3. Optionally, to remove a sort, click {% octicon "x" aria-label="the x icon" %} **No sorting** at the bottom of the list. + ![Screenshot showing "no sorting"](/assets/images/help/projects-v2/no-sorting.png) -Como alternativa, abra a paleta de comandos do projeto pressionando {% data variables.projects.command-palette-shortcut %} e comece a digitar "Classificar por". +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Sort by." -## Agrupamento por valores de campo no layout de tabela +## Grouping by field values in table layout -No layout da tabela, você pode agrupar os itens por um valor de campo personalizado. Quando os itens são agrupados, se você arrastar um item para um novo grupo, será aplicado o valor desse grupo. Por exemplo, se você agrupar por "Status" e arrastar um item com o status `In progress` para o grupo `Done`, o status do item mudará para `Done`. Da mesma forma, ao adicionar um novo item a um grupo, o novo item será preenchido com o valor do grupo. +In the table layout, you can group items by a custom field value. When items are grouped, if you drag an item to a new group, the value of that group is applied. For example, if you group by "Status" and then drag an item with a status of `In progress` to the `Done` group, the status of the item will switch to `Done`. Similarly, when you add a new item to a group, the new item is populated with the value of the group. {% note %} -**Observação:** não é possível fazer o agrupamento por título, etiquetas, revisores ou solicitações de pull vinculadas. +**Note:** You cannot group by title, labels, reviewers, or linked pull requests. {% endnote %} {% data reusables.projects.open-view-menu %} -1. Clique em {% octicon "rows" aria-label="the rows icon" %} **Agrupar**. - ![Captura de tela mostrando o item de menu Agrupar](/assets/images/help/projects-v2/group-menu-item.png) -1. Selecione o campo pelo qual deseja agrupar. - ![Captura de tela mostrando o menu Agrupar](/assets/images/help/projects-v2/group-menu.png) -2. Como alternativa, para desabilitar o agrupamento, clique em {% octicon "x" aria-label="the x icon" %} **Sem agrupamento** na parte inferior da lista. - ![Captura de tela mostrando "Sem agrupamento"](/assets/images/help/projects-v2/no-grouping.png) +1. Click {% octicon "rows" aria-label="the rows icon" %} **Group**. + ![Screenshot showing the group menu item](/assets/images/help/projects-v2/group-menu-item.png) +1. Click the field you want to group by. + ![Screenshot showing the group menu](/assets/images/help/projects-v2/group-menu.png) +2. Optionally, to disable grouping, click {% octicon "x" aria-label="the x icon" %} **No grouping** at the bottom of the list. + ![Screenshot showing "no grouping"](/assets/images/help/projects-v2/no-grouping.png) -Como alternativa, abra a paleta de comandos do projeto pressionando {% data variables.projects.command-palette-shortcut %} e comece a digitar "Agrupar por". +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Group by." -## Definir o campo da coluna no layout do quadro +{% ifversion projects-v2-numeric-summary %} -No layout do painel, você escolhe qualquer campo de seleção ou iteração para as suas colunas. Se você arrastar um item para uma nova coluna, o valor dessa coluna será aplicado ao item arrastado. Por exemplo, se você usar o campo "Status" para as colunas de quadro e arrastar um item com o status `In progress` para a coluna `Done`, o status do item mudará para `Done`. +## Showing the sum of a number field + +You can configure a view to show the sum of one of more number fields, including a count of items in the group or column. For example, if you have a number field tracking the number of hours each item may take to complete, you can display of sum of those hours for each group or column. + +In board layout, field sums are displayed at the top of each column. In table layout, when you enable grouping by a field, field sums are included in each group's header. {% data reusables.projects.open-view-menu %} -1. Clique em {% octicon "columns" aria-label="the columns icon" %} **Campo de Coluna**. - ![Captura de tela mostrando o item Campo de Coluna](/assets/images/help/projects-v2/column-field-menu-item.png) -1. Clique no campo que você deseja usar. - ![Captura de tela mostrando o menu Campo de Coluna](/assets/images/help/projects-v2/column-field-menu.png) +1. Click {% octicon "number" aria-label="the number icon" %} **Field sum**. + + ![Screenshot showing the field sum menu item](/assets/images/help/projects-v2/field-sum-menu.png) + +1. Select the fields you want to include. + + ![Screenshot showing the field sum menu](/assets/images/help/projects-v2/field-sum-select-field.png) + -Como alternativa, abra a paleta de comandos do projeto pressionando {% data variables.projects.command-palette-shortcut %} e comece a digitar "Campo de coluna por". +{% endif %} + +## Setting the column field in board layout + +In the board layout, you choose any single select or iteration field for your columns. If you drag an item to a new column, the value of that column is applied to the dragged item. For example, if you use the "Status" field for your board columns and then drag an item with a status of `In progress` to the `Done` column, the status of the item will switch to `Done`. + +{% data reusables.projects.open-view-menu %} +1. Click {% octicon "columns" aria-label="the columns icon" %} **Column field**. + ![Screenshot showing the column field item](/assets/images/help/projects-v2/column-field-menu-item.png) +1. Click the field you want to use. + ![Screenshot showing the column field menu](/assets/images/help/projects-v2/column-field-menu.png) + +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Column field by." + +{% ifversion projects-v2-column-visibility %} + +## Showing and hiding columns in board layout + +In the board layout, you can can choose which columns to display. The available columns are made up of the contents of your selected column field. + +1. In the board layout, scroll to the right of your columns, and click {% octicon "plus" aria-label="the plus icon" %}. + + ![Screenshot showing the plus symbol button](/assets/images/help/projects-v2/board-add-column.png) + +1. Select the columns you want to show. + + ![Screenshot showing the list of columns](/assets/images/help/projects-v2/board-select-columns.png) + +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md index 38a21a7616..d427bed2f3 100644 --- a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md +++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md @@ -1,10 +1,10 @@ --- -title: 'Melhores práticas para {% data variables.product.prodname_projects_v2 %}' -intro: Confira dicas para gerenciar projetos. +title: 'Best practices for {% data variables.product.prodname_projects_v2 %}' +intro: 'Learn tips for managing your projects.' allowTitleToDifferFromFilename: true miniTocMaxHeadingLevel: 3 versions: - feature: projects-v2 + feature: "projects-v2" redirect_from: - /issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects type: overview @@ -12,75 +12,72 @@ topics: - Projects - Issues - Project management -ms.openlocfilehash: 71cf84e26bdbed717fd5b434e92f071550764cdc -ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147880033' --- -Você pode usar {% data variables.product.prodname_projects_v2 %} para gerenciar seu trabalho no {% data variables.product.company_short %}, onde os seus problemas e suas solicitações de pull são mantidos. Leia sobre as dicas para gerenciar seus projetos de forma eficiente e eficaz. Para obter mais informações sobre {% data variables.product.prodname_projects_v2 %}, confira "[Sobre {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)". -## Dividir problemas grandes em problemas menores +You can use {% data variables.product.prodname_projects_v2 %} to manage your work on {% data variables.product.company_short %}, where your issues and pull requests live. Read on for tips to manage your projects efficiently and effectively. For more information about {% data variables.product.prodname_projects_v2 %}, see "[About {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." -Dividir um problema grande em problemas menores torna o trabalho mais gerenciável e permite que os integrantes da equipe trabalhem em paralelo. Isso também gera pull requests menores, que são mais fáceis de revisar. +## Break down large issues into smaller issues -Para acompanhar como os problemas menores encaixam-se na meta maior, use a lista de tarefas, marcos ou etiquetas. Para obter mais informações, confira "[Sobre as listas de tarefas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)", "[Sobre os marcos](/issues/using-labels-and-milestones-to-track-work/about-milestones)" e "[Como gerenciar rótulos](/issues/using-labels-and-milestones-to-track-work/managing-labels)". +Breaking a large issue into smaller issues makes the work more manageable and enables team members to work in parallel. It also leads to smaller pull requests, which are easier to review. -## Comunicar +To track how smaller issues fit into the larger goal, use task lists, milestones, or labels. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)", "[About milestones](/issues/using-labels-and-milestones-to-track-work/about-milestones)", and "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)." -Os problemas e pull requests incluem funcionalidades embutidas para permitir que você se comunique facilmente com os seus colaboradores. Use @mentions para alertar uma pessoa ou toda a equipe sobre um comentário. Atribua colaboradores a problemas para comunicar responsabilidade. Vincule a problemas relacionados ou pull requests para comunicar como eles estão conectados. +## Communicate -## Fazer uso da descrição e do README +Issues and pull requests include built-in features to let you easily communicate with your collaborators. Use @mentions to alert a person or entire team about a comment. Assign collaborators to issues to communicate responsibility. Link to related issues or pull requests to communicate how they are connected. -Use a descrição do seu projeto e o README para compartilhar informações sobre o projeto. +## Make use of the description and README -Por exemplo: +Use your project's description and README to share information about the project. -- Explicando a finalidade do projeto. -- Descrevendo as visualizações do projeto e como usá-las. -- Incluindo links relevantes e pessoas para entrar em contato e obter mais informações. +For example: -Os READMEs de projeto são compatíveis com Markdown, o que permite que você utilize imagens e formatação avançada, como links, listas e cabeçalhos. +- Explaining the purpose of the project. +- Describing the project views and how to use them. +- Including relevant links and people to contact for more information. -Para obter mais informações, confira "[Criar um {% data variables.projects.project_v2 %}](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project)". +Project READMEs support Markdown which allows you to use images and advanced formatting such as links, lists, and headers. -## Usar visualizações +For more information, see "[Creating a {% data variables.projects.project_v2 %}](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project)." -Use as visualizações do projeto para ver o seu projeto de ângulos diferentes. +## Use views -Por exemplo: +Use project views to look at your project from different angles. -- Filtrar por status para visualizar todos os itens não iniciados -- Agrupar por um campo personalizado de prioridade para monitorar o volume de itens de alta prioridade -- Ordenar por um campo de data personalizado para exibir os itens com a data de envio mais recente +For example: -Para obter mais informações, confira "[Personalizar uma exibição](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)". +- Filter by status to view all un-started items +- Group by a custom priority field to monitor the volume of high priority items +- Sort by a custom date field to view the items with the earliest target ship date -## Tenha uma única fonte de verdade +For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)." -Para evitar que as informações não fiquem sincronizadas, mantenha uma única fonte de verdade. Por exemplo, monitore uma data de envio em um único local, em vez de se espalhar por vários campos. Posteriormente, se a data de envio for alterada, você deverá apenas atualizar a data em um só lugar. +## Have a single source of truth -Os {% data variables.product.prodname_projects_v2 %} ficam automaticamente atualizados com os dados do {% data variables.product.company_short %}, como os destinatários, os marcos e as etiquetas. Quando um desses campos é alterado em um problema ou pull request, a alteração é refletida automaticamente no seu projeto. +To prevent information from getting out of sync, maintain a single source of truth. For example, track a target ship date in a single location instead of spread across multiple fields. Then, if the target ship date shifts, you only need to update the date in one location. -## Usar automação +{% data variables.product.prodname_projects_v2 %} automatically stay up to date with {% data variables.product.company_short %} data, such as assignees, milestones, and labels. When one of these fields changes in an issue or pull request, the change is automatically reflected in your project. -Você pode automatizar as tarefas para gastar menos tempo com trabalho e mais tempo no próprio projeto. Quanto menos você precisar se lembrar de fazer manualmente, mais provável será que o seu projeto fique atualizado. +## Use automation -Os {% data variables.product.prodname_projects_v2 %} oferecem fluxos de trabalho internos. Por exemplo, quando um problema é fechado, você pode definir automaticamente o status como "Concluído". +You can automate tasks to spend less time on busy work and more time on the project itself. The less you need to remember to do manually, the more likely your project will stay up to date. -Além disso, {% data variables.product.prodname_actions %} e a API do GraphQL permitem que você automatize as tarefas de gerenciamento de projetos rotineiros. Por exemplo, para manter o controle das solicitações de pull que estão aguardando revisão, crie um fluxo de trabalho que adiciona uma solicitação de pull a um projeto e define o status como "precisa de revisão". Esse processo pode ser disparado automaticamente quando uma solicitação de pull é marcada como "pronta para revisão". +{% data variables.product.prodname_projects_v2 %} offers built-in workflows. For example, when an issue is closed, you can automatically set the status to "Done." {% ifversion projects-v2-auto-archive %}You can also configure built-in workflows to automatically archive items when they meet certain criteria.{% endif %} -- Para obter um exemplo de fluxo de trabalho, confira "[Automatizar {% data variables.product.prodname_projects_v2 %} usando o Actions](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions)". -- Para obter mais informações sobre a API, confira "[Usar a API para gerenciar {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)". -- Para obter mais informações sobre o {% data variables.product.prodname_actions %}, confira "[{% data variables.product.prodname_actions %}](/actions)". +Additionally, {% data variables.product.prodname_actions %} and the GraphQL API enable you to automate routine project management tasks. For example, to keep track of pull requests awaiting review, you can create a workflow that adds a pull request to a project and sets the status to "needs review"; this process can be automatically triggered when a pull request is marked as "ready for review." -## Usar diferentes tipos de campos +- For more information about the built-in workflows, see "[Using the built-in automations](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations)."{% ifversion projects-v2-auto-archive %} +- For more information about automatically archiving items, see "[Archiving items automatically](/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically)."{% endif %} +- For an example workflow, see "[Automating {% data variables.product.prodname_projects_v2 %} using Actions](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions)." +- For more information about the API, see "[Using the API to manage {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)." +- For more information about {% data variables.product.prodname_actions %}, see ["{% data variables.product.prodname_actions %}](/actions)." -Aproveite os vários tipos de campo para atender às suas necessidades. +## Use different field types -Use um campo de iteração para agendar o trabalho ou criar uma linha do tempo. Você pode agrupar por iteração para ver se os itens estão equilibrados entre iterações, ou você pode filtrar para focar em uma única iteração. Os campos de iteração também permitem ver o trabalho que você realizou em iterações anteriores, o que pode ajudar no planejamento de velocidade e refletir sobre as realizações da sua equipe. Os campos de iteração também são compatíveis com pausas para mostrar quando você e sua equipe estão tirando tempo de suas iterações. Para obter mais informações, confira "[Sobre campos de iteração](/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields)". +Take advantage of the various field types to meet your needs. -Use um único campo de seleção para rastrear informações sobre uma tarefa com base em uma lista de valores predefinidos. Por exemplo, monitore a prioridade ou a fase do projeto. Como os valores são selecionados a partir de uma lista predefinida, você pode facilmente agrupar ou filtrar focar em itens com um valor específico. +Use an iteration field to schedule work or create a timeline. You can group by iteration to see if items are balanced between iterations, or you can filter to focus on a single iteration. Iteration fields also let you view work that you completed in past iterations, which can help with velocity planning and reflecting on your team's accomplishments. Iteration fields also support breaks to show when you and your team are taking time away from their iterations. For more information, see "[About iteration fields](/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields)." -Para obter mais informações sobre os diferentes tipos de campos, confira "[Noções básicas de tipos de campos](/issues/planning-and-tracking-with-projects/understanding-field-types)". +Use a single select field to track information about a task based on a preset list of values. For example, track priority or project phase. Since the values are selected from a preset list, you can easily group or filter to focus on items with a specific value. + +For more information about the different field types, see "[Understanding field types](/issues/planning-and-tracking-with-projects/understanding-field-types)." diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md index ffcac07294..7fc55bb88e 100644 --- a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md +++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md @@ -1,90 +1,86 @@ --- -title: 'Adicionar itens ao seu {% data variables.projects.project_v2 %}' -shortTitle: Adding items -intro: 'Saiba como adicionar solicitações de pull, problemas e rascunhos de problemas aos seus projetos individualmente ou em massa.' +title: 'Adding items to your {% data variables.projects.project_v2 %}' +shortTitle: 'Adding items' +intro: 'Learn how to add pull requests, issues, and draft issues to your projects individually or in bulk.' miniTocMaxHeadingLevel: 4 versions: - feature: projects-v2 + feature: "projects-v2" type: tutorial topics: - Projects allowTitleToDifferFromFilename: true -ms.openlocfilehash: e49758bbf751ddd1cced46719f9740147a1b7b32 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147423730' --- -Seu projeto pode acompanhar os rascunhos de problemas, problemas e pull requests. + +Your project can track draft issues, issues, and pull requests. {% note %} -**Observação:** um projeto pode conter no máximo 1.200 itens e 10.000 itens arquivados. +**Note:** A project can contain a maximum of {% data variables.projects.item_limit %} items and {% data variables.projects.archived_item_limit %} archived items. {% ifversion projects-v2-auto-archive %}To learn more about automatically archiving items when they meet specific criteria, see "[Archiving items automatically](/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically)."{% endif %} {% endnote %} -### Adicionar problemas e solicitações de pull a um projeto +### Adding issues and pull requests to a project -#### Colar a URL de um problema ou de uma solicitação de pull +#### Pasting the URL of an issue or pull request {% data reusables.projects.add-item-via-paste %} -#### Pesquisando um problema ou pull request +#### Searching for an issue or pull request {% data reusables.projects.add-item-bottom-row %} -2. Digite # . -3. Selecione o repositório onde está localizado o pull request ou problema. Você pode digitar parte do nome do repositório para restringir suas opções. - ![Captura de tela mostrando como colar uma URL de problema para adicioná-la ao projeto](/assets/images/help/projects-v2/add-item-select-repo.png) -4. Selecione o problema ou pull request. Você pode digitar parte do título para restringir suas opções. - ![Captura de tela mostrando como colar uma URL de problema para adicioná-la ao projeto](/assets/images/help/projects-v2/add-item-select-issue.png) +2. Enter #. +3. Select the repository where the pull request or issue is located. You can type part of the repository name to narrow down your options. + ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/add-item-select-repo.png) +4. Select the issue or pull request. You can type part of the title to narrow down your options. + ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/add-item-select-issue.png) -#### Adicionar problemas e solicitações de pull em massa +#### Bulk adding issues and pull requests -1. Na linha inferior do projeto, clique em {% octicon "plus" aria-label="plus icon" %}. - ![Captura de tela mostrando o botão + na parte inferior do projeto](/assets/images/help/projects-v2/omnibar-add.png) -1. Clique em **Adicionar item do repositório**. - ![Captura de tela mostrando o item de menu "Adicionar item do repositório"](/assets/images/help/projects-v2/add-bulk-menu-item.png) {% data reusables.projects.bulk-add %} - -#### Adicionar vários problemas ou solicitações de pull de um repositório - -1. Em {% data variables.product.product_location %}, navegue até o repositório que contém os problemas ou solicitações de pull que você deseja adicionar ao seu projeto. -{% data reusables.repositories.sidebar-issue-pr %} -1. À esquerda de cada título de problema, selecione os problemas que você deseja adicionar ao seu projeto. - ![Captura de tela mostrando a caixa de seleção para selecionar o problema ou a solicitação de pull](/assets/images/help/issues/select-issue-checkbox.png) -1. Opcionalmente, para selecionar cada problema ou solicitação de pull na página, na parte superior da lista de problemas ou solicitações de pull, selecione todos. - ![Captura de tela mostrando a caixa de seleção para selecionar tudo na tela](/assets/images/help/issues/select-all-checkbox.png) -1. Acima da lista de problemas ou solicitações de pull, clique em **Projetos**. - ![Captura de tela mostrando a opção Projetos](/assets/images/help/projects-v2/issue-index-project-menu.png) -1. Clique nos projetos aos quais você deseja adicionar os problemas selecionados ou efetuar solicitações de pull. - ![Captura de tela mostrando a caixa de seleção para selecionar tudo na tela](/assets/images/help/projects-v2/issue-index-select-project.png) - -#### Atribuindo um projeto de dentro de um problema ou pull request - -1. Acesse o problema ou pull request que você deseja adicionar a um projeto. -2. Na barra lateral, clique em **Projetos**. - ![Captura de tela mostrando "Projetos" na barra lateral do problema](/assets/images/help/projects-v2/issue-sidebar-projects.png) -3. Selecione o projeto ao qual você deseja adicionar o problema ou pull request. - ![Captura de tela mostrando a seleção de um projeto na barra lateral do problema](/assets/images/help/projects-v2/issue-sidebar-select-project.png) -4. Opcionalmente, preencha os campos personalizados. - ![Barra lateral do projeto](/assets/images/help/projects-v2/issue-edit-project-sidebar.png) - -#### Usando a paleta de comandos para adicionar um problema ou uma solicitação de pull - -1. {% data reusables.projects.open-command-palette %} -1. Digite "Adicionar itens" e pressione Return/Enter. +1. In the bottom row of the project, click {% octicon "plus" aria-label="plus icon" %}. + ![Screenshot showing + button at the bottom of the project](/assets/images/help/projects-v2/omnibar-add.png) +1. Click **Add item from repository**. + ![Screenshot showing "add item from repository" menu item](/assets/images/help/projects-v2/add-bulk-menu-item.png) {% data reusables.projects.bulk-add %} -### Criando problemas de rascunho +#### Adding multiple issues or pull requests from a repository -Os rascunhos são úteis para capturar ideias rapidamente. Ao contrário dos problemas e das solicitações de pull referenciadas de seus repositórios, os rascunhos de problemas só existem em seu projeto. +1. On {% data variables.location.product_location %}, navigate to the repository that contains the issues or pull requests you want to add to your project. +{% data reusables.repositories.sidebar-issue-pr %} +1. To the left of each issue title, select the issues that you want to add to your project. + ![Screenshot showing checkbox to select issue or pull request](/assets/images/help/issues/select-issue-checkbox.png) +1. Optionally, to select every issue or pull request on the page, at the top of the list of issues or pull requests, select all. + ![Screenshot showing checkbox to select all on screen](/assets/images/help/issues/select-all-checkbox.png) +1. Above the list of issues or pull requests, click **Projects**. + ![Screenshot showing projects option](/assets/images/help/projects-v2/issue-index-project-menu.png) +1. Click the projects you want to add the selected issues or pull requests to. + ![Screenshot showing checkbox to select all on screen](/assets/images/help/projects-v2/issue-index-select-project.png) + +#### Assigning a project from within an issue or pull request + +1. Navigate to the issue or pull request that you want to add to a project. +2. In the side bar, click **Projects**. + ![Screenshot showing "Projects" in the issue sidebar](/assets/images/help/projects-v2/issue-sidebar-projects.png) +3. Select the project that you want to add the issue or pull request to. + ![Screenshot showing selecting a project from the issue sidebar](/assets/images/help/projects-v2/issue-sidebar-select-project.png) +4. Optionally, populate the custom fields. + ![Project sidebar](/assets/images/help/projects-v2/issue-edit-project-sidebar.png) + +#### Using the command palette to add an issue or pull request + +1. {% data reusables.projects.open-command-palette %} +1. Start typing "Add items" and press Return. +{% data reusables.projects.bulk-add %} + +### Creating draft issues + +Draft issues are useful to quickly capture ideas. Unlike issues and pull requests that are referenced from your repositories, draft issues exist only in your project. {% data reusables.projects.add-draft-issue %} -Os problemas do rascunho podem ter um título, texto, responsável e quaisquer campos personalizados do seu projeto. Para preencher o repositório, etiquetas ou marcos para o rascunho de um problema, você deverá primeiro converter o rascunho do problema em um problema. Para obter mais informações, confira "[Como converter problemas de rascunho em problemas](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues)". +Draft issues can have a title, text body, assignees, and any custom fields from your project. In order to populate the repository, labels, or milestones for a draft issue, you must first convert the draft issue to an issue. For more information, see "[Converting draft issues to issues](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues)." {% note %} -**Observação**: os usuários não receberão notificações quando forem atribuídos ou mencionados em um problema de rascunho, a menos que o problema de rascunho seja convertido em um problema. +**Note**: Users will not receive notifications when they are assigned to or mentioned in a draft issue unless the draft issue is converted to an issue. -{% endnote %} +{% endnote %} \ No newline at end of file diff --git a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md index 7c23598887..d49c64ef7c 100644 --- a/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md +++ b/translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md @@ -1,51 +1,48 @@ --- -title: 'Arquivar itens do seu {% data variables.projects.project_v2 %}' -shortTitle: Archiving items -intro: 'Você pode arquivar itens, mantê-los disponíveis para restauração ou excluí-los permanentemente.' +title: 'Archiving items from your {% data variables.projects.project_v2 %}' +shortTitle: 'Archiving items' +intro: 'You can archive items, keeping them available to restore, or permanently delete them.' miniTocMaxHeadingLevel: 2 versions: - feature: projects-v2 + feature: "projects-v2" type: tutorial topics: - Projects allowTitleToDifferFromFilename: true -ms.openlocfilehash: fb9ea68e00cf968affad5f127c5d8723179e9782 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147423745' --- -## Arquivar itens -Você pode arquivar um item para manter o contexto sobre o item no projeto, mas removê-lo das visualizações do projeto. +## Archiving items -{% data reusables.projects.select-an-item %} {% data reusables.projects.open-item-menu %} -1. Clique em **Arquivar**. - ![Captura de tela mostrando a opção Arquivar](/assets/images/help/projects-v2/archive-menu-item.png) -1. Quando solicitado, confirme sua escolha clicando em **Arquivar**. - ![Captura de tela mostrando o prompt Arquivar](/assets/images/help/projects-v2/archive-item-prompt.png) +You can archive an item to keep the context about the item in the project but remove it from the project views. {% ifversion projects-v2-auto-archive %}You can also configure your project's built-in workflows to automatically archive items that meet certain criteria. For more information, see "[Archiving items automatically](/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically)."{% endif %} -## Restaurando itens arquivados +{% data reusables.projects.select-an-item %} +{% data reusables.projects.open-item-menu %} +1. Click **Archive**. + ![Screenshot showing archive option](/assets/images/help/projects-v2/archive-menu-item.png) +1. When prompted, confirm your choice by clicking **Archive**. + ![Screenshot showing archive prompt](/assets/images/help/projects-v2/archive-item-prompt.png) -1. Procure seu projeto. -1. No canto superior direito, clique em {% octicon "kebab-horizontal" aria-label="The menu icon" %} para abrir o menu. - ![Captura de tela mostrando o ícone de menu](/assets/images/help/projects-v2/open-menu.png) -1. No menu, clique em {% octicon "archive" aria-label="The archive icon" %} **Itens arquivados**. - ![Captura de tela mostrando o item de menu 'Itens arquivados'](/assets/images/help/projects-v2/archived-items-menu-item.png) -1. Opcionalmente, para filtrar os itens arquivados exibidos, digite o filtro na caixa de texto acima da lista de itens. Para obter mais informações sobre os filtros disponíveis, confira "[Filtrar projetos](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)". - ![Captura de tela mostrando o campo para filtrar itens arquivados](/assets/images/help/issues/filter-archived-items.png) -1. À esquerda de cada título de item, selecione os itens que você deseja restaurar. - ![Captura de tela mostrando caixas de seleção ao lado de itens arquivados](/assets/images/help/issues/select-archived-item.png) -1. Para restaurar os itens selecionados, acima da lista de itens, clique em **Restaurar**. - ![Captura de tela mostrando o botão "Restaurar"](/assets/images/help/issues/restore-archived-item-button.png) +## Restoring archived items -## Excluindo itens +1. Navigate to your project. +1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. + ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png) +1. In the menu, click {% octicon "archive" aria-label="The archive icon" %} **Archived items**. + ![Screenshot showing the 'Archived items' menu item](/assets/images/help/projects-v2/archived-items-menu-item.png) +1. Optionally, to filter the archived items displayed, type your filter into the text box above the list of items. For more information about the available filters, see "[Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)." + ![Screenshot showing field for filtering archived items](/assets/images/help/issues/filter-archived-items.png) +1. To the left of each item title, select the items you would like to restore. + ![Screenshot showing checkboxes next to archived items](/assets/images/help/issues/select-archived-item.png) +1. To restore the selected items, above the list of items, click **Restore**. + ![Screenshot showing the "Restore" button](/assets/images/help/issues/restore-archived-item-button.png) -Você pode excluir um item para removê-lo do projeto completamente. +## Deleting items -{% data reusables.projects.select-an-item %} {% data reusables.projects.open-item-menu %} -1. Clique em **Excluir do projeto**. - ![Captura de tela mostrando a opção Excluir](/assets/images/help/projects-v2/delete-menu-item.png) -1. Quando solicitado, confirme sua escolha clicando em **Excluir**. - ![Captura de tela mostrando o prompt Excluir](/assets/images/help/projects-v2/delete-item-prompt.png) +You can delete an item to remove it from the project entirely. + +{% data reusables.projects.select-an-item %} +{% data reusables.projects.open-item-menu %} +1. Click **Delete from project**. + ![Screenshot showing delete option](/assets/images/help/projects-v2/delete-menu-item.png) +1. When prompted, confirm your choice by clicking **Delete**. + ![Screenshot showing delete prompt](/assets/images/help/projects-v2/delete-item-prompt.png) \ No newline at end of file diff --git a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md index 7499c0e224..02f702fa56 100644 --- a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md +++ b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md @@ -1,6 +1,6 @@ --- -title: Sobre o feed de notícias da sua organização -intro: Você pode usar o feed de notícias da sua organização para se manter atualizado com atividades recentes nos repositórios de propriedade da organização. +title: About your organization’s news feed +intro: You can use your organization's news feed to keep up with recent activity on repositories owned by that organization. redirect_from: - /articles/news-feed - /articles/about-your-organization-s-news-feed @@ -15,19 +15,16 @@ topics: - Organizations - Teams shortTitle: Organization news feed -ms.openlocfilehash: 2ef8e11cd2ede1fedd284aed3d554bcd658d413e -ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145126539' --- -O feed de notícias de uma organização mostra a atividade de outras pessoas nos repositórios que pertencem a essa organização. Você pode usar o feed de notícias da sua organização para ver quando alguém abre, fecha ou faz merge de um problema ou uma pull request, cria ou exclui um branch, cria uma tag ou versão, comenta sobre um problema, uma pull request, ou faz commit, ou faz push de novos commits no {% data variables.product.product_name %}. -## Acessar o feed de notícias da sua organização +An organization's news feed shows other people's activity on repositories owned by that organization. You can use your organization's news feed to see when someone opens, closes, or merges an issue or pull request, creates or deletes a branch, creates a tag or release, comments on an issue, pull request, or commit, or pushes new commits to {% data variables.product.product_name %}. -1. {% data variables.product.signin_link %} para a sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. -2. Abra o {% data reusables.user-settings.personal_dashboard %}. -3. Clique no alternador de contexto da conta no canto superior esquerdo da página. - ![Botão do alternador de contexto no Enterprise](/assets/images/help/organizations/account_context_switcher.png) -4. Selecione uma organização no menu suspenso.{% ifversion fpt or ghec %} ![Menu do alternador de contexto no dotcom](/assets/images/help/organizations/account-context-switcher-selected-dotcom.png){% else %} ![Menu do alternador de contexto no Enterprise](/assets/images/help/organizations/account_context_switcher.png){% endif %} +## Accessing your organization's news feed + +1. {% data variables.product.signin_link %} to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. +2. Open your {% data reusables.user-settings.personal_dashboard %}. +3. Click the account context switcher in the upper-left corner of the page. + ![Context switcher button in Enterprise](/assets/images/help/organizations/account_context_switcher.png) +4. Select an organization from the drop-down menu.{% ifversion fpt or ghec %} + ![Context switcher menu in dotcom](/assets/images/help/organizations/account-context-switcher-selected-dotcom.png){% else %} + ![Context switcher menu in Enterprise](/assets/images/help/organizations/account_context_switcher.png){% endif %} diff --git a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md index fcf577f3d0..adb9d914e2 100644 --- a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md +++ b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- -title: Sobre a autenticação de dois fatores e o SAML de logon único -intro: Os administradores da organização podem habilitar o SAML de logon único e a autenticação de dois fatores para adicionar medidas extras de autenticação para os integrantes da organização. +title: About two-factor authentication and SAML single sign-on +intro: Organizations administrators can enable both SAML single sign-on and two-factor authentication to add additional authentication measures for their organization members. redirect_from: - /articles/about-two-factor-authentication-and-saml-single-sign-on - /github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on @@ -10,22 +10,17 @@ topics: - Organizations - Teams shortTitle: 2FA & SAML single sign-on -ms.openlocfilehash: 1dc8eff35906a5f2c59f097d3bf53482547bd1f5 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145126518' --- -A autenticação de dois fatores (2FA, Two-Factor Authentication) fornece autenticação básica para integrantes da organização. Ao habilitar a 2FA, os administradores da organização limitam a probabilidade de que a conta de um integrante em {% data variables.product.product_location %} possa ser comprometida. Para obter mais informações sobre a 2FA, confira "[Sobre a autenticação de dois fatores](/articles/about-two-factor-authentication)". -Para adicionar outras medidas de autenticação, os administradores da organização também podem [habilitar o SSO (logon único) do SAML](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) para que os membros da organização precisem usar o logon único para acessar uma organização. Para obter mais informações sobre o SSO do SAML, confira "[Sobre o gerenciamento de identidades e acesso com o logon único do SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)". +Two-factor authentication (2FA) provides basic authentication for organization members. By enabling 2FA, organization administrators limit the likelihood that a member's account on {% data variables.location.product_location %} could be compromised. For more information on 2FA, see "[About two-factor authentication](/articles/about-two-factor-authentication)." -Se a 2FA e o SAML SSO forem habilitados, os integrantes da organização deverão fazer o seguinte: -- Use a 2FA para efetuar o login na sua conta em {% data variables.product.product_location %} -- Usar o logon único para acessar a organização -- Usar um token autorizado para acesso por API ou Git e usar logon único para autorizar o token +To add additional authentication measures, organization administrators can also [enable SAML single sign-on (SSO)](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) so that organization members must use single sign-on to access an organization. For more information on SAML SSO, see "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)." -## Leitura adicional +If both 2FA and SAML SSO are enabled, organization members must do the following: +- Use 2FA to log in to their account on {% data variables.location.product_location %} +- Use single sign-on to access the organization +- Use an authorized token for API or Git access and use single sign-on to authorize the token -- "[Como impor o logon único do SAML para sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)" +## Further reading + +- "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" diff --git a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md index 62ae7de276..979337cd31 100644 --- a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -1,6 +1,6 @@ --- -title: Exibir e gerenciar o acesso SAML de um membro à organização -intro: 'Você pode visualizar e revogar a identidade vinculada de um integrante da organização, as sessões ativas e as credenciais autorizadas.' +title: Viewing and managing a member's SAML access to your organization +intro: 'You can view and revoke an organization member''s linked identity, active sessions, and authorized credentials.' permissions: Organization owners can view and manage a member's SAML access to an organization. redirect_from: - /articles/viewing-and-revoking-organization-members-authorized-access-tokens @@ -12,50 +12,65 @@ topics: - Organizations - Teams shortTitle: Manage SAML access -ms.openlocfilehash: 5b8dbe15037eabe416a6b0c63df7f893db8445bb -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145126514' --- -## Sobre o acesso SAML à sua organização -Ao habilitar o logon único SAML para a sua organização, cada integrante da organização pode vincular sua identidade externa no seu provedor de identidade (IdP) à sua conta atual em {% data variables.product.product_location %}. Para acessar os recursos da sua organização no {% data variables.product.product_name %}, o integrante deverá ter uma sessão SAML ativa em seu navegador. Para acessar os recursos da sua organização usando a API ou o Git, o integrante deve usar um token de acesso pessoal ou chave SSH que o integrante autorizou a usar com a sua organização. +## About SAML access to your organization -Você pode visualizar e revogar a identidade vinculada de cada integrante, as sessões ativas e as credenciais autorizadas na mesma página. +When you enable SAML single sign-on for your organization, each organization member can link their external identity on your identity provider (IdP) to their existing account on {% data variables.location.product_location %}. To access your organization's resources on {% data variables.product.product_name %}, the member must have an active SAML session in their browser. To access your organization's resources using the API or Git, the member must use a {% data variables.product.pat_generic %} or SSH key that the member has authorized for use with your organization. -## Visualizar e revogar uma identidade vinculada +You can view and revoke each member's linked identity, active sessions, and authorized credentials on the same page. + +## Viewing and revoking a linked identity {% data reusables.saml.about-linked-identities %} -Quando disponível, a entrada incluirá dados de SCIM. Para obter mais informações, consulte "[Sobre o SCIM para organizações](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)". +When available, the entry will include SCIM data. For more information, see "[About SCIM for organizations](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)." {% warning %} -**Aviso:** para organizações que usam o SCIM: -- A revogação de uma identidade de usuário vinculada em {% data variables.product.product_name %} também removerá os metadados SAML e SCIM. Como resultado, o provedor de identidade não poderá sincronizar ou desprovisionar a identidade do usuário vinculada. -- Um administrador deverá revogar uma identidade vinculada por meio do provedor de identidade. -- Para revogar uma identidade vinculada e vincular uma conta diferente por meio do provedor de identidade, um administrador pode remover e reatribuir o usuário ao aplicativo de {% data variables.product.product_name %}. Para obter mais informações, consulte a documentação do seu provedor de identidade. +**Warning:** For organizations using SCIM: +- Revoking a linked user identity on {% data variables.product.product_name %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity. +- An admin must revoke a linked identity through the identity provider. +- To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.product_name %} application. For more information, see your identity provider's documentation. {% endwarning %} {% data reusables.identity-and-permissions.revoking-identity-team-sync %} -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %} {% data reusables.saml.click-person-revoke-identity %} {% data reusables.saml.saml-identity-linked %} {% data reusables.saml.view-sso-identity %} {% data reusables.saml.revoke-sso-identity %} {% data reusables.saml.confirm-revoke-identity %} +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.people %} +{% data reusables.saml.click-person-revoke-identity %} +{% data reusables.saml.saml-identity-linked %} +{% data reusables.saml.view-sso-identity %} +{% data reusables.saml.revoke-sso-identity %} +{% data reusables.saml.confirm-revoke-identity %} -## Visualizar e revogar uma sessão ativa de SAML +## Viewing and revoking an active SAML session -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %} {% data reusables.saml.click-person-revoke-session %} {% data reusables.saml.saml-identity-linked %} {% data reusables.saml.view-saml-sessions %} {% data reusables.saml.revoke-saml-session %} +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.people %} +{% data reusables.saml.click-person-revoke-session %} +{% data reusables.saml.saml-identity-linked %} +{% data reusables.saml.view-saml-sessions %} +{% data reusables.saml.revoke-saml-session %} -## Visualizar e revogar credenciais autorizadas +## Viewing and revoking authorized credentials {% data reusables.saml.about-authorized-credentials %} -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %} {% data reusables.saml.click-person-revoke-credentials %} {% data reusables.saml.saml-identity-linked %} {% data reusables.saml.view-authorized-credentials %} {% data reusables.saml.revoke-authorized-credentials %} {% data reusables.saml.confirm-revoke-credentials %} +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.people %} +{% data reusables.saml.click-person-revoke-credentials %} +{% data reusables.saml.saml-identity-linked %} +{% data reusables.saml.view-authorized-credentials %} +{% data reusables.saml.revoke-authorized-credentials %} +{% data reusables.saml.confirm-revoke-credentials %} -## Leitura adicional +## Further reading -- "[Sobre o gerenciamento de identidades e acessos com o logon único do SAML](/articles/about-identity-and-access-management-with-saml-single-sign-on)"{% ifversion ghec %} -- "[Exibição e gerenciamento do acesso SAML de um usuário à sua conta empresarial](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)"{% endif %} +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"{% ifversion ghec %} +- "[Viewing and managing a user's SAML access to your enterprise account](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)"{% endif %} diff --git a/translations/pt-BR/content/organizations/index.md b/translations/pt-BR/content/organizations/index.md index dc88da942c..cdffdf1c7c 100644 --- a/translations/pt-BR/content/organizations/index.md +++ b/translations/pt-BR/content/organizations/index.md @@ -39,11 +39,11 @@ children: - /managing-peoples-access-to-your-organization-with-roles - /organizing-members-into-teams - /collaborating-with-your-team - - /managing-access-to-your-organizations-repositories + - /managing-user-access-to-your-organizations-repositories - /managing-access-to-your-organizations-project-boards - - /managing-access-to-your-organizations-apps + - /managing-programmatic-access-to-your-organization - /managing-organization-settings - - /restricting-access-to-your-organizations-data + - /managing-oauth-access-to-your-organizations-data - /keeping-your-organization-secure - /managing-saml-single-sign-on-for-your-organization - /granting-access-to-your-organization-with-saml-single-sign-on diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md index eebe6173f8..488ed3cc15 100644 --- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md +++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md @@ -16,7 +16,6 @@ children: - /restricting-email-notifications-for-your-organization - /reviewing-the-audit-log-for-your-organization - /accessing-compliance-reports-for-your-organization - - /reviewing-your-organizations-installed-integrations ms.openlocfilehash: f3170c9636a6d298ba1faad74018a7f8798215d3 ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d ms.translationtype: HT diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md index b63a8babc9..1bdf328430 100644 --- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md +++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md @@ -39,6 +39,7 @@ To search for specific events, use the `action` qualifier in your query. Actions |------------------|-------------------{% ifversion fpt or ghec %} | [`account`](#account-category-actions) | Contains all activities related to your organization account. | [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." +| [`auto_approve_personal_access_token_requests`](#auto_approve_personal_access_token_requests-category-actions) | Contains activities related to your organization's approval policy for {% data variables.product.pat_v2 %}s. For more information, see "[Setting a {% data variables.product.pat_generic %} policy for your organization](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization)." | [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing. | [`business`](#business-category-actions) | Contains activities related to business settings for an enterprise. | | [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae %} @@ -63,10 +64,11 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`org`](#org-category-actions) | Contains activities related to organization membership.{% ifversion ghec %} | [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %} | [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions) | Contains organization-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %} -| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization. +| [`organization_default_label`](#organization_default_label-category-actions) | Contains all activities related to default labels for repositories in your organization. | [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps. | [`packages`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% ifversion fpt or ghec %} | [`payment_method`](#payment_method-category-actions) | Contains all activities related to how your organization pays for GitHub.{% endif %} +| [`personal_access_token`](#personal_access_token-category-actions) | Contains activities related to {% data variables.product.pat_v2 %}s in your organization. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." | [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your organization's profile picture. | [`project`](#project-category-actions) | Contains all activities related to project boards. | [`protected_branch`](#protected_branch-category-actions) | Contains all activities related to protected branches. @@ -209,6 +211,17 @@ An overview of some of the most common actions that are recorded as events in th | `destroy` | Triggered when the administrator of a security advisory removes someone from the credit section. {% endif %} +{% ifversion pat-v2 %} + +### `auto_approve_personal_access_token_requests` category actions + +| Action | Description +|------------------|------------------- +| `disable` | Triggered when the organization must approve {% data variables.product.pat_v2 %}s before the tokens can access organization resources. For more information, see "[Setting a {% data variables.product.pat_generic %} policy for your organization](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization)." +| `enable` | Triggered when {% data variables.product.pat_v2 %}s can access organization resources without prior approval. For more information, see "[Setting a {% data variables.product.pat_generic %} policy for your organization](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization)." + +{% endif %} + {% ifversion fpt or ghec %} ### `billing` category actions @@ -442,6 +455,16 @@ For more information, see "[Managing the publication of {% data variables.produc {% endif %} +### `oauth_application` category actions + +| Action | Description +|------------------|------------------- +| `create` | Triggered when a new {% data variables.product.prodname_oauth_app %} is created. +| `destroy` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is deleted. +| `reset_secret` | Triggered when an {% data variables.product.prodname_oauth_app %}'s client secret is reset. +| `revoke_tokens` | Triggered when an {% data variables.product.prodname_oauth_app %}'s user tokens are revoked. +| `transfer` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is transferred to a new organization. + ### `org` category actions | Action | Description @@ -478,9 +501,15 @@ For more information, see "[Managing the publication of {% data variables.produc | `runner_group_updated` | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." | `runner_group_runners_added` | Triggered when a self-hosted runner is added to a group. For more information, see [Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). | `runner_group_runner_removed` | Triggered when the REST API is used to remove a self-hosted runner from a group. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)." -| `runner_group_runners_updated`| Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."{% ifversion secret-scanning-audit-log-custom-patterns %} +| `runner_group_runners_updated`| Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)." +{%- ifversion code-security-audit-log-events %} +| `secret_scanning_push_protection_custom_message_disabled` | Triggered when an organization owner or admin disables the custom message triggered by an attempted push to a push-protected repository. For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#enabling-secret-scanning-as-a-push-protection-for-an-organization)." +| `secret_scanning_push_protection_custom_message_enabled` | Triggered when an organization owner or admin enables the custom message triggered by an attempted push to a push-protected repository. For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#enabling-secret-scanning-as-a-push-protection-for-an-organization)." +| `secret_scanning_push_protection_custom_message_updated` | Triggered when an organization owner or admin updates the custom message triggered by an attempted push to a push-protected repository. For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#enabling-secret-scanning-as-a-push-protection-for-an-organization)." +{%- endif %} +{%- ifversion secret-scanning-audit-log-custom-patterns %} | `secret_scanning_push_protection_disable ` | Triggered when an organization owner or person with admin access to the organization disables push protection for secret scanning. For more information, see "[Protecting pushes with secret scanning](/enterprise-cloud@latest/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." -| `secret_scanning_push_protection_enable ` | Triggered when an organization owner or person with admin access to the organization enables push protection for secret scanning.{% endif %} +| `secret_scanning_push_protection_enable ` | Triggered when an organization owner or person with admin access to the organization enables push protection for {% data variables.product.prodname_secret_scanning %}.{%- endif %} | `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% ifversion fpt or ghes or ghec %} | `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %}{% ifversion fpt or ghec %} @@ -516,7 +545,7 @@ For more information, see "[Managing the publication of {% data variables.produc | `delete` | Triggered when a custom pattern is removed from secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)." {% endif %} -### `organization_label` category actions +### `organization_default_label` category actions | Action | Description |------------------|------------------- @@ -524,16 +553,6 @@ For more information, see "[Managing the publication of {% data variables.produc | `update` | Triggered when a default label is edited. | `destroy` | Triggered when a default label is deleted. -### `oauth_application` category actions - -| Action | Description -|------------------|------------------- -| `create` | Triggered when a new {% data variables.product.prodname_oauth_app %} is created. -| `destroy` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is deleted. -| `reset_secret` | Triggered when an {% data variables.product.prodname_oauth_app %}'s client secret is reset. -| `revoke_tokens` | Triggered when an {% data variables.product.prodname_oauth_app %}'s user tokens are revoked. -| `transfer` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is transferred to a new organization. - ### `packages` category actions | Action | Description | @@ -555,6 +574,20 @@ For more information, see "[Managing the publication of {% data variables.produc {% endif %} +{% ifversion pat-v2 %} + +### `personal_access_token` category actions + +| Action | Description +|------------------|------------------- +| `access_granted` | Triggered when a {% data variables.product.pat_v2 %} is granted access to organization resources. For more information, see "[Managing requests for {% data variables.product.pat_generic %} in your organization](/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization)." +| `access_revoked` | Triggered when access to organization resources by a {% data variables.product.pat_v2 %} is revoked. The token can still read public organization resources. For more information, see "[Reviewing and revoking {% data variables.product.pat_generic %} in your organization](/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization)." +| `request_cancelled` | Triggered when a member of the organization cancels a request for their {% data variables.product.pat_v2 %} to access organization resources. +| `request_created` | Triggered when a member of the organization creates a {% data variables.product.pat_v2 %} to access organization resources and the organization requires approval before a {% data variables.product.pat_v2 %} can access organization resources. For more information, see "[Managing requests for {% data variables.product.pat_generic %} in your organization](/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization)." +| `request_denied` | Triggered when a request for a {% data variables.product.pat_v2 %} to access organization resources is denied. For more information, see "[Managing requests for {% data variables.product.pat_generic %} in your organization](/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization)." + +{% endif %} + ### `profile_picture` category actions | Action | Description |------------------|------------------- diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md deleted file mode 100644 index a9be5867bc..0000000000 --- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Reviewing your organization's installed integrations -intro: You can review the permission levels for your organization's installed integrations and configure each integration's access to organization repositories. -redirect_from: - - /articles/reviewing-your-organization-s-installed-integrations - - /articles/reviewing-your-organizations-installed-integrations - - /github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations - - /organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Review installed integrations ---- - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} -1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-label="The apps icon" %} {% data variables.product.prodname_github_apps %}**. -{% else %} -1. In the left sidebar, click **Installed {% data variables.product.prodname_github_apps %}**. - ![Installed {% data variables.product.prodname_github_apps %} tab in the organization settings sidebar](/assets/images/help/organizations/org-settings-installed-github-apps.png) -{% endif %} -2. Next to the {% data variables.product.prodname_github_app %} you'd like to review, click **Configure**. - ![Configure button](/assets/images/help/organizations/configure-installed-integration-button.png) -6. Review the {% data variables.product.prodname_github_app %}'s permissions and repository access. - ![Option to give the {% data variables.product.prodname_github_app %} access to all repositories or specific repositories](/assets/images/help/organizations/toggle-integration-repo-access.png) - - To give the {% data variables.product.prodname_github_app %} access to all of your organization's repositories, select **All repositories**. - - To choose specific repositories to give the application access to, select **Only select repositories**, then type a repository name. -7. Click **Save**. diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md deleted file mode 100644 index 93654dd752..0000000000 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Adicionar gerentes do aplicativo GitHub em sua organização -intro: 'Os proprietários da organização podem conceder aos usuários a capacidade de gerenciar alguns ou todos os {% data variables.product.prodname_github_apps %} pertencentes à organização.' -redirect_from: - - /articles/adding-github-app-managers-in-your-organization - - /github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Add GitHub App managers -ms.openlocfilehash: d8389c85c847b750bdb83eb8b922ad16bfa33bf3 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145126481' ---- -Para obter mais informações sobre as permissões de gerente do {% data variables.product.prodname_github_app %}, confira "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#github-app-managers)". - -## Dar a alguém a capacidade de gerenciar todos os {% data variables.product.prodname_github_apps %} pertencentes à organização - -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.github-apps-settings-sidebar %} -1. Em "Gerenciamento", digite o nome de usuário da pessoa que deseja designar como um gerente do {% data variables.product.prodname_github_app %} na organização e clique em **Conceder**. -![Adicionar um gerente do {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/add-github-app-manager.png) - -## Dar a um indivíduo a capacidade de gerenciar um {% data variables.product.prodname_github_app %} individual - -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.github-apps-settings-sidebar %} -1. Em "{% data variables.product.prodname_github_apps %}", clique no avatar do aplicativo ao qual você deseja adicionar um gerente de {% data variables.product.prodname_github_app %}. -![Seleção do {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png) {% data reusables.organizations.app-managers-settings-sidebar %} -1. Em "Gerentes de aplicativo", digite o nome de usuário da pessoa que deseja designar como gerente do Aplicativo do GitHub para o aplicativo e clique em **Conceder**. -![Adicionar um gerente do {% data variables.product.prodname_github_app %} a um aplicativo específico](/assets/images/help/organizations/add-github-app-manager-for-app.png) - -{% ifversion fpt or ghec %} -## Leitura adicional - -- "[Sobre o {% data variables.product.prodname_dotcom %} Marketplace](/articles/about-github-marketplace/)" {% endif %} diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/index.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/index.md deleted file mode 100644 index 77d2cf9b7f..0000000000 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/index.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Gerenciar acessos aos aplicativos da organização -intro: 'Como proprietário da organização, você pode permitir que os integrantes individuais da organização gerenciem {% data variables.product.prodname_github_apps %} na sua organização.' -redirect_from: - - /articles/managing-access-to-your-organization-s-apps - - /articles/managing-access-to-your-organizations-apps - - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -children: - - /adding-github-app-managers-in-your-organization - - /removing-github-app-managers-from-your-organization -shortTitle: Manage access to apps -ms.openlocfilehash: d40873a01f9027b517868c7dfa43df7ead3c33f9 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145126480' ---- - diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md deleted file mode 100644 index 84e26693cd..0000000000 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Remover gerentes do aplicativo GitHub da organização -intro: 'Os proprietários da organização podem revogar as permissões de gerente do {% data variables.product.prodname_github_app %} concedidas a um integrante da organização.' -redirect_from: - - /articles/removing-github-app-managers-from-your-organization - - /github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Remove GitHub App managers -ms.openlocfilehash: c7dc813294a1fdd7e928a4212af30efa1182fd3d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145126479' ---- -Para obter mais informações sobre as permissões de gerente do {% data variables.product.prodname_github_app %}, confira "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#github-app-managers)". - -## Remover as permissões de gerente do {% data variables.product.prodname_github_app %} em toda a organização - -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.github-apps-settings-sidebar %} -1. Em "Gerenciamento", localize o nome de usuário da pessoa da qual você deseja remover as permissões de gerente do {% data variables.product.prodname_github_app %} e clique em **Revogar**. -![Revogar as permissões de gerente do {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/github-app-manager-revoke-permissions.png) - -## Remover as permissões de gerente do {% data variables.product.prodname_github_app %} de um {% data variables.product.prodname_github_app %} individual - -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.github-apps-settings-sidebar %} -1. Em "{% data variables.product.prodname_github_apps %}", clique no avatar do aplicativo do qual você deseja remover um gerente de {% data variables.product.prodname_github_app %}. -![Seleção do {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png) {% data reusables.organizations.app-managers-settings-sidebar %} -1. Em "Gerentes de aplicativos", localize o nome de usuário da pessoa da qual você deseja remover as permissões de gerente do {% data variables.product.prodname_github_app %} e clique em **Revogar**. -![Revogar as permissões de gerente do {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/github-app-manager-revoke-permissions-individual-app.png) - -{% ifversion fpt or ghec %} -## Leitura adicional - -- "[Sobre o {% data variables.product.prodname_dotcom %} Marketplace](/articles/about-github-marketplace/)" {% endif %} diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md deleted file mode 100644 index 99f3938c99..0000000000 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Adding outside collaborators to repositories in your organization -intro: You can allow people who aren't members of your organization to access repositories that your organization owns. -redirect_from: - - /articles/adding-outside-collaborators-to-repositories-in-your-organization - - /github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Add outside collaborator -permissions: People with admin access to a repository can add an outside collaborator to the repository. ---- - -## About outside collaborators - -An outside collaborator is a person who is not a member of your organization, but has access to one or more of your organization's repositories. You can choose the level of access to grant for each outside collaborator. {% data reusables.organizations.outside_collaborator_forks %} - -{% data reusables.organizations.outside-collaborators-use-seats %} - -{% ifversion fpt %} -Organizations that use {% data variables.product.prodname_ghe_cloud %} can restrict the ability to invite collaborators. For more information, see "[Setting permissions for adding outside collaborators](/enterprise-cloud@latest/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators)" in the {% data variables.product.prodname_ghe_cloud %} documentation. -{% else %} -An organization owner can restrict the ability to invite collaborators. For more information, see "[Setting permissions for adding outside collaborators](/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators)." -{% endif %} - -{% ifversion ghes %} -Before you can add someone as an outside collaborator on a repository, the person must have a personal account on {% data variables.product.product_location %}. If your enterprise uses an external authentication system such as SAML or LDAP, the person you want to add must sign in through that system to create an account. If the person does not have access to the authentication system and built-in authentication is enabled for your enterprise, a site administrator can create an account for the person. For more information, see "[Configuring built-in authentication](/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication)." -{% endif %} - -{% ifversion not ghae %} -If your organization requires two-factor authentication, all outside collaborators must enable two-factor authentication before accepting your invitation to collaborate on a repository. For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization)." -{% endif %} - -## Adding outside collaborators to a repository - -{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} -You can give outside collaborators access to a repository in your repository settings. For more information, see "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#inviting-a-team-or-person)." -{% else %} -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -5. In the left sidebar, click **Collaborators & teams**. - ![Repository settings sidebar with Collaborators & teams highlighted](/assets/images/help/repository/org-repo-settings-collaborators-and-teams.png) -6. Under "Collaborators", type the name of the person you'd like to give access to the repository, then click **Add collaborator**. -![The Collaborators section with the Octocat's username entered in the search field](/assets/images/help/repository/org-repo-collaborators-find-name.png) -7. Next to the new collaborator's name, use the drop-down menu and select the appropriate access level. -![The repository permissions picker](/assets/images/help/repository/org-repo-collaborators-choose-permissions.png) -{% endif %} diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md deleted file mode 100644 index 2226cbb263..0000000000 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Cancelar um convite para se tornar um colaborador externo na sua organização -intro: É possível cancelar todos os convites para que uma pessoa se torne um colaborador externo em repositórios que pertencem à sua organização. -permissions: Organization owners can cancel an invitation to become an outside collaborator in the organization. -redirect_from: - - /github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization -versions: - fpt: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Cancel collaborator invitation -ms.openlocfilehash: 4511f6ffd7a22884a390e073826f7ff198adb7f2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145126460' ---- -Você pode visualizar uma lista de todas as pessoas com convites pendentes para se tornar um colaborador externo em qualquer repositório que pertence à sua organização. - -Para cada colaborador pendente, você pode cancelar todos os convites para juntar-se aos repositórios da organização ao mesmo tempo. - -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %} {% data reusables.organizations.people_tab_outside_collaborators %} -5. Clique em **X colaboradores pendentes**. - ![Botão "Colaboradores pendentes"](/assets/images/help/organizations/pending-collaborator-list.png) -6. À direita da pessoa para a qual você deseja cancelar convites, clique em **Cancelar convites**. - ![Botão "Cancelar convite"](/assets/images/help/organizations/cancel-pending-collaborators.png) -7. Clique em **Cancelar convites para colaboradores pendentes**. - ![Botão usado para confirmar o cancelamento](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md deleted file mode 100644 index b53078bad4..0000000000 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: Converter um integrante da organização em colaborador externo -intro: 'Se um membro atual da organização precisar de acesso apenas a determinados repositórios, como consultores ou funcionários temporários, você poderá convertê-los em colaboradores externos.' -permissions: Organization owners can convert an organization member to an outside collaborator. -redirect_from: - - /articles/converting-an-organization-member-to-an-outside-collaborator - - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Convert member to collaborator -ms.openlocfilehash: 4b9330559895ec96cb6c842d89dbe4e9a8773685 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146754595' ---- -## Sobre conversão de membros da organização em colaboradores externos - -Você pode converter um membro de uma organização em um colaborador externo. Para obter mais informações sobre colaboradores externos, confira "[Como adicionar colaboradores externos aos repositórios da sua organização](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)". - -{% ifversion fpt or ghec %} Se a organização pertencer a uma empresa, a conversão{% elsif ghes or ghae %}Conversão{% endif %} de um membro da organização em um colaborador externo poderá ser restrita. Para obter mais informações, confira "[Como impor políticas de gerenciamento de repositório em sua empresa]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-{% ifversion fpt or ghec %}outside-{% endif %}collaborators-to-repositories){% ifversion ghec or ghes or ghae %}"{% elsif fpt %} na documentação do {% data variables.product.prodname_ghe_cloud %}. {% endif %} - -{% data reusables.organizations.outside-collaborators-use-seats %} {% data reusables.organizations.outside_collaborator_forks %} - -Após conversão de um integrante da organização em um colaborador externo, ele só terá acesso aos repositórios que sua associação à equipe atual permitir. A pessoa não será mais um integrante explícito da organização e não poderá mais: - -- Criar equipes -- Ver todos os integrantes e equipes da organização -- @mention qualquer equipe visível -- Seja um mantenedor de equipe - -Para obter mais informações, confira "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)". - -Recomendamos rever o acesso dos membros da organização aos repositórios para garantir que seu o acesso seja como você espera. Para obter mais informações, confira "[Como gerenciar o acesso de uma pessoa a um repositório da organização](/articles/managing-an-individual-s-access-to-an-organization-repository)". - -Na conversão de um membro da organização em um colaborador externo, os privilégios dele como membro da organização ficam salvos por três meses, para que seja possível restaurar os privilégios de associação se você{% ifversion fpt or ghec %} convidá-lo para reingressar{% else %} adicioná-lo de volta{% endif %} na organização nesse período. Para obter mais informações, confira "[Como restabelecer um ex-membro da sua organização](/articles/reinstating-a-former-member-of-your-organization)". - -## Converter um integrante da organização em colaborador externo - -{% note %} - -**Observação:** talvez você não consiga converter um membro da organização em um colaborador externo, se um proprietário da organização{% ifversion not fpt %} ou proprietário da empresa{% endif %} restringiu sua capacidade de adicionar colaboradores externos. - -{% endnote %} - -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %} -4. Selecione a(s) pessoa(s) que deseja converter em colaborador(es) externo(s). - ![Lista de membros com dois membros selecionados](/assets/images/help/teams/list-of-members-selected-bulk.png) -5. Acima da lista de membros, use o menu suspenso e clique em **Converter em colaborador externo**. - ![Menu suspenso com a opção para converter membros em colaboradores externos](/assets/images/help/teams/user-bulk-management-options.png) -6. Leia as informações sobre como converter membros em colaboradores externos e clique em **Converter em colaborador externo**. - ![Informações sobre permissões de colaboradores externos e botão Converter em colaboradores externos](/assets/images/help/teams/confirm-outside-collaborator-bulk.png) - -## Leitura adicional - -- "[Como adicionar colaboradores externos a repositórios na sua organização](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" -- "[Como remover um colaborador externo de um repositório da organização](/articles/removing-an-outside-collaborator-from-an-organization-repository)" -- "[Como converter um membro externo em um colaborador da organização](/articles/converting-an-outside-collaborator-to-an-organization-member)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md deleted file mode 100644 index 02f4590efe..0000000000 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Remover um colaborador externo em integrante da organização -intro: 'Se você quiser dar permissões mais amplas a um colaborador externo nos repositórios da organização, {% ifversion fpt or ghec %}convide-o a se tornar membro{% else %}torne-o membro{% endif %} da organização.' -redirect_from: - - /articles/converting-an-outside-collaborator-to-an-organization-member - - /github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -permissions: 'Organization owners can {% ifversion fpt or ghec %}invite users to join{% else %}add users to{% endif %} an organization.' -topics: - - Organizations - - Teams -shortTitle: Convert collaborator to member -ms.openlocfilehash: bac55802407b46344c807798e4d8eade5f608e01 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145126458' ---- -{% ifversion fpt or ghec %} Se a sua organização estiver usando uma assinatura paga por usuário, uma licença não utilizada precisará estar disponível para que você possa convidar um novo membro para ingressar na organização ou restabelecer um ex-membro da organização. Para obter mais informações, confira "[Sobre os preços por usuário](/articles/about-per-user-pricing)". {% data reusables.organizations.org-invite-expiration %}{% endif %} - -{% ifversion not ghae %} Se a sua organização [exigir que os membros usem a autenticação de dois fatores](/articles/requiring-two-factor-authentication-in-your-organization), os usuários {% ifversion fpt or ghec %}que você convidar precisam [habilitar a autenticação de dois fatores](/articles/securing-your-account-with-two-factor-authentication-2fa) para que possam aceitar o convite.{% else %}precisam [habilitar a autenticação de dois fatores para que você os adicione](/articles/securing-your-account-with-two-factor-authentication-2fa) à organização.{% endif %} {% endif %} - -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %} {% data reusables.organizations.people_tab_outside_collaborators %} {% ifversion fpt or ghec %} -5. À direita do nome do colaborador externo que você deseja tornar membro, use o menu suspenso {% octicon "gear" aria-label="The gear icon" %} e clique em **Convidar para a organização**.![Convidar colaboradores externos para a organização](/assets/images/help/organizations/invite_outside_collaborator_to_organization.png) {% else %} -5. À direita do nome do colaborador externo que você deseja tornar membro, clique em **Convidar para a organização**.![Convidar colaboradores externos para a organização](/assets/images/enterprise/orgs-and-teams/invite_outside_collabs_to_org.png) {% endif %} {% data reusables.organizations.choose-to-restore-privileges %} {% data reusables.organizations.choose-user-role-send-invitation %} {% ifversion fpt or ghec %} {% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} {% endif %} - -## Leitura adicional - -- "[Como converter um membro da organização em um colaborador externo](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/index.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/index.md deleted file mode 100644 index 67f01dd7e6..0000000000 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/index.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Gerenciar o acesso aos repositórios de sua organização -intro: Proprietários da organização podem gerenciar acessos individuais e de equipes aos repositórios da organização. Mantenedores de equipes também podem gerenciar o acesso ao repositório da equipe. -redirect_from: - - /articles/permission-levels-for-an-organization-repository - - /articles/managing-access-to-your-organization-s-repositories - - /articles/managing-access-to-your-organizations-repositories - - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -children: - - /repository-roles-for-an-organization - - /setting-base-permissions-for-an-organization - - /viewing-people-with-access-to-your-repository - - /managing-an-individuals-access-to-an-organization-repository - - /managing-team-access-to-an-organization-repository - - /adding-outside-collaborators-to-repositories-in-your-organization - - /canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization - - /removing-an-outside-collaborator-from-an-organization-repository - - /converting-an-organization-member-to-an-outside-collaborator - - /converting-an-outside-collaborator-to-an-organization-member - - /reinstating-a-former-outside-collaborators-access-to-your-organization -shortTitle: Manage access to repositories -ms.openlocfilehash: e6789a7d8f2379f7aa2a6193d21ecdd385f69bab -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145126457' ---- - diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md deleted file mode 100644 index 24fcd16b9f..0000000000 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: Managing an individual's access to an organization repository -intro: You can manage a person's access to a repository owned by your organization. -redirect_from: - - /articles/managing-an-individual-s-access-to-an-organization-repository-early-access-program - - /articles/managing-an-individual-s-access-to-an-organization-repository - - /articles/managing-an-individuals-access-to-an-organization-repository - - /github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Manage individual access -permissions: People with admin access to a repository can manage access to the repository. ---- - -## About access to organization repositories - -When you remove a collaborator from a repository in your organization, the collaborator loses read and write access to the repository. If the repository is private and the collaborator has forked the repository, then their fork is also deleted, but the collaborator will still retain any local clones of your repository. - -{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} - -{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} -## Managing an individual's access to an organization repository -You can give a person access to a repository or change a person's level of access to a repository in your repository settings. For more information, see "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." -{% else %} -## Giving a person access to a repository - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.navigate-to-manage-access %} -{% data reusables.organizations.invite-teams-or-people %} -1. In the search field, start typing the name of the person to invite, then click a name in the list of matches. - ![Search field for typing the name of a team or person to invite to the repository](/assets/images/help/repository/manage-access-invite-search-field.png) -6. Under "Choose a role", select the repository role to assign the person, then click **Add NAME to REPOSITORY**. - ![Selecting permissions for the team or person](/assets/images/help/repository/manage-access-invite-choose-role-add.png) - -## Managing an individual's access to an organization repository - -{% data reusables.profile.access_org %} -{% data reusables.user-settings.access_org %} -{% data reusables.organizations.people %} -4. Click either **Members** or **Outside collaborators** to manage people with different types of access. ![Button to invite members or outside collaborators to an organization](/assets/images/help/organizations/select-outside-collaborators.png) -5. To the right of the name of the person you'd like to manage, use the {% octicon "gear" aria-label="The Settings gear" %} drop-down menu, and click **Manage**. - ![The manage access link](/assets/images/help/organizations/member-manage-access.png) -6. On the "Manage access" page, next to the repository, click **Manage access**. -![Manage access button for a repository](/assets/images/help/organizations/repository-manage-access.png) -7. Review the person's access to a given repository, such as whether they're a collaborator or have access to the repository via team membership. -![Repository access matrix for the user](/assets/images/help/organizations/repository-access-matrix-for-user.png) -{% endif %} -## Further reading - -{% ifversion fpt or ghec %}- "[Limiting interactions with your repository](/articles/limiting-interactions-with-your-repository)"{% endif %} -- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md deleted file mode 100644 index 039d6e4860..0000000000 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: Managing team access to an organization repository -intro: 'You can give a team access to a repository, remove a team''s access to a repository, or change a team''s permission level for a repository.' -redirect_from: - - /articles/managing-team-access-to-an-organization-repository-early-access-program - - /articles/managing-team-access-to-an-organization-repository - - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Manage team access ---- - -People with admin access to a repository can manage team access to the repository. Team maintainers can remove a team's access to a repository if the team has direct access to it. If the team's access to the repository is inherited from a parent team, maintainers can choose to reset the current permission to match the parent team's permission. - -{% warning %} - -**Warnings:** -- You can change a team's permission level if the team has direct access to a repository. If the team's access to the repository is inherited from a parent team, you must change the parent team's access to the repository. -- If you add or remove repository access for a parent team, each of that parent's child teams will also receive or lose access to the repository. For more information, see "[About teams](/articles/about-teams)." - -{% endwarning %} - -## Giving a team access to a repository - -{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} -You can give a team access to a repository or change a team's level of access to a repository in your repository settings. For more information, see "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#inviting-a-team-or-person)." -{% else %} -{% data reusables.profile.access_org %} -{% data reusables.user-settings.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team-repositories-tab %} -5. Above the list of repositories, click **Add repository**. - ![The Add repository button](/assets/images/help/organizations/add-repositories-button.png) -6. Type the name of a repository, then click **Add repository to team**. - ![Repository search field](/assets/images/help/organizations/team-repositories-add.png) -7. Optionally, to the right of the repository name, use the drop-down menu and choose a different permission level for the team. - ![Repository access level dropdown](/assets/images/help/organizations/team-repositories-change-permission-level.png) -{% endif %} -## Removing a team's access to a repository - -{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} -You can remove a team's access to an organization repository in your repository settings. For more information, see "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#removing-access-for-a-team-or-person)." - -If a team has direct access to a repository, you can remove that team's access to the repository. If a team's access to the repository is inherited from a parent team, you must remove the repository from the parent team in order to remove the repository from child teams. - -{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} - -{% else %} - -You can remove a team's access to a repository if the team has direct access to a repository. If a team's access to the repository is inherited from a parent team, you must remove the repository from the parent team in order to remove the repository from child teams. - -{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} - -{% data reusables.profile.access_org %} -{% data reusables.user-settings.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team-repositories-tab %} -5. Select the repository or repositories you'd like to remove from the team. - ![List of team repositories with the checkboxes for some repositories selected](/assets/images/help/teams/select-team-repositories-bulk.png) -6. Above the list of repositories, use the drop-down menu, and click **Remove from team**. - ![Drop-down menu with the option to remove a repository from a team](/assets/images/help/teams/remove-team-repo-dropdown.png) -7. Review the repository or repositories that will be removed from the team, then click **Remove repositories**. - ![Modal box with a list of repositories that the team will no longer have access to](/assets/images/help/teams/confirm-remove-team-repos.png) -{% endif %} -## Further reading - -- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md deleted file mode 100644 index 25f911fd73..0000000000 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: Restabelecer o acesso de um ex-colaborador externo à organização -intro: 'É possível restabelecer as permissões de acesso de um ex-colaborador externo para repositórios, forks e configurações da organização.' -redirect_from: - - /articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization - - /articles/reinstating-a-former-outside-collaborators-access-to-your-organization - - /github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Reinstate collaborator -ms.openlocfilehash: 88d986f922f1a66d652dba55f10142f7e493ffa2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146178900' ---- -Quando o acesso de um colaborador externo aos repositórios privados da sua organização é removido, os privilégios e configurações de acesso do usuário são salvos por três meses. Você poderá restaurar os privilégios do usuário se {% ifversion fpt or ghec %}convidá-lo{% else %}adicioná-lo{% endif %} novamente na organização durante esse período. - -{% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} - -Ao restabelecer um ex-colaborador externo, você pode restaurar: - - O acesso anterior do usuário aos repositórios da organização - - As bifurcações privadas de repositórios de propriedade da organização - - A associação nas equipes da organização - - Os acessos e permissões anteriores nos repositórios da organização - - As estrelas dos repositórios da organização - - As atribuições de problemas na organização - - As assinaturas do repositório (configurações de notificação para inspecionar, não inspecionar ou ignorar as atividades de um repositório) - -{% tip %} - -**Dicas**: - - - Somente os proprietários da organização podem restabelecer o acesso de colaboradores externos a uma organização.{% ifversion prevent-org-admin-add-outside-collaborator %} Os proprietários empresariais podem restringir ainda mais a capacidade de restabelecer o acesso de colaboradores externos somente aos proprietários empresariais.{% endif %} Para obter mais informações, confira "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)". - - O restabelecimento de um fluxo de membro no {% data variables.product.product_location %} pode usar o termo "membro" para descrever o restabelecimento de um colaborador externo, mas se você restabelecer essa pessoa e manter os privilégios anteriores dela, ela terá apenas as [permissões anteriores de colaborador externo](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators).{% ifversion fpt or ghec %} - - Se a organização tiver uma assinatura paga por usuário, ela deverá ter uma licença não utilizada disponível para você poder convidar um integrante para participar da organização ou restabelecer um ex-integrante da organização. Para obter mais informações, confira "[Sobre os preços por usuário](/articles/about-per-user-pricing)".{% endif %} - -{% endtip %} - -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %} {% data reusables.organizations.invite_member_from_people_tab %} {% data reusables.organizations.reinstate-user-type-username %} {% ifversion fpt or ghec %} -1. Opte por restaurar os privilégios anteriores do colaborador externo na organização clicando em **Convidar e restabelecer** ou por limpar os privilégios anteriores e definir novas permissões de acesso clicando em **Convidar e começar do zero**. - - {% warning %} - - **Aviso:** caso deseje fazer upgrade do colaborador externo para um membro da sua organização, escolha **Convidar e começar de novo** e selecione uma nova função para essa pessoa. Mas se você optar por começar do zero, as bifurcações privadas de repositórios da organização desse usuário serão perdidas. Para tornar o antigo colaborador externo um membro da sua organização *e* manter os forks dele privados, escolha **Convidar e restabelecer**. Depois que essa pessoa aceitar o convite, você poderá convertê-lo em um membro da organização [convidando-o a ingressar na organização como membro](/articles/converting-an-outside-collaborator-to-an-organization-member). - - {% endwarning %} - - ![Escolha se deseja restaurar as configurações](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) {% else %} -6. Opte por restaurar os privilégios anteriores do colaborador externo na organização clicando em **Adicionar e restabelecer** ou por limpar os privilégios anteriores e definir novas permissões de acesso clicando em **Adicionar e começar do zero**. - - {% warning %} - - **Aviso:** caso deseje fazer upgrade do colaborador externo para um membro da sua organização, escolha **Adicionar e começar de novo** e selecione uma nova função para essa pessoa. Mas se você optar por começar do zero, as bifurcações privadas de repositórios da organização desse usuário serão perdidas. Para tornar o antigo colaborador externo um membro da sua organização *e* manter os forks dele privados, escolha **Adicionar e restabelecer**. Em seguida, você poderá convertê-lo em um membro da organização [adicionando-o à organização como membro](/articles/converting-an-outside-collaborator-to-an-organization-member). - - {% endwarning %} - - ![Escolha se deseja restaurar as configurações](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) {% endif %} {% ifversion fpt or ghec %} -7. Se você limpou os privilégios anteriores de um antigo colaborador externo, escolha uma função para o usuário e, opcionalmente, adicione-o a algumas equipes e clique em **Enviar convite**. - ![Opções Função e Equipe e botão Enviar convite](/assets/images/help/organizations/add-role-send-invitation.png) {% else %} -7. Se você limpou os privilégios anteriores de um antigo colaborador externo, escolha uma função para o usuário e, opcionalmente, adicione-o a algumas equipes e clique em **Adicionar membro**. - ![Opções de função e equipe e botão Adicionar membro](/assets/images/help/organizations/add-role-add-member.png) {% endif %} {% ifversion fpt or ghec %} -8. A pessoa convidada receberá um e-mail com um convite para participar da organização. Ela precisará aceitar o convite antes de se tornar um colaborador externo na organização. {% data reusables.organizations.cancel_org_invite %} {% endif %} - -## Leitura Adicional - -- "[Funções de repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md deleted file mode 100644 index 2460a6e4a0..0000000000 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Removing an outside collaborator from an organization repository -intro: Owners and repository admins can remove an outside collaborator's access to a repository. -redirect_from: - - /articles/removing-an-outside-collaborator-from-an-organization-repository - - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Remove collaborator ---- - -{% ifversion fpt or ghec %} - -{% warning %} - -**Warning:** -- When removing an outside collaborator from a private repository, the paid license count does not automatically downgrade. To pay for fewer licenses after removing users from your organization, follow the steps in "[Downgrading your organization's paid seats](/articles/downgrading-your-organization-s-paid-seats)." - -- You are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. - -{% endwarning %} - -{% endif %} - -While forks of private repositories are deleted when a collaborator is removed, the person will still retain any local clones of your repository. - -## Removing outside collaborators from all repositories in an organization - -{% data reusables.profile.access_org %} -{% data reusables.user-settings.access_org %} -{% data reusables.organizations.people %} -{% data reusables.organizations.people_tab_outside_collaborators %} -5. Select the outside collaborator or outside collaborators you'd like to remove from the organization. -![List of outside collaborators with two outside collaborators selected](/assets/images/help/teams/list-of-outside-collaborators-selected-bulk.png) -6. Above the list of outside collaborators, use the drop-down menu, and click **Remove from all repositories**. -![Drop-down menu with option to remove outside collaborators ](/assets/images/help/teams/user-bulk-management-options-for-outside-collaborators.png) -7. Review the outside collaborator or outside collaborators who will be removed from the organization, then click **Remove outside collaborators**. - ![List of outside collaborators who will be removed and Remove outside collaborators button](/assets/images/help/teams/confirm-remove-outside-collaborators-bulk.png) - -## Removing an outside collaborator from a particular repository in an organization - -If you only want to remove an outside collaborator from certain repositories in your organization, you can remove this person's access to one specific repository at a time. - -{% data reusables.profile.access_org %} -{% data reusables.user-settings.access_org %} -{% data reusables.organizations.people %} -{% data reusables.organizations.people_tab_outside_collaborators %} -5. To the right of the username of the person you want to remove, use the {% octicon "gear" aria-label="The Settings gear" %} drop-down menu, and click **Manage**. - ![Manage access button](/assets/images/help/organizations/member-manage-access.png) -6. To the right of the repository that you want to remove the outside collaborator from, click **Manage access**. -![Select manage access button next to a repository the outside collaborator has access to](/assets/images/help/organizations/second-manage-access-selection-for-collaborator.png) -7. To completely remove the outside collaborator's access to the repository, in the upper right corner, click **Remove access to this repository**. -![Remove access to this repository button](/assets/images/help/organizations/remove-access-to-this-repository.png) -8. To confirm, click **Remove access**. -![Confirm outside collaborator who will be removed from the repository](/assets/images/help/teams/confirm-remove-outside-collaborator-from-a-repository.png) - -{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} -You can also remove an outside collaborator from a repository in the access overview in your repository settings. For more information, see "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#removing-access-for-a-team-or-person)." -{% endif %} -## Further reading - -- "[Adding outside collaborators to repositories in your organization](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" -- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md deleted file mode 100644 index 84d478f3b6..0000000000 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md +++ /dev/null @@ -1,175 +0,0 @@ ---- -title: Repository roles for an organization -intro: 'You can customize access to each repository in your organization by assigning granular roles, giving people access to the features and tasks they need.' -miniTocMaxHeadingLevel: 3 -redirect_from: - - /articles/repository-permission-levels-for-an-organization-early-access-program - - /articles/repository-permission-levels-for-an-organization - - /github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization - - /organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Repository roles ---- - -## Repository roles for organizations - -You can give organization members, outside collaborators, and teams of people different levels of access to repositories owned by an organization by assigning them to roles. Choose the role that best fits each person or team's function in your project without giving people more access to the project than they need. - -From least access to most access, the roles for an organization repository are: -- **Read**: Recommended for non-code contributors who want to view or discuss your project -- **Triage**: Recommended for contributors who need to proactively manage issues and pull requests without write access -- **Write**: Recommended for contributors who actively push to your project -- **Maintain**: Recommended for project managers who need to manage the repository without access to sensitive or destructive actions -- **Admin**: Recommended for people who need full access to the project, including sensitive and destructive actions like managing security or deleting a repository - -{% ifversion fpt %} -If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can create custom repository roles. For more information, see "[Managing custom repository roles for an organization](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)" in the {% data variables.product.prodname_ghe_cloud %} documentation. -{% elsif ghec or ghes > 3.4 or ghae > 3.4 %} -You can create custom repository roles. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." -{% endif %} - -Organization owners can set base permissions that apply to all members of an organization when accessing any of the organization's repositories. For more information, see "[Setting base permissions for an organization](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)." - -Organization owners can also choose to further limit access to certain settings and actions across the organization. For more information on options for specific settings, see "[Managing organization settings](/articles/managing-organization-settings)." - -In addition to managing organization-level settings, organization owners have admin access to every repository owned by the organization. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." - -{% warning %} - -**Warning:** When someone adds a deploy key to a repository, any user who has the private key can read from or write to the repository (depending on the key settings), even if they're later removed from the organization. - -{% endwarning %} - -## Permissions for each role - -{% ifversion fpt %} -Some of the features listed below are limited to organizations using {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} -{% endif %} - -{% ifversion fpt or ghes or ghec %} -{% note %} - -**Note:** The roles required to use security features are listed in "[Access requirements for security features](#access-requirements-for-security-features)" below. - -{% endnote %} -{% endif %} - -| Repository action | Read | Triage | Write | Maintain | Admin | -|:---|:---:|:---:|:---:|:---:|:---:| -| Manage [individual](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository), [team](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository), and [outside collaborator](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization) access to the repository | | | | | **✔️** | -| Pull from the person or team's assigned repositories | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| Fork the person or team's assigned repositories | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| Edit and delete their own comments | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| Open issues | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| Close issues they opened themselves | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| Reopen issues they closed themselves | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| Have an issue assigned to them | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| Send pull requests from forks of the team's assigned repositories | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| Submit reviews on pull requests | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| View published releases | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} -| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% endif %} -| Edit wikis in public repositories | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| Edit wikis in private repositories | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} -| [Report abusive or spammy content](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% endif %} -| Apply/dismiss labels | | **✔️** | **✔️** | **✔️** | **✔️** | -| Create, edit, delete labels | | | **✔️** | **✔️** | **✔️** | -| Close, reopen, and assign all issues and pull requests | | **✔️** | **✔️** | **✔️** | **✔️** | -| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **✔️** | **✔️** | **✔️** | -| Apply milestones | | **✔️** | **✔️** | **✔️** | **✔️** | -| Mark [duplicate issues and pull requests](/articles/about-duplicate-issues-and-pull-requests)| | **✔️** | **✔️** | **✔️** | **✔️** | -| Request [pull request reviews](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) | | **✔️** | **✔️** | **✔️** | **✔️** | -| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **✔️** | **✔️** | **✔️** | -| Push to (write) the person or team's assigned repositories | | | **✔️** | **✔️** | **✔️** | -| Edit and delete anyone's comments on commits, pull requests, and issues | | | **✔️** | **✔️** | **✔️** | -| [Hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **✔️** | **✔️** | **✔️** | -| [Lock conversations](/communities/moderating-comments-and-conversations/locking-conversations) | | | **✔️** | **✔️** | **✔️** | -| Transfer issues (see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)" for details) | | | **✔️** | **✔️** | **✔️** | -| [Act as a designated code owner for a repository](/articles/about-code-owners) | | | **✔️** | **✔️** | **✔️** | -| [Mark a draft pull request as ready for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** | -| [Convert a pull request to a draft](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** | -| Submit reviews that affect a pull request's mergeability | | | **✔️** | **✔️** | **✔️** | -| [Apply suggested changes](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) to pull requests | | | **✔️** | **✔️** | **✔️** | -| Create [status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} -| Create, edit, run, re-run, and cancel [GitHub Actions workflows](/actions/automating-your-workflow-with-github-actions/) | | | **✔️** | **✔️** | **✔️** |{% endif %} -| Create and edit releases | | | **✔️** | **✔️** | **✔️** | -| View draft releases | | | **✔️** | **✔️** | **✔️** | -| Edit a repository's description | | | | **✔️** | **✔️** |{% ifversion fpt or ghae or ghec %} -| [View and install packages](/packages/publishing-and-managing-packages) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **✔️** | **✔️** | **✔️** | -| [Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package) | | | | | **✔️** | {% endif %} -| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **✔️** | **✔️** | -| Enable wikis and restrict wiki editors | | | | **✔️** | **✔️** | -| Enable project boards | | | | **✔️** | **✔️** | -| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **✔️** | **✔️** | -| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **✔️** | **✔️** | -| [Manage branch protection rules](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule) | | | | | **✔️** | -| [Push to protected branches](/articles/about-protected-branches) | | | | **✔️** | **✔️** | -| Merge pull requests on protected branches, even if there are no approving reviews | | | | | **✔️** |{% ifversion fpt or ghes > 3.4 or ghae > 3.4 or ghec %} -| Create tags that match a [tag protection rule](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) | | | | **✔️** | **✔️** | -| Delete tags that match a [tag protection rule](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) | | | | | **✔️** |{% endif %} -| [Create and edit repository social cards](/articles/customizing-your-repositorys-social-media-preview) | | | | **✔️** | **✔️** |{% ifversion fpt or ghec %} -| Limit [interactions in a repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)| | | | **✔️** | **✔️** |{% endif %} -| Delete an issue (see "[Deleting an issue](/articles/deleting-an-issue)") | | | | | **✔️** | -| [Define code owners for a repository](/articles/about-code-owners) | | | | | **✔️** | -| Add a repository to a team (see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" for details) | | | | | **✔️** | -| [Manage outside collaborator access to a repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **✔️** | -| [Change a repository's visibility](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **✔️** | -| Make a repository a template (see "[Creating a template repository](/articles/creating-a-template-repository)") | | | | | **✔️** | -| Change a repository's settings | | | | | **✔️** | -| Manage team and collaborator access to the repository | | | | | **✔️** | -| Edit the repository's default branch | | | | | **✔️** | -| Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **✔️** | -| Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **✔️** | **✔️** | **✔️** | -| Manage webhooks and deploy keys | | | | | **✔️** |{% ifversion fpt or ghec %} -| [Manage data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository) | | | | | **✔️** |{% endif %} -| [Manage the forking policy for a repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **✔️** | -| [Transfer repositories into the organization](/articles/restricting-repository-creation-in-your-organization) | | | | | **✔️** | -| [Delete or transfer repositories out of the organization](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **✔️** | -| [Archive repositories](/articles/about-archiving-repositories) | | | | | **✔️** |{% ifversion fpt or ghec %} -| Display a sponsor button (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **✔️** |{% endif %} -| Create autolink references to external resources, like Jira or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **✔️** |{% ifversion discussions %} -| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **✔️** | **✔️** | -| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions) for {% data variables.product.prodname_discussions %} | | | | **✔️** | **✔️** | -| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | -| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions) to a new repository| | | **✔️** | **✔️** | **✔️** | -| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | -| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | -| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **✔️** | **✔️** | **✔️** | **✔️** | -| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **✔️** | **✔️** | **✔️** | **✔️** | -| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion) | | **✔️** | | **✔️** | **✔️** |{% endif %}{% ifversion fpt or ghec %} -| Create [codespaces](/codespaces/about-codespaces) | | | **✔️** | **✔️** | **✔️** |{% endif %} - -### Access requirements for security features - -In this section, you can find the access required for security features, such as {% data variables.product.prodname_advanced_security %} features. - -| Repository action | Read | Triage | Write | Maintain | Admin | -|:---|:---:|:---:|:---:|:---:|:---:| -| Receive [{% data variables.product.prodname_dependabot_alerts %} for insecure dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **✔️** | -| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **✔️** |{% ifversion ghes or ghae or ghec %} -| [Designate additional people or teams to receive security alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **✔️** |{% endif %}{% ifversion fpt or ghec %} -| Create [security advisories](/code-security/security-advisories/about-github-security-advisories) | | | | | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} -| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **✔️** |{% endif %}{% ifversion fpt or ghec %} -| [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository | | | | | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} -| [View dependency reviews](/code-security/supply-chain-security/about-dependency-review) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% endif %} -| [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **✔️** | **✔️** | **✔️** | -| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️** |{% ifversion ghes or ghae or ghec %} -| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} -| [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **✔️** |{% endif %} - -[1] Repository writers and maintainers can only see alert information for their own commits. - -## Further reading - -- "[Managing access to your organization's repositories](/articles/managing-access-to-your-organization-s-repositories)" -- "[Adding outside collaborators to repositories in your organization](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" -- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md deleted file mode 100644 index 71a4cd0eb4..0000000000 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Definindo permissões base para uma organização -intro: Você pode definir permissões básicas para repositórios que uma organização possui. -permissions: Organization owners can set base permissions for an organization. -redirect_from: - - /github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Set base permissions -ms.openlocfilehash: 734ced023e4a1043634650ff3e4305727397095c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146179924' ---- -## Sobre as permissões básicas para uma organização - -É possível definir as permissões básicas que se aplicam a todos os integrantes da organização ao acessar qualquer um dos repositórios da organização. As permissões básicas não se aplicam a colaboradores externos. - -{% ifversion fpt or ghec %}Por padrão, os membros de uma organização terão permissões de **leitura** nos repositórios da organização.{% endif %} - -Se alguém com acesso de administrador ao repositório de uma organização conceder a um integrante um nível maior de acesso para o repositório, o nível maior de acesso irá substituir a permissão de base. - -{% ifversion custom-repository-roles %} Se você criou uma função de repositório personalizada com uma função herdada com acesso inferior às permissões base da organização, todos os membros atribuídos a essa função terão como padrão as permissões base da organização em vez da função herdada. Para obter mais informações, confira "[Como gerenciar funções de repositório personalizadas de uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)". -{% endif %} - -## Definir permissões básicas - -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.member-privileges %} -5. Em "Permissões básicas", use o menu suspenso para selecionar novas permissões básicas. - ![Seleção do novo nível de permissão no menu suspenso Permissões base](/assets/images/help/organizations/base-permissions-drop-down.png) -6. Revise as alterações. Para confirmar, clique em **Alterar a permissão padrão para PERMISSION**. - ![Como revisar e confirmar a alteração das permissões base](/assets/images/help/organizations/base-permissions-confirm.png) - -## Leitura adicional - -- "[Funções de repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" -- "[Como adicionar colaboradores externos a repositórios na sua organização](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md deleted file mode 100644 index 6c437bf3f1..0000000000 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: Viewing people with access to your repository -intro: 'You can view{% ifversion ghec or ghes or ghae %} and export{% endif %} a list of people with access to a repository within an organization.' -redirect_from: - - /articles/viewing-people-with-access-to-your-repository - - /github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: View people with access -permissions: Organization owners can view people with access to a repository. ---- - -## About the list of people with access to your repository - -You can use this information to help off-board people, gather data for compliance, and other general security checkups. - -{% ifversion fpt %} -Organizations that use {% data variables.product.prodname_ghe_cloud %} can also export a CSV list of people who have access to a repository. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository). -{% endif %} - -{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} -![Access management overview](/assets/images/help/repository/manage-access-overview.png) -{% else %} -![Repository people permissions list](/assets/images/help/repository/repository-permissions-list.png) -{% endif %} -## Viewing people with access to your repository - -{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} -You can see a combined overview of teams and people with access to your repository in your repository settings. For more information, see "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#about-access-management-for-repositories)." -{% else %} -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.accessing-repository-graphs %} -{% data reusables.repositories.accessing-repository-people %} -{% endif %} - -{% ifversion ghec or ghes or ghae %} -## Exporting a list of people with access to your repository - -{% ifversion ghec %} -{% note %} - -**Note:** Only organizations that use {% data variables.product.prodname_ghe_cloud %} can export a list of people with access to a repository. {% data reusables.enterprise.link-to-ghec-trial %} - -{% endnote %} -{% endif %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.accessing-repository-graphs %} -{% data reusables.repositories.accessing-repository-people %} -4. Click **Export CSV**. - ![People tab in the repository sidebar](/assets/images/help/repository/export-repository-permissions.png) -{% endif %} diff --git a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md index ab08538ffc..99c980c99f 100644 --- a/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md +++ b/translations/pt-BR/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md @@ -1,6 +1,6 @@ --- -title: Sobre autoridades certificadas de SSH -intro: 'Com uma autoridade certificada SSH, a organização ou conta corporativa pode oferecer certificados SSH para os integrantes usarem ao acessar seus recursos com o Git.' +title: About SSH certificate authorities +intro: 'With an SSH certificate authority, your organization or enterprise account can provide SSH certificates that members can use to access your resources with Git.' redirect_from: - /articles/about-ssh-certificate-authorities - /github/setting-up-and-managing-organizations-and-teams/about-ssh-certificate-authorities @@ -12,64 +12,60 @@ topics: - Organizations - Teams shortTitle: SSH certificate authorities -ms.openlocfilehash: c4940399efa3c1e88c68224c421de7f43f7ea89b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147061975' --- -## Sobre autoridades certificadas de SSH -Um certificado SSH é um mecanismo utilizado para uma chave SSH assinar outra chave SSH. Se você usa uma autoridade certificada (CA) SSH para fornecer certificados SSH aos integrantes da organização, você pode adicionar a CA em sua conta corporativa ou organização para permitir que integrantes da organização usem os certificados deles para acessar os recursos da organização. +## About SSH certificate authorities + +An SSH certificate is a mechanism for one SSH key to sign another SSH key. If you use an SSH certificate authority (CA) to provide your organization members with signed SSH certificates, you can add the CA to your enterprise account or organization to allow organization members to use their certificates to access organization resources. {% data reusables.organizations.ssh-ca-ghec-only %} -Depois de adicionar uma CA SSH à sua organização ou conta corporativa, você pode usar a CA para assinar certificados SSH de cliente para integrantes da organização. Integrantes da organização podem usar os certificados assinados para acessar os repositórios da sua organização (e somente os repositórios da sua organização) no Git. Opcionalmente, você pode exigir que os integrantes utilizem certificados SSH para acessar recursos da organização. Para obter mais informações, confira "[Como gerenciar as autoridades de certificado SSH da sua organização](/articles/managing-your-organizations-ssh-certificate-authorities)" e "[Como impor políticas para configurações de segurança na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)". +After you add an SSH CA to your organization or enterprise account, you can use the CA to sign client SSH certificates for organization members. Organization members can use the signed certificates to access your organization's repositories (and only your organization's repositories) with Git. Optionally, you can require that members use SSH certificates to access organization resources. For more information, see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" and "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)." -Por exemplo, você pode desenvolver um sistema interno que emite um novo certificado para seus desenvolvedores todas as manhãs. Cada desenvolvedor pode usar o certificado diário para trabalhar nos repositórios da organização no {% data variables.product.product_name %}. No final do dia, o certificado pode expirar automaticamente, protegendo seus repositórios caso o certificado seja adulterado mais tarde. +For example, you can build an internal system that issues a new certificate to your developers every morning. Each developer can use their daily certificate to work on your organization's repositories on {% data variables.product.product_name %}. At the end of the day, the certificate can automatically expire, protecting your repositories if the certificate is later compromised. -{% ifversion ghec %} Os membros da organização podem usar certificados assinados para autenticação mesmo se você tiver imposto o logon único do SAML. A menos que você exija certificados SSH, os integrantes podem continuar a usar outros meios de autenticação para acessar os recursos da organização no Git, como o nome de usuário e senha deles, tokens de acesso pessoais e outras chaves SSH próprias. +{% ifversion ghec %} +Organization members can use their signed certificates for authentication even if you've enforced SAML single sign-on. Unless you make SSH certificates a requirement, organization members can continue to use other means of authentication to access your organization's resources with Git, including their username and password, {% data variables.product.pat_generic %}s, and their own SSH keys. {% endif %} -Os integrantes não poderão usar seus certificados para acessar bifurcações dos seus repositórios que são propriedade das contas pessoais. +Members will not be able to use their certificates to access forks of your repositories that are owned by their personal accounts. -## Sobre os URLs do SSH com certificados SSH +## About SSH URLs with SSH certificates -Se sua organização exigir certificados SSH, para evitar erros de autenticação, os integrantes da organização deverão usar um URL especial que inclua o ID da organização quando executar operações Git por meio do SSH. Este URL especial permite que o cliente e servidor negociem mais facilmente qual chave no computador do integrante deverá ser usada para autenticação. Se um membro usar a URL normal, que começa com `git@github.com`, o cliente SSH poderá oferecer a chave errada, causando uma falha na operação. +If your organization requires SSH certificates, to prevent authentication errors, organization members should use a special URL that includes the organization ID when performing Git operations over SSH. This special URL allows the client and server to more easily negotiate which key on the member's computer should be used for authentication. If a member uses the normal URL, which starts with `git@github.com`, the SSH client might offer the wrong key, causing the operation to fail. -Qualquer pessoa com acesso de leitura no repositório pode encontrar essa URL selecionando o menu suspenso **Código** na página principal do repositório e clicando em **Usar o SSH**. +Anyone with read access to the repository can find this URL by selecting the **Code** dropdown menu on the main page of the repository, then clicking **Use SSH**. -Se sua organização não exigir certificados SSH, os integrantes poderão continuar usando suas próprias chaves SSH ou outros meios de autenticação. Nesse caso, a URL especial ou a URL normal, que começa com `git@github.com`, funcionará. +If your organization doesn't require SSH certificates, members can continue to use their own SSH keys, or other means of authentication. In that case, either the special URL or the normal URL, which starts with `git@github.com`, will work. -## Emitindo certificados +## Issuing certificates -A cada emissão de certificado, você deve incluir uma extensão especificando para qual usuário do {% data variables.product.product_name %} é o certificado. Por exemplo, você pode usar o comando `ssh-keygen` do OpenSSH, substituindo _KEY-IDENTITY_ pela identidade de chave e _USERNAME_ por um nome de usuário do {% data variables.product.product_name %}. O certificado que você gerar será autorizado a agir em nome desse usuário para qualquer um dos recursos da sua organização. Certifique-se de validar a identidade do usuário antes de emitir o certificado. +When you issue each certificate, you must include an extension that specifies which {% data variables.product.product_name %} user the certificate is for. For example, you can use OpenSSH's `ssh-keygen` command, replacing _KEY-IDENTITY_ with your key identity and _USERNAME_ with a {% data variables.product.product_name %} username. The certificate you generate will be authorized to act on behalf of that user for any of your organization's resources. Make sure you validate the user's identity before you issue the certificate. {% note %} -**Observação:** você precisa fazer a atualização para o OpenSSH 7.6 ou posterior para usar esses comandos. +**Note:** You must update to OpenSSH 7.6 or later to use these commands. {% endnote %} ```shell -$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME ./user-key.pub +$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME ./user-key.pub ``` {% warning %} -**Aviso**: depois que um certificado for assinado e emitido, o certificado não poderá ser revogado. Use o sinalizador -`V` para configurar um tempo de vida para o certificado, ou o certificado pode ser usado por tempo indeterminado. +**Warning**: After a certificate has been signed and issued, the certificate cannot be revoked. Make sure to use the -`V` flag to configure a lifetime for the certificate, or the certificate can be used indefinitely. {% endwarning %} -Para emitir um certificado para alguém que utiliza SSH para acessar vários produtos de {% data variables.product.company_short %}, você pode incluir duas extensões de login para especificar o nome de usuário para cada produto. Por exemplo, o comando a seguir emitirá um certificado para _USERNAME-1_ para a conta do usuário do {% data variables.product.prodname_ghe_cloud %} e _USERNAME-2_ para a conta do usuário do {% data variables.product.prodname_ghe_managed %} ou do {% data variables.product.prodname_ghe_server %} em _HOSTNAME_. +To issue a certificate for someone who uses SSH to access multiple {% data variables.product.company_short %} products, you can include two login extensions to specify the username for each product. For example, the following command would issue a certificate for _USERNAME-1_ for the user's account for {% data variables.product.prodname_ghe_cloud %}, and _USERNAME-2_ for the user's account on {% data variables.product.prodname_ghe_managed %} or {% data variables.product.prodname_ghe_server %} at _HOSTNAME_. ```shell -$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@github.com=USERNAME-1 extension:login@HOSTNAME=USERNAME-2 ./user-key.pub +$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@github.com=USERNAME-1 extension:login@HOSTNAME=USERNAME-2 ./user-key.pub ``` -Você pode restringir os endereços IP dos quais um membro da organização pode acessar os recursos da sua organização usando uma extensão `source-address`. A extensão aceita um endereço IP específico ou um intervalo de endereços IP usando a notação CIDR. É possível especificar vários endereços ou intervalos separando os valores com vírgulas. Para obter mais informações, confira "[Roteamento entre domínios sem classes](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)" na Wikipédia. +You can restrict the IP addresses from which an organization member can access your organization's resources by using a `source-address` extension. The extension accepts a specific IP address or a range of IP addresses using CIDR notation. You can specify multiple addresses or ranges by separating the values with commas. For more information, see "[Classless Inter-Domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)" on Wikipedia. ```shell -$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME -O source-address=COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES ./user-key.pub +$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME -O source-address=COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES ./user-key.pub ``` diff --git a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md index d20ed75fb1..3228b6aa3f 100644 --- a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md @@ -1,6 +1,6 @@ --- -title: Como convidar usuários para ingressar em sua organização -intro: 'Você pode convidar qualquer pessoa para se tornar um integrante da sua organização usando o nome de usuário ou endereço de e-mail deles para {% data variables.product.product_location %}.' +title: Inviting users to join your organization +intro: 'You can invite anyone to become a member of your organization using their username or email address for {% data variables.location.product_location %}.' permissions: Organization owners can invite users to join an organization. redirect_from: - /articles/adding-or-inviting-members-to-a-team-in-an-organization @@ -13,26 +13,30 @@ topics: - Organizations - Teams shortTitle: Invite users to join -ms.openlocfilehash: f0b5d1c41fc5f348077a77d29ac4be309c1cad0f -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145093242' --- -## Sobre convites para a organização -Se a organização tiver uma assinatura paga por usuário, ela deverá ter uma licença não utilizada disponível para você poder convidar um integrante para participar da organização ou restabelecer um ex-integrante da organização. Para obter mais informações, confira "[Sobre os preços por usuário](/articles/about-per-user-pricing)". +## About organization invitations + +If your organization has a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." {% data reusables.organizations.org-invite-scim %} -Se a sua organização exige que os integrantes usem a autenticação de dois fatores, os usuários que você convidar deverão ativar a autenticação de dois fatores antes de aceitar o convite. Para obter mais informações, confira "[Como exigir a autenticação de dois fatores na sua organização](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)" e "[Como proteger sua conta com a 2FA (autenticação de dois fatores)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)". +If your organization requires members to use two-factor authentication, users that you invite must enable two-factor authentication before accepting the invitation. For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)" and "[Securing your account with two-factor authentication (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)." -{% ifversion fpt %}As organizações que usam {% data variables.product.prodname_ghe_cloud %}{% else %}Você{% endif %} podem implementar o SCIM para adicionar, gerenciar e remover o acesso dos integrantes da organização a {% data variables.product.prodname_dotcom_the_website %} por meio de um provedor de identidade (IdP). Para obter mais informações, confira "[Sobre o SCIM para organizações](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}."{% endif %} +{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% else %}You{% endif %} can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.prodname_dotcom_the_website %} through an identity provider (IdP). For more information, see "[About SCIM for organizations](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} -## Convidando um usuário para participar da sua organização +## Inviting a user to join your organization -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %} {% data reusables.organizations.invite_member_from_people_tab %} {% data reusables.organizations.invite_to_org %} {% data reusables.organizations.choose-to-restore-privileges %} {% data reusables.organizations.choose-user-role %} {% data reusables.organizations.add-user-to-teams %} {% data reusables.organizations.send-invitation %} {% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.invite_member_from_people_tab %} +{% data reusables.organizations.invite_to_org %} +{% data reusables.organizations.choose-to-restore-privileges %} +{% data reusables.organizations.choose-user-role %} +{% data reusables.organizations.add-user-to-teams %} +{% data reusables.organizations.send-invitation %} +{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} -## Leitura adicional -- "[Como adicionar membros da organização a uma equipe](/articles/adding-organization-members-to-a-team)" +## Further reading +- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)" diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md index e08f2db1a8..88ff35d2d9 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md @@ -1,6 +1,6 @@ --- -title: Como excluir uma conta da organização -intro: 'Quando você exclui uma organização, todos os repositórios, bifurcações de repositórios privados, wikis, problemas, pull requests e páginas de projeto ou de organização são excluídos também. {% ifversion fpt or ghec %}Sua cobrança terminará e, após 90 dias o nome da organização estará disponível para uso em uma nova conta de usuário ou da organização.{% endif %}' +title: Deleting an organization account +intro: 'When you delete an organization, all repositories, forks of private repositories, wikis, issues, pull requests, and Project or Organization Pages are deleted as well. {% ifversion fpt or ghec %}Your billing will end, and after 90 days the organization name becomes available for use on a new user or organization account.{% endif %}' redirect_from: - /articles/deleting-an-organization-account - /github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account @@ -13,33 +13,32 @@ topics: - Organizations - Teams shortTitle: Delete organization -ms.openlocfilehash: e923dcf7fb9135243c5bfe0e68a310719e87ef2e -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145093234' --- -{% ifversion fpt or ghec %} {% tip %} -**Dica**: caso deseje cancelar sua assinatura paga, [faça o downgrade da sua organização para o {% data variables.product.prodname_free_team %}](/articles/downgrading-your-github-subscription) em vez de excluir a organização e o conteúdo. +{% ifversion fpt or ghec %} +{% tip %} + +**Tip**: If you want to cancel your paid subscription, you can [downgrade your organization to {% data variables.product.prodname_free_team %}](/articles/downgrading-your-github-subscription) instead of deleting the organization and its content. {% endtip %} {% endif %} -## 1. Fazer backup do conteúdo da sua organização +## 1. Back up your organization content -{% ifversion not ghes %} Depois que você excluir uma organização, o {% data variables.product.company_short %} **não poderá restaurar seu conteúdo**. Portanto, antes de{% else %}antes de{% endif %} você excluir sua organização, certifique-se de ter uma cópia de todos os repositórios, wikis, problemas e quadros de projetos da conta. +{% ifversion not ghes %} After you delete an organization, {% data variables.product.company_short %} **cannot restore your content**. Therefore, before{% else %}Before{% endif %} you delete your organization, make sure you have a copy of all repositories, wikis, issues, and project boards from the account. -{% ifversion ghes %} {% note %} +{% ifversion ghes %} +{% note %} -**Observação:** se necessário, um administrador do site do {% data variables.product.product_location %} poderá restaurar parcialmente uma organização excluída. Para obter mais informações, confira "[Como restaurar uma organização excluída](/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization)". +**Note:** If necessary, a site administrator for {% data variables.location.product_location %} may be able to partially restore a deleted organization. For more information, see "[Restoring a deleted organization](/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization)." -{% endnote %} {% endif %} +{% endnote %} +{% endif %} -## 2. Excluir a organização +## 2. Delete the organization -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -4. Na parte inferior da página de configurações da organização, clique em **Excluir esta Organização**. - ![Botão Excluir esta Organização](/assets/images/help/settings/settings-organization-delete.png) +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +4. Near the bottom of the organization's settings page, click **Delete this Organization**. + ![Delete this organization button](/assets/images/help/settings/settings-organization-delete.png) diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md index f1fb6e15eb..b181ccd22b 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md @@ -1,6 +1,6 @@ --- -title: Gerenciar o nome de branch-padrão para repositórios na sua organização -intro: 'Você pode definir o nome do branch-padrão para repositórios que os integrantes criam na sua organização em {% data variables.product.product_location %}.' +title: Managing the default branch name for repositories in your organization +intro: 'You can set the default branch name for repositories that members create in your organization on {% data variables.location.product_location %}.' redirect_from: - /github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization permissions: Organization owners can manage the default branch name for new repositories in the organization. @@ -13,31 +13,28 @@ topics: - Organizations - Teams shortTitle: Manage default branch name -ms.openlocfilehash: 38bd35506728f4437c9a1644235fe748c6a8a58a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145095625' --- -## Sobre o gerenciamento do nome do brancc-padrão -Quando um integrante da sua organização cria um novo repositório na sua organização, o repositório contém um branch, que é o branch-padrão. Você pode alterar o nome que {% data variables.product.product_name %} usa para o branch-padrão em novos repositórios que os integrantes da sua organização criam. Para obter mais informações sobre o branch padrão, confira "[Sobre os branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)". +## About management of the default branch name + +When a member of your organization creates a new repository in your organization, the repository contains one branch, which is the default branch. You can change the name that {% data variables.product.product_name %} uses for the default branch in new repositories that members of your organization create. For more information about the default branch, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)." {% data reusables.branches.change-default-branch %} -Se um proprietário da empresa tiver aplicado uma política para o nome do branch padrão para sua empresa, você não poderá definir um nome do branch padrão para sua organização. Em vez disso, você pode alterar o branch padrão para repositórios individuais. Para obter mais informações, confira {% ifversion fpt %}"[Como impor políticas de gerenciamento de repositório na sua empresa](/enterprise-cloud@latest/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)"{% else %}"[Como impor políticas de gerenciamento de repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)"{% endif %} e "[Como alterar o branch padrão](/github/administering-a-repository/changing-the-default-branch)". +If an enterprise owner has enforced a policy for the default branch name for your enterprise, you cannot set a default branch name for your organization. Instead, you can change the default branch for individual repositories. For more information, see {% ifversion fpt %}"[Enforcing repository management policies in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)"{% else %}"[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)"{% endif %} and "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)." -## Definir o nome do branch-padrão +## Setting the default branch name -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.repository-defaults %} -3. Em "Branch padrão do repositório", clique em **Alterar o nome do branch padrão agora**. - ![Botão Substituir](/assets/images/help/organizations/repo-default-name-button.png) -4. Digite o nome-padrão que você gostaria de usar para novos branches. - ![Caixa de texto usada para inserir o nome padrão](/assets/images/help/organizations/repo-default-name-text.png) -5. Clique em **Atualizar**. - ![Botão Atualizar](/assets/images/help/organizations/repo-default-name-update.png) +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +{% data reusables.organizations.repository-defaults %} +3. Under "Repository default branch", click **Change default branch name now**. + ![Override button](/assets/images/help/organizations/repo-default-name-button.png) +4. Type the default name that you would like to use for new branches. + ![Text box for entering default name](/assets/images/help/organizations/repo-default-name-text.png) +5. Click **Update**. + ![Update button](/assets/images/help/organizations/repo-default-name-update.png) -## Leitura adicional +## Further reading -- "[Como gerenciar o nome do branch padrão para seus repositórios](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)" +- "[Managing the default branch name for your repositories](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)" diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index 917a466010..a6056acced 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- -title: Sobre o gerenciamento de identidades e de acesso com o logon único do SAML -intro: 'Se você gerencia centralmente as identidades e aplicativos dos seus usuários com um provedor de identidade (IdP), você pode configurar o Logon Único (SSO) da Linguagem de Markup de Declaração de Segurança (SAML) para proteger os recursos da sua organização em {% data variables.product.prodname_dotcom %}.' +title: About identity and access management with SAML single sign-on +intro: 'If you centrally manage your users'' identities and applications with an identity provider (IdP), you can configure Security Assertion Markup Language (SAML) single sign-on (SSO) to protect your organization''s resources on {% data variables.product.prodname_dotcom %}.' redirect_from: - /articles/about-identity-and-access-management-with-saml-single-sign-on - /github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on @@ -10,63 +10,58 @@ topics: - Organizations - Teams shortTitle: IAM with SAML SSO -ms.openlocfilehash: 509baaf6d9c47295b57d35dfef7d5c65923b6e3c -ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/12/2022 -ms.locfileid: '147526659' --- + {% data reusables.saml.ghec-only %} -## Sobre o SAML SSO +## About SAML SSO {% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.saml-accounts %} -Os proprietários da organização podem aplicar o SSO do SAML para uma organização individual ou os proprietários corporativos podem aplicar o SSO do SAML para todas as organizações em uma conta corporativa. Para obter mais informações, confira "[Como configurar o logon único do SAML para sua empresa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)". +Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)." {% data reusables.saml.outside-collaborators-exemption %} -Antes de ativar o SAML SSO para sua organização, é necessário conectar seu IdP à sua organização. Para obter mais informações, confira "[Como conectar seu provedor de identidade à sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)". +Before enabling SAML SSO for your organization, you'll need to connect your IdP to your organization. For more information, see "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)." -Para uma organização, o SAML SSO pode ser desabilitado, habilitado, mas não aplicado, ou habilitado e aplicado. Depois de ativar o SSO SAML para a sua organização e os integrantes da sua organização efetuarem a autenticação com sucesso com o seu IdP, você poderá aplicar a configuração SAML SSO. Para obter mais informações sobre como impor o SSO do SAML para sua organização do {% data variables.product.prodname_dotcom %}, confira "[Como impor o logon único do SAML para sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)". +For an organization, SAML SSO can be disabled, enabled but not enforced, or enabled and enforced. After you enable SAML SSO for your organization and your organization's members successfully authenticate with your IdP, you can enforce the SAML SSO configuration. For more information about enforcing SAML SSO for your {% data variables.product.prodname_dotcom %} organization, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)." -Os integrantes devem efetuar a autenticação periodicamente com seu IdP para efetuar a autenticação e obter acesso aos recursos da sua organização. A duração desse período de login é especificado pelo seu IdP e geralmente é de 24 horas. Esse requisito de login periódico limita a duração do acesso e exige que os usuários identifiquem-se novamente para continuar. +Members must periodically authenticate with your IdP to authenticate and gain access to your organization's resources. The duration of this login period is specified by your IdP and is generally 24 hours. This periodic login requirement limits the length of access and requires users to re-identify themselves to continue. -Para acessar os recursos protegidos da organização que usam a API e o Git na linha de comando, os integrantes devem autorizar e efetuar a autenticação com um token de acesso pessoal ou chave SSH. Para obter mais informações, confira "[Como autorizar um token de acesso pessoal para uso com o logon único do SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" e "[Como autorizar uma chave SSH para uso com o logon único do SAML](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)". +To access the organization's protected resources using the API and Git on the command line, members must authorize and authenticate with a {% data variables.product.pat_generic %} or SSH key. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." -Na primeira vez que um integrante utiliza o SAML SSO para acessar sua organização, {% data variables.product.prodname_dotcom %} cria automaticamente um registro que vincula a sua organização, a conta do integrante no {% data variables.product.product_location %} e a conta do integrante no seu IdP. Você pode visualizar e revogar a identidade de SAML vinculada, as sessões ativas e credenciais autorizadas para integrantes da sua empresa ou conta corporativa. Para obter mais informações, confira "[Como ver e gerenciar o acesso do SAML de um membro à sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" e "[Como ver e gerenciar o acesso do SAML à sua conta empresarial](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)". +The first time a member uses SAML SSO to access your organization, {% data variables.product.prodname_dotcom %} automatically creates a record that links your organization, the member's account on {% data variables.location.product_location %}, and the member's account on your IdP. You can view and revoke the linked SAML identity, active sessions, and authorized credentials for members of your organization or enterprise account. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" and "[Viewing and managing a user's SAML access to your enterprise account](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)." -Se os integrantes estiverem conectados com uma sessão SAML SSO, ao criarem um novo repositório, a visibilidade-padrão desse repositório será privada. Caso contrário, a visibilidade-padrão será pública. Para obter mais informações sobre a visibilidade do repositório, confira "[Sobre os repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". +If members are signed in with a SAML SSO session when they create a new repository, the default visibility of that repository is private. Otherwise, the default visibility is public. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." -Os integrantes da organização também devem ter uma sessão de SAML ativa para autorizar um {% data variables.product.prodname_oauth_app %}. Você pode optar por não participar deste requisito entrando em contato com {% data variables.contact.contact_support %}. {% data variables.product.product_name %} não recomenda a exclusão deste requisito, o que irá expor sua organização a um maior risco de aquisições de conta e perda potencial de dados. +Organization members must also have an active SAML session to authorize an {% data variables.product.prodname_oauth_app %}. You can opt out of this requirement by contacting {% data variables.contact.contact_support %}. {% data variables.product.product_name %} does not recommend opting out of this requirement, which will expose your organization to a higher risk of account takeovers and potential data loss. {% data reusables.saml.saml-single-logout-not-supported %} -## Serviços SAML compatíveis +## Supported SAML services {% data reusables.saml.saml-supported-idps %} -Alguns IdPs são compatíveis com o o provisionamento de acesso a uma organização {% data variables.product.prodname_dotcom %} via SCIM. Para obter mais informações, confira "[Sobre o SCIM para organizações](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)". +Some IdPs support provisioning access to a {% data variables.product.prodname_dotcom %} organization via SCIM. For more information, see "[About SCIM for organizations](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)." {% data reusables.scim.enterprise-account-scim %} -## Adicionar integrantes a uma organização usando SAML SSO +## Adding members to an organization using SAML SSO -Depois de habilitar o SSO do SAML, há várias maneiras de adicionar membros à organização. Os proprietários da organização podem convidar novos integrantes manualmente no {% data variables.product.product_name %} ou usando a API. Para obter mais informações, confira "[Como convidar usuários para ingressar na sua organização](/articles/inviting-users-to-join-your-organization)" e "[Membros](/rest/reference/orgs#add-or-update-organization-membership)". +After you enable SAML SSO, there are multiple ways you can add new members to your organization. Organization owners can invite new members manually on {% data variables.product.product_name %} or using the API. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/rest/reference/orgs#add-or-update-organization-membership)." -Para provisionar novos usuários sem o convite de um proprietário da organização, você pode usar a URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`, substituindo _ORGANIZATION_ pelo nome da sua organização. Por exemplo, é possível configurar o IdP para que qualquer pessoa que tenha acesso possa clicar em um link no painel do IdP para ingressar na sua organização do {% data variables.product.prodname_dotcom %}. +To provision new users without an invitation from an organization owner, you can use the URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`, replacing _ORGANIZATION_ with the name of your organization. For example, you can configure your IdP so that anyone with access to the IdP can click a link on the IdP's dashboard to join your {% data variables.product.prodname_dotcom %} organization. -Se o seu IdP é compatível com o SCIM, o {% data variables.product.prodname_dotcom %} poderá convidar automaticamente integrantes para participarem da sua organização ao conceder acesso no seu IdP. Se você remover o acesso de um integrante à organização do seu {% data variables.product.prodname_dotcom %} no seu IdP de SAML, o integrante será removido automaticamente da organização de {% data variables.product.prodname_dotcom %}. Para obter mais informações, confira "[Sobre o SCIM para organizações](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)". +If your IdP supports SCIM, {% data variables.product.prodname_dotcom %} can automatically invite members to join your organization when you grant access on your IdP. If you remove a member's access to your {% data variables.product.prodname_dotcom %} organization on your SAML IdP, the member will be automatically removed from the {% data variables.product.prodname_dotcom %} organization. For more information, see "[About SCIM for organizations](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)." {% data reusables.organizations.team-synchronization %} {% data reusables.saml.saml-single-logout-not-supported %} -## Leitura adicional +## Further reading -- "[Referência de configuração do SAML](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference)" -- "[Sobre a autenticação de dois fatores e o logon único do SAML](/articles/about-two-factor-authentication-and-saml-single-sign-on)" -- "[Sobre a autenticação com o logon único do SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" +- "[SAML configuration reference](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference)" +- "[About two-factor authentication and SAML single sign-on ](/articles/about-two-factor-authentication-and-saml-single-sign-on)" +- "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md index 69ac4b7892..ce04ec7d36 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md @@ -1,6 +1,6 @@ --- -title: Configurar SCIM e o logon único SAML usando o Okta -intro: 'Você pode usar o SSO (logon único) do SAML (Security Assertion Markup Language) e o SCIM (Sistema de Gerenciamento de Usuários entre Domínios) com o Okta para gerenciar automaticamente o acesso à organização no {% data variables.product.product_location %}.' +title: Configuring SAML single sign-on and SCIM using Okta +intro: 'You can use Security Assertion Markup Language (SAML) single sign-on (SSO) and System for Cross-domain Identity Management (SCIM) with Okta to automatically manage access to your organization on {% data variables.location.product_location %}.' redirect_from: - /github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta permissions: Organization owners can configure SAML SSO and SCIM using Okta for an organization. @@ -10,54 +10,55 @@ topics: - Organizations - Teams shortTitle: Configure SAML & SCIM with Okta -ms.openlocfilehash: 3b1083e0ec9d792de9e9c1e83cd5b000e8261905 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147883276' --- -## Sobre SAML e SCIM com Okta -Você pode controlar o acesso à sua organização em {% data variables.product.product_location %} e outros aplicativos da web a partir de uma interface central, configurando a organização para usar SAML SSO e o SCIM com Okta, um provedor de identidade (IdP). +## About SAML and SCIM with Okta + +You can control access to your organization on {% data variables.location.product_location %} and other web applications from one central interface by configuring the organization to use SAML SSO and SCIM with Okta, an Identity Provider (IdP). {% data reusables.saml.ghec-only %} -O SAML SSO controla e protege o acesso a recursos da organização, como repositórios, problemas e pull requests. O SCIM adiciona, gerencia e remove automaticamente o acesso dos integrantes à sua organização em {% data variables.product.product_location %} quando você fizer alterações no Okta. Para obter mais informações, confira "[Sobre gerenciamento de identidade e acesso com o logon único do SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)" e "[Sobre o SCIM em organizações](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)". +SAML SSO controls and secures access to organization resources like repositories, issues, and pull requests. SCIM automatically adds, manages, and removes members' access to your organization on {% data variables.location.product_location %} when you make changes in Okta. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)" and "[About SCIM for organizations](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)." -Após ativar o SCIM, os seguintes recursos de provisionamento estarão disponíveis para qualquer usuário ao qual você atribuir seu aplicativo do {% data variables.product.prodname_ghe_cloud %} no Okta. +After you enable SCIM, the following provisioning features are available for any users that you assign your {% data variables.product.prodname_ghe_cloud %} application to in Okta. -| Recurso | Descrição | +| Feature | Description | | --- | --- | -| Fazer push de novos usuários | Ao criar um novo usuário no Okta, o usuário receberá um e-mail para ingressar na sua organização em {% data variables.product.product_location %}. | -| Fazer push de desativações de usuário | Ao desativar um usuário no Okta, ele removerá o usuário da sua organização em {% data variables.product.product_location %}. | -| Fazer push das atualização de perfil | Ao atualizar o perfil de um usuário no Okta, ele irá atualizar os metadados para a associação do usuário na sua organização em {% data variables.product.product_location %}. | -| Reativar usuários | Ao reativar um usuário no Okta, ele enviará um convite por e-mail para o usuário voltar a participar da sua organização em {% data variables.product.product_location %}. | +| Push New Users | When you create a new user in Okta, the user will receive an email to join your organization on {% data variables.location.product_location %}. | +| Push User Deactivation | When you deactivate a user in Okta, Okta will remove the user from your organization on {% data variables.location.product_location %}. | +| Push Profile Updates | When you update a user's profile in Okta, Okta will update the metadata for the user's membership in your organization on {% data variables.location.product_location %}. | +| Reactivate Users | When you reactivate a user in Okta, Okta will send an email invitation for the user to rejoin your organization on {% data variables.location.product_location %}. | -Como alternativa, você pode configurar o SAML SSO para uma empresa usando o Okta. O SCIM para contas corporativas só está disponível com Usuários Corporativos Gerenciados. Para obter mais informações, confira "[Como configurar o logon único do SAML para sua empresa usando o Okta](/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)" e "[Como configurar o provisionamento do SCIM para os Usuários Gerenciados Corporativos com o Okta](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users-with-okta)". +Alternatively, you can configure SAML SSO for an enterprise using Okta. SCIM for enterprise accounts is only available with Enterprise Managed Users. For more information, see "[Configuring SAML single sign-on for your enterprise using Okta](/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)" and "[Configuring SCIM provisioning for Enterprise Managed Users with Okta](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users-with-okta)." -## Adicionar o aplicativo {% data variables.product.prodname_ghe_cloud %} no Okta +## Adding the {% data variables.product.prodname_ghe_cloud %} application in Okta -{% data reusables.saml.okta-sign-on-tab %} {% data reusables.saml.okta-view-setup-instructions %} -1. Habilitar e testar o SAML SSO no {% data variables.product.prodname_dotcom %} usando a URL de logon, a URL do emissor e os certificados públicos da aba "Como configurar o SAML 2.0". Para obter mais informações, confira "[Como habilitar e testar o logon único do SAML para sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization#enabling-and-testing-saml-single-sign-on-for-your-organization)". +{% data reusables.saml.okta-sign-on-tab %} +{% data reusables.saml.okta-view-setup-instructions %} +1. Enable and test SAML SSO on {% data variables.product.prodname_dotcom %} using the sign on URL, issuer URL, and public certificates from the "How to Configure SAML 2.0" guide. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization#enabling-and-testing-saml-single-sign-on-for-your-organization)." -## Configurar provisionamento de acesso com SCIM em Okta +## Configuring access provisioning with SCIM in Okta {% data reusables.scim.dedicated-configuration-account %} -1. Entre no {% data variables.product.prodname_dotcom_the_website %} usando uma conta que seja um proprietário da organização e seja usada apenas para a configuração do SCIM. -1. Para criar uma sessão do SAML ativa para sua organização, navegue até `https://github.com/orgs/ORGANIZATION-NAME/sso`. Para obter mais informações, confira "[Sobre a autenticação com o logon único do SAML](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on#about-oauth-apps-github-apps-and-saml-sso)". -1. Navegue até o Okta. -{% data reusables.saml.okta-dashboard-click-applications %} {% data reusables.saml.okta-applications-click-ghec-application-label %} {% data reusables.saml.okta-provisioning-tab %} {% data reusables.saml.okta-configure-api-integration %} {% data reusables.saml.okta-enable-api-integration %} -1. Clique em **Autenticar-se com o {% data variables.product.prodname_ghe_cloud %} – Organização**. -1. À direita do nome da sua organização, clique em **Conceder**. +1. Sign into {% data variables.product.prodname_dotcom_the_website %} using an account that is an organization owner and is ideally used only for SCIM configuration. +1. To create an active SAML session for your organization, navigate to `https://github.com/orgs/ORGANIZATION-NAME/sso`. For more information, see "[About authentication with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on#about-oauth-apps-github-apps-and-saml-sso)." +1. Navigate to Okta. +{% data reusables.saml.okta-dashboard-click-applications %} +{% data reusables.saml.okta-applications-click-ghec-application-label %} +{% data reusables.saml.okta-provisioning-tab %} +{% data reusables.saml.okta-configure-api-integration %} +{% data reusables.saml.okta-enable-api-integration %} +1. Click **Authenticate with {% data variables.product.prodname_ghe_cloud %} - Organization**. +1. To the right of your organization's name, click **Grant**. - ![Botão "Conceder" para autorizar a integração do Okta e do SCIM para acesso à organização](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png) -1. Clique em **Autorizar o OktaOAN**. -{% data reusables.saml.okta-save-provisioning %} {% data reusables.saml.okta-edit-provisioning %} + !["Grant" button for authorizing Okta SCIM integration to access organization](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png) +1. Click **Authorize OktaOAN**. +{% data reusables.saml.okta-save-provisioning %} +{% data reusables.saml.okta-edit-provisioning %} -## Leitura adicional +## Further reading -- "[Como configurar o logon único do SAML para a sua conta corporativa usando o Okta](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)" -- [Noções básicas sobre o SAML](https://developer.okta.com/docs/concepts/saml/) na documentação do Okta -- [Noções básicas sobre o SCIM](https://developer.okta.com/docs/concepts/scim/) na documentação do Okta +- "[Configuring SAML single sign-on for your enterprise account using Okta](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)" +- [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) in the Okta documentation +- [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) in the Okta documentation diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md index 30a8e80b39..02c9f5a658 100644 --- a/translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md @@ -1,6 +1,6 @@ --- -title: Sobre equipes -intro: As equipes são grupos de membros da organização que refletem a estrutura da sua empresa ou do grupo com menções e permissões de acesso em cascata. +title: About teams +intro: Teams are groups of organization members that reflect your company or group's structure with cascading access permissions and mentions. redirect_from: - /articles/about-teams - /github/setting-up-and-managing-organizations-and-teams/about-teams @@ -12,76 +12,71 @@ versions: topics: - Organizations - Teams -ms.openlocfilehash: 7b899cf08ca58170acdf8fb2fb2ad13d251b76e3 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145149841' --- -![Lista de equipes em uma organização](/assets/images/help/teams/org-list-of-teams.png) -Os proprietários da organização e os mantenedores da equipe podem conceder às equipes acesso de administrador, de leitura ou de gravação aos repositórios da organização. Os membros da organização podem enviar uma notificação para uma equipe inteira mencionando o nome da equipe. Os membros da organização também podem enviar uma notificação para uma equipe inteira solicitando uma análise dessa equipe. Os membros da organização podem solicitar análises de equipes específicas com acesso de leitura ao repositório no qual a solicitação de pull foi aberta. As equipes podem ser designadas como proprietários de determinados tipos de área de código em um arquivo CODEOWNERS. +![List of teams in an organization](/assets/images/help/teams/org-list-of-teams.png) -Para obter mais informações, consulte: -- "[Como gerenciar o acesso da equipe a um repositório da organização](/articles/managing-team-access-to-an-organization-repository)" -- "[Como mencionar pessoas e equipes](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)" -- "[Sobre os proprietários de código](/articles/about-code-owners/)" +Organization owners and team maintainers can give teams admin, read, or write access to organization repositories. Organization members can send a notification to an entire team by mentioning the team's name. Organization members can also send a notification to an entire team by requesting a review from that team. Organization members can request reviews from specific teams with read access to the repository where the pull request is opened. Teams can be designated as owners of certain types or areas of code in a CODEOWNERS file. -![Imagem de uma menção de equipe](/assets/images/help/teams/team-mention.png) +For more information, see: +- "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)" +- "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)" +- "[About code owners](/articles/about-code-owners/)" + +![Image of a team mention](/assets/images/help/teams/team-mention.png) {% ifversion ghes %} -Use também a Sincronização LDAP para sincronizar membros da equipe e funções de equipe do {% data variables.product.product_location %} com os grupos LDAP estabelecidos. Isso permite estabelecer o controle de acesso baseado em função para usuários do servidor LDAP em vez de manualmente no {% data variables.product.product_location %}. Para obter mais informações, confira "[Como habilitar a Sincronização LDAP](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync)". +You can also use LDAP Sync to synchronize {% data variables.location.product_location %} team members and team roles against your established LDAP groups. This lets you establish role-based access control for users from your LDAP server instead of manually within {% data variables.location.product_location %}. For more information, see "[Enabling LDAP Sync](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync)." {% endif %} {% data reusables.organizations.team-synchronization %} -## Visibilidade da equipe +## Team visibility {% data reusables.organizations.types-of-team-visibility %} -Você pode ver todas as equipes às quais você pertence no seu painel pessoal. Para obter mais informações, confira "[Sobre seu painel pessoal](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#finding-your-top-repositories-and-teams)". +You can view all the teams you belong to on your personal dashboard. For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#finding-your-top-repositories-and-teams)." -## Páginas da equipe +## Team pages -Cada equipe tem sua própria página em uma organização. Na página de uma equipe, é possível exibir integrantes da equipe, equipes secundárias e os repositórios da equipe. Os proprietários da organização e os mantenedores de equipe podem acessar as configurações da equipe, bem como atualizar a descrição e a foto de perfil da equipe na página da equipe. +Each team has its own page within an organization. On a team's page, you can view team members, child teams, and the team's repositories. Organization owners and team maintainers can access team settings and update the team's description and profile picture from the team's page. -Os integrantes da organização podem criar e participar de discussões com a equipe. Para obter mais informações, confira "[Sobre as discussões em equipe](/organizations/collaborating-with-your-team/about-team-discussions)". +Organization members can create and participate in discussions with the team. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)." -![Página da equipe listando integrantes e discussões da equipe](/assets/images/help/organizations/team-page-discussions-tab.png) +![Team page listing team members and discussions](/assets/images/help/organizations/team-page-discussions-tab.png) -## Equipes aninhadas +## Nested teams -Você pode refletir seu grupo ou a hierarquia da empresa na sua organização do {% data variables.product.product_name %} com vários níveis de equipes aninhadas. Uma equipe pai pode ter várias equipes filhas, enquanto cada equipe filha tem apenas uma equipe pai. Você não pode aninhar equipes secretas. +You can reflect your group or company's hierarchy within your {% data variables.product.product_name %} organization with multiple levels of nested teams. A parent team can have multiple child teams, while each child team only has one parent team. You cannot nest secret teams. -As equipes filhas herdam as permissões de acesso do pai, simplificando o gerenciamento de permissões para grandes grupos. Os membros das equipes filho também recebem notificações quando a equipe pai é @mentioned, simplificando a comunicação com vários grupos de pessoas. +Child teams inherit the parent's access permissions, simplifying permissions management for large groups. Members of child teams also receive notifications when the parent team is @mentioned, simplifying communication with multiple groups of people. -Por exemplo, se a estrutura da sua equipe for Funcionários > Engenharia > Engenharia de aplicativos > Identidade, conceder à Engenharia acesso de gravação a um repositório significa que a Engenharia de aplicativo e a Identidade também obterão esse acesso. Se você @mention a Equipe de Identidade ou qualquer equipe na parte inferior da hierarquia da organização, elas serão as únicas que receberão uma notificação. +For example, if your team structure is Employees > Engineering > Application Engineering > Identity, granting Engineering write access to a repository means Application Engineering and Identity also get that access. If you @mention the Identity Team or any team at the bottom of the organization hierarchy, they're the only ones who will receive a notification. -![Página das equipes com uma equipe principal e equipes secundárias](/assets/images/help/teams/nested-teams-eng-example.png) +![Teams page with a parent team and child teams](/assets/images/help/teams/nested-teams-eng-example.png) -Para entender facilmente quem compartilha permissões da equipe principal e faz menção, você pode ver todos os integrantes das equipes secundárias de uma equipe principal na guia Members (Integrantes) da página da equipe principal. Os integrantes de uma equipe secundária não são integrantes diretos da equipe principal. +To easily understand who shares a parent team's permissions and mentions, you can see all of the members of a parent team's child teams on the Members tab of the parent team's page. Members of a child team are not direct members of the parent team. -![Página da equipe principal com todos os integrantes das equipes secundárias](/assets/images/help/teams/team-and-subteam-members.png) +![Parent team page with all members of child teams](/assets/images/help/teams/team-and-subteam-members.png) -Você pode escolher uma principal quando criar a equipe ou pode mover uma equipe na hierarquia da organização posteriormente. Para obter mais informações, confira "[Como mover uma equipe na hierarquia da sua organização](/articles/moving-a-team-in-your-organization-s-hierarchy)". +You can choose a parent when you create the team, or you can move a team in your organization's hierarchy later. For more information see, "[Moving a team in your organization’s hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy)." {% data reusables.enterprise_user_management.ldap-sync-nested-teams %} -## Preparar para aninhar equipes em sua organização +## Preparing to nest teams in your organization -Se a sua organização já tiver equipes, você deverá auditar as permissões de acesso ao repositório de cada equipe antes de aninhar equipes acima ou abaixo dela. Também é preciso considerar a nova estrutura que deseja implementar para a organização. +If your organization already has existing teams, you should audit each team's repository access permissions before you nest teams above or below it. You should also consider the new structure you'd like to implement for your organization. -No topo da hierarquia da equipe, você deve fornecer às equipes principais permissões de acesso ao repositório que sejam seguras para cada integrante da equipe principal e suas equipes secundárias. À medida que desce pela hierarquia, você pode conceder às equipes secundárias adicionais, acesso mais granular a repositórios mais confidenciais. +At the top of the team hierarchy, you should give parent teams repository access permissions that are safe for every member of the parent team and its child teams. As you move toward the bottom of the hierarchy, you can grant child teams additional, more granular access to more sensitive repositories. -1. Remova todos os integrantes das equipes existentes -2. Audite e ajuste as permissões de acesso ao repositório de cada equipe e forneça a cada equipe uma equipe principal -3. Crie qualquer equipe nova que desejar, escolha uma principal para cada equipe nova e forneça a ela acesso ao repositório -4. Adicione pessoas diretamente às equipes +1. Remove all members from existing teams +2. Audit and adjust each team's repository access permissions and give each team a parent +3. Create any new teams you'd like to, choose a parent for each new team, and give them repository access +4. Add people directly to teams -## Leitura adicional +## Further reading -- "[Como criar uma equipe](/articles/creating-a-team)" -- "[Como adicionar membros da organização a uma equipe](/articles/adding-organization-members-to-a-team)" +- "[Creating a team](/articles/creating-a-team)" +- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)" diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md index 750301fb4d..e4b9dcfbf5 100644 --- a/translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -1,6 +1,6 @@ --- -title: Sincronizar uma equipe com um grupo de provedor de identidade -intro: 'Você pode sincronizar uma equipe do {% data variables.product.product_name %} com um grupo de IdPs (provedores de identidade) com suporte para adicionar e remover automaticamente os membros da equipe.' +title: Synchronizing a team with an identity provider group +intro: 'You can synchronize a {% data variables.product.product_name %} team with a supported identity provider (IdP) group to automatically add and remove team members.' redirect_from: - /github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group permissions: 'Organization owners and team maintainers can synchronize a {% data variables.product.prodname_dotcom %} team with an IdP group.' @@ -11,85 +11,94 @@ topics: - Organizations - Teams shortTitle: Synchronize with an IdP -ms.openlocfilehash: 5ae57399a05f51334ccd3e99a268fbe9d93c8b47 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147076884' --- + {% data reusables.enterprise-accounts.emu-scim-note %} -## Sobre a sincronização de equipes +## About team synchronization {% data reusables.identity-and-permissions.about-team-sync %} -{% ifversion ghec %}Você pode conectar até cinco grupos de IdP a uma equipe de {% data variables.product.product_name %}.{% elsif ghae %}Você pode conectar uma equipe em {% data variables.product.product_name %} a um grupo de IdP. Todos os usuários do grupo são automaticamente adicionados à equipe e também adicionados à organização principal como integrantes. Ao desconectar um grupo de uma equipe, os usuários que se tornaram integrantes da organização por meio da associação da equipe serão removidos da organização.{% endif %} Você pode atribuir um grupo de IdP a várias equipes de {% data variables.product.product_name %}. +{% ifversion ghec %}You can connect up to five IdP groups to a {% data variables.product.product_name %} team.{% elsif ghae %}You can connect a team on {% data variables.product.product_name %} to one IdP group. All users in the group are automatically added to the team and also added to the parent organization as members. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization.{% endif %} You can assign an IdP group to multiple {% data variables.product.product_name %} teams. -{% ifversion ghec %}A sincronização de equipes não é compatível com grupos de IdP com mais de 5000 integrantes.{% endif %} +{% ifversion ghec %}Team synchronization does not support IdP groups with more than 5000 members.{% endif %} -Uma vez que uma equipe do {% data variables.product.prodname_dotcom %} está conectada a um grupo de IdP, o administrador do IdP deve efetuar as alterações da associação da equipe por meio do provedor de identidade. Você não pode gerenciar a associação da equipe em {% data variables.product.product_name %}{% ifversion ghec %} ou usando a API{% endif %}. +Once a {% data variables.product.prodname_dotcom %} team is connected to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.product_name %}{% ifversion ghec %} or using the API{% endif %}. {% ifversion ghec %}{% data reusables.enterprise-accounts.team-sync-override %}{% endif %} -{% ifversion ghec %} Todas as alterações de associação a uma equipe feitas por meio do IdP serão exibidas no log de auditoria do {% data variables.product.product_name %} como alterações feitas pelo bot de sincronização da equipe. Seu IdP enviará dados de membros da equipe para {% data variables.product.prodname_dotcom %} uma vez a cada hora. -A conexão de uma equipe a um grupo de IdP pode remover alguns integrantes da equipe. Para obter mais informações, confira "[Requisitos para membros de equipes sincronizadas](#requirements-for-members-of-synchronized-teams)". +{% ifversion ghec %} +All team membership changes made through your IdP will appear in the audit log on {% data variables.product.product_name %} as changes made by the team synchronization bot. Your IdP will send team membership data to {% data variables.product.prodname_dotcom %} once every hour. +Connecting a team to an IdP group may remove some team members. For more information, see "[Requirements for members of synchronized teams](#requirements-for-members-of-synchronized-teams)." {% endif %} -{% ifversion ghae %} Quando a associação a um grupo for alterada no IdP, ele enviará uma solicitação do SCIM com as alterações para o {% data variables.product.product_name %} de acordo com o agendamento determinado pelo IdP. Qualquer solicitação que altere a equipe de {% data variables.product.prodname_dotcom %} equipe ou associação da organização será registrada no log de auditoria como alterações feitas pela conta usada para configurar provisionamento do usuário. Para obter mais informações sobre essa conta, confira "[Como configurar o provisionamento de usuário para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". Para obter mais informações sobre agendamentos de solicitação do SCIM, confira "[Verificar o status do provisionamento de usuário](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)" no Microsoft Docs.{% endif %} +{% ifversion ghae %} +When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.product_name %} according to the schedule determined by your IdP. Any requests that change {% data variables.product.prodname_dotcom %} team or organization membership will register in the audit log as changes made by the account used to configure user provisioning. For more information about this account, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." For more information about SCIM request schedules, see "[Check the status of user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)" in the Microsoft Docs. +{% endif %} -As equipes principais não podem sincronizar com grupos de IdP. Se a equipe que você deseja conectar a um grupo IdP for uma equipe principal, recomendamos criar uma equipe nova ou remover as relações aninhadas que fazem da sua equipe uma equipe principal. Para obter mais informações, confira "[Sobre as equipes](/articles/about-teams#nested-teams)", "[Como criar uma equipe](/organizations/organizing-members-into-teams/creating-a-team)" e "[Como mover uma equipe na hierarquia da sua organização](/articles/moving-a-team-in-your-organizations-hierarchy)". +Parent teams cannot synchronize with IdP groups. If the team you want to connect to an IdP group is a parent team, we recommend creating a new team or removing the nested relationships that make your team a parent team. For more information, see "[About teams](/articles/about-teams#nested-teams)," "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)," and "[Moving a team in your organization's hierarchy](/articles/moving-a-team-in-your-organizations-hierarchy)." -Para gerenciar o acesso ao repositório de qualquer equipe do {% data variables.product.prodname_dotcom %} incluindo equipes conectadas a um grupo de IdP, você deve fazer alterações com o {% data variables.product.product_name %}. Para obter mais informações, confira "[Sobre as equipes](/articles/about-teams)" e "[Como gerenciar o acesso da equipe a um repositório da organização](/articles/managing-team-access-to-an-organization-repository)". +To manage repository access for any {% data variables.product.prodname_dotcom %} team, including teams connected to an IdP group, you must make changes with {% data variables.product.product_name %}. For more information, see "[About teams](/articles/about-teams)" and "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)." -{% ifversion ghec %}Você também pode gerenciar a sincronização de equipes com a API. Para obter mais informações, confira "[Sincronização da equipe](/rest/reference/teams#team-sync)".{% endif %} +{% ifversion ghec %}You can also manage team synchronization with the API. For more information, see "[Team synchronization](/rest/reference/teams#team-sync)."{% endif %} {% ifversion ghec %} -## Requisitos para integrantes de equipes sincronizadas +## Requirements for members of synchronized teams -Depois que você conectar uma equipe a um grupo de IdPs, a sincronização da equipe adicionará cada membro do grupo de IdPs à equipe correspondente no {% data variables.product.product_name %} somente se: -- A pessoa for membro da organização no {% data variables.product.product_name %}. -- A pessoa já tiver feito logon com a conta pessoal no {% data variables.product.product_name %} e se autenticado na organização ou na conta corporativa por meio do logon único do SAML, pelo menos uma vez. -- A identidade SSO da pessoa é um integrante do grupo IdP. +After you connect a team to an IdP group, team synchronization will add each member of the IdP group to the corresponding team on {% data variables.product.product_name %} only if: +- The person is a member of the organization on {% data variables.product.product_name %}. +- The person has already logged in with their personal account on {% data variables.product.product_name %} and authenticated to the organization or enterprise account via SAML single sign-on at least once. +- The person's SSO identity is a member of the IdP group. -As equipes ou os membros de grupos existentes que não atenderem a esses critérios serão removidos automaticamente da equipe no {% data variables.product.product_name %} e perderão o acesso aos repositórios. Revogar a identidade vinculada a um usuário também removerá o usuário de quaisquer equipes mapeadas com os grupos de IdP. Para obter mais informações, confira "[Como ver e gerenciar o acesso do SAML de um membro à sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)" e "[Como ver e gerenciar o acesso do SAML de um usuário à sua empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)". +Existing teams or group members who do not meet these criteria will be automatically removed from the team on {% data variables.product.product_name %} and lose access to repositories. Revoking a user's linked identity will also remove the user from from any teams mapped to IdP groups. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)" and "[Viewing and managing a user's SAML access to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)." -Um integrante removido da equipe pode ser adicionado de volta a uma equipe automaticamente após efetuar a autenticação na conta da organização ou na conta corporativa usando SSO e será movidos para o grupo de IdP conectado. +A removed team member can be added back to a team automatically once they have authenticated to the organization or enterprise account using SSO and are moved to the connected IdP group. -Para evitar a remoção involuntária dos integrantes da equipe, recomendamos a aplicar SSO SAML na conta da organização ou da empresa. criar novas equipes para sincronizar dados da associação e verificar a associação de grupo de IdP antes de sincronizar as equipes existentes. Para obter mais informações, confira "[Como impor o logon único do SAML para sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)" e "[Como configurar o logon único do SAML para sua empresa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)". +To avoid unintentionally removing team members, we recommend enforcing SAML SSO in your organization or enterprise account, creating new teams to synchronize membership data, and checking IdP group membership before synchronizing existing teams. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)." {% endif %} -## Pré-requisitos +## Prerequisites -{% ifversion ghec %} Para você conectar uma equipe do {% data variables.product.product_name %} a um grupo do provedor de identidade, o proprietário de uma organização ou de uma empresa precisará habilitar a sincronização da equipe na sua organização ou conta corporativa. Para obter mais informações, confira "[Como gerenciar a sincronização da equipe para sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" e "[Como gerenciar a sincronização da equipe para organizações na sua conta corporativa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)". +{% ifversion ghec %} +Before you can connect a {% data variables.product.product_name %} team with an identity provider group, an organization or enterprise owner must enable team synchronization for your organization or enterprise account. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" and "[Managing team synchronization for organizations in your enterprise account](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)." -Para evitar a remoção involuntária dos integrantes da equipe, visite o portal administrativo do seu IdP e confirme se cada integrante atual da equipe está também nos grupos de IdP aos quais você deseja conectar a esta equipe. Se você não tiver acesso ao provedor de identidade, entre em contato com o administrador do IdP. +To avoid unintentionally removing team members, visit the administrative portal for your IdP and confirm that each current team member is also in the IdP groups that you want to connect to this team. If you don't have this access to your identity provider, you can reach out to your IdP administrator. -Você deve efetuar a autenticação usando SAML SSO. Para obter mais informações, confira "[Autenticação com o logon único do SAML](/articles/authenticating-with-saml-single-sign-on)". +You must authenticate using SAML SSO. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)." -{% elsif ghae %} Para conectar uma equipe do {% data variables.product.product_name %} a um grupo de IdPs, primeiro, você precisa configurar o provisionamento de usuário para o {% data variables.product.product_location %} usando um SCIM (Sistema de Gerenciamento de Usuários entre Domínios) compatível. Para obter mais informações, confira "[Como configurar o provisionamento de usuário para sua empresa](/admin/authentication/configuring-user-provisioning-for-your-enterprise)". +{% elsif ghae %} +Before you can connect a {% data variables.product.product_name %} team with an IdP group, you must first configure user provisioning for {% data variables.location.product_location %} using a supported System for Cross-domain Identity Management (SCIM). For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." -Quando o provisionamento de {% data variables.product.product_name %} for configurado usando o SCIM, você poderá atribuir o aplicativo de {% data variables.product.product_name %} a cada grupo de IdP que você deseja usar em {% data variables.product.product_name %}. Para obter mais informações, confira [Configurar o provisionamento automático de usuário para o GitHub AE](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae) no Microsoft Docs.{% endif %} +Once user provisioning for {% data variables.product.product_name %} is configured using SCIM, you can assign the {% data variables.product.product_name %} application to every IdP group that you want to use on {% data variables.product.product_name %}. For more information, see [Configure automatic user provisioning to GitHub AE](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae) in the Microsoft Docs. +{% endif %} -## Conectar um grupo de IdP a uma equipe +## Connecting an IdP group to a team -Ao conectar um grupo de IdP a uma equipe de {% data variables.product.product_name %}, todos os usuários do grupo serão automaticamente adicionados à equipe. {% ifversion ghae %}Todos os usuários que não eram integrantes dos da organização principal também serão adicionados à organização.{% endif %} +When you connect an IdP group to a {% data variables.product.product_name %} team, all users in the group are automatically added to the team. {% ifversion ghae %}Any users who were not already members of the parent organization members are also added to the organization.{% endif %} -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %} {% ifversion ghec %} -6. Em "Grupos de provedores de identidade", use o menu suspenso e selecione até 5 grupos de provedores de identidade. - ![Menu suspenso usado para escolher grupos de provedores de identidade](/assets/images/help/teams/choose-an-idp-group.png){% elsif ghae %} -6. No "Grupo de Provedores de Identidade", use o menu suspenso e selecione um grupo de provedores de identidade na lista. - ![Menu suspenso usado para escolher um grupo de provedores de identidade](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %} -7. Clique em **Salvar alterações**. +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% ifversion ghec %} +6. Under "Identity Provider Groups", use the drop-down menu, and select up to 5 identity provider groups. + ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png){% elsif ghae %} +6. Under "Identity Provider Group", use the drop-down menu, and select an identity provider group from the list. + ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %} +7. Click **Save changes**. -## Desconectar um grupo de IdP de uma equipe +## Disconnecting an IdP group from a team -Se desconectar um grupo de IdP de uma equipe do {% data variables.product.prodname_dotcom %}, os integrantes da equipe atribuídos à equipe do {% data variables.product.prodname_dotcom %} por meio do grupo de IdP serão removidos da equipe. {% ifversion ghae %} Todos os usuários que eram integrantes da organização principal apenas por causa da conexão com a equipe também serão removidos da organização.{% endif %} +If you disconnect an IdP group from a {% data variables.product.prodname_dotcom %} team, team members that were assigned to the {% data variables.product.prodname_dotcom %} team through the IdP group will be removed from the team. {% ifversion ghae %} Any users who were members of the parent organization only because of that team connection are also removed from the organization.{% endif %} -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %} {% ifversion ghec %} -6. Em "Grupos de Provedores de Identidade", à direita do grupo de IdPs que deseja desconectar, clique em {% octicon "x" aria-label="X symbol" %}. - ![Cancelar a seleção de um grupo de IdPs conectado por meio da equipe do GitHub](/assets/images/help/teams/unselect-idp-group.png){% elsif ghae %} -6. Em "Grupo de Provedores de Identidade", à direita do grupo de IdP que você deseja desconectar, clique em {% octicon "x" aria-label="X symbol" %}. - ![Cancelar a seleção de um grupo de IdPs conectado por meio da equipe do GitHub](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %} -7. Clique em **Salvar alterações**. +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% ifversion ghec %} +6. Under "Identity Provider Groups", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. + ![Unselect a connected IdP group from the GitHub team](/assets/images/help/teams/unselect-idp-group.png){% elsif ghae %} +6. Under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. + ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %} +7. Click **Save changes**. diff --git a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md deleted file mode 100644 index a7aca41d2e..0000000000 --- a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: About OAuth App access restrictions -intro: 'Organizations can choose which {% data variables.product.prodname_oauth_apps %} have access to their repositories and other resources by enabling {% data variables.product.prodname_oauth_app %} access restrictions.' -redirect_from: - - /articles/about-third-party-application-restrictions - - /articles/about-oauth-app-access-restrictions - - /github/setting-up-and-managing-organizations-and-teams/about-oauth-app-access-restrictions -versions: - fpt: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: OAuth App access ---- - -## About OAuth App access restrictions - -{% data reusables.apps.oauth-app-access-restrictions %} - -{% ifversion limit-app-access-requests %} -{% data reusables.organizations.restricted-app-access-requests %}{% endif %} - -{% data reusables.organizations.oauth_app_restrictions_default %} - -{% tip %} - -**Tip**: When an organization has not set up {% data variables.product.prodname_oauth_app %} access restrictions, any {% data variables.product.prodname_oauth_app %} authorized by an organization member can also access the organization's private resources. - -{% endtip %} - -{% ifversion fpt %} -To further protect your organization's resources, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes security features like SAML single sign-on. {% data reusables.enterprise.link-to-ghec-trial %} -{% endif %} - -## Setting up {% data variables.product.prodname_oauth_app %} access restrictions - -When an organization owner sets up {% data variables.product.prodname_oauth_app %} access restrictions for the first time: - -- **Applications that are owned by the organization** are automatically given access to the organization's resources. -- **{% data variables.product.prodname_oauth_apps %}** immediately lose access to the organization's resources. -- **SSH keys created before February 2014** immediately lose access to the organization's resources (this includes user and deploy keys). -- **SSH keys created by {% data variables.product.prodname_oauth_apps %} during or after February 2014** immediately lose access to the organization's resources. -- **Hook deliveries from private organization repositories** will no longer be sent to unapproved {% data variables.product.prodname_oauth_apps %}. -- **API access** to private organization resources is not available for unapproved {% data variables.product.prodname_oauth_apps %}. In addition, there are no privileged create, update, or delete actions on public organization resources. -- **Hooks created by users and hooks created before May 2014** will not be affected. -- **Private forks of organization-owned repositories** are subject to the organization's access restrictions. - -## Resolving SSH access failures - -When an SSH key created before February 2014 loses access to an organization with {% data variables.product.prodname_oauth_app %} access restrictions enabled, subsequent SSH access attempts will fail. Users will encounter an error message directing them to a URL where they can approve the key or upload a trusted key in its place. - -## Webhooks - -When an {% data variables.product.prodname_oauth_app %} is granted access to the organization after restrictions are enabled, any pre-existing webhooks created by that {% data variables.product.prodname_oauth_app %} will resume dispatching. - -When an organization removes access from a previously-approved {% data variables.product.prodname_oauth_app %}, any pre-existing webhooks created by that application will no longer be dispatched (these hooks will be disabled, but not deleted). - -## Re-enabling access restrictions - -If an organization disables {% data variables.product.prodname_oauth_app %} access application restrictions, and later re-enables them, previously approved {% data variables.product.prodname_oauth_app %} are automatically granted access to the organization's resources. - -## Further reading - -- "[Enabling {% data variables.product.prodname_oauth_app %} access restrictions for your organization](/articles/enabling-oauth-app-access-restrictions-for-your-organization)" -- "[Approving {% data variables.product.prodname_oauth_apps %} for your organization](/articles/approving-oauth-apps-for-your-organization)" -- "[Reviewing your organization's installed integrations](/articles/reviewing-your-organization-s-installed-integrations)" -- "[Denying access to a previously approved {% data variables.product.prodname_oauth_app %} for your organization](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)" -- "[Disabling {% data variables.product.prodname_oauth_app %} access restrictions for your organization](/articles/disabling-oauth-app-access-restrictions-for-your-organization)" -- "[Requesting organization approval for {% data variables.product.prodname_oauth_apps %}](/articles/requesting-organization-approval-for-oauth-apps)" -- "[Authorizing {% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)" diff --git a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md deleted file mode 100644 index e50e56dd84..0000000000 --- a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Approving OAuth Apps for your organization -intro: 'When an organization member or outside collaborator requests {% data variables.product.prodname_oauth_app %} access to organization resources, organization owners can approve or deny the request.' -redirect_from: - - /articles/approving-third-party-applications-for-your-organization - - /articles/approving-oauth-apps-for-your-organization - - /github/setting-up-and-managing-organizations-and-teams/approving-oauth-apps-for-your-organization -versions: - fpt: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Approve OAuth Apps ---- -When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, organization members and outside collaborators must [request approval](/articles/requesting-organization-approval-for-oauth-apps) from an organization owner before they can authorize an {% data variables.product.prodname_oauth_app %} that has access to the organization's resources. - -{% ifversion limit-app-access-requests %} -{% data reusables.organizations.restricted-app-access-requests %}{% endif %} - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.oauth_app_access %} -5. Next to the application you'd like to approve, click **Review**. -![Review request link](/assets/images/help/settings/settings-third-party-approve-review.png) -6. After you review the information about the requested application, click **Grant access**. -![Grant access button](/assets/images/help/settings/settings-third-party-approve-grant.png) - -## Further reading - -- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)" diff --git a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md deleted file mode 100644 index 33201ddfbe..0000000000 --- a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Negar acesso a um aplicativo OAuth previamente aprovado para a organização -intro: 'Se uma organização não requer mais um {% data variables.product.prodname_oauth_app %} previamente autorizado, os proprietários podem remover o acesso do aplicativo aos recursos da organização.' -redirect_from: - - /articles/denying-access-to-a-previously-approved-application-for-your-organization - - /articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization - - /github/setting-up-and-managing-organizations-and-teams/denying-access-to-a-previously-approved-oauth-app-for-your-organization -versions: - fpt: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Deny OAuth App -ms.openlocfilehash: bcdbe48debe120d2f13f78a429d35c311343f26c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145128294' ---- -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.oauth_app_access %} -5. Ao lado do aplicativo que você deseja desabilitar, clique em {% octicon "pencil" aria-label="The edit icon" %}. - ![Ícone Editar](/assets/images/help/settings/settings-third-party-deny-edit.png) -6. Clique em **Negar acesso**. - ![Botão Deny confirmation (Negar confirmação)](/assets/images/help/settings/settings-third-party-deny-confirm.png) diff --git a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md deleted file mode 100644 index e272bbd300..0000000000 --- a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Desabilitar restrições de acesso do aplicativo OAuth da sua organização -intro: 'Os proprietários da organização podem desabilitar as restrições em {% data variables.product.prodname_oauth_apps %} que têm acesso aos recursos da organização.' -redirect_from: - - /articles/disabling-third-party-application-restrictions-for-your-organization - - /articles/disabling-oauth-app-access-restrictions-for-your-organization - - /github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization -versions: - fpt: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Disable OAuth App -ms.openlocfilehash: 41fae63d8d491eec7a6cd6a275958d5c96fb5f5c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145128293' ---- -{% danger %} - -**Aviso**: com a desabilitação das restrições de acesso do {% data variables.product.prodname_oauth_app %} da sua organização, qualquer integrante da organização autorizará automaticamente o acesso do {% data variables.product.prodname_oauth_app %} aos recursos privados da organização ao aprovar um aplicativo para ser usado nas configurações de conta pessoal dele. - -{% enddanger %} - -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.oauth_app_access %} -5. Clique em **Remover restrições** - ![Botão para remover restrições](/assets/images/help/settings/settings-third-party-remove-restrictions.png) -6. Depois de revisar as informações sobre desabilitação de restrições de aplicativos de terceiros, clique em **Yes, remove application restrictions** (Sim, remover restrições de aplicativos). - ![Botão para remover confirmação](/assets/images/help/settings/settings-third-party-confirm-disable.png) diff --git a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md deleted file mode 100644 index 23a176c5f1..0000000000 --- a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Habilitar restrições de acesso do aplicativo OAuth da sua organização -intro: 'Os proprietários da organização podem habilitar restrições de acesso do {% data variables.product.prodname_oauth_app %} para impedir que aplicativos não confiáveis acessem recursos da organização ao permitir que integrantes da organização usem {% data variables.product.prodname_oauth_apps %} para suas contas pessoais.' -redirect_from: - - /articles/enabling-third-party-application-restrictions-for-your-organization - - /articles/enabling-oauth-app-access-restrictions-for-your-organization - - /github/setting-up-and-managing-organizations-and-teams/enabling-oauth-app-access-restrictions-for-your-organization -versions: - fpt: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Enable OAuth App -ms.openlocfilehash: 7ae5885530f449c8ce9981067b0d0fe8b23af0d9 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145128291' ---- -{% data reusables.organizations.oauth_app_restrictions_default %} - -{% warning %} - -**Avisos**: -- A habilitação de restrições de acesso do {% data variables.product.prodname_oauth_app %} revogará o acesso da organização para todos os {% data variables.product.prodname_oauth_apps %} e chaves SSH previamente autorizados. Para obter mais informações, confira "[Sobre as restrições de acesso do {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)". -- Depois de configurar as restrições de acesso do {% data variables.product.prodname_oauth_app %}, lembre-se de tornar a autorizar qualquer {% data variables.product.prodname_oauth_app %} que requeira acesso aos dados privados da organização continuamente. Todos os integrantes da organização precisarão criar chaves SSH, e a organização precisará criar chaves de implantação conforme necessário. -- Quando as restrições de acesso do {% data variables.product.prodname_oauth_app %} estiverem habilitadas, os aplicativos poderão usar um token OAuth para acessar informações sobre transações do {% data variables.product.prodname_marketplace %}. - -{% endwarning %} - -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.oauth_app_access %} -5. Em "Política de acesso a aplicativos de terceiros", clique em **Configurar restrições de acesso a aplicativos**. - ![Botão Configurar restrições](/assets/images/help/settings/settings-third-party-set-up-restrictions.png) -6. Depois de revisar as informações sobre as restrições de acesso a terceiros, clique em **Restringir acesso a aplicativos de terceiros**. - ![Botão Confirmação de restrição](/assets/images/help/settings/settings-third-party-restrict-confirm.png) diff --git a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/index.md b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/index.md deleted file mode 100644 index 9119de71d8..0000000000 --- a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/index.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: Restringir o acesso aos dados da organização -intro: 'As restrições de acesso ao {% data variables.product.prodname_oauth_app %} permitem que os proprietários da organização restrinjam o acesso de um app não confiável aos dados da organização. Os membros da organização podem usar o {% data variables.product.prodname_oauth_apps %} para contas pessoais e ainda manter os dados da organização em segurança.' -redirect_from: - - /articles/restricting-access-to-your-organization-s-data - - /articles/restricting-access-to-your-organizations-data - - /github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data -versions: - fpt: '*' - ghec: '*' -topics: - - Organizations - - Teams -children: - - /about-oauth-app-access-restrictions - - /enabling-oauth-app-access-restrictions-for-your-organization - - /disabling-oauth-app-access-restrictions-for-your-organization - - /approving-oauth-apps-for-your-organization - - /denying-access-to-a-previously-approved-oauth-app-for-your-organization -shortTitle: Restrict access to organization data -ms.openlocfilehash: c4d45a93f4fb45adc65dc04151bd58b6ee823344 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145128290' ---- - diff --git a/translations/pt-BR/content/packages/learn-github-packages/about-permissions-for-github-packages.md b/translations/pt-BR/content/packages/learn-github-packages/about-permissions-for-github-packages.md index 68dd781bd9..8d4025e3d6 100644 --- a/translations/pt-BR/content/packages/learn-github-packages/about-permissions-for-github-packages.md +++ b/translations/pt-BR/content/packages/learn-github-packages/about-permissions-for-github-packages.md @@ -45,11 +45,13 @@ For more information, see "[Configuring a package's access control and visibilit ## About scopes and permissions for package registries -To use or manage a package hosted by a package registry, you must use a token with the appropriate scope, and your personal account must have appropriate permissions. +{% data reusables.package_registry.packages-classic-pat-only %} + +To use or manage a package hosted by a package registry, you must use a {% data variables.product.pat_v1 %} with the appropriate scope, and your personal account must have appropriate permissions. For example: -- To download and install packages from a repository, your token must have the `read:packages` scope, and your user account must have read permission. -- {% ifversion fpt or ghes or ghec %}To delete a package on {% data variables.product.product_name %}, your token must at least have the `delete:packages` and `read:packages` scope. The `repo` scope is also required for repo-scoped packages. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% elsif ghae %}To delete a specified version of a package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} +- To download and install packages from a repository, your {% data variables.product.pat_v1 %} must have the `read:packages` scope, and your user account must have read permission. +- {% ifversion fpt or ghes or ghec %}To delete a package on {% data variables.product.product_name %}, your {% data variables.product.pat_v1 %} must at least have the `delete:packages` and `read:packages` scope. The `repo` scope is also required for repo-scoped packages. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% elsif ghae %}To delete a specified version of a package on {% data variables.product.product_name %}, your {% data variables.product.pat_v1 %} must have the `delete:packages` and `repo` scope. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} | Scope | Description | Required permission | | --- | --- | --- | @@ -58,12 +60,12 @@ For example: | `delete:packages` | {% ifversion fpt or ghes or ghec %} Delete packages from {% data variables.product.prodname_registry %} {% elsif ghae %} Delete specified versions of packages from {% data variables.product.prodname_registry %} {% endif %} | admin | | `repo` | Upload and delete packages (along with `write:packages`, or `delete:packages`) | write or admin | -When you create a {% data variables.product.prodname_actions %} workflow, you can use the `GITHUB_TOKEN` to publish and install packages in {% data variables.product.prodname_registry %} without needing to store and manage a personal access token. +When you create a {% data variables.product.prodname_actions %} workflow, you can use the `GITHUB_TOKEN` to publish and install packages in {% data variables.product.prodname_registry %} without needing to store and manage a {% data variables.product.pat_generic %}. For more information, see:{% ifversion fpt or ghec %} - "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)"{% endif %} - "[Publishing and installing a package with {% data variables.product.prodname_actions %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)" -- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token/)" +- "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token/)" - "[Available scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)" ## Maintaining access to packages in {% data variables.product.prodname_actions %} workflows @@ -75,7 +77,7 @@ For more conceptual background on {% data variables.product.prodname_actions %} ### Access tokens - To publish packages associated with the workflow repository, use `GITHUB_TOKEN`. -- To install packages associated with other private repositories that `GITHUB_TOKEN` can't access, use a personal access token +- To install packages associated with other private repositories that `GITHUB_TOKEN` can't access, use a {% data variables.product.pat_v1 %} For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)." diff --git a/translations/pt-BR/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md b/translations/pt-BR/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md index 5e80976dd4..db786ab0a8 100644 --- a/translations/pt-BR/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md +++ b/translations/pt-BR/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md @@ -1,6 +1,6 @@ --- -title: Conectar um repositório a um pacote -intro: 'É possível conectar um repositório a uma imagem de contêiner na {% data variables.product.product_location %}.' +title: Connecting a repository to a package +intro: 'You can connect a repository to a container image on {% data variables.location.product_location %}.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image @@ -10,49 +10,46 @@ versions: ghec: '*' ghes: '*' shortTitle: Connect a repository -ms.openlocfilehash: 087775df9862c3b2a88dd555d9f571066fef8759 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147882332' --- -Ao conectar um repositório a um pacote, a página inicial do pacote mostrará informações e links do repositório, como o LEIAME. -## Conectar um repositório a um pacote de propriedade do usuário em {% data variables.product.prodname_dotcom %} +By connecting a repository to a package, the package landing page will show information and links from the repository, such as the README. + +## Connecting a repository to a user-owned package on {% data variables.product.prodname_dotcom %} {% data reusables.package_registry.package-settings-from-user-level %} {% data reusables.package_registry.repository_connection_steps %} -## Conectar um repositório a um pacote de propriedade da organização em {% data variables.product.prodname_dotcom %} +## Connecting a repository to an organization-owned package on {% data variables.product.prodname_dotcom %} {% data reusables.package_registry.package-settings-from-org-level %} {% data reusables.package_registry.repository_connection_steps %} {% ifversion fpt or ghec or ghes > 3.4 %} -## Conectar um repositório a uma imagem de contêiner usando a linha de comando +## Connecting a repository to a container image using the command line -{% ifversion ghes > 3.4 %} {% data reusables.package_registry.container-registry-ghes-beta %} {% endif %} +{% ifversion ghes > 3.4 %} +{% data reusables.package_registry.container-registry-ghes-beta %} +{% endif %} -1. Em seu Dockerfile, adicione esta linha, substituindo {% ifversion ghes %}`HOSTNAME`, {% endif %}`OWNER` and `REPO` pelos seus detalhes: +1. In your Dockerfile, add this line, replacing {% ifversion ghes %}`HOSTNAME`, {% endif %}`OWNER` and `REPO` with your details: ```shell - LABEL org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPO + LABEL org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPO ``` - Por exemplo, se você fosse o usuário `monalisa` e o proprietário do `my-repo` e o nome do host do {% data variables.product.product_location %} fosse `github.companyname.com`, você adicionaria essa linha ao Dockerfile: + For example, if you're the user `monalisa` and own `my-repo`, and {% data variables.location.product_location %} hostname is `github.companyname.com`, you would add this line to your Dockerfile: ```shell LABEL org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}{% data reusables.package_registry.container-registry-example-hostname %}{% endif %}/monalisa/my-repo ``` - Para obter mais informações, confira "[LABEL](https://docs.docker.com/engine/reference/builder/#label)" na documentação oficial do Docker e "[Chaves de Anotação Predefinidas](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" no repositório `opencontainers/image-spec`. + For more information, see "[LABEL](https://docs.docker.com/engine/reference/builder/#label)" in the official Docker documentation and "[Pre-defined Annotation Keys](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" in the `opencontainers/image-spec` repository. -2. Construa a sua imagem do contêiner. Este exemplo cria uma imagem do Dockerfile no diretório atual e atribui o nome `hello_docker` à imagem. +2. Build your container image. This example builds an image from the Dockerfile in the current directory and assigns the image name `hello_docker`. ```shell $ docker build -t hello_docker . ``` -3. Opcionalmente, revise os detalhes para a imagem do Docker que você deseja marcar. +3. Optionally, review details for the Docker image you want to tag. ```shell $ docker images > REPOSITORY TAG IMAGE ID CREATED SIZE @@ -61,27 +58,27 @@ Ao conectar um repositório a um pacote, a página inicial do pacote mostrará i > hello-world latest fce289e99eb9 16 months ago 1.84kB ``` -4. Marque sua imagem Docker com o nome de imagem desejado e hospedagem de destino. +4. Tag your Docker image with your desired image name and hosting destination. ```shell $ docker tag IMAGE_NAME {% data reusables.package_registry.container-registry-hostname %}/OWNER/NEW_IMAGE_NAME:TAG ``` - Por exemplo: + For example: ```shell $ docker tag 38f737a91f39 {% data reusables.package_registry.container-registry-example-hostname %}/monalisa/hello_docker:latest ``` -5. Se você ainda não o fez, efetue a autenticação em {% data variables.product.prodname_container_registry %}. Para obter mais informações, confira "[Autenticação no {% data variables.product.prodname_container_registry %}](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-the-container-registry)". +5. If you haven't already, authenticate to the {% data variables.product.prodname_container_registry %}. For more information, see "[Authenticating to the {% data variables.product.prodname_container_registry %}](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-the-container-registry)." {% raw %} ```shell $ echo $CR_PAT | docker login {% endraw %}{% data reusables.package_registry.container-registry-hostname %}{% raw %} -u USERNAME --password-stdin > Login Succeeded ``` {% endraw %} -6. Faça push da sua imagem de contêiner para o {% data variables.product.prodname_container_registry %}. +6. Push your container image to the {% data variables.product.prodname_container_registry %}. ```shell $ docker push {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE-NAME:TAG ``` - Por exemplo: + For example: ```shell $ docker push {% data reusables.package_registry.container-registry-example-hostname %}/monalisa/hello_docker:latest ``` diff --git a/translations/pt-BR/content/packages/learn-github-packages/deleting-and-restoring-a-package.md b/translations/pt-BR/content/packages/learn-github-packages/deleting-and-restoring-a-package.md index f3595a34ff..cb8b157547 100644 --- a/translations/pt-BR/content/packages/learn-github-packages/deleting-and-restoring-a-package.md +++ b/translations/pt-BR/content/packages/learn-github-packages/deleting-and-restoring-a-package.md @@ -40,6 +40,8 @@ On {% data variables.product.prodname_dotcom %}, you can also restore an entire {% ifversion fpt or ghec or ghes %} ## Packages API support +{% data reusables.package_registry.packages-classic-pat-only %} + {% ifversion fpt or ghec %} You can use the REST API to manage your packages. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)." @@ -92,7 +94,7 @@ For packages that inherit their permissions and access from repositories, you ca {% data reusables.package_registry.no-graphql-to-delete-packages %}{% ifversion fpt or ghec %} You can however use the REST API. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)."{% endif %} -Use the `deletePackageVersion` mutation in the GraphQL API. You must use a token with the `read:packages`, `delete:packages`, and `repo` scopes. For more information about tokens, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)." +Use the `deletePackageVersion` mutation in the GraphQL API. You must use a {% data variables.product.pat_v1 %} with the `read:packages`, `delete:packages`, and `repo` scopes. For more information about {% data variables.product.pat_v1_plural %}, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)." The following example demonstrates how to delete a package version, using a `packageVersionId` of `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`. @@ -104,7 +106,7 @@ curl -X POST \ HOSTNAME/graphql ``` -To find all of the private packages you have published to {% data variables.product.prodname_registry %}, along with the version IDs for the packages, you can use the `packages` connection through the `repository` object. You will need a token with the `read:packages` and `repo` scopes. For more information, see the [`packages`](/graphql/reference/objects#repository) connection or the [`PackageOwner`](/graphql/reference/interfaces#packageowner) interface. +To find all of the private packages you have published to {% data variables.product.prodname_registry %}, along with the version IDs for the packages, you can use the `packages` connection through the `repository` object. You will need a {% data variables.product.pat_v1 %} with the `read:packages` and `repo` scopes. For more information, see the [`packages`](/graphql/reference/objects#repository) connection or the [`PackageOwner`](/graphql/reference/interfaces#packageowner) interface. For more information about the `deletePackageVersion` mutation, see "[`deletePackageVersion`](/graphql/reference/mutations#deletepackageversion)." diff --git a/translations/pt-BR/content/packages/learn-github-packages/installing-a-package.md b/translations/pt-BR/content/packages/learn-github-packages/installing-a-package.md index bcefac2974..da7cd8260f 100644 --- a/translations/pt-BR/content/packages/learn-github-packages/installing-a-package.md +++ b/translations/pt-BR/content/packages/learn-github-packages/installing-a-package.md @@ -1,6 +1,6 @@ --- -title: Instalando um pacote -intro: 'Você pode instalar um pacote do {% data variables.product.prodname_registry %} e usá-lo como uma dependência no seu próprio projeto.' +title: Installing a package +intro: 'You can install a package from {% data variables.product.prodname_registry %} and use the package as a dependency in your own project.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /github/managing-packages-with-github-packages/installing-a-package @@ -12,26 +12,22 @@ versions: ghes: '*' ghae: '*' ghec: '*' -ms.openlocfilehash: 86c095ab1eddc969e4e04f3305059678ffcb9c20 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145128274' --- -{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} -## Sobre a instalação do pacote +{% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} -Você pode pesquisar em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} para encontrar pacotes em {% data variables.product.prodname_registry %} que você pode instalar no seu próprio projeto. Para obter mais informações, confira "[Pesquisar pacotes no {% data variables.product.prodname_registry %}](/search-github/searching-on-github/searching-for-packages)". +## About package installation -Depois de encontrar um pacote, você pode ler a descrição e as instruções de instalação e utilização na página de pacotes. +You can search on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} to find packages in {% data variables.product.prodname_registry %} that you can install in your own project. For more information, see "[Searching {% data variables.product.prodname_registry %} for packages](/search-github/searching-on-github/searching-for-packages)." -## Instalando um pacote +After you find a package, you can read the package's description and installation and usage instructions on the package page. -Você pode instalar um pacote do {% data variables.product.prodname_registry %} usando qualquer {% ifversion fpt or ghae or ghec %}cliente do pacote compatível{% else %}tipo de pacote habilitado para sua instância{% endif %}, seguindo as mesmas diretrizes gerais. +## Installing a package -1. Efetue a autenticação com {% data variables.product.prodname_registry %} usando as instruções para seu cliente de pacote. Para obter mais informações, confira "[Autenticação no GitHub Packages](/packages/learn-github-packages/introduction-to-github-packages#authenticating-to-github-packages)". -2. Instale o pacote usando as instruções para seu cliente de pacote. +You can install a package from {% data variables.product.prodname_registry %} using any {% ifversion fpt or ghae or ghec %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines. -Para obter instruções específicas do seu cliente de pacotes, confira "[Trabalhando com um registro do {% data variables.product.prodname_registry %}](/packages/working-with-a-github-packages-registry)". +1. Authenticate to {% data variables.product.prodname_registry %} using the instructions for your package client. For more information, see "[Authenticating to GitHub Packages](/packages/learn-github-packages/introduction-to-github-packages#authenticating-to-github-packages)." +2. Install the package using the instructions for your package client. + +For instructions specific to your package client, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)." diff --git a/translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md b/translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md index 530f6d7efe..4537c6fe1d 100644 --- a/translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md +++ b/translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md @@ -101,7 +101,7 @@ For more information about Docker and the {% data variables.product.prodname_con ## Managing packages {% ifversion fpt or ghec %} -You can delete a package in the {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} user interface or using the REST API. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" and the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)." +You can delete a package in the {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} user interface or using the REST API. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" and the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)." {% data reusables.package_registry.no-graphql-to-delete-packages %} {% endif %} @@ -114,7 +114,7 @@ You can delete a private or public package in the {% data variables.product.prod You can delete a version of a package in the {% data variables.product.product_name %} user interface or using the GraphQL API. {% endif %} -When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. +When you use the GraphQL API to query and delete private packages, you must use the same {% data variables.product.pat_v1 %} you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see {% ifversion ghes or ghae %}"[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" and {% endif %}"[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." diff --git a/translations/pt-BR/content/packages/learn-github-packages/publishing-a-package.md b/translations/pt-BR/content/packages/learn-github-packages/publishing-a-package.md index fd325f7dac..57496eecf2 100644 --- a/translations/pt-BR/content/packages/learn-github-packages/publishing-a-package.md +++ b/translations/pt-BR/content/packages/learn-github-packages/publishing-a-package.md @@ -1,6 +1,6 @@ --- -title: Publicando um pacote -intro: 'Você pode publicar um pacote no {% data variables.product.prodname_registry %} para disponibilizar o pacote para que outros façam download e reutilizem.' +title: Publishing a package +intro: 'You can publish a package to {% data variables.product.prodname_registry %} to make the package available for others to download and re-use.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /github/managing-packages-with-github-packages/publishing-a-package @@ -11,32 +11,31 @@ versions: ghes: '*' ghae: '*' ghec: '*' -ms.openlocfilehash: e13e33b6085fbdd736d77d7d8b4998595ea7ffcc -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145128272' --- -{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} -## Sobre os pacotes publicados +{% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} -Você pode ajudar as pessoas a entender e usar seu pacote fornecendo uma descrição e outros detalhes como, por exemplo, a instalação e instruções de uso na página do pacote. O {% data variables.product.product_name %} fornece metadados para cada versão, como a data de publicação, a atividade de download e as versões recentes. Para ver um exemplo de página de pacote, confira [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1). +## About published packages -{% data reusables.package_registry.public-or-private-packages %} Um repositório pode ser conectado a mais de um pacote. Para evitar confusão, certifique-se de que o README e a descrição fornecem informações claras sobre cada pacote. +You can help people understand and use your package by providing a description and other details like installation and usage instructions on the package page. {% data variables.product.product_name %} provides metadata for each version, such as the publication date, download activity, and recent versions. For an example package page, see [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1). -{% ifversion fpt or ghec %} Se uma nova versão de um pacote corrigir uma vulnerabilidade de segurança, você deverá publicar uma consultoria de segurança no seu repositório. {% data variables.product.prodname_dotcom %} revisa a cada consultoria de segurança publicado e pode usá-lo para enviar {% data variables.product.prodname_dependabot_alerts %} para repositórios afetados. Para obter mais informações, confira "[Sobre os Avisos de Segurança do GitHub](/github/managing-security-vulnerabilities/about-github-security-advisories)". +{% data reusables.package_registry.public-or-private-packages %} A repository can be connected to more than one package. To prevent confusion, make sure the README and description clearly provide information about each package. + +{% ifversion fpt or ghec %} +If a new version of a package fixes a security vulnerability, you should publish a security advisory in your repository. {% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. For more information, see "[About GitHub Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." {% endif %} -## Publicando um pacote +## Publishing a package -Você pode publicar um pacote em {% data variables.product.prodname_registry %} usando qualquer {% ifversion fpt or ghae or ghec %}cliente do pacote compatível{% else %}pacote habilitado para sua instância{% endif %}, seguindo as mesmas diretrizes gerais. +{% data reusables.package_registry.packages-classic-pat-only %} -1. Crie ou use um token de acesso existente com os escopos apropriados para a tarefa que você deseja realizar. Para obter mais informações, confira "[Sobre as permissões para o {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)". -2. Efetue a autenticação em {% data variables.product.prodname_registry %} usando seu token de acesso e as instruções para seu cliente do pacote. -3. Publique o pacote usando as instruções do seu cliente de pacote. +You can publish a package to {% data variables.product.prodname_registry %} using any {% ifversion fpt or ghae or ghec %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines. -Para obter instruções específicas ao cliente do pacote, confira"[Como trabalhar com um registro de pacotes GitHub](/packages/working-with-a-github-packages-registry)". +1. Create or use an existing {% data variables.product.pat_v1 %} with the appropriate scopes for the task you want to accomplish. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)." +2. Authenticate to {% data variables.product.prodname_registry %} using your {% data variables.product.pat_v1 %} and the instructions for your package client. +3. Publish the package using the instructions for your package client. -Após publicar um pacote, você poderá visualizá-lo no {% data variables.product.prodname_dotcom %}. Para obter mais informações, confira "[Como ver pacotes](/packages/learn-github-packages/viewing-packages)". +For instructions specific to your package client, see "[Working with a GitHub Packages registry](/packages/working-with-a-github-packages-registry)." + +After you publish a package, you can view the package on {% data variables.product.prodname_dotcom %}. For more information, see "[Viewing packages](/packages/learn-github-packages/viewing-packages)." diff --git a/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md index 34d324af49..a4dbfcc69a 100644 --- a/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md +++ b/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md @@ -32,7 +32,7 @@ You can extend the CI and CD capabilities of your repository by publishing or in ### Authenticating to package registries on {% data variables.product.prodname_dotcom %} -{% ifversion fpt or ghec %}If you want your workflow to authenticate to {% data variables.product.prodname_registry %} to access a package registry other than the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_location %}, then{% else %}To authenticate to package registries on {% data variables.product.product_name %},{% endif %} we recommend using the `GITHUB_TOKEN` that {% data variables.product.product_name %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %} instead of a personal access token for authentication. You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. For forks, the `GITHUB_TOKEN` is granted read access for the parent repository. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)." +{% ifversion fpt or ghec %}If you want your workflow to authenticate to {% data variables.product.prodname_registry %} to access a package registry other than the {% data variables.product.prodname_container_registry %} on {% data variables.location.product_location %}, then{% else %}To authenticate to package registries on {% data variables.product.product_name %},{% endif %} we recommend using the `GITHUB_TOKEN` that {% data variables.product.product_name %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %} instead of a {% data variables.product.pat_generic %} for authentication. You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. For forks, the `GITHUB_TOKEN` is granted read access for the parent repository. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)." You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %} context. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." @@ -53,7 +53,7 @@ When you enable GitHub Actions, GitHub installs a GitHub App on your repository. The {% data variables.packages.prodname_ghcr_and_npm_registry_full %} allows users to create and administer packages as free-standing resources at the organization level. Packages can be owned by an organization or personal account and you can customize access to each of your packages separately from repository permissions. -All workflows accessing the {% data variables.packages.prodname_ghcr_and_npm_registry %} should use the `GITHUB_TOKEN` instead of a personal access token. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)." +All workflows accessing the {% data variables.packages.prodname_ghcr_and_npm_registry %} should use the `GITHUB_TOKEN` instead of a {% data variables.product.pat_generic %}. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)." ## Default permissions and access settings for containers modified through workflows @@ -484,13 +484,13 @@ Installing packages hosted by {% data variables.product.prodname_registry %} thr {% data reusables.package_registry.actions-configuration %} {% ifversion fpt or ghec %} -## Upgrading a workflow that accesses a registry using a PAT +## Upgrading a workflow that accesses a registry using a {% data variables.product.pat_generic %} -The {% data variables.packages.prodname_ghcr_and_npm_registry %} support the `GITHUB_TOKEN` for easy and secure authentication in your workflows. If your workflow is using a personal access token (PAT) to authenticate to the registry, then we highly recommend you update your workflow to use the `GITHUB_TOKEN`. +The {% data variables.packages.prodname_ghcr_and_npm_registry %} support the `GITHUB_TOKEN` for easy and secure authentication in your workflows. If your workflow is using a {% data variables.product.pat_generic %} to authenticate to the registry, then we highly recommend you update your workflow to use the `GITHUB_TOKEN`. For more information about the `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)." -Using the `GITHUB_TOKEN` instead of a PAT, which includes the `repo` scope, increases the security of your repository as you don't need to use a long-lived PAT that offers unnecessary access to the repository where your workflow is run. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)." +Using the `GITHUB_TOKEN` instead of a {% data variables.product.pat_v1 %}, which includes the `repo` scope, increases the security of your repository as you don't need to use a long-lived {% data variables.product.pat_generic %} that offers unnecessary access to the repository where your workflow is run. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)." 1. Navigate to your package landing page. 1. In the left sidebar, click **Actions access**. @@ -504,7 +504,7 @@ Using the `GITHUB_TOKEN` instead of a PAT, which includes the `repo` scope, incr {% endnote %} 1. Optionally, using the "role" drop-down menu, select the default access level that you'd like the repository to have to your container image. ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png) -1. Open your workflow file. On the line where you log in to the registry, replace your PAT with {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}. +1. Open your workflow file. On the line where you log in to the registry, replace your {% data variables.product.pat_generic %} with {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}. For example, this workflow publishes a Docker image to the {% data variables.product.prodname_container_registry %} and uses {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} to authenticate. @@ -544,7 +544,7 @@ jobs: run: docker build . --file Dockerfile --tag $IMAGE_NAME --label "runnumber=${GITHUB_RUN_ID}" - name: Log in to registry - # This is where you will update the PAT to GITHUB_TOKEN + # This is where you will update the {% data variables.product.pat_generic %} to GITHUB_TOKEN run: echo "{% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}" | docker login ghcr.io -u ${{ github.actor }} --password-stdin - name: Push image diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md index b95e7771d1..400f954e6d 100644 --- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md +++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md @@ -1,6 +1,6 @@ --- -title: Fazendo a migração para o Registro do Contêiner a partir do Registro Docker -intro: '{% ifversion docker-ghcr-enterprise-migration %}Um proprietário de empresa pode{% else %}{% data variables.product.company_short %} will{% endif %} migrar imagens do Docker armazenadas anteriormente no Registro do Docker em {% data variables.product.product_location %} para {% data variables.product.prodname_container_registry %}.' +title: Migrating to the Container registry from the Docker registry +intro: '{% ifversion docker-ghcr-enterprise-migration %}An enterprise owner can{% else %}{% data variables.product.company_short %} will{% endif %} migrate Docker images previously stored in the Docker registry on {% data variables.location.product_location %} to the {% data variables.product.prodname_container_registry %}.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images @@ -9,47 +9,42 @@ redirect_from: versions: fpt: '*' ghec: '*' - feature: docker-ghcr-enterprise-migration + feature: 'docker-ghcr-enterprise-migration' shortTitle: Migration to Container registry topics: - Containers - Docker - Migration -ms.openlocfilehash: eb940881f59c9c935695c6fd7e3a62c9c3f387c9 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147409488' --- + {% data reusables.package_registry.container-registry-ghes-beta %} -## Sobre o {% data variables.product.prodname_container_registry %} +## About the {% data variables.product.prodname_container_registry %} -{% data reusables.package_registry.container-registry-benefits %} Para obter mais informações, confira "[Como trabalhar com {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)." +{% data reusables.package_registry.container-registry-benefits %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)." -## Sobre a migração do Registro do Docker +## About migration from the Docker registry -{% data reusables.package_registry.container-registry-replaces-docker-registry %} Se você armazenou imagens do Docker no Registro do Docker, {% ifversion docker-ghcr-enterprise-migration %}um proprietário de empresa{% else %}{% data variables.product.company_short %}{% endif %} migrará gradualmente as imagens para o {% data variables.product.prodname_container_registry %}. Nenhuma ação sua é necessária. +{% data reusables.package_registry.container-registry-replaces-docker-registry %} If you've stored Docker images in the Docker registry, {% ifversion docker-ghcr-enterprise-migration %}an enterprise owner{% else %}{% data variables.product.company_short %}{% endif %} will gradually migrate the images to the {% data variables.product.prodname_container_registry %}. No action is required on your part. {% ifversion docker-ghcr-enterprise-migration %} {% note %} -**Observação**: {% data reusables.package_registry.container-registry-ghes-migration-availability %} Para obter mais informações sobre como encontrar a versão de {% data variables.product.product_name %} usada, confira "[Sobre versões de {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)." +**Note**: {% data reusables.package_registry.container-registry-ghes-migration-availability %} For more information about finding the version of {% data variables.product.product_name %} that you use, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)." {% endnote %} {% endif %} -Depois que uma imagem do Docker tiver sido migrada para {% data variables.product.prodname_container_registry %}, você verá as seguintes alterações nos detalhes do pacote. +After a Docker image has been migrated to the {% data variables.product.prodname_container_registry %}, you'll see the following changes to the details for the package. -- O ícone será o logotipo {% data variables.product.prodname_container_registry %} em vez do logotipo do Docker. -- O domínio na URL de pull será {% data variables.product.prodname_container_registry_namespace %} em vez de dados {% data variables.product.prodname_docker_registry_namespace %}. +- The icon will be the {% data variables.product.prodname_container_registry %} logo instead of the Docker logo. +- The domain in the pull URL will be {% data variables.product.prodname_container_registry_namespace %} instead of {% data variables.product.prodname_docker_registry_namespace %}. {% ifversion fpt or ghec %} -![Captura de tela de uma imagem do Docker migrada para {% data variables.product.prodname_container_registry %}](/assets/images/help/package-registry/container-registry-details-page.png) +![Screenshot of a Docker image migrated to the {% data variables.product.prodname_container_registry %}](/assets/images/help/package-registry/container-registry-details-page.png) {% endif %} @@ -57,18 +52,18 @@ Depois que uma imagem do Docker tiver sido migrada para {% data variables.produc {% ifversion fpt or ghec %} -Após a migração, você não poderá mais usar a API do GraphQL para consultar pacotes com um `PackageType` de "DOCKER". Em vez disso, use a API REST para consultar pacotes com um `package_type` de "container". Para obter mais informações, confira "[Pacotes](/rest/reference/packages)" na documentação da API REST. +After migration, you'll no longer be able to use the GraphQL API to query for packages with a `PackageType` of "DOCKER". Instead, you can use the REST API to query for packages with a `package_type` of "container". For more information, see "[Packages](/rest/reference/packages)" in the REST API documentation. -## Sobre a cobrança do {% data variables.product.prodname_container_registry %} +## About billing for {% data variables.product.prodname_container_registry %} -Para obter mais informações sobre a cobrança do {% data variables.product.prodname_container_registry %}, confira "[Sobre a cobrança do {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)". +For more information about billing for the {% data variables.product.prodname_container_registry %}, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)." {% endif %} {% ifversion docker-ghcr-enterprise-migration %} -## Leitura adicional +## Further reading -- "[Como migrar sua empresa para {% data variables.product.prodname_container_registry %} do Registro do Docker](/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry)" +- "[Migrating your enterprise to the {% data variables.product.prodname_container_registry %} from the Docker registry](/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry)" {% endif %} diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md index 10ac056638..733136372b 100644 --- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md +++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md @@ -1,6 +1,6 @@ --- -title: Trabalhando com o registro do Apache Maven -intro: 'Você pode configurar o Apache Maven para publicar pacotes no {% data variables.product.prodname_registry %} e usar pacotes armazenados no {% data variables.product.prodname_registry %} como dependências em um projeto Java.' +title: Working with the Apache Maven registry +intro: 'You can configure Apache Maven to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /articles/configuring-apache-maven-for-use-with-github-package-registry @@ -14,38 +14,36 @@ versions: ghae: '*' ghec: '*' shortTitle: Apache Maven registry -ms.openlocfilehash: 0d2fafd69ac870a521fee8c7105b79bf8839d62c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147061703' --- -{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} + +{% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} {% data reusables.package_registry.admins-can-configure-package-types %} -## Autenticar-se no {% data variables.product.prodname_registry %} +## Authenticating to {% data variables.product.prodname_registry %} {% data reusables.package_registry.authenticate-packages %} {% data reusables.package_registry.authenticate-packages-github-token %} -### Efetuando a autenticação com um token de acesso pessoal +### Authenticating with a {% data variables.product.pat_generic %} {% data reusables.package_registry.required-scopes %} -Autentique-se no {% data variables.product.prodname_registry %} com o Apache Maven editando o arquivo *~/.m2/settings.xml* para incluir seu token de acesso pessoal. Crie um arquivo *~/.m2/settings.xml* se não houver. +You can authenticate to {% data variables.product.prodname_registry %} with Apache Maven by editing your *~/.m2/settings.xml* file to include your {% data variables.product.pat_v1 %}. Create a new *~/.m2/settings.xml* file if one doesn't exist. -Na tag `servers`, adicione uma tag filho `server` com uma `id`, substituindo *USERNAME* pelo nome de usuário do {% data variables.product.prodname_dotcom %} e *TOKEN* pelo seu token de acesso pessoal. +In the `servers` tag, add a child `server` tag with an `id`, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, and *TOKEN* with your {% data variables.product.pat_generic %}. -Na tag `repositories`, configure um repositório mapeando a `id` do repositório para a `id` adicionada à tag `server` que contém suas credenciais. Substitua {% ifversion ghes or ghae %}*HOSTNAME* pelo nome do host do {% data variables.product.product_location %} e{% endif %} *OWNER* pelo nome da conta de usuário ou de organização que é o proprietário do repositório. Como não é permitido usar letras maiúsculas, é preciso usar letras minúsculas no nome do proprietário do repositório, mesmo que o nome do usuário ou da organização no {% data variables.product.prodname_dotcom %} contenha letras maiúsculas. +In the `repositories` tag, configure a repository by mapping the `id` of the repository to the `id` you added in the `server` tag containing your credentials. Replace {% ifversion ghes or ghae %}*HOSTNAME* with the host name of {% data variables.location.product_location %}, and{% endif %} *OWNER* with the name of the user or organization account that owns the repository. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters. -Caso deseje interagir com vários repositórios, adicione cada repositório para separar os filhos do `repository` na tag `repositories`, mapeando a `id` de cada um para as credenciais contidas na marca `servers`. +If you want to interact with multiple repositories, you can add each repository to separate `repository` children in the `repositories` tag, mapping the `id` of each to the credentials in the `servers` tag. {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} -{% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio habilitado: {% endif %} +{% ifversion ghes %} +If your instance has subdomain isolation enabled: +{% endif %} ```xml ``` -{% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio desabilitado: +{% ifversion ghes %} +If your instance has subdomain isolation disabled: ```xml ` do arquivo *pom.xml*. O {% data variables.product.prodname_dotcom %} fará a correspondência do repositório com base nesse campo. Como o nome do repositório também faz parte do elemento `distributionManagement`, não há etapas adicionais para publicar vários pacotes no mesmo repositório. +If you would like to publish multiple packages to the same repository, you can include the URL of the repository in the `` element of the *pom.xml* file. {% data variables.product.prodname_dotcom %} will match the repository based on that field. Since the repository name is also part of the `distributionManagement` element, there are no additional steps to publish multiple packages to the same repository. -Para obter mais informações sobre como criar um pacote, confira a [documentação do maven.apache.org](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). +For more information on creating a package, see the [maven.apache.org documentation](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). -1. Edite o elemento `distributionManagement` do arquivo *pom.xml* localizado no diretório do pacote, substituindo {% ifversion ghes or ghae %}*HOSTNAME* pelo nome do host do {% data variables.product.product_location %}, {% endif %}`OWNER` pelo nome da conta de usuário ou de organização que é o proprietário do repositório e `REPOSITORY` pelo nome do repositório que contém o projeto.{% ifversion ghes %} +1. Edit the `distributionManagement` element of the *pom.xml* file located in your package directory, replacing {% ifversion ghes or ghae %}*HOSTNAME* with the host name of {% data variables.location.product_location %}, {% endif %}`OWNER` with the name of the user or organization account that owns the repository and `REPOSITORY` with the name of the repository containing your project.{% ifversion ghes %} - Se sua instância tiver o isolamento de subdomínio habilitado:{% endif %} + If your instance has subdomain isolation enabled:{% endif %} ```xml @@ -166,12 +165,12 @@ Para obter mais informações sobre como criar um pacote, confira a [documentaç {% data reusables.package_registry.viewing-packages %} -## Instalando um pacote +## Installing a package -Para instalar um pacote do Apache Maven por meio do {% data variables.product.prodname_registry %}, edite o arquivo *pom.xml* para incluir o pacote como uma dependência. Caso deseje instalar pacotes de mais de um repositório, adicione uma tag `repository` a cada um. Para obter mais informações sobre como usar um arquivo *pom.xml* no seu projeto, confira "[Introdução ao POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)" na documentação do Apache Maven. +To install an Apache Maven package from {% data variables.product.prodname_registry %}, edit the *pom.xml* file to include the package as a dependency. If you want to install packages from more than one repository, add a `repository` tag for each. For more information on using a *pom.xml* file in your project, see "[Introduction to the POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)" in the Apache Maven documentation. {% data reusables.package_registry.authenticate-step %} -2. Adicione as dependências do pacote ao elemento `dependencies` do arquivo *pom.xml* do projeto, substituindo `com.example:test` pelo pacote. +2. Add the package dependencies to the `dependencies` element of your project *pom.xml* file, replacing `com.example:test` with your package. ```xml @@ -183,13 +182,13 @@ Para instalar um pacote do Apache Maven por meio do {% data variables.product.pr ``` {% data reusables.package_registry.checksum-maven-plugin %} -3. Instale o pacote. +3. Install the package. ```shell $ mvn install ``` -## Leitura adicional +## Further reading -- "[Como trabalhar com o registro do Gradle](/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry)" -- "[Como excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package)" +- "[Working with the Gradle registry](/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry)" +- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md index edf9540d4a..6f00ec0d2e 100644 --- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md +++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md @@ -46,7 +46,7 @@ When installing or publishing a Docker image, the {% data variables.product.prod To authenticate to the {% data variables.product.prodname_container_registry %} (`ghcr.io`) within a {% data variables.product.prodname_actions %} workflow, use the `GITHUB_TOKEN` for the best security and experience. {% data reusables.package_registry.authenticate_with_pat_for_v2_registry %} {% endif %} -{% ifversion ghes %}Ensure that you replace `HOSTNAME` with {% data variables.product.product_location_enterprise %} hostname or IP address in the examples below.{% endif %} +{% ifversion ghes %}Ensure that you replace `HOSTNAME` with {% data variables.location.product_location_enterprise %} hostname or IP address in the examples below.{% endif %} {% data reusables.package_registry.authenticate-to-container-registry-steps %} diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md index d6b93afe20..b0fa5478a9 100644 --- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md +++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md @@ -1,6 +1,6 @@ --- -title: Trabalhando com o registro do Docker -intro: '{% ifversion fpt or ghec %}O registro do Docker foi substituído pelo {% data variables.product.prodname_container_registry %}.{% else %}Você pode fazer push e pull das imagens Docker usando o Docker de {% data variables.product.prodname_registry %}{% endif %}' +title: Working with the Docker registry +intro: '{% ifversion fpt or ghec %}The Docker registry has now been replaced by the {% data variables.product.prodname_container_registry %}.{% else %}You can push and pull your Docker images using the {% data variables.product.prodname_registry %} Docker registry.{% endif %}' product: '{% data reusables.gated-features.packages %}' redirect_from: - /articles/configuring-docker-for-use-with-github-package-registry @@ -15,143 +15,165 @@ versions: ghae: '*' ghec: '*' shortTitle: Docker registry -ms.openlocfilehash: f5d37e74f93535fd48f3400ef0b504825aadc657 -ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/12/2022 -ms.locfileid: '147888449' --- + {% ifversion fpt or ghec %} -O registro do Docker do {% data variables.product.prodname_dotcom %} (que usava o namespace `docker.pkg.github.com`) foi substituído pelo {% data variables.product.prodname_container_registry %} (que usa o namespace `https://ghcr.io`). O {% data variables.product.prodname_container_registry %} oferece benefícios como, por exemplo, permissões granulares e otimização de armazenamento para imagens Docker. +{% data variables.product.prodname_dotcom %}'s Docker registry (which used the namespace `docker.pkg.github.com`) has been replaced by the {% data variables.product.prodname_container_registry %} (which uses the namespace `https://ghcr.io`). The {% data variables.product.prodname_container_registry %} offers benefits such as granular permissions and storage optimization for Docker images. -As imagens do Docker armazenadas anteriormente no registro do Docker estão sendo automaticamente transferidas para {% data variables.product.prodname_container_registry %}. Para obter mais informações, confira "[Como migrar para o {% data variables.product.prodname_container_registry %} do registro do Docker](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)" e "[Como trabalhar com o {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)". +Docker images previously stored in the Docker registry are being automatically migrated into the {% data variables.product.prodname_container_registry %}. For more information, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)" and "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)." {% else %} -{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} +{% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} {% data reusables.package_registry.admins-can-configure-package-types %} -## Sobre o suporte ao Docker +## About Docker support -Ao instalar ou publicar uma imagem do Docker, o registro do Docker atualmente não é compatível com camadas externas como, por exemplo, as imagens do Windows. +When installing or publishing a Docker image, the Docker registry does not currently support foreign layers, such as Windows images. -## Autenticar-se no {% data variables.product.prodname_registry %} +## Authenticating to {% data variables.product.prodname_registry %} {% data reusables.package_registry.authenticate-packages %} {% data reusables.package_registry.authenticate-packages-github-token %} -### Efetuando a autenticação com um token de acesso pessoal +### Authenticating with a {% data variables.product.pat_generic %} {% data reusables.package_registry.required-scopes %} -Você pode se autenticar no {% data variables.product.prodname_registry %} usando o comando de logon `docker` do Docker. +You can authenticate to {% data variables.product.prodname_registry %} with Docker using the `docker` login command. -Para manter suas credenciais seguras, recomendamos que você salve seu token de acesso pessoal em um arquivo local no computador e use o sinalizador `--password-stdin` do Docker, que lê o token por meio de um arquivo local. +To keep your credentials secure, we recommend you save your {% data variables.product.pat_generic %} in a local file on your computer and use Docker's `--password-stdin` flag, which reads your token from a local file. -{% ifversion fpt or ghec %} {% raw %} +{% ifversion fpt or ghec %} +{% raw %} ```shell - $ cat ~/TOKEN.txt | docker login https://docker.pkg.github.com -u USERNAME --password-stdin + $ cat ~/TOKEN.txt | docker login https://docker.pkg.github.com -u USERNAME --password-stdin ``` -{% endraw %} {% endif %} +{% endraw %} +{% endif %} -{% ifversion ghes or ghae %} {% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio habilitado: {% endif %} {% raw %} +{% ifversion ghes or ghae %} +{% ifversion ghes %} +If your instance has subdomain isolation enabled: +{% endif %} +{% raw %} ```shell - $ cat ~/TOKEN.txt | docker login docker.HOSTNAME -u USERNAME --password-stdin + $ cat ~/TOKEN.txt | docker login docker.HOSTNAME -u USERNAME --password-stdin ``` -{% endraw %} {% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio desabilitado: +{% endraw %} +{% ifversion ghes %} +If your instance has subdomain isolation disabled: {% raw %} ```shell - $ cat ~/TOKEN.txt | docker login HOSTNAME -u USERNAME --password-stdin + $ cat ~/TOKEN.txt | docker login HOSTNAME -u USERNAME --password-stdin ``` -{% endraw %} {% endif %} +{% endraw %} +{% endif %} {% endif %} -Para usar este exemplo de comando de logon, substitua `USERNAME` pelo seu nome de usuário do {% data variables.product.product_name %} {% ifversion ghes or ghae %}, `HOSTNAME` pela URL do {% data variables.product.product_location %}{% endif %} e `~/TOKEN.txt` pelo caminho do arquivo para o token de acesso pessoal do {% data variables.product.product_name %}. +To use this example login command, replace `USERNAME` with your {% data variables.product.product_name %} username{% ifversion ghes or ghae %}, `HOSTNAME` with the URL for {% data variables.location.product_location %},{% endif %} and `~/TOKEN.txt` with the file path to your {% data variables.product.pat_generic %} for {% data variables.product.product_name %}. -Para obter mais informações, confira "[Logon do Docker](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)". +For more information, see "[Docker login](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)." -## Publicar uma imagem +## Publishing an image {% data reusables.package_registry.docker_registry_deprecation_status %} {% note %} -**Observação:** os nomes das imagens só devem usar letras minúsculas. +**Note:** Image names must only use lowercase letters. {% endnote %} -O {% data variables.product.prodname_registry %} aceita várias imagens do Docker de nível superior por repositório. Um repositório pode ter qualquer número de tags de imagem. Você poderá conhecer uma publicação de serviço degradada ou instalar imagens do Docker com tamanho superior a 10 GB. As camadas são limitadas em 5 GB cada. Para obter mais informações, confira "[Marca do Docker](https://docs.docker.com/engine/reference/commandline/tag/)" na documentação do Docker. +{% data variables.product.prodname_registry %} supports multiple top-level Docker images per repository. A repository can have any number of image tags. You may experience degraded service publishing or installing Docker images larger than 10GB, layers are capped at 5GB each. For more information, see "[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)" in the Docker documentation. {% data reusables.package_registry.viewing-packages %} -1. Determine o nome e a ID da imagem do Docker usando `docker images`. +1. Determine the image name and ID for your docker image using `docker images`. ```shell $ docker images > < > > REPOSITORY TAG IMAGE ID CREATED SIZE - > IMAGE_NAME VERSION IMAGE_ID 4 weeks ago 1.11MB + > IMAGE_NAME VERSION IMAGE_ID 4 weeks ago 1.11MB ``` -2. Ao usar a ID de imagem do Docker, marque a imagem do Docker substituindo *OWNER* pelo nome da conta de usuário ou de organização que é o proprietário do repositório, *REPOSITORY* pelo nome do repositório que contém o projeto, *IMAGE_NAME* pelo nome do pacote ou da imagem,{% ifversion ghes or ghae %} *HOSTNAME* pelo nome do host do {% data variables.product.product_location %}{% endif %} e *VERSION* pela versão do pacote no momento do build. +2. Using the Docker image ID, tag the docker image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% ifversion ghes or ghae %} *HOSTNAME* with the hostname of {% data variables.location.product_location %},{% endif %} and *VERSION* with package version at build time. {% ifversion fpt or ghec %} ```shell - $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` - {% else %} {% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio habilitado: {% endif %} + {% else %} + {% ifversion ghes %} + If your instance has subdomain isolation enabled: + {% endif %} ```shell - $ docker tag IMAGE_ID docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + $ docker tag IMAGE_ID docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` - {% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio desabilitado: + {% ifversion ghes %} + If your instance has subdomain isolation disabled: ```shell - $ docker tag IMAGE_ID HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + $ docker tag IMAGE_ID HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` - {% endif %} {% endif %} -3. Se você ainda não compilou uma imagem do Docker para o pacote, compile a imagem substituindo *OWNER* pelo nome da conta de usuário ou de organização que é o proprietário do repositório, *REPOSITORY* pelo nome do repositório que contém o projeto, *IMAGE_NAME* pelo nome do pacote ou da imagem, *VERSION* pela versão do pacote no momento do build,{% ifversion ghes or ghae %} *HOSTNAME* pelo nome do host do {% data variables.product.product_location %}{% endif %} e *PATH* pela imagem se não está no diretório de trabalho atual. + {% endif %} + {% endif %} +3. If you haven't already built a docker image for the package, build the image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, *VERSION* with package version at build time,{% ifversion ghes or ghae %} *HOSTNAME* with the hostname of {% data variables.location.product_location %},{% endif %} and *PATH* to the image if it isn't in the current working directory. {% ifversion fpt or ghec %} ```shell - $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` - {% else %} {% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio habilitado: {% endif %} + {% else %} + {% ifversion ghes %} + If your instance has subdomain isolation enabled: + {% endif %} ```shell - $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` - {% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio desabilitado: + {% ifversion ghes %} + If your instance has subdomain isolation disabled: ```shell - $ docker build -t HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + $ docker build -t HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` - {% endif %} {% endif %} -4. Publicar a imagem no {% data variables.product.prodname_registry %}. + {% endif %} + {% endif %} +4. Publish the image to {% data variables.product.prodname_registry %}. {% ifversion fpt or ghec %} ```shell - $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` - {% else %} {% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio habilitado: {% endif %} + {% else %} + {% ifversion ghes %} + If your instance has subdomain isolation enabled: + {% endif %} ```shell - $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` - {% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio desabilitado: + {% ifversion ghes %} + If your instance has subdomain isolation disabled: ```shell - $ docker push HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + $ docker push HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` - {% endif %} {% endif %} {% note %} + {% endif %} + {% endif %} + {% note %} - **Observação:** efetue push da imagem usando `IMAGE_NAME:VERSION` e não `IMAGE_NAME:SHA`. + **Note:** You must push your image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`. {% endnote %} -### Exemplo de publicação de uma imagem do Docker +### Example publishing a Docker image -{% ifversion ghes %} Esses exemplos pressupõem que a sua instância tenha o isolamento de subdomínio habilitado. +{% ifversion ghes %} +These examples assume your instance has subdomain isolation enabled. {% endif %} -Você pode publicar a versão 1.0 da imagem `monalisa` no repositório `octocat/octo-app` usando uma ID de imagem. +You can publish version 1.0 of the `monalisa` image to the `octocat/octo-app` repository using an image ID. {% ifversion fpt or ghec %} ```shell @@ -176,15 +198,15 @@ $ docker images > monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB # Tag the image with OWNER/REPO/IMAGE_NAME -$ docker tag c75bebcdd211 docker.HOSTNAME/octocat/octo-app/monalisa:1.0 +$ docker tag c75bebcdd211 docker.HOSTNAME/octocat/octo-app/monalisa:1.0 # Push the image to {% data variables.product.prodname_registry %} -$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 +$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 ``` {% endif %} -Você pode publicar uma nova imagem do Docker pela primeira vez e dar a ela o nome `monalisa`. +You can publish a new Docker image for the first time and name it `monalisa`. {% ifversion fpt or ghec %} ```shell @@ -200,43 +222,47 @@ $ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 ```shell # Build the image with docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION # Assumes Dockerfile resides in the current working directory (.) -$ docker build -t docker.HOSTNAME/octocat/octo-app/monalisa:1.0 . +$ docker build -t docker.HOSTNAME/octocat/octo-app/monalisa:1.0 . # Push the image to {% data variables.product.prodname_registry %} -$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 +$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 ``` {% endif %} -## Baixando uma imagem +## Downloading an image {% data reusables.package_registry.docker_registry_deprecation_status %} -Use o comando `docker pull` para instalar uma imagem do Docker por meio do {% data variables.product.prodname_registry %}, substituindo *OWNER* pelo nome da conta de usuário ou de organização que é o proprietário do repositório, *REPOSITORY* pelo nome do repositório que contém o projeto, *IMAGE_NAME* pelo nome do pacote ou da imagem, {% ifversion ghes or ghae %} *HOSTNAME* pelo nome do host do {% data variables.product.product_location %} {% endif %} e *TAG_NAME* pela marca da imagem que deseja instalar. +You can use the `docker pull` command to install a docker image from {% data variables.product.prodname_registry %}, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% ifversion ghes or ghae %} *HOSTNAME* with the host name of {% data variables.location.product_location %}, {% endif %} and *TAG_NAME* with tag for the image you want to install. {% ifversion fpt or ghec %} ```shell -$ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +$ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME ``` {% else %} -{% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio habilitado: {% endif %} +{% ifversion ghes %} +If your instance has subdomain isolation enabled: +{% endif %} ```shell -$ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +$ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME ``` -{% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio desabilitado: +{% ifversion ghes %} +If your instance has subdomain isolation disabled: ```shell -$ docker pull HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +$ docker pull HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME ``` -{% endif %} {% endif %} +{% endif %} +{% endif %} {% note %} -**Observação:** efetue pull da imagem usando `IMAGE_NAME:VERSION` e não `IMAGE_NAME:SHA`. +**Note:** You must pull the image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`. {% endnote %} -## Leitura adicional +## Further reading -- "[Como excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package)" +- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" {% endif %} diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md index 61c6b34033..e903fc567f 100644 --- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md +++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md @@ -1,6 +1,6 @@ --- -title: Trabalhando com o registro do Gradle -intro: 'Você pode configurar o Gradle para publicar pacotes no registro do Gradle de {% data variables.product.prodname_registry %} e usar pacotes armazenados em {% data variables.product.prodname_registry %} como dependências de um projeto Java.' +title: Working with the Gradle registry +intro: 'You can configure Gradle to publish packages to the {% data variables.product.prodname_registry %} Gradle registry and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /articles/configuring-gradle-for-use-with-github-package-registry @@ -14,42 +14,40 @@ versions: ghae: '*' ghec: '*' shortTitle: Gradle registry -ms.openlocfilehash: 65475c04ea3c6934bdf126500f16c3a907b7efd6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147061656' --- -{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} + +{% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} {% data reusables.package_registry.admins-can-configure-package-types %} -## Autenticar-se no {% data variables.product.prodname_registry %} +## Authenticating to {% data variables.product.prodname_registry %} {% data reusables.package_registry.authenticate-packages %} -{% data reusables.package_registry.authenticate-packages-github-token %} Para obter mais informações sobre como usar o `GITHUB_TOKEN` com o Gradle, confira "[Como publicar pacotes Java com o Gradle](/actions/guides/publishing-java-packages-with-gradle#publishing-packages-to-github-packages)". +{% data reusables.package_registry.authenticate-packages-github-token %} For more information about using `GITHUB_TOKEN` with Gradle, see "[Publishing Java packages with Gradle](/actions/guides/publishing-java-packages-with-gradle#publishing-packages-to-github-packages)." -### Efetuando a autenticação com um token de acesso pessoal +### Authenticating with a {% data variables.product.pat_generic %} {% data reusables.package_registry.required-scopes %} -Autentique-se no {% data variables.product.prodname_registry %} com o Gradle usando o Gradle Groovy ou o Kotlin DSL editando o arquivo *build.gradle* (Gradle Groovy) ou o arquivo *build.gradle.kts* (Kotlin DSL) para incluir seu token de acesso pessoal. Também é possível configurar o Gradle Groovy e o Kotlin DSL para reconhecer um único pacote ou vários pacotes em um repositório. +You can authenticate to {% data variables.product.prodname_registry %} with Gradle using either Gradle Groovy or Kotlin DSL by editing your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file to include your {% data variables.product.pat_v1 %}. You can also configure Gradle Groovy and Kotlin DSL to recognize a single package or multiple packages in a repository. -{% ifversion ghes %} Substitua *REGISTRY-URL* pela URL do registro do Maven da sua instância. Se a sua instância tem o isolamento de subdomínio habilitado, use `maven.HOSTNAME`. Se a sua instância tem o isolamento de subdomínio desabilitado, use `HOSTNAME/_registry/maven`. Nos dois casos, substitua *HOSTNAME* pelo nome do host da instância do {% data variables.product.prodname_ghe_server %}. -{% elsif ghae %} Substitua *REGISTRY-URL* pela URL do registro do Maven da sua empresa, `maven.HOSTNAME`. Substitua *HOSTNAME* pelo nome do host do {% data variables.product.product_location %}. +{% ifversion ghes %} +Replace *REGISTRY-URL* with the URL for your instance's Maven registry. If your instance has subdomain isolation enabled, use `maven.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/maven`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance. +{% elsif ghae %} +Replace *REGISTRY-URL* with the URL for your enterprise's Maven registry, `maven.HOSTNAME`. Replace *HOSTNAME* with the host name of {% data variables.location.product_location %}. {% endif %} -Substitua *USERNAME* pelo seu nome de usuário do {% data variables.product.prodname_dotcom %}, *TOKEN* pelo token de acesso pessoal, *REPOSITORY* pelo nome do repositório que contém o pacote que você deseja publicar e *OWNER* pelo nome da conta de usuário ou de organização no {% data variables.product.prodname_dotcom %} que é o proprietário do repositório. Como não é permitido usar letras maiúsculas, é preciso usar letras minúsculas no nome do proprietário do repositório, mesmo que o nome do usuário ou da organização no {% data variables.product.prodname_dotcom %} contenha letras maiúsculas. +Replace *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your {% data variables.product.pat_v1 %}, *REPOSITORY* with the name of the repository containing the package you want to publish, and *OWNER* with the name of the user or organization account on {% data variables.product.prodname_dotcom %} that owns the repository. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters. {% note %} -**Observação:** {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} Para ver um exemplo, confira "[Como configurar o Apache Maven para uso com o {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)". +**Note:** {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} For an example, see "[Configuring Apache Maven for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)." {% endnote %} -#### Exemplo de uso do Gradle Groovy para um único pacote em um repositório +#### Example using Gradle Groovy for a single package in a repository ```shell plugins { @@ -59,10 +57,10 @@ publishing { repositories { maven { name = "GitHubPackages" - url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") credentials { - username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") + username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") } } } @@ -74,7 +72,7 @@ publishing { } ``` -#### Exemplo de uso do Gradle Groovy para vários pacotes no mesmo repositório +#### Example using Gradle Groovy for multiple packages in the same repository ```shell plugins { @@ -86,10 +84,10 @@ subprojects { repositories { maven { name = "GitHubPackages" - url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") credentials { - username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") + username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") } } } @@ -102,7 +100,7 @@ subprojects { } ``` -#### Exemplo de uso do Kotlin DSL para um único pacote no mesmo repositório +#### Example using Kotlin DSL for a single package in the same repository ```shell plugins { @@ -112,10 +110,10 @@ publishing { repositories { maven { name = "GitHubPackages" - url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") credentials { - username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") + username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") } } } @@ -127,7 +125,7 @@ publishing { } ``` -#### Exemplo de uso do Kotlin DSL para vários pacotes no mesmo repositório +#### Example using Kotlin DSL for multiple packages in the same repository ```shell plugins { @@ -139,10 +137,10 @@ subprojects { repositories { maven { name = "GitHubPackages" - url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") credentials { - username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") + username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") } } } @@ -155,67 +153,67 @@ subprojects { } ``` -## Publicando um pacote +## Publishing a package -{% data reusables.package_registry.default-name %} Por exemplo, o {% data variables.product.prodname_dotcom %} publicará um pacote chamado `com.example.test` no repositório `OWNER/test` do {% data variables.product.prodname_registry %}. +{% data reusables.package_registry.default-name %} For example, {% data variables.product.prodname_dotcom %} will publish a package named `com.example.test` in the `OWNER/test` {% data variables.product.prodname_registry %} repository. {% data reusables.package_registry.viewing-packages %} {% data reusables.package_registry.authenticate-step %} -2. Depois de criar seu pacote, você poderá publicá-lo. +2. After creating your package, you can publish the package. ```shell $ gradle publish ``` -## Usando um pacote publicado +## Using a published package -Para usar um pacote publicado a partir de {% data variables.product.prodname_registry %}, adicione o pacote como uma dependência e adicione o repositório ao seu projeto. Para obter mais informações, confira "[Como declarar dependências](https://docs.gradle.org/current/userguide/declaring_dependencies.html)" na documentação do Gradle. +To use a published package from {% data variables.product.prodname_registry %}, add the package as a dependency and add the repository to your project. For more information, see "[Declaring dependencies](https://docs.gradle.org/current/userguide/declaring_dependencies.html)" in the Gradle documentation. {% data reusables.package_registry.authenticate-step %} -2. Adicione as dependências do pacote ao arquivo *build.gradle* (Gradle Groovy) ou ao arquivo *build.gradle.kts* (Kotlin DSL). +2. Add the package dependencies to your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file. - Exemplo do uso do Gradle Groovy: + Example using Gradle Groovy: ```shell dependencies { implementation 'com.example:package' } ``` - Exemplo de uso do Kotlin DSL: + Example using Kotlin DSL: ```shell dependencies { implementation("com.example:package") } ``` -3. Adicione o repositório ao arquivo *build.gradle* (Gradle Groovy) ou ao arquivo *build.gradle.kts* (Kotlin DSL). +3. Add the repository to your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file. - Exemplo do uso do Gradle Groovy: + Example using Gradle Groovy: ```shell repositories { maven { - url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") credentials { - username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") + username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") } } } ``` - Exemplo de uso do Kotlin DSL: + Example using Kotlin DSL: ```shell repositories { maven { - url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") credentials { - username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") + username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") } } } ``` -## Leitura adicional +## Further reading -- "[Como trabalhar com o registro do Apache Maven](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry)" -- "[Como excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package)" +- "[Working with the Apache Maven registry](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry)" +- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md index b441630065..f17d1a1b94 100644 --- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md +++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md @@ -1,6 +1,6 @@ --- -title: Trabalhando com o registro npm -intro: 'Você pode configurar o npm para publicar pacotes no {% data variables.product.prodname_registry %} e usar pacotes armazenados no {% data variables.product.prodname_registry %} como dependências em um projeto npm.' +title: Working with the npm registry +intro: 'You can configure npm to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in an npm project.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /articles/configuring-npm-for-use-with-github-package-registry @@ -14,158 +14,176 @@ versions: ghae: '*' ghec: '*' shortTitle: npm registry -ms.openlocfilehash: adcaf9cadc6202075e4f89e2287cdf2b733efc3f -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147705016' --- -{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} + +{% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} {% data reusables.package_registry.admins-can-configure-package-types %} -{% ifversion packages-npm-v2 %} {% else %} -## Limites para versões publicadas do npm +{% ifversion packages-npm-v2 %} +{% else %} +## Limits for published npm versions -Se você publicar mais de 1.000 versões de pacote de npm até {% data variables.product.prodname_registry %}, você poderá ver problemas de performance e tempo-limite que ocorrem durante o uso. +If you publish over 1,000 npm package versions to {% data variables.product.prodname_registry %}, you may see performance issues and timeouts occur during usage. -No futuro, para melhorar o desempenho do serviço, você não será capaz de publicar mais de 1.000 versões de um pacote em {% data variables.product.prodname_dotcom %}. Todas as versões publicadas antes de atingir esse limite serão legíveis. +In the future, to improve performance of the service, you won't be able to publish more than 1,000 versions of a package on {% data variables.product.prodname_dotcom %}. Any versions published before hitting this limit will still be readable. -Se você atingir este limite, considere excluir versões de pacote ou entre em contato com o suporte para obter ajuda. Quando este limite for aplicado, a nossa documentação será atualizada com uma forma de contornar este limite. Para obter mais informações, confira "[Como excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package)" ou "[Como entrar em contato com o suporte](/packages/learn-github-packages/about-github-packages#contacting-support)". +If you reach this limit, consider deleting package versions or contact Support for help. When this limit is enforced, our documentation will be updated with a way to work around this limit. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" or "[Contacting Support](/packages/learn-github-packages/about-github-packages#contacting-support)." {% endif %} -## Autenticar-se no {% data variables.product.prodname_registry %} +## Authenticating to {% data variables.product.prodname_registry %} {% data reusables.package_registry.authenticate-packages %} -{% ifversion packages-npm-v2 %} {% data reusables.package_registry.authenticate_with_pat_for_v2_registry %} +{% ifversion packages-npm-v2 %} +{% data reusables.package_registry.authenticate_with_pat_for_v2_registry %} -Você também pode optar por dar permissões de acesso a pacotes independentemente para {% data variables.product.prodname_codespaces %} e {% data variables.product.prodname_actions %}. Para obter mais informações, confira "[Como garantir que os codespaces acessem seu pacote](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-codespaces-access-to-your-package) e [Como garantir o acesso do fluxo de trabalho ao seu pacote](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)". +You can also choose to give access permissions to packages independently for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_actions %}. For more information, see "[Ensuring Codespaces access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-codespaces-access-to-your-package) and [Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)." {% endif %} -### Efetuando a autenticação com um token de acesso pessoal +### Authenticating with a {% data variables.product.pat_generic %} {% data reusables.package_registry.required-scopes %} -Você pode se autenticar no {% data variables.product.prodname_registry %} com o npm editando o arquivo *~/.npmrc* por usuário para incluir seu token de acesso pessoal ou fazendo logon no npm na linha de comando com seu nome de usuário e o token de acesso pessoal. +You can authenticate to {% data variables.product.prodname_registry %} with npm by either editing your per-user *~/.npmrc* file to include your {% data variables.product.pat_v1 %} or by logging in to npm on the command line using your username and {% data variables.product.pat_generic %}. -Para se autenticar adicionando seu token de acesso pessoal ao arquivo *~/.npmrc*, edite o arquivo *~/.npmrc* para que o projeto inclua a linha a seguir, substituindo {% ifversion ghes or ghae %} *HOSTNAME* pelo nome do host da {% data variables.product.product_location %} e {% endif %}*TOKEN* pelo token de acesso pessoal. Crie um arquivo *~/.npmrc* se ele não existir. +To authenticate by adding your {% data variables.product.pat_v1 %} to your *~/.npmrc* file, edit the *~/.npmrc* file for your project to include the following line, replacing {% ifversion ghes or ghae %}*HOSTNAME* with the host name of {% data variables.location.product_location %} and {% endif %}*TOKEN* with your {% data variables.product.pat_generic %}. Create a new *~/.npmrc* file if one doesn't exist. -{% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio habilitado: {% endif %} +{% ifversion ghes %} +If your instance has subdomain isolation enabled: +{% endif %} ```shell -//{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}/:_authToken=TOKEN +//{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}/:_authToken=TOKEN ``` -{% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio desabilitado: +{% ifversion ghes %} +If your instance has subdomain isolation disabled: ```shell -//HOSTNAME/_registry/npm/:_authToken=TOKEN +//HOSTNAME/_registry/npm/:_authToken=TOKEN ``` {% endif %} -Para se autenticar fazendo logon no npm, use o comando `npm login` substituindo *USERNAME* pelo seu nome de usuário do {% data variables.product.prodname_dotcom %}, *TOKEN* pelo token de acesso pessoal e *PUBLIC-EMAIL-ADDRESS* pelo seu endereço de email. +To authenticate by logging in to npm, use the `npm login` command, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your {% data variables.product.pat_v1 %}, and *PUBLIC-EMAIL-ADDRESS* with your email address. -Se o {% data variables.product.prodname_registry %} não é o registro de pacote padrão para usar o npm e você deseja usar o comando `npm audit`, recomendamos que você use o sinalizador `--scope` com o proprietário do pacote quando se autenticar no {% data variables.product.prodname_registry %}. +If {% data variables.product.prodname_registry %} is not your default package registry for using npm and you want to use the `npm audit` command, we recommend you use the `--scope` flag with the owner of the package when you authenticate to {% data variables.product.prodname_registry %}. -{% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio habilitado: {% endif %} +{% ifversion ghes %} +If your instance has subdomain isolation enabled: +{% endif %} ```shell -$ npm login --scope=@OWNER --registry=https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} +$ npm login --scope=@OWNER --registry=https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %} -> Username: USERNAME -> Password: TOKEN -> Email: PUBLIC-EMAIL-ADDRESS +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS ``` -{% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio desabilitado: +{% ifversion ghes %} +If your instance has subdomain isolation disabled: ```shell -$ npm login --scope=@OWNER --registry=https://HOSTNAME/_registry/npm/ -> Username: USERNAME -> Password: TOKEN -> Email: PUBLIC-EMAIL-ADDRESS +$ npm login --scope=@OWNER --registry=https://HOSTNAME/_registry/npm/ +> Username: USERNAME +> Password: TOKEN +> Email: PUBLIC-EMAIL-ADDRESS ``` {% endif %} -## Publicando um pacote +## Publishing a package {% note %} -**Observação:** os nomes e os escopos dos pacotes só devem usar letras minúsculas. +**Note:** Package names and scopes must only use lowercase letters. {% endnote %} -{% ifversion packages-npm-v2 %} O registro {% data variables.product.prodname_registry %} armazena pacotes npm em sua organização ou conta pessoal e permite que você associe um pacote a um repositório. Você pode escolher se deve herdar permissões de um repositório ou definir permissões granulares, independentemente de um repositório. +{% ifversion packages-npm-v2 %} +The {% data variables.product.prodname_registry %} registry stores npm packages within your organization or personal account, and allows you to associate a package with a repository. You can choose whether to inherit permissions from a repository, or set granular permissions independently of a repository. {% endif %} -Por padrão, o {% data variables.product.prodname_registry %} publica um pacote no repositório do {% data variables.product.prodname_dotcom %} que você especificar no campo de nome do arquivo *package.json*. Por exemplo, você publicará um pacote chamado `@my-org/test` no repositório `my-org/test` do {% data variables.product.prodname_dotcom %}. Se você estiver executando o [npm v8.5.3](https://github.com/npm/cli/releases/tag/v8.5.3) ou posterior, poderá adicionar um resumo para a página de listagem de pacotes incluindo um arquivo *README.md* em seu diretório de pacotes. Para obter mais informações, confira "[Como trabalhar com package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" e "[Como criar módulos do Node.js](https://docs.npmjs.com/getting-started/creating-node-modules)" na documentação do npm. +By default, {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the name field of the *package.json* file. For example, you would publish a package named `@my-org/test` to the `my-org/test` {% data variables.product.prodname_dotcom %} repository. If you're running [npm v8.5.3](https://github.com/npm/cli/releases/tag/v8.5.3) or later, you can add a summary for the package listing page by including a *README.md* file in your package directory. For more information, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" and "[How to create Node.js Modules](https://docs.npmjs.com/getting-started/creating-node-modules)" in the npm documentation. -Você pode publicar vários pacotes no mesmo repositório do {% data variables.product.prodname_dotcom %} incluindo um campo `URL` no arquivo *package.json*. Para obter mais informações, confira "[Como publicar vários pacotes no mesmo repositório](#publishing-multiple-packages-to-the-same-repository)". +You can publish multiple packages to the same {% data variables.product.prodname_dotcom %} repository by including a `URL` field in the *package.json* file. For more information, see "[Publishing multiple packages to the same repository](#publishing-multiple-packages-to-the-same-repository)." -{% ifversion fpt or ghec %} Quando um pacote é publicado, ele não é vinculado automaticamente a um repositório. No entanto, você pode optar por vincular seu pacote publicado a um repositório usando a interface do usuário ou a linha de comando. Para obter mais informações, confira "[Como conectar um repositório a um pacote](/packages/learn-github-packages/connecting-a-repository-to-a-package)". +{% ifversion fpt or ghec %} +When a package is published, it isn't automatically linked to a repository. You can however choose to link your published package to a repository using the user interface or command line. For more information, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)." {% endif %} -Configure o mapeamento do escopo para seu projeto usando um arquivo *.npmrc* local no projeto ou usando a opção `publishConfig` em *package.json*. {% data variables.product.prodname_registry %} só é compatível com pacotes npm com escopo definido. Os pacotes com escopo têm nomes com o formato de `@owner/name`. Os pacotes com escopo sempre começam com um símbolo `@`. Talvez seja necessário atualizar o nome no *package.json* para usar o nome com escopo. Por exemplo, `"name": "@codertocat/hello-world-npm"`. +You can set up the scope mapping for your project using either a local *.npmrc* file in the project or using the `publishConfig` option in the *package.json*. {% data variables.product.prodname_registry %} only supports scoped npm packages. Scoped packages have names with the format of `@owner/name`. Scoped packages always begin with an `@` symbol. You may need to update the name in your *package.json* to use the scoped name. For example, `"name": "@codertocat/hello-world-npm"`. -{% ifversion packages-npm-v2 %} Ao publicar um pacote pela primeira vez a visibilidade-padrão será privada. Quando um pacote é vinculado ao repositório, a visibilidade do pacote depende da visibilidade do repositório. Para alterar a visibilidade ou definir permissões de acesso, confira "[Como configurar o controle de acesso e a visibilidade de um pacote](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)". +{% ifversion packages-npm-v2 %} +When you first publish a package, the default visibility is private. When a package is linked to repository, the package visibility is dependent on the repository's visibility. To change the visibility or set access permissions, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)." {% endif %} {% data reusables.package_registry.viewing-packages %} -### Como publicar um pacote usando um arquivo *.npmrc* local +### Publishing a package using a local *.npmrc* file -Use um arquivo *.npmrc* para configurar o mapeamento do escopo para seu projeto. No arquivo *.npmrc*, use a URL e o proprietário da conta do {% data variables.product.prodname_registry %} para que o {% data variables.product.prodname_registry %} saiba o local para o qual as solicitações de pacote devem ser roteadas. O uso de um arquivo *.npmrc* impede que outros desenvolvedores publiquem o pacote acidentalmente em npmjs.org em vez de no {% data variables.product.prodname_registry %}. +You can use an *.npmrc* file to configure the scope mapping for your project. In the *.npmrc* file, use the {% data variables.product.prodname_registry %} URL and account owner so {% data variables.product.prodname_registry %} knows where to route package requests. Using an *.npmrc* file prevents other developers from accidentally publishing the package to npmjs.org instead of {% data variables.product.prodname_registry %}. -{% data reusables.package_registry.authenticate-step %} {% data reusables.package_registry.create-npmrc-owner-step %} {% data reusables.package_registry.add-npmrc-to-repo-step %} -1. Verifique o nome do pacote no *package.json* do projeto. O campo `name` precisa conter o escopo e o nome do pacote. Por exemplo, se o pacote for chamado "test" e você o estiver publicando na organização "My-org" do {% data variables.product.prodname_dotcom %}, o campo `name` no *package.json* deverá ser `@my-org/test`. -{% data reusables.package_registry.verify_repository_field %} {% data reusables.package_registry.publish_package %} +{% data reusables.package_registry.authenticate-step %} +{% data reusables.package_registry.create-npmrc-owner-step %} +{% data reusables.package_registry.add-npmrc-to-repo-step %} +1. Verify the name of your package in your project's *package.json*. The `name` field must contain the scope and the name of the package. For example, if your package is called "test", and you are publishing to the "My-org" {% data variables.product.prodname_dotcom %} organization, the `name` field in your *package.json* should be `@my-org/test`. +{% data reusables.package_registry.verify_repository_field %} +{% data reusables.package_registry.publish_package %} -### Como publicar um pacote usando `publishConfig` no arquivo *package.json* +### Publishing a package using `publishConfig` in the *package.json* file -Use o elemento `publishConfig` no arquivo *package.json* para especificar o registro em que deseja publicar o pacote. Para obter mais informações, confira "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" na documentação do npm. +You can use `publishConfig` element in the *package.json* file to specify the registry where you want the package published. For more information, see "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" in the npm documentation. -1. Edite o arquivo *package.json* do pacote e inclua uma entrada `publishConfig`. - {% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio habilitado: {% endif %} +1. Edit the *package.json* file for your package and include a `publishConfig` entry. + {% ifversion ghes %} + If your instance has subdomain isolation enabled: + {% endif %} ```shell "publishConfig": { - "registry":"https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}" + "registry":"https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}" }, ``` - {% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio desabilitado: + {% ifversion ghes %} + If your instance has subdomain isolation disabled: ```shell "publishConfig": { - "registry":"https://HOSTNAME/_registry/npm/" + "registry":"https://HOSTNAME/_registry/npm/" }, ``` - {% endif %} {% data reusables.package_registry.verify_repository_field %} {% data reusables.package_registry.publish_package %} + {% endif %} +{% data reusables.package_registry.verify_repository_field %} +{% data reusables.package_registry.publish_package %} -## Publicar vários pacotes no mesmo repositório +## Publishing multiple packages to the same repository -Para publicar vários pacotes no mesmo repositório, inclua a URL do repositório do {% data variables.product.prodname_dotcom %} no campo `repository` do arquivo *package.json* de cada pacote. +To publish multiple packages to the same repository, you can include the URL of the {% data variables.product.prodname_dotcom %} repository in the `repository` field of the *package.json* file for each package. -Para garantir que a URL do repositório esteja correta, substitua REPOSITÓRIO pelo nome do repositório que contém o pacote que você deseja publicar, e o PROPRIETÁRIO pelo nome de usuário ou conta de organização no {% data variables.product.prodname_dotcom %} que é proprietário do repositório. +To ensure the repository's URL is correct, replace REPOSITORY with the name of the repository containing the package you want to publish, and OWNER with the name of the user or organization account on {% data variables.product.prodname_dotcom %} that owns the repository. -O {% data variables.product.prodname_registry %} corresponderá ao repositório baseado na URL, em vez de ser baseado no nome do pacote. +{% data variables.product.prodname_registry %} will match the repository based on the URL, instead of based on the package name. ```shell -"repository":"https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY", +"repository":"https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY", ``` -## Instalando um pacote +## Installing a package -Você pode instalar pacotes do {% data variables.product.prodname_registry %} adicionando os pacotes como dependências no arquivo *package.json* do projeto. Para obter mais informações sobre como usar um *package.json* no seu projeto, confira "[Como trabalhar com package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" na documentação do npm. +You can install packages from {% data variables.product.prodname_registry %} by adding the packages as dependencies in the *package.json* file for your project. For more information on using a *package.json* in your project, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" in the npm documentation. -Por padrão, você pode adicionar pacotes a partir de uma organização. Para obter mais informações, confira "[Como instalar pacotes de outras organizações](#installing-packages-from-other-organizations)". +By default, you can add packages from one organization. For more information, see "[Installing packages from other organizations](#installing-packages-from-other-organizations)." -Você também precisa adicionar o arquivo *.npmrc* ao projeto para que todas as solicitações de instalação de pacotes {% ifversion ghae %}sejam encaminhadas para o{% else %}passem pelo{% endif %} {% data variables.product.prodname_registry %}. {% ifversion fpt or ghes or ghec %}Ao rotear todas as solicitações de pacote por meio do {% data variables.product.prodname_registry %}, você pode usar pacotes com escopo e sem escopo de *npmjs.org*. Para obter mais informações, confira "[npm-scope](https://docs.npmjs.com/misc/scope)" na documentação do npm.{% endif %} +You also need to add the *.npmrc* file to your project so that all requests to install packages will {% ifversion ghae %}be routed to{% else %}go through{% endif %} {% data variables.product.prodname_registry %}. {% ifversion fpt or ghes or ghec %}When you route all package requests through {% data variables.product.prodname_registry %}, you can use both scoped and unscoped packages from *npmjs.org*. For more information, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation.{% endif %} -{% ifversion ghae %} Por padrão, você só pode usar pacotes do npm hospedados na sua empresa e não poderá usar pacotes sem escopo. Para obter mais informações sobre como definir o escopo de um pacote, confira "[npm-scope](https://docs.npmjs.com/misc/scope)" na documentação do npm. Se necessário, o suporte do {% data variables.product.prodname_dotcom %} pode habilitar um proxy upstream para npmjs.org. Depois que um proxy upstream for habilitado, se um pacote solicitado não for encontrado na sua empresa, o {% data variables.product.prodname_registry %} fará uma solicitação de proxy para npmjs.org. +{% ifversion ghae %} +By default, you can only use npm packages hosted on your enterprise, and you will not be able to use unscoped packages. For more information on package scoping, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation. If required, {% data variables.product.prodname_dotcom %} support can enable an upstream proxy to npmjs.org. Once an upstream proxy is enabled, if a requested package isn't found on your enterprise, {% data variables.product.prodname_registry %} makes a proxy request to npmjs.org. {% endif %} -{% data reusables.package_registry.authenticate-step %} {% data reusables.package_registry.create-npmrc-owner-step %} {% data reusables.package_registry.add-npmrc-to-repo-step %} -4. Configure *package.json* no projeto para usar o pacote que você está instalando. Para adicionar as dependências de pacote ao arquivo *package.json* para o {% data variables.product.prodname_registry %}, especifique o nome do pacote com escopo completo, como `@my-org/server`. Para pacotes de *npmjs.com*, especifique o nome completo, como `@babel/core` ou `@lodash`. Por exemplo, o *package.json* a seguir usa o pacote `@octo-org/octo-app` como uma dependência. +{% data reusables.package_registry.authenticate-step %} +{% data reusables.package_registry.create-npmrc-owner-step %} +{% data reusables.package_registry.add-npmrc-to-repo-step %} +4. Configure *package.json* in your project to use the package you are installing. To add your package dependencies to the *package.json* file for {% data variables.product.prodname_registry %}, specify the full-scoped package name, such as `@my-org/server`. For packages from *npmjs.com*, specify the full name, such as `@babel/core` or `@lodash`. For example, this following *package.json* uses the `@octo-org/octo-app` package as a dependency. ```json { @@ -180,33 +198,36 @@ Você também precisa adicionar o arquivo *.npmrc* ao projeto para que todas as } } ``` -5. Instale o pacote. +5. Install the package. ```shell $ npm install ``` -### Instalar pacotes de outras organizações +### Installing packages from other organizations -Por padrão, você só pode usar pacotes do {% data variables.product.prodname_registry %} de uma organização. Caso deseje encaminhar solicitações de pacotes para várias organizações e usuários, adicione mais linhas ao arquivo *.npmrc* substituindo {% ifversion ghes or ghae %}*HOSTNAME* pelo nome do host da {% data variables.product.product_location %} e {% endif %}*OWNER* pelo nome da conta de usuário ou da organização que é o proprietário do repositório que contém o projeto. +By default, you can only use {% data variables.product.prodname_registry %} packages from one organization. If you'd like to route package requests to multiple organizations and users, you can add additional lines to your *.npmrc* file, replacing {% ifversion ghes or ghae %}*HOSTNAME* with the host name of {% data variables.location.product_location %} and {% endif %}*OWNER* with the name of the user or organization account that owns the repository containing your project. -{% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio habilitado: {% endif %} +{% ifversion ghes %} +If your instance has subdomain isolation enabled: +{% endif %} ```shell -@OWNER:registry=https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME{% endif %} -@OWNER:registry=https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME{% endif %} +@OWNER:registry=https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME{% endif %} +@OWNER:registry=https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME{% endif %} ``` -{% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio desabilitado: +{% ifversion ghes %} +If your instance has subdomain isolation disabled: ```shell -@OWNER:registry=https://HOSTNAME/_registry/npm -@OWNER:registry=https://HOSTNAME/_registry/npm +@OWNER:registry=https://HOSTNAME/_registry/npm +@OWNER:registry=https://HOSTNAME/_registry/npm ``` {% endif %} {% ifversion ghes %} -## Usando o registro oficial do NPM +## Using the official NPM registry -O {% data variables.product.prodname_registry %} permite que você acesse o registro npm oficial em `registry.npmjs.com`, caso seu administrador do {% data variables.product.prodname_ghe_server %} tenha habilitado esse recurso. Para obter mais informações, confira [Como se conectar ao registro npm](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry). +{% data variables.product.prodname_registry %} allows you to access the official NPM registry at `registry.npmjs.com`, if your {% data variables.product.prodname_ghe_server %} administrator has enabled this feature. For more information, see [Connecting to the official NPM registry](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry). {% endif %} diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md index d4e649b93d..9e13e1e527 100644 --- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md +++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md @@ -1,6 +1,6 @@ --- -title: Trabalhando com o registro NuGet -intro: 'Você pode configurar a CLI (interface de linha de comando) `dotnet` para publicar pacotes NuGet no {% data variables.product.prodname_registry %} e usar pacotes armazenados no {% data variables.product.prodname_registry %} como dependências em um projeto .NET.' +title: Working with the NuGet registry +intro: 'You can configure the `dotnet` command-line interface (CLI) to publish NuGet packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a .NET project.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /articles/configuring-nuget-for-use-with-github-package-registry @@ -15,24 +15,20 @@ versions: ghae: '*' ghec: '*' shortTitle: NuGet registry -ms.openlocfilehash: d97a5645a3d945bb79cf6d3b9e8e09eb6b5d7a42 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147580508' --- -{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} + +{% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} {% data reusables.package_registry.admins-can-configure-package-types %} -## Autenticar-se no {% data variables.product.prodname_registry %} +## Authenticating to {% data variables.product.prodname_registry %} {% data reusables.package_registry.authenticate-packages %} -### Autenticação com o `GITHUB_TOKEN` no {% data variables.product.prodname_actions %} +### Authenticating with `GITHUB_TOKEN` in {% data variables.product.prodname_actions %} -Use o comando a seguir para se autenticar no {% data variables.product.prodname_registry %} em um fluxo de trabalho do {% data variables.product.prodname_actions %} usando o `GITHUB_TOKEN`, em vez de embutir um token em código em um arquivo nuget.config no repositório: +Use the following command to authenticate to {% data variables.product.prodname_registry %} in a {% data variables.product.prodname_actions %} workflow using the `GITHUB_TOKEN` instead of hardcoding a {% data variables.product.pat_generic %} in a nuget.config file in the repository: ```shell dotnet nuget add source --username USERNAME --password {%raw%}${{ secrets.GITHUB_TOKEN }}{% endraw %} --store-password-in-clear-text --name github "https://{% ifversion fpt or ghec %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json" @@ -40,19 +36,20 @@ dotnet nuget add source --username USERNAME --password {%raw%}${{ secrets.GITHUB {% data reusables.package_registry.authenticate-packages-github-token %} -### Efetuando a autenticação com um token de acesso pessoal +### Authenticating with a {% data variables.product.pat_generic %} {% data reusables.package_registry.required-scopes %} -Para se autenticar no {% data variables.product.prodname_registry %} com a CLI (interface de linha de comando) do `dotnet`, crie um arquivo *nuget.config* no diretório do projeto especificando o {% data variables.product.prodname_registry %} como uma fonte em `packageSources` para o cliente da CLI do `dotnet`. +To authenticate to {% data variables.product.prodname_registry %} with the `dotnet` command-line interface (CLI), create a *nuget.config* file in your project directory specifying {% data variables.product.prodname_registry %} as a source under `packageSources` for the `dotnet` CLI client. -Você deve substituir: -- `USERNAME` com o nome de sua conta de usuário em {% data variables.product.prodname_dotcom %}. -- `TOKEN` pelo seu token de acesso pessoal. -- `OWNER` pelo nome da conta de usuário ou de organização que é o proprietário do repositório que contém o projeto.{% ifversion ghes or ghae %} -- `HOSTNAME` pelo nome do host do {% data variables.product.product_location %}.{% endif %} +You must replace: +- `USERNAME` with the name of your personal account on {% data variables.product.prodname_dotcom %}. +- `TOKEN` with your {% data variables.product.pat_v1 %}. +- `OWNER` with the name of the user or organization account that owns the repository containing your project.{% ifversion ghes or ghae %} +- `HOSTNAME` with the host name for {% data variables.location.product_location %}.{% endif %} -{% ifversion ghes %}Se a sua instância tiver o isolamento de subdomínio habilitado: {% endif %} +{% ifversion ghes %}If your instance has subdomain isolation enabled: +{% endif %} ```xml @@ -70,7 +67,8 @@ Você deve substituir: ``` -{% ifversion ghes %} Se a sua instância tiver o isolamento de subdomínio desabilitado: +{% ifversion ghes %} +If your instance has subdomain isolation disabled: ```xml @@ -89,44 +87,44 @@ Você deve substituir: ``` {% endif %} -## Publicando um pacote +## Publishing a package -Publique um pacote no {% data variables.product.prodname_registry %} autenticando-se com um arquivo *nuget.config* ou usando a opção `--api-key` de linha de comando com seu PAT (token de acesso pessoal) do {% data variables.product.prodname_dotcom %}. +You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file, or by using the `--api-key` command line option with your {% data variables.product.prodname_dotcom %} {% data variables.product.pat_v1 %}. -### Publicar um pacote usando um o PAT do GitHub como sua chave da API +### Publishing a package using a GitHub {% data variables.product.pat_generic %} as your API key -Se você ainda não tem um PAT para uso na sua conta no {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, confira "[Como criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)". +If you don't already have a PAT to use for your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." -1. Criar um novo projeto. +1. Create a new project. ```shell dotnet new console --name OctocatApp ``` -2. Empacotar o projeto. +2. Package the project. ```shell dotnet pack --configuration Release ``` -3. Publique o pacote usando o seu PAT como a chave da API. +3. Publish the package using your {% data variables.product.pat_generic %} as the API key. ```shell - dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --api-key YOUR_GITHUB_PAT --source "github" + dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --api-key YOUR_GITHUB_PAT --source "github" ``` {% data reusables.package_registry.viewing-packages %} -### Como publicar um pacote usando um arquivo *nuget.config* +### Publishing a package using a *nuget.config* file -Para a publicação, você precisa usar o mesmo valor para `OWNER` no arquivo *csproj* usado no arquivo de autenticação *nuget.config*. Especifique ou incremente o número de versão no arquivo *.csproj* e use o comando `dotnet pack` para criar um arquivo *.nuspec* para essa versão. Para obter mais informações sobre como criar seu pacote, confira "[Criar e publicar um pacote](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)" na documentação da Microsoft. +When publishing, you need to use the same value for `OWNER` in your *csproj* file that you use in your *nuget.config* authentication file. Specify or increment the version number in your *.csproj* file, then use the `dotnet pack` command to create a *.nuspec* file for that version. For more information on creating your package, see "[Create and publish a package](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)" in the Microsoft documentation. {% data reusables.package_registry.authenticate-step %} -2. Criar um novo projeto. +2. Create a new project. ```shell dotnet new console --name OctocatApp ``` -3. Adicione informações específicas do seu projeto ao arquivo do projeto, que termina com *.csproj*. Você deve substituir: - - `OWNER` pelo nome da conta de usuário ou de organização que é o proprietário do repositório que contém o projeto. - - `REPOSITORY` pelo nome do repositório que contém o pacote que você deseja publicar. - - `1.0.0` pelo número de versão do pacote.{% ifversion ghes or ghae %} - - `HOSTNAME` pelo nome do host do {% data variables.product.product_location %}.{% endif %} +3. Add your project's specific information to your project's file, which ends in *.csproj*. You must replace: + - `OWNER` with the name of the user or organization account that owns the repository containing your project. + - `REPOSITORY` with the name of the repository containing the package you want to publish. + - `1.0.0` with the version number of the package.{% ifversion ghes or ghae %} + - `HOSTNAME` with the host name for {% data variables.location.product_location %}.{% endif %} ``` xml @@ -143,23 +141,23 @@ Para a publicação, você precisa usar o mesmo valor para `OWNER` no arquivo *c ``` -4. Empacotar o projeto. +4. Package the project. ```shell dotnet pack --configuration Release ``` -5. Publique o pacote usando a `key` que você especificou no arquivo *nuget.config*. +5. Publish the package using the `key` you specified in the *nuget.config* file. ```shell dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github" ``` {% data reusables.package_registry.viewing-packages %} -## Publicar vários pacotes no mesmo repositório +## Publishing multiple packages to the same repository -Para publicar vários pacotes no mesmo repositório, você pode incluir a mesma URL do repositório do {% data variables.product.prodname_dotcom %} nos campos `RepositoryURL` em todos os arquivos de projeto *.csproj*. O {% data variables.product.prodname_dotcom %} corresponde ao repositório baseado nesse campo. +To publish multiple packages to the same repository, you can include the same {% data variables.product.prodname_dotcom %} repository URL in the `RepositoryURL` fields in all *.csproj* project files. {% data variables.product.prodname_dotcom %} matches the repository based on that field. -Por exemplo, os projetos *OctodogApp* e *OctocatApp* serão publicados no mesmo repositório: +For example, the *OctodogApp* and *OctocatApp* projects will publish to the same repository: ``` xml @@ -195,13 +193,13 @@ Por exemplo, os projetos *OctodogApp* e *OctocatApp* serão publicados no mesmo ``` -## Instalando um pacote +## Installing a package -O uso de pacotes do {% data variables.product.prodname_dotcom %} no projeto é semelhante ao uso de pacotes de *nuget.org*. Adicione as dependências do pacote ao arquivo *.csproj* especificando o nome e a versão do pacote. Para obter mais informações sobre como usar um arquivo *.csproj* no seu projeto, confira "[Como trabalhar com pacotes NuGet](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)" na documentação da Microsoft. +Using packages from {% data variables.product.prodname_dotcom %} in your project is similar to using packages from *nuget.org*. Add your package dependencies to your *.csproj* file, specifying the package name and version. For more information on using a *.csproj* file in your project, see "[Working with NuGet packages](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)" in the Microsoft documentation. {% data reusables.package_registry.authenticate-step %} -2. Para usar um pacote, adicione `ItemGroup` e configure o campo `PackageReference` no arquivo de projeto *.csproj*. Substitua o valor `OctokittenApp` em `Include="OctokittenApp"` por sua dependência de pacote e o valor `12.0.2` em `Version="12.0.2"` pela versão que você deseja usar: +2. To use a package, add `ItemGroup` and configure the `PackageReference` field in the *.csproj* project file. Replace the `OctokittenApp` value in `Include="OctokittenApp"` with your package dependency, and replace the `12.0.2` value in `Version="12.0.2"` with the version you want to use: ``` xml @@ -223,19 +221,19 @@ O uso de pacotes do {% data variables.product.prodname_dotcom %} no projeto é s ``` -3. Instale os pacotes com o comando `restore`. +3. Install the packages with the `restore` command. ```shell dotnet restore ``` -## Solução de problemas +## Troubleshooting -Talvez o pacote NuGet não consiga efetuar push se a `RepositoryUrl` no *.csproj* não está definida como o repositório esperado. +Your NuGet package may fail to push if the `RepositoryUrl` in *.csproj* is not set to the expected repository . -Se você estiver usando um arquivo nuspec, verifique se ele tem um elemento `repository` com os atributos `type` e `url` obrigatórios. +If you're using a nuspec file, ensure that it has a `repository` element with the required `type` and `url` attributes. -Se você estiver usando um `GITHUB_TOKEN` para autenticação em um registro {% data variables.product.prodname_registry %} em um fluxo de trabalho {% data variables.product.prodname_actions %}, o token não poderá acessar pacotes baseados em repositório privado em um repositório diferente de onde o fluxo de trabalho está sendo executado. Alternativamente, para acessar pacotes associados a outros repositórios, gere um PAT com o escopo `read:packages` e passe esse token como um segredo. +If you're using a `GITHUB_TOKEN` to authenticate to a {% data variables.product.prodname_registry %} registry within a {% data variables.product.prodname_actions %} workflow, the token cannot access private repository-based packages in a different repository other than where the workflow is running in. To access packages associated with other repositories, instead generate a {% data variables.product.pat_v1 %} with the `read:packages` scope and pass this token in as a secret. -## Leitura adicional +## Further reading -- "[Como excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package)" +- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md index 59c8e4f5f5..e179d7aa58 100644 --- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md +++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md @@ -1,6 +1,6 @@ --- -title: Trabalhando com o registro do RubyGems -intro: 'Você pode configurar RubyGems para publicar um pacote em {% data variables.product.prodname_registry %} e usar pacotes armazenados em {% data variables.product.prodname_registry %} como dependências em um projeto Ruby com o Bundler.' +title: Working with the RubyGems registry +intro: 'You can configure RubyGems to publish a package to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Ruby project with Bundler.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /articles/configuring-rubygems-for-use-with-github-package-registry @@ -14,69 +14,65 @@ versions: ghae: '*' ghec: '*' shortTitle: RubyGems registry -ms.openlocfilehash: 56fb2fda7c50e6f1a1a3265e55c77d65a7af8705 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147882324' --- -{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} + +{% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} {% data reusables.package_registry.admins-can-configure-package-types %} -## Pré-requisitos +## Prerequisites -- Você deve ter o RubyGems 2.4.1 ou superior. Para encontrar a versão do seu RubyGems: +- You must have RubyGems 2.4.1 or higher. To find your RubyGems version: ```shell $ gem --version ``` -- Você precisa ter o Bundler 1.6.4 ou superior. Para encontrar sua versão do Bundler: +- You must have bundler 1.6.4 or higher. To find your Bundler version: ```shell $ bundle --version Bundler version 1.13.7 ``` -- Instale o keycutter para gerenciar várias credenciais. Para instalar o keycutter: +- Install keycutter to manage multiple credentials. To install keycutter: ```shell $ gem install keycutter ``` -## Autenticar-se no {% data variables.product.prodname_registry %} +## Authenticating to {% data variables.product.prodname_registry %} {% data reusables.package_registry.authenticate-packages %} {% data reusables.package_registry.authenticate-packages-github-token %} -### Efetuando a autenticação com um token de acesso pessoal +### Authenticating with a {% data variables.product.pat_generic %} {% data reusables.package_registry.required-scopes %} -Autentique-se no {% data variables.product.prodname_registry %} com o RubyGems editando o arquivo *~/.gem/credentials* para publicação de gems, editando o arquivo *~/.gemrc* para instalar um só gem ou usando o Bundler para acompanhar e instalar um ou mais gems. +You can authenticate to {% data variables.product.prodname_registry %} with RubyGems by editing the *~/.gem/credentials* file for publishing gems, editing the *~/.gemrc* file for installing a single gem, or using Bundler for tracking and installing one or more gems. -Para publicar novos gems, você precisa se autenticar no {% data variables.product.prodname_registry %} com o RubyGems editando o arquivo *~/.gem/credentials* para incluir seu token de acesso pessoal. Crie um arquivo *~/.gem/credentials* se ele não existir. +To publish new gems, you need to authenticate to {% data variables.product.prodname_registry %} with RubyGems by editing your *~/.gem/credentials* file to include your {% data variables.product.pat_v1 %}. Create a new *~/.gem/credentials* file if this file doesn't exist. -Por exemplo, crie ou edite um arquivo *~/.gem/credentials* para incluir o conteúdo indicado a seguir, substituindo *TOKEN* pelo seu token de acesso pessoal. +For example, you would create or edit a *~/.gem/credentials* to include the following, replacing *TOKEN* with your {% data variables.product.pat_generic %}. ```shell --- -:github: Bearer TOKEN +:github: Bearer TOKEN ``` -Para instalar gems, você precisa se autenticar no {% data variables.product.prodname_registry %} editando o arquivo *~/.gemrc* para que o projeto inclua `https://USERNAME:TOKEN@{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`. Você deve substituir: - - `USERNAME` pelo seu nome de usuário do {% data variables.product.prodname_dotcom %}. - - `TOKEN` pelo seu token de acesso pessoal. - - `OWNER` pelo nome da conta de usuário ou da organização que é proprietário do repositório que contém o projeto.{% ifversion ghes %} - - `REGISTRY-URL` pela URL do registro do RubyGems da instância. Se a sua instância tem o isolamento de subdomínio habilitado, use `rubygems.HOSTNAME`. Se a sua instância tem o isolamento de subdomínio desabilitado, use `HOSTNAME/_registry/rubygems`. Em ambos os casos, substitua *HOSTNAME* pelo nome do host da sua instância do {% data variables.product.prodname_ghe_server %}. +To install gems, you need to authenticate to {% data variables.product.prodname_registry %} by editing the *~/.gemrc* file for your project to include `https://USERNAME:TOKEN@{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`. You must replace: + - `USERNAME` with your {% data variables.product.prodname_dotcom %} username. + - `TOKEN` with your {% data variables.product.pat_v1 %}. + - `OWNER` with the name of the user or organization account that owns the repository containing your project.{% ifversion ghes %} + - `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance. {% elsif ghae %} - - `REGISTRY-URL` pela URL do registro do RubyGems da instância, `rubygems.HOSTNAME`. Substitua *HOSTNAME* pelo nome do host da {% data variables.product.product_location %}. + - `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.location.product_location %}. {% endif %} -Caso você não tenha um arquivo *~/.gemrc*, crie um arquivo *~/.gemrc* usando este exemplo. +If you don't have a *~/.gemrc* file, create a new *~/.gemrc* file using this example. ```shell --- @@ -90,45 +86,45 @@ Caso você não tenha um arquivo *~/.gemrc*, crie um arquivo *~/.gemrc* usando e ``` -Para se autenticar no Bundler, configure-o para usar seu token de acesso pessoal, substituindo *USERNAME* pelo seu nome de usuário do {% data variables.product.prodname_dotcom %}, *TOKEN* pelo seu token de acesso pessoal e *OWNER* pelo nome da conta de usuário ou da organização que é o proprietário do repositório que contém o projeto.{% ifversion ghes %} Substitua `REGISTRY-URL` pela URL do registro do RubyGems da instância. Se a sua instância tem o isolamento de subdomínio habilitado, use `rubygems.HOSTNAME`. Se a sua instância tem o isolamento de subdomínio desabilitado, use `HOSTNAME/_registry/rubygems`. Em ambos os casos, substitua *HOSTNAME* pelo nome do host da instância do {% data variables.product.prodname_ghe_server %}.{% elsif ghae %} Substitua `REGISTRY-URL` pela URL do registro do RubyGems da instância, `rubygems.HOSTNAME`. Substitua *HOSTNAME* pelo nome do host da {% data variables.product.product_location %}.{% endif %} +To authenticate with Bundler, configure Bundler to use your {% data variables.product.pat_v1 %}, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your {% data variables.product.pat_generic %}, and *OWNER* with the name of the user or organization account that owns the repository containing your project.{% ifversion ghes %} Replace `REGISTRY-URL` with the URL for your instance's RubyGems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance.{% elsif ghae %}Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.location.product_location %}.{% endif %} ```shell -$ bundle config https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER USERNAME:TOKEN +$ bundle config https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER USERNAME:TOKEN ``` -## Publicando um pacote +## Publishing a package -{% data reusables.package_registry.default-name %} Por exemplo, quando você publica `octo-gem` na organização `octo-org`, o {% data variables.product.prodname_registry %} publica o gem no repositório `octo-org/octo-gem`. Para obter mais informações sobre como criar seu gem, confira "[Criar seu gem](http://guides.rubygems.org/make-your-own-gem/)" na documentação do RubyGems. +{% data reusables.package_registry.default-name %} For example, when you publish `octo-gem` to the `octo-org` organization, {% data variables.product.prodname_registry %} publishes the gem to the `octo-org/octo-gem` repository. For more information on creating your gem, see "[Make your own gem](http://guides.rubygems.org/make-your-own-gem/)" in the RubyGems documentation. {% data reusables.package_registry.viewing-packages %} {% data reusables.package_registry.authenticate-step %} -2. Compile o pacote do *gemspec* para criar o pacote *.gem*. +2. Build the package from the *gemspec* to create the *.gem* package. ```shell gem build OCTO-GEM.gemspec ``` -3. Publique um pacote no {% data variables.product.prodname_registry %}, substituindo `OWNER` pelo nome da conta de usuário ou da organização que é o proprietário do repositório que contém o projeto e `OCTO-GEM` pelo nome do pacote do gem.{% ifversion ghes %} Substitua `REGISTRY-URL` pela URL do registro do RubyGems da instância. Se a sua instância tem o isolamento de subdomínio habilitado, use `rubygems.HOSTNAME`. Se a sua instância tem o isolamento de subdomínio desabilitado, use `HOSTNAME/_registry/rubygems`. Em ambos os casos, substitua *HOSTNAME* pelo nome do host da instância do {% data variables.product.prodname_ghe_server %}.{% elsif ghae %} Substitua `REGISTRY-URL` pela URL do registro do RubyGems da instância, `rubygems.HOSTNAME`. Substitua *HOSTNAME* pelo nome do host da {% data variables.product.product_location %}.{% endif %} +3. Publish a package to {% data variables.product.prodname_registry %}, replacing `OWNER` with the name of the user or organization account that owns the repository containing your project and `OCTO-GEM` with the name of your gem package.{% ifversion ghes %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% elsif ghae %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.location.product_location %}.{% endif %} ```shell $ gem push --key github \ - --host https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER \ - OCTO-GEM-0.0.1.gem + --host https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER \ + OCTO-GEM-0.0.1.gem ``` -## Publicar vários pacotes no mesmo repositório +## Publishing multiple packages to the same repository -Para publicar vários gems no mesmo repositório, inclua a URL do repositório do {% data variables.product.prodname_dotcom %} no campo `github_repo` em `gem.metadata`. Se você incluir esse campo, o {% data variables.product.prodname_dotcom %} corresponderá ao repositório com base nesse valor, em vez de usar o nome do gem.{% ifversion ghes or ghae %} Substitua *HOSTNAME* pelo nome do host da {% data variables.product.product_location %}.{% endif %} +To publish multiple gems to the same repository, you can include the URL to the {% data variables.product.prodname_dotcom %} repository in the `github_repo` field in `gem.metadata`. If you include this field, {% data variables.product.prodname_dotcom %} matches the repository based on this value, instead of using the gem name.{% ifversion ghes or ghae %} Replace *HOSTNAME* with the host name of {% data variables.location.product_location %}.{% endif %} ```ruby gem.metadata = { "github_repo" => "ssh://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" } ``` -## Instalando um pacote +## Installing a package -Você pode usar gems no {% data variables.product.prodname_registry %} da mesma forma que você usa gems em *rubygems.org*. Você precisa se autenticar no {% data variables.product.prodname_registry %} adicionando o usuário ou a organização do {% data variables.product.prodname_dotcom %} como uma fonte no arquivo *~/.gemrc* ou usando o Bundler e editando o *Gemfile*. +You can use gems from {% data variables.product.prodname_registry %} much like you use gems from *rubygems.org*. You need to authenticate to {% data variables.product.prodname_registry %} by adding your {% data variables.product.prodname_dotcom %} user or organization as a source in the *~/.gemrc* file or by using Bundler and editing your *Gemfile*. {% data reusables.package_registry.authenticate-step %} -1. Para o Bundler, adicione o usuário ou a organização do {% data variables.product.prodname_dotcom %} como uma fonte no *Gemfile* para buscar gems dessa nova fonte. Por exemplo, você pode adicionar um novo bloco `source` ao *Gemfile* que só usa o {% data variables.product.prodname_registry %} para os pacotes que você especificar, substituindo *GEM NAME* pelo pacote que deseja instalar por meio do {% data variables.product.prodname_registry %} e *OWNER* pelo usuário ou pela organização que é o proprietário do repositório que contém o gem que deseja instalar.{% ifversion ghes %} Substitua `REGISTRY-URL` pela URL do registro do RubyGems da instância. Se a sua instância tem o isolamento de subdomínio habilitado, use `rubygems.HOSTNAME`. Se a sua instância tem o isolamento de subdomínio desabilitado, use `HOSTNAME/_registry/rubygems`. Em ambos os casos, substitua *HOSTNAME* pelo nome do host da instância do {% data variables.product.prodname_ghe_server %}.{% elsif ghae %} Substitua `REGISTRY-URL` pela URL do registro do RubyGems da instância, `rubygems.HOSTNAME`. Substitua *HOSTNAME* pelo nome do host da {% data variables.product.product_location %}.{% endif %} +1. For Bundler, add your {% data variables.product.prodname_dotcom %} user or organization as a source in your *Gemfile* to fetch gems from this new source. For example, you can add a new `source` block to your *Gemfile* that uses {% data variables.product.prodname_registry %} only for the packages you specify, replacing *GEM NAME* with the package you want to install from {% data variables.product.prodname_registry %} and *OWNER* with the user or organization that owns the repository containing the gem you want to install.{% ifversion ghes %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% elsif ghae %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.location.product_location %}.{% endif %} ```ruby source "https://rubygems.org" @@ -140,7 +136,7 @@ Você pode usar gems no {% data variables.product.prodname_registry %} da mesma end ``` -3. Para versões do Bundler anteriores à 1.7.0, adicione uma nova `source` global. Para obter mais informações sobre como usar o Bundler, confira a [documentação em bundler.io](https://bundler.io/gemfile.html). +3. For Bundler versions earlier than 1.7.0, you need to add a new global `source`. For more information on using Bundler, see the [bundler.io documentation](https://bundler.io/gemfile.html). ```ruby source "https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" @@ -150,12 +146,12 @@ Você pode usar gems no {% data variables.product.prodname_registry %} da mesma gem "GEM NAME" ``` -4. Instale o pacote: +4. Install the package: ```shell $ gem install octo-gem --version "0.1.1" ``` -## Leitura adicional +## Further reading -- "[Como excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package)" +- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md index f5154db1ce..960da5c7d3 100644 --- a/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -1,6 +1,6 @@ --- -title: Sobre o GitHub Pages -intro: 'Você pode usar {% data variables.product.prodname_pages %} para hospedar um site sobre você, sua organização, ou seu projeto diretamente a partir de um repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.' +title: About GitHub Pages +intro: 'You can use {% data variables.product.prodname_pages %} to host a website about yourself, your organization, or your project directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}.' redirect_from: - /articles/what-are-github-pages - /articles/what-is-github-pages @@ -18,129 +18,134 @@ versions: ghec: '*' topics: - Pages -ms.openlocfilehash: 1063adbe5396569110af1809a8619440e3bf106b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147507980' --- -## Sobre o {% data variables.product.prodname_pages %} -O {% data variables.product.prodname_pages %} é um serviço de hospedagem de site estático que usa arquivos HTML, CSS e JavaScript diretamente de um repositório no {% data variables.product.product_name %} e, como opção, executa os arquivos por meio de um processo e publica um site. Veja exemplos de sites do {% data variables.product.prodname_pages %} na [coleção de exemplos do {% data variables.product.prodname_pages %}](https://github.com/collections/github-pages-examples). +## About {% data variables.product.prodname_pages %} -{% ifversion fpt or ghec %} É possível hospedar seu site no domínio `github.io` do {% data variables.product.prodname_dotcom %} ou em um domínio personalizado próprio. Para obter mais informações, confira "[Como usar um domínio personalizado com o {% data variables.product.prodname_pages %}](/articles/using-a-custom-domain-with-github-pages)". +{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository on {% data variables.product.product_name %}, optionally runs the files through a build process, and publishes a website. You can see examples of {% data variables.product.prodname_pages %} sites in the [{% data variables.product.prodname_pages %} examples collection](https://github.com/collections/github-pages-examples). + +{% ifversion fpt or ghec %} +You can host your site on {% data variables.product.prodname_dotcom %}'s `github.io` domain or your own custom domain. For more information, see "[Using a custom domain with {% data variables.product.prodname_pages %}](/articles/using-a-custom-domain-with-github-pages)." {% endif %} -{% ifversion fpt or ghec %} {% data reusables.pages.about-private-publishing %} Para obter mais informações, confira "[Alterando a visibilidade de seu site do {% data variables.product.prodname_pages %}]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site) {% ifversion fpt %}" na documentação do {% data variables.product.prodname_ghe_cloud %}. {% else %}". {% endif %} {% endif %} - -Para começar, confira "[Como criar um site do {% data variables.product.prodname_pages %}](/articles/creating-a-github-pages-site)". - -{% ifversion fpt or ghes or ghec %} Os proprietários da organização podem desabilitar a publicação de sites do {% data variables.product.prodname_pages %} nos repositórios da organização. Para obter mais informações, confira "[Como gerenciar a publicação de sites do {% data variables.product.prodname_pages %} para sua organização](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". +{% ifversion fpt or ghec %} +{% data reusables.pages.about-private-publishing %} For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} {% endif %} -## Tipos de site do {% data variables.product.prodname_pages %} +To get started, see "[Creating a {% data variables.product.prodname_pages %} site](/articles/creating-a-github-pages-site)." -Há três tipos de site do {% data variables.product.prodname_pages %}: projeto, usuário e organização. Os sites de projeto são conectados a um projeto específico hospedado no {% data variables.product.product_name %}, como uma biblioteca do JavaScript ou um conjunto de receitas. Os sites de usuário e organização estão conectados a uma conta específica em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. - -Para publicar um site de usuário, você precisa criar um repositório de propriedade da sua conta pessoal chamado {% ifversion fpt or ghec %}`.github.io`{% else %}`.`{% endif %}. Para publicar um site da organização, você precisa criar um repositório de propriedade de uma organização chamado {% ifversion fpt or ghec %}`.github.io`{% else %}`.`{% endif %}. {% ifversion fpt or ghec %}A menos que você esteja usando um domínio personalizado, os sites de usuário e de organização ficam disponíveis em `http(s)://.github.io` ou `http(s)://.github.io`.{% elsif ghae %}Os sites de usuário e de organização ficam disponíveis em `http(s)://pages./` ou `http(s)://pages./`.{% endif %} - -Os arquivos de origem de um site de projeto são armazenados no mesmo repositório que o respectivo projeto. {% ifversion fpt or ghec %} A menos que você esteja usando um domínio personalizado, os sites de projeto ficam disponíveis em `http(s)://.github.io/` ou `http(s)://.github.io/`.{% elsif ghae %}Os sites de projeto ficam disponíveis em `http(s)://pages.///` ou `http(s)://pages.///`.{% endif %} - -{% ifversion ghec %} Se você publicar seu site no modo privado, a URL do site será diferente. Para obter mais informações, confira "[Como alterar a visibilidade do seu site do {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)". +{% ifversion fpt or ghes or ghec %} +Organization owners can disable the publication of {% data variables.product.prodname_pages %} sites from the organization's repositories. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." {% endif %} -{% ifversion fpt or ghec %} Para obter mais informações sobre como os domínios personalizados afetam a URL do seu site, confira "[Sobre os domínios personalizados e o {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)". +## Types of {% data variables.product.prodname_pages %} sites + +There are three types of {% data variables.product.prodname_pages %} sites: project, user, and organization. Project sites are connected to a specific project hosted on {% data variables.product.product_name %}, such as a JavaScript library or a recipe collection. User and organization sites are connected to a specific account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. + +To publish a user site, you must create a repository owned by your personal account that's named {% ifversion fpt or ghec %}`.github.io`{% else %}`.`{% endif %}. To publish an organization site, you must create a repository owned by an organization that's named {% ifversion fpt or ghec %}`.github.io`{% else %}`.`{% endif %}. {% ifversion fpt or ghec %}Unless you're using a custom domain, user and organization sites are available at `http(s)://.github.io` or `http(s)://.github.io`.{% elsif ghae %}User and organization sites are available at `http(s)://pages./` or `http(s)://pages./`.{% endif %} + +The source files for a project site are stored in the same repository as their project. {% ifversion fpt or ghec %}Unless you're using a custom domain, project sites are available at `http(s)://.github.io/` or `http(s)://.github.io/`.{% elsif ghae %}Project sites are available at `http(s)://pages.///` or `http(s)://pages.///`.{% endif %} + +{% ifversion ghec %} +If you publish your site privately, the URL for your site will be different. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." {% endif %} -Você só pode criar um site de usuário ou organização para cada conta em {% data variables.product.product_name %}. Os sites de projeto, sejam eles de uma organização ou de uma conta pessoal, são ilimitados. +{% ifversion fpt or ghec %} +For more information about how custom domains affect the URL for your site, see "[About custom domains and {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)." +{% endif %} -{% ifversion ghes %} A URL em que o site estará disponível depende da habilitação do isolamento do subdomínio para a {% data variables.product.product_location %}. +You can only create one user or organization site for each account on {% data variables.product.product_name %}. Project sites, whether owned by an organization or a personal account, are unlimited. -| Tipo de site | Isolamento de subdomínio habilitado | Isolamento de subdomínio desabilitado | +{% ifversion ghes %} +The URL where your site is available depends on whether subdomain isolation is enabled for {% data variables.location.product_location %}. + +| Type of site | Subdomain isolation enabled | Subdomain isolation disabled | | ------------ | --------------------------- | ---------------------------- | -Usuário | `http(s)://pages./` | `http(s):///pages/` | -Organização | `http(s)://pages./` | `http(s):///pages/` | -Site de projeto de propriedade de uma conta pessoal | `http(s)://pages.///` | `http(s):///pages///` -Site de projeto de propriedade da conta da organização | `http(s)://pages.///` | `http(s):///pages///` +User | `http(s)://pages./` | `http(s):///pages/` | +Organization | `http(s)://pages./` | `http(s):///pages/` | +Project site owned by personal account | `http(s)://pages.///` | `http(s):///pages///` +Project site owned by organization account | `http(s)://pages.///` | `http(s):///pages///` -Para obter mais informações, confira "[Como habilitar o isolamento de subdomínio](/enterprise/admin/installation/enabling-subdomain-isolation)" ou entre em contato com o administrador do site. +For more information, see "[Enabling subdomain isolation](/enterprise/admin/installation/enabling-subdomain-isolation)" or contact your site administrator. {% endif %} -## Publicar fontes para sites do {% data variables.product.prodname_pages %} +## Publishing sources for {% data variables.product.prodname_pages %} sites {% data reusables.pages.private_pages_are_public_warning %} {% data reusables.pages.pages-about-publishing-source %} -Para obter mais informações, confira "[Como configurar uma fonte de publicação para o seu site do GitHub Pages](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." +For more information, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." {% ifversion ghec %} -## Limitações do {% data variables.product.prodname_emus %} -Se você for um {% data variables.product.prodname_managed_user %}, o uso do {% data variables.product.prodname_pages %} será limitado. +## Limitations for {% data variables.product.prodname_emus %} +If you're a {% data variables.enterprise.prodname_managed_user %}, your use of {% data variables.product.prodname_pages %} is limited. - - Os sites do {% data variables.product.prodname_pages %} só podem ser publicados por meio de repositórios pertencentes a organizações. - - Os sites do {% data variables.product.prodname_pages %} só são visíveis para outros membros da empresa. + - {% data variables.product.prodname_pages %} sites can only be published from repositories owned by organizations. + - {% data variables.product.prodname_pages %} sites are only visible to other members of the enterprise. + - You cannot create an organization site (a site published from a repository named `.github.io`) -Para obter mais informações sobre o {% data variables.product.prodname_emus %}, confira "[Sobre o {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)". +For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)." {% endif %} -## Geradores de site estáticos +## Static site generators -O {% data variables.product.prodname_pages %} publica qualquer arquivo estático do qual você faz push no repositório. É possível criar seus próprios arquivos estáticos ou usar um gerador de site estático para que ele crie o site para você. Também pode personalizar seu próprio processo de criação localmente ou em outro servidor. +{% data variables.product.prodname_pages %} publishes any static files that you push to your repository. You can create your own static files or use a static site generator to build your site for you. You can also customize your own build process locally or on another server. {% ifversion pages-custom-workflow %} -Se você usar um processo de build ou um gerador de site estático diferente do Jekyll, poderá escrever um {% data variables.product.prodname_actions %} para criar e publicar seu site. {% data variables.product.product_name %} oferece fluxos de trabalho iniciais para vários geradores de site estático. Para obter mais informações, confira "[Como configurar uma fonte de publicação para o seu site do GitHub Pages](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." +If you use a custom build process or a static site generator other than Jekyll, you can write a {% data variables.product.prodname_actions %} to build and publish your site. {% data variables.product.product_name %} provides starter workflows for several static site generators. For more information, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." -Se você publicar seu site de um branch de origem, {% data variables.product.prodname_pages %} usará o Jekyll para criar seu site por padrão. Se você quiser usar um gerador de site estático diferente do Jekyll, recomendamos que você escreva um {% data variables.product.prodname_actions %} para criar e publicar seu site. Caso contrário, desabilite o processo de build do Jekyll criando um arquivo vazio chamado `.nojekyll` na raiz da fonte de publicação e siga as instruções do gerador de site estático para compilar seu site localmente. +If you publish your site from a source branch, {% data variables.product.prodname_pages %} will use Jekyll to build your site by default. If you want to use a static site generator other than Jekyll, we recommend that you write a {% data variables.product.prodname_actions %} to build and publish your site instead. Otherwise, disable the Jekyll build process by creating an empty file called `.nojekyll` in the root of your publishing source, then follow your static site generator's instructions to build your site locally. {% else %} -É recomendável usar o Jekyll, um gerador de site estático com suporte integrado para {% data variables.product.prodname_pages %} e um processo de compilação simplificado. Para obter mais informações, confira "[Sobre o {% data variables.product.prodname_pages %} e o Jekyll](/articles/about-github-pages-and-jekyll)". +We recommend Jekyll, a static site generator with built-in support for {% data variables.product.prodname_pages %} and a simplified build process. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)." -O {% data variables.product.prodname_pages %} usará o Jekyll para criar seu site por padrão. Caso deseje usar um gerador de site estático que não seja o Jekyll, desabilite o processo de build do Jekyll criando um arquivo vazio chamado `.nojekyll` na raiz da fonte de publicação e siga as instruções do gerador de site estático para compilar seu site localmente. +{% data variables.product.prodname_pages %} will use Jekyll to build your site by default. If you want to use a static site generator other than Jekyll, disable the Jekyll build process by creating an empty file called `.nojekyll` in the root of your publishing source, then follow your static site generator's instructions to build your site locally. {% endif %} -O {% data variables.product.prodname_pages %} não aceita linguagens de servidor como PHP, Ruby ou Python. +{% data variables.product.prodname_pages %} does not support server-side languages such as PHP, Ruby, or Python. -## Limites para o uso de {% data variables.product.prodname_pages %} +## Limits on use of {% data variables.product.prodname_pages %} -{% ifversion fpt or ghec %} Os sites do {% data variables.product.prodname_pages %} criados após 15 de junho de 2016 e que usam os domínios `github.io` são disponibilizados via HTTPS. Se você criou seu site ante de 15 de junho de 2016, é possível habilitar o suporte ao HTTPS para tráfego no seu site. Para obter mais informações, confira "[Como proteger o {% data variables.product.prodname_pages %} com HTTPS](/articles/securing-your-github-pages-site-with-https)". - -### Usos proibidos -{% endif %} O {% data variables.product.prodname_pages %} não foi projetado nem tem permissão para ser usado como um serviço de hospedagem gratuita na Web para administrar sua empresa online, seu site de comércio eletrônico ou qualquer outro site desenvolvido principalmente para facilitar transações comerciais ou fornecer SaaS (software como serviço) comercial. {% data reusables.pages.no_sensitive_data_pages %} - -Além disso, seu uso do {% data variables.product.prodname_pages %} está sujeito aos [Termos de Serviço do GitHub](/free-pro-team@latest/github/site-policy/github-terms-of-service/), incluindo as restrições relativas a esquemas do tipo "enriqueça rápido", conteúdo sexualmente obsceno e atividade ou conteúdo violento ou ameaçador. - -### Limites de uso -Os sites do {% data variables.product.prodname_pages %} estão sujeitos ao seguintes limites de uso: - - - Os repositórios de origem do {% data variables.product.prodname_pages %} têm um limite recomendado de 1 GB.{% ifversion fpt or ghec %} Para obter mais informações, confira "[Qual é a minha cota de disco?](/articles/what-is-my-disk-quota/#file-and-repository-size-limitations)"{% endif %} - - Os sites do {% data variables.product.prodname_pages %} publicados não podem ter mais de 1 GB. {% ifversion fpt or ghec %} - - Os sites do {% data variables.product.prodname_pages %} têm um limite de largura de banda *flexível* de 100 GB por mês. - - Os sites do {% data variables.product.prodname_pages %} têm um limite *flexível* de 10 builds por hora.{% ifversion pages-custom-workflow %} Esse limite não se aplica se você cria e publica seu site com um fluxo de trabalho personalizado de {% data variables.product.prodname_actions %} {% endif %} - - Para fornecer qualidade de serviço consistente para todos os sites {% data variables.product.prodname_pages %}, limites de taxa podem ser aplicados. Esses limites de taxa não se destinam a interferir nos usos legítimos de {% data variables.product.prodname_pages %}. Se a sua solicitação disparar a limitação de taxa, você receberá uma resposta apropriada com um código de status HTTP de `429`, juntamente com um corpo HTML informativo. +{% data variables.product.prodname_pages %} sites created after June 15, 2016, and using `github.io` domains are served over HTTPS. If you created your site before June 15, 2016, you can enable HTTPS support for traffic to your site. For more information, see "[Securing your {% data variables.product.prodname_pages %} with HTTPS](/articles/securing-your-github-pages-site-with-https)." -Se o seu site exceder essas cotas de uso, talvez não possamos atender a ele ou você receba um e-mail formal do {% data variables.contact.contact_support %} sugerindo estratégias para reduzir o impacto do site em nossos servidores, como colocar uma rede de distribuição de conteúdo (CDN, Content Distribution Network) de terceiros na frente do site, usar outros recursos do {% data variables.product.prodname_dotcom %}, como versões, ou migrar para outro serviço de hospedagem que possa atender melhor às suas necessidades. +### Prohibited uses +{% endif %} +{% data variables.product.prodname_pages %} is not intended for or allowed to be used as a free web-hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS). {% data reusables.pages.no_sensitive_data_pages %} + +In addition, your use of {% data variables.product.prodname_pages %} is subject to the [GitHub Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service/), including the restrictions on get-rich-quick schemes, sexually obscene content, and violent or threatening content or activity. + +### Usage limits +{% data variables.product.prodname_pages %} sites are subject to the following usage limits: + + - {% data variables.product.prodname_pages %} source repositories have a recommended limit of 1 GB.{% ifversion fpt or ghec %} For more information, see "[What is my disk quota?](/articles/what-is-my-disk-quota/#file-and-repository-size-limitations)"{% endif %} + - Published {% data variables.product.prodname_pages %} sites may be no larger than 1 GB. +{% ifversion fpt or ghec %} + - {% data variables.product.prodname_pages %} sites have a *soft* bandwidth limit of 100 GB per month. + - {% data variables.product.prodname_pages %} sites have a *soft* limit of 10 builds per hour.{% ifversion pages-custom-workflow %} This limit does not apply if you build and publish your site with a custom {% data variables.product.prodname_actions %} workflow {% endif %} + - In order to provide consistent quality of service for all {% data variables.product.prodname_pages %} sites, rate limits may apply. These rate limits are not intended to interfere with legitimate uses of {% data variables.product.prodname_pages %}. If your request triggers rate limiting, you will receive an appropriate response with an HTTP status code of `429`, along with an informative HTML body. + +If your site exceeds these usage quotas, we may not be able to serve your site, or you may receive a polite email from {% data variables.contact.contact_support %} suggesting strategies for reducing your site's impact on our servers, including putting a third-party content distribution network (CDN) in front of your site, making use of other {% data variables.product.prodname_dotcom %} features such as releases, or moving to a different hosting service that might better fit your needs. {% endif %} -## Tipos de MIME no {% data variables.product.prodname_pages %} +## MIME types on {% data variables.product.prodname_pages %} -Um tipo de MIME é um header que um servidor envia a um navegador, fornecendo informações sobre a natureza e o formato dos arquivos que o navegador solicitou. O {% data variables.product.prodname_pages %} aceita mais de 750 tipos de MIME entre milhares de extensões de arquivo. A lista de tipos MIME compatíveis é gerada com base no [projeto mime-db](https://github.com/jshttp/mime-db). +A MIME type is a header that a server sends to a browser, providing information about the nature and format of the files the browser requested. {% data variables.product.prodname_pages %} supports more than 750 MIME types across thousands of file extensions. The list of supported MIME types is generated from the [mime-db project](https://github.com/jshttp/mime-db). -Embora não seja possível especificar tipos de MIME personalizados por arquivo ou repositório, você pode adicionar ou modificar tipos de MIME para uso no {% data variables.product.prodname_pages %}. Para obter mais informações, confira [as diretrizes de contribuição do mime-db](https://github.com/jshttp/mime-db#adding-custom-media-types). +While you can't specify custom MIME types on a per-file or per-repository basis, you can add or modify MIME types for use on {% data variables.product.prodname_pages %}. For more information, see [the mime-db contributing guidelines](https://github.com/jshttp/mime-db#adding-custom-media-types). {% ifversion fpt %} -## Coleta de dados +## Data collection -Quando um site de {% data variables.product.prodname_pages %} é acessado, o endereço IP do visitante é registrado e armazenado para fins de segurança, independentemente se o visitante efetuou o login em {% data variables.product.prodname_dotcom %} ou não. Para obter mais informações sobre as práticas de segurança do {% data variables.product.prodname_dotcom %}, confira Política de Privacidade do {% data variables.product.prodname_dotcom %}. +When a {% data variables.product.prodname_pages %} site is visited, the visitor's IP address is logged and stored for security purposes, regardless of whether the visitor has signed into {% data variables.product.prodname_dotcom %} or not. For more information about {% data variables.product.prodname_dotcom %}'s security practices, see {% data variables.product.prodname_dotcom %} Privacy Statement. {% endif %} -## Leitura adicional +## Further reading -- [{% data variables.product.prodname_pages %}](https://github.com/skills/github-pages) no {% data variables.product.prodname_learning %} +- [{% data variables.product.prodname_pages %}](https://github.com/skills/github-pages) on {% data variables.product.prodname_learning %} - "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)" diff --git a/translations/pt-BR/content/pages/index.md b/translations/pt-BR/content/pages/index.md index 8df8e43dc0..5c8d0c692f 100644 --- a/translations/pt-BR/content/pages/index.md +++ b/translations/pt-BR/content/pages/index.md @@ -1,7 +1,7 @@ --- -title: Documentação do GitHub Pages +title: GitHub Pages Documentation shortTitle: GitHub Pages -intro: 'Aprenda a criar um site diretamente de um repositório no {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Explore ferramentas de criação de sites como o Jekyll e solucione problemas com o site do {% data variables.product.prodname_pages %}.' +intro: 'Learn how to create a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. Explore website building tools like Jekyll and troubleshoot issues with your {% data variables.product.prodname_pages %} site.' introLinks: quickstart: /pages/quickstart overview: /pages/getting-started-with-github-pages/about-github-pages @@ -49,11 +49,4 @@ children: - /getting-started-with-github-pages - /setting-up-a-github-pages-site-with-jekyll - /configuring-a-custom-domain-for-your-github-pages-site -ms.openlocfilehash: 8f1e83a8329a023f49a73a3716a88f61b2438adb -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147643922' --- - diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md index 12d804f41a..389f6ada15 100644 --- a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md +++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md @@ -1,6 +1,6 @@ --- -title: Criar um site do GitHub Pages com o Jekyll -intro: 'É possível usar o Jekyll para criar um site do {% data variables.product.prodname_pages %} em um repositório novo ou existente.' +title: Creating a GitHub Pages site with Jekyll +intro: 'You can use Jekyll to create a {% data variables.product.prodname_pages %} site in a new or existing repository.' product: '{% data reusables.gated-features.pages %}' redirect_from: - /articles/creating-a-github-pages-site-with-jekyll @@ -14,112 +14,119 @@ versions: topics: - Pages shortTitle: Create site with Jekyll -ms.openlocfilehash: 409b2d1e21f89471e7ad92f790bc7ac67e903a62 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145127619' --- + {% data reusables.pages.org-owners-can-restrict-pages-creation %} -## Pré-requisitos +## Prerequisites -Antes de poder usar o Jekyll para criar um site do {% data variables.product.prodname_pages %}, você precisa instalar o Jekyll e o Git. Para obter mais informações, confira [Instalação](https://jekyllrb.com/docs/installation/) na documentação do Jekyll e "[Configurar o Git](/articles/set-up-git)". +Before you can use Jekyll to create a {% data variables.product.prodname_pages %} site, you must install Jekyll and Git. For more information, see [Installation](https://jekyllrb.com/docs/installation/) in the Jekyll documentation and "[Set up Git](/articles/set-up-git)." {% data reusables.pages.recommend-bundler %} {% data reusables.pages.jekyll-install-troubleshooting %} -## Criar um repositório para seu site +## Creating a repository for your site {% data reusables.pages.new-or-existing-repo %} -{% data reusables.repositories.create_new %} {% data reusables.repositories.owner-drop-down %} {% indented_data_reference reusables.pages.emu-org-only spaces=3 %} {% data reusables.pages.create-repo-name %} {% data reusables.repositories.choose-repo-visibility %} +{% data reusables.repositories.create_new %} +{% data reusables.repositories.owner-drop-down %} +{% indented_data_reference reusables.pages.emu-org-only spaces=3 %} +{% data reusables.pages.create-repo-name %} +{% data reusables.repositories.choose-repo-visibility %} -## Criar seu site +## Creating your site {% data reusables.pages.must-have-repo-first %} {% data reusables.pages.private_pages_are_public_warning %} {% data reusables.command_line.open_the_multi_os_terminal %} -1. Se você ainda não tem uma cópia do seu repositório, procure o local em que deseja armazenar os arquivos de origem do seu site, substituindo _PARENT-FOLDER_ pela pasta que deverá conter a pasta do repositório. +1. If you don't already have a local copy of your repository, navigate to the location where you want to store your site's source files, replacing _PARENT-FOLDER_ with the folder you want to contain the folder for your repository. ```shell - $ cd PARENT-FOLDER + $ cd PARENT-FOLDER ``` -1. Caso você ainda não tenha feito isso, inicialize um repositório Git local, substituindo _REPOSITORY-NAME_ pelo nome do seu repositório. +1. If you haven't already, initialize a local Git repository, replacing _REPOSITORY-NAME_ with the name of your repository. ```shell - $ git init REPOSITORY-NAME + $ git init REPOSITORY-NAME > Initialized empty Git repository in /Users/octocat/my-site/.git/ # Creates a new folder on your computer, initialized as a Git repository ``` - 4. Altere os diretórios no repositório. + 4. Change directories to the repository. ```shell - $ cd REPOSITORY-NAME + $ cd REPOSITORY-NAME # Changes the working directory ``` -{% data reusables.pages.decide-publishing-source %} {% data reusables.pages.navigate-publishing-source %} Por exemplo, se você optar por publicar seu site por meio da pasta `docs` no branch padrão, crie e altere os diretórios para a pasta `docs`. +{% data reusables.pages.decide-publishing-source %} +{% data reusables.pages.navigate-publishing-source %} + For example, if you chose to publish your site from the `docs` folder on the default branch, create and change directories to the `docs` folder. ```shell $ mkdir docs # Creates a new folder called docs $ cd docs ``` - Se você optar por publicar seu site no branch `gh-pages`, crie o branch `gh-pages` e faça check-out dele. + If you chose to publish your site from the `gh-pages` branch, create and checkout the `gh-pages` branch. ```shell $ git checkout --orphan gh-pages # Creates a new branch, with no history or contents, called gh-pages, and switches to the gh-pages branch - $ git rm -rf + $ git rm -rf . # Removes the contents from your default branch from the working directory ``` -1. Para criar um site do Jekyll, use o comando `jekyll new`: +1. To create a new Jekyll site, use the `jekyll new` command: ```shell $ jekyll new --skip-bundle . # Creates a Jekyll site in the current directory ``` -1. Abra o Gemfile que o Jekyll criou. -1. Adicione "#" ao início da linha que começa com `gem "jekyll"` para remover o comentário dessa linha. -1. Adicione o gem `github-pages` editando a linha que começa com `# gem "github-pages"`. Mudar esta linha para: +1. Open the Gemfile that Jekyll created. +1. Add "#" to the beginning of the line that starts with `gem "jekyll"` to comment out this line. +1. Add the `github-pages` gem by editing the line starting with `# gem "github-pages"`. Change this line to: ```shell gem "github-pages", "~> GITHUB-PAGES-VERSION", group: :jekyll_plugins ``` - Substitua _GITHUB-PAGES-VERSION_ pela última versão compatível do gem `github-pages`. Encontre esta versão aqui: "[Versões de dependência](https://pages.github.com/versions/)". + Replace _GITHUB-PAGES-VERSION_ with the latest supported version of the `github-pages` gem. You can find this version here: "[Dependency versions](https://pages.github.com/versions/)." - A versão correta do Jekyll será instalada como uma dependência do gem `github-pages`. -1. Salve e feche o Gemfile. -1. Da linha de comando, execute `bundle install`. -1. Opcionalmente, faça as edições necessárias no arquivo `_config.yml`. Isto é necessário para caminhos relativos quando o repositório é hospedado em um subdiretório. Para obter mais informações, confira "[Como dividir uma subpasta em um novo repositório](/github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository)". + The correct version Jekyll will be installed as a dependency of the `github-pages` gem. +1. Save and close the Gemfile. +1. From the command line, run `bundle install`. +1. Optionally, make any necessary edits to the `_config.yml` file. This is required for relative paths when the repository is hosted in a subdirectory. For more information, see "[Splitting a subfolder out into a new repository](/github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository)." ```yml domain: my-site.github.io # if you want to force HTTPS, specify the domain without the http at the start, e.g. example.com url: https://my-site.github.io # the base hostname and protocol for your site, e.g. http://example.com baseurl: /REPOSITORY-NAME/ # place folder name if the site is served in a subfolder ``` -1. Como alternativa, teste seu site localmente. Para obter mais informações, confira "[Como testar seu site do {% data variables.product.prodname_pages %} localmente com o Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)". -1. Adicione e faça commit do seu trabalho. +1. Optionally, test your site locally. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)." +1. Add and commit your work. ```shell git add . git commit -m 'Initial GitHub pages site with Jekyll' ``` -1. Adicione seu repositório no {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} como um repositório remoto, substituindo {% ifversion ghes or ghae %}_HOSTNAME_ pelo nome do host da sua empresa,{% endif %} _USER_ pela conta à qual o repositório pertence{% ifversion ghes or ghae %},{% endif %} e _REPOSITORY_ pelo nome do repositório. +1. Add your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} as a remote, replacing {% ifversion ghes or ghae %}_HOSTNAME_ with your enterprise's hostname,{% endif %} _USER_ with the account that owns the repository{% ifversion ghes or ghae %},{% endif %} and _REPOSITORY_ with the name of the repository. ```shell {% ifversion fpt or ghec %} -$ git remote add origin https://github.com/USER/REPOSITORY.git +$ git remote add origin https://github.com/USER/REPOSITORY.git {% else %} -$ git remote add origin https://HOSTNAME/USER/REPOSITORY.git +$ git remote add origin https://HOSTNAME/USER/REPOSITORY.git {% endif %} ``` -1. Faça push no repositório para o {% data variables.product.product_name %}, substituindo _BRANCH_ pelo nome do branch em que você está trabalhando. +1. Push the repository to {% data variables.product.product_name %}, replacing _BRANCH_ with the name of the branch you're working on. ```shell - $ git push -u origin BRANCH + $ git push -u origin BRANCH ``` -{% data reusables.pages.configure-publishing-source %} {% data reusables.pages.navigate-site-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %} {% data reusables.pages.choose-visibility %} {% data reusables.pages.visit-site %} {% data reusables.pages.check-workflow-run %} +{% data reusables.pages.configure-publishing-source %} +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +{% data reusables.pages.choose-visibility %} +{% data reusables.pages.visit-site %} +{% data reusables.pages.check-workflow-run %} {% data reusables.pages.admin-must-push %} -## Próximas etapas +## Next steps -Para adicionar uma nova página ou postagem ao seu site, confira "[Como adicionar conteúdo ao seu site do {% data variables.product.prodname_pages %} usando o Jekyll](/articles/adding-content-to-your-github-pages-site-using-jekyll)". +To add a new page or post to your site, see "[Adding content to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-content-to-your-github-pages-site-using-jekyll)." -{% data reusables.pages.add-jekyll-theme %} Para obter mais informações, confira "[Como adicionar um tema ao seu site do {% data variables.product.prodname_pages %} usando o Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)". +{% data reusables.pages.add-jekyll-theme %} For more information, see "[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)." diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md index f701c92f63..32c3ec760b 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md @@ -1,6 +1,6 @@ --- -title: Sobre merges de pull request -intro: 'Você pode [mesclar solicitações de pull](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request) mantendo todos os commits em um branch de recurso, combinando todos os commits em um único commit ou realocando commits individuais do branch `head` no branch `base`.' +title: About pull request merges +intro: 'You can [merge pull requests](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request) by retaining all the commits in a feature branch, squashing all commits into a single commit, or by rebasing individual commits from the `head` branch onto the `base` branch.' redirect_from: - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges - /articles/about-pull-request-merge-squashing @@ -14,67 +14,77 @@ versions: ghec: '*' topics: - Pull requests -ms.openlocfilehash: 512a32eb3f918653eab1127aecb70a2fbc220571 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147580436' --- -## Mesclar seus commits +## Merge your commits {% data reusables.pull_requests.default_merge_option %} -## Combinação por squash e mesclagem de commits +## Squash and merge your commits {% data reusables.pull_requests.squash_and_merge_summary %} -### Mesclar mensagem para uma mesclagem por squash +### Merge message for a squash merge -{% ifversion default-merge-squash-commit-message %} Quando você faz combinação por squash e mesclagem, o {% data variables.product.prodname_dotcom %} gera uma mensagem de commit padrão, que você pode editar. Dependendo de como o repositório está configurado e do número de commits na solicitação de pull, não incluindo commits de mesclagem, essa mensagem pode incluir o título ou a descrição da solicitação de pull ou informações sobre os commits. -{% else %} Quando você faz combinação por squash e mesclagem, o {% data variables.product.prodname_dotcom %} gera uma mensagem de commit padrão, que você pode editar. A mensagem padrão depende do número de commits na solicitação de pull, não incluindo os commits de mesclagem. +{% ifversion default-merge-squash-commit-message %} +When you squash and merge, {% data variables.product.prodname_dotcom %} generates a default commit message, which you can edit. Depending on how the repository is configured and the number of commits in the pull request, not including merge commits, this message may include the pull request title, pull request description, or information about the commits. +{% else %} +When you squash and merge, {% data variables.product.prodname_dotcom %} generates a default commit message, which you can edit. The default message depends on the number of commits in the pull request, not including merge commits. -Número de commits | Resumo | Descrição | ------------------ | ------- | ----------- | -Um commit | O título da mensagem de commit do único commit, seguido do número de pull request | O texto da mensagem de commit para o único commit -Mais de um commit | Título da pull request, seguido do número da pull request | Uma lista das mensagens de commit para todos os commits combinados por squash, por ordem de data +Number of commits | Summary | Description | +----------------- | ------- | ----------- | +One commit | The title of the commit message for the single commit, followed by the pull request number | The body text of the commit message for the single commit +More than one commit | The pull request title, followed by the pull request number | A list of the commit messages for all of the squashed commits, in date order {% endif %} -Número de commits | Resumo | Descrição | +Number of commits | Summary | Description | ----------------- | ------- | ----------- | -Um commit | O título da mensagem de commit do único commit, seguido do número de pull request | O texto da mensagem de commit para o único commit -Mais de um commit | Título da pull request, seguido do número da pull request | Uma lista das mensagens de commit para todos os commits combinados por squash, por ordem de data +One commit | The title of the commit message for the single commit, followed by the pull request number | The body text of the commit message for the single commit +More than one commit | The pull request title, followed by the pull request number | A list of the commit messages for all of the squashed commits, in date order -{% ifversion default-merge-squash-commit-message %} Pessoas com acesso de mantenedor ou administrador a um repositório podem configurar a mensagem de mesclagem padrão de seu repositório para todos os commits com combinação por squash de modo a usar o título da solicitação de pull, o título do solicitação de pull e os detalhes do commit, ou o título e a descrição da solicitação de pull. Para obter mais informações, veja "[Configurar a combinação por squash do commit](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)".{% endif %} +{% ifversion default-merge-squash-commit-message %} +People with maintainer or admin access to a repository can configure their repository's default merge message for all squashed commits to use the pull request title, the pull request title and commit details, or the pull request title and description. For more information, see "[Configure commit squashing](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)".{% endif %} -{% ifversion ghes = 3.6 %} Pessoas com acesso de administrador a um repositório podem configurar o repositório para usar o título da solicitação de pull como a mensagem de mesclagem padrão para todos os commits combinados por squash. Para obter mais informações, veja "[Configurar o squashing de commit](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)". +{% ifversion ghes = 3.6 %} +People with admin access to a repository can configure the repository to use the title of the pull request as the default merge message for all squashed commits. For more information, see "[Configure commit squashing](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)". {% endif %} -### Fazendo combinação por squash e merge com um branch de longa duração +### Squashing and merging a long-running branch -Se você pretende continuar o trabalho no [branch principal](/github/getting-started-with-github/github-glossary#head-branch) de uma solicitação de pull depois que a solicitação de pull for mesclada, recomendamos que você não use a mesclagem squash nem mescle a solicitação de pull. +If you plan to continue work on the [head branch](/github/getting-started-with-github/github-glossary#head-branch) of a pull request after the pull request is merged, we recommend you don't squash and merge the pull request. -Quando você cria uma solicitação de pull, o {% data variables.product.prodname_dotcom %} identifica o commit mais recente que está no branch principal e no [branch base](/github/getting-started-with-github/github-glossary#base-branch): o commit ancestral comum. Quando você combinar por squash e mesclar a pull request, o {% data variables.product.prodname_dotcom %} cria um commit no branch base que contém todas as alterações feitas no branch head desde o commit de ancestral comum. +When you create a pull request, {% data variables.product.prodname_dotcom %} identifies the most recent commit that is on both the head branch and the [base branch](/github/getting-started-with-github/github-glossary#base-branch): the common ancestor commit. When you squash and merge the pull request, {% data variables.product.prodname_dotcom %} creates a commit on the base branch that contains all of the changes you made on the head branch since the common ancestor commit. -Uma vez que esse commit está apenas no branch base e não no branch head, o ancestral comum dos dois branches permanece inalterado. Se você continuar a trabalhar no branch head e, em seguida, criar uma nova pull request entre os dois branches, a pull request incluirá todos os commits desde o ancestral comum, incluindo commits que você combinou por squash e fez merge na pull request anterior. Se não houver conflitos, você pode mesclar esses commits com segurança. No entanto, este fluxo de trabalho torna os conflitos de mesclagem mais prováveis. Se você continuar a combinar por squash e mesclar pull requests para um branch head de longo prazo, você terá que resolver os mesmos conflitos repetidamente. +Because this commit is only on the base branch and not the head branch, the common ancestor of the two branches remains unchanged. If you continue to work on the head branch, then create a new pull request between the two branches, the pull request will include all of the commits since the common ancestor, including commits that you squashed and merged in the previous pull request. If there are no conflicts, you can safely merge these commits. However, this workflow makes merge conflicts more likely. If you continue to squash and merge pull requests for a long-running head branch, you will have to resolve the same conflicts repeatedly. -## Troca de base e mesclagem de commits +## Rebase and merge your commits {% data reusables.pull_requests.rebase_and_merge_summary %} -Você não pode fazer rebase e merge automaticamente no {% data variables.product.product_location %} quando: -- A pull request tem conflitos de merge. -- O rebase dos commits do branch base no branch head se depara com conflitos. -- O rebase dos commits é considerado "não seguro"; por exemplo, quando é possível fazer rebase sem conflitos de merge, mas que geraria um resultado diferente daquele que um merge geraria. +You aren't able to automatically rebase and merge on {% data variables.location.product_location %} when: +- The pull request has merge conflicts. +- Rebasing the commits from the base branch into the head branch runs into conflicts. +- Rebasing the commits is considered "unsafe," such as when a rebase is possible without merge conflicts but would produce a different result than a merge would. -Se ainda quiser fazer rebase dos commits, mas não puder fazer rebase e merge automaticamente no {% data variables.product.product_location %}, você deverá: -- Fazer rebase do branch de tópico (ou branch head) no branch base localmente na linha de comando -- [Resolva todos os conflitos de mesclagem na linha de comando](/articles/resolving-a-merge-conflict-using-the-command-line/). -- Forçar push dos commits com rebase no branch de tópico da pull request (ou branch head remoto). +If you still want to rebase the commits but can't rebase and merge automatically on {% data variables.location.product_location %} you must: +- Rebase the topic branch (or head branch) onto the base branch locally on the command line +- [Resolve any merge conflicts on the command line](/articles/resolving-a-merge-conflict-using-the-command-line/). +- Force-push the rebased commits to the pull request's topic branch (or remote head branch). -Qualquer pessoa com permissões de gravação no repositório pode [mesclar as alterações](/articles/merging-a-pull-request/) usando o botão Trocar base e mesclar do {% data variables.product.product_location %}. +Anyone with write permissions in the repository, can then [merge the changes](/articles/merging-a-pull-request/) using the rebase and merge button on {% data variables.location.product_location %}. -## Leitura adicional +## Indirect merges -- "[Sobre as solicitações de pull](/articles/about-pull-requests/)" -- "[Como resolver conflitos de mesclagem](/github/collaborating-with-pull-requests/addressing-merge-conflicts)" +A pull request can be merged automatically if its head branch is directly or indirectly merged into the base branch externally. In other words, if the head branch's tip commit becomes reachable from the tip of the target branch. For example: + +* Branch `main` is at commit **C**. +* Branch `feature` has been branched off of `main` and is currently at commit **D**. This branch has a pull request targeting `main`. +* Branch `feature_2` is branched off of `feature` and is now at commit **E**. This branch also has a pull request targeting `main`. + +If pull request **E** --> `main` is merged first, pull request **D** --> `main` will be marked as merged *automatically* because all of the commits from `feature` are now reachable from `main`. Merging `feature_2` into `main` and pushing `main` to the server from the command line will mark *both* pull requests as merged. + +Pull requests in this situation will be marked as `merged` even if [branch protection rules](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-rules) have not been satisfied. + +## Further reading + +- "[About pull requests](/articles/about-pull-requests/)" +- "[Addressing merge conflicts](/github/collaborating-with-pull-requests/addressing-merge-conflicts)" diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md index 2419bf0f8e..3d3b8216ae 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md @@ -1,6 +1,6 @@ --- -title: Fazer commit de alterações em um branch de pull request criado a partir de bifurcação -intro: Você pode fazer commit de alterações no branch de uma pull request que foi criada de uma bifurcação no seu repositório com permissão do criador da pull request. +title: Committing changes to a pull request branch created from a fork +intro: You can commit changes on a pull request branch that was created from a fork of your repository with permission from the pull request creator. redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork - /articles/committing-changes-to-a-pull-request-branch-created-from-a-fork @@ -14,44 +14,40 @@ versions: topics: - Pull requests shortTitle: Commit to PR branch from fork -ms.openlocfilehash: 123775ecbcc199382fe2082f22ad04db21fb9661 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145127580' --- -Só é possível fazer commits em branches da pull request que: -- esteja aberta em um repositório em que você tem acesso push e que foi criada de uma bifurcação desse repositório -- estão em uma bifurcação de propriedade do usuário -- tiver permissão concedida pelo criador da pull request -- não têm [restrições de branch](/github/administering-a-repository/about-protected-branches#restrict-who-can-push-to-matching-branches) que impedirão você de fazer commit +You can only make commits on pull request branches that: +- are opened in a repository that you have push access to and that were created from a fork of that repository +- are on a user-owned fork +- have permission granted from the pull request creator +- don't have [branch restrictions](/github/administering-a-repository/about-protected-branches#restrict-who-can-push-to-matching-branches) that will prevent you from committing -Somente o usuário que criou a pull request pode dar a você permissão para fazer push de commits na bifurcação de propriedade do usuário. Para obter mais informações, confira "[Como permitir alterações em um branch de solicitação de pull criado com base em um fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)". +Only the user who created the pull request can give you permission to push commits to the user-owned fork. For more information, see "[Allowing changes to a pull request branch created from a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)." {% note %} -**Observação:** você também pode fazer commits em um branch de solicitação de pull por meio de um fork do repositório com o {% data variables.product.product_location %} criando sua cópia (ou um fork) do fork do repositório e fazendo commit das alterações no mesmo branch principal no qual as alterações de solicitação de pull originais foram criadas. Para obter algumas diretrizes gerais, confira "[Como criar uma solicitação de pull por meio de um fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)". +**Note:** You can also make commits to a pull request branch from a fork of your repository through {% data variables.location.product_location %} by creating your own copy (or fork) of the fork of your repository and committing changes to the same head branch that the original pull request changes were created on. For some general guidelines, see "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)." {% endnote %} -1. No {% data variables.product.product_name %}, navegue até a página principal da bifurcação (ou cópia do repositório) onde o branch da pull request foi criado. -{% data reusables.repositories.copy-clone-url %} {% data reusables.command_line.open_the_multi_os_terminal %} {% tip %} +1. On {% data variables.product.product_name %}, navigate to the main page of the fork (or copy of your repository) where the pull request branch was created. +{% data reusables.repositories.copy-clone-url %} +{% data reusables.command_line.open_the_multi_os_terminal %} + {% tip %} - **Dica:** se preferir clonar o fork usando o {% data variables.product.prodname_desktop %}, confira "[Como clonar um repositório para o {% data variables.product.prodname_desktop %}](/articles/cloning-a-repository/#cloning-a-repository-to-github-desktop)". + **Tip:** If you prefer to clone the fork using {% data variables.product.prodname_desktop %}, then see "[Cloning a repository to {% data variables.product.prodname_desktop %}](/articles/cloning-a-repository/#cloning-a-repository-to-github-desktop)." {% endtip %} -4. Altere o diretório de trabalho atual para o local em que deseja baixar o diretório clonado. +4. Change the current working directory to the location where you want to download the cloned directory. ```shell $ cd open-source-projects ``` -5. Digite `git clone` e cole a URL copiada na Etapa 3. +5. Type `git clone`, and then paste the URL you copied in Step 3. ```shell - $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY + $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY ``` -6. Pressione **Enter**. Seu clone local estará criado. +6. Press **Enter**. Your local clone will be created. ```shell - $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY + $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY > Cloning into `FORK-OF-THE-REPOSITORY`... > remote: Counting objects: 10, done. > remote: Compressing objects: 100% (8/8), done. @@ -60,26 +56,27 @@ Somente o usuário que criou a pull request pode dar a você permissão para faz ``` {% tip %} - **Dica:** a mensagem de erro "fatal: o caminho de destino 'REPOSITORY-NAME' já existe e não é um diretório vazio" significa que o diretório de trabalho atual já contém um repositório com o mesmo nome. Para resolver o erro, você deve clonar a bifurcação em outro diretório. + **Tip:** The error message "fatal: destination path 'REPOSITORY-NAME' already exists and is not an empty directory" means that your current working directory already contains a repository with the same name. To resolve the error, you must clone the fork in a different directory. {% endtip %} -7. Navegue para o seu novo repositório clonado. +7. Navigate into your new cloned repository. ```shell - $ cd FORK-OF-THE-REPOSITORY + $ cd FORK-OF-THE-REPOSITORY ``` -7. Alterne branches para o branch de comparação da pull request onde as alterações originais foram feitas. Se você navegar até a pull request original, visualizará o branch de comparação no topo da pull request. -![compare-branch-example](/assets/images/help/pull_requests/compare-branch-example.png) Neste exemplo, o branch de comparação é `test-branch`: +7. Switch branches to the compare branch of the pull request where the original changes were made. If you navigate to the original pull request, you'll see the compare branch at the top of the pull request. +![compare-branch-example](/assets/images/help/pull_requests/compare-branch-example.png) + In this example, the compare branch is `test-branch`: ```shell - $ git checkout test-branch + $ git checkout TEST-BRANCH ``` {% tip %} - **Dica:** para obter mais informações sobre os branches de solicitação de pull, incluindo exemplos, confira "[Como criar uma solicitação de pull](/articles/creating-a-pull-request#changing-the-branch-range-and-destination-repository)". + **Tip:** For more information about pull request branches, including examples, see "[Creating a Pull Request](/articles/creating-a-pull-request#changing-the-branch-range-and-destination-repository)." {% endtip %} -8. Nesse ponto, você pode fazer qualquer coisa que desejar com este branch. É possível fazer push de novos commits para ele, executar alguns testes locais ou fazer merge de outros branches no branch. Faça modificações conforme desejado. -9. Depois de fazer commit de suas alterações no branch head da pull request, você pode fazer push de suas alterações até a pull request original diretamente. Neste exemplo, o branch principal é `test-branch`: +8. At this point, you can do anything you want with this branch. You can push new commits to it, run some local tests, or merge other branches into the branch. Make modifications as you like. +9. After you commit your changes to the head branch of the pull request you can push your changes up to the original pull request directly. In this example, the head branch is `test-branch`: ```shell $ git push origin test-branch > Counting objects: 32, done. @@ -87,12 +84,12 @@ Somente o usuário que criou a pull request pode dar a você permissão para faz > Compressing objects: 100% (26/26), done. > Writing objects: 100% (29/29), 74.94 KiB | 0 bytes/s, done. > Total 29 (delta 8), reused 0 (delta 0) - > To https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY.git - > 12da2e9..250e946 test-branch -> test-branch + > To https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY.git + > 12da2e9..250e946 TEST-BRANCH -> TEST-BRANCH ``` -Seus novos commits serão refletidos na pull request original do {% data variables.product.product_location %}. +Your new commits will be reflected on the original pull request on {% data variables.location.product_location %}. -## Leitura Adicional +## Further Reading -- "[Sobre os forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" +- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index ed8a455560..5ecd5f08d3 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -30,7 +30,7 @@ shortTitle: Review dependency changes {% ifversion ghec %}Before you can use dependency review in a private repository, you must enable the dependency graph. For more information, see "[Exploring the dependencies of a repository](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)."{% endif %} -{% ifversion ghes %} Before you can use dependency review, you must enable the dependency graph and connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +{% ifversion ghes %} Before you can use dependency review, you must enable the dependency graph and connect {% data variables.location.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} Dependency review allows you to "shift left". You can use the provided predictive information to catch vulnerable dependencies before they hit production. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md index 4f262f5088..a881dd52d4 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md @@ -1,6 +1,6 @@ --- -title: Sobre bifurcações -intro: Uma bifurcação é uma cópia de um repositório que você gerencia. As bifurcações permitem fazer alterações em um projeto sem afetar o repositório original. Você pode fazer fetch de atualizações no repositório ou enviar alterações ao repositório original com pull requests. +title: About forks +intro: A fork is a copy of a repository that you manage. Forks let you make changes to a project without affecting the original repository. You can fetch updates from or submit changes to the original repository with pull requests. redirect_from: - /github/collaborating-with-issues-and-pull-requests/working-with-forks/about-forks - /articles/about-forks @@ -13,39 +13,33 @@ versions: ghec: '*' topics: - Pull requests -ms.openlocfilehash: d7564598bca7c75a4861f4cc2d20b3f7a986f730 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145128020' --- -Bifurcar um repositório é semelhante a copiar um repositório, com duas grandes diferenças: +Forking a repository is similar to copying a repository, with two major differences: -* Use uma solicitação de pull para sugerir alterações do fork pertencente ao usuário para o repositório original na sua instância do GitHub, também conhecida como repositório *upstream*. -* Você pode transmitir alterações do repositório upstream para a sua bifurcação local sincronizando a bifurcação com o repositório upstream. +* You can use a pull request to suggest changes from your user-owned fork to the original repository in its GitHub instance, also known as the *upstream* repository. +* You can bring changes from the upstream repository to your local fork by synchronizing your fork with the upstream repository. {% data reusables.repositories.you-can-fork %} {% ifversion fpt or ghec %} -Se você for um integrante de um {% data variables.product.prodname_emu_enterprise %}, existem outras restrições nos repositórios que você pode bifurcar. {% data reusables.enterprise-accounts.emu-forks %} Para obter mais informações, confira "[Sobre os {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" na documentação do {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %} +If you're a member of a {% data variables.enterprise.prodname_emu_enterprise %}, there are further restrictions on the repositories you can fork. {% data reusables.enterprise-accounts.emu-forks %} For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} {% endif %} {% data reusables.repositories.desktop-fork %} -Excluir uma bifurcação não exclui o repositório upstream original. Faça as alterações desejadas no seu fork (adicione colaboradores, renomeie arquivos, gere {% data variables.product.prodname_pages %}) sem nenhum efeito sobre o original.{% ifversion fpt or ghec %} Não é possível restaurar um repositório com fork excluído. Para obter mais informações, confira "[Como restaurar um repositório excluído](/articles/restoring-a-deleted-repository)".{% endif %} +Deleting a fork will not delete the original upstream repository. You can make any changes you want to your fork—add collaborators, rename files, generate {% data variables.product.prodname_pages %}—with no effect on the original.{% ifversion fpt or ghec %} You cannot restore a deleted forked repository. For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %} -Em projetos de código aberto, as bifurcações são usadas com frequência para iterar ideias ou alterações antes que elas sejam oferecidas de volta ao repositório upstream. Ao fazer alterações na bifurcação do usuário e abrir um pull request que compara seu trabalho com o repositório upstream, você pode dar a qualquer pessoa com acesso push à permissão do repositório upstream para fazer push das alterações para seu branch de pull request (incluindo a exclusão do branch). Isso agiliza a colaboração ao permitir que os mantenedores de repositório façam commits ou executem testes localmente em seu branch de pull requests a partir de uma bifurcação de propriedade do usuário antes de fazer merge. Você não pode dar permissões de push a uma bifurcação de propriedade de uma organização. +In open source projects, forks are often used to iterate on ideas or changes before they are offered back to the upstream repository. When you make changes in your user-owned fork and open a pull request that compares your work to the upstream repository, you can give anyone with push access to the upstream repository permission to push changes to your pull request branch (including deleting the branch). This speeds up collaboration by allowing repository maintainers the ability to make commits or run tests locally to your pull request branch from a user-owned fork before merging. You cannot give push permissions to a fork owned by an organization. {% data reusables.repositories.private_forks_inherit_permissions %} -Se você deseja criar um novo repositório a partir do conteúdo de um repositório existente, mas não quer fazer merge das suas alterações no upstream posteriormente, você poderá duplicar o repositório ou, se o repositório for um modelo, você poderá usar o repositório como um modelo. Para obter mais informações, confira "[Como duplicar um repositório](/articles/duplicating-a-repository)" e "[Como criar um repositório com base em um modelo](/articles/creating-a-repository-from-a-template)". +If you want to create a new repository from the contents of an existing repository but don't want to merge your changes to the upstream in the future, you can duplicate the repository or, if the repository is a template, you can use the repository as a template. For more information, see "[Duplicating a repository](/articles/duplicating-a-repository)" and "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)". -## Leitura adicional +## Further reading -- "[Sobre modelos de desenvolvimento colaborativos](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)" -- "[Como criar uma solicitação de pull com base em um fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)" -- [Guias de Código Aberto](https://opensource.guide/){% ifversion fpt or ghec %} +- "[About collaborative development models](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)" +- "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)" +- [Open Source Guides](https://opensource.guide/){% ifversion fpt or ghec %} - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %} diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md index 9744d41f77..d97744b5d7 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md @@ -1,6 +1,6 @@ --- -title: Sincronizar uma bifurcação -intro: Sincronize uma bifurcação de um repositório para mantê-la atualizada com o repositório upstream. +title: Syncing a fork +intro: Sync a fork of a repository to keep it up-to-date with the upstream repository. redirect_from: - /github/collaborating-with-issues-and-pull-requests/working-with-forks/syncing-a-fork - /articles/syncing-a-fork @@ -19,48 +19,44 @@ versions: topics: - Pull requests permissions: People with write access for a forked repository can sync the fork to the upstream repository. -ms.openlocfilehash: 7c4c97c271e6e151c509a33e53c126190e8e5feb -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147540831' --- -## Sincronizar um branch de fork usando a interface do usuário da Web + +## Syncing a fork branch from the web UI {% ifversion syncing-fork-web-ui %} -1. Em {% data variables.product.product_name %}, acesse a página principal do repositório bifurcado que você deseja sincronizar com o repositório upstream. -2. Selecione a lista suspensa **Sincronizar fork**. - ![Menu suspenso "Sincronizar fork" enfatizado](/assets/images/help/repository/sync-fork-dropdown.png) -3. Revise os detalhes sobre os commits do repositório upstream e clique em **Atualizar branch**. - ![Sincronizar o modal do fork com o botão "Atualizar branch" enfatizado](/assets/images/help/repository/update-branch-button.png) {% else %} -1. Em {% data variables.product.product_name %}, acesse a página principal do repositório bifurcado que você deseja sincronizar com o repositório upstream. -2. Selecione o menu suspenso **Buscar upstream**. - ![Menu suspenso "Buscar upstream"](/assets/images/help/repository/fetch-upstream-drop-down.png) -3. Revise os detalhes sobre os commits do repositório upstream e clique em **Buscar e mesclar**. - ![Botão "Buscar e mesclar"](/assets/images/help/repository/fetch-and-merge-button.png){% endif %} +1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository. +2. Select the **Sync fork** dropdown. + !["Sync fork" dropdown emphasized](/assets/images/help/repository/sync-fork-dropdown.png) +3. Review the details about the commits from the upstream repository, then click **Update branch**. + ![Sync fork modal with "Update branch" button emphasized](/assets/images/help/repository/update-branch-button.png) +{% else %} +1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository. +2. Select the **Fetch upstream** dropdown. + !["Fetch upstream" drop-down](/assets/images/help/repository/fetch-upstream-drop-down.png) +3. Review the details about the commits from the upstream repository, then click **Fetch and merge**. + !["Fetch and merge" button](/assets/images/help/repository/fetch-and-merge-button.png){% endif %} -Se as alterações do repositório a upstream gerarem conflitos, {% data variables.product.company_short %} solicitará a criação de um pull request para resolver os conflitos. +If the changes from the upstream repository cause conflicts, {% data variables.product.company_short %} will prompt you to create a pull request to resolve the conflicts. -## Sincronizar um branch de fork com a {% data variables.product.prodname_cli %} +## Syncing a fork branch with the {% data variables.product.prodname_cli %} -{% data reusables.cli.about-cli %} Para saber mais sobre a {% data variables.product.prodname_cli %}, confira "[Sobre a {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)". +{% data reusables.cli.about-cli %} To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." -Para atualizar o fork remoto por meio do próprio pai, use o subcomando `gh repo sync -b BRANCHNAME` e forneça o nome do fork como argumento. +To update the remote fork from its parent, use the `gh repo sync -b BRANCHNAME` subcommand and supply your fork and branch name as arguments. ```shell -$ gh repo sync owner/cli-fork -b BRANCHNAME +$ gh repo sync owner/cli-fork -b BRANCH_NAME ``` -Se as alterações do repositório upstream causarem conflito, a s {% data variables.product.prodname_cli %} não poderá sincronizá-las. Defina o sinalizador `-force` para substituir o branch de destino. +If the changes from the upstream repository cause conflict then the {% data variables.product.prodname_cli %} can't sync. You can set the `-force` flag to overwrite the destination branch. -## Sincronizar um branch de fork usando a linha de comando +## Syncing a fork branch from the command line -Para sincronizar o fork com um repositório upstream, você precisa [configurar um controle remoto que aponte para o repositório upstream](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork) no Git. +Before you can sync your fork with an upstream repository, you must [configure a remote that points to the upstream repository](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork) in Git. {% data reusables.command_line.open_the_multi_os_terminal %} -2. Altere o diretório de trabalho atual para seu projeto local. -3. Obtenha os branches e os respectivos commits do repositório upstream. Os commits em `BRANCHNAME` serão armazenados no branch `upstream/BRANCHNAME` local. +2. Change the current working directory to your local project. +3. Fetch the branches and their respective commits from the upstream repository. Commits to `BRANCHNAME` will be stored in the local branch `upstream/BRANCHNAME`. ```shell $ git fetch upstream @@ -68,18 +64,18 @@ Para sincronizar o fork com um repositório upstream, você precisa [configurar > remote: Compressing objects: 100% (53/53), done. > remote: Total 62 (delta 27), reused 44 (delta 9) > Unpacking objects: 100% (62/62), done. - > From https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY + > From https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY > * [new branch] main -> upstream/main ``` -4. Faça check-out do branch padrão local do fork, neste caso, usamos o `main`. +4. Check out your fork's local default branch - in this case, we use `main`. ```shell $ git checkout main > Switched to branch 'main' ``` -5. Mescle as alterações do branch padrão upstream, neste caso, `upstream/main`, no branch padrão local. Isso coloca o branch padrão da bifurcação em sincronia com o repositório upstream, sem perder as alterações locais. +5. Merge the changes from the upstream default branch - in this case, `upstream/main` - into your local default branch. This brings your fork's default branch into sync with the upstream repository, without losing your local changes. ```shell $ git merge upstream/main @@ -92,7 +88,7 @@ Para sincronizar o fork com um repositório upstream, você precisa [configurar > create mode 100644 README.md ``` - Se o branch local não tiver commits exclusivos, o Git executará um avanço. Para obter mais informações, confira [Conceitos básicos de branch e mesclagem](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging) na documentação do Git. + If your local branch didn't have any unique commits, Git will perform a fast-forward. For more information, see [Basic Branching and Merging](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging) in the Git documentation. ```shell $ git merge upstream/main > Updating 34e91da..16c56ad @@ -100,10 +96,10 @@ Para sincronizar o fork com um repositório upstream, você precisa [configurar > README.md | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) ``` - Se o branch local tiver commits exclusivos, poderá ser necessário resolver conflitos. Para obter mais informações, confira "[Como resolver conflitos de mesclagem](/github/collaborating-with-pull-requests/addressing-merge-conflicts)". + If your local branch had unique commits, you may need to resolve conflicts. For more information, see "[Addressing merge conflicts](/github/collaborating-with-pull-requests/addressing-merge-conflicts)." {% tip %} -**Dica**: a sincronização do fork atualiza apenas a cópia local do repositório. Para atualizar o fork no {% data variables.product.product_location %}, você precisa [efetuar push das alterações](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/). +**Tip**: Syncing your fork only updates your local copy of the repository. To update your fork on {% data variables.location.product_location %}, you must [push your changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/). {% endtip %} diff --git a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md index 121460eb32..4cbd1eee7d 100644 --- a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md +++ b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md @@ -1,78 +1,73 @@ --- -title: Alterar a mensagem do commit +title: Changing a commit message redirect_from: - /articles/can-i-delete-a-commit-message - /articles/changing-a-commit-message - /github/committing-changes-to-your-project/changing-a-commit-message - /github/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message -intro: 'Se uma mensagem do commit contiver informações imprecisas, incorretas ou confidenciais, você poderá corrigi-las localmente e fazer push de um novo commit com uma nova mensagem para o {% data variables.product.product_name %}. Também é possível alterar uma mensagem do commit para adicionar informações ausentes.' +intro: 'If a commit message contains unclear, incorrect, or sensitive information, you can amend it locally and push a new commit with a new message to {% data variables.product.product_name %}. You can also change a commit message to add missing information.' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' -ms.openlocfilehash: fa4966da0fe443e6635b43fc9b3b11108d57cf6e -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145127173' --- -## Reescrever a mensagem do commit mais recente +## Rewriting the most recent commit message -Você pode alterar a mensagem de commit mais recente usando o comando `git commit --amend`. +You can change the most recent commit message using the `git commit --amend` command. -No Git, o texto da mensagem do commit faz parte do commit. Alterar a mensagem do commit mudará o ID do commit, isto é, a soma de verificação SHA1 que nomeia o commit. Efetivamente, você está criando um commit que substitui o antigo. +In Git, the text of the commit message is part of the commit. Changing the commit message will change the commit ID--i.e., the SHA1 checksum that names the commit. Effectively, you are creating a new commit that replaces the old one. -## Não foi feito push on-line do commit +## Commit has not been pushed online -Se o commit existir no repositório local e não tiver sido publicado no {% data variables.product.product_location %}, você poderá corrigir a mensagem de commit com o comando `git commit --amend`. +If the commit only exists in your local repository and has not been pushed to {% data variables.location.product_location %}, you can amend the commit message with the `git commit --amend` command. -1. Na linha de comando, navegue até o repositório que contém o commit que você deseja corrigir. -2. Digite `git commit --amend` e pressione **Enter**. -3. No editor de texto, edite a mensagem do commit e salve o commit. - - Você pode adicionar um coautor incluindo um trailer no commit. Para obter mais informações, confira "[Como criar um commit com vários autores](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)". +1. On the command line, navigate to the repository that contains the commit you want to amend. +2. Type `git commit --amend` and press **Enter**. +3. In your text editor, edit the commit message, and save the commit. + - You can add a co-author by adding a trailer to the commit. For more information, see "[Creating a commit with multiple authors](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)." {% ifversion fpt or ghec %} - - É possível criar commits em nome da sua organização adicionando um trailer ao commit. Para obter mais informações, confira "[Como criar um commit em nome de uma organização](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization)" {% endif %} + - You can create commits on behalf of your organization by adding a trailer to the commit. For more information, see "[Creating a commit on behalf of an organization](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization)" +{% endif %} -O novo commit e a mensagem aparecerão no {% data variables.product.product_location %} na próxima vez que você fizer push. +The new commit and message will appear on {% data variables.location.product_location %} the next time you push. {% tip %} -Altere o editor de texto padrão do Git alterando a configuração `core.editor`. Para obter mais informações, confira "[Configuração básica do cliente](https://git-scm.com/book/en/Customizing-Git-Git-Configuration#_basic_client_configuration)" no manual do Git. +You can change the default text editor for Git by changing the `core.editor` setting. For more information, see "[Basic Client Configuration](https://git-scm.com/book/en/Customizing-Git-Git-Configuration#_basic_client_configuration)" in the Git manual. {% endtip %} -## Corrigir mensagens do commit antigas ou em grandes quantidades +## Amending older or multiple commit messages -Se você já tiver feito push do commit no {% data variables.product.product_location %}, será necessário forçar o push de um commit com uma mensagem corrigida. +If you have already pushed the commit to {% data variables.location.product_location %}, you will have to force push a commit with an amended message. {% warning %} -O recomendável é evitar tanto quanto possível o push forçado, uma vez que isso altera o histórico do repositório. No caso de push forçado, as pessoas que já clonaram o repositório terão que corrigir manualmente o respectivo histórico local. Para obter mais informações, confira "[Como se recuperar da troca de base upstream](https://git-scm.com/docs/git-rebase#_recovering_from_upstream_rebase)" no manual do Git. +We strongly discourage force pushing, since this changes the history of your repository. If you force push, people who have already cloned your repository will have to manually fix their local history. For more information, see "[Recovering from upstream rebase](https://git-scm.com/docs/git-rebase#_recovering_from_upstream_rebase)" in the Git manual. {% endwarning %} -**Alteração da mensagem de commit enviada por psuh mais recentemente** +**Changing the message of the most recently pushed commit** -1. Siga as [etapas descritas acima](/articles/changing-a-commit-message#commit-has-not-been-pushed-online) para alterar a mensagem de commit. -2. Use o comando `push --force-with-lease` para forçar o push sobre o commit antigo. +1. Follow the [steps above](/articles/changing-a-commit-message#commit-has-not-been-pushed-online) to amend the commit message. +2. Use the `push --force-with-lease` command to force push over the old commit. ```shell - $ git push --force-with-lease origin example-branch + $ git push --force-with-lease origin EXAMPLE-BRANCH ``` -**Alteração das mensagens de commit mais antigo ou múltiplo** +**Changing the message of older or multiple commit messages** -Se precisar corrigir a mensagem de vários commits ou de um commit antigo, você pode usar o rebase interativo e, em seguida, forçar o push para alterar o histórico do commit. +If you need to amend the message for multiple commits or an older commit, you can use interactive rebase, then force push to change the commit history. -1. Na linha de comando, navegue até o repositório que contém o commit que você deseja corrigir. -2. Use o comando `git rebase -i HEAD~n` para ver a lista dos últimos commits `n` no editor de texto padrão. +1. On the command line, navigate to the repository that contains the commit you want to amend. +2. Use the `git rebase -i HEAD~n` command to display a list of the last `n` commits in your default text editor. ```shell # Displays a list of the last 3 commits on the current branch $ git rebase -i HEAD~3 ``` - A lista ficará parecida com o seguinte: + The list will look similar to the following: ```shell pick e499d89 Delete CNAME @@ -97,33 +92,33 @@ Se precisar corrigir a mensagem de vários commits ou de um commit antigo, você # # Note that empty commits are commented out ``` -3. Substitua `pick` por `reword` antes de cada mensagem de commit que deseja alterar. +3. Replace `pick` with `reword` before each commit message you want to change. ```shell pick e499d89 Delete CNAME reword 0c39034 Better README reword f7fde4a Change the commit message but push the same commit. ``` -4. Salve e feche o arquivo da lista de commits. -5. Em cada arquivo de commit resultante, digite a nova mensagem do commit, salve o arquivo e feche-o. -6. Quando estiver pronto para fazer push das suas alterações para o GitHub, use o comando push --force para fazer push forçado sobre o commit antigo. +4. Save and close the commit list file. +5. In each resulting commit file, type the new commit message, save the file, and close it. +6. When you're ready to push your changes to GitHub, use the push --force command to force push over the old commit. ```shell -$ git push --force origin example-branch +$ git push --force origin EXAMPLE-BRANCH ``` -Para obter mais informações sobre a troca de base interativa, confira "[Modo interativo](https://git-scm.com/docs/git-rebase#_interactive_mode)" no manual do Git. +For more information on interactive rebase, see "[Interactive mode](https://git-scm.com/docs/git-rebase#_interactive_mode)" in the Git manual. {% tip %} -Tal como antes, corrigir a mensagem do commit resultará em um novo commit com um novo ID. No entanto, nesse caso, cada commit que segue o commit corrigido também obterá um novo ID, pois cada commit também contém o id de seu principal. +As before, amending the commit message will result in a new commit with a new ID. However, in this case, every commit that follows the amended commit will also get a new ID because each commit also contains the id of its parent. {% endtip %} {% warning %} -Se você incluiu informações confidenciais em uma mensagem do commit, forçar o push de um commit com um commit corrigido pode não remover o commit original do {% data variables.product.product_name %}. O commit antigo não fará parte de um clone subsequente. No entanto, ele ainda poderá ser armazenado no cache do {% data variables.product.product_name %} e ser acessado por meio do ID do commit. Você deve contatar o {% data variables.contact.contact_support %} com o ID do commit antigo para que ele seja apagado do repositório remoto. +If you have included sensitive information in a commit message, force pushing a commit with an amended commit may not remove the original commit from {% data variables.product.product_name %}. The old commit will not be a part of a subsequent clone; however, it may still be cached on {% data variables.product.product_name %} and accessible via the commit ID. You must contact {% data variables.contact.contact_support %} with the old commit ID to have it purged from the remote repository. {% endwarning %} -## Leitura adicional +## Further reading -* "[Como assinar commits](/articles/signing-commits)" +* "[Signing commits](/articles/signing-commits)" diff --git a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md index f300afa119..e4cf27cb8f 100644 --- a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md +++ b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md @@ -1,6 +1,6 @@ --- -title: Criar um commit em nome de uma organização -intro: 'Você pode criar commits em nome de uma organização adicionando um trailer à mensagem do commit. Os commits atribuídos a uma organização incluem um selo `on-behalf-of` no {% data variables.product.product_name %}.' +title: Creating a commit on behalf of an organization +intro: 'You can create commits on behalf of an organization by adding a trailer to the commit''s message. Commits attributed to an organization include an `on-behalf-of` badge on {% data variables.product.product_name %}.' redirect_from: - /articles/creating-a-commit-on-behalf-of-an-organization - /github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization @@ -9,33 +9,27 @@ versions: fpt: '*' ghec: '*' shortTitle: On behalf of an organization -ms.openlocfilehash: 31b8a6b8d1824fa960fb32fa5fd7b4c28625037c -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145127165' --- {% note %} -**Observação:** atualmente, a capacidade de criar um commit em nome de uma organização está em versão beta pública e sujeita a alterações. +**Note:** The ability to create a commit on behalf of an organization is currently in public beta and is subject to change. {% endnote %} -Para criar commits em nome de uma organização: +To create commits on behalf of an organization: -- você deve ser um integrante da organização indicado no trailer -- você deve assinar o commit -- o e-mail do seu commit e o e-mail da organização devem estar em um domínio verificado pela organização -- sua mensagem de commit precisa terminar com o trailer de commit `on-behalf-of: @org ` - - `org` é o logon da organização - - `name@organization.com` está no domínio da organização +- you must be a member of the organization indicated in the trailer +- you must sign the commit +- your commit email and the organization email must be in a domain verified by the organization +- your commit message must end with the commit trailer `on-behalf-of: @org ` + - `org` is the organization's login + - `name@organization.com` is in the organization's domain -As organizações podem usar o email `name@organization.com` como um ponto de contato público para esforços de código aberto. +Organizations can use the `name@organization.com` email as a public point of contact for open source efforts. -## Como criar commits com uma notificação `on-behalf-of` na linha de comando +## Creating commits with an `on-behalf-of` badge on the command line -1. Digite sua mensagem de commit e uma descrição curta e significativa de suas alterações. Depois da descrição do commit, em vez de inserir aspas para encerrar, adicione duas linhas vazias. +1. Type your commit message and a short, meaningful description of your changes. After your commit description, instead of a closing quotation, add two empty lines. ```shell $ git commit -m "Refactor usability tests. > @@ -43,38 +37,38 @@ As organizações podem usar o email `name@organization.com` como um ponto de co ``` {% tip %} - **Dica:** se você estiver usando um editor de texto na linha de comando para digitar sua mensagem de commit, verifique se há duas linhas novas entre o final da descrição do commit e o trailer de commit `on-behalf-of:`. + **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `on-behalf-of:` commit trailer. {% endtip %} -2. Na próxima linha da mensagem de commit, digite `on-behalf-of: @org ` e uma aspa de fechamento. +2. On the next line of the commit message, type `on-behalf-of: @org `, then a closing quotation mark. ```shell $ git commit -m "Refactor usability tests. > > - on-behalf-of: @org <name@organization.com>" + on-behalf-of: @ORG NAME@ORGANIZATION.COM" ``` -O novo commit, mensagem e selo aparecerão no {% data variables.product.product_location %} na próxima vez que você fizer push. Para obter mais informações, confira "[Efetuar push das alterações para um repositório remoto](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)". +The new commit, message, and badge will appear on {% data variables.location.product_location %} the next time you push. For more information, see "[Pushing changes to a remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)." -## Como criar commits com uma notificação `on-behalf-of` no {% data variables.product.product_name %} +## Creating commits with an `on-behalf-of` badge on {% data variables.product.product_name %} -Depois de fazer alterações em um arquivo usando o editor da Web do {% data variables.product.product_name %}, você pode criar um commit em nome da sua organização adicionando um trailer `on-behalf-of:` à mensagem de commit. +After you've made changes in a file using the web editor on {% data variables.product.product_name %}, you can create a commit on behalf of your organization by adding an `on-behalf-of:` trailer to the commit's message. -1. Depois de fazer as alterações, na parte inferior da página, digite uma mensagem de commit curta e significativa que descreve as alterações feitas. - ![Mensagem de commit para a alteração](/assets/images/help/repository/write-commit-message-quick-pull.png) +1. After making your changes, at the bottom of the page, type a short, meaningful commit message that describes the changes you made. + ![Commit message for your change](/assets/images/help/repository/write-commit-message-quick-pull.png) -2. Na caixa de texto abaixo da mensagem de commit, adicione `on-behalf-of: @org `. +2. In the text box below your commit message, add `on-behalf-of: @org `. - ![Exemplo de trailer on-behalf-of da mensagem do commit na segunda caixa de texto da mensagem do commit](/assets/images/help/repository/write-commit-message-on-behalf-of-trailer.png) -4. Clique em **Fazer commit de alterações** ou em **Propor alterações**. + ![Commit message on-behalf-of trailer example in second commit message text box](/assets/images/help/repository/write-commit-message-on-behalf-of-trailer.png) +4. Click **Commit changes** or **Propose changes**. -O novo commit, mensagem e selo aparecerão no {% data variables.product.product_location %}. +The new commit, message, and badge will appear on {% data variables.location.product_location %}. -## Leitura adicional +## Further reading -- "[Como ver as contribuições no seu perfil](/articles/viewing-contributions-on-your-profile)" -- "[Por que minhas contribuições não aparecem no meu perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" -- "[Como ver os colaboradores de um projeto](/articles/viewing-a-projects-contributors)" -- "[Como alterar uma mensagem de commit](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message)" +- "[Viewing contributions on your profile](/articles/viewing-contributions-on-your-profile)" +- "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" +- "[Viewing a project’s contributors](/articles/viewing-a-projects-contributors)" +- "[Changing a commit message](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message)" diff --git a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md index e90daabdf9..a1ac806368 100644 --- a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md +++ b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md @@ -1,6 +1,6 @@ --- -title: Criar um commit com vários autores -intro: 'Você pode atribuir um commit a mais de um autor adicionando um ou mais `Co-authored-by` trailers à mensagem de confirmação. Os commits de coautoria são visíveis em {% data variables.product.product_name %}{% ifversion ghes or ghae %} e podem ser incluídos no gráfico de contribuições do perfil e nas estatísticas do repositório{% endif %}.' +title: Creating a commit with multiple authors +intro: 'You can attribute a commit to more than one author by adding one or more `Co-authored-by` trailers to the commit''s message. Co-authored commits are visible on {% data variables.product.product_name %}{% ifversion ghes or ghae %} and can be included in the profile contributions graph and the repository''s statistics{% endif %}.' redirect_from: - /articles/creating-a-commit-with-multiple-authors - /github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors @@ -11,86 +11,80 @@ versions: ghae: '*' ghec: '*' shortTitle: With multiple authors -ms.openlocfilehash: 4aa5b707e75480ead830e680151064db5f278557 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145127162' --- -## Informações obrigatórias do coautor +## Required co-author information -Para poder adicionar um coautor a um commit, você deve saber o e-mail adequado a ser usado para cada coautor. Para o commit do coautor contar como uma contribuição, você deve usar o e-mail associado à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. +Before you can add a co-author to a commit, you must know the appropriate email to use for each co-author. For the co-author's commit to count as a contribution, you must use the email associated with their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. {% ifversion fpt or ghec %} -Se uma pessoa optar por manter o endereço de email privado, você deverá usar o email `no-reply` fornecido pelo {% data variables.product.product_name %} para proteger a privacidade dela. Caso contrário, o e-mail do coautor estará disponível para o público na mensagem do commit. Se quiser manter seu email privado, você poderá optar por usar um email `no-reply` fornecido pelo {% data variables.product.product_name %} para operações do Git e pedir aos outros coautores que listem seu email `no-reply` nos trailers de commit. +If a person chooses to keep their email address private, you should use their {% data variables.product.product_name %}-provided `no-reply` email to protect their privacy. Otherwise, the co-author's email will be available to the public in the commit message. If you want to keep your email private, you can choose to use a {% data variables.product.product_name %}-provided `no-reply` email for Git operations and ask other co-authors to list your `no-reply` email in commit trailers. -Para obter mais informações, confira "[Como definir seu endereço de email de commit](/articles/setting-your-commit-email-address)". +For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)." {% tip %} - **Dica:** você pode ajudar um coautor a encontrar o endereço de email preferencial dele compartilhando estas informações: - - Para encontrar seu email `no-reply` fornecido pelo {% data variables.product.product_name %}, navegue até a página de configurações do email em "Manter meu endereço de email privado". - - Para encontrar o email usado para configurar o Git no computador, execute `git config user.email` na linha de comando. + **Tip:** You can help a co-author find their preferred email address by sharing this information: + - To find your {% data variables.product.product_name %}-provided `no-reply` email, navigate to your email settings page under "Keep my email address private." + - To find the email you used to configure Git on your computer, run `git config user.email` on the command line. {% endtip %} {% endif %} -## Criar commits coautorados usando o {% data variables.product.prodname_desktop %} +## Creating co-authored commits using {% data variables.product.prodname_desktop %} -Você pode usar o {% data variables.product.prodname_desktop %} para criar um commit com um coautor. Para obter mais informações, confira "[Escrever uma mensagem de commit e efetuar push das alterações](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" e [{% data variables.product.prodname_desktop %}](https://desktop.github.com). +You can use {% data variables.product.prodname_desktop %} to create a commit with a co-author. For more information, see "[Write a commit message and push your changes](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" and [{% data variables.product.prodname_desktop %}](https://desktop.github.com). -![Adicionar um coautor à mensagem do commit](/assets/images/help/desktop/co-authors-demo-hq.gif) +![Add a co-author to the commit message](/assets/images/help/desktop/co-authors-demo-hq.gif) -## Criar commits coautorados na linha de comando +## Creating co-authored commits on the command line {% data reusables.pull_requests.collect-co-author-commit-git-config-info %} -1. Digite sua mensagem de commit e uma descrição curta e significativa de suas alterações. Depois da descrição do commit, em vez de inserir aspas para encerrar, adicione duas linhas vazias. - ```shell +1. Type your commit message and a short, meaningful description of your changes. After your commit description, instead of a closing quotation, add two empty lines. + ``` $ git commit -m "Refactor usability tests. > > ``` {% tip %} - **Dica:** se você estiver usando um editor de texto na linha de comando para digitar sua mensagem de commit, verifique se há duas linhas novas entre o final da descrição do commit e o trailer de commit `Co-authored-by:`. + **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `Co-authored-by:` commit trailer. {% endtip %} -3. Na próxima linha da mensagem de commit, digite `Co-authored-by: name ` com informações específicas para cada coautor. Depois das informações do coautor, adicione aspas de fechamento. +3. On the next line of the commit message, type `Co-authored-by: name ` with specific information for each co-author. After the co-author information, add a closing quotation mark. - Se estiver adicionando vários coautores, dê a cada coautor uma linha própria e um trailer de commit `Co-authored-by:` próprio. - ```shell + If you're adding multiple co-authors, give each co-author their own line and `Co-authored-by:` commit trailer. + ``` $ git commit -m "Refactor usability tests. > > - Co-authored-by: name <name@example.com> - Co-authored-by: another-name <another-name@example.com>" + Co-authored-by: NAME + Co-authored-by: AUTHOR-NAME " ``` -O novo commit e a mensagem aparecerão no {% data variables.product.product_location %} na próxima vez que você fizer push. Para obter mais informações, confira "[Efetuar push das alterações para um repositório remoto](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)". +The new commit and message will appear on {% data variables.location.product_location %} the next time you push. For more information, see "[Pushing changes to a remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)." -## Criar commits coautorados no {% data variables.product.product_name %} +## Creating co-authored commits on {% data variables.product.product_name %} -Depois de fazer alterações em um arquivo usando o editor da Web no {% data variables.product.product_name %}, crie um commit com coautoria adicionando um trailer `Co-authored-by:` à mensagem do commit. +After you've made changes in a file using the web editor on {% data variables.product.product_name %}, you can create a co-authored commit by adding a `Co-authored-by:` trailer to the commit's message. {% data reusables.pull_requests.collect-co-author-commit-git-config-info %} -2. Depois de fazer as alterações juntos, na parte inferior da página, digite uma mensagem de commit curta e significativa que descreve as alterações feitas. - ![Mensagem de commit para a alteração](/assets/images/help/repository/write-commit-message-quick-pull.png) -3. Na caixa de texto abaixo da mensagem de commit, adicione `Co-authored-by: name ` com informações específicas para cada coautor. Se estiver adicionando vários coautores, dê a cada coautor uma linha própria e um trailer de commit `Co-authored-by:` próprio. +2. After making your changes together, at the bottom of the page, type a short, meaningful commit message that describes the changes you made. + ![Commit message for your change](/assets/images/help/repository/write-commit-message-quick-pull.png) +3. In the text box below your commit message, add `Co-authored-by: name ` with specific information for each co-author. If you're adding multiple co-authors, give each co-author their own line and `Co-authored-by:` commit trailer. - ![Exemplo de trailer de coautor da mensagem do commit na segunda caixa de texto da mensagem do commit](/assets/images/help/repository/write-commit-message-co-author-trailer.png) -4. Clique em **Fazer commit de alterações** ou em **Propor alterações**. + ![Commit message co-author trailer example in second commit message text box](/assets/images/help/repository/write-commit-message-co-author-trailer.png) +4. Click **Commit changes** or **Propose changes**. -O novo commit e a mensagem aparecerão no {% data variables.product.product_location %}. +The new commit and message will appear on {% data variables.location.product_location %}. -## Leitura adicional +## Further reading {% ifversion ghes or ghae %} -- "[Como ver as contribuições no seu perfil](/articles/viewing-contributions-on-your-profile)" -- "[Por que minhas contribuições não aparecem no meu perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"{% endif %} -- "[Como ver os colaboradores de um projeto](/articles/viewing-a-projects-contributors)" -- "[Como alterar uma mensagem de commit](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message)" -- "[Como fazer commit de alterações no seu projeto e revisá-las](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" na documentação do {% data variables.product.prodname_desktop %} +- "[Viewing contributions on your profile](/articles/viewing-contributions-on-your-profile)" +- "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"{% endif %} +- "[Viewing a project's contributors](/articles/viewing-a-projects-contributors)" +- "[Changing a commit message](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message)" +- "[Committing and reviewing changes to your project](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" in the {% data variables.product.prodname_desktop %} documentation diff --git a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md index a09a24b387..ceab766830 100644 --- a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md +++ b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md @@ -1,6 +1,6 @@ --- -title: 'O commit aparece no GitHub, mas não no meu clone local' -intro: 'Às vezes, um commit poderá ser visto no {% data variables.product.product_name %}, mas não existirá no clone local do repositório.' +title: Commit exists on GitHub but not in my local clone +intro: 'Sometimes a commit will be viewable on {% data variables.product.product_name %}, but will not exist in your local clone of the repository.' redirect_from: - /articles/commit-exists-on-github-but-not-in-my-local-clone - /github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone @@ -11,57 +11,62 @@ versions: ghae: '*' ghec: '*' shortTitle: Commit missing in local clone -ms.openlocfilehash: 9374b17a111bc3f88bf81d60de97e354c0bcf8ac -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145127159' --- -Ao usar `git show` para ver um commit específico na linha de comando, talvez você receba um erro fatal. +When you use `git show` to view a specific commit on the command line, you may get a fatal error. -Por exemplo, você poderá receber um erro `bad object` localmente: +For example, you may receive a `bad object` error locally: ```shell $ git show 1095ff3d0153115e75b7bca2c09e5136845b5592 > fatal: bad object 1095ff3d0153115e75b7bca2c09e5136845b5592 ``` -No entanto, ao exibir o commit no {% data variables.product.product_location %}, você poderá vê-lo sem qualquer problema: +However, when you view the commit on {% data variables.location.product_location %}, you'll be able to see it without any problems: `github.com/$account/$repository/commit/1095ff3d0153115e75b7bca2c09e5136845b5592` -Há várias explicações possíveis: +There are several possible explanations: -* O repositório local está desatualizado. -* O branch que contém o commit foi excluído, de modo que o commit não é mais referenciado. -* Alguém fez push forçado no commit. +* The local repository is out of date. +* The branch that contains the commit was deleted, so the commit is no longer referenced. +* Someone force pushed over the commit. -## O repositório local está desatualizado +## The local repository is out of date -O repositório local pode não ter o commit ainda. Para obter informações do repositório remoto para o clone local, use `git fetch`: +Your local repository may not have the commit yet. To get information from your remote repository to your local clone, use `git fetch`: ```shell -$ git fetch remote +$ git fetch REMOTE ``` -Isso copia com segurança as informações do repositório remoto para o clone local sem fazer nenhuma alteração nos arquivos dos quais você fez check-out. Use `git fetch upstream` para obter informações de um repositório com fork ou `git fetch origin` para obter informações de um repositório que você apenas clonou. +This safely copies information from the remote repository to your local clone without making any changes to the files you have checked out. +You can use `git fetch upstream` to get information from a repository you've forked, or `git fetch origin` to get information from a repository you've only cloned. {% tip %} -**Dica**: para obter mais informações, leia [como gerenciar repositórios remotos e buscar dados](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) no livro [Pro Git](https://git-scm.com/book). +**Tip**: For more information, read about [managing remotes and fetching data](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) in the [Pro Git](https://git-scm.com/book) book. {% endtip %} -## O branch que continha o commit foi excluído +## The branch that contained the commit was deleted -Se um colaborador no repositório tiver excluído o branch contendo o commit ou tiver forçado o push no branch, o commit ausente poderá ter ficado órfão (ou seja, não poderá ser acessado de nenhuma referência) e, portanto, o fetch dele não poderá ser feito no clone local. +If a collaborator on the repository has deleted the branch containing the commit +or has force pushed over the branch, the missing commit may have been orphaned +(i.e. it cannot be reached from any reference) and therefore will not be fetched +into your local clone. -A boa notícia é que, se um colaborador tiver um clone local do repositório com o commit ausente, ele poderá efetuar push dele de volta no {% data variables.product.product_name %}. Ele precisa garantir que o commit é referenciado por um branch local e efetuar push dele como um novo branch para o {% data variables.product.product_name %}. +Fortunately, if any collaborator has a local clone of the repository with the +missing commit, they can push it back to {% data variables.product.product_name %}. They need to make sure the commit +is referenced by a local branch and then push it as a new branch to {% data variables.product.product_name %}. -Suponha que a pessoa ainda tenha um branch local (vamos chamá-lo de `B`) que contém o commit. Isso pode estar rastreando o branch que teve o push forçado ou que foi excluído, e ela simplesmente ainda não o atualizou. Para preservar o commit, ela pode efetuar push desse branch local para um novo branch (vamos chamá-lo de `recover-B`) no {% data variables.product.product_name %}. Para este exemplo, vamos supor que ela tenha um repositório remoto chamado `upstream` por meio do qual tem acesso de push em `github.com/$account/$repository`. +Let's say that the person still has a local branch (call it `B`) that contains +the commit. This might be tracking the branch that was force pushed or deleted +and they simply haven't updated yet. To preserve the commit, they can push that +local branch to a new branch (call it `recover-B`) on {% data variables.product.product_name %}. For this example, +let's assume they have a remote named `upstream` via which they have push access +to `github.com/$account/$repository`. -A outra pessoa executa: +The other person runs: ```shell $ git branch recover-B B @@ -70,18 +75,18 @@ $ git push upstream B:recover-B # Push local B to new upstream branch, creating new reference to commit ``` -Agora, *você* pode executar: +Now, *you* can run: ```shell $ git fetch upstream recover-B # Fetch commit into your local repository. ``` -## Evitar pushes forçados +## Avoid force pushes -Evite o push forçado em um repositório, a menos que seja absolutamente necessário. Isso se aplica especialmente quando mais de uma pessoa pode fazer push no repositório. Se alguém fizer push forçado em um repositório, ele poderá sobrescrever commits em que outras pessoas basearam seu trabalho. O push forçado faz alterações no histórico do repositório e pode corromper pull requests. +Avoid force pushing to a repository unless absolutely necessary. This is especially true if more than one person can push to the repository. If someone force pushes to a repository, the force push may overwrite commits that other people based their work on. Force pushing changes the repository history and can corrupt pull requests. -## Leitura adicional +## Further reading -- ["Como trabalhar com repositórios remotos" do livro _Pro Git_](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) -- ["Recuperação de dados" do livro _Pro Git_](https://git-scm.com/book/en/Git-Internals-Maintenance-and-Data-Recovery) +- ["Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) +- ["Data Recovery" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Internals-Maintenance-and-Data-Recovery) diff --git a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md index f7facc498f..d4d8bbe644 100644 --- a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md +++ b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md @@ -1,63 +1,58 @@ --- -title: Por que meus commits estão vinculados ao usuário errado? +title: Why are my commits linked to the wrong user? redirect_from: - /articles/how-do-i-get-my-commits-to-link-to-my-github-account - /articles/why-are-my-commits-linked-to-the-wrong-user - /github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user - /github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user -intro: 'O {% data variables.product.product_name %} usa o endereço de e-mail no header do commit para vincular o commit a um usuário do GitHub. Se os commits estiverem sendo vinculados a outro usuário ou não estiverem vinculados a nenhum usuário, talvez você precise alterar as configurações locais do Git{% ifversion not ghae %} e/ou adicionar um endereço de email às configurações de email da conta{% endif %}.' +intro: '{% data variables.product.product_name %} uses the email address in the commit header to link the commit to a GitHub user. If your commits are being linked to another user, or not linked to a user at all, you may need to change your local Git configuration settings{% ifversion not ghae %}, add an email address to your account email settings, or do both{% endif %}.' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' shortTitle: Linked to wrong user -ms.openlocfilehash: 80a871c85aca151f06ca04d1d48d016bd14ed47f -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147883032' --- {% tip %} -**Observação**: se os commits estiverem vinculados a outro usuário, isso não significa que o usuário possa acessar seu repositório. Um usuário só poderá acessar um repositório seu se você adicioná-lo como colaborador ou incluí-lo em uma equipe que tenha acesso ao repositório. +**Note**: If your commits are linked to another user, that does not mean the user can access your repository. A user can only access a repository you own if you add them as a collaborator or add them to a team that has access to the repository. {% endtip %} -## Commits vinculados a outro usuário +## Commits are linked to another user -Se seus commits estiverem vinculados a outro usuário, isso significa que o endereço de e-mail nas configurações locais do Git está conectado à conta desse usuário em {% data variables.product.product_name %}. Nesse caso, você pode alterar o email nas configurações do Git local{% ifversion ghae %} para o endereço associado à sua conta no {% data variables.product.product_name %} a fim de vincular os commits futuros. Os commits antigos não serão vinculados. Para obter mais informações, confira "[Como configurar seu endereço de email de commit](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)".{% else %} e adicione o novo endereço de email à sua conta do {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} para vincular commits futuros a ela. +If your commits are linked to another user, that means the email address in your local Git configuration settings is connected to that user's account on {% data variables.product.product_name %}. In this case, you can change the email in your local Git configuration settings{% ifversion ghae %} to the address associated with your account on {% data variables.product.product_name %} to link your future commits. Old commits will not be linked. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %} and add the new email address to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} account to link future commits to your account. -1. Para alterar o endereço de email na configuração do Git local, siga as etapas descritas em "[Como definir seu endereço de email de commit](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)". Se você trabalha em várias máquinas, precisa alterar essa configuração em cada uma deles. -2. Adicione o endereço de email da etapa 2 às configurações da sua conta seguindo as etapas descritas em "[Como adicionar um endereço de email à sua conta do GitHub](/articles/adding-an-email-address-to-your-github-account)".{% endif %} +1. To change the email address in your local Git configuration, follow the steps in "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)". If you work on multiple machines, you will need to change this setting on each one. +2. Add the email address from step 2 to your account settings by following the steps in "[Adding an email address to your GitHub account](/articles/adding-an-email-address-to-your-github-account)".{% endif %} -Os commits criados a partir daí serão vinculados à sua conta. +Commits you make from this point forward will be linked to your account. -## Commits não vinculados a nenhum usuário +## Commits are not linked to any user -Se seus commits não estiverem vinculados a nenhum usuário, o nome do autor do commit não será exibido como um link para o perfil de um usuário. +If your commits are not linked to any user, the commit author's name will not be rendered as a link to a user profile. -Para verificar o endereço de e-mail usado para esses commits e conectar commits à sua conta, siga estas etapas: +To check the email address used for those commits and connect commits to your account, take the following steps: -1. Navegue até o commit clicando no link da mensagem do commit. -![Link da mensagem de commit](/assets/images/help/commits/commit-msg-link.png) -2. Para ler uma mensagem sobre o motivo do commit não estar vinculado, posicione o cursor sobre o {% octicon "question" aria-label="Question mark" %} à direita do nome de usuário. -![Mensagem exibida quando o curso é posicionado sobre o commit](/assets/images/help/commits/commit-hover-msg.png) +1. Navigate to the commit by clicking the commit message link. +![Commit message link](/assets/images/help/commits/commit-msg-link.png) +2. To read a message about why the commit is not linked, hover over the blue {% octicon "question" aria-label="Question mark" %} to the right of the username. +![Commit hover message](/assets/images/help/commits/commit-hover-msg.png) - - **Autor não reconhecido (com endereço de email)** Se você receber essa mensagem com um endereço de email, o endereço usado para criar o commit não estará conectado à sua conta do {% data variables.product.product_name %}. {% ifversion not ghae %}Para vincular os commits, [adicione o endereço de email às configurações de email do GitHub](/articles/adding-an-email-address-to-your-github-account).{% endif %}{% ifversion not ghae %} Se o endereço de email tiver um Gravatar associado, o Gravatar será exibido ao lado do commit, em vez do Octocat cinza padrão.{% endif %} - - **Autor não reconhecido (sem endereço de email)** Se você receber essa mensagem sem um endereço de email, isso indicará que você usou um endereço de email genérico que não pode ser conectado à sua conta do {% data variables.product.product_name %}.{% ifversion not ghae %} Você precisará [definir seu endereço de email de commit no Git](/articles/setting-your-commit-email-address) e [adicionar o novo endereço às configurações de email do GitHub](/articles/adding-an-email-address-to-your-github-account) para vincular os commits futuros. Os commits antigos não serão vinculados.{% endif %} - - **Email inválido** O endereço de email nas configurações do Git local está em branco ou não está formatado como um endereço de email.{% ifversion not ghae %} Você precisará [definir seu endereço de email de commit no Git](/articles/setting-your-commit-email-address) e [adicionar o novo endereço às configurações de email do GitHub](/articles/adding-an-email-address-to-your-github-account) para vincular os commits futuros. Os commits antigos não serão vinculados.{% endif %} + - **Unrecognized author (with email address)** If you see this message with an email address, the address you used to author the commit is not connected to your account on {% data variables.product.product_name %}. {% ifversion not ghae %}To link your commits, [add the email address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account).{% endif %}{% ifversion not ghae %} If the email address has a Gravatar associated with it, the Gravatar will be displayed next to the commit, rather than the default gray Octocat.{% endif %} + - **Unrecognized author (no email address)** If you see this message without an email address, you used a generic email address that can't be connected to your account on {% data variables.product.product_name %}.{% ifversion not ghae %} You will need to [set your commit email address in Git](/articles/setting-your-commit-email-address), then [add the new address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account) to link your future commits. Old commits will not be linked.{% endif %} + - **Invalid email** The email address in your local Git configuration settings is either blank or not formatted as an email address.{% ifversion not ghae %} You will need to [set your commit email address in Git](/articles/setting-your-commit-email-address), then [add the new address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account) to link your future commits. Old commits will not be linked.{% endif %} -{% ifversion ghae %} Você pode alterar o email nas configurações do Git local para o endereço associado à sua conta a fim de vincular os commits futuros. Os commits antigos não serão vinculados. Para obter mais informações, confira "[Como definir seu endereço de email de commit](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)". +{% ifversion ghae %} +You can change the email in your local Git configuration settings to the address associated with your account to link your future commits. Old commits will not be linked. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)." {% endif %} {% warning %} -Caso a configuração local do Git contenha um endereço de e-mail genérico ou um endereço de e-mail já anexado à conta de outro usuário, os commits anteriores não serão vinculados à sua conta. Embora o Git permita que você altere o endereço de e-mail usado para commits anteriores, é recomendável evitar isso, principalmente em um repositório compartilhado. +If your local Git configuration contained a generic email address, or an email address that was already attached to another user's account, then your previous commits will not be linked to your account. While Git does allow you to change the email address used for previous commits, we strongly discourage this, especially in a shared repository. {% endwarning %} -## Leitura adicional +## Further reading -* "[Pesquisa de commits](/search-github/searching-on-github/searching-commits)" +* "[Searching commits](/search-github/searching-on-github/searching-commits)" diff --git a/translations/pt-BR/content/repositories/archiving-a-github-repository/backing-up-a-repository.md b/translations/pt-BR/content/repositories/archiving-a-github-repository/backing-up-a-repository.md index 2b8c6b147e..79f382bd8d 100644 --- a/translations/pt-BR/content/repositories/archiving-a-github-repository/backing-up-a-repository.md +++ b/translations/pt-BR/content/repositories/archiving-a-github-repository/backing-up-a-repository.md @@ -1,6 +1,6 @@ --- -title: Fazer backup de um repositório -intro: 'Você pode usar o{% ifversion ghes or ghae %} Git e{% endif %} a API {% ifversion fpt or ghec %}ou uma ferramenta de terceiros {% endif %}para fazer backup do seu repositório.' +title: Backing up a repository +intro: 'You can use{% ifversion ghes or ghae %} Git and{% endif %} the API {% ifversion fpt or ghec %}or a third-party tool {% endif %}to back up your repository.' redirect_from: - /articles/backing-up-a-repository - /github/creating-cloning-and-archiving-repositories/backing-up-a-repository @@ -12,39 +12,34 @@ versions: ghec: '*' topics: - Repositories -ms.openlocfilehash: 3c9a6b5569563858987e338584b3b42bededf716 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147883446' --- {% ifversion fpt or ghec %} -Para baixar um arquivo do seu repositório, você pode usar a API para usuário ou migrações da organização. Para obter mais informações, confira "[Migrações](/rest/reference/migrations)". +To download an archive of your repository, you can use the API for user or organization migrations. For more information, see "[Migrations](/rest/reference/migrations)." {% else %} -Você pode baixar e fazer backup dos repositórios manualmente: +You can download and back up your repositories manually: -- Para baixar os dados Git de um repositório no computador local, é preciso clonar o repositório. Para obter mais informações, confira "[Como clonar um repositório](/articles/cloning-a-repository)". -- Também é possível baixar o wiki do repositório. Para obter mais informações, confira "[Como adicionar ou editar páginas de um wiki](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)". +- To download a repository's Git data to your local machine, you'll need to clone the repository. For more information, see "[Cloning a repository](/articles/cloning-a-repository)." +- You can also download your repository's wiki. For more information, see "[Adding or editing wiki pages](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)." -Quando você clona um repositório ou wiki, somente os dados Git, como arquivos e histórico de commits do projeto, são baixados. Você pode usar nossa API para exportar outros elementos do seu repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} para a sua máquina local: +When you clone a repository or wiki, only Git data, such as project files and commit history, is downloaded. You can use our API to export other elements of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} to your local machine: -- [Problemas](/rest/reference/issues#list-issues-for-a-repository) -- [Solicitações pull](/rest/reference/pulls#list-pull-requests) -- [Garfos](/rest/reference/repos#list-forks) -- [Comentários](/rest/reference/issues#list-issue-comments-for-a-repository) -- [Marcos](/rest/reference/issues#list-milestones) -- [Rótulos](/rest/reference/issues#list-labels-for-a-repository) -- [Observadores](/rest/reference/activity#list-watchers) -- [Marcaram com estrela](/rest/reference/activity#list-stargazers) -- [Projetos](/rest/reference/projects#list-repository-projects) {% endif %} +- [Issues](/rest/reference/issues#list-issues-for-a-repository) +- [Pull requests](/rest/reference/pulls#list-pull-requests) +- [Forks](/rest/reference/repos#list-forks) +- [Comments](/rest/reference/issues#list-issue-comments-for-a-repository) +- [Milestones](/rest/reference/issues#list-milestones) +- [Labels](/rest/reference/issues#list-labels-for-a-repository) +- [Watchers](/rest/reference/activity#list-watchers) +- [Stargazers](/rest/reference/activity#list-stargazers) +- [Projects](/rest/reference/projects#list-repository-projects) +{% endif %} -Depois de ter {% ifversion ghes or ghae %}uma versão local de todo o conteúdo do qual deseja fazer backup, você pode criar um arquivo zip e {% else %}baixado seu arquivo, você pode {% endif %}copiá-lo para um disco rígido externo e/ou carregá-lo em um backup baseado em nuvem ou o serviço de armazenamento, como o [Armazenamento de Blobs do Azure](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-overview/), o [Google Drive](https://www.google.com/drive/) ou o [Dropbox](https://www.dropbox.com/). +Once you have {% ifversion ghes or ghae %}a local version of all the content you want to back up, you can create a zip archive and {% else %}downloaded your archive, you can {% endif %}copy it to an external hard drive and/or upload it to a cloud-based backup or storage service such as [Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-overview/), [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/). {% ifversion fpt or ghec %} -## Ferramentas de backup de terceiros +## Third-party backup tools -Existem várias ferramentas de autoatendimento que automatizam backups de repositórios. Ao contrário de projetos arquivados, que arquivam _todos_ os repositórios públicos no {% data variables.product.product_name %} que não tenham se recusado a tornar os dados acessíveis para todos, as ferramentas de backup baixarão dos dados de repositórios _específicos_ e os organizarão em um novo branch ou diretório. Para obter mais informações sobre projetos de arquivamento, confira "[Sobre o arquivamento de conteúdo e de dados no {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)". Para obter mais informações sobre as ferramentas de backup de autoatendimento, confira a [categoria Utilitários de backup no {% data variables.product.prodname_marketplace %}](https://github.com/marketplace?category=backup-utilities). +A number of self-service tools exist that automate backups of repositories. Unlike archival projects, which archive _all_ public repositories on {% data variables.product.product_name %} that have not opted out and make the data accessible to anyone, backup tools will download data from _specific_ repositories and organize it within a new branch or directory. For more information about archival projects, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)." For more information about self-service backup tools, see the [Backup Utilities category on {% data variables.product.prodname_marketplace %}](https://github.com/marketplace?category=backup-utilities). {% endif %} diff --git a/translations/pt-BR/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md b/translations/pt-BR/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md index 072283fa54..27fa92e78b 100644 --- a/translations/pt-BR/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md +++ b/translations/pt-BR/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md @@ -1,6 +1,6 @@ --- -title: Referenciar e citar conteúdo -intro: Você pode usar ferramentas de terceiros para citar e referenciar conteúdo no GitHub. +title: Referencing and citing content +intro: You can use third-party tools to cite and reference content on GitHub. redirect_from: - /articles/referencing-and-citing-content - /github/creating-cloning-and-archiving-repositories/referencing-and-citing-content @@ -11,35 +11,29 @@ versions: topics: - Repositories shortTitle: Reference & cite content -ms.openlocfilehash: e0bb3dabe5e9ebc8a4dff80797087c8adadfb710 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145127138' --- -## Emitir um identificador persistente para o repositório com o Zenodo +## Issuing a persistent identifier for your repository with Zenodo -Para facilitar o referenciamento dos seus repositórios na literatura acadêmica, você pode criar identificadores persistentes, também conhecidos como identificadores de objetos digitais (DOIs). Use a ferramenta de arquivamento de dados [Zenodo](https://zenodo.org/about) para arquivar um repositório no {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} e emitir um DOI para os arquivos. +To make your repositories easier to reference in academic literature, you can create persistent identifiers, also known as Digital Object Identifiers (DOIs). You can use the data archiving tool [Zenodo](https://zenodo.org/about) to archive a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} and issue a DOI for the archive. {% tip %} -**Dicas:** -- O Zenodo só pode acessar repositórios públicos. Portanto, verifique se o repositório que deseja arquivar é [público](/articles/making-a-private-repository-public). -- Caso deseje arquivar um repositório que pertence a uma organização, talvez o proprietário da organização precise [aprovar o acesso](/articles/approving-oauth-apps-for-your-organization) para o aplicativo Zenodo. -- Lembre-se de incluir uma [licença](/articles/open-source-licensing) no seu repositório para que os leitores saibam como podem reutilizar seu trabalho. +**Tips:** +- Zenodo can only access public repositories, so make sure the repository you want to archive is [public](/articles/making-a-private-repository-public). +- If you want to archive a repository that belongs to an organization, the organization owner may need to [approve access](/articles/approving-oauth-apps-for-your-organization) for the Zenodo application. +- Make sure to include a [license](/articles/open-source-licensing) in your repository so readers know how they can reuse your work. {% endtip %} -1. Navegue até o [Zenodo](http://zenodo.org/). -2. No canto superior esquerdo da tela, clique em **Fazer logon**. ![Botão de logon do Zenodo](/assets/images/help/repository/zenodo_login.png) -3. Clique em **Fazer logon com o GitHub**. ![Logon no Zenodo com o GitHub](/assets/images/help/repository/zenodo_login_with_github.png) -4. Leia as informações sobre as permissões de acesso e clique em **Autorizar aplicativo**. ![Autorização do Zenodo](/assets/images/help/repository/zenodo_authorize.png) -5. Navegue até a [página do Zenodo no GitHub](https://zenodo.org/account/settings/github/). ![Página do Zenodo no GitHub](/assets/images/help/repository/zenodo_github_page.png) -6. À direita do nome do repositório que deseja arquivar, alterne o botão de **Desativado** para **Ativado** para habilitá-lo para arquivamento. ![Habilitar o arquivamento do Zenodo no repositório](/assets/images/help/repository/zenodo_toggle_on.png) +1. Navigate to [Zenodo](http://zenodo.org/). +2. In the upper-left corner of the screen, click **Log in**. ![Zenodo log in button](/assets/images/help/repository/zenodo_login.png) +3. Click **Log in with GitHub**. ![Log into Zenodo with GitHub](/assets/images/help/repository/zenodo_login_with_github.png) +4. Review the information about access permissions, then click **Authorize application**. ![Authorize Zenodo](/assets/images/help/repository/zenodo_authorize.png) +5. Navigate to the [Zenodo GitHub page](https://zenodo.org/account/settings/github/). ![Zenodo GitHub page](/assets/images/help/repository/zenodo_github_page.png) +6. To the right of the name of the repository you want to archive, toggle the button from **Off** to **On** to enable it for archiving. ![Enable Zenodo archiving on repository](/assets/images/help/repository/zenodo_toggle_on.png) -O Zenodo arquiva seu repositório e emite uma nova DOI sempre que você cria uma [versão](/articles/about-releases/) do {% data variables.product.product_name %}. Siga as etapas descritas em "[Como criar versões](/articles/creating-releases/)" para criar uma. +Zenodo archives your repository and issues a new DOI each time you create a new {% data variables.product.product_name %} [release](/articles/about-releases/). Follow the steps at "[Creating releases](/articles/creating-releases/)" to create a new one. -## Divulgar e citar materiais de pesquisa com o Figshare +## Publicizing and citing research material with Figshare -Os projetos de pesquisa acadêmica podem usar o serviço de gerenciamento de dados [Figshare](http://figshare.com) para divulgar e citar material de pesquisa. Para obter mais informações, acesse o [site de suporte do Figshare](https://knowledge.figshare.com/articles/item/how-to-connect-figshare-with-your-github-account). +Academics can use the data management service [Figshare](http://figshare.com) to publicize and cite research material. For more information, see [Figshare's support site](https://knowledge.figshare.com/articles/item/how-to-connect-figshare-with-your-github-account). diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md index a8e14f6c54..cbbb88a505 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md @@ -1,6 +1,6 @@ --- -title: Sobre métodos de merge no GitHub -intro: 'Você pode permitir que contribuidores com acesso push ao seu repositório façam merge das respectivas pull requests no {% data variables.product.product_location %} com diferentes opções de merge ou apliquem um método de merge específico para todas as pull requests do seu repositório.' +title: About merge methods on GitHub +intro: 'You can allow contributors with push access to your repository to merge their pull requests on {% data variables.location.product_location %} with different merge options or enforce a specific merge method for all of your repository''s pull requests.' redirect_from: - /articles/about-merge-methods-on-github - /github/administering-a-repository/about-merge-methods-on-github @@ -13,42 +13,38 @@ versions: topics: - Repositories shortTitle: About merge methods -ms.openlocfilehash: 97e8b7159ebadf1fe02ae56f707728c2bc8c439d -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147882438' --- -{% data reusables.pull_requests.configure_pull_request_merges_intro %} É possível aplicar um tipo de método de merge, como combinação por squash ou rebase de commit, apena habilitando o método desejado para o repositório. +{% data reusables.pull_requests.configure_pull_request_merges_intro %} You can enforce one type of merge method, such as commit squashing or rebasing, by only enabling the desired method for your repository. -{% ifversion fpt or ghec %} {% note %} +{% ifversion fpt or ghec %} +{% note %} -**Observação:** ao usar a fila de mesclagem, você não pode mais escolher o método de mesclagem, pois isso é controlado pela fila. {% data reusables.pull_requests.merge-queue-references %} +**Note:** When using the merge queue, you no longer get to choose the merge method, as this is controlled by the queue. {% data reusables.pull_requests.merge-queue-references %} -{% endnote %} {% endif %} +{% endnote %} +{% endif %} {% data reusables.pull_requests.default_merge_option %} -O método de merge padrão cria um commit de mesclagem. Você pode impedir que uma pessoa faça pushing com commits por merge em um branch protegido aplicando um histórico de commit linear. Para obter mais informações, confira "[Sobre os branches protegidos](/github/administering-a-repository/about-protected-branches#require-linear-history)". +The default merge method creates a merge commit. You can prevent anyone from pushing merge commits to a protected branch by enforcing a linear commit history. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-linear-history)." -## Combinar por squash os commits de merge +## Squashing your merge commits {% data reusables.pull_requests.squash_and_merge_summary %} -Antes de habilitar a combinação de commits por squash, considere estas desvantagens: -- Você perde informações sobre quando alterações específicas foram originalmente feitas e quem criou os commits combinados por squash. -- Se você continuar trabalhando no branch principal de um pull request após a combinação por squash e o merge, e, em seguida, criar um novo pull request entre os mesmos branches, commits que você já tenha combinado por squash e feito merge serão listados no novo pull request. Você também pode ter conflitos que tenha que resolver repetidamente em cada pull request consecutivo. Para obter mais informações, confira "[Sobre as mesclagens de solicitações de pull](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges#squashing-and-merging-a-long-running-branch)". -- Alguns comandos Git que usam a ID "SHA" ou "hash" podem ser mais difíceis de usar, pois a ID SHA para os commits originais é perdida. Por exemplo, o uso de [`git rerere`](https://git-scm.com/docs/git-rerere) pode não ser tão eficaz. +Before enabling squashing commits, consider these disadvantages: +- You lose information about when specific changes were originally made and who authored the squashed commits. +- If you continue working on the head branch of a pull request after squashing and merging, and then create a new pull request between the same branches, commits that you previously squashed and merged will be listed in the new pull request. You may also have conflicts that you have to repeatedly resolve in each successive pull request. For more information, see "[About pull request merges](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges#squashing-and-merging-a-long-running-branch)." +- Some Git commands that use the "SHA" or "hash" ID may be harder to use since the SHA ID for the original commits is lost. For example, using [`git rerere`](https://git-scm.com/docs/git-rerere) may not be as effective. -Para obter mais informações, confira "[Como configurar o squash de commit para solicitações de pull](/articles/configuring-commit-squashing-for-pull-requests)". +For more information, see "[Configuring commit squashing for pull requests](/articles/configuring-commit-squashing-for-pull-requests)." -## Fazer rebase e merge de seus commits +## Rebasing and merging your commits {% data reusables.pull_requests.rebase_and_merge_summary %} -Antes de habilitar o rebase de commit, leve em consideração estas desvantagens: -- Os colaboradores do repositório podem precisar trocar a base novamente na linha de comando, resolver os conflitos e forçar por push as alterações para o branch do tópico da solicitação de pull (ou para o branch principal remoto) para usar a opção **Troca de base e mesclagem** do {% data variables.product.product_location %}. O push forçado deve ser feito com cuidado para que os contribuidores não substituam o trabalho que outras pessoas usaram como base para o respectivo trabalho. Para saber mais sobre quando a opção **Troca de base e mesclagem** é desabilitada no {% data variables.product.product_location %} e o fluxo de trabalho necessário para habilitá-la novamente, confira "[Sobre as mesclagens de solicitações de pull](/articles/about-pull-request-merges/#rebase-and-merge-your-pull-request-commits)". +Before enabling commit rebasing, consider these disadvantages: +- Repository contributors may have to rebase on the command line, resolve any conflicts, and force push their changes to the pull request's topic branch (or remote head branch) before they can use the **rebase and merge** option on {% data variables.location.product_location %}. Force pushing must be done carefully so contributors don't overwrite work that others have based their work on. To learn more about when the **Rebase and merge** option is disabled on {% data variables.location.product_location %} and the workflow to re-enable it, see "[About pull request merges](/articles/about-pull-request-merges/#rebase-and-merge-your-pull-request-commits)." - {% indented_data_reference reusables.pull_requests.rebase_and_merge_verification spaces=3 %} -Para obter mais informações, confira "[Como configurar a troca de base de commit para solicitações de pull](/articles/configuring-commit-rebasing-for-pull-requests)". +For more information, see "[Configuring commit rebasing for pull requests](/articles/configuring-commit-rebasing-for-pull-requests)." diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md index 506a34d3b1..610176d045 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md @@ -1,6 +1,6 @@ --- title: Configuring commit merging for pull requests -intro: 'You can enforce, allow, or disable merging with a merge commit for all pull request merges on {% data variables.product.product_location %} in your repository.' +intro: 'You can enforce, allow, or disable merging with a merge commit for all pull request merges on {% data variables.location.product_location %} in your repository.' versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md index 714645fa9e..c4652106f1 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md @@ -1,6 +1,6 @@ --- title: Configuring commit rebasing for pull requests -intro: 'You can enforce, allow, or disable commit rebasing for all pull request merges on {% data variables.product.product_location %} in your repository.' +intro: 'You can enforce, allow, or disable commit rebasing for all pull request merges on {% data variables.location.product_location %} in your repository.' redirect_from: - /articles/configuring-commit-rebasing-for-pull-requests - /github/administering-a-repository/configuring-commit-rebasing-for-pull-requests diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md index 0473b10065..7814e66262 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md @@ -1,6 +1,6 @@ --- title: Configuring commit squashing for pull requests -intro: 'You can enforce, allow, or disable commit squashing for all pull request merges on {% data variables.product.product_location %} in your repository.' +intro: 'You can enforce, allow, or disable commit squashing for all pull request merges on {% data variables.location.product_location %} in your repository.' redirect_from: - /articles/configuring-commit-squashing-for-pull-requests - /github/administering-a-repository/configuring-commit-squashing-for-pull-requests diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md index c48347ddc8..bf762e72cc 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md @@ -1,6 +1,6 @@ --- -title: Configurar merges de pull request -intro: 'Você pode configurar os merges de pull request em {% data variables.product.product_location %} para corresponder ao seu fluxo de trabalho e preferências para gerenciar o histórico do Git.' +title: Configuring pull request merges +intro: 'You can configure pull request merges on {% data variables.location.product_location %} to match your workflow and preferences for managing Git history.' redirect_from: - /articles/configuring-pull-request-merges - /github/administering-a-repository/configuring-pull-request-merges @@ -21,11 +21,5 @@ children: - /managing-auto-merge-for-pull-requests-in-your-repository - /managing-the-automatic-deletion-of-branches shortTitle: Configure PR merges -ms.openlocfilehash: 625392c72ae470fffea4f92288aa7c3124bc18ab -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147580604' --- diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md index 11ab8bb458..16551aab62 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md @@ -1,6 +1,6 @@ --- -title: Renomear um branch -intro: É possível alterar o nome de um branch em um repositório. +title: Renaming a branch +intro: You can change the name of a branch in a repository. permissions: 'People with write permissions to a repository can rename a branch in the repository unless it is the [default branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch){% ifversion fpt or ghec or ghes > 3.3 %} or a [protected branch](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches){% endif %}. People with admin permissions can rename the default branch{% ifversion fpt or ghec or ghes > 3.3 %} and protected branches{% endif %}.' versions: fpt: '*' @@ -12,48 +12,42 @@ topics: redirect_from: - /github/administering-a-repository/renaming-a-branch - /github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch -ms.openlocfilehash: 6e30c7c2615f8b3dc21075e24298796febbce314 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145127101' --- -## Sobre a renomeação de branches +## About renaming branches -Você pode renomear um branch em um repositório em {% data variables.product.product_location %}. Para obter mais informações sobre branches, confira "[Sobre os branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)". +You can rename a branch in a repository on {% data variables.location.product_location %}. For more information about branches, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches))." -Ao renomear um branch em {% data variables.product.product_location %}, todas as URLs que contiverem o nome do branch antigo serão automaticamente redirecionadas para a URL equivalente para o branch renomeado. Atualizam-se também as políticas de proteção de branch também, bem como o branch base para pull requests abertos (incluindo aqueles para bifurcações) e rascunhos de versões. Depois que a renomeação for concluída, {% data variables.product.prodname_dotcom %} fornecerá instruções na página inicial do repositório direcionando os colaboradores para atualizar seus ambientes do Git locais. +When you rename a branch on {% data variables.location.product_location %}, any URLs that contain the old branch name are automatically redirected to the equivalent URL for the renamed branch. Branch protection policies are also updated, as well as the base branch for open pull requests (including those for forks) and draft releases. After the rename is complete, {% data variables.product.prodname_dotcom %} provides instructions on the repository's home page directing contributors to update their local Git environments. -Embora as URLs do arquivo sejam automaticamente redirecionadas, as URLs do arquivo não processado não são redirecionadas. Além disso, o {% data variables.product.prodname_dotcom %} não executará nenhum redirecionamento se os usuários executarem um `git pull` par o nome de branch anterior. +Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name. -Os fluxos de trabalho do {% data variables.product.prodname_actions %} não seguem as renomeações, ou seja, se o repositório publicar uma ação, qualquer pessoa que usar essa ação com `@{old-branch-name}` será interrompida. Você deve considerar adicionar um novo branch com o conteúdo original mais um relatório de commit adicional informando que o nome do branch está obsoleto e sugerindo que os usuários façam a migração para o novo nome do branche. +{% data variables.product.prodname_actions %} workflows do not follow renames, so if your repository publishes an action, anyone using that action with `@{old-branch-name}` will break. You should consider adding a new branch with the original content plus an additional commit reporting that the branch name is deprecated and suggesting that users migrate to the new branch name. -## Renomear um branch +## Renaming a branch {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.navigate-to-branches %} -1. Na lista de branches, à direita do branch que você deseja renomear, clique em {% octicon "pencil" aria-label="The edit icon" %}. - ![Ícone de lápis à direita do branch que você deseja renomear](/assets/images/help/branch/branch-rename-edit.png) -1. Digite um novo nome para o branch. - ![Campo de texto usado para digitar o novo nome do branch](/assets/images/help/branch/branch-rename-type.png) -1. Revise as informações sobre ambientes locais e clique em **Renomear branch**. - ![Informações de ambiente local e botão "Renomear branch"](/assets/images/help/branch/branch-rename-rename.png) +1. In the list of branches, to the right of the branch you want to rename, click {% octicon "pencil" aria-label="The edit icon" %}. + ![Pencil icon to the right of branch you want to rename](/assets/images/help/branch/branch-rename-edit.png) +1. Type a new name for the branch. + ![Text field for typing new branch name](/assets/images/help/branch/branch-rename-type.png) +1. Review the information about local environments, then click **Rename branch**. + ![Local environment information and "Rename branch" button](/assets/images/help/branch/branch-rename-rename.png) -## Atualizar um clone local após alterações de nome do branch +## Updating a local clone after a branch name changes -Após renomear um branch em um repositório em {% data variables.product.product_name %}, qualquer colaborador com um clone local do repositório deverá atualizar o clone. +After you rename a branch in a repository on {% data variables.product.product_name %}, any collaborator with a local clone of the repository will need to update the clone. -A partir do clone local do repositório em um computador, execute os seguintes comandos para atualizar o nome do branch padrão. +From the local clone of the repository on a computer, run the following commands to update the name of the default branch. ```shell -$ git branch -m OLD-BRANCH-NAME NEW-BRANCH-NAME +$ git branch -m OLD-BRANCH-NAME NEW-BRANCH-NAME $ git fetch origin -$ git branch -u origin/NEW-BRANCH-NAME NEW-BRANCH-NAME +$ git branch -u origin/NEW-BRANCH-NAME NEW-BRANCH-NAME $ git remote set-head origin -a ``` -Opcionalmente, execute o comando a seguir para remover as referências de rastreamento para o nome do branch antigo. +Optionally, run the following command to remove tracking references to the old branch name. ``` $ git remote prune origin ``` diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md index 6a7b18c469..014c709c08 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md @@ -1,6 +1,6 @@ --- -title: Sobre repositórios -intro: Um repositório contém todos os arquivos do seu projeto e o histórico de revisão de cada arquivo. Você pode discutir e gerenciar o trabalho do projeto dentro do repositório. +title: About repositories +intro: A repository contains all of your project's files and each file's revision history. You can discuss and manage your project's work within the repository. redirect_from: - /articles/about-repositories - /github/creating-cloning-and-archiving-repositories/about-repositories @@ -18,119 +18,123 @@ versions: ghec: '*' topics: - Repositories -ms.openlocfilehash: e4893e18de51f4d4918eacd3cb4d6da1c0323a1b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147444400' --- -## Sobre repositórios -Você pode possuir repositórios individualmente ou compartilhar a propriedade de repositórios com outras pessoas em uma organização. +## About repositories -É possível restringir quem tem acesso a um repositório escolhendo a visibilidade do repositório. Para obter mais informações, confira "[Sobre a visibilidade do repositório](#about-repository-visibility)". +You can own repositories individually, or you can share ownership of repositories with other people in an organization. -Para repositórios possuídos pelo usuário, você pode fornecer a outras pessoas acesso de colaborador para que elas possam colaborar no seu projeto. Se um repositório pertencer a uma organização, você poderá fornecer aos integrantes da organização permissões de acesso para colaboração no seu repositório. Para obter mais informações, confira "[Níveis de permissão para um repositório da conta pessoal](/articles/permission-levels-for-a-user-account-repository/)" e "[Funções de repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)". +You can restrict who has access to a repository by choosing the repository's visibility. For more information, see "[About repository visibility](#about-repository-visibility)." -{% ifversion fpt or ghec %} Com o {% data variables.product.prodname_free_team %} para contas pessoais e de organizações, você pode trabalhar com colaboradores ilimitados em repositórios públicos ilimitados, com um conjunto completo de recursos, ou em repositórios privados ilimitados, com um conjunto limitado de recursos. Para obter ferramentas avançadas para repositórios privados, você pode fazer o upgrade para {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %} ou {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %} {% else %} Cada pessoa e organização pode ser o proprietário de repositórios ilimitados e convidar um número ilimitado de colaboradores em todos os repositórios. +For user-owned repositories, you can give other people collaborator access so that they can collaborate on your project. If a repository is owned by an organization, you can give organization members access permissions to collaborate on your repository. For more information, see "[Permission levels for a personal account repository](/articles/permission-levels-for-a-user-account-repository/)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." + +{% ifversion fpt or ghec %} +With {% data variables.product.prodname_free_team %} for personal accounts and organizations, you can work with unlimited collaborators on unlimited public repositories with a full feature set, or unlimited private repositories with a limited feature set. To get advanced tooling for private repositories, you can upgrade to {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %} +{% else %} +Each person and organization can own unlimited repositories and invite an unlimited number of collaborators to all repositories. {% endif %} -Você pode usar repositórios para gerenciar seu trabalho e colaborar com outras pessoas. -- Você pode usar problemas para coletar feedback do usuário, relatar erros de software e organizar tarefas que você gostaria de realizar. Para obter mais informações, confira "[Sobre os problemas](/github/managing-your-work-on-github/about-issues)".{% ifversion fpt or ghec %} +You can use repositories to manage your work and collaborate with others. +- You can use issues to collect user feedback, report software bugs, and organize tasks you'd like to accomplish. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues)."{% ifversion fpt or ghec %} - {% data reusables.discussions.you-can-use-discussions %}{% endif %} -- É possível usar pull requests para propor alterações em um repositório. Para obter mais informações, confira "[Sobre as solicitações de pull](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)". -- Você pode usar quadros de projeto para organizar e priorizar seus problemas e pull requests. Para obter mais informações, confira "[Sobre os quadros de projetos](/github/managing-your-work-on-github/about-project-boards)". +- You can use pull requests to propose changes to a repository. For more information, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)." +- You can use project boards to organize and prioritize your issues and pull requests. For more information, see "[About project boards](/github/managing-your-work-on-github/about-project-boards)." {% data reusables.repositories.repo-size-limit %} -## Sobre a visibilidade do repositório +## About repository visibility -É possível restringir quem tem acesso a um repositório escolhendo a visibilidade de um repositório: {% ifversion ghes or ghec %}público, interno ou privado{% elsif ghae %}privado ou interno{% else %} público ou privado{% endif %}. +You can restrict who has access to a repository by choosing a repository's visibility: {% ifversion ghes or ghec %}public, internal, or private{% elsif ghae %}private or internal{% else %} public or private{% endif %}. {% ifversion fpt or ghec or ghes %} -Ao criar um repositório, você pode optar por tornar o repositório público ou privado.{% ifversion ghec or ghes %} Se você estiver criando o repositório em uma organização{% ifversion ghec %} que pertence a uma conta corporativa{% endif %}, você também pode optar por tornar o repositório interno.{% endif %}{% endif %}{% ifversion fpt %} Os repositórios em organizações que usam {% data variables.product.prodname_ghe_cloud %} e são propriedade de uma conta corporativa também podem ser criados com visibilidade interna. Para obter mais informações, confira [a documentação do {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories). +When you create a repository, you can choose to make the repository public or private.{% ifversion ghec or ghes %} If you're creating the repository in an organization{% ifversion ghec %} that is owned by an enterprise account{% endif %}, you can also choose to make the repository internal.{% endif %}{% endif %}{% ifversion fpt %} Repositories in organizations that use {% data variables.product.prodname_ghe_cloud %} and are owned by an enterprise account can also be created with internal visibility. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories). {% elsif ghae %} -Ao criar um repositório pertencente à sua conta pessoal, o repositório é sempre privado. Ao criar um repositório pertencente a uma organização, você pode optar por tornar o repositório privado ou interno. +When you create a repository owned by your personal account, the repository is always private. When you create a repository owned by an organization, you can choose to make the repository private or internal. {% endif %} {%- ifversion fpt or ghec %} -- Os repositórios públicos podem ser acessados por todos na Internet. -- Os repositórios só podem ser acessados por você, pelas pessoas com as quais você compartilha explicitamente o acesso e, para repositórios da organização, por determinados integrantes da organização. +- Public repositories are accessible to everyone on the internet. +- Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members. {%- elsif ghes %} -- Se {% data variables.product.product_location %} não estiver em modo privado ou por trás de um firewall, repositórios públicos poderão ser acessados por todos na internet. Caso contrário, os repositórios públicos estarão disponíveis para todos usando {% data variables.product.product_location %}, incluindo colaboradores externos. -- Os repositórios só podem ser acessados por você, pelas pessoas com as quais você compartilha explicitamente o acesso e, para repositórios da organização, por determinados integrantes da organização. +- If {% data variables.location.product_location %} is not in private mode or behind a firewall, public repositories are accessible to everyone on the internet. Otherwise, public repositories are available to everyone using {% data variables.location.product_location %}, including outside collaborators. +- Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members. {%- elsif ghae %} -- Os repositórios só podem ser acessados por você, pelas pessoas com as quais você compartilha explicitamente o acesso e, para repositórios da organização, por determinados integrantes da organização. -{%- endif %} {%- ifversion ghec or ghes or ghae %} -- Repositórios internos podem ser acessados por todos os integrantes da empresa. Para obter mais informações, confira "[Sobre os repositórios internos](#about-internal-repositories)". +- Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members. +{%- endif %} +{%- ifversion ghec or ghes or ghae %} +- Internal repositories are accessible to all enterprise members. For more information, see "[About internal repositories](#about-internal-repositories)." {%- endif %} -Os proprietários da organização sempre têm acesso a todos os repositórios criados em uma organização. Para obter mais informações, confira "[Funções de repositório de uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)". +Organization owners always have access to every repository created in an organization. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." -As pessoas com permissões de administrador para um repositório podem alterar a visibilidade de um repositório existente. Para obter mais informações, confira "[Como configurar a visibilidade do repositório](/github/administering-a-repository/setting-repository-visibility)". +People with admin permissions for a repository can change an existing repository's visibility. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)." {% ifversion ghes or ghec or ghae %} -## Sobre repositórios internos +## About internal repositories -{% data reusables.repositories.about-internal-repos %} Para obter mais informações sobre o InnerSource, confira o white paper "[Uma introdução ao InnerSource](https://resources.github.com/whitepapers/introduction-to-innersource/)" do {% data variables.product.prodname_dotcom %}. +{% data reusables.repositories.about-internal-repos %} For more information on innersource, see {% data variables.product.prodname_dotcom %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)." -Todos os integrantes da empresa têm permissões de leitura no repositório interno, mas os repositórios internos não são visíveis para pessoas {% ifversion fpt or ghec %}que estão fora da empresa{% else %}que não são integrantes de qualquer organização{% endif %}, incluindo colaboradores externos em repositórios da organização. Para obter mais informações, confira "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" e "[Funções de repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)". +All enterprise members have read permissions to the internal repository, but internal repositories are not visible to people {% ifversion fpt or ghec %}outside of the enterprise{% else %}who are not members of any organization{% endif %}, including outside collaborators on organization repositories. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." -{% ifversion ghes %} {% note %} +{% ifversion ghes %} +{% note %} -**Observação:** um usuário precisa fazer parte de uma organização para ser membro da empresa e ter acesso aos repositórios internos. Se um usuário em {% data variables.product.product_location %} não for um integrante de qualquer organização, esse usuário não terá acesso a repositórios internos. +**Note:** A user must be part of an organization to be an enterprise member and have access to internal repositories. If a user on {% data variables.location.product_location %} is not a member of any organization, that user will not have access to internal repositories. -{% endnote %} {% endif %} +{% endnote %} +{% endif %} {% data reusables.repositories.internal-repo-default %} -{% ifversion ghec %}A menos que sua empresa use {% data variables.product.prodname_emus %}, os membros{% else %}Membros{% endif %} dela podem criar fork de qualquer repositório de propriedade de uma organização na empresa. O repositório bifurcado pertencerá à conta pessoal do integrante e a visibilidade da bifurcação será privada. Se um usuário for removido de todas as organizações pertencentes à empresa, essas bifurcações do usuário dos repositórios internos do usuário serão removidas automaticamente. +{% ifversion ghec %}Unless your enterprise uses {% data variables.product.prodname_emus %}, members{% else %}Members{% endif %} of the enterprise can fork any internal repository owned by an organization in the enterprise. The forked repository will belong to the member's personal account, and the visibility of the fork will be private. If a user is removed from all organizations owned by the enterprise, that user's forks of internal repositories are removed automatically. -{% ifversion ghec %} {% note %} +{% ifversion ghec %} +{% note %} -**Observação:** {% data variables.product.prodname_managed_users_caps %} não pode criar fork de repositórios internos. Para obter mais informações, confira "[Sobre as {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-user-accounts)". +**Note:** {% data variables.enterprise.prodname_managed_users_caps %} cannot fork internal repositories. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-user-accounts)." -{% endnote %} {% endif %} {% endif %} +{% endnote %} +{% endif %} +{% endif %} -## Limites para exibição de conteúdo e diffs no repositório +## Limits for viewing content and diffs in a repository -Determinados tipos de recursos podem ser muito grandes, exigindo processamento elevado no{% data variables.product.product_name %}. Por isso, limites são estabelecidos para assegurar que as solicitações sejam completadas em um período razoável. +Certain types of resources can be quite large, requiring excessive processing on {% data variables.product.product_name %}. Because of this, limits are set to ensure requests complete in a reasonable amount of time. -A maioria dos limites abaixo afetam o {% data variables.product.product_name %} e a API. +Most of the limits below affect both {% data variables.product.product_name %} and the API. -### Limites de texto +### Text limits -Os arquivos de texto com mais de **512 KB** são sempre exibidos como texto sem formatação. O código não realça a sintaxe, e os arquivos em prosa não são convertidos em HTML (como Markdown, AsciiDoc *etc.* ). +Text files over **512 KB** are always displayed as plain text. Code is not syntax highlighted, and prose files are not converted to HTML (such as Markdown, AsciiDoc, *etc.*). -Os arquivos de texto com mais de **5 MB** só ficam disponíveis por meio das respectivas URLs brutas, que são fornecidas por meio de `{% data variables.product.raw_github_com %}`, por exemplo, `https://{% data variables.product.raw_github_com %}/octocat/Spoon-Knife/master/index.html`. Clique no botão **Bruto** para obter a URL bruta de um arquivo. +Text files over **5 MB** are only available through their raw URLs, which are served through `{% data variables.product.raw_github_com %}`; for example, `https://{% data variables.product.raw_github_com %}/octocat/Spoon-Knife/master/index.html`. Click the **Raw** button to get the raw URL for a file. -### Limites de diff +### Diff limits -Os diffs podem ficar muito grandes, por isso impusemos estas restrições em diffs para commits, pull requests e visualizações comparadas: +Because diffs can become very large, we impose these limits on diffs for commits, pull requests, and compare views: -- Em uma solicitação de pull, nenhuma comparação total pode exceder *20 mil linhas que podem ser carregadas* ou *1 MB* de dados de comparação brutos. -- Nenhuma comparação de arquivo único pode exceder *20 mil linhas que podem ser carregadas* ou *500 KB* de dados de comparação brutos. *Quatrocentas linhas* e *20 KB* são carregados automaticamente para um só arquivo. -- O número máximo de arquivos em uma só comparação é limitado a *300*. -- O número máximo de arquivos renderizáveis (como imagens, PDFs e arquivos GeoJSON) em uma só comparação é limitado a *25*. +- In a pull request, no total diff may exceed *20,000 lines that you can load* or *1 MB* of raw diff data. +- No single file's diff may exceed *20,000 lines that you can load* or *500 KB* of raw diff data. *Four hundred lines* and *20 KB* are automatically loaded for a single file. +- The maximum number of files in a single diff is limited to *300*. +- The maximum number of renderable files (such as images, PDFs, and GeoJSON files) in a single diff is limited to *25*. -Algumas partes de um diff limitado podem ser exibidas, mas qualquer excedente de limite não é mostrado. +Some portions of a limited diff may be displayed, but anything exceeding the limit is not shown. -### Limites de listas de commits +### Commit listings limits -As páginas de solicitações de pull e de exibição de comparação mostram uma lista de commits entre as revisões `base` e `head`. Essas listas são limitadas a **250** commits. Caso o limite seja excedido, uma observação indicará que commits adicionais estão presentes (mas não são mostrados). +The compare view and pull requests pages display a list of commits between the `base` and `head` revisions. These lists are limited to **250** commits. If they exceed that limit, a note indicates that additional commits are present (but they're not shown). -## Leitura adicional +## Further reading -- "[Como criar um repositório](/articles/creating-a-new-repository)" -- "[Sobre os forks](/github/collaborating-with-pull-requests/working-with-forks/about-forks)" -- "[Colaboração com problemas e solicitações de pull](/categories/collaborating-with-issues-and-pull-requests)" -- "[Como gerenciar seu trabalho no {% data variables.product.prodname_dotcom %}](/categories/managing-your-work-on-github/)" -- "[Como administrar um repositório](/categories/administering-a-repository)" -- "[Como visualizar dados de repositório com grafos](/categories/visualizing-repository-data-with-graphs/)" -- "[Sobre os wikis](/communities/documenting-your-project-with-wikis/about-wikis)" -- "[Glossário do {% data variables.product.prodname_dotcom %}](/articles/github-glossary)" +- "[Creating a new repository](/articles/creating-a-new-repository)" +- "[About forks](/github/collaborating-with-pull-requests/working-with-forks/about-forks)" +- "[Collaborating with issues and pull requests](/categories/collaborating-with-issues-and-pull-requests)" +- "[Managing your work on {% data variables.product.prodname_dotcom %}](/categories/managing-your-work-on-github/)" +- "[Administering a repository](/categories/administering-a-repository)" +- "[Visualizing repository data with graphs](/categories/visualizing-repository-data-with-graphs/)" +- "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)" +- "[{% data variables.product.prodname_dotcom %} glossary](/articles/github-glossary)" diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/cloning-a-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/cloning-a-repository.md index bd261f0efa..0fd1cafda3 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/cloning-a-repository.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/cloning-a-repository.md @@ -1,6 +1,6 @@ --- -title: Clonar um repositório -intro: 'Ao criar um repositório no {% data variables.product.product_location %}, ele passa a existir como um repositório remoto. É possível clonar o repositório para criar uma cópia local no seu computador e sincronizar entre os dois locais.' +title: Cloning a repository +intro: 'When you create a repository on {% data variables.location.product_location %}, it exists as a remote repository. You can clone your repository to create a local copy on your computer and sync between the two locations.' redirect_from: - /articles/cloning-a-repository - /articles/cloning-a-repository-from-github @@ -13,26 +13,25 @@ versions: ghec: '*' topics: - Repositories -ms.openlocfilehash: fbe00d1568a2f746362d434e769aef2f3466bcf1 -ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/12/2022 -ms.locfileid: '145127098' --- -## Sobre clonagem de um repositório +## About cloning a repository -Você pode clonar um repositório do {% data variables.product.product_location %} para o seu computador local para facilitar a correção de conflitos de merge, adicionar ou remover arquivos e fazer push de commits maiores. Ao clonar um repositório, você copia o repositório do {% data variables.product.product_location %} para a sua máquina local. +You can clone a repository from {% data variables.location.product_location %} to your local computer to make it easier to fix merge conflicts, add or remove files, and push larger commits. When you clone a repository, you copy the repository from {% data variables.location.product_location %} to your local machine. -Clonar um repositório extrai uma cópia completa de todos os dados do repositório que o {% data variables.product.product_location %} tem nesse momento, incluindo todas as versões de cada arquivo e pasta do projeto. Você pode fazer push das alterações no repositório remoto no {% data variables.product.product_location %} ou extrair as alterações de outras pessoas no {% data variables.product.product_location %}. Para obter mais informações, confira "[Como usar o Git](/github/getting-started-with-github/using-git)". +Cloning a repository pulls down a full copy of all the repository data that {% data variables.location.product_location %} has at that point in time, including all versions of every file and folder for the project. You can push your changes to the remote repository on {% data variables.location.product_location %}, or pull other people's changes from {% data variables.location.product_location %}. For more information, see "[Using Git](/github/getting-started-with-github/using-git)". -É possível clonar o repositório existente ou clonar o repositório existente de outra pessoa para contribuir para um projeto. +You can clone your existing repository or clone another person's existing repository to contribute to a project. -## Clonar um repositório +## Cloning a repository {% webui %} -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.copy-clone-url %} {% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.change-current-directory-clone %} {% data reusables.command_line.git-clone-url %} {% data reusables.command_line.local-clone-created %} +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.copy-clone-url %} +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.command_line.change-current-directory-clone %} +{% data reusables.command_line.git-clone-url %} +{% data reusables.command_line.local-clone-created %} {% endwebui %} @@ -40,54 +39,59 @@ Clonar um repositório extrai uma cópia completa de todos os dados do repositó {% data reusables.cli.cli-learn-more %} -Para clonar um repositório localmente, use o subcomando `repo clone`. Substitua o parâmetro `repository` pelo nome do repositório. Por exemplo, `octo-org/octo-repo`, `monalisa/octo-repo` ou `octo-repo`. Se a parte `OWNER/` do argumento do repositório `OWNER/REPO` for omitida, ele usará como padrão o nome do usuário autenticador. +To clone a repository locally, use the `repo clone` subcommand. Replace the `repository` parameter with the repository name. For example, `octo-org/octo-repo`, `monalisa/octo-repo`, or `octo-repo`. If the `OWNER/` portion of the `OWNER/REPO` repository argument is omitted, it defaults to the name of the authenticating user. ```shell -gh repo clone repository +gh repo clone REPOSITORY ``` -Você também pode usar o URL do GitHub para clonar um repositório. +You can also use the GitHub URL to clone a repository. ```shell -gh repo clone https://github.com/cli/cli +gh repo clone https://github.com/PATH-TO/REPOSITORY ``` {% endcli %} {% desktop %} -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.open-with-github-desktop %} -4. Siga as solicitações no {% data variables.product.prodname_desktop %} para concluir o clone. +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.open-with-github-desktop %} +4. Follow the prompts in {% data variables.product.prodname_desktop %} to complete the clone. -Para obter mais informações, confira "[Como 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/)". +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/)." {% enddesktop %} -## Clonar um repositório vazio +## Cloning an empty repository -Um repositório vazio não contém arquivos. Muitas vezes, isso é feito se você não inicializar o repositório com um README ao criá-lo. +An empty repository contains no files. It's often made if you don't initialize the repository with a README when creating it. {% data reusables.repositories.navigate-to-repo %} -2. Para clonar seu repositório usando a linha de comando por HTTPS, em "Configuração rápida", clique em {% octicon "clippy" aria-label="The clipboard icon" %}. Para clonar o repositório usando uma chave SSH, incluindo um certificado emitido pela autoridade de certificação SSH da sua organização, clique em **SSH** e em {% octicon "clippy" aria-label="The clipboard icon" %}. - ![Botão usado para clonar o repositório vazio por meio da URL](/assets/images/help/repository/empty-https-url-clone-button.png) +2. To clone your repository using the command line using HTTPS, under "Quick setup", click {% octicon "clippy" aria-label="The clipboard icon" %}. To clone the repository using an SSH key, including a certificate issued by your organization's SSH certificate authority, click **SSH**, then click {% octicon "clippy" aria-label="The clipboard icon" %}. + ![Empty repository clone URL button](/assets/images/help/repository/empty-https-url-clone-button.png) - Como alternativa, para clonar seu repositório no Desktop, clique em {% octicon "desktop-download" aria-label="The desktop download button" %} **Configurar no Desktop** e siga os prompts para concluir o clone. - ![Botão usado para clonar o repositório vazio no Desktop](/assets/images/help/repository/empty-desktop-clone-button.png) + Alternatively, to clone your repository in Desktop, click {% octicon "desktop-download" aria-label="The desktop download button" %} **Set up in Desktop** and follow the prompts to complete the clone. + ![Empty repository clone desktop button](/assets/images/help/repository/empty-desktop-clone-button.png) -{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.change-current-directory-clone %} {% data reusables.command_line.git-clone-url %} {% data reusables.command_line.local-clone-created %} +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.command_line.change-current-directory-clone %} +{% data reusables.command_line.git-clone-url %} +{% data reusables.command_line.local-clone-created %} -## Solucionar problemas de erros de clonagem +## Troubleshooting cloning errors -Ao clonar um repositório, é possível que você encontre alguns erros. +When cloning a repository it's possible that you might encounter some errors. -Se você não conseguir clonar um repositório, verifique se: +If you're unable to clone a repository, check that: -- Você consegue conectar-se usando HTTPS. Para obter mais informações, confira "[Erros de clonagem HTTPS](/github/creating-cloning-and-archiving-repositories/https-cloning-errors)". -- Você tem permissão para acessar o repositório que você deseja clonar. Para obter mais informações, confira "[Erro: repositório não encontrado](/github/creating-cloning-and-archiving-repositories/error-repository-not-found)". -- O branch-padrão que você deseja clonar ainda existe. Para obter mais informações, confira "[Erro: o HEAD remoto refere-se a uma referência inexistente. Não é possível fazer check-out](/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors#error-remote-head-refers-to-nonexistent-ref-unable-to-checkout)". +- You can connect using HTTPS. For more information, see "[HTTPS cloning errors](/github/creating-cloning-and-archiving-repositories/https-cloning-errors)." +- You have permission to access the repository you want to clone. For more information, see "[Error: Repository not found](/github/creating-cloning-and-archiving-repositories/error-repository-not-found)." +- The default branch you want to clone still exists. For more information, see "[Error: Remote HEAD refers to nonexistent ref, unable to checkout](/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors#error-remote-head-refers-to-nonexistent-ref-unable-to-checkout)." {% ifversion fpt or ghec %} -## Leitura adicional +## Further reading -- "[Solução de problemas de conectividade](/articles/troubleshooting-connectivity-problems)" {% endif %} +- "[Troubleshooting connectivity problems](/articles/troubleshooting-connectivity-problems)" +{% endif %} diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md index 5122ec6d51..a94ca77b5a 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md @@ -1,6 +1,6 @@ --- -title: Duplicar um repositório -intro: 'Para manter um espelho de um repositório sem a bifurcação, é possível executar um comando especial de clone e, em seguida, fazer push do espelho para o novo repositório.' +title: Duplicating a repository +intro: 'To maintain a mirror of a repository without forking it, you can run a special clone command, then mirror-push to the new repository.' redirect_from: - /articles/duplicating-a-repo - /articles/duplicating-a-repository @@ -13,98 +13,92 @@ versions: ghec: '*' topics: - Repositories -ms.openlocfilehash: c9cc58acd7f3b69ff277830bef8dc50fed02c2b6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145127082' --- {% ifversion fpt or ghec %} {% note %} -**Observação:** se você tem um projeto hospedado em outro sistema de controle de versão, importe automaticamente seu projeto para o {% data variables.product.prodname_dotcom %} usando a ferramenta Importador do {% data variables.product.prodname_dotcom %}. Para obter mais informações, confira "[Sobre o Importador do {% data variables.product.prodname_dotcom %}](/get-started/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)". +**Note:** If you have a project hosted on another version control system, you can automatically import your project to {% data variables.product.prodname_dotcom %} using the {% data variables.product.prodname_dotcom %} Importer tool. For more information, see "[About {% data variables.product.prodname_dotcom %} Importer](/get-started/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)." {% endnote %} {% endif %} -Antes de efetuar push do repositório original para a nova cópia ou _espelho_ do repositório, você precisa [criar o repositório](/articles/creating-a-new-repository) no {% data variables.product.product_location %}. Nesses exemplos, `exampleuser/new-repository` ou `exampleuser/mirrored` são os espelhos. +Before you can push the original repository to your new copy, or _mirror_, of the repository, you must [create the new repository](/articles/creating-a-new-repository) on {% data variables.location.product_location %}. In these examples, `exampleuser/new-repository` or `exampleuser/mirrored` are the mirrors. -## Espelhar um repositório +## Mirroring a repository {% data reusables.command_line.open_the_multi_os_terminal %} -2. Crie um clone bare do repositório. +2. Create a bare clone of the repository. ```shell - $ git clone --bare https://{% data variables.command_line.codeblock %}/exampleuser/old-repository.git + $ git clone --bare https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/OLD-REPOSITORY.git ``` -3. Faça espelhamento/push no novo repositório. +3. Mirror-push to the new repository. ```shell - $ cd old-repository.git - $ git push --mirror https://{% data variables.command_line.codeblock %}/exampleuser/new-repository.git + $ cd OLD-REPOSITORY.git + $ git push --mirror https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/NEW-REPOSITORY.git ``` -4. Remova o repositório local temporário que você criou anteriormente. +4. Remove the temporary local repository you created earlier. ```shell $ cd .. - $ rm -rf old-repository.git + $ rm -rf OLD-REPOSITORY.git ``` -## Espelhar um repositório que contém objetos do {% data variables.large_files.product_name_long %} +## Mirroring a repository that contains {% data variables.large_files.product_name_long %} objects {% data reusables.command_line.open_the_multi_os_terminal %} -2. Crie um clone bare do repositório. Substitua o exemplo de nome de usuário pelo nome da pessoa ou da organização a quem pertence o repositório e substitua o exemplo de nome de repositório pelo nome do repositório que você deseja duplicar. +2. Create a bare clone of the repository. Replace the example username with the name of the person or organization who owns the repository, and replace the example repository name with the name of the repository you'd like to duplicate. ```shell - $ git clone --bare https://{% data variables.command_line.codeblock %}/exampleuser/old-repository.git + $ git clone --bare https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/OLD-REPOSITORY.git ``` -3. Navegue até o repositório que você acabou de clonar. +3. Navigate to the repository you just cloned. ```shell - $ cd old-repository.git + $ cd OLD-REPOSITORY.git ``` -4. Extraia os objetos do {% data variables.large_files.product_name_long %} do repositório. +4. Pull in the repository's {% data variables.large_files.product_name_long %} objects. ```shell $ git lfs fetch --all ``` -5. Faça espelhamento/push no novo repositório. +5. Mirror-push to the new repository. ```shell - $ git push --mirror https://{% data variables.command_line.codeblock %}/exampleuser/new-repository.git + $ git push --mirror https://{% data variables.command_line.codeblock %}EXAMPLE-USER/NEW-REPOSITORY.git ``` -6. Faça push nos objetos do {% data variables.large_files.product_name_long %} do repositório no seu espelho. +6. Push the repository's {% data variables.large_files.product_name_long %} objects to your mirror. ```shell - $ git lfs push --all https://github.com/exampleuser/new-repository.git + $ git lfs push --all https://github.com/EXAMPLE-USER/NEW-REPOSITORY.git ``` -7. Remova o repositório local temporário que você criou anteriormente. +7. Remove the temporary local repository you created earlier. ```shell $ cd .. - $ rm -rf old-repository.git + $ rm -rf OLD-REPOSITORY.git ``` -## Espelhar um repositório em outro local +## Mirroring a repository in another location -Se você deseja espelhar um repositório em outro local e ainda obter atualizações do original, é possível clonar um espelho e fazer push das alterações periodicamente. +If you want to mirror a repository in another location, including getting updates from the original, you can clone a mirror and periodically push the changes. {% data reusables.command_line.open_the_multi_os_terminal %} -2. Crie um clone bare espelhado do repositório. +2. Create a bare mirrored clone of the repository. ```shell - $ git clone --mirror https://{% data variables.command_line.codeblock %}/exampleuser/repository-to-mirror.git + $ git clone --mirror https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/REPOSITORY-TO-MIRROR.git ``` -3. Defina o local de push no espelho. +3. Set the push location to your mirror. ```shell - $ cd repository-to-mirror - $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/exampleuser/mirrored + $ cd REPOSITORY-TO-MIRROR + $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/MIRRORED ``` -Assim como um clone bare, um clone espelhado inclui todos os branches remotes e tags, mas todas as referências locais serão substituídas todas as vezes que você fizer fetch, assim ele sempre será o mesmo do repositório original. O push no espelho é simplificado pela configuração da URL para pushes. +As with a bare clone, a mirrored clone includes all remote branches and tags, but all local references will be overwritten each time you fetch, so it will always be the same as the original repository. Setting the URL for pushes simplifies pushing to your mirror. -4. Para atualizar o espelho, obtenha atualizações e faça push. +4. To update your mirror, fetch updates and push. ```shell $ git fetch -p origin $ git push --mirror ``` {% ifversion fpt or ghec %} -## Leitura adicional +## Further reading -* "[Como efetuar push das alterações para o GitHub](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github#pushing-changes-to-github)" -* "[Sobre o Git Large File Storage e o GitHub Desktop](/desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop)" -* "[Sobre o Importador do GitHub](/get-started/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)" +* "[Pushing changes to GitHub](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github#pushing-changes-to-github)" +* "[About Git Large File Storage and GitHub Desktop](/desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop)" +* "[About GitHub Importer](/get-started/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)" {% endif %} diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md index 68b533c1d4..86cdc8a075 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md @@ -1,6 +1,6 @@ --- -title: Restaurar um repositório excluído -intro: '{% ifversion ghes or ghae %}Um proprietário da empresa{% elsif fpt or ghec %}Você{% endif %} pode restaurar alguns repositórios excluídos para recuperar o conteúdo.' +title: Restoring a deleted repository +intro: '{% ifversion ghes or ghae %}An enterprise owner{% elsif fpt or ghec %}You{% endif %} can restore some deleted repositories to recover their contents.' permissions: '{% ifversion ghes or ghae %}{% elsif fpt or ghec %}Anyone can restore deleted repositories that were owned by their own personal account. Organization owners can restore deleted repositories that were owned by the organization.{% endif %}' redirect_from: - /articles/restoring-a-deleted-repository @@ -14,40 +14,43 @@ versions: topics: - Repositories shortTitle: Restore deleted repository -ms.openlocfilehash: 233785cc42ac6dd97a35d042186ae198dd69502a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146200095' --- + {% ifversion ghes or ghae %} -Normalmente, os repositórios excluídos podem ser restaurados em até 90 dias por um proprietário da empresa{% ifversion ghes %} no {% data variables.product.product_location %}{% endif %}. Para obter mais informações, confira "[Como restaurar um repositório excluído](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)". +Usually, deleted repositories can be restored within 90 days by an enterprise owner{% ifversion ghes %} on {% data variables.location.product_location %}{% endif %}. For more information, see "[Restoring a deleted repository](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)." {% else %} -## Sobre a restauração do repositório +## About repository restoration -Um repositório excluído pode ser restaurado em até 90 dias, a menos que ele fizesse parte de uma rede de bifurcação que atualmente não está vazia. Uma rede de bifurcação consiste em um repositório principal, nas bifurcações do repositório e nas bifurcações das bifurcações do repositório. Se o repositório fazia parte de uma rede de bifurcação, ele não poderá ser restaurado, a menos que todos os outros repositórios na rede sejam excluídos ou tenham sido desanexados da rede. Para obter mais informações sobre forks, confira "[Sobre os forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)". +A deleted repository can be restored within 90 days, unless the repository was part of a fork network that is not currently empty. A fork network consists of a parent repository, the repository's forks, and forks of the repository's forks. If your repository was part of a fork network, it cannot be restored unless every other repository in the network is deleted or has been detached from the network. For more information about forks, see "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)." -Se desejar restaurar um repositório que fazia parte de uma rede de bifurcação que atualmente não está vazia, contate o {% data variables.contact.contact_support %}. +If you want to restore a repository that was part of a fork network that is not currently empty, you can contact {% data variables.contact.contact_support %}. -Depois que um repositório é excluído, pode levar até uma hora para que ele seja disponibilizado para restauração. +It can take up to an hour after a repository is deleted before that repository is available for restoration. -Restaurar um repositório não vai restaurar anexos de versão nem permissões de equipe. Os problemas que são restaurados não serão etiquetados. +Restoring a repository will not restore release attachments or team permissions. Issues that are restored will not be labeled. -## Restaurar um repositório excluído que pertencia a uma conta pessoal +## Restoring a deleted repository that was owned by a personal account -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.repo-tab %} {% data reusables.user-settings.deleted-repos %} {% data reusables.user-settings.restore-repo %} {% data reusables.user-settings.restore-confirmation %} +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.repo-tab %} +{% data reusables.user-settings.deleted-repos %} +{% data reusables.user-settings.restore-repo %} +{% data reusables.user-settings.restore-confirmation %} -## Restaurar um repositório excluído que pertencia a uma organização +## Restoring a deleted repository that was owned by an organization -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.deleted-repos %} {% data reusables.user-settings.restore-repo %} {% data reusables.user-settings.restore-confirmation %} +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +{% data reusables.organizations.deleted-repos %} +{% data reusables.user-settings.restore-repo %} +{% data reusables.user-settings.restore-confirmation %} -## Leitura adicional +## Further reading -- "[Como excluir um repositório](/articles/deleting-a-repository)" +- "[Deleting a repository](/articles/deleting-a-repository)" {% endif %} diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md index 7ac01a2f12..21b3f9b46b 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md @@ -1,6 +1,6 @@ --- -title: Solucionar problemas de erros de clonagem -intro: 'Se você tiver problemas para clonar um repositório, verifique estes erros mais comuns.' +title: Troubleshooting cloning errors +intro: 'If you''re having trouble cloning a repository, check these common errors.' redirect_from: - /articles/error-the-requested-url-returned-error-403 - /articles/error-the-requested-url-returned-error-401 @@ -19,45 +19,41 @@ versions: ghec: '*' topics: - Repositories -ms.openlocfilehash: 60a5ff0350fed34841099c18f495b185b75f9832 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147093139' --- -## Erros de clonagem HTTPs -Existem alguns erros comuns ao usar HTTPS com o Git. Esses erros normalmente indicam que você tem uma versão antiga do Git ou que você não tem acesso ao repositório. +## HTTPS cloning errors -Segue aqui um exemplo de erro HTTPS que você pode receber: +There are a few common errors when using HTTPS with Git. These errors usually indicate you have an old version of Git, or you don't have access to the repository. + +Here's an example of an HTTPS error you might receive: ```shell > error: The requested URL returned error: 401 while accessing -> https://{% data variables.command_line.codeblock %}/user/repo.git/info/refs?service=git-receive-pack +> https://{% data variables.command_line.codeblock %}/USER/REPO.git/info/refs?service=git-receive-pack > fatal: HTTP request failed ``` ```shell > Error: The requested URL returned error: 403 while accessing -> https://{% data variables.command_line.codeblock %}/user/repo.git/info/refs +> https://{% data variables.command_line.codeblock %}/USER/REPO.git/info/refs > fatal: HTTP request failed ``` ```shell -> Error: https://{% data variables.command_line.codeblock %}/user/repo.git/info/refs not found: did you run git +> Error: https://{% data variables.command_line.codeblock %}/USER/REPO.git/info/refs not found: did you run git > update-server-info on the server? ``` -### Verifique sua versão do Git +### Check your Git version -Não há uma versão mínima necessária do Git para interagir com {% data variables.product.product_name %}, mas achamos que a versão 1.7.10 é uma versão estável e confortável, e que está disponível em muitas plataformas. Você sempre pode [baixar a última versão no site do Git](https://git-scm.com/downloads). +There's no minimum Git version necessary to interact with {% data variables.product.product_name %}, but we've found version 1.7.10 to be a comfortable stable version that's available on many platforms. You can always [download the latest version on the Git website](https://git-scm.com/downloads). -### Confirme que o remote está correto +### Ensure the remote is correct -O repositório que você está tentando fazer fetch deve existir em {% data variables.product.product_location %} e a URL diferencia maiúsculas de minúsculas. +The repository you're trying to fetch must exist on {% data variables.location.product_location %}, and the URL is case-sensitive. -Encontre a URL do repositório local abrindo a linha de comando e digitando `git remote -v`: +You can find the URL of the local repository by opening the command line and +typing `git remote -v`: ```shell $ git remote -v @@ -74,86 +70,89 @@ $ git remote -v > origin https://github.com/ghost/ReactiveCocoa.git (push) ``` -Como alternativa, você pode alterar a URL por meio do nosso aplicativo do [{% data variables.product.prodname_desktop %}](https://desktop.github.com/). +Alternatively, you can change the URL through our +[{% data variables.product.prodname_desktop %}](https://desktop.github.com/) application. -### Forneça um token de acesso +### Provide an access token -Para acessar {% data variables.product.prodname_dotcom %}, você deve efetuar a autenticação com um token de acesso pessoal em vez de sua senha. Para obter mais informações, confira "[Como criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)". +To access {% data variables.product.prodname_dotcom %}, you must authenticate with a {% data variables.product.pat_generic %} instead of your password. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." {% data reusables.command_line.provide-an-access-token %} -### Verificar suas permissões +### Check your permissions -Quando for solicitado um nome e senha, certifique-se de usar uma conta que tenha acesso ao repositório. +When prompted for a username and password, make sure you use an account that has access to the repository. {% tip %} -**Dica**: se não quiser inserir suas credenciais toda vez que interagir com o repositório remoto, ative o [cache de credenciais](/github/getting-started-with-github/caching-your-github-credentials-in-git). Se você já está usando o cache de credenciais, certifique-se de que o seu computador tem as credenciais corretas armazenadas em cache. Credenciais incorretas ou desatualizadas causarão falha na autenticação. +**Tip**: If you don't want to enter your credentials every time you interact with the remote repository, you can turn on [credential caching](/github/getting-started-with-github/caching-your-github-credentials-in-git). If you are already using credential caching, please make sure that your computer has the correct credentials cached. Incorrect or out of date credentials will cause authentication to fail. {% endtip %} -### Substitua por SSH +### Use SSH instead -Se você configurou as chaves SSH previamente, é possível usar a URL clone SSH em vez de HTTPS. Para obter mais informações, confira "[Sobre os repositórios remotos](/github/getting-started-with-github/about-remote-repositories)". +If you've previously set up SSH keys, you can use the SSH clone URL instead of HTTPS. For more information, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)." -## Erro: repositório não encontrado +## Error: Repository not found -{% ifversion fpt or ghae or ghec %}Se você receber este erro ao clonar um repositório, isso significará que o repositório não existe ou que você não tem permissão para acessá-lo.{% else %}Se você receber este erro ao clonar um repositório, isso significará que o repositório não existe, você não tem permissão para acessá-lo ou o {% data variables.product.product_location %} está no modo privado.{% endif %} Existem algumas soluções para esse erro, dependendo da causa. +{% ifversion fpt or ghae or ghec %}If you see this error when cloning a repository, it means that the repository does not exist or you do not have permission to access it.{% else %}If you see this error when cloning a repository, it means that the repository does not exist, you do not have permission to access it, or {% data variables.location.product_location %} is in private mode.{% endif %} There are a few solutions to this error, depending on the cause. -### Verificar a ortografia +### Check your spelling -Erros de digitação acontecem e os nomes dos repositórios diferenciam maiúsculas de minúsculas. Se você tentar clonar `git@{% data variables.command_line.codeblock %}:user/repo.git`, mas o repositório for realmente chamado `User/Repo`, você receberá esse erro. +Typos happen, and repository names are case-sensitive. If you try to clone `git@{% data variables.command_line.codeblock %}:user/repo.git`, but the repository is really named `User/Repo` you will receive this error. -Para evitar o erro ao clonar, sempre copie e cole a URL clone da página do repositório. Para obter mais informações, confira "[Como clonar um repositório](/articles/cloning-a-repository)". +To avoid this error, when cloning, always copy and paste the clone URL from the repository's page. For more information, see "[Cloning a repository](/articles/cloning-a-repository)." -Para atualizar o repositório remoto em um repositório existente, confira "[Como gerenciar repositórios remotos](/github/getting-started-with-github/managing-remote-repositories)". +To update the remote on an existing repository, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)". -### Verifique as permissões +### Checking your permissions -Se você está tentando clonar um repositório privado, mas não tem permissão para visualizar o repositório, ocorrerá esse erro. +If you are trying to clone a private repository but do not have permission to view the repository, you will receive this error. -Assegure-se de ter acesso ao repositório como: +Make sure that you have access to the repository in one of these ways: -* Proprietário do repositório -* Um [colaborador](/articles/inviting-collaborators-to-a-personal-repository) no repositório -* Um [membro de uma equipe](/articles/adding-organization-members-to-a-team) que tem acesso ao repositório (se o repositório pertence a uma organização) +* The owner of the repository +* A [collaborator](/articles/inviting-collaborators-to-a-personal-repository) on the repository +* A [member of a team](/articles/adding-organization-members-to-a-team) that has access to the repository (if the repository belongs to an organization) -### Verifique seu acesso SSH +### Check your SSH access -Em raras circunstâncias, você pode não ter o devido acesso SSH a um repositório. +In rare circumstances, you may not have the proper SSH access to a repository. -Confirme que a chave SSH em uso está associada a sua conta pessoal em {% data variables.product.product_name %}. Verifique isso digitando o seguinte na linha de comando: +You should ensure that the SSH key you are using is attached to your personal account on {% data variables.product.product_name %}. You can check this by typing +the following into the command line: ```shell $ ssh -T git@{% data variables.command_line.codeblock %} -> Hi username! You've successfully authenticated, but GitHub does not +> Hi USERNAME! You've successfully authenticated, but GitHub does not > provide shell access. ``` -{% ifversion fpt or ghec %} Se o repositório pertencer a uma organização e você estiver usando uma chave SSH gerada por um aplicativo OAuth, o acesso ao aplicativo OAuth poderá ser restringido por um proprietário da organização. Para obter mais informações, confira "[Sobre as restrições de acesso do Aplicativo OAuth](/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions)". +{% ifversion fpt or ghec %} +If the repository belongs to an organization and you're using an SSH key generated by an OAuth App, OAuth App access may have been restricted by an organization owner. For more information, see "[About OAuth App access restrictions](/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions)." {% endif %} -Para obter mais informações, confira [Como adicionar uma nova chave SSH à sua conta do GitHub](/articles/adding-a-new-ssh-key-to-your-github-account). +For more information, see [Adding a new SSH key to your GitHub account](/articles/adding-a-new-ssh-key-to-your-github-account). {% ifversion ghes %} -### Verifique se sua instância está em modo privado +### Check if your instance is in private mode -Caso o administrador do site tenha habilitado o modo privado na sua instância do GitHub Enterprise, os clones anônimos em `git://` ficam desabilitados. Caso não consiga clonar um repositório, contate o administrador de seu site. +If your site administrator has enabled private mode on your GitHub Enterprise instance, anonymous clones over `git://` will be disabled. If you are unable to clone a repository, contact your site administrator. {% endif %} -### Verifique se o repositório realmente existe +### Check that the repository really exists -Se nada resolver o problema, confirme se o repositório realmente existe em {% data variables.product.product_location %}! -Caso você esteja tentando fazer push para um repositório que não existe, você receberá essa mensagem de erro. +If all else fails, make sure that the repository really exists on {% data variables.location.product_location %}! +If you're trying to push to a repository that doesn't exist, you'll get this error. -## Erro: HEAD remote faz referência a um ref inexistente, não é possível fazer checkout +## Error: Remote HEAD refers to nonexistent ref, unable to checkout -O erro ocorre se o branch padrão de um repositório foi excluído em {% data variables.product.product_location %}. +This error occurs if the default branch of a repository has been deleted on {% data variables.location.product_location %}. -É simples identificar esse erro; o Git avisará quando você tentar clonar o repositório: +Detecting this error is simple; Git will warn you when you try to clone the repository: ```shell -$ git clone https://{% data variables.command_line.codeblock %}/user/repo.git +$ git clone https://{% data variables.command_line.codeblock %}/USER/REPO.git # Clone a repo > Cloning into 'repo'... > remote: Counting objects: 66179, done. @@ -164,10 +163,10 @@ $ git clone https://{% data variables.command_line.codeblock %}/user/ warning: remote HEAD refers to nonexistent ref, unable to checkout. ``` -Para corrigir o erro, você precisa ser o administrador do repositório em {% data variables.product.product_location %}. -O ideal será [alterar o branch padrão](/github/administering-a-repository/changing-the-default-branch) do repositório. +To fix the error, you'll need to be an administrator of the repository on {% data variables.location.product_location %}. +You'll want to [change the default branch](/github/administering-a-repository/changing-the-default-branch) of the repository. -Depois de fazer isso, você obterá uma lista de todos os branches disponíveis a partir da linha de comando: +After that, you can get a list of all the available branches from the command line: ```shell $ git branch -a @@ -177,7 +176,7 @@ $ git branch -a > remotes/origin/new-main ``` -Em seguida, mude para o novo branch: +Then, you can just switch to your new branch: ```shell $ git checkout new-main diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md index 53cf00e556..343a994c1e 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md @@ -58,12 +58,12 @@ To reduce the size of your CODEOWNERS file, consider using wildcard patterns to A CODEOWNERS file uses a pattern that follows most of the same rules used in [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) files. The pattern is followed by one or more {% data variables.product.prodname_dotcom %} usernames or team names using the standard `@username` or `@org/team-name` format. Users and teams must have explicit `write` access to the repository, even if the team's members already have access. -{% ifversion fpt or ghec%}In most cases, you{% else %}You{% endif %} can also refer to a user by an email address that has been added to their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, for example `user@example.com`. {% ifversion fpt or ghec %} You cannot use an email address to refer to a {% data variables.product.prodname_managed_user %}. For more information about {% data variables.product.prodname_managed_users %}, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} +{% ifversion fpt or ghec%}In most cases, you{% else %}You{% endif %} can also refer to a user by an email address that has been added to their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, for example `user@example.com`. {% ifversion fpt or ghec %} You cannot use an email address to refer to a {% data variables.enterprise.prodname_managed_user %}. For more information about {% data variables.enterprise.prodname_managed_users %}, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} CODEOWNERS paths are case sensitive, because {% data variables.product.prodname_dotcom %} uses a case sensitive file system. Since CODEOWNERS are evaluated by {% data variables.product.prodname_dotcom %}, even systems that are case insensitive (for example, macOS) must use paths and files that are cased correctly in the CODEOWNERS file. {% ifversion codeowners-errors %} -If any line in your CODEOWNERS file contains invalid syntax, that line will be skipped. When you navigate to the CODEOWNERS file in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, you can see any errors highlighted. A list of errors in a repository's CODEOWNERS file is also accessible via the API. For more information, see "[Repositories](/rest/reference/repos#list-codeowners-errors)" in the REST API documentation. +If any line in your CODEOWNERS file contains invalid syntax, that line will be skipped. When you navigate to the CODEOWNERS file in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, you can see any errors highlighted. A list of errors in a repository's CODEOWNERS file is also accessible via the API. For more information, see "[Repositories](/rest/reference/repos#list-codeowners-errors)" in the REST API documentation. {% else %} If any line in your CODEOWNERS file contains invalid syntax, the file will not be detected and will not be used to request reviews. {% endif %} diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md index 6adb9f0e13..6df07234e6 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md @@ -1,6 +1,6 @@ --- -title: Licenciar um repositório -intro: 'Os repositórios públicos no GitHub são usados frequentemente para compartilhar softwares de código aberto. Para que seu repositório seja realmente de código aberto, você precisará licenciá-lo para que outros tenham a liberdade de usar, alterar e distribuir o software.' +title: Licensing a repository +intro: 'Public repositories on GitHub are often used to share open source software. For your repository to truly be open source, you''ll need to license it so that others are free to use, change, and distribute the software.' redirect_from: - /articles/open-source-licensing - /articles/licensing-a-repository @@ -12,93 +12,87 @@ versions: ghec: '*' topics: - Repositories -ms.openlocfilehash: f49dad5c20909647b1d7da7bb44a80a771337966 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147881793' --- -## Escolher a licença ideal +## Choosing the right license -Criamos [choosealicense.com](https://choosealicense.com) para ajudar você a entender como licenciar seu código. Uma licença de software descreve o que pode e não pode ser feito com seu código-fonte, assim é importante tomar uma decisão fundamentada. +We created [choosealicense.com](https://choosealicense.com), to help you understand how to license your code. A software license tells others what they can and can't do with your source code, so it's important to make an informed decision. -Você não tem qualquer obrigação de escolher uma licença. Entretanto, sem uma licença, são aplicadas as leis padrão de copyright, o que significa que você detém todos os direitos de seu código-fonte e ninguém poderá reproduzir, distribuir ou criar derivativos de seu trabalho. Se você está criando um projeto de código aberto, incentivamos fortemente que você contemple uma licença de código aberto. O [Guia de Código Aberto](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project) fornece diretrizes adicionais sobre como escolher a licença correta para seu projeto. +You're under no obligation to choose a license. However, without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work. If you're creating an open source project, we strongly encourage you to include an open source license. The [Open Source Guide](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project) provides additional guidance on choosing the correct license for your project. {% note %} -**Observação:** se você publicar seu código-fonte em um repositório público no {% data variables.product.product_name %}, {% ifversion fpt or ghec %}de acordo com os [Termos de Serviço](/free-pro-team@latest/github/site-policy/github-terms-of-service), {% endif %}outros usuários do {% data variables.product.product_location %} terão o direito de ver seu repositório e criar forks dele. Se você já criou um repositório e não quer mais que os usuários tenham acesso a ele, você pode torná-lo privado. Ao alterar a visibilidade de um repositório para privado, as bifurcações existentes ou cópias locais criadas por outros usuários continuarão existindo. Para obter mais informações, confira "[Como configurar a visibilidade do repositório](/github/administering-a-repository/setting-repository-visibility)". +**Note:** If you publish your source code in a public repository on {% data variables.product.product_name %}, {% ifversion fpt or ghec %}according to the [Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service), {% endif %}other users of {% data variables.location.product_location %} have the right to view and fork your repository. If you have already created a repository and no longer want users to have access to the repository, you can make the repository private. When you change the visibility of a repository to private, existing forks or local copies created by other users will still exist. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)." {% endnote %} -## Identificar a localização da sua licença +## Determining the location of your license -A maioria das pessoas coloca o texto da licença em um arquivo chamado `LICENSE.txt` (`LICENSE.md` ou `LICENSE.rst`) na raiz do repositório. [Veja um exemplo do Hubot](https://github.com/github/hubot/blob/master/LICENSE.md). +Most people place their license text in a file named `LICENSE.txt` (or `LICENSE.md` or `LICENSE.rst`) in the root of the repository; [here's an example from Hubot](https://github.com/github/hubot/blob/master/LICENSE.md). -Alguns projetos incluem as informações sobre a licença no README. Por exemplo, um README de um projeto pode incluir uma observação declarando "Este projeto está licenciado nos termos da licença MIT." +Some projects include information about their license in their README. For example, a project's README may include a note saying "This project is licensed under the terms of the MIT license." -Como uma prática recomendada, incentivamos que você inclua o arquivo da licença no seu projeto. +As a best practice, we encourage you to include the license file with your project. -## Pesquisar no GitHub por tipo de licença +## Searching GitHub by license type -É possível filtrar repositórios com base nas licenças ou na família de licenças deles usando o qualificador `license` e a palavra-chave exata da licença: +You can filter repositories based on their license or license family using the `license` qualifier and the exact license keyword: -Licença | Palavra-chave da licença +License | License keyword --- | --- -| Licença Academic Free v3.0 | `afl-3.0` | -| Licença do Apache 2.0 | `apache-2.0` | -| Licença artística 2.0 | `artistic-2.0` | +| Academic Free License v3.0 | `afl-3.0` | +| Apache license 2.0 | `apache-2.0` | +| Artistic license 2.0 | `artistic-2.0` | | Boost Software License 1.0 | `bsl-1.0` | -| Licença "Simplificada" de duas cláusulas do BSD | `bsd-2-clause` | -| Licença "Nova" ou "Revisada" de três cláusulas do BSD | `bsd-3-clause` | -| Licença Completa de três cláusulas do BSD | `bsd-3-clause-clear` | -| Família de licenças do Creative Commons | `cc` | +| BSD 2-clause "Simplified" license | `bsd-2-clause` | +| BSD 3-clause "New" or "Revised" license | `bsd-3-clause` | +| BSD 3-clause Clear license | `bsd-3-clause-clear` | +| Creative Commons license family | `cc` | | Creative Commons Zero v1.0 Universal | `cc0-1.0` | -| Atribuição Creative Commons 4.0 | `cc-by-4.0` | -| Atribuição Compartilha Igual Creative Commons 4.0 | `cc-by-sa-4.0` | -| Licença pública WTFPL | `wtfpl` | -| Licença Educational Community v2.0 | `ecl-2.0` | -| Licença Pública do Eclipse 1.0 | `epl-1.0` | -| Licença Pública do Eclipse 2.0 | `epl-2.0` | -| Licença Pública da União Europeia 1.1 | `eupl-1.1` | -| Licença Pública Geral do LGNU Affero v3.0 | `agpl-3.0` | -| Família de Licenças Públicas Gerais do GNU | `gpl` | -| Licença Pública Geral do GNU v2.0 | `gpl-2.0` | -| Licença Pública Geral do GNU v3.0 | `gpl-3.0` | -| Família de Licenças Públicas Gerais Menores do GNU | `lgpl` | -| Licença Pública Geral Menor do GNU v2.1 | `lgpl-2.1` | -| Licença Pública Geral Menor do GNU v3.0 | `lgpl-3.0` | +| Creative Commons Attribution 4.0 | `cc-by-4.0` | +| Creative Commons Attribution Share Alike 4.0 | `cc-by-sa-4.0` | +| Do What The F*ck You Want To Public License | `wtfpl` | +| Educational Community License v2.0 | `ecl-2.0` | +| Eclipse Public License 1.0 | `epl-1.0` | +| Eclipse Public License 2.0 | `epl-2.0` | +| European Union Public License 1.1 | `eupl-1.1` | +| GNU Affero General Public License v3.0 | `agpl-3.0` | +| GNU General Public License family | `gpl` | +| GNU General Public License v2.0 | `gpl-2.0` | +| GNU General Public License v3.0 | `gpl-3.0` | +| GNU Lesser General Public License family | `lgpl` | +| GNU Lesser General Public License v2.1 | `lgpl-2.1` | +| GNU Lesser General Public License v3.0 | `lgpl-3.0` | | ISC | `isc` | -| Licença Pública do LaTeX Project v1.3c | `lppl-1.3c` | -| Licença Pública da Microsoft | `ms-pl` | +| LaTeX Project Public License v1.3c | `lppl-1.3c` | +| Microsoft Public License | `ms-pl` | | MIT | `mit` | -| Licença Pública Mozilla 2.0 | `mpl-2.0` | -| Licença de Software Livre 3.0 | `osl-3.0` | -| Licença do PostgreSQL | `postgresql` | -| Licença Sil Open Font 1.1 | `ofl-1.1` | -| Licença de Código Aberto da University of Illinois/NCSA | `ncsa` | -| A Unlicense | `unlicense` | -| Licença zLib | `zlib` | +| Mozilla Public License 2.0 | `mpl-2.0` | +| Open Software License 3.0 | `osl-3.0` | +| PostgreSQL License | `postgresql` | +| SIL Open Font License 1.1 | `ofl-1.1` | +| University of Illinois/NCSA Open Source License | `ncsa` | +| The Unlicense | `unlicense` | +| zLib License | `zlib` | -Quando você pesquisar uma família de licenças, os resultados incluirão todas as licenças daquela família. Por exemplo, quando você usar a consulta `license:gpl`, os resultados incluirão os repositórios licenciados sob a Licença Pública Geral do GNU v2.0 e a Licença Pública Geral do GNU v3.0. Para obter mais informações, confira "[Pesquisa em repositórios](/search-github/searching-on-github/searching-for-repositories/#search-by-license)". +When you search by a family license, your results will include all licenses in that family. For example, when you use the query `license:gpl`, your results will include repositories licensed under GNU General Public License v2.0 and GNU General Public License v3.0. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-by-license)." -## Identificar uma licença +## Detecting a license -[Licensee de código aberto do RubyGem](https://github.com/licensee/licensee) compara o arquivo *LICENSE* do repositório com uma pequena lista de licenças conhecidas. O Licensee também fornece a [API de Licenças](/rest/reference/licenses) e [fornece informações sobre como os repositórios do {% data variables.product.product_name %} são licenciados](https://github.com/blog/1964-open-source-license-usage-on-github-com). Se o repositório estiver usando uma licença que não está listada no [site Escolher uma Licença](https://choosealicense.com/appendix/), você poderá [solicitar a inclusão da licença](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). +[The open source Ruby gem Licensee](https://github.com/licensee/licensee) compares the repository's *LICENSE* file to a short list of known licenses. Licensee also provides the [Licenses API](/rest/reference/licenses) and [gives us insight into how repositories on {% data variables.product.product_name %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](https://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). -Caso o seu repositório use uma licença listada no site Choose a License que não aparece na parte superior da página do repositório, ele pode conter licenças múltiplas ou outras complexidades. Para que sua licença seja identificada, simplifique o arquivo *LICENSE* e anote a complexidade em algum outro local, como no arquivo *LEIAME* do repositório. +If your repository is using a license that is listed on the Choose a License website and it's not displaying clearly at the top of the repository page, it may contain multiple licenses or other complexity. To have your license detected, simplify your *LICENSE* file and note the complexity somewhere else, such as your repository's *README* file. -## Aplicar uma licença em um repositório com uma licença existente +## Applying a license to a repository with an existing license -O selecionador de licenças somente está disponível quando você cria um novo projeto no GitHub. Você pode adicionar uma licença manualmente usando o navegador. Para obter mais informações sobre como adicionar uma licença a um repositório, confira "[Como adicionar uma licença a um repositório](/articles/adding-a-license-to-a-repository)". +The license picker is only available when you create a new project on GitHub. You can manually add a license using the browser. For more information on adding a license to a repository, see "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)." -![Captura de tela do selecionador de licenças no GitHub.com](/assets/images/help/repository/repository-license-picker.png) +![Screenshot of license picker on GitHub.com](/assets/images/help/repository/repository-license-picker.png) -## Isenção de responsabilidade +## Disclaimer -O objetivo das iniciativas de licenciamento de código aberto do GitHub é oferecer um ponto de partida para ajudar você a tomar uma decisão fundamentada. O GitHub apresenta informações sobre licenças para ajudar os usuários a conseguir informações sobre licenças de código aberto e sobre os projetos que as usam. Esperamos que seja útil, mas esteja ciente de que não somos advogados e que cometemos erros como qualquer pessoa. Por esse motivo, o GitHub fornece as informações de forma "como se apresentam" e não faz garantia em relação a qualquer informação ou licença fornecida em ou por meio dela, e exime-se da responsabilidade por danos resultantes do uso das informações de licença. Se você tiver quaisquer dúvidas com relação à licença ideal para seu código ou quaisquer outras questões legais relacionadas a ele, sempre é melhor consultar um profissional. +The goal of GitHub's open source licensing efforts is to provide a starting point to help you make an informed choice. GitHub displays license information to help users get information about open source licenses and the projects that use them. We hope it helps, but please keep in mind that we’re not lawyers and that we make mistakes like everyone else. For that reason, GitHub provides the information on an "as-is" basis and makes no warranties regarding any information or licenses provided on or through it, and disclaims liability for damages resulting from using the license information. If you have any questions regarding the right license for your code or any other legal issues relating to it, it’s always best to consult with a professional. -## Leitura adicional +## Further reading -- A seção "[O Lado Legal do Código Aberto](https://opensource.guide/legal/)" dos Guias de Código Aberto {% ifversion fpt or ghec %} +- The Open Source Guides' section "[The Legal Side of Open Source](https://opensource.guide/legal/)"{% ifversion fpt or ghec %} - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %} diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md index c04ccf1e31..188b4b10dc 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md @@ -1,29 +1,25 @@ --- -title: Como gerenciar a política de aprovação de confirmação para seu repositório -intro: 'Você pode exigir que os usuários aprovem automaticamente os commits que fazem no seu repositório usando a interface da Web de {% data variables.product.product_name %}.' +title: Managing the commit signoff policy for your repository +intro: You can require users to automatically sign off on the commits they make to your repository using {% data variables.product.product_name %}'s web interface. versions: feature: commit-signoffs permissions: Organization owners and repository administrators can require all commits to a repository to be signed off by the commit author. topics: - Repositories shortTitle: Manage the commit signoff policy -ms.openlocfilehash: 4002f0767497cb2b0db9e43c9783e0c2982c8d33 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147410686' --- -## Sobre as aprovações de commit -As aprovações de commit permitem que os usuários afirmem que um commit está em conformidade com as regras e o licenciamento que regem um repositório. Você pode habilitar as aprovações de commit obrigatórias em repositórios individuais para usuários que fazem commit por meio de {% data variables.product.product_location %}, tornando a aprovação de um commit uma parte tranquila do processo de commit. Depois que as aprovações de commit obrigatórias forem habilitadas para um repositório, cada commit feito nesse repositório por meio da interface da Web de {% data variables.product.product_location %} serão aprovadas automaticamente pelo autor do commit. +## About commit signoffs -Os proprietários da organização também podem habilitar as aprovações de commit obrigatórias no nível da organização. Para obter mais informações, confira "[Como gerenciar a política de aprovação de confirmação para sua organização](/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization)". +Commit signoffs enable users to affirm that a commit complies with the rules and licensing governing a repository. You can enable compulsory commit signoffs on individual repositories for users committing through {% data variables.location.product_location %}'s web interface, making signing off on a commit a seemless part of the commit process. Once compulsory commit signoffs are enabled for a repository, every commit made to that repository through {% data variables.location.product_location %}'s web interface will automatically be signed off on by the commit author. + +Organization owners can also enable compulsory commit signoffs at the organization level. For more information, see "[Managing the commit signoff policy for your organization](/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization)." {% data reusables.repositories.commit-signoffs %} -## Habilitar ou desabilitar as aprovações de commit obrigatórias para seu repositório +## Enabling or disabling compulsory commit signoffs for your repository -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -1. Selecione **Exigir que os colaboradores aprovem commits baseados na Web**. - ![Captura de tela da opção Exigir que os colaboradores aprovem commits baseados na Web](/assets/images/help/repository/require-signoffs.png) +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +1. Select **Require contributors to sign off on web-based commits**. + ![Screenshot of Require contributors to sign off on web-based commits](/assets/images/help/repository/require-signoffs.png) \ No newline at end of file diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md index cf3c452578..9d2e1efb2c 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md @@ -1,6 +1,6 @@ --- -title: Definir a visibilidade do repositório -intro: Você pode escolher quem pode visualizar seu repositório. +title: Setting repository visibility +intro: You can choose who can view your repository. redirect_from: - /articles/making-a-private-repository-public - /articles/making-a-public-repository-private @@ -16,88 +16,89 @@ versions: topics: - Repositories shortTitle: Repository visibility -ms.openlocfilehash: 2ccdafed8e9efe2bf352033d8fa632147f6bb32b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146332018' --- -## Sobre alterações de visibilidade do repositório +## About repository visibility changes -Os proprietários da organização podem restringir a capacidade de alterar a visibilidade do repositório apenas para os proprietários da organização. Para obter mais informações, confira "[Como restringir as alterações de visibilidade do repositório na sua organização](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)". +Organization owners can restrict the ability to change repository visibility to organization owners only. For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)." {% ifversion ghec %} -Os membros de um {% data variables.product.prodname_emu_enterprise %} só podem definir a visibilidade de repositórios pertencentes à sua conta pessoal como privada, e os repositórios das organizações de sua empresa só podem ser privados ou internos. Para obter mais informações, confira "[Sobre os {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)". +Members of an {% data variables.enterprise.prodname_emu_enterprise %} can only set the visibility of repositories owned by their personal account to private, and repositories in their enterprise's organizations can only be private or internal. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." {% endif %} -Recomendamos revisar as seguintes advertências antes de alterar a visibilidade de um repositório. +We recommend reviewing the following caveats before you change the visibility of a repository. {% ifversion ghes or ghae %} {% warning %} -**Aviso:** as alterações na visibilidade de um repositório grande ou de uma rede de repositórios podem afetar a integridade dos dados. As alterações na visibilidade também podem ter efeitos não intencionais nas bifurcações. {% data variables.product.company_short %} recomenda o seguinte antes de alterar a visibilidade da rede de um repositório. +**Warning:** Changes to the visibility of a large repository or repository network may affect data integrity. Visibility changes can also have unintended effects on forks. {% data variables.product.company_short %} recommends the following before changing the visibility of a repository network. -- Aguarde um período de atividade reduzida em {% data variables.product.product_location %}. +- Wait for a period of reduced activity on {% data variables.location.product_location %}. -- Entre em contato com o {% ifversion ghes %}administrador do site{% elsif ghae %}proprietário da empresa{% endif %} antes de prosseguir. O {% ifversion ghes %}administrador do site{% elsif ghae %}proprietário da empresa{% endif %} pode entrar em contato com o {% data variables.contact.contact_ent_support %} para obter mais diretrizes. +- Contact your {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %} before proceeding. Your {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %} can contact {% data variables.contact.contact_ent_support %} for further guidance. {% endwarning %} {% endif %} -### Tornar um repositório privado +### Making a repository private {% ifversion fpt or ghes or ghec %} -* O {% data variables.product.product_name %} desanexará os forks públicos do repositório público e os colocará em uma nova rede. Os forks públicos não se tornam privados.{% endif %} {%- ifversion ghes or ghec or ghae %} -* Se você alterar a visibilidade de um repositório interno para privado, {% data variables.product.prodname_dotcom %} removerá bifurcações que pertencem a qualquer usuário sem acesso ao repositório privado recente. {% ifversion fpt or ghes or ghec %}A visibilidade de qualquer fork também será alterada para privada.{% elsif ghae %}Se o repositório interno tiver algum fork, a visibilidade das forks já será privada.{% endif %} Para obter mais informações, confira "[O que acontece com os forks quando um repositório é excluído ou altera a visibilidade?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)" +* {% data variables.product.product_name %} will detach public forks of the public repository and put them into a new network. Public forks are not made private.{% endif %} +{%- ifversion ghes or ghec or ghae %} +* 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. {% ifversion fpt or ghes or ghec %}The visibility of any forks will also change to private.{% elsif ghae %}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)" {%- endif %} {%- ifversion fpt %} -* Se você estiver usando {% data variables.product.prodname_free_user %} para contas pessoais ou organizações, alguns recursos não estarão disponíveis no repositório depois de alterar a visibilidade para privada. Qualquer site publicado do {% data variables.product.prodname_pages %} terá sua publicação cancelada automaticamente. Se você adicionou um domínio personalizado ao site do {% data variables.product.prodname_pages %}, deverá remover ou atualizar os registros de DNS antes de tornar o repositório privado para evitar o risco de uma aquisição de domínio. Para obter mais informações, confira "[Produtos do {% data variables.product.company_short %}](/get-started/learning-about-github/githubs-products) e "[Como gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". +* If you're using {% data variables.product.prodname_free_user %} for personal accounts or organizations, some features won't be available in the repository after you change the visibility to private. Any published {% data variables.product.prodname_pages %} site will be automatically unpublished. 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 "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products) and "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)." {%- endif %} {%- ifversion fpt or ghec %} -* {% data variables.product.prodname_dotcom %} não incluirá mais o repositório no {% data variables.product.prodname_archive %}. Para obter mais informações, confira "[Sobre o arquivamento de conteúdo e de dados no {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)". -* As funcionalidades de {% data variables.product.prodname_GH_advanced_security %}, como {% data variables.product.prodname_code_scanning %}, irão parar de funcionar{% ifversion ghec %} a menos que o repositório pertença a uma organização que faz parte de uma empresa com uma licença para {% data variables.product.prodname_advanced_security %} e estações livres suficientes.{% endif %} {% data reusables.advanced-security.more-info-ghas %} {%- endif %} +* {% 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)." +* {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working{% ifversion ghec %} unless the repository is owned by an organization that is part of an enterprise with a license for {% data variables.product.prodname_advanced_security %} and sufficient spare seats{% endif %}. {% data reusables.advanced-security.more-info-ghas %} +{%- endif %} {%- ifversion ghes %} -* O acesso de leitura anônimo do Git não está mais disponível. Para obter mais informações, confira "[Como habilitar o acesso de leitura anônimo do Git para um repositório](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository)". +* Anonymous Git read access is no longer available. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository)." {%- endif %} {% ifversion ghes or ghec or ghae %} -### Tornar um repositório interno +### Making a repository internal -* Todas as bifurcações do repositório permanecerão na rede do repositório e a {% data variables.product.product_name %} manterá a relação entre o repositório raiz e a bifurcação. Para obter mais informações, confira "[O que acontece com os forks quando um repositório é excluído ou altera a visibilidade?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)" +* Any forks of the repository will remain in the repository network, and {% data variables.product.product_name %} maintains the relationship between the root repository and the fork. 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)" {% endif %} {% ifversion fpt or ghes or ghec %} -### Tornar um repositório público +### Making a repository public -* O {% data variables.product.product_name %} irá destacar bifurcações privadas e transformá-las em um repositório privado independente. Para obter mais informações, confira "[O que acontece com os forks quando um repositório é excluído ou altera a visibilidade?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)"{% ifversion fpt or ghec %} -* Se você estiver convertendo seu repositório privado em um repositório público, como parte de uma movimentação para a criação de um projeto de código aberto, confira os [Guias de Código Aberto](http://opensource.guide) para obter dicas e diretrizes úteis. Faça também um curso gratuito sobre como gerenciar um projeto de código aberto com o [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Quando seu repositório é público, você também pode visualizar o perfil da comunidade do repositório para ver se os projetos atendem às práticas recomendadas de suporte aos contribuidores. Para obter mais informações, confira "[Como ver seu perfil da comunidade](/articles/viewing-your-community-profile)". -* O repositório automaticamente receberá acesso aos recursos de {% data variables.product.prodname_GH_advanced_security %}. +* {% data variables.product.product_name %} will detach private forks and turn them into a standalone private repository. 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#changing-a-private-repository-to-a-public-repository)"{% ifversion fpt or ghec %} +* If you're converting your private repository to a public repository as part of a move toward creating an open source project, see the [Open Source Guides](http://opensource.guide) for helpful tips and guidelines. You can also take a free course on managing an open source project with [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Once your repository is public, you can also view your repository's community profile to see whether your project meets best practices for supporting contributors. For more information, see "[Viewing your community profile](/articles/viewing-your-community-profile)." +* The repository will automatically gain access to {% data variables.product.prodname_GH_advanced_security %} features. -Para obter informações sobre como aprimorar a segurança do repositório, confira "[Como proteger seu repositório](/code-security/getting-started/securing-your-repository)".{% endif %} +For information about improving repository security, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."{% endif %} {% endif %} -## Alterar a visibilidade de um repositório +## Changing a repository's visibility -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -3. Em "Zona de Perigo", à direita de "Alterar visibilidade do repositório", clique em **Alterar visibilidade**. - ![Botão Alterar visibilidade](/assets/images/help/repository/repo-change-vis.png) -4. Selecione uma visibilidade. -{% ifversion fpt or ghec %} ![Caixa de diálogo de opções para visibilidade do repositório](/assets/images/help/repository/repo-change-select.png){% else %} ![Caixa de diálogo de opções para visibilidade do repositório](/assets/images/enterprise/repos/repo-change-select.png){% endif %} -5. Para verificar se você está alterando a visibilidade do repositório correto, digite o nome do repositório que deseja alterar a visibilidade. -6. Clique em **Entendi. Alterar a visibilidade do repositório**. -{% ifversion fpt or ghec %} ![Botão Confirmar alteração de visibilidade do repositório](/assets/images/help/repository/repo-change-confirm.png){% else %} ![Botão Confirmar alteração de visibilidade do repositório](/assets/images/enterprise/repos/repo-change-confirm.png){% endif %} +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. Under "Danger Zone", to the right of to "Change repository visibility", click **Change visibility**. + ![Change visibility button](/assets/images/help/repository/repo-change-vis.png) +4. Select a visibility. +{% ifversion fpt or ghec %} + ![Dialog of options for repository visibility](/assets/images/help/repository/repo-change-select.png){% else %} + ![Dialog of options for repository visibility](/assets/images/enterprise/repos/repo-change-select.png){% endif %} +5. To verify that you're changing the correct repository's visibility, type the name of the repository you want to change the visibility of. +6. Click **I understand, change repository visibility**. +{% ifversion fpt or ghec %} + ![Confirm change of repository visibility button](/assets/images/help/repository/repo-change-confirm.png){% else %} + ![Confirm change of repository visibility button](/assets/images/enterprise/repos/repo-change-confirm.png){% endif %} -## Leitura adicional -- "[Sobre os repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)" +## Further reading +- "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)" diff --git a/translations/pt-BR/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md b/translations/pt-BR/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md index d7b2952713..4907c70c9c 100644 --- a/translations/pt-BR/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md +++ b/translations/pt-BR/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md @@ -1,6 +1,6 @@ --- -title: Adicionar um arquivo a um repositório -intro: 'Você pode fazer o upload e o commit de um arquivo existente para um repositório no {% data variables.product.product_name %} ou usando a linha de comando.' +title: Adding a file to a repository +intro: 'You can upload and commit an existing file to a repository on {% data variables.product.product_name %} or by using the command line.' redirect_from: - /articles/adding-a-file-to-a-repository - /github/managing-files-in-a-repository/adding-a-file-to-a-repository @@ -18,40 +18,37 @@ versions: topics: - Repositories shortTitle: Add a file -ms.openlocfilehash: da76e182a16b1f72b814882b816f487b8290f3be -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147578905' --- -## Adicionando um arquivo a um repositório em {% data variables.product.product_name %} -Os arquivos que você adiciona a um repositório por meio do navegador são limitados a {% data variables.large_files.max_github_browser_size %} por arquivo. É possível adicionar arquivos maiores, de até {% data variables.large_files.max_github_size %} cada um, usando a linha de comando. Para obter mais informações, confira "[Como adicionar um arquivo a um repositório usando a linha de comando](#adding-a-file-to-a-repository-using-the-command-line)". Para adicionar arquivos maiores que {% data variables.large_files.max_github_size %}, você deverá usar {% data variables.large_files.product_name_long %}. Para obter mais informações, confira "[Sobre grandes arquivos no {% data variables.product.product_name %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github)". +## Adding a file to a repository on {% data variables.product.product_name %} + +Files that you add to a repository via a browser are limited to {% data variables.large_files.max_github_browser_size %} per file. You can add larger files, up to {% data variables.large_files.max_github_size %} each, via the command line. For more information, see "[Adding a file to a repository using the command line](#adding-a-file-to-a-repository-using-the-command-line)." To add files larger than {% data variables.large_files.max_github_size %}, you must use {% data variables.large_files.product_name_long %}. For more information, see "[About large files on {% data variables.product.product_name %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github)." {% tip %} -**Dicas:** -- É possível fazer upload de vários arquivos no {% data variables.product.product_name %} ao mesmo tempo. +**Tips:** +- You can upload multiple files to {% data variables.product.product_name %} at the same time. - {% data reusables.repositories.protected-branches-block-web-edits-uploads %} {% endtip %} {% data reusables.repositories.navigate-to-repo %} -2. Acima da lista de arquivos, usando o menu suspenso **Adicionar arquivo**, clique em **Carregar arquivos**. - !["Carregar arquivos" no menu suspenso "Adicionar arquivo"](/assets/images/help/repository/upload-files-button.png) -3. Arraste e solte o arquivo ou a pasta que deseja fazer upload no repositório na árvore de arquivos. -![Área de arrastar e soltar](/assets/images/help/repository/upload-files-drag-and-drop.png) {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} -6. Clique em **Fazer commit das alterações**. -![Botão Fazer commit de alterações](/assets/images/help/repository/commit-changes-button.png) +2. Above the list of files, using the **Add file** drop-down, click **Upload files**. + !["Upload files" in the "Add file" dropdown](/assets/images/help/repository/upload-files-button.png) +3. Drag and drop the file or folder you'd like to upload to your repository onto the file tree. +![Drag and drop area](/assets/images/help/repository/upload-files-drag-and-drop.png) +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} +6. Click **Commit changes**. +![Commit changes button](/assets/images/help/repository/commit-changes-button.png) -## Adicionar um arquivo a um repositório usando a linha de comando +## Adding a file to a repository using the command line -Você pode enviar um arquivo existente para um repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} usando a linha de comando. +You can upload an existing file to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} using the command line. {% tip %} -**Dica:** você também pode [adicionar um arquivo existente a um repositório por meio do site do {% data variables.product.product_name %}](/articles/adding-a-file-to-a-repository). +**Tip:** You can also [add an existing file to a repository from the {% data variables.product.product_name %} website](/articles/adding-a-file-to-a-repository). {% endtip %} @@ -59,8 +56,10 @@ Você pode enviar um arquivo existente para um repositório em {% ifversion ghae {% data reusables.repositories.sensitive-info-warning %} -1. No seu computador, mova o arquivo do qual deseja fazer upload para o {% data variables.product.product_name %}, no diretório local que foi criado quando o repositório foi clonado. -{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.switching_directories_procedural %} {% data reusables.git.stage_for_commit %} +1. On your computer, move the file you'd like to upload to {% data variables.product.product_name %} into the local directory that was created when you cloned the repository. +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.command_line.switching_directories_procedural %} +{% data reusables.git.stage_for_commit %} ```shell $ git add . # Adds the file to your local repository and stages it for commit. {% data reusables.git.unstage-codeblock %} @@ -72,6 +71,6 @@ Você pode enviar um arquivo existente para um repositório em {% ifversion ghae ``` {% data reusables.git.git-push %} -## Leitura adicional +## Further reading -- "[Como adicionar um código hospedado localmente ao {% data variables.product.product_name %}](/get-started/importing-your-projects-to-github/importing-source-code-to-github//adding-locally-hosted-code-to-github)" +- "[Adding locally hosted code to {% data variables.product.product_name %}](/get-started/importing-your-projects-to-github/importing-source-code-to-github//adding-locally-hosted-code-to-github)" diff --git a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md index 358b0e8a2b..12765fb394 100644 --- a/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md +++ b/translations/pt-BR/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md @@ -40,11 +40,11 @@ shortTitle: Large files {% endnote %} -{% ifversion ghes %}By default, {% endif %}{% data variables.product.product_name %} blocks files larger than {% data variables.large_files.max_github_size %}. {% ifversion ghes %}However, a site administrator can configure a different limit for {% data variables.product.product_location %}. For more information, see "[Setting Git push limits](/enterprise/admin/guides/installation/setting-git-push-limits)."{% endif %} +{% ifversion ghes %}By default, {% endif %}{% data variables.product.product_name %} blocks files larger than {% data variables.large_files.max_github_size %}. {% ifversion ghes %}However, a site administrator can configure a different limit for {% data variables.location.product_location %}. For more information, see "[Setting Git push limits](/enterprise/admin/guides/installation/setting-git-push-limits)."{% endif %} To track files beyond this limit, you must use {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). For more information, see "[About {% data variables.large_files.product_name_long %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)." -If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %} instead of tracking the files. For more information, see "[Distributing large binaries](#distributing-large-binaries)." +If you need to distribute large files within your repository, you can create releases on {% data variables.location.product_location %} instead of tracking the files. For more information, see "[Distributing large binaries](#distributing-large-binaries)." Git is not designed to handle large SQL files. To share large databases with other developers, we recommend using [Dropbox](https://www.dropbox.com/). @@ -62,13 +62,13 @@ Git is not designed to serve as a backup tool. However, there are many solutions {% warning %} -**Warning**: These procedures will permanently remove files from the repository on your computer and {% data variables.product.product_location %}. If the file is important, make a local backup copy in a directory outside of the repository. +**Warning**: These procedures will permanently remove files from the repository on your computer and {% data variables.location.product_location %}. If the file is important, make a local backup copy in a directory outside of the repository. {% endwarning %} ### Removing a file added in the most recent unpushed commit -If the file was added with your most recent commit, and you have not pushed to {% data variables.product.product_location %}, you can delete the file and amend the commit: +If the file was added with your most recent commit, and you have not pushed to {% data variables.location.product_location %}, you can delete the file and amend the commit: {% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.switching_directories_procedural %} @@ -84,7 +84,7 @@ If the file was added with your most recent commit, and you have not pushed to { # Simply making a new commit won't work, as you need # to remove the file from the unpushed history as well ``` -5. Push your commits to {% data variables.product.product_location %}: +5. Push your commits to {% data variables.location.product_location %}: ```shell $ git push # Push our rewritten, smaller commit @@ -96,7 +96,7 @@ If you added a file in an earlier commit, you need to remove it from the reposit ## Distributing large binaries -If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %}. Releases allow you to package software, release notes, and links to binary files, for other people to use. For more information, visit "[About releases](/github/administering-a-repository/about-releases)." +If you need to distribute large files within your repository, you can create releases on {% data variables.location.product_location %}. Releases allow you to package software, release notes, and links to binary files, for other people to use. For more information, visit "[About releases](/github/administering-a-repository/about-releases)." {% ifversion fpt or ghec %} diff --git a/translations/pt-BR/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md b/translations/pt-BR/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md index 022e36298c..d16c96cd5e 100644 --- a/translations/pt-BR/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md +++ b/translations/pt-BR/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md @@ -1,6 +1,6 @@ --- -title: Obter links permanentes em arquivos -intro: 'Ao visualizar um arquivo em {% data variables.product.product_location %}, é possível pressionar a tecla "y" para atualizar a URL para um permalink com a versão exata do arquivo visualizado.' +title: Getting permanent links to files +intro: 'When viewing a file on {% data variables.location.product_location %}, you can press the "y" key to update the URL to a permalink to the exact version of the file you see.' redirect_from: - /articles/getting-a-permanent-link-to-a-file - /articles/how-do-i-get-a-permanent-link-from-file-view-to-permanent-blob-url @@ -15,49 +15,43 @@ versions: topics: - Repositories shortTitle: Permanent links to files -ms.openlocfilehash: 4e3d5ec282f7f7ba820094240698c88e298cdb69 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145126944' --- {% tip %} -**Dica**: pressione "?" em qualquer página do {% data variables.product.product_name %} para ver todos os atalhos de teclado disponíveis. +**Tip**: Press "?" on any page in {% data variables.product.product_name %} to see all available keyboard shortcuts. {% endtip %} -## As visualizações de arquivos mostram a versão mais recente de um branch +## File views show the latest version on a branch -Ao visualizar um arquivo em {% data variables.product.product_location %}, normalmente você vê a versão do head atual de um branch. Por exemplo: +When viewing a file on {% data variables.location.product_location %}, you usually see the version at the current head of a branch. For example: -* [https://github.com/github/codeql/blob/**main**/LEIAME.md](https://github.com/github/codeql/blob/main/README.md) +* [https://github.com/github/codeql/blob/**main**/README.md](https://github.com/github/codeql/blob/main/README.md) -refere-se ao repositório `codeql` do GitHub e mostra a versão atual do branch `main` do arquivo `README.md`. +refers to GitHub's `codeql` repository, and shows the `main` branch's current version of the `README.md` file. -A versão de um arquivo no head de um branch pode ser modificada assim que novos commits são feitos. Desta forma, caso você copie a URL normal, os conteúdos dos arquivos podem não ser os mesmos quando outra pessoa olhá-los posteriormente. +The version of a file at the head of branch can change as new commits are made, so if you were to copy the normal URL, the file contents might not be the same when someone looks at it later. -## Pressione Y para criar um link permanente para um arquivo em um commit específico +## Press Y to permalink to a file in a specific commit -Para obter um link permanente para a versão específica de um arquivo exibido, em vez de usar um nome de branch na URL (ou seja, a parte `main` no exemplo acima), coloque uma ID de commit. Isso será vinculado permanentemente à versão exata do arquivo nesse commit. Por exemplo: +For a permanent link to the specific version of a file that you see, instead of using a branch name in the URL (i.e. the `main` part in the example above), put a commit id. This will permanently link to the exact version of the file in that commit. For example: -* [https://github.com/github/codeql/blob/**b212af08a6cffbb434f3c8a2795a579e092792fd**/LEIAME.md](https://github.com/github/codeql/blob/b212af08a6cffbb434f3c8a2795a579e092792fd/README.md) +* [https://github.com/github/codeql/blob/**b212af08a6cffbb434f3c8a2795a579e092792fd**/README.md](https://github.com/github/codeql/blob/b212af08a6cffbb434f3c8a2795a579e092792fd/README.md) -substitui `main` por uma ID de commit específica e o conteúdo do arquivo não será alterado. +replaces `main` with a specific commit id and the file content will not change. -No entanto, pesquisar o SHA de commit manualmente é inconveniente. Portanto, como um atalho, você pode digitar y para atualizar automaticamente a URL para a versão de link permanente. Em seguida, você pode copiar a URL sabendo que qualquer pessoa com quem você compartilhá-la verá exatamente o que você vê. +Looking up the commit SHA by hand is inconvenient, however, so as a shortcut you can type y to automatically update the URL to the permalink version. Then you can copy the URL knowing that anyone you share it with will see exactly what you saw. {% tip %} -**Dica**: você pode colocar qualquer identificador que possa ser resolvido para um commit na URL, incluindo nomes de branches, SHAs de commits específicos ou tags. +**Tip**: You can put any identifier that can be resolved to a commit in the URL, including branch names, specific commit SHAs, or tags! {% endtip %} -## Criar um link permanente em um trecho de código +## Creating a permanent link to a code snippet -É possível criar um link permanente em uma linha específica ou conjunto de linhas de código de uma determinada versão de arquivo ou pull request. Para obter mais informações, confira "[Como criar um link permanente para um snippet de código](/articles/creating-a-permanent-link-to-a-code-snippet/)". +You can create a permanent link to a specific line or range of lines of code in a specific version of a file or pull request. For more information, see "[Creating a permanent link to a code snippet](/articles/creating-a-permanent-link-to-a-code-snippet/)." -## Leitura adicional +## Further reading -- "[Como arquivar um repositório do GitHub](/articles/archiving-a-github-repository)" +- "[Archiving a GitHub repository](/articles/archiving-a-github-repository)" diff --git a/translations/pt-BR/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/pt-BR/content/repositories/working-with-files/using-files/working-with-non-code-files.md index 229230ac98..5dd1df54fe 100644 --- a/translations/pt-BR/content/repositories/working-with-files/using-files/working-with-non-code-files.md +++ b/translations/pt-BR/content/repositories/working-with-files/using-files/working-with-non-code-files.md @@ -49,7 +49,7 @@ shortTitle: Working with non-code files ### Viewing images -You can directly browse and view images in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}: +You can directly browse and view images in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}: ![inline image](/assets/images/help/images/view.png) @@ -144,7 +144,7 @@ GitHub supports rendering tabular data in the form of *.csv* (comma-separated) a ![Rendered CSV sample](/assets/images/help/repository/rendered_csv.png) -When viewed, any _.csv_ or _.tsv_ file committed to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} automatically renders as an interactive table, complete with headers and row numbering. By default, we'll always assume the first row is your header row. +When viewed, any _.csv_ or _.tsv_ file committed to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} automatically renders as an interactive table, complete with headers and row numbering. By default, we'll always assume the first row is your header row. You can link to a particular row by clicking the row number, or select multiple rows by holding down the shift key. Just copy the URL and send it to a friend. @@ -327,9 +327,9 @@ It may still be possible to render the data by converting the `.geojson` file to ## Working with Jupyter Notebook files on {% data variables.product.prodname_dotcom %} -When you add Jupyter Notebook or IPython Notebook files with a *.ipynb* extension on {% data variables.product.product_location %}, they will render as static HTML files in your repository. +When you add Jupyter Notebook or IPython Notebook files with a *.ipynb* extension on {% data variables.location.product_location %}, they will render as static HTML files in your repository. -The interactive features of the notebook, such as custom JavaScript plots, will not work in your repository on {% data variables.product.product_location %}. For an example, see [*Linking and Interactions.ipynb*](https://github.com/bokeh/bokeh-notebooks/blob/main/tutorial/06%20-%20Linking%20and%20Interactions.ipynb). +The interactive features of the notebook, such as custom JavaScript plots, will not work in your repository on {% data variables.location.product_location %}. For an example, see [*Linking and Interactions.ipynb*](https://github.com/bokeh/bokeh-notebooks/blob/main/tutorial/06%20-%20Linking%20and%20Interactions.ipynb). To view your Jupyter notebook with JavaScript content rendered or to share your notebook files with others you can use [nbviewer](https://nbviewer.jupyter.org/). For an example, see [*Linking and Interactions.ipynb*](https://nbviewer.jupyter.org/github/bokeh/bokeh-notebooks/blob/main/tutorial/06%20-%20Linking%20and%20Interactions.ipynb) rendered on nbviewer. diff --git a/translations/pt-BR/content/rest/activity/notifications.md b/translations/pt-BR/content/rest/activity/notifications.md index 1419327ce1..1623a3b424 100644 --- a/translations/pt-BR/content/rest/activity/notifications.md +++ b/translations/pt-BR/content/rest/activity/notifications.md @@ -1,6 +1,6 @@ --- -title: Notificações -intro: 'A API de Notificações permite que você gerencie notificações do {% data variables.product.product_name %}.' +title: Notifications +intro: 'The Notifications API lets you manage {% data variables.product.product_name %} notifications.' versions: fpt: '*' ghes: '*' @@ -9,22 +9,19 @@ versions: topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 2d68f2b563578608ab66eafbb055edbe5d88d172 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147064271' --- -## Sobre a API de Notificações -A API de Notificações permite que você gerencie notificações do {% data variables.product.product_name %}. Para obter mais informações sobre as notificações, confira "[Sobre notificações](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)". +## About the Notifications API -Todas as chamadas à API de Notificação exigem os escopos de API `notifications` ou `repo`. Fazer isto dará acesso somente-leitura a algum problema e fará commit do conteúdo. Você ainda precisará do escopo `repo` para acessar problemas e commits dos respectivos pontos de extremidade. +{% data reusables.user-settings.notifications-api-classic-pat-only %} -Notificações retornam como "correntes". Uma corrente contém informações sobre a discussão atual de um problema, pull request ou commit. +The Notifications API lets you manage {% data variables.product.product_name %} notifications. For more information about notifications, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." -As notificações são otimizadas para sondagem com o cabeçalho `Last-Modified`. Se não houver novas notificações, você verá uma resposta `304 Not Modified`, mantendo o limite de taxa atual intacto. Há um cabeçalho `X-Poll-Interval` que especifica a frequência (em segundos) com que você tem permissão de sondagem. Em tempos de alta carga do servidor, o tempo pode aumentar. Obedeça o cabeçalho. +All Notification API calls require the `notifications` or `repo` API scopes. Doing this will give read-only access to some issue and commit content. You will still need the `repo` scope to access issues and commits from their respective endpoints. + +Notifications come back as "threads". A thread contains information about the current discussion of an issue, pull request, or commit. + +Notifications are optimized for polling with the `Last-Modified` header. If there are no new notifications, you will see a `304 Not Modified` response, leaving your current rate limit untouched. There is an `X-Poll-Interval` header that specifies how often (in seconds) you are allowed to poll. In times of high server load, the time may increase. Please obey the header. ``` shell # Add authentication to your requests @@ -40,27 +37,27 @@ $ -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT" > X-Poll-Interval: 60 ``` -### Sobre motivos de notificação +### About notification reasons -Ao recuperar respostas da API de Notificações, cada conteúdo tem uma chave intitulada `reason`. Estas correspondem a eventos que ativam uma notificação. +When retrieving responses from the Notifications API, each payload has a key titled `reason`. These correspond to events that trigger a notification. -Estes são possíveis `reason`s para recebimento de uma notificação: +These are the potential `reason`s for receiving a notification: -Nome da razão | Descrição +Reason Name | Description ------------|------------ -`assign` | O problema foi atribuído a você. -`author` | Você criou a corrente. -`comment` | Você comentou na corrente. -`ci_activity` | A execução de um fluxo de trabalho {% data variables.product.prodname_actions %} que você acionou foi concluída. -`invitation` | Você aceitou um convite para contribuir com o repositório. -`manual` | Você assinou a corrente (por meio de um problema ou pull request). -`mention` | Você foi especificamente **@mentioned** no conteúdo. -`review_requested` | Foi solicitado que você ou uma equipe da qual você é integrante revise um pull request.{% ifversion fpt or ghec %} -`security_alert` | O {% data variables.product.prodname_dotcom %} descobriu uma [vulnerabilidade de segurança](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) no seu repositório.{% endif %} -`state_change` | Você alterou o estado da corrente (por exemplo, fechando um problema ou mesclando um pull request). -`subscribed` | Você está inspecionando o repositório. -`team_mention` | Você estava em uma equipe que foi mencionada. +`assign` | You were assigned to the issue. +`author` | You created the thread. +`comment` | You commented on the thread. +`ci_activity` | A {% data variables.product.prodname_actions %} workflow run that you triggered was completed. +`invitation` | You accepted an invitation to contribute to the repository. +`manual` | You subscribed to the thread (via an issue or pull request). +`mention` | You were specifically **@mentioned** in the content. +`review_requested` | You, or a team you're a member of, were requested to review a pull request.{% ifversion fpt or ghec %} +`security_alert` | {% data variables.product.prodname_dotcom %} discovered a [security vulnerability](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in your repository.{% endif %} +`state_change` | You changed the thread state (for example, closing an issue or merging a pull request). +`subscribed` | You're watching the repository. +`team_mention` | You were on a team that was mentioned. -Observe que o `reason` é modificado a cada conversa e poderá mudar se o `reason` em uma notificação posterior for diferente. +Note that the `reason` is modified on a per-thread basis, and can change, if the `reason` on a later notification is different. -Por exemplo, se você for o autor de um problema, as notificações seguintes sobre esse problema terão um `reason` igual a `author`. Em seguida, se você for **@mentioned** no mesmo problema, as notificações que você buscar depois disso terão um `reason` igual a `mention`. O `reason` continua sendo `mention`, independentemente de você ser mencionado novamente. +For example, if you are the author of an issue, subsequent notifications on that issue will have a `reason` of `author`. If you're then **@mentioned** on the same issue, the notifications you fetch thereafter will have a `reason` of `mention`. The `reason` remains as `mention`, regardless of whether you're ever mentioned again. diff --git a/translations/pt-BR/content/rest/apps/oauth-applications.md b/translations/pt-BR/content/rest/apps/oauth-applications.md index 8e7e364159..e964f5eb47 100644 --- a/translations/pt-BR/content/rest/apps/oauth-applications.md +++ b/translations/pt-BR/content/rest/apps/oauth-applications.md @@ -1,5 +1,5 @@ --- -title: Aplicativos OAuth +title: OAuth Apps allowTitleToDifferFromFilename: true intro: '' topics: @@ -10,13 +10,8 @@ versions: ghes: '*' ghae: '*' ghec: '*' -ms.openlocfilehash: bb80e0627236ff7e045dd72823201b6d8e750445 -ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/12/2022 -ms.locfileid: '147888433' --- -## Sobre o {% data variables.product.prodname_oauth_app %} API -Você pode usar esta API para gerenciar os tokens do OAuth que um {% data variables.product.prodname_oauth_app %} usa para acessar as contas das pessoas no {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. +## About the {% data variables.product.prodname_oauth_app %} API + +You can use this API to manage the OAuth tokens an {% data variables.product.prodname_oauth_app %} uses to access people's accounts on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. diff --git a/translations/pt-BR/content/rest/codespaces/codespaces.md b/translations/pt-BR/content/rest/codespaces/codespaces.md index 7d47111001..ce37af620a 100644 --- a/translations/pt-BR/content/rest/codespaces/codespaces.md +++ b/translations/pt-BR/content/rest/codespaces/codespaces.md @@ -1,19 +1,14 @@ --- -title: Espaços de código -intro: A API Codespaces permite que você gerencie os codespaces usando a API REST. +title: Codespaces +intro: The Codespaces API enables you to manage your codespaces using the REST API. versions: fpt: '*' ghec: '*' topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 0108e8ac59714ecea24e1f19d5adf3f2d0371f15 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147110567' --- -## Sobre a API de Codespaces -A API {% data variables.product.prodname_github_codespaces %} permite que você gerencie os {% data variables.product.prodname_codespaces %} usando a API REST. Esta API está disponível para usuários autenticados e aplicativos OAuth, mas não para aplicativos GitHub. Para obter mais informações, confira "[{% data variables.product.prodname_codespaces %}](/codespaces)". +## About the Codespaces API + +The {% data variables.product.prodname_github_codespaces %} API enables you to manage {% data variables.product.prodname_codespaces %} using the REST API. This API is available for authenticated users, {% data variables.product.prodname_oauth_apps %}, and {% data variables.product.prodname_github_apps %}. For more information, see "[{% data variables.product.prodname_codespaces %}](/codespaces)." diff --git a/translations/pt-BR/content/rest/enterprise-admin/admin-stats.md b/translations/pt-BR/content/rest/enterprise-admin/admin-stats.md index dfc490bcd0..6be1e3b2cf 100644 --- a/translations/pt-BR/content/rest/enterprise-admin/admin-stats.md +++ b/translations/pt-BR/content/rest/enterprise-admin/admin-stats.md @@ -1,6 +1,6 @@ --- -title: Estatísticas de admin -intro: A API de Estatísticas Administrativas fornece uma variedade de métricas sobre sua instalação. +title: Admin stats +intro: The Admin Stats API provides a variety of metrics about your installation. versions: ghes: '*' ghae: '*' @@ -9,11 +9,8 @@ versions: topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: a3330488afc37426ef68231eb8d4fed515dcfe16 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147060040' --- -*Ela só está disponível para administradores [autenticados](/rest/overview/resources-in-the-rest-api#authentication) do site.* Os usuários normais receberão uma resposta `404` se tentarem acessá-la. + +*It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. + +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} diff --git a/translations/pt-BR/content/rest/enterprise-admin/announcement.md b/translations/pt-BR/content/rest/enterprise-admin/announcement.md index f6590486b9..d699a2b2f5 100644 --- a/translations/pt-BR/content/rest/enterprise-admin/announcement.md +++ b/translations/pt-BR/content/rest/enterprise-admin/announcement.md @@ -1,19 +1,16 @@ --- -title: Anúncio -intro: A API Comunicado permite que você gerencie a faixa de comunicado global na empresa. +title: Announcement +intro: The Announcement API allows you to manage the global announcement banner in your enterprise. versions: ghes: '*' ghae: '*' topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: e3394dd67e06c362bb26c547f34124e8a7a198af -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147883016' --- -## Anúncio -A API de anúncios permite que você gerencie o banner de anúncio global na sua empresa. Para obter mais informações, confira "[Como personalizar mensagens de usuário para sua empresa](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)". +## Announcement + +The Announcements API allows you to manage the global announcement banner in your enterprise. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)." + +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} diff --git a/translations/pt-BR/content/rest/enterprise-admin/audit-log.md b/translations/pt-BR/content/rest/enterprise-admin/audit-log.md index dd8f1578f9..33ca7acbfc 100644 --- a/translations/pt-BR/content/rest/enterprise-admin/audit-log.md +++ b/translations/pt-BR/content/rest/enterprise-admin/audit-log.md @@ -1,5 +1,5 @@ --- -title: Log de auditoria +title: Audit log intro: '' versions: ghes: '>=3.3' @@ -8,11 +8,6 @@ versions: topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 171735e6b5c5e9dbf66aa746ffd1b216779f89f6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147060015' --- +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} diff --git a/translations/pt-BR/content/rest/enterprise-admin/billing.md b/translations/pt-BR/content/rest/enterprise-admin/billing.md index 87754f96d0..ff04adef94 100644 --- a/translations/pt-BR/content/rest/enterprise-admin/billing.md +++ b/translations/pt-BR/content/rest/enterprise-admin/billing.md @@ -1,5 +1,5 @@ --- -title: Cobrança +title: Billing intro: '' versions: fpt: '*' @@ -8,11 +8,6 @@ versions: topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 81da9a3e3e7dfaf02bf12fd9b67c90048784e834 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147060016' --- +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} diff --git a/translations/pt-BR/content/rest/enterprise-admin/global-webhooks.md b/translations/pt-BR/content/rest/enterprise-admin/global-webhooks.md index 747657fee2..d50e201ec0 100644 --- a/translations/pt-BR/content/rest/enterprise-admin/global-webhooks.md +++ b/translations/pt-BR/content/rest/enterprise-admin/global-webhooks.md @@ -1,19 +1,16 @@ --- -title: Webhooks globais -intro: 'Webhooks globais são instalados na sua empresa. Você pode usar webhooks globais para monitorar, responder ou aplicar regras automaticamente para usuários, organizações, equipes e repositórios na sua empresa.' +title: Global Webhooks +intro: 'Global Webhooks are installed on your enterprise. You can use global webhooks to automatically monitor, respond to, or enforce rules for users, organizations, teams, and repositories on your enterprise.' versions: ghes: '*' ghae: '*' topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 66186eeba470274d91b61aaae700e25716c26ef5 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147067223' --- -Os webhooks globais podem se inscrever nos tipos de eventos [organização](/developers/webhooks-and-events/webhook-events-and-payloads#organization), [usuário](/developers/webhooks-and-events/webhook-events-and-payloads#user), [repositório](/developers/webhooks-and-events/webhook-events-and-payloads#repository), [equipe](/developers/webhooks-and-events/webhook-events-and-payloads#team), [membro](/developers/webhooks-and-events/webhook-events-and-payloads#member), [associação](/developers/webhooks-and-events/webhook-events-and-payloads#membership), [fork](/developers/webhooks-and-events/webhook-events-and-payloads#fork) e [ping](/developers/webhooks-and-events/about-webhooks#ping-event). -*Essa API só está disponível para administradores [autenticados](/rest/overview/resources-in-the-rest-api#authentication) do site.* Os usuários normais receberão uma resposta `404` se tentarem acessá-la. Para saber como configurar webhooks globais, confira [Sobre os webhooks globais](/enterprise/admin/user-management/about-global-webhooks). +Global webhooks can subscribe to the [organization](/developers/webhooks-and-events/webhook-events-and-payloads#organization), [user](/developers/webhooks-and-events/webhook-events-and-payloads#user), [repository](/developers/webhooks-and-events/webhook-events-and-payloads#repository), [team](/developers/webhooks-and-events/webhook-events-and-payloads#team), [member](/developers/webhooks-and-events/webhook-events-and-payloads#member), [membership](/developers/webhooks-and-events/webhook-events-and-payloads#membership), [fork](/developers/webhooks-and-events/webhook-events-and-payloads#fork), and [ping](/developers/webhooks-and-events/about-webhooks#ping-event) event types. + +*This API is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. To learn how to configure global webhooks, see [About global webhooks](/enterprise/admin/user-management/about-global-webhooks). + +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} diff --git a/translations/pt-BR/content/rest/enterprise-admin/index.md b/translations/pt-BR/content/rest/enterprise-admin/index.md index 9b4f7dd71b..4e9927d3a9 100644 --- a/translations/pt-BR/content/rest/enterprise-admin/index.md +++ b/translations/pt-BR/content/rest/enterprise-admin/index.md @@ -1,6 +1,6 @@ --- -title: Administração do GitHub Enterprise -intro: Você pode usar esses pontos de extremidade para administrar a empresa. +title: GitHub Enterprise administration +intro: You can use these endpoints to administer your enterprise. allowTitleToDifferFromFilename: true redirect_from: - /v3/enterprise-admin @@ -31,52 +31,54 @@ children: - /repo-pre-receive-hooks - /users - /scim -ms.openlocfilehash: 19688f806101c8022b64dfc21806b79338917353 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147065589' --- + {% ifversion fpt or ghec %} {% note %} -**Observação:** este artigo se aplica ao {% data variables.product.prodname_ghe_cloud %}. Para ver a versão do {% data variables.product.prodname_ghe_managed %} ou do {% data variables.product.prodname_ghe_server %}, use o menu suspenso **{% data ui.pages.article_version %}** . +**Note:** This article applies to {% data variables.product.prodname_ghe_cloud %}. To see the {% data variables.product.prodname_ghe_managed %} or {% data variables.product.prodname_ghe_server %} version, use the **{% data ui.pages.article_version %}** drop-down menu. {% endnote %} {% endif %} -### URLs do ponto de extremidade +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} -Os pontos de extremidade da API REST{% ifversion ghes %}, exceto os pontos de extremidade da API do [Console de Gerenciamento](#management-console), {% endif %} têm a seguinte URL como prefixo: +### Endpoint URLs + +REST API endpoints{% ifversion ghes %}—except [Management Console](#management-console) API endpoints—{% endif %} are prefixed with the following URL: ```shell {% data variables.product.api_url_pre %} ``` -{% ifversion fpt or ghec %} Quando os pontos de extremidade incluírem `{enterprise}`, substitua `{enterprise}` pelo identificador da sua conta corporativa, que está incluído na URL das configurações corporativas. Por exemplo, se a sua conta corporativa estiver localizada em `https://github.com/enterprises/octo-enterprise`, substitua `{enterprise}` por `octo-enterprise`. +{% ifversion fpt or ghec %} +When endpoints include `{enterprise}`, replace `{enterprise}` with the handle for your enterprise account, which is included in the URL for your enterprise settings. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `{enterprise}` with `octo-enterprise`. {% endif %} -{% ifversion ghes %} Os pontos de extremidade da API do [Console de Gerenciamento](#management-console) só têm um nome do host como prefixo: +{% ifversion ghes %} +[Management Console](#management-console) API endpoints are only prefixed with a hostname: ```shell -http(s)://hostname/ +http(s)://HOSTNAME/ ``` -{% endif %} {% ifversion ghae or ghes %} -### Autenticação +{% endif %} +{% ifversion ghae or ghes %} +### Authentication -Os pontos de extremidade da API de instalação do {% data variables.product.product_name %} aceitam [os mesmos métodos de autenticação](/rest/overview/resources-in-the-rest-api#authentication) da API do GitHub.com. Você pode se autenticar com os **[tokens OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% ifversion ghes %}(que podem ser criados por meio da [API de Autorizações](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}ou com a **[autenticação básica](/rest/overview/resources-in-the-rest-api#basic-authentication)** . {% ifversion ghes %} Os tokens OAuth precisam ter o `site_admin` [escopo OAuth](/developers/apps/scopes-for-oauth-apps#available-scopes) quando usados com pontos de extremidade específicos do Enterprise.{% endif %} +Your {% data variables.product.product_name %} installation's API endpoints accept [the same authentication methods](/rest/overview/resources-in-the-rest-api#authentication) as the GitHub.com API. You can authenticate yourself with **[OAuth tokens](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% ifversion ghes %}(which can be created using the [Authorizations API](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}or **[basic authentication](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% ifversion ghes %} +OAuth tokens must have the `site_admin` [OAuth scope](/developers/apps/scopes-for-oauth-apps#available-scopes) when used with Enterprise-specific endpoints.{% endif %} -Os pontos de extremidade da API de administração do Enterprise só podem ser acessados por administradores do site autenticados do {% data variables.product.product_name %} {% ifversion ghes %}, exceto a API do [Console de Gerenciamento](#management-console), que exige a [senha do Console de Gerenciamento](/enterprise/admin/articles/accessing-the-management-console/){% endif %}. +Enterprise administration API endpoints are only accessible to authenticated {% data variables.product.product_name %} site administrators{% ifversion ghes %}, except for the [Management Console](#management-console) API, which requires the [Management Console password](/enterprise/admin/articles/accessing-the-management-console/){% endif %}. {% endif %} {% ifversion ghae or ghes %} -### Informações da versão +### Version information -A versão atual da sua empresa é retornada no cabeçalho de resposta de cada API: `X-GitHub-Enterprise-Version: {{currentVersion}}.0` -Leia também a versão atual chamando o [meta ponto de extremidade](/rest/reference/meta/). +The current version of your enterprise is returned in the response header of every API: +`X-GitHub-Enterprise-Version: {{currentVersion}}.0` +You can also read the current version by calling the [meta endpoint](/rest/reference/meta/). {% endif %} diff --git a/translations/pt-BR/content/rest/enterprise-admin/ldap.md b/translations/pt-BR/content/rest/enterprise-admin/ldap.md index d0cc8d0f1b..c4727266f5 100644 --- a/translations/pt-BR/content/rest/enterprise-admin/ldap.md +++ b/translations/pt-BR/content/rest/enterprise-admin/ldap.md @@ -1,16 +1,13 @@ --- title: LDAP -intro: 'Você pode usar a API LDAP para atualizar as relações de conta entre um usuário ou equipe {% data variables.product.product_name %} e sua entrada LDAP vinculada ou enfileirar uma nova sincronização.' +intro: 'You can use the LDAP API to update account relationships between a {% data variables.product.product_name %} user or team and its linked LDAP entry or queue a new synchronization.' versions: ghes: '*' topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 0948fbf02aea86d01a7034ae6b1836c0f69ca6e2 -ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147065335' --- -Com os endpoints de mapeamento LDAP, você é capaz de atualizar o Nome Distinto (DN) para o qual um usuário ou uma equipe mapeia. Observe que, em geral, os pontos de extremidade LDAP só serão eficazes se o dispositivo do {% data variables.product.product_name %} tiver a [Sincronização LDAP habilitada](/enterprise/admin/authentication/using-ldap). O ponto de extremidade [Atualizar mapeamento do LDAP para um usuário](#update-ldap-mapping-for-a-user) pode ser usado quando o LDAP está habilitado, mesmo que a Sincronização LDAP esteja desabilitada. + +With the LDAP mapping endpoints, you're able to update the Distinguished Name (DN) that a user or team maps to. Note that the LDAP endpoints are generally only effective if your {% data variables.product.product_name %} appliance has [LDAP Sync enabled](/enterprise/admin/authentication/using-ldap). The [Update LDAP mapping for a user](#update-ldap-mapping-for-a-user) endpoint can be used when LDAP is enabled, even if LDAP Sync is disabled. + +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} diff --git a/translations/pt-BR/content/rest/enterprise-admin/license.md b/translations/pt-BR/content/rest/enterprise-admin/license.md index 8c4a9ab9f2..6af199deca 100644 --- a/translations/pt-BR/content/rest/enterprise-admin/license.md +++ b/translations/pt-BR/content/rest/enterprise-admin/license.md @@ -1,6 +1,6 @@ --- -title: Licença -intro: A API de Licença fornece informações sobre sua licença empresarial. +title: License +intro: The License API provides information on your Enterprise license. versions: ghes: '*' ghae: '*' @@ -8,11 +8,8 @@ versions: topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 5d47f972922a44292ffe4b32e4f90aae250e0948 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147572645' --- -*Ela só está disponível para administradores [autenticados](/rest/overview/resources-in-the-rest-api#authentication) do site.* Os usuários normais receberão uma resposta `404` se tentarem acessá-la. + +*It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. + +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} diff --git a/translations/pt-BR/content/rest/enterprise-admin/management-console.md b/translations/pt-BR/content/rest/enterprise-admin/management-console.md index 93a36a6daa..8bf82468bd 100644 --- a/translations/pt-BR/content/rest/enterprise-admin/management-console.md +++ b/translations/pt-BR/content/rest/enterprise-admin/management-console.md @@ -1,40 +1,37 @@ --- -title: Console de Gerenciamento -intro: 'A API do Console de Gerenciamento ajuda você a gerenciar sua instalação do {% data variables.product.product_name %}.' +title: Management Console +intro: 'The Management Console API helps you manage your {% data variables.product.product_name %} installation.' versions: ghes: '*' topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: da38513a04525b858e041188eec6f691db9be1d9 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147065535' --- + {% tip %} -Você deve definir explicitamente o número da porta ao fazer chamadas de API para o Console de Gerenciamento. Se o TLS estiver habilitado na sua empresa, o número da porta será `8443`; caso contrário, o número da porta será `8080`. +You must explicitly set the port number when making API calls to the Management Console. If TLS is enabled on your enterprise, the port number is `8443`; otherwise, the port number is `8080`. -Se não quiser fornecer um número da porta, você precisará configurar sua ferramenta para seguir os redirecionamentos automaticamente. +If you don't want to provide a port number, you'll need to configure your tool to automatically follow redirects. -Talvez você também precise adicionar o [`-k` sinalizador](http://curl.haxx.se/docs/manpage.html#-k) ao usar `curl`, já que {% data variables.product.product_name %} usa um certificado autoassinado antes de [adicionar seu próprio certificado TLS](/enterprise/admin/guides/installation/configuring-tls/). +You may also need to add the [`-k` flag](http://curl.haxx.se/docs/manpage.html#-k) when using `curl`, since {% data variables.product.product_name %} uses a self-signed certificate before you [add your own TLS certificate](/enterprise/admin/guides/installation/configuring-tls/). {% endtip %} -### Autenticação +### Authentication -Você precisa passar sua [senha do Console de Gerenciamento](/enterprise/admin/articles/accessing-the-management-console/) como um token de autenticação para todos os pontos de extremidade da API do Console de Gerenciamento, exceto [`/setup/api/start`](#create-a-github-enterprise-server-license). +You need to pass your [Management Console password](/enterprise/admin/articles/accessing-the-management-console/) as an authentication token to every Management Console API endpoint except [`/setup/api/start`](#create-a-github-enterprise-server-license). -Use o parâmetro `api_key` para enviar este token com cada solicitação. Por exemplo: +Use the `api_key` parameter to send this token with each request. For example: ```shell -$ curl -L 'https://hostname:admin_port/setup/api?api_key=your-amazing-password' +$ curl -L 'https://HOSTNAME:ADMIN-PORT/setup/api?api_key=YOUR_PASSWORD' ``` -Você também pode usar a autenticação HTTP padrão para enviar esse token. Por exemplo: +You can also use standard HTTP authentication to send this token. For example: ```shell -$ curl -L -u "api_key:your-amazing-password" 'https://hostname:admin_port/setup/api' +$ curl -L -u "api_key:YOUR_PASSWORD" 'https://HOSTNAME:ADMIN-PORT/setup/api' ``` + +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} diff --git a/translations/pt-BR/content/rest/enterprise-admin/org-pre-receive-hooks.md b/translations/pt-BR/content/rest/enterprise-admin/org-pre-receive-hooks.md index 0c4878aee4..44a2256f6e 100644 --- a/translations/pt-BR/content/rest/enterprise-admin/org-pre-receive-hooks.md +++ b/translations/pt-BR/content/rest/enterprise-admin/org-pre-receive-hooks.md @@ -1,28 +1,25 @@ --- -title: Hooks de pré-recebimento da organização -intro: A API de Ganchos de Pré-recebimento da Organização permite que você veja e modifique a imposição dos ganchos de pré-recebimento disponíveis para uma organização. +title: Organization Pre-receive Hooks +intro: The Organization Pre-receive Hooks API allows you to view and modify enforcement of the pre-receive hooks that are available to an organization. versions: ghes: '*' topics: - API miniTocMaxHeadingLevel: 3 allowTitleToDifferFromFilename: true -ms.openlocfilehash: 802ed40ac8e42c1f0a9ef3b6bab4a150dd68603c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147063959' --- -### Atributos do objeto -| Nome | Tipo | Descrição | +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} + +### Object attributes + +| Name | Type | Description | |----------------------------------|-----------|-----------------------------------------------------------| -| `name` | `string` | O nome do hook. | -| `enforcement` | `string` | O estado de aplicação para o hook neste repositório. | -| `allow_downstream_configuration` | `boolean` | Se os repositórios podem substituir a imposição. | -| `configuration_url` | `string` | URL para o ponto de extremidade em que a aplicação é definida. | +| `name` | `string` | The name of the hook. | +| `enforcement` | `string` | The state of enforcement for the hook on this repository. | +| `allow_downstream_configuration` | `boolean` | Whether repositories can override enforcement. | +| `configuration_url` | `string` | URL for the endpoint where enforcement is set. | -Os possíveis valores para *a imposição* são `enabled`, `disabled` e `testing`. `disabled` indica que o gancho de pré-recebimento não será executado. `enabled` indica que ele será executado e rejeitará os pushes que resultem em um status diferente de zero. `testing` significa que o script será executado, mas não fará com que nenhum push seja rejeitado. +Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected. -`configuration_url` pode ser um link para esse ponto de extremidade ou para a configuração global desse gancho. Apenas administradores do site podem acessar a configuração global. +`configuration_url` may be a link to this endpoint or this hook's global configuration. Only site admins are able to access the global configuration. diff --git a/translations/pt-BR/content/rest/enterprise-admin/orgs.md b/translations/pt-BR/content/rest/enterprise-admin/orgs.md index d9558be69b..4f5bfb8d52 100644 --- a/translations/pt-BR/content/rest/enterprise-admin/orgs.md +++ b/translations/pt-BR/content/rest/enterprise-admin/orgs.md @@ -1,6 +1,6 @@ --- -title: Organizações -intro: A API de administração da organização permite a criação de organizações na sua empresa. +title: Organizations +intro: The Organization Administration API allows you to create organizations on your enterprise. versions: ghes: '*' ghae: '*' @@ -8,11 +8,8 @@ topics: - API miniTocMaxHeadingLevel: 3 allowTitleToDifferFromFilename: true -ms.openlocfilehash: dde98174176217083a0c0960a069ed266e5fb413 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147061959' --- -*Ela só está disponível para administradores [autenticados](/rest/overview/resources-in-the-rest-api#authentication) do site.* Os usuários normais receberão uma resposta `404` se tentarem acessá-la. + +*It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. + +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} diff --git a/translations/pt-BR/content/rest/enterprise-admin/pre-receive-environments.md b/translations/pt-BR/content/rest/enterprise-admin/pre-receive-environments.md index c454684819..f03da691ea 100644 --- a/translations/pt-BR/content/rest/enterprise-admin/pre-receive-environments.md +++ b/translations/pt-BR/content/rest/enterprise-admin/pre-receive-environments.md @@ -1,39 +1,36 @@ --- -title: Ambientes Pre-receive -intro: 'A API de Ambientes Pre-receive permite que você crie, liste, atualize e apague ambientes para hooks pre-receive.' +title: Pre-receive Environments +intro: 'The Pre-receive Environments API allows you to create, list, update and delete environments for pre-receive hooks.' versions: ghes: '*' ghae: '*' topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 9db8635691ae2f8fcb8649b648948763168081ac -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147883259' --- -*Ela só está disponível para administradores [autenticados](/rest/overview/resources-in-the-rest-api#authentication) do site.* Os usuários normais receberão uma resposta `404` se tentarem acessá-la. -### Atributos do objeto +*It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. -#### Ambiente pre-receive +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} -| Nome | Tipo | Descrição | +### Object attributes + +#### Pre-receive Environment + +| Name | Type | Description | |-----------------------|-----------|----------------------------------------------------------------------------| -| `name` | `string` | O nome do ambiente conforme exibido na interface do usuário. | -| `image_url` | `string` | URL do tarball que será baixado e extraído. | -| `default_environment` | `boolean` | Se este é o ambiente-padrão que vem com {% data variables.product.product_name %}. | -| `download` | `object` | Status do download deste ambiente. | -| `hooks_count` | `integer` | O número de hooks de pre-receive que usam este ambiente. | +| `name` | `string` | The name of the environment as displayed in the UI. | +| `image_url` | `string` | URL to the tarball that will be downloaded and extracted. | +| `default_environment` | `boolean` | Whether this is the default environment that ships with {% data variables.product.product_name %}. | +| `download` | `object` | This environment's download status. | +| `hooks_count` | `integer` | The number of pre-receive hooks that use this environment. | -#### Download do ambiente pre-receive +#### Pre-receive Environment Download -| Nome | Tipo | Descrição | +| Name | Type | Description | |-----------------|----------|---------------------------------------------------------| -| `state` | `string` | O estado do download mais recente. | -| `downloaded_at` | `string` | A hora em que o download mais recente começou. | -| `message` | `string` | Em caso de falha, serão produzidas mensagens de erro. | +| `state` | `string` | The state of the most recent download. | +| `downloaded_at` | `string` | The time when the most recent download started. | +| `message` | `string` | On failure, this will have any error messages produced. | -Os valores possíveis para `state` são `not_started`, `in_progress`, `success` e `failed`. +Possible values for `state` are `not_started`, `in_progress`, `success`, `failed`. diff --git a/translations/pt-BR/content/rest/enterprise-admin/pre-receive-hooks.md b/translations/pt-BR/content/rest/enterprise-admin/pre-receive-hooks.md index c2e7db44d4..e9fdf6e4a8 100644 --- a/translations/pt-BR/content/rest/enterprise-admin/pre-receive-hooks.md +++ b/translations/pt-BR/content/rest/enterprise-admin/pre-receive-hooks.md @@ -1,31 +1,29 @@ --- -title: Hooks Pre-receive -intro: 'A API de hooks pre-receive permite que você crie, liste, atualize e apague hooks pre-receive.' +title: Pre-receive Hooks +intro: 'The Pre-receive Hooks API allows you to create, list, update and delete pre-receive hooks.' versions: ghes: '*' topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: dd776e7ec95a970f025d4de1ec03f07b2a7b29f7 -ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147066151' --- -*Ela só está disponível para administradores [autenticados](/rest/overview/resources-in-the-rest-api#authentication) do site.* Os usuários normais receberão uma resposta `404` se tentarem acessá-la. -### Atributos do objeto +*It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. -#### Hook pre-receive +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} -| Nome | Tipo | Descrição | +### Object attributes + +#### Pre-receive Hook + +| Name | Type | Description | |----------------------------------|-----------|-----------------------------------------------------------------| -| `name` | `string` | O nome do hook. | -| `script` | `string` | O script que o hook executa. | -| `script_repository` | `object` | O repositório do GitHub onde o script é mantido. | -| `environment` | `object` | O ambiente de pre-receive onde o script é executado. | -| `enforcement` | `string` | O estado de aplicação para este hook. | -| `allow_downstream_configuration` | `boolean` | Se a aplicação pode ser substituída no nível da organização ou do repositório. | +| `name` | `string` | The name of the hook. | +| `script` | `string` | The script that the hook runs. | +| `script_repository` | `object` | The GitHub repository where the script is kept. | +| `environment` | `object` | The pre-receive environment where the script is executed. | +| `enforcement` | `string` | The state of enforcement for this hook. | +| `allow_downstream_configuration` | `boolean` | Whether enforcement can be overridden at the org or repo level. | -Os possíveis valores para *a imposição* são `enabled`, `disabled` e `testing`. `disabled` indica que o gancho de pré-recebimento não será executado. `enabled` indica que ele será executado e rejeitará os pushes que resultem em um status diferente de zero. `testing` significa que o script será executado, mas não fará com que nenhum push seja rejeitado. +Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject +any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected. diff --git a/translations/pt-BR/content/rest/enterprise-admin/repo-pre-receive-hooks.md b/translations/pt-BR/content/rest/enterprise-admin/repo-pre-receive-hooks.md index 063d8e5fc0..cd2153eedf 100644 --- a/translations/pt-BR/content/rest/enterprise-admin/repo-pre-receive-hooks.md +++ b/translations/pt-BR/content/rest/enterprise-admin/repo-pre-receive-hooks.md @@ -1,27 +1,24 @@ --- -title: Hooks pré-recebidos do repositório -intro: A API de Ganchos de Pré-recebimento do Repositório permite que você veja e modifique a imposição dos ganchos de pré-recebimento disponíveis para um repositório. +title: Repository Pre-receive Hooks +intro: The Repository Pre-receive Hooks API allows you to view and modify enforcement of the pre-receive hooks that are available to a repository. versions: ghes: '*' topics: - API miniTocMaxHeadingLevel: 3 allowTitleToDifferFromFilename: true -ms.openlocfilehash: 63ba6f4f7d67b43dd39609a6520a0938365cfc12 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147065159' --- -### Atributos do objeto -| Nome | Tipo | Descrição | +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} + +### Object attributes + +| Name | Type | Description | |---------------------|----------|-----------------------------------------------------------| -| `name` | `string` | O nome do hook. | -| `enforcement` | `string` | O estado de aplicação para o hook neste repositório. | -| `configuration_url` | `string` | URL para o ponto de extremidade em que a aplicação é definida. | +| `name` | `string` | The name of the hook. | +| `enforcement` | `string` | The state of enforcement for the hook on this repository. | +| `configuration_url` | `string` | URL for the endpoint where enforcement is set. | -Os possíveis valores para *a imposição* são `enabled`, `disabled` e `testing`. `disabled` indica que o gancho de pré-recebimento não será executado. `enabled` indica que ele será executado e rejeitará os pushes que resultem em um status diferente de zero. `testing` significa que o script será executado, mas não fará com que nenhum push seja rejeitado. +Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected. -`configuration_url` pode ser um link para esse repositório, o proprietário da organização ou a configuração global. A autorização para acessar o ponto de extremidade em `configuration_url` é determinada no nível do proprietário ou do administrador do site. +`configuration_url` may be a link to this repository, it's organization owner or global configuration. Authorization to access the endpoint at `configuration_url` is determined at the owner or site admin level. diff --git a/translations/pt-BR/content/rest/enterprise-admin/scim.md b/translations/pt-BR/content/rest/enterprise-admin/scim.md index a95eb461b5..ae7b44b582 100644 --- a/translations/pt-BR/content/rest/enterprise-admin/scim.md +++ b/translations/pt-BR/content/rest/enterprise-admin/scim.md @@ -14,6 +14,7 @@ miniTocMaxHeadingLevel: 3 {% endnote %} +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} ## About the SCIM API {% data variables.product.product_name %} provides a SCIM API for use by SCIM-enabled Identity Providers (IdPs). An integration on the IdP can use the API to automatically provision, manage, or deprovision user accounts on a {% data variables.product.product_name %} instance that uses SAML single sign-on (SSO) for authentication. For more information about SAML SSO, see "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)." @@ -38,11 +39,11 @@ GET /scim/v2/Users/{scim_user_id} The SCIM integration on the IdP performs actions on behalf of an enterprise owner for the {% data variables.product.product_name %} instance. For more information, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owners)." -To authenticate requests to the API, the person who configures SCIM on the IdP must use a personal access token (classic) with `admin:enterprise` scope, which the IdP must provide in the request's `Authorization` header. For more information about personal access tokens (classic), see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)". +To authenticate requests to the API, the person who configures SCIM on the IdP must use a {% data variables.product.pat_v1 %} with `admin:enterprise` scope, which the IdP must provide in the request's `Authorization` header. For more information about {% data variables.product.pat_v1_plural %}, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)". {% note %} -**Note:** Enterprise owners must generate and use a personal access token (classic) for authentication of requests to the SCIM API. {% ifversion ghes > 3.8 %}Fine-grained personal access tokens and {% endif %}GitHub app callers are not supported at this time. +**Note:** Enterprise owners must generate and use a {% data variables.product.pat_v1 %} for authentication of requests to the SCIM API. {% ifversion ghes > 3.8 %}{% data variables.product.pat_v2_caps %} and {% endif %}GitHub app callers are not supported at this time. {% endnote %} diff --git a/translations/pt-BR/content/rest/enterprise-admin/users.md b/translations/pt-BR/content/rest/enterprise-admin/users.md index 6d863f29ba..b5548dd5c7 100644 --- a/translations/pt-BR/content/rest/enterprise-admin/users.md +++ b/translations/pt-BR/content/rest/enterprise-admin/users.md @@ -1,17 +1,14 @@ --- -title: Usuários -intro: 'A API de Administração do Usuário permite que você suspenda{% ifversion ghes %}, cancele a suspensão, promova e rebaixe{% endif %}{% ifversion ghae %} e cancele a suspensão{% endif %} dos usuários da sua empresa.' +title: Users +intro: 'The User Administration API allows you to suspend{% ifversion ghes %}, unsuspend, promote, and demote{% endif %}{% ifversion ghae %} and unsuspend{% endif %} users on your enterprise.' versions: ghes: '*' ghae: '*' topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: a483065af09a2baef774cb8ce256350945106faa -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147063167' --- -*Ela só está disponível para administradores [autenticados](/rest/overview/resources-in-the-rest-api#authentication) do site.* Os usuários normais receberão uma resposta `403` se tentarem acessá-la. + +*It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `403` response if they try to access it. + +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} diff --git a/translations/pt-BR/content/rest/gitignore.md b/translations/pt-BR/content/rest/gitignore.md index 8cfb48b8e1..374cb4bb75 100644 --- a/translations/pt-BR/content/rest/gitignore.md +++ b/translations/pt-BR/content/rest/gitignore.md @@ -1,6 +1,6 @@ --- title: Gitignore -intro: A API Gitignore busca modelos `.gitignore` que podem ser usados para ignorar arquivos e diretórios. +intro: The Gitignore API fetches `.gitignore` templates that can be used to ignore files and directories. versions: fpt: '*' ghes: '*' @@ -11,21 +11,16 @@ topics: miniTocMaxHeadingLevel: 3 redirect_from: - /rest/reference/gitignore -ms.openlocfilehash: 082b626aac4af8dcdf435761447caeb015a608db -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147092883' --- -## Sobre a API do Gitignore -Quando você cria um repositório no {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} por meio da API, você pode especificar um [modelo .gitignore](/github/getting-started-with-github/ignoring-files) para aplicá-lo ao repositório após a criação. A API de modelos .gitignore lista modelos do [repositório .gitignore](https://github.com/github/gitignore) do {% data variables.product.product_name %} e efetua fetch deles. +## About the Gitignore API -### Tipos de mídia personalizados para gitignore +When you create a new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} via the API, you can specify a [.gitignore template](/github/getting-started-with-github/ignoring-files) to apply to the repository upon creation. The .gitignore templates API lists and fetches templates from the {% data variables.product.product_name %} [.gitignore repository](https://github.com/github/gitignore). -Você pode usar este tipo de mídia personalizada ao obter um modelo de gitignore. +### Custom media types for gitignore + +You can use this custom media type when getting a gitignore template. application/vnd.github.VERSION.raw -Para obter mais informações, confira "[Tipos de mídia](/rest/overview/media-types)". +For more information, see "[Media types](/rest/overview/media-types)." diff --git a/translations/pt-BR/content/rest/guides/building-a-ci-server.md b/translations/pt-BR/content/rest/guides/building-a-ci-server.md index daea393cca..afe94b461f 100644 --- a/translations/pt-BR/content/rest/guides/building-a-ci-server.md +++ b/translations/pt-BR/content/rest/guides/building-a-ci-server.md @@ -1,6 +1,6 @@ --- -title: Criar um servidor de CI -intro: Crie o seu próprio sistema CI usando a API de status. +title: Building a CI server +intro: Build your own CI system using the Status API. redirect_from: - /guides/building-a-ci-server - /v3/guides/building-a-ci-server @@ -11,31 +11,35 @@ versions: ghec: '*' topics: - API -ms.openlocfilehash: 5c2fcd462e9c07fb9c359525ece7896e10dd9649 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145126776' --- -A [API de Status][status API] é responsável por unir commits a um serviço de teste, de modo que cada push que você efetuar possa ser testado e representado em uma solicitação de pull do {% data variables.product.product_name %}. -Este guia usará a API para demonstrar uma configuração que você pode usar. -No nosso cenário, iremos: -* Executar o nosso conjunto de CI quando um pull request for aberto (iremos definir o status de CI como pendente). -* Quando o CI terminar, definiremos o status do pull request. -O nosso sistema de CI e servidor de hospedagem serão imaginários. Eles podem ser o Travis, o Jenkins ou qualquer outro completamente diferente. O aspecto fundamental deste guia será configurar o servidor que gerencia a comunicação. +The [Status API][status API] is responsible for tying together commits with +a testing service, so that every push you make can be tested and represented +in a {% data variables.product.product_name %} pull request. -Caso ainda não tenha feito isso, [baixe o ngrok][ngrok] e saiba como [usá-lo][using ngrok]. Achamos que ele é uma ferramenta muito útil para expor conexões locais. +This guide will use that API to demonstrate a setup that you can use. +In our scenario, we will: -Observação: baixe o código-fonte completo deste projeto [no repositório platform-samples][platform samples]. +* Run our CI suite when a Pull Request is opened (we'll set the CI status to pending). +* When the CI is finished, we'll set the Pull Request's status accordingly. -## Escrever o seu servidor +Our CI system and host server will be figments of our imagination. They could be +Travis, Jenkins, or something else entirely. The crux of this guide will be setting up +and configuring the server managing the communication. -Vamos escrever um aplicativo rápido do Sinatra para provar que nossas conexões locais estão funcionando. -Vamos começar com isso: +If you haven't already, be sure to [download ngrok][ngrok], and learn how +to [use it][using ngrok]. We find it to be a very useful tool for exposing local +connections. + +Note: you can download the complete source code for this project +[from the platform-samples repo][platform samples]. + +## Writing your server + +We'll write a quick Sinatra app to prove that our local connections are working. +Let's start with this: ``` ruby require 'sinatra' @@ -47,24 +51,29 @@ post '/event_handler' do end ``` -(Se você não estiver familiarizado com o funcionamento do Sinatra, recomendamos [ler o guia do Sinatra][Sinatra]). +(If you're unfamiliar with how Sinatra works, we recommend [reading the Sinatra guide][Sinatra].) -Inicie este servidor. Por padrão, o Sinatra começará na porta `4567`, ou seja, o ideal será configurar o ngrok para começar a escutá-la também. +Start this server up. By default, Sinatra starts on port `4567`, so you'll want +to configure ngrok to start listening for that, too. -Para que esse servidor funcione, precisamos configurar um repositório com um webhook. -O webhook deve ser configurado para ser acionado sempre que um pull request for criado ou mesclada. -Vá em frente e crie um repositório com o qual você esteja confortável para fazer testes. Podemos sugerir [o repositório do Spoon/do Knife de @octocat](https://github.com/octocat/Spoon-Knife)? -Depois disso, você criará um webhook no seu repositório, alimentando-o com a URL fornecida pelo ngrok e escolhendo `application/x-www-form-urlencoded` como o tipo de conteúdo: +In order for this server to work, we'll need to set a repository up with a webhook. +The webhook should be configured to fire whenever a Pull Request is created, or merged. +Go ahead and create a repository you're comfortable playing around in. Might we +suggest [@octocat's Spoon/Knife repository](https://github.com/octocat/Spoon-Knife)? +After that, you'll create a new webhook in your repository, feeding it the URL +that ngrok gave you, and choosing `application/x-www-form-urlencoded` as the +content type: -![Uma nova URL do ngrok](/assets/images/webhook_sample_url.png) +![A new ngrok URL](/assets/images/webhook_sample_url.png) -Clique em **Atualizar webhook**. Você verá a resposta de corpo `Well, it worked!`. -Ótimo! Clique em **Deixe-me selecionar eventos individuais** e selecione o seguinte: +Click **Update webhook**. You should see a body response of `Well, it worked!`. +Great! Click on **Let me select individual events**, and select the following: * Status * Pull Request -Esses são os eventos que o {% data variables.product.product_name %} enviará ao nosso servidor sempre que ocorrer a ação relevante. Vamos atualizar nosso servidor para *apenas* lidar com o cenário de solicitação de pull agora: +These are the events {% data variables.product.product_name %} will send to our server whenever the relevant action +occurs. Let's update our server to *just* handle the Pull Request scenario right now: ``` ruby post '/event_handler' do @@ -85,16 +94,26 @@ helpers do end ``` -O que está havendo? Cada evento que o {% data variables.product.product_name %} envia anexa um cabeçalho HTTP `X-GitHub-Event`. Por enquanto, nos importaremos apenas com os eventos do PR. Daí em diante, usaremos o conteúdo das informações e retornaremos o campo de título. Em um cenário ideal, nosso servidor ficará preocupado com a atualização de cada solicitação de pull, não apenas quando ela é aberta. Isso asseguraria que todos os novos pushes passassem pelos testes de CI. -Mas, para essa demonstração, nós nos preocuparemos quando ela for aberta. +What's going on? Every event that {% data variables.product.product_name %} sends out attached a `X-GitHub-Event` +HTTP header. We'll only care about the PR events for now. From there, we'll +take the payload of information, and return the title field. In an ideal scenario, +our server would be concerned with every time a pull request is updated, not just +when it's opened. That would make sure that every new push passes the CI tests. +But for this demo, we'll just worry about when it's opened. -Para testar esta prova de conceito, faça algumas alterações em um branch no repositório de teste e abra uma solicitação de pull. Seu servidor deve responder de acordo! +To test out this proof-of-concept, make some changes in a branch in your test +repository, and open a pull request. Your server should respond accordingly! -## Trabalhar com status +## Working with statuses -Com o servidor implementado, estamos prontos para iniciar nosso primeiro requisito, que é configurar (e atualizar) os status de CI. Observe que, a qualquer momento, você pode clicar em **Entregar novamente** para enviar o mesmo conteúdo. Não há necessidade de fazer uma nova solicitação de pull toda vez que você faz uma alteração. +With our server in place, we're ready to start our first requirement, which is +setting (and updating) CI statuses. Note that at any time you update your server, +you can click **Redeliver** to send the same payload. There's no need to make a +new pull request every time you make a change! -Como estamos interagindo com os dados da API do {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}, usaremos o [Octokit.rb][octokit.rb] para gerenciar as interações. Configuraremos esse cliente com [um token de acesso pessoal][access token]: +Since we're interacting with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll use [Octokit.rb][octokit.rb] +to manage our interactions. We'll configure that client with +[a {% data variables.product.pat_generic %}][access token]: ``` ruby # !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! @@ -106,7 +125,8 @@ before do end ``` -Em seguida, apenas precisaremos atualizar a solicitação de pull no {% data variables.product.product_name %} para deixar claro que estamos fazendo o processamento na CI: +After that, we'll just need to update the pull request on {% data variables.product.product_name %} to make clear +that we're processing on the CI: ``` ruby def process_pull_request(pull_request) @@ -115,13 +135,16 @@ def process_pull_request(pull_request) end ``` -Aqui, estamos fazendo três coisas muito básicas: +We're doing three very basic things here: -* estamos procurando o nome completo do repositório -* estamos procurando o último SHA do pull request -* estamos definindo o status como "pendente" +* we're looking up the full name of the repository +* we're looking up the last SHA of the pull request +* we're setting the status to "pending" -É isso! Daí em diante, você pode executar qualquer processo de que precise para executar o conjunto de testes. Talvez você transmita seu código para o Jenkins ou ligue para outro serviço Web por meio da API, como o [Travis][travis api]. Em seguida, lembre-se de atualizar o status novamente. Em nosso exemplo, vamos apenas defini-lo como `"success"`: +That's it! From here, you can run whatever process you need to in order to execute +your test suite. Maybe you're going to pass off your code to Jenkins, or call +on another web service via its API, like [Travis][travis api]. After that, you'd +be sure to update the status once more. In our example, we'll just set it to `"success"`: ``` ruby def process_pull_request(pull_request) @@ -132,18 +155,19 @@ def process_pull_request(pull_request) end ``` -## Conclusão +## Conclusion -No GitHub, usamos uma versão do [Janky][janky] para gerenciar a CI por vários anos. -O fluxo básico é essencialmente o mesmo que o servidor que construímos acima. -No GitHub, nós: +At GitHub, we've used a version of [Janky][janky] to manage our CI for years. +The basic flow is essentially the exact same as the server we've built above. +At GitHub, we: -* Notificamos tudo ao Jenkins quando um pull request é criado ou atualizado (via Janky) -* Esperamos por uma resposta no estado da CI -* Se o código for verde, fazemos o merge do pull request +* Fire to Jenkins when a pull request is created or updated (via Janky) +* Wait for a response on the state of the CI +* If the code is green, we merge the pull request -Toda esta comunicação é canalizada de volta para nossas salas de bate-papo. Você não precisa criar sua configuração de CI para usar este exemplo. -Você sempre pode contar com as [integrações do GitHub][integrations]. +All of this communication is funneled back to our chat rooms. You don't need to +build your own CI setup to use this example. +You can always rely on [GitHub integrations][integrations]. [deploy API]: /rest/reference/repos#deployments [status API]: /rest/reference/commits#commit-statuses diff --git a/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md b/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md index 273cbd7f29..ed666cdb27 100644 --- a/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md @@ -54,7 +54,7 @@ gh api /octocat --method GET To make a request using JavaScript, you can use Octokit.js. For more information, see [the Octokit.js README](https://github.com/octokit/octokit.js/#readme). -First, create an instance of `Octokit`.{% ifversion ghes or ghae %} Set the base URL to `{% data variables.product.api_url_code %}`. Replace `[hostname]` with the name of {% data variables.product.product_location %}.{% endif %} +First, create an instance of `Octokit`.{% ifversion ghes or ghae %} Set the base URL to `{% data variables.product.api_url_code %}`. Replace `[hostname]` with the name of {% data variables.location.product_location %}.{% endif %} ```javascript const octokit = new Octokit({ {% ifversion ghes or ghae %} @@ -72,7 +72,7 @@ await octokit.request("GET /octocat", {}); {% curl %} -Prepend the base URL for the {% data variables.product.prodname_dotcom %} REST API, `{% data variables.product.api_url_code %}`, to the path to get the full URL: `{% data variables.product.api_url_code %}/octocat`.{% ifversion ghes or ghae %} Replace `[hostname]` with the name of {% data variables.product.product_location %}.{% endif %} +Prepend the base URL for the {% data variables.product.prodname_dotcom %} REST API, `{% data variables.product.api_url_code %}`, to the path to get the full URL: `{% data variables.product.api_url_code %}/octocat`.{% ifversion ghes or ghae %} Replace `[hostname]` with the name of {% data variables.location.product_location %}.{% endif %} Use the `curl` command in your command line. Use the `--request` or `-X` flag followed by the HTTP method. Use the `--url` flag followed by the full URL. @@ -99,7 +99,7 @@ Many operations require authentication or return additional information if you a You can authenticate your request by adding a token. -If you want to use the {% data variables.product.company_short %} REST API for personal use, you can create a personal access token (PAT). The REST API operations used in this article require `repo` scope for personal access tokens. Other operations may require different scopes. For more information about creating a personal access token, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." +If you want to use the {% data variables.product.company_short %} REST API for personal use, you can create a {% data variables.product.pat_generic %}. The REST API operations used in this article require `repo` scope for {% data variables.product.pat_v1_plural %}{% ifversion pat-v2 %} or, unless otherwise noted, read-only access to public repositories for {% data variables.product.pat_v2 %}s{% endif %}. Other operations may require different scopes{% ifversion pat-v2%} or permissions{% endif %}. For more information about creating a {% data variables.product.pat_generic %}, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." If you want to use the API on behalf of an organization or another user, {% data variables.product.company_short %} recommends that you use a {% data variables.product.prodname_github_app %}. If an operation is available to {% data variables.product.prodname_github_apps %}, the REST reference documentation for that operation will say "Works with GitHub Apps." The REST API operations used in this article require `issues` read and write permissions for {% data variables.product.prodname_github_apps %}. Other operations may require different permissions. For more information, see "[Creating a GitHub App](/developers/apps/building-github-apps/creating-a-github-app)", "[Authenticating with GitHub Apps](/developers/apps/building-github-apps/authenticating-with-github-apps), and "[Identifying and authorizing users for GitHub Apps](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps)." @@ -133,7 +133,7 @@ If these options are not possible, consider using another service such as [the 1 {% endwarning %} -To authenticate with the Octokit.js library, you can pass your token when you create an instance of `Octokit`. Replace `YOUR-TOKEN` with your token.{% ifversion ghes or ghae %} Replace `[hostname]` with the name of {% data variables.product.product_location %}.{% endif %} +To authenticate with the Octokit.js library, you can pass your token when you create an instance of `Octokit`. Replace `YOUR-TOKEN` with your token.{% ifversion ghes or ghae %} Replace `[hostname]` with the name of {% data variables.location.product_location %}.{% endif %} ```javascript const octokit = new Octokit({ {% ifversion ghes or ghae %} @@ -225,7 +225,7 @@ jobs: - name: Setup Node uses: {% data reusables.actions.action-setup-node %} with: - node-version: '16.15.0' + node-version: '16.17.0' cache: npm - name: Install dependencies @@ -340,7 +340,7 @@ Path parameters modify the operation path. For example, the "List repository iss {% ifversion ghes or ghae %} {% note %} -**Note:** In order for this command to work for {% data variables.product.product_location %}, replace `octocat/Spoon-Knife` with a repository owned by {% data variables.product.product_location %}. Otherwise, rerun the `gh auth login` command to authenticate to {% data variables.product.prodname_dotcom_the_website %} instead of {% data variables.product.product_location %}. +**Note:** In order for this command to work for {% data variables.location.product_location %}, replace `octocat/Spoon-Knife` with a repository owned by {% data variables.location.product_location %}. Otherwise, rerun the `gh auth login` command to authenticate to {% data variables.product.prodname_dotcom_the_website %} instead of {% data variables.location.product_location %}. {% endnote %} {% endif %} @@ -358,7 +358,7 @@ gh api --header 'Accept: application/vnd.github+json' --method GET /repos/octoca {% ifversion ghes or ghae %} {% note %} -**Note:** In order for this example to work for {% data variables.product.product_location %}, replace `octocat/Spoon-Knife` with a repository owned by {% data variables.product.product_location %}. Otherwise, create a new `Octokit` instance and do not specify `baseURL`. +**Note:** In order for this example to work for {% data variables.location.product_location %}, replace `octocat/Spoon-Knife` with a repository owned by {% data variables.location.product_location %}. Otherwise, create a new `Octokit` instance and do not specify `baseURL`. {% endnote %} {% endif %} @@ -381,7 +381,7 @@ To get issues from the `octocat/Spoon-Knife` repository, replace `{owner}` with {% ifversion ghes or ghae %} {% note %} -**Note:** If you want to use {% data variables.product.product_location %} instead of {% data variables.product.prodname_dotcom_the_website %}, use `{% data variables.product.api_url_code %}` instead of `https://api.github.com` and replace `[hostname]` with the name of {% data variables.product.product_location %}. Replace `octocat/Spoon-Knife` with a repository owned by {% data variables.product.product_location %}. +**Note:** If you want to use {% data variables.location.product_location %} instead of {% data variables.product.prodname_dotcom_the_website %}, use `{% data variables.product.api_url_code %}` instead of `https://api.github.com` and replace `[hostname]` with the name of {% data variables.location.product_location %}. Replace `octocat/Spoon-Knife` with a repository owned by {% data variables.location.product_location %}. {% endnote %} {% endif %} @@ -474,6 +474,16 @@ gh api --header 'Accept: application/vnd.github+json' --method POST /repos/octoc {% javascript %} +{% ifversion pat-v2 %} + +{% note %} + +If you are using a {% data variables.product.pat_v2 %}, you must replace `octocat/Spoon-Knife` with a repository that you own or that is owned by an organization that you are a member of. Your token must have access to that repository and have read and write permissions for repository issues. For more information about creating a repository, see "[Create a repo](/get-started/quickstart/create-a-repo)." For more information about granting access and permissions to a {% data variables.product.pat_v2 %}, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." + +{% endnote %} + +{% endif %} + When you make a request with Octokit.js, all parameters, including body parameters, are passed in an object as the second argument to the `request` method. ```javascript @@ -489,6 +499,16 @@ await octokit.request("POST /repos/{owner}/{repo}/issues", { {% curl %} +{% ifversion pat-v2 %} + +{% note %} + +If you are using a {% data variables.product.pat_v2 %}, you must replace `octocat/Spoon-Knife` with a repository that you own or that is owned by an organization that you are a member of. Your token must have access to that repository and have read and write permissions for repository issues. For more information about creating a repository, see "[Create a repo](/get-started/quickstart/create-a-repo)." For more information about granting access and permissions to a {% data variables.product.pat_v2 %}, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." + +{% endnote %} + +{% endif %} + For cURL, use the `--data` flag to pass the body parameters in a JSON object. ```shell @@ -556,7 +576,7 @@ X-Ratelimit-Used: 4 X-Xss-Protection: 0 ``` -In this example, the response code is `200`, which indicates a successful request. +In this example, the response code is `200`, which indicates a successful request. {% endcli %} @@ -627,7 +647,7 @@ content-length: 4936 x-github-request-id: 14E0:4BC6:F1B8BA:208E317:62EC2715 ``` -In this example, the response code is `200`, which indicates a successful request. +In this example, the response code is `200`, which indicates a successful request. {% endcurl %} diff --git a/translations/pt-BR/content/rest/guides/traversing-with-pagination.md b/translations/pt-BR/content/rest/guides/traversing-with-pagination.md index ddbfefdf0d..ed7f9b1189 100644 --- a/translations/pt-BR/content/rest/guides/traversing-with-pagination.md +++ b/translations/pt-BR/content/rest/guides/traversing-with-pagination.md @@ -1,6 +1,6 @@ --- -title: Deslocamento com paginação -intro: Explore como usar a paginação para gerenciar as suas respostas com alguns exemplos usando a API de pesquisa. +title: Traversing with pagination +intro: Explore how to use pagination to manage your responses with some examples using the Search API. redirect_from: - /guides/traversing-with-pagination - /v3/guides/traversing-with-pagination @@ -12,84 +12,104 @@ versions: topics: - API shortTitle: Traverse with pagination -ms.openlocfilehash: be0e961847e187b72848eda558636fe3ecb800bd -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145126758' --- -A {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API fornece uma vasta riqueza de informações para os desenvolvedores consumirem. -Na maioria das vezes, você poderá até descobrir que está solicitando _muita_ informação e, para manter nossos servidores satisfeitos, a API [paginará automaticamente os itens solicitados](/rest/overview/resources-in-the-rest-api#pagination). -Neste guia, faremos algumas chamadas à API de Pesquisa e iterar nos resultados usando a paginação. Encontre o código-fonte completo deste projeto no repositório [platform-samples][platform samples]. +The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API provides a vast wealth of information for developers to consume. +Most of the time, you might even find that you're asking for _too much_ information, +and in order to keep our servers happy, the API will automatically [paginate the requested items](/rest/overview/resources-in-the-rest-api#pagination). + +In this guide, we'll make some calls to the Search API, and iterate over +the results using pagination. You can find the complete source code for this project +in the [platform-samples][platform samples] repository. {% data reusables.rest-api.dotcom-only-guide-note %} -## Fundamentos da paginação +## Basics of Pagination -Para começar, é importante conhecer alguns fatos sobre o recebimento de itens paginados: +To start with, it's important to know a few facts about receiving paginated items: -1. Diferentes chamadas de API respondem com diferentes padrões. Por exemplo, uma chamada a [Listar repositórios públicos](/rest/reference/repos#list-public-repositories) fornece itens paginados em conjuntos de 30, enquanto uma chamada à API de Pesquisa do GitHub fornece itens em conjuntos de 100 -2. Você pode especificar quantos itens receber (até um máximo de 100); mas -3. Por razões técnicas, nem todos os pontos de referência comportam-se da mesma forma. Por exemplo, os [eventos](/rest/reference/activity#events) não permitirão que você defina um número máximo para os itens a serem recebidos. -Leia a documentação sobre como lidar com resultados paginados para pontos de extremidade específicos. +1. Different API calls respond with different defaults. For example, a call to +[List public repositories](/rest/reference/repos#list-public-repositories) +provides paginated items in sets of 30, whereas a call to the GitHub Search API +provides items in sets of 100 +2. You can specify how many items to receive (up to a maximum of 100); but, +3. For technical reasons, not every endpoint behaves the same. For example, +[events](/rest/reference/activity#events) won't let you set a maximum for items to receive. +Be sure to read the documentation on how to handle paginated results for specific endpoints. -Informações sobre paginação são fornecidas no [cabeçalho Link](https://datatracker.ietf.org/doc/html/rfc5988) de uma chamada à API. Por exemplo, vamos fazer uma solicitação do cURL à API de pesquisa para descobrir quantas vezes os projetos da Mozilla usam a frase `addClass`: +Information about pagination is provided in [the Link header](https://datatracker.ietf.org/doc/html/rfc5988) +of an API call. For example, let's make a curl request to the search API, to find +out how many times Mozilla projects use the phrase `addClass`: ```shell $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla" ``` -O parâmetro `-I` indica que só nos importamos com os cabeçalhos, não com o conteúdo real. Ao examinar o resultado, você notará algumas informações no cabeçalho -Link parecidas com estas: +The `-I` parameter indicates that we only care about the headers, not the actual +content. In examining the result, you'll notice some information in the Link header +that looks like this: Link: ; rel="next", ; rel="last" -Vamos explicar isso. `rel="next"` indica que a próxima página é `page=2`. Isso faz sentido, pois, por padrão, todas as consultas paginadas começam na página `1.` `rel="last"` fornece mais informações, indicando que a última página de resultados está na página `34`. -Assim, temos mais 33 páginas de informações sobre o `addClass` que podemos consumir. -Ótimo! +Let's break that down. `rel="next"` says that the next page is `page=2`. This makes +sense, since by default, all paginated queries start at page `1.` `rel="last"` +provides some more information, stating that the last page of results is on page `34`. +Thus, we have 33 more pages of information about `addClass` that we can consume. +Nice! -**Sempre** confie nessas relações de vínculo fornecidas a você. Não tente adivinhar nem construir a sua própria URL. +**Always** rely on these link relations provided to you. Don't try to guess or construct your own URL. -### Navegando pelas páginas +### Navigating through the pages -Agora que você sabe quantas páginas há para receber, comece a navegar por elas para consumir os resultados. Faça isso transmitindo um parâmetro `page`. Por padrão, `page` sempre começa em `1`. Vamos pular para a página 14 e ver o que acontece: +Now that you know how many pages there are to receive, you can start navigating +through the pages to consume the results. You do this by passing in a `page` +parameter. By default, `page` always starts at `1`. Let's jump ahead to page 14 +and see what happens: ```shell $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&page=14" ``` -Aqui está o cabeçalho do link mais uma vez: +Here's the link header once more: Link: ; rel="next", ; rel="last", ; rel="first", ; rel="prev" -Como esperado, `rel="next"` está em 15, e `rel="last"` ainda é 34. Mas agora temos mais informações: `rel="first"` indica a URL da _primeira_ página e o mais importante: `rel="prev"` informa o número da página anterior. Ao usar essas informações, você pode construir uma interface do usuário que permite que os usuários pulem entre a primeira, a anterior, a seguinte ou a última lista de resultados em uma chamada à API. +As expected, `rel="next"` is at 15, and `rel="last"` is still 34. But now we've +got some more information: `rel="first"` indicates the URL for the _first_ page, +and more importantly, `rel="prev"` lets you know the page number of the previous +page. Using this information, you could construct some UI that lets users jump +between the first, previous, next, or last list of results in an API call. -### Alterar o número de itens recebidos +### Changing the number of items received -Ao transmitir o parâmetro `per_page`, você pode especificar quantos itens deseja retornar em cada página, até o limite de 100 itens. Vamos experimentar solicitar 50 itens sobre `addClass`: +By passing the `per_page` parameter, you can specify how many items you want +each page to return, up to 100 items. Let's try asking for 50 items about `addClass`: ```shell $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&per_page=50" ``` -Observe o que ele faz com a resposta do cabeçalho: +Notice what it does to the header response: Link: ; rel="next", ; rel="last" -Como você deve ter imaginado, as informações de `rel="last"` indicam que a última página agora é a 20. Isso ocorre porque estamos solicitando mais informações por página sobre os resultados. +As you might have guessed, the `rel="last"` information says that the last page +is now 20. This is because we are asking for more information per page about +our results. -## Consumir informações +## Consuming the information -Você não deseja fazer chamadas de baixo nível ao cURL apenas para trabalhar com a paginação. Portanto, vamos escrever um pequeno script do Ruby que faz tudo o que descrevemos acima. +You don't want to be making low-level curl calls just to be able to work with +pagination, so let's write a little Ruby script that does everything we've +just described above. -Como sempre, primeiro, precisaremos da [biblioteca Octokit.rb do Ruby do GitHub][octokit.rb] e transmitiremos nosso [token de acesso pessoal][personal token]: +As always, first we'll require [GitHub's Octokit.rb][octokit.rb] Ruby library, and +pass in our [{% data variables.product.pat_generic %}][personal token]: ``` ruby require 'octokit' @@ -99,17 +119,26 @@ require 'octokit' client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN'] ``` -Em seguida, executaremos a pesquisa usando o método `search_code` do Octokit. Ao contrário do uso do `curl`, também podemos recuperar imediatamente o número de resultados. Portanto, vamos fazer isso: +Next, we'll execute the search, using Octokit's `search_code` method. Unlike +using `curl`, we can also immediately retrieve the number of results, so let's +do that: ``` ruby results = client.search_code('addClass user:mozilla') total_count = results.total_count ``` -Agora, vamos usar o número da última página, de maneira similar as informações de `page=34>; rel="last"` no cabeçalho Link. O Octokit.rb dá suporte a informações de paginação por meio de uma implementação chamada "[Relações de vínculo de hipermídia][hypermedia-relations]". -Não entraremos em detalhes sobre o que ela é, mas basta dizer que cada elemento na variável `results` tem um hash chamado `rels`, que pode conter informações sobre `:next`, `:last`, `:first` e `:prev`, dependendo do resultado em que você está. Essas relações também contêm informações sobre a URL resultante, pela chamada a `rels[:last].href`. +Now, let's grab the number of the last page, similar to `page=34>; rel="last"` +information in the link header. Octokit.rb support pagination information through +an implementation called "[Hypermedia link relations][hypermedia-relations]." +We won't go into detail about what that is, but, suffice to say, each element +in the `results` variable has a hash called `rels`, which can contain information +about `:next`, `:last`, `:first`, and `:prev`, depending on which result you're +on. These relations also contain information about the resulting URL, by calling +`rels[:last].href`. -Sabendo disso, vamos usar o número de página do último resultado e apresentar todas essas informações ao usuário: +Knowing this, let's grab the page number of the last result, and present all +this information to the user: ``` ruby last_response = client.last_response @@ -118,8 +147,13 @@ number_of_pages = last_response.rels[:last].href.match(/page=(\d+).*$/)[1] puts "There are #{total_count} results, on #{number_of_pages} pages!" ``` -Finalmente, vamos iterar entre os resultados. Você pode fazer isso com um loop `for i in 1..number_of_pages.to_i`, mas vamos seguir os cabeçalhos `rels[:next]` para recuperar as informações de cada página. Para simplificar, vamos apenas usar o caminho do arquivo do primeiro resultado de cada página. Para fazer isso, precisaremos de um loop, e, no final de cada loop, recuperaremos o conjunto de dados da próxima página seguindo as informações de `rels[:next]`. -O loop será concluído quando não houver informações de `rels[:next]` a serem consumidas (em outras palavras, estivermos em `rels[:last]`). Poderá ser semelhante ao seguinte: +Finally, let's iterate through the results. You could do this with a loop `for i in 1..number_of_pages.to_i`, +but instead, let's follow the `rels[:next]` headers to retrieve information from +each page. For the sake of simplicity, let's just grab the file path of the first +result from each page. To do this, we'll need a loop; and at the end of every loop, +we'll retrieve the data set for the next page by following the `rels[:next]` information. +The loop will finish when there is no `rels[:next]` information to consume (in other +words, we are at `rels[:last]`). It might look something like this: ``` ruby puts last_response.data.items.first.path @@ -129,7 +163,9 @@ until last_response.rels[:next].nil? end ``` -Alterar o número de itens por página é extremamente simples com Octokit.rb. Basta transmitir um hash de opções `per_page` para a construção inicial do cliente. Depois disso, o código permanecerá intacto: +Changing the number of items per page is extremely simple with Octokit.rb. Simply +pass a `per_page` options hash to the initial client construction. After that, +your code should remain intact: ``` ruby require 'octokit' @@ -156,15 +192,17 @@ until last_response.rels[:next].nil? end ``` -## Construir links de paginação +## Constructing Pagination Links -Normalmente, com a paginação, sua meta não é concatenar todos os resultados possíveis, mas produzir um conjunto de navegação, como este: +Normally, with pagination, your goal isn't to concatenate all of the possible +results, but rather, to produce a set of navigation, like this: -![Amostra dos links de paginação](/assets/images/pagination_sample.png) +![Sample of pagination links](/assets/images/pagination_sample.png) -Vamos esboçar uma microversão do que isso poderia implicar. +Let's sketch out a micro-version of what that might entail. -Com base no código acima, já sabemos que podemos obter o `number_of_pages` nos resultados paginados com a primeira chamada: +From the code above, we already know we can get the `number_of_pages` in the +paginated results from the first call: ``` ruby require 'octokit' @@ -183,7 +221,7 @@ puts last_response.rels[:last].href puts "There are #{total_count} results, on #{number_of_pages} pages!" ``` -A partir daí, podemos construir uma linda representação em ASCII das caixas numéricas: +From there, we can construct a beautiful ASCII representation of the number boxes: ``` ruby numbers = "" for i in 1..number_of_pages.to_i @@ -192,7 +230,8 @@ end puts numbers ``` -Vamos simular um usuário clicando em uma dessas caixas, construindo um número aleatório: +Let's simulate a user clicking on one of these boxes, by constructing a random +number: ``` ruby random_page = Random.new @@ -201,13 +240,15 @@ random_page = random_page.rand(1..number_of_pages.to_i) puts "A User appeared, and clicked number #{random_page}!" ``` -Agora que temos um número de página, podemos usar o Octokit para recuperar explicitamente essa página individual transmitindo a opção `:page`: +Now that we have a page number, we can use Octokit to explicitly retrieve that +individual page, by passing the `:page` option: ``` ruby clicked_results = client.search_code('addClass user:mozilla', :page => random_page) ``` -Caso desejemos incrementar um pouco, também podemos usar as páginas anterior e a próxima a fim de gerar links para os elementos anterior (`<<`) e posterior (`>>`): +If we wanted to get fancy, we could also grab the previous and next pages, in +order to generate links for back (`<<`) and forward (`>>`) elements: ``` ruby prev_page_href = client.last_response.rels[:prev] ? client.last_response.rels[:prev].href : "(none)" diff --git a/translations/pt-BR/content/rest/guides/working-with-comments.md b/translations/pt-BR/content/rest/guides/working-with-comments.md index eb6228a632..201ac1ffe3 100644 --- a/translations/pt-BR/content/rest/guides/working-with-comments.md +++ b/translations/pt-BR/content/rest/guides/working-with-comments.md @@ -1,6 +1,6 @@ --- -title: Trabalhar com comentários -intro: 'Ao usar a API REST, você pode acessar e gerenciar comentários nos seus pull requests, problemas ou commits.' +title: Working with comments +intro: 'Using the REST API, you can access and manage comments in your pull requests, issues, or commits.' redirect_from: - /guides/working-with-comments - /v3/guides/working-with-comments @@ -11,26 +11,31 @@ versions: ghec: '*' topics: - API -ms.openlocfilehash: 9b3b768d66199fda62bc5e644da9539d5425215e -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145126757' --- -Para qualquer solicitação de pull, o {% data variables.product.product_name %} fornece três tipos de exibições de comentários: [comentários sobre a solicitação de pull][PR comment] como um todo, [comentários sobre uma linha específica][PR line comment] na solicitação de pull e [comentários sobre um commit específico][commit comment] na solicitação de pull. -Cada um desses tipos de comentários passa por uma parte diferente da {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API. -Neste guia, vamos explorar como você pode acessar e manipular cada um. Para cada exemplo, usaremos [este exemplo de solicitação de pull criado][sample PR] no repositório "octocat". Como sempre, os exemplos podem ser encontrados em [nosso repositório platform-samples][platform-samples]. -## Comentários do Pull Request -Para acessar os comentários sobre uma solicitação de pull, você passará pela [API de Problemas][issues]. -A princípio, isso pode parecer contraintuitivo. Mas depois que você entender que uma solicitação de pull é apenas um problema com um código, fará sentido usar a API de Problemas para criar comentários sobre uma solicitação de pull. +For any Pull Request, {% data variables.product.product_name %} provides three kinds of comment views: +[comments on the Pull Request][PR comment] as a whole, [comments on a specific line][PR line comment] within the Pull Request, +and [comments on a specific commit][commit comment] within the Pull Request. -Demonstraremos como buscar comentários de uma solicitação de pull criando um script do Ruby usando o [Octokit.rb][octokit.rb]. O ideal também é criar um [token de acesso pessoal][personal token]. +Each of these types of comments goes through a different portion of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API. +In this guide, we'll explore how you can access and manipulate each one. For every +example, we'll be using [this sample Pull Request made][sample PR] on the "octocat" +repository. As always, samples can be found in [our platform-samples repository][platform-samples]. -O seguinte código ajudará você a começar a acessar os comentários de uma solicitação de pull usando o Octokit.rb: +## Pull Request Comments + +To access comments on a Pull Request, you'll go through [the Issues API][issues]. +This may seem counterintuitive at first. But once you understand that a Pull +Request is just an Issue with code, it makes sense to use the Issues API to +create comments on a Pull Request. + +We'll demonstrate fetching Pull Request comments by creating a Ruby script using +[Octokit.rb][octokit.rb]. You'll also want to create a [{% data variables.product.pat_generic %}][personal token]. + +The following code should help you get started accessing comments from a Pull Request +using Octokit.rb: ``` ruby require 'octokit' @@ -48,13 +53,18 @@ client.issue_comments("octocat/Spoon-Knife", 1176).each do |comment| end ``` -Aqui, especificamente, chamamos a API de Problemas para obter os comentários (`issue_comments`), fornecendo o nome do repositório (`octocat/Spoon-Knife`) e a ID da solicitação de pull na qual estamos interessados (`1176`). Depois disso, é simplesmente uma questão de iterar pelos comentários para buscar informações sobre cada um. +Here, we're specifically calling out to the Issues API to get the comments (`issue_comments`), +providing both the repository's name (`octocat/Spoon-Knife`), and the Pull Request ID +we're interested in (`1176`). After that, it's simply a matter of iterating through +the comments to fetch information about each one. -## Comentários em uma linha de Pull Request +## Pull Request Comments on a Line -Na exibição de comparação, você pode iniciar uma discussão sobre um aspecto específico de uma alteração singular feita na solicitação de pull. Esses comentários ocorrem nas linhas individuais de um arquivo alterado. A URL do ponto de extremidade para essa discussão foi obtida [da API de Revisão de Solicitação de Pull][PR Review API]. +Within the diff view, you can start a discussion on a particular aspect of a singular +change made within the Pull Request. These comments occur on the individual lines +within a changed file. The endpoint URL for this discussion comes from [the Pull Request Review API][PR Review API]. -O código a seguir busca todos os comentários de pull request feitos em arquivos, dado um único número de pull request: +The following code fetches all the Pull Request comments made on files, given a single Pull Request number: ``` ruby require 'octokit' @@ -74,15 +84,19 @@ client.pull_request_comments("octocat/Spoon-Knife", 1176).each do |comment| end ``` -Você perceberá que ele é incrivelmente semelhante ao exemplo acima. A diferença entre esta exibição e o comentário sobre a solicitação de pull é o foco da conversa. -Um comentário feito em uma solicitação de pull deve ser reservado para discussão ou ideias sobre a orientação geral do código. Um comentário feito como parte de uma revisão de solicitação de pull deve lidar especificamente com a forma como determinada alteração foi implementada em um arquivo. +You'll notice that it's incredibly similar to the example above. The difference +between this view and the Pull Request comment is the focus of the conversation. +A comment made on a Pull Request should be reserved for discussion or ideas on +the overall direction of the code. A comment made as part of a Pull Request review should +deal specifically with the way a particular change was implemented within a file. -## Comentários de commit +## Commit Comments -O último tipo de comentários ocorre especificamente nos commits individuais. Por esse motivo, eles usam [a API de comentário de commit][commit comment API]. +The last type of comments occur specifically on individual commits. For this reason, +they make use of [the commit comment API][commit comment API]. -Para recuperar os comentários em um commit, você deverá usar o SHA1 do commit. -Em outras palavras, você não usará nenhum identificador relacionado ao Pull Request. Veja um exemplo: +To retrieve the comments on a commit, you'll want to use the SHA1 of the commit. +In other words, you won't use any identifier related to the Pull Request. Here's an example: ``` ruby require 'octokit' @@ -100,7 +114,8 @@ client.commit_comments("octocat/Spoon-Knife", "cbc28e7c8caee26febc8c013b0adfb97a end ``` -Observe que essa chamada à API vai recuperar os comentários de linha única, bem como os comentários feitos em todo o commit. +Note that this API call will retrieve single line comments, as well as comments made +on the entire commit. [PR comment]: https://github.com/octocat/Spoon-Knife/pull/1176#issuecomment-24114792 [PR line comment]: https://github.com/octocat/Spoon-Knife/pull/1176#discussion_r6252889 diff --git a/translations/pt-BR/content/rest/migrations/source-imports.md b/translations/pt-BR/content/rest/migrations/source-imports.md index 7fec749b98..0034ccd814 100644 --- a/translations/pt-BR/content/rest/migrations/source-imports.md +++ b/translations/pt-BR/content/rest/migrations/source-imports.md @@ -1,5 +1,5 @@ --- -title: Importações de código-fonte +title: Source imports intro: '' versions: fpt: '*' @@ -7,18 +7,15 @@ versions: topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 339b7f9543e91d2d33566435289b2092ef8c02e8 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147065767' --- -## Sobre a API de Importações de código-fonte -{% data variables.migrations.source_imports_intro %} Uma importação de código-fonte típica iniciaria a importação e, em seguida, (opcionalmente) atualizaria os autores e/ou atualizaria a preferência pelo uso do Git LFS se existissem arquivos grandes na importação. Você também pode criar um webhook que escuta no [`RepositoryImportEvent`](/developers/webhooks-and-events/webhook-events-and-payloads#repository_import) para descobrir o status da importação. +## About the Source imports API -Um exemplo mais detalhado pode ser visto neste diagrama: +{% data reusables.user-settings.imports-api-classic-pat-only %} + +{% data variables.migrations.source_imports_intro %} A typical source import would start the import and then (optionally) update the authors and/or update the preference for using Git LFS if large files exist in the import. You can also create a webhook that listens for the [`RepositoryImportEvent`](/developers/webhooks-and-events/webhook-events-and-payloads#repository_import) to find out the status of the import. + +A more detailed example can be seen in this diagram: ``` +---------+ +--------+ +---------------------+ diff --git a/translations/pt-BR/content/rest/overview/index.md b/translations/pt-BR/content/rest/overview/index.md index ed7fa5461e..8bf367bf84 100644 --- a/translations/pt-BR/content/rest/overview/index.md +++ b/translations/pt-BR/content/rest/overview/index.md @@ -18,7 +18,9 @@ children: - /libraries - /openapi-description - /endpoints-available-for-github-apps + - /endpoints-available-for-fine-grained-personal-access-tokens - /permissions-required-for-github-apps + - /permissions-required-for-fine-grained-personal-access-tokens ms.openlocfilehash: 96d6109d1dcd2571ada7e448459980fdf6a92e05 ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a ms.translationtype: HT diff --git a/translations/pt-BR/content/rest/overview/other-authentication-methods.md b/translations/pt-BR/content/rest/overview/other-authentication-methods.md index 9cebcf591a..cd303a1c11 100644 --- a/translations/pt-BR/content/rest/overview/other-authentication-methods.md +++ b/translations/pt-BR/content/rest/overview/other-authentication-methods.md @@ -26,7 +26,7 @@ Instead, they should use the [OAuth web flow](/apps/building-oauth-apps/authoriz {% ifversion ghae %} -To authenticate we recommend using [OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/) tokens, such a personal access token through the [OAuth web flow](/apps/building-oauth-apps/authorizing-oauth-apps/). +To authenticate we recommend using [OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/) tokens, such a {% data variables.product.pat_generic %} through the [OAuth web flow](/apps/building-oauth-apps/authorizing-oauth-apps/). {% endif %} @@ -40,15 +40,15 @@ the existence of user data. Instead, the {% ifversion fpt or ghec %}{% data vari This may cause problems for HTTP libraries that assume a `401 Unauthorized` response. The solution is to manually craft the `Authorization` header. -### Via OAuth and personal access tokens +### Via {% data variables.product.pat_generic %}s -We recommend you use OAuth tokens to authenticate to the GitHub API. OAuth tokens include [personal access tokens][personal-access-tokens] and enable the user to revoke access at any time. +We recommend you use {% ifversion pat-v2%}{% data variables.product.pat_v2 %}s{% else %}{% data variables.product.pat_generic %}s{% endif %} to authenticate to the GitHub API. ```shell $ curl -u USERNAME:TOKEN {% data variables.product.api_url_pre %}/user ``` -This approach is useful if your tools only support Basic Authentication but you want to take advantage of OAuth access token security features. +This approach is useful if your tools only support Basic Authentication but you want to take advantage of {% data variables.product.pat_generic %} security features. ### Via username and password @@ -56,7 +56,7 @@ This approach is useful if your tools only support Basic Authentication but you {% note %} -**Note:** {% data variables.product.prodname_dotcom %} has discontinued password authentication to the API starting on November 13, 2020 for all {% data variables.product.prodname_dotcom_the_website %} accounts, including those on a {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_ghe_cloud %} plan. You must now authenticate to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API with an API token, such as an OAuth access token, GitHub App installation access token, or personal access token, depending on what you need to do with the token. For more information, see "[Troubleshooting](/rest/overview/troubleshooting#basic-authentication-errors)." +**Note:** {% data variables.product.prodname_dotcom %} has discontinued password authentication to the API starting on November 13, 2020 for all {% data variables.product.prodname_dotcom_the_website %} accounts, including those on a {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_ghe_cloud %} plan. You must now authenticate to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API with an API token, such as an OAuth access token, GitHub App installation access token, or {% data variables.product.pat_generic %}, depending on what you need to do with the token. For more information, see "[Troubleshooting](/rest/overview/troubleshooting#basic-authentication-errors)." {% endnote %} @@ -92,7 +92,7 @@ If you have two-factor authentication enabled, make sure you understand how to [ {% endnote %} -If you're using the API to access an organization that enforces [SAML SSO][saml-sso] for authentication, you'll need to create a personal access token (PAT) and [authorize the token][allowlist] for that organization. Visit the URL specified in `X-GitHub-SSO` to authorize the token for the organization. +If you're using the API to access an organization that enforces [SAML SSO][saml-sso] for authentication, you'll need to create a {% data variables.product.pat_generic %} and [authorize the token][allowlist] for that organization. Visit the URL specified in `X-GitHub-SSO` to authorize the token for the organization. ```shell $ curl -v -H "Authorization: Bearer TOKEN" {% data variables.product.api_url_pre %}/repos/octodocs-test/test @@ -104,7 +104,7 @@ $ curl -v -H "Authorization: Bearer TOKEN" {% data variables.product.api_url_pre } ``` -When requesting data that could come from multiple organizations (for example, [requesting a list of issues created by the user][user-issues]), the `X-GitHub-SSO` header indicates which organizations require you to authorize your personal access token: +When requesting data that could come from multiple organizations (for example, [requesting a list of issues created by the user][user-issues]), the `X-GitHub-SSO` header indicates which organizations require you to authorize your {% data variables.product.pat_generic %}: ```shell $ curl -v -H "Authorization: Bearer TOKEN" {% data variables.product.api_url_pre %}/user/issues @@ -112,15 +112,15 @@ $ curl -v -H "Authorization: Bearer TOKEN" {% data variables.product.api_url_pre > X-GitHub-SSO: partial-results; organizations=21955855,20582480 ``` -The value `organizations` is a comma-separated list of organization IDs for organizations require authorization of your personal access token. +The value `organizations` is a comma-separated list of organization IDs for organizations require authorization of your {% data variables.product.pat_generic %}. {% endif %} {% ifversion fpt or ghes or ghec %} ## Working with two-factor authentication -When you have two-factor authentication enabled, [Basic Authentication](#basic-authentication) for _most_ endpoints in the REST API requires that you use a personal access token{% ifversion ghes %} or OAuth token instead of your username and password{% endif %}. +When you have two-factor authentication enabled, [Basic Authentication](#basic-authentication) for _most_ endpoints in the REST API requires that you use a {% data variables.product.pat_generic %}{% ifversion ghes %} or OAuth token instead of your username and password{% endif %}. -You can generate a new personal access token {% ifversion fpt or ghec %}using [{% data variables.product.product_name %} developer settings](https://github.com/settings/tokens/new){% endif %}{% ifversion ghes %} or with the "[Create a new authorization][/rest/reference/oauth-authorizations#create-a-new-authorization]" endpoint in the OAuth Authorizations API to generate a new OAuth token{% endif %}. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". Then you would use these tokens to [authenticate using OAuth token][oauth-auth] with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.{% ifversion ghes %} The only time you need to authenticate with your username and password is when you create your OAuth token or use the OAuth Authorizations API.{% endif %} +You can generate a new {% data variables.product.pat_generic %} {% ifversion fpt or ghec %}using [{% data variables.product.product_name %} developer settings](https://github.com/settings/tokens/new){% endif %}{% ifversion ghes %} or with the "[Create a new authorization][/rest/reference/oauth-authorizations#create-a-new-authorization]" endpoint in the OAuth Authorizations API to generate a new OAuth token{% endif %}. For more information, see "[Creating a {% data variables.product.pat_generic %} for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". Then you would use these tokens to [authenticate using OAuth token][oauth-auth] with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.{% ifversion ghes %} The only time you need to authenticate with your username and password is when you create your OAuth token or use the OAuth Authorizations API.{% endif %} {% endif %} 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 0432d216c9..d0348eb3b4 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 @@ -362,7 +362,7 @@ If {% data variables.product.prodname_dotcom %} takes more than 10 seconds to pr ## Rate limiting -Different types of API requests to {% data variables.product.product_location %} are subject to different rate limits. +Different types of API requests to {% data variables.location.product_location %} are subject to different rate limits. Additionally, the Search API has dedicated limits. For more information, see "[Search](/rest/reference/search#rate-limit)" in the REST API documentation. @@ -372,7 +372,7 @@ Additionally, the Search API has dedicated limits. For more information, see "[S ### Requests from personal accounts -Direct API requests that you authenticate with a personal access token are user-to-server requests. An OAuth App or GitHub App can also make a user-to-server request on your behalf after you authorize the app. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)," "[Authorizing OAuth Apps](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)," and "[Authorizing GitHub Apps](/authentication/keeping-your-account-and-data-secure/authorizing-github-apps)." +Direct API requests that you authenticate with a {% data variables.product.pat_generic %} are user-to-server requests. An OAuth App or GitHub App can also make a user-to-server request on your behalf after you authorize the app. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)," "[Authorizing OAuth Apps](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)," and "[Authorizing GitHub Apps](/authentication/keeping-your-account-and-data-secure/authorizing-github-apps)." {% data variables.product.product_name %} associates all user-to-server requests with the authenticated user. For OAuth Apps and GitHub Apps, this is the user who authorized the app. All user-to-server requests count toward the authenticated user's rate limit. @@ -398,7 +398,7 @@ Requests from a GitHub App may be either user-to-server or server-to-server requ You can use the built-in `GITHUB_TOKEN` to authenticate requests in GitHub Actions workflows. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." -When using `GITHUB_TOKEN`, the rate limit is 1,000 requests per hour per repository.{% ifversion fpt or ghec %} For requests to resources that belong to an enterprise account on {% data variables.product.product_location %}, {% data variables.product.prodname_ghe_cloud %}'s rate limit applies, and the limit is 15,000 requests per hour per repository.{% endif %} +When using `GITHUB_TOKEN`, the rate limit is 1,000 requests per hour per repository.{% ifversion fpt or ghec %} For requests to resources that belong to an enterprise account on {% data variables.location.product_location %}, {% data variables.product.prodname_ghe_cloud %}'s rate limit applies, and the limit is 15,000 requests per hour per repository.{% endif %} ### Checking your rate limit status diff --git a/translations/pt-BR/content/rest/overview/troubleshooting.md b/translations/pt-BR/content/rest/overview/troubleshooting.md index 45a2ce3fae..bcb8e7f189 100644 --- a/translations/pt-BR/content/rest/overview/troubleshooting.md +++ b/translations/pt-BR/content/rest/overview/troubleshooting.md @@ -1,6 +1,6 @@ --- -title: Solução de problemas -intro: Aprenda a resolver os problemas mais comuns que as pessoas enfrentam na API REST. +title: Troubleshooting +intro: Learn how to resolve the most common problems people encounter in the REST API. redirect_from: - /v3/troubleshooting versions: @@ -10,57 +10,62 @@ versions: ghec: '*' topics: - API -ms.openlocfilehash: 0aa55fae9b33604b95e0eeee78e0712e60aaa5c7 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717674' --- -Se você estiver encontrando situações estranhas na API, veja uma lista de resoluções de alguns dos problemas que pode estar enfrentando. -## Erro `404` em um repositório existente -Normalmente, enviamos um erro `404` quando o cliente não está autenticado corretamente. -Você poderá esperar ver um erro `403 Forbidden` nesses casos. No entanto, como não queremos fornecer _nenhuma_ informação sobre os repositórios privados, a API retorna um erro `404`. -Para a solução de problemas, verifique se [você está se autenticando corretamente](/guides/getting-started/), se [o token de acesso OAuth tem os escopos necessários](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), se as [restrições de aplicativo de terceiros][oap-guide] não estão bloqueando o acesso e se [o token não expirou ou foi revogado](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation). +If you're encountering some oddities in the API, here's a list of resolutions to +some of the problems you may be experiencing. -## Nem todos os resultados retornados +## `404` error for an existing repository -A maioria das chamadas à API que acessa uma lista de recursos (_por exemplo_, usuários, problemas _etc._ ) dá suporte à paginação. Se você está fazendo solicitações e recebendo um conjunto incompleto de resultados, provavelmente, só está vendo a primeira página. Você precisará solicitar as páginas restantes para obter mais resultados. +Typically, we send a `404` error when your client isn't properly authenticated. +You might expect to see a `403 Forbidden` in these cases. However, since we don't +want to provide _any_ information about private repositories, the API returns a +`404` error instead. -É importante *não* tentar adivinhar o formato da URL de paginação. Nem todas as chamadas à API usam a mesma estrutura. Em vez disso, extraia as informações de paginação do [cabeçalho Link](/rest#pagination), que é enviado com cada solicitação. +To troubleshoot, ensure [you're authenticating correctly](/guides/getting-started/), [your OAuth access token has the required scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), [third-party application restrictions][oap-guide] are not blocking access, and that [the token has not expired or been revoked](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation). + +## Not all results returned + +Most API calls accessing a list of resources (_e.g._, users, issues, _etc._) support +pagination. If you're making requests and receiving an incomplete set of results, you're +probably only seeing the first page. You'll need to request the remaining pages +in order to get more results. + +It's important to *not* try and guess the format of the pagination URL. Not every +API call uses the same structure. Instead, extract the pagination information from +[the Link Header](/rest#pagination), which is sent with every request. [oap-guide]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ {% ifversion fpt or ghec %} -## Erros de autenticação básica +## Basic authentication errors -Em 13 de novembro de 2020 a autenticação de nome de usuário e senha da API REST e da API de Autorizações OAuth tornaram-se obsoletas e já não funcionaram mais. +On November 13, 2020 username and password authentication to the REST API and the OAuth Authorizations API were deprecated and no longer work. -### Como usar `username`/`password` para a autenticação básica +### Using `username`/`password` for basic authentication -Se você estiver usando `username` e `password` para as chamadas à API, elas não poderão mais ser autenticadas. Por exemplo: +If you're using `username` and `password` for API calls, then they are no longer able to authenticate. For example: ```bash curl -u my_user:my_password https://api.github.com/user/repos ``` -Em vez disso, use um [token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line) ao testar pontos de extremidade ou fazer o desenvolvimento local: +Instead, use a [{% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line) when testing endpoints or doing local development: ```bash curl -H 'Authorization: Bearer my_access_token' https://api.github.com/user/repos ``` -Para os Aplicativos OAuth, você deve usar o [fluxo do aplicativo Web](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) para gerar um token OAuth a ser usado no cabeçalho da chamada à API: +For OAuth Apps, you should use the [web application flow](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to generate an OAuth token to use in the API call's header: ```bash curl -H 'Authorization: Bearer my-oauth-token' https://api.github.com/user/repos ``` -## Tempos limite +## Timeouts -Se {% data variables.product.product_name %} demorar mais de 10 segundos para processar uma solicitação de API, {% data variables.product.product_name %} encerrará a solicitação e você receberá uma resposta de tempo esgotado. +If {% data variables.product.product_name %} takes more than 10 seconds to process an API request, {% data variables.product.product_name %} will terminate the request and you will receive a timeout response. {% endif %} diff --git a/translations/pt-BR/content/rest/packages.md b/translations/pt-BR/content/rest/packages.md index f71762e3b1..9388be2f7f 100644 --- a/translations/pt-BR/content/rest/packages.md +++ b/translations/pt-BR/content/rest/packages.md @@ -1,6 +1,6 @@ --- -title: Pacotes -intro: 'Com a API do {% data variables.product.prodname_registry %}, você pode gerenciar pacotes para seus repositórios e organizações de {% data variables.product.prodname_dotcom %}.' +title: Packages +intro: 'With the {% data variables.product.prodname_registry %} API, you can manage packages for your {% data variables.product.prodname_dotcom %} repositories and organizations.' versions: fpt: '*' ghec: '*' @@ -9,22 +9,17 @@ topics: miniTocMaxHeadingLevel: 3 redirect_from: - /rest/reference/packages -ms.openlocfilehash: 5edb7e30b296626a53fdc41806bcfba88718e6b3 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147059919' --- -## Sobre a API {% data variables.product.prodname_registry %} -A API de {% data variables.product.prodname_registry %} permite gerenciar pacotes usando a API REST. Para saber mais sobre como restaurar ou excluir pacotes, confira "[Restaurar e excluir pacotes](/packages/learn-github-packages/deleting-and-restoring-a-package)". +## About the {% data variables.product.prodname_registry %} API -Para usar essa API, você deve efetuar a autenticação usando um token de acesso pessoal. - - Para acessar metadados do pacote, o token precisa incluir o escopo `read:packages`. - - Para excluir pacotes e versões de pacote, o token precisa incluir os escopos `read:packages` e `delete:packages`. - - Para restaurar pacotes e versões de pacote, o token precisa incluir os escopos `read:packages` e `write:packages`. +The {% data variables.product.prodname_registry %} API enables you to manage packages using the REST API. To learn more about restoring or deleting packages, see "[Restoring and deleting packages](/packages/learn-github-packages/deleting-and-restoring-a-package)." -Se o `package_type` for `npm`, `maven`, `rubygems` ou `nuget`, o token também precisará incluir o escopo `repo`, pois o pacote herda permissões de um repositório do {% data variables.product.prodname_dotcom %}. Se o pacote estiver no {% data variables.product.prodname_container_registry %}, o `package_type` for `container` e o token não precisará do escopo `repo` para acessar ou gerenciar este `package_type`. pacotes de `container` oferecem permissões granulares separadas de um repositório. Para obter mais informações, confira "[Sobre as permissões para o {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)". +To use this API, you must authenticate using a {% data variables.product.pat_v1 %}. + - To access package metadata, your token must include the `read:packages` scope. + - To delete packages and package versions, your token must include the `read:packages` and `delete:packages` scopes. + - To restore packages and package versions, your token must include the `read:packages` and `write:packages` scopes. -Se você quiser usar a API de {% data variables.product.prodname_registry %} para acessar os recursos em uma organização com SSO habilitado, então você deve habilitar o SSO para o seu token de acesso pessoal. Para obter mais informações, confira "[Como autorizar um token de acesso pessoal para uso com o logon único do SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" na documentação do {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %} +If your `package_type` is `npm`, `maven`, `rubygems`, or `nuget`, then your token must also include the `repo` scope since your package inherits permissions from a {% data variables.product.prodname_dotcom %} repository. If your package is in the {% data variables.product.prodname_container_registry %}, then your `package_type` is `container` and your token does not need the `repo` scope to access or manage this `package_type`. `container` packages offer granular permissions separate from a repository. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)." + +If you want to use the {% data variables.product.prodname_registry %} API to access resources in an organization with SSO enabled, then you must enable SSO for your {% data variables.product.pat_v1 %}. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} diff --git a/translations/pt-BR/content/rest/projects/projects.md b/translations/pt-BR/content/rest/projects/projects.md index ecd967430c..1a6b0a537f 100644 --- a/translations/pt-BR/content/rest/projects/projects.md +++ b/translations/pt-BR/content/rest/projects/projects.md @@ -2,7 +2,7 @@ title: '{% data variables.product.prodname_projects_v1_caps %}' shortTitle: Boards allowTitleToDifferFromFilename: true -intro: 'A API de {% data variables.product.prodname_projects_v1 %} permite criar e gerenciar dados {% data variables.projects.projects_v1_boards %} em um repositório.' +intro: 'The {% data variables.product.prodname_projects_v1 %} API lets you create and manage {% data variables.projects.projects_v1_boards %} in a repository.' versions: fpt: '*' ghes: '*' @@ -11,11 +11,8 @@ versions: topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: f5c7d3e39f4de88bd071fecab159b08d540e5055 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147882356' --- + {% data reusables.projects.projects-api %} + +{% data reusables.user-settings.classic-projects-api-classic-pat-only %} diff --git a/translations/pt-BR/content/rest/scim.md b/translations/pt-BR/content/rest/scim.md index 5a46425655..cc680f5db1 100644 --- a/translations/pt-BR/content/rest/scim.md +++ b/translations/pt-BR/content/rest/scim.md @@ -1,6 +1,6 @@ --- title: SCIM -intro: Você pode controlar e gerenciar o acesso de membros da organização do GitHub usando a API SCIM. +intro: You can control and manage your GitHub organization members access using SCIM API. versions: ghec: '*' topics: @@ -8,50 +8,45 @@ topics: miniTocMaxHeadingLevel: 3 redirect_from: - /rest/reference/scim -ms.openlocfilehash: 314ed9433ffeb1ef3f189795727a3b654c529c96 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147883040' --- -## Sobre a API do SCIM -### Provisionamento de SCIM para Organizações +## About the SCIM API -A API do SCIM é usada pelos provedores de identidade (IdPs) habilitados pelo SCIM para automatizar o provisionamento de integrantes da organização de {% data variables.product.product_name %}. A API do {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} é baseada na versão 2.0 do [padrão SCIM](http://www.simplecloud.info/). O ponto de extremidade do SCIM do {% data variables.product.product_name %} que um IdP deve usar é: `{% data variables.product.api_url_code %}/scim/v2/organizations/{org}/`. +### SCIM Provisioning for Organizations + +The SCIM API is used by SCIM-enabled Identity Providers (IdPs) to automate provisioning of {% data variables.product.product_name %} organization membership. The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API is based on version 2.0 of the [SCIM standard](http://www.simplecloud.info/). The {% data variables.product.product_name %} SCIM endpoint that an IdP should use is: `{% data variables.product.api_url_code %}/scim/v2/organizations/{org}/`. {% note %} -**Observações:** - - A API do SCIM só está disponível para organizações individuais que usam [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) com o [SSO do SAML](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) habilitado. Para saber mais sobre o SCIM, confira"[Sobre o SCIM para organizações](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)". - - A API do SCIM não pode ser usada com uma conta corporativa ou com um {% data variables.product.prodname_emu_org %}. +**Notes:** + - The SCIM API is available only for individual organizations that use [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM for organizations](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)." + - The SCIM API cannot be used with an enterprise account or with an {% data variables.enterprise.prodname_emu_org %}. {% endnote %} -### Autenticar chamadas para a API de SCIM +### Authenticating calls to the SCIM API -Você deve efetuar a autenticação como dono de uma organização do {% data variables.product.product_name %} para usar sua API do SCIM. A API espera que um token [de portador OAuth 2.0](/developers/apps/authenticating-with-github-apps) seja incluído no cabeçalho `Authorization`. Você também pode usar um token de acesso pessoal, mas primeiro precisa [autorizá-lo para uso com sua organização de SSO do SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on). +You must authenticate as an owner of a {% data variables.product.product_name %} organization to use its SCIM API. The API expects an [OAuth 2.0 Bearer](/developers/apps/authenticating-with-github-apps) token to be included in the `Authorization` header. If you use a {% data variables.product.pat_v1 %} for authentication, it must have the `admin:org` scope and you must also [authorize it for use with your SAML SSO organization](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on). -### Mapear dados do SAML e SCIM +### Mapping of SAML and SCIM data {% data reusables.scim.nameid-and-username-must-match %} -### Atributos de usuário de SCIM compatíveis +### Supported SCIM User attributes -Nome | Tipo | Descrição +Name | Type | Description -----|------|-------------- -`userName`|`string` | O nome de usuário para o usuário. -`name.givenName`|`string` | Primeiro nome do usuário. -`name.familyName`|`string` | Sobrenome do usuário. -`emails` | `array` | Lista de e-mails dos usuários. -`externalId` | `string` | Este identificador é gerado pelo provedor do SAML e é usado como um ID exclusivo pelo provedor do SAML para corresponder ao usuário do GitHub. Você pode encontrar a `externalID` de um usuário no provedor SAML ou usando o ponto de extremidade [Listar identidades provisionadas do SCIM](#list-scim-provisioned-identities) e a filtragem de outros atributos conhecidos, como o nome de usuário do GitHub ou o endereço de email de um usuário. -`id` | `string` | Identificador gerado pelo ponto de extremidade do SCIM do GitHub. -`active` | `boolean` | Usado para indicar se a identidade está ativa (verdadeira) ou se deve ser desprovisionada (falso). +`userName`|`string` | The username for the user. +`name.givenName`|`string` | The first name of the user. +`name.familyName`|`string` | The last name of the user. +`emails` | `array` | List of user emails. +`externalId` | `string` | This identifier is generated by the SAML provider, and is used as a unique ID by the SAML provider to match against a GitHub user. You can find the `externalID` for a user either at the SAML provider, or using the [List SCIM provisioned identities](#list-scim-provisioned-identities) endpoint and filtering on other known attributes, such as a user's GitHub username or email address. +`id` | `string` | Identifier generated by the GitHub SCIM endpoint. +`active` | `boolean` | Used to indicate whether the identity is active (true) or should be deprovisioned (false). {% note %} -**Observação:** as URLs de ponto de extremidade da API do SCIM diferenciam maiúsculas de minúsculas. Por exemplo, a primeira letra no ponto de extremidade `Users` precisa ser maiúscula: +**Note:** Endpoint URLs for the SCIM API are case sensitive. For example, the first letter in the `Users` endpoint must be capitalized: ```shell GET /scim/v2/organizations/{org}/Users/{scim_user_id} diff --git a/translations/pt-BR/content/rest/teams/team-sync.md b/translations/pt-BR/content/rest/teams/team-sync.md index 407ef36a77..83a7cfda33 100644 --- a/translations/pt-BR/content/rest/teams/team-sync.md +++ b/translations/pt-BR/content/rest/teams/team-sync.md @@ -1,27 +1,22 @@ --- -title: Sincronização de equipe -intro: 'A API de Sincronização da Equipe permite que você gerencie as conexões entre equipes de {% data variables.product.product_name %} e grupos de provedor de identidade externo (IdP).' +title: Team synchronization +intro: 'The Team synchronization API allows you to manage connections between {% data variables.product.product_name %} teams and external identity provider (IdP) groups.' versions: ghec: '*' topics: - API miniTocMaxHeadingLevel: 3 allowTitleToDifferFromFilename: true -ms.openlocfilehash: 6a5d379b1050e10f9e31e14ed2b094a684676737 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147067159' --- -## Sobre a API de Sincronização de Equipe -Para usar esta API, o usuário autenticado deve ser um mantenedor de equipe ou um proprietário da organização associada à equipe. O token que você usa para efetuar a autenticação também deverá ser autorizado para uso com o provedor de IdP (SSO). Para obter mais informações, confira "[Como autorizar um token de acesso pessoal para uso com uma organização de logon único do SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)". +## About the Team synchronization API -Você pode gerenciar os integrantes da equipe do GitHub através do seu IdP com a sincronização de equipe. A sincronização de equipe deve estar habilitada para usar a API de sincronização de equipe. Para obter mais informações, confira "[Como sincronizar equipes entre o seu provedor de identidade e o GitHub](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)". +To use this API, the authenticated user must be a team maintainer or an owner of the organization associated with the team. The token you use to authenticate will also need to be authorized for use with your IdP (SSO) provider. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with a SAML single sign-on organization](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)." + +You can manage GitHub team members through your IdP with team synchronization. Team synchronization must be enabled to use the Team Synchronization API. For more information, see "[Synchronizing teams between your identity provider and GitHub](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)." {% note %} -**Observação:** a API de Sincronização da Equipe não pode ser usada com os {% data variables.product.prodname_emus %}. Para saber mais sobre como gerenciar uma {% data variables.product.prodname_emu_org %}, confira "[API de grupos externos](/enterprise-cloud@latest/rest/reference/teams#external-groups)". +**Note:** The Team Synchronization API cannot be used with {% data variables.product.prodname_emus %}. To learn more about managing an {% data variables.enterprise.prodname_emu_org %}, see "[External groups API](/enterprise-cloud@latest/rest/reference/teams#external-groups)". {% endnote %} diff --git a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md index f891379c3e..503c7cbd7a 100644 --- a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md +++ b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md @@ -1,6 +1,6 @@ --- -title: Sobre a pesquisa no GitHub -intro: 'Use nossas potentes ferramentas de pesquisa para encontrar o que está procurando entre os muitos repositórios, usuários e linhas de código no {% data variables.product.product_name %}.' +title: About searching on GitHub +intro: 'Our integrated search covers the many repositories, users, and lines of code on {% data variables.product.product_name %}.' redirect_from: - /articles/using-the-command-bar - /articles/github-search-basics @@ -17,76 +17,70 @@ versions: ghec: '*' topics: - GitHub search -ms.openlocfilehash: 875bb9876a36ce7f202d31749771dc147f348524 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146179372' --- {% data reusables.search.you-can-search-globally %} -- Para pesquisar globalmente em todo o {% data variables.product.product_name %}, digite o que está procurando no campo de pesquisa que fica na parte superior de qualquer página e escolha "All {% data variables.product.prodname_dotcom %}" (Em todo o GitHub) no menu suspenso da pesquisa. -- Para pesquisar em uma organização ou um repositório específico, navegue até a página da organização ou do repositório, digite o que está procurando no campo de pesquisa que fica na parte superior da página e pressione **Enter**. +- To search globally across all of {% data variables.product.product_name %}, type what you're looking for into the search field at the top of any page, and choose "All {% data variables.product.prodname_dotcom %}" in the search drop-down menu. +- To search within a particular repository or organization, navigate to the repository or organization page, type what you're looking for into the search field at the top of the page, and press **Enter**. {% note %} -**Observações:** +**Notes:** {% ifversion fpt or ghes or ghec %} - {% data reusables.search.required_login %}{% endif %} -- Os sites do {% data variables.product.prodname_pages %} não são pesquisáveis no {% data variables.product.product_name %}. No entanto, você pode pesquisar o conteúdo da fonte, se ele existir no branch padrão de um repositório, usando a pesquisa de código. Para obter mais informações, confira "[Pesquisa de código](/search-github/searching-on-github/searching-code)". Para obter mais informações sobre {% data variables.product.prodname_pages %}, confira "[O que é o GitHub Pages?](/articles/what-is-github-pages/)" -- Atualmente, a nossa pesquisa não é compatível com correspondência exata. -- Sempre que você estiver pesquisando em arquivos de código, serão retornados apenas os dois primeiros resultados de cada arquivo. +- {% data variables.product.prodname_pages %} sites are not searchable on {% data variables.product.product_name %}. However you can search the source content if it exists in the default branch of a repository, using code search. For more information, see "[Searching code](/search-github/searching-on-github/searching-code)." For more information about {% data variables.product.prodname_pages %}, see "[What is GitHub Pages?](/articles/what-is-github-pages/)" +- Currently our search doesn't support exact matching. +- Whenever you are searching in code files, only the first two results in each file will be returned. {% endnote %} -Após a realização de uma pesquisa no {% data variables.product.product_name %}, é possível ordenar os resultados ou refiná-los ainda mais clicando em uma das linguagens na barra lateral. Para obter mais informações, confira "[Classificar os resultados da pesquisa](/search-github/getting-started-with-searching-on-github/sorting-search-results)". +After running a search on {% data variables.product.product_name %}, you can sort the results, or further refine them by clicking one of the languages in the sidebar. For more information, see "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results)." -A pesquisa do {% data variables.product.product_name %} usa um cluster do ElasticSearch para indexar projetos toda vez que uma alteração é enviada por push ao {% data variables.product.product_name %}. Problemas e pull requests são indexados quando são criados ou modificados. +{% data variables.product.product_name %} search uses an ElasticSearch cluster to index projects every time a change is pushed to {% data variables.product.product_name %}. Issues and pull requests are indexed when they are created or modified. -## Tipos de pesquisa no {% data variables.product.prodname_dotcom %} +## Types of searches on {% data variables.product.prodname_dotcom %} -Você pode pesquisar as seguintes informações em todos os repositórios que você pode acessar em {% data variables.product.product_location %}. +You can search for the following information across all repositories you can access on {% data variables.location.product_location %}. -- [Repositórios](/search-github/searching-on-github/searching-for-repositories) -- [Tópicos](/search-github/searching-on-github/searching-topics) -- [Problemas e solicitações de pull](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt or ghec %} -- [Discussões](/search-github/searching-on-github/searching-discussions){% endif %} -- [Código](/search-github/searching-on-github/searching-code) -- [Confirmações](/search-github/searching-on-github/searching-commits) -- [Usuários](/search-github/searching-on-github/searching-users) -- [Pacotes](/search-github/searching-on-github/searching-for-packages) +- [Repositories](/search-github/searching-on-github/searching-for-repositories) +- [Topics](/search-github/searching-on-github/searching-topics) +- [Issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt or ghec %} +- [Discussions](/search-github/searching-on-github/searching-discussions){% endif %} +- [Code](/search-github/searching-on-github/searching-code) +- [Commits](/search-github/searching-on-github/searching-commits) +- [Users](/search-github/searching-on-github/searching-users) +- [Packages](/search-github/searching-on-github/searching-for-packages) - [Wikis](/search-github/searching-on-github/searching-wikis) -## Pesquisar usando uma interface visual +## Searching using a visual interface -Você pode pesquisar {% data variables.product.product_name %} usando o {% data variables.search.search_page_url %} ou {% data variables.search.advanced_url %}. {% ifversion command-palette %}Como alternativa, você pode usar a pesquisa interativa no {% data variables.product.prodname_command_palette %} para pesquisar sua localização atual na interface do usuário, um usuário, um repositório ou uma organização específica e globalmente em todo o {% data variables.product.product_name %}, usando o teclado. Para obter mais informações, confira "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)".{% endif %} +You can search {% data variables.product.product_name %} using the {% data variables.search.search_page_url %} or {% data variables.search.advanced_url %}. {% ifversion command-palette %}Alternatively, you can use the interactive search in the {% data variables.product.prodname_command_palette %} to search your current location in the UI, a specific user, repository or organization, and globally across all of {% data variables.product.product_name %}, without leaving the keyboard. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %} -A {% data variables.search.advanced_url %} fornece uma interface visual para construção de consultas de pesquisa. Você pode filtrar as pesquisas por diversos fatores, como o número de estrelas ou o número de bifurcações que um repositório tem. À medida que você preenche os campos de pesquisa avançada, sua consulta é automaticamente construída na barra de pesquisa superior. +The {% data variables.search.advanced_url %} provides a visual interface for constructing search queries. You can filter your searches by a variety of factors, such as the number of stars or number of forks a repository has. As you fill in the advanced search fields, your query will automatically be constructed in the top search bar. -![Pesquisa avançada](/assets/images/help/search/advanced_search_demo.gif) +![Advanced Search](/assets/images/help/search/advanced_search_demo.gif) -## Pesquisando repositórios em {% data variables.product.prodname_dotcom_the_website %} a partir do seu ambiente corporativo privado +## Searching repositories on {% data variables.product.prodname_dotcom_the_website %} from your private enterprise environment {% ifversion fpt or ghec %} -Se você usar {% data variables.product.prodname_dotcom_the_website %} e {% data variables.product.prodname_ghe_server %} ou {% data variables.product.prodname_ghe_managed %}, e um proprietário de empresa tiver ativado {% data variables.product.prodname_unified_search %}, você poderá pesquisar em ambos os ambientes ao mesmo tempo em {% data variables.product.prodname_ghe_server %} ou {% data variables.product.prodname_ghe_managed %}. Para obter mais informações, confira [a documentação {% data variables.product.prodname_ghe_server %} documentation](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment) ou [the {% data variables.product.prodname_ghe_managed %}](/github-ae@latest/search-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment). +If you use both {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %}, and an enterprise owner has enabled {% data variables.enterprise.prodname_unified_search %}, you can search across both environments at the same time from {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %}. For more information, see [the {% data variables.product.prodname_ghe_server %} documentation](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment) or [the {% data variables.product.prodname_ghe_managed %} documentation](/github-ae@latest/search-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment). {% else %} -Se você usar {% data variables.product.prodname_dotcom_the_website %} e {% data variables.product.product_name %}, e um proprietário de empresa tiver ativado {% data variables.product.prodname_unified_search %}, você poderá pesquisar em ambos os ambientes ao mesmo tempo de {% data variables.product.product_name %}. Para obter mais informações sobre como os proprietários de empresas podem habilitar {% data variables.product.prodname_unified_search %}, confira "[Habilitar {% data variables.product.prodname_unified_search %} para sua empresa](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)", +If you use both {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.product_name %}, and an enterprise owner has enabled {% data variables.enterprise.prodname_unified_search %}, you can search across both environments at the same time from {% data variables.product.product_name %}. For more information about how enterprise owners can enable {% data variables.enterprise.prodname_unified_search %}, see "[Enabling {% data variables.enterprise.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)." -O proprietário da empresa em {% data variables.product.product_name %} pode habilitar separadamente {% data variables.product.prodname_unified_search %} para todos os repositórios públicos em {% data variables.product.prodname_dotcom_the_website %} e para repositórios privados de propriedade da organização ou empresa em {% data variables.product.prodname_dotcom_the_website %} que está conectada a {% data variables.product.product_name %} por meio de {% data variables.product.prodname_github_connect %}. +Your enterprise owner on {% data variables.product.product_name %} can separately enable {% data variables.enterprise.prodname_unified_search %} for all public repositories on {% data variables.product.prodname_dotcom_the_website %} and for private repositories owned by the organization or enterprise on {% data variables.product.prodname_dotcom_the_website %} that is connected to {% data variables.product.product_name %} through {% data variables.product.prodname_github_connect %}. -Antes de poder usar {% data variables.product.prodname_unified_search %} para repositórios privados, você deve conectar suas contas pessoais em {% data variables.product.prodname_dotcom_the_website %} e {% data variables.product.product_name %}. Para obter mais informações, confira "[Como habilitar a pesquisa de repositório {% data variables.product.prodname_dotcom_the_website %} em seu ambiente de empresa privada](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)". +Before you can use {% data variables.enterprise.prodname_unified_search %} for private repositories, you must connect your personal accounts on {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.product_name %}. For more information, see "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." -Ao pesquisar em {% data variables.product.product_name %}, apenas os repositórios privados aos quais você tem acesso e que são de propriedade da organização ou conta corporativa conectada serão incluídos nos resultados da pesquisa. Nem você nem ninguém poderá pesquisar repositórios privados pertencentes à sua conta pessoal em {% data variables.product.prodname_dotcom_the_website %} de {% data variables.product.product_name %}. +When you search from {% data variables.product.product_name %}, only private repositories that you have access to and that are owned by the connected organization or enterprise account will be included in search results. Neither you nor anyone else will be able to search private repositories owned by your personal account on {% data variables.product.prodname_dotcom_the_website %} from {% data variables.product.product_name %}. -Para limitar sua pesquisa a um ambiente, você pode usar uma opção de filtro em {% data variables.search.advanced_url %} ou pode usar o prefixo de pesquisa `environment:`. Para pesquisar apenas conteúdo em {% data variables.product.product_name %}, use a sintaxe de pesquisa `environment:local`. Para pesquisar apenas conteúdo em {% data variables.product.prodname_dotcom_the_website %}, use `environment:github`. +To limit your search to one environment, you can use a filter option on the {% data variables.search.advanced_url %} or you can use the `environment:` search prefix. To only search for content on {% data variables.product.product_name %}, use the search syntax `environment:local`. To only search for content on {% data variables.product.prodname_dotcom_the_website %}, use `environment:github`. {% endif %} -## Leitura adicional +## Further reading -- "[Como entender a sintaxe de pesquisa](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)" -- "[Pesquisar no GitHub](/articles/searching-on-github)" +- "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)" +- "[Searching on GitHub](/articles/searching-on-github)" diff --git a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md index 59e7bb83f9..2c6c969728 100644 --- a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md +++ b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md @@ -1,7 +1,7 @@ --- -title: Habilitar a pesquisa de repositório GitHub.com no ambiente privado da sua empresa +title: Enabling GitHub.com repository search from your private enterprise environment shortTitle: Search GitHub.com from enterprise -intro: 'Você pode conectar suas contas pessoais no {% data variables.product.prodname_dotcom_the_website %} e o ambiente privado do {% data variables.product.prodname_enterprise %} para procurar conteúdo em alguns repositórios do {% data variables.product.prodname_dotcom_the_website %} {% ifversion fpt or ghec %} do ambiente privado{% else %} do {% data variables.product.product_name %}{% endif %}.' +intro: 'You can connect your personal accounts on {% data variables.product.prodname_dotcom_the_website %} and your private {% data variables.product.prodname_enterprise %} environment to search for content in certain {% data variables.product.prodname_dotcom_the_website %} repositories{% ifversion fpt or ghec %} from your private environment{% else %} from {% data variables.product.product_name %}{% endif %}.' redirect_from: - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-account - /articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account @@ -14,23 +14,20 @@ versions: ghae: '*' topics: - GitHub search -ms.openlocfilehash: 2c4ee57036ca2d0114e75a1acaeecec05be5ba3a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147062455' --- -## Sobre a pesquisa de repositórios de {% data variables.product.prodname_dotcom_the_website %} de {% data variables.product.product_name %} -Você pode pesquisar repositórios privados designados em {% data variables.product.prodname_ghe_cloud %} de {% data variables.product.product_location %}{% ifversion ghae %} em {% data variables.product.prodname_ghe_managed %}{% endif %}. Para obter mais informações sobre a pesquisa em ambientes, confira "[Sobre a pesquisa em GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)". +## About search for {% data variables.product.prodname_dotcom_the_website %} repositories from {% data variables.product.product_name %} -## Pré-requisitos +You can search for designated private repositories on {% data variables.product.prodname_ghe_cloud %} from {% data variables.location.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}. For more information about searching across environments, see "[About searching on GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)." -Um proprietário da empresa para {% data variables.product.product_name %} deve habilitar {% data variables.product.prodname_github_connect %} e {% data variables.product.prodname_unified_search %} para repositórios privados. Para obter mais informações, confira "[Como habilitar o {% data variables.product.prodname_unified_search %} para sua empresa](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)". +## Prerequisites -## Habilitando a pesquisa de repositório do {% data variables.product.prodname_dotcom_the_website %} de {% data variables.product.product_name %} +An enterprise owner for {% data variables.product.product_name %} must enable {% data variables.product.prodname_github_connect %} and {% data variables.enterprise.prodname_unified_search %} for private repositories. For more information, see "[Enabling {% data variables.enterprise.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)." -1. Efetue o login em {% data variables.product.product_name %} e {% data variables.product.prodname_dotcom_the_website %}. -1. No canto superior direito de qualquer página do {% data variables.product.product_name %}, clique na foto do seu perfil e clique em **Configurações**. -![Ícone Configurações na barra de usuário](/assets/images/help/settings/userbar-account-settings.png) {% data reusables.github-connect.github-connect-tab-user-settings %} {% data reusables.github-connect.connect-dotcom-and-enterprise %} +## Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from {% data variables.product.product_name %} + +1. Sign into {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}. +1. On {% data variables.product.product_name %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. +![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md b/translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md index da046ef4d0..69c5aeed59 100644 --- a/translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md @@ -1,6 +1,6 @@ --- -title: Pesquisar repositórios -intro: 'Você pode pesquisar repositórios no {% data variables.product.product_name %} e limitar os resultados usando qualquer combinação dos qualificadores de pesquisa de repositórios.' +title: Searching for repositories +intro: 'You can search for repositories on {% data variables.product.product_name %} and narrow the results using these repository search qualifiers in any combination.' redirect_from: - /articles/searching-repositories - /articles/searching-for-repositories @@ -14,195 +14,193 @@ versions: topics: - GitHub search shortTitle: Search for repositories -ms.openlocfilehash: 9a464fbb327809b8af970c9a62c3a70d81c2c6b9 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147527931' --- -Pesquise repositórios globalmente em toda a {% data variables.product.product_location %} ou pesquise repositórios em uma organização específica. Para obter mais informações, confira "[Sobre a pesquisa no {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". +You can search for repositories globally across all of {% data variables.location.product_location %}, or search for repositories within a particular organization. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." -Para incluir forks nos resultados da pesquisa, adicione `fork:true` ou `fork:only` à consulta. Para obter mais informações, confira "[Pesquisa em forks](/search-github/searching-on-github/searching-in-forks)". +To include forks in the search results, you will need to add `fork:true` or `fork:only` to your query. For more information, see "[Searching in forks](/search-github/searching-on-github/searching-in-forks)." {% data reusables.search.syntax_tips %} -## Pesquisar por nome do repositório, descrição ou conteúdo do arquivo README +## Search by repository name, description, or contents of the README file -Com o qualificador `in`, você pode restringir a pesquisa ao nome do repositório, à descrição do repositório, ao conteúdo do arquivo README ou a qualquer combinação desses itens. Quando você omite esse qualificador, somente o nome, a descrição e os tópicos do repositório são pesquisados. +With the `in` qualifier you can restrict your search to the repository name, repository description, repository topics, contents of the README file, or any combination of these. When you omit this qualifier, only the repository name, description, and topics are searched. -| Qualificador | Exemplo +| Qualifier | Example | ------------- | ------------- -| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) corresponde aos repositórios com "jquery" no nome. -| `in:description` | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) corresponde aos repositórios com "jquery" no nome ou na descrição. -| `in:topics` | [**jquery in:topics**](https://github.com/search?q=jquery+in%3Atopics&type=Repositories) corresponde a repositórios rotulados com "jquery" como um tópico. -| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) corresponde aos repositórios que mencionam "jquery" no arquivo README do repositório. -| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) corresponde a um nome de repositório específico. +| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) matches repositories with "jquery" in the repository name. +| `in:description` | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) matches repositories with "jquery" in the repository name or description. +| `in:topics` | [**jquery in:topics**](https://github.com/search?q=jquery+in%3Atopics&type=Repositories) matches repositories labeled with "jquery" as a topic. +| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) matches repositories mentioning "jquery" in the repository's README file. +| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) matches a specific repository name. -## Pesquisar com base no conteúdo do repositório +## Search based on the contents of a repository -Encontre um repositório pesquisando o conteúdo no arquivo README do repositório usando o qualificador `in:readme`. Para obter mais informações, confira "[Sobre os arquivos README](/github/creating-cloning-and-archiving-repositories/about-readmes)". +You can find a repository by searching for content in the repository's README file using the `in:readme` qualifier. For more information, see "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)." -Além de usar o `in:readme`, não é possível encontrar repositórios pesquisando um conteúdo específico no repositório. Para pesquisar um arquivo ou conteúdo específico em um repositório, você pode usar o localizador de arquivos os qualificadores de pesquisa específicos para código. Para obter mais informações, confira "[Como encontrar arquivos no {% data variables.product.prodname_dotcom %}](/search-github/searching-on-github/finding-files-on-github)" e "[Como pesquisar um código](/search-github/searching-on-github/searching-code)". +Besides using `in:readme`, it's not possible to find repositories by searching for specific content within the repository. To search for a specific file or content within a repository, you can use the file finder or code-specific search qualifiers. For more information, see "[Finding files on {% data variables.product.prodname_dotcom %}](/search-github/searching-on-github/finding-files-on-github)" and "[Searching code](/search-github/searching-on-github/searching-code)." -| Qualificador | Exemplo +| Qualifier | Example | ------------- | ------------- -| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) corresponde aos repositórios que mencionam "octocat" no arquivo README do repositório. +| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) matches repositories mentioning "octocat" in the repository's README file. -## Pesquisar nos repositórios de um usuário ou uma organização +## Search within a user's or organization's repositories -Para fazer uma pesquisa em todos os repositórios pertencentes a uma organização ou a um usuário específico, use o qualificador `user` ou `org`. +To search in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. -| Qualificador | Exemplo +| Qualifier | Example | ------------- | ------------- -| user:USERNAME | [**user:defunkt forks:>100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) corresponde aos repositórios de @defunkt que têm mais de 100 forks. -| org:ORGNAME | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) corresponde aos repositórios do GitHub. +| user:USERNAME | [**user:defunkt forks:>100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) matches repositories from @defunkt that have more than 100 forks. +| org:ORGNAME | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) matches repositories from GitHub. -## Pesquisar por tamanho do repositório +## Search by repository size -O qualificador `size` encontra os repositórios que correspondem a um tamanho específico (em kilobytes) usando os qualificadores maior que, menor que e intervalo. Para obter mais informações, confira "[Noções básicas sobre a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)". +The `size` qualifier finds repositories that match a certain size (in kilobytes), using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." -| Qualificador | Exemplo +| Qualifier | Example | ------------- | ------------- -| size:n | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) corresponde aos repositórios que têm exatamente 1 MB. -| | [**size:>=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) corresponde aos repositórios que têm, pelo menos, 30 MB. -| | [**size:<50**](https://github.com/search?q=size%3A%3C50&type=Repositories) corresponde aos repositórios menores que 50 KB. -| | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) corresponde aos repositórios que têm entre 50 KB e 120 KB. +| size:n | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) matches repositories that are 1 MB exactly. +| | [**size:>=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) matches repositories that are at least 30 MB. +| | [**size:<50**](https://github.com/search?q=size%3A%3C50&type=Repositories) matches repositories that are smaller than 50 KB. +| | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) matches repositories that are between 50 KB and 120 KB. -## Pesquisar por número de seguidores +## Search by number of followers -Filtre os repositórios com base no número de usuários que seguem os repositórios usando o qualificador `followers` com os qualificadores maior que, menor que e intervalo. Para obter mais informações, confira "[Noções básicas sobre a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)". +You can filter repositories based on the number of users who follow the repositories, using the `followers` qualifier with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." -| Qualificador | Exemplo +| Qualifier | Example | ------------- | ------------- -| followers:n | [**node followers:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) corresponde aos repositórios com dez mil ou mais seguidores que mencionam a palavra "node". -| | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) corresponde aos repositórios que têm entre um e dez seguidores que mencionam o termo "styleguide linter". +| followers:n | [**node followers:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) matches repositories with 10,000 or more followers mentioning the word "node". +| | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) matches repositories with between 1 and 10 followers, mentioning the word "styleguide linter." -## Pesquisar por número de bifurcações +## Search by number of forks -O qualificador `forks` especifica o número de forks que um repositório deve ter usando os qualificadores maior que, menor que e intervalo. Para obter mais informações, confira "[Noções básicas sobre a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)". +The `forks` qualifier specifies the number of forks a repository should have, using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." -| Qualificador | Exemplo +| Qualifier | Example | ------------- | ------------- -| forks:n | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) corresponde aos repositórios com apenas cinco forks. -| | [**forks:>=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) corresponde aos repositórios com, pelo menos, 205 forks. -| | [**forks:<90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) corresponde aos repositórios com menos de 90 forks. -| | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) corresponde aos repositórios com 10 a 20 forks. +| forks:n | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) matches repositories with only five forks. +| | [**forks:>=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) matches repositories with at least 205 forks. +| | [**forks:<90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) matches repositories with fewer than 90 forks. +| | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) matches repositories with 10 to 20 forks. -## Pesquisar por número de estrelas +## Search by number of stars -Você pode pesquisar repositórios com base no número de estrelas que os repositórios têm, usando os qualificadores maior que, menor que e intervalo. Para obter mais informações, confira "[Como salvar repositórios com estrelas](/github/getting-started-with-github/saving-repositories-with-stars)" e "[Noções básicas sobre a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)". +You can search repositories based on the number of stars the repositories have, using greater than, less than, and range qualifiers. For more information, see "[Saving repositories with stars](/github/getting-started-with-github/saving-repositories-with-stars)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." -| Qualificador | Exemplo +| Qualifier | Example | ------------- | ------------- -| stars:n | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) corresponde aos repositórios com exatamente 500 estrelas. -| | [**stars:10..20 size:<1000**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) corresponde aos repositórios com 1000 a 10 estrelas, com menos de 20 KB. -| | [**stars:>=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) corresponde aos repositórios com, pelo menos, 500 estrelas, incluindo aqueles com forks, escritos em PHP. +| stars:n | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) matches repositories with exactly 500 stars. +| | [**stars:10..20 size:<1000**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) matches repositories 10 to 20 stars, that are smaller than 1000 KB. +| | [**stars:>=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) matches repositories with the at least 500 stars, including forked ones, that are written in PHP. -## Pesquisar por data da criação ou da última atualização do repositório +## Search by when a repository was created or last updated -Você pode filtrar repositórios com base na data de criação ou da última atualização. Para a criação do repositório, você pode usar o qualificador `created`. Para descobrir quando um repositório foi atualizado pela última vez, o ideal é usar o qualificador `pushed`. O qualificador `pushed` retorna uma lista de repositórios, classificados pelo commit mais recente feito em qualquer branch do repositório. +You can filter repositories based on time of creation or time of last update. For repository creation, you can use the `created` qualifier; to find out when a repository was last updated, you'll want to use the `pushed` qualifier. The `pushed` qualifier will return a list of repositories, sorted by the most recent commit made on any branch in the repository. -Os dois usam uma data como parâmetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} +Both take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} {% data reusables.search.date_gt_lt %} -| Qualificador | Exemplo +| Qualifier | Example | ------------- | ------------- -| created:YYYY-MM-DD | [**webos created:<2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) corresponde aos repositórios com a palavra "webos" que foram criados antes de 2011. -| pushed:YYYY-MM-DD | [**css pushed:>2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) corresponde aos repositórios com a palavra "css" que foram enviados por push após janeiro de 2013. -| | [**case pushed:>=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) corresponde aos repositórios com a palavra "case" que foram enviados por push em 6 de março de 2013 ou após essa data e que são forks. +| created:YYYY-MM-DD | [**webos created:<2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) matches repositories with the word "webos" that were created before 2011. +| pushed:YYYY-MM-DD | [**css pushed:>2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) matches repositories with the word "css" that were pushed to after January 2013. +| | [**case pushed:>=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) matches repositories with the word "case" that were pushed to on or after March 6th, 2013, and that are forks. -## Pesquisar por linguagem +## Search by language -Você pode pesquisar repositórios com base na linguagem do código nos repositórios. +You can search repositories based on the language of the code in the repositories. -| Qualificador | Exemplo +| Qualifier | Example | ------------- | ------------- -| language:LANGUAGE | [ **`rails language:javascript`**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) corresponde aos repositórios com a palavra "rails" que foram escritos em JavaScript. +| language:LANGUAGE | [**`rails language:javascript`**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) matches repositories with the word "rails" that are written in JavaScript. -## Pesquisar por tópico +## Search by topic -Você pode encontrar todos os repositórios classificados com um determinado tópico. Para obter mais informações, confira "[Como classificar seu repositório com tópicos](/github/administering-a-repository/classifying-your-repository-with-topics)". +You can find all of the repositories that are classified with a particular topic. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)." -| Qualificador | Exemplo +| Qualifier | Example | ------------- | ------------- -| topic:TOPIC | [ **`topic:jekyll`**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) corresponde aos repositórios que foram classificados com o tópico "Jekyll". +| topic:TOPIC | [**`topic:jekyll`**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) matches repositories that have been classified with the topic "Jekyll." -## Pesquisar por número de tópicos +## Search by number of topics -Você pode pesquisar repositórios pelo número de tópicos que foram aplicados a eles usando o qualificador `topics` com os qualificadores maior que, menor que e intervalo. Para obter mais informações, confira "[Como classificar seu repositório com tópicos](/github/administering-a-repository/classifying-your-repository-with-topics)" e "[Noções básicas sobre a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)". +You can search repositories by the number of topics that have been applied to the repositories, using the `topics` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." -| Qualificador | Exemplo +| Qualifier | Example | ------------- | ------------- -| topics:n | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) corresponde aos repositórios que têm cinco tópicos. -| | [**topics:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) corresponde aos repositórios que têm mais de três tópicos. +| topics:n | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) matches repositories that have five topics. +| | [**topics:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) matches repositories that have more than three topics. {% ifversion fpt or ghes or ghec %} -## Pesquisar por licença +## Search by license -Você pode pesquisar repositórios pelo tipo de licença nos repositórios. É preciso usar uma palavra-chave de licença para filtrar repositórios por uma determinada licença ou família de licenças. Para obter mais informações, confira "[Como licenciar um repositório](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)". +You can search repositories by the type of license in the repositories. You must use a license keyword to filter repositories by a particular license or license family. For more information, see "[Licensing a repository](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)." -| Qualificador | Exemplo +| Qualifier | Example | ------------- | ------------- -| license:LICENSE_KEYWORD | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) corresponde aos repositórios licenciados sob a Licença Apache 2.0. +| license:LICENSE_KEYWORD | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) matches repositories that are licensed under Apache License 2.0. {% endif %} -## Pesquisar por visibilidade do repositório +## Search by repository visibility -Você pode filtrar sua pesquisa com base na visibilidade dos repositórios. Para obter mais informações, confira "[Sobre os repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". +You can filter your search based on the visibility of the repositories. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." -| Qualificador | Exemplo | ------------- | ------------- | {% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) corresponde aos repositórios públicos pertencentes ao {% data variables.product.company_short %}.{% endif %}{% ifversion ghes or ghec or ghae %} | `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) corresponde aos repositórios internos que você pode acessar e contém a palavra "test".{% endif %} | `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) corresponde aos repositórios privados que você pode acessar e contém a palavra "pages". +| Qualifier | Example +| ------------- | ------------- |{% ifversion fpt or ghes or ghec %} +| `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) matches public repositories owned by {% data variables.product.company_short %}.{% endif %}{% ifversion ghes or ghec or ghae %} +| `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) matches internal repositories that you can access and contain the word "test".{% endif %} +| `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) matches private repositories that you can access and contain the word "pages." {% ifversion fpt or ghec %} -## Pesquisar com base no fato de o repositório ser um espelho +## Search based on whether a repository is a mirror -Você pode pesquisar repositórios com base no fato de os repositórios serem espelhos e hospedados em outro lugar. Para obter mais informações, confira "[Como encontrar maneiras de contribuir com o código aberto no {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)". +You can search repositories based on whether the repositories are mirrors and hosted elsewhere. For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)." -| Qualificador | Exemplo +| Qualifier | Example | ------------- | ------------- -| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) corresponde aos repositórios que são espelhos e que contêm a palavra "GNOME". -| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) corresponde aos repositórios que não são espelhos e que contêm a palavra "GNOME". +| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) matches repositories that are mirrors and contain the word "GNOME." +| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) matches repositories that are not mirrors and contain the word "GNOME." {% endif %} -## Pesquisar com base no fato de o repositório estar arquivado +## Search based on whether a repository is archived -Você pode pesquisar repositórios com base no fato de os repositórios estarem ou não arquivados. Para obter mais informações, confira "[Como arquivar repositórios](/repositories/archiving-a-github-repository/archiving-repositories)". +You can search repositories based on whether or not the repositories are archived. For more information, see "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)." -| Qualificador | Exemplo +| Qualifier | Example | ------------- | ------------- -| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) corresponde aos repositórios arquivados e que contêm a palavra "GNOME". -| `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) corresponde aos repositórios que não foram arquivados e que contêm a palavra "GNOME". +| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) matches repositories that are archived and contain the word "GNOME." +| `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) matches repositories that are not archived and contain the word "GNOME." {% ifversion fpt or ghec %} -## Pesquisa com base no número de problemas com os rótulos `good first issue` ou `help wanted` +## Search based on number of issues with `good first issue` or `help wanted` labels -Você pode pesquisar repositórios que tenham um número mínimo de problemas rotulados `help-wanted` ou `good-first-issue` com os qualificadores `help-wanted-issues:>n` e `good-first-issues:>n`. Para obter mais informações, confira "[Como incentivar contribuições úteis para seu projeto com rótulos](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)". +You can search for repositories that have a minimum number of issues labeled `help-wanted` or `good-first-issue` with the qualifiers `help-wanted-issues:>n` and `good-first-issues:>n`. For more information, see "[Encouraging helpful contributions to your project with labels](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)." -| Qualificador | Exemplo +| Qualifier | Example | ------------- | ------------- -| `good-first-issues:>n` | [ **`good-first-issues:>2 javascript`**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) corresponde aos repositórios com mais de dois problemas rotulados `good-first-issue` e que contêm a palavra "javascript". -| `help-wanted-issues:>n`|[**help-wanted-issues:>4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) corresponde aos repositórios com mais de quatro problemas rotulados `help-wanted` e que contêm a palavra "React". +| `good-first-issues:>n` | [**`good-first-issues:>2 javascript`**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) matches repositories with more than two issues labeled `good-first-issue` and that contain the word "javascript." +| `help-wanted-issues:>n`|[**help-wanted-issues:>4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) matches repositories with more than four issues labeled `help-wanted` and that contain the word "React." -## Pesquisar com base na capacidade de patrocinador +## Search based on ability to sponsor -Você pode pesquisar repositórios cujos proprietários podem ser patrocinados no {% data variables.product.prodname_sponsors %} com o qualificador `is:sponsorable`. Para obter mais informações, confira "[Sobre o {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)". +You can search for repositories whose owners can be sponsored on {% data variables.product.prodname_sponsors %} with the `is:sponsorable` qualifier. For more information, see "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." -Você pode pesquisar repositórios que têm um arquivo de financiamento usando o qualificador `has:funding-file`. Para obter mais informações, confira "[Sobre os arquivos FUNDING](/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository#about-funding-files)". +You can search for repositories that have a funding file using the `has:funding-file` qualifier. For more information, see "[About FUNDING files](/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository#about-funding-files)." -| Qualificador | Exemplo +| Qualifier | Example | ------------- | ------------- -| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Repositories) corresponde aos repositórios cujos proprietários têm um perfil do {% data variables.product.prodname_sponsors %}. -| `has:funding-file` | [**has:funding-file**](https://github.com/search?q=has%3Afunding-file&type=Repositories) corresponde aos repositórios que têm um arquivo FUNDING.yml. +| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Repositories) matches repositories whose owners have a {% data variables.product.prodname_sponsors %} profile. +| `has:funding-file` | [**has:funding-file**](https://github.com/search?q=has%3Afunding-file&type=Repositories) matches repositories that have a FUNDING.yml file. {% endif %} -## Leitura adicional +## Further reading -- "[Como classificar os resultados da pesquisa](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" -- "[Como fazer pesquisas em forks](/search-github/searching-on-github/searching-in-forks)" +- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" +- "[Searching in forks](/search-github/searching-on-github/searching-in-forks)" diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md index 4e6d036ae3..0054f0a88c 100644 --- a/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md @@ -20,7 +20,7 @@ You can search for issues and pull requests globally across all of {% data varia {% tip %} **Tips:**{% ifversion ghes or ghae %} - - This article contains example searches on the {% data variables.product.prodname_dotcom %}.com website, but you can use the same search filters on {% data variables.product.product_location %}.{% endif %} + - This article contains example searches on the {% data variables.product.prodname_dotcom %}.com website, but you can use the same search filters on {% data variables.location.product_location %}.{% endif %} - For a list of search syntaxes that you can add to any search qualifier to further improve your results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)". - Use quotations around multi-word search terms. For example, if you want to search for issues with the label "In progress," you'd search for `label:"in progress"`. Search is not case sensitive. - {% data reusables.search.search_issues_and_pull_requests_shortcut %} diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md index 7fff95c1c3..b96b7c361a 100644 --- a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md +++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md @@ -83,7 +83,7 @@ If you choose to receive payouts to a bank account, your bank account can be a d ## Enabling two-factor authentication (2FA) on your {% data variables.product.prodname_dotcom %} account -Before your organization can become a sponsored organization, you must enable 2FA for your account on {% data variables.product.product_location %}. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)." +Before your organization can become a sponsored organization, you must enable 2FA for your account on {% data variables.location.product_location %}. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)." ## Submitting your application to {% data variables.product.prodname_dotcom %} for approval diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md index a5929f0a51..77f5cb9377 100644 --- a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md +++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md @@ -1,6 +1,6 @@ --- title: Setting up GitHub Sponsors for your personal account -intro: 'You can become a sponsored developer by joining {% data variables.product.prodname_sponsors %}, completing your sponsored developer profile, creating sponsorship tiers, submitting your bank and tax information, and enabling two-factor authentication for your account on {% data variables.product.product_location %}.' +intro: 'You can become a sponsored developer by joining {% data variables.product.prodname_sponsors %}, completing your sponsored developer profile, creating sponsorship tiers, submitting your bank and tax information, and enabling two-factor authentication for your account on {% data variables.location.product_location %}.' redirect_from: - /articles/becoming-a-sponsored-developer - /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer @@ -84,7 +84,7 @@ If you choose to receive payouts to a bank account, your region of residence and ## Enabling two-factor authentication (2FA) on your {% data variables.product.prodname_dotcom %} account -Before you can become a sponsored developer, you must enable 2FA for your account on {% data variables.product.product_location %}. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)." +Before you can become a sponsored developer, you must enable 2FA for your account on {% data variables.location.product_location %}. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)." ## Submitting your application to {% data variables.product.prodname_dotcom %} for approval diff --git a/translations/pt-BR/content/support/contacting-github-support/providing-data-to-github-support.md b/translations/pt-BR/content/support/contacting-github-support/providing-data-to-github-support.md index 2e298d86c8..c2460886cc 100644 --- a/translations/pt-BR/content/support/contacting-github-support/providing-data-to-github-support.md +++ b/translations/pt-BR/content/support/contacting-github-support/providing-data-to-github-support.md @@ -1,6 +1,6 @@ --- -title: Fornecer dados para o GitHub Support -intro: 'Uma vez que {% data variables.contact.github_support %} não tem acesso ao seu ambiente, às vezes exigimos alguma informação adicional sobre você.' +title: Providing data to GitHub Support +intro: 'Since {% data variables.contact.github_support %} doesn''t have access to your environment, we sometimes require some additional information from you.' shortTitle: Providing data versions: ghes: '*' @@ -13,22 +13,17 @@ redirect_from: - /admin/enterprise-support/receiving-help-from-github-support/providing-data-to-github-support topics: - Support -ms.openlocfilehash: 56a90a9449a92577d08e068095e5b0dc5b443bb2 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: '146331909' --- -## Sobre os arquivos de diagnóstico e pacotes de suporte -{% data variables.contact.github_support %} pode solicitar que você forneça dados adicionais na forma de arquivos de registro excluídos. Existem três tipos de arquivo de registro que podem ser solicitados que você forneça. +## About diagnostic files and support bundles -Os arquivos de diagnóstico contêm informações sobre as configurações e o ambiente de uma instância de {% data variables.product.prodname_ghe_server %}, os pacotes de suporte contêm diagnósticos e registros dos últimos dois dias, e pacotes de suporte estendidos também contêm diagnósticos e registros, mas dos últimos sete dias. +{% data variables.contact.github_support %} may ask you to provide additional data in the form of sanitized log files. There are three types of log file you may be asked to provide. -## Sobre o arquivo de registro sanitização +Diagnostic files contain information about a {% data variables.product.prodname_ghe_server %} instance's settings and environment, support bundles contain diagnostics and logs from the past two days, and extended support bundles also contain diagnostics and logs but from the past seven days. -Os tokens de autenticação, chaves e segredos são removidos dos arquivos de registro nos seguintes diretórios de registro contidos em um pacote de suporte ou arquivo de diagnóstico: +## About log file sanitization + +Authentication tokens, keys, and secrets are removed from log files in the following log directories contained within a support bundle or diagnostics file: * `alambic-logs` * `babeld-logs` @@ -44,136 +39,146 @@ Os tokens de autenticação, chaves e segredos são removidos dos arquivos de re * `render-logs` * `svn-bridge-logs` -## Criar e compartilhar arquivos de diagnóstico +## Creating and sharing diagnostic files -Os arquivos de diagnóstico são uma visão geral das configurações e do ambiente de uma instância de {% data variables.product.prodname_ghe_server %} que contém: +Diagnostic files are an overview of a {% data variables.product.prodname_ghe_server %} instance's settings and environment that contains: -- Informações da licença do cliente, incluindo o nome da empresa, data de validade e número de licenças de usuário -- Números de versão e SHAs; -- Arquitetura de VMs; -- Nome de host, modo privado, configurações de SSL; -- Listagens de carga e processo; -- Configurações de rede -- Método e detalhes de autenticação; -- Número de repositórios, usuários e outros dados de instalação. +- Client license information, including company name, expiration date, and number of user licenses +- Version numbers and SHAs +- VM architecture +- Host name, private mode, SSL settings +- Load and process listings +- Network settings +- Authentication method and details +- Number of repositories, users, and other installation data -Baixe o diagnóstico para sua instância do {% data variables.enterprise.management_console %} ou executando o utilitário de linha de comando `ghe-diagnostics`. +You can download the diagnostics for your instance from the {% data variables.enterprise.management_console %} or by running the `ghe-diagnostics` command-line utility. -### Criar um arquivo de diagnóstico no {% data variables.enterprise.management_console %} +### Creating a diagnostic file from the {% data variables.enterprise.management_console %} -Você pode usar esse método se não tiver sua chave SSH disponível no momento. +You can use this method if you don't have your SSH key readily available. -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.type-management-console-password %} {% data reusables.enterprise_management_console.support-link %} -5. Clique em **Baixar informações de diagnóstico**. +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.type-management-console-password %} +{% data reusables.enterprise_management_console.support-link %} +5. Click **Download diagnostics info**. -### Criar um arquivo de diagnóstico usando SSH +### Creating a diagnostic file using SSH -Você pode usar esse método sem entrar no {% data variables.enterprise.management_console %}. +You can use this method without signing into the {% data variables.enterprise.management_console %}. -Use o utilitário de linha de comando [ghe-diagnostics](/enterprise/admin/guides/installation/command-line-utilities#ghe-diagnostics) para recuperar o diagnóstico para sua instância. +Use the [ghe-diagnostics](/enterprise/admin/guides/installation/command-line-utilities#ghe-diagnostics) command-line utility to retrieve the diagnostics for your instance. ```shell -$ ssh -p122 admin@hostname -- 'ghe-diagnostics' > diagnostics.txt +$ ssh -p122 admin@HOSTNAME -- 'ghe-diagnostics' > diagnostics.txt ``` -## Criar e compartilhar pacotes de suporte +## Creating and sharing support bundles -Depois do envio da sua solicitação de suporte, podemos pedir que você compartilhe um pacote de suporte com a nossa equipe. O pacote de suporte é um arquivo tar compactado com gzip que inclui diagnósticos e logs importantes da sua instância, como: +After you submit your support request, we may ask you to share a support bundle with our team. The support bundle is a gzip-compressed tar archive that includes diagnostics and important logs from your instance, such as: -- Logs relacionados à autenticação que podem ser úteis na solução de problemas de erros de autenticação, ou na configuração de LDAP, CAS ou SAML; -- Log do {% data variables.enterprise.management_console %}; -- `github-logs/exceptions.log`: informações sobre os erros 500 encontrados no site -- `github-logs/audit.log`: logs de auditoria do {% data variables.product.prodname_ghe_server %} -- `babeld-logs/babeld.log`: logs de proxy do Git -- `system-logs/haproxy.log`: logs do HAProxy -- `elasticsearch-logs/github-enterprise.log`: logs do Elasticsearch -- `configuration-logs/ghe-config.log`: logs de configuração do {% data variables.product.prodname_ghe_server %} -- `collectd/logs/collectd.log`: logs do Collectd -- `mail-logs/mail.log`: logs de entrega de email SMTP +- Authentication-related logs that may be helpful when troubleshooting authentication errors, or configuring LDAP, CAS, or SAML +- {% data variables.enterprise.management_console %} log +- `github-logs/exceptions.log`: Information about 500 errors encountered on the site +- `github-logs/audit.log`: {% data variables.product.prodname_ghe_server %} audit logs +- `babeld-logs/babeld.log`: Git proxy logs +- `system-logs/haproxy.log`: HAProxy logs +- `elasticsearch-logs/github-enterprise.log`: Elasticsearch logs +- `configuration-logs/ghe-config.log`: {% data variables.product.prodname_ghe_server %} configuration logs +- `collectd/logs/collectd.log`: Collectd logs +- `mail-logs/mail.log`: SMTP email delivery logs -Para obter mais informações, confira "[Sobre o log de auditoria para sua empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)". +For more information, see "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)." -Os pacotes de suporte incluem logs dos últimos dois dias. Para obter logs dos últimos sete dias, você pode baixar um pacote de suporte estendido. Para obter mais informações, confira "[Como criar e compartilhar pacotes de suporte estendido](#creating-and-sharing-extended-support-bundles)". +Support bundles include logs from the past two days. To get logs from the past seven days, you can download an extended support bundle. For more information, see "[Creating and sharing extended support bundles](#creating-and-sharing-extended-support-bundles)." {% tip %} -**Dica:** ao entrar em contato com o {% data variables.contact.github_support %}, você receberá um email de confirmação que conterá um link de referência do tíquete. Se o {% data variables.contact.github_support %} solicitar o upload de um pacote de suporte, você pode usar o link de referência do tíquete para fazer o upload requisitado. +**Tip:** When you contact {% data variables.contact.github_support %}, you'll be sent a confirmation email that will contain a ticket reference link. If {% data variables.contact.github_support %} asks you to upload a support bundle, you can use the ticket reference link to upload the support bundle. {% endtip %} -### Criar um pacote de suporte no {% data variables.enterprise.management_console %} +### Creating a support bundle from the {% data variables.enterprise.management_console %} -Você pode usar essas etapas para criar e compartilhar um pacote de suporte se conseguir acessar o {% data variables.enterprise.management_console %} e se tiver acesso à internet. +You can use these steps to create and share a support bundle if you can access the web-based {% data variables.enterprise.management_console %} and have outbound internet access. -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.type-management-console-password %} {% data reusables.enterprise_management_console.support-link %} -5. Clique em **Baixar pacote de suporte**. -{% data reusables.enterprise_enterprise_support.sign-in-to-support %} {% data reusables.enterprise_enterprise_support.upload-support-bundle %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.type-management-console-password %} +{% data reusables.enterprise_management_console.support-link %} +5. Click **Download support bundle**. +{% data reusables.enterprise_enterprise_support.sign-in-to-support %} +{% data reusables.enterprise_enterprise_support.upload-support-bundle %} -### Criar um pacote de suporte usando SSH +### Creating a support bundle using SSH -Você pode usar esses passos para criar e compartilhar um pacote de suporte se você tiver acesso de SSH ao {% data variables.product.product_location %} e tiver acesso à internet de saída. +You can use these steps to create and share a support bundle if you have SSH access to {% data variables.location.product_location %} and have outbound internet access. {% data reusables.enterprise_enterprise_support.use_ghe_cluster_support_bundle %} -1. Baixe o pacote de suporte via SSH: +1. Download the support bundle via SSH: ```shell - $ ssh -p 122 admin@hostname -- 'ghe-support-bundle -o' > support-bundle.tgz + $ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -o' > support-bundle.tgz ``` - Para obter mais informações sobre o comando `ghe-support-bundle`, confira "[Utilitários de linha de comando](/enterprise/admin/guides/installation/command-line-utilities#ghe-support-bundle)". -{% data reusables.enterprise_enterprise_support.sign-in-to-support %} {% data reusables.enterprise_enterprise_support.upload-support-bundle %} + For more information about the `ghe-support-bundle` command, see "[Command-line utilities](/enterprise/admin/guides/installation/command-line-utilities#ghe-support-bundle)". +{% data reusables.enterprise_enterprise_support.sign-in-to-support %} +{% data reusables.enterprise_enterprise_support.upload-support-bundle %} -### Carregar um pacote de suporte usando sua conta corporativa +### Uploading a support bundle using your enterprise account -{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} -3. Na barra lateral esquerda, clique em **Licenciamento da empresa**. - ![Captura de tela que mostra o link "Licenciamento da empresa" na barra lateral das configurações da conta corporativa.](/assets/images/help/enterprises/enterprise-licensing-tab.png) -4. Em "Ajuda do {% data variables.product.prodname_enterprise %}", clique em **Carregar um pacote de suporte**. - ![Captura de tela que mostra "Carregar um link de pacote de suporte".](/assets/images/enterprise/support/upload-support-bundle.png) -5. Em "Selecione uma conta corporativa", selecione a conta associada ao pacote de suporte no menu suspenso. - ![Captura de tela que mostra o menu suspenso usado para selecionar a conta corporativa do pacote de suporte.](/assets/images/enterprise/support/support-bundle-account.png) -6. Em "Carregar um pacote de suporte para o {% data variables.contact.enterprise_support %}", para selecionar o pacote de suporte, clique em **Escolher arquivo** ou arraste o arquivo de pacote de suporte para **Escolher arquivo**. - ![Captura de tela que mostra o botão "Escolher arquivo" para carregar um arquivo de pacote de suporte.](/assets/images/enterprise/support/choose-support-bundle-file.png) -7. Clique em **Carregar**. +{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} +{% data reusables.enterprise-accounts.settings-tab %} +3. In the left sidebar, click **Enterprise licensing**. + ![Screenshot showing "Enterprise licensing" link in the enterprise account settings sidebar.](/assets/images/help/enterprises/enterprise-licensing-tab.png) +4. Under "{% data variables.product.prodname_enterprise %} Help", click **Upload a support bundle**. + ![Screenshot showing "Upload a support bundle link".](/assets/images/enterprise/support/upload-support-bundle.png) +5. Under "Select an enterprise account", select the support bundle's associated account from the drop-down menu. + ![Screenshot showing the dropdown menu to select the support bundle's enterprise account.](/assets/images/enterprise/support/support-bundle-account.png) +6. Under "Upload a support bundle for {% data variables.contact.enterprise_support %}", to select your support bundle, click **Choose file**, or drag your support bundle file onto **Choose file**. + ![Screenshot showing the "Choose file" button to upload a support bundle file.](/assets/images/enterprise/support/choose-support-bundle-file.png) +7. Click **Upload**. -### Fazer upload de um pacote de suporte usando SSH +### Uploading a support bundle directly using SSH -Você pode fazer upload diretamente de um pacote de suporte para o nosso servidor nas seguintes situações: -- Você tem acesso de SSH a {% data variables.product.product_location %}. -- As conexões HTTPS de saída na porta TCP 443 são permitidas por meio do {% data variables.product.product_location %} para _enterprise-bundles.github.com_ e _esbtoolsproduction.blob.core.windows.net_. +You can directly upload a support bundle to our server if: +- You have SSH access to {% data variables.location.product_location %}. +- Outbound HTTPS connections over TCP port 443 are allowed from {% data variables.location.product_location %} to _enterprise-bundles.github.com_ and _esbtoolsproduction.blob.core.windows.net_. -1. Faça upload do pacote para o nosso servidor de pacotes de suporte: +1. Upload the bundle to our support bundle server: ```shell - $ ssh -p122 admin@hostname -- 'ghe-support-bundle -u' + $ ssh -p122 admin@HOSTNAME -- 'ghe-support-bundle -u' ``` -## Criar e compartilhar pacotes de suporte estendidos +## Creating and sharing extended support bundles -Os pacotes de suporte incluem os logs dos últimos dois dias, enquanto os pacotes de suporte _estendidos_ incluem os logs dos últimos sete dias. Se os eventos que o {% data variables.contact.github_support %} está investigando tiverem ocorrido há mais de dois dias, poderemos solicitar que você compartilhe um pacote de suporte estendido. Você precisará do acesso SSH para baixar um pacote estendido, e não é possível fazer o download de um pacote estendido no {% data variables.enterprise.management_console %}. +Support bundles include logs from the past two days, while _extended_ support bundles include logs from the past seven days. If the events that {% data variables.contact.github_support %} is investigating occurred more than two days ago, we may ask you to share an extended support bundle. You will need SSH access to download an extended bundle - you cannot download an extended bundle from the {% data variables.enterprise.management_console %}. -Para evitar que fiquem grandes demais, os pacotes só têm logs que não passaram por rotação nem compactação. A rotação de arquivos de registro no {% data variables.product.prodname_ghe_server %} acontece em várias frequências (diária ou semanalmente) para diferentes arquivos, dependendo das expectativas de tamanho dos registros. +To prevent bundles from becoming too large, bundles only contain logs that haven't been rotated and compressed. Log rotation on {% data variables.product.prodname_ghe_server %} happens at various frequencies (daily or weekly) for different log files, depending on how large we expect the logs to be. -### Criar um pacote de suporte estendido usando SSH +### Creating an extended support bundle using SSH -Você pode usar essas etapas para criar e compartilhar um pacote de suporte estendido se você tiver acesso de SSH ao {% data variables.product.product_location %} e tiver acesso à internet de saída. +You can use these steps to create and share an extended support bundle if you have SSH access to {% data variables.location.product_location %} and you have outbound internet access. -1. Baixe o pacote de suporte estendido por meio do SSH adicionando o sinalizador `-x` ao comando `ghe-support-bundle`: +1. Download the extended support bundle via SSH by adding the `-x` flag to the `ghe-support-bundle` command: ```shell - $ ssh -p 122 admin@hostname -- 'ghe-support-bundle -o -x' > support-bundle.tgz + $ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -o -x' > support-bundle.tgz ``` -{% data reusables.enterprise_enterprise_support.sign-in-to-support %} {% data reusables.enterprise_enterprise_support.upload-support-bundle %} +{% data reusables.enterprise_enterprise_support.sign-in-to-support %} +{% data reusables.enterprise_enterprise_support.upload-support-bundle %} -### Fazer upload de um pacote de suporte estendido usando SSH +### Uploading an extended support bundle directly using SSH -Você pode fazer upload diretamente de um pacote de suporte para o nosso servidor nas seguintes situações: -- Você tem acesso de SSH a {% data variables.product.product_location %}. -- As conexões HTTPS de saída na porta TCP 443 são permitidas por meio do {% data variables.product.product_location %} para _enterprise-bundles.github.com_ e _esbtoolsproduction.blob.core.windows.net_. +You can directly upload a support bundle to our server if: +- You have SSH access to {% data variables.location.product_location %}. +- Outbound HTTPS connections over TCP port 443 are allowed from {% data variables.location.product_location %} to _enterprise-bundles.github.com_ and _esbtoolsproduction.blob.core.windows.net_. -1. Faça upload do pacote para o nosso servidor de pacotes de suporte: +1. Upload the bundle to our support bundle server: ```shell - $ ssh -p122 admin@hostname -- 'ghe-support-bundle -u -x' + $ ssh -p122 admin@HOSTNAME -- 'ghe-support-bundle -u -x' ``` -## Leitura adicional +## Further reading -- "[Sobre o Suporte do GitHub](/support/learning-about-github-support/about-github-support)" -- "[Como gerar uma verificação de integridade para sua empresa](/enterprise-server@latest/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise)" +- "[About GitHub Support](/support/learning-about-github-support/about-github-support)" +- "[Generating a Health Check for your enterprise](/enterprise-server@latest/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise)" diff --git a/translations/pt-BR/content/support/learning-about-github-support/about-github-premium-support.md b/translations/pt-BR/content/support/learning-about-github-support/about-github-premium-support.md index 8a2285436a..6e5bd60a19 100644 --- a/translations/pt-BR/content/support/learning-about-github-support/about-github-premium-support.md +++ b/translations/pt-BR/content/support/learning-about-github-support/about-github-premium-support.md @@ -1,6 +1,6 @@ --- -title: Sobre suporte premium do GitHub -intro: 'O {% data variables.contact.premium_support %} é uma opção de suporte complementar pago oferecida aos clientes do {% data variables.product.prodname_enterprise %}.' +title: About GitHub Premium Support +intro: '{% data variables.contact.premium_support %} is a paid, supplemental support offering for {% data variables.product.prodname_enterprise %} customers.' shortTitle: GitHub Premium Support versions: ghec: '*' @@ -20,130 +20,125 @@ redirect_from: - /support/about-github-support/about-github-premium-support topics: - Support -ms.openlocfilehash: 23504e6554b6dc1dbe0f239d2b73006e588711f9 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147052301' --- + {% note %} -**Observações:** +**Notes:** -- Os termos do {% data variables.contact.premium_support %} estão sujeitos a alteração sem aviso prévio e entram em vigor a partir de novembro de 2021. +- The terms of {% data variables.contact.premium_support %} are subject to change without notice and are effective as of November 2021. - {% data reusables.support.data-protection-and-privacy %} {% endnote %} -## Sobre o {% data variables.contact.premium_support %} +## About {% data variables.contact.premium_support %} {% data reusables.support.premium-support-features %} -## Planos do {% data variables.contact.premium_support %} +## {% data variables.contact.premium_support %} plans -Há dois {% data variables.contact.premium_support %} planos: Premium e Premium Plus / {% data variables.product.microsoft_premium_plus_support_plan %}. +There are two {% data variables.contact.premium_support %} plans: Premium and Premium Plus / {% data variables.product.microsoft_premium_plus_support_plan %}. | | {% data variables.product.premium_support_plan %} | {% data variables.product.premium_plus_support_plan %} | |---|---|------| -| Horário de funcionamento | 24 horas, 7 dias por semana | 24 horas, 7 dias por semana | -| Tempo inicial de resposta |
  • 30 minutos para {% data variables.product.support_ticket_priority_urgent %}
  • 4 hours para {% data variables.product.support_ticket_priority_high %}
|
  • 30 minutos para {% data variables.product.support_ticket_priority_urgent %}
  • 4 hours para {% data variables.product.support_ticket_priority_high %}
| -| Canais de suporte |
  • Envio do tíquete on-line
  • Suporte por telefone em inglês via solicitação de retorno de chamada
  • Solicitação de compartilhamento de tela para problemas críticos
|
  • Envio do tíquete on-line
  • Suporte por telefone em inglês via solicitação de retorno de chamada
  • Solicitação de compartilhamento de tela para problemas críticos
| -| Treinamento | Acesso a conteúdo premium |
  • Acesso a conteúdo premium
  • 1 aula de treinamento virtual por ano
| -| Membros com direito a suporte | 20 | 20 | -| Recursos | Processamento de tíquete com prioridade |
  • Processamento de tíquete com prioridade
  • Engenheiro de Responsabilidade do Cliente Nomeado
| -| Verificações de Integridade | Relatórios de Verificação de Integridade automatizados ilimitados (confira "[Gerar uma Verificação de Integridade para sua empresa]({% ifversion not ghes%}/enterprise-server@latest{% endif %}/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise)") |
  • Relatórios de Verificação de Integridade automatizados ilimitados (confira "[Gerar uma Verificação de Integridade para sua empresa]({% ifversion not ghes%}/enterprise-server@latest{% endif %}/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise)")
  • Verificações de Integridade aprimoradas trimestralmente, com descobertas, interpretações e recomendações de um Engenheiro de Confiabilidade do Cliente (por solicitação)
| -| Horas de consultoria técnica| Nenhum | 4 horas por mês | -| Assistência de atualização do aplicativo | Nenhum | Por solicitação | -| Planejamento de nuvem | Nenhum | Por solicitação | +| Hours of operation | 24 x 7 | 24 x 7 | +| Initial response time |
  • 30 minutes for {% data variables.product.support_ticket_priority_urgent %}
  • 4 hours for {% data variables.product.support_ticket_priority_high %}
|
  • 30 minutes for {% data variables.product.support_ticket_priority_urgent %}
  • 4 hours for {% data variables.product.support_ticket_priority_high %}
| +| Support channels |
  • Online ticket submission
  • Phone support in English via callback request
  • Screen share request for critical issues
|
  • Online ticket submission
  • Phone support in English via callback request
  • Screen share request for critical issues
| +| Training | Access to premium content |
  • Access to premium content
  • 1 virtual training class per year
| +| Members with support entitlements | 20 | 20 | +| Resources | Priority ticket handling |
  • Priority ticket handling
  • Named Customer Reliability Engineer
| +| Health Checks | Unlimited automated Health Check reports (see "[Generating a Health Check for your enterprise]({% ifversion not ghes%}/enterprise-server@latest{% endif %}/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise)") |
  • Unlimited automated Health Check reports (see "[Generating a Health Check for your enterprise]({% ifversion not ghes%}/enterprise-server@latest{% endif %}/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise)")
  • Quarterly enhanced Health Checks, with findings, interpretations, and recommendations from a Customer Reliability Engineer (by request)
| +| Technical advisory hours| None | 4 hours per month | +| Application upgrade assistance | None | By request | +| Cloud planning | None | By request | {% note %} - **Observações:** - - Os proprietários das empresas e os gerentes de cobrança têm automaticamente direito a suporte. Os proprietários das empresas podem adicionar direitos de suporte aos integrantes de organizações pertencentes à sua conta corporativa. Para obter mais informações, confira "[Como gerenciar os direitos de suporte para sua empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)". - - Para o {% data variables.product.premium_plus_support_plan %}, 50% dos serviços gerenciados não utilizados vão para o próximo mês e expiram no final do trimestre. + **Notes:** + - Enterprise owners and billing managers automatically have a support entitlement. Enterprise owners can add support entitlements to members of organizations owned by their enterprise account. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)." + - For the {% data variables.product.premium_plus_support_plan %}, 50% of unused Managed Services hours roll over to the next month and expire at the end of the quarter. {% endnote %} -## Inscrever-se para o {% data variables.contact.premium_support %} +## Signing up for {% data variables.contact.premium_support %} -Para se inscrever no {% data variables.contact.premium_support %} ou atualizar seu plano, [entre em contato com nossa equipe de gerenciamento de contas](https://enterprise.github.com/contact) ou ligue para [+1 (877) 448-4820](tel:+1-877-448-4820). +To sign up for {% data variables.contact.premium_support %} or upgrade your plan, you can [contact our account management team](https://enterprise.github.com/contact) or call [+1 (877) 448-4820](tel:+1-877-448-4820). -## Escopo do suporte +## Scope of support {% data reusables.support.scope-of-support %} -## Entrar em contato com o {% data variables.contact.premium_support %} +## Contacting {% data variables.contact.premium_support %} -Os clientes do {% data variables.contact.premium_support %} podem usar o {% data variables.contact.contact_landing_page_portal %} para relatar problemas por escrito, em inglês. +{% data variables.contact.premium_support %} customers can use the {% data variables.contact.contact_landing_page_portal %} to report issues in writing, in English. -## Horário de funcionamento +## Hours of operation -O {% data variables.contact.premium_support %} está disponível 24 horas por dia, 7 dias por semana. Se a sua compra do {% data variables.contact.premium_support %} foi feita antes de 17 de setembro de 2018, o suporte é limitado nos feriados. Para obter mais informações sobre os feriados observados pelo {% data variables.contact.premium_support %}, confira o cronograma de feriados em "[Sobre o {% data variables.contact.github_support %}](/enterprise-server@latest/admin/enterprise-support/overview/about-github-enterprise-support)". +{% data variables.contact.premium_support %} is available 24 hours a day, 7 days per week. If you purchased {% data variables.contact.premium_support %} prior to September 17, 2018, support is limited during holidays. For more information on holidays {% data variables.contact.premium_support %} observes, see the holiday schedule at "[About {% data variables.contact.github_support %}](/enterprise-server@latest/admin/enterprise-support/overview/about-github-enterprise-support)." -## Tempos de resposta do Contrato de nível de serviço +## Service Level Agreement response times -Para tíquetes que você enviar, o suporte está disponível 24 horas por dia, 7 dias por semana. O tempo inicial de resposta garantido pelo SLA depende do nível de prioridade do tíquete. Tempo de resposta começa quando {% data variables.contact.premium_support %} define o nível de prioridade do tíquete. Uma resposta não significa que o problema tenha sido resolvido. +For tickets you submit, support is available 24 hours a day, 7 days per week. The initial response time guaranteed by the SLA is dependent on the priority level of the ticket. Response time begins when {% data variables.contact.premium_support %} sets the priority level of the ticket. A response does not mean the issue has been resolved. -| Nível de prioridade do tíquete | Tempo inicial de resposta | +| Ticket priority level | Initial response time | | --- | ---| -| {% data variables.product.support_ticket_priority_urgent %} | 30 minutos | -| {% data variables.product.support_ticket_priority_high %} | 4 horas | +| {% data variables.product.support_ticket_priority_urgent %} | 30 minutes | +| {% data variables.product.support_ticket_priority_high %} | 4 hours | {% data reusables.enterprise_enterprise_support.installing-releases %} -Você deve instalar a versão mínima compatível do {% data variables.product.prodname_ghe_server %} conforme a seção Versões compatíveis do seu contrato de licença em até 90 dias após o pedido do {% data variables.contact.premium_support %}. +You must install the minimum supported version of {% data variables.product.prodname_ghe_server %} pursuant to the Supported Releases section of your applicable license agreement within 90 days of placing an order for {% data variables.contact.premium_support %}. -## Atribuindo uma prioridade a um tíquete de suporte +## Assigning a priority to a support ticket -Ao entrar em contato com {% data variables.contact.premium_support %}, você pode escolher uma das quatro prioridades para o tíquete: {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %} ou {% data variables.product.support_ticket_priority_low %}. +When you contact {% data variables.contact.premium_support %}, you can choose one of four priorities for the ticket: {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, or {% data variables.product.support_ticket_priority_low %}. -- [Prioridades de tíquetes do {% data variables.product.prodname_ghe_cloud %}](#ticket-priorities-for-github-enterprise-cloud) -- [Prioridades de tíquetes do {% data variables.product.prodname_ghe_server %}](#ticket-priorities-for-github-enterprise-server) +- [Ticket priorities for {% data variables.product.prodname_ghe_cloud %}](#ticket-priorities-for-github-enterprise-cloud) +- [Ticket priorities for {% data variables.product.prodname_ghe_server %}](#ticket-priorities-for-github-enterprise-server) -### Prioridades de tíquetes para {% data variables.product.prodname_ghe_cloud %} +### Ticket priorities for {% data variables.product.prodname_ghe_cloud %} -| Prioridade | Descrição | Exemplos | +| Priority | Description | Examples | | :---: | --- | --- | -| {% data variables.product.support_ticket_priority_urgent %} | Os fluxos de trabalho de produção para sua organização ou empresa em {% data variables.product.prodname_ghe_cloud %} estão falhando em razão de erros de serviço ou falhas críticas e a falha afeta diretamente a operação do seu negócio. |
  • Erros ou interrupções em {% data variables.product.prodname_dotcom_the_website %} afetam a funcionalidade essencial do Git ou do aplicativo web para todos os integrantes da sua organização ou empresa
| -| {% data variables.product.support_ticket_priority_high %} | Os problemas de conta ou segurança com sua organização ou empresa em {% data variables.product.prodname_ghe_cloud %} causam impacto limitado à sua empresa. |
  • Uma organização ou proprietário da empresa excluiu involuntariamente uma organização
  • Uma organização ou integrante da empresa fez o upload de dados confidenciais em um commit, problema, pull request ou anexo do problema
| -| {% data variables.product.support_ticket_priority_normal %} | Os integrantes da sua organização ou empresa em {% data variables.product.prodname_ghe_cloud %} estão passando por problemas limitados ou moderados com {% data variables.product.prodname_dotcom_the_website %}, ou você tem dúvidas ou preocupações gerais sobre sua organização ou empresa. |
  • Perguntas sobre o uso de APIs e recursos para sua organização ou empresa
  • Problemas com ferramentas para migração de dados da organização que {% data variables.product.company_short %} fornece
  • Recursos relacionados à sua organização ou empresa não funcionando como esperado
  • Dúvidas gerais de segurança sobre sua organização ou empresa
| -| {% data variables.product.support_ticket_priority_low %} | Você tem uma pergunta ou sugestão sobre sua organização ou empresa em {% data variables.product.prodname_ghe_cloud %} que não seja sensível ao tempo, ou não bloqueie a produtividade da sua equipe. |
  • Uso excessivo de recursos para a sua organização ou empresa
  • Pedidos de verificações de integridade
  • Ajuda com o uso de Gists, notificações, wikis, {% data variables.product.prodname_pages %}, {% data variables.product.prodname_desktop %}, Atom ou outros serviços ou recursos periféricos com sua organização ou empresa
  • Solicitações de recursos
  • Comentários sobre o produto
| +| {% data variables.product.support_ticket_priority_urgent %} | Production workflows for your organization or enterprise on {% data variables.product.prodname_ghe_cloud %} are failing due to critical service errors or outages, and the failure directly impacts the operation of your business. |
  • Errors or outages on {% data variables.product.prodname_dotcom_the_website %} affect core Git or web application functionality for all members of your organization or enterprise
| +| {% data variables.product.support_ticket_priority_high %} | Account or security issues with your organization or enterprise on {% data variables.product.prodname_ghe_cloud %} are causing limited impact to your business. |
  • An organization or enterprise owner has unintentionally deleted an organization
  • An organization or enterprise member has uploaded sensitive data in a commit, issue, pull request, or issue attachment
| +| {% data variables.product.support_ticket_priority_normal %} | Members of your organization or enterprise on {% data variables.product.prodname_ghe_cloud %} are experiencing limited or moderate issues with {% data variables.product.prodname_dotcom_the_website %}, or you have general concerns or questions about your organization or enterprise. |
  • Questions about using APIs and features for your organization or enterprise
  • Issues with tools for organization data migration that {% data variables.product.company_short %} provides
  • Features related to your organization or enterprise not working as expected
  • General security questions about your organization or enterprise
| +| {% data variables.product.support_ticket_priority_low %} | You have a question or suggestion about your organization or enterprise on {% data variables.product.prodname_ghe_cloud %} that is not time-sensitive, or does not otherwise block the productivity of your team. |
  • Excessive resource usage for your organization or enterprise
  • Requests for health checks
  • Help with using Gists, notifications, wikis, {% data variables.product.prodname_pages %}, {% data variables.product.prodname_desktop %}, or other peripheral services or features with your organization or enterprise
  • Feature requests
  • Product feedback
| -### Prioridades de tíquetes para {% data variables.product.prodname_ghe_server %} +### Ticket priorities for {% data variables.product.prodname_ghe_server %} {% data reusables.support.ghes-priorities %} -## Resolução e fechamento de tíquete de suporte +## Resolving and closing support tickets -{% data variables.contact.premium_support %} pode considerar um tíquete resolvido após fornecer uma explicação, recomendação, instruções uso, instruções alternativas ou aconselhando você sobre uma versão de {% data variables.product.prodname_ghe_server %} disponível que resolve o problema. +{% data variables.contact.premium_support %} may consider a ticket solved after providing an explanation, recommendation, usage instructions, workaround instructions, or by advising you of an available {% data variables.product.prodname_ghe_server %} release that addresses the issue. -Se você usar um plugin, módulo ou código personalizado incompatível, o {% data variables.contact.premium_support %} solicitará a remoção desse item incompatível durante a tentativa de resolução do problema. Se o problema for corrigido quando o plugin, módulo ou código personalizado incompatível for removido, o {% data variables.contact.premium_support %} poderá considerar o tíquete resolvido. +If you use a custom or unsupported plug-in, module, or custom code, {% data variables.contact.premium_support %} may ask you to remove the unsupported plug-in, module, or code while attempting to resolve the issue. If the problem is fixed when the unsupported plug-in, module, or custom code is removed, {% data variables.contact.premium_support %} may consider the ticket solved. -{% data variables.contact.premium_support %} pode fechar um tíquete se este estiver fora do escopo do suporte ou se várias tentativas de entrar em contato com você ficaram sem resposta. Se {% data variables.contact.premium_support %} encerrar um tíquete por falta de resposta, você pode solicitar que {% data variables.contact.premium_support %} reabra o tíquete. +{% data variables.contact.premium_support %} may close a ticket if the ticket is outside the scope of support or if multiple attempts to contact you have gone unanswered. If {% data variables.contact.premium_support %} closes a ticket due to lack of response, you can request that {% data variables.contact.premium_support %} reopen the ticket. -## Receber créditos para respostas perdidas para tíquetes de suporte +## Receiving credits for missed responses to support tickets -Se você não receber uma resposta inicial dentro do tempo de resposta garantido para mais de quatro tíquetes em um determinado trimestre com base no ano fiscal de {% data variables.product.company_short %}, você será elegível a um crédito. Para honrar o SLA, {% data variables.product.company_short %} reembolsará 20% da taxa trimestral de {% data variables.contact.premium_support %} em dinheiro. Para receber o reembolso, você deve enviar uma solicitação de crédito. +If you don't receive an initial response within the guaranteed response time to more than four tickets in a given quarter based on {% data variables.product.company_short %}'s fiscal year, you're eligible for a credit. To honor the SLA, {% data variables.product.company_short %} will refund 20% of the quarterly {% data variables.contact.premium_support %} fee in cash. To receive the refund, you must submit a credit request. -A solicitação de crédito deve ser feita dentro de 30 dias do final do trimestre durante o qual {% data variables.contact.premium_support %} não respondeu aos seus tíquetes dentro do tempo de resposta indicado. As solicitações de crédito não serão cumpridas se o respectivo prazo tiver passado. Uma vez esgotado o respectivo prazo, você renunciou à capacidade de reivindicar um reembolso pelo crédito qualificado. +The credit request must be made within 30 days of the end of the quarter during which {% data variables.contact.premium_support %} did not respond to your tickets within the designated response time. Credit requests will not be honored if the respective deadline has passed. Once the respective deadline passes, you have waived the ability to claim a refund for the qualified credit. -Para receber um reembolso, você precisa enviar uma solicitação de crédito preenchida para . Para ser elegível, a solicitação de crédito deve: -- Receba de um endereço de e-mail associado à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} -- Ser recebida por {% data variables.product.company_short %} até o final do 30 dia após o trimestre em que ocorreram os quatro créditos qualificados -- Incluir "Solicitação de Crédito" na linha de assunto +To receive a refund, you must submit a completed credit request to . To be eligible, the credit request must: +- Be sent from an email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} +- Be received by {% data variables.product.company_short %} by the end of the 30th day after the quarter in which the four qualifying credits occurred +- Include "Credit Request" in the subject line -As seguintes informações **precisam ser incluídas** na solicitação de crédito: -- **Data** (A data precisa estar dentro de 30 dias após o trimestre com base no término do ano fiscal do {% data variables.product.company_short %} no qual as reivindicações ocorreram [31 de janeiro, 30 de abril, 31 de julho ou 31 de outubro]). -- **Contato do cliente** (Você precisa especificar o nome e o endereço de email). -- **Endereço do cliente** -- **Créditos qualificados** (Você precisa fornecer a data de cada crédito qualificado e o número do tíquete associado).{% ifversion fpt or ghec %} -- **Nome da organização do {% data variables.product.prodname_ghe_cloud %}** {% endif %} -- **Números do tíquete** +The following information **must be included** in your credit request: +- **Date** (The date must be within 30 days after the quarter based on {% data variables.product.company_short %}’s fiscal year end in which the claims occurred [January 31, April 30, July 31, or October 31].) +- **Customer contact** (You must specify both name and email address.) +- **Customer address** +- **Qualifying credits** (You must provide the date of each qualifying credit and the associated ticket number.){% ifversion fpt or ghec %} +- **Name of {% data variables.product.prodname_ghe_cloud %} organization**{% endif %} +- **Ticket numbers** -## Acessar conteúdo premium +## Accessing premium content -Acesse o conteúdo premium entrando no {% data variables.contact.contact_landing_page_portal %}. +You can access premium content by signing in to the {% data variables.contact.contact_landing_page_portal %}. diff --git a/translations/pt-BR/data/learning-tracks/admin.yml b/translations/pt-BR/data/learning-tracks/admin.yml index 5c6d8ced33..6c84460f88 100644 --- a/translations/pt-BR/data/learning-tracks/admin.yml +++ b/translations/pt-BR/data/learning-tracks/admin.yml @@ -1,6 +1,6 @@ get_started_with_github_ae: - title: 'Introdução ao {% data variables.product.prodname_ghe_managed %}' - description: 'Saiba mais sobre {% data variables.product.prodname_ghe_managed %} e realize a configuração inicial de uma nova empresa.' + title: 'Get started with {% data variables.product.prodname_ghe_managed %}' + description: 'Learn about {% data variables.product.prodname_ghe_managed %} and complete the initial configuration of a new enterprise.' featured_track: true versions: ghae: '*' @@ -13,8 +13,8 @@ get_started_with_github_ae: - /admin/github-actions/getting-started-with-github-actions-for-github-ae deploy_an_instance: - title: 'Implante uma instância' - description: 'Instale {% data variables.product.prodname_ghe_server %} na sua plataforma de escolha e configure a autenticação SAML.' + title: 'Deploy an instance' + description: 'Install {% data variables.product.prodname_ghe_server %} on your platform of choice and configure SAML authentication.' featured_track: true versions: ghes: '*' @@ -27,8 +27,8 @@ deploy_an_instance: - /admin/configuration/site-admin-dashboard upgrade_your_instance: - title: 'Atualize sua instância' - description: 'Teste as atualizações no treinamento, notifique os usuários de manutenção e atualize sua instância para os recursos e atualizações de segurança mais recentes.' + title: 'Upgrade your instance' + description: 'Test upgrades in staging, notify users of maintenance, and upgrade your instance for the latest features and security updates.' versions: ghes: '*' guides: @@ -40,8 +40,8 @@ upgrade_your_instance: - /admin/enterprise-management/upgrading-github-enterprise-server adopting_github_actions_for_your_enterprise_ghec: - title: 'Adote o GitHub Actions na sua empresa' - description: 'Saiba como planejar e implementar uma implantação de {% data variables.product.prodname_actions %} na sua empresa.' + title: 'Adopt GitHub Actions for your enterprise' + description: 'Learn how to plan and implement a rollout of {% data variables.product.prodname_actions %} in your enterprise.' versions: ghec: '*' guides: @@ -54,8 +54,8 @@ adopting_github_actions_for_your_enterprise_ghec: - /billing/managing-billing-for-github-actions/about-billing-for-github-actions adopting_github_actions_for_your_enterprise_ghes_and_ghae: - title: 'Adote o GitHub Actions na sua empresa' - description: 'Saiba como planejar e implementar uma implantação de {% data variables.product.prodname_actions %} na sua empresa.' + title: 'Adopt GitHub Actions for your enterprise' + description: 'Learn how to plan and implement a rollout of {% data variables.product.prodname_actions %} in your enterprise.' versions: ghes: '*' ghae: '*' @@ -71,8 +71,8 @@ adopting_github_actions_for_your_enterprise_ghes_and_ghae: - /billing/managing-billing-for-github-actions/about-billing-for-github-actions increase_fault_tolerance: - title: 'Aumente a tolerância de falha da instância' - description: "Faça backup do código de seus desenvolvedores e configure HA (alta disponibilidade) para garantir a confiabilidade do {% data variables.product.prodname_ghe_server %} em seu ambiente." + title: 'Increase the fault tolerance of your instance' + description: "Back up your developers' code and configure high availability (HA) to ensure the reliability of {% data variables.product.prodname_ghe_server %} in your environment." versions: ghes: '*' guides: @@ -83,8 +83,8 @@ increase_fault_tolerance: - /admin/configuration/using-github-enterprise-server-with-a-load-balancer improve_security_of_your_instance: - title: 'Melhore a segurança da sua instância' - description: "Revise a configuração de rede e as funcionalidades de segurança e reforce a instância do {% data variables.product.prodname_ghe_server %} em execução para proteger os dados da sua empresa." + title: 'Improve the security of your instance' + description: "Review network configuration and security features, and harden the instance running {% data variables.product.prodname_ghe_server %} to protect your enterprise's data." versions: ghes: '*' guides: @@ -99,8 +99,8 @@ improve_security_of_your_instance: - /admin/user-management/promoting-or-demoting-a-site-administrator configure_github_actions: - title: 'Configure o {% data variables.product.prodname_actions %}' - description: 'Permita que seus desenvolvedores criem, automatizem, personalizem e executem fluxos de trabalho de desenvolvimento avançados de software em {% data variables.product.product_location %} com {% data variables.product.prodname_actions %}.' + title: 'Configure {% data variables.product.prodname_actions %}' + description: 'Allow your developers to create, automate, customize, and execute powerful software development workflows for {% data variables.location.product_location %} with {% data variables.product.prodname_actions %}.' versions: ghes: '*' guides: @@ -113,7 +113,7 @@ configure_github_actions: configure_github_advanced_security: title: 'Configure {% data variables.product.prodname_GH_advanced_security %}' - description: "Melhore a qualidade e a segurança do código do seu desenvolvedor com {% data variables.product.prodname_GH_advanced_security %}." + description: "Improve the quality and security of your developers' code with {% data variables.product.prodname_GH_advanced_security %}." versions: ghes: '*' guides: @@ -125,8 +125,8 @@ configure_github_advanced_security: - /admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise get_started_with_your_enterprise_account: - title: 'Comece a usar a sua conta corporativa' - description: 'Comece com sua conta corporativa para gerenciar centralmente várias organizações em {% data variables.product.product_name %}.' + title: 'Get started with your enterprise account' + description: 'Get started with your enterprise account to centrally manage multiple organizations on {% data variables.product.product_name %}.' versions: ghes: '*' ghec: '*' diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-1/0-rc1.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-1/0-rc1.yml index e6d338fca0..520bfd612f 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-1/0-rc1.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-1/0-rc1.yml @@ -1,20 +1,20 @@ date: '2021-05-06' release_candidate: true deprecated: true -intro: "Se {% data variables.product.product_location %} estiver executando a compilação de um candidato à versão, você não poderá atualizar com um patch dinâmico. Recomendamos somente executar versões Release Candidate em ambientes de teste." +intro: If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. sections: security_fixes: - - '**MÉDIO** Em certas circunstâncias, os usuários que foram removidos de uma equipe ou organização poderiam manter acesso de escrita a branches para os quais tinham aberto uma solicitação de pull.' - - Os pacotes foram atualizados para as últimas versões de segurança. + - '**MEDIUM** Under certain circumstances, users who were removed from a team or organization could retain write access to branches they had existing pull requests opened for.' + - Packages have been updated to the latest security versions. bugs: - - 'Uma tarefa de limpeza agendada pode fazer com que o desempenho diminua em uma instância com uma tabela de `check_annotations` muito grande.' + - 'A scheduled cleanup job can cause performance to degrade on an instance with a very large `check_annotations` table.' changes: - - Serão arquivadas as anotações com mais de 4 meses de anotações de verificação. - - 'O campo `firstPatchedVersion` agora está disponível nos objetos `SecurityVulnerability` na API GraphQL.' + - Check annotations older than 4 months will be archived. + - 'The `firstPatchedVersion` field is now available on `SecurityVulnerability` objects in the GraphQL API.' known_issues: - - O registro npm do GitHub Packages não retorna mais um valor temporal em respostas de metadados. Isso foi feito para permitir melhorias substanciais de desempenho. Continuamos a ter todos os dados necessários para retornar um valor temporal como parte da resposta de metadados e continuaremos a retornar este valor no futuro quando tivermos resolvido os problemas de desempenho existentes. - - "Em uma nova configuração do GitHub Enterprise Server sem nenhum usuário, um invasor pode criar o primeiro usuário administrador." - - As regras personalizadas de firewall não são mantidas durante uma atualização. - - "Arquivos LFS do Git [enviados através da interface Web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de maneira incorreta." - - 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. - - "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." + - The GitHub Packages npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. + - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-2/0-rc1.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-2/0-rc1.yml index 0213319af5..634366e5e1 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-2/0-rc1.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-2/0-rc1.yml @@ -1,7 +1,7 @@ date: '2021-09-09' release_candidate: true deprecated: true -intro: If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. +intro: If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. sections: features: - heading: Custom patterns for secret scanning @@ -92,7 +92,7 @@ sections: - When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history. # https://github.com/github/releases/issues/1254 - - When a submodule is defined with a relative path in {% data variables.product.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. + - When a submodule is defined with a relative path in {% data variables.location.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. # https://github.com/github/releases/issues/1250 - The web UI can now be used to synchronize an out-of-date branch of a fork with the fork's upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)." diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-2/0.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-2/0.yml index ba34f7a61d..708b798394 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-2/0.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-2/0.yml @@ -90,7 +90,7 @@ sections: - When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history. # https://github.com/github/releases/issues/1254 - - When a submodule is defined with a relative path in {% data variables.product.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. + - When a submodule is defined with a relative path in {% data variables.location.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. # https://github.com/github/releases/issues/1250 - The web UI can now be used to synchronize an out-of-date branch of a fork with the fork's upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)." diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-3/0-rc1.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-3/0-rc1.yml index eaa5046942..840bd35324 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-3/0-rc1.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-3/0-rc1.yml @@ -4,7 +4,7 @@ deprecated: true intro: | {% note %} - **Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. + **Note:** If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. {% endnote %} @@ -31,7 +31,7 @@ sections: - | {% data variables.product.prodname_actions %} now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier. - Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, ephemeral runners are automatically unregistered from {% data variables.product.product_location %}, allowing you to perform any post-job management. + Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, ephemeral runners are automatically unregistered from {% data variables.location.product_location %}, allowing you to perform any post-job management. You can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to {% data variables.product.prodname_actions %} job requests. @@ -289,7 +289,7 @@ sections: - | Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are now deprecated in {% data variables.product.prodname_ghe_server %} 3.3. - Any repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated. + Any repositories that were already present and active on {% data variables.location.product_location %} running version 3.1 or 3.2 will have been automatically updated. Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-3/0.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-3/0.yml index f321bb7caa..5aec8eca3f 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-3/0.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-3/0.yml @@ -22,7 +22,7 @@ sections: - | {% data variables.product.prodname_actions %} now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier. - Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, ephemeral runners are automatically unregistered from {% data variables.product.product_location %}, allowing you to perform any post-job management. + Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, ephemeral runners are automatically unregistered from {% data variables.location.product_location %}, allowing you to perform any post-job management. You can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to {% data variables.product.prodname_actions %} job requests. @@ -289,7 +289,7 @@ sections: - | Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are now deprecated in {% data variables.product.prodname_ghe_server %} 3.3. - Any repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated. + Any repositories that were already present and active on {% data variables.location.product_location %} running version 3.1 or 3.2 will have been automatically updated. Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-4/0-rc1.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-4/0-rc1.yml index f49bb7d8e3..534c6d7f00 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-4/0-rc1.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-4/0-rc1.yml @@ -4,7 +4,7 @@ deprecated: true intro: | {% note %} - **Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. + **Note:** If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. {% endnote %} @@ -276,7 +276,7 @@ sections: - | Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards. - Any repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated. + Any repositories that were already present and active on {% data variables.location.product_location %} running version 3.1 or 3.2 will have been automatically updated. Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-4/0.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-4/0.yml index 0ff37f4058..8f3df3ef18 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-4/0.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-4/0.yml @@ -37,7 +37,7 @@ sections: notes: # https://github.com/github/releases/issues/1946 - | - If you use SAML authentication for {% data variables.product.prodname_ghe_server %}, you can now configure encrypted assertions from your IdP to improve security. Encrypted assertions add an additional layer of encryption when your IdP transmits information to {% data variables.product.product_location %}. For more information, see "[Using SAML](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml#enabling-encrypted-assertions)." + If you use SAML authentication for {% data variables.product.prodname_ghe_server %}, you can now configure encrypted assertions from your IdP to improve security. Encrypted assertions add an additional layer of encryption when your IdP transmits information to {% data variables.location.product_location %}. For more information, see "[Using SAML](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml#enabling-encrypted-assertions)." - heading: Edit files within pull requests in GitHub Mobile for iOS notes: @@ -298,7 +298,7 @@ sections: - | Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards. - Any repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated. + Any repositories that were already present and active on {% data variables.location.product_location %} running version 3.1 or 3.2 will have been automatically updated. Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-4/1.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-4/1.yml index 85b5feeb65..c1e26d10e7 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-4/1.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-4/1.yml @@ -95,7 +95,7 @@ sections: - | Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards. - Any repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated. + Any repositories that were already present and active on {% data variables.location.product_location %} running version 3.1 or 3.2 will have been automatically updated. Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-4/2.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-4/2.yml index be2036c2f4..a6e465aae2 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-4/2.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-4/2.yml @@ -71,7 +71,7 @@ sections: - | Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards. - Any repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated. + Any repositories that were already present and active on {% data variables.location.product_location %} running version 3.1 or 3.2 will have been automatically updated. Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml index 378a8b6706..527354bda7 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml @@ -4,7 +4,7 @@ deprecated: true intro: | {% note %} - **Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. + **Note:** If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. {% endnote %} diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-6/0-rc1.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-6/0-rc1.yml index fc7707911b..d4c97c5267 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-6/0-rc1.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-6/0-rc1.yml @@ -4,7 +4,7 @@ deprecated: true intro: | {% note %} - **Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend that you only run release candidates in a test environment. + **Note:** If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend that you only run release candidates in a test environment. {% endnote %} diff --git a/translations/pt-BR/data/reusables/actions/about-actions-for-enterprises.md b/translations/pt-BR/data/reusables/actions/about-actions-for-enterprises.md index aa9663f517..ff8b663350 100644 --- a/translations/pt-BR/data/reusables/actions/about-actions-for-enterprises.md +++ b/translations/pt-BR/data/reusables/actions/about-actions-for-enterprises.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 9848eca24695b7fb33afcf43bc447c7538f5fc71 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145094539" ---- -{% data variables.product.prodname_actions %} permite que {% ifversion ghec or ghae %}os integrantes da sua empresa{% elsif ghes %}pessoas que utilizam {% data variables.product.product_location %}{% endif %} melhorem a produtividade, automatizando todas as fases do fluxo de trabalho de desenvolvimento de software. +{% data variables.product.prodname_actions %} allows {% ifversion ghec or ghae %}members of your enterprise{% elsif ghes %}people who use {% data variables.location.product_location %}{% endif %} to improve productivity by automating every phase of the software development workflow. diff --git a/translations/pt-BR/data/reusables/actions/cache-default-size.md b/translations/pt-BR/data/reusables/actions/cache-default-size.md index 1de06dc5d6..c79aef489f 100644 --- a/translations/pt-BR/data/reusables/actions/cache-default-size.md +++ b/translations/pt-BR/data/reusables/actions/cache-default-size.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: ab5272155710feedd08dd5b5e4e0f84eacc36694 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147067407" ---- -Por padrão, o armazenamento em cache total que {% data variables.product.prodname_actions %} usa no armazenamento externo para {% data variables.product.product_location %} está limitado a um máximo de 10 GB por repositório e o tamanho máximo permitido que pode ser definido para um repositório é de 25 GB. +By default, the total cache storage that {% data variables.product.prodname_actions %} uses on the external storage for {% data variables.location.product_location %} is limited to a maximum of 10 GB per repository, and the maximum allowed size that can be set for a repository is 25 GB. diff --git a/translations/pt-BR/data/reusables/actions/disabling-github-actions.md b/translations/pt-BR/data/reusables/actions/disabling-github-actions.md index d948485fa2..ef2c62fe2f 100644 --- a/translations/pt-BR/data/reusables/actions/disabling-github-actions.md +++ b/translations/pt-BR/data/reusables/actions/disabling-github-actions.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 3812d31ab730736a7af4ae38c347325f28aeffba -ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147875693" ---- -Por padrão, {% ifversion ghes or ghae %}depois que o {% data variables.product.prodname_actions %} estiver habilitado no {% data variables.product.product_location %}, ele{% elsif fpt or ghec %}{% data variables.product.prodname_actions %}{% endif %} ficará habilitado em todos os repositórios e em todas as organizações. Você pode optar por desabilitar o {% data variables.product.prodname_actions %} ou limitá-lo às ações {% ifversion actions-workflow-policy %}e aos fluxos de trabalho reutilizáveis{% endif %} da sua {% ifversion ghec or ghes or ghae %}empresa{% else %}organização{% endif %}. +By default, {% ifversion ghes or ghae %}after {% data variables.product.prodname_actions %} is enabled on {% data variables.location.product_location %}, it{% elsif fpt or ghec %}{% data variables.product.prodname_actions %}{% endif %} is enabled on all repositories and organizations. You can choose to disable {% data variables.product.prodname_actions %} or limit it to actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %} in your {% ifversion ghec or ghes or ghae %}enterprise{% else %}organization{% 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 d608583c5f..b0541a2c44 100644 --- a/translations/pt-BR/data/reusables/actions/enterprise-common-prereqs.md +++ b/translations/pt-BR/data/reusables/actions/enterprise-common-prereqs.md @@ -1,17 +1,9 @@ ---- -ms.openlocfilehash: 9c9f3713944a20dcdac639249d10c0ab8a4f7baf -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145094434" ---- -* Revisar os requisitos de hardware para {% data variables.product.prodname_actions %}. Para obter mais informações, confira "[Introdução ao {% 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)". -* O TLS deve ser configurado para o domínio de {% data variables.product.product_location %}. Para obter mais informações, confira "[Como configurar o TLS](/admin/configuration/configuring-tls)". +* 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.location.product_location %}'s domain. For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." {% note %} - **Observação:** {% data reusables.actions.enterprise-self-signed-cert %} + **Note:** {% data reusables.actions.enterprise-self-signed-cert %} {% endnote %} * {% data reusables.actions.enterprise-http-proxy %} 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 2f79931eca..62d80c0c34 100644 --- a/translations/pt-BR/data/reusables/actions/enterprise-http-proxy.md +++ b/translations/pt-BR/data/reusables/actions/enterprise-http-proxy.md @@ -1,13 +1,5 @@ ---- -ms.openlocfilehash: c61e071aa06bda0d31a1c4578dfe78addb55867e -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147167376" ---- -Se você tiver um **Servidor Proxy HTTP** configurado no {% data variables.product.product_location %}: - - Você deve adicionar `localhost` e `127.0.0.1` à lista de **Exclusão de Proxy HTTP**. - - Se o bucket BYOS não for roteável, você também deverá adicionar a URL do bucket à lista de exclusão. +If you have an **HTTP Proxy Server** configured on {% data variables.location.product_location %}: + - You must add `localhost` and `127.0.0.1` to the **HTTP Proxy Exclusion** list. + - If the BYOS bucket is not routable, then you must also add the bucket's URL to the exclusion list. - Para obter mais informações sobre como alterar as configurações de proxy, veja "[Configurando um servidor proxy Web de saída](/admin/configuration/configuring-an-outbound-web-proxy-server)". \ No newline at end of file + For more information on changing your proxy settings, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-an-outbound-web-proxy-server)." \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/enterprise-marketplace-actions.md b/translations/pt-BR/data/reusables/actions/enterprise-marketplace-actions.md index cc5e9c324d..44dd8a398e 100644 --- a/translations/pt-BR/data/reusables/actions/enterprise-marketplace-actions.md +++ b/translations/pt-BR/data/reusables/actions/enterprise-marketplace-actions.md @@ -1,16 +1,8 @@ ---- -ms.openlocfilehash: 5e5e40bc161c7779bdfc27931921963c5bf74fc5 -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145094421" ---- {% ifversion ghes %} {% note %} -**Observação:** o {% data variables.product.prodname_actions %} no {% data variables.product.product_location %} pode ter acesso limitado às ações do {% data variables.product.prodname_dotcom_the_website %} ou do {% data variables.product.prodname_marketplace %}. Para obter mais informações, confira "[Como gerenciar o acesso às ações do {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/managing-access-to-actions-from-githubcom)" e entre em contato com o administração do site do {% data variables.product.prodname_enterprise %}. +**Note:** {% data variables.product.prodname_actions %} on {% data variables.location.product_location %} may have limited access to actions on {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_marketplace %}. For more information, see "[Managing access to actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/managing-access-to-actions-from-githubcom)" and contact your {% data variables.product.prodname_enterprise %} site administrator. {% endnote %} 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 a34549549b..f241306500 100644 --- a/translations/pt-BR/data/reusables/actions/enterprise-postinstall-nextsteps.md +++ b/translations/pt-BR/data/reusables/actions/enterprise-postinstall-nextsteps.md @@ -1,11 +1,3 @@ ---- -ms.openlocfilehash: d1d2813fed8f4ebc9e76856fb6477ab58b3c3657 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145094418" ---- -### Próximas etapas +### Next steps -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 as próximas etapas, como o gerenciamento das permissões de acesso do {% data variables.product.prodname_actions %} e a adição de executores auto-hospedados, volte a "[Introdução ao {% 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)". +After the configuration run has successfully completed, {% data variables.product.prodname_actions %} will be enabled on {% data variables.location.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)." diff --git a/translations/pt-BR/data/reusables/actions/github-connect-resolution.md b/translations/pt-BR/data/reusables/actions/github-connect-resolution.md index 3376093956..54fa9eebde 100644 --- a/translations/pt-BR/data/reusables/actions/github-connect-resolution.md +++ b/translations/pt-BR/data/reusables/actions/github-connect-resolution.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 1e9105d419c42c1210ebe51b785ef3c36df094f8 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147066079" ---- -Quando um fluxo de trabalho usa uma ação, fazendo referência ao repositório onde a ação é armazenada, {% data variables.product.prodname_actions %} primeiro tentará encontrar o repositório em {% data variables.product.product_location %}. Se o repositório não existir em {% data variables.product.product_location %} e se você tiver acesso automático para {% data variables.product.prodname_dotcom_the_website %} habilitado, {% data variables.product.prodname_actions %} tentará encontrar o repositório em {% data variables.product.prodname_dotcom_the_website %}. +When a workflow uses an action by referencing the repository where the action is stored, {% data variables.product.prodname_actions %} will first try to find the repository on {% data variables.location.product_location %}. If the repository does not exist on {% data variables.location.product_location %}, and if you have automatic access to {% data variables.product.prodname_dotcom_the_website %} enabled, {% data variables.product.prodname_actions %} will try to find the repository on {% data variables.product.prodname_dotcom_the_website %}. diff --git a/translations/pt-BR/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md b/translations/pt-BR/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md index 1d8d542831..15b3fea980 100644 --- a/translations/pt-BR/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md +++ b/translations/pt-BR/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md @@ -1,20 +1,12 @@ ---- -ms.openlocfilehash: 446bc8429d81d54d38eeaf2852a61d25db17da68 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145186073" ---- -Você pode usar `jobs..outputs` para criar um `map` das saídas para um trabalho. As saídas de trabalho estão disponíveis para todos os trabalhos downstream que dependem deste trabalho. Para obter mais informações sobre como definir dependências de trabalho, confira [`jobs..needs`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idneeds). +You can use `jobs..outputs` to create a `map` of outputs for a job. Job outputs are available to all downstream jobs that depend on this job. For more information on defining job dependencies, see [`jobs..needs`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idneeds). {% data reusables.actions.output-limitations %} -As saídas de trabalho que contêm expressões são avaliadas no executor ao final de cada trabalho. As saídas que contêm segredos são eliminadas no executor e não são enviadas para {% data variables.product.prodname_actions %}. +Job outputs containing expressions are evaluated on the runner at the end of each job. Outputs containing secrets are redacted on the runner and not sent to {% data variables.product.prodname_actions %}. -Para usar saídas de trabalho em um trabalho dependente, você pode usar o contexto `needs`. Para obter mais informações, confira "[Contextos](/actions/learn-github-actions/contexts#needs-context)". +To use job outputs in a dependent job, you can use the `needs` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#needs-context)." -### Exemplo: Definindo saídas para um trabalho +### Example: Defining outputs for a job {% raw %} ```yaml @@ -26,10 +18,18 @@ jobs: output1: ${{ steps.step1.outputs.test }} output2: ${{ steps.step2.outputs.test }} steps: - - id: step1 + - id: step1{% endraw %} +{%- ifversion actions-save-state-set-output-envs %} + run: echo "test=hello" >> $GITHUB_OUTPUT +{%- else %} run: echo "::set-output name=test::hello" - - id: step2 +{%- endif %}{% raw %} + - id: step2{% endraw %} +{%- ifversion actions-save-state-set-output-envs %} + run: echo "test=world" >> $GITHUB_OUTPUT +{%- else %} run: echo "::set-output name=test::world" +{%- endif %}{% raw %} job2: runs-on: ubuntu-latest needs: job1 diff --git a/translations/pt-BR/data/reusables/actions/self-hosted-runner-management-permissions-required.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-management-permissions-required.md index 467a9ecaaa..9c3f42102f 100644 --- a/translations/pt-BR/data/reusables/actions/self-hosted-runner-management-permissions-required.md +++ b/translations/pt-BR/data/reusables/actions/self-hosted-runner-management-permissions-required.md @@ -1,17 +1,9 @@ ---- -ms.openlocfilehash: 324332325762999d6daaf4241ec0f9e291ce98a8 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145065351" ---- -Um executor auto-hospedado pode estar localizado no repositório, na organização ou {% ifversion fpt or ghec %}nas configurações de conta corporativa do {% data variables.product.prodname_dotcom %}{% elsif ghes or ghae %} nas configurações da empresa do {% data variables.product.product_location %}{% endif %}. Para gerenciar um executor auto-hospedado, você deve ter as seguintes permissões, dependendo de onde o executor auto-hospedado foi adicionado: -- **Repositório do usuário**: você precisa ser o proprietário do repositório. -- **Organização**: você precisa ser um proprietário da organização. -- **Repositório da organização**: você precisa ser um proprietário da organização ou ter acesso de administrador no repositório. +A self-hosted runner can be located in either your repository, organization, or {% ifversion fpt or ghec %}enterprise account settings on {% data variables.product.prodname_dotcom %}{% elsif ghes or ghae %} enterprise settings on {% data variables.location.product_location %}{% endif %}. To manage a self-hosted runner, you must have the following permissions, depending on where the self-hosted runner was added: +- **User repository**: You must be the repository owner. +- **Organization**: You must be an organization owner. +- **Organization repository**: You must be an organization owner, or have admin access to the repository. {% ifversion ghec %} -- **Conta corporativa**: você precisa ser um proprietário da empresa. +- **Enterprise account**: You must be an enterprise owner. {% elsif ghes or ghae %} -- **Empresa**: você precisa ser um administrador do site do {% data variables.product.prodname_enterprise %}. +- **Enterprise**: You must be a {% data variables.product.prodname_enterprise %} site administrator. {% endif %} diff --git a/translations/pt-BR/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md index fd0ab82b6b..a648712470 100644 --- a/translations/pt-BR/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md +++ b/translations/pt-BR/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: f5a11de0003ae27a2b49233ad5ef8218423b50d2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147063935" ---- -Para usar ações de {% data variables.product.prodname_dotcom_the_website %},{% ifversion ghes %}, {% data variables.product.product_location %} e {% endif %} seus executores auto-hospedados devem poder fazer conexões de saída para {% data variables.product.prodname_dotcom_the_website %}. Nenhuma conexão de entrada de {% data variables.product.prodname_dotcom_the_website %} é necessária. Para obter mais informações. Para obter mais informações, confira "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-betweens-self-hosted-runners-and-githubcom)". +To use actions from {% data variables.product.prodname_dotcom_the_website %},{% ifversion ghes %} both {% data variables.location.product_location %} and{% endif %} your self-hosted runners must be able to make outbound connections to {% data variables.product.prodname_dotcom_the_website %}. No inbound connections from {% data variables.product.prodname_dotcom_the_website %} are required. For more information. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-betweens-self-hosted-runners-and-githubcom)." diff --git a/translations/pt-BR/data/reusables/actions/self-hosted-runner-ports-protocols.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-ports-protocols.md index af3a7e5a08..862638d843 100644 --- a/translations/pt-BR/data/reusables/actions/self-hosted-runner-ports-protocols.md +++ b/translations/pt-BR/data/reusables/actions/self-hosted-runner-ports-protocols.md @@ -1,9 +1,3 @@ ---- -ms.openlocfilehash: 51b563029cedae82f02da31a5d6473274efb8218 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145083805" ---- -{% ifversion ghes or ghae %} A conexão entre os executores auto-hospedados e o {% data variables.product.product_name %} é feita por {% ifversion ghes %}HTTP (porta 80) ou {% endif %}HTTPS (porta 443). {% ifversion ghes %}Para garantir conectividade por meio de HTTPS, configure TLS para {% data variables.product.product_location %}. Para obter mais informações, confira "[Como configurar o TLS](/admin/configuration/configuring-network-settings/configuring-tls)".{% endif %}{% endif %} +{% ifversion ghes or ghae %} +The connection between self-hosted runners and {% data variables.product.product_name %} is over {% ifversion ghes %}HTTP (port 80) or {% endif %}HTTPS (port 443). {% ifversion ghes %}To ensure connectivity over HTTPS, configure TLS for {% data variables.location.product_location %}. For more information, see "[Configuring TLS](/admin/configuration/configuring-network-settings/configuring-tls)."{% endif %} +{% endif %} diff --git a/translations/pt-BR/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md b/translations/pt-BR/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md index 60b09d68a6..1290be8b1c 100644 --- a/translations/pt-BR/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md +++ b/translations/pt-BR/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 48e8bec26155fe30e20642892cad797e869d69bc -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147065039" ---- -Se você usar executores efêmeros e tiver desabilitado as atualizações automáticas, para atualizar o {% data variables.product.product_location %}, primeiro você deverá atualizar os executores auto-hospedados para a versão do aplicativo executor que sua instância atualizada executará. A atualização do {% data variables.product.product_location %} antes de atualizar os executores efêmeros poderá fazer com que os executores fiquem offline. Para obter mais informações, confira "[Como fazer upgrade do {% data variables.product.product_name %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)". +If you use ephemeral runners and have disabled automatic updates, before you upgrade {% data variables.location.product_location %}, you should first upgrade your self-hosted runners to the version of the runner application that your upgraded instance will run. Upgrading {% data variables.location.product_location %} before you upgrade ephemeral runners may result in your runners going offline. For more information, see "[Upgrading {% data variables.product.product_name %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." 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 37b70cdbe6..bc08e3019b 100644 --- a/translations/pt-BR/data/reusables/actions/workflow-template-overview.md +++ b/translations/pt-BR/data/reusables/actions/workflow-template-overview.md @@ -1,11 +1,3 @@ ---- -ms.openlocfilehash: 51d4b7e23640eafc3bd7830b4ce8f4b6d209f40f -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145083801" ---- -O {% data variables.product.prodname_dotcom %} fornece um fluxo de trabalho inicial pré-configurado que você pode personalizar para criar seu fluxo de trabalho de integração contínua. O {% data variables.product.product_name %} analisa seu código e mostra o fluxo de trabalho inicial de CI que pode ser útil para 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 o fluxo de trabalho inicial como ponto de partida para criar seu fluxo de trabalho personalizado ou usá-lo no estado em que se encontra. +{% data variables.product.prodname_dotcom %} provides preconfigured starter workflows that you can customize to create your own continuous integration workflow. {% data variables.product.product_name %} analyzes your code and shows you CI starter workflows that might be useful for your repository. For example, if your repository contains Node.js code, you'll see suggestions for Node.js projects. You can use starter workflows as a starting place to build your custom workflow or use them as-is. -Navegue pela lista completa do fluxo de trabalho inicial no repositório `actions/starter-workflows` {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows){% else %} no {% data variables.product.product_location %}{% endif %}. +You can browse the full list of starter workflows in the {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` repository on {% data variables.location.product_location %}{% endif %}. diff --git a/translations/pt-BR/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md b/translations/pt-BR/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md index f83898b4bc..6f3376cb84 100644 --- a/translations/pt-BR/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md +++ b/translations/pt-BR/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md @@ -1,22 +1,14 @@ ---- -ms.openlocfilehash: 281a3a039c8a557c209e756d107ac1856a181017 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145083796" ---- -Registramos e exibimos dois números de autores de commits do {% data variables.product.prodname_GH_advanced_security %} no {% data variables.product.product_location %}: +We record and display two numbers of committers for {% data variables.product.prodname_GH_advanced_security %} on {% data variables.location.product_location %}: -- **Autores de commits** é o número de autores de commits que contribuíram com, pelo menos, um repositório {% ifversion fpt or ghec %}privado {% endif %}em uma organização e que usam uma estação na sua licença corporativa. Ou seja, eles também são integrantes da organização, um colaborador externo ou têm um convite pendente para ingressar em uma organização na sua empresa. -- **Exclusivo deste repositório/desta organização** é o número de autores de commits que contribuíram apenas neste repositório ou nos repositórios desta organização. Este número mostra a quantidade de estações de licença que você pode liberar, desabilitando {% data variables.product.prodname_GH_advanced_security %} para esse repositório ou organização. +- **Committers** is the number of committers who contributed to at least one {% ifversion fpt or ghec %}private {% endif %}repository in an organization and who use a seat in your enterprise license. That is, they are also an organization member, an external collaborator, or have a pending invitation to join an organization in your enterprise. +- **Unique to this repository/organization** is the number of committers who contributed only to this repository, or to repositories in this organization. This number shows how many license seats you can free up by disabling {% data variables.product.prodname_GH_advanced_security %} for that repository or organization. -Se não houver committers exclusivos, todos os committers ativos também contribuem para outros repositórios ou organizações que usam {% data variables.product.prodname_GH_advanced_security %}. Desabilitar o recurso para esse repositório ou organização não liberaria nenhuma estação na sua licença. +If there are no unique committers, all active committers also contribute to other repositories or organizations that use {% data variables.product.prodname_GH_advanced_security %}. Disabling the feature for that repository or organization would not free any seats on your license. -Ao remover um usuário da sua conta corporativa, a licença do usuário é liberada dentro de 24 horas. +When you remove a user from your enterprise account, the user's license is freed within 24 hours. {% note %} -**Observação:** os usuários podem contribuir com vários repositórios ou várias organizações. O uso é medido em toda a conta corporativa para garantir que cada integrante utilize uma estação, independentemente da quantidade de repositórios ou organizações para as quais o usuário contribui. +**Note:** Users can contribute to multiple repositories or organizations. Usage is measured across the whole enterprise account to ensure that each member uses one seat regardless of how many repositories or organizations the user contributes to. {% endnote %} diff --git a/translations/pt-BR/data/reusables/apps/user-to-server-rate-limits.md b/translations/pt-BR/data/reusables/apps/user-to-server-rate-limits.md index 0db6a8225c..f56f5c3e0c 100644 --- a/translations/pt-BR/data/reusables/apps/user-to-server-rate-limits.md +++ b/translations/pt-BR/data/reusables/apps/user-to-server-rate-limits.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 3bc47303cbc18b4d40a76fd12e6f692990f66c54 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145094245" ---- -{% ifversion ghes %}Por padrão, as solicitações de usuário para servidor{% else %}Usuário para servidor{% endif %} são limitadas a {% ifversion ghae %}15 mil{% elsif fpt or ghec or ghes %}cinco mil{% endif %} solicitações por hora e por usuário autenticado. Todas as solicitações de aplicativos OAuth autorizadas por um usuário ou um token de acesso pessoal pertencentes ao usuário e as solicitações autenticadas com uma das credenciais de autenticação do usuário compartilham a cota de {% ifversion ghae %}15 mil{% elsif fpt or ghec or ghes %}cinco mil{% endif %} solicitações por hora para esse usuário. +{% ifversion ghes %}By default, user-to-server{% else %}User-to-server{% endif %} requests are limited to {% ifversion ghae %}15,000{% elsif fpt or ghec or ghes %}5,000{% endif %} requests per hour and per authenticated user. All requests from OAuth applications authorized by a user or a {% data variables.product.pat_generic %} owned by the user, and requests authenticated with any of the user's authentication credentials, share the same quota of {% ifversion ghae %}15,000{% elsif fpt or ghec or ghes %}5,000{% endif %} requests per hour for that user. diff --git a/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md b/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md index e2d82877c2..a135b85355 100644 --- a/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md +++ b/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md @@ -1,113 +1,193 @@ ---- -ms.openlocfilehash: 5cb0c8cc93347c8da7c37bfe1082fc933f677288 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147424821" ---- -| Nome da categoria | Descrição +| Category name | Description |------------------|------------------- -{%- ifversion fpt or ghec %} | `account` | Contém atividades relacionadas a uma conta da organização. -| `advisory_credit` | Contém atividades relacionadas ao crédito de um colaborador de uma consultoria de segurança no {% data variables.product.prodname_advisory_database %}. Para obter mais informações, confira "[Sobre os avisos de segurança do {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". -{%- endif %} | `artifact` | Contém atividades relacionadas aos artefatos de execução de fluxo de trabalho do {% data variables.product.prodname_actions %}. -{%- ifversion audit-log-streaming %} | `audit_log_streaming` | Contém atividades relacionadas aos logs de auditoria de streaming para organizações em uma conta corporativa. -{%- endif %} {%- ifversion fpt or ghec %} | `billing` | Contém atividades relacionadas à cobrança de uma organização. -{%- endif %} {%- ifversion ghec or ghes or ghae %} | `business` | Contém atividades relacionadas às configurações corporativas de uma empresa. -{%- endif %} {%- ifversion ghec or ghes or ghae %} | `business` | Contém atividades relacionadas às configurações corporativas de uma empresa. -{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `business_secret_scanning_custom_pattern` | Contém atividades relacionadas aos padrões personalizados para a verificação de segredos em uma empresa. -{%- endif %} | `checks` | Contém atividades relacionadas aos pacotes de verificação e às execuções. -{%- ifversion fpt or ghec %} | `codespaces` | Contém atividades relacionadas aos codespaces de uma organização. -{%- endif %} | `commit_comment` | Contém atividades relacionadas à atualização ou à exclusão de comentários de commit. -{%- ifversion ghes %} | `config_entry` | Contém atividades relacionadas a definições de configuração. Esses eventos só ficam visíveis no log de auditoria do administrador do site. -{%- endif %} {%- ifversion fpt or ghec or ghes > 3.2 or ghae %} | | `dependabot_alerts` | Contém atividades de configuração no nível da organização para {% data variables.product.prodname_dependabot_alerts %} nos repositórios existentes. Para obter mais informações, confira "[Sobre os {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)". -| `dependabot_alerts_new_repos` | Contém atividades de configuração no nível da organização para {% data variables.product.prodname_dependabot_alerts %} em novos repositórios criados na organização. -| `dependabot_repository_access` | Contém atividades relacionadas aos repositórios privados de uma organização que o {% data variables.product.prodname_dependabot %} tem permissão para acessar. -{%- endif %} {%- ifversion fpt or ghec or ghes > 3.2 %} | `dependabot_security_updates` | Contém atividades de configuração no nível da organização para {% data variables.product.prodname_dependabot_security_updates %} nos repositórios existentes. Para obter mais informações, confira "[Como configurar {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)". -| `dependabot_security_updates_new_repos` | Contém atividades de configuração de nível da organização nas {% data variables.product.prodname_dependabot_security_updates %} para os repositórios criados na organização. -{%- endif %} | `dependency_graph` | Contém atividades de configuração no nível da organização dos grafos de dependências nos repositórios. Para obter mais informações, confira "[Sobre o grafo de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". -| `dependency_graph_new_repos` | Contém atividades de configuração no nível da organização para novos repositórios criados na organização. -{%- ifversion fpt or ghec %} | `discussion` | Contém atividades relacionadas às discussões da equipe. -| `discussion_comment` | Contém atividades relacionadas aos comentários postados em discussões em uma página da equipe. -| `discussion_post` | Contém atividades relacionadas às discussões postadas em uma página da equipe. -| `discussion_post_reply` | Contém atividades relacionadas às respostas de discussões postadas em uma página da equipe. -{%- endif %} {%- ifversion ghec or ghes %} | `dotcom_connection` | Contém atividades relacionadas ao {% data variables.product.prodname_github_connect %}. -| `enterprise` | Contém atividades relacionadas às configurações da empresa. -{%- endif %} {%- ifversion ghec %} | `enterprise_domain` | Contém atividades relacionadas aos domínios corporativos verificados. -| `enterprise_installation` | Contém atividades relacionadas aos {% data variables.product.prodname_github_app %}s associados a uma conexão corporativa do {% data variables.product.prodname_github_connect %}. -{%- endif %} {%- ifversion fpt or ghec %} | `environment` | Contém atividades relacionadas a ambientes do {% data variables.product.prodname_actions %}. -{%- endif %} {%- ifversion ghae %} | `external_group` | Contém atividades relacionadas aos grupos do Okta. -| `external_identity` | Contém atividades relacionadas a um usuário em um grupo do Okta. -{%- endif %} | `gist` | Contém atividades relacionadas ao Gists. -| `hook` | Contém atividades relacionadas a webhooks. -| `integration` | Contém atividades relacionadas às integrações de uma conta. -| `integration_installation` | Contém atividades relacionadas às integrações instaladas em uma conta. -| `integration_installation_request` | Contém atividades relacionadas às solicitações de membros da organização para proprietários aprovarem integrações para uso na organização. -{%- ifversion ghec or ghae %} | `ip_allow_list` | Contém atividades relacionadas à habilitação ou à desabilitação da lista de permissões de IP para uma organização. -| `ip_allow_list_entry` | Contém atividades relacionadas à criação, à exclusão e à edição de uma entrada na lista de permissões de IP para uma organização. -{%- endif %} | `issue` | Contém atividades relacionadas à fixação, à transferência ou à exclusão de um problema em um repositório. -| `issue_comment` | Contém atividades relacionadas à fixação, à transferência ou à exclusão de comentários em um problema. -| `issues` | Contém atividades relacionadas à habilitação ou à desabilitação da criação de problemas para uma organização. -{%- ifversion fpt or ghec %} | `marketplace_agreement_signature` | Contém atividades relacionadas à assinatura do Contrato de Desenvolvedor do {% data variables.product.prodname_marketplace %}. -| `marketplace_listing` | Contém atividades relacionadas aos aplicativos de listagem do {% data variables.product.prodname_marketplace %}. -{%- endif %} | `members_can_create_pages` | Contém atividades relacionadas ao gerenciamento da publicação de sites do {% data variables.product.prodname_pages %} para repositórios na organização. Para obter mais informações, confira "[Como gerenciar a publicação de sites do {% data variables.product.prodname_pages %} para sua organização](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". -| `members_can_create_private_pages` | Contém atividades relacionadas ao gerenciamento da publicação de sites privados do {% data variables.product.prodname_pages %} para repositórios na organização. -| `members_can_create_public_pages` | Contém atividades relacionadas ao gerenciamento da publicação de sites públicos do {% data variables.product.prodname_pages %} para repositórios na organização. -{%- ifversion ghec or ghes or ghae %} | `members_can_delete_repos` | Contém atividades relacionadas à habilitação ou à desabilitação da criação de repositórios para uma organização. -{%- endif %} {%- ifversion fpt or ghec %} | `members_can_view_dependency_insights` | Contém atividades de configuração no nível da organização que permitem que os membros da organização vejam insights de dependência. -| `migration` | Contém atividades relacionadas à transferência de dados de um local de *origem* (como uma organização do {% data variables.product.prodname_dotcom_the_website %} ou uma instância do {% data variables.product.prodname_ghe_server %}) para uma instância de *destino* do {% data variables.product.prodname_ghe_server %}. -{%- endif %} | `oauth_access` | Contém atividades relacionadas aos tokens de acesso OAuth. -| `oauth_application` | Contém atividades relacionadas aos Aplicativos OAuth. -{%- ifversion fpt or ghec %} | `oauth_authorization` | Contém atividades relacionadas à autorização de Aplicativos OAuth. -{%- endif %} | `org` | Contém atividades relacionadas à associação a uma organização. -{%- ifversion ghec or ghes or ghae %} | `org_credential_authorization` | Contém atividades relacionadas à autorização de credenciais para uso com o logon único do SAML. -{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `org_secret_scanning_custom_pattern` | Contém atividades relacionadas aos padrões personalizados para a verificação de segredos em uma organização. Para obter mais informações, confira "[Como definir padrões personalizados para a verificação de segredos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)". -| `org.secret_scanning_push_protection` | Contém atividades relacionadas aos padrões personalizados de verificação de segredos em uma organização. Para obter mais informações, confira "[Como proteger os pushes com a verificação de segredos](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)". -{%- endif %} | `organization_default_label` | Contém atividades relacionadas aos rótulos padrão em uma organização. -{%- ifversion fpt or ghec or ghes %} | `organization_domain` |Contém atividades relacionadas aos domínios da organização verificados. -| `organization_projects_change` | Contém atividades relacionadas aos quadros de projetos de toda a organização em uma empresa. -{%- endif %} {%- ifversion fpt or ghec %} | `pages_protected_domain` | Contém atividades relacionadas aos domínios personalizados verificados do {% data variables.product.prodname_pages %}. -| `payment_method` | Contém atividades relacionadas à forma de pagamento do {% data variables.product.prodname_dotcom %} de uma organização. -| `prebuild_configuration` | Contém atividades relacionadas às configurações de pré-build do {% data variables.product.prodname_github_codespaces %}. -{%- endif %} {%- ifversion ghes %} | `pre_receive_environment` | Contém atividades relacionadas aos ambientes de gancho de pré-recebimento. -| `pre_receive_hook` | Contém atividades relacionadas aos ganchos de pré-recebimento. -{%- endif %} {%- ifversion ghes %} | `private_instance_encryption` | Contém atividades relacionadas à habilitação do modo privado para uma empresa. -{%- endif %} | `private_repository_forking` | Contém atividades relacionadas à permissão de forks de repositórios privados e internos para um repositório, uma organização ou uma empresa. -{%- ifversion fpt or ghec %} | `profile_picture` | Contém atividades relacionadas à imagem de perfil de uma organização. -{%- endif %} | `project` | Contém atividades relacionadas aos quadros de projetos. -| `project_field` | Contém atividades relacionadas à criação e à exclusão de campos em um quadro de projetos. -| `project_view` | Contém atividades relacionadas à criação e à exclusão de exibições em um quadro de projetos. -| `protected_branch` | Contém atividades relacionadas aos branches protegidos. -| `public_key` | Contém atividades relacionadas às chaves SSH e às chaves de implantação. -| `pull_request` | Contém atividades relacionadas às solicitação de pull. -| `pull_request_review` | Contém atividades relacionadas às revisões de solicitação de pull. -| `pull_request_review_comment` | Contém atividades relacionadas aos comentários de revisão de solicitação de pull. -| `repo` | Contém atividades relacionadas aos repositórios pertencentes a uma organização. -{%- ifversion fpt or ghec %} | `repository_advisory` | Contém atividades de nível do repositório relacionadas às consultorias de segurança no {% data variables.product.prodname_advisory_database %}. Para obter mais informações, confira "[Sobre os avisos de segurança do {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". -| `repository_content_analysis` | Contém atividades relacionadas [à habilitação ou à desabilitação do uso de dados em um repositório privado](/articles/about-github-s-use-of-your-data). -| `repository_dependency_graph` | Contém atividades de nível do repositório relacionadas à habilitação ou à desabilitação do grafo de dependência em um repositório {% ifversion fpt or ghec %}privado {% endif %}. Para obter mais informações, confira "[Sobre o grafo de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". -{%- endif %} | `repository_image` | Contém atividades relacionadas a imagens para um repositório. -| `repository_invitation` | Contém atividades relacionadas a convites para ingresso em um repositório. -| `repository_projects_change` | Contém atividades relacionadas à habilitação de projetos em um repositório ou em todos os repositórios de uma organização. -{%- ifversion ghec or ghes or ghae %} | `repository_secret_scanning` | Contém atividades de nível do repositório relacionadas à verificação de segredos. Para obter mais informações, confira "[Sobre a verificação de segredos](/github/administering-a-repository/about-secret-scanning)". -{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `repository_secret_scanning_custom_pattern` | Contém atividades relacionadas a padrões personalizados da verificação de segredos em um repositório. Para obter mais informações, confira "[Como definir padrões personalizados para a verificação de segredos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)". {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %} | `repository_secret_scanning_push_protection` | Contém atividades relacionadas a padrões personalizados da verificação de segredos em um repositório. Para obter mais informações, confira "[Como proteger os pushes com a verificação de segredos](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)". -{%- endif %} {%- ifversion fpt or ghec %} | `repository_visibility_change` | Contém atividades relacionadas à permissão de que os membros da organização alterem a visibilidade do repositório para a organização. -{%- endif %} | `repository_vulnerability_alert` | Contém atividades relacionadas a [{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts). -{%- ifversion fpt or ghec %} | `repository_vulnerability_alerts` | Contém atividades de configuração no nível do repositório em relação a {% data variables.product.prodname_dependabot_alerts %}. -| `required_status_check` | Contém atividades relacionadas às verificações de status obrigatórias em branches protegidos. -{%- endif %} {%- ifversion ghec or ghes %} | `restrict_notification_delivery` | Contém atividades relacionadas à restrição de notificações por email para domínios aprovados ou verificados em uma empresa. -{%- endif %} {%- ifversion custom-repository-roles %} | `role` | Contém atividades relacionadas a [funções de repositório personalizadas](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization). -{%- endif %} {%- ifversion ghec or ghes or ghae %} | `secret_scanning` | Contém atividades de configuração de nível da organização para a verificação de segredos em repositórios existentes. Para obter mais informações, confira "[Sobre a verificação de segredos](/github/administering-a-repository/about-secret-scanning)". -| `secret_scanning_new_repos` | Contém atividades de configuração de nível da organização para verificação de segredos para os repositórios criados na organização. -{%- endif %} {%- ifversion ghec or ghes or ghae %} | `security_key` | Contém atividades relacionadas ao registro e à remoção de chaves de segurança. -{%- endif %} {%- ifversion fpt or ghec %} | `sponsors` | Contém eventos relacionados a botões de patrocinador (confira "[Como exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)"). -{%- endif %} {%- ifversion ghec or ghes or ghae %} | `ssh_certificate_authority` | Contém atividades relacionadas a uma autoridade de certificação SSH em uma organização ou uma empresa. -| `ssh_certificate_requirement` | Contém atividades relacionadas ao requisito de que os membros usem certificados SSH para acessar recursos da organização. -{%- endif %} | `staff` | Contém atividades relacionadas a um administrador do site que executa uma ação. -| `team` | Contém atividades relacionadas às equipes em uma organização. -| `team_discussions` | Contém atividades relacionadas ao gerenciamento de discussões em equipe em uma organização. -{%- ifversion ghec %} | `team_sync_tenant` | Contém atividades relacionadas à sincronização de equipe com um IdP para uma empresa ou uma organização. -{%- endif %} {%- ifversion fpt or ghes %} | `two_factor_authentication` | Contém atividades relacionadas à autenticação de dois fatores. -{%- endif %} | `user` | Contém atividades relacionadas aos usuários em uma empresa ou organização. -{%- ifversion ghec or ghes %} | `user_license` | Contém atividades relacionadas a um usuário que ocupa uma estação licenciada e que é membro de uma empresa. -{%- endif %} | `workflows` | Contém atividades relacionadas a fluxos de trabalho do {% data variables.product.prodname_actions %}. +{%- ifversion fpt or ghec %} +| `account` | Contains activities related to an organization account. +| `advisory_credit` | Contains activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." +{%- endif %} +| `artifact` | Contains activities related to {% data variables.product.prodname_actions %} workflow run artifacts. +{%- ifversion audit-log-streaming %} +| `audit_log_streaming` | Contains activities related to streaming audit logs for organizations in an enterprise account. +{%- endif %} +{%- ifversion fpt or ghec %} +| `billing` | Contains activities related to an organization's billing. +{%- endif %} +{%- ifversion ghec or ghes or ghae %} +| `business` | Contains activities related to business settings for an enterprise. +{%- endif %} +{%- ifversion code-security-audit-log-events %} +| `business_advanced_security` | Contains activities related to {% data variables.product.prodname_GH_advanced_security %} in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_secret_scanning` | Contains activities related to {% data variables.product.prodname_secret_scanning %} in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +{%- endif %} +{%- ifversion secret-scanning-audit-log-custom-patterns %} +| `business_secret_scanning_custom_pattern` | Contains activities related to custom patterns for {% data variables.product.prodname_secret_scanning %} in an enterprise. +{%- endif %} +{%- ifversion code-security-audit-log-events %} +| `business_secret_scanning_push_protection` | Contains activities related to the push protection feature of {% data variables.product.prodname_secret_scanning %} in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_secret_scanning_push_protection_custom_message` | Contains activities related to the custom message displayed when push protection is triggered in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +{%- endif %} +| `checks` | Contains activities related to check suites and runs. +{%- ifversion fpt or ghec %} +| `codespaces` | Contains activities related to an organization's codespaces. +{%- endif %} +| `commit_comment` | Contains activities related to updating or deleting commit comments. +{%- ifversion ghes %} +| `config_entry` | Contains activities related to configuration settings. These events are only visible in the site admin audit log. +{%- endif %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} | +| `dependabot_alerts` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." +| `dependabot_alerts_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization. +| `dependabot_repository_access` | Contains activities related to which private repositories in an organization {% data variables.product.prodname_dependabot %} is allowed to access. +{%- endif %} +{%- ifversion fpt or ghec or ghes > 3.2 %} +| `dependabot_security_updates` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." +| `dependabot_security_updates_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization. +{%- endif %} +| `dependency_graph` | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." +| `dependency_graph_new_repos` | Contains organization-level configuration activities for new repositories created in the organization. +{%- ifversion fpt or ghec %} +| `discussion` | Contains activities related to team discussions. +| `discussion_comment` | Contains activities related to comments posted in discussions on a team page. +| `discussion_post` | Contains activities related to discussions posted to a team page. +| `discussion_post_reply` | Contains activities related to replies to discussions posted to a team page. +{%- endif %} +{%- ifversion ghec or ghes %} +| `dotcom_connection` | Contains activities related to {% data variables.product.prodname_github_connect %}. +| `enterprise` | Contains activities related to enterprise settings. +{%- endif %} +{%- ifversion ghec %} +| `enterprise_domain` | Contains activities related to verified enterprise domains. +| `enterprise_installation` | Contains activities related to {% data variables.product.prodname_github_app %}s associated with an {% data variables.product.prodname_github_connect %} enterprise connection. +{%- endif %} +{%- ifversion fpt or ghec %} +| `environment` | Contains activities related to {% data variables.product.prodname_actions %} environments. +{%- endif %} +{%- ifversion ghae %} +| `external_group` | Contains activities related to Okta groups. +| `external_identity` | Contains activities related to a user in an Okta group. +{%- endif %} +| `gist` | Contains activities related to Gists. +| `hook` | Contains activities related to webhooks. +| `integration` | Contains activities related to integrations in an account. +| `integration_installation` | Contains activities related to integrations installed in an account. +| `integration_installation_request` | Contains activities related to organization member requests for owners to approve integrations for use in the organization. +{%- ifversion ghec or ghae %} +| `ip_allow_list` | Contains activities related to enabling or disabling the IP allow list for an organization. +| `ip_allow_list_entry` | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization. +{%- endif %} +| `issue` | Contains activities related to pinning, transferring, or deleting an issue in a repository. +| `issue_comment` | Contains activities related to pinning, transferring, or deleting issue comments. +| `issues` | Contains activities related to enabling or disabling issue creation for an organization. +{%- ifversion fpt or ghec %} +| `marketplace_agreement_signature` | Contains activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement. +| `marketplace_listing` | Contains activities related to listing apps in {% data variables.product.prodname_marketplace %}. +{%- endif %} +| `members_can_create_pages` | Contains activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." +| `members_can_create_private_pages` | Contains activities related to managing the publication of private {% data variables.product.prodname_pages %} sites for repositories in the organization. +| `members_can_create_public_pages` | Contains activities related to managing the publication of public {% data variables.product.prodname_pages %} sites for repositories in the organization. +{%- ifversion ghec or ghes or ghae %} +| `members_can_delete_repos` | Contains activities related to enabling or disabling repository creation for an organization. +{%- endif %} +{%- ifversion fpt or ghec %} +| `members_can_view_dependency_insights` | Contains organization-level configuration activities allowing organization members to view dependency insights. +| `migration` | Contains activities related to transferring data from a *source* location (such as a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance. +{%- endif %} +| `oauth_access` | Contains activities related to OAuth access tokens. +| `oauth_application` | Contains activities related to OAuth Apps. +{%- ifversion fpt or ghec %} +| `oauth_authorization` | Contains activities related to authorizing OAuth Apps. +{%- endif %} +| `org` | Contains activities related to organization membership. +{%- ifversion ghec or ghes or ghae %} +| `org_credential_authorization` | Contains activities related to authorizing credentials for use with SAML single sign-on. +{%- endif %} +{%- ifversion secret-scanning-audit-log-custom-patterns %} +| `org_secret_scanning_custom_pattern` | Contains activities related to custom patterns for secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." +| `org.secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in an organization. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." +{%- endif %} +| `organization_default_label` | Contains activities related to default labels for repositories in an organization. +{%- ifversion fpt or ghec or ghes %} +| `organization_domain` | Contains activities related to verified organization domains. +| `organization_projects_change` | Contains activities related to organization-wide project boards in an enterprise. +{%- endif %} +{%- ifversion fpt or ghec %} +| `pages_protected_domain` | Contains activities related to verified custom domains for {% data variables.product.prodname_pages %}. +| `payment_method` | Contains activities related to how an organization pays for {% data variables.product.prodname_dotcom %}. +| `prebuild_configuration` | Contains activities related to prebuild configurations for {% data variables.product.prodname_github_codespaces %}. +{%- endif %} +{%- ifversion ghes %} +| `pre_receive_environment` | Contains activities related to pre-receive hook environments. +| `pre_receive_hook` | Contains activities related to pre-receive hooks. +{%- endif %} +{%- ifversion ghes %} +| `private_instance_encryption` | Contains activities related to enabling private mode for an enterprise. +{%- endif %} +| `private_repository_forking` | Contains activities related to allowing forks of private and internal repositories, for a repository, organization or enterprise. +{%- ifversion fpt or ghec %} +| `profile_picture` | Contains activities related to an organization's profile picture. +{%- endif %} +| `project` | Contains activities related to project boards. +| `project_field` | Contains activities related to field creation and deletion in a project board. +| `project_view` | Contains activities related to view creation and deletion in a project board. +| `protected_branch` | Contains activities related to protected branches. +| `public_key` | Contains activities related to SSH keys and deploy keys. +| `pull_request` | Contains activities related to pull requests. +| `pull_request_review` | Contains activities related to pull request reviews. +| `pull_request_review_comment` | Contains activities related to pull request review comments. +| `repo` | Contains activities related to the repositories owned by an organization. +{%- ifversion fpt or ghec %} +| `repository_advisory` | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." +| `repository_content_analysis` | Contains activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data). +| `repository_dependency_graph` | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." +{%- endif %} +| `repository_image` | Contains activities related to images for a repository. +| `repository_invitation` | Contains activities related to invitations to join a repository. +| `repository_projects_change` | Contains activities related to enabling projects for a repository or for all repositories in an organization. +{%- ifversion ghec or ghes or ghae %} +| `repository_secret_scanning` | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." +{%- endif %} +{%- ifversion secret-scanning-audit-log-custom-patterns %} +| `repository_secret_scanning_custom_pattern` | Contains activities related to secret scanning custom patterns in a repository. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %} +| `repository_secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." +{%- endif %} +{%- ifversion fpt or ghec %} +| `repository_visibility_change` | Contains activities related to allowing organization members to change repository visibilities for the organization. +{%- endif %} +| `repository_vulnerability_alert` | Contains activities related to [{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts). +{%- ifversion fpt or ghec %} +| `repository_vulnerability_alerts` | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}. +| `required_status_check` | Contains activities related to required status checks for protected branches. +{%- endif %} +{%- ifversion ghec or ghes %} +| `restrict_notification_delivery` | Contains activities related to the restriction of email notifications to approved or verified domains for an enterprise. +{%- endif %} +{%- ifversion custom-repository-roles %} +| `role` | Contains activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization). +{%- endif %} +{%- ifversion ghec or ghes or ghae %} +| `secret_scanning` | Contains organization-level configuration activities for secret scanning in existing repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." +| `secret_scanning_new_repos` | Contains organization-level configuration activities for secret scanning for new repositories created in the organization. +{%- endif %} +{%- ifversion ghec or ghes or ghae %} +| `security_key` | Contains activities related to security keys registration and removal. +{%- endif %} +{%- ifversion fpt or ghec %} +| `sponsors` | Contains events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"). +{%- endif %} +{%- ifversion ghec or ghes or ghae %} +| `ssh_certificate_authority` | Contains activities related to a SSH certificate authority in an organization or enterprise. +| `ssh_certificate_requirement` | Contains activities related to requiring members use SSH certificates to access organization resources. +{%- endif %} +| `staff` | Contains activities related to a site admin performing an action. +| `team` | Contains activities related to teams in an organization. +| `team_discussions` | Contains activities related to managing team discussions for an organization. +{%- ifversion ghec %} +| `team_sync_tenant` | Contains activities related to team synchronization with an IdP for an enterprise or organization. +{%- endif %} +{%- ifversion fpt or ghes %} +| `two_factor_authentication` | Contains activities related to two-factor authentication. +{%- endif %} +| `user` | Contains activities related to users in an enterprise or organization. +{%- ifversion ghec or ghes %} +| `user_license` | Contains activities related to a user occupying a licensed seat in, and being a member of, an enterprise. +{%- endif %} +| `workflows` | Contains activities related to {% data variables.product.prodname_actions %} workflows. diff --git a/translations/pt-BR/data/reusables/branches/new-repo-default-branch.md b/translations/pt-BR/data/reusables/branches/new-repo-default-branch.md index a42ff27dbc..17f774ac0d 100644 --- a/translations/pt-BR/data/reusables/branches/new-repo-default-branch.md +++ b/translations/pt-BR/data/reusables/branches/new-repo-default-branch.md @@ -1,10 +1,2 @@ ---- -ms.openlocfilehash: 9cc8fc34ada2e8d2831de2f62005f139ebcc7cfe -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145094765" ---- -Ao criar um repositório com conteúdo em {% data variables.product.product_location %}, {% data variables.product.product_name %} cria o repositório com um único branch. Este primeiro branch no repositório é o branch-padrão. +When you create a repository with content on {% data variables.location.product_location %}, {% data variables.product.product_name %} creates the repository with a single branch. This first branch in the repository is the default branch. diff --git a/translations/pt-BR/data/reusables/classroom/about-autograding.md b/translations/pt-BR/data/reusables/classroom/about-autograding.md index c1230e0027..29cde59f64 100644 --- a/translations/pt-BR/data/reusables/classroom/about-autograding.md +++ b/translations/pt-BR/data/reusables/classroom/about-autograding.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 861671360dc3718c5d796e9d07924952e221cbb7 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145094194" ---- -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. +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.location.product_location %}. The student can view the test results, make changes, and push to see new results. diff --git a/translations/pt-BR/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md b/translations/pt-BR/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md index 74516286f8..9a06bcca8f 100644 --- a/translations/pt-BR/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md +++ b/translations/pt-BR/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 4a60a2f573a8aebe309f1db397e38cd41ef8eeac -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145094127" ---- -Você pode executar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_name %} usando {% data variables.product.prodname_actions %}. Como alternativa, se você usar um sistema de integração contínua ou um sistema de entrega/Continuous Delivery (CI/CD) de terceiros você poderá executar a análise {% data variables.product.prodname_codeql %} no seu sistema existente e enviar os resultados para {% data variables.product.product_location %}. +You can run {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %} using {% data variables.product.prodname_actions %}. Alternatively, if you use a third-party continuous integration or continuous delivery/deployment (CI/CD) system, you can run {% data variables.product.prodname_codeql %} analysis in your existing system and upload the results to {% data variables.location.product_location %}. diff --git a/translations/pt-BR/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md b/translations/pt-BR/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md index 298b822d14..df8cfa6027 100644 --- a/translations/pt-BR/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md +++ b/translations/pt-BR/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md @@ -1,16 +1,8 @@ ---- -ms.openlocfilehash: e28e49974140b810496d7ca2af2d8ac07d30b754 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145094118" ---- {% ifversion ghes %} {% note %} -**Observação:** o administrador do site precisa habilitar a {% data variables.product.prodname_code_scanning %} para o {% data variables.product.product_location %} para que você possa usar esse recurso. Se você desejar usar o {% data variables.product.prodname_actions %} para fazer a varredura do seu código, o administrador do site também deverá habilitar o {% data variables.product.prodname_actions %} e configurar a infraestrutura necessária. Para obter mais informações, confira "[Como configurar a {% data variables.product.prodname_code_scanning %} para seu dispositivo](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance)".1 +**Note:** Your site administrator must enable {% data variables.product.prodname_code_scanning %} for {% data variables.location.product_location %} before you can use this feature. If you want to use {% data variables.product.prodname_actions %} to scan your code, the site administrator must also enable {% data variables.product.prodname_actions %} and set up the infrastructure required. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance)." {% endnote %} diff --git a/translations/pt-BR/data/reusables/code-scanning/enterprise-enable-code-scanning.md b/translations/pt-BR/data/reusables/code-scanning/enterprise-enable-code-scanning.md index 0216539bcb..700cd26b27 100644 --- a/translations/pt-BR/data/reusables/code-scanning/enterprise-enable-code-scanning.md +++ b/translations/pt-BR/data/reusables/code-scanning/enterprise-enable-code-scanning.md @@ -2,7 +2,7 @@ {% note %} -**Note:** Your site administrator must enable {% data variables.product.prodname_code_scanning %} for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance)." +**Note:** Your site administrator must enable {% data variables.product.prodname_code_scanning %} for {% data variables.location.product_location %} before you can use this feature. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance)." {% ifversion security-feature-enablement-policies %} You may not be able to enable or disable {% data variables.product.prodname_code_scanning %} if an enterprise owner has set a policy at the enterprise level. For more information, see "[Enforcing policies for code security and analysis for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise)."{% endif %} diff --git a/translations/pt-BR/data/reusables/code-scanning/what-is-codeql-cli.md b/translations/pt-BR/data/reusables/code-scanning/what-is-codeql-cli.md index e848cb90a0..2d4e1c65b1 100644 --- a/translations/pt-BR/data/reusables/code-scanning/what-is-codeql-cli.md +++ b/translations/pt-BR/data/reusables/code-scanning/what-is-codeql-cli.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: ec454deef6771dc385435a4148e5e095acfc1659 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145094671" ---- -O {% data variables.product.prodname_codeql_cli %} é um produto inependente que você pode usar para analisar o código. Seu principal propósito é gerar uma representação do banco de dados de uma base de código, um banco de dados de {% data variables.product.prodname_codeql %}. Assim que o banco de dados estiver pronto, você poderá consultá-lo interativamente, ou executar um conjunto de consultas para gerar um conjunto de resultados no formato SARIF e fazer o upload dos resultados para {% data variables.product.product_location %}. +The {% data variables.product.prodname_codeql_cli %} is a standalone product that you can use to analyze code. Its main purpose is to generate a database representation of a codebase, a {% data variables.product.prodname_codeql %} database. Once the database is ready, you can query it interactively, or run a suite of queries to generate a set of results in SARIF format and upload the results to {% data variables.location.product_location %}. diff --git a/translations/pt-BR/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/translations/pt-BR/data/reusables/codespaces/creating-a-codespace-in-vscode.md index 545324000c..1039481541 100644 --- a/translations/pt-BR/data/reusables/codespaces/creating-a-codespace-in-vscode.md +++ b/translations/pt-BR/data/reusables/codespaces/creating-a-codespace-in-vscode.md @@ -1,4 +1,4 @@ -After you connect your account on {% data variables.product.product_location %} to the {% data variables.product.prodname_github_codespaces %} extension, you can create a new codespace. For more information about the {% data variables.product.prodname_github_codespaces %} extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). +After you connect your account on {% data variables.location.product_location %} to the {% data variables.product.prodname_github_codespaces %} extension, you can create a new codespace. For more information about the {% data variables.product.prodname_github_codespaces %} extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 2. Click the Add icon: {% octicon "plus" aria-label="The plus icon" %}. diff --git a/translations/pt-BR/data/reusables/command_line/provide-an-access-token.md b/translations/pt-BR/data/reusables/command_line/provide-an-access-token.md index d3e26b5231..f2a89e69b4 100644 --- a/translations/pt-BR/data/reusables/command_line/provide-an-access-token.md +++ b/translations/pt-BR/data/reusables/command_line/provide-an-access-token.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 0eae1b9c546c076ca089090e61080750f91e9dce -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145127899" ---- -{% ifversion fpt or ghec %}Se você estiver acessando uma organização que usa o SSO do SAML, também precisará autorizar seu token de acesso pessoal a acessar a organização antes de se autenticar. Para obter mais informações, confira "[Sobre a autenticação com o logon único do SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" e "[Como autorizar um token de acesso pessoal para uso com o logon único do SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)".{% endif %} +{% ifversion fpt or ghec %}If you are accessing an organization that uses SAML SSO{% ifversion pat-v2%} and you are using a {% data variables.product.pat_v1 %}{% endif %}, you must also authorize your {% data variables.product.pat_generic %} to access the organization before you authenticate. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" and "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."{% endif %} diff --git a/translations/pt-BR/data/reusables/copilot/install-copilot-in-neovim.md b/translations/pt-BR/data/reusables/copilot/install-copilot-in-neovim.md index 4b785ba40b..4b10c8048b 100644 --- a/translations/pt-BR/data/reusables/copilot/install-copilot-in-neovim.md +++ b/translations/pt-BR/data/reusables/copilot/install-copilot-in-neovim.md @@ -1,10 +1 @@ ---- -ms.openlocfilehash: 1c960bafd80111c73d0bea364cd39e5d68778deb -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147079600" ---- -1. Para usar o {% data variables.product.prodname_copilot %} no Neovim, instale o plug-in do {% data variables.product.prodname_copilot %}. Você pode instalar o plug-in usando um gerenciador de plug-ins ou diretamente. - - Se você usa um gerenciador de plug-ins, como vim-plug ou packer.nvim, use-o para instalar o `github/copilot.vim`. Para obter mais informações, confira a documentação do gerenciador de plug-ins. Por exemplo, veja a documentação do [vim-plug](https://github.com/junegunn/vim-plug) ou do [packer.nvim](https://github.com/wbthomason/packer.nvim). +1. {% data variables.product.prodname_dotcom %} recommends that you install the {% data variables.product.prodname_copilot %} plugin with Neovim's built-in plugin manager. Alternatively, you can use a plugin manager of your choice to install `github/copilot.vim`. diff --git a/translations/pt-BR/data/reusables/dependabot/enterprise-enable-dependabot.md b/translations/pt-BR/data/reusables/dependabot/enterprise-enable-dependabot.md index a74ef3620a..844b35d9ea 100644 --- a/translations/pt-BR/data/reusables/dependabot/enterprise-enable-dependabot.md +++ b/translations/pt-BR/data/reusables/dependabot/enterprise-enable-dependabot.md @@ -2,7 +2,7 @@ {% note %} -**Note:** Your site administrator must set up {% data variables.product.prodname_dependabot_updates %} for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." +**Note:** Your site administrator must set up {% data variables.product.prodname_dependabot_updates %} for {% data variables.location.product_location %} before you can use this feature. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% ifversion security-feature-enablement-policies %} You may not be able to enable or disable {% data variables.product.prodname_dependabot_updates %} if an enterprise owner has set a policy at the enterprise level. For more information, see "[Enforcing policies for code security and analysis for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise)."{% endif %} diff --git a/translations/pt-BR/data/reusables/desktop/get-an-account.md b/translations/pt-BR/data/reusables/desktop/get-an-account.md index 6185468d31..545cc0f5b9 100644 --- a/translations/pt-BR/data/reusables/desktop/get-an-account.md +++ b/translations/pt-BR/data/reusables/desktop/get-an-account.md @@ -1,12 +1,4 @@ ---- -ms.openlocfilehash: 41049556184008283745fe15886e9667774ec424 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145127727" ---- -você já precisa ter uma conta no {% data variables.product.product_location %}. +you must already have an account on {% data variables.location.product_location %}. -- Para obter mais informações sobre como criar uma conta no {% data variables.product.product_location %}, confira "[Como se inscrever em uma nova conta do {% data variables.product.prodname_dotcom %}](/articles/signing-up-for-a-new-github-account/)". -- Para uma conta do {% data variables.product.prodname_enterprise %}, entre em contato com o administrador do site do {% data variables.product.prodname_enterprise %}. +- For more information on creating an account on {% data variables.location.product_location %} account, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account/)". +- For a {% data variables.product.prodname_enterprise %} account, contact your {% data variables.product.prodname_enterprise %} site administrator. diff --git a/translations/pt-BR/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md b/translations/pt-BR/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md index f4ccbbe728..e80cf9e28e 100644 --- a/translations/pt-BR/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md +++ b/translations/pt-BR/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md @@ -1,15 +1,8 @@ ---- -ms.openlocfilehash: f3a872ceadabe044524f906f9c713c2682e0ab88 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145127642" ---- -1. No {% data variables.product.product_location %}, navegue até a página principal da organização. -1. No nome da sua organização, clique em {% octicon "gear" aria-label="The gear icon" %} **Configurações**. -![Botão de configurações da organização](/assets/images/help/discussions/org-settings.png) -1. Em "Discussões", selecione **Habilitar discussões para esta organização**. -1. Selecione um repositório a ser usado como repositório de origem para as discussões da sua organização. - ![Configurações para habilitar discussões para uma organização](/assets/images/help/discussions/enable-org-discussions.png) -1. Clique em **Save** (Salvar). +1. On {% data variables.location.product_location %}, navigate to the main page of your organization. +1. Under your organization name, click {% octicon "gear" aria-label="The gear icon" %} +**Settings**. +![Organization settings button](/assets/images/help/discussions/org-settings.png) +1. Under "Discussions", select **Enable discussions for this organization**. +1. Select a repository to use as the source repository for your organization discussions. + ![Settings to enable discussions for an organization](/assets/images/help/discussions/enable-org-discussions.png) +1. Click **Save**. diff --git a/translations/pt-BR/data/reusables/discussions/navigate-to-repo-or-org.md b/translations/pt-BR/data/reusables/discussions/navigate-to-repo-or-org.md index 654768dfd8..17ca81827c 100644 --- a/translations/pt-BR/data/reusables/discussions/navigate-to-repo-or-org.md +++ b/translations/pt-BR/data/reusables/discussions/navigate-to-repo-or-org.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 5d42e411b239f760ca058d6082557918f9fe9eee -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145127638" ---- -1. No {% data variables.product.product_location %}, navegue até a página principal do repositório ou da organização. +1. On {% data variables.location.product_location %}, navigate to the main page of the repository or organization. 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 547f556293..fb8a039155 100644 --- a/translations/pt-BR/data/reusables/discussions/starting-a-discussion.md +++ b/translations/pt-BR/data/reusables/discussions/starting-a-discussion.md @@ -1,18 +1,10 @@ ---- -ms.openlocfilehash: 4a1af9bdfa8fa3b86b2d64706d24a9dd1d33fd6f -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145127627" ---- -1. No {% data variables.product.product_location %}, navegue até a página principal do repositório ou organização em que você deseja iniciar uma discussão. +1. On {% data variables.location.product_location %}, navigate to the main page of the repository or organization where you want to start a discussion. {% data reusables.discussions.discussions-tab %} -1. Clique em **Nova discussão**. - ![Botão "Nova discussão" na guia "Discussões" de um repositório](/assets/images/help/discussions/new-discussion-button.png) -1. Escolha o menu suspenso **Selecionar Categoria** e clique em uma categoria para ver a discussão. - ![Menu suspenso "Selecionar Categoria" e lista de categorias disponíveis em um 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 o corpo 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) +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) diff --git a/translations/pt-BR/data/reusables/dotcom_billing/view-all-subscriptions.md b/translations/pt-BR/data/reusables/dotcom_billing/view-all-subscriptions.md index 37203943b9..8403ca7ead 100644 --- a/translations/pt-BR/data/reusables/dotcom_billing/view-all-subscriptions.md +++ b/translations/pt-BR/data/reusables/dotcom_billing/view-all-subscriptions.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 24174465a9f462c750d0d51635133501fd1174ce -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145096880" ---- -Para ver todas as assinaturas da sua conta do {% data variables.product.product_location %}, confira "[Como ver suas assinaturas e a data de cobrança](/articles/viewing-your-subscriptions-and-billing-date)". +To view all the subscriptions for your account on {% data variables.location.product_location %}, see "[Viewing your subscriptions and billing date](/articles/viewing-your-subscriptions-and-billing-date)." diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/dormant-user-activity.md b/translations/pt-BR/data/reusables/enterprise-accounts/dormant-user-activity.md index d7dbdc883f..80878d1726 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/dormant-user-activity.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/dormant-user-activity.md @@ -1,31 +1,23 @@ ---- -ms.openlocfilehash: f89c8ea56df60e14b5735d160104d332ff1e804b -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "146680978" ---- -Um usuário será considerado ativo se o usuário tiver realizado qualquer uma das atividades a seguir em {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. +A user is considered active if the user has performed any of the following activities on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. -- Como entrar em {% data variables.product.product_location %} -- Criar um repositório -- Como enviar por push para um repositório -- Como ser adicionado a um repositório -- Como alterar a visibilidade de um repositório -- Criar um problema ou um pull request -- Como fazer comentários sobre um problema ou solicitação de pull -- Como fechar ou reabrir um problema ou solicitação de pull -- Como aplicar um rótulo a um problema ou uma solicitação de pull ou remover um rótulo -- Como atribuir ou cancelar a atribuição de um problema ou solicitação de pull -- Como solicitar uma revisão de uma solicitação de pull ou remover uma solicitação de revisão -- Como criar ou editar um comentário em uma revisão de solicitação de pull -- Como ignorar um comentário em uma solicitação de pull -- Como sincronizar uma solicitação de pull -- Como comentar uma confirmação -- Como publicar uma versão -- Como enviar por push para um wiki -- Inspecionar um repositório -- Favoritando um repositório -- Excluir um repositório -- Como acessar recursos usando um token de acesso pessoal ou uma chave SSH +- Signing into {% data variables.location.product_location %} +- Creating a repository +- Pushing to a repository +- Being added to a repository +- Changing the visibility of a repository +- Creating an issue or pull request +- Commenting on an issue or pull request +- Closing or reopening an issue or pull request +- Applying a label to an issue or pull request, or removing a label +- Assigning or unassigning an issue or pull request +- Requesting a review of a pull request, or removing a review request +- Creating or editing a comment in a pull request review +- Dismissing a comment in a pull request +- Synchronizing a pull request +- Commenting on a commit +- Publishing a release +- Pushing to a wiki +- Watching a repository +- Starring a repository +- Deleting a repository +- Accessing resources by using a {% data variables.product.pat_generic %} or SSH key diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-cap-validates.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-cap-validates.md index c6d4974bd4..f362c9b0ab 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/emu-cap-validates.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-cap-validates.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 583dd6201d170a08509a815a61c854c411e4938f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147067863" ---- -Quando sua empresa usa o SSO do OIDC, {% data variables.product.prodname_dotcom %} usará automaticamente as condições de IP de CAP (política de acesso condicional) do IdP para validar as interações do usuário com o {% data variables.product.prodname_dotcom %}, quando os membros alterarem endereços IP e cada vez que um token de acesso pessoal ou uma chave SSH for usada. +When your enterprise uses OIDC SSO, {% data variables.product.prodname_dotcom %} will automatically use your IdP's conditional access policy (CAP) IP conditions to validate user interactions with {% data variables.product.prodname_dotcom %}, when members change IP addresses, and each time a {% data variables.product.pat_generic %} or SSH key is used. diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-forks.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-forks.md index ab39fc5b3f..f78720f3bc 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/emu-forks.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-forks.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 559e156a8e9660bf4a720567d579eccc032c5573 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145097266" ---- -O {% data variables.product.prodname_managed_users_caps %} não pode criar forks de repositórios fora da empresa nem de repositórios internos. O {% data variables.product.prodname_managed_users_caps %} pode criar forks de repositórios privados pertencentes às organizações da empresa em outras organizações pertencentes à empresa ou como um fork pertencente ao {% data variables.product.prodname_managed_user %}. +{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise or fork internal repositories. {% data variables.enterprise.prodname_managed_users_caps %} can fork private repositories owned by organizations in the enterprise into other organizations owned by the enterprise, or as a fork owned by the {% data variables.enterprise.prodname_managed_user %}. diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-follow.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-follow.md index 17622f7fa9..a27bed899e 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-follow.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-follow.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: e49bce0aba4ff19dac4d6e1910be7301618c8640 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145066043" ---- -{% ifversion ghec %} Os membros de um {% data variables.product.prodname_emu_enterprise %} só podem seguir outros membros da respectiva empresa. {% endif %} +{% ifversion ghec %} Members of an {% data variables.enterprise.prodname_emu_enterprise %} can only follow other members of their enterprise. {% endif %} diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-fork.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-fork.md index 86ef1a1e6b..c3bf0cb89e 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-fork.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-fork.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: e9c13cc91ec4d3ab498ad3d826e59c17f6881619 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145066042" ---- -{% ifversion ghec %}Os membros de um {% data variables.product.prodname_emu_enterprise %} não podem criar forks de repositórios fora da empresa nem de repositórios internos.{% endif %} +{% ifversion ghec %}Members of an {% data variables.enterprise.prodname_emu_enterprise %} cannot fork repositories from outside of the enterprise or fork internal repositories.{% endif %} diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-gist.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-gist.md index 0862f1abf6..5093627199 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-gist.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-gist.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 4bf5ce9ef547b95c4f5ef6c4a9ff71ed553aa4b5 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145066036" ---- -{% ifversion ghec %}Os membros de um {% data variables.product.prodname_emu_enterprise %} não podem criar gists e ter acesso somente leitura nos gists.{% endif %} +{% ifversion ghec %}Members of an {% data variables.enterprise.prodname_emu_enterprise %} cannot create gists and have read-only access to gists.{% endif %} diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-interact.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-interact.md index ecddb9969f..b2162ba7e2 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-interact.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-interact.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 7311dd81bdd55f580a1173cac98382c66fc7e86e -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145066031" ---- -{% ifversion ghec %} Os membros de um {% data variables.product.prodname_emu_enterprise %} só podem interagir com os repositórios da respectiva empresa. {% endif %} +{% ifversion ghec %} Members of an {% data variables.enterprise.prodname_emu_enterprise %} can only interact with repositories within their enterprise. {% endif %} diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-propose.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-propose.md index 40708fed1d..2c473bfaa3 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-propose.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-propose.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 83895ddc4e2fc636d89d9715fee0d8890a3acfb6 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145066030" ---- -{% ifversion ghec %} Os membros de um {% data variables.product.prodname_emu_enterprise %} só podem propor alterações nos repositórios que fazem parte da respectiva empresa. {% endif %} +{% ifversion ghec %} Members of an {% data variables.enterprise.prodname_emu_enterprise %} can only propose changes in repositories that are part of their enterprise. {% endif %} diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-repo.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-repo.md index 149e03cf20..4112f4ef25 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-repo.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-repo.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 8d1b7b8fcff29aeef03dce23e62448db69266940 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145066029" ---- -{% ifversion ghec %} Os membros de um {% data variables.product.prodname_emu_enterprise %} só podem fazer alterações nos repositórios que fazem parte da respectiva empresa. {% endif %} +{% ifversion ghec %} Members of an {% data variables.enterprise.prodname_emu_enterprise %} can only make changes in repositories that are part of their enterprise. {% endif %} diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-short-summary.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-short-summary.md index c307057e3d..c80082fe07 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/emu-short-summary.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-short-summary.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 57efd141644710352395659515a7215b723055f0 -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147875636" ---- -Os {% data variables.product.prodname_emus %} são um recurso do {% data variables.product.prodname_ghe_cloud %} que fornece um controle ainda maior sobre os membros e os recursos corporativos. Com os {% data variables.product.prodname_emus %}, todos os membros são provisionados e gerenciados por meio do seu IdP (provedor de identidade) em vez de os usuários criarem as respectivas contas no {% data variables.product.product_name %}. A associação a uma equipe pode ser gerenciada usando grupos no IdP. Os {% data variables.product.prodname_managed_users_caps %} são restritos à empresa e não podem efetuar push de código, colaborar nem interagir com usuários, repositórios e organizações fora da respectiva empresa. Para obter mais informações, confira "[Sobre os {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion not ghec %}" na documentação do {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %} +{% data variables.product.prodname_emus %} is a feature of {% data variables.product.prodname_ghe_cloud %} that provides even greater control over enterprise members and resources. With {% data variables.product.prodname_emus %}, all members are provisioned and managed through your identity provider (IdP) instead of users creating their own accounts on {% data variables.product.product_name %}. Team membership can be managed using groups on your IdP. {% data variables.enterprise.prodname_managed_users_caps %} are restricted to their enterprise and are unable to push code, collaborate, or interact with users, repositories, and organizations outside of their enterprise. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/oidc-gei-warning.md b/translations/pt-BR/data/reusables/enterprise-accounts/oidc-gei-warning.md index 2243e08c22..5ec0d137b6 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/oidc-gei-warning.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/oidc-gei-warning.md @@ -1,13 +1,5 @@ ---- -ms.openlocfilehash: ca435f630177ca47e4e7f733a7219a7c00a36292 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147066791" ---- {% warning %} -**Aviso:** se você usar o {% data variables.product.prodname_importer_proper_name %} para migrar uma organização do {% data variables.product.product_location_enterprise %}, use uma conta de serviço isenta do CAP do Azure AD, caso contrário, a migração poderá ser bloqueada. +**Warning:** If you use {% data variables.product.prodname_importer_proper_name %} to migrate an organization from {% data variables.location.product_location_enterprise %}, make sure to use a service account that is exempt from Azure AD's CAP otherwise your migration may be blocked. {% endwarning %} diff --git a/translations/pt-BR/data/reusables/enterprise/apply-configuration.md b/translations/pt-BR/data/reusables/enterprise/apply-configuration.md index 416ae9f105..7af7ba5163 100644 --- a/translations/pt-BR/data/reusables/enterprise/apply-configuration.md +++ b/translations/pt-BR/data/reusables/enterprise/apply-configuration.md @@ -1,20 +1,12 @@ ---- -ms.openlocfilehash: a7fec31cb255bd626918fd4bf9a2337debb259ae -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147883251" ---- -1. Para aplicar a configuração, digite o comando a seguir. +1. To apply the configuration, enter the following command. {% note %} - **Observação**: durante uma execução de configuração, os serviços em {% data variables.product.product_location %} podem ser reiniciados, o que pode causar um breve tempo de inatividade para os usuários. + **Note**: During a configuration run, services on {% data variables.location.product_location %} may restart, which can cause brief downtime for users. {% endnote %} ```shell ghe-config-apply ``` -1. Aguarde a conclusão da execução de suas configurações. +1. Wait for the configuration run to complete. diff --git a/translations/pt-BR/data/reusables/enterprise/rate_limit.md b/translations/pt-BR/data/reusables/enterprise/rate_limit.md index c9c49883ae..e6863783bd 100644 --- a/translations/pt-BR/data/reusables/enterprise/rate_limit.md +++ b/translations/pt-BR/data/reusables/enterprise/rate_limit.md @@ -1,16 +1,8 @@ ---- -ms.openlocfilehash: 9c3f4f2a11f84313dc59d7b42db0e5da7f947753 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145093776" ---- {% ifversion ghes %} {% note %} -**Observação**: os limites de taxa a seguir são os limites de taxa padrão do {% data variables.product.product_name %}. Entre em contato com o administrador do site para confirmar os limites de taxa do {% data variables.product.product_location %}. +**Note**: The following rate limits are the default rate limits for {% data variables.product.product_name %}. Contact your site administrator to confirm the rate limits for {% data variables.location.product_location %}. {% endnote %} diff --git a/translations/pt-BR/data/reusables/enterprise/test-in-staging.md b/translations/pt-BR/data/reusables/enterprise/test-in-staging.md index e21b1eba8e..43fe854c49 100644 --- a/translations/pt-BR/data/reusables/enterprise/test-in-staging.md +++ b/translations/pt-BR/data/reusables/enterprise/test-in-staging.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: a852bf18992b237fa442a0d24363787b1cf22a64 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145093773" ---- -O {% data variables.product.company_short %} recomenda fortemente que você verifique novas configurações para autenticação em um ambiente de preparo. Uma configuração incorreta poderá resultar em tempo de inatividade no {% data variables.product.product_location %}. Para obter mais informações, confira "[Como configurar uma instância de preparo](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)". +{% data variables.product.company_short %} strongly recommends that you verify any new configuration for authentication in a staging environment. An incorrect configuration could result in downtime for {% data variables.location.product_location %}. For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)." diff --git a/translations/pt-BR/data/reusables/enterprise_enterprise_support/installing-releases.md b/translations/pt-BR/data/reusables/enterprise_enterprise_support/installing-releases.md index 142eefc78c..444818f8fe 100644 --- a/translations/pt-BR/data/reusables/enterprise_enterprise_support/installing-releases.md +++ b/translations/pt-BR/data/reusables/enterprise_enterprise_support/installing-releases.md @@ -2,6 +2,6 @@ ## Installing {% data variables.product.prodname_ghe_server %} releases -To ensure that {% data variables.product.product_location %} is stable, you must install and implement {% data variables.product.prodname_ghe_server %} releases. Installing {% data variables.product.prodname_ghe_server %} releases ensures that you have the latest features, modifications, and enhancements as well as any updates to features, code corrections, patches or other general updates and fixes to {% data variables.product.prodname_ghe_server %}. +To ensure that {% data variables.location.product_location %} is stable, you must install and implement {% data variables.product.prodname_ghe_server %} releases. Installing {% data variables.product.prodname_ghe_server %} releases ensures that you have the latest features, modifications, and enhancements as well as any updates to features, code corrections, patches or other general updates and fixes to {% data variables.product.prodname_ghe_server %}. {% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise_installation/download-package.md b/translations/pt-BR/data/reusables/enterprise_installation/download-package.md index b27868922a..6dd8199681 100644 --- a/translations/pt-BR/data/reusables/enterprise_installation/download-package.md +++ b/translations/pt-BR/data/reusables/enterprise_installation/download-package.md @@ -1,12 +1,4 @@ ---- -ms.openlocfilehash: 0aa4c7abc78f6d80d30aeb21763b404b98d87301 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147883801" ---- -1. Baixe o pacote de atualização para o {% data variables.product.product_location %} usando `curl `: +1. Download the upgrade package to {% data variables.location.product_location %} using `curl `: ```shell -admin@HOSTNAME:~$ curl -L -O UPGRADE-PKG-URL +admin@HOSTNAME:~$ curl -L -O UPGRADE-PKG-URL ``` 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 21cefb0027..1d514c4aae 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,18 +1,10 @@ ---- -ms.openlocfilehash: 7de065c9dec15e3b92cabf5d3fa711c7d88249ba -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147882784" ---- -- [Requisitos mínimos](#minimum-requirements) +- [Minimum requirements](#minimum-requirements) - [Storage](#storage) -- [CPU e memória](#cpu-and-memory) +- [CPU and memory](#cpu-and-memory) -### Requisitos mínimos +### Minimum requirements -Recomendamos diferentes configurações de hardware dependendo do número de licenças de usuário do {% 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. +We recommend different hardware configurations depending on the number of user licenses for {% data variables.location.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 %} @@ -20,27 +12,27 @@ Recomendamos diferentes configurações de hardware dependendo do número de lic {% data reusables.enterprise_installation.about-adjusting-resources %} -### Armazenamento +### Storage -Recomendamos um SSD de alto desempenho com operações de alta entrada/saída por segundo (IOPS) e baixa latência para {% data variables.product.prodname_ghe_server %}. Cargas de trabalho são intensivas em I/O. Se você usar um hipervisor de metal simples, recomendamos anexar diretamente o disco ou usar um disco a partir de uma rede de área de armazenamento (SAN). +We recommend a high-performance SSD with high input/output operations per second (IOPS) and low latency for {% data variables.product.prodname_ghe_server %}. Workloads are I/O intensive. If you use a bare metal hypervisor, we recommend directly attaching the disk or using a disk from a storage area network (SAN). -A sua instância exige um disco de dados persistente separado do disco raiz. Para obter mais informações, confira "[ Visão geral do sistema](/enterprise/admin/guides/installation/system-overview)". +Your instance requires a persistent data disk separate from the root disk. For more information, see "[System overview](/enterprise/admin/guides/installation/system-overview)." {% ifversion ghes %} -Para configurar o {% data variables.product.prodname_actions %}, você precisa fornecer um armazenamento de blobs externo. Para obter mais informações, confira "[Introdução ao {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server##external-storage-requirements)". +To configure {% 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##external-storage-requirements)." {% endif %} -O espaço disponível no sistema de arquivos raiz será 50% do tamanho total do disco. Você pode redimensionar o disco raiz da sua instância criando uma nova instância ou usando uma instância existente. Para obter mais informações, confira "[Visão geral do sistema](/enterprise/admin/guides/installation/system-overview#storage-architecture)" e "[Como aumentar a capacidade de armazenamento](/enterprise/admin/guides/installation/increasing-storage-capacity)". +The available space on the root filesystem will be 50% of the total disk size. You can resize your instance's root disk by building a new instance or using an existing instance. For more information, see "[System overview](/enterprise/admin/guides/installation/system-overview#storage-architecture)" and "[Increasing storage capacity](/enterprise/admin/guides/installation/increasing-storage-capacity)." -### CPU e memória +### CPU and memory -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. +The CPU and memory resources that {% data variables.product.prodname_ghe_server %} requires depend on the levels of activity for users, automations, and integrations. {% ifversion ghes %} -Se você pretende habilitar o {% data variables.product.prodname_actions %} para os usuários da sua instância do {% data variables.product.prodname_ghe_server %}, talvez seja necessário provisionar recursos adicionais de CPU e memória para a instância. Para obter mais informações, confira "[Introdução ao {% 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)". +If you plan to enable {% data variables.product.prodname_actions %} for the users of your {% data variables.product.prodname_ghe_server %} instance, you may need to provision additional CPU and memory resources for your instance. 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)." {% endif %} @@ -48,10 +40,10 @@ Se você pretende habilitar o {% data variables.product.prodname_actions %} para {% warning %} -**Aviso:** recomendamos que os usuários configurem eventos de webhook para notificar os sistemas externos da atividade no {% data variables.product.prodname_ghe_server %}. As verificações automatizadas de alterações, ou _sondagem_, afetarão negativamente o desempenho e a escalabilidade da instância. Para obter mais informações, confira "[Sobre os webhooks](/github/extending-github/about-webhooks)". +**Warning:** We recommend that users configure webhook events to notify external systems of activity on {% data variables.product.prodname_ghe_server %}. Automated checks for changes, or _polling_, will negatively impact the performance and scalability of your instance. For more information, see "[About webhooks](/github/extending-github/about-webhooks)." {% endwarning %} -Para obter mais informações sobre como monitorar a capacidade e o desempenho do {% data variables.product.prodname_ghe_server %}, confira "[Como monitorar seu dispositivo](/admin/enterprise-management/monitoring-your-appliance)". +For more information about monitoring the capacity and performance of {% data variables.product.prodname_ghe_server %}, see "[Monitoring your appliance](/admin/enterprise-management/monitoring-your-appliance)." -Você pode aumentar os recursos de memória ou da CPU na sua instância. Para obter mais informações, confira "[Como aumentar os recursos de CPU ou de memória](/enterprise/admin/installation/increasing-cpu-or-memory-resources)". +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)." diff --git a/translations/pt-BR/data/reusables/enterprise_installation/hotpatching-explanation.md b/translations/pt-BR/data/reusables/enterprise_installation/hotpatching-explanation.md index 076badfeae..84970a0e35 100644 --- a/translations/pt-BR/data/reusables/enterprise_installation/hotpatching-explanation.md +++ b/translations/pt-BR/data/reusables/enterprise_installation/hotpatching-explanation.md @@ -4,4 +4,4 @@ You can use hotpatching to upgrade to a newer patch release, but not a feature r Hotpatches do not generally require a reboot. If a hotpatch does require a reboot, the {% data variables.product.product_name %} release notes will indicate the requirement. -Hotpatches require a configuration run, which can cause a brief period of errors or unresponsiveness for some or all services on {% data variables.product.product_location %}. You are not required to enable maintenance mode during installation of a hotpatch, but doing so will guarantee that users see a maintenance page instead of errors or timeouts. For more information, see "[Enabling and scheduling maintenance mode](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)." +Hotpatches require a configuration run, which can cause a brief period of errors or unresponsiveness for some or all services on {% data variables.location.product_location %}. You are not required to enable maintenance mode during installation of a hotpatch, but doing so will guarantee that users see a maintenance page instead of errors or timeouts. For more information, see "[Enabling and scheduling maintenance mode](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)." 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 c0f17ed086..ecff795df4 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,13 +1,5 @@ ---- -ms.openlocfilehash: 7f6ced813ea6d819b42c469ae1f285f6732ceeb4 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145093695" ---- {% warning %} -**Aviso:** se você adicionar um anexo de imagem de um comentário sobre um problema ou uma solicitação de pull, qualquer pessoa poderá ver a URL de imagem anônima sem autenticação{% ifversion ghes %}, mesmo que a solicitação de pull esteja em um repositório privado ou se o modo privado estiver habilitado. Para impedir o acesso não autorizado às imagens, restrinja o acesso à rede aos sistemas que fornecem as imagens, incluindo o {% data variables.product.product_location %}{% endif %}.{% ifversion ghae %} Para impedir o acesso não autorizado às URLs de imagem no {% data variables.product.product_name %}, considere a possibilidade de restringir o tráfego de rede para sua empresa. Para obter mais informações, confira "[Como restringir o tráfego de rede para sua empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)".{% endif %} +**Warning:** If you add an image attachment to a pull request or issue comment, anyone can view the anonymized image URL without authentication{% ifversion ghes %}, 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.location.product_location %}{% endif %}.{% ifversion ghae %} 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 %} {% endwarning %} diff --git a/translations/pt-BR/data/reusables/enterprise_installation/ssh-into-instance.md b/translations/pt-BR/data/reusables/enterprise_installation/ssh-into-instance.md index 43f857509b..86f7f9ac05 100644 --- a/translations/pt-BR/data/reusables/enterprise_installation/ssh-into-instance.md +++ b/translations/pt-BR/data/reusables/enterprise_installation/ssh-into-instance.md @@ -1,13 +1,5 @@ ---- -ms.openlocfilehash: 56d00170560f72e7e4fad39972422cf301b377be -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147875661" ---- -1. Entre com o SSH no {% data variables.product.product_location %}. Se sua instância for composta por vários nós, por exemplo, se a alta disponibilidade ou a replicação geográfica estiver configurada, efetue SSH no nó primário. Se você usar um cluster, poderá efetuar SSH em qualquer nó. Para obter mais informações sobre o acesso SSH, confira "[Como acessar o shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)". +1. SSH into {% data variables.location.product_location %}. If your instance comprises multiple nodes, for example if high availability or geo-replication are configured, SSH into the primary node. If you use a cluster, you can SSH into any node. For more information about SSH access, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." ```shell - $ ssh -p 122 admin@HOSTNAME + $ ssh -p 122 admin@HOSTNAME ``` diff --git a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md index 0eee8a1116..4ab76aace6 100644 --- a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md +++ b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: ac036166292f405220029fb6290b1e0a1a278ecb -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145093599" ---- -O limite de inatividade é o tempo que um usuário deve ser inativo para ser considerado inativo. O limite padrão de inatividade é de 90 dias, mas você pode personalizar esse limite no {% data variables.product.product_location %}. +The dormancy threshold is the length of time a user must be inactive to be considered dormant. The default dormancy threshold is 90 days, however you can customize the dormancy threshold for {% data variables.location.product_location %}. diff --git a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/sign-in.md b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/sign-in.md index 6c05603792..404565e28e 100644 --- a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/sign-in.md +++ b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/sign-in.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 0370abebda6c2219a6ef19851958c45d7e4f595f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145093580" ---- -1. Entre no {% data variables.product.product_location %} em `http(s)://HOSTNAME/login`. +1. Sign in to {% data variables.location.product_location %} at `http(s)://HOSTNAME/login`. diff --git a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/tls-downtime.md b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/tls-downtime.md index c8425854d6..06f181e152 100644 --- a/translations/pt-BR/data/reusables/enterprise_site_admin_settings/tls-downtime.md +++ b/translations/pt-BR/data/reusables/enterprise_site_admin_settings/tls-downtime.md @@ -1,13 +1,5 @@ ---- -ms.openlocfilehash: 63560a19f1dc683ba1f02c35f0487aec236217a6 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145065273" ---- {% warning %} -**Aviso:** a configuração do TLS gera uma pequena quantidade de tempo de inatividade no {% data variables.product.product_location %}. +**Warning:** Configuring TLS causes a small amount of downtime for {% data variables.location.product_location %}. {% endwarning %} diff --git a/translations/pt-BR/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md b/translations/pt-BR/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md index 5cc0296696..a8ccf8f70b 100644 --- a/translations/pt-BR/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md +++ b/translations/pt-BR/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 6b4a4fbf8ba73127abab49f8fefc25e1a2d3fbca -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145065270" ---- -Como alternativa, você pode configurar a autenticação externa para {% data variables.product.product_location %}. Se você usar a autenticação externa, deverá convidar pessoas para usar sua instância por meio do provedor de autenticação. Para obter mais informações, confira "[Sobre a autenticação em sua empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)". +Alternatively, you can configure external authentication for {% data variables.location.product_location %}. If you use external authentication, you must invite people to use your instance through your authentication provider. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)." diff --git a/translations/pt-BR/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md b/translations/pt-BR/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md index 51c1d81fe9..d1c1d86a0d 100644 --- a/translations/pt-BR/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md +++ b/translations/pt-BR/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 0e38b9097fcac8c9c60b2b2056000e50f96a0c25 -ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147883590" ---- -Quando você usa a autenticação interna para {% data variables.product.product_location %}, cada pessoa cria uma conta pessoal a partir de um convite ou de uma inscrição. +When you use built-in authentication for {% data variables.location.product_location %}, each person creates a personal account from an invitation or by signing up. diff --git a/translations/pt-BR/data/reusables/enterprise_user_management/built-in-authentication.md b/translations/pt-BR/data/reusables/enterprise_user_management/built-in-authentication.md index 271a4f7530..49151a385f 100644 --- a/translations/pt-BR/data/reusables/enterprise_user_management/built-in-authentication.md +++ b/translations/pt-BR/data/reusables/enterprise_user_management/built-in-authentication.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: d50bb457fe9b5d4daee819a2597f573692aeaa12 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145093572" ---- -Se você deseja permitir a autenticação para algumas pessoas que não têm uma conta em seu provedor de autenticação externo, você pode permitir a autenticação de fallback para contas locais em {% data variables.product.product_location %}. Para obter mais informações, confira "[Como permitir a autenticação interna para usuários fora do seu provedor](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)". +If you want to allow authentication for some people who don't have an account on your external authentication provider, you can allow fallback authentication to local accounts on {% data variables.location.product_location %}. For more information, see "[Allowing built-in authentication for users outside your provider](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)." diff --git a/translations/pt-BR/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md b/translations/pt-BR/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md index f341f10f4d..c52e1e5433 100644 --- a/translations/pt-BR/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md +++ b/translations/pt-BR/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 68778a5aac47ae812ce7fca5219ce8f7e416b1af -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145065267" ---- -{% data variables.product.product_name %} normaliza um valor do seu {% ifversion ghec or ghae %}IdP{% elsif ghes %}provedor de autenticação externo{% endif %} para determinar o nome de usuário de cada conta pessoal nova {% ifversion ghae %}de {% data variables.product.product_name %}{% elsif ghec %}na sua empresa em {% data variables.product.product_location %}{% elsif ghes %}on {% data variables.product.product_location %}{% endif %}. +{% data variables.product.product_name %} normalizes a value from your {% ifversion ghec or ghae %}IdP{% elsif ghes %}external authentication provider{% endif %} to determine the username for each new personal account {% ifversion ghae %}on {% data variables.product.product_name %}{% elsif ghec %}in your enterprise on {% data variables.location.product_location %}{% elsif ghes %}on {% data variables.location.product_location %}{% endif %}. diff --git a/translations/pt-BR/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md b/translations/pt-BR/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md index 39818086e1..7e914e8766 100644 --- a/translations/pt-BR/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md +++ b/translations/pt-BR/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md @@ -1,17 +1,9 @@ ---- -ms.openlocfilehash: b757e88a4ac3718fff996837dd8e00714f0cd7ad -ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147883582" ---- {% warning %} -**Avisos:** +**Warnings:** -- O protocolo do Git é não autenticado e não criptografado. Um invasor pode interceptar dados de repositório transferidos por conexões usando esse protocolo. -- Se você habilitar o acesso de leitura anônimo do Git, será responsável por todo o acesso e uso do recurso. {% data variables.product.company_short %} não é responsável por nenhum acesso indesejado, riscos de segurança ou uso indevido do recurso. -- Vvocê não pode usar este recurso para violar sua licença de {% data variables.product.company_short %}, incluindo o número de licenças de usuários para {% data variables.product.product_location %}. +- The Git protocol is unauthenticated and unencrypted. An attacker could intercept repository data transferred over connections using this protocol. +- If you enable anonymous Git read access, you're responsible for all access and use of the feature. {% data variables.product.company_short %} is not responsible for any unintended access, security risks, or misuse of the feature. +- You may not use this feature to violate your license from {% data variables.product.company_short %}, including the limit on the number of user licenses for {% data variables.location.product_location %}. {% endwarning %} diff --git a/translations/pt-BR/data/reusables/files/choose-commit-email.md b/translations/pt-BR/data/reusables/files/choose-commit-email.md index 5bccaf2a3d..e8e07c32bf 100644 --- a/translations/pt-BR/data/reusables/files/choose-commit-email.md +++ b/translations/pt-BR/data/reusables/files/choose-commit-email.md @@ -1,11 +1,4 @@ ---- -ms.openlocfilehash: e786a92aa48e8c2cb737f766aa20050c2fd94851 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145093559" ---- {% ifversion fpt or ghec %} -1. Se você tiver mais de um endereço de email associado à sua conta do {% data variables.product.product_location %}, clique no menu suspenso do endereço de email e selecione o endereço de email a ser usado como o endereço de email do autor do Git. Apenas endereços de e-mail verificados aparecem neste menu suspenso. Se você habilitou a privacidade do endereço de email, `@users.noreply.github.com` é o endereço de email do autor de commit padrão. Para obter mais informações, confira "[Como definir seu endereço de email de commit](/articles/setting-your-commit-email-address)". -![Escolher endereços de email de commit](/assets/images/help/repository/choose-commit-email-address.png) {% endif %} +1. If you have more than one email address associated with your account on {% data variables.location.product_location %}, click the email address drop-down menu and select the email address to use as the Git author email address. Only verified email addresses appear in this drop-down menu. If you enabled email address privacy, then `@users.noreply.github.com` is the default commit author email address. For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)." +![Choose commit email addresses](/assets/images/help/repository/choose-commit-email-address.png) +{% endif %} diff --git a/translations/pt-BR/data/reusables/getting-started/actions.md b/translations/pt-BR/data/reusables/getting-started/actions.md index 50c8edde03..c655219426 100644 --- a/translations/pt-BR/data/reusables/getting-started/actions.md +++ b/translations/pt-BR/data/reusables/getting-started/actions.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: aec556bebd25dc78544f0ed8250442014a4eba71 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147882092" ---- -Com o {% data variables.product.prodname_actions %}, você pode automatizar e personalizar o fluxo de trabalho de desenvolvimento do {% data variables.product.product_location %} no {% data variables.product.product_name %}. Você pode criar as suas próprias ações e usar e personalizar ações compartilhadas pela comunidade {% data variables.product.prodname_dotcom %}. Para obter mais informações, confira "[Aprenda a usar o {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". +With {% data variables.product.prodname_actions %}, you can automate and customize {% data variables.location.product_location %}'s development workflow on {% data variables.product.product_name %}. You can create your own actions, and use and customize actions shared by the {% data variables.product.prodname_dotcom %} community. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." diff --git a/translations/pt-BR/data/reusables/getting-started/adding-members-to-organizations.md b/translations/pt-BR/data/reusables/getting-started/adding-members-to-organizations.md index 3193fb6f65..42d5f43d6f 100644 --- a/translations/pt-BR/data/reusables/getting-started/adding-members-to-organizations.md +++ b/translations/pt-BR/data/reusables/getting-started/adding-members-to-organizations.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 3b4d678bc4a5a023d7fbcced5c68a6ee5e66fc54 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145093449" ---- -Você pode adicionar membros a organizações no {% data variables.product.product_location %} desde que seja proprietário da organização nas organizações que deseja gerenciar. Você também pode configurar a visibilidade da associação à organização. Para obter mais informações, confira "[Como adicionar pessoas à sua organização](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)" e "[Como configurar a visibilidade da associação à organização](/admin/user-management/managing-organizations-in-your-enterprise/configuring-visibility-for-organization-membership)". +You can add members to organizations in {% data variables.location.product_location %} as long as you are an organization owner in the organizations you want to manage. You can also configure visibility of organization membership. For more information, see "[Adding people to your organization](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)" and "[Configuring visibility for organization membership](/admin/user-management/managing-organizations-in-your-enterprise/configuring-visibility-for-organization-membership)." diff --git a/translations/pt-BR/data/reusables/getting-started/configuring-security-features.md b/translations/pt-BR/data/reusables/getting-started/configuring-security-features.md index d23955faec..be2ff1bb50 100644 --- a/translations/pt-BR/data/reusables/getting-started/configuring-security-features.md +++ b/translations/pt-BR/data/reusables/getting-started/configuring-security-features.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 8657ff2b842e749aa9fff25434a5587acf0ec448 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145093444" ---- -Para manter {% ifversion ghes or ghae %}as organizações do {% data variables.product.product_location %}{% else %}sua organização{% endif %} segura, você pode usar uma variedade de recursos de segurança do {% data variables.product.prodname_dotcom %}, incluindo políticas de segurança, grafos de dependência, verificação de segredos e atualizações de versão e de segurança do Dependabot. Para obter mais informações, confira "[Como proteger sua organização](/code-security/getting-started/securing-your-organization)" e "[Como gerenciar as configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". +To keep {% ifversion ghes or ghae %}the organizations in {% data variables.location.product_location %}{% else %}your organization{% endif %} secure, you can use a variety of {% data variables.product.prodname_dotcom %} security features, including security policies, dependency graphs, secret scanning and Dependabot security and version updates. For more information, see "[Securing your organization](/code-security/getting-started/securing-your-organization)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." diff --git a/translations/pt-BR/data/reusables/getting-started/creating-organizations.md b/translations/pt-BR/data/reusables/getting-started/creating-organizations.md index eacd70149c..70551a4383 100644 --- a/translations/pt-BR/data/reusables/getting-started/creating-organizations.md +++ b/translations/pt-BR/data/reusables/getting-started/creating-organizations.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: ec82fc3572981a7f9fd81165c8fc40056bc56824 -ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147875483" ---- -Você pode criar organizações no {% data variables.product.product_location %} para refletir a estrutura da empresa ou do grupo. Para obter mais informações, confira "[Como criar uma organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". +You can create new organizations in {% data variables.location.product_location %} to reflect your company or group's structure. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." diff --git a/translations/pt-BR/data/reusables/getting-started/enforcing-repo-management-policies.md b/translations/pt-BR/data/reusables/getting-started/enforcing-repo-management-policies.md index 0b641c8a46..a684eecaa6 100644 --- a/translations/pt-BR/data/reusables/getting-started/enforcing-repo-management-policies.md +++ b/translations/pt-BR/data/reusables/getting-started/enforcing-repo-management-policies.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 01211e69f9b41fd5ca1af8bffc9bb73669dba023 -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147880353" ---- -Como proprietário de uma empresa, você pode definir políticas de gerenciamento de repositório para todas as organizações em {% data variables.product.product_location %} ou permitir que as políticas sejam definidas separadamente em cada organização. Para obter mais informações, confira "[Como impor políticas de gerenciamento de repositório na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)". +As an enterprise owner, you can set repository management policies for all organizations in {% data variables.location.product_location %}, or allow policies to be set separately in each organization. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)." diff --git a/translations/pt-BR/data/reusables/getting-started/managing-enterprise-members.md b/translations/pt-BR/data/reusables/getting-started/managing-enterprise-members.md index 4f910035bd..7c74a811a0 100644 --- a/translations/pt-BR/data/reusables/getting-started/managing-enterprise-members.md +++ b/translations/pt-BR/data/reusables/getting-started/managing-enterprise-members.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: ab49c1d935838b59ead4931c40f837f331cc59eb -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145093413" ---- -Você pode gerenciar as configurações e a atividade de auditoria para os membros do {% data variables.product.product_location %}. Você pode {% ifversion ghes %}promover um membro da empresa para ser um administrador do site, {% endif %}gerenciar usuários inativos, ver o log de auditoria para a atividade do usuário e personalizar as mensagens que serão vistas pelos membros da empresa. Para obter mais informações, confira "[Como gerenciar usuários na sua empresa](/admin/user-management/managing-users-in-your-enterprise)". +You can manage settings and audit activity for the members of {% data variables.location.product_location %}. You can {% ifversion ghes %}promote an enterprise member to be a site administrator, {% endif %}manage dormant users, view the audit log for user activity, and customize messages that enterprise members will see. For more information, see "[Managing users in your enterprise](/admin/user-management/managing-users-in-your-enterprise)." diff --git a/translations/pt-BR/data/reusables/git/git-push.md b/translations/pt-BR/data/reusables/git/git-push.md index 11af280d18..58c2a216e0 100644 --- a/translations/pt-BR/data/reusables/git/git-push.md +++ b/translations/pt-BR/data/reusables/git/git-push.md @@ -1,13 +1,5 @@ ---- -ms.openlocfilehash: a13765e853c204f45f461ecbfcf22ba168e8966a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145093375" ---- -1. [Efetue push das alterações](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) no repositório local para o {% data variables.product.product_location %}. +1. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.location.product_location %}. ```shell - $ git push origin your-branch + $ git push origin YOUR_BRANCH # Pushes the changes in your local repository up to the remote repository you specified as the origin ``` diff --git a/translations/pt-BR/data/reusables/large_files/storage_assets_location.md b/translations/pt-BR/data/reusables/large_files/storage_assets_location.md index 3a82e9b3b2..cfc3b76dfa 100644 --- a/translations/pt-BR/data/reusables/large_files/storage_assets_location.md +++ b/translations/pt-BR/data/reusables/large_files/storage_assets_location.md @@ -1,10 +1,3 @@ ---- -ms.openlocfilehash: eaee6a93767f4fb3a9f254f56d797f65d67129d5 -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147880345" ---- -{% ifversion ghes %} Por padrão, o cliente do {% data variables.large_files.product_name_long %} armazena ativos grandes no mesmo servidor que hospeda o repositório Git. Quando o {% data variables.large_files.product_name_short %} estiver habilitado no {% data variables.product.product_location %}, os ativos grandes serão armazenados na partição de dados em `/data/user/storage`. +{% ifversion ghes %} +By default, the {% data variables.large_files.product_name_long %} client stores large assets on the same server that hosts the Git repository. When {% data variables.large_files.product_name_short %} is enabled on {% data variables.location.product_location %}, large assets are stored on the data partition in `/data/user/storage`. {% endif %} diff --git a/translations/pt-BR/data/reusables/large_files/use_lfs_tip.md b/translations/pt-BR/data/reusables/large_files/use_lfs_tip.md index 1c08afff8d..5c45786e34 100644 --- a/translations/pt-BR/data/reusables/large_files/use_lfs_tip.md +++ b/translations/pt-BR/data/reusables/large_files/use_lfs_tip.md @@ -1,13 +1,5 @@ ---- -ms.openlocfilehash: 3357b686e01b80c0148b2f7c4614718a550982aa -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145096647" ---- {% tip %} -**Dica:** se você efetua push de arquivos grandes regularmente para {% data variables.product.product_location %}, considere usar {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). Para obter mais informações, confira "[Controle de versão de arquivos grandes](/articles/versioning-large-files)". +**Tip:** If you regularly push large files to {% data variables.location.product_location %}, consider using {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). For more information, see "[Versioning large files](/articles/versioning-large-files)." {% endtip %} diff --git a/translations/pt-BR/data/reusables/notifications/outbound_email_tip.md b/translations/pt-BR/data/reusables/notifications/outbound_email_tip.md index d7825683ff..e8f714d69a 100644 --- a/translations/pt-BR/data/reusables/notifications/outbound_email_tip.md +++ b/translations/pt-BR/data/reusables/notifications/outbound_email_tip.md @@ -1,13 +1,7 @@ ---- -ms.openlocfilehash: ce7f7a00c03950eff6f829e4715ba3aac0606ad6 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147884362" ---- -{% ifversion ghes or ghae %} {% note %} +{% ifversion ghes or ghae %} +{% note %} -**Observação**: você só receberá notificações por email se o suporte a e-mails de saída estiver ativado no {% data variables.product.product_location %}. Para mais informações, entre em contato com o administrador do site. +**Note**: You'll only receive email notifications if outbound email support is enabled on {% data variables.location.product_location %}. For more information, contact your site administrator. -{% endnote %} {% endif %} +{% endnote %} +{% endif %} diff --git a/translations/pt-BR/data/reusables/notifications/shared_state.md b/translations/pt-BR/data/reusables/notifications/shared_state.md index 0178c7d808..76f7bb93f6 100644 --- a/translations/pt-BR/data/reusables/notifications/shared_state.md +++ b/translations/pt-BR/data/reusables/notifications/shared_state.md @@ -1,13 +1,5 @@ ---- -ms.openlocfilehash: b5e0ba909d27927fefce88d2a763f0b94aa83dab -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145096551" ---- {% tip %} -**Dica:** se você receber notificações da Web e por email, poderá sincronizar automaticamente o status de lido ou não lido da notificação para que as notificações da Web sejam marcadas automaticamente como lidas depois que você ler a notificação por email correspondente. Para habilitar essa sincronização, seu cliente de email precisa conseguir exibir as imagens no {% ifversion fpt or ghec %}`notifications@github.com`{% else %} endereço de email `no-reply` {% ifversion ghae %}do nome do host do {% data variables.product.product_name %}{% elsif ghes %}para a {% data variables.product.product_location %}, que é configurado pelo administrador do site{% endif %}{% endif %}. +**Tip:** If you receive both web and email notifications, you can automatically sync the read or unread status of the notification so that web notifications are automatically marked as read once you've read the corresponding email notification. To enable this sync, your email client must be able to view images from {% ifversion fpt or ghec %}`notifications@github.com`{% else %}the `no-reply` email address {% ifversion ghae %}for your {% data variables.product.product_name %} hostname{% elsif ghes %}for {% data variables.location.product_location %}, which your site administrator configures{% endif %}{% endif %}. {% endtip %} diff --git a/translations/pt-BR/data/reusables/organizations/navigate-to-org.md b/translations/pt-BR/data/reusables/organizations/navigate-to-org.md index dcf900b23e..ef3f95d2c2 100644 --- a/translations/pt-BR/data/reusables/organizations/navigate-to-org.md +++ b/translations/pt-BR/data/reusables/organizations/navigate-to-org.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: fbf26f7ab8e188cea909554cba9edd5d6ab4ca6c -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145096457" ---- -1. No {% data variables.product.product_location %}, navegue até a página principal da organização. +1. On {% data variables.location.product_location %}, navigate to the main page of the organization. diff --git a/translations/pt-BR/data/reusables/package_registry/authenticate-packages.md b/translations/pt-BR/data/reusables/package_registry/authenticate-packages.md index dce624589e..bc3e424d23 100644 --- a/translations/pt-BR/data/reusables/package_registry/authenticate-packages.md +++ b/translations/pt-BR/data/reusables/package_registry/authenticate-packages.md @@ -1,15 +1,9 @@ ---- -ms.openlocfilehash: fd3590bb212b7c9521cb447ca012b19270469a8c -ms.sourcegitcommit: 22d665055b1bee7a5df630385e734e3a149fc720 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 07/13/2022 -ms.locfileid: "145096311" ---- -Você precisa de um token de acesso para publicar, instalar e excluir pacotes. +{% data reusables.package_registry.packages-classic-pat-only %} -Você pode usar um PAT (token de acesso pessoal) para se autenticar no {% data variables.product.prodname_registry %} ou na API do {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}. Ao criar um token de acesso pessoal, você pode atribuir diferentes escopos de token, dependendo da sua necessidade. Para obter mais informações sobre escopos relacionados a pacotes para um PAT, confira "[Sobre as permissões para pacotes do GitHub](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)". +You need an access token to publish, install, and delete private, internal, and public packages. -Para efetuar a autenticação em um registro do {% data variables.product.prodname_registry %} dentro de um fluxo de trabalho de {% data variables.product.prodname_actions %}, você pode utilizar: -- `GITHUB_TOKEN` para publicar pacotes associados ao repositório do fluxo de trabalho. -- um PAT para instalar pacotes associados a outros repositórios privados (que não podem ser acessados pelo `GITHUB_TOKEN`). +You can use a {% data variables.product.pat_v1 %} to authenticate to {% data variables.product.prodname_registry %} or the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API. When you create a {% data variables.product.pat_v1 %}, you can assign the token different scopes depending on your needs. For more information about packages-related scopes for a {% data variables.product.pat_v1 %}, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)." + +To authenticate to a {% data variables.product.prodname_registry %} registry within a {% data variables.product.prodname_actions %} workflow, you can use: +- `GITHUB_TOKEN` to publish packages associated with the workflow repository. +- a {% data variables.product.pat_v1 %} with at least `packages:read` scope to install packages associated with other private repositories (which `GITHUB_TOKEN` can't access). diff --git a/translations/pt-BR/data/reusables/package_registry/authenticate-to-container-registry-steps.md b/translations/pt-BR/data/reusables/package_registry/authenticate-to-container-registry-steps.md index 501b7dee99..cc61c65d06 100644 --- a/translations/pt-BR/data/reusables/package_registry/authenticate-to-container-registry-steps.md +++ b/translations/pt-BR/data/reusables/package_registry/authenticate-to-container-registry-steps.md @@ -1,29 +1,23 @@ ---- -ms.openlocfilehash: 50e7f623d6585c8697d0b1c6c827a855df26c571 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145096300" ---- -1. Crie um novo token de acesso pessoal (PAT) com os escopos apropriados para as tarefas que você deseja realizar. Se sua organização exigir SSO, você deverá habilitar o SSO para seu novo token. +{% data reusables.package_registry.packages-classic-pat-only %} + +1. Create a new {% data variables.product.pat_v1 %} with the appropriate scopes for the tasks you want to accomplish. If your organization requires SSO, you must enable SSO for your new token. {% warning %} - **Observação:** por padrão, quando você selecionar o escopo `write:packages` do PAT (token de acesso pessoal) na interface do usuário, o escopo `repo` também será selecionado. O escopo `repo` oferece acesso desnecessário e amplo, o qual, em particular, recomendamos que você evite usar para fluxos de trabalho do GitHub Actions. Para obter mais informações, confira "[Proteção de segurança do GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)". Como solução alternativa, você pode selecionar apenas o escopo `write:packages` do PAT na interface do usuário com esta URL: `https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/settings/tokens/new?scopes=write:packages`. + **Note:** By default, when you select the `write:packages` scope for your {% data variables.product.pat_v1 %} in the user interface, the `repo` scope will also be selected. The `repo` scope offers unnecessary and broad access, which we recommend you avoid using for {% data variables.product.prodname_actions %} workflows in particular. For more information, see "[Security hardening for GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)." As a workaround, you can select just the `write:packages` scope for your {% data variables.product.pat_v1 %} in the user interface with this url: `https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/settings/tokens/new?scopes=write:packages`. {% endwarning %} - - Selecione o escopo `read:packages` para baixar imagens de contêiner e ler os metadados dela. - - Selecione o escopo `write:packages` para baixar e carregar imagens de contêiner e ler e gravar os metadados dela. - - Selecione o escopo `delete:packages` para excluir imagens de contêiner. + - Select the `read:packages` scope to download container images and read their metadata. + - Select the `write:packages` scope to download and upload container images and read and write their metadata. + - Select the `delete:packages` scope to delete container images. - Para obter mais informações, confira "[Como criar um token de acesso pessoal para a linha de comando](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". + For more information, see "[Creating a {% data variables.product.pat_generic %} for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)." -2. Salve seu PAT. Recomendamos salvar o seu PAT como uma variável de ambiente. +2. Save your {% data variables.product.pat_v1 %}. We recommend saving your token as an environment variable. ```shell $ export CR_PAT=YOUR_TOKEN ``` -3. Usando a CLI para o tipo de contêiner, entre no serviço do {% data variables.product.prodname_container_registry %} em `{% data reusables.package_registry.container-registry-hostname %}`. +3. Using the CLI for your container type, sign in to the {% data variables.product.prodname_container_registry %} service at `{% data reusables.package_registry.container-registry-hostname %}`. {% raw %} ```shell $ echo $CR_PAT | docker login {% endraw %}{% data reusables.package_registry.container-registry-hostname %}{% raw %} -u USERNAME --password-stdin diff --git a/translations/pt-BR/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md b/translations/pt-BR/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md index 2fbdf2b992..db1256da20 100644 --- a/translations/pt-BR/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md +++ b/translations/pt-BR/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md @@ -1,15 +1,7 @@ ---- -ms.openlocfilehash: b5c33a751c34b9a3e0e804c6c5153fbcdc96a7f6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147705056" ---- -Se o seu fluxo de trabalho estiver usando um PAT (token de acesso pessoal) para se autenticar em um registro, então é altamente recomendável atualizar seu fluxo de trabalho para usar o `GITHUB_TOKEN`. +If your workflow is using a {% data variables.product.pat_generic %} to authenticate to a registry, then we highly recommend you update your workflow to use the `GITHUB_TOKEN`. -{% ifversion fpt or ghec %}Para obter diretrizes sobre como atualizar seus fluxos de trabalho que se autenticam em um registro com um token de acesso pessoal, confira "[Como atualizar um fluxo de trabalho que acessa um registro usando PAT](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-a-registry-using-a-pat)."{% endif %} +{% ifversion fpt or ghec %}For guidance on updating your workflows that authenticate to a registry with a {% data variables.product.pat_generic %}, see "[Upgrading a workflow that accesses a registry using a {% data variables.product.pat_generic %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-a-registry-using-a-pat)."{% endif %} -Para obter mais informações sobre o `GITHUB_TOKEN`, confira "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)". +For more information about the `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)." -Para obter mais informações sobre as melhores práticas ao usar um registro em ações, confira "[Proteção de segurança para GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)". +For more information about the best practices when using a registry in actions, see "[Security hardening for GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)." diff --git a/translations/pt-BR/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md b/translations/pt-BR/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md index 1cf3ba6011..7a5938bed8 100644 --- a/translations/pt-BR/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md +++ b/translations/pt-BR/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md @@ -1,11 +1,3 @@ ---- -ms.openlocfilehash: 41b658e6f15ac145ddb7637a1d0ae328b50b8af2 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145096279" ---- -Como a próxima etapa, você pode personalizar os ecossistemas de pacote que você gostaria de disponibilizar para os usuários finais em {% data variables.product.product_location %}. Para obter mais informações, confira "[Como configurar o suporte ao ecossistema de pacotes para sua empresa](/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)". +As a next step, you can customize which package ecosystems you would like to make available to end users on {% data variables.location.product_location %}. For more information, see "[Configuring package ecosystem support for your enterprise](/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." -Para ter uma visão geral de introdução ao {% data variables.product.prodname_registry %} no {% data variables.product.prodname_dotcom %}, confira "[Introdução aos Pacotes do GitHub para sua empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)". +For an overview of getting started with {% data variables.product.prodname_registry %} on {% data variables.product.prodname_dotcom %}, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." diff --git a/translations/pt-BR/data/reusables/package_registry/package-registry-with-github-tokens.md b/translations/pt-BR/data/reusables/package_registry/package-registry-with-github-tokens.md index c033c6532b..e6f45e55dd 100644 --- a/translations/pt-BR/data/reusables/package_registry/package-registry-with-github-tokens.md +++ b/translations/pt-BR/data/reusables/package_registry/package-registry-with-github-tokens.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 12305a068862ac705c591ff473e7170dd8b9e3f5 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145096277" ---- -Se você estiver usando um fluxo de trabalho do {% data variables.product.prodname_actions %}, poderá usar um `GITHUB_TOKEN` para publicar e consumir pacotes no {% data variables.product.prodname_registry %} sem a necessidade de armazenar e gerenciar um token de acesso pessoal. Para obter mais informações, confira "[Autenticação com o `GITHUB_TOKEN`](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)". +If you are using a {% data variables.product.prodname_actions %} workflow, you can use a `GITHUB_TOKEN` to publish and consume packages in {% data variables.product.prodname_registry %} without needing to store and manage a {% data variables.product.pat_generic %}. For more information, see "[Authenticating with the `GITHUB_TOKEN`](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." diff --git a/translations/pt-BR/data/reusables/package_registry/packages-billing.md b/translations/pt-BR/data/reusables/package_registry/packages-billing.md index ff1f88c472..07e599fb33 100644 --- a/translations/pt-BR/data/reusables/package_registry/packages-billing.md +++ b/translations/pt-BR/data/reusables/package_registry/packages-billing.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: ac24f76da582d8aaa7f7a0cbba7d15ab80f95629 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147883777" ---- -O uso de {% data variables.product.prodname_registry %} é gratuito para pacotes públicos. Para pacotes privados, cada conta do {% data variables.product.product_location %} recebe determinada quantidade de armazenamento gratuito e transferência de dados, dependendo do produto usado com a conta. Qualquer uso além dos valores incluídos é controlado pelos limites de gastos. +{% data variables.product.prodname_registry %} usage is free for public packages. For private packages, each account on {% data variables.location.product_location %} receives a certain amount of free storage and data transfer, depending on the product used with the account. Any usage beyond the included amounts is controlled by spending limits. diff --git a/translations/pt-BR/data/reusables/package_registry/required-scopes.md b/translations/pt-BR/data/reusables/package_registry/required-scopes.md index 28c6f44619..9a69fbda9b 100644 --- a/translations/pt-BR/data/reusables/package_registry/required-scopes.md +++ b/translations/pt-BR/data/reusables/package_registry/required-scopes.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 63e116796a07c20d4a6bbb14cfd493f3c2bc09fe -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145096256" ---- -Você deve usar um token de acesso pessoal com os escopos apropriados para publicar e instalar pacotes no {% data variables.product.prodname_registry %}. Para obter mais informações, confira "[Sobre o {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-github-packages#authenticating-to-github-packages)". +You must use a {% data variables.product.pat_v1 %} with the appropriate scopes to publish and install packages in {% data variables.product.prodname_registry %}. For more information, see "[About {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-github-packages#authenticating-to-github-packages)." diff --git a/translations/pt-BR/data/reusables/pages/build-failure-email-server.md b/translations/pt-BR/data/reusables/pages/build-failure-email-server.md index e2c685d9d8..89e9253b46 100644 --- a/translations/pt-BR/data/reusables/pages/build-failure-email-server.md +++ b/translations/pt-BR/data/reusables/pages/build-failure-email-server.md @@ -1,13 +1,7 @@ ---- -ms.openlocfilehash: f206838932fe094447f63dd9005f14252f3c8439 -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147875567" ---- -{% ifversion ghes or ghae %} {% tip %} +{% ifversion ghes or ghae %} + {% tip %} - Você só receberá um email se o suporte a e-mails de saída estiver habilitado no {% data variables.product.product_location %}. Para mais informações, entre em contato com o administrador do site. + You will only receive an email if outbound email support is enabled on {% data variables.location.product_location %}. For more information, contact your site administrator. - {% endtip %} {% endif %} + {% endtip %} +{% endif %} diff --git a/translations/pt-BR/data/reusables/pages/emu-org-only.md b/translations/pt-BR/data/reusables/pages/emu-org-only.md index 8d8b6240a2..fb1844ee17 100644 --- a/translations/pt-BR/data/reusables/pages/emu-org-only.md +++ b/translations/pt-BR/data/reusables/pages/emu-org-only.md @@ -1,13 +1,7 @@ ---- -ms.openlocfilehash: 25b8700240c49223cdd987beb555e15102d41844 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147060999" ---- -{% ifversion ghec %} {% note %} +{% ifversion ghec %} +{% note %} -**Observação:** se você for um {% data variables.product.prodname_managed_user %}, só poderá publicar sites {% data variables.product.prodname_pages %} de repositórios pertencentes às organizações. Para obter mais informações, confira "[Sobre o {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)". +**Note:** If you're a {% data variables.enterprise.prodname_managed_user %}, you can only publish {% data variables.product.prodname_pages %} sites from repositories owned by organizations. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)." -{% endnote %} {% endif %} +{% endnote %} +{% endif %} diff --git a/translations/pt-BR/data/reusables/projects/enable-basic-workflow.md b/translations/pt-BR/data/reusables/projects/enable-basic-workflow.md index c8cd41d803..715219b099 100644 --- a/translations/pt-BR/data/reusables/projects/enable-basic-workflow.md +++ b/translations/pt-BR/data/reusables/projects/enable-basic-workflow.md @@ -1,21 +1,17 @@ ---- -ms.openlocfilehash: 0c55df675453a0707e8695cbca9087c5b585c438 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147423657" ---- -1. Procure seu projeto. -1. No canto superior direito, clique em {% octicon "kebab-horizontal" aria-label="The menu icon" %} para abrir o menu. - ![Captura de tela mostrando o ícone de menu](/assets/images/help/projects-v2/open-menu.png) -1. No menu, clique em {% octicon "workflow" aria-label="The workflow icon" %} **Fluxos de trabalho**. - ![Captura de tela mostrando o item de menu 'Fluxos de Trabalho'](/assets/images/help/projects-v2/workflows-menu-item.png) -1. Em **Fluxos de trabalho padrão**, clique no fluxo de trabalho que deseja editar. - ![Captura de tela mostrando fluxos de trabalho padrão](/assets/images/help/projects-v2/default-workflows.png) -1. Se o fluxo de trabalho puder ser aplicado a problemas e solicitações de pull, ao lado de **Quando**, marque os tipos de itens em que deseja executar uma ação. - ![Captura de tela mostrando a configuração "quando" para um fluxo de trabalho](/assets/images/help/projects-v2/workflow-when.png) -1. Ao lado de **Definir**, escolha o valor com o qual deseja definir o status. - ![Captura de tela mostrando a configuração "definir" para um fluxo de trabalho](/assets/images/help/projects-v2/workflow-set.png) -1. Se o fluxo de trabalho estiver desabilitado, clique na alternância ao lado de **Desabilitado** para habilitar o fluxo de trabalho. - ![Captura de tela mostrando o controle "habilitar" para um fluxo de trabalho](/assets/images/help/projects-v2/workflow-enable.png) +{% data reusables.projects.access-workflows %} +1. Under **Default workflows**, click on the workflow that you want to edit. + + ![Screenshot showing default workflows](/assets/images/help/projects-v2/default-workflows.png) + +2. If the workflow can apply to both issues and pull requests, next to **When**, check the item type(s) that you want to act on. + + ![Screenshot showing the "when" configuration for a workflow](/assets/images/help/projects-v2/workflow-when.png) + +3. Next to **Set**, choose the value that you want to set the status to. + + ![Screenshot showing the "set" configuration for a workflow](/assets/images/help/projects-v2/workflow-set.png) + +4. If the workflow is disabled, click the toggle next to **Off** to enable the workflow. + + ![Screenshot showing the "On/Off" control for a workflow](/assets/images/help/projects-v2/workflow-enable.png) + diff --git a/translations/pt-BR/data/reusables/pull_requests/configure_pull_request_merges_intro.md b/translations/pt-BR/data/reusables/pull_requests/configure_pull_request_merges_intro.md index e5feed2709..48ec676b37 100644 --- a/translations/pt-BR/data/reusables/pull_requests/configure_pull_request_merges_intro.md +++ b/translations/pt-BR/data/reusables/pull_requests/configure_pull_request_merges_intro.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: d9e267c4a5a718fd45107ff259dd9499560d158e -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147875540" ---- -Você pode configurar as opções de merge de pull request no {% data variables.product.product_location %} para atender às suas necessidades de fluxo de trabalho e preferências para gerenciar o histórico do Git. Para obter mais informações, confira "[Como configurar mesclagens de solicitações de pull](/articles/configuring-pull-request-merges)". +You can configure pull request merge options on {% data variables.location.product_location %} to meet your workflow needs and preferences for managing Git history. For more information, see "[Configuring pull request merges](/articles/configuring-pull-request-merges)." diff --git a/translations/pt-BR/data/reusables/pull_requests/default_merge_option.md b/translations/pt-BR/data/reusables/pull_requests/default_merge_option.md index 854c1bfcff..7336d235d6 100644 --- a/translations/pt-BR/data/reusables/pull_requests/default_merge_option.md +++ b/translations/pt-BR/data/reusables/pull_requests/default_merge_option.md @@ -1,13 +1,5 @@ ---- -ms.openlocfilehash: 592835351230fe7a5587c0212811899ab496e84d -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147872777" ---- -Quando você clica na opção padrão **Mesclar solicitação de pull** em uma solicitação de pull no {% data variables.product.product_location %}, todos os commits do branch de recursos são adicionados ao branch base em um commit de mesclagem. A solicitação de pull é mesclada por meio [da opção `--no-ff`](https://git-scm.com/docs/git-merge#_fast_forward_merge). +When you click the default **Merge pull request** option on a pull request on {% data variables.location.product_location %}, all commits from the feature branch are added to the base branch in a merge commit. The pull request is merged using [the `--no-ff` option](https://git-scm.com/docs/git-merge#_fast_forward_merge). -Para mesclar as solicitações de pull, você precisa ter [permissões de gravação](/articles/repository-permission-levels-for-an-organization/) no repositório. +To merge pull requests, you must have [write permissions](/articles/repository-permission-levels-for-an-organization/) in the repository. ![standard-merge-commit-diagram](/assets/images/help/pull_requests/standard-merge-commit-diagram.png) diff --git a/translations/pt-BR/data/reusables/pull_requests/pull_request_merges_and_contributions.md b/translations/pt-BR/data/reusables/pull_requests/pull_request_merges_and_contributions.md index 2b8b0ac35b..e157092539 100644 --- a/translations/pt-BR/data/reusables/pull_requests/pull_request_merges_and_contributions.md +++ b/translations/pt-BR/data/reusables/pull_requests/pull_request_merges_and_contributions.md @@ -1,15 +1,7 @@ ---- -ms.openlocfilehash: fdea0ab10c821f00e16a11eb57a49415b4f5c908 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147882960" ---- {% note %} -**Observações:** {% ifversion ghes or ghae %} -- Para aparecer no gráfico de contribuições do seu perfil, os commits de criação conjunta devem atender aos mesmos critérios que os commits com um autor.{% endif %} -- Ao fazer rebase dos commits, os autores originais do commit e a pessoa que fez o rebase dos commits, seja na linha de comando ou em {% data variables.product.product_location %}, receberá o crédito de contribuição. +**Notes:**{% ifversion ghes or ghae %} +- To appear on your profile contributions graph, co-authored commits must meet the same criteria as commits with one author.{% endif %} +- When rebasing commits, the original authors of the commit and the person who rebased the commits, whether on the command line or on {% data variables.location.product_location %}, receive contribution credit. {% endnote %} diff --git a/translations/pt-BR/data/reusables/pull_requests/rebase_and_merge_summary.md b/translations/pt-BR/data/reusables/pull_requests/rebase_and_merge_summary.md index b2494a3dc9..93a7e1e17f 100644 --- a/translations/pt-BR/data/reusables/pull_requests/rebase_and_merge_summary.md +++ b/translations/pt-BR/data/reusables/pull_requests/rebase_and_merge_summary.md @@ -1,15 +1,7 @@ ---- -ms.openlocfilehash: 371057b7fbe8e92b564e8729b11442bdbf2c1a56 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147882792" ---- -Quando você seleciona a opção **Troca de base e mesclagem** em uma solicitação de pull no {% data variables.product.product_location %}, todos os commits do branch do tópico (ou do branch principal) são adicionados ao branch base individualmente sem um commit de mesclagem. Dessa forma, o comportamento de troca de base e mesclagem se assemelha a uma [mesclagem de avanço rápida](https://git-scm.com/docs/git-merge#_fast_forward_merge) mantendo um histórico de projeto linear. No entanto, a troca de base faz isso reescrevendo o histórico de commit no branch base com novos commits. +When you select the **Rebase and merge** option on a pull request on {% data variables.location.product_location %}, all commits from the topic branch (or head branch) are added onto the base branch individually without a merge commit. In that way, the rebase and merge behavior resembles a [fast-forward merge](https://git-scm.com/docs/git-merge#_fast_forward_merge) by maintaining a linear project history. However, rebasing achieves this by re-writing the commit history on the base branch with new commits. -O comportamento de troca de base e mesclagem no {% data variables.product.product_name %} se desvia ligeiramente de `git rebase`. A troca de base e a mesclagem no {% data variables.product.prodname_dotcom %} sempre atualizará as informações do autor de commit e criará novos SHAs de commit, enquanto o `git rebase` fora do {% data variables.product.prodname_dotcom %} não altera as informações do autor de commit quando a troca de base acontece com base em um commit ancestral. Para obter mais informações sobre `git rebase`, confira [git-rebase](https://git-scm.com/docs/git-rebase) na documentação do Git. +The rebase and merge behavior on {% data variables.product.product_name %} deviates slightly from `git rebase`. Rebase and merge on {% data variables.product.prodname_dotcom %} will always update the committer information and create new commit SHAs, whereas `git rebase` outside of {% data variables.product.prodname_dotcom %} does not change the committer information when the rebase happens on top of an ancestor commit. For more information about `git rebase`, see [git-rebase](https://git-scm.com/docs/git-rebase) in the Git documentation. -Para troca de base e mesclagem das solicitações de pull, você precisa ter [permissões de gravação](/articles/repository-permission-levels-for-an-organization/) no repositório e o repositório precisa [permitir a troca de base e a mesclagem](/articles/configuring-commit-rebasing-for-pull-requests/). +To rebase and merge pull requests, you must have [write permissions](/articles/repository-permission-levels-for-an-organization/) in the repository, and the repository must [allow rebase merging](/articles/configuring-commit-rebasing-for-pull-requests/). -Para ver uma representação visual de `git rebase`, confira [o capítulo "Ramificação do Git – Troca de base " do livro _Pro Git_](https://git-scm.com/book/en/Git-Branching-Rebasing). +For a visual representation of `git rebase`, see [The "Git Branching - Rebasing" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Branching-Rebasing). diff --git a/translations/pt-BR/data/reusables/pull_requests/squash_and_merge_summary.md b/translations/pt-BR/data/reusables/pull_requests/squash_and_merge_summary.md index 810d43c3da..b0f3fc47cc 100644 --- a/translations/pt-BR/data/reusables/pull_requests/squash_and_merge_summary.md +++ b/translations/pt-BR/data/reusables/pull_requests/squash_and_merge_summary.md @@ -1,15 +1,7 @@ ---- -ms.openlocfilehash: c7eea7975ef49a5a6e3deed2ade3cb6bb5543ac0 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145095430" ---- -Quando você seleciona a opção **Mesclar por squash e mesclar** em uma solicitação de pull no {% data variables.product.product_location %}, os commits da solicitação de pull são mesclados por squash em um só commit. Em vez de ver todos os commits individuais de um contribuidor de um branch de tópico, os commits são combinados em um commit e mesclados no branch-padrão. As solicitações de pull com commits mesclados por squash são mescladas com a [opção de avanço rápido](https://git-scm.com/docs/git-merge#_fast_forward_merge). +When you select the **Squash and merge** option on a pull request on {% data variables.location.product_location %}, the pull request's commits are squashed into a single commit. Instead of seeing all of a contributor's individual commits from a topic branch, the commits are combined into one commit and merged into the default branch. Pull requests with squashed commits are merged using the [fast-forward option](https://git-scm.com/docs/git-merge#_fast_forward_merge). -Para mesclar por squash e mesclar solicitações de pull, você precisa ter [permissões de gravação](/articles/repository-permission-levels-for-an-organization/) no repositório, e o repositório precisa [permitir a mesclagem squash](/articles/configuring-commit-squashing-for-pull-requests/). +To squash and merge pull requests, you must have [write permissions](/articles/repository-permission-levels-for-an-organization/) in the repository, and the repository must [allow squash merging](/articles/configuring-commit-squashing-for-pull-requests/). ![commit-squashing-diagram](/assets/images/help/pull_requests/commit-squashing-diagram.png) -Você pode usar combinação por squash e merge para criar um histórico de Git mais simplificado no seu repositório. Os commits de trabalho em andamento são úteis ao trabalhar em um branch de recurso, mas não são necessariamente importantes para manter no histórico do Git. Se você fizer a combinação por squash desses commits em um commit enquanto faz merge com o branch-padrão, você certamente poderá manter as alterações originais com um histórico Git. +You can use squash and merge to create a more streamlined Git history in your repository. Work-in-progress commits are helpful when working on a feature branch, but they aren’t necessarily important to retain in the Git history. If you squash these commits into one commit while merging to the default branch, you can retain the original changes with a clear Git history. diff --git a/translations/pt-BR/data/reusables/repositories/deploy-keys.md b/translations/pt-BR/data/reusables/repositories/deploy-keys.md index cd4349c0ab..595c8025c5 100644 --- a/translations/pt-BR/data/reusables/repositories/deploy-keys.md +++ b/translations/pt-BR/data/reusables/repositories/deploy-keys.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: f4ea2cee931b8d44b44f0febba3304f41bac404c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145084250" ---- -Você pode iniciar projetos por meio de um repositório no {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} para o servidor usando uma chave de implantação, que é uma chave SSH que permite acesso a um só repositório. {% data variables.product.product_name %} anexa a parte pública da chave diretamente ao repositório em vez de uma conta pessoal, e a parte privada da chave permanece no seu servidor. Para obter mais informações, confira "[Como entregar implantações](/rest/guides/delivering-deployments)". +You can launch projects from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} to your server by using a deploy key, which is an SSH key that grants access to a single repository. {% data variables.product.product_name %} attaches the public part of the key directly to your repository instead of a personal account, and the private part of the key remains on your server. For more information, see "[Delivering deployments](/rest/guides/delivering-deployments)." diff --git a/translations/pt-BR/data/reusables/repositories/enable-security-alerts.md b/translations/pt-BR/data/reusables/repositories/enable-security-alerts.md index f2ebbd4070..ff83465bcd 100644 --- a/translations/pt-BR/data/reusables/repositories/enable-security-alerts.md +++ b/translations/pt-BR/data/reusables/repositories/enable-security-alerts.md @@ -1,10 +1,3 @@ ---- -ms.openlocfilehash: 6151a441ef782d82bde352a9761dbd19b239447c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "146455698" ---- -Proprietários do {% ifversion ghes or ghae %} Enterprise devem habilitar {% data variables.product.prodname_dependabot_alerts %} para o {% data variables.product.product_location %} ante de usar esse recurso. Para obter mais informações, confira "[Como habilitar o {% data variables.product.prodname_dependabot %} para sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)". +{% ifversion ghes or ghae %} +Enterprise owners must enable {% data variables.product.prodname_dependabot_alerts %} for {% data variables.location.product_location %} before you can use this feature. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% endif %} diff --git a/translations/pt-BR/data/reusables/repositories/navigate-to-repo.md b/translations/pt-BR/data/reusables/repositories/navigate-to-repo.md index 20c50eef90..6069ceab1f 100644 --- a/translations/pt-BR/data/reusables/repositories/navigate-to-repo.md +++ b/translations/pt-BR/data/reusables/repositories/navigate-to-repo.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: c76385e14b4b841b3e24342316a3026b3cd025d8 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145084231" ---- -1. No {% data variables.product.product_location %}, navegue até a página principal do repositório. +1. On {% data variables.location.product_location %}, navigate to the main page of the repository. diff --git a/translations/pt-BR/data/reusables/repositories/you-can-fork.md b/translations/pt-BR/data/reusables/repositories/you-can-fork.md index b9b87242d9..a38402202e 100644 --- a/translations/pt-BR/data/reusables/repositories/you-can-fork.md +++ b/translations/pt-BR/data/reusables/repositories/you-can-fork.md @@ -1,14 +1,9 @@ ---- -ms.openlocfilehash: 7ab0c705855f1bd271c17eacc9a2533184d1b5f1 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145095250" ---- -{% ifversion ghae %}Se as políticas da sua empresa permitirem a criação de forks privados e repositórios internos, você poderá criar forks de um repositório para sua conta pessoal ou para qualquer organização em que tenha permissões de criação de repositórios. Para obter mais informações, confira "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)". +{% ifversion ghae %} +If the policies for your enterprise permit forking private and internal repositories, you can fork a repository to your personal account or an organization where you have repository creation permissions. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." -{% elsif ghes or ghec %} Você poderá criar forks de um repositório privado ou interno para sua conta pessoal ou uma organização no {% data variables.product.product_location %} em que tem permissões de criação de repositório se as configurações para o repositório e suas políticas corporativas permitirem a criação de fork. +{% elsif ghes or ghec %} +You can fork a private or internal repository to your personal account or an organization on {% data variables.location.product_location %} where you have repository creation permissions, if settings for the repository and your enterprise policies allow forking. -{% elsif fpt %} Se você tiver acesso a um repositório privado e o proprietário permitir a criação de fork, poderá criar fork do repositório para sua conta pessoal ou uma organização no {% data variables.product.prodname_team %} em que terá permissões de criação de repositório. Não é possível criar forks de um repositório privado em uma organização que usa o {% data variables.product.prodname_free_team %}. Para obter mais informações, confira "[Produtos do GitHub](/articles/githubs-products)". +{% elsif fpt %} +If you have access to a private repository and the owner permits forking, you can fork the repository to your personal account, or an organization on {% data variables.product.prodname_team %} where you have repository creation permissions. You cannot fork a private repository to an organization using {% data variables.product.prodname_free_team %}. For more information, see "[GitHub's products](/articles/githubs-products)." {% endif %} diff --git a/translations/pt-BR/data/reusables/rest-api/dotcom-only-guide-note.md b/translations/pt-BR/data/reusables/rest-api/dotcom-only-guide-note.md index d1150640c1..86e1a648f1 100644 --- a/translations/pt-BR/data/reusables/rest-api/dotcom-only-guide-note.md +++ b/translations/pt-BR/data/reusables/rest-api/dotcom-only-guide-note.md @@ -1,20 +1,12 @@ ---- -ms.openlocfilehash: 5cbc48e80c619e40633c439535319ebf617c7d04 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145095245" ---- {% ifversion not fpt or ghec %} {% note %} -**Observação**: o guia a seguir usa a API REST para o {% data variables.product.prodname_dotcom_the_website %}. +**Note**: The following guide uses the REST API for {% data variables.product.prodname_dotcom_the_website %}. -- Use {% data variables.product.api_url_pre %} para acessar a API para o {% data variables.product.product_name %}. +- Use {% data variables.product.api_url_pre %} to access the API for {% data variables.product.product_name %}. -- O guia especifica nomes de usuário e repositórios que podem não existir em {% data variables.product.product_location %}. Talvez você precise usar nomes diferentes para ver a saída semelhante. +- The guide specifies usernames and repositories that may not exist on {% data variables.location.product_location %}. You may need to use different names to see similar output. {% endnote %} diff --git a/translations/pt-BR/data/reusables/saml/about-authorized-credentials.md b/translations/pt-BR/data/reusables/saml/about-authorized-credentials.md index df3767626b..87664ef3bc 100644 --- a/translations/pt-BR/data/reusables/saml/about-authorized-credentials.md +++ b/translations/pt-BR/data/reusables/saml/about-authorized-credentials.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: ac85c101df8f64a7d5e69202cd0c5280bb956b96 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145127568" ---- -Você pode ver cada token de acesso pessoal e a chave SSH que um integrante autorizou para obter acesso à API e ao Git. Somente os últimos caracteres de cada token ou chave são visíveis. Se necessário, trabalhe com o integrante para determinar quais credenciais você deve revogar. +You can see each {% data variables.product.pat_generic %} and SSH key that a member has authorized for API and Git access. Only the last several characters of each token or key are visible. If necessary, work with the member to determine which credentials you should revoke. diff --git a/translations/pt-BR/data/reusables/saml/about-linked-identities.md b/translations/pt-BR/data/reusables/saml/about-linked-identities.md index 77c3f1432e..e1a8512bad 100644 --- a/translations/pt-BR/data/reusables/saml/about-linked-identities.md +++ b/translations/pt-BR/data/reusables/saml/about-linked-identities.md @@ -1,11 +1,3 @@ ---- -ms.openlocfilehash: bb556d0f51869d61db7d0aa1fcaa4c294303581d -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145095239" ---- -Você pode ver a identidade de logon único que um membro vinculou à conta dele no {% data variables.product.product_location %}. +You can view the single sign-on identity that a member has linked to their account on {% data variables.location.product_location %}. -Se um membro vincular a identidade errada à conta dele no {% data variables.product.product_location %}, você poderá revogar a identidade vinculada para permitir que o membro repita a operação. +If a member links the wrong identity to their account on {% data variables.location.product_location %}, you can revoke the linked identity to allow the member to try again. diff --git a/translations/pt-BR/data/reusables/saml/about-saml-access-enterprise-account.md b/translations/pt-BR/data/reusables/saml/about-saml-access-enterprise-account.md index 9d52a74330..08cacea2fa 100644 --- a/translations/pt-BR/data/reusables/saml/about-saml-access-enterprise-account.md +++ b/translations/pt-BR/data/reusables/saml/about-saml-access-enterprise-account.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 94a2fb153d6929e6e319a10b95dfb4fb99ab949d -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145127567" ---- -Para acessar os recursos de cada organização em {% data variables.product.product_name %}, o integrante deve ter uma sessão SAML ativa no navegador. Para acessar os recursos protegidos de cada organização usando a API e o Git, o integrante deve usar um token de acesso pessoal ou chave SSH que o integrante autorizou a usar com a organização. Os proprietários da empresa podem ver e revogar a identidade vinculada de um integrante, sessões ativas ou credenciais autorizadas a qualquer momento. +To access each organization's resources on {% data variables.product.product_name %}, the member must have an active SAML session in their browser. To access each organization's protected resources using the API and Git, the member must use a {% data variables.product.pat_generic %} or SSH key that the member has authorized for use with the organization. Enterprise owners can view and revoke a member's linked identity, active sessions, or authorized credentials at any time. diff --git a/translations/pt-BR/data/reusables/saml/authorized-creds-info.md b/translations/pt-BR/data/reusables/saml/authorized-creds-info.md index 652844609c..5f5411ce06 100644 --- a/translations/pt-BR/data/reusables/saml/authorized-creds-info.md +++ b/translations/pt-BR/data/reusables/saml/authorized-creds-info.md @@ -1,15 +1,7 @@ ---- -ms.openlocfilehash: 4055717eec0cdd95951ec6fb5bdea20efaed1948 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147573374" ---- -Para autorizar um token de acesso pessoal ou uma chave SSH, você precisa ter uma identidade vinculada do SAML. Se você for membro de uma organização em que o SSO do SAML está habilitado, você pode criar uma identidade vinculada autenticando-se na sua organização com o IdP pelo menos uma vez. Para obter mais informações, confira "[Sobre a autenticação com o logon único do SAML](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)". +Before you can authorize a {% data variables.product.pat_generic %} or SSH key, you must have a linked SAML identity. If you're a member of an organization where SAML SSO is enabled, you can create a linked identity by authenticating to your organization with your IdP at least once. For more information, see "[About authentication with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)." -Depois de autorizar um token de acesso pessoal ou chave SSH, o token ou chave permanecerá autorizado até que seja revogado de uma das maneiras a seguir. -- Um proprietário da empresa ou da organização revoga a autorização. -- Você é removido da organização. -- Os escopos em um token de acesso pessoal são editados ou o token é regenerado. -- O token de acesso pessoal venceu, conforme definido durante a criação. +After you authorize a {% data variables.product.pat_generic %} or SSH key, the token or key will stay authorized until revoked in one of the following ways. +- An organization or enterprise owner revokes the authorization. +- You are removed from the organization. +- The scopes in a {% data variables.product.pat_generic %} are edited, or the token is regenerated. +- The {% data variables.product.pat_generic %} expired as defined during creation. diff --git a/translations/pt-BR/data/reusables/saml/must-authorize-linked-identity.md b/translations/pt-BR/data/reusables/saml/must-authorize-linked-identity.md index 8edc0a71c3..5854c09d77 100644 --- a/translations/pt-BR/data/reusables/saml/must-authorize-linked-identity.md +++ b/translations/pt-BR/data/reusables/saml/must-authorize-linked-identity.md @@ -1,13 +1,5 @@ ---- -ms.openlocfilehash: 46bffdc7594863d282ba171fc258f4104a0a09b4 -ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/12/2022 -ms.locfileid: "147067847" ---- {% note %} -**Observação:** se você tiver uma identidade vinculada para uma organização, só poderá usar tokens de acesso pessoal autorizados e chaves SSH com essa organização, mesmo que o SAML não seja imposto. Você terá uma identidade vinculada para uma organização se já tiver se autenticado por meio do SSO do SAML para essa organização, a menos que um proprietário da organização ou da empresa tenha revogado a identidade vinculada posteriormente. Para obter mais informações sobre como revogar identidades vinculadas, confira "[Como ver e gerenciar o acesso do SAML de um membro à sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" e "[Como ver e gerenciar o acesso do SAML de um usuário à sua empresa](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)". +**Note:** If you have a linked identity for an organization, you can only use authorized {% data variables.product.pat_generic %}s and SSH keys with that organization, even if SAML is not enforced. You have a linked identity for an organization if you've ever authenticated via SAML SSO for that organization, unless an organization or enterprise owner later revoked the linked identity. For more information about revoking linked identities, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" and "[Viewing and managing a user's SAML access to your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)." {% endnote %} diff --git a/translations/pt-BR/data/reusables/saml/you-must-periodically-authenticate.md b/translations/pt-BR/data/reusables/saml/you-must-periodically-authenticate.md index f48e8f2ad7..7d345990f4 100644 --- a/translations/pt-BR/data/reusables/saml/you-must-periodically-authenticate.md +++ b/translations/pt-BR/data/reusables/saml/you-must-periodically-authenticate.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: a58f8cdbd481991312d9bce77e1cd41a35ffad75 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145126401" ---- -Você precisa se autenticar periodicamente no IdP do SAML para se autenticar e obter acesso aos {% ifversion fpt or ghec %}recursos da organização no {% data variables.product.prodname_dotcom_the_website %}{% elsif ghae %}{% data variables.product.product_location %}{% endif %}. A duração desse período de login é especificado pelo seu IdP e geralmente é de 24 horas. Esse requisito de login periódico limita a duração do acesso e exige que você identifique-se novamente para continuar. {% ifversion fpt or ghec %}Você pode ver e gerenciar suas sessões ativas do SAML nas configurações de segurança. Para obter mais informações, confira "[Como ver e gerenciar suas sessões ativas do SAML](/articles/viewing-and-managing-your-active-saml-sessions)".{% endif %} +You must periodically authenticate with your SAML IdP to authenticate and gain access to {% ifversion fpt or ghec %}the organization's resources on {% data variables.product.prodname_dotcom_the_website %}{% elsif ghae %}{% data variables.location.product_location %}{% endif %}. The duration of this login period is specified by your IdP and is generally 24 hours. This periodic login requirement limits the length of access and requires you to re-identify yourself to continue. {% ifversion fpt or ghec %}You can view and manage your active SAML sessions in your security settings. For more information, see "[Viewing and managing your active SAML sessions](/articles/viewing-and-managing-your-active-saml-sessions)."{% endif %} diff --git a/translations/pt-BR/data/reusables/scim/enterprise-account-scim.md b/translations/pt-BR/data/reusables/scim/enterprise-account-scim.md index 9f65c8d636..ac08a28b7d 100644 --- a/translations/pt-BR/data/reusables/scim/enterprise-account-scim.md +++ b/translations/pt-BR/data/reusables/scim/enterprise-account-scim.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: e53e61c7e5f6b12e9510b78251b68dea902eac9d -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147875611" ---- -Você não pode usar essa implementação do SCIM com uma conta corporativa ou com um {% data variables.product.prodname_emu_org %}. Se a sua empresa estiver habilitada para {% data variables.product.prodname_emus %}, você deverá usar uma implementação diferente do SCIM. Caso contrário, o SCIM não estará disponível no nível empresarial. Para saber mais, confira "[Configurar o provisionamento scim para {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users).". +You cannot use this implementation of SCIM with an enterprise account or with an {% data variables.enterprise.prodname_emu_org %}. If your enterprise is enabled for {% data variables.product.prodname_emus %}, you must use a different implementation of SCIM. Otherwise, SCIM is not available at the enterprise level. For more information, see "[Configuring SCIM provisioning for {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)." diff --git a/translations/pt-BR/data/reusables/scim/supported-idps.md b/translations/pt-BR/data/reusables/scim/supported-idps.md index 8ab4908643..1243cee7b5 100644 --- a/translations/pt-BR/data/reusables/scim/supported-idps.md +++ b/translations/pt-BR/data/reusables/scim/supported-idps.md @@ -1,13 +1,6 @@ ---- -ms.openlocfilehash: 4dfd2a37e834cd7331131d655545160b8ff2ef7f -ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/12/2022 -ms.locfileid: "145126288" ---- -Os seguintes IdPs podem provisionar ou desprovisionar contas de usuário em {% data variables.product.product_location %} usando o SCIM. +The following IdPs can provision or deprovision user accounts on {% data variables.location.product_location %} using SCIM. {% ifversion ghae %} - Azure AD -- Okta (atualmente em versão beta) {% endif %} +- Okta (currently in beta) +{% endif %} diff --git a/translations/pt-BR/data/reusables/search/syntax_tips.md b/translations/pt-BR/data/reusables/search/syntax_tips.md index 50372f3426..8eedc169a7 100644 --- a/translations/pt-BR/data/reusables/search/syntax_tips.md +++ b/translations/pt-BR/data/reusables/search/syntax_tips.md @@ -1,16 +1,8 @@ ---- -ms.openlocfilehash: b3ef2ec170753526500b4aab081227267c2dcd3d -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147875610" ---- {% tip %} -**Tips:** {% ifversion ghes or ghae %} - - Este artigo contém links para pesquisas de exemplo no site de {% data variables.product.prodname_dotcom_the_website %}, mas você pode usar os mesmos filtros de pesquisa com {% data variables.product.product_name %}. Nos exemplos de pesquisas vinculadas, substitua `github.com` pelo nome do host do {% data variables.product.product_location %}.{% endif %} - - Para ver uma lista de sintaxes de pesquisa que você pode adicionar a qualquer qualificador de pesquisa para aprimorar ainda mais os resultados, confira "[Noções básicas sobre a sintaxe de pesquisa](/articles/understanding-the-search-syntax)". - - Use aspas em termos de pesquisa com várias palavras. Por exemplo, caso deseje pesquisar problemas com o rótulo "Em andamento", pesquise `label:"in progress"`. A pesquisa não faz distinção entre maiúsculas e minúsculas. +**Tips:**{% ifversion ghes or ghae %} + - This article contains links to example searches on the {% data variables.product.prodname_dotcom_the_website %} website, but you can use the same search filters with {% data variables.product.product_name %}. In the linked example searches, replace `github.com` with the hostname for {% data variables.location.product_location %}.{% endif %} + - For a list of search syntaxes that you can add to any search qualifier to further improve your results, see "[Understanding the search syntax](/articles/understanding-the-search-syntax)". + - Use quotations around multi-word search terms. For example, if you want to search for issues with the label "In progress," you'd search for `label:"in progress"`. Search is not case sensitive. {% endtip %} diff --git a/translations/pt-BR/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md b/translations/pt-BR/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md index 7f1c750998..e4513c6c98 100644 --- a/translations/pt-BR/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md +++ b/translations/pt-BR/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md @@ -2,7 +2,7 @@ {% note %} -**Note:** Your site administrator must enable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/enterprise/admin/configuration/configuring-secret-scanning-for-your-appliance)." +**Note:** Your site administrator must enable {% data variables.product.prodname_secret_scanning %} for {% data variables.location.product_location %} before you can use this feature. For more information, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/enterprise/admin/configuration/configuring-secret-scanning-for-your-appliance)." {% ifversion security-feature-enablement-policies %} You may not be able to enable or disable {% data variables.product.prodname_secret_scanning %}, if an enterprise owner has set a policy at the enterprise level. For more information, see "[Enforcing policies for code security and analysis for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise)."{% endif %} {% endnote %} diff --git a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md index f70ad1c9c4..eb5a2953b2 100644 --- a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -17,8 +17,12 @@ Atlassian | Atlassian JSON Web Token | atlassian_jwt Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} Azure | Azure Active Directory Application Secret | azure_active_directory_application_secret{% endif %} +{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %} +Azure | Azure Batch Key Identifiable | azure_batch_key_identifiable{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} Azure | Azure Cache for Redis Access Key | azure_cache_for_redis_access_key{% endif %} +{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %} +Azure | Azure CosmosDB Key Identifiable | azure_cosmosdb_key_identifiable{% endif %} Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token {%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %} Azure | Azure ML Studio (classic) Web Service Key | azure_ml_studio_classic_web_service_key{% endif %} diff --git a/translations/pt-BR/data/reusables/secret-scanning/secret-list-private-push-protection.md b/translations/pt-BR/data/reusables/secret-scanning/secret-list-private-push-protection.md index e73196547f..a2a86f557f 100644 --- a/translations/pt-BR/data/reusables/secret-scanning/secret-list-private-push-protection.md +++ b/translations/pt-BR/data/reusables/secret-scanning/secret-list-private-push-protection.md @@ -8,7 +8,11 @@ Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary A Asana | Asana Personal Access Token | asana_personal_access_token Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token Azure | Azure Active Directory Application Secret | azure_active_directory_application_secret +{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %} +Azure | Azure Batch Key Identifiable | azure_batch_key_identifiable{% endif %} Azure | Azure Cache for Redis Access Key | azure_cache_for_redis_access_key +{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %} +Azure | Azure CosmosDB Key Identifiable | azure_cosmosdb_key_identifiable{% endif %} Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token {%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %} Azure | Azure ML Studio (classic) Web Service Key | azure_ml_studio_classic_web_service_key{% endif %} diff --git a/translations/pt-BR/data/reusables/shortdesc/rate_limits_github_apps.md b/translations/pt-BR/data/reusables/shortdesc/rate_limits_github_apps.md index a6a4ec3b76..499de3d2f5 100644 --- a/translations/pt-BR/data/reusables/shortdesc/rate_limits_github_apps.md +++ b/translations/pt-BR/data/reusables/shortdesc/rate_limits_github_apps.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 5a00eb01f4e2c9ec707f5bbc7c5794c8108220e4 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145128141" ---- -Os limites de taxa do {% data variables.product.prodname_github_apps %} e do {% data variables.product.prodname_oauth_apps %} ajudam a controlar a taxa de tráfego para o {% data variables.product.product_location %}. +Rate limits for {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} help control the rate of traffic to {% data variables.location.product_location %}. diff --git a/translations/pt-BR/data/reusables/sponsors/select-sponsorship-billing.md b/translations/pt-BR/data/reusables/sponsors/select-sponsorship-billing.md index 0a3bd743c5..26b44ffe79 100644 --- a/translations/pt-BR/data/reusables/sponsors/select-sponsorship-billing.md +++ b/translations/pt-BR/data/reusables/sponsors/select-sponsorship-billing.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: aa5db374baed1496a9aa74205d7d19aabd75179d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145128105" ---- -4. Em "Billing information" (Informações de cobrança), revise as informações do pagamento. Opcionalmente, para alterar os detalhes de pagamento de toda a sua conta em {% data variables.product.product_location %}, clique em **Editar**. Em seguida, siga as instruções para preencher o formulário de pagamento. +4. Under "Billing information", review your payment details. Optionally, to change the payment details for your entire account on {% data variables.location.product_location %}, click **Edit**. Then, follow the prompts to complete the payment form. diff --git a/translations/pt-BR/data/reusables/ssh/about-ssh.md b/translations/pt-BR/data/reusables/ssh/about-ssh.md index 8d8978e065..95040d6fd3 100644 --- a/translations/pt-BR/data/reusables/ssh/about-ssh.md +++ b/translations/pt-BR/data/reusables/ssh/about-ssh.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: d7184796459936c64db3513a123f383c43caf4b6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147409747" ---- -Você pode acessar e gravar dados em repositórios em dados {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} usando o SSH (Protocolo Secure Shell). Ao se conectar por meio do SSH, você se autentica usando um arquivo de chave privada no computador local. +You can access and write data in repositories on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} using SSH (Secure Shell Protocol). When you connect via SSH, you authenticate using a private key file on your local machine. diff --git a/translations/pt-BR/data/reusables/ssh/key-type-support.md b/translations/pt-BR/data/reusables/ssh/key-type-support.md index 7f859774ef..324873282a 100644 --- a/translations/pt-BR/data/reusables/ssh/key-type-support.md +++ b/translations/pt-BR/data/reusables/ssh/key-type-support.md @@ -1,18 +1,11 @@ ---- -ms.openlocfilehash: 621dfdbcdc0585f51536c924e1e5d0d9a140ff26 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147410648" ---- -{% ifversion fpt or ghec %} {% note %} +{% ifversion fpt or ghec %} +{% note %} -**Observação:** o {% data variables.product.company_short %} aprimorou a segurança removendo tipos de chaves mais antigos e não seguros em 15 de março de 2022. +**Note:** {% data variables.product.company_short %} improved security by dropping older, insecure key types on March 15, 2022. -Desde essa data, não há mais suporte para as chaves DSA (`ssh-dss`). Não é possível adicionar novas chaves DSA à sua conta pessoal do {% data variables.product.product_location %}. +As of that date, DSA keys (`ssh-dss`) are no longer supported. You cannot add new DSA keys to your personal account on {% data variables.location.product_location %}. -As chaves RSA (`ssh-rsa`) com um `valid_after` antes de 2 de novembro de 2021 podem continuar usando qualquer algoritmo de assinatura. As chaves RSA geradas após essa data precisam usar um algoritmo de assinatura SHA-2. Talvez alguns clientes mais antigos precisem ser atualizados para usar as assinaturas SHA-2. +RSA keys (`ssh-rsa`) with a `valid_after` before November 2, 2021 may continue to use any signature algorithm. RSA keys generated after that date must use a SHA-2 signature algorithm. Some older clients may need to be upgraded in order to use SHA-2 signatures. {% endnote %} @@ -20,15 +13,15 @@ As chaves RSA (`ssh-rsa`) com um `valid_after` antes de 2 de novembro de 2021 po {% note %} -**Observação**: por padrão, com {% data variables.product.product_name %} 3.6 e versões posteriores, a partir da data de corte de meia-noite UTC, em 1º de agosto de 2022, as conexões SSH que atenderem às **duas** condições a seguir falharão. +**Note**: By default with {% data variables.product.product_name %} 3.6 and later, as of the cutoff date of midnight UTC on August 1, 2022, SSH connections that satisfy **both** of the following conditions will fail.
{% data reusables.ssh.rsa-sha-1-connection-failure-criteria %} -{% data variables.product.product_name %} 3.6 e versões posteriores também não dão suporte a conexões SSH que usam criptografias DSA, HMAC-SHA-1 ou CBC. As chaves SSH RSA carregadas antes da data de corte podem continuar sendo autenticadas usando a função de hash SHA-1, desde que a chave permaneça válida. Para obter mais informações sobre como encontrar a versão de {% data variables.product.product_name %} que você usa, confira "[Sobre versões de {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)." +{% data variables.product.product_name %} 3.6 and later also does not support SSH connections that use DSA, HMAC-SHA-1, or CBC ciphers. RSA SSH keys uploaded before the cutoff date can continue to authenticate using the SHA-1 hash function as long as the key remains valid. For more information about finding the version of {% data variables.product.product_name %} that you use, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)." -O administrador do site pode ajustar a data de corte para conexões que usam RSA-SHA-1 e pode bloquear todas as conexões que usam RSA-SHA-1. Para obter mais informações, entre em contato com o administrador do site ou confira "[Como configurar conexões SSH com sua instância](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)". +Your site administrator can adjust the cutoff date for connections using RSA-SHA-1, and may block all connections using RSA-SHA-1. For more information, contact your site administrator or see "[Configuring SSH connections to your instance](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)." {% endnote %} diff --git a/translations/pt-BR/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md b/translations/pt-BR/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md index 1540283930..b08eeab7b8 100644 --- a/translations/pt-BR/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md +++ b/translations/pt-BR/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md @@ -1,10 +1,2 @@ ---- -ms.openlocfilehash: 51813ab823a86fe6428d31b3fd4f80f81458dc23 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147409746" ---- -- A chave RSA foi adicionada a uma conta de usuário em {% data variables.product.product_location %} após a data de corte de meia-noite UTC em 1º de agosto de 2022. -- O cliente SSH assina a tentativa de conexão com a função de hash SHA-1. +- The RSA key was added to a user account on {% data variables.location.product_location %} after the cutoff date of midnight UTC on August 1, 2022. +- The SSH client signs the connection attempt with the SHA-1 hash function. diff --git a/translations/pt-BR/data/reusables/support/submit-a-ticket.md b/translations/pt-BR/data/reusables/support/submit-a-ticket.md index 5e8c7ce5d3..e9b27b7fc5 100644 --- a/translations/pt-BR/data/reusables/support/submit-a-ticket.md +++ b/translations/pt-BR/data/reusables/support/submit-a-ticket.md @@ -1,44 +1,45 @@ ---- -ms.openlocfilehash: b7f16729209b711d9ea95d059f5868ae867fa040 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147419878" ---- -1. Selecione o menu suspenso **Conta ou organização** e clique no nome da conta à qual seu tíquete de suporte está relacionado. -![Captura de tela do menu suspenso "Conta ou organização".](/assets/images/help/support/account-field.png) -1. Selecione o menu suspenso **De** e clique no endereço de email com o qual deseja que o {% data variables.contact.github_support %} entre em contato. -![Captura de tela do menu suspenso "De".](/assets/images/help/support/from-field.png) +1. Select the **Account or organization** dropdown menu and click the name of the account your support ticket is regarding. +![Screenshot of the "Account or organization" dropdown menu.](/assets/images/help/support/account-field.png) +1. Select the **From** drop-down menu and click the email address you'd like {% data variables.contact.github_support %} to contact. +![Screenshot of the "From" dropdown menu.](/assets/images/help/support/from-field.png) {%- ifversion ghec or ghes %} -1. Selecione o menu suspenso **Produto** e clique em {% ifversion ghes %}**GitHub Enterprise Server (auto-hospedado)** {% else %}**GitHub Enterprise Cloud**{% endif %}. -{% ifversion ghec %}![Captura de tela do menu suspenso "Produto".](/assets/images/help/support/product-field-ghec.png){% else %}![Captura de tela do menu suspenso "Produto".](/assets/images/help/support/product-field.png){% endif %} {%- endif %} {%- ifversion ghes %} -1. Se solicitado, selecione o menu suspenso **Instalação do servidor** e clique na instalação à qual seu tíquete de suporte está relacionada. Se a instalação não estiver listada, clique em **Outros**. -![Captura de tela do menu suspenso "Instalação do Servidor"](/assets/images/help/support/installation-field.png) {%- endif %} {%- ifversion ghes %} -1. Selecione o menu suspenso **Série da versão** e clique na versão executada pelo {% data variables.product.product_location_enterprise %}. -![Captura de tela do menu suspenso "Série da versão"](/assets/images/help/support/release-field.png) {%- endif %} {%- ifversion ghes or ghec %} -1. Selecione o menu suspenso **Prioridade** clique na urgência apropriada. Para obter mais informações, confira "[Sobre a prioridade de tíquetes](/support/learning-about-github-support/about-ticket-priority)". - ![Captura de tela do menu suspenso "Prioridade".](/assets/images/help/support/priority-field.png) -{%- endif %} {%- ifversion ghes %} - - Escolha **{% data variables.product.support_ticket_priority_urgent %}** para relatar {% ifversion fpt or ghec %}falhas críticas do sistema{% else %}falhas fatais do sistema, interrupções que afetam operações críticas do sistema, incidentes de segurança e licenças vencidas{% endif %}. - - Escolha **{% data variables.product.support_ticket_priority_high %}** para relatar problemas que afetam operações de negócios, incluindo {% ifversion fpt or ghec %}remoção de dados confidenciais (commits, problemas, solicitações de pull, anexos carregados) das suas contas e restaurações da organização{% else %}problemas de desempenho do sistema{% endif %} ou para relatar bugs críticos. - - Escolha **{% data variables.product.support_ticket_priority_normal %}** para {% ifversion fpt or ghec %}solicitar a recuperação de conta ou a remoção de sinalizador de spam, relatar problemas de logon do usuário{% else %}fazer solicitações técnicas, como alterações de configuração e integrações de terceiros{% endif %} e para relatar bugs não críticos. - - Escolha **{% data variables.product.support_ticket_priority_low %}** para fazer perguntas gerais e enviar solicitações de novos recursos, compras, treinamento ou verificações de integridade. -{%- endif %} {%- ifversion ghes or ghec %} -1. Opcionalmente, se a sua conta incluir o {% data variables.contact.premium_support %} e seu tíquete for {% ifversion ghes %}urgente ou de alta{% elsif ghec %}de alta{% endif %} prioridade, você poderá solicitar um retorno de chamada em inglês. Selecione **Solicitar um retorno de chamada do Suporte do GitHub**, escolha o menu suspenso Código do país para escolher seu país e insira seu número de telefone. -![Captura de tela da caixa de seleção "Solicitar retorno de chamada", do menu suspenso "Código do país" e da caixa de texto "Número de telefone".](/assets/images/help/support/request-callback.png) +1. Select the **Product** dropdown menu and click {% ifversion ghes %}**GitHub Enterprise Server (self-hosted)**{% else %}**GitHub Enterprise Cloud**{% endif %}. +{% ifversion ghec %}![Screenshot of the "Product" dropdown menu.](/assets/images/help/support/product-field-ghec.png){% else %}![Screenshot of the "Product" dropdown menu.](/assets/images/help/support/product-field.png){% endif %} {%- endif %} -1. Em "Subject" (Assunto), insira um título descritivo para o problema que está ocorrendo. -![Captura de tela da caixa de texto "Assunto".](/assets/images/help/support/subject-field.png) -1. Em "How can we help" (Como podemos ajudar), insira as informações adicionais que ajudarão a equipe de suporte a resolver o problema. Use o Markdown para formatar sua mensagem. - ![Captura de tela da área de texto "Como podemos ajudar".](/assets/images/help/support/how-can-we-help-field.png) - Informações úteis podem incluir: - - Etapas para reproduzir o problema - - Quaisquer circunstâncias especiais em torno da descoberta do problema (por exemplo, a primeira ocorrência ou ocorrência após um evento específico, a frequência de ocorrência, o impacto nos negócios do problema e a urgência sugerida) - - Redação exata de mensagens de erro {% indented_data_reference reusables.repositories.anyone-can-view-anonymized-url spaces=3 %} +{%- ifversion ghes %} +1. If prompted, select the **Server installation** dropdown menu and click the installation your support ticket is regarding. If the installation is not listed, click **Other**. +![Screenshot of the "Server Installation" dropdown menu](/assets/images/help/support/installation-field.png) +{%- endif %} +{%- ifversion ghes %} +1. Select the **Release series** dropdown menu and click the release {% data variables.location.product_location_enterprise %} is running. +![Screenshot of the "Release series" dropdown menu](/assets/images/help/support/release-field.png) +{%- endif %} +{%- ifversion ghes or ghec %} +1. Select the **Priority** dropdown menu and click the appropriate urgency. For more information, see "[About ticket priority](/support/learning-about-github-support/about-ticket-priority)." + ![Screenshot of the "Priority" dropdown menu.](/assets/images/help/support/priority-field.png) +{%- endif %} +{%- ifversion ghes %} + - Choose **{% data variables.product.support_ticket_priority_urgent %}** to report {% ifversion fpt or ghec %}critical system failure{% else %}fatal system failures, outages impacting critical system operations, security incidents, and expired licenses{% endif %}. + - Choose **{% data variables.product.support_ticket_priority_high %}** to report issues impacting business operations, including {% ifversion fpt or ghec %}removing sensitive data (commits, issues, pull requests, uploaded attachments) from your own accounts and organization restorations{% else %}system performance issues{% endif %}, or to report critical bugs. + - Choose **{% data variables.product.support_ticket_priority_normal %}** to {% ifversion fpt or ghec %}request account recovery or spam unflagging, report user login issues{% else %}make technical requests like configuration changes and third-party integrations{% endif %}, and to report non-critical bugs. + - Choose **{% data variables.product.support_ticket_priority_low %}** to ask general questions and submit requests for new features, purchases, training, or health checks. +{%- endif %} +{%- ifversion ghes or ghec %} +1. Optionally, if your account includes {% data variables.contact.premium_support %} and your ticket is {% ifversion ghes %}urgent or high{% elsif ghec %}high{% endif %} priority, you can request a callback in English. Select **Request a callback from GitHub Support**, select the country code dropdown menu to choose your country, and enter your phone number. +![Screenshot of the "Request callback" checkbox, "Country code" dropdown menu, and "Phone number" text box.](/assets/images/help/support/request-callback.png) +{%- endif %} +1. Under "Subject", type a descriptive title for the issue you're having. +![Screenshot of the "Subject" text box.](/assets/images/help/support/subject-field.png) +1. Under "How can we help", provide any additional information that will help the Support team troubleshoot the problem. You can use markdown to format your message. + ![Screenshot of the "How can we help" text area.](/assets/images/help/support/how-can-we-help-field.png) + Helpful information may include: + - Steps to reproduce the issue + - Any special circumstances surrounding the discovery of the issue (for example, the first occurrence or occurrence after a specific event, frequency of occurrence, business impact of the problem, and suggested urgency) + - Exact wording of error messages +{% indented_data_reference reusables.repositories.anyone-can-view-anonymized-url spaces=3 %} {%- ifversion ghes %} -1. Opcionalmente, anexe arquivos de diagnóstico e outros arquivos arrastando e soltando, carregando ou colando o conteúdo da área de transferência. +1. Optionally, attach diagnostics files and other files by dragging and dropping, uploading, or pasting from the clipboard. {%- endif %} -1. Clique em **Enviar solicitação**. -![Captura de tela do botão "Enviar solicitação".](/assets/images/help/support/send-request-button.png) +1. Click **Send request**. +![Screenshot of the "Send request" button.](/assets/images/help/support/send-request-button.png) diff --git a/translations/pt-BR/data/reusables/user-settings/password-authentication-deprecation.md b/translations/pt-BR/data/reusables/user-settings/password-authentication-deprecation.md index 6ea28ee382..04a4cbd48e 100644 --- a/translations/pt-BR/data/reusables/user-settings/password-authentication-deprecation.md +++ b/translations/pt-BR/data/reusables/user-settings/password-authentication-deprecation.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 57b54e908b908c3bd26cf35158442ec9a59b96d8 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145065207" ---- -Quando o Git solicitar sua senha, insira seu PAT (token de acesso pessoal). Como alternativa, você pode usar um auxiliar de credencial como o [Gerenciador de Credenciais do Git](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md).{% ifversion not ghae %} A autenticação baseada em senha do Git foi removida para dar lugar a métodos de autenticação mais seguros. {% endif %} Para obter mais informações, veja "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)". +When Git prompts you for your password, enter your {% data variables.product.pat_generic %}. Alternatively, you can use a credential helper like [Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md).{% ifversion not ghae %} Password-based authentication for Git has been removed in favor of more secure authentication methods.{% endif %} For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." diff --git a/translations/pt-BR/data/reusables/user-settings/personal_access_tokens.md b/translations/pt-BR/data/reusables/user-settings/personal_access_tokens.md index 741cb085cd..0a2887b96d 100644 --- a/translations/pt-BR/data/reusables/user-settings/personal_access_tokens.md +++ b/translations/pt-BR/data/reusables/user-settings/personal_access_tokens.md @@ -1,10 +1,2 @@ ---- -ms.openlocfilehash: ab6ddc3736dea3b8c865ae9047373c1de4d1311f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145065204" ---- -1. Na barra lateral esquerda, clique em **Tokens de acesso pessoal**. -![Tokens de acesso pessoal](/assets/images/help/settings/personal_access_tokens_tab.png) +1. In the left sidebar, click **{% data variables.product.pat_generic_caps %}s**. +![{% data variables.product.pat_generic_caps %}s](/assets/images/help/settings/personal_access_tokens_tab.png) diff --git a/translations/pt-BR/data/reusables/user-settings/removes-personal-access-tokens.md b/translations/pt-BR/data/reusables/user-settings/removes-personal-access-tokens.md index c3cb781712..3840329b4c 100644 --- a/translations/pt-BR/data/reusables/user-settings/removes-personal-access-tokens.md +++ b/translations/pt-BR/data/reusables/user-settings/removes-personal-access-tokens.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: a435a91a41d6097a0613eb77253bf4381a75e8c0 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147065991" ---- -Como precaução de segurança, {% data variables.product.company_short %} remove automaticamente os tokens de acesso pessoal que não são usados há um ano. Para fornecer segurança adicional, é altamente recomendável adicionar uma expiração aos seus tokens de acesso pessoal. +As a security precaution, {% data variables.product.company_short %} automatically removes {% data variables.product.pat_generic %}s that haven't been used in a year. To provide additional security, we highly recommend adding an expiration to your {% data variables.product.pat_generic %}s. diff --git a/translations/pt-BR/data/variables/product.yml b/translations/pt-BR/data/variables/product.yml index 769d6949b3..903b4ee61b 100644 --- a/translations/pt-BR/data/variables/product.yml +++ b/translations/pt-BR/data/variables/product.yml @@ -24,14 +24,6 @@ prodname_ghe_managed: 'GitHub AE' prodname_ghe_one: 'GitHub One' prodname_docs: 'GitHub Docs' -## Use these variables when referring specifically to a location within a product -product_location: >- - {% ifversion ghes %}your GitHub Enterprise Server instance{% elsif ghae %}your enterprise{% else %}GitHub.com{% endif %} - -# Used ONLY when you need to refer to a GHES instance in an article that is versioned for non-GHES versions. -# Do not use in other situations! -product_location_enterprise: 'your GitHub Enterprise Server instance' - prodname_free_user: 'GitHub Free' prodname_pro: 'GitHub Pro' prodname_team: 'GitHub Team' @@ -40,10 +32,7 @@ prodname_free_team: 'GitHub Free' prodname_enterprise_backup_utilities: 'GitHub Enterprise Server Backup Utilities' # GitHub Connect (enterprise accounts, other unified features) -## Phrase content so that the uncapitalized unified contributions or unified search variables are not used at the start of a sentence. prodname_github_connect: 'GitHub Connect' -prodname_unified_contributions: 'unified contributions' -prodname_unified_search: 'unified search' # GitHub Enterprise migration tool prodname_importer_proper_name: 'GitHub Enterprise Importer' @@ -96,6 +85,20 @@ prodname_project_v1: >- prodname_project_v1_caps: >- {% ifversion ghes or ghae %}Project board{% else %}Project (classic){% endif %} +# Personal access tokens +pat_generic: 'personal access token' +pat_generic_caps: 'Personal access token' +pat_v2: 'fine-grained personal access token' +pat_v2_caps: 'Fine-grained personal access token' +pat_v1: >- + {% ifversion pat-v2 %}personal access token (classic){% else %}personal access token{% endif %} +pat_v1_plural: >- + {% ifversion pat-v2 %}personal access tokens (classic){% else %}personal access tokens{% endif %} +pat_v1_caps: >- + {% ifversion pat-v2 %}Personal access token (classic){% else %}Personal access token{% endif %} +pat_v1_caps_plural: >- + {% ifversion pat-v2 %}Personal access tokens (classic){% else %}Personal access tokens{% endif %} + # Apps, GitHub Marketplace, and integrations prodname_marketplace: 'GitHub Marketplace' prodname_github_app: 'GitHub App' @@ -124,11 +127,6 @@ prodname_discussions: 'GitHub Discussions' prodname_emu_idp_application: 'GitHub Enterprise Managed User' prodname_emu_idp_oidc_application: 'GitHub Enterprise Managed User (OIDC)' prodname_emus: 'Enterprise Managed Users' -prodname_managed_user: 'managed user account' -prodname_managed_users: 'managed user accounts' -prodname_managed_users_caps: 'Managed user accounts' -prodname_emu_enterprise: 'enterprise with managed users' -prodname_emu_org: 'organization with managed users' # GitHub Issues prodname_github_issues: 'GitHub Issues' @@ -238,14 +236,14 @@ prodname_server_statistics: 'Server Statistics' # Links product_url: >- - {% ifversion fpt or ghec %}github.com{% else %}[hostname]{% endif %} + {% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %} pricing_url: 'https://github.com/pricing' signin_link: >- - {% ifversion fpt or ghec %}[Sign in](https://github.com/login){% else %}Sign in (`https://[hostname]/login`){% endif %} + {% ifversion fpt or ghec %}[Sign in](https://github.com/login){% else %}Sign in (`https://HOSTNAME/login`){% endif %} signout_link: >- - {% ifversion fpt or ghec %}[Sign out](https://github.com/logout){% else %}Sign out (`https://[hostname]/logout`){% endif %} + {% ifversion fpt or ghec %}[Sign out](https://github.com/logout){% else %}Sign out (`https://HOSTNAME/logout`){% endif %} raw_github_com: >- - {% ifversion fpt or ghec %}raw.githubusercontent.com{% else %}[hostname]/user/repo/raw{% endif %} + {% ifversion fpt or ghec %}raw.githubusercontent.com{% else %}HOSTNAME/user/repo/raw{% endif %} # GitHub Enterprise Server past versions current-340-version: '11.10.354' @@ -255,25 +253,25 @@ doc_url_pre: >- {% ifversion fpt or ghec %}https://docs.github.com/rest{% elsif ghes %}https://docs.github.com/enterprise/{{ currentVersion | version_num }}/rest{% elsif ghae %}https://docs.github.com/github-ae@latest/rest{% endif %} # Use this inside command-line code blocks api_url_pre: >- - {% ifversion fpt or ghec %}https://api.github.com{% elsif ghes %}http(s)://[hostname]/api/v3{% elsif ghae %}https://[hostname]/api/v3{% endif %} + {% ifversion fpt or ghec %}https://api.github.com{% elsif ghes %}http(s)://HOSTNAME/api/v3{% elsif ghae %}https://HOSTNAME/api/v3{% endif %} # Use this inside command-line code blocks # Enterprise OAuth paths that don't include "/graphql" or "/api/v3" oauth_host_code: >- - {% ifversion fpt or ghec %}https://github.com{% else %}http(s)://[hostname]{% endif %} + {% ifversion fpt or ghec %}https://github.com{% else %}http(s)://HOSTNAME{% endif %} device_authorization_url: >- {%- ifversion fpt or ghec %} [`https://github.com/login/device`](https://github.com/login/device) {%- elsif ghes %} - `http(s)://[hostname]/login/device` + `http(s)://HOSTNAME/login/device` {%- elsif ghae %} - `https://[hostname]/login/device` + `https://HOSTNAME/login/device` {%- endif %} # Use this all other code blocks api_url_code: >- - {% ifversion fpt or ghec %}https://api.github.com{% elsif ghes %}http(s)://[hostname]/api/v3{% elsif ghae %}https://[hostname]/api/v3{% endif %} + {% ifversion fpt or ghec %}https://api.github.com{% elsif ghes %}http(s)://HOSTNAME/api/v3{% elsif ghae %}https://HOSTNAME/api/v3{% endif %} # Use this inside command-line code blocks graphql_url_pre: >- - {% ifversion fpt or ghec %}https://api.github.com/graphql{% elsif ghes %}http(s)://[hostname]/api/graphql{% elsif ghae %}https://[hostname]/api/graphql{% endif %} + {% ifversion fpt or ghec %}https://api.github.com/graphql{% elsif ghes %}http(s)://HOSTNAME/api/graphql{% elsif ghae %}https://HOSTNAME/api/graphql{% endif %} # Use this all other code blocks graphql_url_code: >- - {% ifversion fpt or ghec %}https://api.github.com/graphql{% elsif ghes %}http(s)://[hostname]/api/graphql{% elsif ghae %}https://[hostname]/api/graphql{% endif %} + {% ifversion fpt or ghec %}https://api.github.com/graphql{% elsif ghes %}http(s)://HOSTNAME/api/graphql{% elsif ghae %}https://HOSTNAME/api/graphql{% endif %} From 3916616759fb4882dc7597d7e9171f381224b5e9 Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Tue, 18 Oct 2022 11:01:30 -0700 Subject: [PATCH 2/2] New translation batch for cn (#31830) --- translations/log/msft-cn-resets.csv | 434 +++++++++++++- .../about-notifications.md | 108 ++-- .../configuring-notifications.md | 22 +- .../managing-notifications-from-your-inbox.md | 171 +++--- .../managing-your-profile-readme.md | 2 +- .../personalizing-your-profile.md | 2 +- ...utions-and-achievements-on-your-profile.md | 2 +- .../viewing-contributions-on-your-profile.md | 84 ++- ...tributions-not-showing-up-on-my-profile.md | 93 ++- .../index.md | 2 +- ...-collaborators-to-a-personal-repository.md | 2 +- ...an-email-address-to-your-github-account.md | 23 +- .../managing-email-preferences/index.md | 10 +- ...membering-your-github-username-or-email.md | 55 +- .../setting-your-commit-email-address.md | 56 +- .../changing-your-github-username.md | 10 +- .../managing-accessibility-settings.md | 49 +- ...fault-branch-name-for-your-repositories.md | 35 +- ...best-practices-for-leaving-your-company.md | 43 +- .../about-continuous-integration.md | 51 +- .../creating-a-composite-action.md | 4 +- .../creating-a-docker-container-action.md | 2 +- .../creating-a-javascript-action.md | 10 +- .../deploying-with-github-actions.md | 91 ++- .../deploying-docker-to-azure-app-service.md | 4 +- ...ncurrency-expressions-and-a-test-matrix.md | 106 ++-- .../about-self-hosted-runners.md | 12 +- ...and-troubleshooting-self-hosted-runners.md | 159 +++--- .../understanding-github-actions.md | 2 +- ...oving-assigned-issues-on-project-boards.md | 60 +- .../publishing-nodejs-packages.md | 2 +- .../automatic-token-authentication.md | 4 +- .../security-guides/encrypted-secrets.md | 2 +- .../security-hardening-for-github-actions.md | 8 +- .../about-github-hosted-runners.md | 2 +- .../using-larger-runners.md | 10 + .../events-that-trigger-workflows.md | 2 +- .../using-workflows/reusing-workflows.md | 2 +- .../storing-workflow-data-as-artifacts.md | 128 ++--- .../using-workflows/triggering-a-workflow.md | 4 +- .../workflow-commands-for-github-actions.md | 6 +- .../workflow-syntax-for-github-actions.md | 4 +- ...guring-code-scanning-for-your-appliance.md | 6 +- ...ring-secret-scanning-for-your-appliance.md | 59 +- ...b-advanced-security-for-your-enterprise.md | 96 ++-- ...pply-chain-security-for-your-enterprise.md | 17 +- ...he-dependency-graph-for-your-enterprise.md | 47 +- ...-vulnerability-data-for-your-enterprise.md | 27 +- .../about-github-connect.md | 28 +- ...c-user-license-sync-for-your-enterprise.md | 31 +- ...enabling-dependabot-for-your-enterprise.md | 14 +- ...g-server-statistics-for-your-enterprise.md | 32 +- ...ified-contributions-for-your-enterprise.md | 43 +- ...ling-unified-search-for-your-enterprise.md | 16 +- .../configuring-github-connect/index.md | 10 +- .../managing-github-connect.md | 106 ++-- .../configuring-a-hostname.md | 36 +- ...onfiguring-an-outbound-web-proxy-server.md | 33 +- .../configuring-built-in-firewall-rules.md | 46 +- .../configuring-dns-nameservers.md | 22 +- .../configuring-tls.md | 78 +-- .../enabling-subdomain-isolation.md | 43 +- .../network-ports.md | 66 +-- ...-enterprise-server-with-a-load-balancer.md | 74 +-- .../validating-your-domain-settings.md | 20 +- .../accessing-the-administrative-shell-ssh.md | 50 +- .../accessing-the-management-console.md | 54 +- .../command-line-utilities.md | 528 +++++++++--------- .../configuring-applications.md | 26 +- .../configuring-backups-on-your-appliance.md | 22 +- .../configuring-email-for-notifications.md | 6 +- ...guring-github-pages-for-your-enterprise.md | 72 +-- ...configuring-host-keys-for-your-instance.md | 29 +- .../configuring-rate-limits.md | 6 +- ...guring-ssh-connections-to-your-instance.md | 39 +- ...the-referrer-policy-for-your-enterprise.md | 36 +- .../configuring-web-commit-signing.md | 65 ++- ...nabling-and-scheduling-maintenance-mode.md | 93 ++- .../enabling-private-mode.md | 23 +- .../initializing-github-ae.md | 175 +++--- ...aging-github-mobile-for-your-enterprise.md | 40 +- .../site-admin-dashboard.md | 22 +- .../troubleshooting-tls-errors.md | 56 +- .../accessing-the-monitor-dashboard.md | 37 +- .../configuring-collectd.md | 52 +- ...ting-a-health-check-for-your-enterprise.md | 55 +- .../monitoring-your-appliance/index.md | 10 +- .../monitoring-using-snmp.md | 118 ++-- .../recommended-alert-thresholds.md | 46 +- .../enabling-automatic-update-checks.md | 33 +- .../increasing-cpu-or-memory-resources.md | 85 ++- .../increasing-storage-capacity.md | 62 +- .../upgrade-requirements.md | 55 +- .../upgrading-github-enterprise-server.md | 10 +- ...rise-server-with-github-actions-enabled.md | 8 +- ...ting-github-actions-for-your-enterprise.md | 151 +++-- .../using-a-staging-environment.md | 39 +- ...ions-with-minio-gateway-for-nas-storage.md | 43 +- ...f-hosted-runners-for-dependabot-updates.md | 77 ++- .../about-github-actions-for-enterprises.md | 4 +- ...ub-actions-for-github-enterprise-server.md | 101 ++-- ...self-hosted-runners-for-your-enterprise.md | 12 +- ...ucing-github-actions-to-your-enterprise.md | 2 +- .../about-using-actions-in-your-enterprise.md | 54 +- ...-githubcom-actions-using-github-connect.md | 57 +- ...manually-syncing-actions-from-githubcom.md | 68 ++- ...version-of-the-official-bundled-actions.md | 67 ++- .../identity-and-access-management/index.md | 10 +- ...bout-authentication-for-your-enterprise.md | 30 +- .../changing-authentication-methods.md | 34 +- .../managing-iam-for-your-enterprise/index.md | 17 +- ...siderations-for-external-authentication.md | 16 +- ...-accounts-single-sign-on-recovery-codes.md | 30 +- .../configuring-built-in-authentication.md | 47 +- .../disabling-unauthenticated-sign-ups.md | 26 +- .../inviting-people-to-use-your-instance.md | 23 +- .../using-cas-for-enterprise-iam/index.md | 10 +- .../using-cas-for-enterprise-iam/using-cas.md | 45 +- .../about-enterprise-managed-users.md | 57 +- ...for-your-idps-conditional-access-policy.md | 6 +- ...uring-oidc-for-enterprise-managed-users.md | 48 +- ...le-sign-on-for-enterprise-managed-users.md | 101 ++-- ...-for-enterprise-managed-users-with-okta.md | 103 ++-- ...ovisioning-for-enterprise-managed-users.md | 74 +-- ...mberships-with-identity-provider-groups.md | 79 +-- .../migrating-from-saml-to-oidc.md | 12 +- .../using-ldap-for-enterprise-iam/index.md | 10 +- .../using-ldap.md | 215 +++---- .../about-saml-for-enterprise-iam.md | 14 +- ...ning-for-your-enterprise-using-azure-ad.md | 44 +- ...isioning-for-your-enterprise-using-okta.md | 153 ++--- ...saml-single-sign-on-for-your-enterprise.md | 190 ++++--- ...g-user-provisioning-for-your-enterprise.md | 82 ++- .../enabling-encrypted-assertions.md | 61 +- .../using-saml-for-enterprise-iam/index.md | 11 +- .../saml-configuration-reference.md | 22 +- ...n-organization-to-an-enterprise-account.md | 41 +- .../troubleshooting-saml-authentication.md | 81 ++- .../updating-a-users-saml-nameid.md | 40 +- ...talling-github-enterprise-server-on-aws.md | 125 ++--- ...lling-github-enterprise-server-on-azure.md | 69 ++- ...erprise-server-on-google-cloud-platform.md | 87 ++- ...thub-enterprise-server-on-openstack-kvm.md | 52 +- ...ling-github-enterprise-server-on-vmware.md | 52 +- .../setting-up-a-staging-instance.md | 4 +- .../about-server-statistics.md | 59 +- .../exporting-server-statistics.md | 53 +- .../managing-global-webhooks.md | 111 ++-- .../audit-log-events-for-your-enterprise.md | 62 +- ...uring-the-audit-log-for-your-enterprise.md | 66 +-- ...es-in-the-audit-log-for-your-enterprise.md | 53 +- ...aming-the-audit-log-for-your-enterprise.md | 2 +- .../admin/overview/about-data-residency.md | 17 +- .../overview/about-enterprise-accounts.md | 4 +- .../about-github-enterprise-server.md | 103 ++-- .../content/admin/overview/system-overview.md | 179 +++--- .../enabling-github-packages-with-aws.md | 50 +- ...github-packages-with-azure-blob-storage.md | 40 +- .../enabling-github-packages-with-minio.md | 50 +- ...ith-github-packages-for-your-enterprise.md | 48 +- ...ainer-registry-from-the-docker-registry.md | 69 ++- ...inio-storage-bucket-for-github-packages.md | 79 ++- .../about-enterprise-policies.md | 26 +- ...s-for-github-actions-in-your-enterprise.md | 6 +- ...or-security-settings-in-your-enterprise.md | 2 +- ...-management-policies-in-your-enterprise.md | 2 +- .../index.md | 1 + .../about-pre-receive-hooks.md | 32 +- .../creating-a-pre-receive-hook-script.md | 185 +++--- ...adding-organizations-to-your-enterprise.md | 88 ++- .../adding-people-to-teams.md | 28 +- .../continuous-integration-using-jenkins.md | 14 +- .../creating-teams.md | 58 +- ...ctor-authentication-for-an-organization.md | 69 +-- .../restoring-a-deleted-organization.md | 57 +- ...-large-file-storage-for-your-enterprise.md | 92 +-- ...izing-user-messages-for-your-enterprise.md | 134 +++-- .../suspending-and-unsuspending-users.md | 103 ++-- ...-a-users-saml-access-to-your-enterprise.md | 51 +- .../viewing-people-in-your-enterprise.md | 2 +- .../about-migrations.md | 66 +-- ...ing-migration-data-from-your-enterprise.md | 64 +-- .../index.md | 10 +- .../migrating-data-to-your-enterprise.md | 155 +++-- ...authentication-with-saml-single-sign-on.md | 53 +- ...-token-for-use-with-saml-single-sign-on.md | 10 +- .../about-ssh.md | 2 +- ...ng-a-new-ssh-key-to-your-github-account.md | 8 +- .../checking-for-existing-ssh-keys.md | 41 +- ...-ssh-key-and-adding-it-to-the-ssh-agent.md | 4 +- .../testing-your-ssh-connection.md | 36 +- .../about-authentication-to-github.md | 112 ++-- .../authorizing-oauth-apps.md | 82 ++- .../creating-a-personal-access-token.md | 145 +++-- .../creating-a-strong-password.md | 34 +- .../index.md | 10 +- .../preventing-unauthorized-access.md | 30 +- ...moving-sensitive-data-from-a-repository.md | 122 ++-- .../reviewing-your-security-log.md | 6 +- .../reviewing-your-ssh-keys.md | 65 +-- .../sudo-mode.md | 78 ++- .../token-expiration-and-revocation.md | 50 +- ...updating-your-github-access-credentials.md | 81 ++- .../about-commit-signature-verification.md | 4 +- ...adding-a-gpg-key-to-your-github-account.md | 71 ++- .../associating-an-email-with-your-gpg-key.md | 56 +- .../telling-git-about-your-signing-key.md | 6 +- .../about-two-factor-authentication.md | 31 +- ...-github-using-two-factor-authentication.md | 90 ++- .../configuring-two-factor-authentication.md | 163 +++--- .../index.md | 10 +- ...ccount-if-you-lose-your-2fa-credentials.md | 89 ++- .../error-agent-admitted-failure-to-sign.md | 28 +- .../error-key-already-in-use.md | 36 +- .../using-ssh-over-the-https-port.md | 28 +- .../about-billing-for-github-packages.md | 59 +- .../about-billing-for-your-enterprise.md | 69 ++- .../about-per-user-pricing.md | 2 +- .../downgrading-your-github-subscription.md | 92 ++- .../upgrading-your-github-subscription.md | 98 ++-- ...n-and-usage-for-your-enterprise-account.md | 4 +- ...io-subscriptions-with-github-enterprise.md | 39 +- ...io-subscriptions-with-github-enterprise.md | 73 ++- .../about-licenses-for-github-enterprise.md | 41 +- ...ding-your-license-for-github-enterprise.md | 38 +- ...new-license-to-github-enterprise-server.md | 37 +- ...ing-license-usage-for-github-enterprise.md | 74 +-- .../configuring-code-scanning.md | 2 +- .../viewing-code-scanning-logs.md | 62 +- .../sarif-support-for-code-scanning.md | 2 +- ...-codeql-code-scanning-in-your-ci-system.md | 2 +- ...onfiguring-codeql-cli-in-your-ci-system.md | 8 +- ...iguring-codeql-runner-in-your-ci-system.md | 190 ++++--- ...installing-codeql-cli-in-your-ci-system.md | 2 +- ...running-codeql-runner-in-your-ci-system.md | 128 ++--- .../about-dependabot-alerts.md | 72 +-- ...isories-in-the-github-advisory-database.md | 8 +- ...isories-in-the-github-advisory-database.md | 4 +- ...tomating-dependabot-with-github-actions.md | 4 +- ...he-detection-of-vulnerable-dependencies.md | 91 ++- .../securing-your-organization.md | 135 ++--- .../secret-scanning/about-secret-scanning.md | 4 + .../managing-alerts-from-secret-scanning.md | 2 +- .../about-the-security-overview.md | 2 +- .../securing-accounts.md | 18 +- .../about-supply-chain-security.md | 4 +- .../configuring-dependency-review.md | 2 +- ...pace-to-access-a-private-image-registry.md | 8 +- ...g-encrypted-secrets-for-your-codespaces.md | 113 ++-- .../zh-CN/content/codespaces/overview.md | 2 +- ...a-prebuild-to-access-other-repositories.md | 16 +- .../about-wikis.md | 33 +- .../changing-access-permissions-for-wikis.md | 22 +- ...epository-from-github-to-github-desktop.md | 42 +- .../about-connections-to-github.md | 20 +- .../authenticating-to-github.md | 148 ++--- .../rate-limits-for-github-apps.md | 41 +- .../authorizing-oauth-apps.md | 238 ++++---- .../scopes-for-oauth-apps.md | 127 +++-- .../getting-started-with-apps/about-apps.md | 101 ++-- .../requirements-for-listing-an-app.md | 76 ++- .../security-best-practices-for-apps.md | 80 ++- ...ting-a-listing-description-for-your-app.md | 204 ++++--- ...icing-plans-for-github-marketplace-apps.md | 48 +- .../developers/overview/about-githubs-apis.md | 8 +- .../overview/managing-deploy-keys.md | 4 +- .../secret-scanning-partner-program.md | 4 +- .../guides/finding-your-discussions.md | 28 +- .../managing-categories-for-discussions.md | 92 ++- .../managing-discussions.md | 151 ++--- ...g-makecode-arcade-with-github-classroom.md | 30 +- .../view-autograding-results.md | 32 +- .../github-extensions-and-integrations.md | 4 +- ...-to-contribute-to-open-source-on-github.md | 48 +- .../about-remote-repositories.md | 76 ++- .../caching-your-github-credentials-in-git.md | 59 +- .../managing-remote-repositories.md | 187 +++---- ...ing-credentials-from-the-macos-keychain.md | 38 +- ...hy-is-git-always-asking-for-my-password.md | 22 +- .../adding-locally-hosted-code-to-github.md | 154 ++--- ...a-git-repository-using-the-command-line.md | 44 +- ...rting-a-repository-with-github-importer.md | 53 +- .../about-github-advanced-security.md | 2 +- .../access-permissions-on-github.md | 51 +- .../types-of-github-accounts.md | 75 +-- .../getting-started-with-github-ae.md | 87 ++- ...ng-started-with-github-enterprise-cloud.md | 251 ++++----- ...g-started-with-github-enterprise-server.md | 142 +++-- .../getting-started-with-github-team.md | 97 ++-- ...etting-started-with-your-github-account.md | 222 ++++---- .../get-started/quickstart/create-a-repo.md | 91 +-- .../get-started/quickstart/fork-a-repo.md | 176 +++--- .../verifying-your-email-address.md | 75 ++- .../get-started/using-git/about-git-rebase.md | 74 ++- ...g-a-subfolder-out-into-a-new-repository.md | 62 +- .../using-github/github-command-palette.md | 257 +++++---- .../get-started/using-github/github-mobile.md | 95 ++-- .../github-cli/github-cli/quickstart.md | 36 +- .../guides/forming-calls-with-graphql.md | 225 ++++---- .../graphql/guides/introduction-to-graphql.md | 86 ++- .../guides/managing-enterprise-accounts.md | 133 +++-- .../about-project-boards.md | 75 ++- .../automating-projects-using-actions.md | 116 ++-- .../automating-your-project/index.md | 1 + .../using-the-api-to-manage-projects.md | 2 +- .../customizing-a-view.md | 162 +++--- .../best-practices-for-projects.md | 87 ++- .../adding-items-to-your-project.md | 112 ++-- .../archiving-items-from-your-project.md | 69 ++- .../about-your-organizations-news-feed.md | 27 +- ...-authentication-and-saml-single-sign-on.md | 27 +- ...embers-saml-access-to-your-organization.md | 65 ++- .../zh-CN/content/organizations/index.md | 6 +- .../index.md | 1 - ...ing-the-audit-log-for-your-organization.md | 61 +- ...ur-organizations-installed-integrations.md | 34 -- ...ithub-app-managers-in-your-organization.md | 42 -- .../index.md | 27 - ...hub-app-managers-from-your-organization.md | 42 -- ...rs-to-repositories-in-your-organization.md | 52 -- ...tside-collaborator-in-your-organization.md | 31 - ...ation-member-to-an-outside-collaborator.md | 65 --- ...-collaborator-to-an-organization-member.md | 34 -- .../index.md | 37 -- ...ls-access-to-an-organization-repository.md | 58 -- ...am-access-to-an-organization-repository.md | 73 --- ...llaborators-access-to-your-organization.md | 74 --- ...borator-from-an-organization-repository.md | 69 --- .../repository-roles-for-an-organization.md | 175 ------ ...ng-base-permissions-for-an-organization.md | 45 -- ...g-people-with-access-to-your-repository.md | 58 -- .../about-ssh-certificate-authorities.md | 50 +- ...nviting-users-to-join-your-organization.md | 36 +- .../deleting-an-organization-account.md | 37 +- ...e-for-repositories-in-your-organization.md | 39 +- ...ess-management-with-saml-single-sign-on.md | 49 +- ...saml-single-sign-on-and-scim-using-okta.md | 71 +-- .../about-teams.md | 75 ++- ...-a-team-with-an-identity-provider-group.md | 105 ++-- .../about-oauth-app-access-restrictions.md | 71 --- ...roving-oauth-apps-for-your-organization.md | 31 - ...pproved-oauth-app-for-your-organization.md | 26 - ...cess-restrictions-for-your-organization.md | 32 -- ...cess-restrictions-for-your-organization.md | 37 -- .../index.md | 28 - .../about-permissions-for-github-packages.md | 14 +- .../connecting-a-repository-to-a-package.md | 45 +- .../deleting-and-restoring-a-package.md | 6 +- .../installing-a-package.md | 30 +- .../introduction-to-github-packages.md | 4 +- .../publishing-a-package.md | 39 +- ...nstalling-a-package-with-github-actions.md | 14 +- ...ainer-registry-from-the-docker-registry.md | 41 +- .../working-with-the-apache-maven-registry.md | 62 +- .../working-with-the-container-registry.md | 2 +- .../working-with-the-docker-registry.md | 172 +++--- .../working-with-the-gradle-registry.md | 104 ++-- .../working-with-the-npm-registry.md | 10 +- .../working-with-the-nuget-registry.md | 102 ++-- .../working-with-the-rubygems-registry.md | 82 ++- .../about-github-pages.md | 149 ++--- translations/zh-CN/content/pages/index.md | 11 +- ...reating-a-github-pages-site-with-jekyll.md | 91 +-- .../about-pull-request-merges.md | 88 +-- ...pull-request-branch-created-from-a-fork.md | 71 ++- ...ng-dependency-changes-in-a-pull-request.md | 2 +- .../working-with-forks/about-forks.md | 32 +- .../working-with-forks/syncing-a-fork.md | 66 +-- .../changing-a-commit-message.md | 79 ++- ...g-a-commit-on-behalf-of-an-organization.md | 66 +-- ...creating-a-commit-with-multiple-authors.md | 78 ++- ...sts-on-github-but-not-in-my-local-clone.md | 67 ++- ...are-my-commits-linked-to-the-wrong-user.md | 51 +- .../backing-up-a-repository.md | 41 +- .../referencing-and-citing-content.md | 40 +- .../about-merge-methods-on-github.md | 42 +- ...guring-commit-merging-for-pull-requests.md | 2 +- ...uring-commit-rebasing-for-pull-requests.md | 2 +- ...ring-commit-squashing-for-pull-requests.md | 2 +- .../configuring-pull-request-merges/index.md | 10 +- .../renaming-a-branch.md | 49 +- .../about-repositories.md | 132 ++--- .../cloning-a-repository.md | 76 +-- .../duplicating-a-repository.md | 80 ++- .../restoring-a-deleted-repository.md | 43 +- .../troubleshooting-cloning-errors.md | 115 ++-- .../about-code-owners.md | 4 +- .../licensing-a-repository.md | 118 ++-- ...mmit-signoff-policy-for-your-repository.md | 26 +- .../setting-repository-visibility.md | 81 +-- .../adding-a-file-to-a-repository.md | 49 +- .../about-large-files-on-github.md | 12 +- .../getting-permanent-links-to-files.md | 42 +- .../working-with-non-code-files.md | 8 +- .../content/rest/activity/notifications.md | 59 +- .../content/rest/apps/oauth-applications.md | 13 +- .../content/rest/codespaces/codespaces.md | 13 +- .../rest/enterprise-admin/admin-stats.md | 15 +- .../rest/enterprise-admin/announcement.md | 17 +- .../rest/enterprise-admin/audit-log.md | 9 +- .../content/rest/enterprise-admin/billing.md | 9 +- .../rest/enterprise-admin/global-webhooks.md | 17 +- .../content/rest/enterprise-admin/index.md | 44 +- .../content/rest/enterprise-admin/ldap.md | 13 +- .../content/rest/enterprise-admin/license.md | 15 +- .../enterprise-admin/management-console.md | 31 +- .../enterprise-admin/org-pre-receive-hooks.md | 29 +- .../content/rest/enterprise-admin/orgs.md | 15 +- .../pre-receive-environments.md | 43 +- .../enterprise-admin/pre-receive-hooks.md | 36 +- .../repo-pre-receive-hooks.md | 27 +- .../content/rest/enterprise-admin/scim.md | 5 +- .../content/rest/enterprise-admin/users.md | 15 +- translations/zh-CN/content/rest/gitignore.md | 19 +- .../rest/guides/building-a-ci-server.md | 128 +++-- .../getting-started-with-the-rest-api.md | 34 +- .../rest/guides/traversing-with-pagination.md | 142 +++-- .../rest/guides/working-with-comments.md | 69 ++- .../content/rest/migrations/source-imports.md | 17 +- .../zh-CN/content/rest/overview/index.md | 2 + .../overview/other-authentication-methods.md | 20 +- .../overview/resources-in-the-rest-api.md | 6 +- .../content/rest/overview/troubleshooting.md | 53 +- translations/zh-CN/content/rest/packages.md | 27 +- .../zh-CN/content/rest/projects/projects.md | 11 +- translations/zh-CN/content/rest/scim.md | 47 +- .../zh-CN/content/rest/teams/team-sync.md | 19 +- .../about-searching-on-github.md | 76 ++- ...rom-your-private-enterprise-environment.md | 4 +- .../searching-for-repositories.md | 206 ++++--- .../searching-issues-and-pull-requests.md | 2 +- ...p-github-sponsors-for-your-organization.md | 2 +- ...thub-sponsors-for-your-personal-account.md | 4 +- .../providing-data-to-github-support.md | 189 ++++--- .../about-github-premium-support.md | 135 +++-- .../zh-CN/data/learning-tracks/admin.yml | 40 +- .../enterprise-server/3-1/0-rc1.yml | 24 +- .../enterprise-server/3-2/0-rc1.yml | 4 +- .../release-notes/enterprise-server/3-2/0.yml | 2 +- .../enterprise-server/3-3/0-rc1.yml | 6 +- .../release-notes/enterprise-server/3-3/0.yml | 4 +- .../enterprise-server/3-4/0-rc1.yml | 4 +- .../release-notes/enterprise-server/3-4/0.yml | 4 +- .../release-notes/enterprise-server/3-4/1.yml | 2 +- .../release-notes/enterprise-server/3-4/2.yml | 2 +- .../enterprise-server/3-5/0-rc1.yml | 2 +- .../enterprise-server/3-6/0-rc1.yml | 2 +- .../actions/about-actions-for-enterprises.md | 2 +- .../reusables/actions/cache-default-size.md | 10 +- .../actions/disabling-github-actions.md | 10 +- .../actions/enterprise-common-prereqs.md | 14 +- .../actions/enterprise-http-proxy.md | 16 +- .../actions/enterprise-marketplace-actions.md | 10 +- .../enterprise-postinstall-nextsteps.md | 12 +- .../actions/github-connect-resolution.md | 10 +- ...-runner-management-permissions-required.md | 20 +- ...self-hosted-runner-networking-to-dotcom.md | 10 +- .../self-hosted-runner-ports-protocols.md | 12 +- .../upgrade-runners-before-upgrade-ghes.md | 10 +- .../actions/workflow-template-overview.md | 2 +- .../about-committer-numbers-ghec-ghes.md | 20 +- .../apps/user-to-server-rate-limits.md | 10 +- .../audit_log/audit-log-action-categories.md | 304 ++++++---- .../branches/new-repo-default-branch.md | 10 +- .../reusables/classroom/about-autograding.md | 10 +- ...ntext-for-actions-and-third-party-tools.md | 10 +- ...enterprise-enable-code-scanning-actions.md | 10 +- .../enterprise-enable-code-scanning.md | 2 +- .../code-scanning/what-is-codeql-cli.md | 10 +- .../creating-a-codespace-in-vscode.md | 2 +- .../command_line/provide-an-access-token.md | 10 +- .../enterprise-enable-dependabot.md | 2 +- .../data/reusables/desktop/get-an-account.md | 14 +- ...ithub-discussions-for-your-organization.md | 23 +- .../discussions/navigate-to-repo-or-org.md | 10 +- .../discussions/starting-a-discussion.md | 26 +- .../dotcom_billing/view-all-subscriptions.md | 10 +- .../dormant-user-activity.md | 52 +- .../enterprise-accounts/emu-cap-validates.md | 10 +- .../enterprise-accounts/emu-forks.md | 10 +- .../emu-permission-follow.md | 10 +- .../emu-permission-fork.md | 10 +- .../emu-permission-gist.md | 10 +- .../emu-permission-interact.md | 10 +- .../emu-permission-propose.md | 10 +- .../emu-permission-repo.md | 10 +- .../enterprise-accounts/emu-short-summary.md | 10 +- .../enterprise-accounts/oidc-gei-warning.md | 10 +- .../enterprise/apply-configuration.md | 14 +- .../data/reusables/enterprise/rate_limit.md | 10 +- .../reusables/enterprise/test-in-staging.md | 10 +- .../installing-releases.md | 2 +- .../download-package.md | 12 +- .../hardware-considerations-all-platforms.md | 40 +- .../hotpatching-explanation.md | 2 +- .../image-urls-viewable-warning.md | 10 +- .../ssh-into-instance.md | 12 +- .../dormancy-threshold.md | 10 +- .../enterprise_site_admin_settings/sign-in.md | 10 +- .../tls-downtime.md | 10 +- ...natively-enable-external-authentication.md | 10 +- .../built-in-authentication-new-accounts.md | 10 +- .../built-in-authentication.md | 10 +- ...r-usernames-for-external-authentication.md | 10 +- .../disclaimer-for-git-read-access.md | 16 +- .../reusables/files/choose-commit-email.md | 13 +- .../data/reusables/getting-started/actions.md | 10 +- .../adding-members-to-organizations.md | 10 +- .../configuring-security-features.md | 10 +- .../getting-started/creating-organizations.md | 10 +- .../enforcing-repo-management-policies.md | 10 +- .../managing-enterprise-members.md | 10 +- .../zh-CN/data/reusables/git/git-push.md | 12 +- .../large_files/storage_assets_location.md | 11 +- .../data/reusables/large_files/use_lfs_tip.md | 10 +- .../notifications/outbound_email_tip.md | 16 +- .../reusables/notifications/shared_state.md | 2 +- .../organizations/navigate-to-org.md | 10 +- .../package_registry/authenticate-packages.md | 20 +- ...uthenticate-to-container-registry-steps.md | 26 +- ...ext-steps-for-packages-enterprise-setup.md | 12 +- .../package-registry-with-github-tokens.md | 10 +- .../package_registry/packages-billing.md | 10 +- .../package_registry/required-scopes.md | 10 +- .../pages/build-failure-email-server.md | 16 +- .../data/reusables/pages/emu-org-only.md | 16 +- .../projects/enable-basic-workflow.md | 38 +- .../configure_pull_request_merges_intro.md | 10 +- .../pull_requests/default_merge_option.md | 12 +- .../pull_request_merges_and_contributions.md | 14 +- .../pull_requests/rebase_and_merge_summary.md | 16 +- .../pull_requests/squash_and_merge_summary.md | 14 +- .../reusables/repositories/deploy-keys.md | 10 +- .../repositories/enable-security-alerts.md | 11 +- .../repositories/navigate-to-repo.md | 10 +- .../reusables/repositories/you-can-fork.md | 17 +- .../rest-api/dotcom-only-guide-note.md | 14 +- .../saml/about-authorized-credentials.md | 10 +- .../reusables/saml/about-linked-identities.md | 12 +- .../about-saml-access-enterprise-account.md | 10 +- .../reusables/saml/authorized-creds-info.md | 20 +- .../saml/must-authorize-linked-identity.md | 10 +- .../you-must-periodically-authenticate.md | 2 +- .../reusables/scim/enterprise-account-scim.md | 10 +- .../data/reusables/scim/supported-idps.md | 13 +- .../data/reusables/search/syntax_tips.md | 16 +- .../enterprise-enable-secret-scanning.md | 2 +- .../partner-secret-list-private-repo.md | 4 + .../secret-list-private-push-protection.md | 4 + .../shortdesc/rate_limits_github_apps.md | 10 +- .../sponsors/select-sponsorship-billing.md | 10 +- .../zh-CN/data/reusables/ssh/about-ssh.md | 10 +- .../data/reusables/ssh/key-type-support.md | 23 +- .../rsa-sha-1-connection-failure-criteria.md | 12 +- .../data/reusables/support/submit-a-ticket.md | 79 +-- .../password-authentication-deprecation.md | 10 +- .../user-settings/personal_access_tokens.md | 12 +- .../removes-personal-access-tokens.md | 10 +- translations/zh-CN/data/variables/product.yml | 52 +- 559 files changed, 12052 insertions(+), 13745 deletions(-) delete mode 100644 translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md delete mode 100644 translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md delete mode 100644 translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/index.md delete mode 100644 translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md delete mode 100644 translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md delete mode 100644 translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md delete mode 100644 translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md delete mode 100644 translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md delete mode 100644 translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/index.md delete mode 100644 translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md delete mode 100644 translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md delete mode 100644 translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md delete mode 100644 translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md delete mode 100644 translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md delete mode 100644 translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md delete mode 100644 translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md delete mode 100644 translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md delete mode 100644 translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md delete mode 100644 translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md delete mode 100644 translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md delete mode 100644 translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md delete mode 100644 translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/index.md diff --git a/translations/log/msft-cn-resets.csv b/translations/log/msft-cn-resets.csv index 661ba6aa70..a2b3362433 100644 --- a/translations/log/msft-cn-resets.csv +++ b/translations/log/msft-cn-resets.csv @@ -128,7 +128,29 @@ translations/zh-CN/content/issues/trying-out-the-new-projects-experience/migrati translations/zh-CN/content/issues/trying-out-the-new-projects-experience/quickstart.md,file deleted because it no longer exists in main translations/zh-CN/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md,file deleted because it no longer exists in main translations/zh-CN/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/index.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/index.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md,file deleted because it no longer exists in main translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md,file deleted because it no longer exists in main +translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/index.md,file deleted because it no longer exists in main translations/zh-CN/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md,file deleted because it no longer exists in main translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/merging-an-upstream-repository-into-your-fork.md,file deleted because it no longer exists in main translations/zh-CN/content/rest/reference/actions.md,file deleted because it no longer exists in main @@ -239,24 +261,37 @@ translations/zh-CN/data/reusables/security-center/beta.md,file deleted because i translations/zh-CN/data/reusables/server-statistics/release-phase.md,file deleted because it no longer exists in main translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md,rendering error translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md,broken liquid tags +translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,broken liquid tags translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,rendering error +translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md,broken liquid tags translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md,rendering error translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,broken liquid tags translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md,broken liquid tags translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md,rendering error +translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags +translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md,broken liquid tags translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md,broken liquid tags translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,rendering error translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,rendering error translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,rendering error +translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md,broken liquid tags +translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md,broken liquid tags +translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md,broken liquid tags +translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md,broken liquid tags translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md,rendering error +translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md,broken liquid tags +translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md,broken liquid tags translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error +translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md,broken liquid tags translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md,broken liquid tags +translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md,broken liquid tags translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md,broken liquid tags translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md,broken liquid tags translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md,rendering error translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error translations/zh-CN/content/actions/deployment/about-deployments/about-continuous-deployment.md,rendering error +translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md,broken liquid tags translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md,rendering error translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md,rendering error translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md,rendering error @@ -270,12 +305,14 @@ translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/d translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md,broken liquid tags translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md,broken liquid tags translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md,broken liquid tags +translations/zh-CN/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md,broken liquid tags translations/zh-CN/content/actions/examples/using-the-github-cli-on-a-runner.md,broken liquid tags translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,rendering error translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,rendering error translations/zh-CN/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md,rendering error translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md,broken liquid tags translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md,rendering error +translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,broken liquid tags translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md,rendering error translations/zh-CN/content/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job.md,broken liquid tags translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md,rendering error @@ -284,6 +321,7 @@ translations/zh-CN/content/actions/learn-github-actions/environment-variables.md translations/zh-CN/content/actions/learn-github-actions/expressions.md,rendering error translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md,broken liquid tags translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md,rendering error +translations/zh-CN/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,broken liquid tags translations/zh-CN/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,broken liquid tags translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md,broken liquid tags translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error @@ -301,56 +339,194 @@ translations/zh-CN/content/actions/using-workflows/creating-starter-workflows-fo translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md,rendering error translations/zh-CN/content/actions/using-workflows/reusing-workflows.md,rendering error translations/zh-CN/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md,rendering error +translations/zh-CN/content/actions/using-workflows/storing-workflow-data-as-artifacts.md,broken liquid tags translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md,rendering error translations/zh-CN/content/actions/using-workflows/workflow-commands-for-github-actions.md,rendering error translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md,rendering error translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,broken liquid tags +translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md,broken liquid tags +translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/configuration/configuring-github-connect/about-github-connect.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md,rendering error +translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md,rendering error +translations/zh-CN/content/admin/configuration/configuring-github-connect/index.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-github-connect/managing-github-connect.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-network-settings/network-ports.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-applications.md,broken liquid tags translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,broken liquid tags translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md,broken liquid tags translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,rendering error +translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags +translations/zh-CN/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,broken liquid tags +translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,broken liquid tags +translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,broken liquid tags +translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/index.md,broken liquid tags +translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md,broken liquid tags +translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md,broken liquid tags +translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md,broken liquid tags +translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,broken liquid tags +translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,broken liquid tags +translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md,broken liquid tags translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md,broken liquid tags +translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,broken liquid tags +translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md,broken liquid tags +translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md,broken liquid tags translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md,rendering error +translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md,broken liquid tags translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md,rendering error translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md,rendering error +translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md,broken liquid tags +translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md,broken liquid tags +translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/index.md,broken liquid tags translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md,broken liquid tags translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md,rendering error +translations/zh-CN/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,broken liquid tags translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,broken liquid tags translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md,broken liquid tags translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md,broken liquid tags translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md,rendering error +translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-for-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/index.md,broken liquid tags translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md,broken liquid tags +translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md,broken liquid tags +translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md,broken liquid tags +translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md,broken liquid tags +translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md,broken liquid tags +translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md,broken liquid tags +translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md,broken liquid tags translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md,broken liquid tags +translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md,broken liquid tags +translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,broken liquid tags +translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,broken liquid tags translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md,rendering error translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md,rendering error +translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md,rendering error +translations/zh-CN/content/admin/overview/about-data-residency.md,broken liquid tags translations/zh-CN/content/admin/overview/about-enterprise-accounts.md,rendering error +translations/zh-CN/content/admin/overview/about-github-enterprise-server.md,broken liquid tags translations/zh-CN/content/admin/overview/about-github-for-enterprises.md,rendering error translations/zh-CN/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/overview/system-overview.md,broken liquid tags +translations/zh-CN/content/admin/packages/enabling-github-packages-with-aws.md,broken liquid tags +translations/zh-CN/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md,broken liquid tags +translations/zh-CN/content/admin/packages/enabling-github-packages-with-minio.md,broken liquid tags +translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md,broken liquid tags +translations/zh-CN/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md,broken liquid tags +translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md,broken liquid tags translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md,broken liquid tags +translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,broken liquid tags +translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md,broken liquid tags +translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md,broken liquid tags +translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,broken liquid tags +translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md,broken liquid tags +translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md,broken liquid tags +translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,broken liquid tags +translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md,rendering error +translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md,broken liquid tags +translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,broken liquid tags +translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md,broken liquid tags +translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,broken liquid tags +translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md,broken liquid tags translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md,rendering error translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md,rendering error translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md,broken liquid tags translations/zh-CN/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md,rendering error +translations/zh-CN/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md,broken liquid tags translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error +translations/zh-CN/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md,broken liquid tags +translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,broken liquid tags +translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md,broken liquid tags +translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,broken liquid tags +translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,broken liquid tags +translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/index.md,broken liquid tags +translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,broken liquid tags +translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,broken liquid tags translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,rendering error +translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md,broken liquid tags +translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md,broken liquid tags +translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md,broken liquid tags +translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md,broken liquid tags translations/zh-CN/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,rendering error +translations/zh-CN/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md,broken liquid tags +translations/zh-CN/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md,broken liquid tags translations/zh-CN/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md,rendering error translations/zh-CN/content/authentication/managing-commit-signature-verification/index.md,broken liquid tags translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-commits.md,broken liquid tags translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-tags.md,broken liquid tags translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md,broken liquid tags +translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,broken liquid tags +translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,broken liquid tags +translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md,broken liquid tags +translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,broken liquid tags +translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,broken liquid tags translations/zh-CN/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md,broken liquid tags +translations/zh-CN/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,broken liquid tags +translations/zh-CN/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,broken liquid tags +translations/zh-CN/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md,broken liquid tags translations/zh-CN/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md,broken liquid tags translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,broken liquid tags translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error @@ -360,9 +536,19 @@ translations/zh-CN/content/billing/managing-billing-for-github-codespaces/managi translations/zh-CN/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md,broken liquid tags translations/zh-CN/content/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot.md,broken liquid tags translations/zh-CN/content/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription.md,broken liquid tags +translations/zh-CN/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md,broken liquid tags +translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md,broken liquid tags translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md,rendering error translations/zh-CN/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md,broken liquid tags +translations/zh-CN/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md,broken liquid tags +translations/zh-CN/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,broken liquid tags translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md,rendering error +translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md,broken liquid tags +translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md,broken liquid tags +translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,broken liquid tags +translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,broken liquid tags +translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,broken liquid tags +translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,broken liquid tags translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,rendering error translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,rendering error @@ -373,11 +559,15 @@ translations/zh-CN/content/code-security/code-scanning/automatically-scanning-yo translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md,rendering error translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md,rendering error translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md,rendering error +translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,broken liquid tags translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,rendering error translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md,broken liquid tags translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md,rendering error translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,rendering error +translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,broken liquid tags translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags +translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,broken liquid tags +translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md,broken liquid tags translations/zh-CN/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md,rendering error translations/zh-CN/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md,rendering error translations/zh-CN/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md,broken liquid tags @@ -389,7 +579,9 @@ translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/c translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md,rendering error translations/zh-CN/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md,rendering error translations/zh-CN/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md,rendering error +translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md,broken liquid tags translations/zh-CN/content/code-security/getting-started/github-security-features.md,rendering error +translations/zh-CN/content/code-security/getting-started/securing-your-organization.md,broken liquid tags translations/zh-CN/content/code-security/getting-started/securing-your-repository.md,rendering error translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md,rendering error translations/zh-CN/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md,rendering error @@ -437,6 +629,7 @@ translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/ translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md,broken liquid tags translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md,broken liquid tags translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces.md,broken liquid tags +translations/zh-CN/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md,broken liquid tags translations/zh-CN/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md,broken liquid tags translations/zh-CN/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md,broken liquid tags translations/zh-CN/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md,broken liquid tags @@ -459,6 +652,8 @@ translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-dotfiles-f translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md,broken liquid tags translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-your-connection-to-github-codespaces.md,broken liquid tags translations/zh-CN/content/codespaces/troubleshooting/working-with-support-for-github-codespaces.md,broken liquid tags +translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md,broken liquid tags +translations/zh-CN/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,broken liquid tags translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,broken liquid tags translations/zh-CN/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md,broken liquid tags @@ -466,14 +661,25 @@ translations/zh-CN/content/copilot/getting-started-with-github-copilot/getting-s translations/zh-CN/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md,broken liquid tags translations/zh-CN/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md,broken liquid tags translations/zh-CN/content/copilot/quickstart.md,broken liquid tags +translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,broken liquid tags translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags +translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md,broken liquid tags +translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,broken liquid tags translations/zh-CN/content/developers/apps/building-github-apps/authenticating-with-github-apps.md,rendering error translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md,rendering error translations/zh-CN/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md,rendering error +translations/zh-CN/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,broken liquid tags +translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md,broken liquid tags +translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md,broken liquid tags +translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md,broken liquid tags translations/zh-CN/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md,broken liquid tags translations/zh-CN/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md,rendering error translations/zh-CN/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md,rendering error translations/zh-CN/content/developers/apps/guides/using-the-github-api-in-your-app.md,rendering error +translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,broken liquid tags +translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md,broken liquid tags +translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,broken liquid tags +translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,broken liquid tags translations/zh-CN/content/developers/overview/about-githubs-apis.md,broken liquid tags translations/zh-CN/content/developers/overview/managing-deploy-keys.md,broken liquid tags translations/zh-CN/content/developers/overview/secret-scanning-partner-program.md,broken liquid tags @@ -481,104 +687,213 @@ translations/zh-CN/content/developers/webhooks-and-events/events/issue-event-typ translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,rendering error translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md,broken liquid tags translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md,broken liquid tags +translations/zh-CN/content/discussions/guides/finding-your-discussions.md,broken liquid tags +translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,broken liquid tags +translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md,broken liquid tags translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student.md,broken liquid tags translations/zh-CN/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/glossary.md,broken liquid tags +translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,broken liquid tags translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,broken liquid tags translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md,broken liquid tags +translations/zh-CN/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,broken liquid tags translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,broken liquid tags translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,broken liquid tags translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,broken liquid tags translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,broken liquid tags +translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,broken liquid tags translations/zh-CN/content/get-started/exploring-projects-on-github/following-organizations.md,broken liquid tags +translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md,broken liquid tags translations/zh-CN/content/get-started/getting-started-with-git/associating-text-editors-with-git.md,broken liquid tags +translations/zh-CN/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md,broken liquid tags +translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md,broken liquid tags +translations/zh-CN/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,broken liquid tags +translations/zh-CN/content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md,broken liquid tags +translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md,broken liquid tags +translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md,broken liquid tags +translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md,broken liquid tags translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md,rendering error +translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md,broken liquid tags +translations/zh-CN/content/get-started/learning-about-github/types-of-github-accounts.md,broken liquid tags +translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md,broken liquid tags +translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,broken liquid tags +translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md,broken liquid tags +translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md,broken liquid tags +translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md,broken liquid tags translations/zh-CN/content/get-started/quickstart/be-social.md,broken liquid tags translations/zh-CN/content/get-started/quickstart/communicating-on-github.md,broken liquid tags +translations/zh-CN/content/get-started/quickstart/create-a-repo.md,broken liquid tags +translations/zh-CN/content/get-started/quickstart/fork-a-repo.md,broken liquid tags translations/zh-CN/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags +translations/zh-CN/content/get-started/signing-up-for-github/verifying-your-email-address.md,broken liquid tags +translations/zh-CN/content/get-started/using-git/about-git-rebase.md,broken liquid tags +translations/zh-CN/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md,broken liquid tags +translations/zh-CN/content/get-started/using-github/github-command-palette.md,broken liquid tags +translations/zh-CN/content/get-started/using-github/github-mobile.md,broken liquid tags translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md,rendering error translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md,broken liquid tags translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md,rendering error translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md,broken liquid tags translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md,broken liquid tags translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md,rendering error +translations/zh-CN/content/github-cli/github-cli/quickstart.md,broken liquid tags +translations/zh-CN/content/graphql/guides/forming-calls-with-graphql.md,broken liquid tags +translations/zh-CN/content/graphql/guides/introduction-to-graphql.md,broken liquid tags +translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md,broken liquid tags translations/zh-CN/content/graphql/guides/migrating-from-rest-to-graphql.md,broken liquid tags translations/zh-CN/content/graphql/overview/about-the-graphql-api.md,rendering error +translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md,broken liquid tags +translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md,broken liquid tags translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md,broken liquid tags +translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md,broken liquid tags +translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md,broken liquid tags +translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md,broken liquid tags +translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md,broken liquid tags translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md,broken liquid tags translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md,broken liquid tags translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md,rendering error translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error +translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,broken liquid tags +translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,broken liquid tags +translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,broken liquid tags translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md,rendering error translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,rendering error -translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md,rendering error translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md,rendering error -translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md,rendering error -translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md,rendering error -translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md,rendering error -translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md,rendering error -translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md,rendering error -translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md,rendering error +translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md,broken liquid tags +translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,broken liquid tags translations/zh-CN/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md,broken liquid tags +translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md,broken liquid tags translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md,rendering error translations/zh-CN/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md,rendering error translations/zh-CN/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md,rendering error +translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,broken liquid tags translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error +translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md,broken liquid tags +translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,broken liquid tags +translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md,rendering error -translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md,broken liquid tags -translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md,broken liquid tags +translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md,broken liquid tags translations/zh-CN/content/packages/learn-github-packages/about-permissions-for-github-packages.md,rendering error translations/zh-CN/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md,rendering error +translations/zh-CN/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md,broken liquid tags translations/zh-CN/content/packages/learn-github-packages/deleting-and-restoring-a-package.md,rendering error +translations/zh-CN/content/packages/learn-github-packages/installing-a-package.md,broken liquid tags translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md,rendering error +translations/zh-CN/content/packages/learn-github-packages/publishing-a-package.md,broken liquid tags translations/zh-CN/content/packages/learn-github-packages/viewing-packages.md,rendering error translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,rendering error +translations/zh-CN/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md,broken liquid tags +translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,broken liquid tags translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,rendering error +translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md,broken liquid tags +translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md,broken liquid tags translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md,rendering error +translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md,broken liquid tags +translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md,broken liquid tags translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,rendering error +translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md,broken liquid tags translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md,rendering error +translations/zh-CN/content/pages/index.md,broken liquid tags +translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md,broken liquid tags translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,broken liquid tags +translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md,broken liquid tags translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md,broken liquid tags +translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,broken liquid tags translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md,rendering error translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md,rendering error translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md,rendering error translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,rendering error +translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md,broken liquid tags +translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md,broken liquid tags +translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,broken liquid tags +translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,broken liquid tags +translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,broken liquid tags +translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,broken liquid tags +translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md,broken liquid tags translations/zh-CN/content/repositories/archiving-a-github-repository/archiving-repositories.md,rendering error +translations/zh-CN/content/repositories/archiving-a-github-repository/backing-up-a-repository.md,broken liquid tags +translations/zh-CN/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md,broken liquid tags +translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md,broken liquid tags translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md,rendering error translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md,rendering error translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md,rendering error +translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md,broken liquid tags translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md,rendering error translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md,rendering error translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md,rendering error translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md,rendering error translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md,rendering error translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md,rendering error +translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,broken liquid tags +translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md,broken liquid tags +translations/zh-CN/content/repositories/creating-and-managing-repositories/cloning-a-repository.md,broken liquid tags +translations/zh-CN/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md,broken liquid tags +translations/zh-CN/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md,broken liquid tags translations/zh-CN/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,rendering error +translations/zh-CN/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,broken liquid tags translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md,rendering error translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md,rendering error +translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,broken liquid tags translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,rendering error translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md,rendering error translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md,rendering error translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md,rendering error +translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md,broken liquid tags +translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,broken liquid tags translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md,rendering error translations/zh-CN/content/repositories/releasing-projects-on-github/comparing-releases.md,rendering error translations/zh-CN/content/repositories/releasing-projects-on-github/linking-to-releases.md,rendering error translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error +translations/zh-CN/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,broken liquid tags translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,broken liquid tags +translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,broken liquid tags translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md,rendering error +translations/zh-CN/content/rest/activity/notifications.md,broken liquid tags +translations/zh-CN/content/rest/apps/oauth-applications.md,broken liquid tags +translations/zh-CN/content/rest/codespaces/codespaces.md,broken liquid tags translations/zh-CN/content/rest/dependabot/index.md,broken liquid tags +translations/zh-CN/content/rest/enterprise-admin/admin-stats.md,broken liquid tags +translations/zh-CN/content/rest/enterprise-admin/announcement.md,broken liquid tags +translations/zh-CN/content/rest/enterprise-admin/audit-log.md,broken liquid tags +translations/zh-CN/content/rest/enterprise-admin/billing.md,broken liquid tags +translations/zh-CN/content/rest/enterprise-admin/global-webhooks.md,broken liquid tags +translations/zh-CN/content/rest/enterprise-admin/index.md,broken liquid tags +translations/zh-CN/content/rest/enterprise-admin/ldap.md,broken liquid tags +translations/zh-CN/content/rest/enterprise-admin/license.md,broken liquid tags +translations/zh-CN/content/rest/enterprise-admin/management-console.md,broken liquid tags +translations/zh-CN/content/rest/enterprise-admin/org-pre-receive-hooks.md,broken liquid tags +translations/zh-CN/content/rest/enterprise-admin/orgs.md,broken liquid tags +translations/zh-CN/content/rest/enterprise-admin/pre-receive-environments.md,broken liquid tags +translations/zh-CN/content/rest/enterprise-admin/pre-receive-hooks.md,broken liquid tags +translations/zh-CN/content/rest/enterprise-admin/repo-pre-receive-hooks.md,broken liquid tags translations/zh-CN/content/rest/enterprise-admin/scim.md,broken liquid tags +translations/zh-CN/content/rest/enterprise-admin/users.md,broken liquid tags +translations/zh-CN/content/rest/gitignore.md,broken liquid tags +translations/zh-CN/content/rest/guides/building-a-ci-server.md,broken liquid tags translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md,rendering error +translations/zh-CN/content/rest/guides/traversing-with-pagination.md,broken liquid tags +translations/zh-CN/content/rest/guides/working-with-comments.md,broken liquid tags +translations/zh-CN/content/rest/migrations/source-imports.md,broken liquid tags translations/zh-CN/content/rest/overview/other-authentication-methods.md,broken liquid tags translations/zh-CN/content/rest/overview/permissions-required-for-github-apps.md,rendering error translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md,broken liquid tags +translations/zh-CN/content/rest/overview/troubleshooting.md,broken liquid tags +translations/zh-CN/content/rest/packages.md,broken liquid tags +translations/zh-CN/content/rest/projects/projects.md,broken liquid tags translations/zh-CN/content/rest/repos/lfs.md,broken liquid tags +translations/zh-CN/content/rest/scim.md,broken liquid tags +translations/zh-CN/content/rest/teams/team-sync.md,broken liquid tags +translations/zh-CN/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md,broken liquid tags translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,rendering error +translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md,broken liquid tags translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md,rendering error translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md,broken liquid tags translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,broken liquid tags translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,broken liquid tags +translations/zh-CN/content/support/contacting-github-support/providing-data-to-github-support.md,broken liquid tags +translations/zh-CN/content/support/learning-about-github-support/about-github-premium-support.md,broken liquid tags translations/zh-CN/content/support/learning-about-github-support/about-github-support.md,rendering error +translations/zh-CN/data/learning-tracks/admin.yml,broken liquid tags translations/zh-CN/data/release-notes/enterprise-server/2-20/15.yml,rendering error translations/zh-CN/data/release-notes/enterprise-server/2-21/17.yml,rendering error translations/zh-CN/data/release-notes/enterprise-server/2-21/6.yml,rendering error @@ -594,6 +909,7 @@ translations/zh-CN/data/release-notes/enterprise-server/3-0/0.yml,rendering erro translations/zh-CN/data/release-notes/enterprise-server/3-0/1.yml,rendering error translations/zh-CN/data/release-notes/enterprise-server/3-0/2.yml,rendering error translations/zh-CN/data/release-notes/enterprise-server/3-0/3.yml,rendering error +translations/zh-CN/data/release-notes/enterprise-server/3-1/0-rc1.yml,broken liquid tags translations/zh-CN/data/release-notes/enterprise-server/3-1/0.yml,rendering error translations/zh-CN/data/release-notes/enterprise-server/3-1/1.yml,rendering error translations/zh-CN/data/release-notes/enterprise-server/3-1/2.yml,rendering error @@ -620,7 +936,14 @@ translations/zh-CN/data/release-notes/enterprise-server/3-6/0-rc1.yml,rendering translations/zh-CN/data/reusables/actions/about-actions-for-enterprises.md,rendering error translations/zh-CN/data/reusables/actions/actions-audit-events-workflow.md,rendering error translations/zh-CN/data/reusables/actions/actions-billing.md,broken liquid tags +translations/zh-CN/data/reusables/actions/cache-default-size.md,broken liquid tags translations/zh-CN/data/reusables/actions/create-runner-group.md,rendering error +translations/zh-CN/data/reusables/actions/disabling-github-actions.md,broken liquid tags +translations/zh-CN/data/reusables/actions/enterprise-common-prereqs.md,broken liquid tags +translations/zh-CN/data/reusables/actions/enterprise-http-proxy.md,broken liquid tags +translations/zh-CN/data/reusables/actions/enterprise-marketplace-actions.md,broken liquid tags +translations/zh-CN/data/reusables/actions/enterprise-postinstall-nextsteps.md,broken liquid tags +translations/zh-CN/data/reusables/actions/github-connect-resolution.md,broken liquid tags translations/zh-CN/data/reusables/actions/ip-allow-list-self-hosted-runners.md,broken liquid tags translations/zh-CN/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md,broken liquid tags translations/zh-CN/data/reusables/actions/jobs/section-running-jobs-in-a-container.md,broken liquid tags @@ -630,29 +953,41 @@ translations/zh-CN/data/reusables/actions/reusable-workflow-calling-syntax.md,re translations/zh-CN/data/reusables/actions/reusable-workflows.md,rendering error translations/zh-CN/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md,rendering error translations/zh-CN/data/reusables/actions/self-hosted-runner-add-to-enterprise.md,rendering error +translations/zh-CN/data/reusables/actions/self-hosted-runner-management-permissions-required.md,broken liquid tags +translations/zh-CN/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md,broken liquid tags +translations/zh-CN/data/reusables/actions/self-hosted-runner-ports-protocols.md,broken liquid tags translations/zh-CN/data/reusables/actions/settings-ui/settings-actions-general.md,rendering error translations/zh-CN/data/reusables/actions/settings-ui/settings-actions-runner-groups.md,rendering error translations/zh-CN/data/reusables/actions/settings-ui/settings-actions-runners.md,rendering error translations/zh-CN/data/reusables/actions/sidebar-secret.md,rendering error +translations/zh-CN/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md,broken liquid tags translations/zh-CN/data/reusables/actions/usage-workflow-run-time.md,rendering error translations/zh-CN/data/reusables/actions/workflow-basic-example-and-explanation.md,broken liquid tags translations/zh-CN/data/reusables/actions/workflow-dispatch-inputs.md,rendering error translations/zh-CN/data/reusables/actions/workflow-template-overview.md,rendering error +translations/zh-CN/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md,broken liquid tags translations/zh-CN/data/reusables/advanced-security/about-ghas-organization-policy.md,broken liquid tags translations/zh-CN/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md,rendering error translations/zh-CN/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md,rendering error translations/zh-CN/data/reusables/advanced-security/secret-scanning-push-protection-org.md,broken liquid tags +translations/zh-CN/data/reusables/apps/user-to-server-rate-limits.md,broken liquid tags +translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md,broken liquid tags translations/zh-CN/data/reusables/audit_log/audit-log-events-workflows.md,rendering error translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md,rendering error translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md,rendering error +translations/zh-CN/data/reusables/branches/new-repo-default-branch.md,broken liquid tags +translations/zh-CN/data/reusables/classroom/about-autograding.md,broken liquid tags translations/zh-CN/data/reusables/code-scanning/analyze-go.md,broken liquid tags translations/zh-CN/data/reusables/code-scanning/autobuild-add-build-steps.md,broken liquid tags +translations/zh-CN/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags translations/zh-CN/data/reusables/code-scanning/codeql-languages-bullets.md,rendering error translations/zh-CN/data/reusables/code-scanning/codeql-languages-keywords.md,rendering error +translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md,broken liquid tags translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags translations/zh-CN/data/reusables/code-scanning/example-configuration-files.md,broken liquid tags translations/zh-CN/data/reusables/code-scanning/licensing-note.md,broken liquid tags translations/zh-CN/data/reusables/code-scanning/run-additional-queries.md,broken liquid tags +translations/zh-CN/data/reusables/code-scanning/what-is-codeql-cli.md,broken liquid tags translations/zh-CN/data/reusables/codespaces/codespaces-api-beta-note.md,broken liquid tags translations/zh-CN/data/reusables/codespaces/codespaces-spending-limit-requirement.md,broken liquid tags translations/zh-CN/data/reusables/codespaces/creating-a-codespace-in-vscode.md,broken liquid tags @@ -665,61 +1000,141 @@ translations/zh-CN/data/reusables/codespaces/rebuild-command.md,broken liquid ta translations/zh-CN/data/reusables/codespaces/secrets-on-start.md,broken liquid tags translations/zh-CN/data/reusables/codespaces/use-chrome.md,broken liquid tags translations/zh-CN/data/reusables/codespaces/your-codespaces-procedure-step.md,broken liquid tags +translations/zh-CN/data/reusables/command_line/provide-an-access-token.md,broken liquid tags translations/zh-CN/data/reusables/copilot/install-copilot-in-neovim.md,broken liquid tags translations/zh-CN/data/reusables/dependabot/beta-security-and-version-updates.md,rendering error translations/zh-CN/data/reusables/dependabot/default-dependencies-allow-ignore.md,broken liquid tags translations/zh-CN/data/reusables/dependabot/enabling-disabling-dependency-graph-private-repo.md,rendering error translations/zh-CN/data/reusables/dependabot/enterprise-enable-dependabot.md,rendering error +translations/zh-CN/data/reusables/desktop/get-an-account.md,broken liquid tags +translations/zh-CN/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md,broken liquid tags +translations/zh-CN/data/reusables/discussions/navigate-to-repo-or-org.md,broken liquid tags +translations/zh-CN/data/reusables/discussions/starting-a-discussion.md,broken liquid tags translations/zh-CN/data/reusables/dotcom_billing/actions-packages-report-download-org-account.md,broken liquid tags +translations/zh-CN/data/reusables/dotcom_billing/view-all-subscriptions.md,broken liquid tags translations/zh-CN/data/reusables/education/submit-application.md,broken liquid tags translations/zh-CN/data/reusables/enterprise-accounts/actions-packages-report-download-enterprise-accounts.md,broken liquid tags translations/zh-CN/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise-accounts/emu-cap-validates.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise-accounts/emu-forks.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-follow.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-fork.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-gist.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-interact.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-propose.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-repo.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise-accounts/emu-short-summary.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise-accounts/oidc-gei-warning.md,broken liquid tags translations/zh-CN/data/reusables/enterprise-accounts/repo-creation-policy.md,broken liquid tags translations/zh-CN/data/reusables/enterprise-accounts/security-tab.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise/apply-configuration.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise/rate_limit.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise/test-in-staging.md,broken liquid tags translations/zh-CN/data/reusables/enterprise_enterprise_support/installing-releases.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise_installation/download-package.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md,broken liquid tags translations/zh-CN/data/reusables/enterprise_installation/hotpatching-explanation.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise_installation/image-urls-viewable-warning.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise_installation/ssh-into-instance.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise_site_admin_settings/sign-in.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise_site_admin_settings/tls-downtime.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentication.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,broken liquid tags +translations/zh-CN/data/reusables/files/choose-commit-email.md,broken liquid tags translations/zh-CN/data/reusables/gated-features/code-scanning.md,broken liquid tags translations/zh-CN/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags translations/zh-CN/data/reusables/gated-features/dependency-vulnerable-calls.md,rendering error translations/zh-CN/data/reusables/gated-features/secret-scanning-partner.md,rendering error translations/zh-CN/data/reusables/gated-features/secret-scanning.md,rendering error +translations/zh-CN/data/reusables/getting-started/actions.md,broken liquid tags +translations/zh-CN/data/reusables/getting-started/adding-members-to-organizations.md,broken liquid tags +translations/zh-CN/data/reusables/getting-started/configuring-security-features.md,broken liquid tags +translations/zh-CN/data/reusables/getting-started/creating-organizations.md,broken liquid tags +translations/zh-CN/data/reusables/getting-started/enforcing-repo-management-policies.md,broken liquid tags translations/zh-CN/data/reusables/getting-started/enterprise-advanced-security.md,broken liquid tags +translations/zh-CN/data/reusables/getting-started/managing-enterprise-members.md,broken liquid tags +translations/zh-CN/data/reusables/git/git-push.md,broken liquid tags translations/zh-CN/data/reusables/identity-and-permissions/ip-allow-lists-enable.md,broken liquid tags translations/zh-CN/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md,broken liquid tags +translations/zh-CN/data/reusables/large_files/storage_assets_location.md,broken liquid tags +translations/zh-CN/data/reusables/large_files/use_lfs_tip.md,broken liquid tags translations/zh-CN/data/reusables/notifications-v2/custom-notification-types.md,broken liquid tags +translations/zh-CN/data/reusables/notifications/outbound_email_tip.md,broken liquid tags translations/zh-CN/data/reusables/notifications/shared_state.md,rendering error translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-options.md,rendering error translations/zh-CN/data/reusables/organizations/billing_plans.md,rendering error translations/zh-CN/data/reusables/organizations/github-apps-settings-sidebar.md,rendering error translations/zh-CN/data/reusables/organizations/member-privileges.md,rendering error +translations/zh-CN/data/reusables/organizations/navigate-to-org.md,broken liquid tags translations/zh-CN/data/reusables/organizations/repository-defaults.md,rendering error translations/zh-CN/data/reusables/organizations/security-and-analysis.md,rendering error translations/zh-CN/data/reusables/organizations/security.md,rendering error translations/zh-CN/data/reusables/organizations/teams_sidebar.md,rendering error translations/zh-CN/data/reusables/organizations/verified-domains.md,rendering error +translations/zh-CN/data/reusables/package_registry/authenticate-packages.md,broken liquid tags +translations/zh-CN/data/reusables/package_registry/authenticate-to-container-registry-steps.md,broken liquid tags +translations/zh-CN/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,broken liquid tags +translations/zh-CN/data/reusables/package_registry/package-registry-with-github-tokens.md,broken liquid tags +translations/zh-CN/data/reusables/package_registry/packages-billing.md,broken liquid tags +translations/zh-CN/data/reusables/package_registry/required-scopes.md,broken liquid tags +translations/zh-CN/data/reusables/pages/build-failure-email-server.md,broken liquid tags +translations/zh-CN/data/reusables/pages/emu-org-only.md,broken liquid tags translations/zh-CN/data/reusables/pages/sidebar-pages.md,rendering error +translations/zh-CN/data/reusables/projects/enable-basic-workflow.md,broken liquid tags +translations/zh-CN/data/reusables/pull_requests/configure_pull_request_merges_intro.md,broken liquid tags +translations/zh-CN/data/reusables/pull_requests/default_merge_option.md,broken liquid tags translations/zh-CN/data/reusables/pull_requests/merge-queue-beta.md,broken liquid tags +translations/zh-CN/data/reusables/pull_requests/pull_request_merges_and_contributions.md,broken liquid tags +translations/zh-CN/data/reusables/pull_requests/rebase_and_merge_summary.md,broken liquid tags translations/zh-CN/data/reusables/pull_requests/resolving-conversations.md,broken liquid tags +translations/zh-CN/data/reusables/pull_requests/squash_and_merge_summary.md,broken liquid tags translations/zh-CN/data/reusables/release-notes/ghas-3.4-secret-scanning-known-issue.md,rendering error translations/zh-CN/data/reusables/repositories/changed-files.md,broken liquid tags +translations/zh-CN/data/reusables/repositories/deploy-keys.md,broken liquid tags +translations/zh-CN/data/reusables/repositories/enable-security-alerts.md,broken liquid tags translations/zh-CN/data/reusables/repositories/navigate-to-code-security-and-analysis.md,rendering error translations/zh-CN/data/reusables/repositories/navigate-to-commit-page.md,broken liquid tags +translations/zh-CN/data/reusables/repositories/navigate-to-repo.md,broken liquid tags translations/zh-CN/data/reusables/repositories/repository-branches.md,rendering error translations/zh-CN/data/reusables/repositories/sidebar-notifications.md,rendering error translations/zh-CN/data/reusables/repositories/suggest-changes.md,broken liquid tags +translations/zh-CN/data/reusables/repositories/you-can-fork.md,broken liquid tags +translations/zh-CN/data/reusables/rest-api/dotcom-only-guide-note.md,broken liquid tags +translations/zh-CN/data/reusables/saml/about-authorized-credentials.md,broken liquid tags +translations/zh-CN/data/reusables/saml/about-linked-identities.md,broken liquid tags +translations/zh-CN/data/reusables/saml/about-saml-access-enterprise-account.md,broken liquid tags +translations/zh-CN/data/reusables/saml/authorized-creds-info.md,broken liquid tags +translations/zh-CN/data/reusables/saml/must-authorize-linked-identity.md,broken liquid tags translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,rendering error +translations/zh-CN/data/reusables/scim/enterprise-account-scim.md,broken liquid tags +translations/zh-CN/data/reusables/scim/supported-idps.md,broken liquid tags +translations/zh-CN/data/reusables/search/syntax_tips.md,broken liquid tags translations/zh-CN/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md,broken liquid tags translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md,rendering error translations/zh-CN/data/reusables/secret-scanning/push-protection-web-ui-choice.md,broken liquid tags translations/zh-CN/data/reusables/secret-scanning/secret-list-private-push-protection.md,rendering error translations/zh-CN/data/reusables/security-overview/permissions.md,rendering error +translations/zh-CN/data/reusables/shortdesc/rate_limits_github_apps.md,broken liquid tags +translations/zh-CN/data/reusables/sponsors/select-sponsorship-billing.md,broken liquid tags +translations/zh-CN/data/reusables/ssh/about-ssh.md,broken liquid tags +translations/zh-CN/data/reusables/ssh/key-type-support.md,broken liquid tags +translations/zh-CN/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md,broken liquid tags translations/zh-CN/data/reusables/support/help_resources.md,rendering error +translations/zh-CN/data/reusables/support/submit-a-ticket.md,broken liquid tags translations/zh-CN/data/reusables/user-settings/access_applications.md,rendering error translations/zh-CN/data/reusables/user-settings/account_settings.md,rendering error translations/zh-CN/data/reusables/user-settings/appearance-settings.md,rendering error translations/zh-CN/data/reusables/user-settings/developer_settings.md,rendering error translations/zh-CN/data/reusables/user-settings/emails.md,rendering error translations/zh-CN/data/reusables/user-settings/organizations.md,rendering error +translations/zh-CN/data/reusables/user-settings/password-authentication-deprecation.md,broken liquid tags +translations/zh-CN/data/reusables/user-settings/personal_access_tokens.md,broken liquid tags +translations/zh-CN/data/reusables/user-settings/removes-personal-access-tokens.md,broken liquid tags translations/zh-CN/data/reusables/user-settings/repo-tab.md,rendering error translations/zh-CN/data/reusables/user-settings/saved_replies.md,rendering error translations/zh-CN/data/reusables/user-settings/security-analysis.md,rendering error @@ -729,3 +1144,4 @@ translations/zh-CN/data/reusables/webhooks/pull_request_properties.md,broken liq translations/zh-CN/data/reusables/webhooks/pull_request_webhook_properties.md,broken liquid tags translations/zh-CN/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md,broken liquid tags translations/zh-CN/data/reusables/webhooks/workflow_run_properties.md,broken liquid tags +translations/zh-CN/data/variables/product.yml,broken liquid tags diff --git a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md index d9234f8cc1..18798d0d6f 100644 --- a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md +++ b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md @@ -1,6 +1,6 @@ --- -title: 关于通知 -intro: '通知提供有关你在 {% data variables.product.product_location %} 上已订阅活动的更新。 可以使用通知收件箱来自定义、分类和管理更新。' +title: About notifications +intro: 'Notifications provide updates about the activity on {% data variables.location.product_location %} that you''ve subscribed to. You can use the notifications inbox to customize, triage, and manage your updates.' redirect_from: - /articles/notifications - /articles/about-notifications @@ -14,90 +14,86 @@ versions: ghec: '*' topics: - Notifications -ms.openlocfilehash: 87034df88eb94c1d880806f01cb8748ed555a284 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147432022' --- -## 通知和订阅 -可选择通过订阅接收有关 {% data variables.product.product_location %} 上的特定活动的持续更新。 通知是您收到的已订阅特定活动的更新。 +## Notifications and subscriptions -### 订阅选项 +You can choose to receive ongoing updates about specific activity on {% data variables.location.product_location %} through a subscription. Notifications are updates that you receive for specific activity that you are subscribed to. -您可以选择订阅关于以下内容的通知: -- 关于特定议题、拉取请求或 Gist 的对话。 -- 仓库或团队讨论中的所有活动。 -- CI 活动,例如仓库中使用 {% data variables.product.prodname_actions %} 设置的工作流程的状态。 -- 仓库 {% data reusables.notifications-v2.custom-notification-types %} (如果启用)。 +### Subscription options -您也可以选择自动关注所有您有推送访问权限的仓库,但复刻除外。 可单击“关注”来手动关注你有权访问的任何其他存储库。 +You can choose to subscribe to notifications for: +- A conversation in a specific issue, pull request, or gist. +- All activity in a repository or team discussion. +- CI activity, such as the status of workflows in repositories set up with {% data variables.product.prodname_actions %}. +- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled). -如果您的某项对话不再感兴趣,您可以取消订阅、取消关注或自定义以后接收的通知类型。 例如,如果不想再接收特定存储库的通知,可单击“取消订阅”。 有关详细信息,请参阅“[管理订阅](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)”。 +You can also choose to automatically watch all repositories that you have push access to, except forks. You can watch any other repository you have access to manually by clicking **Watch**. -### 默认订阅 +If you're no longer interested in a conversation, you can unsubscribe, unwatch, or customize the types of notifications you'll receive in the future. For example, if you no longer want to receive notifications from a particular repository, you can click **Unsubscribe**. For more information, see "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." -一般来说,默认在以下情况下自动订阅对话: -- 在通知设置中未禁用自动关注您加入的仓库或团队。 默认情况下,此设置处于启用状态。 -- 被分配了议题或拉取请求。 -- 打开了拉取请求、议题或创建了团队讨论帖子。 -- 在帖子中发表了评论。 -- 通过单击“关注”或“订阅”手动订阅了帖子 。 -- 向你的用户名执行了 @mentioned。 -- 更改了帖子的状态,例如通过关闭议题或合并拉取请求。 -- 向你所属的团队执行了 @mentioned。 +### Default subscriptions -默认情况下,还会自动关注你创建的以及你的个人帐户所拥有的所有存储库。 +In general, you are automatically subscribed to conversations by default when you have: +- Not disabled automatic watching for repositories or teams you've joined in your notification settings. This setting is enabled by default. +- Been assigned to an issue or pull request. +- Opened a pull request, issue, or created a team discussion post. +- Commented on a thread. +- Subscribed to a thread manually by clicking **Watch** or **Subscribe**. +- Had your username @mentioned. +- Changed the state of a thread, such as by closing an issue or merging a pull request. +- Had a team you're a member of @mentioned. -要取消订阅自动订阅的对话,可更改通知设置,或者直接取消订阅或取消关注 {% data variables.product.product_location %} 上的活动。 有关详细信息,请参阅“[管理订阅](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)”。 +By default, you also automatically watch all repositories that you create and are owned by your personal account. -## 自定义通知和订阅 +To unsubscribe from conversations you're automatically subscribed to, you can change your notification settings or directly unsubscribe or unwatch activity on {% data variables.location.product_location %}. For more information, see "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." -可选择通过 [https://github.com/notifications](https://github.com/notifications){% ifversion fpt or ghes or ghec %} 上和 {% data variables.product.prodname_mobile %} 应用中的通知收件箱查看通知{% endif %},或者通过电子邮件或这些选项的某种组合进行查看。 +## Customizing notifications and subscriptions -要自定义您希望接收的更新类型以及将这些更新发送至何处,请配置通知设置。 有关详细信息,请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)”。 +You can choose to view your notifications through the notifications inbox at [https://github.com/notifications](https://github.com/notifications){% ifversion fpt or ghes or ghec %} and in the {% data variables.product.prodname_mobile %} app{% endif %}, through your email, or some combination of these options. -要保持订阅的可管理性,请审查您的订阅和关注的仓库,并根据需要取消订阅。 有关详细信息,请参阅“[在 GitHub 上管理活动的订阅](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)”。 +To customize the types of updates you'd like to receive and where to send those updates, configure your notification settings. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)." -要自定义如何接收特定拉取请求或议题的更新,可以在议题或拉取请求中配置首选项。 有关详细信息,请参阅“[对单个通知进行分类](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)”。 +To keep your subscriptions manageable, review your subscriptions and watched repositories and unsubscribe as needed. For more information, see "[Managing subscriptions for activity on GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)." -{% ifversion fpt or ghes or ghec %} 可在 {% data variables.product.prodname_mobile %} 应用中自定义和安排推送通知。 有关详细信息,请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#managing-your-notification-settings-with-github-mobile)”。 +To customize how you'd like to receive updates for specific pull requests or issues, you can configure your preferences within the issue or pull request. For more information, see "[Triaging a single notification](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)." + +{% ifversion fpt or ghes or ghec %} +You can customize and schedule push notifications in the {% data variables.product.prodname_mobile %} app. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#managing-your-notification-settings-with-github-mobile)." {% endif %} -## 接收通知的原因 +## Reasons for receiving notifications -您的收件箱配置了默认过滤器,它们代表人们需要跟进通知的最常见原因。 有关收件箱筛选器的详细信息,请参阅“[管理收件箱中的通知](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#default-notification-filters)”。 +Your inbox is configured with default filters, which represent the most common reasons that people need to follow-up on their notifications. For more information about inbox filters, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#default-notification-filters)." -收件箱以标签形式显示你接收通知的 `reasons`。 +Your inbox shows the `reasons` you're receiving notifications as a label. -![收件箱中的原因标签](/assets/images/help/notifications-v2/reasons-as-labels-in-inbox.png) +![Reasons labels in inbox](/assets/images/help/notifications-v2/reasons-as-labels-in-inbox.png) -您可以按订阅通知的原因过滤收件箱。 例如,要仅查看有人请求你审查的拉取请求,可使用 `review-requested` 查询筛选器。 +You can filter your inbox by the reason you're subscribed to notifications. For example, to only see pull requests where someone requested your review, you can use the `review-requested` query filter. -![通过查看请求的原因过滤通知](/assets/images/help/notifications-v2/review-requested-reason.png) +![Filter notifications by review requested reason](/assets/images/help/notifications-v2/review-requested-reason.png) -如果您已将通知配置为通过电子邮件发送,但认为您收到了不属于自己的通知,请考虑使用显示预期收件人的电子邮件标头排除故障。 有关详细信息,请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)”。 +If you've configured notifications to be sent by email and believe you're receiving notifications that don't belong to you, consider troubleshooting with email headers, which show the intended recipient. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)." -## 从收件箱分类通知 +## Triaging notifications from your inbox -为了有效地管理通知,您可以使用以下选项对收件箱进行分类: -- 从收件箱中删除带有“完成”标记的通知。 可单击边栏中的“完成”或使用 `is:done` 查询集中查看所有“已完成”的通知 。 -- 将通知标记为已读或未读。 -- 保存通知供以后查看。 已保存的通知会在收件箱中标记。 可在边栏中单击“已保存”或使用 `is:saved` 查询集中查看所有“已保存”的通知 。 -- 自动取消订阅此通知和此对话的未来更新。 取消订阅还会从收件箱中删除通知。 如果您取消订阅了对话,但有人在此对话中提及您的用户名或您所在的团队(您正在为其接收更新),则您将再次开始接收此对话的通知。 +To effectively manage your notifications, you can triage your inbox with options to: +- Remove a notification from the inbox with **Done**. You can review **Done** notifications all in one place by clicking **Done** in the sidebar or by using the query `is:done`. +- Mark a notification as read or unread. +- **Save** a notification for later review. **Saved** notifications are flagged in your inbox. You can review **Saved** notifications all in one place in the sidebar by clicking **Saved** or by using the query `is:saved`. +- Automatically unsubscribe from this notification and future updates from this conversation. Unsubscribing also removes the notification from your inbox. If you unsubscribe from a conversation and someone mentions your username or a team you're on that you're receiving updates for, then you will start to receive notifications from this conversation again. -您还可以从收件箱中一次分类多个通知。 有关详细信息,请参阅“[管理收件箱中的通知](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)”。 +From your inbox you can also triage multiple notifications at once. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)." -## 自定义通知收件箱 +## Customizing your notifications inbox -要在 {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} 或 {% data variables.product.prodname_mobile %}{% endif %} 上的收件箱中关注一组通知,可创建自定义筛选器。 例如,您可以为您参与的开源项目创建自定义过滤器,只查看您被提及的仓库的通知。 有关详细信息,请参阅“[管理收件箱中的通知](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)”。 有关如何自定义分类工作流的更多示例,请参阅“[自定义对通知进行分类的工作流](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)”。 +To focus on a group of notifications in your inbox on {% data variables.location.product_location %}{% ifversion fpt or ghes or ghec %} or {% data variables.product.prodname_mobile %}{% endif %}, you can create custom filters. For example, you can create a custom filter for an open source project you contribute to and only see notifications for that repository in which you are mentioned. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)." For more examples of how to customize your triaging workflow, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)." -## 通知保留策略 +## Notification retention policy -未标记为“已保存”的通知将保留 5 个月。 标记为“已保存”的通知将无限期保留。 如果已保存通知超过 5 个月后,您取消保存它,则该通知将在一天之内从收件箱中消失。 +Notifications that are not marked as **Saved** are kept for 5 months. Notifications marked as **Saved** are kept indefinitely. If your saved notification is older than 5 months and you unsave it, the notification will disappear from your inbox within a day. -## 反馈和支持 +## Feedback and support -如果你有针对通知的反馈或功能请求,请使用 [{% data variables.product.prodname_github_community %} 讨论](https://github.com/orgs/community/discussions/categories/general)。 +If you have feedback or feature requests for notifications, use a [{% data variables.product.prodname_github_community %} discussion](https://github.com/orgs/community/discussions/categories/general). diff --git a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md index f0ec8c75e9..ee9ed4f6aa 100644 --- a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md +++ b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md @@ -26,11 +26,11 @@ topics: ## Notification delivery options -You can receive notifications for activity on {% data variables.product.product_location %} in the following locations. +You can receive notifications for activity on {% data variables.location.product_location %} in the following locations. - - The notifications inbox in the {% data variables.product.product_location %} web interface{% ifversion fpt or ghes or ghec %} - - The notifications inbox on {% data variables.product.prodname_mobile %}, which syncs with the inbox on {% data variables.product.product_location %}{% endif %} - - An email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} and {% data variables.product.prodname_mobile %}{% endif %} + - The notifications inbox in the {% data variables.location.product_location %} web interface{% ifversion fpt or ghes or ghec %} + - The notifications inbox on {% data variables.product.prodname_mobile %}, which syncs with the inbox on {% data variables.location.product_location %}{% endif %} + - An email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.location.product_location %}{% ifversion fpt or ghes or ghec %} and {% data variables.product.prodname_mobile %}{% endif %} {% ifversion fpt or ghes or ghec %} {% data reusables.notifications-v2.notifications-inbox-required-setting %} For more information, see "[Choosing your notification settings](#choosing-your-notification-settings)." @@ -40,12 +40,12 @@ You can receive notifications for activity on {% data variables.product.product_ ### Benefits of the notifications inbox -The notifications inbox on {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} and {% data variables.product.prodname_mobile %}{% endif %} includes triaging options designed specifically for your {% data variables.product.prodname_dotcom %} notifications flow, including options to: +The notifications inbox on {% data variables.location.product_location %}{% ifversion fpt or ghes or ghec %} and {% data variables.product.prodname_mobile %}{% endif %} includes triaging options designed specifically for your {% data variables.product.prodname_dotcom %} notifications flow, including options to: - Triage multiple notifications at once. - Mark completed notifications as **Done** and remove them from your inbox. To view all of your notifications marked as **Done**, use the `is:done` query. - Save a notification to review later. Saved notifications are flagged in your inbox and kept indefinitely. To view all of your saved notifications, use the `is:saved` query. - Unsubscribe and remove a notification from your inbox. - - Preview the issue, pull request, or team discussion where the notification originates on {% data variables.product.product_location %} from within the notifications inbox. + - Preview the issue, pull request, or team discussion where the notification originates on {% data variables.location.product_location %} from within the notifications inbox. - See one of the latest reasons you're receiving a notification from your inbox with a `reasons` label. - Create custom filters to focus on different notifications when you want. - Group notifications in your inbox by repository or date to get a quick overview with less context switching @@ -85,7 +85,7 @@ Anytime you comment in a conversation or when someone @mentions your username, y {% else %} -For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.product.product_location %}{% ifversion ghes %} and {% data variables.product.prodname_mobile %}{% endif %}. For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)." +For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.location.product_location %}{% ifversion ghes %} and {% data variables.product.prodname_mobile %}{% endif %}. For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)." ![Screenshot of participating and watching notifications options](/assets/images/help/notifications-v2/participating-and-watching-options.png){% endif %} @@ -103,7 +103,7 @@ If you do not enable watching or participating notifications for web{% ifversion ## Customizing your email notifications -After enabling email notifications, {% data variables.product.product_location %} will send notifications to you as multipart emails that contain both HTML and plain text copies of the content. Email notification content includes any Markdown, @mentions, emojis, hash-links, and more, that appear in the original content on {% data variables.product.product_location %}. If you only want to see the text in the email, you can configure your email client to display the plain text copy only. +After enabling email notifications, {% data variables.location.product_location %} will send notifications to you as multipart emails that contain both HTML and plain text copies of the content. Email notification content includes any Markdown, @mentions, emojis, hash-links, and more, that appear in the original content on {% data variables.location.product_location %}. If you only want to see the text in the email, you can configure your email client to display the plain text copy only. {% data reusables.notifications.outbound_email_tip %} @@ -117,7 +117,7 @@ If you're using Gmail, you can click a button beside the notification email to v {% endif %} -Choose a default email address where you want to send updates for conversations you're participating in or watching. You can also specify which activity on {% data variables.product.product_location %} you want to receive updates for using your default email address. For example, choose whether you want updates to your default email from: +Choose a default email address where you want to send updates for conversations you're participating in or watching. You can also specify which activity on {% data variables.location.product_location %} you want to receive updates for using your default email address. For example, choose whether you want updates to your default email from: - Comments on issues and pull requests. - Pull request reviews. - Pull request pushes. @@ -131,11 +131,11 @@ You can also send notifications for a specific repository to an email address. F ## Filtering email notifications -Each email notification that {% data variables.product.product_location %} sends contains header information. The header information in every email is consistent, so you can use it in your email client to filter or forward all {% data variables.product.prodname_dotcom %} notifications, or certain types of {% data variables.product.prodname_dotcom %} notifications. +Each email notification that {% data variables.location.product_location %} sends contains header information. The header information in every email is consistent, so you can use it in your email client to filter or forward all {% data variables.product.prodname_dotcom %} notifications, or certain types of {% data variables.product.prodname_dotcom %} notifications. If you believe you're receiving notifications that don't belong to you, examine the `X-GitHub-Recipient` and `X-GitHub-Recipient-Address` headers. These headers show who the intended recipient is. Depending on your email setup, you may receive notifications intended for another user. -Email notifications from {% data variables.product.product_location %} contain the following header information: +Email notifications from {% data variables.location.product_location %} contain the following header information: | Header | Information | | --- | --- | diff --git a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md index 16a6dbcd4c..ba60987068 100644 --- a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md +++ b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md @@ -1,6 +1,6 @@ --- -title: 从收件箱管理通知 -intro: '使用收件箱快速分类并在电子邮件{% ifversion fpt or ghes or ghec %}与手机{% endif %}之间同步你的通知。' +title: Managing notifications from your inbox +intro: 'Use your inbox to quickly triage and sync your notifications across email{% ifversion fpt or ghes or ghec %} and mobile{% endif %}.' redirect_from: - /articles/marking-notifications-as-read - /articles/saving-notifications-for-later @@ -14,102 +14,98 @@ versions: topics: - Notifications shortTitle: Manage from your inbox -ms.openlocfilehash: 83aa9ce53f68636e299c3a83fe8d06dd189d5d6c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147060456' --- -## 关于收件箱 -{% ifversion fpt or ghes or ghec %} {% data reusables.notifications-v2.notifications-inbox-required-setting %} 有关详细信息,请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)”。 +## About your inbox + +{% ifversion fpt or ghes or ghec %} +{% data reusables.notifications-v2.notifications-inbox-required-setting %} For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)." {% endif %} -要访问通知收件箱,请在任意页面的右上角单击 {% octicon "bell" aria-label="The notifications bell" %}。 +To access your notifications inbox, in the upper-right corner of any page, click {% octicon "bell" aria-label="The notifications bell" %}. - ![表示任何未读消息的通知](/assets/images/help/notifications/notifications_general_existence_indicator.png) + ![Notification indicating any unread message](/assets/images/help/notifications/notifications_general_existence_indicator.png) -收件箱将显示所有尚未取消订阅或标记为“完成”的通知。 可按最适合工作流的方式自定义收件箱,方法包括使用筛选器、查看所有通知或只查看未读通知以及对通知进行分组便于快速了解。 +Your inbox shows all of the notifications that you haven't unsubscribed to or marked as **Done.** You can customize your inbox to best suit your workflow using filters, viewing all or just unread notifications, and grouping your notifications to get a quick overview. - ![收件箱视图](/assets/images/help/notifications-v2/inbox-view.png) + ![inbox view](/assets/images/help/notifications-v2/inbox-view.png) -默认情况下,您的收件箱将显示已读和未读通知。 要仅查看未读通知,可单击“未读”或使用 `is:unread` 查询。 +By default, your inbox will show read and unread notifications. To only see unread notifications, click **Unread** or use the `is:unread` query. - ![未读收件箱视图](/assets/images/help/notifications-v2/unread-inbox-view.png) + ![unread inbox view](/assets/images/help/notifications-v2/unread-inbox-view.png) -## 分类选项 +## Triaging options -有多个选项可对收件箱中的通知进行分类。 +You have several options for triaging notifications from your inbox. -| 分类选项 | 说明 | +| Triaging option | Description | |-----------------|-------------| -| 保存 | 保存通知供以后查看。 要保存通知,请在通知右侧单击 {% octicon "bookmark" aria-label="The bookmark icon" %}。

已保存的通知将无限期保存,可单击边栏中的“已保存”或通过 `is:saved` 查询进行查看。 如果您保存的通知超过5个月并且变成未保存,通知将在一天内从收件箱消失。 | -| 完成 | 将通知标记为已完成,并从收件箱中删除通知。 可单击边栏中的“完成”或通过 `is:done` 查询查看所有已完成的通知。 标记为“完成”的通知将保存 5 个月。 -| 取消订阅 | 自动从收件箱中删除通知并让你通过对话取消订阅,仅当 @mentioned你、@mentioned你所属团队或者请求你审查时才会收到通知。 -| 读取 | 将通知标记为已读。 要在收件箱中只查看已读通知,可使用 `is:read` 查询。 此查询不包括标记为“完成”的通知。 -| Unread | 将通知标记为未读。 要在收件箱中只查看未读通知,可使用 `is:unread` 查询。 | +| Save | Saves your notification for later review. To save a notification, to the right of the notification, click {% octicon "bookmark" aria-label="The bookmark icon" %}.

Saved notifications are kept indefinitely and can be viewed by clicking **Saved** in the sidebar or with the `is:saved` query. If your saved notification is older than 5 months and becomes unsaved, the notification will disappear from your inbox within a day. | +| Done | Marks a notification as completed and removes the notification from your inbox. You can see all completed notifications by clicking **Done** in the sidebar or with the `is:done` query. Notifications marked as **Done** are saved for 5 months. +| Unsubscribe | Automatically removes the notification from your inbox and unsubscribes you from the conversation until you are @mentioned, a team you're on is @mentioned, or you're requested for review. +| Read | Marks a notification as read. To only view read notifications in your inbox, use the `is:read` query. This query doesn't include notifications marked as **Done**. +| Unread | Marks notification as unread. To only view unread notifications in your inbox, use the `is:unread` query. | -若要查看可用的键盘快捷方式,请参阅“[键盘快捷方式](/github/getting-started-with-github/keyboard-shortcuts#notifications)”。 +To see the available keyboard shortcuts, see "[Keyboard Shortcuts](/github/getting-started-with-github/keyboard-shortcuts#notifications)." -在选择分类选项之前,您可以先预览通知的详细信息并进行调查。 有关详细信息,请参阅“[对单个通知进行分类](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification)”。 +Before choosing a triage option, you can preview your notification's details first and investigate. For more information, see "[Triaging a single notification](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification)." -## 同时对多种通知分类 +## Triaging multiple notifications at the same time -要一次对多种通知分类,请选择相关通知并使用 {% octicon "kebab-horizontal" aria-label="The edit icon" %} 下拉列表选择分类选项。 +To triage multiple notifications at once, select the relevant notifications and use the {% octicon "kebab-horizontal" aria-label="The edit icon" %} drop-down to choose a triage option. -![带有分类选项和选定通知的下拉菜单](/assets/images/help/notifications-v2/triage-multiple-notifications-together.png) +![Drop-down menu with triage options and selected notifications](/assets/images/help/notifications-v2/triage-multiple-notifications-together.png) -## 默认通知过滤器 +## Default notification filters -默认情况下,收件箱中有针对分配给你的任务、参与的帖子、请求审查拉取请求的筛选器,或者针对直接 @mentioned你的用户名或 @mentioned你所属团队的筛选器。 +By default, your inbox has filters for when you are assigned, participating in a thread, requested to review a pull request, or when your username is @mentioned directly or a team you're a member of is @mentioned. - ![默认自定义过滤器](/assets/images/help/notifications-v2/default-filters.png) + ![Default custom filters](/assets/images/help/notifications-v2/default-filters.png) -## 使用自定义过滤器自定义收件箱 +## Customizing your inbox with custom filters -您可以添加最多 15 个自定义过滤器。 +You can add up to 15 of your own custom filters. {% data reusables.notifications.access_notifications %} -2. 若要打开筛选器设置,在左侧边栏的“筛选器”旁边,单击 {% octicon "gear" aria-label="The Gear icon" %}。 +2. To open the filter settings, in the left sidebar, next to "Filters", click {% octicon "gear" aria-label="The Gear icon" %}. {% tip %} - 提示:可通过在收件箱视图中创建查询并单击“保存”快速预览筛选器的收件箱结果,这将打开自定义筛选器设置 。 + **Tip:** You can quickly preview a filter's inbox results by creating a query in your inbox view and clicking **Save**, which opens the custom filter settings. {% endtip %} -3. 为过滤器和过滤器查询添加名称。 例如,若要仅查看特定存储库的通知,可以使用查询 `repo:octocat/open-source-project-name reason:participating` 创建筛选器。 您也可以用原生表情键盘添加表情符号。 有关支持的搜索查询的列表,请参阅“[支持的自定义筛选器查询](#supported-queries-for-custom-filters)”。 +3. Add a name for your filter and a filter query. For example, to only see notifications for a specific repository, you can create a filter using the query `repo:octocat/open-source-project-name reason:participating`. You can also add emojis with a native emoji keyboard. For a list of supported search queries, see "[Supported queries for custom filters](#supported-queries-for-custom-filters)." - ![自定义过滤器示例](/assets/images/help/notifications-v2/custom-filter-example.png) + ![Custom filter example](/assets/images/help/notifications-v2/custom-filter-example.png) -4. 单击“创建”。 +4. Click **Create**. -## 自定义过滤器限制 +## Custom filter limitations -自定义过滤器当前不支持: - - 收件箱中的全文搜索,包括搜索拉取请求或议题标题。 - - 区分 `is:issue`、`is:pr` 和 `is:pull-request` 查询筛选器。 这些查询将返回议题和拉取请求。 - - 创建超过 15 个自定义过滤器。 - - 更改默认过滤器或其顺序。 - - 使用 `NOT` 或 `-QUALIFIER` 搜索[排除项](/github/searching-for-information-on-github/understanding-the-search-syntax#exclude-certain-results)。 +Custom filters do not currently support: + - Full text search in your inbox, including searching for pull request or issue titles. + - Distinguishing between the `is:issue`, `is:pr`, and `is:pull-request` query filters. These queries will return both issues and pull requests. + - Creating more than 15 custom filters. + - Changing the default filters or their order. + - Search [exclusion](/github/searching-for-information-on-github/understanding-the-search-syntax#exclude-certain-results) using `NOT` or `-QUALIFIER`. -## 支持的自定义过滤器查询 +## Supported queries for custom filters -以下是您可以使用的过滤器类型: - - 使用 `repo:` 按存储库筛选 - - 使用 `is:` 按讨论类型筛选 - - 使用 `reason:`{% ifversion fpt or ghec %} 按通知原因筛选 - - 使用 `author:` 按通知作者筛选 - - 使用 `org:`{% endif %} 按组织筛选 +These are the types of filters that you can use: + - Filter by repository with `repo:` + - Filter by discussion type with `is:` + - Filter by notification reason with `reason:`{% ifversion fpt or ghec %} + - Filter by notification author with `author:` + - Filter by organization with `org:`{% endif %} -### 支持的 `repo:` 查询 +### Supported `repo:` queries -要添加 `repo:` 筛选器,必须在查询中包含存储库的所有者:`repo:owner/repository`。 所有者是拥有触发通知的 {% data variables.product.prodname_dotcom %} 资产的组织或用户。 例如,`repo:octo-org/octo-repo` 将会显示在 octo-org 组织内的 octo-repo 存储库中触发的通知。 +To add a `repo:` filter, you must include the owner of the repository in the query: `repo:owner/repository`. An owner is the organization or the user who owns the {% data variables.product.prodname_dotcom %} asset that triggers the notification. For example, `repo:octo-org/octo-repo` will show notifications triggered in the octo-repo repository within the octo-org organization. -### 支持的 `is:` 查询 +### Supported `is:` queries -要在 {% data variables.product.product_location %} 上筛选特定活动的通知,可使用 `is` 查询。 例如,若仅查看存储库邀请更新,请使用 `is:repository-invitation`{% ifversion not ghae %},若仅查看 {% data variables.product.prodname_dependabot_alerts %},请使用 `is:repository-vulnerability-alert`{% endif %}。 +To filter notifications for specific activity on {% data variables.location.product_location %}, you can use the `is` query. For example, to only see repository invitation updates, use `is:repository-invitation`{% ifversion not ghae %}, and to only see {% data variables.product.prodname_dependabot_alerts %}, use `is:repository-vulnerability-alert`{% endif %}. - `is:check-suite` - `is:commit` @@ -122,63 +118,64 @@ ms.locfileid: '147060456' - `is:team-discussion`{% ifversion fpt or ghec %} - `is:discussion`{% endif %} -有关减少 {% data variables.product.prodname_dependabot_alerts %} 通知干扰的信息,请参阅“[配置 {% data variables.product.prodname_dependabot_alerts %} 的通知](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)”。 +For information about reducing noise from notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)." -还可使用 `is:` 查询来描述如何对通知进行分类。 +You can also use the `is:` query to describe how the notification was triaged. - `is:saved` - `is:done` - `is:unread` - `is:read` -### 支持的 `reason:` 查询 +### Supported `reason:` queries -要根据收到更新的原因筛选通知,可使用 `reason:` 查询。 例如,要查看请求你(或所属团队)审查拉取请求时的通知,请使用 `reason:review-requested`。 有关详细信息,请参阅“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)”。 +To filter notifications by why you've received an update, you can use the `reason:` query. For example, to see notifications when you (or a team you're on) is requested to review a pull request, use `reason:review-requested`. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)." -| 查询 | 说明 | +| Query | Description | |-----------------|-------------| -| `reason:assign` | 分配给您的议题或拉取请求有更新时。 -| `reason:author` | 当您打开拉取请求或议题并且有更新或新评论时。 -| `reason:comment`| 当您评论了议题、拉取请求或团队讨论时。 -| `reason:participating` | 当你在问题、拉取请求或团队讨论中发表了评论或者 @mentioned 你时。 -| `reason:invitation` | 当您被邀请加入团队、组织或仓库时。 -| `reason:manual` | 当你在尚未订阅的问题或拉取请求上单击“订阅”时。 -| `reason:mention` | 直接 @mentioned你时。 -| `reason:review-requested` | 有人请求您或您所在的团队审查拉取请求。 -| `reason:security-alert` | 为仓库发出安全警报时。 -| `reason:state-change` | 当拉取请求或议题的状态改变时。 例如,议题已关闭或拉取请求合并时。 -| `reason:team-mention` | @mentioned你所属团队时。 -| `reason:ci-activity` | 当仓库有 CI 更新时,例如新的工作流程运行状态。 +| `reason:assign` | When there's an update on an issue or pull request you've been assigned to. +| `reason:author` | When you opened a pull request or issue and there has been an update or new comment. +| `reason:comment`| When you commented on an issue, pull request, or team discussion. +| `reason:participating` | When you have commented on an issue, pull request, or team discussion or you have been @mentioned. +| `reason:invitation` | When you're invited to a team, organization, or repository. +| `reason:manual` | When you click **Subscribe** on an issue or pull request you weren't already subscribed to. +| `reason:mention` | You were directly @mentioned. +| `reason:review-requested` | You or a team you're on have been requested to review a pull request. +| `reason:security-alert` | When a security alert is issued for a repository. +| `reason:state-change` | When the state of a pull request or issue is changed. For example, an issue is closed or a pull request is merged. +| `reason:team-mention` | When a team you're a member of is @mentioned. +| `reason:ci-activity` | When a repository has a CI update, such as a new workflow run status. {% ifversion fpt or ghec %} -### 支持的 `author:` 查询 +### Supported `author:` queries -要按用户筛选通知,可使用 `author:` 查询。 作者是指与通知相关的线程(议题、拉取请求、Gist、讨论等)的原作者。 例如,要查看与 Octocat 用户创建的帖子相关的通知,可使用 `author:octocat`。 +To filter notifications by user, you can use the `author:` query. An author is the original author of the thread (issue, pull request, gist, discussions, and so on) for which you are being notified. For example, to see notifications for threads created by the Octocat user, use `author:octocat`. -### 支持的 `org:` 查询 +### Supported `org:` queries -要按组织筛选通知,可使用 `org` 查询。 您需要在查询中指定的组织是与您在 {% data variables.product.prodname_dotcom %} 上收到的通知相关之仓库所属的组织。 如果您属于多个组织,并且想要查看特定组织的通知,则此查询很有用。 +To filter notifications by organization, you can use the `org` query. The organization you need to specify in the query is the organization of the repository for which you are being notified on {% data variables.product.prodname_dotcom %}. This query is useful if you belong to several organizations, and want to see notifications for a specific organization. -例如,要查看来自 octo-org 组织的通知,可使用 `org:octo-org`。 +For example, to see notifications from the octo-org organization, use `org:octo-org`. {% endif %} -## {% data variables.product.prodname_dependabot %} 自定义过滤器 +## {% data variables.product.prodname_dependabot %} custom filters -{% ifversion fpt or ghec or ghes > 3.2 %} 如果使用 {% data variables.product.prodname_dependabot %} 来保持依赖项更新,可使用并保存这些自定义筛选器: -- `is:repository_vulnerability_alert`,显示 {% data variables.product.prodname_dependabot_alerts %} 的通知。 -- `reason:security_alert`,显示 {% data variables.product.prodname_dependabot_alerts %} 的通知和安全更新拉取请求。 -- `author:app/dependabot`,显示 {% data variables.product.prodname_dependabot %} 生成的通知。 这包括 {% data variables.product.prodname_dependabot_alerts %}、安全更新拉取请求和版本更新拉取请求。 +{% ifversion fpt or ghec or ghes > 3.2 %} +If you use {% data variables.product.prodname_dependabot %} to keep your dependencies up-to-date, you can use and save these custom filters: +- `is:repository_vulnerability_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %}. +- `reason:security_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %} and security update pull requests. +- `author:app/dependabot` to show notifications generated by {% data variables.product.prodname_dependabot %}. This includes {% data variables.product.prodname_dependabot_alerts %}, security update pull requests, and version update pull requests. -有关 {% data variables.product.prodname_dependabot %} 的详细信息,请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”。 +For more information about {% data variables.product.prodname_dependabot %}, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." {% endif %} {% ifversion ghes < 3.3 or ghae %} -如果使用 {% data variables.product.prodname_dependabot %} 来告知不安全的依赖项,则可以使用并保存这些自定义筛选器来显示 {% data variables.product.prodname_dependabot_alerts %} 的通知: +If you use {% data variables.product.prodname_dependabot %} to tell you about insecure dependencies, you can use and save these custom filters to show notifications for {% data variables.product.prodname_dependabot_alerts %}: - `is:repository_vulnerability_alert` - `reason:security_alert` -有关 {% data variables.product.prodname_dependabot %} 的详细信息,请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 +For more information about {% data variables.product.prodname_dependabot %}, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." {% endif %} diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md index c0511693a3..b7f02b36e0 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md @@ -14,7 +14,7 @@ shortTitle: Your profile README --- ## About your profile README -You can share information about yourself with the community on {% data variables.product.product_location %} by creating a profile README. {% data variables.product.prodname_dotcom %} shows your profile README at the top of your profile page. +You can share information about yourself with the community on {% data variables.location.product_location %} by creating a profile README. {% data variables.product.prodname_dotcom %} shows your profile README at the top of your profile page. You decide what information to include in your profile README, so you have full control over how you present yourself on {% data variables.product.prodname_dotcom %}. Here are some examples of information that visitors may find interesting, fun, or useful in your profile README. diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md index 850fdd4282..e8a2772e9f 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md @@ -59,7 +59,7 @@ You can change the name that is displayed on your profile. This name may also be {% ifversion fpt or ghec %} {% note %} -**Note:** If you're a member of an {% data variables.product.prodname_emu_enterprise %}, any changes to your profile name must be made through your identity provider instead of {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} +**Note:** If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, any changes to your profile name must be made through your identity provider instead of {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} {% endnote %} {% endif %} diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md index fa7327e5cf..e88e940a1c 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md @@ -20,7 +20,7 @@ If you publicize your private contributions, people without access to the privat {% note %} -**Note:** {% ifversion fpt or ghes or ghec %}On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, public contributions on your profile are visible {% ifversion fpt or ghec %}to anyone in the world who can access {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}only to other users of {% data variables.product.product_location%}{% endif %}.{% elsif ghae %}On {% data variables.product.prodname_ghe_managed %}, only other members of your enterprise can see the contributions on your profile.{% endif %} +**Note:** {% ifversion fpt or ghes or ghec %}On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, public contributions on your profile are visible {% ifversion fpt or ghec %}to anyone in the world who can access {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}only to other users of {% data variables.location.product_location%}{% endif %}.{% elsif ghae %}On {% data variables.product.prodname_ghe_managed %}, only other members of your enterprise can see the contributions on your profile.{% endif %} {% endnote %} diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md index 8ee42c95d4..5581d21cd0 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md @@ -1,6 +1,6 @@ --- -title: 在个人资料中查看贡献 -intro: '你的 {% data variables.product.product_name %} 个人资料显示{% ifversion fpt or ghes or ghec %}你的固定存储库、成就和{% endif %}过去一年中存储库贡献的图。' +title: Viewing contributions on your profile +intro: 'Your {% data variables.product.product_name %} profile shows off {% ifversion fpt or ghes or ghec %}your pinned repositories, Achievements, and{% endif %} a graph of your repository contributions over the past year.' redirect_from: - /articles/viewing-contributions - /articles/viewing-contributions-on-your-profile-page @@ -15,89 +15,83 @@ versions: topics: - Profiles shortTitle: View contributions -ms.openlocfilehash: 81b2242e0c7a07d8941375d044cacc65ca8dd56d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147079523' --- -{% ifversion fpt or ghes or ghec %}你的贡献图和“成就”显示公共存储库的活动。 {% endif %}可以选择显示 {% ifversion fpt or ghes or ghec %} 公共和 {% endif %} 私有存储库的活动,并将私有存储库中活动的具体详细信息匿名化。 有关详细信息,请参阅“[在配置文件中公开或隐藏私人贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)”。 +{% ifversion fpt or ghes or ghec %}Your contribution graph and Achievements show activity from public repositories. {% endif %}You can choose to show activity from {% ifversion fpt or ghes or ghec %}both public and {% endif %}private repositories, with specific details of your activity in private repositories anonymized. For more information, see "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)." {% note %} -注意:仅当用于创作提交的电子邮件地址与在 {% data variables.product.product_name %} 上的帐户相连时,提交才会显示在你的贡献图中。 有关详细信息,请参阅“[为什么我的贡献没有在我的配置文件中显示?](/articles/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)” +**Note:** Commits will only appear on your contributions graph if the email address you used to author the commits is connected to your account on {% data variables.product.product_name %}. For more information, see "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)" {% endnote %} -## 计为贡献的内容 +## What counts as a contribution -在您的个人资料页面上,某些操作计为贡献: +On your profile page, certain actions count as contributions: -- 提交到存储库的默认分支或 `gh-pages` 分支 -- 创建问题 -- 打开讨论 -- 回答讨论 -- 提议拉取请求 -- 提交拉取请求审查 {% ifversion ghes or ghae %} -- 合作创作存储库默认分支或 `gh-pages` 分支中的提交{% endif %} +- Committing to a repository's default branch or `gh-pages` branch +- Opening an issue +- Opening a discussion +- Answering a discussion +- Proposing a pull request +- Submitting a pull request review{% ifversion ghes or ghae %} +- Co-authoring commits in a repository's default branch or `gh-pages` branch{% endif %} {% data reusables.pull_requests.pull_request_merges_and_contributions %} -## 受欢迎的仓库 +## Popular repositories -此部分显示具有最多查看者的仓库。 {% ifversion fpt or ghes or ghec %}[将存储库固定到配置文件](/articles/pinning-repositories-to-your-profile)后,此部分将更改为“固定的存储库”。{% endif %} +This section displays your repositories with the most watchers. {% ifversion fpt or ghes or ghec %}Once you [pin repositories to your profile](/articles/pinning-repositories-to-your-profile), this section will change to "Pinned repositories."{% endif %} -![受欢迎的仓库](/assets/images/help/profile/profile_popular_repositories.png) +![Popular repositories](/assets/images/help/profile/profile_popular_repositories.png) {% ifversion fpt or ghes or ghec %} -## 固定的仓库 +## Pinned repositories -此部分显示最多六个公共仓库,并可包括您的仓库以及您对其做出贡献的仓库。 为便于查看关于你选择提供的存储库的重要详细信息,此部分中的每个存储库均包括所做工作的摘要、存储库已收到的[星号](/articles/saving-repositories-with-stars/)数量以及存储库中使用的主要编程语言。 有关详细信息,请参阅“[将存储库固定到配置文件](/articles/pinning-repositories-to-your-profile)”。 +This section displays up to six public repositories and can include your repositories as well as repositories you've contributed to. To easily see important details about the repositories you've chosen to feature, each repository in this section includes a summary of the work being done, the number of [stars](/articles/saving-repositories-with-stars/) the repository has received, and the main programming language used in the repository. For more information, see "[Pinning repositories to your profile](/articles/pinning-repositories-to-your-profile)." -![固定的仓库](/assets/images/help/profile/profile_pinned_repositories.png) +![Pinned repositories](/assets/images/help/profile/profile_pinned_repositories.png) {% endif %} -## 贡献日历 +## Contributions calendar -您的贡献日历会显示贡献活动。 +Your contributions calendar shows your contribution activity. -### 查看特定时间的贡献 +### Viewing contributions from specific times -- 单击某个日期的方块可显示该 24 小时期间内所做的贡献。 -- 按“Shift”并单击任意日期的方块可显示该时间范围内所做的贡献。 +- Click on a day's square to show the contributions made during that 24-hour period. +- Press *Shift* and click on another day's square to show contributions made during that time span. {% note %} -注意:可以在贡献日历中选择最多一个月的范围。 如果您选择更大的时间范围,我们将仅显示一个月的贡献。 +**Note:** You can select up to a one-month range on your contributions calendar. If you select a larger time span, we will only display one month of contributions. {% endnote %} -![您的贡献图](/assets/images/help/profile/contributions_graph.png) +![Your contributions graph](/assets/images/help/profile/contributions_graph.png) -### 如何计算贡献事件时间 +### How contribution event times are calculated -对于提交和拉取请求,时间戳的计算方式不同: -- “提交”使用提交时间戳中的时区信息。 有关详细信息,请参阅“[排查日程表上的提交问题](/articles/troubleshooting-commits-on-your-timeline)”。 -- {% data variables.product.product_name %} 上打开的“拉取请求”和“议题”使用浏览器的时区 。 通过 API 打开的内容使用 [API 调用中指定的](https://developer.github.com/changes/2014-03-04-timezone-handling-changes)时间戳或时区。 +Timestamps are calculated differently for commits and pull requests: +- **Commits** use the time zone information in the commit timestamp. For more information, see "[Troubleshooting commits on your timeline](/articles/troubleshooting-commits-on-your-timeline)." +- **Pull requests** and **issues** opened on {% data variables.product.product_name %} use your browser's time zone. Those opened via the API use the timestamp or time zone [specified in the API call](https://developer.github.com/changes/2014-03-04-timezone-handling-changes). -## 活动概述 +## Activity overview -{% data reusables.profile.activity-overview-summary %} 有关详细信息,请参阅“[在配置文件中显示活动概览](/articles/showing-an-overview-of-your-activity-on-your-profile)”。 +{% data reusables.profile.activity-overview-summary %} For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)." -![个人资料中的活动概览部分](/assets/images/help/profile/activity-overview-section.png) +![Activity overview section on profile](/assets/images/help/profile/activity-overview-section.png) -活动概览中提供的组织根据您在组织中的活跃程度确定优先级。 如果在配置文件简历中 @mention 某个组织,并且你是组织成员,则该组织首先在活动概览中确定优先级。 有关详细信息,请参阅“[提及人员和团队](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)”或“[将个人简介添加到配置文件](/articles/adding-a-bio-to-your-profile/)”。 +The organizations featured in the activity overview are prioritized according to how active you are in the organization. If you @mention an organization in your profile bio, and you’re an organization member, then that organization is prioritized first in the activity overview. For more information, see "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)" or "[Adding a bio to your profile](/articles/adding-a-bio-to-your-profile/)." -## 贡献活动 +## Contribution activity -贡献活动部分包括工作的详细时间表,包括您进行或合作的提交、您提议的拉取请求以及您打开的议题。 可通过单击贡献活动底部的“Show more activity(显示更多活动)”或通过在查看页面右侧时单击你感兴趣的年份来查看一段时间内你的贡献。 重要时刻(如您加入组织、提议第一个拉取请求或打开一个备受瞩目议题的日期)将在贡献活动中突出显示。 如果您在时间表中无法看到某些事件,请检查以确保您仍具有事件发生位置组织或仓库的访问权限。 +The contribution activity section includes a detailed timeline of your work, including commits you've made or co-authored, pull requests you've proposed, and issues you've opened. You can see your contributions over time by either clicking **Show more activity** at the bottom of your contribution activity or by clicking the year you're interested in viewing on the right side of the page. Important moments, like the date you joined an organization, proposed your first pull request, or opened a high-profile issue, are highlighted in your contribution activity. If you can't see certain events in your timeline, check to make sure you still have access to the organization or repository where the event happened. -![贡献活动时间过滤器](/assets/images/help/profile/contributions_activity_time_filter.png) +![Contribution activity time filter](/assets/images/help/profile/contributions_activity_time_filter.png) -## 在 {% data variables.product.prodname_dotcom_the_website %} 上查看 {% data variables.product.prodname_enterprise %} 中的贡献 +## Viewing contributions from {% data variables.product.prodname_enterprise %} on {% data variables.product.prodname_dotcom_the_website %} -如果使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} 或 {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} 并且你的企业所有者启用 {% data variables.product.prodname_unified_contributions %},可以向 {% data variables.product.prodname_dotcom_the_website %} 配置文件发送企业贡献计数。 有关详细信息,请参阅“[将企业贡献发送到自己的 {% data variables.product.prodname_dotcom_the_website %} 配置文件](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)”。 +If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and your enterprise owner enables {% data variables.enterprise.prodname_unified_contributions %}, you can send enterprise contribution counts from to your {% data variables.product.prodname_dotcom_the_website %} profile. For more information, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)." diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md index 4f46830bef..3e24053ec8 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md @@ -1,6 +1,6 @@ --- -title: 为什么我的贡献没有在我的个人资料中显示? -intro: 了解贡献图表中可能缺少贡献的常见原因。 +title: Why are my contributions not showing up on my profile? +intro: Learn common reasons that contributions may be missing from your contributions graph. redirect_from: - /articles/why-are-my-contributions-not-showing-up-on-my-profile - /github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile @@ -14,54 +14,49 @@ versions: topics: - Profiles shortTitle: Missing contributions -ms.openlocfilehash: c1f4c9481a5e3ac9328b353ced826c982e1160e7 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147079520' --- -## 关于您的贡献图 -您的个人资料贡献图是您参与{% data variables.product.product_location %}{% ifversion ghae %}拥有{% else %}上{% endif %} 的存储库的记录。 贡献按照协调世界时 (UTC) 而不是您当地的时区加时间戳。 只有在满足特定标准时才会计算贡献。 在某些情况下,我们可能需要重建您的图表才能显示贡献。 +## About your contribution graph -如果您是使用 SAML 单点登录 (SSO) 的组织的成员,则在没有活动的 SSO 会话时,您将无法在配置文件上看到来自该组织的贡献活动。 从组织外部查看您个人资料的用户将看到您组织的贡献活动的匿名贡献活动。 +Your profile contributions graph is a record of contributions you've made to repositories {% ifversion ghae %}owned by{% else %}on{% endif %} {% data variables.location.product_location %}. Contributions are timestamped according to Coordinated Universal Time (UTC) rather than your local time zone. Contributions are only counted if they meet certain criteria. In some cases, we may need to rebuild your graph in order for contributions to appear. -## 计算的贡献 +If you are part of an organization that uses SAML single sign-on (SSO), you won’t be able to see contribution activity from the organization on your profile if you do not have an active SSO session. People viewing your profile from outside your organization will see anonymized contribution activity of your contribution activity for your organization. -### 议题、拉取请求和讨论 +## Contributions that are counted -如果议题、拉取请求和讨论在独立的仓库而不是复刻中打开,它们将在您的贡献图中显示。 +### Issues, pull requests and discussions -### 提交 -如果提交符合以下所有条件,则会在贡献图中显示: -- 用于提交的电子邮件地址与您在 {% data variables.product.product_location %} 上的帐户关联。 -- 提交在独立的仓库而不是复刻中进行。 -- 提交在以下位置进行: - - 在仓库的默认分支中 - - 在 `gh-pages` 分支(对于具有项目网站的存储库)中 +Issues, pull requests and discussions will appear on your contribution graph if they were opened in a standalone repository, not a fork. -有关项目网站的详细信息,请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)”。 +### Commits +Commits will appear on your contributions graph if they meet **all** of the following conditions: +- The email address used for the commits is associated with your account on {% data variables.location.product_location %}. +- The commits were made in a standalone repository, not a fork. +- The commits were made: + - In the repository's default branch + - In the `gh-pages` branch (for repositories with project sites) -此外,以下至少一项必须为 true: -- 您是仓库中的协作者,或者是拥有该仓库的组织的成员。 -- 您已复刻该仓库。 -- 您已打开仓库中的拉取请求或议题。 -- 您已为仓库加星标。 +For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." -## 贡献未计算的常见原因 +In addition, **at least one** of the following must be true: +- You are a collaborator on the repository or are a member of the organization that owns the repository. +- You have forked the repository. +- You have opened a pull request or issue in the repository. +- You have starred the repository. + +## Common reasons that contributions are not counted {% data reusables.pull_requests.pull_request_merges_and_contributions %} -### 24 小时内进行的提交 +### Commit was made less than 24 hours ago -进行满足计为贡献要求的提交后,您可能需要等待最长 24 小时才能看到在贡献图中显示的贡献。 +After making a commit that meets the requirements to count as a contribution, you may need to wait for up to 24 hours to see the contribution appear on your contributions graph. -### 您的本地 Git 提交电子邮件地址未连接到您的帐户 +### Your local Git commit email isn't connected to your account -提交必须使用与你在 {% data variables.product.product_location %}{% ifversion fpt or ghec %} 上的帐户连接的电子邮件地址进行,或者使用在电子邮件设置中提供给你的 {% data variables.product.prodname_dotcom %} 提供的 `noreply` 电子邮件地址进行,{% endif %}才能显示在你的贡献图上。{% ifversion fpt or ghec %} 有关 `noreply` 电子邮件地址的详细信息,请参阅“[设置提交电子邮件地址](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#about-commit-email-addresses)”。{% endif %} +Commits must be made with an email address that is connected to your account on {% data variables.location.product_location %}{% ifversion fpt or ghec %}, or the {% data variables.product.prodname_dotcom %}-provided `noreply` email address provided to you in your email settings,{% endif %} in order to appear on your contributions graph.{% ifversion fpt or ghec %} For more information about `noreply` email addresses, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#about-commit-email-addresses)."{% endif %} -可以通过将 `.patch` 添加到提交 URL 的末尾(例如 https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch)来检查用于提交的电子邮件地址: +You can check the email address used for a commit by adding `.patch` to the end of a commit URL, e.g. https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch: ``` From 67c0afc1da354d8571f51b6f0af8f2794117fd10 Mon Sep 17 00:00:00 2001 @@ -70,37 +65,37 @@ Date: Sun, 27 Apr 2014 15:36:39 +0530 Subject: [PATCH] updated index for better welcome message ``` -`From:` 字段中的电子邮件地址是在[本地 git 配置设置](/articles/set-up-git)中设置的地址。 在此示例中,用于提交的电子邮件地址为 `octocat@nowhere.com`。 +The email address in the `From:` field is the address that was set in the [local git config settings](/articles/set-up-git). In this example, the email address used for the commit is `octocat@nowhere.com`. -如果用于提交的电子邮件地址未连接到您的 {% data variables.product.product_location %} 帐户,{% ifversion ghae %}请更改用于在 Git 中创作提交的电子邮件地址。 有关详细信息,请参阅“[设置提交电子邮件地址](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)”。{% else %}必须[将电子邮件地址添加](/articles/adding-an-email-address-to-your-github-account)到 {% data variables.product.product_location %} 上的帐户。 您的贡献图将在添加新地址后自动重建。{% endif %} +If the email address used for the commit is not connected to your account on {% data variables.location.product_location %}, {% ifversion ghae %}change the email address used to author commits in Git. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %}you must [add the email address](/articles/adding-an-email-address-to-your-github-account) to your account on {% data variables.location.product_location %}. Your contributions graph will be rebuilt automatically when you add the new address.{% endif %} {% warning %} -警告:通用电子邮件地址(如 `jane@computer.local`)无法添加到 {% data variables.product.prodname_dotcom %} 帐户。 如果为您的提交使用这类电子邮件,则提交不会链接到您的 {% data variables.product.prodname_dotcom %} 个人资料,并且不会在您的贡献图中显示。 +**Warning**: Generic email addresses, such as `jane@computer.local`, cannot be added to {% data variables.product.prodname_dotcom %} accounts. If you use such an email for your commits, the commits will not be linked to your {% data variables.product.prodname_dotcom %} profile and will not show up in your contribution graph. {% endwarning %} -### 未在默认分支或 `gh-pages` 分支中执行提交 +### Commit was not made in the default or `gh-pages` branch -仅发生在默认分支或 `gh-pages` 分支(对于包含项目网站的存储库)中的提交才会计入。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)”。 +Commits are only counted if they are made in the default branch or the `gh-pages` branch (for repositories with project sites). For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." -如果提交位于非默认或非 `gh-pages` 分支中,并且你希望将其计入你的贡献,则需要执行以下操作之一: -- [打开拉取请求](/articles/creating-a-pull-request),将更改合并到默认分支或 `gh-pages` 分支中。 -- [更改存储库的默认分支](/github/administering-a-repository/changing-the-default-branch)。 +If your commits are in a non-default or non-`gh-pages` branch and you'd like them to count toward your contributions, you will need to do one of the following: +- [Open a pull request](/articles/creating-a-pull-request) to have your changes merged into the default branch or the `gh-pages` branch. +- [Change the default branch](/github/administering-a-repository/changing-the-default-branch) of the repository. {% warning %} -警告:更改存储库的默认分支将会更改所有存储库协作者的默认分支。 仅当您希望新分支成为进行所有未来拉取请求和提交的基础时才执行此操作。 +**Warning**: Changing the default branch of the repository will change it for all repository collaborators. Only do this if you want the new branch to become the base against which all future pull requests and commits will be made. {% endwarning %} -### 提交在复刻中进行 +### Commit was made in a fork -在复刻中进行的提交不会计入您的贡献。 要将其计入,您必须执行以下操作之一: -- [打开拉取请求](/articles/creating-a-pull-request),将更改合并到父存储库中。 -- 要分离复刻并将其变为 {% data variables.product.product_location %} 上独立的仓库,请联系 {% data variables.contact.contact_support %}。 如果该复刻有自己的复刻,让 {% data variables.contact.contact_support %} 了解这些复刻是随您的仓库移入新网络还是留在当前网络中。 有关详细信息,请参阅“[关于分支](/articles/about-forks/)”。 +Commits made in a fork will not count toward your contributions. To make them count, you must do one of the following: +- [Open a pull request](/articles/creating-a-pull-request) to have your changes merged into the parent repository. +- To detach the fork and turn it into a standalone repository on {% data variables.location.product_location %}, contact {% data variables.contact.contact_support %}. If the fork has forks of its own, let {% data variables.contact.contact_support %} know if the forks should move with your repository into a new network or remain in the current network. For more information, see "[About forks](/articles/about-forks/)." -## 延伸阅读 +## Further reading -- [在个人资料中公开或隐藏你的私人贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile) -- [在个人资料页中查看贡献](/articles/viewing-contributions-on-your-profile-page) +- "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" +- "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)" diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md index 6c35133ec7..63b2860091 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md @@ -1,6 +1,6 @@ --- title: Setting up and managing your personal account on GitHub -intro: You can manage settings for your personal account on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}, including email preferences, access to personal repositories, and organization memberships. You can also manage the account itself. +intro: You can manage settings for your personal account on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}, including email preferences, access to personal repositories, and organization memberships. You can also manage the account itself. shortTitle: Personal accounts redirect_from: - /categories/setting-up-and-managing-your-github-user-account diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md index 8a8d6ef9a6..cd599dfdc0 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md @@ -25,7 +25,7 @@ Repositories owned by an organization can grant more granular access. For more i {% ifversion fpt or ghec %} -If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you can only invite other members of your enterprise to collaborate with you. {% data reusables.enterprise-accounts.emu-more-info-account %} +If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you can only invite other members of your enterprise to collaborate with you. {% data reusables.enterprise-accounts.emu-more-info-account %} {% note %} diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md index ceb6a337d5..0d8d4fd6b1 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md @@ -1,6 +1,6 @@ --- -title: 添加电子邮件地址到 GitHub 帐户 -intro: '{% data variables.product.product_name %} 允许您根据需要为帐户添加多个电子邮件地址。 如果在本地 Git 配置中设置电子邮件地址,您需要将其添加到帐户设置,以将提交连接到帐户。 有关电子邮件地址和提交的详细信息,请参阅“[设置提交电子邮件地址](/articles/setting-your-commit-email-address/)”。' +title: Adding an email address to your GitHub account +intro: '{% data variables.product.product_name %} allows you to add as many email addresses to your account as you like. If you set an email address in your local Git configuration, you will need to add it to your account settings in order to connect your commits to your account. For more information about your email address and commits, see "[Setting your commit email address](/articles/setting-your-commit-email-address/)."' redirect_from: - /articles/adding-an-email-address-to-your-github-account - /github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account @@ -14,27 +14,24 @@ topics: - Accounts - Notifications shortTitle: Add an email address -ms.openlocfilehash: 082326d96da4b36d1f29830491223ce9b649a15d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145164618' --- {% ifversion fpt or ghec %} {% note %} -**注释**: +**Notes**: - {% data reusables.user-settings.no-verification-disposable-emails %} - - 如果您是 {% data variables.product.prodname_emu_enterprise %} 的成员,则无法在 {% data variables.product.prodname_dotcom_the_website %} 上更改您的电子邮件地址。 {% data reusables.enterprise-accounts.emu-more-info-account %} + - If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you cannot make changes to your email address on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} {% endnote %} {% endif %} -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.emails %} {% data reusables.user-settings.add_and_verify_email %} {% data reusables.user-settings.select_primary_email %} +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.emails %} +{% data reusables.user-settings.add_and_verify_email %} +{% data reusables.user-settings.select_primary_email %} -## 延伸阅读 +## Further reading -- [管理电子邮件首选项](/articles/managing-email-preferences/) +- "[Managing email preferences](/articles/managing-email-preferences/)" diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md index 8b5f8be27f..a45d2f7f77 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md @@ -1,6 +1,6 @@ --- -title: 管理电子邮件首选项 -intro: '您可以在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}上添加或更改与您的帐户关联的电子邮件地址。 您也可以管理从 {% data variables.product.product_name %} 收到的电子邮件。' +title: Managing email preferences +intro: 'You can add or change the email addresses associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. You can also manage emails you receive from {% data variables.product.product_name %}.' redirect_from: - /categories/managing-email-preferences - /articles/managing-email-preferences @@ -24,11 +24,5 @@ children: - /types-of-emails-github-sends - /managing-marketing-emails-from-github shortTitle: Manage email preferences -ms.openlocfilehash: 8295d9884f7b2a9bfdef329f693c6492db636a61 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145164719' --- diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md index d8c266b968..d8d8d78c24 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md @@ -1,6 +1,6 @@ --- -title: 记住您的 GitHub 用户名或电子邮件 -intro: '是否距离您第一次登录 {% data variables.product.product_location %} 已经有一段时间? 如果是这样,欢迎回来! 如果无法记住 {% data variables.product.product_name %} 上个人帐户的用户名,可以尝试使用以下方法来记住它。' +title: Remembering your GitHub username or email +intro: 'Are you signing in to {% data variables.location.product_location %} for the first time in a while? If so, welcome back! If you can''t remember the username for your personal account on {% data variables.product.product_name %}, you can try these methods for remembering it.' redirect_from: - /articles/oh-noes-i-ve-forgotten-my-username-email - /articles/oh-noes-i-ve-forgotten-my-username-or-email @@ -16,66 +16,61 @@ topics: - Accounts - Notifications shortTitle: Find your username or email -ms.openlocfilehash: e65ba973a5ca7865aa642ce5d64f8efa0a996742 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145164771' --- {% mac %} -## {% data variables.product.prodname_desktop %} 用户 +## {% data variables.product.prodname_desktop %} users -1. 在“GitHub 桌面”菜单中,单击“首选项” 。 -2. 在 Preferences(首选项)窗口中,验证以下内容: - - 若要查看 {% data variables.product.product_name %} 用户名,请单击“帐户”。 - - 若要查看 Git 电子邮件,请单击“Git”。 请注意,此电子邮件不保证是 [主要 {% data variables.product.product_name %} 电子邮件](/articles/changing-your-primary-email-address)。 +1. In the **GitHub Desktop** menu, click **Preferences**. +2. In the Preferences window, verify the following: + - To view your {% data variables.product.product_name %} username, click **Accounts**. + - To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address). {% endmac %} {% windows %} -## {% data variables.product.prodname_desktop %} 用户 +## {% data variables.product.prodname_desktop %} users -1. 在“文件”菜单中,单击“选项” 。 -2. 在 Options(选项)窗口中,验证以下内容: - - 若要查看 {% data variables.product.product_name %} 用户名,请单击“帐户”。 - - 若要查看 Git 电子邮件,请单击“Git”。 请注意,此电子邮件不保证是 [主要 {% data variables.product.product_name %} 电子邮件](/articles/changing-your-primary-email-address)。 +1. In the **File** menu, click **Options**. +2. In the Options window, verify the following: + - To view your {% data variables.product.product_name %} username, click **Accounts**. + - To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address). {% endwindows %} -## 在 `user.name` 配置中查找用户名 +## Finding your username in your `user.name` configuration -在设置期间,你可能已[在 Git 中设置用户名](/github/getting-started-with-github/setting-your-username-in-git)。 如果这样,您可以查看此配置设置的值: +During set up, you may have [set your username in Git](/github/getting-started-with-github/setting-your-username-in-git). If so, you can review the value of this configuration setting: ```shell $ git config user.name # View the setting -YOUR_USERNAME +YOUR_USERNAME ``` -## 在远程仓库的 URL 中查找您的用户名 +## Finding your username in the URL of remote repositories -如果您有已创建或已复刻的个人仓库的任何本地副本,则可以检查远程仓库的 URL。 +If you have any local copies of personal repositories you have created or forked, you can check the URL of the remote repository. {% tip %} -提示:此方法仅当你拥有原始存储库或其他人存储库中你自己的分叉时才有效。 如果您克隆其他人的仓库,将显示他们的用户名而不是您的用户名。 类似地,组织仓库将显示组织的名称,而不是远程 URL 中的特定用户。 +**Tip**: This method only works if you have an original repository or your own fork of someone else's repository. If you clone someone else's repository, their username will show instead of yours. Similarly, organization repositories will show the name of the organization instead of a particular user in the remote URL. {% endtip %} ```shell -$ cd YOUR_REPOSITORY +$ cd YOUR_REPOSITORY # Change directories to the initialized Git repository $ git remote -v -origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (fetch) -origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (push) +origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (fetch) +origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (push) ``` -用户名紧跟在 `https://{% data variables.command_line.backticks %}/` 后。 +Your user name is what immediately follows the `https://{% data variables.command_line.backticks %}/`. {% ifversion fpt or ghec %} -## 延伸阅读 +## Further reading -- “[验证电子邮件地址](/articles/verifying-your-email-address)”{% endif %} +- "[Verifying your email address](/articles/verifying-your-email-address)" +{% endif %} diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md index 14a934c114..660ceca3bd 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md @@ -1,6 +1,6 @@ --- -title: 设置提交电子邮件地址 -intro: '你可以设置用于在 {% data variables.product.product_location %} 和计算机上创作提交的电子邮件地址。' +title: Setting your commit email address +intro: 'You can set the email address that is used to author commits on {% data variables.location.product_location %} and on your computer.' redirect_from: - /articles/keeping-your-email-address-private - /articles/setting-your-commit-email-address-on-github @@ -22,63 +22,61 @@ topics: - Accounts - Notifications shortTitle: Set commit email address -ms.openlocfilehash: 76b0af2a1afa776281434c36cf33fa0e082c2c56 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '146338947' --- -## 关于提交电子邮件地址 +## About commit email addresses -{% data variables.product.prodname_dotcom %} 使用您的提交电子邮件地址将提交与您的 {% data variables.product.product_location %} 关联。 您可以选择要与从命令行以及基于 web 的 Git 操作推送的提交相关联的电子邮件地址。 +{% data variables.product.prodname_dotcom %} uses your commit email address to associate commits with your account on {% data variables.location.product_location %}. You can choose the email address that will be associated with the commits you push from the command line as well as web-based Git operations you make. -对于基于 Web 的 Git 操作,您可以在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上设置提交电子邮件地址。 对于从命令行推送的提交,您可以在 Git 中设置提交电子邮件地址。 +For web-based Git operations, you can set your commit email address on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For commits you push from the command line, you can set your commit email address in Git. -{% ifversion fpt or ghec %} 在更改提交电子邮件地址之前进行的提交仍与之前的电子邮件地址关联。{% else %} 在 {% data variables.product.product_name %} 上更改提交电子邮件地址后,新电子邮件地址默认在所有未来基于 Web 的 Git 操作中可见。 在更改提交电子邮件地址之前进行的任何提交仍与之前的电子邮件地址关联。{% endif %} +{% ifversion fpt or ghec %}Any commits you made prior to changing your commit email address are still associated with your previous email address.{% else %}After changing your commit email address on {% data variables.product.product_name %}, the new email address will be visible in all of your future web-based Git operations by default. Any commits you made prior to changing your commit email address are still associated with your previous email address.{% endif %} {% ifversion fpt or ghec %} {% note %} -注意:{% data reusables.user-settings.no-verification-disposable-emails %} +**Note**: {% data reusables.user-settings.no-verification-disposable-emails %} {% endnote %} {% endif %} -{% ifversion fpt or ghec %} 如果想将个人电子邮件地址设为私密,则可以使用 {% data variables.product.product_name %} 的 `noreply` 电子邮件地址作为提交电子邮件地址。 要将 `noreply` 电子邮件地址用于从命令行推送的提交,请在 Git 中设置提交电子邮件地址时使用该电子邮件地址。 要将 `noreply` 地址用于基于 Web 的 Git 操作,请在 GitHub 上设置提交电子邮件地址并选择“对我的电子邮件地址保密”。 +{% ifversion fpt or ghec %}If you'd like to keep your personal email address private, you can use a `noreply` email address from {% data variables.product.product_name %} as your commit email address. To use your `noreply` email address for commits you push from the command line, use that email address when you set your commit email address in Git. To use your `noreply` address for web-based Git operations, set your commit email address on GitHub and choose to **Keep my email address private**. -您也可以选择阻止从命令行推送的提交显示您的个人电子邮件地址。 有关详细信息,请参阅“[阻止会暴露个人电子邮件的命令行推送](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)。”{% endif %} +You can also choose to block commits you push from the command line that expose your personal email address. For more information, see "[Blocking command line pushes that expose your personal email](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)."{% endif %} -为确保提交归因于你并且出现在你的贡献图中,请使用已连接到你在 {% data variables.product.product_location %} 上的帐户的电子邮件地址{% ifversion fpt or ghec %},或者在电子邮件设置中提供给你的 `noreply` 电子邮件地址{% endif %}。 {% ifversion not ghae %} 有关详细信息,请参阅“[将电子邮件地址添加到 {% data variables.product.prodname_dotcom %} 帐户](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)”。{% endif %} +To ensure that commits are attributed to you and appear in your contributions graph, use an email address that is connected to your account on {% data variables.location.product_location %}{% ifversion fpt or ghec %}, or the `noreply` email address provided to you in your email settings{% endif %}. {% ifversion not ghae %}For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)."{% endif %} {% ifversion fpt or ghec %} {% note %} -注意:如果于 2017 年 7 月 18 日之后在 {% data variables.product.product_location %} 上创建了帐户,则用于 {% data variables.product.product_name %} 的 `noreply` 电子邮件地址是一个七位数的 ID 号以及格式为 ID+username@users.noreply.github.com 的用户名。 如果于 2017 年 7 月 18 日之前在 {% data variables.product.product_location %} 上创建了帐户,则来自 {% data variables.product.product_name %} 的 `noreply` 电子邮件地址是 username@users.noreply.github.com。 可以通过在电子邮件设置中选择(或取消选择并重新选择)“对我的电子邮件地址保密”,为 {% data variables.product.product_name %} 获取基于 ID 的 `noreply` 电子邮件地址。 +**Note:** If you created your account on {% data variables.location.product_location %} _after_ July 18, 2017, your `noreply` email address for {% data variables.product.product_name %} is a seven-digit ID number and your username in the form of ID+USERNAME@users.noreply.github.com. If you created your account on {% data variables.location.product_location %} _prior to_ July 18, 2017, your `noreply` email address from {% data variables.product.product_name %} is USERNAME@users.noreply.github.com. You can get an ID-based `noreply` email address for {% data variables.product.product_name %} by selecting (or deselecting and reselecting) **Keep my email address private** in your email settings. {% endnote %} -如果使用 {% data variables.product.product_name %} 的 `noreply` 电子邮件地址进行提交,然后[更改用户名](/articles/changing-your-github-username),则这些提交将不会与你在 {% data variables.product.product_location %} 上的帐户相关联。 如果使用的是基于 ID 的 {% data variables.product.product_name %} `noreply` 地址,则不适用。 有关详细信息,请参阅“[更改 {% data variables.product.prodname_dotcom %} 用户名](/articles/changing-your-github-username)。”{% endif %} +If you use your `noreply` email address for {% data variables.product.product_name %} to make commits and then [change your username](/articles/changing-your-github-username), those commits will not be associated with your account on {% data variables.location.product_location %}. This does not apply if you're using the ID-based `noreply` address from {% data variables.product.product_name %}. For more information, see "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username)."{% endif %} -## 在 {% data variables.product.prodname_dotcom %} 上设置提交电子邮件地址 +## Setting your commit email address on {% data variables.product.prodname_dotcom %} {% data reusables.files.commit-author-email-options %} -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.emails %} {% data reusables.user-settings.add_and_verify_email %} {% data reusables.user-settings.select_primary_email %}{% ifversion fpt or ghec %} {% data reusables.user-settings.keeping_your_email_address_private %}{% endif %} +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.emails %} +{% data reusables.user-settings.add_and_verify_email %} +{% data reusables.user-settings.select_primary_email %}{% ifversion fpt or ghec %} +{% data reusables.user-settings.keeping_your_email_address_private %}{% endif %} -## 在 Git 中设置您的提交电子邮件地址 +## Setting your commit email address in Git -可以使用 `git config` 命令更改与 Git 提交关联的电子邮件地址。 设置的新电子邮件地址将在从命令行推送到 {% data variables.product.product_location %} 的任何未来提交中显示。 在您更改提交电子邮件地址之前进行的任何提交仍与之前的电子邮件地址关联。 +You can use the `git config` command to change the email address you associate with your Git commits. The new email address you set will be visible in any future commits you push to {% data variables.location.product_location %} from the command line. Any commits you made prior to changing your commit email address are still associated with your previous email address. -### 为计算机上的每个仓库设置电子邮件地址 +### Setting your email address for every repository on your computer {% data reusables.command_line.open_the_multi_os_terminal %} 2. {% data reusables.user-settings.set_your_email_address_in_git %} ```shell - $ git config --global user.email "email@example.com" + $ git config --global user.email "YOUR_EMAIL" ``` 3. {% data reusables.user-settings.confirm_git_email_address_correct %} ```shell @@ -87,17 +85,17 @@ ms.locfileid: '146338947' ``` 4. {% data reusables.user-settings.link_email_with_your_account %} -### 为一个仓库设置电子邮件地址 +### Setting your email address for a single repository -{% data variables.product.product_name %} 使用在您的本地 Git 配置中设置的电子邮件地址将从命令行推送的提交与您在 {% data variables.product.product_location %} 上的帐户相关联。 +{% data variables.product.product_name %} uses the email address set in your local Git configuration to associate commits pushed from the command line with your account on {% data variables.location.product_location %}. -您可以更改与您在一个仓库中所进行的提交关联的电子邮件地址。 此操作将覆盖这一个仓库中的全局 Git 配置设置,但不会影响任何其他仓库。 +You can change the email address associated with commits you make in a single repository. This will override your global Git configuration settings in this one repository, but will not affect any other repositories. {% data reusables.command_line.open_the_multi_os_terminal %} -2. 将当前工作目录更改为您想要在其中配置与 Git 提交关联的电子邮件地址的本地仓库。 +2. Change the current working directory to the local repository where you want to configure the email address that you associate with your Git commits. 3. {% data reusables.user-settings.set_your_email_address_in_git %} ```shell - $ git config user.email "email@example.com" + $ git config user.email "YOUR_EMAIL" ``` 4. {% data reusables.user-settings.confirm_git_email_address_correct %} ```shell diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md index 5cb7038add..aad324c45b 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md @@ -1,6 +1,6 @@ --- title: Changing your GitHub username -intro: 'You can change the username for your account on {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %} if your instance uses built-in authentication{% endif %}.' +intro: 'You can change the username for your account on {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.location.product_location %} if your instance uses built-in authentication{% endif %}.' redirect_from: - /articles/how-to-change-your-username - /articles/changing-your-github-user-name @@ -25,11 +25,11 @@ shortTitle: Change your username {% ifversion ghec %} -**Note**: Members of an {% data variables.product.prodname_emu_enterprise %} cannot change usernames. Your enterprise's IdP administrator controls your username for {% data variables.product.product_name %}. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." +**Note**: Members of an {% data variables.enterprise.prodname_emu_enterprise %} cannot change usernames. Your enterprise's IdP administrator controls your username for {% data variables.product.product_name %}. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." {% elsif ghes %} -**Note**: If you sign into {% data variables.product.product_location %} with LDAP credentials or single sign-on (SSO), only your local administrator can change your username. For more information about authentication methods for {% data variables.product.product_name %}, see "[Authenticating users for {% data variables.product.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)." +**Note**: If you sign into {% data variables.location.product_location %} with LDAP credentials or single sign-on (SSO), only your local administrator can change your username. For more information about authentication methods for {% data variables.product.product_name %}, see "[Authenticating users for {% data variables.location.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)." {% endif %} @@ -53,7 +53,7 @@ After changing your username, your old username becomes available for anyone els {% ifversion fpt or ghec %} -If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot make changes to your username. {% data reusables.enterprise-accounts.emu-more-info-account %} +If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you cannot make changes to your username. {% data reusables.enterprise-accounts.emu-more-info-account %} {% endif %} @@ -67,7 +67,7 @@ If the new owner of your old username creates a repository with the same name as ## Links to your previous profile page -After changing your username, links to your previous profile page, such as `https://{% data variables.command_line.backticks %}/previoususername`, will return a 404 error. We recommend updating any links to your account on {% data variables.product.product_location %} from elsewhere{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profile{% endif %}. +After changing your username, links to your previous profile page, such as `https://{% data variables.command_line.backticks %}/previoususername`, will return a 404 error. We recommend updating any links to your account on {% data variables.location.product_location %} from elsewhere{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profile{% endif %}. ## Your Git commits diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md index aeece9f612..20771e8187 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md @@ -1,54 +1,51 @@ --- -title: 管理辅助功能设置 +title: Managing accessibility settings shortTitle: Manage accessibility settings -intro: '{% data variables.product.product_name %} 的用户界面可以适应视觉、听觉、运动、认知或学习需求。' +intro: "{% data variables.product.product_name %}'s user interface can adapt to your vision, hearing, motor, cognitive, or learning needs." versions: feature: keyboard-shortcut-accessibility-setting redirect_from: - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings type: how_to miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: d4811368ab825f0b24864283f8be54672f72a787 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147614317' --- -## 关于辅助功能设置 -若要在 {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} 上创建满足需求的体验,可以自定义用户界面。 辅助功能设置对残障人士至关重要,但对任何人都很有用。 例如,键盘快捷方式的自定义对使用语音控制导航的人而言必不可少,但如果 {% data variables.product.product_name %} 的键盘快捷方式与另一个应用程序快捷方式发生冲突,则自定义对任何人都很有用。 +## About accessibility settings -## 管理辅助功能设置 +To create an experience on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} that fits your needs, you can customize the user interface. Accessibility settings can be essential for people with disabilities, but can be useful to anyone. For example, customization of keyboard shortcuts is essential to people who navigate using voice control, but can be useful to anyone when a keyboard shortcut for {% data variables.product.product_name %} clashes with another application shortcut. -可以决定是否要在 {% ifversion fpt or ghec %}{% data variables.product.product_location %}{% elsif ghes or ghae %} 网站上使用 {% data variables.product.product_location %}{% endif %} 的部分或全部键盘快捷方式,并且可以控制动画图像的显示。 +## Managing accessibility settings -### 管理键盘快捷方式 +You can decide whether you want to use some or all keyboard shortcuts on {% ifversion fpt or ghec %}{% data variables.location.product_location %}{% elsif ghes or ghae %}the website for {% data variables.location.product_location %}{% endif %}, and you can control the display of animated images. -可以单纯使用键盘在 {% data variables.product.product_name %} 网站上执行操作。 键盘快捷方式可用于节省时间,但可能意外激活或干扰辅助技术。 +### Managing keyboard shortcuts -默认情况下,在 {% data variables.product.product_name %} 上启用所有键盘快捷方式。 有关详细信息,请参阅“[键盘快捷方式](/get-started/using-github/keyboard-shortcuts)”。 +You can perform actions across the {% data variables.product.product_name %} website by using your keyboard alone. Keyboard shortcuts can be useful to save time, but can be activated accidentally or interfere with assistive technology. -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.accessibility_settings %} -1. 在“键盘快捷方式”下,管理键盘快捷方式的设置。 +By default, all keyboard shortcuts are enabled on {% data variables.product.product_name %}. For more information, see "[Keyboard shortcuts](/get-started/using-github/keyboard-shortcuts)." - - 若要禁用不使用修改键(如 ControlCommand)的快捷键,请在“常规”下取消选择“字符键”。 - - 如果禁用字符键,仍可触发 Web 浏览器的快捷方式,并且仍可触发使用修该键的 {% data variables.product.product_name %} 的快捷方式。 +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.accessibility_settings %} +1. Under "Keyboard shortcuts", manage settings for your keyboard shortcuts. + + - To disable shortcut keys that don't use modifiers keys like Control or Command, under "General", deselect **Character keys**. + - If you disable character keys, you may still be able to trigger shortcuts for your web browser, and you can still trigger shortcuts for {% data variables.product.product_name %} that use a modifier key. {%- ifversion command-palette %} - - 若要自定义用于触发命令面板的键盘快捷方式,在“命令面板”下,请使用下拉菜单选择键盘快捷方式。 有关详细信息,请参阅“[{% data variables.product.company_short %} 命令面板](/get-started/using-github/github-command-palette)”。 + - To customize the keyboard shortcuts for triggering the command palette, under "Command palette", use the drop-down menus to choose a keyboard shortcut. For more information, see "[{% data variables.product.company_short %} Command Palette](/get-started/using-github/github-command-palette)." {%- endif %} {% ifversion motion-management %} -### 管理运动 +### Managing motion -可以控制 {% data variables.product.product_name %} 显示动画 .gif 图像的方式。 +You can control how {% data variables.product.product_name %} displays animated _.gif_ images. -默认情况下,{% data variables.product.product_name %} 与系统级偏好同步,以减少运动。 有关详细信息,请参阅操作系统的文档或设置。 +By default, {% data variables.product.product_name %} syncs with your system-level preference for reduced motion. For more information, see the documentation or settings for your operating system. -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.accessibility_settings %} -1. 在“运动”下,管理运动设置。 +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.accessibility_settings %} +1. Under "Motion", manage settings for motion. - - 若要控制 {% data variables.product.product_name %} 显示动画图像的方式,请在“自动播放动画图像”下选择“与系统同步”、“已启用”或“已禁用” 。 + - To control how {% data variables.product.product_name %} displays animated images, under "Autoplay animated images", select **Sync with system**, **Enabled**, or **Disabled**. {% endif %} diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md index ec8bc5e53e..25c69e1a94 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md @@ -1,6 +1,6 @@ --- -title: 管理仓库的默认分支名称 -intro: '您可以为在 {% data variables.product.product_location %} 上创建的新资料库设置默认分支名称。' +title: Managing the default branch name for your repositories +intro: 'You can set the default branch name for new repositories that you create on {% data variables.location.product_location %}.' versions: fpt: '*' ghes: '*' @@ -13,29 +13,24 @@ redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories shortTitle: Manage default branch name -ms.openlocfilehash: a3943f32860f55becaa840f7ca40c13ba87b5ce2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145193760' --- -## About the default branch name +## About management of the default branch name -当您在 {% data variables.product.product_location %} 上创建一个新仓库时,仓库将包含一个分支,它就是默认分支。 您可以更改 {% data variables.product.product_name %} 用于您新建仓库中默认分支的名称。 有关默认分支的详细信息,请参阅“[关于分支](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)”。 +When you create a new repository on {% data variables.location.product_location %}, the repository contains one branch, which is the default branch. You can change the name that {% data variables.product.product_name %} uses for the default branch in new repositories you create. For more information about the default branch, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)." {% data reusables.branches.change-default-branch %} -## 设置默认分支名称 +## Setting the default branch name -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.repo-tab %} -3. 在“存储库默认分支”下,单击“立即更改默认分支名称”。 - ![“替代”按钮](/assets/images/help/settings/repo-default-name-button.png) -4. 键入要用于新分支的默认名称。 - ![用于输入默认名称的文本框](/assets/images/help/settings/repo-default-name-text.png) -5. 单击“更新”。 - ![“更新”按钮](/assets/images/help/settings/repo-default-name-update.png) +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.repo-tab %} +3. Under "Repository default branch", click **Change default branch name now**. + ![Override button](/assets/images/help/settings/repo-default-name-button.png) +4. Type the default name that you would like to use for new branches. + ![Text box for entering default name](/assets/images/help/settings/repo-default-name-text.png) +5. Click **Update**. + ![Update button](/assets/images/help/settings/repo-default-name-update.png) -## 延伸阅读 +## Further reading -- “[管理组织中存储库的默认分支名称](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)” +- "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)" diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md index 25ab4d853d..aedaff2bc8 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md @@ -1,6 +1,6 @@ --- -title: 关于离开公司的最佳实践 -intro: '如果你的 {% data variables.product.product_name %} 帐户同时用于个人和工作用途,那么你在离开公司或组织的时候需要注意一些问题。' +title: Best practices for leaving your company +intro: 'If you use your account on {% data variables.product.product_name %} for both personal and work purposes, there are a few things to keep in mind when you leave your company or organization.' redirect_from: - /articles/best-practices-for-leaving-your-company - /github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company @@ -13,36 +13,31 @@ versions: topics: - Accounts shortTitle: Leaving your company -ms.openlocfilehash: c288584891981eab7ffe4204e2028b0e70cf1d08 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147687113' --- -在离开公司之前,请确保在个人帐户中更新以下信息: -- 通过[在电子邮件设置中删除公司电子邮件地址](/articles/changing-your-primary-email-address)来取消其验证。 然后,您可以在不验证的情况下重新添加它,以保留与您的帐户相关联的所有相关提交。 -- [将你的主电子邮件地址](/articles/changing-your-primary-email-address)从公司电子邮件地址更改为个人电子邮件地址。 -- [验证新的主电子邮件地址](/articles/verifying-your-email-address)。 -- [更改你的 GitHub 用户名](/articles/changing-your-github-username)以删除对公司或组织的任何引用(如有必要)。 -- 如果为个人帐户启用了双重 (2FA) 身份验证,请确保由自己(而不是你的公司)控制你已配置的 2FA 身份验证方法。 有关详细信息,请参阅“[配置双因素身份验证](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)”。 +Before you leave your company, make sure you update the following information in your personal account: -## 离开组织 +- Unverify your company email address by [deleting it in your Email settings](/articles/changing-your-primary-email-address). You can then re-add it without verifying to keep any associated commits linked to your account. +- [Change your primary email address](/articles/changing-your-primary-email-address) from your company email to your personal email. +- [Verify your new primary email address](/articles/verifying-your-email-address). +- [Change your GitHub username](/articles/changing-your-github-username) to remove any references to your company or organization, if necessary. +- If you've enabled two-factor (2FA) authentication for your personal account, make sure that you (not your company) control the 2FA authentication method you have configured. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)." -如果你在使用属于组织的存储库,则应[删除自己的组织成员身份](/articles/removing-yourself-from-an-organization)。 请注意,如果你是组织所有者,应先将[组织的所有权转让](/articles/transferring-organization-ownership)给其他人。 +## Leaving organizations -除非使用的是 {% data variables.product.prodname_managed_user %},否则即使离开组织,你仍然可以访问你的个人帐户。 有关 {% data variables.product.prodname_emus %} 的详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[关于 {% data variables.product.prodname_emus %}]({% ifversion not ghec%}/enterprise-cloud@latest{% endif %}/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users){% ifversion not ghec %}”。{% else %}。{% endif %} +If you've been working with repositories that belong to an organization, you'll want to [remove yourself as a member of the organization](/articles/removing-yourself-from-an-organization). Note that if you are the organization owner, you should first [transfer ownership of the organization](/articles/transferring-organization-ownership) to another person. -## 删除与个人仓库的职业关联 +Unless you're using a {% data variables.enterprise.prodname_managed_user %}, you'll still be able to access your personal account, even after leaving the organization. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}]({% ifversion not ghec%}/enterprise-cloud@latest{% endif %}/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} -如果你在属于其他人的个人帐户的存储库中与其进行了专业协作,则应从这些存储库中[删除自己的协作者身份](/articles/removing-yourself-from-a-collaborator-s-repository)。 +## Removing professional associations with personal repositories -- [停止关注与工作相关的存储库](https://github.com/watching)。 您不再需要这些通知了! -- [转让你拥有的存储库](/articles/how-to-transfer-a-repository),在你离开后,其他人可能需要继续使用该存储库处理工作。 -- [删除与你的工作相关且属于你的分支](/articles/deleting-a-repository)。 不用担心,删除复刻不会删除上游仓库。 -- 删除您的计算机上可能存在的复刻本地副本: +If you've been collaborating professionally with another person on repositories that belong to their personal account, you'll want to [remove yourself as a collaborator](/articles/removing-yourself-from-a-collaborator-s-repository) from those repositories. + +- [Stop watching repositories](https://github.com/watching) related to your work. You won't want those notifications anymore! +- [Transfer repositories you own](/articles/how-to-transfer-a-repository) that others may need to continue working on after you leave. +- [Delete forks that belong to you](/articles/deleting-a-repository) that are related to the work you were doing. Don't worry, deleting a fork doesn't delete the upstream repository. +- Delete local copies of your forks that may exist on your computer: ```shell -$ rm -rf work_directory +$ rm -rf WORK_DIRECTORY ``` diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md b/translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md index c93ac3bc0f..eed83fb6ff 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md @@ -1,6 +1,6 @@ --- -title: 关于持续集成 -intro: '您可以直接在 {% data variables.product.prodname_dotcom %} 仓库中通过 {% data variables.product.prodname_actions %} 创建自定义持续集成 (CI) 工作流程。' +title: About continuous integration +intro: 'You can create custom continuous integration (CI) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.' redirect_from: - /articles/about-continuous-integration - /github/automating-your-workflow-with-github-actions/about-continuous-integration @@ -16,48 +16,45 @@ type: overview topics: - CI shortTitle: Continuous integration -ms.openlocfilehash: 26b9088133ad561900d06a0c885d6b06b9b55861 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147880659' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## 关于持续集成 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} -持续集成 (CI) 是一种需要频繁提交代码到共享仓库的软件实践。 频繁提交代码能较早检测到错误,减少在查找错误来源时开发者需要调试的代码量。 频繁的代码更新也更便于从软件开发团队的不同成员合并更改。 这对开发者非常有益,他们可以将更多时间用于编写代码,而减少在调试错误或解决合并冲突上所花的时间。 +## About continuous integration -提交代码到仓库时,可以持续创建并测试代码,以确保提交未引入错误。 您的测试可以包括代码语法检查(检查样式格式)、安全性检查、代码覆盖率、功能测试及其他自定义检查。 +Continuous integration (CI) is a software practice that requires frequently committing code to a shared repository. Committing code more often detects 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. -创建和测试代码需要服务器。 您可以在推送代码到仓库之前在本地创建并测试更新,也可以使用 CI 服务器检查仓库中的新代码提交。 +When you commit code to your repository, you can continuously build and test the code to make sure that the commit doesn't introduce errors. Your tests can include code linters (which check style formatting), security checks, code coverage, functional tests, and other custom checks. -## 关于使用 {% data variables.product.prodname_actions %} 的持续集成 +Building and testing your code requires a server. You can build and test updates locally before pushing code to a repository, or you can use a CI server that checks for new code commits in a repository. -{% ifversion ghae %}使用 {% data variables.product.prodname_actions %} 的 CI 提供可以在存储库中生成代码并运行测试的工作流。 工作流程可以在您托管的运行器系统上运行。 有关详细信息,请参阅[关于自承载运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)。 -{% else %}使用 {% data variables.product.prodname_actions %} 的 CI 提供可以在仓库中构建代码并运行测试的工作流程。 工作流程可在 {% data variables.product.prodname_dotcom %} 托管的虚拟机或您自行托管的机器上运行。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_dotcom %} 托管的运行器](/actions/using-github-hosted-runners/about-github-hosted-runners)”和“[关于自托管运行器](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)”。 +## About continuous integration using {% data variables.product.prodname_actions %} + +{% ifversion ghae %}CI using {% data variables.product.prodname_actions %} offers workflows that can build the code in your repository and run your tests. Workflows can run on runner systems that you host. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." +{% else %} CI using {% data variables.product.prodname_actions %} offers workflows that can build the code in your repository and run your tests. Workflows can run on {% data variables.product.prodname_dotcom %}-hosted virtual machines, or on machines that you host yourself. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and "[About self-hosted runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)." {% endif %} -可以配置 CI 工作流,使其在 {% data variables.product.prodname_dotcom %} 事件发生时(例如,当新代码推送到存储库时)运行、按设定的时间表运行,或在使用存储库分发 Webhook 的外部事件发生时运行。 +You can configure your CI workflow to run when a {% data variables.product.prodname_dotcom %} event occurs (for example, when new code is pushed to your repository), on a set schedule, or when an external event occurs using the repository dispatch webhook. -{% data variables.product.product_name %} 运行 CI 测试并在拉取请求中提供每次测试的结果,因此您可以查看分支中的更改是否引入错误。 如果工作流程中的所有 CI 测试通过,您推送的更改可供团队成员审查或合并 如果测试失败,则是其中某项更改导致了失败。 +{% data variables.product.product_name %} runs your CI tests and provides the results of each test in the pull request, so you can see whether the change in your branch introduces an error. When all CI tests in a workflow pass, the changes you pushed are ready to be reviewed by a team member or merged. When a test fails, one of your changes may have caused the failure. -如果在仓库中设置了 CI,{% data variables.product.product_name %} 会分析仓库中的代码,并根据仓库中的语言和框架推荐 CI 工作流程。 例如,如果使用 [Node.js](https://nodejs.org/en/),{% data variables.product.product_name %} 将建议使用入门工作流来安装 Node.js 包并运行测试。 您可以使用 {% data variables.product.product_name %} 建议的 CI 入门工作流程,自定义建议的入门工作流程,或创建自己的自定义工作流程文件来运行 CI 测试。 +When you set up CI in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends CI workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a starter workflow that installs your Node.js packages and runs your tests. You can use the CI starter workflow suggested by {% data variables.product.product_name %}, customize the suggested starter workflow, or create your own custom workflow file to run your CI tests. -![建议的持续集成入门工作流程屏幕截图](/assets/images/help/repository/ci-with-actions-template-picker.png) +![Screenshot of suggested continuous integration starter workflows](/assets/images/help/repository/ci-with-actions-template-picker.png) -除了帮助设置项目的 CI 工作流程之外,您还可以使用 {% data variables.product.prodname_actions %} 创建跨整个软件开发生命周期的工作流程。 例如,您可以使用操作来部署、封装或发行项目。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_actions %}](/articles/about-github-actions)”。 +In addition to helping you set up CI workflows for your project, you can use {% data variables.product.prodname_actions %} to create workflows across the full software development life cycle. For example, you can use actions to deploy, package, or release your project. For more information, see "[About {% data variables.product.prodname_actions %}](/articles/about-github-actions)." -有关常用术语的定义,请参阅“[{% data variables.product.prodname_actions %} 的核心概念](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)”。 +For a definition of common terms, see "[Core concepts for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)." -## 入门工作流程 +## Starter workflow -{% data variables.product.product_name %} 为各种语言和框架提供 CI 入门工作流程。 +{% data variables.product.product_name %} offers CI starter workflow for a variety of languages and frameworks. -在 {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) 存储库{% else %} {% data variables.product.product_location %} 上的 `actions/starter-workflows` 存储库{% endif %}中浏览 {% data variables.product.company_short %} 提供的 CI 入门工作流的完整列表。 +Browse the complete list of CI starter workflow offered by {% data variables.product.company_short %} in the {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) repository{% else %} `actions/starter-workflows` repository on {% data variables.location.product_location %}{% endif %}. -## 延伸阅读 +## Further reading {% ifversion fpt or ghec %} -- [管理 {% data variables.product.prodname_actions %} 的计费](/billing/managing-billing-for-github-actions){% endif %} +- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)" +{% endif %} diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md index 5874bfae6e..382e81006b 100644 --- a/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md +++ b/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md @@ -27,9 +27,9 @@ Once you complete this project, you should understand how to build your own comp ## Prerequisites -Before you begin, you'll create a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. +Before you begin, you'll create a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. -1. Create a new public repository on {% data variables.product.product_location %}. You can choose any repository name, or use the following `hello-world-composite-action` example. You can add these files after your project has been pushed to {% data variables.product.product_name %}. For more information, see "[Create a new repository](/articles/creating-a-new-repository)." +1. Create a new public repository on {% data variables.location.product_location %}. You can choose any repository name, or use the following `hello-world-composite-action` example. You can add these files after your project has been pushed to {% data variables.product.product_name %}. For more information, see "[Create a new repository](/articles/creating-a-new-repository)." 1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)." 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 6d91c1035f..6ea8fbe52c 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 @@ -44,7 +44,7 @@ You may find it helpful to have a basic understanding of {% data variables.produ Before you begin, you'll need to create a {% data variables.product.prodname_dotcom %} repository. -1. Create a new repository on {% data variables.product.product_location %}. You can choose any repository name or use "hello-world-docker-action" like this example. For more information, see "[Create a new repository](/articles/creating-a-new-repository)." +1. Create a new repository on {% data variables.location.product_location %}. You can choose any repository name or use "hello-world-docker-action" like this example. For more information, see "[Create a new repository](/articles/creating-a-new-repository)." 1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)." diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md index 66fc48555f..5a1ea071a9 100644 --- a/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md @@ -41,7 +41,7 @@ Before you begin, you'll need to download Node.js and create a public {% data va {% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}https://nodejs.org/en/download/{% else %}https://nodejs.org/en/download/releases/{% endif %} -1. Create a new public repository on {% data variables.product.product_location %} and call it "hello-world-javascript-action". For more information, see "[Create a new repository](/articles/creating-a-new-repository)." +1. Create a new public repository on {% data variables.location.product_location %} and call it "hello-world-javascript-action". For more information, see "[Create a new repository](/articles/creating-a-new-repository)." 1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)." @@ -141,29 +141,31 @@ In your `hello-world-javascript-action` directory, create a `README.md` file tha - Environment variables the action uses. - An example of how to use your action in a workflow. -```markdown{:copy} +````markdown{:copy} # Hello world javascript action This action prints "Hello World" or "Hello" + the name of a person to greet to the log. ## Inputs -## `who-to-greet` +### `who-to-greet` **Required** The name of the person to greet. Default `"World"`. ## Outputs -## `time` +### `time` The time we greeted you. ## Example usage +```yaml uses: actions/hello-world-javascript-action@v1.1 with: who-to-greet: 'Mona the Octocat' ``` +```` ## Commit, tag, and push your action to GitHub diff --git a/translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md b/translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md index 196b7c07b2..31f3680e14 100644 --- a/translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md +++ b/translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md @@ -1,6 +1,6 @@ --- -title: 使用 GitHub Actions 进行部署 -intro: 了解如何使用环境和并发性等功能控制部署。 +title: Deploying with GitHub Actions +intro: Learn how to control deployments with features like environments and concurrency. versions: fpt: '*' ghes: '*' @@ -12,38 +12,34 @@ redirect_from: topics: - CD shortTitle: Deploy with GitHub Actions -ms.openlocfilehash: 533d85d83bea53d34af3d8b9a47d0d4426ea4bc6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145179182' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## 简介 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} -{% data variables.product.prodname_actions %} 提供了允许您控制部署的功能。 方法: +## Introduction -- 使用各种事件触发工作流程。 -- 配置环境以在作业可以继续之前设置规则,并限制对机密的访问。 -- 使用并发性来控制一次运行的部署数。 +{% data variables.product.prodname_actions %} offers features that let you control deployments. You can: -有关持续部署的详细信息,请参阅“[关于持续部署](/actions/deployment/about-continuous-deployment)”。 +- Trigger workflows with a variety of events. +- Configure environments to set rules before a job can proceed and to limit access to secrets. +- Use concurrency to control the number of deployments running at a time. -## 先决条件 +For more information about continuous deployment, see "[About continuous deployment](/actions/deployment/about-continuous-deployment)." -您应该熟悉 {% data variables.product.prodname_actions %} 的语法。 有关详细信息,请参阅“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。 +## Prerequisites -## 触发部署 +You should be familiar with the syntax for {% data variables.product.prodname_actions %}. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." -您可以使用各种事件来触发您的部署工作流程。 一些最常见的事件包括:`pull_request`、`push` 和 `workflow_dispatch`。 +## Triggering your deployment -例如,具有以下触发器的工作流在以下情况下会运行: +You can use a variety of events to trigger your deployment workflow. Some of the most common are: `pull_request`, `push`, and `workflow_dispatch`. -- 存在针对 `main` 分支的推送。 -- 以 `main` 分支为目标的拉取请求已打开、已同步或重新打开。 -- 有人手动触发它。 +For example, a workflow with the following triggers runs whenever: + +- There is a push to the `main` branch. +- A pull request targeting the `main` branch is opened, synchronized, or reopened. +- Someone manually triggers it. ```yaml on: @@ -56,23 +52,23 @@ on: workflow_dispatch: ``` -有关详细信息,请参阅“[触发工作流的事件](/actions/reference/events-that-trigger-workflows)”。 +For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)." -## 使用环境 +## Using environments {% data reusables.actions.about-environments %} -## 使用并发 +## Using concurrency -并发确保只有使用相同并发组的单一作业或工作流程才会同时运行。 您可以使用并发,以便环境中每次最多有一个正在进行的部署和一个待处理的部署。 +Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. You can use concurrency so that an environment has a maximum of one deployment in progress and one deployment pending at a time. {% note %} -注意:`concurrency` 和 `environment` 未连接。 并发值可以是任何字符串;它无需是环境名称。 此外,如果另一个工作流程使用相同的环境,但未指定并发性,则该工作流程将不受任何并发规则的约束。 +**Note:** `concurrency` and `environment` are not connected. The concurrency value can be any string; it does not need to be an environment name. Additionally, if another workflow uses the same environment but does not specify concurrency, that workflow will not be subject to any concurrency rules. {% endnote %} -例如,当以下工作流运行时,如果使用 `production` 并发组的任何作业或工作流正在进行中,则它将暂停并且状态为 `pending`。 它还将取消使用 `production` 并发组且状态为 `pending` 的任何作业或工作流。 这意味着,由于使用了 `production` 并发组,因此最多有一个正在运行和一个待处理的作业或工作流。 +For example, when the following workflow runs, it will be paused with the status `pending` if any job or workflow that uses the `production` concurrency group is in progress. It will also cancel any job or workflow that uses the `production` concurrency group and has the status `pending`. This means that there will be a maximum of one running and one pending job or workflow in that uses the `production` concurrency group. ```yaml name: Deployment @@ -93,7 +89,7 @@ jobs: # ...deployment-specific steps ``` -您也可以在作业级别指定并发性。 这将允许工作流中的其他作业继续,即使并发作业的状态为 `pending`。 +You can also specify concurrency at the job level. This will allow other jobs in the workflow to proceed even if the concurrent job is `pending`. ```yaml name: Deployment @@ -113,7 +109,7 @@ jobs: # ...deployment-specific steps ``` -还可以使用 `cancel-in-progress` 取消同一并发组中任何当前正在运行的作业或工作流。 +You can also use `cancel-in-progress` to cancel any currently running job or workflow in the same concurrency group. ```yaml name: Deployment @@ -136,41 +132,42 @@ jobs: # ...deployment-specific steps ``` -有关如何编写特定于部署的步骤的指导,请参阅“[查找部署示例](#finding-deployment-examples)”。 +For guidance on writing deployment-specific steps, see "[Finding deployment examples](#finding-deployment-examples)." -## 查看部署历史记录 +## Viewing deployment history -当 {% data variables.product.prodname_actions %} 工作流部署到某个环境时,该环境将显示在存储库的主页上。 有关如何查看环境部署的详细信息,请参阅“[查看部署历史记录](/developers/overview/viewing-deployment-history)”。 +When a {% data variables.product.prodname_actions %} workflow deploys to an environment, the environment is displayed on the main page of the repository. For more information about viewing deployments to environments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)." -## 监控工作流程运行 +## Monitoring workflow runs -每个工作流程运行都会生成一个实时图表,说明运行进度。 您可以使用此图表来监控和调试部署。 有关详细信息,请参阅“[使用可视化效果图](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)”。 +Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug deployments. For more information see, "[Using the visualization graph](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)." -您还可以查看每个工作流程运行的日志和工作流程运行的历史记录。 有关详细信息,请参阅“[查看工作流运行历史记录](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)”。 +You can also view the logs of each workflow run and the history of workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." -## 通过应用跟踪部署 +## Tracking deployments through apps -{% ifversion fpt or ghec %} 如果在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的个人帐户或组织与 Microsoft Teams 或 Slack 集成,可以通过 Microsoft Teams 或 Slack 跟踪使用环境的部署。 例如,当部署正在等待批准、部署获得批准或部署状态更改时,您可以通过应用接收通知。 有关如何集成 Microsoft Teams 或 Slack 的详细信息,请参阅“[GitHub 扩展和集成](/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations#team-communication-tools)”。 +{% ifversion fpt or ghec %} +If your personal account or organization on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} is integrated with Microsoft Teams or Slack, you can track deployments that use environments through Microsoft Teams or Slack. For example, you can receive notifications through the app when a deployment is pending approval, when a deployment is approved, or when the deployment status changes. For more information about integrating Microsoft Teams or Slack, see "[GitHub extensions and integrations](/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations#team-communication-tools)." {% endif %} -你还可以构建一个应用,该应用使用部署和部署状态 web 挂钩来跟踪部署。 {% data reusables.actions.environment-deployment-event %} 有关详细信息,请参阅“[应用](/developers/apps)”和“[Webhook 事件和有效负载](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)”。 +You can also build an app that uses deployment and deployment status webhooks to track deployments. {% data reusables.actions.environment-deployment-event %} For more information, see "[Apps](/developers/apps)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)." {% ifversion fpt or ghes or ghec %} -## 选择运行器 +## Choosing a runner -您可以在 {% data variables.product.company_short %} 托管的运行器或自托管运行器上运行部署工作流程。 来自 {% data variables.product.company_short %} 托管的运行器的流量可能来自[各种网络地址](/rest/reference/meta#get-github-meta-information)。 如果要部署到内部环境,并且公司将外部流量限制到专用网络,则在 {% data variables.product.company_short %} 托管的运行器上运行的 {% data variables.product.prodname_actions %} 工作流可能无法与内部服务或资源通信。 为了克服这一点,您可以托管自己的运行器。 有关详细信息,请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”和“[关于 GitHub 托管的运行器](/actions/using-github-hosted-runners/about-github-hosted-runners)”。 +You can run your deployment workflow on {% data variables.product.company_short %}-hosted runners or on self-hosted runners. Traffic from {% data variables.product.company_short %}-hosted runners can come from a [wide range of network addresses](/rest/reference/meta#get-github-meta-information). If you are deploying to an internal environment and your company restricts external traffic into private networks, {% data variables.product.prodname_actions %} workflows running on {% data variables.product.company_short %}-hosted runners may not be able to communicate with your internal services or resources. To overcome this, you can host your own runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[About GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)." {% endif %} -## 显示状态徽章 +## Displaying a status badge -您可以使用状态徽章来显示您的部署工作流程状态。 {% data reusables.repositories.actions-workflow-status-badge-intro %} +You can use a status badge to display the status of your deployment workflow. {% data reusables.repositories.actions-workflow-status-badge-intro %} -有关详细信息,请参阅“[添加工作流状态徽章](/actions/managing-workflow-runs/adding-a-workflow-status-badge)”。 +For more information, see "[Adding a workflow status badge](/actions/managing-workflow-runs/adding-a-workflow-status-badge)." -## 查找部署示例 +## Finding deployment examples -本文演示了可添加到部署工作流程的 {% data variables.product.prodname_actions %} 的功能。 +This article demonstrated features of {% data variables.product.prodname_actions %} that you can add to your deployment workflows. {% data reusables.actions.cd-templates-actions %} diff --git a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md index c857ecebd0..29abd3f106 100644 --- a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md +++ b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md @@ -55,9 +55,9 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you 1. Set registry credentials for your web app. - Create a personal access token with the `repo` and `read:packages` scopes. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." + Create a {% data variables.product.pat_v1 %} with the `repo` and `read:packages` scopes. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - Set `DOCKER_REGISTRY_SERVER_URL` to `https://ghcr.io`, `DOCKER_REGISTRY_SERVER_USERNAME` to the GitHub username or organization that owns the repository, and `DOCKER_REGISTRY_SERVER_PASSWORD` to your personal access token from above. This will give your web app credentials so it can pull the container image after your workflow pushes a newly built image to the registry. You can do this with the following Azure CLI command: + Set `DOCKER_REGISTRY_SERVER_URL` to `https://ghcr.io`, `DOCKER_REGISTRY_SERVER_USERNAME` to the GitHub username or organization that owns the repository, and `DOCKER_REGISTRY_SERVER_PASSWORD` to your {% data variables.product.pat_generic %} from above. This will give your web app credentials so it can pull the container image after your workflow pushes a newly built image to the registry. You can do this with the following Azure CLI command: ```shell az webapp config appsettings set \ diff --git a/translations/zh-CN/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md b/translations/zh-CN/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md index 7e236f7aeb..3a4f73c6f2 100644 --- a/translations/zh-CN/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md +++ b/translations/zh-CN/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md @@ -1,7 +1,7 @@ --- -title: 使用并发、表达式和测试矩阵 -shortTitle: 'Using concurrency, expressions, and a test matrix' -intro: '如何使用高级 {% data variables.product.prodname_actions %} 功能进行持续集成 (CI)。' +title: 'Using concurrency, expressions, and a test matrix' +shortTitle: 'Use concurrency, expressions, and a test matrix' +intro: 'How to use advanced {% data variables.product.prodname_actions %} features for continuous integration (CI).' versions: fpt: '*' ghes: '>= 3.5' @@ -10,34 +10,40 @@ versions: type: how_to topics: - Workflows -ms.openlocfilehash: f4edac59fdbcc8f8825a51e25b737b94b17128b0 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147496578' --- + {% data reusables.actions.enterprise-github-hosted-runners %} -## 示例概述 +## Example overview -{% data reusables.actions.example-workflow-intro-ci %}触发此工作流时,它将使用 `npm test` 的测试组合矩阵来测试代码。 +{% data reusables.actions.example-workflow-intro-ci %} When this workflow is triggered, it tests your code using a matrix of test combinations with `npm test`. {% data reusables.actions.example-diagram-intro %} -![工作流步骤概述图](/assets/images/help/images/overview-actions-using-concurrency-expressions-and-a-test-matrix.png) +![Overview diagram of workflow steps](/assets/images/help/images/overview-actions-using-concurrency-expressions-and-a-test-matrix.png) -## 此示例中使用的功能 +## Features used in this example {% data reusables.actions.example-table-intro %} -| **功能** | **实现** | +| **Feature** | **Implementation** | | --- | --- | -{% data reusables.actions.workflow-dispatch-table-entry %} {% data reusables.actions.pull-request-table-entry %} {% data reusables.actions.cron-table-entry %} {% data reusables.actions.permissions-table-entry %} {% data reusables.actions.concurrency-table-entry %} | 根据存储库的不同,在不同的运行器上运行作业: | [`runs-on`](/actions/using-jobs/choosing-the-runner-for-a-job)| {% data reusables.actions.if-conditions-table-entry %} | 使用矩阵创建不同的测试配置: | [`matrix`](/actions/using-jobs/using-a-build-matrix-for-your-jobs)| {% data reusables.actions.checkout-action-table-entry %} {% data reusables.actions.setup-node-table-entry %} | 缓存依赖项:| [`actions/cache`](/actions/advanced-guides/caching-dependencies-to-speed-up-workflows)| | 在运行器上运行测试:| `npm test`| +{% data reusables.actions.workflow-dispatch-table-entry %} +{% data reusables.actions.pull-request-table-entry %} +{% data reusables.actions.cron-table-entry %} +{% data reusables.actions.permissions-table-entry %} +{% data reusables.actions.concurrency-table-entry %} +| Running the job on different runners, depending on the repository: | [`runs-on`](/actions/using-jobs/choosing-the-runner-for-a-job)| +{% data reusables.actions.if-conditions-table-entry %} +| Using a matrix to create different test configurations: | [`matrix`](/actions/using-jobs/using-a-build-matrix-for-your-jobs)| +{% data reusables.actions.checkout-action-table-entry %} +{% data reusables.actions.setup-node-table-entry %} +| Caching dependencies: | [`actions/cache`](/actions/advanced-guides/caching-dependencies-to-speed-up-workflows)| +| Running tests on the runner: | `npm test`| -## 示例工作流 +## Example workflow -{% data reusables.actions.example-docs-engineering-intro %} [`test.yml`](https://github.com/github/docs/blob/main/.github/workflows/test.yml)。 +{% data reusables.actions.example-docs-engineering-intro %} [`test.yml`](https://github.com/github/docs/blob/main/.github/workflows/test.yml). {% data reusables.actions.note-understanding-example %} @@ -106,7 +112,7 @@ jobs: # NOT clone them initially and instead, include them manually # only for the test groups that we know need the files. lfs: {% raw %}${{ matrix.test-group == 'content' }}{% endraw %} - # Enables cloning the Early Access repo later with the relevant PAT + # Enables cloning the Early Access repo later with the relevant {% data variables.product.pat_generic %} persist-credentials: 'false' - name: Figure out which docs-early-access branch to checkout, if internal repo @@ -205,15 +211,15 @@ jobs:
-Este fluxo de trabalho é executado sempre que um pull request no repositório for marcado como "pronto para revisão". +This workflow runs whenever a pull request in the repository is marked as "ready for review".
-Usa a ação tibdex/github-app-token para gerar um token de acesso de instalação para seu aplicativo por meio da ID do aplicativo e da chave privada. O token de acesso à instalação é acessado posteriormente no fluxo de trabalho como {% raw %}${{ steps.generate_token.outputs.token }}{% endraw %}. +Uses the tibdex/github-app-token action to generate an installation access token for your app from the app ID and private key. The installation access token is accessed later in the workflow as {% raw %}${{ steps.generate_token.outputs.token }}{% endraw %}.

-Substitua APP_ID pelo nome do segredo que contém a ID do aplicativo. +Replace APP_ID with the name of the secret that contains your app ID.

-Substitua APP_PEM pelo nome do segredo que contém a chave privada do aplicativo. +Replace APP_PEM with the name of the secret that contains your app private key.
-Define variáveis de ambiente para esta etapa. +Sets environment variables for this step.

-Se estiver usando um token de acesso pessoal, substitua YOUR_TOKEN pelo nome do segredo que contém seu token de acesso pessoal. +If you are using a {% data variables.product.pat_generic %}, replace YOUR_TOKEN with the name of the secret that contains your {% data variables.product.pat_generic %}.

-Substitua YOUR_ORGANIZATION pelo nome da sua organização. Por exemplo, octo-org. +Replace YOUR_ORGANIZATION with the name of your organization. For example, octo-org.

-Substitua YOUR_PROJECT_NUMBER pelo número do projeto. Para encontrar o número do projeto, consulte a URL do projeto. Por exemplo, https://github.com/orgs/octo-org/projects/5 tem o número de projeto 5. +Replace YOUR_PROJECT_NUMBER with your project number. To find the project number, look at the project URL. For example, https://github.com/orgs/octo-org/projects/5 has a project number of 5.
-

Usa a {% data variables.product.prodname_cli %} para consultar a API da ID do projeto e a ID e retornar o nome e a ID dos primeiros 20 campos do projeto. fields retorna uma união e a consulta usa fragmentos embutidos (... on) para retornar informações sobre campos ProjectV2Field e ProjectV2SingleSelectField.

+

Uses {% data variables.product.prodname_cli %} to query the API for the ID of the project and return the name and ID of the first 20 fields in the project. fields returns a union and the query uses inline fragments (... on) to return information about any ProjectV2Field and ProjectV2SingleSelectField fields.

-

A resposta é armazenada em um arquivo chamado project_data.json.

+

The response is stored in a file called project_data.json.

-Analisa a resposta da consulta da API e armazena os IDs relevantes como variáveis de ambiente. Modifique este ID para obter o ID para diferentes campos ou opções. Por exemplo: +Parses the response from the API query and stores the relevant IDs as environment variables. Modify this to get the ID for different fields or options. For example:
    -
  • Para obter a ID de um campo chamado Team, adicione echo 'TEAM_FIELD_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Team") | .id' project_data.json) >> $GITHUB_ENV.
  • -
  • Para obter a ID de uma opção chamada Octoteam para o campo Team único selecionado, adicione echo 'OCTOTEAM_OPTION_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Team") |.options[] | select(.name=="Octoteam") |.id' project_data.json) >> $GITHUB_ENV
  • +
  • To get the ID of a field called Team, add echo 'TEAM_FIELD_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Team") | .id' project_data.json) >> $GITHUB_ENV.
  • +
  • To get the ID of an option called Octoteam for the Team single select field, add echo 'OCTOTEAM_OPTION_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Team") |.options[] | select(.name=="Octoteam") |.id' project_data.json) >> $GITHUB_ENV
-Observação: esse fluxo de trabalho pressupõe que você tenha um projeto com um só campo de seleção chamado "Status" que inclui uma opção chamada "Tarefas pendentes" e um campo de data chamado "Data da postagem". Você deve modificar esta seção para corresponder aos campos presentes na sua tabela. +Note: This workflow assumes that you have a project with a single select field called "Status" that includes an option called "Todo" and a date field called "Date posted". You must modify this section to match the fields that are present in your table.
-Define variáveis de ambiente para esta etapa. O GITHUB_TOKEN é descrito acima. PR_ID é a ID da solicitação de pull que disparou esse fluxo de trabalho. +Sets environment variables for this step. GITHUB_TOKEN is described above. PR_ID is the ID of the pull request that triggered this workflow.
-Usa a {% data variables.product.prodname_cli %} e a API para adicionar a solicitação de pull que disparou esse fluxo de trabalho ao projeto. O sinalizador jq analisa a resposta para obter a ID do item criado. +Uses {% data variables.product.prodname_cli %} and the API to add the pull request that triggered this workflow to the project. The jq flag parses the response to get the ID of the created item.
-Armazena o ID do item criado como uma variável de ambiente. +Stores the ID of the created item as an environment variable.
-Salva a data atual como uma variável de ambiente no formato yyyy-mm-dd. +Saves the current date as an environment variable in yyyy-mm-dd format.
-Define variáveis de ambiente para esta etapa. O GITHUB_TOKEN é descrito acima. +Sets environment variables for this step. GITHUB_TOKEN is described above.
-Define o valor do campo Status como Todo. Define o valor do campo Date posted. +Sets the value of the Status field to Todo. Sets the value of the Date posted field.
-## 了解示例 +## Understanding the example - {% data reusables.actions.example-explanation-table-intro %} + {% data reusables.actions.example-explanation-table-intro %} - - + + @@ -238,7 +244,7 @@ on: @@ -250,7 +256,7 @@ on: @@ -262,7 +268,7 @@ on: @@ -276,7 +282,7 @@ on: @@ -290,7 +296,7 @@ permissions: @@ -304,7 +310,7 @@ concurrency: @@ -316,7 +322,7 @@ concurrency: @@ -328,7 +334,7 @@ jobs: @@ -340,7 +346,7 @@ jobs: @@ -352,7 +358,7 @@ jobs: @@ -364,7 +370,7 @@ jobs: @@ -375,7 +381,7 @@ jobs: ``` @@ -387,7 +393,7 @@ jobs: @@ -410,7 +416,7 @@ jobs: @@ -422,7 +428,7 @@ jobs: @@ -438,7 +444,7 @@ jobs: @@ -478,7 +484,7 @@ jobs: @@ -497,7 +503,7 @@ jobs: @@ -527,7 +533,7 @@ jobs: @@ -546,7 +552,7 @@ jobs: @@ -560,7 +566,7 @@ jobs: @@ -576,7 +582,7 @@ jobs: @@ -589,7 +595,7 @@ jobs: @@ -605,7 +611,7 @@ jobs: @@ -618,7 +624,7 @@ jobs: @@ -634,12 +640,12 @@ jobs:
代码解释CodeExplanation
-通过 `on` 关键字,可以定义运行工作流时触发的事件。 可在此处定义多个事件。 有关详细信息,请参阅“[触发工作流](/actions/using-workflows/triggering-a-workflow#using-events-to-trigger-workflows)”。 +The `on` keyword lets you define the events that trigger when the workflow is run. You can define multiple events here. For more information, see "[Triggering a workflow](/actions/using-workflows/triggering-a-workflow#using-events-to-trigger-workflows)."
-如果要在 UI 中手动运行此工作流,请添加 `workflow_dispatch` 事件。 有关详细信息,请参阅 [`workflow_dispatch`](/actions/reference/events-that-trigger-workflows#workflow_dispatch)。 +Add the `workflow_dispatch` event if you want to be able to manually run this workflow in the UI. For more information, see [`workflow_dispatch`](/actions/reference/events-that-trigger-workflows#workflow_dispatch).
-添加 `pull_request` 事件,以便每次创建或更新拉取请求时,工作流都会自动运行。 有关详细信息,请参阅 [`pull_request`](/actions/using-workflows/events-that-trigger-workflows#pull_request)。 +Add the `pull_request` event, so that the workflow runs automatically every time a pull request is created or updated. For more information, see [`pull_request`](/actions/using-workflows/events-that-trigger-workflows#pull_request).
-添加 `push` 事件,以便每次将提交推送到匹配筛选器 `main` 的分支时,工作流都会自动运行。 有关详细信息,请参阅 [`push`](/actions/using-workflows/events-that-trigger-workflows#push)。 +Add the `push` event, so that the workflow runs automatically every time a commit is pushed to a branch matching the filter `main`. For more information, see [`push`](/actions/using-workflows/events-that-trigger-workflows#push).
-修改授予 `GITHUB_TOKEN` 的默认权限。 这将因工作流的需求而异。 有关详细信息,请参阅“[为作业分配权限](/actions/using-jobs/assigning-permissions-to-jobs)”。 +Modifies the default permissions granted to `GITHUB_TOKEN`. This will vary depending on the needs of your workflow. For more information, see "[Assigning permissions to jobs](/actions/using-jobs/assigning-permissions-to-jobs)."
-为特定事件创建并发组,并使用 `||` 运算符定义回退值。 有关详细信息,请参阅“[使用并发](/actions/using-jobs/using-concurrency)”。 +Creates a concurrency group for specific events, and uses the `||` operator to define fallback values. For more information, see "[Using concurrency](/actions/using-jobs/using-concurrency)."
-取消同一并发组中任何当前正在运行的作业或工作流。 +Cancels any currently running job or workflow in the same concurrency group.
-将工作流文件中运行的所有作业组合在一起。 +Groups together all the jobs that run in the workflow file.
-定义 ID 为 `test` 的作业,该作业存储在 `jobs` 键中。 +Defines a job with the ID `test` that is stored within the `jobs` key.
-根据运行工作流的存储库,将作业配置为在 {% data variables.product.prodname_dotcom %} 托管的运行器或自托管运行器上运行。 在此示例中,如果存储库名为 `docs-internal` 且位于 `github` 组织内,则作业将在自托管运行器上运行。 如果存储库与此路径不匹配,则其会在由 {% data variables.product.prodname_dotcom %} 托管的 `ubuntu-latest` 运行器上运行。 有关这些选项的详细信息,请参阅“[为作业选择运行器](/actions/using-jobs/choosing-the-runner-for-a-job)”。 +Configures the job to run on a {% data variables.product.prodname_dotcom %}-hosted runner or a self-hosted runner, depending on the repository running the workflow. In this example, the job will run on a self-hosted runner if the repository is named `docs-internal` and is within the `github` organization. If the repository doesn't match this path, then it will run on an `ubuntu-latest` runner hosted by {% data variables.product.prodname_dotcom %}. For more information on these options see "[Choosing the runner for a job](/actions/using-jobs/choosing-the-runner-for-a-job)."
-设置作业在自动取消之前运行的最大分钟数。 有关详细信息,请参阅 [`timeout-minutes`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes)。 +Sets the maximum number of minutes to let the job run before it is automatically canceled. For more information, see [`timeout-minutes`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes).
- 本部分定义作业的生成矩阵。 + This section defines the build matrix for your jobs.
-将 `fail-fast` 设置为 `false` 可以防止 {% data variables.product.prodname_dotcom %} 在矩阵作业失败时取消所有正在进行的作业。 +Setting `fail-fast` to `false` prevents {% data variables.product.prodname_dotcom %} from cancelling all in-progress jobs if any matrix job fails.
-创建名为 `test-group` 的矩阵,其中包含测试组数组。 这些值与将由 `npm test` 运行的测试组的名称匹配。 +Creates a matrix named `test-group`, with an array of test groups. These values match the names of test groups that will be run by `npm test`.
-将作为 `test` 作业一部分运行的所有步骤组合在一起。 工作流中的每个作业都有其自己的 `steps` 部分。 +Groups together all the steps that will run as part of the `test` job. Each job in a workflow has its own `steps` section.
-`uses` 关键字指示作业检索名为 `actions/checkout` 的操作。 这是检出仓库并将其下载到运行器的操作,允许针对您的代码运行操作(例如测试工具)。 只要工作流程针对仓库的代码运行,或者您使用仓库中定义的操作,您都必须使用检出操作。 使用 `with` 键为操作提供了一些额外的选项。 +The `uses` keyword tells the job to retrieve the action named `actions/checkout`. This is an action that checks out your repository and downloads it to the runner, allowing you to run actions against your code (such as testing tools). You must use the checkout action any time your workflow will run against the repository's code or you are using an action defined in the repository. Some extra options are provided to the action using the `with` key.
-如果当前存储库是 `github/docs-internal` 存储库,此步骤将使用 `actions/github-script` 操作运行脚本,检查是否存在名为 `docs-early-access` 的分支。 +If the current repository is the `github/docs-internal` repository, this step uses the `actions/github-script` action to run a script to check if there is a branch called `docs-early-access`.
-如果当前存储库是 `github/docs-internal` 存储库,此步骤将从上一步中标识的 `github/docs-early-access` 签出分支。 +If the current repository is the `github/docs-internal` repository, this step checks out the branch from the `github/docs-early-access` that was identified in the previous step.
@@ -514,7 +520,7 @@ jobs: -如果当前存储库是 `github/docs-internal` 存储库,则此步骤将使用 `run` 关键字执行 shell 命令,将 `docs-early-access` 存储库的文件夹移动到主存储库的文件夹中。 +If the current repository is the `github/docs-internal` repository, this step uses the `run` keyword to execute shell commands to move the `docs-early-access` repository's folders into the main repository's folders.
-此步骤运行一个命令,从存储库签出 LFS 对象。 +This step runs a command to check out LFS objects from the repository.
-此步骤使用 `trilom/file-changes-action` 操作收集拉取请求中更改的文件,以便在下一步中分析它们。 此示例使用 `a6ca26c14274c33b15e6499323aac178af06ad4b` SHA 固定到操作的特定版本。 +This step uses the `trilom/file-changes-action` action to gather the files changed in the pull request, so they can be analyzed in the next step. This example is pinned to a specific version of the action, using the `a6ca26c14274c33b15e6499323aac178af06ad4b` SHA.
-此步骤运行 shell 命令,该命令使用上一步的输出创建文件,其中包含在拉取请求中更改的文件列表。 +This step runs a shell command that uses an output from the previous step to create a file containing the list of files changed in the pull request.
-此步骤使用 `actions/setup-node` 操作在运行器上安装指定版本的 `node` 软件包,以便你可访问 `npm` 命令。 +This step uses the `actions/setup-node` action to install the specified version of the `node` software package on the runner, which gives you access to the `npm` command.
-此步骤运行 `npm ci` shell 命令来安装项目的 npm 软件包。 +This step runs the `npm ci` shell command to install the npm software packages for the project.
-此步骤使用 `actions/cache` 操作来缓存 Next.js 生成,以便工作流将尝试检索生成的缓存,而不是每次都从头重新生成它。 有关详细信息,请参阅“[缓存依赖项以加快工作流](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)”。 +This step uses the `actions/cache` action to cache the Next.js build, so that the workflow will attempt to retrieve a cache of the build, and not rebuild it from scratch every time. For more information, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)."
-此步骤运行生成脚本。 +This step runs the build script.
-此步骤使用 `npm test` 运行测试,测试矩阵为矩阵中的每个作业提供不同的 {% raw %}`${{ matrix.test-group }}`{% endraw %} 值。 它使用 `DIFF_FILE` 环境变量来识别已更改的文件,并将 `CHANGELOG_CACHE_FILE_PATH` 环境变量用于 changelog 缓存文件。 +This step runs the tests using `npm test`, and the test matrix provides a different value for {% raw %}`${{ matrix.test-group }}`{% endraw %} for each job in the matrix. It uses the `DIFF_FILE` environment variable to know which files have changed, and uses the `CHANGELOG_CACHE_FILE_PATH` environment variable for the changelog cache file.
-## 后续步骤 +## Next steps {% data reusables.actions.learning-actions %} 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 79bbe18b9c..f66ea675e4 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 @@ -17,7 +17,7 @@ type: overview ## About self-hosted runners -A self-hosted runner is a system that you deploy and manage to execute jobs from {% data variables.product.prodname_actions %} on {% ifversion ghae or ghec %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For more information about {% data variables.product.prodname_actions %}, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions){% ifversion fpt %}."{% elsif ghec or ghes or ghae %}" and "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."{% endif %} +A self-hosted runner is a system that you deploy and manage to execute jobs from {% data variables.product.prodname_actions %} on {% ifversion ghae or ghec %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For more information about {% data variables.product.prodname_actions %}, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions){% ifversion fpt %}."{% elsif ghec or ghes or ghae %}" and "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."{% endif %} {% data reusables.actions.self-hosted-runner-description %} {% data reusables.actions.self-hosted-runner-locations %} @@ -143,14 +143,14 @@ The self-hosted runner connects to {% data variables.product.product_name %} to {% data reusables.actions.self-hosted-runner-ports-protocols %} {% ifversion fpt or ghec %} -Since the self-hosted runner opens a connection to {% data variables.product.product_location %}, you do not need to allow {% data variables.product.prodname_dotcom %} to make inbound connections to your self-hosted runner. +Since the self-hosted runner opens a connection to {% data variables.location.product_location %}, you do not need to allow {% data variables.product.prodname_dotcom %} to make inbound connections to your self-hosted runner. {% elsif ghes or ghae %} -Only an outbound connection from the runner to {% data variables.product.product_location %} is required. There is no need for an inbound connection from {% data variables.product.product_location %} to the runner. +Only an outbound connection from the runner to {% data variables.location.product_location %} is required. There is no need for an inbound connection from {% data variables.location.product_location %} to the runner. {%- endif %} {% ifversion ghes %} -{% data variables.product.product_name %} must accept inbound connections from your runners over {% ifversion ghes %}HTTP(S){% else %}HTTPS{% endif %} at {% data variables.product.product_location %}'s hostname and API subdomain, and your runners must allow outbound connections over {% ifversion ghes %}HTTP(S){% else %}HTTPS{% endif %} to {% data variables.product.product_location %}'s hostname and API subdomain. +{% data variables.product.product_name %} must accept inbound connections from your runners over {% ifversion ghes %}HTTP(S){% else %}HTTPS{% endif %} at {% data variables.location.product_location %}'s hostname and API subdomain, and your runners must allow outbound connections over {% ifversion ghes %}HTTP(S){% else %}HTTPS{% endif %} to {% data variables.location.product_location %}'s hostname and API subdomain. {% elsif ghae %} @@ -217,7 +217,7 @@ If you use an IP address allow list for your {% data variables.product.prodname_ {% else %} -{% ifversion ghes %}Self-hosted runners do not require any external internet access in order to function. As a result, you can use network routing to direct communication between the self-hosted runner and {% data variables.product.product_location %}. For example, you can assign a private IP address to your self-hosted runner and configure routing to send traffic to {% data variables.product.product_location %}, with no need for traffic to traverse a public network.{% endif %} +{% ifversion ghes %}Self-hosted runners do not require any external internet access in order to function. As a result, you can use network routing to direct communication between the self-hosted runner and {% data variables.location.product_location %}. For example, you can assign a private IP address to your self-hosted runner and configure routing to send traffic to {% data variables.location.product_location %}, with no need for traffic to traverse a public network.{% endif %} {% endif %} @@ -233,7 +233,7 @@ For more information about troubleshooting common network connectivity issues, s ## Communication between self-hosted runners and {% data variables.product.prodname_dotcom_the_website %} -Self-hosted runners do not need to connect to {% data variables.product.prodname_dotcom_the_website %} unless you have enabled automatic access to {% data variables.product.prodname_dotcom_the_website %} actions for {% data variables.product.product_location %}. For more information, see "[About using actions in your enterprise](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)." +Self-hosted runners do not need to connect to {% data variables.product.prodname_dotcom_the_website %} unless you have enabled automatic access to {% data variables.product.prodname_dotcom_the_website %} actions for {% data variables.location.product_location %}. For more information, see "[About using actions in your enterprise](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)." If you have enabled automatic access to {% data variables.product.prodname_dotcom_the_website %} actions, then the self-hosted runner will connect directly to {% data variables.product.prodname_dotcom_the_website %} to download actions. You must ensure that the machine has the appropriate network access to communicate with the {% data variables.product.prodname_dotcom %} URLs listed below. diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md index 6ea4e15cbd..0e597853c7 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md @@ -1,6 +1,6 @@ --- -title: 对自托管运行程序进行监视和故障排除 -intro: 您可以监控自托管运行器,查看它们的活动并诊断常见问题。 +title: Monitoring and troubleshooting self-hosted runners +intro: You can monitor your self-hosted runners to view their activity and diagnose common issues. redirect_from: - /actions/hosting-your-own-runners/checking-the-status-of-self-hosted-runners - /github/automating-your-workflow-with-github-actions/checking-the-status-of-self-hosted-runners @@ -11,117 +11,119 @@ versions: ghae: '*' ghec: '*' type: tutorial +miniTocMaxHeadingLevel: 3 defaultPlatform: linux shortTitle: Monitor & troubleshoot -ms.openlocfilehash: 57ca9cad51c1936171fcadd73497cf313dd86dd7 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147065632' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## 检查自托管运行器的状态 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## Checking the status of a self-hosted runner {% data reusables.actions.self-hosted-runner-management-permissions-required %} -{% data reusables.actions.self-hosted-runner-navigate-repo-and-org %} {% data reusables.organizations.settings-sidebar-actions-runners %} -1. 在“运行器”下,可以查看已注册运行器的列表,包括运行器的名称、标签和状态。 +{% data reusables.actions.self-hosted-runner-navigate-repo-and-org %} +{% data reusables.organizations.settings-sidebar-actions-runners %} +1. Under "Runners", you can view a list of registered runners, including the runner's name, labels, and status. - 状态可以是下列其中一项: + The status can be one of the following: - * 空闲:运行器已连接到 {% data variables.product.product_name %},并已准备好执行作业。 - * 活动:运行器当前正在执行作业。 - * 脱机:运行器未连接到 {% data variables.product.product_name %}。 这可能是因为机器处于离线状态,自托管运行器应用程序未在机器上运行,或者自托管运行器应用程序无法与 {% data variables.product.product_name %} 通信。 + * **Idle**: The runner is connected to {% data variables.product.product_name %} and is ready to execute jobs. + * **Active**: The runner is currently executing a job. + * **Offline**: The runner is not connected to {% data variables.product.product_name %}. This could be because the machine is offline, the self-hosted runner application is not running on the machine, or the self-hosted runner application cannot communicate with {% data variables.product.product_name %}. -## 网络连接疑难解答 +## Troubleshooting network connectivity -### 检查自托管运行器网络连接 +### Checking self-hosted runner network connectivity -可以结合使用自托管运行器应用程序的 `run` 脚本与 `--check` 参数,以检查自托管运行器是否可以访问 {% data variables.product.product_location %} 上所有必需的网络服务。 +You can use the self-hosted runner application's `run` script with the `--check` parameter to check that a self-hosted runner can access all required network services on {% data variables.location.product_location %}. -除了 `--check` 外,还必须为脚本提供两个参数: +In addition to `--check`, you must provide two arguments to the script: -* `--url`,其中包含指向 {% data variables.product.company_short %} 存储库、组织或企业的 URL。 例如,`--url https://github.com/octo-org/octo-repo`。 -* `--pat`,其中包含必须具有 `workflow` 作用域的个人访问令牌的值。 例如,`--pat ghp_abcd1234`。 有关详细信息,请参阅“[创建个人访问令牌](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)”。 +* `--url` with the URL to your {% data variables.product.company_short %} repository, organization, or enterprise. For example, `--url https://github.com/octo-org/octo-repo`. +* `--pat` with the value of a {% data variables.product.pat_v1 %}, which must have the `workflow` scope{% ifversion pat-v2%}, or a {% data variables.product.pat_v2 %} with workflows read and write access {% endif %}. For example, `--pat ghp_abcd1234`. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." -例如: +For example: {% mac %} {% data reusables.actions.self-hosted-runner-check-mac-linux %} -{% endmac %} {% linux %} +{% endmac %} +{% linux %} {% data reusables.actions.self-hosted-runner-check-mac-linux %} -{% endlinux %} {% windows %} +{% endlinux %} +{% windows %} ```shell -run.cmd --check --url https://github.com/octo-org/octo-repo --pat ghp_abcd1234 +run.cmd --check --url https://github.com/YOUR-ORG/YOUR-REPO --pat GHP_ABCD1234 ``` {% endwindows %} -该脚本测试每项服务,并为每项服务输出 `PASS` 或 `FAIL`。 如有任何失败的检查,您可以在日志文件中看到更多关于问题的详细信息。 日志文件位于安装了运行器应用程序的 `_diag` 目录中,每个检查的日志文件的路径显示在脚本的控制台输出中。 +The script tests each service, and outputs either a `PASS` or `FAIL` for each one. If you have any failing checks, you can see more details on the problem in the log file for the check. The log files are located in the `_diag` directory where you installed the runner application, and the path of the log file for each check is shown in the console output of the script. -如有任何失败的检查,您也应该验证您自己托管的运行器是否符合所有通信要求。 有关详细信息,请参阅[关于自承载运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-requirements)。 +If you have any failing checks, you should also verify that your self-hosted runner machine meets all the communication requirements. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-requirements)." -### 禁用 TLS 证书验证 -{% ifversion ghes %} 默认情况下,自托管运行器应用程序验证 {% data variables.product.product_name %} 的 TLS 证书。 如果您的 {% data variables.product.product_name %} 具有自签名证书或内部颁发的证书,则出于测试目的,您可能希望禁用 TLS 证书验证。 -{% else %} 默认情况下,自托管运行器应用程序验证 {% data variables.product.product_name %} 的 TLS 证书。 如果遇到网络问题,您可能希望禁用 TLS 证书验证以进行测试。 +### Disabling TLS certificate verification +{% ifversion ghes %} +By default, the self-hosted runner application verifies the TLS certificate for {% data variables.product.product_name %}. If your {% data variables.product.product_name %} has a self-signed or internally-issued certificate, you may wish to disable TLS certificate verification for testing purposes. +{% else %} +By default, the self-hosted runner application verifies the TLS certificate for {% data variables.product.product_name %}. If you encounter network problems, you may wish to disable TLS certificate verification for testing purposes. {% endif %} -若要在自托管运行器应用程序中禁用 TLS 证书验证,请在配置和运行自托管运行器应用程序之前将 `GITHUB_ACTIONS_RUNNER_TLS_NO_VERIFY` 环境变量设置为 `1`。 +To disable TLS certification verification in the self-hosted runner application, set the `GITHUB_ACTIONS_RUNNER_TLS_NO_VERIFY` environment variable to `1` before configuring and running the self-hosted runner application. ```shell export GITHUB_ACTIONS_RUNNER_TLS_NO_VERIFY=1 -./config.sh --url https://github.com/octo-org/octo-repo --token +./config.sh --url https://github.com/YOUR-ORG/YOUR-REPO --token ./run.sh ``` {% warning %} -警告:不建议禁用 TLS 验证,因为 TLS 在自托管运行器应用程序和 {% data variables.product.product_name %} 之间提供了隐私和数据完整性。 我们建议您在自托管运行器的操作系统证书存储中安装 {% data variables.product.product_name %} 证书。 有关如何安装 {% data variables.product.product_name %} 证书的指导,请咨询您的操作系统供应商。 +**Warning**: Disabling TLS verification is not recommended since TLS provides privacy and data integrity between the self-hosted runner application and {% data variables.product.product_name %}. We recommend that you install the {% data variables.product.product_name %} certificate in the operating system certificate store for your self-hosted runner. For guidance on how to install the {% data variables.product.product_name %} certificate, check with your operating system vendor. {% endwarning %} -## 查阅自托管运行应用程序日志文件 +## Reviewing the self-hosted runner application log files -您可以监控自托管运行器应用程序的状态及其活动。 日志文件保存在你安装运行器应用程序的 `_diag` 目录中,每次启动应用程序时都会生成新的日志。 文件名开头为 Runner_,后接应用程序启动时的 UTC 时间戳。 +You can monitor the status of the self-hosted runner application and its activities. Log files are kept in the `_diag` directory where you installed the runner application, and a new log is generated each time the application is started. The filename begins with *Runner_*, and is followed by a UTC timestamp of when the application was started. -有关工作流作业执行的详细日志,请参阅介绍 Worker_ 文件的下一节。 +For detailed logs on workflow job executions, see the next section describing the *Worker_* files. -## 查看作业日志文件 +## Reviewing a job's log file -自托管的运行器应用程序为它处理的每个作业创建详细的日志文件。 这些文件存储在安装运行器应用程序的 `_diag` 目录中,文件名以 Worker_ 开头。 +The self-hosted runner application creates a detailed log file for each job that it processes. These files are stored in the `_diag` directory where you installed the runner application, and the filename begins with *Worker_*. {% linux %} -## 使用 journalctl 检查自托管的运行器应用程序服务 +## Using journalctl to check the self-hosted runner application service -对于使用服务运行应用程序的 Linux 自托管运行器,可以使用 `journalctl` 来监视其实时活动。 基于系统的默认服务使用以下命名约定:`actions.runner.-..service`。 此名称在超过 80 个字符时将被截断,因此查找服务名称的首选方式是检查 .service 文件。 例如: +For Linux-based self-hosted runners running the application using a service, you can use `journalctl` to monitor their real-time activity. The default systemd-based service uses the following naming convention: `actions.runner.-..service`. This name is truncated if it exceeds 80 characters, so the preferred way of finding the service's name is by checking the _.service_ file. For example: ```shell $ cat ~/actions-runner/.service actions.runner.octo-org-octo-repo.runner01.service ``` -如果因为服务安装在其他地方而失败,您可以在运行服务列表中找到服务名称。 例如,在大多数 Linux 系统上,可以使用 `systemctl` 命令: +If this fails due to the service being installed elsewhere, you can find the service name in the list of running services. For example, on most Linux systems you can use the `systemctl` command: ```shell $ systemctl --type=service | grep actions.runner actions.runner.octo-org-octo-repo.hostname.service loaded active running GitHub Actions Runner (octo-org-octo-repo.hostname) ``` -可使用 `journalctl` 监视自托管运行器的实时活动: +You can use `journalctl` to monitor the real-time activity of the self-hosted runner: ```shell $ sudo journalctl -u actions.runner.octo-org-octo-repo.runner01.service -f ``` -在此示例输出中,可以看到 `runner01` 启动,接收名为 `testAction` 的作业,然后显示结果状态: +In this example output, you can see `runner01` start, receive a job named `testAction`, and then display the resulting status: ```shell Feb 11 14:57:07 runner01 runsvc.sh[962]: Starting Runner listener with startup type: service @@ -133,23 +135,23 @@ Feb 11 16:06:54 runner01 runsvc.sh[962]: 2020-02-11 16:06:54Z: Running job: test Feb 11 16:07:10 runner01 runsvc.sh[962]: 2020-02-11 16:07:10Z: Job testAction completed with result: Succeeded ``` -若要查看 `systemd` 配置,可在此处找到服务文件:`/etc/systemd/system/actions.runner.-..service`。 -如果您想要自定义自托管的运行器应用程序服务,不要直接修改此文件。 按照“[将自托管运行器应用程序配置为服务](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service)”中所述的说明进行操作。 +To view the `systemd` configuration, you can locate the service file here: `/etc/systemd/system/actions.runner.-..service`. +If you want to customize the self-hosted runner application service, do not directly modify this file. Follow the instructions described in "[Configuring the self-hosted runner application as a service](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service)." {% endlinux %} {% mac %} -## 使用 `launchd` 检查自托管运行器应用程序服务 +## Using `launchd` to check the self-hosted runner application service -对于将应用程序作为服务运行的 macOS 自托管运行器,可以使用 `launchctl` 来监视其实时活动。 基于 launchd 的默认服务使用以下命名约定:`actions.runner.-.`。 此名称在超过 80 个字符时将被截断,因此查找服务名称的首选方式是检查运行器目录中的 .service 文件: +For macOS-based self-hosted runners running the application as a service, you can use `launchctl` to monitor their real-time activity. The default launchd-based service uses the following naming convention: `actions.runner.-.`. This name is truncated if it exceeds 80 characters, so the preferred way of finding the service's name is by checking the _.service_ file in the runner directory: ```shell % cat ~/actions-runner/.service /Users/exampleUsername/Library/LaunchAgents/actions.runner.octo-org-octo-repo.runner01.plist ``` -`svc.sh` 脚本使用 `launchctl` 来检查应用程序是否正在运行。 例如: +The `svc.sh` script uses `launchctl` to check whether the application is running. For example: ```shell $ ./svc.sh status @@ -159,25 +161,25 @@ Started: 379 0 actions.runner.example.runner01 ``` -生成的输出包括进程 ID 和应用程序的 `launchd` 服务的名称。 +The resulting output includes the process ID and the name of the application’s `launchd` service. -若要查看 `launchd` 配置,可在此处找到服务文件:`/Users/exampleUsername/Library/LaunchAgents/actions.runner...service`。 -如果您想要自定义自托管的运行器应用程序服务,不要直接修改此文件。 按照“[将自托管运行器应用程序配置为服务](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service-1)”中所述的说明进行操作。 +To view the `launchd` configuration, you can locate the service file here: `/Users/exampleUsername/Library/LaunchAgents/actions.runner...service`. +If you want to customize the self-hosted runner application service, do not directly modify this file. Follow the instructions described in "[Configuring the self-hosted runner application as a service](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service-1)." {% endmac %} {% windows %} -## 使用 PowerShell 检查自托管的运行器应用程序服务 +## Using PowerShell to check the self-hosted runner application service -对于将应用程序运行为服务的 Windows 自托管运行器,您可以使用 PowerShell 来监控其实时活动。 服务使用命名约定 `GitHub Actions Runner (-.)`。 还可以通过检查运行器目录中的 .service 文件来查找服务的名称: +For Windows-based self-hosted runners running the application as a service, you can use PowerShell to monitor their real-time activity. The service uses the naming convention `GitHub Actions Runner (-.)`. You can also find the service's name by checking the _.service_ file in the runner directory: ```shell PS C:\actions-runner> Get-Content .service actions.runner.octo-org-octo-repo.runner01.service ``` -可以在 Windows 服务应用程序 (`services.msc`) 中查看运行器的状态。 您也可以使用 PowerShell 来检查服务是否在运行: +You can view the status of the runner in the Windows _Services_ application (`services.msc`). You can also use PowerShell to check whether the service is running: ```shell PS C:\actions-runner> Get-Service "actions.runner.octo-org-octo-repo.runner01.service" | Select-Object Name, Status @@ -186,7 +188,7 @@ Name Status actions.runner.octo-org-octo-repo.runner01.service Running ``` -您可以使用 PowerShell 来检查自托管运行器的近期活动。 在此示例输出中,可以看到应用程序启动,接收名为 `testAction` 的作业,然后显示结果状态: +You can use PowerShell to check the recent activity of the self-hosted runner. In this example output, you can see the application start, receive a job named `testAction`, and then display the resulting status: ```shell PS C:\actions-runner> Get-EventLog -LogName Application -Source ActionsRunnerService @@ -205,34 +207,34 @@ PS C:\actions-runner> Get-EventLog -LogName Application -Source ActionsRunnerSer {% endwindows %} -## 监控自动更新过程 +## Monitoring the automatic update process -建议定期检查自动更新过程,因为如果自托管的运行器低于某个版本阈值,将会无法处理作业。 自托管的运行器应用程序自动更新本身,但请注意,此过程不包括对操作系统或其他软件的任何更新;您需要单独管理这些更新。 +We recommend that you regularly check the automatic update process, as the self-hosted runner will not be able to process jobs if it falls below a certain version threshold. The self-hosted runner application automatically updates itself, but note that this process does not include any updates to the operating system or other software; you will need to separately manage these updates. -可以在 Runner_ 日志文件中查看更新活动。 例如: +You can view the update activities in the *Runner_* log files. For example: ```shell [Feb 12 12:37:07 INFO SelfUpdater] An update is available. ``` -此外,还可以在位于安装了运行器应用程序的 `_diag` 目录中的 SelfUpdate 日志文件中找到详细信息。 +In addition, you can find more information in the _SelfUpdate_ log files located in the `_diag` directory where you installed the runner application. {% linux %} -## 自行托管运行器中的容器故障排除 +## Troubleshooting containers in self-hosted runners -### 检查 Docker 是否安装 +### Checking that Docker is installed -如果您的作业需要容器,则自托管的运行器必须基于 Linux,并且需要安装 Docker。 检查自托管运行器是否安装 Docker,以及服务是否正在运行。 +If your jobs require containers, then the self-hosted runner must be Linux-based and needs to have Docker installed. Check that your self-hosted runner has Docker installed and that the service is running. -可以使用 `systemctl` 检查服务状态: +You can use `systemctl` to check the service status: ```shell $ sudo systemctl is-active docker.service active ``` -如果 Docker 未安装,则依赖的操作将因以下错误而失败: +If Docker is not installed, then dependent actions will fail with the following errors: ```shell [2020-02-13 16:56:10Z INFO DockerCommandManager] Which: 'docker' @@ -240,15 +242,15 @@ active [2020-02-13 16:56:10Z ERR StepsRunner] Caught exception from step: System.IO.FileNotFoundException: File not found: 'docker' ``` -### 检查 Docker 权限 +### Checking the Docker permissions -如果作业失败,出现以下错误: +If your job fails with the following error: ```shell dial unix /var/run/docker.sock: connect: permission denied ``` -检查自托管运行器的服务帐户是否有使用 Docker 服务的权限。 可以通过检查 `systemd` 中的自托管运行器的配置来识别此帐户。 例如: +Check that the self-hosted runner's service account has permission to use the Docker service. You can identify this account by checking the configuration of the self-hosted runner in `systemd`. For example: ```shell $ sudo systemctl show -p User actions.runner.octo-org-octo-repo.runner01.service @@ -258,9 +260,26 @@ User=runner-user {% endlinux %} {% ifversion ghes %} -## 解析在 {% data variables.product.product_location %} 升级后处于脱机状态的运行器 +## Resolving runners that are offline after an upgrade of {% data variables.location.product_location %} {% data reusables.actions.upgrade-runners-before-upgrade-ghes %} -如果运行器出于此原因处于脱机状态,请手动更新运行器。 有关详细信息,请参阅操作/运行器存储库中[最新版本](https://github.com/actions/runner/releases/latest)的安装说明。 +If your runners are offline for this reason, manually update the runners. For more information, see the installation instructions for [the latest release](https://github.com/actions/runner/releases/latest) in the actions/runner repository. {% endif %} + +### Checking which Docker engine is installed on the runner + +If your build fails with the following error: + +```shell +Error: Input required and not supplied: java-version +``` + +Check which Docker engine is installed on your self-hosted runner. To pass the inputs of an action into the Docker container, the runner uses environment variables that might contain dashes as part of their names. The action may not able to get the inputs if the Docker engine is not a binary executable, but is instead a shell wrapper or a link (for example, a Docker engine installed on Linux using `snap`). To address this error, configure your self-hosted runner to use a different Docker engine. + +To check if your Docker engine was installed using `snap`, use the `which` command. In the following example, the Docker engine was installed using `snap`: + +```shell +$ which docker +/snap/bin/docker +``` diff --git a/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md index da677ef353..c839f81150 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md @@ -33,7 +33,7 @@ topics: {% elsif ghes or ghae %} -You must host your own Linux, Windows, or macOS virtual machines to run workflows for {% data variables.product.product_location %}. {% data reusables.actions.self-hosted-runner-locations %} +You must host your own Linux, Windows, or macOS virtual machines to run workflows for {% data variables.location.product_location %}. {% data reusables.actions.self-hosted-runner-locations %} {% endif %} diff --git a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md index e0b77637e3..84c4fdbf19 100644 --- a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md +++ b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md @@ -1,6 +1,6 @@ --- -title: 在项目板上移动分配的议题 -intro: '您可以使用 {% data variables.product.prodname_actions %} 在议题被分配时自动将议题移到项目板上的特定列。' +title: Moving assigned issues on project boards +intro: 'You can use {% data variables.product.prodname_actions %} to automatically move an issue to a specific column on a project board when the issue is assigned.' redirect_from: - /actions/guides/moving-assigned-issues-on-project-boards versions: @@ -13,27 +13,23 @@ topics: - Workflows - Project management shortTitle: Move assigned issues -ms.openlocfilehash: 88cec7ca6f2e7774fb29407b0b3ee14dc7041067 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147410457' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## 简介 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} -本教程演示如何在分配问题时使用 [`alex-page/github-project-automation-plus` 操作](https://github.com/marketplace/actions/github-project-automation)自动将问题移至项目板上的特定列。 例如,分配问题后,可以将其移动到项目板的 `In Progress` 列中。 +## Introduction -在本教程中,你将首先创建一个使用 [`alex-page/github-project-automation-plus` 操作](https://github.com/marketplace/actions/github-project-automation)的工作流文件。 然后,您将自定义工作流以适应您的需要。 +This tutorial demonstrates how to use the [`alex-page/github-project-automation-plus` action](https://github.com/marketplace/actions/github-project-automation) to automatically move an issue to a specific column on a project board when the issue is assigned. For example, when an issue is assigned, you can move it into the `In Progress` column your project board. -## 创建工作流程 +In the tutorial, you will first make a workflow file that uses the [`alex-page/github-project-automation-plus` action](https://github.com/marketplace/actions/github-project-automation). Then, you will customize the workflow to suit your needs. + +## Creating the workflow 1. {% data reusables.actions.choose-repo %} -2. 在仓库中,选择项目板。 您可以使用现有项目,也可以创建新项目。 有关如何创建项目的详细信息,请参阅“[创建项目板](/github/managing-your-work-on-github/creating-a-project-board)”。 +2. In your repository, choose a project board. You can use an existing project, or you can create a new project. For more information about creating a project, see "[Creating a project board](/github/managing-your-work-on-github/creating-a-project-board)." 3. {% data reusables.actions.make-workflow-file %} -4. 将以下 YAML 内容复制到工作流程文件中。 +4. Copy the following YAML contents into your workflow file. ```yaml{:copy} {% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %} @@ -56,28 +52,28 @@ ms.locfileid: '147410457' repo-token: {% raw %}${{ secrets.PERSONAL_ACCESS_TOKEN }}{% endraw %} ``` -5. 自定义工工作流程文件中的参数: - - 将 `project` 的值更改为项目板的名称。 如果有多个同名项目板,则 `alex-page/github-project-automation-plus` 操作将对具有指定名称的所有项目执行操作。 - - 将 `column` 的值更改为要在分配问题时将其移动到的列的名称。 - - 更改 `repo-token` 的值: - 1. 创建具有 `repo` 作用域的个人访问令牌。 有关详细信息,请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 - 1. 将此个人访问令牌作为机密存储在仓库中。 有关如何存储机密的详细信息,请参阅“[已加密的机密](/actions/reference/encrypted-secrets)”。 - 1. 在工作流文件中,将 `PERSONAL_ACCESS_TOKEN` 替换为机密的名称。 +5. Customize the parameters in your workflow file: + - Change the value for `project` to the name of your project board. If you have multiple project boards with the same name, the `alex-page/github-project-automation-plus` action will act on all projects with the specified name. + - Change the value for `column` to the name of the column where you want issues to move when they are assigned. + - Change the value for `repo-token`: + 1. Create a {% data variables.product.pat_v1 %} with the `repo` scope. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." + 1. Store this {% data variables.product.pat_generic %} as a secret in your repository. For more information about storing secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)." + 1. In your workflow file, replace `PERSONAL_ACCESS_TOKEN` with the name of your secret. 6. {% data reusables.actions.commit-workflow %} -## 测试工作流程 +## Testing the workflow -每当分配仓库中的议题时,议题将移到指定的项目板列。 如果议题尚未在项目板上,则将添加到项目板中。 +Whenever an issue in your repository is assigned, the issue will be moved to the specified project board column. If the issue is not already on the project board, it will be added to the project board. -如果存储库是用户拥有的存储库,则 `alex-page/github-project-automation-plus` 操作将对存储库或个人帐户中具有指定项目名称和列的所有项目执行操作。 同样,如果您的仓库归组织所有,则该操作将对仓库或组织中具有指定项目名称和列的所有项目执行。 +If your repository is user-owned, the `alex-page/github-project-automation-plus` action will act on all projects in your repository or personal account that have the specified project name and column. Likewise, if your repository is organization-owned, the action will act on all projects in your repository or organization that have the specified project name and column. -通过在仓库中分配议题来测试工作流程。 +Test your workflow by assigning an issue in your repository. -1. 在仓库中打开一个议题。 有关详细信息,请参阅“[创建问题](/github/managing-your-work-on-github/creating-an-issue)”。 -2. 分配议题。 有关详细信息,请参阅“[向其他 GitHub 用户分配问题并拉取请求](/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users)”。 -3. 要查看分配议题所触发的工作流程运行,请查看工作流程运行的历史记录。 有关详细信息,请参阅“[查看工作流运行历史记录](/actions/managing-workflow-runs/viewing-workflow-run-history)”。 -4. 工作流程完成后,分配的议题应会添加到指定的项目板列中。 +1. Open an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)." +2. Assign the issue. For more information, see "[Assigning issues and pull requests to other GitHub users](/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users)." +3. To see the workflow run that assigning the issue triggered, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)." +4. When the workflow completes, the issue that you assigned should be added to the specified project board column. -## 后续步骤 +## Next steps -- 若要详细了解可使用 `alex-page/github-project-automation-plus` 操作执行的其他操作,例如删除或存档项目卡,请访问[`alex-page/github-project-automation-plus`操作文档](https://github.com/marketplace/actions/github-project-automation)。 +- To learn more about additional things you can do with the `alex-page/github-project-automation-plus` action, like deleting or archiving project cards, visit the [`alex-page/github-project-automation-plus` action documentation](https://github.com/marketplace/actions/github-project-automation). diff --git a/translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md b/translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md index 908764eb17..34ccc87811 100644 --- a/translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md +++ b/translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md @@ -115,7 +115,7 @@ If you do provide the `repository` key in your *package.json* file, then the rep To perform authenticated operations against the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN`. {% data reusables.actions.github-token-permissions %} -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)." +If you want to publish your package to a different repository, you must use a {% data variables.product.pat_v1 %} that has permission to write to packages in the destination repository. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)." ### Example workflow diff --git a/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md b/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md index 34239bf6e5..a7a52992a7 100644 --- a/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md +++ b/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md @@ -117,9 +117,9 @@ The permissions for the `GITHUB_TOKEN` are initially set to the default setting ### Granting additional permissions -If you need a token that requires permissions that aren't available in the `GITHUB_TOKEN`, you can create a personal access token and set it as a secret in your repository: +If you need a token that requires permissions that aren't available in the `GITHUB_TOKEN`, you can create a {% data variables.product.pat_generic %} and set it as a secret in your repository: -1. Use or create a token with the appropriate permissions for that repository. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +1. Use or create a token with the appropriate permissions for that repository. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." 1. Add the token as a secret in your workflow's repository, and refer to it using the {%raw%}`${{ secrets.SECRET_NAME }}`{% endraw %} syntax. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." ### Further reading diff --git a/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md b/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md index e678c2474c..cd8cf7b99a 100644 --- a/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md +++ b/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md @@ -60,7 +60,7 @@ You can also manage secrets using the REST API. For more information, see "[Secr ### Limiting credential permissions -When generating credentials, we recommend that you grant the minimum permissions possible. For example, instead of using personal credentials, use [deploy keys](/developers/overview/managing-deploy-keys#deploy-keys) or a service account. Consider granting read-only permissions if that's all that is needed, and limit access as much as possible. When generating a personal access token (PAT), select the fewest scopes necessary. +When generating credentials, we recommend that you grant the minimum permissions possible. For example, instead of using personal credentials, use [deploy keys](/developers/overview/managing-deploy-keys#deploy-keys) or a service account. Consider granting read-only permissions if that's all that is needed, and limit access as much as possible. When generating a {% data variables.product.pat_v1 %}, select the fewest scopes necessary.{% ifversion pat-v2 %} When generating a {% data variables.product.pat_v2 %}, select the minimum repository access required.{% endif %} {% note %} diff --git a/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md index 9b7fb1a826..5a18705739 100644 --- a/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md @@ -261,11 +261,11 @@ This list describes the recommended approaches for accessing repository data wit - Note that deploy keys can only clone and push to the repository using Git, and cannot be used to interact with the REST or GraphQL API, so they may not be appropriate for your requirements. 3. **{% data variables.product.prodname_github_app %} tokens** - {% data variables.product.prodname_github_apps %} can be installed on select repositories, and even have granular permissions on the resources within them. You could create a {% data variables.product.prodname_github_app %} internal to your organization, install it on the repositories you need access to within your workflow, and authenticate as the installation within your workflow to access those repositories. -4. **Personal access tokens** - - You should never use personal access tokens from your own account. These tokens grant access to all repositories within the organizations that you have access to, as well as all personal repositories in your personal account. This indirectly grants broad access to all write-access users of the repository the workflow is in. In addition, if you later leave an organization, workflows using this token will immediately break, and debugging this issue can be challenging. - - If a personal access token is used, it should be one that was generated for a new account that is only granted access to the specific repositories that are needed for the workflow. Note that this approach is not scalable and should be avoided in favor of alternatives, such as deploy keys. +4. **{% data variables.product.pat_generic %}s** + - You should never use a {% data variables.product.pat_v1 %}. These tokens grant access to all repositories within the organizations that you have access to, as well as all personal repositories in your personal account. This indirectly grants broad access to all write-access users of the repository the workflow is in. + - If you do use a {% data variables.product.pat_generic %}, you should never use a {% data variables.product.pat_generic %} from your own account. If you later leave an organization, workflows using this token will immediately break, and debugging this issue can be challenging. Instead, you should use a {% ifversion pat-v2%}{% data variables.product.pat_v2 %}s{% else %}{% data variables.product.pat_generic %}s{% endif %} for a new account that belongs to your organization and that is only granted access to the specific repositories that are needed for the workflow. Note that this approach is not scalable and should be avoided in favor of alternatives, such as deploy keys. 5. **SSH keys on a personal account** - - Workflows should never use the SSH keys on a personal account. Similar to personal access tokens, they grant read/write permissions to all of your personal repositories as well as all the repositories you have access to through organization membership. This indirectly grants broad access to all write-access users of the repository the workflow is in. If you're intending to use an SSH key because you only need to perform repository clones or pushes, and do not need to interact with public APIs, then you should use individual deploy keys instead. + - Workflows should never use the SSH keys on a personal account. Similar to {% data variables.product.pat_v1_plural %}, they grant read/write permissions to all of your personal repositories as well as all the repositories you have access to through organization membership. This indirectly grants broad access to all write-access users of the repository the workflow is in. If you're intending to use an SSH key because you only need to perform repository clones or pushes, and do not need to interact with public APIs, then you should use individual deploy keys instead. ## Hardening for self-hosted runners diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index 16defd8a7e..d47babe64e 100644 --- a/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -90,7 +90,7 @@ While the job runs, the logs and output can be viewed in the {% data variables.p {% note %} -**Note**: {% data variables.product.prodname_dotcom %} also offers {% data variables.actions.hosted_runner %}s, which are available in larger configurations. For more information, see "[Using {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/using-larger-runners)." +**Note**: {% data variables.product.prodname_dotcom %} also offers {% data variables.actions.hosted_runner %}s, which are available in larger configurations. For more information, see "[Machine specs for {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/using-larger-runners#machine-specs-for-larger-runners)." {% endnote %} {% endif %} diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/using-larger-runners.md b/translations/zh-CN/content/actions/using-github-hosted-runners/using-larger-runners.md index e3251b78a6..d4f33140a6 100644 --- a/translations/zh-CN/content/actions/using-github-hosted-runners/using-larger-runners.md +++ b/translations/zh-CN/content/actions/using-github-hosted-runners/using-larger-runners.md @@ -14,6 +14,16 @@ In addition to the [standard {% data variables.product.prodname_dotcom %}-hosted When you add a {% data variables.actions.hosted_runner %} to an organization, you are defining a type of machine from a selection of available hardware specifications and operating system images. {% data variables.product.prodname_dotcom %} will then create multiple instances of this runner that scale up and down to match the job demands of your organization, based on the autoscaling limits you define. +## Machine specs for {% data variables.actions.hosted_runner %}s + +|Size (vcpu) | Memory (GB) | Storage (SSD) | +| ------------- | ------------- | ------------- | +|4 cores | 16 RAM | 150 GB| +| 8 cores | 32 RAM | 300 GB | +|16 cores| 64 RAM | 600 GB | +|32 cores| 128 RAM| 1200 GB| +|64 cores| 256 RAM | 2040 GB| + ## Architectural overview of {% data variables.actions.hosted_runner %}s The {% data variables.actions.hosted_runner %}s are managed at the organization level, where they are arranged into groups that can contain multiple instances of the runner. They can also be created at the enterprise level and shared with organizations in the hierarchy. Once you've created a group, you can then add a runner to the group and update your workflows to target the label assigned to the {% data variables.actions.hosted_runner %}. You can also control which repositories are permitted to send jobs to the group for processing. For more information about groups, see "[Controlling access to {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/controlling-access-to-larger-runners)." diff --git a/translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md b/translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md index 52a8fc5cf1..fa4f441d04 100644 --- a/translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md +++ b/translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md @@ -1264,7 +1264,7 @@ on: workflow_call | Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | | ------------------ | ------------ | ------------ | ------------------| -| [workflow_dispatch](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#workflow_dispatch) | n/a | Last commit on the `GITHUB_REF` branch | Branch that received dispatch | +| [workflow_dispatch](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#workflow_dispatch) | n/a | Last commit on the `GITHUB_REF` branch or tag | Branch or tag that received dispatch | To manually trigger a workflow, use the `workflow_dispatch` event. You can manually trigger a workflow run using the {% data variables.product.product_name %} API, {% data variables.product.prodname_cli %}, or {% data variables.product.product_name %} browser interface. For more information, see "[Manually running a workflow](/actions/managing-workflow-runs/manually-running-a-workflow)." diff --git a/translations/zh-CN/content/actions/using-workflows/reusing-workflows.md b/translations/zh-CN/content/actions/using-workflows/reusing-workflows.md index 79095d002c..7186ebf265 100644 --- a/translations/zh-CN/content/actions/using-workflows/reusing-workflows.md +++ b/translations/zh-CN/content/actions/using-workflows/reusing-workflows.md @@ -76,7 +76,7 @@ Called workflows that are owned by the same user or organization{% ifversion ghe ## Limitations {% ifversion nested-reusable-workflow %} -* You can connect up to four levels of workflows. For more information, see "[Calling a nested reusable workflow](#calling-a-nested-reusable-workflow)." +* You can connect up to four levels of workflows. For more information, see "[Nesting reusable workflows](#nesting-reusable-workflows)." {% else %} * Reusable workflows can't call other reusable workflows. {% endif %} diff --git a/translations/zh-CN/content/actions/using-workflows/storing-workflow-data-as-artifacts.md b/translations/zh-CN/content/actions/using-workflows/storing-workflow-data-as-artifacts.md index feb37bfee4..0be100e2ea 100644 --- a/translations/zh-CN/content/actions/using-workflows/storing-workflow-data-as-artifacts.md +++ b/translations/zh-CN/content/actions/using-workflows/storing-workflow-data-as-artifacts.md @@ -1,7 +1,7 @@ --- -title: 将工作流程数据存储为构件 -shortTitle: Storing workflow artifacts -intro: 构件允许您在工作流程完成后,分享工作流程中作业之间的数据并存储数据。 +title: Storing workflow data as artifacts +shortTitle: Store artifacts +intro: Artifacts allow you to share data between jobs in a workflow and store data once that workflow has completed. redirect_from: - /articles/persisting-workflow-data-using-artifacts - /github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts @@ -17,68 +17,64 @@ versions: type: tutorial topics: - Workflows -ms.openlocfilehash: d23b62f1e77fd08fd798f4fb1af9f44e4d1b1123 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146179733' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## 关于工作流程构件 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} -构件允许您在作业完成后保留数据,并与同一工作流程中的另一个作业共享该数据。 构件是指在工作流程运行过程中产生的文件或文件集。 例如,在工作流程运行结束后,您可以使用构件保存您的构建和测试输出。 {% data reusables.actions.reusable-workflow-artifacts %} +## About workflow artifacts -{% data reusables.actions.artifact-log-retention-statement %} 每当有人向拉取请求推送新提交时,拉取请求的保留期都会重新开始计算。 +Artifacts allow you to persist data after a job has completed, and share that data with another job in the same workflow. An artifact is a file or collection of files produced during a workflow run. For example, you can use artifacts to save your build and test output after a workflow run has ended. {% data reusables.actions.reusable-workflow-artifacts %} -以下是您可以上传的一些常见构件: +{% data reusables.actions.artifact-log-retention-statement %} The retention period for a pull request restarts each time someone pushes a new commit to the pull request. -- 日志文件和核心转储文件 -- 测试结果、失败和屏幕截图 -- 二进制或压缩文件 -- 压力测试性能输出和代码覆盖结果 +These are some of the common artifacts that you can upload: + +- Log files and core dumps +- Test results, failures, and screenshots +- Binary or compressed files +- Stress test performance output and code coverage results {% ifversion fpt or ghec %} -存储构件时使用存储空间 {% data variables.product.product_name %}。 {% data reusables.actions.actions-billing %} 有关详细信息,请参阅“[{% data variables.product.prodname_actions %} 的计费](/billing/managing-billing-for-github-actions)”。 +Storing artifacts uses storage space on {% data variables.product.product_name %}. {% data reusables.actions.actions-billing %} For more information, see "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)." {% else %} -项目会占用外部 Blob 存储上的存储空间,该存储为 {% data variables.product.product_location %} 上的 {% data variables.product.prodname_actions %} 配置。 +Artifacts consume storage space on the external blob storage that is configured for {% data variables.product.prodname_actions %} on {% data variables.location.product_location %}. {% endif %} -构件会在工作流程运行过程中上传,您可以在 UI 中查看构件的名称和大小。 当构件使用 {% data variables.product.product_name %} UI 下载时, 作为构件一部分单独上传的所有文件都会压缩到一个 zip 文件中。 这意味着计费是根据上传的构件大小而不是 zip 文件的大小计算的。 +Artifacts are uploaded during a workflow run, and you can view an artifact's name and size in the UI. When an artifact is downloaded using the {% data variables.product.product_name %} UI, all files that were individually uploaded as part of the artifact get zipped together into a single file. This means that billing is calculated based on the size of the uploaded artifact and not the size of the zip file. -{% data variables.product.product_name %} 提供两项可用于上传和下载构建构件的操作。 有关详细信息,请参阅 {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) 和 [download-artifact](https://github.com/actions/download-artifact) 操作{% else %} {% data variables.product.product_location %} 上的 `actions/upload-artifact` 和 `download-artifact` 操作{% endif %}。 +{% data variables.product.product_name %} provides two actions that you can use to upload and download build artifacts. For more information, see the {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) and [download-artifact](https://github.com/actions/download-artifact) actions{% else %} `actions/upload-artifact` and `download-artifact` actions on {% data variables.location.product_location %}{% endif %}. -要在作业之间共享数据: +To share data between jobs: -* **上传文件**:为上传的文件指定一个名称,并在作业结束前上传数据。 -* **下载文件**:只能下载在同一工作流运行期间上传的工件。 下载文件时,您可以通过名称引用该文件。 +* **Uploading files**: Give the uploaded file a name and upload the data before the job ends. +* **Downloading files**: You can only download artifacts that were uploaded during the same workflow run. When you download a file, you can reference it by name. -作业步骤共享运行器机器的相同环境,但在其各自的进程中运行。 要在作业的步骤之间传递数据,您可以使用输入和输出。 有关输入和输出的详细信息,请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/articles/metadata-syntax-for-github-actions)”。 +The steps of a job share the same environment on the runner machine, but run in their own individual processes. To pass data between steps in a job, you can use inputs and outputs. For more information about inputs and outputs, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions)." {% ifversion actions-caching %} {% data reusables.actions.comparing-artifacts-caching %} -有关依赖项缓存的详细信息,请参阅“[缓存依赖项以加快工作流](/actions/using-workflows/caching-dependencies-to-speed-up-workflows#comparing-artifacts-and-dependency-caching)”。 +For more information on dependency caching, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows#comparing-artifacts-and-dependency-caching)." {% endif %} -## 上传构建和测试构件 +## Uploading build and test artifacts -您可以创建持续集成 (CI) 工作流程来构建和测试您的代码。 有关使用 {% data variables.product.prodname_actions %} 执行 CI 的详细信息,请参阅“[关于持续集成](/articles/about-continuous-integration)”。 +You can create a continuous integration (CI) workflow to build and test your code. For more information about using {% data variables.product.prodname_actions %} to perform CI, see "[About continuous integration](/articles/about-continuous-integration)." -构建和测试代码的输出通常会生成可用于调试测试失败的文件和可部署的生产代码。 您可以配置一个工作流程来构建和测试推送到仓库中的代码,并报告成功或失败状态。 您可以上传构建和测试输出,以用于部署、调试失败的测试或崩溃以及查看测试套件范围。 +The output of building and testing your code often produces files you can use to debug test failures and production code that you can deploy. You can configure a workflow to build and test the code pushed to your repository and report a success or failure status. You can upload the build and test output to use for deployments, debugging failed tests or crashes, and viewing test suite coverage. -可以使用 `upload-artifact` 操作上传工件。 上传构件时,您可以指定单个文件或目录,或多个文件或目录。 您还可以排除某些文件或目录,以及使用通配符模式。 建议为工件命名,如果没有命名,则会使用 `artifact` 作为默认名称。 有关语法的详细信息,请参阅 {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) 操作{% else %} {% data variables.product.product_location %} 上的 `actions/upload-artifact` 操作{% endif %}。 +You can use the `upload-artifact` action to upload artifacts. When uploading an artifact, you can specify a single file or directory, or multiple files or directories. You can also exclude certain files or directories, and use wildcard patterns. We recommend that you provide a name for an artifact, but if no name is provided then `artifact` will be used as the default name. For more information on syntax, see the {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) action{% else %} `actions/upload-artifact` action on {% data variables.location.product_location %}{% endif %}. -### 示例 +### Example -例如,您的仓库或 Web 应用程序可能包含必须转换为 CSS 和 JavaScript 的 SASS 和 TypeScript 文件。 假设生成配置输出 `dist` 目录中已编译的文件,如果所有测试均已成功完成,则可将 `dist` 目录中的文件部署到 Web 应用服务器。 +For example, your repository or a web application might contain SASS and TypeScript files that you must convert to CSS and JavaScript. Assuming your build configuration outputs the compiled files in the `dist` directory, you would deploy the files in the `dist` directory to your web application server if all tests completed successfully. ``` |-- hello-world (repository) @@ -92,9 +88,9 @@ ms.locfileid: '146179733' | ``` -此示例演示了如何创建 Node.js 项目的工作流,该项目在 `src` 目录中生成代码,在 `tests` 目录中运行测试。 可以假定运行 `npm test` 会生成一个名为 `code-coverage.html`、存储在 `output/test/` 目录中的代码覆盖率报告。 +This example shows you how to create a workflow for a Node.js project that builds the code in the `src` directory and runs the tests in the `tests` directory. You can assume that running `npm test` produces a code coverage report named `code-coverage.html` stored in the `output/test/` directory. -工作流上传 `dist` 目录中的生产工件,但不包括任何 Markdown 文件。 它还将 `code-coverage.html` 报表作为另一个工件上传。 +The workflow uploads the production artifacts in the `dist` directory, but excludes any markdown files. It also uploads the `code-coverage.html` report as another artifact. ```yaml{:copy} name: Node CI @@ -126,9 +122,9 @@ jobs: path: output/test/code-coverage.html ``` -## 配置自定义构件保留期 +## Configuring a custom artifact retention period -您可以为工作流程创建的单个构件自定义保留期。 使用工作流创建新工件时,可以同时使用 `retention-days` 和 `upload-artifact` 操作。 此示例演示如何为名为 `my-artifact` 的工件设置 5 天的自定义保留期: +You can define a custom retention period for individual artifacts created by a workflow. When using a workflow to create a new artifact, you can use `retention-days` with the `upload-artifact` action. This example demonstrates how to set a custom retention period of 5 days for the artifact named `my-artifact`: ```yaml{:copy} - name: 'Upload Artifact' @@ -139,25 +135,25 @@ jobs: retention-days: 5 ``` -`retention-days` 值不能超过存储库、组织或企业设置的保留限制。 +The `retention-days` value cannot exceed the retention limit set by the repository, organization, or enterprise. -## 下载或删除构件 +## Downloading or deleting artifacts -在工作流运行期间,可以使用 [`download-artifact`](https://github.com/actions/download-artifact) 操作下载以前在同一工作流运行中上传的工件。 +During a workflow run, you can use the [`download-artifact`](https://github.com/actions/download-artifact) action to download artifacts that were previously uploaded in the same workflow run. -工作流程运行完成后,您可以在 {% data variables.product.prodname_dotcom %} 上或使用 REST API 下载或删除构件。 有关详细信息,请参阅“[下载工作流工件](/actions/managing-workflow-runs/downloading-workflow-artifacts)”、“[删除工作流工件](/actions/managing-workflow-runs/removing-workflow-artifacts)”和“[工件 REST API](/rest/reference/actions#artifacts)”。 +After a workflow run has been completed, you can download or delete artifacts on {% data variables.product.prodname_dotcom %} or using the REST API. For more information, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)," "[Removing workflow artifacts](/actions/managing-workflow-runs/removing-workflow-artifacts)," and the "[Artifacts REST API](/rest/reference/actions#artifacts)." -### 在工作流程运行期间下载构件 +### Downloading artifacts during a workflow run -[`actions/download-artifact`](https://github.com/actions/download-artifact) 操作可用于在工作流运行期间下载以前上传的工件。 +The [`actions/download-artifact`](https://github.com/actions/download-artifact) action can be used to download previously uploaded artifacts during a workflow run. {% note %} -注意:只能下载在同一工作流运行期间上传的工作流中的工件。 +**Note:** You can only download artifacts in a workflow that were uploaded during the same workflow run. {% endnote %} -指定构件的名称以下载单个构件。 如果在未指定名称的情况下上传了工件,则默认名称为 `artifact`。 +Specify an artifact's name to download an individual artifact. If you uploaded an artifact without specifying a name, the default name is `artifact`. ```yaml - name: Download a single artifact @@ -166,37 +162,37 @@ jobs: name: my-artifact ``` -您还可以不指定名称而下载工作流程运行中的所有构件。 如果您在处理大量构件,此功能非常有用。 +You can also download all artifacts in a workflow run by not specifying a name. This can be useful if you are working with lots of artifacts. ```yaml - name: Download all workflow run artifacts uses: {% data reusables.actions.action-download-artifact %} ``` -如果下载所有工作流运行的工件,则会为每个工件使用其名称创建一个目录。 +If you download all workflow run's artifacts, a directory for each artifact is created using its name. -有关语法的详细信息,请参阅 {% ifversion fpt or ghec %}[actions/download-artifact](https://github.com/actions/download-artifact) 操作{% else %} {% data variables.product.product_location %} 上的 `actions/download-artifact` 操作{% endif %}。 +For more information on syntax, see the {% ifversion fpt or ghec %}[actions/download-artifact](https://github.com/actions/download-artifact) action{% else %} `actions/download-artifact` action on {% data variables.location.product_location %}{% endif %}. -## 在工作流中的作业间传递数据 +## Passing data between jobs in a workflow -可以使用 `upload-artifact` 和 `download-artifact` 操作在工作流中的作业间共享数据。 此示例工作流程说明如何在相同工作流程中的任务之间传递数据。 有关详细信息,请参阅 {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) 和 [download-artifact](https://github.com/actions/download-artifact) 操作{% else %} {% data variables.product.product_location %} 上的 `actions/upload-artifact` 和 `download-artifact` 操作{% endif %}。 +You can use the `upload-artifact` and `download-artifact` actions to share data between jobs in a workflow. This example workflow illustrates how to pass data between jobs in the same workflow. For more information, see the {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) and [download-artifact](https://github.com/actions/download-artifact) actions{% else %} `actions/upload-artifact` and `download-artifact` actions on {% data variables.location.product_location %}{% endif %}. -依赖于以前作业构件的作业必须等待依赖项成功完成。 此工作流使用 `needs` 密钥来确保 `job_1`、`job_2` 和 `job_3` 按顺序运行。 例如,`job_2` 需要 `job_1`,方法是使用 `needs: job_1` 语法。 +Jobs that are dependent on a previous job's artifacts must wait for the dependent job to complete successfully. This workflow uses the `needs` keyword to ensure that `job_1`, `job_2`, and `job_3` run sequentially. For example, `job_2` requires `job_1` using the `needs: job_1` syntax. -作业1执行以下步骤: -- 执行数学计算并将结果保存到名为 `math-homework.txt` 的文本文件。 -- 使用 `upload-artifact` 操作上传工件名称为 `homework` 的 `math-homework.txt` 文件。 +Job 1 performs these steps: +- Performs a math calculation and saves the result to a text file called `math-homework.txt`. +- Uses the `upload-artifact` action to upload the `math-homework.txt` file with the artifact name `homework`. -作业 2 使用上一个作业的结果: -- 下载在上一作业中上传的 `homework` 工件。 默认情况下,`download-artifact` 操作会将工件下载到该步骤执行的工作区目录中。 可以使用 `path` 输入参数指定不同的下载目录。 -- 读取 `math-homework.txt` 文件中的值,执行数学计算,并再次将结果保存到 `math-homework.txt`,覆盖其内容。 -- 上传 `math-homework.txt` 文件。 此上传会覆盖之前上传的构件,因为它们共用同一名称。 +Job 2 uses the result in the previous job: +- Downloads the `homework` artifact uploaded in the previous job. By default, the `download-artifact` action downloads artifacts to the workspace directory that the step is executing in. You can use the `path` input parameter to specify a different download directory. +- Reads the value in the `math-homework.txt` file, performs a math calculation, and saves the result to `math-homework.txt` again, overwriting its contents. +- Uploads the `math-homework.txt` file. This upload overwrites the previously uploaded artifact because they share the same name. -作业 3 显示上一个作业中上传的结果: -- 下载 `homework` 工件。 -- 将数学方程式的结果打印到日志中。 +Job 3 displays the result uploaded in the previous job: +- Downloads the `homework` artifact. +- Prints the result of the math equation to the log. -在此工作流示例中执行的完整数学运算是 `(3 + 7) x 9 = 90`。 +The full math operation performed in this workflow example is `(3 + 7) x 9 = 90`. ```yaml{:copy} name: Share data between jobs @@ -252,13 +248,13 @@ jobs: echo The result is $value ``` -工作流程运行运行将会存档它生成的任何构件。 有关下载已存档工件的详细信息,请参阅“[下载工作流工件](/actions/managing-workflow-runs/downloading-workflow-artifacts)”。 -![在作业间传递数据以执行数学运算的工作流](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) +The workflow run will archive any artifacts that it generated. For more information on downloading archived artifacts, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)." +![Workflow that passes data between jobs to perform math](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) {% ifversion fpt or ghec %} -## 延伸阅读 +## Further reading -- “[管理 {% data variables.product.prodname_actions %} 的计费](/billing/managing-billing-for-github-actions)”。 +- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)". {% endif %} diff --git a/translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md b/translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md index c0c7429ee7..8e4adb430f 100644 --- a/translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md +++ b/translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md @@ -36,9 +36,9 @@ The following steps occur to trigger a workflow run: {% data reusables.actions.actions-do-not-trigger-workflows %} For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)." -If you do want to trigger a workflow from within a workflow run, you can use a personal access token instead of `GITHUB_TOKEN` to trigger events that require a token. You'll need to create a personal access token and store it as a secret. To minimize your {% data variables.product.prodname_actions %} usage costs, ensure that you don't create recursive or unintended workflow runs. For more information about creating a personal access token, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about storing a personal access token as a secret, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)." +If you do want to trigger a workflow from within a workflow run, you can use a {% data variables.product.pat_generic %} instead of `GITHUB_TOKEN` to trigger events that require a token. You'll need to create a {% data variables.product.pat_generic %} and store it as a secret. To minimize your {% data variables.product.prodname_actions %} usage costs, ensure that you don't create recursive or unintended workflow runs. For more information about creating a {% data variables.product.pat_generic %}, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about storing a {% data variables.product.pat_generic %} as a secret, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)." -For example, the following workflow uses a personal access token (stored as a secret called `MY_TOKEN`) to add a label to an issue via {% data variables.product.prodname_cli %}. Any workflows that run when a label is added will run once this step is performed. +For example, the following workflow uses a {% data variables.product.pat_generic %} (stored as a secret called `MY_TOKEN`) to add a label to an issue via {% data variables.product.prodname_cli %}. Any workflows that run when a label is added will run once this step is performed. ```yaml on: diff --git a/translations/zh-CN/content/actions/using-workflows/workflow-commands-for-github-actions.md b/translations/zh-CN/content/actions/using-workflows/workflow-commands-for-github-actions.md index 4aaef727ee..190fb29822 100644 --- a/translations/zh-CN/content/actions/using-workflows/workflow-commands-for-github-actions.md +++ b/translations/zh-CN/content/actions/using-workflows/workflow-commands-for-github-actions.md @@ -148,12 +148,12 @@ The following table shows which toolkit functions are available within a workflo | `core.getState` | Accessible using environment variable `STATE_{NAME}` | | `core.isDebug` | Accessible using environment variable `RUNNER_DEBUG` | {%- ifversion actions-job-summaries %} -| `core.summary` | Accessible using environment variable `GITHUB_STEP_SUMMARY` | +| `core.summary` | Accessible using environment file `GITHUB_STEP_SUMMARY` | {%- endif %} -| `core.saveState` | {% ifversion actions-save-state-set-output-envs %}Accessible using environment variable `GITHUB_STATE`{% else %}`save-state`{% endif %} | +| `core.saveState` | {% ifversion actions-save-state-set-output-envs %}Accessible using environment file `GITHUB_STATE`{% else %}`save-state`{% endif %} | | `core.setCommandEcho` | `echo` | | `core.setFailed` | Used as a shortcut for `::error` and `exit 1` | -| `core.setOutput` | {% ifversion actions-save-state-set-output-envs %}Accessible using environment variable `GITHUB_OUTPUT`{% else %}`set-output`{% endif %} | +| `core.setOutput` | {% ifversion actions-save-state-set-output-envs %}Accessible using environment file `GITHUB_OUTPUT`{% else %}`set-output`{% endif %} | | `core.setSecret` | `add-mask` | | `core.startGroup` | `group` | | `core.warning` | `warning` | diff --git a/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md index 405e998caf..5c778a85ca 100644 --- a/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md +++ b/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md @@ -115,7 +115,7 @@ For more information, see "[Reusing workflows](/actions/learn-github-actions/reu #### `on.workflow_call.inputs..type` -Required if input is defined for the `on.workflow_call` keyword. The value of this parameter is a string specifying the data type of the input. This must be one of: `boolean`, `number`, `string` or `choice`. +Required if input is defined for the `on.workflow_call` keyword. The value of this parameter is a string specifying the data type of the input. This must be one of: `boolean`, `number`, or `string`. ### `on.workflow_call.outputs` @@ -497,7 +497,7 @@ jobs: #### Example: Using an action inside a different private repository than the workflow -Your workflow must checkout the private repository and reference the action locally. Generate a personal access token and add the token as an encrypted secret. 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)." +Your workflow must checkout the private repository and reference the action locally. Generate a {% data variables.product.pat_generic %} and add the token as an encrypted secret. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)." Replace `PERSONAL_ACCESS_TOKEN` in the example with the name of your secret. diff --git a/translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md b/translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md index 468b95f2c7..c984aebcab 100644 --- a/translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md +++ b/translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md @@ -1,7 +1,7 @@ --- title: Configuring code scanning for your appliance shortTitle: Configuring code scanning -intro: 'You can enable, configure and disable {% data variables.product.prodname_code_scanning %} for {% data variables.product.product_location %}. {% data variables.product.prodname_code_scanning_capc %} allows users to scan code for vulnerabilities and errors.' +intro: 'You can enable, configure and disable {% data variables.product.prodname_code_scanning %} for {% data variables.location.product_location %}. {% data variables.product.prodname_code_scanning_capc %} allows users to scan code for vulnerabilities and errors.' product: '{% data reusables.gated-features.code-scanning %}' miniTocMaxHeadingLevel: 3 redirect_from: @@ -24,7 +24,7 @@ topics: {% data reusables.code-scanning.about-code-scanning %} -You can configure {% data variables.product.prodname_code_scanning %} to run {% data variables.product.prodname_codeql %} analysis and third-party analysis. {% data variables.product.prodname_code_scanning_capc %} also supports running analysis natively using {% data variables.product.prodname_actions %} or externally using existing CI/CD infrastructure. The table below summarizes all the options available to users when you configure {% data variables.product.product_location %} to allow {% data variables.product.prodname_code_scanning %} using actions. +You can configure {% data variables.product.prodname_code_scanning %} to run {% data variables.product.prodname_codeql %} analysis and third-party analysis. {% data variables.product.prodname_code_scanning_capc %} also supports running analysis natively using {% data variables.product.prodname_actions %} or externally using existing CI/CD infrastructure. The table below summarizes all the options available to users when you configure {% data variables.location.product_location %} to allow {% data variables.product.prodname_code_scanning %} using actions. {% data reusables.code-scanning.enabling-options %} @@ -74,7 +74,7 @@ If you set up the {% data variables.product.prodname_codeql %} action sync tool, ### Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %} 1. If you want to download action workflows on demand from {% data variables.product.prodname_dotcom_the_website %}, you need to enable {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling {% data variables.product.prodname_github_connect %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud#enabling-github-connect)." -2. You'll also need to enable {% data variables.product.prodname_actions %} for {% data variables.product.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." +2. You'll also need to enable {% data variables.product.prodname_actions %} for {% data variables.location.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." 3. The next step is to configure access to actions on {% data variables.product.prodname_dotcom_the_website %} using {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." 4. Add a self-hosted runner to your repository, organization, or enterprise account. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." diff --git a/translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md b/translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md index f6d78dedfb..291f6f4906 100644 --- a/translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md +++ b/translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md @@ -1,7 +1,7 @@ --- -title: 为设备配置密码扫描 +title: Configuring secret scanning for your appliance shortTitle: Configuring secret scanning -intro: '您可以为 {% data variables.product.product_location %} 启用、配置和禁用 {% data variables.product.prodname_secret_scanning %}。 {% data variables.product.prodname_secret_scanning_caps %} 允许用户扫描代码以寻找意外泄露的密码。' +intro: 'You can enable, configure, and disable {% data variables.product.prodname_secret_scanning %} for {% data variables.location.product_location %}. {% data variables.product.prodname_secret_scanning_caps %} allows users to scan code for accidentally committed secrets.' product: '{% data reusables.gated-features.secret-scanning %}' miniTocMaxHeadingLevel: 3 redirect_from: @@ -15,58 +15,59 @@ topics: - Enterprise - Secret scanning - Security -ms.openlocfilehash: c44d724293b970ff3075deb1befb2f0eae427d5c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147066319' --- + {% data reusables.secret-scanning.beta %} -## 关于 {% data variables.product.prodname_secret_scanning %} +## About {% data variables.product.prodname_secret_scanning %} -如果有人将使用已知模式的机密签入存储库,{% data variables.product.prodname_secret_scanning %} 会在签入机密时对其进行捕获,帮助降低机密被泄的影响。 仓库管理员会收到包含密码的任何提交的通知, 然后他们可以快速查看仓库安全选项卡中所有检测到的密码。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)”。 +If someone checks a secret with a known pattern into a repository, {% data variables.product.prodname_secret_scanning %} catches the secret as it's checked in, and helps you mitigate the impact of the leak. Repository administrators are notified about any commit that contains a secret, and they can quickly view all detected secrets in the Security tab for the repository. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)." -## 检查您的许可是否包含 {% data variables.product.prodname_GH_advanced_security %} +## Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %} {% data reusables.advanced-security.check-for-ghas-license %} -## {% data variables.product.prodname_secret_scanning %} 的前提条件 +## Prerequisites for {% data variables.product.prodname_secret_scanning %} -- [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470)(补充流式处理 SIMD 扩展 3)CPU 标志需要在运行 {% data variables.product.product_location %} 的 VM/KVM 上启用。 +- The [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Supplemental Streaming SIMD Extensions 3) CPU flag needs to be enabled on the VM/KVM that runs {% data variables.location.product_location %}. -- {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghes %} 的许可证(请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %} 的计费](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)”){% endif %} +- A license for {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghes %} (see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)"){% endif %} -- 在管理控制台中启用的 {% data variables.product.prodname_secret_scanning_caps %}(请参阅“[为企业启用 {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)”) +- {% data variables.product.prodname_secret_scanning_caps %} enabled in the management console (see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)") -### 检查您的 vCPU 上的 SSSE3 标志的支持 +### Checking support for the SSSE3 flag on your vCPUs -SSSE3 指令集是必需的,因为 {% data variables.product.prodname_secret_scanning %} 利用硬件加速模式匹配来查找提交给 {% data variables.product.prodname_dotcom %} 仓库的潜在凭据。 大多数现代 CPU 都启用了 SSSE3。 您可以检查您的 {% data variables.product.prodname_ghe_server %} 实例的可用 vCPU 是否启用了 SSSE3。 +The SSSE3 set of instructions is required because {% data variables.product.prodname_secret_scanning %} leverages hardware accelerated pattern matching to find potential credentials committed to your {% data variables.product.prodname_dotcom %} repositories. SSSE3 is enabled for most modern CPUs. You can check whether SSSE3 is enabled for the vCPUs available to your {% data variables.product.prodname_ghe_server %} instance. -1. 连接到 {% data variables.product.prodname_ghe_server %} 实例的管理 shell。 有关详细信息,请参阅“[访问管理 shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)”。 -2. 输入以下命令: +1. Connect to the administrative shell for your {% data variables.product.prodname_ghe_server %} instance. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." +2. Enter the following command: ```shell grep -iE '^flags.*ssse3' /proc/cpuinfo >/dev/null | echo $? ``` - 如果返回值 `0`,则意味着 SSSE3 标志可用并且已启用。 您现在可以为 {% data variables.product.product_location %} 启用 {% data variables.product.prodname_secret_scanning %}。 有关详细信息,请参阅下面的“[启用 {% data variables.product.prodname_secret_scanning %}](#enabling-secret-scanning)”。 + If this returns the value `0`, it means that the SSSE3 flag is available and enabled. You can now enable {% data variables.product.prodname_secret_scanning %} for {% data variables.location.product_location %}. For more information, see "[Enabling {% data variables.product.prodname_secret_scanning %}](#enabling-secret-scanning)" below. - 如果不返回 `0`,则 SSSE3 未在 VM/KVM 上启用。 您需要参考硬件/虚拟机监控程序的文档,以了解如何启用该标志,或者如何使其可用于访客 VM。 + If this doesn't return `0`, SSSE3 is not enabled on your VM/KVM. You need to refer to the documentation of the hardware/hypervisor on how to enable the flag, or make it available to guest VMs. -## 启用 {% data variables.product.prodname_secret_scanning %} +## Enabling {% data variables.product.prodname_secret_scanning %} {% data reusables.enterprise_management_console.enable-disable-security-features %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.advanced-security-tab %} -1. 在“安全性”下,单击 {% data variables.product.prodname_secret_scanning_caps %}。 -![用于启用或禁用 {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png) {% data reusables.enterprise_management_console.save-settings %} 的复选框 +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Under "Security," click **{% data variables.product.prodname_secret_scanning_caps %}**. +![Checkbox to enable or disable {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} -## 禁用 {% data variables.product.prodname_secret_scanning %} +## Disabling {% data variables.product.prodname_secret_scanning %} {% data reusables.enterprise_management_console.enable-disable-security-features %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.advanced-security-tab %} -1. 在“安全性”下,取消选择 {% data variables.product.prodname_secret_scanning_caps %}。 -![用于启用或禁用 {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png) {% data reusables.enterprise_management_console.save-settings %} 的复选框 +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Under "Security," unselect **{% data variables.product.prodname_secret_scanning_caps %}**. +![Checkbox to enable or disable {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md b/translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md index 77a6ba89ee..73832aee06 100644 --- a/translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: 为企业启用 GitHub 高级安全性 +title: Enabling GitHub Advanced Security for your enterprise shortTitle: Enabling GitHub Advanced Security -intro: '可配置 {% data variables.product.product_name %} 以包括 {% data variables.product.prodname_GH_advanced_security %}。 这将提供额外的功能,帮助用户发现和修复其代码中的安全问题。' +intro: 'You can configure {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code.' product: '{% data reusables.gated-features.ghas %}' redirect_from: - /admin/advanced-security/enabling-github-advanced-security-for-your-enterprise @@ -14,72 +14,79 @@ topics: - Enterprise - Secret scanning - Security -ms.openlocfilehash: bc516af0c0788eeafe1b833c5627e471982e1c05 -ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147876035' --- -## 关于启用 {% data variables.product.prodname_GH_advanced_security %} + +## About enabling {% data variables.product.prodname_GH_advanced_security %} {% data reusables.advanced-security.ghas-helps-developers %} -{% ifversion ghes %} 为企业启用 {% data variables.product.prodname_GH_advanced_security %} 后,所有组织的存储库管理员都可以启用这些功能,除非你设置了限制访问的策略。 有关详细信息,请参阅“[在企业中强制实施 {% data variables.product.prodname_advanced_security %} 策略](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)”。 -{% else %} 为企业启用 {% data variables.product.prodname_GH_advanced_security %} 后,所有组织的存储库管理员都可以启用这些功能。 {% endif %} - -{% ifversion ghes %} 有关 GitHub 高级安全分阶段部署的指南,请参阅“[大规模采用 GitHub 高级安全简介](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale)”。 +{% ifversion ghes %} +When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features unless you set up a policy to restrict access. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)." +{% else %} +When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features. {% endif %} -## 检查您的许可是否包含 {% data variables.product.prodname_GH_advanced_security %} +{% ifversion ghes %} +For guidance on a phased deployment of GitHub Advanced Security, see "[Introduction to adopting GitHub Advanced Security at scale](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale)." +{% endif %} -{% ifversion ghes %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -1. 如果您的许可包括 {% data variables.product.prodname_GH_advanced_security %},则许可页面将包括显示当前使用情况详细信息的部分。 -![企业许可证的 {% data variables.product.prodname_GH_advanced_security %} 部分](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png) {% endif %} +## Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %} -## 启用 {% data variables.product.prodname_GH_advanced_security %} 的前提条件 +{% ifversion ghes %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.license-tab %} +1. If your license includes {% data variables.product.prodname_GH_advanced_security %}, the license page includes a section showing details of current usage. +![{% data variables.product.prodname_GH_advanced_security %} section of Enterprise license](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png) +{% endif %} -1. 升级 {% data variables.product.product_name %} 的许可证,以包含 {% data variables.product.prodname_GH_advanced_security %}。{% ifversion ghes %}有关许可的信息,请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %} 的计费](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)”。{% endif %} -2. 下载新的许可文件。 有关详细信息,请参阅“[下载 {% data variables.product.prodname_enterprise %} 的许可证](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)”。 -3. 将新许可文件上传到 {% data variables.product.product_location %}。 有关详细信息,请参阅“[将新许可证上传到 {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)”。{% ifversion ghes %} -4. 审查您计划启用的功能的先决条件。 +## Prerequisites for enabling {% data variables.product.prodname_GH_advanced_security %} - - {% data variables.product.prodname_code_scanning_capc %},请参阅“[为设备配置 {% data variables.product.prodname_code_scanning %}](/admin/advanced-security/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)”。 - - {% data variables.product.prodname_secret_scanning_caps %},请参阅“[为设备配置 {% data variables.product.prodname_secret_scanning %}](/admin/advanced-security/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)”。{% endif %} - - {% data variables.product.prodname_dependabot %},请参阅“[为企业启用 {% data variables.product.prodname_dependabot %}](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)”。 +1. Upgrade your license for {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}.{% ifversion ghes %} For information about licensing, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% endif %} +2. Download the new license file. For more information, see "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)." +3. Upload the new license file to {% data variables.location.product_location %}. For more information, see "[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% ifversion ghes %} +4. Review the prerequisites for the features you plan to enable. -## 启用和禁用 {% data variables.product.prodname_GH_advanced_security %} 功能 + - {% data variables.product.prodname_code_scanning_capc %}, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)." + - {% data variables.product.prodname_secret_scanning_caps %}, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/admin/advanced-security/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)."{% endif %} + - {% data variables.product.prodname_dependabot %}, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." + +## Enabling and disabling {% data variables.product.prodname_GH_advanced_security %} features {% data reusables.enterprise_management_console.enable-disable-security-features %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.advanced-security-tab %}{% ifversion ghes %} -1. 在“安全”下,选择要启用的功能,取消选择要禁用的任何功能。 -{% ifversion ghes %}![用于启用或禁用 {% data variables.product.prodname_advanced_security %} 功能的复选框](/assets/images/enterprise/3.2/management-console/enable-security-checkboxes.png){% else %}![用于启用或禁用 {% data variables.product.prodname_advanced_security %} 功能的复选框](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png){% endif %}{% else %} -1. 在“{% data variables.product.prodname_advanced_security %}”下,单击“{% data variables.product.prodname_code_scanning_capc %}”。 -![用于启用或禁用 {% data variables.product.prodname_code_scanning %} 的复选框](/assets/images/enterprise/management-console/enable-code-scanning-checkbox.png){% endif %} {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %}{% ifversion ghes %} +1. Under "Security," select the features that you want to enable and deselect any features you want to disable. +{% ifversion ghes %}![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/3.2/management-console/enable-security-checkboxes.png){% else %}![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png){% endif %}{% else %} +1. Under "{% data variables.product.prodname_advanced_security %}," click **{% data variables.product.prodname_code_scanning_capc %}**. +![Checkbox to enable or disable {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/enable-code-scanning-checkbox.png){% endif %} +{% data reusables.enterprise_management_console.save-settings %} -当 {% data variables.product.product_name %} 完成重启后,您可以设置新启用功能所需的任何额外资源。 有关详细信息,请参阅“[为设备配置 {% data variables.product.prodname_code_scanning %}](/admin/advanced-security/configuring-code-scanning-for-your-appliance)”。 +When {% data variables.product.product_name %} has finished restarting, you're ready to set up any additional resources required for newly enabled features. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance)." -## 通过管理 shell (SSH) 启用或禁用 {% data variables.product.prodname_GH_advanced_security %} 功能 +## Enabling or disabling {% data variables.product.prodname_GH_advanced_security %} features via the administrative shell (SSH) -您可以通过编程方式在 {% data variables.product.product_location %} 上启用或禁用功能。 有关 {% data variables.product.prodname_ghe_server %} 的管理 shell 和命令行实用程序的详细信息,请参阅“[访问管理 shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)”和“[命令行实用程序](/admin/configuration/command-line-utilities#ghe-config)”。 +You can enable or disable features programmatically on {% data variables.location.product_location %}. For more information about the administrative shell and command-line utilities for {% data variables.product.prodname_ghe_server %}, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[Command-line utilities](/admin/configuration/command-line-utilities#ghe-config)." -例如,当您部署用于暂存或灾难恢复的实例时,可以使用基础架构即代码工具启用任何 {% data variables.product.prodname_GH_advanced_security %}。 +For example, you can enable any {% data variables.product.prodname_GH_advanced_security %} feature with your infrastructure-as-code tooling when you deploy an instance for staging or disaster recovery. -1. 通过 SSH 连接到 {% data variables.product.product_location %}。 -1. 启用 {% data variables.product.prodname_GH_advanced_security %} 的功能。 +1. SSH into {% data variables.location.product_location %}. +1. Enable features for {% data variables.product.prodname_GH_advanced_security %}. - - 要启用 {% data variables.product.prodname_code_scanning_capc %},请输入以下命令。 + - To enable {% data variables.product.prodname_code_scanning_capc %}, enter the following commands. ```shell ghe-config app.minio.enabled true ghe-config app.code-scanning.enabled true ``` - - 要启用 {% data variables.product.prodname_secret_scanning_caps %},请输入以下命令。 + - To enable {% data variables.product.prodname_secret_scanning_caps %}, enter the following command. ```shell ghe-config app.secret-scanning.enabled true ``` - - 若要启用依赖项关系图,请输入以下{% ifversion ghes %}命令{% else %}命令{% endif %}。 - {% ifversion ghes %}```shell ghe-config app.dependency-graph.enabled true + - To enable the dependency graph, enter the following {% ifversion ghes %}command{% else %}commands{% endif %}. + {% ifversion ghes %}```shell + ghe-config app.dependency-graph.enabled true ``` {% else %}```shell ghe-config app.github.dependency-graph-enabled true @@ -92,12 +99,13 @@ ms.locfileid: '147876035' ghe-config app.minio.enabled false ghe-config app.code-scanning.enabled false ``` - - 要禁用 {% data variables.product.prodname_secret_scanning %},请输入以下命令。 + - To disable {% data variables.product.prodname_secret_scanning %}, enter the following command. ```shell ghe-config app.secret-scanning.enabled false ``` - - 若要禁用依赖项关系图,请输入以下{% ifversion ghes %}命令{% else %}命令{% endif %}。 - {% ifversion ghes %}```shell ghe-config app.dependency-graph.enabled false + - To disable the dependency graph, enter the following {% ifversion ghes %}command{% else %}commands{% endif %}. + {% ifversion ghes %}```shell + ghe-config app.dependency-graph.enabled false ``` {% else %}```shell ghe-config app.github.dependency-graph-enabled false diff --git a/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md b/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md index cd68019549..ee72a7d813 100644 --- a/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: 关于企业的供应链安全 -intro: 你可以启用可帮助开发人员了解和更新其代码所依赖的依赖项的功能。 +title: About supply chain security for your enterprise +intro: You can enable features that help your developers understand and update the dependencies their code relies on. shortTitle: About supply chain security permissions: '' versions: @@ -11,15 +11,10 @@ topics: - Enterprise - Security - Dependency graph -ms.openlocfilehash: f99085f6c484869623a81c7585216aca936929e1 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145100102' --- -可以允许用户通过{% ifversion ghes %}启用{% elsif ghae %}使用{% endif %} {% data variables.product.product_location %} 的依赖项关系图来识别其项目的依赖关系。 有关详细信息,请参阅“{% ifversion ghes %}[为企业启用依赖项关系图](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise){% elsif ghae %}[关于依赖项关系图](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph){% endif %}。” -还可以通过启用 {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} 和 {% data variables.product.prodname_dependabot_updates %}{% endif %} 允许 {% data variables.product.product_location %} 上的用户查找并修复其代码依赖项中的漏洞。 有关详细信息,请参阅“[为企业启用 {% data variables.product.prodname_dependabot %}](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)”。 +You can allow users to identify their projects' dependencies by {% ifversion ghes %}enabling{% elsif ghae %}using{% endif %} the dependency graph for {% data variables.location.product_location %}. For more information, see "{% ifversion ghes %}[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise){% elsif ghae %}[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph){% endif %}." -启用 {% data variables.product.prodname_dependabot_alerts %} 后,可以从 {% data variables.product.product_location %} 上的 {% data variables.product.prodname_advisory_database %} 查看漏洞数据并手动同步数据。 有关详细信息,请参阅“[查看企业的漏洞数据](/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise)”。 +You can also allow users on {% data variables.location.product_location %} to find and fix vulnerabilities in their code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." + +After you enable {% data variables.product.prodname_dependabot_alerts %}, you can view vulnerability data from the {% data variables.product.prodname_advisory_database %} on {% data variables.location.product_location %} and manually sync the data. For more information, see "[Viewing the vulnerability data for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise)." diff --git a/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md b/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md index 93c926159a..d4d24029d2 100644 --- a/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: 为企业启用依赖项关系图 -intro: 通过启用依赖项关系图,用户可识别其项目的依赖项。 +title: Enabling the dependency graph for your enterprise +intro: You can allow users to identify their projects' dependencies by enabling the dependency graph. shortTitle: Enable dependency graph permissions: Site administrators can enable the dependency graph. versions: @@ -10,34 +10,37 @@ topics: - Enterprise - Security - Dependency graph -ms.openlocfilehash: 6d4ba1a4e69c557a359bb0e99b02d92ff5fb99e0 -ms.sourcegitcommit: dc42bb4a4826b414751ffa9eed38962c3e3fea8e -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 07/13/2022 -ms.locfileid: '147062280' --- -## 关于依赖关系图 -{% data reusables.dependabot.about-the-dependency-graph %} 有关详细信息,请参阅“[关于依赖项关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)” +## About the dependency graph -为企业启用依赖项关系图后,可以启用 {% data variables.product.prodname_dependabot %} 来检测存储库中不安全的依赖项{% ifversion ghes > 3.2 %}并自动修复漏洞{% endif %}。 有关详细信息,请参阅“[对企业启用 {% data variables.product.prodname_dependabot %}](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)”。 +{% data reusables.dependabot.about-the-dependency-graph %} For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" -{% ifversion ghes %} 你可以通过 {% data variables.enterprise.management_console %} 或管理 shell 启用依赖项关系图。 建议使用 {% data variables.enterprise.management_console %},除非 {% data variables.product.product_location %} 使用聚类分析。 +After you enable the dependency graph for your enterprise, you can enable {% data variables.product.prodname_dependabot %} to detect insecure dependencies in your repository{% ifversion ghes > 3.2 %} and automatically fix the vulnerabilities{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." -## 通过 {% data variables.enterprise.management_console %} 启用依赖关系图 +{% ifversion ghes %} +You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend using the {% data variables.enterprise.management_console %} unless {% data variables.location.product_location %} uses clustering. -如果 {% data variables.product.product_location %} 使用聚类分析,则无法使用 {% data variables.enterprise.management_console %} 启用依赖项关系图,而必须使用管理 shell。 有关详细信息,请参阅“[通过管理 shell 启用依赖项关系图](#enabling-the-dependency-graph-via-the-administrative-shell)”。 +## Enabling the dependency graph via the {% data variables.enterprise.management_console %} -{% data reusables.enterprise_site_admin_settings.sign-in %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.advanced-security-tab %} -1. 在“安全性”下,单击“依赖项关系图”。 -![用于启用或禁用依赖项关系图的复选框](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png) {% data reusables.enterprise_management_console.save-settings %} -1. 单击“访问实例”。 +If {% data variables.location.product_location %} uses clustering, you cannot enable the dependency graph with the {% data variables.enterprise.management_console %} and must use the administrative shell instead. For more information, see "[Enabling the dependency graph via the administrative shell](#enabling-the-dependency-graph-via-the-administrative-shell)." -## 通过管理 shell 启用依赖关系图 +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Under "Security," click **Dependency graph**. +![Checkbox to enable or disable the dependency graph](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} +1. Click **Visit your instance**. -{% endif %} {% data reusables.enterprise_site_admin_settings.sign-in %} -1. 在管理 shell 中,启用 {% data variables.product.product_location %} 上的依赖项关系图:{% ifversion ghes %}```shell ghe-config app.dependency-graph.enabled true +## Enabling the dependency graph via the administrative shell + +{% endif %} +{% data reusables.enterprise_site_admin_settings.sign-in %} +1. In the administrative shell, enable the dependency graph on {% data variables.location.product_location %}: + {% ifversion ghes %}```shell + ghe-config app.dependency-graph.enabled true ``` {% else %}```shell ghe-config app.github.dependency-graph-enabled true @@ -52,4 +55,4 @@ ms.locfileid: '147062280' ```shell $ ghe-config-apply ``` -3. 返回到 {% data variables.product.prodname_ghe_server %}。 +3. Return to {% data variables.product.prodname_ghe_server %}. diff --git a/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md b/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md index 054e7c3752..b20b4c62a4 100644 --- a/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md @@ -1,8 +1,8 @@ --- -title: 查看企业的漏洞数据 -intro: '你可以在 {% data variables.product.product_location %} 上查看 {% data variables.product.prodname_advisory_database %} 中的漏洞数据。' +title: Viewing the vulnerability data for your enterprise +intro: 'You can view vulnerability data from the {% data variables.product.prodname_advisory_database %} on {% data variables.location.product_location %}.' shortTitle: View vulnerability data -permissions: 'Site administrators can view vulnerability data on {% data variables.product.product_location %}.' +permissions: 'Site administrators can view vulnerability data on {% data variables.location.product_location %}.' versions: ghes: '*' ghae: '*' @@ -11,22 +11,17 @@ topics: - Enterprise - Security - Dependency graph -ms.openlocfilehash: a9217f4cff35a675d87833e3fdad37ac9fe10665 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145098135' --- -如果为企业启用了 {% data variables.product.prodname_dependabot_alerts %},则可以查看从 {% data variables.product.prodname_advisory_database %} 下载到 {% data variables.product.product_location %} 的所有漏洞。 -可以从 {% data variables.product.prodname_dotcom_the_website %} 手动同步漏洞数据以更新列表。 +If {% data variables.product.prodname_dependabot_alerts %} are enabled for your enterprise, you can view all vulnerabilities that were downloaded to {% data variables.location.product_location %} from the {% data variables.product.prodname_advisory_database %}. -在查看漏洞数据之前,必须启用 {% data variables.product.prodname_dependabot_alerts %}。 有关详细信息,请参阅“[为企业启用 {% data variables.product.prodname_dependabot %}](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)”。 +You can manually sync vulnerability data from {% data variables.product.prodname_dotcom_the_website %} to update the list. + +Before you can view vulnerability data, you must enable {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% data reusables.enterprise_site_admin_settings.access-settings %} -2. 在左侧栏中,单击“漏洞”。 - ![站点管理员边栏中的“漏洞”选项卡](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png) -3. 若要同步漏洞数据,请单击“立即同步漏洞”。 - ![“立即同步漏洞”按钮](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png) +2. In the left sidebar, click **Vulnerabilities**. + ![Vulnerabilities tab in the site admin sidebar](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png) +3. To sync vulnerability data, click **Sync Vulnerabilities now**. + ![Sync vulnerabilities now button](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png) diff --git a/translations/zh-CN/content/admin/configuration/configuring-github-connect/about-github-connect.md b/translations/zh-CN/content/admin/configuration/configuring-github-connect/about-github-connect.md index 4b900f7f44..4b26af2b8e 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-github-connect/about-github-connect.md +++ b/translations/zh-CN/content/admin/configuration/configuring-github-connect/about-github-connect.md @@ -13,28 +13,28 @@ miniTocMaxHeadingLevel: 3 ## About {% data variables.product.prodname_github_connect %} -{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by allowing {% data variables.product.product_location %} to benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}. +{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by allowing {% data variables.location.product_location %} to benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}. -{% data variables.product.prodname_github_connect %} does not open {% data variables.product.product_location %} to the public internet. None of your enterprise's private data is exposed to {% data variables.product.prodname_dotcom_the_website %} users. Instead, {% data variables.product.prodname_github_connect %} transmits only the limited data needed for the individual features you choose to enable. Unless you enable license sync, no personal data is transmitted by {% data variables.product.prodname_github_connect %}. For more information about what data is transmitted by {% data variables.product.prodname_github_connect %}, see "[Data transmission for {% data variables.product.prodname_github_connect %}](#data-transmission-for-github-connect)." +{% data variables.product.prodname_github_connect %} does not open {% data variables.location.product_location %} to the public internet. None of your enterprise's private data is exposed to {% data variables.product.prodname_dotcom_the_website %} users. Instead, {% data variables.product.prodname_github_connect %} transmits only the limited data needed for the individual features you choose to enable. Unless you enable license sync, no personal data is transmitted by {% data variables.product.prodname_github_connect %}. For more information about what data is transmitted by {% data variables.product.prodname_github_connect %}, see "[Data transmission for {% data variables.product.prodname_github_connect %}](#data-transmission-for-github-connect)." Enabling {% data variables.product.prodname_github_connect %} will not allow {% data variables.product.prodname_dotcom_the_website %} users to make changes to {% data variables.product.product_name %}. -To enable {% data variables.product.prodname_github_connect %}, you configure a connection between {% data variables.product.product_location %} and an organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that uses {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)." +To enable {% data variables.product.prodname_github_connect %}, you configure a connection between {% data variables.location.product_location %} and an organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that uses {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)." After enabling {% data variables.product.prodname_github_connect %}, you will be able to enable features such as {% ifversion ghes %}automatic user license sync and {% endif %}{% data variables.product.prodname_dependabot_alerts %}. For more information about all of the features available, see "[{% data variables.product.prodname_github_connect %} features](#github-connect-features)." ## {% data variables.product.prodname_github_connect %} features -After you configure the connection between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %}, you can enable individual features of {% data variables.product.prodname_github_connect %} for your enterprise. +After you configure the connection between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %}, you can enable individual features of {% data variables.product.prodname_github_connect %} for your enterprise. Feature | Description | More information | ------- | ----------- | ---------------- |{% ifversion ghes %} -Automatic user license sync | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae %} +Automatic user license sync | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.location.product_location %} to {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae %} {% data variables.product.prodname_dependabot %} | Allow users to find and fix vulnerabilities in code dependencies. | "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %} {% data variables.product.prodname_dotcom_the_website %} actions | Allow users to use actions from {% data variables.product.prodname_dotcom_the_website %} in workflow files. | "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% ifversion server-statistics %} {% data variables.product.prodname_server_statistics %} | Analyze your own aggregate data from GitHub Enterprise Server, and help us improve GitHub products. | "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %} -Unified search | Allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.product.product_location %}. | "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" -Unified contributions | Allow users to include anonymized contribution counts for their work on {% data variables.product.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}. | "[Enabling {% data variables.product.prodname_unified_contributions %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)" +Unified search | Allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.location.product_location %}. | "[Enabling {% data variables.enterprise.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" +Unified contributions | Allow users to include anonymized contribution counts for their work on {% data variables.location.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}. | "[Enabling {% data variables.enterprise.prodname_unified_contributions %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)" ## Data transmission for {% data variables.product.prodname_github_connect %} @@ -53,17 +53,17 @@ When you enable {% data variables.product.prodname_github_connect %} or specific - The public key portion of your {% data variables.product.prodname_ghe_server %} license - A hash of your {% data variables.product.prodname_ghe_server %} license - The customer name on your {% data variables.product.prodname_ghe_server %} license -- The version of {% data variables.product.product_location_enterprise %}{% endif %} -- The hostname of {% data variables.product.product_location %} -- The organization or enterprise account on {% data variables.product.prodname_ghe_cloud %} that's connected to {% data variables.product.product_location %} -- The authentication token that's used by {% data variables.product.product_location %} to make requests to {% data variables.product.prodname_ghe_cloud %} -- If Transport Layer Security (TLS) is enabled and configured on {% data variables.product.product_location %}{% ifversion ghes %} -- The {% data variables.product.prodname_github_connect %} features that are enabled on {% data variables.product.product_location %}, and the date and time of enablement{% endif %} +- The version of {% data variables.location.product_location_enterprise %}{% endif %} +- The hostname of {% data variables.location.product_location %} +- The organization or enterprise account on {% data variables.product.prodname_ghe_cloud %} that's connected to {% data variables.location.product_location %} +- The authentication token that's used by {% data variables.location.product_location %} to make requests to {% data variables.product.prodname_ghe_cloud %} +- If Transport Layer Security (TLS) is enabled and configured on {% data variables.location.product_location %}{% ifversion ghes %} +- The {% data variables.product.prodname_github_connect %} features that are enabled on {% data variables.location.product_location %}, and the date and time of enablement{% endif %} - The dormancy threshold for your enterprise - The number of dormant users for your enterprise - A count of license-consuming seats, which does not include suspended users -{% data variables.product.prodname_github_connect %} syncs the above connection data between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %} weekly, from the day and approximate time that {% data variables.product.prodname_github_connect %} was enabled. +{% data variables.product.prodname_github_connect %} syncs the above connection data between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %} weekly, from the day and approximate time that {% data variables.product.prodname_github_connect %} was enabled. ### Data transmitted by individual features of {% data variables.product.prodname_github_connect %} diff --git a/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md index 846a0e09f0..4f4bff2a29 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: 为企业启用自动触发用户许可证同步 -intro: '可以通过自动将用户许可证从 {% data variables.product.product_location %} 同步到 {% data variables.product.prodname_ghe_cloud %} 来管理 {% data variables.product.prodname_enterprise %} 环境中的许可证使用情况。' +title: Enabling automatic user license sync for your enterprise +intro: 'You can manage license usage across your {% data variables.product.prodname_enterprise %} environments by automatically syncing user licenses from {% data variables.location.product_location %} to {% data variables.product.prodname_ghe_cloud %}.' redirect_from: - /enterprise/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud - /enterprise/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud @@ -16,33 +16,28 @@ topics: - GitHub Connect - Licensing shortTitle: Automatic user license sync -ms.openlocfilehash: eb0216dcdb629e96ef83de2eea8a7d7b6660a171 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145910557' --- -## 关于自动许可证同步 +## About automatic license synchronization {% data reusables.enterprise-licensing.unique-user-licensing-model %} -{% data reusables.enterprise-licensing.about-license-sync %} 有关详细信息,请参阅“[关于 {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect#data-transmission-for-github-connect)”。 +{% data reusables.enterprise-licensing.about-license-sync %} For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect#data-transmission-for-github-connect)." -如果为企业启用自动用户许可证同步,{% data variables.product.prodname_github_connect %} 将每周自动同步一次 {% data variables.product.prodname_ghe_server %} 与 {% data variables.product.prodname_ghe_cloud %} 之间的许可证使用情况。{% ifversion ghes > 3.4 %}还可以通过手动触发许可证同步作业,在自动每周同步之外随时同步许可证数据。 有关详细信息,请参阅“[触发许可证同步作业](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud#triggering-a-license-sync-job)”。{% endif %} +If you enable automatic user license sync for your enterprise, {% data variables.product.prodname_github_connect %} will automatically synchronize license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} weekly.{% ifversion ghes > 3.4 %} You can also synchronize your license data at any time outside of the automatic weekly sync, by manually triggering a license sync job. For more information, see "[Triggering a license sync job](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud#triggering-a-license-sync-job)."{% endif %} -如果使用多个 {% data variables.product.prodname_ghe_server %} 实例,则可以在 {% data variables.product.prodname_ghe_cloud %} 上启用每个实例与同一组织或企业帐户之间的自动触发许可证同步。 +If you use multiple {% data variables.product.prodname_ghe_server %} instances, you can enable automatic license sync between each of your instances and the same organization or enterprise account on {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise-licensing.view-consumed-licenses %} -您还可以手动将 {% data variables.product.prodname_ghe_server %} 用户许可信息上传到 {% data variables.product.prodname_ghe_cloud %}。 有关详细信息,请参阅“[同步 {% data variables.product.prodname_ghe_server %} 和 {% data variables.product.prodname_ghe_cloud %} 之间的许可证使用情况](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)”。 +You can also manually upload {% data variables.product.prodname_ghe_server %} user license information to {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)." {% data reusables.enterprise-licensing.verified-domains-license-sync %} -## 启用许可同步 +## Enabling license synchronization -在 {% data variables.product.product_location %} 上启用许可证同步之前,必须启用 {% data variables.product.prodname_github_connect %}。 有关详细信息,请参阅“[管理 {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)”。 +Before enabling license synchronization on {% data variables.location.product_location %}, you must enable {% data variables.product.prodname_github_connect %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)." -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %} -1. 在“服务器可同步用户许可证计数和使用情况”下,使用下拉菜单,然后选择“启用”。 - ![用于启用自动触发用户许可证同步的下拉菜单](/assets/images/enterprise/site-admin-settings/enable-user-license-drop-down.png) +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.github-connect-tab %} +1. Under "Server can sync user license count and usage", use the drop-down menu and select **Enabled**. + ![Drop-down menu to enable automatic user license sync](/assets/images/enterprise/site-admin-settings/enable-user-license-drop-down.png) diff --git a/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md index 65a19be5d0..8fa01e4e0d 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md @@ -1,6 +1,6 @@ --- title: Enabling Dependabot for your enterprise -intro: 'You can allow users of {% data variables.product.product_location %} to find and fix vulnerabilities in code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}.' +intro: 'You can allow users of {% data variables.location.product_location %} to find and fix vulnerabilities in code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}.' miniTocMaxHeadingLevel: 3 shortTitle: Dependabot redirect_from: @@ -26,14 +26,14 @@ topics: ## About {% data variables.product.prodname_dependabot %} for {% data variables.product.product_name %} -{% data variables.product.prodname_dependabot %} helps users of {% data variables.product.product_location %} find and fix vulnerabilities in their dependencies.{% ifversion ghes > 3.2 %} You can enable {% data variables.product.prodname_dependabot_alerts %} to notify users about vulnerable dependencies and {% data variables.product.prodname_dependabot_updates %} to fix the vulnerabilities and keep dependencies updated to the latest version. +{% data variables.product.prodname_dependabot %} helps users of {% data variables.location.product_location %} find and fix vulnerabilities in their dependencies.{% ifversion ghes > 3.2 %} You can enable {% data variables.product.prodname_dependabot_alerts %} to notify users about vulnerable dependencies and {% data variables.product.prodname_dependabot_updates %} to fix the vulnerabilities and keep dependencies updated to the latest version. ### About {% data variables.product.prodname_dependabot_alerts %} {% endif %} {% data reusables.dependabot.dependabot-alerts-beta %} -With {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dotcom %} identifies insecure dependencies in repositories and creates alerts on {% data variables.product.product_location %}, using data from the {% data variables.product.prodname_advisory_database %} and the dependency graph service. +With {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dotcom %} identifies insecure dependencies in repositories and creates alerts on {% data variables.location.product_location %}, using data from the {% data variables.product.prodname_advisory_database %} and the dependency graph service. {% data reusables.repositories.tracks-vulnerabilities %} @@ -43,20 +43,20 @@ You can also choose to manually sync vulnerability data at any time. For more in {% note %} -**Note:** When you enable {% data variables.product.prodname_dependabot_alerts %}, no code or information about code from {% data variables.product.product_location %} is uploaded to {% data variables.product.prodname_dotcom_the_website %}. +**Note:** When you enable {% data variables.product.prodname_dependabot_alerts %}, no code or information about code from {% data variables.location.product_location %} is uploaded to {% data variables.product.prodname_dotcom_the_website %}. {% endnote %} -When {% data variables.product.product_location %} receives information about a vulnerability, it identifies repositories in {% data variables.product.product_location %} that use the affected version of the dependency and generates {% data variables.product.prodname_dependabot_alerts %}. You can choose whether or not to notify users automatically about new {% data variables.product.prodname_dependabot_alerts %}. +When {% data variables.location.product_location %} receives information about a vulnerability, it identifies repositories in {% data variables.location.product_location %} that use the affected version of the dependency and generates {% data variables.product.prodname_dependabot_alerts %}. You can choose whether or not to notify users automatically about new {% data variables.product.prodname_dependabot_alerts %}. -For repositories with {% data variables.product.prodname_dependabot_alerts %} enabled, scanning is triggered on any push to the default branch that contains a manifest file or lock file. Additionally, when a new vulnerability record is added to {% data variables.product.product_location %}, {% data variables.product.product_name %} scans all existing repositories on {% data variables.product.product_location %} and generates alerts for any repository that is vulnerable. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +For repositories with {% data variables.product.prodname_dependabot_alerts %} enabled, scanning is triggered on any push to the default branch that contains a manifest file or lock file. Additionally, when a new vulnerability record is added to {% data variables.location.product_location %}, {% data variables.product.product_name %} scans all existing repositories on {% data variables.location.product_location %} and generates alerts for any repository that is vulnerable. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." {% ifversion ghes > 3.2 %} ### About {% data variables.product.prodname_dependabot_updates %} {% data reusables.dependabot.beta-security-and-version-updates %} -After you enable {% data variables.product.prodname_dependabot_alerts %}, you can choose to enable {% data variables.product.prodname_dependabot_updates %}. When {% data variables.product.prodname_dependabot_updates %} are enabled for {% data variables.product.product_location %}, users can configure repositories so that their dependencies are updated and kept secure automatically. +After you enable {% data variables.product.prodname_dependabot_alerts %}, you can choose to enable {% data variables.product.prodname_dependabot_updates %}. When {% data variables.product.prodname_dependabot_updates %} are enabled for {% data variables.location.product_location %}, users can configure repositories so that their dependencies are updated and kept secure automatically. {% note %} diff --git a/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md index fa9d6c0a92..e42ff2fafe 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: 为企业启用服务器统计信息 -intro: '可以从 {% data variables.product.prodname_ghe_server %} 分析自己的聚合数据,并通过启用 {% data variables.product.prodname_server_statistics %} 帮助改进 {% data variables.product.company_short %} 产品。' +title: Enabling Server Statistics for your enterprise +intro: 'You can analyze your own aggregate data from {% data variables.product.prodname_ghe_server %} and help us improve {% data variables.product.company_short %} products by enabling {% data variables.product.prodname_server_statistics %}.' versions: feature: server-statistics redirect_from: @@ -8,27 +8,23 @@ redirect_from: topics: - Enterprise shortTitle: Server Statistics -ms.openlocfilehash: badfdb8abfbe468768ef9a32e183f67633915b54 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147409001' --- -## 关于 {% data variables.product.prodname_server_statistics %} -{% data variables.product.prodname_server_statistics %} 从 {% data variables.product.product_location %} 中收集聚合使用情况数据,你可以使用这些数据更好地预测组织的需求、了解团队的工作方式并显示你从 {% data variables.product.prodname_ghe_server %} 获取的值。 +## About {% data variables.product.prodname_server_statistics %} -{% data variables.product.prodname_server_statistics %} 仅收集有关存储库、问题、拉取请求和其他功能的某些聚合指标。不收集 {% data variables.product.prodname_dotcom %} 内容,例如代码、问题、评论或拉取请求内容。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)”。 +{% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.location.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. -通过启用 {% data variables.product.prodname_server_statistics %},还可帮助提高 {% data variables.product.company_short %}。 你将提供的聚合数据有助于我们了解我们的客户使用 {% data variables.product.prodname_dotcom %} 的方式,并做出更好、更明智的产品决策,最终使你受益。 +{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features.{% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)." -## 启用 {% data variables.product.prodname_server_statistics %} +By enabling {% data variables.product.prodname_server_statistics %}, you are also helping to improve {% data variables.product.company_short %}. The aggregated data you will provide helps us understand how our customers are using {% data variables.product.prodname_dotcom %}, and make better and more informed product decisions, ultimately benefiting you. -启用 {% data variables.product.prodname_server_statistics %} 之前,必须首先通过 {% data variables.product.prodname_github_connect %} 将 {% data variables.product.prodname_ghe_server %} 实例连接到 {% data variables.product.prodname_dotcom_the_website %}。 有关详细信息,请参阅“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@3.1/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)”。 +## Enabling {% data variables.product.prodname_server_statistics %} -可随时从 {% data variables.product.prodname_ghe_server %} 禁用 {% data variables.product.prodname_server_statistics %}。 +Before you can enable {% data variables.product.prodname_server_statistics %}, you must first connect your {% data variables.product.prodname_ghe_server %} instance to {% data variables.product.prodname_dotcom_the_website %} through {% data variables.product.prodname_github_connect %}. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@3.1/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)." -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %} -4. 在“与 GitHub.com 共享服务器统计信息”下,选择下拉菜单并单击“启用”或“禁用” 。 - ![包含禁用或启用选项的 {% data variables.product.prodname_server_statistics %} 下拉菜单的屏幕截图](/assets/images/help/server-statistics/server-statistics-enable-disable-options.png) +You can disable {% data variables.product.prodname_server_statistics %} from {% data variables.product.prodname_ghe_server %} at any time. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.github-connect-tab %} +4. Under "Share server statistics with GitHub.com", select the dropdown menu and click **Enabled** or **Disabled**. + ![Screenshot of {% data variables.product.prodname_server_statistics %} drop-down menu with disabled or enabled options](/assets/images/help/server-statistics/server-statistics-enable-disable-options.png) diff --git a/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md index 582c3a80b7..e9c67f0fcd 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: 为企业启用统一贡献 +title: Enabling unified contributions for your enterprise shortTitle: Unified contributions -intro: '可以允许用户将经过匿名处理的工作贡献计数包含在 {% data variables.product.prodname_dotcom_the_website %} 上贡献图的 {% data variables.product.product_location %} 中。' +intro: 'You can allow users to include anonymized contribution counts for their work on {% data variables.location.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}.' redirect_from: - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-and-github-com - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-github-com @@ -11,7 +11,7 @@ redirect_from: - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-contributions-between-github-enterprise-server-and-githubcom - /admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom -permissions: 'Enterprise owners can enable unified contributions between {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.' +permissions: 'Enterprise owners can enable unified contributions between {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.' versions: ghes: '*' ghae: '*' @@ -19,37 +19,36 @@ type: how_to topics: - Enterprise - GitHub Connect -ms.openlocfilehash: af07f30a8f164f6bec3d3c0f44c77181f1e8db7b -ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147875978' --- + {% data reusables.github-connect.beta %} -## 关于统一贡献 +## About unified contributions -作为企业所有者,你可以允许最终用户将进行过匿名处理的工作贡献计数从 {% data variables.product.product_location %} 发送到其 {% data variables.product.prodname_dotcom_the_website %} 贡献图。 +As an enterprise owner, you can allow end users to send anonymized contribution counts for their work from {% data variables.location.product_location %} to their {% data variables.product.prodname_dotcom_the_website %} contribution graph. -启用 {% data variables.product.prodname_unified_contributions %} 后,每个用户还必须将自己在 {% data variables.product.product_name %} 上的用户帐户与 {% data variables.product.prodname_dotcom_the_website %} 上的个人帐户连接起来,个人用户才能将贡献计数从 {% data variables.product.product_location %} 发送到 {% data variables.product.prodname_dotcom_the_website %}。 有关详细信息,请参阅“[将企业贡献发送到自己的 {% data variables.product.prodname_dotcom_the_website %} 配置文件](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)”。 +After you enable {% data variables.enterprise.prodname_unified_contributions %}, before individual users can send contribution counts from {% data variables.location.product_location %} to {% data variables.product.prodname_dotcom_the_website %}, each user must also connect their user account on {% data variables.product.product_name %} with a personal account on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)." {% data reusables.github-connect.sync-frequency %} -如果企业所有者禁用了该功能或个人用户选择退出连接,则系统将删除 {% data variables.product.prodname_dotcom_the_website %} 上的 {% data variables.product.product_name %} 贡献计数。 如果用户在禁用该功能后重新连接自己的配置文件,则系统将恢复过去 90 天的贡献计数。 +If the enterprise owner disables the functionality or individual users opt out of the connection, the contribution counts from {% data variables.product.product_name %} will be deleted on {% data variables.product.prodname_dotcom_the_website %}. If the user reconnects their profiles after disabling them, the contribution counts for the past 90 days are restored. -{% data variables.product.product_name %} 仅为已连接的用户发送贡献计数和来源 ({% data variables.product.product_name %})。 它不会发送有关贡献或做出该贡献的方式的任何信息。 +{% data variables.product.product_name %} **only** sends the contribution count and source ({% data variables.product.product_name %}) for connected users. It does not send any information about the contribution or how it was made. -## 启用统一贡献 +## Enabling unified contributions -在 {% data variables.product.product_location %} 上启用 {% data variables.product.prodname_unified_contributions %} 之前,必须先启用 {% data variables.product.prodname_github_connect %}。 有关详细信息,请参阅“[管理 {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)”。 +Before enabling {% data variables.enterprise.prodname_unified_contributions %} on {% data variables.location.product_location %}, you must enable {% data variables.product.prodname_github_connect %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)." -{% ifversion ghes %} {% data reusables.github-connect.access-dotcom-and-enterprise %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.business %} {% data reusables.enterprise-accounts.github-connect-tab %}{% else %} -1. 登录到 {% data variables.product.product_location %} 和 {% data variables.product.prodname_dotcom_the_website %}。 +{% ifversion ghes %} +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.business %} +{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} -1. 在“用户可将贡献计数分享到 {% data variables.product.prodname_dotcom_the_website %}”下,单击“请求访问”。 - ![请求访问统一贡献选项](/assets/images/enterprise/site-admin-settings/dotcom-ghe-connection-request-access.png){% ifversion ghes %} -2. [登录](https://enterprise.github.com/login)到站点 {% data variables.product.prodname_ghe_server %} 以接收其他说明。 +1. Under "Users can share contribution counts to {% data variables.product.prodname_dotcom_the_website %}", click **Request access**. + ![Request access to unified contributions option](/assets/images/enterprise/site-admin-settings/dotcom-ghe-connection-request-access.png){% ifversion ghes %} +2. [Sign in](https://enterprise.github.com/login) to the {% data variables.product.prodname_ghe_server %} site to receive further instructions. -当你请求访问时,我们可能会将你重定向到 {% data variables.product.prodname_ghe_server %} 站点,以检查当前的服务条款。 +When you request access, we may redirect you to the {% data variables.product.prodname_ghe_server %} site to check your current terms of service. {% endif %} diff --git a/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md index c9f9de4bf6..196fc8b6b8 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md @@ -1,7 +1,7 @@ --- title: Enabling unified search for your enterprise shortTitle: Unified search -intro: 'You can allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.product.product_location %}.' +intro: 'You can allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.location.product_location %}.' redirect_from: - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-and-github-com - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-github-com @@ -22,30 +22,30 @@ topics: - GitHub search --- -## About {% data variables.product.prodname_unified_search %} +## About {% data variables.enterprise.prodname_unified_search %} {% data reusables.github-connect.beta %} -When you enable unified search, users can view search results from content on {% data variables.product.prodname_dotcom_the_website %} when searching from {% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}. +When you enable unified search, users can view search results from content on {% data variables.product.prodname_dotcom_the_website %} when searching from {% data variables.location.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}. You can choose to allow search results for public repositories on {% data variables.product.prodname_dotcom_the_website %}, and you can separately choose to allow search results for private repositories on {% data variables.product.prodname_ghe_cloud %}. If you enable unified search for private repositories, users can only search private repositories that they have access to and that are owned by the connected organization or enterprise account. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)." -Users will never be able to search {% data variables.product.product_location %} from {% data variables.product.prodname_dotcom_the_website %}, even if they have access to both environments. +Users will never be able to search {% data variables.location.product_location %} from {% data variables.product.prodname_dotcom_the_website %}, even if they have access to both environments. -After you enable unified search for {% data variables.product.product_location %}, before individual users can see search results from private repositories on {% data variables.product.prodname_dotcom_the_website %} in {% data variables.product.product_location %}, each user must also connect their user account on {% data variables.product.product_name %} with a user account on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search in your private enterprise account](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." +After you enable unified search for {% data variables.location.product_location %}, before individual users can see search results from private repositories on {% data variables.product.prodname_dotcom_the_website %} in {% data variables.location.product_location %}, each user must also connect their user account on {% data variables.product.product_name %} with a user account on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search in your private enterprise account](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." Searching via the REST and GraphQL APIs does not include {% data variables.product.prodname_dotcom_the_website %} search results. Advanced search and searching for wikis in {% data variables.product.prodname_dotcom_the_website %} are not supported. -## Enabling {% data variables.product.prodname_unified_search %} +## Enabling {% data variables.enterprise.prodname_unified_search %} -Before you can enable {% data variables.product.prodname_unified_search %}, you must enable {% data variables.product.prodname_github_connect %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)." +Before you can enable {% data variables.enterprise.prodname_unified_search %}, you must enable {% data variables.product.prodname_github_connect %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)." {% ifversion ghes %} {% data reusables.github-connect.access-dotcom-and-enterprise %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.business %} {% data reusables.enterprise-accounts.github-connect-tab %}{% else %} -1. Sign into {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}. +1. Sign into {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} 1. Under "Users can search {% data variables.product.prodname_dotcom_the_website %}", use the drop-down menu and click **Enabled**. ![Enable search option in the search GitHub.com drop-down menu](/assets/images/enterprise/site-admin-settings/github-dotcom-enable-search.png) diff --git a/translations/zh-CN/content/admin/configuration/configuring-github-connect/index.md b/translations/zh-CN/content/admin/configuration/configuring-github-connect/index.md index a2635ef77f..f0cbe3aeab 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-github-connect/index.md +++ b/translations/zh-CN/content/admin/configuration/configuring-github-connect/index.md @@ -1,6 +1,6 @@ --- -title: 配置 GitHub Connect -intro: '使用 {% data variables.product.prodname_github_connect %},可以通过将 {% data variables.product.product_location %} 连接到 {% data variables.product.prodname_ghe_cloud %} 来访问其他功能和工作流。' +title: Configuring GitHub Connect +intro: 'With {% data variables.product.prodname_github_connect %}, you can access additional features and workflows by connecting {% data variables.location.product_location %} to {% data variables.product.prodname_ghe_cloud %}.' redirect_from: - /enterprise/admin/developer-workflow/connecting-github-enterprise-to-github-com - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-and-github-com @@ -25,11 +25,5 @@ children: - /enabling-unified-search-for-your-enterprise - /enabling-unified-contributions-for-your-enterprise shortTitle: GitHub Connect -ms.openlocfilehash: 6d0be48b952a7bb9abb5c439b5ab276e0b886ec8 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145100093' --- diff --git a/translations/zh-CN/content/admin/configuration/configuring-github-connect/managing-github-connect.md b/translations/zh-CN/content/admin/configuration/configuring-github-connect/managing-github-connect.md index 9786f5cbe4..113d5f293b 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-github-connect/managing-github-connect.md +++ b/translations/zh-CN/content/admin/configuration/configuring-github-connect/managing-github-connect.md @@ -1,7 +1,7 @@ --- -title: 管理 GitHub Connect +title: Managing GitHub Connect shortTitle: Manage GitHub Connect -intro: '可启用 {% data variables.product.prodname_github_connect %} 来访问 {% data variables.product.product_location %} 的其他功能和工作流。' +intro: 'You can enable {% data variables.product.prodname_github_connect %} to access additional features and workflows for {% data variables.location.product_location %}.' redirect_from: - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com @@ -20,63 +20,69 @@ topics: - GitHub Connect - Infrastructure - Networking -ms.openlocfilehash: 0dea06870a1bc7bc951580acf3d83a9d2f0984c2 -ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/12/2022 -ms.locfileid: '146332454' --- + {% data reusables.github-connect.beta %} -## 关于 {% data variables.product.prodname_github_connect %} +## About {% data variables.product.prodname_github_connect %} -可以通过启用 {% data variables.product.prodname_github_connect %} 来访问 {% data variables.product.product_location %} 上的其他功能和工作流。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)”。 +You can access additional features and workflows on {% data variables.location.product_location %} by enabling {% data variables.product.prodname_github_connect %}. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)." -启用 {% data variables.product.prodname_github_connect %} 时,需要在 {% data variables.product.product_location %} 与 {% data variables.product.prodname_ghe_cloud %} 上的组织或企业帐户之间配置连接。 启用 {% data variables.product.prodname_github_connect %} 可以在 {% data variables.product.prodname_ghe_cloud %} 上创建组织或企业帐户所拥有的 {% data variables.product.prodname_github_app %}。 {% data variables.product.product_name %} 使用 {% data variables.product.prodname_github_app %} 的凭据向 {% data variables.product.prodname_ghe_cloud %} 发出请求。 - -{% ifversion ghes %} {% data variables.product.prodname_ghe_server %} 会存储来自 {% data variables.product.prodname_github_app %} 的凭据。 这些凭据将复制到任何高可用性或集群环境中的所有节点,并存储在任何备份中,包括由 {% data variables.product.prodname_enterprise_backup_utilities %} 创建的快照。 -- 有效期为一小时的身份验证令牌 -- 用于生成新的身份验证令牌的私钥 {% endif %} - -## 先决条件 - -若要使用 {% data variables.product.prodname_github_connect %},必须在使用 {% data variables.product.prodname_ghe_cloud %} 的 {% data variables.product.prodname_dotcom_the_website %} 上拥有组织或企业帐户。 你可能已将 {% data variables.product.prodname_ghe_cloud %} 包含在计划中。 {% data reusables.enterprise.link-to-ghec-trial %} - -{% ifversion ghes %} 如果 {% data variables.product.prodname_dotcom_the_website %} 上的组织或企业帐户使用 IP 允许列表,则必须将 {% data variables.product.product_location %} 的 IP 地址或网络添加到 {% data variables.product.prodname_dotcom_the_website %} 上的 IP 允许列表。 有关详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[管理组织的允许 IP 地址](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)”或“[为企业中的安全设置实施策略](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)”。 - -若要配置连接,代理配置必须允许连接到 `github.com`、`api.github.com` 和 `uploads.github.com`。 有关详细信息,请参阅“[配置出站代理服务器](/enterprise/admin/guides/installation/configuring-an-outbound-web-proxy-server)”。 -{% endif %} - -## 启用 {% data variables.product.prodname_github_connect %} - -如果企业所有者同时也是使用 {% data variables.product.prodname_ghe_cloud %} 的组织或企业帐户的所有者,可以启用 {% data variables.product.prodname_github_connect %}。 - -如果要将 {% data variables.product.product_location %} 连接到不归企业帐户拥有的 {% data variables.product.prodname_ghe_cloud %} 上的组织,则必须以组织所有者身份登录到 {% data variables.product.prodname_dotcom_the_website %}。 - -如果要将 {% data variables.product.product_location %} 连接到企业帐户拥有的 {% data variables.product.prodname_ghe_cloud %} 上的组织或者连接到企业帐户本身,则必须以企业所有者身份登录到 {% data variables.product.prodname_dotcom_the_website %}。 +When you enable {% data variables.product.prodname_github_connect %}, you configure a connection between {% data variables.location.product_location %} and an organization or enterprise account on {% data variables.product.prodname_ghe_cloud %}. Enabling {% data variables.product.prodname_github_connect %} creates a {% data variables.product.prodname_github_app %} owned by the organization or enterprise account on {% data variables.product.prodname_ghe_cloud %}. {% data variables.product.product_name %} uses the {% data variables.product.prodname_github_app %}'s credentials to make requests to {% data variables.product.prodname_ghe_cloud %}. {% ifversion ghes %} -1. 登录到 {% data variables.product.product_location %} 和 {% data variables.product.prodname_dotcom_the_website %}。 -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %}{% else %} -1. 登录到 {% data variables.product.product_location %} 和 {% data variables.product.prodname_dotcom_the_website %}。 +{% data variables.product.prodname_ghe_server %} stores credentials from the {% data variables.product.prodname_github_app %}. The following credentials will be replicated to all nodes in a high availability or cluster environment, and stored in any backups, including snapshots created by {% data variables.product.prodname_enterprise_backup_utilities %}. +- An authentication token, which is valid for one hour +- A private key, which is used to generate a new authentication token +{% endif %} + +## Prerequisites + +To use {% data variables.product.prodname_github_connect %}, you must have an organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that uses {% data variables.product.prodname_ghe_cloud %}. You may already have {% data variables.product.prodname_ghe_cloud %} included in your plan. {% data reusables.enterprise.link-to-ghec-trial %} + +{% ifversion ghes %} +If your organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} uses IP allow lists, you must add the IP address or network for {% data variables.location.product_location %} to your IP allow list on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Managing allowed IP addresses for your organization](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)" and "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)" in the {% data variables.product.prodname_ghe_cloud %} documentation. + +To configure a connection, your proxy configuration must allow connectivity to `github.com`, `api.github.com`, and `uploads.github.com`. For more information, see "[Configuring an outbound web proxy server](/enterprise/admin/guides/installation/configuring-an-outbound-web-proxy-server)." +{% endif %} + +## Enabling {% data variables.product.prodname_github_connect %} + +Enterprise owners who are also owners of an organization or enterprise account that uses {% data variables.product.prodname_ghe_cloud %} can enable {% data variables.product.prodname_github_connect %}. + +If you're connecting {% data variables.location.product_location %} to an organization on {% data variables.product.prodname_ghe_cloud %} that is not owned by an enterprise account, you must sign into {% data variables.product.prodname_dotcom_the_website %} as an organization owner. + +If you're connecting {% data variables.location.product_location %} to an organization on {% data variables.product.prodname_ghe_cloud %} that is owned by an enterprise account or to an enterprise account itself, you must sign into {% data variables.product.prodname_dotcom_the_website %} as an enterprise owner. + +{% ifversion ghes %} +1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} -1. 在“{% data variables.product.prodname_github_connect %} 尚未启用”下,单击“启用 {% data variables.product.prodname_github_connect %}”。 单击“启用 {% data variables.product.prodname_github_connect %}”,表示你同意“{% data variables.product.prodname_dotcom %} 其他产品和功能的条款”。 -{% ifversion ghes %} ![“启用 GitHub 连接”按钮](/assets/images/enterprise/business-accounts/enable-github-connect-button.png){% else %} ![“启用 GitHub 连接”按钮](/assets/images/enterprise/github-ae/enable-github-connect-button.png) {% endif %} -1. 在要连接的企业帐户或组织旁,单击“连接”。 - ![企业帐户或企业旁边的“连接”按钮](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png) +1. Under "{% data variables.product.prodname_github_connect %} is not enabled yet", click **Enable {% data variables.product.prodname_github_connect %}**. By clicking **Enable {% data variables.product.prodname_github_connect %}**, you agree to the "{% data variables.product.prodname_dotcom %} Terms for Additional Products and Features." +{% ifversion ghes %} + ![Enable GitHub Connect button](/assets/images/enterprise/business-accounts/enable-github-connect-button.png){% else %} + ![Enable GitHub Connect button](/assets/images/enterprise/github-ae/enable-github-connect-button.png) +{% endif %} +1. Next to the enterprise account or organization you'd like to connect, click **Connect**. + ![Connect button next to an enterprise account or business](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png) -## 禁用 {% data variables.product.prodname_github_connect %} +## Disabling {% data variables.product.prodname_github_connect %} -企业所有者可以禁用 {% data variables.product.prodname_github_connect %}。 +Enterprise owners can disable {% data variables.product.prodname_github_connect %}. -与 {% data variables.product.prodname_ghe_cloud %} 断开连接后,{% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} 会从企业帐户或组织中删除,{% data variables.product.product_location %} 上存储的凭据也会删除。 +When you disconnect from {% data variables.product.prodname_ghe_cloud %}, the {% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} is deleted from your enterprise account or organization and credentials stored on {% data variables.location.product_location %} are deleted. -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %} -1. 在要断开连接的企业帐户或组织旁,单击“禁用 {% data variables.product.prodname_github_connect %}”。 -{% ifversion ghes %} ![企业帐户或组织名称旁的“禁用 GitHub Connect”按钮](/assets/images/enterprise/business-accounts/disable-github-connect-button.png) -1. 阅读有关断开连接的信息,并单击“禁用 {% data variables.product.prodname_github_connect %}”。 - ![包含关于断开连接的警告信息和确认按钮的模式窗口](/assets/images/enterprise/business-accounts/confirm-disable-github-connect.png) -{% else %} ![企业帐户或组织名称旁的“禁用 GitHub Connect”按钮](/assets/images/enterprise/github-ae/disable-github-connect-button.png) -1. 阅读有关断开连接的信息,并单击“禁用 {% data variables.product.prodname_github_connect %}”。 - ![包含关于断开连接的警告信息和确认按钮的模式窗口](/assets/images/enterprise/github-ae/confirm-disable-github-connect.png) {% endif %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.github-connect-tab %} +1. Next to the enterprise account or organization you'd like to disconnect, click **Disable {% data variables.product.prodname_github_connect %}**. +{% ifversion ghes %} + ![Disable GitHub Connect button next to an enterprise account or organization name](/assets/images/enterprise/business-accounts/disable-github-connect-button.png) +1. Read the information about disconnecting and click **Disable {% data variables.product.prodname_github_connect %}**. + ![Modal with warning information about disconnecting and confirmation button](/assets/images/enterprise/business-accounts/confirm-disable-github-connect.png) +{% else %} + ![Disable GitHub Connect button next to an enterprise account or organization name](/assets/images/enterprise/github-ae/disable-github-connect-button.png) +1. Read the information about disconnecting and click **Disable {% data variables.product.prodname_github_connect %}**. + ![Modal with warning information about disconnecting and confirmation button](/assets/images/enterprise/github-ae/confirm-disable-github-connect.png) +{% endif %} diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md index 0957255055..3d37a2c2dc 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md +++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md @@ -1,6 +1,6 @@ --- -title: 配置主机名 -intro: 我们建议为您的设备设置主机名,不建议使用硬编码 IP 地址。 +title: Configuring a hostname +intro: We recommend setting a hostname for your appliance instead of using a hard-coded IP address. redirect_from: - /enterprise/admin/guides/installation/configuring-hostnames - /enterprise/admin/installation/configuring-a-hostname @@ -13,27 +13,27 @@ topics: - Enterprise - Fundamentals - Infrastructure -ms.openlocfilehash: 120827f8eca8061d90d397a7e2a21d46ae33f243 -ms.sourcegitcommit: dc42bb4a4826b414751ffa9eed38962c3e3fea8e -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 07/13/2022 -ms.locfileid: '146681315' --- -如果配置的是主机名,而不是硬编码 IP 地址,你将能够更改运行 {% data variables.product.product_location %} 的物理硬件,而不会影响用户或客户端软件。 +If you configure a hostname instead of a hard-coded IP address, you will be able to change the physical hardware that {% data variables.location.product_location %} runs on without affecting users or client software. -{% data variables.enterprise.management_console %} 中的主机名设置应设置为合适的完全限定域名 (FQDN),此域名可在互联网上或您的内部网络内解析。 例如,你的主机名设置可能是 `github.companyname.com.` Web 和 API 请求将自动重定向到 {% data variables.enterprise.management_console %} 中配置的主机名。 请注意,`localhost` 不是有效的主机名设置。 +The hostname setting in the {% data variables.enterprise.management_console %} should be set to an appropriate fully qualified domain name (FQDN) which is resolvable on the internet or within your internal network. For example, your hostname setting could be `github.companyname.com.` Web and API requests will automatically redirect to the hostname configured in the {% data variables.enterprise.management_console %}. Note that `localhost` is not a valid hostname setting. -配置主机名后,可以启用子域隔离以进一步提高 {% data variables.product.product_location %} 的安全性。 有关详细信息,请参阅“[启用子域隔离](/enterprise/admin/guides/installation/enabling-subdomain-isolation/)”。 +Hostnames must be less than 63 characters in length per [Section 2.3.4 of the Domain Names Specification RFC](https://datatracker.ietf.org/doc/html/rfc1035#section-2.3.4). -有关支持的主机名类型的详细信息,请参阅 [HTTP RFC 第 2.1 节](https://tools.ietf.org/html/rfc1123#section-2)。 +After you configure a hostname, you can enable subdomain isolation to further increase the security of {% data variables.location.product_location %}. For more information, see "[Enabling subdomain isolation](/enterprise/admin/guides/installation/enabling-subdomain-isolation/)." + +For more information on the supported hostname types, see [Section 2.1 of the HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2). {% data reusables.enterprise_installation.changing-hostname-not-supported %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.hostname-menu-item %} -4. 键入要为 {% data variables.product.product_location %} 设置的主机名。 - ![用于设置主机名的字段](/assets/images/enterprise/management-console/hostname-field.png) -5. 要测试新主机名的 DNS 和 SSL 设置,请单击“测试域设置”。 - ![“测试域设置”按钮](/assets/images/enterprise/management-console/test-domain-settings.png) {% data reusables.enterprise_management_console.test-domain-settings-failure %} {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.hostname-menu-item %} +4. Type the hostname you'd like to set for {% data variables.location.product_location %}. + ![Field for setting a hostname](/assets/images/enterprise/management-console/hostname-field.png) +5. To test the DNS and SSL settings for the new hostname, click **Test domain settings**. + ![Test domain settings button](/assets/images/enterprise/management-console/test-domain-settings.png) +{% data reusables.enterprise_management_console.test-domain-settings-failure %} +{% data reusables.enterprise_management_console.save-settings %} -为了帮助缓解各种跨站点脚本漏洞,我们建议您在配置主机名后为 {% data variables.product.product_location %} 启用子域隔离。 有关详细信息,请参阅“[启用子域隔离](/enterprise/admin/guides/installation/enabling-subdomain-isolation/)”。 +To help mitigate various cross-site scripting vulnerabilities, we recommend that you enable subdomain isolation for {% data variables.location.product_location %} after you configure a hostname. For more information, see "[Enabling subdomain isolation](/enterprise/admin/guides/installation/enabling-subdomain-isolation/)." diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md index 5cd6b41368..0bf9da396a 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md +++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md @@ -1,6 +1,6 @@ --- -title: 配置出站 Web 代理服务器 -intro: '代理服务器为 {% data variables.product.product_location %} 额外提供了一级安全性。' +title: Configuring an outbound web proxy server +intro: 'A proxy server provides an additional level of security for {% data variables.location.product_location %}.' redirect_from: - /enterprise/admin/guides/installation/configuring-a-proxy-server - /enterprise/admin/installation/configuring-an-outbound-web-proxy-server @@ -15,32 +15,29 @@ topics: - Infrastructure - Networking shortTitle: Configure an outbound proxy -ms.openlocfilehash: 4285f24dd45d127efec4ace66729bf6fd1f188c5 -ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147875991' --- -## 关于 {% data variables.product.product_name %} 的代理 -为 {% data variables.product.product_location %} 启用代理服务器后,除非已将目标主机添加为 HTTP 代理排除项,否则会先通过代理服务器发送由 {% data variables.product.prodname_ghe_server %} 发送的出站消息。 出站消息类型包括传出 web 挂钩、上传包和提取旧头像。 代理服务器的 URL 由协议、域或 IP 地址外加端口号构成,例如 `http://127.0.0.1:8123`。 +## About proxies with {% data variables.product.product_name %} + +When a proxy server is enabled for {% data variables.location.product_location %}, outbound messages sent by {% data variables.product.prodname_ghe_server %} are first sent through the proxy server, unless the destination host is added as an HTTP proxy exclusion. Types of outbound messages include outgoing webhooks, uploading bundles, and fetching legacy avatars. The proxy server's URL is the protocol, domain or IP address, plus the port number, for example `http://127.0.0.1:8123`. {% note %} -注意:若要将 {% data variables.product.product_location %} 连接到 {% data variables.product.prodname_dotcom_the_website %},代理配置必须允许与 `github.com` 和 `api.github.com` 的连接。 有关详细信息,请参阅“[将企业帐户连接到 {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)”。 +**Note:** To connect {% data variables.location.product_location %} to {% data variables.product.prodname_dotcom_the_website %}, your proxy configuration must allow connectivity to `github.com` and `api.github.com`. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." {% endnote %} -{% data reusables.actions.proxy-considerations %} 有关将 {% data variables.product.prodname_actions %} 与 {% data variables.product.prodname_ghe_server %} 结合使用的详细信息,请参阅“[{% data variables.product.prodname_ghe_server %} 的 {% data variables.product.prodname_actions %} 入门](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)”。 +{% data reusables.actions.proxy-considerations %} For more information about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)." -## 配置出站 Web 代理服务器 +## Configuring an outbound web proxy server -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} -1. 在“HTTP 代理服务器”下,键入代理服务器的 URL。 - ![用于输入 HTTP 代理服务器 URL 的字段](/assets/images/enterprise/management-console/http-proxy-field.png) +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +1. Under **HTTP Proxy Server**, type the URL of your proxy server. + ![Field to type the HTTP Proxy Server URL](/assets/images/enterprise/management-console/http-proxy-field.png) -5. 或者在“HTTP 代理排除项”下输入不需要进行代理访问权限的任意主机,并以逗号分隔主机。 要将域中的所有主机排除在“需要代理访问权限”的要求之外,可以使用 `.` 作为通配符前缀。 例如:`.octo-org.tentacle` - ![键入任何 HTTP 代理排除项的字段](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) +5. Optionally, under **HTTP Proxy Exclusion**, type any hosts that do not require proxy access, separating hosts with commas. To exclude all hosts in a domain from requiring proxy access, you can use `.` as a wildcard prefix. For example: `.octo-org.tentacle` + ![Field to type any HTTP Proxy Exclusions](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md index 01ed795aa4..7a0088680e 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md +++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md @@ -1,6 +1,6 @@ --- -title: 配置内置防火墙规则 -intro: '可以查看默认防火墙规则并自定义 {% data variables.product.product_location %} 的规则。' +title: Configuring built-in firewall rules +intro: 'You can view default firewall rules and customize rules for {% data variables.location.product_location %}.' redirect_from: - /enterprise/admin/guides/installation/configuring-firewall-settings - /enterprise/admin/installation/configuring-built-in-firewall-rules @@ -15,25 +15,19 @@ topics: - Infrastructure - Networking shortTitle: Configure firewall rules -ms.openlocfilehash: 7492f69c6b334847229c76f7462beaabbc4154a2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145100090' --- -## 关于 {% data variables.product.product_location %} 的防火墙 +## About {% data variables.location.product_location %}'s firewall -{% data variables.product.prodname_ghe_server %} 在虚拟设备上使用 Ubuntu 的简单防火墙 (UFW)。 有关详细信息,请参阅 Ubuntu 文档中的 [UFW](https://help.ubuntu.com/community/UFW)。 {% data variables.product.prodname_ghe_server %} 在每次发布时都会自动更新允许服务的防火墙允许名单。 +{% data variables.product.prodname_ghe_server %} uses Ubuntu's Uncomplicated Firewall (UFW) on the virtual appliance. For more information see "[UFW](https://help.ubuntu.com/community/UFW)" in the Ubuntu documentation. {% data variables.product.prodname_ghe_server %} automatically updates the firewall allowlist of allowed services with each release. -安装 {% data variables.product.prodname_ghe_server %} 之后,所有必要的网络端口都会自动打开,以接受连接。 每个非必要的端口都会自动配置为 `deny`,默认传出策略会配置为 `allow`。 会为任何新连接启用状态跟踪;这些连接通常是设置了 `SYN` 位的网络数据包。 有关详细信息,请参阅“[网络端口](/enterprise/admin/guides/installation/network-ports)”。 +After you install {% data variables.product.prodname_ghe_server %}, all required network ports are automatically opened to accept connections. Every non-required port is automatically configured as `deny`, and the default outgoing policy is configured as `allow`. Stateful tracking is enabled for any new connections; these are typically network packets with the `SYN` bit set. For more information, see "[Network ports](/enterprise/admin/guides/installation/network-ports)." -UFW 防火墙还会打开 {% data variables.product.prodname_ghe_server %} 所需的其他多个端口才能正常运行。 有关 UFW 规则集的详细信息,请参阅 [UFW 自述文件](https://bazaar.launchpad.net/~jdstrand/ufw/0.30-oneiric/view/head:/README#L213)。 +The UFW firewall also opens several other ports that are required for {% data variables.product.prodname_ghe_server %} to operate properly. For more information on the UFW rule set, see [the UFW README](https://bazaar.launchpad.net/~jdstrand/ufw/0.30-oneiric/view/head:/README#L213). -## 查看默认防火墙规则 +## Viewing the default firewall rules {% data reusables.enterprise_installation.ssh-into-instance %} -2. 若要查看默认防火墙规则,请使用 `sudo ufw status` 命令。 此时会看到与下面类似的输出: +2. To view the default firewall rules, use the `sudo ufw status` command. You should see output similar to this: ```shell $ sudo ufw status > Status: active @@ -61,46 +55,46 @@ UFW 防火墙还会打开 {% data variables.product.prodname_ghe_server %} 所 > ghe-9418 (v6) ALLOW Anywhere (v6) ``` -## 添加自定义防火墙规则 +## Adding custom firewall rules {% warning %} -警告:在添加自定义防火墙规则之前,请备份当前规则,以便在需要时可以重置为已知的工作状态。 如果您被锁定在服务器之外,请与 {% data variables.contact.contact_ent_support %} 联系,以重新配置原始防火墙规则。 恢复原始防火墙规则会导致服务器停机。 +**Warning:** Before you add custom firewall rules, back up your current rules in case you need to reset to a known working state. If you're locked out of your server, contact {% data variables.contact.contact_ent_support %} to reconfigure the original firewall rules. Restoring the original firewall rules involves downtime for your server. {% endwarning %} -1. 配置自定义防火墙规则。 -2. 使用 `status numbered` 命令检查每条新规则的状态。 +1. Configure a custom firewall rule. +2. Check the status of each new rule with the `status numbered` command. ```shell $ sudo ufw status numbered ``` -3. 要备份自定义防火墙规则,请使用 `cp` 命令将规则移动到新文件。 +3. To back up your custom firewall rules, use the `cp`command to move the rules to a new file. ```shell $ sudo cp -r /etc/ufw ~/ufw.backup ``` -升级 {% data variables.product.product_location %} 后,必须重新应用自定义防火墙规则。 我们建议您创建脚本来重新应用防火墙自定义规则。 +After you upgrade {% data variables.location.product_location %}, you must reapply your custom firewall rules. We recommend that you create a script to reapply your firewall custom rules. -## 恢复默认防火墙规则 +## Restoring the default firewall rules -如果更改防火墙规则后出现问题,您可以通过原始备份重置规则。 +If something goes wrong after you change the firewall rules, you can reset the rules from your original backup. {% warning %} -警告:如果对防火墙进行更改之前未备份原始规则,请联系 {% data variables.contact.contact_ent_support %} 获取更多帮助。 +**Warning:** If you didn't back up the original rules before making changes to the firewall, contact {% data variables.contact.contact_ent_support %} for further assistance. {% endwarning %} {% data reusables.enterprise_installation.ssh-into-instance %} -2. 要还原之前的备份规则,请使用 `cp` 命令将规则复制到防火墙。 +2. To restore the previous backup rules, copy them back to the firewall with the `cp` command. ```shell $ sudo cp -f ~/ufw.backup/*rules /etc/ufw ``` -3. 使用 `systemctl` 命令重启防火墙。 +3. Restart the firewall with the `systemctl` command. ```shell $ sudo systemctl restart ufw ``` -4. 使用 `ufw status` 命令确认规则已恢复为默认状态。 +4. Confirm that the rules are back to their defaults with the `ufw status` command. ```shell $ sudo ufw status > Status: active diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md index d5963bdaef..04ddd6fa9e 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md +++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md @@ -1,6 +1,6 @@ --- -title: 配置 DNS 域名服务器 -intro: '在 DHCP 租约提供域名服务器时,{% data variables.product.prodname_ghe_server %} 将为 DNS 设置使用动态主机配置协议 (DHCP)。 如果域名服务器不是由动态主机配置协议 (DHCP) 租约提供,或者您需要使用特定的 DNS 设置,可以手动指定域名服务器。' +title: Configuring DNS nameservers +intro: '{% data variables.product.prodname_ghe_server %} uses the dynamic host configuration protocol (DHCP) for DNS settings when DHCP leases provide nameservers. If nameservers are not provided by a dynamic host configuration protocol (DHCP) lease, or if you need to use specific DNS settings, you can specify the nameservers manually.' redirect_from: - /enterprise/admin/guides/installation/about-dns-nameservers - /enterprise/admin/installation/configuring-dns-nameservers @@ -15,34 +15,28 @@ topics: - Infrastructure - Networking shortTitle: Configure DNS servers -ms.openlocfilehash: b01dc25b9002bf1feb672bbce597c8046b93f12f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147419711' --- -指定的名称服务器必须解析 {% data variables.product.product_location %} 的主机名。 +The nameservers you specify must resolve {% data variables.location.product_location %}'s hostname. {% data reusables.enterprise_installation.changing-hostname-not-supported %} -## 使用虚拟机控制台配置域名服务器 +## Configuring nameservers using the virtual machine console {% data reusables.enterprise_installation.open-vm-console-start %} -2. 为实例配置域名服务器。 +2. Configure nameservers for your instance. {% data reusables.enterprise_installation.vm-console-done %} -## 使用管理 shell 配置域名服务器 +## Configuring nameservers using the administrative shell {% data reusables.enterprise_installation.ssh-into-instance %} -2. 要编辑名称服务器,请在可视模式下使用 `ghe-setup-network` 命令。 有关详细信息,请参阅“[命令行实用工具](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-setup-network)”。 +2. To edit your nameservers, use the `ghe-setup-network` command in visual mode. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-setup-network)." ```shell ghe-setup-network -v ``` -5. 要向 {% data variables.product.product_location %} 添加新的域名服务器条目,请运行以下命令: +5. To add your new nameserver entries to {% data variables.location.product_location %}, run the following: ```shell sudo service resolvconf restart diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md index 35f0184250..bebfbb14fe 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md +++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md @@ -1,6 +1,6 @@ --- -title: 配置 TLS -intro: '你可以在 {% data variables.product.product_location %} 上配置传输层安全性 (TLS),以便使用由可信证书颁发机构签名的证书。' +title: Configuring TLS +intro: 'You can configure Transport Layer Security (TLS) on {% data variables.location.product_location %} so that you can use a certificate that is signed by a trusted certificate authority.' redirect_from: - /enterprise/admin/articles/ssl-configuration - /enterprise/admin/guides/installation/about-tls @@ -16,68 +16,70 @@ topics: - Infrastructure - Networking - Security -ms.openlocfilehash: c11f78b69f5b251a63c0796d46bca4d6c926f002 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146682331' --- -## 关于传输层安全 +## About Transport Layer Security -当 {% data variables.product.prodname_ghe_server %} 首次启动时,会启用 TLS(替代了 SSL)并通过自签名证书进行配置。 由于自签名证书不受 Web 浏览器和 Git 客户端的信任,因此这些客户端将报告证书警告,直至您禁用 TLS 或上传由 Let's Encrypt 等可信颁发机构签名的证书。 +TLS, which replaced SSL, is enabled and configured with a self-signed certificate when {% data variables.product.prodname_ghe_server %} is started for the first time. As self-signed certificates are not trusted by web browsers and Git clients, these clients will report certificate warnings until you disable TLS or upload a certificate signed by a trusted authority, such as Let's Encrypt. -{% data variables.product.prodname_ghe_server %} 设备将在 SSL 启用时发送 HTTP 严格传输安全标头。 禁用 TLS 会导致用户无法访问设备,因为用户的浏览器将不允许协议降级为 HTTP。 有关详细信息,请参阅维基百科上的“[HTTP 严格传输安全 (HSTS)](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)”。 +The {% data variables.product.prodname_ghe_server %} appliance will send HTTP Strict Transport Security headers when SSL is enabled. Disabling TLS will cause users to lose access to the appliance, because their browsers will not allow a protocol downgrade to HTTP. For more information, see "[HTTP Strict Transport Security (HSTS)](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)" on Wikipedia. {% data reusables.enterprise_installation.terminating-tls %} -要允许用户使用 FIDO U2F 进行双重身份验证,您必须为实例启用 TLS。 有关详细信息,请参阅“[配置双因素身份验证](/articles/configuring-two-factor-authentication)”。 +To allow users to use FIDO U2F for two-factor authentication, you must enable TLS for your instance. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)." -## 先决条件 +## Prerequisites -要在生产中使用 TLS,您必须具有由可信证书颁发机构签名的未加密 PEM 格式的证书。 +To use TLS in production, you must have a certificate in an unencrypted PEM format signed by a trusted certificate authority. -证书还需要为“[启用子域隔离](/enterprise/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)”中列出的子域配置使用者可选名称,如果证书已由中间证书颁发机构签名,将需要包含完整的证书链。 有关详细信息,请参阅维基百科上的“[使用者可选名称](http://en.wikipedia.org/wiki/SubjectAltName)”。 +Your certificate will also need Subject Alternative Names configured for the subdomains listed in "[Enabling subdomain isolation](/enterprise/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)" and will need to include the full certificate chain if it has been signed by an intermediate certificate authority. For more information, see "[Subject Alternative Name](http://en.wikipedia.org/wiki/SubjectAltName)" on Wikipedia. -可使用 `ghe-ssl-generate-csr` 命令为实例生成证书签名请求 (CSR)。 有关详细信息,请参阅“[命令行实用程序](/enterprise/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)”。 +You can generate a certificate signing request (CSR) for your instance using the `ghe-ssl-generate-csr` command. For more information, see "[Command-line utilities](/enterprise/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)." -密钥必须是 RSA 密钥,并且不能有密码。 有关详细信息,请参阅“[从密钥文件中删除密码](/admin/guides/installation/troubleshooting-ssl-errors#removing-the-passphrase-from-your-key-file)。 +Your key must be an RSA key and must not have a passphrase. For more information, see "[Removing the passphrase from your key file](/admin/guides/installation/troubleshooting-ssl-errors#removing-the-passphrase-from-your-key-file)". -## 上传自定义 TLS 证书 +## Uploading a custom TLS certificate {% data reusables.enterprise_site_admin_settings.tls-downtime %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} {% data reusables.enterprise_management_console.select-tls-only %} -4. 在“TLS Protocol support”下,选择您想要允许的协议。 - ![包含用于选择 TLS 协议的选项的单选按钮](/assets/images/enterprise/management-console/tls-protocol-support.png) -5. 在“证书”下,单击“选择文件”以选择要安装的 TLS 证书或证书链(PEM 格式)。 此文件通常采用 .pem、.crt 或 .cer 扩展名 。 - ![用于查找 TLS 证书文件的按钮](/assets/images/enterprise/management-console/install-tls-certificate.png) -6. 在“未加密密钥”下,单击“选择文件”以选择要安装的 RSA 密钥(PEM 格式)。 此文件通常采用 .key 扩展名。 - ![用于查找 TLS 密钥文件的按钮](/assets/images/enterprise/management-console/install-tls-key.png) +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +{% data reusables.enterprise_management_console.select-tls-only %} +4. Under "TLS Protocol support", select the protocols you want to allow. + ![Radio buttons with options to choose TLS protocols](/assets/images/enterprise/management-console/tls-protocol-support.png) +5. Under "Certificate", click **Choose File** to choose a TLS certificate or certificate chain (in PEM format) to install. This file will usually have a *.pem*, *.crt*, or *.cer* extension. + ![Button to find TLS certificate file](/assets/images/enterprise/management-console/install-tls-certificate.png) +6. Under "Unencrypted key", click **Choose File** to choose an RSA key (in PEM format) to install. This file will usually have a *.key* extension. + ![Button to find TLS key file](/assets/images/enterprise/management-console/install-tls-key.png) {% data reusables.enterprise_management_console.save-settings %} -## 关于 Let's Encrypt 支持 +## About Let's Encrypt support -Let's Encrypt 是公共证书颁发机构,他们使用 ACME 协议颁发受浏览器信任的免费、自动化 TLS 证书。 您可以在设备上自动获取并续订 Let's Encrypt 证书,无需手动维护。 +Let's Encrypt is a public certificate authority that issues free, automated TLS certificates that are trusted by browsers using the ACME protocol. You can automatically obtain and renew Let's Encrypt certificates on your appliance without any required manual maintenance. {% data reusables.enterprise_installation.lets-encrypt-prerequisites %} -在使用 Let's Encrypt 启用 TLS 证书管理自动化后,{% data variables.product.product_location %} 将与 Let's Encrypt 服务器通信,以获取证书。 要续订证书,Let's Encrypt 服务器必须通过入站 HTTP 请求验证已配置域名的控制。 +When you enable automation of TLS certificate management using Let's Encrypt, {% data variables.location.product_location %} will contact the Let's Encrypt servers to obtain a certificate. To renew a certificate, Let's Encrypt servers must validate control of the configured domain name with inbound HTTP requests. -还可以在 {% data variables.product.product_location %} 上使用 `ghe-ssl-acme` 命令行实用程序自动生成 Let's Encrypt 证书。 有关详细信息,请参阅“[命令行实用程序](/enterprise/admin/guides/installation/command-line-utilities#ghe-ssl-acme)”。 +You can also use the `ghe-ssl-acme` command line utility on {% data variables.location.product_location %} to automatically generate a Let's Encrypt certificate. For more information, see "[Command-line utilities](/enterprise/admin/guides/installation/command-line-utilities#ghe-ssl-acme)." -## 使用 Let's Encrypt 配置 TLS +## Configuring TLS using Let's Encrypt {% data reusables.enterprise_installation.lets-encrypt-prerequisites %} {% data reusables.enterprise_site_admin_settings.tls-downtime %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} {% data reusables.enterprise_management_console.select-tls-only %} -5. 选择“使用 Let's Encrypt 启用 TLS 证书管理自动化”。 - ![用于启用 Let's Encrypt 的复选框](/assets/images/enterprise/management-console/lets-encrypt-checkbox.png) {% data reusables.enterprise_management_console.save-settings %} {% data reusables.enterprise_management_console.privacy %} -7. 单击“请求 TLS 证书”。 - ![“请求 TLS 证书”按钮](/assets/images/enterprise/management-console/request-tls-button.png) -8. 等待“状态”从“开始”更改为“完成”。 - ![Let's Encrypt 状态](/assets/images/enterprise/management-console/lets-encrypt-status.png) -9. 单击“保存配置”。 +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +{% data reusables.enterprise_management_console.select-tls-only %} +5. Select **Enable automation of TLS certificate management using Let's Encrypt**. + ![Checkbox to enable Let's Encrypt](/assets/images/enterprise/management-console/lets-encrypt-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_management_console.privacy %} +7. Click **Request TLS certificate**. + ![Request TLS certificate button](/assets/images/enterprise/management-console/request-tls-button.png) +8. Wait for the "Status" to change from "STARTED" to "DONE". + ![Let's Encrypt status](/assets/images/enterprise/management-console/lets-encrypt-status.png) +9. Click **Save configuration**. diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md index 7c91b5e75b..e1dcf2af52 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md +++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md @@ -1,6 +1,6 @@ --- -title: 启用子域隔离 -intro: '您可以设置子域隔离,将用户提供的内容与 {% data variables.product.prodname_ghe_server %} 设备的其他部分安全地隔离。' +title: Enabling subdomain isolation +intro: 'You can set up subdomain isolation to securely separate user-supplied content from other portions of your {% data variables.product.prodname_ghe_server %} appliance.' redirect_from: - /enterprise/admin/guides/installation/about-subdomain-isolation - /enterprise/admin/installation/enabling-subdomain-isolation @@ -16,20 +16,14 @@ topics: - Networking - Security shortTitle: Enable subdomain isolation -ms.openlocfilehash: ec7b04f845d0ec44c3234ece0194d4396df54892 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146332550' --- -## 关于子域隔离 +## About subdomain isolation -子域隔离可以减少跨站脚本和其他相关漏洞。 有关详细信息,请参阅维基百科上的“[跨站脚本](http://en.wikipedia.org/wiki/Cross-site_scripting)”。 强烈建议在 {% data variables.product.product_location %}. 上启用子域隔离。 +Subdomain isolation mitigates cross-site scripting and other related vulnerabilities. For more information, see "[Cross-site scripting](http://en.wikipedia.org/wiki/Cross-site_scripting)" on Wikipedia. We highly recommend that you enable subdomain isolation on {% data variables.location.product_location %}. -启用子域隔离后,{% data variables.product.prodname_ghe_server %} 会以子域替代多个路径。 启用子域隔离后,尝试访问某些用户提供内容的以前的路径(如 `http(s)://HOSTNAME/raw/`)可能会返回 `404` 错误。 +When subdomain isolation is enabled, {% data variables.product.prodname_ghe_server %} replaces several paths with subdomains. After enabling subdomain isolation, attempts to access the previous paths for some user-supplied content, such as `http(s)://HOSTNAME/raw/`, may return `404` errors. -| 未使用子域隔离的路径 | 使用子域隔离的路径 | +| Path without subdomain isolation | Path with subdomain isolation | | --- | --- | | `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | | `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | @@ -46,24 +40,27 @@ ms.locfileid: '146332550' | `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %}{% ifversion ghes > 3.4 %} -| 不支持 | `https://containers.HOSTNAME/` |{% endif %} +| Not supported | `https://containers.HOSTNAME/` |{% endif %} -## 先决条件 +## Prerequisites {% data reusables.enterprise_installation.disable-github-pages-warning %} -启用子域隔离之前,您必须为新域配置网络设置。 +Before you enable subdomain isolation, you must configure your network settings for your new domain. -- 指定有效域名作为主机名,而不是指定 IP 地址。 有关详细信息,请参阅“[配置主机名](/enterprise/admin/guides/installation/configuring-a-hostname)”。 +- Specify a valid domain name as your hostname, instead of an IP address. For more information, see "[Configuring a hostname](/enterprise/admin/guides/installation/configuring-a-hostname)." {% data reusables.enterprise_installation.changing-hostname-not-supported %} -- 为上文列出的子域设置通配符域名系统 (DNS) 记录或单独的 DNS 记录。 建议为指向服务器 IP 地址的 `*.HOSTNAME` 创建一条 A 记录,从而无需为各个子域创建多条记录。 -- 为 `*.HOSTNAME` 获取一个使用者可选名称 (SAN) 同时适用于 `HOSTNAME` 和通配符域 `*.HOSTNAME` 的通配符传输层安全 (TLS) 证书。 例如,如果主机名为 `github.octoinc.com`,则获取一个公用名值设为 `*.github.octoinc.com`、SAN 值同时设为 `github.octoinc.com` 和 `*.github.octoinc.com` 的证书。 -- 在设备上启用 TLS。 有关详细信息,请参阅“[配置 TLS](/enterprise/admin/guides/installation/configuring-tls/)”。 +- Set up a wildcard Domain Name System (DNS) record or individual DNS records for the subdomains listed above. We recommend creating an A record for `*.HOSTNAME` that points to your server's IP address so you don't have to create multiple records for each subdomain. +- Get a wildcard Transport Layer Security (TLS) certificate for `*.HOSTNAME` with a Subject Alternative Name (SAN) for both `HOSTNAME` and the wildcard domain `*.HOSTNAME`. For example, if your hostname is `github.octoinc.com`, get a certificate with the Common Name value set to `*.github.octoinc.com` and a SAN value set to both `github.octoinc.com` and `*.github.octoinc.com`. +- Enable TLS on your appliance. For more information, see "[Configuring TLS](/enterprise/admin/guides/installation/configuring-tls/)." -## 启用子域隔离 +## Enabling subdomain isolation -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.hostname-menu-item %} -4. 选择“子域隔离(建议)”。 - ![用于启用子域隔离的复选框](/assets/images/enterprise/management-console/subdomain-isolation.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.hostname-menu-item %} +4. Select **Subdomain isolation (recommended)**. + ![Checkbox to enable subdomain isolation](/assets/images/enterprise/management-console/subdomain-isolation.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/network-ports.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/network-ports.md index 31f17e021a..576fc56eeb 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/network-ports.md +++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/network-ports.md @@ -1,5 +1,5 @@ --- -title: 网络端口 +title: Network ports redirect_from: - /enterprise/admin/articles/configuring-firewalls - /enterprise/admin/articles/firewall @@ -8,7 +8,7 @@ redirect_from: - /enterprise/admin/installation/network-ports - /enterprise/admin/configuration/network-ports - /admin/configuration/network-ports -intro: 根据您需要为管理员、最终用户和电子邮件支持显示的网络服务有选择地打开网络端口。 +intro: 'Open network ports selectively based on the network services you need to expose for administrators, end users, and email support.' versions: ghes: '*' type: reference @@ -17,58 +17,52 @@ topics: - Infrastructure - Networking - Security -ms.openlocfilehash: eab2bed3f07c3e9e7ebad900047c1aa74a1d0bc1 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145100081' --- -## 管理端口 +## Administrative ports -配置 {% data variables.product.product_location %} 并运行某些功能需要一些管理端口。 最终用户在使用基本应用程序时不需要管理端口。 +Some administrative ports are required to configure {% data variables.location.product_location %} and run certain features. Administrative ports are not required for basic application use by end users. -| 端口 | 服务 | 说明 | +| Port | Service | Description | |---|---|---| -| 8443 | HTTPS | 基于安全 Web 的 {% data variables.enterprise.management_console %}。 进行基本安装和配置时需要。 | -| 8080 | HTTP | 基于纯文本 Web 的 {% data variables.enterprise.management_console %}。 除非手动禁用 TLS,否则不需要。 | -| 122 | SSH | {% data variables.product.product_location %} 的 shell 访问权限。 需要对高可用性配置中所有节点之间的传入连接开放。 默认 SSH 端口 (22) 专用于 Git 和 SSH 应用程序网络流量。 | -| 1194/UDP | VPN | 采用高可用性配置的安全复制网络隧道。 需要对配置中所有节点之间的通信开放。| -| 123/UDP| NTP | 为时间协议操作所需。 | -| 161/UDP | SNMP | 为网络监视协议操作所需。 | +| 8443 | HTTPS | Secure web-based {% data variables.enterprise.management_console %}. Required for basic installation and configuration. | +| 8080 | HTTP | Plain-text web-based {% data variables.enterprise.management_console %}. Not required unless TLS is disabled manually. | +| 122 | SSH | Shell access for {% data variables.location.product_location %}. Required to be open to incoming connections between all nodes in a high availability configuration. The default SSH port (22) is dedicated to Git and SSH application network traffic. | +| 1194/UDP | VPN | Secure replication network tunnel in high availability configuration. Required to be open for communication between all nodes in the configuration.| +| 123/UDP| NTP | Required for time protocol operation. | +| 161/UDP | SNMP | Required for network monitoring protocol operation. | -## 最终用户的应用程序端口 +## Application ports for end users -应用程序端口为最终用户提供 Web 应用程序和 Git 访问。 +Application ports provide web application and Git access for end users. -| 端口 | 服务 | 说明 | +| Port | Service | Description | |---|---|---| -| 443 | HTTPS | 通过 HTTPS 访问 Web 应用程序和 Git。 | -| 80 | HTTP | 访问 Web 应用程序。 如果配置了 TLS,则所有请求都将重定向到 HTTPS 端口。 | -| 22 | SSH | 通过 SSH 访问 Git。 支持对公共和私有仓库执行克隆、提取和推送操作。 | -| 9418 | Git | Git 协议端口支持通过未加密网络通信对公共仓库执行克隆和提取操作。 {% data reusables.enterprise_installation.when-9418-necessary %} | +| 443 | HTTPS | Access to the web application and Git over HTTPS. | +| 80 | HTTP | Access to the web application. All requests are redirected to the HTTPS port if TLS is configured. | +| 22 | SSH | Access to Git over SSH. Supports clone, fetch, and push operations to public and private repositories. | +| 9418 | Git | Git protocol port supports clone and fetch operations to public repositories with unencrypted network communication. {% data reusables.enterprise_installation.when-9418-necessary %} | {% data reusables.enterprise_installation.terminating-tls %} -## 电子邮件端口 +## Email ports -电子邮件端口必须可直接访问或通过中继访问,以便为最终用户提供入站电子邮件支持。 +Email ports must be accessible directly or via relay for inbound email support for end users. -| 端口 | 服务 | 说明 | +| Port | Service | Description | |---|---|---| -| 25 | SMTP | 支持采用加密的 SMTP (STARTTLS)。 | +| 25 | SMTP | Support for SMTP with encryption (STARTTLS). | -## {% data variables.product.prodname_actions %} 端口 +## {% data variables.product.prodname_actions %} ports -{% data variables.product.prodname_actions %} 端口必须可供自托管运行器访问才能连接到 {% data variables.product.product_location %}。 有关详细信息,请参阅[关于自承载运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-server)。 +{% data variables.product.prodname_actions %} ports must be accessible for self-hosted runners to connect to {% data variables.location.product_location %}. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-server)." -| 端口 | 服务 | 说明 | +| Port | Service | Description | |---|---|---| -| 443 | HTTPS | 自托管运行器连接到 {% data variables.product.product_location %} 以接收作业分配并下载新版本的运行器应用程序。 如果配置了 TLS 则必填。 -| 80 | HTTP | 自托管运行器连接到 {% data variables.product.product_location %} 以接收作业分配并下载新版本的运行器应用程序。 如果未配置 TLS 则必填。 +| 443 | HTTPS | Self-hosted runners connect to {% data variables.location.product_location %} to receive job assignments and to download new versions of the runner application. Required if TLS is configured. +| 80 | HTTP | Self-hosted runners connect to {% data variables.location.product_location %} to receive job assignments and to download new versions of the runner application. Required if TLS is not configured. -如果启用对 {% data variables.product.prodname_dotcom_the_website %} 操作的自动访问, {% data variables.product.prodname_actions %} 将始终先通过这些端口搜索 {% data variables.product.product_location %} 上的操作,然后再检查 {% data variables.product.prodname_dotcom_the_website %}。 有关详细信息,请参阅“[使用 {% data variables.product.prodname_github_connect %} 启用对 {% data variables.product.prodname_dotcom_the_website %} 操作的自动访问](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#about-resolution-for-actions-using-github-connect)”。 +If you enable automatic access to {% data variables.product.prodname_dotcom_the_website %} actions, {% data variables.product.prodname_actions %} will always search for an action on {% data variables.location.product_location %} first, via these ports, before checking {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#about-resolution-for-actions-using-github-connect)." -## 延伸阅读 +## Further reading -- “[配置 TLS](/admin/configuration/configuring-network-settings/configuring-tls)” +- "[Configuring TLS](/admin/configuration/configuring-network-settings/configuring-tls)" diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md index 533bde5cb6..955ed62c25 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md +++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md @@ -1,6 +1,6 @@ --- -title: 结合使用 GitHub Enterprise Server 和负载均衡器 -intro: '在单个 {% data variables.product.prodname_ghe_server %} 设备或一对采用高可用性配置的示例前方使用负载均衡器。' +title: Using GitHub Enterprise Server with a load balancer +intro: 'Use a load balancer in front of a single {% data variables.product.prodname_ghe_server %} instance or a pair of instances in a High Availability configuration.' redirect_from: - /enterprise/admin/guides/installation/using-github-enterprise-with-a-load-balancer - /enterprise/admin/installation/using-github-enterprise-server-with-a-load-balancer @@ -15,22 +15,17 @@ topics: - Infrastructure - Networking shortTitle: Use a load balancer -ms.openlocfilehash: dcbd1261d127e48140f6b6843ef4ec3c35fb84f4 -ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/12/2022 -ms.locfileid: '147167313' --- -## 关于负载均衡器 + +## About load balancers {% data reusables.enterprise_clustering.load_balancer_intro %} {% data reusables.enterprise_clustering.load_balancer_dns %} -## 处理客户端连接信息 +## Handling client connection information -由于与 {% data variables.product.prodname_ghe_server %} 的客户端连接来自负载均衡器,因此客户端 IP 可丢失。 +Because client connections to {% data variables.product.prodname_ghe_server %} come from the load balancer, the client IP address can be lost. {% data reusables.enterprise_clustering.proxy_preference %} @@ -38,63 +33,70 @@ ms.locfileid: '147167313' {% data reusables.enterprise_installation.terminating-tls %} -### 在 {% data variables.product.product_location %} 上启用 PROXY 协议支持 +### Enabling PROXY protocol support on {% data variables.location.product_location %} -强烈建议同时为实例和负载均衡器启用 PROXY 协议支持。 按照您的供应商提供的说明操作,在负载均衡器上启用 PROXY 协议。 有关详细信息,请参阅 [PROXY 协议文档](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt)。 +We strongly recommend enabling PROXY protocol support for both your instance and the load balancer. Use the instructions provided by your vendor to enable the PROXY protocol on your load balancer. For more information, see [the PROXY protocol documentation](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt). {% data reusables.enterprise_installation.proxy-incompatible-with-aws-nlbs %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} -3. 在“外部负载均衡器”下,选择“启用对 PROXY 协议的支持” 。 -![用于启用对 PROXY 协议的支持的复选框](/assets/images/enterprise/management-console/enable-proxy.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +3. Under **External load balancers**, select **Enable support for PROXY protocol**. +![Checkbox to enable support for PROXY protocol](/assets/images/enterprise/management-console/enable-proxy.png) +{% data reusables.enterprise_management_console.save-settings %} {% data reusables.enterprise_clustering.proxy_protocol_ports %} -### 在 {% data variables.product.product_location %} 上启用 X-Forwarded-For 支持 +### Enabling X-Forwarded-For support on {% data variables.location.product_location %} {% data reusables.enterprise_clustering.x-forwarded-for %} {% warning %} -警告:如果在 {% data variables.product.product_location %} 和负载均衡器上配置 `X-Forwarded-For` 支持,则可能无法连接到 {% data variables.enterprise.management_console %}。 有关详细信息,请参阅“[错误:“会话已过期”,无法连接到 {% data variables.enterprise.management_console %}](/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer#error-your-session-has-expired-for-connections-to-the-management-console)”。 +**Warning**: If you configure `X-Forwarded-For` support on {% data variables.location.product_location %} and load balancer, you may not be able to connect to the {% data variables.enterprise.management_console %}. For more information, see "[Error: "Your session has expired" for connections to the {% data variables.enterprise.management_console %}](/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer#error-your-session-has-expired-for-connections-to-the-management-console)." {% endwarning %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} -3. 在“外部负载均衡器”下,选择“允许 HTTP X-Forwarded-For 标头” 。 -![用于允许 HTTP X-Forwarded-For 标头的复选框](/assets/images/enterprise/management-console/allow-xff.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +3. Under **External load balancers**, select **Allow HTTP X-Forwarded-For header**. +![Checkbox to allow the HTTP X-Forwarded-For header](/assets/images/enterprise/management-console/allow-xff.png) +{% data reusables.enterprise_management_console.save-settings %} {% data reusables.enterprise_clustering.without_proxy_protocol_ports %} -## 配置健康状态检查 +## Configuring health checks -如果预配置的检查在该节点上失败,则状态检查允许负载均衡器停止向未响应的节点发送流量。 如果实例因维护或计划外的故障而离线,负载均衡器可以显示状态页面。 在高可用性 (HA) 配置下,负载均衡器可用作故障转移策略的组成部分。 不过,不支持 HA 对的自动故障转移。 在副本示例设备开始为请求提供服务之前,你必须对其进行手动升级。 有关详细信息,请参阅“[为高可用性配置 {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)。” +Health checks allow a load balancer to stop sending traffic to a node that is not responding if a pre-configured check fails on that node. If the instance is offline due to maintenance or unexpected failure, the load balancer can display a status page. In a High Availability (HA) configuration, a load balancer can be used as part of a failover strategy. However, automatic failover of HA pairs is not supported. You must manually promote the replica instance before it will begin serving requests. For more information, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/enterprise/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)." -{% data reusables.enterprise_clustering.health_checks %} {% data reusables.enterprise_site_admin_settings.maintenance-mode-status %} +{% data reusables.enterprise_clustering.health_checks %} +{% data reusables.enterprise_site_admin_settings.maintenance-mode-status %} -## 通过负载均衡器排查连接问题 +## Troubleshooting connectivity through a load balancer -如果无法通过负载均衡器连接到 {% data variables.product.product_location %} 上的服务,可以查看以下信息来解决问题。 +If you cannot connect to services on {% data variables.location.product_location %} through a load balancer, you can review the following information to troubleshoot the problem. {% note %} -注意:始终在过渡环境中测试对网络基础结构和实例配置的更改。 有关详细信息,请参阅“[设置暂存实例](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)”。 +**Note**: Always test changes to your network infrastructure and instance configuration in a staging environment. For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)." {% endnote %} -### 错误:“会话已过期”,无法连接到 {% data variables.enterprise.management_console %} +### Error: "Your session has expired" for connections to the {% data variables.enterprise.management_console %} -如果在实例和负载均衡器上启用对 `X-Forwarded-For` 标头的支持,则可能无法访问实例的 {% data variables.enterprise.management_console %}。 有关连接所需的 {% data variables.enterprise.management_console %} 和端口的详细信息,请参阅“[访问管理控制台](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)”和“[网络端口](/admin/configuration/configuring-network-settings/network-ports)”。 +If you enable support for the `X-Forwarded-For` header on your instance and load balancer, you may not be able to access your instance's {% data variables.enterprise.management_console %}. For more information about the {% data variables.enterprise.management_console %} and ports required for connections, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)" and "[Network ports](/admin/configuration/configuring-network-settings/network-ports)." -如果 {% data variables.product.product_location %} 指示通过负载均衡器连接到 {% data variables.enterprise.management_console %} 时会话已过期,请在负载均衡器上尝试以下配置之一。 +If {% data variables.location.product_location %} indicates that your session has expired when you connect to the {% data variables.enterprise.management_console %} through a load balancer, try one of the following configurations on your load balancer. -- 在端口 8080 和 8443 上禁用连接到实例的 `X-Forwarded-For` 标头。 -- 将负载均衡器配置为在第 4 层上运行,并使用 PROXY 协议(而不是 `X-Forwarded-For`)来传递客户端 IP 地址。 有关详细信息,请参阅在“[在 {% data variables.product.product_location %} 上启用 PROXY 协议支持](#enabling-proxy-protocol-support-on-your-github-enterprise-server-instance)”。 +- Disable `X-Forwarded-For` headers for connections to your instance on ports 8080 and 8443. +- Configure your load balancer to operate on Layer 4, and use the PROXY protocol instead of `X-Forwarded-For` for passthrough of client IP addresses. For more information, see "[Enabling PROXY protocol support on {% data variables.location.product_location %}](#enabling-proxy-protocol-support-on-your-github-enterprise-server-instance)." -有关详细信息,请参阅负载均衡器文档。 +For more information, refer to the documentation for your load balancer. -### 对问题的实时更新和检查运行不起作用 +### Live updates to issues and check runs not working -当通过负载均衡器或反向代理访问 {% data variables.product.product_location %} 时,预期的实时更新(如有关通知标记中问题和更改的新注释或检查运行输出)在页面刷新之前可能不会显示。 当反向代理或负载均衡器在第 7 层模式下运行或不支持所需的 [Websocket](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API) 协议时,这是最常见的。 +When {% data variables.location.product_location %} is accessed via a load balancer or reverse proxy, expected live updates, such as new comments on issues and changes in notification badges or check run output, may not display until the page is refreshed. This is most common when the reverse proxy or load balancer is running in a layer 7 mode or does not support the required [websocket](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API) protocol. -若要启用实时更新,可能需要重新配置负载均衡器或代理。 有关详细信息,请参阅负载均衡器文档。 +To enable live updates, you may need to reconfigure the load balancer or proxy. For more information, refer to the documentation for your load balancer. diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md index 4e8ee48a95..50ed3a2fa2 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md +++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md @@ -1,6 +1,6 @@ --- -title: 验证域设置 -intro: '首次启动 {% data variables.product.product_location %} 之前,请确保域设置已正确配置。' +title: Validating your domain settings +intro: 'Ensure that your domain settings are properly configured before booting up {% data variables.location.product_location %} for the first time.' redirect_from: - /enterprise/admin/installation/validating-your-domain-settings - /enterprise/admin/configuration/validating-your-domain-settings @@ -14,13 +14,11 @@ topics: - Infrastructure - Networking shortTitle: Validate domain settings -ms.openlocfilehash: 113f7b3d3f335e73627cebf90a91cbf326c40c99 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145100078' --- -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.hostname-menu-item %} -4. 要测试设备的 DNS 和 SSL 设置,请单击“测试域设置”。 - ![“测试域设置”按钮](/assets/images/enterprise/management-console/test-domain-settings.png) {% data reusables.enterprise_management_console.test-domain-settings-failure %} {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.hostname-menu-item %} +4. To test your appliance's DNS and SSL settings, click **Test domain settings**. + ![Test domain settings button](/assets/images/enterprise/management-console/test-domain-settings.png) +{% data reusables.enterprise_management_console.test-domain-settings-failure %} +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md index 3295e64ecb..46eaace76c 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md @@ -1,5 +1,5 @@ --- -title: 访问管理 shell (SSH) +title: Accessing the administrative shell (SSH) redirect_from: - /enterprise/admin/articles/ssh-access - /enterprise/admin/articles/adding-an-ssh-key-for-shell-access @@ -20,34 +20,30 @@ topics: - Fundamentals - SSH shortTitle: Access the admin shell (SSH) -ms.openlocfilehash: 8d8b9cd71a436c0874355b1bdd53ba2e400660a0 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145100077' --- -## 关于管理 shell 访问 +## About administrative shell access -如果您有权限通过 SSH 访问管理 shell,可运行 {% data variables.product.prodname_ghe_server %} 的命令行实用程序。 SSH 访问也可用于故障排查、运行备份和配置复制。 管理 SSH 访问与 Git SSH 访问分开管理,仅可通过端口 122 访问。 +If you have SSH access to the administrative shell, you can run {% data variables.product.prodname_ghe_server %}'s command line utilities. SSH access is also useful for troubleshooting, running backups, and configuring replication. Administrative SSH access is managed separately from Git SSH access and is accessible only via port 122. -## 允许通过 SSH 访问管理 shell +## Enabling access to the administrative shell via SSH -要启用管理 SSH 访问,您必须向授权密钥的实例列表添加 SSH 公钥。 +To enable administrative SSH access, you must add your SSH public key to your instance's list of authorized keys. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)." {% tip %} -提示:对授权 SSH 密钥进行的变更会立即生效。 +**Tip:** Changes to authorized SSH keys take effect immediately. {% endtip %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} -3. 在“SSH 访问”下,将密钥粘贴到文本框中,然后单击“添加密钥”。 - ![添加 SSH 密钥的文本框和按钮](/assets/images/enterprise/settings/add-authorized-ssh-key-admin-shell.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +3. Under "SSH access", paste your key into the text box, then click **Add key**. + ![Text box and button for adding an SSH key](/assets/images/enterprise/settings/add-authorized-ssh-key-admin-shell.png) +{% data reusables.enterprise_management_console.save-settings %} -## 通过 SSH 连接到管理 shell +## Connecting to the administrative shell over SSH -将 SSH 密钥添加到列表后,以 `admin` 用户的身份在端口 122 上通过 SSH 连接到实例。 +After you've added your SSH key to the list, connect to the instance over SSH as the `admin` user on port 122. ```shell $ ssh -p 122 admin@github.example.com @@ -55,29 +51,29 @@ Last login: Sun Nov 9 07:53:29 2014 from 169.254.1.1 admin@github-example-com:~$ █ ``` -### 排查 SSH 连接问题 +### Troubleshooting SSH connection problems -如果在尝试通过 SSH 连接到 {% data variables.product.product_location %} 时发生 `Permission denied (publickey)` 错误,请确认是否是通过端口 122 进行连接的。 您可能需要明确指定要使用的 SSH 私钥。 +If you encounter the `Permission denied (publickey)` error when you try to connect to {% data variables.location.product_location %} via SSH, confirm that you are connecting over port 122. You may need to explicitly specify which private SSH key to use. -要使用命令行指定 SSH 私钥,请使用 `-i` 参数运行 `ssh`。 +To specify a private SSH key using the command line, run `ssh` with the `-i` argument. ```shell -ssh -i /path/to/ghe_private_key -p 122 admin@hostname +ssh -i /path/to/ghe_private_key -p 122 admin@HOSTNAME ``` -还可以使用 SSH 配置文件 (`~/.ssh/config`) 指定 SSH 私钥。 +You can also specify a private SSH key using the SSH configuration file (`~/.ssh/config`). ```shell -Host hostname +Host HOSTNAME IdentityFile /path/to/ghe_private_key User admin Port 122 ``` -## 使用本地控制台访问管理 shell +## Accessing the administrative shell using the local console -在 SSH 不可用等紧急情况下,您可以在本地访问管理 shell。 以 `admin` 用户身份登录,并使用在 {% data variables.product.prodname_ghe_server %} 初始设置期间确定的密码。 +In an emergency situation, for example if SSH is unavailable, you can access the administrative shell locally. Sign in as the `admin` user and use the password established during initial setup of {% data variables.product.prodname_ghe_server %}. -## 管理 shell 的访问限制 +## Access limitations for the administrative shell -管理 shell 访问仅可用于故障排查和执行记录的操作程序。 修改系统和应用程序文件、运行程序或安装不受支持的软件包可能导致支持合约失效。 如果您对支持合约允许的活动有任何疑问,请联系 {% data variables.contact.contact_ent_support %}。 +Administrative shell access is permitted for troubleshooting and performing documented operations procedures only. Modifying system and application files, running programs, or installing unsupported software packages may void your support contract. Please contact {% data variables.contact.contact_ent_support %} if you have a question about the activities allowed by your support contract. diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md index dbb8eaf46f..83da0eb50e 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md @@ -1,5 +1,5 @@ --- -title: 访问管理控制台 +title: Accessing the management console intro: '{% data reusables.enterprise_site_admin_settings.about-the-management-console %}' redirect_from: - /enterprise/admin/articles/about-the-management-console @@ -18,52 +18,48 @@ topics: - Enterprise - Fundamentals shortTitle: Access the management console -ms.openlocfilehash: 3ddf8deb75c72679fc3e446127fc43ae6f5de4d3 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146332374' --- -## 关于 {% data variables.enterprise.management_console %} +## About the {% data variables.enterprise.management_console %} -使用 {% data variables.enterprise.management_console %} 执行基本管理活动: -- **初始设置**:首次启动 {% data variables.product.product_location %} 时,在浏览器中访问 {% data variables.product.product_location %} 的 IP 地址,简单了解初始设置流程。 -- **配置实例的基本设置**:在“设”页面上配置 DNS、主机名、SSL、用户身份验证、电子邮件、监视服务和日志转发。 -- **预定维护窗口**:使用 {% data variables.enterprise.management_console %} 或管理 shell 执行维护时,使 {% data variables.product.product_location %} 进入脱机状态。 -- **故障排除**:生成支持包或查看高级诊断信息。 -- **许可证管理**:查看或更新 {% data variables.product.prodname_enterprise %} 许可证。 +Use the {% data variables.enterprise.management_console %} for basic administrative activities: +- **Initial setup**: Walk through the initial setup process when first launching {% data variables.location.product_location %} by visiting {% data variables.location.product_location %}'s IP address in your browser. +- **Configuring basic settings for your instance**: Configure DNS, hostname, SSL, user authentication, email, monitoring services, and log forwarding on the Settings page. +- **Scheduling maintenance windows**: Take {% data variables.location.product_location %} offline while performing maintenance using the {% data variables.enterprise.management_console %} or administrative shell. +- **Troubleshooting**: Generate a support bundle or view high level diagnostic information. +- **License management**: View or update your {% data variables.product.prodname_enterprise %} license. -即使在实例处于维护模式、存在重大应用程序故障或者主机名或 SSL 错误配置的情况下,你也始终可以通过 {% data variables.product.product_location %} 的 IP 地址访问 {% data variables.enterprise.management_console %}。 +You can always reach the {% data variables.enterprise.management_console %} using {% data variables.location.product_location %}'s IP address, even when the instance is in maintenance mode, or there is a critical application failure or hostname or SSL misconfiguration. -要访问 {% data variables.enterprise.management_console %},必须使用在 {% data variables.product.product_location %} 初始设置期间确定的管理员密码。 您还必须能够连接到端口 8443 上的虚拟机主机。 如果无法访问 {% data variables.enterprise.management_console %},请检查中间防火墙和安全组配置。 +To access the {% data variables.enterprise.management_console %}, you must use the administrator password established during initial setup of {% data variables.location.product_location %}. You must also be able to connect to the virtual machine host on port 8443. If you're having trouble reaching the {% data variables.enterprise.management_console %}, please check intermediate firewall and security group configurations. -{% data variables.enterprise.management_console %} 密码哈希存储在 `/data/user/common/secrets.conf` 中,该文件会自动从主设备同步到任何高可用性副本。 对主数据库密码的任何更改都将自动复制到高可用性副本。 有关高可用性的详细信息,请参阅“[关于高可用性配置](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration)”。 +The {% data variables.enterprise.management_console %} password hash is stored in `/data/user/common/secrets.conf`, and that file is automatically synced from the primary appliance to any high-availability replicas. Any change to the primary's password will automatically be replicated to high-availability replicas. For more information about high availability, see "[About high availability configuration](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration)." -## 以站点管理员身份访问 {% data variables.enterprise.management_console %} +## Accessing the {% data variables.enterprise.management_console %} as a site administrator -第一次以网站管理员身份访问 {% data variables.enterprise.management_console %} 时,必须上传您的 {% data variables.product.prodname_enterprise %} 许可文件以向应用程序验证。 有关详细信息,请参阅“[管理 {% data variables.product.prodname_enterprise %} 的许可证](/billing/managing-your-license-for-github-enterprise)”。 +The first time that you access the {% data variables.enterprise.management_console %} as a site administrator, you must upload your {% data variables.product.prodname_enterprise %} license file to authenticate into the app. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)." -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.type-management-console-password %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.type-management-console-password %} -## 以未验证用户身份访问 {% data variables.enterprise.management_console %} +## Accessing the {% data variables.enterprise.management_console %} as an unauthenticated user -1. 在浏览器中访问此 URL,将 `hostname` 替换为实际的 {% data variables.product.prodname_ghe_server %} 主机名或 IP 地址: +1. Visit this URL in your browser, replacing `hostname` with your actual {% data variables.product.prodname_ghe_server %} hostname or IP address: ```shell http(s)://HOSTNAME/setup ``` {% data reusables.enterprise_management_console.type-management-console-password %} -## 登录尝试失败后解锁 {% data variables.enterprise.management_console %} +## Unlocking the {% data variables.enterprise.management_console %} after failed login attempts -如果十分钟内登录尝试失败十次,{% data variables.enterprise.management_console %} 将锁定。 您必须等待登录屏幕自动解锁,然后才能再次尝试登录。 一旦前十分钟内登录尝试失败次数不足十次,登录屏幕便会自动解锁。 成功登录后,计数器会复位。 +The {% data variables.enterprise.management_console %} locks after ten failed login attempts are made in the span of ten minutes. You must wait for the login screen to automatically unlock before attempting to log in again. The login screen automatically unlocks as soon as the previous ten minute period contains fewer than ten failed login attempts. The counter resets after a successful login occurs. -要立即解锁 {% data variables.enterprise.management_console %},请通过管理 shell 使用 `ghe-reactivate-admin-login` 命令。 有关详细信息,请参阅“[命令行实用工具](/enterprise/admin/guides/installation/command-line-utilities#ghe-reactivate-admin-login)”和“[访问管理 shell (SSH)](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/)”。 +To immediately unlock the {% data variables.enterprise.management_console %}, use the `ghe-reactivate-admin-login` command via the administrative shell. For more information, see "[Command line utilities](/enterprise/admin/guides/installation/command-line-utilities#ghe-reactivate-admin-login)" and "[Accessing the administrative shell (SSH)](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/)." -## 排查未能连接到 {% data variables.enterprise.management_console %} 的问题 +## Troubleshooting failed connections to the {% data variables.enterprise.management_console %} -如果无法连接到 {% data variables.product.product_location %} 上的 {% data variables.enterprise.management_console %},可查看以下信息来排查问题。 +If you cannot connect to the {% data variables.enterprise.management_console %} on {% data variables.location.product_location %}, you can review the following information to troubleshoot the problem. -### 错误:对于通过负载均衡器的连接,“会话已过期” +### Error: "Your session has expired" for connections through a load balancer -如果通过负载均衡器访问 {% data variables.product.product_location %},并且与 {% data variables.enterprise.management_console %} 的连接失败且显示“会话已过期”消息,则可能需要重新配置负载均衡器。 有关详细信息,请参阅“[将 {% data variables.product.product_name %} 与负载均衡器配合使用](/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer#error-your-session-has-expired-for-connections-to-the-management-console)”。 +If you access {% data variables.location.product_location %} through a load balancer and connections to the {% data variables.enterprise.management_console %} fail with a message that your session has expired, you may need to reconfigure your load balancer. For more information, see "[Using {% data variables.product.product_name %} with a load balancer](/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer#error-your-session-has-expired-for-connections-to-the-management-console)." diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md index d40da03098..f6ad7b034e 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md @@ -1,6 +1,6 @@ --- -title: 命令行实用程序 -intro: '{% data variables.product.prodname_ghe_server %} 包含的各种实用程序可以帮助解决特殊问题或执行特定任务。' +title: Command-line utilities +intro: '{% data variables.product.prodname_ghe_server %} includes a variety of utilities to help resolve particular problems or perform specific tasks.' redirect_from: - /enterprise/admin/articles/viewing-all-services - /enterprise/admin/articles/command-line-utilities @@ -14,20 +14,14 @@ type: reference topics: - Enterprise - SSH -ms.openlocfilehash: fbc378d84c74187fe3e38ea340b0f06e21410669 -ms.sourcegitcommit: da73949b8f8bd71d40247f1f9c49f8f4c362ecd0 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 07/28/2022 -ms.locfileid: '147432054' --- -以 SSH 管理员用户身份登录后,您可以在虚拟机上的任何位置执行这些命令。 有关详细信息,请参阅“[访问管理 shell (SSH)](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/)”。 +You can execute these commands from anywhere on the VM after signing in as an SSH admin user. For more information, see "[Accessing the administrative shell (SSH)](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/)." -## 常规 +## General -### ghe-announce +### ghe-announce -此实用程序会在每个 {% data variables.product.prodname_enterprise %} 页面顶部设置横幅, 您可以使用横幅向用户广播消息。 +This utility sets a banner at the top of every {% data variables.product.prodname_enterprise %} page. You can use it to broadcast a message to your users. ```shell # Sets a message that's visible to everyone @@ -38,7 +32,8 @@ $ ghe-announce -u > Removed the announcement message ``` -{% ifversion ghe-announce-dismiss %} 要允许每个用户自己关闭通知,请使用 `-d` 标志。 +{% ifversion ghe-announce-dismiss %} +To allow each user to dismiss the announcement for themselves, use the `-d` flag. ```shell # Sets a user-dismissible message that's visible to everyone $ ghe-announce -d -s MESSAGE @@ -49,61 +44,62 @@ $ ghe-announce -u ``` {% endif %} -{% ifversion ghes %} 你也可以使用企业设置在 {% data variables.product.product_name %} 上设置一个公告横幅。 有关详细信息,请参阅“[自定义实例上的用户消息](/enterprise/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)”。 +{% ifversion ghes %} +You can also set an announcement banner using the enterprise settings on {% data variables.product.product_name %}. For more information, see "[Customizing user messages on your instance](/enterprise/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)." {% endif %} {% ifversion ghes %} -### ghe-aqueduct +### ghe-aqueduct -此实用程序会显示关于后台作业(活动作业和队列中的作业)的信息, 它提供的作业计数与每个页面顶部管理员统计信息栏中的计数相同。 +This utility displays information on background jobs, both active and in the queue. It provides the same job count numbers as the admin stats bar at the top of every page. -此实用程序可以帮助确定 Aqueduct 服务器在处理后台作业时是否会出现问题。 下列任一场景均可能指示 Aqueduct 存在问题: +This utility can help identify whether the Aqueduct server is having problems processing background jobs. Any of the following scenarios might be indicative of a problem with Aqueduct: -* 后台作业数增加,而活动作业数保持不变。 -* 事件源未更新。 -* Web 挂钩未触发。 -* Web 界面在 Git 推送后未更新。 +* The number of background jobs is increasing, while the active jobs remain the same. +* The event feeds are not updating. +* Webhooks are not being triggered. +* The web interface is not updating after a Git push. -如果怀疑 Aqueduct 出现故障,请联系 {% data variables.contact.contact_ent_support %} 获取帮助。 +If you suspect Aqueduct is failing, contact {% data variables.contact.contact_ent_support %} for help. -使用此命令,您还可以暂停或恢复队列中的作业。 +With this command, you can also pause or resume jobs in the queue. ```shell $ ghe-aqueduct status # lists queues and the number of currently queued jobs for all queues -$ ghe-aqueduct queue_depth --queue QUEUE +$ ghe-aqueduct queue_depth --queue QUEUE # lists the number of currently queued jobs for the specified queue -$ ghe-aqueduct pause --queue QUEUE +$ ghe-aqueduct pause --queue QUEUE # pauses the specified queue -$ ghe-aqueduct resume --queue QUEUE +$ ghe-aqueduct resume --queue QUEUE # resumes the specified queue ``` {% endif %} -### ghe-check-disk-usage +### ghe-check-disk-usage -此实用程序会检查磁盘中的大文件或已删除但文件句柄仍保持打开的文件。 如果尝试释放根分区中的空间,应运行此实用程序。 +This utility checks the disk for large files or files that have been deleted but still have open file handles. This should be run when you're trying to free up space on the root partition. ```shell ghe-check-disk-usage ``` -### ghe-cleanup-caches +### ghe-cleanup-caches -此实用程序会清理各种有可能占用根卷上的额外磁盘空间的缓存。 如果您发现一段时间内根卷磁盘空间的使用量显著升高,最好运行此应用程序,查看是否可以帮助降低整体使用量 。 +This utility cleans up a variety of caches that might potentially take up extra disk space on the root volume. If you find your root volume disk space usage increasing notably over time it would be a good idea to run this utility to see if it helps reduce overall usage. ```shell ghe-cleanup-caches ``` -### ghe-cleanup-settings +### ghe-cleanup-settings -此实用程序会擦除所有现有的 {% data variables.enterprise.management_console %} 设置。 +This utility wipes all existing {% data variables.enterprise.management_console %} settings. {% tip %} -提示:{% data reusables.enterprise_enterprise_support.support_will_ask_you_to_run_command %} +**Tip**: {% data reusables.enterprise_enterprise_support.support_will_ask_you_to_run_command %} {% endtip %} @@ -111,62 +107,63 @@ ghe-cleanup-caches ghe-cleanup-settings ``` -### ghe-config +### ghe-config -此实用程序可用于检索和修改 {% data variables.product.product_location %} 的配置设置。 +With this utility, you can both retrieve and modify the configuration settings of {% data variables.location.product_location %}. ```shell -$ ghe-config core.github-hostname +$ ghe-config core.github-hostname # Gets the configuration value of `core.github-hostname` -$ ghe-config core.github-hostname 'example.com' -# Sets the configuration value of `core.github-hostname` to `example.com` +$ ghe-config core.github-hostname URL +# Sets the configuration value of `core.github-hostname` to the specified URL $ ghe-config -l # Lists all the configuration values ``` -可让你在 `cluster.conf` 中找到节点的通用唯一标识符 (UUID)。 +Allows you to find the universally unique identifier (UUID) of your node in `cluster.conf`. ```shell - $ ghe-config HOSTNAME.uuid + $ ghe-config HOSTNAME.uuid ``` -{% ifversion ghes %} 可让你将用户列表从 REST API 速率限制中排除。 120,000 个请求的硬性限制仍将适用于这些用户。 有关详细信息,请参阅“[REST API 中的资源](/rest/overview/resources-in-the-rest-api#rate-limiting)”。 +{% ifversion ghes %} +Allows you to exempt a list of users from REST API rate limits. A hard limit of 120,000 requests will still apply to these users. For more information, see "[Resources in the REST API](/rest/overview/resources-in-the-rest-api#rate-limiting)." ``` shell -$ ghe-config app.github.rate-limiting-exempt-users "hubot github-actions" +$ ghe-config app.github.rate-limiting-exempt-users "HUBOT GITHUB-ACTIONS" # Exempts the users hubot and github-actions from rate limits ``` {% endif %} -### ghe-config-apply +### ghe-config-apply -此实用程序会应用 {% data variables.enterprise.management_console %} 设置,重新加载系统服务,准备存储设备,重新加载应用程序服务并运行任何待处理的数据库迁移。 它等效于单击 {% data variables.enterprise.management_console %} web UI 中的“保存设置”,或向 [`/setup/api/configure` 终结点](/enterprise/user/rest/reference/enterprise-admin#management-console)发送 POST 请求。 +This utility applies {% data variables.enterprise.management_console %} settings, reloads system services, prepares a storage device, reloads application services, and runs any pending database migrations. It is equivalent to clicking **Save settings** in the {% data variables.enterprise.management_console %}'s web UI or to sending a POST request to [the `/setup/api/configure` endpoint](/enterprise/user/rest/reference/enterprise-admin#management-console). -您有可能永远不需要手动运行此实用程序,但如果希望通过 SSH 自动完成设置保存过程,也可以使用此实用程序。 +You will probably never need to run this manually, but it's available if you want to automate the process of saving your settings via SSH. ```shell ghe-config-apply ``` -### ghe-console +### ghe-console -此实用程序会在您的 {% data variables.product.prodname_enterprise %} 设备上打开 GitHub Rails 控制台。 {% data reusables.command_line.use_with_support_only %} +This utility opens the GitHub Rails console on your {% data variables.product.prodname_enterprise %} appliance. {% data reusables.command_line.use_with_support_only %} ```shell ghe-console ``` -### ghe-dbconsole +### ghe-dbconsole -此实用程序会在您的 {% data variables.product.prodname_enterprise %} 设备上打开 MySQL 数据库会话。 {% data reusables.command_line.use_with_support_only %} +This utility opens a MySQL database session on your {% data variables.product.prodname_enterprise %} appliance. {% data reusables.command_line.use_with_support_only %} ```shell ghe-dbconsole ``` -### ghe-es-index-status -此实用程序会以 CSV 格式返回 ElasticSearch 索引的摘要。 +### ghe-es-index-status +This utility returns a summary of Elasticsearch indexes in CSV format. -将包含标头行的索引摘要打印到 `STDOUT`: +Print an index summary with a header row to `STDOUT`: ```shell $ ghe-es-index-status -do > warning: parser/current is loading parser/ruby23, which recognizes @@ -185,7 +182,7 @@ $ ghe-es-index-status -do > wikis-4,true,true,true,true,100.0,2613dec44bd14e14577803ac1f9e4b7e07a7c234 ``` -将索引摘要和管道结果打印到 `column`,以供读取: +Print an index summary and pipe results to `column` for readability: ```shell $ ghe-es-index-status -do | column -ts, @@ -205,115 +202,115 @@ $ ghe-es-index-status -do | column -ts, > wikis-4 true true true true 100.0 2613dec44bd14e14577803ac1f9e4b7e07a7c234 ``` -### ghe-legacy-github-services-report +### ghe-legacy-github-services-report -此实用程序会列出您的设备中使用 {% data variables.product.prodname_dotcom %} Services 的仓库,作为一种集成方法,此服务将于 2018 年 10 月 1 日停用。 您的设备上的用户可能已设置 {% data variables.product.prodname_dotcom %} Services,为发往某些仓库的推送创建通知。 有关详细信息,请参阅 {% data variables.product.prodname_blog %} 上的“[宣布弃用 {% data variables.product.prodname_dotcom %} 服务](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)”或“[替换 {% data variables.product.prodname_dotcom %} 服务](/developers/overview/replacing-github-services)”。 如需获取关于此命令的详细信息或附加选项,请使用 `-h` 标志。 +This utility lists repositories on your appliance that use {% data variables.product.prodname_dotcom %} Services, an integration method that will be discontinued on October 1, 2018. Users on your appliance may have set up {% data variables.product.prodname_dotcom %} Services to create notifications for pushes to certain repositories. For more information, see "[Announcing the deprecation of {% data variables.product.prodname_dotcom %} Services](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)" on {% data variables.product.prodname_blog %} or "[Replacing {% data variables.product.prodname_dotcom %} Services](/developers/overview/replacing-github-services)." For more information about this command or for additional options, use the `-h` flag. ```shell ghe-legacy-github-services-report ``` -### ghe-logs-tail +### ghe-logs-tail -此实用程序允许跟踪记录安装中的所有相关日志文件。 您可以传入选项,将日志限制为特定集合。 使用 -h 标志表示附加选项。 +This utility lets you tail log all relevant log files from your installation. You can pass options in to limit the logs to specific sets. Use the -h flag for additional options. ```shell ghe-logs-tail ``` -### ghe-maintenance +### ghe-maintenance -此实用程序允许您控制安装维护模式的状态, 其设计为主要由 {% data variables.enterprise.management_console %} 在后台使用,但也可以直接使用。 有关详细信息,请参阅“[启用和安排维护模式](/admin/guides/installation/enabling-and-scheduling-maintenance-mode)”。 +This utility allows you to control the state of the installation's maintenance mode. It's designed to be used primarily by the {% data variables.enterprise.management_console %} behind-the-scenes, but it can be used directly. For more information, see "[Enabling and scheduling maintenance mode](/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." ```shell ghe-maintenance -h ``` -### ghe-motd +### ghe-motd -此实用程序重新显示管理员通过管理 shell 访问实例时看到的当天消息 (MOTD)。 输出包含实例状态的概述。 +This utility re-displays the message of the day (MOTD) that administrators see when accessing the instance via the administrative shell. The output contains an overview of the instance's state. ```shell ghe-motd ``` -### ghe-nwo +### ghe-nwo -此实用程序会根据仓库 ID 返回仓库名称和所有者。 +This utility returns a repository's name and owner based on the repository ID. ```shell -ghe-nwo REPOSITORY_ID +ghe-nwo REPOSITORY_ID ``` -### ghe-org-admin-promote +### ghe-org-admin-promote -使用此命令可为设备上具有站点管理员权限的用户提供组织所有者权限,或者为组织中的任何用户提供组织所有者权限。 您必须指定用户和/或组织。 `ghe-org-admin-promote` 命令始终会在运行前要求确认,除非使用 `-y` 标志绕过确认过程。 +Use this command to give organization owner privileges to users with site admin privileges on the appliance, or to give organization owner privileges to any single user in a single organization. You must specify a user and/or an organization. The `ghe-org-admin-promote` command will always ask for confirmation before running unless you use the `-y` flag to bypass the confirmation. -您可将以下选项与实用程序配合使用: +You can use these options with the utility: -- `-u` 标志指定用户名。 使用此标志可为特定用户提供组织所有者权限。 省略 `-u` 标志会将所有站点管理员提升为指定组织的所有者。 -- `-o` 标志指定组织。 使用此标志可提供特定组织中的所有者权限。 省略 `-o` 标志会将所有组织中的所有者权限授予指定的站点管理员。 -- `-a` 标志会将所有组织中的所有者权限授予所有站点管理员。 -- `-y` 标志可绕过手动确认。 +- The `-u` flag specifies a username. Use this flag to give organization owner privileges to a specific user. Omit the `-u` flag to promote all site admins to the specified organization. +- The `-o` flag specifies an organization. Use this flag to give owner privileges in a specific organization. Omit the `-o` flag to give owner permissions in all organizations to the specified site admin. +- The `-a` flag gives owner privileges in all organizations to all site admins. +- The `-y` flag bypasses the manual confirmation. -此实用程序无法将非站点管理员升级为所有组织的所有者。 可以使用 [ghe-user-promote](#ghe-user-promote) 将普通用户帐户提升为站点管理员。 +This utility cannot promote a non-site admin to be an owner of all organizations. You can promote an ordinary user account to a site admin with [ghe-user-promote](#ghe-user-promote). -将特定组织中的组织所有者权限授予特定的站点管理员 +Give organization owner privileges in a specific organization to a specific site admin ```shell -ghe-org-admin-promote -u USERNAME -o ORGANIZATION +ghe-org-admin-promote -u USERNAME -o ORGANIZATION ``` -将所有组织中的组织所有者权限授予特定的站点管理员 +Give organization owner privileges in all organizations to a specific site admin ```shell -ghe-org-admin-promote -u USERNAME +ghe-org-admin-promote -u USERNAME ``` -将特定组织中的组织所有者权限授予所有站点管理员 +Give organization owner privileges in a specific organization to all site admins ```shell -ghe-org-admin-promote -o ORGANIZATION +ghe-org-admin-promote -o ORGANIZATION ``` -将所有组织中的组织所有者权限授予所有站点管理员 +Give organization owner privileges in all organizations to all site admins ```shell ghe-org-admin-promote -a ``` -### ghe-reactivate-admin-login +### ghe-reactivate-admin-login -在 10 分钟内登录尝试失败 10 次后,使用此命令可立即解锁 {% data variables.enterprise.management_console %}。 +Use this command to immediately unlock the {% data variables.enterprise.management_console %} after 10 failed login attempts in the span of 10 minutes. ```shell $ ghe-reactivate-admin-login ``` -### ghe-saml-mapping-csv +### ghe-saml-mapping-csv -此实用程序可帮助映射 SAML 记录。 +This utility can help map SAML records. -为 {% data variables.product.product_name %} 用户创建包含所有 SAML 映射的 CSV 文件: +To create a CSV file containing all the SAML mapping for your {% data variables.product.product_name %} users: ```shell $ ghe-saml-mapping-csv -d ``` -要使用新值执行更新 SAML 映射的排演: +To perform a dry run of updating SAML mappings with new values: ```shell $ ghe-saml-mapping-csv -u -n -f /path/to/file ``` -要使用新值更新 SAML 映射: +To update SAML mappings with new values: ```shell $ ghe-saml-mapping-csv -u -f /path/to/file ``` -### ghe-service-list +### ghe-service-list -此实用程序会列出您的设备上已启动或停止(正在运行或等待)的服务。 +This utility lists all of the services that have been started or stopped (are running or waiting) on your appliance. ```shell $ ghe-service-list @@ -338,49 +335,49 @@ stop/waiting - ghe-replica-mode ``` -### ghe-set-password +### ghe-set-password -使用 `ghe-set-password`,可以设置新密码,以便在 [{% data variables.enterprise.management_console %}](/enterprise/admin/guides/installation/accessing-the-management-console) 中进行身份验证。 +With `ghe-set-password`, you can set a new password to authenticate into the [{% data variables.enterprise.management_console %}](/enterprise/admin/guides/installation/accessing-the-management-console). ```shell ghe-set-password ``` -### ghe-setup-network +### ghe-setup-network -使用此实用工具可以配置主网络接口。 +This utility allows you to configure the primary network interface. -若要进入可视模式(该模式将引导你完成网络设置的配置),请执行以下操作: +To enter visual mode, which will guide you through configuration of network settings: ```shell $ ghe-setup-network -v ``` -使用 -h 标志表示附加选项。 +Use the -h flag for additional options. -### ghe-ssh-check-host-keys +### ghe-ssh-check-host-keys -此实用程序会对照已知泄露的 SSH 主机密钥检查现有的 SSH 主机密钥。 +This utility checks the existing SSH host keys against the list of known leaked SSH host keys. ```shell $ ghe-ssh-check-host-keys ``` -如果发现主机密钥泄露,实用程序会以状态 `1` 退出并显示以下消息: +If a leaked host key is found the utility exits with status `1` and a message: ```shell > One or more of your SSH host keys were found in the blacklist. > Please reset your host keys using ghe-ssh-roll-host-keys. ``` -如果未发现主机密钥泄露,实用程序会以状态 `0` 退出并显示以下消息: +If a leaked host key was not found, the utility exits with status `0` and a message: ```shell > The SSH host keys were not found in the SSH host key blacklist. > No additional steps are needed/recommended at this time. ``` -### ghe-ssh-roll-host-keys +### ghe-ssh-roll-host-keys -此实用程序会滚动 SSH 主机密钥并将其替换为新生成的密钥。 +This utility rolls the SSH host keys and replaces them with newly generated keys. ```shell $ sudo ghe-ssh-roll-host-keys @@ -392,9 +389,9 @@ existing keys in /etc/ssh/ssh_host_* and generate new ones. [y/N] > SSH host keys have successfully been rolled. ``` -### ghe-ssh-weak-fingerprints +### ghe-ssh-weak-fingerprints -此实用程序会返回存储在 {% data variables.product.prodname_enterprise %} 设备上的已知弱 SSH 密钥的报告。 您可以选择批量撤销用户密钥。 此实用程序将报告弱系统密钥,必须在 [{% data variables.enterprise.management_console %}](/enterprise/admin/guides/installation/accessing-the-management-console) 中手动撤销这些密钥。 +This utility returns a report of known weak SSH keys stored on the {% data variables.product.prodname_enterprise %} appliance. You can optionally revoke user keys as a bulk action. The utility will report weak system keys, which you must manually revoke in the [{% data variables.enterprise.management_console %}](/enterprise/admin/guides/installation/accessing-the-management-console). ```shell # Print a report of weak user and system SSH keys @@ -404,23 +401,23 @@ $ ghe-ssh-weak-fingerprints $ ghe-ssh-weak-fingerprints --revoke ``` -### ghe-ssl-acme +### ghe-ssl-acme -此实用程序允许您在 {% data variables.product.prodname_enterprise %} 设备上安装 Let's Encrypt 证书。 有关详细信息,请参阅“[配置 TLS](/enterprise/admin/guides/installation/configuring-tls)”。 +This utility allows you to install a Let's Encrypt certificate on your {% data variables.product.prodname_enterprise %} appliance. For more information, see "[Configuring TLS](/enterprise/admin/guides/installation/configuring-tls)." -可以使用 `-x` 标志来删除 ACME 配置。 +You can use the `-x` flag to remove the ACME configuration. ```shell ghe-ssl-acme -e ``` -### ghe-ssl-ca-certificate-install +### ghe-ssl-ca-certificate-install -此实用程序允许您在 {% data variables.product.prodname_enterprise %} 服务器上安装自定义根 CA 证书。 证书必须采用 PEM 格式。 此外,如果证书提供者在一个文件中包含多个 CA 证书,则必须将其拆分到多个单独文件中,随后再将这些文件逐个传递到 `ghe-ssl-ca-certificate-install`。 +This utility allows you to install a custom root CA certificate on your {% data variables.product.prodname_enterprise %} server. The certificate must be in PEM format. Furthermore, if your certificate provider includes multiple CA certificates in a single file, you must separate them into individual files that you then pass to `ghe-ssl-ca-certificate-install` one at a time. -运行此实用程序可添加证书链进行 S/MIME 提交签名验证。 有关详细信息,请参阅“[关于提交签名验证](/enterprise/user/articles/about-commit-signature-verification/)”。 +Run this utility to add a certificate chain for S/MIME commit signature verification. For more information, see "[About commit signature verification](/enterprise/user/articles/about-commit-signature-verification/)." -如果 {% data variables.product.product_location %} 无法连接到另一台服务器的原因是后者使用自签名 SSL 证书或没有为其提供必要 CA 包的 SSL 证书,请运行此实用程序。 确认这一点的一种方法是从 {% data variables.product.product_location %} 运行 `openssl s_client -connect host:port -verify 0 -CApath /etc/ssl/certs`。 如果可以验证远程服务器的 SSL 证书,`SSL-Session` 的返回代码应为 0,如下所示。 +Run this utility when {% data variables.location.product_location %} is unable to connect to another server because the latter is using a self-signed SSL certificate or an SSL certificate for which it doesn't provide the necessary CA bundle. One way to confirm this is to run `openssl s_client -connect host:port -verify 0 -CApath /etc/ssl/certs` from {% data variables.location.product_location %}. If the remote server's SSL certificate can be verified, your `SSL-Session` should have a return code of 0, as shown below. ``` SSL-Session: @@ -435,7 +432,7 @@ SSL-Session: Verify return code: 0 (ok) ``` -另一方面,如果无法验证远程服务器的 SSL 证书,`SSL-Session` 的返回代码应为非零值: +If, on the other hand, the remote server's SSL certificate can *not* be verified, your `SSL-Session` should have a nonzero return code: ``` SSL-Session: @@ -450,191 +447,193 @@ SSL-Session: Verify return code: 27 (certificate not trusted) ``` -您可以将以下附加选项与实用程序结合使用: -- `-r` 标志允许你卸载 CA 证书。 -- `-h` 标志可显示更多用法信息。 +You can use these additional options with the utility: +- The `-r` flag allows you to uninstall a CA certificate. +- The `-h` flag displays more usage information. ```shell -ghe-ssl-ca-certificate-install -c /path/to/certificate +ghe-ssl-ca-certificate-install -c CERTIFICATE_PATH ``` -### ghe-ssl-certificate-setup +### ghe-ssl-certificate-setup -此实用工具允许您更新 {% data variables.product.product_location %} 的 SSL 证书。 +This utility allows you to update an SSL certificate for {% data variables.location.product_location %}. -如需获取关于此命令的详细信息或附加选项,请使用 `-h` 标志。 +For more information about this command or for additional options, use the `-h` flag. ```shell ghe-ssl-certificate-setup ``` -### ghe-ssl-generate-csr +### ghe-ssl-generate-csr -此实用程序允许您生成可与商业或私有证书颁发机构共享的私钥和证书签名请求 (CSR),以获取可与您的实例配合使用的有效证书。 有关详细信息,请参阅“[配置 TLS](/enterprise/admin/guides/installation/configuring-tls)”。 +This utility allows you to generate a private key and certificate signing request (CSR), which you can share with a commercial or private certificate authority to get a valid certificate to use with your instance. For more information, see "[Configuring TLS](/enterprise/admin/guides/installation/configuring-tls)." -如需获取关于此命令的详细信息或附加选项,请使用 `-h` 标志。 +For more information about this command or for additional options, use the `-h` flag. ```shell ghe-ssl-generate-csr ``` -### ghe-storage-extend +### ghe-storage-extend -某些平台需要使用此脚本扩展用户量。 有关详细信息,请参阅“[增加存储容量](/enterprise/admin/guides/installation/increasing-storage-capacity/)”。 +Some platforms require this script to expand the user volume. For more information, see "[Increasing Storage Capacity](/enterprise/admin/guides/installation/increasing-storage-capacity/)". ```shell $ ghe-storage-extend ``` -### ghe-version +### ghe-version -此实用工具会打印 {% data variables.product.product_location %} 的版本、平台和内部版本号。 +This utility prints the version, platform, and build of {% data variables.location.product_location %}. ```shell $ ghe-version ``` -### ghe-webhook-logs +### ghe-webhook-logs -此实用程序会返回 web 挂钩交付日志,供管理员审查和确定任何问题。 +This utility returns webhook delivery logs for administrators to review and identify any issues. ```shell ghe-webhook-logs ``` -显示过去一天所有失败的挂钩交付:{% ifversion ghes %} +To show all failed hook deliveries in the past day: +{% ifversion ghes %} ```shell -ghe-webhook-logs -f -a YYYY-MM-DD +ghe-webhook-logs -f -a YYYY-MM-DD ``` -日期格式应为 `YYYY-MM-DD`、`YYYY-MM-DD HH:MM:SS` 或 `YYYY-MM-DD HH:MM:SS (+/-) HH:M`。 +The date format should be `YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS`, or `YYYY-MM-DD HH:MM:SS (+/-) HH:M`. {% else %} ```shell -ghe-webhook-logs -f -a YYYYMMDD +ghe-webhook-logs -f -a YYYYMMDD ``` {% endif %} -显示交付的完整挂钩有效负载、结果以及任何异常:{% ifversion ghes %} +To show the full hook payload, result, and any exceptions for the delivery: +{% ifversion ghes %} ```shell -ghe-webhook-logs -g delivery-guid +ghe-webhook-logs -g DELIVERY_GUID ``` {% else %} ```shell -ghe-webhook-logs -g delivery-guid -v +ghe-webhook-logs -g DELIVERY_GUID -v ``` {% endif %} -## 群集 +## Clustering -### ghe-cluster-status +### ghe-cluster-status -在 {% data variables.product.prodname_ghe_server %} 的集群部署中检查节点和服务的运行状况。 +Check the health of your nodes and services in a cluster deployment of {% data variables.product.prodname_ghe_server %}. ```shell $ ghe-cluster-status ``` -### ghe-cluster-support-bundle +### ghe-cluster-support-bundle -此实用程序创建的支持包 tarball 包含采用 Geo-replication 或集群配置的各个节点中的重要日志。 +This utility creates a support bundle tarball containing important logs from each of the nodes in either a Geo-replication or Clustering configuration. -默认情况下,该命令在 /tmp 中创建 tarball,但也可以使用它将 tarball `cat` 为 `STDOUT`,以通过 SSH 轻松进行流式传输。 在 Web UI 未响应或从 /setup/support 下载支持包失败的情况下,可以使用此方法。 如果要生成包含旧日志的 extended 捆绑,则必须使用此命令。 您还可以使用此命令将集群支持包直接上传到 {% data variables.product.prodname_enterprise %} Support。 +By default, the command creates the tarball in */tmp*, but you can also have it `cat` the tarball to `STDOUT` for easy streaming over SSH. This is helpful in the case where the web UI is unresponsive or downloading a support bundle from */setup/support* doesn't work. You must use this command if you want to generate an *extended* bundle, containing older logs. You can also use this command to upload the cluster support bundle directly to {% data variables.product.prodname_enterprise %} support. -要创建标准捆绑包: +To create a standard bundle: ```shell -$ ssh -p 122 admin@hostname -- 'ghe-cluster-support-bundle -o' > cluster-support-bundle.tgz +$ ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -o' > cluster-support-bundle.tgz ``` -要创建扩展捆绑包: +To create an extended bundle: ```shell -$ ssh -p 122 admin@hostname -- 'ghe-cluster-support-bundle -x -o' > cluster-support-bundle.tgz +$ ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -x -o' > cluster-support-bundle.tgz ``` -要将捆绑包发送至 {% data variables.contact.github_support %}: +To send a bundle to {% data variables.contact.github_support %}: ```shell -$ ssh -p 122 admin@hostname -- 'ghe-cluster-support-bundle -u' +$ ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -u' ``` -要将捆绑包发送至 {% data variables.contact.github_support %} 并关联捆绑包与事件单: +To send a bundle to {% data variables.contact.github_support %} and associate the bundle with a ticket: ```shell -$ ssh -p 122 admin@hostname -- 'ghe-cluster-support-bundle -t ticket-id' +$ ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -t TICKET_ID' ``` {% ifversion ghes %} -### ghe-cluster-failover +### ghe-cluster-failover -从主动群集节点故障转移至被动群集节点。 有关详细信息,请参阅“[启动到副本群集的故障转移](/enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster)”。 +Fail over from active cluster nodes to passive cluster nodes. For more information, see "[Initiating a failover to your replica cluster](/enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster)." ```shell ghe-cluster-failover ``` {% endif %} -### ghe-dpages +### ghe-dpages -此实用程序可用于管理分配的 {% data variables.product.prodname_pages %} 服务器。 +This utility allows you to manage the distributed {% data variables.product.prodname_pages %} server. ```shell ghe-dpages ``` -要显示仓库位置和健康状态摘要: +To show a summary of repository location and health: ```shell ghe-dpages status ``` -要在撤出集群节点之前撤出 {% data variables.product.prodname_pages %} 存储服务: +To evacuate a {% data variables.product.prodname_pages %} storage service before evacuating a cluster node: ```shell -ghe-dpages evacuate pages-server-UUID +ghe-dpages evacuate pages-server-UUID ``` -### ghe-spokes +### ghe-spokes -此实用程序允许您管理分布式 git 服务器上各仓库的三个副本。 +This utility allows you to manage the three copies of each repository on the distributed git servers. ```shell ghe-spokes ``` -要显示仓库位置和健康状态摘要: +To show a summary of repository location and health: ```shell ghe-spokes status ``` -要显示存储仓库的服务器: +To show the servers in which the repository is stored: ```shell ghe-spokes route ``` -要撤出集群节点上的存储服务: +To evacuate storage services on a cluster node: ```shell -ghe-spokes server evacuate git-server-UUID +ghe-spokes server evacuate git-server-UUID ``` -### ghe-storage +### ghe-storage -此实用程序允许您在撤出集群节点之前撤出所有存储服务。 +This utility allows you to evacuate all storage services before evacuating a cluster node. ```shell -ghe-storage evacuate storage-server-UUID +ghe-storage evacuate storage-server-UUID ``` -## Git +## Git -### ghe-btop +### ghe-btop -当前 Git 操作的类 `top` 接口。 +A `top`-like interface for current Git operations. ```shell ghe-btop [ | --help | --usage ] ``` -#### ghe-governor +#### ghe-governor -此工具有助于分析 Git 流量。 它查询位于 `/data/user/gitmon` 下的 Governor 数据文件。 {% data variables.product.company_short %} 为每个文件保存一小时的数据,保留两周。 有关详细信息,请参阅 {% data variables.product.prodname_github_community %} 中的[使用 Governor 分析 Git 流量](https://github.community/t/analyzing-git-traffic-using-governor/13516)。 +This utility helps to analyze Git traffic. It queries _Governor_ data files, located under `/data/user/gitmon`. {% data variables.product.company_short %} holds one hour of data per file, retained for two weeks. For more information, see [Analyzing Git traffic using Governor](https://github.community/t/analyzing-git-traffic-using-governor/13516) in {% data variables.product.prodname_github_community %}. ```bash ghe-governor [options] @@ -657,106 +656,106 @@ Valid subcommands are: Try ghe-governor --help for more information on the arguments each subcommand takes. ``` -### ghe-repo +### ghe-repo -此实用程序允许你切换到存储库的目录并以 `git` 用户身份打开交互式 shell。 可以通过 `git-*` 或 `git-nw-*` 等命令对存储库执行手动检查或维护。 +This utility allows you to change to a repository's directory and open an interactive shell as the `git` user. You can perform manual inspection or maintenance of a repository via commands like `git-*` or `git-nw-*`. ```shell -ghe-repo username/reponame +ghe-repo USERNAME/REPONAME ``` -### ghe-repo-gc +### ghe-repo-gc -此实用程序会手动重新打包仓库网络,以优化包存储。 如果仓库较大,运行此命令有助于减小其整体大小。 {% data variables.product.prodname_enterprise %} 会在与仓库网络交互的过程中自动运行此命令。 +This utility manually repackages a repository network to optimize pack storage. If you have a large repository, running this command may help reduce its overall size. {% data variables.product.prodname_enterprise %} automatically runs this command throughout your interaction with a repository network. -可以添加可选的 `--prune` 参数来删除不是从分支、标记或其他任何 ref 引用的不可达 Git 对象。此方法特别适用于立即删除[之前泄露的敏感信息](/enterprise/user/articles/remove-sensitive-data/)。 +You can add the optional `--prune` argument to remove unreachable Git objects that aren't referenced from a branch, tag, or any other ref. This is particularly useful for immediately removing [previously expunged sensitive information](/enterprise/user/articles/remove-sensitive-data/). {% warning %} -警告:在使用 `--prune` 参数删除无法访问的 Git 对象之前,请将 {% data variables.product.product_location %} 置于维护模式,或确保存储库处于脱机状态。 有关详细信息,请参阅“[启用和安排维护模式](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)”。 +**Warning**: Before using the `--prune` argument to remove unreachable Git objects, put {% data variables.location.product_location %} into maintenance mode, or ensure all repositories within the same repository network are locked. For more information, see "[Enabling and scheduling maintenance mode](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)." {% endwarning %} ```shell -ghe-repo-gc username/reponame +ghe-repo-gc USERNAME/REPONAME ``` -## {% data variables.product.prodname_actions %} +## {% data variables.product.prodname_actions %} -### ghe-actions-check +### ghe-actions-check -此实用工具检查 {% data variables.product.prodname_actions %} 的所有服务是否正常运行。 有关详细信息,请参阅“[{% data variables.product.product_name %} 的 {% data variables.product.prodname_actions %} 入门](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server)”和“[排查企业的 {% data variables.product.prodname_actions %}](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise)”。 +This utility checks that all services for {% data variables.product.prodname_actions %} are healthy. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server)" and "[Troubleshooting {% data variables.product.prodname_actions %} for your enterprise](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise)." ```shell ghe-actions-check ``` -### ghe-actions-precheck +### ghe-actions-precheck -此实用工具测试 {% data variables.product.product_location %} 上 {% data variables.product.prodname_actions %} 的 blob 存储配置。 在为实例启用 {% data variables.product.prodname_actions %} 之前,您可以使用该实用工具验证您的存储配置。 +This utility tests the blob storage configuration for {% data variables.product.prodname_actions %} on {% data variables.location.product_location %}. You can use the utility to verify your storage configuration before you enable {% data variables.product.prodname_actions %} for your instance. -有关 {% data variables.product.prodname_actions %} 的配置的详细信息,请参阅“[{% data variables.product.product_name %} 的 {% data variables.product.prodname_actions %} 入门](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server)”。 +For more information about the configuration of {% data variables.product.prodname_actions %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server)." ```shell -ghe-actions-precheck -p [provider] -cs ["connectionstring"] +ghe-actions-precheck -p [PROVIDER] -cs ["CONNECTION-STRING"] ``` -如果存储系统配置正确,您将看到以下输出。 +If your storage system is configured correctly, you'll see the following output. ``` All Storage tests passed ``` -## 导入和导出 +## Import and export -### ghe-migrator +### ghe-migrator -`ghe-migrator` 属于高保真工具,可帮助用户从一个 GitHub 实例迁移到另一个实例。 您可以整合实例或将组织、用户、团队和仓库从 GitHub.com 移至 {% data variables.product.prodname_enterprise %}。 +`ghe-migrator` is a hi-fidelity tool to help you migrate from one GitHub instance to another. You can consolidate your instances or move your organization, users, teams, and repositories from GitHub.com to {% data variables.product.prodname_enterprise %}. -有关详细信息,请参阅有关[将数据迁移到企业和从企业迁移数据](/enterprise/admin/user-management/migrating-data-to-and-from-your-enterprise/)的指南。 +For more information, please see our guides on [migrating data to and from your enterprise](/enterprise/admin/user-management/migrating-data-to-and-from-your-enterprise/). -### git-import-detect +### git-import-detect -给定一个 URL,检测哪种类型的源控制管理系统位于另一端。 在手动导入过程中,此信息很可能是已知的,但在自动执行的脚本中非常有用。 +Given a URL, detect which type of source control management system is at the other end. During a manual import this is likely already known, but this can be very useful in automated scripts. ```shell git-import-detect ``` -### git-import-hg-raw +### git-import-hg-raw -此实用程序可将 Mercurial 仓库导入至此 Git 仓库。 有关详细信息,请参阅“[从第三方版本控制系统导入数据](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)”。 +This utility imports a Mercurial repository to this Git repository. For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)." ```shell git-import-hg-raw ``` -### git-import-svn-raw +### git-import-svn-raw -此实用程序可将 Subversion 历史记录和文件数据导入至 Git 分支。 这属于直接复制树,会忽略任何主干或分支差异。 有关详细信息,请参阅“[从第三方版本控制系统导入数据](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)”。 +This utility imports Subversion history and file data into a Git branch. This is a straight copy of the tree, ignoring any trunk or branch distinction. For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)." ```shell git-import-svn-raw ``` -### git-import-tfs-raw +### git-import-tfs-raw -此实用程序可从 Team Foundation Version Control (TFVC) 导入。 有关详细信息,请参阅“[从第三方版本控制系统导入数据](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)”。 +This utility imports from Team Foundation Version Control (TFVC). For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)." ```shell git-import-tfs-raw ``` -### git-import-rewrite +### git-import-rewrite -此实用程序可重写导入的仓库。 这样,您将有机会重命名作者,对于 Subversion 和 TFVC,可基于文件夹生成 Git 分支。 有关详细信息,请参阅“[从第三方版本控制系统导入数据](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)”。 +This utility rewrites the imported repository. This gives you a chance to rename authors and, for Subversion and TFVC, produces Git branches based on folders. For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)." ```shell git-import-rewrite ``` {% ifversion ghes > 3.3 %} -## 安全 +## Security -### ghe-find-insecure-git-operations +### ghe-find-insecure-git-operations -此实用工具搜索实例的日志并通过 SSH 识别使用不安全算法或哈希函数(包括 DSA、RSA-SHA-1、HMAC-SHA-1 和 CBC 密码)的 Git 操作。 可以使用输出来支持每个客户端转换到更安全的 SSH 连接。 有关详细信息,请参阅 [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server){% ifversion ghes < 3.6 %}.{% elsif ghes > 3.5 %} 和“[配置与实例的 SSH 连接](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)。{% endif %} +This utility searches your instance's logs and identifies Git operations over SSH that use insecure algorithms or hash functions, including DSA, RSA-SHA-1, HMAC-SHA-1, and CBC ciphers. You can use the output to support each client's transition to a more secure SSH connection. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server){% ifversion ghes < 3.6 %}.{% elsif ghes > 3.5 %} and "[Configuring SSH connections to your instance](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)."{% endif %} ```shell ghe-find-insecure-git-operations @@ -764,167 +763,168 @@ ghe-find-insecure-git-operations {% endif %} -## 支持 +## Support -### ghe-diagnostics +### ghe-diagnostics -此实用程序会执行各项检查并收集关于安装的信息,您可以将此类信息发送给支持团队,以帮助诊断您遇到的问题。 +This utility performs a variety of checks and gathers information about your installation that you can send to support to help diagnose problems you're having. -目前,此实用程序的输出与下载 {% data variables.enterprise.management_console %} 中的诊断信息类似,但会逐渐增加一些 Web UI 中未提供的其他改进。 有关详细信息,请参阅“[创建和共享诊断文件](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-diagnostic-files)”。 +Currently, this utility's output is similar to downloading the diagnostics info in the {% data variables.enterprise.management_console %}, but may have additional improvements added to it over time that aren't available in the web UI. For more information, see "[Creating and sharing diagnostic files](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-diagnostic-files)." ```shell ghe-diagnostics ``` -### ghe-support-bundle +### ghe-support-bundle -{% data reusables.enterprise_enterprise_support.use_ghe_cluster_support_bundle %} 此实用程序会创建包含实例中重要日志的支持捆绑 tarball。 +{% data reusables.enterprise_enterprise_support.use_ghe_cluster_support_bundle %} +This utility creates a support bundle tarball containing important logs from your instance. -默认情况下,该命令在 /tmp 中创建 tarball,但也可以使用它将 tarball `cat` 为 `STDOUT`,以通过 SSH 轻松进行流式传输。 在 Web UI 未响应或从 /setup/support 下载支持包失败的情况下,可以使用此方法。 如果要生成包含旧日志的 extended 捆绑,则必须使用此命令。 您还可以使用此命令将支持包直接上传到 {% data variables.product.prodname_enterprise %} Support。 +By default, the command creates the tarball in */tmp*, but you can also have it `cat` the tarball to `STDOUT` for easy streaming over SSH. This is helpful in the case where the web UI is unresponsive or downloading a support bundle from */setup/support* doesn't work. You must use this command if you want to generate an *extended* bundle, containing older logs. You can also use this command to upload the support bundle directly to {% data variables.product.prodname_enterprise %} support. -要创建标准捆绑包: +To create a standard bundle: ```shell -$ ssh -p 122 admin@hostname -- 'ghe-support-bundle -o' > support-bundle.tgz +$ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -o' > support-bundle.tgz ``` -要创建扩展捆绑包: +To create an extended bundle: ```shell -$ ssh -p 122 admin@hostname -- 'ghe-support-bundle -x -o' > support-bundle.tgz +$ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -x -o' > support-bundle.tgz ``` -要将捆绑包发送至 {% data variables.contact.github_support %}: +To send a bundle to {% data variables.contact.github_support %}: ```shell -$ ssh -p 122 admin@hostname -- 'ghe-support-bundle -u' +$ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -u' ``` -要将捆绑包发送至 {% data variables.contact.github_support %} 并关联捆绑包与事件单: +To send a bundle to {% data variables.contact.github_support %} and associate the bundle with a ticket: ```shell -$ ssh -p 122 admin@hostname -- 'ghe-support-bundle -t ticket-id' +$ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -t TICKET_ID' ``` -### ghe-support-upload +### ghe-support-upload -此实用程序会将您的设备中的信息发送到 {% data variables.product.prodname_enterprise %} Support。 可以指定本地文件,或通过 `STDIN` 提供最大 100MB 的数据流。 可以选择将上传的数据与支持事件单相关联。 +This utility sends information from your appliance to {% data variables.product.prodname_enterprise %} support. You can either specify a local file, or provide a stream of up to 100MB of data via `STDIN`. The uploaded data can optionally be associated with a support ticket. -要将文件发送至 {% data variables.contact.github_support %} 并关联文件与事件单: +To send a file to {% data variables.contact.github_support %} and associate the file with a ticket: ```shell -ghe-support-upload -f path/to/your/file -t ticket-id +ghe-support-upload -f FILE_PATH -t TICKET_ID ``` -通过 `STDIN` 上传数据并关联数据与票证: +To upload data via `STDIN` and associating the data with a ticket: ```shell -ghe-repl-status -vv | ghe-support-upload -t ticket-id -d "Verbose Replication Status" +ghe-repl-status -vv | ghe-support-upload -t TICKET_ID -d "Verbose Replication Status" ``` -在此示例中,`ghe-repl-status -vv` 从副本设备发送详细状态信息。 应将 `ghe-repl-status -vv` 替换为要传输到 `STDIN` 的特定数据,并将 `Verbose Replication Status` 替换为数据的简单说明。 {% data reusables.enterprise_enterprise_support.support_will_ask_you_to_run_command %} +In this example, `ghe-repl-status -vv` sends verbose status information from a replica appliance. You should replace `ghe-repl-status -vv` with the specific data you'd like to stream to `STDIN`, and `Verbose Replication Status` with a brief description of the data. {% data reusables.enterprise_enterprise_support.support_will_ask_you_to_run_command %} -## 升级 {% data variables.product.prodname_ghe_server %} +## Upgrading {% data variables.product.prodname_ghe_server %} -### ghe-upgrade +### ghe-upgrade -此实用程序会安装或验证升级包。 如果升级失败或中断,您还可以使用此实用程序回滚补丁版本。 有关详细信息,请参阅“[升级 {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)”。 +This utility installs or verifies an upgrade package. You can also use this utility to roll back a patch release if an upgrade fails or is interrupted. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)." -要验证升级包: +To verify an upgrade package: ```shell -ghe-upgrade --verify UPGRADE-PACKAGE-FILENAME +ghe-upgrade --verify UPGRADE-PACKAGE-FILENAME ``` -要安装升级包: +To install an upgrade package: ```shell -ghe-upgrade UPGRADE-PACKAGE-FILENAME +ghe-upgrade UPGRADE-PACKAGE-FILENAME ``` {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %} -### ghe-upgrade-scheduler +### ghe-upgrade-scheduler -此实用程序可以管理已排定的升级包安装。 您可以显示、新建或移除已排定的安装。 您必须使用 cron 表达式创建日程。 有关详细信息,请参阅 [Cron Wikipedia 条目](https://en.wikipedia.org/wiki/Cron#Overview)。 +This utility manages scheduled installation of upgrade packages. You can show, create new, or remove scheduled installations. You must create schedules using cron expressions. For more information, see the [Cron Wikipedia entry](https://en.wikipedia.org/wiki/Cron#Overview). -要安排新的包安装: +To schedule a new installation for a package: ```shell -$ ghe-upgrade-scheduler -c "0 2 15 12 *" UPGRADE-PACKAGE-FILENAME +$ ghe-upgrade-scheduler -c "0 2 15 12 *" UPGRADE-PACKAGE-FILENAME ``` -要显示已安排的包安装: +To show scheduled installations for a package: ```shell -$ ghe-upgrade-scheduler -s UPGRADE PACKAGE FILENAME -> 0 2 15 12 * /usr/local/bin/ghe-upgrade -y -s UPGRADE-PACKAGE-FILENAME > /data/user/common/UPGRADE-PACKAGE-FILENAME.log 2>&1 +$ ghe-upgrade-scheduler -s UPGRADE PACKAGE FILENAME +> 0 2 15 12 * /usr/local/bin/ghe-upgrade -y -s UPGRADE-PACKAGE-FILENAME > /data/user/common/UPGRADE-PACKAGE-FILENAME.log 2>&1 ``` -要删除已安排的包安装: +To remove scheduled installations for a package: ```shell -$ ghe-upgrade-scheduler -r UPGRADE PACKAGE FILENAME +$ ghe-upgrade-scheduler -r UPGRADE PACKAGE FILENAME ``` -### ghe-update-check +### ghe-update-check -此实用程序将检查 {% data variables.product.prodname_enterprise %} 是否有新的补丁版本可用。 如果有新的补丁版本,并且实例中有可用空间,系统将下载此包。 默认情况下,包会保存到 /var/lib/ghe-updates。 然后,管理员可以[执行升级](/enterprise/admin/guides/installation/updating-the-virtual-machine-and-physical-resources/)。 +This utility will check to see if a new patch release of {% data variables.product.prodname_enterprise %} is available. If it is, and if space is available on your instance, it will download the package. By default, it's saved to */var/lib/ghe-updates*. An administrator can then [perform the upgrade](/enterprise/admin/guides/installation/updating-the-virtual-machine-and-physical-resources/). -包含下载状态的文件位于 /var/lib/ghe-updates/ghe-update-check.status。 +A file containing the status of the download is available at */var/lib/ghe-updates/ghe-update-check.status*. -要查看最新的 {% data variables.product.prodname_enterprise %} 版本,请使用 `-i` 开关。 +To check for the latest {% data variables.product.prodname_enterprise %} release, use the `-i` switch. ```shell -$ ssh -p 122 admin@hostname -- 'ghe-update-check' +$ ssh -p 122 admin@HOSTNAME -- 'ghe-update-check' ``` -## 用户管理 +## User management -### ghe-license-usage +### ghe-license-usage -此实用程序可按 JSON 格式导出安装用户列表。 如果您的实例连接至 {% data variables.product.prodname_ghe_cloud %},{% data variables.product.prodname_ghe_server %} 将使用此信息向 {% data variables.product.prodname_ghe_cloud %} 报告许可信息。 有关详细信息,请参阅“[将企业帐户连接到 {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)”。 +This utility exports a list of the installation's users in JSON format. If your instance is connected to {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} uses this information for reporting licensing information to {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %} ](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." -默认情况下,生成的 JSON 文件中的用户列表为加密格式。 将 `-h` 标志用于更多选项。 +By default, the list of users in the resulting JSON file is encrypted. Use the `-h` flag for more options. ```shell ghe-license-usage ``` -### ghe-org-membership-update +### ghe-org-membership-update -此实用程序将对您的实例中的所有成员强制实施默认的组织成员关系可见性设置。 有关详细信息,请参阅“[配置组织成员关系的可见性](/enterprise/admin/guides/user-management/configuring-visibility-for-organization-membership)”。 设置选项为 `public` 或 `private`。 +This utility will enforce the default organization membership visibility setting on all members in your instance. For more information, see "[Configuring visibility for organization membership](/enterprise/admin/guides/user-management/configuring-visibility-for-organization-membership)." Setting options are `public` or `private`. ```shell -ghe-org-membership-update --visibility=SETTING +ghe-org-membership-update --visibility=SETTING ``` ### `ghe-user-csv` -此实用程序可将所有安装用户列表导出为 CSV 格式。 CSV 文件包含电子邮件地址、用户所属类型(例如管理员、用户)、用户拥有的存储库数量、SSH 密钥数量、组织成员关系数量、上次登录的 IP 地址等。有关更多选项,请使用 `-h` 标志。 +This utility exports a list of all the users in the installation into CSV format. The CSV file includes the email address, which type of user they are (e.g., admin, user), how many repositories they have, how many SSH keys, how many organization memberships, last logged IP address, etc. Use the `-h` flag for more options. ```shell ghe-user-csv -o > users.csv ``` -### ghe-user-demote +### ghe-user-demote -此实用程序会将指定用户从管理员状态降级为普通用户状态。 建议使用 Web UI 执行此操作,但在 `ghe-user-promote` 实用程序运行出错并且需要再次通过 CLI 将用户降级的情况下提供此实用程序。 +This utility demotes the specified user from admin status to that of a regular user. We recommend using the web UI to perform this action, but provide this utility in case the `ghe-user-promote` utility is run in error and you need to demote a user again from the CLI. ```shell -ghe-user-demote some-user-name +ghe-user-demote USERNAME ``` -### ghe-user-promote +### ghe-user-promote -此实用程序会将指定用户帐户升级为站点管理员。 +This utility promotes the specified user account to a site administrator. ```shell -ghe-user-promote some-user-name +ghe-user-promote USERNAME ``` -### ghe-user-suspend +### ghe-user-suspend -此实用程序会挂起指定用户,避免他们登录、推送或从仓库拉取。 +This utility suspends the specified user, preventing them from logging in, pushing, or pulling from your repositories. ```shell -ghe-user-suspend some-user-name +ghe-user-suspend USERNAME ``` -### ghe-user-unsuspend +### ghe-user-unsuspend -此实用程序会取消挂起指定用户,向他们授予登录、推送以及从仓库拉取的权限。 +This utility unsuspends the specified user, granting them access to login, push, and pull from your repositories. ```shell -ghe-user-unsuspend some-user-name +ghe-user-unsuspend USERNAME ``` diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-applications.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-applications.md index fafdb9df1f..07a9b2af5d 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-applications.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-applications.md @@ -1,6 +1,6 @@ --- -title: 配置应用程序 -intro: '你可以为 {% data variables.product.product_location %} 配置内部应用程序设置。' +title: Configuring applications +intro: 'You can configure internal application settings for {% data variables.location.product_location %}.' redirect_from: - /enterprise/admin/installation/configuring-applications - /enterprise/admin/configuration/configuring-applications @@ -11,19 +11,15 @@ type: how_to topics: - Enterprise - Fundamentals -ms.openlocfilehash: bcc51bdabb5dc0b5ecdd4f77db9246a60c8df496 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145100074' --- -## 调整图像缓存 +## Adjusting image caching -可以选择 {% data variables.product.product_location %} 缓存头像的时长。 如果您增加缓存时间,则会增加加载用户头像所需的时长。 将缓存时间值配置为过小的值会导致 {% data variables.product.product_location %} 工作进程过载。 +You can choose the amount of time that {% data variables.location.product_location %} caches avatars. When you increase the cache time, you increase the amount of time a user's avatar will take to load. Configuring the cache time with too low a value can overload {% data variables.location.product_location %} work processes. -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} -3. 在左侧边栏中,单击“应用程序”。 -![设置边栏中的“应用程序”选项卡](/assets/images/enterprise/management-console/sidebar-applications.png) -4. 在“头像图像缓存时间(秒)”下,输入希望 {% data variables.product.product_location %} 缓存头像图像的秒数。 -![头像图像缓存表单字段](/assets/images/enterprise/management-console/add-image-caching-value-field.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +3. In the left sidebar, click **Applications**. +![Applications tab in the settings sidebar](/assets/images/enterprise/management-console/sidebar-applications.png) +4. Under "Avatar image cache time (seconds)", type the number of seconds that you would like {% data variables.location.product_location %} to cache avatar images. +![Avatar image caching form field](/assets/images/enterprise/management-console/add-image-caching-value-field.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md index 82d3255404..a8fecf4017 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md @@ -14,7 +14,7 @@ redirect_from: - /enterprise/admin/installation/configuring-backups-on-your-appliance - /enterprise/admin/configuration/configuring-backups-on-your-appliance - /admin/configuration/configuring-backups-on-your-appliance -intro: 'As part of a disaster recovery plan, you can protect production data on {% data variables.product.product_location %} by configuring automated backups.' +intro: 'As part of a disaster recovery plan, you can protect production data on {% data variables.location.product_location %} by configuring automated backups.' versions: ghes: '*' type: how_to @@ -26,7 +26,7 @@ topics: --- ## About {% data variables.product.prodname_enterprise_backup_utilities %} -{% data variables.product.prodname_enterprise_backup_utilities %} is a backup system you install on a separate host, which takes backup snapshots of {% data variables.product.product_location %} at regular intervals over a secure SSH network connection. You can use a snapshot to restore an existing {% data variables.product.prodname_ghe_server %} instance to a previous state from the backup host. +{% data variables.product.prodname_enterprise_backup_utilities %} is a backup system you install on a separate host, which takes backup snapshots of {% data variables.location.product_location %} at regular intervals over a secure SSH network connection. You can use a snapshot to restore an existing {% data variables.product.prodname_ghe_server %} instance to a previous state from the backup host. Only data added since the last snapshot will transfer over the network and occupy additional physical storage space. To minimize performance impact, backups are performed online under the lowest CPU/IO priority. You do not need to schedule a maintenance window to perform a backup. @@ -36,11 +36,11 @@ For more detailed information on features, requirements, and advanced usage, see ## Prerequisites -To use {% data variables.product.prodname_enterprise_backup_utilities %}, you must have a Linux or Unix host system separate from {% data variables.product.product_location %}. +To use {% data variables.product.prodname_enterprise_backup_utilities %}, you must have a Linux or Unix host system separate from {% data variables.location.product_location %}. You can also integrate {% data variables.product.prodname_enterprise_backup_utilities %} into an existing environment for long-term permanent storage of critical data. -We recommend that the backup host and {% data variables.product.product_location %} be geographically distant from each other. This ensures that backups are available for recovery in the event of a major disaster or network outage at the primary site. +We recommend that the backup host and {% data variables.location.product_location %} be geographically distant from each other. This ensures that backups are available for recovery in the event of a major disaster or network outage at the primary site. Physical storage requirements will vary based on Git repository disk usage and expected growth patterns: @@ -89,14 +89,14 @@ Backup snapshots are written to the disk path set by the `GHE_DATA_DIR` data dir {% note %} - **Note:** If {% data variables.product.product_location %} is deployed as a cluster or in a high availability configuration using a load balancer, the `GHE_HOSTNAME` can be the load balancer hostname, as long as it allows SSH access (on port 122) to {% data variables.product.product_location %}. + **Note:** If {% data variables.location.product_location %} is deployed as a cluster or in a high availability configuration using a load balancer, the `GHE_HOSTNAME` can be the load balancer hostname, as long as it allows SSH access (on port 122) to {% data variables.location.product_location %}. To ensure a recovered appliance is immediately available, perform backups targeting the primary instance even in a geo-replication configuration. {% endnote %} 1. Set the `GHE_DATA_DIR` value to the filesystem location where you want to store backup snapshots. We recommend choosing a location on the same filesystem as your backup host, but outside of where you cloned the Git repository in step 1. 1. To grant your backup host access to your instance, open your primary instance's settings page at `http(s)://HOSTNAME/setup/settings` and add the backup host's SSH key to the list of authorized SSH keys. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh#enabling-access-to-the-administrative-shell-via-ssh)." -1. On your backup host, verify SSH connectivity with {% data variables.product.product_location %} with the `ghe-host-check` command. +1. On your backup host, verify SSH connectivity with {% data variables.location.product_location %} with the `ghe-host-check` command. ```shell ./bin/ghe-host-check @@ -111,7 +111,7 @@ For more information on advanced usage, see the [{% data variables.product.prodn ## Upgrading {% data variables.product.prodname_enterprise_backup_utilities %} -When upgrading {% data variables.product.prodname_enterprise_backup_utilities %}, you must choose a release that will work with your current version of {% data variables.product.product_name %}. Your installation of {% data variables.product.prodname_enterprise_backup_utilities %} must be at least the same version as {% data variables.product.product_location %}, and cannot be more than two versions ahead. For more information, see [{% data variables.product.prodname_ghe_server %} version requirements](https://github.com/github/backup-utils/blob/master/docs/requirements.md#github-enterprise-server-version-requirements) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation. +When upgrading {% data variables.product.prodname_enterprise_backup_utilities %}, you must choose a release that will work with your current version of {% data variables.product.product_name %}. Your installation of {% data variables.product.prodname_enterprise_backup_utilities %} must be at least the same version as {% data variables.location.product_location %}, and cannot be more than two versions ahead. For more information, see [{% data variables.product.prodname_ghe_server %} version requirements](https://github.com/github/backup-utils/blob/master/docs/requirements.md#github-enterprise-server-version-requirements) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation. You can upgrade {% data variables.product.prodname_enterprise_backup_utilities %} in a Git repository by fetching and checking out the latest changes. Alternatively, if you don't use a Git repository for your installation, you can extract a new archive into place, or you can change your approach to use a Git repository instead. @@ -198,24 +198,24 @@ If backup attempts overlap, the `ghe-backup` command will abort with an error me ## Restoring a backup -In the event of prolonged outage or catastrophic event at the primary site, you can restore {% data variables.product.product_location %} by provisioning another {% data variables.product.prodname_enterprise %} appliance and performing a restore from the backup host. You must add the backup host's SSH key to the target {% data variables.product.prodname_enterprise %} appliance as an authorized SSH key before restoring an appliance. +In the event of prolonged outage or catastrophic event at the primary site, you can restore {% data variables.location.product_location %} by provisioning another {% data variables.product.prodname_enterprise %} appliance and performing a restore from the backup host. You must add the backup host's SSH key to the target {% data variables.product.prodname_enterprise %} appliance as an authorized SSH key before restoring an appliance. {% note %} -**Note:** When performing backup restores to {% data variables.product.product_location %}, the same version supportability rules apply. You can only restore data from at most two feature releases behind. +**Note:** When performing backup restores to {% data variables.location.product_location %}, the same version supportability rules apply. You can only restore data from at most two feature releases behind. For example, if you take a backup from {% data variables.product.product_name %} 3.0.x, you can restore the backup to a {% data variables.product.product_name %} 3.2.x instance. You cannot restore data from a backup of {% data variables.product.product_name %} 2.22.x to an instance running 3.2.x, because that would be three jumps between versions (2.22 to 3.0 to 3.1 to 3.2). You would first need to restore to an instance running 3.1.x, and then upgrade to 3.2.x. {% endnote %} -To restore {% data variables.product.product_location %} from the last successful snapshot, use the `ghe-restore` command. +To restore {% data variables.location.product_location %} from the last successful snapshot, use the `ghe-restore` command. {% note %} **Note:** Prior to restoring a backup, ensure: - Maintenance mode is enabled on the primary instance and all active processes have completed. For more information, see "[Enabling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)." - Replication is stopped on all replicas in high availability configurations. For more information, see the `ghe-repl-stop` command in "[About high availability configuration](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration#ghe-repl-stop)." -- If {% data variables.product.product_location %} has {% data variables.product.prodname_actions %} enabled, you must first configure the {% data variables.product.prodname_actions %} external storage provider on the replacement appliance. For more information, see "[Backing up and restoring {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %} enabled](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)." +- If {% data variables.location.product_location %} has {% data variables.product.prodname_actions %} enabled, you must first configure the {% data variables.product.prodname_actions %} external storage provider on the replacement appliance. For more information, see "[Backing up and restoring {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %} enabled](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)." {% endnote %} diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md index bc73631e43..d91bc49e77 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md @@ -1,6 +1,6 @@ --- title: Configuring email for notifications -intro: 'To make it easy for users to respond quickly to activity on {% data variables.product.product_name %}, you can configure {% data variables.product.product_location %} to send email notifications for issue, pull request, and commit comments.' +intro: 'To make it easy for users to respond quickly to activity on {% data variables.product.product_name %}, you can configure {% data variables.location.product_location %} to send email notifications for issue, pull request, and commit comments.' redirect_from: - /enterprise/admin/guides/installation/email-configuration - /enterprise/admin/articles/configuring-email @@ -159,7 +159,7 @@ This log shows that the appliance: * The `login` authentication type was performed (`<- "AUTH LOGIN\r\n"`). * The SMTP Server rejected the authentication as invalid (`-> "535-5.7.1 Username and Password not accepted.`). -### Check {% data variables.product.product_location %} logs +### Check {% data variables.location.product_location %} logs If you need to verify that your inbound email is functioning, there are two log files that you can examine on your instance: To verify that */var/log/mail.log* and */var/log/mail-replies/metroplex.log*. @@ -193,7 +193,7 @@ In order to properly process inbound emails, you must configure a valid A Record ### Check firewall or AWS Security Group settings -If {% data variables.product.product_location %} is behind a firewall or is being served through an AWS Security Group, make sure port 25 is open to all mail servers that send emails to `reply@reply.[hostname]`. +If {% data variables.location.product_location %} is behind a firewall or is being served through an AWS Security Group, make sure port 25 is open to all mail servers that send emails to `reply@reply.[hostname]`. ### Contact support {% ifversion ghes %} diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md index 07cad0fac6..13c0a766fb 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: 为企业配置 GitHub Pages -intro: '您可以为企业{% ifversion ghes %} 启用或禁用 {% data variables.product.prodname_pages %} ,并选择是否使网站{% endif %}可公开访问。' +title: Configuring GitHub Pages for your enterprise +intro: 'You can enable or disable {% data variables.product.prodname_pages %} for your enterprise{% ifversion ghes %} and choose whether to make sites publicly accessible{% endif %}.' redirect_from: - /enterprise/admin/guides/installation/disabling-github-enterprise-pages - /enterprise/admin/guides/installation/configuring-github-enterprise-pages @@ -17,68 +17,76 @@ topics: - Enterprise - Pages shortTitle: Configure GitHub Pages -ms.openlocfilehash: 1cb2bd78f006bfd86a3f0a2e42db4fcf2cea3b73 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145098112' --- + {% ifversion ghes %} -## 为 {% data variables.product.prodname_pages %} 启用公共站点 +## Enabling public sites for {% data variables.product.prodname_pages %} -如果在企业上启用了专用模式,则除非启用公用网站,否则公众无法访问企业托管的 {% data variables.product.prodname_pages %} 网站。 +If private mode is enabled on your enterprise, the public cannot access {% data variables.product.prodname_pages %} sites hosted by your enterprise unless you enable public sites. {% warning %} -**警告:** 如果为 {% data variables.product.prodname_pages %} 启用公共站点,则企业上每个存储库中的每个站点均可由公众访问。 +**Warning:** If you enable public sites for {% data variables.product.prodname_pages %}, every site in every repository on your enterprise will be accessible to the public. {% endwarning %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.pages-tab %} -4. 选择“公共页面”。 - ![启用“公共页面”的复选框](/assets/images/enterprise/management-console/public-pages-checkbox.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.pages-tab %} +4. Select **Public Pages**. + ![Checkbox to enable Public Pages](/assets/images/enterprise/management-console/public-pages-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} -## 为企业禁用 {% data variables.product.prodname_pages %} +## Disabling {% data variables.product.prodname_pages %} for your enterprise -如果为企业禁用了子域隔离,则还应禁用 {% data variables.product.prodname_pages %},以免遭受潜在安全漏洞的攻击。 有关详细信息,请参阅“[启用子域隔离](/admin/configuration/enabling-subdomain-isolation)”。 +If subdomain isolation is disabled for your enterprise, you should also disable {% data variables.product.prodname_pages %} to protect yourself from potential security vulnerabilities. For more information, see "[Enabling subdomain isolation](/admin/configuration/enabling-subdomain-isolation)." -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.pages-tab %} -1. 取消选择“启用页面”。 - ![禁用 {% data variables.product.prodname_pages %} 的复选框](/assets/images/enterprise/management-console/pages-select-button.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.pages-tab %} +1. Unselect **Enable Pages**. + ![Checkbox to disable {% data variables.product.prodname_pages %}](/assets/images/enterprise/management-console/pages-select-button.png) +{% data reusables.enterprise_management_console.save-settings %} {% endif %} {% ifversion ghae %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.pages-tab %} -1. 在“页面策略”下,取消选择“启用 {% data variables.product.prodname_pages %}”。 - ![禁用 {% data variables.product.prodname_pages %} 的复选框](/assets/images/enterprise/business-accounts/enable-github-pages-checkbox.png) {% data reusables.enterprise-accounts.pages-policies-save %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.pages-tab %} +1. Under "Pages policies", deselect **Enable {% data variables.product.prodname_pages %}**. + ![Checkbox to disable {% data variables.product.prodname_pages %}](/assets/images/enterprise/business-accounts/enable-github-pages-checkbox.png) +{% data reusables.enterprise-accounts.pages-policies-save %} {% endif %} {% ifversion ghes > 3.4 %} -## 为企业配置 {% data variables.product.prodname_pages %} 响应头 +## Configuring {% data variables.product.prodname_pages %} response headers for your enterprise -你可以为 {% data variables.product.product_location %} 托管的 {% data variables.product.prodname_pages %} 站点添加或覆盖响应头。 +You can add or override response headers for {% data variables.product.prodname_pages %} sites hosted by {% data variables.location.product_location %}. {% warning %} -**警告:** 确保在保存前正确配置响应头。 配置错误可能会对 {% data variables.product.product_location %} 的安全性产生负面影响。 +**Warning:** Ensure that your response headers are properly configured before saving. Improper configurations may negatively impact the security of {% data variables.location.product_location %}. {% endwarning %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.pages-tab %} -1. 键入标头设置,然后单击“添加标头”。 - - 在“Http 标头名称”字段中,输入标头名称。 标头名称的长度应小于 128 个字符。 - - 在“Http 标头值”字段中,键入标头值。 标头值的长度应小于 300 个字符。 -![{% data variables.enterprise.management_console %} 中的 {% data variables.product.prodname_pages %} 响应头名称和值字段](/assets/images/enterprise/management-console/pages-override-header-section.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.pages-tab %} +1. Type the headers settings, then click **Add headers**. + - In the **Http Header Name** field, type the header name. The length of header name should less than 128 characters. + - In the **Http Header Value** field, type the header value. The length of header value should less than 300 characters. +![The {% data variables.product.prodname_pages %} response header name and value fields in the {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/pages-override-header-section.png) +{% data reusables.enterprise_management_console.save-settings %} {% endif %} {% ifversion ghes %} -## 延伸阅读 +## Further reading -- “[启用专用模式](/admin/configuration/enabling-private-mode)”{% endif %} +- "[Enabling private mode](/admin/configuration/enabling-private-mode)" +{% endif %} diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md index f2d1947fec..0930d0297d 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md @@ -1,8 +1,8 @@ --- -title: 为实例配置主机密钥 +title: Configuring host keys for your instance shortTitle: Configure host keys -intro: '可通过配置实例用来为传入 SSH 连接生成和播发主机密钥的算法,来提高 {% data variables.product.product_location %} 的安全性。' -permissions: 'Site administrators can configure the host keys for a {% data variables.product.product_name %} instance.' +intro: 'You can increase the security of {% data variables.location.product_location %} by configuring the algorithms that your instance uses to generate and advertise host keys for incoming SSH connections.' +permissions: "Site administrators can configure the host keys for a {% data variables.product.product_name %} instance." versions: ghes: '>= 3.6' type: how_to @@ -13,38 +13,33 @@ topics: - Networking - Security - SSH -ms.openlocfilehash: d7ab49b814500ac2c35fa65f82c0fb480122ed1b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147410726' --- -## 关于实例的主机密钥 -接受 SSH 连接的服务器将播发一个或多个加密主机密钥,以安全地识别 SSH 客户端的服务器。 为了在连接初始化期间确认服务器的标识,客户端会存储并验证主机密钥。 有关详细信息,请参阅 SSH Academy 网站上的 [SSH 主机密钥 - 内容、原因、方法](https://ssh.com/academy/ssh/host-key)。 +## About host keys for your instance + +Servers that accept SSH connections advertise one or more cryptographic host keys to securely identify the server to SSH clients. To confirm the server's identity during the initialization of a connection, clients store and verify the host key. For more information, see [SSH Host Key - What, Why, How](https://ssh.com/academy/ssh/host-key) on the SSH Academy website. {% data reusables.enterprise.about-ssh-ports %} -默认情况下,{% data variables.product.product_location %} 使用 OpenSSH 样式的主机密钥轮换来生成和播发主机密钥。 若要在环境中提高 SSH 的安全性,可以启用其他算法来生成主机密钥。 +By default, {% data variables.location.product_location %} generates and advertises host keys with OpenSSH-style host key rotation. To increase the security of SSH in your environment, you can enable additional algorithms for the generation of host keys. {% note %} -注意:如果启用其他主机密钥算法,则不使用 OpenSSH 进行 SSH 连接的客户端可能会在连接过程中遇到警告,或者无法完全连接。 一些 SSH 实现可以忽略不受支持的算法并退回到其他算法。 如果客户端不支持回退操作,连接将失败。 例如,适用于 Go 的 SSH 库不支持回退到其他算法。 +**Note**: If you enable additional host key algorithms, clients that do not use OpenSSH for SSH connections may experience warnings during connection, or fail to connect entirely. Some SSH implementations can ignore unsupported algorithms and fall back to a different algorithm. If the client does not support fallback, the connection will fail. For example, the SSH library for Go does not support fallback to a different algorithm. {% endnote %} -## 管理 Ed25519 主机密钥 +## Managing an Ed25519 host key -若要提高连接到 {% data variables.product.product_location %} 的客户端的安全性,可以启用 Ed25519 主机密钥的生成和播发。 Ed25519 可在不降低速度的情况免受对一些针对旧版签名算法的攻击。 旧版 SSH 客户端可能不支持 Ed25519。 默认情况下,{% data variables.product.product_name %} 实例不会生成或播发 Ed25519 主机密钥。 有关详细信息,请参阅 [Ed25519 网站](https://ed25519.cr.yp.to)。 +To improve security for clients that connect to {% data variables.location.product_location %}, you can enable the generation and advertisement of an Ed25519 host key. Ed25519 is immune to some attacks that target older signature algorithms, without sacrificing speed. Older SSH clients may not support Ed25519. By default, {% data variables.product.product_name %} instances do not generate or advertise an Ed25519 host key. For more information, see [the Ed25519 website](https://ed25519.cr.yp.to). {% data reusables.enterprise_installation.ssh-into-instance %} -1. 要启用 Ed25519 主机密钥的生成和播发,请输入以下命令。 +1. To enable generation and advertisement of the Ed25519 host key, enter the following command. ```shell ghe-config app.babeld.host-key-ed25519 true ``` -1. (可选)输入以下命令以禁用 Ed25519 主机密钥的生成和播发。 +1. Optionally, enter the following command to disable generation and advertisement of the Ed25519 host key. ```shell ghe-config app.babeld.host-key-ed25519 false diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md index 56837a896b..a3a2e28ce7 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md @@ -36,7 +36,7 @@ You can exempt a list of users from API rate limits using the `ghe-config` utili ## Enabling secondary rate limits -Setting secondary rate limits protects the overall level of service on {% data variables.product.product_location %}. +Setting secondary rate limits protects the overall level of service on {% data variables.location.product_location %}. {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} @@ -76,13 +76,13 @@ You can apply a rate limit to {% data variables.product.prodname_actions %} work ### About rate limits for {% data variables.product.prodname_actions %} -Your {% data variables.product.product_name %} instance assigns each {% data variables.product.prodname_actions %} workflow job to a runner. If your instance cannot immediately assign a job to an available runner, the job will wait in a queue until a runner is available. If {% data variables.product.prodname_actions %} experiences sustained high load, the queue can back up, and the performance of {% data variables.product.product_location %} may degrade. +Your {% data variables.product.product_name %} instance assigns each {% data variables.product.prodname_actions %} workflow job to a runner. If your instance cannot immediately assign a job to an available runner, the job will wait in a queue until a runner is available. If {% data variables.product.prodname_actions %} experiences sustained high load, the queue can back up, and the performance of {% data variables.location.product_location %} may degrade. To avoid this performance degradation, you can configure a rate limit for {% data variables.product.prodname_actions %}. This rate limit is expressed in job runs per minute. {% data variables.product.product_name %} calculates and applies the rate limit for the sum total of all job runs on the instance. If runs exceed the rate limit, additional runs will fail instead of entering the queue. The following error will appear in the run's annotations. > You've exceeded the rate limit for workflow run requests. Please wait before retrying the run. -An appropriate rate limit protects {% data variables.product.product_location %} from abnormal usage of {% data variables.product.prodname_actions %} without interfering with day-to-day operations. The exact threshold depends on your instance's available resources and overall load profile. For more information about the hardware requirements for {% data variables.product.prodname_actions %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-requirements)." +An appropriate rate limit protects {% data variables.location.product_location %} from abnormal usage of {% data variables.product.prodname_actions %} without interfering with day-to-day operations. The exact threshold depends on your instance's available resources and overall load profile. For more information about the hardware requirements for {% data variables.product.prodname_actions %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-requirements)." By default, the rate limit for {% data variables.product.prodname_actions %} is disabled. Because {% data variables.product.product_name %} can handle temporary spikes in usage without performance degradation, this rate limit is intended to protect against sustained high load. We recommend leaving the rate limit disabled unless you are experiencing performance problems. In some cases, {% data variables.contact.github_support %} may recommend that you enable a rate limit for {% data variables.product.prodname_actions %}. diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md index 5daeb8c301..c76cd8b27b 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md @@ -1,8 +1,8 @@ --- -title: 配置与实例的 SSH 连接 +title: Configuring SSH connections to your instance shortTitle: Configure SSH connections -intro: '可以通过配置客户端可用于建立连接的 SSH 算法来提高 {% data variables.product.product_location %} 的安全性。' -permissions: 'Site administrators can configure SSH connections to a {% data variables.product.product_name %} instance.' +intro: 'You can increase the security of {% data variables.location.product_location %} by configuring the SSH algorithms that clients can use to establish a connection.' +permissions: "Site administrators can configure SSH connections to a {% data variables.product.product_name %} instance." versions: ghes: '>= 3.6' type: how_to @@ -13,43 +13,38 @@ topics: - Networking - Security - SSH -ms.openlocfilehash: cf884172028d5419a0cf5287b4a108ee7ca52c12 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147409759' --- -## 关于与实例的 SSH 连接 + +## About SSH connections to your instance {% data reusables.enterprise.about-ssh-ports %} -若要在你的环境中容纳 SSH 客户端,可以配置 {% data variables.product.product_location %} 将接受的连接类型。 +To accommodate the SSH clients in your environment, you can configure the types of connections that {% data variables.location.product_location %} will accept. -## 使用 RSA 密钥配置 SSH 连接 +## Configuring SSH connections with RSA keys -当用户通过端口 22 借助 SSH 在 {% data variables.product.product_location %} 上执行 Git 操作时,客户端可以使用 RSA 密钥进行身份验证。 客户端可以使用 SHA-1 哈希函数对尝试进行签名。 在此上下文中,SHA-1 哈希函数不再安全。 有关详细信息,请参阅维基百科上的 [SHA-1](https://en.wikipedia.org/wiki/SHA-1)。 +When users perform Git operations on {% data variables.location.product_location %} via SSH over port 22, the client can authenticate with an RSA key. The client may sign the attempt using the SHA-1 hash function. In this context, the SHA-1 hash function is no longer secure. For more information, see [SHA-1](https://en.wikipedia.org/wiki/SHA-1) on Wikipedia. -默认情况下{% ifversion ghes < 3.7 %},在 {% data variables.product.product_name %} 3.6 及更高版本上{% endif %},同时满足以下两个条件的 SSH 连接将失败。 +By default{% ifversion ghes < 3.7 %} on {% data variables.product.product_name %} 3.6 and later{% endif %}, SSH connections that satisfy **both** of the following conditions will fail. {% data reusables.ssh.rsa-sha-1-connection-failure-criteria %} -可以调整截止日期。 如果用户在截止日期之前上传了 RSA 密钥,只要密钥保持有效,客户端便可以继续使用 SHA-1 成功连接。 或者,如果客户端使用 SHA-1 哈希函数对连接进行签名,你可以拒绝所有使用 RSA 密钥进行身份验证的 SSH 连接。 +You can adjust the cutoff date. If the user uploaded the RSA key before the cutoff date, the client can continue to connect successfuly using SHA-1 as long as the key remains valid. Alternatively, you can reject all SSH connections authenticated with an RSA key if the client signs the connection using the SHA-1 hash function. -无论你为实例选择何种设置,客户端都可以继续使用任何使用 SHA-2 哈希函数签名的 RSA 密钥进行连接。 +Regardless of the setting you choose for your instance, clients can continue to connect using any RSA key signed with a SHA-2 hash function. -若使用 SSH 证书颁发机构,如果证书的 `valid_after` 日期晚于截止日期,则连接将失败。 有关详细信息,请参阅“[关于 SSH 证书颁发机构](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)”。 +If you use an SSH certificate authority, connections will fail if the certificate's `valid_after` date is after the cutoff date. For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)." -有关详细信息,请参阅 [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server)。 +For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server). {% data reusables.enterprise_installation.ssh-into-instance %} -1. 使用 `ghe-find-insecure-git-operations` 实用工具审核实例的日志以查找使用不安全算法或哈希函数的连接。 有关详细信息,请参阅“[命令行实用工具](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-find-insecure-git-operations)”。 -1. 若要配置一个截止日期,在该截止日期之后,{% data variables.product.product_location %} 将拒绝来自使用该日期之后上传的 RSA 密钥的客户端的连接(如果连接由 SHA-1 哈希函数签名),请输入以下命令。 将 RFC-3399-UTC-TIMESTAMP 替换为有效的 RFC 3399 UTC 时间戳。 例如,默认值 2022 年 8 月 1 日将表示为 `2022-08-01T00:00:00Z`。 有关详细信息,请参阅 IETF 网站上的 [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339)。 +1. Audit your instance's logs for connections that use unsecure algorithms or hash functions using the `ghe-find-insecure-git-operations` utility. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-find-insecure-git-operations)." +1. To configure a cutoff date after which {% data variables.location.product_location %} will deny connections from clients that use an RSA key uploaded after the date if the connection is signed by the SHA-1 hash function, enter the following command. Replace _**RFC-3399-UTC-TIMESTAMP**_ with a valid RFC 3399 UTC timestamp. For example, the default value, August 1, 2022, would be represented as `2022-08-01T00:00:00Z`. For more information, see [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) on the IETF website.
-   $ ghe-config app.gitauth.rsa-sha1 RFC-3339-UTC-TIMESTAMP
+   $ ghe-config app.gitauth.rsa-sha1 RFC-3339-UTC-TIMESTAMP
    
-1. 或者,若要完全禁用使用由 SHA-1 哈希函数签名的 RSA 密钥的 SSH 连接,请输入以下命令。 +1. Alternatively, to completely disable SSH connections using RSA keys that are signed with the SHA-1 hash function, enter the following command. ```shell ghe-config app.gitauth.rsa-sha1 false diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md index a81684ae15..ef1314f097 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: 为企业配置引荐来源网址策略 +title: Configuring the referrer policy for your enterprise shortTitle: Configure referrer policy -intro: '您可以通过为跨域请求配置策略来增强 {% data variables.product.product_location %} 的隐私保护。' +intro: 'You can increase the privacy of {% data variables.location.product_location %} by configuring the policy for cross-origin requests.' versions: ghes: '*' type: how_to @@ -10,33 +10,29 @@ topics: - Networking - Privacy - Security -ms.openlocfilehash: 4824e938e044a89e9d0e534564214c6a46ba44da -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147066488' --- -## 关于企业的引荐来源网址策略 -引荐来源网址策略控制当有人访问从 {% data variables.product.product_location %} 到外部站点的链接时,{% data variables.product.product_name %} 在 HTTP 标头中传输的信息。 +## About the referrer policy for your enterprise -默认情况下,当 {% data variables.product.product_location %} 上的用户从你的实例上的文件或注释中访问指向另一个站点的链接时,请求会在 `Referer` 标头中以纯文本形式包含你的实例的主机名。 如果链接指向外部网站,则网站的所有者可以在请求或日志文件中读取您的实例的主机名。 +The referrer policy controls the information that {% data variables.product.product_name %} transmits in HTTP headers when someone visits a link from {% data variables.location.product_location %} to an external site. -您可以控制当用户从您的实例访问链接时 {% data variables.product.product_name %} 发送的信息。 +By default, when a user on {% data variables.location.product_location %} visits a link to another site from a file or comment on your instance, the request includes the hostname for your instance in plain text within the `Referer` header. If the link leads to an external website, the owner of the website could read the hostname for your instance in requests or log files. -## 启用 `same-origin` 引荐者策略 +You can control the information that {% data variables.product.product_name %} sends when a user visits a link from your instance. -可以启用 `same-origin` 引荐者策略,以指示新式浏览器将 {% data variables.product.product_location %} 的主机名排除在对外部网站的请求之外。 该设置适用于实例上 Web 界面中的所有链接。 默认情况下,{% data variables.product.product_name %} 使用 `origin-when-cross-origin` 和 `strict-origin-when-cross-origin` 引荐者策略,这意味着实例的主机名将显示在对外部网站的 HTTP 和 HTTPS 请求中。 +## Enabling the `same-origin` referrer policy + +You can enable the `same-origin` referrer policy to instruct modern browsers to exclude the hostname for {% data variables.location.product_location %} from requests to external websites. The setting applies to all links from the web interface on your instance. By default, {% data variables.product.product_name %} uses the `origin-when-cross-origin` and `strict-origin-when-cross-origin` referrer policies, which means your instance's hostname will appear in HTTP and HTTPS requests to external websites. {% note %} -注意:将引荐者策略更改为 `same-origin` 可能会影响要求请求的 HTTP 标头中有主机名的外部站点。 +**Note**: Changing the referrer policy to `same-origin` can affect external sites that expect a hostname in the HTTP headers for a request. {% endnote %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} -1. 在“用户代理引荐者策略”下,选择“为所有组织启用同源引荐者策略”。 - ![用于启用同源引荐者策略的复选框](/assets/images/enterprise/settings/referrer-policy-checkbox.png) -1. 单击“ **保存**”。 - ![用于启用同源引荐者策略的“保存”按钮](/assets/images/enterprise/settings/referrer-policy-save-button.png) +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +1. Under "User Agent Referrer Policy", select **Enable same origin referrer policy for all organizations**. + ![Checkbox for enabling same origin referrer policy](/assets/images/enterprise/settings/referrer-policy-checkbox.png) +1. Click **Save**. + ![Save button for enabling same origin referrer policy](/assets/images/enterprise/settings/referrer-policy-save-button.png) diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md index 3d44679d6f..37a73bf097 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md @@ -1,7 +1,7 @@ --- -title: 配置 Web 提交签名 +title: Configuring web commit signing shortTitle: Configure web commit signing -intro: '可以在 {% data variables.product.product_name %} 的 Web 界面中启用提交自动签名。' +intro: 'You can enable auto-signing of commits made in the web interface of {% data variables.product.product_name %}.' versions: ghes: '>=3.5' type: how_to @@ -11,62 +11,67 @@ topics: - Fundamentals - Identity - Security -permissions: 'Site administrators can configure web commit signing for {% data variables.product.product_location %}.' -ms.openlocfilehash: 759b158235e5727b474441d10b33016b58277c7f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147068032' +permissions: 'Site administrators can configure web commit signing for {% data variables.location.product_location %}.' --- -## 关于 Web 提交签名 -如果启用 Web 提交签名,{% data variables.product.product_name %} 将自动使用 GPG 对用户在 {% data variables.product.product_location %} 的 Web 界面上所做的提交进行签名。 由 {% data variables.product.product_name %} 签名的提交将具有已验证状态。 有关详细信息,请参阅“[关于提交签名验证](/authentication/managing-commit-signature-verification/about-commit-signature-verification)”。 +## About web commit signing -可以启用 Web 提交签名,轮换用于 Web 提交签名的私钥,以及禁用 Web 提交签名。 +If you enable web commit signing, {% data variables.product.product_name %} will automatically use GPG to sign commits users make on the web interface of {% data variables.location.product_location %}. Commits signed by {% data variables.product.product_name %} will have a verified status. For more information, see "[About commit signature verification](/authentication/managing-commit-signature-verification/about-commit-signature-verification)." -## 启用 Web 提交签名 +You can enable web commit signing, rotate the private key used for web commit signing, and disable web commit signing. + +## Enabling web commit signing {% data reusables.enterprise_site_admin_settings.create-pgp-key-web-commit-signing %} - - 如果在 {% data variables.enterprise.management_console %} 中定义了无答复电子邮件地址,请使用该电子邮件地址。 如果没有,请使用任何电子邮件地址,例如 `web-flow@my-company.com`。 电子邮件地址不需要是有效的。 -{% data reusables.enterprise_site_admin_settings.pgp-key-no-passphrase %} {% data reusables.enterprise_site_admin_settings.pgp-key-env-variable %} {% data reusables.enterprise_site_admin_settings.update-commit-signing-service %} -1. 启用 Web 提交签名。 + - Use `web-flow` as the username. If `web-flow` is unavailable or unusable, use any new unique username. Use this username throughout the following steps in this article. + - If you have a no-reply email address defined in the {% data variables.enterprise.management_console %}, use that email address. If not, use any email address, such as `web-flow@my-company.com`. The email address does not need to be valid. +{% data reusables.enterprise_site_admin_settings.pgp-key-no-passphrase %} +{% data reusables.enterprise_site_admin_settings.pgp-key-env-variable %} +{% data reusables.enterprise_site_admin_settings.update-commit-signing-service %} +1. Enable web commit signing. ```bash{:copy} ghe-config app.github.web-commit-signing-enabled true ``` -1. 应用配置,然后等待配置运行完成。 +1. Apply the configuration, then wait for the configuration run to complete. ```bash{:copy} ghe-config-apply ``` -1. 通过内置身份验证或外部身份验证在 {% data variables.product.product_location %} 上创建新用户。 有关详细信息,请参阅“[关于企业身份验证](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)”。 - - 用户的用户名必须是 `web-flow`。 - - 用户的电子邮件地址必须与用于 PGP 密钥的地址相同。 {% data reusables.enterprise_site_admin_settings.add-key-to-web-flow-user %} {% data reusables.enterprise_site_admin_settings.email-settings %} -1. 在“无答复电子邮件地址”下,键入用于 PGP 密钥的同一个电子邮件地址。 +1. Create a new user on {% data variables.location.product_location %} via built-in authentication or external authentication. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)." + - The user's username must be the same username you used when creating the PGP key in step 1 above, for example, `web-flow`. + - The user's email address must be the same address you used when creating the PGP key. +{% data reusables.enterprise_site_admin_settings.add-key-to-web-flow-user %} +{% data reusables.enterprise_site_admin_settings.email-settings %} +1. Under "No-reply email address", type the same email address you used when creating the PGP key. {% note %} - 注意:仅当为 {% data variables.product.product_location %} 启用电子邮件时,才会显示“无答复电子邮件地址”字段。 有关详细信息,请参阅“[配置邮件通知](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications#configuring-smtp-for-your-enterprise)”。 + **Note:** The "No-reply email address" field will only be displayed if you've enabled email for {% data variables.location.product_location %}. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications#configuring-smtp-for-your-enterprise)." - {% endnote %} {% data reusables.enterprise_management_console.save-settings %} + {% endnote %} +{% data reusables.enterprise_management_console.save-settings %} -## 轮换用于 Web 提交签名的私钥 +## Rotating the private key used for web commit signing {% data reusables.enterprise_site_admin_settings.create-pgp-key-web-commit-signing %} - - 使用 {% data variables.enterprise.management_console %} 中定义的无答复电子邮件地址,该地址应与 `web-flow` 用户的电子邮件地址相同。 -{% data reusables.enterprise_site_admin_settings.pgp-key-no-passphrase %} {% data reusables.enterprise_site_admin_settings.pgp-key-env-variable %} {% data reusables.enterprise_site_admin_settings.update-commit-signing-service %} {% data reusables.enterprise_site_admin_settings.add-key-to-web-flow-user %} + - Use the web commit signing user's username, for example, `web-flow`. + - Use the no-reply email address defined in the {% data variables.enterprise.management_console %}, which should be the same as the email address of the web commit signing user, for example, `web-flow`. +{% data reusables.enterprise_site_admin_settings.pgp-key-no-passphrase %} +{% data reusables.enterprise_site_admin_settings.pgp-key-env-variable %} +{% data reusables.enterprise_site_admin_settings.update-commit-signing-service %} +{% data reusables.enterprise_site_admin_settings.add-key-to-web-flow-user %} -## 禁用 Web 提交签名 +## Disabling web commit signing -可以为 {% data variables.product.product_location %} 禁用 Web 提交签名。 +You can disable web commit signing for {% data variables.location.product_location %}. -1. 在管理 shell 中,运行以下命令。 +1. In the administrative shell, run the following command. ```bash{:copy} ghe-config app.github.web-commit-signing-enabled false ``` -1. 应用配置。 +1. Apply the configuration. ```bash{:copy} ghe-config-apply diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md index 4226682a33..fd5a8111b5 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md @@ -1,6 +1,6 @@ --- -title: 启用和排定维护模式 -intro: '一些标准维护程序(例如升级 {% data variables.product.product_location %} 或还原备份)要求实例进入脱机状态才能正常使用。' +title: Enabling and scheduling maintenance mode +intro: 'Some standard maintenance procedures, such as upgrading {% data variables.location.product_location %} or restoring backups, require the instance to be taken offline for normal use.' redirect_from: - /enterprise/admin/maintenance-mode - /enterprise/admin/categories/maintenance-mode @@ -20,80 +20,77 @@ topics: - Maintenance - Upgrades shortTitle: Configure maintenance mode -ms.openlocfilehash: 45ac412b1ae13e69d710c4dd93072143f6ffa502 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146331766' --- -## 关于维护模式 +## About maintenance mode -某些操作类型要求你让 {% data variables.product.product_location %} 进入脱机状态并将其置于维护模式: -- 升级到新版本的 {% data variables.product.prodname_ghe_server %} -- 增加分配给虚拟机的 CPU、内存或存储资源 -- 将数据从一台虚拟机迁移到另一台虚拟机 -- 通过 {% data variables.product.prodname_enterprise_backup_utilities %} 快照还原数据 -- 排查某些类型的关键应用程序问题 +Some types of operations require that you take {% data variables.location.product_location %} offline and put it into maintenance mode: +- Upgrading to a new version of {% data variables.product.prodname_ghe_server %} +- Increasing CPU, memory, or storage resources allocated to the virtual machine +- Migrating data from one virtual machine to another +- Restoring data from a {% data variables.product.prodname_enterprise_backup_utilities %} snapshot +- Troubleshooting certain types of critical application issues -我们建议您至少将维护窗口排定在 30 分钟后,以便用户提前作好准备。 排定维护窗口后,所有用户在访问站点时都会看到横幅。 +We recommend that you schedule a maintenance window for at least 30 minutes in the future to give users time to prepare. When a maintenance window is scheduled, all users will see a banner when accessing the site. -![关于已排定维护的最终用户横幅](/assets/images/enterprise/maintenance/maintenance-scheduled.png) +![End user banner about scheduled maintenance](/assets/images/enterprise/maintenance/maintenance-scheduled.png) -在实例进入维护模式后,所有正常 HTTP 和 Git 访问都会遭到拒绝。 Git 提取、克隆和推送操作也会被拒绝,并显示一条错误消息,指示站点暂时不可用。 在高可用性配置中,Git 复制将暂停。 GitHub Actions 作业不会执行。 在浏览器中访问该站点会显示维护页面。 +When the instance is in maintenance mode, all normal HTTP and Git access is refused. Git fetch, clone, and push operations are also rejected with an error message indicating that the site is temporarily unavailable. In high availability configurations, Git replication will be paused. GitHub Actions jobs will not be executed. Visiting the site in a browser results in a maintenance page. -![维护模式启动屏幕](/assets/images/enterprise/maintenance/maintenance-mode-maintenance-page.png) +![The maintenance mode splash screen](/assets/images/enterprise/maintenance/maintenance-mode-maintenance-page.png) {% ifversion ip-exception-list %} -可以通过配置 IP 例外列表来执行维护操作的初始验证,以仅允许从提供的 IP 地址和范围访问 {% data variables.product.product_location %}。 尝试从未在 IP 例外列表中指定的 IP 地址访问 {% data variables.product.product_location %} 时收到的响应与实例处于维护模式时发送的响应一致。 +You can perform initial validation of your maintenance operation by configuring an IP exception list to allow access to {% data variables.location.product_location %} from only the IP addresses and ranges provided. Attempts to access {% data variables.location.product_location %} from IP addresses not specified on the IP exception list will receive a response consistent with those sent when the instance is in maintenance mode. {% endif %} -## 立即启用维护模式或排定在未来的某个时间进行维护 +## Enabling maintenance mode immediately or scheduling a maintenance window for a later time -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} -2. 在 {% data variables.enterprise.management_console %} 顶部,单击“维护”。 - ![“维护”选项卡](/assets/images/enterprise/management-console/maintenance-tab.png) -3. 在“Enable and schedule”下,决定立即启用维护模式还是排定在未来的某个时间进行维护。 - - 若要立即启用维护模式,请使用下拉菜单,然后单击“立即”。 - ![包含已选择立即启用维护模式的选项的下拉菜单](/assets/images/enterprise/maintenance/enable-maintenance-mode-now.png) - - 要排定在未来的某个时间进行维护,请使用下拉菜单,然后单击开始时间。 - ![包含已选择排定在两小时后进行维护的选项的下拉菜单](/assets/images/enterprise/maintenance/schedule-maintenance-mode-two-hours.png) -4. 选择“启用维护模式”。 - ![用于启用或计划维护模式的复选框](/assets/images/enterprise/maintenance/enable-maintenance-mode-checkbox.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +2. At the top of the {% data variables.enterprise.management_console %}, click **Maintenance**. + ![Maintenance tab](/assets/images/enterprise/management-console/maintenance-tab.png) +3. Under "Enable and schedule", decide whether to enable maintenance mode immediately or to schedule a maintenance window for a future time. + - To enable maintenance mode immediately, use the drop-down menu and click **now**. + ![Drop-down menu with the option to enable maintenance mode now selected](/assets/images/enterprise/maintenance/enable-maintenance-mode-now.png) + - To schedule a maintenance window for a future time, use the drop-down menu and click a start time. + ![Drop-down menu with the option to schedule a maintenance window in two hours selected](/assets/images/enterprise/maintenance/schedule-maintenance-mode-two-hours.png) +4. Select **Enable maintenance mode**. + ![Checkbox for enabling or scheduling maintenance mode](/assets/images/enterprise/maintenance/enable-maintenance-mode-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} {% ifversion ip-exception-list %} -## 使用 IP 例外列表在维护模式下验证更改 +## Validating changes in maintenance mode using the IP exception list -IP 例外列表提供对 {% data variables.product.product_location %} 的受控和受限访问,这非常适合在执行维护操作后对服务器运行状况进行初始验证。 启用后,{% data variables.product.product_location %} 将退出维护模式,并且仅适用于配置的 IP 地址。 维护模式复选框将更新,以反映状态更改。 +The IP exception list provides controlled and restricted access to {% data variables.location.product_location %}, which is ideal for initial validation of server health following a maintenance operation. Once enabled, {% data variables.location.product_location %} will be taken out of maintenance mode and available only to the configured IP addresses. The maintenance mode checkbox will be updated to reflect the change in state. -如果重新启用维护模式,将禁用 IP 例外列表,并且 {% data variables.product.product_location %} 将恢复维护模式。 如果只是禁用 IP 例外列表,{% data variables.product.product_location %} 将恢复正常操作。 +If you re-enable maintenance mode, the IP exception list will be disabled and {% data variables.location.product_location %} will return to maintenance mode. If you just disable the IP exception list, {% data variables.location.product_location %} will return to normal operation. -还可以使用命令行实用程序配置 IP 异常列表。 有关详细信息,请参阅“[命令行实用程序](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-maintenance)”和“[访问管理 shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)”。 +You can also use a command-line utility to configure the IP exception list. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-maintenance)" and "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} -1. 在 {% data variables.enterprise.management_console %} 顶部,单击“维护”,并确认已启用维护模式。 - ![“维护”选项卡](/assets/images/enterprise/management-console/maintenance-tab.png) -1. 选择“启用 IP 例外列表”。 - ![“启用 IP 例外列表”复选框](/assets/images/enterprise/maintenance/enable-ip-exception-list.png) -1. 在文本框中,键入应允许访问 {% data variables.product.product_location %} 的以空格分隔的 IP 地址或 CIDR 块的有效列表。 - ![IP 地址的已完成字段](/assets/images/enterprise/maintenance/ip-exception-list-ip-addresses.png) -1. 单击“ **保存**”。 -![保存 IP 例外列表后](/assets/images/enterprise/maintenance/ip-exception-save.png) +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +1. At the top of the {% data variables.enterprise.management_console %}, click **Maintenance**, and confirm maintenance mode is already enabled. + ![Maintenance tab](/assets/images/enterprise/management-console/maintenance-tab.png) +1. Select **Enable IP exception list**. + ![Checkbox for enabling ip exception list](/assets/images/enterprise/maintenance/enable-ip-exception-list.png) +1. In the text box, type a valid list of space-separated IP addresses or CIDR blocks that should be allowed to access {% data variables.location.product_location %}. + ![completed field for IP addresses](/assets/images/enterprise/maintenance/ip-exception-list-ip-addresses.png) +1. Click **Save**. +![after IP excetpion list has saved](/assets/images/enterprise/maintenance/ip-exception-save.png) {% endif %} -## 通过 {% data variables.product.prodname_enterprise_api %} 排定维护模式 +## Scheduling maintenance mode with the {% data variables.product.prodname_enterprise_api %} -您可以通过 {% data variables.product.prodname_enterprise_api %} 排定在其他时间或日期进行维护。 有关详细信息,请参阅“[管理控制台](/enterprise/user/rest/reference/enterprise-admin#enable-or-disable-maintenance-mode)”。 +You can schedule maintenance for different times or dates with the {% data variables.product.prodname_enterprise_api %}. For more information, see "[Management Console](/enterprise/user/rest/reference/enterprise-admin#enable-or-disable-maintenance-mode)." -## 为集群中的所有节点启用或禁用维护模式 +## Enabling or disabling maintenance mode for all nodes in a cluster -使用 `ghe-cluster-maintenance` 实用工具,可以为群集中的每个节点设置或取消设置维护模式。 +With the `ghe-cluster-maintenance` utility, you can set or unset maintenance mode for every node in a cluster. ```shell $ ghe-cluster-maintenance -h diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md index 26078be865..e0f3bb8c8f 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md @@ -1,6 +1,6 @@ --- -title: 启用私有模式 -intro: '在私有模式下,{% data variables.product.prodname_ghe_server %} 要求每个用户必须登录才能访问安装。' +title: Enabling private mode +intro: 'In private mode, {% data variables.product.prodname_ghe_server %} requires every user to sign in to access the installation.' redirect_from: - /enterprise/admin/articles/private-mode - /enterprise/admin/guides/installation/security @@ -20,19 +20,16 @@ topics: - Networking - Privacy - Security -ms.openlocfilehash: 99488886b1da5b07c2ddb5d7054c10957f6c573b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146332782' --- -如果 {% data variables.product.product_location %} 可通过 Internet 公开访问,就必须启用私密模式。 在私密模式下,用户不能通过 `git://` 匿名克隆存储库。 如果还启用了内置身份验证,管理员必须邀请新用户在实例上创建帐户。 有关详细信息,请参阅“[配置内置身份验证](/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication)”。 +You must enable private mode if {% data variables.location.product_location %} is publicly accessible over the Internet. In private mode, users cannot anonymously clone repositories over `git://`. If built-in authentication is also enabled, an administrator must invite new users to create an account on the instance. For more information, see "[Configuring built-in authentication](/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication)." {% data reusables.enterprise_installation.image-urls-viewable-warning %} -启用私密模式后,可以允许未验证的 Git 操作(以及对 {% data variables.product.product_location %} 具有网络访问权限的任何人)读取已启用匿名 Git 读取权限的实例上的公共存储库代码。 有关详细信息,请参阅“[允许管理员启用对公共存储库的匿名 Git 读取访问](/enterprise/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)”。 +With private mode enabled, you can allow unauthenticated Git operations (and anyone with network access to {% data variables.location.product_location %}) to read a public repository's code on your instance with anonymous Git read access enabled. For more information, see "[Allowing admins to enable anonymous Git read access to public repositories](/enterprise/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)." -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} -4. 选择“私密模式”。 - ![启用私密模式的复选框](/assets/images/enterprise/management-console/private-mode-checkbox.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +4. Select **Private mode**. + ![Checkbox for enabling private mode](/assets/images/enterprise/management-console/private-mode-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md index 31635a5b83..5b582d0630 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md @@ -1,6 +1,6 @@ --- -title: 初始化 GitHub AE -intro: '要让您的企业准备好使用,您可以完成 {% data variables.product.product_name %} 的初始配置。' +title: Initializing GitHub AE +intro: 'To get your enterprise ready to use, you can complete the initial configuration of {% data variables.product.product_name %}.' versions: ghae: '*' type: how_to @@ -9,128 +9,123 @@ topics: redirect_from: - /admin/configuration/initializing-github-ae - /enterprise-server@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae -ms.openlocfilehash: f7d53e727fc7cbc58743a62d9c9d755cb799dbef -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147400352' --- -## 关于初始化 +## About initialization -在初始化企业之前,必须购买 {% data variables.product.product_name %}。 更多信息请联系 {% data variables.contact.contact_enterprise_sales %}。 +Before you can initialize your enterprise, you must purchase {% data variables.product.product_name %}. For more information, contact {% data variables.contact.contact_enterprise_sales %}. -{% data reusables.github-ae.initialize-enterprise %} 确保您提供的信息与 IdP 中的预期企业所有者信息相匹配。 有关企业所有者的详细信息,请参阅“[企业中的角色](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)”。 +{% data reusables.github-ae.initialize-enterprise %} Make sure the information you provide matches the intended enterprise owner's information in the IdP. For more information about enterprise owners, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)." {% note %} -**注释**: +**Notes**: -- 如果 {% data variables.product.prodname_ghe_managed %} 的初始密码在您完成初始化之前过期,您可以随时从邀请电子邮件请求重置密码。 +- If the initial password for {% data variables.product.prodname_ghe_managed %} expires before you finish initialization, you can request a password reset at any time from your invitation email. -- 将 {% data variables.product.prodname_ghe_managed %} 的初始用户名和密码安全地存储在密码管理器中。 {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} +- Store the initial username and password for {% data variables.product.prodname_ghe_managed %} securely in a password manager. {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} {% endnote %} -在初始化期间,企业所有者将命名企业、配置 SAML SSO、为企业中的所有组织创建策略以及为用户配置支持联系人。 +During initialization, the enterprise owner will name your enterprise, configure SAML SSO, create policies for all organizations in your enterprise, and configure a support contact for your users. -## 先决条件 +## Prerequisites -要开始初始化,您将收到来自 {% data variables.product.company_short %} 的邀请电子邮件。 在配置 {% data variables.product.prodname_ghe_managed %} 之前,要查看以下先决条件。 +To begin initialization, you will receive an invitation email from {% data variables.product.company_short %}. Before you configure {% data variables.product.prodname_ghe_managed %}, review the following prerequisites. -1. 要初始化 {% data variables.product.product_location %},您必须具有 SAML 身份提供程序 (Idp)。 {% data reusables.saml.ae-uses-saml-sso %} 在初始化过程中将您的 IdP 连接到企业,您应该具有您的 IdP 实体 ID (SSO) URL、发行者 ID URL 和公共签名证书(Base64 编码)。 有关详细信息,请参阅“[关于企业标识和访问管理](/admin/authentication/about-identity-and-access-management-for-your-enterprise)”。 +1. To initialize {% data variables.location.product_location %}, you must have a SAML identity provider (IdP). {% data reusables.saml.ae-uses-saml-sso %} To connect your IdP to your enterprise during initialization, you should have your IdP's Entity ID (SSO) URL, Issuer ID URL, and public signing certificate (Base64-encoded). For more information, see "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)." {% note %} - **注意**:{% data reusables.saml.create-a-machine-user %} + **Note**: {% data reusables.saml.create-a-machine-user %} {% endnote %} 2. {% data reusables.saml.assert-the-administrator-attribute %} -## 登录并命名企业 +## Signing in and naming your enterprise -1. 按照欢迎电子邮件中的说明联系您的企业。 -2. 在“更改密码”下键入你的凭据,然后单击“更改密码”。 -3. 在“你希望将企业帐户命名为什么?”下,键入企业的名称,然后单击“保存并继续”。 - ![“保存并继续”按钮,用于命名企业](/assets/images/enterprise/configuration/ae-enterprise-configuration.png) +1. Follow the instructions in your welcome email to reach your enterprise. +2. Type your credentials under "Change password", then click **Change password**. +3. Under "What would you like your enterprise account to be named?", type the enterprise's name, then click **Save and continue**. + !["Save and continue" button for naming an enterprise](/assets/images/enterprise/configuration/ae-enterprise-configuration.png) -## 将 IdP 连接到企业 +## Connecting your IdP to your enterprise -要配置 {% data variables.product.product_name %} 的身份验证,您必须提供包含 SAML IdP 详细信息的 {% data variables.product.product_name %}。 {% data variables.product.company_short %} 建议使用 Azure AD 作为您的 IdP。 有关详细信息,请参阅“[使用标识提供者配置身份验证和预配](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)”。 +To configure authentication for {% data variables.product.product_name %}, you must provide {% data variables.product.product_name %} with the details for your SAML IdP. {% data variables.product.company_short %} recommends using Azure AD as your IdP. For more information, see "[Configuring authentication and provisioning with your identity provider](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)." -1. 在“设置标识提供者”右侧,单击“配置”。 - ![IdP 配置的“配置”按钮](/assets/images/enterprise/configuration/ae-idp-configure.png) -1. 在“Sign on URL(登录 URL)”下,复制并粘贴 SAML IdP 的 URL。 - ![SAML IdP 登录 URL 的文本字段](/assets/images/enterprise/configuration/ae-idp-sign-on-url.png) -1. 在“Issuer(发行机构)”下,复制并粘贴 SAML IdP 的发行机构 URL。 - ![SAML IdP 的发行机构 URL 的文本字段](/assets/images/enterprise/configuration/ae-idp-issuer-url.png) -1. 在“Public certificate(公共证书)”下,复制并粘贴 SAML IdP 的公共证书。 - ![SAML IdP 公共证书的文本字段](/assets/images/enterprise/configuration/ae-idp-public-certificate.png) -1. 单击“测试 SAML 配置”,确保你输入的信息是正确的。 - ![“测试 SAML 配置”按钮](/assets/images/enterprise/configuration/ae-test-saml-configuration.png) -1. 单击“ **保存**”。 - ![用于 IdP 配置的“保存”按钮](/assets/images/enterprise/configuration/ae-save.png) +1. To the right of "Set up your identity provider", click **Configure**. + !["Configure" button for IdP configuration](/assets/images/enterprise/configuration/ae-idp-configure.png) +1. Under "Sign on URL", copy and paste the URL for your SAML IdP. + ![Text field for SAML IdP's sign-on URL](/assets/images/enterprise/configuration/ae-idp-sign-on-url.png) +1. Under "Issuer", copy and paste the issuer URL for your SAML IdP. + ![Text field for SAML IdP's issuer URL](/assets/images/enterprise/configuration/ae-idp-issuer-url.png) +1. Under "Public certificate", copy and paste the public certificate for your SAML IdP. + ![Text field for SAML IdP's public certificate](/assets/images/enterprise/configuration/ae-idp-public-certificate.png) +1. Click **Test SAML configuration** to ensure that the information you've entered is correct. + !["Test SAML configuration" button](/assets/images/enterprise/configuration/ae-test-saml-configuration.png) +1. Click **Save**. + !["Save" button for IdP configuration](/assets/images/enterprise/configuration/ae-save.png) -## 设置企业策略 +## Setting your enterprise policies -配置策略将为企业的仓库和组织管理设置限制。 这些可以在初始化过程后重新配置。 +Configuring policies will set limitations for repository and organization management for your enterprise. These can be reconfigured after the initialization process. -1. 在“设置企业策略”右侧,单击“配置”。 - ![用于策略配置的“配置”按钮](/assets/images/enterprise/configuration/ae-policies-configure.png) -2. 在“Default Repository Permissions(默认仓库权限)”下,使用下拉菜单,并单击企业中仓库的默认权限级别。 如果某人可通过多种途径访问组织(个人访问、通过团队访问或作为组织成员访问),则最高的项目板权限级别将覆盖任何较低的权限级别。 (可选)若要允许企业内的组织设置其默认仓库权限,请单击“无策略” - ![默认仓库权限选项的下拉菜单](/assets/images/enterprise/configuration/ae-repository-permissions-menu.png) -3. 在“Repository creation(仓库创建)”下,选择是否允许会员创建仓库. (可选)若要允许企业内的组织设置权限,请单击“无策略”。 - ![用于企业策略配置的“成员可创建存储库”按钮](/assets/images/enterprise/configuration/ae-repository-creation-permissions.png) -4. 在“Repository forking(仓库复刻)”下,选择是否允许私有和内部仓库复刻。 (可选)若要允许企业内的组织设置权限,请单击“无策略” - ![存储库分支创建权限选项的下拉菜单](/assets/images/enterprise/configuration/ae-repository-forking-menu.png) -5. 在“Repository invitations(仓库邀请)”下,选择成员或组织所有者是否可以邀请合作者进入仓库。 (可选)若要允许企业内的组织设置权限,请单击“无策略” - ![存储库邀请权限选项的下拉菜单](/assets/images/enterprise/configuration/ae-repository-invitations-menu.png) -6. 在“Default repository visibility(默认仓库可见性)”下,使用下拉菜单并单击新仓库的默认可见性设置。 - ![默认存储库可见性选项的下拉菜单](/assets/images/enterprise/configuration/ae-repository-visibility-menu.png) -7. 在“Users can create organizations(用户可以创建组织)”下,使用下拉菜单来启用或禁用企业成员创建组织。 - ![组织创建权限选项的下拉菜单](/assets/images/enterprise/configuration/ae-organization-creation-permissions-menu.png) -8. 在“Force pushes(强制推送)”下,使用下拉菜单选择是允许还是阻止强制推送。 - ![强制推送配置选项的下拉菜单](/assets/images/enterprise/configuration/ae-force-pushes-configuration-menu.png) -9. 在“Git SSH access(Git SSH 访问)”下,使用下拉菜单并选择是否为企业中所有仓库启用 Git SSH 访问。 - ![Git SSH 访问选项的下拉菜单](/assets/images/enterprise/configuration/ae-git-ssh-access-menu.png) -10. 单击“保存” - ![用于企业策略配置的“保存”按钮](/assets/images/enterprise/configuration/ae-save.png) -11. (可选)要重置所有选项,请单击“Reset to default policies(重置为默认策略)”。 - ![重置所有默认策略的链接](/assets/images/enterprise/configuration/ae-reset-default-options.png) +1. To the right of "Set your enterprise policies", click **Configure**. + !["Configure" button for policies configuration](/assets/images/enterprise/configuration/ae-policies-configure.png) +2. Under "Default Repository Permissions", use the drop-down menu and click a default permissions level for repositories in your enterprise. If a person has multiple avenues of access to an organization, either individually, through a team, or as an organization member, the highest permission level overrides any lower permission levels. Optionally, to allow organizations within your enterprise to set their default repository permissions, click **No policy** + ![Drop-down menu for default repository permissions options](/assets/images/enterprise/configuration/ae-repository-permissions-menu.png) +3. Under "Repository creation", choose whether you want to allow members to create repositories. Optionally, to allow organizations within your enterprise to set permissions, click **No policy**. + !["Members can create repositories" button for enterprise policies configuration](/assets/images/enterprise/configuration/ae-repository-creation-permissions.png) +4. Under "Repository forking", choose whether to allow forking of private and internal repositories. Optionally, to allow organizations within your enterprise to set permissions, click **No policy** + ![Drop-down menu for repository forking permissions options](/assets/images/enterprise/configuration/ae-repository-forking-menu.png) +5. Under "Repository invitations", choose whether members or organization owners can invite collaborators to repositories. Optionally, to allow organizations within your enterprise to set permissions, click **No policy** + ![Drop-down menu for repository invitation permissions options](/assets/images/enterprise/configuration/ae-repository-invitations-menu.png) +6. Under "Default repository visibility", use the drop-down menu and click the default visibility setting for new repositories. + ![Drop-down menu for default repository visibility options](/assets/images/enterprise/configuration/ae-repository-visibility-menu.png) +7. Under "Users can create organizations", use the drop-down menu to enable or disable organization creation access for members of the enterprise. + ![Drop-down menu for organization creation permissions options](/assets/images/enterprise/configuration/ae-organization-creation-permissions-menu.png) +8. Under "Force pushes", use the drop-down menu and choose whether to allow or block force pushes. + ![Drop-down menu for force pushes configuration options](/assets/images/enterprise/configuration/ae-force-pushes-configuration-menu.png) +9. Under "Git SSH access", use the drop-down menu and choose whether to enable Git SSH access for all repositories in the enterprise. + ![Drop-down menu for Git SSH access options](/assets/images/enterprise/configuration/ae-git-ssh-access-menu.png) +10. Click **Save** + !["Save" button for enterprise policies configuration](/assets/images/enterprise/configuration/ae-save.png) +11. Optionally, to reset all selections, click "Reset to default policies". + ![Link to reset all default policies](/assets/images/enterprise/configuration/ae-reset-default-options.png) -## 设置内部支持联系人 +## Setting your internal support contact -您可以配置用户联系内部支持团队的方法。 这可以在初始化过程后重新配置。 +You can configure the method your users will use to contact your internal support team. This can be reconfigured after the initialization process. -1. 在“内部支持联系人”右侧,单击“配置”。 - ![用于内部支持联系人配置的“配置”按钮](/assets/images/enterprise/configuration/ae-support-configure.png) -2. 在“Internal support contact(内部支持联系人)”下,选择您企业的用户通过网址或电子邮件地址联系支持的方法。 然后,键入支持联系信息。 - ![内部支持联系人 URL 的文本字段](/assets/images/enterprise/configuration/ae-support-link-url.png) -3. 单击“ **保存**”。 - ![用于企业支持联系人配置的“保存”按钮](/assets/images/enterprise/configuration/ae-save.png) +1. To the right of "Internal support contact", click **Configure**. + !["Configure" button for internal support contact configuration](/assets/images/enterprise/configuration/ae-support-configure.png) +2. Under "Internal support contact", select the method for users of your enterprise to contact support, through a URL or an e-mail address. Then, type the support contact information. + ![Text field for internal support contact URL](/assets/images/enterprise/configuration/ae-support-link-url.png) +3. Click **Save**. + !["Save" button for enterprise support contact configuration](/assets/images/enterprise/configuration/ae-save.png) -## 设置电子邮件设置 +## Setting your email settings -一旦初始化,您便可在初始化过程后重新配置任何设置。 有关详细信息,请参阅“[配置邮件通知](/admin/configuration/configuring-email-for-notifications)”。 +Once this is initialized, you can reconfigure any settings after the initialization process. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-email-for-notifications)." -1. 在“配置电子邮件设置”右侧,单击“配置”。 - ![用于电子邮件设置配置的“配置”按钮](/assets/images/enterprise/configuration/ae-email-configure.png) -2. 选择“启用电子邮件”。 这将启用出站和入站电子邮件,但是,为使入站电子邮件运行,您还需要配置 DNS 设置。 有关详细信息,请参阅“[配置 DNS 和防火墙设置,以允许传入电子邮件](/admin/configuration/configuring-email-for-notifications#configuring-dns-and-firewall-settings-to-allow-incoming-emails)”。 - ![用于电子邮件设置配置的“启用”复选框](/assets/images/enterprise/configuration/ae-enable-email-configure.png) -3. 完成电子邮件服务器设置: - - 在“服务器地址”字段中,输入 SMTP 服务器的地址。 - - 在“端口”字段中,输入 SMTP 服务器用于发送电子邮件的端口。 - - 在“域”字段中,输入 SMTP 服务器将随 HELO 响应(如有)发送的域名。 - - 在“身份验证”下拉菜单中,选择 SMTP 服务器所使用的加密类型。 - - 在“无回复电子邮件地址”字段中,输入要在所有通知电子邮件的“发件人”和“收件人”字段中使用的电子邮件地址。 +1. To the right of "Configure email settings", click **Configure**. + !["Configure" button for email settings configuration](/assets/images/enterprise/configuration/ae-email-configure.png) +2. Select **Enable email**. This will enable both outbound and inbound email, however, for inbound email to work you will also need to configure your DNS settings. For more information, see "[Configuring DNS and firewall + settings to allow incoming emails](/admin/configuration/configuring-email-for-notifications#configuring-dns-and-firewall-settings-to-allow-incoming-emails)." + !["Enable" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-enable-email-configure.png) +3. Complete your email server settings: + - In the **Server address** field, type the address of your SMTP server. + - In the **Port** field, type the port that your SMTP server uses to send email. + - In the **Domain** field, type the domain name that your SMTP server will send with a HELO response, if any. + - In the **Authentication** dropdown, choose the type of encryption used by your SMTP server. + - In the **No-reply email address** field, type the email address to use in the From and To fields for all notification emails. -4. 如果想放弃发送到无回复电子邮件地址的所有传入电子邮件,请选中“放弃发送到无回复电子邮件地址的电子邮件”。 - ![用于电子邮件设置配置的“放弃”复选框](/assets/images/enterprise/configuration/ae-discard-email.png) -5. 单击“测试电子邮件设置”。 - ![用于邮件设置配置的“测试邮件设置”按钮](/assets/images/enterprise/configuration/ae-test-email.png) -6. 在“发送测试电子邮件到”下,请输入测试电子邮件要发送到的电子邮件地址,然后单击“发送测试电子邮件”。 - ![用于邮件设置配置的“发送测试电子邮件”按钮](/assets/images/enterprise/configuration/ae-send-test-email.png) -7. 单击“ **保存**”。 - ![用于企业支持联系人配置的“保存”按钮](/assets/images/enterprise/configuration/ae-save.png) +4. If you want to discard all incoming emails that are addressed to the no-reply email address, select **Discard email addressed to the no-reply email address**. + !["Discard" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-discard-email.png) +5. Click **Test email settings**. + !["Test email settings" button for email settings configuration](/assets/images/enterprise/configuration/ae-test-email.png) +6. Under "Send test email to," type the email address where you want to send a test email, then click **Send test email**. + !["Send test email" button for email settings configuration](/assets/images/enterprise/configuration/ae-send-test-email.png) +7. Click **Save**. + !["Save" button for enterprise support contact configuration](/assets/images/enterprise/configuration/ae-save.png) diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md index a43eb8daa2..d288949214 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: 管理企业的 GitHub Mobile -intro: '可以决定用户是否可以使用 {% data variables.product.prodname_mobile %} 连接到 {% data variables.product.product_location %}。' +title: Managing GitHub Mobile for your enterprise +intro: 'You can decide whether people can use {% data variables.product.prodname_mobile %} to connect to {% data variables.location.product_location %}.' permissions: 'Enterprise owners can manage {% data variables.product.prodname_mobile %} for a {% data variables.product.product_name %} instance.' versions: ghes: '*' @@ -12,29 +12,29 @@ redirect_from: - /admin/configuration/configuring-your-enterprise/managing-github-for-mobile-for-your-enterprise - /admin/configuration/managing-github-for-mobile-for-your-enterprise shortTitle: Manage GitHub Mobile -ms.openlocfilehash: f46673c16611a7f1ced6d0476c6ad3d79807f6d9 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147062264' --- -## 关于 {% data variables.product.prodname_mobile %} -在身份验证成功后,借助 {% data variables.product.prodname_mobile %} 可从移动设备会审、协作和管理 {% data variables.product.product_location %} 上的工作。 {% data reusables.mobile.about-mobile %}有关详细信息,请参阅“[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)”。 +## About {% data variables.product.prodname_mobile %} -可允许或禁止用户使用 {% data variables.product.prodname_mobile %} 向 {% data variables.product.product_location %} 进行身份验证并访问实例的数据。 默认情况下,{% data variables.product.prodname_mobile %} {% ifversion ghes > 3.3 %}为使用 {% data variables.product.product_location %} 的用户启用。{% else %}不为使用 {% data variables.product.product_location %} 的用户启用。 若要允许使用 {% data variables.product.prodname_mobile %} 连接到实例,必须为实例启用该功能。{% endif %} +{% data variables.product.prodname_mobile %} allows people to triage, collaborate, and manage work on {% data variables.location.product_location %} from a mobile device after successful authentication. {% data reusables.mobile.about-mobile %} For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)." -{% ifversion ghes < 3.6 %} {% note %} +You can allow or disallow people from using {% data variables.product.prodname_mobile %} to authenticate to {% data variables.location.product_location %} and access your instance's data. By default, {% data variables.product.prodname_mobile %} is{% ifversion ghes > 3.3 %} enabled for people who use {% data variables.location.product_location %}.{% else %} not enabled for people who use {% data variables.location.product_location %}. To allow connection to your instance with {% data variables.product.prodname_mobile %}, you must enable the feature for your instance.{% endif %} -注意:如果升级到 {% data variables.product.prodname_ghe_server %} 3.4.0 或更高版本,并且以前未禁用或启用 {% data variables.product.prodname_mobile %},则默认情况下将启用 {% data variables.product.prodname_mobile %}。 如果以前为实例禁用或启用了 {% data variables.product.prodname_mobile %},则升级后将保留首选项。 有关升级实例的详细信息,请参阅“[升级 {% data variables.product.product_name %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)”。 +{% ifversion ghes < 3.6 %} +{% note %} -{% endnote %} {% endif %} +**Note:** If you upgrade to {% data variables.product.prodname_ghe_server %} 3.4.0 or later and have not previously disabled or enabled {% data variables.product.prodname_mobile %}, {% data variables.product.prodname_mobile %} will be enabled by default. If you previously disabled or enabled {% data variables.product.prodname_mobile %} for your instance, your preference will be preserved upon upgrade. For more information about upgrading your instance, see "[Upgrading {% data variables.product.product_name %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." -## 启用或禁用 {% data variables.product.prodname_mobile %} +{% endnote %} +{% endif %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.type-management-console-password %} -1. 在左边栏中,单击“移动”。 - ![{% data variables.product.prodname_ghe_server %} 管理控制台左边栏中的“移动”](/assets/images/enterprise/management-console/click-mobile.png) -1. 在“GitHub Mobile”下,选择或取消选择“启用 GitHub Mobile 应用”。 - ![{% data variables.product.prodname_ghe_server %} 管理控制台中的“启用 GitHub Mobile 应用”复选框](/assets/images/enterprise/management-console/select-enable-github-mobile-apps.png) {% data reusables.enterprise_management_console.save-settings %} +## Enabling or disabling {% data variables.product.prodname_mobile %} + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.type-management-console-password %} +1. In the left sidebar, click **Mobile**. + !["Mobile" in the left sidebar for the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/click-mobile.png) +1. Under "GitHub Mobile", select or deselect **Enable GitHub Mobile Apps**. + ![Checkbox for "Enable GitHub Mobile Apps" in the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/select-enable-github-mobile-apps.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md index ea742e0fc5..7d3c7e3665 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md @@ -51,7 +51,7 @@ For more information on audit logging in general, see "[About the audit log for ## Reports -If you need to get information on the users, organizations, and repositories in {% data variables.product.product_location %}, you would ordinarily fetch JSON data through the [GitHub API](/rest). Unfortunately, the API may not provide all of the data that you want and it requires a bit of technical expertise to use. The site admin dashboard offers a **Reports** section as an alternative, making it easy for you to download CSV reports with most of the information that you are likely to need for users, organizations, and repositories. +If you need to get information on the users, organizations, and repositories in {% data variables.location.product_location %}, you would ordinarily fetch JSON data through the [GitHub API](/rest). Unfortunately, the API may not provide all of the data that you want and it requires a bit of technical expertise to use. The site admin dashboard offers a **Reports** section as an alternative, making it easy for you to download CSV reports with most of the information that you are likely to need for users, organizations, and repositories. Specifically, you can download CSV reports that list @@ -62,7 +62,7 @@ Specifically, you can download CSV reports that list - all organizations - all repositories -You can also access these reports programmatically via standard HTTP authentication with a site admin account. You must use a personal access token with the `site_admin` scope. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +You can also access these reports programmatically via standard HTTP authentication with a site admin account. You must use a {% data variables.product.pat_v1 %} with the `site_admin` scope. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." For example, here is how you would download the "all users" report using cURL: @@ -164,7 +164,7 @@ You can create a new index, or you can click on an existing index in the list to - Start a new index repair job. - Enable or disable index repair jobs. -A progress bar shows the current status of a repair job across background workers. The bar is the percentage difference of the repair offset with the highest record ID in the database. You can ignore the value shown in the progress bar after a repair job has completed. The progress bar shows the difference between the repair offset and the highest record ID in the database, and will decrease as more repositories are added to {% data variables.product.product_location %} even though those repositories are actually indexed. +A progress bar shows the current status of a repair job across background workers. The bar is the percentage difference of the repair offset with the highest record ID in the database. You can ignore the value shown in the progress bar after a repair job has completed. The progress bar shows the difference between the repair offset and the highest record ID in the database, and will decrease as more repositories are added to {% data variables.location.product_location %} even though those repositories are actually indexed. To minimize the effects on I/O performance and reduce the chances of operations timing out, run the repair job during off-peak hours. As the job reconciles the search index with database and Git repository data, one CPU will be used. Monitor your system's load averages and CPU usage with a utility like `top`. If you don't notice any significant increase in resource consumption, it should also be safe to run an index repair job during peak hours. @@ -177,7 +177,7 @@ This allows you to enable or disable both search and index operations on source {% endif %} ## Reserved logins -Certain words are reserved for internal use in {% data variables.product.product_location %}, which means that these words cannot be used as usernames. +Certain words are reserved for internal use in {% data variables.location.product_location %}, which means that these words cannot be used as usernames. For example, the following words are reserved, among others: @@ -216,7 +216,7 @@ Refer to this section of the site admin dashboard to manage organizations, peopl ## Repositories -This is a list of the repositories on {% data variables.product.product_location %}. You can click on a repository name and access functions for administering the repository. +This is a list of the repositories on {% data variables.location.product_location %}. You can click on a repository name and access functions for administering the repository. - [Blocking force pushes to a repository](/enterprise/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) - [Configuring {% data variables.large_files.product_name_long %}](/enterprise/admin/guides/installation/configuring-git-large-file-storage/#configuring-git-large-file-storage-for-an-individual-repository) @@ -224,21 +224,21 @@ This is a list of the repositories on {% data variables.product.product_location ## All users -Here you can see all of the users on {% data variables.product.product_location %}, and [initiate an SSH key audit](/enterprise/admin/guides/user-management/auditing-ssh-keys). +Here you can see all of the users on {% data variables.location.product_location %}, and [initiate an SSH key audit](/enterprise/admin/guides/user-management/auditing-ssh-keys). ## Site admins -Here you can see all of the administrators on {% data variables.product.product_location %}, and [initiate an SSH key audit](/enterprise/admin/guides/user-management/auditing-ssh-keys). +Here you can see all of the administrators on {% data variables.location.product_location %}, and [initiate an SSH key audit](/enterprise/admin/guides/user-management/auditing-ssh-keys). ## Dormant users {% ifversion ghes %} -Here you can see and [suspend](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users) all of the inactive users on {% data variables.product.product_location %}. A user account is considered to be inactive ("dormant") when it: +Here you can see and [suspend](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users) all of the inactive users on {% data variables.location.product_location %}. A user account is considered to be inactive ("dormant") when it: {% endif %} {% ifversion ghae %} -Here you can see and suspend all of the inactive users on {% data variables.product.product_location %}. A user account is considered to be inactive ("dormant") when it: +Here you can see and suspend all of the inactive users on {% data variables.location.product_location %}. A user account is considered to be inactive ("dormant") when it: {% endif %} -- Has existed for longer than the dormancy threshold that's set for {% data variables.product.product_location %}. +- Has existed for longer than the dormancy threshold that's set for {% data variables.location.product_location %}. - Has not generated any activity within that time period. - Is not a site administrator. @@ -246,4 +246,4 @@ Here you can see and suspend all of the inactive users on {% data variables.prod ## Suspended users -Here you can see all of the users who have been suspended on {% data variables.product.product_location %}, and [initiate an SSH key audit](/enterprise/admin/guides/user-management/auditing-ssh-keys). +Here you can see all of the users who have been suspended on {% data variables.location.product_location %}, and [initiate an SSH key audit](/enterprise/admin/guides/user-management/auditing-ssh-keys). diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md index 354a424e0b..eca1544cea 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md +++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md @@ -1,6 +1,6 @@ --- -title: 排查 TLS 错误 -intro: 如果你的设备遇到 TLS 问题,可以采取相应措施加以解决。 +title: Troubleshooting TLS errors +intro: 'If you run into TLS issues with your appliance, you can take actions to resolve them.' redirect_from: - /enterprise/admin/articles/troubleshooting-ssl-errors - /enterprise/admin/categories/dns-ssl-and-subdomain-configuration @@ -19,74 +19,68 @@ topics: - Security - Troubleshooting shortTitle: Troubleshoot TLS errors -ms.openlocfilehash: 855737f89f0380333b1f37c26d512c889f2ee786 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147881249' --- -## 将密码从密钥文件中移除 +## Removing the passphrase from your key file -如果您的 Linux 机器上安装了 OpenSSL,可以移除密码。 +If you have a Linux machine with OpenSSL installed, you can remove your passphrase. -1. 重命名原始密钥文件。 +1. Rename your original key file. ```shell $ mv yourdomain.key yourdomain.key.orig ``` -2. 生成不含密码的新密钥。 +2. Generate a new key without a passphrase. ```shell $ openssl rsa -in yourdomain.key.orig -out yourdomain.key ``` -运行此命令时系统会提示您输入密钥的密码。 +You'll be prompted for the key's passphrase when you run this command. -有关 OpenSSL 的详细信息,请参阅 [OpenSSL 文档](https://www.openssl.org/docs/)。 +For more information about OpenSSL, see [OpenSSL's documentation](https://www.openssl.org/docs/). -## 将 TLS 证书或密钥转换为 PEM 格式 +## Converting your TLS certificate or key into PEM format -如果安装了 OpenSSL,可以使用 `openssl` 命令将密钥转换为 PEM 格式。 例如,您可以将密钥从 DER 格式转换为 PEM 格式。 +If you have OpenSSL installed, you can convert your key into PEM format by using the `openssl` command. For example, you can convert a key from DER format into PEM format. ```shell $ openssl rsa -in yourdomain.der -inform DER -out yourdomain.key -outform PEM ``` -否则,可以使用 SSL Converter 工具将证书转换为 PEM 格式。 有关详细信息,请参阅 [SSL 转换器工具的文档](https://www.sslshopper.com/ssl-converter.html)。 +Otherwise, you can use the SSL Converter tool to convert your certificate into the PEM format. For more information, see the [SSL Converter tool's documentation](https://www.sslshopper.com/ssl-converter.html). -## 上传密钥后安装无响应 +## Unresponsive installation after uploading a key -如果上传 TLS 密钥后 {% data variables.product.product_location %}无响应,请[联系 {% data variables.product.prodname_enterprise %} 支持部门](https://enterprise.github.com/support),并提供具体详细信息,包括 TLS 证书的副本。 请确保未包含私钥。 +If {% data variables.location.product_location %} is unresponsive after uploading an TLS key, please [contact {% data variables.product.prodname_enterprise %} Support](https://enterprise.github.com/support) with specific details, including a copy of your TLS certificate. Ensure that your private key **is not** included. -## 证书有效性错误 +## Certificate validity errors -如果 Web 浏览器和命令行 Git 等客户端无法验证 TLS 证书的有效性,则会显示错误消息。 这种情况通常发生在自签名证书以及由不被客户端承认的中间根证书颁发的“链式根”证书上。 +Clients such as web browsers and command-line Git will display an error message if they cannot verify the validity of an TLS certificate. This often occurs with self-signed certificates as well as "chained root" certificates issued from an intermediate root certificate that is not recognized by the client. -如果您要使用由证书颁发机构 (CA) 签名的证书,那么您上传到 {% data variables.product.prodname_ghe_server %} 的证书文件必须包含具有该 CA 的根证书的证书链。 要创建此类文件,请将整个证书链(“或证书包”)连接到证书末端,确保包含主机名的主要证书在前。 在大多数系统中,您可以使用与下列命令相似的命令来执行此操作: +If you are using a certificate signed by a certificate authority (CA), the certificate file that you upload to {% data variables.product.prodname_ghe_server %} must include a certificate chain with that CA's root certificate. To create such a file, concatenate your entire certificate chain (or "certificate bundle") onto the end of your certificate, ensuring that the principal certificate with your hostname comes first. On most systems you can do this with a command similar to: ```shell $ cat yourdomain.com.crt bundle-certificates.crt > yourdomain.combined.crt ``` -可以从证书颁发机构或 TLS 供应商处下载证书捆绑包(例如 `bundle-certificates.crt`)。 +You should be able to download a certificate bundle (for example, `bundle-certificates.crt`) from your certificate authority or TLS vendor. -## 安装自签名或不受信任的证书颁发机构 (CA) 根证书 +## Installing self-signed or untrusted certificate authority (CA) root certificates -如果您的 {% data variables.product.prodname_ghe_server %} 设备与网络中使用自签名或不受信证书的其他机器进行交互,您需要将签名 CA 的根证书导入到系统范围的证书库中,以通过 HTTPS 访问这些系统。 +If your {% data variables.product.prodname_ghe_server %} appliance interacts with other machines on your network that use a self-signed or untrusted certificate, you will need to import the signing CA's root certificate into the system-wide certificate store in order to access those systems over HTTPS. -1. 从本地证书颁发机构获取 CA 的根证书并确保其为 PEM 格式。 -2. 以“admin”用户身份在端口 122 上通过 SSH 将文件复制到您的 {% data variables.product.prodname_ghe_server %} 设备。 +1. Obtain the CA's root certificate from your local certificate authority and ensure it is in PEM format. +2. Copy the file to your {% data variables.product.prodname_ghe_server %} appliance over SSH as the "admin" user on port 122. ```shell $ scp -P 122 rootCA.crt admin@HOSTNAME:/home/admin ``` -3. 以“admin”用户身份在端口 122 上通过 SSH 连接到 {% data variables.product.prodname_ghe_server %} 管理 shell。 +3. Connect to the {% data variables.product.prodname_ghe_server %} administrative shell over SSH as the "admin" user on port 122. ```shell $ ssh -p 122 admin@HOSTNAME ``` -4. 将证书导入到系统范围的证书库中。 +4. Import the certificate into the system-wide certificate store. ```shell $ ghe-ssl-ca-certificate-install -c rootCA.crt ``` -## 更新 TLS 证书 +## Updating a TLS certificate -你可以生成新的自签名证书,或者使用 `ghe-ssl-certificate-setup` 命令行实用工具更新 {% data variables.product.product_location %}的现有 TLS 证书。 有关详细信息,请参阅“[命令行实用工具](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-ssl-ca-certificate-setup)”。 +You can generate a new self-signed certificate or update an existing TLS certificate for {% data variables.location.product_location %} with the `ghe-ssl-certificate-setup` command line utility. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-ssl-ca-certificate-setup)." diff --git a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md index e5ff198d4a..c2f149719e 100644 --- a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md +++ b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md @@ -1,6 +1,6 @@ --- -title: 访问监视仪表板 -intro: '{% data variables.product.prodname_ghe_server %} 中基于 Web 的监视仪表板可以显示关于 {% data variables.product.prodname_ghe_server %} 设备的历史数据,例如 CPU 和内存使用情况、应用程序和身份验证响应时间以及整体系统健康状况。' +title: Accessing the monitor dashboard +intro: '{% data variables.product.prodname_ghe_server %} includes a web-based monitoring dashboard that displays historical data about your {% data variables.product.prodname_ghe_server %} appliance, such as CPU and storage usage, application and authentication response times, and general system health.' redirect_from: - /enterprise/admin/installation/accessing-the-monitor-dashboard - /enterprise/admin/enterprise-management/accessing-the-monitor-dashboard @@ -15,33 +15,28 @@ topics: - Monitoring - Performance shortTitle: Access the monitor dashboard -ms.openlocfilehash: b529369813635a8cafe5f7c7ac6fc04af39001f5 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146332366' --- -## 访问监视仪表板 +## Accessing the monitor dashboard -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} -2. 在页面顶部,单击“监视”。 -![监视仪表板链接](/assets/images/enterprise/management-console/monitor-dash-link.png) +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +2. At the top of the page, click **Monitor**. +![The Monitor Dashboard link](/assets/images/enterprise/management-console/monitor-dash-link.png) -## 排查设备上的常见资源分配问题 +## Troubleshooting common resource allocation problems on your appliance {% note %} -注意:由于通过持续集成 (CI) 或构建服务器定期轮询 {% data variables.product.product_location %} 会引发拒绝服务攻击,从而导致问题的出现,因此,建议使用 Webhook 推送更新。 有关详细信息,请参阅“[关于 Webhook](/enterprise/user/articles/about-webhooks/)”。 +**Note**: Because regularly polling {% data variables.location.product_location %} with continuous integration (CI) or build servers can effectively cause a denial of service attack that results in problems, we recommend using webhooks to push updates. For more information, see "[About webhooks](/enterprise/user/articles/about-webhooks/)". {% endnote %} -使用监视仪表板实时了解设备资源健康状况并确定如何解决高利用率问题。 +Use the monitor dashboard to stay informed on your appliance's resource health and make decisions on how to fix high usage issues. -| 问题 | 可能原因 | 建议 | +| Problem | Possible cause(s) | Recommendations | | -------- | ----------------- | --------------- | -| 高 CPU 使用率 | 在同一主机上运行的其他服务或程序争用 VM | 如有可能,请将其他服务或程序重新配置为占用较少的 CPU 资源。 要增加 VM 的总 CPU 资源,请参阅“[增加 CPU 或内存资源](/enterprise/admin/guides/installation/increasing-cpu-or-memory-resources/)”。 | -| 内存使用率较高 | 在同一主机上运行的其他服务或程序争用 VM | 如有可能,请将其他服务或程序重新配置为占用较少内存。 要增加 VM 上可用的总内存,请参阅“[增加 CPU 或内存资源](/enterprise/admin/guides/installation/increasing-cpu-or-memory-resources/)”。 | -| 可用磁盘空间小 | 较大的二进制或日志文件占用磁盘空间 | 如有可能,请在独立服务器上托管较大的二进制文件,并压缩或存档日志文件。 如有必要,请按照“[增加存储容量](/enterprise/admin/guides/installation/increasing-storage-capacity/)”中的步骤操作,为你的平台增加 VM 的磁盘空间。 | -| 响应时间较正常时间长 | 通常是上述问题之一造成的 | 确定并解决根本问题。 如果响应时间仍较长,请联系 {% data variables.contact.contact_ent_support %}。 | -| 错误率提高 | 软件问题 | 联系 {% data variables.contact.contact_ent_support %} 并附上支持包。 有关详细信息,请参阅“[将数据提供给 {% data variables.product.prodname_enterprise %} 支持](/enterprise/{{ currentVersion}}/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-support-bundles)”。 | +| High CPU usage | VM contention from other services or programs running on the same host | If possible, reconfigure other services or programs to use fewer CPU resources. To increase total CPU resources for the VM, see "[Increasing CPU or memory resources](/enterprise/admin/guides/installation/increasing-cpu-or-memory-resources/)." | +| High memory usage | VM contention from other services or programs running on the same host | If possible, reconfigure other services or programs to use less memory. To increase the total memory available on the VM, see "[Increasing CPU or memory resources](/enterprise/admin/guides/installation/increasing-cpu-or-memory-resources/)." | +| Low disk space availability | Large binaries or log files consuming disk space | If possible, host large binaries on a separate server, and compress or archive log files. If necessary, increase disk space on the VM by following the steps for your platform in "[Increasing storage capacity](/enterprise/admin/guides/installation/increasing-storage-capacity/)." | +| Higher than usual response times | Often caused by one of the above issues | Identify and fix the underlying issues. If response times remain high, contact {% data variables.contact.contact_ent_support %}. | +| Elevated error rates | Software issues | Contact {% data variables.contact.contact_ent_support %} and include your support bundle. For more information, see "[Providing data to {% data variables.product.prodname_enterprise %} Support](/enterprise/{{ currentVersion}}/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-support-bundles)." | diff --git a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md index 165ac7d1d0..0c216af47e 100644 --- a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md +++ b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md @@ -1,6 +1,6 @@ --- -title: 配置 collectd -intro: '{% data variables.product.prodname_enterprise %} 可以通过 `collectd` 收集数据并将数据发送到外部 `collectd` 服务器。 除了其他指标外,我们还会收集标准数据集,例如 CPU 利用率、内存与磁盘使用量、网络接口流量与错误,以及 VM 的总负荷。' +title: Configuring collectd +intro: '{% data variables.product.prodname_enterprise %} can gather data with `collectd` and send it to an external `collectd` server. Among other metrics, we gather a standard set of data such as CPU utilization, memory and disk consumption, network interface traffic and errors, and the VM''s overall load.' redirect_from: - /enterprise/admin/installation/configuring-collectd - /enterprise/admin/articles/configuring-collectd @@ -15,21 +15,15 @@ topics: - Infrastructure - Monitoring - Performance -ms.openlocfilehash: f63eb940681be3131a470a7786e134550fdba152 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145100022' --- -## 设置外部 `collectd` 服务器 +## Set up an external `collectd` server -如果尚未设置外部 `collectd` 服务器,则需要在对 {% data variables.product.product_location %} 启用 `collectd` 转发之前进行设置。 `collectd` 服务器必须运行 `collectd` 5.x 或更高版本。 +If you haven't already set up an external `collectd` server, you will need to do so before enabling `collectd` forwarding on {% data variables.location.product_location %}. Your `collectd` server must be running `collectd` version 5.x or higher. -1. 登录到 `collectd` 服务器。 -2. 创建或编辑 `collectd` 配置文件,以加载网络插件并使用正确的值填充服务器和端口指令。 在大多数发行版中,该文件位于 `/etc/collectd/collectd.conf` +1. Log into your `collectd` server. +2. Create or edit the `collectd` configuration file to load the network plugin and populate the server and port directives with the proper values. On most distributions, this is located at `/etc/collectd/collectd.conf` -用于运行 `collectd` 服务器的示例 collectd.conf: +An example *collectd.conf* to run a `collectd` server: LoadPlugin network ... @@ -38,32 +32,34 @@ ms.locfileid: '145100022' Listen "0.0.0.0" "25826" -## 在 {% data variables.product.prodname_enterprise %} 上启用 collectd 转发 +## Enable collectd forwarding on {% data variables.product.prodname_enterprise %} -默认情况下,在 {% data variables.product.prodname_enterprise %} 上禁用 `collectd` 转发。 请按照以下步骤启用和配置 `collectd` 转发: +By default, `collectd` forwarding is disabled on {% data variables.product.prodname_enterprise %}. Follow the steps below to enable and configure `collectd` forwarding: -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} -1. 在日志转发设置下方,选择“启用 collectd 转发”。 -1. 在“服务器地址”字段中,输入要将 {% data variables.product.prodname_enterprise %} 设备统计信息转发到的 `collectd` 服务器的地址。 -1. 在“端口”字段中,输入用于连接到 `collectd` 服务器的端口。 (默认为 25826) -1. 在“加密设置”下拉菜单中,选择与 `collectd` 服务器通信的安全级别。 (无、签名数据包或加密数据包。){% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +1. Below the log forwarding settings, select **Enable collectd forwarding**. +1. In the **Server address** field, type the address of the `collectd` server to which you'd like to forward {% data variables.product.prodname_enterprise %} appliance statistics. +1. In the **Port** field, type the port used to connect to the `collectd` server. (Defaults to 25826) +1. In the **Cryptographic setup** dropdown menu, select the security level of communications with the `collectd` server. (None, signed packets, or encrypted packets.) +{% data reusables.enterprise_management_console.save-settings %} -## 使用 `ghe-export-graphs` 导出 collectd 数据 +## Exporting collectd data with `ghe-export-graphs` -命令行工具 `ghe-export-graphs` 将导出 `collectd` 存储在 RRD 数据库中的数据。 此命令会将数据转换为 XML 格式并导出到一个 tarball (`.tgz`) 中。 +The command-line tool `ghe-export-graphs` will export the data that `collectd` stores in RRD databases. This command turns the data into XML and exports it into a single tarball (`.tgz`). -此文件的主要用途是为 {% data variables.contact.contact_ent_support %} 团队提供关于 VM 性能的数据(无需下载整个支持包), 不应包含在常规备份导出范围中,也没有对应的导入文件。 如果您联系 {% data variables.contact.contact_ent_support %},我们可能会要求您提供此数据,以便协助故障排查。 +Its primary use is to provide the {% data variables.contact.contact_ent_support %} team with data about a VM's performance, without the need for downloading a full Support Bundle. It shouldn't be included in your regular backup exports and there is no import counterpart. If you contact {% data variables.contact.contact_ent_support %}, we may ask for this data to assist with troubleshooting. -### 使用情况 +### Usage ```shell ssh -p 122 admin@[hostname] -- 'ghe-export-graphs' && scp -P 122 admin@[hostname]:~/graphs.tar.gz . ``` -## 故障排除 +## Troubleshooting -### 中央 collectd 服务器未收到数据 +### Central collectd server receives no data -{% data variables.product.prodname_enterprise %} 随附 `collectd` 版本 5.x。 `collectd` 5.x 不能后向兼容 4.x 发行版系列。 中央 `collectd` 服务器的版本至少需要是 5.x 才能接受从 {% data variables.product.product_location %} 发送的数据。 +{% data variables.product.prodname_enterprise %} ships with `collectd` version 5.x. `collectd` 5.x is not backwards compatible with the 4.x release series. Your central `collectd` server needs to be at least version 5.x to accept data sent from {% data variables.location.product_location %}. -要获取其他问题的帮助,请联系 {% data variables.contact.contact_ent_support %}。 +For help with further questions or issues, contact {% data variables.contact.contact_ent_support %}. diff --git a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md index 0bd266ad02..436c8127ba 100644 --- a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: 为企业生成运行状况检查 -intro: '可通过生成运行状况检查来深入了解 {% data variables.product.product_location %} 的一般运行状况与 Git 和 API 请求。' +title: Generating a Health Check for your enterprise +intro: 'You can gain insight into the general health and Git and API requests of {% data variables.location.product_location %} by generating a Health Check.' versions: ghes: '*' type: how_to @@ -11,53 +11,48 @@ topics: - Monitoring - Performance product: '{% data reusables.gated-features.generated-health-checks %}' -ms.openlocfilehash: f02fc61f050fc01a69f9fafe2dcdc95d91322dfa -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146460015' --- + {% note %} -**注意:** 为 {% data variables.product.prodname_ghe_server %} 生成运行状况检查目前处于测试阶段,可能会发生更改。 +**Note:** Generating a Health Check is currently in beta for {% data variables.product.prodname_ghe_server %} and subject to change. {% endnote %} -## 关于生成的运行状况检查 +## About generated Health Checks -可以为包含大量数据(例如诊断和日志文件)的 {% data variables.product.product_location %} 创建支持捆绑包。 为了帮助分析和解释这些数据,可以生成运行状况检查。 有关支持捆绑包的详细信息,请参阅“[向 {% data variables.contact.github_support %} 提供数据](/support/contacting-github-support/providing-data-to-github-support#creating-and-sharing-support-bundles)”。 +You can create a support bundle for {% data variables.location.product_location %} that contains a lot of data, such as diagnostics and log files. To help analyze and interpret this data, you can generate a Health Check. For more information about support bundles, see "[Providing data to {% data variables.contact.github_support %}](/support/contacting-github-support/providing-data-to-github-support#creating-and-sharing-support-bundles)." -运行状况检查提供有关 {% data variables.product.product_location %} 的以下信息。 -- 针对 {% data variables.product.product_location %} 一般运行状况的见解,例如升级状态、存储和许可证席位消耗 -- 重点关注子域隔离和用户身份验证的安全部分 -- Git 请求分析,包括有关最繁忙的存储库和 Git 用户的详细信息 -- API 请求分析,包括最繁忙的时间、最频繁请求的终结点和最活跃的调用方 +A Health Check provides the following information about {% data variables.location.product_location %}. +- Insights into the general health of {% data variables.location.product_location %}, such as upgrade status, storage, and license seat consumption +- A security section, which focuses on subdomain isolation and user authentication +- Analysis of Git requests, with details about the busiest repositories and Git users +- Analysis of API requests, including the busiest times, most frequently requested endpoints, and most active callers -如果要为 {% data variables.product.prodname_ghe_cloud %} 生成运行状况检查,请联系 {% data variables.contact.github_support %}。 有关详细信息,请参阅“[创建支持工单](/support/contacting-github-support/creating-a-support-ticket)”。 +If you want to generate a Health Check for {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.github_support %}. For more information, see "[Creating a support ticket](/support/contacting-github-support/creating-a-support-ticket)." -## 生成运行状况检查 +## Generating a Health Check -在生成运行状况检查之前,你必须创建一个支持捆绑包。 有关详细信息,请参阅“[向 {% data variables.contact.github_support %} 提供数据](/support/contacting-github-support/providing-data-to-github-support#creating-and-sharing-support-bundles)”。 +Before you can generate a Health Check, you must create a support bundle. For more information, see "[Providing data to {% data variables.contact.github_support %}](/support/contacting-github-support/providing-data-to-github-support#creating-and-sharing-support-bundles)." -1. 导航到 [{% data variables.contact.support_portal %}](https://support.github.com/)。 -2. 在页面的右上角,单击“高级”。 +1. Navigate to the [{% data variables.contact.support_portal %}](https://support.github.com/). +2. In the upper-right corner of the page, click **Premium**. - ![GitHub 支持门户标题中“高级”链接的屏幕截图。](/assets/images/enterprise/support/support-portal-header-premium.png) + ![Screenshot of the "Premium" link in the GitHub Support Portal header.](/assets/images/enterprise/support/support-portal-header-premium.png) -3. 在“运行状况检查”的右侧,单击“请求运行状况检查” 。 +3. To the right of **Health Checks**, click **Request Health Check**. - ![“请求运行状况检查”按钮的屏幕截图。](/assets/images/enterprise/support/support-portal-request-health-check.png) + ![Screenshot of the "Request Health Check" button.](/assets/images/enterprise/support/support-portal-request-health-check.png) -4. 在“选择企业帐户”下,选择下拉菜单并单击企业帐户。 +4. Under "Select an enterprise account", select the dropdown menu and click an enterprise account. - ![“企业帐户”下拉菜单的屏幕截图。](/assets/images/enterprise/support/health-check-dialog-ea.png) + ![Screenshot of the "enterprise account" dropdown menu.](/assets/images/enterprise/support/health-check-dialog-ea.png) -5. 在“上传支持捆绑包”下,单击“选择文件”并选择要上传的文件。 然后,单击“请求运行状况检查”。 +5. Under "Upload a support bundle", click **Chose File** and choose a file to upload. Then, click **Request Health Check**. - ![“选择文件”和“请求运行状况检查”按钮的屏幕截图。](/assets/images/enterprise/support/health-check-dialog-choose-file.png) + ![Screenshot of the "Choose file" and "Request Health Check" buttons.](/assets/images/enterprise/support/health-check-dialog-choose-file.png) -请求运行状况检查后,系统会计划一个作业来生成运行状况检查。 数小时到一天后,生成的运行状况检查将显示在 {% data variables.contact.support_portal %} 的“运行状况检查”部分中。 +After you request a Health Check, a job is scheduled to generate the Health Check. After several hours to one day, the generated Health Check will appear in the "Health Checks" section of the {% data variables.contact.support_portal %}. -![{% data variables.contact.support_portal %} 的“运行状况检查”部分的屏幕截图。](/assets/images/enterprise/support/support-portal-health-checks-section.png) +![Screenshot of the Health Checks section of the {% data variables.contact.support_portal %}.](/assets/images/enterprise/support/support-portal-health-checks-section.png) diff --git a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/index.md b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/index.md index 4f3a215c3e..fb441b33e9 100644 --- a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/index.md +++ b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/index.md @@ -1,6 +1,6 @@ --- -title: 监控设备 -intro: '随着 {% data variables.product.product_location %} 使用量的逐渐增加,系统资源(例如 CPU、内存和存储空间)的利用率也会提高。 您可以配置监视和警报来提示潜在问题,以免这些问题对应用程序性能或可用性造成严重的负面影响。' +title: Monitoring your appliance +intro: 'As use of {% data variables.location.product_location %} increases over time, the utilization of system resources, like CPU, memory, and storage will also increase. You can configure monitoring and alerting so that you''re aware of potential issues before they become critical enough to negatively impact application performance or availability.' redirect_from: - /enterprise/admin/guides/installation/system-resource-monitoring-and-alerting - /enterprise/admin/guides/installation/monitoring-your-github-enterprise-appliance @@ -18,11 +18,5 @@ children: - /monitoring-using-snmp - /about-system-logs - /generating-a-health-check-for-your-enterprise -ms.openlocfilehash: 3232d21371c2ad18ff8a4ebc8dcf7ea603d152ac -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145099083' --- diff --git a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md index 9fc93e3691..9c3f478189 100644 --- a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md +++ b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md @@ -1,6 +1,6 @@ --- -title: 使用 SNMP 进行监视 -intro: '{% data variables.product.prodname_enterprise %} 通过 SNMP 提供关于磁盘使用情况、CPU 利用率和内存使用情况等方面的数据。' +title: Monitoring using SNMP +intro: '{% data variables.product.prodname_enterprise %} provides data on disk usage, CPU utilization, memory usage, and more over SNMP.' redirect_from: - /enterprise/admin/installation/monitoring-using-snmp - /enterprise/admin/articles/monitoring-using-snmp @@ -14,104 +14,108 @@ topics: - Infrastructure - Monitoring - Performance -ms.openlocfilehash: 0f156d2939cbc83e3b0a72bbc1cbaf72f0c886d7 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145179150' --- -SNMP 是一种用于通过网络监视设备的公共标准。 强烈建议启用 SNMP,以便监视 {% data variables.product.product_location %} 的运行状况,并了解何时向主机增加更多内存、存储空间或处理器能力。 +SNMP is a common standard for monitoring devices over a network. We strongly recommend enabling SNMP so you can monitor the health of {% data variables.location.product_location %} and know when to add more memory, storage, or processor power to the host machine. -{% data variables.product.prodname_enterprise %} 具有标准 SNMP 安装,因此你可以利用可用于 Nagios 或任何其他监视系统的[多种插件](https://www.monitoring-plugins.org/doc/man/check_snmp.html)。 +{% data variables.product.prodname_enterprise %} has a standard SNMP installation, so you can take advantage of the [many plugins](https://www.monitoring-plugins.org/doc/man/check_snmp.html) available for Nagios or for any other monitoring system. -## 配置 SNMP v2c +## Configuring SNMP v2c -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.access-monitoring %} {% data reusables.enterprise_management_console.enable-snmp %} -4. 在“社区字符串”字段中,输入新的社区字符串。 如果留空,则默认为 `public`。 -![用于添加社区字符串的字段](/assets/images/enterprise/management-console/community-string.png) {% data reusables.enterprise_management_console.save-settings %} -5. 要测试 SNMP 配置,请在网络中支持 SNMP 的单独工作站上运行以下命令: +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.access-monitoring %} +{% data reusables.enterprise_management_console.enable-snmp %} +4. In the **Community string** field, enter a new community string. If left blank, this defaults to `public`. +![Field to add the community string](/assets/images/enterprise/management-console/community-string.png) +{% data reusables.enterprise_management_console.save-settings %} +5. Test your SNMP configuration by running the following command on a separate workstation with SNMP support in your network: ```shell # community-string is your community string # hostname is the IP or domain of your Enterprise instance - $ snmpget -v 2c -c community-string -O e hostname hrSystemDate.0 + $ snmpget -v 2c -c COMMUNITY-STRING -O e HOSTNAME hrSystemDate.0 ``` -这应该返回 {% data variables.product.product_location %} 主机上的系统时间。 +This should return the system time on {% data variables.location.product_location %} host. -## 基于用户的安全性 +## User-based security -如果您启用 SNMP v3,则可以通过用户安全模型 (USM) 充分利用提升的基于用户的安全性。 对于每个唯一的用户,您可以指定一个安全等级: -- `noAuthNoPriv`:此安全等级不提供任何身份验证和隐私保护。 -- `authNoPriv`:此安全级别提供身份验证,但不提供隐私保护。 要查询设备,您需要用户名和密码(长度必须至少为八个字符)。 与 SNMPv2 相似,发送的信息不会进行加密。 身份验证协议可以是 MD5 或 SHA,默认为 SHA。 -- `authPriv`:此安全级别提供身份验证和隐私保护。 要求进行身份验证(包含一个长度至少为八个字符的身份验证密码),并且会对响应进行加密。 不需要隐私密码,但如果提供隐私密码,其长度必须至少为八个字符。 如果不提供隐私密码,将使用身份验证密码。 隐私协议可以是 DES 或 AES,默认为 AES。 +If you enable SNMP v3, you can take advantage of increased user based security through the User Security Model (USM). For each unique user, you can specify a security level: +- `noAuthNoPriv`: This security level provides no authentication and no privacy. +- `authNoPriv`: This security level provides authentication but no privacy. To query the appliance you'll need a username and password (that must be at least eight characters long). Information is sent without encryption, similar to SNMPv2. The authentication protocol can be either MD5 or SHA and defaults to SHA. +- `authPriv`: This security level provides authentication with privacy. Authentication, including a minimum eight-character authentication password, is required and responses are encrypted. A privacy password is not required, but if provided it must be at least eight characters long. If a privacy password isn't provided, the authentication password is used. The privacy protocol can be either DES or AES and defaults to AES. -## 配置 SNMP v3 的用户 +## Configuring users for SNMP v3 -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.access-monitoring %} {% data reusables.enterprise_management_console.enable-snmp %} -4. 选择“SNMP v3”。 -![用于启用 SNMP v3 的按钮](/assets/images/enterprise/management-console/enable-snmpv3.png) -5. 在“Username(用户名)”中,输入 SNMP v3 用户的唯一用户名。 -![用于键入 SNMP v3 用户名的字段](/assets/images/enterprise/management-console/snmpv3-username.png) -6. 在“安全级别”下拉菜单中,单击你的 SNMP v3 用户的安全级别。 -![SNMP v3 用户安全级别的下拉菜单](/assets/images/enterprise/management-console/snmpv3-securitylevel.png) -7. 对于具有 `authnopriv` 安全级别的 SNMP v3 用户:![authnopriv 安全级别的设置](/assets/images/enterprise/management-console/snmpv3-authnopriv.png) +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.access-monitoring %} +{% data reusables.enterprise_management_console.enable-snmp %} +4. Select **SNMP v3**. +![Button to enable SNMP v3](/assets/images/enterprise/management-console/enable-snmpv3.png) +5. In "Username", type the unique username of your SNMP v3 user. +![Field to type the SNMP v3 username](/assets/images/enterprise/management-console/snmpv3-username.png) +6. In the **Security Level** dropdown menu, click the security level for your SNMP v3 user. +![Dropdown menu for the SNMP v3 user's security level](/assets/images/enterprise/management-console/snmpv3-securitylevel.png) +7. For SNMP v3 users with the `authnopriv` security level: + ![Settings for the authnopriv security level](/assets/images/enterprise/management-console/snmpv3-authnopriv.png) - {% data reusables.enterprise_management_console.authentication-password %} - {% data reusables.enterprise_management_console.authentication-protocol %} -8. 对于具有 `authpriv` 安全级别的 SNMP v3 用户:![authpriv 安全级别的设置](/assets/images/enterprise/management-console/snmpv3-authpriv.png) +8. For SNMP v3 users with the `authpriv` security level: + ![Settings for the authpriv security level](/assets/images/enterprise/management-console/snmpv3-authpriv.png) - {% data reusables.enterprise_management_console.authentication-password %} - {% data reusables.enterprise_management_console.authentication-protocol %} - - (可选)在“Privacy password(隐私密码)”中输入隐私保护密码。 - - 在“隐私密码”右侧的“协议”下拉菜单中,单击你要使用的隐私协议方法。 -9. 单击“添加用户” 。 -![用于添加 SNMP v3 用户的按钮](/assets/images/enterprise/management-console/snmpv3-adduser.png) {% data reusables.enterprise_management_console.save-settings %} + - Optionally, in "Privacy password", type the privacy password. + - On the right side of "Privacy password", in the **Protocol** dropdown menu, click the privacy protocol method you want to use. +9. Click **Add user**. +![Button to add SNMP v3 user](/assets/images/enterprise/management-console/snmpv3-adduser.png) +{% data reusables.enterprise_management_console.save-settings %} -#### 查询 SNMP 数据 +#### Querying SNMP data -关于您的设备的硬件和软件级信息都适用于 SNMP v3。 由于 `noAuthNoPriv` 和 `authNoPriv` 安全级别缺少加密和隐私,我们会将 `hrSWRun` 表 (1.3.6.1.2.1.25.4) 从生成的 SNMP 报告中排除。 如果你使用 `authPriv` 安全级别,则会包含此表。 有关详细信息,请参阅“[OID 参考文档](https://oidref.com/1.3.6.1.2.1.25.4)”。 +Both hardware and software-level information about your appliance is available with SNMP v3. Due to the lack of encryption and privacy for the `noAuthNoPriv` and `authNoPriv` security levels, we exclude the `hrSWRun` table (1.3.6.1.2.1.25.4) from the resulting SNMP reports. We include this table if you're using the `authPriv` security level. For more information, see the "[OID reference documentation](https://oidref.com/1.3.6.1.2.1.25.4)." -如果使用 SNMP v2c,则仅会提供关于您的设备的硬件级信息。 {% data variables.product.prodname_enterprise %} 中的应用程序和服务未配置 OID 来报告指标。 有多个 MIB 可用,可以通过在网络中支持 SNMP 的单独工作站上运行 `snmpwalk` 来查看它们: +With SNMP v2c, only hardware-level information about your appliance is available. The applications and services within {% data variables.product.prodname_enterprise %} do not have OIDs configured to report metrics. Several MIBs are available, which you can see by running `snmpwalk` on a separate workstation with SNMP support in your network: ```shell # community-string is your community string # hostname is the IP or domain of your Enterprise instance -$ snmpwalk -v 2c -c community-string -O e hostname +$ snmpwalk -v 2c -c COMMUNITY-STRING -O e HOSTNAME ``` -在 SNMP 的可用 MIB 中,最有用的是 `HOST-RESOURCES-MIB` (1.3.6.1.2.1.25)。 请参见下表,了解此 MIB 中的一些重要对象: +Of the available MIBs for SNMP, the most useful is `HOST-RESOURCES-MIB` (1.3.6.1.2.1.25). See the table below for some important objects in this MIB: -| 名称 | OID | 说明 | +| Name | OID | Description | | ---- | --- | ----------- | -| hrSystemDate.2 | 1.3.6.1.2.1.25.1.2 | 本地日期和时间的主机标记。 | -| hrSystemUptime.0 | 1.3.6.1.2.1.25.1.1.0 | 自主机上次初始化以来的时间。 | -| hrMemorySize.0 | 1.3.6.1.2.1.25.2.2.0 | 主机上 RAM 的大小。 | -| hrSystemProcesses.0 | 1.3.6.1.2.1.25.1.6.0 | 主机上当前加载或运行的进程上下文数。 | -| hrStorageUsed.1 | 1.3.6.1.2.1.25.2.3.1.6.1 | 主机上已占用的存储空间大小(单位为 hrStorageAllocationUnits)。 | -| hrStorageAllocationUnits.1 | 1.3.6.1.2.1.25.2.3.1.4.1 | hrStorageAllocationUnit 的大小(单位为字节) | +| hrSystemDate.2 | 1.3.6.1.2.1.25.1.2 | The hosts notion of the local date and time of day. | +| hrSystemUptime.0 | 1.3.6.1.2.1.25.1.1.0 | How long it's been since the host was last initialized. | +| hrMemorySize.0 | 1.3.6.1.2.1.25.2.2.0 | The amount of RAM on the host. | +| hrSystemProcesses.0 | 1.3.6.1.2.1.25.1.6.0 | The number of process contexts currently loaded or running on the host. | +| hrStorageUsed.1 | 1.3.6.1.2.1.25.2.3.1.6.1 | The amount of storage space consumed on the host, in hrStorageAllocationUnits. | +| hrStorageAllocationUnits.1 | 1.3.6.1.2.1.25.2.3.1.4.1 | The size, in bytes, of an hrStorageAllocationUnit | -例如,若要使用 SNMP v3 查询 `hrMemorySize`,请在网络中支持 SNMP 的单独工作站上运行以下命令: +For example, to query for `hrMemorySize` with SNMP v3, run the following command on a separate workstation with SNMP support in your network: ```shell # username is the unique username of your SNMP v3 user # auth password is the authentication password # privacy password is the privacy password # hostname is the IP or domain of your Enterprise instance -$ snmpget -v 3 -u username -l authPriv \ - -A "auth password" -a SHA \ - -X "privacy password" -x AES \ - -O e hostname HOST-RESOURCES-MIB::hrMemorySize.0 +$ snmpget -v 3 -u USERNAME -l authPriv \ + -A "AUTH PASSWORD" -a SHA \ + -X "PRIVACY PASSWORD" -x AES \ + -O e HOSTNAME HOST-RESOURCES-MIB::hrMemorySize.0 ``` -若要使用 SNMP v2c 查询 `hrMemorySize`,请在网络中支持 SNMP 的单独工作站上运行以下命令: +With SNMP v2c, to query for `hrMemorySize`, run the following command on a separate workstation with SNMP support in your network: ```shell # community-string is your community string # hostname is the IP or domain of your Enterprise instance -snmpget -v 2c -c community-string hostname HOST-RESOURCES-MIB::hrMemorySize.0 +snmpget -v 2c -c COMMUNITY-STRING HOSTNAME HOST-RESOURCES-MIB::hrMemorySize.0 ``` {% tip %} -**注意:** 为防止泄露有关设备上运行的服务的信息,我们会将 `hrSWRun` 表 (1.3.6.1.2.1.25.4) 从生成的 SNMP 报告中排除,除非你对 SNMP v3 使用 `authPriv` 安全级别。 如果你使用 `authPriv` 安全级别,则会包含 `hrSWRun` 表。 +**Note:** To prevent leaking information about services running on your appliance, we exclude the `hrSWRun` table (1.3.6.1.2.1.25.4) from the resulting SNMP reports unless you're using the `authPriv` security level with SNMP v3. If you're using the `authPriv` security level, we include the `hrSWRun` table. {% endtip %} -有关 SNMP 中常见系统属性的 OID 映射的详细信息,请参阅“[用于 CPU、内存和磁盘统计信息的 Linux SNMP OID](http://www.linux-admins.net/2012/02/linux-snmp-oids-for-cpumemory-and-disk.html)”。 +For more information on OID mappings for common system attributes in SNMP, see "[Linux SNMP OID’s for CPU, Memory and Disk Statistics](http://www.linux-admins.net/2012/02/linux-snmp-oids-for-cpumemory-and-disk.html)". diff --git a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md index 161635d4b9..48672a0695 100644 --- a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md +++ b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md @@ -1,6 +1,6 @@ --- -title: 建议的警报阈值 -intro: '您可以配置警报来提前通知系统资源问题,以免它们影响您的 {% data variables.product.prodname_ghe_server %} 设备的性能。' +title: Recommended alert thresholds +intro: 'You can configure an alert to notify you of system resource issues before they affect your {% data variables.product.prodname_ghe_server %} appliance''s performance.' redirect_from: - /enterprise/admin/guides/installation/about-recommended-alert-thresholds - /enterprise/admin/installation/about-recommended-alert-thresholds @@ -17,42 +17,36 @@ topics: - Performance - Storage shortTitle: Recommended alert thresholds -ms.openlocfilehash: 73adc62a8a322666e08da01a76568c16ed18458c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145098076' --- -## 监视存储 +## Monitoring storage -建议您同时对根存储设备和用户存储设备进行监视,并为警报配置合适的值,在可用磁盘空间不足时提供足够长的响应时间。 +We recommend that you monitor both the root and user storage devices and configure an alert with values that allow for ample response time when available disk space is low. -| 严重性 | 阈值 | +| Severity | Threshold | | -------- | --------- | -| **警告** | 已用磁盘空间超出总大小的 70% | -| **严重** | 已用磁盘空间超出总大小的 85% | +| **Warning** | Disk use exceeds 70% of total available | +| **Critical** | Disk use exceeds 85% of total available | -您可以根据分配的总存储空间、历史增长模式和预期响应时间调整这些值。 我们建议多分配一些存储资源,以便考虑增长情况并避免因分配额外存储空间而需要停机。 +You can adjust these values based on the total amount of storage allocated, historical growth patterns, and expected time to respond. We recommend over-allocating storage resources to allow for growth and prevent the downtime required to allocate additional storage. -## 监视 CPU 和平均负载使用情况 +## Monitoring CPU and load average usage -虽然 CPU 利用率随资源密集型 Git 操作上下波动属于正常情况,但我们建议配置警报来监视异常增高的 CPU 利用率,因为 CPU 利用率长时间处于高水平可能说明实例配置不足。 建议监视 15 分钟系统平均负载,以获取接近或超过分配给虚拟机的 CPU 核心数的值。 +Although it is normal for CPU usage to fluctuate based on resource-intense Git operations, we recommend configuring an alert for abnormally high CPU utilization, as prolonged spikes can mean your instance is under-provisioned. We recommend monitoring the fifteen-minute system load average for values nearing or exceeding the number of CPU cores allocated to the virtual machine. -| 严重性 | 阈值 | +| Severity | Threshold | | -------- | --------- | -| **警告** | 十五分钟平均负载超出 1 倍的 CPU 核心 | -| **严重** | 十五分钟平均负载超出 2 倍的 CPU 核心 | +| **Warning** | Fifteen minute load average exceeds 1x CPU cores | +| **Critical** | Fifteen minute load average exceeds 2x CPU cores | -我们还建议监视虚拟化“盗取”时间,以确保在同一主机系统上运行的虚拟机不会用掉所有实例资源。 +We also recommend that you monitor virtualization "steal" time to ensure that other virtual machines running on the same host system are not using all of the instance's resources. -## 监视内存使用量 +## Monitoring memory usage -分配给 {% data variables.product.product_location %} 的物理内存大小对整体性能和应用程序响应能力有着极大的影响。 系统设计为通过大量使用内核磁盘缓存来加快 Git 操作速度。 建议将正常 RSS 工作使用量设置在最高使用量时总可用 RAM 的 50% 之内。 +The amount of physical memory allocated to {% data variables.location.product_location %} can have a large impact on overall performance and application responsiveness. The system is designed to make heavy use of the kernel disk cache to speed up Git operations. We recommend that the normal RSS working set fit within 50% of total available RAM at peak usage. -| 严重性 | 阈值 | +| Severity | Threshold | | -------- | --------- | -| **警告** | 持续 RSS 使用量超出总可用内存大小的 50% | -| **严重** | 持续 RSS 使用量超出总可用内存大小的 70% | +| **Warning** | Sustained RSS usage exceeds 50% of total available memory | +| **Critical** | Sustained RSS usage exceeds 70% of total available memory | -如果内存已耗尽,内核 OOM 终止程序将尝试终止占用 RAM 较多的应用程序进程以释放内存资源,这样可能导致服务中断。 建议为虚拟机分配的内存大小应大于正常操作过程所需的内存。 +If memory is exhausted, the kernel OOM killer will attempt to free memory resources by forcibly killing RAM heavy application processes, which could result in a disruption of service. We recommend allocating more memory to the virtual machine than is required in the normal course of operations. diff --git a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md index 4d7d430a1b..645c354107 100644 --- a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md +++ b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md @@ -1,6 +1,6 @@ --- -title: 启用自动更新检查 -intro: '你可以启用自动更新检查,使 {% data variables.product.product_location %} 检查和下载最新的 {% data variables.product.prodname_ghe_server %} 版本。' +title: Enabling automatic update checks +intro: 'You can enable automatic update checks so that {% data variables.location.product_location %} checks for and downloads the latest {% data variables.product.prodname_ghe_server %} release.' redirect_from: - /enterprise/admin/installation/enabling-automatic-update-checks - /enterprise/admin/enterprise-management/enabling-automatic-update-checks @@ -12,31 +12,28 @@ topics: - Enterprise - Upgrades shortTitle: Enable automatic update checks -ms.openlocfilehash: c566dc54958cc7d4f26a9279ea3bf8a76aafa636 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146331886' --- -在 {% data variables.product.product_location %} 的升级包自动下载后,你会收到一条消息,通知你可以升级 {% data variables.product.prodname_ghe_server %}。 包会下载到 {% data variables.product.product_location %} 上的 `/var/lib/ghe-updates` 目录中。 有关详细信息,请参阅“[升级 {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server)”。 +When an upgrade package is automatically downloaded for {% data variables.location.product_location %}, you'll receive a message letting you know you can upgrade {% data variables.product.prodname_ghe_server %}. Packages download to the `/var/lib/ghe-updates` directory on {% data variables.location.product_location %}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server)." -如果升级有可用的热补丁,将自动下载 `.hpkg`。 在 Management Console 中,您可以选择立即安装热补丁或排定稍后安装。 有关详细信息,请参阅“[使用热补丁进行升级](/enterprise/admin/guides/installation/upgrading-github-enterprise-server#upgrading-with-a-hotpatch)”。 +If a hotpatch is available for an upgrade, the `.hpkg` will download automatically. In the management console you can choose to install the hotpatch immediately or schedule installation for a later time. For more information, see "[Upgrading with a hotpatch](/enterprise/admin/guides/installation/upgrading-github-enterprise-server#upgrading-with-a-hotpatch)." {% tip %} -提示:若要启用自动更新检查,{% data variables.product.product_location %} 必须能够连接到 `https://github-enterprise.s3.amazonaws.com`。 +**Tip:** To enable automatic update checks, {% data variables.location.product_location %} must be able to connect to `https://github-enterprise.s3.amazonaws.com`. {% endtip %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.updates-tab %} -4. 单击“是,自动检查更新”。 -![用于启用自动更新的按钮](/assets/images/enterprise/management-console/enable_updates_button.png){% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.updates-tab %} +4. Click **Yes, automatically check for updates**. +![Button for enabling automatic updates](/assets/images/enterprise/management-console/enable_updates_button.png) +{% data reusables.enterprise_management_console.save-settings %} -要查看您的实例是否处于最新状态,请检查 Updates 选项卡上的横幅。 +To see if your instance is up-to-date, check the banner on the Updates tab. -![指示您的 GitHub Enterprise Server 版本的横幅](/assets/images/enterprise/management-console/up-to-date-banner.png) +![Banner indicating your release of GitHub Enterprise Server](/assets/images/enterprise/management-console/up-to-date-banner.png) -在“日志”下,可看到最近的更新检查的状态。 +Under **Logs**, you can see the status of the most recent update check. -![更新日志](/assets/images/enterprise/management-console/update-log.png) +![Logs for update](/assets/images/enterprise/management-console/update-log.png) diff --git a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md index 0b5ecd4f44..884c2a3d88 100644 --- a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md +++ b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md @@ -1,6 +1,6 @@ --- -title: 增加 CPU 或内存资源 -intro: '如果 {% data variables.product.prodname_ghe_server %} 上的操作速度较慢,您可能需要增加 CPU 或内存资源。' +title: Increasing CPU or memory resources +intro: 'You can increase the CPU or memory resources for a {% data variables.product.prodname_ghe_server %} instance.' redirect_from: - /enterprise/admin/installation/increasing-cpu-or-memory-resources - /enterprise/admin/enterprise-management/increasing-cpu-or-memory-resources @@ -13,104 +13,99 @@ topics: - Infrastructure - Performance shortTitle: Increase CPU or memory -ms.openlocfilehash: 1ac89694cf374cca1ba47f228f881dc4a5fd405f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146331862' --- {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %} {% note %} -注意:在增加 CPU 或内存资源之前,请将实例置于维护模式。{% ifversion ip-exception-list %} 可以通过配置 IP 异常列表验证更改,以允许从指定 IP 地址进行访问。 {% endif %} 有关详细信息,请参阅“[启用和排定维护模式](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)”。 +**Note:** Before increasing CPU or memory resources, put your instance in maintenance mode.{% ifversion ip-exception-list %} You can validate changes by configuring an IP exception list to allow access from specified IP addresses. {% endif %} For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." {% endnote %} -## 为 AWS 增加 CPU 或内存资源 +## Adding CPU or memory resources for AWS {% note %} -注意:要为 AWS 增加 CPU 或内存资源,必须能够熟练使用 AWS 管理控制台或 `aws ec2` 命令行接口管理 EC2 实例。 有关使用所选 AWS 工具执行重设大小的背景和详细信息,请参阅关于[重设 Amazon EBS 支持的实例大小](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html)的 AWS 文档。 +**Note:** To add CPU or memory resources for AWS, you must be familiar with using either the AWS management console or the `aws ec2` command line interface to manage EC2 instances. For background and details on using the AWS tools of your choice to perform the resize, see the AWS documentation on [resizing an Amazon EBS-backed instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html). {% endnote %} -### 调整的考量因素 +### Resizing considerations -在为 {% data variables.product.product_location %} 增加 CPU 或内存资源之前,回顾以下建议。 +Before increasing CPU or memory resources for {% data variables.location.product_location %}, review the following recommendations. -- 通过 CPU 扩大内存。 {% data reusables.enterprise_installation.increasing-cpus-req %} -- 将弹性 IP 地址分配给实例。 如果未分配弹性 IP,则在重启后您必须调整 {% data variables.product.prodname_ghe_server %} 主机的 DNS A 记录,以反映公共 IP 地址的变更。 在实例重新启动后,如果它启动到 VPC 中,会自动保留弹性 IP (EIP)。 如果实例启动到 EC2-Classic 中,则必须手动重新关联弹性 IP。 +- **Scale your memory with CPUs**. {% data reusables.enterprise_installation.increasing-cpus-req %} +- **Assign an Elastic IP address to the instance**. If you haven't assigned an Elastic IP to your instance, you'll have to adjust the DNS A records for your {% data variables.product.prodname_ghe_server %} host after the restart to account for the change in public IP address. Once your instance restarts, the instance keeps the Elastic IP if you launched the instance in a virtual private cloud (VPC). If you create the instance in an EC2-Classic network, you must manually reassign the Elastic IP to the instance. -### 支持的 AWS 实例类型 +### Supported AWS instance types -您需要根据 CPU/内存规范确定升级的目标实例类型。 +You need to determine the instance type you would like to upgrade to based on CPU/memory specifications. {% data reusables.enterprise_installation.warning-on-scaling %} {% data reusables.enterprise_installation.aws-instance-recommendation %} -### 针对 AWS 进行调整 +### Resizing for AWS {% note %} -注意:对于启动到 EC2-Classic 中的实例,请记下与实例关联的弹性 IP 地址以及实例的 ID。 重启实例后,请重新关联弹性 IP 地址。 +**Note:** For instances launched in EC2-Classic, write down both the Elastic IP address associated with the instance and the instance's ID. Once you restart the instance, re-associate the Elastic IP address. {% endnote %} -无法将 CPU 或内存资源添加到现有的 AWS/EC2 实例。 相反,您必须执行以下操作: +It's not possible to add CPU or memory resources to an existing AWS/EC2 instance. Instead, you must: -1. 停止实例。 -2. 更改实例类型。 -3. 启动实例。 +1. Stop the instance. +2. Change the instance type. +3. Start the instance. {% data reusables.enterprise_installation.configuration-recognized %} -## 在 Microsoft Azure 上添加 CPU 或内存资源 +## Adding CPU or memory resources on Microsoft Azure {% note %} -注意:要在 Microsoft Azure 中添加 CPU 或内存资源,必须熟悉使用 Azure Portal、Azure CLI 或 Azure PowerShell 来管理 VM 实例。 有关使用所选 Azure 工具执行重设大小的背景和详细信息,请参阅 Azure 文档中有关[更改虚拟机大小](https://docs.microsoft.com/en-us/azure/virtual-machines/resize-vm)的内容。 +**Note:** To add CPU or memory resources in Microsoft Azure, you must be familiar with using either the Azure Portal, Azure CLI or Azure PowerShell to manage VM instances. For background and details on using the Azure tools of your choice to perform the resize, please refer to the Azure documentation on [changing the size of a virtual machine](https://docs.microsoft.com/en-us/azure/virtual-machines/resize-vm). {% endnote %} -### 调整的考量因素 +### Resizing considerations -在为 {% data variables.product.product_location %} 增加 CPU 或内存资源之前,回顾以下建议。 +Before increasing CPU or memory resources for {% data variables.location.product_location %}, review the following recommendations. -- 通过 CPU 扩大内存。 {% data reusables.enterprise_installation.increasing-cpus-req %} -- 为实例分配静态 IP 地址。 如果您尚未为实例分配静态 IP,则可能必须在重新启动后调整 {% data variables.product.prodname_ghe_server %} 主机的 DNS A 记录,以应对 IP 地址的更改。 +- **Scale your memory with CPUs**. {% data reusables.enterprise_installation.increasing-cpus-req %} +- **Assign a static IP address to the instance**. If you haven't assigned a static IP to your instance, you might have to adjust the DNS A records for your {% data variables.product.prodname_ghe_server %} host after the restart to account for the change in IP address. -### 支持的 Microsoft Azure 实例大小 +### Supported Microsoft Azure instance sizes -您需要根据 CPU/内存规格确定要升级到的实例大小。 +You need to determine the instance size you would like to upgrade to based on CPU/memory specifications. {% data reusables.enterprise_installation.warning-on-scaling %} {% data reusables.enterprise_installation.azure-instance-recommendation %} -### 针对 Microsoft Azure 调整大小 +### Resizing for Microsoft Azure -可以通过更改 VM 大小来纵向扩展虚拟机。 更改其大小将会导致它重新启动。 在某些情况下,必须先解除分配 VM。 如果新大小在当前托管 VM 的硬件群集上不可用,则可能会出现这种情况。 +You can scale the VM up by changing the VM size. Changing its size will cause it to be restarted. In some cases, you must deallocate the VM first. This can happen if the new size is not available on the hardware cluster that is currently hosting the VM. -1. 所需步骤,请参阅 Azure 文档中有关[更改虚拟机大小](https://docs.microsoft.com/en-us/azure/virtual-machines/resize-vm)的内容。 +1. Refer to the Azure documentation on [changing the size of a virtual machine](https://docs.microsoft.com/en-us/azure/virtual-machines/resize-vm) for the required steps. {% data reusables.enterprise_installation.configuration-recognized %} -## 为 OpenStack KVM 增加 CPU 或内存资源 +## Adding CPU or memory resources for OpenStack KVM -无法将 CPU 或内存资源添加到现有的 OpenStack KVM 实例。 相反,您必须执行以下操作: +It's not possible to add CPU or memory resources to an existing OpenStack KVM instance. Instead, you must: -1. 生成当前实例的快照。 -2. 停止实例。 -3. 选择包含所需 CPU 和/或内存资源的新实例。 +1. Take a snapshot of the current instance. +2. Stop the instance. +3. Select a new instance flavor that has the desired CPU and/or memory resources. -## 为 VMWare 增加 CPU 或内存资源 +## Adding CPU or memory resources for VMware {% data reusables.enterprise_installation.increasing-cpus-req %} -1. 使用 vSphere Client 连接到 VMware ESXi 主机。 -2. 关闭 {% data variables.product.product_location %}。 -3. 选择虚拟机,然后单击“编辑设置”。 -4. 在“硬件”下,根据需要调整分配给虚拟机的 CPU 和/或内存资源:![VMware 设置资源](/assets/images/enterprise/vmware/vsphere-hardware-tab.png) -5. 要启动虚拟机,请单击“确定”。 +1. Use the vSphere Client to connect to the VMware ESXi host. +2. Shut down {% data variables.location.product_location %}. +3. Select the virtual machine and click **Edit Settings**. +4. Under "Hardware", adjust the CPU and/or memory resources allocated to the virtual machine as needed: +![VMware setup resources](/assets/images/enterprise/vmware/vsphere-hardware-tab.png) +5. To start the virtual machine, click **OK**. {% data reusables.enterprise_installation.configuration-recognized %} diff --git a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md index cdc34bb1b5..e55e7cb44d 100644 --- a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md +++ b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md @@ -1,6 +1,6 @@ --- -title: 增加存储容量 -intro: 您可以增加或更改可供 Git 仓库、数据库、搜索索引和其他持久应用程序数据使用的存储容量。 +title: Increasing storage capacity +intro: 'You can increase or change the amount of storage available for Git repositories, databases, search indexes, and other persistent application data.' redirect_from: - /enterprise/admin/installation/increasing-storage-capacity - /enterprise/admin/enterprise-management/increasing-storage-capacity @@ -14,86 +14,80 @@ topics: - Performance - Storage shortTitle: Increase storage capacity -ms.openlocfilehash: b6542e1f43ce4111358de3940c8e46dea2afd5d5 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147881120' --- {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %} -随着更多的用户加入 {% data variables.product.product_location %},你可能需要调整存储卷大小。 有关调整存储容量的信息,请参阅虚拟平台的相关文档。 +As more users join {% data variables.location.product_location %}, you may need to resize your storage volume. Refer to the documentation for your virtualization platform for information on resizing storage. -## 要求和建议 +## Requirements and recommendations {% note %} -注意:在重新调整任何存储卷的大小之前,请将实例置于维护模式。{% ifversion ip-exception-list %} 你可以通过配置 IP 例外列表来验证更改,从而允许从指定 IP 地址进行访问。 {% endif %} 有关详细信息,请参阅“[启用和排定维护模式](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)”。 +**Note:** Before resizing any storage volume, put your instance in maintenance mode.{% ifversion ip-exception-list %} You can validate changes by configuring an IP exception list to allow access from specified IP addresses. {% endif %} For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." {% endnote %} -### 最低要求 +### Minimum requirements {% data reusables.enterprise_installation.hardware-rec-table %} -## 增加数据分区大小 +## Increasing the data partition size -1. 使用虚拟平台工具调整现有用户卷磁盘大小。 +1. Resize the existing user volume disk using your virtualization platform's tools. {% data reusables.enterprise_installation.ssh-into-instance %} -3. 将设备置于维护模式。 有关详细信息,请参阅“[启用和安排维护模式](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)”。 -4. 重启设备,以检测新存储分配。 +3. Put the appliance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." +4. Reboot the appliance to detect the new storage allocation: ```shell $ sudo reboot ``` -5. 运行 `ghe-storage-extend` 命令以扩展 `/data/user` 文件系统: +5. Run the `ghe-storage-extend` command to expand the `/data/user` filesystem: ```shell $ ghe-storage-extend ``` -## 使用新设备增加根分区大小 +## Increasing the root partition size using a new appliance -1. 使用版本与当前设备相同的较大根磁盘来设置新的 {% data variables.product.prodname_ghe_server %} 实例。 有关详细信息,请参阅“[设置 {% data variables.product.prodname_ghe_server %} 实例](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance)”。 -2. 关闭当前设备: +1. Set up a new {% data variables.product.prodname_ghe_server %} instance with a larger root disk using the same version as your current appliance. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance)." +2. Shut down the current appliance: ```shell $ sudo poweroff ``` -3. 使用虚拟平台工具将数据磁盘从当前设备中拆下。 -4. 将数据磁盘安装到根磁盘较大的新设备上。 +3. Detach the data disk from the current appliance using your virtualization platform's tools. +4. Attach the data disk to the new appliance with the larger root disk. -## 使用现有设备增加根分区大小 +## Increasing the root partition size using an existing appliance {% warning %} -警告:在增加根分区大小之前,你必须将你的实例置于维护模式。 有关详细信息,请参阅“[启用和安排维护模式](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)”。 +**Warning:** Before increasing the root partition size, you must put your instance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." {% endwarning %} -1. 将新磁盘连接到 {% data variables.product.prodname_ghe_server %} 设备。 -1. 运行 `lsblk` 命令以标识新磁盘的设备名称。 -1. 运行 `parted` 命令以设置磁盘格式,用你的设备名称取代 `/dev/xvdg`: +1. Attach a new disk to your {% data variables.product.prodname_ghe_server %} appliance. +1. Run the `lsblk` command to identify the new disk's device name. +1. Run the `parted` command to format the disk, substituting your device name for `/dev/xvdg`: ```shell $ sudo parted /dev/xvdg mklabel msdos $ sudo parted /dev/xvdg mkpart primary ext4 0% 50% $ sudo parted /dev/xvdg mkpart primary ext4 50% 100% ``` -1. 若要停止复制,请运行 `ghe-repl-stop` 命令。 +1. To stop replication, run the `ghe-repl-stop` command. ```shell $ ghe-repl-stop ``` -1. 运行 `ghe-upgrade` 命令,将完整的平台特定包安装到新分区的磁盘中。 通用热补丁升级包(例如 `github-enterprise-2.11.9.hpkg`)无法按预期工作。 在 `ghe-upgrade` 命令完成后,应用程序服务将自动终止。 +1. Run the `ghe-upgrade` command to install a full, platform specific package to the newly partitioned disk. A universal hotpatch upgrade package, such as `github-enterprise-2.11.9.hpkg`, will not work as expected. After the `ghe-upgrade` command completes, application services will automatically terminate. ```shell $ ghe-upgrade PACKAGE-NAME.pkg -s -t /dev/xvdg1 ``` -1. 关闭设备: +1. Shut down the appliance: ```shell $ sudo poweroff ``` -1. 在虚拟机监控程序中,移除旧的根磁盘,并将新的根磁盘连接到旧的根磁盘的位置。 -1. 启动设备。 -1. 确保系统服务正常运行,然后释放维护模式。 有关详细信息,请参阅“[启用和安排维护模式](/admin/guides/installation/enabling-and-scheduling-maintenance-mode)”。 +1. In the hypervisor, remove the old root disk and attach the new root disk at the same location as the old root disk. +1. Start the appliance. +1. Ensure system services are functioning correctly, then release maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." -如果你的设备配置为高可用性或异地复制,请记住在所有节点上的存储升级后,使用 `ghe-repl-start` 在每个副本节点上开始复制。 +If your appliance is configured for high-availability or geo-replication, remember to start replication on each replica node using `ghe-repl-start` after the storage on all nodes has been upgraded. diff --git a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md index 5cb10a3362..24cfb85f46 100644 --- a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md +++ b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md @@ -1,6 +1,6 @@ --- -title: 升级要求 -intro: '对 {% data variables.product.prodname_ghe_server %} 进行升级之前,请查阅升级策略规划的建议和要求。' +title: Upgrade requirements +intro: 'Before upgrading {% data variables.product.prodname_ghe_server %}, review these recommendations and requirements to plan your upgrade strategy.' redirect_from: - /enterprise/admin/installation/upgrade-requirements - /enterprise/admin/guides/installation/finding-the-current-github-enterprise-release @@ -13,46 +13,41 @@ type: reference topics: - Enterprise - Upgrades -ms.openlocfilehash: 5b2aae044f2f5198bbd96669221936658d9464a6 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147065184' --- {% note %} -注意:{% ifversion ghes < 3.3 %}- {% data variables.product.prodname_actions %}、{% data variables.product.prodname_registry %}、{% data variables.product.prodname_mobile %} 和 {% data variables.product.prodname_GH_advanced_security %} 等功能可用于 {% data variables.product.prodname_ghe_server %} 3.0 或更高版本。 我们强烈建议升级到 3.0 或更高版本,以利用关键安全更新、错误修复和功能增强。{% endif %} -- [enterprise.github.com](https://enterprise.github.com/releases) 上提供了支持版本的升级包。 验证完成升级所需的升级包的可用性。 如果升级包不可用,请联系 {% data variables.contact.contact_ent_support %} 获得帮助。 -- 如果使用的是 {% data variables.product.prodname_ghe_server %} 群集,请参阅 {% data variables.product.prodname_ghe_server %} 群集指南中的“[升级群集](/enterprise/admin/guides/clustering/upgrading-a-cluster/)”,了解群集特有的特定说明。 -- {% data variables.product.prodname_ghe_server %} 版本说明提供了 {% data variables.product.prodname_ghe_server %} 每一版本的新功能一览表。 有关详细信息,请参阅[发布页面](https://enterprise.github.com/releases)。 +**Notes:** +{% ifversion ghes < 3.3 %}- Features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, {% data variables.product.prodname_mobile %} and {% data variables.product.prodname_GH_advanced_security %} are available on {% data variables.product.prodname_ghe_server %} 3.0 or higher. We highly recommend upgrading to 3.0 or later releases to take advantage of critical security updates, bug fixes and feature enhancements.{% endif %} +- Upgrade packages are available at [enterprise.github.com](https://enterprise.github.com/releases) for supported versions. Verify the availability of the upgrade packages you will need to complete the upgrade. If a package is not available, contact {% data variables.contact.contact_ent_support %} for assistance. +- If you're using {% data variables.product.prodname_ghe_server %} Clustering, see "[Upgrading a cluster](/enterprise/admin/guides/clustering/upgrading-a-cluster/)" in the {% data variables.product.prodname_ghe_server %} Clustering Guide for specific instructions unique to clustering. +- The release notes for {% data variables.product.prodname_ghe_server %} provide a comprehensive list of new features for every version of {% data variables.product.prodname_ghe_server %}. For more information, see the [releases page](https://enterprise.github.com/releases). {% endnote %} -## 建议 +## Recommendations -- 尽量减少升级过程中的升级次数。 例如,不要从 {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} 升级到 {{ enterpriseServerReleases.supported[1] }} 再升级到 {{ enterpriseServerReleases.latest }},而应从 {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} 升级到 {{ enterpriseServerReleases.latest }}。 使用 [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) 查找当前发行版本的升级路径。 -- 如果你的版本比最新版本低几个版本,请通过升级过程的每一步骤尽量将 {% data variables.product.product_location %} 升级为更高版本。 在每次升级时尽可能使用最新版本,这样一来您可以充分利用性能改进和错误修复。 例如,您可以从 {% data variables.product.prodname_enterprise %} 2.7 升级到 2.8 再升级到 2.10,但从 {% data variables.product.prodname_enterprise %} 2.7 升级到 2.9 再升级到 2.10 会在第二步中使用更高版本。 -- 升级时使用最新补丁版本。 {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} -- 使用暂存实例测试升级步骤。 有关详细信息,请参阅“[设置暂存实例](/enterprise/admin/guides/installation/setting-up-a-staging-instance/)”。 -- 如果运行多次升级,两次功能升级之间至少应间隔 24 小时,以便使数据迁移和后台升级任务能够彻底完成。 -- 在升级虚拟机之前拍摄快照。 有关详细信息,请参阅“[拍摄快照](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server#taking-a-snapshot)”。 -- 确保您最近成功备份了实例。 有关详细信息,请参阅 [{% data variables.product.prodname_enterprise_backup_utilities %} README.md 文件](https://github.com/github/backup-utils#readme)。 +- Include as few upgrades as possible in your upgrade process. For example, instead of upgrading from {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} to {{ enterpriseServerReleases.supported[1] }} to {{ enterpriseServerReleases.latest }}, you could upgrade from {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} to {{ enterpriseServerReleases.latest }}. Use the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version. +- If you’re several versions behind, upgrade {% data variables.location.product_location %} as far forward as possible with each step of your upgrade process. Using the latest version possible on each upgrade allows you to take advantage of performance improvements and bug fixes. For example, you could upgrade from {% data variables.product.prodname_enterprise %} 2.7 to 2.8 to 2.10, but upgrading from {% data variables.product.prodname_enterprise %} 2.7 to 2.9 to 2.10 uses a later version in the second step. +- Use the latest patch release when upgrading. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} +- Use a staging instance to test the upgrade steps. For more information, see "[Setting up a staging instance](/enterprise/admin/guides/installation/setting-up-a-staging-instance/)." +- When running multiple upgrades, wait at least 24 hours between feature upgrades to allow data migrations and upgrade tasks running in the background to fully complete. +- Take a snapshot before upgrading your virtual machine. For more information, see "[Taking a snapshot](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server#taking-a-snapshot)." +- Ensure you have a recent, successful backup of your instance. For more information, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README.md file](https://github.com/github/backup-utils#readme). -## 要求 +## Requirements -- 必须从最近两个版本的功能版本开始升级。 例如,要升级到 {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.latest }},您必须使用 {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[1] }} 或 {{ enterpriseServerReleases.supported[2] }}。 -- 使用升级包进行升级时,请为 {% data variables.product.prodname_ghe_server %} 最终用户安排维护时段。 +- You must upgrade from a feature release that's **at most** two releases behind. For example, to upgrade to {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.latest }}, you must be on {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[1] }} or {{ enterpriseServerReleases.supported[2] }}. +- When upgrading using an upgrade package, schedule a maintenance window for {% data variables.product.prodname_ghe_server %} end users. - {% data reusables.enterprise_installation.hotpatching-explanation %} -- 如果受影响的服务(例如内核、MySQL 或 Elasticsearch)需要重启 VM 或服务,热补丁可能需要停机一段时间。 需要重启时,系统会通知您。 您可以在稍后完成重启。 -- 通过热补丁升级时,必须提供额外的根存储,因为热补丁会安装某些服务的多个版本,直至升级完成。 如果根磁盘存储空间不足,运行前检查将发出通知。 -- 通过热补丁进行升级时,您的实例负荷不能过大,否则可能影响热补丁过程。 -- 升级到 {% data variables.product.prodname_ghe_server %} 2.17 会将您的审核日志从 ElasticSearchElasticSearch 迁移到 MySQL。 这种迁移还会增加恢复快照所需的时长和磁盘空间大小。 迁移之前,请使用此命令检查 ElasticSearch 审核日志索引中的字节数: +- A hotpatch may require downtime if the affected services (like kernel, MySQL, or Elasticsearch) require a VM reboot or a service restart. You'll be notified when a reboot or restart is required. You can complete the reboot or restart at a later time. +- Additional root storage must be available when upgrading through hotpatching, as it installs multiple versions of certain services until the upgrade is complete. Pre-flight checks will notify you if you don't have enough root disk storage. +- When upgrading through hotpatching, your instance cannot be too heavily loaded, as it may impact the hotpatching process. +- Upgrading to {% data variables.product.prodname_ghe_server %} 2.17 migrates your audit logs from Elasticsearch to MySQL. This migration also increases the amount of time and disk space it takes to restore a snapshot. Before migrating, check the number of bytes in your Elasticsearch audit log indices with this command: ``` shell curl -s http://localhost:9201/audit_log/_stats/store | jq ._all.primaries.store.size_in_bytes ``` -使用此数字估算 MySQL 审核日志将需要的磁盘空间大小。 该脚本还会在导入过程中监视可用磁盘空间大小。 在可用磁盘空间大小接近于迁移必需的磁盘空间大小时,监视此数字尤为重要。 +Use the number to estimate the amount of disk space the MySQL audit logs will need. The script also monitors your free disk space while the import is in progress. Monitoring this number is especially useful if your free disk space is close to the amount of disk space necessary for migration. -## 后续步骤 +## Next steps -查看这些建议和要求后,您可以对 {% data variables.product.prodname_ghe_server %} 进行升级。 有关详细信息,请参阅“[升级 {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)”。 +After reviewing these recommendations and requirements, you can upgrade {% data variables.product.prodname_ghe_server %}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)." diff --git a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md index 590bf709b2..c1c8100472 100644 --- a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md +++ b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md @@ -32,11 +32,11 @@ shortTitle: Upgrading GHES {% note %} - **Note:** Your {% data variables.product.prodname_enterprise_backup_utilities %} version needs to be the same version as, or at most two versions ahead of, {% data variables.product.product_location %}. For more information, see "[Upgrading GitHub Enterprise Server Backup Utilities](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance#upgrading-github-enterprise-server-backup-utilities)." + **Note:** Your {% data variables.product.prodname_enterprise_backup_utilities %} version needs to be the same version as, or at most two versions ahead of, {% data variables.location.product_location %}. For more information, see "[Upgrading GitHub Enterprise Server Backup Utilities](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance#upgrading-github-enterprise-server-backup-utilities)." {% endnote %} -1. If {% data variables.product.product_location %} uses ephemeral self-hosted runners for {% data variables.product.prodname_actions %} and you've disabled automatic updates, upgrade your runners to the version of the runner application that your upgraded instance will run. +1. If {% data variables.location.product_location %} uses ephemeral self-hosted runners for {% data variables.product.prodname_actions %} and you've disabled automatic updates, upgrade your runners to the version of the runner application that your upgraded instance will run. 1. If you are upgrading using an upgrade package, schedule a maintenance window for {% data variables.product.prodname_ghe_server %} end users. If you are using a hotpatch, maintenance mode is not required. {% note %} @@ -84,7 +84,7 @@ Using the {% data variables.enterprise.management_console %}, you can install a **{% ifversion ghes %}Notes{% else %}Note{% endif %}**: {% ifversion ghes %} -- If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. +- If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. - {% endif %}Installing a hotpatch using the {% data variables.enterprise.management_console %} is not available in clustered environments. To install a hotpatch in a clustered environment, see "[Upgrading a cluster](/enterprise/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)." @@ -184,7 +184,7 @@ While you can use a hotpatch to upgrade to the latest patch release within a fea {% ifversion ip-exception-list %} 1. Optionally, to validate the upgrade, configure an IP exception list to allow access to a specified list of IP addresses. For more information, see "[Validating changes in maintenance mode using the IP exception list](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)." {% endif %} -7. For single appliance upgrades, disable maintenance mode so users can use {% data variables.product.product_location %}. +7. For single appliance upgrades, disable maintenance mode so users can use {% data variables.location.product_location %}. {% note %} @@ -239,7 +239,7 @@ Appliances configured for high-availability and geo-replication use replica inst - If you have upgraded each node to {% data variables.product.product_name %} 3.6.0 or later and started replication, but `git replication is behind the primary` continues to appear after 45 minutes, contact {% data variables.contact.enterprise_support %}. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)." {%- endif %} - {% ifversion ghes = 3.4 or ghes = 3.5 or ghes = 3.6 %}Otherwise, if{% else %}If{% endif %} `ghe-repl-status` did not return `OK`, contact {% data variables.contact.enterprise_support %}. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)." -6. When you have completed upgrading the last replica, and the resync is complete, disable maintenance mode so users can use {% data variables.product.product_location %}. +6. When you have completed upgrading the last replica, and the resync is complete, disable maintenance mode so users can use {% data variables.location.product_location %}. ## Restoring from a failed upgrade diff --git a/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md index bd71918b12..986fa1a462 100644 --- a/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md +++ b/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md @@ -1,7 +1,7 @@ --- title: Backing up and restoring GitHub Enterprise Server with GitHub Actions enabled shortTitle: Backing up and restoring -intro: 'To restore a backup of {% data variables.product.product_location %} when {% data variables.product.prodname_actions %} is enabled, you must configure {% data variables.product.prodname_actions %} before restoring the backup with {% data variables.product.prodname_enterprise_backup_utilities %}.' +intro: 'To restore a backup of {% data variables.location.product_location %} when {% data variables.product.prodname_actions %} is enabled, you must configure {% data variables.product.prodname_actions %} before restoring the backup with {% data variables.product.prodname_enterprise_backup_utilities %}.' versions: ghes: '*' type: how_to @@ -16,13 +16,13 @@ redirect_from: ## About backups of {% data variables.product.product_name %} when using {% data variables.product.prodname_actions %} -You can use {% data variables.product.prodname_enterprise_backup_utilities %} to back up and restore the data and configuration for {% data variables.product.product_location %} to a new instance. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-backups-on-your-appliance)." +You can use {% data variables.product.prodname_enterprise_backup_utilities %} to back up and restore the data and configuration for {% data variables.location.product_location %} to a new instance. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-backups-on-your-appliance)." However, not all the data for {% data variables.product.prodname_actions %} is included in these backups. {% data reusables.actions.enterprise-storage-ha-backups %} ## Restoring a backup of {% data variables.product.product_name %} when {% data variables.product.prodname_actions %} is enabled -To restore a backup of {% data variables.product.product_location %} with {% data variables.product.prodname_actions %}, you must manually configure network settings and external storage on the destination instance before you restore your backup from {% data variables.product.prodname_enterprise_backup_utilities %}. +To restore a backup of {% data variables.location.product_location %} with {% data variables.product.prodname_actions %}, you must manually configure network settings and external storage on the destination instance before you restore your backup from {% data variables.product.prodname_enterprise_backup_utilities %}. 1. Confirm that the source instance is offline. 1. Manually configure network settings on the replacement {% data variables.product.prodname_ghe_server %} instance. Network settings are excluded from the backup snapshot, and are not overwritten by `ghe-restore`. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)." @@ -41,4 +41,4 @@ To restore a backup of {% data variables.product.product_location %} with {% dat ``` {% data reusables.actions.apply-configuration-and-enable %} 1. After {% data variables.product.prodname_actions %} is configured and enabled, to restore the rest of the data from the backup, use the `ghe-restore` command. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)." -1. Re-register your self-hosted runners on the destination instance. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." +1. Re-register your self-hosted runners on the destination instance. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." \ No newline at end of file diff --git a/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md index 26d08e5fe2..c38c209a49 100644 --- a/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: 企业 GitHub Actions 故障排除 -intro: '在 {% data variables.product.prodname_ghe_server %} 上使用 {% data variables.product.prodname_actions %} 时的常见问题疑难解答。' +title: Troubleshooting GitHub Actions for your enterprise +intro: 'Troubleshooting common issues that occur when using {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.' permissions: 'Site administrators can troubleshoot {% data variables.product.prodname_actions %} issues and modify {% data variables.product.prodname_ghe_server %} configurations.' versions: ghes: '*' @@ -12,79 +12,74 @@ topics: redirect_from: - /admin/github-actions/troubleshooting-github-actions-for-your-enterprise shortTitle: Troubleshoot GitHub Actions -ms.openlocfilehash: ff78e1b68664d5eb0931bb98d325e22ae0c458f3 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145099081' --- -## 检查 {% data variables.product.prodname_actions %} 的运行状况 -可以使用 `ghe-actions-check` 命令行实用工具检查 {% data variables.product.product_location %} 上 {% data variables.product.prodname_actions %} 的运行状况。 有关详细信息,请参阅“[命令行实用工具](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-actions-check)”和“[访问管理 shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)”。 +## Checking the health of {% data variables.product.prodname_actions %} -## 使用 {% data variables.product.prodname_ghe_server %} 自签名证书时配置自托管的运行器 +You can check the health of {% data variables.product.prodname_actions %} on {% data variables.location.product_location %} with the `ghe-actions-check` command-line utility. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-actions-check)" and "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." -{% data reusables.actions.enterprise-self-signed-cert %} 有关详细信息,请参阅“[配置 TLS](/admin/configuration/configuring-tls)”。 +## Configuring self-hosted runners when using a self-signed certificate for {% data variables.product.prodname_ghe_server %} -### 在运行器上安装证书 +{% data reusables.actions.enterprise-self-signed-cert %} For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." -为使自托管的运行器使用自签名证书连接到 {% data variables.product.prodname_ghe_server %},您必须在运行器上安装证书以增强连接安全。 +### Installing the certificate on the runner machine -有关安装证书所需的步骤,请参阅运行器操作系统的文件。 +For a self-hosted runner to connect to a {% data variables.product.prodname_ghe_server %} using a self-signed certificate, you must install the certificate on the runner machine so that the connection is security hardened. -### 配置 Node.JS 使用证书 +For the steps required to install a certificate, refer to the documentation for your runner's operating system. -大多数操作都以 JavaScript 编写并使用 Node.js,这不会使用操作系统证书存储。 要使自托管运行器使用证书,你必须在运行器计算机上设置 `NODE_EXTRA_CA_CERTS` 环境变量。 +### Configuring Node.JS to use the certificate -可以将此环境变量设置为系统环境变量,也可以在自托管运行器应用程序目录中名为 .env 的文件中声明此环境变量。 +Most actions are written in JavaScript and run using Node.js, which does not use the operating system certificate store. For the self-hosted runner application to use the certificate, you must set the `NODE_EXTRA_CA_CERTS` environment variable on the runner machine. -例如: +You can set the environment variable as a system environment variable, or declare it in a file named _.env_ in the self-hosted runner application directory. + +For example: ```shell NODE_EXTRA_CA_CERTS=/usr/share/ca-certificates/extra/mycertfile.crt ``` -当自托管的运行器应用程序启动时,环境变量将被读取,因此您必须在配置或启动自托管的运行器应用程序之前设置环境变量。 如果您的证书配置更改,您必须重新启动自托管的运行器应用程序。 +Environment variables are read when the self-hosted runner application starts, so you must set the environment variable before configuring or starting the self-hosted runner application. If your certificate configuration changes, you must restart the self-hosted runner application. -### 配置 Docker 容器使用证书 +### Configuring Docker containers to use the certificate -如果您在工作流程中使用 Docker 容器操作或服务容器,则除了设置上述环境变量外,您可能还需要在 Docker 映像中安装证书。 +If you use Docker container actions or service containers in your workflows, you might also need to install the certificate in your Docker image in addition to setting the above environment variable. -## 配置 {% data variables.product.prodname_actions %} 的 HTTP 代理设置 +## Configuring HTTP proxy settings for {% data variables.product.prodname_actions %} {% data reusables.actions.enterprise-http-proxy %} -如果未正确配置这些设置,你可能会在设置或更改 {% data variables.product.prodname_actions %} 配置时收到错误,例如 `Resource unexpectedly moved to https://`。 +If these settings aren't correctly configured, you might receive errors like `Resource unexpectedly moved to https://` when setting or changing your {% data variables.product.prodname_actions %} configuration. -## 运行器未使用新主机名连接到 {% data variables.product.prodname_ghe_server %} +## Runners not connecting to {% data variables.product.prodname_ghe_server %} with a new hostname {% data reusables.enterprise_installation.changing-hostname-not-supported %} -如果您在环境中使用新主机名部署 {% data variables.product.prodname_ghe_server %},并且旧主机名不再解析到您的实例,则自托管运行器将无法连接到旧主机名,并且不会执行任何作业。 +If you deploy {% data variables.product.prodname_ghe_server %} in your environment with a new hostname and the old hostname no longer resolves to your instance, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs. -您将需要更新自托管运行器的配置,以对 {% data variables.product.product_location %} 使用新的主机名。 每个自托管运行器将需要以下程序之一: +You will need to update the configuration of your self-hosted runners to use the new hostname for {% data variables.location.product_location %}. Each self-hosted runner will require one of the following procedures: -* 在自托管运行器应用程序目录中,编辑 `.runner` 和 `.credentials` 文件以将所有提及的旧主机名均替换为新主机名,然后重启自托管运行器应用程序。 -* 使用 UI 从 {% data variables.product.prodname_ghe_server %} 移除运行器,并重新添加。 有关详细信息,请参阅“[删除自托管运行器](/actions/hosting-your-own-runners/removing-self-hosted-runners)”和“[添加自托管运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners)”。 +* In the self-hosted runner application directory, edit the `.runner` and `.credentials` files to replace all mentions of the old hostname with the new hostname, then restart the self-hosted runner application. +* Remove the runner from {% data variables.product.prodname_ghe_server %} using the UI, and re-add it. For more information, see "[Removing self-hosted runners](/actions/hosting-your-own-runners/removing-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." -## 作业卡住以及 {% data variables.product.prodname_actions %} 内存和 CPU 限制 +## Stuck jobs and {% data variables.product.prodname_actions %} memory and CPU limits -{% data variables.product.prodname_actions %} 由运行在 {% data variables.product.product_location %} 上的多项服务组成。 默认情况下,这些服务使用默认的 CPU 和内存限制设置,大多数情况下都适用。 但是,当 {% data variables.product.prodname_actions %} 用户多时,可能需要调整这些设置。 +{% data variables.product.prodname_actions %} is composed of multiple services running on {% data variables.location.product_location %}. By default, these services are set up with default CPU and memory limits that should work for most instances. However, heavy users of {% data variables.product.prodname_actions %} might need to adjust these settings. -如果您注意到作业未开始,或者任务进度在 UI 中不更新或改变,可能是达到了 CPU 或内存限制(即使有空闲的运行器)。 +You may be hitting the CPU or memory limits if you notice that jobs are not starting (even though there are idle runners), or if the job's progress is not updating or changing in the UI. -### 1. 在管理控制台中检查整体 CPU 和内存使用情况 +### 1. Check the overall CPU and memory usage in the management console -访问管理控制台并使用监控仪表板来检查“System Health(系统健康)”下的整体 CPU 和内存图。 有关详细信息,请参阅“[访问监视仪表板](/admin/enterprise-management/accessing-the-monitor-dashboard)”。 +Access the management console and use the monitor dashboard to inspect the overall CPU and memory graphs under "System Health". For more information, see "[Accessing the monitor dashboard](/admin/enterprise-management/accessing-the-monitor-dashboard)." -如果总体“系统健康”CPU 使用接近 100%,或者没有可用的内存,则表示 {% data variables.product.product_location %} 在满负荷运行,需要扩展。 有关详细信息,请参阅“[增加 CPU 或内存资源](/admin/enterprise-management/increasing-cpu-or-memory-resources)”。 +If the overall "System Health" CPU usage is close to 100%, or there is no free memory left, then {% data variables.location.product_location %} is running at capacity and needs to be scaled up. For more information, see "[Increasing CPU or memory resources](/admin/enterprise-management/increasing-cpu-or-memory-resources)." -### 2. 在管理控制台中检查 Nomad Jobs CPU 和内存使用情况 +### 2. Check the Nomad Jobs CPU and memory usage in the management console -如果总体“系统健康”CPU 和内存使用情况正常,请向下滚动监控仪表板页面到“Nomad Jobs”部分,并查看“CPU 百分比值”和“内存使用情况”图。 +If the overall "System Health" CPU and memory usage is OK, scroll down the monitor dashboard page to the "Nomad Jobs" section, and look at the "CPU Percent Value" and "Memory Usage" graphs. -这些图表中的每幅图都对应于一项服务。 对于 {% data variables.product.prodname_actions %} 服务,请查询: +Each plot in these graphs corresponds to one service. For {% data variables.product.prodname_actions %} services, look for: * `mps_frontend` * `mps_backend` @@ -93,18 +88,18 @@ NODE_EXTRA_CA_CERTS=/usr/share/ca-certificates/extra/mycertfile.crt * `actions_frontend` * `actions_backend` -如果其中任何一项服务达到或接近 100% CPU 利用率,或者内存接近其限制(默认情况下为 2 GB),则这些服务的资源配置可能需要增加。 请注意上述服务中哪些已经达到或接近极限。 +If any of these services are at or near 100% CPU utilization, or the memory is near their limit (2 GB by default), then the resource allocation for these services might need increasing. Take note of which of the above services are at or near their limit. -### 3. 对达到限制的服务增加资源分配 +### 3. Increase the resource allocation for services at their limit -1. 使用 SSH 登录到管理 shell。 有关详细信息,请参阅“[访问管理 shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)”。 -1. 运行以下命令,查看可用于分配的资源: +1. Log in to the administrative shell using SSH. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." +1. Run the following command to see what resources are available for allocation: ```shell nomad node status -self ``` - 在输出中找到“Allocated Resources(分配的资源)”部分。 这类似于以下示例: + In the output, find the "Allocated Resources" section. It looks similar to the following example: ``` Allocated Resources @@ -112,25 +107,25 @@ NODE_EXTRA_CA_CERTS=/usr/share/ca-certificates/extra/mycertfile.crt 7740/49600 MHZ 23 GiB/32 GiB 4.4 GiB/7.9 GiB ``` - 对于 CPU 和内存,这显示了分配给所有服务的量(左侧值)以及可用量(右侧值) 。 在上面的示例中,总共有 32 GiB 内存,分配 23 GiB。 这意味着有 9 GiB 内存可供分配。 + For CPU and memory, this shows how much is allocated to the **total** of **all** services (the left value) and how much is available (the right value). In the example above, there is 23 GiB of memory allocated out of 32 GiB total. This means there is 9 GiB of memory available for allocation. {% warning %} - 警告:请注意不要分配超过可用资源总量,否则服务将无法启动。 + **Warning:** Be careful not to allocate more than the total available resources, or services will fail to start. {% endwarning %} -1. 将目录更改为 `/etc/consul-templates/etc/nomad-jobs/actions`: +1. Change directory to `/etc/consul-templates/etc/nomad-jobs/actions`: ```shell cd /etc/consul-templates/etc/nomad-jobs/actions ``` - 在此目录中,有三个文件与上面的 {% data variables.product.prodname_actions %} 服务对应: + In this directory there are three files that correspond to the {% data variables.product.prodname_actions %} services from above: * `mps.hcl.ctmpl` * `token.hcl.ctmpl` * `actions.hcl.ctmpl` -1. 对于确定需要调整的服务,请打开相应的文件,并找到如下所示的 `resources` 组: +1. For the services that you identified that need adjustment, open the corresponding file and locate the `resources` group that looks like the following: ``` resources { @@ -142,9 +137,9 @@ NODE_EXTRA_CA_CERTS=/usr/share/ca-certificates/extra/mycertfile.crt } ``` - CPU 资源的值以 MHz 为单位,而内存资源以 MB 为单位。 + The values are in MHz for CPU resources, and MB for memory resources. - 例如,要将上述示例中的资源限制增加到 1 GHz 的 CPU 和 4 GB 的内存,则将其更改为: + For example, to increase the resource limits in the above example to 1 GHz for the CPU and 4 GB of memory, change it to: ``` resources { @@ -155,39 +150,39 @@ NODE_EXTRA_CA_CERTS=/usr/share/ca-certificates/extra/mycertfile.crt } } ``` -1. 保存并退出该文件。 -1. 运行 `ghe-config-apply` 来应用更改。 +1. Save and exit the file. +1. Run `ghe-config-apply` to apply the changes. - 运行 `ghe-config-apply` 时,如果输出类似于 `Failed to run nomad job '/etc/nomad-jobs/.hcl'`,则说明在更改时可能过度了分配 CPU 或内存资源。 如果发生这种情况,请再次编辑配置文件,并降低分配的 CPU 或内存,然后重新运行 `ghe-config-apply`。 -1. 应用配置后,运行 `ghe-actions-check` 以验证 {% data variables.product.prodname_actions %} 服务是否正常运行。 + When running `ghe-config-apply`, if you see output like `Failed to run nomad job '/etc/nomad-jobs/.hcl'`, then the change has likely over-allocated CPU or memory resources. If this happens, edit the configuration files again and lower the allocated CPU or memory, then re-run `ghe-config-apply`. +1. After the configuration is applied, run `ghe-actions-check` to verify that the {% data variables.product.prodname_actions %} services are operational. {% ifversion fpt or ghec or ghes > 3.2 %} -## {% data variables.product.prodname_dependabot %} 触发现有工作流程时的故障疑难解答 +## Troubleshooting failures when {% data variables.product.prodname_dependabot %} triggers existing workflows {% data reusables.dependabot.beta-security-and-version-updates %} -为 {% data variables.product.product_location %} 设置 {% data variables.product.prodname_dependabot %} 更新后,当现有工作流程由 {% data variables.product.prodname_dependabot %} 事件触发时,您可能会看到失败。 +After you set up {% data variables.product.prodname_dependabot %} updates for {% data variables.location.product_location %}, you may see failures when existing workflows are triggered by {% data variables.product.prodname_dependabot %} events. -默认情况下,由 {% data variables.product.prodname_dependabot %} 从 `push`、`pull_request`、`pull_request_review` 或 `pull_request_review_comment` 事件中触发的 {% data variables.product.prodname_actions %} 工作流运行被视为从存储库分支中打开。 与其他参与者触发的工作流不同,这意味着它们会接收一个只读 `GITHUB_TOKEN`,并且无权访问任何通常可用的机密。 这将导致尝试写入仓库的任何工作流程在由 {% data variables.product.prodname_dependabot %} 触发时失败。 +By default, {% data variables.product.prodname_actions %} workflow runs that are triggered by {% data variables.product.prodname_dependabot %} from `push`, `pull_request`, `pull_request_review`, or `pull_request_review_comment` events are treated as if they were opened from a repository fork. Unlike workflows triggered by other actors, this means they receive a read-only `GITHUB_TOKEN` and do not have access to any secrets that are normally available. This will cause any workflows that attempt to write to the repository to fail when they are triggered by {% data variables.product.prodname_dependabot %}. -有三种方法可以解决此问题: +There are three ways to resolve this problem: -1. 可以更新工作流,使其不再由 {% data variables.product.prodname_dependabot %} 使用如下表达式触发:`if: github.actor != 'dependabot[bot]'`。 有关详细信息,请参阅“[表达式](/actions/learn-github-actions/expressions)”。 -2. 可以修改工作流以使用包含 `pull_request_target` 的两步过程,该过程没有这些限制。 有关详细信息,请参阅“[使用 {% data variables.product.prodname_actions %} 自动化 {% data variables.product.prodname_dependabot %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions#responding-to-events)”。 -3. 可为由 {% data variables.product.prodname_dependabot %} 触发的工作流提供对机密的访问权限,并允许 `permissions` 术语增加 `GITHUB_TOKEN` 的默认范围。 有关详细信息,请参阅下面的“[为由 {% data variables.product.prodname_dependabot %} 触发的工作流提供对机密的访问权限和增加的权限](#providing-workflows-triggered-by-dependabot-access-to-secrets-and-increased-permissions)”。 +1. You can update your workflows so that they are no longer triggered by {% data variables.product.prodname_dependabot %} using an expression like: `if: github.actor != 'dependabot[bot]'`. For more information, see "[Expressions](/actions/learn-github-actions/expressions)." +2. You can modify your workflows to use a two-step process that includes `pull_request_target` which does not have these limitations. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions#responding-to-events)." +3. You can provide workflows triggered by {% data variables.product.prodname_dependabot %} access to secrets and allow the `permissions` term to increase the default scope of the `GITHUB_TOKEN`. For more information, see "[Providing workflows triggered by{% data variables.product.prodname_dependabot %} access to secrets and increased permissions](#providing-workflows-triggered-by-dependabot-access-to-secrets-and-increased-permissions)" below. -### 提供由 {% data variables.product.prodname_dependabot %} 机密访问权限和增加权限触发的工作流程 +### Providing workflows triggered by {% data variables.product.prodname_dependabot %} access to secrets and increased permissions -1. 使用 SSH 登录到管理 shell。 有关详细信息,请参阅“[访问管理 shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)”。 -1. 要消除 {% data variables.product.product_location %} 上由 {% data variables.product.prodname_dependabot %} 触发的工作流程限制,请使用以下命令。 +1. Log in to the administrative shell using SSH. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." +1. To remove the limitations on workflows triggered by {% data variables.product.prodname_dependabot %} on {% data variables.location.product_location %}, use the following command. ``` shell $ ghe-config app.actions.disable-dependabot-enforcement true ``` -1. 应用配置。 +1. Apply the configuration. ```shell $ ghe-config-apply ``` -1. 返回到 {% data variables.product.prodname_ghe_server %}。 +1. Return to {% data variables.product.prodname_ghe_server %}. {% endif %} @@ -195,38 +190,38 @@ NODE_EXTRA_CA_CERTS=/usr/share/ca-certificates/extra/mycertfile.crt -## {% data variables.product.prodname_actions %} 中的捆绑操作疑难解答 +## Troubleshooting bundled actions in {% data variables.product.prodname_actions %} -如果在 {% data variables.product.prodname_ghe_server %} 中安装 {% data variables.product.prodname_actions %} 时收到以下错误,则可以通过安装官方捆绑的操作和入门工作流程来解决此问题。 +If you receive the following error when installing {% data variables.product.prodname_actions %} in {% data variables.product.prodname_ghe_server %}, you can resolve the problem by installing the official bundled actions and starter workflows. ```shell A part of the Actions setup had problems and needs an administrator to resolve. ``` -要在 {% data variables.product.prodname_ghe_server %} 的指定组织内安装官方捆绑操作和启动工作流程,请按照以下步骤操作。 +To install the official bundled actions and starter workflows within a designated organization in {% data variables.product.prodname_ghe_server %}, follow this procedure. -1. 确定将要存储官方捆绑操作和入门工作流程的组织。 您可以创建新组织或重新使用现有组织。 - - 要创建新组织,请参阅“[从头开始创建新组织](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)”。 - - 若在为此组织选择名称时需要帮助,请参阅“[保留名称](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#reserved-names)”。 +1. Identify an organization that will store the official bundled actions and starter worflows. You can create a new organization or reuse an existing one. + - To create a new organization, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." + - For assistance with choosing a name for this organization, see "[Reserved Names](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#reserved-names)." -1. 使用 SSH 登录到管理 shell。 有关详细信息,请参阅“[访问管理 shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)”。 -1. 要将组织指定为存储捆绑操作的位置,请使用 `ghe-config` 命令,将 `ORGANIZATION` 替换为组织的名称。 +1. Log in to the administrative shell using SSH. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." +1. To designate your organization as the location to store the bundled actions, use the `ghe-config` command, replacing `ORGANIZATION` with the name of your organization. ```shell $ ghe-config app.actions.actions-org ORGANIZATION ``` - and: + and: ```shell $ ghe-config app.actions.github-org ORGANIZATION ``` -1. 要将捆绑操作添加到您的组织,请取消设置 SHA。 +1. To add the bundled actions to your organization, unset the SHA. ```shell $ ghe-config --unset 'app.actions.actions-repos-sha1sum' ``` -1. 应用配置。 +1. Apply the configuration. ```shell $ ghe-config-apply ``` -完成这些步骤后,你可以在“[管理企业中 GitHub Actions 的访问权限](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#managing-access-permissions-for-github-actions-in-your-enterprise)”中继续配置 {% data variables.product.prodname_actions %}。 +After you've completed these steps, you can resume configuring {% data variables.product.prodname_actions %} at "[Managing access permissions for GitHub Actions in your enterprise](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#managing-access-permissions-for-github-actions-in-your-enterprise)." {% endif %} diff --git a/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md b/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md index 6456f916de..c9f9e75ca4 100644 --- a/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md +++ b/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md @@ -1,6 +1,6 @@ --- -title: 使用暂存环境 -intro: '了解如何将 {% data variables.product.prodname_actions %} 与 {% data variables.product.prodname_ghe_server %} 暂存实例配合使用。' +title: Using a staging environment +intro: 'Learn about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %} staging instances.' versions: ghes: '*' type: how_to @@ -12,46 +12,41 @@ topics: redirect_from: - /admin/github-actions/using-a-staging-environment shortTitle: Use staging environment -ms.openlocfilehash: 3d244d25aae5a6e21b4db1cd04352343d6650975 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145100006' --- -## 关于 {% data variables.product.product_name %} 的过渡环境 -为 {% data variables.product.product_location %} 提供临时或测试环境会有用,这样您就可以在生产环境中实施更新或新功能之前进行测试。 有关详细信息,请参阅“[设置暂存实例](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)”。 +## About staging environments for {% data variables.product.product_name %} -## 关于 {% data variables.product.prodname_actions %} 的过渡环境 +It can be useful to have a staging or testing environment for {% data variables.location.product_location %}, so that you can test updates or new features before implementing them in your production environment. For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)." -创建过渡环境的常见方法是在过渡环境中将生产 {% data variables.product.product_name %} 实例的备份还原到新虚拟机。 如果使用暂存实例并计划测试 {% data variables.product.prodname_actions %} 功能,则应在过渡环境中查看存储配置。 +## Using a staging environment with {% data variables.product.prodname_actions %} -将 {% data variables.product.prodname_ghe_server %} 备份还原到暂存实例后,如果尝试从现有的 {% data variables.product.prodname_actions %} 工作流运行中查看日志或项目,则会看到 `404` 错误,因为暂存存储位置中缺少该数据。 若要解决 `404` 错误,可以从生产中复制要在过渡环境中使用的数据。 +A common way to create the staging environment is to restore a backup of your production {% data variables.product.product_name %} instance to a new virtual machine in the staging environment. If you use a staging instance and plan to test {% data variables.product.prodname_actions %} functionality, you should review your storage configuration in the staging environment. -### 配置存储 +After you restore a {% data variables.product.prodname_ghe_server %} backup to the staging instance, if you try to view logs or artifacts from existing {% data variables.product.prodname_actions %} workflow runs on your staging instance, you will see `404` errors, because this data will be missing from your staging storage location. To work around the `404` errors, you can copy data from production to use in your staging environment. -在设置包含启用了 {% data variables.product.prodname_actions %} 的 {% data variables.product.product_name %} 实例的过渡环境时,你必须对 {% data variables.product.prodname_actions %} 存储使用与生产环境不同的外部存储配置。 +### Configuring storage + +When you set up a staging environment that includes a {% data variables.product.product_name %} instance with {% data variables.product.prodname_actions %} enabled, you must use a different external storage configuration for {% data variables.product.prodname_actions %} storage than your production environment. {% warning %} -警告:如果不更改存储配置,暂存实例可能会写入用于生产的相同外部存储,这可能会导致数据丢失。 +**Warning**: If you don't change the storage configuration, your staging instance may be able to write to the same external storage that you use for production, which could result in loss of data. {% endwarning %} -有关 {% 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-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#enabling-github-actions-with-your-storage-provider)”。 +For more information about storage configuration for {% data variables.product.prodname_actions %}, 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-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#enabling-github-actions-with-your-storage-provider)." -### 将文件从生产复制到暂存 +### Copying files from production to staging -若要更准确地映射生产环境,可以选择将文件从 {% data variables.product.prodname_actions %} 的生产存储位置复制到暂存存储位置。 +To more accurately mirror your production environment, you can optionally copy files from your production storage location for {% data variables.product.prodname_actions %} to the staging storage location. -* 对于 Azure 存储帐户,可以使用 [`azcopy`](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs#copy-all-containers-directories-and-blobs-to-another-storage-account)。 例如: +* For an Azure storage account, you can use [`azcopy`](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs#copy-all-containers-directories-and-blobs-to-another-storage-account). For example: ```shell azcopy copy 'https://SOURCE-STORAGE-ACCOUNT-NAME.blob.core.windows.net/SAS-TOKEN' 'https://DESTINATION-STORAGE-ACCOUNT-NAME.blob.core.windows.net/' --recursive ``` -* 对于 Amazon S3 存储桶,可以使用 [`aws s3 sync`](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html)。 例如: +* For Amazon S3 buckets, you can use [`aws s3 sync`](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html). For example: ```shell - aws s3 sync s3://SOURCE-BUCKET s3://DESTINATION-BUCKET + aws s3 sync s3://SOURCE-BUCKET s3://DESTINATION-BUCKET ``` diff --git a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md index f52a65d2c7..be47b2ae56 100644 --- a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md +++ b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md @@ -1,6 +1,6 @@ --- -title: 使用 MinIO Gateway for NAS 存储启用 GitHub Actions -intro: '可以在 {% data variables.product.prodname_ghe_server %} 上启用 {% data variables.product.prodname_actions %},并使用 MinIO Gateway for NAS 存储来存储工作流运行生成的数据。' +title: Enabling GitHub Actions with MinIO Gateway for NAS storage +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use MinIO Gateway for NAS storage to store data generated by workflow runs.' permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' versions: ghes: '*' @@ -13,35 +13,36 @@ topics: redirect_from: - /admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage shortTitle: MinIO Gateway for NAS storage -ms.openlocfilehash: 9fced80eb2a486ffae44d21f3fad278a933eb92d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146682307' --- + {% data reusables.actions.minio-gateways-removal %} -## 先决条件 +## Prerequisites -在启用 {% data variables.product.prodname_actions %} 之前,请确保您已完成以下步骤: +Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: -* 为避免设备上的资源争用,我们建议将 MinIO 与 {% data variables.product.product_location %} 分开托管。 -* 创建用于存储工作流数据的桶。 {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %} +* To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.location.product_location %}. +* Create your bucket for storing workflow data. {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %} {% data reusables.actions.enterprise-common-prereqs %} -## 使用 MinIO Gateway for NAS 存储启用 {% data variables.product.prodname_actions %} +## Enabling {% data variables.product.prodname_actions %} with MinIO Gateway for NAS storage -{% data reusables.enterprise_installation.ssh-into-instance %} {% data reusables.actions.perform-blob-storage-precheck %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.actions %} {% data reusables.actions.enterprise-enable-checkbox %} -1. 在“项目和日志存储”下,选择“Amazon S3”,然后输入存储桶的详细信息: +{% data reusables.enterprise_installation.ssh-into-instance %} +{% data reusables.actions.perform-blob-storage-precheck %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.actions %} +{% data reusables.actions.enterprise-enable-checkbox %} +1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details: - * AWS 服务 URL:MinIO 服务的 URL。 例如 `https://my-minio.example:9000`。 - * AWS S3 存储桶:S3 存储桶的名称。 - * AWS S3 访问密钥和 AWS S3 密钥:用于 MinIO 实例的 `MINIO_ACCESS_KEY` 和 `MINIO_SECRET_KEY` 。 + * **AWS Service URL**: The URL to your MinIO service. For example, `https://my-minio.example:9000`. + * **AWS S3 Bucket**: The name of your S3 bucket. + * **AWS S3 Access Key** and **AWS S3 Secret Key**: The `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` used for your MinIO instance. - ![用于选择 Amazon S3 存储的单选按钮和用于 MinIO 配置的字段](/assets/images/enterprise/management-console/actions-minio-s3-storage.png) -1. 在“项目和日志存储”下,选择“强制路径样式”。 - ![“强制路径样式”的复选框](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) {% data reusables.enterprise_management_console.save-settings %} + ![Radio button for selecting Amazon S3 Storage and fields for MinIO configuration](/assets/images/enterprise/management-console/actions-minio-s3-storage.png) +1. Under "Artifact & Log Storage", select **Force path style**. + ![Checkbox to Force path style](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) +{% data reusables.enterprise_management_console.save-settings %} {% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md index 5823625b0b..dec9d74057 100644 --- a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md +++ b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md @@ -1,6 +1,6 @@ --- -title: 管理企业中 Dependabot 更新的自托管运行器 -intro: '可以为 {% data variables.product.product_location %} 创建专用运行器,{% data variables.product.prodname_dependabot %} 使用它来创建拉取请求,以帮助保护和维护企业存储库中使用的依赖项。' +title: Managing self-hosted runners for Dependabot updates on your enterprise +intro: 'You can create dedicated runners for {% data variables.location.product_location %} that {% data variables.product.prodname_dependabot %} uses to create pull requests to help secure and maintain the dependencies used in repositories on your enterprise.' redirect_from: - /admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates allowTitleToDifferFromFilename: true @@ -13,47 +13,44 @@ topics: - Dependabot - Dependencies shortTitle: Dependabot updates -ms.openlocfilehash: 68fa6772ea2312f3cc0440d76808ee6816eead8e -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146681067' --- + {% data reusables.dependabot.beta-security-and-version-updates %} -## 关于 {% data variables.product.prodname_dependabot_updates %} 的自托管运行器 +## About self-hosted runners for {% data variables.product.prodname_dependabot_updates %} -可以通过设置 {% data variables.product.prodname_dependabot %} 安全性和版本更新来帮助 {% data variables.product.product_location %} 的用户创建和维护安全代码。 借助 {% data variables.product.prodname_dependabot_updates %},开发人员可以配置存储库,以便其依赖项自动更新并保持安全性。 有关详细信息,请参阅“[为企业启用 {% data variables.product.prodname_dependabot %}](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)”。 +You can help users of {% data variables.location.product_location %} to create and maintain secure code by setting up {% data variables.product.prodname_dependabot %} security and version updates. With {% data variables.product.prodname_dependabot_updates %}, developers can configure repositories so that their dependencies are updated and kept secure automatically. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." -要在 {% data variables.product.product_location %} 上使用 {% data variables.product.prodname_dependabot_updates %},必须配置自托管运行器来创建将更新依赖项的拉取请求。 +To use {% data variables.product.prodname_dependabot_updates %} on {% data variables.location.product_location %}, you must configure self-hosted runners to create the pull requests that will update dependencies. -## 先决条件 +## Prerequisites -{% ifversion dependabot-updates-github-connect %} 配置自托管运行器只是启用 {% data variables.product.prodname_dependabot_updates %} 过程中的一个步骤。 在这些步骤之前必须先执行几个步骤,包括配置 {% data variables.product.product_location %} 以将 {% data variables.product.prodname_actions %} 与自托管运行器配合使用。 有关详细信息,请参阅“[为企业启用 {% data variables.product.prodname_dependabot %}](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)”。 -{% else %} 在为 {% data variables.product.prodname_dependabot_updates %} 配置自托管运行器之前,必须: +{% ifversion dependabot-updates-github-connect %} +Configuring self-hosted runners is only one step in the middle of the process for enabling {% data variables.product.prodname_dependabot_updates %}. There are several steps you must follow before these steps, including configuring {% data variables.location.product_location %} to use {% data variables.product.prodname_actions %} with self-hosted runners. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." +{% else %} +Before you configure self-hosted runners for {% data variables.product.prodname_dependabot_updates %}, you must: -- 配置 {% data variables.product.product_location %} 以将 {% data variables.product.prodname_actions %} 与自托管运行器配合使用。 有关详细信息,请参阅“[适用于 GitHub Enterprise Server 的 {% data variables.product.prodname_actions %} 入门](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)”。 -- 为企业启用 {% data variables.product.prodname_dependabot_alerts %}。 有关详细信息,请参阅“[为企业启用 {% data variables.product.prodname_dependabot %}](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)”。 +- Configure {% data variables.location.product_location %} to use {% data variables.product.prodname_actions %} with self-hosted runners. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)." +- Enable {% data variables.product.prodname_dependabot_alerts %} for your enterprise. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% endif %} -## 为 {% data variables.product.prodname_dependabot_updates %} 配置自托管运行器 +## Configuring self-hosted runners for {% data variables.product.prodname_dependabot_updates %} -将 {% data variables.product.product_location %} 配置为使用 {% data variables.product.prodname_actions %} 后,需要为 {% data variables.product.prodname_dependabot_updates %} 添加自托管运行器。 +After you configure {% data variables.location.product_location %} to use {% data variables.product.prodname_actions %}, you need to add self-hosted runners for {% data variables.product.prodname_dependabot_updates %}. -### {% data variables.product.prodname_dependabot %} 运行器的系统要求 +### System requirements for {% data variables.product.prodname_dependabot %} runners -用于 {% data variables.product.prodname_dependabot %} 运行器的任何 VM 都必须满足自托管运行器的要求。 此外,它们还必须满足以下要求。 +Any VM that you use for {% data variables.product.prodname_dependabot %} runners must meet the requirements for self-hosted runners. In addition, they must meet the following requirements. -- Linux 操作系统{% ifversion ghes < 3.5 %} -- 已安装 Git{% endif %} -- 安装有运行器用户访问权限的 Docker: - - 建议在无根模式下安装 Docker,并将运行器配置为在没有 `root` 特权的情况下访问 Docker。 - - 或者,安装 Docker 并授予运行器用户提升的权限来运行 Docker。 +- Linux operating system{% ifversion ghes < 3.5 %} +- Git installed{% endif %} +- Docker installed with access for the runner users: + - We recommend installing Docker in rootless mode and configuring the runners to access Docker without `root` privileges. + - Alternatively, install Docker and give the runner users raised privileges to run Docker. -CPU 和内存要求将取决于在给定 VM 上部署的并发运行器的数量。 作为指导,我们已在一台 2 CPU 8GB 的计算机上成功设置了 20 个运行器,但最终,CPU 和内存要求将在很大程度上取决于正在更新的存储库。 某些生态系统需要比其他生态系统更多的资源。 +The CPU and memory requirements will depend on the number of concurrent runners you deploy on a given VM. As guidance, we have successfully set up 20 runners on a single 2 CPU 8GB machine, but ultimately, your CPU and memory requirements will heavily depend on the repositories being updated. Some ecosystems will require more resources than others. -如果在 VM 上指定了 14 个以上的并发运行器,则还必须更新 Docker `/etc/docker/daemon.json` 配置,以增加 Docker 可以创建的默认网络数。 +If you specify more than 14 concurrent runners on a VM, you must also update the Docker `/etc/docker/daemon.json` configuration to increase the default number of networks Docker can create. ``` { @@ -63,23 +60,23 @@ CPU 和内存要求将取决于在给定 VM 上部署的并发运行器的数量 } ``` -### {% data variables.product.prodname_dependabot %} 运行器的网络要求 +### Network requirements for {% data variables.product.prodname_dependabot %} runners -{% data variables.product.prodname_dependabot %} 运行器需要访问公共 Internet、{% data variables.product.prodname_dotcom_the_website %} 以及将在 {% data variables.product.prodname_dependabot %} 更新中使用的任何内部注册表。 为了最大程度地降低内部网络的风险,应该限制虚拟机 (VM) 对内部网络的访问。 如果运行器下载了一个被劫持的依赖项,这将减少内部系统损坏的可能性。 +{% data variables.product.prodname_dependabot %} runners require access to the public internet, {% data variables.product.prodname_dotcom_the_website %}, and any internal registries that will be used in {% data variables.product.prodname_dependabot %} updates. To minimize the risk to your internal network, you should limit access from the Virtual Machine (VM) to your internal network. This reduces the potential for damage to internal systems if a runner were to download a hijacked dependency. -### 为 {% data variables.product.prodname_dependabot %} 添加自托管运行器 +### Adding self-hosted runners for {% data variables.product.prodname_dependabot %} updates -1. 在存储库、组织或企业帐户级别预配自托管运行器。 有关自托管运行器的信息,请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”和“[添加自托管运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners)”。 +1. Provision self-hosted runners, at the repository, organization, or enterprise account level. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." -2. 按照上述要求设置自托管运行器。 例如,在运行 Ubuntu 20.04 的 VM 上,你可以:{% ifversion ghes < 3.5 %} +2. Set up the self-hosted runners with the requirements described above. For example, on a VM running Ubuntu 20.04 you would:{% ifversion ghes < 3.5 %} - - 验证是否已安装 Git:`command -v git`{% endif %} - - 安装 Docker 并确保运行器用户有权访问 Docker。 有关详细信息,请参阅 Docker 文档。 - - [在 Ubuntu 上安装 Docker 引擎](https://docs.docker.com/engine/install/ubuntu/) - - 建议方法:[以非根用户身份运行 Docker 守护程序(无根模式)](https://docs.docker.com/engine/security/rootless/) - - 替代方法:[以非根用户身份管理 Docker](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) - - 验证运行器是否有权访问公共 Internet,并且只能访问 {% data variables.product.prodname_dependabot %} 所需的内部网络。 + - Verify that Git is installed: `command -v git`{% endif %} + - Install Docker and ensure that the runner users have access to Docker. For more information, see the Docker documentation. + - [Install Docker Engine on Ubuntu](https://docs.docker.com/engine/install/ubuntu/) + - Recommended approach: [Run the Docker daemon as a non-root user (Rootless mode)](https://docs.docker.com/engine/security/rootless/) + - Alternative approach: [Manage Docker as a non-root user](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) + - Verify that the runners have access to the public internet and can only access the internal networks that {% data variables.product.prodname_dependabot %} needs. -3. 将 `dependabot` 标签分配给希望 {% data variables.product.prodname_dependabot %} 使用的每个运行器。 有关详细信息,请参阅“[将标签与自托管运行器配合使用](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners#assigning-a-label-to-a-self-hosted-runner)”。 +3. Assign a `dependabot` label to each runner you want {% data variables.product.prodname_dependabot %} to use. For more information, see "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners#assigning-a-label-to-a-self-hosted-runner)." -4. (可选)允许 {% data variables.product.prodname_dependabot %} 触发的工作流使用只读权限以外的权限,并有权访问通常可用的任何机密。 有关详细信息,请参阅[排查企业 {% data variables.product.prodname_actions %} 问题](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise#enabling-workflows-triggered-by-dependabot-access-to-dependabot-secrets-and-increased-permissions)。 +4. Optionally, enable workflows triggered by {% data variables.product.prodname_dependabot %} to use more than read-only permissions and to have access to any secrets that are normally available. For more information, see "[Troubleshooting {% data variables.product.prodname_actions %} for your enterprise](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise#enabling-workflows-triggered-by-dependabot-access-to-dependabot-secrets-and-increased-permissions)." diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md index 53143aafdb..c8553798a2 100644 --- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md +++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md @@ -33,7 +33,7 @@ topics: {% data variables.product.prodname_actions %} helps your team work faster at scale. When large repositories start using {% data variables.product.prodname_actions %}, teams merge significantly more pull requests per day, and the pull requests are merged significantly faster. For more information, see "[Writing and shipping code faster](https://octoverse.github.com/writing-code-faster/#scale-through-automation)" in the State of the Octoverse. -You can create your own unique automations, or you can use and adapt workflows from our ecosystem of over 10,000 actions built by industry leaders and the open source community. {% ifversion ghec %}For more information, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."{% else %}You can restrict your developers to using actions that exist on {% data variables.product.product_location %}, or you can allow your developers to access actions on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About using actions in your enterprise](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)."{% endif %} +You can create your own unique automations, or you can use and adapt workflows from our ecosystem of over 10,000 actions built by industry leaders and the open source community. {% ifversion ghec %}For more information, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."{% else %}You can restrict your developers to using actions that exist on {% data variables.location.product_location %}, or you can allow your developers to access actions on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About using actions in your enterprise](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)."{% endif %} {% data variables.product.prodname_actions %} is developer friendly, because it's integrated directly into the familiar {% data variables.product.product_name %} experience. @@ -50,7 +50,7 @@ You can create your own unique automations, or you can use and adapt workflows f {% data reusables.actions.migrating-enterprise %} {% ifversion ghes %} -{% data reusables.actions.ghes-actions-not-enabled-by-default %} After you finish planning, you can follow the instructions for enabling {% data variables.product.prodname_actions %}. For example, you may need to upgrade the CPU and memory resources for {% data variables.product.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server)." +{% data reusables.actions.ghes-actions-not-enabled-by-default %} After you finish planning, you can follow the instructions for enabling {% data variables.product.prodname_actions %}. For example, you may need to upgrade the CPU and memory resources for {% data variables.location.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server)." {% else %} After you finish planning, you can follow the instructions for getting started with {% data variables.product.prodname_actions %}. For more information, see {% ifversion ghec %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_cloud %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud)."{% elsif ghae %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)."{% endif %} diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md index d36aecbacc..babd01f28f 100644 --- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md @@ -1,7 +1,7 @@ --- -title: GitHub Actions for GitHub Enterprise Server 使用入门 +title: Getting started with GitHub Actions for GitHub Enterprise Server shortTitle: Get started -intro: '了解首次在 {% data variables.product.prodname_ghe_server %} 上启用和配置 {% data variables.product.prodname_actions %}。' +intro: 'Learn about enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} for the first time.' permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' redirect_from: - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage @@ -14,45 +14,39 @@ type: how_to topics: - Actions - Enterprise -ms.openlocfilehash: 886f057de3893ae10dbddda6c1ee03d428511677 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147580573' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## 关于 {% data variables.product.prodname_ghe_server %} 上的 {% data variables.product.prodname_actions %} +## About {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} -本文介绍站点管理员如何配置 {% data variables.product.prodname_ghe_server %} 来使用 {% data variables.product.prodname_actions %}。 +This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}. {% data reusables.enterprise.upgrade-ghes-for-actions %} -{% data reusables.actions.ghes-actions-not-enabled-by-default %} 您需要确定您的实例是否有足够的 CPU 和内存资源处理来自 {% data variables.product.prodname_actions %} 的负载而不会造成性能损失,并可能增加这些资源。 你还需要确定将哪个存储提供商用于存储工作流运行生成的工件{% ifversion actions-caching %}和缓存{% endif %}所需的 Blob 存储。 然后,您将为企业启用 {% data variables.product.prodname_actions %},管理访问权限,并添加自托管运行器以运行工作流程。 +{% data reusables.actions.ghes-actions-not-enabled-by-default %} You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from {% data variables.product.prodname_actions %} without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts{% ifversion actions-caching %} and caches{% endif %} generated by workflow runs. Then, you'll enable {% data variables.product.prodname_actions %} for your enterprise, manage access permissions, and add self-hosted runners to run workflows. {% data reusables.actions.introducing-enterprise %} {% data reusables.actions.migrating-enterprise %} -## 检查硬件要求 +## Review hardware requirements {%- ifversion ghes < 3.6 %} -可用于 {% data variables.product.product_location %} 的 CPU 和内存资源可确定可同时运行且不造成绩效损失的工作数量。 {% data reusables.actions.minimum-hardware %} +The CPU and memory resources available to {% data variables.location.product_location %} determine the number of jobs that can be run concurrently without performance loss. {% data reusables.actions.minimum-hardware %} -在没有性能损失的情况下并行工作的高峰数量取决于作业持续时间限、构件使用、运行操作的仓库数量,以及实例所做的与操作无关的其他工作量等。 GitHub 的内部测试在一系列 CPU 和内存配置中证明了 GitHub Enterprise Server 的以下性能目标: +The peak quantity of concurrent jobs running without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations: {% endif %} {%- ifversion ghes > 3.5 %} -可用于 {% data variables.product.product_location %} 的 CPU 和内存资源可确定在不造成性能损失的情况下可以配置的运行器数量。 {% data reusables.actions.minimum-hardware %} +The CPU and memory resources available to {% data variables.location.product_location %} determine the number of runners that can be configured without performance loss. {% data reusables.actions.minimum-hardware %} -在没有性能损失的情况下连接运行器的高峰数量取决于作业持续时间限、构件使用、运行操作的存储库数量,以及实例所做的与操作无关的其他工作量等因素。 GitHub 的内部测试在一系列 CPU 和内存配置中证明了 GitHub Enterprise Server 的以下性能目标: +The peak quantity of connected runners without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations: {% endif %} @@ -60,7 +54,7 @@ ms.locfileid: '147580573' {% data reusables.actions.hardware-requirements-3.2 %} -最大并发性是使用多个存储库、大约 10 分钟的作业持续时间和 10 MB 的项目上传来度量的。 您可能会经历不同的性能,具体取决于实例的总体活动水平。 +Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. {%- endif %} @@ -68,7 +62,7 @@ ms.locfileid: '147580573' {% data reusables.actions.hardware-requirements-3.3 %} -最大并发性是使用多个存储库、大约 10 分钟的作业持续时间和 10 MB 的项目上传来度量的。 您可能会经历不同的性能,具体取决于实例的总体活动水平。 +Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. {%- endif %} @@ -76,7 +70,7 @@ ms.locfileid: '147580573' {% data reusables.actions.hardware-requirements-3.4 %} -最大并发性是使用多个存储库、大约 10 分钟的作业持续时间和 10 MB 的项目上传来度量的。 您可能会经历不同的性能,具体取决于实例的总体活动水平。 +Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. {%- endif %} @@ -84,11 +78,11 @@ ms.locfileid: '147580573' {% data reusables.actions.hardware-requirements-3.5 %} -{% data variables.product.company_short %} 使用多个存储库、约 10 分钟的作业持续时间以及 10 MB 项目上传测得最大并行数。 您可能会经历不同的性能,具体取决于实例的总体活动水平。 +{% data variables.product.company_short %} measured maximum concurrency using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. {% note %} -注意:从 {% data variables.product.prodname_ghe_server %} 3.5 开始,{% data variables.product.company_short %} 的内部测试使用第三代 CPU 来更好地反映典型的客户配置。 CPU 中的这项更改表示此版本 {% data variables.product.prodname_ghe_server %} 中性能目标的一小部分更改。 +**Note:** Beginning with {% data variables.product.prodname_ghe_server %} 3.5, {% data variables.product.company_short %}'s internal testing uses 3rd generation CPUs to better reflect a typical customer configuration. This change in CPU represents a small portion of the changes to performance targets in this version of {% data variables.product.prodname_ghe_server %}. {% endnote %} @@ -99,20 +93,21 @@ ms.locfileid: '147580573' {% data reusables.actions.hardware-requirements-3.6 %} -{% data variables.product.company_short %} 使用多个存储库、约 10 分钟的作业持续时间以及 10 MB 项目上传测得最大连接运行器数量。 您可能会经历不同的性能,具体取决于实例的总体活动水平。 +{% data variables.product.company_short %} measured maximum connected runners using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. {% note %} -**注意:** +**Notes:** -- 从 {% data variables.product.prodname_ghe_server %} 3.6 开始,{% data variables.product.company_short %} 记录连接运行器,而不是并发作业。 连接运行器表示可以连接并预期会利用的最多数量的运行器。 还应该注意的是,连接的运行器数量超出预期数量可能会对性能产生负面影响。 +- Beginning with {% data variables.product.prodname_ghe_server %} 3.6, {% data variables.product.company_short %} documents connected runners as opposed to concurrent jobs. Connected runners represents the most runners you can connect and expect to utilize. It should also be noted that connecting more runners than you can expect to utilize can negatively impact performance. -- 从 {% data variables.product.prodname_ghe_server %} 3.5 开始,{% data variables.product.company_short %} 的内部测试使用第三代 CPU 来更好地反映典型的客户配置。 CPU 中的这项更改表示此版本 {% data variables.product.prodname_ghe_server %} 中性能目标的一小部分更改。 -{% endnote %} {%- endif %} +- Beginning with {% data variables.product.prodname_ghe_server %} 3.5, {% data variables.product.company_short %}'s internal testing uses 3rd generation CPUs to better reflect a typical customer configuration. This change in CPU represents a small portion of the changes to performance targets in this version of {% data variables.product.prodname_ghe_server %}. +{% endnote %} +{%- endif %} -如果您计划为现有实例的用户启用 {% data variables.product.prodname_actions %},请查看用户的活动级别和实例上的自动化,并确保已为用户预配足够的 CPU 和内存。 有关监视 {% data variables.product.prodname_ghe_server %} 的容量和性能的详细信息,请参阅“[监视设备](/admin/enterprise-management/monitoring-your-appliance)”。 +If you plan to enable {% data variables.product.prodname_actions %} for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. For more information about monitoring the capacity and performance of {% data variables.product.prodname_ghe_server %}, see "[Monitoring your appliance](/admin/enterprise-management/monitoring-your-appliance)." -有关 {% data variables.product.product_location %} 的最低硬件要求的更多信息,请参阅实例平台的硬件考虑因素。 +For more information about minimum hardware requirements for {% data variables.location.product_location %}, 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) @@ -126,66 +121,66 @@ ms.locfileid: '147580573' {% ifversion ghes > 3.4 %} -(可选)可以通过为 {% data variables.product.prodname_actions %} 配置速率限制来限制对 {% data variables.product.product_location %} 的资源消耗。 有关详细信息,请参阅“[配置速率限制](/admin/configuration/configuring-your-enterprise/configuring-rate-limits#configuring-rate-limits-for-github-actions)”。 +Optionally, you can limit resource consumption on {% data variables.location.product_location %} by configuring a rate limit for {% data variables.product.prodname_actions %}. For more information, see "[Configuring rate limits](/admin/configuration/configuring-your-enterprise/configuring-rate-limits#configuring-rate-limits-for-github-actions)." {% endif %} -## 外部存储要求 +## External storage requirements -要在 {% data variables.product.prodname_ghe_server %} 上启用 {% data variables.product.prodname_actions %},您必须有权访问外部 Blob 存储。 +To enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}, you must have access to external blob storage. -{% data variables.product.prodname_actions %} 使用 Blob 存储来存储工作流运行生成的数据,如工作流日志{% ifversion actions-caching %}、缓存{% endif %} 和用户上传的生成工件。 所需存储量取决于您使用 {% data variables.product.prodname_actions %} 的情况。 仅支持单个外部存储配置,不能同时使用多个存储提供程序。 +{% data variables.product.prodname_actions %} uses blob storage to store data generated by workflow runs, such as workflow logs{% ifversion actions-caching %}, caches,{% endif %} and user-uploaded build artifacts. The amount of storage required depends on your usage of {% data variables.product.prodname_actions %}. Only a single external storage configuration is supported, and you can't use multiple storage providers at the same time. -{% data variables.product.prodname_actions %} 支持以下存储提供商: +{% data variables.product.prodname_actions %} supports these storage providers: -* Azure Blob 存储 +* Azure Blob storage * Amazon S3 -* S3 兼容的 MinIO Gateway for NAS +* S3-compatible MinIO Gateway for NAS {% note %} -注意:只有这些是 {% data variables.product.company_short %} 支持并可以提供帮助的存储提供程序。 由于 S3 API 的差异,其他 S3 API 兼容的存储提供程序难以正常工作。 [联系我们](https://support.github.com/contact)以请求支持额外的存储提供程序。 +**Note:** These are the only storage providers that {% data variables.product.company_short %} supports and can provide assistance with. Other S3 API-compatible storage providers are unlikely to work due to differences from the S3 API. [Contact us](https://support.github.com/contact) to request support for additional storage providers. {% endnote %} {% data reusables.actions.minio-gateways-removal %} -在启用 {% data variables.product.prodname_actions %} 之前,可使用 `ghe-actions-precheck` 实用程序从管理 shell 测试存储配置。 有关详细信息,请参阅“[命令行实用程序](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-actions-check)”和“[访问管理 shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)”。 +Before you enable {% data variables.product.prodname_actions %}, you can test your storage configuration from the administrative shell with the `ghe-actions-precheck` utility. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-actions-check)" and "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." -## 网络注意事项 +## Networking considerations -{% data reusables.actions.proxy-considerations %} 有关将代理与 {% data variables.product.prodname_ghe_server %} 配合使用的详细信息,请参阅“[配置出站 Web 代理服务器](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)”。 +{% data reusables.actions.proxy-considerations %} For more information about using a proxy with {% data variables.product.prodname_ghe_server %}, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)." {% ifversion ghes %} -## 使用您的存储提供程序启用 {% data variables.product.prodname_actions %} +## Enabling {% data variables.product.prodname_actions %} with your storage provider -请按照以下过程之一使用所选存储提供程序启用 {% data variables.product.prodname_actions %}: +Follow one of the procedures below to enable {% data variables.product.prodname_actions %} with your chosen storage provider: -* [使用 Azure Blob 存储启用 GitHub Actions](/admin/github-actions/enabling-github-actions-with-azure-blob-storage) -* [使用 Amazon S3 存储启用 GitHub Actions](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage) -* [使用 MinIO Gateway for NAS 存储启用 GitHub Actions](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage) +* [Enabling GitHub Actions with Azure Blob storage](/admin/github-actions/enabling-github-actions-with-azure-blob-storage) +* [Enabling GitHub Actions with Amazon S3 storage](/admin/github-actions/enabling-github-actions-with-amazon-s3-storage) +* [Enabling GitHub Actions with MinIO Gateway for NAS storage](/admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage) -## 管理企业中 {% data variables.product.prodname_actions %} 的访问权限 +## Managing access permissions for {% data variables.product.prodname_actions %} in your enterprise -您可以使用策略来管理 {% data variables.product.prodname_actions %} 的访问。 有关详细信息,请参阅“[为企业强制实施 GitHub Actions 策略](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)”。 +You can use policies to manage access to {% data variables.product.prodname_actions %}. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." -## 添加自托管的运行器 +## Adding self-hosted runners {% data reusables.actions.enterprise-github-hosted-runners %} -要运行 {% data variables.product.prodname_actions %} 工作流程,您需要添加自托管运行器。 您可以在企业、组织或仓库级别添加自托管运行器。 有关详细信息,请参阅“[添加自托管运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners)”。 +To run {% data variables.product.prodname_actions %} workflows, you need to add self-hosted runners. You can add self-hosted runners at the enterprise, organization, or repository levels. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." -## 管理哪些操作可用于您的企业 +## Managing which actions can be used in your enterprise -您可以控制允许用户在企业中使用哪些操作。 这包括设置 {% data variables.product.prodname_github_connect %} 以自动访问来自 {% data variables.product.prodname_dotcom_the_website %} 的操作,或手动同步来自 {% data variables.product.prodname_dotcom_the_website %} 的操作。 +You can control which actions your users are allowed to use in your enterprise. This includes setting up {% data variables.product.prodname_github_connect %} for automatic access to actions from {% data variables.product.prodname_dotcom_the_website %}, or manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}. -有关详细信息,请参阅“[关于在企业中使用操作](/admin/github-actions/about-using-actions-in-your-enterprise)”。 +For more information, see "[About using actions in your enterprise](/admin/github-actions/about-using-actions-in-your-enterprise)." {% data reusables.actions.general-security-hardening %} {% endif %} -## 保留名称 +## Reserved names -为企业启用 {% data variables.product.prodname_actions %} 时,会创建两个组织:`github` 和 `actions`。 如果企业已使用 `github` 组织名称,则将改用 `github-org`(如果 `github-org` 也在使用中,则改用 `github-github-org`)。 如果企业已使用 `actions` 组织名称,则将改用 `github-actions`(如果 `github-actions` 也在使用中,则改用 `github-actions-org`)。 启用操作后,您将无法再使用这些名称。 +When you enable {% data variables.product.prodname_actions %} for your enterprise, two organizations are created: `github` and `actions`. If your enterprise already uses the `github` organization name, `github-org` (or `github-github-org` if `github-org` is also in use) will be used instead. If your enterprise already uses the `actions` organization name, `github-actions` (or `github-actions-org` if `github-actions` is also in use) will be used instead. Once actions is enabled, you won't be able to use these names anymore. diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md index 2e27bf07bd..8fc4c6c049 100644 --- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md @@ -18,7 +18,7 @@ topics: {% data reusables.actions.about-actions-for-enterprises %} For more information, see "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)." -With {% data variables.product.prodname_actions %}, developers can write and combine individual tasks called actions to create custom workflows. {% ifversion ghes or ghae %}To enable {% data variables.product.prodname_actions %} for {% ifversion ghae %}your enterprise{% elsif ghes %} {% data variables.product.product_location %}{% endif %}, you must host at least one machine to execute jobs.{% endif %} {% ifversion ghec %}You can host your own runner machine to execute jobs, and this{% elsif ghes or ghae %}This{% endif %} machine is called a self-hosted runner. {% data reusables.actions.self-hosted-runner-locations %} {% data reusables.actions.self-hosted-runner-architecture %} {% ifversion ghec %}All{% elsif ghes or ghae %}Self-hosted{% endif %} runners can run Linux, Windows, or macOS. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." +With {% data variables.product.prodname_actions %}, developers can write and combine individual tasks called actions to create custom workflows. {% ifversion ghes or ghae %}To enable {% data variables.product.prodname_actions %} for {% ifversion ghae %}your enterprise{% elsif ghes %} {% data variables.location.product_location %}{% endif %}, you must host at least one machine to execute jobs.{% endif %} {% ifversion ghec %}You can host your own runner machine to execute jobs, and this{% elsif ghes or ghae %}This{% endif %} machine is called a self-hosted runner. {% data reusables.actions.self-hosted-runner-locations %} {% data reusables.actions.self-hosted-runner-architecture %} {% ifversion ghec %}All{% elsif ghes or ghae %}Self-hosted{% endif %} runners can run Linux, Windows, or macOS. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." {% ifversion ghec %} @@ -38,7 +38,7 @@ This guide shows you how to apply a centralized management approach to self-host You'll also find additional information about how to monitor and secure your self-hosted runners,{% ifversion ghes or ghae %} how to access actions from {% data variables.product.prodname_dotcom_the_website %},{% endif %} and how to customize the software on your runner machines. -After you finish the guide, {% ifversion ghec or ghae %}members of your enterprise{% elsif ghes %}users of {% data variables.product.product_location %}{% endif %} will be able to run workflow jobs from {% data variables.product.prodname_actions %} on a self-hosted runner machine. +After you finish the guide, {% ifversion ghec or ghae %}members of your enterprise{% elsif ghes %}users of {% data variables.location.product_location %}{% endif %} will be able to run workflow jobs from {% data variables.product.prodname_actions %} on a self-hosted runner machine. ## Prerequisites @@ -48,7 +48,7 @@ After you finish the guide, {% ifversion ghec or ghae %}members of your enterpri ## 1. Configure policies for {% data variables.product.prodname_actions %} -First, enable {% data variables.product.prodname_actions %} for all organizations, and configure a policy to restrict the actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} that can run {% ifversion ghec or ghae%}within your enterprise on {% data variables.product.product_name %}{% elsif ghes %}on {% data variables.product.product_location %}{% endif %}. Optionally, organization owners can further restrict these policies for each organization. +First, enable {% data variables.product.prodname_actions %} for all organizations, and configure a policy to restrict the actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} that can run {% ifversion ghec or ghae%}within your enterprise on {% data variables.product.product_name %}{% elsif ghes %}on {% data variables.location.product_location %}{% endif %}. Optionally, organization owners can further restrict these policies for each organization. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} @@ -65,11 +65,11 @@ First, enable {% data variables.product.prodname_actions %} for all organization {%- endif %} 1. Click **Save**. -You can configure additional policies to restrict the actions available to {% ifversion ghec or ghae %}enterprise members{% elsif ghes %}users of {% data variables.product.product_location %}{% endif %}. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#allowing-select-actions-to-run)." +You can configure additional policies to restrict the actions available to {% ifversion ghec or ghae %}enterprise members{% elsif ghes %}users of {% data variables.location.product_location %}{% endif %}. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#allowing-select-actions-to-run)." ## 2. Deploy the self-hosted runner for your enterprise -Next, add a self-hosted runner to your enterprise. {% data variables.product.product_name %} will guide you through installation of the necessary software on the runner machine. After you deploy the runner, you can verify connectivity between the runner machine and {%ifversion ghec or ghae %}your enterprise{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. +Next, add a self-hosted runner to your enterprise. {% data variables.product.product_name %} will guide you through installation of the necessary software on the runner machine. After you deploy the runner, you can verify connectivity between the runner machine and {%ifversion ghec or ghae %}your enterprise{% elsif ghes %}{% data variables.location.product_location %}{% endif %}. ### Adding the self-hosted runner @@ -126,7 +126,7 @@ For more information, see "[Managing access to self-hosted runners using groups] ## 5. Automatically scale your self-hosted runners -Optionally, you can build custom tooling to automatically scale the self-hosted runners for {% ifversion ghec or ghae %}your enterprise{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. For example, your tooling can respond to webhook events from {% data variables.product.product_location %} to automatically scale a cluster of runner machines. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)." +Optionally, you can build custom tooling to automatically scale the self-hosted runners for {% ifversion ghec or ghae %}your enterprise{% elsif ghes %}{% data variables.location.product_location %}{% endif %}. For example, your tooling can respond to webhook events from {% data variables.location.product_location %} to automatically scale a cluster of runner machines. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)." {% endif %} diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md index d8de55e3fa..8ac0a99e29 100644 --- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md +++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md @@ -91,7 +91,7 @@ You should plan for how you'll manage the resources required to use {% data vari {% ifversion ghes %} ### Hardware requirements -You may need to upgrade the CPU and memory resources for {% data variables.product.product_location %} to handle the load from {% data variables.product.prodname_actions %} without causing performance loss. 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-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-requirements)." +You may need to upgrade the CPU and memory resources for {% data variables.location.product_location %} to handle the load from {% data variables.product.prodname_actions %} without causing performance loss. 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-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-requirements)." {% endif %} ### Runners diff --git a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md index 9445d42e19..8aa85ea18f 100644 --- a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md +++ b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: 关于在企业中使用操作 -intro: '{% data variables.product.product_name %} 包含了大多数 {% data variables.product.prodname_dotcom %} 编写的操作,并且有选项允许访问来自 {% data variables.product.prodname_dotcom_the_website %} 和 {% data variables.product.prodname_marketplace %} 的其他操作。' +title: About using actions in your enterprise +intro: '{% data variables.product.product_name %} includes most {% data variables.product.prodname_dotcom %}-authored actions, and has options for enabling access to other actions from {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_marketplace %}.' redirect_from: - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server - /admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server @@ -14,63 +14,61 @@ topics: - Actions - Enterprise shortTitle: About actions in your enterprise -ms.openlocfilehash: 2e18b932548aa7ad9b65c090b6a5418762bcb501 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146139006' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## 关于 {% data variables.product.product_name %} 中的操作 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} -{% data variables.product.prodname_actions %} 工作流可使用操作,它们是一些单独的任务,可以组合这些操作以创建作业并自定义工作流。 您可以创建自己的操作,或者使用和自定义 {% data variables.product.prodname_dotcom %} 社区分享的操作。 +## About actions on {% data variables.product.product_name %} -{% data reusables.actions.enterprise-no-internet-actions %} 您可以限制开发人员使用存储在 {% data variables.product.product_location %} 上的操作,其中包括大多数官方 {% data variables.product.company_short %} 创作的操作,以及开发人员创建的任何操作。 或者,为了让您的开发人员从行业领导者和开源社区构建的完整操作生态系统中受益,您可以配置对 {% data variables.product.prodname_dotcom_the_website %} 的其他操作的访问。 +{% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the {% data variables.product.prodname_dotcom %} community. -我们建议允许自动访问 {% data variables.product.prodname_dotcom_the_website %} 的所有操作。 {% ifversion ghes %}但是,这需要 {% data variables.product.product_name %} {% data variables.product.prodname_dotcom_the_website %} 建立出站连接。 如果您不想允许这些连接,或者{% else %}如果{% endif %} 您希望更好地控制在企业中使用哪些操作,则可以手动同步 {% data variables.product.prodname_dotcom_the_website %} 中的特定操作。 +{% data reusables.actions.enterprise-no-internet-actions %} You can restrict your developers to using actions that are stored on {% data variables.location.product_location %}, which includes most official {% data variables.product.company_short %}-authored actions, as well as any actions your developers create. Alternatively, to allow your developers to benefit from the full ecosystem of actions built by industry leaders and the open source community, you can configure access to other actions from {% data variables.product.prodname_dotcom_the_website %}. -## 与您的企业实例捆绑的正式操作 +We recommend allowing automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %}. {% ifversion ghes %}However, this does require {% data variables.product.product_name %} to make outbound connections to {% data variables.product.prodname_dotcom_the_website %}. If you don't want to allow these connections, or{% else %}If{% endif %} you want to have greater control over which actions are used on your enterprise, you can manually sync specific actions from {% data variables.product.prodname_dotcom_the_website %}. + +## Official actions bundled with your enterprise instance {% data reusables.actions.actions-bundled-with-ghes %} -捆绑的官方操作包括以下内容等。 +The bundled official actions include the following, among others. - `actions/checkout` - `actions/upload-artifact` - `actions/download-artifact` - `actions/labeler` -- 各种 `actions/setup-` 操作 +- Various `actions/setup-` actions -若要查看企业实例中包含的所有官方操作,请浏览到实例上的 `actions` 组织:https://HOSTNAME/actions。 +To see all the official actions included on your enterprise instance, browse to the `actions` organization on your instance: https://HOSTNAME/actions. -{% data variables.product.product_location %} 和 {% data variables.product.prodname_dotcom_the_website %} 之间不需要连接即可使用这些操作。 +There is no connection required between {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %} to use these actions. -每个操作都是 `actions` 组织中的存储库,每个操作存储库都包含工作流可以用于引用操作的必要标记、分支和提交 SHA。 有关如何更新捆绑官方操作的信息,请参阅“[使用最新版本的官方捆绑操作](/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions)。” +Each action is a repository in the `actions` organization, and each action repository includes the necessary tags, branches, and commit SHAs that your workflows can use to reference the action. For information on how to update the bundled official actions, see "[Using the latest version of the official bundled actions](/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions)." {% note %} -**注意:** -- 在包含自托管运行器的 {% data variables.product.product_name %} 上使用设置操作(例如 `actions/setup-LANGUAGE`)时,可能需要在无法访问 Internet 的运行器上设置工具缓存。 有关详细信息,请参阅“[在无法访问 Internet 的自托管运行器上设置工具缓存](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)。” -- 当 {% data variables.product.product_name %} 更新时,捆绑的操作会自动替换为升级包中的默认版本。 +**Notes:** +- When using setup actions (such as `actions/setup-LANGUAGE`) on {% data variables.product.product_name %} with self-hosted runners, you might need to set up the tools cache on runners that do not have internet access. For more information, see "[Setting up the tool cache on self-hosted runners without internet access](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)." +- When {% data variables.product.product_name %} is updated, bundled actions are automatically replaced with default versions in the upgrade package. {% endnote %} -## 配置对 {% data variables.product.prodname_dotcom_the_website %} 上操作的访问权限 +## Configuring access to actions on {% data variables.product.prodname_dotcom_the_website %} {% data reusables.actions.access-actions-on-dotcom %} -推荐的方法是启用自动访问来自 {% data variables.product.prodname_dotcom_the_website %} 的所有操作。 通过使用 {% data variables.product.prodname_github_connect %} 将 {% data variables.product.product_name %} 与 {% data variables.product.prodname_ghe_cloud %} 集成可实现这一点。 有关详细信息,请参阅“[使用 {% data variables.product.prodname_github_connect %} 启用对 {% data variables.product.prodname_dotcom_the_website %} 操作的自动访问](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)”。 +The recommended approach is to enable automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %}. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". -{% ifversion ghes %} {% note %} +{% ifversion ghes %} +{% note %} -注意:在配置对 {% data variables.product.prodname_dotcom_the_website %} 的操作的访问之前,必须配置 {% data variables.product.product_location %} 以使用 {% data variables.product.prodname_actions %}。 有关详细信息,请参阅“[适用于 GitHub Enterprise Server 的 {% data variables.product.prodname_actions %} 的使用入门](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)。” +**Note:** Before you can configure access to actions on {% data variables.product.prodname_dotcom_the_website %}, you must configure {% data variables.location.product_location %} to use {% data variables.product.prodname_actions %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)." -{% endnote %} {% endif %} +{% endnote %} +{% endif %} {% data reusables.actions.self-hosted-runner-networking-to-dotcom %} {% data reusables.actions.enterprise-limit-actions-use %} -或者,如果希望在企业中更严格地控制允许的操作,或者不希望允许与 {% data variables.product.prodname_dotcom_the_website %} 的出站连接,可以使用 `actions-sync` 工具手动将操作下载并同步到企业实例上。 有关详细信息,请参阅“[从 {% data variables.product.prodname_dotcom_the_website %} 手动同步操作](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)。” +Alternatively, if you want stricter control over which actions are allowed in your enterprise, or you do not want to allow outbound connections to {% data variables.product.prodname_dotcom_the_website %}, you can manually download and sync actions onto your enterprise instance using the `actions-sync` tool. For more information, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)." diff --git a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index 8783fb3b48..709907e154 100644 --- a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -1,6 +1,6 @@ --- -title: 使用 GitHub Connect 启用对 GitHub.com 操作的自动访问 -intro: '要允许企业中的 {% data variables.product.prodname_actions %} 使用来自 {% data variables.product.prodname_dotcom_the_website %} 的操作,您可以将企业实例连接到 {% data variables.product.prodname_ghe_cloud %}。' +title: Enabling automatic access to GitHub.com actions using GitHub Connect +intro: 'To allow {% data variables.product.prodname_actions %} in your enterprise to use actions from {% data variables.product.prodname_dotcom_the_website %}, you can connect your enterprise instance to {% data variables.product.prodname_ghe_cloud %}.' permissions: 'Enterprise owners can enable access to all {% data variables.product.prodname_dotcom_the_website %} actions.' redirect_from: - /enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect @@ -14,60 +14,57 @@ topics: - Enterprise - GitHub Connect shortTitle: Use GitHub Connect for actions -ms.openlocfilehash: 85942d047f8bce5c2f58e8f92148b5fb85f5d871 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145099990' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## 关于自动访问 {% data variables.product.prodname_dotcom_the_website %} 操作 +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} -默认情况下,{% data variables.product.product_name %} 上的 {% data variables.product.prodname_actions %} 工作流不能直接使用 {% data variables.product.prodname_dotcom_the_website %} 或 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) 中的操作。 若要使 {% data variables.product.prodname_dotcom_the_website %} 中的所有操作在企业实例上可用,可以使用 {% data variables.product.prodname_github_connect %} 将 {% data variables.product.product_name %} 与 {% data variables.product.prodname_ghe_cloud %} 集成。 +## About automatic access to {% data variables.product.prodname_dotcom_the_website %} actions + +By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.product_name %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can use {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. {% data reusables.actions.self-hosted-runner-networking-to-dotcom %} -或者,如果想要更严格地控制企业中允许哪些操作,则可以使用 `actions-sync` 工具手动下载操作并将其同步到企业实例中。 有关详细信息,请参阅“[从 {% data variables.product.prodname_dotcom_the_website %} 手动同步操作](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)”。 +Alternatively, if you want stricter control over which actions are allowed in your enterprise, you can manually download and sync actions onto your enterprise instance using the `actions-sync` tool. For more information, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)." -## 关于使用 {% data variables.product.prodname_github_connect %} 的操作的解决方案 +## About resolution for actions using {% data variables.product.prodname_github_connect %} {% data reusables.actions.github-connect-resolution %} -如果用户在企业中创建的组织和仓库与 {% data variables.product.prodname_dotcom_the_website %} 上的组织和仓库名称匹配,则将使用企业上的仓库代替 {% data variables.product.prodname_dotcom_the_website %} 仓库。 {% ifversion ghes < 3.3 or ghae %}恶意用户可以利用此行为将代码作为工作流的一部分运行{% else %}有关详细信息,请参阅“[自动停用在 {% data variables.product.prodname_dotcom_the_website%} 上访问的操作的命名空间](#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)”。 +If a user has already created an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom_the_website %}, the repository on your enterprise will be used instead of the {% data variables.product.prodname_dotcom_the_website %} repository. {% ifversion ghes < 3.3 or ghae %}A malicious user could take advantage of this behavior to run code as part of a workflow{% else %}For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." {% endif %} -## 启用对所有 {% data variables.product.prodname_dotcom_the_website %} 操作的自动访问 +## Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions -在为企业启用对 {% data variables.product.prodname_dotcom_the_website %} 的所有操作的访问权限之前,必须{% ifversion ghes %}: -- 配置 {% data variables.product.product_location %} 使用 {% data variables.product.prodname_actions %}。 有关详细信息,请参阅“[适用于 GitHub Enterprise Server 的 {% data variables.product.prodname_actions %} 入门](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)”。 -- 启用{% else %} 启用{% endif %} {% data variables.product.prodname_github_connect %}。 有关详细信息,请参阅“[管理 {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)”。 +Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} for your enterprise, you must{% ifversion ghes %}: +- Configure {% data variables.location.product_location %} to use {% data variables.product.prodname_actions %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)." +- Enable{% else %} enable{% endif %} {% data variables.product.prodname_github_connect %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)." -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %} -1. 在“用户在工作流运行中可以使用 GitHub.com 上的操作”下,使用下拉菜单选择“已启用”。 - ![工作流运行中用于访问 GitHub.com 上操作的下拉菜单](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png) +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.github-connect-tab %} +1. Under "Users can utilize actions from GitHub.com in workflow runs", use the drop-down menu and select **Enabled**. + ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png) 1. {% data reusables.actions.enterprise-limit-actions-use %} {% ifversion ghes > 3.2 or ghae %} -## 自动停用在 {% data variables.product.prodname_dotcom_the_website %} 上访问的操作的命名空间 +## Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %} -启用 {% data variables.product.prodname_github_connect %} 时,用户不会看到现有工作流程行为的变化,因为 {% data variables.product.prodname_actions %} 在回退到 {% data variables.product.prodname_dotcom_the_website%} 之前会搜索 {% data variables.product.product_location %} 上的每个操作。 这可确保企业创建的任何自定义版本的操作优先于 {% data variables.product.prodname_dotcom_the_website%} 上的对应版本。 +When you enable {% data variables.product.prodname_github_connect %}, users see no change in behavior for existing workflows because {% data variables.product.prodname_actions %} searches {% data variables.location.product_location %} for each action before falling back to {% data variables.product.prodname_dotcom_the_website%}. This ensures that any custom versions of actions your enterprise has created are used in preference to their counterparts on {% data variables.product.prodname_dotcom_the_website%}. -自动停用在 {% data variables.product.prodname_dotcom_the_website %} 上访问的操作的命名空间,可阻止具有 {% data variables.product.product_location %} 访问权限的恶意用户进行中间人攻击的可能性。 首次使用对 {% data variables.product.prodname_dotcom_the_website %} 执行的操作时,该命名空间将在 {% data variables.product.product_location %} 中停用。 这将阻止任何用户在企业中创建与 {% data variables.product.prodname_dotcom_the_website %} 上的组织和存储库名称匹配的组织和存储库。 这可确保在工作流程运行时始终运行预期的操作。 +Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %} blocks the potential for a man-in-the-middle attack by a malicious user with access to {% data variables.location.product_location %}. When an action on {% data variables.product.prodname_dotcom_the_website %} is used for the first time, that namespace is retired in {% data variables.location.product_location %}. This blocks any user creating an organization and repository in your enterprise that matches that organization and repository name on {% data variables.product.prodname_dotcom_the_website %}. This ensures that when a workflow runs, the intended action is always run. -使用 {% data variables.product.prodname_dotcom_the_website %} 中的操作后,如果要在 {% data variables.product.product_location %} 中创建具有相同名称的操作,首先需要使该组织和存储库的命名空间可用。 +After using an action from {% data variables.product.prodname_dotcom_the_website %}, if you want to create an action in {% data variables.location.product_location %} with the same name, first you need to make the namespace for that organization and repository available. {% data reusables.enterprise_site_admin_settings.access-settings %} -2. 在左侧边栏中的“站点管理员”下,单击“已停用的命名空间” 。 -3. 找到要在 {% data variables.product.product_location %} 中使用的命名空间,然后单击“取消停用”。 - ![取消停用命名空间](/assets/images/enterprise/site-admin-settings/unretire-namespace.png) -4. 转到相关组织并创建新的存储库。 +2. In the left sidebar, under **Site admin** click **Retired namespaces**. +3. Locate the namespace that you want use in {% data variables.location.product_location %} and click **Unretire**. + ![Unretire namespace](/assets/images/enterprise/site-admin-settings/unretire-namespace.png) +4. Go to the relevant organization and create a new repository. {% tip %} - **提示:** 取消停用命名空间时,请务必尽快使用该名称创建新存储库。 如果在创建本地存储库之前,工作流程在 {% data variables.product.prodname_dotcom_the_website %} 上调用关联的操作,则命名空间将再次停用。 对于频繁运行的工作流程中使用的操作,您可能会发现命名空间在您有时间创建本地存储库之前再次停用。 在这种情况下,您可以暂时禁用相关工作流程,直到创建新存储库。 + **Tip:** When you unretire a namespace, always create the new repository with that name as soon as possible. If a workflow calls the associated action on {% data variables.product.prodname_dotcom_the_website %} before you create the local repository, the namespace will be retired again. For actions used in workflows that run frequently, you may find that a namespace is retired again before you have time to create the local repository. In this case, you can temporarily disable the relevant workflows until you have created the new repository. {% endtip %} diff --git a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md index 9b70f0bc9b..e44a1c5cf1 100644 --- a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md +++ b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md @@ -1,6 +1,6 @@ --- -title: 手动从 GitHub.com 同步操作 -intro: '对于需要访问 {% data variables.product.prodname_dotcom_the_website %} 上操作的用户,您可以将特定操作同步到企业。' +title: Manually syncing actions from GitHub.com +intro: 'For users that need access to actions from {% data variables.product.prodname_dotcom_the_website %}, you can sync specific actions to your enterprise.' redirect_from: - /enterprise/admin/github-actions/manually-syncing-actions-from-githubcom - /admin/github-actions/manually-syncing-actions-from-githubcom @@ -12,53 +12,51 @@ topics: - Actions - Enterprise shortTitle: Manually sync actions -ms.openlocfilehash: f4116663e510da9b7551e4a9050dd4ba838ed7c6 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145099988' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.enterprise-no-internet-actions %} {% ifversion ghes or ghae %} -推荐的允许从 {% data variables.product.prodname_dotcom_the_website %} 访问操作的方法是启用自动访问所有操作。 为此,可使用 {% data variables.product.prodname_github_connect %} 将 {% data variables.product.product_name %} 与 {% data variables.product.prodname_ghe_cloud %} 集成。 有关详细信息,请参阅“[使用 {% data variables.product.prodname_github_connect %} 启用对 {% data variables.product.prodname_dotcom_the_website %} 操作的自动访问](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)。” +The recommended approach of enabling access to actions from {% data variables.product.prodname_dotcom_the_website %} is to enable automatic access to all actions. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." -但是,如果想更严格地控制企业中允许的操作,{% else %}你{% endif %}可以按照本指南使用 {% data variables.product.company_short %} 的开源 [`actions-sync`](https://github.com/actions/actions-sync) 工具将各个操作存储库从 {% data variables.product.prodname_dotcom_the_website %} 同步到企业。 +However, if you want stricter control over which actions are allowed in your enterprise, you{% else %}You{% endif %} can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise. -## 关于 `actions-sync` 工具 +## About the `actions-sync` tool -`actions-sync` 工具必须在可以访问 {% data variables.product.prodname_dotcom_the_website %} API 和 {% data variables.product.product_name %} 实例的 API 的计算机上运行。 计算机不需要同时连接到两者。 +The `actions-sync` tool must be run on a machine that can access the {% data variables.product.prodname_dotcom_the_website %} API and your {% data variables.product.product_name %} instance's API. The machine doesn't need to be connected to both at the same time. -如果计算机可以同时访问这两个系统,则可以使用单一 `actions-sync sync` 命令进行同步。 如果一次只能访问一个系统,可以使用 `actions-sync pull` 和 `push` 命令。 +If your machine has access to both systems at the same time, you can do the sync with a single `actions-sync sync` command. If you can only access one system at a time, you can use the `actions-sync pull` and `push` commands. -`actions-sync` 工具只能从存储在公共存储库中的 {% data variables.product.prodname_dotcom_the_website %} 下载操作。 +The `actions-sync` tool can only download actions from {% data variables.product.prodname_dotcom_the_website %} that are stored in public repositories. -{% ifversion ghes > 3.2 or ghae %} {% note %} +{% ifversion ghes > 3.2 or ghae %} +{% note %} -注意:`actions-sync` 工具适用于未启用 {% data variables.product.prodname_github_connect %} 的系统。 如果在启用了 {% data variables.product.prodname_github_connect %} 的系统上运行该工具,则可能会看到错误 `The repository has been retired and cannot be reused`。 这表示工作流程已直接在 {% data variables.product.prodname_dotcom_the_website %} 上使用了该操作,并且命名空间已在 {% data variables.product.product_location %} 上停用。 有关详细信息,请参阅“[自动停用在 {% data variables.product.prodname_dotcom_the_website%} 上访问的操作的命名空间](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)”。 +**Note:** The `actions-sync` tool is intended for use in systems where {% data variables.product.prodname_github_connect %} is not enabled. If you run the tool on a system with {% data variables.product.prodname_github_connect %} enabled, you may see the error `The repository has been retired and cannot be reused`. This indicates that a workflow has used that action directly on {% data variables.product.prodname_dotcom_the_website %} and the namespace is retired on {% data variables.location.product_location %}. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." -{% endnote %} {% endif %} +{% endnote %} +{% endif %} -## 先决条件 +## Prerequisites -* 在使用 `actions-sync` 工具之前,必须确保所有目标组织已经存在于企业中。 以下示例演示如何将操作同步到名为 `synced-actions` 的组织。 有关详细信息,请参阅“[从头开始创建新组织](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)”。 -* 您必须在企业上创建可以创建并写入目标组织中的仓库的个人访问令牌 (PAT)。 有关详细信息,请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。{% ifversion ghes %} -* 如果想同步 {% data variables.product.product_location %} 上 `actions` 组织中的捆绑操作,你必须是 `actions` 组织的所有者。 +* Before using the `actions-sync` tool, you must ensure that all destination organizations already exist in your enterprise. The following example demonstrates how to sync actions to an organization named `synced-actions`. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." +* You must create a {% data variables.product.pat_generic %} on your enterprise that can create and write to repositories in the destination organizations. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."{% ifversion ghes %} +* If you want to sync the bundled actions in the `actions` organization on {% data variables.location.product_location %}, you must be an owner of the `actions` organization. {% note %} - 注意:默认情况下,即使站点管理员也不是捆绑的 `actions` 组织的所有者。 + **Note:** By default, even site administrators are not owners of the bundled `actions` organization. {% endnote %} - 站点管理员可以在管理 shell 中使用 `ghe-org-admin-promote` 命令将用户升级为捆绑的 `actions` 组织的所有者。 有关详细信息,请参阅“[访问管理 shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)”和“[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)”。 + Site administrators can use the `ghe-org-admin-promote` command in the administrative shell to promote a user to be an owner of the bundled `actions` organization. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)." ```shell - ghe-org-admin-promote -u USERNAME -o actions + ghe-org-admin-promote -u USERNAME -o actions ```{% endif %} ## Example: Using the `actions-sync` tool @@ -83,20 +81,20 @@ This example demonstrates using the `actions-sync` tool to sync an individual ac --repo-name "actions/stale:synced-actions/actions-stale" ``` - 上述命令使用以下参数: + The above command uses the following arguments: - * `--cache-dir`:运行命令的计算机上的缓存目录。 - * `--destination-token`:目标企业实例的个人访问令牌。 - * `--destination-url`:目标企业实例的 URL。 - * `--repo-name`:要同步的操作存储库。其采用格式 `owner/repository:destination_owner/destination_repository`。 + * `--cache-dir`: The cache directory on the machine running the command. + * `--destination-token`: A {% data variables.product.pat_generic %} for the destination enterprise instance. + * `--destination-url`: The URL of the destination enterprise instance. + * `--repo-name`: The action repository to sync. This takes the format of `owner/repository:destination_owner/destination_repository`. - * 上面的示例将 [`actions/stale`](https://github.com/actions/stale) 存储库同步到目标企业实例上的 `synced-actions/actions-stale` 存储库。 在运行上述命令之前,必须在企业中创建名为 `synced-actions` 的组织。 - * 如果省略 `:destination_owner/destination_repository`,工具将使用企业的原始所有者和存储库名称。 在运行命令之前,必须在企业中创建一个与操作的所有者名称匹配的新组织。 考虑使用一个中心组织来存储企业中同步的操作,因为这样在同步来自不同所有者的操作时,将无需创建多个新的组织。 - * 可以通过将 `--repo-name` 参数替换为 `--repo-name-list` 或 `--repo-name-list-file` 来同步多个操作。 有关详细信息,请参阅 [`actions-sync` README](https://github.com/actions/actions-sync#actions-sync)。 -1. 在企业中创建操作仓库后,企业中的人员可以使用目标仓库在其工作流程中引用操作。 对于上面显示的示例操作: + * The above example syncs the [`actions/stale`](https://github.com/actions/stale) repository to the `synced-actions/actions-stale` repository on the destination enterprise instance. You must create the organization named `synced-actions` in your enterprise before running the above command. + * If you omit `:destination_owner/destination_repository`, the tool uses the original owner and repository name for your enterprise. Before running the command, you must create a new organization in your enterprise that matches the owner name of the action. Consider using a central organization to store the synced actions in your enterprise, as this means you will not need to create multiple new organizations if you sync actions from different owners. + * You can sync multiple actions by replacing the `--repo-name` parameter with `--repo-name-list` or `--repo-name-list-file`. For more information, see the [`actions-sync` README](https://github.com/actions/actions-sync#actions-sync). +1. After the action repository is created in your enterprise, people in your enterprise can use the destination repository to reference the action in their workflows. For the example action shown above: ```yaml uses: synced-actions/actions-stale@v1 ``` - 有关详细信息,请参阅“[GitHub Actions 的工作流语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsuses)”。 + For more information, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsuses)." diff --git a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md index bc3f23633f..c75e4e6eef 100644 --- a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md +++ b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md @@ -1,6 +1,6 @@ --- -title: 使用官方捆绑操作的最新版本 -intro: '您可以更新与企业捆绑的操作,或直接从 {% data variables.product.prodname_dotcom_the_website %} 使用操作。' +title: Using the latest version of the official bundled actions +intro: 'You can update the actions that are bundled with your enterprise, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.' versions: ghes: '*' ghae: '*' @@ -12,48 +12,45 @@ topics: redirect_from: - /admin/github-actions/using-the-latest-version-of-the-official-bundled-actions shortTitle: Use the latest bundled actions -ms.openlocfilehash: 3243199ad7f5d216a351ddc2db7a4e6afed66c9b -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145099987' --- -{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} -您的企业实例包含一些您可以在工作流程中使用的内置操作。 有关捆绑操作的详细信息,请参阅“[与你的企业实例捆绑的正式操作](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)”。 +Your enterprise instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see "[Official actions bundled with your enterprise instance](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)." -这些捆绑的操作是在 https://github.com/actions 上找到的正式操作的即时快照;因此,这些操作可能有更新的版本。 可以使用 `actions-sync` 工具更新这些操作,也可以配置 {% data variables.product.prodname_github_connect %} 以允许访问 {% data variables.product.prodname_dotcom_the_website %} 上的最新操作。 后续部分将介绍这些选项。 +These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions, so there may be newer versions of these actions available. You can use the `actions-sync` tool to update these actions, or you can configure {% data variables.product.prodname_github_connect %} to allow access to the latest actions on {% data variables.product.prodname_dotcom_the_website %}. These options are described in the following sections. -## 使用 `actions-sync` 更新捆绑的操作 +## Using `actions-sync` to update the bundled actions -若要更新捆绑操作,可以使用 `actions-sync` 工具更新快照。 有关使用 `actions-sync` 的详细信息,请参阅“[从 {% data variables.product.prodname_dotcom_the_website %} 手动同步操作](/admin/github-actions/manually-syncing-actions-from-githubcom)”。 +To update the bundled actions, you can use the `actions-sync` tool to update the snapshot. For more information on using `actions-sync`, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)." -## 使用 {% data variables.product.prodname_github_connect %} 访问最新操作 +## Using {% data variables.product.prodname_github_connect %} to access the latest actions -您可以使用 {% data variables.product.prodname_github_connect %} 允许 {% data variables.product.product_name %} 使用来自 {% data variables.product.prodname_dotcom_the_website %} 的操作。 有关详细信息,请参阅“[使用 {% data variables.product.prodname_github_connect %} 启用对 {% data variables.product.prodname_dotcom_the_website %} 操作的自动访问](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)。” +You can use {% data variables.product.prodname_github_connect %} to allow {% data variables.product.product_name %} to use actions from {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." -配置 {% data variables.product.prodname_github_connect %} 后,你可以在实例上的 `actions` 组织中删除其本地存储库,以使用最新版本的操作。 例如,如果企业实例正在使用 `actions/checkout` 操作的 `v1`,并且你需要使用企业实例上不可用的 `{% data reusables.actions.action-checkout %}`,请执行以下步骤以能够使用 {% data variables.product.prodname_dotcom_the_website %} 中的最新 `checkout` 操作: +Once {% data variables.product.prodname_github_connect %} is configured, you can use the latest version of an action by deleting its local repository in the `actions` organization on your instance. For example, if your enterprise instance is using `v1` of the `actions/checkout` action, and you need to use `{% data reusables.actions.action-checkout %}` which isn't available on your enterprise instance, perform the following steps to be able to use the latest `checkout` action from {% data variables.product.prodname_dotcom_the_website %}: -1. 从 {% data variables.product.product_name %} 上的企业所有者帐户中,导航到要从操作组织中删除的存储库(在此示例中为 `checkout`)。 -1. 默认情况下,站点管理员不是捆绑的操作组织的所有者。 若要获取删除 `checkout` 存储库所需的访问权限,必须使用站点管理工具。 在该仓库中任何页面的右上角单击 {% octicon "rocket" aria-label="The rocket ship" %}。 - ![用于访问站点管理员设置的火箭图标](/assets/images/enterprise/site-admin-settings/access-new-settings.png) -1. 单击 {% octicon "shield-lock" %}“安全性”以查看存储库的安全概述。 - ![存储库的安全标头](/assets/images/enterprise/site-admin-settings/access-repo-security-info.png) -1. 在“特权访问”下,单击“解锁”。 - ![解锁按钮](/assets/images/enterprise/site-admin-settings/unlock-priviledged-repo-access.png) -1. 在“原因”下,键入解锁存储库的原因,然后单击“解锁” 。 - ![确认对话框](/assets/images/enterprise/site-admin-settings/confirm-unlock-repo-access.png) -1. 现在,存储库已解锁,你可以离开网站管理员页面,并删除`actions` 组织中的存储库。 在页面顶部,单击存储库名称,在此示例中单击“签出”以返回到摘要页。 - ![存储库名称链接](/assets/images/enterprise/site-admin-settings/display-repository-admin-summary.png) -1. 在“存储库信息”下,单击“查看代码”以离开站点管理员页面并显示 `checkout` 存储库。 -1. 删除 `actions` 组织中的 `checkout` 存储库。 有关如何删除存储库的信息,请参阅“[删除存储库](/github/administering-a-repository/deleting-a-repository)”。 - ![查看代码链接](/assets/images/enterprise/site-admin-settings/exit-admin-page-for-repository.png) -1. 将工作流的 YAML 配置为使用 `{% data reusables.actions.action-checkout %}`。 -1. 每次运行工作流时,运行器都将使用来自 {% data variables.product.prodname_dotcom_the_website %} 的指定版本的 `actions/checkout`。 +1. From an enterprise owner account on {% data variables.product.product_name %}, navigate to the repository you want to delete from the *actions* organization (in this example `checkout`). +1. By default, site administrators are not owners of the bundled *actions* organization. To get the access required to delete the `checkout` repository, you must use the site admin tools. Click {% octicon "rocket" aria-label="The rocket ship" %} in the upper-right corner of any page in that repository. + ![Rocketship icon for accessing site admin settings](/assets/images/enterprise/site-admin-settings/access-new-settings.png) +1. Click {% octicon "shield-lock" %} **Security** to see the security overview for the repository. + ![Security header the repository](/assets/images/enterprise/site-admin-settings/access-repo-security-info.png) +1. Under "Privileged access", click **Unlock**. + ![Unlock button](/assets/images/enterprise/site-admin-settings/unlock-priviledged-repo-access.png) +1. Under **Reason**, type a reason for unlocking the repository, then click **Unlock**. + ![Confirmation dialog](/assets/images/enterprise/site-admin-settings/confirm-unlock-repo-access.png) +1. Now that the repository is unlocked, you can leave the site admin pages and delete the repository within the `actions` organization. At the top of the page, click the repository name, in this example **checkout**, to return to the summary page. + ![Repository name link](/assets/images/enterprise/site-admin-settings/display-repository-admin-summary.png) +1. Under "Repository info", click **View code** to leave the site admin pages and display the `checkout` repository. +1. Delete the `checkout` repository within the `actions` organization. For information on how to delete a repository, see "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)." + ![View code link](/assets/images/enterprise/site-admin-settings/exit-admin-page-for-repository.png) +1. Configure your workflow's YAML to use `{% data reusables.actions.action-checkout %}`. +1. Each time your workflow runs, the runner will use the specified version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}. - {% ifversion ghes > 3.2 or ghae %} {% note %} + {% ifversion ghes > 3.2 or ghae %} + {% note %} - 注意:首次从 {% data variables.product.prodname_dotcom_the_website %} 使用 `checkout` 操作时,`actions/checkout` 命名空间会在 {% data variables.product.product_location %} 上自动停用。 如果要还原为使用操作的本地副本,则首先需要从停用中删除命名空间。 有关详细信息,请参阅“[自动停用在 {% data variables.product.prodname_dotcom_the_website%} 上访问的操作的命名空间](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)”。 + **Note:** The first time the `checkout` action is used from {% data variables.product.prodname_dotcom_the_website %}, the `actions/checkout` namespace is automatically retired on {% data variables.location.product_location %}. If you ever want to revert to using a local copy of the action, you first need to remove the namespace from retirement. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." - {% endnote %} {% endif %} + {% endnote %} + {% endif %} diff --git a/translations/zh-CN/content/admin/identity-and-access-management/index.md b/translations/zh-CN/content/admin/identity-and-access-management/index.md index 033b36bd33..477ee3ba03 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/index.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/index.md @@ -1,6 +1,6 @@ --- -title: 标识和访问管理 -intro: '你可以配置人们如何访问 {% ifversion ghec or ghae %}{% data variables.product.product_name %} 上你的企业{% elsif ghes %}{% data variables.product.product_location %}{% endif %}。' +title: Identity and access management +intro: 'You can configure how people access {% ifversion ghec or ghae %}your enterprise on {% data variables.product.product_name %}{% elsif ghes %}{% data variables.location.product_location %}{% endif %}.' redirect_from: - /enterprise/admin/authentication - /admin/authentication @@ -21,11 +21,5 @@ children: - /using-saml-for-enterprise-iam - /using-enterprise-managed-users-for-iam - /managing-recovery-codes-for-your-enterprise -ms.openlocfilehash: 8c7a364ba6310617452626901c5859ef54cd2b47 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147882809' --- diff --git a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md index 0ad52e007b..3466c75d14 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md @@ -1,7 +1,7 @@ --- title: About authentication for your enterprise shortTitle: About authentication -intro: 'You {% ifversion ghae %}must configure SAML single sign-on (SSO) so people can{% else %}can choose how people{% endif %} authenticate to access {% ifversion ghec %}your enterprise''s resources on {% data variables.product.product_name %}{% elsif ghes %}{% data variables.product.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %}.' +intro: 'You {% ifversion ghae %}must configure SAML single sign-on (SSO) so people can{% else %}can choose how people{% endif %} authenticate to access {% ifversion ghec %}your enterprise''s resources on {% data variables.product.product_name %}{% elsif ghes %}{% data variables.location.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %}.' versions: ghec: '*' ghes: '*' @@ -29,23 +29,23 @@ After learning more about these options, to determine which method is best for y The following options are available for account management and authentication on {% data variables.product.product_name %}. -- [Authentication through {% data variables.product.product_location %}](#authentication-through-githubcom) -- [Authentication through {% data variables.product.product_location %} with additional SAML access restriction](#authentication-through-githubcom-with-additional-saml-access-restriction) +- [Authentication through {% data variables.location.product_location %}](#authentication-through-githubcom) +- [Authentication through {% data variables.location.product_location %} with additional SAML access restriction](#authentication-through-githubcom-with-additional-saml-access-restriction) - [Authentication with {% data variables.product.prodname_emus %} and federation](#authentication-with-enterprise-managed-users-and-federation) -### Authentication through {% data variables.product.product_location %} +### Authentication through {% data variables.location.product_location %} -By default, each member must create a personal account on {% data variables.product.product_location %}. You grant access to your enterprise, and the member can access your enterprise's resources after signing into the account on {% data variables.product.product_location %}. The member manages the account, and can contribute to other enterprises, organizations, and repositories on {% data variables.product.product_location %}. +By default, each member must create a personal account on {% data variables.location.product_location %}. You grant access to your enterprise, and the member can access your enterprise's resources after signing into the account on {% data variables.location.product_location %}. The member manages the account, and can contribute to other enterprises, organizations, and repositories on {% data variables.location.product_location %}. -### Authentication through {% data variables.product.product_location %} with additional SAML access restriction +### Authentication through {% data variables.location.product_location %} with additional SAML access restriction -If you configure additional SAML access restriction, each member must create and manage a personal account on {% data variables.product.product_location %}. You grant access to your enterprise, and the member can access your enterprise's resources after both signing into the account on {% data variables.product.product_location %} and successfully authenticating with your SAML identity provider (IdP). The member can contribute to other enterprises, organizations, and repositories on {% data variables.product.product_location %} using their personal account. For more information about requiring SAML authentication for all access your enterprise's resources, see "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)." +If you configure additional SAML access restriction, each member must create and manage a personal account on {% data variables.location.product_location %}. You grant access to your enterprise, and the member can access your enterprise's resources after both signing into the account on {% data variables.location.product_location %} and successfully authenticating with your SAML identity provider (IdP). The member can contribute to other enterprises, organizations, and repositories on {% data variables.location.product_location %} using their personal account. For more information about requiring SAML authentication for all access your enterprise's resources, see "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)." If you use a standalone organization with {% data variables.product.product_name %}, or if you don't want to use SAML authentication for every organization in your enterprise, you can configure SAML for an individual organization. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." ### Authentication with {% data variables.product.prodname_emus %} and federation -If you need more control of the accounts for your enterprise members on {% data variables.product.product_location %}, you can use {% data variables.product.prodname_emus %}. With {% data variables.product.prodname_emus %}, you provision and manage accounts for your enterprise members on {% data variables.product.product_location %} using your IdP. Each member signs into an account that you create, and your enterprise manages the account. Contributions to the rest of {% data variables.product.prodname_dotcom_the_website %} are restricted. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)." +If you need more control of the accounts for your enterprise members on {% data variables.location.product_location %}, you can use {% data variables.product.prodname_emus %}. With {% data variables.product.prodname_emus %}, you provision and manage accounts for your enterprise members on {% data variables.location.product_location %} using your IdP. Each member signs into an account that you create, and your enterprise manages the account. Contributions to the rest of {% data variables.product.prodname_dotcom_the_website %} are restricted. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)." ## Identifying the best authentication method for your enterprise @@ -76,29 +76,29 @@ You can use {% data variables.product.prodname_emus %} with an unsupported IdP o ### Do your developers work in public repositories, gists, or {% data variables.product.prodname_pages %} sites? -To prevent enterprise members from accidentally leaking corporate-owned content to the public on {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_emus %} imposes strong restrictions on what users can do. For example, {% data variables.product.prodname_managed_users %} cannot create public repositories, gists of any visibility, or {% data variables.product.prodname_pages %} sites that are visible outside the enterprise. For a full list of restrictions, see "[Abilities and restrictions of {% data variables.product.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-users)." +To prevent enterprise members from accidentally leaking corporate-owned content to the public on {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_emus %} imposes strong restrictions on what users can do. For example, {% data variables.enterprise.prodname_managed_users %} cannot create public repositories, gists of any visibility, or {% data variables.product.prodname_pages %} sites that are visible outside the enterprise. For a full list of restrictions, see "[Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-users)." These restrictions are unacceptable for some enterprises. To determine whether {% data variables.product.prodname_emus %} will work for you, review the restrictions with your developers, and confirm whether any of the restrictions will hinder your existing workflows. If so, SAML SSO may be a better choice for your enterprise. ### Do your developers rely on collaboration outside of your enterprise? -{% data variables.product.prodname_managed_users_caps %} can only contribute to repositories within your enterprise. If your developers must contribute to both repositories within and outside of your enterprise, including private repositories, {% data variables.product.prodname_emus %} may not be right for your enterprise. SAML SSO may be a better solution. +{% data variables.enterprise.prodname_managed_users_caps %} can only contribute to repositories within your enterprise. If your developers must contribute to both repositories within and outside of your enterprise, including private repositories, {% data variables.product.prodname_emus %} may not be right for your enterprise. SAML SSO may be a better solution. -Some companies maintain repositories within an existing enterprise using SAML SSO on {% data variables.product.product_location %}, and also create an {% data variables.product.prodname_emu_enterprise %}. Developers who contribute to repositories owned by both enterprises from a single workstation must switch between the accounts on {% data variables.product.product_location %} within a single browser, or use a different browser for each account. The developer may also need to customize the workstation's Git configuration to accommodate the two accounts. The complexity of this workflow can increase the risk of mistakenly leaking internal code to the public. +Some companies maintain repositories within an existing enterprise using SAML SSO on {% data variables.location.product_location %}, and also create an {% data variables.enterprise.prodname_emu_enterprise %}. Developers who contribute to repositories owned by both enterprises from a single workstation must switch between the accounts on {% data variables.location.product_location %} within a single browser, or use a different browser for each account. The developer may also need to customize the workstation's Git configuration to accommodate the two accounts. The complexity of this workflow can increase the risk of mistakenly leaking internal code to the public. -If you decide to create an {% data variables.product.prodname_emu_enterprise %} but require that developers contribute to resources outside of the enterprise from a single workstation, you can provide support for switching between the accounts in a developer's local Git configuration. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#supporting-developers-with-multiple-user-accounts-on-githubcom)." +If you decide to create an {% data variables.enterprise.prodname_emu_enterprise %} but require that developers contribute to resources outside of the enterprise from a single workstation, you can provide support for switching between the accounts in a developer's local Git configuration. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#supporting-developers-with-multiple-user-accounts-on-githubcom)." ### Does your enterprise rely on outside collaborators? With SAML SSO, you can give access to specific repositories to people who are not members of your IdP's directory, by using the outside collaborator role. This can be especially useful for collaborators that are external to your business, such as contractors. For more information, see "[Adding outside collaborators to repositories in your organization](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." -With {% data variables.product.prodname_emus %}, the outside collaborator role does not exist. Your enterprise's resources can only be accessed by {% data variables.product.prodname_managed_users %}, which are always provisioned by your IdP. To give external collaborators access to your enterprise, you would have to use guest accounts in your IdP. If you're interested in {% data variables.product.prodname_emus %}, confirm with your developers whether this will hinder any of their existing workflows. If so, SAML SSO may be a better solution. +With {% data variables.product.prodname_emus %}, the outside collaborator role does not exist. Your enterprise's resources can only be accessed by {% data variables.enterprise.prodname_managed_users %}, which are always provisioned by your IdP. To give external collaborators access to your enterprise, you would have to use guest accounts in your IdP. If you're interested in {% data variables.product.prodname_emus %}, confirm with your developers whether this will hinder any of their existing workflows. If so, SAML SSO may be a better solution. ### Can your enterprise tolerate migration costs? If your enterprise is new to {% data variables.product.prodname_dotcom_the_website %}, SAML SSO and {% data variables.product.prodname_emus %} are equally easy to adopt. -If you're already using {% data variables.product.prodname_dotcom_the_website %} with developers managing their own user accounts, adopting {% data variables.product.prodname_emus %} requires migrating to a new enterprise account. For more information, see "[About enterprises with {% data variables.product.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#about-enterprises-with-managed-users)." +If you're already using {% data variables.product.prodname_dotcom_the_website %} with developers managing their own user accounts, adopting {% data variables.product.prodname_emus %} requires migrating to a new enterprise account. For more information, see "[About enterprises with {% data variables.enterprise.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#about-enterprises-with-managed-users)." Although {% data variables.product.prodname_emus %} is free, the migration process may require time or cost from your team. Confirm that this migration process is acceptable to your business and your developers. If not, SAML SSO may be the better choice for you. @@ -119,7 +119,7 @@ The following authentication methods are available for {% data variables.product ### External authentication -If you use an external directory or identity provider (IdP) to centralize access to multiple web applications, you may be able to configure external authentication for {% data variables.product.product_location %}. For more information, see the following. +If you use an external directory or identity provider (IdP) to centralize access to multiple web applications, you may be able to configure external authentication for {% data variables.location.product_location %}. For more information, see the following. - "[Using CAS for enterprise IAM](/admin/identity-and-access-management/using-cas-for-enterprise-iam)" - "[Using LDAP for enterprise IAM](/admin/identity-and-access-management/using-ldap-for-enterprise-iam)" diff --git a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md index 8cde223bc2..85b2acf6bd 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md @@ -1,6 +1,6 @@ --- -title: 更改身份验证方法 -intro: '您可以随时更改 {% data variables.product.prodname_ghe_server %} 对您现有的帐户进行身份验证的方法。' +title: Changing authentication methods +intro: 'You can change the way {% data variables.product.prodname_ghe_server %} authenticates with your existing accounts at any time.' redirect_from: - /enterprise/admin/user-management/changing-authentication-methods - /enterprise/admin/authentication/changing-authentication-methods @@ -16,33 +16,27 @@ topics: - Enterprise - Identity shortTitle: Change authentication methods -ms.openlocfilehash: 074c4fe8784d3ea7b8ada6b532e680384571facf -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147882689' --- -更改身份验证方法时,{% data variables.product.product_location %} 上的用户帐户将保留,只要他们的用户名没有发生变化,用户就可以继续登录原来的帐户。 +User accounts on {% data variables.location.product_location %} are preserved when you change the authentication method and users will continue to log into the same account as long as their username doesn't change. -如果新的身份验证方法更改了用户名,将创建新帐户。 作为管理员,可以通过站点管理员设置或使用[用户管理 API](/rest/reference/enterprise-admin#update-the-username-for-a-user) 重命名用户。 +If the new method of authentication changes usernames, new accounts will be created. As an administrator, you can rename users through the site admin settings or by using [the User Administration API](/rest/reference/enterprise-admin#update-the-username-for-a-user). -您应当考虑的其他问题包括: +Other issues you should take into consideration include: -* **密码:** 如果对实例改为使用内置身份验证方法,则用户必须在更改完成后 [设置密码](/enterprise/user/articles/how-can-i-reset-my-password/)。 +* **Passwords:** If you switch to using built-in authentication for your instance, users must [set a password](/enterprise/user/articles/how-can-i-reset-my-password/) after the change is completed. -* **站点管理员:** 管理权限 [在你使用 SAML 时由你的标识提供者控制](/enterprise/admin/guides/user-management/using-saml/#saml-attributes),而 [在你使用 LDAP 时由组成员身份控制](/enterprise/admin/authentication/using-ldap#configuring-ldap-with-your-github-enterprise-server-instance)。 +* **Site administrators:** Administrative privileges are [controlled by your identity provider when you use SAML](/enterprise/admin/guides/user-management/using-saml/#saml-attributes) and can be [controlled by group membership when you use LDAP](/enterprise/admin/authentication/using-ldap#configuring-ldap-with-your-github-enterprise-server-instance). -* **团队成员身份:** 只有 LDAP 可让你从目录服务器 [控制团队成员身份](/enterprise/admin/authentication/using-ldap#configuring-ldap-with-your-github-enterprise-server-instance)。 +* **Team membership:** Only LDAP lets you [control team membership](/enterprise/admin/authentication/using-ldap#configuring-ldap-with-your-github-enterprise-server-instance) from your directory server. -* **用户挂起:** 当你使用 LDAP 进行身份验证时,可以通过受限制的组控制对 {% data variables.product.prodname_ghe_server %} 的访问权限。 在切换到 LDAP 后,如果配置受限制的组,那么不属于其中任何一个组的现有用户将被挂起。 在用户登录或下一次 LDAP 同步期间将发生挂起。 +* **User suspension:** When you use LDAP to authenticate, access to {% data variables.product.prodname_ghe_server %} can be controlled via _restricted groups_. After switching to LDAP, if restricted groups are configured, existing users who are not in one of those groups will be suspended. Suspension will occur either when they log in or during the next LDAP Sync. -* **组成员身份:** 当你使用 LDAP 进行身份验证时,系统会根据受限制的组成员身份和 Active Directory 中的帐户状态自动 [挂起和取消挂起](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users)。 +* **Group membership:** When you use LDAP to authenticate, users are automatically [suspended and unsuspended](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users) based on restricted group membership and account status with Active Directory. -* **Git 身份验证:** SAML 和 CAS 仅支持通过 HTTP 或 HTTPS 使用 [个人访问令牌](/articles/creating-an-access-token-for-command-line-use)进行的 Git 身份验证。 不支持通过 HTTP 或 HTTPS 进行的密码身份验证。 LDAP 默认支持基于密码的 Git 身份验证,但我们建议你[禁用该方法](/enterprise/admin/authentication/using-ldap#disabling-password-authentication-for-git-operations),并强制通过个人访问令牌或 SSH 密钥进行身份验证。 +* **Git authentication:** SAML and CAS only supports Git authentication over HTTP or HTTPS using a [{% data variables.product.pat_generic %}](/articles/creating-an-access-token-for-command-line-use). Password authentication over HTTP or HTTPS is not supported. LDAP supports password-based Git authentication by default, but we recommend that you [disable that method](/enterprise/admin/authentication/using-ldap#disabling-password-authentication-for-git-operations) and force authentication via a {% data variables.product.pat_generic %} or SSH key. -* **API 身份验证:** SAML 和 CAS 仅支持使用 [个人访问令牌](/articles/creating-an-access-token-for-command-line-use)进行的 API 身份验证。 不支持基本身份验证。 +* **API authentication:** SAML and CAS only supports API authentication using a [{% data variables.product.pat_generic %}](/articles/creating-an-access-token-for-command-line-use). Basic authentication is not supported. -* **双因素身份验证:** {% data reusables.enterprise_user_management.external_auth_disables_2fa %} +* **Two-factor authentication:** {% data reusables.enterprise_user_management.external_auth_disables_2fa %} -* **对在外部身份验证提供者中无帐户的用户进行身份验证:** 你可以邀请用户在 {% data variables.product.product_location %} 中进行身份验证,而无需将他们添加到标识提供者中。 有关详细信息,请参阅“[允许对提供者外部的用户使用内置身份验证](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)”。 +* **Fallback authentication for users with no account on your external authentication provider:** You can invite users to authenticate to {% data variables.location.product_location %} without adding them to your identity provider. For more information, see "[Allowing built-in authentication for users outside your provider](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)." diff --git a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md index 7b654e6eb6..f43f417986 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md @@ -1,9 +1,12 @@ --- -title: 管理企业的 IAM +title: Managing IAM for your enterprise intro: | - {%- ifversion ghec %} 你可以邀请 {% data variables.product.product_location %} 上的现有个人帐户成为企业成员,并且可以选择启用 SAML 单一登录 (SSO) 来集中管理访问权限。 或者,可以将 {% data variables.product.prodname_emus %} 与 SAML SSO 配合使用来创建和控制企业成员的帐户。 - {%- elsif ghes %} 你可以使用 {% data variables.product.product_name %} 的内置身份验证,也可以使用 CAS、LDAP 或 SAML 集中管理对实例的身份验证和访问。 - {%- elsif ghae %} 必须使用 SAML 单一登录 (SSO) 在 {% data variables.product.product_name %} 上集中管理对企业的身份验证和访问。 (可选)当对标识提供者 (IdP) 进行更改时,可以使用跨域身份管理系统 (SCIM) 在 {% data variables.product.product_name %} 上自动预配帐户和访问权限。 + {%- ifversion ghec %} + You can invite existing personal accounts on {% data variables.location.product_location %} to be members of your enterprise, and you can optionally enable SAML single sign-on (SSO) to centrally manage access. Alternatively, you can use {% data variables.product.prodname_emus %} with SAML SSO to create and control the accounts of your enterprise members. + {%- elsif ghes %} + You can use {% data variables.product.product_name %}'s built-in authentication, or you can centrally manage authentication and access to your instance with CAS, LDAP, or SAML. + {%- elsif ghae %} + You must use SAML single sign-on (SSO) to centrally manage authentication and access to your enterprise on {% data variables.product.product_name %}. Optionally, you can use System for Cross-domain Identity Management (SCIM) to automatically provision accounts and access on {% data variables.product.product_name %} when you make changes on your identity provider (IdP). {%- endif %} redirect_from: - /enterprise/admin/categories/authentication @@ -29,11 +32,5 @@ children: - /allowing-built-in-authentication-for-users-outside-your-provider - /troubleshooting-identity-and-access-management-for-your-enterprise shortTitle: Manage IAM for your enterprise -ms.openlocfilehash: 0af30fe07928336fd93ba3b17fd1efff0b64e354 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147718003' --- diff --git a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md index 822f11384e..2eaaa11272 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md @@ -30,7 +30,7 @@ topics: You can configure external authentication for {% data variables.product.product_name %} using CAS, LDAP, or SAML. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#authentication-methods-for-github-enterprise-server)." -When you use external authentication, {% data variables.product.product_location %} automatically creates a username for each person when the person signs into {% data variables.product.product_location %} through your external authentication system for the first time. +When you use external authentication, {% data variables.location.product_location %} automatically creates a username for each person when the person signs into {% data variables.location.product_location %} through your external authentication system for the first time. {% elsif ghec %} @@ -45,11 +45,11 @@ If you use an enterprise with {% data variables.product.prodname_emus %}, member {% endif %} {% ifversion ghec %} -## About usernames for {% data variables.product.prodname_managed_users %} +## About usernames for {% data variables.enterprise.prodname_managed_users %} -When your {% data variables.product.prodname_emu_enterprise %} is created, you will choose a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} The setup user who configures SAML SSO has a username in the format of **@SHORT-CODE_admin**. +When your {% data variables.enterprise.prodname_emu_enterprise %} is created, you will choose a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} The setup user who configures SAML SSO has a username in the format of **@SHORT-CODE_admin**. -When you provision a new user from your identity provider, the new {% data variables.product.prodname_managed_user %} will have a {% data variables.product.prodname_dotcom %} username in the format of **@IDP-USERNAME_SHORT-CODE**. The IDP-USERNAME component is formed by normalizing the SCIM `userName` attribute value sent from the IdP. +When you provision a new user from your identity provider, the new {% data variables.enterprise.prodname_managed_user %} will have a {% data variables.product.prodname_dotcom %} username in the format of **@IDP-USERNAME_SHORT-CODE**. The IDP-USERNAME component is formed by normalizing the SCIM `userName` attribute value sent from the IdP. | Identity provider | {% data variables.product.prodname_dotcom %} username | |-----------------------------------|----------------------| @@ -100,7 +100,7 @@ When you configure SAML authentication, {% data variables.product.product_name % {% ifversion not ghec %} ### About username normalization with SAML -{% ifversion ghes %}If you configure SAML authentication for {% data variables.product.product_location %}, {% endif %}{% data variables.product.product_name %} determines each person's username by one of the following assertions in the SAML response, ordered by descending priority. +{% ifversion ghes %}If you configure SAML authentication for {% data variables.location.product_location %}, {% endif %}{% data variables.product.product_name %} determines each person's username by one of the following assertions in the SAML response, ordered by descending priority. 1. The custom `username` attribute, if defined and present 1. An `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name` assertion, if present @@ -109,12 +109,12 @@ When you configure SAML authentication, {% data variables.product.product_name % {% data variables.product.product_name %} requires the `NameID` element even if other attributes are present. For more information, see "[SAML configuration reference](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-attributes)." -{% data variables.product.product_name %} creates a mapping between the `NameID` from the IdP and the username {% ifversion ghae %}in{% else %}on{% endif %} {% data variables.product.product_location %}, so the `NameID` should be persistent, unique, and not subject to change for the lifecycle of the user. +{% data variables.product.product_name %} creates a mapping between the `NameID` from the IdP and the username {% ifversion ghae %}in{% else %}on{% endif %} {% data variables.location.product_location %}, so the `NameID` should be persistent, unique, and not subject to change for the lifecycle of the user. {% ifversion ghes %} {% note %} -**Note**: If the `NameID` for a user does change on the IdP, the person will see an error message when signing into {% data variables.product.product_location %}. To restore the person's access, you'll need to update the user account's `NameID` mapping. For more information, see "[Updating a user's SAML `NameID`](/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid)." +**Note**: If the `NameID` for a user does change on the IdP, the person will see an error message when signing into {% data variables.location.product_location %}. To restore the person's access, you'll need to update the user account's `NameID` mapping. For more information, see "[Updating a user's SAML `NameID`](/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid)." {% endnote %} {% endif %} @@ -125,7 +125,7 @@ When you configure SAML authentication, {% data variables.product.product_name % When a new user is being provisioned, if the user's normalized username conflicts with an existing user in the enterprise, the provisioning attempt will fail with a `409` error. -To resolve this problem, you must make a change in your IdP so that the normalized usernames will be unique. If you cannot change the identifier that's being normalized, you can change the attribute mapping for the `userName` attribute. If you change the attribute mapping, usernames of existing {% data variables.product.prodname_managed_users %} will be updated, but nothing else about the accounts will change, including activity history. +To resolve this problem, you must make a change in your IdP so that the normalized usernames will be unique. If you cannot change the identifier that's being normalized, you can change the attribute mapping for the `userName` attribute. If you change the attribute mapping, usernames of existing {% data variables.enterprise.prodname_managed_users %} will be updated, but nothing else about the accounts will change, including activity history. {% note %} diff --git a/translations/zh-CN/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md b/translations/zh-CN/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md index 634477f0db..48536e3ec9 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md @@ -1,7 +1,7 @@ --- -title: 下载企业帐户的单一登录恢复代码 +title: Downloading your enterprise account's single sign-on recovery codes shortTitle: Download recovery codes -intro: '如果标识提供者 (IdP) 不可用,为了确保你可以访问 {% data variables.product.product_name %},应下载企业帐户的单一登录 (SSO) 恢复代码。' +intro: 'To ensure that you can access {% data variables.product.product_name %} if your identity provider (IdP) is unavailable, you should download your enterprise account''s single sign-on (SSO) recovery codes.' versions: ghec: '*' type: how_to @@ -13,27 +13,25 @@ topics: redirect_from: - /admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-saml-single-sign-on-recovery-codes permissions: Enterprise owners can download the SSO recovery codes for the enterprise account. -ms.openlocfilehash: 82f44654b18a36d2fb29797fe8b6e0426785522b -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147063592' --- -如果 IdP 不可用,可以使用恢复代码在 {% data variables.product.product_location %} 上登录和访问企业。 有关详细信息,请参阅“[在标识提供者不可用时访问企业帐户](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/accessing-your-enterprise-account-if-your-identity-provider-is-unavailable)”。 -如果在配置 SSO 时未保存恢复代码,你仍可从企业的设置中访问代码。 +In the event that your IdP is unavailable, you can use a recovery code to sign in and access your enterprise on {% data variables.location.product_location %}. For more information, see "[Accessing your enterprise account if your identity provider is unavailable](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/accessing-your-enterprise-account-if-your-identity-provider-is-unavailable)." + +If you did not save your recovery codes when you configured SSO, you can still access the codes from your enterprise's settings. -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} -1. 在{% ifversion oidc-for-emu %}{% endif %}“需要 SAML 身份验证”{% ifversion oidc-for-emu %}或“需要 OIDC 身份验证”{% endif %}下,单击“保存恢复代码”。{% ifversion oidc-for-emu %} {% note %} +1. Under{% ifversion oidc-for-emu %} either{% endif %} "Require SAML authentication"{% ifversion oidc-for-emu %} or "Require OIDC authentication"{% endif %}, click **Save your recovery codes**.{% ifversion oidc-for-emu %} + {% note %} - 注意:OIDC SSO 仅适用于 {% data variables.product.prodname_emus %}。 有关详细信息,请参阅“[关于企业托管用户](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)”。 + **Note:** OIDC SSO is only available for {% data variables.product.prodname_emus %}. For more information, see "[About Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)." {% endnote %}{% endif %} - ![实施前测试 SAML 配置的按钮的屏幕截图](/assets/images/help/enterprises/saml-recovery-codes-link.png) -1. 要保存恢复代码,请单击“下载”、“打印”或“复制” 。 - ![下载、打印或复制恢复代码的按钮的屏幕截图](/assets/images/help/saml/saml_recovery_code_options.png) + ![Screenshot of the button to test SAML configuration before enforcing](/assets/images/help/enterprises/saml-recovery-codes-link.png) +1. To save your recovery codes, click **Download**, **Print**, or **Copy**. + ![Screenshot of the buttons to download, print, or copy your recovery codes](/assets/images/help/saml/saml_recovery_code_options.png) diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md b/translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md index 4f8c5c838b..50f7970f7e 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md @@ -1,6 +1,6 @@ --- -title: 配置内置身份验证 -intro: '当你使用默认身份验证方法时,所有身份验证详细信息都将存储在 {% data variables.product.product_location %} 中。' +title: Configuring built-in authentication +intro: 'When you use the default authentication method, all authentication details are stored on {% data variables.location.product_location %}.' permissions: 'Site administrators can configure authentication for a {% data variables.product.product_name %} instance.' redirect_from: - /enterprise/admin/user-management/using-built-in-authentication @@ -17,42 +17,41 @@ topics: - Enterprise - Identity shortTitle: Configure built-in authentication -ms.openlocfilehash: 6fbcd68efc953b5a32139a6907975e6918976860 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717811' --- -## 关于内置身份验证 -默认情况下,{% data variables.product.product_name %} 使用内置身份验证。 每个人都可以通过邀请或注册在 {% data variables.product.product_location %} 上创建用户帐户,然后使用帐户的凭据进行身份验证以访问你的实例。 你的 {% data variables.product.product_name %} 实例中存储有帐户的身份验证信息。 +## About built-in authentication -你可以阻止未经身份验证的人员在你的实例上创建新用户帐户。 有关详细信息,请参阅“[禁用未经身份验证的注册](/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups)”。 +By default, {% data variables.product.product_name %} uses built-in authentication. Each person creates a user account on {% data variables.location.product_location %} from an invitation or by signing up, and then authenticates with the credentials for the account to access your instance. Your {% data variables.product.product_name %} instance stores the authentication information for the account. + +You can prevent unauthenticated people from creating new user accounts on your instance. For more information, see "[Disabling unauthenticated sign-ups](/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups)." {% data reusables.enterprise_user_management.alternatively-enable-external-authentication %} -## 配置内置身份验证 +## Configuring built-in authentication -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.authentication %} -4. 选择“内置身份验证”。 -![选择内置身份验证选项](/assets/images/enterprise/management-console/built-in-auth-select.png) +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.authentication %} +4. Select **Built in authentication**. +![Select built-in authentication option](/assets/images/enterprise/management-console/built-in-auth-select.png) -{% data reusables.enterprise_user_management.two_factor_auth_header %} {% data reusables.enterprise_user_management.2fa_is_available %} +{% data reusables.enterprise_user_management.two_factor_auth_header %} +{% data reusables.enterprise_user_management.2fa_is_available %} -## 创建账户 +## Creating your account -在实例创建完成后,您需要创建自己的管理员帐户。 +Once your instance has been created, you'll need to create your own admin account. -1. 在 `http(s)://[hostname]/join` 中的“创建管理员帐户”页上,选择用户名、密码和电子邮件地址,然后单击“创建帐户”。 -![创建管理员帐户](/assets/images/enterprise/site-admin-settings/create-first-admin-acct.png) {% data reusables.enterprise_site_admin_settings.sign-in %} +1. On the "Create Admin Account" page at `http(s)://[hostname]/join`, choose your username, password, and email address, then click **Create an account**. +![Create Admin Account](/assets/images/enterprise/site-admin-settings/create-first-admin-acct.png) +{% data reusables.enterprise_site_admin_settings.sign-in %} -## 后续步骤 +## Next steps -配置内置身份验证并创建管理帐户后,可以邀请用户创建帐户并使用你的实例。 有关详细信息,请参阅“[邀请他人使用你的实例](/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance)”。 +After you configure built-in authentication and create your administrative account, you can invite people to create accounts and use your instance. For more information, see "[Inviting people to use your instance](/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance)." -## 延伸阅读 +## Further reading -- “[配置电子邮件通知](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)” +- "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)" diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md b/translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md index 4504ff88f3..040dd977c6 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md @@ -1,5 +1,5 @@ --- -title: 禁用未经身份验证的注册 +title: Disabling unauthenticated sign-ups redirect_from: - /enterprise/admin/articles/disabling-sign-ups - /enterprise/admin/user-management/disabling-unauthenticated-sign-ups @@ -7,7 +7,7 @@ redirect_from: - /admin/authentication/disabling-unauthenticated-sign-ups - /enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups - /admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups -intro: '如果对 {% data variables.product.product_location %} 使用内置身份验证,则可阻止未经身份验证的人在你的实例上创建新用户帐户。' +intro: 'If you''re using built-in authentication for {% data variables.location.product_location %}, you can block unauthenticated people from creating new user accounts on your instance.' permissions: 'Site administrators can disable unauthenticated sign-ups on a {% data variables.product.product_name %} instance.' versions: ghes: '*' @@ -18,21 +18,19 @@ topics: - Enterprise - Identity shortTitle: Block unauthenticated sign-up -ms.openlocfilehash: 063da3aa1e73501d05251e40d7afcb271833afaf -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147065382' --- -## 关于未经身份验证的注册 -{% data reusables.enterprise_user_management.built-in-authentication-new-accounts %} {% data reusables.enterprise_user_management.unauthenticated-sign-ups %} 可以禁用未经身份验证的注册,并要求邀请在实例上创建新的用户帐户。 +## About unauthenticated sign-ups + +{% data reusables.enterprise_user_management.built-in-authentication-new-accounts %} {% data reusables.enterprise_user_management.unauthenticated-sign-ups %} You can disable unauthenticated sign-ups and require an invitation to create a new user account on your instance. {% data reusables.enterprise_user_management.alternatively-enable-external-authentication %} -## 禁用未经身份验证的注册 +## Disabling unauthenticated sign-ups -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} -3. 取消选择“启用注册”。 -![启用“注册”复选框](/assets/images/enterprise/management-console/enable-sign-up.png) {% data reusables.enterprise_management_console.save-settings %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.privacy %} +3. Unselect **Enable sign-up**. +![Enable sign-up checkbox](/assets/images/enterprise/management-console/enable-sign-up.png) +{% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md b/translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md index d8b379f270..826da0bc57 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md @@ -1,6 +1,6 @@ --- -title: 邀请用户使用实例 -intro: '对 {% data variables.product.product_name %} 使用内置身份验证时,可以通过电子邮件地址邀请人员在实例上创建用户帐户。' +title: Inviting people to use your instance +intro: 'When you use built-in authentication for {% data variables.product.product_name %}, you can invite people by email address to create a user account on your instance.' versions: ghes: '*' permissions: 'Enterprise owners can invite people to create a user account on a {% data variables.product.product_name %} instance.' @@ -11,23 +11,20 @@ topics: - Enterprise - Identity shortTitle: Invite people -ms.openlocfilehash: d7ccb5e06f297a11ba97fa41d8250821909e5e3d -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717795' --- -## 关于新用户的邀请 + +## About invitations for new users {% data reusables.enterprise_user_management.built-in-authentication-new-accounts %} {% data reusables.enterprise_user_management.unauthenticated-sign-ups %} -可以禁用未经身份验证的注册,并要求邀请才能在实例上创建新用户帐户。 有关详细信息,请参阅“[禁用未经身份验证的注册](/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups)”。 +You can disable unauthenticated sign-ups and require an invitation to create a new user account on your instance. For more information, see "[Disabling unauthenticated sign-ups](/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups)." {% data reusables.enterprise_user_management.alternatively-enable-external-authentication %} -## 邀请用户创建用户帐户 +## Inviting people to create a user account -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.invite-user-sidebar-tab %} {% data reusables.enterprise_site_admin_settings.invite-user-reset-link %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.invite-user-sidebar-tab %} +{% data reusables.enterprise_site_admin_settings.invite-user-reset-link %} -如果已为 {% data variables.product.product_location %} 上的通知配置了电子邮件,则实例会将邀请发送到提供的电子邮件地址。 有关详细信息,请参阅“[配置邮件通知](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)”。 +If you've configured email for notifications on {% data variables.location.product_location %}, your instance will send the invitation to the provided email address. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)." diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md b/translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md index b01ce2d2f4..eb31c71027 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md @@ -1,16 +1,10 @@ --- -title: 将 CAS 用于企业 IAM +title: Using CAS for enterprise IAM shortTitle: CAS for enterprise IAM -intro: '可以通过与现有 CAS 标识提供者 (IdP) 集成,来集中管理帐户和对 {% data variables.product.product_location %} 的访问权限。' +intro: 'You can centrally manage accounts and access to {% data variables.location.product_location %} by integrating with your existing CAS identity provider (IdP).' versions: ghes: '*' children: - /using-cas -ms.openlocfilehash: cc611feeed0f22033ed0c92883b3f95afe41ea92 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145099968' --- diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md b/translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md index 53e4d8f402..80a7879125 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md @@ -1,5 +1,5 @@ --- -title: 使用 CAS +title: Using CAS redirect_from: - /enterprise/admin/articles/configuring-cas-authentication - /enterprise/admin/articles/about-cas-authentication @@ -8,7 +8,7 @@ redirect_from: - /admin/authentication/using-cas - /enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas - /admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-cas -intro: '如果使用中央身份验证服务 (CAS) 集中访问多个 Web 应用程序,可以通过为实例配置 CAS 身份验证来集成 {% data variables.product.product_name %}。' +intro: 'If you use Central Authentication Service (CAS) to centralize access to multiple web applications, you can integrate {% data variables.product.product_name %} by configuring CAS authentication for your instance.' versions: ghes: '*' type: how_to @@ -18,42 +18,39 @@ topics: - Enterprise - Identity - SSO -ms.openlocfilehash: 4bd9c8baf32ab09c593a251ca4f1cb698e075501 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147884275' --- -## 关于 {% data variables.product.product_name %} 的 CAS 身份验证 -CAS 是一种单一登录 (SSO) 协议,可集中管理多个 Web 应用程序的身份验证。 有关详细信息,请参阅维基百科上的“[集中身份验证服务](https://en.wikipedia.org/wiki/Central_Authentication_Service)”。 +## About CAS authentication for {% data variables.product.product_name %} -配置 CAS 后,使用 {% data variables.product.product_location %} 的人员必须使用个人访问令牌通过 HTTP(S) 对 API 或 Git 请求进行身份验证。 不能使用 CAS 凭据对这些请求进行身份验证。 有关详细信息,请参阅“[创建个人访问令牌](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)”。 +CAS is a single sign-on (SSO) protocol that centralizes authentication to multiple web applications. For more information, see "[Central Authentication Service](https://en.wikipedia.org/wiki/Central_Authentication_Service)" on Wikipedia. -如果配置 CAS,则在标识提供者 (IdP) 上拥有帐户的用户在登录 {% data variables.product.product_location %} 之前不会使用用户许可证。 +After you configure CAS, people who use {% data variables.location.product_location %} must use a {% data variables.product.pat_generic %} to authenticate API or Git requests over HTTP(S). CAS credentials cannot be used to authenticate these requests. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." + +If you configure CAS, people with accounts on your identity provider (IdP) do not consume a user license until the person signs into {% data variables.location.product_location %}. {% data reusables.enterprise_user_management.built-in-authentication %} -## 使用 CAS 时的用户名考量因素 +## Username considerations with CAS -{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} 有关详细信息,请参阅“[外部身份验证的用户名注意事项](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)”。 +{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)." -## CAS 属性 +## CAS attributes -以下属性可用。 +The following attributes are available. -| 特性名 | 类型 | 说明 | +| Attribute name | Type | Description | |--------------------------|----------|-------------| -| `username` | 必需 | {% data variables.product.prodname_ghe_server %} 用户名。 | +| `username` | Required | The {% data variables.product.prodname_ghe_server %} username. | -## 配置 CAS +## Configuring CAS -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.authentication %} -3. 选择“CAS”。 +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.authentication %} +3. Select **CAS**. - ![用于身份验证的 CAS 选择的屏幕截图](/assets/images/enterprise/management-console/cas-select.png) + ![Screenshot of selection of CAS for authentication](/assets/images/enterprise/management-console/cas-select.png) 4. {% data reusables.enterprise_user_management.built-in-authentication-option %} - ![CAS 的回退内置身份验证选项的屏幕截图](/assets/images/enterprise/management-console/cas-built-in-authentication.png) -5. 在“服务器 URL”字段中,键入 CAS 服务器的完整 URL。 如果 {% data variables.product.prodname_ghe_server %} 无法验证 CAS 服务器使用的证书,可以使用 `ghe-ssl-ca-certificate-install` 命令将其安装为受信任的证书。 有关详细信息,请参阅“[命令行实用程序](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-ssl-ca-certificate-install)”。 + ![Screenshot of of fallback built-in authentication option for CAS](/assets/images/enterprise/management-console/cas-built-in-authentication.png) +5. In the **Server URL** field, type the full URL of your CAS server. If your CAS server uses a certificate that can't be validated by {% data variables.product.prodname_ghe_server %}, you can use the `ghe-ssl-ca-certificate-install` command to install it as a trusted certificate. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-ssl-ca-certificate-install)." diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md index 1444925cd5..90a11171f2 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md @@ -22,9 +22,9 @@ topics: With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access for the user accounts from your IdP. -In your IdP, you can give each {% data variables.product.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.product.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.product.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." +In your IdP, you can give each {% data variables.enterprise.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.enterprise.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.enterprise.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." -Organization membership can be managed manually, or you can update membership automatically as {% data variables.product.prodname_managed_users %} are added to IdP groups that are connected to teams within the organization. When a {% data variables.product.prodname_managed_user %} is manually added to an organization, unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization. For more information about managing organization and team membership automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)." +Organization membership can be managed manually, or you can update membership automatically as {% data variables.enterprise.prodname_managed_users %} are added to IdP groups that are connected to teams within the organization. When a {% data variables.enterprise.prodname_managed_user %} is manually added to an organization, unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization. For more information about managing organization and team membership automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)." {% ifversion oidc-for-emu %} @@ -32,11 +32,11 @@ Organization membership can be managed manually, or you can update membership au {% endif %} -You can grant {% data variables.product.prodname_managed_users %} access to and the ability to contribute to repositories within your enterprise, but {% data variables.product.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. For more information, see "[Abilities and restrictions of {% data variables.product.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users)." +You can grant {% data variables.enterprise.prodname_managed_users %} access to and the ability to contribute to repositories within your enterprise, but {% data variables.enterprise.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. For more information, see "[Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users)." -The usernames of your enterprise's {% data variables.product.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)." +The usernames of your enterprise's {% data variables.enterprise.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)." -Enterprise owners can audit all of the {% data variables.product.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}. For more information, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise)." +Enterprise owners can audit all of the {% data variables.enterprise.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}. For more information, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise)." To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. For more information about creating this account, see "[About enterprises with managed users](#about-enterprises-with-managed-users)." @@ -60,24 +60,25 @@ To use {% data variables.product.prodname_emus %}, you need a separate type of e {% endif %} -## Abilities and restrictions of {% data variables.product.prodname_managed_users %} +## Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %} -{% data variables.product.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.product.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. These visibility and access restrictions for users and content apply to all requests, including API requests. +{% data variables.enterprise.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.enterprise.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. These visibility and access restrictions for users and content apply to all requests, including API requests. -* {% data variables.product.prodname_managed_users_caps %} cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.product.prodname_managed_users %} be invited to other enterprises. +* {% data variables.enterprise.prodname_managed_users_caps %} cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.enterprise.prodname_managed_users %} be invited to other enterprises. * Outside collaborators are not supported by {% data variables.product.prodname_emus %}. -* {% data variables.product.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise. -* {% data variables.product.prodname_managed_users_caps %} can view all public repositories on {% data variables.product.prodname_dotcom_the_website %}, but cannot push code to repositories outside of the enterprise. -* {% data variables.product.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise. -* {% data variables.product.prodname_managed_users_caps %} cannot follow users outside of the enterprise. -* {% data variables.product.prodname_managed_users_caps %} cannot create gists or comment on gists. -* {% data variables.product.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts. -* Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.product.prodname_managed_user %} to collaborate. -* You can choose whether {% data variables.product.prodname_managed_users %} are able to create repositories owned by their user accounts. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)." -* If you allow {% data variables.product.prodname_managed_users %} to create repositories owned by their user accounts, they can only own private repositories and can only invite other enterprise members to collaborate on their user-owned repositories. +* {% data variables.enterprise.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise. +* {% data variables.enterprise.prodname_managed_users_caps %} can view all public repositories on {% data variables.product.prodname_dotcom_the_website %}, but cannot push code to repositories outside of the enterprise. +* {% data variables.enterprise.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise. +* {% data variables.enterprise.prodname_managed_users_caps %} cannot follow users outside of the enterprise. +* {% data variables.enterprise.prodname_managed_users_caps %} cannot create gists or comment on gists. +* {% data variables.enterprise.prodname_managed_users_caps %} cannot create starter workflows for {% data variables.product.prodname_actions %}. +* {% data variables.enterprise.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts. +* Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.enterprise.prodname_managed_user %} to collaborate. +* You can choose whether {% data variables.enterprise.prodname_managed_users %} are able to create repositories owned by their user accounts. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)." +* If you allow {% data variables.enterprise.prodname_managed_users %} to create repositories owned by their user accounts, they can only own private repositories and can only invite other enterprise members to collaborate on their user-owned repositories. * {% data reusables.enterprise-accounts.emu-forks %} -* Only private and internal repositories can be created in organizations owned by an {% data variables.product.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings. -* {% data variables.product.prodname_managed_users_caps %} are limited in their use of {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)." +* Only private and internal repositories can be created in organizations owned by an {% data variables.enterprise.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings. +* {% data variables.enterprise.prodname_managed_users_caps %} are limited in their use of {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)." ## Getting started with {% data variables.product.prodname_emus %} @@ -85,7 +86,7 @@ Before your developers can use {% data variables.product.prodname_ghe_cloud %} w 1. To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. To try out {% data variables.product.prodname_emus %} or to discuss options for migrating from your existing enterprise, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). - Your contact on the GitHub Sales team will work with you to create your new {% data variables.product.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)." + Your contact on the GitHub Sales team will work with you to create your new {% data variables.enterprise.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)." 2. After we create your enterprise, you will receive an email from {% data variables.product.prodname_dotcom %} inviting you to choose a password for your enterprise's setup user, which will be the first owner in the enterprise. Use an incognito or private browsing window when setting the password. The setup user is only used to configure single sign-on and SCIM provisioning integration for the enterprise. It will no longer have access to administer the enterprise account once SSO is successfully enabled. The setup user's username is your enterprise's shortcode suffixed with `_admin`. @@ -112,17 +113,17 @@ Before your developers can use {% data variables.product.prodname_ghe_cloud %} w 5. Once authentication and provisioning are configured, you can start provisioning members and managing teams. For more information, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)." -If members of your enterprise must use one workstation to contribute to repositories on {% data variables.product.product_location %} from both a {% data variables.product.prodname_managed_user %} and a personal account, you can provide support. For more information, see "[Supporting developers with multiple user accounts on {% data variables.product.prodname_dotcom_the_website %}](#supporting-developers-with-multiple-user-accounts-on-githubcom)." +If members of your enterprise must use one workstation to contribute to repositories on {% data variables.location.product_location %} from both a {% data variables.enterprise.prodname_managed_user %} and a personal account, you can provide support. For more information, see "[Supporting developers with multiple user accounts on {% data variables.product.prodname_dotcom_the_website %}](#supporting-developers-with-multiple-user-accounts-on-githubcom)." -## Authenticating as a {% data variables.product.prodname_managed_user %} +## Authenticating as a {% data variables.enterprise.prodname_managed_user %} -{% data variables.product.prodname_managed_users_caps %} must authenticate through their identity provider. To authenticate, a {% data variables.product.prodname_managed_user %} can visit their IdP application portal or use the login page on {% data variables.product.prodname_dotcom_the_website %}. +{% data variables.enterprise.prodname_managed_users_caps %} must authenticate through their identity provider. To authenticate, a {% data variables.enterprise.prodname_managed_user %} can visit their IdP application portal or use the login page on {% data variables.product.prodname_dotcom_the_website %}. By default, when an unauthenticated user attempts to access an enterprise that uses {% data variables.product.prodname_emus %}, {% data variables.product.company_short %} displays a 404 error. An enterprise owner can optionally enable automatic redirects to single sign-on (SSO) instead of the 404. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)." {% data reusables.enterprise-accounts.about-recovery-codes %} For more information, see "[Managing recovery codes for your enterprise](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)." -### Authenticating as a {% data variables.product.prodname_managed_user %} via {% data variables.product.prodname_dotcom_the_website %} +### Authenticating as a {% data variables.enterprise.prodname_managed_user %} via {% data variables.product.prodname_dotcom_the_website %} 1. Navigate to [https://github.com/login](https://github.com/login). 1. In the "Username or email address" text box, enter your username including the underscore and short code. @@ -137,10 +138,10 @@ By default, when an unauthenticated user attempts to access an enterprise that u A conflict may occur when provisioning users if the unique parts of the identifier provided by your IdP are removed during normalization. {% data reusables.enterprise-accounts.emu-only-emails-within-the-enterprise-can-conflict %} If you're unable to provision a user due to a username conflict, you should modify the username provided by your IdP. For more information, see "[Resolving username conflicts](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-conflicts)." -The profile name and email address of a {% data variables.product.prodname_managed_user %} is also provided by the IdP. {% data variables.product.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}, and the IdP can only provide a single email address. +The profile name and email address of a {% data variables.enterprise.prodname_managed_user %} is also provided by the IdP. {% data variables.enterprise.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}, and the IdP can only provide a single email address. -## Supporting developers with multiple user accounts on {% data variables.product.product_location %} +## Supporting developers with multiple user accounts on {% data variables.location.product_location %} -People on your team may need to contribute to resources on {% data variables.product.product_location %} that are outside of your {% data variables.product.prodname_emu_enterprise %}. For example, you may wish to maintain a separate enterprise for your company's open source projects. Because a {% data variables.product.prodname_managed_user %} cannot contribute to public resources, users will need to maintain a separate, personal account for this work. +People on your team may need to contribute to resources on {% data variables.location.product_location %} that are outside of your {% data variables.enterprise.prodname_emu_enterprise %}. For example, you may wish to maintain a separate enterprise for your company's open source projects. Because a {% data variables.enterprise.prodname_managed_user %} cannot contribute to public resources, users will need to maintain a separate, personal account for this work. -People who must contribute from two user accounts on {% data variables.product.product_location %} using one workstation can configure Git to simplify the process. For more information, see "[Managing multiple accounts](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)." +People who must contribute from two user accounts on {% data variables.location.product_location %} using one workstation can configure Git to simplify the process. For more information, see "[Managing multiple accounts](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)." diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md index 28d9c00c89..74dd43ee44 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md @@ -18,7 +18,7 @@ topics: {% data reusables.enterprise-accounts.emu-cap-validates %} -CAP support is enabled automatically for any {% data variables.product.prodname_emu_enterprise %} that enables OIDC SSO and cannot be disabled. {% data variables.product.prodname_dotcom %} enforces your IdP's IP conditions but not device compliance conditions. +CAP support is enabled automatically for any {% data variables.enterprise.prodname_emu_enterprise %} that enables OIDC SSO and cannot be disabled. {% data variables.product.prodname_dotcom %} enforces your IdP's IP conditions but not device compliance conditions. For more information about using OIDC with {% data variables.product.prodname_emus %}, see "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)" and "[Migrating from SAML to OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)." @@ -36,9 +36,9 @@ For more information about using OIDC with {% data variables.product.prodname_em ### {% data variables.product.prodname_actions %} -Actions that use a personal access token will likely be blocked by your IdP's CAP. We recommend that personal access tokens are created by a service account which is then exempted from IP controls in your IdP's CAP. +Actions that use a {% data variables.product.pat_generic %} will likely be blocked by your IdP's CAP. We recommend that {% data variables.product.pat_generic %}s are created by a service account which is then exempted from IP controls in your IdP's CAP. -If you're unable to use a service account, another option for unblocking actions that use personal access tokens is to allow the IP ranges used by {% data variables.product.prodname_actions %}. For more information, see "[About GitHub's IP addresses](/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses)." +If you're unable to use a service account, another option for unblocking actions that use {% data variables.product.pat_generic %}s is to allow the IP ranges used by {% data variables.product.prodname_actions %}. For more information, see "[About GitHub's IP addresses](/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses)." ### {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md index a96b9c5234..66e9c9d84f 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md @@ -1,7 +1,7 @@ --- -title: 为企业托管用户配置 OIDC +title: Configuring OIDC for Enterprise Managed Users shortTitle: OIDC for managed users -intro: '可以通过配置 OpenID Connect (OIDC) 单一登录 (SSO) 自动管理对 {% data variables.product.prodname_dotcom %} 上的企业帐户的访问,并启用对 IdP 的条件访问策略 (CAP) 的支持。' +intro: 'You can automatically manage access to your enterprise account on {% data variables.product.prodname_dotcom %} by configuring OpenID Connect (OIDC) single sign-on (SSO) and enable support for your IdP''s Conditional Access Policy (CAP).' product: '{% data reusables.gated-features.emus %}' versions: feature: oidc-for-emu @@ -10,42 +10,40 @@ topics: - Authentication - Enterprise - SSO -ms.openlocfilehash: d52626ad035d957a7908e07e81d12824b9601ee5 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147061776' --- + {% data reusables.enterprise-accounts.oidc-beta-notice %} -## 关于适用于企业托管用户的 OIDC +## About OIDC for Enterprise Managed Users -通过 {% data variables.product.prodname_emus %},企业使用标识提供者 (IdP) 对所有成员进行身份验证。 可以使用 OpenID Connect (OIDC) 管理 {% data variables.product.prodname_emu_enterprise %} 的身份验证。 启用 OIDC SSO 是一个一键式设置过程,证书由 {% data variables.product.prodname_dotcom %} 和你的 IdP 管理。 +With {% data variables.product.prodname_emus %}, your enterprise uses your identity provider (IdP) to authenticate all members. You can use OpenID Connect (OIDC) to manage authentication for your {% data variables.enterprise.prodname_emu_enterprise %}. Enabling OIDC SSO is a one-click setup process with certificates managed by {% data variables.product.prodname_dotcom %} and your IdP. -{% data reusables.enterprise-accounts.emu-cap-validates %} 有关详细信息,请参阅“[关于对 IdP 的条件访问策略的支持](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)”。 +{% data reusables.enterprise-accounts.emu-cap-validates %} For more information, see "[About support for your IdP's Conditional Access Policy](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)." -可以通过从 IdP 更改为 {% data variables.product.prodname_dotcom %} 颁发的 ID 令牌的生存期属性,调整会话的生存期,以及 {% data variables.product.prodname_managed_user %} 对 IdP 重新进行身份验证的频率。 默认生存期为 1 小时。 有关详细信息,请参阅 Azure AD 文档中的“[Microsoft 标识平台中的可配置令牌生存期](https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-lifetimes)”。 +You can adjust the lifetime of a session, and how often a {% data variables.enterprise.prodname_managed_user %} needs to reauthenticate with your IdP, by changing the lifetime policy property of the ID tokens issued for {% data variables.product.prodname_dotcom %} from your IdP. The default lifetime is one hour. For more information, see "[Configurable token lifetimes in the Microsoft identity platform](https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-lifetimes)" in the Azure AD documentation. -如果目前使用 SAML SSO 进行身份验证,并且更希望使用 OIDC 并受益于 CAP 支持,则可以遵循迁移路径。 有关详细信息,请参阅“[从 SAML 迁移到 OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)”。 +If you currently use SAML SSO for authentication and would prefer to use OIDC and benefit from CAP support, you can follow a migration path. For more information, see "[Migrating from SAML to OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)." {% data reusables.enterprise-accounts.oidc-gei-warning %} -## 标识提供者支持 +## Identity provider support -对 OIDC 的支持为公共 beta 版,使用 Azure Active Directory (Azure AD) 的客户都可使用。 +Support for OIDC is in public beta and available for customers using Azure Active Directory (Azure AD). -每个 Azure AD 租户只能支持一个与 {% data variables.product.prodname_emus %} 的 OIDC 集成。 如果要将 Azure AD 连接到 {% data variables.product.prodname_dotcom %} 上的多个企业,请改用 SAML。 有关详细信息,请参阅“[为 {% data variables.product.prodname_emus %} 配置 SAML 单一登录](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users)”。 +Each Azure AD tenant can support only one OIDC integration with {% data variables.product.prodname_emus %}. If you want to connect Azure AD to more than one enterprise on {% data variables.product.prodname_dotcom %}, use SAML instead. For more information, see "[Configuring SAML single sign-on for {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users)." -## 为企业托管用户配置 OIDC +## Configuring OIDC for Enterprise Managed Users -1. 使用用户名“@SHORT-CODE_admin”以新企业的安装用户身份登录到 {% data variables.product.prodname_dotcom_the_website %}。 -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} -1. 选择“要求 OIDC 单一登录”。 - ![显示“要求 OIDC 单一登录”复选框的屏幕截图](/assets/images/help/enterprises/require-oidc.png) -1. 若要继续设置并重定向到 Azure AD,请单击“保存”。 -{% data reusables.enterprise-accounts.emu-azure-admin-consent %} {% data reusables.enterprise-accounts.download-recovery-codes %} +1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@SHORT-CODE_admin**. +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +1. Select **Require OIDC single sign-on**. + ![Screenshot showing the "Require OIDC single sign-on" checkbox](/assets/images/help/enterprises/require-oidc.png) +1. To continue setup and be redirected to Azure AD, click **Save**. +{% data reusables.enterprise-accounts.emu-azure-admin-consent %} +{% data reusables.enterprise-accounts.download-recovery-codes %} -## 启用设置 +## Enabling provisioning -启用 OIDC SSO 后,启用预配。 有关详细信息,请参阅“[为企业托管用户配置 SCIM 预配](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)”。 +After you enable OIDC SSO, enable provisioning. For more information, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)." diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md index 37c8934f17..fe4dde3d44 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md @@ -1,7 +1,7 @@ --- -title: 为企业托管用户配置 SAML 单一登录 +title: Configuring SAML single sign-on for Enterprise Managed Users shortTitle: SAML for managed users -intro: '可以通过配置安全断言标记语言 (SAML) 单一登录 (SSO) 来自动管理对 {% data variables.product.prodname_dotcom %} 上企业帐户的访问。' +intro: 'You can automatically manage access to your enterprise account on {% data variables.product.prodname_dotcom %} by configuring Security Assertion Markup Language (SAML) single sign-on (SSO).' product: '{% data reusables.gated-features.emus %}' redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users @@ -15,34 +15,29 @@ topics: - Authentication - Enterprise - SSO -ms.openlocfilehash: 8464afda7b87f23d7466851901536668c4440944 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145955501' --- -## 关于 {% data variables.product.prodname_emus %} 的 SAML 单一登录 -通过 {% data variables.product.prodname_emus %},企业使用 SAML SSO 对所有成员进行身份验证。 你的企业成员将通过 IdP 登录,而不是使用 {% data variables.product.prodname_dotcom %} 用户名和密码登录到 {% data variables.product.prodname_dotcom %}。 +## About SAML single sign-on for {% data variables.product.prodname_emus %} -{% data variables.product.prodname_emus %} 支持以下 IdP: +With {% data variables.product.prodname_emus %}, your enterprise uses SAML SSO to authenticate all members. Instead of signing in to {% data variables.product.prodname_dotcom %} with a {% data variables.product.prodname_dotcom %} username and password, members of your enterprise will sign in through your IdP. + +{% data variables.product.prodname_emus %} supports the following IdPs: {% data reusables.enterprise-accounts.emu-supported-idps %} -配置 SAML SSO 后,我们建议存储恢复代码,以便在标识提供者不可用时恢复对企业的访问权限。 +After you configure SAML SSO, we recommend storing your recovery codes so you can recover access to your enterprise in the event that your identity provider is unavailable. {% note %} -注意:启用 SAML SSO 后,可在 {% data variables.product.prodname_dotcom %} 上为现有的 SAML 配置所更新的唯一设置是 SAML 证书。 如果需要更新登录 URL 或颁发者,必须首先禁用 SAML SSO,然后使用新设置重新配置 SAML SSO。 +**Note:** When SAML SSO is enabled, the only setting you can update on {% data variables.product.prodname_dotcom %} for your existing SAML configuration is the SAML certificate. If you need to update the Sign on URL or Issuer, you must first disable SAML SSO and then reconfigure SAML SSO with the new settings. {% endnote %} -## 配置 {% data variables.product.prodname_emus %} 的 SAML 单一登录 +## Configuring SAML single sign-on for {% data variables.product.prodname_emus %} -要为 {% data variables.product.prodname_emu_enterprise %} 配置 SAML SSO,需要在 IdP 上配置应用程序,然后在 GitHub.com 上配置企业。 配置 SAML SSO 后,可以配置用户预配。 +To configure SAML SSO for your {% data variables.enterprise.prodname_emu_enterprise %}, you must configure an application on your IdP and then configure your enterprise on GitHub.com. After you configure SAML SSO, you can configure user provisioning. -要在 IdP 上安装和配置 {% data variables.product.prodname_emu_idp_application %} 应用程序,必须在受支持的 IdP 上拥有租户和管理访问权限。 +To install and configure the {% data variables.product.prodname_emu_idp_application %} application on your IdP, you must have a tenant and administrative access on a supported IdP. {% note %} @@ -50,71 +45,73 @@ ms.locfileid: '145955501' {% endnote %} -1. [配置标识提供者](#configuring-your-identity-provider) -2. [配置企业](#configuring-your-enterprise) -3. [启用设置](#enabling-provisioning) +1. [Configuring your identity provider](#configuring-your-identity-provider) +2. [Configuring your enterprise](#configuring-your-enterprise) +3. [Enabling provisioning](#enabling-provisioning) -### 配置标识提供者 +### Configuring your identity provider -要配置 IdP,请按照他们提供的说明在 IdP 上配置 {% data variables.product.prodname_emu_idp_application %} 应用程序。 +To configure your IdP, follow the instructions they provide for configuring the {% data variables.product.prodname_emu_idp_application %} application on your IdP. -1. 要安装 {% data variables.product.prodname_emu_idp_application %} 应用程序,请单击下面的 IdP 链接: +1. To install the {% data variables.product.prodname_emu_idp_application %} application, click the link for your IdP below: - - [Azure Active Directory 上的 {% data variables.product.prodname_emu_idp_application %} 应用程序](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/aad.githubenterprisemanageduser?tab=Overview) - - [Okta 上的 {% data variables.product.prodname_emu_idp_application %} 应用程序](https://www.okta.com/integrations/github-enterprise-managed-user) + - [{% data variables.product.prodname_emu_idp_application %} application on Azure Active Directory](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/aad.githubenterprisemanageduser?tab=Overview) + - [{% data variables.product.prodname_emu_idp_application %} application on Okta](https://www.okta.com/integrations/github-enterprise-managed-user) -1. 要配置 {% data variables.product.prodname_emu_idp_application %} 应用程序和 IdP,请单击以下链接,并按照 IdP 提供的说明进行操作: +1. To configure the {% data variables.product.prodname_emu_idp_application %} application and your IdP, click the link below and follow the instructions provided by your IdP: - - [{% data variables.product.prodname_emus %} 的 Azure Active Directory 教程](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-tutorial) - - [{% data variables.product.prodname_emus %} 的 Okta 文档](https://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-GitHub-Enterprise-Managed-User.html) + - [Azure Active Directory tutorial for {% data variables.product.prodname_emus %}](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-tutorial) + - [Okta documentation for {% data variables.product.prodname_emus %}](https://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-GitHub-Enterprise-Managed-User.html) -1. 因此,你可以测试和配置企业,将自己或将在 {% data variables.product.prodname_dotcom %} 上配置 SAML SSO 的用户分配到 IdP 上的 {% data variables.product.prodname_emu_idp_application %} 应用程序。 +1. So you can test and configure your enterprise, assign yourself or the user that will be configuring SAML SSO on {% data variables.product.prodname_dotcom %} to the {% data variables.product.prodname_emu_idp_application %} application on your IdP. -1. 若要能够继续在 {% data variables.product.prodname_dotcom %} 上配置企业,请找到并记下在 IdP 上安装的应用程序的以下信息: +1. To enable you to continue configuring your enterprise on {% data variables.product.prodname_dotcom %}, locate and note the following information from the application you installed on your IdP: - | 值 | 其他名称 | 说明 | + | Value | Other names | Description | | :- | :- | :- | - | IdP 登录 URL | 登录 URL、IdP URL | IdP 上的应用程序的 URL | - | IdP 标识符 URL | 颁发者 | 用于 SAML 身份验证的服务提供商的 IdP 标识符 | - | 签名证书,Base64 编码 | 公用证书 | IdP 用于对身份验证请求进行签名的公共证书 | + | IdP Sign-On URL | Login URL, IdP URL | Application's URL on your IdP | + | IdP Identifier URL | Issuer | IdP's identifier to service providers for SAML authentication | + | Signing certificate, Base64-encoded | Public certificate | Public certificate that IdP uses to sign authentication requests | -### 配置企业 +### Configuring your enterprise -在标识提供者上安装并配置 {% data variables.product.prodname_emu_idp_application %} 应用程序之后,便可以配置企业。 +After you install and configure the {% data variables.product.prodname_emu_idp_application %} application on your identity provider, you can configure your enterprise. -1. 使用用户名“@SHORT-CODE_admin”以新企业的安装用户身份登录到 {% data variables.product.prodname_dotcom_the_website %}。 +1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@SHORT-CODE_admin**. -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} -1. 在“SAML 单一登录”下,选择“要求 SAML 身份验证”。 - ![用于启用 SAML SSO 的复选框](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) +1. Under "SAML single sign-on", select **Require SAML authentication**. + ![Checkbox for enabling SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) -1. 在“登录 URL”下,键入在配置 IdP 时记下的用于单一登录请求的 IdP 的 HTTPS 终结点。 -![登录时将成员转发到的 URL 字段](/assets/images/help/saml/saml_sign_on_url_business.png) +1. Under **Sign on URL**, type the HTTPS endpoint of your IdP for single sign-on requests that you noted while configuring your IdP. +![Field for the URL that members will be forwarded to when signing in](/assets/images/help/saml/saml_sign_on_url_business.png) -1. (可选)在“颁发者”字段下,输入在配置 IdP 时记下的 SAML 颁发者 URL,以验证发送的消息的真实性。 -![SAML 颁发者的姓名字段](/assets/images/help/saml/saml_issuer.png) +1. Under **Issuer**, type your SAML issuer URL that you noted while configuring your IdP, to verify the authenticity of sent messages. +![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png) -1. 在“公共证书”下,粘贴在配置 IdP 时记下的证书以验证 SAML 响应。 -![标识提供程序的公共证书字段](/assets/images/help/saml/saml_public_certificate.png) +1. Under **Public Certificate**, paste the certificate that you noted while configuring your IdP, to verify SAML responses. +![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png) -1. 要验证来自 SAML 签发者的请求的完整性,请单击 {% octicon "pencil" aria-label="The edit icon" %}。 然后,在“签名方法”和“摘要方法”下拉菜单中,选择 SAML 签发者使用的哈希算法。 -![SAML 颁发者使用的签名方法和摘要方法哈希算法下拉列表](/assets/images/help/saml/saml_hashing_method.png) +1. To verify the integrity of the requests from your SAML issuer, click {% octicon "pencil" aria-label="The edit icon" %}. Then, in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. +![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png) -1. 在为企业启用 SAML SSO 之前,单击“测试 SMAL 配置”,以确保已输入的信息正确。 ![实施前测试 SAML 配置的按钮](/assets/images/help/saml/saml_test.png) +1. Before enabling SAML SSO for your enterprise, to ensure that the information you've entered is correct, click **Test SAML configuration**. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png) -1. 单击“ **保存**”。 +1. Click **Save**. {% note %} - 注意:当企业需要 SAML SSO 时,安装用户将不再有权访问企业,但将保持登录到 GitHub。 只有 IdP 预配的 {% data variables.product.prodname_managed_users %} 才能访问企业。 + **Note:** When you require SAML SSO for your enterprise, the setup user will no longer have access to the enterprise but will remain signed in to GitHub. Only {% data variables.enterprise.prodname_managed_users %} provisioned by your IdP will have access to the enterprise. {% endnote %} {% data reusables.enterprise-accounts.download-recovery-codes %} -### 启用设置 +### Enabling provisioning -启用 SAML SSO 后,启用预配。 有关详细信息,请参阅“[为企业托管用户配置 SCIM 预配](//admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)”。 +After you enable SAML SSO, enable provisioning. For more information, see "[Configuring SCIM provisioning for enterprise managed users](//admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)." diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md index 8bc19c1377..dddd160ff4 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md @@ -1,7 +1,7 @@ --- -title: 使用 Okta 为企业托管用户配置 SCIM 预配 +title: Configuring SCIM provisioning for Enterprise Managed Users with Okta shortTitle: Set up provisioning with Okta -intro: 您可以使用 Okta 作为身份提供商来预配新用户并管理其企业和团队的成员身份。 +intro: You can provision new users and manage their membership of your enterprise and teams using Okta as your identity provider. product: '{% data reusables.gated-features.emus %}' versions: ghec: '*' @@ -17,86 +17,81 @@ topics: - Authentication - Enterprise - SSO -ms.openlocfilehash: 11cfbf1b5d5a3e23b3d911375aa8ba6826d48817 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147444933' --- -## 关于使用 Okta 进行预配 -您可以使用 {% data variables.product.prodname_emus %} Okta 作为您的身份提供商来预配新帐户、管理企业成员身份以及管理企业中组织的团队成员身份。 有关预配 {% data variables.product.prodname_emus %} 的详细信息,请参阅“[为 Enterprise Managed User 配置 SCIM 预配](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)”。 +## About provisioning with Okta -在使用 Okta 配置预配之前,必须配置 SAML 单点登录。 有关详细信息,请参阅“[为 Enterprise Managed User 配置 SAML 单一登录](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)”。 +You can use {% data variables.product.prodname_emus %} with Okta as your identity provider to provision new accounts, manage enterprise membership, and manage team memberships for organizations in your enterprise. For more information about provisioning for {% data variables.product.prodname_emus %}, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)." -要使用 Okta 配置预配,必须在 {% data variables.product.prodname_emu_idp_application %} 应用程序中设置企业名称,并输入安装用户的个人访问令牌。 然后,您可以在 Okta 中开始预配用户。 +Before you can configure provisioning with Okta, you must configure SAML single-sign on. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)." -## 支持的功能 +To configure provisioning with Okta, you must set your enterprise's name in the {% data variables.product.prodname_emu_idp_application %} application and enter your setup user's {% data variables.product.pat_generic %}. You can then start provisioning users in Okta. -{% data variables.product.prodname_emus %} 支持 Okta 中的许多预配功能。 +## Supported features -| 功能 | 说明 | +{% data variables.product.prodname_emus %} supports many provisioning features in Okta. + +| Feature | Description | | --- | --- | -| 推送新用户 | 分配给 Okta 中的 {% data variables.product.prodname_emu_idp_application %} 应用程序的用户将在 {% data variables.product.product_name %} 上自动创建。 | -| 推送配置文件更新 | 对 Okta 中的用户配置文件所做的更新将被推送到 {% data variables.product.product_name %}。 | -| 推送组 | Okta 中作为推送组分配给 {% data variables.product.prodname_emu_idp_application %} 应用程序的组将在 {% data variables.product.product_name %} 上自动创建。 | -| 推送用户停用 | 从 Okta 中的 {% data variables.product.prodname_emu_idp_application %} 应用程序中取消分配用户将在 {% data variables.product.product_name %} 上禁用该用户。 用户将无法登录,但会保留用户的信息。 | -| 重新激活用户 | 将启用 Okta 中已重新激活其 Okta 帐户并将其分配回 {% data variables.product.prodname_emu_idp_application %} 应用程序的用户。 | +| Push New Users | Users that are assigned to the {% data variables.product.prodname_emu_idp_application %} application in Okta are automatically created in the enterprise on {% data variables.product.product_name %}. | +| Push Profile Update | Updates made to the user's profile in Okta will be pushed to {% data variables.product.product_name %}. | +| Push Groups | Groups in Okta that are assigned to the {% data variables.product.prodname_emu_idp_application %} application as Push Groups are automatically created in the enterprise on {% data variables.product.product_name %}. | +| Push User Deactivation | Unassigning the user from the {% data variables.product.prodname_emu_idp_application %} application in Okta will disable the user on {% data variables.product.product_name %}. The user will not be able to sign in, but the user's information is maintained. | +| Reactivate Users | Users in Okta whose Okta accounts are reactivated and who are assigned back to the {% data variables.product.prodname_emu_idp_application %} application will be enabled. | {% note %} -**注意:** {% data variables.product.prodname_emus %} 不支持修改用户名。 +**Note:** {% data variables.product.prodname_emus %} does not support modifications to usernames. {% endnote %} -## 设置企业名称 +## Setting your enterprise name -创建 {% data variables.product.prodname_emu_enterprise %} 后,可以通过在 Okta 中设置企业名称来开始配置预配。 +After your {% data variables.enterprise.prodname_emu_enterprise %} has been created, you can begin to configure provisioning by setting your enterprise name in Okta. -1. 导航到 Okta 上的 {% data variables.product.prodname_emu_idp_application %} 应用程序。 -1. 单击“登录”选项卡。 -1. 若要进行更改,请单击“编辑”。 -1. 在“Advanced Sign-on Settings(高级登录设置)”下的“Enterprise Name(企业名称)”文本框中,键入您的企业名称。 例如,如果你在 `https://github.com/enterprises/octoinc` 访问你的企业,则你的企业名称将为“octoinc”。 -![Okta 上的“企业名称”字段的屏幕截图](/assets/images/help/enterprises/okta-emu-enterprise-name.png) -1. 若要保存企业名称,请单击“保存”。 +1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta. +1. Click the **Sign On** tab. +1. To make changes, click **Edit**. +1. Under "Advanced Sign-on Settings", in the "Enterprise Name" text box, type your enterprise name. For example, if you access your enterprise at `https://github.com/enterprises/octoinc`, your enterprise name would be "octoinc". +![Screenshot of the Enterprise Name field on Okta](/assets/images/help/enterprises/okta-emu-enterprise-name.png) +1. To save your enterprise name, click **Save**. -## 配置预配 +## Configuring provisioning -设置企业名称后,可以继续配置预配设置。 +After setting your enterprise name, you can proceed to configure provisioning settings. -若要配置预配,具有 @SHORT-CODE_admin 用户名的安装用户将需要提供 admin:enterprise 作用域的个人访问令牌 。 有关创建新令牌的详细信息,请参阅“[创建个人访问令牌](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)”。 +To configure provisioning, the setup user with the **@SHORT-CODE_admin** username will need to provide a {% data variables.product.pat_v1 %} with the **admin:enterprise** scope. For more information on creating a new token, see "[Creating a {% data variables.product.pat_generic %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)." -1. 导航到 Okta 上的 {% data variables.product.prodname_emu_idp_application %} 应用程序。 -1. 单击 **资源调配** 选项卡。 -1. 在“设置”菜单中,单击“集成”。 -1. 若要进行更改,请单击“编辑”。 -1. 选择“启用 API 集成”。 -1. 在“API 令牌”字段中,输入属于安装用户的作用域为 admin:enterprise 的个人访问令牌。 -![显示 Okta 上的 API 令牌字段的屏幕截图](/assets/images/help/enterprises/okta-emu-token.png) -1. 单击“测试 API 凭据”。 如果测试成功,屏幕顶部将显示一条验证消息。 -1. 若要保存令牌,请单击“保存”。 -1. 在“设置”菜单中,单击“转到应用”。 -![显示 Okta 上的“转到应用”菜单项的屏幕截图](/assets/images/help/enterprises/okta-emu-to-app-menu.png) -1. 在“预配到应用”的右侧,要允许进行更改,请单击“编辑”。 -1. 对于“创建用户”、“更新用户属性”和“停用用户”,选择“启用” 。 -![显示 Okta 上的预配选项的屏幕截图](/assets/images/help/enterprises/okta-emu-provisioning-to-app.png) -1. 若要完成配置预配,请单击“保存”。 +1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta. +1. Click the **Provisioning** tab. +1. In the settings menu, click **Integration**. +1. To make changes, click **Edit**. +1. Select **Enable API integration**. +1. In the "API Token" field, enter the {% data variables.product.pat_v1 %} with the **admin:enterprise** scope belonging to the setup user. +![Screenshot showing the API Token field on Okta](/assets/images/help/enterprises/okta-emu-token.png) +1. Click **Test API Credentials**. If the test is successful, a verification message will appear at the top of the screen. +1. To save the token, click **Save**. +1. In the settings menu, click **To App**. +![Screenshot showing the To App menu item on Okta](/assets/images/help/enterprises/okta-emu-to-app-menu.png) +1. To the right of "Provisioning to App", to allow changes to be made, click **Edit**. +1. Select **Enable** for **Create Users**, **Update User Attributes**, and **Deactivate Users**. +![Screenshot showing provisioning options on Okta](/assets/images/help/enterprises/okta-emu-provisioning-to-app.png) +1. To finish configuring provisioning, click **Save**. -## 分配用户和组 +## Assigning users and groups -配置 SAML SSO 和预配后,您可以通过将用户分配到 {% data variables.product.prodname_emu_idp_application %} 应用程序在 {% data variables.product.prodname_dotcom_the_website %} 上预配新用户。 +After you have configured SAML SSO and provisioning, you will be able provision new users on {% data variables.product.prodname_dotcom_the_website %} by assigning users to the {% data variables.product.prodname_emu_idp_application %} application. {% data reusables.scim.emu-scim-rate-limit %} -您还可以通过将组分配给应用程序并将其添加到 Okta 中的“Push Groups(推送组)”选项卡来自动管理组织成员身份。 成功预配组后,该组将可用于连接到企业组织中的团队。 有关管理团队的详细信息,请参阅“[使用标识提供者组管理团队成员身份](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)”。 +You can also automatically manage organization membership by assigning groups to the application and adding them to the "Push Groups" tab in Okta. When the group is provisioned successfully, it will be available to connect to teams in the enterprise's organizations. For more information about managing teams, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)." -分配用户时,可以使用 {% data variables.product.prodname_emu_idp_application %} 应用程序中的“角色”属性在 {% data variables.product.product_name %} 上设置用户在企业中的角色。 有关角色的详细信息,请参阅“[企业中的角色](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)”。 +When assigning users, you can use the "Roles" attribute in the {% data variables.product.prodname_emu_idp_application %} application to set a user's role in your enterprise on {% data variables.product.product_name %}. For more information on roles, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)." -![显示 Okta 上已预配用户的角色选项的屏幕截图](/assets/images/help/enterprises/okta-emu-user-role.png) +![Screenshot showing the role options for provisioned user on Okta](/assets/images/help/enterprises/okta-emu-user-role.png) -## 取消预配用户和组 +## Deprovisioning users and groups -若要从 {% data variables.product.product_name %} 中删除用户或组,请从 Okta 的“分配”选项卡和“推送组”选项卡中删除用户或组。 对于用户,请确保从“推送组”选项卡中的所有组中删除该用户。 +To remove a user or group from {% data variables.product.product_name %}, remove the user or group from both the "Assignments" tab and the "Push groups" tab in Okta. For users, make sure the user is removed from all groups in the "Push Groups" tab. diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md index 3293f5e6ba..af0d546dab 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md @@ -1,7 +1,7 @@ --- -title: 为 Enterprise Managed User 配置 SCIM 预配 +title: Configuring SCIM provisioning for Enterprise Managed Users shortTitle: Provisioning managed users -intro: 你可以配置标识提供者以预配新用户并管理其在企业和团队中的成员身份。 +intro: You can configure your identity provider to provision new users and manage their membership in your enterprise and teams. product: '{% data reusables.gated-features.emus %}' redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users @@ -13,58 +13,60 @@ versions: topics: - Accounts - Enterprise -ms.openlocfilehash: 3ce59680c100004496e761d2a93adc9e9cae0a22 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147881495' --- -## 关于 {% data variables.product.prodname_emus %} 的预配 -必须为 {% data variables.product.prodname_emus %} 配置预配才能为企业成员创建、管理和停用用户帐户。 为 {% data variables.product.prodname_emus %} 配置预配时,在标识提供者中分配给 {% data variables.product.prodname_emu_idp_application %} 应用程序的用户将通过 SCIM 预配为 {% data variables.product.prodname_dotcom %} 上的新用户帐户,并且这些用户将添加到你的企业中。 +## About provisioning for {% data variables.product.prodname_emus %} -在 IdP 上更新与用户标识关联的信息时,IdP 将在 GitHub.com 上更新用户的帐户。 从 {% data variables.product.prodname_emu_idp_application %} 应用程序取消分配用户或停用 IdP 上的用户帐户时,IdP 将与 {% data variables.product.prodname_dotcom %} 进行通信,以使任何会话失效并禁用该成员的帐户。 已禁用帐户的信息会保留,其用户名将更改为原始用户名的哈希,并追加短代码。 如果将用户重新分配到 {% data variables.product.prodname_emu_idp_application %} 应用程序或在 IdP 上重新激活其帐户,则会重新激活 {% data variables.product.prodname_dotcom %} 上的 {% data variables.product.prodname_managed_user %} 帐户,并还原用户名。 +You must configure provisioning for {% data variables.product.prodname_emus %} to create, manage, and deactivate user accounts for your enterprise members. When you configure provisioning for {% data variables.product.prodname_emus %}, users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your identity provider are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} via SCIM, and the users are added to your enterprise. -IdP 中的组可用于管理企业组织中的团队成员身份,使你可通过 IdP 配置存储库访问权限和权限。 有关详细信息,请参阅“[使用标识提供者组管理团队成员身份](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)”。 +When you update information associated with a user's identity on your IdP, your IdP will update the user's account on GitHub.com. When you unassign the user from the {% data variables.product.prodname_emu_idp_application %} application or deactivate a user's account on your IdP, your IdP will communicate with {% data variables.product.prodname_dotcom %} to invalidate any sessions and disable the member's account. The disabled account's information is maintained and their username is changed to a hash of their original username with the short code appended. If you reassign a user to the {% data variables.product.prodname_emu_idp_application %} application or reactivate their account on your IdP, the {% data variables.enterprise.prodname_managed_user %} account on {% data variables.product.prodname_dotcom %} will be reactivated and username restored. -## 先决条件 +Groups in your IdP can be used to manage team membership within your enterprise's organizations, allowing you to configure repository access and permissions through your IdP. For more information, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)." -在为 {% data variables.product.prodname_emus %} 配置预配之前,必须配置 SAML{% ifversion oidc-for-emu %} 或 OIDC{% endif %} 单一登录。 {% ifversion oidc-for-emu %} +## Prerequisites -- 有关配置 OIDC 的详细信息,请参阅“[为企业托管用户配置 OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)” -- {% endif %}有关配置 SAML 的详细信息,请参阅“[为企业托管用户配置 SAML 单一登录](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)”。 +Before you can configure provisioning for {% data variables.product.prodname_emus %}, you must configure SAML{% ifversion oidc-for-emu %} or OIDC{% endif %} single-sign on. {% ifversion oidc-for-emu %} -## 创建个人访问令牌 +- For more information on configuring OIDC, see "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)" +- {% endif %}For information on configuring SAML, see "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)." -若要为 {% data variables.product.prodname_emu_enterprise %} 配置预配,需要使用属于安装用户的 admin:enterprise 作用域的个人访问令牌。 +## Creating a {% data variables.product.pat_generic %} + +To configure provisioning for your {% data variables.enterprise.prodname_emu_enterprise %}, you need a {% data variables.product.pat_v1 %} with the **admin:enterprise** scope that belongs to the setup user. {% warning %} -**警告:** 如果令牌过期或预配的用户创建了令牌,SCIM 预配可能会意外停止工作。 请确保在以安装用户身份登录时创建令牌,并将令牌过期设置为“不过期”。 +**Warning:** If the token expires or a provisioned user creates the token, SCIM provisioning may unexpectedly stop working. Make sure that you create the token while signed in as the setup user and that the token expiration is set to "No expiration". {% endwarning %} -1. 使用用户名“@SHORT-CODE_admin”以新企业的安装用户身份登录到 {% data variables.product.prodname_dotcom_the_website %}。 -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.personal_access_tokens %} {% data reusables.user-settings.generate_new_token %} -1. 在“备注”下,为令牌提供描述性名称。 - ![显示令牌名称的屏幕截图](/assets/images/help/enterprises/emu-pat-name.png) -1. 选择“过期”下拉菜单,然后单击“不过期” 。 - ![显示将令牌过期设置为“不过期”的屏幕截图](/assets/images/help/enterprises/emu-pat-no-expiration.png) -1. 选择 admin:enterprise 作用域。 - ![显示 admin:enterprise 作用域的屏幕截图](/assets/images/help/enterprises/enterprise-pat-scope.png) -1. 单击“生成令牌”。 - ![生成令牌按钮](/assets/images/help/settings/generate_token.png) -1. 若要将令牌复制到剪贴板,请单击 {% octicon "paste" aria-label="The copy icon" %}。 - ![新建的令牌](/assets/images/help/settings/personal_access_tokens.png) -2. 若要保存令牌以供以后使用,请将新令牌安全地存储在密码管理器中。 +1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@SHORT-CODE_admin**. +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% data reusables.user-settings.personal_access_tokens %} +{% data reusables.user-settings.generate_new_token %} +1. Under **Note**, give your token a descriptive name. + ![Screenshot showing the token's name](/assets/images/help/enterprises/emu-pat-name.png) +1. Select the **Expiration** drop-down menu, then click **No expiration**. + ![Screenshot showing token expiration set to no expiration](/assets/images/help/enterprises/emu-pat-no-expiration.png) +1. Select the **admin:enterprise** scope. + ![Screenshot showing the admin:enterprise scope](/assets/images/help/enterprises/enterprise-pat-scope.png) +1. Click **Generate token**. + ![Generate token button](/assets/images/help/settings/generate_token.png) +1. To copy the token to your clipboard, click the {% octicon "paste" aria-label="The copy icon" %}. + ![Newly created token](/assets/images/help/settings/personal_access_tokens.png) +2. To save the token for use later, store the new token securely in a password manager. -## 为 {% data variables.product.prodname_emus %} 配置预配 +## Configuring provisioning for {% data variables.product.prodname_emus %} -创建个人访问令牌并安全地存储该令牌后,可以在标识提供者上配置预配。 +After creating your {% data variables.product.pat_generic %} and storing it securely, you can configure provisioning on your identity provider. {% data reusables.scim.emu-scim-rate-limit %} -若要配置预配,请遵循下表中的相应链接。 +To configure provisioning, follow the appropriate link from the table below. -| 标识提供者 | SSO 方法 | 详细信息 | |---|---|---|{% ifversion oidc-for-emu %} | Azure AD | OIDC | Azure AD 文档中的[教程:为 GitHub Enterprise Managed User (OIDC) 配置自动用户预配](https://docs.microsoft.com/azure/active-directory/saas-apps/github-enterprise-managed-user-oidc-provisioning-tutorial) |{% endif %} | Azure AD | SAML | Azure AD 文档中的[教程:为 GitHub Enterprise Managed User (OIDC) 配置自动用户预配](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-provisioning-tutorial) | |Okta |SAML | [使用 Okta 为企业托管用户配置 SCIM 预配](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users-with-okta) | +| Identity provider | SSO method | More information | +|---|---|---|{% ifversion oidc-for-emu %} +| Azure AD | OIDC | [Tutorial: Configure GitHub Enterprise Managed User (OIDC) for automatic user provisioning](https://docs.microsoft.com/azure/active-directory/saas-apps/github-enterprise-managed-user-oidc-provisioning-tutorial) in the Azure AD documentation |{% endif %} +| Azure AD | SAML | [Tutorial: Configure GitHub Enterprise Managed User for automatic user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-provisioning-tutorial) in the Azure AD documentation | +| Okta | SAML | [Configuring SCIM provisioning for Enterprise Managed Users with Okta](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users-with-okta) | diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md index 8d1a4ffd2b..e7306b64c7 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md @@ -1,7 +1,7 @@ --- -title: 使用标识提供者组管理团队成员身份 +title: Managing team memberships with identity provider groups shortTitle: Manage teams with your IdP -intro: '可通过将标识提供者 (IdP) 组连接到 {% data variables.product.prodname_emu_enterprise %},通过 IdP 管理 {% data variables.product.product_name %} 上的团队成员身份。' +intro: 'You can manage team membership on {% data variables.product.product_name %} through your identity provider (IdP) by connecting IdP groups with your {% data variables.enterprise.prodname_emu_enterprise %}.' product: '{% data reusables.gated-features.emus %}' redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups @@ -16,64 +16,67 @@ topics: - Enterprise - SSO - Teams -ms.openlocfilehash: 2ac4eed05fdac627f0846c11f3b9a03be3c693a0 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145955544' --- -## 关于使用 {% data variables.product.prodname_emus %} 的团队管理 -使用 {% data variables.product.prodname_emus %},可以通过 IdP 管理企业内的团队成员身份。 将某个企业组织中的团队连接到 IdP 组时,IdP 组对成员身份的更改会自动反映在企业中,从而减少手动更新和自定义脚本的需要。 +## About team management with {% data variables.product.prodname_emus %} -当 IdP 组的更改或新的团队连接导致 {% data variables.product.prodname_managed_user %} 加入他们尚未加入的组织中的团队时,{% data variables.product.prodname_managed_user %} 将自动添加到组织中。 组织所有者还可以手动管理组织成员身份。 当你断开组与团队的连接时,如果未通过任何其他方式为其分配组织成员身份,则通过团队成员身份成为组织成员的用户将从组织中删除。 +With {% data variables.product.prodname_emus %}, you can manage team membership within your enterprise through your IdP. When you connect a team in one of your enterprise's organizations to an IdP group, changes to membership from the IdP group are reflected in your enterprise automatically, reducing the need for manual updates and custom scripts. -可以将企业中的团队连接到一个 IdP 组。 可以将同一 IdP 组分配给企业中的多个团队。 +When a change to an IdP group or a new team connection results in a {% data variables.enterprise.prodname_managed_user %} joining a team in an organization they were not already a member of, the {% data variables.enterprise.prodname_managed_user %} will automatically be added to the organization. Organization owners can also manage organization membership manually. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization if they are not assigned membership in the organization by any other means. -如果要将现有团队连接到 IdP 组,必须先删除手动添加的任何成员。 将企业中的团队连接到 IdP 组后,IdP 管理员必须通过标识提供者更改团队成员身份。 无法在 {% data variables.product.prodname_dotcom_the_website %} 上管理团队成员身份。 +You can connect a team in your enterprise to one IdP group. You can assign the same IdP group to multiple teams in your enterprise. -当 Idp 上的组成员身份发生变化时,你的 IdP 会根据 IdP 确定的时间表发送 SCIM 请求,其中包含对 {% data variables.product.prodname_dotcom_the_website %} 的更改,因此更改可能不会立即发生。 任何更改团队或组织成员身份的请求都将在审核日志中注册为用于配置用户预配的帐户所做的更改。 +If you are connecting an existing team to an IdP group, you must first remove any members that were added manually. After you connect a team in your enterprise to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.prodname_dotcom_the_website %}. -连接到 IdP 组的团队不能是其他团队的父级,也不能是另一个团队的子级。 如果要连接到 IdP 组的团队是父团队或子团队,建议创建一个新团队或删除使你的团队成为父团队的嵌套关系。 +When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.prodname_dotcom_the_website %} according to the schedule determined by your IdP, so change may not be immediate. Any requests that change team or organization membership will register in the audit log as changes made by the account used to configure user provisioning. -若要管理企业中任何团队(包括连接到 IdP 组的团队)的存储库访问权限,必须对 {% data variables.product.prodname_dotcom_the_website %} 进行更改。 有关详细信息,请参阅“[管理团队对组织存储库的访问权限](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)”。 +Teams connected to IdP groups cannot be parents of other teams nor a child of another team. If the team you want to connect to an IdP group is a parent or child team, we recommend creating a new team or removing the nested relationships that make your team a parent team. -## 创建连接到 IdP 组的新团队 +To manage repository access for any team in your enterprise, including teams connected to an IdP group, you must make changes on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)". -组织的任何成员都可以创建新团队并将团队连接到 IdP 组。 +## Creating a new team connected to an IdP group -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.new_team %} {% data reusables.organizations.team_name %} {% data reusables.organizations.team_description %} -1. 若要连接团队,请选择“标识提供者组”下拉菜单,然后单击要连接的团队。 - ![用于选择标识提供者组的下拉菜单](/assets/images/help/teams/choose-an-idp-group.png) {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create_team %} +Any member of an organization can create a new team and connect the team to an IdP group. -## 管理现有团队和 IdP 组之间的连接 +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.new_team %} +{% data reusables.organizations.team_name %} +{% data reusables.organizations.team_description %} +1. To connect a team, select the "Identity Provider Groups" drop-down menu and click the team you want to connect. + ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png) +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create_team %} -组织所有者和团队维护者可以管理 IdP 组和团队之间的现有连接。 +## Managing the connection between an existing team and an IdP group + +Organization owners and team maintainers can manage the existing connection between an IdP group and a team. {% note %} -注意:在首次将 {% data variables.product.prodname_dotcom_the_website %} 上的现有团队连接到 IdP 组之前,必须先删除 {% data variables.product.prodname_dotcom_the_website %} 上的所有团队成员。 有关详细信息,请参阅“[从团队中删除组织成员](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)”。 +**Note**: Before you connect an existing team on {% data variables.product.prodname_dotcom_the_website %} to an IdP group for the first time, all members of the team on {% data variables.product.prodname_dotcom_the_website %} must first be removed. For more information, see "[Removing organization members from a team](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)." {% endnote %} {% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %} -1. (可选)在“标识提供者组”下,单击要断开连接的 IdP 组右侧的 {% octicon "x" aria-label="X symbol" %}。 - ![从 GitHub 团队取消选择已连接的 IdP 组](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png) -1. 若要连接 IdP 组,请在“标识提供者组”下选择下拉菜单,然后从列表中单击标识提供者组。 - ![用于选择标识提供者组的下拉菜单](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png) -1. 单击“保存更改”。 +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +1. Optionally, under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. + ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png) +1. To connect an IdP group, under "Identity Provider Group", select the drop-down menu, and click an identity provider group from the list. + ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png) +1. Click **Save changes**. -## 查看 IdP 组、组成员身份和连接的团队 +## Viewing IdP groups, group membership, and connected teams -可以查看 IdP 组列表,查看连接到 IdP 组的任何团队,并在 {% data variables.product.product_name %} 上查看每个 IdP 组的成员身份。 必须在 IdP 上编辑组的成员身份。 +You can review a list of IdP groups, see any teams connected to an IdP group, and see the membership of each IdP group on {% data variables.product.product_name %}. You must edit the membership for a group on your IdP. {% data reusables.enterprise-accounts.access-enterprise %} -1. 若要查看 IdP 组列表,请在左侧边栏中单击 {% octicon "key" aria-label="The key icon" %}“标识提供者”。 - ![显示企业侧栏中“标识提供者”选项卡的屏幕截图](/assets/images/help/enterprises/enterprise-account-identity-provider-tab.png) -2. 若要查看连接到 IdP 组的成员和团队,请单击该组的名称。 - ![显示 IdP 组列表的屏幕截图,其中突出显示了组名称](/assets/images/help/enterprises/select-idp-group.png) -4. 若要查看连接到 IdP 组的团队,请单击“团队”。 - ![显示“团队”按钮的屏幕截图](/assets/images/help/enterprises/idp-groups-team-switcher.png) +1. To review a list of IdP groups, in the left sidebar, click {% octicon "key" aria-label="The key icon" %} **Identity provider**. + ![Screenshot showing "Identity provider" tab in enterprise sidebar](/assets/images/help/enterprises/enterprise-account-identity-provider-tab.png) +2. To see the members and teams connected to an IdP group, click the group's name. + ![Screenshot showing list of IdP groups, the group name is highlighted](/assets/images/help/enterprises/select-idp-group.png) +4. To view the teams connected to the IdP group, click **Teams**. + ![Screenshot showing the "Teams" button](/assets/images/help/enterprises/idp-groups-team-switcher.png) diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md index f6e7cb1071..1d10031b84 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md @@ -1,7 +1,7 @@ --- title: Migrating from SAML to OIDC shortTitle: Migrating from SAML to OIDC -intro: 'If you''re using SAML to authenticate members in your {% data variables.product.prodname_emu_enterprise %}, you can migrate to OpenID Connect (OIDC) and benefit from support for your IdP''s Conditional Access Policy.' +intro: 'If you''re using SAML to authenticate members in your {% data variables.enterprise.prodname_emu_enterprise %}, you can migrate to OpenID Connect (OIDC) and benefit from support for your IdP''s Conditional Access Policy.' product: '{% data reusables.gated-features.emus %}' versions: feature: oidc-for-emu @@ -14,11 +14,11 @@ topics: {% data reusables.enterprise-accounts.oidc-beta-notice %} -## About migrating your {% data variables.product.prodname_emu_enterprise %} from SAML to OIDC +## About migrating your {% data variables.enterprise.prodname_emu_enterprise %} from SAML to OIDC -If your {% data variables.product.prodname_emu_enterprise %} uses SAML SSO to authenticate with Azure Active Directory (Azure AD), you can migrate to OIDC. {% data reusables.enterprise-accounts.emu-cap-validates %} +If your {% data variables.enterprise.prodname_emu_enterprise %} uses SAML SSO to authenticate with Azure Active Directory (Azure AD), you can migrate to OIDC. {% data reusables.enterprise-accounts.emu-cap-validates %} -When you migrate from SAML to OIDC, {% data variables.product.prodname_managed_users %} and groups that were previously provisioned for SAML but are not provisioned by the {% data variables.product.prodname_emu_idp_oidc_application %} application will have "(SAML)" appended to their display names. +When you migrate from SAML to OIDC, {% data variables.enterprise.prodname_managed_users %} and groups that were previously provisioned for SAML but are not provisioned by the {% data variables.product.prodname_emu_idp_oidc_application %} application will have "(SAML)" appended to their display names. If you're new to {% data variables.product.prodname_emus %} and haven't yet configured authentication for your enterprise, you do not need to migrate and can set up OIDC single sign-on immediately. For more information, see "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)." @@ -47,11 +47,11 @@ If you're new to {% data variables.product.prodname_emus %} and haven't yet conf ![Screenshot showing the "Configure with Azure" button](/assets/images/help/enterprises/saml-to-oidc-button.png) 1. Read both warnings and click to continue. {% data reusables.enterprise-accounts.emu-azure-admin-consent %} -1. In a new tab or window, while signed in as the setup user on {% data variables.product.prodname_dotcom_the_website %}, create a personal access token with the **admin:enterprise** scope and **no expiration** and copy it to your clipboard. For more information about creating a new token, see "[Creating a personal access token](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)." +1. In a new tab or window, while signed in as the setup user on {% data variables.product.prodname_dotcom_the_website %}, create a {% data variables.product.pat_v1 %} with the **admin:enterprise** scope and **no expiration** and copy it to your clipboard. For more information about creating a new token, see "[Creating a {% data variables.product.pat_generic %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)." 1. In the settings for the {% data variables.product.prodname_emu_idp_oidc_application %} application in Azure Portal, under "Tenant URL", type `https://api.github.com/scim/v2/enterprises/YOUR_ENTERPRISE`, replacing YOUR_ENTERPRISE with the name of your enterprise account. For example, if your enterprise account's URL is `https://github.com/enterprises/octo-corp`, the name of the enterprise account is `octo-corp`. -1. Under "Secret token", paste the personal access token with the **admin:enterprise** scope that you created earlier. +1. Under "Secret token", paste the {% data variables.product.pat_v1 %} with the **admin:enterprise** scope that you created earlier. 1. To test the configuration, click **Test Connection**. 1. To save your changes, at the top of the form, click **Save**. 1. In Azure Portal, copy the users and groups from the old {% data variables.product.prodname_emu_idp_application %} application to the new {% data variables.product.prodname_emu_idp_oidc_application %} application. diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md b/translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md index 95c5c9c871..67af5b8586 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md @@ -1,16 +1,10 @@ --- -title: 使用 LDAP 进行企业 IAM +title: Using LDAP for enterprise IAM shortTitle: LDAP for enterprise IAM -intro: '可以通过与现有 LDAP 目录集成,来集中管理帐户和对 {% data variables.product.product_location %} 的访问权限。' +intro: 'You can centrally manage accounts and access to {% data variables.location.product_location %} by integrating with your existing LDAP directory.' versions: ghes: '*' children: - /using-ldap -ms.openlocfilehash: 40145a8d9c4905731eef2d710171ffae7872ecea -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717803' --- diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md b/translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md index 4dc7ba18f9..1054fee109 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md @@ -1,5 +1,5 @@ --- -title: 使用 LDAP +title: Using LDAP redirect_from: - /enterprise/admin/articles/configuring-ldap-authentication - /enterprise/admin/articles/about-ldap-authentication @@ -11,7 +11,7 @@ redirect_from: - /admin/authentication/using-ldap - /enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap - /admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap -intro: '如果使用轻型目录访问协议 (LDAP) 集中访问应用程序,可以通过为实例配置 LDAP 身份验证来集成 {% data variables.product.product_name %}。' +intro: 'If you use Lightweight Directory Access Protocol (LDAP) to centralize access across applications, you can integrate {% data variables.product.product_name %} by configuring LDAP authentication for your instance.' versions: ghes: '*' type: how_to @@ -20,24 +20,19 @@ topics: - Authentication - Enterprise - Identity -ms.openlocfilehash: bed91adf09819869204f40b1a9e09c63925904ff -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147062992' --- -## 关于 {% data variables.product.product_name %} 的 LDAP 身份验证 -LDAP 是一种用于访问和维护目录信息服务的热门应用程序协议,是将第三方软件与大型公司用户目录集成时使用的最常见协议之一。 有关详细信息,请参阅 Wikipedia 上的“[轻型目录访问协议](https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol)”。 +## About LDAP authentication for {% data variables.product.product_name %} -如果使用 LDAP 目录进行集中式身份验证,则可以为使用 {% data variables.product.product_location %} 的用户配置 LDAP 身份验证。 +LDAP is a popular application protocol for access and maintenance of directory information services, and is one of the most common protocols for integration of third-party software with large company user directories. For more information, see "[Lightweight Directory Access Protocol](https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol)" on Wikipedia. + +If you use an LDAP directory for centralized authentication, you can configure LDAP authentication for the people who use {% data variables.location.product_location %}. {% data reusables.enterprise_user_management.built-in-authentication %} -## 支持的 LDAP 服务 +## Supported LDAP services -{% data variables.product.prodname_ghe_server %} 可与下列 LDAP 服务集成: +{% data variables.product.prodname_ghe_server %} integrates with these LDAP services: * Active Directory * FreeIPA @@ -46,165 +41,173 @@ LDAP 是一种用于访问和维护目录信息服务的热门应用程序协议 * Open Directory * 389-ds -## 使用 LDAP 时的用户名考量因素 +## Username considerations with LDAP -{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} 有关详细信息,请参阅“[外部身份验证的用户名注意事项](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)”。 +{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)." -## 使用 {% data variables.product.product_location %} 配置 LDAP +## Configuring LDAP with {% data variables.location.product_location %} -在您配置 LDAP 后,用户将能够使用他们的 LDAP 凭据登录您的实例。 在用户首次登录时,他们个人资料中的姓名、电子邮件地址和 SSH 密钥将使用您的目录中的 LDAP 属性进行设置。 +After you configure LDAP, users will be able to sign into your instance with their LDAP credentials. When users sign in for the first time, their profile names, email addresses, and SSH keys will be set with the LDAP attributes from your directory. -当您通过 {% data variables.enterprise.management_console %} 为用户配置 LDAP 访问权限时,在用户首次登录您的实例前,用户许可不可用。 但是,如果您使用站点管理员设置手动创建帐户,用户许可将立即可用。 +When you configure LDAP access for users via the {% data variables.enterprise.management_console %}, your user licenses aren't used until the first time a user signs in to your instance. However, if you create an account manually using site admin settings, the user license is immediately accounted for. {% warning %} -警告:在 {% data variables.product.product_location %} 上配置 LDAP 之前,请确保你的 LDAP 服务支持分页结果。 +**Warning:** Before configuring LDAP on {% data variables.location.product_location %}, make sure that your LDAP service supports paged results. {% endwarning %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.authentication %} -3. 在“身份验证”下选择“LDAP”。 -![选择 LDAP](/assets/images/enterprise/management-console/ldap-select.png) -4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![选中 LDAP 内置身份验证复选框](/assets/images/enterprise/management-console/ldap-built-in-authentication.png) -5. 添加您的配置设置。 +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.authentication %} +3. Under "Authentication", select **LDAP**. +![LDAP select](/assets/images/enterprise/management-console/ldap-select.png) +4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Select LDAP built-in authentication checkbox](/assets/images/enterprise/management-console/ldap-built-in-authentication.png) +5. Add your configuration settings. -## LDAP 属性 -使用以下属性完成 {% data variables.product.product_location %} 的 LDAP 配置。 +## LDAP attributes +Use these attributes to finish configuring LDAP for {% data variables.location.product_location %}. -| 特性名 | 类型 | 说明 | +| Attribute name | Type | Description | |--------------------------|----------|-------------| -| `Host` | 必需 | LDAP 主机,例如 `ldap.example.com` 或 `10.0.0.30`。 如果主机名只能在内部网络中使用,需要先配置 {% data variables.product.product_location %} 的 DNS,以便它可以使用内部域名服务器解析主机名。 | -| `Port` | 必需 | 主机的 LDAP 服务侦听的端口。 示例包括:389 和 636(适用于 LDAPS)。 | -| `Encryption` | 必需 | 用于确保与 LDAP 服务器之间的通信安全的加密方法。 示例包括明文(无加密)、SSL/LDAPS(从一开始就加密)和 StartTLS(在连接后升级为加密通信)。 | -| `Domain search user` | 可选 | 查找其他登录用户的 LDAP 用户,以允许身份验证。 这一般是一个专为第三方集成创建的服务帐户。 使用完全限定的名称,例如 `cn=Administrator,cn=Users,dc=Example,dc=com`。 对于 Active Directory,还可为域搜索用户使用 `[DOMAIN]\[USERNAME]` 语法(例如 `WINDOWS\Administrator`)。 | -| `Domain search password` | 可选 | 域搜索用户的密码。 | -| `Administrators group` | 可选 | 登录您的设备后,此组中的用户将被升级为站点管理员。 如果您不配置 LDAP 管理员组,则登录您的设备的第一个 LDAP 用户帐户将被自动升级为站点管理员。 | -| `Domain base` | 必需 | 想要搜索其用户和组的 LDAP 子树的完全限定 `Distinguished Name` (DN)。 您可以添加任意数量的组;不过,每个组和它所包含的用户都必须在相同的基础域中定义。 如果您指定受限的用户组,那么只有属于这些组的用户将在作用域内。 我们建议您将 LDAP 目录树的顶级指定为您的基础域,并使用受限的用户组来控制权限。 | -| `Restricted user groups` | 可选 | 如果指定,将仅允许这些组中的用户登录。 您只需要指定组的常用名 (CN),您可以添加任意数量的组。 如果未指定组,则指定基础域作用域中的所有用户都将可以登录你的 {% data variables.product.prodname_ghe_server %} 实例。 | -| `User ID` | 必需 | 标识尝试身份验证的 LDAP 用户的 LDAP 属性。 建立映射后,用户可以更改他们的 {% data variables.product.prodname_ghe_server %} 用户名。 对于大多数 Active Directory 安装来说,此字段应为 `sAMAccountName`,但对其他 LDAP 解决方案(例如 OpenLDAP)来说,可能是 `uid`。 默认值为 `uid`。 | -| `Profile name` | 可选 | 将在用户的 {% data variables.product.prodname_ghe_server %} 个人资料页面上显示的姓名。 除非启用 LDAP 同步,否则用户可以更改他们的个人资料姓名。 | -| `Emails` | 可选 | 用户的 {% data variables.product.prodname_ghe_server %} 帐户的电子邮件地址。 | -| `SSH keys` | 可选 | 连接到用户的 {% data variables.product.prodname_ghe_server %} 帐户的 SSH 公钥。 密钥必须采用 OpenSSH 格式。 | -| `GPG keys` | 可选 | 连接到用户的 {% data variables.product.prodname_ghe_server %} 帐户的 GPG 密钥。 | -| `Disable LDAP authentication for Git operations` | 可选 |如果选择,将[禁止](#disabling-password-authentication-for-git-operations)用户使用 LDAP 密码对 Git 操作进行身份验证。 | -| `Enable LDAP certificate verification` | 可选 |如果选择,[请启用](#enabling-ldap-certificate-verification) LDAP 证书验证。 | -| `Synchronization` | 可选 |如果选择,将[启用](#enabling-ldap-sync) LDAP 同步。 | +| `Host` | Required | The LDAP host, e.g. `ldap.example.com` or `10.0.0.30`. If the hostname is only available from your internal network, you may need to configure {% data variables.location.product_location %}'s DNS first so it can resolve the hostname using your internal nameservers. | +| `Port` | Required | The port the host's LDAP services are listening on. Examples include: 389 and 636 (for LDAPS). | +| `Encryption` | Required | The encryption method used to secure communications to the LDAP server. Examples include plain (no encryption), SSL/LDAPS (encrypted from the start), and StartTLS (upgrade to encrypted communication once connected). | +| `Domain search user` | Optional | The LDAP user that looks up other users that sign in, to allow authentication. This is typically a service account created specifically for third-party integrations. Use a fully qualified name, such as `cn=Administrator,cn=Users,dc=Example,dc=com`. With Active Directory, you can also use the `[DOMAIN]\[USERNAME]` syntax (e.g. `WINDOWS\Administrator`) for the domain search user with Active Directory. | +| `Domain search password` | Optional | The password for the domain search user. | +| `Administrators group` | Optional | Users in this group are promoted to site administrators when signing into your appliance. If you don't configure an LDAP Administrators group, the first LDAP user account that signs into your appliance will be automatically promoted to a site administrator. | +| `Domain base` | Required | The fully qualified `Distinguished Name` (DN) of an LDAP subtree you want to search for users and groups. You can add as many as you like; however, each group must be defined in the same domain base as the users that belong to it. If you specify restricted user groups, only users that belong to those groups will be in scope. We recommend that you specify the top level of your LDAP directory tree as your domain base and use restricted user groups to control access. | +| `Restricted user groups` | Optional | If specified, only users in these groups will be allowed to log in. You only need to specify the common names (CNs) of the groups, and you can add as many groups as you like. If no groups are specified, *all* users within the scope of the specified domain base will be able to sign in to your {% data variables.product.prodname_ghe_server %} instance. | +| `User ID` | Required | The LDAP attribute that identifies the LDAP user who attempts authentication. Once a mapping is established, users may change their {% data variables.product.prodname_ghe_server %} usernames. This field should be `sAMAccountName` for most Active Directory installations, but it may be `uid` for other LDAP solutions, such as OpenLDAP. The default value is `uid`. | +| `Profile name` | Optional | The name that will appear on the user's {% data variables.product.prodname_ghe_server %} profile page. Unless LDAP Sync is enabled, users may change their profile names. | +| `Emails` | Optional | The email addresses for a user's {% data variables.product.prodname_ghe_server %} account. | +| `SSH keys` | Optional | The public SSH keys attached to a user's {% data variables.product.prodname_ghe_server %} account. The keys must be in OpenSSH format. | +| `GPG keys` | Optional | The GPG keys attached to a user's {% data variables.product.prodname_ghe_server %} account. | +| `Disable LDAP authentication for Git operations` | Optional |If selected, [turns off](#disabling-password-authentication-for-git-operations) users' ability to use LDAP passwords to authenticate Git operations. | +| `Enable LDAP certificate verification` | Optional |If selected, [turns on](#enabling-ldap-certificate-verification) LDAP certificate verification. | +| `Synchronization` | Optional |If selected, [turns on](#enabling-ldap-sync) LDAP Sync. | -### 为 Git 操作禁用密码身份验证 +### Disabling password authentication for Git operations -在 LDAP 设置中选择“禁用 Git 操作的用户名和密码身份验证”,为 Git 权限强制使用个人访问令牌或 SSH 密钥,这样有助于防止服务器被 LDAP 身份验证请求过载。 我们建议使用此设置,因为响应慢的 LDAP 服务器是性能问题和故障的常见来源,尤其是在遇到轮询导致的大量请求时。 +Select **Disable username and password authentication for Git operations** in your LDAP settings to enforce use of {% data variables.product.pat_generic %}s or SSH keys for Git access, which can help prevent your server from being overloaded by LDAP authentication requests. We recommend this setting because a slow-responding LDAP server, especially combined with a large number of requests due to polling, is a frequent source of performance issues and outages. -![为 Git 禁用 LDAP 密码身份验证的复选框](/assets/images/enterprise/management-console/ldap-disable-password-auth-for-git.png) +![Disable LDAP password auth for Git check box](/assets/images/enterprise/management-console/ldap-disable-password-auth-for-git.png) -选择此选项时,如果用户通过命令行尝试为 Git 操作使用密码,他们将收到一条错误消息,内容为 `Password authentication is not allowed for Git operations. You must use a personal access token.` +When this option is selected, if a user tries to use a password for Git operations via the command line, they will receive an error message that says, `Password authentication is not allowed for Git operations. You must use a {% data variables.product.pat_generic %}.` -### 启用 LDAP 证书验证 +### Enabling LDAP certificate verification -在 LDAP 设置中选择“启用 LDAP 证书验证”,验证用于 TLS 的 LDAP 服务器证书。 +Select **Enable LDAP certificate verification** in your LDAP settings to validate the LDAP server certificate you use with TLS. -![LDAP 证书验证复选框](/assets/images/enterprise/management-console/ldap-enable-certificate-verification.png) +![LDAP certificate verification box](/assets/images/enterprise/management-console/ldap-enable-certificate-verification.png) -选择此选项时,将对证书进行验证,以确保: -- 如果证书至少包含一个使用者可选名称 (SAN),则其中的一个 SAN 将匹配 LDAP 主机名。 否则,常用名 (CN) 将匹配 LDAP 主机名。 -- 证书未过期。 -- 证书由受信任的证书颁发机构 (CA) 签名。 +When this option is selected, the certificate is validated to make sure: +- If the certificate contains at least one Subject Alternative Name (SAN), one of the SANs matches the LDAP hostname. Otherwise, the Common Name (CN) matches the LDAP hostname. +- The certificate is not expired. +- The certificate is signed by a trusted certificate authority (CA). -### 启用 LDAP 同步 +### Enabling LDAP Sync {% note %} -注意:使用 LDAP 同步的团队限制为最多 1499 名成员。 +**Note:** Teams using LDAP Sync are limited to a maximum 1499 members. {% endnote %} -借助 LDAP 同步,您可以将 {% data variables.product.prodname_ghe_server %} 用户和团队成员关系与建立的 LDAP 组同步。 这样,您可以在 LDAP 服务器中为用户建立基于角色的权限控制,而不用在 {% data variables.product.prodname_ghe_server %} 中手动建立。 有关详细信息,请参阅“[创建团队](/enterprise/admin/guides/user-management/creating-teams#creating-teams-with-ldap-sync-enabled)”。 +LDAP Sync lets you synchronize {% data variables.product.prodname_ghe_server %} users and team membership against your established LDAP groups. This lets you establish role-based access control for users from your LDAP server instead of manually within {% data variables.product.prodname_ghe_server %}. For more information, see "[Creating teams](/enterprise/admin/guides/user-management/creating-teams#creating-teams-with-ldap-sync-enabled)." -若要启用 LDAP 同步,请在 LDAP 设置中选择“同步电子邮件”、“同步 SSH 密钥”或“同步 GPG 密钥” 。 +To enable LDAP Sync, in your LDAP settings, select **Synchronize Emails**, **Synchronize SSH Keys**, or **Synchronize GPG Keys** . -![Synchronization 复选框](/assets/images/enterprise/management-console/ldap-synchronize.png) +![Synchronization check box](/assets/images/enterprise/management-console/ldap-synchronize.png) -启用 LDAP 同步后,某个同步作业将以指定的时间间隔运行,在每个用户帐户上执行以下操作: +After you enable LDAP sync, a synchronization job will run at the specified time interval to perform the following operations on each user account: -- 如果您已允许对您的身份提供程序覆盖范围以外的用户进行内置身份验证,并且该用户使用内置身份验证,请前进到下一个用户。 -- 如果用户没有 LDAP 映射,请尝试将用户映射到目录中的 LDAP 条目。 如果用户无法映射到 LDAP 条目,请挂起该用户并前进到下一个用户。 -- 如果存在 LDAP 映射但目录中相应的 LDAP 条目缺失,请挂起该用户并前进到下一个用户。 -- 如果相应的 LDAP 条目已被标记为禁用并且该用户尚未被挂起,请挂起该用户并前进到下一个用户。 -- 如果相应的 LDAP 条目未标记为禁用,用户已被挂起,并在管理中心启用了“重新激活挂起的用户”,请取消挂起该用户。 -- 如果在实例中配置了一个或多个受限用户组,并且相应的 LDAP 条目不在其中,请挂起该用户。 -- 如果在实例上配置了一个或多个受限用户组,相应的 LDAP 条目位于其中一个组中,并在管理中心启用了“重新激活挂起的用户”,请取消挂起该用户。 -- 如果相应的 LDAP 条目包括 `name` 属性,请更新用户的个人资料姓名。 -- 如果相应的 LDAP 条目位于管理员组中,请将该用户升级为站点管理员。 -- 如果相应的 LDAP 条目不位于管理员组中,请将该用户降级为普通帐户。 -- 如果为电子邮件定义了一个 LDAP 用户字段,请将该用户的电子邮件设置与 LDAP 条目同步。 将第一个 LDAP `mail` 条目设为主电子邮件。 -- 如果为 SSH 公钥定义了一个 LDAP 用户字段,请将该用户的 SSH 公钥与 LDAP 条目同步。 -- 如果为 GPG 密钥定义了一个 LDAP 用户字段,请将该用户的 GPG 密钥与 LDAP 条目同步。 +- If you've allowed built-in authentication for users outside your identity provider, and the user is using built-in authentication, move on to the next user. +- If no LDAP mapping exists for the user, try to map the user to an LDAP entry in the directory. If the user cannot be mapped to an LDAP entry, suspend the user and move on to the next user. +- If there is an LDAP mapping and the corresponding LDAP entry in the directory is missing, suspend the user and move on to the next user. +- If the corresponding LDAP entry has been marked as disabled and the user is not already suspended, suspend the user and move on to the next user. +- If the corresponding LDAP entry is not marked as disabled, and the user is suspended, and _Reactivate suspended users_ is enabled in the Admin Center, unsuspend the user. +- If one or more restricted user groups are configured on the instance and the corresponding LDAP entry is not in one of these groups, suspend the user. +- If one or more restricted user groups are configured on the instance, the corresponding LDAP entry is in one of these groups, and _Reactivate suspended users_ is enabled in the Admin Center, unsuspend the user. +- If the corresponding LDAP entry includes a `name` attribute, update the user's profile name. +- If the corresponding LDAP entry is in the Administrators group, promote the user to site administrator. +- If the corresponding LDAP entry is not in the Administrators group, demote the user to a normal account. +- If an LDAP User field is defined for emails, synchronize the user's email settings with the LDAP entry. Set the first LDAP `mail` entry as the primary email. +- If an LDAP User field is defined for SSH public keys, synchronize the user's public SSH keys with the LDAP entry. +- If an LDAP User field is defined for GPG keys, synchronize the user's GPG keys with the LDAP entry. {% note %} -注意:只有当使用 Active Directory、`userAccountControl` 属性存在并用 `ACCOUNTDISABLE` 标记时,才可以将 LDAP 条目标记为禁用。 Active Directory 的某些变体(例如 AD LDS 和 ADAM)不支持 `userAccountControl` 属性。 +**Note**: LDAP entries can only be marked as disabled if you use Active Directory and the `userAccountControl` attribute is present and flagged with `ACCOUNTDISABLE`. Some variations of Active Directory, such as AD LDS and ADAM, don't support the `userAccountControl` attribute. {% endnote %} -某个同步作业也将以指定的时间间隔运行,在已经映射到 LDAP 组的每个团队上执行以下操作: +A synchronization job will also run at the specified time interval to perform the following operations on each team that has been mapped to an LDAP group: -- 如果已移除团队的相应 LDAP 组,请移除团队中的所有成员。 -- 如果已从 LDAP 组中移除 LDAP 成员条目,请从团队中移除相应的用户。 如果用户不再是组织中任何团队的成员,请从组织中删除该用户。 如果用户因此失去了任何仓库的访问权限,请删除用户在这些仓库中的任何私有分叉。 -- 如果已向 LDAP 组中添加 LDAP 成员条目,请将相应的用户添加到团队中。 如果用户因此重新获得了任何仓库的访问权限,请恢复过去 90 天内因为用户失去访问权限而被删除的仓库中的任何私有分叉。 +- If a team's corresponding LDAP group has been removed, remove all members from the team. +- If LDAP member entries have been removed from the LDAP group, remove the corresponding users from the team. If the user is no longer a member of any team in the organization, remove the user from the organization. If the user loses access to any repositories as a result, delete any private forks the user has of those repositories. +- If LDAP member entries have been added to the LDAP group, add the corresponding users to the team. If the user regains access to any repositories as a result, restore any private forks of the repositories that were deleted because the user lost access in the past 90 days. {% data reusables.enterprise_user_management.ldap-sync-nested-teams %} {% warning %} -**安全警告:** +**Security Warning:** -启用 LDAP 同步后,站点管理员和组织所有者可以搜索要映射团队的目标组的 LDAP 目录。 +When LDAP Sync is enabled, site admins and organization owners can search the LDAP directory for groups to map the team to. -这样有可能将敏感的组织信息披露给合同工或其他没有权限的用户,包括: +This has the potential to disclose sensitive organizational information to contractors or other unprivileged users, including: -- 对“域搜索用户”可见的特定 LDAP 组的存在性。 -- 具有 {% data variables.product.prodname_ghe_server %} 用户帐户的 LDAP 组的成员,如果创建与该 LDAP 组同步的团队,此信息将被披露。 +- The existence of specific LDAP Groups visible to the *Domain search user*. +- Members of the LDAP group who have {% data variables.product.prodname_ghe_server %} user accounts, which is disclosed when creating a team synced with that LDAP group. -如果不需要披露此类信息,您的公司或组织应在管理员控制台中限制配置的“域搜索用户”的权限。 如果无法进行此类限制,请联系 {% data variables.contact.contact_ent_support %}。 +If disclosing such information is not desired, your company or organization should restrict the permissions of the configured *Domain search user* in the admin console. If such restriction isn't possible, contact {% data variables.contact.contact_ent_support %}. {% endwarning %} -### 支持的 LDAP 组对象类 +### Supported LDAP group object classes -{% data variables.product.prodname_ghe_server %} 支持下列 LDAP 组对象类。 可以嵌套组。 +{% data variables.product.prodname_ghe_server %} supports these LDAP group object classes. Groups can be nested. - `group` - `groupOfNames` - `groupOfUniqueNames` - `posixGroup` -## 查看和创建 LDAP 用户 +## Viewing and creating LDAP users -您可以查看具有您的实例访问权限的 LDAP 用户的完整列表和配置新用户。 +You can view the full list of LDAP users who have access to your instance and provision new users. -{% data reusables.enterprise_site_admin_settings.sign-in %} {% data reusables.enterprise_site_admin_settings.access-settings %} -3. 在左边栏中,单击“LDAP 用户”。 -![LDAP 用户选项卡](/assets/images/enterprise/site-admin-settings/ldap-users-tab.png) -4. 若要搜索用户,请输入完整或部分用户名,然后单击“搜索”。 现有用户将显示在搜索结果中。 如果用户不存在,请单击“创建”以预配新用户帐户。 -![LDAP 搜索](/assets/images/enterprise/site-admin-settings/ldap-users-search.jpg) +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +3. In the left sidebar, click **LDAP users**. +![LDAP users tab](/assets/images/enterprise/site-admin-settings/ldap-users-tab.png) +4. To search for a user, type a full or partial username and click **Search**. Existing users will be displayed in search results. If a user doesn’t exist, click **Create** to provision the new user account. +![LDAP search](/assets/images/enterprise/site-admin-settings/ldap-users-search.jpg) -## 更新 LDAP 帐户 +## Updating LDAP accounts -除非[启用 LDAP 同步](#enabling-ldap-sync),否则 LDAP 帐户的变更将不会自动与 {% data variables.product.prodname_ghe_server %} 同步。 +Unless [LDAP Sync is enabled](#enabling-ldap-sync), changes to LDAP accounts are not automatically synchronized with {% data variables.product.prodname_ghe_server %}. -* 要使用新的 LDAP 管理员组,必须在 {% data variables.product.prodname_ghe_server %} 上手动升级和降级用户,以反映 LDAP 中的变更。 -* 若要在 LDAP 管理员组中添加或移除 LDAP 帐户,请[在 {% data variables.product.prodname_ghe_server %} 上升级或降级帐户](/enterprise/admin/guides/user-management/promoting-or-demoting-a-site-administrator)。 -* 若要删除 LDAP 帐户,请[挂起 {% data variables.product.prodname_ghe_server %} 帐户](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users)。 +* To use a new LDAP admin group, users must be manually promoted and demoted on {% data variables.product.prodname_ghe_server %} to reflect changes in LDAP. +* To add or remove LDAP accounts in LDAP admin groups, [promote or demote the accounts on {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/user-management/promoting-or-demoting-a-site-administrator). +* To remove LDAP accounts, [suspend the {% data variables.product.prodname_ghe_server %} accounts](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users). -### 手动同步 LDAP 帐户 +### Manually syncing LDAP accounts -{% data reusables.enterprise_site_admin_settings.sign-in %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.search-user %} {% data reusables.enterprise_site_admin_settings.click-user %} {% data reusables.enterprise_site_admin_settings.admin-top-tab %} {% data reusables.enterprise_site_admin_settings.admin-tab %} -5. 在“LDAP”下,单击“立即同步”,使用 LDAP 服务器中的数据手动更新帐户。 -![LDAP“立即同步”按钮](/assets/images/enterprise/site-admin-settings/ldap-sync-now-button.png) +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.search-user %} +{% data reusables.enterprise_site_admin_settings.click-user %} +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +5. Under "LDAP," click **Sync now** to manually update the account with data from your LDAP server. +![LDAP sync now button](/assets/images/enterprise/site-admin-settings/ldap-sync-now-button.png) -也可以[使用 API 触发手动同步](/enterprise/user/rest/reference/enterprise-admin#ldap)。 +You can also [use the API to trigger a manual sync](/enterprise/user/rest/reference/enterprise-admin#ldap). -## 撤消对 {% data variables.product.product_location %} 的访问权限 +## Revoking access to {% data variables.location.product_location %} -如果[启用 LDAP 同步](#enabling-ldap-sync),删除用户的 LDAP 凭据将在下一次同步操作后挂起他们的帐户。 +If [LDAP Sync is enabled](#enabling-ldap-sync), removing a user's LDAP credentials will suspend their account after the next synchronization run. -如果未启用 LDAP 同步,则必须在删除 LDAP 凭据后手动挂起 {% data variables.product.prodname_ghe_server %} 帐户。 有关详细信息,请参阅“[挂起和取消挂起用户](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users)”。 +If LDAP Sync is **not** enabled, you must manually suspend the {% data variables.product.prodname_ghe_server %} account after you remove the LDAP credentials. For more information, see "[Suspending and unsuspending users](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users)". diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md index 0992bd4192..6bbe5ad199 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md @@ -1,7 +1,7 @@ --- title: About SAML for enterprise IAM shortTitle: About SAML for IAM -intro: 'You can use SAML single sign-on (SSO) {% ifversion ghae %}and System for Cross-domain Identity Management (SCIM) {% endif %}to centrally manage access {% ifversion ghec %}to organizations owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}to {% data variables.product.product_location %}{% elsif ghae %}to {% data variables.product.product_location %}{% endif %}.' +intro: 'You can use SAML single sign-on (SSO) {% ifversion ghae %}and System for Cross-domain Identity Management (SCIM) {% endif %}to centrally manage access {% ifversion ghec %}to organizations owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}to {% data variables.location.product_location %}{% elsif ghae %}to {% data variables.location.product_location %}{% endif %}.' versions: ghec: '*' ghes: '*' @@ -24,11 +24,11 @@ redirect_from: - /admin/identity-and-access-management/using-saml-for-enterprise-iam/about-identity-and-access-management-for-your-enterprise --- -## About SAML SSO for {% ifversion ghec or ghae %}your enterprise on {% endif %}{% ifversion ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} +## About SAML SSO for {% ifversion ghec or ghae %}your enterprise on {% endif %}{% ifversion ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} {% ifversion ghec %} -If your enterprise members manage their own user accounts on {% data variables.product.product_location %}, you can configure SAML authentication as an additional access restriction for your enterprise or organization. {% data reusables.saml.dotcom-saml-explanation %} +If your enterprise members manage their own user accounts on {% data variables.location.product_location %}, you can configure SAML authentication as an additional access restriction for your enterprise or organization. {% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.saml-accounts %} @@ -52,9 +52,9 @@ If you use Azure AD as your IDP, you can use team synchronization to manage team {% elsif ghes %} -SAML SSO allows people to authenticate and access {% data variables.product.product_location %} through an external system for identity management. +SAML SSO allows people to authenticate and access {% data variables.location.product_location %} through an external system for identity management. -SAML is an XML-based standard for authentication and authorization. When you configure SAML for {% data variables.product.product_location %}, the external system for authentication is called an identity provider (IdP). Your instance acts as a SAML service provider (SP). For more information about the SAML standard, see [Security Assertion Markup Language](https://en.wikipedia.org/wiki/Security_Assertion_Markup_Language) on Wikipedia. +SAML is an XML-based standard for authentication and authorization. When you configure SAML for {% data variables.location.product_location %}, the external system for authentication is called an identity provider (IdP). Your instance acts as a SAML service provider (SP). For more information about the SAML standard, see [Security Assertion Markup Language](https://en.wikipedia.org/wiki/Security_Assertion_Markup_Language) on Wikipedia. For more information about the configuration of SAML SSO on {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise)." @@ -68,11 +68,11 @@ For more information about the configuration of SAML SSO on {% data variables.pr {% data reusables.saml.ae-uses-saml-sso %} {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} -After you configure the application for {% data variables.product.product_name %} on your identity provider (IdP), you can provision access to {% data variables.product.product_location %} by assigning the application to users and groups on your IdP. For more information about SAML SSO for {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)." +After you configure the application for {% data variables.product.product_name %} on your identity provider (IdP), you can provision access to {% data variables.location.product_location %} by assigning the application to users and groups on your IdP. For more information about SAML SSO for {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)." {% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." -To learn how to configure both authentication and user provisioning for {% data variables.product.product_location %} with your specific IdP, see "[Configuring authentication and provisioning with your identity provider](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)." +To learn how to configure both authentication and user provisioning for {% data variables.location.product_location %} with your specific IdP, see "[Configuring authentication and provisioning with your identity provider](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)." {% endif %} diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md index 9a8f06d1db..8775694a20 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md @@ -1,7 +1,7 @@ --- -title: 使用 Azure AD 为企业配置身份验证和预配 +title: Configuring authentication and provisioning for your enterprise using Azure AD shortTitle: Configure with Azure AD -intro: '您可以使用 Azure Active Directory (Azure AD) 中的租户作为身份提供程序 (IDP) 来集中管理 {% data variables.product.product_location %} 的身份验证和用户预配。' +intro: 'You can use a tenant in Azure Active Directory (Azure AD) as an identity provider (IdP) to centrally manage authentication and user provisioning for {% data variables.location.product_location %}.' permissions: 'Enterprise owners can configure authentication and provisioning for an enterprise on {% data variables.product.product_name %}.' versions: ghae: '*' @@ -16,48 +16,42 @@ redirect_from: - /admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad - /admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad - /admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad -ms.openlocfilehash: 6374081e3a0d71238b0ebd84e64575da55ea8e61 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145099039' --- -## 关于使用 Azure AD 进行身份验证和用户预配 +## About authentication and user provisioning with Azure AD -Azure Active Directory (Azure AD) 是一项来自 Microsoft 的服务,它允许您集中管理用户帐户和 web 应用程序访问。 有关详细信息,请参阅 Microsoft Docs 中的[什么是 Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) +Azure Active Directory (Azure AD) is a service from Microsoft that allows you to centrally manage user accounts and access to web applications. For more information, see [What is Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) in the Microsoft Docs. -要管理身份以及对 {% data variables.product.product_name %} 的访问,您可以使用 Azure AD 租户作为 SAML IdP 进行身份验证。 您也可以配置 Azure AD 自动预配帐户并获取 SCIM 会员资格,这样您可以创建 {% data variables.product.prodname_ghe_managed %} 用户,并从您的 Azure AD 租户管理团队和组织成员资格。 +To manage identity and access for {% data variables.product.product_name %}, you can use an Azure AD tenant as a SAML IdP for authentication. You can also configure Azure AD to automatically provision accounts and access membership with SCIM, which allows you to create {% data variables.product.prodname_ghe_managed %} users and manage team and organization membership from your Azure AD tenant. -使用 Azure AD 对 {% data variables.product.prodname_ghe_managed %} 启用 SAML SSO 和 SCIM 后,您可以从 Azure AD 租户完成以下任务。 +After you enable SAML SSO and SCIM for {% data variables.product.prodname_ghe_managed %} using Azure AD, you can accomplish the following from your Azure AD tenant. -* 将 Azure AD 上的 {% data variables.product.prodname_ghe_managed %} 应用程序分配给用户帐户,以便在 {% data variables.product.product_name %} 上自动创建并授予对相应用户帐户的访问权限。 -* 为 Azure AD 上的用户帐户取消分配 {% data variables.product.prodname_ghe_managed %} 应用程序,以在 {% data variables.product.product_name %} 上停用相应的用户帐户 。 -* 为 Azure AD 上的 IdP 组分配 {% data variables.product.prodname_ghe_managed %} 应用程序,以为 IdP 组的所有成员授予对 {% data variables.product.product_name %} 上用户帐户的访问权限 。 此外,IdP 组也可以在 {% data variables.product.prodname_ghe_managed %} 上连接到团队及其父组织。 -* 从 IdP 组取消分配 {% data variables.product.prodname_ghe_managed %} 应用程序来停用仅通过 IdP 组访问的所有 IdP 用户的 {% data variables.product.product_name %} 用户帐户,并从父组织中删除这些用户。 IdP 组将与 {% data variables.product.product_name %} 上的任何团队断开连接。 +* Assign the {% data variables.product.prodname_ghe_managed %} application on Azure AD to a user account to automatically create and grant access to a corresponding user account on {% data variables.product.product_name %}. +* Unassign the {% data variables.product.prodname_ghe_managed %} application to a user account on Azure AD to deactivate the corresponding user account on {% data variables.product.product_name %}. +* Assign the {% data variables.product.prodname_ghe_managed %} application to an IdP group on Azure AD to automatically create and grant access to user accounts on {% data variables.product.product_name %} for all members of the IdP group. In addition, the IdP group is available on {% data variables.product.prodname_ghe_managed %} for connection to a team and its parent organization. +* Unassign the {% data variables.product.prodname_ghe_managed %} application from an IdP group to deactivate the {% data variables.product.product_name %} user accounts of all IdP users who had access only through that IdP group and remove the users from the parent organization. The IdP group will be disconnected from any teams on {% data variables.product.product_name %}. -有关在 {% data variables.product.product_location %} 上管理企业的标识和访问的详细信息,请参阅“[管理企业的标识和访问](/admin/authentication/managing-identity-and-access-for-your-enterprise)”。 有关将团队与 IdP 组同步的详细信息,请参阅“[将团队与标识提供者组同步](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)”。 +For more information about managing identity and access for your enterprise on {% data variables.location.product_location %}, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." For more information about synchronizing teams with IdP groups, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." -## 先决条件 +## Prerequisites -要使用 Azure AD 配置 {% data variables.product.product_name %} 的身份验证和用户预配,您必须有 Azure AD 帐户和租户。 有关详细信息,请参阅 [Azure AD 网站](https://azure.microsoft.com/free/active-directory)和 Microsoft Docs 中的[快速入门:创建 Azure Active Directory 租户](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant)。 +To configure authentication and user provisioning for {% data variables.product.product_name %} using Azure AD, you must have an Azure AD account and tenant. For more information, see the [Azure AD website](https://azure.microsoft.com/free/active-directory) and [Quickstart: Create an Azure Active Directory tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant) in the Microsoft Docs. -{% data reusables.saml.assert-the-administrator-attribute %} 有关在 Azure AD 的 SAML 声明中包含 `administrator` 属性的详细信息,请参阅 Microsoft Docs 中的[如何:为企业应用程序自定义 SAML 令牌中颁发的声明](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization)。 +{% data reusables.saml.assert-the-administrator-attribute %} For more information about including the `administrator` attribute in the SAML claim from Azure AD, see [How to: customize claims issued in the SAML token for enterprise applications](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization) in the Microsoft Docs. {% data reusables.saml.create-a-machine-user %} -## 使用 Azure AD 配置身份验证和用户预配 +## Configuring authentication and user provisioning with Azure AD {% ifversion ghae %} -1. 在 Azure AD 中,将 {% data variables.product.ae_azure_ad_app_link %} 添加到您的租户并配置单点登录。 有关详细信息,请参阅 Microsoft Docs 中的[教程:Azure Active Directory 单一登录 (SSO) 与 {% data variables.product.prodname_ghe_managed %} 的集成](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial)。 +1. In Azure AD, add {% data variables.product.ae_azure_ad_app_link %} to your tenant and configure single sign-on. For more information, see [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.prodname_ghe_managed %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs. -1. 在 {% data variables.product.prodname_ghe_managed %} 中,输入 Azure AD 租户的详细信息。 +1. In {% data variables.product.prodname_ghe_managed %}, enter the details for your Azure AD tenant. - {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} - - 如果已为使用其他 IdP 的 {% data variables.product.product_location %} 配置 SAML SSO,并且希望改为使用 Azure AD,您可以编辑配置。 有关详细信息,请参阅“[为企业配置 SAML 单一登录](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise#editing-the-saml-sso-configuration)”。 + - If you've already configured SAML SSO for {% data variables.location.product_location %} using another IdP and you want to use Azure AD instead, you can edit your configuration. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise#editing-the-saml-sso-configuration)." -1. 在 {% data variables.product.product_name %} 中启用用户预配,并在 Azure AD 中配置用户预配。 有关详细信息,请参阅“[为企业配置用户预配](/admin/authentication/configuring-user-provisioning-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)”。 +1. Enable user provisioning in {% data variables.product.product_name %} and configure user provisioning in Azure AD. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)." {% endif %} diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md index 884af661aa..e0b7437cad 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md @@ -1,7 +1,7 @@ --- -title: 使用 Okta 为企业配置身份验证和预配 +title: Configuring authentication and provisioning for your enterprise using Okta shortTitle: Configure with Okta -intro: '你可以使用 Okta 作为标识提供者 (IdP) 集中管理 {% data variables.product.prodname_ghe_managed %} 的身份验证和用户预配。' +intro: 'You can use Okta as an identity provider (IdP) to centrally manage authentication and user provisioning for {% data variables.product.prodname_ghe_managed %}.' permissions: 'Enterprise owners can configure authentication and provisioning for {% data variables.product.prodname_ghe_managed %}.' versions: ghae: '*' @@ -16,143 +16,144 @@ topics: - Identity - SSO miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 824554d1e35131e1e44f816e6fac3b40803db46d -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145098053' --- + {% data reusables.saml.okta-ae-sso-beta %} -## 关于 SAML 和 SCIM 与 Octa +## About SAML and SCIM with Okta -你可以使用 Okta 作为 {% data variables.product.prodname_ghe_managed %} 的标识提供者 IdP,这可允许 Okta 用户使用其 Okta 凭据登录到 {% data variables.product.prodname_ghe_managed %}。 +You can use Okta as an Identity Provider (IdP) for {% data variables.product.prodname_ghe_managed %}, which allows your Okta users to sign in to {% data variables.product.prodname_ghe_managed %} using their Okta credentials. -要使用 Okta 作为 {% data variables.product.prodname_ghe_managed %} 的 IdP,可以将 {% data variables.product.prodname_ghe_managed %} 应用添加到 Okta,将 Okta 配置为 {% data variables.product.prodname_ghe_managed %} 中的 IdP,以及为 Okta 用户和组预配访问权限。 +To use Okta as your IdP for {% data variables.product.prodname_ghe_managed %}, you can add the {% data variables.product.prodname_ghe_managed %} app to Okta, configure Okta as your IdP in {% data variables.product.prodname_ghe_managed %}, and provision access for your Okta users and groups. -以下预配功能可用于分配给 {% data variables.product.prodname_ghe_managed %} 应用程序的所有 Okta 用户。 +The following provisioning features are available for all Okta users that you assign to your {% data variables.product.prodname_ghe_managed %} application. -| 功能 | 说明 | +| Feature | Description | | --- | --- | -| 推送新用户 | 在 Okta 中创建新用户时,用户将添加到 {% data variables.product.prodname_ghe_managed %}。 | -| 推送用户停用 | 在 Okta 中停用用户时,它将在 {% data variables.product.prodname_ghe_managed %} 上从你的企业中暂停该用户。 | -| 推送个人资料更新 | 在 Okta 中更新用户的配置文件时,它将在 {% data variables.product.prodname_ghe_managed %} 上从你的企业中更新该用户的成员身份元数据。 | -| 重新激活用户 | 在 Okta 中重新激活用户时,它将在 {% data variables.product.prodname_ghe_managed %} 上从你的企业中取消暂停该用户。 | +| Push New Users | When you create a new user in Okta, the user is added to {% data variables.product.prodname_ghe_managed %}. | +| Push User Deactivation | When you deactivate a user in Okta, it will suspend the user from your enterprise on {% data variables.product.prodname_ghe_managed %}. | +| Push Profile Updates | When you update a user's profile in Okta, it will update the metadata for the user's membership in your enterprise on {% data variables.product.prodname_ghe_managed %}. | +| Reactivate Users | When you reactivate a user in Okta, it will unsuspend the user in your enterprise on {% data variables.product.prodname_ghe_managed %}. | -## 在 Okta 中添加 {% data variables.product.prodname_ghe_managed %} 应用程序 +## Adding the {% data variables.product.prodname_ghe_managed %} application in Okta {% data reusables.saml.okta-ae-applications-menu %} -1. 单击“浏览应用目录” +1. Click **Browse App Catalog** - ![浏览应用目录](/assets/images/help/saml/okta-ae-browse-app-catalog.png) + !["Browse App Catalog"](/assets/images/help/saml/okta-ae-browse-app-catalog.png) -1. 在搜索字段中,键入“GitHub AE”,然后单击结果中的“GitHub AE”。 +1. In the search field, type "GitHub AE", then click **GitHub AE** in the results. - ![搜索结果](/assets/images/help/saml/okta-ae-search.png) + !["Search result"](/assets/images/help/saml/okta-ae-search.png) -1. 单击“添加”。 +1. Click **Add**. - ![添加 GitHub AE 应用](/assets/images/help/saml/okta-ae-add-github-ae.png) + !["Add GitHub AE app"](/assets/images/help/saml/okta-ae-add-github-ae.png) -1. 对于“基 URL”,请在 {% data variables.product.prodname_ghe_managed %} 上键入企业的 URL。 +1. For "Base URL", type the URL of your enterprise on {% data variables.product.prodname_ghe_managed %}. - ![配置基 URL](/assets/images/help/saml/okta-ae-configure-base-url.png) + !["Configure Base URL"](/assets/images/help/saml/okta-ae-configure-base-url.png) -1. 单击“Done”(完成) 。 +1. Click **Done**. -## 为 {% data variables.product.prodname_ghe_managed %} 启用 SAML SSO +## Enabling SAML SSO for {% data variables.product.prodname_ghe_managed %} -要为 {% data variables.product.prodname_ghe_managed %} 启用单一登录 (SSO),必须将 {% data variables.product.prodname_ghe_managed %} 配置为使用 Okta 提供的登录 URL、证书颁发者 URL 和公共证书。 可以在“GitHub AE”应用中找到这些详细信息。 +To enable single sign-on (SSO) for {% data variables.product.prodname_ghe_managed %}, you must configure {% data variables.product.prodname_ghe_managed %} to use the sign-on URL, issuer URL, and public certificate provided by Okta. You can find locate these details in the "GitHub AE" app. -{% data reusables.saml.okta-ae-applications-menu %} {% data reusables.saml.okta-ae-configure-app %} -1. 单击“登录”。 +{% data reusables.saml.okta-ae-applications-menu %} +{% data reusables.saml.okta-ae-configure-app %} +1. Click **Sign On**. - ![“登录”选项卡](/assets/images/help/saml/okta-ae-sign-on-tab.png) + ![Sign On tab](/assets/images/help/saml/okta-ae-sign-on-tab.png) -1. 单击“查看设置说明”。 +1. Click **View Setup Instructions**. - ![“登录”选项卡](/assets/images/help/saml/okta-ae-view-setup-instructions.png) + ![Sign On tab](/assets/images/help/saml/okta-ae-view-setup-instructions.png) -1. 记下“登录 URL”、“证书颁发者”和“公共证书”详细信息。 -1. 使用这些详细信息在 {% data variables.product.prodname_ghe_managed %} 上为企业启用 SAML SSO。 有关详细信息,请参阅“[为企业配置 SAML 单一登录](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)”。 +1. Take note of the "Sign on URL", "Issuer", and "Public certificate" details. +1. Use the details to enable SAML SSO for your enterprise on {% data variables.product.prodname_ghe_managed %}. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)." {% note %} -**注意**:要从 {% data variables.product.prodname_ghe_managed %} 中测试 SAML 配置,必须将 Okta 用户帐户分配给 {% data variables.product.prodname_ghe_managed %} 应用。 +**Note:** To test your SAML configuration from {% data variables.product.prodname_ghe_managed %}, your Okta user account must be assigned to the {% data variables.product.prodname_ghe_managed %} app. {% endnote %} -## 启用 API 集成 +## Enabling API integration -Okta 中的 GitHub AE 应用使用 {% data variables.product.product_name %} API 与企业进行交互,以实现 SCIM 和 SSO。 此过程说明如何通过为 Okta 配置 {% data variables.product.prodname_ghe_managed %} 的个人访问令牌来启用和测试对 API 的访问。 +The "GitHub AE" app in Okta uses the {% data variables.product.product_name %} API to interact with your enterprise for SCIM and SSO. This procedure explains how to enable and test access to the API by configuring Okta with a {% data variables.product.pat_generic %} for {% data variables.product.prodname_ghe_managed %}. -1. 在 {% data variables.product.prodname_ghe_managed %} 中,生成具有 `admin:enterprise` 作用域的个人访问令牌。 有关详细信息,请参阅“[创建个人访问令牌](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)”。 -{% data reusables.saml.okta-ae-applications-menu %} {% data reusables.saml.okta-ae-configure-app %} {% data reusables.saml.okta-ae-provisioning-tab %} -1. 单击“配置 API 集成”。 +1. In {% data variables.product.prodname_ghe_managed %}, generate a {% data variables.product.pat_v1 %} with the `admin:enterprise` scope. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)". +{% data reusables.saml.okta-ae-applications-menu %} +{% data reusables.saml.okta-ae-configure-app %} +{% data reusables.saml.okta-ae-provisioning-tab %} +1. Click **Configure API Integration**. -1. 选择“启用 API 集成”。 +1. Select **Enable API integration**. - ![启用 API 集成](/assets/images/help/saml/okta-ae-enable-api-integration.png) + ![Enable API integration](/assets/images/help/saml/okta-ae-enable-api-integration.png) -1. 对于“API 令牌”,请键入前面生成的 {% data variables.product.prodname_ghe_managed %} 个人访问令牌。 +1. For "API Token", type the {% data variables.product.prodname_ghe_managed %} {% data variables.product.pat_generic %} you generated previously. -1. 单击“测试 API 凭据”。 +1. Click **Test API Credentials**. {% note %} -**注意**:如果看到 `Error authenticating: No results for users returned`,请确认已为{% data variables.product.prodname_ghe_managed %} 启用 SSO。 有关详细信息,请参阅“[为 {% data variables.product.prodname_ghe_managed %} 启用 SAML SSO](#enabling-saml-sso-for-github-ae)”。 +**Note:** If you see `Error authenticating: No results for users returned`, confirm that you have enabled SSO for {% data variables.product.prodname_ghe_managed %}. For more information see "[Enabling SAML SSO for {% data variables.product.prodname_ghe_managed %}](#enabling-saml-sso-for-github-ae)." {% endnote %} -## 配置 SCIM 预配设置 +## Configuring SCIM provisioning settings -此过程演示如何为 Okta 预配配置 SCIM 设置。 这些设置定义自动将 Okta 用户帐户预配到 {% data variables.product.prodname_ghe_managed %} 时将使用哪些功能。 +This procedure demonstrates how to configure the SCIM settings for Okta provisioning. These settings define which features will be used when automatically provisioning Okta user accounts to {% data variables.product.prodname_ghe_managed %}. -{% data reusables.saml.okta-ae-applications-menu %} {% data reusables.saml.okta-ae-configure-app %} {% data reusables.saml.okta-ae-provisioning-tab %} -1. 在“设置”下,单击“到应用”。 +{% data reusables.saml.okta-ae-applications-menu %} +{% data reusables.saml.okta-ae-configure-app %} +{% data reusables.saml.okta-ae-provisioning-tab %} +1. Under "Settings", click **To App**. - ![“到应用”设置](/assets/images/help/saml/okta-ae-to-app-settings.png) + !["To App" settings](/assets/images/help/saml/okta-ae-to-app-settings.png) -1. 在“预配到应用”右侧,单击“编辑”。 -1. 在“创建用户”右侧,选择“启用”。 -1. 在“更新用户属性”右侧,选择“启用”。 -1. 在“停用用户”右侧,选择“启用”。 -1. 单击“ **保存**”。 +1. To the right of "Provisioning to App", click **Edit**. +1. To the right of "Create Users", select **Enable**. +1. To the right of "Update User Attributes", select **Enable**. +1. To the right of "Deactivate Users", select **Enable**. +1. Click **Save**. -## 允许 Okta 用户和组访问 {% data variables.product.prodname_ghe_managed %} +## Allowing Okta users and groups to access {% data variables.product.prodname_ghe_managed %} -你可以为单个 Okta 用户或整个组预配对 {% data variables.product.product_name %} 的访问权限。 +You can provision access to {% data variables.product.product_name %} for your individual Okta users, or for entire groups. -### 为 Okta 用户预配访问权限 +### Provisioning access for Okta users -在 Okta 用户可以使用其凭据登录到 {% data variables.product.prodname_ghe_managed %} 之前,必须将这些用户分配到 Okta 中的 GitHub AE 应用。 +Before your Okta users can use their credentials to sign in to {% data variables.product.prodname_ghe_managed %}, you must assign the users to the "GitHub AE" app in Okta. -{% data reusables.saml.okta-ae-applications-menu %} {% data reusables.saml.okta-ae-configure-app %} +{% data reusables.saml.okta-ae-applications-menu %} +{% data reusables.saml.okta-ae-configure-app %} -1. 单击“分配”。 +1. Click **Assignments**. - ![Assignments(分配)选项卡](/assets/images/help/saml/okta-ae-assignments-tab.png) + ![Assignments tab](/assets/images/help/saml/okta-ae-assignments-tab.png) -1. 选择“分配”下拉菜单,然后单击“分配给人员”。 +1. Select the Assign drop-down menu and click **Assign to People**. - ![“分配给人员”按钮](/assets/images/help/saml/okta-ae-assign-to-people.png) + !["Assign to People" button](/assets/images/help/saml/okta-ae-assign-to-people.png) -1. 在所需用户帐户的右侧,单击“分配”。 +1. To the right of the required user account, click **Assign**. - ![用户列表](/assets/images/help/saml/okta-ae-assign-user.png) + ![List of users](/assets/images/help/saml/okta-ae-assign-user.png) -1. 在角色右侧,单击用户的角色,然后单击“保存并返回”。 +1. To the right of "Role", click a role for the user, then click **Save and go back**. - ![角色选择](/assets/images/help/saml/okta-ae-assign-role.png) + ![Role selection](/assets/images/help/saml/okta-ae-assign-role.png) -1. 单击“完成”。 +1. Click **Done**. -### 为 Okta 组预配访问权限 +### Provisioning access for Okta groups -可以将 Okta 组映射到 {% data variables.product.prodname_ghe_managed %} 中的团队。 然后,Okta 组的成员将自动成为映射的 {% data variables.product.prodname_ghe_managed %} 团队的成员。 有关详细信息,请参阅“[将 Okta 组映射到团队](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)”。 +You can map your Okta group to a team in {% data variables.product.prodname_ghe_managed %}. Members of the Okta group will then automatically become members of the mapped {% data variables.product.prodname_ghe_managed %} team. For more information, see "[Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." -## 延伸阅读 +## Further reading -- 在 Okta 文档中[了解 SAML](https://developer.okta.com/docs/concepts/saml/)。 -- 在 Okta 文档中[了解 SCIM](https://developer.okta.com/docs/concepts/scim/)。 +- [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) in the Okta documentation. +- [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) in the Okta documentation. diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md index e7730423f3..5f0283606c 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: 为企业配置 SAML 单点登录 +title: Configuring SAML single sign-on for your enterprise shortTitle: Configure SAML SSO -intro: '你可以通过{% ifversion ghec %}强制执行{% elsif ghes or ghae %}配置{% endif %}通过身份提供商 (IdP) 的 SAML 单一登录 (SSO),控制和保护对{% ifversion ghec %}资源(如企业组织中的存储库、问题和拉取请求){% elsif ghes %}{% data variables.product.product_location %}{% elsif ghae %}你在 {% data variables.product.prodname_ghe_managed %} 上的企业{% endif %}的访问。' +intro: 'You can control and secure access to {% ifversion ghec %}resources like repositories, issues, and pull requests within your enterprise''s organizations{% elsif ghes %}{% data variables.location.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.prodname_ghe_managed %}{% endif %} by {% ifversion ghec %}enforcing{% elsif ghes or ghae %}configuring{% endif %} SAML single sign-on (SSO) through your identity provider (IdP).' permissions: '{% ifversion ghes %}Site administrators{% elsif ghec or ghae %}Enterprise owners{% endif %} can configure SAML SSO for {% ifversion ghec or ghae %}an enterprise on {% data variables.product.product_name %}{% elsif ghes %}a {% data variables.product.product_name %} instance{% endif %}.' versions: ghec: '*' @@ -21,16 +21,11 @@ redirect_from: - /github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account - /admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise - /admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise -ms.openlocfilehash: a53a82ca88bb13b4e8fbb6ec5b2f2cd513f7b6a4 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147526828' --- + {% data reusables.enterprise-accounts.emu-saml-note %} -## 关于 SAML SSO +## About SAML SSO {% ifversion ghec %} @@ -38,11 +33,11 @@ ms.locfileid: '147526828' {% data reusables.saml.saml-accounts %} -有关详细信息,请参阅[关于使用 SAML 单一登录进行标识和访问管理](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)。 +For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." {% data reusables.saml.about-saml-enterprise-accounts %} -{% data reusables.saml.about-saml-access-enterprise-account %}有关详细信息,请参阅“[查看和管理用户对企业帐户 SAML 的访问](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)”。 +{% data reusables.saml.about-saml-access-enterprise-account %} For more information, see "[Viewing and managing a user's SAML access to your enterprise account](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)." {% data reusables.saml.saml-disabled-linked-identities-removed %} @@ -50,9 +45,9 @@ ms.locfileid: '147526828' {% elsif ghes or ghae %} -SAML SSO 允许您从 SAML IDP 集中控制和安全访问 {% data variables.product.product_location %}。 当未经身份验证的用户在浏览器中访问 {% data variables.product.product_location %} 时,{% data variables.product.product_name %} 会将用户重定向到您的 SAML IDP 进行身份验证。 在用户使用 IdP 上的帐户成功进行身份验证后,IdP 会将用户重定向回 {% data variables.product.product_location %}。 {% data variables.product.product_name %} 将验证 IdP 的响应,然后授予用户访问权限。 +SAML SSO allows you to centrally control and secure access to {% data variables.location.product_location %} from your SAML IdP. When an unauthenticated user visits {% data variables.location.product_location %} in a browser, {% data variables.product.product_name %} will redirect the user to your SAML IdP to authenticate. After the user successfully authenticates with an account on the IdP, the IdP redirects the user back to {% data variables.location.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access to the user. -当用户在 IdP 上成功进行身份验证后,用户对 {% data variables.product.product_location %} 的 SAML 会话将在浏览器中激活 24 小时。 24 小时后,用户必须再次使用您的 IdP 进行身份验证。 +After a user successfully authenticates on your IdP, the user's SAML session for {% data variables.location.product_location %} is active in the browser for 24 hours. After 24 hours, the user must authenticate again with your IdP. {% data reusables.saml.saml-ghes-account-revocation %} @@ -60,166 +55,176 @@ SAML SSO 允许您从 SAML IDP 集中控制和安全访问 {% data variables.pro {% data reusables.saml.assert-the-administrator-attribute %} -{% data reusables.scim.after-you-configure-saml %} 有关详细信息,请参阅[配置企业的用户预配](/admin/authentication/configuring-user-provisioning-for-your-enterprise)。 +{% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." {% endif %} {% endif %} -## 支持的身份提供程序 +## Supported identity providers {% data reusables.saml.saml-supported-idps %} {% ifversion ghec %} -## 使用 SAML 时的用户名考量因素 +## Username considerations with SAML -{% ifversion ghec %}如果使用 {% data variables.product.prodname_emus %},{% endif %}{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} 有关详细信息,请参阅“[外部身份验证的用户名注意事项](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)”。 +{% ifversion ghec %}If you use {% data variables.product.prodname_emus %}, {% endif %}{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)." -## 为企业帐户中的组织强制实施 SAML 单一登录 +## Enforcing SAML single-sign on for organizations in your enterprise account {% note %} -**注意:** +**Notes:** -- 为您的企业实施 SAML SSO 时,企业配置将覆盖任何现有的组织级 SAML 配置。 {% data reusables.saml.switching-from-org-to-enterprise %} 有关详细信息,请参阅“[将 SAML 配置从组织切换为企业帐户](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)”。 -- 当你为组织强制实施 SAML SSO 时,{% data variables.product.company_short %} 会删除未通过 SAML IdP 成功进行身份验证的任何组织成员。 当为企业强制实施 SAML SSO 时,{% data variables.product.company_short %} 不会删除未通过 SAML IdP 成功进行身份验证的企业成员。 下一次当某个成员访问企业资源时,该成员必须使用 SAML IdP 进行身份验证。 +- When you enforce SAML SSO for your enterprise, the enterprise configuration will override any existing organization-level SAML configurations. {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." +- When you enforce SAML SSO for an organization, {% data variables.product.company_short %} removes any members of the organization that have not authenticated successfully with your SAML IdP. When you require SAML SSO for your enterprise, {% data variables.product.company_short %} does not remove members of the enterprise that have not authenticated successfully with your SAML IdP. The next time a member accesses the enterprise's resources, the member must authenticate with your SAML IdP. {% endnote %} -有关如何使用 Okta 启用 SAML 的详细信息,请参阅“[使用 Okta 为企业帐户配置 SAML 单一登录](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)”。 +For more detailed information about how to enable SAML using Okta, see "[Configuring SAML single sign-on for your enterprise account using Okta](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)." -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} 4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. 在“SAML 单一登录”下,选择“要求 SAML 身份验证”。 - ![用于启用 SAML SSO 的复选框](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) -6. 在“登录 URL”字段中,为单一登录请求键入 IdP 的 HTTPS 终结点。 此值可在 IdP 配置中找到。 -![登录时将成员转发到的 URL 字段](/assets/images/help/saml/saml_sign_on_url_business.png) -7. (可选)在“颁发者”字段中,键入 SAML 颁发者 URL 以验证已发送消息的真实性。 -![SAML 颁发者的姓名字段](/assets/images/help/saml/saml_issuer.png) -8. 在“公共证书”下,粘贴证书以验证 SAML 响应。 -![标识提供程序的公共证书字段](/assets/images/help/saml/saml_public_certificate.png) -9. 若要验证来自 SAML 颁发者的请求完整性,请单击 {% octicon "pencil" aria-label="The edit icon" %}。 然后,在“Signature Method(签名方法)”和“Digest Method(摘要方法)”下拉菜单中,选择 SAML 签发者使用的哈希算法。 -![SAML 颁发者使用的签名方法和摘要方法哈希算法下拉列表](/assets/images/help/saml/saml_hashing_method.png) -10. 在为企业启用 SAML SSO 之前,请单击“测试 SMAL 配置”,以确保已输入的信息正确。 ![实施前测试 SAML 配置的按钮](/assets/images/help/saml/saml_test.png) -11. 单击“ **保存**”。 +5. Under "SAML single sign-on", select **Require SAML authentication**. + ![Checkbox for enabling SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) +6. In the **Sign on URL** field, type the HTTPS endpoint of your IdP for single sign-on requests. This value is available in your IdP configuration. +![Field for the URL that members will be forwarded to when signing in](/assets/images/help/saml/saml_sign_on_url_business.png) +7. Optionally, in the **Issuer** field, type your SAML issuer URL to verify the authenticity of sent messages. +![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png) +8. Under **Public Certificate**, paste a certificate to verify SAML responses. +![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png) +9. To verify the integrity of the requests from your SAML issuer, click {% octicon "pencil" aria-label="The edit icon" %}. Then in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. +![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png) +10. Before enabling SAML SSO for your enterprise, click **Test SAML configuration** to ensure that the information you've entered is correct. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png) +11. Click **Save**. {% data reusables.enterprise-accounts.download-recovery-codes %} {% elsif ghes %} -## 配置 SAML SSO +## Configuring SAML SSO -可以为 {% data variables.product.product_location %} 启用或禁用 SAML 身份验证,也可以编辑现有配置。 可以在管理控制台中查看和编辑 {% data variables.product.product_name %} 的身份验证设置。 有关详细信息,请参阅“[访问管理控制台](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)”。 +You can enable or disable SAML authentication for {% data variables.location.product_location %}, or you can edit an existing configuration. You can view and edit authentication settings for {% data variables.product.product_name %} in the management console. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)." {% note %} -注意:{% data reusables.enterprise.test-in-staging %} +**Note**: {% data reusables.enterprise.test-in-staging %} {% endnote %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.authentication %} -1. 选择“SAML”。 +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.authentication %} +1. Select **SAML**. - ![在管理控制台中启用 SAML 身份验证的选项的屏幕截图](/assets/images/enterprise/management-console/auth-select-saml.png) + ![Screenshot of option to enable SAML authentication in management console](/assets/images/enterprise/management-console/auth-select-saml.png) 1. {% data reusables.enterprise_user_management.built-in-authentication-option %} - ![在 SAML IdP 外部启用内置身份验证的选项的屏幕截图](/assets/images/enterprise/management-console/saml-built-in-authentication.png) -1. (可选)若要启用未经请求的响应 SSO,请选择“IdP 发起的 SSO”。 默认情况下,{% data variables.product.prodname_ghe_server %} 将对未经请求的标识提供者 (IdP) 发起的请求进行回复,并向 IdP 返回一个 `AuthnRequest`。 + ![Screenshot of option to enable built-in authentication outside of SAML IdP](/assets/images/enterprise/management-console/saml-built-in-authentication.png) +1. Optionally, to enable unsolicited response SSO, select **IdP initiated SSO**. By default, {% data variables.product.prodname_ghe_server %} will reply to an unsolicited Identity Provider (IdP) initiated request with an `AuthnRequest` back to the IdP. - ![启用 IdP 发起的未经请求响应的选项的屏幕截图](/assets/images/enterprise/management-console/saml-idp-sso.png) + ![Screenshot of option to enable IdP-initiated unsolicited response](/assets/images/enterprise/management-console/saml-idp-sso.png) {% tip %} - 注意:建议将此值保持未选中状态。 应仅在罕见情况下才启用此功能,即 SAML 实现不支持服务提供程序发起的 SSO,并且 {% data variables.contact.enterprise_support %} 建议执行此操作。 + **Note**: We recommend keeping this value **unselected**. You should enable this feature **only** in the rare instance that your SAML implementation does not support service provider initiated SSO, and when advised by {% data variables.contact.enterprise_support %}. {% endtip %} -1. 如果你不希望 SAML 提供程序为 {% data variables.product.product_location %} 上的用户确定管理员权限,请选择“禁用管理员降级/升级” 。 +1. Select **Disable administrator demotion/promotion** if you **do not** want your SAML provider to determine administrator rights for users on {% data variables.location.product_location %}. - ![用于启用选项以遵从 IdP 的“管理员”属性,从而启用或禁用管理权限的选项的屏幕截图](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png) {%- ifversion ghes > 3.3 %} -1. (可选)若要允许 {% data variables.product.product_location %} 从 SAML IdP 接收加密断言,请选择“需要加密断言”。 必须确保 IdP 支持加密断言,并且管理控制台中的加密和密钥传输方法与 IdP 上配置的值相匹配。 还必须向 IdP 提供 {% data variables.product.product_location %} 的公共证书。 有关详细信息,请参阅“[启用加密断言](/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions)”。 + ![Screenshot of option to enable option to respect the "administrator" attribute from the IdP to enable or disable administrative rights](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png) +{%- ifversion ghes > 3.3 %} +1. Optionally, to allow {% data variables.location.product_location %} to receive encrypted assertions from your SAML IdP, select **Require encrypted assertions**. You must ensure that your IdP supports encrypted assertions and that the encryption and key transport methods in the management console match the values configured on your IdP. You must also provide {% data variables.location.product_location %}'s public certificate to your IdP. For more information, see "[Enabling encrypted assertions](/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions)." - ![管理控制台“身份验证”部分中“启用加密断言”复选框的屏幕截图](/assets/images/help/saml/management-console-enable-encrypted-assertions.png) {%- endif %} -1. 在“单一登录 URL”字段中,输入 IdP 上用于单一登录请求的 HTTP 或 HTTPS 终结点。 此值由您的 IdP 配置提供。 如果主机只能在内部网络中使用,则可能需要[配置 {% data variables.product.product_location %} 以使用内部名称服务器](/enterprise/admin/guides/installation/configuring-dns-nameservers/)。 + ![Screenshot of "Enable encrypted assertions" checkbox within management console's "Authentication" section](/assets/images/help/saml/management-console-enable-encrypted-assertions.png) +{%- endif %} +1. In the **Single sign-on URL** field, type the HTTP or HTTPS endpoint on your IdP for single sign-on requests. This value is provided by your IdP configuration. If the host is only available from your internal network, you may need to [configure {% data variables.location.product_location %} to use internal nameservers](/enterprise/admin/guides/installation/configuring-dns-nameservers/). - ![单一登录 URL 的文本字段的屏幕截图](/assets/images/enterprise/management-console/saml-single-sign-url.png) -1. (可选)在“颁发者”字段中,键入 SAML 颁发者的名称。 这将验证发送到 {% data variables.product.product_location %} 的消息的真实性。 + ![Screenshot of text field for single sign-on URL](/assets/images/enterprise/management-console/saml-single-sign-url.png) +1. Optionally, in the **Issuer** field, type your SAML issuer's name. This verifies the authenticity of messages sent to {% data variables.location.product_location %}. - ![SAML 颁发者 URL 的文本字段的屏幕截图](/assets/images/enterprise/management-console/saml-issuer.png) -1. 在“签名方法”和“摘要方法”下拉菜单中,选择 SAML 颁发者用来验证来自 {% data variables.product.product_location %} 的请求完整性的哈希算法 。 使用“名称标识符格式”下拉菜单指定格式。 + ![Screenshot of text field for SAML issuer URL](/assets/images/enterprise/management-console/saml-issuer.png) +1. In the **Signature Method** and **Digest Method** drop-down menus, choose the hashing algorithm used by your SAML issuer to verify the integrity of the requests from {% data variables.location.product_location %}. Specify the format with the **Name Identifier Format** drop-down menu. - ![用于选择签名和摘要方法的下拉菜单的屏幕截图](/assets/images/enterprise/management-console/saml-method.png) -1. 在“验证证书”下,单击“选择文件”并选择一个证书以验证来自 IdP 的 SAML 响应 。 + ![Screenshot of drop-down menus to select signature and digest method](/assets/images/enterprise/management-console/saml-method.png) +1. Under **Verification certificate**, click **Choose File** and choose a certificate to validate SAML responses from the IdP. - ![用于从 IdP 上传验证证书的按钮的屏幕截图](/assets/images/enterprise/management-console/saml-verification-cert.png) -1. 如果需要,请修改 SAML 属性名称以匹配您的 IdP,或者接受默认名称。 + ![Screenshot of button for uploading validation certificate from IdP](/assets/images/enterprise/management-console/saml-verification-cert.png) +1. Modify the SAML attribute names to match your IdP if needed, or accept the default names. - ![用于输入其他 SAML 属性的字段的屏幕截图](/assets/images/enterprise/management-console/saml-attributes.png) + ![Screenshot of fields for entering additional SAML attributes](/assets/images/enterprise/management-console/saml-attributes.png) {% elsif ghae %} -## 启用 SAML SSO +## Enabling SAML SSO {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} -以下 IdP 提供有关为 {% data variables.product.product_name %} 配置 SAML SSO 的文档。 如果您的 IdP 未列出,请与您的 IdP 联系,以请求 {% data variables.product.product_name %}。 +The following IdPs provide documentation about configuring SAML SSO for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}. - | IdP | 详细信息 | + | IdP | More information | | :- | :- | - | Azure AD | “[使用 Azure AD 为企业配置身份验证和预置](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)” | -| Okta | “[使用 Okta 为企业配置身份验证和预配](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)” | + | Azure AD | "[Configuring authentication and provisioning for your enterprise using Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)" | +| Okta | "[Configuring authentication and provisioning for your enterprise using Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)" | -在 {% data variables.product.product_name %} 的初始化期间,必须在 IdP 上将 {% data variables.product.product_name %} 配置为 SAML 服务提供程序 (SP)。 您必须在 IdP 上输入多个唯一值以将 {% data variables.product.product_name %} 配置为有效的 SP。 有关详细信息,请参阅“[SAML 配置参考](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-metadata)”。 +During initialization for {% data variables.product.product_name %}, you must configure {% data variables.product.product_name %} as a SAML service provider (SP) on your IdP. You must enter several unique values on your IdP to configure {% data variables.product.product_name %} as a valid SP. For more information, see "[SAML configuration reference](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-metadata)." -## 编辑 SAML SSO 配置 +## Editing the SAML SSO configuration -如果 IdP 的详细信息发生更改,则需要编辑 {% data variables.product.product_location %} 的 SAML SSO 配置。 例如,如果 IdP 的证书过期,您可以编辑公共证书的值。 +If the details for your IdP change, you'll need to edit the SAML SSO configuration for {% data variables.location.product_location %}. For example, if the certificate for your IdP expires, you can edit the value for the public certificate. {% ifversion ghae %} {% note %} -注意:{% data reusables.saml.contact-support-if-your-idp-is-unavailable %} +**Note**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} {% endnote %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} -1. 在“SAML single sign-on(SAML 单点登录)”下,键入 IdP 的新详细信息。 - ![具有 IdP 详细信息的文本输入字段,用于企业 SAML SSO 配置](/assets/images/help/saml/ae-edit-idp-details.png) -1. (可选)单击 {% octicon "pencil" aria-label="The edit icon" %} 以配置新的签名或摘要方法。 - ![用于更改签名和摘要方法的编辑图标](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest.png) +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +1. Under "SAML single sign-on", type the new details for your IdP. + ![Text entry fields with IdP details for SAML SSO configuration for an enterprise](/assets/images/help/saml/ae-edit-idp-details.png) +1. Optionally, click {% octicon "pencil" aria-label="The edit icon" %} to configure a new signature or digest method. + ![Edit icon for changing signature and digest method](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest.png) - - 使用下拉菜单并选择新的签名或摘要方法。 - ![用于选择新签名或摘要方法的下拉菜单](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png) -1. 要确保输入的信息是正确的,请单击“测试 SAML 配置”。 - ![“测试 SAML 配置”按钮](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png) -1. 单击“ **保存**”。 - ![SAML SSO 配置的“保存”按钮](/assets/images/help/saml/ae-edit-idp-details-save.png) -1. (可选)要自动预配和取消预配 {% data variables.product.product_location %} 的用户帐户,请使用 SCIM 重新配置用户预配。 有关详细信息,请参阅“[为企业配置用户预配](/admin/authentication/configuring-user-provisioning-for-your-enterprise)”。 + - Use the drop-down menus and choose the new signature or digest method. + ![Drop-down menus for choosing a new signature or digest method](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png) +1. To ensure that the information you've entered is correct, click **Test SAML configuration**. + !["Test SAML configuration" button](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png) +1. Click **Save**. + !["Save" button for SAML SSO configuration](/assets/images/help/saml/ae-edit-idp-details-save.png) +1. Optionally, to automatically provision and deprovision user accounts for {% data variables.location.product_location %}, reconfigure user provisioning with SCIM. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." {% endif %} {% ifversion ghae %} -## 禁用 SAML SSO +## Disabling SAML SSO {% warning %} -警告:如果禁用 {% data variables.product.product_location %} 的 SAML SSO,没有现有 SAML SSO 会话的用户不能登录 {% data variables.product.product_location %}。 {% data variables.product.product_location %} 上的 SAML SSO 会话在 24 小时后结束。 +**Warning**: If you disable SAML SSO for {% data variables.location.product_location %}, users without existing SAML SSO sessions cannot sign into {% data variables.location.product_location %}. SAML SSO sessions on {% data variables.location.product_location %} end after 24 hours. {% endwarning %} {% note %} -注意:{% data reusables.saml.contact-support-if-your-idp-is-unavailable %} +**Note**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %} {% endnote %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} -1. 在“SAML 单一登录”下,取消选择“启用 SAML 身份验证”。 - ![“启用 SAML 身份验证”的复选框](/assets/images/help/saml/ae-saml-disabled.png) -1. 若要禁用 SAML SSO 并要求使用在初始化期间创建的内置用户帐户进行登录,请单击“保存”。 - ![SAML SSO 配置的“保存”按钮](/assets/images/help/saml/ae-saml-disabled-save.png) +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +1. Under "SAML single sign-on", unselect **Enable SAML authentication**. + ![Checkbox for "Enable SAML authentication"](/assets/images/help/saml/ae-saml-disabled.png) +1. To disable SAML SSO and require signing in with the built-in user account you created during initialization, click **Save**. + !["Save" button for SAML SSO configuration](/assets/images/help/saml/ae-saml-disabled-save.png) {% endif %} @@ -227,10 +232,13 @@ SAML SSO 允许您从 SAML IDP 集中控制和安全访问 {% data variables.pro {% ifversion ghec or ghes %} -## 延伸阅读 +## Further reading {%- ifversion ghec %} -- “[管理组织的 SAML 单一登录](/organizations/managing-saml-single-sign-on-for-your-organization)”{%- endif %} {%- ifversion ghes %} -- “[升级或降级站点管理员](/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator)”{%- endif %} +- "[Managing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization)" +{%- endif %} +{%- ifversion ghes %} +- "[Promoting or demoting a site administrator](/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator)" +{%- endif %} {% endif %} diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-for-your-enterprise.md b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-for-your-enterprise.md index 6cb2623215..0118676666 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: 为企业配置用户预配 +title: Configuring user provisioning for your enterprise shortTitle: Configure user provisioning -intro: '您可以为企业配置跨域身份管理 (SCIM),以在将 {% data variables.product.product_location %} 的应用程序分配给身份提供商 (IdP) 上的用户时,就自动在 {% data variables.product.product_location %} 上预配用户帐户。' +intro: 'You can configure System for Cross-domain Identity Management (SCIM) for your enterprise, which automatically provisions user accounts on {% data variables.location.product_location %} when you assign the application for {% data variables.location.product_location %} to a user on your identity provider (IdP).' permissions: 'Enterprise owners can configure user provisioning for an enterprise on {% data variables.product.product_name %}.' versions: ghae: '*' @@ -15,73 +15,71 @@ topics: redirect_from: - /admin/authentication/configuring-user-provisioning-for-your-enterprise - /admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-user-provisioning-for-your-enterprise -ms.openlocfilehash: c76cf3a3245b272fc61db68470e7a34796a89e42 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145098052' --- -## 关于企业的用户预配 +## About user provisioning for your enterprise -{% data reusables.saml.ae-uses-saml-sso %} 有关详细信息,请参阅“[为企业配置 SAML 单一登录](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)”。 +{% data reusables.saml.ae-uses-saml-sso %} For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)." -在 IdP 上分配或取消分配应用程序时,可以使用 SCIM 配置用户预配以自动创建或暂停用户帐户并授予 {% data variables.product.product_name %} 访问权限。 有关 SCIM 的详细信息,请参阅 IETF 网站上的[跨域身份管理系统:协议 (RFC 7644)](https://tools.ietf.org/html/rfc7644)。 +You can configure user provisioning with SCIM to automatically create or suspend user accounts and grant access for {% data variables.product.product_name %} when you assign or unassign the application on your IdP. For more information about SCIM, see [System for Cross-domain Identity Management: Protocol (RFC 7644)](https://tools.ietf.org/html/rfc7644) on the IETF website. -如果不使用 SCIM 配置用户预配,则向用户分配或取消分配应用程序时,IdP 将不会自动与 {% data variables.product.product_name %} 通信。 如果没有 SCIM,{% data variables.product.product_name %} 会在有人第一次导航到 {% data variables.product.product_name %} 并通过 IdP 进行身份验证来登录时使用 SAML 实时 (JIT) 预配创建用户帐户。 +If you do not configure user provisioning with SCIM, your IdP will not communicate with {% data variables.product.product_name %} automatically when you assign or unassign the application to a user. Without SCIM, {% data variables.product.product_name %} creates a user account using SAML Just-in-Time (JIT) provisioning the first time someone navigates to {% data variables.product.product_name %} and signs in by authenticating through your IdP. -配置预配允许 IdP 在您将 {% data variables.product.product_name %} 的应用程序分配或取消分配给 IdP 上的用户时与 {% data variables.product.product_location %} 通信。 当您分配应用程序时,IdP 将提示 {% data variables.product.product_location %} 创建帐户并向用户发送一封登录电子邮件。 取消分配应用程序时,IdP 将与 {% data variables.product.product_name %} 通信以取消任何 SAML 会话并禁用成员的帐户。 +Configuring provisioning allows your IdP to communicate with {% data variables.location.product_location %} when you assign or unassign the application for {% data variables.product.product_name %} to a user on your IdP. When you assign the application, your IdP will prompt {% data variables.location.product_location %} to create an account and send an onboarding email to the user. When you unassign the application, your IdP will communicate with {% data variables.product.product_name %} to invalidate any SAML sessions and disable the member's account. -要为企业配置预配,必须在 {% data variables.product.product_name %} 上启用预配,然后在 IdP 上安装和配置预配应用程序。 +To configure provisioning for your enterprise, you must enable provisioning on {% data variables.product.product_name %}, then install and configure a provisioning application on your IdP. -IdP 上的预配应用程序通过企业的 SCIM API 与 {% data variables.product.product_name %} 通信。 有关详细信息,请参阅 {% data variables.product.prodname_dotcom %} REST API 文档中的“[GitHub Enterprise 管理](/rest/reference/enterprise-admin#scim)”。 +The provisioning application on your IdP communicates with {% data variables.product.product_name %} via our SCIM API for enterprises. For more information, see "[GitHub Enterprise administration](/rest/reference/enterprise-admin#scim)" in the {% data variables.product.prodname_dotcom %} REST API documentation. -## 支持的身份提供程序 +## Supported identity providers -支持以下 IdP 用于通过 {% data variables.product.prodname_ghe_managed %} 的 SSO: +The following IdPs are supported for SSO with {% data variables.product.prodname_ghe_managed %}: {% data reusables.saml.okta-ae-sso-beta %} {% data reusables.github-ae.saml-idp-table %} -对于支持团队映射的 IdP,您可以将 {% data variables.product.product_name %} 应用程序分配给或取消分配给 IdP 中的用户组。 然后,这些组可供 {% data variables.product.product_location %} 中的组织所有者和团队维护员用来映射到 {% data variables.product.product_name %} 团队。 有关详细信息,请参阅“[将 Okta 组映射到团队](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)”。 +For IdPs that support team mapping, you can assign or unassign the application for {% data variables.product.product_name %} to groups of users in your IdP. These groups are then available to organization owners and team maintainers in {% data variables.location.product_location %} to map to {% data variables.product.product_name %} teams. For more information, see "[Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." -## 先决条件 +## Prerequisites -要自动预配和解除预配从 IdP 访问 {% data variables.product.product_location %},必须先在初始化 {% data variables.product.product_name %} 时配置 SAML SSO。 有关详细信息,请参阅“[初始化 {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)”。 +To automatically provision and deprovision access to {% data variables.location.product_location %} from your IdP, you must first configure SAML SSO when you initialize {% data variables.product.product_name %}. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)." -您必须对 IdP 具有管理访问权限,才能配置应用程序进行 {% data variables.product.product_name %} 的用户预配。 +You must have administrative access on your IdP to configure the application for user provisioning for {% data variables.product.product_name %}. -## 为企业启用用户预配 +## Enabling user provisioning for your enterprise -1. 当以企业所有者身份登录到 {% data variables.product.product_location %} 时,需创建一个具有 admin:enterprise 作用域的个人访问令牌。 有关详细信息,请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 +1. While signed into {% data variables.location.product_location %} as an enterprise owner, create a {% data variables.product.pat_v1 %} with **admin:enterprise** scope. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." {% note %} - **注释**: - - 要创建个人访问令牌,我们建议使用初始化期间创建的第一个企业所有者的帐户。 有关详细信息,请参阅“[初始化 {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)”。 - - 您需要此个人访问令牌在 IdP 上为 SCIM 配置应用程序。 将令牌安全地存储在密码管理器中,直到您稍后在这些说明中再次需要该令牌。 + **Notes**: + - To create the {% data variables.product.pat_generic %}, we recommend using the account for the first enterprise owner that you created during initialization. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)." + - You'll need this {% data variables.product.pat_generic %} to configure the application for SCIM on your IdP. Store the token securely in a password manager until you need the token again later in these instructions. - {% endnote %} {% warning %} + {% endnote %} + {% warning %} - 警告:如果创建个人访问令牌的企业所有者的用户帐户被停用或取消预配,IdP 将不再自动为企业预配和取消预配用户帐户。 另一个企业所有者必须创建新的个人访问令牌,并在 IdP 上重新配置预配。 + **Warning**: If the user account for the enterprise owner who creates the {% data variables.product.pat_generic %} is deactivated or deprovisioned, your IdP will no longer provision and deprovision user accounts for your enterprise automatically. Another enterprise owner must create a new {% data variables.product.pat_generic %} and reconfigure provisioning on the IdP. - {% endwarning %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} -1. 在“SCIM 用户预配”下,选择“需要 SCIM 用户预配”。 - ![企业安全设置中的“需要 SCIM 用户预配”复选框](/assets/images/help/enterprises/settings-require-scim-user-provisioning.png) -1. 单击“ **保存**”。 - ![企业安全设置中“需要 SCIM 用户预配”下的“保存”按钮](/assets/images/help/enterprises/settings-scim-save.png) -1. 在 IdP 上 {% data variables.product.product_name %} 的应用程序中配置用户预配。 + {% endwarning %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} +1. Under "SCIM User Provisioning", select **Require SCIM user provisioning**. + ![Checkbox for "Require SCIM user provisioning" within enterprise security settings](/assets/images/help/enterprises/settings-require-scim-user-provisioning.png) +1. Click **Save**. + ![Save button under "Require SCIM user provisioning" within enterprise security settings](/assets/images/help/enterprises/settings-scim-save.png) +1. Configure user provisioning in the application for {% data variables.product.product_name %} on your IdP. - 以下 IdP 提供有关为 {% data variables.product.product_name %} 配置预配的文档。 如果您的 IdP 未列出,请与您的 IdP 联系,以请求 {% data variables.product.product_name %}。 + The following IdPs provide documentation about configuring provisioning for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}. - | IdP | 详细信息 | + | IdP | More information | | :- | :- | - | Azure AD | [教程:在 Microsoft Docs 中配置 {% data variables.product.prodname_ghe_managed %} 以实现自动用户预配](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial)。若要为 {% data variables.product.prodname_ghe_managed %} 配置 Azure AD,请参阅“[使用 Azure AD 为企业配置身份验证和进行预配](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)”。| -| Okta | (beta 版本)若要为 {% data variables.product.prodname_ghe_managed %} 配置 Okta,请参阅“[使用 Okta 为企业配置身份验证和进行预配](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)”。| + | Azure AD | [Tutorial: Configure {% data variables.product.prodname_ghe_managed %} for automatic user provisioning](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial) in the Microsoft Docs. To configure Azure AD for {% data variables.product.prodname_ghe_managed %}, see "[Configuring authentication and provisioning for your enterprise using Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)."| +| Okta | (beta) To configure Okta for {% data variables.product.prodname_ghe_managed %}, see "[Configuring authentication and provisioning for your enterprise using Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)."| - IdP 上的应用程序需要两个值来预配或取消预配 {% data variables.product.product_location %} 上的用户帐户。 + The application on your IdP requires two values to provision or deprovision user accounts on {% data variables.location.product_location %}. - | 值 | 其他名称 | 说明 | 示例 | + | Value | Other names | Description | Example | | :- | :- | :- | :- | - | URL | 租户 URL | {% data variables.product.prodname_ghe_managed %} 上企业的 SCIM 预配 API 的 URL | {% data variables.product.api_url_pre %}/scim/v2 | - | 共享密钥 | 个人访问令牌、机密令牌 | IdP 上的应用程序用于代表企业所有者执行预配任务的令牌 | 您在步骤 1 中创建的个人访问令牌 | + | URL | Tenant URL | URL to the SCIM provisioning API for your enterprise on {% data variables.product.prodname_ghe_managed %} | {% data variables.product.api_url_pre %}/scim/v2 | + | Shared secret | {% data variables.product.pat_generic_caps %}, secret token | Token for application on your IdP to perform provisioning tasks on behalf of an enterprise owner | {% data variables.product.pat_generic_caps %} you created in step 1 | diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md index a85e477495..83a3c87b14 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md @@ -1,7 +1,7 @@ --- -title: 启用加密断言 +title: Enabling encrypted assertions shortTitle: Enable encrypted assertions -intro: '通过加密 SAML 标识提供者 (IdP) 发送的消息,可以使用 SAML 单一登录 (SSO) 提高 {% data variables.product.product_location %} 的安全性。' +intro: 'You can improve {% data variables.location.product_location %}''s security with SAML single sign-on (SSO) by encrypting the messages that your SAML identity provider (IdP) sends.' permissions: 'Site administrators can configure encrypted assertions for a {% data variables.product.product_name %} instance.' versions: ghes: '> 3.3' @@ -13,51 +13,48 @@ topics: - Identity - Security - SSO -ms.openlocfilehash: ecb60a4398993155fa7498f26e7628660e88e54a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147063776' --- -## 关于加密断言 -如果 IdP 支持断言加密,则可以在 {% data variables.product.product_name %} 上配置加密断言,以提高身份验证过程中的安全性。 +## About encrypted assertions -## 先决条件 +If your IdP support encryption of assertions, you can configure encrypted assertions on {% data variables.product.product_name %} for increased security during the authentication process. -若要启用加密断言以对 {% data variables.product.product_name %} 进行身份验证,则必须配置 SAML 身份验证,并且 IdP 必须支持加密断言。 +## Prerequisites -## 启用加密断言 +To enable encrypted assertions for authentication to {% data variables.product.product_name %}, you must configure SAML authentication, and your IdP must support encrypted assertions. -要启用加密断言,必须向 IdP 提供 {% data variables.product.product_location %} 的公共证书,并配置与 IdP 匹配的加密设置。 +## Enabling encrypted assertions + +To enable encrypted assertions, you must provide {% data variables.location.product_location %}'s public certificate to your IdP, and configure encryption settings that match your IdP. {% note %} -注意:{% data reusables.enterprise.test-in-staging %} +**Note**: {% data reusables.enterprise.test-in-staging %} {% endnote %} -1. (可选)启用 SAML 调试。 SAML 调试在 {% data variables.product.product_name %} 的身份验证日志中记录详细条目,并且可以帮助你排查身份验证尝试失败的问题。 有关详细信息,请参阅“[对 SAML 身份验证进行故障排除](/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication#configuring-saml-debugging)”。 -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.authentication %} -1. 选择“需要加密断言”。 +1. Optionally, enable SAML debugging. SAML debugging records verbose entries in {% data variables.product.product_name %}'s authentication log, and may help you troubleshoot failed authentication attempts. For more information, see "[Troubleshooting SAML authentication](/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication#configuring-saml-debugging)." +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.authentication %} +1. Select **Require encrypted assertions**. - ![管理控制台“身份验证”部分中“启用加密断言”复选框的屏幕截图](/assets/images/help/saml/management-console-enable-encrypted-assertions.png) -1. 在“加密证书”右侧,单击“下载”,将 {% data variables.product.product_location %} 的公共证书副本保存在本地计算机上。 + ![Screenshot of "Enable encrypted assertions" checkbox within management console's "Authentication" section](/assets/images/help/saml/management-console-enable-encrypted-assertions.png) +1. To the right of "Encryption Certificate", click **Download** to save a copy of {% data variables.location.product_location %}'s public certificate on your local machine. - ![用于加密断言的公共证书的“下载”按钮的屏幕截图](/assets/images/help/saml/management-console-encrypted-assertions-download-certificate.png) -1. 以管理员身份登录到 SAML IdP。 -1. 在 {% data variables.product.product_location %} 的应用程序中,启用加密断言。 - - 请注意加密方法和密钥传输方法。 - - 提供你在步骤 7 中下载的公共证书。 -1. 返回到 {% data variables.product.product_location %} 上的管理控制台。 -1. 在“加密方法”的右侧,选择步骤 9 中的 IdP 加密方法。 + ![Screenshot of "Download" button for public certificate for encrypted assertions](/assets/images/help/saml/management-console-encrypted-assertions-download-certificate.png) +1. Sign into your SAML IdP as an administrator. +1. In the application for {% data variables.location.product_location %}, enable encrypted assertions. + - Note the encryption method and key transport method. + - Provide the public certificate you downloaded in step 7. +1. Return to the management console on {% data variables.location.product_location %}. +1. To the right of "Encryption Method", select the encryption method for your IdP from step 9. - ![加密断言的“加密方法”屏幕截图](/assets/images/help/saml/management-console-encrypted-assertions-encryption-method.png) -1. 在“密钥传输方法”的右侧,选择步骤 9 中的 IdP 密钥传输方法。 + ![Screenshot of "Encryption Method" for encrypted assertions](/assets/images/help/saml/management-console-encrypted-assertions-encryption-method.png) +1. To the right of "Key Transport Method", select the key transport method for your IdP from step 9. - ![加密断言的“密钥传输方法”屏幕截图](/assets/images/help/saml/management-console-encrypted-assertions-key-transport-method.png) -1. 单击“保存设置”。 + ![Screenshot of "Key Transport Method" for encrypted assertions](/assets/images/help/saml/management-console-encrypted-assertions-key-transport-method.png) +1. Click **Save settings**. {% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %} -如果启用了 SAML 调试以使用加密断言测试身份验证,请在完成测试后禁用 SAML 调试。 有关详细信息,请参阅“[对 SAML 身份验证进行故障排除](/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication#configuring-saml-debugging)”。 +If you enabled SAML debugging to test authentication with encrypted assertions, disable SAML debugging when you're done testing. For more information, see "[Troubleshooting SAML authentication](/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication#configuring-saml-debugging)." diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/index.md b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/index.md index 786655dd2a..9dfcee6f4c 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/index.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/index.md @@ -1,7 +1,7 @@ --- -title: 将 SAML 用于企业 IAM +title: Using SAML for enterprise IAM shortTitle: SAML for enterprise IAM -intro: '可以通过 SAML 单一登录 (SSO){% ifversion ghec or ghae %} 和跨域身份管理系统 (SCIM){% endif %} 集中管理{% ifversion ghes or ghae %}帐户和{% endif %}访问{% ifversion ghes %}{% data variables.product.product_location %}{% elsif ghae %}你的企业{% elsif ghec %}你的企业资源{% endif %}。' +intro: 'You can centrally manage {% ifversion ghes or ghae %}accounts and {% endif %}access to {% ifversion ghes %}{% data variables.location.product_location %}{% elsif ghae %}your enterprise{% elsif ghec %}your enterprise''s resources{% endif %} with SAML single sign-on (SSO){% ifversion ghec or ghae %} and System for Cross-domain Identity Management (SCIM){% endif %}.' versions: ghec: '*' ghes: '*' @@ -32,11 +32,6 @@ children: - /updating-a-users-saml-nameid - /switching-your-saml-configuration-from-an-organization-to-an-enterprise-account - /troubleshooting-saml-authentication -ms.openlocfilehash: 4258d753035ce174cb0f45f186b2b99c9ce1752b -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145099965' --- + {% data reusables.enterprise-accounts.emu-saml-note %} diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md index d17cfa8c89..a7575e8ea9 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md @@ -1,7 +1,7 @@ --- title: SAML configuration reference shortTitle: SAML reference -intro: 'You can see SAML metadata for {% ifversion ghec %}your organization or enterprise on {% data variables.product.product_name %}{% elsif ghes %}{% data variables.product.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %}, and you can learn more about available SAML attributes and response requirements.' +intro: 'You can see SAML metadata for {% ifversion ghec %}your organization or enterprise on {% data variables.product.product_name %}{% elsif ghes %}{% data variables.location.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %}, and you can learn more about available SAML attributes and response requirements.' versions: ghec: '*' ghes: '*' @@ -17,7 +17,7 @@ topics: ## About SAML configuration -To use SAML single sign-on (SSO) for authentication to {% data variables.product.product_name %}, you must configure both your external SAML identity provider (IdP) and {% ifversion ghes %}{% data variables.product.product_location %}{% elsif ghec %}your enterprise or organization on {% data variables.product.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %}. In a SAML configuration, {% data variables.product.product_name %} functions as a SAML service provider (SP). +To use SAML single sign-on (SSO) for authentication to {% data variables.product.product_name %}, you must configure both your external SAML identity provider (IdP) and {% ifversion ghes %}{% data variables.location.product_location %}{% elsif ghec %}your enterprise or organization on {% data variables.location.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %}. In a SAML configuration, {% data variables.product.product_name %} functions as a SAML service provider (SP). You must enter unique values from your SAML IdP when configuring SAML SSO for {% data variables.product.product_name %}, and you must also enter unique values from {% data variables.product.product_name %} on your IdP. For more information about the configuration of SAML SSO for {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise){% ifversion ghes or ghae %}{% elsif ghec %}" or "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization){% endif %}." @@ -31,27 +31,27 @@ The SP metadata for {% data variables.product.product_name %} is available for e You can configure SAML SSO for an individual organization in your enterprise. You can also configure SAML SSO for an organization if you use an individual organization on {% data variables.product.product_name %} and do not use an enterprise account. For more information, see "[Managing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization)." -The SP metadata for an organization on {% data variables.product.product_location %} is available at `https://github.com/orgs/ORGANIZATION/saml/metadata`, where **ORGANIZATION** is the name of your organization on {% data variables.product.product_location %}. +The SP metadata for an organization on {% data variables.location.product_location %} is available at `https://github.com/orgs/ORGANIZATION/saml/metadata`, where **ORGANIZATION** is the name of your organization on {% data variables.location.product_location %}. | Value | Other names | Description | Example | | :- | :- | :- | :- | -| SP Entity ID | SP URL, audience restriction | The top-level URL for your organization on {% data variables.product.product_location %} | `https://github.com/orgs/ORGANIZATION` | +| SP Entity ID | SP URL, audience restriction | The top-level URL for your organization on {% data variables.location.product_location %} | `https://github.com/orgs/ORGANIZATION` | | SP Assertion Consumer Service (ACS) URL | Reply, recipient, or destination URL | URL where IdP sends SAML responses | `https://github.com/orgs/ORGANIZATION/saml/consume` | | SP Single Sign-On (SSO) URL | | URL where IdP begins SSO | `https://github.com/orgs/ORGANIZATION/saml/sso` | ### Enterprises -The SP metadata for an enterprise on {% data variables.product.product_location %} is available at `https://github.com/enterprises/ENTERPRISE/saml/metadata`, where **ENTERPRISE** is the name of your enterprise on {% data variables.product.product_location %}. +The SP metadata for an enterprise on {% data variables.location.product_location %} is available at `https://github.com/enterprises/ENTERPRISE/saml/metadata`, where **ENTERPRISE** is the name of your enterprise on {% data variables.location.product_location %}. | Value | Other names | Description | Example | | :- | :- | :- | :- | -| SP Entity ID | SP URL, audience restriction | The top-level URL for your enterprise on {% data variables.product.product_location %} | `https://github.com/enterprises/ENTERPRISE` | +| SP Entity ID | SP URL, audience restriction | The top-level URL for your enterprise on {% data variables.location.product_location %} | `https://github.com/enterprises/ENTERPRISE` | | SP Assertion Consumer Service (ACS) URL | Reply, recipient, or destination URL | URL where IdP sends SAML responses | `https://github.com/enterprises/ENTERPRISE/saml/consume` | | SP Single Sign-On (SSO) URL | | URL where IdP begins SSO | `https://github.com/enterprises/ENTERPRISE/saml/sso` | {% elsif ghes %} -The SP metadata for {% data variables.product.product_location %} is available at `http(s)://HOSTNAME/saml/metadata`, where **HOSTNAME** is the hostname for your instance. {% data variables.product.product_name %} uses the `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST` binding. +The SP metadata for {% data variables.location.product_location %} is available at `http(s)://HOSTNAME/saml/metadata`, where **HOSTNAME** is the hostname for your instance. {% data variables.product.product_name %} uses the `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST` binding. | Value | Other names | Description | Example | | :- | :- | :- | :- | @@ -78,10 +78,10 @@ The following SAML attributes are available for {% data variables.product.produc | Name | Required? | Description | | :- | :- | :- | | `NameID` | Yes | A persistent user identifier. Any persistent name identifier format may be used. {% ifversion ghec %}If you use an enterprise with {% data variables.product.prodname_emus %}, {% endif %}{% data variables.product.product_name %} will normalize the `NameID` element to use as a username unless one of the alternative assertions is provided. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."

{% note %}**Note:** It's important to use a human-readable, persistent identifier. Using a transient identifier format like `urn:oasis:names:tc:SAML:2.0:nameid-format:transient` will result in re-linking of accounts on every sign-in, which can be detrimental to authorization management.{% endnote %} | -| `SessionNotOnOrAfter` | No | The date that {% data variables.product.product_name %} invalidates the associated session. After invalidation, the person must authenticate once again to access {% ifversion ghec or ghae %}your enterprise's resources{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. For more information, see "[Session duration and timeout](#session-duration-and-timeout)." | +| `SessionNotOnOrAfter` | No | The date that {% data variables.product.product_name %} invalidates the associated session. After invalidation, the person must authenticate once again to access {% ifversion ghec or ghae %}your enterprise's resources{% elsif ghes %}{% data variables.location.product_location %}{% endif %}. For more information, see "[Session duration and timeout](#session-duration-and-timeout)." | {%- ifversion ghes or ghae %} | `administrator` | No | When the value is `true`, {% data variables.product.product_name %} will automatically promote the user to be a {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %}. Setting this attribute to anything but `true` will result in demotion, as long as the value is not blank. Omitting this attribute or leaving the value blank will not change the role of the user. | -| `username` | No | The username for {% data variables.product.product_location %}. | +| `username` | No | The username for {% data variables.location.product_location %}. | {%- endif %} | `full_name` | No | {% ifversion ghec %}If you configure SAML SSO for an enterprise and you use {% data variables.product.prodname_emus %}, the{% else %}The{% endif %} full name of the user to display on the user's profile page. | | `emails` | No | The email addresses for the user.{% ifversion ghes or ghae %} You can specify more than one address.{% endif %}{% ifversion ghec or ghes %} If you sync license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_github_connect %} uses `emails` to identify unique users across products. For more information, see "[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."{% endif %} | @@ -102,7 +102,7 @@ To specify more than one value for an attribute, use multiple `` element on the root response document and match the ACS URL only when the root response document is signed. If your IdP signs the assertion, {% data variables.product.product_name %} will ignore the assertion. -- Your IdP must always provide the `` element as part of the `` element. The value must match your `EntityId` for {% data variables.product.product_name %}.{% ifversion ghes or ghae %} This value is the URL where you access {% data variables.product.product_location %}, such as {% ifversion ghes %}`http(s)://HOSTNAME`{% elsif ghae %}`https://SUBDOMAIN.githubenterprise.com`, `https://SUBDOMAIN.github.us`, or `https://SUBDOMAIN.ghe.com`{% endif %}.{% endif %} +- Your IdP must always provide the `` element as part of the `` element. The value must match your `EntityId` for {% data variables.product.product_name %}.{% ifversion ghes or ghae %} This value is the URL where you access {% data variables.location.product_location %}, such as {% ifversion ghes %}`http(s)://HOSTNAME`{% elsif ghae %}`https://SUBDOMAIN.githubenterprise.com`, `https://SUBDOMAIN.github.us`, or `https://SUBDOMAIN.ghe.com`{% endif %}.{% endif %} {%- ifversion ghec %} - If you configure SAML for an organization, this value is `https://github.com/orgs/ORGANIZATION`. @@ -132,7 +132,7 @@ To specify more than one value for an attribute, use multiple `ENCODED OUTPUT +$ base64 --decode ENCODED_OUTPUT ``` -## Error: "Another user already owns the account"(错误:“其他用户已拥有该帐户”) +## Error: "Another user already owns the account" -当用户首次使用 SAML 身份验证登录 {% data variables.product.product_location %} 时,{% data variables.product.product_name %} 会在实例上创建一个用户帐户并将 SAML `NameID` 映射到该帐户。 +When a user signs into {% data variables.location.product_location %} for the first time with SAML authentication, {% data variables.product.product_name %} creates a user account on the instance and maps the SAML `NameID` to the account. -当用户再次登录时,{% data variables.product.prodname_ghe_server %} 会比较帐户的 `NameID` 映射与 IdP 的响应。 如果 IdP 响应中的 `NameID` 不再与 {% data variables.product.product_name %} 对用户预期的 `NameID` 匹配,登录将失败。 用户将看到以下消息。 +When the user signs in again, {% data variables.product.prodname_ghe_server %} compares the account's `NameID` mapping to the IdP's response. If the `NameID` in the IdP's response no longer matches the `NameID` that {% data variables.product.product_name %} expects for the user, the sign-in will fail. The user will see the following message. -> 另一个用户已经拥有该帐户。 请让您的管理员检查身份验证日志。 +> Another user already owns the account. Please have your administrator check the authentication log. -该消息通常表示此人的用户名或电子邮件地址已在 IdP 上更改。 请确保 {% data variables.product.prodname_ghe_server %} 上用户帐户的 `NameID` 映射与 IdP 上用户的 `NameID` 匹配。 有关详细信息,请参阅“[更新用户的 SAML `NameID`](/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid)”。 +The message typically indicates that the person's username or email address has changed on the IdP. Ensure that the `NameID` mapping for the user account on {% data variables.product.prodname_ghe_server %} matches the user's `NameID` on your IdP. For more information, see "[Updating a user's SAML `NameID`](/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid)." -## Error: Recipient in SAML response was blank or not valid(错误:SAML 响应中的收件人为空或无效) +## Error: Recipient in SAML response was blank or not valid -如果 `Recipient` 与 {% data variables.product.product_location %} 的 ACS URL 不匹配,则当用户尝试进行身份验证时,身份验证日志中将显示以下两条错误消息之一。 +If the `Recipient` does not match the ACS URL for {% data variables.location.product_location %}, one of the following two error messages will appear in the authentication log when a user attempts to authenticate. ``` Recipient in the SAML response must not be blank. @@ -84,29 +81,31 @@ Recipient in the SAML response must not be blank. Recipient in the SAML response was not valid. ``` -请确保将 IdP 上的 `Recipient` 的值设置为 {% data variables.product.product_location %} 的完整 ACS URL。 例如 `https://ghe.corp.example.com/saml/consume`。 +Ensure that you set the value for `Recipient` on your IdP to the full ACS URL for {% data variables.location.product_location %}. For example, `https://ghe.corp.example.com/saml/consume`. -## Error: "SAML Response is not signed or has been modified"(错误:“SAML 响应未签名或已修改”) +## Error: "SAML Response is not signed or has been modified" -如果您的 IdP 未对 SAML 响应进行签名,或者签名与内容不匹配,则身份验证日志中将显示以下错误消息。 +If your IdP does not sign the SAML response, or the signature does not match the contents, the following error message will appear in the authentication log. ``` SAML Response is not signed or has been modified. ``` -确保为 IdP 上的 {% data variables.product.product_name %} 应用程序配置签名的断言。 +Ensure that you configure signed assertions for the {% data variables.product.product_name %} application on your IdP. -## Error: "Audience is invalid" or "No assertion found"(错误:“受众无效”或“未找到断言”) +## Error: "Audience is invalid" or "No assertion found" -如果 IdP 的响应中 `Audience` 的值缺失或不正确,则身份验证日志中将显示以下错误消息。 +If the IdP's response has a missing or incorrect value for `Audience`, the following error message will appear in the authentication log. ``` Audience is invalid. Audience attribute does not match https://YOUR-INSTANCE-URL ``` -请确保将 IdP 上的 `Audience` 的值设置为 {% data variables.product.product_location %} 的 `EntityId`,这是实例的完整 URL。 例如,`https://ghe.corp.example.com`。 +Ensure that you set the value for `Audience` on your IdP to the `EntityId` for {% data variables.location.product_location %}, which is the full URL to your instance. For example, `https://ghe.corp.example.com`. {% endif %} {% data reusables.saml.current-time-earlier-than-notbefore-condition %} -{% ifversion ghec %} {% data reusables.saml.authentication-loop %} {% endif %} +{% ifversion ghec %} +{% data reusables.saml.authentication-loop %} +{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md index b84f2f4919..65bdad9b8c 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md @@ -1,7 +1,7 @@ --- -title: 更新用户的 SAML NameID +title: Updating a user's SAML NameID shortTitle: Update SAML NameID -intro: '如果标识提供者 (IdP) 上的帐户的`NameID` 发生更改,并且该人员无法再{% ifversion ghes or ghae %}登录到 {% data variables.product.product_location %}{% elsif ghec %}进行身份验证以访问企业的资源{% endif %},必须{% ifversion ghec %}联系 {% data variables.product.company_short %} 支持部门,或撤销该人员的链接标识{% elsif ghes %}更新 {% data variables.product.product_location %} 上的 `NameID` 映射{% elsif ghae %}联系 {% data variables.product.company_short %} 支持部门{% endif %}。' +intro: 'When an account''s `NameID` changes on your identity provider (IdP) and the person can no longer {% ifversion ghes or ghae %}sign into {% data variables.location.product_location %}{% elsif ghec %}authenticate to access your enterprise''s resources{% endif %}, you must {% ifversion ghec %}either contact {% data variables.product.company_short %} Support or revoke the person''s linked identity{% elsif ghes %}update the `NameID` mapping on {% data variables.location.product_location %}{% elsif ghae %}contact {% data variables.product.company_short %} Support{% endif %}.' versions: ghes: '*' type: how_to @@ -11,29 +11,25 @@ topics: - Enterprise - Identity - SSO -ms.openlocfilehash: 7a151143219fc0885861beedb69a2608983c5588 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717899' --- -## 关于用户的 SAML `NameID` 更新 -在某些情况下,可能需要更新与 SAML IdP 上的某个用户帐户关联的值。 如果该标识符也是你用于对 {% data variables.product.product_name %} 进行身份验证的 `NameID`,则必须更新实例上的 `NameID` 映射,以便此人可以继续成功进行身份验证。 有关详细信息,请参阅“[外部身份验证的用户名注意事项](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)”。 +## About updates to users' SAML `NameID` -## 更新用户的 SAML `NameID` +In some situations, you may need to update values associated with a person's account on your SAML IdP. If that identifier is also the `NameID` that you use for authentication on {% data variables.product.product_name %}, you must update the `NameID` mapping on your instance so the person can continue to authenticate successfully. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)." -企业所有者可以在 {% data variables.product.product_name %} 实例上更新用户的 SAML `NameID`。 +## Updating a user's SAML `NameID` + +Enterprise owners can update a user's SAML `NameID` on a {% data variables.product.product_name %} instance. {% data reusables.enterprise_site_admin_settings.access-settings %} -2. 在左侧边栏中,单击“所有用户”。 - ![站点管理员设置中的“所有用户”边栏项](/assets/images/enterprise/site-admin-settings/all-users.png) -3. 在用户列表中,单击要为其更新 `NameID` 映射的用户名。 - ![实例用户帐户列表中的用户名](/assets/images/enterprise/site-admin-settings/all-users-click-username.png) {% data reusables.enterprise_site_admin_settings.security-tab %} -5. 在“更新 SAML NameID”右侧,单击“编辑”。 - ![“SAML 身份验证”下和“更新 SAML NameID”右侧的“编辑”按钮](/assets/images/enterprise/site-admin-settings/update-saml-nameid-edit.png) -6. 在“NameID”字段中,为用户键入新的 `NameID`。 - ![键入了 NameID 的模式对话框中的“NameID”字段](/assets/images/enterprise/site-admin-settings/update-saml-nameid-field-in-modal.png) -7. 单击“更新 NameID”。 - ![模式中已更新 NameID 值下的“更新 NameID”按钮](/assets/images/enterprise/site-admin-settings/update-saml-nameid-update.png) +2. In the left sidebar, click **All users**. + !["All users" sidebar item in site administrator settings](/assets/images/enterprise/site-admin-settings/all-users.png) +3. In the list of users, click the username you'd like to update the `NameID` mapping for. + ![Username in list of instance user accounts](/assets/images/enterprise/site-admin-settings/all-users-click-username.png) +{% data reusables.enterprise_site_admin_settings.security-tab %} +5. To the right of "Update SAML NameID", click **Edit** . + !["Edit" button under "SAML authentication" and to the right of "Update SAML NameID"](/assets/images/enterprise/site-admin-settings/update-saml-nameid-edit.png) +6. In the "NameID" field, type the new `NameID` for the user. + !["NameID" field in modal dialog with NameID typed](/assets/images/enterprise/site-admin-settings/update-saml-nameid-field-in-modal.png) +7. Click **Update NameID**. + !["Update NameID" button under updated NameID value within modal](/assets/images/enterprise/site-admin-settings/update-saml-nameid-update.png) diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md index 077f43d62e..e45d5484e8 100644 --- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md +++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md @@ -1,6 +1,6 @@ --- -title: 在 AWS 上安装 GitHub Enterprise Server -intro: '要在 Amazon Web Services (AWS) 上安装 {% data variables.product.prodname_ghe_server %},您必须启动 Amazon Elastic Compute Cloud (EC2) 实例并创建和连接单独的 Amazon Elastic Block Store (EBS) 数据卷。' +title: Installing GitHub Enterprise Server on AWS +intro: 'To install {% data variables.product.prodname_ghe_server %} on Amazon Web Services (AWS), you must launch an Amazon Elastic Compute Cloud (EC2) instance and create and attach a separate Amazon Elastic Block Store (EBS) data volume.' redirect_from: - /enterprise/admin/guides/installation/installing-github-enterprise-on-aws - /enterprise/admin/installation/installing-github-enterprise-server-on-aws @@ -14,136 +14,133 @@ topics: - Infrastructure - Set up shortTitle: Install on AWS -ms.openlocfilehash: f91f2337cc13690d0476c836a15ec72a5c0685cb -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147876079' --- -## 先决条件 +## Prerequisites - {% data reusables.enterprise_installation.software-license %} -- 您必须具有能够启动 EC2 实例和创建 EBS 卷的 AWS 帐户。 有关详细信息,请参阅 [Amazon Web Services 网站](https://aws.amazon.com/)。 -- 启动 {% data variables.product.product_location %} 所需的大部分操作也可以使用 AWS 管理控制台执行。 不过,我们建议安装 AWS 命令行接口 (CLI) 进行初始设置。 下文介绍了使用 AWS CLI 的示例。 有关详细信息,请参阅 Amazon 指南“[使用 AWS 管理控制台](http://docs.aws.amazon.com/awsconsolehelpdocs/latest/gsg/getting-started.html)”和“[什么是 AWS 命令行接口](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html)”。 +- You must have an AWS account capable of launching EC2 instances and creating EBS volumes. For more information, see the [Amazon Web Services website](https://aws.amazon.com/). +- Most actions needed to launch {% data variables.location.product_location %} may also be performed using the AWS management console. However, we recommend installing the AWS command line interface (CLI) for initial setup. Examples using the AWS CLI are included below. For more information, see Amazon's guides "[Working with the AWS Management Console](http://docs.aws.amazon.com/awsconsolehelpdocs/latest/gsg/getting-started.html)" and "[What is the AWS Command Line Interface](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html)." {% note %} -注意:目前 {% data variables.product.prodname_ghe_server %} 不支持使用 Amazon IDMSv2 元数据 API。 +**Note:** At this time {% data variables.product.prodname_ghe_server %} does not support the use of the Amazon IDMSv2 Metadata API. {% endnote %} -本指南假定您已熟悉以下 AWS 概念: +This guide assumes you are familiar with the following AWS concepts: - - [启动 EC2 实例](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/LaunchingAndUsingInstances.html) - - [管理 EBS 卷](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html) - - [使用安全组](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html)(用于管理对实例的网络访问) - - [弹性 IP 地址 (EIP)](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html)(强烈建议用于生产环境) - - [EC2 和虚拟私有云](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html)(如果你计划启动虚拟私有云) - - [AWS 定价](https://aws.amazon.com/pricing/)(用于计算和管理成本) + - [Launching EC2 Instances](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/LaunchingAndUsingInstances.html) + - [Managing EBS Volumes](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html) + - [Using Security Groups](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html) (For managing network access to your instance) + - [Elastic IP Addresses (EIP)](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html) (Strongly recommended for production environments) + - [EC2 and Virtual Private Cloud](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html) (If you plan to launch into a Virtual Private Cloud) + - [AWS Pricing](https://aws.amazon.com/pricing/) (For calculating and managing costs) -有关体系结构概述,请参阅“[用于部署 GitHub Enterprise Server 的 AWS 体系结构图](/assets/images/installing-github-enterprise-server-on-aws.png)”。 +For an architectural overview, see the "[AWS Architecture Diagram for Deploying GitHub Enterprise Server](/assets/images/installing-github-enterprise-server-on-aws.png)". -本指南建议在 AWS 上设置 {% data variables.product.product_location %} 时使用最小权限原则。 有关详细信息,请参阅 [AWS 标识和访问管理 (IAM) 文档](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege)。 +This guide recommends the principle of least privilege when setting up {% data variables.location.product_location %} on AWS. For more information, refer to the [AWS Identity and Access Management (IAM) documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege). -## 硬件注意事项 +## Hardware considerations {% data reusables.enterprise_installation.hardware-considerations-all-platforms %} -## 确定实例类型 +## Determining the instance type -在 AWS 上启动 {% data variables.product.product_location %} 之前,您需要确定最符合您的组织需求的设备类型。 若要查看 {% data variables.product.product_name %} 的最低要求,请参阅“[最低要求](#minimum-requirements)”。 +Before launching {% data variables.location.product_location %} on AWS, you'll need to determine the machine type that best fits the needs of your organization. To review the minimum requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)." {% data reusables.enterprise_installation.warning-on-scaling %} {% data reusables.enterprise_installation.aws-instance-recommendation %} -## 选择 {% data variables.product.prodname_ghe_server %} AMI +## Selecting the {% data variables.product.prodname_ghe_server %} AMI -您可以使用 {% data variables.product.prodname_ghe_server %} 门户或 AWS CLI 为 {% data variables.product.prodname_ghe_server %} 选择 Amazon Machine Image (AMI)。 +You can select an Amazon Machine Image (AMI) for {% data variables.product.prodname_ghe_server %} using the {% data variables.product.prodname_ghe_server %} portal or the AWS CLI. -{% data variables.product.prodname_ghe_server %} 的 AMI 适用于 AWS GovCloud(美国东部和美国西部)区域。 因此,受特定法规要求约束的美国客户可以在符合联邦要求的云环境中运行 {% data variables.product.prodname_ghe_server %}。 有关 AWS 符合联邦和其他标准的详细信息,请参阅 [AWS 的 GovCloud (US) 页面](http://aws.amazon.com/govcloud-us/)和 [AWS 的合规性页面](https://aws.amazon.com/compliance/)。 +AMIs for {% data variables.product.prodname_ghe_server %} are available in the AWS GovCloud (US-East and US-West) region. This allows US customers with specific regulatory requirements to run {% data variables.product.prodname_ghe_server %} in a federally compliant cloud environment. For more information on AWS's compliance with federal and other standards, see [AWS's GovCloud (US) page](http://aws.amazon.com/govcloud-us/) and [AWS's compliance page](https://aws.amazon.com/compliance/). -### 使用 {% data variables.product.prodname_ghe_server %} 门户选择 AMI +### Using the {% data variables.product.prodname_ghe_server %} portal to select an AMI {% data reusables.enterprise_installation.download-appliance %} -3. 在“云中的 {% data variables.product.prodname_dotcom %}”下,选择“选择你的平台”下拉菜单,然后单击“Amazon Web Services”。 -4. 选择“选择你的 AWS 区域”下拉菜单,然后单击所需区域。 -5. 记下显示的 AMI ID。 +3. Under "{% data variables.product.prodname_dotcom %} in the Cloud", select the "Select your platform" dropdown menu, and click **Amazon Web Services**. +4. Select the "Select your AWS region" drop-down menu, and click your desired region. +5. Take note of the AMI ID that is displayed. -### 使用 AWS CLI 选择 AMI +### Using the AWS CLI to select an AMI -1. 使用 AWS CLI 获取由 {% data variables.product.prodname_dotcom %} 的 AWS 所有者 ID(`025577942450` 代表 GovCloud,`895557238572` 代表其他地区)发布的 {% data variables.product.prodname_ghe_server %} 图像列表。 有关详细信息,请参阅 AWS 文档中的“[describe-images](http://docs.aws.amazon.com/cli/latest/reference/ec2/describe-images.html)”。 +1. Using the AWS CLI, get a list of {% data variables.product.prodname_ghe_server %} images published by {% data variables.product.prodname_dotcom %}'s AWS owner IDs (`025577942450` for GovCloud, and `895557238572` for other regions). For more information, see "[describe-images](http://docs.aws.amazon.com/cli/latest/reference/ec2/describe-images.html)" in the AWS documentation. ```shell aws ec2 describe-images \ - --owners OWNER ID \ + --owners OWNER_ID \ --query 'sort_by(Images,&Name)[*].{Name:Name,ImageID:ImageId}' \ --output=text ``` -2. 记下最新 {% data variables.product.prodname_ghe_server %} 映像的 AMI ID。 +2. Take note of the AMI ID for the latest {% data variables.product.prodname_ghe_server %} image. -## 添加安全组 +## Creating a security group -如果是首次设置 AMI,您需要创建安全组并为下表中的每个端口添加新的安全组规则。 有关详细信息,请参阅 AWS 指南“[使用安全组](http://docs.aws.amazon.com/cli/latest/userguide/cli-ec2-sg.html)”。 +If you're setting up your AMI for the first time, you will need to create a security group and add a new security group rule for each port in the table below. For more information, see the AWS guide "[Using Security Groups](http://docs.aws.amazon.com/cli/latest/userguide/cli-ec2-sg.html)." -1. 使用 AWS CLI 创建新的安全组。 有关详细信息,请参阅 AWS 文档中的“[create-security-group](http://docs.aws.amazon.com/cli/latest/reference/ec2/create-security-group.html)”。 +1. Using the AWS CLI, create a new security group. For more information, see "[create-security-group](http://docs.aws.amazon.com/cli/latest/reference/ec2/create-security-group.html)" in the AWS documentation. ```shell - $ aws ec2 create-security-group --group-name SECURITY_GROUP_NAME --description "SECURITY GROUP DESCRIPTION" + $ aws ec2 create-security-group --group-name SECURITY_GROUP_NAME --description "SECURITY GROUP DESCRIPTION" ``` -2. 记下新创建的安全组的安全组 ID (`sg-xxxxxxxx`)。 +2. Take note of the security group ID (`sg-xxxxxxxx`) of your newly created security group. -3. 为下表中的每个端口创建安全组规则。 有关详细信息,请参阅 AWS 文档中的“[authorize-security-group-ingress](http://docs.aws.amazon.com/cli/latest/reference/ec2/authorize-security-group-ingress.html)”。 +3. Create a security group rule for each of the ports in the table below. For more information, see "[authorize-security-group-ingress](http://docs.aws.amazon.com/cli/latest/reference/ec2/authorize-security-group-ingress.html)" in the AWS documentation. ```shell - $ aws ec2 authorize-security-group-ingress --group-id SECURITY_GROUP_ID --protocol PROTOCOL --port PORT_NUMBER --cidr SOURCE IP RANGE + $ aws ec2 authorize-security-group-ingress --group-id SECURITY_GROUP_ID --protocol PROTOCOL --port PORT_NUMBER --cidr SOURCE IP RANGE ``` - 此表列出了每个端口的用途。 + This table identifies what each port is used for. {% data reusables.enterprise_installation.necessary_ports %} -## 创建 {% data variables.product.prodname_ghe_server %} 实例 +## Creating the {% data variables.product.prodname_ghe_server %} instance -要创建实例,您需要使用 {% data variables.product.prodname_ghe_server %} AMI 启动 EC2 实例,并连接额外的存储卷来存储实例数据。 有关详细信息,请参阅“[硬件注意事项](#hardware-considerations)”。 +To create the instance, you'll need to launch an EC2 instance with your {% data variables.product.prodname_ghe_server %} AMI and attach an additional storage volume for your instance data. For more information, see "[Hardware considerations](#hardware-considerations)." {% note %} -注意:可以加密数据磁盘以获得额外的安全级别,并确保写入实例的所有数据都受到保护。 使用加密磁盘会对性能稍有影响。 如果你决定要对卷加密,强烈建议你在首次启动实例之前进行加密。 -有关详细信息,请参阅 [Amazon EBS 加密指南](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html)。 +**Note:** You can encrypt the data disk to gain an extra level of security and ensure that any data you write to your instance is protected. There is a slight performance impact when using encrypted disks. If you decide to encrypt your volume, we strongly recommend doing so **before** starting your instance for the first time. + For more information, see the [Amazon guide on EBS encryption](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html). {% endnote %} {% warning %} -警告:如果决定在配置完实例后启用加密,则需要将数据迁移到加密卷,此过程将导致用户停机一段时间。 +**Warning:** If you decide to enable encryption after you've configured your instance, you will need to migrate your data to the encrypted volume, which will incur some downtime for your users. {% endwarning %} -### 启动 EC2 实例 +### Launching an EC2 instance -在 AWS CLI 中,使用 AMI 以及您创建的安全组启动 EC2 实例。 附上新的块设备,以用作实例数据的存储卷,并根据您的用户许可数配置大小。 有关详细信息,请参阅 AWS 文档中的“[run-instances](http://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html)”。 +In the AWS CLI, launch an EC2 instance using your AMI and the security group you created. Attach a new block device to use as a storage volume for your instance data, and configure the size based on your user license count. For more information, see "[run-instances](http://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html)" in the AWS documentation. ```shell aws ec2 run-instances \ - --security-group-ids SECURITY_GROUP_ID \ - --instance-type INSTANCE_TYPE \ - --image-id AMI_ID \ - --block-device-mappings '[{"DeviceName":"/dev/xvdf","Ebs":{"VolumeSize":SIZE,"VolumeType":"TYPE"}}]' \ - --region REGION \ + --security-group-ids SECURITY_GROUP_ID \ + --instance-type INSTANCE_TYPE \ + --image-id AMI_ID \ + --block-device-mappings '[{"DeviceName":"/dev/xvdf","Ebs":{"VolumeSize":SIZE,"VolumeType":"TYPE"}}]' \ + --region REGION \ --ebs-optimized ``` -### 分配弹性 IP 并将其与实例关联 +### Allocating an Elastic IP and associating it with the instance -如果是生产实例,我们强烈建议先分配弹性 IP (EIP) 并将其与实例关联,然后再继续进行 {% data variables.product.prodname_ghe_server %} 配置。 否则,实例重新启动后将无法保留公共 IP 地址。 有关详细信息,请参阅 Amazon 文档中的“[分配弹性 IP 地址](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-allocating)”和“[将弹性 IP 地址与正在运行的实例关联](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-associating)”。 +If this is a production instance, we strongly recommend allocating an Elastic IP (EIP) and associating it with the instance before proceeding to {% data variables.product.prodname_ghe_server %} configuration. Otherwise, the public IP address of the instance will not be retained after instance restarts. For more information, see "[Allocating an Elastic IP Address](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-allocating)" and "[Associating an Elastic IP Address with a Running Instance](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-associating)" in the Amazon documentation. -如果采用生产高可用性配置,主实例和副本实例均应分配单独的 EIP。 有关详细信息,请参阅“[为高可用性配置 {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)”。 +Both primary and replica instances should be assigned separate EIPs in production High Availability configurations. For more information, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/enterprise/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)." -## 配置 {% data variables.product.prodname_ghe_server %} 实例 +## Configuring the {% data variables.product.prodname_ghe_server %} instance -{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} {% data reusables.enterprise_installation.upload-a-license-file %} {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} 有关详细信息,请参阅“[配置 {% data variables.product.prodname_ghe_server %} 设备](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)”。 -{% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} +{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} +{% data reusables.enterprise_installation.upload-a-license-file %} +{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." +{% data reusables.enterprise_installation.instance-will-restart-automatically %} +{% data reusables.enterprise_installation.visit-your-instance %} -## 延伸阅读 +## Further reading -- [系统概述](/enterprise/admin/guides/installation/system-overview) {% ifversion ghes %} -- [关于升级到新版本](/admin/overview/about-upgrades-to-new-releases) {% endif %} +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md index 4d4ead15a0..a23d4e9069 100644 --- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md +++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md @@ -1,6 +1,6 @@ --- -title: 在 Azure 上安装 GitHub Enterprise Server -intro: '若要在 Azure 上安装 {% data variables.product.prodname_ghe_server %},必须部署到支持高级存储的内存优化实例上。' +title: Installing GitHub Enterprise Server on Azure +intro: 'To install {% data variables.product.prodname_ghe_server %} on Azure, you must deploy onto a memory-optimized instance that supports premium storage.' redirect_from: - /enterprise/admin/guides/installation/installing-github-enterprise-on-azure - /enterprise/admin/installation/installing-github-enterprise-server-on-azure @@ -14,80 +14,74 @@ topics: - Infrastructure - Set up shortTitle: Install on Azure -ms.openlocfilehash: 52c435b01e830968eaf81dc411727ea2bacabd2d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145098040' --- -您可以将 {% data variables.product.prodname_ghe_server %} 部署在全局 Azure 或 Azure Government 上。 +You can deploy {% data variables.product.prodname_ghe_server %} on global Azure or Azure Government. -## 先决条件 +## Prerequisites - {% data reusables.enterprise_installation.software-license %} -- 您必须具有能够配置新机器的 Azure 帐户。 有关详细信息,请参阅 [Microsoft Azure 网站](https://azure.microsoft.com)。 -- 启动虚拟机 (VM) 所需的大部分操作也可以使用 Azure Portal 执行。 不过,我们建议安装 Azure 命令行接口 (CLI) 进行初始设置。 下文介绍了使用 Azure CLI 2.0 的示例。 有关详细信息,请参阅 Azure 指南“[安装 Azure CLI 2.0](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)”。 +- You must have an Azure account capable of provisioning new machines. For more information, see the [Microsoft Azure website](https://azure.microsoft.com). +- Most actions needed to launch your virtual machine (VM) may also be performed using the Azure Portal. However, we recommend installing the Azure command line interface (CLI) for initial setup. Examples using the Azure CLI 2.0 are included below. For more information, see Azure's guide "[Install Azure CLI 2.0](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)." -## 硬件注意事项 +## Hardware considerations {% data reusables.enterprise_installation.hardware-considerations-all-platforms %} -## 确定虚拟机类型 +## Determining the virtual machine type -在 Azure 上启动 {% data variables.product.product_location %} 之前,您需要确定最符合您的组织需求的设备类型。 有关内存优化计算机的详细信息,请参阅 Microsoft Azure 文档中的“[内存优化虚拟机大小](https://docs.microsoft.com/en-gb/azure/virtual-machines/sizes-memory)”。 若要查看 {% data variables.product.product_name %} 的最低资源要求,请参阅“[最低要求](#minimum-requirements)”。 +Before launching {% data variables.location.product_location %} on Azure, you'll need to determine the machine type that best fits the needs of your organization. For more information about memory optimized machines, see "[Memory optimized virtual machine sizes](https://docs.microsoft.com/en-gb/azure/virtual-machines/sizes-memory)" in the Microsoft Azure documentation. To review the minimum resource requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)." {% data reusables.enterprise_installation.warning-on-scaling %} {% data reusables.enterprise_installation.azure-instance-recommendation %} -## 创建 {% data variables.product.prodname_ghe_server %} 虚拟机 +## Creating the {% data variables.product.prodname_ghe_server %} virtual machine {% data reusables.enterprise_installation.create-ghe-instance %} -1. 找到最新的 {% data variables.product.prodname_ghe_server %} 设备映像。 有关 `vm image list` 命令的详细信息,请参阅 Microsoft 文档中的“[`az vm image list`](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)”。 +1. Find the most recent {% data variables.product.prodname_ghe_server %} appliance image. For more information about the `vm image list` command, see "[`az vm image list`](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)" in the Microsoft documentation. ```shell $ az vm image list --all -f GitHub-Enterprise | grep '"urn":' | sort -V ``` -2. 使用找到的设备映像创建新的 VM。 有关详细信息,请参阅 Microsoft 文档中的“[`az vm create`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_create)”。 +2. Create a new VM using the appliance image you found. For more information, see "[`az vm create`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_create)" in the Microsoft documentation. - 传入以下选项:VM 名称、资源组、VM 大小、首选 Azure 地区名称、上一步中列出的设备映像 VM 的名称,以及用于高级存储的存储 SKU。 有关资源组的详细信息,请参阅 Microsoft 文档中的“[资源组](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview#resource-groups)”。 + Pass in options for the name of your VM, the resource group, the size of your VM, the name of your preferred Azure region, the name of the appliance image VM you listed in the previous step, and the storage SKU for premium storage. For more information about resource groups, see "[Resource groups](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview#resource-groups)" in the Microsoft documentation. ```shell - $ az vm create -n VM_NAME -g RESOURCE_GROUP --size VM_SIZE -l REGION --image APPLIANCE_IMAGE_NAME --storage-sku Premium_LRS + $ az vm create -n VM_NAME -g RESOURCE_GROUP --size VM_SIZE -l REGION --image APPLIANCE_IMAGE_NAME --storage-sku Premium_LRS ``` -3. 在 VM 上配置安全设置,以打开所需端口。 有关详细信息,请参阅 Microsoft 文档中的“[`az vm open-port`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)”。 请参阅下表中对每个端口的说明,以确定需要打开的端口。 +3. Configure the security settings on your VM to open up required ports. For more information, see "[`az vm open-port`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)" in the Microsoft documentation. See the table below for a description of each port to determine what ports you need to open. ```shell - $ az vm open-port -n VM_NAME -g RESOURCE_GROUP --port PORT_NUMBER + $ az vm open-port -n VM_NAME -g RESOURCE_GROUP --port PORT_NUMBER ``` - 此表列出了每个端口的用途。 + This table identifies what each port is used for. {% data reusables.enterprise_installation.necessary_ports %} -4. 创建新的未加密数据磁盘并将其附加至 VM,然后根据用户许可数配置大小。 有关详细信息,请参阅 Microsoft 文档中的“[`az vm disk attach`](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)”。 +4. Create and attach a new unencrypted data disk to the VM, and configure the size based on your user license count. For more information, see "[`az vm disk attach`](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" in the Microsoft documentation. - 传入以下选项:VM 名称(例如 `ghe-acme-corp`)、资源组、高级存储 SKU、磁盘大小(例如 `100`)以及生成的 VHD 的名称。 + Pass in options for the name of your VM (for example, `ghe-acme-corp`), the resource group, the premium storage SKU, the size of the disk (for example, `200`), and a name for the resulting VHD. ```shell - $ az vm disk attach --vm-name VM_NAME -g RESOURCE_GROUP --sku Premium_LRS --new -z SIZE_IN_GB --name ghe-data.vhd --caching ReadWrite + $ az vm disk attach --vm-name VM_NAME -g RESOURCE_GROUP --sku Premium_LRS --new -z SIZE_IN_GB --name ghe-data.vhd --caching ReadWrite ``` {% note %} - 注意:为确保非生产实例具有足够的 I/O 吞吐量,建议最小磁盘大小为 40 GiB 并启用读/写缓存 (`--caching ReadWrite`)。 + **Note:** For non-production instances to have sufficient I/O throughput, the recommended minimum disk size is 150 GiB with read/write cache enabled (`--caching ReadWrite`). {% endnote %} -## 配置 {% data variables.product.prodname_ghe_server %} 虚拟机 +## Configuring the {% data variables.product.prodname_ghe_server %} virtual machine -1. 在配置 VM 之前,您必须等待其进入 ReadyRole 状态。 使用 `vm list` 命令检查 VM 的状态。 有关详细信息,请参阅 Microsoft 文档中的“[`az vm list`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_list)”。 +1. Before configuring the VM, you must wait for it to enter ReadyRole status. Check the status of the VM with the `vm list` command. For more information, see "[`az vm list`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_list)" in the Microsoft documentation. ```shell - $ az vm list -d -g RESOURCE_GROUP -o table + $ az vm list -d -g RESOURCE_GROUP -o table > Name ResourceGroup PowerState PublicIps Fqdns Location Zones > ------ --------------- ------------ ------------ ------- ---------- ------- > VM_NAME RESOURCE_GROUP VM running 40.76.79.202 eastus @@ -95,14 +89,17 @@ ms.locfileid: '145098040' ``` {% note %} - 注意:Azure 不会自动为 VM 创建 FQDNS 条目。 有关详细信息,请参阅 Azure 指南,了解如何“[在 Azure 门户中为 Linux VM 创建完全限定域名](https://docs.microsoft.com/azure/virtual-machines/linux/portal-create-fqdn)”。 + **Note:** Azure does not automatically create a FQDNS entry for the VM. For more information, see Azure's guide on how to "[Create a fully qualified domain name in the Azure portal for a Linux VM](https://docs.microsoft.com/azure/virtual-machines/linux/portal-create-fqdn)." {% endnote %} - {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} {% data reusables.enterprise_installation.upload-a-license-file %} {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} 有关详细信息,请参阅“[配置 {% data variables.product.prodname_ghe_server %} 设备](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)”。 - {% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} + {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} + {% data reusables.enterprise_installation.upload-a-license-file %} + {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." + {% data reusables.enterprise_installation.instance-will-restart-automatically %} + {% data reusables.enterprise_installation.visit-your-instance %} -## 延伸阅读 +## Further reading -- [系统概述](/enterprise/admin/guides/installation/system-overview) {% ifversion ghes %} -- [关于升级到新版本](/admin/overview/about-upgrades-to-new-releases) {% endif %} +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md index bf81702209..b60a736ab4 100644 --- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md +++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md @@ -1,6 +1,6 @@ --- -title: 在 Google Cloud Platform 上安装 GitHub Enterprise Server -intro: '要在 Google Cloud Platform 上安装 {% data variables.product.prodname_ghe_server %},您必须部署到受支持的机器类型上,并使用持久标准磁盘或持久 SSD。' +title: Installing GitHub Enterprise Server on Google Cloud Platform +intro: 'To install {% data variables.product.prodname_ghe_server %} on Google Cloud Platform, you must deploy onto a supported machine type and use a persistent standard disk or a persistent SSD.' redirect_from: - /enterprise/admin/guides/installation/installing-github-enterprise-on-google-cloud-platform - /enterprise/admin/installation/installing-github-enterprise-server-on-google-cloud-platform @@ -14,91 +14,88 @@ topics: - Infrastructure - Set up shortTitle: Install on GCP -ms.openlocfilehash: 0fffebece94753365e1b98f014f0514cdef4f98a -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145099024' --- -## 先决条件 +## Prerequisites - {% data reusables.enterprise_installation.software-license %} -- 您必须具有能够启动 Google Compute Engine (GCE) 虚拟机 (VM) 实例的 Google Cloud Platform 帐户。 有关详细信息,请参阅 [Google Cloud Platform 网站](https://cloud.google.com/)和 [Google Cloud Platform 文档](https://cloud.google.com/docs/)。 -- 启动实例所需的大多数操作也可以使用 [Google Cloud Platform 控制台](https://cloud.google.com/compute/docs/console)执行。 不过,我们建议安装 gcloud compute 命令行工具进行初始设置。 下文介绍了使用 gcloud compute 命令行工具的示例。 有关详细信息,请参阅 Google 文档中的“[gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/)”安装和安装指南。 +- You must have a Google Cloud Platform account capable of launching Google Compute Engine (GCE) virtual machine (VM) instances. For more information, see the [Google Cloud Platform website](https://cloud.google.com/) and the [Google Cloud Platform Documentation](https://cloud.google.com/docs/). +- Most actions needed to launch your instance may also be performed using the [Google Cloud Platform Console](https://cloud.google.com/compute/docs/console). However, we recommend installing the gcloud compute command-line tool for initial setup. Examples using the gcloud compute command-line tool are included below. For more information, see the "[gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/)" installation and setup guide in the Google documentation. -## 硬件注意事项 +## Hardware considerations {% data reusables.enterprise_installation.hardware-considerations-all-platforms %} -## 确定机器类型 +## Determining the machine type -在 Google Cloud Platform 上启动 {% data variables.product.product_location %} 之前,你需要确定最适应组织需求的计算机类型。 若要查看 {% data variables.product.product_name %} 的最低要求,请参阅“[最低要求](#minimum-requirements)”。 +Before launching {% data variables.location.product_location %} on Google Cloud Platform, you'll need to determine the machine type that best fits the needs of your organization. To review the minimum requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)." {% data reusables.enterprise_installation.warning-on-scaling %} -{% data variables.product.company_short %} 建议对 {% data variables.product.prodname_ghe_server %} 使用通用高内存设备。 有关详细信息,请参阅 Google Compute Engine 文档中的“[计算机类型](https://cloud.google.com/compute/docs/machine-types#n2_high-memory_machine_types)”。 +{% data variables.product.company_short %} recommends a general-purpose, high-memory machine for {% data variables.product.prodname_ghe_server %}. For more information, see "[Machine types](https://cloud.google.com/compute/docs/machine-types#n2_high-memory_machine_types)" in the Google Compute Engine documentation. -## 选择 {% data variables.product.prodname_ghe_server %} 映像 +## Selecting the {% data variables.product.prodname_ghe_server %} image -1. 使用 [gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/) 命令行工具,列出公共 {% data variables.product.prodname_ghe_server %} 映像: +1. Using the [gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/) command-line tool, list the public {% data variables.product.prodname_ghe_server %} images: ```shell $ gcloud compute images list --project github-enterprise-public --no-standard-images ``` -2. 记下 {% data variables.product.prodname_ghe_server %} 最新 GCE 映像的映像名称。 +2. Take note of the image name for the latest GCE image of {% data variables.product.prodname_ghe_server %}. -## 配置防火墙 +## Configuring the firewall -GCE 虚拟机作为具有防火墙的网络的成员创建。 对于与 {% data variables.product.prodname_ghe_server %} VM 关联的网络,您需要将防火墙配置为允许下表中列出的必需端口。 有关 Google Cloud Platform 上防火墙规则的详细信息,请参阅 Google 指南“[防火墙规则概述](https://cloud.google.com/vpc/docs/firewalls)”。 +GCE virtual machines are created as a member of a network, which has a firewall. For the network associated with the {% data variables.product.prodname_ghe_server %} VM, you'll need to configure the firewall to allow the required ports listed in the table below. For more information about firewall rules on Google Cloud Platform, see the Google guide "[Firewall Rules Overview](https://cloud.google.com/vpc/docs/firewalls)." -1. 使用 gcloud compute 命令行工具创建网络。 有关详细信息,请参阅 Google 文档中的“[gcloud compute networks create](https://cloud.google.com/sdk/gcloud/reference/compute/networks/create)”。 +1. Using the gcloud compute command-line tool, create the network. For more information, see "[gcloud compute networks create](https://cloud.google.com/sdk/gcloud/reference/compute/networks/create)" in the Google documentation. ```shell - $ gcloud compute networks create NETWORK-NAME --subnet-mode auto + $ gcloud compute networks create NETWORK-NAME --subnet-mode auto ``` -2. 为下表中的各个端口创建防火墙规则。 有关详细信息,请参阅 Google 文档中的“[gcloud compute firewall-rules](https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/)”。 +2. Create a firewall rule for each of the ports in the table below. For more information, see "[gcloud compute firewall-rules](https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/)" in the Google documentation. ```shell - $ gcloud compute firewall-rules create RULE-NAME \ - --network NETWORK-NAME \ + $ gcloud compute firewall-rules create RULE-NAME \ + --network NETWORK-NAME \ --allow tcp:22,tcp:25,tcp:80,tcp:122,udp:161,tcp:443,udp:1194,tcp:8080,tcp:8443,tcp:9418,icmp ``` - 此表列出了必需端口以及各端口的用途。 + This table identifies the required ports and what each port is used for. {% data reusables.enterprise_installation.necessary_ports %} -## 分配静态 IP 并将其分配给 VM +## Allocating a static IP and assigning it to the VM -如果此设备为生产设备,强烈建议保留静态外部 IP 地址并将其分配给 {% data variables.product.prodname_ghe_server %} VM。 否则,重新启动后将不会保留 VM 的公共 IP 地址。 有关详细信息,请参阅 Google 指南“[保留静态外部 IP 地址](https://cloud.google.com/compute/docs/configure-instance-ip-addresses)”。 +If this is a production appliance, we strongly recommend reserving a static external IP address and assigning it to the {% data variables.product.prodname_ghe_server %} VM. Otherwise, the public IP address of the VM will not be retained after restarts. For more information, see the Google guide "[Reserving a Static External IP Address](https://cloud.google.com/compute/docs/configure-instance-ip-addresses)." -在生产高可用性配置中,主设备和副本设备均应获得单独的静态 IP 地址。 +In production High Availability configurations, both primary and replica appliances should be assigned separate static IP addresses. -## 创建 {% data variables.product.prodname_ghe_server %} 实例 +## Creating the {% data variables.product.prodname_ghe_server %} instance -要创建 {% data variables.product.prodname_ghe_server %} 实例,您需要使用 {% data variables.product.prodname_ghe_server %} 映像创建 GCE 实例并连接额外的存储卷来存储实例数据。 有关详细信息,请参阅“[硬件注意事项](#hardware-considerations)”。 +To create the {% data variables.product.prodname_ghe_server %} instance, you'll need to create a GCE instance with your {% data variables.product.prodname_ghe_server %} image and attach an additional storage volume for your instance data. For more information, see "[Hardware considerations](#hardware-considerations)." -1. 使用 gcloud compute 命令行工具,创建数据磁盘,将其用作您的实例数据的附加存储卷,并根据用户许可数配置大小。 有关详细信息,请参阅 Google 文档中的“[gcloud compute disks create](https://cloud.google.com/sdk/gcloud/reference/compute/disks/create)”。 +1. Using the gcloud compute command-line tool, create a data disk to use as an attached storage volume for your instance data, and configure the size based on your user license count. For more information, see "[gcloud compute disks create](https://cloud.google.com/sdk/gcloud/reference/compute/disks/create)" in the Google documentation. ```shell - $ gcloud compute disks create DATA-DISK-NAME --size DATA-DISK-SIZE --type DATA-DISK-TYPE --zone ZONE + $ gcloud compute disks create DATA-DISK-NAME --size DATA-DISK-SIZE --type DATA-DISK-TYPE --zone ZONE ``` -2. 然后,使用所选 {% data variables.product.prodname_ghe_server %} 映像的名称创建实例,并连接数据磁盘。 有关详细信息,请参阅 Google 文档中的“[gcloud compute instances create](https://cloud.google.com/sdk/gcloud/reference/compute/instances/create)”。 +2. Then create an instance using the name of the {% data variables.product.prodname_ghe_server %} image you selected, and attach the data disk. For more information, see "[gcloud compute instances create](https://cloud.google.com/sdk/gcloud/reference/compute/instances/create)" in the Google documentation. ```shell - $ gcloud compute instances create INSTANCE-NAME \ + $ gcloud compute instances create INSTANCE-NAME \ --machine-type n1-standard-8 \ - --image GITHUB-ENTERPRISE-IMAGE-NAME \ - --disk name=DATA-DISK-NAME \ + --image GITHUB-ENTERPRISE-IMAGE-NAME \ + --disk name=DATA-DISK-NAME \ --metadata serial-port-enable=1 \ - --zone ZONE \ - --network NETWORK-NAME \ + --zone ZONE \ + --network NETWORK-NAME \ --image-project github-enterprise-public ``` -## 配置实例 +## Configuring the instance -{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} {% data reusables.enterprise_installation.upload-a-license-file %} {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} 有关详细信息,请参阅“[配置 {% data variables.product.prodname_ghe_server %} 设备](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)”。 -{% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} +{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} +{% data reusables.enterprise_installation.upload-a-license-file %} +{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." +{% data reusables.enterprise_installation.instance-will-restart-automatically %} +{% data reusables.enterprise_installation.visit-your-instance %} -## 延伸阅读 +## Further reading -- [系统概述](/enterprise/admin/guides/installation/system-overview) {% ifversion ghes %} -- [关于升级到新版本](/admin/overview/about-upgrades-to-new-releases) {% endif %} +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md index 849e1785a1..3381721392 100644 --- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md +++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md @@ -1,6 +1,6 @@ --- -title: 在 OpenStack KVM 上安装 GitHub Enterprise Server -intro: '要在 OpenStack KVM 上安装 {% data variables.product.prodname_ghe_server %},您必须具有 OpenStack 访问权限并下载 {% data variables.product.prodname_ghe_server %} QCOW2 映像。' +title: Installing GitHub Enterprise Server on OpenStack KVM +intro: 'To install {% data variables.product.prodname_ghe_server %} on OpenStack KVM, you must have OpenStack access and download the {% data variables.product.prodname_ghe_server %} QCOW2 image.' redirect_from: - /enterprise/admin/guides/installation/installing-github-enterprise-on-openstack-kvm - /enterprise/admin/installation/installing-github-enterprise-server-on-openstack-kvm @@ -14,46 +14,44 @@ topics: - Infrastructure - Set up shortTitle: Install on OpenStack -ms.openlocfilehash: 105201d2759b333d297278aa7fe32a9544c68839 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147884953' --- -## 先决条件 +## Prerequisites - {% data reusables.enterprise_installation.software-license %} -- 您必须有权访问 OpenStack Horizon,即 OpenStack 服务基于 Web 的用户界面。 有关详细信息,请参阅 [Horizon 文档](https://docs.openstack.org/horizon/latest/)。 +- You must have access to an installation of OpenStack Horizon, the web-based user interface to OpenStack services. For more information, see the [Horizon documentation](https://docs.openstack.org/horizon/latest/). -## 硬件注意事项 +## Hardware considerations {% data reusables.enterprise_installation.hardware-considerations-all-platforms %} -## 下载 {% data variables.product.prodname_ghe_server %} 映像 +## Downloading the {% data variables.product.prodname_ghe_server %} image -{% data reusables.enterprise_installation.download-license %} {% data reusables.enterprise_installation.download-appliance %} -4. 在“{% data variables.product.prodname_dotcom %} 本地”下,选择“选择虚拟机监控程序”下拉菜单,然后单击“OpenStack KVM (QCOW2)”。 -5. 单击“下载 OpenStack KVM (QCOW2)”。 +{% data reusables.enterprise_installation.download-license %} +{% data reusables.enterprise_installation.download-appliance %} +4. Under "{% data variables.product.prodname_dotcom %} On-premises", select the "Select your hypervisor" dropdown menu and click **OpenStack KVM (QCOW2)**. +5. Click **Download for OpenStack KVM (QCOW2)**. -## 创建 {% data variables.product.prodname_ghe_server %} 实例 +## Creating the {% data variables.product.prodname_ghe_server %} instance {% data reusables.enterprise_installation.create-ghe-instance %} -1. 在 OpenStack Horizon 中,上传您下载的 {% data variables.product.prodname_ghe_server %} 映像。 有关说明,请参阅 OpenStack 指南“[上传和管理映像](https://docs.openstack.org/horizon/latest/user/manage-images.html)”的“上传映像”部分。 -{% data reusables.enterprise_installation.create-attached-storage-volume %} 有关说明,请参阅 OpenStack 指南“[创建和管理卷](https://docs.openstack.org/horizon/latest/user/manage-volumes.html)”。 -3. 创建安全组,并为下表中的各个端口添加新的安全组规则。 有关说明,请参阅 OpenStack 指南“[为实例配置访问和安全性](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html)” +1. In OpenStack Horizon, upload the {% data variables.product.prodname_ghe_server %} image you downloaded. For instructions, see the "Upload an image" section of the OpenStack guide "[Upload and manage images](https://docs.openstack.org/horizon/latest/user/manage-images.html)." +{% data reusables.enterprise_installation.create-attached-storage-volume %} For instructions, see the OpenStack guide "[Create and manage volumes](https://docs.openstack.org/horizon/latest/user/manage-volumes.html)." +3. Create a security group, and add a new security group rule for each port in the table below. For instructions, see the OpenStack guide "[Configure access and security for instances](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html)." {% data reusables.enterprise_installation.necessary_ports %} -4. 也可以将浮动 IP 关联到实例。 根据 OpenStack 设置,您可能需要将浮动 IP 分配给项目并将其关联到实例。 请联系您的系统管理员以确定您是否属于这种情况。 有关详细信息,请参阅 OpenStack 文档中的“[将浮动 IP 地址分配给实例](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html#allocate-a-floating-ip-address-to-an-instance)”。 -5. 使用在前几步创建的映像、数据卷和安全组启动 {% data variables.product.product_location %}。 有关说明,请参阅 OpenStack 指南“[启动和管理实例](https://docs.openstack.org/horizon/latest/user/launch-instances.html)”。 +4. Optionally, associate a floating IP to the instance. Depending on your OpenStack setup, you may need to allocate a floating IP to the project and associate it to the instance. Contact your system administrator to determine if this is the case for you. For more information, see "[Allocate a floating IP address to an instance](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html#allocate-a-floating-ip-address-to-an-instance)" in the OpenStack documentation. +5. Launch {% data variables.location.product_location %} using the image, data volume, and security group created in the previous steps. For instructions, see the OpenStack guide "[Launch and manage instances](https://docs.openstack.org/horizon/latest/user/launch-instances.html)." -## 配置 {% data variables.product.prodname_ghe_server %} 实例 +## Configuring the {% data variables.product.prodname_ghe_server %} instance -{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} {% data reusables.enterprise_installation.upload-a-license-file %} {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} 有关详细信息,请参阅“[配置 {% data variables.product.prodname_ghe_server %} 设备](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)”。 -{% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} +{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} +{% data reusables.enterprise_installation.upload-a-license-file %} +{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." +{% data reusables.enterprise_installation.instance-will-restart-automatically %} +{% data reusables.enterprise_installation.visit-your-instance %} -## 延伸阅读 +## Further reading -- [系统概述](/enterprise/admin/guides/installation/system-overview) {% ifversion ghes %} -- [关于升级到新版本](/admin/overview/about-upgrades-to-new-releases) {% endif %} +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md index 6ddc16c765..5c82bae468 100644 --- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md +++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md @@ -1,6 +1,6 @@ --- -title: 在 VMware 上安装 GitHub Enterprise Server -intro: '要在 VMWare 上安装 {% data variables.product.prodname_ghe_server %},您必须下载 VMWare vSphere 客户端,然后下载并部署 {% data variables.product.prodname_ghe_server %} 软件。' +title: Installing GitHub Enterprise Server on VMware +intro: 'To install {% data variables.product.prodname_ghe_server %} on VMware, you must download the VMware vSphere client, and then download and deploy the {% data variables.product.prodname_ghe_server %} software.' redirect_from: - /enterprise/admin/articles/getting-started-with-vmware - /enterprise/admin/articles/installing-vmware-tools @@ -17,44 +17,42 @@ topics: - Infrastructure - Set up shortTitle: Install on VMware -ms.openlocfilehash: f9e81c624f93c7478eed04b65b3ef43a69ef9291 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147859408' --- -## 先决条件 +## Prerequisites - {% data reusables.enterprise_installation.software-license %} -- 必须有一个 VMware vSphere ESXi 虚拟机监控程序,将其应用于将运行 {% data variables.product.product_location %}s 的裸机计算机。 我们支持适用于 {% data variables.product.prodname_ghe_server %} 3.4 及更早版本的版本 5.5 - 6.7。 {% data variables.product.prodname_ghe_server %} 3.5 及更高版本支持 ESX 版本 7.0。 ESXi Hypervisor 免费提供,不包含(可选)vCenter Server。 有关详细信息,请参阅 [VMware ESXi 文档](https://www.vmware.com/products/esxi-and-esx.html)。 -- 您将需要访问 vSphere Client。 如果您有 vCenter Server,可以使用 vSphere Web Client。 有关详细信息,请参阅 VMware 指南“[使用 vSphere Web Client 登录到 vCenter Server](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-CE128B59-E236-45FF-9976-D134DADC8178.html)”。 +- You must have a VMware vSphere ESXi Hypervisor, applied to a bare metal machine that will run {% data variables.location.product_location %}s. We support versions 5.5 through 6.7 for {% data variables.product.prodname_ghe_server %} 3.4 and earlier. ESX version 7.0 is supported for {% data variables.product.prodname_ghe_server %} 3.5 and later. The ESXi Hypervisor is free and does not include the (optional) vCenter Server. For more information, see [the VMware ESXi documentation](https://www.vmware.com/products/esxi-and-esx.html). +- You will need access to a vSphere Client. If you have vCenter Server you can use the vSphere Web Client. For more information, see the VMware guide "[Log in to vCenter Server by Using the vSphere Web Client](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-CE128B59-E236-45FF-9976-D134DADC8178.html)." -## 硬件注意事项 +## Hardware considerations {% data reusables.enterprise_installation.hardware-considerations-all-platforms %} -## 下载 {% data variables.product.prodname_ghe_server %} 映像 +## Downloading the {% data variables.product.prodname_ghe_server %} image -{% data reusables.enterprise_installation.download-license %} {% data reusables.enterprise_installation.download-appliance %} -4. 在“{% data variables.product.prodname_dotcom %} 本地”下,选择“选择虚拟机监控程序”下拉菜单,然后单击“VMware ESXi/vSphere (OVA)”。 -5. 单击“下载 VMware ESXi/vSphere(OVA)”。 +{% data reusables.enterprise_installation.download-license %} +{% data reusables.enterprise_installation.download-appliance %} +4. Under "{% data variables.product.prodname_dotcom %} On-premises", select the "Select your hypervisor" dropdown menu and click **VMware ESXi/vSphere (OVA)**. +5. Click **Download for VMware ESXi/vSphere (OVA)**. -## 创建 {% data variables.product.prodname_ghe_server %} 实例 +## Creating the {% data variables.product.prodname_ghe_server %} instance {% data reusables.enterprise_installation.create-ghe-instance %} -1. 使用 vSphere Windows Client 或 vCenter Web Client 导入您下载的 {% data variables.product.prodname_ghe_server %} 映像。 有关说明,请参阅 VMware 指南“[部署 OVF 或 OVA 模板](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-17BEDA21-43F6-41F4-8FB2-E01D275FE9B4.html)”。 - - 选择数据存储时,请选择空间足以容纳 VM 磁盘的数据存储。 有关针对实例大小建议的最小硬件规格,请参阅“[硬件注意事项](#hardware-considerations)”。 建议采用支持延迟归零的密集预配。 - - 取消选中“部署后启用”复选框,因为需要在预配 VM 后为存储库数据添加一个附加的存储卷。 -{% data reusables.enterprise_installation.create-attached-storage-volume %} 有关说明,请参阅 VMware 指南“[将新硬盘添加到虚拟机](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-F4917C61-3D24-4DB9-B347-B5722A84368C.html)”。 +1. Using the vSphere Windows Client or the vCenter Web Client, import the {% data variables.product.prodname_ghe_server %} image you downloaded. For instructions, see the VMware guide "[Deploy an OVF or OVA Template](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-17BEDA21-43F6-41F4-8FB2-E01D275FE9B4.html)." + - When selecting a datastore, choose one with sufficient space to host the VM's disks. For the minimum hardware specifications recommended for your instance size, see "[Hardware considerations](#hardware-considerations)." We recommend thick provisioning with lazy zeroing. + - Leave the **Power on after deployment** box unchecked, as you will need to add an attached storage volume for your repository data after provisioning the VM. +{% data reusables.enterprise_installation.create-attached-storage-volume %} For instructions, see the VMware guide "[Add a New Hard Disk to a Virtual Machine](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-F4917C61-3D24-4DB9-B347-B5722A84368C.html)." -## 配置 {% data variables.product.prodname_ghe_server %} 实例 +## Configuring the {% data variables.product.prodname_ghe_server %} instance -{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} {% data reusables.enterprise_installation.upload-a-license-file %} {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} 有关详细信息,请参阅“[配置 {% data variables.product.prodname_ghe_server %} 设备](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)”。 -{% data reusables.enterprise_installation.instance-will-restart-automatically %} {% data reusables.enterprise_installation.visit-your-instance %} +{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %} +{% data reusables.enterprise_installation.upload-a-license-file %} +{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)." +{% data reusables.enterprise_installation.instance-will-restart-automatically %} +{% data reusables.enterprise_installation.visit-your-instance %} -## 延伸阅读 +## Further reading -- [系统概述](/enterprise/admin/guides/installation/system-overview) {% ifversion ghes %} -- [关于升级到新版本](/admin/overview/about-upgrades-to-new-releases) {% endif %} +- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %} +- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %} diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md index 9445e64621..ecfcde73e0 100644 --- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md +++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md @@ -17,7 +17,7 @@ miniTocMaxHeadingLevel: 3 ## About staging instances -{% data variables.product.company_short %} recommends that you set up a separate environment to test backups, updates, or changes to the configuration for {% data variables.product.product_location %}. This environment, which you should isolate from your production systems, is called a staging environment. +{% data variables.product.company_short %} recommends that you set up a separate environment to test backups, updates, or changes to the configuration for {% data variables.location.product_location %}. This environment, which you should isolate from your production systems, is called a staging environment. For example, to protect against loss of data, you can regularly validate the backup of your production instance. You can regularly restore the backup of your production data to a separate {% data variables.product.product_name %} instance in a staging environment. On this staging instance, you could also test the upgrade to the latest feature release of {% data variables.product.product_name %}. @@ -136,7 +136,7 @@ To access the staging instance using the same hostname, update your local hosts {% note %} -**Note**: Your staging instance must be accessible from the same hostname as your production instance. Changing the hostname for {% data variables.product.product_location %} is not supported. For more information, see "[Configuring a hostname](/admin/configuration/configuring-network-settings/configuring-a-hostname)." +**Note**: Your staging instance must be accessible from the same hostname as your production instance. Changing the hostname for {% data variables.location.product_location %} is not supported. For more information, see "[Configuring a hostname](/admin/configuration/configuring-network-settings/configuring-a-hostname)." {% endnote %} diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md index b9b9aa6bc2..8dca96d496 100644 --- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md +++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md @@ -1,6 +1,6 @@ --- -title: 关于服务器统计信息 -intro: '你可以使用 {% data variables.product.prodname_server_statistics %} 分析 {% data variables.product.prodname_ghe_server %} 中你自己的聚合数据,并帮助我们改进 {% data variables.product.company_short %} 产品。' +title: About Server Statistics +intro: 'You can use {% data variables.product.prodname_server_statistics %} to analyze your own aggregate data from {% data variables.product.prodname_ghe_server %}, and help us improve {% data variables.product.company_short %} products.' versions: feature: server-statistics permissions: 'Enterprise owners can enable {% data variables.product.prodname_server_statistics %}.' @@ -8,54 +8,49 @@ redirect_from: - /early-access/github/analyze-how-your-team-works-with-server-statistics/about-server-statistics topics: - Enterprise -ms.openlocfilehash: c71cab38c096d5984a5136147b6dbc75e794c173 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147409321' --- -## 关于 {% data variables.product.prodname_server_statistics %} 的优势 -{% data variables.product.prodname_server_statistics %} 可以帮助你预测组织的需求,了解团队的工作方式,并显示从 {% data variables.product.prodname_ghe_server %} 获取的值。 +## About the benefits of {% data variables.product.prodname_server_statistics %} -启用后,{% data variables.product.prodname_server_statistics %} 会收集有关随时间推移在实例上使用多少特定功能的聚合数据。 与其他仅返回前一天的数据的[管理员统计信息 API](/rest/reference/enterprise-admin#admin-stats) 终结点不同,{% data variables.product.prodname_server_statistics %} 可提供自启用该功能以来收集的所有 {% data variables.product.prodname_server_statistics %} 指标的历史数据。 有关详细信息,请参阅“[为企业启用 {% data variables.product.prodname_server_statistics %}](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)”。 +{% data variables.product.prodname_server_statistics %} can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. -启用 {% data variables.product.prodname_server_statistics %} 时,你将帮助构建更好的 {% data variables.product.prodname_dotcom %}。 你将提供的聚合数据让我们能够深入了解 {% data variables.product.prodname_dotcom %} 如何为我们的客户增加价值。 此信息使 {% data variables.product.company_short %} 能够做出更好、更明智的产品决策,最终使你受益。 +Once enabled, {% data variables.product.prodname_server_statistics %} collects aggregate data on how much certain features are used on your instance over time. Unlike other [Admin Stats API](/rest/reference/enterprise-admin#admin-stats) endpoints, which only return data for the last day, {% data variables.product.prodname_server_statistics %} provides historical data of all {% data variables.product.prodname_server_statistics %} metrics collected since the day you enabled the feature. For more information, see "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." -## 关于数据安全性 +When you enable {% data variables.product.prodname_server_statistics %}, you're helping to build a better {% data variables.product.prodname_dotcom %}. The aggregated data you'll provide gives us insights into how {% data variables.product.prodname_dotcom %} adds value to our customers. This information allows {% data variables.product.company_short %} to make better and more informed product decisions, ultimately benefiting you. -我们尊重你的数据。 除非你先授予我们权限,否则我们永远不会从 {% data variables.product.product_location %} 传输数据。 +## About data security -我们不会收集任何个人数据。 我们也不会收集任何 {% data variables.product.company_short %} 内容,例如代码、问题、评论或拉取请求内容。 +We respect your data. We will never transmit data from {% data variables.location.product_location %} unless you have first given us permission to do so. -只有 {% data variables.product.prodname_ghe_cloud %} 上连接的企业帐户或组织的所有者才能访问数据。 +We collect no personal data. We also don't collect any {% data variables.product.company_short %} content, such as code, issues, comments, or pull request content. -我们仅在存储库、问题、拉取请求和其他功能上收集某些聚合指标。 有关收集的聚合指标列表,请参阅“[收集的 {% data variables.product.prodname_server_statistics %} 数据](#server-statistics-data-collected)”。 +Only owners of the connected enterprise account or organization on {% data variables.product.prodname_ghe_cloud %} can access the data. -我们可能会在 {% data variables.product.prodname_ghe_server %} 的未来功能版本中更新收集的指标,届时将在 [{% data variables.product.prodname_ghe_server %} 发行说明](/admin/release-notes)中进行介绍。 此外,我们会将所有指标更新都更新到本文中。 +Only certain aggregate metrics are collected on repositories, issues, pull requests, and other features. To see the list of aggregate metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](#server-statistics-data-collected)." -若要更好地了解如何存储和保护 {% data variables.product.prodname_server_statistics %} 数据,请参阅“[GitHub 安全性](https://github.com/security)”。 +Any updates to the collected metrics will happen in future feature releases of {% data variables.product.prodname_ghe_server %} and will be described in the [{% data variables.product.prodname_ghe_server %} release notes](/admin/release-notes). In addition, we will update this article with all metric updates. -### 关于数据保留和删除 +For a better understanding of how we store and secure {% data variables.product.prodname_server_statistics %} data, see "[GitHub Security](https://github.com/security)." -只要 {% data variables.product.prodname_ghe_server %} 许可证处于活动状态,并且启用了 {% data variables.product.prodname_server_statistics %} 功能,{% data variables.product.company_short %} 就会收集 {% data variables.product.prodname_server_statistics %} 数据。 +### About data retention and deletion -如果要删除数据,可以联系 GitHub 支持、{% data variables.product.prodname_dotcom %} 客户代表或客户成功经理。 通常,我们在隐私声明中指定的时间范围内删除数据。 有关详细信息,请参阅 {% data variables.product.prodname_dotcom_the_website %} 文档中的 [{% data variables.product.company_short %} 隐私声明](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#data-retention-and-deletion-of-data)。 +{% data variables.product.company_short %} collects {% data variables.product.prodname_server_statistics %} data for as long as your {% data variables.product.prodname_ghe_server %} license is active and the {% data variables.product.prodname_server_statistics %} feature is enabled. -### 关于数据可移植性 +If you would like to delete your data, you may do so by contacting GitHub Support, your {% data variables.product.prodname_dotcom %} account representative, or your Customer Success Manager. Generally, we delete data in the timeframe specified in our privacy statement. For more information, see [{% data variables.product.company_short %}'s privacy statement](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#data-retention-and-deletion-of-data) in the {% data variables.product.prodname_dotcom_the_website %} documentation. -作为 {% data variables.product.prodname_ghe_cloud %} 上的组织所有者或企业所有者,你可以通过导出 CSV 或 JSON 文件中的数据或通过 {% data variables.product.prodname_server_statistics %} REST API 来访问 {% data variables.product.prodname_server_statistics %} 数据。 有关详细信息,请参阅“[使用 REST API 请求 {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)”或“[导出 {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics)”。 +### About data portability -## 关于禁用数据收集 +As an organization owner or enterprise owner on {% data variables.product.prodname_ghe_cloud %}, you can access {% data variables.product.prodname_server_statistics %} data by exporting the data in a CSV or JSON file or through the {% data variables.product.prodname_server_statistics %} REST API. For more information, see "[Requesting {% data variables.product.prodname_server_statistics %} using the REST API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)" or "[Exporting {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics)." -可以随时禁用 {% data variables.product.prodname_server_statistics %} 功能。 有关详细信息,请参阅“[为企业启用 {% data variables.product.prodname_server_statistics %}](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)”。 +## About disabling data collection -## 收集的 {% data variables.product.prodname_server_statistics %} 数据 +You can disable the {% data variables.product.prodname_server_statistics %} feature at any time. For more information, see "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." -启用 {% data variables.product.prodname_server_statistics %} 后,将通过在 {% data variables.product.product_location %} 上运行的每日作业收集指标。 聚合指标存储在 {% data variables.product.prodname_ghe_cloud %} 上的组织或企业帐户上,不会存储在 {% data variables.product.product_location %} 上。 +## {% data variables.product.prodname_server_statistics %} data collected -将每天收集和传输以下聚合指标,并显示当天的总计数: +After you enable {% data variables.product.prodname_server_statistics %}, metrics are collected through a daily job that runs on {% data variables.location.product_location %}. The aggregate metrics are stored on your organization or enterprise account on {% data variables.product.prodname_ghe_cloud %} and are not stored on {% data variables.location.product_location %}. + +The following aggregate metrics will be collected and transmitted on a daily basis and represent the total counts for the day: - `active_hooks` - `admin_users` - `closed_issues` @@ -98,8 +93,8 @@ ms.locfileid: '147409321' - `total_wikis` - `unmergeable_pulls` -## {% data variables.product.prodname_server_statistics %} 有效负载示例 +## {% data variables.product.prodname_server_statistics %} payload example -若要查看 {% data variables.product.prodname_server_statistics %} API 的响应有效负载示例,请参阅“[使用 REST API 请求 {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)”。 +To see an example of the response payload for the {% data variables.product.prodname_server_statistics %} API, see "[Requesting {% data variables.product.prodname_server_statistics %} using the REST API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)." -有关收集的数据列表,请参阅“[收集的 {% data variables.product.prodname_server_statistics %} 数据](#server-statistics-data-collected)”。 +To see a list of the data collected, see "[{% data variables.product.prodname_server_statistics %} data collected](#server-statistics-data-collected)." diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md index 4e01f32d9c..7c27d61f40 100644 --- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md +++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md @@ -1,52 +1,47 @@ --- -title: 导出服务器统计信息 +title: Exporting Server Statistics shortTitle: Export Server Statistics -intro: '可以通过下载 CSV 或 JSON 文件形式的 {% data variables.product.prodname_server_statistics %} 指标来分析 {% data variables.product.prodname_ghe_server %} 使用情况。' +intro: 'You can use your own tools to analyze your {% data variables.product.prodname_ghe_server %} usage over time by downloading your {% data variables.product.prodname_server_statistics %} metrics in a CSV or JSON file.' versions: feature: server-statistics redirect_from: - /early-access/github/analyze-how-your-team-works-with-server-statistics/exploring-server-statistics -ms.openlocfilehash: 4e8fa1d040303ec569d11a8a41708ede10b3e76e -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147718163' --- -最多可以在 CSV 或 JSON 文件中下载过去 365 天的 {% data variables.product.prodname_server_statistics %} 数据。 此数据包括存储库、问题和拉取请求的聚合指标,可帮助你预测组织的需求、了解团队的工作方式,以及显示从 {% data variables.product.prodname_ghe_server %} 获取的值。 -必须先启用 {% data variables.product.prodname_server_statistics %} 才能下载此数据。 有关详细信息,请参阅“[为企业启用 {% data variables.product.prodname_server_statistics %}](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)”。 +You can download up to the last 365 days of {% data variables.product.prodname_server_statistics %} data in a CSV or JSON file. This data, which includes aggregate metrics on repositories, issues, and pull requests, can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. -若要预览可供下载的指标,请参阅“[关于 {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)”。 +Before you can download this data, you must enable {% data variables.product.prodname_server_statistics %}. For more information, see "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." -若要下载这些指标,你必须是 {% data variables.product.prodname_ghe_cloud %} 的企业所有者或组织所有者。 - - 如果 {% data variables.product.product_location %} 连接到了 {% data variables.product.prodname_ghe_cloud %} 上的企业帐户,请参阅“[从企业帐户下载指标](#downloading-metrics-from-your-enterprise-account)”。 - - 如果 {% data variables.product.product_location %} 连接到了 {% data variables.product.prodname_ghe_cloud %} 上的组织,请参阅“[从组织下载指标](#downloading-metrics-from-your-organization)”。 +To preview the metrics available to download, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)." -若要了解有关 {% data variables.product.prodname_github_connect %} 的详细信息,请参阅“[关于 {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)”。 +To download these metrics, you must be an enterprise owner or organization owner on {% data variables.product.prodname_ghe_cloud %}. + - If {% data variables.location.product_location %} is connected to an enterprise account on {% data variables.product.prodname_ghe_cloud %}, see "[Downloading metrics from your enterprise account](#downloading-metrics-from-your-enterprise-account)." + - If {% data variables.location.product_location %} is connected to an organization on {% data variables.product.prodname_ghe_cloud %}, see "[Downloading metrics from your organization](#downloading-metrics-from-your-organization)." -## 从企业帐户下载指标 +To learn more about {% data variables.product.prodname_github_connect %}, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)." -1. 在 {% data variables.product.prodname_ghe_cloud %} 的右上角,单击你的配置文件照片,然后单击“你的企业”。 - ![包含“你的企业”选项的下拉菜单](/assets/images/help/enterprises/enterprise-admin-account-settings.png) +## Downloading metrics from your enterprise account -2. 在所需的企业帐户旁边,单击“设置”。 - ![企业管理员帐户旁边的“设置”按钮](/assets/images/help/enterprises/enterprise-admin-account-settings-button.png) +1. In the top-right corner of {% data variables.product.prodname_ghe_cloud %}, click your profile photo, then click **Your enterprises**. + ![Drop down menu with "Your enterprises" option](/assets/images/help/enterprises/enterprise-admin-account-settings.png) -3. 在左侧,单击“GitHub Connect”。 - ![企业管理员帐户下的“GitHub Connect”选项](/assets/images//help/enterprises/enterprise-admin-github-connect.png) +2. Next to your desired enterprise account, click **Settings**. + ![Settings button next to Enterprise admin account](/assets/images/help/enterprises/enterprise-admin-account-settings-button.png) + +3. On the left, click **GitHub Connect**. + ![GitHub Connect option under enterprise admin account](/assets/images//help/enterprises/enterprise-admin-github-connect.png) {% data reusables.server-statistics.csv-download %} -## 从组织下载指标 +## Downloading metrics from your organization -1. 在 {% data variables.product.prodname_ghe_cloud %} 的右上角,单击你的配置文件照片,然后单击“你的组织”。 - ![包含“你的组织”选项的下拉菜单](/assets/images/help/enterprises/github-enterprise-cloud-organizations.png) +1. In the top-right corner of {% data variables.product.prodname_ghe_cloud %}, click your profile photo, then click **Your organizations**. + ![Drop down menu with "Your organizations" option](/assets/images/help/enterprises/github-enterprise-cloud-organizations.png) -2. 在组织列表中,在连接到 {% data variables.product.product_location %} 的组织旁边,单击“设置”。 - ![{% data variables.product.prodname_ghe_cloud %} 组织旁边的“设置”按钮](/assets/images/help/enterprises/settings-for-ghec-org.png) +2. In the list of organizations, next to the organization that's connected to {% data variables.location.product_location %}, click **Settings**. + ![Settings button next to {% data variables.product.prodname_ghe_cloud %} organization](/assets/images/help/enterprises/settings-for-ghec-org.png) -3. 在左侧,单击“GitHub Connect”。 - ![组织帐户设置左侧栏中的“GitHub Connect”选项](/assets/images/help/enterprises/github-connect-option-for-ghec-org.png) +3. On the left, click **GitHub Connect**. + ![GitHub Connect option in an organization account settings left sidebar](/assets/images/help/enterprises/github-connect-option-for-ghec-org.png) {% data reusables.server-statistics.csv-download %} diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md index c628a95757..b52e938922 100644 --- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md +++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md @@ -1,7 +1,7 @@ --- -title: 管理全局 web 挂钩 +title: Managing global webhooks shortTitle: Manage global webhooks -intro: 您可以配置全局 web 挂钩,以便在企业内部发生事件时通知外部 Web 服务器。 +intro: You can configure global webhooks to notify external web servers when events occur within your enterprise. permissions: Enterprise owners can manage global webhooks for an enterprise account. redirect_from: - /enterprise/admin/user-management/about-global-webhooks @@ -22,72 +22,79 @@ type: how_to topics: - Enterprise - Webhooks -ms.openlocfilehash: 751a6dc55b9d1aded22a8225f4bf7d058aa32b77 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145099948' --- -## 关于全局 web 挂钩 -当企业内部发生事件时,您可以使用全局 web 挂钩通知外部 Web 服务器。 您可以将服务器配置为接收 web 挂钩的有效负载,然后运行监控、响应或实施企业用户和组织管理规则的应用程序或代码。 有关详细信息,请参阅“[Webhook](/developers/webhooks-and-events/webhooks)”。 +## About global webhooks -例如,您可以将 {% data variables.product.product_location %} 配置为在有人创建、删除或修改企业内的存储库或组织时发送 web 挂钩。 您可以将服务器配置为在收到 web 挂钩后自动执行任务。 +You can use global webhooks to notify an external web server when events occur within your enterprise. You can configure the server to receive the webhook's payload, then run an application or code that monitors, responds to, or enforces rules for user and organization management for your enterprise. For more information, see "[Webhooks](/developers/webhooks-and-events/webhooks)." -![全局 web 挂钩列表](/assets/images/enterprise/site-admin-settings/list-of-global-webhooks.png) +For example, you can configure {% data variables.location.product_location %} to send a webhook when someone creates, deletes, or modifies a repository or organization within your enterprise. You can configure the server to automatically perform a task after receiving the webhook. + +![List of global webhooks](/assets/images/enterprise/site-admin-settings/list-of-global-webhooks.png) {% data reusables.enterprise_user_management.manage-global-webhooks-api %} -## 添加全局 web 挂钩 +## Adding a global webhook -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.hooks-tab %} -5. 单击“添加 Webhook” 。 - ![管理中心内“Webhook”页面上的“添加 Webhook”按钮](/assets/images/enterprise/site-admin-settings/add-global-webhook-button.png) -6. 输入您想要接收有效负载的 URL。 - ![用于键入有效负载 URL 的字段](/assets/images/enterprise/site-admin-settings/add-global-webhook-payload-url.png) -7. (可选)使用“内容类型”下拉菜单,并单击一个有效负载格式。 - ![列出内容类型选项的下拉菜单](/assets/images/enterprise/site-admin-settings/add-global-webhook-content-type-dropdown.png) -8. (可选)在“机密”字段中,键入用作 `secret` 密钥的字符串。 - ![用于键入用作密钥的字符串的字段](/assets/images/enterprise/site-admin-settings/add-global-webhook-secret.png) -9. (可选)如果有效负载 URL 为 HTTPS,并且你不希望 {% data variables.product.prodname_ghe_server %} 在传递有效负载时验证 SSL 证书,请选择“禁用 SSL 验证”。 阅读 SSL 验证的信息,然后单击“我已了解我的 Webhook 可能不安全”。 - ![用于禁用 SSL 验证的复选框](/assets/images/enterprise/site-admin-settings/add-global-webhook-disable-ssl-button.png) +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +5. Click **Add webhook**. + ![Add webhook button on Webhooks page in Admin center](/assets/images/enterprise/site-admin-settings/add-global-webhook-button.png) +6. Type the URL where you'd like to receive payloads. + ![Field to type a payload URL](/assets/images/enterprise/site-admin-settings/add-global-webhook-payload-url.png) +7. Optionally, use the **Content type** drop-down menu, and click a payload format. + ![Drop-down menu listing content type options](/assets/images/enterprise/site-admin-settings/add-global-webhook-content-type-dropdown.png) +8. Optionally, in the **Secret** field, type a string to use as a `secret` key. + ![Field to type a string to use as a secret key](/assets/images/enterprise/site-admin-settings/add-global-webhook-secret.png) +9. Optionally, if your payload URL is HTTPS and you would not like {% data variables.product.prodname_ghe_server %} to verify SSL certificates when delivering payloads, select **Disable SSL verification**. Read the information about SSL verification, then click **I understand my webhooks may not be secure**. + ![Checkbox for disabling SSL verification](/assets/images/enterprise/site-admin-settings/add-global-webhook-disable-ssl-button.png) {% warning %} - 警告:SSL 验证有助于确保安全传递挂钩有效负载。 我们不建议禁用 SSL 验证。 + **Warning:** SSL verification helps ensure that hook payloads are delivered securely. We do not recommend disabling SSL verification. {% endwarning %} -10. 确定您希望此 web 挂钩对每个事件还是选定事件触发。 - ![包含用于为每个事件或选定事件接收有效负载的选项的单选按钮](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-events.png) - - 对于每个事件,请选择“向我发送所有内容”。 - - 要选择特定事件,请选择“让我选择单个事件”。 -11. 如果选择单个事件,请选择将触发 web 挂钩的事件。 - {% ifversion ghec %} ![单个全局 Webhook 事件的复选框](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events.png) {% elsif ghes or ghae %} ![单个全局 Webhook 事件的复选框](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events-ghes-and-ae.png) {% endif %} -12. 确认选中了“活动”复选框。 - ![已选择的“活动”复选框](/assets/images/help/business-accounts/webhook-active.png) -13. 单击“添加 Webhook” 。 +10. Decide if you'd like this webhook to trigger for every event or for selected events. + ![Radio buttons with options to receive payloads for every event or selected events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-events.png) + - For every event, select **Send me everything**. + - To choose specific events, select **Let me select individual events**. +11. If you chose to select individual events, select the events that will trigger the webhook. + {% ifversion ghec %} + ![Checkboxes for individual global webhook events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events.png) + {% elsif ghes or ghae %} + ![Checkboxes for individual global webhook events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events-ghes-and-ae.png) + {% endif %} +12. Confirm that the **Active** checkbox is selected. + ![Selected Active checkbox](/assets/images/help/business-accounts/webhook-active.png) +13. Click **Add webhook**. -## 编辑全局 web 挂钩 +## Editing a global webhook -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.hooks-tab %} -5. 在想要编辑的 Webhook 旁,单击“编辑”。 - ![Webhook 旁的“编辑”按钮](/assets/images/enterprise/site-admin-settings/edit-global-webhook-button.png) -6. 更新 web 挂钩的设置。 -7. 单击“更新 Webhook”。 +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +5. Next to the webhook you'd like to edit, click **Edit**. + ![Edit button next to a webhook](/assets/images/enterprise/site-admin-settings/edit-global-webhook-button.png) +6. Update the webhook's settings. +7. Click **Update webhook**. -## 删除全局 web 挂钩 +## Deleting a global webhook -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.hooks-tab %} -5. 在想要删除的 Webhook 旁,单击“删除”。 - ![Webhook 旁的“删除”按钮](/assets/images/enterprise/site-admin-settings/delete-global-webhook-button.png) -6. 阅读有关删除 Webhook 的信息,然后单击“是,删除 Webhook”。 - ![包含警告信息的弹出框和用于确认删除 Webhook 的按钮](/assets/images/enterprise/site-admin-settings/confirm-delete-global-webhook.png) +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +5. Next to the webhook you'd like to delete, click **Delete**. + ![Delete button next to a webhook](/assets/images/enterprise/site-admin-settings/delete-global-webhook-button.png) +6. Read the information about deleting a webhook, then click **Yes, delete webhook**. + ![Pop-up box with warning information and button to confirm deleting the webhook](/assets/images/enterprise/site-admin-settings/confirm-delete-global-webhook.png) -## 查看最近的交付和回复 +## Viewing recent deliveries and responses -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.hooks-tab %} -5. 在 web 挂钩列表中,单击您想要查看其投递的 web 挂钩。 - ![包含用于查看每个 Webhook 的链接的 Webhook 列表](/assets/images/enterprise/site-admin-settings/click-global-webhook.png) -6. 在“Recent deliveries”下,单击投递以查看详细信息。 - ![包含用于查看详细信息的链接的 Webhook 最近交付列表](/assets/images/enterprise/site-admin-settings/global-webhooks-recent-deliveries.png) +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.hooks-tab %} +5. In the list of webhooks, click the webhook for which you'd like to see deliveries. + ![List of webhooks with links to view each webhook](/assets/images/enterprise/site-admin-settings/click-global-webhook.png) +6. Under "Recent deliveries", click a delivery to view details. + ![List of the webhook's recent deliveries with links to view details](/assets/images/enterprise/site-admin-settings/global-webhooks-recent-deliveries.png) diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md index 2da60940c7..863a314cec 100644 --- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md @@ -28,7 +28,7 @@ topics: The scope of the events that appear in your enterprise's audit log depend on whether your enterprise uses {% data variables.product.prodname_emus %}. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)." - If your enterprise does not use {% data variables.product.prodname_emus %}, the audit log only includes events related to the enterprise account and the organizations within the enterprise account, which are listed in this article. -- If your enterprise uses {% data variables.product.prodname_emus %}, the audit log also includes user events for {% data variables.product.prodname_managed_users %}, such as each time the user logs in to {% data variables.product.product_name %}. For a list of these events, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log#security-log-actions)." +- If your enterprise uses {% data variables.product.prodname_emus %}, the audit log also includes user events for {% data variables.enterprise.prodname_managed_users %}, such as each time the user logs in to {% data variables.product.product_name %}. For a list of these events, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log#security-log-actions)." {% endif %} {%- ifversion fpt or ghec %} @@ -159,6 +159,32 @@ The scope of the events that appear in your enterprise's audit log depend on whe | `business.update_saml_provider_settings` | The SAML single sign-on provider settings for an enterprise were updated. {%- endif %} +{% ifversion code-security-audit-log-events %} + +## `business_advanced_security` category actions + +| Action | Description +|--------|------------- +| `business_advanced_security.disabled` | {% data variables.product.prodname_GH_advanced_security %} was disabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_advanced_security.enabled` | {% data variables.product.prodname_GH_advanced_security %} was enabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_advanced_security.disabled_for_new_repos` | {% data variables.product.prodname_GH_advanced_security %} was disabled for new repositories in your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_advanced_security.enabled_for_new_repos` | {% data variables.product.prodname_GH_advanced_security %} was enabled for new repositories in your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." + +{% endif %} + +{% ifversion code-security-audit-log-events %} + +## `business_secret_scanning` category actions + +| Action | Description +|--------|------------- +| `business_secret_scanning.disable` | {% data variables.product.prodname_secret_scanning_caps %} was disabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_secret_scanning.enable` | {% data variables.product.prodname_secret_scanning_caps %} was enabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_secret_scanning.disabled_for_new_repos` | {% data variables.product.prodname_secret_scanning_caps %} was disabled for new repositories in your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_secret_scanning.enabled_for_new_repos` | {% data variables.product.prodname_secret_scanning_caps %} was enabled for new repositories in your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." + +{% endif %} + {%- ifversion secret-scanning-audit-log-custom-patterns %} ## `business_secret_scanning_custom_pattern` category actions @@ -169,6 +195,31 @@ Action | Description | `business_secret_scanning_custom_pattern.update` | Changes to an enterprise-level custom pattern are saved for secret scanning. {%- endif %} +{% ifversion code-security-audit-log-events %} + +## `business_secret_scanning_push_protection` category actions + +| Action | Description +|--------|------------- +| `business_secret_scanning_push_protection.disable` | Push protection for {% data variables.product.prodname_secret_scanning %} was disabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_secret_scanning_push_protection.enable` | Push protection for {% data variables.product.prodname_secret_scanning %} was enabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_secret_scanning_push_protection.disabled_for_new_repos` | Push protection for {% data variables.product.prodname_secret_scanning %} was disabled for new repositories in your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_secret_scanning_push_protection.enabled_for_new_repos` | Push protection for {% data variables.product.prodname_secret_scanning %} was enabled for new repositories in your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." + +{% endif %} + +{% ifversion code-security-audit-log-events %} + +## `business_secret_scanning_push_protection_custom_message` category actions + +| Action | Description +|--------|------------- +| `business_secret_scanning_push_protection_custom_message.disable` | The custom message triggered by an attempted push to a push-protected repository was disabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_secret_scanning_push_protection_custom_message.enable` | The custom message triggered by an attempted push to a push-protected repository was enabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_secret_scanning_push_protection_custom_message.update` | The custom message triggered by an attempted push to a push-protected repository was updated for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." + +{% endif %} + ## `checks` category actions | Action | Description @@ -436,7 +487,7 @@ Before you'll see `git` category actions, you must enable Git events in the audi | `integration.revoke_all_tokens` | All user tokens for an integration were requested to be revoked. | `integration.revoke_tokens` | Token(s) for an integration were revoked. -## `integration_installation`category actions +## `integration_installation` category actions | Action | Description |--------|------------- @@ -573,7 +624,7 @@ Before you'll see `git` category actions, you must enable Git events in the audi | Action | Description |--------|------------- -`oauth_access.create` | An [OAuth access token][] was generated for a user account. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." +`oauth_access.create` | An [OAuth access token][] was generated for a user account. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." `oauth_access.destroy` | An [OAuth access token][] was deleted from a user account. [OAuth access token]: /developers/apps/building-oauth-apps/authorizing-oauth-apps @@ -717,6 +768,11 @@ Before you'll see `git` category actions, you must enable Git events in the audi {%- ifversion fpt or ghec %} | `org.runner_group_visiblity_updated` | The visibility of a self-hosted runner group was updated via the REST API. For more information, see "[Update a self-hosted runner group for an organization](/rest/reference/actions#update-a-self-hosted-runner-group-for-an-organization)." {%- endif %} +{%- ifversion code-security-audit-log-events %} +| `org.secret_scanning_push_protection_custom_message_disabled` | The custom message triggered by an attempted push to a push-protected repository was disabled for your organization. For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#enabling-secret-scanning-as-a-push-protection-for-an-organization)." +| `org.secret_scanning_push_protection_custom_message_enabled` | The custom message triggered by an attempted push to a push-protected repository was enabled for your organization. For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#enabling-secret-scanning-as-a-push-protection-for-an-organization)." +| `org.secret_scanning_push_protection_custom_message_updated` | The custom message triggered by an attempted push to a push-protected repository was updated for your organization. For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#enabling-secret-scanning-as-a-push-protection-for-an-organization)." +{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `org.secret_scanning_push_protection_disable` | An organization owner or administrator disabled push protection for secret scanning. For more information, see "[Protecting pushes with secret scanning](/enterprise-cloud@latest/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." | `org.secret_scanning_push_protection_enable` | An organization owner or administrator enabled push protection for secret scanning. diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md index 925ac5e922..0bcdaf5744 100644 --- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md @@ -1,8 +1,8 @@ --- -title: 为企业配置审核日志 -intro: 可以为企业的审核日志配置设置。 +title: Configuring the audit log for your enterprise +intro: "You can configure settings for your enterprise's audit log." shortTitle: Configure audit logs -permissions: Enterprise owners can configure the audit log. +permissions: 'Enterprise owners can configure the audit log.' versions: feature: audit-data-retention-tab type: how_to @@ -10,45 +10,47 @@ topics: - Auditing - Enterprise - Logging -ms.openlocfilehash: 79bf5f2ae2f1b2762ea32a6bef85b04e9cf95739 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147424861' --- -## 关于审核日志配置 -可以为审核日志数据配置保留期,并查看索引存储详细信息。 +## About audit log configuration -{% ifversion enable-git-events %}配置保留期后,可以启用或禁用与 Git 相关的事件出现在在审核日志中。 -{% endif %} - -## 为审核日志数据配置保留期 - -可以为 {% data variables.product.product_location %} 的审核日志数据配置保留期。 超过配置期限的数据将从磁盘中永久移除。 - -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} {% data reusables.audit_log.audit-data-retention-tab %} -1. 在“配置审核日志保留期设置”下,选择下拉菜单并选择一个保留期。 - - ![审核日志保留期设置下拉菜单的屏幕截图](/assets/images/help/enterprises/audit-log-retention-dropdown.png) -1. 单击“ **保存**”。 +You can configure a retention period for audit log data and see index storage details. {% ifversion enable-git-events %} -## 管理审核日志中的 Git 事件 +After you configure a retention period, you can enable or disable Git-related events from appearing in the audit log. +{% endif %} -可以启用或禁用与 Git 相关的事件(例如 `git.clone` 和 `git.push`)出现在审核日志中。 有关记录的 Git 事件列表,请参阅“[企业的审核日志事件](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)”。 +## Configuring a retention period for audit log data -如果确实启用了 Git 事件,由于记录了大量的 Git 事件,我们建议监视实例的文件存储并查看相关的警报配置。 有关详细信息,请参阅“[监视存储](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)”。 +You can configure a retention period for audit log data for {% data variables.location.product_location %}. Data that exceeds the period you configure will be permanently removed from disk. -在审核日志中启用 Git 事件之前,必须为审核日志数据配置保留期,而不是“无限制”。 有关详细信息,请参阅“[为审核日志数据配置保留期](#configuring-a-retention-period-for-audit-log-data)”。 +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.audit-log-tab %} +{% data reusables.audit_log.audit-data-retention-tab %} +1. Under "Configure audit log retention settings", select the dropdown menu and click a retention period. + + ![Screenshot of the dropdown menu for audit log retention settings](/assets/images/help/enterprises/audit-log-retention-dropdown.png) +1. Click **Save**. + +{% ifversion enable-git-events %} +## Managing Git events in the audit log + +You can enable or disable Git-related events, such as `git.clone` and `git.push`, from appearing in your audit log. For a list of the Git events are are logged, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)." + +If you do enable Git events, due to the large number of Git events that are logged, we recommend monitoring your instance's file storage and reviewing your related alert configurations. For more information, see "[Monitoring storage](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)." + +Before you can enable Git events in the audit log, you must configure a retention period for audit log data other than "infinite." For more information, see "[Configuring a retention period for audit log data](#configuring-a-retention-period-for-audit-log-data)." {% data reusables.audit_log.git-events-not-in-search-results %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} {% data reusables.audit_log.audit-data-retention-tab %} -1. 在“Git 事件选择加入”下,选择或取消选择“在审核日志中启用 Git 事件”。 +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.audit-log-tab %} +{% data reusables.audit_log.audit-data-retention-tab %} +1. Under "Git event opt-in", select or deselect **Enable git events in the audit-log**. - ![用于在审核日志中启用 Git 事件的复选框的屏幕截图](/assets/images/help/enterprises/enable-git-events-checkbox.png) -1. 单击“ **保存**”。 + ![Screenshot of the checkbox to enable Git events in the audit log](/assets/images/help/enterprises/enable-git-events-checkbox.png) +1. Click **Save**. -{% endif %} +{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md index 5f09917573..540bbcda05 100644 --- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: 在企业审核日志中显示 IP 地址 -intro: 可以在企业审核日志中显示事件的源 IP 地址。 +title: Displaying IP addresses in the audit log for your enterprise +intro: You can display the source IP address for events in your enterprise's audit log. shortTitle: IP addresses in audit log permissions: Enterprise owners can display IP addresses in the audit log for an enterprise. versions: @@ -12,44 +12,41 @@ topics: - Logging - Networking - Security -ms.openlocfilehash: 7dad3642866b637432442591d8e5714e3db6f59f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147508073' --- -## 关于在审核日志中显示 IP 地址 -默认情况下,{% data variables.product.product_name %} 不会显示企业审核日志中事件的源 IP 地址。 (可选)为了确保合规性并响应威胁,可以显示与负责每个事件的参与者相关联的完整 IP 地址。 参与者通常是用户,但也可以是应用或集成。 +## About display of IP addresses in the audit log -你有责任履行查看或存储企业审核日志中显示的 IP 地址所随附的任何法律义务。 +By default, {% data variables.product.product_name %} does not display the source IP address for events in your enterprise's audit log. Optionally, to ensure compliance and respond to threats, you can display the full IP address associated with the actor responsible for each event. Actors are typically users, but can also be apps or integrations. -如果选择显示 IP 地址,则 IP 地址仅显示在企业的审核日志中。 对于企业拥有的个人组织的审核日志中的事件,不会显示 IP 地址。 有关组织审核日志的详细信息,请参阅“[查看组织的审核日志](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)”。 +You are responsible for meeting any legal obligations that accompany the viewing or storage of IP addresses displayed within your enterprise's audit log. -无论在 {% data variables.product.product_location %} 上为企业使用哪种身份验证方法,都可以在审核日志中显示 IP 地址。 有关详细信息,请参阅“[关于企业身份验证](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)”。 +If you choose to display IP addresses, the IP addresses only appear in your enterprise's audit log. IP addresses will not appear for events in the audit logs for individual organizations owned by your enterprise. For more information about organization audit logs, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)." -当任何人在 {% data variables.product.product_location %} 上创建帐户时,即表示该用户同意 {% data variables.product.company_short %} 收集与 {% data variables.product.company_short %} 服务连接相关的基本信息(包括源 IP 地址)。 有关详细信息,请参阅“[GitHub 隐私声明](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#usage-information)”。 +You can display IP addresses in the audit log regardless of which authentication method you use for your enterprise on {% data variables.location.product_location %}. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)." -## 在审核日志中显示 IP 地址的事件 +When anyone creates an account on {% data variables.location.product_location %}, the person agrees to {% data variables.product.company_short %}'s collection of basic information about connections to {% data variables.product.company_short %}'s services, including source IP address. For more information, see "[GitHub Privacy Statement](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#usage-information)." -当企业成员与企业或企业中的组织拥有的资源交互时,{% data variables.product.product_name %} 将在审核日志中显示 IP 地址。 例如,你将看到一个审核事件的 IP 地址,这些事件涉及企业中组织拥有的内部或专用存储库,或与这些存储库关联的资源,例如问题、拉取请求、操作或项目。 +## Events that display IP addresses in the audit log -如果企业成员使用他们管理的个人帐户访问 {% data variables.product.product_location %},因为你不使用 {% data variables.product.prodname_emus %},所以 {% data variables.product.product_name %} 不会在审核日志中针对以下操作显示事件或 IP 地址。 +{% data variables.product.product_name %} displays an IP address in the audit log when a member of the enterprise interacts with a resource owned by your enterprise or an organization in your enterprise. For example, you will see an IP address for audited events involving an internal or private repository owned by an organization in your enterprise, or resources associated with those repositories, such as an issue, pull request, action, or project. + +If members of your enterprise access {% data variables.location.product_location %} with personal accounts that they manage, because you do not use {% data variables.product.prodname_emus %}, {% data variables.product.product_name %} does not display an event or IP address in the audit log for the following actions. -- 通过 {% data variables.product.product_location %} 进行身份验证 -- 与个人帐户拥有的资源(包括存储库、gist 或项目)的交互 -- 与企业中组织拥有的公共存储库交互 +- Authentication to {% data variables.location.product_location %} +- Interactions with a resource owned by the personal account, including a repository, gist, or project +- Interactions with a public repository owned by an organization in your enterprise -## 启用在审核日志中显示 IP 地址 +## Enabling display of IP addresses in the audit log -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} -1. 在“审核日志”下,单击“源 IP 泄露”。 +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.audit-log-tab %} +1. Under "Audit log", click **Source IP disclosure**. - ![“源 IP 泄露”选项卡的屏幕截图](/assets/images/help/enterprises/audit-log-source-ip-disclosure-tab.png) -1. 在“在审核日志中披露参与者 IP 地址”下,选择“启用源 IP 泄露”。 + ![Screenshot of "Source IP disclosure" tab](/assets/images/help/enterprises/audit-log-source-ip-disclosure-tab.png) +1. Under "Disclose actor IP addresses in audit logs", select **Enable source IP disclosure**. - ![启用在审核日志中显示 IP 地址的复选框的屏幕截图](/assets/images/help/enterprises/audit-log-enable-source-ip-disclosure-checkbox.png) -1. 单击“保存” 。 + ![Screenshot of checkbox to enable display of IP addresses in audit logs](/assets/images/help/enterprises/audit-log-enable-source-ip-disclosure-checkbox.png) +1. Click **Save**. -启用该功能后,可以访问审核日志以查看包含 IP 地址的事件。 有关详细信息,请参阅“[访问企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)”。 +After you enable the feature, you can access the audit log to view events that include IP addresses. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)." diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md index 643a2ff328..7ef4d78ae4 100644 --- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md @@ -311,7 +311,7 @@ To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint you must ma {% ifversion pause-audit-log-stream %} ## Pausing audit log streaming -Pausing the stream allows you to perform maintenance on the receiving application without losing audit data. Audit logs are stored for up to seven days on {% data variables.product.product_location %} and are then exported when you unpause the stream. +Pausing the stream allows you to perform maintenance on the receiving application without losing audit data. Audit logs are stored for up to seven days on {% data variables.location.product_location %} and are then exported when you unpause the stream. {% ifversion streaming-datadog %} Datadog only accepts logs from up to 18 hours in the past. If you pause a stream to a Datadog endpoint for more than 18 hours, you risk losing logs that Datadog won't accept after you resume streaming. diff --git a/translations/zh-CN/content/admin/overview/about-data-residency.md b/translations/zh-CN/content/admin/overview/about-data-residency.md index 7b510fbefd..1147142dd9 100644 --- a/translations/zh-CN/content/admin/overview/about-data-residency.md +++ b/translations/zh-CN/content/admin/overview/about-data-residency.md @@ -1,21 +1,16 @@ --- -title: 关于数据保存 -intro: '您可以选择 {% data variables.product.product_name %} 为您的企业存储所有客户数据的地理位置。' +title: About data residency +intro: 'You can choose the geography where {% data variables.product.product_name %} stores all customer data for your enterprise.' versions: ghae: '*' type: overview topics: - Enterprise - Fundamentals -ms.openlocfilehash: b182073799b1f45b697bef47a4314644bc8a52b1 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145098694' --- -{% data reusables.github-ae.github-ae-enables-you %} 您可以选择为 {% data variables.product.product_location %} 存储所有客户数据的地理位置,企业成员可以从世界任何地方访问 {% data variables.product.product_name %}。 -创建企业时,您可以告诉 {% data variables.contact.contact_enterprise_sales %} 在哪里存储客户数据。 {% data variables.product.company_short %} 不会将您企业的任何数据存储或移动到您选择的地理区域之外。 +{% data reusables.github-ae.github-ae-enables-you %} You can choose the geography where you store all the customer data for {% data variables.location.product_location %}, and members of your enterprise can access {% data variables.product.product_name %} from anywhere in the world. -有关可用地理位置的更多信息,请联系 {% data variables.contact.contact_enterprise_sales %}。 +When creating your enterprise, you can tell {% data variables.contact.contact_enterprise_sales %} where to store your customer data. {% data variables.product.company_short %} will not store or move any of your enterprise's data outside of the geography you choose. + +For more information about the available geographies, contact {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md b/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md index 60793424f8..feb02861bf 100644 --- a/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md +++ b/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md @@ -28,7 +28,7 @@ Your enterprise account on {% data variables.product.prodname_dotcom_the_website {% elsif ghes or ghae %} -The enterprise account on {% ifversion ghes %}{% data variables.product.product_location_enterprise %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} allows you to manage the organizations{% ifversion ghes %} on{% elsif ghae %} owned by{% endif %} your {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} instance{% elsif ghae %}enterprise{% endif %}. +The enterprise account on {% ifversion ghes %}{% data variables.location.product_location_enterprise %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} allows you to manage the organizations{% ifversion ghes %} on{% elsif ghae %} owned by{% endif %} your {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} instance{% elsif ghae %}enterprise{% endif %}. {% endif %} @@ -76,7 +76,7 @@ If you use both {% data variables.product.prodname_ghe_cloud %} and {% data vari - Billing and usage for {% data variables.product.prodname_ghe_server %} instances - Requests and support bundle sharing with {% data variables.contact.enterprise_support %} -You can also connect the enterprise account on {% data variables.product.product_location_enterprise %} to your enterprise account on {% data variables.product.prodname_dotcom_the_website %} to see license usage details for your {% data variables.product.prodname_enterprise %} subscription from {% data variables.product.prodname_dotcom_the_website %}. For more information, see {% ifversion ghec %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."{% endif %} +You can also connect the enterprise account on {% data variables.location.product_location_enterprise %} to your enterprise account on {% data variables.product.prodname_dotcom_the_website %} to see license usage details for your {% data variables.product.prodname_enterprise %} subscription from {% data variables.product.prodname_dotcom_the_website %}. For more information, see {% ifversion ghec %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."{% endif %} For more information about the differences between {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}, see "[{% data variables.product.prodname_dotcom %}'s products](/get-started/learning-about-github/githubs-products)." {% data reusables.enterprise-accounts.to-upgrade-or-get-started %} diff --git a/translations/zh-CN/content/admin/overview/about-github-enterprise-server.md b/translations/zh-CN/content/admin/overview/about-github-enterprise-server.md index a0ccb62bbd..c3b54b8acf 100644 --- a/translations/zh-CN/content/admin/overview/about-github-enterprise-server.md +++ b/translations/zh-CN/content/admin/overview/about-github-enterprise-server.md @@ -1,104 +1,99 @@ --- -title: 关于 GitHub Enterprise Server -intro: '{% data variables.product.product_name %} 是可在专用环境中托管的软件开发平台。' +title: About GitHub Enterprise Server +intro: '{% data variables.product.product_name %} is a software development platform that you can host in a private environment.' versions: ghes: '*' type: overview topics: - Enterprise - Fundamentals -ms.openlocfilehash: 2622e3708cc31b24fe39929da68ba5dc8e864d88 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147877157' --- -## 关于 {% data variables.product.product_name %} -{% data reusables.enterprise.ghes-is-a-self-hosted-platform %}你的团队可以使用 {% data variables.product.product_name %} 通过 Git 版本控制、强大的 API、生产力和协作工具及集成生成和交付软件。 熟悉 {% data variables.product.prodname_dotcom_the_website %} 的开发人员可以使用熟悉的功能和工作流无缝加入和参与。 {% data reusables.enterprise.about-github-for-enterprises %} +## About {% data variables.product.product_name %} + +{% data reusables.enterprise.ghes-is-a-self-hosted-platform %} Your team can use {% data variables.product.product_name %} to build and ship software using Git version control, powerful APIs, productivity and collaboration tools, and integrations. Developers familiar with {% data variables.product.prodname_dotcom_the_website %} can onboard and contribute seamlessly using familiar features and workflows. {% data reusables.enterprise.about-github-for-enterprises %} {% data reusables.enterprise.ghes-runs-on-your-infrastructure %} -{% data reusables.enterprise.github-distributes-ghes %}有关详细信息,请参阅“[系统概述](/admin/overview/system-overview)”。 +{% data reusables.enterprise.github-distributes-ghes %} For more information, see "[System overview](/admin/overview/system-overview)." -可以选择在本地部署 {% data variables.product.product_name %} 或支持云环境。 +You can choose to deploy {% data variables.product.product_name %} on premises, or to a supported cloud environment. -## 支持的部署环境 +## Supported environments for deployment -可以将 {% data variables.product.product_name %} 部署到本地数据中心内的虚拟化虚拟机监控程序,或部署到公有云服务。 +You can deploy {% data variables.product.product_name %} to a virtualization hypervisor within your on-premises datacenter, or to a public cloud service. -{% data variables.product.company_short %} 支持用于本地部署的以下虚拟化虚拟机监控程序。 +{% data variables.product.company_short %} supports the following virtualization hypervisors for on-premises deployment. - Microsoft Hyper-V - OpenStack KVM - VMware ESXi -{% data variables.product.company_short %} 支持以下云部署服务。 +{% data variables.product.company_short %} supports the following services for cloud deployment. - Amazon Web Services (AWS) - Google Cloud Platform (GCP) - Microsoft Azure -有关详细信息,请参阅“[设置 {% data variables.product.prodname_ghe_server %} 实例](/admin/installation/setting-up-a-github-enterprise-server-instance)”。 +For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)." -## 关于发布和升级 +## About releases and upgrades -{% data reusables.enterprise.constantly-improving %}你负责升级到实例。 有关详细信息,请参阅“[{% data variables.product.product_name %} 版本](/admin/all-releases)”。 +{% data reusables.enterprise.constantly-improving %} You are responsible for upgrades to your instance. For more information, see "[{% data variables.product.product_name %} releases](/admin/all-releases)." -## 关于管理 +## About administration -可以通过浏览器、管理 SSH 访问和 REST 或 GraphQL API 配置和监视 {% data variables.product.product_name %}。 {% data variables.product.company_short %} 发现,具有 Linux 管理体验的人员在部署和维护 {% data variables.product.product_name %} 时更为成功。 +You can configure and monitor {% data variables.product.product_name %} via browser, administrative SSH access, and REST or GraphQL APIs. {% data variables.product.company_short %} has found that people with Linux administration experience are more successful with the deployment and maintainance of {% data variables.product.product_name %}. -你可以向某些员工授予对 {% data variables.product.product_name %} 的管理访问权限,以便他们可以设置外部身份验证、配置实例以满足开发人员需求,以及监视实例的活动和性能。 为了确保符合业务规则或法规限制,管理员可以配置控制人们如何使用 {% data variables.product.product_location %} 的策略。 有关详细信息,请参阅以下文章。 +You can give certain employees administrative access to {% data variables.product.product_name %}, so they can set up external authentication, configure the instance to meet developer needs, and monitor the instance's activity and performance. To ensure compliance with business rules or regulatory restrictions, administrators can configure policies that control how people use {% data variables.location.product_location %}. For more information, see the following articles. -- “[关于企业身份验证](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)” -- “[配置你的企业](/admin/configuration/configuring-your-enterprise)” -- “[关于 {% data variables.product.prodname_enterprise %} API](/admin/overview/about-the-github-enterprise-api)” -- “[监视你的设备](/admin/enterprise-management/monitoring-your-appliance)” -- “[监视企业中的活动](/admin/monitoring-activity-in-your-enterprise)” -- “[关于企业策略](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)” +- "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)" +- "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)" +- "[About the {% data variables.product.prodname_enterprise %} API](/admin/overview/about-the-github-enterprise-api)" +- "[Monitoring your appliance](/admin/enterprise-management/monitoring-your-appliance)" +- "[Monitoring activity in your enterprise](/admin/monitoring-activity-in-your-enterprise)" +- "[About enterprise policies](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)" -## 关于可选功能 +## About optional features -可以为 {% data variables.product.product_name %} 配置可选功能,以提高企业的软件开发生命周期。 +You can configure optional features for {% data variables.product.product_name %} that improve the software development lifecycle for your enterprise. -| 功能 | 说明 | 详细信息 | +| Feature | Description | More information | | :- | :- | :- | -| {% data variables.product.prodname_actions %} | 自动化 CI/CD 和开发工作流 | “[关于企业的 {% data variables.product.prodname_actions %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)” | -| {% data variables.product.prodname_github_connect %} | 以有限方式受益于 {% data variables.product.prodname_dotcom_the_website %} 的强大功能 | “[关于 {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)” | -| {% data variables.product.prodname_GH_advanced_security %} | 提高代码安全性和质量 | “[关于 {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)” | -| {% data variables.product.prodname_registry %} | 为企业托管软件包 | “[{% data variables.product.prodname_registry %} 简介](/packages/learn-github-packages/introduction-to-github-packages)” | +| {% data variables.product.prodname_actions %} | Automate CI/CD and development workflows | "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)" | +| {% data variables.product.prodname_github_connect %} | Benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways | "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)" | +| {% data variables.product.prodname_GH_advanced_security %} | Improve code security and quality | "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)" | +| {% data variables.product.prodname_registry %} | Host software packages for your enterprise | "[Introduction to {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)" | -## 关于部署拓扑 +## About deployment topologies -默认情况下,{% data variables.product.product_name %} 作为独立实例运行。 可以通过为部署使用不同的拓扑来提高 {% data variables.product.product_name %} 的可靠性和性能。 +By default, {% data variables.product.product_name %} runs as a standalone instance. You can increase the reliability and performance of {% data variables.product.product_name %} by using a different topology for your deployment. -- 若要缓解系统或网络故障的影响,可以部署被动副本实例。 在影响主实例的中断期间,可以手动故障转移到副本实例。 有关详细信息,请参阅“[关于高可用性配置](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration)”。 -- 可以配置多个活动副本,以提高与主实例相距很远的开发人员的性能。 有关详细信息,请参阅“[有关异地复制](/admin/enterprise-management/configuring-high-availability/about-geo-replication)”。 -- 一些拥有数万个开发人员的企业可能会受益于横向缩放而不是垂直缩放的群集配置。 有关详细信息,请参阅“[关于群集](/admin/enterprise-management/configuring-clustering/about-clustering)”。 +- To mitigate the impact of system or network failures, you can deploy a passive replica instance. During an outage that affects your primary instance, you can manually fail over to the replica instance. For more information, see "[About high availability configuration](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration)." +- You can configure multiple active replicas to improve performance for developers who are geographically distant from your primary instance. For more information, see "[About geo-replication](/admin/enterprise-management/configuring-high-availability/about-geo-replication)." +- Some enterprises with tens of thousands of developers may benefit from a cluster configuration that scales horizontally instead of vertically. For more information, see "[About clustering](/admin/enterprise-management/configuring-clustering/about-clustering)." -## 关于备份和灾难恢复 +## About backups and disaster recovery -为了防止开发人员的数据丢失或服务中断,{% data variables.product.company_short %} 强烈建议你制定灾难恢复计划。 可以通过使用 {% data variables.product.prodname_enterprise_backup_utilities %} 部署和配置 Linux 或 Unix 主机系统来备份实例的配置和用户数据。 有关详细信息,请参阅“[在设备上配置备份](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)”。 +To safeguard against data loss or service disruptions for your developers, {% data variables.product.company_short %} strongly recommends that you establish a plan for disaster recovery. You can back up your instance's configuration and user data by deploying and configuring a Linux or Unix host system with {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)." -此外,还可以将被动副本实例配置为在系统或网络出现故障时故障转移到该实例。 有关详细信息,请参阅“[关于部署拓扑](#about-deployment-topologies)”。 +Additionally, you can configure a passive replica instance to fail over to in the event of a system or network failure. For more information, see "[About deployment topologies](#about-deployment-topologies)." -## 关于文档 +## About documentation -此网站上提供了 {% data variables.product.product_name %} 的管理员和用户的文档 {% data variables.product.prodname_docs %}。 +Documentation for both administrators and users of {% data variables.product.product_name %} is available on this site, {% data variables.product.prodname_docs %}. -- [企业管理员文档](/admin) -- [用户文档](/) +- [Enterprise administrator documentation](/admin) +- [User documentation](/) -{% data variables.product.product_name %} 的不同版本分别反映在有关 {% data variables.product.prodname_docs %} 的文档中。 有关详细信息,请参阅[关于 {% data variables.product.prodname_docs %} 的版本](/get-started/learning-about-github/about-versions-of-github-docs)。 +Different versions of {% data variables.product.product_name %} are reflected separately in the documentation on {% data variables.product.prodname_docs %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." -## 尝试 {% data variables.product.product_name %} +## Trying {% data variables.product.product_name %} -可以注册 {% data variables.product.product_name %} 的免费 45 天试用版。 有关详细信息,请参阅“[设置试用版 {% data variables.product.prodname_ghe_server %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server)”。 +You can sign up for a free, 45-day trial of {% data variables.product.product_name %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server)." -## 延伸阅读 +## Further reading -- “[{% data variables.product.product_name %} 入门](/get-started/onboarding/getting-started-with-github-enterprise-server)” -- “[关于 {% data variables.contact.github_support %}](/support/learning-about-github-support/about-github-support)” -- `github/roadmap` 存储库中的 [{% data variables.product.prodname_roadmap %}]( {% data variables.product.prodname_roadmap_link %} ) +- "[Getting started with {% data variables.product.product_name %}](/get-started/onboarding/getting-started-with-github-enterprise-server)" +- "[About {% data variables.contact.github_support %}](/support/learning-about-github-support/about-github-support)" +- [ {% data variables.product.prodname_roadmap %} ]( {% data variables.product.prodname_roadmap_link %} ) in the `github/roadmap` repository diff --git a/translations/zh-CN/content/admin/overview/system-overview.md b/translations/zh-CN/content/admin/overview/system-overview.md index 277fae1f99..c1e59ff959 100644 --- a/translations/zh-CN/content/admin/overview/system-overview.md +++ b/translations/zh-CN/content/admin/overview/system-overview.md @@ -1,6 +1,6 @@ --- -title: 系统概览 -intro: '详细了解 {% data variables.product.product_name %} 的系统内部结构、功能和安全性。' +title: System overview +intro: 'Learn more about {% data variables.product.product_name %}''s system internals, functionality, and security.' redirect_from: - /enterprise/admin/installation/system-overview - /enterprise/admin/overview/system-overview @@ -13,160 +13,155 @@ topics: - Infrastructure - Security - Storage -ms.openlocfilehash: 656d68b267b4a739812b10e9409609f61cacdd5e -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147066936' --- -## 关于 {% data variables.product.product_name %} -{% data reusables.enterprise.ghes-is-a-self-hosted-platform %} {% data reusables.enterprise.github-distributes-ghes %} 有关详细信息,请参阅“[关于 {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server)”。 +## About {% data variables.product.product_name %} -## 存储体系结构 +{% data reusables.enterprise.ghes-is-a-self-hosted-platform %} {% data reusables.enterprise.github-distributes-ghes %} For more information, see "[About {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server)." -{% data variables.product.product_name %} 需要两个存储卷,一个装载到根文件系统路径 (`/`) 下,另一个装载到用户文件系统路径 (`/data/user`) 下 。 这种架构将运行软件环境与持久应用程序数据分离,从而可以简化升级、回滚和恢复程序。 +## Storage architecture -根文件系统包含在分布式机器映像中。 它包含基本操作系统和 {% data variables.product.product_name %} 应用程序环境。 根文件系统应被视为临时性的。 升级到今后的 {% data variables.product.product_name %} 版本时,根文件系统中的所有数据都将被替代。 +{% data variables.product.product_name %} requires two storage volumes, one mounted to the *root filesystem* path (`/`) and the other to the *user filesystem* path (`/data/user`). This architecture simplifies the upgrade, rollback, and recovery procedures by separating the running software environment from persistent application data. -根存储量分成两个相同大小的分区。 其中一个分区将装载为根文件系统 (`/`)。 另一个分区仅在升级和升级的回退过程中作为 `/mnt/upgrade` 装载,以便在必要时更容易回退。 例如,如果分配了 200GB 根卷,將有 100GB 分配到根文件系统,100GB 用于升级和回滚。 +The root filesystem is included in the distributed machine image. It contains the base operating system and the {% data variables.product.product_name %} application environment. The root filesystem should be treated as ephemeral. Any data on the root filesystem will be replaced when upgrading to future {% data variables.product.product_name %} releases. -根文件系统包含存储以下信息的文件。 此列表并未囊括所有方式。 +The root storage volume is split into two equally-sized partitions. One of the partitions will be mounted as the root filesystem (`/`). The other partition is only mounted during upgrades and rollbacks of upgrades as `/mnt/upgrade`, to facilitate easier rollbacks if necessary. For example, if a 200GB root volume is allocated, there will be 100GB allocated to the root filesystem and 100GB reserved for the upgrades and rollbacks. -- 自定义证书颁发机构 (CA) 证书(在 `/usr/local/share/ca-certificates*` 中) -- 自定义网络配置 -- 自定义防火墙配置 -- 复制状态 +The root filesystem contains files that store the following information. This list is not exhaustive. -用户文件系统包含存储以下配置和数据的文件。 此列表并未囊括所有方式。 +- Custom certificate authority (CA) certificates (in `/usr/local/share/ca-certificates*`) +- Custom networking configurations +- Custom firewall configurations +- The replication state -- Git 存储库 -- 数据库 -- 搜索索引 -- 在 {% data variables.product.prodname_pages %} 站点上发布的内容 -- {% data variables.large_files.product_name_long %} 中的大文件 -- 预接收挂钩环境 +The user filesystem contains files that store following configuration and data. This list is not exhaustive. -## 部署拓扑 +- Git repositories +- Databases +- Search indexes +- Content published on {% data variables.product.prodname_pages %} sites +- Large files from {% data variables.large_files.product_name_long %} +- Pre-receive hook environments -可以在各种拓扑(例如高可用性对)中部署 {% data variables.product.product_name %}。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server#about-deployment-topologies)”。 +## Deployment topologies -## 数据保留和数据中心冗余 +You can deploy {% data variables.product.product_name %} in a variety of topologies, such as a high availability pair. For more information, see "[About {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server#about-deployment-topologies)." + +## Data retention and datacenter redundancy {% warning %} -**警告**:在生产环境中使用 {% data variables.product.product_name %} 之前,我们强烈建议你设置备份和灾难恢复计划。 +**Warning**: Before using {% data variables.product.product_name %} in a production environment, we strongly recommend you set up backups and a disaster recovery plan. {% endwarning %} -{% data variables.product.product_name %} 包括支持通过 {% data variables.product.prodname_enterprise_backup_utilities %} 进行联机和增量备份。 您可以通过安全网络链接(SSH 管理端口)远距离为场外或地理上分散的存储生成增量快照。 在主数据中心发生灾难时,你可以在恢复时通过网络将快照恢复到新预配的实例中。 +{% data variables.product.product_name %} includes support for online and incremental backups with {% data variables.product.prodname_enterprise_backup_utilities %}. You can take incremental snapshots over a secure network link (the SSH administrative port) over long distances for off-site or geographically dispersed storage. You can restore snapshots over the network into a newly provisioned instance at time of recovery in case of disaster at the primary datacenter. -除网络备份外,在实例处于离线或维护模式时,还支持用户存储卷的 AWS (EBS) 和 VMware 磁盘快照。 如果您的服务级别要求允许定期离线维护,可以将定期卷快照用作低成本、低复杂性的方案,代替通过 {% data variables.product.prodname_enterprise_backup_utilities %} 进行网络备份。 +In addition to network backups, both AWS (EBS) and VMware disk snapshots of the user storage volumes are supported while the instance is offline or in maintenance mode. Regular volume snapshots can be used as a low-cost, low-complexity alternative to network backups with {% data variables.product.prodname_enterprise_backup_utilities %} if your service level requirements allow for regular offline maintenance. -有关详细信息,请参阅“[在设备上配置备份](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)”。 +For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)." -## 安全性 +## Security {% data reusables.enterprise.ghes-runs-on-your-infrastructure %} -{% data variables.product.product_name %} 还包含额外的安全功能。 +{% data variables.product.product_name %} also includes additional security features. -- [操作系统、软件和补丁](#operating-system-software-and-patches) -- [网络安全](#network-security) -- [应用程序安全性](#application-security) -- [外部服务和支持访问](#external-services-and-support-access) -- [加密通信](#encrypted-communication) -- [用户和访问权限](#users-and-access-permissions) -- [身份验证](#authentication) -- [审核和访问日志记录](#audit-and-access-logging) +- [Operating system, software, and patches](#operating-system-software-and-patches) +- [Network security](#network-security) +- [Application security](#application-security) +- [External services and support access](#external-services-and-support-access) +- [Encrypted communication](#encrypted-communication) +- [Users and access permissions](#users-and-access-permissions) +- [Authentication](#authentication) +- [Audit and access logging](#audit-and-access-logging) -### 操作系统、软件和补丁 +### Operating system, software, and patches -{% data variables.product.product_name %} 运行自定义的 Linux 操作系统,其中只包含必要的应用程序和服务。 {% data variables.product.company_short %} 将实例核心操作系统的补丁作为其标准产品发布周期的一部分进行分发。 补丁可解决 {% data variables.product.product_name %} 的功能、稳定性和非关键性安全问题。 {% data variables.product.company_short %} 还根据需要在常规发布周期之外提供重要的安全补丁。 +{% data variables.product.product_name %} runs a customized Linux operating system with only the necessary applications and services. {% data variables.product.company_short %} distributes patches for the instance's core operating system as part of its standard product release cycle. Patches address functionality, stability, and non-critical security issues for {% data variables.product.product_name %}. {% data variables.product.company_short %} also provides critical security patches as needed outside of the regular release cycle. -{% data variables.product.product_name %} 作为一种设备提供,许多操作系统包与通常的 Debian 分发相比进行了修改。 因此,我们不支持修改基础操作系统(包括操作系统升级),与 [{% data variables.product.prodname_ghe_server %} 许可证和支持协议](https://enterprise.github.com/license)第 11.3 除外条款保持一致。 +{% data variables.product.product_name %} is provided as an appliance, and many of the operating system packages are modified compared to the usual Debian distribution. We do not support modifying the underlying operating system for this reason (including operating system upgrades), which is aligned with the [{% data variables.product.prodname_ghe_server %} license and support agreement](https://enterprise.github.com/license), under section 11.3 Exclusions. -目前,{% data variables.product.product_name %} 的基础操作系统是 Debian 9 (Stretch),并接受 Debian 长期支持计划的支持。 计划在 Stretch 的 Debian LTS 期间结束前迁移到更新的基础操作系统。 +Currently, the base operating system for {% data variables.product.product_name %} is Debian 9 (Stretch), which receives support under the Debian Long Term Support program. There are plans to move to a newer base operating system before the end of the Debian LTS period for Stretch. -定期补丁更新发布在 {% data variables.product.product_name %} [发行](https://enterprise.github.com/releases)页面上,[发行说明](/admin/release-notes)页面提供了详细信息。 这些补丁一般含有经过测试并且质量经过我们工程团队批准的上游供应商和项目安全补丁。 从上游更新发布到测试以及捆绑于即将发布的 {% data variables.product.product_name %} 补丁版本中时,可能稍有延迟。 +Regular patch updates are released on the {% data variables.product.product_name %} [releases](https://enterprise.github.com/releases) page, and the [release notes](/admin/release-notes) page provides more information. These patches typically contain upstream vendor and project security patches after they've been tested and quality approved by our engineering team. There can be a slight time delay from when the upstream update is released to when it's tested and bundled in an upcoming {% data variables.product.product_name %} patch release. -### 网络安全性 +### Network security -{% data variables.product.product_name %} 的内部防火墙限制对实例服务的网络访问。 网络上仅提供设备正常运行所需的服务。 有关详细信息,请参阅“[网络端口](/admin/configuration/configuring-network-settings/network-ports)”。 +{% data variables.product.product_name %}'s internal firewall restricts network access to the instance's services. Only services necessary for the appliance to function are available over the network. For more information, see "[Network ports](/admin/configuration/configuring-network-settings/network-ports)." -### 应用程序安全性 +### Application security -{% data variables.product.company_short %} 的应用程序安全团队全时关注 {% data variables.product.company_short %} 产品(包括 {% data variables.product.product_name %})的漏洞评估、渗透测试和代码评审。 {% data variables.product.company_short %} 还与外部安全公司签约,要求他们对 {% data variables.product.company_short %} 产品定期进行安全性评估。 +{% data variables.product.company_short %}'s application security team focuses full-time on vulnerability assessment, penetration testing, and code review for {% data variables.product.company_short %} products, including {% data variables.product.product_name %}. {% data variables.product.company_short %} also contracts with outside security firms to provide point-in-time security assessments of {% data variables.product.company_short %} products. -### 外部服务和支持 +### External services and support access -{% data variables.product.product_name %} 无需从网络访问外部服务也可以正常运行。 您可以选择集成外部服务,以提供电子邮件传送、外部监控和日志转发等功能。 有关详细信息,请参阅“[配置电子邮件通知](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)”、“[设置外部监视](/admin/enterprise-management/monitoring-your-appliance/setting-up-external-monitoring)”和“[日志转发](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)”。 +{% data variables.product.product_name %} can operate without any egress access from your network to outside services. You can optionally enable integration with external services for email delivery, external monitoring, and log forwarding. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)," "[Setting up external monitoring](/admin/enterprise-management/monitoring-your-appliance/setting-up-external-monitoring)," and "[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)." -您可以手动收集故障排除数据并发送至 {% data variables.contact.github_support %}。 有关详细信息,请参阅“[向 {% data variables.contact.github_support %} 提供数据](/support/contacting-github-support/providing-data-to-github-support)”。 +You can manually collect and send troubleshooting data to {% data variables.contact.github_support %}. For more information, see "[Providing data to {% data variables.contact.github_support %}](/support/contacting-github-support/providing-data-to-github-support)." -### 加密通信 +### Encrypted communication -{% data variables.product.company_short %} 将 {% data variables.product.product_name %} 设计为在公司防火墙后面运行。 为确保线路通信安全,我们建议您启用传输层安全协议 (TLS)。 {% data variables.product.product_name %} 在 HTTPS 流量方面支持 2048 位和更高的商业 TLS 证书。 有关详细信息,请参阅“[配置 TLS](/admin/configuration/configuring-network-settings/configuring-tls)”。 +{% data variables.product.company_short %} designs {% data variables.product.product_name %} to run behind your corporate firewall. To secure communication over the wire, we encourage you to enable Transport Layer Security (TLS). {% data variables.product.product_name %} supports 2048-bit and higher commercial TLS certificates for HTTPS traffic. For more information, see "[Configuring TLS](/admin/configuration/configuring-network-settings/configuring-tls)." -默认情况下,该实例还为使用 Git 的仓库访问和管理目的提供安全外壳 (SSH) 访问。 有关详细信息,请参阅“[关于 SSH](/authentication/connecting-to-github-with-ssh/about-ssh)”和“[访问管理 shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)”。 +By default, the instance also offers Secure Shell (SSH) access for both repository access using Git and administrative purposes. For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)" and "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." {% ifversion ghes > 3.3 %} -如果您为 {% data variables.product.product_location %} 配置 SAML 身份验证,则可以在实例和 SAML IdP 之间启用加密断言。 有关详细信息,请参阅“[使用 SAML](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml#enabling-encrypted-assertions)”。 +If you configure SAML authentication for {% data variables.location.product_location %}, you can enable encrypted assertions between the instance and your SAML IdP. For more information, see "[Using SAML](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml#enabling-encrypted-assertions)." {% endif %} -### 用户和访问权限 +### Users and access permissions -{% data variables.product.product_name %} 提供三种类型的帐户。 +{% data variables.product.product_name %} provides three types of accounts. -- `admin` Linux 用户帐户已控制对基础操作系统的访问,包括对直接文件系统和数据库的访问。 一小部分受信任的管理员应该有权访问此帐户,他们可以通过 SSH 访问。 有关详细信息,请参阅“[访问管理 shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)”。 -- 实例 Web 应用程序中的用户帐户对自己的数据以及其他用户或组织明确授予权限的任何数据具有完全访问权限。 -- 实例 Web 应用程序中的站点管理员是可以管理高级 Web 应用程序和实例设置、用户和组织帐户设置以及仓库数据的用户帐户。 +- The `admin` Linux user account has controlled access to the underlying operating system, including direct filesystem and database access. A small set of trusted administrators should have access to this account, which they can access over SSH. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." +- User accounts in the instance's web application have full access to their own data and any data that other users or organizations explicitly grant. +- Site administrators in the instance's web application are user accounts that can manage high-level web application and instance settings, user and organization account settings, and repository data. -有关 {% data variables.product.product_name %} 用户权限的详细信息,请参阅“[{% data variables.product.prodname_dotcom %} 上的访问权限](/get-started/learning-about-github/access-permissions-on-github)”。 +For more information about {% data variables.product.product_name %}'s user permissions, see "[Access permissions on {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/access-permissions-on-github)." -### 身份验证 +### Authentication -{% data variables.product.product_name %} 提供四种身份验证方法。 +{% data variables.product.product_name %} provides four authentication methods. -- SSH 公钥身份验证提供使用 Git 的仓库访问权限和管理 shell 的访问权限。 有关详细信息,请参阅“[关于 SSH](/authentication/connecting-to-github-with-ssh/about-ssh)”和“[访问管理 shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)”。 -- 使用 HTTP cookie 的用户名和密码身份验证提供 Web 应用程序访问和会话管理权限,可选择双重身份验证 (2FA)。 有关详细信息,请参阅“[使用内置身份验证](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication)”。 -- 使用 LDAP 服务、SAML 身份提供程序 (IdP) 或其他兼容服务的外部 LDAP、SAML 或 CAS 身份验证提供对 Web 应用程序的访问权限。 有关详细信息,请参阅“[管理企业的 IAM](/admin/identity-and-access-management/managing-iam-for-your-enterprise)”。 -- OAuth 和个人访问令牌为外部客户端和服务提供对 Git 仓库数据和 API 的访问权限。 有关详细信息,请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 +- SSH public key authentication provides both repository access using Git and administrative shell access. For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)" and "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." +- Username and password authentication with HTTP cookies provides web application access and session management, with optional two-factor authentication (2FA). For more information, see "[Using built-in authentication](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication)." +- External LDAP, SAML, or CAS authentication using an LDAP service, SAML Identity Provider (IdP), or other compatible service provides access to the web application. For more information, see "[Managing IAM for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise)." +- OAuth and {% data variables.product.pat_generic %}s provide access to Git repository data and APIs for both external clients and services. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." -### 审核和访问日志记录 +### Audit and access logging -{% data variables.product.product_name %} 存储传统的操作系统日志和应用程序日志。 应用程序还会编写详细的审核和安全日志,永久存储在 {% data variables.product.product_name %} 上。 可通过 `syslog-ng` 协议将两种类型的日志实时转发到多个目标。 有关详细信息,请参阅“[关于你企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)”和“[日志转发](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)”。 +{% data variables.product.product_name %} stores both traditional operating system and application logs. The application also writes detailed auditing and security logs, which {% data variables.product.product_name %} stores permanently. You can forward both types of logs in real time to multiple destinations via the `syslog-ng` protocol. For more information, see "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)" and "[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)." -访问和审核日志包括如下信息。 +Access and audit logs include information like the following. -#### 访问日志 +#### Access logs -- 关于浏览器和 API 访问的完整 web 服务器日志 -- 通过 Git、HTTP 和 SSH 协议访问仓库数据的完整日志 -- 通过 HTTPS 和 SSH 的管理访问日志 +- Full web server logs for both browser and API access +- Full logs for access to repository data over Git, HTTPS, and SSH protocols +- Administrative access logs over HTTPS and SSH -#### 审核日志 +#### Audit logs -- 用户登录、密码重置、2FA 请求、电子邮件设置更改,以及对授权应用程序和 API 的更改 -- 站点管理员操作,例如解锁用户帐户和仓库 -- 仓库推送事件、访问授权、转让和重命名 -- 组织成员变更,包括团队创建和删除 +- User logins, password resets, 2FA requests, email setting changes, and changes to authorized applications and APIs +- Site administrator actions, such as unlocking user accounts and repositories +- Repository push events, access grants, transfers, and renames +- Organization membership changes, including team creation and destruction -## {% data variables.product.product_name %} 的开源依赖项 +## Open source dependencies for {% data variables.product.product_name %} -若要查看实例的 {% data variables.product.product_name %} 版本中依赖项的完整列表以及每个项目的许可证,请访问 `http(s)://HOSTNAME/site/credits`。 +You can see a complete list of dependencies in your instance's version of {% data variables.product.product_name %}, as well as each project's license, at `http(s)://HOSTNAME/site/credits`. -你的实例上提供包含依赖项和关联元数据完整列表的 tarball。 +Tarballs with a full list of dependencies and associated metadata are available on your instance. -- 对于所有平台通用的依赖项,请访问 `/usr/local/share/enterprise/dependencies--base.tar.gz` -- 对于特定于平台的依赖项,请访问 `/usr/local/share/enterprise/dependencies--.tar.gz` +- For dependencies common to all platforms, at `/usr/local/share/enterprise/dependencies--base.tar.gz` +- For dependencies specific to a platform, at `/usr/local/share/enterprise/dependencies--.tar.gz` -还在 `https://enterprise.github.com/releases//download.html` 处提供包含依赖项和元数据完整列表的 tarball。 +Tarballs are also available, with a full list of dependencies and metadata, at `https://enterprise.github.com/releases//download.html`. -## 延伸阅读 +## Further reading -- [设置 {% data variables.product.prodname_ghe_server %} 的试用版](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server) -- [设置 {% data variables.product.prodname_ghe_server %} 实例](/admin/installation/setting-up-a-github-enterprise-server-instance) +- "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server)" +- "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)" diff --git a/translations/zh-CN/content/admin/packages/enabling-github-packages-with-aws.md b/translations/zh-CN/content/admin/packages/enabling-github-packages-with-aws.md index f0b4b0384e..a60407369d 100644 --- a/translations/zh-CN/content/admin/packages/enabling-github-packages-with-aws.md +++ b/translations/zh-CN/content/admin/packages/enabling-github-packages-with-aws.md @@ -1,6 +1,6 @@ --- -title: 使用 AWS 启用 GitHub Packages -intro: '以 AWS 作为外部存储设置 {% data variables.product.prodname_registry %} 。' +title: Enabling GitHub Packages with AWS +intro: 'Set up {% data variables.product.prodname_registry %} with AWS as your external storage.' versions: ghes: '*' type: tutorial @@ -10,27 +10,22 @@ topics: - Packages - Packages shortTitle: Enable Packages with AWS -ms.openlocfilehash: 185373657cad88bc0a45e48eb5835abdf394f9ce -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145099002' --- + {% warning %} -警告: -- 为存储桶配置所需的限制性访问策略至关重要,因为 {% data variables.product.company_short %} 不会将特定对象权限或其他访问控制列表 (ACL) 应用于存储桶配置。 例如,如果将存储桶设为公共,则在公共互联网上可以访问存储桶中的数据。 有关详细信息,请参阅 AWS 文档中的“[设置 Bucket 和对象访问权限](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/set-permissions.html)”。 -- 我们建议对 {% data variables.product.prodname_registry %} 使用专用存储桶,与用于 {% data variables.product.prodname_actions %} 存储的存储桶分开。 -- 请确保配置将来要使用的存储桶。 在开始使用 {% data variables.product.prodname_registry %} 后,我们不建议更改存储系统。 +**Warnings:** +- It is critical that you configure any restrictive access policies you need for your storage bucket, because {% data variables.product.company_short %} does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible to the public internet. For more information, see "[Setting bucket and object access permissions](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/set-permissions.html)" in the AWS Documentation. +- We recommend using a dedicated bucket for {% data variables.product.prodname_registry %}, separate from the bucket you use for {% data variables.product.prodname_actions %} storage. +- Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}. {% endwarning %} -## 先决条件 +## Prerequisites -在 {% data variables.product.product_location_enterprise %} 上启用和配置 {% data variables.product.prodname_registry %} 之前,您必须准备 AWS 存储桶。 为了准备 AWS Bucket,建议在 [AWS 文档](https://docs.aws.amazon.com/index.html)中查阅官方 AWS 文档。 +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your AWS storage bucket. To prepare your AWS storage bucket, we recommend consulting the official AWS docs at [AWS Documentation](https://docs.aws.amazon.com/index.html). -确保您的 AWS 访问密钥 ID 和密钥具有以下权限: +Ensure your AWS access key ID and secret have the following permissions: - `s3:PutObject` - `s3:GetObject` - `s3:ListBucketMultipartUploads` @@ -39,23 +34,28 @@ ms.locfileid: '145099002' - `s3:DeleteObject` - `s3:ListBucket` -## 使用 AWS 外部存储启用 {% data variables.product.prodname_registry %} +## Enabling {% data variables.product.prodname_registry %} with AWS external storage -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} {% ifversion ghes %} -1. 在“包存储”下,选择“Amazon S3”并输入存储 Bucket 的详细信息: - - AWS 服务 URL:Bucket 的服务 URL。 例如,如果你的 S3 存储桶是在 `us-west-2 region` 中创建的,则此值应为 `https://s3.us-west-2.amazonaws.com`。 +1. Under "Packages Storage", select **Amazon S3** and enter your storage bucket's details: + - **AWS Service URL:** The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2 region`, this value should be `https://s3.us-west-2.amazonaws.com`. - 有关详细信息,请参阅 AWS 文档中的“[AWS 服务终结点](https://docs.aws.amazon.com/general/latest/gr/rande.html)”。 + For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation. - - AWS S3 Bucket:S3 Bucket 的名称,专用于 {% data variables.product.prodname_registry %}。 - - AWS S3 访问密钥和 AWS S3 密钥:用于访问 Bucket 的 AWS 访问密钥 ID 和密钥 。 + - **AWS S3 Bucket:** The name of your S3 bucket dedicated to {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key to access your bucket. - 有关管理 AWS 访问密钥的详细信息,请参阅“[AWS 标识和访问管理文档](https://docs.aws.amazon.com/iam/index.html)”。 + For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." - ![S3 AWS Bucket 详细信息的输入框](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) {% endif %} {% data reusables.enterprise_management_console.save-settings %} + ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) +{% endif %} +{% data reusables.enterprise_management_console.save-settings %} -## 后续步骤 +## Next steps {% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/zh-CN/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/zh-CN/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md index f70e98510c..a1a74dd1f4 100644 --- a/translations/zh-CN/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md +++ b/translations/zh-CN/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md @@ -1,6 +1,6 @@ --- -title: 使用 Azure Blob 存储启用 GitHub Packages -intro: '以 Azure Blob 存储作为外部存储设置 {% data variables.product.prodname_registry %} 。' +title: Enabling GitHub Packages with Azure Blob Storage +intro: 'Set up {% data variables.product.prodname_registry %} with Azure Blob Storage as your external storage.' versions: ghes: '*' type: tutorial @@ -9,41 +9,39 @@ topics: - Packages - Storage shortTitle: Enable Packages with Azure -ms.openlocfilehash: ff9f7cc0e001a639cf5222ade02a6dabd57a3c47 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145099930' --- + {% warning %} -警告: -- 为存储桶设置所需的限制性访问策略至关重要,因为 {% data variables.product.company_short %} 不会将特定对象权限或其他访问控制列表 (ACL) 应用于存储桶配置。 例如,如果将存储桶设为公共,则在公共互联网上可以访问存储桶中的数据。 -- 我们建议对 {% data variables.product.prodname_registry %} 使用专用存储桶,与用于 {% data variables.product.prodname_actions %} 存储的存储桶分开。 -- 请确保配置将来要使用的存储桶。 在开始使用 {% data variables.product.prodname_registry %} 后,我们不建议更改存储系统。 +**Warnings:** +- It is critical that you set the restrictive access policies you need for your storage bucket, because {% data variables.product.company_short %} does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible on the public internet. +- We recommend using a dedicated bucket for {% data variables.product.prodname_registry %}, separate from the bucket you use for {% data variables.product.prodname_actions %} storage. +- Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}. {% endwarning %} -## 先决条件 +## Prerequisites -在 {% data variables.product.product_location_enterprise %} 上启用和配置 {% data variables.product.prodname_registry %} 之前,您必须准备 Azure Blob 桶。 若要准备 Azure Blob 存储 Bucket,建议查阅官方 [Azure Blob 存储文档站点](https://docs.microsoft.com/en-us/azure/storage/blobs/)上的官方 Azure Blob 存储文档。 +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your Azure Blob storage bucket. To prepare your Azure Blob storage bucket, we recommend consulting the official Azure Blob storage docs at the official [Azure Blob Storage documentation site](https://docs.microsoft.com/en-us/azure/storage/blobs/). -## 使用 Azure Blob 存储启用 {% data variables.product.prodname_registry %} +## Enabling {% data variables.product.prodname_registry %} with Azure Blob Storage -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %} -1. 在“包存储”下,选择“Azure Blob 存储”,然后为包存储 Bucket 和连接字符串输入 Azure 容器名称。 - ![Azure Blob 存储容器名称和连接字符串框](/assets/images/help/package-registry/azure-blob-storage-settings.png) +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} +1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string. + ![Azure Blob storage container name and connection string boxes](/assets/images/help/package-registry/azure-blob-storage-settings.png) {% note %} - 注意:可以通过导航到 Azure 存储帐户中的“访问密钥”菜单来查找 Azure 连接字符串。 - 目前不支持使用 SAS 令牌或 SAS URL 作为连接字符串。 + **Note:** You can find your Azure Connection String by navigating to the Access Key menu in your Azure storage account. + Usage of a SAS Token or SAS URL as connection string is not currently supported. {% endnote %} {% data reusables.enterprise_management_console.save-settings %} -## 后续步骤 +## Next steps {% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/zh-CN/content/admin/packages/enabling-github-packages-with-minio.md b/translations/zh-CN/content/admin/packages/enabling-github-packages-with-minio.md index 0140798e99..0fa9b47390 100644 --- a/translations/zh-CN/content/admin/packages/enabling-github-packages-with-minio.md +++ b/translations/zh-CN/content/admin/packages/enabling-github-packages-with-minio.md @@ -1,6 +1,6 @@ --- -title: 使用 MinIO 启用 GitHub Packages -intro: '以 MinIO 作为外部存储设置 {% data variables.product.prodname_registry %} 。' +title: Enabling GitHub Packages with MinIO +intro: 'Set up {% data variables.product.prodname_registry %} with MinIO as your external storage.' versions: ghes: '*' type: tutorial @@ -9,27 +9,22 @@ topics: - Packages - Storage shortTitle: Enable Packages with MinIO -ms.openlocfilehash: 2e7d76ee696dfbcd2369c577ef2d2ee803a09638 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145099001' --- + {% warning %} -警告: -- 为存储桶设置所需的限制性访问策略至关重要,因为 {% data variables.product.company_short %} 不会将特定对象权限或其他访问控制列表 (ACL) 应用于存储桶配置。 例如,如果将存储桶设为公共,则在公共互联网上可以访问存储桶中的数据。 -- 我们建议对 {% data variables.product.prodname_registry %} 使用专用存储桶,与用于 {% data variables.product.prodname_actions %} 存储的存储桶分开。 -- 请确保配置将来要使用的存储桶。 在开始使用 {% data variables.product.prodname_registry %} 后,我们不建议更改存储系统。 +**Warnings:** +- It is critical that you set the restrictive access policies you need for your storage bucket, because {% data variables.product.company_short %} does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible on the public internet. +- We recommend using a dedicated bucket for {% data variables.product.prodname_registry %}, separate from the bucket you use for {% data variables.product.prodname_actions %} storage. +- Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}. {% endwarning %} -## 先决条件 +## Prerequisites -在 {% data variables.product.product_location_enterprise %} 上启用和配置 {% data variables.product.prodname_registry %} 之前,您必须准备 MinIO 存储桶。 若要帮助快速设置 MinIO Bucket 并浏览 MinIO 的自定义选项,请参阅“[为 {% data variables.product.prodname_registry %} 配置 MinIO 存储 Bucket 快速入门](/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages)”。 +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your MinIO storage bucket. To help you quickly set up a MinIO bucket and navigate MinIO's customization options, see the "[Quickstart for configuring your MinIO storage bucket for {% data variables.product.prodname_registry %}](/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages)." -确保您的 MinIO 外部存储访问密钥 ID 和密码具有以下权限: +Ensure your MinIO external storage access key ID and secret have these permissions: - `s3:PutObject` - `s3:GetObject` - `s3:ListBucketMultipartUploads` @@ -38,21 +33,26 @@ ms.locfileid: '145099001' - `s3:DeleteObject` - `s3:ListBucket` -## 使用 MinIO 外部存储启用 {% data variables.product.prodname_registry %} +## Enabling {% data variables.product.prodname_registry %} with MinIO external storage -虽然 MinIO 目前没有出现在“封装存储”下的用户界面中,MinIO 在 {% data variables.product.prodname_enterprise %} 上仍然受 {% data variables.product.prodname_registry %} 支持。 另请注意,MinIO 的对象存储与 S3 API 兼容,您可以输入MinIO 存储桶详细信息代替 AWS S3 详细信息。 +Although MinIO does not currently appear in the user interface under "Package Storage", MinIO is still supported by {% data variables.product.prodname_registry %} on {% data variables.product.prodname_enterprise %}. Also, note that MinIO's object storage is compatible with the S3 API and you can enter MinIO's bucket details in place of AWS S3 details. -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_site_admin_settings.packages-tab %} +{% data reusables.package_registry.enable-enterprise-github-packages %} {% ifversion ghes %} -1. 在“包存储”下,选择“Amazon S3”。 -1. 在 AWS 存储设置中输入 MinIO 存储桶的详细信息。 - - AWS 服务 URL:MinIO Bucket 的托管 URL。 - - AWS S3 Bucket:与 S3 兼容的 MinIO Bucket 的名称,专用于 {% data variables.product.prodname_registry %}。 - - AWS S3 访问密钥和 AWS S3 密钥:输入用于访问 Bucket 的 MinIO 访问密钥 ID 和密钥 。 +1. Under "Packages Storage", select **Amazon S3**. +1. Enter your MinIO storage bucket's details in the AWS storage settings. + - **AWS Service URL:** The hosting URL for your MinIO bucket. + - **AWS S3 Bucket:** The name of your S3-compatible MinIO bucket dedicated to {% data variables.product.prodname_registry %}. + - **AWS S3 Access Key** and **AWS S3 Secret Key**: Enter the MinIO access key ID and secret key to access your bucket. - ![S3 AWS Bucket 详细信息的输入框](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) {% endif %} {% data reusables.enterprise_management_console.save-settings %} + ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png) +{% endif %} +{% data reusables.enterprise_management_console.save-settings %} -## 后续步骤 +## Next steps {% data reusables.package_registry.next-steps-for-packages-enterprise-setup %} diff --git a/translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md index a8e56c1ad2..43a79f9653 100644 --- a/translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: 企业 GitHub Packages 使用入门 +title: Getting started with GitHub Packages for your enterprise shortTitle: Getting started with GitHub Packages -intro: '您可以通过启用功能、配置第三方存储、配置您想要支持的生态系统以及更新您的 TLS 证书,开始在 {% data variables.product.product_location %} 上使用 {% data variables.product.prodname_registry %}。' +intro: 'You can start using {% data variables.product.prodname_registry %} on {% data variables.location.product_location %} by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate.' redirect_from: - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise - /admin/packages/enabling-github-packages-for-your-enterprise @@ -11,46 +11,42 @@ type: how_to topics: - Enterprise - Packages -ms.openlocfilehash: 2389eba768a8b2f865165b43dde0e1b6381c6ae7 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '146199960' --- + + {% data reusables.package_registry.packages-cluster-support %} -## 步骤 1:检查 {% data variables.product.prodname_registry %} 是否可用于您的企业 +## Step 1: Check whether {% data variables.product.prodname_registry %} is available for your enterprise -{% data variables.product.prodname_registry %} 在 {% data variables.product.prodname_ghe_server %} 3.0 或更高版本中可用。 如果您使用的是早期版本的 {% data variables.product.prodname_ghe_server %},则必须升级才能使用 {% data variables.product.prodname_registry %}。 有关升级 {% data variables.product.prodname_ghe_server %} 实例的详细信息,请参阅“[关于升级到新版本](/admin/overview/about-upgrades-to-new-releases)”。 -## 步骤 2:启用 {% data variables.product.prodname_registry %} 并配置外部存储 +{% data variables.product.prodname_registry %} is available in {% data variables.product.prodname_ghe_server %} 3.0 or higher. If you're using an earlier version of {% data variables.product.prodname_ghe_server %}, you'll have to upgrade to use {% data variables.product.prodname_registry %}. For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)." +## Step 2: Enable {% data variables.product.prodname_registry %} and configure external storage -{% data variables.product.prodname_ghe_server %} 上的 {% data variables.product.prodname_registry %} 使用外部 Blob 存储来存储您的软件包。 +{% data variables.product.prodname_registry %} on {% data variables.product.prodname_ghe_server %} uses external blob storage to store your packages. -在为 {% data variables.product.product_location %} 启用 {% data variables.product.prodname_registry %} 后,需要准备您的第三方存储桶。 所需的存储量取决于您对 {% data variables.product.prodname_registry %} 的使用,且设置指南可能因存储提供商而异。 +After enabling {% data variables.product.prodname_registry %} for {% data variables.location.product_location %}, you'll need to prepare your third-party storage bucket. The amount of storage required depends on your usage of {% data variables.product.prodname_registry %}, and the setup guidelines can vary by storage provider. -支持的外部存储提供商 +Supported external storage providers - Amazon Web Services (AWS) S3 {% ifversion ghes %} - Azure Blob Storage {% endif %} - MinIO -要启用 {% data variables.product.prodname_registry %} 并配置第三方存储,请参阅: - - [使用 AWS 启用 GitHub 包](/admin/packages/enabling-github-packages-with-aws){% ifversion ghes %} - - [使用 Azure Blob 存储启用 GitHub 包](/admin/packages/enabling-github-packages-with-azure-blob-storage){% endif %} - - [使用 MinIO 启用 GitHub Packages](/admin/packages/enabling-github-packages-with-minio) +To enable {% data variables.product.prodname_registry %} and configure third-party storage, see: + - "[Enabling GitHub Packages with AWS](/admin/packages/enabling-github-packages-with-aws)"{% ifversion ghes %} + - "[Enabling GitHub Packages with Azure Blob Storage](/admin/packages/enabling-github-packages-with-azure-blob-storage)"{% endif %} + - "[Enabling GitHub Packages with MinIO](/admin/packages/enabling-github-packages-with-minio)" -## 步骤 3:指定包生态系统以支持实例 +## Step 3: Specify the package ecosystems to support on your instance -选择您要在 {% data variables.product.product_location %} 上启用、禁用或设置为只读的包生态系统。 可用选项包括 {% ifversion ghes > 3.4 %}{% data variables.product.prodname_container_registry %}、{% endif %}Docker、RubyGems、npm、Apache Maven、Gradle 或 NuGet。 有关详细信息,请参阅“[为企业配置包生态系统支持](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)”。 +Choose which package ecosystems you'd like to enable, disable, or set to read-only on {% data variables.location.product_location %}. Available options are {% ifversion ghes > 3.4 %}{% data variables.product.prodname_container_registry %}, {% endif %}Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. For more information, see "[Configuring package ecosystem support for your enterprise](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." -## 步骤 4:如果需要,请确保具有包主机 URL 的 TLS 证书 +## Step 4: Ensure you have a TLS certificate for your package host URL, if needed -如果为 {% data variables.product.product_location %} 启用了子域隔离,则需要创建并上传 TLS 证书,该证书允许要使用的每个生态系统的包主机 URL,例如 `{% data reusables.package_registry.container-registry-hostname %}`。 确保每个包主机 URL 包含 `https://`。 +If subdomain isolation is enabled for {% data variables.location.product_location %}, you will need to create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as `{% data reusables.package_registry.container-registry-hostname %}`. Make sure each package host URL includes `https://`. - 可以手动创建证书,也可以使用“让我们加密”。 如果已经使用“让我们加密”,必须在启用 {% data variables.product.prodname_registry %} 后申请新的 TLS 证书。 有关包主机 URL 的详细信息,请参阅“[启用子域隔离](/enterprise/admin/configuration/enabling-subdomain-isolation)”。 有关将 TLS 证书上传到 {% data variables.product.product_name %} 的详细信息,请参阅“[配置 TLS](/enterprise/admin/configuration/configuring-tls)”。 + You can create the certificate manually, or you can use _Let's Encrypt_. If you already use _Let's Encrypt_, you must request a new TLS certificate after enabling {% data variables.product.prodname_registry %}. For more information about package host URLs, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)." For more information about uploading TLS certificates to {% data variables.product.product_name %}, see "[Configuring TLS](/enterprise/admin/configuration/configuring-tls)." -## 步骤 5:检查并重命名保留名称 +## Step 5: Check for and rename reserved names -如果要在禁用子域隔离的情况下使用 Docker 生态系统,必须先重命名 {% data variables.product.product_location %} 上名为 `v2` 的任何用户或组织,然后才能在 {% data variables.enterprise.management_console %} 中启用 Docker 生态系统支持。 Docker 使用 `v2` 帐户名称来管理与 Docker API 的路径冲突;启用 Docker 注册表支持后,将无法再使用此名称。 +If you want to use the Docker ecosystem with subdomain isolation disabled, you **must** first rename any user or organization named `v2` on {% data variables.location.product_location %}, prior to enabling Docker ecosystem support in the {% data variables.enterprise.management_console %}. Docker uses a `v2` account name to manage path conflicts with the Docker API, and once Docker registry support is enabled, you won't be able to use this name anymore. -可导航到站点管理仪表板中的“保留登录名”页来查看已保留供内部使用的登录名完整列表。 有关详细信息,请参阅“[保留登录名](/admin/configuration/configuring-your-enterprise/site-admin-dashboard#reserved-logins)”。 +You can view a full list of logins reserved for internal use by navigating to the "Reserved logins" page in the Site admin dashboard. For more information, see "[Reserved logins](/admin/configuration/configuring-your-enterprise/site-admin-dashboard#reserved-logins)." diff --git a/translations/zh-CN/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md b/translations/zh-CN/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md index 1ab4d31eaa..9305406cc8 100644 --- a/translations/zh-CN/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md +++ b/translations/zh-CN/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md @@ -1,78 +1,77 @@ --- -title: 将企业从 Docker 注册表迁移到容器注册表 -intro: '可以将先前存储在 {% data variables.product.product_location %} 上的 Docker 注册表中的 Docker 映像迁移到 {% data variables.product.prodname_container_registry %}。' +title: Migrating your enterprise to the Container registry from the Docker registry +intro: 'You can migrate Docker images previously stored in the Docker registry on {% data variables.location.product_location %} to the {% data variables.product.prodname_container_registry %}.' product: '{% data reusables.gated-features.packages %}' -permissions: 'Enterprise owners can migrate Docker images to the {% data variables.product.prodname_container_registry %}.' +permissions: "Enterprise owners can migrate Docker images to the {% data variables.product.prodname_container_registry %}." versions: - feature: docker-ghcr-enterprise-migration + feature: 'docker-ghcr-enterprise-migration' shortTitle: Migrate to Container registry topics: - Containers - Docker - Migration -ms.openlocfilehash: b4fd99bad9d9ae68354d01a9bd80ebec89e0918b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147578664' --- + {% data reusables.package_registry.container-registry-ghes-beta %} -## 关于 {% data variables.product.prodname_container_registry %} +## About the {% data variables.product.prodname_container_registry %} -{% data reusables.package_registry.container-registry-benefits %}有关详细信息,请参阅“[使用 {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)”。 +{% data reusables.package_registry.container-registry-benefits %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)." -有关配置 {% data variables.product.product_location %} 的 {% data variables.product.prodname_registry %} 的详细信息,请参阅“[企业的 {% data variables.product.prodname_registry %} 使用入门](/admin/packages/getting-started-with-github-packages-for-your-enterprise)”。 +For more information about configuring {% data variables.product.prodname_registry %} for {% data variables.location.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." -## 关于从 Docker 注册表迁移 +## About migration from the Docker registry -{% data reusables.package_registry.container-registry-replaces-docker-registry %}如果 {% data variables.product.product_location %} 上的 Docker 注册表包含映像,则必须手动将映像迁移到 {% data variables.product.prodname_container_registry %}。 +{% data reusables.package_registry.container-registry-replaces-docker-registry %} If the Docker registry on {% data variables.location.product_location %} contains images, you must manually migrate the images to the {% data variables.product.prodname_container_registry %}. {% ifversion ghes %} {% note %} -注意:{% data reusables.package_registry.container-registry-ghes-migration-availability %} +**Note**: {% data reusables.package_registry.container-registry-ghes-migration-availability %} {% endnote %} {% endif %} -{% data reusables.package_registry.container-registry-migration-namespaces %}有关迁移到 {% data variables.product.prodname_container_registry %} 的影响的详细信息,请参阅“[从 Docker 注册表迁移到 {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry#about-migration-from-the-docker-registry)”。 +{% data reusables.package_registry.container-registry-migration-namespaces %} For more information about the impact of migration to the {% data variables.product.prodname_container_registry %}, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry#about-migration-from-the-docker-registry)." -## 将组织迁移到 {% data variables.product.prodname_container_registry %} +## Migrating organizations to the {% data variables.product.prodname_container_registry %} -可以开始将组织的所有 Docker 映像迁移到 {% data variables.product.prodname_container_registry %}。 迁移操作的持续时间取决于要迁移的映像总数和{% ifversion ghes %}实例{% elsif ghae %}{% data variables.product.product_name %}{% endif %}上的总体负载。 成功迁移后,{% data variables.product.product_name %} 将显示摘要,以后所有 Docker 映像的上传都将使用 {% data variables.product.prodname_container_registry %}。 +You can start a migration of all your organizations' Docker images to the {% data variables.product.prodname_container_registry %}. The duration of the migration operation depends on the total number of images to migrate, and the overall load on {% ifversion ghes %}your instance{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. After a successful migration, {% data variables.product.product_name %} will display a summary, and all future uploads of Docker images will use the {% data variables.product.prodname_container_registry %}. -如果{% ifversion ghes %}站点管理员{% elsif ghae %}和企业所有者{% endif %}为{% data variables.product.product_location %}配置了电子邮件通知,则将在迁移完成后收到一封电子邮件。 有关详细信息,请参阅“[配置邮件通知](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)”。 +If {% ifversion ghes %}a site administrator{% elsif ghae %}an enterprise owner{% endif %} has configured email notifications for {% data variables.location.product_location %}, you will receive an email after the migration is complete. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)." {% note %} -{% ifversion ghes %}注意{% elsif ghae %}注意{% endif %}: +**{% ifversion ghes %}Notes{% elsif ghae %}Note{% endif %}**: {%- ifversion ghes %} -- 在迁移过程中,实例的 CPU 和内存使用率将会增加。 为确保用户的实例性能,{% data variables.product.company_short %} 建议在活动减少期间开始迁移。 -{%- endif %} {% ifversion ghes %}- {% endif %}在迁移过程中,请勿修改企业的设置{% ifversion ghes %}或从管理 SSH 会话运行 `ghe-config-apply`{% endif %}。 {% ifversion ghes %}这些操作将触发配置运行,从而可以重启服务和{% elsif ghae %}。如果修改这些设置,{% endif %} 可能会中断迁移。 +- During the migration, the CPU and memory usage for your instance will increase. To ensure the performance of the instance for your users, {% data variables.product.company_short %} recommends that you begin a migration during a period of reduced activity. +{%- endif %} +{% ifversion ghes %}- {% endif %}During the migration, do not modify settings for your enterprise{% ifversion ghes %} or run `ghe-config-apply` from an administrative SSH session{% endif %}. {% ifversion ghes %}These actions will trigger a configuration run, which can restart services and {% elsif ghae %}Modifying these settings {% endif %} may interrupt the migration. {%- ifversion ghes %} -- 迁移后,由于 Docker 注册表和 {% data variables.product.prodname_container_registry %} 中的映像文件重复,因此实例的存储压力将会增加。 {% data variables.product.product_name %} 的未来版本将在所有迁移完成后删除重复的文件。 +- After the migration, storage pressure on your instance will increase due to the duplication of image files in the Docker registry and the {% data variables.product.prodname_container_registry %}. A future release of {% data variables.product.product_name %} will remove the duplicated files when all migrations are complete. -有关监视 {% data variables.product.product_location %} 的性能和存储的详细信息,请参阅“[访问监视仪表板](/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard)”。 +For more information about monitoring the performance and storage of {% data variables.location.product_location %}, see "[Accessing the monitor dashboard](/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard)." {% endif %} {% endnote %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} -1. 在左侧边栏中,单击“包”。 -1. 在要迁移的包数量的右侧,单击“开始迁移”。 在迁移过程中,{% data variables.product.product_name %} 将在此页上显示进度。 +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +1. In the left sidebar, click **Packages**. +1. To the right of the number of packages to migrate, click **Start migration**. During the migration, {% data variables.product.product_name %} will display progress on this page. -迁移完成后,该页将显示结果。 如果迁移失败,该页将显示拥有导致失败的包的组织。 +After the migration completes, the page will display the results. If a migration fails, the page will show the organizations that own the package that caused the failure. -## 重新运行失败的组织迁移 +## Re-running a failed organization migration -在迁移之前,如果用户在 {% data variables.product.prodname_container_registry %} 中创建了与 Docker 注册表中的现有包同名的包,则迁移将失败。 +Prior to migration, if a user has created a package in the {% data variables.product.prodname_container_registry %} that has an identical name to an existing package in the Docker registry, the migration will fail. -1. 删除 {% data variables.product.prodname_container_registry %} 中受影响的容器。 有关详细信息,请参阅“[删除和还原包](/packages/learn-github-packages/deleting-and-restoring-a-package#deleting-a-version-of-an-organization-scoped-package-on-github)”。 -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.packages-tab %} -1. 在要迁移的包数量的右侧,单击“重新开始迁移”。 在迁移过程中,{% data variables.product.product_name %} 将在此页上显示进度。 -1. 如果迁移再次失败,请从步骤 1 开始并重新运行迁移。 +1. Delete the affected container in the {% data variables.product.prodname_container_registry %}. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package#deleting-a-version-of-an-organization-scoped-package-on-github)." +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.packages-tab %} +1. To the right of the number of packages to migrate, click **Re-run migration**. During the migration, {% data variables.product.product_name %} will display progress on this page. +1. If the migration fails again, start from step 1 and re-run the migration. diff --git a/translations/zh-CN/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/zh-CN/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md index bba99360b5..443b6038e1 100644 --- a/translations/zh-CN/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md +++ b/translations/zh-CN/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md @@ -1,6 +1,6 @@ --- -title: 为 GitHub Packages 配置 MinIO 存储桶的快速入门 -intro: '配置您的自定义 MinIO 存储桶,用于 {% data variables.product.prodname_registry %}。' +title: Quickstart for configuring your MinIO storage bucket for GitHub Packages +intro: 'Configure your custom MinIO storage bucket for use with {% data variables.product.prodname_registry %}.' versions: ghes: '*' type: quick_start @@ -9,57 +9,52 @@ topics: - Enterprise - Storage shortTitle: Quickstart for MinIO -ms.openlocfilehash: 5e3da768643c3979380d3fb205518a7053c7360b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146688971' --- + {% data reusables.package_registry.packages-ghes-release-stage %} -在 {% data variables.product.product_location_enterprise %} 上启用和配置 {% data variables.product.prodname_registry %} 之前,您必须准备第三方存储解决方案。 +Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your third-party storage solution. -MinIO 在企业上提供对象存储并支持 S3 API 和 {% data variables.product.prodname_registry %}。 +MinIO offers object storage with support for the S3 API and {% data variables.product.prodname_registry %} on your enterprise. -此快速入门将演示如何使用 Docker 设置 MinIO 以与 {% data variables.product.prodname_registry %} 使用,但除了 Docker 之外,您还有其他用于管理 MinIO 的选项。 有关 MinIO 的详细信息,请参阅官方 [MinIO 文档](https://docs.min.io/)。 +This quickstart shows you how to set up MinIO using Docker for use with {% data variables.product.prodname_registry %} but you have other options for managing MinIO besides Docker. For more information about MinIO, see the official [MinIO docs](https://docs.min.io/). -## 1. 根据需求选择 MinIO 模式 +## 1. Choose a MinIO mode for your needs -| MinIO 模式 | 优化对象 | 需要存储基础架构 | +| MinIO mode | Optimized for | Storage infrastructure required | |----|----|----| -| 独立 MinIO(在单个主机上) | 快速设置 | 空值 | -| MinIO 作为 NAS 网关 | NAS(网络连接存储)| NAS 设备 | -| 群集式 MinIO(也称为分布式 MinIO)| 数据安全性 | 在群集中运行的存储服务器 | +| Standalone MinIO (on a single host) | Fast setup | N/A | +| MinIO as a NAS gateway | NAS (Network-attached storage)| NAS devices | +| Clustered MinIO (also called Distributed MinIO)| Data security | Storage servers running in a cluster | -有关选项的详细信息,请参阅官方 [MinIO 文档](https://docs.min.io/)。 +For more information about your options, see the official [MinIO docs](https://docs.min.io/). {% warning %} -警告:MinIO 已宣布删除 MinIO 网关。 从 2022 年 6 月 1 日起,当前 MinIO NAS 网关实施的支持和 Bug 修复将仅通过其 LTS 支持合同提供给付费客户。 如果要继续使用 MinIO 网关与 {% data variables.product.prodname_registry %},我们建议转向 MinIO LTS 支持。 有关详细信息,请参阅[计划删除 minio/minio 存储库中的适用于 GCS、Azure 和 HDFS 的 MinIO 网格](https://github.com/minio/minio/issues/14331)。 +**Warning**: MinIO has announced removal of MinIO Gateways. Starting June 1st, 2022, support and bug fixes for the current MinIO NAS Gateway implementation will only be available for paid customers via their LTS support contract. If you want to continue using MinIO Gateways with {% data variables.product.prodname_registry %}, we recommend moving to MinIO LTS support. For more information, see [Scheduled removal of MinIO Gateway for GCS, Azure, HDFS](https://github.com/minio/minio/issues/14331) in the minio/minio repository. -其他 MinIO 模式在标准支持下仍然可用。 +Other modes of MinIO remain available with standard support. {% endwarning %} -## 2. 安装、运行和登录到 MinIO +## 2. Install, run, and sign in to MinIO -1. 为 MinIO 设置首选环境变量。 +1. Set up your preferred environment variables for MinIO. - 这些示例使用 `MINIO_DIR`: + These examples use `MINIO_DIR`: ```shell $ export MINIO_DIR=$(pwd)/minio $ mkdir -p $MINIO_DIR ``` -2. 安装 MinIO。 +2. Install MinIO. ```shell $ docker pull minio/minio ``` - 有关详细信息,请参阅官方“[MinIO 快速入门指南](https://docs.min.io/docs/minio-quickstart-guide)”。 + For more information, see the official "[MinIO Quickstart Guide](https://docs.min.io/docs/minio-quickstart-guide)." -3. 使用您的 MinIO 访问密钥登录 MinIO。 +3. Sign in to MinIO using your MinIO access key and secret. {% linux %} ```shell @@ -77,16 +72,16 @@ MinIO 在企业上提供对象存储并支持 S3 API 和 {% data variables.produ ``` {% endmac %} - 您可以使用环境变量访问 MinIO 密钥: + You can access your MinIO keys using the environment variables: ```shell $ echo $MINIO_ACCESS_KEY $ echo $MINIO_SECRET_KEY ``` -4. 在您选择的模式下运行 MinIO。 +4. Run MinIO in your chosen mode. - * 在单一主机上使用 Docker 运行 MinIO: + * Run MinIO using Docker on a single host: ```shell $ docker run -p 9000:9000 \ @@ -96,11 +91,11 @@ MinIO 在企业上提供对象存储并支持 S3 API 和 {% data variables.produ minio/minio server /data ``` - 有关详细信息,请参阅“[MinIO Docker 快速入门指南](https://docs.min.io/docs/minio-docker-quickstart-guide.html)”。 + For more information, see "[MinIO Docker Quickstart guide](https://docs.min.io/docs/minio-docker-quickstart-guide.html)." - * 使用 Docker 作为 NAS 网关运行 MinIO: + * Run MinIO using Docker as a NAS gateway: - 此设置对于已经有 NAS 用作 {% data variables.product.prodname_registry %} 的备份存储的部署非常有用。 + This setup is useful for deployments where there is already a NAS you want to use as the backup storage for {% data variables.product.prodname_registry %}. ```shell $ docker run -p 9000:9000 \ @@ -110,40 +105,40 @@ MinIO 在企业上提供对象存储并支持 S3 API 和 {% data variables.produ minio/minio gateway nas /data ``` - * 使用 Docker 作为集群运行 MinIO: 此 MinIO 部署使用多个主机和 MinIO 的擦除编码来提供最强的数据保护。 若要在群集模式下运行 MinIO,请参阅“[分布式 MinIO 快速入门指南](https://docs.min.io/docs/distributed-minio-quickstart-guide.html)”。 + * Run MinIO using Docker as a cluster. This MinIO deployment uses several hosts and MinIO's erasure coding for the strongest data protection. To run MinIO in a cluster mode, see the "[Distributed MinIO Quickstart Guide](https://docs.min.io/docs/distributed-minio-quickstart-guide.html)." -## 3. 为 {% data variables.product.prodname_registry %} 创建 MinIO 存储桶 +## 3. Create your MinIO bucket for {% data variables.product.prodname_registry %} -1. 安装 MinIO 客户端。 +1. Install the MinIO client. ```shell $ docker pull minio/mc ``` -2. 使用 {% data variables.product.prodname_ghe_server %} 可以访问的主机 URL 创建存储桶。 +2. Create a bucket with a host URL that {% data variables.product.prodname_ghe_server %} can access. - * 本地部署示例: + * Local deployments example: ```shell $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @localhost:9000" - $ docker run minio/mc BUCKET-NAME + $ docker run minio/mc BUCKET-NAME ``` - 此示例可用于 MinIO 单机版或作为 NAS 网关的 MinIO。 + This example can be used for MinIO standalone or MinIO as a NAS gateway. - * 集群部署示例: + * Clustered deployments example: ```shell $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @minioclustername.example.com:9000" $ docker run minio/mc mb packages ``` -## 后续步骤 +## Next steps -要完成 {% data variables.product.prodname_registry %} 的存储配置,您需要复制 MinIO 存储 URL: +To finish configuring storage for {% data variables.product.prodname_registry %}, you'll need to copy the MinIO storage URL: ``` echo "http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY}@minioclustername.example.com:9000" ``` -有关后续步骤,请参阅“[使用 MinIO 启用 {% data variables.product.prodname_registry %}](/admin/packages/enabling-github-packages-with-minio)”。 +For the next steps, see "[Enabling {% data variables.product.prodname_registry %} with MinIO](/admin/packages/enabling-github-packages-with-minio)." diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md index 419ba187fa..15cdbd6559 100644 --- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md +++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md @@ -1,6 +1,6 @@ --- -title: 关于企业策略 -intro: 使用企业策略,可以管理企业拥有的所有组织的策略。 +title: About enterprise policies +intro: 'With enterprise policies, you can manage the policies for all the organizations owned by your enterprise.' versions: ghec: '*' ghes: '*' @@ -9,26 +9,22 @@ type: overview topics: - Enterprise - Policies -ms.openlocfilehash: d452a6f24b3108b915e20b673ebd317a409ac8ae -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147718115' --- -为了帮助你实施业务规则和法规合规性,策略为企业帐户拥有的所有组织提供单个管理点。 + +To help you enforce business rules and regulatory compliance, policies provide a single point of management for all the organizations owned by an enterprise account. {% data reusables.enterprise.about-policies %} -例如,使用“基本权限”策略,可以允许组织所有者为其组织配置“基本权限”策略,也可以为企业中的所有组织强制实施特定的基本权限级别,例如“读取”。 +For example, with the "Base permissions" policy, you can allow organization owners to configure the "Base permissions" policy for their organization, or you can enforce a specific base permissions level, such as "Read", for all organizations within the enterprise. -默认情况下,不会强制实施企业策略。 要确定应强制实施以满足业务独特需求的策略,建议从存储库管理策略开始,查看企业帐户中所有可用的策略。 有关详细信息,请参阅“[在企业中强制实施存储库管理策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)”。 +By default, no enterprise policies are enforced. To identify policies that should be enforced to meet the unique requirements of your business, we recommend reviewing all the available policies in your enterprise account, starting with repository management policies. For more information, see "[Enforcing repository management polices in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)." -配置企业策略时,如需了解更改每个策略所产生的影响,可以查看企业拥有的组织的当前配置。 +While you're configuring enterprise policies, to help you understand the impact of changing each policy, you can view the current configurations for the organizations owned by your enterprise. -{% ifversion ghes %} 在企业中强制实施标准的另一种方法是使用预接收挂钩(即在 {% data variables.product.product_location %} 上运行的脚本)来实现质量检查。 有关详细信息,请参阅“[使用预接收挂钩强制实施策略](/admin/policies/enforcing-policy-with-pre-receive-hooks)”。 +{% ifversion ghes %} +Another way to enforce standards within your enterprise is to use pre-receive hooks, which are scripts that run on {% data variables.location.product_location %} to implement quality checks. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)." {% endif %} -## 延伸阅读 +## Further reading -- “[关于企业帐户](/admin/overview/about-enterprise-accounts)” +- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)" diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md index 573f4583b1..82c8463b34 100644 --- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md +++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md @@ -32,7 +32,7 @@ shortTitle: GitHub Actions policies {% data variables.product.prodname_actions %} helps members of your enterprise automate software development workflows on {% data variables.product.product_name %}. For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)." -{% ifversion ghes %}If you enable {% data variables.product.prodname_actions %}, any{% else %}Any{% endif %} organization on {% data variables.product.product_location %} can use {% data variables.product.prodname_actions %}. You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} use {% data variables.product.prodname_actions %}. By default, organization owners can manage how members use {% data variables.product.prodname_actions %}. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)." +{% ifversion ghes %}If you enable {% data variables.product.prodname_actions %}, any{% else %}Any{% endif %} organization on {% data variables.location.product_location %} can use {% data variables.product.prodname_actions %}. You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} use {% data variables.product.prodname_actions %}. By default, organization owners can manage how members use {% data variables.product.prodname_actions %}. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)." ## Enforcing a policy to restrict the use of {% data variables.product.prodname_actions %} in your enterprise @@ -48,7 +48,7 @@ You can choose to disable {% data variables.product.prodname_actions %} for all {%- ifversion ghes or ghae %} {% note %} - **Note:** To enable access to public actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %}, you must first configure {% data variables.product.product_location %} to connect to {% data variables.product.prodname_dotcom_the_website %}. 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)." + **Note:** To enable access to public actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %}, you must first configure {% data variables.location.product_location %} to connect to {% data variables.product.prodname_dotcom_the_website %}. 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)." {% endnote %} {%- endif %} @@ -86,7 +86,7 @@ You can choose to disable {% data variables.product.prodname_actions %} for all ## Enforcing a policy for fork pull requests in your enterprise -You can enforce policies to control how {% data variables.product.prodname_actions %} behaves for {% data variables.product.product_location %} when members of your enterprise{% ifversion ghec %} or outside collaborators{% endif %} run workflows from forks. +You can enforce policies to control how {% data variables.product.prodname_actions %} behaves for {% data variables.location.product_location %} when members of your enterprise{% ifversion ghec %} or outside collaborators{% endif %} run workflows from forks. {% ifversion ghec %} diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md index 8a3ff71aa6..bedf7001c2 100644 --- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md +++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md @@ -183,7 +183,7 @@ To prevent confusion from your developers, you can change this behavior so that {% note %} -**Note:** If a user is signed in to their personal account when they attempt to access any of your enterprise's resources, they'll be automatically signed out and redirected to SSO to sign in to their {% data variables.product.prodname_managed_user %}. For more information, see "[Managing multiple accounts](/enterprise-cloud@latest/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)." +**Note:** If a user is signed in to their personal account when they attempt to access any of your enterprise's resources, they'll be automatically signed out and redirected to SSO to sign in to their {% data variables.enterprise.prodname_managed_user %}. For more information, see "[Managing multiple accounts](/enterprise-cloud@latest/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)." {% endnote %} diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md index 5ec3ef3506..991873cdca 100644 --- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md +++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md @@ -304,7 +304,7 @@ You can override the default inherited settings by configuring the settings for {% data reusables.enterprise_user_management.disclaimer-for-git-read-access %} -If you have [enabled private mode](/enterprise/admin/configuration/enabling-private-mode) for {% data variables.product.product_location %}, you can allow repository administrators to enable anonymous Git read access to public repositories. +If you have [enabled private mode](/enterprise/admin/configuration/enabling-private-mode) for {% data variables.location.product_location %}, you can allow repository administrators to enable anonymous Git read access to public repositories. Enabling anonymous Git read access allows users to bypass authentication for custom tools on your enterprise. When you or a repository administrator enable this access setting for a repository, unauthenticated Git operations (and anyone with network access to {% data variables.product.product_name %}) will have read access to the repository without authentication. diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/index.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/index.md index 8ef7185208..1e3ed27454 100644 --- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/index.md +++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/index.md @@ -22,6 +22,7 @@ children: - /enforcing-policies-for-dependency-insights-in-your-enterprise - /enforcing-policies-for-github-actions-in-your-enterprise - /enforcing-policies-for-code-security-and-analysis-for-your-enterprise + - /enforcing-policies-for-personal-access-tokens-in-your-enterprise shortTitle: Enforce policies ms.openlocfilehash: 045831c9b6e9632db2f7743f2cf30d965ee3c327 ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 diff --git a/translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md b/translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md index a7fea3de74..d72c609a0d 100644 --- a/translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md +++ b/translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md @@ -1,6 +1,6 @@ --- -title: 关于预接收挂钩 -intro: '预接收挂钩是在 {% data variables.product.prodname_ghe_server %} 设备上运行的脚本,可用于实施质量检查。' +title: About pre-receive hooks +intro: '*Pre-receive hooks* are scripts that run on the {% data variables.product.prodname_ghe_server %} appliance that you can use to implement quality checks.' redirect_from: - /enterprise/admin/developer-workflow/about-pre-receive-hooks - /enterprise/admin/policies/about-pre-receive-hooks @@ -12,26 +12,20 @@ topics: - Enterprise - Policies - Pre-receive hooks -ms.openlocfilehash: a62d5391f9733c4a79ea8ba5d5f8f0d821d47d5c -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145098022' --- -当发生推送时,每个脚本都在隔离的环境中运行,并且可以对推送的内容执行检查。 如果 exit status 为 0,脚本将导致接受推送,如果 exit status 不为零,则会拒绝接受推送。 +When a push occurs, each script runs in an isolated environment and can perform checks on the content of the push. The scripts will cause the push to be accepted if the exit status is 0, or rejected if the exit status is non-zero. -## 使用方案 -使用预接收挂钩来满足业务规则、强制执行法规遵从性,并防止出现某些常见错误。 +## Usage scenarios +Use pre-receive hooks to satisfy business rules, enforce regulatory compliance, and prevent certain common mistakes. -如何使用预接收挂钩的示例: +Examples of how you can use pre-receive hooks: -- 需要提交消息来遵循特定的模式或格式,例如包括有效的事件单号或超过一定长度。 -- 通过拒绝所有推送来锁定分支或仓库。 -- 通过阻止关键词、模式或文件类型来防止将敏感数据添加到仓库。 -- 防止 PR 作者合并他们自己的更改。 +- Require commit messages to follow a specific pattern or format, such as including a valid ticket number or being over a certain length. +- Lock a branch or repository by rejecting all pushes. +- Prevent sensitive data from being added to the repository by blocking keywords, patterns or file types. +- Prevent a PR author from merging their own changes. -## 对性能和工作流程的影响 -对开发者及其工作流程的影响可能很大,因此必须谨慎考虑。 基于业务需求并经过深思熟虑实施的预接收挂钩将为整个组织带来最大好处。 +## Impact on performance and workflows +Impact to developers and their workflows can be significant and must be considered carefully. Pre-receive hooks that are based on business needs and implemented thoughtfully will provide the most benefit to the organization as a whole. -预接收挂钩可能会对 {% data variables.product.product_location %} 的性能产生意外影响,因此应谨慎实施和审查。 +Pre-receive hooks can have unintended effects on the performance of {% data variables.location.product_location %} and should be carefully implemented and reviewed. diff --git a/translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md b/translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md index faa63e77d6..90a4866503 100644 --- a/translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md +++ b/translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md @@ -1,6 +1,6 @@ --- -title: 创建预接收挂钩脚本 -intro: 使用预接收挂钩脚本创建基于内容来接受或拒绝推送的要求。 +title: Creating a pre-receive hook script +intro: Use pre-receive hook scripts to create requirements for accepting or rejecting a push based on the contents. miniTocMaxHeadingLevel: 3 redirect_from: - /enterprise/admin/developer-workflow/creating-a-pre-receive-hook-script @@ -14,138 +14,145 @@ topics: - Policies - Pre-receive hooks shortTitle: Pre-receive hook scripts -ms.openlocfilehash: 3d01ba3d5d189e65cbd2b4589af9072571837944 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146332350' --- -可以在 [`github/platform-samples` 存储库](https://github.com/github/platform-samples/tree/master/pre-receive-hooks)中查看 {% data variables.product.prodname_ghe_server %} 的预接收挂钩示例。 +You can see examples of pre-receive hooks for {% data variables.product.prodname_ghe_server %} in the [`github/platform-samples` repository](https://github.com/github/platform-samples/tree/master/pre-receive-hooks). -## 编写预接收挂钩脚本 -预接收挂钩脚本在 {% data variables.product.product_location %} 上的预接收挂钩环境中执行。 创建预接收挂钩脚本时,请考虑可用的输入、输出、退出状态和环境变量。 +## Writing a pre-receive hook script +A pre-receive hook script executes in a pre-receive hook environment on {% data variables.location.product_location %}. When you create a pre-receive hook script, consider the available input, output, exit status, and environment variables. -### 输入 (`stdin`) -推送发生后,在为远程存储库更新任何引用之前,在 {% data variables.product.product_location %} 上的 `git-receive-pack` 进程将调用预接收挂钩脚本。 脚本的标准输入 `stdin` 是一个字符串,对每个要更新的 ref 包含一行。 每行都包含 ref 的旧对象名称、引用的新对象名称和 ref 的全名。 +### Input (`stdin`) +After a push occurs and before any refs are updated for the remote repository, the `git-receive-pack` process on {% data variables.location.product_location %} invokes the pre-receive hook script. Standard input for the script, `stdin`, is a string containing a line for each ref to update. Each line contains the old object name for the ref, the new object name for the ref, and the full name of the ref. ``` SP SP LF ``` -此字符串表示以下参数。 +This string represents the following arguments. -| 参数 | 说明 | +| Argument | Description | | :------------- | :------------- | -| `` | 存储在 ref 中的旧对象名称。
创建一个新的 ref 时,该值为 40 个零。 | -| `` | 要存储在 ref 中的新对象名称。
删除 ref 时,该值为 40 个零。 | -| `` | ref 的全名。 | +| `` | Old object name stored in the ref.
When you create a new ref, the value is 40 zeroes. | +| `` | New object name to be stored in the ref.
When you delete a ref, the value is 40 zeroes. | +| `` | The full name of the ref. | -有关 `git-receive-pack` 的详细信息,请参阅 Git 文档中的“[git-receive-pack](https://git-scm.com/docs/git-receive-pack)”。 有关 ref 的详细信息,请参阅“Pro Git”中的“[Git 引用](https://git-scm.com/book/en/v2/Git-Internals-Git-References)”。 +For more information about `git-receive-pack`, see "[git-receive-pack](https://git-scm.com/docs/git-receive-pack)" in the Git documentation. For more information about refs, see "[Git References](https://git-scm.com/book/en/v2/Git-Internals-Git-References)" in *Pro Git*. -### 输出 (`stdout`) +### Output (`stdout`) -脚本的标准输出 `stdout` 将传回客户端。 任何 `echo` 语句将在命令行或用户界面上对用户均可见。 +The standard output for the script, `stdout`, is passed back to the client. Any `echo` statements will be visible to the user on the command line or in the user interface. -### 退出状态 +### Exit status -预接收脚本的退出状态决定是否接受推送。 +The exit status of a pre-receive script determines if the push will be accepted. -| Exit-status 值 | 操作 | +| Exit-status value | Action | | :- | :- | -| 0 | 将接受推送。 | -| 非零 | 将拒绝推送。 | +| 0 | The push will be accepted. | +| non-zero | The push will be rejected. | -### 环境变量 +### Environment variables -除了预接收挂钩脚本 `stdin` 的标准输入,{% data variables.product.prodname_ghe_server %} 在 Bash 环境中还为脚本执行提供以下变量。 有关预接收挂钩脚本的 `stdin` 的详细信息,请参阅“[输入 (`stdin`)](#input-stdin)”。 +In addition to the standard input for your pre-receive hook script, `stdin`, {% data variables.product.prodname_ghe_server %} makes the following variables available in the Bash environment for your script's execution. For more information about `stdin` for your pre-receive hook script, see "[Input (`stdin`)](#input-stdin)." -预接收挂钩脚本可使用不同的环境变量,具体取决于触发脚本运行的因素。 +Different environment variables are available to your pre-receive hook script depending on what triggers the script to run. -- [始终可用](#always-available) -- [可用于从 Web 界面或 API 推送](#available-for-pushes-from-the-web-interface-or-api) -- [可用于拉取请求合并](#available-for-pull-request-merges) -- [可用于使用 SSH 身份验证的推送](#available-for-pushes-using-ssh-authentication) +- [Always available](#always-available) +- [Available for pushes from the web interface or API](#available-for-pushes-from-the-web-interface-or-api) +- [Available for pull request merges](#available-for-pull-request-merges) +- [Available for pushes using SSH authentication](#available-for-pushes-using-ssh-authentication) -#### 始终可用 +#### Always available -以下变量在预接收挂钩环境中始终可用。 +The following variables are always available in the pre-receive hook environment. -| 变量 | 说明 | 示例值 | +| Variable | Description | Example value | | :- | :- | :- | -|
$GIT_DIR
| 实例上远程仓库的路径 | /data/user/repositories/a/ab/
a1/b2/34/100001234/1234.git | -|
$GIT_PUSH_OPTION_COUNT
| 客户端使用 `--push-option` 发送的推送选项数。 有关详细信息,请参阅 Git 文档中的“[git-push](https://git-scm.com/docs/git-push#Documentation/git-push.txt---push-optionltoptiongt)”。 | 1 | -|
$GIT\_PUSH\_OPTION\_N
| 其中 N 是一个从 0 开始的整数,此变量包含客户端发送的推送选项字符串。 发送的第一个选项存储在 `GIT_PUSH_OPTION_0` 中,发送的第二个选项存储在 `GIT_PUSH_OPTION_1` 中,依此类推。 有关推送选项的详细信息,请参阅 Git 文档中的“[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)”。 | abcd |{% ifversion ghes %} -|
$GIT_USER_AGENT
| 推送更改的 Git 客户端发送的 user-agent 字符串。 | git/2.0.0{% endif %} -|
$GITHUB_REPO_NAME
| 以 NAME/OWNER 格式更新的存储库名称 | octo-org/hello-enterprise | -|
$GITHUB_REPO_PUBLIC
| 表示更新的仓库是否公开的布尔值 |
  • true:仓库的可见性是公开的
  • false:仓库的可见性是私密或内部的
-|
$GITHUB_USER_IP
| 发起推送的客户端 IP 地址 | 192.0.2.1 | -|
$GITHUB_USER_LOGIN
| 发起推送的帐户的用户名 | octocat | +|
$GIT_DIR
| Path to the remote repository on the instance | /data/user/repositories/a/ab/
a1/b2/34/100001234/1234.git | +|
$GIT_PUSH_OPTION_COUNT
| The number of push options that were sent by the client with `--push-option`. For more information, see "[git-push](https://git-scm.com/docs/git-push#Documentation/git-push.txt---push-optionltoptiongt)" in the Git documentation. | 1 | +|
$GIT\_PUSH\_OPTION\_N
| Where _N_ is an integer starting at 0, this variable contains the push option string that was sent by the client. The first option that was sent is stored in `GIT_PUSH_OPTION_0`, the second option that was sent is stored in `GIT_PUSH_OPTION_1`, and so on. For more information about push options, see "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" in the Git documentation. | abcd |{% ifversion ghes %} +|
$GIT_USER_AGENT
| User-agent string sent by the Git client that pushed the changes | git/2.0.0{% endif %} +|
$GITHUB_REPO_NAME
| Name of the repository being updated in _NAME_/_OWNER_ format | octo-org/hello-enterprise | +|
$GITHUB_REPO_PUBLIC
| Boolean representing whether the repository being updated is public |
  • true: Repository's visibility is public
  • false: Repository's visibility is private or internal
+|
$GITHUB_USER_IP
| IP address of client that initiated the push | 192.0.2.1 | +|
$GITHUB_USER_LOGIN
| Username for account that initiated the push | octocat | -#### 可用于从 Web 界面或 API 推送 +#### Available for pushes from the web interface or API -当触发挂钩的 ref 更新通过 {% data variables.product.prodname_ghe_server %} 的 Web 界面或 API 进行时,`$GITHUB_VIA` 变量可用于预接收挂钩环境。 该值描述了更新 ref 的操作。 +The `$GITHUB_VIA` variable is available in the pre-receive hook environment when the ref update that triggers the hook occurs via either the web interface or the API for {% data variables.product.prodname_ghe_server %}. The value describes the action that updated the ref. -| 值 | 操作 | 详细信息 | +| Value | Action | More information | | :- | :- | :- | -|
auto-merge deployment api
| 通过 API 创建的部署自动合并基础分支 | REST API 文档中的“[创建部署](/rest/reference/deployments#create-a-deployment)” | -|
blob#save
| 在 Web 界面中更改文件的内容 | [编辑文件](/repositories/working-with-files/managing-files/editing-files) | -|
branch merge api
| 通过 API 合并分支 | REST API 文档中的“[合并分支](/rest/reference/branches#merge-a-branch)” | -|
branches page delete button
| 在 Web 界面中删除分支 | [在存储库中创建和删除分支](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch) | -|
git refs create api
| 通过 API 创建 ref | REST API 文档中的“[Git 数据库](/rest/reference/git#create-a-reference)” | -|
git refs delete api
| 通过 API 删除 ref | REST API 文档中的“[Git 数据库](/rest/reference/git#delete-a-reference)” | -|
git refs update api
| 通过 API 更新 ref | REST API 文档中的“[Git 数据库](/rest/reference/git#update-a-reference)” | -|
git repo contents api
| 通过 API 更改文件的内容 | REST API 文档中的“[创建或更新文件内容](/rest/reference/repos#create-or-update-file-contents)” | -{%- ifversion ghes %} | `merge ` | 使用自动合并合并拉取请求 |“[自动合并拉取请求](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)”| {%- endif %} |
merge base into head
| 当基础分支需要严格的状态检查时从基础分支更新主题分支(例如,通过拉取请求中的“更新分支”)|“[关于受保护的分支](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)”| |
pull request branch delete button
| 从 Web 界面中的拉取请求中删除主题分支 |“[在拉取请求中删除和还原分支](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#deleting-a-branch-used-for-a-pull-request)”| |
pull request branch undo button
| 从 Web 界面中的拉取请求还原主题分支 |“[在拉取请求中删除和还原分支](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#restoring-a-deleted-branch)”| |
pull request merge api
| 通过 API 合并拉取请求 | REST API 文档中的“[拉取](/rest/reference/pulls#merge-a-pull-request)”| |
pull request merge button
| 在 Web 界面中合并拉取请求 |“[合并拉取请求](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request#merging-a-pull-request-on-github)”| |
pull request revert button
| 拉取请求的还原 |“[还原拉取请求](/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request)”| |
releases delete button
| 版本删除 |“[管理存储库中的版本](/github/administering-a-repository/managing-releases-in-a-repository#deleting-a-release)”| |
stafftools branch restore
| 从站点管理仪表板还原分支 |“[站点管理仪表板](/admin/configuration/site-admin-dashboard#repositories)”| |
tag create api
| 通过 API 创建标记 | REST API 文档中的“[Git 数据库](/rest/reference/git#create-a-tag-object)”| |
slumlord (#SHA)
| 通过 Subversion 提交 |“[对 Subversion 客户端的支持](/github/importing-your-projects-to-github/support-for-subversion-clients#making-commits-to-subversion)”| |
web branch create
| 通过 Web 界面创建分支 |“[在存储库中创建和删除分支](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)”| +|
auto-merge deployment api
| Automatic merge of the base branch via a deployment created with the API | "[Create a deployment](/rest/reference/deployments#create-a-deployment)" in the REST API documentation | +|
blob#save
| Change to a file's contents in the web interface | "[Editing files](/repositories/working-with-files/managing-files/editing-files)" | +|
branch merge api
| Merge of a branch via the API | "[Merge a branch](/rest/reference/branches#merge-a-branch)" in the REST API documentation | +|
branches page delete button
| Deletion of a branch in the web interface | "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" | +|
git refs create api
| Creation of a ref via the API | "[Git database](/rest/reference/git#create-a-reference)" in the REST API documentation | +|
git refs delete api
| Deletion of a ref via the API | "[Git database](/rest/reference/git#delete-a-reference)" in the REST API documentation | +|
git refs update api
| Update of a ref via the API | "[Git database](/rest/reference/git#update-a-reference)" in the REST API documentation | +|
git repo contents api
| Change to a file's contents via the API | "[Create or update file contents](/rest/reference/repos#create-or-update-file-contents)" in the REST API documentation | +{%- ifversion ghes %} +| `merge ` | Merge of a pull request using auto-merge | "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)" | +{%- endif %} +|
merge base into head
| Update of the topic branch from the base branch when the base branch requires strict status checks (via **Update branch** in a pull request, for example) | "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" | +|
pull request branch delete button
| Deletion of a topic branch from a pull request in the web interface | "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#deleting-a-branch-used-for-a-pull-request)" | +|
pull request branch undo button
| Restoration of a topic branch from a pull request in the web interface | "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#restoring-a-deleted-branch)" | +|
pull request merge api
| Merge of a pull request via the API | "[Pulls](/rest/reference/pulls#merge-a-pull-request)" in the REST API documentation | +|
pull request merge button
| Merge of a pull request in the web interface | "[Merging a pull request](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request#merging-a-pull-request-on-github)" | +|
pull request revert button
| Revert of a pull request | "[Reverting a pull request](/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request)" | +|
releases delete button
| Deletion of a release | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#deleting-a-release)" | +|
stafftools branch restore
| Restoration of a branch from the site admin dashboard | "[Site admin dashboard](/admin/configuration/site-admin-dashboard#repositories)" | +|
tag create api
| Creation of a tag via the API | "[Git database](/rest/reference/git#create-a-tag-object)" in the REST API documentation | +|
slumlord (#SHA)
| Commit via Subversion | "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients#making-commits-to-subversion)" | +|
web branch create
| Creation of a branch via the web interface | "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)" | -#### 可用于拉取请求合并 +#### Available for pull request merges -当触发挂钩的推送由于拉取请求请求合并而成为推送时,以下变量在预接收挂钩环境中可用。 +The following variables are available in the pre-receive hook environment when the push that triggers the hook is a push due to the merge of a pull request. -| 变量 | 说明 | 示例值 | +| Variable | Description | Example value | | :- | :- | :- | -|
$GITHUB_PULL_REQUEST_AUTHOR_LOGIN
| 编写拉取请求的帐户的用户名 | octocat | -|
$GITHUB_PULL_REQUEST_HEAD
| 拉取请求的主题分支的名称,格式为 `USERNAME:BRANCH` | octocat:fix-bug | -|
$GITHUB_PULL_REQUEST_BASE
| 拉取请求的基础分支的名称,格式为 `USERNAME:BRANCH` | octocat:main | +|
$GITHUB_PULL_REQUEST_AUTHOR_LOGIN
| Username of account that authored the pull request | octocat | +|
$GITHUB_PULL_REQUEST_HEAD
| The name of the pull request's topic branch, in the format `USERNAME:BRANCH` | octocat:fix-bug | +|
$GITHUB_PULL_REQUEST_BASE
| The name of the pull request's base branch, in the format `USERNAME:BRANCH` | octocat:main | -#### 可用于使用 SSH 身份验证的推送 +#### Available for pushes using SSH authentication -| 变量 | 说明 | 示例值 | +| Variable | Description | Example value | | :- | :- | :- | -|
$GITHUB_PUBLIC_KEY_FINGERPRINT
| 推送更改的用户的公钥指纹 | a1:b2:c3:d4:e5:f6:g7:h8:i9:j0:k1:l2:m3:n4:o5:p6 | +|
$GITHUB_PUBLIC_KEY_FINGERPRINT
| The public key fingerprint for the user who pushed the changes | a1:b2:c3:d4:e5:f6:g7:h8:i9:j0:k1:l2:m3:n4:o5:p6 | -## 设置权限并将预接收挂钩推送到 {% data variables.product.prodname_ghe_server %} +## Setting permissions and pushing a pre-receive hook to {% data variables.product.prodname_ghe_server %} -{% data variables.product.product_location %} 上的仓库中包含预接收挂钩脚本。 站点管理员必须考虑仓库权限,确保只有适当的用户才能访问。 +A pre-receive hook script is contained in a repository on {% data variables.location.product_location %}. A site administrator must take into consideration the repository permissions and ensure that only the appropriate users have access. -我们建议将挂钩合并到单个仓库。 如果统一的挂钩存储库是公共的,则可以使用 `README.md` 来解释策略强制实施。 此外,也可以通过拉取请求接受贡献。 但是,只能从默认分支添加预接收挂钩。 对于测试工作流程,应使用具有配置的仓库的分支。 +We recommend consolidating hooks to a single repository. If the consolidated hook repository is public, the `README.md` can be used to explain policy enforcements. Also, contributions can be accepted via pull requests. However, pre-receive hooks can only be added from the default branch. For a testing workflow, forks of the repository with configuration should be used. -1. 对于 Mac 用户,确保脚本具有执行权限: +1. For Mac users, ensure the scripts have execute permissions: ```shell - $ sudo chmod +x SCRIPT_FILE.sh + $ sudo chmod +x SCRIPT_FILE.sh ``` - 对于 Windows 用户,确保脚本具有执行权限: + For Windows users, ensure the scripts have execute permissions: ```shell - git update-index --chmod=+x SCRIPT_FILE.sh + git update-index --chmod=+x SCRIPT_FILE.sh ``` -2. 在 {% data variables.product.product_location %} 提交并推送到指定的预接收挂钩仓库。 +2. Commit and push to the designated repository for pre-receive hooks on {% data variables.location.product_location %}. ```shell - $ git commit -m "YOUR COMMIT MESSAGE" + $ git commit -m "YOUR COMMIT MESSAGE" $ git push ``` -3. 在 {% data variables.product.prodname_ghe_server %} 实例上[创建预接收挂钩](/enterprise/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance/#creating-pre-receive-hooks)。 +3. [Create the pre-receive hook](/enterprise/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance/#creating-pre-receive-hooks) on the {% data variables.product.prodname_ghe_server %} instance. -## 在本地测试预接收脚本 -在 {% data variables.product.product_location %} 上创建或更新预接收挂钩脚本之前,您可以在本地对其进行测试。 一种方法是创建本地 Docker 环境以充当可以执行预接收挂钩的远程仓库。 +## Testing pre-receive scripts locally +You can test a pre-receive hook script locally before you create or update it on {% data variables.location.product_location %}. One method is to create a local Docker environment to act as a remote repository that can execute the pre-receive hook. {% data reusables.linux.ensure-docker %} -2. 创建一个名为 `Dockerfile.dev` 的文件,其中包含: +2. Create a file called `Dockerfile.dev` containing: ```dockerfile FROM gliderlabs/alpine:3.3 @@ -167,7 +174,7 @@ ms.locfileid: '146332350' CMD ["/usr/sbin/sshd", "-D"] ``` -3. 创建一个名为 `always_reject.sh` 的测试预接收脚本。 此示例脚本将拒绝所有推送,这对于锁定仓库非常有用: +3. Create a test pre-receive script called `always_reject.sh`. This example script will reject all pushes, which is useful for locking a repository: ``` #!/usr/bin/env bash @@ -176,13 +183,13 @@ ms.locfileid: '146332350' exit 1 ``` -4. 确保 `always_reject.sh` 脚本具有执行权限: +4. Ensure the `always_reject.sh` scripts has execute permissions: ```shell $ chmod +x always_reject.sh ``` -5. 从包含 `Dockerfile.dev` 的目录中,生成一个映像: +5. From the directory containing `Dockerfile.dev`, build an image: ```shell $ docker build -f Dockerfile.dev -t pre-receive.dev . @@ -205,32 +212,32 @@ ms.locfileid: '146332350' > Successfully built dd8610c24f82 ``` -6. 运行包含生成的 SSH 密钥的数据容器: +6. Run a data container that contains a generated SSH key: ```shell $ docker run --name data pre-receive.dev /bin/true ``` -7. 将测试预接收挂钩 `always_reject.sh` 复制到数据容器中: +7. Copy the test pre-receive hook `always_reject.sh` into the data container: ```shell $ docker cp always_reject.sh data:/home/git/test.git/hooks/pre-receive ``` -8. 运行运行 `sshd` 并执行挂钩的应用程序容器。 记下返回的容器 ID: +8. Run an application container that runs `sshd` and executes the hook. Take note of the container id that is returned: ```shell $ docker run -d -p 52311:22 --volumes-from data pre-receive.dev > 7f888bc700b8d23405dbcaf039e6c71d486793cad7d8ae4dd184f4a47000bc58 ``` -9. 将生成的 SSH 密钥从数据容器复制到本地计算机: +9. Copy the generated SSH key from the data container to the local machine: ```shell $ docker cp data:/home/git/.ssh/id_ed25519 . ``` -10. 修改测试存储库的远程并推送到 Docker 容器内的 `test.git` 存储库。 此示例使用 `git@github.com:octocat/Hello-World.git`,但你可以使用任何想要的存储库。 此示例假定您的本地计算机 (127.0.0.1) 绑定了端口 52311,但如果 docker 在远程计算机上运行,则可以使用不同的 IP 地址。 +10. Modify the remote of a test repository and push to the `test.git` repo within the Docker container. This example uses `git@github.com:octocat/Hello-World.git` but you can use any repository you want. This example assumes your local machine (127.0.0.1) is binding port 52311, but you can use a different IP address if docker is running on a remote machine. ```shell $ git clone git@github.com:octocat/Hello-World.git @@ -249,7 +256,7 @@ ms.locfileid: '146332350' > error: failed to push some refs to 'git@192.168.99.100:test.git' ``` - 请注意,在执行预接收挂钩并回显脚本中的输出后,将拒绝推送。 + Notice that the push was rejected after executing the pre-receive hook and echoing the output from the script. -## 延伸阅读 - - Pro Git 网站中的“[自定义 Git - Git 强制实施策略示例](https://git-scm.com/book/en/v2/Customizing-Git-An-Example-Git-Enforced-Policy)” +## Further reading + - "[Customizing Git - An Example Git-Enforced Policy](https://git-scm.com/book/en/v2/Customizing-Git-An-Example-Git-Enforced-Policy)" from the *Pro Git website* diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md index b0c9e857bf..96b0308009 100644 --- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: 将组织添加到企业 -intro: 您可以创建新的组织或邀请现有组织来管理您的企业。 +title: Adding organizations to your enterprise +intro: You can create new organizations or invite existing organizations to manage within your enterprise. redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account - /articles/adding-organizations-to-your-enterprise-account @@ -15,63 +15,59 @@ topics: - Organizations shortTitle: Add organizations permissions: Enterprise owners can add organizations to an enterprise. -ms.openlocfilehash: 09e4fa9c1b33f50e35f6088eb671b90df4a5eda3 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147573351' --- -## 关于将组织添加到企业帐户 -您的企业帐户可以拥有组织。 企业成员可以跨组织内的相关项目进行协作。 有关详细信息,请参阅“[关于组织](/organizations/collaborating-with-groups-in-organizations/about-organizations)”。 +## About addition of organizations to your enterprise account -可将新组织添加到企业帐户。 如果不使用 {% data variables.product.prodname_emus %},可将 {% data variables.product.product_location %} 上的现有组织添加到企业。 不能将 {% data variables.product.prodname_emu_enterprise %} 中的现有组织添加到其他企业。 +Your enterprise account can own organizations. Members of your enterprise can collaborate across related projects within an organization. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." -{% data reusables.enterprise.create-an-enterprise-account %} 有关详细信息,请参阅“[创建企业帐户](/admin/overview/creating-an-enterprise-account)”。 +You can add new organizations to your enterprise account. If you do not use {% data variables.product.prodname_emus %}, you can add existing organizations on {% data variables.location.product_location %} to your enterprise. You cannot add an existing organization from an {% data variables.enterprise.prodname_emu_enterprise %} to a different enterprise. -将现有组织添加到企业后,该组织的资源仍可供同一 URL 的成员访问,并且以下更改将会应用。 +{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)." -- 组织的成员将成为企业成员,并且 {% data variables.product.company_short %} 将按组织的使用情况向企业帐户收费。 必须确保企业帐户有足够的许可证来容纳任何新成员。 有关详细信息,请参阅“[关于企业的计费](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)”。 -- 企业所有者可管理他们在组织内的角色。 有关详细信息,请参阅“[管理企业拥有的组织中的角色](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)”。 -- 应用于企业的任何策略都将应用于组织。 有关详细信息,请参阅“[关于企业策略](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)”。 -- 如果为企业帐户配置了 SAML SSO,则企业的 SAML 配置将应用于组织。 如果组织使用了 SAML SSO,则企业帐户的配置将替换组织的配置。 SCIM 不适用于企业帐户,因此将为组织禁用 SCIM。 有关详细信息,请参阅“[为企业配置 SAML 单一登录](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise)”和“[将 SAML 配置从组织切换到企业帐户](/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)”。 -- 如果为组织配置了 SAML SSO,则成员现有的有权访问组织资源的个人访问令牌 (PAT) 或 SSH 密钥将有权访问相同的资源。 要访问企业拥有的其他组织,成员必须授权 PAT 或密钥。 有关详细信息,请参阅“[授权用于 SAML 单一登录的个人访问令牌](/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)”和“[授权用于 SAML 单一登录的 SSH 密钥](/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)”。 -- 如果组织通过 {% data variables.product.prodname_github_connect %} 连接到 {% data variables.product.prodname_ghe_server %} 或 {% data variables.product.prodname_ghe_managed %},则将组织添加到企业帐户不会更新连接。 {% data variables.product.prodname_github_connect %} 功能将不再适用于组织。 要继续使用 {% data variables.product.prodname_github_connect %},必须禁用并重新启用该功能。 有关详细信息,请参阅以下文章。 +After you add an existing organization to your enterprise, the organization's resources remain accessible to members at the same URLs, and the following changes will apply. - - {% data variables.product.prodname_ghe_server %} 文档中的“[管理 {% data variables.product.prodname_github_connect %}](/enterprise-server@latest/admin/configuration/configuring-github-connect/managing-github-connect)” - - {% data variables.product.prodname_ghe_managed %} 文档中的“[管理 {% data variables.product.prodname_github_connect %}](/github-ae@latest/admin/configuration/configuring-github-connect/managing-github-connect)” -- 如果组织使用计费的 {% data variables.product.prodname_marketplace %} 应用,则组织可继续使用这些应用,但必须直接向供应商支付费用。 有关详细信息,请与应用供应商联系。 +- The organization's members will become members of the enterprise, and {% data variables.product.company_short %} will bill the enterprise account for the organization's usage. You must ensure that the enterprise account has enough licenses to accommodate any new members. For more information, see "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)." +- Enterprise owners can manage their role within the organization. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)." +- Any policies applied to the enterprise will apply to the organization. For more information, see "[About enterprise policies](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)." +- If SAML SSO is configured for the enterprise account, the enterprise's SAML configuration will apply to the organization. If the organization used SAML SSO, the enterprise account's configuration will replace the organization's configuration. SCIM is not available for enterprise accounts, so SCIM will be disabled for the organization. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise)" and "[Switching your SAML configuration from an organization to an enterprise account](/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." +- If SAML SSO was configured for the organization, members' existing {% data variables.product.pat_generic %} or SSH keys that were authorized to access the organization's resources will be authorized to access the same resources. To access additional organizations owned by the enterprise, members must authorize the {% data variables.product.pat_generic %} or key. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." +- If the organization was connected to {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %} using {% data variables.product.prodname_github_connect %}, adding the organization to an enterprise will not update the connection. {% data variables.product.prodname_github_connect %} features will no longer function for the organization. To continue using {% data variables.product.prodname_github_connect %}, you must disable and re-enable the feature. For more information, see the following articles. -## 在企业帐户中创建组织 + - "[Managing {% data variables.product.prodname_github_connect %}](/enterprise-server@latest/admin/configuration/configuring-github-connect/managing-github-connect)" in the {% data variables.product.prodname_ghe_server %} documentation + - "[Managing {% data variables.product.prodname_github_connect %}](/github-ae@latest/admin/configuration/configuring-github-connect/managing-github-connect)" in the {% data variables.product.prodname_ghe_managed %} documentation +- If the organization used billed {% data variables.product.prodname_marketplace %} apps, the organization can continue to use the apps, but must pay the vendor directly. For more information, contact the app's vendor. +- Any coupons will be removed from the organization. To reapply the coupon, [contact our sales team](https://github.com/enterprise/contact). -在企业帐户设置中创建的新组织包含在企业帐户的 {% data variables.product.prodname_ghe_cloud %} 订阅中。 +## Creating an organization in your enterprise account -创建企业帐户所拥有的组织的企业所有者自动成为组织所有者。 有关组织所有者的详细信息,请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。 +New organizations you create within your enterprise account settings are included in your enterprise account's {% data variables.product.prodname_ghe_cloud %} subscription. + +Enterprise owners who create an organization owned by the enterprise account automatically become organization owners. For more information about organization owners, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." {% data reusables.enterprise-accounts.access-enterprise %} -2. 在“组织”选项卡中的组织列表上方,单击“新建组织” . - ![“新建组织”按钮](/assets/images/help/business-accounts/enterprise-account-add-org.png) -3. 在 "Organization name"(组织名称)下,输入组织的名称。 - ![用于键入新组织名称的字段](/assets/images/help/business-accounts/new-organization-name-field.png) -4. 单击“创建组织”。 -5. 在“邀请所有者”下,键入想邀其成为组织所有者的人员的用户名,然后单击“邀请”。 - ![组织所有者搜索字段和“邀请”按钮](/assets/images/help/business-accounts/invite-org-owner.png) -6. 单击“完成”。 +2. On the **Organizations** tab, above the list of organizations, click **New organization**. + ![New organization button](/assets/images/help/business-accounts/enterprise-account-add-org.png) +3. Under "Organization name", type a name for your organization. + ![Field to type a new organization name](/assets/images/help/business-accounts/new-organization-name-field.png) +4. Click **Create organization**. +5. Under "Invite owners", type the username of a person you'd like to invite to become an organization owner, then click **Invite**. + ![Organization owner search field and Invite button](/assets/images/help/business-accounts/invite-org-owner.png) +6. Click **Finish**. -## 邀请组织加入您的企业帐户 +## Inviting an organization to join your enterprise account -企业所有者可以邀请现有组织加入其企业帐户。 如果您要邀请的组织已经归其他企业所有,则在上一个企业放弃对组织的所有权之前,您将无法发出邀请。 有关详细信息,请参阅“[从企业中删除组织](/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise)”。 +Enterprise owners can invite existing organizations to join their enterprise account. If the organization you want to invite is already owned by another enterprise, you will not be able to issue an invitation until the previous enterprise gives up ownership of the organization. For more information, see "[Removing an organization from your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise)." {% data reusables.enterprise-accounts.access-enterprise %} -2. 在“组织”选项卡中的组织列表上方,单击“邀请组织” 。 -![邀请组织](/assets/images/help/business-accounts/enterprise-account-invite-organization.png) -3. 在“Organization name(组织名称)”下,开始键入要邀请的组织名称,并在它出现在下拉列表中时选择它。 -![搜索组织](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png) -4. 单击“邀请组织”。 -5. 组织所有者将收到一封邀请他们加入企业的电子邮件。 至少有一个所有者接受邀请才能继续该过程。 您可以在所有者批准邀请之前随时取消或重新发送邀请。 -![取消或重新发送](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png) -6. 一旦组织所有者批准了邀请,您可以在待定邀请列表中查看其状态。 -![待定邀请](/assets/images/help/business-accounts/enterprise-account-pending.png) -7. 单击“批准”完成传输,或单击“取消”以取消传输 。 -![批准邀请](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png) +2. On the **Organizations** tab, above the list of organizations, click **Invite organization**. +![Invite organization](/assets/images/help/business-accounts/enterprise-account-invite-organization.png) +3. Under "Organization name", start typing the name of the organization you want to invite and select it when it appears in the drop-down list. +![Search for organization](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png) +4. Click **Invite organization**. +5. The organization owners will receive an email inviting them to join the enterprise. At least one owner needs to accept the invitation before the process can continue. You can cancel or resend the invitation at any time before an owner approves it. +![Cancel or resend](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png) +6. Once an organization owner has approved the invitation, you can view its status in the list of pending invitations. +![Pending invitation](/assets/images/help/business-accounts/enterprise-account-pending.png) +7. Click **Approve** to complete the transfer, or **Cancel** to cancel it. +![Approve invitation](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png) diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md index 53cb2f1ff3..d4be251522 100644 --- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md +++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md @@ -1,12 +1,12 @@ --- -title: Adding people to teams(将用户添加到团队) +title: Adding people to teams redirect_from: - /enterprise/admin/articles/adding-teams - /enterprise/admin/articles/adding-or-inviting-people-to-teams - /enterprise/admin/guides/user-management/adding-or-inviting-people-to-teams - /enterprise/admin/user-management/adding-people-to-teams - /admin/user-management/adding-people-to-teams -intro: '创建团队后,组织管理员可以将用户从 {% data variables.product.product_location %} 添加到团队并决定他们可以访问哪些存储库。' +intro: 'Once a team has been created, organization admins can add users from {% data variables.location.product_location %} to the team and determine which repositories they have access to.' versions: ghes: '*' ghae: '*' @@ -16,28 +16,26 @@ topics: - Enterprise - Teams - User account -ms.openlocfilehash: 1246641db416630d0faed75821078618a4399eb8 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147884251' --- -每个团队都有自己单独定义的[组织所拥有存储库的访问权限](/articles/permission-levels-for-an-organization)。 +Each team has its own individually defined [access permissions for repositories owned by your organization](/articles/permission-levels-for-an-organization). -- 具有所有者角色的成员可以向所有团队添加成员或从中移除现有组织成员。 -- 具有管理员权限的团队成员仅可以修改所属团队的成员资格和仓库。 +- Members with the owner role can add or remove existing organization members from all teams. +- Members of teams that give admin permissions can only modify team membership and repositories for that team. -## 设置团队 +## Setting up a team -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.invite_to_team %} {% data reusables.organizations.review-team-repository-access %} +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.invite_to_team %} +{% data reusables.organizations.review-team-repository-access %} {% ifversion ghes %} -## 将团队映射到 LDAP 组(例如,使用 LDAP 同步进行用户身份验证) +## Mapping teams to LDAP groups (for instances using LDAP Sync for user authentication) {% data reusables.enterprise_management_console.badge_indicator %} -要将新成员添加到已同步至 LDAP 组的团队,请将用户添加为 LDAP 组的成员,或者联系您的 LDAP 管理员。 +To add a new member to a team synced to an LDAP group, add the user as a member of the LDAP group, or contact your LDAP administrator. {% endif %} diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md index 6ab1fa5387..859fe38bc4 100644 --- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md +++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md @@ -1,6 +1,6 @@ --- -title: 使用 Jenkins 的持续集成 -intro: '当向 {% data variables.product.product_location %} 中的存储库进行推送时,你可以在 Jenkins 服务器上自动触发构建作业。' +title: Continuous integration using Jenkins +intro: 'You can automatically trigger build jobs on a Jenkins server when pushes are made to a repository in {% data variables.location.product_location %}.' redirect_from: - /enterprise/admin/developer-workflow/continuous-integration-using-jenkins - /enterprise/admin/user-management/continuous-integration-using-jenkins @@ -13,13 +13,7 @@ topics: - CI - Enterprise shortTitle: CI using Jenkins -ms.openlocfilehash: dacb99db402d0d06aa4a3c4248e1fcabfd2d085d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145098679' --- -## 要求 +## Requirements -- 按照我们的白皮书“[使用 Jenkins 和 GitHub 实现 CI 的实用指南](https://resources.github.com/whitepapers/practical-guide-to-CI-with-Jenkins-and-GitHub/)”,逐步了解如何在向 {% data variables.product.product_location %} 中的存储库进行推送时在 Jenkins 服务器上自动触发生成作业。 +- Follow our white paper "[Practical guide to CI with Jenkins and GitHub](https://resources.github.com/whitepapers/practical-guide-to-CI-with-Jenkins-and-GitHub/)" to get step by step instructions on how you can automatically trigger build jobs on a Jenkins server when pushes are made to a repository in {% data variables.location.product_location %}. diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md index 42da8d0a32..d87b91370c 100644 --- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md +++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md @@ -1,6 +1,6 @@ --- -title: Creating teams(创建团队) -intro: 借助团队,组织可以创建成员组和控制仓库的访问权限。 可以向团队成员授予特定仓库的读取、写入或管理员权限。 +title: Creating teams +intro: 'Teams give organizations the ability to create groups of members and control access to repositories. Team members can be granted read, write, or admin permissions to specific repositories.' redirect_from: - /enterprise/admin/user-management/creating-teams - /admin/user-management/creating-teams @@ -13,47 +13,55 @@ topics: - Enterprise - Teams - User account -ms.openlocfilehash: 83db75485e7967941fdcd3ab651e638aa1eabb3f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146332334' --- -团队是 {% data variables.product.prodname_dotcom %} 的许多协作功能的核心,例如团队 @mentions,用于通知相关方你希望请求他们的意见或关注。 有关详细信息,请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)。” +Teams are central to many of {% data variables.product.prodname_dotcom %}'s collaborative features, such as team @mentions to notify appropriate parties that you'd like to request their input or attention. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." -一个团队可以代表您的公司内的一个组,或者包含具有特定兴趣或专业知识的人。 例如,{% data variables.product.product_location %} 上的可访问性专家团队可能包括来自多个不同部门的人。 团队可以体现职能关注,对公司现有的部门层次结构进行补充。 +A team can represent a group within your company or include people with certain interests or expertise. For example, a team of accessibility experts on {% data variables.location.product_location %} could comprise of people from several different departments. Teams can represent functional concerns that complement a company's existing divisional hierarchy. -组织可以创建包含多个级别的嵌套团队来反映公司或小组的层级结构。 有关详细信息,请参阅“[关于团队](/enterprise/user/articles/about-teams/#nested-teams)”。 +Organizations can create multiple levels of nested teams to reflect a company or group's hierarchy structure. For more information, see "[About teams](/enterprise/user/articles/about-teams/#nested-teams)." -## 创建团队 +## Creating a team -审慎的团队组合是控制仓库权限的强有力方式。 例如,如果组织只允许发布工程团队将代码推送到任何存储库的默认分支,则你可以只授予发布工程团队对组织的存储库的管理员权限,并授予所有其他团队读取权限 。 +A prudent combination of teams is a powerful way to control repository access. For example, if your organization allows only your release engineering team to push code to the default branch of any repository, you could give only the release engineering team **admin** permissions to your organization's repositories and give all other teams **read** permissions. -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.new_team %} {% data reusables.organizations.team_name %} {% data reusables.organizations.team_description %} {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create-team-choose-parent %} {% data reusables.organizations.create_team %} +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.new_team %} +{% data reusables.organizations.team_name %} +{% data reusables.organizations.team_description %} +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create-team-choose-parent %} +{% data reusables.organizations.create_team %} {% ifversion ghes %} -## 创建启用 LDAP 同步的团队 +## Creating teams with LDAP Sync enabled -使用 LDAP 进行用户身份验证的实例可以使用 LDAP 同步管理团队的成员。 在“LDAP 组”字段中设置组的可分辨名称 (DN) 会将团队映射到 LDAP 服务器上的 LDAP 组 。 如果使用 LDAP 同步来管理团队成员,则无法在 {% data variables.product.product_location %} 内管理团队。 启用 LDAP 同步后,映射的团队将以配置的间隔定期在后台同步成员。 有关详细信息,请参阅“[启用 LDAP 同步](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync)。” +Instances using LDAP for user authentication can use LDAP Sync to manage a team's members. Setting the group's **Distinguished Name** (DN) in the **LDAP group** field will map a team to an LDAP group on your LDAP server. If you use LDAP Sync to manage a team's members, you won't be able to manage your team within {% data variables.location.product_location %}. The mapped team will sync its members in the background and periodically at the interval configured when LDAP Sync is enabled. For more information, see "[Enabling LDAP Sync](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync)." -您必须是站点管理员和组织所有者才能创建启用了 LDAP 同步的团队。 +You must be a site admin and an organization owner to create a team with LDAP sync enabled. {% data reusables.enterprise_user_management.ldap-sync-nested-teams %} {% warning %} -**注意:** -- LDAP 同步仅管理团队的成员列表。 您必须在 {% data variables.product.prodname_ghe_server %} 内管理团队的仓库和权限。 -- 如果到 DN 的 LDAP 组映射被移除(例如,LDAP 组被删除),将从同步的 {% data variables.product.prodname_ghe_server %} 团队中移除每个成员。 若要解决此问题,请将团队映射到新的 DN,重新添加团队成员,然后[手动同步映射](/enterprise/admin/authentication/using-ldap#manually-syncing-ldap-accounts)。 -- 启用 LDAP 同步后,如果某个用户被从仓库中移除,他们将失去访问权限,但是他们的分叉将不会删除。 如果某个用户被添加到团队中并在三个月内拥有原始组织仓库的访问权限,他们对分叉的访问权限将在下一次同步时自动恢复。 +**Notes:** +- LDAP Sync only manages the team's member list. You must manage the team's repositories and permissions from within {% data variables.product.prodname_ghe_server %}. +- If an LDAP group mapping to a DN is removed, such as if the LDAP group is deleted, then every member is removed from the synced {% data variables.product.prodname_ghe_server %} team. To fix this, map the team to a new DN, add the team members back, and [manually sync the mapping](/enterprise/admin/authentication/using-ldap#manually-syncing-ldap-accounts). +- When LDAP Sync is enabled, if a person is removed from a repository, they will lose access but their forks will not be deleted. If the person is added to a team with access to the original organization repository within three months, their access to the forks will be automatically restored on the next sync. {% endwarning %} -1. 确保[已启用 LDAP 同步](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync)。 -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.new_team %} {% data reusables.organizations.team_name %} -6. 搜索要映射团队的目标 LDAP 组的 DN。 如果您不知道 DN,请输入 LDAP 组的名称。 {% data variables.product.prodname_ghe_server %} 将搜索并自动完成任何匹配。 -![映射到 LDAP 组 DN](/assets/images/enterprise/orgs-and-teams/ldap-group-mapping.png) {% data reusables.organizations.team_description %} {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create-team-choose-parent %} {% data reusables.organizations.create_team %} +1. Ensure that [LDAP Sync is enabled](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync). +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.new_team %} +{% data reusables.organizations.team_name %} +6. Search for an LDAP group's DN to map the team to. If you don't know the DN, type the LDAP group's name. {% data variables.product.prodname_ghe_server %} will search for and autocomplete any matches. +![Mapping to the LDAP group DN](/assets/images/enterprise/orgs-and-teams/ldap-group-mapping.png) +{% data reusables.organizations.team_description %} +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create-team-choose-parent %} +{% data reusables.organizations.create_team %} {% endif %} diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md index 15b58756ca..103d51e4a9 100644 --- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md +++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md @@ -1,6 +1,6 @@ --- -title: 为组织要求双重身份验证 -intro: 您可以要求组织成员和外部协作者为他们在组织中的个人帐户启用双重身份验证,使恶意操作者更难以访问组织的仓库和设置。 +title: Requiring two-factor authentication for an organization +intro: 'You can require organization members and outside collaborators to enable two-factor authentication for their personal accounts in an organization, making it harder for malicious actors to access an organization''s repositories and settings.' redirect_from: - /enterprise/admin/user-management/requiring-two-factor-authentication-for-an-organization - /admin/user-management/requiring-two-factor-authentication-for-an-organization @@ -14,58 +14,59 @@ topics: - Policies - Security shortTitle: Require 2FA -ms.openlocfilehash: 2f7fe986cf3b13a171f85da9d5fdb74eeed0d648 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '146331638' --- -使用 LDAP 或内置身份验证时,{% data variables.product.product_location %} 将支持双重身份验证。 组织管理员可以要求成员启用双重身份验证。 +When using LDAP or built-in authentication, two-factor authentication is supported on {% data variables.location.product_location %}. Organization administrators can require members to have two-factor authentication enabled. {% data reusables.enterprise_user_management.external_auth_disables_2fa %} -有关详细信息,请参阅“[关于双重身份验证](/github/authenticating-to-github/about-two-factor-authentication)”。 +For more information, see "[About two-factor authentication](/github/authenticating-to-github/about-two-factor-authentication)." -## 强制执行双重身份验证的要求 +## Requirements for enforcing two-factor authentication -在你要求组织成员和外部协作者使用 2FA 之前,必须为自己的个人帐户[启用双重身份验证](/enterprise/user/articles/securing-your-account-with-two-factor-authentication-2fa/)。 +Before you can require organization members and outside collaborators to use 2FA, you must [enable two-factor authentication](/enterprise/user/articles/securing-your-account-with-two-factor-authentication-2fa/) for your own personal account. {% warning %} -警告: +**Warnings:** -- 如果您要求双重身份验证,则不使用双重身份验证的成员和外部协作者(包括自动程序帐户)将从组织中移除,并失去对仓库的访问权限,包括他们的私有仓库分叉。 如果用户在被从组织中移除的三个月内为自己的个人帐户启用 2FA,你可以[恢复他们的访问权限和设置](/enterprise/user/articles/reinstating-a-former-member-of-your-organization)。 -- 如果需要双重身份验证,则禁用双重身份验证的组织成员或外部协作者将被自动从组织中移除。 -- 如果您是某个要求双重身份验证的组织的唯一所有者,则在不为组织禁用双重身份验证要求的情况下,您将无法为个人帐户禁用双重身份验证。 +- When your require two-factor authentication, members and outside collaborators (including bot accounts) who do not use 2FA will be removed from the organization and lose access to its repositories, including their forks of private repositories. If they enable 2FA for their personal account within three months of being removed from the organization, you can [reinstate their access privileges and settings](/enterprise/user/articles/reinstating-a-former-member-of-your-organization). +- When 2FA is required, organization members or outside collaborators who disable 2FA will automatically be removed from the organization. +- If you're the sole owner of an organization that requires two-factor authentication, you won't be able to disable 2FA for your personal account without disabling required two-factor authentication for the organization. {% endwarning %} -在您要求使用双重身份验证之前,我们建议通知组织成员和外部协作者,并要求他们为帐户设置双重身份验证。 可以在组织的“人员”选项卡上[查看成员和外部协作者是否已使用 2FA](/enterprise/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)。 +Before you require use of two-factor authentication, we recommend notifying organization members and outside collaborators and asking them to set up 2FA for their accounts. You can [see if members and outside collaborators already use 2FA](/enterprise/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled) on an organization's People tab. -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %} {% data reusables.organizations.require_two_factor_authentication %} {% data reusables.organizations.removed_outside_collaborators %} +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +{% data reusables.organizations.security %} +{% data reusables.organizations.require_two_factor_authentication %} +{% data reusables.organizations.removed_outside_collaborators %} -## 查看从您的组织中删除的人员 +## Viewing people who were removed from your organization -若要查看在你要求双重身份验证后因为不合规而被从组织中自动移除的用户,可以在搜索字段中使用 `reason:two_factor_requirement_non_compliance` [搜索审核日志](/enterprise/admin/guides/installation/searching-the-audit-log/)。 +To view people who were automatically removed from your organization for non-compliance when you required two-factor authentication, you can [search the audit log](/enterprise/admin/guides/installation/searching-the-audit-log/) using `reason:two_factor_requirement_non_compliance` in the search field. -{% data reusables.audit_log.octicon_icon %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.audit_log.audit_log_sidebar_for_site_admins %} -4. 使用 `reason:two_factor_requirement_non_compliance` 输入搜索查询。 - ![显示因 2FA 不合规而被移除的用户的员工工具审核日志事件](/assets/images/help/2fa/2fa_noncompliance_stafftools_audit_log_search.png) 请执行相应地操作,缩小以下对象的搜索范围: - - 对于已删除的组织成员,请输入 `action:org.remove_member AND reason:two_factor_requirement_non_compliance` - - 对于已删除的外部协作者,请输入 `action:org.remove_outside_collaborator AND reason:two_factor_requirement_non_compliance` +{% data reusables.audit_log.octicon_icon %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.audit_log.audit_log_sidebar_for_site_admins %} +4. Enter your search query using `reason:two_factor_requirement_non_compliance`. + ![Staff tools audit log event showing a user removed for 2FA non-compliance](/assets/images/help/2fa/2fa_noncompliance_stafftools_audit_log_search.png) + To narrow your search for: + - Organizations members removed, enter `action:org.remove_member AND reason:two_factor_requirement_non_compliance` + - Outside collaborators removed, enter `action:org.remove_outside_collaborator AND reason:two_factor_requirement_non_compliance` - 您还可以在搜索中使用组织名称,查看已从特定组织中移除的用户: + You can also view people removed from a particular organization by using the organization name in your search: - `org:octo-org AND reason:two_factor_requirement_non_compliance` -5. 单击 **“搜索”** 。 +5. Click **Search**. -## 帮助被删除的成员和外部协作者重新加入您的组织 +## Helping removed members and outside collaborators rejoin your organization -如果在您启用双重身份验证使用要求时有任何成员或外部协作者被从组织中删除,他们将收到通知他们已被删除的电子邮件。 他们应当为个人帐户启用双重身份验证,并联系组织所有者来请求您的组织的访问权限。 +If any members or outside collaborators are removed from the organization when you enable required use of two-factor authentication, they'll receive an email notifying them that they've been removed. They should then enable 2FA for their personal account, and contact an organization owner to request access to your organization. -## 延伸阅读 +## Further reading -- [查看组织中的用户是否已启用 2FA](/enterprise/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled) -- [使用双因素身份验证 (2FA) 保护你的帐户](/enterprise/user/articles/securing-your-account-with-two-factor-authentication-2fa) -- [恢复组织的前成员](/enterprise/user/articles/reinstating-a-former-member-of-your-organization) -- [恢复前外部协作者对组织的访问权限](/enterprise/user/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization) +- "[Viewing whether users in your organization have 2FA enabled](/enterprise/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)" +- "[Securing your account with two-factor authentication (2FA)](/enterprise/user/articles/securing-your-account-with-two-factor-authentication-2fa)" +- "[Reinstating a former member of your organization](/enterprise/user/articles/reinstating-a-former-member-of-your-organization)" +- "[Reinstating a former outside collaborator's access to your organization](/enterprise/user/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)" diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md index 3f379f047c..d30c176041 100644 --- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md +++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md @@ -1,6 +1,6 @@ --- -title: 还原已删除的组织 -intro: '可以部分还原以前在 {% data variables.product.product_location %} 上删除的组织。' +title: Restoring a deleted organization +intro: 'You can partially restore an organization that was previously deleted on {% data variables.location.product_location %}.' versions: ghes: '*' type: how_to @@ -10,49 +10,44 @@ topics: - Organizations shortTitle: Restore organization permissions: 'Site administers can restore an organization on {% data variables.product.product_name %}.' -ms.openlocfilehash: 1963b1e55a9c8047c19bafd087162caa8d5085f2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147063752' --- -## 关于组织还原 -只要审核日志 Elasticsearch 索引包含 `org.delete` 事件的数据,你就可以使用站点管理仪表板还原之前在 {% data variables.product.product_location %} 上删除的组织。 +## About organization restoration -还原组织后,该组织将不会与删除前完全相同。 必须手动还原组织拥有的所有存储库。 有关详细信息,请参阅“[还原已删除的存储库](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)”。 +You can use the site admin dashboard to restore an organization that was previously deleted on {% data variables.location.product_location %}, as long as the audit log Elasticsearch indices contain the data for the `org.delete` event. -你也可以使用审核日志来帮助手动重新添加团队和组织成员。 有关详细信息,请参阅“[还原成员和团队](#restoring-members-and-teams)”。 +Immediately after you restore an organization, the organization will not be exactly the same as it was prior to the deletion. You'll have to manually restore any repositories that were owned by the organization. For more information, see "[Restoring a deleted repository](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)." -## 还原组织 +You can also use the audit log to help you manually re-add teams and organization members. For more information, see "[Restoring members and teams](#restoring-members-and-teams)." + +## Restoring an organization {% data reusables.enterprise_site_admin_settings.access-settings %} -1. 在“搜索用户、组织、企业、团队、存储库、Gist 和应用程序”下,搜索组织。 +1. Under "Search users, organizations, enterprises, teams, repositories, gists, and applications", search for the organization. - ![搜索字段和“搜索”按钮的屏幕截图](/assets/images/enterprise/stafftools/search-field.png) + ![Screenshot of the search field and Search button](/assets/images/enterprise/stafftools/search-field.png) -1. 在“已删除的帐户”下,在要还原的组织右侧,选择“{% octicon "kebab-horizontal" aria-label="The edit icon" %}”下拉菜单,然后单击“重新创建”。 +1. Under "Deleted accounts", to the right of the organization you want to restore, select the {% octicon "kebab-horizontal" aria-label="The edit icon" %} dropdown menu, then click **Recreate**. - ![已删除组织的下拉菜单屏幕截图](/assets/images/enterprise/stafftools/recreate-organization.png) + ![Screenshot of the dropdown menu for a deleted organization](/assets/images/enterprise/stafftools/recreate-organization.png) -## 还原成员和团队 +## Restoring members and teams -可以使用审核日志查找组织以前的成员和团队的列表,然后手动进行重新创建。 有关使用审核日志的详细信息,请参阅“[审核整个企业的用户](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise)”。 +You can use the audit log to find a list of the previous members and teams of the organization, then recreate them manually. For more information about using the audit log, see "[Auditing users across your enterprise](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise)." -在下面的所有搜索词组中,将 ORGANIZATION 替换为组织名称,将 TEAM 替换为团队名称。 +In all the search phrases below, replace ORGANIZATION with the name of the organization and TEAM with the name of the team. -### 还原组织成员 +### Restoring organization members -1. 要查找在组织中添加和删除的所有用户,请在审核日志中搜索 `action:org.add_member org:ORGANIZATION` 和 `action:org.remove_member org:ORGANIZATION`。 -1. 手动将每个仍应是成员的用户添加到组织中。 有关详细信息,请参阅“[将人员添加到组织](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)”。 +1. To find all users who were added to and removed from the organization, search the audit log for `action:org.add_member org:ORGANIZATION` and `action:org.remove_member org:ORGANIZATION`. +1. Manually add to the organization each user that should still be a member. For more information, see "[Adding people to your organization](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)." -### 还原团队 +### Restoring teams -1. 要查找每个团队名称,请在审核日志中搜索 `action:team.create org:ORGANIZATION`。 -1. 手动重新创建团队。 有关详细信息,请参阅“[创建团队](/organizations/organizing-members-into-teams/creating-a-team)”。 -1. 要查找已添加到每个团队的成员,请搜索 `action:team.add_member team:"ORGANIZATION/TEAM"`。 -1. 手动重新添加团队成员。 有关详细信息,请参阅“[将组织成员添加到团队](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)”。 -1. 要查找团队有权访问的存储库,请搜索 `action:team.add_repository team:"ORGANIZATION/TEAM"`。 -1. 要查找团队被授予对每个存储库的访问级别,请搜索 `action:team.update_repository_permission team:"ORGANIZATION/TEAM"`。 -1. 再次手动授予团队访问权限。 有关详细信息,请参阅“[管理团队对组织存储库的访问](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)”。 +1. To find each team name, search the audit log for `action:team.create org:ORGANIZATION`. +1. Manually recreate the team. For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)." +1. To find the members that have been added to each team, search for `action:team.add_member team:"ORGANIZATION/TEAM"`. +1. Manually re-add the team members. For more information, see "[Adding organization members to a team](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)." +1. To find the repositories that the team was granted access to, search for `action:team.add_repository team:"ORGANIZATION/TEAM"`. +1. To find the access level that the team was granted for each repository, search for `action:team.update_repository_permission team:"ORGANIZATION/TEAM"`. +1. Manually give the team access again. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)." diff --git a/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md index 2dcbff760a..c8f5a68291 100644 --- a/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md @@ -1,5 +1,5 @@ --- -title: 为企业配置 Git 大型文件存储 +title: Configuring Git Large File Storage for your enterprise intro: '{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %}' redirect_from: - /enterprise/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise @@ -23,93 +23,105 @@ topics: - LFS - Storage shortTitle: Configure Git LFS -ms.openlocfilehash: d6364bc1d45643ebb3dc1c46cec467515fd4da55 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145098674' --- -## 关于 {% data variables.large_files.product_name_long %} +## About {% data variables.large_files.product_name_long %} -{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %} 您可以将 {% data variables.large_files.product_name_long %} 与单一仓库、所有个人或组织仓库或企业中的每一个仓库结合使用。 您需要先为企业启用 {% data variables.large_files.product_name_short %},然后才能为特定仓库或组织启用 {% data variables.large_files.product_name_short %}。 +{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %} You can use {% data variables.large_files.product_name_long %} with a single repository, all of your personal or organization repositories, or with every repository in your enterprise. Before you can enable {% data variables.large_files.product_name_short %} for specific repositories or organizations, you need to enable {% data variables.large_files.product_name_short %} for your enterprise. -{% data reusables.large_files.storage_assets_location %} {% data reusables.large_files.rejected_pushes %} +{% data reusables.large_files.storage_assets_location %} +{% data reusables.large_files.rejected_pushes %} -有关详细信息,请参阅“[关于 {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)”、“[大型文件的版本控制](/enterprise/user/articles/versioning-large-files/)”和 [{% data variables.large_files.product_name_long %} 项目站点](https://git-lfs.github.com/)。 +For more information, see "[About {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)", "[Versioning large files](/enterprise/user/articles/versioning-large-files/)," and the [{% data variables.large_files.product_name_long %} project site](https://git-lfs.github.com/). {% data reusables.large_files.can-include-lfs-objects-archives %} -## 为企业配置 {% data variables.large_files.product_name_long %} +## Configuring {% data variables.large_files.product_name_long %} for your enterprise -{% data reusables.enterprise-accounts.access-enterprise %} {% ifversion ghes or ghae %} {% data reusables.enterprise-accounts.policies-tab %} {% else %} {% data reusables.enterprise-accounts.settings-tab %} {% endif %} {% data reusables.enterprise-accounts.options-tab %} -4. 在“{% data variables.large_files.product_name_short %} 访问”下,使用下拉菜单,然后单击“已启用”或“已禁用” 。 -![Git LFS 访问](/assets/images/enterprise/site-admin-settings/git-lfs-admin-center.png) +{% data reusables.enterprise-accounts.access-enterprise %} +{% ifversion ghes or ghae %} +{% data reusables.enterprise-accounts.policies-tab %} +{% else %} +{% data reusables.enterprise-accounts.settings-tab %} +{% endif %} +{% data reusables.enterprise-accounts.options-tab %} +4. Under "{% data variables.large_files.product_name_short %} access", use the drop-down menu, and click **Enabled** or **Disabled**. +![Git LFS Access](/assets/images/enterprise/site-admin-settings/git-lfs-admin-center.png) -## 为各个仓库配置 {% data variables.large_files.product_name_long %} +## Configuring {% data variables.large_files.product_name_long %} for an individual repository {% data reusables.enterprise_site_admin_settings.override-policy %} -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.repository-search %} {% data reusables.enterprise_site_admin_settings.click-repo %} {% data reusables.enterprise_site_admin_settings.admin-top-tab %} {% data reusables.enterprise_site_admin_settings.admin-tab %} {% data reusables.enterprise_site_admin_settings.git-lfs-toggle %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.repository-search %} +{% data reusables.enterprise_site_admin_settings.click-repo %} +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +{% data reusables.enterprise_site_admin_settings.git-lfs-toggle %} -## 为用户帐户或组织拥有的每个仓库配置 {% data variables.large_files.product_name_long %} +## Configuring {% data variables.large_files.product_name_long %} for every repository owned by a user account or organization -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.search-user-or-org %} {% data reusables.enterprise_site_admin_settings.click-user-or-org %} {% data reusables.enterprise_site_admin_settings.admin-top-tab %} {% data reusables.enterprise_site_admin_settings.admin-tab %} {% data reusables.enterprise_site_admin_settings.git-lfs-toggle %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.search-user-or-org %} +{% data reusables.enterprise_site_admin_settings.click-user-or-org %} +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +{% data reusables.enterprise_site_admin_settings.git-lfs-toggle %} {% ifversion ghes %} -## 将 Git Large File Storage 配置为使用第三方服务器 +## Configuring Git Large File Storage to use a third party server -{% data reusables.large_files.storage_assets_location %} {% data reusables.large_files.rejected_pushes %} +{% data reusables.large_files.storage_assets_location %} +{% data reusables.large_files.rejected_pushes %} -1. 在 {% data variables.product.product_location %} 上禁用 {% data variables.large_files.product_name_short %}。 有关详细信息,请参阅“[为你的企业配置 {% data variables.large_files.product_name_long %}](#configuring-git-large-file-storage-for-your-enterprise)”。 +1. Disable {% data variables.large_files.product_name_short %} on {% data variables.location.product_location %}. For more information, see "[Configuring {% data variables.large_files.product_name_long %} for your enterprise](#configuring-git-large-file-storage-for-your-enterprise)." -2. 创建指向第三方服务器的 {% data variables.large_files.product_name_short %} 配置文件。 +2. Create a {% data variables.large_files.product_name_short %} configuration file that points to the third party server. ```shell # Show default configuration $ git lfs env > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c) > git version 2.7.4 (Apple Git-66)   - > Endpoint=https://GITHUB-ENTERPRISE-HOST/path/to/repo/info/lfs (auth=basic) + > Endpoint=https://GITHUB-ENTERPRISE-HOST/path/to/repo/info/lfs (auth=basic)   # Create .lfsconfig that points to third party server. - $ git config -f .lfsconfig remote.origin.lfsurl https://THIRD-PARTY-LFS-SERVER/path/to/repo + $ git config -f .lfsconfig remote.origin.lfsurl https://THIRD-PARTY-LFS-SERVER/path/to/repo $ git lfs env > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c) > git version 2.7.4 (Apple Git-66)   - > Endpoint=https://THIRD-PARTY-LFS-SERVER/path/to/repo/info/lfs (auth=none) + > Endpoint=https://THIRD-PARTY-LFS-SERVER/path/to/repo/info/lfs (auth=none)   # Show the contents of .lfsconfig $ cat .lfsconfig [remote "origin"] - lfsurl = https://THIRD-PARTY-LFS-SERVER/path/to/repo + lfsurl = https://THIRD-PARTY-LFS-SERVER/path/to/repo ``` -3. 为使各用户的 {% data variables.large_files.product_name_short %} 配置相同,请向存储库提交自定义 `.lfsconfig` 文件。 +3. To keep the same {% data variables.large_files.product_name_short %} configuration for each user, commit a custom `.lfsconfig` file to the repository. ```shell $ git add .lfsconfig $ git commit -m "Adding LFS config file" ``` -3. 迁移任何现有的 {% data variables.large_files.product_name_short %} 资源。 有关详细信息,请参阅“[迁移到不同的 {% data variables.large_files.product_name_long %} 服务器](#migrating-to-a-different-git-large-file-storage-server)”。 +3. Migrate any existing {% data variables.large_files.product_name_short %} assets. For more information, see "[Migrating to a different {% data variables.large_files.product_name_long %} server](#migrating-to-a-different-git-large-file-storage-server)." -## 迁移到其他 Git Large File Storage 服务器 +## Migrating to a different Git Large File Storage server -迁移到其他 {% data variables.large_files.product_name_long %} 服务器之前,您必须将 {% data variables.large_files.product_name_short %} 配置为使用第三方服务器。 有关详细信息,请参阅“[配置 {% data variables.large_files.product_name_long %} 以使用第三方服务器](#configuring-git-large-file-storage-to-use-a-third-party-server)”。 +Before migrating to a different {% data variables.large_files.product_name_long %} server, you must configure {% data variables.large_files.product_name_short %} to use a third party server. For more information, see "[Configuring {% data variables.large_files.product_name_long %} to use a third party server](#configuring-git-large-file-storage-to-use-a-third-party-server)." -1. 使用第二个远端配置仓库。 +1. Configure the repository with a second remote. ```shell - $ git remote add NEW-REMOTE https://NEW-REMOTE-HOSTNAME/path/to/repo + $ git remote add NEW-REMOTE https://NEW-REMOTE-HOSTNAME/path/to/repo   $ git lfs env > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c) > git version 2.7.4 (Apple Git-66)   - > Endpoint=https://GITHUB-ENTERPRISE-HOST/path/to/repo/info/lfs (auth=basic) - > Endpoint (NEW-REMOTE)=https://NEW-REMOTE-HOSTNAME/path/to/repo/info/lfs (auth=none) + > Endpoint=https://GITHUB-ENTERPRISE-HOST/path/to/repo/info/lfs (auth=basic) + > Endpoint (NEW-REMOTE)=https://NEW-REMOTE-HOSTNAME/path/to/repo/info/lfs (auth=none) ``` -2. 从旧远端提取所有对象。 +2. Fetch all objects from the old remote. ```shell $ git lfs fetch origin --all > Scanning for all objects ever referenced... @@ -118,9 +130,9 @@ ms.locfileid: '145098674' > Git LFS: (16 of 16 files) 48.71 MB / 48.85 MB ``` -3. 将所有对象推送到新远端。 +3. Push all objects to the new remote. ```shell - $ git lfs push NEW-REMOTE --all + $ git lfs push NEW-REMOTE --all > Scanning for all objects ever referenced... > ✔ 16 objects found > Pushing objects... @@ -128,6 +140,6 @@ ms.locfileid: '145098674' ``` {% endif %} -## 延伸阅读 +## Further reading -- [{% data variables.large_files.product_name_long %} 项目站点](https://git-lfs.github.com/) +- [{% data variables.large_files.product_name_long %} project site](https://git-lfs.github.com/) diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md index 8d956611cc..08a8461a70 100644 --- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md @@ -1,12 +1,12 @@ --- -title: 自定义企业的用户消息 +title: Customizing user messages for your enterprise shortTitle: Customizing user messages redirect_from: - /enterprise/admin/user-management/creating-a-custom-sign-in-message - /enterprise/admin/user-management/customizing-user-messages-on-your-instance - /admin/user-management/customizing-user-messages-on-your-instance - /admin/user-management/customizing-user-messages-for-your-enterprise -intro: '您可以创建用户将在 {% data variables.product.product_location %} 上看到的自定义消息。' +intro: 'You can create custom messages that users will see on {% data variables.location.product_location %}.' versions: ghes: '*' ghae: '*' @@ -14,96 +14,112 @@ type: how_to topics: - Enterprise - Maintenance -ms.openlocfilehash: 08cd547cd79b1e731f439688f02b475db8db4d1d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147052054' --- -## 关于用户消息 +## About user messages -有几种类型的用户消息。 -- 出现在{% ifversion ghes %}登录或{% endif %}退出登录{% ifversion ghes or ghae %}页面上的消息 -- 必须忽略在弹出窗口中出现一次的强制性消息{% endif %}{% ifversion ghes or ghae %} -- 公告横幅,出现在每个页面的顶部{% endif %} +There are several types of user messages. +- Messages that appear on the {% ifversion ghes %}sign in or {% endif %}sign out page{% ifversion ghes or ghae %} +- Mandatory messages, which appear once in a pop-up window that must be dismissed{% endif %}{% ifversion ghes or ghae %} +- Announcement banners, which appear at the top of every page{% endif %} -{% ifversion ghes %} {% note %} +{% ifversion ghes %} +{% note %} -注意:如果使用 SAML 进行身份验证,登录页面将由标识提供者呈现,无法通过 {% data variables.product.prodname_ghe_server %} 进行自定义。 +**Note:** If you are using SAML for authentication, the sign in page is presented by your identity provider and is not customizable via {% data variables.product.prodname_ghe_server %}. {% endnote %} -您可以使用 Markdown 格式化消息。 有关详细信息,请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上编写和设置格式](/articles/about-writing-and-formatting-on-github/)”。 +You can use Markdown to format your message. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/)." -## 创建自定义登录消息 +## Creating a custom sign in message -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. {% ifversion ghes %}在“登录页面”的右侧{% else %}下方{% endif %},单击“添加消息”或“编辑消息” 。 -![{% ifversion ghes %}添加{% else %}编辑{% endif %}消息按钮](/assets/images/enterprise/site-admin-settings/edit-message.png) -6. 在“登录消息”下,输入想要用户看到的消息。 -![登录消息](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% ifversion ghes %} {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![预览按钮](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png) -8. 预览显示的消息。 -![呈现的登录消息](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png) {% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} {% endif %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +5. {% ifversion ghes %}To the right of{% else %}Under{% endif %} "Sign in page", click **Add message** or **Edit message**. +![{% ifversion ghes %}Add{% else %}Edit{% endif %} message button](/assets/images/enterprise/site-admin-settings/edit-message.png) +6. Under **Sign in message**, type the message you'd like users to see. +![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png){% ifversion ghes %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} +{% data reusables.enterprise_site_admin_settings.click-preview %} + ![Preview button](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png) +8. Review the rendered message. +![Sign in message rendered](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png) +{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} +{% endif %} -## 创建自定义退出消息 +## Creating a custom sign out message -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. {% ifversion ghes or ghae %}在“退出登录页面”的右侧{% else %}下方{% endif %},单击“添加消息”或“编辑消息” 。 -![“添加消息”按钮](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) -6. 在“退出登录消息”下,输入想要用户看到的消息。 -![签名 two_factor_auth_header 消息](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% ifversion ghes or ghae %} {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![预览按钮](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png) -8. 预览显示的消息。 -![呈现的退出登录消息](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png) {% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +5. {% ifversion ghes or ghae %}To the right of{% else %}Under{% endif %} "Sign out page", click **Add message** or **Edit message**. +![Add message button](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png) +6. Under **Sign out message**, type the message you'd like users to see. +![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% ifversion ghes or ghae %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} +{% data reusables.enterprise_site_admin_settings.click-preview %} + ![Preview button](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png) +8. Review the rendered message. +![Sign out message rendered](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png) +{% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} {% ifversion ghes or ghae %} -## 创建必读消息 +## Creating a mandatory message -您可以创建必读消息,保存后,{% data variables.product.product_name %} 将在所有用户首次登录时显示该消息。 该消息出现在弹出窗口中,用户必须忽略后才能使用 {% data variables.product.product_location %}。 +You can create a mandatory message that {% data variables.product.product_name %} will show to all users the first time they sign in after you save the message. The message appears in a pop-up window that the user must dismiss before the user can use {% data variables.location.product_location %}. -必读消息有多种用途。 +Mandatory messages have a variety of uses. -- 为新员工提供入职信息 -- 告诉用户如何获得 {% data variables.product.product_location %} 帮助 -- 确保所有用户阅读有关使用 {% data variables.product.product_location %} 的服务条款 +- Providing onboarding information for new employees +- Telling users how to get help with {% data variables.location.product_location %} +- Ensuring that all users read your terms of service for using {% data variables.location.product_location %} -如果消息中包含 Markdown 复选框,则用户必须选中所有复选框才能忽略消息。 例如,如果您在必读消息中包含服务条款,您可以要求每个用户选中复选框以确认他们阅读了这些条款。 +If you include Markdown checkboxes in the message, all checkboxes must be selected before the user can dismiss the message. For example, if you include your terms of service in the mandatory message, you can require that each user selects a checkbox to confirm the user has read the terms. -每次用户看到必读消息时,都会创建审核日志事件。 该事件包括用户看到的消息的版本。 有关详细信息,请参阅“[企业的审核日志事件](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)”。 +Each time a user sees a mandatory message, an audit log event is created. The event includes the version of the message that the user saw. For more information see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)." {% note %} -注意:如果更改了 {% data variables.product.product_location %} 的必读消息,已经确认该消息的用户将不会看到新消息。 +**Note:** If you change the mandatory message for {% data variables.location.product_location %}, users who have already acknowledged the message will not see the new message. {% endnote %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -1. 在“必读消息”的右侧,单击“添加消息”。 - ![添加必须消息按钮](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) -1. 在“Mandatory message(必读消息)”下面的文本框中输入消息。 - ![必读消息文本框](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) {% data reusables.enterprise_site_admin_settings.message-preview-save %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +1. To the right of "Mandatory message", click **Add message**. + ![Add mandatory message button](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) +1. Under "Mandatory message", in the text box, type your message. + ![Mandatory message text box](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) +{% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %} {% ifversion ghes or ghae %} -## 创建全局公告横幅 +## Creating a global announcement banner -您可以设置全局公告横幅,以便在每个页面顶部向所有用户显示。 +You can set a global announcement banner to be displayed to all users at the top of every page. -{% ifversion ghae or ghes %} 你也可以使用命令行实用工具或{% ifversion ghes %}使用 API 在管理 shell 中{% endif %}设置公告横幅。 有关详细信息,请参阅{% ifversion ghes %}“[命令行实用工具](/enterprise/admin/configuration/command-line-utilities#ghe-announce)”和{% endif %}“[{% data variables.product.prodname_enterprise %} 管理](/rest/reference/enterprise-admin#announcements)”。 +{% ifversion ghae or ghes %} +You can also set an announcement banner{% ifversion ghes %} in the administrative shell using a command line utility or{% endif %} using the API. For more information, see {% ifversion ghes %}"[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)" and {% endif %}"[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)." {% else %} -您还可以使用命令行工具在管理 shell 中设置公告横幅。 有关详细信息,请参阅“[命令行实用工具](/enterprise/admin/configuration/command-line-utilities#ghe-announce)”。 +You can also set an announcement banner in the administrative shell using a command line utility. For more information, see "[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-announce)." {% endif %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -1. {% ifversion ghes or ghae %}在“公告”的右侧{% else %}下方{% endif %},单击“添加公告”。 - ![“添加公告”按钮](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) -1. 在“Announcement(公告)”下的在文本字段中键入要显示在横幅中的公告。 - ![用于输入公告的文本字段](/assets/images/enterprise/site-admin-settings/announcement-text-field.png) -1. (可选)在“Expires on(到期日)”下,选择日历下拉菜单并单击一个到期日。 - ![用于选择到期日期的日历下拉菜单](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png){% ifversion ghe-announce-dismiss %} -1. (可选)若要允许每个用户关闭公告,请选择“用户可关闭”。 +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +1. {% ifversion ghes or ghae %}To the right of{% else %}Under{% endif %} "Announcement", click **Add announcement**. + ![Add announcement button](/assets/images/enterprise/site-admin-settings/add-announcement-button.png) +1. Under "Announcement", in the text field, type the announcement you want displayed in a banner. + ![Text field to enter announcement](/assets/images/enterprise/site-admin-settings/announcement-text-field.png) +1. Optionally, under "Expires on", select the calendar drop-down menu and click an expiration date. + ![Calendar drop-down menu to choose expiration date](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png){% ifversion ghe-announce-dismiss %} +1. Optionally, to allow each user to dismiss the announcement, select **User dismissible**. - ![“用户可关闭”复选框的屏幕截图](/assets/images/enterprise/site-admin-settings/user-dismissible-checkbox.png){% endif %} {% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %} + ![Screenshot of the "User dismissible" checkbox](/assets/images/enterprise/site-admin-settings/user-dismissible-checkbox.png){% endif %} +{% data reusables.enterprise_site_admin_settings.message-preview-save %} +{% endif %} diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md index 2bbd8ccb40..46f9801fb1 100644 --- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md +++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md @@ -1,5 +1,5 @@ --- -title: 挂起和取消挂起用户 +title: Suspending and unsuspending users redirect_from: - /enterprise/admin/articles/suspending-a-user - /enterprise/admin/articles/unsuspending-a-user @@ -8,7 +8,7 @@ redirect_from: - /enterprise/admin/articles/suspending-and-unsuspending-users - /enterprise/admin/user-management/suspending-and-unsuspending-users - /admin/user-management/suspending-and-unsuspending-users -intro: '如果用户离开公司或者调动到公司的其他部门,你应当移除或修改他们访问 {% data variables.product.product_location %} 的能力。' +intro: 'If a user leaves or moves to a different part of the company, you should remove or modify their ability to access {% data variables.location.product_location %}.' versions: ghes: '*' type: how_to @@ -18,16 +18,10 @@ topics: - Security - User account shortTitle: Manage user suspension -ms.openlocfilehash: d888678438f62fb585dac1cab4905ff02d8eb824 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146331902' --- -如果员工从公司离职,您可以暂停他们的 {% data variables.product.prodname_ghe_server %} 帐户,打开您的 {% data variables.product.prodname_enterprise %} 许可中的用户许可,同时保存他们创建的议题、评论、仓库、Gist 及其他数据。 被挂起的用户既无法登录您的实例,也无法推送或拉取代码。 +If employees leave the company, you can suspend their {% data variables.product.prodname_ghe_server %} accounts to open up user licenses in your {% data variables.product.prodname_enterprise %} license while preserving the issues, comments, repositories, gists, and other data they created. Suspended users cannot sign into your instance, nor can they push or pull code. -在您挂起用户时,变更将立即生效,并且不会通知用户。 如果用户尝试拉取仓库或推送到仓库,他们将收到此错误消息: +When you suspend a user, the change takes effect immediately with no notification to the user. If the user attempts to pull or push to a repository, they'll receive this error: ```shell $ git clone git@[hostname]:john-doe/test-repo.git @@ -36,65 +30,74 @@ ERROR: Your account is suspended. Please check with your installation administra fatal: The remote end hung up unexpectedly ``` -在挂起站点管理员之前,您必须将其降级为普通用户。 有关详细信息,请参阅“[推广或降级网站管理员](/enterprise/admin/user-management/promoting-or-demoting-a-site-administrator)”。 +Before suspending site administrators, you must demote them to regular users. For more information, see "[Promoting or demoting a site administrator](/enterprise/admin/user-management/promoting-or-demoting-a-site-administrator)." {% tip %} -注意:如果为 {% data variables.product.product_location %} [启用了 LDAP Sync](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync),则从 LDAP 目录服务器中删除用户时会将其自动挂起。 为您的实例启用 LDAP 同步后,将禁用普通用户挂起方法。 +**Note:** If [LDAP Sync is enabled](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync) for {% data variables.location.product_location %}, users are automatically suspended when they're removed from the LDAP directory server. When LDAP Sync is enabled for your instance, normal user suspension methods are disabled. {% endtip %} -## 从用户管理员仪表板挂起用户 - -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.search-user %} {% data reusables.enterprise_site_admin_settings.click-user %} {% data reusables.enterprise_site_admin_settings.admin-top-tab %} {% data reusables.enterprise_site_admin_settings.admin-tab %} -5. 在红色“危险区域”框的“帐户暂停”下,单击“暂停”。 -![“挂起”按钮](/assets/images/enterprise/site-admin-settings/suspend.png) -6. 提供挂起用户的原因。 -![挂起原因](/assets/images/enterprise/site-admin-settings/suspend-reason.png) - -## 从用户管理员仪表板取消挂起用户 - -挂起用户后,取消挂起用户的操作将立即可用。 用户将不会收到通知。 +## Suspending a user from the user admin dashboard {% data reusables.enterprise_site_admin_settings.access-settings %} -3. 在左侧边栏中,单击“挂起用户”。 -![“挂起用户”选项卡](/assets/images/enterprise/site-admin-settings/user/suspended-users-tab.png) -2. 单击您想要取消挂起的用户帐户的名称。 -![挂起用户](/assets/images/enterprise/site-admin-settings/user/suspended-user.png) {% data reusables.enterprise_site_admin_settings.admin-top-tab %} {% data reusables.enterprise_site_admin_settings.admin-tab %} -4. 在红色“危险区域”框的“帐户暂停”下,单击“取消挂起”。 -![“取消挂起”按钮](/assets/images/enterprise/site-admin-settings/unsuspend.png) -5. 提供取消挂起用户的原因。 -![取消挂起原因](/assets/images/enterprise/site-admin-settings/unsuspend-reason.png) +{% data reusables.enterprise_site_admin_settings.search-user %} +{% data reusables.enterprise_site_admin_settings.click-user %} +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +5. Under "Account suspension," in the red Danger Zone box, click **Suspend**. +![Suspend button](/assets/images/enterprise/site-admin-settings/suspend.png) +6. Provide a reason to suspend the user. +![Suspend reason](/assets/images/enterprise/site-admin-settings/suspend-reason.png) -## 从命令行挂起用户 +## Unsuspending a user from the user admin dashboard + +As when suspending a user, unsuspending a user takes effect immediately. The user will not be notified. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +3. In the left sidebar, click **Suspended users**. +![Suspended users tab](/assets/images/enterprise/site-admin-settings/user/suspended-users-tab.png) +2. Click the name of the user account that you would like to unsuspend. +![Suspended user](/assets/images/enterprise/site-admin-settings/user/suspended-user.png) +{% data reusables.enterprise_site_admin_settings.admin-top-tab %} +{% data reusables.enterprise_site_admin_settings.admin-tab %} +4. Under "Account suspension," in the red Danger Zone box, click **Unsuspend**. +![Unsuspend button](/assets/images/enterprise/site-admin-settings/unsuspend.png) +5. Provide a reason to unsuspend the user. +![Unsuspend reason](/assets/images/enterprise/site-admin-settings/unsuspend-reason.png) + +## Suspending a user from the command line {% data reusables.enterprise_installation.ssh-into-instance %} -2. 使用要挂起的用户名运行 [ghe-user-suspend](/enterprise/admin/guides/installation/command-line-utilities#ghe-user-suspend)。 +2. Run [ghe-user-suspend](/enterprise/admin/guides/installation/command-line-utilities#ghe-user-suspend) with the username to suspend. ```shell - $ ghe-user-suspend username + $ ghe-user-suspend USERNAME ``` -## 为挂起的用户创建自定义消息 +## Creating a custom message for suspended users -您可以创建自定义消息,被挂起的用户会在尝试登录时看到此消息。 +You can create a custom message that suspended users will see when attempting to sign in. -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -5. 单击“添加消息”。 -![添加消息](/assets/images/enterprise/site-admin-settings/add-message.png) -6. 在“挂起的用户消息”框中键入消息。 您可以输入 Markdown,或者使用 Markdown 工具栏设置消息的样式。 -![已挂起用户消息](/assets/images/enterprise/site-admin-settings/suspended-user-message.png) -7. 在“已挂起用户消息”字段下,单击“预览”按钮,以查看呈现的消息。 -![预览按钮](/assets/images/enterprise/site-admin-settings/suspended-user-message-preview-button.png) -8. 预览显示的消息。 -![呈现的已挂起用户消息](/assets/images/enterprise/site-admin-settings/suspended-user-message-rendered.png) {% data reusables.enterprise_site_admin_settings.save-changes %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.messages-tab %} +5. Click **Add message**. +![Add message](/assets/images/enterprise/site-admin-settings/add-message.png) +6. Type your message into the **Suspended user message** box. You can type Markdown, or use the Markdown toolbar to style your message. +![Suspended user message](/assets/images/enterprise/site-admin-settings/suspended-user-message.png) +7. Click the **Preview** button under the **Suspended user message** field to see the rendered message. +![Preview button](/assets/images/enterprise/site-admin-settings/suspended-user-message-preview-button.png) +8. Review the rendered message. +![Suspended user message rendered](/assets/images/enterprise/site-admin-settings/suspended-user-message-rendered.png) +{% data reusables.enterprise_site_admin_settings.save-changes %} -## 从命令行取消挂起用户 +## Unsuspending a user from the command line {% data reusables.enterprise_installation.ssh-into-instance %} -2. 使用用户名运行 [ghe-user-unsuspend](/enterprise/admin/guides/installation/command-line-utilities#ghe-user-unsuspend) 以取消挂起。 +2. Run [ghe-user-unsuspend](/enterprise/admin/guides/installation/command-line-utilities#ghe-user-unsuspend) with the username to unsuspend. ```shell - $ ghe-user-unsuspend username + $ ghe-user-unsuspend USERNAME ``` -## 延伸阅读 -- “[挂起用户](/rest/reference/enterprise-admin#suspend-a-user)” +## Further reading +- "[Suspend a user](/rest/reference/enterprise-admin#suspend-a-user)" diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md index 15ff156ea0..39a210fec7 100644 --- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: 查看和管理用户对企业的 SAML 访问 -intro: 您可以查看和撤销企业成员的链接身份、活动会话和授权凭据。 +title: Viewing and managing a user's SAML access to your enterprise +intro: 'You can view and revoke an enterprise member''s linked identity, active sessions, and authorized credentials.' permissions: Enterprise owners can view and manage a member's SAML access to an organization. redirect_from: - /github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account @@ -12,39 +12,50 @@ versions: topics: - Enterprise shortTitle: View & manage SAML access -ms.openlocfilehash: 25c706f5aff79f65adf4968546a9a8123794f583 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145098945' --- -## 关于对企业帐户的 SAML 访问 +## About SAML access to your enterprise account -当您为企业帐户启用 SAML 单点登录时,每个企业成员都可以将其身份提供商 (IdP) 上的外部身份链接到 {% data variables.product.product_location %} 上的现有帐户。 {% data reusables.saml.about-saml-access-enterprise-account %} +When you enable SAML single sign-on for your enterprise account, each enterprise member can link their external identity on your identity provider (IdP) to their existing account on {% data variables.location.product_location %}. {% data reusables.saml.about-saml-access-enterprise-account %} -如果您的企业使用 {% data variables.product.prodname_emus %},成员将使用通过您的 IdP 预配的帐户。 {% data variables.product.prodname_managed_users_caps %} 将不会在 {% data variables.product.product_name %} 上使用他们现有的用户帐户。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)”。 +If your enterprise is uses {% data variables.product.prodname_emus %}, your members will use accounts provisioned through your IdP. {% data variables.enterprise.prodname_managed_users_caps %} will not use their existing user account on {% data variables.product.product_name %}. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." -## 查看和撤销链接的身份 +## Viewing and revoking a linked identity {% data reusables.saml.about-linked-identities %} -如果您的企业使用 {% data variables.product.prodname_emus %},您将无法从 {% data variables.product.product_name %} 上的企业中取消或删除用户帐户。 您需要对企业的 {% data variables.product.prodname_managed_users %} 进行的任何更改都应该通过您的 IdP 进行。 +If your enterprise uses {% data variables.product.prodname_emus %}, you will not be able to deprovision or remove user accounts from the enterprise on {% data variables.product.product_name %}. Any changes you need to make to your enterprise's {% data variables.enterprise.prodname_managed_users %} should be made through your IdP. {% data reusables.identity-and-permissions.revoking-identity-team-sync %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} {% data reusables.saml.click-person-revoke-identity %} {% data reusables.saml.saml-identity-linked %} {% data reusables.saml.view-sso-identity %} {% data reusables.saml.revoke-sso-identity %} {% data reusables.saml.confirm-revoke-identity %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.people-tab %} +{% data reusables.saml.click-person-revoke-identity %} +{% data reusables.saml.saml-identity-linked %} +{% data reusables.saml.view-sso-identity %} +{% data reusables.saml.revoke-sso-identity %} +{% data reusables.saml.confirm-revoke-identity %} -## 查看和撤销活动的 SAML 会话 +## Viewing and revoking an active SAML session -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} {% data reusables.saml.click-person-revoke-session %} {% data reusables.saml.saml-identity-linked %} {% data reusables.saml.view-saml-sessions %} {% data reusables.saml.revoke-saml-session %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.people-tab %} +{% data reusables.saml.click-person-revoke-session %} +{% data reusables.saml.saml-identity-linked %} +{% data reusables.saml.view-saml-sessions %} +{% data reusables.saml.revoke-saml-session %} -## 查看和撤销授权的凭据 +## Viewing and revoking authorized credentials {% data reusables.saml.about-authorized-credentials %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} {% data reusables.saml.click-person-revoke-credentials %} {% data reusables.saml.saml-identity-linked %} {% data reusables.saml.view-authorized-credentials %} {% data reusables.saml.revoke-authorized-credentials %} {% data reusables.saml.confirm-revoke-credentials %} +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.people-tab %} +{% data reusables.saml.click-person-revoke-credentials %} +{% data reusables.saml.saml-identity-linked %} +{% data reusables.saml.view-authorized-credentials %} +{% data reusables.saml.revoke-authorized-credentials %} +{% data reusables.saml.confirm-revoke-credentials %} -## 延伸阅读 +## Further reading -- “[查看和管理成员对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)” +- "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md index 0514107389..0596124afa 100644 --- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md @@ -114,7 +114,7 @@ If you use {% data variables.product.prodname_vss_ghe %}, the list of pending in ![Screenshot of the "Members", "Administrators", and "Outside collaborators" tabs](/assets/images/help/enterprises/pending-invitations-type-tabs.png) -## Viewing suspended members in an {% data variables.product.prodname_emu_enterprise %} +## Viewing suspended members in an {% data variables.enterprise.prodname_emu_enterprise %} If your enterprise uses {% data variables.product.prodname_emus %}, you can also view suspended users. Suspended users are members who have been deprovisioned after being unassigned from the {% data variables.product.prodname_emu_idp_application %} application or deleted from the identity provider. For more information, see "[About Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users)." diff --git a/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md b/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md index 41d99ff0a0..f0f6adac03 100644 --- a/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md +++ b/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md @@ -1,6 +1,6 @@ --- -title: 关于迁移 -intro: '迁移是将数据从源位置({% data variables.product.prodname_dotcom_the_website %} 组织或 {% data variables.product.prodname_ghe_server %} 实例)转移到目标 {% data variables.product.prodname_ghe_server %} 实例的过程。 在更换平台或或升级实例上的硬件时,可以使用迁移转移数据。' +title: About migrations +intro: 'A migration is the process of transferring data from a *source* location (either a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance. Migrations can be used to transfer your data when changing platforms or upgrading hardware on your instance.' redirect_from: - /enterprise/admin/migrations/about-migrations - /enterprise/admin/user-management/about-migrations @@ -11,47 +11,41 @@ type: overview topics: - Enterprise - Migration -ms.openlocfilehash: accb9c62655f8825077a00e05a93182b36cd6e8d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147541181' --- -## 迁移的类型 +## Types of migrations -您可以执行三种类型的迁移: +There are three types of migrations you can perform: -- 从 {% data variables.product.prodname_ghe_server %} 实例迁移到另一个 {% data variables.product.prodname_ghe_server %} 实例。 您可以迁移实例上由任何用户或组织拥有的任意数量的仓库。 在执行迁移之前,您必须具有两个实例的站点管理员访问权限。 -- 从 {% data variables.product.prodname_dotcom_the_website %} 组织迁移到 {% data variables.product.prodname_ghe_server %} 实例。 您可以迁移由组织拥有的任意数量的仓库。 在执行迁移前,必须拥有 {% data variables.product.prodname_dotcom_the_website %} 组织的[管理访问权限](/enterprise/user/articles/permission-levels-for-an-organization/)和目标实例的站点管理员访问权限。 -- “试运行”是将数据导入[暂存实例](/enterprise/admin/guides/installation/setting-up-a-staging-instance/)的迁移。 这些试运行非常有用,可用于查看在向 {% data variables.product.product_location %} 应用迁移后将要发生的变化。 强烈建议你先在暂存实例上执行试运行,然后再将数据导入生产实例。 +- A migration from a {% data variables.product.prodname_ghe_server %} instance to another {% data variables.product.prodname_ghe_server %} instance. You can migrate any number of repositories owned by any user or organization on the instance. Before performing a migration, you must have site administrator access to both instances. +- A migration from a {% data variables.product.prodname_dotcom_the_website %} organization to a {% data variables.product.prodname_ghe_server %} instance. You can migrate any number of repositories owned by the organization. Before performing a migration, you must have [administrative access](/enterprise/user/articles/permission-levels-for-an-organization/) to the {% data variables.product.prodname_dotcom_the_website %} organization as well as site administrator access to the target instance. +- *Trial runs* are migrations that import data to a [staging instance](/enterprise/admin/guides/installation/setting-up-a-staging-instance/). These can be useful to see what *would* happen if a migration were applied to {% data variables.location.product_location %}. **We strongly recommend that you perform a trial run on a staging instance before importing data to your production instance.** -## 迁移的数据 +## Migrated data -在迁移中,一切都围绕仓库进行。 与仓库关联的大多数数据都可以迁移。 例如,组织内的存储库将迁移存储库和组织,以及与该存储库关联的任何用户、团队、议题和拉取请求。 +In a migration, everything revolves around a repository. Most data associated with a repository can be migrated. For example, a repository within an organization will migrate the repository *and* the organization, as well as any users, teams, issues, and pull requests associated with the repository. -下表中的项可随仓库一起迁移。 迁移数据列表中未显示的任何项都无法迁移,包括 {% data variables.large_files.product_name_short %} 资产。 +The items in the table below can be migrated with a repository. Any items not shown in the list of migrated data can not be migrated, including {% data variables.large_files.product_name_short %} assets. {% data reusables.enterprise_migrations.fork-persistence %} -| 与迁移的仓库关联的数据 | 备注 | +| Data associated with a migrated repository | Notes | |---------------------------------------------|--------| -| 用户 | 将重写用户的 @mentions,使其与目标匹配。 -| 组织 | 将迁移组织的名称和详细信息。 -| 存储库 | Git 树、blob、提交和行的链接将重写以匹配目标。 迁移程序将遵循三个仓库重定向的最大值。 内部存储库作为专用存储库迁移。 存档状态未设置。 -| Wiki | 将迁移所有 wiki 数据。 -| Teams | 将重写团队的 @mentions,使其与目标匹配。 -| 里程碑 | 将保留时间戳。 -| 项目板 | 将迁移与仓库和拥有仓库的组织关联的项目板。 -| 问题 | 将保留问题引用和时间戳。 -| 问题评论 | 将针对目标实例重写评论的交叉引用。 -| 拉取请求 | 将重写拉取请求的交叉引用以匹配目标。 将保留时间戳。 -| 拉取请求审查 | 将迁移拉取请求审查和关联的数据。 -| 拉取请求审查评论 | 将针对目标实例重写评论的交叉引用。 将保留时间戳。 -| 提交注释 | 将针对目标实例重写评论的交叉引用。 将保留时间戳。 -| 版本 | 将迁移所有版本数据。 -| 在拉取请求或问题上进行的操作 | 将保留对拉取请求或问题的所有修改(例如,分配用户、重命名标题和修改标签)以及每个操作的时间戳。 -| 文件附件 | [议题和拉取请求中的文件附件](/articles/file-attachments-on-issues-and-pull-requests)将得到迁移。 在迁移过程中,您可以选择将此禁用。 -| Webhook | 仅迁移有效的 web 挂钩。 -| 仓库部署密钥 | 将迁移仓库部署密钥。 -| 受保护的分支 | 将迁移受保护分支设置和关联的数据。 +| Users | **@mentions** of users are rewritten to match the target. +| Organizations | An organization's name and details are migrated. +| Repositories | Links to Git trees, blobs, commits, and lines are rewritten to match the target. The migrator follows a maximum of three repository redirects. Internal repositories are migrated as private repositories. Archive status is unset. +| Wikis | All wiki data is migrated. +| Teams | **@mentions** of teams are rewritten to match the target. +| Milestones | Timestamps are preserved. +| Project boards | Project boards associated with the repository and with the organization that owns the repository are migrated. +| Issues | Issue references and timestamps are preserved. +| Issue comments | Cross-references to comments are rewritten for the target instance. +| Pull requests | Cross-references to pull requests are rewritten to match the target. Timestamps are preserved. +| Pull request reviews | Pull request reviews and associated data are migrated. +| Pull request review comments | Cross-references to comments are rewritten for the target instance. Timestamps are preserved. +| Commit comments | Cross-references to comments are rewritten for the target instance. Timestamps are preserved. +| Releases | All releases data is migrated. +| Actions taken on pull requests or issues | All modifications to pull requests or issues, such as assigning users, renaming titles, and modifying labels are preserved, along with timestamps for each action. +| File attachments | [File attachments on issues and pull requests](/articles/file-attachments-on-issues-and-pull-requests) are migrated. You can choose to disable this as part of the migration. +| Webhooks | Only active webhooks are migrated. +| Repository deploy keys | Repository deploy keys are migrated. +| Protected branches | Protected branch settings and associated data are migrated. diff --git a/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md b/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md index af27a2bcd6..857f19fd91 100644 --- a/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: 从企业导出迁移数据 -intro: '要更改平台或从试用实例迁移到生产实例,可以通过准备实例、锁定仓库和生成迁移存档来从 {% data variables.product.prodname_ghe_server %} 实例导出迁移数据。' +title: Exporting migration data from your enterprise +intro: 'To change platforms or move from a trial instance to a production instance, you can export migration data from a {% data variables.product.prodname_ghe_server %} instance by preparing the instance, locking the repositories, and generating a migration archive.' redirect_from: - /enterprise/admin/guides/migrations/exporting-migration-data-from-github-enterprise - /enterprise/admin/migrations/exporting-migration-data-from-github-enterprise-server @@ -18,49 +18,43 @@ topics: - Enterprise - Migration shortTitle: Export from your enterprise -ms.openlocfilehash: 5bff2e21a493cc35448d68daf87aa87ed82a8a28 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145098943' --- -## 准备 {% data variables.product.prodname_ghe_server %} 源实例 +## Preparing the {% data variables.product.prodname_ghe_server %} source instance -1. 验证您在 {% data variables.product.prodname_ghe_server %} 源上是站点管理员。 执行此操作的最佳方法是验证是否可以[通过 SSH 连接到实例](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/)。 +1. Verify that you are a site administrator on the {% data variables.product.prodname_ghe_server %} source. The best way to do this is to verify that you can [SSH into the instance](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/). -2. 在 {% data variables.product.prodname_ghe_server %} 源实例上{% data reusables.enterprise_migrations.token-generation %}。 +2. {% data reusables.enterprise_migrations.token-generation %} on the {% data variables.product.prodname_ghe_server %} source instance. {% data reusables.enterprise_migrations.make-a-list %} -## 导出 {% data variables.product.prodname_ghe_server %} 源仓库 +## Exporting the {% data variables.product.prodname_ghe_server %} source repositories {% data reusables.enterprise_migrations.locking-repositories %} {% data reusables.enterprise_installation.ssh-into-instance %} -2. 要准备需要导出的存储库,请使用 `ghe-migrator add` 命令和存储库的 URL: - * 如果要锁定存储库,请在命令后附加 `--lock`。 如果要执行试用运行,则不需要 `--lock`。 +2. To prepare a repository for export, use the `ghe-migrator add` command with the repository's URL: + * If you're locking the repository, append the command with `--lock`. If you're performing a trial run, `--lock` is not needed. ```shell - $ ghe-migrator add https://hostname/username/reponame --lock + $ ghe-migrator add https://HOSTNAME/USERNAME/REPO-NAME --lock ``` - * 可以通过将 `--exclude_attachments` 附加到命令来排除文件附件。 {% data reusables.enterprise_migrations.exclude-file-attachments %} - * 要一次准备多个将导出的存储库,请创建一个文本文件并在单独的行中列出每个存储库 URL,然后运行包含 `ghe-migrator add` 标志和文本文件路径的 `-i` 命令。 + * You can exclude file attachments by appending `--exclude_attachments` to the command. {% data reusables.enterprise_migrations.exclude-file-attachments %} + * To prepare multiple repositories at once for export, create a text file listing each repository URL on a separate line, and run the `ghe-migrator add` command with the `-i` flag and the path to your text file. ```shell - $ ghe-migrator add -i PATH/TO/YOUR/REPOSITORY_URLS.txt + $ ghe-migrator add -i PATH/TO/YOUR/REPOSITORY_URL.txt ``` -3. 出现提示时,请输入您的 {% data variables.product.prodname_ghe_server %} 用户名: +3. When prompted, enter your {% data variables.product.prodname_ghe_server %} username: ```shell Enter username authorized for migration: admin ``` -4. 系统提示输入个人访问令牌时,请输入你在“[准备 {% data variables.product.prodname_ghe_server %} 源实例](#preparing-the-github-enterprise-server-source-instance)”中创建的访问令牌: +4. When prompted for a {% data variables.product.pat_generic %}, enter the access token you created in "[Preparing the {% data variables.product.prodname_ghe_server %} source instance](#preparing-the-github-enterprise-server-source-instance)": ```shell - Enter personal access token: ************** + Enter {% data variables.product.pat_generic %}: ************** ``` -5. 在 `ghe-migrator add` 完成后,它将打印自身生成并用于标识此导出的唯一的“迁移 GUID”以及添加到导出中的资源列表。 你将使用它在后续 `ghe-migrator add` 和 `ghe-migrator export` 步骤中生成的迁移 GUID,来指示 `ghe-migrator` 继续对同一导出进行操作。 +5. When `ghe-migrator add` has finished it will print the unique "Migration GUID" that it generated to identify this export as well as a list of the resources that were added to the export. You will use the Migration GUID that it generated in subsequent `ghe-migrator add` and `ghe-migrator export` steps to tell `ghe-migrator` to continue operating on the same export. ```shell > 101 models added to export - > Migration GUID: example-migration-guid + > Migration GUID: EXAMPLE-MIGRATION-GUID > Number of records in this migration: > users | 5 > organizations | 1 @@ -79,33 +73,33 @@ ms.locfileid: '145098943' > attachments | 4 > projects | 2 ``` - 每次您添加包含现有迁移 GUID 的新仓库时,它都会更新现有导出。 如果在没有迁移 GUID的情况下再次运行 `ghe-migrator add`,将会启动新的导出并生成新的迁移 GUID。 开始准备要导入的迁移时,不要再次使用在导出过程中生成的迁移 GUID。 + Each time you add a new repository with an existing Migration GUID it will update the existing export. If you run `ghe-migrator add` again without a Migration GUID it will start a new export and generate a new Migration GUID. **Do not re-use the Migration GUID generated during an export when you start preparing your migration for import**. -3. 如果锁定了源存储库,则可以使用 `ghe-migrator target_url` 命令,在链接到存储库新位置的存储库页面上设置自定义锁定消息。 传递源仓库 URL、目标仓库 URL 和第 5 步中的迁移 GUID: +3. If you locked the source repository, you can use the `ghe-migrator target_url` command to set a custom lock message on the repository page that links to the repository's new location. Pass the source repository URL, the target repository URL, and the Migration GUID from Step 5: ```shell - $ ghe-migrator target_url https://hostname/username/reponame https://target_hostname/target_username/target_reponame -g MIGRATION_GUID + $ ghe-migrator target_url https://HOSTNAME/USERNAME/REPO-NAME https://TARGET-HOSTNAME/TARGET-USER-NAME/TARGET-REPO-NAME -g MIGRATION-GUID ``` -6. 若要将更多存储库添加到同一导出,请使用带有 `-g` 标志的 `ghe-migrator add` 命令。 您需要传入新仓库 URL 和第 5 步中的迁移 GUID: +6. To add more repositories to the same export, use the `ghe-migrator add` command with the `-g` flag. You'll pass in the new repository URL and the Migration GUID from Step 5: ```shell - $ ghe-migrator add https://hostname/username/other_reponame -g MIGRATION_GUID --lock + $ ghe-migrator add https://HOSTNAME/USERNAME/OTHER-REPO-NAME -g MIGRATION-GUID --lock ``` -7. 添加完存储库后,请使用包含 `-g` 标志和第 5 步中的迁移 GUID 的 `ghe-migrator export` 命令生成迁移存档: +7. When you've finished adding repositories, generate the migration archive using the `ghe-migrator export` command with the `-g` flag and the Migration GUID from Step 5: ```shell - $ ghe-migrator export -g MIGRATION_GUID - > Archive saved to: /data/github/current/tmp/MIGRATION_GUID.tar.gz + $ ghe-migrator export -g MIGRATION-GUID + > Archive saved to: /data/github/current/tmp/MIGRATION-GUID.tar.gz ``` * {% data reusables.enterprise_migrations.specify-staging-path %} -8. 关闭与 {% data variables.product.product_location %} 的连接: +8. Close the connection to {% data variables.location.product_location %}: ```shell $ exit > logout - > Connection to hostname closed. + > Connection to HOSTNAME closed. ``` -9. 使用 [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) 命令将迁移存档复制到计算机。 存档文件将使用迁移 GUID 命名: +9. Copy the migration archive to your computer using the [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) command. The archive file will be named with the Migration GUID: ```shell - $ scp -P 122 admin@hostname:/data/github/current/tmp/MIGRATION_GUID.tar.gz ~/Desktop + $ scp -P 122 admin@HOSTNAME:/data/github/current/tmp/MIGRATION-GUID.tar.gz ~/Desktop ``` {% data reusables.enterprise_migrations.ready-to-import-migrations %} diff --git a/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md b/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md index 5559486f69..ac34326e09 100644 --- a/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md +++ b/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md @@ -1,6 +1,6 @@ --- -title: 将数据迁移到企业或从企业迁移数据 -intro: '可以从 {% data variables.product.prodname_ghe_server %} 或 {% data variables.product.prodname_dotcom_the_website %} 导出用户、组织和存储库数据,然后将此数据导入至 {% data variables.product.product_location %}。' +title: Migrating data to and from your enterprise +intro: 'You can export user, organization, and repository data from {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_dotcom_the_website %}, then import that data into {% data variables.location.product_location %}.' redirect_from: - /enterprise/admin/articles/moving-a-repository-from-github-com-to-github-enterprise - /enterprise/admin/categories/migrations-and-upgrades @@ -18,11 +18,5 @@ children: - /migrating-data-to-your-enterprise - /importing-data-from-third-party-version-control-systems shortTitle: Migration for an enterprise -ms.openlocfilehash: 1f08da59c2b9330f2230f8377230132bc2a57704 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145098942' --- diff --git a/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md b/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md index 89227e5aa8..b19fb060b4 100644 --- a/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: 将数据迁移到企业 -intro: '生成迁移存档后,您可以将数据导入目标 {% data variables.product.prodname_ghe_server %} 实例。 在将变更永久应用到目标实例之前,您需要检查变更,查看有无潜在的冲突。' +title: Migrating data to your enterprise +intro: 'After generating a migration archive, you can import the data to your target {% data variables.product.prodname_ghe_server %} instance. You''ll be able to review changes for potential conflicts before permanently applying the changes to your target instance.' redirect_from: - /enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise - /enterprise/admin/migrations/applying-the-imported-data-on-github-enterprise-server @@ -19,27 +19,21 @@ topics: - Enterprise - Migration shortTitle: Import to your enterprise -ms.openlocfilehash: 19bd9e1e8cee072e8a8f00861e2d8f876b5b8450 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717667' --- -## 在 {% data variables.product.prodname_ghe_server %} 上应用导入的数据 +## Applying the imported data on {% data variables.product.prodname_ghe_server %} -在将数据迁移到企业之前,您必须准备数据并解决任何冲突。 有关详细信息,请参阅“[准备将数据迁移到企业](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)”。 +Before you can migrate data to your enterprise, you must prepare the data and resolve any conflicts. For more information, see "[Preparing to migrate data to your enterprise](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)." -在准备数据并解决冲突后,您可以将导入的数据应用于 {% data variables.product.product_name %}。 +After you prepare the data and resolve conflicts, you can apply the imported data on {% data variables.product.product_name %}. {% data reusables.enterprise_installation.ssh-into-target-instance %} -2. 使用 `ghe-migrator import` 命令启动导入过程。 需要: - * 迁移 GUID。 有关详细信息,请参阅“[准备将数据迁移到企业](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)”。 - * 用于身份验证的个人访问令牌。 您使用的个人访问令牌仅用于站点管理员身份验证,不需要任何特定范围。 有关详细信息,请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 +2. Using the `ghe-migrator import` command, start the import process. You'll need: + * Your Migration GUID. For more information, see "[Preparing to migrate data to your enterprise](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)." + * Your {% data variables.product.pat_generic %} for authentication. The {% data variables.product.pat_generic %} that you use is only for authentication as a site administrator, and does not require any specific scope{% ifversion pat-v2 %} or permissions{% endif %}. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." ```shell - $ ghe-migrator import /home/admin/MIGRATION_GUID.tar.gz -g MIGRATION_GUID -u username -p TOKEN + $ ghe-migrator import /home/admin/MIGRATION-GUID.tar.gz -g MIGRATION-GUID -u USERNAME -p TOKEN > Starting GitHub::Migrator > Import 100% complete / @@ -47,110 +41,113 @@ ms.locfileid: '147717667' * {% data reusables.enterprise_migrations.specify-staging-path %} -## 检查迁移数据 +## Reviewing migration data -默认情况下,`ghe-migrator audit` 返回每条记录。 它还可以让您按以下方式筛选记录: +By default, `ghe-migrator audit` returns every record. It also allows you to filter records by: - * 记录的类型。 - * 记录的状态。 + * The types of records. + * The state of the records. -记录类型与[迁移数据](/enterprise/admin/guides/migrations/about-migrations/#migrated-data)中的记录类型相匹配。 +The record types match those found in the [migrated data](/enterprise/admin/guides/migrations/about-migrations/#migrated-data). -## 记录类型筛选器 +## Record type filters -| 记录类型 | 筛选器名称 | +| Record type | Filter name | |-----------------------|--------| -| 用户 | `user` -| 组织 | `organization` -| 存储库 | `repository` +| Users | `user` +| Organizations | `organization` +| Repositories | `repository` | Teams | `team` -| 里程碑 | `milestone` -| 项目板 | `project` -| 问题 | `issue` -| 问题评论 | `issue_comment` -| 拉取请求 | `pull_request` -| 拉取请求审查 | `pull_request_review` -| 提交注释 | `commit_comment` -| 拉取请求审查评论 | `pull_request_review_comment` -| 版本 | `release` -| 在拉取请求或问题上进行的操作 | `issue_event` -| 受保护的分支 | `protected_branch` +| Milestones | `milestone` +| Project boards | `project` +| Issues | `issue` +| Issue comments | `issue_comment` +| Pull requests | `pull_request` +| Pull request reviews | `pull_request_review` +| Commit comments | `commit_comment` +| Pull request review comments | `pull_request_review_comment` +| Releases | `release` +| Actions taken on pull requests or issues | `issue_event` +| Protected branches | `protected_branch` -## 记录状态筛选器 +## Record state filters -| 记录状态 | 说明 | +| Record state | Description | |-----------------|----------------| -| `export` | 将导出记录。 | -| `import` | 将导入记录。 | -| `map` | 将映射记录。 | -| `rename` | 将重命名记录。 | -| `merge` | 将合并记录。 | -| `exported` | 已成功导出记录。 | -| `imported` | 已成功导入记录。 | -| `mapped` | 已成功映射记录。 | -| `renamed` | 已成功重命名记录。 | -| `merged` | 已成功合并记录。 | -| `failed_export` | 记录导出失败。 | -| `failed_import` | 记录导入失败。 | -| `failed_map` | 记录映射失败。 | -| `failed_rename` | 记录重命名失败。 | -| `failed_merge` | 记录合并失败。 | +| `export` | The record will be exported. | +| `import` | The record will be imported. | +| `map` | The record will be mapped. | +| `rename` | The record will be renamed. | +| `merge` | The record will be merged. | +| `exported` | The record was successfully exported. | +| `imported` | The record was successfully imported. | +| `mapped` | The record was successfully mapped. | +| `renamed` | The record was successfully renamed. | +| `merged` | The record was successfully merged. | +| `failed_export` | The record failed to export. | +| `failed_import` | The record failed to be imported. | +| `failed_map` | The record failed to be mapped. | +| `failed_rename` | The record failed to be renamed. | +| `failed_merge` | The record failed to be merged. | -## 筛选审核的记录 +## Filtering audited records -通过 `ghe-migrator audit` 命令,可以使用 `-m` 标志根据记录类型进行筛选。 同样,可以使用 `-s` 标志筛选导入状态。 命令如下所示: +With the `ghe-migrator audit` command, you can filter based on the record type using the `-m` flag. Similarly, you can filter on the import state using the `-s` flag. The command looks like this: ```shell -$ ghe-migrator audit -m RECORD_TYPE -s STATE -g MIGRATION_GUID +$ ghe-migrator audit -m RECORD_TYPE -s STATE -g MIGRATION-GUID ``` -例如,要查看每个成功导入的组织和团队,您可以输入: +For example, to view every successfully imported organization and team, you would enter: ```shell -$ ghe-migrator audit -m organization,team -s mapped,renamed -g MIGRATION_GUID +$ ghe-migrator audit -m organization,team -s mapped,renamed -g MIGRATION-GUID > model_name,source_url,target_url,state > organization,https://gh.source/octo-org/,https://ghe.target/octo-org/,renamed ``` -**我们强烈建议审核每个失败的导入。** 为此,你将输入: +**We strongly recommend auditing every import that failed.** To do that, you will enter: ```shell -$ ghe-migrator audit -s failed_import,failed_map,failed_rename,failed_merge -g MIGRATION_GUID +$ ghe-migrator audit -s failed_import,failed_map,failed_rename,failed_merge -g MIGRATION-GUID > model_name,source_url,target_url,state > user,https://gh.source/octocat,https://gh.target/octocat,failed > repository,https://gh.source/octo-org/octo-project,https://ghe.target/octo-org/octo-project,failed ``` -如果您对失败的导入有任何疑问,请联系 {% data variables.contact.contact_ent_support %}。 +If you have any concerns about failed imports, contact {% data variables.contact.contact_ent_support %}. -## 在 {% data variables.product.prodname_ghe_server %} 上完成导入 +## Completing the import on {% data variables.product.prodname_ghe_server %} -在迁移应用到目标实例并且您已审查迁移后,您需要解锁仓库并将其从源中删除。 我们建议等待两周再删除您的源数据,以便确保所有数据都能按预期运行。 +After your migration is applied to your target instance and you have reviewed the migration, you''ll unlock the repositories and delete them off the source. Before deleting your source data we recommend waiting around two weeks to ensure that everything is functioning as expected. -## 在目标实例上解锁仓库 +## Unlocking repositories on the target instance -{% data reusables.enterprise_installation.ssh-into-instance %} {% data reusables.enterprise_migrations.unlocking-on-instances %} +{% data reusables.enterprise_installation.ssh-into-instance %} +{% data reusables.enterprise_migrations.unlocking-on-instances %} -## 在源上解锁仓库 +## Unlocking repositories on the source -### 从 {% data variables.product.prodname_dotcom_the_website %} 上的组织解锁仓库 +### Unlocking repositories from an organization on {% data variables.product.prodname_dotcom_the_website %} + +To unlock the repositories on a {% data variables.product.prodname_dotcom_the_website %} organization, you'll send a `DELETE` request to [the migration unlock endpoint](/free-pro-team@latest/rest/migrations#unlock-an-organization-repository). You'll need: + * Your access token for authentication + * The unique `id` of the migration + * The name of the repository to unlock -若要解锁 {% data variables.product.prodname_dotcom_the_website %} 组织上的存储库,你需要向[迁移解锁终结点](/free-pro-team@latest/rest/migrations#unlock-an-organization-repository)发送 `DELETE` 请求。 需要: - * 身份验证的访问令牌 - * 迁移的唯一 `id` - * 要解锁的仓库的名称 ```shell -curl -H "Authorization: Bearer GITHUB_ACCESS_TOKEN" -X DELETE \ +curl -H "Authorization: Bearer GITHUB_ACCESS_TOKEN" -X DELETE \ -H "Accept: application/vnd.github.wyandotte-preview+json" \ - https://api.github.com/orgs/orgname/migrations/id/repos/repo_name/lock + https://api.github.com/orgs/ORG-NAME/migrations/ID/repos/REPO_NAME/lock ``` -### 从 {% data variables.product.prodname_dotcom_the_website %} 上的组织中删除仓库 +### Deleting repositories from an organization on {% data variables.product.prodname_dotcom_the_website %} -解锁 {% data variables.product.prodname_dotcom_the_website %} 组织的存储库后,应该删除之前使用[存储库删除终结点](/rest/repos/#delete-a-repository)迁移的每个存储库。 您需要身份验证的访问令牌: +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/repos/#delete-a-repository). You'll need your access token for authentication: ```shell -curl -H "Authorization: Bearer GITHUB_ACCESS_TOKEN" -X DELETE \ - https://api.github.com/repos/orgname/repo_name +curl -H "Authorization: Bearer GITHUB_ACCESS_TOKEN" -X DELETE \ + https://api.github.com/repos/ORG-NAME/REPO_NAME ``` -### 从 {% data variables.product.prodname_ghe_server %} 实例解锁仓库 +### Unlocking repositories from a {% data variables.product.prodname_ghe_server %} instance -{% data reusables.enterprise_installation.ssh-into-instance %} {% data reusables.enterprise_migrations.unlocking-on-instances %} +{% data reusables.enterprise_installation.ssh-into-instance %} +{% data reusables.enterprise_migrations.unlocking-on-instances %} diff --git a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md index d2a60017e0..c0787f5ae1 100644 --- a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- -title: 关于使用 SAML 单点登录进行身份验证 -intro: '可以通过身份提供商 (IdP) {% ifversion ghae %}以 SAML 单一登录 (SSO) {% endif %}验证来访问{% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %}使用 SAML 单一登录 (SSO) 的组织{% endif %}。' +title: About authentication with SAML single sign-on +intro: 'You can access {% ifversion ghae %}{% data variables.location.product_location %}{% elsif ghec %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% ifversion ghae %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).' redirect_from: - /articles/about-authentication-with-saml-single-sign-on - /github/authenticating-to-github/about-authentication-with-saml-single-sign-on @@ -11,65 +11,60 @@ versions: topics: - SSO shortTitle: SAML single sign-on -ms.openlocfilehash: 7fb15bab585093a618f9c082d340c2fe66d67df7 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147527908' --- -## 关于使用 SAML SSO 进行身份验证 +## About authentication with SAML SSO {% ifversion ghae %} -SAML SSO 允许企业所有者从 SAML IdP 集中控制和安全访问 {% data variables.product.product_name %}。 在浏览器中访问 {% data variables.product.product_location %} 时,{% data variables.product.product_name %} 会将用户重定向到您的 IdP 进行身份验证。 在使用 IdP 上的帐户成功进行身份验证后,IdP 会将您重定向回 {% data variables.product.product_location %}。 {% data variables.product.product_name %} 将验证 IdP 的响应,然后授予访问权限。 +SAML SSO allows an enterprise owner to centrally control and secure access to {% data variables.product.product_name %} from a SAML IdP. When you visit {% data variables.location.product_location %} in a browser, {% data variables.product.product_name %} will redirect you to your IdP to authenticate. After you successfully authenticate with an account on the IdP, the IdP redirects you back to {% data variables.location.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access. {% data reusables.saml.you-must-periodically-authenticate %} -如果您无法访问 {% data variables.product.product_name %},请与本地企业所有者或 {% data variables.product.product_name %} 的管理员联系。 你可以在 {% data variables.product.product_name %} 上的任何页面底部单击“支持”找到企业的联系信息。 {% data variables.product.company_short %} 和 {% data variables.contact.github_support %} 无法访问您的 IdP,并且无法解决身份验证问题。 +If you can't access {% data variables.product.product_name %}, contact your local enterprise owner or administrator for {% data variables.product.product_name %}. You may be able to locate contact information for your enterprise by clicking **Support** at the bottom of any page on {% data variables.product.product_name %}. {% data variables.product.company_short %} and {% data variables.contact.github_support %} do not have access to your IdP, and cannot troubleshoot authentication problems. {% endif %} {% ifversion fpt or ghec %} -{% data reusables.saml.dotcom-saml-explanation %} 组织所有者可以邀请你在 {% data variables.product.prodname_dotcom %} 上的个人帐户加入其使用 SAML SSO 的组织,这样你可以对该组织做出贡献,并且保留你在 {% data variables.product.prodname_dotcom %} 上的现有身份和贡献。 +{% data reusables.saml.dotcom-saml-explanation %} Organization owners can invite your personal account on {% data variables.product.prodname_dotcom %} to join their organization that uses SAML SSO, which allows you to contribute to the organization and retain your existing identity and contributions on {% data variables.product.prodname_dotcom %}. -如果你是 {% data variables.product.prodname_emu_enterprise %} 的成员,则将转而使用为你预配且由你的企业控制的新帐户。 {% data reusables.enterprise-accounts.emu-more-info-account %} +If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you will instead use a new account that is provisioned for you and controlled by your enterprise. {% data reusables.enterprise-accounts.emu-more-info-account %} -在访问使用 SAML SSO 的组织中的专用资源时,{% data variables.product.prodname_dotcom %} 会将你重定向到组织的 SAML IdP 进行身份验证。 在 IdP 上成功验证您的帐户后,IdP 会将您重定向回到 {% data variables.product.prodname_dotcom %},您可以在那里访问组织的资源。 +When you access private resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to {% data variables.product.prodname_dotcom %}, where you can access the organization's resources. {% data reusables.saml.outside-collaborators-exemption %} -如果您最近在浏览器中使用组织的 SAML IdP 进行过身份验证,则在访问使用 SAML SSO 的 {% data variables.product.prodname_dotcom %} 组织时会自动获得授权。 如果您最近没有在浏览器中使用组织的 SAML IdP 进行身份验证,则必须在 SAML IdP 进行身份验证后才可访问组织。 +If you have recently authenticated with your organization's SAML IdP in your browser, you are automatically authorized when you access a {% data variables.product.prodname_dotcom %} organization that uses SAML SSO. If you haven't recently authenticated with your organization's SAML IdP in your browser, you must authenticate at the SAML IdP before you can access the organization. {% data reusables.saml.you-must-periodically-authenticate %} -## 关联的 SAML 标识 +## Linked SAML identities -使用 IdP 帐户进行身份验证并返回到 {% data variables.product.prodname_dotcom %} 时,{% data variables.product.prodname_dotcom %} 会在组织或企业中记录你的 {% data variables.product.prodname_dotcom %} 个人帐户与你登录到的 SAML 标识之间的关联。 这个关联的标识用于验证你在该组织中的成员身份,并且根据你的组织或企业设置,还用于确定你所属的具体组织和团队。 每个 {% data variables.product.prodname_dotcom %} 帐户只能关联到每个组织的一个 SAML 标识。 同样地,每个 SAML 标识只能关联到一个组织中的一个 {% data variables.product.prodname_dotcom %} 帐户。 +When you authenticate with your IdP account and return to {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_dotcom %} will record a link in the organization or enterprise between your {% data variables.product.prodname_dotcom %} personal account and the SAML identity you signed into. This linked identity is used to validate your membership in that organization, and depending on your organization or enterprise setup, is also used to determine which organizations and teams you're a member of as well. Each {% data variables.product.prodname_dotcom %} account can be linked to exactly one SAML identity per organization. Likewise, each SAML identity can be linked to exactly one {% data variables.product.prodname_dotcom %} account in an organization. -如果使用已关联到其他 {% data variables.product.prodname_dotcom %} 帐户的 SAML 标识登录,会收到一条错误消息,指示无法使用该 SAML 标识进行登录。 如果尝试使用新的 {% data variables.product.prodname_dotcom %} 帐户在组织内部工作,就可能会出现这种情况。 如果不想将该 SAML 标识与该 {% data variables.product.prodname_dotcom %} 帐户一起使用,则需要注销该 SAML 标识,然后重复 SAML 登录。 如果确实要将该 SAML 标识与 {% data variables.product.prodname_dotcom %} 帐户一起使用,需要要求管理员取消该 SAML 标识与旧帐户的关联,以便你可将其关联到新帐户。 根据组织或企业的设置,管理员可能需要在 SAML 提供商中重新分配你的标识。 有关详细信息,请参阅“[查看和管理成员对组织的 SAML 访问权限](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)”。 +If you sign in with a SAML identity that is already linked to another {% data variables.product.prodname_dotcom %} account, you will receive an error message indicating that you cannot sign in with that SAML identity. This situation can occur if you are attempting to use a new {% data variables.product.prodname_dotcom %} account to work inside of your organization. If you didn't intend to use that SAML identity with that {% data variables.product.prodname_dotcom %} account, then you'll need to sign out of that SAML identity and then repeat the SAML login. If you do want to use that SAML identity with your {% data variables.product.prodname_dotcom %} account, you'll need to ask your admin to unlink your SAML identity from your old account, so that you can link it to your new account. Depending on the setup of your organization or enterprise, your admin may also need to reassign your identity within your SAML provider. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)." -如果用于登录的 SAML 标识与当前关联到 {% data variables.product.prodname_dotcom %} 帐户的 SAML 标识不匹配,会收到一条警告,要求你重新关联帐户。 SAML 标识用于管理访问权限和团队成员身份,因此继续使用新的 SAML 标识可能会导致你无法再访问 {% data variables.product.prodname_dotcom %} 中的团队和组织。 只有当你知道将来应该使用这个新的 SAML 标识进行身份验证时,才继续操作。 +If the SAML identity you sign in with does not match the SAML identity that is currently linked to your {% data variables.product.prodname_dotcom %} account, you'll receive a warning that you are about to relink your account. Because your SAML identity is used to govern access and team membership, continuing with the new SAML identity can cause you to lose access to teams and organizations inside of {% data variables.product.prodname_dotcom %}. Only continue if you know that you're supposed to use that new SAML identity for authentication in the future. -## 使用 SAML SSO 授权 PAT 和 SSH 密钥 +## Authorizing {% data variables.product.pat_generic %}s and SSH keys with SAML SSO -要在命令行上使用 API 或 Git 访问使用 SAML SSO 的组织中受保护的内容,需要使用授权的 HTTPS 个人访问令牌或授权的 SSH 密钥。 +To use the API or Git on the command line to access protected content in an organization that uses SAML SSO, you will need to use an authorized {% data variables.product.pat_generic %} over HTTPS or an authorized SSH key. -如果没有个人访问令牌或 SSH 密钥,可以创建用于命令行的个人访问令牌或生成新的 SSH 密钥。 有关详细信息,请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”或“[生成新的 SSH 密钥并将其添加到 ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)”。 +If you don't have a {% data variables.product.pat_generic %} or an SSH key, you can create a {% data variables.product.pat_generic %} for the command line or generate a new SSH key. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)" or "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." -要对使用或实施 SAML SSO 的组织使用新的或现有的个人访问令牌或 SSH 密钥,需要授权该令牌或授权 SSH 密钥用于 SAML SSO 组织。 有关详细信息,请参阅“[授权用于 SAML 单一登录的个人访问令牌](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)”或“[授权用于 SAML 单一登录的 SSH 密钥](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)”。 +To use a new or existing {% data variables.product.pat_generic %} or SSH key with an organization that uses or enforces SAML SSO, you will need to authorize the token or authorize the SSH key for use with a SAML SSO organization. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." -## 关于 {% data variables.product.prodname_oauth_apps %}、{% data variables.product.prodname_github_apps %} 和 SAML SSO +## About {% data variables.product.prodname_oauth_apps %}, {% data variables.product.prodname_github_apps %}, and SAML SSO -每次授权 {% data variables.product.prodname_oauth_app %} 或 {% data variables.product.prodname_github_app %} 访问使用或实施 SAML SSO 的组织时,你都必须有一个活动的 SAML 会话。 可以通过在浏览器中导航到 `https://github.com/orgs/ORGANIZATION-NAME/sso` 来创建活动的 SAML 会话。 +You must have an active SAML session each time you authorize an {% data variables.product.prodname_oauth_app %} or {% data variables.product.prodname_github_app %} to access an organization that uses or enforces SAML SSO. You can create an active SAML session by navigating to `https://github.com/orgs/ORGANIZATION-NAME/sso` in your browser. -企业或组织所有者为组织启用或强制实施 SAML SSO 后,以及首次通过 SAML 进行身份验证后,必须对之前授权访问组织的任何 {% data variables.product.prodname_oauth_apps %} 或 {% data variables.product.prodname_github_apps %} 进行重新授权。 +After an enterprise or organization owner enables or enforces SAML SSO for an organization, and after you authenticate via SAML for the first time, you must reauthorize any {% data variables.product.prodname_oauth_apps %} or {% data variables.product.prodname_github_apps %} that you previously authorized to access the organization. -若要查看已授权的 {% data variables.product.prodname_oauth_apps %},请访问 [{% data variables.product.prodname_oauth_apps %} 页面](https://github.com/settings/applications)。 若要查看已授权的 {% data variables.product.prodname_github_apps %},请访问 [{% data variables.product.prodname_github_apps %} 页面](https://github.com/settings/apps/authorizations)。 +To see the {% data variables.product.prodname_oauth_apps %} you've authorized, visit your [{% data variables.product.prodname_oauth_apps %} page](https://github.com/settings/applications). To see the {% data variables.product.prodname_github_apps %} you've authorized, visit your [{% data variables.product.prodname_github_apps %} page](https://github.com/settings/apps/authorizations). {% endif %} -## 延伸阅读 +## Further reading -{% ifversion ghec %}- “[关于 SAML 单一登录的标识和访问管理](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)”{% endif %} {% ifversion ghae %}- “[关于企业标识和访问管理](/admin/authentication/about-identity-and-access-management-for-your-enterprise)”{% endif %} +{% ifversion ghec %}- "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} +{% ifversion ghae %}- "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} diff --git a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md index 5dc56f5acf..cc1537e412 100644 --- a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md +++ b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- title: Authorizing a personal access token for use with SAML single sign-on -intro: 'To use a personal access token with an organization that uses SAML single sign-on (SSO), you must first authorize the token.' +intro: 'To use a {% data variables.product.pat_v1 %} with an organization that uses SAML single sign-on (SSO), you must first authorize the token.' redirect_from: - /articles/authorizing-a-personal-access-token-for-use-with-a-saml-single-sign-on-organization - /articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on @@ -10,9 +10,9 @@ versions: ghec: '*' topics: - SSO -shortTitle: PAT with SAML +shortTitle: '{% data variables.product.pat_generic_caps %} with SAML' --- -You can authorize an existing personal access token, or [create a new personal access token](/github/authenticating-to-github/creating-a-personal-access-token) and then authorize it. +You must authorize your {% data variables.product.pat_v1 %} after creation before the token can access an organization that uses SAML single sign-on (SSO). For more information about creating a new {% data variables.product.pat_v1 %}, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."{% ifversion pat-v2 %} {% data variables.product.pat_v2_caps %}s are authorized during token creation, before access to the organization is granted.{% endif %} {% data reusables.saml.must-authorize-linked-identity %} @@ -23,11 +23,11 @@ You can authorize an existing personal access token, or [create a new personal a {% data reusables.user-settings.personal_access_tokens %} 3. Next to the token you'd like to authorize, click **Configure SSO**. {% data reusables.saml.authenticate-with-saml-at-least-once %} - ![Screenshot of the dropdown menu to configure SSO for a personal access token](/assets/images/help/settings/sso-allowlist-button.png) + ![Screenshot of the dropdown menu to configure SSO for a {% data variables.product.pat_v1 %}](/assets/images/help/settings/sso-allowlist-button.png) 4. To the right of the organization you'd like to authorize the token for, click **Authorize**. ![Token authorize button](/assets/images/help/settings/token-authorize-button.png) ## Further reading -- "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)" +- "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)" - "[About authentication with SAML single sign-on](/articles/about-authentication-with-saml-single-sign-on)" diff --git a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md index 53b7c7225e..547784b6ad 100644 --- a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md +++ b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/about-ssh.md @@ -1,6 +1,6 @@ --- title: About SSH -intro: 'Using the SSH protocol, you can connect and authenticate to remote servers and services. With SSH keys, you can connect to {% data variables.product.product_name %} without supplying your username and personal access token at each visit.{% ifversion ssh-commit-verification %} You can also use an SSH key to sign commits.{% endif %}' +intro: 'Using the SSH protocol, you can connect and authenticate to remote servers and services. With SSH keys, you can connect to {% data variables.product.product_name %} without supplying your username and {% data variables.product.pat_generic %} at each visit.{% ifversion ssh-commit-verification %} You can also use an SSH key to sign commits.{% endif %}' redirect_from: - /articles/about-ssh - /github/authenticating-to-github/about-ssh diff --git a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md index eabcedfe38..1e7cde5e8d 100644 --- a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md +++ b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md @@ -1,6 +1,6 @@ --- title: Adding a new SSH key to your GitHub account -intro: 'To configure your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} to use your new (or existing) SSH key, you''ll also need to add the key to your account.' +intro: 'To configure your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} to use your new (or existing) SSH key, you''ll also need to add the key to your account.' redirect_from: - /articles/adding-a-new-ssh-key-to-your-github-account - /github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account @@ -21,18 +21,18 @@ shortTitle: Add a new SSH key {% ifversion ssh-commit-verification %}You can also use SSH to sign commits and tags. For more information about commit signing, see "[About commit signature verification](/articles/about-commit-signature-verification)."{% endif %} -After you generate an SSH key pair, you must add the public key to {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable SSH access for your account. +After you generate an SSH key pair, you must add the public key to {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable SSH access for your account. ## Prerequisites -Before adding a new SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, complete the following steps. +Before adding a new SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, complete the following steps. 1. Check for existing SSH keys. For more information, see "[Checking for existing SSH keys](/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys)." 1. Generate a new SSH key and add it to your machine's SSH agent. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." ## Adding a new SSH key to your account -After adding a new SSH authentication key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, you can reconfigure any local repositories to use SSH. For more information, see "[Switching remote URLs from HTTPS to SSH](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-https-to-ssh)." +After adding a new SSH authentication key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, you can reconfigure any local repositories to use SSH. For more information, see "[Switching remote URLs from HTTPS to SSH](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-https-to-ssh)." {% data reusables.ssh.key-type-support %} diff --git a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md index 0441cda5ad..e840701467 100644 --- a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md +++ b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md @@ -1,6 +1,6 @@ --- -title: 检查现有 SSH 密钥 -intro: 在生成 SSH 密钥之前,您可以检查是否有任何现有的 SSH 密钥。 +title: Checking for existing SSH keys +intro: 'Before you generate an SSH key, you can check to see if you have any existing SSH keys.' redirect_from: - /articles/checking-for-existing-ssh-keys - /github/authenticating-to-github/checking-for-existing-ssh-keys @@ -13,46 +13,41 @@ versions: topics: - SSH shortTitle: Check for existing SSH key -ms.openlocfilehash: 4487e44b1cbba7038364e92f3194d5c3c06c505b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147409105' --- -## 关于 SSH 密钥 -可以使用 SSH 在 {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} 上的存储库中执行 Git 操作。 有关详细信息,请参阅“[关于 SSH](/authentication/connecting-to-github-with-ssh/about-ssh)”。 +## About SSH keys -如果有现有的 SSH 密钥,则可以使用该密钥通过 SSH 对 Git 操作进行身份验证。 +You can use SSH to perform Git operations in repositories on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)." -## 检查现有 SSH 密钥 +If you have an existing SSH key, you can use the key to authenticate Git operations over SSH. -在生成新的 SSH 密钥之前,应该检查本地计算机是否存在现有密钥。 +## Checking for existing SSH keys + +Before you generate a new SSH key, you should check your local machine for existing keys. {% data reusables.ssh.key-type-support %} {% data reusables.command_line.open_the_multi_os_terminal %} -2. 输入 `ls -al ~/.ssh` 以查看是否存在现有的 SSH 密钥。 +2. Enter `ls -al ~/.ssh` to see if existing SSH keys are present. ```shell $ ls -al ~/.ssh # Lists the files in your .ssh directory, if they exist ``` -3. 检查目录列表以查看是否已经有 SSH 公钥。 默认情况下,{% ifversion ghae %}{% data variables.product.product_name %} 的一个支持的公钥的文件名是 id_rsa.pub。{% else %}{% data variables.product.product_name %} 的一个支持的公钥的文件名是以下之一。 - - id_rsa.pub - - id_ecdsa.pub - - id_ed25519.pub{% endif %} +3. Check the directory listing to see if you already have a public SSH key. By default, the {% ifversion ghae %}filename of a supported public key for {% data variables.product.product_name %} is *id_rsa.pub*.{% else %}filenames of supported public keys for {% data variables.product.product_name %} are one of the following. + - *id_rsa.pub* + - *id_ecdsa.pub* + - *id_ed25519.pub*{% endif %} {% tip %} - 提示:如果收到错误,指示 ~/.ssh 不存在,则表明默认位置中没有现有的 SSH 密钥对。 您可以在下一步中创建新的 SSH 密钥对。 + **Tip**: If you receive an error that *~/.ssh* doesn't exist, you do not have an existing SSH key pair in the default location. You can create a new SSH key pair in the next step. {% endtip %} -4. 生成新的 SSH 密钥或上传现有密钥。 - - 如果您没有受支持的公钥和私钥对,或者不希望使用任何可用的密钥对,请生成新的 SSH 密钥。 - - 如果你看到列出了要用于连接到 {% data variables.product.product_name %} 的现有公钥和私钥对(例如,id_rsa.pub 和 id_rsa),则可以将密钥添加到 ssh-代理 。 +4. Either generate a new SSH key or upload an existing key. + - If you don't have a supported public and private key pair, or don't wish to use any that are available, generate a new SSH key. + - If you see an existing public and private key pair listed (for example, *id_rsa.pub* and *id_rsa*) that you would like to use to connect to {% data variables.product.product_name %}, you can add the key to the ssh-agent. - 有关生成新的 SSH 密钥或向 ssh-代理添加现有密钥的详细信息,请参阅“[生成新的 SSH 密钥并将其添加到 ssh-代理](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)。” + For more information about generation of a new SSH key or addition of an existing key to the ssh-agent, see "[Generating a new SSH key and adding it to the ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." diff --git a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md index 870e5fd520..e6c655b322 100644 --- a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md +++ b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md @@ -29,11 +29,11 @@ If you want to use a hardware security key to authenticate to {% data variables. ## Generating a new SSH key -You can generate a new SSH key on your local machine. After you generate the key, you can add the key to your account on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable authentication for Git operations over SSH. +You can generate a new SSH key on your local machine. After you generate the key, you can add the key to your account on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable authentication for Git operations over SSH. {% ifversion ghes %} -If you are a site administrator for {% data variables.product.product_location %}, you can use the same key to grant yourself administrative SSH access to the instance. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." +If you are a site administrator for {% data variables.location.product_location %}, you can use the same key to grant yourself administrative SSH access to the instance. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." {% endif %} diff --git a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md index a920a76acf..a97d7da6c6 100644 --- a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md +++ b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md @@ -1,6 +1,6 @@ --- -title: 测试 SSH 连接 -intro: '设置 SSH 密钥并将其添加到您在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的帐户后,您可以测试连接。' +title: Testing your SSH connection +intro: 'After you''ve set up your SSH key and added it to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, you can test your connection.' redirect_from: - /articles/testing-your-ssh-connection - /github/authenticating-to-github/testing-your-ssh-connection @@ -13,28 +13,22 @@ versions: topics: - SSH shortTitle: Test your SSH connection -ms.openlocfilehash: 7724c5939b319748f270db2f190a6df825b0bb4f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146338971' --- -测试 SSH 连接之前,您应已完成以下各项: -- [检查现有 SSH 密钥](/articles/checking-for-existing-ssh-keys) -- [生成新 SSH 密钥](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) -- [为 GitHub 帐户添加新的 SSH 密钥](/articles/adding-a-new-ssh-key-to-your-github-account) +Before testing your SSH connection, you should have: +- [Checked for existing SSH keys](/articles/checking-for-existing-ssh-keys) +- [Generated a new SSH key](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) +- [Added a new SSH key to your GitHub account](/articles/adding-a-new-ssh-key-to-your-github-account) -测试连接时,您将需要使用密码(即您之前创建的 SSH 密钥密码)验证此操作。 有关使用 SSH 密钥密码的详细信息,请参阅“[使用 SSH 密钥密码](/articles/working-with-ssh-key-passphrases)”。 +When you test your connection, you'll need to authenticate this action using your password, which is the SSH key passphrase you created earlier. For more information on working with SSH key passphrases, see ["Working with SSH key passphrases"](/articles/working-with-ssh-key-passphrases). {% data reusables.command_line.open_the_multi_os_terminal %} -2. 输入以下内容: +2. Enter the following: ```shell $ ssh -T git@{% data variables.command_line.codeblock %} # Attempts to ssh to {% data variables.product.product_name %} ``` - 您可能会看到类似如下的警告: + You may see a warning like this: ```shell > The authenticity of host '{% data variables.command_line.codeblock %} (IP ADDRESS)' can't be established. @@ -42,15 +36,15 @@ ms.locfileid: '146338971' > Are you sure you want to continue connecting (yes/no)? ``` -3. 验证所看到消息中的指纹是否与 {% ifversion fpt or ghec %}[{% data variables.product.prodname_dotcom %} 的公钥指纹](/github/authenticating-to-github/githubs-ssh-key-fingerprints){% else %}企业的公钥指纹{% endif %}匹配。 如果是,则键入 `yes`: +3. Verify that the fingerprint in the message you see matches {% ifversion fpt or ghec %}[{% data variables.product.prodname_dotcom %}'s public key fingerprint](/github/authenticating-to-github/githubs-ssh-key-fingerprints){% else %} your enterprise's public key fingerprint{% endif %}. If it does, then type `yes`: ```shell - > Hi username! You've successfully authenticated, but GitHub does not + > Hi USERNAME! You've successfully authenticated, but GitHub does not > provide shell access. ``` {% linux %} - 你可能会看到此错误消息: + You may see this error message: ```shell ... Agent admitted failure to sign using the key. @@ -58,14 +52,14 @@ ms.locfileid: '146338971' Permission denied (publickey). ``` - 这是某些 Linux 发行版的已知问题。 有关详细信息,请参阅“[错误:代理承认没有签名](/articles/error-agent-admitted-failure-to-sign)”。 + This is a known problem with certain Linux distributions. For more information, see ["Error: Agent admitted failure to sign"](/articles/error-agent-admitted-failure-to-sign). {% endlinux %} {% note %} - 注意:远程命令应退出,并显示代码 1。 + **Note:** The remote command should exit with code 1. {% endnote %} -4. 验证生成的消息包含您的用户名。 如果收到“权限被拒绝”消息,请参阅“[错误:权限被拒绝(公钥)](/articles/error-permission-denied-publickey)”。 +4. Verify that the resulting message contains your username. If you receive a "permission denied" message, see ["Error: Permission denied (publickey)"](/articles/error-permission-denied-publickey). diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md index df96216a6e..0eefcc7612 100644 --- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md +++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md @@ -1,6 +1,6 @@ --- -title: 关于向 GitHub 验证 -intro: '您可以根据身份验证位置使用不同的凭据,向 {% data variables.product.product_name %} 验证来安全地访问帐户的资源。' +title: About authentication to GitHub +intro: 'You can securely access your account''s resources by authenticating to {% data variables.product.product_name %}, using different credentials depending on where you authenticate.' versions: fpt: '*' ghes: '*' @@ -13,107 +13,101 @@ redirect_from: - /github/authenticating-to-github/about-authentication-to-github - /github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github shortTitle: Authentication to GitHub -ms.openlocfilehash: d40d3e18c75c2e5d8f16ebbb4fd9b6fdf03e2a73 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147718091' --- -## 关于 {% data variables.product.prodname_dotcom %} 向验证身份 +## About authentication to {% data variables.product.prodname_dotcom %} -为确保帐户安全,必须先进行身份验证,然后才能访问 {% data variables.product.product_name %} 上的{% ifversion not ghae %}某些{% endif %}资源。 向 {% data variables.product.product_name %} 验证时,您提供或确认您唯一的凭据,以证明您就是声明者。 +To keep your account secure, you must authenticate before you can access{% ifversion not ghae %} certain{% endif %} resources on {% data variables.product.product_name %}. When you authenticate to {% data variables.product.product_name %}, you supply or confirm credentials that are unique to you to prove that you are exactly who you declare to be. -您可以通过多种方式访问 {% data variables.product.product_name %} 中的资源:浏览器中、通过 {% data variables.product.prodname_desktop %} 或其他桌面应用程序、使用 API 或通过命令行。 每种访问 {% data variables.product.product_name %} 的方式都支持不同的身份验证模式。 +You can access your resources in {% data variables.product.product_name %} in a variety of ways: in the browser, via {% data variables.product.prodname_desktop %} or another desktop application, with the API, or via the command line. Each way of accessing {% data variables.product.product_name %} supports different modes of authentication. {%- ifversion not fpt %} -- 标识提供者 (IdP){% endif %}{% ifversion not ghae %} -- 用于双因素身份验证的用户名和密码{% endif %} -- 个人访问令牌 -- SSH 密钥 +- Your identity provider (IdP){% endif %}{% ifversion not ghae %} +- Username and password with two-factor authentication{% endif %} +- {% data variables.product.pat_generic_caps %} +- SSH key -## 在浏览器中进行身份验证 +## Authenticating in your browser {% ifversion ghae %} -你可以使用 IdP 在浏览器中向 {% data variables.product.product_name %} 验证。 有关详细信息,请参阅“[关于通过 SAML 单一登录进行身份验证](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)”。 +You can authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)." {% else %} {% ifversion fpt or ghec %} -如果您是 {% data variables.product.prodname_emu_enterprise %} 的成员,您将使用 IdP 在浏览器中向 {% data variables.product.product_name %} 验证。 有关详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[作为托管用户进行身份验证](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}”。{% else %}."{% endif %} +If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you will authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[Authenticating as a managed user](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} -如果你不是 {% data variables.product.prodname_emu_enterprise %} 的成员,你将使用 {% data variables.product.prodname_dotcom_the_website %} 用户名和密码进行身份验证。 还可以使用双因素身份验证和 SAML 单一登录,组织和企业所有者可能需要这一点。 +If you're not a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you will authenticate using your {% data variables.product.prodname_dotcom_the_website %} username and password. You may also use two-factor authentication and SAML single sign-on, which can be required by organization and enterprise owners. {% else %} -你可以在浏览器中以多种方式向 {% data variables.product.product_name %} 验证。 +You can authenticate to {% data variables.product.product_name %} in your browser in a number of ways. {% endif %} -- **仅用户名和密码** - - 在 {% data variables.product.product_name %} 上创建帐户时,你将创建一个密码。 我们建议您使用密码管理器生成随机且唯一的密码。 有关详细信息,请参阅“[创建强密码](/github/authenticating-to-github/creating-a-strong-password)”。{% ifversion fpt or ghec %} - - 如果未启用 2FA,{% data variables.product.product_name %} 将在首次从无法识别的设备(例如新浏览器配置文件、已删除 Cookie 的浏览器或新计算机)登录时请求其他验证。 +- **Username and password only** + - You'll create a password when you create your account on {% data variables.product.product_name %}. We recommend that you use a password manager to generate a random and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/creating-a-strong-password)."{% ifversion fpt or ghec %} + - If you have not enabled 2FA, {% data variables.product.product_name %} will ask for additional verification when you first sign in from an unrecognized device, such as a new browser profile, a browser where the cookies have been deleted, or a new computer. - 提供用户名和密码后,系统将要求你提供一个验证码,我们会通过电子邮件发送给你。 如果已安装 {% data variables.product.prodname_mobile %} 应用程序,则将改为收到通知。 有关详细信息,请参阅“[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)”。{% endif %} -- **双因素身份验证 (2FA)** (推荐) - - 如果你启用 2FA,则在成功输入用户名和密码后,我们还将提示你提供基于时间的一次性密码 (TOTP) 应用程序在移动设备{% ifversion fpt or ghec %}上生成的代码或以短信 (SMS){% endif %} 形式发送的代码。 有关详细信息,请参阅“[使用双因素身份验证访问 {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)”。 - - 除了使用 TOTP 应用程序{% ifversion fpt or ghec %}或短信{% endif %}进行身份验证外,你还可以选择使用 WebAuthn 添加采用{% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %}或{% endif %}安全密钥的备用身份验证方法。 有关详细信息,请参阅 {% ifversion fpt or ghec %}“[使用 {% data variables.product.prodname_mobile %} 配置双因素身份验证](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)”和 {% endif %}“[使用安全密钥配置双因素身份验证](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)”。{% ifversion ghes %} -- **外部身份验证** - - 站点管理员可以将 {% data variables.product.product_location %} 配置为使用外部身份验证,而不是用户名和密码。 有关详细信息,请参阅“[外部身份验证方法](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)”。{% endif %}{% ifversion fpt or ghec %} -- **SAML 单一登录** - - 在可以访问使用 SAML 单一登录的组织或企业帐户拥有的资源之前,可能还需要通过 IdP 进行身份验证。 有关详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[关于使用 SAML 单一登录进行身份验证](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}”。{% else %}."{% endif %}{% endif %} + After providing your username and password, you will be asked to provide a verification code that we will send to you via email. If you have the {% data variables.product.prodname_mobile %} application installed, you'll receive a notification there instead. For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)."{% endif %} +- **Two-factor authentication (2FA)** (recommended) + - If you enable 2FA, after you successfully enter your username and password, we'll also prompt you to provide a code that's generated by a time-based one time password (TOTP) application on your mobile device{% ifversion fpt or ghec %} or sent as a text message (SMS){% endif %}. For more information, see "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)." + - In addition to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}, you can optionally add an alternative method of authentication with {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} or{% endif %} a security key using WebAuthn. For more information, see {% ifversion fpt or ghec %}"[Configuring two-factor authentication with {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" and {% endif %}"[Configuring two-factor authentication using a security key](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."{% ifversion ghes %} +- **External authentication** + - Your site administrator may configure {% data variables.location.product_location %} to use external authentication instead of a username and password. For more information, see "[External authentication methods](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)."{% endif %}{% ifversion fpt or ghec %} +- **SAML single sign-on** + - Before you can access resources owned by an organization or enterprise account that uses SAML single sign-on, you may need to also authenticate through an IdP. For more information, see "[About authentication with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} {% endif %} -## 向 {% data variables.product.prodname_desktop %} 验证身份 -您可以使用浏览器向 {% data variables.product.prodname_desktop %} 验证身份。 有关详细信息,请参阅“[向 {% data variables.product.prodname_dotcom %} 进行身份验证](/desktop/getting-started-with-github-desktop/authenticating-to-github)”。 +## Authenticating with {% data variables.product.prodname_desktop %} +You can authenticate with {% data variables.product.prodname_desktop %} using your browser. For more information, see "[Authenticating to {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)." -## 使用 API 验证身份 +## Authenticating with the API -您可以通过不同方式使用 API 进行身份验证。 +You can authenticate with the API in different ways. -- **个人访问令牌** - - 在有限的情况(如测试)下可以使用个人访问令牌访问 API。 使用个人访问令牌可让您随时撤销访问。 有关详细信息,请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 -- **Web 应用程序流程** - - 对于生产中的 OAuth 应用程序,应使用 Web 应用程序流程进行身份验证。 有关详细信息,请参阅“[授权 OAuth 应用](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)”。 -- **GitHub 应用** - - 对于生产中的 GitHub 应用程序,您应代表应用安装进行身份验证。 有关详细信息,请参阅“[使用 {% data variables.product.prodname_github_apps %} 进行身份验证](/apps/building-github-apps/authenticating-with-github-apps/)”。 +- **{% data variables.product.pat_generic_caps %}s** + - In limited situations, such as testing, you can use a {% data variables.product.pat_generic %} to access the API. Using a {% data variables.product.pat_generic %} enables you to revoke access at any time. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." +- **Web application flow** + - For OAuth Apps in production, you should authenticate using the web application flow. For more information, see "[Authorizing OAuth Apps](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)." +- **GitHub Apps** + - For GitHub Apps in production, you should authenticate on behalf of the app installation. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/authenticating-with-github-apps/)." -## 使用命令行进行身份验证 +## Authenticating with the command line -您可以通过两种方式从命令行访问 {% data variables.product.product_name %} 上的仓库:HTTPS 和 SSH ,两者采用不同的身份验证。 验证方法取决于克隆仓库时您是选择 HTTPS 还是 SSH 远程 URL。 有关访问方式的详细信息,请参阅“[关于远程存储库](/github/getting-started-with-github/about-remote-repositories)”。 +You can access repositories on {% data variables.product.product_name %} from the command line in two ways, HTTPS and SSH, and both have a different way of authenticating. The method of authenticating is determined based on whether you choose an HTTPS or SSH remote URL when you clone the repository. For more information about which way to access, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)." ### HTTPS -即使您在防火墙或代理后面,也可以通过 HTTPS 处理 {% data variables.product.product_name %} 上的所有仓库。 +You can work with all repositories on {% data variables.product.product_name %} over HTTPS, even if you are behind a firewall or proxy. -如果您使用 {% data variables.product.prodname_cli %} 进行身份验证,您可以使用个人访问令牌或通过 Web 浏览器进行身份验证。 有关使用 {% data variables.product.prodname_cli %} 进行身份验证的详细信息,请参阅 [`gh auth login`](https://cli.github.com/manual/gh_auth_login)。 +If you authenticate with {% data variables.product.prodname_cli %}, you can either authenticate with a {% data variables.product.pat_generic %} or via the web browser. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). -如果您不使用 {% data variables.product.prodname_cli %} 进行身份验证,则必须使用个人访问令牌进行身份验证。 {% data reusables.user-settings.password-authentication-deprecation %}除非你使用[凭据小助手](/github/getting-started-with-github/caching-your-github-credentials-in-git)缓存了凭据,否则每次使用 Git 向 {% data variables.product.product_name %} 验证时,系统都会提示你输入凭据以向 {% data variables.product.product_name %} 验证。 +If you authenticate without {% data variables.product.prodname_cli %}, you must authenticate with a {% data variables.product.pat_generic %}. {% data reusables.user-settings.password-authentication-deprecation %} Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your credentials to authenticate with {% data variables.product.product_name %}, unless you cache them with a [credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git). ### SSH -您可以通过 SSH 处理 {% data variables.product.product_name %} 上的所有仓库,尽管防火墙和代理可能拒绝允许 SSH 连接。 +You can work with all repositories on {% data variables.product.product_name %} over SSH, although firewalls and proxies might refuse to allow SSH connections. -如果您使用 {% data variables.product.prodname_cli %} 进行身份验证,CLI 会在您的机器上找到 SSH 公共密钥,并提示您选择一个用于上传。 如果 {% data variables.product.prodname_cli %} 找不到用于上传的 SSH 公钥,则可以生成新的 SSH 公钥/私钥对,并将公钥上传到您在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的帐户。 然后,您可以使用个人访问令牌进行身份验证,也可以通过 Web 浏览器进行身份验证。 有关使用 {% data variables.product.prodname_cli %} 进行身份验证的详细信息,请参阅 [`gh auth login`](https://cli.github.com/manual/gh_auth_login)。 +If you authenticate with {% data variables.product.prodname_cli %}, the CLI will find SSH public keys on your machine and will prompt you to select one for upload. If {% data variables.product.prodname_cli %} does not find a SSH public key for upload, it can generate a new SSH public/private keypair and upload the public key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. Then, you can either authenticate with a {% data variables.product.pat_generic %} or via the web browser. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). -如果您在没有 {% data variables.product.prodname_cli %} 的情况下进行身份验证,则需要在本地计算机上生成 SSH 公钥/私钥对,并将公钥添加到您在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的帐户。 有关详细信息,请参阅“[生成新的 SSH 密钥并将其添加到 ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)”。 除非你已[存储密钥](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent),否则每次使用 Git 向 {% data variables.product.product_name %} 进行身份验证时,系统都会提示你输入 SSH 密钥密码。 +If you authenticate without {% data variables.product.prodname_cli %}, you will need to generate an SSH public/private keypair on your local machine and add the public key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your SSH key passphrase, unless you've [stored the key](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent). {% ifversion fpt or ghec %} -### SAML 单点登录授权 +### Authorizing for SAML single sign-on -若要使用个人访问令牌或 SSH 密钥访问由使用 SAML 单一登录的组织所拥有的资源,还必须授权个人令牌或 SSH 密钥。 有关详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[授权个人访问令牌以用于 SAML 单一登录](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)”或“[授权 SSH 密钥以用于 SAML 单一登录](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}”。{% else %}."{% endif %}{% endif %} +To use a {% data variables.product.pat_generic %} or SSH key to access resources owned by an organization that uses SAML single sign-on, you must also authorize the personal token or SSH key. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} -## {% data variables.product.company_short %} 的令牌格式 +## {% data variables.product.company_short %}'s token formats -以前缀开头的 {% data variables.product.company_short %} 议题令牌表示令牌的类型。 +{% data variables.product.company_short %} issues tokens that begin with a prefix to indicate the token's type. -| 令牌类型 | 前缀 | 详细信息 | +| Token type | Prefix | More information | | :- | :- | :- | -| 个人访问令牌 | `ghp_` | “[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)” | -| OAuth 访问令牌 | `gho_` | “[授权 {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)” | -| {% data variables.product.prodname_github_app %} 的用户到服务器令牌 | `ghu_` | “[针对 {% data variables.product.prodname_github_apps %} 识别和授权用户](/developers/apps/identifying-and-authorizing-users-for-github-apps)” | -| {% data variables.product.prodname_github_app %} 的服务器到服务器令牌 | `ghs_` | “[使用 {% data variables.product.prodname_github_apps %} 进行身份验证](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)” | -| {% data variables.product.prodname_github_app %} 的刷新令牌 | `ghr_` | “[刷新用户到服务器访问令牌](/developers/apps/refreshing-user-to-server-access-tokens)” | +| {% data variables.product.pat_generic_caps %} | `ghp_` | "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)" | +| OAuth access token | `gho_` | "[Authorizing {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)" | +| User-to-server token for a {% data variables.product.prodname_github_app %} | `ghu_` | "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/developers/apps/identifying-and-authorizing-users-for-github-apps)" | +| Server-to-server token for a {% data variables.product.prodname_github_app %} | `ghs_` | "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)" | +| Refresh token for a {% data variables.product.prodname_github_app %} | `ghr_` | "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)" | diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md index 917b71a114..9eaad2d5c4 100644 --- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md +++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md @@ -1,6 +1,6 @@ --- -title: 授权 OAuth 应用 -intro: '您可以将 {% data variables.product.product_name %} 身份连接到使用 OAuth 的第三方应用程序。 在授权 {% data variables.product.prodname_oauth_app %} 时,应确保您信任应用程序,查阅开发者是谁,并查阅应用程序要访问的信息类型。' +title: Authorizing OAuth Apps +intro: 'You can connect your {% data variables.product.product_name %} identity to third-party applications using OAuth. When authorizing an {% data variables.product.prodname_oauth_app %}, you should ensure you trust the application, review who it''s developed by, and review the kinds of information the application wants to access.' redirect_from: - /articles/authorizing-oauth-apps - /github/authenticating-to-github/authorizing-oauth-apps @@ -13,95 +13,89 @@ versions: topics: - Identity - Access management -ms.openlocfilehash: a6205e33d29170c7ff72ad6f6d6ede45c0145ef6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147423162' --- -当 {% data variables.product.prodname_oauth_app %} 想要通过您在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}上的帐户识别您时,您会看到一个页面,其中包含该应用的开发者联系信息以及所请求的特定数据列表。 +When an {% data variables.product.prodname_oauth_app %} wants to identify you by your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, you'll see a page with the app's developer contact information and a list of the specific data that's being requested. {% ifversion fpt or ghec %} {% tip %} -提示:必须先[验证电子邮件地址](/articles/verifying-your-email-address),才能为 {% data variables.product.prodname_oauth_app %} 授权。 +**Tip:** You must [verify your email address](/articles/verifying-your-email-address) before you can authorize an {% data variables.product.prodname_oauth_app %}. {% endtip %} {% endif %} -## {% data variables.product.prodname_oauth_app %} 访问 +## {% data variables.product.prodname_oauth_app %} access -{% data variables.product.prodname_oauth_apps %} 可以具有对 {% data variables.product.product_name %} 数据的读取或写入权限 。 +{% data variables.product.prodname_oauth_apps %} can have *read* or *write* access to your {% data variables.product.product_name %} data. -- 读取权限仅允许应用查看数据。 -- 写入权限允许应用更改数据。 +- **Read access** only allows an app to *look at* your data. +- **Write access** allows an app to *change* your data. {% tip %} -提示:{% data reusables.user-settings.review_oauth_tokens_tip %} +**Tip:** {% data reusables.user-settings.review_oauth_tokens_tip %} {% endtip %} -### 关于 OAuth 范围 +### About OAuth scopes -范围是 {% data variables.product.prodname_oauth_app %} 可以申请访问公共及非公共数据的权限组。 +*Scopes* are named groups of permissions that an {% data variables.product.prodname_oauth_app %} can request to access both public and non-public data. -当您想使用集成了 {% data variables.product.product_name %} 的 {% data variables.product.prodname_oauth_app %} 时,该应用程序可让您了解需要的数据访问权限类型。 如果您授予应用程序访问权限,则应用程序将能代您执行操作,例如读取或修改数据。 例如,如果要使用请求 `user:email` 作用域的应用,该应用将具有对专用电子邮件地址的只读访问权限。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_oauth_apps %} 的范围](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)”。 +When you want to use an {% data variables.product.prodname_oauth_app %} that integrates with {% data variables.product.product_name %}, that app lets you know what type of access to your data will be required. If you grant access to the app, then the app will be able to perform actions on your behalf, such as reading or modifying data. For example, if you want to use an app that requests `user:email` scope, the app will have read-only access to your private email addresses. For more information, see "[About scopes for {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)." {% tip %} -注意:目前,无法将源代码访问范围限定为只读。 +**Note:** Currently, you can't scope source code access to read-only. {% endtip %} {% data reusables.apps.oauth-token-limit %} -### 申请的数据类型 +### Types of requested data -{% data variables.product.prodname_oauth_apps %} 可以申请多种类型的数据。 +{% data variables.product.prodname_oauth_apps %} can request several types of data. -| 数据类型 | 说明 | +| Type of data | Description | | --- | --- | -| 提交状态 | 您可以授权应用程序报告您的提交状态。 提交状态访问权限允许应用程序确定对特定提交的构建是否成功。 应用程序无法访问您的代码,但可以读取和写入特定提交的状态信息。 | -| 部署 | 部署状态访问权限允许应用程序根据公共和私有仓库的特定提交确定部署是否成功。 应用程序无法访问您的代码。 | -| Gists | [Gist](https://gist.github.com) 访问权限允许应用读取或写入公共和机密 Gist。 | -| 挂钩 | [Webhook](/webhooks) 访问权限允许应用在你管理的存储库上读取或写入挂钩配置。 | -| 通知 | 通知访问权限允许应用程序读取您的 {% data variables.product.product_name %} 通知,如议题和拉取请求的评论。 但应用程序仍然无法访问仓库中的任何内容。 | -| Organizations and teams(组织和团队) | 组织和团队访问权限允许应用程序访问并管理组织和团队成员资格。 | -| 个人用户数据 | 用户数据包括您的用户个人资料中的信息,例如您的姓名、电子邮件地址和地点。 | -| 存储库 | 仓库信息包括贡献者的姓名、您创建的分支以及仓库中的实际文件。 应用程序可以申请访问用户级别的公共或私有仓库。 | -| 仓库删除 | 应用程序可以申请删除您管理的仓库,但无法访问您的代码。 |{% ifversion projects-oauth-scope %} -| 项目 | 访问用户和组织 {% data variables.projects.projects_v2 %}。 应用可以请求读/写或只读访问权限。 |{% endif %} +| Commit status | You can grant access for an app to report your commit status. Commit status access allows apps to determine if a build is a successful against a specific commit. Apps won't have access to your code, but they can read and write status information against a specific commit. | +| Deployments | Deployment status access allows apps to determine if a deployment is successful against a specific commit for public and private repositories. Apps won't have access to your code. | +| Gists | [Gist](https://gist.github.com) access allows apps to read or write to both your public and secret Gists. | +| Hooks | [Webhooks](/webhooks) access allows apps to read or write hook configurations on repositories you manage. | +| Notifications | Notification access allows apps to read your {% data variables.product.product_name %} notifications, such as comments on issues and pull requests. However, apps remain unable to access anything in your repositories. | +| Organizations and teams | Organization and teams access allows apps to access and manage organization and team membership. | +| Personal user data | User data includes information found in your user profile, like your name, e-mail address, and location. | +| Repositories | Repository information includes the names of contributors, the branches you've created, and the actual files within your repository. Apps can request access for either public or private repositories on a user-wide level. | +| Repository delete | Apps can request to delete repositories that you administer, but they won't have access to your code. |{% ifversion projects-oauth-scope %} +| Projects | Access to user and organization {% data variables.projects.projects_v2 %}. Apps can request either read/write or read only access. |{% endif %} -## 申请更新的权限 +## Requesting updated permissions -当 {% data variables.product.prodname_oauth_apps %} 申请新的访问权限时,将会通知其当前权限与新权限之间的差异。 +When {% data variables.product.prodname_oauth_apps %} request new access permissions, they will notify you of the differences between their current permissions and the new permissions. {% ifversion fpt or ghec %} -## {% data variables.product.prodname_oauth_apps %} 和组织 +## {% data variables.product.prodname_oauth_apps %} and organizations -当你授权 {% data variables.product.prodname_oauth_app %} 访问你的个人帐户时,你还会看到该授权对你所在的每个组织的影响。 +When you authorize an {% data variables.product.prodname_oauth_app %} for your personal account, you'll also see how the authorization will affect each organization you're a member of. -- 对于具有 {% data variables.product.prodname_oauth_app %} 访问限制的组织,你可以请求组织管理员批准应用程序在该组织中使用。 如果组织未批准应用程序,则应用程序只能访问组织的公共资源。 如果你是组织管理员,则可以自行[批准应用程序](/articles/approving-oauth-apps-for-your-organization)。 +- **For organizations *with* {% data variables.product.prodname_oauth_app %} access restrictions, you can request that organization admins approve the application for use in that organization.** If the organization does not approve the application, then the application will only be able to access the organization's public resources. If you're an organization admin, you can [approve the application](/articles/approving-oauth-apps-for-your-organization) yourself. -- 对于没有 {% data variables.product.prodname_oauth_app %} 访问限制的组织,将自动授予应用程序对该组织资源的访问权限。 因此,应注意批准哪些 {% data variables.product.prodname_oauth_apps %} 访问你的个人帐户资源以及任何组织资源。 +- **For organizations *without* {% data variables.product.prodname_oauth_app %} access restrictions, the application will automatically be authorized for access to that organization's resources.** For this reason, you should be careful about which {% data variables.product.prodname_oauth_apps %} you approve for access to your personal account resources as well as any organization resources. -如果您属于任何实施 SAML 单点登录的组织,则在每次授权 {% data variables.product.prodname_oauth_app %} 时每个组织都必须有一个活动的 SAML 会话。 +If you belong to any organizations that enforce SAML single sign-on, you must have an active SAML session for each organization each time you authorize an {% data variables.product.prodname_oauth_app %}. {% note %} -注意:如果你在对强制实施 SAML 单一登录的组织进行身份验证时遇到错误,则可能需要从[帐户设置页](https://github.com/settings/applications)撤销 OAuth 应用并重复身份验证流程以重新为应用授权。 +**Note:** If you are encountering errors authenticating to an organization that enforces SAML single sign-on, you may need to revoke the OAuth App from your [account settings page](https://github.com/settings/applications) and repeat the authentication flow to reauthorize the app. {% endnote %} -## 延伸阅读 +## Further reading -- [关于 {% data variables.product.prodname_oauth_app %} 访问限制](/articles/about-oauth-app-access-restrictions) -- [为 GitHub 应用授权](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps) -- [{% data variables.product.prodname_marketplace %} 支持](/articles/github-marketplace-support) +- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)" +- "[Authorizing GitHub Apps](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)" +- "[{% data variables.product.prodname_marketplace %} support](/articles/github-marketplace-support)" {% endif %} diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md index 12449e35bf..88febb34fe 100644 --- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md +++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md @@ -1,6 +1,6 @@ --- -title: 创建个人访问令牌 -intro: 可以通过命令行或 API 创建个人访问令牌来代替密码。 +title: Creating a personal access token +intro: You can create a {% data variables.product.pat_generic %} to use in place of a password with the command line or with the API. redirect_from: - /articles/creating-an-oauth-token-for-command-line-use - /articles/creating-an-access-token-for-command-line-use @@ -17,60 +17,131 @@ versions: topics: - Identity - Access management -shortTitle: Create a PAT -ms.openlocfilehash: 437e06ba2fdf82252702106600ac6da73ee4c792 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147064424' +shortTitle: Create a {% data variables.product.pat_generic %} --- -{% note %} -**注意:** +{% warning %} -- 如果在命令行上使用 {% data variables.product.prodname_cli %} 向 {% data variables.product.product_name %} 进行身份验证,可跳过生成个人访问令牌,并通过 Web 浏览器进行身份验证。 有关使用 {% data variables.product.prodname_cli %} 进行身份验证的详细信息,请参阅 [`gh auth login`](https://cli.github.com/manual/gh_auth_login)。 -- [Git 凭据管理器](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md)是使用个人访问令牌 (PAT) 的安全跨平台替代方案,无需管理 PAT 范围和到期日期。 有关安装说明,请参阅 GitCredentialManager/git-credential-manager 存储库中的[下载和安装](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md#download-and-install)。 +**Warning**: Treat your access tokens like passwords. -{% endnote %} +To access {% data variables.product.company_short %} from the command line, consider using {% data variables.product.prodname_cli %} or [Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md) instead of creating a {% data variables.product.pat_generic %}. -使用 [GitHub API](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) 或[命令行](#using-a-token-on-the-command-line)时,可使用个人访问令牌 (PAT) 替代密码向 {% data variables.product.product_name %} 进行身份验证。 +When using a {% data variables.product.pat_generic %} in a script, consider storing your token as a secret and running your script through {% data variables.product.prodname_actions %}. For more information, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."{%- ifversion ghec or fpt %} You can also store your token as a {% data variables.product.prodname_codespaces %} secret and run your script in {% data variables.product.prodname_codespaces %}. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."{% endif %} -{% ifversion fpt or ghec %}如果要使用 PAT 访问使用 SAML SSO 的组织所拥有的资源,则必须授权 PAT。 有关详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[关于使用 SAML 单一登录进行身份验证](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)”和“[授权个人访问令牌以用于 SAML 单一登录](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}”。{% else %}”。{% endif %}{% endif %} +If these options are not possible, consider using another service such as [the 1Password CLI](https://developer.1password.com/docs/cli/secret-references/) to store your token securely. + +{% endwarning %} + +## About {% data variables.product.pat_generic %}s + +{% data variables.product.pat_generic_caps %} are an alternative to using passwords for authentication to {% data variables.product.product_name %} when using the [GitHub API](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) or the [command line](#using-a-token-on-the-command-line). {% data variables.product.pat_generic_caps %}s are intended to access {% data variables.product.company_short %} resources on behalf of yourself. To access resources on behalf of an organization, or for long-lived integrations, you should use a {% data variables.product.prodname_github_app %}. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)." + +{% ifversion pat-v2 %} + +{% data variables.product.company_short %} currently supports two types of {% data variables.product.pat_generic %}s: {% data variables.product.pat_v2 %}s and {% data variables.product.pat_v1_plural %}. {% data variables.product.company_short %} recommends that you use {% data variables.product.pat_v2 %}s instead of {% data variables.product.pat_v1_plural %} whenever possible. {% data variables.product.pat_v2_caps %}s have several security advantages over {% data variables.product.pat_v1_plural %}: + +- Each token can only access resources owned by a single user or organization. +- Each token can only access specific repositories. +- Each token is granted specific permissions, which offer more control than the scopes granted to {% data variables.product.pat_v1_plural %}. +- Each token must have an expiration date. +- Organization owners can require approval for any {% data variables.product.pat_v2 %}s that can access resources in the organization.{% ifversion ghec or ghes or ghae %} +- Enterprise owners can require approval for any {% data variables.product.pat_v2 %}s that can access resources in organizations owned by the enterprise.{% endif %} + +Additionally, organization owners can restrict the access of {% data variables.product.pat_v1 %} to their organization{% ifversion ghec or ghes or ghae %}, and enterprise owners can restrict the access of {% data variables.product.pat_v1 %} to the enterprise or organizations owned by the enterprise{% endif %}. + +{% data reusables.user-settings.patv2-limitations %} + +{% endif %} {% ifversion fpt or ghec %}{% data reusables.user-settings.removes-personal-access-tokens %}{% endif %} -没有指定范围的令牌只能访问公共信息。 若要使用令牌从命令行访问存储库,请选择 `repo`。 有关详细信息,请参阅“[可用范围](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)”。 +{% ifversion pat-v2 %} -## 创建令牌 +## Creating a {% data variables.product.pat_v2 %} -{% ifversion fpt or ghec %}1。 [验证电子邮件地址](/github/getting-started-with-github/verifying-your-email-address)(如果尚未验证)。{% endif %} {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.personal_access_tokens %} {% data reusables.user-settings.generate_new_token %} -5. 给令牌一个描述性名称。 - ![令牌描述字段](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae or ghec %} -6. 若要为令牌提供到期时间,请选择“到期”下拉菜单,然后单击默认值或使用日历选择器。 - ![令牌到期字段](/assets/images/help/settings/token_expiration.png){% endif %} -7. 选择要授予此令牌的作用域或权限。 若要使用令牌从命令行访问存储库,请选择“存储库”。 - {% ifversion fpt or ghes or ghec %}![选择令牌范围](/assets/images/help/settings/token_scopes.gif){% elsif ghae %}![选择令牌范围](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png){% endif %} -8. 单击“生成令牌”。 - ![“生成令牌”按钮](/assets/images/help/settings/generate_token.png){% ifversion fpt or ghec %}![新建的令牌](/assets/images/help/settings/personal_access_tokens.png){% elsif ghes or ghae %}![新建的令牌](/assets/images/help/settings/personal_access_tokens_ghe.png){% else %}![新建的令牌](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png){% endif %} {% warning %} +{% note %} - 警告:请将令牌视为密码,并保密。 使用 API 时,应将令牌用作环境变量,而不是将其硬编码到程序中。 +**Note**: {% data reusables.user-settings.pat-v2-beta %} - {% endwarning %} +{% endnote %} -{% ifversion fpt or ghec %}9. 要使用您的令牌向使用 SAML 单点登录的组织验证,请对令牌进行授权。 有关详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[授权个人访问令牌以用于 SAML 单一登录](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}”。{% else %}”。{% endif %}{% endif %} +{% ifversion fpt or ghec %}1. [Verify your email address](/github/getting-started-with-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %} +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Fine-grained tokens**. +1. Click **Generate new token**. +1. Optionally, under **Token name**, enter a name for the token. +1. Under **Expiration**, select an expiration for the token. +1. Optionally, under **Description**, add a note to describe the purpose of the token. +1. Under **Resource owner**, select a resource owner. The token will only be able to access resources owned by the selected resource owner. Organizations that you are a member of will not appear unless the organization opted in to {% data variables.product.pat_v2 %}s. For more information, see "[Setting a {% data variables.product.pat_generic %} policy for your organization](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization)."{% ifversion ghec or ghae %} You may be required to perform SAML single sign-on (SSO) if the selected organization requires it and you do not already have an active SAML session.{% endif %} +1. Optionally, if the resource owner is an organization that requires approval for {% data variables.product.pat_v2 %}s, below the resource owner, in the box, enter a justification for the request. +1. Under **Repository access**, select which repositories you want the token to access. You should choose the minimal repository access that meets your needs. Tokens always include read-only access to all public repositories on GitHub. +1. If you selected **Only select repositories** in the previous step, under the **Selected repositories** dropdown, select the repositories that you want the token to access. +1. Under **Permissions**, select which permissions to grant the token. Depending on which resource owner and which repository access you specified, there are repository, organization, and account permissions. You should choose the minimal permissions necessary for your needs. For more information about what permissions are required for each REST API operation, see "[Permissions required for {% data variables.product.pat_v2 %}s](/rest/overview/permissions-required-for-fine-grained-personal-access-tokens)." +1. Click **Generate token**. -## 在命令行上使用令牌 +If you selected an organization as the resource owner and the organization requires approval for {% data variables.product.pat_v2 %}s, then your token will be marked as `pending` until it is reviewed by an organization administrator. Your token will only be able to read public resources until it is approved. If you are an owner of the organization, your request is automatically approved. For more information, see "[Reviewing and revoking {% data variables.product.pat_generic %}s in your organization](/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization)". + +{% endif %} + +## Creating a {% data variables.product.pat_v1 %} + +{% ifversion pat-v2 %} + +{% note %} + +**Note**: Organization owners can restrict the access of {% data variables.product.pat_v1 %} to their organization. If you try to use a {% data variables.product.pat_v1 %} to access resources in an organization that has disabled {% data variables.product.pat_v1 %} access, your request will fail with a 403 response. Instead, you must use a {% data variables.product.prodname_github_app %}, {% data variables.product.prodname_oauth_app %}, or {% data variables.product.pat_v2 %}. + +{% endnote %} + +{% endif %} + +{% ifversion pat-v2 %} + +{% warning %} + +**Note**: Your {% data variables.product.pat_v1 %} can access every repository that you can access. {% data variables.product.company_short %} recommends that you use {% data variables.product.pat_v2 %}s instead, which you can restrict to specific repositories. {% data variables.product.pat_v2_caps %}s also enable you to specify fine-grained permissions instead of broad scopes. + +{% endwarning %} + +{% endif %} + +{% ifversion fpt or ghec %}1. [Verify your email address](/github/getting-started-with-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %} +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.developer_settings %} +{% ifversion pat-v2 %}1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Tokens (classic)**.{% else %}{% data reusables.user-settings.personal_access_tokens %}{% endif %} +{% ifversion pat-v2%}1. Select **Generate new token**, then click **Generate new token (classic)**.{% else %}{% data reusables.user-settings.generate_new_token %}{% endif %} +5. Give your token a descriptive name. + ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae or ghec %} +6. To give your token an expiration, select the **Expiration** drop-down menu, then click a default or use the calendar picker. + ![Token expiration field](/assets/images/help/settings/token_expiration.png){% endif %} +7. Select the scopes you'd like to grant this token. To use your token to access repositories from the command line, select **repo**. A token with no assigned scopes can only access public information. For more information, see "[Available scopes](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)". + {% ifversion fpt or ghes or ghec %} + ![Selecting token scopes](/assets/images/help/settings/token_scopes.gif) + {% elsif ghae %} + ![Selecting token scopes](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png) + {% endif %} +8. Click **Generate token**. + ![Generate token button](/assets/images/help/settings/generate_token.png) + {% ifversion fpt or ghec %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens.png) + {% elsif ghes or ghae %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe.png) + {% else %} + ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png){% endif %}{% ifversion fpt or ghec %} +1. To use your token to access resources owned by an organization that uses SAML single sign-on, authorize the token. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} + +## Using a token on the command line {% data reusables.command_line.providing-token-as-password %} -个人访问令牌只能用于 HTTPS Git 操作。 如果存储库使用 SSH 远程 URL,则需要[将远程 URL 从 SSH 切换到 HTTPS](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-ssh-to-https)。 +{% data variables.product.pat_generic_caps %}s can only be used for HTTPS Git operations. If your repository uses an SSH remote URL, you will need to [switch the remote from SSH to HTTPS](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-ssh-to-https). -如果没有提示您输入用户名和密码,说明您的凭据可能已缓存在计算机上。 可[在密钥链中更新凭据](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain),从而用令牌替换旧密码。 +If you are not prompted for your username and password, your credentials may be cached on your computer. You can [update your credentials in the Keychain](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain) to replace your old password with the token. -您可以使用 Git 客户端缓存 PAT,而不必为每个 HTTPS Git 操作手动输入 PAT。 Git 会将您的凭据临时存储在内存中,直到过期为止。 您还可以将令牌存储在 Git 可以在每个请求之前读取的纯文本文件中。 有关详细信息,请参阅“[在 Git 中缓存 {% data variables.product.prodname_dotcom %} 凭据](/github/getting-started-with-github/caching-your-github-credentials-in-git)”。 +Instead of manually entering your {% data variables.product.pat_generic %} for every HTTPS Git operation, you can cache your {% data variables.product.pat_generic %} with a Git client. Git will temporarily store your credentials in memory until an expiry interval has passed. You can also store the token in a plain text file that Git can read before every request. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)." -## 延伸阅读 +## Further reading -- [关于 GitHub 身份验证](/github/authenticating-to-github/about-authentication-to-github){% ifversion fpt or ghae or ghes > 3.2 or ghec %} -- “[令牌过期和吊销](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)”{% endif %} +- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %} +- "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md index 113af7ff12..758beda311 100644 --- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md +++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md @@ -1,6 +1,6 @@ --- -title: 创建强密码 -intro: '使用密码管理器以强大而唯一的密码保护您在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的帐户。' +title: Creating a strong password +intro: 'Secure your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} with a strong and unique password using a password manager.' redirect_from: - /articles/what-is-a-strong-password - /articles/creating-a-strong-password @@ -14,31 +14,25 @@ topics: - Identity - Access management shortTitle: Create a strong password -ms.openlocfilehash: 97473f9b04c8d033471f89cac9a0b0d08bebcba3 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145084655' --- -您必须在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上为您的帐户选择或生成一个密码,该密码至少是: -- {% ifversion ghes %}七{% else %}八{% endif %}个字符且包含数字和小写字母,或 -- 至少 15 个字符,任意字符组合 +You must choose or generate a password for your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} that is at least: +- {% ifversion ghes %}Seven{% else %}Eight{% endif %} characters long, if it includes a number and a lowercase letter, or +- 15 characters long with any combination of characters -为确保您的帐户安全,我们建议您遵循以下最佳实践: -- 使用密码管理器(例如 [LastPass](https://lastpass.com/) 或 [1Password](https://1password.com/))生成至少 15 个字符的密码。 -- 为 {% data variables.product.product_name %} 生成唯一的密码。 如果您在其他地方使用 {% data variables.product.product_name %} 密码,并且该服务遭到入侵,则攻击者或其他恶意行为者可能会使用该信息访问您在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的帐户。 +To keep your account secure, we recommend you follow these best practices: +- Use a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/), to generate a password of at least 15 characters. +- Generate a unique password for {% data variables.product.product_name %}. If you use your {% data variables.product.product_name %} password elsewhere and that service is compromised, then attackers or other malicious actors could use that information to access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. -- 为您的帐户配置双重身份验证。 有关详细信息,请参阅[关于双因素身份验证](/articles/about-two-factor-authentication)。 -- 不与任何人分享您的密码,即使是潜在协作者。 在 {% data variables.product.product_name %} 上每个人都应使用自己的个人帐户。 有关协作方式的详细信息,请参阅:“[邀请协作者加入个人存储库](/articles/inviting-collaborators-to-a-personal-repository)”、“[关于协作开发模型](/articles/about-collaborative-development-models/)”或“[与组织中的团体协作](/organizations/collaborating-with-groups-in-organizations/)。” +- Configure two-factor authentication for your personal account. For more information, see "[About two-factor authentication](/articles/about-two-factor-authentication)." +- Never share your password, even with a potential collaborator. Each person should use their own personal account on {% data variables.product.product_name %}. For more information on ways to collaborate, see: "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)," "[About collaborative development models](/articles/about-collaborative-development-models/)," or "[Collaborating with groups in organizations](/organizations/collaborating-with-groups-in-organizations/)." {% data reusables.repositories.blocked-passwords %} -您只能使用密码通过浏览器登录 {% data variables.product.product_name %}。 使用其他方式(例如命令行或 API)向 {% data variables.product.product_name %} 验证时,应使用其他凭据。 有关详细信息,请参阅“[关于对 {% data variables.product.prodname_dotcom %} 的身份验证](/github/authenticating-to-github/about-authentication-to-github)”。 +You can only use your password to log on to {% data variables.product.product_name %} using your browser. When you authenticate to {% data variables.product.product_name %} with other means, such as the command line or API, you should use other credentials. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)." {% ifversion fpt or ghec %}{% data reusables.user-settings.password-authentication-deprecation %}{% endif %} -## 延伸阅读 +## Further reading -- [在 Git 中缓存 {% data variables.product.product_name %} 凭据](/github/getting-started-with-github/caching-your-github-credentials-in-git/) -- [保护帐户和数据安全](/articles/keeping-your-account-and-data-secure/) +- "[Caching your {% data variables.product.product_name %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)" +- "[Keeping your account and data secure](/articles/keeping-your-account-and-data-secure/)" diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/index.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/index.md index 2057971b43..3e202cd327 100644 --- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/index.md +++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/index.md @@ -1,6 +1,6 @@ --- -title: 保护帐户和数据安全 -intro: '为了保护您的个人信息,应该确保您在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的帐户和任何相关数据的安全。' +title: Keeping your account and data secure +intro: 'To protect your personal information, you should keep both your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} and any associated data secure.' redirect_from: - /articles/keeping-your-account-and-data-secure - /github/authenticating-to-github/keeping-your-account-and-data-secure @@ -33,11 +33,5 @@ children: - /sudo-mode - /preventing-unauthorized-access shortTitle: Account security -ms.openlocfilehash: 39ccc832d4584952bc03cd484cfe72080ccfaa18 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145084653' --- diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md index 5e9e3a0692..a0bcd546ee 100644 --- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md +++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md @@ -1,6 +1,6 @@ --- -title: 防止未授权的访问 -intro: '在登录 {% data variables.product.product_location %} 时,你可能会收到媒体中安全事件的警报,如发现 [Heartbleed bug](http://heartbleed.com/) 或计算机被盗。 在这种情况下,更改密码可防止后面对您的帐户和项目的任何非预期访问。' +title: Preventing unauthorized access +intro: 'You may be alerted to a security incident in the media, such as the discovery of the [Heartbleed bug](http://heartbleed.com/), or your computer could be stolen while you''re signed in to {% data variables.location.product_location %}. In such cases, changing your password prevents any unintended future access to your account and projects.' redirect_from: - /articles/preventing-unauthorized-access - /github/authenticating-to-github/preventing-unauthorized-access @@ -13,24 +13,18 @@ topics: - Identity - Access management shortTitle: Unauthorized access -ms.openlocfilehash: 2b7a29ad3df05ef758c82330f24fe7568e137130 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145084651' --- -{% data variables.product.product_name %} 需要密码来执行敏感的操作,如新增 SSH 密钥、授权应用程序或修改团队成员。 +{% data variables.product.product_name %} requires a password to perform sensitive actions, such as adding new SSH keys, authorizing applications, or modifying team members. -在更改密码后,应执行以下操作,以确保您的帐户安全: +After changing your password, you should perform these actions to make sure that your account is secure: -- 在帐户上[启用双因素身份验证](/articles/about-two-factor-authentication),以便访问时不止需要提供密码。 -- [查看 SSH 密钥](/articles/reviewing-your-ssh-keys)、[部署密钥](/articles/reviewing-your-deploy-keys)和[授权集成](/articles/reviewing-your-authorized-integrations),并在 SSH 和应用程序设置中撤销未经授权的或不熟悉的访问权限。 +- [Enable two-factor authentication](/articles/about-two-factor-authentication) on your account so that access requires more than just a password. +- [Review your SSH keys](/articles/reviewing-your-ssh-keys), [deploy keys](/articles/reviewing-your-deploy-keys), and [authorized integrations](/articles/reviewing-your-authorized-integrations) and revoke unauthorized or unfamiliar access in your SSH and Applications settings. {% ifversion fpt or ghec %} -- [验证所有电子邮件地址](/articles/verifying-your-email-address)。 如果攻击者在您的帐户中添加了他们的电子邮件地址,他们可能实施非预期的密码重置。 +- [Verify all your email addresses](/articles/verifying-your-email-address). If an attacker added their email address to your account, it could allow them to force an unintended password reset. {% endif %} -- [查看帐户的安全日志](/github/authenticating-to-github/reviewing-your-security-log)。 其中概述了您的仓库的各种配置。 例如,您可以确保没有私有仓库改为公共,或没有仓库被转让。 -- 查看存储库上的 [Webhook](/articles/creating-webhooks)。 Web 挂钩可能允许攻击者拦截到仓库的推送。 -- [确保未创建新的部署密钥](/guides/managing-deploy-keys/#deploy-keys)。 这可能允许外部服务器访问您的项目。 -- 检查最近对仓库的提交。 -- 检查每个仓库的协作者列表。 +- [Review your account's security log](/github/authenticating-to-github/reviewing-your-security-log). This provides an overview on various configurations made to your repositories. For example, you can ensure that no private repositories were turned public, or that no repositories were transferred. +- [Review the webhooks](/articles/creating-webhooks) on your repositories. Webhooks could allow an attacker to intercept pushes made to your repository. +- [Make sure that no new deploy keys](/guides/managing-deploy-keys/#deploy-keys) were created. This could enable outside servers access to your projects. +- Review recent commits made to your repositories. +- Review the list of collaborators for each repository. diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md index 1ada04e306..1f4dc55b3f 100644 --- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md +++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md @@ -1,6 +1,6 @@ --- -title: 从存储库中删除敏感数据 -intro: 如果将敏感数据(例如密码或 SSH 密钥)提交到 Git 仓库,您可以将其从历史记录中删除。 要从存储库的历史记录中彻底删除不需要的文件,可以使用 `git filter-repo` 工具或 BFG Repo-Cleaner 开放源代码工具。 +title: Removing sensitive data from a repository +intro: 'If you commit sensitive data, such as a password or SSH key into a Git repository, you can remove it from the history. To entirely remove unwanted files from a repository''s history you can use either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool.' redirect_from: - /remove-sensitive-data - /removing-sensitive-data @@ -17,88 +17,86 @@ topics: - Identity - Access management shortTitle: Remove sensitive data -ms.openlocfilehash: 4c93f372f1d537fd94f06e66986e53d6641923d2 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145084649' --- -`git filter-repo` 工具和 BFG Repo-Cleaner 将重写存储库的历史记录,这将更改你更改的现有提交的 SHA,以及任何相关的提交。 更改的提交 SHA 可能会影响存储库中未完结的拉取请求。 我们建议在从存储库中删除文件之前合并或关闭所有未完结的拉取请求。 +The `git filter-repo` tool and the BFG Repo-Cleaner rewrite your repository's history, which changes the SHAs for existing commits that you alter and any dependent commits. Changed commit SHAs may affect open pull requests in your repository. We recommend merging or closing all open pull requests before removing files from your repository. -可以使用 `git rm` 从最新提交中删除文件。 有关删除在最新提交中添加的文件的信息,请参阅“[关于 {% data variables.product.prodname_dotcom %} 上的大型文件](/repositories/working-with-files/managing-large-files/about-large-files-on-github#removing-files-from-a-repositorys-history)。” +You can remove the file from the latest commit with `git rm`. For information on removing a file that was added with the latest commit, see "[About large files on {% data variables.product.prodname_dotcom %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github#removing-files-from-a-repositorys-history)." {% warning %} -警告:本文说明如何使用无法从 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上存储库中的任何分支或标记访问的敏感数据进行提交。 但是,这些提交在你存储库的任何克隆或分支中、直接通过 {% data variables.product.product_name %} 上缓存视图中其 SHA-1 哈希以及通过引用它们的任何拉取请求可能仍然可访问。 您无法从仓库的其他用户的克隆或复刻删除敏感数据,但您可以通过联系 {% data variables.contact.contact_support %},永久删除 {% data variables.product.product_name %} 上拉取请求中敏感数据的缓存视图和引用。 +**Warning**: This article tells you how to make commits with sensitive data unreachable from any branches or tags in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. However, those commits may still be accessible in any clones or forks of your repository, directly via their SHA-1 hashes in cached views on {% data variables.product.product_name %}, and through any pull requests that reference them. You cannot remove sensitive data from other users' clones of your repository, but you can permanently remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %} by contacting {% data variables.contact.contact_support %}. -将提交推送到 {% data variables.product.product_name %} 后,应将提交中的所有敏感数据视为泄露。 如果你提交了密码,请更改密码! 如果您提交了密钥,请生成新密钥。 删除泄露的数据并不能解决其初始暴露问题,尤其是在仓库的现有克隆或复刻中。 在重写仓库历史记录的决定中考虑这些限制。 +If the commit that introduced the sensitive data exists in any forks of your repository, it will continue to be accessible, unless the fork owner removes the sensitive data from their fork or deletes the fork entirely. + +Once you have pushed a commit to {% data variables.product.product_name %}, you should consider any sensitive data in the commit compromised. If you have committed a password, you should change it. If you have committed a key, generate a new one. Removing the compromised data doesn't resolve its initial exposure, especially in existing clones or forks of your repository. + +Consider these limitations in your decision to rewrite your repository's history. {% endwarning %} -## 从仓库的历史记录中清除文件 +## Purging a file from your repository's history -你可以使用 `git filter-repo` 工具或 BFG Repo-Cleaner 开源工具从存储库的历史记录中清除文件。 +You can purge a file from your repository's history using either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool. -### 使用 BFG +### Using the BFG -[BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) 是由开源社区生成和维护的工具。 它提供了一种可替代 `git filter-branch` 的更快、更简单的方法,用于删除不需要的数据。 +The [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) is a tool that's built and maintained by the open source community. It provides a faster, simpler alternative to `git filter-branch` for removing unwanted data. -例如,要删除包含敏感数据的文件并保持最新提交不变,请运行: +For example, to remove your file with sensitive data and leave your latest commit untouched, run: ```shell -$ bfg --delete-files YOUR-FILE-WITH-SENSITIVE-DATA +$ bfg --delete-files YOUR-FILE-WITH-SENSITIVE-DATA ``` -要替换可以在存储库的历史记录中找到的 `passwords.txt` 列出的所有文本,请运行: +To replace all text listed in `passwords.txt` wherever it can be found in your repository's history, run: ```shell $ bfg --replace-text passwords.txt ``` -删除敏感数据后,必须强制将更改推送到 {% data variables.product.product_name %}。 强制推送会重写存储库历史记录,这会从提交历史记录中删除敏感数据。 如果强制推送,它可能会覆盖其他人基于其工作的提交。 +After the sensitive data is removed, you must force push your changes to {% data variables.product.product_name %}. Force pushing rewrites the repository history, which removes sensitive data from the commit history. If you force push, it may overwrite commits that other people have based their work on. ```shell $ git push --force ``` -有关完整的使用情况和下载说明,请参阅 [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) 的文档。 +See the [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/)'s documentation for full usage and download instructions. -### 使用 git filter-repo +### Using git filter-repo {% warning %} -**警告:** 如果在储藏更改之后运行 `git filter-repo`,则无法使用其他储藏命令检索更改。 在运行 `git filter-repo` 之前,建议取消储藏所做的任何更改。 要取消储藏你已储藏的最后一组更改,请运行 `git stash show -p | git apply -R`。 有关详细信息,请参阅 [Git 工具 - 储藏和清理](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning)。 +**Warning:** If you run `git filter-repo` after stashing changes, you won't be able to retrieve your changes with other stash commands. Before running `git filter-repo`, we recommend unstashing any changes you've made. To unstash the last set of changes you've stashed, run `git stash show -p | git apply -R`. For more information, see [Git Tools - Stashing and Cleaning](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning). {% endwarning %} -为了说明 `git filter-repo` 的工作原理,我们将向你展示如何从存储库的历史记录中删除包含敏感数据的文件,并将其添加到 `.gitignore`,以确保不会意外地重新提交。 +To illustrate how `git filter-repo` works, we'll show you how to remove your file with sensitive data from the history of your repository and add it to `.gitignore` to ensure that it is not accidentally re-committed. -1. 安装 [git filter-repo](https://github.com/newren/git-filter-repo) 工具的最新版本。 可以手动安装 `git-filter-repo`,也可以使用包管理器安装。 例如,若使用 HomeBrew 安装工具,请使用 `brew install` 命令。 +1. Install the latest release of the [git filter-repo](https://github.com/newren/git-filter-repo) tool. You can install `git-filter-repo` manually or by using a package manager. For example, to install the tool with HomeBrew, use the `brew install` command. ``` brew install git-filter-repo ``` - 有关详细信息,请参阅 `newren/git-filter-repo` 存储库中的 [INSTALL.md](https://github.com/newren/git-filter-repo/blob/main/INSTALL.md)。 + For more information, see [*INSTALL.md*](https://github.com/newren/git-filter-repo/blob/main/INSTALL.md) in the `newren/git-filter-repo` repository. -2. 如果存储库的本地副本的历史记录中没有敏感数据,请[将存储库克隆到本地计算机](/articles/cloning-a-repository/)。 +2. If you don't already have a local copy of your repository with sensitive data in its history, [clone the repository](/articles/cloning-a-repository/) to your local computer. ```shell - $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY - > Initialized empty Git repository in /Users/YOUR-FILE-PATH/YOUR-REPOSITORY/.git/ + $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY + > Initialized empty Git repository in /Users/YOUR-FILE-PATH/YOUR-REPOSITORY/.git/ > remote: Counting objects: 1301, done. > remote: Compressing objects: 100% (769/769), done. > remote: Total 1301 (delta 724), reused 910 (delta 522) > Receiving objects: 100% (1301/1301), 164.39 KiB, done. > Resolving deltas: 100% (724/724), done. ``` -3. 导航到存储库的工作目录。 +3. Navigate into the repository's working directory. ```shell - $ cd YOUR-REPOSITORY + $ cd YOUR-REPOSITORY ``` -4. 运行以下命令,将 `PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA` 替换为要删除的文件的路径,而不只是其文件名。 这些参数将: - - 强制 Git 处理(而不是签出)每个分支和标记的整个历史记录 - - 删除指定的文件,以及作为结果生成的任何空提交 - - 删除存储在 .git/config 文件中的某些配置,例如远程 URL。 你可能需要提前备份此文件,以便稍后还原。 - - **覆盖现有标记** +4. Run the following command, replacing `PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA` with the **path to the file you want to remove, not just its filename**. These arguments will: + - Force Git to process, but not check out, the entire history of every branch and tag + - Remove the specified file, as well as any empty commits generated as a result + - Remove some configurations, such as the remote URL, stored in the *.git/config* file. You may want to back up this file in advance for restoration later. + - **Overwrite your existing tags** ```shell $ git filter-repo --invert-paths --path PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA Parsed 197 commits @@ -116,21 +114,21 @@ $ git push --force {% note %} - **注意:** 如果包含敏感数据的文件以前存在于任何其他路径(因为它被移动或重命名),则也必须在这些路径上运行此命令。 + **Note:** If the file with sensitive data used to exist at any other paths (because it was moved or renamed), you must run this command on those paths, as well. {% endnote %} -5. 将包含敏感数据的文件添加到 `.gitignore`,以确保不会意外地再次提交。 +5. Add your file with sensitive data to `.gitignore` to ensure that you don't accidentally commit it again. ```shell - $ echo "YOUR-FILE-WITH-SENSITIVE-DATA" >> .gitignore + $ echo "YOUR-FILE-WITH-SENSITIVE-DATA" >> .gitignore $ git add .gitignore - $ git commit -m "Add YOUR-FILE-WITH-SENSITIVE-DATA to .gitignore" - > [main 051452f] Add YOUR-FILE-WITH-SENSITIVE-DATA to .gitignore + $ git commit -m "Add YOUR-FILE-WITH-SENSITIVE-DATA to .gitignore" + > [main 051452f] Add YOUR-FILE-WITH-SENSITIVE-DATA to .gitignore > 1 files changed, 1 insertions(+), 0 deletions(-) ``` -6. 仔细检查是否已从存储库的历史记录中删除了所需的所有内容,并且已签出所有分支。 -7. 在对存储库的状态感到满意,请强制推送本地更改以覆盖 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}上的存储库,以及您向上推送的所有分支。 需要强制推送才能从提交历史记录中删除敏感数据。 +6. Double-check that you've removed everything you wanted to from your repository's history, and that all of your branches are checked out. +7. Once you're happy with the state of your repository, force-push your local changes to overwrite your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, as well as all the branches you've pushed up. A force push is required to remove sensitive data from your commit history. ```shell $ git push origin --force --all > Counting objects: 1074, done. @@ -138,10 +136,10 @@ $ git push --force > Compressing objects: 100% (677/677), done. > Writing objects: 100% (1058/1058), 148.85 KiB, done. > Total 1058 (delta 590), reused 602 (delta 378) - > To https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY.git + > To https://{% data variables.command_line.codeblock %}/YOUR-USERNAME.YOUR-REPOSITORY.git > + 48dc599...051452f main -> main (forced update) ``` -8. 要从[标记版本](/articles/about-releases)删除敏感文件,还需要针对 Git 标记强制推送: +8. In order to remove the sensitive file from [your tagged releases](/articles/about-releases), you'll also need to force-push against your Git tags: ```shell $ git push origin --force --tags > Counting objects: 321, done. @@ -149,19 +147,19 @@ $ git push --force > Compressing objects: 100% (166/166), done. > Writing objects: 100% (321/321), 331.74 KiB | 0 bytes/s, done. > Total 321 (delta 124), reused 269 (delta 108) - > To https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY.git + > To https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY.git > + 48dc599...051452f main -> main (forced update) ``` -## 完全从 {% data variables.product.prodname_dotcom %} 中删除数据 +## Fully removing the data from {% data variables.product.prodname_dotcom %} -在使用 BFG 工具或 `git filter-repo` 删除敏感数据并将更改推送到 {% data variables.product.product_name %} 后,你必须再采取一些步骤,以完全从 {% data variables.product.product_name %} 中删除数据。 +After using either the BFG tool or `git filter-repo` to remove the sensitive data and pushing your changes to {% data variables.product.product_name %}, you must take a few more steps to fully remove the data from {% data variables.product.product_name %}. -1. 联系 {% data variables.contact.contact_support %},请求他们删除 {% data variables.product.product_name %} 上拉取请求中敏感数据的缓存视图和引用。 请提供存储库的名称和/或指向需要删除的提交的链接。{% ifversion ghes %} 有关站点管理员如何删除无法访问的 Git 对象,请参阅“[命令行实用程序](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-repo-gc)”。{% endif %} +1. Contact {% data variables.contact.contact_support %}, asking them to remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %}. Please provide the name of the repository and/or a link to the commit you need removed.{% ifversion ghes %} For more information about how site administrators can remove unreachable Git objects, see "[Command line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-repo-gc)."{% endif %} -2. 告知协作者对根据旧式(受损)存储库历史记录创建的所有分支进行[变基](https://git-scm.com/book/en/Git-Branching-Rebasing),而不是合并。 一次合并提交可能会重新引入您刚刚遇到清除问题的部分或全部污染的历史记录。 +2. Tell your collaborators to [rebase](https://git-scm.com/book/en/Git-Branching-Rebasing), *not* merge, any branches they created off of your old (tainted) repository history. One merge commit could reintroduce some or all of the tainted history that you just went to the trouble of purging. -3. 经过一段时间并且确信 BFG 工具 / `git filter-repo` 没有任何意外的副作用后,你可以通过以下命令(使用 Git 1.8.5 或更新版本)强制取消引用本地存储库中的所有对象并进行垃圾回收: +3. After some time has passed and you're confident that the BFG tool / `git filter-repo` had no unintended side effects, you can force all objects in your local repository to be dereferenced and garbage collected with the following commands (using Git 1.8.5 or newer): ```shell $ git for-each-ref --format="delete %(refname)" refs/original | git update-ref --stdin $ git reflog expire --expire=now --all @@ -174,21 +172,21 @@ $ git push --force ``` {% note %} - **注意:** 你也可以通过以下方法实现此目的:将筛选的历史记录推送到新的或空的存储库,然后从 {% data variables.product.product_name %} 进行全新克隆。 + **Note:** You can also achieve this by pushing your filtered history to a new or empty repository and then making a fresh clone from {% data variables.product.product_name %}. {% endnote %} -## 避免将来的意外提交 +## Avoiding accidental commits in the future -有一些简单的技巧可避免提交您不想要提交的内容: +There are a few simple tricks to avoid committing things you don't want committed: -- 使用 [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) 或 [gitk](https://git-scm.com/docs/gitk) 等可视化程序提交更改。 可视程序通常可以更容易地查看每次提交时将添加、删除和修改具体哪些文件。 -- 避免在命令行中使用笼统的命令 `git add .` 和 `git commit -a`,而是使用 `git add filename` 和 `git rm filename` 来单独暂存文件。 -- 使用 `git add --interactive` 单独查看和暂存每个文件中的更改。 -- 使用 `git diff --cached` 查看为提交暂存的更改。 如果不使用 `-a` 标志,这就是 `git commit` 将产生的确切差异。 +- Use a visual program like [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) or [gitk](https://git-scm.com/docs/gitk) to commit changes. Visual programs generally make it easier to see exactly which files will be added, deleted, and modified with each commit. +- Avoid the catch-all commands `git add .` and `git commit -a` on the command line—use `git add filename` and `git rm filename` to individually stage files, instead. +- Use `git add --interactive` to individually review and stage changes within each file. +- Use `git diff --cached` to review the changes that you have staged for commit. This is the exact diff that `git commit` will produce as long as you don't use the `-a` flag. -## 延伸阅读 +## Further reading -- [`git filter-repo` 手册页](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html) -- [Pro Git:Git 工具 - 重写历史记录](https://git-scm.com/book/en/Git-Tools-Rewriting-History) -- [关于机密扫描](/code-security/secret-security/about-secret-scanning) +- [`git filter-repo` man page](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html) +- [Pro Git: Git Tools - Rewriting History](https://git-scm.com/book/en/Git-Tools-Rewriting-History) +- "[About Secret scanning](/code-security/secret-security/about-secret-scanning)" diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md index a0f830267b..dfbb52b360 100644 --- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md +++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md @@ -144,8 +144,8 @@ An overview of some of the most common actions that are recorded as events in th | Action | Description |------------------|------------------- -| `create` | Triggered when you [add a new public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/adding-a-new-ssh-key-to-your-github-account). -| `delete` | Triggered when you [remove a public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}](/articles/reviewing-your-ssh-keys). +| `create` | Triggered when you [add a new public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}](/articles/adding-a-new-ssh-key-to-your-github-account). +| `delete` | Triggered when you [remove a public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}](/articles/reviewing-your-ssh-keys). ### `repo` category actions @@ -242,7 +242,7 @@ An overview of some of the most common actions that are recorded as events in th | `change_password` | Triggered when you change your password. | `forgot_password` | Triggered when you ask for [a password reset](/articles/how-can-i-reset-my-password).{% endif %} | `hide_private_contributions_count` | Triggered when you [hide private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile). -| `login` | Triggered when you log in to {% data variables.product.product_location %}.{% ifversion ghes or ghae %} +| `login` | Triggered when you log in to {% data variables.location.product_location %}.{% ifversion ghes or ghae %} `mandatory_message_viewed` | Triggered when you view a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %} | `failed_login` | Triggered when you failed to log in successfully. | `remove_email` | Triggered when you remove an email address. diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md index 842da80c02..65491b5760 100644 --- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md +++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md @@ -1,6 +1,6 @@ --- -title: 审查 SSH 密钥 -intro: '为了保证您的凭据安全,您应该定期检查您的 SSH 密钥、部署密钥 并审核已授权的应用程序,以访问您在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的帐户。' +title: Reviewing your SSH keys +intro: 'To keep your credentials secure, you should regularly audit your SSH keys, deploy keys, and review authorized applications that access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}.' redirect_from: - /articles/keeping-your-application-access-tokens-safe - /articles/keeping-your-ssh-keys-and-application-access-tokens-safe @@ -15,97 +15,94 @@ versions: topics: - Identity - Access management -ms.openlocfilehash: 4f15ea8fd56994de4d9b30c21e6afb081e20a327 -ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147875994' --- -您可以删除未经授权(或可能已泄密)的 SSH 密钥,以确保攻击者无法再访问您的仓库。 您还可以批准有效的现有 SSH 密钥。 +You can delete unauthorized (or possibly compromised) SSH keys to ensure that an attacker no longer has access to your repositories. You can also approve existing SSH keys that are valid. {% mac %} -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.ssh %} -3. 在 SSH Settings(SSH 设置)页面中,记下与您的帐户关联的 SSH 密钥。 对于无法识别或已过期的密钥,单击“删除”。 如果有要保留的有效 SSH 密钥,单击“审批”。 - ![SSH 密钥列表](/assets/images/help/settings/settings-ssh-key-review.png) +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.ssh %} +3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**. + ![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png) {% tip %} - 注意:如果由于 Git 操作失败而审核 SSH 密钥,则导致 [SSH 密钥审核错误](/articles/error-we-re-doing-an-ssh-key-audit)的未经验证的密钥将在 SSH 密钥列表中突出显示。 + **Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys. {% endtip %} -4. 打开终端。 +4. Open Terminal. {% data reusables.command_line.start_ssh_agent %} -6. 找到并记录公钥指纹。 +6. Find and take a note of your public key fingerprint. ```shell $ ssh-add -l -E sha256 - > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) + > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) ``` -7. {% data variables.product.product_name %} 上的 SSH 密钥应匹配计算机上的相同密钥。 +7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer. {% endmac %} {% windows %} -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.ssh %} -3. 在 SSH Settings(SSH 设置)页面中,记下与您的帐户关联的 SSH 密钥。 对于无法识别或已过期的密钥,单击“删除”。 如果有要保留的有效 SSH 密钥,单击“审批”。 - ![SSH 密钥列表](/assets/images/help/settings/settings-ssh-key-review.png) +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.ssh %} +3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**. + ![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png) {% tip %} - 注意:如果由于 Git 操作失败而审核 SSH 密钥,则导致 [SSH 密钥审核错误](/articles/error-we-re-doing-an-ssh-key-audit)的未经验证的密钥将在 SSH 密钥列表中突出显示。 + **Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys. {% endtip %} -4. 打开 Git Bash。 +4. Open Git Bash. 5. {% data reusables.desktop.windows_git_bash_turn_on_ssh_agent %} {% data reusables.desktop.windows_git_for_windows_turn_on_ssh_agent %} -6. 找到并记录公钥指纹。 +6. Find and take a note of your public key fingerprint. ```shell $ ssh-add -l -E sha256 - > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) + > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) ``` -7. {% data variables.product.product_name %} 上的 SSH 密钥应匹配计算机上的相同密钥。 +7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer. {% endwindows %} {% linux %} -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.ssh %} -3. 在 SSH Settings(SSH 设置)页面中,记下与您的帐户关联的 SSH 密钥。 对于无法识别或已过期的密钥,单击“删除”。 如果有要保留的有效 SSH 密钥,单击“审批”。 - ![SSH 密钥列表](/assets/images/help/settings/settings-ssh-key-review.png) +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.ssh %} +3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**. + ![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png) {% tip %} - 注意:如果由于 Git 操作失败而审核 SSH 密钥,则导致 [SSH 密钥审核错误](/articles/error-we-re-doing-an-ssh-key-audit)的未经验证的密钥将在 SSH 密钥列表中突出显示。 + **Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys. {% endtip %} -4. 打开终端。 +4. Open Terminal. {% data reusables.command_line.start_ssh_agent %} -6. 找到并记录公钥指纹。 +6. Find and take a note of your public key fingerprint. ```shell $ ssh-add -l -E sha256 - > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) + > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA) ``` -7. {% data variables.product.product_name %} 上的 SSH 密钥应匹配计算机上的相同密钥。 +7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer. {% endlinux %} {% warning %} -警告:如果在 {% data variables.product.product_name %} 上看到不熟悉的 SSH 密钥,请立即删除并联系 {% data variables.contact.contact_support %} 寻求进一步的帮助。 无法识别的公钥可能表示安全问题。 +**Warning**: If you see an SSH key you're not familiar with on {% data variables.product.product_name %}, delete it immediately and contact {% data variables.contact.contact_support %} for further help. An unidentified public key may indicate a possible security concern. {% endwarning %} diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md index 85ab06e26d..25cebe2a85 100644 --- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md +++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md @@ -1,6 +1,6 @@ --- -title: Sudo 模式 -intro: '为了在你执行可能敏感的操作之前确认你帐户的访问权限,{% data variables.product.product_location %} 会提示进行身份验证。' +title: Sudo mode +intro: 'To confirm access to your account before you perform a potentially sensitive action, {% data variables.location.product_location %} prompts for authentication.' redirect_from: - /articles/sudo-mode - /github/authenticating-to-github/sudo-mode @@ -13,83 +13,81 @@ miniTocMaxHeadingLevel: 3 topics: - Identity - Access management -ms.openlocfilehash: 909552ff2252e14430050541da5f6bae582f66b3 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147540824' --- -## 关于 sudo 模式 -为了在你对 {% data variables.product.product_location %} 执行可能敏感的操作时维护帐户的安全,即使你已登录,也必须进行身份验证。 例如,{% data variables.product.company_short %} 认为以下操作是敏感操作,因为每个操作都可能允许新用户或系统访问你的帐户。 +## About sudo mode -- 修改关联的电子邮件地址 -- 授权第三方应用程序 -- 添加新的 SSH 密钥 +To maintain the security of your account when you perform a potentially sensitive action on {% data variables.location.product_location %}, you must authenticate even though you're already signed in. For example, {% data variables.product.company_short %} considers the following actions sensitive because each action could allow a new person or system to access your account. -当你经过身份验证来执行敏感操作后,会话暂时处于“sudo 模式”。 在 sudo 模式下,无需身份验证即可执行敏感操作。 {% data variables.product.product_name %} 将等待几小时,然后再次提示你进行身份验证。 在此期间,你执行的任何敏感操作都将重置计时器。 +- Modification of an associated email address +- Authorization of a third-party application +- Addition of a new SSH key + +After you authenticate to perform a sensitive action, your session is temporarily in "sudo mode." In sudo mode, you can perform sensitive actions without authentication. {% data variables.product.product_name %} will wait a few hours before prompting you for authentication again. During this time, any sensitive action that you perform will reset the timer. {% ifversion ghes %} {% note %} -注意:如果 {% data variables.product.product_location %} 使用 CAS 或 SAML SSO 等外部身份验证方法,你不会收到进入 sudo 模式的提示。 更多信息请联系站点管理员。 +**Note**: If {% data variables.location.product_location %} uses an external authentication method like CAS or SAML SSO, you will not receive prompts to enter sudo mode. For more information, contact your site administrator. {% endnote %} {% endif %} -“sudo”是指 Unix 系统上的一个程序,该名称是“superuser do”的缩写 。 有关详细信息,请参阅维基百科上的 [sudo](https://wikipedia.org/wiki/Sudo)。 +"sudo" is a reference to a program on Unix systems, where the name is short for "**su**peruser **do**." For more information, see [sudo](https://wikipedia.org/wiki/Sudo) on Wikipedia. -## 确认对 sudo 模式的访问权限 +## Confirming access for sudo mode -要确认对 sudo 模式的访问权限,{% ifversion totp-and-mobile-sudo-challenge %}可以{% else %}必须{% endif %}使用密码进行身份验证。{% ifversion totp-and-mobile-sudo-challenge %}或者可选择使用其他身份验证方法,例如{% ifversion fpt or ghec %}安全密钥、{% data variables.product.prodname_mobile %} 或 2FA 代码{% elsif ghes %}安全密钥或 2FA 代码{% endif %}。{% endif %} +To confirm access for sudo mode, you {% ifversion totp-and-mobile-sudo-challenge %}can{% else %}must{% endif %} authenticate with your password.{% ifversion totp-and-mobile-sudo-challenge %} Optionally, you can use a different authentication method, like {% ifversion fpt or ghec %}a security key, {% data variables.product.prodname_mobile %}, or a 2FA code{% elsif ghes %}a security key or a 2FA code{% endif %}.{% endif %} {%- ifversion totp-and-mobile-sudo-challenge %} -- [使用安全密钥确认访问权限](#confirming-access-using-a-security-key) {%- ifversion fpt or ghec %} -- [使用 GitHub Mobile 确认访问权限](#confirming-access-using-github-mobile) {%- endif %} -- [使用 2FA 代码确认访问权限](#confirming-access-using-a-2fa-code) -- [使用密码确认访问权限](#confirming-access-using-your-password) {%- endif %} +- [Confirming access using a security key](#confirming-access-using-a-security-key) +{%- ifversion fpt or ghec %} +- [Confirming access using GitHub Mobile](#confirming-access-using-github-mobile) +{%- endif %} +- [Confirming access using a 2FA code](#confirming-access-using-a-2fa-code) +- [Confirming access using your password](#confirming-access-using-your-password) +{%- endif %} {% ifversion totp-and-mobile-sudo-challenge %} -### 使用安全密钥确认访问权限 +### Confirming access using a security key -必须使用安全密钥为帐户配置双因素身份验证 (2FA),才能使用安全密钥确认帐户是否拥有对 sudo 模式的访问权限。 有关详细信息,请参阅“[配置双因素身份验证](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)”。 +You must configure two-factor authentication (2FA) for your account using a security key to confirm access to your account for sudo mode using the security key. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)." -当系统提示对 sudo 模式进行身份验证时,请单击“使用安全密钥”,然后按照提示进行操作。 +When prompted to authenticate for sudo mode, click **Use security key**, then follow the prompts. -![sudo 模式的安全密钥选项的屏幕截图](/assets/images/help/settings/sudo_mode_prompt_security_key.png) +![Screenshot of security key option for sudo mode](/assets/images/help/settings/sudo_mode_prompt_security_key.png) {% ifversion fpt or ghec %} -### 使用 {% data variables.product.prodname_mobile %} 确认访问权限 +### Confirming access using {% data variables.product.prodname_mobile %} -必须安装并登录 {% data variables.product.prodname_mobile %},才能使用该应用确认帐户是否拥有对 sudo 模式的访问权限。 有关详细信息,请参阅“[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)”。 +You must install and sign into {% data variables.product.prodname_mobile %} to confirm access to your account for sudo mode using the app. For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)." -1. 当系统提示对 sudo 模式进行身份验证时,请单击“使用 GitHub Mobile”。 +1. When prompted to authenticate for sudo mode, click **Use GitHub Mobile**. - ![sudo 模式的 {% data variables.product.prodname_mobile %} 选项的屏幕截图](/assets/images/help/settings/sudo_mode_prompt_github_mobile_prompt.png) -1. 打开 {% data variables.product.prodname_mobile %}。 {% data variables.product.prodname_mobile %} 将显示必须在 {% data variables.product.product_location %} 上输入才能批准请求的数字。 + ![Screenshot of {% data variables.product.prodname_mobile %} option for sudo mode](/assets/images/help/settings/sudo_mode_prompt_github_mobile_prompt.png) +1. Open {% data variables.product.prodname_mobile %}. {% data variables.product.prodname_mobile %} will display numbers that you must enter on {% data variables.location.product_location %} to approve the request. - ![{% data variables.product.prodname_mobile %} 中数字的屏幕截图,该数字用于在 {% data variables.product.product_name %} 上输入来审核 sudo 模式访问权限](/assets/images/help/settings/sudo_mode_prompt_github_mobile.png) -1. 在 {% data variables.product.product_name %} 上,键入 {% data variables.product.prodname_mobile %} 中显示的数字。 + ![Screenshot of numbers from {% data variables.product.prodname_mobile %} to enter on {% data variables.product.product_name %} to approve sudo mode access](/assets/images/help/settings/sudo_mode_prompt_github_mobile.png) +1. On {% data variables.product.product_name %}, type the numbers displayed in {% data variables.product.prodname_mobile %}. {% endif %} -### 使用 2FA 代码确认访问权限 +### Confirming access using a 2FA code -必须使用 TOTP 移动应用{% ifversion fpt or ghec %}或短信{% endif %}配置 2FA,才能使用 2FA 代码确认帐户是否拥有对 sudo 模式的访问权限。 有关详细信息,请参阅“[配置双因素身份验证](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)”。 +You must configure 2FA using a TOTP mobile app{% ifversion fpt or ghec %} or text messages{% endif %} to confirm access to your account for sudo mode using a 2FA code. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)." -当系统提示对 sudo 模式进行身份验证时,请键入 TOTP 移动应用{% ifversion fpt or ghec %}或短信{% endif %}中的验证码,然后单击“验证”。 +When prompted to authenticate for sudo mode, type the authentication code from your TOTP mobile app{% ifversion fpt or ghec %} or the text message{% endif %}, then click **Verify**. -![sudo 模式的 2FA 代码提示的屏幕截图](/assets/images/help/settings/sudo_mode_prompt_2fa_code.png) +![Screenshot of 2FA code prompt for sudo mode](/assets/images/help/settings/sudo_mode_prompt_2fa_code.png) -### 使用密码确认访问权限 +### Confirming access using your password {% endif %} -当系统提示对 sudo 模式进行身份验证时,请键入密码,然后单击“确认”。 +When prompted to authenticate for sudo mode, type your password, then click **Confirm**. -![sudo 模式的密码提示的屏幕截图](/assets/images/help/settings/sudo_mode_prompt_password.png) +![Screenshot of password prompt for sudo mode](/assets/images/help/settings/sudo_mode_prompt_password.png) diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md index 9568b5c1b3..7dae72fd34 100644 --- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md +++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md @@ -1,6 +1,6 @@ --- -title: 令牌过期和吊销 -intro: '您的令牌可能会过期,也可以由您、您授权的应用程序以及 {% data variables.product.product_name %} 自行吊销。' +title: Token expiration and revocation +intro: 'Your tokens can expire and can also be revoked by you, applications you have authorized, and {% data variables.product.product_name %} itself.' versions: fpt: '*' ghes: '*' @@ -12,59 +12,55 @@ topics: shortTitle: Token expiration redirect_from: - /github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation -ms.openlocfilehash: aa1d8902fc120aa616b8a3355f1add21a482d99e -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145084634' --- -当令牌 {% ifversion fpt or ghae or ghes > 3.2 or ghec %}已过期或 {% endif %} 已撤销时,它不能再用于对 Git 和 API 请求进行身份验证。 无法还原过期或已吊销的令牌,您或应用程序将需要创建新令牌。 -本文介绍了 {% data variables.product.product_name %} 令牌可能被吊销或过期的可能原因。 +When a token {% ifversion fpt or ghae or ghes > 3.2 or ghec %}has expired or {% endif %} has been revoked, it can no longer be used to authenticate Git and API requests. It is not possible to restore an expired or revoked token, you or the application will need to create a new token. + +This article explains the possible reasons your {% data variables.product.product_name %} token might be revoked or expire. {% note %} -**注意:** 当个人访问令牌或 OAuth 令牌过期或撤销时,你可能会在安全日志中看到 `oauth_authorization.destroy` 操作。 有关详细信息,请参阅“[查看安全日志](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-security-log)”。 +**Note:** When a {% data variables.product.pat_generic %} or OAuth token expires or is revoked, you may see an `oauth_authorization.destroy` action in your security log. For more information, see "[Reviewing your security log](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-security-log)." {% endnote %} {% ifversion fpt or ghae or ghes > 3.2 or ghec %} -## 令牌在到达其到期日期后被吊销 +## Token revoked after reaching its expiration date -创建个人访问令牌时,建议为令牌设置过期时间。 到达令牌的到期日期后,令牌将自动吊销。 有关详细信息,请参阅“[创建个人访问令牌](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)”。 +When you create a {% data variables.product.pat_generic %}, we recommend that you set an expiration for your token. Upon reaching your token's expiration date, the token is automatically revoked. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." {% endif %} {% ifversion fpt or ghec %} -## 令牌在推送到公共存储库或公共 Gist 时被吊销 +## Token revoked when pushed to a public repository or public gist -如果将有效的 OAuth 令牌、{% data variables.product.prodname_github_app %} 令牌或个人访问令牌推送到公共存储库或公共 gist,则该令牌将自动吊销。 +If a valid OAuth token, {% data variables.product.prodname_github_app %} token, or {% data variables.product.pat_generic %} is pushed to a public repository or public gist, the token will be automatically revoked. + +OAuth tokens and personal {% data variables.product.pat_v1_plural %} pushed to public repositories and public gists will only be revoked if the token has scopes.{% ifversion pat-v2 %} {% data variables.product.pat_v2_caps %}s will always be revoked.{% endif %} -推送到公共存储库和公共 gist 的 OAuth 令牌和个人访问令牌只有在令牌具有作用域时才会被吊销。 {% endif %} {% ifversion fpt or ghec %} -## 令牌因未使用而过期 +## Token expired due to lack of use -当 OAuth 令牌或个人访问令牌一年内未使用时,{% data variables.product.product_name %} 会自动将其吊销。 +{% data variables.product.product_name %} will automatically revoke an OAuth token or {% data variables.product.pat_generic %} when the token hasn't been used in one year. {% endif %} -## 用户吊销令牌 +## Token revoked by the user -您可以从帐户设置中撤销对 {% data variables.product.prodname_github_app %} 或 {% data variables.product.prodname_oauth_app %} 的授权,这将吊销与应用程序关联的任何令牌。 有关详细信息,请参阅“[查看授权集成](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)”和“[查看授权的应用程序 (OAuth)](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth)”。 +You can revoke your authorization of a {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %} from your account settings which will revoke any tokens associated with the app. For more information, see "[Reviewing your authorized integrations](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)" and "[Reviewing your authorized applications (OAuth)](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth)." -撤销授权后,与授权关联的任何令牌也将被吊销。 要重新授权应用程序,请按照第三方应用程序或网站上的说明再次连接您在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的帐户。 +Once an authorization is revoked, any tokens associated with the authorization will be revoked as well. To re-authorize an application, follow the instructions from the third-party application or website to connect your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} again. -## {% data variables.product.prodname_oauth_app %} 吊销令牌 +## Token revoked by the {% data variables.product.prodname_oauth_app %} -{% data variables.product.prodname_oauth_app %} 的所有者可以撤销帐户对其应用程序的授权,这也会吊销与授权关联的任何令牌。 有关撤销 OAuth 应用的授权的详细信息,请参阅“[删除应用授权](/rest/reference/apps#delete-an-app-authorization)”。 +The owner of an {% data variables.product.prodname_oauth_app %} can revoke an account's authorization of their app, this will also revoke any tokens associated with the authorization. For more information about revoking authorizations of your OAuth app, see "[Delete an app authorization](/rest/reference/apps#delete-an-app-authorization)." -{% data variables.product.prodname_oauth_app %} 所有者还可以撤销与授权关联的单个令牌。 有关撤消 OAuth 应用的单个令牌的详细信息,请参阅“[删除应用令牌](/rest/apps/oauth-applications#delete-an-app-token)”。 +{% data variables.product.prodname_oauth_app %} owners can also revoke individual tokens associated with an authorization. For more information about revoking individual tokens for your OAuth app, see "[Delete an app token](/rest/apps/oauth-applications#delete-an-app-token)". -## 令牌由于具有相同作用域的 {% data variables.product.prodname_oauth_app %} 的令牌过多而被吊销 +## Token revoked due to excess of tokens for an {% data variables.product.prodname_oauth_app %} with the same scope {% data reusables.apps.oauth-token-limit %} -## 用户令牌因配置 {% data variables.product.prodname_github_app %} 而被吊销 +## User token revoked due to {% data variables.product.prodname_github_app %} configuration -默认情况下,由 {% data variables.product.prodname_github_app %} 创建的用户到服务器令牌将在八小时后过期。 {% data variables.product.prodname_github_apps %} 的所有者可以配置其应用,以便用户到服务器的令牌不会过期。 有关更改 {% data variables.product.prodname_dotcom %} 应用的用户到服务器令牌的行为方式的详细信息,请参阅“[激活应用的可选功能](/developers/apps/getting-started-with-apps/activating-optional-features-for-apps)”。 +User-to-server tokens created by a {% data variables.product.prodname_github_app %} will expire after eight hours by default. Owners of {% data variables.product.prodname_github_apps %} can configure their apps so that user-to-server tokens do not expire. For more information about changing how your {% data variables.product.prodname_dotcom %} App's user-to-server tokens behave, see "[Activating optional features for apps](/developers/apps/getting-started-with-apps/activating-optional-features-for-apps)." diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md index 4ec20da07e..12e35114b2 100644 --- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md +++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md @@ -1,6 +1,6 @@ --- -title: 更新 GitHub 访问凭据 -intro: '{% data variables.product.product_name %} 凭据{% ifversion not ghae %}不仅包括密码,还包括{% endif %}你用于与 {% data variables.product.product_name %} 通信的访问令牌、SSH 密钥和应用程序 API 令牌。 如果您有需要,可以自行重置所有这些访问凭据。' +title: Updating your GitHub access credentials +intro: '{% data variables.product.product_name %} credentials include{% ifversion not ghae %} not only your password, but also{% endif %} the access tokens, SSH keys, and application API tokens you use to communicate with {% data variables.product.product_name %}. Should you have the need, you can reset all of these access credentials yourself.' redirect_from: - /articles/rolling-your-credentials - /articles/how-can-i-reset-my-password @@ -16,74 +16,73 @@ topics: - Identity - Access management shortTitle: Update access credentials -ms.openlocfilehash: 650c0027b679690def6d1c77d727a87b8688b889 -ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/12/2022 -ms.locfileid: '147508414' --- {% ifversion not ghae %} -## 请求新密码 +## Requesting a new password -1. 要请求新密码,请访问 {% ifversion fpt or ghec %} https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}。 -2. 在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上输入与你的个人帐户关联的电子邮件地址,然后单击“发送密码重置电子邮件”。 如果已配置,该电子邮件将发送到备用电子邮件地址。 - ![密码重置电子邮件请求对话框](/assets/images/help/settings/password-recovery-email-request.png) -3. 我们将向您发送一封电子邮件,其中含有可让您重置密码的链接。 您必须在收到电子邮件后的 3 小时内单击此链接。 如果您没有收到来自我们的电子邮件,请确保检查垃圾邮件文件夹。 -4. 如果你启用了双因素身份验证,系统将提示你输入 2FA 凭据:{% ifversion fpt or ghec %} - * 如果有 {% data variables.product.prodname_mobile %},则会向你发送推送通知来验证身份。 打开推送通知或 {% data variables.product.prodname_mobile %} 应用,并在浏览器中的密码重置页上输入显示的两位数代码。 - ![双因素 {% data variables.product.prodname_mobile %} 身份验证提示](/assets/images/help/2fa/2fa-mobile-challenge-password-reset.png) - * 若要跳过使用 GitHub Mobile 进行验证,请单击“输入双因素身份验证或恢复代码”。 - ![{% data variables.product.product_name %} 上的双因素 GitHub Mobile 身份验证提示,其中突出显示“输入双因素身份验证或恢复代码”](/assets/images/help/2fa/2fa-github-mobile-password-reset.png){% endif %} - * 键入身份验证代码或恢复代码之一,然后单击“验证”。 - ![双重身份验证提示](/assets/images/help/2fa/2fa-password-reset.png) - * 如果已向帐户添加了安全密钥,请单击“使用安全密钥”,而无需键入身份验证码。 +1. To request a new password, visit {% ifversion fpt or ghec %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}. +2. Enter the email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then click **Send password reset email.** The email will be sent to the backup email address if you have one configured. + ![Password reset email request dialog](/assets/images/help/settings/password-recovery-email-request.png) +3. We'll email you a link that will allow you to reset your password. You must click on this link within 3 hours of receiving the email. If you didn't receive an email from us, make sure to check your spam folder. +4. If you have enabled two-factor authentication, you will be prompted for your 2FA credentials: +{% ifversion fpt or ghec %} + * If you have {% data variables.product.prodname_mobile %}, you will be sent a push notification to verify your identity. Open the push notification or the {% data variables.product.prodname_mobile %} app and enter the two-digit code shown to you on the password reset page in your browser. + ![Two-factor {% data variables.product.prodname_mobile %} authentication prompt](/assets/images/help/2fa/2fa-mobile-challenge-password-reset.png) + * To skip using GitHub Mobile to verify, click **Enter two-factor authentication or recovery code**. + ![Two-factor GitHub Mobile authentication prompt on {% data variables.product.product_name %} with "Enter two-factor authentication or recovery code" highlighted](/assets/images/help/2fa/2fa-github-mobile-password-reset.png) +{% endif %} + * Type your authentication code or one of your recovery codes and click **Verify**. + ![Two-factor authentication prompt](/assets/images/help/2fa/2fa-password-reset.png) + * If you have added a security key to your account, click **Use security key** instead of typing an authentication code. {% ifversion fpt or ghec %} - * 如果已设置 [{% data variables.product.prodname_mobile %}](https://github.com/mobile),请改为单击“使用 GitHub Mobile 进行身份验证”。 + * If you have set up [{% data variables.product.prodname_mobile %}](https://github.com/mobile), click **Authenticate with GitHub Mobile** instead. {% endif %} -5. 键入新密码,确认新密码,然后单击“更改密码”。 要获取有关创建强密码的帮助,请参阅“[创建强密码](/articles/creating-a-strong-password)”。 - {% ifversion fpt or ghec %}![密码恢复框](/assets/images/help/settings/password-recovery-page.png){% else %} ![密码恢复框](/assets/images/enterprise/settings/password-recovery-page.png){% endif %} +5. Type a new password, confirm your new password, and click **Change password**. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)." + {% ifversion fpt or ghec %}![Password recovery box](/assets/images/help/settings/password-recovery-page.png){% else %} + ![Password recovery box](/assets/images/enterprise/settings/password-recovery-page.png){% endif %} {% tip %} -为避免将来丢失密码,建议使用安全的密码管理器,例如 [LastPass](https://lastpass.com/) 或 [1Password](https://1password.com/)。 +To avoid losing your password in the future, we suggest using a secure password manager, like [LastPass](https://lastpass.com/) or [1Password](https://1password.com/). {% endtip %} -## 更改现有的密码 +## Changing an existing password {% data reusables.repositories.blocked-passwords %} -1. {% data variables.product.signin_link %}到 {% data variables.product.product_name %}。 -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security %} -4. 在“Change password(更改密码)”下,输入旧密码、强新密码并确认新密码。 要获取有关创建强密码的帮助,请参阅“[创建强密码](/articles/creating-a-strong-password)” -5. 单击“更新密码”。 +1. {% data variables.product.signin_link %} to {% data variables.product.product_name %}. +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.security %} +4. Under "Change password", type your old password, a strong new password, and confirm your new password. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)" +5. Click **Update password**. {% tip %} -为实现更高的安全性,除了更改密码以外,还可启用双重身份验证。 有关详细信息,请参阅[关于双重身份验证](/articles/about-two-factor-authentication)。 +For greater security, enable two-factor authentication in addition to changing your password. See [About two-factor authentication](/articles/about-two-factor-authentication) for more details. -{% endtip %} {% endif %} -## 更新访问令牌 +{% endtip %} +{% endif %} +## Updating your access tokens -有关审查和删除访问令牌的说明,请参阅“[审查授权的集成](/articles/reviewing-your-authorized-integrations)”。 要生成新的访问令牌,请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 +See "[Reviewing your authorized integrations](/articles/reviewing-your-authorized-integrations)" for instructions on reviewing and deleting access tokens. To generate new access tokens, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." {% ifversion not ghae %} -如果你已重置帐户密码,并且还希望触发从 {% data variables.product.prodname_mobile %} 应用退出登录,则可以撤销对“GitHub iOS”或“GitHub Android”OAuth 应用的授权。 这将使与你帐户关联的 {% data variables.product.prodname_mobile %} 应用的所有实例退出登录。 有关其他信息,请参阅“[审查授权的集成](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)”。 +If you have reset your account password and would also like to trigger a sign-out from the {% data variables.product.prodname_mobile %} app, you can revoke your authorization of the "GitHub iOS" or "GitHub Android" OAuth App. This will sign out all instances of the {% data variables.product.prodname_mobile %} app associated with your account. For additional information, see "[Reviewing your authorized integrations](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)." {% endif %} -## 更新 SSH 密钥 +## Updating your SSH keys -有关审查和删除 SSH 密钥的说明,请参阅“[审查 SSH 密钥](/articles/reviewing-your-ssh-keys)”。 要生成和添加新的 SSH 密钥,请参阅“[生成 SSH 密钥](/articles/generating-an-ssh-key)”。 +See "[Reviewing your SSH keys](/articles/reviewing-your-ssh-keys)" for instructions on reviewing and deleting SSH keys. To generate and add new SSH keys, see "[Generating an SSH key](/articles/generating-an-ssh-key)." -## 重置 API 令牌 +## Resetting API tokens -如果您向 {% data variables.product.product_name %} 注册了任何应用程序,则需要重置其 OAuth 令牌。 有关详细信息,请参阅“[重置授权](/rest/reference/apps#reset-an-authorization)”终结点。 +If you have any applications registered with {% data variables.product.product_name %}, you'll want to reset their OAuth tokens. For more information, see the "[Reset an authorization](/rest/reference/apps#reset-an-authorization)" endpoint. {% ifversion not ghae %} -## 防止未授权的访问 +## Preventing unauthorized access -有关保护帐户和阻止未授权访问的更多提示,请参阅“[阻止未授权的访问](/articles/preventing-unauthorized-access)”。 +For more tips on securing your account and preventing unauthorized access, see "[Preventing unauthorized access](/articles/preventing-unauthorized-access)." {% endif %} diff --git a/translations/zh-CN/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md b/translations/zh-CN/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md index b2287d3a5e..4f526c28c2 100644 --- a/translations/zh-CN/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md +++ b/translations/zh-CN/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md @@ -73,7 +73,7 @@ You can optionally choose to have {% data variables.product.prodname_dotcom %} G You can use GPG to sign commits with a GPG key that you generate yourself. -{% data variables.product.product_name %} uses OpenPGP libraries to confirm that your locally signed commits and tags are cryptographically verifiable against a public key you have added to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. +{% data variables.product.product_name %} uses OpenPGP libraries to confirm that your locally signed commits and tags are cryptographically verifiable against a public key you have added to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. To sign commits using GPG and have those commits verified on {% data variables.product.product_name %}, follow these steps: @@ -90,7 +90,7 @@ To sign commits using GPG and have those commits verified on {% data variables.p You can use SSH to sign commits with an SSH public key that you generate yourself. If you already use an SSH key to authenticate with {% data variables.product.product_name %}, you can also upload that same key again for use as a signing key. There's no limit on the number of signing keys you can add to your account. -{% data variables.product.product_name %} uses [ssh_data](https://github.com/github/ssh_data), an open source Ruby library, to confirm that your locally signed commits and tags are cryptographically verifiable against a public key you have added to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. +{% data variables.product.product_name %} uses [ssh_data](https://github.com/github/ssh_data), an open source Ruby library, to confirm that your locally signed commits and tags are cryptographically verifiable against a public key you have added to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. {% data reusables.gpg.ssh-git-version %} diff --git a/translations/zh-CN/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md b/translations/zh-CN/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md index 3d66db7a17..febbc304fa 100644 --- a/translations/zh-CN/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md +++ b/translations/zh-CN/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md @@ -1,6 +1,6 @@ --- -title: 将 GPG 密钥添加到 GitHub 帐户 -intro: '要在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上配置帐户以使用新的(或现有的)GPG 密钥,还需要将密钥添加到帐户。' +title: Adding a GPG key to your GitHub account +intro: 'To configure your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} to use your new (or existing) GPG key, you''ll also need the key to your account.' redirect_from: - /articles/adding-a-gpg-key-to-your-github-account - /github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account @@ -19,55 +19,54 @@ topics: - Identity - Access management shortTitle: Add a GPG key -ms.openlocfilehash: db832d4e02ea5f19303b3178fb669967238e661b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147369336' --- -## 关于向帐户添加 GPG 密钥 -若要在 {% data variables.product.product_name %} 上对与你的帐户关联的提交进行签名,可以将公共 GPG 密钥添加到你的个人帐户。 在添加密钥之前,应检查现有密钥。 如果未找到任何现有密钥,可以生成并复制新的密钥。 有关详细信息,请参阅“[检查现有 GPG 密钥](/articles/checking-for-existing-gpg-keys)”和“[生成新的 GPG 密钥](/articles/generating-a-new-gpg-key)”。 +## About addition of GPG keys to your account -可以向你在 {% data variables.product.product_name %} 上的帐户添加多个公钥。 由任何相应的私钥签名的提交将显示为已验证。 如果删除公钥,则由相应私钥签名的任何提交将不再显示为已验证。 +To sign commits associated with your account on {% data variables.product.product_name %}, you can add a public GPG key to your personal account. Before you add a key, you should check for existing keys. If you don't find any existing keys, you can generate and copy a new key. For more information, see "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)" and "[Generating a new GPG key](/articles/generating-a-new-gpg-key)." -{% ifversion upload-expired-or-revoked-gpg-key %} 若要验证尽可能多的提交,可以添加已过期和已撤销的密钥。 如果密钥满足所有其他验证要求,则之前由任何相应私钥签名的提交将显示为已验证状态,并指出它们的签名密钥已过期或已撤销。 +You can add multiple public keys to your account on {% data variables.product.product_name %}. Commits signed by any of the corresponding private keys will show as verified. If you remove a public key, any commits signed by the corresponding private key will no longer show as verified. -![一个已验证的提交,它的密钥已过期](/assets/images/help/settings/gpg-verified-with-expired-key.png) {% endif %} +{% ifversion upload-expired-or-revoked-gpg-key %} +To verify as many of your commits as possible, you can add expired and revoked keys. If the key meets all other verification requirements, commits that were previously signed by any of the corresponding private keys will show as verified and indicate that their signing key is expired or revoked. + +![A verified commit whose key expired](/assets/images/help/settings/gpg-verified-with-expired-key.png) +{% endif %} {% data reusables.gpg.supported-gpg-key-algorithms %} -验证签名时,{% data variables.product.product_name %} 将提取签名,并尝试分析它的密钥 ID。 随后,将此密钥 ID 与添加到 {% data variables.product.product_name %} 的密钥进行匹配。 在匹配的 GPG 密钥被添加到 {% data variables.product.product_name %} 之前,它将无法验证你的签名。 +When verifying a signature, {% data variables.product.product_name %} extracts the signature and attempts to parse its key ID. The key ID is then matched with keys added to {% data variables.product.product_name %}. Until a matching GPG key is added to {% data variables.product.product_name %}, it cannot verify your signatures. -## 添加 GPG 密钥 +## Adding a GPG key -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.ssh %} -3. 单击“新建 GPG 密钥”。 - ![“GPG 密钥”按钮](/assets/images/help/settings/gpg-add-gpg-key.png) -4. 在“密钥”字段中,粘贴[生成 GPG 密钥](/articles/generating-a-new-gpg-key)时复制的 GPG 密钥。 - ![密钥字段](/assets/images/help/settings/gpg-key-paste.png) -5. 单击“添加 GPG 密钥” - ![“添加密钥”按钮](/assets/images/help/settings/gpg-add-key.png) -6. 要确认操作,请输入您的 {% data variables.product.product_name %} 密码。 +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.ssh %} +3. Click **New GPG key**. + ![GPG Key button](/assets/images/help/settings/gpg-add-gpg-key.png) +4. In the "Key" field, paste the GPG key you copied when you [generated your GPG key](/articles/generating-a-new-gpg-key). + ![The key field](/assets/images/help/settings/gpg-key-paste.png) +5. Click **Add GPG key**. + ![The Add key button](/assets/images/help/settings/gpg-add-key.png) +6. To confirm the action, enter your {% data variables.product.product_name %} password. -{% ifversion upload-expired-or-revoked-gpg-key %} {% else %} -## 更新过期的 GPG 密钥 +{% ifversion upload-expired-or-revoked-gpg-key %} +{% else %} +## Updating an expired GPG key -验证签名时,{% data variables.product.product_name %} 会检查密钥是否已撤销或过期。 如果您的签名密钥已撤销或过期,则 {% data variables.product.product_name %} 无法验证您的签名。 +When verifying a signature, {% data variables.product.product_name %} checks that the key is not revoked or expired. If your signing key is revoked or expired, {% data variables.product.product_name %} cannot verify your signatures. -如果你的密钥已过期,必须[更新它的过期时间](https://www.gnupg.org/gph/en/manual.html#AEN329)、导出新密钥、删除 {% data variables.product.product_name %} 上帐户中的过期密钥,然后按上述步骤向帐户添加新的密钥。 只要密钥满足所有其他验证要求,您以前的提交和标记就会显示为已验证。 +If your key is expired, you must [update its expiration](https://www.gnupg.org/gph/en/manual.html#AEN329), export the new key, delete the expired key in your account on {% data variables.product.product_name %}, and add the new key to your account as described above. Your previous commits and tags will show as verified, as long as the key meets all other verification requirements. -如果您的密钥已撤销,请使用主密钥或未撤销的其他密钥为提交签名。 +If your key is revoked, use the primary key or another key that is not revoked to sign your commits. -如果您的密钥无效且您没有在密钥集中使用其他有效的密钥,而是使用一组新凭据生成新的 GPG 密钥,则使用已撤销或过期的密钥进行的提交将仍显示为未验证。 此外,你的新凭据将无法对你的旧提交和标记进行重新签名或验证。 +If your key is invalid and you don't use another valid key in your key set, but instead generate a new GPG key with a new set of credentials, then your commits made with the revoked or expired key will continue to show as unverified. Also, your new credentials will not be able to re-sign or verify your old commits and tags. {% endif %} -## 延伸阅读 +## Further reading -- [检查现有 GPG 密钥](/articles/checking-for-existing-gpg-keys) -- [生成新 GPG 密钥](/articles/generating-a-new-gpg-key) -- [将签名密钥告知 Git](/articles/telling-git-about-your-signing-key) -- [将电子邮件与 GPG 密钥关联](/articles/associating-an-email-with-your-gpg-key) -- [使用 GPG 密钥对提交和标记进行签名](/articles/signing-commits-and-tags-using-gpg) -- [关于提交签名验证](/articles/about-commit-signature-verification) +- "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)" +- "[Generating a new GPG key](/articles/generating-a-new-gpg-key)" +- "[Telling Git about your signing key](/articles/telling-git-about-your-signing-key)" +- "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)" +- "[Signing commits and tags using GPG keys](/articles/signing-commits-and-tags-using-gpg)" +- "[About commit signature verification](/articles/about-commit-signature-verification)" diff --git a/translations/zh-CN/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md b/translations/zh-CN/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md index 9612ec6ec3..3c92549eb7 100644 --- a/translations/zh-CN/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md +++ b/translations/zh-CN/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md @@ -1,6 +1,6 @@ --- -title: 将电子邮件与 GPG 密钥关联 -intro: 'GPG 密钥必须 {% data variables.product.product_name %} 验证过与提交者身份匹配的电子邮件地址匹配。' +title: Associating an email with your GPG key +intro: 'Your GPG key must be associated with a {% data variables.product.product_name %} verified email that matches your committer identity.' redirect_from: - /articles/associating-an-email-with-your-gpg-key - /github/authenticating-to-github/associating-an-email-with-your-gpg-key @@ -14,53 +14,49 @@ topics: - Identity - Access management shortTitle: Associate email with GPG key -ms.openlocfilehash: d36c053e1df0c329fb8d4607b1338c49414e76de -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147369279' --- {% note %} -如果您使用与您的提交者身份以及 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}上帐户关联的已验证电子邮件地址相匹配的 GPG 密钥,则可以开始对提交和标签进行签名。 +If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags. {% endnote %} -{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} -4. 输入 `gpg --edit-key GPG key ID`,替换为你想要使用的 GPG 密钥 ID。 在以下示例中,GPG 密钥 ID 为 `3AA5C34371567BD2`: +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.gpg.list-keys-with-note %} +{% data reusables.gpg.copy-gpg-key-id %} +4. Enter `gpg --edit-key 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 --edit-key 3AA5C34371567BD2 + $ gpg --edit-key 3AA5C34371567BD2 ``` -5. 输入 `gpg> adduid` 以添加用户 ID 详细信息。 +5. Enter `gpg> adduid` to add the user ID details. ```shell $ gpg> adduid ``` -6. 按照提示提供您的真实姓名、电子邮件地址和任何注释。 可以通过选择 `N`、`C` 或 `E` 来修改条目。 {% data reusables.gpg.private-email %} {% ifversion fpt or ghec %} 有关详细信息,请参阅“[设置提交电子邮件地址](/articles/setting-your-commit-email-address)”。{% endif %} +6. Follow the prompts to supply your real name, email address, and any comments. You can modify your entries by choosing `N`, `C`, or `E`. {% data reusables.gpg.private-email %} {% ifversion fpt or ghec %} For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)."{% endif %} ```shell - Real Name: Octocat - Email address: octocat@github.com - Comment: GitHub key + Real Name: OCTOCAT + Email address: "octocat@github.com" + Comment: GITHUB-KEY Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? ``` -7. 输入 `O` 以确认你的选择。 -8. 输入密钥的密码。 -9. 输入 `gpg> save` 以保存更改 +7. Enter `O` to confirm your selections. +8. Enter your key's passphrase. +9. Enter `gpg> save` to save the changes ```shell $ gpg> save ``` -10. 输入 `gpg --armor --export GPG key ID`,替换为你想要使用的 GPG 密钥 ID。 在以下示例中,GPG 密钥 ID 为 `3AA5C34371567BD2`: +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 + $ gpg --armor --export 3AA5C34371567BD2 # Prints the GPG key, in ASCII armor format ``` -11. 通过[将 GPG 密钥添加到 GitHub 帐户](/articles/adding-a-gpg-key-to-your-github-account)来上传 GPG 密钥。 +11. Upload the GPG key by [adding it to your GitHub account](/articles/adding-a-gpg-key-to-your-github-account). -## 延伸阅读 +## Further reading -- [检查现有 GPG 密钥](/articles/checking-for-existing-gpg-keys) -- [生成新 GPG 密钥](/articles/generating-a-new-gpg-key) -- [在 GPG 密钥中使用经验证的电子邮件地址](/articles/using-a-verified-email-address-in-your-gpg-key) -- [将 GPG 密钥添加到 GitHub 帐户](/articles/adding-a-gpg-key-to-your-github-account) -- [对提交签名](/articles/signing-commits) -- [对标记签名](/articles/signing-tags) +- "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)" +- "[Generating a new GPG key](/articles/generating-a-new-gpg-key)" +- "[Using a verified email address in your GPG key](/articles/using-a-verified-email-address-in-your-gpg-key)" +- "[Adding a GPG key to your GitHub account](/articles/adding-a-gpg-key-to-your-github-account)" +- "[Signing commits](/articles/signing-commits)" +- "[Signing tags](/articles/signing-tags)" diff --git a/translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md index 6e9972c33c..504536da90 100644 --- a/translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md +++ b/translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md @@ -20,7 +20,7 @@ shortTitle: Tell Git your signing key ## Telling Git about your GPG key -If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags. +If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags. {% note %} @@ -58,7 +58,7 @@ If you have multiple GPG keys, you need to tell Git which one to use. ## Telling Git about your GPG key -If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags. +If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags. {% note %} @@ -80,7 +80,7 @@ If you have multiple GPG keys, you need to tell Git which one to use. ## Telling Git about your GPG key -If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then you can begin signing commits and signing tags. +If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags. {% note %} diff --git a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md index 5f6a61ea37..66084e4142 100644 --- a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md +++ b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md @@ -1,6 +1,6 @@ --- -title: 关于双重身份验证 -intro: '{% data reusables.two_fa.about-2fa %}启用 2FA 时,必须使用您的用户名和密码登录,并提供另一种只有您知道或可以访问的身份验证形式。' +title: About two-factor authentication +intro: '{% data reusables.two_fa.about-2fa %} With 2FA, you have to log in with your username and password and provide another form of authentication that only you know or have access to.' redirect_from: - /articles/about-two-factor-authentication - /github/authenticating-to-github/about-two-factor-authentication @@ -12,42 +12,37 @@ versions: topics: - 2FA shortTitle: About 2FA -ms.openlocfilehash: f4b15aeeece76ce5e5afe915e0e0bc4893c4dbb6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145084612' --- -对于 {% data variables.product.product_name %} 来说,第二种身份验证形式是一个由移动设备上的应用程序生成的{% ifversion fpt or ghec %}或者以短信 (SMS) 形式发送的{% endif %}代码。 在启用 2FA 后,只要有人尝试登录您在 {% data variables.product.product_name %} 上的帐户,{% data variables.product.product_location %} 就会生成验证码。 用户能登录你的帐户的唯一方式是,他们知道你的密码,且有权访问你手机上的验证码。 +For {% data variables.product.product_name %}, the second form of authentication is a code that's generated by an application on your mobile device{% ifversion fpt or ghec %} or sent as a text message (SMS){% endif %}. After you enable 2FA, {% data variables.product.product_name %} generates an authentication code any time someone attempts to sign into your account on {% data variables.location.product_location %}. The only way someone can sign into your account is if they know both your password and have access to the authentication code on your phone. {% data reusables.two_fa.after-2fa-add-security-key %} -{% ifversion fpt or ghec %} 除了安全密钥之外,你还可以在配置 TOTP 移动应用或短信后使用 {% data variables.product.prodname_mobile %} 进行双因素身份验证。 {% data variables.product.prodname_mobile %} 使用公钥加密来保护你的帐户,允许你使用用于登录 {% data variables.product.prodname_mobile %} 的任何移动设备作为第二重身份验证。 +{% ifversion fpt or ghec %} +In addition to security keys, you can also use {% data variables.product.prodname_mobile %} for 2FA after configuring a TOTP mobile app or text messages. {% data variables.product.prodname_mobile %} uses public-key cryptography to secure your account, allowing you to use any mobile device that you've used to sign in to {% data variables.product.prodname_mobile %} as your second factor. {% endif %} -您还可以配置其他恢复方法,以防无法访问双重身份验证凭据。 有关设置 2FA 的详细信息,请参阅“[配置双因素身份验证](/articles/configuring-two-factor-authentication)”和“[配置双因素身份验证恢复方法](/articles/configuring-two-factor-authentication-recovery-methods)”。 +You can also configure additional recovery methods in case you lose access to your two-factor authentication credentials. For more information on setting up 2FA, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)" and "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)." -为确保帐户安全,强烈建议启用 2FA,不仅在 {% data variables.product.product_name %} 上启用,在支持 2FA 的其他网站和应用上也要启用。 您可以启用 2FA 以访问 {% data variables.product.product_name %} 和 {% data variables.product.prodname_desktop %}。 +We **strongly** urge you to enable 2FA for the safety of your account, not only on {% data variables.product.product_name %}, but on other websites and apps that support 2FA. You can enable 2FA to access {% data variables.product.product_name %} and {% data variables.product.prodname_desktop %}. -有关详细信息,请参阅“[使用双因素身份验证访问 {% data variables.product.prodname_dotcom %}](/articles/accessing-github-using-two-factor-authentication)”。 +For more information, see "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)." -## 双重身份验证恢复代码 +## Two-factor authentication recovery codes -{% data reusables.two_fa.about-recovery-codes %} 有关详细信息,请参阅“[丢失 2FA 凭据时恢复帐户](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)”。 +{% data reusables.two_fa.about-recovery-codes %} For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)." {% ifversion fpt or ghec %} {% warning %} -警告:{% data reusables.two_fa.support-may-not-help %} 有关详细信息,请参阅“[丢失 2FA 凭据时恢复帐户](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)”。 +**Warning**: {% data reusables.two_fa.support-may-not-help %} For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)." {% endwarning %} {% endif %} -## 在你的组织中要求进行双因素身份验证 +## Requiring two-factor authentication in your organization -组织所有者可要求组织成员{% ifversion fpt or ghec %}、帐单管理员{% endif %}和外部协作者使用双因素身份验证保护其个人帐户。 有关详细信息,请参阅“[要求在组织中进行双因素身份验证](/articles/requiring-two-factor-authentication-in-your-organization)”。 +Organization owners can require that organization members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators use two-factor authentication to secure their personal accounts. For more information, see "[Requiring two-factor authentication in your organization](/articles/requiring-two-factor-authentication-in-your-organization)." {% data reusables.two_fa.auth_methods_2fa %} diff --git a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md index d1a25e19da..a79e1f0801 100644 --- a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md +++ b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md @@ -1,6 +1,6 @@ --- -title: 使用双重身份验证访问 GitHub -intro: '启用 2FA 后,在登录到 {% data variables.product.product_name %} 时需要提供 2FA 验证码以及密码。' +title: Accessing GitHub using two-factor authentication +intro: 'With 2FA enabled, you''ll be asked to provide your 2FA authentication code, as well as your password, when you sign in to {% data variables.product.product_name %}.' redirect_from: - /articles/providing-your-2fa-security-code - /articles/providing-your-2fa-authentication-code @@ -15,89 +15,83 @@ versions: topics: - 2FA shortTitle: Access GitHub with 2FA -ms.openlocfilehash: 244cc4b45165cbc327729fd6d1c5ac519a6a6d7a -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145084610' --- -启用双重身份验证后,您在通过浏览器访问 {% data variables.product.product_name %} 时需要提供验证码。 如果使用其他方法访问 {% data variables.product.product_name %},如 API 或命令行,则需要使用其他形式的身份验证。 有关详细信息,请参阅“[关于对 {% data variables.product.prodname_dotcom %} 的身份验证](/github/authenticating-to-github/about-authentication-to-github)”。 +With two-factor authentication enabled, you'll need to provide an authentication code when accessing {% data variables.product.product_name %} through your browser. If you access {% data variables.product.product_name %} using other methods, such as the API or the command line, you'll need to use an alternative form of authentication. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)." -## 登录网站时提供 2FA 码 +## Providing a 2FA code when signing in to the website -在使用密码登录 {% data variables.product.product_name %} 后,系统会提示你提供{% ifversion fpt or ghec %}短信或{% endif %} TOTP 应用中的验证码。 +After you sign in to {% data variables.product.product_name %} using your password, you'll be prompted to provide an authentication code from {% ifversion fpt or ghec %}a text message or{% endif %} your TOTP app. -{% data variables.product.product_name %} 仅在您注销后、使用新设备或会话过期时才会要求您再次提供 2FA 验证码。 +{% data variables.product.product_name %} will only ask you to provide your 2FA authentication code again if you've logged out, are using a new device, or your session expires. -### 通过 TOTP 应用程序生成代码 +### Generating a code through a TOTP application -如果选择使用 TOTP 应用程序在智能手机上设置双重身份验证,可随时为 {% data variables.product.product_name %} 生成验证码。 大多数情况下,只有启动应用程序才会生成新代码。 具体说明请参阅应用程序的文档。 +If you chose to set up two-factor authentication using a TOTP application on your smartphone, you can generate an authentication code for {% data variables.product.product_name %} at any time. In most cases, just launching the application will generate a new code. You should refer to your application's documentation for specific instructions. -如果在配置双重身份验证后删除移动应用程序,则需要提供恢复代码才可访问您的帐户。 有关详细信息,请参阅“[丢失双因素身份验证凭据时恢复帐户](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)” +If you delete the mobile application after configuring two-factor authentication, you'll need to provide your recovery code to get access to your account. For more information, see "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" {% ifversion fpt or ghec %} -### 接收短信 +### Receiving a text message -如果设置通过短信进行双重身份验证,{% data variables.product.product_name %} 将通过短信向您发送验证码。 +If you set up two-factor authentication via text messages, {% data variables.product.product_name %} will send you a text message with your authentication code. -### 向 {% data variables.product.prodname_mobile %} 验证 +### Verifying with {% data variables.product.prodname_mobile %} -如果您已安装并登录到 {% data variables.product.prodname_mobile %},则可以选择向 {% data variables.product.prodname_mobile %} 验证以进行双重身份验证。 +If you have installed and signed in to {% data variables.product.prodname_mobile %}, you may choose to authenticate with {% data variables.product.prodname_mobile %} for two-factor authentication. -1. 使用您的用户名和密码通过浏览器登录 {% data variables.product.product_name %}。 -2. 如果您已向帐号添加了安全密钥,系统将首先提示您插入并使用安全密钥。 若要跳过使用安全密钥,请单击“使用 {% data variables.product.prodname_mobile %} 进行身份验证”。 - ![突出显示“使用 {% data variables.product.prodname_mobile %} 进行身份验证”的 {% data variables.product.product_name %} 上的双因素身份验证质询](/assets/images/help/2fa/2fa-select-mobile.png) -3. {% data variables.product.product_name %} 将向您发送推送通知以验证您的登录尝试。 打开推送通知或打开 {% data variables.product.prodname_mobile %} 应用程序将显示提示,要求你批准或拒绝此登录尝试。 +1. Sign in to {% data variables.product.product_name %} with your browser, using your username and password. +2. If you have added a security key to your account, you'll first be prompted to insert and use a security key. To skip using a security key, click **Authenticate with {% data variables.product.prodname_mobile %}**. + ![Two-factor authentication challenge on {% data variables.product.product_name %} with "Authenticate with {% data variables.product.prodname_mobile %}" highlighted](/assets/images/help/2fa/2fa-select-mobile.png) +3. {% data variables.product.product_name %} will send you a push notification to verify your sign in attempt. Opening the push notification or opening the {% data variables.product.prodname_mobile %} app will display a prompt, asking you to approve or reject this sign in attempt. {% note %} - 注意:此提示可能要求你输入正在登录的浏览器中显示的两位数字。 + **Note**: This prompt may require you to enter a two-digit number displayed within the browser you are signing in to. {% endnote %} - ![需要两位数输入的 {% data variables.product.prodname_mobile %} 的双重身份验证质询](/assets/images/help/2fa/2fa-mobile-number-challenge.png) + ![Two-factor authentication challenge with {% data variables.product.prodname_mobile %} requiring a two-digit input](/assets/images/help/2fa/2fa-mobile-number-challenge.png) - - 使用 {% data variables.product.prodname_mobile %} 批准登录尝试后,您的浏览器将自动完成登录尝试。 - - 拒绝登录尝试将阻止身份验证完成。 有关详细信息,请参阅“[确保帐户和数据安全](/authentication/keeping-your-account-and-data-secure)”。 + - Upon approving the login attempt using {% data variables.product.prodname_mobile %}, your browser will complete the sign in attempt automatically. + - Rejecting the sign in attempt will prevent the authentication from finishing. For more information, see "[Keeping your account and data secure](/authentication/keeping-your-account-and-data-secure)." {% endif %} -## 通过命令行使用双重身份验证 +## Using two-factor authentication with the command line -启用 2FA 后,将不再使用密码在命令行上访问 {% data variables.product.product_name %}。 请改用 Git 凭据管理器、个人访问令牌或 SSH 密钥。 +After you've enabled 2FA, you will no longer use your password to access {% data variables.product.product_name %} on the command line. Instead, use Git Credential Manager, a {% data variables.product.pat_generic %}, or an SSH key. -### 使用 Git 凭据管理器在命令行上进行身份验证 +### Authenticating on the command line using Git Credential Manager -[Git 凭据管理器](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md)是一个安全的 Git 凭据帮助程序,可在 Windows、macOS 和 Linux 上运行。 有关 Git 凭据帮助程序的详细信息,请参阅 Pro Git 手册中的[避免重复](https://git-scm.com/docs/gitcredentials#_avoiding_repetition)。 +[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md) is a secure Git credential helper that runs on Windows, macOS, and Linux. For more information about Git credential helpers, see [Avoiding repetition](https://git-scm.com/docs/gitcredentials#_avoiding_repetition) in the Pro Git book. -安装说明因计算机操作系统而异。 有关详细信息,请参阅 GitCredentialManager/git-credential-manager 存储库中的[下载和安装](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md#download-and-install)。 +Setup instructions vary based on your computer's operating system. For more information, see [Download and install](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md#download-and-install) in the GitCredentialManager/git-credential-manager repository. -### 在命令行上使用 HTTPS 验证 +### Authenticating on the command line using HTTPS -启用 2FA 后,必须创建个人访问令牌以用作在命令行上使用 HTTPS URL 向 {% data variables.product.product_name %} 验证时的密码。 +After you've enabled 2FA, you must create a {% data variables.product.pat_generic %} to use as a password when authenticating to {% data variables.product.product_name %} on the command line using HTTPS URLs. -当命令行上提供用户名和密码时,使用您的 {% data variables.product.product_name %} 用户名和个人访问令牌。 命令行提示不会指出在要求密码时您应输入个人访问令牌。 +When prompted for a username and password on the command line, use your {% data variables.product.product_name %} username and {% data variables.product.pat_generic %}. The command line prompt won't specify that you should enter your {% data variables.product.pat_generic %} when it asks for your password. -有关详细信息,请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 +For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." -### 在命令行上使用 SSH 验证 +### Authenticating on the command line using SSH -启用 2FA 不会更改您在命令行上使用 SSH URL 向 {% data variables.product.product_name %} 验证的方式。 有关设置和使用 SSH 密钥的详细信息,请参阅“[使用 SSH 连接到 {% data variables.product.prodname_dotcom %}](/articles/connecting-to-github-with-ssh/)”。 +Enabling 2FA doesn't change how you authenticate to {% data variables.product.product_name %} on the command line using SSH URLs. For more information about setting up and using an SSH key, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/articles/connecting-to-github-with-ssh/)." -## 使用双重身份验证通过 Subversion 访问仓库 +## Using two-factor authentication to access a repository using Subversion -通过 Subversion 访问仓库时,必须提供个人人访问令牌,而不是输入密码。 有关详细信息,请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 +When you access a repository via Subversion, you must provide a {% data variables.product.pat_generic %} instead of entering your password. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." -## 故障排除 +## Troubleshooting -如果失去对双重身份验证凭据的访问,您可以使用恢复代码或其他恢复方式(如已设置)重新获取对帐户的访问。 有关详细信息,请参阅“[丢失 2FA 凭据时恢复帐户](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)”。 +If you lose access to your two-factor authentication credentials, you can use your recovery codes or another recovery method (if you've set one up) to regain access to your account. For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)." -如果身份验证失败多次,您可能要与移动提供商同步手机的时钟。 通常,这需要在手机的时钟上选中 "Set automatically"(自动设置)选项,而不是提供自己的时区。 +If your authentication fails several times, you may wish to synchronize your phone's clock with your mobile provider. Often, this involves checking the "Set automatically" option on your phone's clock, rather than providing your own time zone. -## 延伸阅读 +## Further reading -- [关于双因素身份验证](/articles/about-two-factor-authentication) -- [配置双因素身份验证](/articles/configuring-two-factor-authentication) -- [配置双因素身份验证恢复方法](/articles/configuring-two-factor-authentication-recovery-methods) -- [丢失双因素身份验证凭据时恢复帐户](/articles/recovering-your-account-if-you-lose-your-2fa-credentials) +- "[About two-factor authentication](/articles/about-two-factor-authentication)" +- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)" +- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)" +- "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" diff --git a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md index ff370080e8..ec06abf702 100644 --- a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md +++ b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md @@ -1,6 +1,6 @@ --- -title: 配置双重身份验证 -intro: 您可以选择多个选项,以向帐户添加第二个身份验证源。 +title: Configuring two-factor authentication +intro: You can choose among multiple options to add a second source of authentication to your account. redirect_from: - /articles/configuring-two-factor-authentication-via-a-totp-mobile-app - /articles/configuring-two-factor-authentication-via-text-message @@ -15,34 +15,28 @@ versions: topics: - 2FA shortTitle: Configure 2FA -ms.openlocfilehash: e7d6f4e9518bdd7ef7012e996f8ad72179711949 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147063560' --- -你可以使用移动应用{% ifversion fpt or ghec %} 或通过短信{% endif %}配置双重身份验证。 您也可以添加安全密钥。 +You can configure two-factor authentication using a mobile app{% ifversion fpt or ghec %} or via text message{% endif %}. You can also add a security key. -我们强烈建议使用基于时间的一次性密码 (TOTP) 应用程序来配置 2FA。{% ifversion fpt or ghec %} TOTP 应用程序比 SMS 更可靠,特别是对于美国以外的地区。{% endif %} TOTP 应用支持在云中安全备份你的验证码,并且在无法访问设备的情况下也可以进行还原。 +We strongly recommend using a time-based one-time password (TOTP) application to configure 2FA.{% ifversion fpt or ghec %} TOTP applications are more reliable than SMS, especially for locations outside the United States.{% endif %} TOTP apps support the secure backup of your authentication codes in the cloud and can be restored if you lose access to your device. {% warning %} -**警告:** -- 如果你是要求双重身份验证的组织中的成员{% ifversion fpt or ghec %}、账单管理员{% endif %}或其专用存储库的外部协作者,则必须离开该组织后才能在 {% data variables.product.product_location %} 上禁用 2FA。 -- 如果禁用 2FA,您将自动失去对该组织以及您在该组织私有仓库中所拥有的任何私有复刻的访问权限。 要恢复对该组织和复刻的访问权限,请重新启用双重身份验证并联系组织所有者。 +**Warning:** +- If you're a member{% ifversion fpt or ghec %}, billing manager,{% endif %} or outside collaborator to a private repository of an organization that requires two-factor authentication, you must leave the organization before you can disable 2FA on {% data variables.location.product_location %}. +- If you disable 2FA, you will automatically lose access to the organization and any private forks you have of the organization's private repositories. To regain access to the organization and your forks, re-enable two-factor authentication and contact an organization owner. {% endwarning %} {% ifversion fpt or ghec %} -如果你是{% data variables.product.prodname_emu_enterprise %}的成员,则无法为你的{% data variables.product.prodname_managed_user %}帐户配置 2FA,除非你以设置用户的身份登录。 对于除设置用户以外的用户,管理员必须针对你的标识提供者 (IdP) 配置 2FA。 +If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you cannot configure 2FA for your {% data variables.enterprise.prodname_managed_user %} account unless you're signed in as the setup user. For users other than the setup user, an administrator must configure 2FA on your identity provider (IdP). {% endif %} -## 使用 TOTP 移动应用程序配置双重身份验证 +## Configuring two-factor authentication using a TOTP mobile app -基于时间的一次性密码 (TOTP) 应用程序可自动生成在特定时间后变化的验证码。 我们建议使用基于云的 TOTP 应用程序,例如: +A time-based one-time password (TOTP) application automatically generates an authentication code that changes after a certain period of time. We recommend using cloud-based TOTP apps such as: - [1Password](https://support.1password.com/one-time-passwords/) - [Authy](https://authy.com/guides/github/) - [LastPass Authenticator](https://lastpass.com/auth/) @@ -50,99 +44,112 @@ ms.locfileid: '147063560' {% tip %} -提示:若要在多个设备上通过 TOTP 配置身份验证,请在设置过程中,同时使用每个设备扫描 QR 码。 如果已启用 2FA,但您要添加其他设备,则必须从安全设置中重新配置 2FA。 +**Tip**: To configure authentication via TOTP on multiple devices, during setup, scan the QR code using each device at the same time. If 2FA is already enabled and you want to add another device, you must re-configure 2FA from your security settings. {% endtip %} -1. 下载 TOTP 应用程序。 -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security %} {% data reusables.two_fa.enable-two-factor-authentication %} {%- ifversion fpt or ghec or ghes %} -5. 在“双重身份验证”下,选择“使用应用进行设置”,然后单击“继续” 。 -6. 在“Authentication verification(身份验证)”下,执行以下操作之一: - - 使用移动设备的应用程序扫描 QR 码。 扫描完成后,应用程序会显示六位数代码,您可以在 {% data variables.product.product_name %} 输入该代码。 - - 如果无法扫描 QR 码,请单击“输入此文本代码”以查看可在 TOTP 应用中手动输入的代码。 - ![单击“输入此代码”](/assets/images/help/2fa/2fa_wizard_app_click_code.png) -7. TOTP 移动应用程序将保存您在 {% data variables.product.product_location %} 上的帐户并每隔几秒生成新的验证码。 在 {% data variables.product.product_name %} 上,请在“Enter the six-digit code from the application(从应用程序输入六位数代码)”下的字段中输入代码。 如果恢复代码未自动显示,请单击“继续”。 -![TOTP 输入代码字段](/assets/images/help/2fa/2fa_wizard_app_enter_code.png) {% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %} {%- else %} -5. 在“双重身份验证”页上,单击“使用应用进行设置”。 -6. 将恢复代码保存在安全的位置。 在失去访问权限时,恢复代码可帮助您恢复帐户登录。 - - 若要将恢复代码保存在设备上,请单击“下载”。 - - 若要保存恢复代码的打印件,请单击“打印”。 - - 若要复制恢复代码以存储在密码管理器中,请单击“复制”。 - ![可选择下载、打印或复制代码的恢复代码列表](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png) -7. 保存双重身份验证恢复代码后,单击“下一步”。 -8. 在双重身份验证页面上,执行以下操作之一: - - 使用移动设备的应用程序扫描 QR 码。 扫描完成后,应用程序会显示六位数代码,您可以在 {% data variables.product.product_name %} 输入该代码。 - - 如果无法扫描 QR 码,请单击“输入此文本代码”以查看可复制的代码,然后在 {% data variables.product.product_name %} 上手动输入。 - ![单击“输入此代码”](/assets/images/help/2fa/totp-click-enter-code.png) -9. TOTP 移动应用程序将保存您在 {% data variables.product.product_location %} 上的帐户并每隔几秒生成新的验证码。 在 {% data variables.product.product_name %} 中的 2FA 页面上,键入代码并单击“启用”。 - ![TOTP“启用”字段](/assets/images/help/2fa/totp-enter-code.png) {%- endif %} {% data reusables.two_fa.test_2fa_immediately %} +1. Download a TOTP app. +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.security %} +{% data reusables.two_fa.enable-two-factor-authentication %} +{%- ifversion fpt or ghec or ghes %} +5. Under "Two-factor authentication", select **Set up using an app** and click **Continue**. +6. Under "Authentication verification", do one of the following: + - Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}. + - If you can't scan the QR code, click **enter this text code** to see a code that you can manually enter in your TOTP app instead. + ![Click enter this code](/assets/images/help/2fa/2fa_wizard_app_click_code.png) +7. The TOTP mobile application saves your account on {% data variables.location.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code from the application". If your recovery codes are not automatically displayed, click **Continue**. +![TOTP enter code field](/assets/images/help/2fa/2fa_wizard_app_enter_code.png) +{% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %} +{%- else %} +5. On the Two-factor authentication page, click **Set up using an app**. +6. Save your recovery codes in a safe place. Your recovery codes can help you get back into your account if you lose access. + - To save your recovery codes on your device, click **Download**. + - To save a hard copy of your recovery codes, click **Print**. + - To copy your recovery codes for storage in a password manager, click **Copy**. + ![List of recovery codes with option to download, print, or copy the codes](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png) +7. After saving your two-factor recovery codes, click **Next**. +8. On the Two-factor authentication page, do one of the following: + - Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}. + - If you can't scan the QR code, click **enter this text code** to see a code you can copy and manually enter on {% data variables.product.product_name %} instead. + ![Click enter this code](/assets/images/help/2fa/totp-click-enter-code.png) +9. The TOTP mobile application saves your account on {% data variables.location.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, on the 2FA page, type the code and click **Enable**. + ![TOTP Enable field](/assets/images/help/2fa/totp-enter-code.png) +{%- endif %} +{% data reusables.two_fa.test_2fa_immediately %} {% ifversion fpt or ghec %} -## 使用短信配置双重身份验证 +## Configuring two-factor authentication using text messages -如果无法使用 TOTP 移动应用程序进行身份验证,您可以使用短信进行身份验证。 也可以提供后备设备的号码作为第二号码。 在无法访问主设备和恢复代码时,可通过备用短信号码恢复帐户登录。 +If you're unable to authenticate using a TOTP mobile app, you can authenticate using SMS messages. You can also provide a second number for a fallback device. If you lose access to both your primary device and your recovery codes, a backup SMS number can get you back in to your account. -在使用此方法之前,请确保您可以接收短信。 运营商可能会收取短信费用。 +Before using this method, be sure that you can receive text messages. Carrier rates may apply. {% warning %} -警告:我们强烈建议使用 TOTP 应用程序进行双重身份验证,而不是使用 SMS 。 {% data variables.product.product_name %} 并非支持向每个国家/地区的手机发送短信。 通过短信配置身份验证之前,请查看 {% data variables.product.product_name %} 支持通过 SMS 验证的国家/地区列表。 有关详细信息,请参阅“[支持 SMS 身份验证的国家/地区](/articles/countries-where-sms-authentication-is-supported)”。 +**Warning:** We **strongly recommend** using a TOTP application for two-factor authentication instead of SMS. {% data variables.product.product_name %} doesn't support sending SMS messages to phones in every country. Before configuring authentication via text message, review the list of countries where {% data variables.product.product_name %} supports authentication via SMS. For more information, see "[Countries where SMS authentication is supported](/articles/countries-where-sms-authentication-is-supported)". {% endwarning %} -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security %} {% data reusables.two_fa.enable-two-factor-authentication %} -4. 在“双重身份验证”下,选择“使用 SMS 进行设置”,然后单击“继续” 。 -5. 在“Authentication verification(身份验证)”下,选择您的国家/地区代码并键入您的手机号码,包括区号。 确认信息无误后,单击“发送验证码”。 +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.security %} +{% data reusables.two_fa.enable-two-factor-authentication %} +4. Under "Two-factor authentication", select **Set up using SMS** and click **Continue**. +5. Under "Authentication verification", select your country code and type your mobile phone number, including the area code. When your information is correct, click **Send authentication code**. - ![2FA SMS 屏幕](/assets/images/help/2fa/2fa_wizard_sms_send.png) + ![2FA SMS screen](/assets/images/help/2fa/2fa_wizard_sms_send.png) -6. 您将收到含安全码的短信。 在 {% data variables.product.product_name %} 上,请在“输入发送到手机的六位数代码”下的字段中键入代码,然后单击“继续”。 +6. You'll receive a text message with a security code. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code sent to your phone" and click **Continue**. - ![2FA SMS“继续”字段](/assets/images/help/2fa/2fa_wizard_sms_enter_code.png) {% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %} {% data reusables.two_fa.test_2fa_immediately %} + ![2FA SMS continue field](/assets/images/help/2fa/2fa_wizard_sms_enter_code.png) +{% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %} +{% data reusables.two_fa.test_2fa_immediately %} {% endif %} -## 使用安全密钥配置双重身份验证 +## Configuring two-factor authentication using a security key {% data reusables.two_fa.after-2fa-add-security-key %} -在大多数设备和浏览器上,您可以通过 USB 或 NFC 使用物理安全密钥。 某些浏览器可以使用设备上的指纹读取器、面部识别或密码/PIN 作为安全密钥。 +On most devices and browsers, you can use a physical security key over USB or NFC. Some browsers can use the fingerprint reader, facial recognition, or password/PIN on your device as a security key. -使用安全密钥进行身份验证是使用 TOTP 应用程序{% ifversion fpt or ghec %}或短信进行身份验证的备用选择{% endif %}。 如果您丢失了安全密钥,仍可以使用手机的代码进行登录。 +Authentication with a security key is *secondary* to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}. If you lose your security key, you'll still be able to use your phone's code to sign in. -1. 必须已通过 TOTP 移动应用{% ifversion fpt or ghec %} 或通过 SMS{% endif %} 配置了 2FA。 -2. 确保您的计算机中已插入 WebAuthn 兼容安全密钥。 -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security %} -5. 在“安全密钥”旁边,单击“添加”。 - ![添加安全密钥选项](/assets/images/help/2fa/add-security-keys-option.png) -6. 在“安全密钥”下,单击“注册新安全密钥”。 - ![注册新安全密钥](/assets/images/help/2fa/security-key-register.png) -7. 键入安全密钥的昵称,然后单击“添加”。 - ![为安全密钥提供昵称](/assets/images/help/2fa/security-key-nickname.png) -8. 按照安全密钥的文档激活安全密钥。 - ![提示输入安全密钥](/assets/images/help/2fa/security-key-prompt.png) -9. 确认您已下载并且能够访问恢复代码。 如果尚未下载,或者要生成另一组代码,请下载代码并将其保存在安全位置。 如果无法访问自己的帐户,您可以使用恢复代码来恢复帐户访问。 有关详细信息,请参阅“[丢失 2FA 凭据时恢复帐户](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)”。 - ![“下载恢复代码”按钮](/assets/images/help/2fa/2fa-recover-during-setup.png) {% data reusables.two_fa.test_2fa_immediately %} +1. You must have already configured 2FA via a TOTP mobile app{% ifversion fpt or ghec %} or via SMS{% endif %}. +2. Ensure that you have a WebAuthn compatible security key inserted into your computer. +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.security %} +5. Next to "Security keys", click **Add**. + ![Add security keys option](/assets/images/help/2fa/add-security-keys-option.png) +6. Under "Security keys", click **Register new security key**. + ![Registering a new security key](/assets/images/help/2fa/security-key-register.png) +7. Type a nickname for the security key, then click **Add**. + ![Providing a nickname for a security key](/assets/images/help/2fa/security-key-nickname.png) +8. Activate your security key, following your security key's documentation. + ![Prompt for a security key](/assets/images/help/2fa/security-key-prompt.png) +9. Confirm that you've downloaded and can access your recovery codes. If you haven't already, or if you'd like to generate another set of codes, download your codes and save them in a safe place. If you lose access to your account, you can use your recovery codes to get back into your account. For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)." + ![Download recovery codes button](/assets/images/help/2fa/2fa-recover-during-setup.png) +{% data reusables.two_fa.test_2fa_immediately %} {% ifversion fpt or ghec %} -## 使用 {% data variables.product.prodname_mobile %} 配置双重身份验证 +## Configuring two-factor authentication using {% data variables.product.prodname_mobile %} -在 Web 浏览器中登录 {% data variables.product.prodname_dotcom %} 帐户时,您可以使用 {% data variables.product.prodname_mobile %} 进行双重身份验证。 向 {% data variables.product.prodname_mobile %} 进行双重身份验证不依赖于 TOTP,而是使用公钥加密来保护您的帐户。 +You can use {% data variables.product.prodname_mobile %} for 2FA when signing into your {% data variables.product.prodname_dotcom %} account in a web browser. 2FA with {% data variables.product.prodname_mobile %} does not rely on TOTP, and instead uses public-key cryptography to secure your account. -配置 TOTP 应用程序或 SMS 后,您还可以使用 {% data variables.product.prodname_mobile %} 进行身份验证。 如果将来您不再有权访问 {% data variables.product.prodname_mobile %},您仍然可以使用安全密钥或 TOTP 应用程序登录。 +Once you have configured a TOTP application, or SMS, you can also use {% data variables.product.prodname_mobile %} to authenticate. If, in the future, you no longer have access to {% data variables.product.prodname_mobile %}, you will still be able to use security keys or TOTP applications to sign in. -1. 您必须已经通过 TOTP 移动应用程序或短信配置双重身份验证。 -2. 安装 [{% data variables.product.prodname_mobile %}](https://github.com/mobile)。 -3. 从 {% data variables.product.prodname_mobile %} 登录到您的 {% data variables.product.product_name %} 帐户。 +1. You must have already configured 2FA via a TOTP mobile app or via SMS. +2. Install [{% data variables.product.prodname_mobile %}](https://github.com/mobile). +3. Sign in to your {% data variables.product.product_name %} account from {% data variables.product.prodname_mobile %}. -登录后,您现在可以将设备用于 2FA。 +After signing in, you can now use your device for 2FA. {% endif %} -## 延伸阅读 +## Further reading -- [关于双因素身份验证](/articles/about-two-factor-authentication) -- [配置双重身份验证恢复方法](/articles/configuring-two-factor-authentication-recovery-methods) -- [使用双重身份验证访问 {% data variables.product.prodname_dotcom %}](/articles/accessing-github-using-two-factor-authentication) -- [丢失 2FA 凭据时恢复帐户](/articles/recovering-your-account-if-you-lose-your-2fa-credentials) -- [创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token) +- "[About two-factor authentication](/articles/about-two-factor-authentication)" +- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)" +- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)" +- "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)" +- "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)" diff --git a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md index 6c21543714..ee314edd92 100644 --- a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md +++ b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md @@ -1,6 +1,6 @@ --- -title: 使用双重身份验证 (2FA) 保护您的帐户 -intro: '您可以将您在 {% data variables.product.product_location %} 上的帐户设置为在登录时除了密码以外还需要验证码。' +title: Securing your account with two-factor authentication (2FA) +intro: 'You can set up your account on {% data variables.location.product_location %} to require an authentication code in addition to your password when you sign in.' redirect_from: - /categories/84/articles - /categories/two-factor-authentication-2fa @@ -22,11 +22,5 @@ children: - /countries-where-sms-authentication-is-supported - /disabling-two-factor-authentication-for-your-personal-account shortTitle: Secure your account with 2FA -ms.openlocfilehash: 886af1b083719e4381fcc30fcd4855507d718889 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145084594' --- diff --git a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md index 8e1cb6d4c1..6c4ac89dc0 100644 --- a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md +++ b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md @@ -1,6 +1,6 @@ --- -title: 丢失 2FA 凭据时恢复帐户 -intro: 如果无法访问双重身份验证凭据,您可以使用恢复代码或其他恢复选项重新获取对帐户的访问权限。 +title: Recovering your account if you lose your 2FA credentials +intro: 'If you lose access to your two-factor authentication credentials, you can use your recovery codes, or another recovery option, to regain access to your account.' redirect_from: - /articles/recovering-your-account-if-you-lost-your-2fa-credentials - /articles/authenticating-with-an-account-recovery-token @@ -14,18 +14,12 @@ versions: topics: - 2FA shortTitle: Recover an account with 2FA -ms.openlocfilehash: 1a93d77d4da76a6efbc96ba5d80d0fe7e800c08a -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145084595' --- {% ifversion fpt or ghec %} {% warning %} -**警告**: +**Warnings**: - {% data reusables.two_fa.support-may-not-help %} @@ -33,83 +27,84 @@ ms.locfileid: '145084595' {% endif %} -## 使用双因素身份验证恢复代码 +## Using a two-factor authentication recovery code -使用您的恢复代码之一自动重新进入您的帐户。 您可能已将恢复代码保存到密码管理器或计算机的下载文件夹中。 恢复代码的默认文件名为 `github-recovery-codes.txt`。 有关恢复代码的详细信息,请参阅“[配置双因素身份验证的恢复方法](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)”。 +Use one of your recovery codes to automatically regain entry into your account. You may have saved your recovery codes to a password manager or your computer's downloads folder. The default filename for recovery codes is `github-recovery-codes.txt`. For more information about recovery codes, see "[Configuring two-factor authentication recovery methods](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)." -1. 输入您的用户名和密码以提示身份验证。 +1. Type your username and password to prompt authentication. {% warning %} - 警告:{% data reusables.accounts.you-must-know-your-password %} + **Warning**: {% data reusables.accounts.you-must-know-your-password %} {% endwarning %} {% ifversion fpt or ghec %} -1. 在“有问题?”下,单击“使用恢复代码或请求重置”。 +1. Under "Having problems?", click **Use a recovery code or request a reset**. - ![使用恢复代码的链接的屏幕截图](/assets/images/help/2fa/2fa-recovery-code-link.png) {%- else %} -1. 在 2FA 页面上的“没有你的电话?”下,单击“输入双因素恢复代码”。 + ![Screenshot of link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png) +{%- else %} +1. On the 2FA page, under "Don't have your phone?", click **Enter a two-factor recovery code**. - ![使用恢复代码的链接的屏幕截图](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %} -1. 输入恢复代码之一,然后单击“验证”。 + ![Screenshot of link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %} +1. Type one of your recovery codes, then click **Verify**. - ![输入恢复代码的字段和验证按钮](/assets/images/help/2fa/2fa-type-verify-recovery-code.png) + ![Field to type a recovery code and Verify button](/assets/images/help/2fa/2fa-type-verify-recovery-code.png) {% ifversion fpt or ghec %} -## 使用后备号码进行身份验证 +## Authenticating with a fallback number -如果无法访问主要 TOTP 应用程序或电话号码,则可以提供发送到后备号码的双因素身份验证码,以自动重新获得对帐户的访问权限。 +If you lose access to your primary TOTP app or phone number, you can provide a two-factor authentication code sent to your fallback number to automatically regain access to your account. {% endif %} -## 使用安全密钥进行身份验证 +## Authenticating with a security key -如果您使用安全密钥配置双重身份验证,则可以使用安全密钥作为辅助身份验证方法来自动重新获得对帐户的访问权限。 有关详细信息,请参阅“[配置双因素身份验证](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)”。 +If you configured two-factor authentication using a security key, you can use your security key as a secondary authentication method to automatically regain access to your account. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)." {% ifversion fpt or ghec %} -## 使用经过验证的设备、SSH 令牌或个人访问令牌进行身份验证 +## Authenticating with a verified device, SSH token, or {% data variables.product.pat_generic %} -如果您知道 {% data variables.product.product_location %} 的密码但无法访问双重身份验证凭据,或没有双重身份验证恢复代码,则可以将一次性密码发送到经验证的电子邮件地址,以开始验证过程,重新获得对帐户的访问权限。 +If you know your password for {% data variables.location.product_location %} but don't have the two-factor authentication credentials or your two-factor authentication recovery codes, you can have a one-time password sent to your verified email address to begin the verification process and regain access to your account. {% note %} -注意:出于安全原因,使用一次性密码验证进行身份验证来重新获得帐户访问权限可能需要最长三个工作日。 在此期间,{% data variables.product.company_short %} 不会审核提交的其他请求。 +**Note**: For security reasons, regaining access to your account by authenticating with a one-time password can take up to three business days. {% data variables.product.company_short %} will not review additional requests submitted during this time. {% endnote %} -在这 3-5 天的等待期内,您随时可以使用双重身份验证凭据或双重身份验证恢复代码重新获得对帐户的访问权限。 +You can use your two-factor authentication credentials or two-factor authentication recovery codes to regain access to your account anytime during the 3-5 day waiting period. -1. 输入您的用户名和密码以提示身份验证。 +1. Type your username and password to prompt authentication. {% warning %} - 警告:{% data reusables.accounts.you-must-know-your-password %} + **Warning**: {% data reusables.accounts.you-must-know-your-password %} {% endwarning %} -1. 在“有问题?”下,单击“使用恢复代码或请求重置”。 +1. Under "Having problems?", click **Use a recovery code or request a reset**. - ![没有 2fa 设备或恢复码时的链接的屏幕截图](/assets/images/help/2fa/no-access-link.png) -1. 在“已锁定?”的右侧,单击“尝试恢复你的帐户”。 + ![Screenshot of link if you don't have your 2fa device or recovery codes](/assets/images/help/2fa/no-access-link.png) +1. To the right of "Locked out?", click **Try recovering your account**. - ![用于尝试恢复帐户的链接的屏幕截图](/assets/images/help/2fa/try-recovering-your-account-link.png) -1. 单击“我理解,开始”请求重置身份验证设置。 + ![Screenshot of link to try recovering your account](/assets/images/help/2fa/try-recovering-your-account-link.png) +1. Click **I understand, get started** to request a reset of your authentication settings. - ![用于开始重置身份验证设置的按钮的屏幕截图](/assets/images/help/2fa/reset-auth-settings.png) -1. 单击“发送一次性密码”,向与你的帐户关联的所有合格地址发送一次性密码。 只有经过验证的电子邮件才有资格进行帐户恢复。 如果您已将密码重置限制为主地址和/或备用地址,则这些地址是唯一有资格恢复帐户的地址。 + ![Screenshot of button to start reset of authentication settings](/assets/images/help/2fa/reset-auth-settings.png) +1. Click **Send one-time password** to send a one-time password to all eligible addresses associated with your account. Only verified emails are eligible for account recovery. If you've restricted password resets to your primary and/or backup addresses, these addresses are the only addresses eligible for account recovery. - ![用于发送一次性密码的按钮的屏幕截图](/assets/images/help/2fa/send-one-time-password.png) -1. 在“One-time password(一次性密码)”下,键入恢复电子邮件 {% data variables.product.prodname_dotcom %} 发送的临时密码。 + ![Screenshot of button to send one-time password](/assets/images/help/2fa/send-one-time-password.png) +1. Under "One-time password", type the temporary password from the recovery email {% data variables.product.prodname_dotcom %} sent. - ![用于键入一次性密码的字段的屏幕截图](/assets/images/help/2fa/one-time-password-field.png) -1. 单击“验证电子邮件地址”。 + ![Screenshot of field to type one-time password](/assets/images/help/2fa/one-time-password-field.png) +1. Click **Verify email address**. - ![用于验证电子邮件地址的按钮的屏幕截图](/assets/images/help/2fa/verify-email-address.png) -1. 选择替代验证因素。 - - 如果之前已经使用当前设备登录此帐户,并且想使用该设备进行验证,请单击“使用此设备进行验证”。 - - 如果之前已在此帐户上设置 SSH 密钥,并且想使用此 SSH 密钥进行验证,请单击“SSH 密钥”。 - - 如果之前已经设置个人访问令牌,并且想使用个人访问令牌进行验证,请单击“个人访问令牌”。 + ![Screenshot of button to verify email address](/assets/images/help/2fa/verify-email-address.png) +1. Choose an alternative verification factor. + - If you've used your current device to log into this account before and would like to use the device for verification, click **Verify with this device**. + - If you've previously set up an SSH key on this account and would like to use the SSH key for verification, click **SSH key**. + - If you've previously set up a {% data variables.product.pat_generic %} and would like to use the {% data variables.product.pat_generic %} for verification, click **{% data variables.product.pat_generic_caps %}**. - ![用于替代验证的按钮的屏幕截图](/assets/images/help/2fa/alt-verifications.png) -1. {% data variables.contact.github_support %} 的成员将在三个工作日内审查您的请求并给您发送电子邮件。 如果您的请求获得批准,您将收到一个完成帐户恢复过程的链接。 如果您的请求被拒绝,电子邮件将说明就任何其他问题联系支持的方式。 + ![Screenshot of buttons for alternative verification](/assets/images/help/2fa/alt-verifications.png) +1. A member of {% data variables.contact.github_support %} will review your request and email you within three business days. If your request is approved, you'll receive a link to complete your account recovery process. If your request is denied, the email will include a way to contact support with any additional questions. {% endif %} diff --git a/translations/zh-CN/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md b/translations/zh-CN/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md index 59faffeffe..d134f687e9 100644 --- a/translations/zh-CN/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md +++ b/translations/zh-CN/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md @@ -1,6 +1,6 @@ --- -title: 错误:代理承认没有签署 -intro: '在极少数情况下,通过 Linux 上的 SSH 连接到 {% data variables.product.product_name %} 会产生错误 `"Agent admitted failure to sign using the key"`。 请遵循以下步骤解决此问题。' +title: 'Error: Agent admitted failure to sign' +intro: 'In rare circumstances, connecting to {% data variables.product.product_name %} via SSH on Linux produces the error `"Agent admitted failure to sign using the key"`. Follow these steps to resolve the problem.' redirect_from: - /articles/error-agent-admitted-failure-to-sign-using-the-key - /articles/error-agent-admitted-failure-to-sign @@ -14,14 +14,8 @@ versions: topics: - SSH shortTitle: Agent failure to sign -ms.openlocfilehash: eceb783df61b403a6b94b8eda84be62e63aa5ead -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145084579' --- -在 Linux 上尝试将通过 SSH 连接到 {% data variables.product.product_location %} 时,可能在终端上看到以下信息: +When trying to SSH into {% data variables.location.product_location %} on a Linux computer, you may see the following message in your terminal: ```shell $ ssh -vT git@{% data variables.command_line.codeblock %} @@ -31,28 +25,28 @@ $ ssh -vT git@{% data variables.command_line.codeblock %} > Permission denied (publickey). ``` -有关详细信息,请参阅此问题报告。 +For more details, see this issue report. -## 解决方法 +## Resolution -通过使用 `ssh-add` 将密钥加载到 SSH 代理,应该能够修复此错误: +You should be able to fix this error by loading your keys into your SSH agent with `ssh-add`: ```shell # start the ssh-agent in the background $ eval "$(ssh-agent -s)" > Agent pid 59566 $ ssh-add -> Enter passphrase for /home/you/.ssh/id_rsa: [tippy tap] -> Identity added: /home/you/.ssh/id_rsa (/home/you/.ssh/id_rsa) +> Enter passphrase for /home/YOU/.ssh/id_rsa: [tippy tap] +> Identity added: /home/YOU/.ssh/id_rsa (/home/YOU/.ssh/id_rsa) ``` -如果密钥没有默认文件名 (`/.ssh/id_rsa`),必须将该路径传递到 `ssh-add`: +If your key does not have the default filename (`/.ssh/id_rsa`), you'll have to pass that path to `ssh-add`: ```shell # start the ssh-agent in the background $ eval "$(ssh-agent -s)" > Agent pid 59566 $ ssh-add ~/.ssh/my_other_key -> Enter passphrase for /home/you/.ssh/my_other_key: [tappity tap tap] -> Identity added: /home/you/.ssh/my_other_key (/home/you/.ssh/my_other_key) +> Enter passphrase for /home/YOU/.ssh/my_other_key: [tappity tap tap] +> Identity added: /home/YOU/.ssh/my_other_key (/home/YOU/.ssh/my_other_key) ``` diff --git a/translations/zh-CN/content/authentication/troubleshooting-ssh/error-key-already-in-use.md b/translations/zh-CN/content/authentication/troubleshooting-ssh/error-key-already-in-use.md index 1ab6570c1f..315f4701b6 100644 --- a/translations/zh-CN/content/authentication/troubleshooting-ssh/error-key-already-in-use.md +++ b/translations/zh-CN/content/authentication/troubleshooting-ssh/error-key-already-in-use.md @@ -1,6 +1,6 @@ --- -title: 错误:密钥已被使用 -intro: '尝试添加已添加到其他帐户或存储库的[密钥](/articles/adding-a-new-ssh-key-to-your-github-account)时,会发生此错误。' +title: 'Error: Key already in use' +intro: 'This error occurs when you try to [add a key](/articles/adding-a-new-ssh-key-to-your-github-account) that''s already been added to another account or repository.' redirect_from: - /articles/error-key-already-in-use - /github/authenticating-to-github/error-key-already-in-use @@ -12,39 +12,33 @@ versions: ghec: '*' topics: - SSH -ms.openlocfilehash: d202de2efe05951fe829a8198b20831fc15bbd72 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145084576' --- -## 查找已使用密钥的位置 +## Finding where the key has been used -要确定已使用该密钥的位置,请打开终端并键入 `ssh` 命令。 使用 `-i` 标记提供要检查的密钥的路径: +To determine where the key has already been used, open a terminal and type the `ssh` command. Use the `-i` flag to provide the path to the key you want to check: ```shell -$ ssh -T -ai ~/.ssh/id_rsa git@{% data variables.command_line.codeblock %} -# Connect to {% data variables.product.product_location %} using a specific ssh key -> Hi username! You've successfully authenticated, but GitHub does not +$ ssh -T -ai ~/.ssh/id_rsa git@{% data variables.command_line.codeblock %} +# Connect to {% data variables.location.product_location %} using a specific ssh key +> Hi USERNAME! You've successfully authenticated, but GitHub does not > provide shell access. ``` -响应中的用户名是 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上密钥当前附加到的帐户。 如果响应类似于“username/repo”,则表示密钥已作为[部署密钥](/guides/managing-deploy-keys#deploy-keys)附加到存储库。 +The *username* in the response is the account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} that the key is currently attached to. If the response looks something like "username/repo", the key has been attached to a repository as a [*deploy key*](/guides/managing-deploy-keys#deploy-keys). -要强制 SSH 仅使用命令行上提供的密钥,请使用 `-o` 添加 `IdentitiesOnly=yes` 选项: +To force SSH to use only the key provided on the command line, use `-o` to add the `IdentitiesOnly=yes` option: ```shell -$ ssh -v -o "IdentitiesOnly=yes" -i ~/.ssh/id_rsa git@{% data variables.command_line.codeblock %} +$ ssh -v -o "IdentitiesOnly=yes" -i ~/.ssh/id_rsa git@{% data variables.command_line.codeblock %} ``` -## 修复问题 +## Fixing the issue -为解决此问题,请先从其他帐户或存储库删除该密钥,然后[将其添加到帐户](/articles/adding-a-new-ssh-key-to-your-github-account)。 +To resolve the issue, first remove the key from the other account or repository and then [add it to your account](/articles/adding-a-new-ssh-key-to-your-github-account). -如果没有传输密钥的权限,请联系有权限的用户,删除密钥对并[生成新的密钥对](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)。 +If you don't have permissions to transfer the key, and can't contact a user who does, remove the keypair and [generate a brand new one](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent). -## 部署密钥 +## Deploy keys -在密钥作为部署密钥附加到一个仓库后,无法再用于另一个仓库。 如果在设置部署密钥时出现此错误,请参阅“[管理部署密钥](/guides/managing-deploy-keys)”。 +Once a key has been attached to one repository as a deploy key, it cannot be used on another repository. If you're running into this error while setting up deploy keys, see "[Managing deploy keys](/guides/managing-deploy-keys)." diff --git a/translations/zh-CN/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/translations/zh-CN/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md index 9cc6a93e78..9f094aa659 100644 --- a/translations/zh-CN/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md +++ b/translations/zh-CN/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md @@ -1,6 +1,6 @@ --- -title: 在 HTTPS 端口使用 SSH -intro: '有时,防火墙会完全拒绝允许 SSH 连接。 如果无法选择使用[具有凭据缓存的 HTTPS 克隆](/github/getting-started-with-github/caching-your-github-credentials-in-git),可以尝试使用通过 HTTPS 端口建立的 SSH 连接克隆。 大多数防火墙规则应允许此操作,但代理服务器可能会干扰。' +title: Using SSH over the HTTPS port +intro: 'Sometimes, firewalls refuse to allow SSH connections entirely. If using [HTTPS cloning with credential caching](/github/getting-started-with-github/caching-your-github-credentials-in-git) is not an option, you can attempt to clone using an SSH connection made over the HTTPS port. Most firewall rules should allow this, but proxy servers may interfere.' redirect_from: - /articles/using-ssh-over-the-https-port - /github/authenticating-to-github/using-ssh-over-the-https-port @@ -11,34 +11,28 @@ versions: topics: - SSH shortTitle: Use SSH over HTTPS port -ms.openlocfilehash: 47bdb96fac65d9432dfc54f671366d1b6c153556 -ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147883399' --- {% tip %} -{% data variables.product.prodname_ghe_server %} 用户:目前不支持经 SSH 通过 HTTPS 端口访问 {% data variables.product.prodname_ghe_server %}。 +**{% data variables.product.prodname_ghe_server %} users**: Accessing {% data variables.product.prodname_ghe_server %} via SSH over the HTTPS port is currently not supported. {% endtip %} -要测试通过 HTTPS 端口的 SSH 是否可行,请运行以下 SSH 命令: +To test if SSH over the HTTPS port is possible, run this SSH command: ```shell $ ssh -T -p 443 git@ssh.github.com -> Hi username! You've successfully authenticated, but GitHub does not +> Hi USERNAME! You've successfully authenticated, but GitHub does not > provide shell access. ``` -如果这样有效,万事大吉! 否则,可能需要[遵循我们的故障排除指南](/articles/error-permission-denied-publickey)。 +If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey). -## 启用通过 HTTPS 的 SSH 连接 +## Enabling SSH connections over HTTPS -如果你能在端口 443 上通过 SSH 连接到 `git@ssh.{% data variables.command_line.backticks %}`,则可覆盖你的 SSH 设置来强制与 {% data variables.product.product_location %} 的任何连接均通过该服务器和端口运行。 +If you are able to SSH into `git@ssh.{% data variables.command_line.backticks %}` over port 443, you can override your SSH settings to force any connection to {% data variables.location.product_location %} to run through that server and port. -要在 SSH 配置文件中设置此行为,请在 `~/.ssh/config` 编辑该文件,并添加以下部分: +To set this in your SSH configuration file, edit the file at `~/.ssh/config`, and add this section: ``` Host {% data variables.command_line.codeblock %} @@ -47,10 +41,10 @@ Port 443 User git ``` -您可以通过再次连接到 {% data variables.product.product_location %} 测试此项是否有效: +You can test that this works by connecting once more to {% data variables.location.product_location %}: ```shell $ ssh -T git@{% data variables.command_line.codeblock %} -> Hi username! You've successfully authenticated, but GitHub does not +> Hi USERNAME! You've successfully authenticated, but GitHub does not > provide shell access. ``` diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md b/translations/zh-CN/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md index 02067d13dc..dcdfa5e6df 100644 --- a/translations/zh-CN/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md +++ b/translations/zh-CN/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md @@ -1,6 +1,6 @@ --- -title: 关于 GitHub 包的计费 -intro: '如果对 {% data variables.product.prodname_registry %} 的使用超出帐户包含的存储容量或数据传输,您需要支付额外的使用费。' +title: About billing for GitHub Packages +intro: 'If you want to use {% data variables.product.prodname_registry %} beyond the storage or data transfer included in your account, you will be billed for additional usage.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages @@ -13,72 +13,67 @@ topics: - Packages - Spending limits shortTitle: About billing -ms.openlocfilehash: e75b13f2422ac407264381a4637e763608bc9657 -ms.sourcegitcommit: 58db85219d094c2fb752117361e21eb49965d6ad -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 08/15/2022 -ms.locfileid: '147576987' --- -## 关于 {% data variables.product.prodname_registry %} 的计费 +## About billing for {% data variables.product.prodname_registry %} {% data reusables.package_registry.packages-billing %} -{% data reusables.package_registry.packages-spending-limit-brief %} 有关详细信息,请参阅“[关于支出限制](#about-spending-limits)”。 +{% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)." {% note %} -容器映像存储的计费更新:{% data variables.product.prodname_container_registry %} 的容器映像存储和带宽的免费使用期已经延长。 如果您正在使用 {% data variables.product.prodname_container_registry %} ,您将在开始计费之前至少一个月收到通知,并且会收到您预计要支付多少款项的预估。 有关 {% data variables.product.prodname_container_registry %} 的详细信息,请参阅“[使用容器注册表](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)”。 +**Billing update for container image storage:** The period of free use for container image storage and bandwidth for the {% data variables.product.prodname_container_registry %} has been extended. If you are using {% data variables.product.prodname_container_registry %} you'll be informed at least one month in advance of billing commencing and you'll be given an estimate of how much you should expect to pay. For more information about the {% data variables.product.prodname_container_registry %}, see "[Working with the Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)." {% endnote %} -{% ifversion ghec %} 如果通过 Microsoft 企业协议购买了 {% data variables.product.prodname_enterprise %},则可以将 Azure 订阅 ID 连接到企业帐户,以启用和支付超出额度的 {% data variables.product.prodname_registry %} 使用量,包括帐户。 有关详细信息,请参阅“[将 Azure 订阅连接到企业](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)”。 +{% ifversion ghec %} +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](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)." {% endif %} -数据传输每月都会重置,而存储使用量不重置。 +Data transfer resets every month, while storage usage does not. -产品 | 存储 | 数据传输(每月) +Product | Storage | Data transfer (per month) ------- | ------- | --------- {% data variables.product.prodname_free_user %} | 500MB | 1GB {% data variables.product.prodname_pro %} | 2GB | 10GB -组织的 {% data variables.product.prodname_free_team %} | 500MB | 1GB | +{% data variables.product.prodname_free_team %} for organizations | 500MB | 1GB | {% data variables.product.prodname_team %} | 2GB | 10GB {% data variables.product.prodname_ghe_cloud %} | 50GB | 100GB -如果是 {% data variables.product.prodname_actions %} 触发的,所有传出的数据以及从任何来源传入的数据都是免费的。 当使用 `GITHUB_TOKEN` 登录到 {% data variables.product.prodname_registry %} 时,我们断定你正在使用 {% data variables.product.prodname_actions %} 下载包。 +All data transferred out, when triggered by {% data variables.product.prodname_actions %}, and data transferred in from any source is free. We determine you are downloading packages using {% data variables.product.prodname_actions %} when you log in to {% data variables.product.prodname_registry %} using a `GITHUB_TOKEN`. -||已托管|自托管| +||Hosted|Self-Hosted| |-|-|-| -|使用 `GITHUB_TOKEN` 进行访问|免费|免费| -|使用个人访问令牌访问|免费|$| +|Access using a `GITHUB_TOKEN`|Free|Free| +|Access using a {% data variables.product.pat_generic %}|Free|$| -存储使用情况与 {% data variables.product.prodname_actions %} 为您的帐户所拥有的仓库产生的构件共享。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_actions %} 的计费](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)”。 +Storage usage is shared with build artifacts produced by {% data variables.product.prodname_actions %} for repositories owned by your account. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)." -{% data variables.product.prodname_dotcom %} 向拥有其中发布软件包的仓库的帐户收取使用费。 如果你的帐户使用量超过这些限制,并且你设定的支出限额超过 0 美元,那么你将每天为每 GB 存储量支付 0.25 美元,每 GB 数据传输量支付 0.50 美元。 +{% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where the package is published. If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and $0.50 USD per GB of data transfer. -例如,如果您的组织使用 {% data variables.product.prodname_team %},允许无限制的支出,使用了 150GB 的存储量,一个月内还传输了 50GB 的数据,则组织在当月的存储量超限 148GB,数据传输量为 40GB。 超限的存储量费用每天每 GB 为 0.25 美元,总共 37 美元。 超限的数据传输费用每 GB 为 0.50 美元,总共 20 美元。 +For example, if your organization uses {% data variables.product.prodname_team %}, allows unlimited spending, uses 150GB of storage, and has 50GB of data transfer out during a month, the organization would have overages of 148GB for storage and 40GB for data transfer for that month. The storage overage would cost $0.008 USD per GB per day or approximately $37 USD for a 31-day month. The overage for data transfer would cost $0.50 USD per GB or $20 USD. {% data reusables.dotcom_billing.pricing_calculator.pricing_cal_packages %} -到月底,{% data variables.product.prodname_dotcom %} 会将您的数据传输舍入到最接近的 GB。 +At the end of the month, {% data variables.product.prodname_dotcom %} rounds your data transfer to the nearest GB. -{% data variables.product.prodname_dotcom %} 根据每个月的小时用量计算该月的存储使用量。 例如,如果在三月的 10 天内使用 3 GB 的存储,在三月的 21 天使用 12 GB 的存储,则存储使用量为: +{% data variables.product.prodname_dotcom %} calculates your storage usage for each month based on hourly usage during that month. For example, if you use 3 GB of storage for 10 days of March and 12 GB for 21 days of March, your storage usage would be: -- 3 GB x 10 天 x(每天 24 小时)= 720 GB-小时 -- 12 GB x 21 天 x(每天 24 小时)= 6,048 GB-小时 -- 720 GB-小时 + 6,048 GB-小时 = 6,768 GB-小时 -- 6,768 GB-小时 / (每月 744 小时) = 9.0967 GB-月 +- 3 GB x 10 days x (24 hours per day) = 720 GB-Hours +- 12 GB x 21 days x (24 hours per day) = 6,048 GB-Hours +- 720 GB-Hours + 6,048 GB-Hours = 6,768 GB-Hours +- 6,768 GB-Hours / (744 hours per month) = 9.0967 GB-Months -到月底,{% data variables.product.prodname_dotcom %} 会将您的存储量舍入到最接近的 MB。 因此,三月的存储使用量为 9.097 GB。 +At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB. Therefore, your storage usage for March would be 9.097 GB. -您的 {% data variables.product.prodname_registry %} 使用将共用帐户的现有计费日期、付款方式和收据。 {% data reusables.dotcom_billing.view-all-subscriptions %} +Your {% data variables.product.prodname_registry %} usage shares your account's existing billing date, payment method, and receipt. {% data reusables.dotcom_billing.view-all-subscriptions %} {% data reusables.user-settings.context_switcher %} -## 关于支出限制 +## About spending limits {% data reusables.package_registry.packages-spending-limit-detailed %} -有关管理和更改帐户支出限制的信息,请参阅“[管理 {% data variables.product.prodname_registry %} 的支出限制](/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages)”。 +For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages)." {% data reusables.dotcom_billing.actions-packages-unpaid-account %} diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md index 66f69023ed..8193a24ee4 100644 --- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md +++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md @@ -1,6 +1,6 @@ --- -title: 关于企业的计费 -intro: '您可以在查看您在 {% data variables.product.prodname_dotcom_the_website %} 上的{% ifversion ghec or ghes %}企业帐户{% endif %}的帐单信息。' +title: About billing for your enterprise +intro: 'You can view billing information for your enterprise{% ifversion ghec or ghes %} account on {% data variables.product.prodname_dotcom_the_website %}{% endif %}.' redirect_from: - /admin/overview/managing-billing-for-your-enterprise - /enterprise/admin/installation/managing-billing-for-github-enterprise @@ -14,69 +14,68 @@ type: overview topics: - Enterprise shortTitle: Billing for your enterprise -ms.openlocfilehash: 1b048c16293b7183636bc383ca926c4e5c7f0bd2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147573407' --- -## 关于企业的计费 + +## About billing for your enterprise {% ifversion ghae %} -{% data reusables.github-ae.about-billing %} 每天一次,{% data variables.product.prodname_dotcom %} 将计算拥有企业许可证的用户数目。 {% data variables.product.company_short %} 对每个许可的用户计费,而不论用户当天是否登录 {% data variables.product.prodname_ghe_managed %}。 +{% data reusables.github-ae.about-billing %} Once per day, {% data variables.product.prodname_dotcom %} will count the number of users with a license for your enterprise. {% data variables.product.company_short %} bills you for each licensed user regardless of whether the user logged into {% data variables.product.prodname_ghe_managed %} that day. -对于商业区,每个用户每天的价格是 1.2580645161 美元。 在 31 天的月份中,每个用户的每月费用为 39 美元。 对于天数较少的月份,每月费用较低。 每个计费月份在日历月第一天的固定时间开始。 +For commercial regions, the price per user per day is $1.2580645161. For 31-day months, the monthly cost for each user is $39. For months with fewer days, the monthly cost is lower. Each billing month begins at a fixed time on the first day of the calendar month. -如果月中添加许可用户,则该用户将仅包含在其拥有许可证的天数的计数中。 当您移除授权用户时,该用户将在计数中保留到该月底。 因此,如果在一个月中添加用户然后在该月移除该用户,则用户将从添加之日到月底包含在计数中。 如果您在用户被移除的同一个月内重新添加该用户,不会有额外的费用。 +If you add a licensed user mid-month, that user will only be included in the count for the days they have a license. When you remove a licensed user, that user will remain in the count until the end of that month. Therefore, if you add a user mid-month and later remove the user in the same month, the user will be included in the count from the day the user was added through the end of the month. There is no additional cost if you re-add a user during the same month the user was removed. -例如,以下是在不同日期具有许可证的用户的费用。 +For example, here are the costs for users with licenses on different dates. -用户 | 许可日期 | 计入的天数 | Cost +User | License dates | Counted days | Cost ---- | ------------ | ------- | ----- -@octocat | 1 月 1 日至 1 月 31 日 | 31 | $39 -@robocat | 2 月 1 日至 2 月 28 日 | 28 | $35.23 -@devtocat | 1 月 15 日至 1 月 31 日 | 17 | $21.39 -@doctocat | 1 月 1 日至 1 月 15 日 | 31 | $39 -@prodocat | 1 月 7 日至 1 月 15 日 | 25 | $31.45 -@monalisa | 1 月 1 日至 1 月 7 日,
1 月 15 日至 1 月 31 日 | 31 | $39 +@octocat | January 1 - January 31 | 31 | $39 +@robocat | February 1 - February 28 | 28 | $35.23 +@devtocat | January 15 - January 31 | 17 | $21.39 +@doctocat | January 1 - January 15 | 31 | $39 +@prodocat | January 7 - January 15 | 25 | $31.45 +@monalisa | January 1 - January 7,
January 15 - January 31 | 31 | $39 -{% data variables.product.prodname_ghe_managed %} 的每个实例至少 500 个用户。 {% data variables.product.company_short %} 按每个实例至少 500 个用户计费,即使当天拥有许可证的用户少于 500 个也一样。 +{% data variables.product.prodname_ghe_managed %} has a 500-user minimum per instance. {% data variables.product.company_short %} bills you for a minimum of 500 users per instance, even if there are fewer than 500 users with a license that day. -可在 [Azure 帐户门户中](https://portal.azure.com)查看当前使用情况。 +You can see your current usage in your [Azure account portal](https://portal.azure.com). {% elsif ghec or ghes %} {% ifversion ghec %} -当你在 {% data variables.product.product_location %} 上使用企业帐户时,企业帐户是企业内所有计费的中心点,包括企业拥有的组织。 +When you use an enterprise account on {% data variables.location.product_location %}, the enterprise account is the central point for all billing within your enterprise, including the organizations that your enterprise owns. -如果将 {% data variables.product.product_name %} 用于单个组织,但尚未拥有企业帐户,请创建企业帐户并添加组织。 有关详细信息,请参阅“[创建企业帐户](/admin/overview/creating-an-enterprise-account)”。 +If you use {% data variables.product.product_name %} with an individual organization and do not yet have an enterprise account, you create an enterprise account and add your organization. For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)." -{% data variables.product.company_short %} 每月对你的企业帐户的许可席位总数以及你与 {% data variables.product.prodname_ghe_cloud %} 一起使用的任何其他服务进行计费(如 {% data variables.product.prodname_actions %} 分钟)。 如果在 {% data variables.product.product_name %} 上使用独立组织,则会在组织级别按所有使用量计费。 有关帐单的许可证席位的详细信息,请参阅“[关于每用户定价](/billing/managing-billing-for-your-github-account/about-per-user-pricing)”。 +{% data variables.product.company_short %} bills monthly for the total number of licensed seats for your enterprise account, as well as any additional services you use with {% data variables.product.prodname_ghe_cloud %}, such as {% data variables.product.prodname_actions %} minutes. If you use a standalone organization on {% data variables.product.product_name %}, you'll be billed at the organization level for all usage. For more information your bill's license seats, see "[About per-user pricing](/billing/managing-billing-for-your-github-account/about-per-user-pricing)." {% elsif ghes %} -{% data variables.product.product_location %} 上的每个用户都会占用许可证上的一个席位。 {% data variables.product.company_short %} 按月收取许可证上消耗的席位总数的费用。 +Each user on {% data variables.location.product_location %} consumes a seat on your license. {% data variables.product.company_short %} bills monthly for the total number of seats consumed on your license. {% endif %} -{% ifversion ghec %}对于拥有企业帐户的 {% data variables.product.prodname_ghe_cloud %} 客户,{% data variables.product.company_short %} 通过 {% data variables.product.prodname_dotcom_the_website %} 上的企业帐户计费。 对于已开票的客户,每个{% elsif ghes %}对于已开票的 {% data variables.product.prodname_enterprise %} 客户,{% data variables.product.company_short %} 通过 {% data variables.product.prodname_dotcom_the_website %} 上的企业帐户计费。 每张{% endif %}发票都包含所有已付费的 {% data variables.product.prodname_dotcom_the_website %} 服务和任何 {% data variables.product.prodname_ghe_server %} 实例的单笔帐单费用。 有关{% ifversion ghes %}许可、使用情况和发票{% elsif ghec %}使用情况和发票{% endif %}的详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的以下内容{% ifversion ghes %}。{% else %}{% endif %} +{% ifversion ghec %}For {% data variables.product.prodname_ghe_cloud %} customers with an enterprise account, {% data variables.product.company_short %} bills through your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. For invoiced customers, each{% elsif ghes %}For invoiced {% data variables.product.prodname_enterprise %} customers, {% data variables.product.company_short %} bills through an enterprise account on {% data variables.product.prodname_dotcom_the_website %}. Each{% endif %} invoice includes a single bill charge for all of your paid {% data variables.product.prodname_dotcom_the_website %} services and any {% data variables.product.prodname_ghe_server %} instances. For more information about {% ifversion ghes %}licensing, usage, and invoices{% elsif ghec %}usage and invoices{% endif %}, see the following{% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %} {%- ifversion ghes %} -- “[关于每用户定价](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/about-per-user-pricing)”{%- endif %} -- “[查看企业帐户的订阅和使用情况]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)” -- “[管理企业的发票]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise)” +- "[About per-user pricing](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/about-per-user-pricing)" +{%- endif %} +- "[Viewing the subscription and usage for your enterprise account]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" +- "[Managing invoices for your enterprise]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise)" -您在 {% data variables.product.prodname_dotcom_the_website %} 上的企业帐户的管理员可以访问和管理企业的帐单。 有关详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[企业中的角色]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise){% ifversion ghec %}."{% elsif ghes %}”。{% endif %} +Administrators for your enterprise account on {% data variables.product.prodname_dotcom_the_website %} can access and manage billing for the enterprise. For more information, see "[Roles in an enterprise]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise){% ifversion ghec %}."{% elsif ghes %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %} -{% ifversion ghec %} {% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} 有关详细信息,请参阅“[将 Azure 订阅连接到企业](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)”。 +{% ifversion ghec %} +{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)." {% endif %} -{% ifversion ghes %} {% data reusables.billing.ghes-with-no-enterprise-account %} {% endif %} +{% ifversion ghes %} +{% data reusables.billing.ghes-with-no-enterprise-account %} +{% endif %} {% endif %} -## 延伸阅读 +## Further reading -- “[关于企业帐户](/admin/overview/about-enterprise-accounts)” +- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)" diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md index 0253200ccb..5f06513eaa 100644 --- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md +++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md @@ -86,7 +86,7 @@ In addition to licensed seats, your bill may include other charges, such as {% d {% data variables.product.company_short %} does not bill for any of the following accounts: -- {% data variables.product.prodname_managed_users_caps %} that are suspended +- {% data variables.enterprise.prodname_managed_users_caps %} that are suspended - Enterprise owners who are not a member or owner of at least one organization in the enterprise - Enterprise billing managers - Billing managers for individual organizations diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md index 4d1f0fcdc8..a78c974347 100644 --- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md +++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md @@ -1,6 +1,6 @@ --- -title: 降级 GitHub 订阅 -intro: '您可以随时降级 {% data variables.product.product_location %} 上任何类型的帐户的订阅。' +title: Downgrading your GitHub subscription +intro: 'You can downgrade the subscription for any type of account on {% data variables.location.product_location %} at any time.' redirect_from: - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription - /articles/downgrading-your-personal-account-s-billing-plan @@ -27,80 +27,76 @@ topics: - Repositories - User account shortTitle: Downgrade subscription -ms.openlocfilehash: b709c94090c1f79bfd8e16cc7df2c943d64b5aa7 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145084489' --- -## 降级您的 {% data variables.product.product_name %} 订阅 +## Downgrading your {% data variables.product.product_name %} subscription -降级个人帐户或组织的订阅时,定价和帐户功能更改将在下一个帐单日期生效。 对付费个人帐户或组织订阅的更改不影响其他付费 {% data variables.product.prodname_dotcom %} 功能的订阅或付款。 有关详细信息,请参阅“[升级或降级如何影响计费流程?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)”。 +When you downgrade your personal account or organization's subscription, pricing and account feature changes take effect on your next billing date. Changes to your paid personal account or organization subscription does not affect subscriptions or payments for other paid {% data variables.product.prodname_dotcom %} features. For more information, see "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)." -## 降级个人帐户的订阅 +## Downgrading your personal account's subscription -如果将你的个人帐户从 {% data variables.product.prodname_pro %} 降级为 {% data variables.product.prodname_free_user %},该帐户将失去对专用存储库中高级代码评审工具的访问权限。 {% data reusables.gated-features.more-info %} +If you downgrade your personal account from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, the account will lose access to advanced code review tools on private repositories. {% data reusables.gated-features.more-info %} -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.billing_plans %} -1. 在“当前计划”下,使用“编辑”下拉列表,然后单击“降级为免费” 。 - ![“降级为免费”按钮](/assets/images/help/billing/downgrade-to-free.png) -5. 阅读有关个人帐户在下一个计费日期将无法再使用的功能的信息,然后单击“我了解,继续降级”。 - ![“继续降级”按钮](/assets/images/help/billing/continue-with-downgrade.png) +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.billing_plans %} +1. Under "Current plan", use the **Edit** drop-down and click **Downgrade to Free**. + ![Downgrade to free button](/assets/images/help/billing/downgrade-to-free.png) +5. Read the information about the features your personal account will no longer have access to on your next billing date, then click **I understand. Continue with downgrade**. + ![Continue with downgrade button](/assets/images/help/billing/continue-with-downgrade.png) -如果您在私有仓库中发布了 {% data variables.product.prodname_pages %} 站点,并添加了自定义域,在从 {% data variables.product.prodname_pro %} 降级至 {% data variables.product.prodname_free_user %} 前,请删除或更新您的 DNS 记录,以避免域接管的风险。 有关详细信息,请参阅“[为你的 {% data variables.product.prodname_pages %} 站点管理自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)”。 +If you published a {% data variables.product.prodname_pages %} site in a private repository and added a custom domain, remove or update your DNS records before downgrading from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, 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)." -## 降级组织的订阅 +## Downgrading your organization's subscription {% data reusables.dotcom_billing.org-billing-perms %} -如果将您的组织从 {% data variables.product.prodname_team %} 降级到 {% data variables.product.prodname_free_team %},该帐户将失去对团队高级协作和管理工具的访问权限。 +If you downgrade your organization from {% data variables.product.prodname_team %} to {% data variables.product.prodname_free_team %} for an organization, the account will lose access to advanced collaboration and management tools for teams. -如果将您的组织从 {% data variables.product.prodname_ghe_cloud %} 降级到 {% data variables.product.prodname_team %} 或 {% data variables.product.prodname_free_team %},该帐户将失去对高级安全性、合规性和部署控件的访问权限。 {% data reusables.gated-features.more-info %} +If you downgrade your organization from {% data variables.product.prodname_ghe_cloud %} to {% data variables.product.prodname_team %} or {% data variables.product.prodname_free_team %}, the account will lose access to advanced security, compliance, and deployment controls. {% data reusables.gated-features.more-info %} {% note %} -注意:如果你目前正在试用 {% data variables.product.prodname_ghe_cloud %},并且在试用结束前没有购买 {% data variables.product.prodname_enterprise %},你的组织将自动降级为 {% data variables.product.prodname_free_team %} 或 {% data variables.product.prodname_team %}。 有关详细信息,请参阅“[设置试用版 {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)”。 +**Note:** If you're currently trialing {% data variables.product.prodname_ghe_cloud %}, and you don't purchase {% data variables.product.prodname_enterprise %} before the trial ends, your organization will be automatically downgraded to {% data variables.product.prodname_free_team %} or {% data variables.product.prodname_team %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)." {% endnote %} {% data reusables.organizations.billing-settings %} -1. 在“当前计划”下,使用“修改”下拉菜单并单击所需的降级选项。 - ![“降级”按钮](/assets/images/help/billing/downgrade-option-button.png) {% data reusables.dotcom_billing.confirm_cancel_org_plan %} +1. Under "Current plan", use the **Edit** drop-down and click the downgrade option you want. + ![Downgrade button](/assets/images/help/billing/downgrade-option-button.png) +{% data reusables.dotcom_billing.confirm_cancel_org_plan %} -## 降级采用传统的按仓库定价模式的组织订阅 +## Downgrading an organization's subscription with legacy per-repository pricing {% data reusables.dotcom_billing.org-billing-perms %} -{% data reusables.dotcom_billing.switch-legacy-billing %} 有关详细信息,请参阅“[将组织从每存储库定价切换到每用户定价](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)”。 +{% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[Switching your organization from per-repository to per-user pricing](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)." {% data reusables.organizations.billing-settings %} -5. 在“订阅”下,选择“编辑”下拉菜单,然后单击“编辑计划”。 - ![“编辑计划”下拉菜单](/assets/images/help/billing/edit-plan-dropdown.png) -1. 在“账单/计划”下,单击要更改的计划旁边的“降级”。 - ![降级按钮](/assets/images/help/billing/downgrade-plan-option-button.png) -1. 输入降级帐户的原因,然后单击“降级计划”。 - ![降级原因文本框和降级按钮](/assets/images/help/billing/downgrade-plan-button.png) +5. Under "Subscriptions", select the "Edit" drop-down, and click **Edit plan**. + ![Edit Plan dropdown](/assets/images/help/billing/edit-plan-dropdown.png) +1. Under "Billing/Plans", next to the plan you want to change, click **Downgrade**. + ![Downgrade button](/assets/images/help/billing/downgrade-plan-option-button.png) +1. Enter the reason you're downgrading your account, then click **Downgrade plan**. + ![Text box for downgrade reason and downgrade button](/assets/images/help/billing/downgrade-plan-button.png) -## 从组织删除付费席位 +## Removing paid seats from your organization -要减少组织使用的付费席位数,您可以从组织中删除成员,或将成员转换为外部协作者并仅给予他们公共仓库的访问权限。 有关详细信息,请参阅: -- [从组织中删除成员](/articles/removing-a-member-from-your-organization) -- [将组织成员转换为外部协作者](/articles/converting-an-organization-member-to-an-outside-collaborator) -- [管理个人对组织存储库的访问](/articles/managing-an-individual-s-access-to-an-organization-repository) +To reduce the number of paid seats your organization uses, you can remove members from your organization or convert members to outside collaborators and give them access to only public repositories. For more information, see: +- "[Removing a member from your organization](/articles/removing-a-member-from-your-organization)" +- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)" +- "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)" {% data reusables.organizations.billing-settings %} -1. 在“当前计划”下,使用“编辑”下拉列表,然后单击“删除席位” 。 - ![“删除席位”下拉菜单](/assets/images/help/billing/remove-seats-dropdown.png) -1. 在“Remove seats”(删除席位)下,选择要降级的席位数。 - ![“删除席位”选项](/assets/images/help/billing/remove-seats-amount.png) -1. 查看有关下一个计费日期的新付款的信息,然后单击“删除席位”。 - ![“删除席位”按钮](/assets/images/help/billing/remove-seats-button.png) +1. Under "Current plan", use the **Edit** drop-down and click **Remove seats**. + ![remove seats dropdown](/assets/images/help/billing/remove-seats-dropdown.png) +1. Under "Remove seats", select the number of seats you'd like to downgrade to. + ![remove seats option](/assets/images/help/billing/remove-seats-amount.png) +1. Review the information about your new payment on your next billing date, then click **Remove seats**. + ![remove seats button](/assets/images/help/billing/remove-seats-button.png) -## 延伸阅读 +## Further reading -- “[{% data variables.product.prodname_dotcom %} 的产品](/articles/github-s-products)” -- “[升级或降级如何影响计费过程?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)” -- “[关于 {% data variables.product.prodname_dotcom %} 的计费](/articles/about-billing-on-github)”。 -- [关于每用户定价](/articles/about-per-user-pricing) +- "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)" +- "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)" +- "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)." +- "[About per-user pricing](/articles/about-per-user-pricing)" diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md index 65f3314a94..9d40ff9312 100644 --- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md +++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md @@ -1,6 +1,6 @@ --- -title: 升级 GitHub 订阅 -intro: '您可以随时升级 {% data variables.product.product_location %} 上任何类型的帐户的订阅。' +title: Upgrading your GitHub subscription +intro: 'You can upgrade the subscription for any type of account on {% data variables.location.product_location %} at any time.' miniTocMaxHeadingLevel: 3 redirect_from: - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription @@ -30,69 +30,83 @@ topics: - Upgrades - User account shortTitle: Upgrade your subscription -ms.openlocfilehash: 47426fa211521a166738c5a9bb00edddfc2556f2 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145084475' --- -## 关于订阅升级 + +## About subscription upgrades {% data reusables.accounts.accounts-billed-separately %} -升级帐户的订阅时,升级将更改仅适用于该帐户的付费功能,而不会更改您使用的任何其他帐户。 +When you upgrade the subscription for an account, the upgrade changes the paid features available for that account only, and not any other accounts you use. -## 升级个人帐户的订阅 +## Upgrading your personal account's subscription -你可以将个人帐户从 {% data variables.product.prodname_free_user %} 升级到 {% data variables.product.prodname_pro %},以便在个人帐户拥有的私有存储库上获取高级代码评审工具。 升级您的个人帐户不会影响您可能管理的任何组织或这些组织拥有的存储库。 {% data reusables.gated-features.more-info %} +You can upgrade your personal account from {% data variables.product.prodname_free_user %} to {% data variables.product.prodname_pro %} to get advanced code review tools on private repositories owned by your personal account. Upgrading your personal account does not affect any organizations you may manage or repositories owned by those organizations. {% data reusables.gated-features.more-info %} -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.billing_plans %} -1. 在“当前计划”旁边,单击“升级”。 - ![“升级”按钮](/assets/images/help/billing/settings_billing_user_upgrade.png) -2. 在“比较计划”页上的“Pro”下,单击“升级到 Pro”。 -{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} {% data reusables.dotcom_billing.show-plan-details %} {% data reusables.dotcom_billing.enter-billing-info %} {% data reusables.dotcom_billing.enter-payment-info %} {% data reusables.dotcom_billing.finish_upgrade %} +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.billing_plans %} +1. Next to "Current plan", click **Upgrade**. + ![Upgrade button](/assets/images/help/billing/settings_billing_user_upgrade.png) +2. Under "Pro" on the "Compare plans" page, click **Upgrade to Pro**. +{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} +{% data reusables.dotcom_billing.show-plan-details %} +{% data reusables.dotcom_billing.enter-billing-info %} +{% data reusables.dotcom_billing.enter-payment-info %} +{% data reusables.dotcom_billing.finish_upgrade %} -## 管理组织的订阅 +## Managing your organization's subscription -您可以将组织的订阅升级到其他产品,为现有产品添加席位,或者从每存储库定价切换到每用户定价。 +You can upgrade your organization's subscription to a different product, add seats to your existing product, or switch from per-repository to per-user pricing. -### 升级组织的订阅 +### Upgrading your organization's subscription -您可以将组织从 {% data variables.product.prodname_free_team %} 升级到 {% data variables.product.prodname_team %},以访问团队的高级协作和管理工具,也可以将组织升级到 {% data variables.product.prodname_ghe_cloud %} 以使用更多的安全性、合规性和部署控件。 升级组织不会影响您的个人帐户或您的个人帐户拥有的存储库。 {% data reusables.gated-features.more-info-org-products %} +You can upgrade your organization from {% data variables.product.prodname_free_team %} for an organization to {% data variables.product.prodname_team %} to access advanced collaboration and management tools for teams, or upgrade your organization to {% data variables.product.prodname_ghe_cloud %} for additional security, compliance, and deployment controls. Upgrading an organization does not affect your personal account or repositories owned by your personal account. {% data reusables.gated-features.more-info-org-products %} {% data reusables.dotcom_billing.org-billing-perms %} -{% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.upgrade_org %} {% data reusables.dotcom_billing.choose_org_plan %} {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} {% data reusables.dotcom_billing.show-plan-details %} {% data reusables.dotcom_billing.enter-payment-info %} {% data reusables.dotcom_billing.owned_by_business %} {% data reusables.dotcom_billing.finish_upgrade %} +{% data reusables.organizations.billing-settings %} +{% data reusables.dotcom_billing.upgrade_org %} +{% data reusables.dotcom_billing.choose_org_plan %} +{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} +{% data reusables.dotcom_billing.show-plan-details %} +{% data reusables.dotcom_billing.enter-payment-info %} +{% data reusables.dotcom_billing.owned_by_business %} +{% data reusables.dotcom_billing.finish_upgrade %} -### 使用 {% data variables.product.prodname_ghe_cloud %} 的组织的后续步骤 +### Next steps for organizations using {% data variables.product.prodname_ghe_cloud %} -如果您已将组织升级到 {% data variables.product.prodname_ghe_cloud %},便可设置组织的身份和访问管理。 有关详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[管理组织的 SAML 单一登录](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization){% ifversion fpt %}”。{% else %}."{% endif %} +If you upgraded your organization to {% data variables.product.prodname_ghe_cloud %}, you can set up identity and access management for your organization. For more information, see "[Managing SAML single sign-on for your organization](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} -如果想要将企业帐户与 {% data variables.product.prodname_ghe_cloud %} 一起使用,请联系 {% data variables.contact.contact_enterprise_sales %}。 有关详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[关于企业帐户](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}”。{% else %}."{% endif %} +If you'd like to use an enterprise account with {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} -### 将席位添加到您的组织 +### Adding seats to your organization -如果希望其他用户能够访问您 {% data variables.product.prodname_team %} 组织的私有仓库,您可以随时购买更多席位。 - -{% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.add-seats %} {% data reusables.dotcom_billing.number-of-seats %} {% data reusables.dotcom_billing.confirm-add-seats %} - -### 将组织从按仓库定价切换为按用户定价 - -{% data reusables.dotcom_billing.switch-legacy-billing %} 有关详细信息,请参阅“[关于每用户定价](/articles/about-per-user-pricing)”。 +If you'd like additional users to have access to your {% data variables.product.prodname_team %} organization's private repositories, you can purchase more seats anytime. {% data reusables.organizations.billing-settings %} -5. 在计划名称的右侧,使用“编辑”下拉菜单,并选择“编辑计划” 。 - ![“编辑”下拉菜单](/assets/images/help/billing/per-user-upgrade-button.png) -6. 在“适用于团队的高级工具”的右侧,单击“立即升级”。 - ![“立即升级”按钮](/assets/images/help/billing/per-user-upgrade-now-button.png) {% data reusables.dotcom_billing.choose_org_plan %} {% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} {% data reusables.dotcom_billing.owned_by_business %} {% data reusables.dotcom_billing.finish_upgrade %} +{% data reusables.dotcom_billing.add-seats %} +{% data reusables.dotcom_billing.number-of-seats %} +{% data reusables.dotcom_billing.confirm-add-seats %} -## 升级时对 500 错误进行故障排除 +### Switching your organization from per-repository to per-user pricing + +{% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." + +{% data reusables.organizations.billing-settings %} +5. To the right of your plan name, use the **Edit** drop-down menu, and select **Edit plan**. + ![Edit drop-down menu](/assets/images/help/billing/per-user-upgrade-button.png) +6. To the right of "Advanced tools for teams", click **Upgrade now**. + ![Upgrade now button](/assets/images/help/billing/per-user-upgrade-now-button.png) +{% data reusables.dotcom_billing.choose_org_plan %} +{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %} +{% data reusables.dotcom_billing.owned_by_business %} +{% data reusables.dotcom_billing.finish_upgrade %} + +## Troubleshooting a 500 error when upgrading {% data reusables.dotcom_billing.500-error %} -## 延伸阅读 +## Further reading -- “[{% data variables.product.prodname_dotcom %} 的产品](/articles/github-s-products)” -- “[升级或降级如何影响计费过程?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)” -- “[关于 {% data variables.product.prodname_dotcom %} 的计费](/articles/about-billing-on-github)”。 +- "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)" +- "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)" +- "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)." diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md index e9eea5a2f7..aba1e9288f 100644 --- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -1,6 +1,6 @@ --- title: Viewing the subscription and usage for your enterprise account -intro: 'You can view the current {% ifversion ghec %}subscription, {% endif %}license usage{% ifversion ghec %}, invoices, payment history, and other billing information{% endif %} for {% ifversion ghec %}your enterprise account{% elsif ghes %}{% data variables.product.product_location_enterprise %}{% endif %}.' +intro: 'You can view the current {% ifversion ghec %}subscription, {% endif %}license usage{% ifversion ghec %}, invoices, payment history, and other billing information{% endif %} for {% ifversion ghec %}your enterprise account{% elsif ghes %}{% data variables.location.product_location_enterprise %}{% endif %}.' permissions: 'Enterprise owners {% ifversion ghec %}and billing managers {% endif %}can access and manage all billing settings for enterprise accounts.' redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account @@ -17,7 +17,7 @@ shortTitle: View subscription & usage ## About billing for enterprise accounts -You can view an overview of {% ifversion ghec %}your subscription and paid{% elsif ghes %}the license{% endif %} usage for {% ifversion ghec %}your{% elsif ghes %}the{% endif %} enterprise account on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.{% ifversion ghec %} {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)."{% endif %} +You can view an overview of {% ifversion ghec %}your subscription and paid{% elsif ghes %}the license{% endif %} usage for {% ifversion ghec %}your{% elsif ghes %}the{% endif %} enterprise account on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.location.product_location %}{% endif %}.{% ifversion ghec %} {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)."{% endif %} For invoiced {% data variables.product.prodname_enterprise %} customers{% ifversion ghes %} who use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}{% endif %}, each invoice includes details about billed services for all products. For example, in addition to your usage for {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, you may have usage for {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghec %}, {% elsif ghes %}. You may also have usage on {% data variables.product.prodname_dotcom_the_website %}, like {% endif %}paid licenses in organizations outside of your enterprise account, data packs for {% data variables.large_files.product_name_long %}, or subscriptions to apps in {% data variables.product.prodname_marketplace %}. For more information about invoices, see "[Managing invoices for your enterprise]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise){% ifversion ghec %}."{% elsif ghes %}" in the {% data variables.product.prodname_dotcom_the_website %} documentation.{% endif %} diff --git a/translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md b/translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md index a320099932..af80bbb3a1 100644 --- a/translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md +++ b/translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md @@ -1,6 +1,6 @@ --- -title: 关于包含 GitHub Enterprise 的 Visual Studio 订阅 -intro: '您可以通过 Microsoft 的组合服务授予团队中的 {% data variables.product.prodname_vs %} 订阅者访问 {% data variables.product.prodname_enterprise %}。' +title: About Visual Studio subscriptions with GitHub Enterprise +intro: 'You can give {% data variables.product.prodname_vs %} subscribers on your team access to {% data variables.product.prodname_enterprise %} with a combined offering from Microsoft.' redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/managing-licenses-for-visual-studio-subscription-with-github-enterprise - /github/setting-up-and-managing-your-enterprise/managing-licenses-for-the-github-enterprise-and-visual-studio-bundle @@ -17,40 +17,35 @@ topics: - Enterprise - Licensing shortTitle: About -ms.openlocfilehash: d3adb998cb3413387766753a4dcdbee033df6506 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147052254' --- -## 关于 {% data variables.product.prodname_vss_ghe %} -{% data reusables.enterprise-accounts.vss-ghe-description %} {% data variables.product.prodname_vss_ghe %} 可根据 Microsoft 企业协议的条款从 Microsoft 获得。 有关详细信息,请参阅 {% data variables.product.prodname_vs %} 网站上的 [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/)。 +## About {% data variables.product.prodname_vss_ghe %} -要使用许可的 {% data variables.product.prodname_enterprise %} 部分,每个订阅者在 {% data variables.product.prodname_dotcom_the_website %} 上的个人帐户必须是或成为 {% data variables.product.prodname_dotcom_the_website %} 上的企业所拥有组织的成员。 为此,组织所有者可以通过电子邮件地址邀请新成员加入组织。 订阅者可以使用 {% data variables.product.prodname_dotcom_the_website %} 上的现有个人帐户或新建一个帐户来接受邀请。 +{% data reusables.enterprise-accounts.vss-ghe-description %} {% data variables.product.prodname_vss_ghe %} is available from Microsoft under the terms of the Microsoft Enterprise Agreement. For more information, see [{% data variables.product.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/) on the {% data variables.product.prodname_vs %} website. -有关设置 {% data variables.product.prodname_vss_ghe %} 的详细信息,请参阅“[设置 {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise)”。 +To use the {% data variables.product.prodname_enterprise %} portion of the license, each subscriber's personal account on {% data variables.product.prodname_dotcom_the_website %} must be or become a member of an organization owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}. To accomplish this, organization owners can invite new members to an organization by email address. The subscriber can accept the invitation with an existing personal account on {% data variables.product.prodname_dotcom_the_website %} or create a new account. -## 关于 {% data variables.product.prodname_vss_ghe %} 的许可证 +For more information about the setup of {% data variables.product.prodname_vss_ghe %}, see "[Setting up {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise)." -将 {% data variables.product.prodname_vss_ghe %} 许可证分配给订阅者后,订阅者将使用 {% data variables.product.prodname_dotcom_the_website %} 上的个人帐户加入你企业中的组织,从而使用该许可证的 {% data variables.product.prodname_enterprise %} 部分。 如果 {% data variables.product.prodname_dotcom_the_website %} 上的企业成员个人帐户经过认证的电子邮件地址匹配订阅 {% data variables.product.prodname_vs %} 帐户的用户主名 (UPN),则 {% data variables.product.prodname_vs %} 订阅者将自动占用一个 {% data variables.product.prodname_vss_ghe %} 许可。 +## About licenses for {% data variables.product.prodname_vss_ghe %} -您的企业在 {% data variables.product.prodname_dotcom %} 上的许可总数等于任何标准 {% data variables.product.prodname_enterprise %} 许可和包括 {% data variables.product.prodname_dotcom %} 访问权限的 {% data variables.product.prodname_vs %} 订阅许可数量的总和。 如果企业成员的个人帐户与 {% data variables.product.prodname_vs %} 订阅者的电子邮件地址不对应,则该个人帐户占用的许可不适用于 {% data variables.product.prodname_vs %} 订阅者。 +After you assign a license for {% data variables.product.prodname_vss_ghe %} to a subscriber, the subscriber will use the {% data variables.product.prodname_enterprise %} portion of the license by joining an organization in your enterprise with a personal account on {% data variables.product.prodname_dotcom_the_website %}. If the verified email address for the personal account of an enterprise member on {% data variables.product.prodname_dotcom_the_website %} matches the User Primary Name (UPN) for a subscriber to your {% data variables.product.prodname_vs %} account, the {% data variables.product.prodname_vs %} subscriber will automatically consume one license for {% data variables.product.prodname_vss_ghe %}. -有关 {% data variables.product.prodname_enterprise %} 的详细信息,请参阅“[{% data variables.product.company_short %} 的产品](/github/getting-started-with-github/githubs-products#github-enterprise)”。 有关 {% data variables.product.prodname_dotcom_the_website %} 帐户的详细信息,请参阅“[{% data variables.product.prodname_dotcom %} 帐户的类型](/github/getting-started-with-github/types-of-github-accounts)”。 +The total quantity of your licenses for your enterprise on {% data variables.product.prodname_dotcom %} is the sum of any standard {% data variables.product.prodname_enterprise %} licenses and the number of {% data variables.product.prodname_vs %} subscription licenses that include access to {% data variables.product.prodname_dotcom %}. If the personal account for an enterprise member does not correspond with the email address for a {% data variables.product.prodname_vs %} subscriber, the license that the personal account consumes is unavailable for a {% data variables.product.prodname_vs %} subscriber. -您可以在 {% data variables.product.product_location %} 上查看企业可用的 {% data variables.product.prodname_enterprise %} 许可证数量。 待处理的邀请列表包括尚未成为企业中至少一个组织成员的订阅者。 有关详细信息,请参阅“[查看企业帐户的订阅和使用情况](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)”和“[查看企业中的人员](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-and-outside-collaborators)”。 +For more information about {% data variables.product.prodname_enterprise %}, see "[{% data variables.product.company_short %}'s products](/github/getting-started-with-github/githubs-products#github-enterprise)." For more information about accounts on {% data variables.product.prodname_dotcom_the_website %}, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/github/getting-started-with-github/types-of-github-accounts)." + +You can view the number of {% data variables.product.prodname_enterprise %} licenses available to your enterprise on {% data variables.location.product_location %}. The list of pending invitations includes subscribers who are not yet members of at least one organization in your enterprise. For more information, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" and "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-and-outside-collaborators)." {% tip %} -**提示**:如果在“[查看企业帐户的订阅和使用情况](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account#viewing-the-subscription-and-usage-for-your-enterprise-account)”的步骤 6 中下载了包含企业许可证使用情况的 CSV 文件,则“名称”或“配置文件”列缺少值的任何成员尚未接受加入企业内组织的邀请。 +**Tip**: If you download a CSV file with your enterprise's license usage in step 6 of "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account#viewing-the-subscription-and-usage-for-your-enterprise-account)," any members with a missing value for the "Name" or "Profile" columns have not yet accepted an invitation to join an organization within the enterprise. {% endtip %} -您也可以在 {% data variables.product.prodname_vss_admin_portal_with_url %} 中查看对订阅者的待处理 {% data variables.product.prodname_enterprise %} 邀请。 +You can also see pending {% data variables.product.prodname_enterprise %} invitations to subscribers in {% data variables.product.prodname_vss_admin_portal_with_url %}. -## 延伸阅读 +## Further reading -- Microsoft Docs 中的[包含 {% data variables.product.prodname_enterprise %} 的 {% data variables.product.prodname_vs %} 订阅](https://docs.microsoft.com/visualstudio/subscriptions/access-github)。 -- Microsoft Docs 中的[使用 {% data variables.product.prodname_vs %} 或 {% data variables.product.prodname_vscode %} 从 {% data variables.product.prodname_dotcom %} 部署应用](https://docs.microsoft.com/en-us/azure/developer/github/deploy-with-visual-studio) +- [{% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/visualstudio/subscriptions/access-github) in Microsoft Docs +- [Use {% data variables.product.prodname_vs %} or {% data variables.product.prodname_vscode %} to deploy apps from {% data variables.product.prodname_dotcom %}](https://docs.microsoft.com/en-us/azure/developer/github/deploy-with-visual-studio) in Microsoft Docs diff --git a/translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md b/translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md index c9318453ca..41af3a41ef 100644 --- a/translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md +++ b/translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md @@ -1,6 +1,6 @@ --- -title: 使用 GitHub Enterprise 设置 Visual Studio 订阅 -intro: '您的团队订阅 {% data variables.product.prodname_vs %} 还可以获得 {% data variables.product.prodname_enterprise %} 的访问权限。' +title: Setting up Visual Studio subscriptions with GitHub Enterprise +intro: 'Your team''s subscription to {% data variables.product.prodname_vs %} can also provide access to {% data variables.product.prodname_enterprise %}.' versions: ghec: '*' type: how_to @@ -8,67 +8,64 @@ topics: - Enterprise - Licensing shortTitle: Set up -ms.openlocfilehash: 644a106a749a8c8324b6a3e83dcaa72c8ad878b1 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717955' --- -## 关于 {% data variables.product.prodname_vss_ghe %} 的设置 -{% data reusables.enterprise-accounts.vss-ghe-description %} 有关详细信息,请参阅“[关于 {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise)”。 +## About setup of {% data variables.product.prodname_vss_ghe %} -本指南展示团队如何获得 {% data variables.product.prodname_vs %} 订阅者的许可,以及 {% data variables.product.prodname_enterprise %} 使用入门。 +{% data reusables.enterprise-accounts.vss-ghe-description %} For more information, see "[About {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise)." -如果你更喜欢视频,可以观看 Microsoft Visual Studio 的 YouTube 频道上的[使用 {% data variables.product.prodname_vs %} 订阅设置 {% data variables.product.prodname_enterprise %} 许可证](https://www.youtube.com/watch?v=P_zBgp_BE_I)。 +This guide shows you how your team can get {% data variables.product.prodname_vs %} subscribers licensed and started with {% data variables.product.prodname_enterprise %}. -## {% data variables.product.prodname_vss_ghe %} 的角色 +If you prefer video, you can watch [Setting up your {% data variables.product.prodname_enterprise %} licenses with {% data variables.product.prodname_vs %} subscriptions](https://www.youtube.com/watch?v=P_zBgp_BE_I) on +Microsoft Visual Studio's YouTube channel. -在设置 {% data variables.product.prodname_vss_ghe %} 之前,请务必了解此组合产品的角色。 +## Roles for {% data variables.product.prodname_vss_ghe %} -| 角色 | 服务 | 说明 | 详细信息 | +Before setting up {% data variables.product.prodname_vss_ghe %}, it's important to understand the roles for this combined offering. + +| Role | Service | Description | More information | | :- | :- | :- | :- | -| **订阅管理员** | {% data variables.product.prodname_vs %} 订阅 | 为 {% data variables.product.prodname_vs %} 订阅分配许可证的人员 | Microsoft Docs 中的[管理员职责概述](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) | -| **订阅服务器** | {% data variables.product.prodname_vs %} 订阅 | 使用许可证进行 {% data variables.product.prodname_vs %} 订阅的人员 | Microsoft Docs 中的 [Visual Studio 订阅文档](https://docs.microsoft.com/en-us/visualstudio/subscriptions/)。 | -| **企业所有者** | {% data variables.product.prodname_dotcom %} | 在 {% data variables.product.product_location %} 上拥有企业管理员个人帐户的人 | [企业中的角色](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner) | -| **组织所有者** | {% data variables.product.prodname_dotcom %} | 在 {% data variables.product.product_location %} 上拥有团队企业中组织所有者个人帐户的人员 | [组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners) | -| **企业成员** | {% data variables.product.prodname_dotcom %} | 在 {% data variables.product.product_location %} 上拥有企业成员个人帐户的人员 | [企业中的角色](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members) | +| **Subscriptions admin** | {% data variables.product.prodname_vs %} subscription | Person who assigns licenses for {% data variables.product.prodname_vs %} subscription | [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs | +| **Subscriber** | {% data variables.product.prodname_vs %} subscription | Person who uses a license for {% data variables.product.prodname_vs %} subscription | [Visual Studio Subscriptions documentation](https://docs.microsoft.com/en-us/visualstudio/subscriptions/) in Microsoft Docs | +| **Enterprise owner** | {% data variables.product.prodname_dotcom %} | Person who has a personal account that's an administrator of an enterprise on {% data variables.location.product_location %} | "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)" | +| **Organization owner** | {% data variables.product.prodname_dotcom %} | Person who has a personal account that's an owner of an organization in your team's enterprise on {% data variables.location.product_location %} | "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners)" | +| **Enterprise member** | {% data variables.product.prodname_dotcom %} | Person who has a personal account that's a member of an enterprise on {% data variables.location.product_location %} | "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members)" | -## 先决条件 +## Prerequisites -- 团队的 {% data variables.product.prodname_vs %} 订阅必须包含 {% data variables.product.prodname_enterprise %}。 有关详细信息,请参阅 {% data variables.product.prodname_vs %} 网站上的 [{% data variables.product.prodname_vs %} 订阅和权益](https://visualstudio.microsoft.com/subscriptions/)以及 Microsoft 文档中的[管理员职责概述](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities)。 +- Your team's {% data variables.product.prodname_vs %} subscription must include {% data variables.product.prodname_enterprise %}. For more information, see [{% data variables.product.prodname_vs %} Subscriptions and Benefits](https://visualstudio.microsoft.com/subscriptions/) on the {% data variables.product.prodname_vs %} website and + [Overview of admin responsibilities](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft Docs. - - 您的团队必须在 {% data variables.product.product_location %} 上有企业。 如果您不确定您的团队是否拥有企业,请与您的 {% data variables.product.prodname_dotcom %} 管理员联系。 如果您不确定团队中谁负责 {% data variables.product.prodname_dotcom %},请联系 {% data variables.contact.contact_enterprise_sales %}。 有关详细信息,请参阅“[关于企业帐户](/admin/overview/about-enterprise-accounts)”。 + - Your team must have an enterprise on {% data variables.location.product_location %}. If you're not sure whether your team has an enterprise, contact your {% data variables.product.prodname_dotcom %} administrator. If you're not sure who on your team is responsible for {% data variables.product.prodname_dotcom %}, contact {% data variables.contact.contact_enterprise_sales %}. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)." -## 设置 {% data variables.product.prodname_vss_ghe %} +## Setting up {% data variables.product.prodname_vss_ghe %} -要设置 {% data variables.product.prodname_vss_ghe %},团队成员必须完成以下任务。 +To set up {% data variables.product.prodname_vss_ghe %}, members of your team must complete the following tasks. -一个人或许能够完成任务,因为此人具有所有角色,但您可能需要与多个人协调任务。 有关详细信息,请参阅“[{% data variables.product.prodname_vss_ghe %} 的角色](#roles-for-visual-studio-subscriptions-with-github-enterprise)”。 +One person may be able to complete the tasks because the person has all of the roles, but you may need to coordinate the tasks with multiple people. For more information, see "[Roles for {% data variables.product.prodname_vss_ghe %}](#roles-for-visual-studio-subscriptions-with-github-enterprise)." -1. 企业所有者必须在 {% data variables.product.product_location %} 上创建至少一个组织。 有关详细信息,请参阅“[将组织添加到企业](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)”。 +1. An enterprise owner must create at least one organization in your enterprise on {% data variables.location.product_location %}. For more information, see "[Adding organizations to your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)." -1. 订阅管理员必须将 {% data variables.product.prodname_vs %} 许可证分配给 {% data variables.product.prodname_vss_admin_portal_with_url %} 中的订阅者。 更多信息请参阅 Microsoft 文档中的 [{% data variables.product.prodname_vs %} 订阅管理员门户概述](https://docs.microsoft.com/en-us/visualstudio/subscriptions/using-admin-portal)和[在 {% data variables.product.prodname_vs %} 订阅管理员门户中分配 {% data variables.product.prodname_vs %} 许可证](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-license)。 +1. The subscription admin must assign a license for {% data variables.product.prodname_vs %} to a subscriber in {% data variables.product.prodname_vss_admin_portal_with_url %}. For more information, see [Overview of the {% data variables.product.prodname_vs %} Subscriptions Administrator Portal](https://docs.microsoft.com/en-us/visualstudio/subscriptions/using-admin-portal) and [Assign {% data variables.product.prodname_vs %} Licenses in the {% data variables.product.prodname_vs %} Subscriptions Administration Portal](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-license) in Microsoft Docs. -1. (可选)如果订阅管理员在将 {% data variables.product.prodname_enterprise %} 添加到订阅之前将许可证分配给 {% data variables.product.prodname_vs %} 中的订阅者,则订阅管理员可以在 {% data variables.product.prodname_vs %} 管理门户中将订阅者移动到组合产品/服务。 有关详细信息,请参阅 Microsoft Docs 中的[使用 {% data variables.product.prodname_enterprise %} 管理 {% data variables.product.prodname_vs %} 订阅](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-github#moving-to-visual-studio-with-github-enterprise)。 +1. Optionally, if the subscription admin assigned licenses to subscribers in {% data variables.product.prodname_vs %} before adding {% data variables.product.prodname_enterprise %} to the subscription, the subscription admin can move the subscribers to the combined offering in the {% data variables.product.prodname_vs %} administration portal. For more information, see [Manage {% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-github#moving-to-visual-studio-with-github-enterprise) in Microsoft Docs. -1. 如果订阅管理员尚未禁用电子邮件通知,则订阅者将收到两封确认电子邮件。 有关详细信息,请参阅Microsoft 文档中的[包含 {% data variables.product.prodname_enterprise %} 的 {% data variables.product.prodname_vs %} 订阅](https://docs.microsoft.com/en-us/visualstudio/subscriptions/access-github#what-is-the-visual-studio-subscription-with-github-enterprise-setup-process)。 +1. If the subscription admin has not disabled email notifications, the subscriber will receive two confirmation emails. For more information, see [{% data variables.product.prodname_vs %} subscriptions with {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/access-github#what-is-the-visual-studio-subscription-with-github-enterprise-setup-process) in Microsoft Docs. -1. 组织所有者必须在步骤 1 中的 {% data variables.product.product_location %} 上邀请订阅者加入组织。 订阅者可以使用 {% data variables.product.prodname_dotcom_the_website %} 上的现有个人帐户或新建一个帐户来接受邀请。 订阅者加入组织后,订阅者将成为企业成员。 有关详细信息,请参阅“[邀请用户加入你的组织](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)”。 +1. An organization owner must invite the subscriber to the organization on {% data variables.location.product_location %} from step 1. The subscriber can accept the invitation with an existing personal account on {% data variables.product.prodname_dotcom_the_website %} or create a new account. After the subscriber joins the organization, the subscriber becomes an enterprise member. For more information, see "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)." {% tip %} - **提示**: + **Tips**: - - 虽然不是必需的,但我们建议组织所有者向订阅者的用户主名 (UPN) 使用的同一电子邮件地址发送邀请。 当 {% data variables.product.product_location %} 上的电子邮件地址与订阅者的 UPN 匹配时,可以确保其他企业不会索要该订阅者的许可证。 - - 如果订阅者在 {% data variables.product.product_location %} 上接受具有现有个人帐户的组织邀请,我们建议订阅者在 {% data variables.product.product_location %} 上将他们用于 {% data variables.product.prodname_vs %} 的电子邮件地址添加到其个人帐户。 有关详细信息,请参阅“[将电子邮件地址添加到 {% data variables.product.prodname_dotcom %} 帐户](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account)”。 - - 如果组织所有者必须邀请大量订阅者,脚本可以使进程更快。 有关详细信息,请参阅 `github/platform-samples` 存储库中的[示例 PowerShell 脚本](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1)。 + - While not required, we recommend that the organization owner sends an invitation to the same email address used for the subscriber's User Primary Name (UPN). When the email address on {% data variables.location.product_location %} matches the subscriber's UPN, you can ensure that another enterprise does not claim the subscriber's license. + - If the subscriber accepts the invitation to the organization with an existing personal account on {% data variables.location.product_location %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their personal account on {% data variables.location.product_location %}. For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account)." + - If the organization owner must invite a large number of subscribers, a script may make the process faster. For more information, see [the sample PowerShell script](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1) in the `github/platform-samples` repository. {% endtip %} -为团队中的订阅者设置 {% data variables.product.prodname_vss_ghe %} 后,企业所有者可以在 {% data variables.product.product_location %} 上查看许可信息。 有关详细信息,请参阅“[查看企业帐户的订阅和使用情况](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)”。 +After {% data variables.product.prodname_vss_ghe %} is set up for subscribers on your team, enterprise owners can review licensing information on {% data variables.location.product_location %}. For more information, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)." -## 延伸阅读 +## Further reading -- “[{% data variables.product.prodname_ghe_cloud %} 入门](/get-started/onboarding/getting-started-with-github-enterprise-cloud)” +- "[Getting started with {% data variables.product.prodname_ghe_cloud %}](/get-started/onboarding/getting-started-with-github-enterprise-cloud)" diff --git a/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md b/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md index e744fa5ec8..2a8b764350 100644 --- a/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md +++ b/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md @@ -1,6 +1,6 @@ --- -title: 关于 GitHub Enterprise 的许可证 -intro: '{% ifversion ghec %}如果除了使用 {% data variables.product.prodname_ghe_cloud %} 之外还部署 {% data variables.product.prodname_ghe_server %},{% else %}你{% endif %}可以在 {% ifversion ghes %} {% data variables.product.prodname_enterprise %}{% endif %} 部署之间同步许可证使用情况,并使用许可证文件解锁每个 {% data variables.product.prodname_ghe_server %} 实例。' +title: About licenses for GitHub Enterprise +intro: '{% ifversion ghec %}If you deploy {% data variables.product.prodname_ghe_server %} in addition to using {% data variables.product.prodname_ghe_cloud %}, you{% else %}You{% endif %} can synchronize your license usage between{% ifversion ghes %} {% data variables.product.prodname_enterprise %}{% endif %} deployments, and use a license file to unlock each {% data variables.product.prodname_ghe_server %} instance.' versions: ghec: '*' ghes: '*' @@ -9,41 +9,36 @@ topics: - Enterprise - Licensing shortTitle: About licenses -ms.openlocfilehash: eb904ed497df785cfefa25cee7a5cb1fe5acfaa0 -ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145910509' --- -## 关于 {% data variables.product.prodname_enterprise %} 的许可 + +## About licensing for {% data variables.product.prodname_enterprise %} {% data reusables.enterprise.about-deployment-methods %} {% data reusables.enterprise-licensing.unique-user-licensing-model %} -为确保同一用户不会为多个企业部署使用多个许可证,可以在 {% data variables.product.prodname_ghe_server %} 和 {% data variables.product.prodname_ghe_cloud %} 部署之间同步许可证使用情况。 +To ensure the same user isn't consuming more than one license for multiple enterprise deployments, you can synchronize license usage between your {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} deployments. -若要使用 {% data variables.product.prodname_ghe_server %} 实例,必须上传 {% data variables.product.company_short %} 在你购买、续订或向 {% data variables.product.prodname_enterprise %} 添加用户许可证时提供的许可证文件。 +In order to use a {% data variables.product.prodname_ghe_server %} instance, you must upload a license file that {% data variables.product.company_short %} provides when you purchase, renew, or add user licenses to {% data variables.product.prodname_enterprise %}. -## 关于同步 {% data variables.product.prodname_enterprise %} 的许可证使用情况 +## About synchronization of license usage for {% data variables.product.prodname_enterprise %} -{% data reusables.enterprise-licensing.about-license-sync %} 有关详细信息,请参阅“[同步 {% data variables.product.prodname_ghe_server %} 和 {% data variables.product.prodname_ghe_cloud %} 之间的许可证使用情况](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)”。 +{% data reusables.enterprise-licensing.about-license-sync %} For more information, see "[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)." -## 关于 {% data variables.product.prodname_enterprise %} 的许可证文件 +## About license files for {% data variables.product.prodname_enterprise %} -购买或续订 {% data variables.product.prodname_enterprise %} 时,{% data variables.product.company_short %} 会为 {% ifversion ghec %}{% data variables.product.prodname_ghe_server %}的部署{% elsif ghes %}{% data variables.product.product_location_enterprise %}{% endif %}提供许可证文件。 许可证文件有到期日期,控制可以使用 {% data variables.product.product_location_enterprise %} 的人数。 下载并安装 {% data variables.product.prodname_ghe_server %} 后,必须上传许可证文件以解锁应用程序以供使用。 +When you purchase or renew {% data variables.product.prodname_enterprise %}, {% data variables.product.company_short %} provides a license file {% ifversion ghec %}for your deployments of {% data variables.product.prodname_ghe_server %}{% elsif ghes %}for {% data variables.location.product_location_enterprise %}{% endif %}. A license file has an expiration date and controls the number of people who can use {% data variables.location.product_location_enterprise %}. After you download and install {% data variables.product.prodname_ghe_server %}, you must upload the license file to unlock the application for you to use. -有关下载许可证文件的详细信息,请参阅“[下载 {% data variables.product.prodname_enterprise %} 的许可证文件](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)”。 +For more information about downloading your license file, see "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)." -有关上传许可证文件的详细信息,请参阅 {% ifversion ghec %} {% data variables.product.prodname_ghe_server %} 文档中的[将新的许可证上传到 {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)。{% elsif ghes %} [将新的许可证上传到 {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)。{% endif %} +For more information about uploading your license file, see {% ifversion ghec %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% endif %} -如果您的许可证过期,将无法通过 Web 浏览器或 Git 访问 {% data variables.product.prodname_ghe_server %}。 需要时,您可以使用命令行实用程序备份所有数据。 有关详细信息,请参阅{% ifversion ghec %}"[Configuring backups on your appliance]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/guides/installation/configuring-backups-on-your-appliance)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}“[在设备上配置备份](/admin/guides/installation/configuring-backups-on-your-appliance)”。 {% endif %} +If your license expires, you won't be able to access {% data variables.product.prodname_ghe_server %} via a web browser or Git. If needed, you will be able to use command-line utilities to back up all your data. For more information, see {% ifversion ghec %}"[Configuring backups on your appliance]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/guides/installation/configuring-backups-on-your-appliance)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Configuring backups on your appliance](/admin/guides/installation/configuring-backups-on-your-appliance)." {% endif %} -如对续订许可有任何疑问,请联系 {% data variables.contact.contact_enterprise_sales %}。 +If you have any questions about renewing your license, contact {% data variables.contact.contact_enterprise_sales %}. -## 延伸阅读 +## Further reading -- [关于企业的计费](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise) -- [{% data variables.product.prodname_enterprise %} 发布](https://enterprise.github.com/releases/)网站 -- [设置 {% data variables.product.prodname_ghe_server %} 实例]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/installation/setting-up-a-github-enterprise-server-instance) +- "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)" +- [{% data variables.product.prodname_enterprise %} Releases](https://enterprise.github.com/releases/) website +- "[Setting up a {% data variables.product.prodname_ghe_server %} instance]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/installation/setting-up-a-github-enterprise-server-instance)" diff --git a/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md b/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md index 27d066bec0..9e67e9dfa4 100644 --- a/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md +++ b/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md @@ -1,6 +1,6 @@ --- -title: 下载 GitHub Enterprise 许可证 -intro: '您可以下载 {% data variables.product.prodname_ghe_server %} 的许可证文件副本。' +title: Downloading your license for GitHub Enterprise +intro: 'You can download a copy of your license file for {% data variables.product.prodname_ghe_server %}.' permissions: 'Enterprise owners can download license files for {% data variables.product.prodname_ghe_server %}.' versions: ghec: '*' @@ -10,33 +10,29 @@ topics: - Enterprise - Licensing shortTitle: Download your license -ms.openlocfilehash: eed588e2580558280e2e11639f0904b5f9fcf118 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145084441' --- -## 关于 {% data variables.product.prodname_enterprise %} 的许可证文件 -从 {% data variables.contact.contact_enterprise_sales %}购买或升级 {% data variables.product.prodname_enterprise %} 许可证后,必须下载新的许可证文件。 有关 {% data variables.product.prodname_enterprise %} 许可证的详细信息,请参阅“[关于 {% data variables.product.prodname_enterprise %} 的许可证](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)”。 +## About license files for {% data variables.product.prodname_enterprise %} + +After you purchase or upgrade a license for {% data variables.product.prodname_enterprise %} from {% data variables.contact.contact_enterprise_sales %}, you must download your new license file. For more information about licenses for {% data variables.product.prodname_enterprise %}, see "[About licenses for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)." {% data reusables.enterprise-licensing.contact-sales-for-renewals-or-seats %} -## 从 {% data variables.product.prodname_dotcom_the_website %} 下载许可证 +## Downloading your license from {% data variables.product.prodname_dotcom_the_website %} -您必须在 {% data variables.product.prodname_dotcom_the_website %} 上拥有企业帐户才能从 {% data variables.product.prodname_dotcom_the_website %} 下载许可证。 有关详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[关于企业帐户](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion ghes %}”。{% elsif ghec %}。”{% endif %} +You must have an enterprise account on {% data variables.product.prodname_dotcom_the_website %} to download your license from {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion ghes %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% elsif ghec %}."{% endif %} -{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} -1. 在左侧边栏中,单击“企业许可”。 - ![企业帐户设置侧边栏中的“企业许可”选项卡](/assets/images/help/enterprises/enterprise-licensing-tab.png) -1. 在“Enterprise Server 实例”下,单击 {% octicon "download" aria-label="The download icon" %} 下载许可证文件。 - ![下载 GitHub Enterprise Server 许可证](/assets/images/help/business-accounts/download-ghes-license.png) +{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} +{% data reusables.enterprise-accounts.settings-tab %} +1. In the left sidebar, click **Enterprise licensing**. + !["Enterprise licensing" tab in the enterprise account settings sidebar](/assets/images/help/enterprises/enterprise-licensing-tab.png) +1. Under "Enterprise Server Instances", click {% octicon "download" aria-label="The download icon" %} to download your license file. + ![Download GitHub Enterprise Server license](/assets/images/help/business-accounts/download-ghes-license.png) -下载许可证文件后,可以将文件上传到 {% data variables.product.product_location_enterprise %} 以验证应用程序。 有关详细信息,请参阅 {% ifversion ghec %}{% data variables.product.prodname_ghe_server %} 文档中的“[将新许可证上传到 {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)”。{% elsif ghes %}“[将新许可证上传到 {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)”。{% endif %} +After you download your license file, you can upload the file to {% data variables.location.product_location_enterprise %} to validate your application. For more information, see {% ifversion ghec %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% endif %} -## 如果您在 {% data variables.product.prodname_dotcom_the_website %} 上没有企业帐户,请下载许可证 +## Downloading your license if you don't have an enterprise account on {% data variables.product.prodname_dotcom_the_website %} -如果你没有 {% data variables.product.prodname_dotcom_the_website %} 的企业帐户,或者不确定,可从 [{% data variables.product.prodname_enterprise %} 网站](https://enterprise.github.com/download)下载你的 {% data variables.product.prodname_ghe_server %} 许可证。 +If you do not have an enterprise account on {% data variables.product.prodname_dotcom_the_website %}, or if you're not sure, you may be able to download your {% data variables.product.prodname_ghe_server %} license from the [{% data variables.product.prodname_enterprise %} website](https://enterprise.github.com/download). -如对下载许可证有任何疑问,请联系 {% data variables.contact.contact_enterprise_sales %}。 +If you have any questions about downloading your license, contact {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md b/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md index dfa8df5bfb..e66cfc6dd6 100644 --- a/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md +++ b/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md @@ -1,6 +1,6 @@ --- -title: 将新许可证上传到 GitHub Enterprise Server -intro: '您可以将 {% data variables.product.prodname_enterprise %} 的许可文件上传到 {% data variables.product.product_location_enterprise %} 以验证您的应用程序。' +title: Uploading a new license to GitHub Enterprise Server +intro: 'You can upload your license file for {% data variables.product.prodname_enterprise %} to {% data variables.location.product_location_enterprise %} to validate your application.' versions: ghes: '*' type: how_to @@ -8,33 +8,30 @@ topics: - Enterprise - Licensing shortTitle: Upload a new license -ms.openlocfilehash: 184206b210289e062e83e237acaa853bb80470c1 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145084436' --- -## 关于 {% data variables.product.prodname_enterprise %} 的许可证文件 -从 {% data variables.contact.contact_enterprise_sales %} 购买或升级 {% data variables.product.prodname_enterprise %} 许可证后,必须将新许可证文件上传到 {% data variables.product.product_location_enterprise %} 才能解锁新用户许可证。 有关 {% data variables.product.product_name %} 许可证的详细信息,请参阅“[关于 {% data variables.product.prodname_enterprise %} 的许可证](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)”和“[下载 {% data variables.product.prodname_enterprise %} 的许可证](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)”。 +## About license files for {% data variables.product.prodname_enterprise %} + +After you purchase or upgrade a license for {% data variables.product.prodname_enterprise %} from {% data variables.contact.contact_enterprise_sales %}, you must upload the new license file to {% data variables.location.product_location_enterprise %} to unlock your new user licenses. For more information about licenses for {% data variables.product.product_name %}, see "[About licenses for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)" and "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)." {% data reusables.enterprise-licensing.contact-sales-for-renewals-or-seats %} -## 将许可证上传到 {% data variables.product.product_location_enterprise %} +## Uploading your license to {% data variables.location.product_location_enterprise %} {% warning %} -警告:更新许可证会导致 {% data variables.product.product_location %} 出现短暂停机。 +**Warning:** Updating your license causes a small amount of downtime for {% data variables.location.product_location %}. {% endwarning %} -1. 以站点管理员的身份登录到 {% data variables.product.product_location_enterprise %}。 -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -1. 在“快速链接”下,单击“更新许可证”。 - ![“更新许可证”链接](/assets/images/enterprise/business-accounts/update-license-link.png) -1. 若要选择许可证,请单击“许可证文件”,或将许可证文件拖动到“许可证文件” 。 - ![上传许可证文件](/assets/images/enterprise/management-console/upload-license.png) -1. 单击“上载” 。 - ![开始上传](/assets/images/enterprise/management-console/begin-upload.png) +1. Sign into {% data variables.location.product_location_enterprise %} as a site administrator. +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.license-tab %} +1. Under "Quick links", click **Update license**. + ![Update license link](/assets/images/enterprise/business-accounts/update-license-link.png) +1. To select your license, click **License file**, or drag your license file onto **License file**. + ![Upload license file](/assets/images/enterprise/management-console/upload-license.png) +1. Click **Upload**. + ![Begin upload](/assets/images/enterprise/management-console/begin-upload.png) diff --git a/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md b/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md index 0827bbf327..452c276d23 100644 --- a/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md +++ b/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md @@ -1,6 +1,6 @@ --- -title: 查看 GitHub Enterprise 的许可证使用情况 -intro: '您可以在 {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %} 上查看企业的许可证使用情况。' +title: Viewing license usage for GitHub Enterprise +intro: 'You can view license usage for your enterprise on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.location.product_location %}{% endif %}.' permissions: 'Enterprise owners can view license usage for {% data variables.product.prodname_enterprise %}.' versions: ghec: '*' @@ -10,59 +10,59 @@ topics: - Enterprise - Licensing shortTitle: View license usage -ms.openlocfilehash: 7f3c3c6e65928601d01ac17139928af6ceedf354 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147572614' --- -## 关于 {% data variables.product.prodname_enterprise %} 的许可证使用情况 -可在 {% data variables.product.product_location %} 上查看 {% data variables.product.product_name %} 的许可证使用情况。 +## About license usage for {% data variables.product.prodname_enterprise %} -如果同时使用 {% data variables.product.prodname_ghe_cloud %} 和 {% data variables.product.prodname_ghe_server %} 并在这两个产品之间同步许可证使用情况,则可在 {% data variables.product.prodname_dotcom_the_website %} 上查看两者的许可证使用情况。 有关许可证同步的详细信息,请参阅“[同步 {% data variables.product.prodname_ghe_server %} 和 {% data variables.product.prodname_ghe_cloud %} 之间的许可证使用情况](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)”。 +You can view license usage for {% data variables.product.product_name %} on {% data variables.location.product_location %}. + +If you use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} and sync license usage between the products, you can view license usage for both on {% data variables.product.prodname_dotcom_the_website %}. For more information about license sync, see "[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)." {% ifversion ghes %} -要详细了解如何在 {% data variables.product.prodname_dotcom_the_website %} 上查看许可证使用情况,并了解如何确定许可证上次同步时间,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[查看 {% data variables.product.prodname_enterprise %} 的许可证使用情况](/enterprise-cloud@latest/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise)”。 +For more information about viewing license usage on {% data variables.product.prodname_dotcom_the_website %} and identifying when the last license sync occurred, see "[Viewing license usage for {% data variables.product.prodname_enterprise %}](/enterprise-cloud@latest/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise)" in the {% data variables.product.prodname_ghe_cloud %} documentation. {% endif %} -还可使用 REST API 返回已使用的许可证数据和许可证同步作业的状态。 有关详细信息,请参阅 REST API 文档中的“[GitHub Enterprise 管理](/enterprise-cloud@latest/rest/enterprise-admin/license)”。 +You can also use the REST API to return consumed licenses data and the status of the license sync job. For more information, see "[GitHub Enterprise administration](/enterprise-cloud@latest/rest/enterprise-admin/license)" in the REST API documentation. -若要详细了解与企业帐户关联的许可证数据以及如何计算已使用的用户席位数,请参阅“[GitHub Enterprise 许可证使用情况疑难解答](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)”。 +To learn more about the license data associated with your enterprise account and how the number of consumed user seats are calculated, see "[Troubleshooting license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)." -## 查看 {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %} 上的许可证使用情况 +## Viewing license usage on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.location.product_location %}{% endif %} -您可以查看企业的许可证使用情况并下载包含许可证详细信息的文件。 如果在此报告中未看到预期的许可证计数,则订阅者拥有的 {% data variables.product.prodname_vs %} 订阅电子邮件地址和 {% data variables.product.prodname_dotcom_the_website %} 电子邮件地址可能不完全相同。 有关详细信息,请参阅“[GitHub Enterprise 许可证使用情况疑难解答](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)”。 +You can view the license usage for your enterprise and download a file with license details. If you're not seeing expected license counts in this report, it's possible that the subscriber’s assigned {% data variables.product.prodname_vs %} subscription email address and {% data variables.product.prodname_dotcom_the_website %} email address aren't exactly the same. For further information, see "[Troubleshooting license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)." {% ifversion ghec %} -{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} -1. 在左侧边栏中,单击“企业许可”。 - ![企业帐户设置侧边栏中的“企业许可”选项卡](/assets/images/help/enterprises/enterprise-licensing-tab.png) -1. 检查您当前的 {% data variables.product.prodname_enterprise %} 许可,以及已使用和可用的用户许可。 - - 若要以 CSV 文件的形式下载已使用的许可证报表,请在右上角单击 {% octicon "download" aria-label="The download icon" %}。 若要详细了解如何查看此报表中的数据,请参阅“[GitHub Enterprise 许可证使用情况疑难解答](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)”。 - - 如果您的许可证包含 {% data variables.product.prodname_GH_advanced_security %},您可以查看您的总席位使用情况。 有关详细信息,请参阅“[查看 {% data variables.product.prodname_GH_advanced_security %} 使用情况](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)”。 +{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} +{% data reusables.enterprise-accounts.settings-tab %} +1. In the left sidebar, click **Enterprise licensing**. + !["Enterprise licensing" tab in the enterprise account settings sidebar](/assets/images/help/enterprises/enterprise-licensing-tab.png) +1. Review your current {% data variables.product.prodname_enterprise %} license, as well as consumed and available user licenses. + - To download the consumed license report as a CSV file, in the top right, click {% octicon "download" aria-label="The download icon" %}. For more information about reviewing the data in this report, see "[Troubleshooting license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)." + - If your license includes {% data variables.product.prodname_GH_advanced_security %}, you can review your total seat use. For more information, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)." {% elsif ghes %} -{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -1. 查看你当前的 {% data variables.product.prodname_enterprise %} 许可证,以及已使用和可用的用户许可证。{% ifversion ghes %} - - 若要以 JSON 文件的形式下载已使用的许可证报表,请在右上角的“快速链接”下,选择“导出许可证使用情况”。 若要详细了解如何查看此报表中的数据,请参阅“[GitHub Enterprise 许可证使用情况疑难解答](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)”。 - - 如果您的许可证包含 {% data variables.product.prodname_GH_advanced_security %},您可以查看您的总席位使用情况以及每个组织的提交者细分。 有关详细信息,请参阅“[管理企业的 {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security)”。{% endif %} - -{% endif %} {% ifversion ghec %} -## 查看许可证上次同步日期 - -{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} -1. 在左侧边栏中,单击“企业许可”。 - ![企业帐户设置侧边栏中的“企业许可”选项卡](/assets/images/help/enterprises/enterprise-licensing-tab.png) -1. 要确定许可证上次同步时间,请在“企业服务器实例”下,查找“使用情况已上传”或“使用情况已同步”事件旁边的时间戳。 - - “服务器使用情况已上传”表示在上传 {% data variables.product.prodname_ghe_server %} 许可证文件时,手动更新了环境之间的许可证使用情况。 - - “{% data variables.product.prodname_github_connect %} 服务器使用情况已同步”表示环境之间的许可证使用情况已自动更新。 - - “{% data variables.product.prodname_github_connect %} 服务器使用情况从未同步”表示已配置 {% data variables.product.prodname_github_connect %},但从未成功更新环境之间的许可证使用情况。 +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.license-tab %} +1. Review your current {% data variables.product.prodname_enterprise %} license, as well as consumed and available user licenses.{% ifversion ghes %} + - To download the consumed license report as a JSON file, in the top right under "Quick links", choose **Export license usage**. For more information about reviewing the data in this report, see "[Troubleshooting license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)." + - If your license includes {% data variables.product.prodname_GH_advanced_security %}, you can review your total seat use as well as a per-organization breakdown of committers. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security)."{% endif %} + +{% endif %} +{% ifversion ghec %} +## Viewing the last license sync date + +{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} +{% data reusables.enterprise-accounts.settings-tab %} +1. In the left sidebar, click **Enterprise licensing**. + !["Enterprise licensing" tab in the enterprise account settings sidebar](/assets/images/help/enterprises/enterprise-licensing-tab.png) +1. To identify when the last license sync occurred, under "Enterprise Server instances", look for timestamps next to usage uploaded or synced events. + - "Server usage uploaded" indicates license usage between environments was manually updated when a {% data variables.product.prodname_ghe_server %} license file was uploaded. + - "{% data variables.product.prodname_github_connect %} server usage synced" indicates license usage between environments was automatically updated. + - "{% data variables.product.prodname_github_connect %} server usage never synced" indicates that {% data variables.product.prodname_github_connect %} is configured, but license usage between environments has never updated successfully. {% endif %} diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md index 4dca5936e8..e7a4e2b032 100644 --- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md +++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md @@ -351,7 +351,7 @@ If your workflow uses packs that are published on a {% data variables.product.pr {% endraw %} ``` -The package patterns in the registries list are examined in order, so you should generally place the most specific package patterns first. The values for `token` must be a personal access token generated by the GitHub instance you are downloading from with the `read:packages` permission. +The package patterns in the registries list are examined in order, so you should generally place the most specific package patterns first. The values for `token` must be a {% data variables.product.pat_v1 %} generated by the GitHub instance you are downloading from with the `read:packages` permission. Notice the `|` after the `registries` property name. This is important since {% data variables.product.prodname_actions %} inputs can only accept strings. Using the `|` converts the subsequent text to a string, which is parsed later by the {% data reusables.actions.action-codeql-action-init %} action. diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md index 9a082c7088..2066a0a5cc 100644 --- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md +++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md @@ -1,6 +1,6 @@ --- -title: 查看代码扫描日志 -intro: '您可以在 {% data variables.product.product_location %} 中查看 {% data variables.product.prodname_code_scanning %} 分析期间生成的输出。' +title: Viewing code scanning logs +intro: 'You can view the output generated during {% data variables.product.prodname_code_scanning %} analysis in {% data variables.location.product_location %}.' product: '{% data reusables.gated-features.code-scanning %}' permissions: 'If you have write permissions to a repository, you can view the {% data variables.product.prodname_code_scanning %} logs for that repository.' miniTocMaxHeadingLevel: 4 @@ -14,73 +14,69 @@ versions: topics: - Security shortTitle: View code scanning logs -ms.openlocfilehash: e4f4c3e601540e02c01bbe3761a11528a746a519 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147444627' --- -{% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} -## 关于第三方 {% data variables.product.prodname_code_scanning %} 设置 +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} -您可以使用各种工具在仓库中设置 {% data variables.product.prodname_code_scanning %} 。 有关详细信息,请参阅“[为存储库设置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#options-for-setting-up-code-scanning)”。 +## About your {% data variables.product.prodname_code_scanning %} setup -您可用的日志和诊断信息取决于您在 {% data variables.product.prodname_code_scanning %} 中使用的方法。 你可以使用警报列表中的“工具”下拉菜单,检查存储库的“安全性”选项卡中使用的 {% data variables.product.prodname_code_scanning %} 类型。 有关详细信息,请参阅“[管理存储库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)”。 +You can use a variety of tools to set up {% data variables.product.prodname_code_scanning %} in your repository. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#options-for-setting-up-code-scanning)." -## 关于分析和诊断信息 +The log and diagnostic information available to you depends on the method you use for {% data variables.product.prodname_code_scanning %} in your repository. You can check the type of {% data variables.product.prodname_code_scanning %} you're using in the **Security** tab of your repository, by using the **Tool** drop-down menu in the alert list. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." -您可以使用 {% data variables.product.prodname_dotcom %} 上的 {% data variables.product.prodname_codeql %} 分析查看 {% data variables.product.prodname_code_scanning %} 运行的分析和诊断信息。 +## About analysis and diagnostic information -在警报列表顶部的标题中显示最近分析的“分析”信息。 有关详细信息,请参阅“[管理存储库的代码扫描警报](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)”。 +You can see analysis and diagnostic information for {% data variables.product.prodname_code_scanning %} run using {% data variables.product.prodname_codeql %} analysis on {% data variables.product.prodname_dotcom %}. -“诊断”信息显示在行动工作流日志中,包含摘要指标和提取器诊断。 有关访问 {% data variables.product.prodname_dotcom %} 上的 {% data variables.product.prodname_code_scanning %} 日志的信息,请参阅下面的“[查看 {% data variables.product.prodname_code_scanning %} 的日志记录输出](#viewing-the-logging-output-from-code-scanning)”。 +**Analysis** information is shown for the most recent analysis in a header at the top of the list of alerts. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." -如果您在 {% data variables.product.prodname_dotcom %} 外部使用 {% data variables.product.prodname_codeql_cli %} ,您将在数据库分析期间生成的输出中看到诊断信息。 此信息也包含在您随 {% data variables.product.prodname_code_scanning %} 结果上传到 {% data variables.product.prodname_dotcom %} 的 SARIF 结果文件中。 +**Diagnostic** information is displayed in the Action workflow logs and consists of summary metrics and extractor diagnostics. For information about accessing {% data variables.product.prodname_code_scanning %} logs on {% data variables.product.prodname_dotcom %}, see "[Viewing the logging output from {% data variables.product.prodname_code_scanning %}](#viewing-the-logging-output-from-code-scanning)" below. -有关 {% data variables.product.prodname_codeql_cli %} 的信息,请参阅“[在 CI 系统中配置 {% data variables.product.prodname_codeql_cli %}](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)”。 +If you're using the {% data variables.product.prodname_codeql_cli %} outside {% data variables.product.prodname_dotcom %}, you'll see diagnostic information in the output generated during database analysis. This information is also included in the SARIF results file you upload to {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_code_scanning %} results. -### 关于摘要指标 +For information about the {% data variables.product.prodname_codeql_cli %}, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)." + +### About summary metrics {% data reusables.code-scanning.summary-metrics %} -### 关于 {% data variables.product.prodname_codeql %} 源代码提取诊断信息 +### About {% data variables.product.prodname_codeql %} source code extraction diagnostics {% data reusables.code-scanning.extractor-diagnostics %} {% ifversion codeql-action-debug-logging %} -通过启用调试日志记录,可以查看有关在创建数据库期间发生的 {% data variables.product.prodname_codeql %} 提取器错误和警告的更多详细信息。 有关详细信息,请参阅“[对 CodeQL 工作流进行故障排除](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow#creating-codeql-debugging-artifacts-by-re-running-jobs-with-debug-logging-enabled)”。 +You can see more detailed information about {% data variables.product.prodname_codeql %} extractor errors and warnings that occurred during database creation by enabling debug logging. For more information, see "[Troubleshooting the CodeQL workflow](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow#creating-codeql-debugging-artifacts-by-re-running-jobs-with-debug-logging-enabled)." {% endif %} -## 查看来自 {% data variables.product.prodname_code_scanning %} 的日志记录输出 +## Viewing the logging output from {% data variables.product.prodname_code_scanning %} -本节适用于使用 {% data variables.product.prodname_code_scanning %} 的 {% data variables.product.prodname_actions %} 运行({% data variables.product.prodname_codeql %} 或第三方)。 +This section applies to {% data variables.product.prodname_code_scanning %} run using {% data variables.product.prodname_actions %} ({% data variables.product.prodname_codeql %} or third-party). -为仓库设置 {% 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 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" and "Configuring notifications." 条目的文本是提交消息的标题。 + 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. - ![显示 {% data variables.product.prodname_code_scanning %} 工作流的操作列表](/assets/images/help/repository/code-scanning-actions-list.png) + ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png) -1. 单击 {% data variables.product.prodname_code_scanning %} 工作流程的项目。 +1. Click the entry for the {% data variables.product.prodname_code_scanning %} workflow. -2. 单击左侧的作业名称。 例如,“分析(语言)”。 +2. Click the job name on the left. For example, **Analyze (LANGUAGE)**. - ![{% data variables.product.prodname_code_scanning %} 工作流程的日志输出](/assets/images/help/repository/code-scanning-logging-analyze-action.png) + ![Log output from the {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-logging-analyze-action.png) -1. 查看此工作流运行时操作的日志记录输出。 +1. Review the logging output from the actions in this workflow as they run. -1. 在所有作业完成后,您可以查看已识别的任何 {% data variables.product.prodname_code_scanning %} 警报的详细信息。 有关详细信息,请参阅“[管理存储库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)”。 +1. Once all jobs are complete, you can view the details of any {% data variables.product.prodname_code_scanning %} alerts that were identified. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." {% note %} -注意:如果发起将 {% data variables.product.prodname_code_scanning %} 工作流添加到存储库的拉取请求,则在合并拉取请求之前,来自该拉取请求的警报不会直接显示在 {% data variables.product.prodname_code_scanning_capc %} 页面上。 如果发现任何警报,你可以在合并拉取请求之前查看这些警报,方法是在 {% data variables.product.prodname_code_scanning_capc %} 页面的横幅中单击“发现 n 条警报”的链接。 +**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. -![单击“发现的 n 条警报”链接](/assets/images/help/repository/code-scanning-alerts-found-link.png) +![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) {% endnote %} diff --git a/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md index 19be329625..12b421a65d 100644 --- a/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -130,7 +130,7 @@ Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.pr |----|----| | `tool.driver` | **Required.** A `toolComponent` object that describes the analysis tool. For more information, see the [`toolComponent` object](#toolcomponent-object). | | `tool.extensions[]` | **Optional.** An array of `toolComponent` objects that represent any plugins or extensions used by the tool during analysis. For more information, see the [`toolComponent` object](#toolcomponent-object). | -| `invocation.workingDirectory.uri` | **Optional.** This field is used only when `checkout_uri` (SARIF upload API only) or `checkout_path` (% data variables.product.prodname_actions %} only) are not provided. The value is used to convert absolute URIs used in [`physicalLocation` objects](#physicallocation-object) to relative URIs. For more information, see "[Specifying the root for source files](#specifying-the-root-for-source-files)."| +| `invocation.workingDirectory.uri` | **Optional.** This field is used only when `checkout_uri` (SARIF upload API only) or `checkout_path` ({% data variables.product.prodname_actions %} only) are not provided. The value is used to convert absolute URIs used in [`physicalLocation` objects](#physicallocation-object) to relative URIs. For more information, see "[Specifying the root for source files](#specifying-the-root-for-source-files)."| | `results[]` | **Required.** The results of the analysis tool. {% data variables.product.prodname_code_scanning_capc %} displays the results on {% data variables.product.prodname_dotcom %}. For more information, see the [`result` object](#result-object). ### `toolComponent` object diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md index 2f4203d676..370ce281d8 100644 --- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md +++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md @@ -1,7 +1,7 @@ --- title: About CodeQL code scanning in your CI system shortTitle: Code scanning in your CI -intro: 'You can analyze your code with {% data variables.product.prodname_codeql %} in a third-party continuous integration system and upload the results to {% data variables.product.product_location %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.' +intro: 'You can analyze your code with {% data variables.product.prodname_codeql %} in a third-party continuous integration system and upload the results to {% data variables.location.product_location %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.' product: '{% data reusables.gated-features.code-scanning %}' versions: fpt: '*' diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md index 36eea83bc0..1a0e74ad50 100644 --- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md +++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md @@ -187,7 +187,7 @@ $ codeql database analyze /codeql-dbs/example-repo \ {% data reusables.code-scanning.upload-sarif-alert-limit %} -Before you can upload results to {% data variables.product.product_name %}, you must determine the best way to pass the {% data variables.product.prodname_github_app %} or personal access token you created earlier to the {% data variables.product.prodname_codeql_cli %} (see [Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system#generating-a-token-for-authentication-with-github)). We recommend that you review your CI system's guidance on the secure use of a secret store. The {% data variables.product.prodname_codeql_cli %} supports: +Before you can upload results to {% data variables.product.product_name %}, you must determine the best way to pass the {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} you created earlier to the {% data variables.product.prodname_codeql_cli %} (see [Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system#generating-a-token-for-authentication-with-github)). We recommend that you review your CI system's guidance on the secure use of a secret store. The {% data variables.product.prodname_codeql_cli %} supports: - Passing the token to the CLI via standard input using the `--github-auth-stdin` option (recommended). - Saving the secret in the environment variable `GITHUB_TOKEN` and running the CLI without including the `--github-auth-stdin` option. @@ -207,7 +207,7 @@ When you have decided on the most secure and reliable method for your CI server, | `--commit` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the full SHA of the commit you analyzed. | `--sarif` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the SARIF file to load.{% ifversion ghes or ghae %} | `--github-url` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the URL for {% data variables.product.product_name %}.{% endif %} -| `--github-auth-stdin` | | Optional. Use to pass the CLI the {% data variables.product.prodname_github_app %} or personal access token created for authentication with {% data variables.product.company_short %}'s REST API via standard input. This is not needed if the command has access to a `GITHUB_TOKEN` environment variable set with this token. +| `--github-auth-stdin` | | Optional. Use to pass the CLI the {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} created for authentication with {% data variables.product.company_short %}'s REST API via standard input. This is not needed if the command has access to a `GITHUB_TOKEN` environment variable set with this token. For more information, see [github upload-results](https://codeql.github.com/docs/codeql-cli/manual/github-upload-results/) in the documentation for the {% data variables.product.prodname_codeql_cli %}. @@ -231,12 +231,12 @@ There is no output from this command unless the upload was unsuccessful. The com The {% data variables.product.prodname_codeql_cli %} bundle includes queries that are maintained by {% data variables.product.company_short %} experts, security researchers, and community contributors. If you want to run queries developed by other organizations, {% data variables.product.prodname_codeql %} query packs provide an efficient and reliable way to download and run queries. For more information, see "[About code scanning with CodeQL](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)." -Before you can use a {% data variables.product.prodname_codeql %} pack to analyze a database, you must download any packages you require from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}. This can be done either by using the `--download` flag as part of the `codeql database analyze` command. If a package is not publicly available, you will need to use a {% data variables.product.prodname_github_app %} or personal access token to authenticate. For more information and an example, see "[Uploading results to {% data variables.product.product_name %}](#uploading-results-to-github)" above. +Before you can use a {% data variables.product.prodname_codeql %} pack to analyze a database, you must download any packages you require from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}. This can be done either by using the `--download` flag as part of the `codeql database analyze` command. If a package is not publicly available, you will need to use a {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} to authenticate. For more information and an example, see "[Uploading results to {% data variables.product.product_name %}](#uploading-results-to-github)" above. | Option | Required | Usage | |--------|:--------:|-----| | `` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the scope and name of one or more CodeQL query packs to download using a comma-separated list. Optionally, include the version to download and unzip. By default the latest version of this pack is downloaded. Optionally, include a path to a query, directory, or query suite to run. If no path is included, then run the default queries of this pack. | -| `--github-auth-stdin` | | Optional. Pass the {% data variables.product.prodname_github_app %} or personal access token created for authentication with {% data variables.product.company_short %}'s REST API to the CLI via standard input. This is not needed if the command has access to a `GITHUB_TOKEN` environment variable set with this token. +| `--github-auth-stdin` | | Optional. Pass the {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} created for authentication with {% data variables.product.company_short %}'s REST API to the CLI via standard input. This is not needed if the command has access to a `GITHUB_TOKEN` environment variable set with this token. ### Basic example diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md index cc1e521fa4..e9d72e176b 100644 --- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md +++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md @@ -1,7 +1,7 @@ --- -title: 在 CI 系统中配置 CodeQL 运行器 +title: Configuring CodeQL runner in your CI system shortTitle: Configure CodeQL runner -intro: '您可以配置 {% data variables.product.prodname_codeql_runner %} 如何扫描项目中的代码并将结果上传到 {% data variables.product.prodname_dotcom %}。' +intro: 'You can configure how the {% data variables.product.prodname_codeql_runner %} scans the code in your project and uploads the results to {% data variables.product.prodname_dotcom %}.' product: '{% data reusables.gated-features.code-scanning %}' miniTocMaxHeadingLevel: 3 redirect_from: @@ -24,35 +24,33 @@ topics: - C/C++ - C# - Java -ms.openlocfilehash: 4a1f114fa605f90ee4ccc82dcd30007f1ad17623 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147060888' --- -{% data reusables.code-scanning.deprecation-codeql-runner %} {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} -## 关于在 CI 系统中配置 {% data variables.product.prodname_codeql %}{% data variables.product.prodname_code_scanning %} -要将 {% data variables.product.prodname_code_scanning %} 集成到 CI 系统中,您可以使用 {% data variables.product.prodname_codeql_runner %}。 有关详细信息,请参阅“[在 CI 系统中运行 {% data variables.product.prodname_codeql_runner %}](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)”。 +{% data reusables.code-scanning.deprecation-codeql-runner %} +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning %} -一般情况下,调用 {% data variables.product.prodname_codeql_runner %} 如下所示。 +## About configuring {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system + +To integrate {% data variables.product.prodname_code_scanning %} into your CI system, you can use the {% data variables.product.prodname_codeql_runner %}. For more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)." + +In general, you invoke the {% data variables.product.prodname_codeql_runner %} as follows. ```shell $ /path/to-runner/codeql-runner-OS ``` -`/path/to-runner/` 取决于你在 CI 系统中下载 {% data variables.product.prodname_codeql_runner %} 的位置。 `codeql-runner-OS` 取决于所使用的操作系统。 -有三个版本的 {% data variables.product.prodname_codeql_runner %}:`codeql-runner-linux`、`codeql-runner-macos` 和 `codeql-runner-win`,分别适用于 Linux、macOS 和 Windows 系统。 +`/path/to-runner/` depends on where you've downloaded the {% data variables.product.prodname_codeql_runner %} on your CI system. `codeql-runner-OS` depends on the operating system you use. +There are three versions of the {% data variables.product.prodname_codeql_runner %}, `codeql-runner-linux`, `codeql-runner-macos`, and `codeql-runner-win`, for Linux, macOS, and Windows systems respectively. -要自定义 {% data variables.product.prodname_codeql_runner %} 扫描代码的方式,可以使用 `--languages` 和 `--queries` 等标志,也可以在单独的配置文件中指定自定义设置。 +To customize the way the {% data variables.product.prodname_codeql_runner %} scans your code, you can use flags, such as `--languages` and `--queries`, or you can specify custom settings in a separate configuration file. -## 扫描拉取请求 +## Scanning pull requests -每当创建拉取请求时扫描代码可防止开发者在代码中引入新的漏洞和错误。 +Scanning code whenever a pull request is created prevents developers from introducing new vulnerabilities and errors into the code. -若要扫描拉取请求,请运行 `analyze` 命令并使用 `--ref` 标志来指定拉取请求。 引用为 `refs/pull//head` 或 `refs/pull//merge`,具体取决于你签出的是拉取请求分支的 HEAD 提交还是基础分支的合并提交。 +To scan a pull request, run the `analyze` command and use the `--ref` flag to specify the pull request. The reference is `refs/pull//head` or `refs/pull//merge`, depending on whether you have checked out the HEAD commit of the pull request branch or a merge commit with the base branch. ```shell $ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge @@ -60,50 +58,50 @@ $ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge {% note %} -注意:如果你使用第三方工具分析代码,并希望结果显示为拉取请求检查,则必须运行 `upload` 命令并使用 `--ref` 标志来指定拉取请求而不是分支。 引用为 `refs/pull//head` 或 `refs/pull//merge`。 +**Note**: If you analyze code with a third-party tool and want the results to appear as pull request checks, you must run the `upload` command and use the `--ref` flag to specify the pull request instead of the branch. The reference is `refs/pull//head` or `refs/pull//merge`. {% endnote %} -## 覆盖自动语言检测 +## Overriding automatic language detection -{% data variables.product.prodname_codeql_runner %} 自动检测并扫描用支持的语言编写的代码。 +The {% data variables.product.prodname_codeql_runner %} automatically detects and scans code written in the supported languages. {% data reusables.code-scanning.codeql-languages-bullets %} {% data reusables.code-scanning.specify-language-to-analyze %} -要替代自动语言检测,请运行带有 `--languages` 标志的 `init` 命令,后跟以逗号分隔的语言关键字列表。 支持语言的关键词是 {% data reusables.code-scanning.codeql-languages-keywords %}。 +To override automatic language detection, run the `init` command with the `--languages` flag, followed by a comma-separated list of language keywords. The keywords for the supported languages are {% data reusables.code-scanning.codeql-languages-keywords %}. ```shell $ /path/to-runner/codeql-runner-linux init --languages cpp,java ``` -## 运行额外查询 +## Running additional queries {% data reusables.code-scanning.run-additional-queries %} {% data reusables.code-scanning.codeql-query-suites-explanation %} -要添加一个或多个查询,请将以逗号分隔的路径列表传递到 `init` 命令的 `--queries` 标志。 您也可以在配置文件中指定额外查询。 +To add one or more queries, pass a comma-separated list of paths to the `--queries` flag of the `init` command. You can also specify additional queries in a configuration file. -如果你还要将配置文件用于自定义设置,并使用 `--queries` 标志指定额外查询,则 {% data variables.product.prodname_codeql_runner %} 会使用通过 `--queries` 指定的额外查询而不是配置文件中的任何查询。 -如果要运行使用该标志指定的额外查询与配置文件中指定的查询的组合集,请在传递给 `--queries` 的值前面加上 `+` 符号。 -有关详细信息,请参阅“[使用自定义配置文件](#using-a-custom-configuration-file)”。 +If you also are using a configuration file for custom settings, and you are also specifying additional queries with the `--queries` flag, the {% data variables.product.prodname_codeql_runner %} uses the additional queries specified with the `--queries` flag instead of any in the configuration file. +If you want to run the combined set of additional queries specified with the flag and in the configuration file, prefix the value passed to `--queries` with the `+` symbol. +For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)." -在下面的示例中,`+` 符号可确保 {% data variables.product.prodname_codeql_runner %} 结合使用额外查询与所引用配置文件中指定的任何查询。 +In the following example, the `+` symbol ensures that the {% data variables.product.prodname_codeql_runner %} uses the additional queries together with any queries specified in the referenced configuration file. ```shell $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml --queries +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main ``` -## 使用自定义配置文件 +## Using a custom configuration file -您可以在单独的配置文件中指定自定义设置,而不向 {% data variables.product.prodname_codeql_runner %} 命令传递额外信息。 +Instead of passing additional information to the {% data variables.product.prodname_codeql_runner %} commands, you can specify custom settings in a separate configuration file. -配置文件为 YAML 文件。 它使用的语法类似于 {% data variables.product.prodname_actions %} 的工作流程语法,如下例所示。 有关详细信息,请参阅“[{% data variables.product.prodname_actions %} 的工作流语法](/actions/reference/workflow-syntax-for-github-actions)”。 +The configuration file is a YAML file. It uses syntax similar to the workflow syntax for {% data variables.product.prodname_actions %}, as illustrated in the examples below. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)." -使用 `init` 命令的 `--config-file` 标志指定配置文件。 `--config-file` 的值是要使用的配置文件的路径。 此示例加载配置文件 .github/codeql/codeql-config.yml。 +Use the `--config-file` flag of the `init` command to specify the configuration file. The value of `--config-file` is the path to the configuration file that you want to use. This example loads the configuration file _.github/codeql/codeql-config.yml_. ```shell $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml @@ -111,108 +109,108 @@ $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-c {% data reusables.code-scanning.custom-configuration-file %} -### 示例配置文件 +### Example configuration files {% data reusables.code-scanning.example-configuration-files %} -## 为编译语言配置 {% data variables.product.prodname_code_scanning %} +## Configuring {% data variables.product.prodname_code_scanning %} for compiled languages -对于编译语言 C/C++、C# 和 Java,{% data variables.product.prodname_codeql %} 在分析之前构建代码。 {% data reusables.code-scanning.analyze-go %} +For the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} builds the code before analyzing it. {% data reusables.code-scanning.analyze-go %} -对于许多常见的构建系统,{% data variables.product.prodname_codeql_runner %} 可以自动构建代码。 要尝试自动生成代码,请在步骤 `init` 和 `analyze` 之间运行 `autobuild`。 请注意,如果您的仓库需要特定版本的构建工具,您可能需要先手动安装该构建工具。 +For many common build systems, the {% data variables.product.prodname_codeql_runner %} can build the code automatically. To attempt to build the code automatically, run `autobuild` between the `init` and `analyze` steps. Note that if your repository requires a specific version of a build tool, you may need to install the build tool manually first. -`autobuild` 过程仅尝试为存储库生成一种编译语言。 自动选择用于分析的语言是涵盖文件最多的语言。 如果要明确选择一种语言,请使用 `autobuild` 命令的 `--language` 标志。 +The `autobuild` process only ever attempts to build _one_ compiled language for a repository. The language automatically selected for analysis is the language with the most files. If you want to choose a language explicitly, use the `--language` flag of the `autobuild` command. ```shell $ /path/to-runner/codeql-runner-linux autobuild --language csharp ``` -如果 `autobuild` 命令无法生成代码,可以在步骤 `init` 和 `analyze` 之间自行运行生成步骤。 有关详细信息,请参阅“[在 CI 系统中运行 {% data variables.product.prodname_codeql_runner %}](/code-security/secure-coding/running-codeql-runner-in-your-ci-system#compiled-language-example)”。 +If the `autobuild` command can't build your code, you can run the build steps yourself, between the `init` and `analyze` steps. For more information, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system#compiled-language-example)." -## 将 {% data variables.product.prodname_code_scanning %} 数据上传到 {% data variables.product.prodname_dotcom %} +## Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %} -默认情况下,当你运行 `analyze` 命令时,{% data variables.product.prodname_codeql_runner %} 会上传来自 {% data variables.product.prodname_code_scanning %} 的结果。 还可以使用 `upload` 命令单独上传 SARIF 文件。 +By default, the {% data variables.product.prodname_codeql_runner %} uploads results from {% data variables.product.prodname_code_scanning %} when you run the `analyze` command. You can also upload SARIF files separately, by using the `upload` command. -上传数据后,{% data variables.product.prodname_dotcom %} 将在您的仓库中显示警报。 -- 如果已上传到拉取请求,例如 `--ref refs/pull/42/merge` 或 `--ref refs/pull/42/head`,则结果会在拉取请求检查中显示为警报。 有关详细信息,请参阅[在拉取请求中对代码扫描警报进行会审](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)。 -- 如果已上传到分支,例如 `--ref refs/heads/my-branch`,则结果会显示在存储库的“安全”选项卡中。 有关详细信息,请参阅“[管理存储库的代码扫描警报](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)”。 +Once you've uploaded the data, {% data variables.product.prodname_dotcom %} displays the alerts in your repository. +- If you uploaded to a pull request, for example `--ref refs/pull/42/merge` or `--ref refs/pull/42/head`, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." +- If you uploaded to a branch, for example `--ref refs/heads/my-branch`, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." -## {% data variables.product.prodname_codeql_runner %} 命令引用 +## {% data variables.product.prodname_codeql_runner %} command reference -{% data variables.product.prodname_codeql_runner %} 支持以下命令和标志。 +The {% data variables.product.prodname_codeql_runner %} supports the following commands and flags. ### `init` -为每种要分析的语言初始化 {% data variables.product.prodname_codeql_runner %} 并创建 {% data variables.product.prodname_codeql %} 数据库。 +Initializes the {% data variables.product.prodname_codeql_runner %} and creates a {% data variables.product.prodname_codeql %} database for each language to be analyzed. -| 标志 | 必需 | 输入值 | +| Flag | Required | Input value | | ---- |:--------:| ----------- | -| `--repository` | ✓ | 要初始化的仓库名称。 | -| `--github-url` | ✓ | 托管仓库的 {% data variables.product.prodname_dotcom %} 实例的 URL。 | -| `--github-auth-stdin` | ✓ | 从标准输入读取 {% data variables.product.prodname_github_apps %} 令牌或个人访问令牌。 | -| `--languages` | | 要分析的语言列表,以逗号分隔。 默认情况下,{% data variables.product.prodname_codeql_runner %} 检测和分析仓库中所有支持的语言。 | -| `--queries` | | 除了默认的安全查询套件之外,要运行的额外查询列表,以逗号分隔。 这会覆盖自定义配置文件中的 `queries` 设置。 | -| `--config-file` | | 自定义配置文件的路径。 | -| `--codeql-path` | | 要使用的 {% data variables.product.prodname_codeql %} CLI 可执行文件副本的路径。 默认情况下,{% data variables.product.prodname_codeql_runner %} 下载副本。 | -| `--temp-dir` | | 存储临时文件的目录。 默认为 `./codeql-runner`。 | -| `--tools-dir` | | 在运行之间存储 {% data variables.product.prodname_codeql %} 工具和其他文件的目录。 默认值为主目录的子目录。 | -| `--checkout-path` | | 检出仓库的路径。 默认值为当前工作目录。 | -| `--debug` | | 无。 打印更详细的输出。 | -| `--trace-process-name` | | Advanced, Windows only. 注入此进程的 Windows 追踪器的过程名称。 | -| `--trace-process-level` | | Advanced, Windows only. 注入此进程的 Windows 追踪器的父进程级别数。 | -| `-h`, `--help` | | 无。 显示命令的帮助。 | +| `--repository` | ✓ | Name of the repository to initialize. | +| `--github-url` | ✓ | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted. | +| `--github-auth-stdin` | ✓ | Read the {% data variables.product.prodname_github_apps %} token or {% data variables.product.pat_generic %} from standard input. | +| `--languages` | | Comma-separated list of languages to analyze. By default, the {% data variables.product.prodname_codeql_runner %} detects and analyzes all supported languages in the repository. | +| `--queries` | | Comma-separated list of additional queries to run, in addition to the default suite of security queries. This overrides the `queries` setting in the custom configuration file. | +| `--config-file` | | Path to custom configuration file. | +| `--codeql-path` | | Path to a copy of the {% data variables.product.prodname_codeql %} CLI executable to use. By default, the {% data variables.product.prodname_codeql_runner %} downloads a copy. | +| `--temp-dir` | | Directory where temporary files are stored. The default is `./codeql-runner`. | +| `--tools-dir` | | Directory where {% data variables.product.prodname_codeql %} tools and other files are stored between runs. The default is a subdirectory of the home directory. | +| `--checkout-path` | | The path to the checkout of your repository. The default is the current working directory. | +| `--debug` | | None. Prints more verbose output. | +| `--trace-process-name` | | Advanced, Windows only. Name of the process where a Windows tracer of this process is injected. | +| `--trace-process-level` | | Advanced, Windows only. Number of levels up of the parent process where a Windows tracer of this process is injected. | +| `-h`, `--help` | | None. Displays help for the command. | ### `autobuild` -尝试为编译语言 C/C++、C# 和 Java 构建代码。 对于这些语言,{% data variables.product.prodname_codeql %} 在分析之前构建代码。 在步骤 `init` 和 `analyze` 之间运行 `autobuild`。 +Attempts to build the code for the compiled languages C/C++, C#, and Java. For those languages, {% data variables.product.prodname_codeql %} builds the code before analyzing it. Run `autobuild` between the `init` and `analyze` steps. -| 标志 | 必需 | 输入值 | +| Flag | Required | Input value | | ---- |:--------:| ----------- | -| `--language` | | 要构建的语言。 默认情况下,{% data variables.product.prodname_codeql_runner %} 构建涵盖最多文件的编译语言。 | -| `--temp-dir` | | 存储临时文件的目录。 默认为 `./codeql-runner`。 | -| `--debug` | | 无。 打印更详细的输出。 | -| `-h`, `--help` | | 无。 显示命令的帮助。 | +| `--language` | | The language to build. By default, the {% data variables.product.prodname_codeql_runner %} builds the compiled language with the most files. | +| `--temp-dir` | | Directory where temporary files are stored. The default is `./codeql-runner`. | +| `--debug` | | None. Prints more verbose output. | +| `-h`, `--help` | | None. Displays help for the command. | ### `analyze` -分析 {% data variables.product.prodname_codeql %} 数据库中的代码并将结果上传到 {% data variables.product.product_name %}。 +Analyzes the code in the {% data variables.product.prodname_codeql %} databases and uploads results to {% data variables.product.product_name %}. -| 标志 | 必需 | 输入值 | +| Flag | Required | Input value | | ---- |:--------:| ----------- | -| `--repository` | ✓ | 要分析的仓库名称。 | -| `--commit` | ✓ | 要分析的提交的 SHA。 在 Git 和 Azure DevOps 中,这对应于 `git rev-parse HEAD` 的值。 在 Jenkins 中,这对应于 `$GIT_COMMIT`。 | -| `--ref` | ✓ | 要分析的引用的名称,例如 `refs/heads/main` 或 `refs/pull/42/merge`。 在 Git 或 Jenkins 中,这对应于 `git symbolic-ref HEAD` 的值。 在 Azure DevOps 中,这对应于 `$(Build.SourceBranch)`。 | -| `--github-url` | ✓ | 托管仓库的 {% data variables.product.prodname_dotcom %} 实例的 URL。 | -| `--github-auth-stdin` | ✓ | 从标准输入读取 {% data variables.product.prodname_github_apps %} 令牌或个人访问令牌。 | -| `--checkout-path` | | 检出仓库的路径。 默认值为当前工作目录。 | -| `--no-upload` | | 无。 阻止 {% data variables.product.prodname_codeql_runner %} 将结果上传到 {% data variables.product.product_name %}。 | -| `--output-dir` | | 存储输出 SARIF 文件的目录。 默认在临时文件目录中。 | -| `--ram` | | 运行查询时要使用的内存量。 默认使用所有可用的内存。 | -| `--no-add-snippets` | | 无。 从 SARIF 输出排除代码片段。 | -| `--category` | | 用于此分析的 SARIF 结果文件中要包含的类别。 类别可用于区分同一工具和提交的多次分析,但是在不同语言或代码的不同部分进行。 该值将显示在 SARIF v2.1.0 中的 `.automationDetails.id` 属性中。 | -| `--threads` | | 运行查询时要使用的线程数。 默认使用所有可用的核心。 | -| `--temp-dir` | | 存储临时文件的目录。 默认为 `./codeql-runner`。 | -| `--debug` | | 无。 打印更详细的输出。 | -| `-h`, `--help` | | 无。 显示命令的帮助。 | +| `--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` or `refs/pull/42/merge`. In Git or 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-stdin` | ✓ | Read the {% data variables.product.prodname_github_apps %} token or {% data variables.product.pat_generic %} from standard input. | +| `--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_name %}. | +| `--output-dir` | | Directory where the output SARIF files are stored. The default is in the directory of temporary files. | +| `--ram` | | Amount of memory to use when running queries. The default is to use all available memory. | +| `--no-add-snippets` | | None. Excludes code snippets from the SARIF output. | +| `--category` | | Category to include in the SARIF results file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the `.automationDetails.id` property in SARIF v2.1.0. | +| `--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. | ### `upload` -将 SARIF 文件上传到 {% data variables.product.product_name %}。 +Uploads SARIF files to {% data variables.product.product_name %}. {% note %} -注意:如果使用 CodeQL 运行器分析代码,则 `analyze` 命令默认上传 SARIF 结果。 可以使用 `upload` 命令上传由其他工具生成的 SARIF 结果。 +**Note**: If you analyze code with the CodeQL runner, the `analyze` command uploads SARIF results by default. You can use the `upload` command to upload SARIF results that were generated by other tools. {% endnote %} -| 标志 | 必需 | 输入值 | +| Flag | Required | Input value | | ---- |:--------:| ----------- | -| `--sarif-file` | ✓ | 要上传的 SARIF 文件,或包含多个 SARIF 文件的目录。 | -| `--repository` | ✓ | 已分析的仓库名称。 | -| `--commit` | ✓ | 已分析的提交的 SHA。 在 Git 和 Azure DevOps 中,这对应于 `git rev-parse HEAD` 的值。 在 Jenkins 中,这对应于 `$GIT_COMMIT`。 | -| `--ref` | ✓ | 已分析的引用的名称,例如 `refs/heads/main` 或 `refs/pull/42/merge`。 在 Git 或 Jenkins 中,这对应于 `git symbolic-ref HEAD` 的值。 在 Azure DevOps 中,这对应于 `$(Build.SourceBranch)`。 | -| `--github-url` | ✓ | 托管仓库的 {% data variables.product.prodname_dotcom %} 实例的 URL。 | -| `--github-auth-stdin` | ✓ | 从标准输入读取 {% data variables.product.prodname_github_apps %} 令牌或个人访问令牌。 | -| `--checkout-path` | | 检出仓库的路径。 默认值为当前工作目录。 | -| `--debug` | | 无。 打印更详细的输出。 | -| `-h`, `--help` | | 无。 显示命令的帮助。 | +| `--sarif-file` | ✓ | SARIF file to upload, or a directory containing multiple SARIF files. | +| `--repository` | ✓ | Name of the repository that was analyzed. | +| `--commit` | ✓ | SHA of the commit that was analyzed. In Git and in Azure DevOps, this corresponds to the value of `git rev-parse HEAD`. In Jenkins, this corresponds to `$GIT_COMMIT`. | +| `--ref` | ✓ | Name of the reference that was analyzed, for example `refs/heads/main` or `refs/pull/42/merge`. In Git or 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-stdin` | ✓ | Read the {% data variables.product.prodname_github_apps %} token or {% data variables.product.pat_generic %} from standard input. | +| `--checkout-path` | | The path to the checkout of your repository. The default is the current working directory. | +| `--debug` | | None. Prints more verbose output. | +| `-h`, `--help` | | None. Displays help for the command. | diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md index 28ef5c6e85..8ad9bee420 100644 --- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md +++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md @@ -112,7 +112,7 @@ You should check that the output contains the expected languages and also that t ## Generating a token for authentication with {% data variables.product.product_name %} -Each CI server needs a {% data variables.product.prodname_github_app %} or personal access token for the {% data variables.product.prodname_codeql_cli %} to use to upload results to {% data variables.product.product_name %}. You must use an access token or a {% data variables.product.prodname_github_app %} with the `security_events` write permission. If CI servers already use a token with this scope to checkout repositories from {% data variables.product.product_name %}, you could potentially allow the {% data variables.product.prodname_codeql_cli %} to use the same token. Otherwise, you should create a new token with the `security_events` write permission and add this to the CI system's secret store. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +Each CI server needs a {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} for the {% data variables.product.prodname_codeql_cli %} to use to upload results to {% data variables.product.product_name %}. You must use an access token or a {% data variables.product.prodname_github_app %} with the `security_events` write permission. If CI servers already use a token with this scope to checkout repositories from {% data variables.product.product_name %}, you could potentially allow the {% data variables.product.prodname_codeql_cli %} to use the same token. Otherwise, you should create a new token with the `security_events` write permission and add this to the CI system's secret store. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." ## Next steps diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md index 69da5fbdac..a2056c24bf 100644 --- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md +++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md @@ -1,7 +1,7 @@ --- -title: 在 CI 系统中运行 CodeQL 运行器 +title: Running CodeQL runner in your CI system shortTitle: Run CodeQL runner -intro: '您可以使用 {% data variables.product.prodname_codeql_runner %} 在第三方持续集成系统中执行 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}。' +intro: 'You can use the {% data variables.product.prodname_codeql_runner %} to perform {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in a third-party continuous integration system.' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system @@ -24,102 +24,102 @@ topics: - Integration - CI - SARIF -ms.openlocfilehash: c4803ff75aa157bc89dc2bfa776c03b3a1cf305a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146178677' --- + {% ifversion codeql-runner-supported %} -{% data reusables.code-scanning.deprecation-codeql-runner %} {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} +{% data reusables.code-scanning.deprecation-codeql-runner %} +{% data reusables.code-scanning.beta %} +{% data reusables.code-scanning.enterprise-enable-code-scanning %} -## 关于 {% data variables.product.prodname_codeql_runner %} +## About the {% data variables.product.prodname_codeql_runner %} -{% data variables.product.prodname_codeql_runner %} 是可以用来在第三方持续集成 (CI) 系统中处理的代码上运行 {% data variables.product.prodname_code_scanning %} 的工具。 {% data reusables.code-scanning.about-code-scanning %} 有关信息,请参阅“[关于使用 {% data variables.product.prodname_codeql %} 进行 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)”。 +The {% data variables.product.prodname_codeql_runner %} is a tool you can use to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." -在许多情况下,在 CI 系统中直接使用 {% data variables.product.prodname_codeql_cli %} 设置 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 更简单。 +In many cases it is easier to set up {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_cli %} directly in your CI system. -您也可以使用 {% data variables.product.prodname_actions %} 在 {% data variables.product.product_name %} 中运行 {% data variables.product.prodname_code_scanning %}。 有关信息,请参阅“[为存储库设置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)”。 +Alternatively, you can use {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %}. For information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/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_name %}。 这些结果在仓库中显示为 {% data variables.product.prodname_code_scanning %} 警报。 +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_name %}. These results are displayed as {% data variables.product.prodname_code_scanning %} alerts in the repository. {% note %} -注意:{% ifversion fpt or ghec %} -* {% data variables.product.prodname_codeql_runner %} 使用 {% data variables.product.prodname_codeql %} CLI 来分析代码,因此具有相同的许可条件。 它可自由用于 {% data variables.product.prodname_dotcom_the_website %} 上维护的公共仓库,并且可用于具有 {% data variables.product.prodname_advanced_security %} 许可证的客户所拥有的私有仓库。 有关信息,请参阅“[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} 条款和条件](https://securitylab.github.com/tools/codeql/license)”以及“[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)”。 +**Note:** +{% ifversion fpt or ghec %} +* The {% data variables.product.prodname_codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. It's free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." {% else %} -* {% data variables.product.prodname_codeql_runner %} 可用于拥有 {% data variables.product.prodname_advanced_security %} 许可证的客户。 -{% endif %} {% ifversion ghae %} -* 请勿将 {% data variables.product.prodname_codeql_runner %} 与 {% data variables.product.prodname_codeql %} CLI 混淆。 {% data variables.product.prodname_codeql %} CLI 是一个命令行接口,允许您创建用于安全研究的 {% data variables.product.prodname_codeql %} 数据库并运行 {% data variables.product.prodname_codeql %} 查询。 -有关详细信息,请参阅“[{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/)”。 -{% endif %} {% endnote %} +* The {% data variables.product.prodname_codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license. +{% endif %} +{% ifversion ghae %} +* The {% data variables.product.prodname_codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is a command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries. +For more information, see "[{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/)." +{% endif %} +{% endnote %} -## 下载 {% data variables.product.prodname_codeql_runner %} +## Downloading the {% data variables.product.prodname_codeql_runner %} -可以从 https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases 下载 {% data variables.product.prodname_codeql_runner %}。 在某些操作系统上,您可能需要更改下载文件的权限才能运行它。 +You can download the {% data variables.product.prodname_codeql_runner %} from https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it. -在 Linux 上: +On Linux: ```shell chmod +x codeql-runner-linux ``` -在 macOS 上: +On macOS: ```shell chmod +x codeql-runner-macos sudo xattr -d com.apple.quarantine codeql-runner-macos ``` -在 Windows 中,`codeql-runner-win.exe` 文件通常无需更改权限。 +On Windows, the `codeql-runner-win.exe` file usually requires no change to permissions. -## 将 {% data variables.product.prodname_codeql_runner %} 添加到 CI 系统 +## Adding the {% data variables.product.prodname_codeql_runner %} to your CI system -下载 {% data variables.product.prodname_codeql_runner %} 并确认它可执行后,应将运行器提供给您打算用于 {% data variables.product.prodname_code_scanning %} 的每个 CI 服务器。 例如,您可以配置每台服务器从中央内部位置复制运行器。 或者,您也可以使用 REST API 直接从 {% data variables.product.prodname_dotcom %} 获取运行器,例如: +Once you download the {% data variables.product.prodname_codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from {% data variables.product.prodname_dotcom %}, for example: ```shell -wget https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux +wget https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux chmod +x codeql-runner-linux ``` -除此之外,每个 CI 服务器还需要: +In addition to this, each CI server also needs: -- 一个供 {% data variables.product.prodname_codeql_runner %} 使用的 {% data variables.product.prodname_github_app %} 或个人访问令牌。 必须使用具有 `repo` 范围的访问令牌,或具有 `security_events` 写入权限和 `metadata` 与 `contents` 读取权限的 {% data variables.product.prodname_github_app %}。 有关信息,请参阅“[生成 {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)”和“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 -- 访问与此 {% data variables.product.prodname_codeql_runner %} 发行版相关联的 {% data variables.product.prodname_codeql %} 包。 此包包含 {% data variables.product.prodname_codeql %} 分析所需的查询和库,以及供运行器内部使用的 {% data variables.product.prodname_codeql %} CLI。 有关信息,请参阅“[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)”。 +- A {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} for the {% data variables.product.prodname_codeql_runner %} to use. You must use an access token with the `repo` scope, or a {% data variables.product.prodname_github_app %} with the `security_events` write permission, and `metadata` and `contents` read permissions. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." +- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.product.prodname_codeql_runner %}. This package contains queries and libraries needed for {% data variables.product.prodname_codeql %} analysis, plus the {% data variables.product.prodname_codeql %} CLI, which is used internally by the runner. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." -提供 {% data variables.product.prodname_codeql %} 包访问权限的选项: +The options for providing access to the {% data variables.product.prodname_codeql %} bundle are: -1. 允许 CI 服务器访问 https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action,以便 {% data variables.product.prodname_codeql_runner %} 可以自动下载包。 -1. 手动下载/提取包,将其与其他中心资源一起存储,并使用 `--codeql-path` 标志指定包在调用中的位置以初始化 {% data variables.product.prodname_codeql_runner %}。 +1. Allow the CI servers access to https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action so that the {% data variables.product.prodname_codeql_runner %} can download the bundle automatically. +1. Manually download/extract the bundle, store it with other central resources, and use the `--codeql-path` flag to specify the location of the bundle in calls to initialize the {% data variables.product.prodname_codeql_runner %}. -## 调用 {% data variables.product.prodname_codeql_runner %} +## Calling the {% data variables.product.prodname_codeql_runner %} -您应该从要分析的仓库的检出位置调用 {% data variables.product.prodname_codeql_runner %}。 两个主要命令是: +You should call the {% data variables.product.prodname_codeql_runner %} from the checkout location of the repository you want to analyze. The two main commands are: -1. `init` 需要初始化运行器并为需要分析的每种语言创建一个 {% data variables.product.prodname_codeql %} 数据库。 这些数据库由后续命令填充和分析。 -1. `analyze` 需要填充 {% data variables.product.prodname_codeql %} 数据库、分析它们并将结果上传到 {% data variables.product.product_name %}。 +1. `init` required to initialize the runner and create a {% data variables.product.prodname_codeql %} database for each language to be analyzed. These databases are populated and analyzed by subsequent commands. +1. `analyze` required to populate the {% data variables.product.prodname_codeql %} databases, analyze them, and upload results to {% data variables.product.product_name %}. -对于这两个命令,都必须指定 {% data variables.product.product_name %} 的 URL、存储库 OWNER/NAME 以及 {% data variables.product.prodname_github_apps %} 或用于身份验证的个人访问令牌。 还需要指定 CodeQL 包的位置,除非 CI 服务器有权直接从 `github/codeql-action` 存储库下载它。 +For both commands, you must specify the URL of {% data variables.product.product_name %}, the repository *OWNER/NAME*, and the {% data variables.product.prodname_github_apps %} or {% data variables.product.pat_generic %} to use for authentication. You also need to specify the location of the CodeQL bundle, unless the CI server has access to download it directly from the `github/codeql-action` repository. -可以配置 {% data variables.product.prodname_codeql_runner %} 存储 CodeQL 包的位置,以便将来使用 `--tools-dir` 标志在服务器上进行分析,还可配置在使用 `--temp-dir` 进行分析的过程中储存临时文件的位置。 +You can configure where the {% data variables.product.prodname_codeql_runner %} stores the CodeQL bundle for future analysis on a server using the `--tools-dir` flag and where it stores temporary files during analysis using `--temp-dir`. -要查看运行器的命令行引用,请使用 `-h` 标志。 例如,要列出所有命令,请运行:`codeql-runner-OS -h`,或者要列出可用于 `init` 命令的所有标志,请运行:`codeql-runner-OS init -h`(其中 `OS` 因你使用的可执行文件而异)。 有关详细信息,请参阅“[在 CI 系统中配置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system#codeql-runner-command-reference)”。 +To view the command-line reference for the runner, use the `-h` flag. For example, to list all commands run: `codeql-runner-OS -h`, or to list all the flags available for the `init` command run: `codeql-runner-OS init -h` (where `OS` varies according to the executable that you are using). For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system#codeql-runner-command-reference)." {% data reusables.code-scanning.upload-sarif-alert-limit %} -### 基本示例 +### Basic example -此示例在 Linux CI 服务器上为托管在 `{% data variables.command_line.git_url_example %}` 上的 `octo-org/example-repo` 存储库运行 {% data variables.product.prodname_codeql %} 分析。 这个过程非常简单,因为仓库只包含可通过 {% data variables.product.prodname_codeql %} 直接分析的语言,而无需构建(例如 Go、JavaScript、Python 和 TypeScript)。 +This example runs {% data variables.product.prodname_codeql %} analysis on a Linux CI server for the `octo-org/example-repo` repository hosted on `{% data variables.command_line.git_url_example %}`. The process is very simple because the repository contains only languages that can be analyzed by {% data variables.product.prodname_codeql %} directly, without being built (that is, Go, JavaScript, Python, and TypeScript). -在此示例中,服务器有权直接从 `github/codeql-action` 存储库下载 {% data variables.product.prodname_codeql %} 包,因此无需使用 `--codeql-path` 标志。 +In this example, the server has access to download the {% data variables.product.prodname_codeql %} bundle directly from the `github/codeql-action` repository, so there is no need to use the `--codeql-path` flag. -1. 检出要分析的仓库。 -1. 移至检出仓库的目录。 -1. 初始化 {% data variables.product.prodname_codeql_runner %} 并为检测到的语言创建 {% data variables.product.prodname_codeql %}。 +1. Check out the repository to analyze. +1. Move into the directory where the repository is checked out. +1. Initialize the {% data variables.product.prodname_codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected. ```shell $ echo "$TOKEN" | /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo @@ -131,13 +131,13 @@ chmod +x codeql-runner-linux {% data reusables.code-scanning.codeql-runner-analyze-example %} -### 编译语言示例 +### Compiled language example -此示例与前面的示例相似,但此例中的仓库含有用 C/C++、C# 或 Java 编写的代码。 要为这些语言创建 {% data variables.product.prodname_codeql %} 数据库,CLI 需要监控构建。 在初始化过程结束时,运行器会报告您需要在构建代码之前设置环境的命令。 你需要在调用正常的 CI 构建进程之前运行此命令,然后运行 `analyze` 命令。 +This example is similar to the previous example, however this time the repository has code in C/C++, C#, or Java. To create a {% data variables.product.prodname_codeql %} database for these languages, the CLI needs to monitor the build. At the end of the initialization process, the runner reports the command you need to set up the environment before building the code. You need to run this command, before calling the normal CI build process, and then running the `analyze` command. -1. 检出要分析的仓库。 -1. 移至检出仓库的目录。 -1. 初始化 {% data variables.product.prodname_codeql_runner %} 并为检测到的语言创建 {% data variables.product.prodname_codeql %}。 +1. Check out the repository to analyze. +1. Move into the directory where the repository is checked out. +1. Initialize the {% data variables.product.prodname_codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected. ```shell $ echo "$TOKEN" | /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2 --github-url {% data variables.command_line.git_url_example %} --github-auth-stdin @@ -148,37 +148,37 @@ chmod +x codeql-runner-linux Please export these variables to future processes so that CodeQL can monitor the build, for example by running ". /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh". ``` -1. 获取由 `init` 操作生成的脚本以设置环境,从而监视生成。 请注意以下代码片段中的先导点和空间。 +1. Source the script generated by the `init` action to set up the environment to monitor the build. Note the leading dot and space in the following code snippet. ```shell $ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh ``` -1. 构建代码。 在 macOS 上,需要使用环境变量 `$CODEQL_RUNNER` 为构建命令添加前缀。 有关详细信息,请参阅“[对 CI 系统中的 {% data variables.product.prodname_codeql_runner %} 进行故障排除](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)”。 +1. Build the code. On macOS, you need to prefix the build command with the environment variable `$CODEQL_RUNNER`. For more information, see "[Troubleshooting {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)." {% data reusables.code-scanning.codeql-runner-analyze-example %} {% note %} -注意:如果使用容器化构建,则需要在构建任务的容器中运行 {% data variables.product.prodname_codeql_runner %}。 +**Note:** If you use a containerized build, you need to run the {% data variables.product.prodname_codeql_runner %} in the container where your build task takes place. {% endnote %} -## 延伸阅读 +## Further reading -- [在 CI 系统中配置 {% data variables.product.prodname_codeql_runner %}](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system) -- [对 CI 系统中的 {% data variables.product.prodname_codeql_runner %} 进行故障排除](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system) +- "[Configuring {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)" +- "[Troubleshooting {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system)" {% else %} -## 关于 {% data variables.product.prodname_codeql_runner %} +## About the {% data variables.product.prodname_codeql_runner %} -{% data variables.product.prodname_codeql_runner %} 已被弃用。 [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-cli-binaries/releases) 版本 2.7.6 具有完整的功能奇偶一致性。 +The {% data variables.product.prodname_codeql_runner %} has been deprecated. [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-cli-binaries/releases) version 2.7.6 has complete feature parity. -有关迁移到 {% data variables.product.prodname_codeql_cli %} 的信息,请参阅“[从 CodeQL 运行器迁移到 CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)”。 +For information on migrating to {% data variables.product.prodname_codeql_cli %}, see "[Migrating from the CodeQL runner to CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)." -## 延伸阅读 +## Further reading -- GitHub 博客中的 [CodeQL 运行器弃用](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/) +- [CodeQL runner deprecation](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/) in the GitHub Blog {% endif %} diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md index d92f7570d6..fa3ad2ded3 100644 --- a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md +++ b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md @@ -1,6 +1,6 @@ --- -title: 关于 Dependabot 警报 -intro: '当我们检测到存储库使用易受攻击的依赖项{% ifversion GH-advisory-db-supports-malware %} 或恶意软件{% endif %} 时,{% data variables.product.product_name %} 发送 {% data variables.product.prodname_dependabot_alerts %}。' +title: About Dependabot alerts +intro: '{% data variables.product.product_name %} sends {% data variables.product.prodname_dependabot_alerts %} when we detect that your repository uses a vulnerable dependency{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}.' redirect_from: - /articles/about-security-alerts-for-vulnerable-dependencies - /github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies @@ -20,87 +20,87 @@ topics: - Repositories - Dependencies shortTitle: Dependabot alerts -ms.openlocfilehash: 4a1e85a620465247dcd63e8ce9c88c99a0af31fd -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147526732' --- -## 关于 {% data variables.product.prodname_dependabot_alerts %} +## About {% data variables.product.prodname_dependabot_alerts %} -{% ifversion GH-advisory-db-supports-malware %} {% data reusables.advisory-database.beta-malware-advisories %} {% endif %} +{% ifversion GH-advisory-db-supports-malware %} +{% data reusables.advisory-database.beta-malware-advisories %} +{% endif %} -{% data variables.product.prodname_dependabot_alerts %} 告知代码依赖于不安全的包。 +{% data variables.product.prodname_dependabot_alerts %} tell you that your code depends on a package that is insecure. -当代码依赖于具有安全漏洞的包时,这可能会导致项目或使用它的人遇到一系列问题。 应尽快升级到该包的安全版本。{% ifversion GH-advisory-db-supports-malware %} 如果代码使用恶意软件,则需要将包替换为安全的替代项。{% endif %} +If your code depends on a package with a security vulnerability, this can cause a range of problems for your project or the people who use it. You should upgrade to a secure version of the package as soon as possible.{% ifversion GH-advisory-db-supports-malware %} If your code uses malware, you need to replace the package with a secure alternative.{% endif %} {% data reusables.security-advisory.link-browsing-advisory-db %} -## 不安全依赖项的检测 +## Detection of insecure dependencies {% data reusables.dependabot.dependabot-alerts-beta %} -{% data variables.product.prodname_dependabot %} 执行扫描以检测不安全的依赖关系,并在以下情况下发送 {% data variables.product.prodname_dependabot_alerts %} : +{% data variables.product.prodname_dependabot %} performs a scan to detect insecure dependencies, and sends {% data variables.product.prodname_dependabot_alerts %} when: {% ifversion fpt or ghec %} -- 新公告添加到 {% data variables.product.prodname_advisory_database %}。 有关详细信息,请参阅“[在 {% data variables.product.prodname_advisory_database %} 中浏览安全公告](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database)”。{% else %} -- 新公告数据每小时从 {% data variables.product.prodname_dotcom_the_website %} 同步到 {% data variables.product.product_location %}。 {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %} {% note %} +- A new advisory is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database)."{% else %} +- New advisory data is synchronized to {% data variables.location.product_location %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %} + {% note %} - 注意:只有经过 {% data variables.product.company_short %} 审核的公告才会触发 {% data variables.product.prodname_dependabot_alerts %}。 + **Note:** Only advisories that have been reviewed by {% data variables.product.company_short %} will trigger {% data variables.product.prodname_dependabot_alerts %}. {% endnote %} -- 存储库的依赖项关系图发生更改。 例如,当参与者推送提交以更改所依赖的包或版本时{% ifversion fpt or ghec %},或者当某个依赖项的代码发生更改时{% endif %}。 有关详细信息,请参阅“[关于依赖项关系图](/code-security/supply-chain-security/about-the-dependency-graph)”。 +- The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% ifversion fpt or ghec %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/code-security/supply-chain-security/about-the-dependency-graph)." {% data reusables.repositories.dependency-review %} -有关 {% data variables.product.product_name %} 检测到其中不安全的依赖项的生态系统列表,请参阅“[支持的包生态系统](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)”。 +For a list of the ecosystems that {% data variables.product.product_name %} detects insecure dependencies in, see "[Supported package ecosystems](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." {% note %} -注意:保持清单和锁定文件处于最新状态非常重要。 如果依赖关系图不能准确反映你当前的依赖项和版本,则可能错过有关你使用的不安全依赖项的警报。 您还可以收到不再使用的依赖项的警报。 +**Note:** It is important to keep your manifest and lock files up to date. If the dependency graph doesn't accurately reflect your current dependencies and versions, then you could miss alerts for insecure dependencies that you use. You may also get alerts for dependencies that you no longer use. {% endnote %} -## {% data variables.product.prodname_dependabot_alerts %} 的配置 +## Configuration of {% data variables.product.prodname_dependabot_alerts %} {% data reusables.repositories.enable-security-alerts %} -{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} 检测公共存储库中易受攻击的依赖项和恶意软件并显示依赖项关系图,但默认情况下不会生成 {% data variables.product.prodname_dependabot_alerts %}。 仓库所有者或具有管理员访问权限的人员可以为公共公共仓库启用 {% data variables.product.prodname_dependabot_alerts %}。 私有仓库的所有者或具有管理员权限的人员可以通过为其仓库启用依赖关系图和 {% data variables.product.prodname_dependabot_alerts %} 来启用 {% data variables.product.prodname_dependabot_alerts %}。 +{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerable dependencies and malware in _public_ repositories and displays the dependency graph, but does not generate {% data variables.product.prodname_dependabot_alerts %} by default. Repository owners or people with admin access can enable {% data variables.product.prodname_dependabot_alerts %} for public repositories. Owners of private repositories, or people with admin access, can enable {% data variables.product.prodname_dependabot_alerts %} by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for their repositories. -你也可以为用户帐户或组织拥有的所有存储库启用或禁用 {% data variables.product.prodname_dependabot_alerts %}。 有关详细信息,请参阅“[配置 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts)”。 +You can also enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories owned by your user account or organization. For more information, see "[Configuring {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts)." -有关 {% data variables.product.prodname_dependabot_alerts %} 相关操作的访问要求的信息,请参阅“[组织的存储库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#access-requirements-for-security-features)”。 +For information about access requirements for actions related to {% data variables.product.prodname_dependabot_alerts %}, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#access-requirements-for-security-features)." -{% data variables.product.product_name %} 将立即开始生成依赖关系图,并在发现任何不安全的依赖项后立即生成警报。 依赖关系图通常在几分钟之内填充,但对于依赖项很多的仓库,可能需要更长时间。 有关详细信息,请参阅“[管理专用存储库的数据使用设置](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)”。 +{% data variables.product.product_name %} starts generating the dependency graph immediately and generates alerts for any insecure dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "[Managing data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)." {% endif %} -当 {% data variables.product.product_name %} 发现易受攻击的依赖项{% ifversion GH-advisory-db-supports-malware %} 或恶意软件时{% endif %},我们会生成 {% data variables.product.prodname_dependabot %} 警报,并将其显示{% ifversion fpt or ghec or ghes %}在存储库的“安全”选项卡上和{% endif %}在存储库的依赖项关系图中。 警报包括项目中受影响文件的{% ifversion fpt or ghec or ghes %}链接,以及{% endif %}有关已修复的版本的信息。 {% data variables.product.product_name %} 还可能根据受影响仓库的管理员的通知首选项向他们通知新的警报。 有关详细信息,请参阅“[配置 {% data variables.product.prodname_dependabot_alerts %} 的通知](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)”。 +When {% data variables.product.product_name %} identifies a vulnerable dependency{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}, we generate a {% data variables.product.prodname_dependabot %} alert and display it {% ifversion fpt or ghec or ghes %} on the Security tab for the repository and{% endif %} in the repository's dependency graph. The alert includes {% ifversion fpt or ghec or ghes %}a link to the affected file in the project, and {% endif %}information about a fixed version. {% data variables.product.product_name %} may also notify the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)." -{% ifversion fpt or ghec or ghes > 3.2 %} 对于已启用 {% data variables.product.prodname_dependabot_security_updates %} 的存储库,警报中还包含一个拉取请求链接,用于将清单或锁定文件更新到能解决该漏洞的最低版本。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”。 +{% ifversion fpt or ghec or ghes > 3.2 %} +For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." {% endif %} {% warning %} -注意:{% data variables.product.product_name %} 的安全功能并不声明捕获所有漏洞{% ifversion GH-advisory-db-supports-malware %} 和恶意软件{% endif %}。 我们积极维护 {% data variables.product.prodname_advisory_database %} 并生成包含最新信息的警报。 但是,我们无法在保证的时间范围内捕获所有漏洞或告知你已知的漏洞。 这些功能不能替代针对每个依赖项潜在漏洞或任何其他问题的人工评审,建议在必要时咨询安全服务或进行彻底的依赖项评审。 +**Note**: {% data variables.product.product_name %}'s security features do not claim to catch all vulnerabilities{% ifversion GH-advisory-db-supports-malware %} and malware{% endif %}. We actively maintain {% data variables.product.prodname_advisory_database %} and generate alerts with the most up-to-date information. However, we cannot catch everything or tell you about known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough dependency review when necessary. {% endwarning %} -## 访问 {% data variables.product.prodname_dependabot_alerts %} +## Access to {% data variables.product.prodname_dependabot_alerts %} -你可以{% ifversion fpt or ghec %}在存储库的“安全性”选项卡中或{% endif %}在存储库的依赖项关系图中查看影响特定项目的所有警报。 有关详细信息,请参阅“[查看和更新 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)”。 +You can see all of the alerts that affect a particular project{% ifversion fpt or ghec %} on the repository's Security tab or{% endif %} in the repository's dependency graph. For more information, see "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)." -默认情况下,我们会向受影响仓库中具有管理员权限的人员通知有关新的 {% data variables.product.prodname_dependabot_alerts %}。 {% ifversion fpt or ghec %}{% data variables.product.product_name %} 绝不会公开披露任何存储库的不安全依赖项。 也可以将 {% data variables.product.prodname_dependabot_alerts %} 设为对使用你拥有或具有管理员权限的存储库的其他人或团队可见。 有关详细信息,请参阅“[管理存储库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)”。 +By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}. {% ifversion fpt or ghec %}{% data variables.product.product_name %} never publicly discloses insecure dependencies for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working with repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." {% endif %} -{% data reusables.notifications.vulnerable-dependency-notification-enable %} {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %} 有关详细信息,请参阅“[为 {% data variables.product.prodname_dependabot_alerts %} 配置通知](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)”。 +{% data reusables.notifications.vulnerable-dependency-notification-enable %} +{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %} For more information, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)." -你还可以查看与 {% data variables.product.prodname_advisory_database %} 中的特定公告对应的 {% data variables.product.prodname_dependabot_alerts %}。 {% data reusables.security-advisory.link-browsing-advisory-db %} +You can also see all the {% data variables.product.prodname_dependabot_alerts %} that correspond to a particular advisory in the {% data variables.product.prodname_advisory_database %}. {% data reusables.security-advisory.link-browsing-advisory-db %} {% ifversion fpt or ghec or ghes > 3.2 %} -## 延伸阅读 +## Further reading -- [关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates) -- “[查看和更新 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)”{% endif %} {% ifversion fpt or ghec %}-“[关于 {% data variables.product.prodname_dotcom %} 的隐私](/get-started/privacy-on-github)”{% endif %} +- "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% endif %} +{% ifversion fpt or ghec %}- "[Privacy on {% data variables.product.prodname_dotcom %}](/get-started/privacy-on-github)"{% endif %} diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md index 00c92688af..663dc63e1b 100644 --- a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md +++ b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md @@ -149,9 +149,9 @@ For any {% data variables.product.company_short %}-reviewed advisory in the {% d 5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name. {% ifversion security-advisories-ghes-ghae %} -## Accessing the local advisory database on {% data variables.product.product_location %} +## Accessing the local advisory database on {% data variables.location.product_location %} -If your site administrator has enabled {% data variables.product.prodname_github_connect %} for {% data variables.product.product_location %}, you can also browse reviewed advisories locally. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)". +If your site administrator has enabled {% data variables.product.prodname_github_connect %} for {% data variables.location.product_location %}, you can also browse reviewed advisories locally. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)". You can use your local advisory database to check whether a specific security vulnerability is included, and therefore whether you'd get alerts for vulnerable dependencies. You can also view any vulnerable repositories. @@ -165,9 +165,9 @@ You can use your local advisory database to check whether a specific security vu {% endnote %} 3. Click an advisory to view details.{% ifversion GH-advisory-db-supports-malware %} By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. To show malware advisories, use `type:malware` in the search bar.{% endif %} -You can also suggest improvements to any advisory directly from your local advisory database. For more information, see "[Editing advisories from {% data variables.product.product_location %}](/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database#editing-advisories-from-your-github-enterprise-server-instance)". +You can also suggest improvements to any advisory directly from your local advisory database. For more information, see "[Editing advisories from {% data variables.location.product_location %}](/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database#editing-advisories-from-your-github-enterprise-server-instance)". -### Viewing vulnerable repositories for {% data variables.product.product_location %} +### Viewing vulnerable repositories for {% data variables.location.product_location %} {% data reusables.repositories.enable-security-alerts %} diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md index 2a8eaeb186..688f003461 100644 --- a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md +++ b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md @@ -43,9 +43,9 @@ Only repository owners and administrators can edit repository-level security adv You can also open a pull request directly on an advisory file in the [github/advisory-database](https://github.com/github/advisory-database) repository. For more information, see the [contribution guidelines](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md). {% ifversion security-advisories-ghes-ghae %} -## Editing advisories from {% data variables.product.product_location %} +## Editing advisories from {% data variables.location.product_location %} -If you have {% data variables.product.prodname_github_connect %} enabled for {% data variables.product.product_location %}, you will be able to see advisories by adding `/advisories` to the instance url. +If you have {% data variables.product.prodname_github_connect %} enabled for {% data variables.location.product_location %}, you will be able to see advisories by adding `/advisories` to the instance url. 1. Navigate to `https://HOSTNAME/advisories`. 2. Select the security advisory you would like to contribute to. diff --git a/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md b/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md index b6cf7bad95..4d727384fd 100644 --- a/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md +++ b/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md @@ -115,7 +115,7 @@ jobs: {% note %} -**Note:** Your site administrator can override these restrictions for {% data variables.product.product_location %}. For more information, see "[Troubleshooting {% data variables.product.prodname_actions %} for your enterprise](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise#troubleshooting-failures-when-dependabot-triggers-existing-workflows)." +**Note:** Your site administrator can override these restrictions for {% data variables.location.product_location %}. For more information, see "[Troubleshooting {% data variables.product.prodname_actions %} for your enterprise](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise#troubleshooting-failures-when-dependabot-triggers-existing-workflows)." If the restrictions are removed, when a workflow is triggered by {% data variables.product.prodname_dependabot %} it will have access to {% data variables.product.prodname_actions %} secrets and can use the `permissions` term to increase the default scope of the `GITHUB_TOKEN` from read-only access. You can ignore the specific steps in the "Handling `pull_request` events" and "Handling `push` events" sections, as it no longer applies. @@ -245,7 +245,7 @@ Here are several common scenarios that can be automated using {% data variables. {% note %} -**Note:** If your site administrator has overridden restrictions for {% data variables.product.prodname_dependabot %} on {% data variables.product.product_location %}, you can use `pull_request` instead of `pull_request_target` in the following workflows. +**Note:** If your site administrator has overridden restrictions for {% data variables.product.prodname_dependabot %} on {% data variables.location.product_location %}, you can use `pull_request` instead of `pull_request_target` in the following workflows. {% endnote %} diff --git a/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md index fc90314177..7974d9e6ee 100644 --- a/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -1,6 +1,6 @@ --- -title: 漏洞依赖项检测疑难解答 -intro: '如果 {% data variables.product.product_name %} 报告的依赖项信息不符合您的预期,则需要考虑许多因素,您可以检查各种问题。' +title: Troubleshooting the detection of vulnerable dependencies +intro: 'If the dependency information reported by {% data variables.product.product_name %} is not what you expected, there are a number of points to consider, and various things you can check.' shortTitle: Troubleshoot vulnerability detection redirect_from: - /github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies @@ -22,81 +22,78 @@ topics: - Vulnerabilities - CVEs - Repositories -ms.openlocfilehash: 50e63a273d1bd787c2c324d3ceed9a8d31b64c9e -ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147883415' --- -{% data reusables.dependabot.beta-security-and-version-updates %} {% data reusables.dependabot.result-discrepancy %} -## 为什么似乎缺少某些依赖项? +{% data reusables.dependabot.beta-security-and-version-updates %} +{% data reusables.dependabot.result-discrepancy %} -{% data variables.product.prodname_dotcom %} 生成和显示依赖项数据不同于其他工具。 因此,如果您过去使用其他工具来识别依赖项,则几乎可以肯定您会看到不同的结果。 考虑以下情况: +## Why do some dependencies seem to be missing? -* {% data variables.product.prodname_advisory_database %} 是 {% data variables.product.prodname_dotcom %} 用来识别漏洞依赖项{% ifversion GH-advisory-db-supports-malware %}和恶意软件{% endif %}的数据源之一。 它是一款免费的精选数据库,用于收集 {% data variables.product.prodname_dotcom %} 上常见软件包生态系统的安全公告。 它包括从 {% data variables.product.prodname_security_advisories %} 直接报告给 {% data variables.product.prodname_dotcom %} 的数据,以及官方馈送和社区来源。 这些数据由 {% data variables.product.prodname_dotcom %} 审查和整理,以确保不会与开发社区分享虚假或不可行的信息。 {% data reusables.security-advisory.link-browsing-advisory-db %} -* 依赖项图解析用户仓库中所有已知的包清单文件。 例如,对于 npm,它将解析 package-lock.json 文件。 它构造所有仓库依赖项和公共依赖项的图表。 当启用依赖关系图时,当任何人推送到默认分支时,都会发生这种情况,其中包括对支持的清单格式进行更改的提交。 有关详细信息,请参阅“[关于依赖项关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”和“[依赖项关系图故障排除](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)”。 -* {% data variables.product.prodname_dependabot %} 扫描对包含清单文件的默认分支的任何推送。 添加新公告时,它会扫描所有现有存储库并为每个受影响的存储库生成警报。 {% data variables.product.prodname_dependabot_alerts %} 在存储库级别汇总,而不是针对每条公告创建一个警报。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”。 -* {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} 在你收到关于存储库中易受攻击依赖项的警报时触发。 在可能的情况下,{% data variables.product.prodname_dependabot %} 会在您的仓库中创建拉取请求,以将易受攻击的依赖项升级到避免漏洞所需的最低安全版本。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”和“[{% data variables.product.prodname_dependabot %} 错误故障排除](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)”。 +{% data variables.product.prodname_dotcom %} generates and displays dependency data differently than other tools. Consequently, if you've been using another tool to identify dependencies you will almost certainly see different results. Consider the following: + +* {% data variables.product.prodname_advisory_database %} is one of the data sources that {% data variables.product.prodname_dotcom %} uses to identify vulnerable dependencies{% ifversion GH-advisory-db-supports-malware %} and malware{% endif %}. It's a free, curated database of security advisories for common package ecosystems on {% data variables.product.prodname_dotcom %}. It includes both data reported directly to {% data variables.product.prodname_dotcom %} from {% data variables.product.prodname_security_advisories %}, as well as official feeds and community sources. This data is reviewed and curated by {% data variables.product.prodname_dotcom %} to ensure that false or unactionable information is not shared with the development community. {% data reusables.security-advisory.link-browsing-advisory-db %} +* The dependency graph parses all known package manifest files in a user’s repository. For example, for npm it will parse the _package-lock.json_ file. It constructs a graph of all of the repository’s dependencies and public dependents. This happens when you enable the dependency graph and when anyone pushes to the default branch, and it includes commits that makes changes to a supported manifest format. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" and "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)." +* {% data variables.product.prodname_dependabot %} scans any push, to the default branch, that contains a manifest file. When a new advisory is added, it scans all existing repositories and generates an alert for each repository that is affected. {% data variables.product.prodname_dependabot_alerts %} are aggregated at the repository level, rather than creating one alert per advisory. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." +* {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)." - {% endif %}{% data variables.product.prodname_dependabot %} 不会按计划扫描存储库,而是在发生某些变更时扫描存储库。 例如,新增依赖项({% data variables.product.prodname_dotcom %} 在每次推送时都会进行此项检查)时,或者当新的公告添加到公告数据库{% ifversion ghes or ghae %}以及同步到 {% data variables.product.product_location %}{% endif %} 时,就会触发扫描。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-insecure-dependencies)”。 + {% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new advisory is added to the database{% ifversion ghes or ghae %} and synchronized to {% data variables.location.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-insecure-dependencies)." -## {% data variables.product.prodname_dependabot_alerts %} 是否仅与清单和锁定文件中的不安全依赖项相关? +## Do {% data variables.product.prodname_dependabot_alerts %} only relate to insecure dependencies in manifests and lockfiles? -{% data variables.product.prodname_dependabot_alerts %} 提醒您应更新的依赖项,包括可从清单或锁定文件确定版本的过渡依赖项。 {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} 仅在 {% data variables.product.prodname_dependabot %} 可直接修复依赖项时才建议更改,即以下情况: -* 在清单或锁定文件中明确声明的直接依赖项 -* 在锁定文件中声明的过渡依赖项{% endif %} +{% data variables.product.prodname_dependabot_alerts %} advise you about dependencies you should update, including transitive dependencies, where the version can be determined from a manifest or a lockfile. {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} only suggest a change where {% data variables.product.prodname_dependabot %} can directly "fix" the dependency, that is, when these are: +* Direct dependencies explicitly declared in a manifest or lockfile +* Transitive dependencies declared in a lockfile{% endif %} -检查:未在存储库的清单或锁定文件中指定的组件是否存在未捕获的漏洞? +**Check**: Is the uncaught vulnerability for a component that's not specified in the repository's manifest or lockfile? -## 为什么我无法获取某些生态系统的 {% data variables.product.prodname_dependabot_alerts %}? +## Why don't I get {% data variables.product.prodname_dependabot_alerts %} for some ecosystems? -{% data variables.product.prodname_dependabot_alerts %} 支持一组可提供高质量、可操作数据的生态系统。 {% data variables.product.prodname_advisory_database %} 中的特选公告、依赖项关系图、{% ifversion fpt or ghec %}{% data variables.product.prodname_dependabot %}安全更新{% endif %} 和 {% data variables.product.prodname_dependabot_alerts %} 提供用于多个生态系统,包括 Java’s Maven、JavaScript’s npm 和 Yarn、.NET’s NuGet、Python’s pip、Ruby's RubyGems 以及 PHP’s Composer。 我们将在今后继续增加对更多生态系统的支持。 有关我们支持的包生态系统的概述,请参阅“[关于依赖项关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)”。 +{% data variables.product.prodname_dependabot_alerts %} are supported for a set of ecosystems where we can provide high-quality, actionable data. Curated advisories in the {% data variables.product.prodname_advisory_database %}, the dependency graph, {% ifversion fpt or ghec %}{% data variables.product.prodname_dependabot %} security updates, {% endif %}and {% data variables.product.prodname_dependabot_alerts %} are provided for several ecosystems, including Java’s Maven, JavaScript’s npm and Yarn, .NET’s NuGet, Python’s pip, Ruby's RubyGems, and PHP’s Composer. We'll continue to add support for more ecosystems over time. For an overview of the package ecosystems that we support, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." -值得注意的是,可能存在其他生态系统的安全公告。 未经审查的安全公告中的信息由特定存储库的维护员提供。 此数据不是由 {% data variables.product.prodname_dotcom %} 策展的。 {% data reusables.security-advisory.link-browsing-advisory-db %} +It's worth noting that security advisories may exist for other ecosystems. The information in an unreviewed security advisory is provided by the maintainers of a particular repository. This data is not curated by {% data variables.product.prodname_dotcom %}. {% data reusables.security-advisory.link-browsing-advisory-db %} -检查:未捕获的漏洞是否适用于不受支持的生态系统? +**Check**: Does the uncaught vulnerability apply to an unsupported ecosystem? -## {% data variables.product.prodname_dependabot %} 是否会针对已知多年的漏洞生成警报? +## Does {% data variables.product.prodname_dependabot %} generate alerts for vulnerabilities that have been known for many years? -{% data variables.product.prodname_advisory_database %} 于 2019 年 11 月推出,并在最初回顾性包含了受支持生态系统的安全风险公告(从 2017 年开始)。 将 CVE 添加到数据库时,我们会优先处理较新的 CVE,以及影响较新版本软件的 CVE。 +The {% data variables.product.prodname_advisory_database %} was launched in November 2019, and initially back-filled to include advisories for security risks in the supported ecosystems, starting from 2017. When adding CVEs to the database, we prioritize curating newer CVEs, and CVEs affecting newer versions of software. -提供了一些有关较旧漏洞的信息,尤其是在这些 CVE 特别普遍的地方,但一些较旧的漏洞未包含在 {% data variables.product.prodname_advisory_database %} 中。 如果您需要将一些特定的旧漏洞包含在数据库中,请联系 {% data variables.contact.contact_support %}。 +Some information on older vulnerabilities is available, especially where these CVEs are particularly widespread, however some old vulnerabilities are not included in the {% data variables.product.prodname_advisory_database %}. If there's a specific old vulnerability that you need to be included in the database, contact {% data variables.contact.contact_support %}. -检查:未捕获的漏洞在国家漏洞数据库中的发布日期是否早于 2017 年? +**Check**: Does the uncaught vulnerability have a publish date earlier than 2017 in the National Vulnerability Database? -## 为什么 {% data variables.product.prodname_advisory_database %} 使用已发布漏洞数据的子集? +## Why does {% data variables.product.prodname_advisory_database %} use a subset of published vulnerability data? -有些第三方工具使用未经人为检查或过滤的未整理 CVE 数据。 这意味着 CVE 带有标签或严重错误或其他质量问题,将导致更频繁,更嘈杂且更无用的警报。 +Some third-party tools use uncurated CVE data that isn't checked or filtered by a human. This means that CVEs with tagging or severity errors, or other quality issues, will cause more frequent, more noisy, and less useful alerts. -由于 {% data variables.product.prodname_dependabot %} 使用 {% data variables.product.prodname_advisory_database %} 中的策展数据,因此警报量可能较少,但是收到的警报将是准确和相关的。 +Since {% data variables.product.prodname_dependabot %} uses curated data in the {% data variables.product.prodname_advisory_database %}, the volume of alerts may be lower, but the alerts you do receive will be accurate and relevant. {% ifversion fpt or ghec %} -## 是否每个不安全依赖项都会生成单独的警报? +## Does each insecure dependency generate a separate alert? -当依赖项具有多个漏洞时,将在通报和清单级别为每个漏洞生成警报。 +When a dependency has multiple vulnerabilities, an alert is generated for each vulnerability at the level of advisory plus manifest. -![{% data variables.product.prodname_dependabot_alerts %} 选项卡的屏幕截图,其中显示同一程序包中两个具有不同清单的警报。](/assets/images/help/repository/dependabot-alerts-view.png) +![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing two alerts from the same package with different manifests.](/assets/images/help/repository/dependabot-alerts-view.png) -旧版 {% data variables.product.prodname_dependabot_alerts %} 被分组到一个聚合警报中,其中包含同一依赖项的所有漏洞。 如果导航到指向旧版 {% data variables.product.prodname_dependabot %} 警报的链接,则会将你重定向到筛选的 {% data variables.product.prodname_dependabot_alerts %} 选项卡,以显示该依赖程序包和清单的漏洞。 +Legacy {% data variables.product.prodname_dependabot_alerts %} were grouped into a single aggregated alert with all the vulnerabilities for the same dependency. If you navigate to a link to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to the {% data variables.product.prodname_dependabot_alerts %} tab filtered to display vulnerabilities for that dependent package and manifest. -![{% data variables.product.prodname_dependabot_alerts %} 选项卡的屏幕截图,该选项卡在导航到旧版 {% data variables.product.prodname_dependabot %} 警报时显示筛选的警报。](/assets/images/help/repository/legacy-dependabot-alerts-view.png) +![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing the filtered alerts from navigating to a legacy {% data variables.product.prodname_dependabot %} alert.](/assets/images/help/repository/legacy-dependabot-alerts-view.png) -{% data variables.product.prodname_dotcom %} 中的 {% data variables.product.prodname_dependabot_alerts %} 计数显示警报数的总数,即漏洞数,而不是依赖项数。 +The {% data variables.product.prodname_dependabot_alerts %} count in {% data variables.product.prodname_dotcom %} shows a total for the number of alerts, which is the number of vulnerabilities, not the number of dependencies. -检查:如果看到的总数存在差异,请检查是否未将警报号与依赖项编号进行比较。 还要检查是否您查看的是所有警报,而不是已筛选警报的子集。 +**Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with dependency numbers. Also check that you are viewing all alerts and not a subset of filtered alerts. {% endif %} {% ifversion fpt or ghec or ghes > 3.2 %} -## Dependabot 能否忽略特定依赖项? +## Can Dependabot ignore specific dependencies? -可以配置 {% data variables.product.prodname_dependabot %} 以忽略配置文件中的特定依赖项,这将阻止这些依赖项的安全和版本更新。 如果只想使用安全更新,则需要使用配置文件替代默认行为。 有关详细信息,请参阅“[使用配置文件替代默认行为](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates#overriding-the-default-behavior-with-a-configuration-file)”,以防止激活版本更新。 有关忽略依赖项的信息,请参阅“[`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore)。”{% endif %} +You can configure {% data variables.product.prodname_dependabot %} to ignore specific dependencies in the configuration file, which will prevent security and version updates for those dependencies. If you only wish to use security updates, you will need to override the default behavior with a configuration file. For more information, see "[Overriding the default behavior with a configuration file](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates#overriding-the-default-behavior-with-a-configuration-file)" to prevent version updates from being activated. For information about ignoring dependencies, see "[`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore)." +{% endif %} -## 延伸阅读 +## Further reading -- [关于 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) -- [查看和更新 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts) -- [管理存储库的安全性和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) -- [依赖项关系图故障排除](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph){% ifversion fpt or ghec or ghes > 3.2 %} -- [{% data variables.product.prodname_dependabot %} 错误故障排除](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors){% endif %} +- "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" +- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" +- "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)"{% ifversion fpt or ghec or ghes > 3.2 %} +- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} diff --git a/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md b/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md index d2f3bf00e5..e00a81e612 100644 --- a/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md +++ b/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md @@ -1,6 +1,6 @@ --- -title: 保护你的组织 -intro: '您可以使用许多 {% data variables.product.prodname_dotcom %} 功能来帮助保护组织的安全。' +title: Securing your organization +intro: 'You can use a number of {% data variables.product.prodname_dotcom %} features to help keep your organization secure.' permissions: Organization owners can configure organization security settings. versions: fpt: '*' @@ -14,123 +14,124 @@ topics: - Vulnerabilities - Advanced Security shortTitle: Secure your organization -ms.openlocfilehash: 5ffc3393e751e4b0f24d9a59e644af7a3200f460 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147526836' --- -## 简介 -本指南向您展示如何配置一个组织的安全功能。 组织的安全需求是独一无二的,您可能不需要启用每个安全功能。 有关详细信息,请参阅“[{% data variables.product.prodname_dotcom %} 安全功能](/code-security/getting-started/github-security-features)”。 + +## Introduction +This guide shows you how to configure security features for an organization. Your organization's security needs are unique and you may not need to enable every security feature. For more information, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)." {% data reusables.advanced-security.security-feature-availability %} -## 管理对组织的访问 +## Managing access to your organization -您可以使用角色来控制用户可以在组织中执行的操作。 {% ifversion security-managers %}例如,可将安全管理员角色分配给团队,以便他们能够管理整个组织的安全设置,以及拥有对所有存储库的读取访问权限。{% endif %} 有关详细信息,请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。 +You can use roles to control what actions people can take in your organization. {% ifversion security-managers %}For example, you can assign the security manager role to a team to give them the ability to manage security settings across your organization, as well as read access to all repositories.{% endif %} For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." {% ifversion fpt or ghes or ghec %} -## 创建默认安全策略 +## Creating a default security policy -您可以创建默认安全策略,该策略将显示在组织中任何没有自己的安全策略的公共仓库中。 有关详细信息,请参阅“[创建默认社区运行状况文件](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)”。 +You can create a default security policy that will display in any of your organization's public repositories that do not have their own security policy. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." {% endif %} -## 管理 {% data variables.product.prodname_dependabot_alerts %} 和依赖关系图 +## Managing {% data variables.product.prodname_dependabot_alerts %} and the dependency graph -{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} 检测公共存储库中的漏洞并显示依赖关系图。 您可以为组织拥有的所有公共仓库启用或禁用 {% data variables.product.prodname_dependabot_alerts %}。 您可以为组织拥有的所有私有仓库启用或禁用 {% data variables.product.prodname_dependabot_alerts %} 和依赖关系图。 +{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and displays the dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all public repositories owned by your organization. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all private repositories owned by your organization. -1. 单击你的个人资料照片,然后单击“组织”。 -2. 单击组织旁边的“设置”。 -3. 单击“安全性和分析”。 -4. 单击你要管理的功能旁边的“全部启用”或“全部禁用” 。 -5. (可选)选择“自动对新存储库启用”。 +1. Click your profile photo, then click **Organizations**. +2. Click **Settings** next to your organization. +3. Click **Security & analysis**. +4. Click **Enable all** or **Disable all** next to the feature that you want to manage. +5. Optionally, select **Automatically enable for new repositories**. {% endif %} -{% data reusables.dependabot.dependabot-alerts-beta %} {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} +{% data reusables.dependabot.dependabot-alerts-beta %} +{% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} -有关详细信息,请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”、“[探索存储库的依赖项](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)”和“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 +For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)," "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)," and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -## 管理依赖项审查 +## Managing dependency review -依赖项评审是一项 {% data variables.product.prodname_advanced_security %} 功能,可让您在将拉取请求合并到存储库之前可视化拉取请求中的依赖项更改。 有关详细信息,请参阅“[关于依赖项审查](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)”。 +Dependency review is an {% data variables.product.prodname_advanced_security %} feature that lets you visualize dependency changes in pull requests before they are merged into your repositories. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)." -{% ifversion fpt or ghec %} 已为所有公共存储库启用了依赖项审查。 {% ifversion fpt %}将 {% data variables.product.prodname_ghe_cloud %} 与 {% data variables.product.prodname_advanced_security %} 一起使用的组织还可以对私有和内部存储库启用依赖项审查。 有关详细信息,请参阅 [{% data variables.product.prodname_ghe_cloud %} 文档](/enterprise-cloud@latest/code-security/getting-started/securing-your-organization#managing-dependency-review)。 {% endif %}{% endif %}{% ifversion ghec %}对于组织拥有的私有和内部存储库,您可以通过启用依赖关系图并启用 {% data variables.product.prodname_advanced_security %} 来启用依赖项审查(见下文)。 {% elsif ghes or ghae %}为 {% data variables.product.product_location %} 启用了依赖关系图并且为组织启用了 {% data variables.product.prodname_advanced_security %} 时,可以使用依赖项评审(见下文)。{% endif %} +{% ifversion fpt or ghec %}Dependency review is already enabled for all public repositories. {% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable dependency review for private and internal repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-organization#managing-dependency-review). {% endif %}{% endif %}{% ifversion ghec %}For private and internal repositories that are owned by an organization, you can enable dependency review by enabling the dependency graph and enabling {% data variables.product.prodname_advanced_security %} (see below). +{% elsif ghes or ghae %}Dependency review is available when dependency graph is enabled for {% data variables.location.product_location %} and you enable {% data variables.product.prodname_advanced_security %} for the organization (see below).{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %} -## 管理 {% data variables.product.prodname_dependabot_security_updates %} +## Managing {% data variables.product.prodname_dependabot_security_updates %} -对于任何使用 {% data variables.product.prodname_dependabot_alerts %} 的仓库,您可以启用 {% data variables.product.prodname_dependabot_security_updates %} 在检测到漏洞时提出带有安全更新的拉取请求。 您也可以为组织的所有仓库启用或禁用 {% data variables.product.prodname_dependabot_security_updates %}。 +For any repository that uses {% data variables.product.prodname_dependabot_alerts %}, you can enable {% data variables.product.prodname_dependabot_security_updates %} to raise pull requests with security updates when vulnerabilities are detected. You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories across your organization. -1. 单击你的个人资料照片,然后单击“组织”。 -2. 单击组织旁边的“设置”。 -3. 单击“安全性和分析”。 -4. 单击 {% data variables.product.prodname_dependabot_security_updates %} 旁边的“全部启用”或“全部禁用” 。 -5. (可选)选择“自动对新存储库启用”。 +1. Click your profile photo, then click **Organizations**. +2. Click **Settings** next to your organization. +3. Click **Security & analysis**. +4. Click **Enable all** or **Disable all** next to {% data variables.product.prodname_dependabot_security_updates %}. +5. Optionally, select **Automatically enable for new repositories**. -有关详细信息,请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-dependabot-security-updates)”和“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 +For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-dependabot-security-updates)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." -## 管理 {% data variables.product.prodname_dependabot_version_updates %} +## Managing {% data variables.product.prodname_dependabot_version_updates %} -您可以让 {% data variables.product.prodname_dependabot %} 自动提出拉取请求以保持依赖项的更新。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates)”。 +You can enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates)." -要启用 {% data variables.product.prodname_dependabot_version_updates %},必须创建 dependabot.yml 配置文件。 有关详细信息,请参阅“[配置 {% data variables.product.prodname_dependabot %} 版本更新](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)”。 +To enable {% data variables.product.prodname_dependabot_version_updates %}, you must create a *dependabot.yml* configuration file. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)." {% endif %} {% ifversion ghes or ghae or ghec %} -## 管理 {% data variables.product.prodname_GH_advanced_security %} +## Managing {% data variables.product.prodname_GH_advanced_security %} -{% ifversion ghes or ghec %} 如果你的{% ifversion ghec %}organization is owned by an enterprise that{% else %}企业{% endif %}拥有 {% data variables.product.prodname_advanced_security %} 许可证,则可启用或禁用 {% data variables.product.prodname_advanced_security %} 功能。 -{% elsif ghae %} 你可以启用或禁用 {% data variables.product.prodname_advanced_security %} 功能。 +{% ifversion ghes or ghec %} +If your {% ifversion ghec %}organization is owned by an enterprise that{% else %}enterprise{% endif %} has an {% data variables.product.prodname_advanced_security %} license, you can enable or disable {% data variables.product.prodname_advanced_security %} features. +{% elsif ghae %} +You can enable or disable {% data variables.product.prodname_advanced_security %} features. {% endif %} -1. 单击你的个人资料照片,然后单击“组织”。 -2. 单击组织旁边的“设置”。 -3. 单击“安全性和分析”。 -4. 单击 {% data variables.product.prodname_GH_advanced_security %} 旁边的“全部启用”或“全部禁用” 。 -5. (可选)选择“自动对新专用存储库启用”。 +1. Click your profile photo, then click **Organizations**. +2. Click **Settings** next to your organization. +3. Click **Security & analysis**. +4. Click **Enable all** or **Disable all** next to {% data variables.product.prodname_GH_advanced_security %}. +5. Optionally, select **Automatically enable for new private repositories**. -有关详细信息,请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)”和“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 +For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% endif %} -## 配置 {% data variables.product.prodname_secret_scanning %} +## Configuring {% data variables.product.prodname_secret_scanning %} -{% data variables.product.prodname_secret_scanning_caps %} 是一项 {% data variables.product.prodname_advanced_security %} 功能,用于扫描存储库以查找非安全存储的机密。 +{% data variables.product.prodname_secret_scanning_caps %} is an {% data variables.product.prodname_advanced_security %} feature that scans repositories for secrets that are insecurely stored. -已为所有公共存储库启用了 {% ifversion fpt or ghec %}{% data variables.product.prodname_secret_scanning_caps %} 。 将 {% data variables.product.prodname_ghe_cloud %} 与 {% data variables.product.prodname_advanced_security %} 结合使用的组织还可以为专用存储库和内部存储库启用 {% data variables.product.prodname_secret_scanning %}。{% endif %} {% ifversion fpt %}有关详细信息,请参阅 [{% data variables.product.prodname_ghe_cloud %} 文档](/enterprise-cloud@latest/code-security/getting-started/securing-your-organization#configuring-secret-scanning)。 {% endif %} +{% ifversion fpt or ghec %}{% data variables.product.prodname_secret_scanning_caps %} is already enabled for all public repositories. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable {% data variables.product.prodname_secret_scanning %} for private and internal repositories.{% endif %} {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-organization#configuring-secret-scanning). {% endif %} -如果您的企业使用 {% data variables.product.prodname_advanced_security %},则{% ifversion ghes or ghae %}{% data variables.product.prodname_secret_scanning_caps %} 可用。{% endif %} +{% ifversion ghes or ghae %}{% data variables.product.prodname_secret_scanning_caps %} is available if your enterprise uses {% data variables.product.prodname_advanced_security %}.{% endif %} -{% ifversion not fpt %} 你可以对已启用 {% data variables.product.prodname_advanced_security %} 的所有存储库启用或禁用 {% data variables.product.prodname_secret_scanning %}。 +{% ifversion not fpt %} +You can enable or disable {% data variables.product.prodname_secret_scanning %} for all repositories across your organization that have {% data variables.product.prodname_advanced_security %} enabled. -1. 单击你的个人资料照片,然后单击“组织”。 -2. 单击组织旁边的“设置”。 -3. 单击“安全性和分析”。 -4. 单击 {% data variables.product.prodname_secret_scanning_caps %} 旁边的“全部启用”或“全部禁用”(仅限 {% data variables.product.prodname_GH_advanced_security %} 存储库) 。 -5. (可选)选择“自动对添加到 {% data variables.product.prodname_advanced_security %} 的专用存储库启用”。 +1. Click your profile photo, then click **Organizations**. +2. Click **Settings** next to your organization. +3. Click **Security & analysis**. +4. Click **Enable all** or **Disable all** next to {% data variables.product.prodname_secret_scanning_caps %} ({% data variables.product.prodname_GH_advanced_security %} repositories only). +5. Optionally, select **Automatically enable for private repositories added to {% data variables.product.prodname_advanced_security %}**. -有关详细信息,请参阅[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)。 +For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% endif %} -## 配置 {% data variables.product.prodname_code_scanning %} +## Configuring {% data variables.product.prodname_code_scanning %} -{% data variables.product.prodname_code_scanning_capc %} 是一项 {% data variables.product.prodname_advanced_security %} 功能,可扫描代码以查找安全漏洞和错误 +{% data variables.product.prodname_code_scanning_capc %} is an {% data variables.product.prodname_advanced_security %} feature that scans code for security vulnerabilities and errors. -{% ifversion fpt or ghec %}{% data variables.product.prodname_code_scanning_capc %} 可用于所有公共存储库。 将 {% data variables.product.prodname_ghe_cloud %} 与 {% data variables.product.prodname_advanced_security %} 一起使用的组织还可以将 {% data variables.product.prodname_code_scanning %} 用于私有和内部存储库。如果您的企业使用 {% data variables.product.prodname_advanced_security %},则 {% else %}{% data variables.product.prodname_code_scanning_capc %} 可用 。{% endif %} +{% ifversion fpt or ghec %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally use {% data variables.product.prodname_code_scanning %} for private and internal repositories.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if your enterprise uses {% data variables.product.prodname_advanced_security %}.{% endif %} -{% data variables.product.prodname_code_scanning_capc %} 是在存储库级别配置的。 有关详细信息,请参阅“[为存储库设置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)”。 +{% data variables.product.prodname_code_scanning_capc %} is configured at the repository level. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)." -## 后续步骤 -您可以查看和管理来自安全功能的警报,以解决代码中的依赖项和漏洞。 有关详细信息,请参阅{% ifversion fpt or ghes or ghec %}“[查看和更新 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)”、{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}“[管理用于依赖项更新的拉取请求](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)”、{% endif %}“[管理存储库的 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)”和“[管理来自 {% data variables.product.prodname_secret_scanning %} 的警报](/code-security/secret-security/managing-alerts-from-secret-scanning)”。 +## Next steps +You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." -{% ifversion fpt or ghec %}如果您存在安全漏洞,您可以创建安全通告,以私下讨论和修复该漏洞。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)”和“[创建安全通告](/code-security/security-advisories/creating-a-security-advisory)”。 +{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)." {% endif %} -{% ifversion ghes or ghec or ghae %}你{% elsif fpt %}使用 {% data variables.product.prodname_ghe_cloud %}{% endif %} 的组织可在安全概述中查看、筛选{% ifversion ghes or ghec or ghae %}你的{% elsif fpt %}他们的{% endif %}组织拥有的存储库的安全警报,并对这些警报进行排序。 有关详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的{% ifversion ghes or ghec or ghae %}“[关于安全概述](/code-security/security-overview/about-the-security-overview)”。{% elsif fpt %}“[关于安全概述](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)”。{% endif %} +{% ifversion ghes or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes or ghec or ghae %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %} {% ifversion ghec %} -## 延伸阅读 +## Further reading -[访问组织的合规性报告](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization) {% endif %} +"[Accessing compliance reports for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization)" +{% endif %} diff --git a/translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md b/translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md index 519e8b2ba2..b9dce9457c 100644 --- a/translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md +++ b/translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md @@ -74,6 +74,10 @@ If you're a repository administrator you can enable {% data variables.product.pr {% ifversion ghes or ghae or ghec %}You can also define custom {% data variables.product.prodname_secret_scanning %} patterns for a repository, organization, or enterprise. For more information, see "[Defining custom patterns for {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)." {% endif %} + +{% ifversion secret-scanning-ghas-store-tokens %} +{% data variables.product.company_short %} stores detected secrets using symmetric encryption, both in transit and at rest.{% endif %}{% ifversion ghes > 3.7 %} To rotate the encryption keys used for storing the detected secrets, you can contact {% data variables.contact.contact_ent_support %}.{% endif %} + ### About {% data variables.product.prodname_secret_scanning %} alerts When you enable {% data variables.product.prodname_secret_scanning %} for a repository or push commits to a repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of those commits for secrets that match patterns defined by service providers{% ifversion ghes or ghae or ghec %} and any custom patterns defined in your enterprise, organization, or repository{% endif %}. {% ifversion secret-scanning-backfills %}{% data variables.product.prodname_dotcom %} also periodically runs a scan of all historical content in repositories with {% data variables.product.prodname_secret_scanning %} enabled.{% endif%} diff --git a/translations/zh-CN/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md b/translations/zh-CN/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md index 188283b50a..72be0fcd50 100644 --- a/translations/zh-CN/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md +++ b/translations/zh-CN/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md @@ -68,7 +68,7 @@ shortTitle: Manage secret alerts Once a secret has been committed to a repository, you should consider the secret compromised. {% data variables.product.prodname_dotcom %} recommends the following actions for compromised secrets: -- For a compromised {% data variables.product.prodname_dotcom %} personal access token, delete the compromised token, create a new token, and update any services that use the old token. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)." +- For a compromised {% data variables.product.prodname_dotcom %} {% data variables.product.pat_generic %}, delete the compromised token, create a new token, and update any services that use the old token. For more information, see "[Creating a {% data variables.product.pat_generic %} for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)." - For all other secrets, first verify that the secret committed to {% data variables.product.product_name %} is valid. If so, create a new secret, update any services that use the old secret, and then delete the old secret. {% ifversion ghec %} diff --git a/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md b/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md index 1d531390f5..69e55a8adc 100644 --- a/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md +++ b/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md @@ -43,7 +43,7 @@ In the security overview, you can view, sort, and filter alerts to understand th {% ifversion security-overview-views %} -In the security overview, there are dedicated views for each type of security alert, such as Dependabot, code scanning, and secret scanning alerts. You can use these views to limit your analysis to a specific set of alerts, and narrow the results further with a range of filters specific to each view. For example, in the secret scanning alert view, you can use the `Secret type` filter to view only secret scanning alerts for a specific secret, like a GitHub Personal Access Token. At the repository level, you can use the security overview to assess the specific repository's current security status, and configure any additional security features not yet in use on the repository. +In the security overview, there are dedicated views for each type of security alert, such as Dependabot, code scanning, and secret scanning alerts. You can use these views to limit your analysis to a specific set of alerts, and narrow the results further with a range of filters specific to each view. For example, in the secret scanning alert view, you can use the `Secret type` filter to view only secret scanning alerts for a specific secret, like a GitHub {% data variables.product.pat_generic %}. At the repository level, you can use the security overview to assess the specific repository's current security status, and configure any additional security features not yet in use on the repository. {% endif %} diff --git a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md index 78a0c5a03c..d16b736502 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md @@ -22,7 +22,7 @@ This guide describes the highest impact changes you can make to increase account ## What's the risk? -Account security is fundamental to the security of your supply chain. If an attacker can take over your account on {% data variables.product.product_name %}, they can then make malicious changes to your code or build process. So your first goal should be to make it difficult for someone to take over your account and the accounts of other {% ifversion ghes %}users{% else %}members{% endif %} of {% ifversion fpt %}your organization{% elsif ghec or ghae %}your organization or enterprise{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. +Account security is fundamental to the security of your supply chain. If an attacker can take over your account on {% data variables.product.product_name %}, they can then make malicious changes to your code or build process. So your first goal should be to make it difficult for someone to take over your account and the accounts of other {% ifversion ghes %}users{% else %}members{% endif %} of {% ifversion fpt %}your organization{% elsif ghec or ghae %}your organization or enterprise{% elsif ghes %}{% data variables.location.product_location %}{% endif %}. {% ifversion ghec or ghes %} ## Centralize authentication @@ -31,7 +31,7 @@ Account security is fundamental to the security of your supply chain. If an atta {% ifversion ghec %} If you're an enterprise or organization owner, you can configure centralized authentication with SAML. While you can add or remove members manually, it's simpler and more secure to set up single sign-on (SSO) and SCIM between {% data variables.product.product_name %} and your SAML identity provider (IdP). This also simplifies the authentication process for all members of your enterprise. -You can configure SAML authentication for an enterprise or organization account. With SAML, you can grant access to the personal accounts of members of your enterprise or organization on {% data variables.product.product_location %} through your IdP, or you can create and control the accounts that belong to your enterprise by using {% data variables.product.prodname_emus %}. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)." +You can configure SAML authentication for an enterprise or organization account. With SAML, you can grant access to the personal accounts of members of your enterprise or organization on {% data variables.location.product_location %} through your IdP, or you can create and control the accounts that belong to your enterprise by using {% data variables.product.prodname_emus %}. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)." After you configure SAML authentication, when members request access to your resources, they'll be directed to your SSO flow to ensure they are still recognized by your IdP. If they are unrecognized, their request is declined. @@ -39,7 +39,7 @@ Some IdPs support a protocol called SCIM, which can automatically provision or d {% endif %} {% ifversion ghes %} -If you're the site administrator for {% data variables.product.product_location %}, you can simplify the login experience for users by choosing an authentication method that connects with your existing identity provider (IdP), like CAS, SAML, or LDAP. This means that they no longer need to remember an extra password for {% data variables.product.prodname_dotcom %}. +If you're the site administrator for {% data variables.location.product_location %}, you can simplify the login experience for users by choosing an authentication method that connects with your existing identity provider (IdP), like CAS, SAML, or LDAP. This means that they no longer need to remember an extra password for {% data variables.product.prodname_dotcom %}. Some authentication methods also support communicating additional information to {% data variables.product.product_name %}, for example, what groups the user is a member of, or synchronizing cryptographic keys for the user. This is a great way to simplify your administration as your organization grows. @@ -48,7 +48,7 @@ For more information about the authentication methods available for {% data vari ## Configure two-factor authentication -The best way to improve the security of {% ifversion fpt %}your personal account{% elsif ghes %}your personal account or {% data variables.product.product_location %}{% elsif ghec %}your accounts{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %} is to configure two-factor authentication (2FA){% ifversion ghae %} on your SAML identity provider (IdP){% endif %}. Passwords by themselves can be compromised by being guessable, by being reused on another site that's been compromised, or by social engineering, like phishing. 2FA makes it much more difficult for your accounts to be compromised, even if an attacker has your password. +The best way to improve the security of {% ifversion fpt %}your personal account{% elsif ghes %}your personal account or {% data variables.location.product_location %}{% elsif ghec %}your accounts{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %} is to configure two-factor authentication (2FA){% ifversion ghae %} on your SAML identity provider (IdP){% endif %}. Passwords by themselves can be compromised by being guessable, by being reused on another site that's been compromised, or by social engineering, like phishing. 2FA makes it much more difficult for your accounts to be compromised, even if an attacker has your password. {% ifversion not ghae %} @@ -57,7 +57,7 @@ If you're an enterprise owner, you may be able to configure a policy to require {% endif %} {% ifversion ghes %} -If you're the site administrator for {% data variables.product.product_location %}, you may be able to configure 2FA for all users of your instance. The availability of 2FA on {% data variables.product.product_name %} depends on the authentication method that you use. For more information, see "[Centralize user authentication](#centralize-user-authentication)." +If you're the site administrator for {% data variables.location.product_location %}, you may be able to configure 2FA for all users of your instance. The availability of 2FA on {% data variables.product.product_name %} depends on the authentication method that you use. For more information, see "[Centralize user authentication](#centralize-user-authentication)." {% endif %} If you're an organization owner, then you {% ifversion fpt %}can{% else %}may be able to{% endif %} require that all members of the organization enable 2FA. @@ -69,14 +69,14 @@ If you're an organization owner, then you {% ifversion fpt %}can{% else %}may be Enterprise owners may be able to require 2FA for all {% ifversion ghes %}users on{% elsif ghec %}members of{% endif %} the {% ifversion ghes %}instance{% elsif ghec %}enterprise{% endif %}. The availability of 2FA policies on {% data variables.product.product_name %} depends on how {% ifversion ghes %}users{% else %}members{% endif %} authenticate to access your {% ifversion ghes %}instance{% elsif ghec %}enterprise's resources{% endif %}. {% ifversion ghes %} -- If you sign into {% data variables.product.product_location %} through an external IdP using CAS or SAML SSO, you +- If you sign into {% data variables.location.product_location %} through an external IdP using CAS or SAML SSO, you {% elsif ghec %} If your enterprise uses {% data variables.product.prodname_emus %} or SAML authentication is enforced for your enterprise, you {%- endif %} cannot configure 2FA on {% data variables.product.product_name %}. Someone with administrative access to your IdP must configure 2FA for the IdP. {% ifversion ghes %} -- If you sign into {% data variables.product.product_location %} through an external LDAP directory, you can require 2FA for your enterprise on {% data variables.product.product_name %}. If you allow built-in authentication for users outside of your directory, individual users can enable 2FA, but you cannot require 2FA for your enterprise. +- If you sign into {% data variables.location.product_location %} through an external LDAP directory, you can require 2FA for your enterprise on {% data variables.product.product_name %}. If you allow built-in authentication for users outside of your directory, individual users can enable 2FA, but you cannot require 2FA for your enterprise. {% endif %} @@ -89,7 +89,7 @@ For more information, see {% ifversion ghec %}"[About identity and access manage {% ifversion ghec or ghes %} {% note %} -**Note**: Depending on the authentication method that {% ifversion ghec %}an enterprise owner{% elsif ghes %}a site administrator{% endif %} has configured for {% ifversion ghec %}your enterprise on {% endif %}{% data variables.product.product_location %}, you may not be able to enable 2FA for your personal account. +**Note**: Depending on the authentication method that {% ifversion ghec %}an enterprise owner{% elsif ghes %}a site administrator{% endif %} has configured for {% ifversion ghec %}your enterprise on {% endif %}{% data variables.location.product_location %}, you may not be able to enable 2FA for your personal account. {% endnote %} {% endif %} @@ -103,7 +103,7 @@ When you set up 2FA, you should always download the recovery codes and set up mo {% ifversion ghec or ghes %} {% note %} -**Note**: Depending on the authentication method that {% ifversion ghec %}an enterprise owner{% elsif ghes %}a site administrator{% endif %} has configured for {% ifversion ghec %}your enterprise on {% endif %}{% data variables.product.product_location %}, you may not be able to require 2FA for your organization. +**Note**: Depending on the authentication method that {% ifversion ghec %}an enterprise owner{% elsif ghes %}a site administrator{% endif %} has configured for {% ifversion ghec %}your enterprise on {% endif %}{% data variables.location.product_location %}, you may not be able to require 2FA for your organization. {% endnote %} {% endif %} diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md index c5c6fdf15f..33e8c19950 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md @@ -111,7 +111,7 @@ The term "{% data variables.product.prodname_dependabot %}" encompasses the foll - {% data variables.product.prodname_dependabot %} performs a scan to detect insecure dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when: {% ifversion fpt or ghec %} - A new advisory is added to the {% data variables.product.prodname_advisory_database %}.{% else %} - - New advisory data is synchronized to {% data variables.product.product_location %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %} + - New advisory data is synchronized to {% data variables.location.product_location %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %} - The dependency graph for the repository changes. - {% data variables.product.prodname_dependabot_alerts %} are displayed {% ifversion fpt or ghec or ghes %} on the **Security** tab for the repository and{% endif %} in the repository's dependency graph. The alert includes {% ifversion fpt or ghec or ghes %}a link to the affected file in the project, and {% endif %}information about a fixed version. @@ -164,7 +164,7 @@ Any repository type: {% ifversion ghes or ghae %} - **Dependency graph** and **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. Both features are configured at an enterprise level by the enterprise owner. For more information, see {% ifversion ghes %}"[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)" and {% endif %}"[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." -- **Dependency review**—available when dependency graph is enabled for {% data variables.product.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)." +- **Dependency review**—available when dependency graph is enabled for {% data variables.location.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)." {% endif %} {% ifversion ghes > 3.2 %} - **{% data variables.product.prodname_dependabot_security_updates %}**—not enabled by default. You can enable {% data variables.product.prodname_dependabot_security_updates %} for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)." diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md index 5abdb8b0d4..06bb91f769 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md @@ -38,7 +38,7 @@ Dependency review is included in {% data variables.product.product_name %} for p {% elsif ghes or ghae %} -Dependency review is available when dependency graph is enabled for {% data variables.product.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository.{% ifversion ghes %} For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)."{% endif %} +Dependency review is available when dependency graph is enabled for {% data variables.location.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository.{% ifversion ghes %} For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)."{% endif %} ### Checking if the dependency graph is enabled diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md index f8ef3037ef..40094b5db2 100644 --- a/translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md +++ b/translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md @@ -30,7 +30,7 @@ If you publish a container image to {% data variables.packages.prodname_ghcr_or_ By default, when you publish a container image to {% data variables.packages.prodname_ghcr_or_npm_registry %}, the image inherits the access setting of the repository from which the image was published. For example, if the repository is public, the image is also public. If the repository is private, the image is also private, but is accessible from the repository. -This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.packages.prodname_ghcr_or_npm_registry %} using a Personal Access Token (PAT). +This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.packages.prodname_ghcr_or_npm_registry %} using a % data variables.product.pat_generic %}. If the **Inherit access from repo** option was not selected when the image was published, you can manually add the repository to the published container image's access controls. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#inheriting-access-for-a-container-image-from-a-repository)." @@ -46,13 +46,13 @@ If you want to allow a subset of an organization's repositories to access a cont ### Publishing a container image from a codespace -Seamless access from a codespace to {% data variables.packages.prodname_ghcr_or_npm_registry %} is limited to pulling container images. If you want to publish a container image from inside a codespace, you must use a personal access token (PAT) with the `write:packages` scope. +Seamless access from a codespace to {% data variables.packages.prodname_ghcr_or_npm_registry %} is limited to pulling container images. If you want to publish a container image from inside a codespace, you must use a {% data variables.product.pat_v1 %} with the `write:packages` scope. We recommend publishing images via {% data variables.product.prodname_actions %}. For more information, see "[Publishing Docker images](/actions/publishing-packages/publishing-docker-images)" and "[Publishing Node.js packages](/actions/publishing-packages/publishing-nodejs-packages)." ## Accessing images stored in other container registries -If you are accessing a container image from a registry that isn't {% data variables.packages.prodname_ghcr_or_npm_registry %}, {% data variables.product.prodname_github_codespaces %} checks for the presence of three secrets, which define the server name, username, and personal access token (PAT) for a container registry. If these secrets are found, {% data variables.product.prodname_github_codespaces %} will make the registry available inside your codespace. +If you are accessing a container image from a registry that isn't {% data variables.packages.prodname_ghcr_or_npm_registry %}, {% data variables.product.prodname_github_codespaces %} checks for the presence of three secrets, which define the server name, username, and {% data variables.product.pat_generic %} for a container registry. If these secrets are found, {% data variables.product.prodname_github_codespaces %} will make the registry available inside your codespace. - `<*>_CONTAINER_REGISTRY_SERVER` - `<*>_CONTAINER_REGISTRY_USER` @@ -71,7 +71,7 @@ For a private image registry in Azure, you could create the following secrets: ``` ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io ACR_CONTAINER_REGISTRY_USER = acr-user-here -ACR_CONTAINER_REGISTRY_PASSWORD = +ACR_CONTAINER_REGISTRY_PASSWORD = ``` For information on common image registries, see "[Common image registry servers](#common-image-registry-servers)." Note that accessing AWS Elastic Container Registry (ECR) is different. diff --git a/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md index 7906fa375a..253b3ea97e 100644 --- a/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md +++ b/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md @@ -1,6 +1,6 @@ --- -title: 管理代码空间的加密密码 -intro: 您可以在代码空间中存储要通过环境变量访问的敏感信息(如令牌)。 +title: Managing encrypted secrets for your codespaces +intro: 'You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -15,84 +15,89 @@ topics: - Security - Secret store shortTitle: Encrypted secrets -ms.openlocfilehash: 6951acb82614d35e3394a2af8e58fc8f8442ab3a -ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/12/2022 -ms.locfileid: '147419791' --- -## 关于 {% data variables.product.prodname_github_codespaces %} 的加密机密 -你可以将要在 codespace 中使用的加密密码添加到你的个人帐户。 例如,您可能想要存储和访问以下敏感信息作为加密密码。 + -- 对云服务的个人访问令牌 -- 服务主体 -- 订阅标识符 -- [专用映像注册表的凭据](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry) -您可以选择哪些仓库应有权访问每个密码。 然后,您可以在为有权访问密码的仓库创建的任何代码空间中使用该密码。 +## About encrypted secrets for {% data variables.product.prodname_github_codespaces %} + +You can add encrypted secrets to your personal account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets. + +- {% data variables.product.pat_generic %}s to cloud services +- Service principals +- Subscription identifiers +- [Credentials for a private image registry](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry) + +You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret. {% data reusables.codespaces.secrets-on-start %} -### 命名密钥 +### Naming secrets -{% data reusables.codespaces.secrets-naming %} 例如,在仓库级别创建的密钥必须在该仓库中具有唯一的名称。 +{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository. {% data reusables.codespaces.secret-precedence %} -### 密码的限制 +### Limits for secrets -最多可以为 {% data variables.product.prodname_github_codespaces %} 存储 100 个密码。 +You can store up to 100 secrets for {% data variables.product.prodname_github_codespaces %}. -密码大小限于 64 KB。 +Secrets are limited to 64 KB in size. -## 添加密码 +## Adding a secret -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.codespaces-tab %} -1. 在“Codespaces 机密”右侧,单击“新建机密”。 - ![“新建机密”按钮](/assets/images/help/settings/codespaces-new-secret-button.png) -1. 在“Name(名称)”下,输入密码的名称。 - ![“名称”文本框](/assets/images/help/settings/codespaces-secret-name-field.png) {% data reusables.user-settings.codespaces-secret-value %} {% data reusables.user-settings.codespaces-secret-repository-access %} -1. 单击“添加机密”。 +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.codespaces-tab %} +1. To the right of "Codespaces secrets", click **New secret**. + !["New secret" button](/assets/images/help/settings/codespaces-new-secret-button.png) +1. Under "Name", type a name for your secret. + !["Name" text box](/assets/images/help/settings/codespaces-secret-name-field.png) +{% data reusables.user-settings.codespaces-secret-value %} +{% data reusables.user-settings.codespaces-secret-repository-access %} +1. Click **Add secret**. -## 编辑密码 +## Editing a secret -您可以更新现有密码的值,也可以更改哪些仓库可以访问密码。 +You can update the value of an existing secret, and you can change which repositories can access a secret. -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.codespaces-tab %} -1. 在“Codespaces 机密”下,在要编辑的机密的右侧,单击“更新”。 - ![“更新”按钮](/assets/images/help/settings/codespaces-secret-update-button.png) -1. 在“值”下,单击“输入新值”。 - ![“输入新值”链接](/assets/images/help/settings/codespaces-secret-update-value-text.png) {% data reusables.user-settings.codespaces-secret-value %} {% data reusables.user-settings.codespaces-secret-repository-access %} -1. (可选)要删除密码对仓库的访问权限,请取消选择仓库。 - ![用于删除对存储库的访问权限的复选框](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) -1. 单击“保存更改”。 +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.codespaces-tab %} +1. Under "Codespaces secrets", to the right of the secret you want to edit, click **Update**. + !["Update" button](/assets/images/help/settings/codespaces-secret-update-button.png) +1. Under "Value", click **enter a new value**. + !["enter a new value" link](/assets/images/help/settings/codespaces-secret-update-value-text.png) +{% data reusables.user-settings.codespaces-secret-value %} +{% data reusables.user-settings.codespaces-secret-repository-access %} +1. Optionally, to remove the secret's access to a repository, deselect the repository. + ![Checkboxes to remove access to repositories](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png) +1. Click **Save changes**. -## 删除密码 +## Deleting a secret -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.codespaces-tab %} -1. 在“Codespaces 机密”下,在要删除的机密的右侧,单击“删除”。 - ![“删除”按钮](/assets/images/help/settings/codespaces-secret-delete-button.png) -1. 阅读警告,然后单击“确定”。 - ![确认删除机密](/assets/images/help/settings/codespaces-secret-delete-warning.png) +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.codespaces-tab %} +1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. + !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png) +1. Read the warning, then click **OK**. + ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png) -## 使用机密 +## Using secrets -机密作为环境变量导出到用户的终端会话中。 +A secret is exported as an environment variable into the user's terminal session. - ![在终端显示导出机密的值](/assets/images/help/codespaces/exported-codespace-secret.png) + ![Displaying the value of an exported secret in the terminal](/assets/images/help/codespaces/exported-codespace-secret.png) -Codespace 生成并运行后,可以在 Codespace 中使用机密。 例如,机密可用于: +You can use secrets in a codespace after the codespace is built and is running. For example, a secret can be used: -* 从集成终端或 ssh 会话启动应用程序时。 -* 在 Codespace 开始运行后运行的开发容器生命周期脚本中。 有关开发容器生命周期脚本的详细信息,请参阅 containers.dev 的相关文档:[规范](https://containers.dev/implementors/json_reference/#lifecycle-scripts)。 +* When launching an application from the integrated terminal or ssh session. +* Within a dev container lifecycle script that is run after the codespace is running. For more information about dev container lifecycle scripts, see the documentation on containers.dev: [Specification](https://containers.dev/implementors/json_reference/#lifecycle-scripts). -Codespace 机密不可用于: +Codespace secrets cannot be used during: -* Codespace 生成时(即,在 Dockerfile 或自定义入口点内)。 -* 在开发容器功能内。 有关详细信息,请参阅 containers.dev 相关文档中的 `features` 属性:[规范](https://containers.dev/implementors/json_reference/#general-properties)。 +* Codespace build time (that is, within a Dockerfile or custom entry point). +* Within a dev container feature. For more information, see the `features` attribute in the documentation on containers.dev: [Specification](https://containers.dev/implementors/json_reference/#general-properties). -## 延伸阅读 +## Further reading -- “[管理 {% data variables.product.prodname_github_codespaces %} 的存储库和组织的加密密码](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces)” +- "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces)" diff --git a/translations/zh-CN/content/codespaces/overview.md b/translations/zh-CN/content/codespaces/overview.md index 1a6ee65780..b193cde66d 100644 --- a/translations/zh-CN/content/codespaces/overview.md +++ b/translations/zh-CN/content/codespaces/overview.md @@ -22,7 +22,7 @@ topics: A codespace is a development environment that's hosted in the cloud. You can customize your project for {% data variables.product.prodname_github_codespaces %} by committing [configuration files](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project) to your repository (often known as Configuration-as-Code), which creates a repeatable codespace configuration for all users of your project. -{% data variables.product.prodname_github_codespaces %} run on a variety of VM-based compute options hosted by {% data variables.product.product_location %}, which you can configure from 2 core machines up to 32 core machines. You can connect to your codespaces from the browser or locally using {% data variables.product.prodname_vscode %}. +{% data variables.product.prodname_github_codespaces %} run on a variety of VM-based compute options hosted by {% data variables.location.product_location %}, which you can configure from 2 core machines up to 32 core machines. You can connect to your codespaces from the browser or locally using {% data variables.product.prodname_vscode %}. ![A diagram showing how {% data variables.product.prodname_github_codespaces %} works](/assets/images/help/codespaces/codespaces-diagram.png) diff --git a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md index ff49dcf7ed..f9f02988d3 100644 --- a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md +++ b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md @@ -29,33 +29,33 @@ When you create or edit a prebuild configuration for a `devcontainer.json` file ## Allowing a prebuild write access external resources -If your project requires write access to resources, or if the external resources reside in a repository with a different owner to the repository for which you are creating a prebuild configuration, you can use a personal access token (PAT) to grant this access. +If your project requires write access to resources, or if the external resources reside in a repository with a different owner to the repository for which you are creating a prebuild configuration, you can use a {% data variables.product.pat_generic %} to grant this access. -You will need to create a new personal account and then use this account to create a PAT with the appropriate scopes. +You will need to create a new personal account and then use this account to create a {% data variables.product.pat_v1 %} with the appropriate scopes. 1. Create a new personal account on {% data variables.product.prodname_dotcom %}. {% warning %} - **Warning**: Although you can generate the PAT using your existing personal account, we strongly recommend creating a new account with access only to the target repositories required for your scenario. This is because the access token's `repository` permission grants access to all of the repositories that the account has access to. For more information, see "[Signing up for a new GitHub account](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)" and "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#considering-cross-repository-access)." + **Warning**: Although you can generate the {% data variables.product.pat_v1 %} using your existing personal account, we strongly recommend creating a new account with access only to the target repositories required for your scenario. This is because the access token's `repository` permission grants access to all of the repositories that the account has access to. For more information, see "[Signing up for a new GitHub account](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)" and "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#considering-cross-repository-access)." {% endwarning %} 1. Give the new account read access to the required repositories. For more information, see "[Managing an individual's access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)." -1. While signed into the new account, create a PAT with the `repo` scope. Optionally, if the prebuild will need to download packages from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, also select the `read:packages` scope. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." +1. While signed into the new account, create a {% data variables.product.pat_v1 %} with the `repo` scope. Optionally, if the prebuild will need to download packages from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, also select the `read:packages` scope. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - !['repo' and 'packages' scopes selected for a PAT](/assets/images/help/codespaces/prebuilds-select-scopes.png) + !['repo' and 'packages' scopes selected for a {% data variables.product.pat_v1 %}](/assets/images/help/codespaces/prebuilds-select-scopes.png) If the prebuild will use a package from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, you will need to either grant the new account access to the package or configure the package to inherit the access permissions of the repository you are prebuilding. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)." -{% ifversion ghec %}1. Authorize the token for use with SAML single sign-on (SSO), so that it can access repositories that are owned by organizations with SSO enabled. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)." +{% ifversion ghec %}1. Authorize the token for use with SAML single sign-on (SSO), so that it can access repositories that are owned by organizations with SSO enabled. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)." - ![The button to configure SSO for a PAT](/assets/images/help/codespaces/configure-SSO-for-PAT.png) + ![The button to configure SSO for a {% data variables.product.pat_v1 %}](/assets/images/help/codespaces/configure-SSO-for-PAT.png) {% endif %} 1. Copy the token string. You will assign this to a {% data variables.product.prodname_codespaces %} repository secret. 1. Sign back into the account that has admin access to the repository. 1. In the repository for which you want to create {% data variables.product.prodname_github_codespaces %} prebuilds, create a new {% data variables.product.prodname_codespaces %} repository secret called `CODESPACES_PREBUILD_TOKEN`, giving it the value of the token you created and copied. For more information, see "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-a-repository)." -The PAT will be used for all subsequent prebuilds created for your repository. Unlike other {% data variables.product.prodname_codespaces %} repository secrets, the `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and will not be available to use in codespaces created from your repository. +The {% data variables.product.pat_generic %} will be used for all subsequent prebuilds created for your repository. Unlike other {% data variables.product.prodname_codespaces %} repository secrets, the `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and will not be available to use in codespaces created from your repository. ## Further reading diff --git a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md index f0ab7253be..24a9ff072b 100644 --- a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md +++ b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md @@ -1,6 +1,6 @@ --- -title: 关于 wikis -intro: 您可以将仓库文档托管在 wiki 中,以便其他人使用和参与您的项目。 +title: About wikis +intro: 'You can host documentation for your repository in a wiki, so that others can use and contribute to your project.' redirect_from: - /articles/about-github-wikis - /articles/about-wikis @@ -13,33 +13,28 @@ versions: ghec: '*' topics: - Community -ms.openlocfilehash: 94800761c60bb984745e582e2c9691e294e7a90d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147529621' --- -{% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的每个仓库都配备了一个托管文档部分,叫做 wiki。 您可以使用仓库的 wiki 共享项目的长内容,例如如何使用项目,您是如何设计项目的,或者其核心原则是什么。 自述文件快速介绍项目的内容,而您可以使用 wiki 提供其他文档。 有关详细信息,请参阅“[关于 README](/articles/about-readmes)”。 -使用 wiki,可以像在 {% data variables.product.product_name %} 的任何其他位置一样编写内容。 有关详细信息,请参阅“[在 {% data variables.product.prodname_dotcom %} 上编写和设置格式入门](/articles/getting-started-with-writing-and-formatting-on-github)”。 我们使用[开源标记库](https://github.com/github/markup)将不同的格式转换为 HTML,以便选择使用 Markdown 或任何其他支持的格式编写。 +Every repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} comes equipped with a section for hosting documentation, called a wiki. You can use your repository's wiki to share long-form content about your project, such as how to use it, how you designed it, or its core principles. A README file quickly tells what your project can do, while you can use a wiki to provide additional documentation. For more information, see "[About READMEs](/articles/about-readmes)." + +With wikis, you can write content just like everywhere else on {% data variables.product.product_name %}. For more information, see "[Getting started with writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/getting-started-with-writing-and-formatting-on-github)." We use [our open-source Markup library](https://github.com/github/markup) to convert different formats into HTML, so you can choose to write in Markdown or any other supported format. {% data reusables.getting-started.math-and-diagrams %} -{% ifversion fpt or ghes or ghec %}如果在公共存储库中创建 wiki,则该 wiki 可供{% ifversion ghes %}具有 {% data variables.product.product_location %} 访问权限的任何人{% else %}公共{% endif %}访问。 {% endif %}如果您在私有{% ifversion ghec or ghes %} 或内部{% endif %} 存储库中创建 Wiki,则仅有权访问该仓库的{% ifversion fpt or ghes or ghec %}人员{% elsif ghae %}企业成员{% endif %} 才能访问该 Wiki。 有关详细信息,请参阅[设置存储库可见性](/articles/setting-repository-visibility)。 +{% ifversion fpt or ghes or ghec %}If you create a wiki in a public repository, the wiki is available to {% ifversion ghes %}anyone with access to {% data variables.location.product_location %}{% else %}the public{% endif %}. {% endif %}If you create a wiki in a private{% ifversion ghec or ghes %} or internal{% endif %} repository, only {% ifversion fpt or ghes or ghec %}people{% elsif ghae %}enterprise members{% endif %} with access to the repository can access the wiki. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)." -您可以直接在 {% data variables.product.product_name %} 上编辑 wikis,也可在本地编辑 wiki 文件。 默认情况下,只有能够写入仓库的人才可更改 wikis,但您可以允许 {% data variables.product.product_location %} 上的每个人参与{% ifversion ghae %}内部{% else %}公共{% endif %}仓库中的 wiki。 有关详细信息,请参阅“[更改对 wiki 的访问权限](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis)”。 +You can edit wikis directly on {% data variables.product.product_name %}, or you can edit wiki files locally. By default, only people with write access to your repository can make changes to wikis, although you can allow everyone on {% data variables.location.product_location %} to contribute to a wiki in {% ifversion ghae %}an internal{% else %}a public{% endif %} repository. For more information, see "[Changing access permissions for wikis](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis)." {% note %} -注意:搜索引擎不会对 Wiki 的内容编制索引。 若要通过搜索引擎对内容编制索引,可以在公共存储库中使用 [{% data variables.product.prodname_pages %}](/pages)。 +**Note:** Search engines will not index the contents of wikis. To have your content indexed by search engines, you can use [{% data variables.product.prodname_pages %}](/pages) in a public repository. {% endnote %} -## 延伸阅读 +## Further reading -- [添加或编辑 Wiki 页面](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages) -- [为 Wiki 创建页脚或边栏](/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki) -- [编辑 Wiki 内容](/communities/documenting-your-project-with-wikis/editing-wiki-content) -- [查看 Wiki 的更改历史记录](/articles/viewing-a-wiki-s-history-of-changes) -- [搜索 Wiki](/search-github/searching-on-github/searching-wikis) +- "[Adding or editing wiki pages](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)" +- "[Creating a footer or sidebar for your wiki](/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki)" +- "[Editing wiki content](/communities/documenting-your-project-with-wikis/editing-wiki-content)" +- "[Viewing a wiki's history of changes](/articles/viewing-a-wiki-s-history-of-changes)" +- "[Searching wikis](/search-github/searching-on-github/searching-wikis)" diff --git a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md index 4ce52bf3eb..1601243f86 100644 --- a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md +++ b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md @@ -1,6 +1,6 @@ --- -title: 更改对 wiki 的访问权限 -intro: '默认情况下,只有仓库协作者才能编辑{% ifversion fpt or ghec or ghes %}公共{% endif %}仓库的 wiki,但您可以允许拥有 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 帐户的任何人编辑您的 wiki。' +title: Changing access permissions for wikis +intro: 'Only repository collaborators can edit a {% ifversion fpt or ghec or ghes %}public{% endif %} repository''s wiki by default, but you can allow anyone with an account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} to edit your wiki.' product: '{% data reusables.gated-features.wikis %}' redirect_from: - /articles/changing-access-permissions-for-wikis @@ -13,17 +13,13 @@ versions: topics: - Community shortTitle: Change access permissions -ms.openlocfilehash: 51a9ec690f0bdad1be302592091565b65e5f9b9b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145086615' --- -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -3. 在“功能”下,取消选中“仅限于协作者编辑”。 - ![Wiki 编辑限制](/assets/images/help/wiki/wiki_restrict_editing.png) -## 延伸阅读 +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. Under Features, unselect **Restrict edits to collaborators only**. + ![Wiki restrict editing](/assets/images/help/wiki/wiki_restrict_editing.png) -- [禁用 Wiki](/communities/documenting-your-project-with-wikis/disabling-wikis) +## Further reading + +- "[Disabling wikis](/communities/documenting-your-project-with-wikis/disabling-wikis)" diff --git a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md index 4b799550c2..a73f507945 100644 --- a/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md +++ b/translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md @@ -1,57 +1,53 @@ --- -title: 将仓库从 GitHub 克隆到 GitHub Desktop -intro: '您可以使用 {% data variables.product.prodname_dotcom %} 将远程仓库克隆到 {% data variables.product.prodname_desktop %}。' +title: Cloning a repository from GitHub to GitHub Desktop +intro: 'You can use {% data variables.product.prodname_dotcom %} to clone remote repositories to {% data variables.product.prodname_desktop %}.' redirect_from: - /desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop - /desktop/contributing-and-collaborating-using-github-desktop/cloning-a-repository-from-github-to-github-desktop versions: fpt: '*' shortTitle: Clone a GitHub repo -ms.openlocfilehash: ba4ddcc8c3d95454ab06cac0293162e2fe01fe32 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145099284' --- {% tip %} -提示:也可使用 {% data variables.product.prodname_desktop %} 克隆 {% data variables.product.prodname_dotcom %} 上的存储库。 有关详细信息,请参阅“[从 {% data variables.product.prodname_desktop %} 克隆存储库](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)”。 +**Tip:** You also can use {% data variables.product.prodname_desktop %} to clone repositories that exist on {% data variables.product.prodname_dotcom %}. For more information, see "[Cloning a repository from {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)." {% endtip %} {% mac %} -1. 开始克隆前,请先登录到 {% data variables.product.product_location %} 和 {% data variables.product.prodname_desktop %}。 -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.open-with-github-desktop %} -5. 单击“选择...”,并使用 Finder 窗口找到要克隆存储库的本地路径。 -![URL 选项卡中的“选择”按钮](/assets/images/help/desktop/clone-choose-button-url-mac.png) +1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_desktop %} before you start to clone. +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.open-with-github-desktop %} +5. Click **Choose...** and, using the Finder window, navigate to a local path where you want to clone the repository. +![The choose button on the URL tab](/assets/images/help/desktop/clone-choose-button-url-mac.png) {% note %} - 注意:如果存储库配置为使用 LFS,系统会提示你初始化 {% data variables.large_files.product_name_short %}。 + **Note:** If the repository is configured to use LFS, you will be prompted to initialize {% data variables.large_files.product_name_short %}. {% endnote %} -5. 单击“克隆”。 -![URL 选项卡中的“克隆”按钮](/assets/images/help/desktop/clone-button-url-mac.png) +5. Click **Clone**. +![The clone button on the URL tab](/assets/images/help/desktop/clone-button-url-mac.png) {% endmac %} {% windows %} -1. 开始克隆前,请先登录到 {% data variables.product.product_location %} 和 {% data variables.product.prodname_desktop %}。 -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.open-with-github-desktop %} -5. 单击“选择...”,并使用 Windows 资源管理器找到要克隆存储库的本地路径。 -![“选择”按钮](/assets/images/help/desktop/clone-choose-button-url-win.png) +1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_desktop %} before you start to clone. +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.open-with-github-desktop %} +5. 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-url-win.png) {% note %} - 注意:如果存储库配置为使用 LFS,系统会提示你初始化 {% data variables.large_files.product_name_short %}。 + **Note:** If the repository is configured to use LFS, you will be prompted to initialize {% data variables.large_files.product_name_short %}. {% endnote %} -5. 单击“克隆”。 -![“克隆”按钮](/assets/images/help/desktop/clone-button-url-win.png) +5. Click **Clone**. +![The clone button](/assets/images/help/desktop/clone-button-url-win.png) {% endwindows %} diff --git a/translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md b/translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md index a38e14a9c2..b550521342 100644 --- a/translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md +++ b/translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md @@ -1,24 +1,18 @@ --- -title: 关于连接到 GitHub -intro: '{% data variables.product.prodname_desktop %} 使用 HTTPS 与 {% data variables.product.prodname_dotcom %} 安全地交换数据。' +title: About connections to GitHub +intro: '{% data variables.product.prodname_desktop %} uses HTTPS to securely exchange data with {% data variables.product.prodname_dotcom %}.' redirect_from: - /desktop/getting-started-with-github-desktop/about-connections-to-github - /desktop/installing-and-configuring-github-desktop/about-connections-to-github versions: fpt: '*' shortTitle: About connections -ms.openlocfilehash: 94f1e7db78504a115b233f17485f1b12299a1e11 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145099239' --- -当您对远程仓库执行拉取、推送、克隆和复刻操作时,{% data variables.product.prodname_desktop %} 将连接到 {% data variables.product.prodname_dotcom %}。 要从 {% data variables.product.prodname_desktop %} 连接到 {% data variables.product.prodname_dotcom %},您必须验证您的帐户。 有关详细信息,请参阅“[向 {% data variables.product.prodname_dotcom %} 进行身份验证](/desktop/getting-started-with-github-desktop/authenticating-to-github)”。 +{% data variables.product.prodname_desktop %} connects to {% data variables.product.prodname_dotcom %} when you pull from, push to, clone, and fork remote repositories. To connect to {% data variables.product.prodname_dotcom %} from {% data variables.product.prodname_desktop %}, you must authenticate your account. For more information, see "[Authenticating to {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)." -在向 {% data variables.product.prodname_dotcom %} 验证后,您可以通过 {% data variables.product.prodname_desktop %} 连接远程仓库。 {% data variables.product.prodname_desktop %} 缓存您的凭据(用户名和密码或个人访问令牌),并使用凭据验证到远程存储库的每个连接。 +After you authenticate to {% data variables.product.prodname_dotcom %}, you can connect to remote repositories with {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} caches your credentials (username and password or {% data variables.product.pat_generic %}) and uses the credentials to authenticate for each connection to the remote repository. -{% data variables.product.prodname_desktop %} 使用 HTTPS 连接到 {% data variables.product.prodname_dotcom %}。 如果使用 {% data variables.product.prodname_desktop %} 访问使用 SSH 克隆的仓库,可能会遇到错误。 要连接到使用 SSH 克隆的仓库,请更改远程 URL。 有关详细信息,请参阅“[管理远程存储库](/github/getting-started-with-github/managing-remote-repositories)”。 +{% data variables.product.prodname_desktop %} connects to {% data variables.product.prodname_dotcom %} using HTTPS. If you use {% data variables.product.prodname_desktop %} to access repositories that were cloned using SSH, you may encounter errors. To connect to a repository that was cloned using SSH, change the remote's URLs. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." -## 延伸阅读 -- [从 GitHub Desktop 克隆和复刻存储库](/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop) +## Further reading +- "[Cloning and forking repositories from GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop)" diff --git a/translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md b/translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md index 519cf16890..220f7b85da 100644 --- a/translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md +++ b/translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md @@ -1,120 +1,126 @@ --- -title: 对 GitHub 进行身份验证 +title: Authenticating to GitHub shortTitle: Authentication -intro: '您可以通过向 {% data variables.product.prodname_dotcom %} 验证来安全地访问您的帐户在 {% data variables.product.prodname_desktop %} 上的资源。' +intro: 'You can securely access your account''s resources on {% data variables.product.prodname_desktop %} by authenticating to {% data variables.product.prodname_dotcom %}.' redirect_from: - /desktop/getting-started-with-github-desktop/authenticating-to-github-using-the-browser - /desktop/getting-started-with-github-desktop/authenticating-to-github - /desktop/installing-and-configuring-github-desktop/authenticating-to-github versions: fpt: '*' -ms.openlocfilehash: e88d59a03d876b23d8eb72aae7324db64981096f -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145099231' --- -## 关于身份验证 +## About authentication -为确保帐户安全,必须先进行身份验证,然后才可使用 {% data variables.product.prodname_desktop %} 访问 {% data variables.product.prodname_dotcom %}上的资源。 +To keep your account secure, you must authenticate before you can use {% data variables.product.prodname_desktop %} to access resources on {% data variables.product.prodname_dotcom %}. -在进行身份验证之前,{% data reusables.desktop.get-an-account %} +Before you authenticate, {% data reusables.desktop.get-an-account %} {% mac %} -## 在 {% data variables.product.prodname_dotcom %} 上验证帐户 +## Authenticating an account on {% data variables.product.prodname_dotcom %} -{% data reusables.desktop.mac-select-desktop-menu %} {% data reusables.desktop.mac-select-accounts %} -3. 在“{% data variables.product.prodname_dotcom_the_website %}”的右侧,单击“登录”。 - ![GitHub 的登录按钮](/assets/images/help/desktop/mac-sign-in-github.png) {% data reusables.desktop.sign-in-browser %} +{% data reusables.desktop.mac-select-desktop-menu %} +{% data reusables.desktop.mac-select-accounts %} +3. To the right of "{% data variables.product.prodname_dotcom_the_website %}," click **Sign In**. + ![The Sign In button for GitHub](/assets/images/help/desktop/mac-sign-in-github.png) +{% data reusables.desktop.sign-in-browser %} -{% data reusables.desktop.authenticate-in-browser %} {% data reusables.desktop.2fa-in-browser %} -7. 在 {% data variables.product.prodname_dotcom %} 验证帐户后,按照提示返回到 {% data variables.product.prodname_desktop %}。 +{% data reusables.desktop.authenticate-in-browser %} +{% data reusables.desktop.2fa-in-browser %} +7. After {% data variables.product.prodname_dotcom %} authenticates your account, follow the prompts to return to {% data variables.product.prodname_desktop %}. -## 在 {% data variables.product.prodname_ghe_server %} 上验证帐户 +## Authenticating an account on {% data variables.product.prodname_ghe_server %} -{% data reusables.desktop.mac-select-desktop-menu %} {% data reusables.desktop.mac-select-accounts %} {% data reusables.desktop.choose-product-authenticate %} -4. 若要在 {% data variables.product.product_location_enterprise %} 上添加帐户,请在“企业地址”下键入实例的 URL,然后单击“继续”。 - ![GitHub Enterprise 的登录按钮](/assets/images/help/desktop/mac-sign-in-button-enterprise.png) {% data reusables.desktop.sign-in-browser %} -1. 若要对 {% data variables.product.product_location_enterprise %} 帐户进行身份验证,请键入帐户凭据,然后单击“登录”。 - ![浏览器中 {% data variables.product.prodname_ghe_server %} 的“登录”按钮](/assets/images/help/desktop/enterprise-sign-in-button-browser.png) +{% data reusables.desktop.mac-select-desktop-menu %} +{% data reusables.desktop.mac-select-accounts %} +{% data reusables.desktop.choose-product-authenticate %} +4. To add an account on {% data variables.location.product_location_enterprise %}, type the URL for your instance under "Enterprise address," then click **Continue**. + ![The Sign In button for GitHub Enterprise](/assets/images/help/desktop/mac-sign-in-button-enterprise.png) +{% data reusables.desktop.sign-in-browser %} +1. To authenticate to {% data variables.location.product_location_enterprise %} account, type your account credentials and click **Sign in**. + ![The Sign In button for {% data variables.product.prodname_ghe_server %} in browser](/assets/images/help/desktop/enterprise-sign-in-button-browser.png) - 或者,如果你已登录 {% data variables.product.product_location_enterprise %} 帐户,请按照提示返回 {% data variables.product.prodname_desktop %} 完成身份验证。 + Alternatively, if you were already signed in to {% data variables.location.product_location_enterprise %} account, follow the prompts to return to {% data variables.product.prodname_desktop %} to finish authenticating. {% endmac %} {% windows %} -## 在 {% data variables.product.prodname_dotcom %} 上验证帐户 +## Authenticating an account on {% data variables.product.prodname_dotcom %} -{% data reusables.desktop.windows-choose-options %} {% data reusables.desktop.windows-select-accounts %} -3. 在“GitHub.com”右侧,单击“登录”。 - ![GitHub 的登录按钮](/assets/images/help/desktop/windows-sign-in-github.png) {% data reusables.desktop.sign-in-browser %} +{% data reusables.desktop.windows-choose-options %} +{% data reusables.desktop.windows-select-accounts %} +3. To the right of "GitHub.com," click **Sign in**. + ![The Sign In button for GitHub](/assets/images/help/desktop/windows-sign-in-github.png) +{% data reusables.desktop.sign-in-browser %} {% data reusables.user-settings.password-authentication-deprecation-desktop %} -{% data reusables.desktop.authenticate-in-browser %} {% data reusables.desktop.2fa-in-browser %} -7. 在 {% data variables.product.prodname_dotcom %} 验证帐户后,按照提示返回到 {% data variables.product.prodname_desktop %}。 +{% data reusables.desktop.authenticate-in-browser %} +{% data reusables.desktop.2fa-in-browser %} +7. After {% data variables.product.prodname_dotcom %} authenticates your account, follow the prompts to return to {% data variables.product.prodname_desktop %}. -## 在 {% data variables.product.prodname_enterprise %} 上验证帐户 +## Authenticating an account on {% data variables.product.prodname_enterprise %} -{% data reusables.desktop.windows-choose-options %} {% data reusables.desktop.windows-select-accounts %} {% data reusables.desktop.choose-product-authenticate %} -4. 若要添加 {% data variables.product.prodname_enterprise %} 帐户,请在“企业地址”下键入凭据,然后单击“继续”。 - ![GitHub Enterprise 的登录按钮](/assets/images/help/desktop/windows-sign-in-button-enterprise.png) {% data reusables.desktop.retrieve-2fa %} +{% data reusables.desktop.windows-choose-options %} +{% data reusables.desktop.windows-select-accounts %} +{% data reusables.desktop.choose-product-authenticate %} +4. To add a {% data variables.product.prodname_enterprise %} account, type your credentials under "Enterprise address," then click **Continue**. + ![The Sign In button for GitHub Enterprise](/assets/images/help/desktop/windows-sign-in-button-enterprise.png) +{% data reusables.desktop.retrieve-2fa %} {% endwindows %} -## 排查身份验证问题 +## Troubleshooting authentication issues -如果 {% data variables.product.prodname_desktop %} 遇到身份验证错误,可以使用错误消息进行故障排除。 +If {% data variables.product.prodname_desktop %} encounters an authentication error, you can use error messages to troubleshoot. -如果您遇到身份验证错误,请先尝试在 {% data variables.product.prodname_desktop %} 上注销您的帐户,然后重新登录。 +If you encounter an authentication error, first try signing out and signing back in to your account on {% data variables.product.prodname_desktop %}. -对于某些错误,{% data variables.product.prodname_desktop %} 会以错误消息提示您。 如果没有提示,或者要查找任何错误的更多信息,请使用以下步骤查看 {% data variables.product.prodname_desktop %} 日志文件。 +For some errors, {% data variables.product.prodname_desktop %} will prompt you with an error message. If you are not prompted, or to find more information about any error, view the {% data variables.product.prodname_desktop %} log files by using the following steps. {% mac %} -1. 使用“帮助”下拉菜单,然后单击“在 Finder 中显示日志” 。 - ![“在 Finder 中显示日志”按钮](/assets/images/help/desktop/mac-show-logs.png) -2. 选择您遇到身份验证错误之日的日志文件。 +1. Use the **Help** drop-down menu and click **Show Logs in Finder**. + ![The Show Logs in Finder button](/assets/images/help/desktop/mac-show-logs.png) +2. Select the log file from the date when you encountered the authentication error. {% endmac %} {% windows %} -1. 使用“帮助”下拉菜单,然后单击“在 Explorer 中显示日志” 。 - ![“在 Explorer 中显示日志”按钮](/assets/images/help/desktop/windows-show-logs.png) -2. 选择您遇到身份验证错误之日的日志文件。 +1. Use the **Help** drop-down menu and click **Show Logs in Explorer**. + ![The Show Logs in Explorer button](/assets/images/help/desktop/windows-show-logs.png) +2. Select the log file from the date when you encountered the authentication error. {% endwindows %} -查看下面的故障排除信息,了解您遇到的错误消息。 +Review the troubleshooting information below for the error message that you encounter. -### 无效凭据 +### Bad credentials ```shell Error: Bad credentials ``` -此错误意味着存储的帐户凭据有问题。 +This error means that there is an issue with your stored account credentials. -要解决问题,请在 {% data variables.product.prodname_desktop %} 上注销您的帐户,然后重新登录。 +To troubleshoot, sign out of your account on {% data variables.product.prodname_desktop %} and then sign back in. -### 空令牌 +### Empty token ```shell -info: [ui] [AppStore.withAuthenticatingUser] account found for repository: node - (empty token) +info: [ui] [AppStore.withAuthenticatingUser] account found for repository: node - USERNAME (empty token) ``` -这个错误表示 {% data variables.product.prodname_desktop %} 找不到它在系统密钥链中创建的访问令牌。 +This error means that {% data variables.product.prodname_desktop %} is unable to find the access token that it created in the system keychain. -要解决问题,请在 {% data variables.product.prodname_desktop %} 上注销您的帐户,然后重新登录。 +To troubleshoot, sign out of your account on {% data variables.product.prodname_desktop %} and then sign back in. -### 未找到仓库 +### Repository not found ```shell fatal: repository 'https://github.com//.git' not found @@ -122,11 +128,11 @@ fatal: repository 'https://github.com//.git' not found (The error was parsed as 8: The repository does not seem to exist anymore. You may not have access, or it may have been deleted or renamed.) ``` -这个错误表示您没有权限访问您想克隆的仓库。 +This error means that you do not have permission to access the repository that you are trying to clone. -要解决问题,请联系您组织中管理权限的人。 +To troubleshoot, contact the person in your organization who administers permissions. -### 无法读取远程仓库 +### Could not read from remote repository ```shell git@github.com: Permission denied (publickey). @@ -135,11 +141,11 @@ fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. ``` -这个错误表示您没有设置有效的 SSH 密钥。 +This error means that you do not have a valid SSH key set up. -若要进行故障排除,请参阅“[生成新的 SSH 密钥并将其添加到 SSH 代理](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)”。 +To troubleshoot, see "[Generating a new SSH key and adding it to the SSH agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." -### 无法克隆 +### Failed to clone ```shell fatal: clone of 'git@github.com:/' into submodule path '' failed @@ -151,34 +157,34 @@ Please make sure you have the correct access rights and the repository exists. ``` -这个错误表示您尝试克隆的仓库包含您无法访问的子模块,或者您没有设置有效的 SSH 密钥。 +This error means that either the repository that you are trying to clone has submodules that you do not have access to or you do not have a valid SSH key set up. -如果您无法访问子模块,请通过联系管理仓库权限的人解决问题。 +If you do not have access to the submodules, troubleshoot by contacting the person who administers permissions for the repository. -如果没有设置有效的 SSH 密钥,请参阅“[生成新的 SSH 密钥并将其添加到 SSH 代理](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)”。 +If you do not have a valid SSH key set up, see "[Generating a new SSH key and adding it to the SSH agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." {% windows %} -### 无法读取 AskPass 响应 +### Unable to read AskPass response ```shell error: unable to read askpass response from '/Users//GitHub Desktop.app/Contents/Resources/app/static/ask-pass-trampoline.sh' fatal: could not read Username for 'https://github.com': terminal prompts disabled ``` -这个错误可能是多个事件造成的。 +This error can be caused by multiple events. -如果 `Command Processor` 注册表项已修改,{% data variables.product.prodname_desktop %} 将以 `Authentication failed` 错误响应。 要检查这些注册表条目是否已修改,请按照以下步骤操作。 +If the `Command Processor` registry entries are modified, {% data variables.product.prodname_desktop %} will respond with an `Authentication failed` error. To check if these registry entries have been modified, follow these steps. -1. 打开注册表编辑器 (`regedit.exe`) 并导航到以下位置。 +1. Open the Registry Editor (`regedit.exe`) and navigate to the following locations. `HKEY_CURRENT_USER\Software\Microsoft\Command Processor\` `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor\` -2. 检查任一位置是否有 `Autorun` 值。 -3. 如果有 `Autorun` 值,请将其删除。 +2. Check to see if there is an `Autorun` value in either location. +3. If there is an `Autorun` value, delete it. -如果您的 Windows 用户名延长了 Unicode 字符,可能导致 AskPass 响应错误。 要解决问题,请创建新的 Windows 用户帐户,然后将文件迁移到该帐户。 有关详细信息,请参阅 Microsoft 文档中的“[在 Windows 中创建用户帐户](https://support.microsoft.com/en-us/help/13951/windows-create-user-account)”。 +If your Windows username has extended Unicode characters, it may cause an AskPass response error. To troubleshoot, create a new Windows user account and migrate your files to that account. For more information, see "[Create a user account in Windows](https://support.microsoft.com/en-us/help/13951/windows-create-user-account)" in the Microsoft documentation. {% endwindows %} -## 延伸阅读 -- [关于向 GitHub 进行身份验证](/github/authenticating-to-github/about-authentication-to-github) +## Further reading +- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)" diff --git a/translations/zh-CN/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md b/translations/zh-CN/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md index cf3b460a7a..8f7e7bdec0 100644 --- a/translations/zh-CN/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md +++ b/translations/zh-CN/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md @@ -1,5 +1,5 @@ --- -title: GitHub 应用的速率限制 +title: Rate limits for GitHub Apps intro: '{% data reusables.shortdesc.rate_limits_github_apps %}' redirect_from: - /early-access/integrations/rate-limits @@ -15,62 +15,57 @@ versions: topics: - GitHub Apps shortTitle: Rate limits -ms.openlocfilehash: fd2c9a92c6603a6e64ec17b614f46baf2370c98b -ms.sourcegitcommit: d243bbae4ce3c849695b5bc9221e705ee5a4a64f -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 07/12/2022 -ms.locfileid: '147081126' --- + {% data reusables.enterprise.rate_limit %} {% data reusables.rest-api.always-check-your-limit %} {% ifversion ghec or fpt %} -## 关于应用程序的速率限制 +## About rate limits for apps -{% data variables.product.prodname_github_apps %} 和 {% data variables.product.prodname_oauth_apps %} 的速率限制取决于安装应用程序的组织的计划。 有关详细信息,请参阅“[{% data variables.product.company_short %} 的产品](/get-started/learning-about-github/githubs-products)”和“[{% data variables.product.company_short %} 帐户的类型](/get-started/learning-about-github/types-of-github-accounts#organization-accounts)”。 +Rate limits for {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} depend on the plan for the organization where you install the application. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)" and "[Types of {% data variables.product.company_short %} accounts](/get-started/learning-about-github/types-of-github-accounts#organization-accounts)." {% endif %} -## 服务器到服务器请求 +## Server-to-server requests {% ifversion ghec or fpt %} -### {% data variables.product.prodname_dotcom_the_website %} 的默认服务器到服务器速率限制 +### Default server-to-server rate limits for {% data variables.product.prodname_dotcom_the_website %} {% endif %} -发出服务器-服务器请求的 {% data variables.product.prodname_github_apps %} 使用安装的最低速率限制为每小时 5,000 个请求。 如果应用程序安装在具有 20 个以上用户的组织中,则该应用程序每小时为每个用户再接收 50 个请求。 具有 20 个以上仓库的安装每小时会为每个仓库再接收 50 个请求。 安装的最大速率限制为每小时 12,500 个请求。 +{% data variables.product.prodname_github_apps %} making server-to-server requests use the installation's minimum rate limit of 5,000 requests per hour. If an application is installed on an organization with more than 20 users, the application receives another 50 requests per hour for each user. Installations that have more than 20 repositories receive another 50 requests per hour for each repository. The maximum rate limit for an installation is 12,500 requests per hour. {% ifversion fpt or ghec %} -### {% data variables.product.prodname_ghe_cloud %} 的服务器到服务器速率限制 +### Server-to-server rate limits for {% data variables.product.prodname_ghe_cloud %} {% endif %} {% ifversion fpt or ghec %} -安装在 {% data variables.product.product_location %} 上企业内的组织或存储库上的 {% data variables.product.prodname_github_apps %} 每小时有 15,000 个请求的限制。 +{% data variables.product.prodname_github_apps %} that are installed on an organization within an enterprise on {% data variables.location.product_location %} are subject to a limit of 15,000 requests per hour per organization that has installed the app. {% endif %} -## 用户到服务器请求 +## User-to-server requests -{% data variables.product.prodname_github_apps %} 和 {% data variables.product.prodname_oauth_apps %} 还可以代表用户执行操作,在用户授权应用后发出用户到服务器的请求。 有关详细信息,请参阅“[授权 {% data variables.product.prodname_github_apps %}](/authentication/keeping-your-account-and-data-secure/authorizing-github-apps)”和“[授权 {% data variables.product.prodname_oauth_apps %}](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)”。 +{% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} can also act on behalf of a user, making user-to-server requests after the user authorizes the app. For more information, see "[Authorizing {% data variables.product.prodname_github_apps %}](/authentication/keeping-your-account-and-data-secure/authorizing-github-apps)" and "[Authorizing {% data variables.product.prodname_oauth_apps %}](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)." -来自 {% data variables.product.prodname_oauth_apps %} 的用户到服务器请求使用 OAuth 令牌进行身份验证。 来自 {% data variables.product.prodname_github_apps %} 的用户到服务器请求使用 OAuth 令牌或即将过期的用户访问令牌进行身份验证。 有关详细信息,请参阅“[为 {% data variables.product.prodname_github_apps %} 识别和授权用户](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#identifying-and-authorizing-users-for-github-apps)”和“[授权 {% data variables.product.prodname_oauth_apps %}](/developers/apps/building-oauth-apps/authorizing-oauth-apps)”。 +User-to-server requests from {% data variables.product.prodname_oauth_apps %} are authenticated with an OAuth token. User-to-server requests from {% data variables.product.prodname_github_apps %} are authenticated with either an OAuth token or an expiring user access token. For more information, see "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#identifying-and-authorizing-users-for-github-apps)" and "[Authorizing {% data variables.product.prodname_oauth_apps %}](/developers/apps/building-oauth-apps/authorizing-oauth-apps)." {% ifversion fpt or ghec %} -### {% data variables.product.prodname_dotcom_the_website %} 的默认用户到服务器速率限制 +### Default user-to-server rate limits for {% data variables.product.prodname_dotcom_the_website %} {% endif %} {% ifversion ghec %} -{% data variables.product.prodname_github_apps %} 发出的用户到服务器请求的速率限制取决于应用程序的安装位置。 如果应用程序安装在 {% data variables.product.product_location %} 上由企业拥有的组织或存储库上,则速率高于企业外部的安装。 +The rate limits for user-to-server requests made by {% data variables.product.prodname_github_apps %} depend on where the app is installed. If the app is installed on organizations or repositories owned by an enterprise on {% data variables.location.product_location %}, then the rate is higher than for installations outside an enterprise. {% endif %} @@ -78,13 +73,13 @@ ms.locfileid: '147081126' {% ifversion fpt or ghec %} -### {% data variables.product.prodname_ghe_cloud %} 的用户到服务器速率限制 +### User-to-server rate limits for {% data variables.product.prodname_ghe_cloud %} {% data reusables.apps.user-to-server-rate-limits-ghec %} {% endif %} -## 延伸阅读 +## Further reading -- REST API 文档中的“[速率限制](/rest/overview/resources-in-the-rest-api#rate-limiting)” -- GraphQL API 文档中的“[资源限制](/graphql/overview/resource-limitations)” +- "[Rate limiting](/rest/overview/resources-in-the-rest-api#rate-limiting)" in the REST API documentation +- "[Resource limitations](/graphql/overview/resource-limitations)" in the GraphQL API documentation diff --git a/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md index 18e234e87b..9ed610b338 100644 --- a/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md +++ b/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md @@ -1,5 +1,5 @@ --- -title: 授权 OAuth 应用 +title: Authorizing OAuth Apps intro: '{% data reusables.shortdesc.authorizing_oauth_apps %}' redirect_from: - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-authorization-options-for-oauth-apps @@ -16,73 +16,67 @@ versions: ghec: '*' topics: - OAuth Apps -ms.openlocfilehash: 10aa111156377c08f0dc4ad0210cf8ad30b8a3ac -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717787' --- -{% data variables.product.product_name %} 的 OAuth 实现支持标准[授权代码授权类型](https://tools.ietf.org/html/rfc6749#section-4.1)和对无权访问 Web 浏览器的应用的 OAuth 2.0 [设备授权](https://tools.ietf.org/html/rfc8628)。 +{% data variables.product.product_name %}'s OAuth implementation supports the standard [authorization code grant type](https://tools.ietf.org/html/rfc6749#section-4.1) and the OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628) for apps that don't have access to a web browser. -如果想跳过以标准方式授权应用(例如在测试应用时),可以使用[非 Web 应用程序流](#non-web-application-flow)。 +If you want to skip authorizing your app in the standard way, such as when testing your app, you can use the [non-web application flow](#non-web-application-flow). -要授权您的 OAuth 应用程序,请考虑哪个授权流程最适合您的应用程序。 +To authorize your OAuth app, consider which authorization flow best fits your app. -- [Web 应用程序流](#web-application-flow):用于授权用户使用在浏览器中运行的标准 OAuth 应用。 (不支持[隐式授权类型](https://tools.ietf.org/html/rfc6749#section-4.2)。) -- [设备流](#device-flow):用于无外设应用,例如 CLI 工具。 +- [web application flow](#web-application-flow): Used to authorize users for standard OAuth apps that run in the browser. (The [implicit grant type](https://tools.ietf.org/html/rfc6749#section-4.2) is not supported.) +- [device flow](#device-flow): Used for headless apps, such as CLI tools. -## Web 应用程序流程 +## Web application flow {% note %} -注意:如果要生成 GitHub 应用,仍可以使用 OAuth Web 应用程序流,但设置方面有一些重要差别。 有关详细信息,请参阅“[标识和授权 GitHub 应用的用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。 +**Note:** If you are building a GitHub App, you can still use the OAuth web application flow, but the setup has some important differences. See "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information. {% endnote %} -授权应用程序用户的 web 应用程序流程是: +The web application flow to authorize users for your app is: -1. 用户被重定向,以请求他们的 GitHub 身份 -2. 用户被 GitHub 重定向回您的站点 -3. 您的应用程序使用用户的访问令牌访问 API +1. Users are redirected to request their GitHub identity +2. Users are redirected back to your site by GitHub +3. Your app accesses the API with the user's access token -### 1. 请求用户的 GitHub 标识 +### 1. Request a user's GitHub identity GET {% data variables.product.oauth_host_code %}/login/oauth/authorize -当 GitHub 应用指定 `login` 参数时,它将提示用户使用他们可用于登录和授权你的应用的特定帐户。 +When your GitHub App specifies a `login` parameter, it prompts users with a specific account they can use for signing in and authorizing your app. -#### 参数 +#### Parameters -名称 | 类型 | 说明 +Name | Type | Description -----|------|-------------- -`client_id`|`string` | “必需”。 {% ifversion fpt or ghec %}[注册](https://github.com/settings/applications/new){% else %}registered{% endif %}时从 GitHub 收到的客户端 ID。 -`redirect_uri`|`string` | 用户获得授权后被发送到的应用程序中的 URL。 请参阅以下有关[重定向 URL](#redirect-urls) 的详细信息。 -`login` | `string` | 提供用于登录和授权应用程序的特定账户。 -`scope`|`string` | [范围](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)的空格分隔列表。 如果未提供,则 `scope` 默认为未授权应用程序的任何范围的用户的空列表。 对于已向应用程序授权作用域的用户,不会显示含作用域列表的 OAuth 授权页面。 相反,通过用户向应用程序授权的作用域集,此流程步骤将自动完成。 例如,如果用户已经执行了两次 Web 流,并且已授权一个具有 `user` 范围的令牌和另一个具有 `repo` 范围的令牌,则不提供 `scope` 的第三个 Web 流将收到具有 `user` 和 `repo` 范围的令牌。 +`client_id`|`string` | **Required**. The client ID you received from GitHub when you {% ifversion fpt or ghec %}[registered](https://github.com/settings/applications/new){% else %}registered{% endif %}. +`redirect_uri`|`string` | The URL in your application where users will be sent after authorization. See details below about [redirect urls](#redirect-urls). +`login` | `string` | Suggests a specific account to use for signing in and authorizing the app. +`scope`|`string` | A space-delimited list of [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). If not provided, `scope` defaults to an empty list for users that have not authorized any scopes for the application. For users who have authorized scopes for the application, the user won't be shown the OAuth authorization page with the list of scopes. Instead, this step of the flow will automatically complete with the set of scopes the user has authorized for the application. For example, if a user has already performed the web flow twice and has authorized one token with `user` scope and another token with `repo` scope, a third web flow that does not provide a `scope` will receive a token with `user` and `repo` scope. `state` | `string` | {% data reusables.apps.state_description %} -`allow_signup`|`string` | 在 OAuth 流程中,是否向经过验证的用户提供注册 GitHub 的选项。 默认为 `true`。 在策略禁止注册时使用 `false`。 +`allow_signup`|`string` | Whether or not unauthenticated users will be offered an option to sign up for GitHub during the OAuth flow. The default is `true`. Use `false` when a policy prohibits signups. -### 2. 用户被 GitHub 重定向回你的站点 +### 2. Users are redirected back to your site by GitHub -如果用户接受你的请求,{% data variables.product.product_name %} 会使用代码参数中的临时 `code` 以及你在上一步的 `state` 参数中提供的状态重定向回你的站点。 临时代码将在 10 分钟后到期。 如果状态不匹配,然后第三方创建了请求,您应该中止此过程。 +If the user accepts your request, {% data variables.product.product_name %} redirects back to your site with a temporary `code` in a code parameter as well as the state you provided in the previous step in a `state` parameter. The temporary code will expire after 10 minutes. If the states don't match, then a third party created the request, and you should abort the process. -将此 `code` 交换为访问令牌: +Exchange this `code` for an access token: POST {% data variables.product.oauth_host_code %}/login/oauth/access_token -#### 参数 +#### Parameters -名称 | 类型 | 说明 +Name | Type | Description -----|------|-------------- -`client_id` | `string` | **必填。** 从 {% data variables.product.product_name %} 收到的 {% data variables.product.prodname_oauth_app %} 的客户端 ID。 -`client_secret` | `string` | **必填。** 从 {% data variables.product.product_name %} 收到的 {% data variables.product.prodname_oauth_app %} 的客户端密码。 -`code` | `string` | **必填。** 收到的作为对步骤 1 的响应的代码。 -`redirect_uri` | `string` | 用户获得授权后被发送到的应用程序中的 URL。 +`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}. +`client_secret` | `string` | **Required.** The client secret you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}. +`code` | `string` | **Required.** The code you received as a response to Step 1. +`redirect_uri` | `string` | The URL in your application where users are sent after authorization. -#### 响应 +#### Response -默认情况下,响应采用以下形式: +By default, the response takes the following form: ``` access_token=gho_16C7e42F292c6912E7710c838347Ae178B4a&scope=repo%2Cgist&token_type=bearer @@ -108,57 +102,57 @@ Accept: application/xml ``` -### 3. 使用访问令牌访问 API +### 3. Use the access token to access the API -访问令牌可用于代表用户向 API 提出请求。 +The access token allows you to make requests to the API on a behalf of a user. Authorization: Bearer OAUTH-TOKEN GET {% data variables.product.api_url_code %}/user -例如,您可以像以下这样在 curl 中设置“授权”标头: +For example, in curl you can set the Authorization header like this: ```shell curl -H "Authorization: Bearer OAUTH-TOKEN" {% data variables.product.api_url_pre %}/user ``` -## 设备流程 +## Device flow {% note %} -注意:设备流处于公开测试阶段,可能会发生更改。 +**Note:** The device flow is in public beta and subject to change. {% endnote %} -设备流程允许您授权用户使用无头应用程序,例如 CLI 工具或 Git 凭据管理器。 +The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager. {% ifversion device-flow-is-opt-in %} -在使用设备流识别和授权用户之前,必须先在应用的设置中启用它。 有关在应用中启用设备流的详细信息,请参阅“[修改 OAuth 应用](/developers/apps/managing-oauth-apps/modifying-an-oauth-app)”(适用于 OAuth 应用)和“[修改 GitHub 应用](/developers/apps/managing-github-apps/modifying-a-github-app)”(适用于 GitHub 应用)。 +Before you can use the device flow to authorize and identify users, you must first enable it in your app's settings. For more information about enabling the device flow in your app, see "[Modifying an OAuth App](/developers/apps/managing-oauth-apps/modifying-an-oauth-app)" for OAuth Apps and "[Modifying a GitHub App](/developers/apps/managing-github-apps/modifying-a-github-app)" for GitHub Apps. {% endif %} -### 设备流程概述 +### Overview of the device flow -1. 您的应用程序会请求设备和用户验证码,并获取用户将在其中输入用户验证码的授权 URL。 -2. 应用程序提示用户在 {% data variables.product.device_authorization_url %} 中输入用户验证码。 -3. 应用程序轮询用户身份验证状态。 用户授权设备后,应用程序将能够使用新的访问令牌进行 API 调用。 +1. Your app requests device and user verification codes and gets the authorization URL where the user will enter the user verification code. +2. The app prompts the user to enter a user verification code at {% data variables.product.device_authorization_url %}. +3. The app polls for the user authentication status. Once the user has authorized the device, the app will be able to make API calls with a new access token. -### 第 1 步:应用程序从 GitHub 请求设备和用户验证码 +### Step 1: App requests the device and user verification codes from GitHub POST {% data variables.product.oauth_host_code %}/login/device/code -您的应用程序必须请求用户验证码和验证 URL,因为应用程序在下一步中提示用户进行身份验证时将使用它们。 此请求还返回设备验证代码,应用程序必须使用它们来接收访问令牌和检查用户身份验证的状态。 +Your app must request a user verification code and verification URL that the app will use to prompt the user to authenticate in the next step. This request also returns a device verification code that the app must use to receive an access token and check the status of user authentication. -#### 输入参数 +#### Input Parameters -名称 | 类型 | 说明 +Name | Type | Description -----|------|-------------- -`client_id` | `string` | **必填。** 从 {% data variables.product.product_name %} 收到的应用的客户端 ID。 -`scope` | `string` | 应用程序请求访问的范围。 +`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your app. +`scope` | `string` | The scope that your app is requesting access to. -#### 响应 +#### Response -默认情况下,响应采用以下形式: +By default, the response takes the following form: ``` device_code=3584d83530557fdd1f46af8289938c8ef79f9dc5&expires_in=900&interval=5&user_code=WDJB-MJHT&verification_uri=https%3A%2F%{% data variables.product.product_url %}%2Flogin%2Fdevice @@ -188,43 +182,43 @@ Accept: application/xml ``` -#### 响应参数 +#### Response parameters -名称 | 类型 | 说明 +Name | Type | Description -----|------|-------------- -`device_code` | `string` | 设备验证码为 40 个字符,用于验证设备。 -`user_code` | `string` | 用户验证码显示在设备上,以便用户可以在浏览器中输入该代码。 此代码为 8 个字符,中间有连字符。 -`verification_uri` | `string` | 用户需要在其中输入 `user_code` 的验证 URL:{% data variables.product.device_authorization_url %}。 -`expires_in` | `integer`| `device_code` 和 `user_code` 过期之前的秒数。 默认值为 900 秒或 15 分钟。 -`interval` | `integer` | 在能够发出新的访问令牌请求 (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) 以完成设备授权之前必须经过的最短秒数。 例如,如果间隔为 5,则只有经过 5 秒后才能发出新请求。 如果在 5 秒内发出多个请求,则将达到速率限制并收到 `slow_down` 错误。 +`device_code` | `string` | The device verification code is 40 characters and used to verify the device. +`user_code` | `string` | The user verification code is displayed on the device so the user can enter the code in a browser. This code is 8 characters with a hyphen in the middle. +`verification_uri` | `string` | The verification URL where users need to enter the `user_code`: {% data variables.product.device_authorization_url %}. +`expires_in` | `integer`| The number of seconds before the `device_code` and `user_code` expire. The default is 900 seconds or 15 minutes. +`interval` | `integer` | The minimum number of seconds that must pass before you can make a new access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) to complete the device authorization. For example, if the interval is 5, then you cannot make a new request until 5 seconds pass. If you make more than one request over 5 seconds, then you will hit the rate limit and receive a `slow_down` error. -### 第 2 步:提示用户在浏览器中输入用户代码 +### Step 2: Prompt the user to enter the user code in a browser -您的设备将显示用户验证码并提示用户在 {% data variables.product.device_authorization_url %} 中输入该代码。 +Your device will show the user verification code and prompt the user to enter the code at {% data variables.product.device_authorization_url %}. - ![用于输入设备上显示的用户验证码的字段](/assets/images/github-apps/device_authorization_page_for_user_code.png) + ![Field to enter the user verification code displayed on your device](/assets/images/github-apps/device_authorization_page_for_user_code.png) -### 第 3 步:应用程序轮询 GitHub 以检查用户是否授权设备 +### Step 3: App polls GitHub to check if the user authorized the device POST {% data variables.product.oauth_host_code %}/login/oauth/access_token -应用将发出轮询 `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` 的设备授权请求,直到设备和用户代码过期,或者用户已使用有效的用户代码成功授权应用。 应用必须使用在步骤 1 中检索到的最短轮询 `interval`,以免出现速率限制错误。 有关详细信息,请参阅“[设备流的速率限制](#rate-limits-for-the-device-flow)”。 +Your app will make device authorization requests that poll `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`, until the device and user codes expire or the user has successfully authorized the app with a valid user code. The app must use the minimum polling `interval` retrieved in step 1 to avoid rate limit errors. For more information, see "[Rate limits for the device flow](#rate-limits-for-the-device-flow)." -用户必须在 15 分钟(或 900 秒内)内输入有效代码。 15 分钟后,需要使用 `POST {% data variables.product.oauth_host_code %}/login/device/code` 请求新的设备授权代码。 +The user must enter a valid code within 15 minutes (or 900 seconds). After 15 minutes, you will need to request a new device authorization code with `POST {% data variables.product.oauth_host_code %}/login/device/code`. -一旦用户授权, 应用程序将收到一个访问令牌,该令牌可用于代表用户向 API 发出请求。 +Once the user has authorized, the app will receive an access token that can be used to make requests to the API on behalf of a user. -#### 输入参数 +#### Input parameters -名称 | 类型 | 说明 +Name | Type | Description -----|------|-------------- -`client_id` | `string` | **必填。** 从 {% data variables.product.product_name %} 收到的 {% data variables.product.prodname_oauth_app %} 的客户端 ID。 -`device_code` | `string` | **必填。** 从 `POST {% data variables.product.oauth_host_code %}/login/device/code` 请求收到的设备验证码。 -`grant_type` | `string` | **必填。** 授权类型必须是 `urn:ietf:params:oauth:grant-type:device_code`。 +`client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}. +`device_code` | `string` | **Required.** The device verification code you received from the `POST {% data variables.product.oauth_host_code %}/login/device/code` request. +`grant_type` | `string` | **Required.** The grant type must be `urn:ietf:params:oauth:grant-type:device_code`. -#### 响应 +#### Response -默认情况下,响应采用以下形式: +By default, the response takes the following form: ``` access_token=gho_16C7e42F292c6912E7710c838347Ae178B4a&token_type=bearer&scope=repo%2Cgist @@ -250,76 +244,88 @@ Accept: application/xml ``` -### 设备流程的速率限制 +### Rate limits for the device flow -当用户在浏览器上提交验证码时,每个应用程序在一个小时内的提交速率限制为 50 个。 +When a user submits the verification code on the browser, there is a rate limit of 50 submissions in an hour per application. -如果在请求之间所需的最小时间范围(即 `interval`)内发出多个访问令牌请求 (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`),你将达到速率限制,并收到 `slow_down` 错误响应。 `slow_down` 错误响应向上一个 `interval` 添加 5 秒钟的时间。 有关详细信息,请参阅[设备流错误](#errors-for-the-device-flow)。 +If you make more than one access token request (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) within the required minimum timeframe between requests (or `interval`), you'll hit the rate limit and receive a `slow_down` error response. The `slow_down` error response adds 5 seconds to the last `interval`. For more information, see the [Errors for the device flow](#errors-for-the-device-flow). -### 设备流程的错误代码 +### Error codes for the device flow -| 错误代码 | 说明 | +| Error code | Description | |----|----| -| `authorization_pending`| 授权请求待处理并且用户尚未输入用户代码时,将发生此错误。 应用应在不超出 [`interval`](#response-parameters) 的情况下继续轮询 `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` 请求,这需要每个请求之间的最短秒数。 | -| `slow_down` | 收到 `slow_down` 错误时,会使用 `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` 向请求之间所需的最短 `interval` 或时间范围添加 5 秒钟的额外时间。 例如,如果请求之间的启动间隔至少需要 5 秒,并且你收到了 `slow_down` 错误响应,那么现在必须等待至少 10 秒,然后才能发出新的 OAuth 访问令牌请求。 错误响应包括必须使用的新 `interval`。 -| `expired_token` | 如果设备代码已过期,则将看到 `token_expired` 错误。 您必须发出新的设备代码请求。 -| `unsupported_grant_type` | 轮询 OAuth 令牌请求 `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` 时,授权类型必须为 `urn:ietf:params:oauth:grant-type:device_code` 并且必须作为输入参数包含在内。 -| `incorrect_client_credentials` | 对于设备流程,您必须传递应用程序的客户端 ID,您可以在应用程序设置页面上找到该 ID。 设备流不需要 `client_secret`。 -| `incorrect_device_code` | 提供的 device_code 无效。 -| `access_denied` | 当用户在授权过程中单击取消时,你将收到 `access_denied` 错误,该用户将无法再次使用验证码。{% ifversion device-flow-is-opt-in %} -| `device_flow_disabled` | 尚未在应用的设置中启用设备流。 有关详细信息,请参阅“[设备流](#device-flow)”。{% endif %} +| `authorization_pending`| This error occurs when the authorization request is pending and the user hasn't entered the user code yet. The app is expected to keep polling the `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` request without exceeding the [`interval`](#response-parameters), which requires a minimum number of seconds between each request. | +| `slow_down` | When you receive the `slow_down` error, 5 extra seconds are added to the minimum `interval` or timeframe required between your requests using `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. For example, if the starting interval required at least 5 seconds between requests and you get a `slow_down` error response, you must now wait a minimum of 10 seconds before making a new request for an OAuth access token. The error response includes the new `interval` that you must use. +| `expired_token` | If the device code expired, then you will see the `token_expired` error. You must make a new request for a device code. +| `unsupported_grant_type` | The grant type must be `urn:ietf:params:oauth:grant-type:device_code` and included as an input parameter when you poll the OAuth token request `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`. +| `incorrect_client_credentials` | For the device flow, you must pass your app's client ID, which you can find on your app settings page. The `client_secret` is not needed for the device flow. +| `incorrect_device_code` | The device_code provided is not valid. +| `access_denied` | When a user clicks cancel during the authorization process, you'll receive a `access_denied` error and the user won't be able to use the verification code again.{% ifversion device-flow-is-opt-in %} +| `device_flow_disabled` | Device flow has not been enabled in the app's settings. For more information, see "[Device flow](#device-flow)."{% endif %} -有关详细信息,请参阅“[OAuth 2.0 设备授权](https://tools.ietf.org/html/rfc8628#section-3.5)”。 +For more information, see the "[OAuth 2.0 Device Authorization Grant](https://tools.ietf.org/html/rfc8628#section-3.5)." -## 非 Web 应用程序流程 +## Non-Web application flow -非 web 身份验证适用于测试等有限的情况。 如果需要,可以使用[基本身份验证](/rest/overview/other-authentication-methods#basic-authentication)通过[个人访问令牌设置页](/articles/creating-an-access-token-for-command-line-use)创建个人访问令牌。 此方法支持用户随时撤销访问权限。 +Non-web authentication is available for limited situations like testing. If you need to, you can use [Basic Authentication](/rest/overview/other-authentication-methods#basic-authentication) to create a {% data variables.product.pat_generic %} using your [{% data variables.product.pat_generic %}s settings page](/articles/creating-an-access-token-for-command-line-use). This technique enables the user to revoke access at any time. -{% ifversion fpt or ghes or ghec %} {% note %} +{% ifversion fpt or ghes or ghec %} +{% note %} -注意:使用非 Web 应用程序流创建 OAuth2 令牌时,如果你或你的用户启用了双因素身份验证,请确保了解如何[使用双因素身份验证](/rest/overview/other-authentication-methods#working-with-two-factor-authentication)。 +**Note:** When using the non-web application flow to create an OAuth2 token, make sure to understand how to [work with +two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication) if +you or your users have two-factor authentication enabled. -{% endnote %} {% endif %} +{% endnote %} +{% endif %} -## 重定向 URL +## Redirect URLs -`redirect_uri` 参数是可选的。 如果忽略该参数,GitHub 会将用户重定向到 OAuth 应用程序设置中配置的回叫 URL。 如果提供该参数,重定向 URL 的主机和端口必须与回叫 URL 完全匹配。 重定向 URL 的路径必须引用回叫 URL 的子目录。 +The `redirect_uri` parameter is optional. If left out, GitHub will +redirect users to the callback URL configured in the OAuth Application +settings. If provided, the redirect URL's host (excluding sub-domains) and port must exactly +match the callback URL. The redirect URL's path must reference a +subdirectory of the callback URL. CALLBACK: http://example.com/path GOOD: http://example.com/path GOOD: http://example.com/path/subdir/other + GOOD: http://oauth.example.com/path + GOOD: http://oauth.example.com/path/subdir/other BAD: http://example.com/bar BAD: http://example.com/ BAD: http://example.com:8080/path BAD: http://oauth.example.com:8080/path BAD: http://example.org -### 本地主机重定向 URL +### Loopback redirect urls -可选 `redirect_uri` 参数还可用于本地主机 URL。 如果应用程序指定 URL 和端口,授权后,应用程序用户将被重定向到提供的 URL 和端口。 `redirect_uri` 不需要与应用的回叫 URL 中指定的端口匹配。 +The optional `redirect_uri` parameter can also be used for loopback URLs. If the application specifies a loopback URL and a port, then after authorizing the application users will be redirected to the provided URL and port. The `redirect_uri` does not need to match the port specified in the callback URL for the app. -对于 `http://127.0.0.1/path` 回叫 URL,可以使用以下 `redirect_uri`: +For the `http://127.0.0.1/path` callback URL, you can use this `redirect_uri`: ``` http://127.0.0.1:1234/path ``` -## 为 OAuth 应用程序创建多个令牌 +Note that OAuth RFC [recommends not to use `localhost`](https://datatracker.ietf.org/doc/html/rfc8252#section-7.3), but instead to use loopback literal `127.0.0.1` or IPv6 `::1`. -您可以为用户/应用程序/作用域组合创建多个令牌,以便为特定用例创建令牌。 +## Creating multiple tokens for OAuth Apps -如果您的 OAuth 应用程序支持一个使用 GitHub 登录且只需基本用户信息的工作流程,此方法将非常有用。 另一个工作流程可能需要访问用户的私有仓库。 您的 OAuth 应用程序可以使用多个令牌为每个用例执行 web 流程,只需要所需的作用域。 如果用户仅使用您的应用程序登录,则无需向他们的私有仓库授予您的 OAuth 应用程序访问权限。 +You can create multiple tokens for a user/application/scope combination to create tokens for specific use cases. + +This is useful if your OAuth App supports one workflow that uses GitHub for sign-in and only requires basic user information. Another workflow may require access to a user's private repositories. Using multiple tokens, your OAuth App can perform the web flow for each use case, requesting only the scopes needed. If a user only uses your application to sign in, they are never required to grant your OAuth App access to their private repositories. {% data reusables.apps.oauth-token-limit %} {% data reusables.apps.deletes_ssh_keys %} -## 指示用户审查其访问权限 +## Directing users to review their access -您可以链接至 OAuth 应用程序的授权信息,以便用户审查和撤销其应用程序授权。 +You can link to authorization information for an OAuth App so that users can review and revoke their application authorizations. -若要生成此链接,需要使用在注册应用程序时从 GitHub 收到的 OAuth 应用 `client_id`。 +To build this link, you'll need your OAuth Apps `client_id` that you received from GitHub when you registered the application. ``` {% data variables.product.oauth_host_code %}/settings/connections/applications/:client_id @@ -327,17 +333,17 @@ http://127.0.0.1:1234/path {% tip %} -提示:若要详细了解 OAuth 应用可以为用户访问的资源,请参阅“[为用户发现资源](/rest/guides/discovering-resources-for-a-user)”。 +**Tip:** To learn more about the resources that your OAuth App can access for a user, see "[Discovering resources for a user](/rest/guides/discovering-resources-for-a-user)." {% endtip %} -## 故障排除 +## Troubleshooting -* “[排查授权请求错误](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)” -* “[排查 OAuth 应用访问令牌请求错误](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)” -* “[设备流错误](#error-codes-for-the-device-flow)”{% ifversion fpt or ghae or ghes > 3.2 or ghec %} -* “[令牌过期和吊销](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)”{% endif %} +* "[Troubleshooting authorization request errors](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)" +* "[Troubleshooting OAuth App access token request errors](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)" +* "[Device flow errors](#error-codes-for-the-device-flow)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %} +* "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} -## 延伸阅读 +## Further reading -- “[关于对 {% data variables.product.prodname_dotcom %} 进行身份验证](/github/authenticating-to-github/about-authentication-to-github)” +- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)" diff --git a/translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md b/translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md index 380cdadf6d..cca12402c8 100644 --- a/translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md +++ b/translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md @@ -1,5 +1,5 @@ --- -title: OAuth 应用程序的作用域 +title: Scopes for OAuth Apps intro: '{% data reusables.shortdesc.understanding_scopes_for_oauth_apps %}' redirect_from: - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps @@ -13,24 +13,18 @@ versions: ghec: '*' topics: - OAuth Apps -ms.openlocfilehash: e7d943c95dc3d8fea6e025cbae8c5b65f9ccf864 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717939' --- -在 GitHub 上设置 OAuth 应用程序时,请求的作用域会在授权表单上显示给用户。 +When setting up an OAuth App on GitHub, requested scopes are displayed to the user on the authorization form. {% note %} -注意:如果你在构建 GitHub 应用,则不需要在授权请求中提供范围。 有关详细信息,请参阅“[标识和授权 GitHub 应用用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。 +**Note:** If you're building a GitHub App, you don’t need to provide scopes in your authorization request. For more on this, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." {% endnote %} -如果 {% data variables.product.prodname_oauth_app %} 无法访问浏览器(如 CLI 工具),则无需为用户指定向应用程序验证的作用域。 有关详细信息,请参阅“[授权 OAuth 应用](/developers/apps/authorizing-oauth-apps#device-flow)”。 +If your {% data variables.product.prodname_oauth_app %} doesn't have access to a browser, such as a CLI tool, then you don't need to specify a scope for users to authenticate to your app. For more information, see "[Authorizing OAuth apps](/developers/apps/authorizing-oauth-apps#device-flow)." -检查标头以查看您拥有哪些 OAuth 作用域,以及 API 操作接受什么: +Check headers to see what OAuth scopes you have, and what the API action accepts: ```shell $ curl -H "Authorization: Bearer OAUTH-TOKEN" {% data variables.product.api_url_pre %}/users/codertocat -I @@ -39,40 +33,58 @@ X-OAuth-Scopes: repo, user X-Accepted-OAuth-Scopes: user ``` -* `X-OAuth-Scopes` 列出令牌已授权的范围。 -* `X-Accepted-OAuth-Scopes` 列出操作检查的范围。 +* `X-OAuth-Scopes` lists the scopes your token has authorized. +* `X-Accepted-OAuth-Scopes` lists the scopes that the action checks for. -## 可用的范围 +## Available scopes -名称 | 说明 -----|-----------|{% ifversion not ghae %} **`(no scope)`** | 授予对公共信息(包括用户个人资料信息、存储库信息和 Gist)的只读访问权限{% endif %}{% ifversion ghes or ghae %} **`site_admin`** | 向站点管理员授予对 [{% data variables.product.prodname_ghe_server %} 管理 API 终结点](/rest/reference/enterprise-admin)的访问权限。{% endif %} **`repo`** | 授予对公共{% ifversion ghec or ghes or ghae %}、内部{% endif %}和专用存储库的完全访问权限,包括对代码、提交状态、存储库邀请、协作者、部署状态和存储库 Webhook 的读写权限。 注意:除了存储库相关资源外,`repo` 范围还授予对组织拥有的资源(包括项目、邀请、团队成员身份和 Webhook)的管理权限。 此范围还授予对用户所拥有的项目的管理权限。 - `repo:status`| 授予对{% ifversion fpt %}公共和专用{% elsif ghec or ghes %}公共、专用和内部{% elsif ghae %}专用和内部{% endif %}存储库中的提交状态的读/写访问权限。 仅在授予其他用户或服务对专用存储库提交状态的访问权限而不授予对代码的访问权限时,才需要此范围。 - `repo_deployment`| 授予对 {% ifversion not ghae %}公共{% else %}内部{% endif %}和专用存储库的[部署状态](/rest/reference/repos#deployments)的访问权限。 仅在授予其他用户或服务对部署状态的访问权限而不授予对代码的访问权限时,才需要此范围。{% ifversion not ghae %}  `public_repo`| 将访问权限限制为公共存储库。 这包括对公共仓库和组织的代码、提交状态、仓库项目、协作者以及部署状态的读取/写入权限。 对公共存储库标星也需要此权限。{% endif %}  `repo:invite` | 授予接受/拒绝存储库协作邀请的权限。 仅在授予其他用户或服务对邀请的访问权限而不授予对代码的访问权限时,才需要此范围。{% ifversion fpt or ghes or ghec %}  `security_events` | 授予:
对 [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning) {%- ifversion ghec %} 中安全事件的读取和写入权限
对 [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning){%- endif %} 中安全事件的读取和写入权限
仅在授予其他用户或服务对安全事件的访问权限而不授予对代码的访问权限时,才需要此范围。{% endif %} **`admin:repo_hook`** | 授予对{% ifversion fpt %}公共或专用{% elsif ghec or ghes %}公共、专用或内部{% elsif ghae %}专用或内部{% endif %}存储库中存储库挂钩的读取、写入、ping 和删除访问权限。 `repo` {% ifversion fpt or ghec or ghes %}和 `public_repo` 范围授予{% else %}范围授予{% endif %}对存储库(包括存储库挂钩)的完全访问权限。 使用 `admin:repo_hook` 范围将访问权限限制为仅存储库挂钩。 - `write:repo_hook` | 授予对{% ifversion fpt %}公共或专用{% elsif ghec or ghes %}公共、专用或内部{% elsif ghae %}专用或内部{% endif %}存储库中挂钩的读取、写入和 ping 访问权限。 - `read:repo_hook`| 授予对{% ifversion fpt %}公共或专用{% elsif ghec or ghes %}公共、专用或内部{% elsif ghae %}专用或内部{% endif %}存储库中挂钩的读取和 ping 访问权限。 -**`admin:org`** | 全面管理组织及其团队、项目和成员。 - `write:org`| 对组织成员身份、组织项目和团队成员身份的读取和写入权限。 - `read:org`| 对组织成员身份、组织项目和团队成员身份的只读权限。 -**`admin:public_key`** | 全面管理公钥。 - `write:public_key`| 创建、列出和查看公钥的详细信息。 - `read:public_key`| 列出和查看公钥的详细信息。 -**`admin:org_hook`** | 授予对组织挂钩的读取、写入、ping 和删除权限。 注意:OAuth 令牌只能对由 OAuth 应用创建的组织挂钩执行这些操作。 个人访问令牌只能对用户创建的组织挂钩执行这些操作。 -**`gist`** | 授予对 Gist 的写入权限。 -**`notifications`** | 授予:
* 对用户的通知的读取访问权限
* 对线程的“标记为读取”访问权限
* 对存储库的监视和取消监视访问权限,以及
* 对线程订阅的读取、写入和删除访问权限。 -**`user`** | 仅授予对个人资料的读取/写入权限。 请注意,此范围包括 `user:email` 和 `user:follow`。 - `read:user`| 授予读取用户个人资料数据的权限。 - `user:email`| 授予对用户电子邮件地址的读取权限。 - `user:follow`| 授予关注或取消关注其他用户的权限。{% ifversion projects-oauth-scope %} **`project`** | 授予对用户和组织 {% data variables.projects.projects_v2 %} 的读/写访问权限。 - `read:project`| 授予对用户和组织 {% data variables.projects.projects_v2 %} 的只读访问权限。{% endif %} **`delete_repo`** | 授予删除可管理存储库的权限。 -**`write:discussion`** | 授予对团队讨论的读取和写入权限。 - `read:discussion` | 授予对团队讨论的读取权限。 -**`write:packages`** | 授予在 {% data variables.product.prodname_registry %} 中上传或发布包的权限。 有关详细信息,请参阅“[发布包](/github/managing-packages-with-github-packages/publishing-a-package)”。 -**`read:packages`** | 授予从 {% data variables.product.prodname_registry %} 下载或安装包的权限。 有关详细信息,请参阅“[安装包](/github/managing-packages-with-github-packages/installing-a-package)”。 -**`delete:packages`** | 授予从 {% data variables.product.prodname_registry %} 删除包的权限。 有关详细信息,请参阅“[删除和还原包](/packages/learn-github-packages/deleting-and-restoring-a-package)”。 -**`admin:gpg_key`** | 全面管理 GPG 密钥。 - `write:gpg_key`| 创建、列出和查看 GPG 密钥的详细信息。 - `read:gpg_key`| 列出和查看 GPG 密钥的详细信息。{% ifversion fpt or ghec %} **`codespace`** | 授予创建和管理 codespace 的权限。 Codespaces 可以暴露可能有不同范围集的 GITHUB_TOKEN。 有关详细信息,请参阅“[{% data variables.product.prodname_github_codespaces %} 中的安全性](/codespaces/codespaces-reference/security-in-github-codespaces#authentication)”。{% endif %} **`workflow`** | 授予添加和更新 {% data variables.product.prodname_actions %} 工作流文件的权限。 如果在同一仓库中的另一个分支上存在相同的文件(具有相同的路径和内容),则工作流程文件可以在没有此作用域的情况下提交。 工作流文件可以公开可能有不同范围集的 `GITHUB_TOKEN`。 有关详细信息,请参阅“[工作流中的身份验证](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)”。{% ifversion not fpt %} `admin:enterprise` | 完全掌控企业功能。 有关详细信息,请参阅 GraphQL API 文档中的“[管理企业帐户](/graphql/guides/managing-enterprise-accounts)”。

包括 `manage_runners:enterprise`{% ifversion ghec or ghes > 3.3 %}、`manage_billing:enterprise`、{% endif %} 和 `read:enterprise`。  `manage_runners:enterprise` | 完全掌控企业内部的自承载运行程序。 有关详细信息,请参阅[关于自承载运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)。 {% ifversion ghec or ghes > 3.3 %}  `manage_billing:enterprise` | 读取和写入企业账单数据。 有关详细信息,请参阅 REST API 文档中的“[账单](/rest/billing)”。 {% endif %}  `read:enterprise` | 读取企业资料中的所有数据。 不包括企业成员或组织的个人资料数据。{% endif %} {% note %} +Name | Description +-----|-----------|{% ifversion not ghae %} +**`(no scope)`** | Grants read-only access to public information (including user profile info, repository info, and gists){% endif %}{% ifversion ghes or ghae %} +**`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/rest/reference/enterprise-admin).{% endif %} +**`repo`** | Grants full access to public{% ifversion ghec or ghes or ghae %}, internal,{% endif %} and private repositories including read and write access to code, commit statuses, repository invitations, collaborators, deployment statuses, and repository webhooks. **Note**: In addition to repository related resources, the `repo` scope also grants access to manage organization-owned resources including projects, invitations, team memberships and webhooks. This scope also grants the ability to manage projects owned by users. + `repo:status`| Grants read/write access to commit statuses in {% ifversion fpt %}public and private{% elsif ghec or ghes %}public, private, and internal{% elsif ghae %}private and internal{% endif %} repositories. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code. + `repo_deployment`| Grants access to [deployment statuses](/rest/reference/repos#deployments) for {% ifversion not ghae %}public{% else %}internal{% endif %} and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code.{% ifversion not ghae %} + `public_repo`| Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories.{% endif %} + `repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% ifversion fpt or ghes or ghec %} + `security_events` | Grants:
read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning) {%- ifversion ghec %}
read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning){%- endif %}
This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %} +**`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories. The `repo` {% ifversion fpt or ghec or ghes %}and `public_repo` scopes grant{% else %}scope grants{% endif %} full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks. + `write:repo_hook` | Grants read, write, and ping access to hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories. + `read:repo_hook`| Grants read and ping access to hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories. +**`admin:org`** | Fully manage the organization and its teams, projects, and memberships. + `write:org`| Read and write access to organization membership, organization projects, and team membership. + `read:org`| Read-only access to organization membership, organization projects, and team membership. +**`admin:public_key`** | Fully manage public keys. + `write:public_key`| Create, list, and view details for public keys. + `read:public_key`| List and view details for public keys. +**`admin:org_hook`** | Grants read, write, ping, and delete access to organization hooks. **Note:** OAuth tokens will only be able to perform these actions on organization hooks which were created by the OAuth App. {% data variables.product.pat_generic_caps %}s will only be able to perform these actions on organization hooks created by a user. +**`gist`** | Grants write access to gists. +**`notifications`** | Grants:
* read access to a user's notifications
* mark as read access to threads
* watch and unwatch access to a repository, and
* read, write, and delete access to thread subscriptions. +**`user`** | Grants read/write access to profile info only. Note that this scope includes `user:email` and `user:follow`. + `read:user`| Grants access to read a user's profile data. + `user:email`| Grants read access to a user's email addresses. + `user:follow`| Grants access to follow or unfollow other users.{% ifversion projects-oauth-scope %} +**`project`** | Grants read/write access to user and organization {% data variables.projects.projects_v2 %}. + `read:project`| Grants read only access to user and organization {% data variables.projects.projects_v2 %}.{% endif %} +**`delete_repo`** | Grants access to delete adminable repositories. +**`write:discussion`** | Allows read and write access for team discussions. + `read:discussion` | Allows read access for team discussions. +**`write:packages`** | Grants access to upload or publish a package in {% data variables.product.prodname_registry %}. For more information, see "[Publishing a package](/github/managing-packages-with-github-packages/publishing-a-package)". +**`read:packages`** | Grants access to download or install packages from {% data variables.product.prodname_registry %}. For more information, see "[Installing a package](/github/managing-packages-with-github-packages/installing-a-package)". +**`delete:packages`** | Grants access to delete packages from {% data variables.product.prodname_registry %}. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." +**`admin:gpg_key`** | Fully manage GPG keys. + `write:gpg_key`| Create, list, and view details for GPG keys. + `read:gpg_key`| List and view details for GPG keys.{% ifversion fpt or ghec %} +**`codespace`** | Grants the ability to create and manage codespaces. Codespaces can expose a GITHUB_TOKEN which may have a different set of scopes. For more information, see "[Security in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/security-in-github-codespaces#authentication)."{% endif %} +**`workflow`** | Grants the ability to add and update {% data variables.product.prodname_actions %} workflow files. Workflow files can be committed without this scope if the same file (with both the same path and contents) exists on another branch in the same repository. Workflow files can expose `GITHUB_TOKEN` which may have a different set of scopes. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."{% ifversion not fpt %} +**`admin:enterprise`** | Gives full control of enterprise functionality. For more information, see "[Managing enterprise accounts](/graphql/guides/managing-enterprise-accounts)" in the GraphQL API documentation.

Includes `manage_runners:enterprise`{% ifversion ghec or ghes > 3.3 %}, `manage_billing:enterprise`,{% endif %} and `read:enterprise`. + `manage_runners:enterprise` | Gives full control over self-hosted runners within the enterprise. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." {% ifversion ghec or ghes > 3.3 %} + `manage_billing:enterprise` | Read and write enterprise billing data. For more information, see "[Billing](/rest/billing)" in the REST API documentation. {% endif %} + `read:enterprise` | Read all data on an enterprise profile. Does not include profile data of enterprise members or organizations.{% endif %} +{% note %} -注意:OAuth 应用可以在初始重定向中请求范围。 可使用 `%20` 以空格分隔多个范围来指定它们: +**Note:** Your OAuth App can request the scopes in the initial redirection. You +can specify multiple scopes by separating them with a space using `%20`: https://github.com/login/oauth/authorize? client_id=...& @@ -80,18 +92,31 @@ X-Accepted-OAuth-Scopes: user {% endnote %} -## 请求的作用域和授予的作用域 +## Requested scopes and granted scopes -`scope` 属性列出了附加到用户授予的令牌的范围。 通常,这些作用域与您请求的作用域相同。 -但是,用户可以编辑其范围,实际授予应用程序更少的权限(相比你最初请求的权限)。 此外,用户还可以在 OAuth 流程完成后编辑令牌范围。 -你应该意识到这种可能性,并相应地调整应用程序的行为。 +The `scope` attribute lists scopes attached to the token that were granted by +the user. Normally, these scopes will be identical to what you requested. +However, users can edit their scopes, effectively +granting your application less access than you originally requested. Also, users +can edit token scopes after the OAuth flow is completed. +You should be aware of this possibility and adjust your application's behavior +accordingly. -如果用户选择授予更少的权限(相比你最初请求的权限),妥善处理这种错误情况非常重要。 例如,应用程序可以警告或以其他方式告诉用户,他们可用的功能会减少或者无法执行某些操作。 +It's important to handle error cases where a user chooses to grant you +less access than you originally requested. For example, applications can warn +or otherwise communicate with their users that they will see reduced +functionality or be unable to perform some actions. -此外,应用程序总是可以将用户送回流程以获取更多权限,但不要忘记,用户总是可以说不。 +Also, applications can always send users back through the flow again to get +additional permission, but don’t forget that users can always say no. -请查看[身份验证基础知识指南](/guides/basics-of-authentication/),其中提供了有关处理可修改令牌范围的提示。 +Check out the [Basics of Authentication guide](/guides/basics-of-authentication/), which +provides tips on handling modifiable token scopes. -## 标准化作用域 +## Normalized scopes -请求多个范围时,将用标准化的范围列表保存令牌,而放弃其他请求的范围隐式包含的那些范围。 例如,请求 `user,gist,user:email` 将生成仅具有 `user` 和 `gist` 范围的令牌,因为使用 `user:email` 范围授予的权限包含在 `user` 范围中。 +When requesting multiple scopes, the token is saved with a normalized list +of scopes, discarding those that are implicitly included by another requested +scope. For example, requesting `user,gist,user:email` will result in a +token with `user` and `gist` scopes only since the access granted with +`user:email` scope is included in the `user` scope. diff --git a/translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md b/translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md index 0e14ac3fdc..166ace7868 100644 --- a/translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md +++ b/translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md @@ -1,6 +1,6 @@ --- -title: 关于应用程序 -intro: '你可以构建与 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 的集成来增加灵活性并减少自己工作流程中的摩擦。{% ifversion fpt or ghec %} 你也可以与 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) 上的其他 API 集成。{% endif %}' +title: About apps +intro: 'You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs to add flexibility and reduce friction in your own workflow.{% ifversion fpt or ghec %} You can also share integrations with others on [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).{% endif %}' redirect_from: - /apps/building-integrationssetting-up-a-new-integration - /apps/building-integrations @@ -14,98 +14,93 @@ versions: ghec: '*' topics: - GitHub Apps -ms.openlocfilehash: 9f8c392906f494b41aaa216ef5f6b58f7968f32a -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145085040' --- -{% data variables.product.prodname_dotcom %} 上的应用程序允许您自动化并改进工作流程。 可以生成应用来改进工作流。{% ifversion fpt or ghec %}也可以在 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) 中分享或销售应用。 若要了解如何在 {% data variables.product.prodname_marketplace %} 中上架应用,请参阅“[GitHub 市场入门](/marketplace/getting-started/)”。{% endif %} +Apps on {% data variables.product.prodname_dotcom %} allow you to automate and improve your workflow. You can build apps to improve your workflow.{% ifversion fpt or ghec %} You can also share or sell apps in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). To learn how to list an app on {% data variables.product.prodname_marketplace %}, see "[Getting started with GitHub Marketplace](/marketplace/getting-started/)."{% endif %} -{% data reusables.marketplace.github_apps_preferred %},但 GitHub 支持 {% data variables.product.prodname_oauth_apps %} 和 {% data variables.product.prodname_github_apps %}。 有关选择应用类型的信息,请参阅“[GitHub 应用与 OAuth 应用的区别](/developers/apps/differences-between-github-apps-and-oauth-apps)”。 +{% data reusables.marketplace.github_apps_preferred %}, but GitHub supports both {% data variables.product.prodname_oauth_apps %} and {% data variables.product.prodname_github_apps %}. For information on choosing a type of app, see "[Differences between GitHub Apps and OAuth Apps](/developers/apps/differences-between-github-apps-and-oauth-apps)." {% data reusables.apps.general-apps-restrictions %} -有关生成 {% data variables.product.prodname_github_app %} 的过程演练,请参阅“[生成第一个 {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)”。 +For a walkthrough of the process of building a {% data variables.product.prodname_github_app %}, see "[Building Your First {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)." -## 关于 {% data variables.product.prodname_github_apps %} +## About {% data variables.product.prodname_github_apps %} -{% data variables.product.prodname_github_apps %} 是 GitHub 中的一流产品。 {% data variables.product.prodname_github_app %} 应用程序以自己的名义运行,通过 API 直接使用自己的身份进行操作,这意味着您无需作为独立用户维护自动程序或服务帐户。 +{% data variables.product.prodname_github_apps %} are first-class actors within GitHub. A {% data variables.product.prodname_github_app %} acts on its own behalf, taking actions via the API directly using its own identity, which means you don't need to maintain a bot or service account as a separate user. -{% data variables.product.prodname_github_apps %} 可以直接安装在组织和个人帐户上,并获得对特定仓库的访问权限。 它们拥有内置 web 挂钩和狭窄的特定权限。 设置 {% data variables.product.prodname_github_app %}时,可以选择希望它访问的仓库。 例如,可以设置一个名为在存储库中`MyGitHub`写入问题且`octocat`仅 _写入_ 存储库的应用`octocat`。 要安装 {% data variables.product.prodname_github_app %},您必须是组织所有者或在仓库中具有管理员权限。 +{% data variables.product.prodname_github_apps %} can be installed directly on organizations and personal accounts and granted access to specific repositories. They come with built-in webhooks and narrow, specific permissions. When you set up your {% data variables.product.prodname_github_app %}, you can select the repositories you want it to access. For example, you can set up an app called `MyGitHub` that writes issues in the `octocat` repository and _only_ the `octocat` repository. To install a {% data variables.product.prodname_github_app %}, you must be an organization owner or have admin permissions in a repository. {% data reusables.apps.app_manager_role %} -{% data variables.product.prodname_github_apps %} 是需要托管在某处的应用程序。 有关涵盖服务器和托管的分步说明,请参阅“[生成第一个 {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)”。 +{% data variables.product.prodname_github_apps %} are applications that need to be hosted somewhere. For step-by-step instructions that cover servers and hosting, see "[Building Your First {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)." -要改进自己的工作流程,可以创建一个包含多个脚本或整个应用程序的 {% data variables.product.prodname_github_app %},然后将此应用程序连接至许多其他工具。 例如,您可以将 {% data variables.product.prodname_github_apps %} 连接至 GitHub、Slack、自己可能拥有的其他内部应用程序、电子邮件程序或其他 API。 +To improve your workflow, you can create a {% data variables.product.prodname_github_app %} that contains multiple scripts or an entire application, and then connect that app to many other tools. For example, you can connect {% data variables.product.prodname_github_apps %} to GitHub, Slack, other in-house apps you may have, email programs, or other APIs. -创建 {% data variables.product.prodname_github_apps %} 时,请记住以下方法: +Keep these ideas in mind when creating {% data variables.product.prodname_github_apps %}: {% ifversion fpt or ghec %} * {% data reusables.apps.maximum-github-apps-allowed %} {% endif %} -* {% data variables.product.prodname_github_app %} 的操作应独立于用户(除非此应用使用[用户到服务器](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests)令牌)。 {% data reusables.apps.expiring_user_authorization_tokens %} +* A {% data variables.product.prodname_github_app %} should take actions independent of a user (unless the app is using a [user-to-server](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests) token). {% data reusables.apps.expiring_user_authorization_tokens %} -* 请确保 {% data variables.product.prodname_github_app %} 与特定仓库集成。 -* {% data variables.product.prodname_github_app %} 应该连接到个人帐户或组织。 -* 不要指望 {% data variables.product.prodname_github_app %} 知道并尽其所能。 -* 如果您只需要“使用GitHub登录”服务,请不要使用 {% data variables.product.prodname_github_app %}。 但是 {% data variables.product.prodname_github_app %} 可以使用[用户标识流](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)让用户登录和执行其他操作。 -* 如果只想充当 GitHub 用户并执行用户所能执行的所有操作,请不要生成 {% data variables.product.prodname_github_app %}。{% ifversion fpt or ghec %} +* Make sure the {% data variables.product.prodname_github_app %} integrates with specific repositories. +* The {% data variables.product.prodname_github_app %} should connect to a personal account or an organization. +* Don't expect the {% data variables.product.prodname_github_app %} to know and do everything a user can. +* Don't use a {% data variables.product.prodname_github_app %} if you just need a "Login with GitHub" service. But a {% data variables.product.prodname_github_app %} can use a [user identification flow](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) to log users in _and_ do other things. +* Don't build a {% data variables.product.prodname_github_app %} if you _only_ want to act as a GitHub user and do everything that user can do.{% ifversion fpt or ghec %} * {% data reusables.apps.general-apps-restrictions %}{% endif %} -若要开始开发 {% data variables.product.prodname_github_apps %},请从“[创建 {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/)”开始。{% ifversion fpt or ghec %}若要了解如何使用 {% data variables.product.prodname_github_app %} 清单创建预配置的 {% data variables.product.prodname_github_apps %},请参阅“[从清单创建 {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/creating-github-apps-from-a-manifest/)”。{% endif %} +To begin developing {% data variables.product.prodname_github_apps %}, start with "[Creating a {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/)."{% ifversion fpt or ghec %} To learn how to use {% data variables.product.prodname_github_app %} Manifests, which allow people to create preconfigured {% data variables.product.prodname_github_apps %}, see "[Creating {% data variables.product.prodname_github_apps %} from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)."{% endif %} -## 关于 {% data variables.product.prodname_oauth_apps %} +## About {% data variables.product.prodname_oauth_apps %} -OAuth2 是一种协议,它允许外部应用程序请求授权在不使用密码的情况下访问用户 {% data variables.product.prodname_dotcom %} 帐户中的私有信息。 此协议优先于基本验证,因为令牌可能仅限于特定类型的数据,用户可以随时撤销。 +OAuth2 is a protocol that lets external applications request authorization to private details in a user's {% data variables.product.prodname_dotcom %} account without accessing their password. This is preferred over Basic Authentication because tokens can be limited to specific types of data and can be revoked by users at any time. {% data reusables.apps.deletes_ssh_keys %} -{% data variables.product.prodname_oauth_app %} 使用 {% data variables.product.prodname_dotcom %} 作为身份提供程序以验证为授予应用程序访问权限的用户。 这意味着,当用户授予 {% data variables.product.prodname_oauth_app %} 访问权限时,将授权访问其帐户有权访问的所有存储库,以及他们所属的、未阻止第三方访问的任何组织。 +An {% data variables.product.prodname_oauth_app %} uses {% data variables.product.prodname_dotcom %} as an identity provider to authenticate as the user who grants access to the app. This means when a user grants an {% data variables.product.prodname_oauth_app %} access, they grant permissions to _all_ repositories they have access to in their account, and also to any organizations they belong to that haven't blocked third-party access. -如果要创建比简单脚本的处理范围更复杂的流程,构建 {% data variables.product.prodname_oauth_app %} 是一个很好的选择。 请注意,{% data variables.product.prodname_oauth_apps %} 是需要托管在某处的应用程序。 +Building an {% data variables.product.prodname_oauth_app %} is a good option if you are creating more complex processes than a simple script can handle. Note that {% data variables.product.prodname_oauth_apps %} are applications that need to be hosted somewhere. -创建 {% data variables.product.prodname_oauth_apps %} 时,请记住以下几点: +Keep these ideas in mind when creating {% data variables.product.prodname_oauth_apps %}: {% ifversion fpt or ghec %} * {% data reusables.apps.maximum-oauth-apps-allowed %} {% endif %} -* {% data variables.product.prodname_oauth_app %} 在所有 {% data variables.product.prodname_dotcom %} 中(例如,在提供用户通知时)应始终代表经身份验证的 {% data variables.product.prodname_dotcom %} 用户。 -* 通过为经身份验证的用户启用“使用 {% data variables.product.prodname_dotcom %} 进行登录”,{% data variables.product.prodname_oauth_app %} 可用作身份提供程序。 -* 如果您希望应用程序作用于单个仓库,请不要构建 {% data variables.product.prodname_oauth_app %}。 使用 `repo` OAuth 作用域,{% data variables.product.prodname_oauth_apps %} 可以作用于经身份验证用户的所有存储库。 -* 不要构建 {% data variables.product.prodname_oauth_app %} 作为团队或公司的应用程序。 {% data variables.product.prodname_oauth_apps %} 将验证为单个用户,因此,如果有人创建了 {% data variables.product.prodname_oauth_app %} 供公司使用,那么一旦他们离开公司,其他人将无法访问它。{% ifversion fpt or ghec %} +* An {% data variables.product.prodname_oauth_app %} should always act as the authenticated {% data variables.product.prodname_dotcom %} user across all of {% data variables.product.prodname_dotcom %} (for example, when providing user notifications). +* An {% data variables.product.prodname_oauth_app %} can be used as an identity provider by enabling a "Login with {% data variables.product.prodname_dotcom %}" for the authenticated user. +* Don't build an {% data variables.product.prodname_oauth_app %} if you want your application to act on a single repository. With the `repo` OAuth scope, {% data variables.product.prodname_oauth_apps %} can act on _all_ of the authenticated user's repositories. +* Don't build an {% data variables.product.prodname_oauth_app %} to act as an application for your team or company. {% data variables.product.prodname_oauth_apps %} authenticate as a single user, so if one person creates an {% data variables.product.prodname_oauth_app %} for a company to use, and then they leave the company, no one else will have access to it.{% ifversion fpt or ghec %} * {% data reusables.apps.oauth-apps-restrictions %}{% endif %} -有关 {% data variables.product.prodname_oauth_apps %} 的详细信息,请参阅“[创建 {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)”和“[注册应用](/rest/guides/basics-of-authentication#registering-your-app)”。 +For more on {% data variables.product.prodname_oauth_apps %}, see "[Creating an {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" and "[Registering your app](/rest/guides/basics-of-authentication#registering-your-app)." -## 个人访问令牌 +## {% data variables.product.pat_generic_caps %}s -[个人访问令牌](/articles/creating-a-personal-access-token-for-the-command-line/)是一个字符串,其功能类似于 [OAuth 令牌](/apps/building-oauth-apps/authorizing-oauth-apps/),可以通过[作用域](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)指定其权限。 个人访问令牌还与密码类似,但您能拥有很多令牌,而且可以随时撤销对每个令牌的访问权限。 +A [{% data variables.product.pat_generic %}](/articles/creating-a-personal-access-token-for-the-command-line/) is a string of characters that functions similarly to an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/) in that you can specify its permissions via [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). A {% data variables.product.pat_generic %} is also similar to a password, but you can have many of them and you can revoke access to each one at any time. -例如,您可以启用个人访问令牌,以写入仓库。 如果随后运行 cURL 命令或编写在存储库中[创建问题](/rest/reference/issues#create-an-issue)的脚本,则需要传递个人访问令牌以进行身份验证。 您可以将个人访问令牌存储为环境变量,以免每次使用时都要输入。 +As an example, you can enable a {% data variables.product.pat_generic %} to write to your repositories. If then you run a cURL command or write a script that [creates an issue](/rest/reference/issues#create-an-issue) in your repository, you would pass the {% data variables.product.pat_generic %} to authenticate. You can store the {% data variables.product.pat_generic %} as an environment variable to avoid typing it every time you use it. -使用个人访问令牌时,请牢记以下几点: +Keep these ideas in mind when using {% data variables.product.pat_generic %}s: -* 记得只能用此令牌代表您自己。 -* 您可以执行一次性 cURL 请求。 -* 您可以运行个人脚本。 -* 不要为整个团队或公司设置脚本。 -* 不要设置共享个人帐户来充当机器人用户。{% ifversion fpt or ghes > 3.2 or ghae or ghec %} -* 请为您的个人访问令牌设置期限,以帮助保护您的信息安全。{% endif %} +* Remember to use this token to represent yourself only. +* You can perform one-off cURL requests. +* You can run personal scripts. +* Don't set up a script for your whole team or company to use. +* Don't set up a shared personal account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae or ghec %} +* Grant your token the minimal privileges it needs. +* Set an expiration for your {% data variables.product.pat_generic %}s, to help keep your information secure.{% endif %} -## 确定要构建的集成 +## Determining which integration to build -在开始创建集成之前,您需要确定使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 访问、验证和交互的最佳方式。 下图提供了一些问题,您在决定是否对集成使用个人访问令牌、{% data variables.product.prodname_github_apps %} 或 {% data variables.product.prodname_oauth_apps %} 时可以考虑这些问题。 +Before you get started creating integrations, you need to determine the best way to access, authenticate, and interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs. The following image offers some questions to ask yourself when deciding whether to use {% data variables.product.pat_generic %}s, {% data variables.product.prodname_github_apps %}, or {% data variables.product.prodname_oauth_apps %} for your integration. -![应用程序问题流程简介](/assets/images/intro-to-apps-flow.png) +![Intro to apps question flow](/assets/images/intro-to-apps-flow.png) -请考虑关于您的集成需要如何操作及它需要访问什么等问题: +Consider these questions about how your integration needs to behave and what it needs to access: -* 我的集成是只像我一样,还是更像一个应用程序? -* 我是否希望它作为单独的实体独立于我运行? -* 它是否能访问我可以访问的一切,或者说我想限制它的访问权限? -* 它是简单还是复杂? 例如,个人访问令牌对简单的脚本和 cURL 有益,而 {% data variables.product.prodname_oauth_app %} 可以处理更复杂的脚本。 +* Will my integration act only as me, or will it act more like an application? +* Do I want it to act independently of me as its own entity? +* Will it access everything that I can access, or do I want to limit its access? +* Is it simple or complex? For example, {% data variables.product.pat_generic %}s are good for simple scripts and cURLs, whereas an {% data variables.product.prodname_oauth_app %} can handle more complex scripting. -## 请求支持 +## Requesting support {% data reusables.support.help_resources %} diff --git a/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md b/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md index 320f402a94..6653241592 100644 --- a/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md +++ b/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md @@ -1,6 +1,6 @@ --- -title: 上架应用程序的要求 -intro: '{% data variables.product.prodname_marketplace %} 上的应用程序必须满足本页列出的要求才能发布上架。' +title: Requirements for listing an app +intro: 'Apps on {% data variables.product.prodname_marketplace %} must meet the requirements outlined on this page before the listing can be published.' redirect_from: - /apps/adding-integrations/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace - /apps/marketplace/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace @@ -15,72 +15,66 @@ versions: topics: - Marketplace shortTitle: Listing requirements -ms.openlocfilehash: 58112d935a77119325dab4ad72c87561d0c00e47 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145084989' --- -在 {% data variables.product.prodname_marketplace %} 中上架应用程序的要求取决于您是要提供免费应用程序还是付费应用程序。 +The requirements for listing an app on {% data variables.product.prodname_marketplace %} vary according to whether you want to offer a free or a paid app. -## 对所有 {% data variables.product.prodname_marketplace %} 上架产品的要求 +## Requirements for all {% data variables.product.prodname_marketplace %} listings -{% data variables.product.prodname_marketplace %} 中的所有上架产品应该是能够为 {% data variables.product.product_name %} 社区提供价值的工具。 提交要发布的上架信息时,必须阅读并接受“[{% data variables.product.prodname_marketplace %} 开发人员协议](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)”的条款。 +All listings on {% data variables.product.prodname_marketplace %} should be for tools that provide value to the {% data variables.product.product_name %} community. When you submit your listing for publication, you must read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)." -### 所有应用程序的用户体验要求 +### User experience requirements for all apps -所有上架产品应满足以下要求,无论它们是免费应用程序还是付费应用程序。 +All listings should meet the following requirements, regardless of whether they are for a free or paid app. -- 上架信息不得主动诱导用户离开 {% data variables.product.product_name %}。 -- 上架信息必须包含发布者的有效联系信息。 -- 上架信息必须包含应用程序的相关说明。 -- 上架信息必须指定定价计划。 -- 应用程序必须为客户提供价值,并通过身份验证以外的其他方式与平台集成。 -- 应用程序必须在 {% data variables.product.prodname_marketplace %} 中公开可用,并且不能是测试版或只能通过邀请获取。 -- 应用程序必须设置 web 挂钩事件,以便在发生计划更改或取消时通过 {% data variables.product.prodname_marketplace %} API 通知发布者。 有关详细信息,请参阅“[在应用中使用 {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)”。 +- Listings must not actively persuade users away from {% data variables.product.product_name %}. +- Listings must include valid contact information for the publisher. +- Listings must have a relevant description of the application. +- Listings must specify a pricing plan. +- Apps must provide value to customers and integrate with the platform in some way beyond authentication. +- Apps must be publicly available in {% data variables.product.prodname_marketplace %} and cannot be in beta or available by invite only. +- Apps must have webhook events set up to notify the publisher of any plan changes or cancellations using the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -有关提供良好客户体验的详细信息,请参阅“[应用的客户体验最佳做法](/developers/github-marketplace/customer-experience-best-practices-for-apps)”。 +For more information on providing a good customer experience, see "[Customer experience best practices for apps](/developers/github-marketplace/customer-experience-best-practices-for-apps)." -### 所有应用程序的品牌和上架要求 +### Brand and listing requirements for all apps -- 使用 GitHub 徽标的应用程序必须遵循 {% data variables.product.company_short %} 指南。 有关详细信息,请参阅“[{% data variables.product.company_short %} 徽标和用法](https://github.com/logos)”。 -- 应用必须具有符合“[编写 {% data variables.product.prodname_marketplace %} 上架产品描述](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)”中提供的建议的徽标、功能卡和屏幕截图图像。 -- 上架信息必须包含认真编写并且没有语法错误的说明。 有关编写上架产品的指导,请参阅“[编写 {% data variables.product.prodname_marketplace %} 上架产品描述](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)”。 +- Apps that use GitHub logos must follow the {% data variables.product.company_short %} guidelines. For more information, see "[{% data variables.product.company_short %} Logos and Usage](https://github.com/logos)." +- Apps must have a logo, feature card, and screenshots images that meet the recommendations provided in "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)." +- Listings must include descriptions that are well written and free of grammatical errors. For guidance in writing your listing, see "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)." -为了保护您的客户,我们建议您还要遵循安全最佳实践。 有关详细信息,请参阅“[应用的安全性最佳做法](/developers/github-marketplace/security-best-practices-for-apps)”。 +To protect your customers, we recommend that you also follow security best practices. For more information, see "[Security best practices for apps](/developers/github-marketplace/security-best-practices-for-apps)." -## 免费应用程序注意事项 +## Considerations for free apps {% data reusables.marketplace.free-apps-encouraged %} -## 付费应用程序的要求 +## Requirements for paid apps -要在 {% data variables.product.prodname_marketplace %} 上发布应用程序的付费计划,您的应用程序必须由身份为经验证发布者的组织所拥有。 有关验证过程或转移应用所有权的详细信息,请参阅“[为组织申请发布者验证](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)”。 +To publish a paid plan for your app on {% data variables.product.prodname_marketplace %}, your app must be owned by an organization that is a verified publisher. For more information about the verification process or transferring ownership of your app, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)." -如果您的应用程序已发布,并且您是经验证的发布者,则您可以使用定价计划编辑器发布新的付费计划。 有关详细信息,请参阅“[设置上架产品的定价计划](/developers/github-marketplace/setting-pricing-plans-for-your-listing)”。 +If your app is already published and you're a verified publisher, then you can publish a new paid plan from the pricing plan editor. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)." -要发布付费应用程序(或提供付费计划的应用程序),您还必须满足以下要求: +To publish a paid app (or an app that offers a paid plan), you must also meet the following requirements: -- {% data variables.product.prodname_github_apps %} 应至少有 100 个安装设施。 -- {% data variables.product.prodname_oauth_apps %} 应至少有 200 个用户。 -- 所有付费应用程序必须处理关于新购买、升级、降级、取消和免费试用的 {% data variables.product.prodname_marketplace %} 购买事件。 有关详细信息,请参阅下面的“[付费应用的计费要求](#billing-requirements-for-paid-apps)”。 +- {% data variables.product.prodname_github_apps %} should have a minimum of 100 installations. +- {% data variables.product.prodname_oauth_apps %} should have a minimum of 200 users. +- All paid apps must handle {% data variables.product.prodname_marketplace %} purchase events for new purchases, upgrades, downgrades, cancellations, and free trials. For more information, see "[Billing requirements for paid apps](#billing-requirements-for-paid-apps)" below. -当您准备在 {% data variables.product.prodname_marketplace %} 上发布应用程序时,您必须请求验证应用程序上架信息。 +When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the app listing. {% note %} -注意:{% data reusables.marketplace.app-transfer-to-org-for-verification %} 有关如何将应用转移到组织的信息,请参阅:“[提交要发布的上架信息](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)”。 +**Note:** {% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to transfer an app to an organization, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)." {% endnote %} -## 付费应用程序的计费要求 +## Billing requirements for paid apps -您的应用程序无需处理付款,但需要使用 {% data variables.product.prodname_marketplace %} 购买事件来管理新购买、升级、降级、取消和免费试用。 有关如何将这些事件集成到应用的信息,请参阅“[在应用中使用 {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)”。 +Your app does not need to handle payments but does need to use {% data variables.product.prodname_marketplace %} purchase events to manage new purchases, upgrades, downgrades, cancellations, and free trials. For information about how integrate these events into your app, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -GitHub 的计费 API 允许客户在不离开 GitHub 的情况下购买应用程序,并使用已附加到其在 {% data variables.product.product_location %} 上帐户的付款方式来支付服务费用。 +Using GitHub's billing API allows customers to purchase an app without leaving GitHub and to pay for the service with the payment method already attached to their account on {% data variables.location.product_location %}. -- 应用程序必须在付费订阅计划中支持月度和年度计费。 -- 上架产品可提供免费和付费计划的任何组合。 免费计划是可选项,但建议提供。 有关详细信息,请参阅“[设置 {% data variables.product.prodname_marketplace %} 上架产品的定价计划](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)”。 +- Apps must support both monthly and annual billing for paid subscriptions purchases. +- Listings may offer any combination of free and paid plans. Free plans are optional but encouraged. For more information, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)." diff --git a/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md b/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md index 14d2ccaa0f..f5da9567b4 100644 --- a/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md +++ b/translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md @@ -1,6 +1,6 @@ --- -title: 应用程序的安全最佳实践 -intro: '准备在 {% data variables.product.prodname_marketplace %} 上分享安全应用程序的指南。' +title: Security best practices for apps +intro: 'Guidelines for preparing a secure app to share on {% data variables.product.prodname_marketplace %}.' redirect_from: - /apps/marketplace/getting-started/security-review-process - /marketplace/getting-started/security-review-process @@ -12,58 +12,52 @@ versions: ghec: '*' topics: - Marketplace -ms.openlocfilehash: aaff313f73b74ba28f765050a8f993a9dddea1be -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145084984' --- -遵循这些最佳实践将有助于您提供安全的用户体验。 +If you follow these best practices it will help you to provide a secure user experience. -## 授权、身份验证和访问控制 +## Authorization, authentication, and access control -我们建议创建 GitHub 应用程序,而不是 OAuth 应用程序。 {% data reusables.marketplace.github_apps_preferred %}。 有关详细信息,请参阅“[GitHub 应用与 OAuth 应用的区别](/apps/differences-between-apps/)”。 -- 应用程序应使用最小权限原则,只请求应用程序执行其预期功能所需的 OAuth 作用域和 GitHub 应用程序权限。 有关详细信息,请参阅维基百科[最小权限原则](https://en.wikipedia.org/wiki/Principle_of_least_privilege)。 -- 应用程序应为客户提供删除其帐户的方法,而无需发送电子邮件或呼叫支持人员。 -- 应用程序不应在应用程序的不同实现之间共享令牌。 例如,桌面应用程序应该使用与基于 Web 的应用程序不同的令牌。 单个令牌允许每个应用程序单独请求 GitHub 资源所需的访问权限。 -- 根据每种用户类型所需的功能,针对不同的用户角色设计应用程序。 例如,标准用户不应有权访问管理功能,帐单管理员可能不需要仓库代码推送权限。 -- 应用程序不应共享服务帐户(如电子邮件或数据库服务)来管理 SaaS 服务。 -- 应用程序中使用的所有服务都应具有唯一的登录名和密码凭据。 -- 对生产托管基础架构的管理员权限只能授予担当管理职责的工程师和员工。 -- 应用不应使用个人访问令牌进行身份验证,并且应作为 [OAuth 应用](/apps/about-apps/#about-oauth-apps)或 [GitHub 应用](/apps/about-apps/#about-github-apps)进行身份验证: - - OAuth 应用应使用 [OAuth 令牌](/apps/building-oauth-apps/authorizing-oauth-apps/)进行身份验证。 - - GitHub 应用应使用 [JSON Web 令牌 (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)、[OAuth 令牌](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)或[安装访问令牌](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)进行身份验证。 +We recommend creating a GitHub App rather than an OAuth App. {% data reusables.marketplace.github_apps_preferred %}. See "[Differences between GitHub Apps and OAuth Apps](/apps/differences-between-apps/)" for more details. +- Apps should use the principle of least privilege and should only request the OAuth scopes and GitHub App permissions that the app needs to perform its intended functionality. For more information, see [Principle of least privilege](https://en.wikipedia.org/wiki/Principle_of_least_privilege) in Wikipedia. +- Apps should provide customers with a way to delete their account, without having to email or call a support person. +- Apps should not share tokens between different implementations of the app. For example, a desktop app should have a separate token from a web-based app. Individual tokens allow each app to request the access needed for GitHub resources separately. +- Design your app with different user roles, depending on the functionality needed by each type of user. For example, a standard user should not have access to admin functionality, and billing managers might not need push access to repository code. +- Apps should not share service accounts such as email or database services to manage your SaaS service. +- All services used in your app should have unique login and password credentials. +- Admin privilege access to the production hosting infrastructure should only be given to engineers and employees with administrative duties. +- Apps should not use {% data variables.product.pat_generic %}s to authenticate and should authenticate as an [OAuth App](/apps/about-apps/#about-oauth-apps) or a [GitHub App](/apps/about-apps/#about-github-apps): + - OAuth Apps should authenticate using an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/). + - GitHub Apps should authenticate using either a [JSON Web Token (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app), [OAuth token](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/), or [installation access token](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). -## 数据保护 +## Data protection -- 应用程序应使用带有有效 TLS 证书或 SSH for Git 的 HTTPS 对通过公共互联网传输的数据进行加密。 -- 应用程序应安全地存储客户端 ID 和客户端密钥。 建议将它们存储为[环境变量](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables)。 -- 应用程序应在收到用户请求后 30 天内或在用户与 GitHub 的法律关系终止后 30 天内删除所有 GitHub 用户数据。 -- 应用程序不应要求用户提供其 GitHub 密码。 -- 应用程序应该对令牌、客户端 ID 和客户端密钥进行加密。 +- Apps should encrypt data transferred over the public internet using HTTPS, with a valid TLS certificate, or SSH for Git. +- Apps should store client ID and client secret keys securely. We recommend storing them as [environmental variables](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables). +- Apps should delete all GitHub user data within 30 days of receiving a request from the user, or within 30 days of the end of the user's legal relationship with GitHub. +- Apps should not require the user to provide their GitHub password. +- Apps should encrypt tokens, client IDs, and client secrets. -## 日志记录和监视 +## Logging and monitoring -应用程序应具有日志记录和监视功能。 应用程序日志应保留至少 30 天,并存档至少一年。 -安全日志应包括: +Apps should have logging and monitoring capabilities. App logs should be retained for at least 30 days and archived for at least one year. +A security log should include: -- 身份验证和授权事件 -- 服务配置更改 -- 对象读取和写入 -- 所有用户和组权限更改 -- 角色提升到管理员 -- 每个事件的一致时间戳 -- 所有记录操作的源用户、IP 地址和/或主机名 +- Authentication and authorization events +- Service configuration changes +- Object reads and writes +- All user and group permission changes +- Elevation of role to admin +- Consistent timestamping for each event +- Source users, IP addresses, and/or hostnames for all logged actions -## 事件响应工作流 +## Incident response workflow -要为用户提供安全体验,应在上架应用程序之前制定明确的事件响应计划。 我们建议您在自己的公司内成立安全和运营事件响应团队,而不是使用第三方供应商。 您应该能够在确认事件后 24 小时内通知 {% data variables.product.product_name %}。 +To provide a secure experience for users, you should have a clear incident response plan in place before listing your app. We recommend having a security and operations incident response team in your company rather than using a third-party vendor. You should have the capability to notify {% data variables.product.product_name %} within 24 hours of a confirmed incident. -有关事件响应工作流的示例,请参阅 [SANS 研究所网站](https://www.sans.org/information-security-policy/)上的“数据泄露响应策略”。 包含明确的事件响应措施的简短文档比冗长的策略模板更有价值。 +For an example of an incident response workflow, see the "Data Breach Response Policy" on the [SANS Institute website](https://www.sans.org/information-security-policy/). A short document with clear steps to take in the event of an incident is more valuable than a lengthy policy template. -## 漏洞管理和补丁工作流程 +## Vulnerability management and patching workflow -您应该定期对生产基础架构进行漏洞扫描。 您应该对漏洞扫描的结果进行分类,并定义您同意修复漏洞的时间段。 +You should conduct regular vulnerability scans of production infrastructure. You should triage the results of vulnerability scans and define a period of time in which you agree to remediate the vulnerability. -如果您还没有准备好设置完整的漏洞管理程序,最好先创建一个修补流程。 有关创建修补程序管理策略的指南,请参阅此 TechRepublic 文章:“[建立修补程序管理策略](https://www.techrepublic.com/article/establish-a-patch-management-policy-87756/)”。 +If you are not ready to set up a full vulnerability management program, it's useful to start by creating a patching process. For guidance in creating a patch management policy, see this TechRepublic article "[Establish a patch management policy](https://www.techrepublic.com/article/establish-a-patch-management-policy-87756/)." diff --git a/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md b/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md index 28b9b22cb7..0725eb52ca 100644 --- a/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md +++ b/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md @@ -1,6 +1,6 @@ --- -title: 编写应用程序的上架说明 -intro: '要在 {% data variables.product.prodname_marketplace %} 中[上架应用](/marketplace/listing-on-github-marketplace/),你需要根据 GitHub 的指南编写应用说明并提供图像。' +title: Writing a listing description for your app +intro: 'To [list your app](/marketplace/listing-on-github-marketplace/) in the {% data variables.product.prodname_marketplace %}, you''ll need to write descriptions of your app and provide images that follow GitHub''s guidelines.' redirect_from: - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-writing-github-app-descriptions - /apps/marketplace/creating-and-submitting-your-app-for-approval/writing-github-app-descriptions @@ -17,186 +17,180 @@ versions: topics: - Marketplace shortTitle: Write listing descriptions -ms.openlocfilehash: f29e049529801011d25d2723c5851b56d7a8bb92 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146139254' --- -下面是关于需要在商品草稿的“商品说明”部分填写的字段的指南。 +Here are guidelines about the fields you'll need to fill out in the **Listing description** section of your draft listing. -## 命名和链接 +## Naming and links -### 上架产品名称 +### Listing name -你的商品名称将显示在 [{% data variables.product.prodname_marketplace %} 主页](https://github.com/marketplace)上。 名称仅限于 255 个字符,可能与应用名称不同。 您的列表不能与 {% data variables.product.product_location %} 上现有的帐户同名,除非该名称是您自己的用户或组织名称。 +Your listing's name will appear on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace). The name is limited to 255 characters and can be different from your app's name. Your listing cannot have the same name as an existing account on {% data variables.location.product_location %}, unless the name is your own user or organization name. -### 简短说明 +### Very short description -社区将在 [{% data variables.product.prodname_marketplace %} 主页](https://github.com/marketplace)上看到应用名称下的“非常简短的”说明。 +The community will see the "very short" description under your app's name on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace). -![{% data variables.product.prodname_marketplace %} 应用程序简短说明](/assets/images/marketplace/marketplace_short_description.png) +![{% data variables.product.prodname_marketplace %} app short description](/assets/images/marketplace/marketplace_short_description.png) -#### 长度 +#### Length -我们建议将简短说明控制在 40-80 个字符。 尽管可以使用更多字符,但简洁的描述使客户更容易快速阅读和理解。 +We recommend keeping short descriptions to 40-80 characters. Although you are allowed to use more characters, concise descriptions are easier for customers to read and understand quickly. -#### 内容 +#### Content -- 介绍应用程序的功能。 不要在此空间使用呼吁用语。 例如: +- Describe the app’s functionality. Don't use this space for a call to action. For example: - 可以:针对 GitHub 问题的轻型项目管理 + **DO:** Lightweight project management for GitHub issues - 不可:管理 GitHub 上的项目和问题 + **DON'T:** Manage your projects and issues on GitHub - 提示:在呼吁用语中的谓词末尾加上“s”,将其转变为可接受的说明:Manages your projects and issues on GitHub(管理 GitHub 上的项目和问题) + **Tip:** Add an "s" to the end of the verb in a call to action to turn it into an acceptable description: _Manages your projects and issues on GitHub_ -- 不要在说明中重复应用程序的名称。 +- Don’t repeat the app’s name in the description. - 可以:容器原生持续集成工具 + **DO:** A container-native continuous integration tool - 不可:Skycap 是一种容器原生持续集成工具 + **DON'T:** Skycap is a container-native continuous integration tool -#### 格式化 +#### Formatting -- 始终使用句子大小写规则。 只大写第一个字母和专有名词。 +- Always use sentence-case capitalization. Only capitalize the first letter and proper nouns. -- 在简短说明的末尾不要使用标点符号。 简短说明不应包含完整的句子,并且绝对不能包含一个以上的句子。 +- Don't use punctuation at the end of your short description. Short descriptions should not include complete sentences, and definitely should not include more than one sentence. -- 仅大写专有名词。 例如: +- Only capitalize proper nouns. For example: - 可以:One-click delivery automation for web developers + **DO:** One-click delivery automation for web developers - 不可:One-click delivery automation for Web Developers + **DON'T:** One-click delivery automation for Web Developers -- 始终在列表中使用[连续逗号](https://en.wikipedia.org/wiki/Serial_comma)。 +- Always use a [serial comma](https://en.wikipedia.org/wiki/Serial_comma) in lists. -- 避免将 GitHub 社区称为“用户”。 +- Avoid referring to the GitHub community as "users." - 可以:为组织中的人员自动创建问题 + **DO:** Create issues automatically for people in your organization - 不可:为组织的用户自动创建问题 + **DON'T:** Create issues automatically for an organization's users -- 避免使用首字母缩写词,除非是约定俗成的缩写(如 API)。 例如: +- Avoid acronyms unless they’re well established (such as API). For example: - 可以:Agile task boards, estimates, and reports without leaving GitHub + **DO:** Agile task boards, estimates, and reports without leaving GitHub - 不可:Agile task boards, estimates, and reports without leaving GitHub’s UI + **DON'T:** Agile task boards, estimates, and reports without leaving GitHub’s UI -### 类别 +### Categories -{% data variables.product.prodname_marketplace %} 中的应用程序可以按类别显示。 在“主要类别”下拉列表中选择最能描述应用的主要功能的类别,并(可选)选择适合应用的“辅助类别” 。 +Apps in {% data variables.product.prodname_marketplace %} can be displayed by category. Select the category that best describes the main functionality of your app in the **Primary category** dropdown, and optionally select a **Secondary category** that fits your app. -### 支持的语言 +### Supported languages -如果您的应用程序仅适用于特定语言,请选择它支持的最多 10 种编程语言。 这些语言显示在应用程序的 {% data variables.product.prodname_marketplace %} 上架信息页面上。 此字段可选。 +If your app only works with specific languages, select up to 10 programming languages that your app supports. These languages are displayed on your app's {% data variables.product.prodname_marketplace %} listing page. This field is optional. -### 上架信息中的 URL +### Listing URLs -**所需 URL** -* 客户支持 URL:当客户进行技术支持、产品或帐户查询时,他们将访问的网页的 URL。 -* 隐私策略 URL:显示应用的隐私策略的网页。 -* 安装 URL:仅针对 OAuth 应用显示此字段。 (GitHub 应用不使用此 URL,因为它们使用 GitHub 应用的设置页面中的可选设置 URL。)当客户购买 OAuth 应用时,GitHub 会在客户安装该应用后将其重定向到安装 URL。 需要将客户重定向到 `https://github.com/login/oauth/authorize` 以开始 OAuth 授权流。 有关更多详细信息,请参阅“[OAuth 应用的新购买](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)”。 如果您要上架 GitHub 应用程序,请跳过此字段。 +**Required URLs** +* **Customer support URL:** The URL of a web page that your customers will go to when they have technical support, product, or account inquiries. +* **Privacy policy URL:** The web page that displays your app's privacy policy. +* **Installation URL:** This field is shown for OAuth Apps only. (GitHub Apps don't use this URL because they use the optional Setup URL from the GitHub App's settings page instead.) When a customer purchases your OAuth App, GitHub will redirect customers to the installation URL after they install the app. You will need to redirect customers to `https://github.com/login/oauth/authorize` to begin the OAuth authorization flow. See "[New purchases for OAuth Apps](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" for more details. Skip this field if you're listing a GitHub App. -**可选 URL** -* 公司 URL:指向公司网站的链接。 -* 状态 URL:指向显示应用状态的网页的链接。 状态页面可以包括当前和历史事件报告、Web 应用程序正常运行时间状态以及预定维护。 -* 文档 URL:指向指导客户如何使用应用的文档的链接。 +**Optional URLs** +* **Company URL:** A link to your company's website. +* **Status URL:** A link to a web page that displays the status of your app. Status pages can include current and historical incident reports, web application uptime status, and scheduled maintenance. +* **Documentation URL:** A link to documentation that teaches customers how to use your app. -## 徽标和特征卡 +## Logo and feature card -{% data variables.product.prodname_marketplace %} 使用圆形徽章内的方形徽标图像显示所有上架产品,以便从视觉上区分应用程序。 +{% data variables.product.prodname_marketplace %} displays all listings with a square logo image inside a circular badge to visually distinguish apps. -![GitHub Marketplace 徽标和徽章图像](/assets/images/marketplace/marketplace-logo-and-badge.png) +![GitHub Marketplace logo and badge images](/assets/images/marketplace/marketplace-logo-and-badge.png) -特征卡由应用程序的徽标、名称和自定义背景图像组成,可体现您的品牌个性。 如果你的应用是[主页](https://github.com/marketplace)顶部的四个随机特色应用之一,{% data variables.product.prodname_marketplace %} 将显示此卡片。 每个应用程序的简短说明显示在其特征卡的下方。 +A feature card consists of your app's logo, name, and a custom background image that captures your brand personality. {% data variables.product.prodname_marketplace %} displays this card if your app is one of the four randomly featured apps at the top of the [homepage](https://github.com/marketplace). Each app's very short description is displayed below its feature card. -![特征卡](/assets/images/marketplace/marketplace_feature_card.png) +![Feature card](/assets/images/marketplace/marketplace_feature_card.png) -当您上传图像和选择颜色时,{% data variables.product.prodname_marketplace %} 上架草稿将显示徽标和特征卡的预览。 +As you upload images and select colors, your {% data variables.product.prodname_marketplace %} draft listing will display a preview of your logo and feature card. -#### 徽标指南 +#### Guidelines for logos -您必须上传徽标的自定义图像。 对于徽章,请选择背景颜色。 +You must upload a custom image for the logo. For the badge, choose a background color. -- 上传至少为 200 像素 x 200 像素的徽标图像,这样在发布上架信息时就不必放大徽标。 -- 徽标将被裁剪为正方形。 建议上传徽标居中的正方形图像文件。 -- 为获得最佳效果,请上传透明背景的徽标图像。 -- 要显示无缝徽章的外观,请选择与徽标图像的背景颜色(或透明度)匹配的徽章背景颜色。 -- 避免使用带有文字的徽标图像。 带有文字的徽标在小屏幕上缩放效果不佳。 +- Upload a logo image that is at least 200 pixels x 200 pixels so your logo won't have to be upscaled when your listing is published. +- Logos will be cropped to a square. We recommend uploading a square image file with your logo in the center. +- For best results, upload a logo image with a transparent background. +- To give the appearance of a seamless badge, choose a badge background color that matches the background color (or transparency) of your logo image. +- Avoid using logo images with words or text in them. Logos with text do not scale well on small screens. -#### 特征卡指南 +#### Guidelines for feature cards -您必须上传特征卡的自定义背景图像。 对于应用程序的名称,请选择文本颜色。 +You must upload a custom background image for the feature card. For the app's name, choose a text color. -- 在背景图像中使用图案或纹理赋予卡片视觉特征,使其在 {% data variables.product.prodname_marketplace %} 主页的深色背景下引人注目。 特征卡应体现应用程序的品牌个性。 -- 背景图像尺寸为 965 像素 x 482 像素(宽 x 高)。 -- 为应用程序的名称选择文本颜色,使其清晰地显示在背景图像上。 +- Use a pattern or texture in your background image to give your card a visual identity and help it stand out against the dark background of the {% data variables.product.prodname_marketplace %} homepage. Feature cards should capture your app's brand personality. +- Background image measures 965 pixels x 482 pixels (width x height). +- Choose a text color for your app's name that shows up clearly over the background image. -## 商品详细信息 +## Listing details -要获取应用程序的登录页面,请在 {% data variables.product.prodname_marketplace %} 主页或类别页面上单击应用程序的名称。 登录页面显示应用程序的较长说明,包括两个部分:“Introductory description(简介)”和“Detailed description(详细说明)”。 +To get to your app's landing page, click your app's name from the {% data variables.product.prodname_marketplace %} homepage or category page. The landing page displays a longer description of the app, which includes two parts: an "Introductory description" and a "Detailed description." -“Introductory description(简介)”显示在应用程序 {% data variables.product.prodname_marketplace %} 登录页面的顶部。 +Your "Introductory description" is displayed at the top of your app's {% data variables.product.prodname_marketplace %} landing page. -![{% data variables.product.prodname_marketplace %} 简介](/assets/images/marketplace/marketplace_intro_description.png) +![{% data variables.product.prodname_marketplace %} introductory description](/assets/images/marketplace/marketplace_intro_description.png) -单击“阅读更多......”显示“详细说明”。 +Clicking **Read more...**, displays the "Detailed description." -![{% data variables.product.prodname_marketplace %} 详细说明](/assets/images/marketplace/marketplace_detailed_description.png) +![{% data variables.product.prodname_marketplace %} detailed description](/assets/images/marketplace/marketplace_detailed_description.png) -请遵循以下指南编写这些说明。 +Follow these guidelines for writing these descriptions. -### 长度 +### Length -建议在[列出应用](/marketplace/listing-on-github-marketplace/)时,在所需的“介绍性说明”字段中编写 1-2 句简要摘要(介于 150-250 个字符之间)。 尽管可以使用更多字符,但简洁的概述使客户更容易快速阅读和理解。 +We recommend writing a 1-2 sentence high-level summary between 150-250 characters in the required "Introductory description" field when [listing your app](/marketplace/listing-on-github-marketplace/). Although you are allowed to use more characters, concise summaries are easier for customers to read and understand quickly. -您可以在可选的“Detailed description(详细说明)”字段中添加更多信息。 在单击应用登陆页上的介绍性说明下方的“阅读更多......”时,将看到此说明。 详细说明包含 3-5 个[价值主张](https://en.wikipedia.org/wiki/Value_proposition),每个主张用 1-2 个句子描述。 此说明最多可以使用 1,000 个字符。 +You can add more information in the optional "Detailed description" field. You see this description when you click **Read more...** below the introductory description on your app's landing page. A detailed description consists of 3-5 [value propositions](https://en.wikipedia.org/wiki/Value_proposition), with 1-2 sentences describing each one. You can use up to 1,000 characters for this description. -### 内容 +### Content -- 始终用应用程序的名称开始简介。 +- Always begin introductory descriptions with your app's name. -- 始终用主动语态编写说明和价值主张。 +- Always write descriptions and value propositions using the active voice. -### 格式化 +### Formatting -- 始终在价值主张标题中使用句子大小写规则。 只大写第一个字母和专有名词。 +- Always use sentence-case capitalization in value proposition titles. Only capitalize the first letter and proper nouns. -- 在说明中使用句点。 避免使用感叹号。 +- Use periods in your descriptions. Avoid exclamation marks. -- 在价值主张标题的末尾不要使用标点符号。 价值主张标题不应包含完整的句子,并且不能包含一个以上的句子。 +- Don't use punctuation at the end of your value proposition titles. Value proposition titles should not include complete sentences, and should not include more than one sentence. -- 对于每个价值主张,请在其标题后加上一段说明。 使用 Markdown 将标题的格式设置为[三级标头](/articles/basic-writing-and-formatting-syntax/#headings)。 例如: +- For each value proposition, include a title followed by a paragraph of description. Format the title as a [level-three header](/articles/basic-writing-and-formatting-syntax/#headings) using Markdown. For example: - ### 学习所需的技能 + ### Learn the skills you need - GitHub Skills 可以帮助你可学习如何使用 GitHub、如何使用 Markdown 更有效地沟通以及如何处理合并冲突等。 + GitHub Skills can help you learn how to use GitHub, communicate more effectively with Markdown, handle merge conflicts, and more. -- 仅大写专有名词。 +- Only capitalize proper nouns. -- 始终在列表中使用[连续逗号](https://en.wikipedia.org/wiki/Serial_comma)。 +- Always use the [serial comma](https://en.wikipedia.org/wiki/Serial_comma) in lists. -- 避免将 GitHub 社区称为“用户”。 +- Avoid referring to the GitHub community as "users." - 可以:为组织中的人员自动创建问题 + **DO:** Create issues automatically for people in your organization - 不可:为组织的用户自动创建问题 + **DON'T:** Create issues automatically for an organization's users -- 避免使用首字母缩写词,除非是约定俗成的缩写(如 API)。 +- Avoid acronyms unless they’re well established (such as API). -## 产品屏幕截图 +## Product screenshots -您可以上传应用程序的最多五张屏幕截图,以显示在应用程序的登录页面上。 向每个屏幕截图添加可选标题以提供上下文。 上传屏幕截图后,您将其拖动到希望它们在登录页面上显示的位置。 +You can upload up to five screenshot images of your app to display on your app's landing page. Add an optional caption to each screenshot to provide context. After you upload your screenshots, you can drag them into the order you want them to be displayed on the landing page. -### 屏幕截图指南 +### Guidelines for screenshots -- 图像必须具有高分辨率(至少 1200 像素宽)。 -- 所有图像必须具有相同的高度和宽度(宽高比),以避免用户切换图像时出现页面跳跃。 -- 显示尽可能多的用户界面,以便用户看到应用程序执行的操作。 -- 在浏览器中截取应用程序的屏幕时,仅包括显示窗口中的内容。 避免包括地址栏、标题栏或工具栏图标,它们不能很好地适应较小的屏幕尺寸。 -- GitHub 在应用程序登录页面的图框中显示您上传的屏幕截图,因此您无需在屏幕截图周围添加图框或边框。 -- 简短明快的字幕效果最好。 +- Images must be of high resolution (at least 1200px wide). +- All images must be the same height and width (aspect ratio) to avoid page jumps when people click from one image to the next. +- Show as much of the user interface as possible so people can see what your app does. +- When taking screenshots of your app in a browser, only include the content in the display window. Avoid including the address bar, title bar, or toolbar icons, which do not scale well to smaller screen sizes. +- GitHub displays the screenshots you upload in a box on your app's landing page, so you don't need to add boxes or borders around your screenshots. +- Captions are most effective when they are short and snappy. -![GitHub Marketplace 屏幕截图](/assets/images/marketplace/marketplace-screenshots.png) +![GitHub Marketplace screenshot image](/assets/images/marketplace/marketplace-screenshots.png) diff --git a/translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md b/translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md index bbf5297755..39aa90ed6b 100644 --- a/translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md +++ b/translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md @@ -1,6 +1,6 @@ --- -title: GitHub Marketplace 应用程序的定价计划 -intro: '定价计划允许您为应用程序提供不同级别的服务或资源。 您可以在 {% data variables.product.prodname_marketplace %} 上架信息中提供最多 10 个定价计划。' +title: Pricing plans for GitHub Marketplace apps +intro: 'Pricing plans allow you to provide your app with different levels of service or resources. You can offer up to 10 pricing plans in your {% data variables.product.prodname_marketplace %} listing.' redirect_from: - /apps/marketplace/selling-your-app/github-marketplace-pricing-plans - /marketplace/selling-your-app/github-marketplace-pricing-plans @@ -11,55 +11,49 @@ versions: topics: - Marketplace shortTitle: Pricing plans for apps -ms.openlocfilehash: e1ab751c26e59ec42e16dc7d9e5c0118dedffbde -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147876069' --- -{% data variables.product.prodname_marketplace %} 定价计划可以是免费、统一定价或每单位定价。 价格以美元设置、显示和处理。 付费计划仅限验证的发布者发布的应用。 有关成为已验证发布者的详细信息,请参阅“[为组织申请发布者验证](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)”。 +{% data variables.product.prodname_marketplace %} pricing plans can be free, flat rate, or per-unit. Prices are set, displayed, and processed in US dollars. Paid plans are restricted to apps published by verified publishers. For more information about becoming a verified publisher, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)." -客户使用附加到其在 {% data variables.product.product_location %} 上帐户的付款方式购买您的应用程序,而不必离开 {% data variables.product.prodname_dotcom_the_website %}。 您不必编写代码来执行结算交易,但必须处理来自 {% data variables.product.prodname_marketplace %} API 的事件。 有关详细信息,请参阅“[在应用中使用 {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)”。 +Customers purchase your app using a payment method attached to their account on {% data variables.location.product_location %}, without having to leave {% data variables.product.prodname_dotcom_the_website %}. You don't have to write code to perform billing transactions, but you will have to handle events from the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -如果您在 {% data variables.product.prodname_marketplace %} 中上架的应用程序有多个计划选项,您可以设置相应的定价计划。 例如,如果您的应用程序有两个计划选项:开源计划和专业计划,您可以为开源计划设置一个免费定价计划,为专业计划设置一个统一定价计划。 每个 {% data variables.product.prodname_marketplace %} 上架产品必须为列出的每个计划提供年度和月度价格。 +If the app you're listing on {% data variables.product.prodname_marketplace %} has multiple plan options, you can set up corresponding pricing plans. For example, if your app has two plan options, an open source plan and a pro plan, you can set up a free pricing plan for your open source plan and a flat pricing plan for your pro plan. Each {% data variables.product.prodname_marketplace %} listing must have an annual and a monthly price for every plan that's listed. -有关如何创建定价计划的详细信息,请参阅“[设置 {% data variables.product.prodname_marketplace %} 上架的定价计划](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)”。 +For more information on how to create a pricing plan, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)." {% data reusables.marketplace.free-plan-note %} -## 定价计划的类型 +## Types of pricing plans -### 免费定价计划 +### Free pricing plans {% data reusables.marketplace.free-apps-encouraged %} -免费计划对用户完全免费。 如果您设置免费定价计划,则无法向选择免费定价计划的用户收取使用应用程序的费用。 您可以为上架产品同时创建免费和付费计划。 +Free plans are completely free for users. If you set up a free pricing plan, you cannot charge users that choose the free pricing plan for the use of your app. You can create both free and paid plans for your listing. -所有应用程序都需要处理新购买和取消事件。 仅含免费计划的应用程序无需处理免费试用、升级和降级事件。 有关详细信息,请参阅“[在应用中使用 {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)”。 +All apps need to handle events for new purchases and cancellations. Apps that only have free plans do not need to handle events for free trials, upgrades, and downgrades. For more information, see: "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -如果您向已作为免费服务在 {% data variables.product.prodname_marketplace %} 中上架的应用程序添加付费计划,则需要请求验证应用程序并完成财务手续。 +If you add a paid plan to an app that you've already listed in {% data variables.product.prodname_marketplace %} as a free service, you'll need to request verification for the app and go through financial onboarding. -### 付费定价计划 +### Paid pricing plans -有两种类型的付费定价计划: +There are two types of paid pricing plan: -- 统一定价计划按月和按年收取固定费用。 +- Flat rate pricing plans charge a set fee on a monthly and yearly basis. -- 每单位定价计划按月或按年向您指定的单位收取固定费用。 “单位”可以是您愿意指定的任何对象(例如用户、席位或人员)。 +- Per-unit pricing plans charge a set fee on either a monthly or yearly basis for a unit that you specify. A "unit" can be anything you'd like (for example, a user, seat, or person). -您可能还希望提供免费试用。 这些选项为客户提供为期 14 天免费试用 OAuth 或 GitHub 应用程序的机会。 设置 Marketplace 定价计划时,您可以选择为统一定价或每单位定价计划提供免费试用选项。 +You may also want to offer free trials. These provide free, 14-day trials of OAuth or GitHub Apps to customers. When you set up a Marketplace pricing plan, you can select the option to provide a free trial for flat-rate or per-unit pricing plans. -## 免费试用 +## Free trials -客户可以免费试用 Marketplace 上架产品中包含免费试用选项的任何付费计划。 但是,客户不能对一个 Marketplace 产品使用多次免费试用机会。 +Customers can start a free trial for any paid plan on a Marketplace listing that includes free trials. However, customers cannot create more than one free trial per marketplace product. -免费试用的固定期限为 14 天。 客户在试用期结束前 4 天(免费试用期第 11 天)收到通知,他们的计划将升级。 在免费试用结束时,如果客户不取消,他们将自动注册到他们正在试用的计划中。 +Free trials have a fixed length of 14 days. Customers are notified 4 days before the end of their trial period (on day 11 of the free trial) that their plan will be upgraded. At the end of a free trial, customers will be auto-enrolled into the plan they are trialing if they do not cancel. -有关详细信息,请参阅“[处理新购买和免费试用](/developers/github-marketplace/handling-new-purchases-and-free-trials/)”。 +For more information, see: "[Handling new purchases and free trials](/developers/github-marketplace/handling-new-purchases-and-free-trials/)." {% note %} -注意:GitHub 希望你在取消试用后 30 天(从收到取消事件开始算起)内删除任何私人客户数据。 +**Note:** GitHub expects you to delete any private customer data within 30 days of a cancelled trial, beginning at the receipt of the cancellation event. {% endnote %} diff --git a/translations/zh-CN/content/developers/overview/about-githubs-apis.md b/translations/zh-CN/content/developers/overview/about-githubs-apis.md index 0911a23156..dbaa547ee2 100644 --- a/translations/zh-CN/content/developers/overview/about-githubs-apis.md +++ b/translations/zh-CN/content/developers/overview/about-githubs-apis.md @@ -18,9 +18,9 @@ topics: {% data variables.product.company_short %} provides two APIs: a REST API and a GraphQL API. You can interact with both APIs using {% data variables.product.prodname_cli %}, curl, the official Octokit libraries, and third party libraries. Occasionally, a feature may be supported on one API but not the other. -You should choose the API that best aligns with your needs and that you are most comfortable using. This article discusses the benefits of each API. +You should use the API that best aligns with your needs and that you are most comfortable using. You don't need to exclusively use one API over the other. Node IDs let you move between the REST API and GraphQL API. For more information, see "[Using global node IDs](/graphql/guides/using-global-node-ids)." -For more information about the GraphQL API, see [the GraphQL documentation](/graphql). For more information about the REST API, see [the REST documentation](/rest). +This article discusses the benefits of each API. For more information about the GraphQL API, see "[About the GraphQL API](/graphql/overview/about-the-graphql-api)." For more information about the REST API, see [the REST documentation](/rest). ## Choosing the GraphQL API @@ -79,7 +79,3 @@ mutation { } } ``` - -## Choosing both - -You don't need to exclusively use one API over the other. Node IDs let you move between the REST API and GraphQL API. For more information, see "[Using global node IDs](/graphql/guides/using-global-node-ids)." diff --git a/translations/zh-CN/content/developers/overview/managing-deploy-keys.md b/translations/zh-CN/content/developers/overview/managing-deploy-keys.md index 45e840a023..9f838c2051 100644 --- a/translations/zh-CN/content/developers/overview/managing-deploy-keys.md +++ b/translations/zh-CN/content/developers/overview/managing-deploy-keys.md @@ -61,7 +61,7 @@ If you don't want to use SSH keys, you can use HTTPS with OAuth tokens. #### Setup -See [our guide on creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token). +See [our guide on creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token). ## Deploy keys @@ -151,7 +151,7 @@ Since GitHub Apps are a first class actor on {% data variables.product.product_ ## Machine users -If your server needs to access multiple repositories, you can create a new account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} and attach an SSH key that will be used exclusively for automation. Since this account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team). +If your server needs to access multiple repositories, you can create a new account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} and attach an SSH key that will be used exclusively for automation. Since this account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team). {% ifversion fpt or ghec %} diff --git a/translations/zh-CN/content/developers/overview/secret-scanning-partner-program.md b/translations/zh-CN/content/developers/overview/secret-scanning-partner-program.md index 6f888275c8..dfbff80a06 100644 --- a/translations/zh-CN/content/developers/overview/secret-scanning-partner-program.md +++ b/translations/zh-CN/content/developers/overview/secret-scanning-partner-program.md @@ -110,7 +110,7 @@ key to use based on the value of `GITHUB-PUBLIC-KEY-IDENTIFIER`. {% note %} -**Note**: When you send a request to the public key endpoint above, you may hit rate limits. To avoid hitting rate limits, you can use a personal access token (no scopes required) as suggested in the samples below, or use a conditional request. For more information, see "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#conditional-requests)." +**Note**: When you send a request to the public key endpoint above, you may hit rate limits. To avoid hitting rate limits, you can use a {% data variables.product.pat_v1 %} (no scopes required){% ifversion pat-v2 %} or a {% data variables.product.pat_v2 %} (only the automatic public repositories read access required){% endif %} as suggested in the samples below, or use a conditional request. For more information, see "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#conditional-requests)." {% endnote %} @@ -149,7 +149,7 @@ HzZFI03Exwz8Lh/tCfL3YxwMdLjB+bMznsanlhK0RwcGP3IDb34kQDIo3Q== {% endnote %} The following code snippets demonstrate how you could perform signature validation. -The code examples assume you've set an environment variable called `GITHUB_PRODUCTION_TOKEN` with a generated [personal access token](https://github.com/settings/tokens) (PAT) to avoid hitting rate limits. The PAT does not need any scopes/permissions. +The code examples assume you've set an environment variable called `GITHUB_PRODUCTION_TOKEN` with a generated [{% data variables.product.pat_generic %}](https://github.com/settings/tokens) to avoid hitting rate limits. The {% data variables.product.pat_generic %} does not need any scopes/permissions. **Validation sample in Go** ```golang diff --git a/translations/zh-CN/content/discussions/guides/finding-your-discussions.md b/translations/zh-CN/content/discussions/guides/finding-your-discussions.md index aabf4b797e..5cf3819504 100644 --- a/translations/zh-CN/content/discussions/guides/finding-your-discussions.md +++ b/translations/zh-CN/content/discussions/guides/finding-your-discussions.md @@ -1,26 +1,22 @@ --- -title: 查找讨论 -intro: 可以轻松访问你创建或参与的每个讨论。 +title: Finding your discussions +intro: You can easily access every discussion you've created or participated in. versions: feature: discussions shortTitle: Find discussions redirect_from: - /discussions/guides/finding-discussions-across-multiple-repositories -ms.openlocfilehash: cef92d2d042ece7feeeb0364244a70520f12966d -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147883269' --- -## 查找讨论 -1. 在 {% data variables.product.product_location %} 的右上角,单击你的个人资料照片,然后单击“你的讨论”。 - ![{% data variables.product.product_name %} 上个人资料照片下拉菜单中的“你的讨论”](/assets/images/help/discussions/your-discussions.png) -1. 在“已创建”和“已批注”之间切换,以查看已创建或参与的讨论 。 -## 延伸阅读 +## Finding discussions -- [搜索讨论](/search-github/searching-on-github/searching-discussions) -- [关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions) -- [管理社区的讨论](/discussions/managing-discussions-for-your-community) +1. In the top-right corner of {% data variables.location.product_location %}, click your profile photo, then click **Your discussions**. + !["Your discussions" in drop-down menu for profile photo on {% data variables.product.product_name %}](/assets/images/help/discussions/your-discussions.png) +1. Toggle between **Created** and **Commented** to see the discussions you've created or participated in. + +## Further reading + +- "[Searching discussions](/search-github/searching-on-github/searching-discussions)" +- "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" +- "[Managing discussions for your community](/discussions/managing-discussions-for-your-community)" diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md index bc080bc218..bd69c78cb1 100644 --- a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md +++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md @@ -1,70 +1,68 @@ --- -title: 管理讨论类别 -intro: 可以对讨论进行分类,以组织社区成员的对话,也可为每个类别选择格式。 +title: Managing categories for discussions +intro: 'You can categorize discussions to organize conversations for your community members, and you can choose a format for each category.' permissions: Repository administrators and people with write or greater access to a repository can manage categories for discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage categories for discussions in the organization. versions: feature: discussions shortTitle: Manage categories redirect_from: - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository -ms.openlocfilehash: e16d25ad2bb72f4aea9b441529cb8e9a7a0fee48 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147410465' --- -## 关于讨论类别 + + +## About categories for discussions {% data reusables.discussions.about-discussions %} {% data reusables.discussions.about-categories-and-formats %} {% data reusables.discussions.about-announcement-format %} -每个类别必须具有唯一的名称和表情符号配对,并可以附有说明其用途的详细说明。 类别帮助维护者组织如何提交对话,并可自定义,以帮助区分问答或更多开放式对话的类别。 {% data reusables.discussions.repository-category-limit %} 有关详细信息,请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)”。 +Each category must have a unique name and emoji pairing, and can be accompanied by a detailed description stating its purpose. Categories help maintainers organize how conversations are filed and are customizable to help distinguish categories that are Q&A or more open-ended conversations. {% data reusables.discussions.repository-category-limit %} For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." -## 默认类别 +## Default categories -| 类别 | 用途 | 格式 | +| Category | Purpose | Format | | :- | :- | :- | -| 📣 公告 | 项目维护者提供的最新消息和新闻 | 公告 | -| #️⃣ 常规 | 与项目相关的任何及所有内容 | 开放式讨论 | -|💡 想法 | 改变或改进项目的想法 | 开放式讨论 | -| 🗳 投票 | 提供多个选项的投票,供社区进行投票和讨论 | 投票 | -| 🙏 问答 | 供社区回答的问题,使用问题/回答的形式 | 问答 | -| 🙌 展示和说明 | 与项目有关的创作、试验或测试 | 开放式讨论 | +| 📣 Announcements | Updates and news from project maintainers | Announcement | +| #️⃣ General | Anything and everything relevant to the project | Open-ended discussion | +|💡 Ideas | Ideas to change or improve the project | Open-ended discussion | +| 🗳 Polls | Polls with multiple options for the community to vote for and discuss | Polls | +| 🙏 Q&A | Questions for the community to answer, with a question/answer format | Question and Answer | +| 🙌 Show and tell | Creations, experiments, or tests relevant to the project | Open-ended discussion | -## 创建类别 +## Creating a category -1. 在 {% data variables.product.product_location %} 上,导航到要在其中创建类别的存储库或组织的主页。 -{% data reusables.discussions.discussions-tab %} {% data reusables.discussions.edit-categories %} -1. 单击“新建类别”。 - ![存储库讨论类别列表上方的“新建类别”按钮](/assets/images/help/discussions/click-new-category-button.png) -1. 编辑类别的表情符号、标题、说明和讨论格式。 有关讨论格式的详细信息,请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)”。 - ![新建类别的表情符号、标题、说明和讨论格式](/assets/images/help/discussions/edit-category-details.png) -1. 单击“创建”。 - ![新建类别的“创建”按钮](/assets/images/help/discussions/new-category-click-create-button.png) - -## 编辑类别 - -您可以编辑类别以更改类别的表情符号、标题、说明和讨论格式。 - -1. 在 {% data variables.product.product_location %} 上,导航到要在其中编辑类别的存储库或组织的主页。 +1. On {% data variables.location.product_location %}, navigate to the main page of the repository or organization where you want to create a category. {% data reusables.discussions.discussions-tab %} -1. 在列表中类别右侧,单击 {% octicon "pencil" aria-label="The pencil icon" %}。 - ![存储库类别列表中类别右侧的“编辑”按钮](/assets/images/help/discussions/click-edit-for-category.png) -1. {% data reusables.discussions.edit-category-details %} ![编辑现有类别的表情符号、标题、说明和讨论格式](/assets/images/help/discussions/edit-existing-category-details.png) -1. 单击“保存更改”。 - ![现有类别的“保存更改”按钮](/assets/images/help/discussions/existing-category-click-save-changes-button.png) +{% data reusables.discussions.edit-categories %} +1. Click **New category**. + !["New category" button above list of discussion categories for a repository](/assets/images/help/discussions/click-new-category-button.png) +1. Edit the emoji, title, description, and discussion format for the category. For more information about discussion formats, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)." + ![Emoji, title, description, and discussion format for new category](/assets/images/help/discussions/edit-category-details.png) +1. Click **Create**. + !["Create" button for new category](/assets/images/help/discussions/new-category-click-create-button.png) -## 删除类别 +## Editing a category -删除类别时,{% data variables.product.product_name %} 会将已删除类别中的所有讨论移到您选择的现有类别。 +You can edit a category to change the category's emoji, title, description, and discussion format. -1. 在 {% data variables.product.product_location %} 上,导航到要在其中删除类别的存储库或组织的主页。 +1. On {% data variables.location.product_location %}, navigate to the main page of the repository or organization where you want to edit a category. {% data reusables.discussions.discussions-tab %} -1. 在列表中类别右侧,单击 {% octicon "trash" aria-label="The trash icon" %}。 - ![存储库类别列表中类别右侧的“回收站”按钮](/assets/images/help/discussions/click-delete-for-category.png) -1. 使用下拉菜单,为要删除的类别中的任何讨论选择新类别。 - ![删除现有类别时用于选择新建类别的下拉菜单](/assets/images/help/discussions/choose-new-category.png) -1. 单击“删除和移动”。 - ![删除现有类别时用于选择新建类别的下拉菜单](/assets/images/help/discussions/click-delete-and-move-button.png) +1. To the right of a category in the list, click {% octicon "pencil" aria-label="The pencil icon" %}. + ![Edit button to the right of category in list of categories for a repository](/assets/images/help/discussions/click-edit-for-category.png) +1. {% data reusables.discussions.edit-category-details %} + ![Editing emoji, title, description, and discussion format for existing category](/assets/images/help/discussions/edit-existing-category-details.png) +1. Click **Save changes**. + !["Save changes" button for existing category](/assets/images/help/discussions/existing-category-click-save-changes-button.png) + +## Deleting a category + +When you delete a category, {% data variables.product.product_name %} will move all discussions in the deleted category to an existing category that you choose. + +1. On {% data variables.location.product_location %}, navigate to the main page of the repository or organization where you want to delete a category. +{% data reusables.discussions.discussions-tab %} +1. To the right of a category in the list, click {% octicon "trash" aria-label="The trash icon" %}. + ![Trash button to the right of category in list of categories for a repository](/assets/images/help/discussions/click-delete-for-category.png) +1. Use the drop-down menu, and choose a new category for any discussions in the category you're deleting. + ![Drop-down menu for choosing new category when deleting an existing category](/assets/images/help/discussions/choose-new-category.png) +1. Click **Delete & Move**. + ![Drop-down menu for choosing new category when deleting an existing category](/assets/images/help/discussions/click-delete-and-move-button.png) diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md index 26d9f21fd5..2c45e9104d 100644 --- a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md +++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md @@ -1,109 +1,118 @@ --- -title: 管理讨论 -intro: 可以分类、聚焦、转让或删除讨论。 +title: Managing discussions +intro: 'You can categorize, spotlight, transfer, or delete the discussions.' permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage discussions in the organization. versions: feature: discussions shortTitle: Manage discussions redirect_from: - /discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository -ms.openlocfilehash: 95e806959eef023fd05e91a43f9269c98b5db052 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147786212' --- -## 关于讨论的管理 -{% data reusables.discussions.about-discussions %} 有关讨论的详细信息,请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)”。 -组织所有者可以选择在组织拥有的存储库中创建讨论所需的权限。 同样,若要选择创建组织讨论所需的权限,组织所有者可以更改源存储库中所需的权限。 有关详细信息,请参阅“[管理组织中存储库的讨论创建](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)”。 +## About management of discussions -作为讨论维护者,您可以创建社区资源,以鼓励与总体项目目标一致的讨论,并为协作者维护一个友好、开放的论坛。 为协作者制定{% ifversion fpt or ghec %}行为守则或{% endif %}参与指南将有助于促进协作和富有成效的论坛。 有关如何创建社区资源的详细信息,请参阅{% ifversion fpt or ghec %}“[向项目添加行为准则](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)”和{% endif %}“[设置适用于存储库参与者的指南](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)”。 +{% data reusables.discussions.about-discussions %} For more information about discussions, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." -当讨论产生可以解决的想法或漏洞时,您可以从讨论创建新议题。 有关详细信息,请参阅“[创建问题](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)”。 +Organization owners can choose the permissions required to create a discussion in repositories owned by the organization. Similarly, to choose the permissions required to create an organization discussion, organization owners can change the permissions required in the source repository. For more information, see "[Managing discussion creation for repositories in your organization](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)." -有关如何促进健康讨论的详细信息,请参阅“[缓和评论和对话](/communities/moderating-comments-and-conversations)”。 +As a discussions maintainer, you can create community resources to encourage discussions that are aligned with the overall project goal and maintain a friendly open forum for collaborators. Creating{% ifversion fpt or ghec %} a code of conduct or{% endif %} contribution guidelines for collaborators to follow will help facilitate a collaborative and productive forum. For more information on creating community resources, see{% ifversion fpt or ghec %} "[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)," and{% endif %} "[Setting guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)." + +When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)." + +For more information on facilitating a healthy discussion, see "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)." {% data reusables.discussions.you-can-label-discussions %} -## 必备知识 +## Prerequisites -要管理仓库中的讨论,必须为仓库启用 {% data variables.product.prodname_discussions %}。 有关详细信息,请参阅“[启用或禁用存储库的 {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)”。 +To manage discussions in a repository, {% data variables.product.prodname_discussions %} must be enabled for the repository. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." -若要管理组织中的讨论,必须为组织启用 {% data variables.product.prodname_discussions %}。 有关详细信息,请参阅“[启用或禁用组织的 {% data variables.product.prodname_discussions %}](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)”。 +To manage discussions in an organization, {% data variables.product.prodname_discussions %} must be enabled for the organization. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)." -## 更改讨论类别 +## Changing the category for a discussion -您可以对讨论进行分类,以帮助社区成员查找相关的讨论。 有关详细信息,请参阅“[管理讨论的类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)”。 +You can categorize discussions to help community members find related discussions. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)." -您也可以将讨论移动到另一个类别。 无法将讨论移动到投票类别或从投票类别移出。 +You can also move a discussion to a different category. It's not possible to move a discussion to or from the polls category. -{% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. 在右侧边栏中“Category(类别)”的右侧,单击 {% octicon "gear" aria-label="The gear icon" %}。 - ![带有齿轮图标的“类别”](/assets/images/help/discussions/category-in-sidebar.png) -1. 单击一个类别。 - ![“更改类别”下拉菜单](/assets/images/help/discussions/change-category-drop-down.png) +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, to the right of "Category", click {% octicon "gear" aria-label="The gear icon" %}. + !["Category" with gear icon](/assets/images/help/discussions/category-in-sidebar.png) +1. Click a category. + !["Change category" drop-down menu](/assets/images/help/discussions/change-category-drop-down.png) -## 固定讨论 +## Pinning a discussion -可以在存储库或组织讨论列表上固定多达四个重要的讨论。 +You can pin up to four important discussions above the list of discussions for the repository or organization. -{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. 在右侧栏中,单击 {% octicon "pin" aria-label="The pin icon" %}“固定讨论”。 - ![讨论的右侧栏中的“固定讨论”](/assets/images/help/discussions/click-pin-discussion.png) -1. (可选)自定义固定讨论的外观。 - ![固定讨论的自定义选项](/assets/images/help/discussions/customize-pinned-discussion.png) -1. 单击“固定讨论”。 - ![固定讨论的自定义选项下的“固定讨论”按钮](/assets/images/help/discussions/click-pin-discussion-button.png) +{% data reusables.discussions.navigate-to-repo-or-org %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**. + !["Pin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-pin-discussion.png) +1. Optionally, customize the look of the pinned discussion. + ![Customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png) +1. Click **Pin discussion**. + !["Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png) -## 编辑固定的讨论 +## Editing a pinned discussion -编辑固定的讨论不会更改讨论的类别。 有关详细信息,请参阅“[管理讨论的类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)”。 +Editing a pinned discussion will not change the discussion's category. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)." -{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. 在右侧栏中,单击 {% octicon "pencil" aria-label="The pencil icon" %}“编辑固定讨论”。 - ![讨论的右侧栏中的“编辑固定讨论”](/assets/images/help/discussions/click-edit-pinned-discussion.png) -1. 自定义固定的讨论的外观。 - ![固定讨论的自定义选项](/assets/images/help/discussions/customize-pinned-discussion.png) -1. 单击“固定讨论”。 - ![固定讨论的自定义选项下的“固定讨论”按钮](/assets/images/help/discussions/click-pin-discussion-button.png) +{% data reusables.discussions.navigate-to-repo-or-org %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**. + !["Edit pinned discussion" in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png) +1. Customize the look of the pinned discussion. + ![Customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png) +1. Click **Pin discussion**. + !["Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png) -## 取消固定讨论 +## Unpinning a discussion -{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. 在右侧栏中,单击 {% octicon "pin" aria-label="The pin icon" %}“取消固定讨论”。 - ![讨论的右侧栏中的“取消固定讨论”](/assets/images/help/discussions/click-unpin-discussion.png) -1. 阅读警告,然后单击“取消固定讨论”。 - ![模态中警告下方的“取消固定讨论”按钮](/assets/images/help/discussions/click-unpin-discussion-button.png) +{% data reusables.discussions.navigate-to-repo-or-org %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**. + !["Unpin discussion" in right sidebar for discussion](/assets/images/help/discussions/click-unpin-discussion.png) +1. Read the warning, then click **Unpin discussion**. + !["Unpin discussion" button beneath warning in modal](/assets/images/help/discussions/click-unpin-discussion-button.png) -## 转让讨论 +## Transferring a discussion -要转让讨论,您必须具有在要转让讨论的仓库中创建讨论的权限。 如果要将讨论转让给组织,必须具有在组织的讨论的源存储库中创建讨论的权限。 您只能在同一用户或组织帐户拥有的仓库之间转让讨论。 不能将讨论从专用{% ifversion ghec or ghes %}或内部{% endif %}存储库转移到公共存储库。 +To transfer a discussion, you must have permissions to create discussions in the repository where you want to transfer the discussion. If you want to transfer a discussion to an organization, you must have permissions to create discussions in the source repository for the organization's discussions. You can only transfer discussions between repositories owned by the same user or organization account. You can't transfer a discussion from a private{% ifversion ghec or ghes %} or internal{% endif %} repository to a public repository. -{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. 在右侧栏中,单击 {% octicon "arrow-right" aria-label="The right arrow icon" %}“转让讨论”。 - ![讨论的右侧栏中的“转让讨论”](/assets/images/help/discussions/click-transfer-discussion.png) -1. 选择“选择存储库”下拉列表,并单击要将讨论转让到的存储库。 如果要将讨论转让给组织,请选择组织的讨论的源存储库。 - ![“选择存储库”下拉列表、“查找存储库”搜索字段以及列表中的存储库](/assets/images/help/discussions/use-choose-a-repository-drop-down.png) -1. 单击“转让讨论”。 - ![“转让讨论”按钮](/assets/images/help/discussions/click-transfer-discussion-button.png) +{% data reusables.discussions.navigate-to-repo-or-org %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} **Transfer discussion**. + !["Transfer discussion" in right sidebar for discussion](/assets/images/help/discussions/click-transfer-discussion.png) +1. Select the **Choose a repository** drop-down, and click the repository you want to transfer the discussion to. If you want to transfer a discussion to an organization, choose the source repository for the organization's discussions. + !["Choose a repository" drop-down, "Find a repository" search field, and repository in list](/assets/images/help/discussions/use-choose-a-repository-drop-down.png) +1. Click **Transfer discussion**. + !["Transfer discussion" button](/assets/images/help/discussions/click-transfer-discussion-button.png) -## 删除讨论 +## Deleting a discussion -{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. 在右侧栏中,单击 {% octicon "trash" aria-label="The trash arrow icon" %}“删除讨论”。 - ![讨论的右侧栏中的“删除讨论”](/assets/images/help/discussions/click-delete-discussion.png) -1. 阅读警告,然后单击“删除此讨论”。 - ![模态中警告下方的“删除此讨论”按钮](/assets/images/help/discussions/click-delete-this-discussion-button.png) +{% data reusables.discussions.navigate-to-repo-or-org %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**. + !["Delete discussion" in right sidebar for discussion](/assets/images/help/discussions/click-delete-discussion.png) +1. Read the warning, then click **Delete this discussion**. + !["Delete this discussion" button beneath warning in modal](/assets/images/help/discussions/click-delete-this-discussion-button.png) -## 基于标签转换议题 +## Converting issues based on labels -您可以将具有相同标签的所有议题批量转换为讨论。 具有此标签的未来议题也将自动转换为您配置的讨论和类别。 +You can convert all issues with the same label to discussions in bulk. Future issues with this label will also automatically convert to the discussion and category you configure. -1. 在 {% data variables.product.product_location %} 上,导航到存储库的主页,对于组织讨论,导航到源存储库的主页。 -{% data reusables.repositories.sidebar-issues %} {% data reusables.project-management.labels %} -1. 在要转换为问题的标签旁边,单击“转换问题”。 -1. 选择“选择类别”下拉菜单,然后单击某个类别进行讨论。 -1. 单击“我明白,将此问题转化为讨论”。 +1. On {% data variables.location.product_location %}, navigate to the main page of the repository or, for organization discussions, the source repository. +{% data reusables.repositories.sidebar-issues %} +{% data reusables.project-management.labels %} +1. Next to the label you want to convert to issues, click **Convert issues**. +1. Select the **Choose a category** drop-down menu, and click a category for your discussion. +1. Click **I understand, convert this issue to a discussion**. diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md index 9591e560f7..4272e08f49 100644 --- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md @@ -1,37 +1,31 @@ --- -title: 关于使用 MakeCode Arcade 与 GitHub Classroom +title: About using MakeCode Arcade with GitHub Classroom shortTitle: About using MakeCode Arcade -intro: '您可以将 MakeCode Arcade 配置为 {% data variables.product.prodname_classroom %} 中作业的在线 IDE。' +intro: 'You can configure MakeCode Arcade as the online IDE for assignments in {% data variables.product.prodname_classroom %}.' versions: fpt: '*' redirect_from: - /education/manage-coursework-with-github-classroom/student-experience-makecode - /education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom -ms.openlocfilehash: f4786f67c7a9d0444e92d3c5560f4d86b6a0af7d -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145099786' --- -## 关于 MakeCode Arcade +## About MakeCode Arcade -MakeCode Arcade 是一个在线集成开发环境 (IDE),用于使用拖放块编程和 JavaScript 开发复古街机游戏。 学生可以使用 MakeCode Arcade 在浏览器中编写、编辑、运行、测试和调试代码。 有关 IDE 和 {% data variables.product.prodname_classroom %} 的详细信息,请参阅“[将 {% data variables.product.prodname_classroom %} 与 IDE 集成](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)”。 +MakeCode Arcade is an online integrated development environment (IDE) for developing retro arcade games using drag-and-drop block programming and JavaScript. Students can write, edit, run, test, and debug code in a browser with MakeCode Arcade. For more information about IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)." {% data reusables.classroom.readme-contains-button-for-online-ide %} -学生第一次单击按钮访问 MakeCode Arcade 时,必须使用 {% data variables.product.product_name %} 证书登录 MakeCode Arcade。 登录后,学生将有权访问包含作业仓库中代码、在 MakeCode Arcade 上完全配置的开发环境。 +The first time the student clicks the button to visit MakeCode Arcade, the student must sign into MakeCode Arcade 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 MakeCode Arcade. -有关使用 MakeCode Arcade 的详细信息,请参阅 [MakeCode Arcade](https://arcade.makecode.com/ide-tour) 和 MakeCode Arcade 网站上的[文档](https://arcade.makecode.com/docs)。 +For more information about working on MakeCode Arcade, see the [MakeCode Arcade Tour](https://arcade.makecode.com/ide-tour) and [documentation](https://arcade.makecode.com/docs) on the MakeCode Arcade website. -MakeCode Arcade 不支持对小组作业进行多人编辑。 但学生可以协作使用 Git 和 {% data variables.product.product_name %} 功能,如分支和拉取请求。 +MakeCode Arcade does not support multiplayer-editing for group assignments. Instead, students can collaborate with Git and {% data variables.product.product_name %} features like branches and pull requests. -## 关于使用 MakeCode Arcade 提交作业 +## About submission of assignments with MakeCode Arcade -默认情况下,MakeCode Arcade 配置为推送到 {% data variables.product.product_location %} 上的作业仓库。 使用 MakeCode Arcade 处理作业后,学生应使用屏幕底部的 {% octicon "mark-github" aria-label="The GitHub mark" %}{% octicon "arrow-up" aria-label="The up arrow icon" %} 按钮将更改推送到 {% data variables.product.product_location %}。 +By default, MakeCode Arcade is configured to push to the assignment repository on {% data variables.location.product_location %}. After making progress on an assignment with MakeCode Arcade, students should push changes to {% data variables.location.product_location %} using the {% octicon "mark-github" aria-label="The GitHub mark" %}{% octicon "arrow-up" aria-label="The up arrow icon" %} button at the bottom of the screen. -![MakeCode Arcade 版本控制功能](/assets/images/help/classroom/ide-makecode-arcade-version-control-button.png) +![MakeCode Arcade version control functionality](/assets/images/help/classroom/ide-makecode-arcade-version-control-button.png) -## 延伸阅读 +## Further reading -- [关于自述文件](/github/creating-cloning-and-archiving-repositories/about-readmes) +- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)" diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md index f8ae5e6a8b..7e93c63392 100644 --- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md @@ -1,36 +1,30 @@ --- -title: 查看自动评分结果 -intro: 您可以在作业仓库中查看自动评分结果。 +title: View autograding results +intro: You can see results from autograding within the repository for your assignment. versions: fpt: '*' redirect_from: - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-students - /education/manage-coursework-with-github-classroom/view-autograding-results -ms.openlocfilehash: ea4de9b0122e39f5ecb4d960d4f0ee8c94ba2ee5 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145099780' --- -## 关于自动分级 +## About autograding -教师可以配置测试在您推送到 {% data variables.product.product_location %} 上的作业仓库时自动检查您的工作。 +Your teacher can configure tests that automatically check your work when you push to an assignment repository on {% data variables.location.product_location %}. -如果您是学生,并且讲师已为 {% data variables.product.prodname_classroom %} 中的作业配置自动评分,则您会在整个作业仓库找到自动评分测试结果。 如果提交的所有测试都成功,您将看到绿色复选标记。 如果提交的任何测试失败,您会看到红色的 X。您可以通过单击绿色复选标记或红色 X 查看详细日志。 +If you're a student and your instructor has configured autograding for your assignment in {% data variables.product.prodname_classroom %}, you'll find autograding test results throughout your assignment repository. If all tests succeed for a commit, you'll see a green checkmark. If any tests fail for a commit, you'll see a red X. You can see detailed logs by clicking the green checkmark or red X. -## 查看作业仓库的自动评分结果 +## Viewing autograding results for an assignment repository -{% data variables.product.prodname_classroom %} 使用 {% data variables.product.prodname_actions %} 来运行自动评分测试。 有关查看自动评分测试日志的详细信息,请参阅“[使用工作流运行日志](/actions/managing-workflow-runs/using-workflow-run-logs#viewing-logs-to-diagnose-failures)”。 +{% data variables.product.prodname_classroom %} uses {% data variables.product.prodname_actions %} to run autograding tests. For more information about viewing the logs for an autograding test, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs#viewing-logs-to-diagnose-failures)." -“操作”选项卡显示测试运行的完整历史记录。 +The **Actions** tab shows the full history of test runs. -![“所有工作流”处于选中状态的“操作”选项卡](/assets/images/help/classroom/autograding-actions-tab.png) +!["Actions" tab with "All workflows" selected](/assets/images/help/classroom/autograding-actions-tab.png) -您可以单击特定的测试运行来查看日志输出,如编译错误和测试失败。 +You can click a specific test run to review log output, like compilation errors and test failures. -![{% data variables.product.prodname_actions %} 中的“{% data variables.product.prodname_classroom %} 自动评分工作流”测试结果日志 ](/assets/images/help/classroom/autograding-actions-logs.png) +![The "{% data variables.product.prodname_classroom %} Autograding Workflow" test results logs in {% data variables.product.prodname_actions %} ](/assets/images/help/classroom/autograding-actions-logs.png) -## 延伸阅读 +## Further reading -- [关于状态检查](/github/collaborating-with-issues-and-pull-requests/about-status-checks) +- "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)" diff --git a/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md index 463ad45f8b..1963647dc6 100644 --- a/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md +++ b/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md @@ -29,7 +29,7 @@ With the {% data variables.product.prodname_dotcom %} for {% data variables.prod ## Project management tools -You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party project management tools, such as Jira. +You can integrate your personal or organization account on {% data variables.location.product_location %} with third-party project management tools, such as Jira. ### Jira Cloud and {% data variables.product.product_name %}.com integration @@ -37,7 +37,7 @@ You can integrate Jira Cloud with your personal or organization account to scan ## Team communication tools -You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party team communication tools, such as Slack or Microsoft Teams. +You can integrate your personal or organization account on {% data variables.location.product_location %} with third-party team communication tools, such as Slack or Microsoft Teams. ### Slack and {% data variables.product.product_name %} integration diff --git a/translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md index d0edc162f8..d46262cbb0 100644 --- a/translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md +++ b/translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md @@ -1,6 +1,6 @@ --- -title: 寻找在 GitHub 上参与开源项目的方法 -intro: '可以找到在 {% data variables.product.product_location %} 上参加与你相关的开源项目的方法。' +title: Finding ways to contribute to open source on GitHub +intro: 'You can find ways to contribute to open source projects on {% data variables.location.product_location %} that are relevant to you.' permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}' redirect_from: - /articles/where-can-i-find-open-source-projects-to-work-on @@ -17,46 +17,40 @@ versions: topics: - Open Source shortTitle: Contribute to open source -ms.openlocfilehash: 434927bb3fd1f6816cf76b82a949a4b3369acba9 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145099762' --- -## 发现相关项目 +## Discovering relevant projects -如果你有感兴趣的特定主题,请访问 `github.com/topics/`。 例如,如果你对机器学习感兴趣,可以通过访问 https://github.com/topics/machine-learning 找到相关的项目和合适的第一个议题。 可以通过访问[主题](https://github.com/topics)来浏览热门主题。 您还可以搜索与您感兴趣的主题相匹配的仓库。 有关详细信息,请参阅“[搜索存储库](/search-github/searching-on-github/searching-for-repositories#search-by-topic)”。 +If there's a particular topic that interests you, visit `github.com/topics/`. For example, if you are interested in machine learning, you can find relevant projects and good first issues by visiting https://github.com/topics/machine-learning. You can browse popular topics by visiting [Topics](https://github.com/topics). You can also search for repositories that match a topic you're interested in. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)." -如果你一直活跃在 {% data variables.product.product_location %} 上,可以根据过去的参与情况、标星以及在 [Explore](https://github.com/explore) 中的其他活动,为你的项目找到个性化的建议和合适的第一个议题。 您还可以注册 Explore 通讯以根据您的兴趣接收相关电子邮件,了解参与 {% data variables.product.product_name %} 的机会。 若要注册,请参阅 [Explore 电子邮件新闻稿](https://github.com/explore/subscribe)"。 +If you've been active on {% data variables.location.product_location %}, you can find personalized recommendations for projects and good first issues based on your past contributions, stars, and other activities in [Explore](https://github.com/explore). You can also sign up for the Explore newsletter to receive emails about opportunities to contribute to {% data variables.product.product_name %} based on your interests. To sign up, see [Explore email newsletter](https://github.com/explore/subscribe). -使用个人仪表板及时了解你关注的存储库和人员以及组织的最近活动。 有关详细信息,请参阅“[关于个人仪表板](/articles/about-your-personal-dashboard)”。 +Keep up with recent activity from repositories you watch, as well as people and organizations you follow, with your personal dashboard. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)." {% data reusables.support.ask-and-answer-forum %} -## 查找合适的第一个议题 +## Finding good first issues -如果已经知道要参与哪些项目,可通过访问 `github.com///contribute` 查找该存储库中便于初学者参与的议题。 例如,可以在 https://github.com/electron/electron/contribute 上找到第一次参与 `electron/electron` 的方法。 +If you already know what project you want to work on, you can find beginner-friendly issues in that repository by visiting `github.com///contribute`. For an example, you can find ways to make your first contribution to `electron/electron` at https://github.com/electron/electron/contribute. -## 创建问题 +## Opening an issue -如果在开源项目中遇到漏洞,请检查该漏洞是否已报告。 如果该漏洞尚未报告,您可以根据项目的参与指南开启一个议题来报告该漏洞。 +If you encounter a bug in an open source project, check if the bug has already been reported. If the bug has not been reported, you can open an issue to report the bug according to the project's contribution guidelines. -## 验证议题或拉取请求 +## Validating an issue or pull request -您可以通过多种方式为开源项目做出贡献。 +There are a variety of ways that you can contribute to open source projects. -### 重现报告的漏洞 -您可以通过验证议题或为现有议题添加额外上下文来为开源项目做出贡献。 +### Reproducing a reported bug +You can contribute to an open source project by validating an issue or adding additional context to an existing issue. -### 测试拉取请求 -您可以通过将拉取请求合并到项目的本地副本中并测试更改来为开源项目做出贡献。 在对拉取请求的评论中添加测试结果。 +### Testing a pull request +You can contribute to an open source project by merging a pull request into your local copy of the project and testing the changes. Add the outcome of your testing in a comment on the pull request. -### 更新议题 -您可以通过向现有议题添加额外信息来为开源项目做出贡献。 +### Updating issues +You can contribute to an open source project by adding additional information to existing issues. -## 延伸阅读 +## Further reading -- “[使用主题对存储库分类](/articles/classifying-your-repository-with-topics)” -- “[关于组织仪表板](/articles/about-your-organization-dashboard)” +- "[Classifying your repository with topics](/articles/classifying-your-repository-with-topics)" +- "[About your organization dashboard](/articles/about-your-organization-dashboard)" diff --git a/translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md b/translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md index dd70b14ca5..9f811b3086 100644 --- a/translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md +++ b/translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md @@ -1,5 +1,5 @@ --- -title: 关于远程仓库 +title: About remote repositories redirect_from: - /articles/working-when-github-goes-down - /articles/sharing-repositories-without-github @@ -10,91 +10,85 @@ redirect_from: - /github/using-git/about-remote-repositories - /github/getting-started-with-github/about-remote-repositories - /github/getting-started-with-github/getting-started-with-git/about-remote-repositories -intro: 'GitHub 的协作开发方法取决于从您的本地仓库发布提交到 {% data variables.product.product_name %},以供其他人查看、提取和更新。' +intro: 'GitHub''s collaborative approach to development depends on publishing commits from your local repository to {% data variables.product.product_name %} for other people to view, fetch, and update.' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' -ms.openlocfilehash: 3b328831e09b62dce320ce2c230151e15d1b430b -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145097910' --- -## 关于远程仓库 +## About remote repositories -远程 URL 是 Git 一种指示“您的代码存储位置”的绝佳方式。 该 URL 可能是您在 GitHub 上的仓库,也可以是另一个用户的复刻,甚至在完全不同的服务器上。 +A remote URL is Git's fancy way of saying "the place where your code is stored." That URL could be your repository on GitHub, or another user's fork, or even on a completely different server. -您只能推送到两类 URL 地址: +You can only push to two types of URL addresses: -* HTTPS URL(例如 `https://{% data variables.command_line.backticks %}/user/repo.git`) -* SSH URL(例如 `git@{% data variables.command_line.backticks %}:user/repo.git`) +* An HTTPS URL like `https://{% data variables.command_line.backticks %}/user/repo.git` +* An SSH URL, like `git@{% data variables.command_line.backticks %}:user/repo.git` -Git 将远程 URL 与名称相关联,你的默认远程通常名为 `origin`。 +Git associates a remote URL with a name, and your default remote is usually called `origin`. -## 创建远程仓库 +## Creating remote repositories -可以使用 `git remote add` 命令将远程 URL 与名称匹配。 -例如,在命令行中输入以下命令: +You can use the `git remote add` command to match a remote URL with a name. +For example, you'd type the following in the command line: ```shell -git remote add origin <REMOTE_URL> +git remote add origin <REMOTE_URL> ``` -这会将名称 `origin` 与 `REMOTE_URL` 相关联。 +This associates the name `origin` with the `REMOTE_URL`. -可以使用命令 `git remote set-url` [更改远程 URL](/github/getting-started-with-github/managing-remote-repositories)。 +You can use the command `git remote set-url` to [change a remote's URL](/github/getting-started-with-github/managing-remote-repositories). -## 选择远程仓库的 URL +## Choosing a URL for your remote repository -克隆 {% data variables.product.product_location %} 上的存储库有几种方法。 +There are several ways to clone repositories available on {% data variables.location.product_location %}. -当您登录到帐户查看仓库时,可以用于将项目克隆到计算机上的 URL 在仓库详细信息下方提供。 +When you view a repository while signed in to your account, the URLs you can use to clone the project onto your computer are available below the repository details. -有关设置或更改远程 URL 的信息,请参阅“[管理远程存储库](/github/getting-started-with-github/managing-remote-repositories)”。 +For information on setting or changing your remote URL, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." -## 使用 HTTPS URL 克隆 +## Cloning with HTTPS URLs -`https://` 克隆 URL 在所有存储库上都可用,无论可见性如何。 即使你在防火墙或代理后面,`https://` 克隆 URL 也有效。 +The `https://` clone URLs are available on all repositories, regardless of visibility. `https://` clone URLs work even if you are behind a firewall or proxy. -在命令行上使用 HTTPS URL 将 `git clone`、`git fetch`、`git pull` 或 `git push` 执行到远程存储库时,Git 将要求你提供 {% data variables.product.product_name %} 用户名和密码。 {% data reusables.user-settings.password-authentication-deprecation %} +When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using HTTPS URLs on the command line, Git will ask for your {% data variables.product.product_name %} username and password. {% data reusables.user-settings.password-authentication-deprecation %} {% data reusables.command_line.provide-an-access-token %} {% tip %} -**提示**: -- 您可以使用凭据小助手,让 Git 在每次与 {% data variables.product.prodname_dotcom %} 通信时记住您的 {% data variables.product.prodname_dotcom %} 凭据。 有关详细信息,请参阅“[在 Git 中缓存 {% data variables.product.prodname_dotcom %} 凭据](/github/getting-started-with-github/caching-your-github-credentials-in-git)”。 -- 要克隆仓库而不在命令行中对 {% data variables.product.product_name %} 进行身份验证,您可以使用 {% data variables.product.prodname_desktop %} 进行克隆。 有关详细信息,请参阅“[将存储库从 {% data variables.product.prodname_dotcom %} 克隆到 {% data variables.product.prodname_dotcom %} 桌面](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)”。 +**Tips**: +- You can use a credential helper so Git will remember your {% data variables.product.prodname_dotcom %} credentials every time it talks to {% data variables.product.prodname_dotcom %}. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)." +- To clone a repository without authenticating to {% data variables.product.product_name %} on the command line, you can use {% data variables.product.prodname_desktop %} to clone instead. For more information, see "[Cloning a repository from {% data variables.product.prodname_dotcom %} to {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)." {% endtip %} - {% ifversion fpt or ghec %}如果希望使用 SSH,但不能通过端口 22 进行连接,则可通过 HTTPS 端口使用 SSH。 有关详细信息,请参阅“[在 HTTPS 端口使用 SSH](/github/authenticating-to-github/using-ssh-over-the-https-port)”。{% endif %} + {% ifversion fpt or ghec %}If you'd rather use SSH but cannot connect over port 22, you might be able to use SSH over the HTTPS port. For more information, see "[Using SSH over the HTTPS port](/github/authenticating-to-github/using-ssh-over-the-https-port)."{% endif %} -## 使用 SSH URL 克隆 +## Cloning with SSH URLs -SSH URL 通过 SSH(一种安全协议)提供 Git 仓库的访问权限。 若要使用这些 URL,必须在计算机上生成 SSH 密钥对,并将“公共”密钥添加到你在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的帐户。 有关详细信息,请参阅“[通过 SSH 连接到 {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/connecting-to-github-with-ssh)”。 +SSH URLs provide access to a Git repository via SSH, a secure protocol. To use these URLs, you must generate an SSH keypair on your computer and add the **public** key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For more information, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/github/authenticating-to-github/connecting-to-github-with-ssh)." -使用 SSH URL 将 `git clone`、`git fetch`、`git pull` 或 `git push` 执行到远程存储库时,系统将提示你输入密码,并且必须提供 SSH 密钥密码。 有关详细信息,请参阅“[使用 SSH 密钥密码](/github/authenticating-to-github/working-with-ssh-key-passphrases)”。 +When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using SSH URLs, you'll be prompted for a password and must provide your SSH key passphrase. For more information, see "[Working with SSH key passphrases](/github/authenticating-to-github/working-with-ssh-key-passphrases)." -{% ifversion fpt or ghec %}如果要访问使用 SAML 单一登录 (SSO) 的组织,在进行身份验证之前,还必须授权 SSH 密钥以访问组织。 有关详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[关于使用 SAML 单一登录进行身份验证](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)”和“[授权 SSH 密钥以用于 SAML 单一登录](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}”。{% else %}."{% endif %}{% endif %} +{% ifversion fpt or ghec %}If you are accessing an organization that uses SAML single sign-on (SSO), you must authorize your SSH key to access the organization before you authenticate. For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} {% tip %} -提示:可以使用 SSH URL 将存储库克隆到计算机,或作为将代码部署到生产服务器的安全方法。 您还可以将 SSH 代理转发与部署脚本一起使用,以避免管理服务器上的密钥。 有关详细信息,请参阅“[使用 SSH 代理转发](/developers/overview/using-ssh-agent-forwarding)”。 +**Tip**: You can use an SSH URL to clone a repository to your computer, or as a secure way of deploying your code to production servers. You can also use SSH agent forwarding with your deploy script to avoid managing keys on the server. For more information, see "[Using SSH Agent Forwarding](/developers/overview/using-ssh-agent-forwarding)." {% endtip %} -## 使用 {% data variables.product.prodname_cli %} 克隆 +## Cloning with {% data variables.product.prodname_cli %} -您还可以安装 {% data variables.product.prodname_cli %} 以在终端中使用 {% data variables.product.product_name %} 工作流程。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)”。 +You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} workflows in your terminal. For more information, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." {% ifversion not ghae %} -## 使用 Subversion 克隆 +## Cloning with Subversion -还可以使用 [Subversion](https://subversion.apache.org/) 客户端访问 {% data variables.product.prodname_dotcom %} 上的任何存储库。 Subversion 提供不同于 Git 的功能集。 有关详细信息,请参阅“[Subversion 和 Git 有哪些区别?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)” +You can also use a [Subversion](https://subversion.apache.org/) client to access any repository on {% data variables.product.prodname_dotcom %}. Subversion offers a different feature set than Git. For more information, see "[What are the differences between Subversion and Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)" -您也可以从 Subversion 客户端访问 {% data variables.product.prodname_dotcom %} 上的仓库。 有关详细信息,请参阅“[对 Subversion 客户端的支持](/github/importing-your-projects-to-github/support-for-subversion-clients)”。 +You can also access repositories on {% data variables.product.prodname_dotcom %} from Subversion clients. For more information, see "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients)." {% endif %} diff --git a/translations/zh-CN/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md b/translations/zh-CN/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md index 5e7736e6e0..a32b554c10 100644 --- a/translations/zh-CN/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md +++ b/translations/zh-CN/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md @@ -1,5 +1,5 @@ --- -title: 在 Git 中缓存 GitHub 凭据 +title: Caching your GitHub credentials in Git redirect_from: - /firewalls-and-proxies - /articles/caching-your-github-password-in-git @@ -7,82 +7,77 @@ redirect_from: - /github/using-git/caching-your-github-credentials-in-git - /github/getting-started-with-github/caching-your-github-credentials-in-git - /github/getting-started-with-github/getting-started-with-git/caching-your-github-credentials-in-git -intro: '如果你[使用 HTTPS 克隆 {% data variables.product.product_name %} 存储库](/github/getting-started-with-github/about-remote-repositories),我们建议你使用 {% data variables.product.prodname_cli %} 或 Git Credential Manager (GCM) 来记住你的凭据。' +intro: 'If you''re [cloning {% data variables.product.product_name %} repositories using HTTPS](/github/getting-started-with-github/about-remote-repositories), we recommend you use {% data variables.product.prodname_cli %} or Git Credential Manager (GCM) to remember your credentials.' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' shortTitle: Caching credentials -ms.openlocfilehash: 203eed949beb3c1ada9c4c099cbaf214aac0c4f7 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145097909' --- + {% tip %} -**提示:** 如果使用 SSH 克隆 {% data variables.product.product_name %} 存储库,则可使用 SSH 密钥进行身份验证,而不是使用其他凭据。 有关设置 SSH 连接的信息,请参阅“[生成 SSH 密钥](/articles/generating-an-ssh-key)”。 +**Tip:** If you clone {% data variables.product.product_name %} repositories using SSH, then you can authenticate using an SSH key instead of using other credentials. For information about setting up an SSH connection, see "[Generating an SSH Key](/articles/generating-an-ssh-key)." {% endtip %} ## {% data variables.product.prodname_cli %} -选择 `HTTPS` 作为 Git 操作的首选协议时,{% data variables.product.prodname_cli %} 将自动为你存储 Git 凭据,并对询问你是否要使用 {% data variables.product.product_name %} 凭据向 Git 进行身份验证的提示回答“是”。 +{% data variables.product.prodname_cli %} will automatically store your Git credentials for you when you choose `HTTPS` as your preferred protocol for Git operations and answer "yes" to the prompt asking if you would like to authenticate to Git with your {% data variables.product.product_name %} credentials. -1. 在 macOS、Windows 或 Linux 上[安装](https://github.com/cli/cli#installation) {% data variables.product.prodname_cli %}。 -2. 在命令行中,输入 `gh auth login`,然后按照提示进行操作。 - - 当系统提示输入 Git 操作的首选协议时,请选择 `HTTPS`。 - - 当系统询问是否要使用 {% data variables.product.product_name %} 凭据向 Git 进行身份验证时,请输入 `Y`。 +1. [Install](https://github.com/cli/cli#installation) {% data variables.product.prodname_cli %} on macOS, Windows, or Linux. +2. In the command line, enter `gh auth login`, then follow the prompts. + - When prompted for your preferred protocol for Git operations, select `HTTPS`. + - When asked if you would like to authenticate to Git with your {% data variables.product.product_name %} credentials, enter `Y`. -有关使用 {% data variables.product.prodname_cli %} 进行身份验证的详细信息,请参阅 [`gh auth login`](https://cli.github.com/manual/gh_auth_login)。 +For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). ## Git Credential Manager -[Git 凭据管理器](https://github.com/GitCredentialManager/git-credential-manager) (GCM) 是安全存储凭据并通过 HTTPS 连接到 GitHub 的另一种方法。 使用 GCM 时,不必手动[创建和存储 PAT](/github/authenticating-to-github/creating-a-personal-access-token),因为 GCM 代表你管理身份验证,包括 2FA(双因素身份验证)。 +[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager) (GCM) is another way to store your credentials securely and connect to GitHub over HTTPS. With GCM, you don't have to manually [create and store a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token), as GCM manages authentication on your behalf, including 2FA (two-factor authentication). {% mac %} -1. 使用 [Homebrew](https://brew.sh/) 安装 Git: +1. Install Git using [Homebrew](https://brew.sh/): ```shell $ brew install git ``` -2. 使用 Homebrew 安装 GCM: +2. Install GCM using Homebrew: ```shell $ brew tap microsoft/git $ brew install --cask git-credential-manager-core ``` - 对于 MacOS,不需要运行 `git config`,因为 GCM 会自动为你配置 Git。 + For MacOS, you don't need to run `git config` because GCM automatically configures Git for you. {% data reusables.gcm-core.next-time-you-clone %} -验证成功后,您的凭据存储在 macOS 密钥链中,每次克隆 HTTPS URL 时都会使用。 Git 不会要求您在命令行中再次键入凭据,除非您更改凭据。 +Once you've authenticated successfully, your credentials are stored in the macOS keychain and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials. {% endmac %} {% windows %} -1. 安装 Windows 版 Git,其中包括 GCM。 有关详细信息,请参阅[版本页面](https://github.com/git-for-windows/git/releases/latest)中的 [Git for Windows 版本](https://github.com/git-for-windows/git/releases/latest)。 +1. Install Git for Windows, which includes GCM. For more information, see "[Git for Windows releases](https://github.com/git-for-windows/git/releases/latest)" from its [releases page](https://github.com/git-for-windows/git/releases/latest). -我们建议始终安装最新版本。 至少安装版本 2.29 或更高版本,这是第一个为 GitHub 提供 OAuth 支持的版本。 +We recommend always installing the latest version. At a minimum, install version 2.29 or higher, which is the first version offering OAuth support for GitHub. {% data reusables.gcm-core.next-time-you-clone %} -成功通过身份验证后,您的凭据将存储在 Windows 凭据管理器中,并且每次克隆 HTTPS URL 时都将使用。 Git 不会要求您在命令行中再次键入凭据,除非您更改凭据。 +Once you've authenticated successfully, your credentials are stored in the Windows credential manager and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials.
{% warning %} -**警告:** 旧版本的 Git for Windows 附有 Windows 版 Git 凭据管理器。 此旧产品不再受支持,并且无法通过 OAuth 连接到 GitHub。 建议升级到[最新版本的 Git for Windows](https://github.com/git-for-windows/git/releases/latest)。 +**Warning:** Older versions of Git for Windows came with Git Credential Manager for Windows. This older product is no longer supported and cannot connect to GitHub via OAuth. We recommend you upgrade to [the latest version of Git for Windows](https://github.com/git-for-windows/git/releases/latest). {% endwarning %} {% warning %} -**警告:** 如果在 Windows 版凭据管理器中缓存了不正确或过期的凭据,Git 将无法访问 {% data variables.product.product_name %}。 若要重置缓存的凭据,以便 Git 提示输入凭据,请在 Windows 控制面板中的“用户帐户”>“凭据管理器”下访问凭据管理器。 找到 {% data variables.product.product_name %} 条目并将其删除。 +**Warning:** If you cached incorrect or outdated credentials in Credential Manager for Windows, Git will fail to access {% data variables.product.product_name %}. To reset your cached credentials so that Git prompts you to enter your credentials, access the Credential Manager in the Windows Control Panel under User Accounts > Credential Manager. Look for the {% data variables.product.product_name %} entry and delete it. {% endwarning %} @@ -90,22 +85,22 @@ ms.locfileid: '145097909' {% linux %} -对于 Linux,安装 Git 和 GCM,然后配置 Git 使用 GCM。 +For Linux, install Git and GCM, then configure Git to use GCM. -1. 从发行版的打包系统安装 Git。 说明将根据您运行的 Linux 的风格而有所不同。 +1. Install Git from your distro's packaging system. Instructions will vary depending on the flavor of Linux you run. -2. 安装 GCM。 查看 [GCM 存储库中的说明](https://github.com/GitCredentialManager/git-credential-manager#linux-install-instructions),说明将根据运行的 Linux 的风格而有所不同。 +2. Install GCM. See the [instructions in the GCM repo](https://github.com/GitCredentialManager/git-credential-manager#linux-install-instructions), as they'll vary depending on the flavor of Linux you run. -3. 配置 Git 使用 GCM 有几个支持商店,您可以从中选择,因此请参阅 GCM 文档来完成设置。 有关详细信息,请参阅“[GCM Linux](https://aka.ms/gcmcore-linuxcredstores)”。 +3. Configure Git to use GCM. There are several backing stores that you may choose from, so see the GCM docs to complete your setup. For more information, see "[GCM Linux](https://aka.ms/gcmcore-linuxcredstores)." {% data reusables.gcm-core.next-time-you-clone %} -验证成功后,您的凭据存储在系统中,每次克隆 HTTPS URL 时都会使用。 Git 不会要求您在命令行中再次键入凭据,除非您更改凭据。 +Once you've authenticated successfully, your credentials are stored on your system and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials. -有关在 Linux 上存储凭据的更多选项,请参阅 Pro Git 中的[凭据存储](https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage)。 +For more options for storing your credentials on Linux, see [Credential Storage](https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage) in Pro Git. {% endlinux %}
-如需详细信息或报告 GCM 问题,请参阅官方 GCM 文档的“[Git 凭据管理器](https://github.com/GitCredentialManager/git-credential-manager)”部分。 +For more information or to report issues with GCM, see the official GCM docs at "[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager)." diff --git a/translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md b/translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md index 5536ab96ca..b10cb2025a 100644 --- a/translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md +++ b/translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md @@ -1,6 +1,6 @@ --- -title: 管理远程仓库 -intro: '了解如何使用计算机上的本地仓库以及 {% data variables.product.product_name %} 上托管的远程仓库。' +title: Managing remote repositories +intro: 'Learn to work with your local repositories on your computer and remote repositories hosted on {% data variables.product.product_name %}.' redirect_from: - /categories/18/articles - /remotes @@ -24,221 +24,216 @@ versions: ghae: '*' ghec: '*' shortTitle: Manage remote repositories -ms.openlocfilehash: 413e1f8fca1991ea198e28daab9d8507668d4f29 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145128992' --- -## 添加远程仓库 +## Adding a remote repository -要新增远程,请在终端上存储存储库的目录中使用 `git remote add` 命令。 +To add a new remote, use the `git remote add` command on the terminal, in the directory your repository is stored at. -`git remote add` 命令采用两个参数: -* 远程名称(例如 `origin`) -* 远程 URL(例如 `https://{% data variables.command_line.backticks %}/user/repo.git`) +The `git remote add` command takes two arguments: +* A remote name, for example, `origin` +* A remote URL, for example, `https://{% data variables.command_line.backticks %}/user/repo.git` -例如: +For example: ```shell -$ git remote add origin https://{% data variables.command_line.codeblock %}/user/repo.git +$ git remote add origin https://{% data variables.command_line.codeblock %}/USER/REPO>.git # Set a new remote $ git remote -v # Verify new remote -> origin https://{% data variables.command_line.codeblock %}/user/repo.git (fetch) -> origin https://{% data variables.command_line.codeblock %}/user/repo.git (push) +> origin https://{% data variables.command_line.codeblock %}/USER/REPO.git (fetch) +> origin https://{% data variables.command_line.codeblock %}/USER/REPO.git (push) ``` -有关要使用的 URL 的详细信息,请参阅“[关于远程存储库](/github/getting-started-with-github/about-remote-repositories)”。 +For more information on which URL to use, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)." -### 故障排除:远程原点已存在 +### Troubleshooting: Remote origin already exists -此错误消息表示您尝试添加的远程与本地仓库中的远程名称相同。 +This error means you've tried to add a remote with a name that already exists in your local repository. ```shell $ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git > fatal: remote origin already exists. ``` -若要解决此问题,可以: -* 对新远程使用不同的名称。 -* 在添加新的远程之前,重命名现有的远程仓库。 有关详细信息,请参阅下面的“[重命名远程存储库](#renaming-a-remote-repository)”。 -* 在添加新的远程之前,删除现有的远程仓库。 有关详细信息,请参阅下面的“[删除远程存储库](#removing-a-remote-repository)”。 +To fix this, you can: +* Use a different name for the new remote. +* Rename the existing remote repository before you add the new remote. For more information, see "[Renaming a remote repository](#renaming-a-remote-repository)" below. +* Delete the existing remote repository before you add the new remote. For more information, see "[Removing a remote repository](#removing-a-remote-repository)" below. -## 更改远程仓库的 URL +## Changing a remote repository's URL -`git remote set-url` 命令更改现有的远程存储库 URL。 +The `git remote set-url` command changes an existing remote repository URL. {% tip %} -提示:有关 HTTPS 和 SSH URL 之间区别的信息,请参阅“[关于远程存储库](/github/getting-started-with-github/about-remote-repositories)”。 +**Tip:** For information on the difference between HTTPS and SSH URLs, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)." {% endtip %} -`git remote set-url` 命令采用两个参数: +The `git remote set-url` command takes two arguments: -* 现有远程仓库的名称。 例如,`origin` 或 `upstream` 是两个常见的选项。 -* 远程仓库的新 URL。 例如: - * 如果您要更新为使用 HTTPS,您的 URL 可能如下所示: +* An existing remote name. For example, `origin` or `upstream` are two common choices. +* A new URL for the remote. For example: + * If you're updating to use HTTPS, your URL might look like: ```shell -https://{% data variables.command_line.backticks %}/USERNAME/REPOSITORY.git +https://{% data variables.command_line.backticks %}/USERNAME/REPOSITORY.git ``` - * 如果您要更新为使用 SSH,您的 URL 可能如下所示: + * If you're updating to use SSH, your URL might look like: ```shell -git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git +git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git ``` -### 将远程 URL 从 SSH 切换到 HTTPS +### Switching remote URLs from SSH to HTTPS {% data reusables.command_line.open_the_multi_os_terminal %} -2. 将当前工作目录更改为您的本地仓库。 -3. 列出现有远程仓库以获取要更改的远程仓库的名称。 +2. Change the current working directory to your local project. +3. List your existing remotes in order to get the name of the remote you want to change. ```shell $ git remote -v - > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (fetch) - > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (push) + > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (fetch) + > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (push) ``` -4. 使用 `git remote set-url` 命令将远程 URL 从 SSH 更改为 HTTPS。 +4. Change your remote's URL from SSH to HTTPS with the `git remote set-url` command. ```shell - $ git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git + $ git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git ``` -5. 验证远程 URL 是否已更改。 +5. Verify that the remote URL has changed. ```shell $ git remote -v # Verify new remote URL - > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (push) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (push) ``` -下次将 `git fetch`、`git pull` 或 `git push` 执行到远程存储库时,系统将要求你提供 GitHub 用户名和密码。 {% data reusables.user-settings.password-authentication-deprecation %} +The next time you `git fetch`, `git pull`, or `git push` to the remote repository, you'll be asked for your GitHub username and password. {% data reusables.user-settings.password-authentication-deprecation %} -可以[使用凭据帮助程序](/github/getting-started-with-github/caching-your-github-credentials-in-git)以便 Git 每次与 GitHub 通信时都会记住你的 GitHub 用户名和个人访问令牌。 +You can [use a credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git) so Git will remember your GitHub username and {% data variables.product.pat_generic %} every time it talks to GitHub. -### 将远程 URL 从 HTTPS 切换到 SSH +### Switching remote URLs from HTTPS to SSH {% data reusables.command_line.open_the_multi_os_terminal %} -2. 将当前工作目录更改为您的本地仓库。 -3. 列出现有远程仓库以获取要更改的远程仓库的名称。 +2. Change the current working directory to your local project. +3. List your existing remotes in order to get the name of the remote you want to change. ```shell $ git remote -v - > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (push) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (push) ``` -4. 使用 `git remote set-url` 命令将远程 URL 从 HTTPS 更改为 SSH。 +4. Change your remote's URL from HTTPS to SSH with the `git remote set-url` command. ```shell - $ git remote set-url origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git + $ git remote set-url origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git ``` -5. 验证远程 URL 是否已更改。 +5. Verify that the remote URL has changed. ```shell $ git remote -v # Verify new remote URL - > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (fetch) - > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (push) + > origin git@{% data variables.command_line.codeblock %}: USERNAME/REPOSITORY.git (fetch) + > origin git@{% data variables.command_line.codeblock %}: USERNAME/REPOSITORY.git (push) ``` -### 故障排除:没有该远程 '[name]' +### Troubleshooting: No such remote '[name]' -此错误表示您尝试更改的远程不存在: +This error means that the remote you tried to change doesn't exist: ```shell $ git remote set-url sofake https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife > fatal: No such remote 'sofake' ``` -检查您是否正确键入了远程仓库的名称。 +Check that you've correctly typed the remote name. -## 重命名远程仓库 +## Renaming a remote repository -使用 `git remote rename` 命令重命名现有远程。 +Use the `git remote rename` command to rename an existing remote. -`git remote rename` 命令采用两个参数: -* 现有远程名称(例如 `origin`) -* 远程的新名称(例如 `destination`) +The `git remote rename` command takes two arguments: +* An existing remote name, for example, `origin` +* A new name for the remote, for example, `destination` -## 示例 +## Example -这些示例假定[使用 HTTPS 进行克隆](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)(建议这样做)。 +These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended. ```shell $ git remote -v # View existing remotes -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) $ git remote rename origin destination # Change remote name from 'origin' to 'destination' $ git remote -v # Verify remote's new name -> destination https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) -> destination https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) +> destination https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) +> destination https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) ``` -### 故障排除:无法将配置部分 'remote.[old name]' 重命名为 'remote.[new name]' +### Troubleshooting: Could not rename config section 'remote.[old name]' to 'remote.[new name]' -此错误表示您键入的旧远程名称不存在。 +This error means that the old remote name you typed doesn't exist. -可以使用 `git remote -v` 命令检查当前存在的远程: +You can check which remotes currently exist with the `git remote -v` command: ```shell $ git remote -v # View existing remotes -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) ``` -### 故障排除:远程 [new name] 已存在 +### Troubleshooting: Remote [new name] already exists -此错误表示您要使用的远程名称已经存在。 要解决此问题,使用不同的远程名称,或重命名原始远程。 +This error means that the remote name you want to use already exists. To solve this, either use a different remote name, or rename the original remote. -## 删除远程仓库 +## Removing a remote repository -使用 `git remote rm` 命令从存储库中删除远程 URL。 +Use the `git remote rm` command to remove a remote URL from your repository. -`git remote rm` 命令采用一个参数: -* 远程名称(例如 `destination`) +The `git remote rm` command takes one argument: +* A remote name, for example, `destination` -从存储库中删除远程 URL 只会取消本地和远程存储库的链接。 它不会删除远程存储库。 +Removing the remote URL from your repository only unlinks the local and remote repositories. It does not delete the remote repository. -## 示例 +## Example -这些示例假定[使用 HTTPS 进行克隆](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)(建议这样做)。 +These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended. ```shell $ git remote -v # View current remotes -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) -> destination https://{% data variables.command_line.codeblock %}/FORKER/REPOSITORY.git (fetch) -> destination https://{% data variables.command_line.codeblock %}/FORKER/REPOSITORY.git (push) +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) +> destination https://{% data variables.command_line.codeblock %}/FORKER/REPOSITORY.git (fetch) +> destination https://{% data variables.command_line.codeblock %}/FORKER/REPOSITORY.git (push) $ git remote rm destination # Remove remote $ git remote -v # Verify it's gone -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) -> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) +> origin https://{% data variables.command_line.codeblock %}/ OWNER/REPOSITORY.git (fetch) +> origin https://{% data variables.command_line.codeblock %}/ OWNER/REPOSITORY.git (push) ``` {% warning %} -注意:`git remote rm` 不会从服务器中删除远程存储库。 它只是从本地存储库中删除远程及其引用。 +**Note**: `git remote rm` does not delete the remote repository from the server. It simply +removes the remote and its references from your local repository. {% endwarning %} -### 故障排除:无法删除配置部分 'remote.[name]' +### Troubleshooting: Could not remove config section 'remote.[name]' -此错误表示您尝试删除的远程不存在: +This error means that the remote you tried to delete doesn't exist: ```shell $ git remote rm sofake > error: Could not remove config section 'remote.sofake' ``` -检查您是否正确键入了远程仓库的名称。 +Check that you've correctly typed the remote name. -## 延伸阅读 +## Further reading -- [Pro Git 书籍中的“使用远程”](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) +- "[Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) diff --git a/translations/zh-CN/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md b/translations/zh-CN/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md index 12a0be1a16..507b7c8f52 100644 --- a/translations/zh-CN/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md +++ b/translations/zh-CN/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md @@ -1,6 +1,6 @@ --- -title: 更新 OSX 密钥链中的凭据 -intro: '如果在 {% data variables.product.product_name %} 上更改你的{% ifversion not ghae %}用户名、密码或{% endif %} 个人访问令牌,你需要在 `git-credential-osxkeychain` 帮助程序中更新保存的凭据。' +title: Updating credentials from the macOS Keychain +intro: 'You''ll need to update your saved credentials in the `git-credential-osxkeychain` helper if you change your{% ifversion not ghae %} username, password, or{% endif %} {% data variables.product.pat_generic %} on {% data variables.product.product_name %}.' redirect_from: - /articles/updating-credentials-from-the-osx-keychain - /github/using-git/updating-credentials-from-the-osx-keychain @@ -13,44 +13,38 @@ versions: ghae: '*' ghec: '*' shortTitle: macOS Keychain credentials -ms.openlocfilehash: ce2e225bcff1aca0c034e564fe3233e5f9cb68d2 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145128979' --- {% tip %} -**注意:** 从 macOS 密钥链更新凭据仅适用于使用内置到 macOS 的 `osxkeychain` 帮助程序手动配置 PAT 的用户。 +**Note:** Updating credentials from the macOS Keychain only applies to users who manually configured a {% data variables.product.pat_generic %} using the `osxkeychain` helper that is built-in to macOS. -建议改为[配置 SSH](/articles/generating-an-ssh-key) 或升级到 [Git 凭据管理器](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) (GCM)。 GCM 可以代表您管理身份验证(不再需要手动 PAT),包括 2FA(双重身份验证)。 +We recommend you either [configure SSH](/articles/generating-an-ssh-key) or upgrade to the [Git Credential Manager](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) (GCM) instead. GCM can manage authentication on your behalf (no more manual {% data variables.product.pat_generic %}s) including 2FA (two-factor auth). {% endtip %} {% data reusables.user-settings.password-authentication-deprecation %} -## 通过 Keychain Access 更新凭据 +## Updating your credentials via Keychain Access -1. 单击菜单栏右侧的 Spotlight 图标(放大镜)。 键入 `Keychain access`,然后按 Enter 键启动应用。 - ![Spotlight 搜索栏](/assets/images/help/setup/keychain-access.png) -2. 在密钥链访问中,搜索 {% data variables.command_line.backticks %}。 -3. 查找 `{% data variables.command_line.backticks %}` 的“Internet 密码”条目。 -4. 相应地编辑或删除该条目。 +1. Click on the Spotlight icon (magnifying glass) on the right side of the menu bar. Type `Keychain access` then press the Enter key to launch the app. + ![Spotlight Search bar](/assets/images/help/setup/keychain-access.png) +2. In Keychain Access, search for **{% data variables.command_line.backticks %}**. +3. Find the "internet password" entry for `{% data variables.command_line.backticks %}`. +4. Edit or delete the entry accordingly. -## 通过命令行删除凭据 +## Deleting your credentials via the command line -通过命令行,您可以使用凭据小助手直接擦除密钥链条目。 +Through the command line, you can use the credential helper directly to erase the keychain entry. ```shell $ git credential-osxkeychain erase host={% data variables.command_line.codeblock %} protocol=https -> [Press Return] +> [Press Return] ``` -如果成功,则不会打印出任何内容。若要测试它是否正常工作,请尝试从 {% data variables.product.product_location %} 克隆专用存储库。 如果提示您输入密码,则该密钥链条目已删除。 +If it's successful, nothing will print out. To test that it works, try and clone a private repository from {% data variables.location.product_location %}. If you are prompted for a password, the keychain entry was deleted. -## 延伸阅读 +## Further reading -- [在 Git 中缓存 {% data variables.product.prodname_dotcom %} 凭据](/github/getting-started-with-github/caching-your-github-credentials-in-git/) +- "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)" diff --git a/translations/zh-CN/content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md b/translations/zh-CN/content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md index 38fbc3473f..284df7ffb1 100644 --- a/translations/zh-CN/content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md +++ b/translations/zh-CN/content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md @@ -1,6 +1,6 @@ --- -title: 为什么 Git 总是询问我的密码? -intro: 如果 Git 在您每次尝试与 GitHub 交互时均提示输入用户名和密码,则您可能为仓库使用的是 HTTPS 克隆 URL。 +title: Why is Git always asking for my password? +intro: 'If Git prompts you for a username and password every time you try to interact with GitHub, you''re probably using the HTTPS clone URL for your repository.' redirect_from: - /articles/why-is-git-always-asking-for-my-password - /github/using-git/why-is-git-always-asking-for-my-password @@ -12,21 +12,15 @@ versions: ghae: '*' ghec: '*' shortTitle: Git passwords -ms.openlocfilehash: 06a8cf617072075f39a880ec58173e7cfbc5bc8a -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145128975' --- -与使用 SSH 相比,使用 HTTPS 远程 URL 具有一些优势。 它比 SSH 更容易设置,通常通过严格的防火墙和代理进行工作。 但是,每次拉取或推送仓库时,它也会提示您输入 {% data variables.product.product_name %} 凭据。 +Using an HTTPS remote URL has some advantages compared with using SSH. It's easier to set up than SSH, and usually works through strict firewalls and proxies. However, it also prompts you to enter your {% data variables.product.product_name %} credentials every time you pull or push a repository. {% data reusables.user-settings.password-authentication-deprecation %} -可以通过将 Git 配置为用于[缓存凭据](/github/getting-started-with-github/caching-your-github-credentials-in-git)来避免系统提示输入密码。 在配置凭据缓存后,当您使用 HTTPS 拉取或推送仓库时,Git 会自动使用缓存的个人访问令牌。 +You can avoid being prompted for your password by configuring Git to [cache your credentials](/github/getting-started-with-github/caching-your-github-credentials-in-git) for you. Once you've configured credential caching, Git automatically uses your cached {% data variables.product.pat_generic %} when you pull or push a repository using HTTPS. -## 延伸阅读 +## Further reading -- “[关于远程存储库](/github/getting-started-with-github/about-remote-repositories)”。 -- “[关于向 {% data variables.product.prodname_dotcom %} 进行身份验证](/github/authenticating-to-github/about-authentication-to-github)” -- “[将 SSH 密钥添加到 ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)” +- "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)." +- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)" +- "[Adding your SSH key to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)" diff --git a/translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md b/translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md index 3591b8af04..d42181b790 100644 --- a/translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md +++ b/translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md @@ -1,6 +1,6 @@ --- -title: 将本地托管代码添加到 GitHub -intro: '了解如何使用 {% data variables.product.prodname_cli %} 或 Git 命令从命令行将现有源代码或存储库添加到 {% data variables.product.product_name %}。 然后,共享代码并邀请其他人与你一起工作。' +title: Adding locally hosted code to GitHub +intro: 'Learn how to add existing source code or repositories to {% data variables.product.product_name %} from the command line using {% data variables.product.prodname_cli %} or Git Commands. Then, share your code and invite others to work with you.' redirect_from: - /articles/add-an-existing-project-to-github - /articles/adding-an-existing-project-to-github-using-the-command-line @@ -13,79 +13,85 @@ versions: ghae: '*' ghec: '*' shortTitle: Add locally hosted code -ms.openlocfilehash: 5dc22ef9d8b5f11618bc90414c9d94fcdfe50462 -ms.sourcegitcommit: 22d665055b1bee7a5df630385e734e3a149fc720 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 07/13/2022 -ms.locfileid: '145128968' --- -## 关于将现有源代码添加到 {% data variables.product.product_name %} -如果计算机或专用网络上已有本地存储的源代码或存储库,可以通过在终端中键入命令来将其添加到 {% data variables.product.product_name %} 中。 也可以通过直接键入 Git 命令或使用 {% data variables.product.prodname_cli %} 来执行此操作。 +## About adding existing source code to {% data variables.product.product_name %} -{% data variables.product.prodname_cli %} 是用于从计算机的命令行使用 {% data variables.product.prodname_dotcom %} 的开源工具。 {% data variables.product.prodname_cli %} 可以简化使用命令行将现有项目添加到 {% data variables.product.product_name %} 的过程。 要详细了解 {% data variables.product.prodname_cli %},请参阅“[关于 {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)”。 +If you have existing source code or repositories stored locally on your computer or private network you can add them to {% data variables.product.product_name %} by typing commands in a terminal. You can do this by typing Git commands directly, or by using {% data variables.product.prodname_cli %}. + +{% data variables.product.prodname_cli %} is an open source tool for using {% data variables.product.prodname_dotcom %} from your computer's command line. {% data variables.product.prodname_cli %} can simplify the process of adding an existing project to {% data variables.product.product_name %} using the command line. To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." {% tip %} -提示:如果你最喜欢点按式用户界面,请尝试使用 {% data variables.product.prodname_desktop %} 添加项目。 有关详细信息,请参阅“{% data variables.product.prodname_desktop %} 帮助”中的[将存储从本地计算机添加到 GitHub 桌面](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop)。 +**Tip:** If you're most comfortable with a point-and-click user interface, try adding your project with {% data variables.product.prodname_desktop %}. For more information, see "[Adding a repository from your local computer to GitHub Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop)" in the *{% data variables.product.prodname_desktop %} Help*. {% endtip %} {% data reusables.repositories.sensitive-info-warning %} -## 使用 {% data variables.product.prodname_cli %} 将本地存储库添加到 {% data variables.product.product_name %} +## Adding a local repository to {% data variables.product.product_name %} with {% data variables.product.prodname_cli %} -1. 在命令行中,导航到项目的根目录。 -1. 将本地目录初始化为 Git 仓库。 +1. In the command line, navigate to the root directory of your project. +1. Initialize the local directory as a Git repository. ```shell git init -b main ``` -1. 暂存并提交项目中的所有文件 +1. Stage and commit all the files in your project. ```shell git add . && git commit -m "initial commit" ``` -1. 要为 GitHub 上的项目创建存储库,请使用 `gh repo create` 子命令。 出现提示时,选择“将现有本地存储库推送到 GitHub”,并输入存储库所需的名称。 如果希望项目属于某个组织而不是你的用户帐户,请使用 `organization-name/project-name` 指定组织名称和项目名称。 +1. To create a repository for your project on GitHub, use the `gh repo create` subcommand. When prompted, select **Push an existing local repository to GitHub** and enter the desired name for your repository. If you want your project to belong to an organization instead of your user account, specify the organization name and project name with `organization-name/project-name`. -1. 按照交互式提示进行操作。 要添加远程并推送存储库,请在被要求添加远程并将提交推送到当前分支时确认“是”。 +1. Follow the interactive prompts. To add the remote and push the repository, confirm yes when asked to add the remote and push the commits to the current branch. -1. 或者,若要跳过提示,请使用 `--source` 标志提供存储库的路径,并传递可见性标志(`--public`、`--private` 或 `--internal`)。 例如 `gh repo create --source=. --public`。 使用 `--remote` 标志指定远程。 要推送提交,请传递 `--push` 标志。 有关可能的参数的详细信息,请参阅 [GitHub CLI 手册](https://cli.github.com/manual/gh_repo_create)。 +1. Alternatively, to skip all the prompts, supply the path to the repository with the `--source` flag and pass a visibility flag (`--public`, `--private`, or `--internal`). For example, `gh repo create --source=. --public`. Specify a remote with the `--remote` flag. To push your commits, pass the `--push` flag. For more information about possible arguments, see the [GitHub CLI manual](https://cli.github.com/manual/gh_repo_create). -## 将本地存储库添加到 {% data variables.product.product_name %} using Git +## Adding a local repository to {% data variables.product.product_name %} using Git {% mac %} -1. 在 {% data variables.product.product_location %} 上[新建存储库](/repositories/creating-and-managing-repositories/creating-a-new-repository)。 为避免错误,请勿使用 README、许可或 `gitignore` 文件初始化新存储库。 您可以在项目推送到 {% data variables.product.product_name %} 之后添加这些文件。 - ![新建存储库下拉菜单](/assets/images/help/repository/repo-create.png) {% data reusables.command_line.open_the_multi_os_terminal %} -3. 将当前工作目录更改为您的本地仓库。 -4. 将本地目录初始化为 Git 仓库。 - ```shell - $ git init -b main - ``` -5. 在新的本地仓库中添加文件。 这会暂存它们用于第一次提交。 +1. [Create a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository) on {% data variables.location.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}. + ![Create New Repository drop-down](/assets/images/help/repository/repo-create.png) +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Change the current working directory to your local project. +4. Use the `init` command to initialize the local directory as a Git repository. By default, the initial branch is called `master`. + + If you’re using Git 2.28.0 or a later version, you can set the name of the default branch using `-b`. + + ``` shell + $ git init -b main + ``` + + If you’re using Git 2.27.1 or an earlier version, you can set the name of the default branch using `&& git symbolic-ref HEAD refs/heads/main`. + + ``` shell + $ git init && git symbolic-ref HEAD refs/heads/main + ``` +5. Add the files in your new local repository. This stages them for the first commit. + ```shell $ git add . # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %} ``` -6. 提交暂存在本地仓库中的文件。 +6. Commit the files that you've staged in your local repository. ```shell $ git commit -m "First commit" # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %} ``` -7. 在仓库顶部 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 的快速设置页面,点击 {% octicon "clippy" aria-label="The copy to clipboard icon" %} 以复制远程仓库 URL。 - ![创建远程存储库 URL 字段](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) -8. 在终端中,[添加远程存储库的 URL](/github/getting-started-with-github/managing-remote-repositories)(将在其中推送本地存储库)。 +7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL. + ![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) +8. In Terminal, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed. ```shell - $ git remote add origin <REMOTE_URL> + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL ``` -9. [将本地存储库中的更改推送](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)到 {% data variables.product.product_location %}。 +9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.location.product_location %}. ```shell $ git push -u origin main # Pushes the changes in your local repository up to the remote repository you specified as the origin @@ -95,33 +101,43 @@ ms.locfileid: '145128968' {% windows %} -1. 在 {% data variables.product.product_location %} 上[新建存储库](/articles/creating-a-new-repository)。 为避免错误,请勿使用 README、许可或 `gitignore` 文件初始化新存储库。 您可以在项目推送到 {% data variables.product.product_name %} 之后添加这些文件。 - ![新建存储库下拉菜单](/assets/images/help/repository/repo-create.png) {% data reusables.command_line.open_the_multi_os_terminal %} -3. 将当前工作目录更改为您的本地仓库。 -4. 将本地目录初始化为 Git 仓库。 - ```shell - $ git init -b main - ``` -5. 在新的本地仓库中添加文件。 这会暂存它们用于第一次提交。 +1. [Create a new repository](/articles/creating-a-new-repository) on {% data variables.location.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}. + ![Create New Repository drop-down](/assets/images/help/repository/repo-create.png) +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Change the current working directory to your local project. +4. Use the `init` command to initialize the local directory as a Git repository. By default, the initial branch is called `master`. + + If you’re using Git 2.28.0 or a later version, you can set the name of the default branch using `-b`. + + ``` shell + $ git init -b main + ``` + + If you’re using Git 2.27.1 or an earlier version, you can set the name of the default branch using `&& git symbolic-ref HEAD refs/heads/main`. + + ``` shell + $ git init && git symbolic-ref HEAD refs/heads/main + ``` +5. Add the files in your new local repository. This stages them for the first commit. ```shell $ git add . # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %} ``` -6. 提交暂存在本地仓库中的文件。 +6. Commit the files that you've staged in your local repository. ```shell $ git commit -m "First commit" # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %} ``` -7. 在仓库顶部 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 的快速设置页面,点击 {% octicon "clippy" aria-label="The copy to clipboard icon" %} 以复制远程仓库 URL。 - ![创建远程存储库 URL 字段](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) -8. 在命令提示中,[添加远程存储库的 URL](/github/getting-started-with-github/managing-remote-repositories)(将在其中推送本地存储库)。 +7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL. + ![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) +8. In the Command prompt, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed. ```shell - $ git remote add origin <REMOTE_URL> + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL ``` -9. [将本地存储库中的更改推送](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)到 {% data variables.product.product_location %}。 +9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.location.product_location %}. ```shell $ git push origin main # Pushes the changes in your local repository up to the remote repository you specified as the origin @@ -131,33 +147,43 @@ ms.locfileid: '145128968' {% linux %} -1. 在 {% data variables.product.product_location %} 上[新建存储库](/articles/creating-a-new-repository)。 为避免错误,请勿使用 README、许可或 `gitignore` 文件初始化新存储库。 您可以在项目推送到 {% data variables.product.product_name %} 之后添加这些文件。 - ![新建存储库下拉菜单](/assets/images/help/repository/repo-create.png) {% data reusables.command_line.open_the_multi_os_terminal %} -3. 将当前工作目录更改为您的本地仓库。 -4. 将本地目录初始化为 Git 仓库。 - ```shell - $ git init -b main - ``` -5. 在新的本地仓库中添加文件。 这会暂存它们用于第一次提交。 +1. [Create a new repository](/articles/creating-a-new-repository) on {% data variables.location.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}. + ![Create New Repository drop-down](/assets/images/help/repository/repo-create.png) +{% data reusables.command_line.open_the_multi_os_terminal %} +3. Change the current working directory to your local project. +4. Use the `init` command to initialize the local directory as a Git repository. By default, the initial branch is called `master`. + + If you’re using Git 2.28.0 or a later version, you can set the name of the default branch using `-b`. + + ``` shell + $ git init -b main + ``` + + If you’re using Git 2.27.1 or an earlier version, you can set the name of the default branch using `&& git symbolic-ref HEAD refs/heads/main`. + + ``` shell + $ git init && git symbolic-ref HEAD refs/heads/main + ``` +5. Add the files in your new local repository. This stages them for the first commit. ```shell $ git add . # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %} ``` -6. 提交暂存在本地仓库中的文件。 +6. Commit the files that you've staged in your local repository. ```shell $ git commit -m "First commit" # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %} ``` -7. 在仓库顶部 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 的快速设置页面,点击 {% octicon "clippy" aria-label="The copy to clipboard icon" %} 以复制远程仓库 URL。 - ![创建远程存储库 URL 字段](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) -8. 在终端中,[添加远程存储库的 URL](/github/getting-started-with-github/managing-remote-repositories)(将在其中推送本地存储库)。 +7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL. + ![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) +8. In Terminal, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed. ```shell - $ git remote add origin <REMOTE_URL> + $ git remote add origin <REMOTE_URL> # Sets the new remote $ git remote -v # Verifies the new remote URL ``` -9. [将本地存储库中的更改推送](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)到 {% data variables.product.product_location %}。 +9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.location.product_location %}. ```shell $ git push origin main # Pushes the changes in your local repository up to the remote repository you specified as the origin @@ -165,6 +191,6 @@ ms.locfileid: '145128968' {% endlinux %} -## 延伸阅读 +## Further reading -- [添加文件到存储库](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line) +- "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)" diff --git a/translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md b/translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md index 50d764eda1..c25bdf5f5c 100644 --- a/translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md +++ b/translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md @@ -1,6 +1,6 @@ --- -title: 使用命令行导入 Git 仓库 -intro: '{% ifversion fpt %}如果 [GitHub 导入工具](/articles/importing-a-repository-with-github-importer)不适用于你的目的,例如,如果你现有的代码托管在私有网络上,则建议使用命令行导入。{% else %}当你现有的代码托管在私有网络上时,适合使用命令行导入 Git 项目。{% endif %}' +title: Importing a Git repository using the command line +intro: '{% ifversion fpt %}If [GitHub Importer](/articles/importing-a-repository-with-github-importer) is not suitable for your purposes, such as if your existing code is hosted on a private network, then we recommend importing using the command line.{% else %}Importing Git projects using the command line is suitable when your existing code is hosted on a private network.{% endif %}' redirect_from: - /articles/importing-a-git-repository-using-the-command-line - /github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line @@ -11,43 +11,37 @@ versions: ghae: '*' ghec: '*' shortTitle: Import repo locally -ms.openlocfilehash: bd3a5e5ffca38250a74851444f6cac4cbb06eb53 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145128967' --- -在开始之前,请确保您知道: +Before you start, make sure you know: -- 您的 {% data variables.product.product_name %} 用户名 -- 外部存储库的克隆 URL,例如 `https://external-host.com/user/repo.git` 或 `git://external-host.com/user/repo.git`(可能 `external-host.com` 域名前面是 `user@`) +- Your {% data variables.product.product_name %} username +- The clone URL for the external repository, such as `https://external-host.com/user/repo.git` or `git://external-host.com/user/repo.git` (perhaps with a `user@` in front of the `external-host.com` domain name) {% tip %} -为便于示范,我们将使用: +For purposes of demonstration, we'll use: -- 外部帐户 extuser -- 外部 Git 主机 `https://external-host.com` -- 名为 ghuser 的 {% data variables.product.product_name %} 个人帐户 -- {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的存储库 repo.git +- An external account named **extuser** +- An external Git host named `https://external-host.com` +- A {% data variables.product.product_name %} personal account named **ghuser** +- A repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} named **repo.git** {% endtip %} -1. [在 {% data variables.product.product_name %} 上新建存储库](/articles/creating-a-new-repository)。 您将在此新仓库中导入外部 Git 仓库。 -2. 在命令行上,使用外部克隆 URL 创建仓库的“裸”克隆。 这会创建数据的完整副本,但没有编辑文件的工作目录,并确保干净、新鲜地导出所有旧数据。 +1. [Create a new repository on {% data variables.product.product_name %}](/articles/creating-a-new-repository). You'll import your external Git repository to this new repository. +2. On the command line, make a "bare" clone of the repository using the external clone URL. This creates a full copy of the data, but without a working directory for editing files, and ensures a clean, fresh export of all the old data. ```shell - $ git clone --bare https://external-host.com/extuser/repo.git + $ git clone --bare https://external-host.com/EXTUSER/REPO.git # Makes a bare clone of the external repository in a local directory ``` -3. 使用“镜像”选项将本地克隆的仓库推送到 {% data variables.product.product_name %},以确保所有引用(如分支和标记)都复制到导入的仓库。 +3. Push the locally cloned repository to {% data variables.product.product_name %} using the "mirror" option, which ensures that all references, such as branches and tags, are copied to the imported repository. ```shell - $ cd repo.git - $ git push --mirror https://{% data variables.command_line.codeblock %}/ghuser/repo.git - # Pushes the mirror to the new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} + $ cd REPO.git + $ git push --mirror https://{% data variables.command_line.codeblock %}/USER/REPO.git + # Pushes the mirror to the new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} ``` -4. 删除临时本地仓库。 +4. Remove the temporary local repository. ```shell $ cd .. - $ rm -rf repo.git + $ rm -rf REPO.git ``` diff --git a/translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md b/translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md index 0f9c06fba5..ab8be9b319 100644 --- a/translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md +++ b/translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md @@ -1,6 +1,6 @@ --- -title: 使用 GitHub 导入工具导入仓库 -intro: 如果您有项目托管在另一个版本控制系统上,可以使用 GitHub 导入工具将其自动导入到 GitHub。 +title: Importing a repository with GitHub Importer +intro: 'If you have a project hosted on another version control system, you can automatically import it to GitHub using the GitHub Importer tool.' redirect_from: - /articles/importing-from-other-version-control-systems-to-github - /articles/importing-a-repository-with-github-importer @@ -10,42 +10,37 @@ versions: fpt: '*' ghec: '*' shortTitle: Use GitHub Importer -ms.openlocfilehash: 09b03d2c2c62cf5812f35a3d5b3379c2d0c8e33e -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145911197' --- {% tip %} -提示:GitHub 导入工具并不适用于所有导入。 例如,如果您现有的代码托管在私有网络上,我们的工具便无法访问。 在这些情况下,我们建议对 Git 存储库[使用命令行导入](/articles/importing-a-git-repository-using-the-command-line),或者对从其他版本控制系统导入的项目使用[源代码迁移工具](/articles/source-code-migration-tools)。 +**Tip:** GitHub Importer is not suitable for all imports. For example, if your existing code is hosted on a private network, our tool won't be able to access it. In these cases, we recommend [importing using the command line](/articles/importing-a-git-repository-using-the-command-line) for Git repositories or an external [source code migration tool](/articles/source-code-migration-tools) for projects imported from other version control systems. {% endtip %} -如果在导入时要将存储库中的提交匹配到作者的 GitHub 个人帐户,请确保在开始导入之前,存储库的每个参与者都有 GitHub 帐户。 +If you'd like to match the commits in your repository to the authors' GitHub personal accounts during the import, make sure every contributor to your repository has a GitHub account before you begin the import. {% data reusables.repositories.repo-size-limit %} -1. 在任何页面的右上角,单击 {% octicon "plus" aria-label="Plus symbol" %},然后单击“导入存储库”。 -![新存储库菜单中的导入存储库选项](/assets/images/help/importer/import-repository.png) -2. 在 "Your old repository's clone URL"(您的旧仓库的克隆 URL)下,输入要导入的项目的 URL。 -![导入的存储库的 URL 对应的文本字段](/assets/images/help/importer/import-url.png) -3. 选择拥有存储库的个人帐户或组织,然后输入 GitHub 上帐户的名称。 -![存储库所有者菜单和存储库名称字段](/assets/images/help/importer/import-repo-owner-name.png) -4. 指定新存储库是“公共”还是“专用” 。 有关详细信息,请参阅[设置存储库可见性](/articles/setting-repository-visibility)。 -![公共或专用存储库单选按钮](/assets/images/help/importer/import-public-or-private.png) -5. 检查你输入的信息,然后单击“开始导入”。 -![“开始导入”按钮](/assets/images/help/importer/begin-import-button.png) -6. 如果你的旧项目需要凭据,请输入该项目的登录信息,然后单击“提交”。 如果在旧项目中为用户帐户启用了 SAML SSO 或 2FA,请在“密码”字段中输入具有存储库读取权限的个人访问令牌,而不是密码。 -![受密码保护项目的密码表单和“提交”按钮](/assets/images/help/importer/submit-old-credentials-importer.png) -7. 如果有多个项目托管在旧项目的克隆 URL 上,请选择要导入的项目,然后单击“提交”。 -![要导入的项目列表和“提交”按钮](/assets/images/help/importer/choose-project-importer.png) -8. 如果项目包含超过 100 MB 的文件,请选择是否使用 [Git 大型文件存储](/articles/versioning-large-files)导入大型文件,然后单击“继续”。 -![“Git 大型文件存储”菜单和“继续”按钮](/assets/images/help/importer/select-gitlfs-importer.png) +1. In the upper-right corner of any page, click {% octicon "plus" aria-label="Plus symbol" %}, and then click **Import repository**. +![Import repository option in new repository menu](/assets/images/help/importer/import-repository.png) +2. Under "Your old repository's clone URL", type the URL of the project you want to import. +![Text field for URL of imported repository](/assets/images/help/importer/import-url.png) +3. Choose your personal account or an organization to own the repository, then type a name for the repository on GitHub. +![Repository owner menu and repository name field](/assets/images/help/importer/import-repo-owner-name.png) +4. Specify whether the new repository should be *public* or *private*. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)." +![Public or private repository radio buttons](/assets/images/help/importer/import-public-or-private.png) +5. Review the information you entered, then click **Begin import**. +![Begin import button](/assets/images/help/importer/begin-import-button.png) +6. If your old project requires credentials, type your login information for that project, then click **Submit**. +If SAML SSO or 2FA are enabled for your user account on the old project, enter a {% data variables.product.pat_generic %} with repository read permissions in the "Password" field instead of your password. +![Password form and Submit button for password-protected project](/assets/images/help/importer/submit-old-credentials-importer.png) +7. If there are multiple projects hosted at your old project's clone URL, choose the project you'd like to import, then click **Submit**. +![List of projects to import and Submit button](/assets/images/help/importer/choose-project-importer.png) +8. If your project contains files larger than 100 MB, choose whether to import the large files using [Git Large File Storage](/articles/versioning-large-files), then click **Continue**. +![Git Large File Storage menu and Continue button](/assets/images/help/importer/select-gitlfs-importer.png) -在仓库完成导入时,您会收到一封电子邮件。 +You'll receive an email when the repository has been completely imported. -## 延伸阅读 +## Further reading -- “[使用 GitHub 导入工具更新提交作者归属](/articles/updating-commit-author-attribution-with-github-importer)” +- "[Updating commit author attribution with GitHub Importer](/articles/updating-commit-author-attribution-with-github-importer)" diff --git a/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md index d0d20d47d6..401194125d 100644 --- a/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md +++ b/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md @@ -62,7 +62,7 @@ To learn about what you need to know to plan your {% data variables.product.prod ## Enabling {% data variables.product.prodname_advanced_security %} features {%- ifversion ghes %} -The site administrator must enable {% data variables.product.prodname_advanced_security %} for {% data variables.product.product_location %} before you can use these features. For more information, see "[Configuring Advanced Security features](/admin/configuration/configuring-advanced-security-features). +The site administrator must enable {% data variables.product.prodname_advanced_security %} for {% data variables.location.product_location %} before you can use these features. For more information, see "[Configuring Advanced Security features](/admin/configuration/configuring-advanced-security-features). Once your system is set up, you can enable and disable these features at the organization or repository level. diff --git a/translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md b/translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md index 8c23fa000c..8967160362 100644 --- a/translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md +++ b/translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md @@ -1,5 +1,5 @@ --- -title: GitHub 上的访问权限 +title: Access permissions on GitHub redirect_from: - /articles/needs-to-be-written-what-can-the-different-types-of-org-team-permissions-do - /articles/what-are-the-different-types-of-team-permissions @@ -7,7 +7,7 @@ redirect_from: - /articles/access-permissions-on-github - /github/getting-started-with-github/access-permissions-on-github - /github/getting-started-with-github/learning-about-github/access-permissions-on-github -intro: '使用角色,您可以控制谁有权访问您在 {% data variables.product.product_name %} 上的帐户和资源,以及每个人拥有的访问权限级别。' +intro: 'With roles, you can control who has access to your accounts and resources on {% data variables.product.product_name %} and the level of access each person has.' versions: fpt: '*' ghes: '*' @@ -17,41 +17,40 @@ topics: - Permissions - Accounts shortTitle: Access permissions -ms.openlocfilehash: 32db1949cbc110559023f719682caed0319aae9e -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145128916' --- -## 关于 {% data variables.product.prodname_dotcom %} 上的访问权限 + +## About access permissions on {% data variables.product.prodname_dotcom %} {% data reusables.organizations.about-roles %} -对于不同类型的帐户,角色的工作方式不同。 有关帐户的详细信息,请参阅“[{% data variables.product.prodname_dotcom %} 帐户类型](/get-started/learning-about-github/types-of-github-accounts)”。 +Roles work differently for different types of accounts. For more information about accounts, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)." -## 个人帐户 +## Personal accounts -个人帐户拥有的存储库有两种权限级别:存储库所有者和协作者 。 有关详细信息,请参阅“[个人帐户存储库的权限级别](/articles/permission-levels-for-a-user-account-repository)”。 +A repository owned by a personal account has two permission levels: the *repository owner* and *collaborators*. For more information, see "[Permission levels for a personal account repository](/articles/permission-levels-for-a-user-account-repository)." -## 组织帐户 +## Organization accounts -组织成员可以拥有所有者{% ifversion fpt or ghec %}、计费管理员{% endif %}或成员角色 。 所有者对组织具有完全管理权限{% ifversion fpt or ghec %},而计费管理员可以管理计费设置{% endif %}。 成员是其他每个人的默认角色。 您可以通过团队一次管理多个成员的访问权限。 有关详细信息,请参阅: -- [组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization) -- [组织的项目委员会权限](/articles/project-board-permissions-for-an-organization) -- [组织的存储库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization) -- [关于团队](/articles/about-teams) +Organization members can have *owner*{% ifversion fpt or ghec %}, *billing manager*,{% endif %} or *member* roles. Owners have complete administrative access to your organization{% ifversion fpt or ghec %}, while billing managers can manage billing settings{% endif %}. Member is the default role for everyone else. You can manage access permissions for multiple members at a time with teams. For more information, see: +- "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" +- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" +- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" +- "[About teams](/articles/about-teams)" -## 企业帐户 +## Enterprise accounts -{% ifversion fpt %} {% data reusables.gated-features.enterprise-accounts %} +{% ifversion fpt %} +{% data reusables.gated-features.enterprise-accounts %} -有关企业帐户权限的详细信息,请参阅 [{% data variables.product.prodname_ghe_cloud %} 文档](/enterprise-cloud@latest/get-started/learning-about-github/access-permissions-on-github)。 -{% else %}企业所有者对企业帐户拥有最终执行权,并且可以在企业帐户中执行所有操作。{% ifversion ghec or ghes %}计费管理员可以管理企业帐户的计费设置。{% endif %}企业帐户所拥有的组织的成员和外部协作者自动成为企业帐户的成员,尽管他们无法访问企业帐户本身或其设置 。 有关详细信息,请参阅“[企业中的角色](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)”。 +For more information about permissions for enterprise accounts, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/access-permissions-on-github). +{% else %} +*Enterprise owners* have ultimate power over the enterprise account and can take every action in the enterprise account.{% ifversion ghec or ghes %} *Billing managers* can manage your enterprise account's billing settings.{% endif %} Members and outside collaborators of organizations owned by your enterprise account are automatically members of the enterprise account, although they have no access to the enterprise account itself or its settings. For more information, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)." -{% ifversion ghec %}如果企业使用 {% data variables.product.prodname_emus %},成员将在 {% data variables.product.prodname_dotcom %} 上预配作为新个人帐户,并由标识提供者完全托管。 {% data variables.product.prodname_managed_users %} 对不属于其企业的存储库具有只读访问权限,并且无法与不是企业成员的用户进行交互。 在企业拥有的组织中,可以向 {% data variables.product.prodname_managed_users %} 授予与常规组织相同的粒度访问级别。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)”。 -{% endif %} {% endif %} +{% ifversion ghec %} +If an enterprise uses {% data variables.product.prodname_emus %}, members are provisioned as new personal accounts on {% data variables.product.prodname_dotcom %} and are fully managed by the identity provider. The {% data variables.enterprise.prodname_managed_users %} have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the {% data variables.enterprise.prodname_managed_users %} can be granted the same granular access levels available for regular organizations. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." +{% endif %} +{% endif %} -## 延伸阅读 +## Further reading -- [{% data variables.product.prodname_dotcom %} 帐户类型](/articles/types-of-github-accounts) +- "[Types of {% data variables.product.prodname_dotcom %} accounts](/articles/types-of-github-accounts)" diff --git a/translations/zh-CN/content/get-started/learning-about-github/types-of-github-accounts.md b/translations/zh-CN/content/get-started/learning-about-github/types-of-github-accounts.md index ded8d0220e..70b4afd8f5 100644 --- a/translations/zh-CN/content/get-started/learning-about-github/types-of-github-accounts.md +++ b/translations/zh-CN/content/get-started/learning-about-github/types-of-github-accounts.md @@ -1,6 +1,6 @@ --- -title: GitHub 帐户类型 -intro: '{% data variables.product.product_name %} 上的帐户允许您组织和控制对代码的访问。' +title: Types of GitHub accounts +intro: 'Accounts on {% data variables.product.product_name %} allow you to organize and control access to code.' redirect_from: - /manage-multiple-clients - /managing-clients @@ -20,69 +20,70 @@ topics: - Mobile - Desktop - Security -ms.openlocfilehash: 9316fcb8b069b0b596c89d10ac1f89d86f1a62b7 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145128892' --- -## 关于 {% data variables.product.product_name %} 上的帐户 -使用 {% data variables.product.product_name %},您可以存储和协作处理代码。 帐户允许您组织和控制对该代码的访问。 {% data variables.product.product_name %} 上有三种类型的帐户。 -- 个人帐户 -- 组织帐户 -- 企业帐户 +## About accounts on {% data variables.product.product_name %} -每个使用 {% data variables.product.product_name %} 的人都登录个人帐户。 组织帐户增强了多个个人帐户之间的协作,{% ifversion fpt or ghec %}企业帐户{% else %}{% data variables.product.product_location %} 的企业帐户{% endif %} 允许集中管理多个组织。 +With {% data variables.product.product_name %}, you can store and collaborate on code. Accounts allow you to organize and control access to that code. There are three types of accounts on {% data variables.product.product_name %}. +- Personal accounts +- Organization accounts +- Enterprise accounts -## 个人帐户 +Every person who uses {% data variables.product.product_name %} signs into a personal account. An organization account enhances collaboration between multiple personal accounts, and {% ifversion fpt or ghec %}an enterprise account{% else %}the enterprise account for {% data variables.location.product_location %}{% endif %} allows central management of multiple organizations. -每个使用 {% data variables.product.product_location %} 的人都登录个人帐户。 您的个人帐户是您在 {% data variables.product.product_location %} 上的身份,并具有用户名和个人资料。 例如,查看 [@octocat 的个人资料](https://github.com/octocat)。 +## Personal accounts -您的个人帐户可以拥有存储库、包和项目等资源。 每当您对 {% data variables.product.product_location %} 执行任何操作(例如创建议题或查看拉取请求)时,该操作都将归因于您的个人帐户。 +Every person who uses {% data variables.location.product_location %} signs into a personal account. Your personal account is your identity on {% data variables.location.product_location %} and has a username and profile. For example, see [@octocat's profile](https://github.com/octocat). -{% ifversion fpt or ghec %}每个个人帐户使用 {% data variables.product.prodname_free_user %} 或 {% data variables.product.prodname_pro %}。 所有个人帐户都可以拥有无限数量的公共和私有存储库,这些存储库上的协作者数量不受限制。 如果您使用 {% data variables.product.prodname_free_user %},则您的个人帐户拥有的私有仓库的功能集有限。 您可以升级到 {% data variables.product.prodname_pro %} 以获取私有仓库的完整功能集。 有关详细信息,请参阅“[{% data variables.product.prodname_dotcom %} 的产品](/articles/githubs-products)”。 {% else %}您可以创建由您的个人帐户拥有的无限数量的存储库,并在这些存储库上拥有无限数量的协作者。{% endif %} +Your personal account can own resources such as repositories, packages, and projects. Any time you take any action on {% data variables.location.product_location %}, such as creating an issue or reviewing a pull request, the action is attributed to your personal account. + +{% ifversion fpt or ghec %}Each personal account uses either {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %}. All personal accounts can own an unlimited number of public and private repositories, with an unlimited number of collaborators on those repositories. If you use {% data variables.product.prodname_free_user %}, private repositories owned by your personal account have a limited feature set. You can upgrade to {% data variables.product.prodname_pro %} to get a full feature set for private repositories. For more information, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)." {% else %}You can create an unlimited number of repositories owned by your personal account, with an unlimited number of collaborators on those repositories.{% endif %} {% tip %} -**提示**:个人帐户预期供人类使用,但你可以创建帐户以自动执行 {% data variables.product.product_name %} 上的活动。 此类型的帐户称为计算机用户。 例如,可以创建计算机用户帐户以自动执行持续集成 (CI) 工作流程。 +**Tip**: Personal accounts are intended for humans, but you can create accounts to automate activity on {% data variables.product.product_name %}. This type of account is called a machine user. For example, you can create a machine user account to automate continuous integration (CI) workflows. {% endtip %} -{% ifversion fpt or ghec %} 大多数人会使用一个个人帐户来完成他们在 {% data variables.product.prodname_dotcom_the_website %} 上的所有工作,包括开源项目和带薪工作。 如果您当前使用多个为自己创建的个人帐户,我们建议您合并这些帐户。 有关详细信息,请参阅“[合并多个个人帐户](/articles/merging-multiple-user-accounts)”。 +{% ifversion fpt or ghec %} +Most people will use one personal account for all their work on {% data variables.product.prodname_dotcom_the_website %}, including both open source projects and paid employment. If you're currently using more than one personal account that you created for yourself, we suggest combining the accounts. For more information, see "[Merging multiple personal accounts](/articles/merging-multiple-user-accounts)." {% endif %} -## 组织帐户 +## Organization accounts -组织是共享帐户,无限数量的人员可以同时跨多个项目进行协作。 +Organizations are shared accounts where an unlimited number of people can collaborate across many projects at once. -与个人帐户一样,组织可以拥有存储库、文件包和项目等资源。 但是,您无法登录到组织。 相反,每个人都登录到自己的个人帐户,并且该人员对组织资源执行的任何操作都将归因于其个人帐户。 每个个人帐户都可以是多个组织的成员。 +Like personal accounts, organizations can own resources such as repositories, packages, and projects. However, you cannot sign into an organization. Instead, each person signs into their own personal account, and any actions the person takes on organization resources are attributed to their personal account. Each personal account can be a member of multiple organizations. -可以为组织中的个人帐户分配组织中的不同角色,这些角色授予对组织及其数据的不同级别的访问权限。 所有成员都可以在存储库和项目中相互协作,但只有组织所有者和安全管理员才能管理组织的设置,并使用复杂的安全和管理功能控制对组织数据的访问。 有关详细信息,请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”和“[保护组织安全](/organizations/keeping-your-organization-secure)”。 +The personal accounts within an organization can be given different roles in the organization, which grant different levels of access to the organization and its data. All members can collaborate with each other in repositories and projects, but only organization owners and security managers can manage the settings for the organization and control access to the organization's data with sophisticated security and administrative features. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" and "[Keeping your organization secure](/organizations/keeping-your-organization-secure)." -![显示用户必须登录到其个人帐户才能访问组织资源的图表](/assets/images/help/overview/sign-in-pattern.png) +![Diagram showing that users must sign in to their personal account to access an organization's resources](/assets/images/help/overview/sign-in-pattern.png) -{% ifversion fpt or ghec %} 即使你是使用 SAML 单一登录的组织的成员,你仍将在 {% data variables.product.prodname_dotcom_the_website %} 登录你自己的个人帐户,并且该个人帐户将链接到你在组织的标识提供者 (IdP) 中的标识。 有关详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[关于使用 SAML 单一登录进行身份验证](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}”{% else %}。"{% endif %} +{% ifversion fpt or ghec %} +Even if you're a member of an organization that uses SAML single sign-on, you will still sign into your own personal account on {% data variables.product.prodname_dotcom_the_website %}, and that personal account will be linked to your identity in your organization's identity provider (IdP). For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation{% else %}."{% endif %} -但是,如果您是使用 {% data variables.product.prodname_emus %} 的企业的成员,而不是使用您创建的个人帐户,则企业的 IdP 将为您预置一个新帐户。 要访问该企业拥有的任何组织,您必须使用其 IdP 而不是 {% data variables.product.prodname_dotcom_the_website %} 用户名和密码进行身份验证。 有关详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[关于 {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}”。{% else %}."{% endif %} {% endif %} +However, if you're a member of an enterprise that uses {% data variables.product.prodname_emus %}, instead of using a personal account that you created, a new account will be provisioned for you by the enterprise's IdP. To access any organizations owned by that enterprise, you must authenticate using their IdP instead of a {% data variables.product.prodname_dotcom_the_website %} username and password. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} +{% endif %} -您还可以创建称为团队的组织成员的嵌套子组,以反映组的结构并简化访问管理。 有关详细信息,请参阅“[关于团队](/organizations/organizing-members-into-teams/about-teams)”。 +You can also create nested sub-groups of organization members called teams, to reflect your group's structure and simplify access management. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)." {% data reusables.organizations.organization-plans %} -有关组织的所有功能的详细信息,请参阅“[关于组织](/organizations/collaborating-with-groups-in-organizations/about-organizations)”。 +For more information about all the features of organizations, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." -## 企业帐户 +## Enterprise accounts -{% ifversion fpt %} {% data variables.product.prodname_ghe_cloud %} 和 {% data variables.product.prodname_ghe_server %} 包括企业帐户,这些帐户允许管理员集中管理多个组织的策略和计费,并在组织之间启用内部资源。 有关详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[关于企业帐户](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)”。 -{% elsif ghec %} 企业帐户允许对多个组织进行集中策略管理和计费。 您可以使用企业帐户集中管理策略和帐单。 与组织不同,企业帐户不能直接拥有存储库、文件包或项目等资源。 这些资源由企业帐户中的组织拥有。 有关详细信息,请参阅“[关于企业帐户](/admin/overview/about-enterprise-accounts)”。 -{% elsif ghes or ghae %} 你的企业帐户是 {% endif %} {% data variables.product.product_location %} 上{% ifversion ghae %}拥有的{% elsif ghes %}所有组织的集合。 您可以使用企业帐户集中管理策略和帐单。 与组织不同,企业帐户不能直接拥有存储库、文件包或项目等资源。 这些资源由企业帐户中的组织拥有。 有关详细信息,请参阅“[关于企业帐户](/admin/overview/about-enterprise-accounts)”。 +{% ifversion fpt %} +{% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} include enterprise accounts, which allow administrators to centrally manage policy and billing for multiple organizations and enable innersourcing between the organizations. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)" in the {% data variables.product.prodname_ghe_cloud %} documentation. +{% elsif ghec %} +Enterprise accounts allow central policy management and billing for multiple organizations. You can use your enterprise account to centrally manage policy and billing. Unlike organizations, enterprise accounts cannot directly own resources like repositories, packages, or projects. These resources are owned by organizations within the enterprise account instead. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)." +{% elsif ghes or ghae %} +Your enterprise account is a collection of all the organizations {% ifversion ghae %}owned by{% elsif ghes %}on{% endif %} {% data variables.location.product_location %}. You can use your enterprise account to centrally manage policy and billing. Unlike organizations, enterprise accounts cannot directly own resources like repositories, packages, or projects. These resources are owned by organizations within the enterprise account instead. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)." {% endif %} -## 延伸阅读 +## Further reading {% ifversion fpt or ghec %} -- “[注册新 {% data variables.product.prodname_dotcom %} 帐户](/articles/signing-up-for-a-new-github-account)”{% endif %} -- “[创建新的组织帐户](/articles/creating-a-new-organization-account)” -- {% data variables.product.company_short %} 资源中的[组织人员成功协作](https://vimeo.com/333786093)视频 +- "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)"{% endif %} +- "[Creating a new organization account](/articles/creating-a-new-organization-account)" +- [Organizing people for successful collaboration](https://vimeo.com/333786093) video in {% data variables.product.company_short %} Resources diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md index 6ff816df16..0717b20b76 100644 --- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md +++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md @@ -1,88 +1,83 @@ --- -title: 开始使用 GitHub AE -intro: '开始为 {% data variables.product.product_location %} 设置和配置 {% data variables.product.product_name %}。' +title: Getting started with GitHub AE +intro: 'Get started with setting up and configuring {% data variables.product.product_name %} for {% data variables.location.product_location %}.' versions: ghae: '*' -ms.openlocfilehash: e83b868b6cd204b7a96f40b7287c017eec90096f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147389969' --- -本指南将引导您作为企业所有者在 {% data variables.product.product_name %} 上完成 {% data variables.product.product_location %} 的设置、配置和管理。 若要了解 {% data variables.product.product_name %} 相关详细信息,请参阅“[关于 {% data variables.product.prodname_ghe_managed %}](/admin/overview/about-github-ae)。” -## 第 1 部分:设置 {% data variables.product.product_name %} -要开始使用 {% data variables.product.product_name %},可以创建企业帐户、初始化 {% data variables.product.product_name %}、配置 IP 允许列表、配置用户身份验证和预配以及管理 {% data variables.product.product_location %} 的计费。 +This guide will walk you through setting up, configuring, and managing settings for {% data variables.location.product_location %} on {% data variables.product.product_name %} as an enterprise owner. For more information about {% data variables.product.product_name %}, see "[About {% data variables.product.prodname_ghe_managed %}](/admin/overview/about-github-ae)." -### 1. 创建你的 {% data variables.product.product_name %} 企业帐户 -您首先需要购买 {% data variables.product.product_name %}。 有关详细信息,请联系 [{% data variables.product.prodname_dotcom %} 的销售团队](https://enterprise.github.com/contact)。 +## Part 1: Setting up {% data variables.product.product_name %} +To get started with {% data variables.product.product_name %}, you can create your enterprise account, initialize {% data variables.product.product_name %}, configure an IP allow list, configure user authentication and provisioning, and manage billing for {% data variables.location.product_location %}. + +### 1. Creating your {% data variables.product.product_name %} enterprise account +You will first need to purchase {% data variables.product.product_name %}. For more information, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). {% data reusables.github-ae.initialize-enterprise %} -### 2. 初始化 {% data variables.product.product_name %} -当 {% data variables.product.company_short %} 在 {% data variables.product.product_name %} 上为 {% data variables.product.product_location %} 创建所有者帐户后,您将收到一封电子邮件,要求您登录并完成初始化。 在初始化期间,作为企业所有者,您将命名 {% data variables.product.product_location %}、配置 SAML SSO、为 {% data variables.product.product_location %} 中的所有组织创建策略,并为企业成员配置支持联系人。 有关详细信息,请参阅“[初始化 {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)”。 +### 2. Initializing {% data variables.product.product_name %} +After {% data variables.product.company_short %} creates the owner account for {% data variables.location.product_location %} on {% data variables.product.product_name %}, you will receive an email to sign in and complete the initialization. During initialization, you, as the enterprise owner, will name {% data variables.location.product_location %}, configure SAML SSO, create policies for all organizations in {% data variables.location.product_location %}, and configure a support contact for your enterprise members. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)." -### 3. 限制网络流量 -您可以为特定 IP 地址配置允许列表,以限制对企业帐户中组织拥有的资产的访问。 有关详细信息,请参阅“[限制到企业的网络流量](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)”。 +### 3. Restricting network traffic +You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)." -### 4. 管理 {% data variables.product.product_location %} 的标识和访问 -您可以使用 SAML 单点登录 (SSO) 进行用户身份验证和跨域身份管理系统 (SCIM) 从身份提供商 (IdP) 集中管理对 {% data variables.product.product_name %} 上 {% data variables.product.product_location %} 的访问。 在配置预配后,您可以从 IdP 分配用户给应用程序或取消分配,从而在企业中创建或禁用用户帐户。 有关详细信息,请参阅“[关于企业标识和访问管理](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)”。 +### 4. Managing identity and access for {% data variables.location.product_location %} +You can centrally manage access to {% data variables.location.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. For more information, see "[About identity and access management for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)." -### 5. 管理 {% data variables.product.product_location %} 的计费 -{% data variables.product.product_name %} 上 {% data variables.product.product_location %} 订阅的所有者可以在 Azure 门户中查看 {% data variables.product.product_name %} 的计费详细信息。 有关详细信息,请参阅“[管理企业的计费](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)”。 +### 5. Managing billing for {% data variables.location.product_location %} +Owners of the subscription for {% data variables.location.product_location %} on {% data variables.product.product_name %} can view billing details for {% data variables.product.product_name %} in the Azure portal. For more information, see "[Managing billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)." -## 第 2 部分:组织和管理企业成员 -作为 {% data variables.product.product_name %} 的企业所有者,您可以管理用户、存储库、团队和组织级别的设置。 您可以管理 {% data variables.product.product_location %} 的成员,创建和管理组织,设置存储库管理策略,以及创建和管理团队。 +## Part 2: Organizing and managing enterprise members +As an enterprise owner for {% data variables.product.product_name %}, you can manage settings on user, repository, team, and organization levels. You can manage members of {% data variables.location.product_location %}, create and manage organizations, set policies for repository management, and create and manage teams. -### 1. 管理 {% data variables.product.product_location %} 的成员 +### 1. Managing members of {% data variables.location.product_location %} {% data reusables.getting-started.managing-enterprise-members %} -### 2. 创建组织 +### 2. Creating organizations {% data reusables.getting-started.creating-organizations %} -### 3. 向组织添加成员 +### 3. Adding members to organizations {% data reusables.getting-started.adding-members-to-organizations %} -### 4. 创建团队 +### 4. Creating teams {% data reusables.getting-started.creating-teams %} -### 5. 设置组织和存储库权限级别 +### 5. Setting organization and repository permission levels {% data reusables.getting-started.setting-org-and-repo-permissions %} -### 6. 实施存储库管理策略 +### 6. Enforcing repository management policies {% data reusables.getting-started.enforcing-repo-management-policies %} -## 第 3 部分:安全构建 -要提高 {% data variables.product.product_location %} 的安全性,您可以监控 {% data variables.product.product_location %},并为组织配置安全性和分析功能。 +## Part 3: Building securely +To increase the security of {% data variables.location.product_location %}, you can monitor {% data variables.location.product_location %} and configure security and analysis features for your organizations. -### 1. 监视 {% data variables.product.product_location %} -您可以使用活动仪表板和审核日志记录监控 {% data variables.product.product_location %}。 有关详细信息,请参阅“[监视企业中的活动](/admin/monitoring-activity-in-your-enterprise)”。 +### 1. Monitoring {% data variables.location.product_location %} +You can monitor {% data variables.location.product_location %} with your activity dashboard and audit logging. For more information, see "[Monitoring activity in your enterprise](/admin/monitoring-activity-in-your-enterprise)." -### 2. 为组织配置安全功能 +### 2. Configuring security features for your organizations {% data reusables.getting-started.configuring-security-features %} -## 第 4 部分:自定义和自动化 {% data variables.product.product_location %} 上的工作 -您可以使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API、{% data variables.product.prodname_actions %}和 {% data variables.product.prodname_pages %}{% data variables.product.product_location %} 自定义和自动化组织中的工作。 +## Part 4: Customizing and automating work on {% data variables.location.product_location %} +You can customize and automate work in organizations in {% data variables.location.product_location %} with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, and {% data variables.product.prodname_pages %}. -### 1. 使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API +### 1. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API {% data reusables.getting-started.api %} -### 2. 生成 {% data variables.product.prodname_actions %} +### 2. Building {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -有关为 {% data variables.product.product_name %} 启用和配置 {% data variables.product.prodname_actions %} 的详细信息,请参阅“[{% data variables.product.prodname_ghe_managed %} 的 {% data variables.product.prodname_actions %} 入门](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)”。 +For more information on enabling and configuring {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)." -### 3. 使用 {% data variables.product.prodname_pages %} +### 3. Using {% data variables.product.prodname_pages %} {% data reusables.getting-started.github-pages-enterprise %} -## 第 5 部分:使用 {% data variables.product.prodname_dotcom %} 的学习和支持资源 -您的企业成员可以通过我们的学习资源了解有关 Git 和 {% data variables.product.prodname_dotcom %} 的更多信息,您也可以通过 {% data variables.product.prodname_dotcom %} Enterprise 支持获得所需的支持。 +## Part 5: Using {% data variables.product.prodname_dotcom %}'s learning and support resources +Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need with {% data variables.product.prodname_dotcom %} Enterprise Support. -### 1. 在 {% data variables.product.prodname_docs %} 上阅读 {% data variables.product.product_name %} -您可以阅读反映 {% data variables.product.prodname_ghe_managed %} 可用功能的文档。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_docs %} 的版本](/get-started/learning-about-github/about-versions-of-github-docs)”。 +### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %} +You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_managed %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." -### 2. 通过 {% data variables.product.prodname_learning %} 学习 +### 2. Learning with {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning-enterprise %} -### 3. 使用 {% data variables.product.prodname_dotcom %} Enterprise 支持 +### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support {% data reusables.getting-started.contact-support-enterprise %} diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index bccc6811e2..8d918c17ca 100644 --- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -1,223 +1,218 @@ --- -title: 开始使用 GitHub Enterprise Cloud -intro: '开始设置和管理 {% data variables.product.prodname_ghe_cloud %} 组织或企业帐户。' +title: Getting started with GitHub Enterprise Cloud +intro: 'Get started with setting up and managing your {% data variables.product.prodname_ghe_cloud %} organization or enterprise account.' versions: fpt: '*' ghec: '*' -ms.openlocfilehash: 249c89ad65bf9a9fc0140b8fb48e7bd0530ff594 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147389961' --- -本指南将引导您以组织或企业所有者的身份设置、配置和管理您的 {% data variables.product.prodname_ghe_cloud %} 帐户。 + +This guide will walk you through setting up, configuring and managing your {% data variables.product.prodname_ghe_cloud %} account as an organization or enterprise owner. {% data reusables.enterprise.ghec-cta-button %} -## 第 1 部分:选择您的帐户类型 +## Part 1: Choosing your account type -{% data variables.product.prodname_dotcom %} 提供两种类型的企业产品: +{% data variables.product.prodname_dotcom %} provides two types of Enterprise products: -- {% data variables.product.prodname_ghe_cloud %} -- {% data variables.product.prodname_ghe_server %} +- **{% data variables.product.prodname_ghe_cloud %}** +- **{% data variables.product.prodname_ghe_server %}** -产品之间的主要区别在于 {% data variables.product.prodname_ghe_cloud %} 由 {% data variables.product.prodname_dotcom %} 托管,而 {% data variables.product.prodname_ghe_server %} 是自托管的。 +The main difference between the products is that {% data variables.product.prodname_ghe_cloud %} is hosted by {% data variables.product.prodname_dotcom %}, while {% data variables.product.prodname_ghe_server %} is self-hosted. {% data reusables.enterprise.about-github-for-enterprises %} -使用 {% data variables.product.prodname_ghe_cloud %},您可以选择 使用 {% data variables.product.prodname_emus %}。 {% data reusables.enterprise-accounts.emu-short-summary %} +With {% data variables.product.prodname_ghe_cloud %}, you have the option of using {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %} -如果你选择让成员创建和管理自己的个人帐户,可以将两种类型的帐户与 {% data variables.product.prodname_ghe_cloud %} 一起使用: +If you choose to let your members create and manage their own personal accounts instead, there are two types of accounts you can use with {% data variables.product.prodname_ghe_cloud %}: -- 单个组织帐户 -- 包含多个组织的企业帐户 +- A single organization account +- An enterprise account that contains multiple organizations -### 1. 了解组织帐户和企业帐户之间的差异 +### 1. Understanding the differences between an organization account and enterprise account -组织和企业帐户都可用于 {% data variables.product.prodname_ghe_cloud %}。 组织是一个共享帐户,其中一组人员可以同时跨多个项目进行协作,所有者和管理员可以管理对数据和项目的访问权限。 企业帐户支持多个组织之间的协作,并允许所有者集中管理这些组织的策略、计费和安全性。 有关差异的详细信息,请参阅[组织和企业帐户](/organizations/collaborating-with-groups-in-organizations/about-organizations#organizations-and-enterprise-accounts)。 +Both organization and enterprise accounts are available with {% data variables.product.prodname_ghe_cloud %}. An organization is a shared account where groups of people can collaborate across many projects at once, and owners and administrators can manage access to data and projects. An enterprise account enables collaboration between multiple organizations, and allows owners to centrally manage policy, billing and security for these organizations. For more information on the differences, see "[Organizations and enterprise accounts](/organizations/collaborating-with-groups-in-organizations/about-organizations#organizations-and-enterprise-accounts)." -如果选择企业帐户,请记住,某些策略只能在组织级别设置,而其他策略可以针对企业中的所有组织强制执行。 +If you choose an enterprise account, keep in mind that some policies can be set only at an organization level, while others can be enforced for all organizations in an enterprise. -选择所需的帐户类型后,您可以继续设置帐户。 在本指南的每个部分中,根据您的帐户类型转到单个组织或企业帐户部分。 +Once you choose the account type you would like, you can proceed to setting up your account. In each of the sections in this guide, proceed to either the single organization or enterprise account section based on your account type. -## 第 2 部分:设置您的帐户 -要开始使用 {% data variables.product.prodname_ghe_cloud %},需要创建组织或企业帐户,并设置和查看计费设置、订阅和使用情况。 -### 使用 {% data variables.product.prodname_ghe_cloud %} 设置单个组织帐户 +## Part 2: Setting up your account +To get started with {% data variables.product.prodname_ghe_cloud %}, you will want to create your organization or enterprise account and set up and view billing settings, subscriptions and usage. +### Setting up a single organization account with {% data variables.product.prodname_ghe_cloud %} -#### 1. 关于组织 -组织是共享帐户,供多个项目的人员同时协作之用。 借助 {% data variables.product.prodname_ghe_cloud %},所有者和管理员可以通过复杂的用户身份验证和管理以及升级的支持和安全选项来管理其组织。 有关详细信息,请参阅[关于组织](/organizations/collaborating-with-groups-in-organizations/about-organizations)。 -#### 2. 创建或升级组织帐户 +#### 1. About organizations +Organizations are shared accounts where groups of people can collaborate across many projects at once. With {% data variables.product.prodname_ghe_cloud %}, owners and administrators can manage their organization with sophisticated user authentication and management, as well as escalated support and security options. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." +#### 2. Creating or upgrading an organization account -要将组织帐户与 {% data variables.product.prodname_ghe_cloud %} 配合使用,您首先需要创建一个组织。 当系统提示您选择计划时,选择“企业”。 有关详细信息,请参阅[从头开始创建新组织](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)。 +To use an organization account with {% data variables.product.prodname_ghe_cloud %}, you will first need to create an organization. When prompted to choose a plan, select "Enterprise". For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." -或者,如果你有想要升级的现有组织帐户,请按照[升级 {% data variables.product.prodname_dotcom %} 订阅](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)中的步骤操作。 -#### 3. 设置和管理计费 +Alternatively, if you have an existing organization account that you would like to upgrade, follow the steps in "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)." +#### 3. Setting up and managing billing -如果选择将组织帐户与 {% data variables.product.prodname_ghe_cloud %} 配合使用,你将首先有权访问 [30 天试用版](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)。 如果您在试用期结束前未购买 {% data variables.product.prodname_enterprise %} 或 {% data variables.product.prodname_team %} ,您的组织将被降级为 {% data variables.product.prodname_free_user %},并且无法访问仅付费产品中包含的任何高级工具和功能。 有关详细信息,请参阅[完成试用](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)。 +When you choose to use an organization account with {% data variables.product.prodname_ghe_cloud %}, you'll first have access to a [30-day trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud). If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_user %} and lose access to any advanced tooling and features that are only included with paid products. For more information, see "[Finishing your trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)." -通过组织的计费设置页面,可以管理付款方式和计费周期等设置、查看有关订阅的信息以及升级存储空间和 {% data variables.product.prodname_actions %} 分钟数。 有关管理计费设置的详细信息,请参阅[管理 {% data variables.product.prodname_dotcom %} 计费设置](/billing/managing-your-github-billing-settings)。 +Your organization's billing settings page allows you to manage settings like your payment method and billing cycle, view information about your subscription, and upgrade your storage and {% data variables.product.prodname_actions %} minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)." -只有具有所有者或计费管理员角色的组织成员才能访问或更改组织的计费设置 。 帐单管理员是管理组织的计费设置的用户,不在组织的订阅中使用付费许可证。 有关将计费管理员添加到组织的详细信息,请参阅[为组织添加计费管理员](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)。 +Only organization members with the *owner* or *billing manager* role can access or change billing settings for your organization. A billing manager is a user who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)." -### 使用 {% data variables.product.prodname_ghe_cloud %} 设置企业帐户 +### Setting up an enterprise account with {% data variables.product.prodname_ghe_cloud %} -#### 1. 关于企业帐户 +#### 1. About enterprise accounts -企业帐户允许您集中管理多个 {% data variables.product.prodname_dotcom %} 组织的策略和设置,包括成员访问、计费、使用情况和安全性。 有关详细信息,请参阅[关于企业帐户](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)。 +An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)." -#### 2. 创建企业帐户 +#### 2. Creating an enterpise account - 通过发票付款的 {% data variables.product.prodname_ghe_cloud %} 客户可以直接通过 {% data variables.product.prodname_dotcom %} 创建企业帐户。 有关详细信息,请参阅“[创建企业帐户](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)”。 + {% data variables.product.prodname_ghe_cloud %} customers paying by invoice can create an enterprise account directly through {% data variables.product.prodname_dotcom %}. For more information, see "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)." - 目前未通过发票付款的 {% data variables.product.prodname_ghe_cloud %} 客户可以联系 [{% data variables.product.prodname_dotcom %} 的销售团队](https://enterprise.github.com/contact)为你创建企业帐户。 + {% data variables.product.prodname_ghe_cloud %} customers not currently paying by invoice can contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact) to create an enterprise account for you. -#### 3. 将组织添加到企业帐户 +#### 3. Adding organizations to your enterprise account -您可以在企业帐户中创建要管理的新组织。 有关详细信息,请参阅[将组织添加到企业](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)。 +You can create new organizations to manage within your enterprise account. For more information, see "[Adding organizations to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)." -如果要将现有组织转移到企业帐户,请与 {% data variables.product.prodname_dotcom %} 销售客户代表联系。 -#### 4. 查看企业帐户的订阅和使用情况 -您可以随时查看企业帐户的当前订阅、许可证使用情况、发票、付款历史记录和其他帐单信息。 企业所有者和帐单管理员都可以访问和管理企业帐户的帐单设置。 有关详细信息,请参阅[查看企业帐户的订阅和使用情况](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)。 +Contact your {% data variables.product.prodname_dotcom %} sales account representative if you want to transfer an existing organization to your enterprise account. +#### 4. Viewing the subscription and usage for your enterprise account +You can view your current subscription, license usage, invoices, payment history, and other billing information for your enterprise account at any time. Both enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Viewing the subscription and usage for your enterprise account](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)." -## 第 3 部分:使用 {% data variables.product.prodname_ghe_cloud %} 管理组织或企业成员和团队 +## Part 3: Managing your organization or enterprise members and teams with {% data variables.product.prodname_ghe_cloud %} -### 管理组织中的成员和团队 -您可以设置权限和成员角色,创建和管理团队,并授予人员访问组织中存储库的权限。 -#### 1. 管理组织成员 +### Managing members and teams in your organization +You can set permissions and member roles, create and manage teams, and give people access to repositories in your organization. +#### 1. Managing members of your organization {% data reusables.getting-started.managing-org-members %} -#### 2. 组织权限和角色 +#### 2. Organization permissions and roles {% data reusables.getting-started.org-permissions-and-roles %} -#### 3. 关于和创建团队 +#### 3. About and creating teams {% data reusables.getting-started.about-and-creating-teams %} -#### 4. 管理团队设置 +#### 4. Managing team settings {% data reusables.getting-started.managing-team-settings %} -#### 5. 为人员和团队提供对存储库、项目板和应用的访问权限 +#### 5. Giving people and teams access to repositories, project boards and apps {% data reusables.getting-started.giving-access-to-repositories-projects-apps %} -### 管理企业帐户的成员 -管理企业成员与管理组织中的成员或团队是分开的。 请务必注意,企业所有者或管理员无法访问组织级设置或管理其企业中组织的成员,除非他们成为组织所有者。 有关详细信息,请参阅上面的[管理组织中的成员和团队](#managing-members-and-teams-in-your-organization)部分。 +### Managing members of an enterprise account +Managing members of an enterprise is separate from managing members or teams in an organization. It is important to note that enterprise owners or administrators cannot access organization-level settings or manage members for organizations in their enterprise unless they are made an organization owner. For more information, see the above section, "[Managing members and teams in your organization](#managing-members-and-teams-in-your-organization)." -如果您的企业使用 {% data variables.product.prodname_emus %},则您的成员将通过您的身份提供商进行完全管理。 添加成员、更改其成员身份以及分配角色都是使用您的 IdP 进行管理的。 有关详细信息,请参阅[关于 {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)。 +If your enterprise uses {% data variables.product.prodname_emus %}, your members are fully managed through your identity provider. Adding members, making changes to their membership, and assigning roles is all managed using your IdP. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." -如果您的企业不使用 {% data variables.product.prodname_emus %},请按照以下步骤操作。 +If your enterprise does not use {% data variables.product.prodname_emus %}, follow the steps below. -#### 1. 在企业中分配角色 -默认情况下,企业中的每个人都是企业的成员。 还有一些管理角色,包括企业所有者和帐单管理员,它们对企业设置和数据具有不同级别的访问权限。 有关详细信息,请参阅[企业中的角色](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)。 -#### 2. 邀请人员管理企业 -您可以邀请人员以企业所有者或帐单管理员的身份管理您的企业,也可以删除不再需要访问权限的人员。 有关详细信息,请参阅[邀请人员管理企业](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)。 +#### 1. Assigning roles in an enterprise +By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. For more information, see "[Roles in an enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)." +#### 2. Inviting people to manage your enterprise +You can invite people to manage your enterprise as enterprise owners or billing managers, as well as remove those who no longer need access. For more information, see "[Inviting people to manage your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)." -您还可以授予企业成员在支持门户中管理支持工单的能力。 有关详细信息,请参阅[管理企业的支持权利](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)。 -#### 3. 查看企业中的人员 -要审核对企业拥有的资源或用户许可证使用情况的访问,可以查看企业中的每个企业管理员、企业成员和外部协作者。 您可以查看成员所属的组织以及外部协作者有权访问的特定存储库。 有关详细信息,请参阅[查看企业中的人员](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)。 +You can also grant enterprise members the ability to manage support tickets in the support portal. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)." +#### 3. Viewing people in your enterprise +To audit access to enterprise-owned resources or user license usage, you can view every enterprise administrator, enterprise member, and outside collaborator in your enterprise. You can see the organizations that a member belongs to and the specific repositories that an outside collaborator has access to. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)." -## 第 4 部分:使用 {% data variables.product.prodname_ghe_cloud %} 管理安全性 +## Part 4: Managing security with {% data variables.product.prodname_ghe_cloud %} -* [管理单个组织的安全性](#managing-security-for-a-single-organization) -* [管理 {% data variables.product.prodname_emu_enterprise %} 的安全性](#managing-security-for-an-enterprise-with-managed-users) -* [在没有 {% data variables.product.prodname_managed_users %} 的情况下管理企业帐户的安全性](#managing-security-for-an-enterprise-account-without-managed-users) +* [Managing security for a single organization](#managing-security-for-a-single-organization) +* [Managing security for an {% data variables.enterprise.prodname_emu_enterprise %}](#managing-security-for-an-enterprise-with-managed-users) +* [Managing security for an enterprise account without {% data variables.enterprise.prodname_managed_users %}](#managing-security-for-an-enterprise-account-without-managed-users) -### 管理单个组织的安全性 -通过要求双重身份验证、配置安全功能、查看组织的审核日志和集成以及启用 SAML 单点登录和团队同步,可以帮助确保组织的安全。 -#### 1. 需要双因素身份验证 +### Managing security for a single organization +You can help keep your organization secure by requiring two-factor authentication, configuring security features, reviewing your organization's audit log and integrations, and enabling SAML single sign-on and team synchronization. +#### 1. Requiring two-factor authentication {% data reusables.getting-started.requiring-2fa %} -#### 2. 为组织配置安全功能 +#### 2. Configuring security features for your organization {% data reusables.getting-started.configuring-security-features %} -#### 3. 查看组织的审核日志和集成 +#### 3. Reviewing your organization's audit log and integrations {% data reusables.getting-started.reviewing-org-audit-log-and-integrations %} -#### 4. 为组织启用和强制实施 SAML 单一登录 -如果您使用身份提供商 (IdP) 管理应用程序和组织成员的身份,则可以配置 SAML 单点登录 (SSO) 来控制和保护对组织资源(如存储库、议题和拉取请求)的访问。 当您的组织成员访问使用 SAML SSO 的组织资源时,{% data variables.product.prodname_dotcom %} 会将其重定向到您的 IdP 进行身份验证。 有关详细信息,请参阅[关于使用 SAML 单一登录进行标识和访问管理](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)。 +#### 4. Enabling and enforcing SAML single sign-on for your organization +If you manage your applications and the identities of your organization members with an identity provider (IdP), you can configure SAML single-sign-on (SSO) to control and secure access to organization resources like repositories, issues and pull requests. When members of your organization access organization resources that use SAML SSO, {% data variables.product.prodname_dotcom %} will redirect them to your IdP to authenticate. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." -组织所有者可以选择禁用、启用但不强制实施,或者启用并强制实施 SAML SSO。 有关详细信息,请参阅[为组织启用和测试 SAML 单一登录](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)和[为组织强制实施 SAML 单一登录](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)。 -#### 5. 管理组织的团队同步 -组织所有者可以在您的身份提供商 (IdP) 和 {% data variables.product.prodname_dotcom %} 之间启用团队同步,以允许组织所有者和团队维护员将组织中的团队与 IdP 组连接起来。 有关详细信息,请参阅[管理组织的团队同步](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)。 +Organization owners can choose to disable, enable but not enforce, or enable and enforce SAML SSO. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)" and "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)." +#### 5. Managing team synchronization for your organization +Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)." -### 管理 {% data variables.product.prodname_emu_enterprise %} 的安全性 +### Managing security for an {% data variables.enterprise.prodname_emu_enterprise %} -有了 {% data variables.product.prodname_emus %},可通过身份提供商集中管理访问和身份。 应在您的 IdP 上启用并强制实施双重身份验证和其他登录要求。 +With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP. -#### 1. 在 {% data variables.product.prodname_emu_enterprise %} 中启用和 SAML 单一登录和预配 +#### 1. Enabling and SAML single sign-on and provisioning in your {% data variables.enterprise.prodname_emu_enterprise %} -在 {% data variables.product.prodname_emu_enterprise %} 中,所有成员都由身份提供商配置和管理。 您必须先启用 SAML SSO 和 SCIM 预配,然后才能开始使用企业。 有关为 {% data variables.product.prodname_emu_enterprise %} 配置 SAML SSO 和预配的详细信息,请参阅[为企业托管用户配置 SAML 单一登录](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)。 +In an {% data variables.enterprise.prodname_emu_enterprise %}, all members are provisioned and managed by your identity provider. You must enable SAML SSO and SCIM provisioning before you can start using your enterprise. For more information on configuring SAML SSO and provisioning for an {% data variables.enterprise.prodname_emu_enterprise %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." -#### 2. 使用标识提供者管理 {% data variables.product.prodname_emu_enterprise %} 中的团队 +#### 2. Managing teams in your {% data variables.enterprise.prodname_emu_enterprise %} with your identity provider -您可以将组织中的团队连接到身份提供商中的安全组,管理团队的成员身份以及通过 IdP 访问存储库。 有关详细信息,请参阅[使用标识提供者组管理团队成员身份](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)。 +You can connect teams in your organizations to security groups in your identity provider, managing membership of your teams and access to repositories through your IdP. For more information, see "[Managing team memberships with identity provider groups](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." -#### 3. 管理 {% data variables.product.prodname_emu_enterprise %} 中允许用于组织的 IP 地址 +#### 3. Managing allowed IP addresses for organizations in your {% data variables.enterprise.prodname_emu_enterprise %} -您可以为特定 IP 地址配置允许列表,以限制对 {% data variables.product.prodname_emu_enterprise %} 中组织拥有的资产的访问。 有关详细信息,请参阅[为企业中的安全设置强制实施策略](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise) +You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your {% data variables.enterprise.prodname_emu_enterprise %}. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)." -#### 4. 在 {% data variables.product.prodname_emu_enterprise %} 中强制实施高级安全功能的策略 +#### 4. Enforcing policies for Advanced Security features in your {% data variables.enterprise.prodname_emu_enterprise %} {% data reusables.getting-started.enterprise-advanced-security %} -### 在没有 {% data variables.product.prodname_managed_users %} 的情况下管理企业帐户的安全性 -要管理企业的安全性,可以要求双重身份验证、管理允许的 IP 地址、在企业级别启用 SAML 单点登录和团队同步,以及注册并强制实施 GitHub 高级安全功能。 +### Managing security for an enterprise account without {% data variables.enterprise.prodname_managed_users %} +To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features. -#### 1. 要求对企业帐户中的组织进行双因素身份验证并管理允许的 IP 地址 -企业所有者可以要求企业帐户拥有的所有组织中的组织成员、帐单管理员和外部协作者使用双重身份验证来保护其个人帐户。 在此之前,我们建议通知所有能够访问企业中组织的人。 您还可以为特定 IP 地址配置允许列表,以限制对企业帐户中组织拥有的资产的访问。 +#### 1. Requiring two-factor authentication and managing allowed IP addresses for organizations in your enterprise account +Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise account use two-factor authentication to secure their personal accounts. Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. -有关强制实施双因素身份验证和允许的 IP 地址列表的详细信息,请参阅[在企业中强制实施安全设置策略](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)。 -#### 2. 为企业帐户中的组织启用和强制实施 SAML 单一登录 -您可以使用 IdP 和 SAM 单点登录 (SSO) 集中管理对企业资源、组织成员身份和团队成员身份的访问权限。 企业所有者可以在企业帐户拥有的所有组织中启用 SAML SSO。 有关详细信息,请参阅[关于企业标识和访问管理](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)。 +For more information on enforcing two-factor authentication and allowed IP address lists, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)." +#### 2. Enabling and enforcing SAML single sign-on for organizations in your enterprise account +You can centrally manage access to your enterprise's resources, organization membership and team membership using your IdP and SAM single sign-on (SSO). Enterprise owners can enable SAML SSO across all organizations owned by an enterprise account. For more information, see "[About identity and access management for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)." -#### 3. 管理团队同步 -您可以启用和管理身份提供商 (IdP) 与 {% data variables.product.prodname_dotcom %} 之间的团队同步,以允许您的企业帐户拥有的组织管理 IdP 组的团队成员身份。 有关详细信息,请参阅[管理企业帐户中组织的团队同步](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise) +#### 3. Managing team synchronization +You can enable and manage team synchronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. For more information, see "[Managing team synchronization for organizations in your enterprise account](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)." -#### 4. 在企业帐户中强制实施高级安全功能的策略 +#### 4. Enforcing policies for Advanced Security features in your enterprise account {% data reusables.getting-started.enterprise-advanced-security %} -## 第 5 部分:管理组织和企业级策略和设置 +## Part 5: Managing organization and enterprise level policies and settings -### 管理单个组织的设置 -要管理和审核组织,可以设置组织策略、管理存储库更改的权限以及使用组织级别的社区健康文件。 -#### 1. 管理组织策略 +### Managing settings for a single organization +To manage and moderate your organization, you can set organization policies, manage permissions for repository changes, and use organization-level community health files. +#### 1. Managing organization policies {% data reusables.getting-started.managing-org-policies %} -#### 2. 管理存储库更改 +#### 2. Managing repository changes {% data reusables.getting-started.managing-repo-changes %} -#### 3. 使用组织级别的社区运行状况文件和审查工具 +#### 3. Using organization-level community health files and moderation tools {% data reusables.getting-started.using-org-community-files-and-moderation-tools %} -### 管理企业帐户的设置 -要管理和主持企业,可以为企业中的组织设置策略、查看审核日志、配置 web 挂钩以及限制电子邮件通知。 -#### 1. 管理企业帐户中组织的策略 +### Managing settings for an enterprise account +To manage and moderate your enterprise, you can set policies for organizations within the enterprise, view audit logs, configure webhooks, and restrict email notifications. +#### 1. Managing policies for organizations in your enterprise account -您可以选择为企业拥有的所有组织强制实施多个策略,也可以选择允许在每个组织中设置这些策略。 您可以强制实施的策略类型包括存储库管理、项目板和团队策略。 有关详细信息,请参阅[为企业设置策略](/enterprise-cloud@latest/admin/policies)。 -#### 2. 查看审核日志、配置 Webhook 以及限制企业的电子邮件通知 -您可以在企业审核日志中查看企业帐户拥有的所有组织的操作。 您还可以将 web 挂钩配置为从企业帐户拥有的组织接收事件。 有关详细信息,请参阅[查看企业的审核日志](/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)和[监视企业](/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise)。 +You can choose to enforce a number of policies for all organizations owned by your enterprise, or choose to allow these policies to be set in each organization. Types of policies you can enforce include repository management, project board, and team policies. For more information, see "[Setting policies for your enterprise](/enterprise-cloud@latest/admin/policies)." +#### 2. Viewing audit logs, configuring webhooks, and restricting email notifications for your enterprise +You can view actions from all of the organizations owned by your enterprise account in the enterprise audit log. You can also configure webhooks to receive events from organizations owned by your enterprise account. For more information, see "[Reviewing audit logs for your enterprise](/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)" and "[Monitoring your enterprise](/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise)." -您还可以限制企业帐户的电子邮件通知,以便企业成员只能使用已验证或已批准的域中的电子邮件地址来接收通知。 有关详细信息,请参阅[限制企业的电子邮件通知](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)。 +You can also restrict email notifications for your enterprise account so that enterprise members can only use an email address in a verified or approved domain to receive notifications. For more information, see "[Restricting email notifications for your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)." -## 第 6 部分:自定义和自动化组织或企业在 {% data variables.product.prodname_dotcom %} 上的工作 -组织或企业的成员可以使用 {% data variables.product.prodname_marketplace %}、{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 中的工具以及现有的 {% data variables.product.product_name %} 功能来自定义和自动化工作。 +## Part 6: Customizing and automating your organization or enterprise's work on {% data variables.product.prodname_dotcom %} +Members of your organization or enterprise can use tools from the {% data variables.product.prodname_marketplace %}, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, and existing {% data variables.product.product_name %} features to customize and automate your work. -### 1. 使用 {% data variables.product.prodname_marketplace %} +### 1. Using {% data variables.product.prodname_marketplace %} {% data reusables.getting-started.marketplace %} -### 2. 使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API +### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API {% data reusables.getting-started.api %} -### 3. 生成 {% data variables.product.prodname_actions %} +### 3. Building {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -### 4. 发布和管理 {% data variables.product.prodname_registry %} +### 4. Publishing and managing {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} -### 5. 使用 {% data variables.product.prodname_pages %} -{% data variables.product.prodname_pages %} 是一项静态站点托管服务,它直接从存储库获取 HTML、CSS 和 JavaScript 文件并发布网站。 您可以在组织级别管理 {% data variables.product.prodname_pages %} 站点的发布。 有关详细信息,请参阅[为组织管理 {% data variables.product.prodname_pages %} 站点的发布](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)和[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)。 -## 第 7 部分:参与 {% data variables.product.prodname_dotcom %} 的社区 +### 5. Using {% data variables.product.prodname_pages %} +{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository and publishes a website. You can manage the publication of {% data variables.product.prodname_pages %} sites at the organization level. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" and "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)." +## Part 7: Participating in {% data variables.product.prodname_dotcom %}'s community -组织或企业的成员可以使用 GitHub 的学习和支持资源来获得所需的帮助。 您还可以支持开源社区。 +Members of your organization or enterprise can use GitHub's learning and support resources to get the help they need. You can also support the open source community. -### 1. 阅读 {% data variables.product.prodname_docs %} 上的 {% data variables.product.prodname_ghe_cloud %} -您可以阅读反映 {% data variables.product.prodname_ghe_cloud %} 可用功能的文档。 有关详细信息,请参阅[关于 {% data variables.product.prodname_docs %} 的版本](/get-started/learning-about-github/about-versions-of-github-docs)。 +### 1. Reading about {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_docs %} +You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." -### 2. 通过 {% data variables.product.prodname_learning %} 学习 -组织或企业的成员可以通过在自己的 GitHub 存储库中使用 [{% data variables.product.prodname_learning %}](https://skills.github.com/) 完成有趣、逼真的项目来学习新技能。 每门课程都是由 GitHub 社区创建并由友好的机器人教授的实践课程。 +### 2. Learning with {% data variables.product.prodname_learning %} +Members of your organization or enterprise can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://skills.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by a friendly bot. -有关详细信息,请参阅 [Git 和 {% data variables.product.prodname_dotcom %} 学习资源](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)。 -### 3. 支持开放源代码社区 +For more information, see "[Git and {% data variables.product.prodname_dotcom %} learning resources](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)." +### 3. Supporting the open source community {% data reusables.getting-started.sponsors %} -### 4. 联系 {% data variables.contact.github_support %} +### 4. Contacting {% data variables.contact.github_support %} {% data reusables.getting-started.contact-support %} -{% data variables.product.prodname_ghe_cloud %} 允许您以八小时的目标响应时间提交优先支持请求。 有关详细信息,请参阅 [{% data variables.product.prodname_ghe_cloud %} 支持](/github/working-with-github-support/github-enterprise-cloud-support)。 +{% data variables.product.prodname_ghe_cloud %} allows you to submit priority support requests with a target eight-hour response time. For more information, see "[{% data variables.product.prodname_ghe_cloud %} support](/github/working-with-github-support/github-enterprise-cloud-support)." diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md index ebd927dcf8..5f749b66af 100644 --- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md +++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md @@ -1,130 +1,126 @@ --- -title: 开始使用 GitHub Enterprise Server -intro: '开始设置和管理 {% data variables.product.product_location %}。' +title: Getting started with GitHub Enterprise Server +intro: 'Get started with setting up and managing {% data variables.location.product_location %}.' versions: ghes: '*' -ms.openlocfilehash: 01ed16fd08a57e96270ed1cc577784ba52a15dbf -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146454267' --- -本指南将引导您以企业管理员身份设置、配置和管理 {% data variables.product.product_location %}。 -{% data variables.product.company_short %} 提供了两种部署 {% data variables.product.prodname_enterprise %} 的方法。 +This guide will walk you through setting up, configuring and managing {% data variables.location.product_location %} as an enterprise administrator. -- {% data variables.product.prodname_ghe_cloud %} -- {% data variables.product.prodname_ghe_server %} +{% data variables.product.company_short %} provides two ways to deploy {% data variables.product.prodname_enterprise %}. -{% data variables.product.company_short %} 托管 {% data variables.product.prodname_ghe_cloud %}。 可以在自己的数据中心或受支持的云提供商中部署和托管 {% data variables.product.prodname_ghe_server %} 。 +- **{% data variables.product.prodname_ghe_cloud %}** +- **{% data variables.product.prodname_ghe_server %}** -有关 {% data variables.product.product_name %} 的详细信息,请参阅“[关于 {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server)”。 +{% data variables.product.company_short %} hosts {% data variables.product.prodname_ghe_cloud %}. You can deploy and host {% data variables.product.prodname_ghe_server %} in your own datacenter or a supported cloud provider. -## 第 1 部分:安装 {% data variables.product.product_name %} -要开始使用 {% data variables.product.product_name %},您需要创建企业帐户、安装实例、使用管理控制台进行初始设置、配置实例和管理帐单。 -### 1. 创建企业帐户 -在安装 {% data variables.product.product_name %} 之前,可以通过联系 [{% data variables.product.prodname_dotcom %} 的销售团队](https://enterprise.github.com/contact)在 {% data variables.product.prodname_dotcom_the_website %} 上创建一个企业帐户。 {% data variables.product.prodname_dotcom_the_website %} 上的企业帐户可用于计费以及通过 {% data variables.product.prodname_github_connect %} 与 {% data variables.product.prodname_dotcom_the_website %} 共享功能。 有关详细信息,请参阅[关于企业帐户](/admin/overview/about-enterprise-accounts)。 -### 2. 安装 {% data variables.product.product_name %} -要开始使用 {% data variables.product.product_name %},您需要在所选的虚拟化平台上安装设备。 有关详细信息,请参阅“[设置 {% data variables.product.prodname_ghe_server %} 实例](/admin/installation/setting-up-a-github-enterprise-server-instance)”。 +For more information about {% data variables.product.product_name %}, see "[About {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server)." -### 3. 使用管理控制台 -您将使用管理控制台在首次启动 {% data variables.product.product_location %} 时完成初始设置过程。 您还可以使用管理控制台管理实例设置,例如许可证、域、身份验证和 TLS。 有关详细信息,请参阅“[访问管理控制台](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)”。 +## Part 1: Installing {% data variables.product.product_name %} +To get started with {% data variables.product.product_name %}, you will need to create your enterprise account, install the instance, use the Management Console for initial setup, configure your instance, and manage billing. +### 1. Creating your enterprise account +Before you install {% data variables.product.product_name %}, you can create an enterprise account on {% data variables.product.prodname_dotcom_the_website %} by contacting [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). An enterprise account on {% data variables.product.prodname_dotcom_the_website %} is useful for billing and for shared features with {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)." +### 2. Installing {% data variables.product.product_name %} +To get started with {% data variables.product.product_name %}, you will need to install the appliance on a virtualization platform of your choice. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)." -### 4. 配置 {% data variables.product.product_location %} -除了管理控制台之外,您还可以使用站点管理仪表板和管理 shell (SSH) 来管理 {% data variables.product.product_location %}。 例如,您可以配置应用程序和速率限制、查看报告、使用命令行实用程序。 有关详细信息,请参阅“[配置你的企业](/admin/configuration/configuring-your-enterprise)”。 +### 3. Using the Management Console +You will use the Management Console to walk through the initial setup process when first launching {% data variables.location.product_location %}. You can also use the Management Console to manage instance settings such as the license, domain, authentication, and TLS. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)." -您可以使用 {% data variables.product.product_name %} 通过动态主机配置协议 (DHCP) 使用的默认网络设置,也可以使用虚拟机控制台配置网络设置。 您还可以配置代理服务器或防火墙规则。 有关详细信息,请参阅“[配置网络设置](/admin/configuration/configuring-network-settings)”。 +### 4. Configuring {% data variables.location.product_location %} +In addition to the Management Console, you can use the site admin dashboard and the administrative shell (SSH) to manage {% data variables.location.product_location %}. For example, you can configure applications and rate limits, view reports, use command-line utilities. For more information, see "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)." -### 5. 配置高可用性 -您可以配置 {% data variables.product.product_location %} 以实现高可用性,以最大程度地减少硬件故障和网络中断的影响。 有关详细信息,请参阅“[配置高可用性](/admin/enterprise-management/configuring-high-availability)”。 +You can use the default network settings used by {% data variables.product.product_name %} via the dynamic host configuration protocol (DHCP), or you can also configure the network settings using the virtual machine console. You can also configure a proxy server or firewall rules. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)." -### 6. 设置暂存实例 -您可以设置暂存实例来测试修改、规划灾难恢复,并在将更新应用于 {% data variables.product.product_location %} 之前试用更新。 有关详细信息,请参阅“[设置暂存实例](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)”。 +### 5. Configuring high availability +You can configure {% data variables.location.product_location %} for high availability to minimize the impact of hardware failures and network outages. For more information, see "[Configuring high availability](/admin/enterprise-management/configuring-high-availability)." -### 7. 指定备份和灾难恢复 -要保护生产数据,您可以使用 {% data variables.product.prodname_enterprise_backup_utilities %} 配置 {% data variables.product.product_location %} 的自动备份。 有关详细信息,请参阅“[在设备上配置备份](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)”。 +### 6. Setting up a staging instance +You can set up a staging instance to test modifications, plan for disaster recovery, and try out updates before applying them to {% data variables.location.product_location %}. For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)." -### 8. 管理企业的账单 -对于连接到您的企业帐户的所有组织和 {% data variables.product.product_name %} 实例,帐单将汇总到所有付费 {% data variables.product.prodname_dotcom %}.com 服务的单个帐单费用中。 企业所有者和帐单管理员均可访问和管理企业帐户的帐单设置。 有关详细信息,请参阅“[管理企业的计费](/admin/overview/managing-billing-for-your-enterprise)”。 +### 7. Designating backups and disaster recovery +To protect your production data, you can configure automated backups of {% data variables.location.product_location %} with {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)." -## 第 2 部分:组织和管理团队 -作为企业所有者或管理员,您可以管理用户、存储库、团队和组织级别的设置。 您可以管理企业成员、创建和管理组织、设置存储库管理策略以及创建和管理团队。 +### 8. Managing billing for your enterprise +Billing for all the organizations and {% data variables.product.product_name %} instances connected to your enterprise account is aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom %}.com services. Enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." -### 1. 管理 {% data variables.product.product_location %} 的成员 +## Part 2: Organizing and managing your team +As an enterprise owner or administrator, you can manage settings on user, repository, team and organization levels. You can manage members of your enterprise, create and manage organizations, set policies for repository management, and create and manage teams. + +### 1. Managing members of {% data variables.location.product_location %} {% data reusables.getting-started.managing-enterprise-members %} -### 2. 创建组织 +### 2. Creating organizations {% data reusables.getting-started.creating-organizations %} -### 3. 向组织添加成员 +### 3. Adding members to organizations {% data reusables.getting-started.adding-members-to-organizations %} -### 4. 创建团队 +### 4. Creating teams {% data reusables.getting-started.creating-teams %} -### 5. 设置组织和存储库权限级别 +### 5. Setting organization and repository permission levels {% data reusables.getting-started.setting-org-and-repo-permissions %} -### 6. 实施存储库管理策略 +### 6. Enforcing repository management policies {% data reusables.getting-started.enforcing-repo-management-policies %} -## 第 3 部分:安全构建 -要提高 {% data variables.product.product_location %} 的安全性,可以为企业成员配置身份验证,使用工具和审核日志记录以保持合规性,为组织配置安全性和分析功能,以及选择性地启用 {% data variables.product.prodname_GH_advanced_security %}。 -### 1. 对企业成员进行身份验证 -可以使用 {% data variables.product.product_name %} 的内置身份验证方法,也可以在外部身份验证提供程序(如 CAS、LDAP 或 SAML)之间进行选择,以集成现有帐户并集中管理用户对 {% data variables.product.product_location %} 的访问。 有关详细信息,请参阅“[关于企业身份验证](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)”。 +## Part 3: Building securely +To increase the security of {% data variables.location.product_location %}, you can configure authentication for enterprise members, use tools and audit logging to stay in compliance, configure security and analysis features for your organizations, and optionally enable {% data variables.product.prodname_GH_advanced_security %}. +### 1. Authenticating enterprise members +You can use {% data variables.product.product_name %}'s built-in authentication method, or you can choose between an external authentication provider, such as CAS, LDAP, or SAML, to integrate your existing accounts and centrally manage user access to {% data variables.location.product_location %}. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)." -您还可以要求对每个组织进行双重身份验证。 有关详细信息,请参阅“[要求对组织进行双因素身份验证](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)”。 +You can also require two-factor authentication for each of your organizations. For more information, see "[Requiring two factor authentication for an organization](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)." -### 2. 保持合规性 -您可以实施所需的状态检查和提交验证,以强制实施组织的合规性标准并自动执行合规性工作流。 您还可以使用组织的审核日志来查看团队执行的操作。 有关详细信息,请参阅“[使用预接收挂钩强制实施策略](/admin/policies/enforcing-policy-with-pre-receive-hooks)”和“[关于企业审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)”。 +### 2. Staying in compliance +You can implement required status checks and commit verifications to enforce your organization's compliance standards and automate compliance workflows. You can also use the audit log for your organization to review actions performed by your team. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)" and "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)." {% ifversion ghes %} -### 3. 为组织配置安全功能 -{% data reusables.getting-started.configuring-security-features %} {% endif %} - -{% ifversion ghes %} -### 4. 启用 {% data variables.product.prodname_GH_advanced_security %} 功能 -您可以升级 {% data variables.product.product_name %} 许可证以包含 {% data variables.product.prodname_GH_advanced_security %}。 这将提供额外的功能,帮助用户发现和修复其代码中的安全问题,例如代码和机密扫描。 有关详细信息,请参阅“[企业的 {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)”。 +### 3. Configuring security features for your organizations +{% data reusables.getting-started.configuring-security-features %} {% endif %} -## 第 4 部分:自定义和自动化企业在 {% data variables.product.prodname_dotcom %} 上的工作 -您可以使用 {% data variables.product.prodname_dotcom %} 和 {% data variables.product.prodname_oauth_apps %}、{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API、{% data variables.product.prodname_actions %}、{% data variables.product.prodname_registry %} 和 {% data variables.product.prodname_pages %} 自定义和自动化企业中组织中的工作。 +{% ifversion ghes %} +### 4. Enabling {% data variables.product.prodname_GH_advanced_security %} features +You can upgrade your {% data variables.product.product_name %} license to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code, such as code and secret scanning. For more information, see "[{% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)." +{% endif %} -### 1. 构建 {% data variables.product.prodname_github_apps %} 和 {% data variables.product.prodname_oauth_apps %} -您可以构建与 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 的集成,如 {% data variables.product.prodname_github_apps %} 或 {% data variables.product.prodname_oauth_apps %},以便在企业中的组织中使用,以补充和扩展您的工作流程。 有关详细信息,请参阅“[关于应用](/developers/apps/getting-started-with-apps/about-apps)”。 -### 2. 使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API +## Part 4: Customizing and automating your enterprise's work on {% data variables.product.prodname_dotcom %} +You can customize and automate work in organizations in your enterprise with {% data variables.product.prodname_dotcom %} and {% data variables.product.prodname_oauth_apps %}, {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} , and {% data variables.product.prodname_pages %}. + +### 1. Building {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} +You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)." +### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API {% data reusables.getting-started.api %} {% ifversion ghes %} -### 3. 生成 {% data variables.product.prodname_actions %} +### 3. Building {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -有关在 {% data variables.product.product_name %} 上启用和配置 {% data variables.product.prodname_actions %} 的详细信息,请参阅“[{% data variables.product.prodname_ghe_server %} 的 {% data variables.product.prodname_actions %} 使用入门](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)”。 +For more information on enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)." -### 4. 发布和管理 {% data variables.product.prodname_registry %} +### 4. Publishing and managing {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} -有关启用和配置 {% data variables.product.product_location %} 的 {% data variables.product.prodname_registry %} 的详细信息,请参阅“[企业的 {% data variables.product.prodname_registry %} 使用入门](/admin/packages/getting-started-with-github-packages-for-your-enterprise)”。 +For more information on enabling and configuring {% data variables.product.prodname_registry %} for {% data variables.location.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." {% endif %} -### 5. 使用 {% data variables.product.prodname_pages %} +### 5. Using {% data variables.product.prodname_pages %} {% data reusables.getting-started.github-pages-enterprise %} -## 第 5 部分:与其他 {% data variables.product.prodname_dotcom %} 资源连接 -您可以使用 {% data variables.product.prodname_github_connect %} 共享资源。 +## Part 5: Connecting with other {% data variables.product.prodname_dotcom %} resources +You can use {% data variables.product.prodname_github_connect %} to share resources. -如果您既是 {% data variables.product.product_name %} 实例的所有者,又是 {% data variables.product.prodname_ghe_cloud %} 组织或企业帐户的所有者,则可以启用 {% data variables.product.prodname_github_connect %}。 {% data variables.product.prodname_github_connect %} 允许您在 {% data variables.product.product_location %} 与 {% data variables.product.prodname_ghe_cloud %} 之间共享特定的工作流程和功能,例如统一搜索和贡献。 有关详细信息,请参阅“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)”。 +If you are the owner of both a {% data variables.product.product_name %} instance and a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account, you can enable {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} allows you to share specific workflows and features between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %}, such as unified search and contributions. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)." -## 第 6 部分:使用 {% data variables.product.prodname_dotcom %} 的学习和支持资源 -您的企业成员可以通过我们的学习资源了解有关 Git 和 {% data variables.product.prodname_dotcom %} 的更多信息,并且您可以使用 {% data variables.product.prodname_dotcom %} Enterprise 支持来设置和管理 {% data variables.product.product_location %} 时获得所需的支持。 +## Part 6: Using {% data variables.product.prodname_dotcom %}'s learning and support resources +Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need when setting up and managing {% data variables.location.product_location %} with {% data variables.product.prodname_dotcom %} Enterprise Support. -### 1. 在 {% data variables.product.prodname_docs %} 上阅读 {% data variables.product.product_name %} +### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %} -您可以阅读反映 {% data variables.product.prodname_ghe_server %} 可用功能的文档。 有关详细信息,请参阅[关于 {% data variables.product.prodname_docs %} 的版本](/get-started/learning-about-github/about-versions-of-github-docs)。 +You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_server %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." -### 2. 通过 {% data variables.product.prodname_learning %} 学习 +### 2. Learning with {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning-enterprise %} -### 3. 使用 {% data variables.product.prodname_dotcom %} Enterprise 支持 +### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support {% data reusables.getting-started.contact-support-enterprise %} diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md index bf43f07d98..0f9f02a3ef 100644 --- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md +++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md @@ -1,104 +1,99 @@ --- -title: 开始使用 GitHub Team -intro: '通过 {% data variables.product.prodname_team %} 组人员可以在组织帐户中同时跨多个项目进行协作。' +title: Getting started with GitHub Team +intro: 'With {% data variables.product.prodname_team %} groups of people can collaborate across many projects at the same time in an organization account.' versions: fpt: '*' -ms.openlocfilehash: 46b5376b72ce30f7c526f693f2adb9253853cf1d -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '146139158' --- -本指南将引导您以组织所有者的身份设置、配置和管理您的 {% data variables.product.prodname_team %} 帐户。 -## 第 1 部分:在 {% data variables.product.product_location %}上配置您的帐户 -若要开始使用 {% data variables.product.prodname_team %},首先需要创建个人帐户或登录到 {% data variables.product.prodname_dotcom %} 上的现有帐户,创建组织并设置账单。 +This guide will walk you through setting up, configuring and managing your {% data variables.product.prodname_team %} account as an organization owner. -### 1. 关于组织 -组织是共享帐户,其中业务和开源项目可同时跨多个项目进行协作。 所有者和管理员可使用复杂的安全性和管理功能来管理成员对组织数据和项目的访问。 有关组织功能的详细信息,请参阅“[关于组织](/organizations/collaborating-with-groups-in-organizations/about-organizations#terms-of-service-and-data-protection-for-organizations)”。 +## Part 1: Configuring your account on {% data variables.location.product_location %} +As the first steps in starting with {% data variables.product.prodname_team %}, you will need to create a personal account or log into your existing account on {% data variables.product.prodname_dotcom %}, create an organization, and set up billing. -### 2. 创建组织并注册 {% data variables.product.prodname_team %} -在创建组织之前,你需要在 {% data variables.product.product_location %} 上创建个人帐户或登录到现有帐户。 有关详细信息,请参阅“[注册新 {% data variables.product.prodname_dotcom %} 帐户](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)”。 +### 1. About organizations +Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features. For more information on the features of organizations, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations#terms-of-service-and-data-protection-for-organizations)." -设置个人帐户后,你可以创建组织并选择计划。 您可以在此处为组织选择 {% data variables.product.prodname_team %} 订阅。 有关详细信息,请参阅“[从头开始创建新组织](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)”。 +### 2. Creating an organization and signing up for {% data variables.product.prodname_team %} +Before creating an organization, you will need to create a personal account or log in to your existing account on {% data variables.location.product_location %}. For more information, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)." -### 3. 管理组织的账单 -您必须单独管理每个个人帐户和组织的结算设置、付款方式以及付费功能和产品。 您可以使用设置中的上下文切换器在不同帐户的设置之间切换。 有关详细信息,请参阅“[在不同帐户的设置之间切换](/billing/managing-your-github-billing-settings/about-billing-on-github#switching-between-settings-for-your-different-accounts)”。 +Once your personal account is set up, you can create an organization and pick a plan. This is where you can choose a {% data variables.product.prodname_team %} subscription for your organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." -通过组织的计费设置页面,您可以管理付款方式、结算周期和帐单邮箱等设置,或查看订阅、帐单日期和付款历史记录等信息。 您还可以查看和升级您的存储和 GitHub Actions 分钟数。 有关管理计费设置的详细信息,请参阅“[管理 {% data variables.product.prodname_dotcom %} 计费设置](/billing/managing-your-github-billing-settings)”。 +### 3. Managing billing for an organization +You must manage billing settings, payment method, and paid features and products for each of your personal accounts and organizations separately. You can switch between settings for your different accounts using the context switcher in your settings. For more information, see "[Switching between settings for your different accounts](/billing/managing-your-github-billing-settings/about-billing-on-github#switching-between-settings-for-your-different-accounts)." -只有具有所有者或账单管理员角色的组织成员才能访问或更改组织的计费设置 。 帐单管理员是管理组织的计费设置且不在组织的订阅中使用付费许可证的人员。 有关将账单管理员添加到组织的详细信息,请参阅“[为组织添加帐单管理员](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)”。 +Your organization's billing settings page allows you to manage settings like your payment method, billing cycle and billing email, or view information such as your subscription, billing date and payment history. You can also view and upgrade your storage and GitHub Actions minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)." + +Only organization members with the *owner* or *billing manager* role can access or change billing settings for your organization. A billing manager is someone who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)." -## 第 2 部分:添加成员和设置团队 -创建组织后,您可以邀请成员并设置权限和角色。 您还可以创建不同级别的团队,并为组织的存储库、项目板和应用程序设置自定义权限级别。 +## Part 2: Adding members and setting up teams +After creating your organization, you can invite members and set permissions and roles. You can also create different levels of teams and set customized levels of permissions for your organization's repositories, project boards, and apps. -### 1. 管理组织成员 +### 1. Managing members of your organization {% data reusables.getting-started.managing-org-members %} -### 2. 组织权限和角色 +### 2. Organization permissions and roles {% data reusables.getting-started.org-permissions-and-roles %} -### 3. 关于和创建团队 +### 3. About and creating teams {% data reusables.getting-started.about-and-creating-teams %} -### 4. 管理团队设置 +### 4. Managing team settings {% data reusables.getting-started.managing-team-settings %} -### 5. 为人员和团队提供对存储库、项目板和应用的访问权限 +### 5. Giving people and teams access to repositories, project boards and apps {% data reusables.getting-started.giving-access-to-repositories-projects-apps %} -## 第 3 部分:管理组织的安全性 -通过建议或要求对组织成员进行双重身份验证、配置安全功能以及查看组织的审核日志和集成,可以帮助提高组织的安全性。 +## Part 3: Managing security for your organization +You can help to make your organization more secure by recommending or requiring two-factor authentication for your organization members, configuring security features, and reviewing your organization's audit log and integrations. -### 1. 需要双重身份验证 +### 1. Requiring two-factor authentication {% data reusables.getting-started.requiring-2fa %} -### 2. 为组织配置安全功能 +### 2. Configuring security features for your organization {% data reusables.getting-started.configuring-security-features %} -### 3. 查看组织的审核日志和集成 +### 3. Reviewing your organization's audit log and integrations {% data reusables.getting-started.reviewing-org-audit-log-and-integrations %} -## 第 4 部分:设置组织级别策略 -### 1. 管理组织策略 +## Part 4: Setting organization level policies +### 1. Managing organization policies {% data reusables.getting-started.managing-org-policies %} -### 2. 管理存储库更改 +### 2. Managing repository changes {% data reusables.getting-started.managing-repo-changes %} -### 3. 使用组织级别的社区运行状况文件和审查工具 +### 3. Using organization-level community health files and moderation tools {% data reusables.getting-started.using-org-community-files-and-moderation-tools %} -## 第 5 部分:自定义和自动化 {% data variables.product.product_name %} 上的工作 +## Part 5: Customizing and automating your work on {% data variables.product.product_name %} {% data reusables.getting-started.customizing-and-automating %} -### 1. 使用 {% data variables.product.prodname_marketplace %} +### 1. Using {% data variables.product.prodname_marketplace %} {% data reusables.getting-started.marketplace %} -### 2. 使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API +### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API {% data reusables.getting-started.api %} -### 3. 生成 {% data variables.product.prodname_actions %} +### 3. Building {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -### 4. 发布和管理 {% data variables.product.prodname_registry %} +### 4. Publishing and managing {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} -## 第 6 部分:参与 {% data variables.product.prodname_dotcom %} 的社区 +## Part 6: Participating in {% data variables.product.prodname_dotcom %}'s community {% data reusables.getting-started.participating-in-community %} -### 1. 参与开源项目 +### 1. Contributing to open source projects {% data reusables.getting-started.open-source-projects %} -### 2. 与 {% data variables.product.prodname_gcf %} 交互 +### 2. Interacting with the {% data variables.product.prodname_gcf %} {% data reusables.support.ask-and-answer-forum %} -### 3. 了解 {% data variables.product.prodname_docs %} 上的 {% data variables.product.prodname_team %} -您可以阅读反映 {% data variables.product.prodname_team %} 可用功能的文档。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_docs %} 的版本](/get-started/learning-about-github/about-versions-of-github-docs)”。 +### 3. Reading about {% data variables.product.prodname_team %} on {% data variables.product.prodname_docs %} +You can read documentation that reflects the features available with {% data variables.product.prodname_team %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." -### 4. 通过 {% data variables.product.prodname_learning %} 学习 +### 4. Learning with {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning %} -### 5. 支持开源社区 +### 5. Supporting the open source community {% data reusables.getting-started.sponsors %} -### 6. 联系 {% data variables.contact.github_support %} +### 6. Contacting {% data variables.contact.github_support %} {% data reusables.getting-started.contact-support %} -## 延伸阅读 +## Further reading -- [开始使用 GitHub 帐户](/get-started/onboarding/getting-started-with-your-github-account) +- "[Getting started with your GitHub account](/get-started/onboarding/getting-started-with-your-github-account)" diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md index dbf948f14a..9fe0d1f65c 100644 --- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md +++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md @@ -1,199 +1,203 @@ --- -title: 开始使用 GitHub 帐户 -intro: '使用 {% data variables.product.prodname_dotcom %} 上的个人帐户,你可以导入或创建存储库、与他人协作以及与 {% data variables.product.prodname_dotcom %} 社区联系。' +title: Getting started with your GitHub account +intro: 'With a personal account on {% data variables.product.prodname_dotcom %}, you can import or create repositories, collaborate with others, and connect with the {% data variables.product.prodname_dotcom %} community.' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' -ms.openlocfilehash: 38d23c1a1b5021a681aedff8813daad751905d8a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147408920' --- -本指南将引导您完成 {% data variables.product.company_short %} 帐户的设置,并开始使用 {% data variables.product.product_name %} 协作和社区功能。 -## 第 1 部分:配置 {% data variables.product.prodname_dotcom %} 帐户 +This guide will walk you through setting up your {% data variables.product.company_short %} account and getting started with {% data variables.product.product_name %}'s features for collaboration and community. -{% ifversion fpt or ghec %} 开始使用 {% data variables.product.product_name %} 的第一步是创建一个帐户,选择最适合你需求的产品,验证你的电子邮件,设置双重身份验证以及查看你的配置文件。 -{% elsif ghes %} 开始使用 {% data variables.product.product_name %} 的第一步是访问你的帐户,设置双重身份验证并查看你的配置文件。 -{% elsif ghae %} 开始使用 {% data variables.product.product_name %} 的第一步是访问你的帐户并查看你的配置文件。 -{% endif %} - -{% ifversion fpt or ghec %} {% data variables.product.prodname_dotcom %} 上有几种类型的帐户。 {% endif %} 使用 {% data variables.product.product_name %} 的每个人都有自己的个人帐户,该帐户可以是多个组织和团队的一部分。 你的个人帐户是你在 {% data variables.product.product_location %} 上的身份,代表你个人。 +## Part 1: Configuring your {% data variables.product.prodname_dotcom %} account {% ifversion fpt or ghec %} -### 1. 创建帐户 -要在 {% data variables.product.product_location %} 上注册帐户,请导航到 https://github.com/ 并按照提示操作。 +The first steps in starting with {% data variables.product.product_name %} are to create an account, choose a product that fits your needs best, verify your email, set up two-factor authentication, and view your profile. +{% elsif ghes %} +The first steps in starting with {% data variables.product.product_name %} are to access your account, set up two-factor authentication, and view your profile. +{% elsif ghae %} +The first steps in starting with {% data variables.product.product_name %} are to access your account and view your profile. +{% endif %} -为了保证 {% data variables.product.prodname_dotcom %} 帐户的安全,您应该使用强大且唯一的密码。 有关详细信息,请参阅“[创建强密码](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)”。 +{% ifversion fpt or ghec %}There are several types of accounts on {% data variables.product.prodname_dotcom %}. {% endif %} Every person who uses {% data variables.product.product_name %} has their own personal account, which can be part of multiple organizations and teams. Your personal account is your identity on {% data variables.location.product_location %} and represents you as an individual. -### 2. 选择 {% data variables.product.prodname_dotcom %} 产品 -您可以选择 {% data variables.product.prodname_free_user %} 或 {% data variables.product.prodname_pro %} 来访问个人帐户的不同功能。 如果您一开始不确定需要哪种产品,可以随时升级。 +{% ifversion fpt or ghec %} +### 1. Creating an account +To sign up for an account on {% data variables.location.product_location %}, navigate to https://github.com/ and follow the prompts. -有关所有 {% data variables.product.prodname_dotcom %} 计划的详细信息,请参阅“[{% data variables.product.prodname_dotcom %} 的产品](/get-started/learning-about-github/githubs-products)”。 +To keep your {% data variables.product.prodname_dotcom %} account secure you should use a strong and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)." -### 3. 验证电子邮件地址 -为确保您可以使用 {% data variables.product.product_name %} 计划中的所有功能,请在注册新帐户后验证您的电子邮件地址。 有关详细信息,请参阅“[验证电子邮件地址](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)”。 +### 2. Choosing your {% data variables.product.prodname_dotcom %} product +You can choose {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %} to get access to different features for your personal account. You can upgrade at any time if you are unsure at first which product you want. + +For more information on all of {% data variables.product.prodname_dotcom %}'s plans, see "[{% data variables.product.prodname_dotcom %}'s products](/get-started/learning-about-github/githubs-products)." + +### 3. Verifying your email address +To ensure you can use all the features in your {% data variables.product.product_name %} plan, verify your email address after signing up for a new account. For more information, see "[Verifying your email address](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)." {% endif %} {% ifversion ghes %} -### 1. 访问你的帐户 -{% data variables.product.product_name %} 实例的管理员将通知您如何验证和访问您的帐户。 该过程因他们为实例配置的身份验证模式而异。 +### 1. Accessing your account +The administrator of your {% data variables.product.product_name %} instance will notify you about how to authenticate and access your account. The process varies depending on the authentication mode they have configured for the instance. {% endif %} {% ifversion ghae %} -### 1. 访问你的帐户 -在 {% data variables.product.product_name %} 的企业所有者设置您的帐户后,您将收到一封电子邮件通知,允许您使用 SAML 单点登录 (SSO) 进行身份验证并访问您的帐户。 +### 1. Accessing your account +You will receive an email notification once your enterprise owner for {% data variables.product.product_name %} has set up your account, allowing you to authenticate with SAML single sign-on (SSO) and access your account. {% endif %} {% ifversion fpt or ghes or ghec %} -### {% ifversion fpt or ghec %}4.{% else %}2.{% endif %} 配置双重身份验证 -双因素身份验证 (2FA) 是登录网站或应用时采用的额外安全保障。 我们强烈建议您配置 2FA 以确保帐户安全。 有关详细信息,请参阅[关于双因素身份验证](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)。 +### {% ifversion fpt or ghec %}4.{% else %}2.{% endif %} Configuring two-factor authentication +Two-factor authentication, or 2FA, is an extra layer of security used when logging into websites or apps. We strongly urge you to configure 2FA for the safety of your account. For more information, see "[About two-factor authentication](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)." {% endif %} -### {% ifversion fpt or ghec %}5.{% elsif ghes %}3.{% else %}2.{% endif %} 查看您的 {% data variables.product.prodname_dotcom %} 个人资料和贡献图 -您的 {% data variables.product.prodname_dotcom %} 个人资料通过您固定的存储库和 gist、您选择公开的组织成员资格、您所做的贡献以及您创建的项目,向人们讲述您的工作故事。 有关详细信息,请参阅“[关于你的配置文件](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile)”和“[查看你的配置文件上的贡献](/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile)”。 +### {% ifversion fpt or ghec %}5.{% elsif ghes %}3.{% else %}2.{% endif %} Viewing your {% data variables.product.prodname_dotcom %} profile and contribution graph +Your {% data variables.product.prodname_dotcom %} profile tells people the story of your work through the repositories and gists you've pinned, the organization memberships you've chosen to publicize, the contributions you've made, and the projects you've created. For more information, see "[About your profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile)" and "[Viewing contributions on your profile](/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile)." -## 第 2 部分:使用 {% data variables.product.product_name %} 的工具和流程 -为了最好地使用 {% data variables.product.product_name %},您需要设置 Git。 Git 负责在你计算机上本地发生的、与 {% data variables.product.prodname_dotcom %} 有关的所有内容。 为了在 {% data variables.product.product_name %} 上有效地进行协作,您需要使用 {% data variables.product.prodname_dotcom %} Flavored Markdown 编写议题和拉取请求。 +## Part 2: Using {% data variables.product.product_name %}'s tools and processes +To best use {% data variables.product.product_name %}, you'll need to set up Git. Git is responsible for everything {% data variables.product.prodname_dotcom %}-related that happens locally on your computer. To effectively collaborate on {% data variables.product.product_name %}, you'll write in issues and pull requests using {% data variables.product.prodname_dotcom %} Flavored Markdown. -### 1. 了解 Git -{% data variables.product.prodname_dotcom %} 的协作开发方法取决于从您的本地仓库发布提交到 {% data variables.product.product_name %},以供其他人使用 Git 查看、提取和更新。 有关 Git 的详细信息,请参阅“[Git 手册](https://guides.github.com/introduction/git-handbook/)”指南。 有关如何在 {% data variables.product.product_name %} 上使用 Git 的详细信息,请参阅“[{% data variables.product.prodname_dotcom %} 流](/get-started/quickstart/github-flow)”。 -### 2. 设置 Git -如果您计划在计算机上本地使用 Git,无论是通过命令行、IDE 还是文本编辑器,您都需要安装和设置 Git。 有关详细信息,请参阅“[设置 Git](/get-started/quickstart/set-up-git)”。 +### 1. Learning Git +{% data variables.product.prodname_dotcom %}'s collaborative approach to development depends on publishing commits from your local repository to {% data variables.product.product_name %} for other people to view, fetch, and update using Git. For more information about Git, see the "[Git Handbook](https://guides.github.com/introduction/git-handbook/)" guide. For more information about how Git is used on {% data variables.product.product_name %}, see "[{% data variables.product.prodname_dotcom %} flow](/get-started/quickstart/github-flow)." +### 2. Setting up Git +If you plan to use Git locally on your computer, whether through the command line, an IDE or text editor, you will need to install and set up Git. For more information, see "[Set up Git](/get-started/quickstart/set-up-git)." -如果您更喜欢使用可视化界面,可以下载并使用 {% data variables.product.prodname_desktop %}。 {% data variables.product.prodname_desktop %} 与 Git 一起打包,因此无需单独安装 Git。 有关详细信息,请参阅“[{% data variables.product.prodname_desktop %} 入门指南](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)”。 +If you prefer to use a visual interface, you can download and use {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} comes packaged with Git, so there is no need to install Git separately. For more information, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)." -安装 Git 后,您可以从本地计算机连接到 {% data variables.product.product_name %} 存储库,无论是您自己的存储库还是其他用户的复刻。 当您从 Git 连接到 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的存储库时,您需要使用 HTTPS 或 SSH 向 {% data variables.product.product_name %} 进行身份验证。 有关详细信息,请参阅“[关于远程存储库](/get-started/getting-started-with-git/about-remote-repositories)”。 +Once you install Git, you can connect to {% data variables.product.product_name %} repositories from your local computer, whether your own repository or another user's fork. When you connect to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} from Git, you'll need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH. For more information, see "[About remote repositories](/get-started/getting-started-with-git/about-remote-repositories)." -### 3. 选择如何与 {% data variables.product.product_name %} 互动 -每个人都有自己独特的工作流程,用于与 {% data variables.product.prodname_dotcom %} 互动;您使用的接口和方法取决于您的偏好和需求。 +### 3. Choosing how to interact with {% data variables.product.product_name %} +Everyone has their own unique workflow for interacting with {% data variables.product.prodname_dotcom %}; the interfaces and methods you use depend on your preference and what works best for your needs. -有关如何使用这些方法向 {% data variables.product.product_name %} 进行身份验证的详细信息,请参阅“[关于向 {% data variables.product.prodname_dotcom %} 进行身份验证](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github)”。 +For more information about how to authenticate to {% data variables.product.product_name %} with each of these methods, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github)." -| **方法** | **说明** | **用例** | +| **Method** | **Description** | **Use cases** | | ------------- | ------------- | ------------- | -| 浏览到 {% data variables.product.prodname_dotcom_the_website %} | 如果您不需要在本地处理文件,{% data variables.product.product_name %} 可让您直接在浏览器中完成大多数与 Git 相关的操作,从创建和复刻存储库到编辑文件和打开拉取请求。| 如果您想要一个可视化界面,并且需要执行不需要在本地工作的快速、简单更改,则此方法非常有用。 | -| {% data variables.product.prodname_desktop %} | {% data variables.product.prodname_desktop %} 可扩展并简化您的 {% data variables.product.prodname_dotcom_the_website %} 工作流程,它使用可视界面,而不是在命令行上使用命令文本。 有关 {% data variables.product.prodname_desktop %} 入门的详细信息,请参阅“[{% data variables.product.prodname_desktop %} 入门指南](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)”。 | 如果您需要或想要在本地处理文件,但更喜欢使用可视化界面来使用 Git 并与 {% data variables.product.product_name %} 交互,则此方法最佳。 | -| IDE 或文本编辑器 | 可以设置默认文本编辑器(如 [Atom](https://atom.io/) 或 [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/))以使用 Git 打开和编辑文件、使用扩展和查看项目结构。 有关详细信息,请参阅“[将文本编辑器与 Git 关联](/github/using-git/associating-text-editors-with-git)”。 | 如果您正在处理更复杂的文件和项目,并且希望所有内容都在一个地方,这将很方便,因为文本编辑器或 IDE 通常允许您直接访问编辑器中的命令行。 | -| 命令行,带或不带 {% data variables.product.prodname_cli %} | 要最精细地控制和自定义如何使用 Git 以及与 {% data variables.product.product_name %} 交互的方式,可以使用命令行。 有关使用 Git 命令的详细信息,请参阅“[Git 速查表](/github/getting-started-with-github/quickstart/git-cheatsheet)”。

{% data variables.product.prodname_cli %} 是一个可以安装的命令行工具,可将拉取请求、问题、{% data variables.product.prodname_actions %} 和其他 {% data variables.product.prodname_dotcom %} 功能引入终端,让你可以在一个地方完成所有工作。 有关详细信息,请参阅“[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)”。 | 如果您已经使用命令行,或者您更习惯于使用命令行,这样最方便,可以避免切换上下文。 | -| {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} 有 REST API 和 GraphQL API,您可以使用它们与 {% data variables.product.product_name %} 进行交互。 有关详细信息,请参阅“[API 入门指南](/github/extending-github/getting-started-with-the-api)”。 | 如果要自动执行常见任务、备份数据或创建扩展 {% data variables.product.prodname_dotcom %} 的集成,则 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 将非常有用。 | -### 4. 在 {% data variables.product.product_name %} 上编写 -为了使您的通信清晰明了,在议题和拉取请求中井井有条,您可以使用 {% data variables.product.prodname_dotcom %} Flavored Markdown 进行格式化,结合易读、易写语法与一些自定义功能。 有关详细信息,请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上编写和设置格式](/github/writing-on-github/about-writing-and-formatting-on-github)”。 +| Browse to {% data variables.product.prodname_dotcom_the_website %} | If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete most Git-related actions directly in the browser, from creating and forking repositories to editing files and opening pull requests.| This method is useful if you want a visual interface and need to do quick, simple changes that don't require working locally. | +| {% data variables.product.prodname_desktop %} | {% data variables.product.prodname_desktop %} extends and simplifies your {% data variables.product.prodname_dotcom_the_website %} workflow, using a visual interface instead of text commands on the command line. For more information on getting started with {% data variables.product.prodname_desktop %}, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)." | This method is best if you need or want to work with files locally, but prefer using a visual interface to use Git and interact with {% data variables.product.product_name %}. | +| IDE or text editor | You can set a default text editor like [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. For more information, see "[Associating text editors with Git](/github/using-git/associating-text-editors-with-git)." | This is convenient if you are working with more complex files and projects and want everything in one place, since text editors or IDEs often allow you to directly access the command line in the editor. | +| Command line, with or without {% data variables.product.prodname_cli %} | For the most granular control and customization of how you use Git and interact with {% data variables.product.product_name %}, you can use the command line. For more information on using Git commands, see "[Git cheatsheet](/github/getting-started-with-github/quickstart/git-cheatsheet)."

{% data variables.product.prodname_cli %} is a separate command-line tool you can install that brings pull requests, issues, {% data variables.product.prodname_actions %}, and other {% data variables.product.prodname_dotcom %} features to your terminal, so you can do all your work in one place. For more information, see "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)." | This is most convenient if you are already working from the command line, allowing you to avoid switching context, or if you are more comfortable using the command line. | +| {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} has a REST API and GraphQL API that you can use to interact with {% data variables.product.product_name %}. For more information, see "[Getting started with the API](/github/extending-github/getting-started-with-the-api)." | The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API would be most helpful if you wanted to automate common tasks, back up your data, or create integrations that extend {% data variables.product.prodname_dotcom %}. | +### 4. Writing on {% data variables.product.product_name %} +To make your communication clear and organized in issues and pull requests, you can use {% data variables.product.prodname_dotcom %} Flavored Markdown for formatting, which combines an easy-to-read, easy-to-write syntax with some custom functionality. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)." -可以通过 {% data variables.product.prodname_learning %} 上的“[使用 Markdown 进行通信](https://github.com/skills/communicate-using-markdown)”课程了解 {% data variables.product.prodname_dotcom %} 风格的 Markdown。 +You can learn {% data variables.product.prodname_dotcom %} Flavored Markdown with the "[Communicate using Markdown](https://github.com/skills/communicate-using-markdown)" course on {% data variables.product.prodname_learning %}. -### 5. 在 {% data variables.product.product_name %} 上搜索 -我们的集成搜索可让您在 {% data variables.product.product_name %} 上的众多存储库、用户和代码行中查找所要的内容。 您可以全局搜索所有 {% data variables.product.product_name %},或将搜索限于特定仓库或组织。 有关可在 {% data variables.product.product_name %} 上执行的搜索类型的详细信息,请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上搜索](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github)”。 +### 5. Searching on {% data variables.product.product_name %} +Our integrated search allows you to find what you are looking for among the many repositories, users and lines of code on {% data variables.product.product_name %}. You can search globally across all of {% data variables.product.product_name %} or limit your search to a particular repository or organization. For more information about the types of searches you can do on {% data variables.product.product_name %}, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github)." -我们的搜索语法允许您使用限定符构建查询,以指定要搜索的内容。 有关在搜索中使用的搜索语法的详细信息,请参阅“[在 {% data variables.product.prodname_dotcom %} 上搜索](/github/searching-for-information-on-github/searching-on-github)”。 +Our search syntax allows you to construct queries using qualifiers to specify what you want to search for. For more information on the search syntax to use in search, see "[Searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/searching-on-github)." -### 6. 管理 {% data variables.product.product_name %} 上的文件 -使用 {% data variables.product.product_name %},您可以在存储库或您具有写入权限的任何存储库中创建、编辑、移动和删除文件。 您还可以逐行跟踪文件中更改的历史记录。 有关详细信息,请参阅“[管理 {% data variables.product.prodname_dotcom %} 上的文件](/github/managing-files-in-a-repository/managing-files-on-github)”。 +### 6. Managing files on {% data variables.product.product_name %} +With {% data variables.product.product_name %}, you can create, edit, move and delete files in your repository or any repository you have write access to. You can also track the history of changes in a file line by line. For more information, see "[Managing files on {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/managing-files-on-github)." -## 第 3 部分:在 {% data variables.product.product_name %} 上进行协作 -任意数量的人都可以在 {% data variables.product.product_name %} 的存储库中一起工作。 您可以配置设置、创建项目板和管理通知,以鼓励有效的协作。 +## Part 3: Collaborating on {% data variables.product.product_name %} +Any number of people can work together in repositories across {% data variables.product.product_name %}. You can configure settings, create project boards, and manage your notifications to encourage effective collaboration. -### 1. 使用存储库 +### 1. Working with repositories -#### 创建仓库 -仓库就像项目的文件夹。 你的个人帐户中可以有任意数量的公共和私有存储库。 存储库可以包含文件夹和文件、图像、视频、电子表格和数据集,以及存储库中所有文件的修订历史记录。 有关详细信息,请参阅[关于存储库](/github/creating-cloning-and-archiving-repositories/about-repositories)。 +#### Creating a repository +A repository is like a folder for your project. You can have any number of public and private repositories in your personal account. Repositories can contain folders and files, images, videos, spreadsheets, and data sets, as well as the revision history for all files in the repository. For more information, see "[About repositories](/github/creating-cloning-and-archiving-repositories/about-repositories)." -创建新存储库时,应使用 README 文件初始化存储库,以便让人们了解您的项目。 有关详细信息,请参阅“[创建新存储库](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)”。 +When you create a new repository, you should initialize the repository with a README file to let people know about your project. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)." -#### 克隆仓库 -您可以将现有存储库从 {% data variables.product.product_name %} 克隆到本地计算机,从而更轻松地添加或删除文件、修复合并冲突或进行复杂提交。 克隆存储库将提取 {% data variables.product.prodname_dotcom %} 在当时拥有的所有存储库数据的完整副本,包括项目每个文件和文件夹的所有版本。 有关详细信息,请参阅“[克隆存储库](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)”。 +#### Cloning a repository +You can clone an existing repository from {% data variables.product.product_name %} to your local computer, making it easier to add or remove files, fix merge conflicts, or make complex commits. Cloning a repository pulls down a full copy of all the repository data that {% data variables.product.prodname_dotcom %} has at that point in time, including all versions of every file and folder for the project. For more information, see "[Cloning a repository](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)." -#### 复刻仓库 -复刻是您管理的存储库的副本,除非您向项目所有者提交拉取请求,否则您所做的任何更改都不会影响原始存储库。 复刻最常见的用法是对其他人的项目提出更改或将其他人的项目用作自己创意的起点。 有关详细信息,请参阅“[使用分支](/github/collaborating-with-pull-requests/working-with-forks)”。 -### 2. 导入项目 -如果您有要移动到 {% data variables.product.product_name %} 的现有项目,则可以使用 {% data variables.product.prodname_dotcom %} 导入程序、命令行或外部迁移工具导入项目。 有关详细信息,请参阅“[将源代码导入到 {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github)”。 +#### Forking a repository +A fork is a copy of a repository that you manage, where any changes you make will not affect the original repository unless you submit a pull request to the project owner. Most commonly, forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea. For more information, see "[Working with forks](/github/collaborating-with-pull-requests/working-with-forks)." +### 2. Importing your projects +If you have existing projects you'd like to move over to {% data variables.product.product_name %} you can import projects using the {% data variables.product.prodname_dotcom %} Importer, the command line, or external migration tools. For more information, see "[Importing source code to {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github)." -### 3. 管理协作者和权限 -您可以使用仓库议题、拉取请求及项目板与其他人协作处理您的项目。 可以从存储库设置中的“协作者”选项卡中邀请其他人作为协作者加入你的存储库。 有关详细信息,请参阅“[邀请协作者访问个人存储库](/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)”。 +### 3. Managing collaborators and permissions +You can collaborate on your project with others using your repository's issues, pull requests, and project boards. You can invite other people to your repository as collaborators from the **Collaborators** tab in the repository settings. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)." -你是在个人帐户中创建的任何存储库的所有者,并拥有对存储库的完全控制。 协作者对您的存储库具有写入权限,他们的操作权限有限。 有关详细信息,请参阅“[个人帐户存储库的权限级别](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)”。 +You are the owner of any repository you create in your personal account and have full control of the repository. Collaborators have write access to your repository, limiting what they have permission to do. For more information, see "[Permission levels for a personal account repository](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)." -### 4. 管理存储库设置 -作为存储库的所有者,您可以配置多个设置,包括存储库的可见性、主题和社交媒体预览。 有关详细信息,请参阅“[管理存储库设置](/github/administering-a-repository/managing-repository-settings)”。 +### 4. Managing repository settings +As the owner of a repository you can configure several settings, including the repository's visibility, topics, and social media preview. For more information, see "[Managing repository settings](/github/administering-a-repository/managing-repository-settings)." -### 5. 设置项目以获得正常的贡献 -{% ifversion fpt or ghec %} 为了鼓励存储库中的协作者,你需要一个鼓励人们使用、参与和宣传你的项目的社区。 有关详细信息,请参阅开源指南中的“[构建友好社区](https://opensource.guide/building-community/)”。 +### 5. Setting up your project for healthy contributions +{% ifversion fpt or ghec %} +To encourage collaborators in your repository, you need a community that encourages people to use, contribute to, and evangelize your project. For more information, see "[Building Welcoming Communities](https://opensource.guide/building-community/)" in the Open Source Guides. -通过向存储库添加贡献指南、行为准则和许可证等文件,您可以营造一个环境,让协作者更容易做出有意义、有用的贡献。 有关详细信息,请参阅“[设置项目的健康贡献](/communities/setting-up-your-project-for-healthy-contributions)”。 -{% endif %} {% ifversion ghes or ghae %} 通过向存储库添加贡献指南、行为准则和支持资源等文件,你可以营造一个环境,让协作者更容易做出有意义、有用的贡献。 有关详细信息,请参阅“[设置项目的健康贡献](/communities/setting-up-your-project-for-healthy-contributions)”。 +By adding files like contributing guidelines, a code of conduct, and a license to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)." +{% endif %} +{% ifversion ghes or ghae %} +By adding files like contributing guidelines, a code of conduct, and support resources to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)." {% endif %} -### 6. 使用 GitHub 问题和项目板 -您可以使用 GitHub Issues 来组织工作议题和拉取请求,并使用项目板管理工作流程。 有关详细信息,请参阅“[关于问题](/issues/tracking-your-work-with-issues/about-issues)”和“[关于项目板](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)”。 +### 6. Using GitHub Issues and project boards +You can use GitHub Issues to organize your work with issues and pull requests and manage your workflow with project boards. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)" and "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." -### 7. 管理通知 -通知会提供有关您订阅或参与的 {% data variables.product.prodname_dotcom %} 活动的更新。 如果您的某项对话不再感兴趣,您可以取消订阅、取消关注或自定义以后接收的通知类型。 有关详细信息,请参阅“[关于通知](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)”。 +### 7. Managing notifications +Notifications provide updates about the activity on {% data variables.product.prodname_dotcom %} you've subscribed to or participated in. If you're no longer interested in a conversation, you can unsubscribe, unwatch, or customize the types of notifications you'll receive in the future. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." -### 8. 使用 {% data variables.product.prodname_pages %} -您可以使用 {% data variables.product.prodname_pages %} 直接从 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的存储库创建和托管网站。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)”。 +### 8. Working with {% data variables.product.prodname_pages %} +You can use {% data variables.product.prodname_pages %} to create and host a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)." {% ifversion discussions %} -### 9. 使用 {% data variables.product.prodname_discussions %} -您可以为存储库启用 {% data variables.product.prodname_discussions %},以帮助围绕项目构建社区。 维护者、贡献者和访客可以使用讨论来共享公告、提出和回答问题,以及参与关于目标的对话。 有关详细信息,请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)”。 +### 9. Using {% data variables.product.prodname_discussions %} +You can enable {% data variables.product.prodname_discussions %} for your repository to help build a community around your project. Maintainers, contributors and visitors can use discussions to share announcements, ask and answer questions, and participate in conversations around goals. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." {% endif %} -## 第 4 部分:自定义和自动化 {% data variables.product.product_name %} 上的工作 +## Part 4: Customizing and automating your work on {% data variables.product.product_name %} {% data reusables.getting-started.customizing-and-automating %} {% ifversion fpt or ghec %} -### 1. 使用 {% data variables.product.prodname_marketplace %} -{% data reusables.getting-started.marketplace %} {% endif %} -### {% ifversion fpt or ghec %}2.{% else %}1.{% endif %} 使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API +### 1. Using {% data variables.product.prodname_marketplace %} +{% data reusables.getting-started.marketplace %} +{% endif %} +### {% ifversion fpt or ghec %}2.{% else %}1.{% endif %} Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API {% data reusables.getting-started.api %} -### {% ifversion fpt or ghec %}3.{% else %}2.{% endif %} 构建 {% data variables.product.prodname_actions %} +### {% ifversion fpt or ghec %}3.{% else %}2.{% endif %} Building {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -### {% ifversion fpt or ghec %}4.{% else %}3.{% endif %} 发布和管理 {% data variables.product.prodname_registry %} +### {% ifversion fpt or ghec %}4.{% else %}3.{% endif %} Publishing and managing {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} -## 第 5 部分:在 {% data variables.product.product_name %} 上安全地构建 -{% data variables.product.product_name %} 具有各种安全功能,有助于确保存储库中代码和机密的安全。 某些功能适用于所有存储库,而另一些功能仅适用于公共存储库和具有 {% data variables.product.prodname_GH_advanced_security %} 许可证的存储库。 有关 {% data variables.product.product_name %} 安全功能的概述,请参阅“[{% data variables.product.prodname_dotcom %} 安全功能](/code-security/getting-started/github-security-features)”。 +## Part 5: Building securely on {% data variables.product.product_name %} +{% data variables.product.product_name %} has a variety of security features that help keep code and secrets secure in repositories. Some features are available for all repositories, while others are only available for public repositories and repositories with a {% data variables.product.prodname_GH_advanced_security %} license. For an overview of {% data variables.product.product_name %} security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)." -### 1. 保护存储库 -作为存储库管理员,您可以通过配置存储库安全设置来保护您的存储库。 其中包括管理对存储库的访问、设置安全策略和管理依赖项。 对于公共存储库以及启用了 {% data variables.product.prodname_GH_advanced_security %} 的组织拥有的私有存储库,您还可以配置代码和机密扫描以自动识别漏洞并确保令牌和密钥不会公开。 +### 1. Securing your repository +As a repository administrator, you can secure your repositories by configuring repository security settings. These include managing access to your repository, setting a security policy, and managing dependencies. For public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled, you can also configure code and secret scanning to automatically identify vulnerabilities and ensure tokens and keys are not exposed. -有关保护存储库的步骤的详细信息,请参阅“[保护存储库](/code-security/getting-started/securing-your-repository)”。 +For more information on steps you can take to secure your repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository)." {% ifversion fpt or ghec %} -### 2. 管理依赖项 -安全构建的很大一部分是维护项目的依赖项,以确保所依赖的所有包和应用程序都已更新且安全。 通过浏览存储库的依赖关系图,使用 Dependabot 自动引发拉取请求以使依赖项保持最新,以及接收依赖项的警报和易受攻击依赖项的安全更新,您可以管理上 {% data variables.product.product_name %} 存储库的依赖关系。 +### 2. Managing your dependencies +A large part of building securely is maintaining your project's dependencies to ensure that all packages and applications you depend on are updated and secure. You can manage your repository's dependencies on {% data variables.product.product_name %} by exploring the dependency graph for your repository, using Dependabot to automatically raise pull requests to keep your dependencies up-to-date, and receiving Dependabot alerts and security updates for vulnerable dependencies. -有关详细信息,请参阅“[保护软件供应链](/code-security/supply-chain-security)”。 +For more information, see "[Securing your software supply chain](/code-security/supply-chain-security)." {% endif %} -## 第 6 部分:参与 {% data variables.product.prodname_dotcom %} 的社区 +## Part 6: Participating in {% data variables.product.prodname_dotcom %}'s community {% data reusables.getting-started.participating-in-community %} -### 1. 参与开源项目 +### 1. Contributing to open source projects {% data reusables.getting-started.open-source-projects %} -### 2. 与 {% data variables.product.prodname_gcf %} 互动 +### 2. Interacting with {% data variables.product.prodname_gcf %} {% data reusables.support.ask-and-answer-forum %} -### 3. 在 {% data variables.product.prodname_docs %} 上阅读 {% data variables.product.product_name %} +### 3. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %} {% data reusables.docs.you-can-read-docs-for-your-product %} -### 4. 通过 {% data variables.product.prodname_learning %} 学习 +### 4. Learning with {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning %} {% ifversion fpt or ghec %} -### 5. 支持开源社区 +### 5. Supporting the open source community {% data reusables.getting-started.sponsors %} -### 6. 联系 {% data variables.contact.github_support %} +### 6. Contacting {% data variables.contact.github_support %} {% data reusables.getting-started.contact-support %} {% ifversion fpt %} -## 延伸阅读 -- “[{% data variables.product.prodname_team %} 入门指南](/get-started/onboarding/getting-started-with-github-team)”{% endif %} {% endif %} +## Further reading +- "[Getting started with {% data variables.product.prodname_team %}](/get-started/onboarding/getting-started-with-github-team)" +{% endif %} +{% endif %} diff --git a/translations/zh-CN/content/get-started/quickstart/create-a-repo.md b/translations/zh-CN/content/get-started/quickstart/create-a-repo.md index abe1b6978b..06048bb4fd 100644 --- a/translations/zh-CN/content/get-started/quickstart/create-a-repo.md +++ b/translations/zh-CN/content/get-started/quickstart/create-a-repo.md @@ -1,11 +1,11 @@ --- -title: 创建存储库 +title: Create a repo redirect_from: - /create-a-repo - /articles/create-a-repo - /github/getting-started-with-github/create-a-repo - /github/getting-started-with-github/quickstart/create-a-repo -intro: '若要将项目放在 {% data variables.product.prodname_dotcom %} 上,需要创建一个存储库来存放它。' +intro: 'To put your project up on {% data variables.product.prodname_dotcom %}, you will need to create a repository for it to live in.' versions: fpt: '*' ghes: '*' @@ -16,22 +16,16 @@ topics: - Issues - Notifications - Accounts -ms.openlocfilehash: 66db99def4463929236197fdc4903f82bfc1cbe2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146682291' --- -## 创建存储库 +## Create a repository {% ifversion fpt or ghec %} -可以在 {% data variables.product.prodname_dotcom %} 存储库中存储各种项目,包括开源项目。 通过开源项目,可以共享代码以开发更好、更可靠的软件。 您可以使用仓库与他人协作并跟踪您的工作。 有关详细信息,请参阅[关于存储库](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)。 若要详细了解开放源代码项目,请访问 [OpenSource.org](https://opensource.org/about)。 +You can store a variety of projects in {% data variables.product.prodname_dotcom %} repositories, including open source projects. With open source projects, you can share code to make better, more reliable software. You can use repositories to collaborate with others and track your work. For more information, see "[About repositories](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)." To learn more about open source projects, visit [OpenSource.org](https://opensource.org/about). {% elsif ghes or ghae %} -您可以在 {% data variables.product.product_name %} 仓库中存储各种项目,包括内部来源项目。 通过内部源代码,您可以分享代码来获取更好、更可靠的软件。 有关内部来源的详细信息,请参阅 {% data variables.product.company_short %} 的白皮书[内部来源简介](https://resources.github.com/whitepapers/introduction-to-innersource/)。 +You can store a variety of projects in {% data variables.product.product_name %} repositories, including innersource projects. With innersource, you can share code to make better, more reliable software. For more information on innersource, see {% data variables.product.company_short %}'s white paper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)." {% endif %} @@ -39,10 +33,10 @@ ms.locfileid: '146682291' {% note %} -**注意:** -- 可以为开放源代码项目创建公共存储库。 创建公共存储库时,请确保包含一个[许可文件](https://choosealicense.com/),用于界定你希望与他人共享自己项目的方式。 {% data reusables.open-source.open-source-guide-repositories %} +**Notes:** +- You can create public repositories for an open source project. When creating your public repository, make sure to include a [license file](https://choosealicense.com/) that determines how you want your project to be shared with others. {% data reusables.open-source.open-source-guide-repositories %} - {% data reusables.open-source.open-source-learning %} -- 还可以将社区运行状况文件添加到存储库中,以设置有关如何参与、保护存储库安全等的准则。 有关详细信息,请参阅[创建默认社区运行状况文件](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)。 +- You can also add community health files to your repositories, to set guidelines on how to contribute, keep your repositories safe, and much more. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." {% endnote %} @@ -51,12 +45,15 @@ ms.locfileid: '146682291' {% webui %} {% data reusables.repositories.create_new %} -2. 为存储库键入简短好记的名称。 例如 "hello-world"。 - ![用于输入存储库名称的字段](/assets/images/help/repository/create-repository-name.png) -3. 可以选择性地添加存储库的说明。 例如,“我在 {% data variables.product.product_name %} 上的第一个仓库”。 - ![用于输入存储库说明的字段](/assets/images/help/repository/create-repository-desc.png) {% data reusables.repositories.choose-repo-visibility %} {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %} +2. Type a short, memorable name for your repository. For example, "hello-world". + ![Field for entering a repository name](/assets/images/help/repository/create-repository-name.png) +3. Optionally, add a description of your repository. For example, "My first repository on {% data variables.product.product_name %}." + ![Field for entering a repository description](/assets/images/help/repository/create-repository-desc.png) +{% data reusables.repositories.choose-repo-visibility %} +{% data reusables.repositories.initialize-with-readme %} +{% data reusables.repositories.create-repo %} -恭喜! 你已经成功创建了第一个存储库,并使用自述文件对其进行了初始化。 +Congratulations! You've successfully created your first repository, and initialized it with a *README* file. {% endwebui %} @@ -64,47 +61,51 @@ ms.locfileid: '146682291' {% data reusables.cli.cli-learn-more %} -1. 在命令行中,导航到要在其中创建新项目的本地克隆的目录。 -2. 若要为项目创建存储库,请使用 `gh repo create` 子命令。 出现提示时,选择“从头开始在 GitHub 上创建新存储库”,然后输入新项目的名称 如果希望项目属于某个组织而不是你的个人帐户,请使用 `organization-name/project-name` 指定组织名称和项目名称。 -3. 按照交互式提示进行操作。 要在本地克隆存储库,请在询问您是否要克隆远程项目目录时确认是。 -4. 或者,若要跳过提示,请提供存储库名称和可见性标志(`--public`、`--private` 或 `--internal`)。 例如 `gh repo create project-name --public`。 若要在本地克隆存储库,请传递 `--clone` 标志。 有关可能的参数的详细信息,请参阅 [GitHub CLI 手册](https://cli.github.com/manual/gh_repo_create)。 +1. In the command line, navigate to the directory where you would like to create a local clone of your new project. +2. To create a repository for your project, use the `gh repo create` subcommand. When prompted, select **Create a new repository on GitHub from scratch** and enter the name of your new project. If you want your project to belong to an organization instead of to your personal account, specify the organization name and project name with `organization-name/project-name`. +3. Follow the interactive prompts. To clone the repository locally, confirm yes when asked if you would like to clone the remote project directory. +4. Alternatively, to skip the prompts supply the repository name and a visibility flag (`--public`, `--private`, or `--internal`). For example, `gh repo create project-name --public`. To clone the repository locally, pass the `--clone` flag. For more information about possible arguments, see the [GitHub CLI manual](https://cli.github.com/manual/gh_repo_create). {% endcli %} -## 提交您的第一个更改 +## Commit your first change {% webui %} -*[提交](/articles/github-glossary#commit)* 就像是项目中所有文件在特定时间点的快照。 +A *[commit](/articles/github-glossary#commit)* is like a snapshot of all the files in your project at a particular point in time. -创建新存储库时,你使用自述文件对其进行了初始化。 README 文件用于更详细地描述项目或添加一些指南性文档(例如如何安装或使用项目)。 README 文件的内容会自动显示在存储库的首页上。 +When you created your new repository, you initialized it with a *README* file. *README* files are a great place to describe your project in more detail, or add some documentation such as how to install or use your project. The contents of your *README* file are automatically shown on the front page of your repository. -让我们提交对自述文件的更改。 +Let's commit a change to the *README* file. -1. 在存储库的文件列表中,单击“README.md”。 - ![文件列表中的自述文件](/assets/images/help/repository/create-commit-open-readme.png) -2. 在文件内容上方,单击 {% octicon "pencil" aria-label="The edit icon" %}。 -3. 在“编辑文件”选项卡上,键入一些关于你自己的信息。 - ![文件中的新内容](/assets/images/help/repository/edit-readme-light.png) {% data reusables.files.preview_change %} -5. 查看您对文件所做的更改。 你会看到新内容以绿色显示。 - ![文件预览视图](/assets/images/help/repository/create-commit-review.png) {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} +1. In your repository's list of files, click ***README.md***. + ![README file in file list](/assets/images/help/repository/create-commit-open-readme.png) +2. Above the file's content, click {% octicon "pencil" aria-label="The edit icon" %}. +3. On the **Edit file** tab, type some information about yourself. + ![New content in file](/assets/images/help/repository/edit-readme-light.png) +{% data reusables.files.preview_change %} +5. Review the changes you made to the file. You will see the new content in green. + ![File preview view](/assets/images/help/repository/create-commit-review.png) +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} +{% data reusables.files.propose_file_change %} {% endwebui %} {% cli %} -创建项目后,可以开始提交更改。 +Now that you have created a project, you can start committing changes. -README 文件用于更详细地描述项目或添加一些指南性文档(例如如何安装或使用项目)。 README 文件的内容会自动显示在存储库的首页上。 按照以下步骤添加一个自述文件。 +*README* files are a great place to describe your project in more detail, or add some documentation such as how to install or use your project. The contents of your *README* file are automatically shown on the front page of your repository. Follow these steps to add a *README* file. -1. 在命令行中,导航到新项目的根目录。 (此目录是在运行 `gh repo create` 命令时创建的。) -1. 创建自述文件,其中包含有关项目的一些信息。 +1. In the command line, navigate to the root directory of your new project. (This directory was created when you ran the `gh repo create` command.) +1. Create a *README* file with some information about the project. ```shell echo "info about this project" >> README.md ``` -1. 输入 `git status`。 你会看到你有一个未跟踪的 `README.md` 文件。 +1. Enter `git status`. You will see that you have an untracked `README.md` file. ```shell $ git status @@ -116,13 +117,13 @@ README 文件用于更详细地描述项目或添加一些指南性文档(例 nothing added to commit but untracked files present (use "git add" to track) ``` -1. 暂存并提交文件。 +1. Stage and commit the file. ```shell git add README.md && git commit -m "Add README" ``` -1. 将更改推送到您的分支。 +1. Push the changes to your branch. ```shell git push --set-upstream origin HEAD @@ -130,17 +131,17 @@ README 文件用于更详细地描述项目或添加一些指南性文档(例 {% endcli %} -## 后续步骤 +## Next steps -你现在已经创建了一个存储库,其中包括自述文件,并在 {% data variables.product.product_location %} 上创建了你的第一个提交。 +You have now created a repository, including a *README* file, and created your first commit on {% data variables.location.product_location %}. {% webui %} -* 现在可以克隆 {% data variables.product.prodname_dotcom %} 存储库以在计算机上创建本地副本。 从您的本地仓库,您可以提交并创建拉取请求来更新上游仓库中的更改。 有关详细信息,请参阅[克隆存储库](/github/creating-cloning-and-archiving-repositories/cloning-a-repository)和[设置 Git](/articles/set-up-git)。 +* You can now clone a {% data variables.product.prodname_dotcom %} repository to create a local copy on your computer. From your local repository you can commit, and create a pull request to update the changes in the upstream repository. For more information, see "[Cloning a repository](/github/creating-cloning-and-archiving-repositories/cloning-a-repository)" and "[Set up Git](/articles/set-up-git)." {% endwebui %} -* 可以在 {% data variables.product.prodname_dotcom %} 上找到有趣的项目和存储库,并通过创建存储库分支来更改它们。 {% data reusables.getting-started.fork-a-repository %} +* You can find interesting projects and repositories on {% data variables.product.prodname_dotcom %} and make changes to them by creating a fork of the repository. {% data reusables.getting-started.fork-a-repository %} * {% data reusables.getting-started.being-social %} diff --git a/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md b/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md index 89188ac27b..ad5ed4621b 100644 --- a/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md +++ b/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md @@ -1,12 +1,12 @@ --- -title: 创建存储库分支 +title: Fork a repo redirect_from: - /fork-a-repo - /forking - /articles/fork-a-repo - /github/getting-started-with-github/fork-a-repo - /github/getting-started-with-github/quickstart/fork-a-repo -intro: 分叉是存储库的副本。 通过复刻仓库,您可以自由地尝试更改而不会影响原始项目。 +intro: A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project. permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}' versions: fpt: '*' @@ -18,67 +18,61 @@ topics: - Issues - Notifications - Accounts -ms.openlocfilehash: b6f98f30c67f14fab1da3658e42e8eba67f5f50c -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717571' --- -## 关于分叉 +## About forks -最常见的是,分支用于对其他人的项目提出你没有写入权限的项目的更改,或者使用其他人的项目作为你自己想法的起点。 您可以复刻仓库以创建仓库的副本,并在不影响上游仓库的情况下进行更改。 有关详细信息,请参阅“[使用分支](/github/collaborating-with-issues-and-pull-requests/working-with-forks)”。 +Most commonly, forks are used to either propose changes to someone else's project to which you do not have write access, or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)." -### 对其他人的项目提出更改 +### Propose changes to someone else's project -例如,可以使用复刻提出与修复 Bug 相关的更改。 无需为你发现的漏洞创建问题,你可以: +For example, you can use forks to propose changes related to fixing a bug. Rather than logging an issue for a bug you have found, you can: -- 创建存储库分支。 -- 进行修复 -- 向项目所有者提交拉取请求。 +- Fork the repository. +- Make the fix. +- Submit a pull request to the project owner. -### 将其他人的项目用作自己创意的起点。 +### Use someone else's project as a starting point for your own idea. -开源软件的理念是通过共享代码,可以开发出更好、更可靠的软件。 有关详细信息,请参阅开放源代码计划上的“[关于开放源代码计划](https://opensource.org/about)”。 +Open source software is based on the idea that by sharing code, we can make better, more reliable software. For more information, see the "[About the Open Source Initiative](https://opensource.org/about)" on the Open Source Initiative. -有关将开放源代码原则应用于组织在 {% data variables.product.product_location %} 上的开发工作的详细信息,请参阅 {% data variables.product.prodname_dotcom %} 的白皮书“[内部源简介](https://resources.github.com/whitepapers/introduction-to-innersource/)”。 +For more information about applying open source principles to your organization's development work on {% data variables.location.product_location %}, see {% data variables.product.prodname_dotcom %}'s white paper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)." {% ifversion fpt or ghes or ghec %} -从其他人的项目复刻创建公共仓库时,请确保包含许可文件以确定您希望与其他人共享项目。 有关详细信息,请参阅 choosealicense 上的“[选择开放源代码许可](https://choosealicense.com/)”。 +When creating your public repository from a fork of someone's project, make sure to include a license file that determines how you want your project to be shared with others. For more information, see "[Choose an open source license](https://choosealicense.com/)" at choosealicense.com. {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning %} {% endif %} -## 先决条件 +## Prerequisites -如果尚未设置,应首先 [设置 Git](/articles/set-up-git)。 不要忘记[从 Git 向 {% data variables.product.product_location %} 设置身份验证](/articles/set-up-git#next-steps-authenticating-with-github-from-git)。 +If you have not yet, you should first [set up Git](/articles/set-up-git). Don't forget to [set up authentication to {% data variables.location.product_location %} from Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git) as well. -## 复刻仓库 +## Forking a repository {% webui %} -您可能为了对上游或原始仓库提议更改而复刻项目。 在这种情况下,最好定期将您的复刻与上游仓库同步。 为此,您需要在命令行上使用 Git。 可以使用刚才已创建分支的同一 [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) 存储库来练习设置上游存储库。 +You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked. -1. 在 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %} 上,导航到 [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) 存储库。 -2. 在页面右上角,单击“分支”。 - ![分支按钮](/assets/images/help/repository/fork_button.png) -3. 为分支存储库选择所有者。 - ![创建一个突出显示所有者下拉菜单的新分支页](/assets/images/help/repository/fork-choose-owner.png) -4. 默认情况下,分支的名称与其父存储库的相同。 可更改分支的名称以进一步区分它。 - ![创建一个突出显示存储库名称字段的新分支页](/assets/images/help/repository/fork-choose-repo-name.png) -5. 可以选择性地添加分支的说明。 - ![创建一个突出显示说明字段的新分支页](/assets/images/help/repository/fork-description.png) -6. 选择是仅将默认分支还是将所有分支复制到新分支。 对于许多分支场景(例如参与开源项目),你只需复制默认分支。 默认情况下,只复制默认分支。 - ![只复制默认分支的选项](/assets/images/help/repository/copy-default-branch-only.png) -7. 单击“创建分支”。 - ![突出显示的“创建分支”按钮](/assets/images/help/repository/fork-create-button.png) +1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository. +2. In the top-right corner of the page, click **Fork**. + ![Fork button](/assets/images/help/repository/fork_button.png) +3. Select an owner for the forked repository. + ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png) +4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further. + ![Create a new fork page with repository name field emphasized](/assets/images/help/repository/fork-choose-repo-name.png) +5. Optionally, add a description of your fork. + ![Create a new fork page with description field emphasized](/assets/images/help/repository/fork-description.png) +6. Choose whether to copy only the default branch or all branches to the new fork. For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. By default, only the default branch is copied. + ![Option to copy only the default branch](/assets/images/help/repository/copy-default-branch-only.png) +7. Click **Create fork**. + ![Emphasized create fork button](/assets/images/help/repository/fork-create-button.png) {% note %} -注意:如果要从父存储库复制其他分支,可从“分支”页执行此操作 。 有关详细信息,请参阅“[在存储库中创建和删除分支](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)”。{% endnote %} +**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %} {% endwebui %} @@ -86,38 +80,41 @@ ms.locfileid: '147717571' {% data reusables.cli.cli-learn-more %} -若要创建存储库的分支,请使用 `gh repo fork` 子命令。 +To create a fork of a repository, use the `gh repo fork` subcommand. ```shell -gh repo fork repository +gh repo fork REPOSITORY ``` -若要在组织中创建分支,请使用 `--org` 标记。 +To create the fork in an organization, use the `--org` flag. ```shell -gh repo fork repository --org "octo-org" +gh repo fork REPOSITORY --org "octo-org" ``` {% endcli %} -{% desktop %} {% enddesktop %} +{% desktop %} +{% enddesktop %} -## 克隆复刻的仓库 +## Cloning your forked repository -现在,你有了 Spoon-Knife 存储库的分支,但你的计算机本地还没有该存储库中的文件。 +Right now, you have a fork of the Spoon-Knife repository, but you do not have the files in that repository locally on your computer. {% webui %} -1. 在 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %} 上,导航到 Spoon-Knife 存储库的分支。 -{% data reusables.repositories.copy-clone-url %} {% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.change-current-directory-clone %} -4. 键入 `git clone`,然后粘贴之前复制的 URL。 它将如下所示,使用你的 {% data variables.product.product_name %} 用户名替换 `YOUR-USERNAME`: +1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to **your fork** of the Spoon-Knife repository. +{% data reusables.repositories.copy-clone-url %} +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.command_line.change-current-directory-clone %} +4. Type `git clone`, and then paste the URL you copied earlier. It will look like this, with your {% data variables.product.product_name %} username instead of `YOUR-USERNAME`: ```shell - $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife + $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife ``` -5. 按 **Enter**。 将创建您的本地克隆。 +5. Press **Enter**. Your local clone will be created. ```shell - $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife + $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife > Cloning into `Spoon-Knife`... > remote: Counting objects: 10, done. > remote: Compressing objects: 100% (8/8), done. @@ -131,55 +128,60 @@ gh repo fork repository --org "octo-org" {% data reusables.cli.cli-learn-more %} -若要创建分支的克隆,请使用 `--clone` 标记。 +To create a clone of your fork, use the `--clone` flag. ```shell -gh repo fork repository --clone=true +gh repo fork REPOSITORY --clone=true ``` {% endcli %} {% desktop %} -{% 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.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 %} {% enddesktop %} -## 配置 Git 以将您的复刻与原始仓库同步 +## Configuring Git to sync your fork with the original repository -为了对原始仓库提议更改而复刻项目时,您可以配置 Git 以将更改从原始或上游仓库拉取到复刻的本地克隆。 +When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork. {% webui %} -1. 在 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %} 上,导航到 [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) 存储库。 -{% data reusables.repositories.copy-clone-url %} {% data reusables.command_line.open_the_multi_os_terminal %} -4. 将目录更改为您克隆的复刻的位置。 - - 若要转到主目录,请只键入 `cd`,不要键入其他文本。 - - 若要列出当前目录中的文件和文件夹,请键入 `ls`。 - - 若要进入列出的某个目录,请键入 `cd your_listed_directory`。 - - 若要回到上一个目录,请键入 `cd ..`。 -5. 键入 `git remote -v`,然后按“Enter”。 你将看到当前为分支配置的远程存储库。 +1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository. +{% data reusables.repositories.copy-clone-url %} +{% data reusables.command_line.open_the_multi_os_terminal %} +4. Change directories to the location of the fork you cloned. + - To go to your home directory, type just `cd` with no other text. + - To list the files and folders in your current directory, type `ls`. + - To go into one of your listed directories, type `cd your_listed_directory`. + - To go up one directory, type `cd ..`. +5. Type `git remote -v` and press **Enter**. You will see the current configured remote repository for your fork. ```shell $ git remote -v - > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) ``` -6. 键入 `git remote add upstream`,然后粘贴在步骤 3 中复制的 URL,然后按 Enter。 它将如下所示: +6. Type `git remote add upstream`, and then paste the URL you copied in Step 3 and press **Enter**. It will look like this: ```shell $ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/Spoon-Knife.git ``` -7. 若要验证为分支指定的新上游存储库,请再次键入 `git remote -v`。 你应该会看到分支的 URL 为 `origin`,原始存储库的 URL 为 `upstream`。 +7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`. ```shell $ git remote -v - > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) - > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (fetch) - > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (push) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/ YOUR_FORK.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ ORIGINAL_REPOSITORY.git (fetch) + > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ ORIGINAL_REPOSITORY.git (push) ``` -现在,您可以使用一些 Git 命令使您的复刻与上游仓库保持同步。 有关详细信息,请参阅“[同步分支](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)”。 +Now, you can keep your fork synced with the upstream repository with a few Git commands. For more information, see "[Syncing a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)." {% endwebui %} @@ -187,41 +189,41 @@ gh repo fork repository --clone=true {% data reusables.cli.cli-learn-more %} -若要为分支存储库配置远程存储库,请使用 `--remote` 标志。 +To configure a remote repository for the forked repository, use the `--remote` flag. ```shell -gh repo fork repository --remote=true +gh repo fork REPOSITORY --remote=true ``` -若要指定远程存储库的名称,请使用 `--remote-name` 标志。 +To specify the remote repository's name, use the `--remote-name` flag. ```shell -gh repo fork repository --remote-name "main-remote-repo" +gh repo fork REPOSITORY --remote-name "main-remote-repo" ``` {% endcli %} -### 编辑分支 +### Editing a fork -您可以对复刻进行任何更改,包括: +You can make any changes to a fork, including: -- 创建分支:[分支](/articles/creating-and-deleting-branches-within-your-repository/)支持在不影响主项目的情况下构建新功能或测试创意。 -- 打开拉取请求:如果希望回馈原始存储库,可以通过提交[拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests),请求原作者将你的分支拉取到他们的存储库。 +- **Creating branches:** [*Branches*](/articles/creating-and-deleting-branches-within-your-repository/) allow you to build new features or test out ideas without putting your main project at risk. +- **Opening pull requests:** If you are hoping to contribute back to the original repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests). -## 另找一个仓库进行复刻 -复刻仓库,开始参与项目。 {% data reusables.repositories.you-can-fork %} +## Find another repository to fork +Fork a repository to start contributing to a project. {% data reusables.repositories.you-can-fork %} -{% ifversion fpt or ghec %}你可以查看[浏览](https://github.com/explore),查找项目并开始参与开放源代码存储库。 有关详细信息,请参阅“[查找为 {% data variables.product.prodname_dotcom %} 上的开放源代码做贡献的方式](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)”。 +{% ifversion fpt or ghec %}You can browse [Explore](https://github.com/explore) to find projects and start contributing to open source repositories. For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)." {% endif %} -## 后续步骤 +## Next Steps -您现在已经复刻了仓库、练习了克隆复刻并配置了上游仓库。 +You have now forked a repository, practiced cloning your fork, and configured an upstream repository. -* 有关克隆分支和从计算机同步分支存储库更改的详细信息,请参阅“[设置 Git](/articles/set-up-git)”。 +* For more information about cloning the fork and syncing the changes in a forked repository from your computer, see "[Set up Git](/articles/set-up-git)." -* 您也可以创建一个新的仓库,以将所有项目放在 {% data variables.product.prodname_dotcom %} 上并共享代码。 {% data reusables.getting-started.create-a-repository %}" +* You can also create a new repository where you can put all your projects and share the code on {% data variables.product.prodname_dotcom %}. {% data reusables.getting-started.create-a-repository %}" * {% data reusables.getting-started.being-social %} diff --git a/translations/zh-CN/content/get-started/signing-up-for-github/verifying-your-email-address.md b/translations/zh-CN/content/get-started/signing-up-for-github/verifying-your-email-address.md index 2fb724658a..64e0ef6f88 100644 --- a/translations/zh-CN/content/get-started/signing-up-for-github/verifying-your-email-address.md +++ b/translations/zh-CN/content/get-started/signing-up-for-github/verifying-your-email-address.md @@ -1,6 +1,6 @@ --- -title: 验证电子邮件地址 -intro: '验证主电子邮件地址可确保增强的安全性,以便 {% data variables.product.prodname_dotcom %} 员工在您忘记密码时更好地协助您,并为您提供 {% data variables.product.prodname_dotcom %} 上更多功能的访问权限。' +title: Verifying your email address +intro: 'Verifying your primary email address ensures strengthened security, allows {% data variables.product.prodname_dotcom %} staff to better assist you if you forget your password, and gives you access to more features on {% data variables.product.prodname_dotcom %}.' redirect_from: - /articles/troubleshooting-email-verification - /articles/setting-up-email-verification @@ -13,64 +13,59 @@ versions: topics: - Accounts shortTitle: Verify your email address -ms.openlocfilehash: 75c455907ab0cc89f1ba8b30d6fa1d37f2d9798f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145109496' --- -## 关于电子邮件通知 +## About email verification -您可在注册新帐户后或添加新电子邮件地址时验证您的电子邮件地址。 如果电子邮件地址无法送达或退回,它将无法进行验证。 +You can verify your email address after signing up for a new account, or when you add a new email address. If an email address is undeliverable or bouncing, it will be unverified. -如果没有验证电子邮件地址,您将无法: - - 创建或复刻仓库 - - 创建议题或拉取请求 - - 对议题、拉取请求或提交发表评论 - - 授权 {% data variables.product.prodname_oauth_app %} 应用程序 - - 生成个人访问令牌 - - 接收电子邮件通知 - - 对仓库加星标 - - 创建或更新项目板,包括添加卡片 - - 创建或更新 gist - - 创建或使用 {% data variables.product.prodname_actions %} - - 通过 {% data variables.product.prodname_sponsors %} 赞助开发者 +If you do not verify your email address, you will not be able to: + - Create or fork repositories + - Create issues or pull requests + - Comment on issues, pull requests, or commits + - Authorize {% data variables.product.prodname_oauth_app %} applications + - Generate {% data variables.product.pat_generic %}s + - Receive email notifications + - Star repositories + - Create or update project boards, including adding cards + - Create or update gists + - Create or use {% data variables.product.prodname_actions %} + - Sponsor developers with {% data variables.product.prodname_sponsors %} {% warning %} -**警告**: +**Warnings**: - {% data reusables.user-settings.no-verification-disposable-emails %} - {% data reusables.user-settings.verify-org-approved-email-domain %} {% endwarning %} -## 验证电子邮件地址 +## Verifying your email address -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.emails %} -1. 在电子邮件地址下,单击“重新发送验证电子邮件”。 - ![重新发送验证电子邮件链接](/assets/images/help/settings/email-verify-button.png) -4. {% data variables.product.prodname_dotcom %} 将向您发送一封含有链接的电子邮件。 单击该链接后,您将转到 {% data variables.product.prodname_dotcom %} 仪表板并看到确认横幅。 - ![确认电子邮件已验证的横幅](/assets/images/help/settings/email-verification-confirmation-banner.png) +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.emails %} +1. Under your email address, click **Resend verification email**. + ![Resend verification email link](/assets/images/help/settings/email-verify-button.png) +4. {% data variables.product.prodname_dotcom %} will send you an email with a link in it. After you click that link, you'll be taken to your {% data variables.product.prodname_dotcom %} dashboard and see a confirmation banner. + ![Banner confirming that your email was verified](/assets/images/help/settings/email-verification-confirmation-banner.png) -## 电子邮件验证故障排除 +## Troubleshooting email verification -### 无法发送验证电子邮件 +### Unable to send verification email {% data reusables.user-settings.no-verification-disposable-emails %} -### 单击验证链接后的错误页面 +### Error page after clicking verification link -验证链接将在 24 小时后过期。 如果您没有在 24 小时内验证电子邮件,则可以请求其他电子邮件验证链接。 有关详细信息,请参阅“[验证电子邮件地址](/articles/verifying-your-email-address)”。 +The verification link expires after 24 hours. If you don't verify your email within 24 hours, you can request another email verification link. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)." -如果您在 24 小时内单击了确认电子邮件中的链接并被定向到错误页面,则应确保您已登录到 {% data variables.product.product_location %} 上正确的帐户。 +If you click on the link in the confirmation email within 24 hours and you are directed to an error page, you should ensure that you're signed into the correct account on {% data variables.location.product_location %}. -1. 您在 {% data variables.product.product_location %} 上的个人帐户的 {% data variables.product.signout_link %}。 -2. 退出并重新启动浏览器。 -3. 您在 {% data variables.product.product_location %} 上的个人帐户的 {% data variables.product.signin_link %}。 -4. 单击我们发送给您的电子邮件中的验证链接。 +1. {% data variables.product.signout_link %} of your personal account on {% data variables.location.product_location %}. +2. Quit and restart your browser. +3. {% data variables.product.signin_link %} to your personal account on {% data variables.location.product_location %}. +4. Click on the verification link in the email we sent you. -## 延伸阅读 +## Further reading -- [更改主电子邮件地址](/articles/changing-your-primary-email-address) +- "[Changing your primary email address](/articles/changing-your-primary-email-address)" diff --git a/translations/zh-CN/content/get-started/using-git/about-git-rebase.md b/translations/zh-CN/content/get-started/using-git/about-git-rebase.md index f7efe85e38..07389b8bb1 100644 --- a/translations/zh-CN/content/get-started/using-git/about-git-rebase.md +++ b/translations/zh-CN/content/get-started/using-git/about-git-rebase.md @@ -1,5 +1,5 @@ --- -title: 关于 Git 变基 +title: About Git rebase redirect_from: - /rebase - /articles/interactive-rebase @@ -7,74 +7,68 @@ redirect_from: - /github/using-git/about-git-rebase - /github/getting-started-with-github/about-git-rebase - /github/getting-started-with-github/using-git/about-git-rebase -intro: '`git rebase` 命令用于轻松更改一系列提交,修改存储库的历史记录。 您可以重新排序、编辑提交或将提交压缩到一起。' +intro: 'The `git rebase` command allows you to easily change a series of commits, modifying the history of your repository. You can reorder, edit, or squash commits together.' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' -ms.openlocfilehash: 5ffa3cbb1fcb6c8c37e56e434b08018582a0ff2b -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145098889' --- -通常,你会使用 `git rebase` 来: +Typically, you would use `git rebase` to: -* 编辑之前的提交消息 -* 将多个提交合并为一个 -* 删除或还原不再必要的提交 +* Edit previous commit messages +* Combine multiple commits into one +* Delete or revert commits that are no longer necessary {% warning %} -警告:由于更改提交历史记录可能会给其他人使用存储库造成困难,因此如果提交已经推送到存储库,建议不要执行提交变基。 若要了解如何在 {% data variables.product.product_location %} 上安全地变基,请参阅“[关于拉取请求合并](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)”。 +**Warning**: Because changing your commit history can make things difficult for everyone else using the repository, it's considered bad practice to rebase commits when you've already pushed to a repository. To learn how to safely rebase on {% data variables.location.product_location %}, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)." {% endwarning %} -## 对分支变基提交 +## Rebasing commits against a branch -要对另一个分支与当前分支状态之间的所有提交变基,可以在 shell(Windows 的命令提示符或者 Mac 和 Linux 的终端)中输入以下命令: +To rebase all the commits between another branch and the current branch state, you can enter the following command in your shell (either the command prompt for Windows, or the terminal for Mac and Linux): ```shell -$ git rebase --interactive other_branch_name +$ git rebase --interactive OTHER-BRANCH-NAME ``` -## 对某一时间点变基提交 +## Rebasing commits against a point in time -要变基当前分支中最近的几个提交,可以在 shell 中输入以下命令: +To rebase the last few commits in your current branch, you can enter the following command in your shell: ```shell $ git rebase --interactive HEAD~7 ``` -## 变基时可用的命令 +## Commands available while rebasing -变基时有六个命令可用: +There are six commands available while rebasing:
pick
-
pick 只表示包含提交。 在变基进行时重新排列 pick 命令的顺序会更改提交的顺序。 如果选择不包含提交,应删除整行。
+
pick simply means that the commit is included. Rearranging the order of the pick commands changes the order of the commits when the rebase is underway. If you choose not to include a commit, you should delete the entire line.
reword
-
reword 命令类似于 pick,但在使用后,变基过程就会暂停,让你有机会改变提交消息。 提交所做的任何更改都不受影响。
+
The reword command is similar to pick, but after you use it, the rebase process will pause and give you a chance to alter the commit message. Any changes made by the commit are not affected.
edit
-
如果选择 edit 提交,你将有机会修订提交,也就是说,可以完全添加或更改提交。 您也可以创建更多提交后再继续变基。 这样您可以将大提交拆分为小提交,或者删除在提交中执行错误更改。
+
If you choose to edit a commit, you'll be given the chance to amend the commit, meaning that you can add or change the commit entirely. You can also make more commits before you continue the rebase. This allows you to split a large commit into smaller ones, or, remove erroneous changes made in a commit.
squash
-
此命令可用于将两个或以上的提交合并为一个。 下面的提交压缩到其上面的提交。 Git 让您有机会编写描述两次更改的新提交消息。
+
This command lets you combine two or more commits into a single commit. A commit is squashed into the commit above it. Git gives you the chance to write a new commit message describing both changes.
fixup
-
这类似于 squash,但要合并的提交丢弃了其消息。 提交只是合并到其上面的提交,之前提交的消息用于描述两次更改。
+
This is similar to squash, but the commit to be merged has its message discarded. The commit is simply merged into the commit above it, and the earlier commit's message is used to describe both changes.
exec
-
这可让您对提交运行任意 shell 命令。
+
This lets you run arbitrary shell commands against a commit.
-## 使用 `git rebase` 的示例 +## An example of using `git rebase` -无论使用哪个命令,Git 都将启动[默认文本编辑器](/github/getting-started-with-github/associating-text-editors-with-git),并且打开一个文件,其中详细说明了所选范围的提交信息。 该文件类似于: +No matter which command you use, Git will launch [your default text editor](/github/getting-started-with-github/associating-text-editors-with-git) and open a file that details the commits in the range you've chosen. That file looks something like this: ``` pick 1fc6c95 Patch A @@ -100,18 +94,18 @@ pick 7b36971 something to move before patch B # ``` -从上到下分解此信息,我们可以看出: +Breaking this information, from top to bottom, we see that: -- 列出了七个命令,表示从起点到当前分支状态之间有七处更改。 -- 您选择要变基的提交按最早更改(顶部)到最新更改(底部)的顺序存储。 -- 每行列出一个命令(默认为 `pick`)、提交 SHA 和提交消息。 整个 `git rebase` 过程以这三列的操作为中心。 做出的更改将变基到存储库。 -- 提交后,Git 会告知正在处理的提交范围 (`41a72e6..7b36971`)。 -- 最后,Git 会提供一些帮助,告知在变基提交时可用的命令。 +- Seven commits are listed, which indicates that there were seven changes between our starting point and our current branch state. +- The commits you chose to rebase are sorted in the order of the oldest changes (at the top) to the newest changes (at the bottom). +- Each line lists a command (by default, `pick`), the commit SHA, and the commit message. The entire `git rebase` procedure centers around your manipulation of these three columns. The changes you make are *rebased* onto your repository. +- After the commits, Git tells you the range of commits we're working with (`41a72e6..7b36971`). +- Finally, Git gives some help by telling you the commands that are available to you when rebasing commits. -## 延伸阅读 +## Further reading -- [使用 Git 变基](/articles/using-git-rebase) -- [Pro Git 书籍中的“Git 分支”一章](https://git-scm.com/book/en/Git-Branching-Rebasing) -- [Pro Git 书籍中的“交互式变基”一章](https://git-scm.com/book/en/Git-Tools-Rewriting-History#_changing_multiple) -- [使用变基压缩提交](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html) -- {% data variables.product.prodname_desktop %} 文档中的“[同步分支](/desktop/contributing-to-projects/syncing-your-branch)” +- "[Using Git rebase](/articles/using-git-rebase)" +- [The "Git Branching" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Branching-Rebasing) +- [The "Interactive Rebasing" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Tools-Rewriting-History#_changing_multiple) +- "[Squashing commits with rebase](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)" +- "[Syncing your branch](/desktop/contributing-to-projects/syncing-your-branch)" in the {% data variables.product.prodname_desktop %} documentation diff --git a/translations/zh-CN/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/translations/zh-CN/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md index e825a01c7c..672cc12698 100644 --- a/translations/zh-CN/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md +++ b/translations/zh-CN/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md @@ -1,49 +1,43 @@ --- -title: 将子文件夹拆分成新仓库 +title: Splitting a subfolder out into a new repository redirect_from: - /articles/splitting-a-subpath-out-into-a-new-repository - /articles/splitting-a-subfolder-out-into-a-new-repository - /github/using-git/splitting-a-subfolder-out-into-a-new-repository - /github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository - /github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository -intro: 您可以将 Git 仓库内的文件夹变为全新的仓库。 +intro: You can turn a folder within a Git repository into a brand new repository. versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' shortTitle: Splitting a subfolder -ms.openlocfilehash: 21467b459f1e7af1dd28e5b7a20c962786aed2b5 -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147876072' --- -如果您创建仓库的新克隆副本,则将文件夹拆分为单独的仓库时不会丢失任何 Git 历史记录或更改。 +If you create a new clone of the repository, you won't lose any of your Git history or changes when you split a folder into a separate repository. {% data reusables.command_line.open_the_multi_os_terminal %} -2. 将当前工作目录更改为您要创建新仓库的位置。 +2. Change the current working directory to the location where you want to create your new repository. -4. 克隆包含该子文件夹的仓库。 +4. Clone the repository that contains the subfolder. ```shell - $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME + $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME ``` -4. 将当前工作目录更改为您克隆的仓库。 +4. Change the current working directory to your cloned repository. ```shell - $ cd REPOSITORY-NAME + $ cd REPOSITORY-NAME ``` -5. 若要从存储库中的其余文件中筛选出子文件夹,请运行 [`git filter-repo`](https://github.com/newren/git-filter-repo),并提供以下信息: - - `FOLDER-NAME`:项目中要在其中创建单独存储库的文件夹。 +5. To filter out the subfolder from the rest of the files in the repository, run [`git filter-repo`](https://github.com/newren/git-filter-repo), supplying this information: + - `FOLDER-NAME`: The folder within your project where you'd like to create a separate repository. {% windows %} {% tip %} - 提示:Windows 用户应使用 `/` 来分隔文件夹。 + **Tip:** Windows users should use `/` to delimit folders. {% endtip %} @@ -53,44 +47,44 @@ ms.locfileid: '147876072' $ git filter-repo --path FOLDER-NAME1/ --path FOLDER-NAME2/ # Filter the specified branch in your directory and remove empty commits > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89) - > Ref 'refs/heads/BRANCH-NAME' was rewritten + > Ref 'refs/heads/BRANCH-NAME' was rewritten ``` - 现在,该仓库应仅包含您的子文件夹中的文件。 + The repository should now only contain the files that were in your subfolder(s). -6. 在 {% data variables.product.product_name %} 上[新建存储库](/articles/creating-a-new-repository/)。 +6. [Create a new repository](/articles/creating-a-new-repository/) on {% data variables.product.product_name %}. -7. 在新仓库顶部 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 的快速设置页面,点击 {% octicon "clippy" aria-label="The copy to clipboard icon" %} 以复制远程仓库 URL。 - - ![创建远程仓库 URL 字段](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) +7. At the top of your new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL. + + ![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) {% tip %} - 提示:有关 HTTPS 和 SSH URL 之间区别的信息,请参阅“[关于远程存储库](/github/getting-started-with-github/about-remote-repositories)”。 + **Tip:** For information on the difference between HTTPS and SSH URLs, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)." {% endtip %} -8. 检查仓库现有的远程名称。 例如,`origin` 或 `upstream` 是两个常见的选项。 +8. Check the existing remote name for your repository. For example, `origin` or `upstream` are two common choices. ```shell $ git remote -v - > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (push) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (push) ``` -9. 使用现有的远程名称和您在步骤 7 中复制的远程仓库 URL 为新仓库设置新的远程 URL。 +9. Set up a new remote URL for your new repository using the existing remote name and the remote repository URL you copied in step 7. ```shell - git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git + git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git ``` -10. 使用新仓库名称验证远程 URL 是否已更改。 +10. Verify that the remote URL has changed with your new repository name. ```shell $ git remote -v # Verify new remote URL - > origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (fetch) - > origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (push) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (fetch) + > origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (push) ``` -11. 将您的更改推送到 {% data variables.product.product_name %} 上的新仓库。 +11. Push your changes to the new repository on {% data variables.product.product_name %}. ```shell - git push -u origin BRANCH-NAME + git push -u origin BRANCH-NAME ``` diff --git a/translations/zh-CN/content/get-started/using-github/github-command-palette.md b/translations/zh-CN/content/get-started/using-github/github-command-palette.md index abc268a19a..d5a12c7c75 100644 --- a/translations/zh-CN/content/get-started/using-github/github-command-palette.md +++ b/translations/zh-CN/content/get-started/using-github/github-command-palette.md @@ -1,234 +1,229 @@ --- -title: GitHub 命令面板 -intro: '使用 {% data variables.product.product_name %} 中的命令面板可以直接从键盘导航、搜索和运行命令。' +title: GitHub Command Palette +intro: 'Use the command palette in {% data variables.product.product_name %} to navigate, search, and run commands directly from your keyboard.' versions: feature: command-palette shortTitle: GitHub Command Palette -ms.openlocfilehash: 1b9b8ecfa5e8824bcf7032c51250238ff5f8e8a7 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147423138' --- + {% data reusables.command-palette.beta-note %} -## 关于 {% data variables.product.prodname_command_palette %} +## About the {% data variables.product.prodname_command_palette %} -您可以使用 {% data variables.product.prodname_command_palette %} 在 {% data variables.product.product_name %} 上导航、搜索和运行命令。 命令面板是一种按需方式,用于根据您最近使用的当前上下文和资源显示建议。 您可以从 {% data variables.product.product_name %} 上的任何位置使用键盘快捷键打开命令面板,这样可以节省您的时间,手也不需要离开键盘。 +You can navigate, search, and run commands on {% data variables.product.product_name %} with the {% data variables.product.prodname_command_palette %}. The command palette is an on-demand way to show suggestions based on your current context and resources you've used recently. You can open the command palette with a keyboard shortcut from anywhere on {% data variables.product.product_name %}, which saves you time and keeps your hands on the keyboard. -### 快速导航 +### Fast navigation -打开命令面板时,建议会进行优化,使你可以从存储库、个人帐户或组织中的任意位置轻松访问顶级页面,如“问题”页面。 如果未列出所需的位置,请开始输入位置的名称或编号以优化建议。 +When you open the command palette, the suggestions are optimized to give you easy access from anywhere in a repository, personal account, or organization to top-level pages like the Issues page. If the location you want isn't listed, start entering the name or number for the location to refine the suggestions. -![命令面板存储库建议](/assets/images/help/command-palette/command-palette-navigation-repo-default.png) +![Command palette repository suggestions](/assets/images/help/command-palette/command-palette-navigation-repo-default.png) -### 轻松访问命令 +### Easy access to commands -直接从键盘运行命令而无需浏览一系列菜单的功能可能会改变您使用 {% data variables.product.prodname_dotcom %} 的方式。 例如,您可以通过几次击键切换主题,从而在需求变化时轻松切换主题。 +The ability to run commands directly from your keyboard, without navigating through a series of menus, may change the way you use {% data variables.product.prodname_dotcom %}. For example, you can switch themes with a few keystrokes, making it easy to toggle between themes as your needs change. -![命令面板更改主题](/assets/images/help/command-palette/command-palette-command-change-theme.png) +![Command palette change theme](/assets/images/help/command-palette/command-palette-command-change-theme.png) -## 打开 {% data variables.product.prodname_command_palette %} +## Opening the {% data variables.product.prodname_command_palette %} -使用以下默认键盘快捷键之一打开命令面板: -- Windows 和 Linux:Ctrl+KCtrl+Alt+K -- Mac:Command+KCommand+Option+K +Open the command palette using one of the following default keyboard shortcuts: +- Windows and Linux: Ctrl+K or Ctrl+Alt+K +- Mac: Command+K or Command+Option+K -你可以在用户设置的[辅助功能部分](https://github.com/settings/accessibility)中自定义用于打开命令面板的键盘快捷方式。 有关详细信息,请参阅“[自定义 {% data variables.product.prodname_command_palette %} 键盘快捷方式](#customizing-your-github-command-palette-keyboard-shortcuts)”。 +You can customize the keyboard shortcuts you use to open the command palette in the [Accessibility section](https://github.com/settings/accessibility) of your user settings. For more information, see "[Customizing your {% data variables.product.prodname_command_palette %} keyboard shortcuts](#customizing-your-github-command-palette-keyboard-shortcuts)." -打开命令面板时,它会在左上角显示你的位置,并将其用作建议的范围(例如 `mashed-avocado` 组织)。 +When you open the command palette, it shows your location at the top left and uses it as the scope for suggestions (for example, the `mashed-avocado` organization). -![命令面板启动](/assets/images/help/command-palette/command-palette-launch.png) +![Command palette launch](/assets/images/help/command-palette/command-palette-launch.png) {% note %} -**注意:** -- 如果正在编辑 Markdown 文本,请使用 Ctrl+Alt+K(Windows 和 Linux)或 Command+Option+K (Mac) 打开命令面板。{% ifversion projects-v2 %} -- 如果正在处理 {% data variables.projects.project_v2 %},会改为显示项目特定的命令面板。 有关详细信息,请参阅“[自定义视图](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)”。{% endif %} +**Notes:** +- If you are editing Markdown text, open the command palette with Ctrl+Alt+K (Windows and Linux) or Command+Option+K (Mac).{% ifversion projects-v2 %} +- If you are working on a {% data variables.projects.project_v2 %}, a project-specific command palette is displayed instead. For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)."{% endif %} {% endnote %} -### 自定义 {% data variables.product.prodname_command_palette %} 键盘快捷键 +### Customizing your {% data variables.product.prodname_command_palette %} keyboard shortcuts -用于打开命令面板的默认键盘快捷键可能与默认操作系统和浏览器键盘快捷键冲突。 你可以在帐户设置的[辅助功能部分](https://github.com/settings/accessibility)中自定义键盘快捷方式。 在命令面板设置中,可以自定义用于在搜索模式和命令模式下打开命令面板的键盘快捷键。 +The default keyboard shortcuts used to open the command palette may conflict with your default OS and browser keyboard shortcuts. You have the option to customize your keyboard shortcuts in the [Accessibility section](https://github.com/settings/accessibility) of your account settings. In the command palette settings, you can customize the keyboard shortcuts for opening the command palette in both search mode and command mode. -![命令面板键盘快捷键设置](/assets/images/help/command-palette/command-palette-keyboard-shortcut-settings.png) -## 使用 {% data variables.product.prodname_command_palette %} 导航 +![Command palette keyboard shortcut settings](/assets/images/help/command-palette/command-palette-keyboard-shortcut-settings.png) +## Navigating with the {% data variables.product.prodname_command_palette %} -可以使用命令面板导航到 {% data variables.product.product_name %} 上您有权访问的任何页面。 +You can use the command palette to navigate to any page that you have access to on {% data variables.product.product_name %}. {% data reusables.command-palette.open-palette %} -2. 开始键入要导航到的路径。 命令面板中的建议将更改以匹配您的文本。 +2. Start typing the path you want to navigate to. The suggestions in the command palette change to match your text. - ![命令面板导航当前范围](/assets/images/help/command-palette/command-palette-navigation-current-scope.png) + ![Command palette navigation current scope](/assets/images/help/command-palette/command-palette-navigation-current-scope.png) {% data reusables.command-palette.change-scope %} - 您还可以使用按键来缩小搜索范围。 有关详细信息,请参阅“[按键功能](#keystroke-functions)”。 + You can also use keystrokes to narrow your search. For more information, see "[Keystroke functions](#keystroke-functions)." -4. 完成输入路径,或使用箭头键从建议列表中突出显示所需的路径。 +4. Finish entering the path, or use the arrow keys to highlight the path you want from the list of suggestions. -5. 使用 Enter 跳转到所选位置。 或者,使用 Ctrl+Enter(Windows 和 Linux)或 Command+Enter (Mac) 在新的浏览器标签页中打开该位置。 +5. Use Enter to jump to your chosen location. Alternatively, use Ctrl+Enter (Windows and Linux) or Command+Enter (Mac) to open the location in a new browser tab. -## 使用 {% data variables.product.prodname_command_palette %} 搜索 +## Searching with the {% data variables.product.prodname_command_palette %} -可以使用命令面板在 {% data variables.product.product_location %} 上搜索任何内容。 +You can use the command palette to search for anything on {% data variables.location.product_location %}. {% data reusables.command-palette.open-palette %} {% data reusables.command-palette.change-scope %} -3. (可选)使用按键查找特定类型的资源: +3. Optionally, use keystrokes to find specific types of resource: - - # 搜索问题、拉取请求、讨论和项目 - - ! 搜索项目 - - @ 搜索用户、组织和存储库 - - / 搜索存储库范围内的文件 + - # Search for issues, pull requests, discussions, and projects + - ! Search for projects + - @ Search for users, organizations, and repositories + - / Search for files within a repository scope - ![命令面板搜索文件](/assets/images/help/command-palette/command-palette-search-files.png) + ![Command palette search files](/assets/images/help/command-palette/command-palette-search-files.png) -4. 开始输入搜索字词。 命令面板将根据您的搜索范围为您提供一系列建议的搜索。 +4. Begin entering your search terms. The command palette will offer you a range of suggested searches based on your search scope. {% tip %} - 你也可以在命令面板中使用 {% data variables.product.prodname_dotcom %} 集成搜索的完整语法。 有关详细信息,请参阅“[搜索有关 {% data variables.product.prodname_dotcom %} 的信息](/search-github)”。 + You can also use the full syntax of {% data variables.product.prodname_dotcom %}'s integrated search within the command palette. For more information, see "[Searching for information on {% data variables.product.prodname_dotcom %}](/search-github)." {% endtip %} -5. 使用箭头键突出显示所需的搜索结果,并使用 Enter 跳转到所选位置。 或者,使用 Ctrl+Enter(Windows 和 Linux)或 Command+Enter (Mac) 在新的浏览器标签页中打开该位置。 +5. Use the arrow keys to highlight the search result you want and use Enter to jump to your chosen location. Alternatively, use Ctrl+Enter (Windows and Linux) or Command+Enter (Mac) to open the location in a new browser tab. -## 从 {% data variables.product.prodname_command_palette %} 运行命令 +## Running commands from the {% data variables.product.prodname_command_palette %} -您可以使用 {% data variables.product.prodname_command_palette %} 来运行命令。 例如,您可以创建新的存储库或议题,或更改主题。 运行命令时,其操作的位置由基础页面或命令面板中显示的范围确定。 +You can use the {% data variables.product.prodname_command_palette %} to run commands. For example, you can create a new repository or issue, or change your theme. When you run a command, the location for its action is determined by either the underlying page or the scope shown in the command palette. -- 拉取请求和议题命令始终在基础页面上运行。 -- 更高级别的命令(例如存储库命令)在命令面板中显示的范围中运行。 +- Pull request and issue commands always run on the underlying page. +- Higher-level commands, for example, repository commands, run in the scope shown in the command palette. -有关受支持命令的完整列表,请参阅“[{% data variables.product.prodname_command_palette %} 参考](#github-command-palette-reference)”。 +For a full list of supported commands, see "[{% data variables.product.prodname_command_palette %} reference](#github-command-palette-reference)." -1. 在命令模式下打开命令面板的默认键盘快捷方式是 Ctrl+Shift+K(Windows 和 Linux)或 Command+Shift+K (Mac)。 如果已打开命令面板,请按 > 切换到命令模式。 {% data variables.product.prodname_dotcom %} 根据您的位置建议命令。 +1. The default keyboard shortcuts to open the command palette in command mode are Ctrl+Shift+K (Windows and Linux) or Command+Shift+K (Mac). If you already have the command palette open, press > to switch to command mode. {% data variables.product.prodname_dotcom %} suggests commands based on your location. - ![命令面板命令模式](/assets/images/help/command-palette/command-palette-command-mode.png) + ![Command palette command mode](/assets/images/help/command-palette/command-palette-command-mode.png) {% data reusables.command-palette.change-scope %} -3. 如果未显示所需的命令,请检查范围,然后开始在文本框中输入命令名称。 +3. If the command you want is not displayed, check your scope then start entering the command name in the text box. -4. 使用箭头键突出显示所需的命令,然后使用 Enter 运行它。 +4. Use the arrow keys to highlight the command you want and use Enter to run it. -## 关闭命令面板 +## Closing the command palette -当命令面板处于活动状态时,可以使用以下键盘快捷键之一关闭命令面板: +When the command palette is active, you can use one of the following keyboard shortcuts to close the command palette: -- 搜索和导航模式:EscCtrl+K(Windows 和 Linux)或 Command+K (Mac) -- 命令模式:EscCtrl+Shift+K(Windows 和 Linux)或 Command+Shift+K (Mac) +- Search and navigation mode: Esc or Ctrl+K (Windows and Linux) Command+K (Mac) +- Command mode: Esc or Ctrl+Shift+K (Windows and Linux) Command+Shift+K (Mac) -如果在辅助功能设置中自定义了命令面板键盘快捷键,则自定义的键盘快捷键将用于打开和关闭命令面板。 +If you have customized the command palette keyboard shortcuts in the Accessibility settings, your customized keyboard shortcuts will be used for both opening and closing the command palette. -## {% data variables.product.prodname_command_palette %} 引用 +## {% data variables.product.prodname_command_palette %} reference -### 按键功能 +### Keystroke functions -当命令面板处于导航和搜索模式时,这些按键可用,也就是说,它们在命令模式下不可用。 +These keystrokes are available when the command palette is in navigation and search modes, that is, they are not available in command mode. -| 击键 | 函数 | +| Keystroke | Function | | :- | :- | -|>| 进入命令模式。 有关详细信息,请参阅“[从 {% data variables.product.prodname_command_palette %} 运行命令](#running-commands-from-the-github-command-palette)”。 | -|#| 搜索议题、拉取请求、讨论和项目。 有关详细信息,请参阅“[使用 {% data variables.product.prodname_command_palette %} 搜索](#searching-with-the-github-command-palette)”。| -|@| 搜索用户、组织和存储库。 有关详细信息,请参阅“[使用 {% data variables.product.prodname_command_palette %} 搜索](#searching-with-the-github-command-palette)”。| -|/| 搜索存储库范围内的文件或组织范围内的存储库。 有关详细信息,请参阅“[使用 {% data variables.product.prodname_command_palette %} 搜索](#searching-with-the-github-command-palette)”。 | -|!| 只搜索项目。 有关详细信息,请参阅“[使用 {% data variables.product.prodname_command_palette %} 搜索](#searching-with-the-github-command-palette)”。| -|Ctrl+CCommand+C| 将突出显示结果的搜索或导航 URL 复制到剪贴板。| -|Enter| 跳转到突出显示的结果或运行突出显示的命令。| -|Ctrl+EnterCommand+Enter| 在新的浏览器选项卡中打开突出显示的搜索或导航结果。| -|?| 在命令面板中显示帮助。| +|>| Enter command mode. For more information, see "[Running commands from the {% data variables.product.prodname_command_palette %}](#running-commands-from-the-github-command-palette)." | +|#| Search for issues, pull requests, discussions, and projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."| +|@| Search for users, organizations, and repositories. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."| +|/| Search for files within a repository scope or repositories within an organization scope. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." | +|!| Search just for projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."| +|Ctrl+C or Command+C| Copy the search or navigation URL for the highlighted result to the clipboard.| +|Enter| Jump to the highlighted result or run the highlighted command.| +|Ctrl+Enter or Command+Enter| Open the highlighted search or navigation result in a new brower tab.| +|?| Display help within the command palette.| -### 全局命令 +### Global commands -以下命令可从所有范围使用。 +These commands are available from all scopes. -| Command | 行为| +| Command | Behavior| | :- | :- | :- | -|`Import repository`|通过从另一个版本控制系统导入项目来创建新存储库。 有关详细信息,请参阅“[使用 GitHub 导入工具导入存储库](/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)”。 | -|`New gist`|打开新 gist。 有关详细信息,请参阅“[创建 Gist](/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)”。 | -|`New organization`|创建新组织。 有关详细信息,请参阅“[从头开始创建新组织](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)”。 | -|`New project`|创建新的项目板。 有关详细信息,请参阅“[创建项目](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project)”。 | -|`New repository`|从头开始创建新的存储库。 有关详细信息,请参阅“[创建新存储库](/repositories/creating-and-managing-repositories/creating-a-new-repository)”。 | -|`Switch theme to `|直接更改为 UI 的其他主题。 有关详细信息,请参阅“[管理主题设置](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings)”。 | +|`Import repository`|Create a new repository by importing a project from another version control system. For more information, see "[Importing a repository with GitHub importer](/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)." | +|`New gist`|Open a new gist. For more information, see "[Creating a gist](/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)." | +|`New organization`|Create a new organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." | +|`New project`|Create a new project board. For more information, see "[Creating a project](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project)." | +|`New repository`|Create a new repository from scratch. For more information, see "[Creating a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository)." | +|`Switch theme to `|Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings)." | -### 组织命令 +### Organization commands -以下命令仅在组织的范围内可用。 +These commands are available only within the scope of an organization. -| Command | 行为| +| Command | Behavior| | :- | :- | -| `New team`| 在当前组织中创建新团队。 有关详细信息,请参阅“[创建团队](/organizations/organizing-members-into-teams/creating-a-team)”。 +| `New team`| Create a new team in the current organization. For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)." -### 存储库命令 +### Repository commands -这些命令中的大多数仅在存储库的主页上可用。 如果某个命令在其他页面上也可用,则会在行为列中注明。 +Most of these commands are available only on the home page of the repository. If a command is also available on other pages, this is noted in the behavior column. -| Command | 行为| +| Command | Behavior| | :- | :- | -|`Clone repository: `|将使用 {% data variables.product.prodname_cli %}、HTTPS 或 SSH 克隆存储库所需的 URL 复制到剪贴板。 有关详细信息,请参阅“[克隆存储库](/repositories/creating-and-managing-repositories/cloning-a-repository)”。| -|`New discussion`|在存储库中创建新讨论。 有关详细信息,请参阅“[创建新讨论](/discussions/quickstart#creating-a-new-discussion)”。| -|`New file`|从存储库中的任何页面创建新文件。 有关详细信息,请参阅“[将文件添加到存储库](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)”。 -|`New issue`|从存储库中的任何页面打开新议题。 有关详细信息,请参阅“[创建问题](/issues/tracking-your-work-with-issues/creating-an-issue)”。| -|`Open in new codespace`|为此存储库创建并打开代码空间。 有关详细信息,请参阅“[创建 codespace](/codespaces/developing-in-codespaces/creating-a-codespace)”。| -|`Open in github.dev editor`|在 github.dev 编辑器中打开当前存储库。 有关详细信息,请参阅“[打开基于 Web 的编辑器](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)”。| +|`Clone repository: `|Copy the URL needed to clone the repository using {% data variables.product.prodname_cli %}, HTTPS, or SSH to the clipboard. For more information, see "[Cloning a repository](/repositories/creating-and-managing-repositories/cloning-a-repository)."| +|`New discussion`|Create a new discussion in the repository. For more information, see "[Creating a new discussion](/discussions/quickstart#creating-a-new-discussion)."| +|`New file`|Create a new file from any page in the repository. For more information, see "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)." +|`New issue`|Open a new issue from any page in the repository. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue)."| +|`Open in new codespace`|Create and open a codespace for this repository. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)."| +|`Open in github.dev editor`|Open the current repository in the github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)."| -### 文件命令 +### File commands -以下命令仅当您从存储库中的文件打开命令面板时才可用。 +These commands are available only when you open the command palette from a file in a repository. -| Command | 行为| +| Command | Behavior| | :- | :- | -|`Copy permalink`|创建指向包含当前提交 SHA 的文件的链接,并将该链接复制到剪贴板。 有关详细信息,请参阅“[获取文件的永久链接](/repositories/working-with-files/using-files/getting-permanent-links-to-files#press-y-to-permalink-to-a-file-in-a-specific-commit)”。 -|`Open in github.dev editor`|在 github.dev 编辑器中打开当前显示的文件。 有关详细信息,请参阅“[打开基于 Web 的编辑器](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)”。| +|`Copy permalink`|Create a link to the file that includes the current commit SHA and copy the link to the clipboard. For more information, see "[Getting permanent links to files](/repositories/working-with-files/using-files/getting-permanent-links-to-files#press-y-to-permalink-to-a-file-in-a-specific-commit)." +|`Open in github.dev editor`|Open the currently displayed file in github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)."| -### 讨论命令 +### Discussion commands -以下命令仅当您从讨论中打开命令面板时才可用。 它们作用于当前页面,不受命令面板中设置的范围的影响。 +These commands are available only when you open the command palette from a discussion. They act on your current page and are not affected by the scope set in the command palette. -| Command | 行为| +| Command | Behavior| | :- | :- | -|`Delete discussion...`|永久删除讨论。 有关详细信息,请参阅“[管理讨论](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion)”。 -|`Edit discussion body`|打开讨论的正文以供编辑。 -|`Subscribe`/`unsubscribe`|选择接收或不接收有关讨论内容增加的通知。 有关详细信息,请参阅“[关于通知](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)”。 -|`Transfer discussion...`|将讨论移动到其他存储库。 有关详细信息,请参阅“[管理讨论](/discussions/managing-discussions-for-your-community/managing-discussions#transferring-a-discussion)”。 +|`Delete discussion...`|Permanently delete the discussion. For more information, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion)." +|`Edit discussion body`|Open the main body of the discussion ready for editing. +|`Subscribe`/`unsubscribe`|Opt in or out of notifications for additions to the discussion. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." +|`Transfer discussion...`|Move the discussion to a different repository. For more information, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions#transferring-a-discussion)." -### 议题命令 +### Issue commands -以下命令仅当您从议题中打开命令面板时才可用。 它们作用于当前页面,不受命令面板中设置的范围的影响。 +These commands are available only when you open the command palette from an issue. They act on your current page and are not affected by the scope set in the command palette. -| Command | 行为| +| Command | Behavior| | :- | :- | -|`Close`/`reopen issue`|关闭或重新打开当前议题。 有关详细信息,请参阅“[关于问题](/issues/tracking-your-work-with-issues/about-issues)”。| -|`Convert issue to discussion...`|将当前议题转换为讨论。 有关详细信息,请参阅“[审查讨论](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)”。 -|`Delete issue...`|删除当前议题。 有关详细信息,请参阅“[删除问题](/issues/tracking-your-work-with-issues/deleting-an-issue)”。| -|`Edit issue body`|打开议题正文以进行编辑。 -|`Edit issue title`|打开议题的标题以进行编辑。 -|`Lock issue`|将新评论限于对存储库具有写入访问权限的用户。 有关详细信息,请参阅“[锁定对话](/communities/moderating-comments-and-conversations/locking-conversations)”。 -|`Pin`/`unpin issue`|更改议题是否显示在存储库的固定议题部分中。 有关详细信息,请参阅“[将问题固定到存储库](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)”。| -|`Subscribe`/`unsubscribe`|选择接收或不接收有关此议题更改的通知。 有关详细信息,请参阅“[关于通知](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)”。 -|`Transfer issue...`|将议题转移到另一个存储库。 有关详细信息,请参阅“[将问题转移到其他存储库](/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)”。| +|`Close`/`reopen issue`|Close or reopen the current issue. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)."| +|`Convert issue to discussion...`|Convert the current issue into a discussion. For more information, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)." +|`Delete issue...`|Delete the current issue. For more information, see "[Deleting an issue](/issues/tracking-your-work-with-issues/deleting-an-issue)."| +|`Edit issue body`|Open the main body of the issue ready for editing. +|`Edit issue title`|Open the title of the issue ready for editing. +|`Lock issue`|Limit new comments to users with write access to the repository. For more information, see "[Locking conversations](/communities/moderating-comments-and-conversations/locking-conversations)." +|`Pin`/`unpin issue`|Change whether or not the issue is shown in the pinned issues section for the repository. For more information, see "[Pinning an issue to your repository](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)."| +|`Subscribe`/`unsubscribe`|Opt in or out of notifications for changes to this issue. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." +|`Transfer issue...`|Transfer the issue to another repository. For more information, see "[Transferring an issue to another repository](/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)."| -### 拉取请求命令 +### Pull request commands -以下命令仅当您从拉取请求打开命令面板时才可用。 它们作用于当前页面,不受命令面板中设置的范围的影响。 +These commands are available only when you open the command palette from a pull request. They act on your current page and are not affected by the scope set in the command palette. -| Command | 行为| +| Command | Behavior| | :- | :- | -|`Close`/`reopen pull request`|关闭或重新打开当前拉取请求。 有关详细信息,请参阅“[关于拉取请求](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)”。| -|`Convert to draft`/`Mark pull request as ready for review`|更改拉取请求的状态,以将其显示为就绪或未准备好以供审阅。 有关详细信息,请参阅“[更改拉取请求的状态](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)”。| -|`Copy current branch name`| 将拉取请求的头部分支的名称添加到剪贴板。 -|`Edit pull request body`|打开拉取请求的正文以进行编辑。 -|`Edit pull request title`|打开拉取请求的标题以进行编辑。 -|`Open in new codespace`|为拉取请求的头部分支创建并打开代码空间。 有关详细信息,请参阅“[创建 codespace](/codespaces/developing-in-codespaces/creating-a-codespace)”。 -|`Subscribe`/`unsubscribe`|选择接收或不接收有关此拉取请求更改的通知。 有关详细信息,请参阅“[关于通知](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)”。 -|`Update current branch`|使用来自基础分支的更改更新拉取请求的头部分支。 这仅适用于以存储库的默认分支为目标的拉取请求。 有关详细信息,请参阅“[关于分支](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)”。| +|`Close`/`reopen pull request`|Close or reopen the current pull request. For more information, see "[About pull requests](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."| +|`Convert to draft`/`Mark pull request as ready for review`|Change the state of the pull request to show it as ready, or not ready, for review. For more information, see "[Changing the state of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)."| +|`Copy current branch name`| Add the name of the head branch for the pull request to the clipboard. +|`Edit pull request body`|Open the main body of the pull request ready for editing. +|`Edit pull request title`|Open the title of the pull request ready for editing. +|`Open in new codespace`|Create and open a codespace for the head branch of the pull request. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)." +|`Subscribe`/`unsubscribe`|Opt in or out of notifications for changes to this pull request. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." +|`Update current branch`|Update the head branch of the pull request with changes from the base branch. This is available only for pull requests that target the default branch of the repository. For more information, see "[About branches](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)."| diff --git a/translations/zh-CN/content/get-started/using-github/github-mobile.md b/translations/zh-CN/content/get-started/using-github/github-mobile.md index b35611d26c..74cd8e8b2a 100644 --- a/translations/zh-CN/content/get-started/using-github/github-mobile.md +++ b/translations/zh-CN/content/get-started/using-github/github-mobile.md @@ -1,6 +1,6 @@ --- title: GitHub Mobile -intro: '从移动设备对 {% data variables.product.product_name %} 上的工作进行分类、协作和管理。' +intro: 'Triage, collaborate, and manage your work on {% data variables.product.product_name %} from your mobile device.' versions: fpt: '*' ghes: '*' @@ -11,87 +11,84 @@ redirect_from: - /get-started/using-github/github-for-mobile - /github/getting-started-with-github/github-for-mobile - /github/getting-started-with-github/using-github/github-for-mobile -ms.openlocfilehash: a9af0848fdc26c5efd3dfb2d00076e3af5fb00bc -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147508446' --- -## 关于 {% data variables.product.prodname_mobile %} + +## About {% data variables.product.prodname_mobile %} {% data reusables.mobile.about-mobile %} -{% data variables.product.prodname_mobile %} 让你可以随时随地快速高效地在 {% data variables.product.product_name %} 上执行重要工作。 {% data variables.product.prodname_mobile %} 通过可信的第一方客户端应用程序可以安全可靠地访问 {% data variables.product.product_name %} 数据。 +{% data variables.product.prodname_mobile %} gives you a way to do high-impact work on {% data variables.product.product_name %} quickly and from anywhere. {% data variables.product.prodname_mobile %} is a safe and secure way to access your {% data variables.product.product_name %} data through a trusted, first-party client application. -通过 {% data variables.product.prodname_mobile %},您可以: +With {% data variables.product.prodname_mobile %} you can: -- 管理、分类和清除通知 -- 阅读、审查及协作处理问题和拉取请求 -- 搜索、浏览用户、仓库和组织以及与之交互 -- 当有人提到用户名时收到推送通知 {% ifversion fpt or ghec %}- 使用双因素身份验证保护 GitHub.com 帐户 -- 在无法识别的设备上验证登录尝试{% endif %} +- Manage, triage, and clear notifications +- Read, review, and collaborate on issues and pull requests +- Edit files in pull requests +- Search for, browse, and interact with users, repositories, and organizations +- Receive a push notification when someone mentions your username +{% ifversion fpt or ghec %}- Secure your GitHub.com account with two-factor authentication +- Verify your sign in attempts on unrecognized devices{% endif %} -有关 {% data variables.product.prodname_mobile %} 的通知的详细信息,请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)”。 +For more information about notifications for {% data variables.product.prodname_mobile %}, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)." -{% ifversion fpt or ghec %}- 有关使用 {% data variables.product.prodname_mobile %} 进行双因素身份验证的详细信息,请参阅“[配置 {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile) 和[使用 {% data variables.product.prodname_mobile %} 进行身份验证](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication##verifying-with-github-mobile)”。 {% endif %} +{% ifversion fpt or ghec %}- For more information on two-factor authentication using {% data variables.product.prodname_mobile %}, see "[Configuring {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile) and [Authenticating using {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication##verifying-with-github-mobile)." {% endif %} -## 安装 {% data variables.product.prodname_mobile %} +## Installing {% data variables.product.prodname_mobile %} -若要为 Android 或 iOS 安装 {% data variables.product.prodname_mobile %},请参阅 [{% data variables.product.prodname_mobile %}](https://github.com/mobile)。 +To install {% data variables.product.prodname_mobile %} for Android or iOS, see [{% data variables.product.prodname_mobile %}](https://github.com/mobile). -## 管理帐户 +## Managing accounts -可以使用 {% data variables.product.prodname_dotcom_the_website %} 上的一个个人帐户和 {% data variables.product.prodname_ghe_server %} 上的一个个人帐户同时登录到移动设备。 有关不同产品的详细信息,请参阅“[{% data variables.product.company_short %} 的产品](/get-started/learning-about-github/githubs-products)”。 +You can be simultaneously signed into mobile with one personal account on {% data variables.product.prodname_dotcom_the_website %} and one personal account on {% data variables.product.prodname_ghe_server %}. For more information about our different products, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)." {% data reusables.mobile.push-notifications-on-ghes %} -如果您需要通过 VPN 访问企业,{% data variables.product.prodname_mobile %} 可能不适用于您的企业。 +{% data variables.product.prodname_mobile %} may not work with your enterprise if you're required to access your enterprise over VPN. -### 先决条件 +### Prerequisites -您必须在设备上安装 {% data variables.product.prodname_mobile %} 1.4 或更高版本,才能使用 {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}。 +You must install {% data variables.product.prodname_mobile %} 1.4 or later on your device to use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}. -要同时使用 {% data variables.product.prodname_mobile %} 与 {% data variables.product.prodname_ghe_server %},{% data variables.product.product_location %} 必须为 3.0 或更高版本,并且企业所有者必须为企业启用移动版支持。 有关详细信息,请参阅 {% data variables.product.prodname_ghe_server %} 文档中的 {% ifversion ghes %}“[发行说明](/enterprise-server/admin/release-notes)”和{% endif %}“[为企业管理 {% data variables.product.prodname_mobile %}]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}”。{% else %}。{% endif %} +To use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, {% data variables.location.product_location %} must be version 3.0 or greater, and your enterprise owner must enable mobile support for your enterprise. For more information, see {% ifversion ghes %}"[Release notes](/enterprise-server/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %} -在具有 {% data variables.product.prodname_ghe_server %} 的 {% data variables.product.prodname_mobile %} beta 版本期间,必须使用 {% data variables.product.prodname_dotcom_the_website %} 上的个人帐户登录。 +During the beta for {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, you must be signed in with a personal account on {% data variables.product.prodname_dotcom_the_website %}. -### 添加、切换或登出账户 +### Adding, switching, or signing out of accounts -可以使用 {% data variables.product.prodname_ghe_server %} 上的个人帐户登录到移动设备。 在应用的底部,长按 {% octicon "person" aria-label="The person icon" %}“个人资料”,然后点击 {% octicon "plus" aria-label="The plus icon" %}“添加企业帐户” 。 按提示登录。 +You can sign into mobile with a personal account on {% data variables.product.prodname_ghe_server %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account**. Follow the prompts to sign in. -在 {% data variables.product.prodname_ghe_server %} 上使用个人帐户登录移动设备后,就可以在帐户和 {% data variables.product.prodname_dotcom_the_website %} 上的帐户之间进行切换。 在应用的底部,长按 {% octicon "person" aria-label="The person icon" %}“个人资料”,然后点击要切换到的帐户。 +After you sign into mobile with a personal account on {% data variables.product.prodname_ghe_server %}, you can switch between the account and your account on {% data variables.product.prodname_dotcom_the_website %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap the account you want to switch to. -如果不再需要从 {% data variables.product.prodname_mobile %} 访问 {% data variables.product.prodname_ghe_server %} 上的个人帐户数据,则可以退出登录该帐户。 在应用底部,长按 {% octicon "person" aria-label="The person icon" %}“个人资料”,向左滑动要退出的帐户,然后点击“退出” 。 +If you no longer need to access data for your personal account on {% data variables.product.prodname_ghe_server %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**. -## {% data variables.product.prodname_mobile %} 支持的语言 +## Supported languages for {% data variables.product.prodname_mobile %} -{% data variables.product.prodname_mobile %} 支持以下语言。 +{% data variables.product.prodname_mobile %} is available in the following languages. -- 英语 -- 日语 -- 巴西葡萄牙语 -- 简体中文 -- 西班牙语 +- English +- Japanese +- Brazilian Portuguese +- Simplified Chinese +- Spanish -如果将设备上的语言配置为受支持的语言,则 {% data variables.product.prodname_mobile %} 默认为该语言。 你可以在 {% data variables.product.prodname_mobile %} 的“设置”菜单中更改 {% data variables.product.prodname_mobile %} 的语言。 +If you configure the language on your device to a supported language, {% data variables.product.prodname_mobile %} will default to the language. You can change the language for {% data variables.product.prodname_mobile %} in {% data variables.product.prodname_mobile %}'s **Settings** menu. -## 管理 iOS 上 {% data variables.product.prodname_mobile %} 的通用链接 +## Managing Universal Links for {% data variables.product.prodname_mobile %} on iOS -{% data variables.product.prodname_mobile %} 自动启用 iOS 的通用链接。 当您点击任何 {% data variables.product.product_name %} 链接时,目标 URL 都会在 {% data variables.product.prodname_mobile %} 中打开,而不是在 Safari 中打开。 有关详细信息,请参阅 Apple 开发人员网站上的[通用链接](https://developer.apple.com/ios/universal-links/)。 +{% data variables.product.prodname_mobile %} automatically enables Universal Links for iOS. When you tap any {% data variables.product.product_name %} link, the destination URL will open in {% data variables.product.prodname_mobile %} instead of Safari. For more information, see [Universal Links](https://developer.apple.com/ios/universal-links/) on the Apple Developer site. -若要禁用通用链接,请长按任何 {% data variables.product.product_name %} 链接,然后点击“打开”。 以后每次点击 {% data variables.product.product_name %} 链接时,目标 URL 将在 Safari 中打开,而不是在 {% data variables.product.prodname_mobile %} 中打开。 +To disable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open**. Every time you tap a {% data variables.product.product_name %} link in the future, the destination URL will open in Safari instead of {% data variables.product.prodname_mobile %}. -若要重新启用通用链接,请长按任意 {% data variables.product.product_name %} 链接,然后点击“在 {% data variables.product.prodname_dotcom %} 中打开”。 +To re-enable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open in {% data variables.product.prodname_dotcom %}**. -## 分享反馈 +## Sharing feedback -可以在 [{% data variables.product.prodname_github_community %}](https://github.com/orgs/community/discussions/categories/mobile) 上为 {% data variables.product.prodname_mobile %} 提交功能请求或其他反馈。 +You can submit feature requests or other feedback for {% data variables.product.prodname_mobile %} on [{% data variables.product.prodname_github_community %}](https://github.com/orgs/community/discussions/categories/mobile). -## 选择退出 iOS 的测试版 +## Opting out of beta releases for iOS -如果您正在使用 TestFlight 参加 iOS 版 {% data variables.product.prodname_mobile %} 的测试,可以随时退出。 +If you're testing a beta release of {% data variables.product.prodname_mobile %} for iOS using TestFlight, you can leave the beta at any time. -1. 在 iOS 设备上,打开 TestFlight app。 -2. 在“应用”下,点击 {% data variables.product.prodname_dotcom %}。 -3. 在页面底部,点击“停止测试”。 +1. On your iOS device, open the TestFlight app. +2. Under "Apps", tap **{% data variables.product.prodname_dotcom %}**. +3. At the bottom of the page, tap **Stop Testing**. diff --git a/translations/zh-CN/content/github-cli/github-cli/quickstart.md b/translations/zh-CN/content/github-cli/github-cli/quickstart.md index 254819be91..4b77a522cb 100644 --- a/translations/zh-CN/content/github-cli/github-cli/quickstart.md +++ b/translations/zh-CN/content/github-cli/github-cli/quickstart.md @@ -1,6 +1,6 @@ --- -title: GitHub CLI 快速入门 -intro: '开始使用 {% data variables.product.prodname_cli %} 在命令行中使用 {% data variables.product.company_short %}。' +title: GitHub CLI quickstart +intro: 'Start using {% data variables.product.prodname_cli %} to work with {% data variables.product.company_short %} in the command line.' versions: fpt: '*' ghes: '*' @@ -11,41 +11,37 @@ topics: type: overview allowTitleToDifferFromFilename: true shortTitle: Quickstart -ms.openlocfilehash: 004f848e973aa66d19b9de6b922d65dba76f1aea -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145066714' --- -## 关于 {% data variables.product.prodname_cli %} + +## About {% data variables.product.prodname_cli %} {% data reusables.cli.about-cli %} -## 入门 +## Getting started -1. 在 macOS、Windows 或 Linux 上[安装](https://github.com/cli/cli#installation) {% data variables.product.prodname_cli %}。 -1. 在命令行中,向 {% data variables.product.company_short %} 进行身份验证。 +1. [Install](https://github.com/cli/cli#installation) {% data variables.product.prodname_cli %} on macOS, Windows, or Linux. +1. In the command line, authenticate to {% data variables.product.company_short %}. ```shell gh auth login ``` - {% ifversion not fpt or ghec %} 若要向 {% data variables.product.product_location %} 进行身份验证,请使用 `--hostname` 标志。 + {% ifversion not fpt or ghec %} + To authenticate to {% data variables.location.product_location %}, use the `--hostname` flag. ```shell - gh auth login --hostname hostname + gh auth login --hostname HOSTNAME ``` {% endif %} -1. 开始在命令行中使用 {% data variables.product.company_short %}。 例如,使用 `gh issue status` 或 `gh issue list --assignee @me` 查找要处理的问题。 使用 `gh pr create` 创建拉取请求。 使用 `gh pr checkout`、`gh pr diff` 和 `gh pr review` 查看拉取请求。 +1. Start working with {% data variables.product.company_short %} in the command line. For example, find an issue to work on with `gh issue status` or `gh issue list --assignee @me`. Create a pull request with `gh pr create`. Review a pull request with `gh pr checkout`, `gh pr diff` and `gh pr review`. -## 后续步骤 +## Next steps -- 告诉 {% data variables.product.prodname_cli %} 哪个文本编辑器用于打开文本编辑器的命令。 例如,输入 `gh config set editor "code -w"` 将首选文本编辑器设置为 {% data variables.product.prodname_vscode %}。 有关详细信息,请参阅 [`gh config set`](https://cli.github.com/manual/gh_config_set)。 +- Tell {% data variables.product.prodname_cli %} which text editor to use for commands that open a text editor. For example, enter `gh config set editor "code -w"` to set your preferred text editor to {% data variables.product.prodname_vscode %}. For more information, see [`gh config set`](https://cli.github.com/manual/gh_config_set). -- 为通常运行的命令定义别名。 例如,如果运行 `gh alias set prd "pr create --draft"`,则你可以运行 `gh prd` 以快速打开草稿拉取请求。 有关详细信息,请参阅 [`gh alias`](https://cli.github.com/manual/gh_alias)。 +- Define aliases for commands that you commonly run. For example, if you run `gh alias set prd "pr create --draft"`, you will then be able to run `gh prd` to quickly open a draft pull request. For more information, see [`gh alias`](https://cli.github.com/manual/gh_alias). -- 使用 {% data variables.product.prodname_cli %} 扩展创建或添加自定义命令。 有关详细信息,请参阅“[使用 {% data variables.product.prodname_cli %} 扩展](/github-cli/github-cli/using-github-cli-extensions)”和“[创建 {% data variables.product.prodname_cli %} 扩展](/github-cli/github-cli/creating-github-cli-extensions)”。 +- Create or add custom commands with {% data variables.product.prodname_cli %} extensions. For more information, see "[Using {% data variables.product.prodname_cli %} extensions](/github-cli/github-cli/using-github-cli-extensions)" and "[Creating {% data variables.product.prodname_cli %} extensions](/github-cli/github-cli/creating-github-cli-extensions)." -- 有关可以使用 {% data variables.product.prodname_cli %} 运行的所有命令的详细信息,请参阅“[{% data variables.product.prodname_cli %} 参考](/github-cli/github-cli/github-cli-reference)”。 +- For more information about all of the commands that you can run with {% data variables.product.prodname_cli %}, see "[{% data variables.product.prodname_cli %} reference](/github-cli/github-cli/github-cli-reference)." diff --git a/translations/zh-CN/content/graphql/guides/forming-calls-with-graphql.md b/translations/zh-CN/content/graphql/guides/forming-calls-with-graphql.md index 18aeeeb68a..51259302ab 100644 --- a/translations/zh-CN/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/zh-CN/content/graphql/guides/forming-calls-with-graphql.md @@ -1,6 +1,6 @@ --- -title: 使用 GraphQL 建立调用 -intro: 了解如何向 GraphQL API 验证身份,以及如何创建并运行查询和突变。 +title: Forming calls with GraphQL +intro: 'Learn how to authenticate to the GraphQL API, then learn how to create and run queries and mutations.' redirect_from: - /v4/guides/forming-calls - /graphql/guides/forming-calls @@ -12,26 +12,23 @@ versions: topics: - API shortTitle: Form calls with GraphQL -ms.openlocfilehash: b3778872cad120f64f2fdbc238f2319bdd758513 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147527892' --- -## 使用 GraphQL 进行身份验证 -要与 GraphQL 服务器通信,需要具有正确作用域的 OAuth 令牌。 +## Authenticating with GraphQL -按照“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”中的步骤创建令牌。 您需要的作用域取决于您尝试请求的数据类型。 例如,选择“用户”范围以请求用户数据。 如果需要访问存储库信息,请选择相应的“存储库”范围。 +{% data reusables.user-settings.graphql-classic-pat-only %} + +To communicate with the GraphQL server, you'll need a {% data variables.product.pat_generic %} with the right scopes. + +Follow the steps in "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)" to create a token. The scopes you require depends on the type of data you're trying to request. For example, select the **User** scopes to request user data. If you need access to repository information, select the appropriate **Repository** scopes. {% ifversion fpt or ghec %} -要匹配 [GraphQL 浏览器](/graphql/guides/using-the-explorer)的行为,可请求以下范围: +To match the behavior of the [GraphQL Explorer](/graphql/guides/using-the-explorer), request the following scopes: {% else %} -建议使用以下作用域: +The following scopes are recommended: {% endif %} @@ -48,26 +45,26 @@ read:enterprise read:gpg_key ``` -如果资源需要特定作用域,API 会通知您。 +The API notifies you if a resource requires a specific scope. -## GraphQL 端点 +## The GraphQL endpoint -REST API 有多个端点;GraphQL API 只有一个端点: +The REST API has numerous endpoints; the GraphQL API has a single endpoint:
{% data variables.product.graphql_url_pre %}
-无论执行什么操作,端点都保持不变。 +The endpoint remains constant no matter what operation you perform. -## 与 GraphQL 通信 +## Communicating with GraphQL -由于 GraphQL 操作由多行 JSON 组成,因此 GitHub 建议使用[浏览器](/graphql/guides/using-the-explorer)进行 GraphQL 调用。 也可以使用 cURL 或任何其他采用 HTTP 的库。 +Because GraphQL operations consist of multiline JSON, GitHub recommends using the [Explorer](/graphql/guides/using-the-explorer) to make GraphQL calls. You can also use cURL or any other HTTP-speaking library. -在 REST 中,[HTTP 谓词](/rest#http-verbs)确定执行的操作。 在 GraphQL 中,无论是执行查询还是突变,都要提供 JSON 编码的正文,因此 HTTP 谓词为 `POST`。 唯一的例外是[内省查询](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api),它是一种简单的 `GET` 到终结点查询。 有关 GraphQL 与 REST 的更多信息,请参阅“[从 REST 迁移到 GraphQL](/graphql/guides/migrating-from-rest-to-graphql)”。 +In REST, [HTTP verbs](/rest#http-verbs) determine the operation performed. In GraphQL, you'll provide a JSON-encoded body whether you're performing a query or a mutation, so the HTTP verb is `POST`. The exception is an [introspection query](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api), which is a simple `GET` to the endpoint. For more information on GraphQL versus REST, see "[Migrating from REST to GraphQL](/graphql/guides/migrating-from-rest-to-graphql)." -要使用 cURL 查询 GraphQL,请利用 JSON 有效负载发出 `POST` 请求。 有效负载必须包含一个名为 `query` 的字符串: +To query GraphQL using cURL, make a `POST` request with a JSON payload. The payload must contain a string called `query`: ```shell -curl -H "Authorization: bearer token" -X POST -d " \ +curl -H "Authorization: bearer TOKEN" -X POST -d " \ { \ \"query\": \"query { viewer { login }}\" \ } \ @@ -76,63 +73,63 @@ curl -H "Authorization: bearer token" -X POST -d " \ {% tip %} -注意:`"query"` 的字符串值必须进行换行符转义,否则架构将无法正确解析它。 对于 `POST` 正文,请使用外双引号和转义的内双引号。 +**Note**: The string value of `"query"` must escape newline characters or the schema will not parse it correctly. For the `POST` body, use outer double quotes and escaped inner double quotes. {% endtip %} -### 关于查询和突变操作 +### About query and mutation operations -GitHub 的 GraphQL API 中允许的两种操作类型为查询和突变 。 比较 GraphQL 与 REST,查询操作就像 `GET` 请求,而突变操作则像 `POST`/`PATCH`/`DELETE`。 [突变名称](/graphql/reference/mutations)确定执行的修改内容。 +The two types of allowed operations in GitHub's GraphQL API are _queries_ and _mutations_. Comparing GraphQL to REST, queries operate like `GET` requests, while mutations operate like `POST`/`PATCH`/`DELETE`. The [mutation name](/graphql/reference/mutations) determines which modification is executed. -有关速率限制的信息,请参阅“[GraphQL 资源限制](/graphql/overview/resource-limitations)”。 +For information about rate limiting, see "[GraphQL resource limitations](/graphql/overview/resource-limitations)." -查询和突变形式相似,但有一些重要差异。 +Queries and mutations share similar forms, with some important differences. -### 关于查询 +### About queries -GraphQL 查询仅返回你指定的数据。 要建立查询,必须指定[字段内的字段](/graphql/guides/introduction-to-graphql#field)(也称为嵌套的子字段),直到仅返回[标量](/graphql/reference/scalars)。 +GraphQL queries return only the data you specify. To form a query, you must specify [fields within fields](/graphql/guides/introduction-to-graphql#field) (also known as _nested subfields_) until you return only [scalars](/graphql/reference/scalars). -查询的结构如下: +Queries are structured like this:
query {
-  JSON objects to return
+  JSON-OBJECT-TO-RETURN
 }
-有关实际示例,请参阅“[示例查询](#example-query)”。 +For a real-world example, see "[Example query](#example-query)." -### 关于突变 +### About mutations -要建立突变,必须指定三个参数: +To form a mutation, you must specify three things: -1. 突变名称。 您要执行的修改类型。 -2. 输入对象。 要发送到服务器的数据,由输入字段组成。 将其作为参数传递至突变名称。 -3. 有效负载对象。 要从服务器返回的数据,由返回字段组成。 将其作为突变名称的正文传递。 +1. _Mutation name_. The type of modification you want to perform. +2. _Input object_. The data you want to send to the server, composed of _input fields_. Pass it as an argument to the mutation name. +3. _Payload object_. The data you want to return from the server, composed of _return fields_. Pass it as the body of the mutation name. -突变的结构如下: +Mutations are structured like this:
mutation {
-  mutationName(input: {MutationNameInput!}) {
-    MutationNamePayload
+  MUTATION-NAME(input: {MUTATION-NAME-INPUT!}) {
+    MUTATION-NAME-PAYLOAD
   }
 }
-此示例中的输入对象为 `MutationNameInput`,有效负载对象为 `MutationNamePayload`。 +The input object in this example is `MutationNameInput`, and the payload object is `MutationNamePayload`. -在[突变](/graphql/reference/mutations)引用中,列出的输入字段是作为输入对象传递的内容。 列出的返回字段是作为有效负载对象传递的内容。 +In the [mutations](/graphql/reference/mutations) reference, the listed _input fields_ are what you pass as the input object. The listed _return fields_ are what you pass as the payload object. -有关实际示例,请参阅“[示例突变](#example-mutation)”。 +For a real-world example, see "[Example mutation](#example-mutation)." -## 使用变量 +## Working with variables -[变量](https://graphql.github.io/learn/queries/#variables)可使查询更具动态和更加强大,并且可以在传递突变输入对象时降低复杂性。 +[Variables](https://graphql.github.io/learn/queries/#variables) can make queries more dynamic and powerful, and they can reduce complexity when passing mutation input objects. {% note %} -注意:如果使用的是此浏览器,请确保在单独的[“查询变量”窗格](/graphql/guides/using-the-explorer#using-the-variable-pane)中输入变量,且 JSON 对象之前不含 `variables` 一词。 +**Note**: If you're using the Explorer, make sure to enter variables in the separate [Query Variables pane](/graphql/guides/using-the-explorer#using-the-variable-pane), and do not include the word `variables` before the JSON object. {% endnote %} -下面是一个单变量查询示例: +Here's an example query with a single variable: ```graphql query($number_of_repos:Int!) { @@ -150,9 +147,9 @@ variables { } ``` -使用变量包含三个步骤: +There are three steps to using variables: -1. 在 `variables` 对象中定义操作以外的变量: +1. Define the variable outside the operation in a `variables` object: ```graphql variables { @@ -160,33 +157,33 @@ variables { } ``` - 此对象必须是有效的 JSON。 本示例显示了一个简单的 `Int` 变量类型,但可以定义更复杂的变量类型,如输入对象。 也可以在此定义多个变量。 + The object must be valid JSON. This example shows a simple `Int` variable type, but it's possible to define more complex variable types, such as input objects. You can also define multiple variables here. -2. 将变量作为参数传递至操作: +2. Pass the variable to the operation as an argument: ```graphql query($number_of_repos:Int!){ ``` - 此参数是一个键值对,其中键为以 `$` 开头的名称(例如 `$number_of_repos`),值为类型(例如 `Int`) 。 添加 `!` 以指出是否需要此类型。 如果您已经定义了多个变量,请将它们作为多个参数加入此处。 + The argument is a key-value pair, where the key is the _name_ starting with `$` (e.g., `$number_of_repos`), and the value is the _type_ (e.g., `Int`). Add a `!` to indicate whether the type is required. If you've defined multiple variables, include them here as multiple arguments. -3. 在操作中使用变量: +3. Use the variable within the operation: ```graphql repositories(last: $number_of_repos) { ``` - 在本示例中,我们用变量替换要检索的仓库编号。 在步骤 2 中指定类型,因为 GraphQL 会强制执行强类型化。 + In this example, we substitute the variable for the number of repositories to retrieve. We specify a type in step 2 because GraphQL enforces strong typing. -此流程会使查询参数具有动态性。 现在,只需更改 `variables` 对象中的值,查询的其余部分则保持不变。 +This process makes the query argument dynamic. We can now simply change the value in the `variables` object and keep the rest of the query the same. -将变量用作参数可支持动态更新 `variables` 对象中的值,而无需更改查询。 +Using variables as arguments lets you dynamically update values in the `variables` object without changing the query. -## 示例查询 +## Example query -我们来演练一个较为复杂的查询,并将此信息放在上下文中。 +Let's walk through a more complex query and put this information in context. -下面的查询用于查找 `octocat/Hello-World` 存储库,查找 20 个最近关闭的问题,并返回每个问题的标题、URL 和前 5 个标签: +The following query looks up the `octocat/Hello-World` repository, finds the 20 most recent closed issues, and returns each issue's title, URL, and first 5 labels: ```graphql query { @@ -210,35 +207,35 @@ query { } ``` -逐行查看此查询的组成元素: +Looking at the composition line by line: * `query {` - 由于我们想从服务器读取数据,而不是修改数据,因此 `query` 是根操作。 (如果未指定操作,则 `query` 也是默认操作。) + Because we want to read data from the server, not modify it, `query` is the root operation. (If you don't specify an operation, `query` is also the default.) * `repository(owner:"octocat", name:"Hello-World") {` - 要开始查询,需找到 [`repository`](/graphql/reference/objects#repository) 对象。 架构验证表明此对象需要 `owner` 和 `name` 参数。 + To begin the query, we want to find a [`repository`](/graphql/reference/objects#repository) object. The schema validation indicates this object requires an `owner` and a `name` argument. * `issues(last:20, states:CLOSED) {` - 为考虑到存储库中的所有问题,我们调用 `issues` 对象。 (可查询 `repository` 中的单个 `issue`,但这需要了解我们想返回的问题编号,并将其作为参数。) + To account for all issues in the repository, we call the `issues` object. (We _could_ query a single `issue` on a `repository`, but that would require us to know the number of the issue we want to return and provide it as an argument.) - 有关 `issues` 对象的一些详细信息: + Some details about the `issues` object: - - [文档](/graphql/reference/objects#repository)中指出,此对象的类型为 `IssueConnection`。 - - 架构验证表明此对象需要将 `last` 或 `first` 个结果作为参数,因此我们提供了 `20`。 - - [文档](/graphql/reference/objects#repository)也指出,此对象接受 `states` 参数,即一种 [`IssueState`](/graphql/reference/enums#issuestate) 枚举类型,可接受的值为 `OPEN` 或 `CLOSED`。 要仅查找已关闭的问题,可对 `states` 键赋值 `CLOSED`。 + - The [docs](/graphql/reference/objects#repository) tell us this object has the type `IssueConnection`. + - Schema validation indicates this object requires a `last` or `first` number of results as an argument, so we provide `20`. + - The [docs](/graphql/reference/objects#repository) also tell us this object accepts a `states` argument, which is an [`IssueState`](/graphql/reference/enums#issuestate) enum that accepts `OPEN` or `CLOSED` values. To find only closed issues, we give the `states` key a value of `CLOSED`. * `edges {` - 我们知道 `issues` 是一种连接,因为它的类型为 `IssueConnection`。 要检索关于各个问题的数据,必须通过 `edges` 访问节点。 + We know `issues` is a connection because it has the `IssueConnection` type. To retrieve data about individual issues, we have to access the node via `edges`. * `node {` - 在本示例中,我们将检索边缘末尾的节点。 [`IssueConnection` 文档指示 `IssueConnection` 类型末尾的节点为 `Issue` 对象](/graphql/reference/objects#issueconnection)。 + Here we retrieve the node at the end of the edge. The [`IssueConnection` docs](/graphql/reference/objects#issueconnection) indicate the node at the end of the `IssueConnection` type is an `Issue` object. -* 了解了要检索 `Issue` 对象后,现在可以查看[文档](/graphql/reference/objects#issue)并指定要返回的字段: +* Now that we know we're retrieving an `Issue` object, we can look at the [docs](/graphql/reference/objects#issue) and specify the fields we want to return: ```graphql title @@ -252,18 +249,18 @@ query { } ``` - 在此指定 `Issue` 对象的 `title`、`url` 和 `labels` 字段。 + Here we specify the `title`, `url`, and `labels` fields of the `Issue` object. - `labels` 字段的类型为 [`LabelConnection`](/graphql/reference/objects#labelconnection)。 与 `issues` 对象一样,`labels` 也是一种连接,因此必须将其边缘传送到连接的节点:`label` 对象。 在此节点上,可指定要返回的 `label` 对象字段,在本例中为 `name`。 + The `labels` field has the type [`LabelConnection`](/graphql/reference/objects#labelconnection). As with the `issues` object, because `labels` is a connection, we must travel its edges to a connected node: the `label` object. At the node, we can specify the `label` object fields we want to return, in this case, `name`. -你可能会注意到,在 Octocat 的{% ifversion not ghae %}公共{% endif %} `Hello-World` 存储库中运行此查询不会返回很多标签。 尝试在您自己的其中一个使用标签的仓库中运行,很可能会看到不同的结果。 +You may notice that running this query on the Octocat's {% ifversion not ghae %}public{% endif %} `Hello-World` repository won't return many labels. Try running it on one of your own repositories that does use labels, and you'll likely see a difference. -## 突变示例 +## Example mutation -突变通常需要只有先执行查询才能找到的信息。 本示例显示两个操作: +Mutations often require information that you can only find out by performing a query first. This example shows two operations: -1. 用于获取议题 ID 的查询。 -2. 用于向议题添加表情符号反应的突变。 +1. A query to get an issue ID. +2. A mutation to add an emoji reaction to the issue. ```graphql query FindIssueID { @@ -288,81 +285,81 @@ mutation AddReactionToIssue { {% tip %} -如果为查询和突变命名(在本示例中为 `FindIssueID` 和 `AddReactionToIssue`),则可以将二者放入此浏览器的同一个窗口,但操作将作为对 GraphQL 终结点的单独调用执行。 不能同时执行查询和突变,反之亦然。 +Although you can include a query and a mutation in the same Explorer window if you give them names (`FindIssueID` and `AddReactionToIssue` in this example), the operations will be executed as separate calls to the GraphQL endpoint. It's not possible to perform a query at the same time as a mutation, or vice versa. {% endtip %} -我们演练一遍这个示例。 任务听起来简单:向议题添加表情符号反应即可。 +Let's walk through the example. The task sounds simple: add an emoji reaction to an issue. -那么,我们怎么知道从查询开始呢? 还不知道。 +So how do we know to begin with a query? We don't, yet. -因为我们想修改服务器上的数据(向议题添加表情符号),所以先搜索架构,查找有用的突变。 参考文档所示为 [`addReaction`](/graphql/reference/mutations#addreaction) 突变,其描述为:`Adds a reaction to a subject.` Perfect! +Because we want to modify data on the server (attach an emoji to an issue), we begin by searching the schema for a helpful mutation. The reference docs show the [`addReaction`](/graphql/reference/mutations#addreaction) mutation, with this description: `Adds a reaction to a subject.` Perfect! -突变文档列出了三个输入字段: +The docs for the mutation list three input fields: * `clientMutationId` (`String`) * `subjectId` (`ID!`) * `content` (`ReactionContent!`) -`!` 指示 `subjectId` 和 `content` 是必填字段。 必填字段 `content` 是有道理的:我们想添加反应,因此需要指定要使用哪个表情符号。 +The `!`s indicate that `subjectId` and `content` are required fields. A required `content` makes sense: we want to add a reaction, so we'll need to specify which emoji to use. -但 `subjectId` 为什么是必填字段呢? 这是因为,`subjectId` 是确定要对哪个存储库中的哪个问题做出反应的唯一方式 。 +But why is `subjectId` required? It's because the `subjectId` is the only way to identify _which_ issue in _which_ repository to react to. -因此,本示例要从查询开始:获取 `ID`。 +This is why we start this example with a query: to get the `ID`. -让我们逐行检查查询: +Let's examine the query line by line: * `query FindIssueID {` - 我们将执行查询,并将其命名为 `FindIssueID`。 请注意,为查询命名是可选操作;我们在此为它命名,然后即可将它与突变放在同一个 Explorer 窗口中。 + Here we're performing a query, and we name it `FindIssueID`. Note that naming a query is optional; we give it a name here so that we can include it in same Explorer window as the mutation. * `repository(owner:"octocat", name:"Hello-World") {` - 通过查询 `repository` 对象并传递 `owner` 和 `name` 参数来指定存储库。 + We specify the repository by querying the `repository` object and passing `owner` and `name` arguments. * `issue(number:349) {` - 通过查询 `issue` 对象和传递 `number` 参数来指定要做出反应的问题。 + We specify the issue to react to by querying the `issue` object and passing a `number` argument. * `id` - 我们将检索 `https://github.com/octocat/Hello-World/issues/349` 的 `id`,并作为 `subjectId` 传递。 + This is where we retrieve the `id` of `https://github.com/octocat/Hello-World/issues/349` to pass as the `subjectId`. -运行查询时,将获取 `id`:`MDU6SXNzdWUyMzEzOTE1NTE=` +When we run the query, we get the `id`: `MDU6SXNzdWUyMzEzOTE1NTE=` {% tip %} -注意:查询中返回的 `id` 是将在突变中作为 `subjectID` 传递的值。 文档和架构内省都不会显示这种关系;您需要理解这些名称背后的概念才能找出答案。 +**Note**: The `id` returned in the query is the value we'll pass as the `subjectID` in the mutation. Neither the docs nor schema introspection will indicate this relationship; you'll need to understand the concepts behind the names to figure this out. {% endtip %} -在 ID 已知的情况下,可以继续进行突变操作: +With the ID known, we can proceed with the mutation: * `mutation AddReactionToIssue {` - 我们将执行突变,并将其命名为 `AddReactionToIssue`。 与查询一样,为突变命名是可选操作;我们在此为它命名,然后即可将它与查询放在同一个 Explorer 窗口中。 + Here we're performing a mutation, and we name it `AddReactionToIssue`. As with queries, naming a mutation is optional; we give it a name here so we can include it in the same Explorer window as the query. * `addReaction(input:{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}) {` - 让我们来检查这一行: + Let's examine this line: - - `addReaction` 是突变的名称。 - - `input` 是必需的参数键。 突变的参数键始终是 `input`。 - - `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}` 是必需的参数值。 突变的参数值始终是由输入字段(在本例中为 `subjectId` 和 `content`)组成的[输入对象](/graphql/reference/input-objects)(因此带有大括号)。 + - `addReaction` is the name of the mutation. + - `input` is the required argument key. This will always be `input` for a mutation. + - `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}` is the required argument value. This will always be an [input object](/graphql/reference/input-objects) (hence the curly braces) composed of input fields (`subjectId` and `content` in this case) for a mutation. - 我们怎么知道内容使用哪个值呢? [`addReaction` 文档](/graphql/reference/mutations#addreaction)指出,`content` 字段的类型为 [`ReactionContent`](/graphql/reference/enums#reactioncontent),即一种[枚举类型](/graphql/reference/enums),因为 GitHub 只支持使用某些表情符号进行反应。 这些是允许的反应值 (注意,某些值与其相应的表情符号名称不同): + How do we know which value to use for the content? The [`addReaction` docs](/graphql/reference/mutations#addreaction) tell us the `content` field has the type [`ReactionContent`](/graphql/reference/enums#reactioncontent), which is an [enum](/graphql/reference/enums) because only certain emoji reactions are supported on GitHub issues. These are the allowed values for reactions (note some values differ from their corresponding emoji names): {% data reusables.repositories.reaction_list %} -* 调用的其余部分由有效负载对象组成。 我们将在此指定执行突变后由服务器返回的数据。 这几行来自 [`addReaction` 文档](/graphql/reference/mutations#addreaction),其中包含三个可能返回的字段: +* The rest of the call is composed of the payload object. This is where we specify the data we want the server to return after we've performed the mutation. These lines come from the [`addReaction` docs](/graphql/reference/mutations#addreaction), which three possible return fields: - `clientMutationId` (`String`) - `reaction` (`Reaction!`) - `subject` (`Reactable!`) - 在本示例中,返回两个必填字段(`reaction` 和 `subject`),二者均包含必填子字段(分别为 `content` 和 `id`)。 + In this example, we return the two required fields (`reaction` and `subject`), both of which have required subfields (respectively, `content` and `id`). -我们运行突变时,响应如下: +When we run the mutation, this is the response: ```json { @@ -379,9 +376,9 @@ mutation AddReactionToIssue { } ``` -就这么简单! 将鼠标悬停在 :tada: 上找到你的用户名,查看[问题的反应](https://github.com/octocat/Hello-World/issues/349)。 +That's it! Check out your [reaction to the issue](https://github.com/octocat/Hello-World/issues/349) by hovering over the :tada: to find your username. -最后注意:当您在输入对象中传递多个字段时,语法可能会变笨拙。 将字段移入[变量](#working-with-variables)可避免这种情况。 下面是您利用变量重写原始突变的方式: +One final note: when you pass multiple fields in an input object, the syntax can get unwieldy. Moving the fields into a [variable](#working-with-variables) can help. Here's how you could rewrite the original mutation using a variable: ```graphql mutation($myVar:AddReactionInput!) { @@ -404,19 +401,19 @@ variables { {% note %} -你可能会注意到,前文示例中的 `content` 字段值(直接用于突变)在 `HOORAY` 两侧没有引号,但在变量中使用时有引号。 原因是: -* 直接在突变中使用 `content` 时,架构预计此值的类型为 [`ReactionContent`](/graphql/reference/enums#reactioncontent),即一种枚举类型,而非字符串。 如果您在枚举值两侧添加引号,架构验证将出现错误,因为引号是为字符串保留的。 -* 在变量中使用 `content` 时,变量部分必须为有效的 JSON,因此需要引号。 当变量在执行过程中传递至突变时,架构验证将正确解释 `ReactionContent` 类型。 +You may notice that the `content` field value in the earlier example (where it's used directly in the mutation) does not have quotes around `HOORAY`, but it does have quotes when used in the variable. There's a reason for this: +* When you use `content` directly in the mutation, the schema expects the value to be of type [`ReactionContent`](/graphql/reference/enums#reactioncontent), which is an _enum_, not a string. Schema validation will throw an error if you add quotes around the enum value, as quotes are reserved for strings. +* When you use `content` in a variable, the variables section must be valid JSON, so the quotes are required. Schema validation correctly interprets the `ReactionContent` type when the variable is passed into the mutation during execution. -有关枚举与字符串之间差异的更多信息,请参阅[官方 GraphQL 规格](https://graphql.github.io/graphql-spec/June2018/#sec-Enums)。 +For more information on the difference between enums and strings, see the [official GraphQL spec](https://graphql.github.io/graphql-spec/June2018/#sec-Enums). {% endnote %} -## 延伸阅读 +## Further reading -建立 GraphQL 调用时,可执行更多操作。 下面是接下来要阅读的一些内容: +There is a _lot_ more you can do when forming GraphQL calls. Here are some places to look next: -* [分页](https://graphql.org/learn/pagination/) -* [片段](https://graphql.org/learn/queries/#fragments) -* [行内分段](https://graphql.org/learn/queries/#inline-fragments) -* [指令](https://graphql.org/learn/queries/#directives) +* [Pagination](https://graphql.org/learn/pagination/) +* [Fragments](https://graphql.org/learn/queries/#fragments) +* [Inline fragments](https://graphql.org/learn/queries/#inline-fragments) +* [Directives](https://graphql.org/learn/queries/#directives) diff --git a/translations/zh-CN/content/graphql/guides/introduction-to-graphql.md b/translations/zh-CN/content/graphql/guides/introduction-to-graphql.md index 028b38a782..8459cf109f 100644 --- a/translations/zh-CN/content/graphql/guides/introduction-to-graphql.md +++ b/translations/zh-CN/content/graphql/guides/introduction-to-graphql.md @@ -1,6 +1,6 @@ --- -title: GraphQL 简介 -intro: 了解使用 GitHub GraphQL API 的有用术语和概念。 +title: Introduction to GraphQL +intro: Learn useful terminology and concepts for using the GitHub GraphQL API. redirect_from: - /v4/guides/intro-to-graphql - /graphql/guides/intro-to-graphql @@ -11,40 +11,36 @@ versions: ghae: '*' topics: - API -ms.openlocfilehash: abc74dfd4aa65035405fd956c6438a487381284b -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145066670' --- -## GraphQL 术语 -GitHub GraphQL API 表示 GitHub REST API 发生的架构和概念转变。 你可能会在 GraphQL API [参考文档](/graphql)中遇到一些新术语。 +## GraphQL terminology -## 架构 +The GitHub GraphQL API represents an architectural and conceptual shift from the GitHub REST API. You will likely encounter some new terminology in the GraphQL API [reference docs](/graphql). -架构可定义 GraphQL API 的类型系统。 它将描述客户端可以访问的完整可能数据集(对象、字段、关系、一切)。 来自客户端的调用已针对架构进行[验证](https://graphql.github.io/learn/validation/)和[执行](https://graphql.github.io/learn/execution/)。 客户端可通过[省](#discovering-the-graphql-api)找到有关架构的信息。 架构位于 GraphQL API 服务器上。 有关详细信息,请参阅“[发现 GraphQL API](#discovering-the-graphql-api)”。 +## Schema -## 字段 +A schema defines a GraphQL API's type system. It describes the complete set of possible data (objects, fields, relationships, everything) that a client can access. Calls from the client are [validated](https://graphql.github.io/learn/validation/) and [executed](https://graphql.github.io/learn/execution/) against the schema. A client can find information about the schema via [introspection](#discovering-the-graphql-api). A schema resides on the GraphQL API server. For more information, see "[Discovering the GraphQL API](#discovering-the-graphql-api)." -字段是一种可从对象检索的数据单元。 正如[官方 GraphQL 文档](https://graphql.github.io/learn/schema/)所述:“GraphQL 查询语言主要关于选择对象的字段。”。 +## Field -[官方规范](https://graphql.github.io/graphql-spec/June2018/#sec-Language.Fields)还提到了字段: +A field is a unit of data you can retrieve from an object. As the [official GraphQL docs](https://graphql.github.io/learn/schema/) say: +"The GraphQL query language is basically about selecting fields on objects." -> 所有 GraphQL 操作都必须将其选项指定为可返回标量值的字段,以确保得到明确响应。 +The [official spec](https://graphql.github.io/graphql-spec/June2018/#sec-Language.Fields) also says about fields: -这意味着,如果您尝试返回的字段不是标量,架构验证将出现错误。 必须添加嵌套子字段,直到所有字段都返回标量。 +> All GraphQL operations must specify their selections down to fields which return scalar values to ensure an unambiguously shaped response. -## 参数 +This means that if you try to return a field that is not a scalar, schema validation will throw an error. You must add nested subfields until all fields return scalars. -参数是指一组附加至特定字段的键值对。 某些字段需要参数。 [Mutation](/graphql/guides/forming-calls-with-graphql#about-mutations) 需要输入对象作为参数。 +## Argument -## 实现 +An argument is a set of key-value pairs attached to a specific field. Some fields require an argument. [Mutations](/graphql/guides/forming-calls-with-graphql#about-mutations) require an input object as an argument. -GraphQL 架构可以使用术语“实现”来定义对象如何从[接口](/graphql/reference/interfaces)继承。 +## Implementation -下面是定义接口 `X` 和对象 `Y` 的架构的设计示例: +A GraphQL schema may use the term _implements_ to define how an object inherits from an [interface](/graphql/reference/interfaces). + +Here's a contrived example of a schema that defines interface `X` and object `Y`: ``` interface X { @@ -59,33 +55,33 @@ type Y implements X { } ``` -这意味着,对象 `Y` 需要与接口 `X` 相同的字段/参数/返回类型,同时添加特定于对象 `Y` 的新字段。 (`!` 表示该字段为必填项。) +This means object `Y` requires the same fields/arguments/return types that interface `X` does, while adding new fields specific to object `Y`. (The `!` means the field is required.) -在参考文档中,您将发现: +In the reference docs, you'll find that: -* 每个[对象](/graphql/reference/objects)都在“实现”下列出了其继承的接口。 +* Each [object](/graphql/reference/objects) lists the interface(s) _from which it inherits_ under **Implements**. -* 每个[接口](/graphql/reference/interfaces)都在“实现”下列出了从其继承的对象。 +* Each [interface](/graphql/reference/interfaces) lists the objects _that inherit from it_ under **Implementations**. -## 连接 +## Connection -连接可用于查询作为同一个调用的一部分的相关对象。 通过连接,可以使用单个 GraphQL 调用,其中,必须对 REST API 使用多个调用。 有关详细信息,请参阅“[从 REST 迁移到 GraphQL](/graphql/guides/migrating-from-rest-to-graphql)”。 +Connections let you query related objects as part of the same call. With connections, you can use a single GraphQL call where you would have to use multiple calls to a REST API. For more information, see "[Migrating from REST to GraphQL](/graphql/guides/migrating-from-rest-to-graphql)." -它有助于绘制图形:用线连接点。 点是节点,线是边缘。 连接可定义节点之间的关系。 +It's helpful to picture a graph: dots connected by lines. The dots are nodes, the lines are edges. A connection defines a relationship between nodes. -## 边缘 +## Edge -边缘表示节点之间的连接。 查询连接时,可以遍历边缘获取节点。 每个 `edges` 字段都有一个 `node` 字段和 `cursor` 一个字段。 游标用于[分页](https://graphql.github.io/learn/pagination/)。 +Edges represent connections between nodes. When you query a connection, you traverse its edges to get to its nodes. Every `edges` field has a `node` field and a `cursor` field. Cursors are used for [pagination](https://graphql.github.io/learn/pagination/). -## 节点 +## Node -Node 是对象的通用术语。 您可以直接查找节点,或通过连接访问相关节点。 如果指定不返回[标量](/graphql/reference/scalars)的 `node`,则必须包含子字段,直到所有字段都返回标量。 有关通过 REST API 访问节点 ID 并在 GraphQL 查询中使用它们的信息,请参阅“[使用全局节点 ID](/graphql/guides/using-global-node-ids)”。 +_Node_ is a generic term for an object. You can look up a node directly, or you can access related nodes via a connection. If you specify a `node` that does not return a [scalar](/graphql/reference/scalars), you must include subfields until all fields return scalars. For information on accessing node IDs via the REST API and using them in GraphQL queries, see "[Using Global Node IDs](/graphql/guides/using-global-node-ids)." -## 了解 GraphQL API +## Discovering the GraphQL API -GraphQL 是[内省的](https://graphql.github.io/learn/introspection/)。 这意味着,您可以查询 GraphQL 架构,了解关于其自身的详细信息。 +GraphQL is [introspective](https://graphql.github.io/learn/introspection/). This means you can query a GraphQL schema for details about itself. -* 查询 `__schema` 以列出架构中定义的所有类型并获取关于每个类型的详细信息: +* Query `__schema` to list all types defined in the schema and get details about each: ```graphql query { @@ -102,7 +98,7 @@ GraphQL 是[内省的](https://graphql.github.io/learn/introspection/)。 这意 } ``` -* 查询 `__type` 以获取有关任何类型的详细信息: +* Query `__type` to get details about any type: ```graphql query { @@ -117,31 +113,31 @@ GraphQL 是[内省的](https://graphql.github.io/learn/introspection/)。 这意 } ``` -* 还可以通过 `GET` 请求运行架构的内省查询: +* You can also run an _introspection query_ of the schema via a `GET` request: ```shell - $ curl -H "Authorization: bearer token" {% data variables.product.graphql_url_pre %} + $ curl -H "Authorization: bearer TOKEN" {% data variables.product.graphql_url_pre %} ``` {% note %} - 注意:如果收到响应 `"message": "Bad credentials"` 或 `401 Unauthorized`,请检查你所使用的令牌是否有效。 有关详细信息,请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 + **Note**: If you get the response `"message": "Bad credentials"` or `401 Unauthorized`, check that you are using a valid token. The GraphQL API only supports authentication using a {% data variables.product.pat_v1 %}. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." {% endnote %} - 结果出现在 JSON 中,因此,我们建议整洁打印,以便阅读和搜索。 为此,可使用 [jq](https://stedolan.github.io/jq/) 等命令行工具或将结果通过管道传输到 `python -m json.tool`。 + The results are in JSON, so we recommend pretty-printing them for easier reading and searching. You can use a command-line tool like [jq](https://stedolan.github.io/jq/) or pipe the results into `python -m json.tool` for this purpose. - 或者,也可以传递 `idl` 媒体类型,以返回 IDL 格式的结果,这是架构的压缩版本: + Alternatively, you can pass the `idl` media type to return the results in IDL format, which is a condensed version of the schema: ```shell - $ curl -H "Authorization: bearer token" -H "Accept: application/vnd.github.v4.idl" \ + $ curl -H "Authorization: bearer TOKEN" -H "Accept: application/vnd.github.v4.idl" \ {% data variables.product.graphql_url_pre %} ``` {% note %} - 注意:自省查询可能是将在 GraphQL 中运行的唯一 `GET` 请求。 如果要传递正文,则无论是查询还是突变,GraphQL 请求方法都为 `POST`。 + **Note**: The introspection query is probably the only `GET` request you'll run in GraphQL. If you're passing a body, the GraphQL request method is `POST`, whether it's a query or a mutation. {% endnote %} - 有关执行查询的详细信息,请参阅“[使用 GraphQL 形成调用](/graphql/guides/forming-calls-with-graphql)”。 + For more information about performing queries, see "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." diff --git a/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md b/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md index 306156d08b..6c5a8fa020 100644 --- a/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md @@ -1,6 +1,6 @@ --- -title: 管理企业帐户 -intro: 您可以使用 GraphQL API 管理企业帐户及其拥有的组织。 +title: Managing enterprise accounts +intro: You can manage your enterprise account and the organizations it owns with the GraphQL API. redirect_from: - /v4/guides/managing-enterprise-accounts versions: @@ -10,99 +10,96 @@ versions: topics: - API shortTitle: Manage enterprise accounts -ms.openlocfilehash: bdfcca52766b85406df12b597822d5a5a596f26b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145066666' --- -## 关于使用 GraphQL 管理企业帐户 -为帮助您监测和更改组织并保持合规性,可以使用只能作为 GraphQL API 的企业帐户 API 和审核日志 API。 +## About managing enterprise accounts with GraphQL -企业帐户端点适用于 GitHub Enterprise Cloud 和 GitHub Enterprise Server。 +To help you monitor and make changes in your organizations and maintain compliance, you can use the Enterprise Accounts API and the Audit Log API, which are only available as GraphQL APIs. -使用 GraphQL 可以请求并仅返回指定的数据。 例如,可以创建 GraphQL 查询或请求信息,以查看添加到组织的所有新组织成员。 或者,可以做出更改,以邀请管理员加入企业帐户。 +The enterprise account endpoints work for both GitHub Enterprise Cloud and for GitHub Enterprise Server. -使用审核日志 API,可以监视下列行为: -- 访问组织或存储库设置。 -- 更改权限。 -- 在组织、存储库或团队中添加或删除用户。 -- 将用户提升为管理员。 -- 更改 GitHub 应用权限。 +GraphQL allows you to request and return just the data you specify. For example, you can create a GraphQL query, or request for information, to see all the new organization members added to your organization. Or you can make a mutation, or change, to invite an administrator to your enterprise account. -使用审核日志 API 可以保留审核日志数据的副本。 对于使用审核日志 API 执行的查询,GraphQL 响应最多可包含 90 至 120 天的数据。 有关审核日志 API 提供的字段列表,请参阅“[AuditEntry 接口](/graphql/reference/interfaces#auditentry/)”。 +With the Audit Log API, you can monitor when someone: +- Accesses your organization or repository settings. +- Changes permissions. +- Adds or removes users in an organization, repository, or team. +- Promotes users to admin. +- Changes permissions of a GitHub App. -通过企业帐户 API,可以: -- 列出并审查属于企业帐户的所有组织和仓库。 -- 更改企业帐户设置。 -- 配置企业帐户及其组织的设置策略。 -- 邀请管理员加入您的企业帐户。 -- 在企业帐户中创建新组织。 +The Audit Log API enables you to keep copies of your audit log data. For queries made with the Audit Log API, the GraphQL response can include data for up to 90 to 120 days. For a list of the fields available with the Audit Log API, see the "[AuditEntry interface](/graphql/reference/interfaces#auditentry/)." -有关企业帐户 API 提供的字段列表,请参阅“[企业帐户 API 的 GraphQL 字段和类型](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)”。 +With the Enterprise Accounts API, you can: +- List and review all of the organizations and repositories that belong to your enterprise account. +- Change Enterprise account settings. +- Configure policies for settings on your enterprise account and its organizations. +- Invite administrators to your enterprise account. +- Create new organizations in your enterprise account. -## 开始将 GraphQL 用于企业帐户 +For a list of the fields available with the Enterprise Accounts API, see "[GraphQL fields and types for the Enterprise account API](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)." -按照以下步骤开始利用 GraphQL 管理企业帐户: - - 使用个人访问令牌进行身份验证 - - 选择 GraphQL 客户端或使用 GraphQL Explorer - - 设置 Insomnia 以使用 GraphQL API +## Getting started using GraphQL for enterprise accounts -如需一些示例查询,请参阅“[使用企业帐户 API 的示例查询](#an-example-query-using-the-enterprise-accounts-api)”。 +Follow these steps to get started using GraphQL to manage your enterprise accounts: + - Authenticating with a {% data variables.product.pat_generic %} + - Choosing a GraphQL client or using the GraphQL Explorer + - Setting up Insomnia to use the GraphQL API -### 1. 使用个人访问令牌进行身份验证 +For some example queries, see "[An example query using the Enterprise Accounts API](#an-example-query-using-the-enterprise-accounts-api)." -1. 要使用 GraphQL 进行身份验证,需要通过开发者设置生成个人访问令牌 (PAT)。 有关详细信息,请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 +### 1. Authenticate with your {% data variables.product.pat_generic %} -2. 向要访问的 GHES 区域的个人访问令牌授予管理员和完全控制权限。 要获得对私有仓库、组织、团队、用户数据及企业帐单和个人资料数据访问的完全权限,建议您为个人访问令牌选择以下作用域: +{% data reusables.user-settings.graphql-classic-pat-only %} + +1. To authenticate with GraphQL, you need to generate a {% data variables.product.pat_generic %} from developer settings. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." + +2. Grant admin and full control permissions to your {% data variables.product.pat_generic %} for areas of GHES you'd like to access. For full permission to private repositories, organizations, teams, user data, and access to enterprise billing and profile data, we recommend you select these scopes for your {% data variables.product.pat_generic %}: - `repo` - `admin:org` - `user` - `admin:enterprise` - 企业帐户特定作用域包括: - - `admin:enterprise`:完全控制企业(包括 {% ifversion ghes > 3.2 or ghae or ghec %}`manage_runners:enterprise`、{% endif %}`manage_billing:enterprise` 和 `read:enterprise`) - - `manage_billing:enterprise`:读取和写入企业账单数据。{% ifversion ghes > 3.2 or ghae %} - - `manage_runners:enterprise`:获得管理 GitHub Actions 企业运行器和运行器组的权限。{% endif %} - - `read:enterprise`:读取企业资料数据。 + The enterprise account specific scopes are: + - `admin:enterprise`: Gives full control of enterprises (includes {% ifversion ghes > 3.2 or ghae or ghec %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` and `read:enterprise`) + - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes > 3.2 or ghae %} + - `manage_runners:enterprise`: Access to manage GitHub Actions enterprise runners and runner-groups.{% endif %} + - `read:enterprise`: Read enterprise profile data. -3. 复制个人访问令牌并保存在安全的位置,直到将其添加至您的 GraphQL 客户端。 +3. Copy your {% data variables.product.pat_generic %} and keep it in a secure place until you add it to your GraphQL client. -### 2. 选择 GraphQL 客户端 +### 2. Choose a GraphQL client -建议您使用 GraphiQL 或可用于配置基准 URL 的其他独立 GraphQL 客户端。 +We recommend you use GraphiQL or another standalone GraphQL client that lets you configure the base URL. -也可以考虑使用以下 GraphQL 客户端: +You may also consider using these GraphQL clients: - [Insomnia](https://support.insomnia.rest/article/176-graphql-queries) - [GraphiQL](https://www.gatsbyjs.org/docs/running-queries-with-graphiql/) - [Postman](https://learning.getpostman.com/docs/postman/sending_api_requests/graphql/) -接下来将使用 Insomnia。 +The next steps will use Insomnia. -### 3. 设置 Insomnia,将 GitHub GraphQL API 用于企业帐户 +### 3. Setting up Insomnia to use the GitHub GraphQL API with enterprise accounts -1. 将基 url 和 `POST` 方法添加至 GraphQL 客户端。 使用 GraphQL 请求信息(查询)、更改信息(突变)或使用 GitHub API 传输数据时,默认 HTTP 方法为 `POST`,基 url 遵循此语法: - - 对于企业实例:`https:///api/graphql` - - 对于 GitHub Enterprise 云:`https://api.github.com/graphql` +1. Add the base url and `POST` method to your GraphQL client. When using GraphQL to request information (queries), change information (mutations), or transfer data using the GitHub API, the default HTTP method is `POST` and the base url follows this syntax: + - For your enterprise instance: `https:///api/graphql` + - For GitHub Enterprise Cloud: `https://api.github.com/graphql` -2. 要进行身份验证,请打开身份验证选项菜单,并选择“持有者令牌”。 接下来,添加您之前复制的个人访问令牌。 +2. To authenticate, open the authentication options menu and select **Bearer token**. Next, add your {% data variables.product.pat_generic %} that you copied earlier. - ![个人访问令牌的权限选项](/assets/images/developer/graphql/insomnia-base-url-and-pat.png) + ![Permissions options for {% data variables.product.pat_generic %}](/assets/images/developer/graphql/insomnia-base-url-and-pat.png) - ![个人访问令牌的权限选项](/assets/images/developer/graphql/insomnia-bearer-token-option.png) + ![Permissions options for {% data variables.product.pat_generic %}](/assets/images/developer/graphql/insomnia-bearer-token-option.png) -3. 加入标头信息。 - - 添加 `Content-Type` 和 `application/json` 分别作为标头和值。 - ![标准标头](/assets/images/developer/graphql/json-content-type-header.png) - ![包含审核日志 API 预览值的标头](/assets/images/developer/graphql/preview-header-for-2.18.png) +3. Include header information. + - Add `Content-Type` as the header and `application/json` as the value. + ![Standard header](/assets/images/developer/graphql/json-content-type-header.png) + ![Header with preview value for the Audit Log API](/assets/images/developer/graphql/preview-header-for-2.18.png) -现在可以开始执行查询了。 +Now you are ready to start making queries. -## 使用企业账户 API 的查询示例 +## An example query using the Enterprise Accounts API -此 GraphQL 查询使用 Enterprise Accounts API 请求每个设备的组织中 {% ifversion not ghae %}`public`{% else %}`private`{% endif %} 存储库的总数。 要自定义此查询,请用企业帐户的句柄替换 ``。 例如,如果企业帐户位于 `https://github.com/enterprises/octo-enterprise`,请用 `octo-enterprise` 替换 ``。 +This GraphQL query requests the total number of {% ifversion not ghae %}`public`{% else %}`private`{% endif %} repositories in each of your appliance's organizations using the Enterprise Accounts API. To customize this query, replace `` with the handle for your enterprise account. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `` with `octo-enterprise`. {% ifversion not ghae %} @@ -169,7 +166,7 @@ variables { ``` {% endif %} -下一个 GraphQL 查询示例显示了在不使用企业帐户 API 的情况下检索每个组织中的 {% ifversion not ghae %}`public`{% else %}`private`{% endif %} 存储库总数的难度。 请注意,GraphQL 企业账户 API 已使企业执行此任务变得更简单,因为您只需要自定义单个变量。 要自定义此查询,请将 `` 和 `` 等项替换为实例中的组织名称。 +The next GraphQL query example shows how challenging it is to retrieve the number of {% ifversion not ghae %}`public`{% else %}`private`{% endif %} repositories in each organization without using the Enterprise Account API. Notice that the GraphQL Enterprise Accounts API has made this task simpler for enterprises since you only need to customize a single variable. To customize this query, replace `` and ``, etc. with the organization names on your instance. {% ifversion not ghae %} ```graphql @@ -217,7 +214,7 @@ fragment repositories on Organization { ``` {% endif %} -## 分别查询每个组织 +## Query each organization separately {% ifversion not ghae %} @@ -265,7 +262,7 @@ fragment repositories on Organization { {% endif %} -此 GraphQL 查询用于请求企业组织的最后 5 个日志条目。 要自定义此查询,请替换 `` 和 ``。 +This GraphQL query requests the last 5 log entries for an enterprise organization. To customize this query, replace `` and ``. ```graphql { @@ -291,13 +288,13 @@ fragment repositories on Organization { } ``` -有关开始使用 GraphQL 的更多信息,请参阅“[GraphQL 简介](/graphql/guides/introduction-to-graphql)”和“[使用 GraphQL 形成调用](/graphql/guides/forming-calls-with-graphql)”。 +For more information about getting started with GraphQL, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)" and "[Forming Calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." -## 企业账户 API 的 GraphQL 字段和类型 +## GraphQL fields and types for the Enterprise Accounts API -下面是关于可与企业账户 API 结合使用的新查询、突变和架构定义类型的概述。 +Here's an overview of the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API. -有关可与企业帐户 API 结合使用的新查询、突变和架构定义类型的详细信息,请参阅任何 [GraphQL 参考页面](/graphql)含有详细 GraphQL 定义的边栏。 +For more details about the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API, see the sidebar with detailed GraphQL definitions from any [GraphQL reference page](/graphql). -您可以从 GitHub 的 GraphQL explorer 访问参考文档。 有关详细信息,请参阅“[使用资源管理器](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)”。 -有关其他信息,如身份验证和速率限制详细信息,请查看[指南](/graphql/guides)。 +You can access the reference docs from within the GraphQL explorer on GitHub. For more information, see "[Using the explorer](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)." +For other information, such as authentication and rate limit details, check out the [guides](/graphql/guides). diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md index 5898ff29f2..aa83f058df 100644 --- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md +++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md @@ -1,79 +1,74 @@ --- -title: '关于 {% data variables.product.prodname_projects_v1 %}' -intro: '{% data variables.product.product_name %} 上的 {% data variables.product.prodname_projects_v1_caps %} 有助于组织工作和排列工作优先级。 可以为特定功能工作、全面的路线图甚至发布检查列表创建 {% data variables.projects.projects_v1_boards %}。 通过 {% data variables.product.prodname_projects_v1 %},可以灵活地创建适合需求的自定义工作流。' +title: About {% data variables.product.prodname_projects_v1 %} +intro: '{% data variables.product.prodname_projects_v1_caps %} on {% data variables.product.product_name %} help you organize and prioritize your work. You can create {% data variables.projects.projects_v1_boards %} for specific feature work, comprehensive roadmaps, or even release checklists. With {% data variables.product.prodname_projects_v1 %}, you have the flexibility to create customized workflows that suit your needs.' redirect_from: - /github/managing-your-work-on-github/managing-project-boards/about-project-boards - /articles/about-projects - /articles/about-project-boards - /github/managing-your-work-on-github/about-project-boards versions: - feature: projects-v1 + feature: "projects-v1" topics: - Pull requests allowTitleToDifferFromFilename: true -ms.openlocfilehash: 5ec81cf456ddca503e58ca6703ae3372875bd62c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147614237' --- + {% data reusables.projects.project_boards_old %} -{% data variables.projects.projects_v1_boards_caps %} 包括问题、拉取请求和注释,在选择的列中分类为卡。 您可以拖放或使用键盘快捷键对列中的卡片重新排序,在不同列之间移动卡片,以及更改列的顺序。 +{% data variables.projects.projects_v1_boards_caps %} are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. You can drag and drop or use keyboard shortcuts to reorder cards within a column, move cards from column to column, and change the order of columns. -{% data variables.projects.projects_v1_board_caps %} 卡包含问题和拉取请求的相关元数据,如标签、被分派人、状态和创建者。 {% data reusables.project-management.edit-in-project %} +{% data variables.projects.projects_v1_board_caps %} cards contain relevant metadata for issues and pull requests, like labels, assignees, the status, and who opened it. {% data reusables.project-management.edit-in-project %} -可以在列中创建注释以用作任务提醒、对 {% data variables.product.product_location %} 上任何存储库中的问题和拉取请求的引用,或用于添加与 {% data variables.projects.projects_v1_board %} 相关的信息。 可以通过在注释中添加链接,为另一个 {% data variables.projects.projects_v1_board %} 创建参考卡。 如果注释不足以满足您的需求,您可以将其转换为议题。 有关将注释转换为问题的详细信息,请参阅“[向 {% data variables.product.prodname_project_v1 %} 添加注释](/articles/adding-notes-to-a-project-board)”。 +You can create notes within columns to serve as task reminders, references to issues and pull requests from any repository on {% data variables.location.product_location %}, or to add information related to the {% data variables.projects.projects_v1_board %}. You can create a reference card for another {% data variables.projects.projects_v1_board %} by adding a link to a note. If the note isn't sufficient for your needs, you can convert it to an issue. For more information on converting notes to issues, see "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)." -项目板的类型: +Types of project boards: -- 用户拥有的 {% data variables.projects.projects_v1_board %} 可以包含任何个人存储库中的问题和拉取请求。 -- 组织范围的 {% data variables.projects.projects_v1_board %} 可以包含属于组织的任何存储库中的问题和拉取请求。 {% data reusables.project-management.link-repos-to-project-board %} 有关详细信息,请参阅“[将存储库链接到 {% data variables.product.prodname_project_v1 %}](/articles/linking-a-repository-to-a-project-board)”。 -- **存储库 {% data variables.projects.projects_v1_board %}** 包含单一存储库中的问题和拉取请求。 它们也可包含引用其他仓库中议题和拉取请求的注释。 +- **User-owned {% data variables.projects.projects_v1_board %}** can contain issues and pull requests from any personal repository. +- **Organization-wide {% data variables.projects.projects_v1_board %}** can contain issues and pull requests from any repository that belongs to an organization. {% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a {% data variables.product.prodname_project_v1 %}](/articles/linking-a-repository-to-a-project-board)." +- **Repository {% data variables.projects.projects_v1_board %}** are scoped to issues and pull requests within a single repository. They can also include notes that reference issues and pull requests in other repositories. -## 创建和查看 {% data variables.projects.projects_v1_boards %} +## Creating and viewing {% data variables.projects.projects_v1_boards %} -若要为组织创建 {% data variables.projects.projects_v1_board %},必须是组织成员。 组织所有者或具有 {% data variables.projects.projects_v1_board %} 管理员权限的人员可以自定义对 {% data variables.projects.projects_v1_board %} 的访问权限。 +To create a {% data variables.projects.projects_v1_board %} for your organization, you must be an organization member. Organization owners and people with {% data variables.projects.projects_v1_board %} admin permissions can customize access to the {% data variables.projects.projects_v1_board %}. {% ifversion classic-project-visibility-permissions %}{% data reusables.projects.owners-can-limit-visibility-permissions %}{% endif %} -如果组织拥有的 {% data variables.projects.projects_v1_board %} 包含你没有查看权限的存储库中的问题和拉取请求,将对该卡进行编辑。 有关详细信息,请参阅“[组织的 {% data variables.product.prodname_project_v1_caps %} 权限](/articles/project-board-permissions-for-an-organization)”。 +If an organization-owned {% data variables.projects.projects_v1_board %} includes issues or pull requests from a repository that you don't have permission to view, the card will be redacted. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." -活动视图显示 {% data variables.projects.projects_v1_board %} 的最近历史记录,例如某人创建的卡或在列之间移动的卡。 若要访问活动视图,请单击“菜单”并向下滚动。 +The activity view shows the {% data variables.projects.projects_v1_board %}'s recent history, such as cards someone created or moved between columns. To access the activity view, click **Menu** and scroll down. -若要查找 {% data variables.projects.projects_v1_board %} 上的特定卡或查看一部分卡,可以筛选 {% data variables.projects.projects_v1_board %} 卡。 有关详细信息,请参阅“[筛选 {% data variables.product.prodname_project_v1 %} 上的卡](/articles/filtering-cards-on-a-project-board)”。 +To find specific cards on a {% data variables.projects.projects_v1_board %} or view a subset of the cards, you can filter {% data variables.projects.projects_v1_board %} cards. For more information, see "[Filtering cards on a {% data variables.product.prodname_project_v1 %}](/articles/filtering-cards-on-a-project-board)." -为简化工作流并从 {% data variables.projects.projects_v1_board %} 移除已完成的任务,可以将卡存档。 有关详细信息,请参阅“[对 {% data variables.product.prodname_project_v1 %} 上的卡进行存档](/articles/archiving-cards-on-a-project-board)”。 +To simplify your workflow and keep completed tasks off your {% data variables.projects.projects_v1_board %}, you can archive cards. For more information, see "[Archiving cards on a {% data variables.product.prodname_project_v1 %}](/articles/archiving-cards-on-a-project-board)." -如果已完成所有 {% data variables.projects.projects_v1_board %} 任务,或者无需再使用 {% data variables.projects.projects_v1_board %},可以关闭 {% data variables.projects.projects_v1_board %}。 有关详细信息,请参阅“[关闭 {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)”。 +If you've completed all of your {% data variables.projects.projects_v1_board %} tasks or no longer need to use your {% data variables.projects.projects_v1_board %}, you can close the {% data variables.projects.projects_v1_board %}. For more information, see "[Closing a {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)." -如果希望以不同的方式跟踪工作,还可以[禁用存储库中的 {% data variables.projects.projects_v1_boards %}](/articles/disabling-project-boards-in-a-repository) 或[禁用组织中的 {% data variables.projects.projects_v1_boards %}](/articles/disabling-project-boards-in-your-organization)。 +You can also [disable {% data variables.projects.projects_v1_boards %} in a repository](/articles/disabling-project-boards-in-a-repository) or [disable {% data variables.projects.projects_v1_boards %} in your organization](/articles/disabling-project-boards-in-your-organization), if you prefer to track your work in a different way. {% data reusables.project-management.project-board-import-with-api %} -## {% data variables.projects.projects_v1_boards %} 的模板 +## Templates for {% data variables.projects.projects_v1_boards %} -可以使用模板快速设置新的 {% data variables.projects.projects_v1_board %}。 在使用模板创建 {% data variables.projects.projects_v1_board %} 时,新板将包含列以及具有 {% data variables.product.prodname_projects_v1 %} 使用提示的卡。 您也可以选择已配置自动化的模板。 +You can use templates to quickly set up a new {% data variables.projects.projects_v1_board %}. When you use a template to create a {% data variables.projects.projects_v1_board %}, your new board will include columns as well as cards with tips for using {% data variables.product.prodname_projects_v1 %}. You can also choose a template with automation already configured. -| 模板 | 说明 | +| Template | Description | | --- | --- | -| 基本看板 | 使用 To do(待处理)、In progress(进行中)和 Done(已完成)列跟踪您的任务 | -| 自动化看板 | 卡自动在 To do(待处理)、In progress(进行中)和 Done(已完成)列之间移动 | -| 带审查的自动化看板 | 板卡自动在 To do(待处理)、In progress(进行中)和 Done(已完成)列之间移动,并且包含拉取请求审查状态的附加触发条件 | -| 漏洞查验 | 通过 To do(待处理)、In progress(进行中)和 Done(已完成)列查验漏洞并排列优先级 | +| Basic kanban | Track your tasks with To do, In progress, and Done columns | +| Automated kanban | Cards automatically move between To do, In progress, and Done columns | +| Automated kanban with review | Cards automatically move between To do, In progress, and Done columns, with additional triggers for pull request review status | +| Bug triage | Triage and prioritize bugs with To do, High priority, Low priority, and Closed columns | -有关 {% data variables.product.prodname_projects_v1 %} 自动化的详细信息,请参阅“[关于 {% data variables.product.prodname_projects_v1 %} 的自动化](/articles/about-automation-for-project-boards)”。 +For more information on automation for {% data variables.product.prodname_projects_v1 %}, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)." -![具有基本看板模板的 {% data variables.product.prodname_project_v1 %}](/assets/images/help/projects/project-board-basic-kanban-template.png) +![{% data variables.product.prodname_project_v1 %} with basic kanban template](/assets/images/help/projects/project-board-basic-kanban-template.png) {% data reusables.project-management.copy-project-boards %} -## 延伸阅读 +## Further reading -- [创建 {% data variables.product.prodname_project_v1 %}](/articles/creating-a-project-board) -- [编辑 {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board){% ifversion fpt or ghec %} -- [复制 {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board)"{% endif %} -- [向 {% data variables.product.prodname_project_v1 %} 添加问题和拉取请求](/articles/adding-issues-and-pull-requests-to-a-project-board) -- [组织的 {% data variables.product.prodname_project_v1_caps %} 权限](/articles/project-board-permissions-for-an-organization) -- [键盘快捷方式](/articles/keyboard-shortcuts/#project-boards) +- "[Creating a {% data variables.product.prodname_project_v1 %}](/articles/creating-a-project-board)" +- "[Editing a {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)"{% ifversion fpt or ghec %} +- "[Copying a {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board)"{% endif %} +- "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)" +- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)" +- "[Keyboard shortcuts](/articles/keyboard-shortcuts/#project-boards)" diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md index f13496285f..3b0e137b23 100644 --- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md +++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md @@ -1,58 +1,54 @@ --- -title: '使用 Actions 自动化 {% data variables.product.prodname_projects_v2 %}' -shortTitle: Automating with Actions -intro: '可以使用 {% data variables.product.prodname_actions %} 自动化你的项目。' +title: 'Automating {% data variables.product.prodname_projects_v2 %} using Actions' +shortTitle: 'Automating with Actions' +intro: 'You can use {% data variables.product.prodname_actions %} to automate your projects.' miniTocMaxHeadingLevel: 3 versions: - feature: projects-v2 + feature: "projects-v2" redirect_from: - /issues/trying-out-the-new-projects-experience/automating-projects type: tutorial topics: - Projects allowTitleToDifferFromFilename: true -ms.openlocfilehash: 7c1d37f43653204eba7f3bf4c1b9b5ab6b01db51 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147423900' --- -## {% data variables.product.prodname_actions %} 工作流程 -本节说明如何使用 GraphQL API 和 {% data variables.product.prodname_actions %} 向组织项目添加拉取请求。 在示例工作流程中,当拉取请求标记为“准备审核”时,项目中会添加一项“状态”字段设置为“待办”的新任务,并且当前日期添加到自定义的“发布日期”字段中。 -您可以复制以下工作流程之一,并按照下表中的说明对其进行修改,以满足您的需求。 +## {% data variables.product.prodname_actions %} workflows -项目可以跨越多个仓库,但工作流是特定于仓库的。 将工作流添加到希望项目跟踪的每个存储库。有关创建工作流文件的详细信息,请参阅“[{% data variables.product.prodname_actions %} 快速入门](/actions/quickstart)”。 +This section demonstrates how to use the GraphQL API and {% data variables.product.prodname_actions %} to add a pull request to an organization project. In the example workflows, when the pull request is marked as "ready for review", a new task is added to the project with a "Status" field set to "Todo", and the current date is added to a custom "Date posted" field. -本文假设您基本了解 {% data variables.product.prodname_actions %}。 有关 {% data variables.product.prodname_actions %} 的详细信息,请参阅“[{% data variables.product.prodname_actions %}](/actions)”。 +You can copy one of the workflows below and modify it as described in the table below to meet your needs. -有关可以通过 API 对项目进行的其他更改的详细信息,请参阅“[使用 API 管理项目](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)”。 +A project can span multiple repositories, but a workflow is specific to a repository. Add the workflow to each repository that you want your project to track. For more information about creating workflow files, see "[Quickstart for {% data variables.product.prodname_actions %}](/actions/quickstart)." -你可能还希望使用 actions/add-to-project 工作流,该工作流由 {% data variables.product.company_short %} 维护,并将当前问题或拉取请求添加到指定的项目。 有关详细信息,请参阅 [actions/add-to-project](https://github.com/actions/add-to-project) 存储库和自述文件。 +This article assumes that you have a basic understanding of {% data variables.product.prodname_actions %}. For more information about {% data variables.product.prodname_actions %}, see "[{% data variables.product.prodname_actions %}](/actions)." + +For more information about other changes you can make to your project through the API, see "[Using the API to manage projects](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)." + +You may also want to use the **actions/add-to-project** workflow, which is maintained by {% data variables.product.company_short %} and will add the current issue or pull request to the project specified. For more information, see the [actions/add-to-project](https://github.com/actions/add-to-project) repository and README. {% note %} -注意:`GITHUB_TOKEN` 的范围限定为存储库级别,并且无法访问 {% data variables.projects.projects_v2 %}。 若要访问 {% data variables.projects.projects_v2 %},可以创建 {% data variables.product.prodname_github_app %}(建议用于组织项目)或个人访问令牌(建议用于用户项目)。 下面显示了这两种方法的工作流程示例。 +**Note:** `GITHUB_TOKEN` is scoped to the repository level and cannot access {% data variables.projects.projects_v2 %}. To access {% data variables.projects.projects_v2 %} you can either create a {% data variables.product.prodname_github_app %} (recommended for organization projects) or a {% data variables.product.pat_generic %} (recommended for user projects). Workflow examples for both approaches are shown below. {% endnote %} -### 使用 {% data variables.product.prodname_github_app %} 进行身份验证的示例工作流程 +### Example workflow authenticating with a {% data variables.product.prodname_github_app %} -1. 创建 {% data variables.product.prodname_github_app %} 或选择组织拥有的现有 {% data variables.product.prodname_github_app %}。 有关详细信息,请参阅“[创建 {% data variables.product.prodname_github_app %}](/developers/apps/building-github-apps/creating-a-github-app)”。 -2. 授予 {% data variables.product.prodname_github_app %} 对组织项目的读取和写入权限。 有关详细信息,请参阅“[编辑 {% data variables.product.prodname_github_app %} 的权限](/developers/apps/managing-github-apps/editing-a-github-apps-permissions)”。 +1. Create a {% data variables.product.prodname_github_app %} or choose an existing {% data variables.product.prodname_github_app %} owned by your organization. For more information, see "[Creating a {% data variables.product.prodname_github_app %}](/developers/apps/building-github-apps/creating-a-github-app)." +2. Give your {% data variables.product.prodname_github_app %} read and write permissions to organization projects. For more information, see "[Editing a {% data variables.product.prodname_github_app %}'s permissions](/developers/apps/managing-github-apps/editing-a-github-apps-permissions)." {% note %} - 注意:你可以控制应用对组织项目和存储库项目的权限。 您必须授予读取和写入组织项目的权限;读取和写入存储库项目的权限是不够的。 + **Note:** You can control your app's permission to organization projects and to repository projects. You must give permission to read and write organization projects; permission to read and write repository projects will not be sufficient. {% endnote %} -3. 在组织中安装 {% data variables.product.prodname_github_app %}。 为项目需要访问的所有存储库安装它。 有关详细信息,请参阅“[安装{% data variables.product.prodname_github_apps %}](/developers/apps/managing-github-apps/installing-github-apps#installing-your-private-github-app-on-your-repository)”。 -4. 将 {% data variables.product.prodname_github_app %} 的 ID 作为机密存储在存储库或组织中。 在以下工作流中,将 `APP_ID` 替换为机密的名称。 您可以在应用的设置页面上或通过应用 API 找到应用 ID。 有关详细信息,请参阅“[应用](/rest/reference/apps#get-an-app)”。 -5. 为应用生成私钥。 将生成的文件的内容作为机密存储在存储库或组织中。 (存储文件的全部内容,包括 `-----BEGIN RSA PRIVATE KEY-----` 和 `-----END RSA PRIVATE KEY-----`。)在以下工作流中,将 `APP_PEM` 替换为机密的名称。 有关详细信息,请参阅“[使用 {% data variables.product.prodname_github_apps %} 进行身份验证](/developers/apps/building-github-apps/authenticating-with-github-apps#generating-a-private-key)”。 -6. 在以下工作流中,将 `YOUR_ORGANIZATION` 替换为组织的名称。 例如 `octo-org`。 将 `YOUR_PROJECT_NUMBER` 替换为项目编号。 要查找项目编号,请查看项目 URL。 例如,`https://github.com/orgs/octo-org/projects/5` 的项目编号为 5。 +3. Install the {% data variables.product.prodname_github_app %} in your organization. Install it for all repositories that your project needs to access. For more information, see "[Installing {% data variables.product.prodname_github_apps %}](/developers/apps/managing-github-apps/installing-github-apps#installing-your-private-github-app-on-your-repository)." +4. Store your {% data variables.product.prodname_github_app %}'s ID as a secret in your repository or organization. In the following workflow, replace `APP_ID` with the name of the secret. You can find your app ID on the settings page for your app or through the App API. For more information, see "[Apps](/rest/reference/apps#get-an-app)." +5. Generate a private key for your app. Store the contents of the resulting file as a secret in your repository or organization. (Store the entire contents of the file, including `-----BEGIN RSA PRIVATE KEY-----` and `-----END RSA PRIVATE KEY-----`.) In the following workflow, replace `APP_PEM` with the name of the secret. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#generating-a-private-key)." +6. In the following workflow, replace `YOUR_ORGANIZATION` with the name of your organization. For example, `octo-org`. Replace `YOUR_PROJECT_NUMBER` with your project number. To find the project number, look at the project URL. For example, `https://github.com/orgs/octo-org/projects/5` has a project number of 5. ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -171,11 +167,11 @@ jobs: ``` -### 使用个人访问令牌进行身份验证的示例工作流程 +### Example workflow authenticating with a {% data variables.product.pat_generic %} -1. 使用 `project` 和 `repo` 范围创建个人访问令牌。 有关详细信息,请参阅“[创建个人访问令牌](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)”。 -2. 将个人访问令牌另存为存储库或组织中的机密。 -3. 在以下工作流中,将 `YOUR_TOKEN` 替换为机密的名称。 将 `YOUR_ORGANIZATION` 替换为组织的名称。 例如,`octo-org`。 将 `YOUR_PROJECT_NUMBER` 替换为项目编号。 要查找项目编号,请查看项目 URL。 例如,`https://github.com/orgs/octo-org/projects/5` 的项目编号为 5。 +1. Create a {% data variables.product.pat_v1 %} with the `project` and `repo` scopes. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." +2. Save the {% data variables.product.pat_generic %} as a secret in your repository or organization. +3. In the following workflow, replace `YOUR_TOKEN` with the name of the secret. Replace `YOUR_ORGANIZATION` with the name of your organization. For example, `octo-org`. Replace `YOUR_PROJECT_NUMBER` with your project number. To find the project number, look at the project URL. For example, `https://github.com/orgs/octo-org/projects/5` has a project number of 5. ```yaml{:copy} name: Add PR to project @@ -283,9 +279,9 @@ jobs: ``` -### 工作流程说明 +### Workflow explanation -下表说明了示例工作流程的各个部分,并向您展示了如何调整工作流程以供自己使用。 +The following table explains sections of the example workflows and shows you how to adapt the workflows for your own use. @@ -301,14 +297,14 @@ on: @@ -399,9 +395,9 @@ gh api graphql -f query=' @@ -417,19 +413,19 @@ echo 'TODO_OPTION_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select @@ -468,7 +464,7 @@ item_id="$( gh api graphql -f query=' @@ -481,7 +477,7 @@ echo 'ITEM_ID='$item_id >> $GITHUB_ENV @@ -494,21 +490,21 @@ echo "DATE=$(date +"%Y-%m-%d")" >> $GITHUB_ENV @@ -564,7 +560,7 @@ gh api graphql -f query=' diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md index eaa903d053..875febbdd6 100644 --- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md +++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md @@ -11,6 +11,7 @@ children: - /using-the-built-in-automations - /using-the-api-to-manage-projects - /automating-projects-using-actions + - /archiving-items-automatically allowTitleToDifferFromFilename: true ms.openlocfilehash: 6c9777a65125f574e4a2cd05a7177448606f8348 ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md index 8c6927581a..afb973e02b 100644 --- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md +++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md @@ -21,7 +21,7 @@ This article demonstrates how to use the GraphQL API to manage a project. For mo {% curl %} -In all of the following cURL examples, replace `TOKEN` with a token that has the `read:project` scope (for queries) or `project` scope (for queries and mutations). The token can be a personal access token for a user or an installation access token for a {% data variables.product.prodname_github_app %}. For more information about creating a personal access token, see "[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about creating an installation access token for a {% data variables.product.prodname_github_app %}, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-a-github-app)." +In all of the following cURL examples, replace `TOKEN` with a token that has the `read:project` scope (for queries) or `project` scope (for queries and mutations). The token can be a {% data variables.product.pat_v1 %} for a user or an installation access token for a {% data variables.product.prodname_github_app %}. For more information about creating a {% data variables.product.pat_generic %}, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about creating an installation access token for a {% data variables.product.prodname_github_app %}, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-a-github-app)." {% endcurl %} diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md index 6fe19f6924..1929b511b2 100644 --- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md +++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md @@ -1,118 +1,150 @@ --- -title: 自定义视图 -intro: 通过更改项目中的布局、分组、排序来显示你所需的信息。 +title: 'Customizing a view' +intro: 'Display the information you need by changing the layout, grouping, sorting in your project.' miniTocMaxHeadingLevel: 3 versions: - feature: projects-v2 + feature: "projects-v2" redirect_from: - /issues/trying-out-the-new-projects-experience/customizing-your-project-views type: tutorial topics: - Projects -ms.openlocfilehash: 962a20daac125cdec5510daf3d792e0aaf6a194b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147423965' --- -## 更改项目布局 -您可以将项目视为表或板。 + +## Changing the project layout + +You can view your project as a table or as a board. {% data reusables.projects.open-view-menu %} -1. 在“布局”下,单击“表”或“板” 。 - ![显示“布局”选项的屏幕截图](/assets/images/help/projects-v2/table-or-board.png) +1. Under "Layout", click either **Table** or **Board**. + ![Screenshot showing layout option](/assets/images/help/projects-v2/table-or-board.png) -或者,通过按 {% data variables.projects.command-palette-shortcut %} 打开项目命令面板,然后开始键入“切换布局”。 +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Switch layout." -## 显示和隐藏字段 +## Showing and hiding fields -您可以显示或隐藏特定字段。 +You can show or hide a specific field. {% data reusables.projects.open-view-menu %} -1. 在“配置”下,单击 {% octicon "note" aria-label="the note icon" %} 和当前显示字段的列表。 - ![显示“显示和隐藏字段”菜单选项的屏幕截图](/assets/images/help/projects-v2/show-hide-fields-menu-item.png) -1. 选择或取消选择希望显示或隐藏的字段。 - ![显示“显示和隐藏字段”菜单的屏幕截图](/assets/images/help/projects-v2/show-hide-fields.png) +1. Under "Configuration", click {% octicon "note" aria-label="the note icon" %} and the list of currently shown fields. + ![Screenshot showing show and hide fields menu option](/assets/images/help/projects-v2/show-hide-fields-menu-item.png) +1. Select or deselect the fields you want to show or hide. + ![Screenshot showing show and hide fields menu](/assets/images/help/projects-v2/show-hide-fields.png) -也可以在表视图中隐藏单个字段。 +You can also hide individual fields in table view. -1. 在希望隐藏的字段的旁边,单击 {% octicon "kebab-horizontal" aria-label="the kebab icon" %}。 - ![显示“字段”菜单图标的屏幕截图](/assets/images/help/projects-v2/modify-field-menu.png) -1. 单击 {% octicon "eye-closed" aria-label="the eye closed icon" %}“隐藏字段”。 - ![显示“隐藏字段”菜单选项的屏幕截图](/assets/images/help/projects-v2/hide-field-via-menu.png) +1. Next to the field you want to hide, click {% octicon "kebab-horizontal" aria-label="the kebab icon" %}. + ![Screenshot showing field menu icon](/assets/images/help/projects-v2/modify-field-menu.png) +1. Click {% octicon "eye-closed" aria-label="the eye closed icon" %} **Hide field**. + ![Screenshot showing hide field menu option](/assets/images/help/projects-v2/hide-field-via-menu.png) -或者,通过按 {% data variables.projects.command-palette-shortcut %} 打开项目命令面板,然后开始键入“显示”、“隐藏”或字段名称。 +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "show", "hide", or the name of the field. -## 对字段重新排序 +## Reordering fields -在表布局中,可以更改字段的顺序。 +In table layout, you can change the order of fields. -1. 单击字段标题。 - ![显示“字段标题”的屏幕截图](/assets/images/help/projects-v2/select-field-header.png) -2. 继续单击时,将字段拖到所需位置。 +1. Click the field header. + ![Screenshot showing the field header](/assets/images/help/projects-v2/select-field-header.png) +2. While continuing to click, drag the field to the required location. -## 对行重新排序 +## Reordering rows -在表布局中,您可以更改行的顺序。 +In table layout, you can change the order of rows. -1. 点击行开头的数字。 - ![显示行号的屏幕截图](/assets/images/help/projects-v2/select-row-number.png) -2. 继续单击时,将行拖到所需位置。 +1. Click the number at the start of the row. + ![Screenshot showing the row number](/assets/images/help/projects-v2/select-row-number.png) +2. While continuing to click, drag the row to the required location. -## 按字段值排序 +## Sorting by field values -在表布局中,您可以按字段值排序项。 +In table layout, you can sort items by a field value. {% note %} -注意:对表格排序时,你不能手动重新排序行。 +**Note:** When a table is sorted, you cannot manually reorder rows. {% endnote %} {% data reusables.projects.open-view-menu %} -1. 单击“排序”。 - ![显示“排序”菜单项的屏幕截图](/assets/images/help/projects-v2/sort-menu-item.png) -1. 选择你希望设为排序依据的字段。 - ![显示“排序”菜单的屏幕截图](/assets/images/help/projects-v2/sort-menu.png) -2. (可选)若要更改排序的方向,请单击 {% octicon "sort-desc" aria-label="the sort icon" %}。 - ![显示“排序顺序”选项的屏幕截图](/assets/images/help/projects-v2/sort-order.png) -3. (可选)若要移除排序,请单击列表底部的 {% octicon "x" aria-label="the x icon" %}“无排序”。 - ![显示“无排序”的屏幕截图](/assets/images/help/projects-v2/no-sorting.png) +1. Click **Sort**. + ![Screenshot showing the sort menu item](/assets/images/help/projects-v2/sort-menu-item.png) +1. Click the field you want to sort by. + ![Screenshot showing the sort menu](/assets/images/help/projects-v2/sort-menu.png) +2. Optionally, to change the direction of the sort, click {% octicon "sort-desc" aria-label="the sort icon" %}. + ![Screenshot showing sort order option](/assets/images/help/projects-v2/sort-order.png) +3. Optionally, to remove a sort, click {% octicon "x" aria-label="the x icon" %} **No sorting** at the bottom of the list. + ![Screenshot showing "no sorting"](/assets/images/help/projects-v2/no-sorting.png) -或者,通过按 {% data variables.projects.command-palette-shortcut %} 打开项目命令面板,然后开始键入“排序依据”。 +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Sort by." -## 在表布局中按字段值分组 +## Grouping by field values in table layout -在表布局中,您可以按自定义字段值排序组项。 对项分组时,如果将项拖动到新组,则应用该组的值。 例如,如果你是按“状态”分组,然后将一个状态为 `In progress` 的项拖动到 `Done` 组,则该项的状态将切换为 `Done`。 同样,当您向组添加新项时,新项将使用组的值填充。 +In the table layout, you can group items by a custom field value. When items are grouped, if you drag an item to a new group, the value of that group is applied. For example, if you group by "Status" and then drag an item with a status of `In progress` to the `Done` group, the status of the item will switch to `Done`. Similarly, when you add a new item to a group, the new item is populated with the value of the group. {% note %} -注意:无法按标题、标签、审查者或链接的拉取请求进行分组。 +**Note:** You cannot group by title, labels, reviewers, or linked pull requests. {% endnote %} {% data reusables.projects.open-view-menu %} -1. 单击 {% octicon "rows" aria-label="the rows icon" %}“组”。 - ![显示“组”菜单项的屏幕截图](/assets/images/help/projects-v2/group-menu-item.png) -1. 单击你希望设为分组依据的字段。 - ![显示“组”菜单的屏幕截图](/assets/images/help/projects-v2/group-menu.png) -2. (可选)若要禁用分组,请单击列表底部的 {% octicon "x" aria-label="the x icon" %}“无分组”。 - ![显示“无分组”的屏幕截图](/assets/images/help/projects-v2/no-grouping.png) +1. Click {% octicon "rows" aria-label="the rows icon" %} **Group**. + ![Screenshot showing the group menu item](/assets/images/help/projects-v2/group-menu-item.png) +1. Click the field you want to group by. + ![Screenshot showing the group menu](/assets/images/help/projects-v2/group-menu.png) +2. Optionally, to disable grouping, click {% octicon "x" aria-label="the x icon" %} **No grouping** at the bottom of the list. + ![Screenshot showing "no grouping"](/assets/images/help/projects-v2/no-grouping.png) -或者,通过按 {% data variables.projects.command-palette-shortcut %} 打开项目命令面板,然后开始键入“分组依据”。 +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Group by." -## 在板布局中设置列字段 +{% ifversion projects-v2-numeric-summary %} -在板布局中,您可以为列选择任何单选或迭代字段。 如果将某个项拖到新列,则该列的值将应用于拖动的项。 例如,如果对板列使用“状态”字段,然后将状态为 `In progress` 的项拖到 `Done` 列,则该项的状态将切换为 `Done`。 +## Showing the sum of a number field + +You can configure a view to show the sum of one of more number fields, including a count of items in the group or column. For example, if you have a number field tracking the number of hours each item may take to complete, you can display of sum of those hours for each group or column. + +In board layout, field sums are displayed at the top of each column. In table layout, when you enable grouping by a field, field sums are included in each group's header. {% data reusables.projects.open-view-menu %} -1. 单击 {% octicon "columns" aria-label="the columns icon" %}“列字段”。 - ![显示“列字段”项的屏幕截图](/assets/images/help/projects-v2/column-field-menu-item.png) -1. 单击你希望使用的字段。 - ![显示“列字段”菜单的屏幕截图](/assets/images/help/projects-v2/column-field-menu.png) +1. Click {% octicon "number" aria-label="the number icon" %} **Field sum**. + + ![Screenshot showing the field sum menu item](/assets/images/help/projects-v2/field-sum-menu.png) + +1. Select the fields you want to include. + + ![Screenshot showing the field sum menu](/assets/images/help/projects-v2/field-sum-select-field.png) + -或者,通过按 {% data variables.projects.command-palette-shortcut %} 打开项目命令面板,然后开始键入“列字段依据”。 +{% endif %} + +## Setting the column field in board layout + +In the board layout, you choose any single select or iteration field for your columns. If you drag an item to a new column, the value of that column is applied to the dragged item. For example, if you use the "Status" field for your board columns and then drag an item with a status of `In progress` to the `Done` column, the status of the item will switch to `Done`. + +{% data reusables.projects.open-view-menu %} +1. Click {% octicon "columns" aria-label="the columns icon" %} **Column field**. + ![Screenshot showing the column field item](/assets/images/help/projects-v2/column-field-menu-item.png) +1. Click the field you want to use. + ![Screenshot showing the column field menu](/assets/images/help/projects-v2/column-field-menu.png) + +Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Column field by." + +{% ifversion projects-v2-column-visibility %} + +## Showing and hiding columns in board layout + +In the board layout, you can can choose which columns to display. The available columns are made up of the contents of your selected column field. + +1. In the board layout, scroll to the right of your columns, and click {% octicon "plus" aria-label="the plus icon" %}. + + ![Screenshot showing the plus symbol button](/assets/images/help/projects-v2/board-add-column.png) + +1. Select the columns you want to show. + + ![Screenshot showing the list of columns](/assets/images/help/projects-v2/board-select-columns.png) + +{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md index 10e17e9937..d427bed2f3 100644 --- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md +++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md @@ -1,10 +1,10 @@ --- -title: '{% data variables.product.prodname_projects_v2 %} 的最佳做法' -intro: 学习管理项目的技巧。 +title: 'Best practices for {% data variables.product.prodname_projects_v2 %}' +intro: 'Learn tips for managing your projects.' allowTitleToDifferFromFilename: true miniTocMaxHeadingLevel: 3 versions: - feature: projects-v2 + feature: "projects-v2" redirect_from: - /issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects type: overview @@ -12,75 +12,72 @@ topics: - Projects - Issues - Project management -ms.openlocfilehash: 71cf84e26bdbed717fd5b434e92f071550764cdc -ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147880034' --- -可使用 {% data variables.product.prodname_projects_v2 %} 来管理你在 {% data variables.product.company_short %} 上的工作,其中包括问题和拉取请求。 阅读提示以便高效和有效地管理您的项目。 有关 {% data variables.product.prodname_projects_v2 %} 的详细信息,请参阅“[关于 {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)”。 -## 将大议题分成较小的议题 +You can use {% data variables.product.prodname_projects_v2 %} to manage your work on {% data variables.product.company_short %}, where your issues and pull requests live. Read on for tips to manage your projects efficiently and effectively. For more information about {% data variables.product.prodname_projects_v2 %}, see "[About {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." -将大议题分解为较小的议题,使工作更加易于管理,并使团队成员能够并行工作。 它还会导致较小的拉取请求,这些请求更容易审查。 +## Break down large issues into smaller issues -要跟踪较小的议题如何融入更大的目标,请使用任务列表、里程碑或标签。 有关详细信息,请参阅“[关于任务列表](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)”、“[关于里程碑](/issues/using-labels-and-milestones-to-track-work/about-milestones)”和“[管理标签](/issues/using-labels-and-milestones-to-track-work/managing-labels)”。 +Breaking a large issue into smaller issues makes the work more manageable and enables team members to work in parallel. It also leads to smaller pull requests, which are easier to review. -## 通信 +To track how smaller issues fit into the larger goal, use task lists, milestones, or labels. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)", "[About milestones](/issues/using-labels-and-milestones-to-track-work/about-milestones)", and "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)." -议题和拉取请求包括内置功能,让您轻松地与协作者沟通。 使用 @mentions 提醒个人或整个团队注意某条评论。 指派议题协作者负责沟通。 链接到相关的议题或拉取请求以沟通它们是如何连接的。 +## Communicate -## 使用描述和 README +Issues and pull requests include built-in features to let you easily communicate with your collaborators. Use @mentions to alert a person or entire team about a comment. Assign collaborators to issues to communicate responsibility. Link to related issues or pull requests to communicate how they are connected. -使用您的项目描述和 README 来分享有关该项目的信息。 +## Make use of the description and README -例如: +Use your project's description and README to share information about the project. -- 解释项目的目的。 -- 描述项目视图及其使用方法。 -- 包括相关链接和要联系的人员以获取更多信息。 +For example: -项目 README 支持 Markdown,它允许您使用图像和高级格式,如链接、列表和标题。 +- Explaining the purpose of the project. +- Describing the project views and how to use them. +- Including relevant links and people to contact for more information. -有关详细信息,请参阅“[创建 {% data variables.projects.project_v2 %}](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project)”。 +Project READMEs support Markdown which allows you to use images and advanced formatting such as links, lists, and headers. -## 使用视图 +For more information, see "[Creating a {% data variables.projects.project_v2 %}](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project)." -使用项目视图从不同角度查看您的项目。 +## Use views -例如: +Use project views to look at your project from different angles. -- 按状态过滤以查看所有未启动的项 -- 按自定义优先级字段分组以监控高优先级项目的数量 -- 按自定义日期字段排序,以查看具有最早目标运输日期的物品 +For example: -有关详细信息,请参阅“[自定义视图](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)”。 +- Filter by status to view all un-started items +- Group by a custom priority field to monitor the volume of high priority items +- Sort by a custom date field to view the items with the earliest target ship date -## 拥有单一真相来源 +For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)." -为了防止信息不同步,请保持单一真相来源。 例如,在一个位置跟踪目标运输日期,而不是分布于多个字段。 然后,如果目标运输日期发生变化,您只需要在一个位置更新日期。 +## Have a single source of truth -{% data variables.product.prodname_projects_v2 %} 自动更新 {% data variables.product.company_short %} 数据,例如代理人、里程碑和标签。 当其中一个字段在议题或拉取请求中发生变化时,更改会自动反映在您的项目中。 +To prevent information from getting out of sync, maintain a single source of truth. For example, track a target ship date in a single location instead of spread across multiple fields. Then, if the target ship date shifts, you only need to update the date in one location. -## 使用自动化 +{% data variables.product.prodname_projects_v2 %} automatically stay up to date with {% data variables.product.company_short %} data, such as assignees, milestones, and labels. When one of these fields changes in an issue or pull request, the change is automatically reflected in your project. -您可以自动执行任务,以减少您在繁琐工作上花费的时间,将更多的时间用于项目本身。 需要手动操作的越少,项目就越有可能保持最新状态。 +## Use automation -{% data variables.product.prodname_projects_v2 %} 提供内置工作流。 例如,当议题关闭时,您可以自动将状态设置为“完成”。 +You can automate tasks to spend less time on busy work and more time on the project itself. The less you need to remember to do manually, the more likely your project will stay up to date. -此外,{% data variables.product.prodname_actions %} 和 GraphQL API 还可让您实现例行项目管理任务自动化。 例如,要跟踪等待审查的拉取请求,您可以创建一个工作流程,将拉取请求添加到项目并将状态设置为“需要审核”;当拉取请求标记为“准备审核”时,可以自动触发此过程。 +{% data variables.product.prodname_projects_v2 %} offers built-in workflows. For example, when an issue is closed, you can automatically set the status to "Done." {% ifversion projects-v2-auto-archive %}You can also configure built-in workflows to automatically archive items when they meet certain criteria.{% endif %} -- 有关示例工作流,请参阅“[使用 Actions 自动执行 {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions)”。 -- 有关 API 的详细信息,请参阅“[使用 API 管理 {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)”。 -- 有关 {% data variables.product.prodname_actions %} 的详细信息,请参阅 [“{% data variables.product.prodname_actions %}](/actions)”。 +Additionally, {% data variables.product.prodname_actions %} and the GraphQL API enable you to automate routine project management tasks. For example, to keep track of pull requests awaiting review, you can create a workflow that adds a pull request to a project and sets the status to "needs review"; this process can be automatically triggered when a pull request is marked as "ready for review." -## 使用不同的字段类型 +- For more information about the built-in workflows, see "[Using the built-in automations](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations)."{% ifversion projects-v2-auto-archive %} +- For more information about automatically archiving items, see "[Archiving items automatically](/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically)."{% endif %} +- For an example workflow, see "[Automating {% data variables.product.prodname_projects_v2 %} using Actions](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions)." +- For more information about the API, see "[Using the API to manage {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)." +- For more information about {% data variables.product.prodname_actions %}, see ["{% data variables.product.prodname_actions %}](/actions)." -利用各种字段类型来满足您的需求。 +## Use different field types -使用迭代字段可以安排工作或创建日程表。 您可以按迭代进行分组以查看项目在迭代之间是否平衡,也可以进行筛选以专注于单个迭代。 迭代字段还允许您查看在过去迭代中完成的工作,这有助于快速规划和反映团队的成就。 迭代字段还支持休息,以显示您和您的团队何时从迭代中抽出时间。 有关详细信息,请参阅“[关于迭代字段](/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields)”。 +Take advantage of the various field types to meet your needs. -使用单选字段可以根据预设的值列表跟踪有关任务的信息。 例如,跟踪优先级或项目阶段。 由于这些值是从预设列表中选择的,因此您可以轻松地对值进行分组或筛选,以将焦点放在具有特定值的项目上。 +Use an iteration field to schedule work or create a timeline. You can group by iteration to see if items are balanced between iterations, or you can filter to focus on a single iteration. Iteration fields also let you view work that you completed in past iterations, which can help with velocity planning and reflecting on your team's accomplishments. Iteration fields also support breaks to show when you and your team are taking time away from their iterations. For more information, see "[About iteration fields](/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields)." -有关不同字段类型的详细信息,请参阅“[了解字段类型](/issues/planning-and-tracking-with-projects/understanding-field-types)”。 +Use a single select field to track information about a task based on a preset list of values. For example, track priority or project phase. Since the values are selected from a preset list, you can easily group or filter to focus on items with a specific value. + +For more information about the different field types, see "[Understanding field types](/issues/planning-and-tracking-with-projects/understanding-field-types)." diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md index 337ff5ff01..7fc55bb88e 100644 --- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md +++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md @@ -1,90 +1,86 @@ --- -title: '将项添加到你的 {% data variables.projects.project_v2 %}' -shortTitle: Adding items -intro: 了解如何将拉取请求、问题和草稿问题单独或批量添加到你的项目中。 +title: 'Adding items to your {% data variables.projects.project_v2 %}' +shortTitle: 'Adding items' +intro: 'Learn how to add pull requests, issues, and draft issues to your projects individually or in bulk.' miniTocMaxHeadingLevel: 4 versions: - feature: projects-v2 + feature: "projects-v2" type: tutorial topics: - Projects allowTitleToDifferFromFilename: true -ms.openlocfilehash: e49758bbf751ddd1cced46719f9740147a1b7b32 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147423792' --- -您的项目可以跟踪草稿议题、议题和拉取请求。 + +Your project can track draft issues, issues, and pull requests. {% note %} -注意:项目最多可以包含 1,200 个项和 10,000 个存档项。 +**Note:** A project can contain a maximum of {% data variables.projects.item_limit %} items and {% data variables.projects.archived_item_limit %} archived items. {% ifversion projects-v2-auto-archive %}To learn more about automatically archiving items when they meet specific criteria, see "[Archiving items automatically](/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically)."{% endif %} {% endnote %} -### 将问题和拉取请求添加到项目 +### Adding issues and pull requests to a project -#### 粘贴问题或拉取请求的 URL +#### Pasting the URL of an issue or pull request {% data reusables.projects.add-item-via-paste %} -#### 搜索议题或拉取请求 +#### Searching for an issue or pull request {% data reusables.projects.add-item-bottom-row %} -2. 输入 # 。 -3. 选择拉取请求或议题所在的仓库。 您可以输入仓库名称的一部分来缩小选项范围。 - ![显示粘贴问题 URL 以将其添加到项目的屏幕截图](/assets/images/help/projects-v2/add-item-select-repo.png) -4. 选择议题或拉取请求。 您可以键入标题的一部分以缩小选项范围。 - ![显示粘贴问题 URL 以将其添加到项目的屏幕截图](/assets/images/help/projects-v2/add-item-select-issue.png) +2. Enter #. +3. Select the repository where the pull request or issue is located. You can type part of the repository name to narrow down your options. + ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/add-item-select-repo.png) +4. Select the issue or pull request. You can type part of the title to narrow down your options. + ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/add-item-select-issue.png) -#### 批量添加问题和拉取请求 +#### Bulk adding issues and pull requests -1. 在项目的最后一行,单击 {% octicon "plus" aria-label="plus icon" %}。 - ![显示项目底部 + 按钮的屏幕截图](/assets/images/help/projects-v2/omnibar-add.png) -1. 单击“从存储库添加项”。 - ![显示“从存储库添加项”菜单项的屏幕截图](/assets/images/help/projects-v2/add-bulk-menu-item.png) {% data reusables.projects.bulk-add %} - -#### 从存储库添加多个问题或拉取请求 - -1. 在 {% data variables.product.product_location %} 上,导航到包含要添加到项目中的问题或拉取请求的存储库。 -{% data reusables.repositories.sidebar-issue-pr %} -1. 在每个问题标题的左侧,选择要添加到项目中的问题。 - ![显示用于选择问题或拉取请求的复选框的屏幕截图](/assets/images/help/issues/select-issue-checkbox.png) -1. (可选)若要选择页面上的每个问题或拉取请求,请在问题或拉取请求列表的顶部选择全选。 - ![显示用于在屏幕上全选的复选框的屏幕截图](/assets/images/help/issues/select-all-checkbox.png) -1. 在问题列表或拉取请求的上方,单击“项目”。 - ![显示“项目”选项的屏幕截图](/assets/images/help/projects-v2/issue-index-project-menu.png) -1. 单击要向其添加所选问题或拉取请求的项目。 - ![显示用于在屏幕上全选的复选框的屏幕截图](/assets/images/help/projects-v2/issue-index-select-project.png) - -#### 从议题或拉取请求中分配项目 - -1. 导航到要添加到项目的议题或拉取请求。 -2. 在侧栏中,单击“项目”。 - ![显示问题侧边栏中“项目”的屏幕截图](/assets/images/help/projects-v2/issue-sidebar-projects.png) -3. 选择要添加议题或拉取请求的项目。 - ![显示从问题侧边栏选择项目的屏幕截图](/assets/images/help/projects-v2/issue-sidebar-select-project.png) -4. (可选)填充自定义字段。 - ![项目侧边栏](/assets/images/help/projects-v2/issue-edit-project-sidebar.png) - -#### 使用命令面板添加问题或拉取请求 - -1. {% data reusables.projects.open-command-palette %} -1. 开始键入“添加项”,然后按 Return。 +1. In the bottom row of the project, click {% octicon "plus" aria-label="plus icon" %}. + ![Screenshot showing + button at the bottom of the project](/assets/images/help/projects-v2/omnibar-add.png) +1. Click **Add item from repository**. + ![Screenshot showing "add item from repository" menu item](/assets/images/help/projects-v2/add-bulk-menu-item.png) {% data reusables.projects.bulk-add %} -### 创建草稿议题 +#### Adding multiple issues or pull requests from a repository -草稿议题有助于快速捕获想法。 与从存储库引用的问题和拉取请求不同,草稿问题只存在于你的项目中。 +1. On {% data variables.location.product_location %}, navigate to the repository that contains the issues or pull requests you want to add to your project. +{% data reusables.repositories.sidebar-issue-pr %} +1. To the left of each issue title, select the issues that you want to add to your project. + ![Screenshot showing checkbox to select issue or pull request](/assets/images/help/issues/select-issue-checkbox.png) +1. Optionally, to select every issue or pull request on the page, at the top of the list of issues or pull requests, select all. + ![Screenshot showing checkbox to select all on screen](/assets/images/help/issues/select-all-checkbox.png) +1. Above the list of issues or pull requests, click **Projects**. + ![Screenshot showing projects option](/assets/images/help/projects-v2/issue-index-project-menu.png) +1. Click the projects you want to add the selected issues or pull requests to. + ![Screenshot showing checkbox to select all on screen](/assets/images/help/projects-v2/issue-index-select-project.png) + +#### Assigning a project from within an issue or pull request + +1. Navigate to the issue or pull request that you want to add to a project. +2. In the side bar, click **Projects**. + ![Screenshot showing "Projects" in the issue sidebar](/assets/images/help/projects-v2/issue-sidebar-projects.png) +3. Select the project that you want to add the issue or pull request to. + ![Screenshot showing selecting a project from the issue sidebar](/assets/images/help/projects-v2/issue-sidebar-select-project.png) +4. Optionally, populate the custom fields. + ![Project sidebar](/assets/images/help/projects-v2/issue-edit-project-sidebar.png) + +#### Using the command palette to add an issue or pull request + +1. {% data reusables.projects.open-command-palette %} +1. Start typing "Add items" and press Return. +{% data reusables.projects.bulk-add %} + +### Creating draft issues + +Draft issues are useful to quickly capture ideas. Unlike issues and pull requests that are referenced from your repositories, draft issues exist only in your project. {% data reusables.projects.add-draft-issue %} -草稿议题可以具有标题、文本正文、受理人以及项目中的任何自定义字段。 为了填充草稿议题的存储库、标签或里程碑,必须首先将草稿问题转换为议题。 有关详细信息,请参阅“[将草稿问题转换为问题](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues)”。 +Draft issues can have a title, text body, assignees, and any custom fields from your project. In order to populate the repository, labels, or milestones for a draft issue, you must first convert the draft issue to an issue. For more information, see "[Converting draft issues to issues](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues)." {% note %} -注意:用户在草稿问题中被分配或提及时不会收到通知,除非草稿问题已转换为问题。 +**Note**: Users will not receive notifications when they are assigned to or mentioned in a draft issue unless the draft issue is converted to an issue. -{% endnote %} +{% endnote %} \ No newline at end of file diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md index d957ea5a00..d49c64ef7c 100644 --- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md +++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md @@ -1,51 +1,48 @@ --- -title: '存档 {% data variables.projects.project_v2 %} 中的项' -shortTitle: Archiving items -intro: 可以存档项,使其可用于还原,或永久删除。 +title: 'Archiving items from your {% data variables.projects.project_v2 %}' +shortTitle: 'Archiving items' +intro: 'You can archive items, keeping them available to restore, or permanently delete them.' miniTocMaxHeadingLevel: 2 versions: - feature: projects-v2 + feature: "projects-v2" type: tutorial topics: - Projects allowTitleToDifferFromFilename: true -ms.openlocfilehash: fb9ea68e00cf968affad5f127c5d8723179e9782 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147423807' --- -## 存档项 -您可以对项存档以保留项目中有关该项的上下文,但将其从项目视图中移除。 +## Archiving items -{% data reusables.projects.select-an-item %} {% data reusables.projects.open-item-menu %} -1. 单击“存档”。 - ![显示“存档”选项的屏幕截图](/assets/images/help/projects-v2/archive-menu-item.png) -1. 出现提示时,单击“存档”确认选择。 - ![显示存档提示的屏幕截图](/assets/images/help/projects-v2/archive-item-prompt.png) +You can archive an item to keep the context about the item in the project but remove it from the project views. {% ifversion projects-v2-auto-archive %}You can also configure your project's built-in workflows to automatically archive items that meet certain criteria. For more information, see "[Archiving items automatically](/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically)."{% endif %} -## 恢复存档的项 +{% data reusables.projects.select-an-item %} +{% data reusables.projects.open-item-menu %} +1. Click **Archive**. + ![Screenshot showing archive option](/assets/images/help/projects-v2/archive-menu-item.png) +1. When prompted, confirm your choice by clicking **Archive**. + ![Screenshot showing archive prompt](/assets/images/help/projects-v2/archive-item-prompt.png) -1. 导航到你的项目。 -1. 在右上角,单击 {% octicon "kebab-horizontal" aria-label="The menu icon" %} 以打开菜单。 - ![显示菜单图标的屏幕截图](/assets/images/help/projects-v2/open-menu.png) -1. 在菜单中,单击 {% octicon "archive" aria-label="The archive icon" %}“已存档项”。 - ![显示“已存档项”菜单项的屏幕截图](/assets/images/help/projects-v2/archived-items-menu-item.png) -1. (可选)若要筛选显示的已存档项,请在项列表上方的文本框中键入筛选器。 有关可用筛选器的详细信息,请参阅“[筛选项目](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)”。 - ![显示用于筛选已存档项的字段的屏幕截图](/assets/images/help/issues/filter-archived-items.png) -1. 在每个项标题的左侧,选择要还原的项。 - ![显示已存档项旁边的复选框的屏幕截图](/assets/images/help/issues/select-archived-item.png) -1. 若要还原所选的项,请单击项列表上方的“还原”。 - ![显示“还原”按钮的屏幕截图](/assets/images/help/issues/restore-archived-item-button.png) +## Restoring archived items -## 删除项 +1. Navigate to your project. +1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. + ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png) +1. In the menu, click {% octicon "archive" aria-label="The archive icon" %} **Archived items**. + ![Screenshot showing the 'Archived items' menu item](/assets/images/help/projects-v2/archived-items-menu-item.png) +1. Optionally, to filter the archived items displayed, type your filter into the text box above the list of items. For more information about the available filters, see "[Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)." + ![Screenshot showing field for filtering archived items](/assets/images/help/issues/filter-archived-items.png) +1. To the left of each item title, select the items you would like to restore. + ![Screenshot showing checkboxes next to archived items](/assets/images/help/issues/select-archived-item.png) +1. To restore the selected items, above the list of items, click **Restore**. + ![Screenshot showing the "Restore" button](/assets/images/help/issues/restore-archived-item-button.png) -您可以删除某个项以将其从项目中完全移除。 +## Deleting items -{% data reusables.projects.select-an-item %} {% data reusables.projects.open-item-menu %} -1. 单击“从项目中删除”。 - ![显示“删除”选项的屏幕截图](/assets/images/help/projects-v2/delete-menu-item.png) -1. 出现提示时,单击“删除”确认选择。 - ![显示删除提示的屏幕截图](/assets/images/help/projects-v2/delete-item-prompt.png) +You can delete an item to remove it from the project entirely. + +{% data reusables.projects.select-an-item %} +{% data reusables.projects.open-item-menu %} +1. Click **Delete from project**. + ![Screenshot showing delete option](/assets/images/help/projects-v2/delete-menu-item.png) +1. When prompted, confirm your choice by clicking **Delete**. + ![Screenshot showing delete prompt](/assets/images/help/projects-v2/delete-item-prompt.png) \ No newline at end of file diff --git a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md index ed054d2081..02f702fa56 100644 --- a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md +++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md @@ -1,6 +1,6 @@ --- -title: 关于组织的消息馈送 -intro: 您可以使用组织的消息馈送跟进该组织拥有的仓库上的近期活动。 +title: About your organization’s news feed +intro: You can use your organization's news feed to keep up with recent activity on repositories owned by that organization. redirect_from: - /articles/news-feed - /articles/about-your-organization-s-news-feed @@ -15,19 +15,16 @@ topics: - Organizations - Teams shortTitle: Organization news feed -ms.openlocfilehash: 2ef8e11cd2ede1fedd284aed3d554bcd658d413e -ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145128604' --- -组织的消息馈送显示其他人在该组织拥有的仓库上的活动。 您可以使用组织的消息馈送来查看何时有人打开、关闭或合并议题或拉取请求,创建或删除分支,创建标记或发行版,评论议题,拉取请求,或者提交或推送提交到 {% data variables.product.product_name %}。 -## 访问组织的消息馈送 +An organization's news feed shows other people's activity on repositories owned by that organization. You can use your organization's news feed to see when someone opens, closes, or merges an issue or pull request, creates or deletes a branch, creates a tag or release, comments on an issue, pull request, or commit, or pushes new commits to {% data variables.product.product_name %}. -1. {% data variables.product.signin_link %} 到 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的帐户。 -2. 打开 {% data reusables.user-settings.personal_dashboard %}。 -3. 单击页面左上角的帐户上下文切换器。 - ![Enterprise 中的上下文切换器按钮](/assets/images/help/organizations/account_context_switcher.png) -4. 从下拉菜单中选择组织。{% ifversion fpt or ghec %} ![dotcom 中的上下文切换器菜单](/assets/images/help/organizations/account-context-switcher-selected-dotcom.png){% else %} ![Enterprise 中的上下文切换器菜单](/assets/images/help/organizations/account_context_switcher.png){% endif %} +## Accessing your organization's news feed + +1. {% data variables.product.signin_link %} to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. +2. Open your {% data reusables.user-settings.personal_dashboard %}. +3. Click the account context switcher in the upper-left corner of the page. + ![Context switcher button in Enterprise](/assets/images/help/organizations/account_context_switcher.png) +4. Select an organization from the drop-down menu.{% ifversion fpt or ghec %} + ![Context switcher menu in dotcom](/assets/images/help/organizations/account-context-switcher-selected-dotcom.png){% else %} + ![Context switcher menu in Enterprise](/assets/images/help/organizations/account_context_switcher.png){% endif %} diff --git a/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md index 7d2a18d519..adb9d914e2 100644 --- a/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md +++ b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- -title: 关于双重身份验证和 SAML 单点登录 -intro: 组织管理员可启用 SAML 单点登录及双重身份验证,为其组织成员增加额外的身份验证措施。 +title: About two-factor authentication and SAML single sign-on +intro: Organizations administrators can enable both SAML single sign-on and two-factor authentication to add additional authentication measures for their organization members. redirect_from: - /articles/about-two-factor-authentication-and-saml-single-sign-on - /github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on @@ -10,22 +10,17 @@ topics: - Organizations - Teams shortTitle: 2FA & SAML single sign-on -ms.openlocfilehash: 1dc8eff35906a5f2c59f097d3bf53482547bd1f5 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145127540' --- -双重身份验证 (2FA) 为组织成员提供基本验证。 通过启用 2FA,组织管理员可降低 {% data variables.product.product_location %} 上成员的帐户被盗的可能性。 有关 2FA 的详细信息,请参阅“[关于双重身份验证](/articles/about-two-factor-authentication)”。 -若要添加其他身份验证措施,组织管理员也可以[启用 SAML 单一登录 (SSO)](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization),组织成员必须使用单一登录才能访问组织。 有关 SAML SSO 的详细信息,请参阅“[关于使用 SAML 单一登录进行标识和访问管理](/articles/about-identity-and-access-management-with-saml-single-sign-on)”。 +Two-factor authentication (2FA) provides basic authentication for organization members. By enabling 2FA, organization administrators limit the likelihood that a member's account on {% data variables.location.product_location %} could be compromised. For more information on 2FA, see "[About two-factor authentication](/articles/about-two-factor-authentication)." -如果同时启用了 2FA 和 SAML SSO,组织成员必须执行以下操作: -- 使用 2FA 登录其在 {% data variables.product.product_location %} 上的帐户 -- 使用单点登录访问组织 -- 使用授权用于 API 或 Git 访问的令牌,并使用单点登录授权令牌 +To add additional authentication measures, organization administrators can also [enable SAML single sign-on (SSO)](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) so that organization members must use single sign-on to access an organization. For more information on SAML SSO, see "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)." -## 延伸阅读 +If both 2FA and SAML SSO are enabled, organization members must do the following: +- Use 2FA to log in to their account on {% data variables.location.product_location %} +- Use single sign-on to access the organization +- Use an authorized token for API or Git access and use single sign-on to authorize the token -- [为组织强制执行 SAML 单一登录](/articles/enforcing-saml-single-sign-on-for-your-organization) +## Further reading + +- "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" diff --git a/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md index 6e7ffd78b2..979337cd31 100644 --- a/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -1,6 +1,6 @@ --- -title: 查看和管理成员 SAML 对组织的访问权限 -intro: 您可以查看和撤销组织成员的链接身份、活动会话和授权凭据。 +title: Viewing and managing a member's SAML access to your organization +intro: 'You can view and revoke an organization member''s linked identity, active sessions, and authorized credentials.' permissions: Organization owners can view and manage a member's SAML access to an organization. redirect_from: - /articles/viewing-and-revoking-organization-members-authorized-access-tokens @@ -12,50 +12,65 @@ topics: - Organizations - Teams shortTitle: Manage SAML access -ms.openlocfilehash: 5b8dbe15037eabe416a6b0c63df7f893db8445bb -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145127536' --- -## 关于对组织的 SAML 访问 -对组织启用 SAML 单点登录时,每个组织成员都可以将其在身份提供程序 (IdP) 上的外部身份链接到其在 {% data variables.product.product_location %} 上的现有帐户。 要在 {% data variables.product.product_name %} 上访问组织的资源,成员必须在其浏览器中启动 SAML 会话。 要使用 API 或 Git 访问组织的资源,成员必须使用被授权用于组织的个人访问令牌或 SSH 密钥。 +## About SAML access to your organization -您可以在同一页面上查看和撤销每个成员的链接身份、活动会话和授权凭据。 +When you enable SAML single sign-on for your organization, each organization member can link their external identity on your identity provider (IdP) to their existing account on {% data variables.location.product_location %}. To access your organization's resources on {% data variables.product.product_name %}, the member must have an active SAML session in their browser. To access your organization's resources using the API or Git, the member must use a {% data variables.product.pat_generic %} or SSH key that the member has authorized for use with your organization. -## 查看和撤销链接的身份 +You can view and revoke each member's linked identity, active sessions, and authorized credentials on the same page. + +## Viewing and revoking a linked identity {% data reusables.saml.about-linked-identities %} -如果可用,该条目将包含 SCIM 数据。 有关详细信息,请参阅“[关于组织的 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)”。 +When available, the entry will include SCIM data. For more information, see "[About SCIM for organizations](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)." {% warning %} -警告:对于使用 SCIM 的组织: -- 撤销 {% data variables.product.product_name %} 上链接的用户身份也会删除 SAML 和 SCIM 元数据。 因此,身份提供商无法同步或解除预配已链接的用户身份。 -- 管理员必须通过身份提供商撤销链接的身份。 -- 要撤销链接的身份并通过身份提供商链接其他帐户,管理员可以删除用户并重新分配给 {% data variables.product.product_name %} 应用程序。 更多信息请参阅身份提供商的文档。 +**Warning:** For organizations using SCIM: +- Revoking a linked user identity on {% data variables.product.product_name %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity. +- An admin must revoke a linked identity through the identity provider. +- To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.product_name %} application. For more information, see your identity provider's documentation. {% endwarning %} {% data reusables.identity-and-permissions.revoking-identity-team-sync %} -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %} {% data reusables.saml.click-person-revoke-identity %} {% data reusables.saml.saml-identity-linked %} {% data reusables.saml.view-sso-identity %} {% data reusables.saml.revoke-sso-identity %} {% data reusables.saml.confirm-revoke-identity %} +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.people %} +{% data reusables.saml.click-person-revoke-identity %} +{% data reusables.saml.saml-identity-linked %} +{% data reusables.saml.view-sso-identity %} +{% data reusables.saml.revoke-sso-identity %} +{% data reusables.saml.confirm-revoke-identity %} -## 查看和撤销活动的 SAML 会话 +## Viewing and revoking an active SAML session -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %} {% data reusables.saml.click-person-revoke-session %} {% data reusables.saml.saml-identity-linked %} {% data reusables.saml.view-saml-sessions %} {% data reusables.saml.revoke-saml-session %} +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.people %} +{% data reusables.saml.click-person-revoke-session %} +{% data reusables.saml.saml-identity-linked %} +{% data reusables.saml.view-saml-sessions %} +{% data reusables.saml.revoke-saml-session %} -## 查看和撤销授权的凭据 +## Viewing and revoking authorized credentials {% data reusables.saml.about-authorized-credentials %} -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %} {% data reusables.saml.click-person-revoke-credentials %} {% data reusables.saml.saml-identity-linked %} {% data reusables.saml.view-authorized-credentials %} {% data reusables.saml.revoke-authorized-credentials %} {% data reusables.saml.confirm-revoke-credentials %} +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.people %} +{% data reusables.saml.click-person-revoke-credentials %} +{% data reusables.saml.saml-identity-linked %} +{% data reusables.saml.view-authorized-credentials %} +{% data reusables.saml.revoke-authorized-credentials %} +{% data reusables.saml.confirm-revoke-credentials %} -## 延伸阅读 +## Further reading -- [关于使用 SAML 单一登录进行的标识和访问管理](/articles/about-identity-and-access-management-with-saml-single-sign-on){% ifversion ghec %} -- [查看和管理用户对企业帐户的 SAML 访问](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise){% endif %} +- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"{% ifversion ghec %} +- "[Viewing and managing a user's SAML access to your enterprise account](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)"{% endif %} diff --git a/translations/zh-CN/content/organizations/index.md b/translations/zh-CN/content/organizations/index.md index b737de3487..c323cfcf4f 100644 --- a/translations/zh-CN/content/organizations/index.md +++ b/translations/zh-CN/content/organizations/index.md @@ -39,11 +39,11 @@ children: - /managing-peoples-access-to-your-organization-with-roles - /organizing-members-into-teams - /collaborating-with-your-team - - /managing-access-to-your-organizations-repositories + - /managing-user-access-to-your-organizations-repositories - /managing-access-to-your-organizations-project-boards - - /managing-access-to-your-organizations-apps + - /managing-programmatic-access-to-your-organization - /managing-organization-settings - - /restricting-access-to-your-organizations-data + - /managing-oauth-access-to-your-organizations-data - /keeping-your-organization-secure - /managing-saml-single-sign-on-for-your-organization - /granting-access-to-your-organization-with-saml-single-sign-on diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md index 2ea8fe2181..83821a82fd 100644 --- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md +++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md @@ -16,7 +16,6 @@ children: - /restricting-email-notifications-for-your-organization - /reviewing-the-audit-log-for-your-organization - /accessing-compliance-reports-for-your-organization - - /reviewing-your-organizations-installed-integrations ms.openlocfilehash: f3170c9636a6d298ba1faad74018a7f8798215d3 ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d ms.translationtype: HT diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md index b63a8babc9..1bdf328430 100644 --- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md +++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md @@ -39,6 +39,7 @@ To search for specific events, use the `action` qualifier in your query. Actions |------------------|-------------------{% ifversion fpt or ghec %} | [`account`](#account-category-actions) | Contains all activities related to your organization account. | [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." +| [`auto_approve_personal_access_token_requests`](#auto_approve_personal_access_token_requests-category-actions) | Contains activities related to your organization's approval policy for {% data variables.product.pat_v2 %}s. For more information, see "[Setting a {% data variables.product.pat_generic %} policy for your organization](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization)." | [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing. | [`business`](#business-category-actions) | Contains activities related to business settings for an enterprise. | | [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae %} @@ -63,10 +64,11 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`org`](#org-category-actions) | Contains activities related to organization membership.{% ifversion ghec %} | [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %} | [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions) | Contains organization-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %} -| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization. +| [`organization_default_label`](#organization_default_label-category-actions) | Contains all activities related to default labels for repositories in your organization. | [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps. | [`packages`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% ifversion fpt or ghec %} | [`payment_method`](#payment_method-category-actions) | Contains all activities related to how your organization pays for GitHub.{% endif %} +| [`personal_access_token`](#personal_access_token-category-actions) | Contains activities related to {% data variables.product.pat_v2 %}s in your organization. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." | [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your organization's profile picture. | [`project`](#project-category-actions) | Contains all activities related to project boards. | [`protected_branch`](#protected_branch-category-actions) | Contains all activities related to protected branches. @@ -209,6 +211,17 @@ An overview of some of the most common actions that are recorded as events in th | `destroy` | Triggered when the administrator of a security advisory removes someone from the credit section. {% endif %} +{% ifversion pat-v2 %} + +### `auto_approve_personal_access_token_requests` category actions + +| Action | Description +|------------------|------------------- +| `disable` | Triggered when the organization must approve {% data variables.product.pat_v2 %}s before the tokens can access organization resources. For more information, see "[Setting a {% data variables.product.pat_generic %} policy for your organization](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization)." +| `enable` | Triggered when {% data variables.product.pat_v2 %}s can access organization resources without prior approval. For more information, see "[Setting a {% data variables.product.pat_generic %} policy for your organization](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization)." + +{% endif %} + {% ifversion fpt or ghec %} ### `billing` category actions @@ -442,6 +455,16 @@ For more information, see "[Managing the publication of {% data variables.produc {% endif %} +### `oauth_application` category actions + +| Action | Description +|------------------|------------------- +| `create` | Triggered when a new {% data variables.product.prodname_oauth_app %} is created. +| `destroy` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is deleted. +| `reset_secret` | Triggered when an {% data variables.product.prodname_oauth_app %}'s client secret is reset. +| `revoke_tokens` | Triggered when an {% data variables.product.prodname_oauth_app %}'s user tokens are revoked. +| `transfer` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is transferred to a new organization. + ### `org` category actions | Action | Description @@ -478,9 +501,15 @@ For more information, see "[Managing the publication of {% data variables.produc | `runner_group_updated` | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." | `runner_group_runners_added` | Triggered when a self-hosted runner is added to a group. For more information, see [Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). | `runner_group_runner_removed` | Triggered when the REST API is used to remove a self-hosted runner from a group. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)." -| `runner_group_runners_updated`| Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."{% ifversion secret-scanning-audit-log-custom-patterns %} +| `runner_group_runners_updated`| Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)." +{%- ifversion code-security-audit-log-events %} +| `secret_scanning_push_protection_custom_message_disabled` | Triggered when an organization owner or admin disables the custom message triggered by an attempted push to a push-protected repository. For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#enabling-secret-scanning-as-a-push-protection-for-an-organization)." +| `secret_scanning_push_protection_custom_message_enabled` | Triggered when an organization owner or admin enables the custom message triggered by an attempted push to a push-protected repository. For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#enabling-secret-scanning-as-a-push-protection-for-an-organization)." +| `secret_scanning_push_protection_custom_message_updated` | Triggered when an organization owner or admin updates the custom message triggered by an attempted push to a push-protected repository. For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#enabling-secret-scanning-as-a-push-protection-for-an-organization)." +{%- endif %} +{%- ifversion secret-scanning-audit-log-custom-patterns %} | `secret_scanning_push_protection_disable ` | Triggered when an organization owner or person with admin access to the organization disables push protection for secret scanning. For more information, see "[Protecting pushes with secret scanning](/enterprise-cloud@latest/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." -| `secret_scanning_push_protection_enable ` | Triggered when an organization owner or person with admin access to the organization enables push protection for secret scanning.{% endif %} +| `secret_scanning_push_protection_enable ` | Triggered when an organization owner or person with admin access to the organization enables push protection for {% data variables.product.prodname_secret_scanning %}.{%- endif %} | `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% ifversion fpt or ghes or ghec %} | `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %}{% ifversion fpt or ghec %} @@ -516,7 +545,7 @@ For more information, see "[Managing the publication of {% data variables.produc | `delete` | Triggered when a custom pattern is removed from secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)." {% endif %} -### `organization_label` category actions +### `organization_default_label` category actions | Action | Description |------------------|------------------- @@ -524,16 +553,6 @@ For more information, see "[Managing the publication of {% data variables.produc | `update` | Triggered when a default label is edited. | `destroy` | Triggered when a default label is deleted. -### `oauth_application` category actions - -| Action | Description -|------------------|------------------- -| `create` | Triggered when a new {% data variables.product.prodname_oauth_app %} is created. -| `destroy` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is deleted. -| `reset_secret` | Triggered when an {% data variables.product.prodname_oauth_app %}'s client secret is reset. -| `revoke_tokens` | Triggered when an {% data variables.product.prodname_oauth_app %}'s user tokens are revoked. -| `transfer` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is transferred to a new organization. - ### `packages` category actions | Action | Description | @@ -555,6 +574,20 @@ For more information, see "[Managing the publication of {% data variables.produc {% endif %} +{% ifversion pat-v2 %} + +### `personal_access_token` category actions + +| Action | Description +|------------------|------------------- +| `access_granted` | Triggered when a {% data variables.product.pat_v2 %} is granted access to organization resources. For more information, see "[Managing requests for {% data variables.product.pat_generic %} in your organization](/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization)." +| `access_revoked` | Triggered when access to organization resources by a {% data variables.product.pat_v2 %} is revoked. The token can still read public organization resources. For more information, see "[Reviewing and revoking {% data variables.product.pat_generic %} in your organization](/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization)." +| `request_cancelled` | Triggered when a member of the organization cancels a request for their {% data variables.product.pat_v2 %} to access organization resources. +| `request_created` | Triggered when a member of the organization creates a {% data variables.product.pat_v2 %} to access organization resources and the organization requires approval before a {% data variables.product.pat_v2 %} can access organization resources. For more information, see "[Managing requests for {% data variables.product.pat_generic %} in your organization](/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization)." +| `request_denied` | Triggered when a request for a {% data variables.product.pat_v2 %} to access organization resources is denied. For more information, see "[Managing requests for {% data variables.product.pat_generic %} in your organization](/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization)." + +{% endif %} + ### `profile_picture` category actions | Action | Description |------------------|------------------- diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md deleted file mode 100644 index a9be5867bc..0000000000 --- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Reviewing your organization's installed integrations -intro: You can review the permission levels for your organization's installed integrations and configure each integration's access to organization repositories. -redirect_from: - - /articles/reviewing-your-organization-s-installed-integrations - - /articles/reviewing-your-organizations-installed-integrations - - /github/setting-up-and-managing-organizations-and-teams/reviewing-your-organizations-installed-integrations - - /organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Review installed integrations ---- - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} -1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-label="The apps icon" %} {% data variables.product.prodname_github_apps %}**. -{% else %} -1. In the left sidebar, click **Installed {% data variables.product.prodname_github_apps %}**. - ![Installed {% data variables.product.prodname_github_apps %} tab in the organization settings sidebar](/assets/images/help/organizations/org-settings-installed-github-apps.png) -{% endif %} -2. Next to the {% data variables.product.prodname_github_app %} you'd like to review, click **Configure**. - ![Configure button](/assets/images/help/organizations/configure-installed-integration-button.png) -6. Review the {% data variables.product.prodname_github_app %}'s permissions and repository access. - ![Option to give the {% data variables.product.prodname_github_app %} access to all repositories or specific repositories](/assets/images/help/organizations/toggle-integration-repo-access.png) - - To give the {% data variables.product.prodname_github_app %} access to all of your organization's repositories, select **All repositories**. - - To choose specific repositories to give the application access to, select **Only select repositories**, then type a repository name. -7. Click **Save**. diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md deleted file mode 100644 index f2aa4e4512..0000000000 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: 为组织添加 GitHub 应用程序管理员 -intro: '组织所有者可授权用户管理组织拥有的某些或所有 {% data variables.product.prodname_github_apps %}。' -redirect_from: - - /articles/adding-github-app-managers-in-your-organization - - /github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Add GitHub App managers -ms.openlocfilehash: d8389c85c847b750bdb83eb8b922ad16bfa33bf3 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145127503' ---- -有关 {% data variables.product.prodname_github_app %} 管理员权限的详细信息,请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#github-app-managers)”。 - -## 授权某人管理组织拥有的所有 {% data variables.product.prodname_github_apps %} - -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.github-apps-settings-sidebar %} -1. 在“管理”下,键入要指定为组织中 {% data variables.product.prodname_github_app %} 管理员的人员,然后单击“授权”。 -![添加 {% data variables.product.prodname_github_app %} 管理员](/assets/images/help/organizations/add-github-app-manager.png) - -## 授权某人管理个别 {% data variables.product.prodname_github_app %} - -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.github-apps-settings-sidebar %} -1. 在 "{% data variables.product.prodname_github_apps %}" 下,单击要为其添加 {% data variables.product.prodname_github_app %} 管理员的应用程序的头像。 -![选择 {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png) {% data reusables.organizations.app-managers-settings-sidebar %} -1. 在“应用管理员”下,键入要指定为应用的 GitHub 应用管理员的人员,然后单击“授权”。 -![添加特定应用的 {% data variables.product.prodname_github_app %} 管理员](/assets/images/help/organizations/add-github-app-manager-for-app.png) - -{% ifversion fpt or ghec %} -## 延伸阅读 - -- [关于 {% data variables.product.prodname_dotcom %} 市场](/articles/about-github-marketplace/) {% endif %} diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/index.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/index.md deleted file mode 100644 index 423c5af009..0000000000 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/index.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: 管理对组织应用程序的访问 -intro: '作为组织所有者,您可以允许个别组织成员管理组织中的 {% data variables.product.prodname_github_apps %}。' -redirect_from: - - /articles/managing-access-to-your-organization-s-apps - - /articles/managing-access-to-your-organizations-apps - - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-apps -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -children: - - /adding-github-app-managers-in-your-organization - - /removing-github-app-managers-from-your-organization -shortTitle: Manage access to apps -ms.openlocfilehash: d40873a01f9027b517868c7dfa43df7ead3c33f9 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145127502' ---- - diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md deleted file mode 100644 index cb0099c645..0000000000 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: 从组织中删除 GitHub 应用程序管理员 -intro: '组织所有者可以撤销授予组织成员的 {% data variables.product.prodname_github_app %}管理员权限。' -redirect_from: - - /articles/removing-github-app-managers-from-your-organization - - /github/setting-up-and-managing-organizations-and-teams/removing-github-app-managers-from-your-organization -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Remove GitHub App managers -ms.openlocfilehash: c7dc813294a1fdd7e928a4212af30efa1182fd3d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145127501' ---- -有关 {% data variables.product.prodname_github_app %} 管理员权限的详细信息,请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#github-app-managers)”。 - -## 删除整个组织的 {% data variables.product.prodname_github_app %}管理员权限 - -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.github-apps-settings-sidebar %} -1. 在“管理”下,找到要删除其 {% data variables.product.prodname_github_app %} 管理员权限的人员的用户名,然后单击“撤销”。 -![撤销 {% data variables.product.prodname_github_app %} 管理员权限](/assets/images/help/organizations/github-app-manager-revoke-permissions.png) - -## 删除单个 {% data variables.product.prodname_github_app %}的 {% data variables.product.prodname_github_app %}管理员权限 - -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.github-apps-settings-sidebar %} -1. 在 "{% data variables.product.prodname_github_apps %}" 下,单击要从其删除 {% data variables.product.prodname_github_app %}管理员的应用程序的头像。 -![选择 {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png) {% data reusables.organizations.app-managers-settings-sidebar %} -1. 在“应用管理员”下,找到要删除其 {% data variables.product.prodname_github_app %} 管理员权限的人员的用户名,然后单击“撤销”。 -![撤销 {% data variables.product.prodname_github_app %} 管理员权限](/assets/images/help/organizations/github-app-manager-revoke-permissions-individual-app.png) - -{% ifversion fpt or ghec %} -## 延伸阅读 - -- [关于 {% data variables.product.prodname_dotcom %} 市场](/articles/about-github-marketplace/) {% endif %} diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md deleted file mode 100644 index 99f3938c99..0000000000 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Adding outside collaborators to repositories in your organization -intro: You can allow people who aren't members of your organization to access repositories that your organization owns. -redirect_from: - - /articles/adding-outside-collaborators-to-repositories-in-your-organization - - /github/setting-up-and-managing-organizations-and-teams/adding-outside-collaborators-to-repositories-in-your-organization -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Add outside collaborator -permissions: People with admin access to a repository can add an outside collaborator to the repository. ---- - -## About outside collaborators - -An outside collaborator is a person who is not a member of your organization, but has access to one or more of your organization's repositories. You can choose the level of access to grant for each outside collaborator. {% data reusables.organizations.outside_collaborator_forks %} - -{% data reusables.organizations.outside-collaborators-use-seats %} - -{% ifversion fpt %} -Organizations that use {% data variables.product.prodname_ghe_cloud %} can restrict the ability to invite collaborators. For more information, see "[Setting permissions for adding outside collaborators](/enterprise-cloud@latest/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators)" in the {% data variables.product.prodname_ghe_cloud %} documentation. -{% else %} -An organization owner can restrict the ability to invite collaborators. For more information, see "[Setting permissions for adding outside collaborators](/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators)." -{% endif %} - -{% ifversion ghes %} -Before you can add someone as an outside collaborator on a repository, the person must have a personal account on {% data variables.product.product_location %}. If your enterprise uses an external authentication system such as SAML or LDAP, the person you want to add must sign in through that system to create an account. If the person does not have access to the authentication system and built-in authentication is enabled for your enterprise, a site administrator can create an account for the person. For more information, see "[Configuring built-in authentication](/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication)." -{% endif %} - -{% ifversion not ghae %} -If your organization requires two-factor authentication, all outside collaborators must enable two-factor authentication before accepting your invitation to collaborate on a repository. For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization)." -{% endif %} - -## Adding outside collaborators to a repository - -{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} -You can give outside collaborators access to a repository in your repository settings. For more information, see "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#inviting-a-team-or-person)." -{% else %} -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -5. In the left sidebar, click **Collaborators & teams**. - ![Repository settings sidebar with Collaborators & teams highlighted](/assets/images/help/repository/org-repo-settings-collaborators-and-teams.png) -6. Under "Collaborators", type the name of the person you'd like to give access to the repository, then click **Add collaborator**. -![The Collaborators section with the Octocat's username entered in the search field](/assets/images/help/repository/org-repo-collaborators-find-name.png) -7. Next to the new collaborator's name, use the drop-down menu and select the appropriate access level. -![The repository permissions picker](/assets/images/help/repository/org-repo-collaborators-choose-permissions.png) -{% endif %} diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md deleted file mode 100644 index 8e514a142c..0000000000 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: 取消成为组织外部协作者的邀请 -intro: 您可以取消让某人成为组织拥有仓库的外部协作者的所有邀请。 -permissions: Organization owners can cancel an invitation to become an outside collaborator in the organization. -redirect_from: - - /github/setting-up-and-managing-organizations-and-teams/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization -versions: - fpt: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Cancel collaborator invitation -ms.openlocfilehash: 4511f6ffd7a22884a390e073826f7ff198adb7f2 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145127482' ---- -您可以查看所有待定邀请(邀请成为组织拥有的任何仓库上的外部协作者)人员列表。 - -对于每个待定协作者,您可以同时取消加入组织仓库的所有邀请。 - -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %} {% data reusables.organizations.people_tab_outside_collaborators %} -5. 单击“X 待定协作者”。 - ![“待定协作者”按钮](/assets/images/help/organizations/pending-collaborator-list.png) -6. 在要取消邀请的人员右侧,单击“取消邀请”。 - ![“取消邀请”按钮](/assets/images/help/organizations/cancel-pending-collaborators.png) -7. 单击“取消对待定协作者的邀请”。 - ![确认取消按钮](/assets/images/help/organizations/confirm-cancelation-of-pending-collaborators.png) diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md deleted file mode 100644 index e116d9d6ec..0000000000 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -title: 将组织成员转换为外部协作者 -intro: 如果组织的某些当前成员只需要访问特定仓库,例如顾问或临时员工,你可以将他们转换为外部协作者。 -permissions: Organization owners can convert an organization member to an outside collaborator. -redirect_from: - - /articles/converting-an-organization-member-to-an-outside-collaborator - - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-member-to-an-outside-collaborator -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Convert member to collaborator -ms.openlocfilehash: 4b9330559895ec96cb6c842d89dbe4e9a8773685 -ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '146754596' ---- -## 关于组织成员转换为外部协作者 - -可以将组织的成员转换为外部协作者。 有关外部协作者的详细信息,请参阅“[将外部协作者添加到组织中的存储库](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)”。 - -{% ifversion fpt or ghec %}如果组织由企业所有,则可能会限制将组织成员转换{% elsif ghes or ghae %}转换{% endif %}为外部协作者。 有关详细信息,请参阅“[在企业中实施存储库管理策略]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-{% ifversion fpt or ghec %}outside-{% endif %}collaborators-to-repositories){% ifversion ghec or ghes or ghae %}”。"{% elsif fpt %}"(在 {% data variables.product.prodname_ghe_cloud %} 文档中)。{% endif %} - -{% data reusables.organizations.outside-collaborators-use-seats %} {% data reusables.organizations.outside_collaborator_forks %} - -将组织成员转换为外部协作者后,他们将只能访问其当前团队成员资格允许的仓库。 他们将不再是组织的正式成员,不再能够: - -- 创建团队 -- 查看所有组织成员和团队 -- @mention 任何可见团队 -- 成为团队维护员 - -有关详细信息,请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。 - -建议查看组织成员对仓库的访问权限,以确保其访问权限符合您的预期。 有关详细信息,请参阅[管理个人对组织存储库的访问](/articles/managing-an-individual-s-access-to-an-organization-repository)。 - -将组织成员转换为外部协作者时,他们作为组织成员的权限将保存三个月,因此,如果你在该时间范围内{% ifversion fpt or ghec %} 邀请他们重新加入{% else %} 将他们重新添加到{% endif %} 你的组织,你可以恢复其成员权限。 有关详细信息,请参阅“[恢复组织的前成员](/articles/reinstating-a-former-member-of-your-organization)”。 - -## 将组织成员转换为外部协作者 - -{% note %} - -注意:如果组织所有者{% ifversion not fpt %} 或企业所有者{% endif %} 限制了你添加外部协作者的能力,你可能无法将组织成员转换为外部协作者。 - -{% endnote %} - -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %} -4. 选择要转换为外部协作者的人员。 - ![选中两名成员的成员列表](/assets/images/help/teams/list-of-members-selected-bulk.png) -5. 在成员列表的上方,使用下拉菜单并单击“转换为外部协作者”。 - ![含有将成员转换为外部协作者选项的下拉菜单](/assets/images/help/teams/user-bulk-management-options.png) -6. 阅读有关将成员转换为外部协作者的信息,然后单击“转换为外部协作者”。 - ![有关外部协作者权限的信息和转换为外部协作者按钮](/assets/images/help/teams/confirm-outside-collaborator-bulk.png) - -## 延伸阅读 - -- [将外部协作者添加到组织中的存储库](/articles/adding-outside-collaborators-to-repositories-in-your-organization) -- [从组织存储库中删除外部协作者](/articles/removing-an-outside-collaborator-from-an-organization-repository) -- [将外部协作者转换为组织成员](/articles/converting-an-outside-collaborator-to-an-organization-member) diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md deleted file mode 100644 index 33f0ad923f..0000000000 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: 将外部协作者转换为组织成员 -intro: '如果你希望为组织存储库的外部协作者提供更广泛的组织内权限,可以{% ifversion fpt or ghec %}邀请他们成为组织的成员{% else %}让他们成为组织成员{% endif %}。' -redirect_from: - - /articles/converting-an-outside-collaborator-to-an-organization-member - - /github/setting-up-and-managing-organizations-and-teams/converting-an-outside-collaborator-to-an-organization-member -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -permissions: 'Organization owners can {% ifversion fpt or ghec %}invite users to join{% else %}add users to{% endif %} an organization.' -topics: - - Organizations - - Teams -shortTitle: Convert collaborator to member -ms.openlocfilehash: bac55802407b46344c807798e4d8eade5f608e01 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145127480' ---- -{% ifversion fpt or ghec %}如果组织采用付费的每用户订阅,则必须有未使用的许可证才可邀请新成员加入组织或恢复前组织成员。 有关详细信息,请参阅“[关于每用户定价](/articles/about-per-user-pricing)”。 {% data reusables.organizations.org-invite-expiration %}{% endif %} - -{% ifversion not ghae %}如果组织[需要成员使用双因素身份验证](/articles/requiring-two-factor-authentication-in-your-organization),则{% ifversion fpt or ghec %}你邀请的用户必须[启用双因素身份验证](/articles/securing-your-account-with-two-factor-authentication-2fa),然后才可接受邀请。{% else %}用户必须[启用双因素身份验证](/articles/securing-your-account-with-two-factor-authentication-2fa),然后才可将用户添加到组织。{% endif %} {% endif %} - -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %} {% data reusables.organizations.people_tab_outside_collaborators %} {% ifversion fpt or ghec %} -5. 在要添加为成员的外部协作者姓名的右侧,使用 {% octicon "gear" aria-label="The gear icon" %} 下拉菜单,然后单击“邀请加入组织”。![邀请外部协作者加入组织](/assets/images/help/organizations/invite_outside_collaborator_to_organization.png){% else %} -5. 在要添加为成员的外部协作者姓名的右侧,单击“邀请加入组织”。![邀请外部协作者加入组织](/assets/images/enterprise/orgs-and-teams/invite_outside_collabs_to_org.png){% endif %} {% data reusables.organizations.choose-to-restore-privileges %} {% data reusables.organizations.choose-user-role-send-invitation %} {% ifversion fpt or ghec %} {% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} {% endif %} - -## 延伸阅读 - -- [将组织成员转换为外部协作者](/articles/converting-an-organization-member-to-an-outside-collaborator) diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/index.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/index.md deleted file mode 100644 index ae91ca9437..0000000000 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/index.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: 管理对组织存储库的访问权限 -intro: 组织所有者可以管理个人和团队对组织仓库的访问。 团队维护员也可以管理团队的仓库访问权限。 -redirect_from: - - /articles/permission-levels-for-an-organization-repository - - /articles/managing-access-to-your-organization-s-repositories - - /articles/managing-access-to-your-organizations-repositories - - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-repositories -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -children: - - /repository-roles-for-an-organization - - /setting-base-permissions-for-an-organization - - /viewing-people-with-access-to-your-repository - - /managing-an-individuals-access-to-an-organization-repository - - /managing-team-access-to-an-organization-repository - - /adding-outside-collaborators-to-repositories-in-your-organization - - /canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization - - /removing-an-outside-collaborator-from-an-organization-repository - - /converting-an-organization-member-to-an-outside-collaborator - - /converting-an-outside-collaborator-to-an-organization-member - - /reinstating-a-former-outside-collaborators-access-to-your-organization -shortTitle: Manage access to repositories -ms.openlocfilehash: e6789a7d8f2379f7aa2a6193d21ecdd385f69bab -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145127479' ---- - diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md deleted file mode 100644 index 24fcd16b9f..0000000000 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: Managing an individual's access to an organization repository -intro: You can manage a person's access to a repository owned by your organization. -redirect_from: - - /articles/managing-an-individual-s-access-to-an-organization-repository-early-access-program - - /articles/managing-an-individual-s-access-to-an-organization-repository - - /articles/managing-an-individuals-access-to-an-organization-repository - - /github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-repository -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Manage individual access -permissions: People with admin access to a repository can manage access to the repository. ---- - -## About access to organization repositories - -When you remove a collaborator from a repository in your organization, the collaborator loses read and write access to the repository. If the repository is private and the collaborator has forked the repository, then their fork is also deleted, but the collaborator will still retain any local clones of your repository. - -{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} - -{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} -## Managing an individual's access to an organization repository -You can give a person access to a repository or change a person's level of access to a repository in your repository settings. For more information, see "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." -{% else %} -## Giving a person access to a repository - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-settings %} -{% data reusables.repositories.navigate-to-manage-access %} -{% data reusables.organizations.invite-teams-or-people %} -1. In the search field, start typing the name of the person to invite, then click a name in the list of matches. - ![Search field for typing the name of a team or person to invite to the repository](/assets/images/help/repository/manage-access-invite-search-field.png) -6. Under "Choose a role", select the repository role to assign the person, then click **Add NAME to REPOSITORY**. - ![Selecting permissions for the team or person](/assets/images/help/repository/manage-access-invite-choose-role-add.png) - -## Managing an individual's access to an organization repository - -{% data reusables.profile.access_org %} -{% data reusables.user-settings.access_org %} -{% data reusables.organizations.people %} -4. Click either **Members** or **Outside collaborators** to manage people with different types of access. ![Button to invite members or outside collaborators to an organization](/assets/images/help/organizations/select-outside-collaborators.png) -5. To the right of the name of the person you'd like to manage, use the {% octicon "gear" aria-label="The Settings gear" %} drop-down menu, and click **Manage**. - ![The manage access link](/assets/images/help/organizations/member-manage-access.png) -6. On the "Manage access" page, next to the repository, click **Manage access**. -![Manage access button for a repository](/assets/images/help/organizations/repository-manage-access.png) -7. Review the person's access to a given repository, such as whether they're a collaborator or have access to the repository via team membership. -![Repository access matrix for the user](/assets/images/help/organizations/repository-access-matrix-for-user.png) -{% endif %} -## Further reading - -{% ifversion fpt or ghec %}- "[Limiting interactions with your repository](/articles/limiting-interactions-with-your-repository)"{% endif %} -- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md deleted file mode 100644 index 039d6e4860..0000000000 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: Managing team access to an organization repository -intro: 'You can give a team access to a repository, remove a team''s access to a repository, or change a team''s permission level for a repository.' -redirect_from: - - /articles/managing-team-access-to-an-organization-repository-early-access-program - - /articles/managing-team-access-to-an-organization-repository - - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-repository -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Manage team access ---- - -People with admin access to a repository can manage team access to the repository. Team maintainers can remove a team's access to a repository if the team has direct access to it. If the team's access to the repository is inherited from a parent team, maintainers can choose to reset the current permission to match the parent team's permission. - -{% warning %} - -**Warnings:** -- You can change a team's permission level if the team has direct access to a repository. If the team's access to the repository is inherited from a parent team, you must change the parent team's access to the repository. -- If you add or remove repository access for a parent team, each of that parent's child teams will also receive or lose access to the repository. For more information, see "[About teams](/articles/about-teams)." - -{% endwarning %} - -## Giving a team access to a repository - -{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} -You can give a team access to a repository or change a team's level of access to a repository in your repository settings. For more information, see "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#inviting-a-team-or-person)." -{% else %} -{% data reusables.profile.access_org %} -{% data reusables.user-settings.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team-repositories-tab %} -5. Above the list of repositories, click **Add repository**. - ![The Add repository button](/assets/images/help/organizations/add-repositories-button.png) -6. Type the name of a repository, then click **Add repository to team**. - ![Repository search field](/assets/images/help/organizations/team-repositories-add.png) -7. Optionally, to the right of the repository name, use the drop-down menu and choose a different permission level for the team. - ![Repository access level dropdown](/assets/images/help/organizations/team-repositories-change-permission-level.png) -{% endif %} -## Removing a team's access to a repository - -{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} -You can remove a team's access to an organization repository in your repository settings. For more information, see "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#removing-access-for-a-team-or-person)." - -If a team has direct access to a repository, you can remove that team's access to the repository. If a team's access to the repository is inherited from a parent team, you must remove the repository from the parent team in order to remove the repository from child teams. - -{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} - -{% else %} - -You can remove a team's access to a repository if the team has direct access to a repository. If a team's access to the repository is inherited from a parent team, you must remove the repository from the parent team in order to remove the repository from child teams. - -{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} - -{% data reusables.profile.access_org %} -{% data reusables.user-settings.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team-repositories-tab %} -5. Select the repository or repositories you'd like to remove from the team. - ![List of team repositories with the checkboxes for some repositories selected](/assets/images/help/teams/select-team-repositories-bulk.png) -6. Above the list of repositories, use the drop-down menu, and click **Remove from team**. - ![Drop-down menu with the option to remove a repository from a team](/assets/images/help/teams/remove-team-repo-dropdown.png) -7. Review the repository or repositories that will be removed from the team, then click **Remove repositories**. - ![Modal box with a list of repositories that the team will no longer have access to](/assets/images/help/teams/confirm-remove-team-repos.png) -{% endif %} -## Further reading - -- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md deleted file mode 100644 index f30b3f3bfe..0000000000 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: 恢复前外部协作者对组织的访问权限 -intro: 您可以恢复前外部协作者对组织仓库、复刻和设置的访问权限。 -redirect_from: - - /articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization - - /articles/reinstating-a-former-outside-collaborators-access-to-your-organization - - /github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-outside-collaborators-access-to-your-organization -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Reinstate collaborator -ms.openlocfilehash: 88d986f922f1a66d652dba55f10142f7e493ffa2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146178901' ---- -当外部协作者对组织私有仓库的权限被删除时,该用户的访问权限和设置将保存三个月。 如果您在该时间范围内将用户{% ifversion fpt or ghec %}邀请{% else %}添加{% endif %}回组织,则可以恢复该用户的权限。 - -{% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %} - -恢复前外部协作者时,您可以恢复以下各项: - - 用户对组织仓库以前的访问权限 - - 组织拥有的仓库的任何私有复刻 - - 组织团队的成员身份 - - 组织仓库以前的访问权限和权限 - - 组织仓库的星标 - - 组织中的议题分配 - - 仓库订阅(关注、不关注或忽略仓库活动的通知设置) - -{% tip %} - -**提示**: - - - 只有组织所有者才能恢复外部协作者对组织的访问权限。{% ifversion prevent-org-admin-add-outside-collaborator %} 企业所有者可能会进一步限制恢复外部协作者对企业所有者的访问权限的能力。{% endif %} 有关详细信息,请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。 - - 在 {% data variables.product.product_location %} 上恢复成员流时,可能会使用术语“成员”来描述恢复外部协作者,但如果恢复此人并保留其以前的特权,则他们将仅拥有以前的[外部协作者权限](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)。{% ifversion fpt or ghec %} - - 如果您的组织采用付费的每用户订阅,则必须有未使用的许可才可邀请新成员加入组织或恢复前组织成员。 有关详细信息,请参阅“[关于每用户定价](/articles/about-per-user-pricing)”。{% endif %} - -{% endtip %} - -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %} {% data reusables.organizations.invite_member_from_people_tab %} {% data reusables.organizations.reinstate-user-type-username %} {% ifversion fpt or ghec %} -1. 通过单击“邀请并恢复”选择恢复外部协作者以前在组织中的权限,或通过单击“邀请并重新开始”选择清除他们以前的权限并设置新的访问权限 。 - - {% warning %} - - 警告:如果要将外部协作者升级为组织的成员,请选择“邀请并重新开始”,并为此人选择一个新角色 。 但是,请注意,如果您选择重新开始,则此人员组织仓库的私人复刻将会丢失。 若要使前外部协作者成为组织的成员并保留其专用分支,请选择“邀请并恢复”。 在此人接受邀请后,可以通过[邀请他们以成员身份加入组织](/articles/converting-an-outside-collaborator-to-an-organization-member),将他们转变为组织成员。 - - {% endwarning %} - - ![选择是否恢复设置](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png) {% else %} -6. 通过单击“添加并恢复”选择恢复外部协作者以前在组织中的权限,或通过单击“添加并重新开始”选择清除他们以前的权限并设置新的访问权限 。 - - {% warning %} - - 警告:如果要将外部协作者升级为组织的成员,请选择“添加并重新开始”,并为此人选择一个新角色 。 但是,请注意,如果您选择重新开始,则此人员组织仓库的私人复刻将会丢失。 若要使前外部协作者成为组织的成员并保留其专用分支,请选择“添加并恢复”。 然后,可以通过[将其作为成员添加到组织](/articles/converting-an-outside-collaborator-to-an-organization-member)来将其转变为组织成员。 - - {% endwarning %} - - ![选择是否还原设置](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png) {% endif %} {% ifversion fpt or ghec %} -7. 如果清除了前外部协作者以前的权限,请为该用户选择一个角色,并(可选)将其添加到某些团队,然后单击“发送邀请”。 - ![角色和团队选项及“发送邀请”按钮](/assets/images/help/organizations/add-role-send-invitation.png) {% else %} -7. 如果清除了前外部协作者以前的权限,请为该用户选择一个角色,并(可选)将其添加到某些团队,然后单击“添加成员”。 - ![角色和团队选项及“添加成员”按钮](/assets/images/help/organizations/add-role-add-member.png) {% endif %} {% ifversion fpt or ghec %} -8. 被邀请的人员将收到邀请其加入组织的电子邮件。 它们需要接受邀请,然后才能成为组织中的外部协作者。 {% data reusables.organizations.cancel_org_invite %} {% endif %} - -## 深入阅读 - -- “[组织的存储库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)” diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md deleted file mode 100644 index 2460a6e4a0..0000000000 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Removing an outside collaborator from an organization repository -intro: Owners and repository admins can remove an outside collaborator's access to a repository. -redirect_from: - - /articles/removing-an-outside-collaborator-from-an-organization-repository - - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-repository -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Remove collaborator ---- - -{% ifversion fpt or ghec %} - -{% warning %} - -**Warning:** -- When removing an outside collaborator from a private repository, the paid license count does not automatically downgrade. To pay for fewer licenses after removing users from your organization, follow the steps in "[Downgrading your organization's paid seats](/articles/downgrading-your-organization-s-paid-seats)." - -- You are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property. - -{% endwarning %} - -{% endif %} - -While forks of private repositories are deleted when a collaborator is removed, the person will still retain any local clones of your repository. - -## Removing outside collaborators from all repositories in an organization - -{% data reusables.profile.access_org %} -{% data reusables.user-settings.access_org %} -{% data reusables.organizations.people %} -{% data reusables.organizations.people_tab_outside_collaborators %} -5. Select the outside collaborator or outside collaborators you'd like to remove from the organization. -![List of outside collaborators with two outside collaborators selected](/assets/images/help/teams/list-of-outside-collaborators-selected-bulk.png) -6. Above the list of outside collaborators, use the drop-down menu, and click **Remove from all repositories**. -![Drop-down menu with option to remove outside collaborators ](/assets/images/help/teams/user-bulk-management-options-for-outside-collaborators.png) -7. Review the outside collaborator or outside collaborators who will be removed from the organization, then click **Remove outside collaborators**. - ![List of outside collaborators who will be removed and Remove outside collaborators button](/assets/images/help/teams/confirm-remove-outside-collaborators-bulk.png) - -## Removing an outside collaborator from a particular repository in an organization - -If you only want to remove an outside collaborator from certain repositories in your organization, you can remove this person's access to one specific repository at a time. - -{% data reusables.profile.access_org %} -{% data reusables.user-settings.access_org %} -{% data reusables.organizations.people %} -{% data reusables.organizations.people_tab_outside_collaborators %} -5. To the right of the username of the person you want to remove, use the {% octicon "gear" aria-label="The Settings gear" %} drop-down menu, and click **Manage**. - ![Manage access button](/assets/images/help/organizations/member-manage-access.png) -6. To the right of the repository that you want to remove the outside collaborator from, click **Manage access**. -![Select manage access button next to a repository the outside collaborator has access to](/assets/images/help/organizations/second-manage-access-selection-for-collaborator.png) -7. To completely remove the outside collaborator's access to the repository, in the upper right corner, click **Remove access to this repository**. -![Remove access to this repository button](/assets/images/help/organizations/remove-access-to-this-repository.png) -8. To confirm, click **Remove access**. -![Confirm outside collaborator who will be removed from the repository](/assets/images/help/teams/confirm-remove-outside-collaborator-from-a-repository.png) - -{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} -You can also remove an outside collaborator from a repository in the access overview in your repository settings. For more information, see "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#removing-access-for-a-team-or-person)." -{% endif %} -## Further reading - -- "[Adding outside collaborators to repositories in your organization](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" -- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)" diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md deleted file mode 100644 index 84d478f3b6..0000000000 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md +++ /dev/null @@ -1,175 +0,0 @@ ---- -title: Repository roles for an organization -intro: 'You can customize access to each repository in your organization by assigning granular roles, giving people access to the features and tasks they need.' -miniTocMaxHeadingLevel: 3 -redirect_from: - - /articles/repository-permission-levels-for-an-organization-early-access-program - - /articles/repository-permission-levels-for-an-organization - - /github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization - - /organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Repository roles ---- - -## Repository roles for organizations - -You can give organization members, outside collaborators, and teams of people different levels of access to repositories owned by an organization by assigning them to roles. Choose the role that best fits each person or team's function in your project without giving people more access to the project than they need. - -From least access to most access, the roles for an organization repository are: -- **Read**: Recommended for non-code contributors who want to view or discuss your project -- **Triage**: Recommended for contributors who need to proactively manage issues and pull requests without write access -- **Write**: Recommended for contributors who actively push to your project -- **Maintain**: Recommended for project managers who need to manage the repository without access to sensitive or destructive actions -- **Admin**: Recommended for people who need full access to the project, including sensitive and destructive actions like managing security or deleting a repository - -{% ifversion fpt %} -If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can create custom repository roles. For more information, see "[Managing custom repository roles for an organization](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)" in the {% data variables.product.prodname_ghe_cloud %} documentation. -{% elsif ghec or ghes > 3.4 or ghae > 3.4 %} -You can create custom repository roles. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." -{% endif %} - -Organization owners can set base permissions that apply to all members of an organization when accessing any of the organization's repositories. For more information, see "[Setting base permissions for an organization](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)." - -Organization owners can also choose to further limit access to certain settings and actions across the organization. For more information on options for specific settings, see "[Managing organization settings](/articles/managing-organization-settings)." - -In addition to managing organization-level settings, organization owners have admin access to every repository owned by the organization. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." - -{% warning %} - -**Warning:** When someone adds a deploy key to a repository, any user who has the private key can read from or write to the repository (depending on the key settings), even if they're later removed from the organization. - -{% endwarning %} - -## Permissions for each role - -{% ifversion fpt %} -Some of the features listed below are limited to organizations using {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} -{% endif %} - -{% ifversion fpt or ghes or ghec %} -{% note %} - -**Note:** The roles required to use security features are listed in "[Access requirements for security features](#access-requirements-for-security-features)" below. - -{% endnote %} -{% endif %} - -| Repository action | Read | Triage | Write | Maintain | Admin | -|:---|:---:|:---:|:---:|:---:|:---:| -| Manage [individual](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository), [team](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository), and [outside collaborator](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization) access to the repository | | | | | **✔️** | -| Pull from the person or team's assigned repositories | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| Fork the person or team's assigned repositories | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| Edit and delete their own comments | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| Open issues | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| Close issues they opened themselves | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| Reopen issues they closed themselves | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| Have an issue assigned to them | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| Send pull requests from forks of the team's assigned repositories | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| Submit reviews on pull requests | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| View published releases | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} -| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% endif %} -| Edit wikis in public repositories | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| Edit wikis in private repositories | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} -| [Report abusive or spammy content](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% endif %} -| Apply/dismiss labels | | **✔️** | **✔️** | **✔️** | **✔️** | -| Create, edit, delete labels | | | **✔️** | **✔️** | **✔️** | -| Close, reopen, and assign all issues and pull requests | | **✔️** | **✔️** | **✔️** | **✔️** | -| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **✔️** | **✔️** | **✔️** | -| Apply milestones | | **✔️** | **✔️** | **✔️** | **✔️** | -| Mark [duplicate issues and pull requests](/articles/about-duplicate-issues-and-pull-requests)| | **✔️** | **✔️** | **✔️** | **✔️** | -| Request [pull request reviews](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) | | **✔️** | **✔️** | **✔️** | **✔️** | -| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **✔️** | **✔️** | **✔️** | -| Push to (write) the person or team's assigned repositories | | | **✔️** | **✔️** | **✔️** | -| Edit and delete anyone's comments on commits, pull requests, and issues | | | **✔️** | **✔️** | **✔️** | -| [Hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **✔️** | **✔️** | **✔️** | -| [Lock conversations](/communities/moderating-comments-and-conversations/locking-conversations) | | | **✔️** | **✔️** | **✔️** | -| Transfer issues (see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)" for details) | | | **✔️** | **✔️** | **✔️** | -| [Act as a designated code owner for a repository](/articles/about-code-owners) | | | **✔️** | **✔️** | **✔️** | -| [Mark a draft pull request as ready for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** | -| [Convert a pull request to a draft](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** | -| Submit reviews that affect a pull request's mergeability | | | **✔️** | **✔️** | **✔️** | -| [Apply suggested changes](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) to pull requests | | | **✔️** | **✔️** | **✔️** | -| Create [status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} -| Create, edit, run, re-run, and cancel [GitHub Actions workflows](/actions/automating-your-workflow-with-github-actions/) | | | **✔️** | **✔️** | **✔️** |{% endif %} -| Create and edit releases | | | **✔️** | **✔️** | **✔️** | -| View draft releases | | | **✔️** | **✔️** | **✔️** | -| Edit a repository's description | | | | **✔️** | **✔️** |{% ifversion fpt or ghae or ghec %} -| [View and install packages](/packages/publishing-and-managing-packages) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **✔️** | **✔️** | **✔️** | -| [Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package) | | | | | **✔️** | {% endif %} -| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **✔️** | **✔️** | -| Enable wikis and restrict wiki editors | | | | **✔️** | **✔️** | -| Enable project boards | | | | **✔️** | **✔️** | -| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **✔️** | **✔️** | -| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **✔️** | **✔️** | -| [Manage branch protection rules](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule) | | | | | **✔️** | -| [Push to protected branches](/articles/about-protected-branches) | | | | **✔️** | **✔️** | -| Merge pull requests on protected branches, even if there are no approving reviews | | | | | **✔️** |{% ifversion fpt or ghes > 3.4 or ghae > 3.4 or ghec %} -| Create tags that match a [tag protection rule](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) | | | | **✔️** | **✔️** | -| Delete tags that match a [tag protection rule](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) | | | | | **✔️** |{% endif %} -| [Create and edit repository social cards](/articles/customizing-your-repositorys-social-media-preview) | | | | **✔️** | **✔️** |{% ifversion fpt or ghec %} -| Limit [interactions in a repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)| | | | **✔️** | **✔️** |{% endif %} -| Delete an issue (see "[Deleting an issue](/articles/deleting-an-issue)") | | | | | **✔️** | -| [Define code owners for a repository](/articles/about-code-owners) | | | | | **✔️** | -| Add a repository to a team (see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" for details) | | | | | **✔️** | -| [Manage outside collaborator access to a repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **✔️** | -| [Change a repository's visibility](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **✔️** | -| Make a repository a template (see "[Creating a template repository](/articles/creating-a-template-repository)") | | | | | **✔️** | -| Change a repository's settings | | | | | **✔️** | -| Manage team and collaborator access to the repository | | | | | **✔️** | -| Edit the repository's default branch | | | | | **✔️** | -| Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **✔️** | -| Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **✔️** | **✔️** | **✔️** | -| Manage webhooks and deploy keys | | | | | **✔️** |{% ifversion fpt or ghec %} -| [Manage data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository) | | | | | **✔️** |{% endif %} -| [Manage the forking policy for a repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **✔️** | -| [Transfer repositories into the organization](/articles/restricting-repository-creation-in-your-organization) | | | | | **✔️** | -| [Delete or transfer repositories out of the organization](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **✔️** | -| [Archive repositories](/articles/about-archiving-repositories) | | | | | **✔️** |{% ifversion fpt or ghec %} -| Display a sponsor button (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **✔️** |{% endif %} -| Create autolink references to external resources, like Jira or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **✔️** |{% ifversion discussions %} -| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **✔️** | **✔️** | -| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions) for {% data variables.product.prodname_discussions %} | | | | **✔️** | **✔️** | -| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | -| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions) to a new repository| | | **✔️** | **✔️** | **✔️** | -| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | -| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | -| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **✔️** | **✔️** | **✔️** | **✔️** | -| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **✔️** | **✔️** | **✔️** | **✔️** | -| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion) | | **✔️** | | **✔️** | **✔️** |{% endif %}{% ifversion fpt or ghec %} -| Create [codespaces](/codespaces/about-codespaces) | | | **✔️** | **✔️** | **✔️** |{% endif %} - -### Access requirements for security features - -In this section, you can find the access required for security features, such as {% data variables.product.prodname_advanced_security %} features. - -| Repository action | Read | Triage | Write | Maintain | Admin | -|:---|:---:|:---:|:---:|:---:|:---:| -| Receive [{% data variables.product.prodname_dependabot_alerts %} for insecure dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **✔️** | -| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **✔️** |{% ifversion ghes or ghae or ghec %} -| [Designate additional people or teams to receive security alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **✔️** |{% endif %}{% ifversion fpt or ghec %} -| Create [security advisories](/code-security/security-advisories/about-github-security-advisories) | | | | | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} -| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **✔️** |{% endif %}{% ifversion fpt or ghec %} -| [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository | | | | | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} -| [View dependency reviews](/code-security/supply-chain-security/about-dependency-review) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% endif %} -| [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | -| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **✔️** | **✔️** | **✔️** | -| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️** |{% ifversion ghes or ghae or ghec %} -| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} -| [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **✔️** |{% endif %} - -[1] Repository writers and maintainers can only see alert information for their own commits. - -## Further reading - -- "[Managing access to your organization's repositories](/articles/managing-access-to-your-organization-s-repositories)" -- "[Adding outside collaborators to repositories in your organization](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" -- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md deleted file mode 100644 index 7046b072f2..0000000000 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: 为组织设置基本权限 -intro: 您可以为组织拥有的仓库设置基本权限。 -permissions: Organization owners can set base permissions for an organization. -redirect_from: - - /github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Set base permissions -ms.openlocfilehash: 734ced023e4a1043634650ff3e4305727397095c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146179925' ---- -## 关于组织的基本权限 - -您可以在访问组织的任何仓库时设置适用于组织所有成员的基本权限。 基本权限不适用于外部协作者。 - -{% ifversion fpt or ghec %}默认情况下,组织的成员将对组织的存储库拥有读取权限。{% endif %} - -如果对组织存储库具有管理员访问权限的人员向成员授予对存储库的更高级别的访问权限,则较高级别的访问权限将覆盖基本权限。 - -{% ifversion custom-repository-roles %} 如果你创建了继承角色的访问权限低于组织基本权限的自定义存储库角色,则分配给该角色的任何成员都将默认使用组织的基本权限,而不是继承的角色。 有关详细信息,请参阅“[管理组织的自定义存储库角色](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)”。 -{% endif %} - -## 设置基本权限 - -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.member-privileges %} -5. 在“Base permissions(基本权限)”下,使用下拉菜单选择新的基本权限。 - ![从基本权限下拉菜单中选择新的权限级别](/assets/images/help/organizations/base-permissions-drop-down.png) -6. 查看更改。 要确认,请单击“将默认权限更改为 PERMISSION”。 - ![审查并确认基本权限的更改](/assets/images/help/organizations/base-permissions-confirm.png) - -## 延伸阅读 - -- [组织的存储库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization) -- [将外部协作者添加到组织中的存储库](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization) diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md deleted file mode 100644 index 6c437bf3f1..0000000000 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md +++ /dev/null @@ -1,58 +0,0 @@ ---- -title: Viewing people with access to your repository -intro: 'You can view{% ifversion ghec or ghes or ghae %} and export{% endif %} a list of people with access to a repository within an organization.' -redirect_from: - - /articles/viewing-people-with-access-to-your-repository - - /github/setting-up-and-managing-organizations-and-teams/viewing-people-with-access-to-your-repository -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: View people with access -permissions: Organization owners can view people with access to a repository. ---- - -## About the list of people with access to your repository - -You can use this information to help off-board people, gather data for compliance, and other general security checkups. - -{% ifversion fpt %} -Organizations that use {% data variables.product.prodname_ghe_cloud %} can also export a CSV list of people who have access to a repository. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository). -{% endif %} - -{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} -![Access management overview](/assets/images/help/repository/manage-access-overview.png) -{% else %} -![Repository people permissions list](/assets/images/help/repository/repository-permissions-list.png) -{% endif %} -## Viewing people with access to your repository - -{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} -You can see a combined overview of teams and people with access to your repository in your repository settings. For more information, see "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#about-access-management-for-repositories)." -{% else %} -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.accessing-repository-graphs %} -{% data reusables.repositories.accessing-repository-people %} -{% endif %} - -{% ifversion ghec or ghes or ghae %} -## Exporting a list of people with access to your repository - -{% ifversion ghec %} -{% note %} - -**Note:** Only organizations that use {% data variables.product.prodname_ghe_cloud %} can export a list of people with access to a repository. {% data reusables.enterprise.link-to-ghec-trial %} - -{% endnote %} -{% endif %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.accessing-repository-graphs %} -{% data reusables.repositories.accessing-repository-people %} -4. Click **Export CSV**. - ![People tab in the repository sidebar](/assets/images/help/repository/export-repository-permissions.png) -{% endif %} diff --git a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md index 329990ae11..99c980c99f 100644 --- a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md +++ b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md @@ -1,6 +1,6 @@ --- -title: 关于 SSH 认证中心 -intro: 通过 SSH 认证中心,组织或企业帐户可提供 SSH 证书,供成员用来通过 Git 访问您的资源。 +title: About SSH certificate authorities +intro: 'With an SSH certificate authority, your organization or enterprise account can provide SSH certificates that members can use to access your resources with Git.' redirect_from: - /articles/about-ssh-certificate-authorities - /github/setting-up-and-managing-organizations-and-teams/about-ssh-certificate-authorities @@ -12,64 +12,60 @@ topics: - Organizations - Teams shortTitle: SSH certificate authorities -ms.openlocfilehash: c4940399efa3c1e88c68224c421de7f43f7ea89b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147061977' --- -## 关于 SSH 认证中心 -SSH 证书是一种机制:一个 SSH 密钥对另一个 SSH 密钥签名。 如果使用 SSH 认证中心 (CA) 为组织成员提供已签名的 SSH 证书,您可以将 CA 添加到企业帐户或组织,以便组织成员使用其证书访问组织资源。 +## About SSH certificate authorities + +An SSH certificate is a mechanism for one SSH key to sign another SSH key. If you use an SSH certificate authority (CA) to provide your organization members with signed SSH certificates, you can add the CA to your enterprise account or organization to allow organization members to use their certificates to access organization resources. {% data reusables.organizations.ssh-ca-ghec-only %} -在将 SSH CA 添加到组织或企业帐户后,您可以使用 CA 为组织成员签名客户 SSH 证书。 组织成员可以使用已签名的证书通过 Git 访问组织的仓库(并且只访问您组织的仓库)。 (可选)您可以要求成员使用 SSH 证书访问组织资源。 有关详细信息,请参阅“[管理组织的 SSH 证书颁发机构](/articles/managing-your-organizations-ssh-certificate-authorities)”和“[在企业中强制实施安全设置策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)”。 +After you add an SSH CA to your organization or enterprise account, you can use the CA to sign client SSH certificates for organization members. Organization members can use the signed certificates to access your organization's repositories (and only your organization's repositories) with Git. Optionally, you can require that members use SSH certificates to access organization resources. For more information, see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" and "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)." -例如,您可以构建内部系统,每天早上向开发者颁发新证书。 每个开发者可以使用其每日证书处理组织在 {% data variables.product.product_name %} 上的仓库。 在一天结束时,证书会自动到期,以保护仓库,避免证书以后被窃取。 +For example, you can build an internal system that issues a new certificate to your developers every morning. Each developer can use their daily certificate to work on your organization's repositories on {% data variables.product.product_name %}. At the end of the day, the certificate can automatically expire, protecting your repositories if the certificate is later compromised. -{% ifversion ghec %} 即使实施了 SAML 单一登录,组织成员也可使用其签名的证书进行身份验证。 除非您将 SSH 证书设为要求,组织成员可继续使用其他验证方式通过 Git 访问组织的资源,包括他们的用户名和密码、个人访问令牌及其自己的 SSH 密钥。 +{% ifversion ghec %} +Organization members can use their signed certificates for authentication even if you've enforced SAML single sign-on. Unless you make SSH certificates a requirement, organization members can continue to use other means of authentication to access your organization's resources with Git, including their username and password, {% data variables.product.pat_generic %}s, and their own SSH keys. {% endif %} -成员将无法使用其证书访问其个人帐户拥有的仓库的复刻。 +Members will not be able to use their certificates to access forks of your repositories that are owned by their personal accounts. -## 关于使用 SSH 证书的 SSH URL +## About SSH URLs with SSH certificates -如果您的组织需要 SSH 证书,为了防止身份验证错误,组织成员在通过 SSH 执行 Git 操作时应使用包含组织 ID 的特殊 URL。 此特殊 URL 允许客户端和服务器更轻松地协商应使用成员计算机上的哪个密钥进行身份验证。 如果成员使用以 `git@github.com` 开头的正常 URL,则 SSH 客户端可能会提供错误的密钥,从而导致操作失败。 +If your organization requires SSH certificates, to prevent authentication errors, organization members should use a special URL that includes the organization ID when performing Git operations over SSH. This special URL allows the client and server to more easily negotiate which key on the member's computer should be used for authentication. If a member uses the normal URL, which starts with `git@github.com`, the SSH client might offer the wrong key, causing the operation to fail. -对存储库具有读取访问权限的任何人都可以通过以下方式找到此 URL:选择存储库主页上的“代码”下拉菜单,然后单击“使用 SSH” 。 +Anyone with read access to the repository can find this URL by selecting the **Code** dropdown menu on the main page of the repository, then clicking **Use SSH**. -如果您的组织不需要 SSH 证书,则成员可以继续使用自己的 SSH 密钥或其他身份验证方式。 在这种情况下,特殊 URL 或以 `git@github.com` 开头的正常 URL 将起作用。 +If your organization doesn't require SSH certificates, members can continue to use their own SSH keys, or other means of authentication. In that case, either the special URL or the normal URL, which starts with `git@github.com`, will work. -## 颁发证书 +## Issuing certificates -在颁发每个证书时,必须包含扩展,以指定证书用于哪个 {% data variables.product.product_name %} 用户。 例如,你可以使用 OpenSSH 的 `ssh-keygen` 命令,将 _KEY-IDENTITY_ 替换为密钥标识,_USERNAME_ 替换为 {% data variables.product.product_name %} 用户名。 您生成的证书将授权代表该用户使用您组织的任何资源。 在签发证书之前,请确保验证用户的身份。 +When you issue each certificate, you must include an extension that specifies which {% data variables.product.product_name %} user the certificate is for. For example, you can use OpenSSH's `ssh-keygen` command, replacing _KEY-IDENTITY_ with your key identity and _USERNAME_ with a {% data variables.product.product_name %} username. The certificate you generate will be authorized to act on behalf of that user for any of your organization's resources. Make sure you validate the user's identity before you issue the certificate. {% note %} -注意:必须更新到 OpenSSH 7.6 或更高版本才能使用这些命令。 +**Note:** You must update to OpenSSH 7.6 or later to use these commands. {% endnote %} ```shell -$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME ./user-key.pub +$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME ./user-key.pub ``` {% warning %} -警告:证书签名并颁发后,无法吊销。 请确保使用 -`V` 标志来配置证书的生存期,否则证书可以无限期使用。 +**Warning**: After a certificate has been signed and issued, the certificate cannot be revoked. Make sure to use the -`V` flag to configure a lifetime for the certificate, or the certificate can be used indefinitely. {% endwarning %} -要为使用 SSH 访问多个 {% data variables.product.company_short %} 产品的人颁发证书,您可以包括两个登录扩展,以指定每个产品的用户名。 例如,以下命令将为 {% data variables.product.prodname_ghe_cloud %} 的用户帐户颁发 _USERNAME-1_ 的证书,为 _HOSTNAME_ 处的 {% data variables.product.prodname_ghe_managed %} 或 {% data variables.product.prodname_ghe_server %} 上的用户帐户颁发 _USERNAME-2_ 的证书。 +To issue a certificate for someone who uses SSH to access multiple {% data variables.product.company_short %} products, you can include two login extensions to specify the username for each product. For example, the following command would issue a certificate for _USERNAME-1_ for the user's account for {% data variables.product.prodname_ghe_cloud %}, and _USERNAME-2_ for the user's account on {% data variables.product.prodname_ghe_managed %} or {% data variables.product.prodname_ghe_server %} at _HOSTNAME_. ```shell -$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@github.com=USERNAME-1 extension:login@HOSTNAME=USERNAME-2 ./user-key.pub +$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@github.com=USERNAME-1 extension:login@HOSTNAME=USERNAME-2 ./user-key.pub ``` -可以使用 `source-address` 扩展来限制组织成员用来访问组织资源的 IP 地址。 扩展接受采用 CIDR 表示法的特定 IP 地址或一个 IP 地址范围。 您可以指定多个地址或范围,用逗号分隔值。 有关详细信息,请参阅 Wikipedia 上的“[无类别域际路由](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)”。 +You can restrict the IP addresses from which an organization member can access your organization's resources by using a `source-address` extension. The extension accepts a specific IP address or a range of IP addresses using CIDR notation. You can specify multiple addresses or ranges by separating the values with commas. For more information, see "[Classless Inter-Domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)" on Wikipedia. ```shell -$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME -O source-address=COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES ./user-key.pub +$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME -O source-address=COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES ./user-key.pub ``` diff --git a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md index 889f6f9bb9..3228b6aa3f 100644 --- a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md @@ -1,6 +1,6 @@ --- -title: Inviting users to join your organization(邀请用户加入你的组织) -intro: '您可以使用任何人的 {% data variables.product.product_location %} 用户名或电子邮件地址邀请他们成为您组织的成员。' +title: Inviting users to join your organization +intro: 'You can invite anyone to become a member of your organization using their username or email address for {% data variables.location.product_location %}.' permissions: Organization owners can invite users to join an organization. redirect_from: - /articles/adding-or-inviting-members-to-a-team-in-an-organization @@ -13,26 +13,30 @@ topics: - Organizations - Teams shortTitle: Invite users to join -ms.openlocfilehash: f0b5d1c41fc5f348077a77d29ac4be309c1cad0f -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145097336' --- -## 关于组织邀请 -如果您的组织采用付费的每用户订阅,则必须有未使用的许可才可邀请新成员加入组织或恢复前组织成员。 有关详细信息,请参阅“[关于每用户定价](/articles/about-per-user-pricing)”。 +## About organization invitations + +If your organization has a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." {% data reusables.organizations.org-invite-scim %} -如果您的组织要求成员使用双重身份验证,则您邀请的用户在接受邀请之前必须启用双重身份验证。 有关详细信息,请参阅“[要求在组织中进行双因素身份验证](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)”和“[使用双因素身份验证 (2FA) 保护帐户](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)”。 +If your organization requires members to use two-factor authentication, users that you invite must enable two-factor authentication before accepting the invitation. For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)" and "[Securing your account with two-factor authentication (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)." -{% ifversion fpt %}使用 {% data variables.product.prodname_ghe_cloud %}{% else %}您{% endif %} 的组织可以实施 SCIM,以添加、管理和删除组织成员通过身份提供商 (IdP) 对 {% data variables.product.prodname_dotcom_the_website %} 的访问权限。 有关详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[关于组织的 SCIM](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations){% ifversion fpt %}”。{% else %}."{% endif %} +{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% else %}You{% endif %} can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.prodname_dotcom_the_website %} through an identity provider (IdP). For more information, see "[About SCIM for organizations](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} -## 邀请用户加入您的组织 +## Inviting a user to join your organization -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %} {% data reusables.organizations.invite_member_from_people_tab %} {% data reusables.organizations.invite_to_org %} {% data reusables.organizations.choose-to-restore-privileges %} {% data reusables.organizations.choose-user-role %} {% data reusables.organizations.add-user-to-teams %} {% data reusables.organizations.send-invitation %} {% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.people %} +{% data reusables.organizations.invite_member_from_people_tab %} +{% data reusables.organizations.invite_to_org %} +{% data reusables.organizations.choose-to-restore-privileges %} +{% data reusables.organizations.choose-user-role %} +{% data reusables.organizations.add-user-to-teams %} +{% data reusables.organizations.send-invitation %} +{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %} -## 延伸阅读 -- “[将组织成员添加到团队](/articles/adding-organization-members-to-a-team)” +## Further reading +- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)" diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md index 22a04ad897..88ff35d2d9 100644 --- a/translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md +++ b/translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md @@ -1,6 +1,6 @@ --- -title: 删除组织帐户 -intro: '删除组织时,所有仓库、私有仓库复刻、wiki、议题、拉取请求和项目或组织页面也被删除。 {% ifversion fpt or ghec %}您的结算将结束,90 天后,组织名称将可用于新的用户或组织帐户。{% endif %}' +title: Deleting an organization account +intro: 'When you delete an organization, all repositories, forks of private repositories, wikis, issues, pull requests, and Project or Organization Pages are deleted as well. {% ifversion fpt or ghec %}Your billing will end, and after 90 days the organization name becomes available for use on a new user or organization account.{% endif %}' redirect_from: - /articles/deleting-an-organization-account - /github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account @@ -13,33 +13,32 @@ topics: - Organizations - Teams shortTitle: Delete organization -ms.openlocfilehash: e923dcf7fb9135243c5bfe0e68a310719e87ef2e -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/12/2022 -ms.locfileid: '147886764' --- -{% ifversion fpt or ghec %} {% tip %} -提示:如果要取消已付费的订阅,可以[将组织降级到 {% data variables.product.prodname_free_team %}](/articles/downgrading-your-github-subscription),而不是删除组织及其内容。 +{% ifversion fpt or ghec %} +{% tip %} + +**Tip**: If you want to cancel your paid subscription, you can [downgrade your organization to {% data variables.product.prodname_free_team %}](/articles/downgrading-your-github-subscription) instead of deleting the organization and its content. {% endtip %} {% endif %} -## 1. 备份组织内容 +## 1. Back up your organization content -{% ifversion not ghes %} 删除组织后,{% data variables.product.company_short %} 无法恢复内容。 因此,在删除组织{% else %}之前{% endif %},请确保您拥有该帐户中所有仓库、wiki、议题和项目板的副本。 +{% ifversion not ghes %} After you delete an organization, {% data variables.product.company_short %} **cannot restore your content**. Therefore, before{% else %}Before{% endif %} you delete your organization, make sure you have a copy of all repositories, wikis, issues, and project boards from the account. -{% ifversion ghes %} {% note %} +{% ifversion ghes %} +{% note %} -注意:如有必要,{% data variables.product.product_location %} 的站点管理员或能部分恢复已删除的组织。 有关详细信息,请参阅“[恢复已删除的组织](/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization)”。 +**Note:** If necessary, a site administrator for {% data variables.location.product_location %} may be able to partially restore a deleted organization. For more information, see "[Restoring a deleted organization](/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization)." -{% endnote %} {% endif %} +{% endnote %} +{% endif %} -## 2. 删除组织 +## 2. Delete the organization -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -4. 在组织设置页面底部附近,单击“删除此组织”。 - ![“删除此组织”按钮](/assets/images/help/settings/settings-organization-delete.png) +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +4. Near the bottom of the organization's settings page, click **Delete this Organization**. + ![Delete this organization button](/assets/images/help/settings/settings-organization-delete.png) diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md index 72a939d693..b181ccd22b 100644 --- a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md @@ -1,6 +1,6 @@ --- -title: 管理组织中仓库的默认分支名称 -intro: '可以为成员在 {% data variables.product.product_location %} 上的组织中创建的存储库设置默认分支名称。' +title: Managing the default branch name for repositories in your organization +intro: 'You can set the default branch name for repositories that members create in your organization on {% data variables.location.product_location %}.' redirect_from: - /github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization permissions: Organization owners can manage the default branch name for new repositories in the organization. @@ -13,31 +13,28 @@ topics: - Organizations - Teams shortTitle: Manage default branch name -ms.openlocfilehash: 38bd35506728f4437c9a1644235fe748c6a8a58a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145099719' --- -## About the default branch name -当组织成员在组织中创建一个新仓库时,该仓库将包含一个分支,它就是默认分支。 可以更改 {% data variables.product.product_name %} 用于组织成员创建的新存储库中的默认分支的名称。 有关默认分支的详细信息,请参阅“[关于分支](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)”。 +## About management of the default branch name + +When a member of your organization creates a new repository in your organization, the repository contains one branch, which is the default branch. You can change the name that {% data variables.product.product_name %} uses for the default branch in new repositories that members of your organization create. For more information about the default branch, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)." {% data reusables.branches.change-default-branch %} -如果企业所有者为您的企业强制实施了默认分支名称策略,您将无法为组织设置默认分支名称。 但是,您可以更改单个仓库的默认分支。 有关详细信息,请参阅 {% ifversion fpt %}“[在企业中强制实施存储库管理策略](/enterprise-cloud@latest/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)”{% else %}“[在企业中强制实施存储库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)”{% endif %}和“[更改默认分支](/github/administering-a-repository/changing-the-default-branch)”。 +If an enterprise owner has enforced a policy for the default branch name for your enterprise, you cannot set a default branch name for your organization. Instead, you can change the default branch for individual repositories. For more information, see {% ifversion fpt %}"[Enforcing repository management policies in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)"{% else %}"[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)"{% endif %} and "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)." -## 设置默认分支名称 +## Setting the default branch name -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.repository-defaults %} -3. 在“存储库默认分支”下,单击“立即更改默认分支名称”。 - ![“替代”按钮](/assets/images/help/organizations/repo-default-name-button.png) -4. 键入要用于新分支的默认名称。 - ![用于输入默认名称的文本框](/assets/images/help/organizations/repo-default-name-text.png) -5. 单击“更新”。 - ![“更新”按钮](/assets/images/help/organizations/repo-default-name-update.png) +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +{% data reusables.organizations.repository-defaults %} +3. Under "Repository default branch", click **Change default branch name now**. + ![Override button](/assets/images/help/organizations/repo-default-name-button.png) +4. Type the default name that you would like to use for new branches. + ![Text box for entering default name](/assets/images/help/organizations/repo-default-name-text.png) +5. Click **Update**. + ![Update button](/assets/images/help/organizations/repo-default-name-update.png) -## 延伸阅读 +## Further reading -- “[管理存储库的默认分支名称](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)” +- "[Managing the default branch name for your repositories](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)" diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index 7aa152a6c8..a6056acced 100644 --- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- -title: 关于使用 SAML 单一登录进行的标识和访问管理 -intro: '如果您使用身份提供程序 (IdP) 集中管理用户身份和应用程序,可以配置安全声明标记语言 (SAML) 单点登录 (SSO) 来保护组织在 {% data variables.product.prodname_dotcom %} 上的资源。' +title: About identity and access management with SAML single sign-on +intro: 'If you centrally manage your users'' identities and applications with an identity provider (IdP), you can configure Security Assertion Markup Language (SAML) single sign-on (SSO) to protect your organization''s resources on {% data variables.product.prodname_dotcom %}.' redirect_from: - /articles/about-identity-and-access-management-with-saml-single-sign-on - /github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on @@ -10,63 +10,58 @@ topics: - Organizations - Teams shortTitle: IAM with SAML SSO -ms.openlocfilehash: 509baaf6d9c47295b57d35dfef7d5c65923b6e3c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147526660' --- + {% data reusables.saml.ghec-only %} -## 关于 SAML SSO +## About SAML SSO {% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.saml-accounts %} -组织所有者可以对单个组织强制实施 SAML SSO,企业所有者可以为企业帐户中的所有组织强制实施 SAML SSO。 有关详细信息,请参阅“[为企业配置 SAML 单一登录](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)”。 +Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)." {% data reusables.saml.outside-collaborators-exemption %} -在为您的组织启用 SAML SSO 之前,您需要将 IdP 连接到组织。 有关详细信息,请参阅“[将标识提供者连接到组织](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)”。 +Before enabling SAML SSO for your organization, you'll need to connect your IdP to your organization. For more information, see "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)." -对于组织,SAML SSO 可以禁用、启用但不实施或者启用并实施。 为组织启用 SAML SSO 并且组织成员使用 IdP 成功完成身份验证后,您可以实施 SAML SSO 配置。 有关为 {% data variables.product.prodname_dotcom %} 组织强制实施 SAML SSO 的更多信息,请参阅“[为组织强制实施 SAML 单一登录](/articles/enforcing-saml-single-sign-on-for-your-organization)”。 +For an organization, SAML SSO can be disabled, enabled but not enforced, or enabled and enforced. After you enable SAML SSO for your organization and your organization's members successfully authenticate with your IdP, you can enforce the SAML SSO configuration. For more information about enforcing SAML SSO for your {% data variables.product.prodname_dotcom %} organization, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)." -成员必须定期使用您的 IdP 进行身份验证,以获得对组织资源的访问权限。 此登录期的持续时间由 IdP 指定,一般为 24 小时。 此定期登录要求会限制访问的时长,您必须重新验证身份后才可继续访问。 +Members must periodically authenticate with your IdP to authenticate and gain access to your organization's resources. The duration of this login period is specified by your IdP and is generally 24 hours. This periodic login requirement limits the length of access and requires users to re-identify themselves to continue. -要在命令行使用 API 和 Git 访问组织受保护的资源,成员必须授权并使用个人访问令牌或 SSH 密钥验证身份。 有关详细信息,请参阅“[授权用于 SAML 单一登录的个人访问令牌](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)”和“[授权用于 SAML 单一登录的 SSH 密钥](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)”。 +To access the organization's protected resources using the API and Git on the command line, members must authorize and authenticate with a {% data variables.product.pat_generic %} or SSH key. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." -成员第一次使用 SAML SSO 访问您的组织时,{% data variables.product.prodname_dotcom %} 会自动创建一条记录,以链接您的组织、成员在 {% data variables.product.product_location %} 上的帐户以及成员在 IdP 上的帐户。 您可以查看和撤销组织成员或企业帐户关联的 SAML 身份、活动的会话以及授权的凭据。 有关详细信息,请参阅“[查看和管理成员对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)”和“[查看和管理用户对企业帐户的 SAML 访问](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)”。 +The first time a member uses SAML SSO to access your organization, {% data variables.product.prodname_dotcom %} automatically creates a record that links your organization, the member's account on {% data variables.location.product_location %}, and the member's account on your IdP. You can view and revoke the linked SAML identity, active sessions, and authorized credentials for members of your organization or enterprise account. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" and "[Viewing and managing a user's SAML access to your enterprise account](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)." -如果成员在创建新的仓库时使用 SAML SSO 会话登录,则该仓库的默认可见性为私密。 否则,默认可见性为公开。 有关存储库可见性的详细信息,请参阅“[关于存储库](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)”。 +If members are signed in with a SAML SSO session when they create a new repository, the default visibility of that repository is private. Otherwise, the default visibility is public. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." -组织成员还必须具有活动的 SAML 会话才可授权 {% data variables.product.prodname_oauth_app %}。 您可以联系 {% data variables.contact.contact_support %} 选择退出此要求。 {% data variables.product.product_name %} 不建议退出此要求,因为它会使您的组织面临更高的帐户接管风险和潜在的数据丢失风险。 +Organization members must also have an active SAML session to authorize an {% data variables.product.prodname_oauth_app %}. You can opt out of this requirement by contacting {% data variables.contact.contact_support %}. {% data variables.product.product_name %} does not recommend opting out of this requirement, which will expose your organization to a higher risk of account takeovers and potential data loss. {% data reusables.saml.saml-single-logout-not-supported %} -## 支持的 SAML 服务 +## Supported SAML services {% data reusables.saml.saml-supported-idps %} -有些 IdP 支持配置通过 SCIM 访问 {% data variables.product.prodname_dotcom %} 组织。 有关详细信息,请参阅“[关于组织的 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)”。 +Some IdPs support provisioning access to a {% data variables.product.prodname_dotcom %} organization via SCIM. For more information, see "[About SCIM for organizations](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)." {% data reusables.scim.enterprise-account-scim %} -## 使用 SAML SSO 添加成员到组织 +## Adding members to an organization using SAML SSO -启用 SAML SSO 后,可以通过多种方式向组织添加新成员。 组织所有者可在 {% data variables.product.product_name %} 上或使用 API 手动邀请新成员。 有关详细信息,请参阅“[邀请用户加入你的组织](/articles/inviting-users-to-join-your-organization)”和“[成员](/rest/reference/orgs#add-or-update-organization-membership)”。 +After you enable SAML SSO, there are multiple ways you can add new members to your organization. Organization owners can invite new members manually on {% data variables.product.product_name %} or using the API. For more information, see "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)" and "[Members](/rest/reference/orgs#add-or-update-organization-membership)." -若要在没有组织所有者邀请的情况下预配新用户,可使用 URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`,并将“ORGANIZATION”替换为你的组织名称。 例如,您可以配置 IdP,让能访问 IdP 的任何人都可单击 IdP 仪表板上的链接加入 {% data variables.product.prodname_dotcom %} 组织。 +To provision new users without an invitation from an organization owner, you can use the URL `https://github.com/orgs/ORGANIZATION/sso/sign_up`, replacing _ORGANIZATION_ with the name of your organization. For example, you can configure your IdP so that anyone with access to the IdP can click a link on the IdP's dashboard to join your {% data variables.product.prodname_dotcom %} organization. -如果您的 IdP 支持 SCIM,当您在 IdP 上授予访问权限时,{% data variables.product.prodname_dotcom %} 可以自动邀请成员加入您的组织。 如果您删除成员对 SAML IdP 上 {% data variables.product.prodname_dotcom %} 组织的访问权限,该成员将自动从 {% data variables.product.prodname_dotcom %} 组织删除。 有关详细信息,请参阅“[关于组织的 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)”。 +If your IdP supports SCIM, {% data variables.product.prodname_dotcom %} can automatically invite members to join your organization when you grant access on your IdP. If you remove a member's access to your {% data variables.product.prodname_dotcom %} organization on your SAML IdP, the member will be automatically removed from the {% data variables.product.prodname_dotcom %} organization. For more information, see "[About SCIM for organizations](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)." {% data reusables.organizations.team-synchronization %} {% data reusables.saml.saml-single-logout-not-supported %} -## 延伸阅读 +## Further reading -- “[SAML 配置参考](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference)” -- “[关于双因素身份验证和 SAML 单一登录](/articles/about-two-factor-authentication-and-saml-single-sign-on)” -- “[关于使用 SAML 单一登录进行身份验证](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)” +- "[SAML configuration reference](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference)" +- "[About two-factor authentication and SAML single sign-on ](/articles/about-two-factor-authentication-and-saml-single-sign-on)" +- "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md index f2d207ecca..ce04ec7d36 100644 --- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md @@ -1,6 +1,6 @@ --- -title: 使用 Octa 配置 SAML 单个登录和 SCIM -intro: '可以使用安全断言标记语言 (SAML) 单一登录 (SSO) 和跨域身份管理系统 (SCIM) 与 Okta 一起来自动管理对 {% data variables.product.product_location %} 上组织的访问。' +title: Configuring SAML single sign-on and SCIM using Okta +intro: 'You can use Security Assertion Markup Language (SAML) single sign-on (SSO) and System for Cross-domain Identity Management (SCIM) with Okta to automatically manage access to your organization on {% data variables.location.product_location %}.' redirect_from: - /github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta permissions: Organization owners can configure SAML SSO and SCIM using Okta for an organization. @@ -10,54 +10,55 @@ topics: - Organizations - Teams shortTitle: Configure SAML & SCIM with Okta -ms.openlocfilehash: 3b1083e0ec9d792de9e9c1e83cd5b000e8261905 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147883277' --- -## 关于 SAML 和 SCIM 与 Octa -通过将组织配置为将 SAML SSO 和 SCIM 与身份提供程序 (IdP) Okta 结合使用,您可以从一个中心界面控制对您 {% data variables.product.product_location %} 和其他 Web 应用程序上的组织的访问。 +## About SAML and SCIM with Okta + +You can control access to your organization on {% data variables.location.product_location %} and other web applications from one central interface by configuring the organization to use SAML SSO and SCIM with Okta, an Identity Provider (IdP). {% data reusables.saml.ghec-only %} -SAML SSO 控制并保护对组织资源(如仓库、议题和拉取请求)的访问。 当您在 Okta 中进行更改时,SCIM 会自动添加、管理和删除成员对您在 {% data variables.product.product_location %} 上的组织的访问权限。 有关详细信息,请参阅“[关于使用 SAML 单一登录进行标识和访问管理](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)”和“[关于组织的 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)”。 +SAML SSO controls and secures access to organization resources like repositories, issues, and pull requests. SCIM automatically adds, manages, and removes members' access to your organization on {% data variables.location.product_location %} when you make changes in Okta. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)" and "[About SCIM for organizations](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)." -启用 SCIM 后,您在 Okta 中为其分配了 {% data variables.product.prodname_ghe_cloud %} 应用程序的任何用户都可以使用以下配置。 +After you enable SCIM, the following provisioning features are available for any users that you assign your {% data variables.product.prodname_ghe_cloud %} application to in Okta. -| 功能 | 说明 | +| Feature | Description | | --- | --- | -| 推送新用户 | 当您在 Okta 中创建新用户时,该用户将收到一封电子邮件,要求您在 {% data variables.product.product_location %} 上加入您的组织。 | -| 推送用户停用 | 当您在 Okta 中停用用户时,Okta 将从您在 {% data variables.product.product_location %} 上的组织中删除该用户。 | -| 推送个人资料更新 | 当您在 Okta 中更新用户的个人资料时,Okta 将更新您在 {% data variables.product.product_location %} 上的组织中该用户成员身份的元数据。 | -| 重新激活用户 | 当您在 Okta 中重新激活用户时,Okta 将发送电子邮件邀请该用户在 {% data variables.product.product_location %} 上重新加入您的组织。 | +| Push New Users | When you create a new user in Okta, the user will receive an email to join your organization on {% data variables.location.product_location %}. | +| Push User Deactivation | When you deactivate a user in Okta, Okta will remove the user from your organization on {% data variables.location.product_location %}. | +| Push Profile Updates | When you update a user's profile in Okta, Okta will update the metadata for the user's membership in your organization on {% data variables.location.product_location %}. | +| Reactivate Users | When you reactivate a user in Okta, Okta will send an email invitation for the user to rejoin your organization on {% data variables.location.product_location %}. | -或者,您可以使用 Okta 为企业配置 SAML SSO。 适用于企业帐户的 SCIM 仅适用于企业托管用户。 有关详细信息,请参阅“[使用 Okta 为企业配置 SAML 单一登录](/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)”和“[使用 Okta 为企业托管用户配置 SCIM 配置](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users-with-okta)”。 +Alternatively, you can configure SAML SSO for an enterprise using Okta. SCIM for enterprise accounts is only available with Enterprise Managed Users. For more information, see "[Configuring SAML single sign-on for your enterprise using Okta](/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)" and "[Configuring SCIM provisioning for Enterprise Managed Users with Okta](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users-with-okta)." -## 在 Okta 中添加 {% data variables.product.prodname_ghe_cloud %} 应用程序 +## Adding the {% data variables.product.prodname_ghe_cloud %} application in Okta -{% data reusables.saml.okta-sign-on-tab %} {% data reusables.saml.okta-view-setup-instructions %} -1. 按照“如何配置 SAML 2.0”指南,使用登录 URL、发行机构 URL 和公共证书在 {% data variables.product.prodname_dotcom %} 上启用并测试 SAML SSO。 有关详细信息,请参阅“[为组织启用和测试 SAML 单一登录](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization#enabling-and-testing-saml-single-sign-on-for-your-organization)”。 +{% data reusables.saml.okta-sign-on-tab %} +{% data reusables.saml.okta-view-setup-instructions %} +1. Enable and test SAML SSO on {% data variables.product.prodname_dotcom %} using the sign on URL, issuer URL, and public certificates from the "How to Configure SAML 2.0" guide. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization#enabling-and-testing-saml-single-sign-on-for-your-organization)." -## 在 Okta 中使用 SCIM 配置访问配置 +## Configuring access provisioning with SCIM in Okta {% data reusables.scim.dedicated-configuration-account %} -1. 使用组织所有者的帐户登录到 {% data variables.product.prodname_dotcom_the_website %},理想情况下仅用于 SCIM 配置。 -1. 若要为组织创建活动的 SAML 会话,请导航到 `https://github.com/orgs/ORGANIZATION-NAME/sso`。 有关详细信息,请参阅“[关于通过 SAML 单一登录进行身份验证](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on#about-oauth-apps-github-apps-and-saml-sso)”。 -1. 导航到 Okta。 -{% data reusables.saml.okta-dashboard-click-applications %} {% data reusables.saml.okta-applications-click-ghec-application-label %} {% data reusables.saml.okta-provisioning-tab %} {% data reusables.saml.okta-configure-api-integration %} {% data reusables.saml.okta-enable-api-integration %} -1. 单击“使用 {% data variables.product.prodname_ghe_cloud %} 进行身份验证 - 组织”。 -1. 在组织名称右侧,单击“授权”。 +1. Sign into {% data variables.product.prodname_dotcom_the_website %} using an account that is an organization owner and is ideally used only for SCIM configuration. +1. To create an active SAML session for your organization, navigate to `https://github.com/orgs/ORGANIZATION-NAME/sso`. For more information, see "[About authentication with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on#about-oauth-apps-github-apps-and-saml-sso)." +1. Navigate to Okta. +{% data reusables.saml.okta-dashboard-click-applications %} +{% data reusables.saml.okta-applications-click-ghec-application-label %} +{% data reusables.saml.okta-provisioning-tab %} +{% data reusables.saml.okta-configure-api-integration %} +{% data reusables.saml.okta-enable-api-integration %} +1. Click **Authenticate with {% data variables.product.prodname_ghe_cloud %} - Organization**. +1. To the right of your organization's name, click **Grant**. - ![用于授权 Okta SCIM 集成访问组织的“授权”按钮](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png) -1. 单击“授权 OktaOAN”。 -{% data reusables.saml.okta-save-provisioning %} {% data reusables.saml.okta-edit-provisioning %} + !["Grant" button for authorizing Okta SCIM integration to access organization](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png) +1. Click **Authorize OktaOAN**. +{% data reusables.saml.okta-save-provisioning %} +{% data reusables.saml.okta-edit-provisioning %} -## 延伸阅读 +## Further reading -- “[使用 Okta 为企业帐户配置 SAML 单一登录](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)” -- 在 Okta 文档中[了解 SAML](https://developer.okta.com/docs/concepts/saml/) -- 在 Okta 文档中[了解 SCIM](https://developer.okta.com/docs/concepts/scim/) +- "[Configuring SAML single sign-on for your enterprise account using Okta](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)" +- [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) in the Okta documentation +- [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) in the Okta documentation diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md index 7c5a0f11c4..02c9f5a658 100644 --- a/translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md @@ -1,6 +1,6 @@ --- -title: 关于团队 -intro: 团队是组织成员构成的小组,反映了公司或小组具有级联访问权限和提及功能的结构。 +title: About teams +intro: Teams are groups of organization members that reflect your company or group's structure with cascading access permissions and mentions. redirect_from: - /articles/about-teams - /github/setting-up-and-managing-organizations-and-teams/about-teams @@ -12,76 +12,71 @@ versions: topics: - Organizations - Teams -ms.openlocfilehash: 7b899cf08ca58170acdf8fb2fb2ad13d251b76e3 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145149843' --- -![组织中的团队列表](/assets/images/help/teams/org-list-of-teams.png) -组织所有者和团队维护员可向团队授予对组织存储库的管理、读取或写权限。 组织成员可通过提及团队的名称,向整个团队发送通知。 此外,组织成员可通过请求团队评审,向整个团队发送通知。 组织成员组可请求有权读取打开拉取请求的存储库的特定团队进行评审。 可在 CODEOWNERS 文件中将团队指定为某些代码类型或区域的所有者。 +![List of teams in an organization](/assets/images/help/teams/org-list-of-teams.png) -有关详细信息,请参阅: -- “[管理团队对组织存储库的访问](/articles/managing-team-access-to-an-organization-repository)” -- “[提及人员和团队](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)” -- “[关于代码所有者](/articles/about-code-owners/)” +Organization owners and team maintainers can give teams admin, read, or write access to organization repositories. Organization members can send a notification to an entire team by mentioning the team's name. Organization members can also send a notification to an entire team by requesting a review from that team. Organization members can request reviews from specific teams with read access to the repository where the pull request is opened. Teams can be designated as owners of certain types or areas of code in a CODEOWNERS file. -![团队提及图像](/assets/images/help/teams/team-mention.png) +For more information, see: +- "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)" +- "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)" +- "[About code owners](/articles/about-code-owners/)" + +![Image of a team mention](/assets/images/help/teams/team-mention.png) {% ifversion ghes %} -还可以使用 LDAP 同步根据确定的 LDAP 组同步 {% data variables.product.product_location %} 团队成员和团队角色。 这使你能够从 LDAP 服务器为用户建立基于角色的访问控制,而不是在 {% data variables.product.product_location %} 中手动建立。 有关详细信息,请参阅“[启用 LDAP 同步](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync)”。 +You can also use LDAP Sync to synchronize {% data variables.location.product_location %} team members and team roles against your established LDAP groups. This lets you establish role-based access control for users from your LDAP server instead of manually within {% data variables.location.product_location %}. For more information, see "[Enabling LDAP Sync](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync)." {% endif %} {% data reusables.organizations.team-synchronization %} -## 团队可见性 +## Team visibility {% data reusables.organizations.types-of-team-visibility %} -您可以在个人仪表板上查看您所属的所有团队。 有关详细信息,请参阅“[关于个人仪表板](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#finding-your-top-repositories-and-teams)”。 +You can view all the teams you belong to on your personal dashboard. For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#finding-your-top-repositories-and-teams)." -## 团队页面 +## Team pages -每个团队都在组织中有自己的页面。 在团队的页面上,您可以查看团队成员、子团队和团队的仓库。 组织所有者和团队维护员可从团队页面访问团队设置以及更新团队的说明和头像。 +Each team has its own page within an organization. On a team's page, you can view team members, child teams, and the team's repositories. Organization owners and team maintainers can access team settings and update the team's description and profile picture from the team's page. -组织成员可以创建和参与团队讨论。 有关详细信息,请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”。 +Organization members can create and participate in discussions with the team. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)." -![列出团队成员和讨论的团队页面](/assets/images/help/organizations/team-page-discussions-tab.png) +![Team page listing team members and discussions](/assets/images/help/organizations/team-page-discussions-tab.png) -## 嵌套团队 +## Nested teams -您可以在 {% data variables.product.product_name %} 组织中通过多级嵌套团队反映您的组或公司的层级。 父级团队可具有多个子级团队,而每个子级团队只有一个父级团队。 不可嵌套机密团队。 +You can reflect your group or company's hierarchy within your {% data variables.product.product_name %} organization with multiple levels of nested teams. A parent team can have multiple child teams, while each child team only has one parent team. You cannot nest secret teams. -子级团队会继承父级团队的访问权限,这简化了大型组的权限管理。 当父团队被 @提及时,子团队的成员也会收到通知,这简化了与多组人员的通信。 +Child teams inherit the parent's access permissions, simplifying permissions management for large groups. Members of child teams also receive notifications when the parent team is @mentioned, simplifying communication with multiple groups of people. -例如,如果您的团队结构是“员工 > 工程 > 应用工程 > 身份”,则向“工程”授予对仓库的写入权限意味着“应用工程”和“身份”也会获得该访问权限。 如果你 @提及标识团队或组织层次结构底部的任何团队,则它们将是唯一会收到通知的团队。 +For example, if your team structure is Employees > Engineering > Application Engineering > Identity, granting Engineering write access to a repository means Application Engineering and Identity also get that access. If you @mention the Identity Team or any team at the bottom of the organization hierarchy, they're the only ones who will receive a notification. -![包含父团队和子团队的团队页面](/assets/images/help/teams/nested-teams-eng-example.png) +![Teams page with a parent team and child teams](/assets/images/help/teams/nested-teams-eng-example.png) -要轻松了解谁共享父团队的权限和提及,可以在父团队页面的 Members(成员)选项卡上查看其子团队的所有成员。 子团队的成员不是父团队的直接成员。 +To easily understand who shares a parent team's permissions and mentions, you can see all of the members of a parent team's child teams on the Members tab of the parent team's page. Members of a child team are not direct members of the parent team. -![包含子团队所有成员的父团队页面](/assets/images/help/teams/team-and-subteam-members.png) +![Parent team page with all members of child teams](/assets/images/help/teams/team-and-subteam-members.png) -在创建团队时您可以选择父团队,或者以后在组织的层次结构中移动团队。 有关详细信息,请参阅“[在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy)”。 +You can choose a parent when you create the team, or you can move a team in your organization's hierarchy later. For more information see, "[Moving a team in your organization’s hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy)." {% data reusables.enterprise_user_management.ldap-sync-nested-teams %} -## 准备在组织中嵌套团队 +## Preparing to nest teams in your organization -如果您的组织已经有团队,则在其上面或下面嵌套团队之前,应审计每个团队的仓库访问权限。 也应考虑要为组织实施的新结构。 +If your organization already has existing teams, you should audit each team's repository access permissions before you nest teams above or below it. You should also consider the new structure you'd like to implement for your organization. -在团队层次结构的顶部,应向父团队授予对父团队及其子团队每个成员都安全的仓库访问权限。 随着在向层次结构底部的移动,可以更细致地向子团队成员授予访问敏感仓库的其他权限。 +At the top of the team hierarchy, you should give parent teams repository access permissions that are safe for every member of the parent team and its child teams. As you move toward the bottom of the hierarchy, you can grant child teams additional, more granular access to more sensitive repositories. -1. 从现有团队删除所有成员 -2. 审计并调整每个团队的仓库访问权限,并为每个团队指定一个父团队 -3. 创建需要的任何新团队,为每个新团队选择一个父团队,并向他们授予仓库访问权限 -4. 直接向团队添加人员 +1. Remove all members from existing teams +2. Audit and adjust each team's repository access permissions and give each team a parent +3. Create any new teams you'd like to, choose a parent for each new team, and give them repository access +4. Add people directly to teams -## 延伸阅读 +## Further reading -- “[创建团队](/articles/creating-a-team)” -- “[将组织成员添加到团队](/articles/adding-organization-members-to-a-team)” +- "[Creating a team](/articles/creating-a-team)" +- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)" diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md index 8b3ff99a7f..e4b9dcfbf5 100644 --- a/translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -1,6 +1,6 @@ --- -title: 将团队与身份提供程序组同步 -intro: '你可以将 {% data variables.product.product_name %} 团队与支持的标识提供者 (IdP) 组同步,以自动添加和删除团队成员。' +title: Synchronizing a team with an identity provider group +intro: 'You can synchronize a {% data variables.product.product_name %} team with a supported identity provider (IdP) group to automatically add and remove team members.' redirect_from: - /github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group permissions: 'Organization owners and team maintainers can synchronize a {% data variables.product.prodname_dotcom %} team with an IdP group.' @@ -11,85 +11,94 @@ topics: - Organizations - Teams shortTitle: Synchronize with an IdP -ms.openlocfilehash: 5ae57399a05f51334ccd3e99a268fbe9d93c8b47 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147076885' --- + {% data reusables.enterprise-accounts.emu-scim-note %} -## 关于团队同步 +## About team synchronization {% data reusables.identity-and-permissions.about-team-sync %} -{% ifversion ghec %}您可以将最多 5 个 IdP 组连接到 {% data variables.product.product_name %} 团队。{% elsif ghae %}您可以将 {% data variables.product.product_name %} 上的团队连接到一个 IdP 组。 组中的所有用户将自动添加到团队中,并作为成员添加到父组织。 当您断开组与团队的连接时,通过团队成员资格成为组织成员的用户将从组织中删除。{% endif %} 您可以将 IdP 组分配给多个 {% data variables.product.product_name %} 团队。 +{% ifversion ghec %}You can connect up to five IdP groups to a {% data variables.product.product_name %} team.{% elsif ghae %}You can connect a team on {% data variables.product.product_name %} to one IdP group. All users in the group are automatically added to the team and also added to the parent organization as members. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization.{% endif %} You can assign an IdP group to multiple {% data variables.product.product_name %} teams. -{% ifversion ghec %}团队同步不支持超过 5000 个成员的 IdP 组。{% endif %} +{% ifversion ghec %}Team synchronization does not support IdP groups with more than 5000 members.{% endif %} -{% data variables.product.prodname_dotcom %} 团队连接到 IdP 组后,您的 IdP 管理员必须通过身份提供程序进行团队成员资格更改。 您不能在 {% data variables.product.product_name %} 上{% ifversion ghec %}或使用 API{% endif %} 管理团队成员资格。 +Once a {% data variables.product.prodname_dotcom %} team is connected to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.product_name %}{% ifversion ghec %} or using the API{% endif %}. {% ifversion ghec %}{% data reusables.enterprise-accounts.team-sync-override %}{% endif %} -{% ifversion ghec %} 通过 IdP 进行的所有团队成员资格更改都将在 {% data variables.product.product_name %} 的审核日志中显示为团队同步机器人所进行的更改。 您的 IdP 会将团队成员数据发送至 {% data variables.product.prodname_dotcom %},每小时一次。 -将团队连接到 IdP 组可能会删除一些团队成员。 有关详细信息,请参阅“[同步团队成员的要求](#requirements-for-members-of-synchronized-teams)”。 +{% ifversion ghec %} +All team membership changes made through your IdP will appear in the audit log on {% data variables.product.product_name %} as changes made by the team synchronization bot. Your IdP will send team membership data to {% data variables.product.prodname_dotcom %} once every hour. +Connecting a team to an IdP group may remove some team members. For more information, see "[Requirements for members of synchronized teams](#requirements-for-members-of-synchronized-teams)." {% endif %} -{% ifversion ghae %} 当 Idp 上的组成员身份发生变化时,IdP 会根据 IdP 确定的时间表发送 SCIM 请求,请求更改 {% data variables.product.product_name %}。 更改 {% data variables.product.prodname_dotcom %} 团队或组织成员资格的任何请求都将在审核日志中注册为用于配置用户预配的帐户所做的更改。 有关此帐户的详细信息,请参阅“[为企业配置用户预配](/admin/authentication/configuring-user-provisioning-for-your-enterprise)”。 有关 SCIM 请求计划的详细信息,请参阅 Microsoft Docs 中的“[检查用户预配的状态](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)”。{% endif %} +{% ifversion ghae %} +When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.product_name %} according to the schedule determined by your IdP. Any requests that change {% data variables.product.prodname_dotcom %} team or organization membership will register in the audit log as changes made by the account used to configure user provisioning. For more information about this account, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." For more information about SCIM request schedules, see "[Check the status of user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user)" in the Microsoft Docs. +{% endif %} -父团队无法与 IdP 组同步。 如果要连接到 IdP 组的团队是父团队,我们建议您创建一个新团队或删除使团队成为父团队的嵌套关系。 有关详细信息,请参阅“[关于团队](/articles/about-teams#nested-teams)”、“[创建团队](/organizations/organizing-members-into-teams/creating-a-team)”和“[在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organizations-hierarchy)”。 +Parent teams cannot synchronize with IdP groups. If the team you want to connect to an IdP group is a parent team, we recommend creating a new team or removing the nested relationships that make your team a parent team. For more information, see "[About teams](/articles/about-teams#nested-teams)," "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)," and "[Moving a team in your organization's hierarchy](/articles/moving-a-team-in-your-organizations-hierarchy)." -要管理 {% data variables.product.prodname_dotcom %} 团队(包括连接到 IdP 组的团队)的仓库访问权限,您必须使用 {% data variables.product.product_name %} 进行更改。 有关详细信息,请参阅“[关于团队](/articles/about-teams)”和“[管理团队对组织存储库的访问权限](/articles/managing-team-access-to-an-organization-repository)”。 +To manage repository access for any {% data variables.product.prodname_dotcom %} team, including teams connected to an IdP group, you must make changes with {% data variables.product.product_name %}. For more information, see "[About teams](/articles/about-teams)" and "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)." -{% ifversion ghec %}您还可以使用 API 管理团队同步。 有关详细信息,请参阅“[团队同步](/rest/reference/teams#team-sync)”。{% endif %} +{% ifversion ghec %}You can also manage team synchronization with the API. For more information, see "[Team synchronization](/rest/reference/teams#team-sync)."{% endif %} {% ifversion ghec %} -## 已同步团队成员的要求 +## Requirements for members of synchronized teams -将团队连接到 IdP 组后,团队同步仅在以下情况下将 IdP 组的每个成员添加到 {% data variables.product.product_name %} 上的相应团队: -- 此人是 {% data variables.product.product_name %} 上的组织的成员。 -- 此人已使用 {% data variables.product.product_name %} 上的个人帐户登录,并至少一次通过 SAML 单一登录对组织或企业帐户进行了身份验证。 -- 此人的 SSO 身份是 IdP 组的成员。 +After you connect a team to an IdP group, team synchronization will add each member of the IdP group to the corresponding team on {% data variables.product.product_name %} only if: +- The person is a member of the organization on {% data variables.product.product_name %}. +- The person has already logged in with their personal account on {% data variables.product.product_name %} and authenticated to the organization or enterprise account via SAML single sign-on at least once. +- The person's SSO identity is a member of the IdP group. -不符合这些条件的现有团队或组成员将自动从 {% data variables.product.product_name %} 上的团队中删除,并失去对存储库的访问权限。 撤销用户关联的身份也会将用户从映射到 IdP 组的任何团队中删除。 有关详细信息,请参阅“[查看和管理成员对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)”和“[查看和管理用户对企业的 SAML 访问](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)”。 +Existing teams or group members who do not meet these criteria will be automatically removed from the team on {% data variables.product.product_name %} and lose access to repositories. Revoking a user's linked identity will also remove the user from from any teams mapped to IdP groups. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)" and "[Viewing and managing a user's SAML access to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)." -删除后的团队成员在使用 SSO 向组织或企业帐户进行身份验证后可以自动添加回团队,并移动到已连接的 IdP 组。 +A removed team member can be added back to a team automatically once they have authenticated to the organization or enterprise account using SSO and are moved to the connected IdP group. -为避免无意中删除团队成员,建议在组织或企业帐户中强制实施 SAML SSO,创建新团队以同步成员资格数据,并在同步现有团队之前检查 IdP 组成员资格。 有关详细信息,请参阅“[为组织执行 SAML 单一登录](/articles/enforcing-saml-single-sign-on-for-your-organization)”和“[为企业配置 SAML 单一登录](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)”。 +To avoid unintentionally removing team members, we recommend enforcing SAML SSO in your organization or enterprise account, creating new teams to synchronize membership data, and checking IdP group membership before synchronizing existing teams. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)." {% endif %} -## 先决条件 +## Prerequisites -{% ifversion ghec %} 在连接 {% data variables.product.product_name %} 团队与身份提供程序组之前,组织或企业所有者必须为组织或企业帐户启用团队同步。 有关详细信息,请参阅“[为组织管理团队同步](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)”和“[为企业帐户中的组织管理团队同步](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)”。 +{% ifversion ghec %} +Before you can connect a {% data variables.product.product_name %} team with an identity provider group, an organization or enterprise owner must enable team synchronization for your organization or enterprise account. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" and "[Managing team synchronization for organizations in your enterprise account](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)." -为避免无意中删除团队成员,请访问 IdP 的管理门户,并确认每个当前团队成员也位于要连接到此团队的 IdP 组中。 如果您没有身份提供程序的这一访问权限,在可以联系 IdP 管理员。 +To avoid unintentionally removing team members, visit the administrative portal for your IdP and confirm that each current team member is also in the IdP groups that you want to connect to this team. If you don't have this access to your identity provider, you can reach out to your IdP administrator. -您必须使用 SAML SSO 进行身份验证。 有关详细信息,请参阅“[通过 SAML 单一登录进行身份验证](/articles/authenticating-with-saml-single-sign-on)”。 +You must authenticate using SAML SSO. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)." -{% elsif ghae %} 在连接 {% data variables.product.product_name %} 团队与 IdP 组时,必须先使用支持的跨域身份管理系统 (SCIM) 配置 {% data variables.product.product_location %} 的用户预配。 有关详细信息,请参阅“[为企业配置用户预配](/admin/authentication/configuring-user-provisioning-for-your-enterprise)”。 +{% elsif ghae %} +Before you can connect a {% data variables.product.product_name %} team with an IdP group, you must first configure user provisioning for {% data variables.location.product_location %} using a supported System for Cross-domain Identity Management (SCIM). For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." -在使用 SCIM 配置 {% data variables.product.product_name %} 的用户预配后,您可以将 {% data variables.product.product_name %} 应用程序分配到您想要在 {% data variables.product.product_name %} 上使用的每个 IdP 组。 有关详细信息,请参阅 Microsoft Docs 中的[为 GitHub AE 配置自动用户预配](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae)。{% endif %} +Once user provisioning for {% data variables.product.product_name %} is configured using SCIM, you can assign the {% data variables.product.product_name %} application to every IdP group that you want to use on {% data variables.product.product_name %}. For more information, see [Configure automatic user provisioning to GitHub AE](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae) in the Microsoft Docs. +{% endif %} -## 将 IdP 组连接到团队 +## Connecting an IdP group to a team -将 IdP 组连接到 {% data variables.product.product_name %} 团队时,组中的所有用户都会自动添加到团队中。 {% ifversion ghae %}任何尚未成为父组织成员的用户也会添加到组织。{% endif %} +When you connect an IdP group to a {% data variables.product.product_name %} team, all users in the group are automatically added to the team. {% ifversion ghae %}Any users who were not already members of the parent organization members are also added to the organization.{% endif %} -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %} {% ifversion ghec %} -6. 在“Identity Provider Groups(身份提供程序组)”下,使用下拉菜单,选择最多 5 个身份提供程序组。 - ![用于选择标识提供程序组的下拉菜单](/assets/images/help/teams/choose-an-idp-group.png){% elsif ghae %} -6. 在“Identity Provider Groups(身份提供程序组)”下,使用下拉菜单从列表中选择身份提供程序组。 - ![用于选择标识提供程序组的下拉菜单](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %} -7. 单击“保存更改”。 +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% ifversion ghec %} +6. Under "Identity Provider Groups", use the drop-down menu, and select up to 5 identity provider groups. + ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png){% elsif ghae %} +6. Under "Identity Provider Group", use the drop-down menu, and select an identity provider group from the list. + ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %} +7. Click **Save changes**. -## 断开 IdP 组与团队的连接 +## Disconnecting an IdP group from a team -如果您断开 IdP 组与 {% data variables.product.prodname_dotcom %} 团队的连接,则通过 IdP 组分配给 {% data variables.product.prodname_dotcom %} 团队的团队成员将从团队中删除。 {% ifversion ghae %} 任何只是因为团队连接而成为父组织成员的用户也会从组织中删除。{% endif %} +If you disconnect an IdP group from a {% data variables.product.prodname_dotcom %} team, team members that were assigned to the {% data variables.product.prodname_dotcom %} team through the IdP group will be removed from the team. {% ifversion ghae %} Any users who were members of the parent organization only because of that team connection are also removed from the organization.{% endif %} -{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %} {% ifversion ghec %} -6. 在“Identity Provider Groups(身份提供程序组)”下,单击要断开连接的 IdP 组右侧的 {% octicon "x" aria-label="X symbol" %}。 - ![从 GitHub 团队取消选择已连接的 IdP 组](/assets/images/help/teams/unselect-idp-group.png){% elsif ghae %} -6. 在“Identity Provider Group(身份提供程序组)”下,单击要断开连接的 IdP 组右侧的 {% octicon "x" aria-label="X symbol" %}。 - ![从 GitHub 团队取消选择已连接的 IdP 组](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %} -7. 单击“保存更改”。 +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +{% ifversion ghec %} +6. Under "Identity Provider Groups", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. + ![Unselect a connected IdP group from the GitHub team](/assets/images/help/teams/unselect-idp-group.png){% elsif ghae %} +6. Under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. + ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %} +7. Click **Save changes**. diff --git a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md deleted file mode 100644 index a7aca41d2e..0000000000 --- a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: About OAuth App access restrictions -intro: 'Organizations can choose which {% data variables.product.prodname_oauth_apps %} have access to their repositories and other resources by enabling {% data variables.product.prodname_oauth_app %} access restrictions.' -redirect_from: - - /articles/about-third-party-application-restrictions - - /articles/about-oauth-app-access-restrictions - - /github/setting-up-and-managing-organizations-and-teams/about-oauth-app-access-restrictions -versions: - fpt: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: OAuth App access ---- - -## About OAuth App access restrictions - -{% data reusables.apps.oauth-app-access-restrictions %} - -{% ifversion limit-app-access-requests %} -{% data reusables.organizations.restricted-app-access-requests %}{% endif %} - -{% data reusables.organizations.oauth_app_restrictions_default %} - -{% tip %} - -**Tip**: When an organization has not set up {% data variables.product.prodname_oauth_app %} access restrictions, any {% data variables.product.prodname_oauth_app %} authorized by an organization member can also access the organization's private resources. - -{% endtip %} - -{% ifversion fpt %} -To further protect your organization's resources, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes security features like SAML single sign-on. {% data reusables.enterprise.link-to-ghec-trial %} -{% endif %} - -## Setting up {% data variables.product.prodname_oauth_app %} access restrictions - -When an organization owner sets up {% data variables.product.prodname_oauth_app %} access restrictions for the first time: - -- **Applications that are owned by the organization** are automatically given access to the organization's resources. -- **{% data variables.product.prodname_oauth_apps %}** immediately lose access to the organization's resources. -- **SSH keys created before February 2014** immediately lose access to the organization's resources (this includes user and deploy keys). -- **SSH keys created by {% data variables.product.prodname_oauth_apps %} during or after February 2014** immediately lose access to the organization's resources. -- **Hook deliveries from private organization repositories** will no longer be sent to unapproved {% data variables.product.prodname_oauth_apps %}. -- **API access** to private organization resources is not available for unapproved {% data variables.product.prodname_oauth_apps %}. In addition, there are no privileged create, update, or delete actions on public organization resources. -- **Hooks created by users and hooks created before May 2014** will not be affected. -- **Private forks of organization-owned repositories** are subject to the organization's access restrictions. - -## Resolving SSH access failures - -When an SSH key created before February 2014 loses access to an organization with {% data variables.product.prodname_oauth_app %} access restrictions enabled, subsequent SSH access attempts will fail. Users will encounter an error message directing them to a URL where they can approve the key or upload a trusted key in its place. - -## Webhooks - -When an {% data variables.product.prodname_oauth_app %} is granted access to the organization after restrictions are enabled, any pre-existing webhooks created by that {% data variables.product.prodname_oauth_app %} will resume dispatching. - -When an organization removes access from a previously-approved {% data variables.product.prodname_oauth_app %}, any pre-existing webhooks created by that application will no longer be dispatched (these hooks will be disabled, but not deleted). - -## Re-enabling access restrictions - -If an organization disables {% data variables.product.prodname_oauth_app %} access application restrictions, and later re-enables them, previously approved {% data variables.product.prodname_oauth_app %} are automatically granted access to the organization's resources. - -## Further reading - -- "[Enabling {% data variables.product.prodname_oauth_app %} access restrictions for your organization](/articles/enabling-oauth-app-access-restrictions-for-your-organization)" -- "[Approving {% data variables.product.prodname_oauth_apps %} for your organization](/articles/approving-oauth-apps-for-your-organization)" -- "[Reviewing your organization's installed integrations](/articles/reviewing-your-organization-s-installed-integrations)" -- "[Denying access to a previously approved {% data variables.product.prodname_oauth_app %} for your organization](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)" -- "[Disabling {% data variables.product.prodname_oauth_app %} access restrictions for your organization](/articles/disabling-oauth-app-access-restrictions-for-your-organization)" -- "[Requesting organization approval for {% data variables.product.prodname_oauth_apps %}](/articles/requesting-organization-approval-for-oauth-apps)" -- "[Authorizing {% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)" diff --git a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md deleted file mode 100644 index e50e56dd84..0000000000 --- a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: Approving OAuth Apps for your organization -intro: 'When an organization member or outside collaborator requests {% data variables.product.prodname_oauth_app %} access to organization resources, organization owners can approve or deny the request.' -redirect_from: - - /articles/approving-third-party-applications-for-your-organization - - /articles/approving-oauth-apps-for-your-organization - - /github/setting-up-and-managing-organizations-and-teams/approving-oauth-apps-for-your-organization -versions: - fpt: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Approve OAuth Apps ---- -When {% data variables.product.prodname_oauth_app %} access restrictions are enabled, organization members and outside collaborators must [request approval](/articles/requesting-organization-approval-for-oauth-apps) from an organization owner before they can authorize an {% data variables.product.prodname_oauth_app %} that has access to the organization's resources. - -{% ifversion limit-app-access-requests %} -{% data reusables.organizations.restricted-app-access-requests %}{% endif %} - -{% data reusables.profile.access_org %} -{% data reusables.profile.org_settings %} -{% data reusables.organizations.oauth_app_access %} -5. Next to the application you'd like to approve, click **Review**. -![Review request link](/assets/images/help/settings/settings-third-party-approve-review.png) -6. After you review the information about the requested application, click **Grant access**. -![Grant access button](/assets/images/help/settings/settings-third-party-approve-grant.png) - -## Further reading - -- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)" diff --git a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md deleted file mode 100644 index 21b85937cc..0000000000 --- a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: 拒绝此前批准的 OAuth 应用程序对组织的访问权限 -intro: '如果组织不再需要之前授权的 {% data variables.product.prodname_oauth_app %},所有者可删除此应用程序对组织资源的访问权限。' -redirect_from: - - /articles/denying-access-to-a-previously-approved-application-for-your-organization - - /articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization - - /github/setting-up-and-managing-organizations-and-teams/denying-access-to-a-previously-approved-oauth-app-for-your-organization -versions: - fpt: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Deny OAuth App -ms.openlocfilehash: bcdbe48debe120d2f13f78a429d35c311343f26c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145130342' ---- -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.oauth_app_access %} -5. 在要禁用的应用程序旁边,单击 {% octicon "pencil" aria-label="The edit icon" %}。 - ![“编辑”图标](/assets/images/help/settings/settings-third-party-deny-edit.png) -6. 单击“拒绝访问”。 - ![“拒绝确认”按钮](/assets/images/help/settings/settings-third-party-deny-confirm.png) diff --git a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md deleted file mode 100644 index 9cebefe887..0000000000 --- a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: 禁用 OAuth 应用程序对您的组织的访问权限限制 -intro: '组织所有者可禁用对拥有组织资源访问权限的 {% data variables.product.prodname_oauth_apps %} 的限制。' -redirect_from: - - /articles/disabling-third-party-application-restrictions-for-your-organization - - /articles/disabling-oauth-app-access-restrictions-for-your-organization - - /github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization -versions: - fpt: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Disable OAuth App -ms.openlocfilehash: 41fae63d8d491eec7a6cd6a275958d5c96fb5f5c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145130341' ---- -{% danger %} - -警告:禁用 {% data variables.product.prodname_oauth_app %} 对组织的访问权限限制后,任何组织成员批准某一应用程序使用其私有帐户设置时,将自动授予 {% data variables.product.prodname_oauth_app %} 对组织私有资源的访问权限。 - -{% enddanger %} - -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.oauth_app_access %} -5. 单击“删除限制”。 - ![“删除限制”按钮](/assets/images/help/settings/settings-third-party-remove-restrictions.png) -6. 审查有关禁用第三方应用程序限制的信息后,请单击“是,删除应用程序限制”。 - ![删除确认按钮](/assets/images/help/settings/settings-third-party-confirm-disable.png) diff --git a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md deleted file mode 100644 index 4f396a22fe..0000000000 --- a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: 对组织启用 OAuth App 访问限制 -intro: '组织所有者可启用 {% data variables.product.prodname_oauth_app %} 访问限制,以便在组织成员在其个人账户上使用允许 {% data variables.product.prodname_oauth_apps %} 的同时,防止不受信任的应用程序访问组织的资源。' -redirect_from: - - /articles/enabling-third-party-application-restrictions-for-your-organization - - /articles/enabling-oauth-app-access-restrictions-for-your-organization - - /github/setting-up-and-managing-organizations-and-teams/enabling-oauth-app-access-restrictions-for-your-organization -versions: - fpt: '*' - ghec: '*' -topics: - - Organizations - - Teams -shortTitle: Enable OAuth App -ms.openlocfilehash: 7ae5885530f449c8ce9981067b0d0fe8b23af0d9 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145130339' ---- -{% data reusables.organizations.oauth_app_restrictions_default %} - -{% warning %} - -**警告**: -- 启用 {% data variables.product.prodname_oauth_app %} 访问限制将撤销对所有之前已授权 {% data variables.product.prodname_oauth_apps %} 和 SSH 密钥的组织访问权限。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_oauth_app %} 访问限制](/articles/about-oauth-app-access-restrictions)”。 -- 在设置 {% data variables.product.prodname_oauth_app %} 访问限制后,确保重新授权任何需要持续访问组织私有数据的 {% data variables.product.prodname_oauth_app %}。 所有组织成员将需要创建新的 SSH 密钥,并且组织将需要根据需要创建新的部署密钥。 -- 启用 {% data variables.product.prodname_oauth_app %} 访问限制后,应用程序可以使用 OAuth 令牌访问有关 {% data variables.product.prodname_marketplace %} 事务的信息。 - -{% endwarning %} - -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.oauth_app_access %} -5. 在“第三方应用程序访问策略”下,单击“设置应用程序访问限制”。 - ![设置限制按钮](/assets/images/help/settings/settings-third-party-set-up-restrictions.png) -6. 审查有关第三方访问限制的信息后,单击“限制第三方应用程序访问”。 - ![限制确认按钮](/assets/images/help/settings/settings-third-party-restrict-confirm.png) diff --git a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/index.md b/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/index.md deleted file mode 100644 index 6773f45ef9..0000000000 --- a/translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/index.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: 限制对组织数据的访问 -intro: '{% data variables.product.prodname_oauth_app %} 访问限制允许组织所有者限制不受信任的应用程序访问组织的数据。 然后,组织成员可对其个人用户帐户使用 {% data variables.product.prodname_oauth_apps %},同时保证组织数据安全。' -redirect_from: - - /articles/restricting-access-to-your-organization-s-data - - /articles/restricting-access-to-your-organizations-data - - /github/setting-up-and-managing-organizations-and-teams/restricting-access-to-your-organizations-data -versions: - fpt: '*' - ghec: '*' -topics: - - Organizations - - Teams -children: - - /about-oauth-app-access-restrictions - - /enabling-oauth-app-access-restrictions-for-your-organization - - /disabling-oauth-app-access-restrictions-for-your-organization - - /approving-oauth-apps-for-your-organization - - /denying-access-to-a-previously-approved-oauth-app-for-your-organization -shortTitle: Restrict access to organization data -ms.openlocfilehash: c4d45a93f4fb45adc65dc04151bd58b6ee823344 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145130338' ---- - diff --git a/translations/zh-CN/content/packages/learn-github-packages/about-permissions-for-github-packages.md b/translations/zh-CN/content/packages/learn-github-packages/about-permissions-for-github-packages.md index 68dd781bd9..8d4025e3d6 100644 --- a/translations/zh-CN/content/packages/learn-github-packages/about-permissions-for-github-packages.md +++ b/translations/zh-CN/content/packages/learn-github-packages/about-permissions-for-github-packages.md @@ -45,11 +45,13 @@ For more information, see "[Configuring a package's access control and visibilit ## About scopes and permissions for package registries -To use or manage a package hosted by a package registry, you must use a token with the appropriate scope, and your personal account must have appropriate permissions. +{% data reusables.package_registry.packages-classic-pat-only %} + +To use or manage a package hosted by a package registry, you must use a {% data variables.product.pat_v1 %} with the appropriate scope, and your personal account must have appropriate permissions. For example: -- To download and install packages from a repository, your token must have the `read:packages` scope, and your user account must have read permission. -- {% ifversion fpt or ghes or ghec %}To delete a package on {% data variables.product.product_name %}, your token must at least have the `delete:packages` and `read:packages` scope. The `repo` scope is also required for repo-scoped packages. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% elsif ghae %}To delete a specified version of a package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} +- To download and install packages from a repository, your {% data variables.product.pat_v1 %} must have the `read:packages` scope, and your user account must have read permission. +- {% ifversion fpt or ghes or ghec %}To delete a package on {% data variables.product.product_name %}, your {% data variables.product.pat_v1 %} must at least have the `delete:packages` and `read:packages` scope. The `repo` scope is also required for repo-scoped packages. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% elsif ghae %}To delete a specified version of a package on {% data variables.product.product_name %}, your {% data variables.product.pat_v1 %} must have the `delete:packages` and `repo` scope. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} | Scope | Description | Required permission | | --- | --- | --- | @@ -58,12 +60,12 @@ For example: | `delete:packages` | {% ifversion fpt or ghes or ghec %} Delete packages from {% data variables.product.prodname_registry %} {% elsif ghae %} Delete specified versions of packages from {% data variables.product.prodname_registry %} {% endif %} | admin | | `repo` | Upload and delete packages (along with `write:packages`, or `delete:packages`) | write or admin | -When you create a {% data variables.product.prodname_actions %} workflow, you can use the `GITHUB_TOKEN` to publish and install packages in {% data variables.product.prodname_registry %} without needing to store and manage a personal access token. +When you create a {% data variables.product.prodname_actions %} workflow, you can use the `GITHUB_TOKEN` to publish and install packages in {% data variables.product.prodname_registry %} without needing to store and manage a {% data variables.product.pat_generic %}. For more information, see:{% ifversion fpt or ghec %} - "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)"{% endif %} - "[Publishing and installing a package with {% data variables.product.prodname_actions %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)" -- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token/)" +- "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token/)" - "[Available scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)" ## Maintaining access to packages in {% data variables.product.prodname_actions %} workflows @@ -75,7 +77,7 @@ For more conceptual background on {% data variables.product.prodname_actions %} ### Access tokens - To publish packages associated with the workflow repository, use `GITHUB_TOKEN`. -- To install packages associated with other private repositories that `GITHUB_TOKEN` can't access, use a personal access token +- To install packages associated with other private repositories that `GITHUB_TOKEN` can't access, use a {% data variables.product.pat_v1 %} For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)." diff --git a/translations/zh-CN/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md b/translations/zh-CN/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md index 0549b49958..db786ab0a8 100644 --- a/translations/zh-CN/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md +++ b/translations/zh-CN/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md @@ -1,6 +1,6 @@ --- -title: 将仓库连接到包 -intro: '可以将存储库连接到 {% data variables.product.product_location %} 上的容器映像。' +title: Connecting a repository to a package +intro: 'You can connect a repository to a container image on {% data variables.location.product_location %}.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image @@ -10,49 +10,46 @@ versions: ghec: '*' ghes: '*' shortTitle: Connect a repository -ms.openlocfilehash: 087775df9862c3b2a88dd555d9f571066fef8759 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147882333' --- -通过将仓库连接到包,包登录页面将显示来自仓库的信息和链接,例如 README。 -## 在 {% data variables.product.prodname_dotcom %} 上将仓库连接到用户拥有的包 +By connecting a repository to a package, the package landing page will show information and links from the repository, such as the README. + +## Connecting a repository to a user-owned package on {% data variables.product.prodname_dotcom %} {% data reusables.package_registry.package-settings-from-user-level %} {% data reusables.package_registry.repository_connection_steps %} -## 在 {% data variables.product.prodname_dotcom %} 上将仓库连接到组织拥有的包 +## Connecting a repository to an organization-owned package on {% data variables.product.prodname_dotcom %} {% data reusables.package_registry.package-settings-from-org-level %} {% data reusables.package_registry.repository_connection_steps %} {% ifversion fpt or ghec or ghes > 3.4 %} -## 使用命令行将仓库连接到容器映像 +## Connecting a repository to a container image using the command line -{% ifversion ghes > 3.4 %} {% data reusables.package_registry.container-registry-ghes-beta %} {% endif %} +{% ifversion ghes > 3.4 %} +{% data reusables.package_registry.container-registry-ghes-beta %} +{% endif %} -1. 在 Dockerfile 中,添加此行,将 {% ifversion ghes %}`HOSTNAME`、{% endif %}`OWNER` 和 `REPO` 替换为详细信息: +1. In your Dockerfile, add this line, replacing {% ifversion ghes %}`HOSTNAME`, {% endif %}`OWNER` and `REPO` with your details: ```shell - LABEL org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPO + LABEL org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPO ``` - 例如,如果你是拥有 `my-repo` 的用户 `monalisa`,且 {% data variables.product.product_location %} 主机名为 `github.companyname.com`,则会将此行添加到 Dockerfile: + For example, if you're the user `monalisa` and own `my-repo`, and {% data variables.location.product_location %} hostname is `github.companyname.com`, you would add this line to your Dockerfile: ```shell LABEL org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}{% data reusables.package_registry.container-registry-example-hostname %}{% endif %}/monalisa/my-repo ``` - 有关详细信息,请参阅 Docker 官方文档中的“[标签](https://docs.docker.com/engine/reference/builder/#label)”和 `opencontainers/image-spec` 存储库中的“[预定义的注释键](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)”。 + For more information, see "[LABEL](https://docs.docker.com/engine/reference/builder/#label)" in the official Docker documentation and "[Pre-defined Annotation Keys](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" in the `opencontainers/image-spec` repository. -2. 构建容器映像。 此示例从当前目录中的 Dockerfile 生成映像,并分配映像名称 `hello_docker`。 +2. Build your container image. This example builds an image from the Dockerfile in the current directory and assigns the image name `hello_docker`. ```shell $ docker build -t hello_docker . ``` -3. (可选)查看您想要标记的 Docker 映像的详细信息。 +3. Optionally, review details for the Docker image you want to tag. ```shell $ docker images > REPOSITORY TAG IMAGE ID CREATED SIZE @@ -61,27 +58,27 @@ ms.locfileid: '147882333' > hello-world latest fce289e99eb9 16 months ago 1.84kB ``` -4. 使用所需的映像名称和托管目标标记 Docker 映像。 +4. Tag your Docker image with your desired image name and hosting destination. ```shell $ docker tag IMAGE_NAME {% data reusables.package_registry.container-registry-hostname %}/OWNER/NEW_IMAGE_NAME:TAG ``` - 例如: + For example: ```shell $ docker tag 38f737a91f39 {% data reusables.package_registry.container-registry-example-hostname %}/monalisa/hello_docker:latest ``` -5. 如果尚未向 {% data variables.product.prodname_container_registry %} 验证,请验证。 有关详细信息,请参阅“[对 {% data variables.product.prodname_container_registry %} 进行身份验证](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-the-container-registry)”。 +5. If you haven't already, authenticate to the {% data variables.product.prodname_container_registry %}. For more information, see "[Authenticating to the {% data variables.product.prodname_container_registry %}](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-the-container-registry)." {% raw %} ```shell $ echo $CR_PAT | docker login {% endraw %}{% data reusables.package_registry.container-registry-hostname %}{% raw %} -u USERNAME --password-stdin > Login Succeeded ``` {% endraw %} -6. 推送容器映像到 {% data variables.product.prodname_container_registry %}。 +6. Push your container image to the {% data variables.product.prodname_container_registry %}. ```shell $ docker push {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE-NAME:TAG ``` - 例如: + For example: ```shell $ docker push {% data reusables.package_registry.container-registry-example-hostname %}/monalisa/hello_docker:latest ``` diff --git a/translations/zh-CN/content/packages/learn-github-packages/deleting-and-restoring-a-package.md b/translations/zh-CN/content/packages/learn-github-packages/deleting-and-restoring-a-package.md index f3595a34ff..cb8b157547 100644 --- a/translations/zh-CN/content/packages/learn-github-packages/deleting-and-restoring-a-package.md +++ b/translations/zh-CN/content/packages/learn-github-packages/deleting-and-restoring-a-package.md @@ -40,6 +40,8 @@ On {% data variables.product.prodname_dotcom %}, you can also restore an entire {% ifversion fpt or ghec or ghes %} ## Packages API support +{% data reusables.package_registry.packages-classic-pat-only %} + {% ifversion fpt or ghec %} You can use the REST API to manage your packages. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)." @@ -92,7 +94,7 @@ For packages that inherit their permissions and access from repositories, you ca {% data reusables.package_registry.no-graphql-to-delete-packages %}{% ifversion fpt or ghec %} You can however use the REST API. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)."{% endif %} -Use the `deletePackageVersion` mutation in the GraphQL API. You must use a token with the `read:packages`, `delete:packages`, and `repo` scopes. For more information about tokens, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)." +Use the `deletePackageVersion` mutation in the GraphQL API. You must use a {% data variables.product.pat_v1 %} with the `read:packages`, `delete:packages`, and `repo` scopes. For more information about {% data variables.product.pat_v1_plural %}, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)." The following example demonstrates how to delete a package version, using a `packageVersionId` of `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`. @@ -104,7 +106,7 @@ curl -X POST \ HOSTNAME/graphql ``` -To find all of the private packages you have published to {% data variables.product.prodname_registry %}, along with the version IDs for the packages, you can use the `packages` connection through the `repository` object. You will need a token with the `read:packages` and `repo` scopes. For more information, see the [`packages`](/graphql/reference/objects#repository) connection or the [`PackageOwner`](/graphql/reference/interfaces#packageowner) interface. +To find all of the private packages you have published to {% data variables.product.prodname_registry %}, along with the version IDs for the packages, you can use the `packages` connection through the `repository` object. You will need a {% data variables.product.pat_v1 %} with the `read:packages` and `repo` scopes. For more information, see the [`packages`](/graphql/reference/objects#repository) connection or the [`PackageOwner`](/graphql/reference/interfaces#packageowner) interface. For more information about the `deletePackageVersion` mutation, see "[`deletePackageVersion`](/graphql/reference/mutations#deletepackageversion)." diff --git a/translations/zh-CN/content/packages/learn-github-packages/installing-a-package.md b/translations/zh-CN/content/packages/learn-github-packages/installing-a-package.md index da305e87ef..da7cd8260f 100644 --- a/translations/zh-CN/content/packages/learn-github-packages/installing-a-package.md +++ b/translations/zh-CN/content/packages/learn-github-packages/installing-a-package.md @@ -1,6 +1,6 @@ --- -title: 安装包 -intro: '您可以从 {% data variables.product.prodname_registry %} 安装包,并将包用作自己项目中的依赖项。' +title: Installing a package +intro: 'You can install a package from {% data variables.product.prodname_registry %} and use the package as a dependency in your own project.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /github/managing-packages-with-github-packages/installing-a-package @@ -12,26 +12,22 @@ versions: ghes: '*' ghae: '*' ghec: '*' -ms.openlocfilehash: 86c095ab1eddc969e4e04f3305059678ffcb9c20 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145130322' --- -{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} -## 关于包的安装 +{% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} -您可以在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上搜索,以查找 {% data variables.product.prodname_registry %} 中可以在自己项目中安装的包。 有关详细信息,请参阅“[在 {% data variables.product.prodname_registry %} 中搜索包](/search-github/searching-on-github/searching-for-packages)”。 +## About package installation -找到包后,您可以在包页面上阅读包的说明以及安装和使用说明。 +You can search on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} to find packages in {% data variables.product.prodname_registry %} that you can install in your own project. For more information, see "[Searching {% data variables.product.prodname_registry %} for packages](/search-github/searching-on-github/searching-for-packages)." -## 安装包 +After you find a package, you can read the package's description and installation and usage instructions on the package page. -你可以按照相同的一般准则,使用任何为实例启用的{% ifversion fpt or ghae or ghec %}支持的包客户端{% else %}包类型{% endif %}从 {% data variables.product.prodname_registry %} 安装包。 +## Installing a package -1. 按照包客户端的说明,向 {% data variables.product.prodname_registry %} 验证。 有关详细信息,请参阅“[对 GitHub 包进行身份验证](/packages/learn-github-packages/introduction-to-github-packages#authenticating-to-github-packages)”。 -2. 按照包客户端的说明安装包。 +You can install a package from {% data variables.product.prodname_registry %} using any {% ifversion fpt or ghae or ghec %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines. -有关特定于包客户端的说明,请参阅“[使用 {% data variables.product.prodname_registry %} 注册表](/packages/working-with-a-github-packages-registry)”。 +1. Authenticate to {% data variables.product.prodname_registry %} using the instructions for your package client. For more information, see "[Authenticating to GitHub Packages](/packages/learn-github-packages/introduction-to-github-packages#authenticating-to-github-packages)." +2. Install the package using the instructions for your package client. + +For instructions specific to your package client, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)." diff --git a/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md b/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md index 530f6d7efe..4537c6fe1d 100644 --- a/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md +++ b/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md @@ -101,7 +101,7 @@ For more information about Docker and the {% data variables.product.prodname_con ## Managing packages {% ifversion fpt or ghec %} -You can delete a package in the {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} user interface or using the REST API. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" and the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)." +You can delete a package in the {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} user interface or using the REST API. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" and the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)." {% data reusables.package_registry.no-graphql-to-delete-packages %} {% endif %} @@ -114,7 +114,7 @@ You can delete a private or public package in the {% data variables.product.prod You can delete a version of a package in the {% data variables.product.product_name %} user interface or using the GraphQL API. {% endif %} -When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. +When you use the GraphQL API to query and delete private packages, you must use the same {% data variables.product.pat_v1 %} you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see {% ifversion ghes or ghae %}"[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" and {% endif %}"[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)." diff --git a/translations/zh-CN/content/packages/learn-github-packages/publishing-a-package.md b/translations/zh-CN/content/packages/learn-github-packages/publishing-a-package.md index 0c5ff90454..57496eecf2 100644 --- a/translations/zh-CN/content/packages/learn-github-packages/publishing-a-package.md +++ b/translations/zh-CN/content/packages/learn-github-packages/publishing-a-package.md @@ -1,6 +1,6 @@ --- -title: 发布包 -intro: '您可以将包发布到 {% data variables.product.prodname_registry %} 以供他人下载和再用。' +title: Publishing a package +intro: 'You can publish a package to {% data variables.product.prodname_registry %} to make the package available for others to download and re-use.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /github/managing-packages-with-github-packages/publishing-a-package @@ -11,32 +11,31 @@ versions: ghes: '*' ghae: '*' ghec: '*' -ms.openlocfilehash: e13e33b6085fbdd736d77d7d8b4998595ea7ffcc -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145130320' --- -{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} -## 关于发布的包 +{% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} -您可以在包页面上提供说明和其他详细信息,例如安装和使用说明,以帮助他人了解和使用您的包。 {% data variables.product.product_name %} 提供每个版本的元数据,例如发布日期、下载活动和最新版本。 有关示例包页面,请参阅 [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1)。 +## About published packages -{% data reusables.package_registry.public-or-private-packages %} 一个仓库可连接到多个包。 为避免混淆,请确保使用自述文件和说明清楚地阐明每个包的相关信息。 +You can help people understand and use your package by providing a description and other details like installation and usage instructions on the package page. {% data variables.product.product_name %} provides metadata for each version, such as the publication date, download activity, and recent versions. For an example package page, see [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1). -{% ifversion fpt or ghec %} 如果包的新版本修复了安全漏洞,则应在存储库中发布安全公告。 {% data variables.product.prodname_dotcom %} 审查每个发布的安全通告,并且可能使用它向受影响的仓库发送 {% data variables.product.prodname_dependabot_alerts %}。 有关详细信息,请参阅“[关于 GitHub 安全公告](/github/managing-security-vulnerabilities/about-github-security-advisories)”。 +{% data reusables.package_registry.public-or-private-packages %} A repository can be connected to more than one package. To prevent confusion, make sure the README and description clearly provide information about each package. + +{% ifversion fpt or ghec %} +If a new version of a package fixes a security vulnerability, you should publish a security advisory in your repository. {% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. For more information, see "[About GitHub Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." {% endif %} -## 发布包 +## Publishing a package -您可以按照一般准则,使用任何{% ifversion fpt or ghae or ghec %}支持的包客户端{% else %}为您的实例启用的包类型{% endif %}将包发布到 {% data variables.product.prodname_registry %}。 +{% data reusables.package_registry.packages-classic-pat-only %} -1. 针对要完成的任务,创建具有适当作用域的访问令牌或使用现有的此类令牌。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_registry %} 的权限](/packages/learn-github-packages/about-permissions-for-github-packages)”。 -2. 按照包客户端的说明,使用访问令牌向 {% data variables.product.prodname_registry %} 验证。 -3. 按照包客户端的说明发布包。 +You can publish a package to {% data variables.product.prodname_registry %} using any {% ifversion fpt or ghae or ghec %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines. -有关包客户端的特定说明,请参阅“[使用 GitHub Packages 注册表](/packages/working-with-a-github-packages-registry)”。 +1. Create or use an existing {% data variables.product.pat_v1 %} with the appropriate scopes for the task you want to accomplish. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)." +2. Authenticate to {% data variables.product.prodname_registry %} using your {% data variables.product.pat_v1 %} and the instructions for your package client. +3. Publish the package using the instructions for your package client. -在发布包后,您可以在 {% data variables.product.prodname_dotcom %} 上查看该包。 有关详细信息,请参阅“[查看包](/packages/learn-github-packages/viewing-packages)”。 +For instructions specific to your package client, see "[Working with a GitHub Packages registry](/packages/working-with-a-github-packages-registry)." + +After you publish a package, you can view the package on {% data variables.product.prodname_dotcom %}. For more information, see "[Viewing packages](/packages/learn-github-packages/viewing-packages)." diff --git a/translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md index 34d324af49..a4dbfcc69a 100644 --- a/translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md +++ b/translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md @@ -32,7 +32,7 @@ You can extend the CI and CD capabilities of your repository by publishing or in ### Authenticating to package registries on {% data variables.product.prodname_dotcom %} -{% ifversion fpt or ghec %}If you want your workflow to authenticate to {% data variables.product.prodname_registry %} to access a package registry other than the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_location %}, then{% else %}To authenticate to package registries on {% data variables.product.product_name %},{% endif %} we recommend using the `GITHUB_TOKEN` that {% data variables.product.product_name %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %} instead of a personal access token for authentication. You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. For forks, the `GITHUB_TOKEN` is granted read access for the parent repository. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)." +{% ifversion fpt or ghec %}If you want your workflow to authenticate to {% data variables.product.prodname_registry %} to access a package registry other than the {% data variables.product.prodname_container_registry %} on {% data variables.location.product_location %}, then{% else %}To authenticate to package registries on {% data variables.product.product_name %},{% endif %} we recommend using the `GITHUB_TOKEN` that {% data variables.product.product_name %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %} instead of a {% data variables.product.pat_generic %} for authentication. You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. For forks, the `GITHUB_TOKEN` is granted read access for the parent repository. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)." You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %} context. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." @@ -53,7 +53,7 @@ When you enable GitHub Actions, GitHub installs a GitHub App on your repository. The {% data variables.packages.prodname_ghcr_and_npm_registry_full %} allows users to create and administer packages as free-standing resources at the organization level. Packages can be owned by an organization or personal account and you can customize access to each of your packages separately from repository permissions. -All workflows accessing the {% data variables.packages.prodname_ghcr_and_npm_registry %} should use the `GITHUB_TOKEN` instead of a personal access token. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)." +All workflows accessing the {% data variables.packages.prodname_ghcr_and_npm_registry %} should use the `GITHUB_TOKEN` instead of a {% data variables.product.pat_generic %}. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)." ## Default permissions and access settings for containers modified through workflows @@ -484,13 +484,13 @@ Installing packages hosted by {% data variables.product.prodname_registry %} thr {% data reusables.package_registry.actions-configuration %} {% ifversion fpt or ghec %} -## Upgrading a workflow that accesses a registry using a PAT +## Upgrading a workflow that accesses a registry using a {% data variables.product.pat_generic %} -The {% data variables.packages.prodname_ghcr_and_npm_registry %} support the `GITHUB_TOKEN` for easy and secure authentication in your workflows. If your workflow is using a personal access token (PAT) to authenticate to the registry, then we highly recommend you update your workflow to use the `GITHUB_TOKEN`. +The {% data variables.packages.prodname_ghcr_and_npm_registry %} support the `GITHUB_TOKEN` for easy and secure authentication in your workflows. If your workflow is using a {% data variables.product.pat_generic %} to authenticate to the registry, then we highly recommend you update your workflow to use the `GITHUB_TOKEN`. For more information about the `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)." -Using the `GITHUB_TOKEN` instead of a PAT, which includes the `repo` scope, increases the security of your repository as you don't need to use a long-lived PAT that offers unnecessary access to the repository where your workflow is run. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)." +Using the `GITHUB_TOKEN` instead of a {% data variables.product.pat_v1 %}, which includes the `repo` scope, increases the security of your repository as you don't need to use a long-lived {% data variables.product.pat_generic %} that offers unnecessary access to the repository where your workflow is run. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)." 1. Navigate to your package landing page. 1. In the left sidebar, click **Actions access**. @@ -504,7 +504,7 @@ Using the `GITHUB_TOKEN` instead of a PAT, which includes the `repo` scope, incr {% endnote %} 1. Optionally, using the "role" drop-down menu, select the default access level that you'd like the repository to have to your container image. ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png) -1. Open your workflow file. On the line where you log in to the registry, replace your PAT with {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}. +1. Open your workflow file. On the line where you log in to the registry, replace your {% data variables.product.pat_generic %} with {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}. For example, this workflow publishes a Docker image to the {% data variables.product.prodname_container_registry %} and uses {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} to authenticate. @@ -544,7 +544,7 @@ jobs: run: docker build . --file Dockerfile --tag $IMAGE_NAME --label "runnumber=${GITHUB_RUN_ID}" - name: Log in to registry - # This is where you will update the PAT to GITHUB_TOKEN + # This is where you will update the {% data variables.product.pat_generic %} to GITHUB_TOKEN run: echo "{% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}" | docker login ghcr.io -u ${{ github.actor }} --password-stdin - name: Push image diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md index ca2de2dfc8..400f954e6d 100644 --- a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md +++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md @@ -1,6 +1,6 @@ --- -title: 从 Docker 注册表迁移到容器注册表 -intro: '{% ifversion docker-ghcr-enterprise-migration %}企业所有者可以{% else %}{% data variables.product.company_short %}将{% endif %}之前存储在 {% data variables.product.product_location %} 上的 Docker 注册表中的 Docker 映像迁移到 {% data variables.product.prodname_container_registry %}。' +title: Migrating to the Container registry from the Docker registry +intro: '{% ifversion docker-ghcr-enterprise-migration %}An enterprise owner can{% else %}{% data variables.product.company_short %} will{% endif %} migrate Docker images previously stored in the Docker registry on {% data variables.location.product_location %} to the {% data variables.product.prodname_container_registry %}.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images @@ -9,47 +9,42 @@ redirect_from: versions: fpt: '*' ghec: '*' - feature: docker-ghcr-enterprise-migration + feature: 'docker-ghcr-enterprise-migration' shortTitle: Migration to Container registry topics: - Containers - Docker - Migration -ms.openlocfilehash: eb940881f59c9c935695c6fd7e3a62c9c3f387c9 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147409489' --- + {% data reusables.package_registry.container-registry-ghes-beta %} -## 关于 {% data variables.product.prodname_container_registry %} +## About the {% data variables.product.prodname_container_registry %} -{% data reusables.package_registry.container-registry-benefits %}有关详细信息,请参阅“[使用 {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)”。 +{% data reusables.package_registry.container-registry-benefits %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)." -## 关于从 Docker 注册表迁移 +## About migration from the Docker registry -{% data reusables.package_registry.container-registry-replaces-docker-registry %}如果已将 Docker 映像存储在 Docker 注册表中,则{% ifversion docker-ghcr-enterprise-migration %}企业所有者{% else %}{% data variables.product.company_short %}{% endif %}会逐步将映像迁移到 {% data variables.product.prodname_container_registry %}。 你无需执行任何操作。 +{% data reusables.package_registry.container-registry-replaces-docker-registry %} If you've stored Docker images in the Docker registry, {% ifversion docker-ghcr-enterprise-migration %}an enterprise owner{% else %}{% data variables.product.company_short %}{% endif %} will gradually migrate the images to the {% data variables.product.prodname_container_registry %}. No action is required on your part. {% ifversion docker-ghcr-enterprise-migration %} {% note %} -注意:{% data reusables.package_registry.container-registry-ghes-migration-availability %}有关查找所使用的 {% data variables.product.product_name %} 版本的详细信息,请参阅“[关于 {% data variables.product.prodname_docs %} 的版本](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)”。 +**Note**: {% data reusables.package_registry.container-registry-ghes-migration-availability %} For more information about finding the version of {% data variables.product.product_name %} that you use, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)." {% endnote %} {% endif %} -在将 Docker 映像迁移到 {% data variables.product.prodname_container_registry %} 后,你将看到对包详细信息所做的以下更改。 +After a Docker image has been migrated to the {% data variables.product.prodname_container_registry %}, you'll see the following changes to the details for the package. -- 该图标将是 {% data variables.product.prodname_container_registry %} 徽标,而不是 Docker 徽标。 -- 拉取 URL 中的域将是 {% data variables.product.prodname_container_registry_namespace %} 而不是 {% data variables.product.prodname_docker_registry_namespace %}。 +- The icon will be the {% data variables.product.prodname_container_registry %} logo instead of the Docker logo. +- The domain in the pull URL will be {% data variables.product.prodname_container_registry_namespace %} instead of {% data variables.product.prodname_docker_registry_namespace %}. {% ifversion fpt or ghec %} -![迁移到 {% data variables.product.prodname_container_registry %} 的 Docker 映像的屏幕截图](/assets/images/help/package-registry/container-registry-details-page.png) +![Screenshot of a Docker image migrated to the {% data variables.product.prodname_container_registry %}](/assets/images/help/package-registry/container-registry-details-page.png) {% endif %} @@ -57,18 +52,18 @@ ms.locfileid: '147409489' {% ifversion fpt or ghec %} -迁移后,便无法再使用 GraphQL API 来查询 `PackageType` 为“DOCKER”的包。 可以改为使用 REST API 查询 `package_type` 为“容器”的包。 有关详细信息,请参阅 REST API 文档中的“[包](/rest/reference/packages)”。 +After migration, you'll no longer be able to use the GraphQL API to query for packages with a `PackageType` of "DOCKER". Instead, you can use the REST API to query for packages with a `package_type` of "container". For more information, see "[Packages](/rest/reference/packages)" in the REST API documentation. -## 关于 {% data variables.product.prodname_container_registry %} 的计费 +## About billing for {% data variables.product.prodname_container_registry %} -有关 {% data variables.product.prodname_container_registry %} 计费的详细信息,请参阅“[关于 {% data variables.product.prodname_registry %} 的计费](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)”。 +For more information about billing for the {% data variables.product.prodname_container_registry %}, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)." {% endif %} {% ifversion docker-ghcr-enterprise-migration %} -## 延伸阅读 +## Further reading -- [将企业从 Docker 注册表迁移到 {% data variables.product.prodname_container_registry %}](/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry) +- "[Migrating your enterprise to the {% data variables.product.prodname_container_registry %} from the Docker registry](/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry)" {% endif %} diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md index 85a94d6146..733136372b 100644 --- a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md +++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md @@ -1,6 +1,6 @@ --- -title: 使用 Apache Maven 注册表 -intro: '您可以配置 Apache Maven 以将包发布到 {% data variables.product.prodname_registry %} 并将存储在 {% data variables.product.prodname_registry %} 上的包用作 Java 项目中的依赖项。' +title: Working with the Apache Maven registry +intro: 'You can configure Apache Maven to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /articles/configuring-apache-maven-for-use-with-github-package-registry @@ -14,39 +14,36 @@ versions: ghae: '*' ghec: '*' shortTitle: Apache Maven registry -ms.openlocfilehash: 0d2fafd69ac870a521fee8c7105b79bf8839d62c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147061704' --- -{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} + +{% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} {% data reusables.package_registry.admins-can-configure-package-types %} -## 向 {% data variables.product.prodname_registry %} 验证 +## Authenticating to {% data variables.product.prodname_registry %} {% data reusables.package_registry.authenticate-packages %} {% data reusables.package_registry.authenticate-packages-github-token %} -### 使用个人访问令牌进行身份验证 +### Authenticating with a {% data variables.product.pat_generic %} {% data reusables.package_registry.required-scopes %} -通过编辑 ~/.m2/settings.xml 文件以包含个人访问令牌,可以使用 Apache Maven 向 {% data variables.product.prodname_registry %} 进行身份验证。 如果 ~/.m2/settings.xml 文件不存在,请新建该文件。 +You can authenticate to {% data variables.product.prodname_registry %} with Apache Maven by editing your *~/.m2/settings.xml* file to include your {% data variables.product.pat_v1 %}. Create a new *~/.m2/settings.xml* file if one doesn't exist. -在 `servers` 标记中,添加一个带有 `id` 的子 `server` 标记,将“USERNAME”替换为 {% data variables.product.prodname_dotcom %} 用户名,并将“TOKEN”替换为个人访问令牌。 +In the `servers` tag, add a child `server` tag with an `id`, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, and *TOKEN* with your {% data variables.product.pat_generic %}. -在 `repositories` 标记中,通过将存储库的 `id` 映射到在包含凭据的 `server` 标记中添加的 `id` 来对该存储库进行配置。 将 {% ifversion ghes or ghae %}HOSTNAME 替换为 {% data variables.product.product_location %} 的主机名,并将{% endif %} OWNER 替换为拥有该存储库的用户或组织帐户的名称。 由于不支持大写字母,因此,即使您的 {% data variables.product.prodname_dotcom %} 用户或组织名称中包含大写字母,也必须对仓库所有者使用小写字母。 +In the `repositories` tag, configure a repository by mapping the `id` of the repository to the `id` you added in the `server` tag containing your credentials. Replace {% ifversion ghes or ghae %}*HOSTNAME* with the host name of {% data variables.location.product_location %}, and{% endif %} *OWNER* with the name of the user or organization account that owns the repository. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters. -如果要与多个存储库交互,可以将每个存储库添加到 `repositories` 标记中独立的子 `repository`,将每个存储库的 -`id` 映射到 `servers` 标记中的凭据。 +If you want to interact with multiple repositories, you can add each repository to separate `repository` children in the `repositories` tag, mapping the `id` of each to the credentials in the `servers` tag. {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} -{% ifversion ghes %} 如果实例启用了子域隔离:{% endif %} +{% ifversion ghes %} +If your instance has subdomain isolation enabled: +{% endif %} ```xml ``` -{% ifversion ghes %} 如果实例禁用了子域隔离: +{% ifversion ghes %} +If your instance has subdomain isolation disabled: ```xml ` 元素中包含该存储库的 URL。 {% data variables.product.prodname_dotcom %} 将根据该字段匹配仓库。 由于存储库名称也是 `distributionManagement` 元素的一部分,因此将多个包发布到同一存储库无需额外步骤。 +If you would like to publish multiple packages to the same repository, you can include the URL of the repository in the `` element of the *pom.xml* file. {% data variables.product.prodname_dotcom %} will match the repository based on that field. Since the repository name is also part of the `distributionManagement` element, there are no additional steps to publish multiple packages to the same repository. -有关创建包的详细信息,请参阅 [maven.apache.org 文档](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html)。 +For more information on creating a package, see the [maven.apache.org documentation](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html). -1. 编辑位于包目录中的 pom.xml 文件的 `distributionManagement` 元素,将 {% ifversion ghes or ghae %}HOSTNAME 替换为 {% data variables.product.product_location %} 的主机名,将 {% endif %}`OWNER` 替换为拥有该存储库的用户或组织帐户的名称,并将 `REPOSITORY` 替换为包含项目的存储库的名称。{% ifversion ghes %} +1. Edit the `distributionManagement` element of the *pom.xml* file located in your package directory, replacing {% ifversion ghes or ghae %}*HOSTNAME* with the host name of {% data variables.location.product_location %}, {% endif %}`OWNER` with the name of the user or organization account that owns the repository and `REPOSITORY` with the name of the repository containing your project.{% ifversion ghes %} - 如果您的实例启用了子域隔离功能:{% endif %} + If your instance has subdomain isolation enabled:{% endif %} ```xml @@ -169,12 +165,12 @@ ms.locfileid: '147061704' {% data reusables.package_registry.viewing-packages %} -## 安装包 +## Installing a package -要从 {% data variables.product.prodname_registry %} 安装 Apache Maven 包,请编辑 pom.xml 文件以包含该包作为依赖项。 如果要从多个存储库安装包,请为每个存储库添加 `repository` 标记。 有关在项目中使用 pom.xml 文件的详细信息,请参阅 Apache Maven 文档中的“[POM 简介](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)”。 +To install an Apache Maven package from {% data variables.product.prodname_registry %}, edit the *pom.xml* file to include the package as a dependency. If you want to install packages from more than one repository, add a `repository` tag for each. For more information on using a *pom.xml* file in your project, see "[Introduction to the POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)" in the Apache Maven documentation. {% data reusables.package_registry.authenticate-step %} -2. 将包依赖项添加到项目 pom.xml 文件的 `dependencies` 元素,将 `com.example:test` 替换为包。 +2. Add the package dependencies to the `dependencies` element of your project *pom.xml* file, replacing `com.example:test` with your package. ```xml @@ -186,13 +182,13 @@ ms.locfileid: '147061704' ``` {% data reusables.package_registry.checksum-maven-plugin %} -3. 安装此包。 +3. Install the package. ```shell $ mvn install ``` -## 延伸阅读 +## Further reading -- “[使用 Gradle 注册表](/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry)” -- [删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package) +- "[Working with the Gradle registry](/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry)" +- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md index edf9540d4a..6f00ec0d2e 100644 --- a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md +++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md @@ -46,7 +46,7 @@ When installing or publishing a Docker image, the {% data variables.product.prod To authenticate to the {% data variables.product.prodname_container_registry %} (`ghcr.io`) within a {% data variables.product.prodname_actions %} workflow, use the `GITHUB_TOKEN` for the best security and experience. {% data reusables.package_registry.authenticate_with_pat_for_v2_registry %} {% endif %} -{% ifversion ghes %}Ensure that you replace `HOSTNAME` with {% data variables.product.product_location_enterprise %} hostname or IP address in the examples below.{% endif %} +{% ifversion ghes %}Ensure that you replace `HOSTNAME` with {% data variables.location.product_location_enterprise %} hostname or IP address in the examples below.{% endif %} {% data reusables.package_registry.authenticate-to-container-registry-steps %} diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md index 0ea713b72d..b0fa5478a9 100644 --- a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md +++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md @@ -1,6 +1,6 @@ --- -title: 使用 Docker 注册表 -intro: '{% ifversion fpt or ghec %}Docker 注册表现已被 {% data variables.product.prodname_container_registry %} 取代。{% else %}您可以使用 {% data variables.product.prodname_registry %} Docker 注册表推送和拉取您的 Docker 映像。{% endif %}' +title: Working with the Docker registry +intro: '{% ifversion fpt or ghec %}The Docker registry has now been replaced by the {% data variables.product.prodname_container_registry %}.{% else %}You can push and pull your Docker images using the {% data variables.product.prodname_registry %} Docker registry.{% endif %}' product: '{% data reusables.gated-features.packages %}' redirect_from: - /articles/configuring-docker-for-use-with-github-package-registry @@ -15,143 +15,165 @@ versions: ghae: '*' ghec: '*' shortTitle: Docker registry -ms.openlocfilehash: f5d37e74f93535fd48f3400ef0b504825aadc657 -ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/12/2022 -ms.locfileid: '147888450' --- + {% ifversion fpt or ghec %} -{% data variables.product.prodname_dotcom %} 的 Docker 注册表(使用命名空间 `docker.pkg.github.com`)已被 {% data variables.product.prodname_container_registry %} 替换(使用命名空间 `https://ghcr.io`)。 {% data variables.product.prodname_container_registry %} 为 Docker 映像提供粒度权限和存储优化等优点。 +{% data variables.product.prodname_dotcom %}'s Docker registry (which used the namespace `docker.pkg.github.com`) has been replaced by the {% data variables.product.prodname_container_registry %} (which uses the namespace `https://ghcr.io`). The {% data variables.product.prodname_container_registry %} offers benefits such as granular permissions and storage optimization for Docker images. -先前存储在 Docker 注册表中的 Docker 映像将自动迁移到 {% data variables.product.prodname_container_registry %}。 有关详细信息,请参阅“[从 Docker 注册表迁移到 {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)”和“[使用 {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)。” +Docker images previously stored in the Docker registry are being automatically migrated into the {% data variables.product.prodname_container_registry %}. For more information, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)" and "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)." {% else %} -{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} +{% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} {% data reusables.package_registry.admins-can-configure-package-types %} -## 关于 Docker 支持 +## About Docker support -安装或发布 Docker 映像时,Docker 注册表目前不支持外部层,例如 Windows 映像。 +When installing or publishing a Docker image, the Docker registry does not currently support foreign layers, such as Windows images. -## 向 {% data variables.product.prodname_registry %} 验证 +## Authenticating to {% data variables.product.prodname_registry %} {% data reusables.package_registry.authenticate-packages %} {% data reusables.package_registry.authenticate-packages-github-token %} -### 使用个人访问令牌进行身份验证 +### Authenticating with a {% data variables.product.pat_generic %} {% data reusables.package_registry.required-scopes %} -可以使用 `docker` 登录命令,通过 Docker 向 {% data variables.product.prodname_registry %} 验证。 +You can authenticate to {% data variables.product.prodname_registry %} with Docker using the `docker` login command. -为确保凭据安全,我们建议将个人访问令牌保存在计算机的本地文件中,然后使用 Docker 的 `--password-stdin` 标志从本地文件读取令牌。 +To keep your credentials secure, we recommend you save your {% data variables.product.pat_generic %} in a local file on your computer and use Docker's `--password-stdin` flag, which reads your token from a local file. -{% ifversion fpt or ghec %} {% raw %} +{% ifversion fpt or ghec %} +{% raw %} ```shell - $ cat ~/TOKEN.txt | docker login https://docker.pkg.github.com -u USERNAME --password-stdin + $ cat ~/TOKEN.txt | docker login https://docker.pkg.github.com -u USERNAME --password-stdin ``` -{% endraw %} {% endif %} +{% endraw %} +{% endif %} -{% ifversion ghes or ghae %} {% ifversion ghes %} 如果实例启用了子域隔离:{% endif %} {% raw %} +{% ifversion ghes or ghae %} +{% ifversion ghes %} +If your instance has subdomain isolation enabled: +{% endif %} +{% raw %} ```shell - $ cat ~/TOKEN.txt | docker login docker.HOSTNAME -u USERNAME --password-stdin + $ cat ~/TOKEN.txt | docker login docker.HOSTNAME -u USERNAME --password-stdin ``` -{% endraw %} {% ifversion ghes %} 如果实例禁用了子域隔离: +{% endraw %} +{% ifversion ghes %} +If your instance has subdomain isolation disabled: {% raw %} ```shell - $ cat ~/TOKEN.txt | docker login HOSTNAME -u USERNAME --password-stdin + $ cat ~/TOKEN.txt | docker login HOSTNAME -u USERNAME --password-stdin ``` -{% endraw %} {% endif %} +{% endraw %} +{% endif %} {% endif %} -要使用此示例登录命令,请将 `USERNAME` 替换为 {% data variables.product.product_name %} 用户名{% ifversion ghes or ghae %},将 `HOSTNAME` 替换为 {% data variables.product.product_location %} 的 URL,{% endif %}并将 `~/TOKEN.txt` 替换为用于 {% data variables.product.product_name %} 的个人访问令牌的文件路径。 +To use this example login command, replace `USERNAME` with your {% data variables.product.product_name %} username{% ifversion ghes or ghae %}, `HOSTNAME` with the URL for {% data variables.location.product_location %},{% endif %} and `~/TOKEN.txt` with the file path to your {% data variables.product.pat_generic %} for {% data variables.product.product_name %}. -有关详细信息,请参阅“[Docker 登录](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)”。 +For more information, see "[Docker login](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)." -## 发布映像 +## Publishing an image {% data reusables.package_registry.docker_registry_deprecation_status %} {% note %} -注意:映像名称只能使用小写字母。 +**Note:** Image names must only use lowercase letters. {% endnote %} -{% data variables.product.prodname_registry %} 支持每个仓库的多个顶层 Docker 镜像。 仓库可以拥有任意数量的映像标记。 在发布或安装大于 10GB 的 Docker 映像(每个图层上限为 5GB)时,可能会遇到服务降级的情况。 有关详细信息,请参阅 Docker 文档中的“[Docker 标记](https://docs.docker.com/engine/reference/commandline/tag/)”。 +{% data variables.product.prodname_registry %} supports multiple top-level Docker images per repository. A repository can have any number of image tags. You may experience degraded service publishing or installing Docker images larger than 10GB, layers are capped at 5GB each. For more information, see "[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)" in the Docker documentation. {% data reusables.package_registry.viewing-packages %} -1. 使用 `docker images` 确定 Docker 映像的名称和 ID。 +1. Determine the image name and ID for your docker image using `docker images`. ```shell $ docker images > < > > REPOSITORY TAG IMAGE ID CREATED SIZE - > IMAGE_NAME VERSION IMAGE_ID 4 weeks ago 1.11MB + > IMAGE_NAME VERSION IMAGE_ID 4 weeks ago 1.11MB ``` -2. 使用 Docker 映像 ID、标记和 Docker 映像,将 OWNER 替换为拥有存储库的用户或组织帐户的名称,将 REPOSITORY 替换为包含项目的存储库的名称,将 IMAGE_NAME 替换为包或映像的名称,{% ifversion ghes or ghae %}将 HOSTNAME 替换为 {% data variables.product.product_location %} 的主机名,{% endif %}并将 VERSION 替换为生成时的包版本 。 +2. Using the Docker image ID, tag the docker image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% ifversion ghes or ghae %} *HOSTNAME* with the hostname of {% data variables.location.product_location %},{% endif %} and *VERSION* with package version at build time. {% ifversion fpt or ghec %} ```shell - $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` - {% else %} {% ifversion ghes %} 如果实例启用了子域隔离:{% endif %} + {% else %} + {% ifversion ghes %} + If your instance has subdomain isolation enabled: + {% endif %} ```shell - $ docker tag IMAGE_ID docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + $ docker tag IMAGE_ID docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` - {% ifversion ghes %} 如果实例禁用了子域隔离: + {% ifversion ghes %} + If your instance has subdomain isolation disabled: ```shell - $ docker tag IMAGE_ID HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + $ docker tag IMAGE_ID HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` - {% endif %} {% endif %} -3. 如果尚未为包生成 Docker 映像,请生成映像,将 OWNER 替换为拥有存储库的用户或组织帐户的名称,将 REPOSITORY 替换为包含项目的存储库的名称,将 IMAGE_NAME 替换为包或映像的名称,将 VERSION 替换为生成时的包版本,{% ifversion ghes or ghae %}将 HOSTNAME 替换为 {% data variables.product.product_location %} 的主机名,{% endif %}并将 PATH 替换为映像路径(如果映像未在当前工作目录中) 。 + {% endif %} + {% endif %} +3. If you haven't already built a docker image for the package, build the image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, *VERSION* with package version at build time,{% ifversion ghes or ghae %} *HOSTNAME* with the hostname of {% data variables.location.product_location %},{% endif %} and *PATH* to the image if it isn't in the current working directory. {% ifversion fpt or ghec %} ```shell - $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` - {% else %} {% ifversion ghes %} 如果实例启用了子域隔离:{% endif %} + {% else %} + {% ifversion ghes %} + If your instance has subdomain isolation enabled: + {% endif %} ```shell - $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` - {% ifversion ghes %} 如果实例禁用了子域隔离: + {% ifversion ghes %} + If your instance has subdomain isolation disabled: ```shell - $ docker build -t HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH + $ docker build -t HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH ``` - {% endif %} {% endif %} -4. 将映像发布到 {% data variables.product.prodname_registry %}。 + {% endif %} + {% endif %} +4. Publish the image to {% data variables.product.prodname_registry %}. {% ifversion fpt or ghec %} ```shell - $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION + $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` - {% else %} {% ifversion ghes %} 如果实例启用了子域隔离:{% endif %} + {% else %} + {% ifversion ghes %} + If your instance has subdomain isolation enabled: + {% endif %} ```shell - $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` - {% ifversion ghes %} 如果实例禁用了子域隔离: + {% ifversion ghes %} + If your instance has subdomain isolation disabled: ```shell - $ docker push HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION + $ docker push HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION ``` - {% endif %} {% endif %} {% note %} + {% endif %} + {% endif %} + {% note %} - 注意:必须使用 `IMAGE_NAME:VERSION` 而不是 `IMAGE_NAME:SHA` 推送映像。 + **Note:** You must push your image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`. {% endnote %} -### 发布 Docker 映像的示例 +### Example publishing a Docker image -{% ifversion ghes %} 这些示例假设实例已启用子域隔离。 +{% ifversion ghes %} +These examples assume your instance has subdomain isolation enabled. {% endif %} -可以使用映像 ID 将 `monalisa` 映像的 1.0 版本发布到 `octocat/octo-app` 存储库。 +You can publish version 1.0 of the `monalisa` image to the `octocat/octo-app` repository using an image ID. {% ifversion fpt or ghec %} ```shell @@ -176,15 +198,15 @@ $ docker images > monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB # Tag the image with OWNER/REPO/IMAGE_NAME -$ docker tag c75bebcdd211 docker.HOSTNAME/octocat/octo-app/monalisa:1.0 +$ docker tag c75bebcdd211 docker.HOSTNAME/octocat/octo-app/monalisa:1.0 # Push the image to {% data variables.product.prodname_registry %} -$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 +$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 ``` {% endif %} -首次可以发布新的 Docker 映像并将其命名为 `monalisa`。 +You can publish a new Docker image for the first time and name it `monalisa`. {% ifversion fpt or ghec %} ```shell @@ -200,43 +222,47 @@ $ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0 ```shell # Build the image with docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION # Assumes Dockerfile resides in the current working directory (.) -$ docker build -t docker.HOSTNAME/octocat/octo-app/monalisa:1.0 . +$ docker build -t docker.HOSTNAME/octocat/octo-app/monalisa:1.0 . # Push the image to {% data variables.product.prodname_registry %} -$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 +$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0 ``` {% endif %} -## 下载图像 +## Downloading an image {% data reusables.package_registry.docker_registry_deprecation_status %} -可以使用 `docker pull` 命令从 {% data variables.product.prodname_registry %} 安装 Docker 映像,将 OWNER 替换为拥有存储库的用户或组织帐户的名称,将 REPOSITORY 替换为包含项目的存储库的名称,将 IMAGE_NAME 替换为包或映像的名称,{% ifversion ghes or ghae %}将 HOSTNAME 替换为 {% data variables.product.product_location %} 的主机名,{% endif %} 并将 TAG_NAME 替换为要安装的映像的标记 。 +You can use the `docker pull` command to install a docker image from {% data variables.product.prodname_registry %}, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% ifversion ghes or ghae %} *HOSTNAME* with the host name of {% data variables.location.product_location %}, {% endif %} and *TAG_NAME* with tag for the image you want to install. {% ifversion fpt or ghec %} ```shell -$ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +$ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME ``` {% else %} -{% ifversion ghes %} 如果实例启用了子域隔离:{% endif %} +{% ifversion ghes %} +If your instance has subdomain isolation enabled: +{% endif %} ```shell -$ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +$ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME ``` -{% ifversion ghes %} 如果实例禁用了子域隔离: +{% ifversion ghes %} +If your instance has subdomain isolation disabled: ```shell -$ docker pull HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME +$ docker pull HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME ``` -{% endif %} {% endif %} +{% endif %} +{% endif %} {% note %} -注意:必须使用 `IMAGE_NAME:VERSION` 而不是 `IMAGE_NAME:SHA` 拉取映像。 +**Note:** You must pull the image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`. {% endnote %} -## 延伸阅读 +## Further reading -- [删除和还原包](/packages/learn-github-packages/deleting-and-restoring-a-package) +- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" {% endif %} diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md index 3cbe4eab4f..e903fc567f 100644 --- a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md +++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md @@ -1,6 +1,6 @@ --- -title: 使用 Gradle 注册表 -intro: '您可以配置 Gradle 以将包发布到 {% data variables.product.prodname_registry %} Gradle 注册表并将存储在 {% data variables.product.prodname_registry %} 上的包用作 Java 项目中的依赖项。' +title: Working with the Gradle registry +intro: 'You can configure Gradle to publish packages to the {% data variables.product.prodname_registry %} Gradle registry and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /articles/configuring-gradle-for-use-with-github-package-registry @@ -14,42 +14,40 @@ versions: ghae: '*' ghec: '*' shortTitle: Gradle registry -ms.openlocfilehash: 65475c04ea3c6934bdf126500f16c3a907b7efd6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147061657' --- -{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} + +{% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} {% data reusables.package_registry.admins-can-configure-package-types %} -## 向 {% data variables.product.prodname_registry %} 验证 +## Authenticating to {% data variables.product.prodname_registry %} {% data reusables.package_registry.authenticate-packages %} -{% data reusables.package_registry.authenticate-packages-github-token %} 有关将 `GITHUB_TOKEN` 与 Gradle 结合使用的详细信息,请参阅“[使用 Gradle 发布 Java 包](/actions/guides/publishing-java-packages-with-gradle#publishing-packages-to-github-packages)”。 +{% data reusables.package_registry.authenticate-packages-github-token %} For more information about using `GITHUB_TOKEN` with Gradle, see "[Publishing Java packages with Gradle](/actions/guides/publishing-java-packages-with-gradle#publishing-packages-to-github-packages)." -### 使用个人访问令牌进行身份验证 +### Authenticating with a {% data variables.product.pat_generic %} {% data reusables.package_registry.required-scopes %} -你可以使用 Gradle Groovy 或 Kotlin DSL 通过 Gradle 向 {% data variables.product.prodname_registry %} 进行验证,方法是编辑你的 build.gradle 文件 (Gradle Groovy) 或 build.gradle.kts 文件 (Kotlin DSL),将你的个人访问令牌包含在其中 。 您还可以配置 Gradle Groovy 和 Kotlin DSL 以识别仓库中的一个或多个包。 +You can authenticate to {% data variables.product.prodname_registry %} with Gradle using either Gradle Groovy or Kotlin DSL by editing your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file to include your {% data variables.product.pat_v1 %}. You can also configure Gradle Groovy and Kotlin DSL to recognize a single package or multiple packages in a repository. -{% ifversion ghes %} 将 REGISTRY-URL 替换为你实例的 Maven 注册表的 URL。 如果你的实例启用了子域隔离功能,请使用 `maven.HOSTNAME`。 如果你的实例禁用了子域隔离功能,请使用 `HOSTNAME/_registry/maven`。 在任一情况下,都将 HOSTNAME 替换为 {% data variables.product.prodname_ghe_server %} 实例的主机名。 -{% elsif ghae %} 将 REGISTRY-URL 替换为企业 Maven 注册表 `maven.HOSTNAME` 的 URL。 将 HOSTNAME 替换为 {% data variables.product.product_location %} 的主机名。 +{% ifversion ghes %} +Replace *REGISTRY-URL* with the URL for your instance's Maven registry. If your instance has subdomain isolation enabled, use `maven.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/maven`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance. +{% elsif ghae %} +Replace *REGISTRY-URL* with the URL for your enterprise's Maven registry, `maven.HOSTNAME`. Replace *HOSTNAME* with the host name of {% data variables.location.product_location %}. {% endif %} -将 USERNAME 替换为你的 {% data variables.product.prodname_dotcom %} 用户名,将 TOKEN 替换为你的个人访问令牌,将 REPOSITORY 替换为包含要发布的包的存储库的名称,将 OWNER 替换为 {% data variables.product.prodname_dotcom %} 上拥有该存储库的用户或组织帐户的名称 。 由于不支持大写字母,因此,即使您的 {% data variables.product.prodname_dotcom %} 用户或组织名称中包含大写字母,也必须对仓库所有者使用小写字母。 +Replace *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your {% data variables.product.pat_v1 %}, *REPOSITORY* with the name of the repository containing the package you want to publish, and *OWNER* with the name of the user or organization account on {% data variables.product.prodname_dotcom %} that owns the repository. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters. {% note %} -注意:{% data reusables.package_registry.apache-maven-snapshot-versions-supported %} 有关示例,请参阅“[配置 Apache Maven 以用于 {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)”。 +**Note:** {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} For an example, see "[Configuring Apache Maven for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)." {% endnote %} -#### 将 Gradle Groovy 用于一个仓库中单个包的示例 +#### Example using Gradle Groovy for a single package in a repository ```shell plugins { @@ -59,10 +57,10 @@ publishing { repositories { maven { name = "GitHubPackages" - url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") credentials { - username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") + username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") } } } @@ -74,7 +72,7 @@ publishing { } ``` -#### 将 Gradle Groovy 用于同一个仓库中多个包的示例 +#### Example using Gradle Groovy for multiple packages in the same repository ```shell plugins { @@ -86,10 +84,10 @@ subprojects { repositories { maven { name = "GitHubPackages" - url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") credentials { - username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") + username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") } } } @@ -102,7 +100,7 @@ subprojects { } ``` -#### 将 Kotlin DSL 用于同一个仓库中单个包的示例 +#### Example using Kotlin DSL for a single package in the same repository ```shell plugins { @@ -112,10 +110,10 @@ publishing { repositories { maven { name = "GitHubPackages" - url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") credentials { - username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") + username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") } } } @@ -127,7 +125,7 @@ publishing { } ``` -#### 将 Kotlin DSL 用于同一个仓库中多个包的示例 +#### Example using Kotlin DSL for multiple packages in the same repository ```shell plugins { @@ -139,10 +137,10 @@ subprojects { repositories { maven { name = "GitHubPackages" - url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") credentials { - username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") + username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") } } } @@ -155,67 +153,67 @@ subprojects { } ``` -## 发布包 +## Publishing a package -{% data reusables.package_registry.default-name %} 例如,{% data variables.product.prodname_dotcom %} 将名为 `com.example.test` 的包发布到 `OWNER/test` {% data variables.product.prodname_registry %} 存储库中。 +{% data reusables.package_registry.default-name %} For example, {% data variables.product.prodname_dotcom %} will publish a package named `com.example.test` in the `OWNER/test` {% data variables.product.prodname_registry %} repository. {% data reusables.package_registry.viewing-packages %} {% data reusables.package_registry.authenticate-step %} -2. 创建包后,您可以发布包。 +2. After creating your package, you can publish the package. ```shell $ gradle publish ``` -## 使用已发布的包 +## Using a published package -要使用 {% data variables.product.prodname_registry %} 发布的软件包,请将包添加为依赖项,并将仓库添加到项目。 有关详细信息,请参阅 Gradle 文档中的“[声明依赖项](https://docs.gradle.org/current/userguide/declaring_dependencies.html)”。 +To use a published package from {% data variables.product.prodname_registry %}, add the package as a dependency and add the repository to your project. For more information, see "[Declaring dependencies](https://docs.gradle.org/current/userguide/declaring_dependencies.html)" in the Gradle documentation. {% data reusables.package_registry.authenticate-step %} -2. 将包依赖项添加到你的 build.gradle 文件 (Gradle Groovy) 或 build.gradle.kts 文件 (Kotlin DSL) 。 +2. Add the package dependencies to your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file. - 使用 Gradle Groovy 的示例: + Example using Gradle Groovy: ```shell dependencies { implementation 'com.example:package' } ``` - 使用 Kotlin DSL 的示例: + Example using Kotlin DSL: ```shell dependencies { implementation("com.example:package") } ``` -3. 将存储库添加到 build.gradle 文件 (Gradle Groovy) 或 build.gradle.kts 文件 (Kotlin DSL) 。 +3. Add the repository to your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file. - 使用 Gradle Groovy 的示例: + Example using Gradle Groovy: ```shell repositories { maven { - url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") credentials { - username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") + username = project.findProperty("gpr.user") ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") ?: System.getenv("TOKEN") } } } ``` - 使用 Kotlin DSL 的示例: + Example using Kotlin DSL: ```shell repositories { maven { - url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") + url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY") credentials { - username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") - password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") + username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME") + password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN") } } } ``` -## 延伸阅读 +## Further reading -- [使用 Apache Maven 注册表](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry) -- [删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package) +- "[Working with the Apache Maven registry](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry)" +- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md index cc0d74151d..f17d1a1b94 100644 --- a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md +++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md @@ -42,13 +42,13 @@ If you reach this limit, consider deleting package versions or contact Support f You can also choose to give access permissions to packages independently for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_actions %}. For more information, see "[Ensuring Codespaces access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-codespaces-access-to-your-package) and [Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)." {% endif %} -### Authenticating with a personal access token +### Authenticating with a {% data variables.product.pat_generic %} {% data reusables.package_registry.required-scopes %} -You can authenticate to {% data variables.product.prodname_registry %} with npm by either editing your per-user *~/.npmrc* file to include your personal access token or by logging in to npm on the command line using your username and personal access token. +You can authenticate to {% data variables.product.prodname_registry %} with npm by either editing your per-user *~/.npmrc* file to include your {% data variables.product.pat_v1 %} or by logging in to npm on the command line using your username and {% data variables.product.pat_generic %}. -To authenticate by adding your personal access token to your *~/.npmrc* file, edit the *~/.npmrc* file for your project to include the following line, replacing {% ifversion ghes or ghae %}*HOSTNAME* with the host name of {% data variables.product.product_location %} and {% endif %}*TOKEN* with your personal access token. Create a new *~/.npmrc* file if one doesn't exist. +To authenticate by adding your {% data variables.product.pat_v1 %} to your *~/.npmrc* file, edit the *~/.npmrc* file for your project to include the following line, replacing {% ifversion ghes or ghae %}*HOSTNAME* with the host name of {% data variables.location.product_location %} and {% endif %}*TOKEN* with your {% data variables.product.pat_generic %}. Create a new *~/.npmrc* file if one doesn't exist. {% ifversion ghes %} If your instance has subdomain isolation enabled: @@ -66,7 +66,7 @@ If your instance has subdomain isolation disabled: ``` {% endif %} -To authenticate by logging in to npm, use the `npm login` command, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, and *PUBLIC-EMAIL-ADDRESS* with your email address. +To authenticate by logging in to npm, use the `npm login` command, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your {% data variables.product.pat_v1 %}, and *PUBLIC-EMAIL-ADDRESS* with your email address. If {% data variables.product.prodname_registry %} is not your default package registry for using npm and you want to use the `npm audit` command, we recommend you use the `--scope` flag with the owner of the package when you authenticate to {% data variables.product.prodname_registry %}. @@ -206,7 +206,7 @@ By default, you can only use npm packages hosted on your enterprise, and you wil ### Installing packages from other organizations -By default, you can only use {% data variables.product.prodname_registry %} packages from one organization. If you'd like to route package requests to multiple organizations and users, you can add additional lines to your *.npmrc* file, replacing {% ifversion ghes or ghae %}*HOSTNAME* with the host name of {% data variables.product.product_location %} and {% endif %}*OWNER* with the name of the user or organization account that owns the repository containing your project. +By default, you can only use {% data variables.product.prodname_registry %} packages from one organization. If you'd like to route package requests to multiple organizations and users, you can add additional lines to your *.npmrc* file, replacing {% ifversion ghes or ghae %}*HOSTNAME* with the host name of {% data variables.location.product_location %} and {% endif %}*OWNER* with the name of the user or organization account that owns the repository containing your project. {% ifversion ghes %} If your instance has subdomain isolation enabled: diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md index 074da2f85c..9e13e1e527 100644 --- a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md +++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md @@ -1,6 +1,6 @@ --- -title: 使用 NuGet 注册表 -intro: '你可以配置 `dotnet` 命令行接口 (CLI) 以将 NuGet 包发布到 {% data variables.product.prodname_registry %} 并将存储在 {% data variables.product.prodname_registry %} 上的包用作 .NET 项目中的依赖项。' +title: Working with the NuGet registry +intro: 'You can configure the `dotnet` command-line interface (CLI) to publish NuGet packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a .NET project.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /articles/configuring-nuget-for-use-with-github-package-registry @@ -15,24 +15,20 @@ versions: ghae: '*' ghec: '*' shortTitle: NuGet registry -ms.openlocfilehash: d97a5645a3d945bb79cf6d3b9e8e09eb6b5d7a42 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147580509' --- -{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} + +{% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} {% data reusables.package_registry.admins-can-configure-package-types %} -## 向 {% data variables.product.prodname_registry %} 验证 +## Authenticating to {% data variables.product.prodname_registry %} {% data reusables.package_registry.authenticate-packages %} -### 在 {% data variables.product.prodname_actions %} 中使用 `GITHUB_TOKEN` 进行身份验证 +### Authenticating with `GITHUB_TOKEN` in {% data variables.product.prodname_actions %} -在 {% data variables.product.prodname_actions %} 工作流中通过以下命令使用 `GITHUB_TOKEN` 向 {% data variables.product.prodname_registry %} 进行身份验证,而不是对存储库的 nuget.config 文件中的令牌进行硬编码: +Use the following command to authenticate to {% data variables.product.prodname_registry %} in a {% data variables.product.prodname_actions %} workflow using the `GITHUB_TOKEN` instead of hardcoding a {% data variables.product.pat_generic %} in a nuget.config file in the repository: ```shell dotnet nuget add source --username USERNAME --password {%raw%}${{ secrets.GITHUB_TOKEN }}{% endraw %} --store-password-in-clear-text --name github "https://{% ifversion fpt or ghec %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json" @@ -40,19 +36,20 @@ dotnet nuget add source --username USERNAME --password {%raw%}${{ secrets.GITHUB {% data reusables.package_registry.authenticate-packages-github-token %} -### 使用个人访问令牌进行身份验证 +### Authenticating with a {% data variables.product.pat_generic %} {% data reusables.package_registry.required-scopes %} -要使用 `dotnet` 命令行接口 (CLI) 向 {% data variables.product.prodname_registry %} 进行身份验证,请在项目目录中创建一个 nuget.config 文件,将 {% data variables.product.prodname_registry %} 指定为 `dotnet` CLI 客户端的 `packageSources` 下的源。 +To authenticate to {% data variables.product.prodname_registry %} with the `dotnet` command-line interface (CLI), create a *nuget.config* file in your project directory specifying {% data variables.product.prodname_registry %} as a source under `packageSources` for the `dotnet` CLI client. -必须: -- 将 `USERNAME` 替换为 {% data variables.product.prodname_dotcom %} 上的个人帐户的名称。 -- 将 `TOKEN` 替换为个人访问令牌。 -- 将 `OWNER` 替换为拥有项目所在存储库的用户或组织帐户的名称。{% ifversion ghes or ghae %} -- 将 `HOSTNAME` 替换为 {% data variables.product.product_location %} 的主机名。{% endif %} +You must replace: +- `USERNAME` with the name of your personal account on {% data variables.product.prodname_dotcom %}. +- `TOKEN` with your {% data variables.product.pat_v1 %}. +- `OWNER` with the name of the user or organization account that owns the repository containing your project.{% ifversion ghes or ghae %} +- `HOSTNAME` with the host name for {% data variables.location.product_location %}.{% endif %} -{% ifversion ghes %}如果实例启用了子域隔离:{% endif %} +{% ifversion ghes %}If your instance has subdomain isolation enabled: +{% endif %} ```xml @@ -70,7 +67,8 @@ dotnet nuget add source --username USERNAME --password {%raw%}${{ secrets.GITHUB ``` -{% ifversion ghes %}如果实例禁用了子域隔离: +{% ifversion ghes %} +If your instance has subdomain isolation disabled: ```xml @@ -89,44 +87,44 @@ dotnet nuget add source --username USERNAME --password {%raw%}${{ secrets.GITHUB ``` {% endif %} -## 发布包 +## Publishing a package -可通过使用 nuget.config 文件进行身份验证或使用包含 {% data variables.product.prodname_dotcom %} 个人访问令牌 (PAT) 的 `--api-key` 命令行选项,向 {% data variables.product.prodname_registry %} 发布包。 +You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file, or by using the `--api-key` command line option with your {% data variables.product.prodname_dotcom %} {% data variables.product.pat_v1 %}. -### 使用 GitHub PAT 作为 API 密钥发布包 +### Publishing a package using a GitHub {% data variables.product.pat_generic %} as your API key -如果还没有用于 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上帐户的 PAT,请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 +If you don't already have a PAT to use for your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." -1. 创建新项目。 +1. Create a new project. ```shell dotnet new console --name OctocatApp ``` -2. 打包项目。 +2. Package the project. ```shell dotnet pack --configuration Release ``` -3. 使用您的 PAT 作为 API 密钥发布包。 +3. Publish the package using your {% data variables.product.pat_generic %} as the API key. ```shell - dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --api-key YOUR_GITHUB_PAT --source "github" + dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --api-key YOUR_GITHUB_PAT --source "github" ``` {% data reusables.package_registry.viewing-packages %} -### 使用 nuget.config 文件发布包 +### Publishing a package using a *nuget.config* file -发布时,需要将 csproj 文件中的 `OWNER` 值用于 nuget.config 身份验证文件 。 在 .csproj 文件中指定或递增版本号,然后使用 `dotnet pack` 命令创建该版本的 .nuspec 文件 。 有关创建包的详细信息,请参阅 Microsoft 文档中的“[创建和发布包](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)”。 +When publishing, you need to use the same value for `OWNER` in your *csproj* file that you use in your *nuget.config* authentication file. Specify or increment the version number in your *.csproj* file, then use the `dotnet pack` command to create a *.nuspec* file for that version. For more information on creating your package, see "[Create and publish a package](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)" in the Microsoft documentation. {% data reusables.package_registry.authenticate-step %} -2. 创建新项目。 +2. Create a new project. ```shell dotnet new console --name OctocatApp ``` -3. 将项目的特定信息添加到以 .csproj 结尾的项目文件中。 必须: - - 将 `OWNER` 替换为拥有项目所在存储库的用户或组织帐户的名称。 - - 将 `REPOSITORY` 替换为要发布的包所在存储库的名称。 - - 将 `1.0.0` 替换为包的版本号。{% ifversion ghes or ghae %} - - 将 `HOSTNAME` 替换为 {% data variables.product.product_location %} 的主机名。{% endif %} +3. Add your project's specific information to your project's file, which ends in *.csproj*. You must replace: + - `OWNER` with the name of the user or organization account that owns the repository containing your project. + - `REPOSITORY` with the name of the repository containing the package you want to publish. + - `1.0.0` with the version number of the package.{% ifversion ghes or ghae %} + - `HOSTNAME` with the host name for {% data variables.location.product_location %}.{% endif %} ``` xml @@ -143,23 +141,23 @@ dotnet nuget add source --username USERNAME --password {%raw%}${{ secrets.GITHUB ``` -4. 打包项目。 +4. Package the project. ```shell dotnet pack --configuration Release ``` -5. 使用在 nuget.config 文件中指定的 `key` 发布包。 +5. Publish the package using the `key` you specified in the *nuget.config* file. ```shell dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github" ``` {% data reusables.package_registry.viewing-packages %} -## 将多个包发布到同一个仓库 +## Publishing multiple packages to the same repository -要将多个包发布到同一个存储库,可以在所有 .csproj 项目文件的 `RepositoryURL` 字段中包含相同的 {% data variables.product.prodname_dotcom %} 存储库 URL。 {% data variables.product.prodname_dotcom %} 根据该字段匹配仓库。 +To publish multiple packages to the same repository, you can include the same {% data variables.product.prodname_dotcom %} repository URL in the `RepositoryURL` fields in all *.csproj* project files. {% data variables.product.prodname_dotcom %} matches the repository based on that field. -例如,OctodogApp 和 OctocatApp 项目将发布到同一个存储库 : +For example, the *OctodogApp* and *OctocatApp* projects will publish to the same repository: ``` xml @@ -195,13 +193,13 @@ dotnet nuget add source --username USERNAME --password {%raw%}${{ secrets.GITHUB ``` -## 安装包 +## Installing a package -在项目中使用来自 {% data variables.product.prodname_dotcom %} 的包类似于使用来自 nuget.org 的包。将包依赖项添加到 .csproj 文件,并指定包名称和版本 。 有关在项目中使用 .csproj 文件的详细信息,请参阅 Microsoft 文档中的“[使用 NuGet 包](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)”。 +Using packages from {% data variables.product.prodname_dotcom %} in your project is similar to using packages from *nuget.org*. Add your package dependencies to your *.csproj* file, specifying the package name and version. For more information on using a *.csproj* file in your project, see "[Working with NuGet packages](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)" in the Microsoft documentation. {% data reusables.package_registry.authenticate-step %} -2. 要使用包,请在 .csproj 项目文件中添加 `ItemGroup` 并配置 `PackageReference` 字段。 将 `Include="OctokittenApp"` 中的 `OctokittenApp` 值替换为包依赖项,并将 `Version="12.0.2"` 中的 `12.0.2` 值替换为要使用的版本: +2. To use a package, add `ItemGroup` and configure the `PackageReference` field in the *.csproj* project file. Replace the `OctokittenApp` value in `Include="OctokittenApp"` with your package dependency, and replace the `12.0.2` value in `Version="12.0.2"` with the version you want to use: ``` xml @@ -223,19 +221,19 @@ dotnet nuget add source --username USERNAME --password {%raw%}${{ secrets.GITHUB ``` -3. 使用 `restore` 命令安装包。 +3. Install the packages with the `restore` command. ```shell dotnet restore ``` -## 故障排除 +## Troubleshooting -如果 .csproj 中的 `RepositoryUrl` 未设置为预期存储库,则 NuGet 包可能无法推送。 +Your NuGet package may fail to push if the `RepositoryUrl` in *.csproj* is not set to the expected repository . -如果使用的是 nuspec 文件,请确保它具有包含必要的 `type` 和 `url` 属性的 `repository` 元素。 +If you're using a nuspec file, ensure that it has a `repository` element with the required `type` and `url` attributes. -如果使用 `GITHUB_TOKEN` 对 {% data variables.product.prodname_actions %} 工作流内的 {% data variables.product.prodname_registry %} 注册表进行身份验证,则令牌无法在工作流运行范围以外的其他存储库中访问基于专用存储库的包。 若要访问与其他存储库关联的包,请改为生成具有 `read:packages` 范围的 PAT,并将此令牌作为机密传入。 +If you're using a `GITHUB_TOKEN` to authenticate to a {% data variables.product.prodname_registry %} registry within a {% data variables.product.prodname_actions %} workflow, the token cannot access private repository-based packages in a different repository other than where the workflow is running in. To access packages associated with other repositories, instead generate a {% data variables.product.pat_v1 %} with the `read:packages` scope and pass this token in as a secret. -## 延伸阅读 +## Further reading -- [删除和还原包](/packages/learn-github-packages/deleting-and-restoring-a-package) +- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md index 101689060d..e179d7aa58 100644 --- a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md +++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md @@ -1,6 +1,6 @@ --- -title: 使用 RubyGems 注册表 -intro: '您可以配置 RubyGems 以将包发布到 {% data variables.product.prodname_registry %} 并将存储在 {% data variables.product.prodname_registry %} 上的包用作带 Bundler 的 Ruby 项目中的依赖项。' +title: Working with the RubyGems registry +intro: 'You can configure RubyGems to publish a package to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Ruby project with Bundler.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /articles/configuring-rubygems-for-use-with-github-package-registry @@ -14,69 +14,65 @@ versions: ghae: '*' ghec: '*' shortTitle: RubyGems registry -ms.openlocfilehash: 56fb2fda7c50e6f1a1a3265e55c77d65a7af8705 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147882325' --- -{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} + +{% data reusables.package_registry.packages-ghes-release-stage %} +{% data reusables.package_registry.packages-ghae-release-stage %} {% data reusables.package_registry.admins-can-configure-package-types %} -## 先决条件 +## Prerequisites -- 您必须具有 RubyGems 2.4.1 或更高版本。 要查找您的 RubyGems 版本: +- You must have RubyGems 2.4.1 or higher. To find your RubyGems version: ```shell $ gem --version ``` -- 必须拥有 bundler 1.6.4 或更高版本。 要查找您的 Bundler 版本: +- You must have bundler 1.6.4 or higher. To find your Bundler version: ```shell $ bundle --version Bundler version 1.13.7 ``` -- 安装 keycutter 以管理多个凭据。 要安装 keycutter: +- Install keycutter to manage multiple credentials. To install keycutter: ```shell $ gem install keycutter ``` -## 向 {% data variables.product.prodname_registry %} 验证 +## Authenticating to {% data variables.product.prodname_registry %} {% data reusables.package_registry.authenticate-packages %} {% data reusables.package_registry.authenticate-packages-github-token %} -### 使用个人访问令牌进行身份验证 +### Authenticating with a {% data variables.product.pat_generic %} {% data reusables.package_registry.required-scopes %} -通过编辑用于发布 gem 的 ~/.gem/credentials 文件、编辑用于安装单个 gem 的 ~/.gemrc 文件或使用用于跟踪和安装一个或多个 gem 的 Bundler,可使用 RubyGems 向 {% data variables.product.prodname_registry %} 进行身份验证 。 +You can authenticate to {% data variables.product.prodname_registry %} with RubyGems by editing the *~/.gem/credentials* file for publishing gems, editing the *~/.gemrc* file for installing a single gem, or using Bundler for tracking and installing one or more gems. -要发布新的 gem,需要通过编辑 ~/.gem/credentials 文件以包含你的个人访问令牌,使用 RubyGems 向 {% data variables.product.prodname_registry %} 进行身份验证。 如果此文件不存在,请创建新的 ~/.gem/credentials 文件。 +To publish new gems, you need to authenticate to {% data variables.product.prodname_registry %} with RubyGems by editing your *~/.gem/credentials* file to include your {% data variables.product.pat_v1 %}. Create a new *~/.gem/credentials* file if this file doesn't exist. -例如,创建或编辑 ~/.gem/credentials 以包含以下内容,将“令牌”替换为个人访问令牌 。 +For example, you would create or edit a *~/.gem/credentials* to include the following, replacing *TOKEN* with your {% data variables.product.pat_generic %}. ```shell --- -:github: Bearer TOKEN +:github: Bearer TOKEN ``` -要安装 gem,需要通过编辑项目的 ~/.gemrc 文件以包含 `https://USERNAME:TOKEN@{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`,来对 {% data variables.product.prodname_registry %} 进行身份验证。 必须: - - 将 `USERNAME` 替换为 {% data variables.product.prodname_dotcom %} 用户名。 - - 将 `TOKEN` 替换为个人访问令牌。 - - 将 `OWNER` 替换为拥有项目所在存储库的用户或组织帐户的名称。{% ifversion ghes %} - - 将 `REGISTRY-URL` 替换为实例的 Rubygems 注册表的 URL。 如果实例启用了子域隔离功能,请使用 `rubygems.HOSTNAME`。 如果实例禁用了子域隔离功能,请使用 `HOSTNAME/_registry/rubygems`。 在任一情况下,都将 HOSTNAME 替换为 {% data variables.product.prodname_ghe_server %} 实例的主机名。 +To install gems, you need to authenticate to {% data variables.product.prodname_registry %} by editing the *~/.gemrc* file for your project to include `https://USERNAME:TOKEN@{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`. You must replace: + - `USERNAME` with your {% data variables.product.prodname_dotcom %} username. + - `TOKEN` with your {% data variables.product.pat_v1 %}. + - `OWNER` with the name of the user or organization account that owns the repository containing your project.{% ifversion ghes %} + - `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance. {% elsif ghae %} - - 将 `REGISTRY-URL` 替换为实例的 Rubygems 注册表 `rubygems.HOSTNAME` 的 URL。 将 HOSTNAME 替换为 {% data variables.product.product_location %} 的主机名。 + - `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.location.product_location %}. {% endif %} -如果没有 ~/.gemrc 文件,请使用此示例创建新的 ~/.gemrc 文件 。 +If you don't have a *~/.gemrc* file, create a new *~/.gemrc* file using this example. ```shell --- @@ -90,45 +86,45 @@ ms.locfileid: '147882325' ``` -若要使用 Bundler 进行身份验证,请将 Bundler 配置为使用个人访问令牌,将“用户名”替换为 {% data variables.product.prodname_dotcom %} 用户名,将“令牌”替换为个人访问令牌,并将“所有者”替换为拥有包含项目的存储库的用户或组织帐户的名称。{% ifversion ghes %} 将 `REGISTRY-URL` 替换为实例的 RubyGems 注册表的 URL 。 如果实例启用了子域隔离功能,请使用 `rubygems.HOSTNAME`。 如果实例禁用了子域隔离功能,请使用 `HOSTNAME/_registry/rubygems`。 在任一情况下,请将“主机名”替换为 {% data variables.product.prodname_ghe_server %} 实例的主机名。{% elsif ghae %}将 `REGISTRY-URL` 替换为实例的 Rubygems 注册表 `rubygems.HOSTNAME` 的 URL。 将 HOSTNAME 替换为 {% data variables.product.product_location %} 的主机名。{% endif %} +To authenticate with Bundler, configure Bundler to use your {% data variables.product.pat_v1 %}, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your {% data variables.product.pat_generic %}, and *OWNER* with the name of the user or organization account that owns the repository containing your project.{% ifversion ghes %} Replace `REGISTRY-URL` with the URL for your instance's RubyGems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance.{% elsif ghae %}Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.location.product_location %}.{% endif %} ```shell -$ bundle config https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER USERNAME:TOKEN +$ bundle config https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER USERNAME:TOKEN ``` -## 发布包 +## Publishing a package -{% data reusables.package_registry.default-name %} 例如,将 `octo-gem` 发布到 `octo-org` 组织时,{% data variables.product.prodname_registry %} 会将 gem 发布到 `octo-org/octo-gem` 存储库。 有关创建 gem 的详细信息,请参阅 RubyGems 文档中的“[创建自己的 gem](http://guides.rubygems.org/make-your-own-gem/)”。 +{% data reusables.package_registry.default-name %} For example, when you publish `octo-gem` to the `octo-org` organization, {% data variables.product.prodname_registry %} publishes the gem to the `octo-org/octo-gem` repository. For more information on creating your gem, see "[Make your own gem](http://guides.rubygems.org/make-your-own-gem/)" in the RubyGems documentation. {% data reusables.package_registry.viewing-packages %} {% data reusables.package_registry.authenticate-step %} -2. 从 gemspec 生成包以创建 .gem 包 。 +2. Build the package from the *gemspec* to create the *.gem* package. ```shell gem build OCTO-GEM.gemspec ``` -3. 将包发布到 {% data variables.product.prodname_registry %},将 `OWNER` 替换为拥有包含项目的存储库的用户或组织帐户的名称,并将 `OCTO-GEM` 替换为 gem 包的名称。{% ifversion ghes %} 将 `REGISTRY-URL` 替换为实例的 Rubygems 注册表的 URL。 如果实例启用了子域隔离功能,请使用 `rubygems.HOSTNAME`。 如果实例禁用了子域隔离功能,请使用 `HOSTNAME/_registry/rubygems`。 在任一情况下,请将“主机名”替换为 {% data variables.product.prodname_ghe_server %} 实例的主机名。{% elsif ghae %} 将 `REGISTRY-URL` 替换为实例的 Rubygems 注册表 `rubygems.HOSTNAME` 的 URL。 将 HOSTNAME 替换为 {% data variables.product.product_location %} 的主机名。{% endif %} +3. Publish a package to {% data variables.product.prodname_registry %}, replacing `OWNER` with the name of the user or organization account that owns the repository containing your project and `OCTO-GEM` with the name of your gem package.{% ifversion ghes %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% elsif ghae %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.location.product_location %}.{% endif %} ```shell $ gem push --key github \ - --host https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER \ - OCTO-GEM-0.0.1.gem + --host https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER \ + OCTO-GEM-0.0.1.gem ``` -## 将多个包发布到同一个仓库 +## Publishing multiple packages to the same repository -要将多个 gem 发布到同一存储库,可在 `gem.metadata` 的 `github_repo` 字段中包含指向 {% data variables.product.prodname_dotcom %} 存储库的 URL。 如果包含此字段,则 {% data variables.product.prodname_dotcom %} 将基于此值匹配存储库,而不是使用 gem 名称。{% ifversion ghes or ghae %} 将“主机名”替换为 {% data variables.product.product_location %} 的主机名。{% endif %} +To publish multiple gems to the same repository, you can include the URL to the {% data variables.product.prodname_dotcom %} repository in the `github_repo` field in `gem.metadata`. If you include this field, {% data variables.product.prodname_dotcom %} matches the repository based on this value, instead of using the gem name.{% ifversion ghes or ghae %} Replace *HOSTNAME* with the host name of {% data variables.location.product_location %}.{% endif %} ```ruby gem.metadata = { "github_repo" => "ssh://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" } ``` -## 安装包 +## Installing a package -可使用来自 {% data variables.product.prodname_registry %} 的 gem,就像使用来自 rubygems.org 的 gem 一样。需要通过在 ~/.gemrc 文件中将 {% data variables.product.prodname_dotcom %} 用户或组织添加为源,或者通过使用 Bundler 并编辑 Gemfile,对 {% data variables.product.prodname_registry %} 进行身份验证 。 +You can use gems from {% data variables.product.prodname_registry %} much like you use gems from *rubygems.org*. You need to authenticate to {% data variables.product.prodname_registry %} by adding your {% data variables.product.prodname_dotcom %} user or organization as a source in the *~/.gemrc* file or by using Bundler and editing your *Gemfile*. {% data reusables.package_registry.authenticate-step %} -1. 对于 Bundler,请将 {% data variables.product.prodname_dotcom %} 用户或组织添加为 Gemfile 中的源,以便从这个新源获取 gem。 例如,可以将一个新的 `source` 块添加到 Gemfile,其仅对指定的包使用 {% data variables.product.prodname_registry %},将 GEM NAME 替换为要从 {% data variables.product.prodname_registry %} 安装的包,并将“所有者”替换为拥有包含要安装的 gem 的存储库的用户或组织。{% ifversion ghes %} 将 `REGISTRY-URL` 替换为实例的 Rubygems 注册表的 URL 。 如果实例启用了子域隔离功能,请使用 `rubygems.HOSTNAME`。 如果实例禁用了子域隔离功能,请使用 `HOSTNAME/_registry/rubygems`。 在任一情况下,请将“主机名”替换为 {% data variables.product.prodname_ghe_server %} 实例的主机名。{% elsif ghae %} 将 `REGISTRY-URL` 替换为实例的 Rubygems 注册表 `rubygems.HOSTNAME` 的 URL。 将 HOSTNAME 替换为 {% data variables.product.product_location %} 的主机名。{% endif %} +1. For Bundler, add your {% data variables.product.prodname_dotcom %} user or organization as a source in your *Gemfile* to fetch gems from this new source. For example, you can add a new `source` block to your *Gemfile* that uses {% data variables.product.prodname_registry %} only for the packages you specify, replacing *GEM NAME* with the package you want to install from {% data variables.product.prodname_registry %} and *OWNER* with the user or organization that owns the repository containing the gem you want to install.{% ifversion ghes %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% elsif ghae %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.location.product_location %}.{% endif %} ```ruby source "https://rubygems.org" @@ -140,7 +136,7 @@ gem.metadata = { "github_repo" => "ssh://{% ifversion fpt or ghec %}github.com{% end ``` -3. 对于低于 1.7.0 的 Bundler 版本,需要添加新的全局 `source`。 有关使用 Bundler 的详细信息,请参阅 [bundler.io 文档](https://bundler.io/gemfile.html)。 +3. For Bundler versions earlier than 1.7.0, you need to add a new global `source`. For more information on using Bundler, see the [bundler.io documentation](https://bundler.io/gemfile.html). ```ruby source "https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" @@ -150,12 +146,12 @@ gem.metadata = { "github_repo" => "ssh://{% ifversion fpt or ghec %}github.com{% gem "GEM NAME" ``` -4. 安装包: +4. Install the package: ```shell $ gem install octo-gem --version "0.1.1" ``` -## 延伸阅读 +## Further reading -- [删除和还原包](/packages/learn-github-packages/deleting-and-restoring-a-package) +- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md index e8d1ec4e99..960da5c7d3 100644 --- a/translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md +++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -1,6 +1,6 @@ --- -title: 关于 GitHub Pages -intro: '您可以使用 {% data variables.product.prodname_pages %} 直接从 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的仓库托管关于自己、您的组织或您的项目的站点。' +title: About GitHub Pages +intro: 'You can use {% data variables.product.prodname_pages %} to host a website about yourself, your organization, or your project directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}.' redirect_from: - /articles/what-are-github-pages - /articles/what-is-github-pages @@ -18,129 +18,134 @@ versions: ghec: '*' topics: - Pages -ms.openlocfilehash: 1063adbe5396569110af1809a8619440e3bf106b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147507987' --- -## 关于 {% data variables.product.prodname_pages %} -{% data variables.product.prodname_pages %} 是一项静态站点托管服务,它直接从 {% data variables.product.product_name %} 上的仓库获取 HTML、CSS 和 JavaScript 文件,(可选)通过构建过程运行文件,然后发布网站。 可以在 [{% data variables.product.prodname_pages %} 示例集合](https://github.com/collections/github-pages-examples)中看到 {% data variables.product.prodname_pages %} 站点的示例。 +## About {% data variables.product.prodname_pages %} -{% ifversion fpt or ghec %} 你可以在 {% data variables.product.prodname_dotcom %} 的 `github.io` 域或自己的自定义域上托管站点。 有关详细信息,请参阅“[将自定义域与 {% data variables.product.prodname_pages %} 配合使用](/articles/using-a-custom-domain-with-github-pages)”。 +{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository on {% data variables.product.product_name %}, optionally runs the files through a build process, and publishes a website. You can see examples of {% data variables.product.prodname_pages %} sites in the [{% data variables.product.prodname_pages %} examples collection](https://github.com/collections/github-pages-examples). + +{% ifversion fpt or ghec %} +You can host your site on {% data variables.product.prodname_dotcom %}'s `github.io` domain or your own custom domain. For more information, see "[Using a custom domain with {% data variables.product.prodname_pages %}](/articles/using-a-custom-domain-with-github-pages)." {% endif %} -{% ifversion fpt or ghec %} {% data reusables.pages.about-private-publishing %} 有关详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[更改 {% data variables.product.prodname_pages %} 站点的可见性]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site){% ifversion fpt %}”。{% else %}."{% endif %} {% endif %} - -若要开始,请参阅“[创建 {% data variables.product.prodname_pages %} 站点](/articles/creating-a-github-pages-site)”。 - -{% ifversion fpt or ghes or ghec %} 组织所有者可禁止从组织的存储库发布 {% data variables.product.prodname_pages %} 站点。 有关详细信息,请参阅“[为组织管理 {% data variables.product.prodname_pages %} 站点的发布](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)”。 +{% ifversion fpt or ghec %} +{% data reusables.pages.about-private-publishing %} For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} {% endif %} -## {% data variables.product.prodname_pages %} 站点的类型 +To get started, see "[Creating a {% data variables.product.prodname_pages %} site](/articles/creating-a-github-pages-site)." -有三种类型的 {% data variables.product.prodname_pages %} 站点:项目、用户和组织。 项目站点连接到 {% data variables.product.product_name %} 上托管的特定项目,例如 JavaScript 库或配方集合。 用户和组织站点连接到 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的特定帐户。 - -若要发布用户站点,必须创建名为 {% ifversion fpt or ghec %}`.github.io`{% else %}`.`{% endif %} 的个人帐户拥有的存储库。 若要发布组织站点,必须创建名为 {% ifversion fpt or ghec %}`.github.io`{% else %}`.`{% endif %} 的组织帐户拥有的存储库。 {% ifversion fpt or ghec %}除非使用的是自定义域,否则用户和组织站点在 `http(s)://.github.io` 或 `http(s)://.github.io` 中可用。{% elsif ghae %}用户和组织站点在 `http(s)://pages./` 或 `http(s)://pages./` 上可用。{% endif %} - -项目站点的源文件与其项目存储在同一个仓库中。 {% ifversion fpt or ghec %}除非使用的是自定义域,否则项目站点在 `http(s)://.github.io/` 或 `http(s)://.github.io/` 中可用。{% elsif ghae %}项目站点在 `http(s)://pages.///` 或 `http(s)://pages.///` 上可用。{% endif %} - -{% ifversion ghec %} 如果私下发布站点,则站点的 URL 将有所不同。 有关详细信息,请参阅“[更改 {% data variables.product.prodname_pages %} 站点的可见性](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)”。 +{% ifversion fpt or ghes or ghec %} +Organization owners can disable the publication of {% data variables.product.prodname_pages %} sites from the organization's repositories. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." {% endif %} -{% ifversion fpt or ghec %} 有关自定义域如何影响站点的 URL 的详细信息,请参阅“[关于自定义域和 {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)”。 +## Types of {% data variables.product.prodname_pages %} sites + +There are three types of {% data variables.product.prodname_pages %} sites: project, user, and organization. Project sites are connected to a specific project hosted on {% data variables.product.product_name %}, such as a JavaScript library or a recipe collection. User and organization sites are connected to a specific account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. + +To publish a user site, you must create a repository owned by your personal account that's named {% ifversion fpt or ghec %}`.github.io`{% else %}`.`{% endif %}. To publish an organization site, you must create a repository owned by an organization that's named {% ifversion fpt or ghec %}`.github.io`{% else %}`.`{% endif %}. {% ifversion fpt or ghec %}Unless you're using a custom domain, user and organization sites are available at `http(s)://.github.io` or `http(s)://.github.io`.{% elsif ghae %}User and organization sites are available at `http(s)://pages./` or `http(s)://pages./`.{% endif %} + +The source files for a project site are stored in the same repository as their project. {% ifversion fpt or ghec %}Unless you're using a custom domain, project sites are available at `http(s)://.github.io/` or `http(s)://.github.io/`.{% elsif ghae %}Project sites are available at `http(s)://pages.///` or `http(s)://pages.///`.{% endif %} + +{% ifversion ghec %} +If you publish your site privately, the URL for your site will be different. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." {% endif %} -您只能为 {% data variables.product.product_name %} 上的每个帐户创建一个用户或组织站点。 项目站点(无论是组织还是个人帐户拥有)没有限制。 +{% ifversion fpt or ghec %} +For more information about how custom domains affect the URL for your site, see "[About custom domains and {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)." +{% endif %} -{% ifversion ghes %} 你的站点可用的 URL 取决于是否为 {% data variables.product.product_location %} 启用了子域隔离。 +You can only create one user or organization site for each account on {% data variables.product.product_name %}. Project sites, whether owned by an organization or a personal account, are unlimited. -| 站点类型 | 子域隔离已启用 | 子域隔离已禁用 | +{% ifversion ghes %} +The URL where your site is available depends on whether subdomain isolation is enabled for {% data variables.location.product_location %}. + +| Type of site | Subdomain isolation enabled | Subdomain isolation disabled | | ------------ | --------------------------- | ---------------------------- | -用户 | `http(s)://pages./` | `http(s):///pages/` | -组织 | `http(s)://pages./` | `http(s):///pages/` | -个人帐户拥有的项目站点 | `http(s)://pages.///` | `http(s):///pages///` -组织帐户拥有的项目站点 | `http(s)://pages.///` | `http(s):///pages///` +User | `http(s)://pages./` | `http(s):///pages/` | +Organization | `http(s)://pages./` | `http(s):///pages/` | +Project site owned by personal account | `http(s)://pages.///` | `http(s):///pages///` +Project site owned by organization account | `http(s)://pages.///` | `http(s):///pages///` -有关详细信息,请参阅“[启用子域隔离](/enterprise/admin/installation/enabling-subdomain-isolation)”或者与站点管理员联系。 +For more information, see "[Enabling subdomain isolation](/enterprise/admin/installation/enabling-subdomain-isolation)" or contact your site administrator. {% endif %} -## {% data variables.product.prodname_pages %} 站点的发布来源 +## Publishing sources for {% data variables.product.prodname_pages %} sites {% data reusables.pages.private_pages_are_public_warning %} {% data reusables.pages.pages-about-publishing-source %} -有关详细信息,请参阅“[为 GitHub Pages 站点配置发布源](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)”。 +For more information, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." {% ifversion ghec %} -## {% data variables.product.prodname_emus %} 的限制 -如果你是 {% data variables.product.prodname_managed_user %},则 {% data variables.product.prodname_pages %} 的使用是受限的。 +## Limitations for {% data variables.product.prodname_emus %} +If you're a {% data variables.enterprise.prodname_managed_user %}, your use of {% data variables.product.prodname_pages %} is limited. - - {% data variables.product.prodname_pages %} 站点只能从组织拥有的存储库发布。 - - {% data variables.product.prodname_pages %} 站点仅对企业的其他成员可见。 + - {% data variables.product.prodname_pages %} sites can only be published from repositories owned by organizations. + - {% data variables.product.prodname_pages %} sites are only visible to other members of the enterprise. + - You cannot create an organization site (a site published from a repository named `.github.io`) -有关 {% data variables.product.prodname_emus %} 的详细信息,请参阅“[关于 {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)”。 +For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)." {% endif %} -## 静态站点生成器 +## Static site generators -{% data variables.product.prodname_pages %} 会发布您推送到仓库的任何静态文件。 您可以创建自己的静态文件或使用静态站点生成器为您构建站点。 您还可以在本地或其他服务器上自定义自己的构建过程。 +{% data variables.product.prodname_pages %} publishes any static files that you push to your repository. You can create your own static files or use a static site generator to build your site for you. You can also customize your own build process locally or on another server. {% ifversion pages-custom-workflow %} -如果使用自定义生成过程或 Jekyll 以外的静态站点生成器,可以编写 {% data variables.product.prodname_actions %} 来生成和发布站点。 {% data variables.product.product_name %} 为多个静态站点生成器提供入门工作流。 有关详细信息,请参阅“[为 GitHub Pages 站点配置发布源](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)”。 +If you use a custom build process or a static site generator other than Jekyll, you can write a {% data variables.product.prodname_actions %} to build and publish your site. {% data variables.product.product_name %} provides starter workflows for several static site generators. For more information, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)." -如果从源分支发布站点,{% data variables.product.prodname_pages %} 将默认使用 Jekyll 生成站点。 如果想使用 Jekyll 以外的静态站点生成器,则建议编写 {% data variables.product.prodname_actions %} 来生成和发布站点。 否则,通过在发布源的根目录中创建一个名为 `.nojekyll` 的空文件来禁用 Jekyll 生成过程,然后按照静态站点生成器的说明在本地生成站点。 +If you publish your site from a source branch, {% data variables.product.prodname_pages %} will use Jekyll to build your site by default. If you want to use a static site generator other than Jekyll, we recommend that you write a {% data variables.product.prodname_actions %} to build and publish your site instead. Otherwise, disable the Jekyll build process by creating an empty file called `.nojekyll` in the root of your publishing source, then follow your static site generator's instructions to build your site locally. {% else %} -我们建议使用 Jekyll,它是一个静态站点生成器,内置 {% data variables.product.prodname_pages %} 支持和简化的构建流程。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_pages %} 和 Jekyll](/articles/about-github-pages-and-jekyll)”。 +We recommend Jekyll, a static site generator with built-in support for {% data variables.product.prodname_pages %} and a simplified build process. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)." -默认情况下,{% data variables.product.prodname_pages %} 将使用 Jekyll 来构建您的站点。 如果你想使用除 Jekyll 以外的静态站点生成器,通过在发布来源的根目录中创建一个名为 `.nojekyll` 的空文件来禁用 Jekyll 构建过程,然后按照静态站点生成器的说明在本地构建站点。 +{% data variables.product.prodname_pages %} will use Jekyll to build your site by default. If you want to use a static site generator other than Jekyll, disable the Jekyll build process by creating an empty file called `.nojekyll` in the root of your publishing source, then follow your static site generator's instructions to build your site locally. {% endif %} -{% data variables.product.prodname_pages %} 不支持服务器端语言,例如 PHP、Ruby 或 Python。 +{% data variables.product.prodname_pages %} does not support server-side languages such as PHP, Ruby, or Python. -## {% data variables.product.prodname_pages %} 使用限制 +## Limits on use of {% data variables.product.prodname_pages %} -{% ifversion fpt or ghec %} 2016 年 6 月 15 日后创建并使用 `github.io` 域的 {% data variables.product.prodname_pages %} 站点通过 HTTPS 提供服务。 如果您在 2016 年 6 月 15 日之前创建站点,您可以为站点的流量启用 HTTPS 支持。 有关详细信息,请参阅“[使用 HTTPS 保护 {% data variables.product.prodname_pages %}](/articles/securing-your-github-pages-site-with-https)”。 - -### 禁止使用 -{% endif %} {% data variables.product.prodname_pages %} 并非旨在用于或允许用作免费的 Web 托管服务来运行你的在线业务、电子商务站点或主要针对促进商业交易或提供商业软件即服务 (SaaS) 的任何其他网站。 {% data reusables.pages.no_sensitive_data_pages %} - -此外,你对 {% data variables.product.prodname_pages %} 的使用受 [GitHub 服务条款](/free-pro-team@latest/github/site-policy/github-terms-of-service/)的约束,包括对快速致富计划、淫秽内容以及暴力或威胁性内容或活动的限制。 - -### 使用限制 -{% data variables.product.prodname_pages %} 站点受到以下使用限制的约束: - - - {% data variables.product.prodname_pages %} 源存储库的建议限制为 1 GB。{% ifversion fpt or ghec %}有关详细信息,请参阅“[我的磁盘配额是什么?](/articles/what-is-my-disk-quota/#file-and-repository-size-limitations)”{% endif %} - - 发布的 {% data variables.product.prodname_pages %} 站点不得超过 1 GB。 {% ifversion fpt or ghec %} - - {% data variables.product.prodname_pages %} 站点的软带宽限制为每月 100 GB。 - - {% data variables.product.prodname_pages %} 站点的软限制为每小时 10 次生成。{% ifversion pages-custom-workflow %} 如果使用自定义 {% data variables.product.prodname_actions %} 工作流生成和发布站点,则此限制不适用 {% endif %} - - 为了为所有 {% data variables.product.prodname_pages %} 站点提供一致的服务质量,可能会实施速率限制。 这些速率限制无意干扰 {% data variables.product.prodname_pages %} 的合法使用。 如果你的请求触发了速率限制,你将收到相应响应,其中包含 HTTP 状态代码 `429` 以及信息性 HTML 正文。 +{% data variables.product.prodname_pages %} sites created after June 15, 2016, and using `github.io` domains are served over HTTPS. If you created your site before June 15, 2016, you can enable HTTPS support for traffic to your site. For more information, see "[Securing your {% data variables.product.prodname_pages %} with HTTPS](/articles/securing-your-github-pages-site-with-https)." -如果您的站点超出这些使用配额,我们可能无法为您的站点提供服务;或者您可能收到来自 {% data variables.contact.contact_support %} 的礼貌电子邮件,建议降低站点对服务器影响的策略,包括将第三方内容分发网络 (CDN) 置于您的站点前,利用其他 {% data variables.product.prodname_dotcom %} 功能(如发行版)或转用可能更符合您需求的其他托管服务。 +### Prohibited uses +{% endif %} +{% data variables.product.prodname_pages %} is not intended for or allowed to be used as a free web-hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS). {% data reusables.pages.no_sensitive_data_pages %} + +In addition, your use of {% data variables.product.prodname_pages %} is subject to the [GitHub Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service/), including the restrictions on get-rich-quick schemes, sexually obscene content, and violent or threatening content or activity. + +### Usage limits +{% data variables.product.prodname_pages %} sites are subject to the following usage limits: + + - {% data variables.product.prodname_pages %} source repositories have a recommended limit of 1 GB.{% ifversion fpt or ghec %} For more information, see "[What is my disk quota?](/articles/what-is-my-disk-quota/#file-and-repository-size-limitations)"{% endif %} + - Published {% data variables.product.prodname_pages %} sites may be no larger than 1 GB. +{% ifversion fpt or ghec %} + - {% data variables.product.prodname_pages %} sites have a *soft* bandwidth limit of 100 GB per month. + - {% data variables.product.prodname_pages %} sites have a *soft* limit of 10 builds per hour.{% ifversion pages-custom-workflow %} This limit does not apply if you build and publish your site with a custom {% data variables.product.prodname_actions %} workflow {% endif %} + - In order to provide consistent quality of service for all {% data variables.product.prodname_pages %} sites, rate limits may apply. These rate limits are not intended to interfere with legitimate uses of {% data variables.product.prodname_pages %}. If your request triggers rate limiting, you will receive an appropriate response with an HTTP status code of `429`, along with an informative HTML body. + +If your site exceeds these usage quotas, we may not be able to serve your site, or you may receive a polite email from {% data variables.contact.contact_support %} suggesting strategies for reducing your site's impact on our servers, including putting a third-party content distribution network (CDN) in front of your site, making use of other {% data variables.product.prodname_dotcom %} features such as releases, or moving to a different hosting service that might better fit your needs. {% endif %} -## {% data variables.product.prodname_pages %} 上的 MIME 类型 +## MIME types on {% data variables.product.prodname_pages %} -MIME 类型是服务器发送到浏览器的标头,提供有关浏览器所请求文件性质和格式的信息。 {% data variables.product.prodname_pages %} 支持数千种文件扩展名中 750 多种 MIME 类型。 支持的 MIME 类型列表是从 [mime-db 项目](https://github.com/jshttp/mime-db)生成的。 +A MIME type is a header that a server sends to a browser, providing information about the nature and format of the files the browser requested. {% data variables.product.prodname_pages %} supports more than 750 MIME types across thousands of file extensions. The list of supported MIME types is generated from the [mime-db project](https://github.com/jshttp/mime-db). -虽然无法基于每个文件或每个仓库指定自定义 MIME 类型,但您可以添加或修改 MIME 类型以在 {% data variables.product.prodname_pages %} 上使用。 有关详细信息,请参阅 [mime-db 贡献指南](https://github.com/jshttp/mime-db#adding-custom-media-types)。 +While you can't specify custom MIME types on a per-file or per-repository basis, you can add or modify MIME types for use on {% data variables.product.prodname_pages %}. For more information, see [the mime-db contributing guidelines](https://github.com/jshttp/mime-db#adding-custom-media-types). {% ifversion fpt %} -## 数据收集 +## Data collection -访问 {% data variables.product.prodname_pages %} 站点时,出于安全目的,无论访问者是否已登录 {% data variables.product.prodname_dotcom %} ,都会记录并存储访问者的 IP 地址。 有关 {% data variables.product.prodname_dotcom %} 的安全做法的详细信息,请参阅 {% data variables.product.prodname_dotcom %} 隐私声明。 +When a {% data variables.product.prodname_pages %} site is visited, the visitor's IP address is logged and stored for security purposes, regardless of whether the visitor has signed into {% data variables.product.prodname_dotcom %} or not. For more information about {% data variables.product.prodname_dotcom %}'s security practices, see {% data variables.product.prodname_dotcom %} Privacy Statement. {% endif %} -## 延伸阅读 +## Further reading -- {% data variables.product.prodname_learning %} 上的 [{% data variables.product.prodname_pages %}](https://github.com/skills/github-pages) -- “[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)” +- [{% data variables.product.prodname_pages %}](https://github.com/skills/github-pages) on {% data variables.product.prodname_learning %} +- "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)" diff --git a/translations/zh-CN/content/pages/index.md b/translations/zh-CN/content/pages/index.md index 597ed0814e..5c8d0c692f 100644 --- a/translations/zh-CN/content/pages/index.md +++ b/translations/zh-CN/content/pages/index.md @@ -1,7 +1,7 @@ --- -title: GitHub Pages 文档 +title: GitHub Pages Documentation shortTitle: GitHub Pages -intro: '了解如何直接从 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的存储库创建网站。 浏览 Jekyll 等网站生成工具并解决 {% data variables.product.prodname_pages %} 站点的问题。' +intro: 'Learn how to create a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. Explore website building tools like Jekyll and troubleshoot issues with your {% data variables.product.prodname_pages %} site.' introLinks: quickstart: /pages/quickstart overview: /pages/getting-started-with-github-pages/about-github-pages @@ -49,11 +49,4 @@ children: - /getting-started-with-github-pages - /setting-up-a-github-pages-site-with-jekyll - /configuring-a-custom-domain-for-your-github-pages-site -ms.openlocfilehash: 8f1e83a8329a023f49a73a3716a88f61b2438adb -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147643923' --- - diff --git a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md index 275a21ebe6..389f6ada15 100644 --- a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md +++ b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md @@ -1,6 +1,6 @@ --- -title: 使用 Jekyll 创建 GitHub Pages 站点 -intro: '您可以使用 Jekyll 在新仓库或现有仓库中创建 {% data variables.product.prodname_pages %} 站点。' +title: Creating a GitHub Pages site with Jekyll +intro: 'You can use Jekyll to create a {% data variables.product.prodname_pages %} site in a new or existing repository.' product: '{% data reusables.gated-features.pages %}' redirect_from: - /articles/creating-a-github-pages-site-with-jekyll @@ -14,112 +14,119 @@ versions: topics: - Pages shortTitle: Create site with Jekyll -ms.openlocfilehash: 409b2d1e21f89471e7ad92f790bc7ac67e903a62 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145129667' --- + {% data reusables.pages.org-owners-can-restrict-pages-creation %} -## 先决条件 +## Prerequisites -必须安装 Jekyll 和 Git 后才可使用 Jekyll 创建 {% data variables.product.prodname_pages %} 站点。 有关详细信息,请参阅 Jekyll 文档中的[安装](https://jekyllrb.com/docs/installation/)和“[设置 Git](/articles/set-up-git)”。 +Before you can use Jekyll to create a {% data variables.product.prodname_pages %} site, you must install Jekyll and Git. For more information, see [Installation](https://jekyllrb.com/docs/installation/) in the Jekyll documentation and "[Set up Git](/articles/set-up-git)." {% data reusables.pages.recommend-bundler %} {% data reusables.pages.jekyll-install-troubleshooting %} -## 为站点创建仓库 +## Creating a repository for your site {% data reusables.pages.new-or-existing-repo %} -{% data reusables.repositories.create_new %} {% data reusables.repositories.owner-drop-down %} {% indented_data_reference reusables.pages.emu-org-only spaces=3 %} {% data reusables.pages.create-repo-name %} {% data reusables.repositories.choose-repo-visibility %} +{% data reusables.repositories.create_new %} +{% data reusables.repositories.owner-drop-down %} +{% indented_data_reference reusables.pages.emu-org-only spaces=3 %} +{% data reusables.pages.create-repo-name %} +{% data reusables.repositories.choose-repo-visibility %} -## 创建站点 +## Creating your site {% data reusables.pages.must-have-repo-first %} {% data reusables.pages.private_pages_are_public_warning %} {% data reusables.command_line.open_the_multi_os_terminal %} -1. 如果还没有本地版存储,请导航到想要存储站点源文件的位置,将 PARENT-FOLDER 替换为要包含存储库文件夹的文件夹。 +1. If you don't already have a local copy of your repository, navigate to the location where you want to store your site's source files, replacing _PARENT-FOLDER_ with the folder you want to contain the folder for your repository. ```shell - $ cd PARENT-FOLDER + $ cd PARENT-FOLDER ``` -1. 如果尚未初始化本地 Git 存储库,请将 REPOSITORY-NAME 替换为存储库名称。 +1. If you haven't already, initialize a local Git repository, replacing _REPOSITORY-NAME_ with the name of your repository. ```shell - $ git init REPOSITORY-NAME + $ git init REPOSITORY-NAME > Initialized empty Git repository in /Users/octocat/my-site/.git/ # Creates a new folder on your computer, initialized as a Git repository ``` - 4. 将目录更改为仓库。 + 4. Change directories to the repository. ```shell - $ cd REPOSITORY-NAME + $ cd REPOSITORY-NAME # Changes the working directory ``` -{% data reusables.pages.decide-publishing-source %} {% data reusables.pages.navigate-publishing-source %} 例如,如果选择从默认分支上的 `docs` 文件夹发布站点,请创建目录并将目录更改为 `docs` 文件夹。 +{% data reusables.pages.decide-publishing-source %} +{% data reusables.pages.navigate-publishing-source %} + For example, if you chose to publish your site from the `docs` folder on the default branch, create and change directories to the `docs` folder. ```shell $ mkdir docs # Creates a new folder called docs $ cd docs ``` - 如果选择从 `gh-pages` 分支发布站点,请创建并签出 `gh-pages` 分支。 + If you chose to publish your site from the `gh-pages` branch, create and checkout the `gh-pages` branch. ```shell $ git checkout --orphan gh-pages # Creates a new branch, with no history or contents, called gh-pages, and switches to the gh-pages branch - $ git rm -rf + $ git rm -rf . # Removes the contents from your default branch from the working directory ``` -1. 若要创建新 Jekyll 站点,请使用 `jekyll new` 命令: +1. To create a new Jekyll site, use the `jekyll new` command: ```shell $ jekyll new --skip-bundle . # Creates a Jekyll site in the current directory ``` -1. 打开 Jekyll 创建的 Gemfile 文件。 -1. 将“#”添加到以 `gem "jekyll"` 开头的行首,以注释禁止此行。 -1. 编辑以 `# gem "github-pages"` 开头的行,以添加 `github-pages` gem。 将此行更改为: +1. Open the Gemfile that Jekyll created. +1. Add "#" to the beginning of the line that starts with `gem "jekyll"` to comment out this line. +1. Add the `github-pages` gem by editing the line starting with `# gem "github-pages"`. Change this line to: ```shell gem "github-pages", "~> GITHUB-PAGES-VERSION", group: :jekyll_plugins ``` - 将 GITHUB-PAGES-VERSION 替换为 `github-pages` gem 的最新支持版本。 可以在以下位置找到这个版本:“[依赖项版本](https://pages.github.com/versions/)”。 + Replace _GITHUB-PAGES-VERSION_ with the latest supported version of the `github-pages` gem. You can find this version here: "[Dependency versions](https://pages.github.com/versions/)." - 正确版本的 Jekyll 将安装为 `github-pages` gem 的依赖项。 -1. 保存并关闭 Gemfile。 -1. 从命令行中,运行 `bundle install`。 -1. (可选)对 `_config.yml` 文件进行任何必要的编辑。 当仓库托管在子目录时相对路径需要此设置。 有关详细信息,请参阅“[将子文件夹拆分到新存储库中](/github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository)”。 + The correct version Jekyll will be installed as a dependency of the `github-pages` gem. +1. Save and close the Gemfile. +1. From the command line, run `bundle install`. +1. Optionally, make any necessary edits to the `_config.yml` file. This is required for relative paths when the repository is hosted in a subdirectory. For more information, see "[Splitting a subfolder out into a new repository](/github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository)." ```yml domain: my-site.github.io # if you want to force HTTPS, specify the domain without the http at the start, e.g. example.com url: https://my-site.github.io # the base hostname and protocol for your site, e.g. http://example.com baseurl: /REPOSITORY-NAME/ # place folder name if the site is served in a subfolder ``` -1. (可选)在本地测试您的站点。 有关详细信息,请参阅“[使用 Jekyll 在本地测试 {% data variables.product.prodname_pages %} 站点](/articles/testing-your-github-pages-site-locally-with-jekyll)”。 -1. 添加并提交您的工作。 +1. Optionally, test your site locally. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)." +1. Add and commit your work. ```shell git add . git commit -m 'Initial GitHub pages site with Jekyll' ``` -1. 将 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的存储库添加为远程存储库,将 {% ifversion ghes or ghae %}HOSTNAME 替换为企业的主机名,{% endif %} 将 USER 替换为拥有该存储库的帐户{% ifversion ghes or ghae %},{% endif %}并将 REPOSITORY 替换为存储库名称 。 +1. Add your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} as a remote, replacing {% ifversion ghes or ghae %}_HOSTNAME_ with your enterprise's hostname,{% endif %} _USER_ with the account that owns the repository{% ifversion ghes or ghae %},{% endif %} and _REPOSITORY_ with the name of the repository. ```shell {% ifversion fpt or ghec %} -$ git remote add origin https://github.com/USER/REPOSITORY.git +$ git remote add origin https://github.com/USER/REPOSITORY.git {% else %} -$ git remote add origin https://HOSTNAME/USER/REPOSITORY.git +$ git remote add origin https://HOSTNAME/USER/REPOSITORY.git {% endif %} ``` -1. 将存储库推送到 {% data variables.product.product_name %},将 BRANCH 替换为所操作的分支的名称。 +1. Push the repository to {% data variables.product.product_name %}, replacing _BRANCH_ with the name of the branch you're working on. ```shell - $ git push -u origin BRANCH + $ git push -u origin BRANCH ``` -{% data reusables.pages.configure-publishing-source %} {% data reusables.pages.navigate-site-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %} {% data reusables.pages.choose-visibility %} {% data reusables.pages.visit-site %} {% data reusables.pages.check-workflow-run %} +{% data reusables.pages.configure-publishing-source %} +{% data reusables.pages.navigate-site-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.pages.sidebar-pages %} +{% data reusables.pages.choose-visibility %} +{% data reusables.pages.visit-site %} +{% data reusables.pages.check-workflow-run %} {% data reusables.pages.admin-must-push %} -## 后续步骤 +## Next steps -若要向站点添加新页面或帖子,请参阅“[使用 Jekyll 添加内容到 {% data variables.product.prodname_pages %} 站点](/articles/adding-content-to-your-github-pages-site-using-jekyll)”。 +To add a new page or post to your site, see "[Adding content to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-content-to-your-github-pages-site-using-jekyll)." -{% data reusables.pages.add-jekyll-theme %} 有关详细信息,请参阅“[使用 Jekyll 将主题添加到 {% data variables.product.prodname_pages %} 站点](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)”。 +{% data reusables.pages.add-jekyll-theme %} For more information, see "[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)." diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md index 12363a6823..32c3ec760b 100644 --- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md +++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md @@ -1,6 +1,6 @@ --- -title: 关于拉取请求合并 -intro: '可以通过将所有提交保留在功能分支中、将所有提交压缩到一个提交中,或者将个别提交从 `head` 变基为 `base` 分支,以[合并拉取请求](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)。' +title: About pull request merges +intro: 'You can [merge pull requests](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request) by retaining all the commits in a feature branch, squashing all commits into a single commit, or by rebasing individual commits from the `head` branch onto the `base` branch.' redirect_from: - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges - /articles/about-pull-request-merge-squashing @@ -14,67 +14,77 @@ versions: ghec: '*' topics: - Pull requests -ms.openlocfilehash: 512a32eb3f918653eab1127aecb70a2fbc220571 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147580437' --- -## 合并提交 +## Merge your commits {% data reusables.pull_requests.default_merge_option %} -## 压缩和合并提交 +## Squash and merge your commits {% data reusables.pull_requests.squash_and_merge_summary %} -### 合并压缩合并的消息 +### Merge message for a squash merge -{% ifversion default-merge-squash-commit-message %} 在压缩和合并时,{% data variables.product.prodname_dotcom %} 生成默认的提交消息,你可以对其进行编辑。 根据存储库的配置方式和拉取请求中的提交数(不包括合并提交),此消息可能包括拉取请求标题、拉取请求说明或有关提交的信息。 -{% else %} 在压缩和合并时,{% data variables.product.prodname_dotcom %} 生成默认的提交消息,你可以对其进行编辑。 默认消息取决于拉取请求中的提交数,不包括合并提交。 +{% ifversion default-merge-squash-commit-message %} +When you squash and merge, {% data variables.product.prodname_dotcom %} generates a default commit message, which you can edit. Depending on how the repository is configured and the number of commits in the pull request, not including merge commits, this message may include the pull request title, pull request description, or information about the commits. +{% else %} +When you squash and merge, {% data variables.product.prodname_dotcom %} generates a default commit message, which you can edit. The default message depends on the number of commits in the pull request, not including merge commits. -提交数 | 总结 | 说明 | ------------------ | ------- | ----------- | -一个提交 | 单个提交的提交消息标题,后接拉取请求编号 | 单个提交的提交消息正文 -多个提交 | 拉取请求标题,后接拉取请求编号 | 按日期顺序列出所有被压缩提交的提交消息 +Number of commits | Summary | Description | +----------------- | ------- | ----------- | +One commit | The title of the commit message for the single commit, followed by the pull request number | The body text of the commit message for the single commit +More than one commit | The pull request title, followed by the pull request number | A list of the commit messages for all of the squashed commits, in date order {% endif %} -提交数 | 总结 | 说明 | +Number of commits | Summary | Description | ----------------- | ------- | ----------- | -一个提交 | 单个提交的提交消息标题,后接拉取请求编号 | 单个提交的提交消息正文 -多个提交 | 拉取请求标题,后接拉取请求编号 | 按日期顺序列出所有被压缩提交的提交消息 +One commit | The title of the commit message for the single commit, followed by the pull request number | The body text of the commit message for the single commit +More than one commit | The pull request title, followed by the pull request number | A list of the commit messages for all of the squashed commits, in date order -{% ifversion default-merge-squash-commit-message %} 拥有存储库维护员或管理员权限的人员可以为所有已压缩提交配置其存储库的默认合并消息,以使用拉取请求标题、拉取请求标题和提交详细信息或拉取请求标题和说明。 有关详细信息,请参阅“[配置提交压缩](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)”。{% endif %} +{% ifversion default-merge-squash-commit-message %} +People with maintainer or admin access to a repository can configure their repository's default merge message for all squashed commits to use the pull request title, the pull request title and commit details, or the pull request title and description. For more information, see "[Configure commit squashing](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)".{% endif %} -{% ifversion ghes = 3.6 %} 拥有存储库管理员访问权限的人员可以将存储库配置为使用拉取请求的标题作为所有已压缩提交的默认合并消息。 有关详细信息,请参阅“[配置提交压缩](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)”。 +{% ifversion ghes = 3.6 %} +People with admin access to a repository can configure the repository to use the title of the pull request as the default merge message for all squashed commits. For more information, see "[Configure commit squashing](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)". {% endif %} -### 压缩与合并长运行分支 +### Squashing and merging a long-running branch -如果计划在合并拉取请求后继续操作[头部分支](/github/getting-started-with-github/github-glossary#head-branch),建议不要压缩与合并拉取请求。 +If you plan to continue work on the [head branch](/github/getting-started-with-github/github-glossary#head-branch) of a pull request after the pull request is merged, we recommend you don't squash and merge the pull request. -在创建拉取请求时,{% data variables.product.prodname_dotcom %} 会标识头部分支和[基础分支](/github/getting-started-with-github/github-glossary#base-branch)上的最新提交:共同的提交原型。 在压缩与合并拉取请求时,{% data variables.product.prodname_dotcom %} 会在基础分支上创建提交,其中包含自提交原型以来对头部分支所做的所有更改。 +When you create a pull request, {% data variables.product.prodname_dotcom %} identifies the most recent commit that is on both the head branch and the [base branch](/github/getting-started-with-github/github-glossary#base-branch): the common ancestor commit. When you squash and merge the pull request, {% data variables.product.prodname_dotcom %} creates a commit on the base branch that contains all of the changes you made on the head branch since the common ancestor commit. -由于此提交仅位于基础分支而不是头部分支上,因此两个分支的共同原型保持不变。 如果您继续使用头部分支,则在两个分支之间创建新的拉取请求,该拉取请求将包含自共同原型以来的所有提交,其中包括你在之前的拉取请求中压缩与合并的提交。 如果没有冲突,您可以安全地合并这些提交。 但是,此工作流会增大合并冲突的可能性。 如果您继续压缩与合并长运行头部分支的拉取请求,则必须反复解决相同的冲突。 +Because this commit is only on the base branch and not the head branch, the common ancestor of the two branches remains unchanged. If you continue to work on the head branch, then create a new pull request between the two branches, the pull request will include all of the commits since the common ancestor, including commits that you squashed and merged in the previous pull request. If there are no conflicts, you can safely merge these commits. However, this workflow makes merge conflicts more likely. If you continue to squash and merge pull requests for a long-running head branch, you will have to resolve the same conflicts repeatedly. -## 对提交进行变基和合并 +## Rebase and merge your commits {% data reusables.pull_requests.rebase_and_merge_summary %} -在以下情况下,您无法在 {% data variables.product.product_location %} 上自动变基与合并: -- 拉取请求有合并冲突。 -- 将提交从基本分支变基为遇到冲突的头部分支。 -- 变基提交被视为“不安全”,例如变基可行、不会发生冲突但会产生与合并不同的结果时。 +You aren't able to automatically rebase and merge on {% data variables.location.product_location %} when: +- The pull request has merge conflicts. +- Rebasing the commits from the base branch into the head branch runs into conflicts. +- Rebasing the commits is considered "unsafe," such as when a rebase is possible without merge conflicts but would produce a different result than a merge would. -如果您仍然要变基提交,但不能在 {% data variables.product.product_location %} 上自动变基与合并,则您必须: -- 在命令行上以本地方式将主题分支(或头部分支)变基为基本分支 -- [解决命令行上的任何合并冲突](/articles/resolving-a-merge-conflict-using-the-command-line/)。 -- 强制推送变基的命令到拉取请求的主题分支(或远端头部分支)。 +If you still want to rebase the commits but can't rebase and merge automatically on {% data variables.location.product_location %} you must: +- Rebase the topic branch (or head branch) onto the base branch locally on the command line +- [Resolve any merge conflicts on the command line](/articles/resolving-a-merge-conflict-using-the-command-line/). +- Force-push the rebased commits to the pull request's topic branch (or remote head branch). -在存储库中具有写入权限的任何人都可以使用 {% data variables.product.product_location %} 上的变基与合并按钮[合并更改](/articles/merging-a-pull-request/)。 +Anyone with write permissions in the repository, can then [merge the changes](/articles/merging-a-pull-request/) using the rebase and merge button on {% data variables.location.product_location %}. -## 延伸阅读 +## Indirect merges -- “[关于拉取请求](/articles/about-pull-requests/)” -- “[解决合并冲突](/github/collaborating-with-pull-requests/addressing-merge-conflicts)” +A pull request can be merged automatically if its head branch is directly or indirectly merged into the base branch externally. In other words, if the head branch's tip commit becomes reachable from the tip of the target branch. For example: + +* Branch `main` is at commit **C**. +* Branch `feature` has been branched off of `main` and is currently at commit **D**. This branch has a pull request targeting `main`. +* Branch `feature_2` is branched off of `feature` and is now at commit **E**. This branch also has a pull request targeting `main`. + +If pull request **E** --> `main` is merged first, pull request **D** --> `main` will be marked as merged *automatically* because all of the commits from `feature` are now reachable from `main`. Merging `feature_2` into `main` and pushing `main` to the server from the command line will mark *both* pull requests as merged. + +Pull requests in this situation will be marked as `merged` even if [branch protection rules](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-rules) have not been satisfied. + +## Further reading + +- "[About pull requests](/articles/about-pull-requests/)" +- "[Addressing merge conflicts](/github/collaborating-with-pull-requests/addressing-merge-conflicts)" diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md index 491d462e79..3d3b8216ae 100644 --- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md +++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md @@ -1,6 +1,6 @@ --- -title: 将更改提交到从复刻创建的拉取请求分支 -intro: 在拉取请求创建者的许可下,您可以在从仓库复刻创建的拉取请求分支上提交更改。 +title: Committing changes to a pull request branch created from a fork +intro: You can commit changes on a pull request branch that was created from a fork of your repository with permission from the pull request creator. redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork - /articles/committing-changes-to-a-pull-request-branch-created-from-a-fork @@ -14,44 +14,40 @@ versions: topics: - Pull requests shortTitle: Commit to PR branch from fork -ms.openlocfilehash: 123775ecbcc199382fe2082f22ad04db21fb9661 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145129628' --- -在拉取请求分支上进行提交必须满足以下条件: -- 该拉取请求分支在您拥有推送权限的仓库中打开,并且是从仓库的复刻创建的 -- 在用户拥有的复刻上 -- 拥有拉取请求创建者授予的许可 -- 没有阻止你提交的[分支限制](/github/administering-a-repository/about-protected-branches#restrict-who-can-push-to-matching-branches) +You can only make commits on pull request branches that: +- are opened in a repository that you have push access to and that were created from a fork of that repository +- are on a user-owned fork +- have permission granted from the pull request creator +- don't have [branch restrictions](/github/administering-a-repository/about-protected-branches#restrict-who-can-push-to-matching-branches) that will prevent you from committing -只有创建拉取请求的用户才能授予您向用户拥有的复刻推送提交的权限。 有关详细信息,请参阅“[允许更改从复刻创建的拉取请求分支](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)”。 +Only the user who created the pull request can give you permission to push commits to the user-owned fork. For more information, see "[Allowing changes to a pull request branch created from a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)." {% note %} -**注意:** 还可以通过创建自己的存储库复刻副本(或复刻)并将更改提交到创建原始拉取请求更改的头部分支,从而通过 {% data variables.product.product_location %} 向存储库复刻的拉取请求分支进行提交。 有关一些一般准则,请参阅“[从复刻创建拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)”。 +**Note:** You can also make commits to a pull request branch from a fork of your repository through {% data variables.location.product_location %} by creating your own copy (or fork) of the fork of your repository and committing changes to the same head branch that the original pull request changes were created on. For some general guidelines, see "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)." {% endnote %} -1. 在 {% data variables.product.product_name %} 上,导航到创建拉取请求分支的复刻(或仓库副本)的主页面。 -{% data reusables.repositories.copy-clone-url %} {% data reusables.command_line.open_the_multi_os_terminal %} {% tip %} +1. On {% data variables.product.product_name %}, navigate to the main page of the fork (or copy of your repository) where the pull request branch was created. +{% data reusables.repositories.copy-clone-url %} +{% data reusables.command_line.open_the_multi_os_terminal %} + {% tip %} - **提示:** 如果要使用 {% data variables.product.prodname_desktop %} 克隆复刻,请参阅“[将存储库克隆到 {% data variables.product.prodname_desktop %}](/articles/cloning-a-repository/#cloning-a-repository-to-github-desktop)。” + **Tip:** If you prefer to clone the fork using {% data variables.product.prodname_desktop %}, then see "[Cloning a repository to {% data variables.product.prodname_desktop %}](/articles/cloning-a-repository/#cloning-a-repository-to-github-desktop)." {% endtip %} -4. 将当前工作目录更改为要下载克隆目录的位置。 +4. Change the current working directory to the location where you want to download the cloned directory. ```shell $ cd open-source-projects ``` -5. 键入 `git clone`,然后粘贴在步骤 3 中复制的 URL。 +5. Type `git clone`, and then paste the URL you copied in Step 3. ```shell - $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY + $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY ``` -6. 按 **Enter**。 将创建您的本地克隆。 +6. Press **Enter**. Your local clone will be created. ```shell - $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY + $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY > Cloning into `FORK-OF-THE-REPOSITORY`... > remote: Counting objects: 10, done. > remote: Compressing objects: 100% (8/8), done. @@ -60,26 +56,27 @@ ms.locfileid: '145129628' ``` {% tip %} - **提示:** 错误消息“致命错误: 目标路径 'REPOSITORY-NAME' 已存在并且不是空目录”表示你当前的工作目录已包含同名存储库。 要解决此错误,必须将复刻克隆到另一个目录中。 + **Tip:** The error message "fatal: destination path 'REPOSITORY-NAME' already exists and is not an empty directory" means that your current working directory already contains a repository with the same name. To resolve the error, you must clone the fork in a different directory. {% endtip %} -7. 导航到新的克隆仓库。 +7. Navigate into your new cloned repository. ```shell - $ cd FORK-OF-THE-REPOSITORY + $ cd FORK-OF-THE-REPOSITORY ``` -7. 将分支切换到进行原始更改的拉取请求的比较分支。 如果您导航到原始拉取请求,您将在拉取请求的顶部看到比较分支。 -![compare-branch-example](/assets/images/help/pull_requests/compare-branch-example.png) 在此示例中,比较分支为 `test-branch`: +7. Switch branches to the compare branch of the pull request where the original changes were made. If you navigate to the original pull request, you'll see the compare branch at the top of the pull request. +![compare-branch-example](/assets/images/help/pull_requests/compare-branch-example.png) + In this example, the compare branch is `test-branch`: ```shell - $ git checkout test-branch + $ git checkout TEST-BRANCH ``` {% tip %} - **提示:** 有关拉取请求分支的详细信息(包括示例),请参阅“[创建拉取请求](/articles/creating-a-pull-request#changing-the-branch-range-and-destination-repository)”。 + **Tip:** For more information about pull request branches, including examples, see "[Creating a Pull Request](/articles/creating-a-pull-request#changing-the-branch-range-and-destination-repository)." {% endtip %} -8. 现在,您可以使用此分支执行任何操作。 您可以向该分支推送新提交、运行一些本地测试或将其他分支合并到其中。 根据需要进行修改。 -9. 在更改提交到拉取请求的头部分支后,您可以将更改直接推送到原始拉取请求。 在此示例中,头部分支为 `test-branch`: +8. At this point, you can do anything you want with this branch. You can push new commits to it, run some local tests, or merge other branches into the branch. Make modifications as you like. +9. After you commit your changes to the head branch of the pull request you can push your changes up to the original pull request directly. In this example, the head branch is `test-branch`: ```shell $ git push origin test-branch > Counting objects: 32, done. @@ -87,12 +84,12 @@ ms.locfileid: '145129628' > Compressing objects: 100% (26/26), done. > Writing objects: 100% (29/29), 74.94 KiB | 0 bytes/s, done. > Total 29 (delta 8), reused 0 (delta 0) - > To https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY.git - > 12da2e9..250e946 test-branch -> test-branch + > To https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY.git + > 12da2e9..250e946 TEST-BRANCH -> TEST-BRANCH ``` -您的新提交将反映在 {% data variables.product.product_location %} 上的原始拉取请求中。 +Your new commits will be reflected on the original pull request on {% data variables.location.product_location %}. -## 深入阅读 +## Further Reading -- “[关于复刻](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)” +- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index ed8a455560..5ecd5f08d3 100644 --- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -30,7 +30,7 @@ shortTitle: Review dependency changes {% ifversion ghec %}Before you can use dependency review in a private repository, you must enable the dependency graph. For more information, see "[Exploring the dependencies of a repository](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)."{% endif %} -{% ifversion ghes %} Before you can use dependency review, you must enable the dependency graph and connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +{% ifversion ghes %} Before you can use dependency review, you must enable the dependency graph and connect {% data variables.location.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} Dependency review allows you to "shift left". You can use the provided predictive information to catch vulnerable dependencies before they hit production. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md index 8a932592e4..a881dd52d4 100644 --- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md +++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md @@ -1,6 +1,6 @@ --- -title: 关于分叉 -intro: 复刻是您管理的仓库的副本。 复刻用于更改项目而不影响原始仓库。 您可以通过拉取请求从原始仓库提取更新,或者提交更改到原始仓库。 +title: About forks +intro: A fork is a copy of a repository that you manage. Forks let you make changes to a project without affecting the original repository. You can fetch updates from or submit changes to the original repository with pull requests. redirect_from: - /github/collaborating-with-issues-and-pull-requests/working-with-forks/about-forks - /articles/about-forks @@ -13,39 +13,33 @@ versions: ghec: '*' topics: - Pull requests -ms.openlocfilehash: d7564598bca7c75a4861f4cc2d20b3f7a986f730 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145130068' --- -复刻仓库类似于复制仓库,主要有两点差异: +Forking a repository is similar to copying a repository, with two major differences: -* 可以使用拉取请求来建议从用户拥有的分支到其 GitHub 实例中的原始存储库(也称为“上游”存储库)的更改。 -* 您可以通过同步复刻与上游仓库,将更改从上游仓库提交到本地复刻。 +* You can use a pull request to suggest changes from your user-owned fork to the original repository in its GitHub instance, also known as the *upstream* repository. +* You can bring changes from the upstream repository to your local fork by synchronizing your fork with the upstream repository. {% data reusables.repositories.you-can-fork %} {% ifversion fpt or ghec %} -如果您是 {% data variables.product.prodname_emu_enterprise %} 的成员,则可以复刻的存储库有进一步的限制。 {% data reusables.enterprise-accounts.emu-forks %} 有关详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[关于 {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}”。{% else %}."{% endif %} +If you're a member of a {% data variables.enterprise.prodname_emu_enterprise %}, there are further restrictions on the repositories you can fork. {% data reusables.enterprise-accounts.emu-forks %} For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} {% endif %} {% data reusables.repositories.desktop-fork %} -删除复刻不会删除原始上游仓库。 可以对分支进行任何所需的更改(添加协作者、重命名文件、生成 {% data variables.product.prodname_pages %}),而不影响原始版本。{% ifversion fpt or ghec %} 无法还原已删除的分支存储库。 有关详细信息,请参阅“[还原已删除的存储库](/articles/restoring-a-deleted-repository)”。{% endif %} +Deleting a fork will not delete the original upstream repository. You can make any changes you want to your fork—add collaborators, rename files, generate {% data variables.product.prodname_pages %}—with no effect on the original.{% ifversion fpt or ghec %} You cannot restore a deleted forked repository. For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %} -在开源项目中,复刻常用于迭代想法或更改,然后将其提交回上游仓库。 在用户拥有的复刻中进行更改,然后打开拉取请求以比较您的工作与上游仓库,便可允许对上游仓库具有推送权限的任何推送更改到拉取请求分支(包括删除分支)。 这可加速协作,让仓库维护员在合并之前于本地从用户拥有的复刻对拉取请求进行提交或运行测试。 不可向组织拥有的复刻授予推送权限。 +In open source projects, forks are often used to iterate on ideas or changes before they are offered back to the upstream repository. When you make changes in your user-owned fork and open a pull request that compares your work to the upstream repository, you can give anyone with push access to the upstream repository permission to push changes to your pull request branch (including deleting the branch). This speeds up collaboration by allowing repository maintainers the ability to make commits or run tests locally to your pull request branch from a user-owned fork before merging. You cannot give push permissions to a fork owned by an organization. {% data reusables.repositories.private_forks_inherit_permissions %} -如果以后要从现有仓库的内容创建新仓库,但不想合并上游更改,您可以复制仓库 ,或者,如果该仓库是模板,您可以使用该仓库作为模板。 有关详细信息,请参阅“[复制存储库](/articles/duplicating-a-repository)”和“[从模板创建存储库](/articles/creating-a-repository-from-a-template)”。 +If you want to create a new repository from the contents of an existing repository but don't want to merge your changes to the upstream in the future, you can duplicate the repository or, if the repository is a template, you can use the repository as a template. For more information, see "[Duplicating a repository](/articles/duplicating-a-repository)" and "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)". -## 延伸阅读 +## Further reading -- “[关于协作开发模型](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)” -- “[从分支创建拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)” -- [开源指南](https://opensource.guide/){% ifversion fpt or ghec %} +- "[About collaborative development models](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)" +- "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)" +- [Open Source Guides](https://opensource.guide/){% ifversion fpt or ghec %} - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %} diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md index 94a6d525f0..d97744b5d7 100644 --- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md +++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md @@ -1,6 +1,6 @@ --- -title: 同步复刻 -intro: 同步仓库的复刻以通过上游仓库使其保持最新。 +title: Syncing a fork +intro: Sync a fork of a repository to keep it up-to-date with the upstream repository. redirect_from: - /github/collaborating-with-issues-and-pull-requests/working-with-forks/syncing-a-fork - /articles/syncing-a-fork @@ -19,48 +19,44 @@ versions: topics: - Pull requests permissions: People with write access for a forked repository can sync the fork to the upstream repository. -ms.openlocfilehash: 7c4c97c271e6e151c509a33e53c126190e8e5feb -ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/12/2022 -ms.locfileid: '147540832' --- -## 从 Web UI 同步分叉分支 + +## Syncing a fork branch from the web UI {% ifversion syncing-fork-web-ui %} -1. 在 {% data variables.product.product_name %} 上,导航到您想要与上游版本库同步的复刻仓库主页。 -2. 选择“同步分支”下拉菜单。 - ![突出显示“同步分支”下拉菜单](/assets/images/help/repository/sync-fork-dropdown.png) -3. 查看有关上游存储库提交的详细信息,然后单击“更新分支”。 - ![突出显示“更新分支”按钮的同步分支模式](/assets/images/help/repository/update-branch-button.png) {% else %} -1. 在 {% data variables.product.product_name %} 上,导航到您想要与上游版本库同步的复刻仓库主页。 -2. 选择“提取上游”下拉菜单。 - ![“提取上游”下拉菜单](/assets/images/help/repository/fetch-upstream-drop-down.png) -3. 查看有关上游存储库提交的详细信息,然后单击“提取并合并”。 - ![“提取并合并”按钮](/assets/images/help/repository/fetch-and-merge-button.png){% endif %} +1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository. +2. Select the **Sync fork** dropdown. + !["Sync fork" dropdown emphasized](/assets/images/help/repository/sync-fork-dropdown.png) +3. Review the details about the commits from the upstream repository, then click **Update branch**. + ![Sync fork modal with "Update branch" button emphasized](/assets/images/help/repository/update-branch-button.png) +{% else %} +1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository. +2. Select the **Fetch upstream** dropdown. + !["Fetch upstream" drop-down](/assets/images/help/repository/fetch-upstream-drop-down.png) +3. Review the details about the commits from the upstream repository, then click **Fetch and merge**. + !["Fetch and merge" button](/assets/images/help/repository/fetch-and-merge-button.png){% endif %} -如果上游仓库的更改导致冲突,{% data variables.product.company_short %} 将提示您创建拉取请求以解决冲突。 +If the changes from the upstream repository cause conflicts, {% data variables.product.company_short %} will prompt you to create a pull request to resolve the conflicts. -## 使用 {% data variables.product.prodname_cli %} 同步分叉分支 +## Syncing a fork branch with the {% data variables.product.prodname_cli %} -{% data reusables.cli.about-cli %} 若要详细了解 {% data variables.product.prodname_cli %},请参阅“[关于 {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)”。 +{% data reusables.cli.about-cli %} To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." -要从其父级更新远程分支,请使用 `gh repo sync -b BRANCHNAME` 子命令并提供分叉和分支名作为参数。 +To update the remote fork from its parent, use the `gh repo sync -b BRANCHNAME` subcommand and supply your fork and branch name as arguments. ```shell -$ gh repo sync owner/cli-fork -b BRANCHNAME +$ gh repo sync owner/cli-fork -b BRANCH_NAME ``` -如果上游存储库的更改导致冲突,则 {% data variables.product.prodname_cli %} 无法同步。你可以设置 `-force` 标志以覆盖目标分支。 +If the changes from the upstream repository cause conflict then the {% data variables.product.prodname_cli %} can't sync. You can set the `-force` flag to overwrite the destination branch. -## 从命令行同步分叉分支 +## Syncing a fork branch from the command line -必须先在 Git 中[配置指向上游存储库的远程库](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork),然后才能将分支与上游存储库同步。 +Before you can sync your fork with an upstream repository, you must [configure a remote that points to the upstream repository](/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork) in Git. {% data reusables.command_line.open_the_multi_os_terminal %} -2. 将当前工作目录更改为您的本地仓库。 -3. 从上游仓库获取分支及其各自的提交。 对 `BRANCHNAME` 的提交将保存在本地分支 `upstream/BRANCHNAME` 中。 +2. Change the current working directory to your local project. +3. Fetch the branches and their respective commits from the upstream repository. Commits to `BRANCHNAME` will be stored in the local branch `upstream/BRANCHNAME`. ```shell $ git fetch upstream @@ -68,18 +64,18 @@ $ gh repo sync owner/cli-fork -b BRANCHNAME > remote: Compressing objects: 100% (53/53), done. > remote: Total 62 (delta 27), reused 44 (delta 9) > Unpacking objects: 100% (62/62), done. - > From https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY + > From https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY > * [new branch] main -> upstream/main ``` -4. 签出分支的本地默认分支,在本例中,我们使用 `main`。 +4. Check out your fork's local default branch - in this case, we use `main`. ```shell $ git checkout main > Switched to branch 'main' ``` -5. 将上游默认分支(在本例中为 `upstream/main`)的更改合并到本地默认分支中。 这会使复刻的默认分支与上游仓库同步,而不会丢失本地更改。 +5. Merge the changes from the upstream default branch - in this case, `upstream/main` - into your local default branch. This brings your fork's default branch into sync with the upstream repository, without losing your local changes. ```shell $ git merge upstream/main @@ -92,7 +88,7 @@ $ gh repo sync owner/cli-fork -b BRANCHNAME > create mode 100644 README.md ``` - 如果本地分支没有任何唯一提交,Git 将执行快速转发。 有关详细信息,请参阅 Git 文档中的[基本分支和合并](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging)。 + If your local branch didn't have any unique commits, Git will perform a fast-forward. For more information, see [Basic Branching and Merging](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging) in the Git documentation. ```shell $ git merge upstream/main > Updating 34e91da..16c56ad @@ -100,10 +96,10 @@ $ gh repo sync owner/cli-fork -b BRANCHNAME > README.md | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) ``` - 如果本地分支具有唯一提交,则可能需要解决冲突。 有关详细信息,请参阅“[解决合并冲突](/github/collaborating-with-pull-requests/addressing-merge-conflicts)”。 + If your local branch had unique commits, you may need to resolve conflicts. For more information, see "[Addressing merge conflicts](/github/collaborating-with-pull-requests/addressing-merge-conflicts)." {% tip %} -**提示**:同步分支只更新存储库的本地副本。 若要在 {% data variables.product.product_location %} 上更新分支,必须[推送更改](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)。 +**Tip**: Syncing your fork only updates your local copy of the repository. To update your fork on {% data variables.location.product_location %}, you must [push your changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/). {% endtip %} diff --git a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md index eae99858d1..4cbd1eee7d 100644 --- a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md +++ b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md @@ -1,78 +1,73 @@ --- -title: 更改提交消息 +title: Changing a commit message redirect_from: - /articles/can-i-delete-a-commit-message - /articles/changing-a-commit-message - /github/committing-changes-to-your-project/changing-a-commit-message - /github/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message -intro: '如果提交消息中包含不明确、不正确或敏感的信息,您可以在本地修改它,然后将含有新消息的新提交推送到 {% data variables.product.product_name %}。 您还可以更改提交消息以添加遗漏的信息。' +intro: 'If a commit message contains unclear, incorrect, or sensitive information, you can amend it locally and push a new commit with a new message to {% data variables.product.product_name %}. You can also change a commit message to add missing information.' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' -ms.openlocfilehash: fa4966da0fe443e6635b43fc9b3b11108d57cf6e -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145129461' --- -## 重写最近的提交消息 +## Rewriting the most recent commit message -可以使用 `git commit --amend` 命令更改最新的提交消息。 +You can change the most recent commit message using the `git commit --amend` command. -在 Git 中,提交消息的文本是提交的一部分。 更改提交消息将更改提交 ID - 即用于命名提交的 SHA1 校验和。 实际上,您是创建一个新提交以替换旧提交。 +In Git, the text of the commit message is part of the commit. Changing the commit message will change the commit ID--i.e., the SHA1 checksum that names the commit. Effectively, you are creating a new commit that replaces the old one. -## 提交尚未推送上线 +## Commit has not been pushed online -如果提交仅存在于你的本地存储库中,尚未推送到 {% data variables.product.product_location %},则可使用 `git commit --amend` 命令修改提交消息。 +If the commit only exists in your local repository and has not been pushed to {% data variables.location.product_location %}, you can amend the commit message with the `git commit --amend` command. -1. 在命令行上,导航到包含要修改的提交的仓库。 -2. 键入 `git commit --amend`,然后按“Enter”。 -3. 在文本编辑器中编辑提交消息,然后保存该提交。 - - 通过在提交中添加尾行可添加合作作者。 有关详细信息,请参阅“[创建具有多个作者的提交](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)”。 +1. On the command line, navigate to the repository that contains the commit you want to amend. +2. Type `git commit --amend` and press **Enter**. +3. In your text editor, edit the commit message, and save the commit. + - You can add a co-author by adding a trailer to the commit. For more information, see "[Creating a commit with multiple authors](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)." {% ifversion fpt or ghec %} - - 通过在提交中添加尾行可创建代表组织的提交。 有关详细信息,请参阅“[代表组织创建提交](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization)”{% endif %} + - You can create commits on behalf of your organization by adding a trailer to the commit. For more information, see "[Creating a commit on behalf of an organization](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization)" +{% endif %} -在下次推送时,新的提交和消息将显示在 {% data variables.product.product_location %} 上。 +The new commit and message will appear on {% data variables.location.product_location %} the next time you push. {% tip %} -通过更改 `core.editor` 设置可更改 Git 的默认文本编辑器。 有关详细信息,请参阅 Git 手册中的“[基本客户端配置](https://git-scm.com/book/en/Customizing-Git-Git-Configuration#_basic_client_configuration)”。 +You can change the default text editor for Git by changing the `core.editor` setting. For more information, see "[Basic Client Configuration](https://git-scm.com/book/en/Customizing-Git-Git-Configuration#_basic_client_configuration)" in the Git manual. {% endtip %} -## 修改旧提交或多个提交的消息 +## Amending older or multiple commit messages -如果您已将提交推送到 {% data variables.product.product_location %},则必须强制推送含有修正消息的提交。 +If you have already pushed the commit to {% data variables.location.product_location %}, you will have to force push a commit with an amended message. {% warning %} -我们很不提倡强制推送,因为这会改变仓库的历史记录。 如果强制推送,已克隆仓库的人员必须手动修复其本地历史记录。 有关详细信息,请参阅 Git 手册中的“[从上游变基恢复](https://git-scm.com/docs/git-rebase#_recovering_from_upstream_rebase)”。 +We strongly discourage force pushing, since this changes the history of your repository. If you force push, people who have already cloned your repository will have to manually fix their local history. For more information, see "[Recovering from upstream rebase](https://git-scm.com/docs/git-rebase#_recovering_from_upstream_rebase)" in the Git manual. {% endwarning %} -**更改最近推送提交的消息** +**Changing the message of the most recently pushed commit** -1. 按照[上述步骤](/articles/changing-a-commit-message#commit-has-not-been-pushed-online)修改提交消息。 -2. 使用 `push --force-with-lease` 命令强制推送旧提交。 +1. Follow the [steps above](/articles/changing-a-commit-message#commit-has-not-been-pushed-online) to amend the commit message. +2. Use the `push --force-with-lease` command to force push over the old commit. ```shell - $ git push --force-with-lease origin example-branch + $ git push --force-with-lease origin EXAMPLE-BRANCH ``` -**更改旧提交或多个提交的消息** +**Changing the message of older or multiple commit messages** -如果需要修改多个提交或旧提交的消息,您可以使用交互式变基,然后强制推送以更改提交历史记录。 +If you need to amend the message for multiple commits or an older commit, you can use interactive rebase, then force push to change the commit history. -1. 在命令行上,导航到包含要修改的提交的仓库。 -2. 使用 `git rebase -i HEAD~n` 命令在默认文本编辑器中显示最后一次 `n` 提交的列表。 +1. On the command line, navigate to the repository that contains the commit you want to amend. +2. Use the `git rebase -i HEAD~n` command to display a list of the last `n` commits in your default text editor. ```shell # Displays a list of the last 3 commits on the current branch $ git rebase -i HEAD~3 ``` - 此列表将类似于以下内容: + The list will look similar to the following: ```shell pick e499d89 Delete CNAME @@ -97,33 +92,33 @@ ms.locfileid: '145129461' # # Note that empty commits are commented out ``` -3. 在要更改的每个提交消息的前面,将 `pick` 替换为 `reword`。 +3. Replace `pick` with `reword` before each commit message you want to change. ```shell pick e499d89 Delete CNAME reword 0c39034 Better README reword f7fde4a Change the commit message but push the same commit. ``` -4. 保存并关闭提交列表文件。 -5. 在每个生成的提交文件中,键入新的提交消息,保存文件,然后关闭它。 -6. 准备好将更改推送到 GitHub 时,请使用 push - force 命令强制推送旧提交。 +4. Save and close the commit list file. +5. In each resulting commit file, type the new commit message, save the file, and close it. +6. When you're ready to push your changes to GitHub, use the push --force command to force push over the old commit. ```shell -$ git push --force origin example-branch +$ git push --force origin EXAMPLE-BRANCH ``` -有关交互式变基的详细信息,请参阅 Git 手册中的“[交互式模式](https://git-scm.com/docs/git-rebase#_interactive_mode)”。 +For more information on interactive rebase, see "[Interactive mode](https://git-scm.com/docs/git-rebase#_interactive_mode)" in the Git manual. {% tip %} -如前文所述,修改提交消息会生成含有新 ID 的新提交。 但是,在这种情况下,该修改提交的每个后续提交也会获得一个新 ID,因为每个提交也包含其父提交的 ID。 +As before, amending the commit message will result in a new commit with a new ID. However, in this case, every commit that follows the amended commit will also get a new ID because each commit also contains the id of its parent. {% endtip %} {% warning %} -如果您的提交消息中包含敏感信息,则强制推送修改后的提交可能不会导致从 {% data variables.product.product_name %} 中删除原提交。 旧提交不会成为后续克隆的一部分;但是,它可能仍然缓存在 {% data variables.product.product_name %} 上,并且可通过提交 ID 访问。 您必须联系 {% data variables.contact.contact_support %} 并提供旧提交 ID,以便从远程仓库中清除它。 +If you have included sensitive information in a commit message, force pushing a commit with an amended commit may not remove the original commit from {% data variables.product.product_name %}. The old commit will not be a part of a subsequent clone; however, it may still be cached on {% data variables.product.product_name %} and accessible via the commit ID. You must contact {% data variables.contact.contact_support %} with the old commit ID to have it purged from the remote repository. {% endwarning %} -## 延伸阅读 +## Further reading -* [对提交签名](/articles/signing-commits) +* "[Signing commits](/articles/signing-commits)" diff --git a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md index 88d2e5c2ad..e4cf27cb8f 100644 --- a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md +++ b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md @@ -1,6 +1,6 @@ --- -title: 代表组织创建提交 -intro: '通过在提交消息中添加尾行可代表组织创建提交。 归属于组织的提交应包含 {% data variables.product.product_name %} 上的 `on-behalf-of` 徽章。' +title: Creating a commit on behalf of an organization +intro: 'You can create commits on behalf of an organization by adding a trailer to the commit''s message. Commits attributed to an organization include an `on-behalf-of` badge on {% data variables.product.product_name %}.' redirect_from: - /articles/creating-a-commit-on-behalf-of-an-organization - /github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization @@ -9,33 +9,27 @@ versions: fpt: '*' ghec: '*' shortTitle: On behalf of an organization -ms.openlocfilehash: 31b8a6b8d1824fa960fb32fa5fd7b4c28625037c -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145129453' --- {% note %} -**注意:** 代表组织创建提交的功能目前为公开 beta 版本,可能会有所更改。 +**Note:** The ability to create a commit on behalf of an organization is currently in public beta and is subject to change. {% endnote %} -要代表组织创建提交: +To create commits on behalf of an organization: -- 您必须是尾行所述组织的成员 -- 您必须对提交签名 -- 您的提交电子邮件地址和组织电子邮件地址必须位于经组织验证的域中 -- 提交消息必须以提交尾部 `on-behalf-of: @org ` 结束 - - `org` 是组织的登录名 - - `name@organization.com` 在组织的域中 +- you must be a member of the organization indicated in the trailer +- you must sign the commit +- your commit email and the organization email must be in a domain verified by the organization +- your commit message must end with the commit trailer `on-behalf-of: @org ` + - `org` is the organization's login + - `name@organization.com` is in the organization's domain -组织可以将 `name@organization.com` 电子邮件用作开放源代码工作的公共联络点。 +Organizations can use the `name@organization.com` email as a public point of contact for open source efforts. -## 在命令行上使用 `on-behalf-of` 徽章创建提交 +## Creating commits with an `on-behalf-of` badge on the command line -1. 输入提交消息以及简短、有意义的更改描述。 在提交描述后,不要加上右引号,而是添加两个空行。 +1. Type your commit message and a short, meaningful description of your changes. After your commit description, instead of a closing quotation, add two empty lines. ```shell $ git commit -m "Refactor usability tests. > @@ -43,38 +37,38 @@ ms.locfileid: '145129453' ``` {% tip %} - **提示:** 如果在命令行上使用文本编辑器来键入提交消息,请确保在提交描述的末尾和 `on-behalf-of:` 提交尾部之间有两个换行符。 + **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `on-behalf-of:` commit trailer. {% endtip %} -2. 在提交消息的下一行,键入 `on-behalf-of: @org `,然后是右引号。 +2. On the next line of the commit message, type `on-behalf-of: @org `, then a closing quotation mark. ```shell $ git commit -m "Refactor usability tests. > > - on-behalf-of: @org <name@organization.com>" + on-behalf-of: @ORG NAME@ORGANIZATION.COM" ``` -在下次推送时,新的提交、消息和徽章将显示在 {% data variables.product.product_location %} 上。 有关详细信息,请参阅“[将更改推送到远程存储库](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)”。 +The new commit, message, and badge will appear on {% data variables.location.product_location %} the next time you push. For more information, see "[Pushing changes to a remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)." -## 在 {% data variables.product.product_name %} 上使用 `on-behalf-of` 徽章创建提交 +## Creating commits with an `on-behalf-of` badge on {% data variables.product.product_name %} -在 {% data variables.product.product_name %} 上使用 Web 编辑器对文件进行更改后,你可以通过将 `on-behalf-of:` 尾部添加到提交的消息中来代表组织创建提交。 +After you've made changes in a file using the web editor on {% data variables.product.product_name %}, you can create a commit on behalf of your organization by adding an `on-behalf-of:` trailer to the commit's message. -1. 进行更改后,在页面底部键入简短、有意义的提交消息,以描述您所做的更改。 - ![更改的提交消息](/assets/images/help/repository/write-commit-message-quick-pull.png) +1. After making your changes, at the bottom of the page, type a short, meaningful commit message that describes the changes you made. + ![Commit message for your change](/assets/images/help/repository/write-commit-message-quick-pull.png) -2. 在提交消息下方的文本框中,添加 `on-behalf-of: @org `。 +2. In the text box below your commit message, add `on-behalf-of: @org `. - ![第二个提交消息文本框中的提交消息代表尾行示例](/assets/images/help/repository/write-commit-message-on-behalf-of-trailer.png) -4. 单击“提交更改”或“建议更改” 。 + ![Commit message on-behalf-of trailer example in second commit message text box](/assets/images/help/repository/write-commit-message-on-behalf-of-trailer.png) +4. Click **Commit changes** or **Propose changes**. -新的提交、消息和徽章将显示在 {% data variables.product.product_location %} 上。 +The new commit, message, and badge will appear on {% data variables.location.product_location %}. -## 延伸阅读 +## Further reading -- [在个人资料中查看贡献](/articles/viewing-contributions-on-your-profile) -- [为什么我的贡献未显示在我的个人资料上?](/articles/why-are-my-contributions-not-showing-up-on-my-profile) -- [查看项目的参与者](/articles/viewing-a-projects-contributors) -- [更改提交消息](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message) +- "[Viewing contributions on your profile](/articles/viewing-contributions-on-your-profile)" +- "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" +- "[Viewing a project’s contributors](/articles/viewing-a-projects-contributors)" +- "[Changing a commit message](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message)" diff --git a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md index 7581427bb9..a1ac806368 100644 --- a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md +++ b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md @@ -1,6 +1,6 @@ --- -title: 创建有多个作者的提交 -intro: '通过在提交消息中添加一个或多个 `Co-authored-by` 尾行,可将提交归属于多个作者。 合作提交在 {% data variables.product.product_name %}{% ifversion ghes or ghae %} 上可见,并且可包含在个人资料贡献图和存储库统计信息中{% endif %}。' +title: Creating a commit with multiple authors +intro: 'You can attribute a commit to more than one author by adding one or more `Co-authored-by` trailers to the commit''s message. Co-authored commits are visible on {% data variables.product.product_name %}{% ifversion ghes or ghae %} and can be included in the profile contributions graph and the repository''s statistics{% endif %}.' redirect_from: - /articles/creating-a-commit-with-multiple-authors - /github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors @@ -11,86 +11,80 @@ versions: ghae: '*' ghec: '*' shortTitle: With multiple authors -ms.openlocfilehash: 4aa5b707e75480ead830e680151064db5f278557 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145129450' --- -## 必需的合作作者信息 +## Required co-author information -向提交添加合作作者之前,您必须知道用于每个合作作者的适当电子邮件地址。 为使合作作者的提交计为贡献,您必须使用与他们在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的帐户相关联的电子邮件。 +Before you can add a co-author to a commit, you must know the appropriate email to use for each co-author. For the co-author's commit to count as a contribution, you must use the email associated with their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. {% ifversion fpt or ghec %} -如果用户选择将其电子邮件地址保密,则应使用其 {% data variables.product.product_name %} 提供的 `no-reply` 电子邮件地址来保护其隐私。 否则,合作作者的电子邮件地址将在提交消息中公开。 如果要保持电子邮件地址的私密性,可选择使用 {% data variables.product.product_name %} 为 Git 操作提供的 `no-reply` 电子邮件地址,并要求其他共同作者在提交尾行中列出你的 `no-reply` 电子邮件地址。 +If a person chooses to keep their email address private, you should use their {% data variables.product.product_name %}-provided `no-reply` email to protect their privacy. Otherwise, the co-author's email will be available to the public in the commit message. If you want to keep your email private, you can choose to use a {% data variables.product.product_name %}-provided `no-reply` email for Git operations and ask other co-authors to list your `no-reply` email in commit trailers. -有关详细信息,请参阅“[设置提交电子邮件地址](/articles/setting-your-commit-email-address)”。 +For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)." {% tip %} - 提示:通过分享此信息可帮助共同作者找到其首选电子邮件地址: - - 若要查找 {% data variables.product.product_name %} 提供的 `no-reply` 电子邮件地址,请导航至“将我的电子邮件地址保密”下的电子邮件设置页面。 - - 若要在计算机上查找用于配置 Git 的电子邮件地址,请在命令行上运行 `git config user.email`。 + **Tip:** You can help a co-author find their preferred email address by sharing this information: + - To find your {% data variables.product.product_name %}-provided `no-reply` email, navigate to your email settings page under "Keep my email address private." + - To find the email you used to configure Git on your computer, run `git config user.email` on the command line. {% endtip %} {% endif %} -## 使用 {% data variables.product.prodname_desktop %} 创建合作提交 +## Creating co-authored commits using {% data variables.product.prodname_desktop %} -可以使用 {% data variables.product.prodname_desktop %} 创建合作提交。 有关详细信息,请参阅“[编写提交消息并推送更改](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)”和 [{% data variables.product.prodname_desktop %}](https://desktop.github.com)。 +You can use {% data variables.product.prodname_desktop %} to create a commit with a co-author. For more information, see "[Write a commit message and push your changes](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" and [{% data variables.product.prodname_desktop %}](https://desktop.github.com). -![添加合作作者到提交消息](/assets/images/help/desktop/co-authors-demo-hq.gif) +![Add a co-author to the commit message](/assets/images/help/desktop/co-authors-demo-hq.gif) -## 在命令行上创建合作提交 +## Creating co-authored commits on the command line {% data reusables.pull_requests.collect-co-author-commit-git-config-info %} -1. 输入提交消息以及简短、有意义的更改描述。 在提交描述后,不要加上右引号,而是添加两个空行。 - ```shell +1. Type your commit message and a short, meaningful description of your changes. After your commit description, instead of a closing quotation, add two empty lines. + ``` $ git commit -m "Refactor usability tests. > > ``` {% tip %} - **提示:** 如果在命令行上使用文本编辑器来键入提交消息,请确保在提交描述的末尾和 `Co-authored-by:` 提交尾部之间有两个换行符。 + **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `Co-authored-by:` commit trailer. {% endtip %} -3. 在提交消息的下一行,根据每个共同作者的特定信息键入 `Co-authored-by: name `。 在合作作者的信息后面,添加一个右引号。 +3. On the next line of the commit message, type `Co-authored-by: name ` with specific information for each co-author. After the co-author information, add a closing quotation mark. - 如果要添加多个共同作者,请为每个共同作者键入一个 `Co-authored-by:` 提交尾行。 - ```shell + If you're adding multiple co-authors, give each co-author their own line and `Co-authored-by:` commit trailer. + ``` $ git commit -m "Refactor usability tests. > > - Co-authored-by: name <name@example.com> - Co-authored-by: another-name <another-name@example.com>" + Co-authored-by: NAME + Co-authored-by: AUTHOR-NAME " ``` -在下次推送时,新的提交和消息将显示在 {% data variables.product.product_location %} 上。 有关详细信息,请参阅“[将更改推送到远程存储库](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)”。 +The new commit and message will appear on {% data variables.location.product_location %} the next time you push. For more information, see "[Pushing changes to a remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)." -## 在 {% data variables.product.product_name %} 上创建合作提交 +## Creating co-authored commits on {% data variables.product.product_name %} -在 {% data variables.product.product_name %} 上使用 Web 编辑器对文件进行更改后,可通过在提交消息中添加 `Co-authored-by:` 尾行来创建共同创作的提交。 +After you've made changes in a file using the web editor on {% data variables.product.product_name %}, you can create a co-authored commit by adding a `Co-authored-by:` trailer to the commit's message. {% data reusables.pull_requests.collect-co-author-commit-git-config-info %} -2. 合作进行更改后,在页面底部键入简短、有意义的提交消息,以描述你们所做的更改。 - ![有关更改的提交消息](/assets/images/help/repository/write-commit-message-quick-pull.png) -3. 在提交消息下方的文本框中,根据每个共同作者的特定信息添加 `Co-authored-by: name `。 如果要添加多个共同作者,请为每个共同作者键入一个 `Co-authored-by:` 提交尾行。 +2. After making your changes together, at the bottom of the page, type a short, meaningful commit message that describes the changes you made. + ![Commit message for your change](/assets/images/help/repository/write-commit-message-quick-pull.png) +3. In the text box below your commit message, add `Co-authored-by: name ` with specific information for each co-author. If you're adding multiple co-authors, give each co-author their own line and `Co-authored-by:` commit trailer. - ![第二个提交消息文本框中的提交消息合作作者尾行示例](/assets/images/help/repository/write-commit-message-co-author-trailer.png) -4. 单击“提交更改”或“建议更改” 。 + ![Commit message co-author trailer example in second commit message text box](/assets/images/help/repository/write-commit-message-co-author-trailer.png) +4. Click **Commit changes** or **Propose changes**. -新的提交和消息将显示在 {% data variables.product.product_location %} 上。 +The new commit and message will appear on {% data variables.location.product_location %}. -## 延伸阅读 +## Further reading {% ifversion ghes or ghae %} -- [在个人资料中查看贡献](/articles/viewing-contributions-on-your-profile) -- [为什么我的贡献未显示在我的个人资料上?](/articles/why-are-my-contributions-not-showing-up-on-my-profile){% endif %} -- [查看项目的参与者](/articles/viewing-a-projects-contributors) -- [更改提交消息](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message) -- {% data variables.product.prodname_desktop %} 文档中的“[提交并审查对项目的更改](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)” +- "[Viewing contributions on your profile](/articles/viewing-contributions-on-your-profile)" +- "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"{% endif %} +- "[Viewing a project's contributors](/articles/viewing-a-projects-contributors)" +- "[Changing a commit message](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message)" +- "[Committing and reviewing changes to your project](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" in the {% data variables.product.prodname_desktop %} documentation diff --git a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md index a7f00651ac..ceab766830 100644 --- a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md +++ b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md @@ -1,6 +1,6 @@ --- -title: 存在于 GitHub 上但不存在于本地克隆中的提交 -intro: '有时,提交可以在 {% data variables.product.product_name %} 上查看到,但不存在于仓库的本地克隆中。' +title: Commit exists on GitHub but not in my local clone +intro: 'Sometimes a commit will be viewable on {% data variables.product.product_name %}, but will not exist in your local clone of the repository.' redirect_from: - /articles/commit-exists-on-github-but-not-in-my-local-clone - /github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone @@ -11,57 +11,62 @@ versions: ghae: '*' ghec: '*' shortTitle: Commit missing in local clone -ms.openlocfilehash: 9374b17a111bc3f88bf81d60de97e354c0bcf8ac -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145129447' --- -使用 `git show` 在命令行上查看特定提交时,可能会收到灾难性错误。 +When you use `git show` to view a specific commit on the command line, you may get a fatal error. -例如,可能会在本地收到 `bad object` 错误: +For example, you may receive a `bad object` error locally: ```shell $ git show 1095ff3d0153115e75b7bca2c09e5136845b5592 > fatal: bad object 1095ff3d0153115e75b7bca2c09e5136845b5592 ``` -但是,当您在 {% data variables.product.product_location %} 上查看该提交时,却可以看到它,并且不会遇到任何问题: +However, when you view the commit on {% data variables.location.product_location %}, you'll be able to see it without any problems: `github.com/$account/$repository/commit/1095ff3d0153115e75b7bca2c09e5136845b5592` -有几种可能的解释: +There are several possible explanations: -* 本地仓库已过期。 -* 包含提交的分支已被删除,因此该提交的引用不再有效。 -* 有人强制推送了提交。 +* The local repository is out of date. +* The branch that contains the commit was deleted, so the commit is no longer referenced. +* Someone force pushed over the commit. -## 本地仓库已过期 +## The local repository is out of date -您的本地仓库可能还没有提交。 要将信息从远程存储库提取到本地克隆,请使用 `git fetch`: +Your local repository may not have the commit yet. To get information from your remote repository to your local clone, use `git fetch`: ```shell -$ git fetch remote +$ git fetch REMOTE ``` -这可以安全地将信息从远程存储库复制到本地克隆,而无需对已签出的文件进行任何更改。可以使用 `git fetch upstream` 从创建分支的存储库中获取信息,或使用 `git fetch origin` 从仅克隆的存储库中获取信息。 +This safely copies information from the remote repository to your local clone without making any changes to the files you have checked out. +You can use `git fetch upstream` to get information from a repository you've forked, or `git fetch origin` to get information from a repository you've only cloned. {% tip %} -提示:有关详细信息,请阅读 [Pro Git](https://git-scm.com/book) 手册中的[管理远程库并提取数据](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)。 +**Tip**: For more information, read about [managing remotes and fetching data](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) in the [Pro Git](https://git-scm.com/book) book. {% endtip %} -## 包含提交的分支已被删除 +## The branch that contained the commit was deleted -如果存储库的协作者已删除包含提交的分支或者已强制推送该分支,则缺失的提交可能已为孤立状态(即无法从任何引用访问它),它也因此不会被提取到本地克隆中。 +If a collaborator on the repository has deleted the branch containing the commit +or has force pushed over the branch, the missing commit may have been orphaned +(i.e. it cannot be reached from any reference) and therefore will not be fetched +into your local clone. -如果幸好有某个协作者的本地克隆存储库中包含了该缺失的提交,则他们可以将其推送回 {% data variables.product.product_name %}。 他们需要确保通过本地分支引用该提交,然后将其作为新分支推送到 {% data variables.product.product_name %}。 +Fortunately, if any collaborator has a local clone of the repository with the +missing commit, they can push it back to {% data variables.product.product_name %}. They need to make sure the commit +is referenced by a local branch and then push it as a new branch to {% data variables.product.product_name %}. -假设某人仍有包含该提交的本地分支(称为 `B`)。 这可能会跟踪已被强制推送或删除的分支,它们只是还没有更新。 要保留该提交,可以将该本地分支推送到 {% data variables.product.product_name %} 上的新分支(称为 `recover-B`)。 在此例中,假设他们有一个名为 `upstream` 的远程库,通过该远程库他们可以获得对 `github.com/$account/$repository` 的推送访问权限。 +Let's say that the person still has a local branch (call it `B`) that contains +the commit. This might be tracking the branch that was force pushed or deleted +and they simply haven't updated yet. To preserve the commit, they can push that +local branch to a new branch (call it `recover-B`) on {% data variables.product.product_name %}. For this example, +let's assume they have a remote named `upstream` via which they have push access +to `github.com/$account/$repository`. -他们运行: +The other person runs: ```shell $ git branch recover-B B @@ -70,18 +75,18 @@ $ git push upstream B:recover-B # Push local B to new upstream branch, creating new reference to commit ``` -现在,可以运行: +Now, *you* can run: ```shell $ git fetch upstream recover-B # Fetch commit into your local repository. ``` -## 避免强制推送 +## Avoid force pushes -除非万不得已,否则应避免向仓库强制推送。 如果可以向仓库推送的人不止一个,这个原则尤为重要。 如果有人强制推送到仓库,则强制推送可能会覆盖其他人基于其工作的承诺。 强制推送会更改存储库历史记录,并可能损坏拉取请求。 +Avoid force pushing to a repository unless absolutely necessary. This is especially true if more than one person can push to the repository. If someone force pushes to a repository, the force push may overwrite commits that other people based their work on. Force pushing changes the repository history and can corrupt pull requests. -## 延伸阅读 +## Further reading -- [Pro Git 手册中的“使用远程库”](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) -- [Pro Git 手册中的“数据恢复”](https://git-scm.com/book/en/Git-Internals-Maintenance-and-Data-Recovery) +- ["Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) +- ["Data Recovery" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Internals-Maintenance-and-Data-Recovery) diff --git a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md index 28ec99423c..d4d8bbe644 100644 --- a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md +++ b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md @@ -1,63 +1,58 @@ --- -title: 我的提交为什么链接到错误的用户? +title: Why are my commits linked to the wrong user? redirect_from: - /articles/how-do-i-get-my-commits-to-link-to-my-github-account - /articles/why-are-my-commits-linked-to-the-wrong-user - /github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user - /github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user -intro: '{% data variables.product.product_name %} 使用提交标题中的电子邮件地址将提交链接到 GitHub 用户。 如果将提交链接到其他用户,或者根本没有链接到任何用户,你可能需要更改本地 Git 配置设置{% ifversion not ghae %},将电子邮件地址添加到帐户电子邮件设置,或同时执行这两项操作{% endif %}。' +intro: '{% data variables.product.product_name %} uses the email address in the commit header to link the commit to a GitHub user. If your commits are being linked to another user, or not linked to a user at all, you may need to change your local Git configuration settings{% ifversion not ghae %}, add an email address to your account email settings, or do both{% endif %}.' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' shortTitle: Linked to wrong user -ms.openlocfilehash: 80a871c85aca151f06ca04d1d48d016bd14ed47f -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147883033' --- {% tip %} -注意:如果提交与其他用户关联,这并不意味着该用户能够访问你的存储库。 只有您将用户作为协作者添加或将其添加到具有仓库访问权限的团队时,用户才能访问您拥有的仓库。 +**Note**: If your commits are linked to another user, that does not mean the user can access your repository. A user can only access a repository you own if you add them as a collaborator or add them to a team that has access to the repository. {% endtip %} -## 提交链接到其他用户 +## Commits are linked to another user -如果您的提交链接到其他用户,则意味着本地 Git 配置设置中的电子邮件地址已连接到该用户在 {% data variables.product.product_name %}上的帐户。 在这种情况下,可以将本地 Git 配置设置{% ifversion ghae %}中的电子邮件更改为 {% data variables.product.product_name %} 上与你的帐户关联的地址,以关联未来的提交。 原来的提交不会进行链接。 有关详细信息,请参阅“[设置提交电子邮件地址](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)。”{% else %}并将新的电子邮件地址添加到你在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 帐户上的帐户,将未来的提交与你的帐户关联。 +If your commits are linked to another user, that means the email address in your local Git configuration settings is connected to that user's account on {% data variables.product.product_name %}. In this case, you can change the email in your local Git configuration settings{% ifversion ghae %} to the address associated with your account on {% data variables.product.product_name %} to link your future commits. Old commits will not be linked. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %} and add the new email address to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} account to link future commits to your account. -1. 要更改本地 Git 配置中的电子邮件地址,请按照“[设置提交电子邮件地址](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)”中的步骤操作。 如果您在多台计算机上工作,则需要在每台计算机上更改此设置。 -2. 按照“[将电子邮件地址添加到 GitHub 帐户](/articles/adding-an-email-address-to-your-github-account)”中的步骤,将第 2 步中的电子邮件地址添加到你的帐户设置中。{% endif %} +1. To change the email address in your local Git configuration, follow the steps in "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)". If you work on multiple machines, you will need to change this setting on each one. +2. Add the email address from step 2 to your account settings by following the steps in "[Adding an email address to your GitHub account](/articles/adding-an-email-address-to-your-github-account)".{% endif %} -从这时开始,您提交的内容将链接到您的帐户。 +Commits you make from this point forward will be linked to your account. -## 提交没有链接到任何用户 +## Commits are not linked to any user -如果您的提交没有链接到任何用户,则提交作者的名称不会显示为到用户配置文件的链接。 +If your commits are not linked to any user, the commit author's name will not be rendered as a link to a user profile. -要检查用于这些提交的电子邮件地址并将提交连接到您的帐户,请执行以下步骤: +To check the email address used for those commits and connect commits to your account, take the following steps: -1. 通过单击提交消息链接导航到提交。 -![提交消息关联](/assets/images/help/commits/commit-msg-link.png) -2. 要阅读有关提交未关联原因的消息,请将鼠标悬停在用户名右侧的蓝色 {% octicon "question" aria-label="Question mark" %} 上。 -![提交悬停消息](/assets/images/help/commits/commit-hover-msg.png) +1. Navigate to the commit by clicking the commit message link. +![Commit message link](/assets/images/help/commits/commit-msg-link.png) +2. To read a message about why the commit is not linked, hover over the blue {% octicon "question" aria-label="Question mark" %} to the right of the username. +![Commit hover message](/assets/images/help/commits/commit-hover-msg.png) - - **作者无法识别(有电子邮件地址)** 如果你看到这条消息且有电子邮件地址,则表示用于创作提交的地址未连接到你在 {% data variables.product.product_name %} 上的帐户。 {% ifversion not ghae %}要关联提交,请[将电子邮件地址添加到 GitHub 电子邮件设置](/articles/adding-an-email-address-to-your-github-account)。{% endif %}{% ifversion not ghae %} 如果电子邮件地址关联了 Gravatar,提交旁将显示该 Gravatar,而不是默认的灰色 Octocat。{% endif %} - - **作者无法识别(无电子邮件地址)** 如果你看到这条消息且没有电子邮件地址,则表示使用了无法连接到在 {% data variables.product.product_name %} 上的帐户的通用电子邮件地址。{% ifversion not ghae %}你需要 [在 Git 中设置提交电子邮件地址](/articles/setting-your-commit-email-address),然后 [将新地址添加到 GitHub 电子邮件设置](/articles/adding-an-email-address-to-your-github-account)以关联未来的提交。 旧提交不会链接。{% endif %} - - **电子邮件无效** 本地 Git 配置设置中的电子邮件地址为空白或未格式化为电子邮件地址。{% ifversion not ghae %}你需要 [在 Git 中设置提交电子邮件地址](/articles/setting-your-commit-email-address),然后 [将新地址添加到 GitHub 电子邮件设置](/articles/adding-an-email-address-to-your-github-account)以关联未来的提交。 旧提交不会链接。{% endif %} + - **Unrecognized author (with email address)** If you see this message with an email address, the address you used to author the commit is not connected to your account on {% data variables.product.product_name %}. {% ifversion not ghae %}To link your commits, [add the email address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account).{% endif %}{% ifversion not ghae %} If the email address has a Gravatar associated with it, the Gravatar will be displayed next to the commit, rather than the default gray Octocat.{% endif %} + - **Unrecognized author (no email address)** If you see this message without an email address, you used a generic email address that can't be connected to your account on {% data variables.product.product_name %}.{% ifversion not ghae %} You will need to [set your commit email address in Git](/articles/setting-your-commit-email-address), then [add the new address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account) to link your future commits. Old commits will not be linked.{% endif %} + - **Invalid email** The email address in your local Git configuration settings is either blank or not formatted as an email address.{% ifversion not ghae %} You will need to [set your commit email address in Git](/articles/setting-your-commit-email-address), then [add the new address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account) to link your future commits. Old commits will not be linked.{% endif %} -{% ifversion ghae %} 可以将本地 Git 配置设置中的电子邮件地址更改为与你的帐户关联的地址,以关联未来的提交。 原来的提交不会进行链接。 有关详细信息,请参阅“[设置提交电子邮件地址](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)”。 +{% ifversion ghae %} +You can change the email in your local Git configuration settings to the address associated with your account to link your future commits. Old commits will not be linked. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)." {% endif %} {% warning %} -如果您的本地 Git 配置包含通用电子邮件地址或已附加到其他用户帐户的电子邮件地址,则您之前的提交将不会链接到您的帐户。 虽然 Git 允许您更改用于以前提交的电子邮件地址,但我们强烈反对这样做,尤其是在共享仓库中。 +If your local Git configuration contained a generic email address, or an email address that was already attached to another user's account, then your previous commits will not be linked to your account. While Git does allow you to change the email address used for previous commits, we strongly discourage this, especially in a shared repository. {% endwarning %} -## 延伸阅读 +## Further reading -* [搜索提交](/search-github/searching-on-github/searching-commits) +* "[Searching commits](/search-github/searching-on-github/searching-commits)" diff --git a/translations/zh-CN/content/repositories/archiving-a-github-repository/backing-up-a-repository.md b/translations/zh-CN/content/repositories/archiving-a-github-repository/backing-up-a-repository.md index 3e20c82926..79f382bd8d 100644 --- a/translations/zh-CN/content/repositories/archiving-a-github-repository/backing-up-a-repository.md +++ b/translations/zh-CN/content/repositories/archiving-a-github-repository/backing-up-a-repository.md @@ -1,6 +1,6 @@ --- -title: 备份仓库 -intro: '可使用{% ifversion ghes or ghae %} Git 和{% endif %} API {% ifversion fpt or ghec %}或第三方工具{% endif %}备份仓库。' +title: Backing up a repository +intro: 'You can use{% ifversion ghes or ghae %} Git and{% endif %} the API {% ifversion fpt or ghec %}or a third-party tool {% endif %}to back up your repository.' redirect_from: - /articles/backing-up-a-repository - /github/creating-cloning-and-archiving-repositories/backing-up-a-repository @@ -12,39 +12,34 @@ versions: ghec: '*' topics: - Repositories -ms.openlocfilehash: 3c9a6b5569563858987e338584b3b42bededf716 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147883447' --- {% ifversion fpt or ghec %} -要下载仓库的存档,您可以使用 API 进行用户或组织迁移。 有关详细信息,请参阅“[迁移](/rest/reference/migrations)”。 +To download an archive of your repository, you can use the API for user or organization migrations. For more information, see "[Migrations](/rest/reference/migrations)." {% else %} -您可以手动下载和备份仓库: +You can download and back up your repositories manually: -- 要将仓库的 Git 数据下载到本地计算机,您需要克隆该仓库。 有关详细信息,请参阅“[克隆存储库](/articles/cloning-a-repository)”。 -- 还可以下载仓库的 wiki。 有关详细信息,请参阅“[添加或编辑 Wiki 页面](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)”。 +- To download a repository's Git data to your local machine, you'll need to clone the repository. For more information, see "[Cloning a repository](/articles/cloning-a-repository)." +- You can also download your repository's wiki. For more information, see "[Adding or editing wiki pages](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)." -克隆仓库或 wiki 时,仅下载 Git 数据,例如项目文件和提交历史记录。 您可以使用我们的 API 将 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上存储库的其他元素导出到本地计算机: +When you clone a repository or wiki, only Git data, such as project files and commit history, is downloaded. You can use our API to export other elements of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} to your local machine: -- [问题](/rest/reference/issues#list-issues-for-a-repository) -- [拉取请求](/rest/reference/pulls#list-pull-requests) -- [前叉](/rest/reference/repos#list-forks) -- [注释](/rest/reference/issues#list-issue-comments-for-a-repository) -- [里程碑](/rest/reference/issues#list-milestones) -- [标签](/rest/reference/issues#list-labels-for-a-repository) +- [Issues](/rest/reference/issues#list-issues-for-a-repository) +- [Pull requests](/rest/reference/pulls#list-pull-requests) +- [Forks](/rest/reference/repos#list-forks) +- [Comments](/rest/reference/issues#list-issue-comments-for-a-repository) +- [Milestones](/rest/reference/issues#list-milestones) +- [Labels](/rest/reference/issues#list-labels-for-a-repository) - [Watchers](/rest/reference/activity#list-watchers) - [Stargazers](/rest/reference/activity#list-stargazers) -- [Projects](/rest/reference/projects#list-repository-projects) {% endif %} +- [Projects](/rest/reference/projects#list-repository-projects) +{% endif %} -一旦拥有{% ifversion ghes or ghae %}要备份的所有内容的本地版本,可以创建一个 zip 存档并{% else %}下载存档,可以{% endif %}将它复制到外部硬盘驱动器和/或将其上传到基于云的备份或存储服务,例如 [Azure Blob 存储](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-overview/)、[Google Drive](https://www.google.com/drive/) 或 [Dropbox](https://www.dropbox.com/)。 +Once you have {% ifversion ghes or ghae %}a local version of all the content you want to back up, you can create a zip archive and {% else %}downloaded your archive, you can {% endif %}copy it to an external hard drive and/or upload it to a cloud-based backup or storage service such as [Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-overview/), [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/). {% ifversion fpt or ghec %} -## 第三方备份工具 +## Third-party backup tools -有许多自助服务工具可自动备份仓库。 存档项目将所有公共存储库存档在未选择退出的 {% data variables.product.product_name %} 上,并让任何人都可以访问数据,而备份工具则不同,它将从特定存储库下载数据并组织在新分支或目录中 。 有关存档项目的详细信息,请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上存档内容和数据](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)”。 有关自助备份工具的详细信息,请参阅 [{% data variables.product.prodname_marketplace %} 上的备份实用程序类别](https://github.com/marketplace?category=backup-utilities)。 +A number of self-service tools exist that automate backups of repositories. Unlike archival projects, which archive _all_ public repositories on {% data variables.product.product_name %} that have not opted out and make the data accessible to anyone, backup tools will download data from _specific_ repositories and organize it within a new branch or directory. For more information about archival projects, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)." For more information about self-service backup tools, see the [Backup Utilities category on {% data variables.product.prodname_marketplace %}](https://github.com/marketplace?category=backup-utilities). {% endif %} diff --git a/translations/zh-CN/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md b/translations/zh-CN/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md index 49b80b0fc0..27fa92e78b 100644 --- a/translations/zh-CN/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md +++ b/translations/zh-CN/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md @@ -1,6 +1,6 @@ --- -title: 参考和引用内容 -intro: 您可以使用第三方工具参考和引用 GitHub 上的内容。 +title: Referencing and citing content +intro: You can use third-party tools to cite and reference content on GitHub. redirect_from: - /articles/referencing-and-citing-content - /github/creating-cloning-and-archiving-repositories/referencing-and-citing-content @@ -11,35 +11,29 @@ versions: topics: - Repositories shortTitle: Reference & cite content -ms.openlocfilehash: e0bb3dabe5e9ebc8a4dff80797087c8adadfb710 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145129426' --- -## 使用 Zenodo 发出仓库的持久标识符 +## Issuing a persistent identifier for your repository with Zenodo -为了使您的仓库在学术文献中更易于参考,您可以创建持久标识符,也称为数字对象标识符 (DOI)。 可以使用数据存档工具 [Zenodo](https://zenodo.org/about) 对 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的存储库进行存档,并为存档发出 DOI。 +To make your repositories easier to reference in academic literature, you can create persistent identifiers, also known as Digital Object Identifiers (DOIs). You can use the data archiving tool [Zenodo](https://zenodo.org/about) to archive a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} and issue a DOI for the archive. {% tip %} -**提示:** -- Zenodo 只能访问公共存储库,因此请确保要存档的存储库是[公共](/articles/making-a-private-repository-public)的。 -- 如果要存档属于组织的存储库,组织所有者可能需要对 Zenodo 应用程序[批准访问权限](/articles/approving-oauth-apps-for-your-organization)。 -- 请确保存储库中包含[许可证](/articles/open-source-licensing),以便读者了解如何重复使用你的工作。 +**Tips:** +- Zenodo can only access public repositories, so make sure the repository you want to archive is [public](/articles/making-a-private-repository-public). +- If you want to archive a repository that belongs to an organization, the organization owner may need to [approve access](/articles/approving-oauth-apps-for-your-organization) for the Zenodo application. +- Make sure to include a [license](/articles/open-source-licensing) in your repository so readers know how they can reuse your work. {% endtip %} -1. 导航到 [Zenodo](http://zenodo.org/)。 -2. 在屏幕左下角单击“登录”。 ![Zenodo 登录按钮](/assets/images/help/repository/zenodo_login.png) -3. 单击“使用 GitHub 登录”。 ![使用 GitHub 登录 Zenodo](/assets/images/help/repository/zenodo_login_with_github.png) -4. 审阅有关访问权限的信息,然后单击“授权应用程序”。 ![授权 Zenodo](/assets/images/help/repository/zenodo_authorize.png) -5. 导航到 [Zenodo GitHub 页面](https://zenodo.org/account/settings/github/)。 ![Zenodo GitHub 页面](/assets/images/help/repository/zenodo_github_page.png) -6. 在要存档的存储库的名称右侧,将按钮从“关”切换为“开”,使它能够进行存档。 ![在存储库上启用 Zenodo 存档](/assets/images/help/repository/zenodo_toggle_on.png) +1. Navigate to [Zenodo](http://zenodo.org/). +2. In the upper-left corner of the screen, click **Log in**. ![Zenodo log in button](/assets/images/help/repository/zenodo_login.png) +3. Click **Log in with GitHub**. ![Log into Zenodo with GitHub](/assets/images/help/repository/zenodo_login_with_github.png) +4. Review the information about access permissions, then click **Authorize application**. ![Authorize Zenodo](/assets/images/help/repository/zenodo_authorize.png) +5. Navigate to the [Zenodo GitHub page](https://zenodo.org/account/settings/github/). ![Zenodo GitHub page](/assets/images/help/repository/zenodo_github_page.png) +6. To the right of the name of the repository you want to archive, toggle the button from **Off** to **On** to enable it for archiving. ![Enable Zenodo archiving on repository](/assets/images/help/repository/zenodo_toggle_on.png) -Zenodo 会在你每次创建新 {% data variables.product.product_name %} [版本](/articles/about-releases/)时存档存储库和发出新的 DOI。 按照“[创建版本](/articles/creating-releases/)”中的步骤创建新的版本。 +Zenodo archives your repository and issues a new DOI each time you create a new {% data variables.product.product_name %} [release](/articles/about-releases/). Follow the steps at "[Creating releases](/articles/creating-releases/)" to create a new one. -## 使用 Figshare 宣传和引用研究资料 +## Publicizing and citing research material with Figshare -学者可以使用数据管理服务 [Figshare](http://figshare.com) 来宣传和引用研究材料。 有关详细信息,请参阅“[Figshare 的支持站点](https://knowledge.figshare.com/articles/item/how-to-connect-figshare-with-your-github-account)”。 +Academics can use the data management service [Figshare](http://figshare.com) to publicize and cite research material. For more information, see [Figshare's support site](https://knowledge.figshare.com/articles/item/how-to-connect-figshare-with-your-github-account). diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md index 39d76ce51e..cbbb88a505 100644 --- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md +++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md @@ -1,6 +1,6 @@ --- -title: 关于 GitHub 上的合并方法 -intro: '您可以允许能够推送到仓库的贡献者使用不同的合并选项在 {% data variables.product.product_location %} 上合并其推送请求,或者对所有仓库的拉取请求实施特定的合并方法。' +title: About merge methods on GitHub +intro: 'You can allow contributors with push access to your repository to merge their pull requests on {% data variables.location.product_location %} with different merge options or enforce a specific merge method for all of your repository''s pull requests.' redirect_from: - /articles/about-merge-methods-on-github - /github/administering-a-repository/about-merge-methods-on-github @@ -13,42 +13,38 @@ versions: topics: - Repositories shortTitle: About merge methods -ms.openlocfilehash: 97e8b7159ebadf1fe02ae56f707728c2bc8c439d -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147882439' --- -{% data reusables.pull_requests.configure_pull_request_merges_intro %} 您可以只对仓库启用所需的方法,以实施一种合并方法,如提交压缩或变基。 +{% data reusables.pull_requests.configure_pull_request_merges_intro %} You can enforce one type of merge method, such as commit squashing or rebasing, by only enabling the desired method for your repository. -{% ifversion fpt or ghec %} {% note %} +{% ifversion fpt or ghec %} +{% note %} -注意:使用合并队列时,你将无法再选择合并方法,因为这由队列控制。 {% data reusables.pull_requests.merge-queue-references %} +**Note:** When using the merge queue, you no longer get to choose the merge method, as this is controlled by the queue. {% data reusables.pull_requests.merge-queue-references %} -{% endnote %} {% endif %} +{% endnote %} +{% endif %} {% data reusables.pull_requests.default_merge_option %} -默认合并方法创建合并提交。 通过强制实施线性提交历史记录,可以防止任何人将合并提交推送到受保护分支。 有关详细信息,请参阅“[关于受保护的分支](/github/administering-a-repository/about-protected-branches#require-linear-history)”。 +The default merge method creates a merge commit. You can prevent anyone from pushing merge commits to a protected branch by enforcing a linear commit history. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-linear-history)." -## 压缩合并提交 +## Squashing your merge commits {% data reusables.pull_requests.squash_and_merge_summary %} -在启用压缩提交之前,请考虑以下缺点: -- 您会丢失关于最初何时执行了特定更改以及是谁进行了压缩提交的信息。 -- 如果在压缩与合并后继续操作拉取请求的头部分支,然后在相同分支之间创建新的拉取请求,您先前被压缩与合并的提交将列于新的拉取请求中。 可能还有必须在每个连续的拉取请求中反复解决的冲突。 有关详细信息,请参阅“[关于拉取请求合并](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges#squashing-and-merging-a-long-running-branch)”。 -- 有些使用 "SHA" 或“哈希”ID 的 Git 命令可能更难使用,因为原始提交的 SHA ID 已经丢失。 例如,使用 [`git rerere`](https://git-scm.com/docs/git-rerere) 可能不那么有效。 +Before enabling squashing commits, consider these disadvantages: +- You lose information about when specific changes were originally made and who authored the squashed commits. +- If you continue working on the head branch of a pull request after squashing and merging, and then create a new pull request between the same branches, commits that you previously squashed and merged will be listed in the new pull request. You may also have conflicts that you have to repeatedly resolve in each successive pull request. For more information, see "[About pull request merges](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges#squashing-and-merging-a-long-running-branch)." +- Some Git commands that use the "SHA" or "hash" ID may be harder to use since the SHA ID for the original commits is lost. For example, using [`git rerere`](https://git-scm.com/docs/git-rerere) may not be as effective. -有关详细信息,请参阅“[为拉取请求配置提交压缩](/articles/configuring-commit-squashing-for-pull-requests)”。 +For more information, see "[Configuring commit squashing for pull requests](/articles/configuring-commit-squashing-for-pull-requests)." -## 变基和合并提交 +## Rebasing and merging your commits {% data reusables.pull_requests.rebase_and_merge_summary %} -在启用提交变基之前,请考虑以下缺点: -- 存储库参与者可能必须在命令行上变基、解决所有冲突,并将其更改推送到拉取请求的主题分支(或删除头分支),然后才可在 {% data variables.product.product_location %} 上使用“变基和合并”选项。 强制推送必须谨慎执行,以免贡献者覆盖别人在其工作基础上所做的工作。 若要详细了解何时在 {% data variables.product.product_location %} 上禁用“变基和合并”选项,并了解用于重新启用它的工作流,请参阅“[关于拉取请求合并](/articles/about-pull-request-merges/#rebase-and-merge-your-pull-request-commits)”。 +Before enabling commit rebasing, consider these disadvantages: +- Repository contributors may have to rebase on the command line, resolve any conflicts, and force push their changes to the pull request's topic branch (or remote head branch) before they can use the **rebase and merge** option on {% data variables.location.product_location %}. Force pushing must be done carefully so contributors don't overwrite work that others have based their work on. To learn more about when the **Rebase and merge** option is disabled on {% data variables.location.product_location %} and the workflow to re-enable it, see "[About pull request merges](/articles/about-pull-request-merges/#rebase-and-merge-your-pull-request-commits)." - {% indented_data_reference reusables.pull_requests.rebase_and_merge_verification spaces=3 %} -有关详细信息,请参阅“[为拉取请求配置提交变基](/articles/configuring-commit-rebasing-for-pull-requests)”。 +For more information, see "[Configuring commit rebasing for pull requests](/articles/configuring-commit-rebasing-for-pull-requests)." diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md index 506a34d3b1..610176d045 100644 --- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md +++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md @@ -1,6 +1,6 @@ --- title: Configuring commit merging for pull requests -intro: 'You can enforce, allow, or disable merging with a merge commit for all pull request merges on {% data variables.product.product_location %} in your repository.' +intro: 'You can enforce, allow, or disable merging with a merge commit for all pull request merges on {% data variables.location.product_location %} in your repository.' versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md index 714645fa9e..c4652106f1 100644 --- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md +++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md @@ -1,6 +1,6 @@ --- title: Configuring commit rebasing for pull requests -intro: 'You can enforce, allow, or disable commit rebasing for all pull request merges on {% data variables.product.product_location %} in your repository.' +intro: 'You can enforce, allow, or disable commit rebasing for all pull request merges on {% data variables.location.product_location %} in your repository.' redirect_from: - /articles/configuring-commit-rebasing-for-pull-requests - /github/administering-a-repository/configuring-commit-rebasing-for-pull-requests diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md index 0473b10065..7814e66262 100644 --- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md +++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md @@ -1,6 +1,6 @@ --- title: Configuring commit squashing for pull requests -intro: 'You can enforce, allow, or disable commit squashing for all pull request merges on {% data variables.product.product_location %} in your repository.' +intro: 'You can enforce, allow, or disable commit squashing for all pull request merges on {% data variables.location.product_location %} in your repository.' redirect_from: - /articles/configuring-commit-squashing-for-pull-requests - /github/administering-a-repository/configuring-commit-squashing-for-pull-requests diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md index d296f306cc..bf762e72cc 100644 --- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md +++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md @@ -1,6 +1,6 @@ --- -title: 配置拉取请求合并 -intro: '您可以在 {% data variables.product.product_location %} 上配置拉取请求合并,以匹配您的工作流程和用于管理 Git 历史记录的首选项。' +title: Configuring pull request merges +intro: 'You can configure pull request merges on {% data variables.location.product_location %} to match your workflow and preferences for managing Git history.' redirect_from: - /articles/configuring-pull-request-merges - /github/administering-a-repository/configuring-pull-request-merges @@ -21,11 +21,5 @@ children: - /managing-auto-merge-for-pull-requests-in-your-repository - /managing-the-automatic-deletion-of-branches shortTitle: Configure PR merges -ms.openlocfilehash: 625392c72ae470fffea4f92288aa7c3124bc18ab -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147580605' --- diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md index 8a9674eff8..16551aab62 100644 --- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md +++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md @@ -1,6 +1,6 @@ --- -title: 重命名分支 -intro: 您可以更改仓库中分支的名称。 +title: Renaming a branch +intro: You can change the name of a branch in a repository. permissions: 'People with write permissions to a repository can rename a branch in the repository unless it is the [default branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch){% ifversion fpt or ghec or ghes > 3.3 %} or a [protected branch](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches){% endif %}. People with admin permissions can rename the default branch{% ifversion fpt or ghec or ghes > 3.3 %} and protected branches{% endif %}.' versions: fpt: '*' @@ -12,47 +12,42 @@ topics: redirect_from: - /github/administering-a-repository/renaming-a-branch - /github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch -ms.openlocfilehash: 6e30c7c2615f8b3dc21075e24298796febbce314 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145129389' --- -## 关于重命名分支 +## About renaming branches -您可以重命名 {% data variables.product.product_location %} 上仓库中的分支。 有关分支的详细信息,请参阅“[关于分支](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)”。 +You can rename a branch in a repository on {% data variables.location.product_location %}. For more information about branches, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches))." -当您在 {% data variables.product.product_location %}上重命名分支时,任何包含旧分支名称的网址都会自动重定向到重命名分支的等效 URL。 还更新了分支保护政策以及打开的拉取请求(包括复刻的拉取请求)的基础分支和草稿版本。 重命名完成后, {% data variables.product.prodname_dotcom %} 在仓库主页上提供说明,指示贡献者更新他们的本地 Git 环境。 +When you rename a branch on {% data variables.location.product_location %}, any URLs that contain the old branch name are automatically redirected to the equivalent URL for the renamed branch. Branch protection policies are also updated, as well as the base branch for open pull requests (including those for forks) and draft releases. After the rename is complete, {% data variables.product.prodname_dotcom %} provides instructions on the repository's home page directing contributors to update their local Git environments. -虽然文件 URL 会自动重定向,但原始文件 URL 未被重定向。 此外,如果用户对前一个分支名称执行 `git pull`,则 {% data variables.product.prodname_dotcom %} 不会执行任何重定向。 +Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name. -{% data variables.product.prodname_actions %} 工作流不遵循重命名,因此,如果存储库发布了一个操作,任何使用 `@{old-branch-name}` 的操作都将中断。 您应该考虑添加带有原始内容的新分支,外加一个额外的提交报告,说明分支名称已弃用,并建议用户迁移到新的分支名称。 +{% data variables.product.prodname_actions %} workflows do not follow renames, so if your repository publishes an action, anyone using that action with `@{old-branch-name}` will break. You should consider adding a new branch with the original content plus an additional commit reporting that the branch name is deprecated and suggesting that users migrate to the new branch name. -## 重命名分支 +## Renaming a branch -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.navigate-to-branches %} -1. 在分支列表中,在要重命名的分支的右侧,单击 {% octicon "pencil" aria-label="The edit icon" %}。 - ![要重命名的分支右侧的铅笔图标](/assets/images/help/branch/branch-rename-edit.png) -1. 为分支输入新名称。 - ![用于键入新分支名称的文本字段](/assets/images/help/branch/branch-rename-type.png) -1. 查看有关本地环境的信息,然后单击“重命名分支”。 - ![本地环境信息和“重命名分支”按钮](/assets/images/help/branch/branch-rename-rename.png) +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.navigate-to-branches %} +1. In the list of branches, to the right of the branch you want to rename, click {% octicon "pencil" aria-label="The edit icon" %}. + ![Pencil icon to the right of branch you want to rename](/assets/images/help/branch/branch-rename-edit.png) +1. Type a new name for the branch. + ![Text field for typing new branch name](/assets/images/help/branch/branch-rename-type.png) +1. Review the information about local environments, then click **Rename branch**. + ![Local environment information and "Rename branch" button](/assets/images/help/branch/branch-rename-rename.png) -## 在分支名称更改后更新本地克隆 +## Updating a local clone after a branch name changes -在您重命名 {% data variables.product.product_name %} 仓库中的分支后,拥有该仓库本地克隆的所有协作者都需要更新克隆。 +After you rename a branch in a repository on {% data variables.product.product_name %}, any collaborator with a local clone of the repository will need to update the clone. -从计算机上的仓库本地克隆中,运行以下命令以更新默认分支的名称。 +From the local clone of the repository on a computer, run the following commands to update the name of the default branch. ```shell -$ git branch -m OLD-BRANCH-NAME NEW-BRANCH-NAME +$ git branch -m OLD-BRANCH-NAME NEW-BRANCH-NAME $ git fetch origin -$ git branch -u origin/NEW-BRANCH-NAME NEW-BRANCH-NAME +$ git branch -u origin/NEW-BRANCH-NAME NEW-BRANCH-NAME $ git remote set-head origin -a ``` -(可选)运行下面的命令来删除对旧分支名称的跟踪引用。 +Optionally, run the following command to remove tracking references to the old branch name. ``` $ git remote prune origin ``` diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md index 268373565a..014c709c08 100644 --- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md +++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md @@ -1,6 +1,6 @@ --- -title: 关于仓库 -intro: 仓库包含项目的所有文件,并存储每个文件的修订记录。 您可以在仓库中讨论并管理项目的工作。 +title: About repositories +intro: A repository contains all of your project's files and each file's revision history. You can discuss and manage your project's work within the repository. redirect_from: - /articles/about-repositories - /github/creating-cloning-and-archiving-repositories/about-repositories @@ -18,119 +18,123 @@ versions: ghec: '*' topics: - Repositories -ms.openlocfilehash: e4893e18de51f4d4918eacd3cb4d6da1c0323a1b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147444401' --- -## 关于仓库 -您可以个人拥有仓库,也可以与组织中的其他人共享仓库的所有权。 +## About repositories -您可以通过选择仓库的可见性来限制谁可以访问仓库。 有关详细信息,请参阅“[关于存储库可见性](#about-repository-visibility)”。 +You can own repositories individually, or you can share ownership of repositories with other people in an organization. -对于用户拥有的仓库,您可以向其他人授予协作者访问权限,以便他们可以协作处理您的项目。 如果仓库归组织所有,您可以向组织成员授予访问权限,以便协作处理您的仓库。 有关详细信息,请参阅“[帐户存储库的权限级别](/articles/permission-levels-for-a-user-account-repository/)”和“[组织的存储库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)”。 +You can restrict who has access to a repository by choosing the repository's visibility. For more information, see "[About repository visibility](#about-repository-visibility)." -{% ifversion fpt or ghec %} 通过个人帐户和组织的 {% data variables.product.prodname_free_team %},可与无限制的协作者合作处理设置了完全功能的无限制公共存储库,或者是设置了有限功能的无限制专用存储库。 要获取对私有仓库的高级处理,您可以升级到 {% data variables.product.prodname_pro %}、{% data variables.product.prodname_team %} 或 {% data variables.product.prodname_ghe_cloud %}。 {% data reusables.gated-features.more-info %} {% else %} 每个人和组织都可拥有无限制的存储库,并且可邀请无限制的协作者参与所有存储库。 +For user-owned repositories, you can give other people collaborator access so that they can collaborate on your project. If a repository is owned by an organization, you can give organization members access permissions to collaborate on your repository. For more information, see "[Permission levels for a personal account repository](/articles/permission-levels-for-a-user-account-repository/)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." + +{% ifversion fpt or ghec %} +With {% data variables.product.prodname_free_team %} for personal accounts and organizations, you can work with unlimited collaborators on unlimited public repositories with a full feature set, or unlimited private repositories with a limited feature set. To get advanced tooling for private repositories, you can upgrade to {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %} +{% else %} +Each person and organization can own unlimited repositories and invite an unlimited number of collaborators to all repositories. {% endif %} -您可以使用仓库管理您的工作并与他人合作。 -- 您可以使用议题来收集用户反馈,报告软件缺陷,并组织您想要完成的任务。 有关详细信息,请参阅“[关于问题](/github/managing-your-work-on-github/about-issues)”。{% ifversion fpt or ghec %} +You can use repositories to manage your work and collaborate with others. +- You can use issues to collect user feedback, report software bugs, and organize tasks you'd like to accomplish. For more information, see "[About issues](/github/managing-your-work-on-github/about-issues)."{% ifversion fpt or ghec %} - {% data reusables.discussions.you-can-use-discussions %}{% endif %} -- 您可以使用拉取请求来建议对仓库的更改。 有关详细信息,请参阅“[关于拉取请求](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)”。 -- 您可以使用项目板来组织议题和拉取请求并排定优先级。 有关详细信息,请参阅“[关于项目板](/github/managing-your-work-on-github/about-project-boards)”。 +- You can use pull requests to propose changes to a repository. For more information, see "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)." +- You can use project boards to organize and prioritize your issues and pull requests. For more information, see "[About project boards](/github/managing-your-work-on-github/about-project-boards)." {% data reusables.repositories.repo-size-limit %} -## 关于仓库可见性 +## About repository visibility -可以通过选择存储库的可见性来限制谁有权访问存储库:{% ifversion ghes or ghec %}公共、内部或专用{% elsif ghae %}专用或内部{% else %}公共或专用{% endif %}。 +You can restrict who has access to a repository by choosing a repository's visibility: {% ifversion ghes or ghec %}public, internal, or private{% elsif ghae %}private or internal{% else %} public or private{% endif %}. {% ifversion fpt or ghec or ghes %} -创建存储库时,可以选择将存储库设为公开或私有。{% ifversion ghec or ghes %} 如果要在{% ifversion ghec %}企业帐户拥有的{% endif %} 组织中创建存储库,则还可以选择将存储库设为内部存储库。{% endif %}{% endif %}{% ifversion fpt %}还可以通过内部可见性创建使用 {% data variables.product.prodname_ghe_cloud %} 并由企业帐户拥有的组织中的存储库。 有关详细信息,请参阅 [{% data variables.product.prodname_ghe_cloud %} 文档](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories)。 +When you create a repository, you can choose to make the repository public or private.{% ifversion ghec or ghes %} If you're creating the repository in an organization{% ifversion ghec %} that is owned by an enterprise account{% endif %}, you can also choose to make the repository internal.{% endif %}{% endif %}{% ifversion fpt %} Repositories in organizations that use {% data variables.product.prodname_ghe_cloud %} and are owned by an enterprise account can also be created with internal visibility. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories). {% elsif ghae %} -当你创建由你的个人帐户拥有的存储库时,存储库始终是私有的。 创建组织拥有的存储库时,可以选择将存储库设为私有或内部存储库。 +When you create a repository owned by your personal account, the repository is always private. When you create a repository owned by an organization, you can choose to make the repository private or internal. {% endif %} {%- ifversion fpt or ghec %} -- 互联网上的所有人都可以访问公共存储库。 -- 私有仓库仅可供您、您明确与其共享访问权限的人访问,而对于组织仓库,只有某些组织成员可以访问。 +- Public repositories are accessible to everyone on the internet. +- Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members. {%- elsif ghes %} -- 如果 {% data variables.product.product_location %} 不是私人模式或在防火墙后面,所有人都可以在互联网上访问公共仓库。 或者,使用 {% data variables.product.product_location %} 的每个人都可以使用公共仓库,包括外部协作者。 -- 私有仓库仅可供您、您明确与其共享访问权限的人访问,而对于组织仓库,只有某些组织成员可以访问。 +- If {% data variables.location.product_location %} is not in private mode or behind a firewall, public repositories are accessible to everyone on the internet. Otherwise, public repositories are available to everyone using {% data variables.location.product_location %}, including outside collaborators. +- Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members. {%- elsif ghae %} -- 私有仓库仅可供您、您明确与其共享访问权限的人访问,而对于组织仓库,只有某些组织成员可以访问。 -{%- endif %} {%- ifversion ghec or ghes or ghae %} -- 所有企业成员均可访问内部仓库。 有关详细信息,请参阅“[关于内部存储库](#about-internal-repositories)”。 +- Private repositories are only accessible to you, people you explicitly share access with, and, for organization repositories, certain organization members. +{%- endif %} +{%- ifversion ghec or ghes or ghae %} +- Internal repositories are accessible to all enterprise members. For more information, see "[About internal repositories](#about-internal-repositories)." {%- endif %} -组织所有者始终有权访问其组织中创建的每个仓库。 有关详细信息,请参阅“[组织的存储库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)”。 +Organization owners always have access to every repository created in an organization. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." -拥有仓库管理员权限的人可更改现有仓库的可见性。 有关详细信息,请参阅“[设置存储库可见性](/github/administering-a-repository/setting-repository-visibility)”。 +People with admin permissions for a repository can change an existing repository's visibility. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)." {% ifversion ghes or ghec or ghae %} -## 关于内部仓库 +## About internal repositories -{% data reusables.repositories.about-internal-repos %} 有关 InnerSource 的详细信息,请参阅 {% data variables.product.prodname_dotcom %} 的白皮书“[InnerSource 简介](https://resources.github.com/whitepapers/introduction-to-innersource/)”。 +{% data reusables.repositories.about-internal-repos %} For more information on innersource, see {% data variables.product.prodname_dotcom %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)." -所有企业成员对内部仓库具有读取权限,但内部仓库对{% ifversion fpt or ghec %}企业外部{% else %}非组织成员{% endif %}的人员不可见,包括组织仓库的外部协作者。 有关详细信息,请参阅“[企业中的角色](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)”和“[组织的存储库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)”。 +All enterprise members have read permissions to the internal repository, but internal repositories are not visible to people {% ifversion fpt or ghec %}outside of the enterprise{% else %}who are not members of any organization{% endif %}, including outside collaborators on organization repositories. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." -{% ifversion ghes %} {% note %} +{% ifversion ghes %} +{% note %} -注意:用户必须是组织的一部分才能成为企业成员并有权访问内部存储库。 如果 {% data variables.product.product_location %} 上的用户不是任何组织的成员,则该用户将无权访问内部存储库。 +**Note:** A user must be part of an organization to be an enterprise member and have access to internal repositories. If a user on {% data variables.location.product_location %} is not a member of any organization, that user will not have access to internal repositories. -{% endnote %} {% endif %} +{% endnote %} +{% endif %} {% data reusables.repositories.internal-repo-default %} -{% ifversion ghec %}除非企业使用 {% data variables.product.prodname_emus %},否则企业的成员{% else %}成员{% endif %}可以复刻企业中组织拥有的任何内部存储库。 分支存储库将属于成员的个人帐户,分支将为私人可见。 如果用户从企业拥有的所有组织中删除,该用户的内部仓库复刻也会自动删除。 +{% ifversion ghec %}Unless your enterprise uses {% data variables.product.prodname_emus %}, members{% else %}Members{% endif %} of the enterprise can fork any internal repository owned by an organization in the enterprise. The forked repository will belong to the member's personal account, and the visibility of the fork will be private. If a user is removed from all organizations owned by the enterprise, that user's forks of internal repositories are removed automatically. -{% ifversion ghec %} {% note %} +{% ifversion ghec %} +{% note %} -注意:{% data variables.product.prodname_managed_users_caps %} 无法为内部存储库创建分支。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-user-accounts)”。 +**Note:** {% data variables.enterprise.prodname_managed_users_caps %} cannot fork internal repositories. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-user-accounts)." -{% endnote %} {% endif %} {% endif %} +{% endnote %} +{% endif %} +{% endif %} -## 限制查看仓库中的内容和差异 +## Limits for viewing content and diffs in a repository -有些类型的资源可能很大,需要在 {% data variables.product.product_name %} 上额外处理。 因此,可设置限制,以确保申请在合理的时间内完成。 +Certain types of resources can be quite large, requiring excessive processing on {% data variables.product.product_name %}. Because of this, limits are set to ensure requests complete in a reasonable amount of time. -以下限制大多会影响 {% data variables.product.product_name %} 和 API。 +Most of the limits below affect both {% data variables.product.product_name %} and the API. -### 文本限制 +### Text limits -超过 512 KB 的文本文件始终显示为纯文本。 不突出显示代码中的语法,文本文件不会转换成 HTML(如 Markdown、AsciiDoc 等)。 +Text files over **512 KB** are always displayed as plain text. Code is not syntax highlighted, and prose files are not converted to HTML (such as Markdown, AsciiDoc, *etc.*). -超过 5 MB 的文本文件只能通过其原始 URL 获取,这些 URL 通过 `{% data variables.product.raw_github_com %}` 提供;例如 `https://{% data variables.product.raw_github_com %}/octocat/Spoon-Knife/master/index.html`。 单击“原始”按钮可获取文件的原始 URL。 +Text files over **5 MB** are only available through their raw URLs, which are served through `{% data variables.product.raw_github_com %}`; for example, `https://{% data variables.product.raw_github_com %}/octocat/Spoon-Knife/master/index.html`. Click the **Raw** button to get the raw URL for a file. -### 差异限制 +### Diff limits -因为差异可能很大,所以我们会对评论、拉取请求和比较视图的差异施加限制: +Because diffs can become very large, we impose these limits on diffs for commits, pull requests, and compare views: -- 在拉取请求中,总差异不得超过可加载的 20,000 行或 1 MB 的原始差异数据 。 -- 任何单个文件的差异都不得超过可加载的 20,000 行或 500 KB 的原始差异数据 。 为单个文件自动加载 400 行和 20 KB 。 -- 单一差异中的最大文件数限于 300。 -- 单一差异中可呈现的文件(如图像、PDF 和 GeoJSON 文件)最大数量限于 25。 +- In a pull request, no total diff may exceed *20,000 lines that you can load* or *1 MB* of raw diff data. +- No single file's diff may exceed *20,000 lines that you can load* or *500 KB* of raw diff data. *Four hundred lines* and *20 KB* are automatically loaded for a single file. +- The maximum number of files in a single diff is limited to *300*. +- The maximum number of renderable files (such as images, PDFs, and GeoJSON files) in a single diff is limited to *25*. -受限差异的某些部分可能会显示,但超过限制的任何部分都不会显示。 +Some portions of a limited diff may be displayed, but anything exceeding the limit is not shown. -### 提交列表限制 +### Commit listings limits -比较视图和拉取请求页显示 `base` 和 `head` 修订之间的提交列表。 这些列表限制为 250 个提交。 如果超过该限制,将会出现一条表示附加评论的注释(但不显示)。 +The compare view and pull requests pages display a list of commits between the `base` and `head` revisions. These lists are limited to **250** commits. If they exceed that limit, a note indicates that additional commits are present (but they're not shown). -## 延伸阅读 +## Further reading -- [创建新存储库](/articles/creating-a-new-repository) -- [关于分支](/github/collaborating-with-pull-requests/working-with-forks/about-forks) -- [协作处理问题和拉取请求](/categories/collaborating-with-issues-and-pull-requests) -- [管理 {% data variables.product.prodname_dotcom %} 上的工作](/categories/managing-your-work-on-github/) -- [管理存储库](/categories/administering-a-repository) -- [使用图形来可视化存储库数据](/categories/visualizing-repository-data-with-graphs/) -- [关于 Wiki](/communities/documenting-your-project-with-wikis/about-wikis) -- [{% data variables.product.prodname_dotcom %} 术语表](/articles/github-glossary) +- "[Creating a new repository](/articles/creating-a-new-repository)" +- "[About forks](/github/collaborating-with-pull-requests/working-with-forks/about-forks)" +- "[Collaborating with issues and pull requests](/categories/collaborating-with-issues-and-pull-requests)" +- "[Managing your work on {% data variables.product.prodname_dotcom %}](/categories/managing-your-work-on-github/)" +- "[Administering a repository](/categories/administering-a-repository)" +- "[Visualizing repository data with graphs](/categories/visualizing-repository-data-with-graphs/)" +- "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)" +- "[{% data variables.product.prodname_dotcom %} glossary](/articles/github-glossary)" diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/cloning-a-repository.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/cloning-a-repository.md index ff8b5facfe..0fd1cafda3 100644 --- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/cloning-a-repository.md +++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/cloning-a-repository.md @@ -1,6 +1,6 @@ --- -title: 克隆仓库 -intro: '在 {% data variables.product.product_location %} 上创建仓库时,它将作为远程仓库存在。 您可以克隆仓库以在计算机上创建本地副本,并在两个位置之间进行同步。' +title: Cloning a repository +intro: 'When you create a repository on {% data variables.location.product_location %}, it exists as a remote repository. You can clone your repository to create a local copy on your computer and sync between the two locations.' redirect_from: - /articles/cloning-a-repository - /articles/cloning-a-repository-from-github @@ -13,26 +13,25 @@ versions: ghec: '*' topics: - Repositories -ms.openlocfilehash: fbe00d1568a2f746362d434e769aef2f3466bcf1 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145129386' --- -## 关于克隆仓库 +## About cloning a repository -您可以将仓库从 {% data variables.product.product_location %} 克隆到本地计算机,以便修复合并冲突、添加或删除文件以及推送较大的提交。 克隆仓库时,将仓库从 {% data variables.product.product_location %} 复制到本地计算机。 +You can clone a repository from {% data variables.location.product_location %} to your local computer to make it easier to fix merge conflicts, add or remove files, and push larger commits. When you clone a repository, you copy the repository from {% data variables.location.product_location %} to your local machine. -克隆仓库将提取 {% data variables.product.product_location %} 在当时拥有的所有仓库数据的完整副本,包括项目每个文件和文件夹的所有版本。 您可以将更改推送到 {% data variables.product.product_location %} 上的远程仓库,或者从 {% data variables.product.product_location %} 拉取其他人的更改。 有关详细信息,请参阅“[使用 Git](/github/getting-started-with-github/using-git)”。 +Cloning a repository pulls down a full copy of all the repository data that {% data variables.location.product_location %} has at that point in time, including all versions of every file and folder for the project. You can push your changes to the remote repository on {% data variables.location.product_location %}, or pull other people's changes from {% data variables.location.product_location %}. For more information, see "[Using Git](/github/getting-started-with-github/using-git)". -您可以克隆自己的现有仓库或克隆其他人的现有仓库以参与项目。 +You can clone your existing repository or clone another person's existing repository to contribute to a project. -## 克隆仓库 +## Cloning a repository {% webui %} -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.copy-clone-url %} {% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.change-current-directory-clone %} {% data reusables.command_line.git-clone-url %} {% data reusables.command_line.local-clone-created %} +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.copy-clone-url %} +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.command_line.change-current-directory-clone %} +{% data reusables.command_line.git-clone-url %} +{% data reusables.command_line.local-clone-created %} {% endwebui %} @@ -40,54 +39,59 @@ ms.locfileid: '145129386' {% data reusables.cli.cli-learn-more %} -若要在本地克隆存储库,请使用 `repo clone` 子命令。 将 `repository` 参数替换为存储库名称。 例如,`octo-org/octo-repo`、`monalisa/octo-repo` 或 `octo-repo`。 如果省略 `OWNER/REPO` 存储库参数的 `OWNER/` 部分,则默认为验证用户的名称。 +To clone a repository locally, use the `repo clone` subcommand. Replace the `repository` parameter with the repository name. For example, `octo-org/octo-repo`, `monalisa/octo-repo`, or `octo-repo`. If the `OWNER/` portion of the `OWNER/REPO` repository argument is omitted, it defaults to the name of the authenticating user. ```shell -gh repo clone repository +gh repo clone REPOSITORY ``` -您也可以使用 GitHub URL来克隆仓库。 +You can also use the GitHub URL to clone a repository. ```shell -gh repo clone https://github.com/cli/cli +gh repo clone https://github.com/PATH-TO/REPOSITORY ``` {% endcli %} {% desktop %} -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.open-with-github-desktop %} -4. 按照 {% data variables.product.prodname_desktop %} 中的提示完成克隆。 +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.open-with-github-desktop %} +4. Follow the prompts in {% data variables.product.prodname_desktop %} to complete the clone. -有关详细信息,请参阅“[将存储库从 {% data variables.product.prodname_dotcom %} 克隆到 {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)”。 +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/)." {% enddesktop %} -## 克隆空仓库 +## Cloning an empty repository -空仓库不含任何文件。 如果创建仓库时不使用 README 初始化仓库,通常会出现空仓库。 +An empty repository contains no files. It's often made if you don't initialize the repository with a README when creating it. {% data reusables.repositories.navigate-to-repo %} -2. 要使用 HTTPS 通过命令行克隆存储库,请在“快速设置”下单击 {% octicon "clippy" aria-label="The clipboard icon" %}。 要使用 SSH 密钥克隆存储库,包括组织的 SSH 证书颁发机构颁发的证书,请单击“SSH”,然后单击 {% octicon "clippy" aria-label="The clipboard icon" %}。 - ![空存储库克隆 URL 按钮](/assets/images/help/repository/empty-https-url-clone-button.png) +2. To clone your repository using the command line using HTTPS, under "Quick setup", click {% octicon "clippy" aria-label="The clipboard icon" %}. To clone the repository using an SSH key, including a certificate issued by your organization's SSH certificate authority, click **SSH**, then click {% octicon "clippy" aria-label="The clipboard icon" %}. + ![Empty repository clone URL button](/assets/images/help/repository/empty-https-url-clone-button.png) - 或者,要在 Desktop 中克隆存储库,请单击 {% octicon "desktop-download" aria-label="The desktop download button" %}“在 Desktop 中进行设置”,然后按照提示完成克隆。 - ![空存储库克隆桌面按钮](/assets/images/help/repository/empty-desktop-clone-button.png) + Alternatively, to clone your repository in Desktop, click {% octicon "desktop-download" aria-label="The desktop download button" %} **Set up in Desktop** and follow the prompts to complete the clone. + ![Empty repository clone desktop button](/assets/images/help/repository/empty-desktop-clone-button.png) -{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.change-current-directory-clone %} {% data reusables.command_line.git-clone-url %} {% data reusables.command_line.local-clone-created %} +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.command_line.change-current-directory-clone %} +{% data reusables.command_line.git-clone-url %} +{% data reusables.command_line.local-clone-created %} -## 排查克隆错误 +## Troubleshooting cloning errors -在克隆仓库时,可能会遇到一些错误。 +When cloning a repository it's possible that you might encounter some errors. -如果无法克隆仓库,请检查: +If you're unable to clone a repository, check that: -- 您可以使用 HTTPS 连接。 有关详细信息,请参阅“[HTTPS 克隆错误](/github/creating-cloning-and-archiving-repositories/https-cloning-errors)”。 -- 您有权访问要克隆的仓库。 有关详细信息,请参阅“[错误:找不到存储库](/github/creating-cloning-and-archiving-repositories/error-repository-not-found)”。 -- 要克隆的默认分支仍然存在。 有关详细信息,请参阅“[错误:远程 HEAD 引用不存在的 ref,无法签出](/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors#error-remote-head-refers-to-nonexistent-ref-unable-to-checkout)”。 +- You can connect using HTTPS. For more information, see "[HTTPS cloning errors](/github/creating-cloning-and-archiving-repositories/https-cloning-errors)." +- You have permission to access the repository you want to clone. For more information, see "[Error: Repository not found](/github/creating-cloning-and-archiving-repositories/error-repository-not-found)." +- The default branch you want to clone still exists. For more information, see "[Error: Remote HEAD refers to nonexistent ref, unable to checkout](/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors#error-remote-head-refers-to-nonexistent-ref-unable-to-checkout)." {% ifversion fpt or ghec %} -## 延伸阅读 +## Further reading -- [排查连接问题](/articles/troubleshooting-connectivity-problems){% endif %} +- "[Troubleshooting connectivity problems](/articles/troubleshooting-connectivity-problems)" +{% endif %} diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md index 6f165d4a17..a94ca77b5a 100644 --- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md +++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md @@ -1,6 +1,6 @@ --- -title: 复制仓库 -intro: 要维护存储库的镜像而不对其进行复刻,可以运行特殊的克隆命令,然后镜像推送到新存储库。 +title: Duplicating a repository +intro: 'To maintain a mirror of a repository without forking it, you can run a special clone command, then mirror-push to the new repository.' redirect_from: - /articles/duplicating-a-repo - /articles/duplicating-a-repository @@ -13,98 +13,92 @@ versions: ghec: '*' topics: - Repositories -ms.openlocfilehash: c9cc58acd7f3b69ff277830bef8dc50fed02c2b6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145129370' --- {% ifversion fpt or ghec %} {% note %} -注意:如果你在其他版本控制系统上托管了项目,则可以使用 {% data variables.product.prodname_dotcom %} 导入程序工具自动将项目导入到 {% data variables.product.prodname_dotcom %}。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_dotcom %} 导入程序](/get-started/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)”。 +**Note:** If you have a project hosted on another version control system, you can automatically import your project to {% data variables.product.prodname_dotcom %} using the {% data variables.product.prodname_dotcom %} Importer tool. For more information, see "[About {% data variables.product.prodname_dotcom %} Importer](/get-started/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)." {% endnote %} {% endif %} -在将原始存储库推送到存储库的新副本或镜像之前,必须在 {% data variables.product.product_location %} 上[创建新的存储库](/articles/creating-a-new-repository)。 在这些示例中,`exampleuser/new-repository` 或 `exampleuser/mirrored` 为镜像。 +Before you can push the original repository to your new copy, or _mirror_, of the repository, you must [create the new repository](/articles/creating-a-new-repository) on {% data variables.location.product_location %}. In these examples, `exampleuser/new-repository` or `exampleuser/mirrored` are the mirrors. -## 镜像仓库 +## Mirroring a repository {% data reusables.command_line.open_the_multi_os_terminal %} -2. 创建仓库的裸克隆。 +2. Create a bare clone of the repository. ```shell - $ git clone --bare https://{% data variables.command_line.codeblock %}/exampleuser/old-repository.git + $ git clone --bare https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/OLD-REPOSITORY.git ``` -3. 镜像推送至新仓库。 +3. Mirror-push to the new repository. ```shell - $ cd old-repository.git - $ git push --mirror https://{% data variables.command_line.codeblock %}/exampleuser/new-repository.git + $ cd OLD-REPOSITORY.git + $ git push --mirror https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/NEW-REPOSITORY.git ``` -4. 删除您之前创建的临时本地仓库。 +4. Remove the temporary local repository you created earlier. ```shell $ cd .. - $ rm -rf old-repository.git + $ rm -rf OLD-REPOSITORY.git ``` -## 镜像包含 {% data variables.large_files.product_name_long %} 对象的仓库。 +## Mirroring a repository that contains {% data variables.large_files.product_name_long %} objects {% data reusables.command_line.open_the_multi_os_terminal %} -2. 创建仓库的裸克隆。 将示例用户名替换为拥有仓库的个人或组织的名称,并将示例仓库名称替换为要复制的仓库的名称。 +2. Create a bare clone of the repository. Replace the example username with the name of the person or organization who owns the repository, and replace the example repository name with the name of the repository you'd like to duplicate. ```shell - $ git clone --bare https://{% data variables.command_line.codeblock %}/exampleuser/old-repository.git + $ git clone --bare https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/OLD-REPOSITORY.git ``` -3. 导航到刚克隆的仓库。 +3. Navigate to the repository you just cloned. ```shell - $ cd old-repository.git + $ cd OLD-REPOSITORY.git ``` -4. 拉取仓库的 {% data variables.large_files.product_name_long %} 对象。 +4. Pull in the repository's {% data variables.large_files.product_name_long %} objects. ```shell $ git lfs fetch --all ``` -5. 镜像推送至新仓库。 +5. Mirror-push to the new repository. ```shell - $ git push --mirror https://{% data variables.command_line.codeblock %}/exampleuser/new-repository.git + $ git push --mirror https://{% data variables.command_line.codeblock %}EXAMPLE-USER/NEW-REPOSITORY.git ``` -6. 将仓库的 {% data variables.large_files.product_name_long %} 对象推送至镜像。 +6. Push the repository's {% data variables.large_files.product_name_long %} objects to your mirror. ```shell - $ git lfs push --all https://github.com/exampleuser/new-repository.git + $ git lfs push --all https://github.com/EXAMPLE-USER/NEW-REPOSITORY.git ``` -7. 删除您之前创建的临时本地仓库。 +7. Remove the temporary local repository you created earlier. ```shell $ cd .. - $ rm -rf old-repository.git + $ rm -rf OLD-REPOSITORY.git ``` -## 镜像其他位置的仓库 +## Mirroring a repository in another location -如果要镜像其他位置的仓库,包括从原始位置获取更新,可以克隆镜像并定期推送更改。 +If you want to mirror a repository in another location, including getting updates from the original, you can clone a mirror and periodically push the changes. {% data reusables.command_line.open_the_multi_os_terminal %} -2. 创建仓库的裸镜像克隆。 +2. Create a bare mirrored clone of the repository. ```shell - $ git clone --mirror https://{% data variables.command_line.codeblock %}/exampleuser/repository-to-mirror.git + $ git clone --mirror https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/REPOSITORY-TO-MIRROR.git ``` -3. 设置到镜像的推送位置。 +3. Set the push location to your mirror. ```shell - $ cd repository-to-mirror - $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/exampleuser/mirrored + $ cd REPOSITORY-TO-MIRROR + $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/MIRRORED ``` -与裸克隆一样,镜像的克隆包括所有远程分支和标记,但每次获取时都会覆盖所有本地引用,因此它始终与原始仓库相同。 设置推送 URL 可简化至镜像的推送。 +As with a bare clone, a mirrored clone includes all remote branches and tags, but all local references will be overwritten each time you fetch, so it will always be the same as the original repository. Setting the URL for pushes simplifies pushing to your mirror. -4. 如需更新镜像,请获取更新和推送。 +4. To update your mirror, fetch updates and push. ```shell $ git fetch -p origin $ git push --mirror ``` {% ifversion fpt or ghec %} -## 延伸阅读 +## Further reading -* [将更改推送到 GitHub](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github#pushing-changes-to-github) -* [关于 Git 大文件存储和 GitHub Desktop](/desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop) -* [关于 GitHub 导入工具](/get-started/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer) +* "[Pushing changes to GitHub](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github#pushing-changes-to-github)" +* "[About Git Large File Storage and GitHub Desktop](/desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop)" +* "[About GitHub Importer](/get-started/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)" {% endif %} diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md index 3503db2111..86cdc8a075 100644 --- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md +++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md @@ -1,6 +1,6 @@ --- -title: 恢复已删除的仓库 -intro: '{% ifversion ghes or ghae %}企业所有者{% elsif fpt or ghec %}你{% endif %}可还原某些已删除的存储库以恢复其内容。' +title: Restoring a deleted repository +intro: '{% ifversion ghes or ghae %}An enterprise owner{% elsif fpt or ghec %}You{% endif %} can restore some deleted repositories to recover their contents.' permissions: '{% ifversion ghes or ghae %}{% elsif fpt or ghec %}Anyone can restore deleted repositories that were owned by their own personal account. Organization owners can restore deleted repositories that were owned by the organization.{% endif %}' redirect_from: - /articles/restoring-a-deleted-repository @@ -14,40 +14,43 @@ versions: topics: - Repositories shortTitle: Restore deleted repository -ms.openlocfilehash: 233785cc42ac6dd97a35d042186ae198dd69502a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146200096' --- + {% ifversion ghes or ghae %} -通常,企业所有者{% ifversion ghes %}可在 {% data variables.product.product_location %}{% endif %} 上在删除后的 90 天内还原已删除的存储库。 有关详细信息,请参阅“[还原已删除的存储库](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)”。 +Usually, deleted repositories can be restored within 90 days by an enterprise owner{% ifversion ghes %} on {% data variables.location.product_location %}{% endif %}. For more information, see "[Restoring a deleted repository](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)." {% else %} -## 关于仓库恢复 +## About repository restoration -删除的仓库可在 90 天内恢复,除非仓库是目前非空白的复刻网络的一部分。 复刻网络由父仓库、仓库的复刻以及该仓库复刻的复刻组成。 如果仓库是复刻网络的一部分,则在网络中的每个其他仓库被删除或者从网络中脱离之前,无法恢复它。 有关分支的详细信息,请参阅“[关于分支](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)”。 +A deleted repository can be restored within 90 days, unless the repository was part of a fork network that is not currently empty. A fork network consists of a parent repository, the repository's forks, and forks of the repository's forks. If your repository was part of a fork network, it cannot be restored unless every other repository in the network is deleted or has been detached from the network. For more information about forks, see "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)." -如果要恢复属于当前非空白的复刻网络一部分的仓库,可以联系 {% data variables.contact.contact_support %}。 +If you want to restore a repository that was part of a fork network that is not currently empty, you can contact {% data variables.contact.contact_support %}. -仓库被删除后,可能需要一个小时才能恢复。 +It can take up to an hour after a repository is deleted before that repository is available for restoration. -恢复仓库不会恢复发行版附件或团队权限。 已恢复的议题不会被标记。 +Restoring a repository will not restore release attachments or team permissions. Issues that are restored will not be labeled. -## 还原个人帐户所拥有的已删除存储库 +## Restoring a deleted repository that was owned by a personal account -{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.repo-tab %} {% data reusables.user-settings.deleted-repos %} {% data reusables.user-settings.restore-repo %} {% data reusables.user-settings.restore-confirmation %} +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.repo-tab %} +{% data reusables.user-settings.deleted-repos %} +{% data reusables.user-settings.restore-repo %} +{% data reusables.user-settings.restore-confirmation %} -## 恢复组织所拥有的已删除仓库 +## Restoring a deleted repository that was owned by an organization -{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.deleted-repos %} {% data reusables.user-settings.restore-repo %} {% data reusables.user-settings.restore-confirmation %} +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +{% data reusables.organizations.deleted-repos %} +{% data reusables.user-settings.restore-repo %} +{% data reusables.user-settings.restore-confirmation %} -## 延伸阅读 +## Further reading -- [删除存储库](/articles/deleting-a-repository) +- "[Deleting a repository](/articles/deleting-a-repository)" {% endif %} diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md index ec9b66273e..21b3f9b46b 100644 --- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md +++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md @@ -1,6 +1,6 @@ --- -title: 排查克隆错误 -intro: 如果您在克隆存储库时遇到问题,请检查这些常见错误。 +title: Troubleshooting cloning errors +intro: 'If you''re having trouble cloning a repository, check these common errors.' redirect_from: - /articles/error-the-requested-url-returned-error-403 - /articles/error-the-requested-url-returned-error-401 @@ -19,45 +19,41 @@ versions: ghec: '*' topics: - Repositories -ms.openlocfilehash: 60a5ff0350fed34841099c18f495b185b75f9832 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147093140' --- -## HTTPS 克隆错误 -对 Git 使用 HTTPS 时有几种常见错误。 这些错误通常表示您有旧版 Git,或无法访问仓库。 +## HTTPS cloning errors -下面是您可能收到的 HTTPS 错误示例: +There are a few common errors when using HTTPS with Git. These errors usually indicate you have an old version of Git, or you don't have access to the repository. + +Here's an example of an HTTPS error you might receive: ```shell > error: The requested URL returned error: 401 while accessing -> https://{% data variables.command_line.codeblock %}/user/repo.git/info/refs?service=git-receive-pack +> https://{% data variables.command_line.codeblock %}/USER/REPO.git/info/refs?service=git-receive-pack > fatal: HTTP request failed ``` ```shell > Error: The requested URL returned error: 403 while accessing -> https://{% data variables.command_line.codeblock %}/user/repo.git/info/refs +> https://{% data variables.command_line.codeblock %}/USER/REPO.git/info/refs > fatal: HTTP request failed ``` ```shell -> Error: https://{% data variables.command_line.codeblock %}/user/repo.git/info/refs not found: did you run git +> Error: https://{% data variables.command_line.codeblock %}/USER/REPO.git/info/refs not found: did you run git > update-server-info on the server? ``` -### 检查 Git 版本 +### Check your Git version -与 {% data variables.product.product_name %} 交互没有最低 Git 版本要求,但我们发现 1.7.10 版是一个方便、稳定的版本,适用于许多平台。 你可以始终在 [Git 网站上下载最新版本](https://git-scm.com/downloads)。 +There's no minimum Git version necessary to interact with {% data variables.product.product_name %}, but we've found version 1.7.10 to be a comfortable stable version that's available on many platforms. You can always [download the latest version on the Git website](https://git-scm.com/downloads). -### 确保远程正确 +### Ensure the remote is correct -您要提取的仓库必须存在于 {% data variables.product.product_location %} 上,且 URL 区分大小写。 +The repository you're trying to fetch must exist on {% data variables.location.product_location %}, and the URL is case-sensitive. -可以打开命令行并键入 `git remote -v` 来查找本地存储库的 URL: +You can find the URL of the local repository by opening the command line and +typing `git remote -v`: ```shell $ git remote -v @@ -74,86 +70,89 @@ $ git remote -v > origin https://github.com/ghost/ReactiveCocoa.git (push) ``` -也可通过 [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) 应用程序更改 URL。 +Alternatively, you can change the URL through our +[{% data variables.product.prodname_desktop %}](https://desktop.github.com/) application. -### 提供访问令牌 +### Provide an access token -要访问 {% data variables.product.prodname_dotcom %},您必须使用个人访问令牌而不是密码进行身份验证。 有关详细信息,请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 +To access {% data variables.product.prodname_dotcom %}, you must authenticate with a {% data variables.product.pat_generic %} instead of your password. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." {% data reusables.command_line.provide-an-access-token %} -### 检查权限 +### Check your permissions -提示输入用户名和密码时,确保使用可以访问仓库的帐户。 +When prompted for a username and password, make sure you use an account that has access to the repository. {% tip %} -提示:如果不想在每次与远程存储库交互时都输入用户名和密码,可以打开[凭据缓存](/github/getting-started-with-github/caching-your-github-credentials-in-git)。 如果已在使用凭据缓存,请确保您的计算机缓存了正确的凭据。 不正确或过期的凭据将导致身份验证失败。 +**Tip**: If you don't want to enter your credentials every time you interact with the remote repository, you can turn on [credential caching](/github/getting-started-with-github/caching-your-github-credentials-in-git). If you are already using credential caching, please make sure that your computer has the correct credentials cached. Incorrect or out of date credentials will cause authentication to fail. {% endtip %} -### 改用 SSH +### Use SSH instead -如果您以前设置了 SSH 密钥,便可使用 SSH 克隆 URL,而不使用 HTTPS。 有关详细信息,请参阅“[关于远程存储库](/github/getting-started-with-github/about-remote-repositories)”。 +If you've previously set up SSH keys, you can use the SSH clone URL instead of HTTPS. For more information, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)." -## 错误:未找到仓库 +## Error: Repository not found -{% ifversion fpt or ghae or ghec %}如果在克隆存储库时看到此错误,这意味着存储库不存在或者你无权访问它。{% else %}如果在克隆存储库时看到此错误,这意味着存储库不存在或者你无权访问它,或者 {% data variables.product.product_location %} 处于专用模式。{% endif %} 此错误有一些解决方案,具体取决于错误原因。 +{% ifversion fpt or ghae or ghec %}If you see this error when cloning a repository, it means that the repository does not exist or you do not have permission to access it.{% else %}If you see this error when cloning a repository, it means that the repository does not exist, you do not have permission to access it, or {% data variables.location.product_location %} is in private mode.{% endif %} There are a few solutions to this error, depending on the cause. -### 检查拼写 +### Check your spelling -拼写错误可能发生,并且仓库名称区分大小写。 如果尝试克隆 `git@{% data variables.command_line.codeblock %}:user/repo.git`,但存储库已实际命名为 `User/Repo`,则会收到此错误。 +Typos happen, and repository names are case-sensitive. If you try to clone `git@{% data variables.command_line.codeblock %}:user/repo.git`, but the repository is really named `User/Repo` you will receive this error. -要避免此错误,克隆时,始终从仓库页面复制和粘贴克隆 URL。 有关详细信息,请参阅“[克隆存储库](/articles/cloning-a-repository)”。 +To avoid this error, when cloning, always copy and paste the clone URL from the repository's page. For more information, see "[Cloning a repository](/articles/cloning-a-repository)." -若要更新现有存储库上的的远程存储,请参阅“[管理远程存储库](/github/getting-started-with-github/managing-remote-repositories)”。 +To update the remote on an existing repository, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)". -### 检查权限 +### Checking your permissions -如果您尝试克隆私有仓库,但没有查看仓库的权限,您将收到此错误。 +If you are trying to clone a private repository but do not have permission to view the repository, you will receive this error. -确保您通过以下方式之一中,拥有仓库的访问权限: +Make sure that you have access to the repository in one of these ways: -* 仓库所有者 -* 存储库上的[协作者](/articles/inviting-collaborators-to-a-personal-repository) -* 拥有存储库访问权限的[团队成员](/articles/adding-organization-members-to-a-team)(如果存储库属于组织) +* The owner of the repository +* A [collaborator](/articles/inviting-collaborators-to-a-personal-repository) on the repository +* A [member of a team](/articles/adding-organization-members-to-a-team) that has access to the repository (if the repository belongs to an organization) -### 检查 SSH 访问权限 +### Check your SSH access -在极少数情况下,您可能没有仓库的适当 SSH 访问权限。 +In rare circumstances, you may not have the proper SSH access to a repository. -应确保正在使用的 SSH 密钥已连接到你在 {% data variables.product.product_name %} 上的个人帐户。 可以通过在命令行中键入以下内容检查此项: +You should ensure that the SSH key you are using is attached to your personal account on {% data variables.product.product_name %}. You can check this by typing +the following into the command line: ```shell $ ssh -T git@{% data variables.command_line.codeblock %} -> Hi username! You've successfully authenticated, but GitHub does not +> Hi USERNAME! You've successfully authenticated, but GitHub does not > provide shell access. ``` -{% ifversion fpt or ghec %} 如果存储库属于某一组织并且你使用的是 OAuth 应用生成的 SSH 密钥,则 OAuth 应用访问权限可能已被组织所有者所限制。 有关详细信息,请参阅“[关于 OAuth 应用访问限制](/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions)”。 +{% ifversion fpt or ghec %} +If the repository belongs to an organization and you're using an SSH key generated by an OAuth App, OAuth App access may have been restricted by an organization owner. For more information, see "[About OAuth App access restrictions](/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions)." {% endif %} -有关详细信息,请参阅“[将新的 SSH 密钥添加到 GitHub 帐户](/articles/adding-a-new-ssh-key-to-your-github-account)”。 +For more information, see [Adding a new SSH key to your GitHub account](/articles/adding-a-new-ssh-key-to-your-github-account). {% ifversion ghes %} -### 检查实例是否处于私有模式 +### Check if your instance is in private mode -如果站点管理员已对你的 GitHub Enterprise 实例启用专用模式,将禁用通过 `git://` 进行的匿名克隆。 如果您无法克隆仓库,请联系您的站点管理员。 +If your site administrator has enabled private mode on your GitHub Enterprise instance, anonymous clones over `git://` will be disabled. If you are unable to clone a repository, contact your site administrator. {% endif %} -### 检查仓库是否确实存在 +### Check that the repository really exists -如果所有其他内容失败,确保仓库在 {% data variables.product.product_location %} 上确实存在! -如果您尝试推送不存在的仓库,您将收到此错误。 +If all else fails, make sure that the repository really exists on {% data variables.location.product_location %}! +If you're trying to push to a repository that doesn't exist, you'll get this error. -## 错误:远程 HEAD 引用不存在的 ref,无法检出 +## Error: Remote HEAD refers to nonexistent ref, unable to checkout -如果已在 {% data variables.product.product_location %} 上删除仓库的默认分支,会发生此错误。 +This error occurs if the default branch of a repository has been deleted on {% data variables.location.product_location %}. -检测此错误很简单;当您尝试克隆以下仓库时,Git 会警告您: +Detecting this error is simple; Git will warn you when you try to clone the repository: ```shell -$ git clone https://{% data variables.command_line.codeblock %}/user/repo.git +$ git clone https://{% data variables.command_line.codeblock %}/USER/REPO.git # Clone a repo > Cloning into 'repo'... > remote: Counting objects: 66179, done. @@ -164,10 +163,10 @@ $ git clone https://{% data variables.command_line.codeblock %}/user/ warning: remote HEAD refers to nonexistent ref, unable to checkout. ``` -要修复此错误,您需要成为 {% data variables.product.product_location %} 上仓库的管理员。 -你将要[更改存储库的默认分支](/github/administering-a-repository/changing-the-default-branch)。 +To fix the error, you'll need to be an administrator of the repository on {% data variables.location.product_location %}. +You'll want to [change the default branch](/github/administering-a-repository/changing-the-default-branch) of the repository. -之后,您可以从命令行获取所有可用分支的列表: +After that, you can get a list of all the available branches from the command line: ```shell $ git branch -a @@ -177,7 +176,7 @@ $ git branch -a > remotes/origin/new-main ``` -然后,您可以切换到新分支: +Then, you can just switch to your new branch: ```shell $ git checkout new-main diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md index 53cf00e556..343a994c1e 100644 --- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md +++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md @@ -58,12 +58,12 @@ To reduce the size of your CODEOWNERS file, consider using wildcard patterns to A CODEOWNERS file uses a pattern that follows most of the same rules used in [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) files. The pattern is followed by one or more {% data variables.product.prodname_dotcom %} usernames or team names using the standard `@username` or `@org/team-name` format. Users and teams must have explicit `write` access to the repository, even if the team's members already have access. -{% ifversion fpt or ghec%}In most cases, you{% else %}You{% endif %} can also refer to a user by an email address that has been added to their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, for example `user@example.com`. {% ifversion fpt or ghec %} You cannot use an email address to refer to a {% data variables.product.prodname_managed_user %}. For more information about {% data variables.product.prodname_managed_users %}, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} +{% ifversion fpt or ghec%}In most cases, you{% else %}You{% endif %} can also refer to a user by an email address that has been added to their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, for example `user@example.com`. {% ifversion fpt or ghec %} You cannot use an email address to refer to a {% data variables.enterprise.prodname_managed_user %}. For more information about {% data variables.enterprise.prodname_managed_users %}, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} CODEOWNERS paths are case sensitive, because {% data variables.product.prodname_dotcom %} uses a case sensitive file system. Since CODEOWNERS are evaluated by {% data variables.product.prodname_dotcom %}, even systems that are case insensitive (for example, macOS) must use paths and files that are cased correctly in the CODEOWNERS file. {% ifversion codeowners-errors %} -If any line in your CODEOWNERS file contains invalid syntax, that line will be skipped. When you navigate to the CODEOWNERS file in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, you can see any errors highlighted. A list of errors in a repository's CODEOWNERS file is also accessible via the API. For more information, see "[Repositories](/rest/reference/repos#list-codeowners-errors)" in the REST API documentation. +If any line in your CODEOWNERS file contains invalid syntax, that line will be skipped. When you navigate to the CODEOWNERS file in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, you can see any errors highlighted. A list of errors in a repository's CODEOWNERS file is also accessible via the API. For more information, see "[Repositories](/rest/reference/repos#list-codeowners-errors)" in the REST API documentation. {% else %} If any line in your CODEOWNERS file contains invalid syntax, the file will not be detected and will not be used to request reviews. {% endif %} diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md index 50adc4e0d6..6df07234e6 100644 --- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md +++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md @@ -1,6 +1,6 @@ --- -title: 许可仓库 -intro: GitHub 上的公共仓库常用于共享开源软件。 要使仓库真正开源,您需要许可它供其他人免费使用、更改和分发软件。 +title: Licensing a repository +intro: 'Public repositories on GitHub are often used to share open source software. For your repository to truly be open source, you''ll need to license it so that others are free to use, change, and distribute the software.' redirect_from: - /articles/open-source-licensing - /articles/licensing-a-repository @@ -12,93 +12,87 @@ versions: ghec: '*' topics: - Repositories -ms.openlocfilehash: f49dad5c20909647b1d7da7bb44a80a771337966 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147881794' --- -## 选择合适的许可 +## Choosing the right license -我们创建了 [choosealicense.com](https://choosealicense.com),帮助你了解如何授权代码。 软件许可是告诉其他人,他们能够对您的代码做什么,不能做什么,因此做明智的决定很重要。 +We created [choosealicense.com](https://choosealicense.com), to help you understand how to license your code. A software license tells others what they can and can't do with your source code, so it's important to make an informed decision. -您没有选择许可的义务, 但如果没有许可,就会默认实施版权法,因此您会保留对您的源代码的所有权利,任何人都不能复制、分发您的工作或创建其派生作品。 如果您创建开源项目,强烈建议您包含开源许可。 [开放源代码指南](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project)为项目选择正确许可证提供了额外指导。 +You're under no obligation to choose a license. However, without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work. If you're creating an open source project, we strongly encourage you to include an open source license. The [Open Source Guide](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project) provides additional guidance on choosing the correct license for your project. {% note %} -注意:{% ifversion fpt or ghec %}根据[服务条款](/free-pro-team@latest/github/site-policy/github-terms-of-service),如果你在 {% data variables.product.product_name %} 的公共存储库中发布源代码,{% endif %}{% data variables.product.product_location %} 的其他用户有权查看你的存储库并为其创建分支。 如果您已创建仓库,并且不再希望用户访问它,便可将仓库设为私有。 在将仓库的可见性变为私有时,其他用户创建的现有复刻或本地副本仍将存在。 有关详细信息,请参阅“[设置存储库可见性](/github/administering-a-repository/setting-repository-visibility)”。 +**Note:** If you publish your source code in a public repository on {% data variables.product.product_name %}, {% ifversion fpt or ghec %}according to the [Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service), {% endif %}other users of {% data variables.location.product_location %} have the right to view and fork your repository. If you have already created a repository and no longer want users to have access to the repository, you can make the repository private. When you change the visibility of a repository to private, existing forks or local copies created by other users will still exist. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)." {% endnote %} -## 确定许可的位置 +## Determining the location of your license -大多数用户都会将许可证文本放在存储库根中名为 `LICENSE.txt`(或者 `LICENSE.md` 或 `LICENSE.rst`)的文件中;[此处有来自 Hubot 的示例](https://github.com/github/hubot/blob/master/LICENSE.md)。 +Most people place their license text in a file named `LICENSE.txt` (or `LICENSE.md` or `LICENSE.rst`) in the root of the repository; [here's an example from Hubot](https://github.com/github/hubot/blob/master/LICENSE.md). -有些项目在其自述文件中包含许可的相关信息。 例如,项目的自述文件可能包含一条注释,表示“此项目根据 MIT 许可的条款进行许可”。 +Some projects include information about their license in their README. For example, a project's README may include a note saying "This project is licensed under the terms of the MIT license." -作为最佳实践,我们建议您的项目随附许可文件。 +As a best practice, we encourage you to include the license file with your project. -## 按许可类型搜索 GitHub +## Searching GitHub by license type -你可以使用 `license` 限定符和精确的许可证关键字,根据存储库的许可证或许可证系列来筛选存储库: +You can filter repositories based on their license or license family using the `license` qualifier and the exact license keyword: -许可证 | 许可关键字 +License | License keyword --- | --- -| 学术自由许可证 v3.0 | `afl-3.0` | -| Apache 许可证 2.0 | `apache-2.0` | -| 艺术许可协议 2.0 | `artistic-2.0` | -| Boost 软件许可证 1.0 | `bsl-1.0` | -| 二条款 BSD“简化版”许可证 | `bsd-2-clause` | -| 三条款 BSD“新版”或“修改版”许可证 | `bsd-3-clause` | -| BSD 3 条款净化版许可证 | `bsd-3-clause-clear` | -| 知识共享许可证系列 | `cc` | -| 免费知识共享 v1.0 通用 | `cc0-1.0` | -| 知识共享署名 4.0 | `cc-by-4.0` | -| 知识共享署名相同方式共享 4.0 | `cc-by-sa-4.0` | -| 你想干嘛就干嘛公共许可证 | `wtfpl` | -| 教育社区许可证 v2.0 | `ecl-2.0` | -| Eclipse 公共许可证 1.0 | `epl-1.0` | -| Eclipse 公共许可证 2.0 | `epl-2.0` | -| 欧盟公共许可证 1.1 | `eupl-1.1` | -| GNU Affero 通用公共许可证 v3.0 | `agpl-3.0` | -| GNU 通用公共许可证系列 | `gpl` | -| GNU 通用公共许可证 v2.0 | `gpl-2.0` | -| GNU 通用公共许可证 v3.0 | `gpl-3.0` | -| GNU 宽通用公共许可证系列 | `lgpl` | -| GNU 宽通用公共许可证 v2.1 | `lgpl-2.1` | -| GNU 宽通用公共许可证 v3.0 | `lgpl-3.0` | +| Academic Free License v3.0 | `afl-3.0` | +| Apache license 2.0 | `apache-2.0` | +| Artistic license 2.0 | `artistic-2.0` | +| Boost Software License 1.0 | `bsl-1.0` | +| BSD 2-clause "Simplified" license | `bsd-2-clause` | +| BSD 3-clause "New" or "Revised" license | `bsd-3-clause` | +| BSD 3-clause Clear license | `bsd-3-clause-clear` | +| Creative Commons license family | `cc` | +| Creative Commons Zero v1.0 Universal | `cc0-1.0` | +| Creative Commons Attribution 4.0 | `cc-by-4.0` | +| Creative Commons Attribution Share Alike 4.0 | `cc-by-sa-4.0` | +| Do What The F*ck You Want To Public License | `wtfpl` | +| Educational Community License v2.0 | `ecl-2.0` | +| Eclipse Public License 1.0 | `epl-1.0` | +| Eclipse Public License 2.0 | `epl-2.0` | +| European Union Public License 1.1 | `eupl-1.1` | +| GNU Affero General Public License v3.0 | `agpl-3.0` | +| GNU General Public License family | `gpl` | +| GNU General Public License v2.0 | `gpl-2.0` | +| GNU General Public License v3.0 | `gpl-3.0` | +| GNU Lesser General Public License family | `lgpl` | +| GNU Lesser General Public License v2.1 | `lgpl-2.1` | +| GNU Lesser General Public License v3.0 | `lgpl-3.0` | | ISC | `isc` | -| LaTeX 项目公共许可证 v1.3c | `lppl-1.3c` | -| Microsoft 公共许可证 | `ms-pl` | +| LaTeX Project Public License v1.3c | `lppl-1.3c` | +| Microsoft Public License | `ms-pl` | | MIT | `mit` | -| Mozilla 公共许可证 2.0 | `mpl-2.0` | -| 开放软件许可证 3.0 | `osl-3.0` | -| PostgreSQL 许可证 | `postgresql` | -| SIL 开源字体许可 1.1 | `ofl-1.1` | -| 伊利诺伊大学/NCSA 开源许可证 | `ncsa` | +| Mozilla Public License 2.0 | `mpl-2.0` | +| Open Software License 3.0 | `osl-3.0` | +| PostgreSQL License | `postgresql` | +| SIL Open Font License 1.1 | `ofl-1.1` | +| University of Illinois/NCSA Open Source License | `ncsa` | | The Unlicense | `unlicense` | -| zLib 许可证 | `zlib` | +| zLib License | `zlib` | -按系列许可搜索时,搜索结果将包含该系列的所有许可。 例如,使用查询 `license:gpl` 时,搜索结果将包括由 GNU 通用公共许可证 v2.0 和 GNU 通用公共许可证 v3.0 许可的存储库。 有关详细信息,请参阅“[搜索存储库](/search-github/searching-on-github/searching-for-repositories/#search-by-license)”。 +When you search by a family license, your results will include all licenses in that family. For example, when you use the query `license:gpl`, your results will include repositories licensed under GNU General Public License v2.0 and GNU General Public License v3.0. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-by-license)." -## 检测许可 +## Detecting a license -[开放源代码 Ruby gem 被许可方](https://github.com/licensee/licensee)将存储库的许可证文件与已知许可证的简短列表进行比较。 被许可方还提供[许可证 API](/rest/reference/licenses),[让我们了解 {% data variables.product.product_name %} 上的存储库如何获得许可](https://github.com/blog/1964-open-source-license-usage-on-github-com)。 如果存储库使用的许可证未在[选择许可证网站](https://choosealicense.com/appendix/)上列出,可以[请求包括许可证](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license)。 +[The open source Ruby gem Licensee](https://github.com/licensee/licensee) compares the repository's *LICENSE* file to a short list of known licenses. Licensee also provides the [Licenses API](/rest/reference/licenses) and [gives us insight into how repositories on {% data variables.product.product_name %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](https://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license). -如果您的仓库使用的许可列在“选择许可”网站中,但未明确显示在仓库页面顶部,其中可能包含多个许可或存在其他复杂性。 为使你的许可证被检测到,请简化许可证文件,并在其他地方(例如存储库的自述文件中)注明复杂度 。 +If your repository is using a license that is listed on the Choose a License website and it's not displaying clearly at the top of the repository page, it may contain multiple licenses or other complexity. To have your license detected, simplify your *LICENSE* file and note the complexity somewhere else, such as your repository's *README* file. -## 将许可应用到带现有许可的仓库 +## Applying a license to a repository with an existing license -许可选择器仅当您在 GitHub 上创建新项目时可用。 您可以使用浏览器手动添加许可。 有关将许可证添加到存储库的详细信息,请参阅“[将许可证添加到存储库](/articles/adding-a-license-to-a-repository)”。 +The license picker is only available when you create a new project on GitHub. You can manually add a license using the browser. For more information on adding a license to a repository, see "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)." -![GitHub.com 上许可选择器的屏幕截图](/assets/images/help/repository/repository-license-picker.png) +![Screenshot of license picker on GitHub.com](/assets/images/help/repository/repository-license-picker.png) -## 免责声明 +## Disclaimer -GitHub 开源许可的目标是提供一个起点,帮助您做出明智的决定。 GitHub 显示许可信息以帮助用户了解开源许可以及使用它们的项目。 我们希望它有帮助,但请记住,我们不是律师,像其他人一样,我们也会犯错。 因此,GitHub“按原样”提供信息,对提供或通过其提供的任何信息或许可不做任何保证,并对使用许可信息所造成的损害不承担责任。 如果对适合您的代码的许可有任何疑问,或有任何其他相关的问题,最好咨询专业人员。 +The goal of GitHub's open source licensing efforts is to provide a starting point to help you make an informed choice. GitHub displays license information to help users get information about open source licenses and the projects that use them. We hope it helps, but please keep in mind that we’re not lawyers and that we make mistakes like everyone else. For that reason, GitHub provides the information on an "as-is" basis and makes no warranties regarding any information or licenses provided on or through it, and disclaims liability for damages resulting from using the license information. If you have any questions regarding the right license for your code or any other legal issues relating to it, it’s always best to consult with a professional. -## 延伸阅读 +## Further reading -- 《开放源代码指南》的“[开放源代码的法律层面](https://opensource.guide/legal/)”部分{% ifversion fpt or ghec %} -- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}) {% endif %} +- The Open Source Guides' section "[The Legal Side of Open Source](https://opensource.guide/legal/)"{% ifversion fpt or ghec %} +- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %} diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md index 218d8bc930..188b4b10dc 100644 --- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md +++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md @@ -1,29 +1,25 @@ --- -title: 管理存储库的提交签字策略 -intro: '可以要求用户使用 {% data variables.product.product_name %} 的 Web 界面自动签字其对存储库所做的提交。' +title: Managing the commit signoff policy for your repository +intro: You can require users to automatically sign off on the commits they make to your repository using {% data variables.product.product_name %}'s web interface. versions: feature: commit-signoffs permissions: Organization owners and repository administrators can require all commits to a repository to be signed off by the commit author. topics: - Repositories shortTitle: Manage the commit signoff policy -ms.openlocfilehash: 4002f0767497cb2b0db9e43c9783e0c2982c8d33 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147410719' --- -## 关于提交签字 -提交签字使用户能够确认提交符合有关管理存储库的规则和许可。 可通过 {% data variables.product.product_location %} 的 Web 界面为用户提交在各个存储库上启用强制提交签字,从而使签字提交在提交过程中顺利执行。 为存储库启用强制提交签字后,通过 {% data variables.product.product_location %} 的 Web 界面对该存储库进行的每个提交都将由提交作者自动签字。 +## About commit signoffs -组织所有者还可以在组织级别启用强制提交签字。 有关详细信息,请参阅“[管理组织的提交签字策略](/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization)”。 +Commit signoffs enable users to affirm that a commit complies with the rules and licensing governing a repository. You can enable compulsory commit signoffs on individual repositories for users committing through {% data variables.location.product_location %}'s web interface, making signing off on a commit a seemless part of the commit process. Once compulsory commit signoffs are enabled for a repository, every commit made to that repository through {% data variables.location.product_location %}'s web interface will automatically be signed off on by the commit author. + +Organization owners can also enable compulsory commit signoffs at the organization level. For more information, see "[Managing the commit signoff policy for your organization](/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization)." {% data reusables.repositories.commit-signoffs %} -## 为存储库启用或禁用强制提交签字 +## Enabling or disabling compulsory commit signoffs for your repository -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -1. 选择“要求参与者签署基于 Web 的提交”。 - ![“要求参与者签署基于 Web 的提交”的屏幕截图](/assets/images/help/repository/require-signoffs.png) +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +1. Select **Require contributors to sign off on web-based commits**. + ![Screenshot of Require contributors to sign off on web-based commits](/assets/images/help/repository/require-signoffs.png) \ No newline at end of file diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md index a5a600a8e6..9d2e1efb2c 100644 --- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md +++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md @@ -1,6 +1,6 @@ --- -title: 设置存储库可见性 -intro: 您可选择能够查看仓库的人员。 +title: Setting repository visibility +intro: You can choose who can view your repository. redirect_from: - /articles/making-a-private-repository-public - /articles/making-a-public-repository-private @@ -16,88 +16,89 @@ versions: topics: - Repositories shortTitle: Repository visibility -ms.openlocfilehash: 2ccdafed8e9efe2bf352033d8fa632147f6bb32b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146332019' --- -## 关于仓库可见性更改 +## About repository visibility changes -组织所有者可以限制只有组织所有者才能更改仓库可见性。 有关详细信息,请参阅“[限制组织中的存储库可见性更改](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)”。 +Organization owners can restrict the ability to change repository visibility to organization owners only. For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)." {% ifversion ghec %} -{% data variables.product.prodname_emu_enterprise %} 的成员只能将其个人帐户拥有的存储库的可见性设置为私有,并且其企业组织中的存储库只能是私有的或内部的。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)”。 +Members of an {% data variables.enterprise.prodname_emu_enterprise %} can only set the visibility of repositories owned by their personal account to private, and repositories in their enterprise's organizations can only be private or internal. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." {% endif %} -我们建议在您更改仓库可见性之前审查以下注意事项。 +We recommend reviewing the following caveats before you change the visibility of a repository. {% ifversion ghes or ghae %} {% warning %} -警告:更改大型存储库或存储库网络的可见性可能会影响数据完整性。 可见性变化也可能对复刻产生意外影响。 {% data variables.product.company_short %} 建议在更改仓库网络的可见性之前遵循以下建议。 +**Warning:** Changes to the visibility of a large repository or repository network may affect data integrity. Visibility changes can also have unintended effects on forks. {% data variables.product.company_short %} recommends the following before changing the visibility of a repository network. -- 等待一段时间,让 {% data variables.product.product_location %} 上的活动减少。 +- Wait for a period of reduced activity on {% data variables.location.product_location %}. -- 在继续操作之前,请联系{% ifversion ghes %}站点管理员{% elsif ghae %}企业所有者{% endif %}。 {% ifversion ghes %}站点管理员{% elsif ghae %}企业所有者{% endif %}可以联系 {% data variables.contact.contact_ent_support %} 以获取进一步的指导。 +- Contact your {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %} before proceeding. Your {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %} can contact {% data variables.contact.contact_ent_support %} for further guidance. {% endwarning %} {% endif %} -### 将仓库设为私有 +### Making a repository private {% ifversion fpt or ghes or ghec %} -* {% data variables.product.product_name %} 将分离公共存储库的公共分支并将其放入新的网络中。 公共分支无法设为专用。{% endif %} {%- ifversion ghes or ghec or ghae %} -* 如果您将仓库的可见性从内部更改为私有, {% data variables.product.prodname_dotcom %} 将删除属于任何没有新私有仓库访问权限的用户的复刻。 {% ifversion fpt or ghes or ghec %}任何分支的可见性也将更改为专用。{% elsif ghae %}如果内部存储库具有任何分支,则分支的可见性已是专用的。{% endif %}有关详细信息,请参阅“[删除存储库或更改其可见性时,分支会发生什么情况?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)” +* {% data variables.product.product_name %} will detach public forks of the public repository and put them into a new network. Public forks are not made private.{% endif %} +{%- ifversion ghes or ghec or ghae %} +* 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. {% ifversion fpt or ghes or ghec %}The visibility of any forks will also change to private.{% elsif ghae %}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)" {%- endif %} {%- ifversion fpt %} -* 如果对个人帐户或组织使用 {% data variables.product.prodname_free_user %},有些功能在你将可见性更改为私有后不可用于存储库。 任何已发布的 {% data variables.product.prodname_pages %} 站点都将自动取消发布。 如果您将自定义域添加到 {% data variables.product.prodname_pages %} 站点,应在将仓库设为私有之前删除或更新 DNS 记录,以避免域接管的风险。 有关详细信息,请参阅“[{% data variables.product.company_short %} 的产品](/get-started/learning-about-github/githubs-products) 和 [管理 {% data variables.product.prodname_pages %} 站点的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)”。 +* If you're using {% data variables.product.prodname_free_user %} for personal accounts or organizations, some features won't be available in the repository after you change the visibility to private. Any published {% data variables.product.prodname_pages %} site will be automatically unpublished. 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 "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products) and "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)." {%- endif %} {%- ifversion fpt or ghec %} -* {% 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)”。 -* {% data variables.product.prodname_GH_advanced_security %} 功能,例如 {% data variables.product.prodname_code_scanning %},将停止工作{% ifversion ghec %},除非拥有仓库的组织具有 {% data variables.product.prodname_advanced_security %} 许可证和充分的备用席位{% endif %}。 {% data reusables.advanced-security.more-info-ghas %} {%- endif %} +* {% 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)." +* {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working{% ifversion ghec %} unless the repository is owned by an organization that is part of an enterprise with a license for {% data variables.product.prodname_advanced_security %} and sufficient spare seats{% endif %}. {% data reusables.advanced-security.more-info-ghas %} +{%- endif %} {%- ifversion ghes %} -* 匿名 Git 读取权限不再可用。 有关详细信息,请参阅“[为存储库启用匿名 Git 读取访问](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository)”。 +* Anonymous Git read access is no longer available. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository)." {%- endif %} {% ifversion ghes or ghec or ghae %} -### 将仓库设为内部 +### Making a repository internal -* 仓库的任何复刻都将保留在仓库网络中, {% data variables.product.product_name %} 维护根仓库与复刻之间的关系。 有关详细信息,请参阅“[删除存储库或更改其可见性时,分支会发生什么情况?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)” +* Any forks of the repository will remain in the repository network, and {% data variables.product.product_name %} maintains the relationship between the root repository and the fork. 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)" {% endif %} {% ifversion fpt or ghes or ghec %} -### 将仓库设为公共 +### Making a repository public -* {% data variables.product.product_name %} 将会分离私有复刻并将它们变成独立的私有仓库。 有关详细信息,请参阅“[删除存储库或更改其可见性时,分支会发生什么情况?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)”{% ifversion fpt or ghec %} -* 如果在创建开源项目时将专用存储库转换为公共存储库,请参阅[开源代码指南](http://opensource.guide)以获得有用的提示和指导。 还可以利用 [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}) 免费学习管理开源项目的课程。 您的仓库设为公共后,您还可以查看仓库的社区资料以了解项目是否符合支持贡献者的最佳做法。 有关详细信息,请参阅“[查看社区配置文件](/articles/viewing-your-community-profile)”。 -* 仓库将自动获得对 {% data variables.product.prodname_GH_advanced_security %} 功能的使用权限。 +* {% data variables.product.product_name %} will detach private forks and turn them into a standalone private repository. 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#changing-a-private-repository-to-a-public-repository)"{% ifversion fpt or ghec %} +* If you're converting your private repository to a public repository as part of a move toward creating an open source project, see the [Open Source Guides](http://opensource.guide) for helpful tips and guidelines. You can also take a free course on managing an open source project with [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Once your repository is public, you can also view your repository's community profile to see whether your project meets best practices for supporting contributors. For more information, see "[Viewing your community profile](/articles/viewing-your-community-profile)." +* The repository will automatically gain access to {% data variables.product.prodname_GH_advanced_security %} features. -有关提高存储库安全性的信息,请参阅“[保护存储库](/code-security/getting-started/securing-your-repository)”。{% endif %} +For information about improving repository security, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."{% endif %} {% endif %} -## 更改仓库的可见性 +## Changing a repository's visibility -{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -3. 在“危险区域”下的“更改存储库可见性”右侧,单击“更改可见性”。 - ![“更改可见性”按钮](/assets/images/help/repository/repo-change-vis.png) -4. 选择可见性。 -{% ifversion fpt or ghec %} ![存储库可见性选项的对话框](/assets/images/help/repository/repo-change-select.png){% else %} ![存储库可见性选项的对话框](/assets/images/enterprise/repos/repo-change-select.png){% endif %} -5. 要验证您是否正在更改正确仓库的可见性,请键入您想要更改其可见性的仓库名称。 -6. 单击“我了解,更改存储库可见性”。 -{% ifversion fpt or ghec %} ![确认更改存储库可见性按钮](/assets/images/help/repository/repo-change-confirm.png){% else %} ![确认更改存储库可见性按钮](/assets/images/enterprise/repos/repo-change-confirm.png){% endif %} +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +3. Under "Danger Zone", to the right of to "Change repository visibility", click **Change visibility**. + ![Change visibility button](/assets/images/help/repository/repo-change-vis.png) +4. Select a visibility. +{% ifversion fpt or ghec %} + ![Dialog of options for repository visibility](/assets/images/help/repository/repo-change-select.png){% else %} + ![Dialog of options for repository visibility](/assets/images/enterprise/repos/repo-change-select.png){% endif %} +5. To verify that you're changing the correct repository's visibility, type the name of the repository you want to change the visibility of. +6. Click **I understand, change repository visibility**. +{% ifversion fpt or ghec %} + ![Confirm change of repository visibility button](/assets/images/help/repository/repo-change-confirm.png){% else %} + ![Confirm change of repository visibility button](/assets/images/enterprise/repos/repo-change-confirm.png){% endif %} -## 延伸阅读 -- “[关于存储库](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)” +## Further reading +- "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)" diff --git a/translations/zh-CN/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md b/translations/zh-CN/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md index 288cddafe7..4907c70c9c 100644 --- a/translations/zh-CN/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md +++ b/translations/zh-CN/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md @@ -1,6 +1,6 @@ --- -title: 添加文件到仓库 -intro: '您可以在 {% data variables.product.product_name %} 上或使用命令行将现有文件上传并提交到存储库。' +title: Adding a file to a repository +intro: 'You can upload and commit an existing file to a repository on {% data variables.product.product_name %} or by using the command line.' redirect_from: - /articles/adding-a-file-to-a-repository - /github/managing-files-in-a-repository/adding-a-file-to-a-repository @@ -18,40 +18,37 @@ versions: topics: - Repositories shortTitle: Add a file -ms.openlocfilehash: da76e182a16b1f72b814882b816f487b8290f3be -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147578906' --- -## 将文件添加到 {% data variables.product.product_name %} 上的存储库 -通过浏览器添加到仓库的文件大小限于每个文件 {% data variables.large_files.max_github_browser_size %}。 较大的文件可通过命令行添加,最大每个 {% data variables.large_files.max_github_size %}。 有关详细信息,请参阅“[使用命令行将文件添加到存储库](#adding-a-file-to-a-repository-using-the-command-line)”。 要添加大于 {% data variables.large_files.max_github_size %} 的文件,则必须使用 {% data variables.large_files.product_name_long %}。 有关详细信息,请参阅“[关于 {% data variables.product.product_name %} 的大文件](/repositories/working-with-files/managing-large-files/about-large-files-on-github)”。 +## Adding a file to a repository on {% data variables.product.product_name %} + +Files that you add to a repository via a browser are limited to {% data variables.large_files.max_github_browser_size %} per file. You can add larger files, up to {% data variables.large_files.max_github_size %} each, via the command line. For more information, see "[Adding a file to a repository using the command line](#adding-a-file-to-a-repository-using-the-command-line)." To add files larger than {% data variables.large_files.max_github_size %}, you must use {% data variables.large_files.product_name_long %}. For more information, see "[About large files on {% data variables.product.product_name %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github)." {% tip %} -**提示:** -- 您可以同时将多个文件上传到 {% data variables.product.product_name %}。 +**Tips:** +- You can upload multiple files to {% data variables.product.product_name %} at the same time. - {% data reusables.repositories.protected-branches-block-web-edits-uploads %} {% endtip %} {% data reusables.repositories.navigate-to-repo %} -2. 在文件列表上方,使用“添加文件”下拉列表,在其中单击“上传文件” 。 - ![“添加文件”下拉列表中的“上传文件”](/assets/images/help/repository/upload-files-button.png) -3. 将要上传的文件或文件夹拖放到文件树中。 -![拖放区域](/assets/images/help/repository/upload-files-drag-and-drop.png) {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} -6. 单击“提交更改”。 -![“提交更改”按钮](/assets/images/help/repository/commit-changes-button.png) +2. Above the list of files, using the **Add file** drop-down, click **Upload files**. + !["Upload files" in the "Add file" dropdown](/assets/images/help/repository/upload-files-button.png) +3. Drag and drop the file or folder you'd like to upload to your repository onto the file tree. +![Drag and drop area](/assets/images/help/repository/upload-files-drag-and-drop.png) +{% data reusables.files.write_commit_message %} +{% data reusables.files.choose_commit_branch %} +6. Click **Commit changes**. +![Commit changes button](/assets/images/help/repository/commit-changes-button.png) -## 使用命令行提交文件到仓库 +## Adding a file to a repository using the command line -您可以使用命令行将现有文件上传到 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的存储库。 +You can upload an existing file to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} using the command line. {% tip %} -提示:还可以[将现有文件从 {% data variables.product.product_name %} 网站添加到存储库](/articles/adding-a-file-to-a-repository)。 +**Tip:** You can also [add an existing file to a repository from the {% data variables.product.product_name %} website](/articles/adding-a-file-to-a-repository). {% endtip %} @@ -59,8 +56,10 @@ ms.locfileid: '147578906' {% data reusables.repositories.sensitive-info-warning %} -1. 在计算机上,将要上传到 {% data variables.product.product_name %} 的文件移入在克隆仓库时创建的本地目录。 -{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.switching_directories_procedural %} {% data reusables.git.stage_for_commit %} +1. On your computer, move the file you'd like to upload to {% data variables.product.product_name %} into the local directory that was created when you cloned the repository. +{% data reusables.command_line.open_the_multi_os_terminal %} +{% data reusables.command_line.switching_directories_procedural %} +{% data reusables.git.stage_for_commit %} ```shell $ git add . # Adds the file to your local repository and stages it for commit. {% data reusables.git.unstage-codeblock %} @@ -72,6 +71,6 @@ ms.locfileid: '147578906' ``` {% data reusables.git.git-push %} -## 延伸阅读 +## Further reading -- [将本地托管代码添加到 {% data variables.product.product_name %}](/get-started/importing-your-projects-to-github/importing-source-code-to-github//adding-locally-hosted-code-to-github) +- "[Adding locally hosted code to {% data variables.product.product_name %}](/get-started/importing-your-projects-to-github/importing-source-code-to-github//adding-locally-hosted-code-to-github)" diff --git a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md index 358b0e8a2b..12765fb394 100644 --- a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md +++ b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md @@ -40,11 +40,11 @@ shortTitle: Large files {% endnote %} -{% ifversion ghes %}By default, {% endif %}{% data variables.product.product_name %} blocks files larger than {% data variables.large_files.max_github_size %}. {% ifversion ghes %}However, a site administrator can configure a different limit for {% data variables.product.product_location %}. For more information, see "[Setting Git push limits](/enterprise/admin/guides/installation/setting-git-push-limits)."{% endif %} +{% ifversion ghes %}By default, {% endif %}{% data variables.product.product_name %} blocks files larger than {% data variables.large_files.max_github_size %}. {% ifversion ghes %}However, a site administrator can configure a different limit for {% data variables.location.product_location %}. For more information, see "[Setting Git push limits](/enterprise/admin/guides/installation/setting-git-push-limits)."{% endif %} To track files beyond this limit, you must use {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). For more information, see "[About {% data variables.large_files.product_name_long %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)." -If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %} instead of tracking the files. For more information, see "[Distributing large binaries](#distributing-large-binaries)." +If you need to distribute large files within your repository, you can create releases on {% data variables.location.product_location %} instead of tracking the files. For more information, see "[Distributing large binaries](#distributing-large-binaries)." Git is not designed to handle large SQL files. To share large databases with other developers, we recommend using [Dropbox](https://www.dropbox.com/). @@ -62,13 +62,13 @@ Git is not designed to serve as a backup tool. However, there are many solutions {% warning %} -**Warning**: These procedures will permanently remove files from the repository on your computer and {% data variables.product.product_location %}. If the file is important, make a local backup copy in a directory outside of the repository. +**Warning**: These procedures will permanently remove files from the repository on your computer and {% data variables.location.product_location %}. If the file is important, make a local backup copy in a directory outside of the repository. {% endwarning %} ### Removing a file added in the most recent unpushed commit -If the file was added with your most recent commit, and you have not pushed to {% data variables.product.product_location %}, you can delete the file and amend the commit: +If the file was added with your most recent commit, and you have not pushed to {% data variables.location.product_location %}, you can delete the file and amend the commit: {% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.switching_directories_procedural %} @@ -84,7 +84,7 @@ If the file was added with your most recent commit, and you have not pushed to { # Simply making a new commit won't work, as you need # to remove the file from the unpushed history as well ``` -5. Push your commits to {% data variables.product.product_location %}: +5. Push your commits to {% data variables.location.product_location %}: ```shell $ git push # Push our rewritten, smaller commit @@ -96,7 +96,7 @@ If you added a file in an earlier commit, you need to remove it from the reposit ## Distributing large binaries -If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %}. Releases allow you to package software, release notes, and links to binary files, for other people to use. For more information, visit "[About releases](/github/administering-a-repository/about-releases)." +If you need to distribute large files within your repository, you can create releases on {% data variables.location.product_location %}. Releases allow you to package software, release notes, and links to binary files, for other people to use. For more information, visit "[About releases](/github/administering-a-repository/about-releases)." {% ifversion fpt or ghec %} diff --git a/translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md b/translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md index c0eb7f9851..d16c96cd5e 100644 --- a/translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md +++ b/translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md @@ -1,6 +1,6 @@ --- -title: 创建文件的永久链接 -intro: '在 {% data variables.product.product_location %} 上查看文件时,您可以按 "y" 键将 URL 更新为指向所查看文件精确版本的永久链接。' +title: Getting permanent links to files +intro: 'When viewing a file on {% data variables.location.product_location %}, you can press the "y" key to update the URL to a permalink to the exact version of the file you see.' redirect_from: - /articles/getting-a-permanent-link-to-a-file - /articles/how-do-i-get-a-permanent-link-from-file-view-to-permanent-blob-url @@ -15,49 +15,43 @@ versions: topics: - Repositories shortTitle: Permanent links to files -ms.openlocfilehash: 4e3d5ec282f7f7ba820094240698c88e298cdb69 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145129232' --- {% tip %} -提示:在 {% data variables.product.product_name %} 的任意页面上按“?”可查看所有可用的键盘快捷键。 +**Tip**: Press "?" on any page in {% data variables.product.product_name %} to see all available keyboard shortcuts. {% endtip %} -## 文件视图显示分支上的最新版本 +## File views show the latest version on a branch -在 {% data variables.product.product_location %} 上查看文件时,通常会在分支头部看到当前版本。 例如: +When viewing a file on {% data variables.location.product_location %}, you usually see the version at the current head of a branch. For example: -* [https://github.com/github/codeql/blob/ main/README.md](https://github.com/github/codeql/blob/main/README.md) +* [https://github.com/github/codeql/blob/**main**/README.md](https://github.com/github/codeql/blob/main/README.md) -引用 GitHub 的 `codeql` 存储库,并显示 `main` 分支中 `README.md` 文件的当前版本。 +refers to GitHub's `codeql` repository, and shows the `main` branch's current version of the `README.md` file. -分支头部的文件版本可能会随着新的提交而改变,因此如果您复制常规的 URL,当以后有人查看时,文件内容可能会不同。 +The version of a file at the head of branch can change as new commits are made, so if you were to copy the normal URL, the file contents might not be the same when someone looks at it later. -## 按 Y 永久链接到特定提交中的文件 +## Press Y to permalink to a file in a specific commit -要永久链接到所查看的特定版本的文件,请不要在 URL 中使用分支名称(即上面示例中的 `main` 部分),而是使用提交 ID。这将永久链接到与该提交中完全相同的文件版本。 例如: +For a permanent link to the specific version of a file that you see, instead of using a branch name in the URL (i.e. the `main` part in the example above), put a commit id. This will permanently link to the exact version of the file in that commit. For example: -* [https://github.com/github/codeql/blob/ b212af08a6cffbb434f3c8a2795a579e092792fd/README.md](https://github.com/github/codeql/blob/b212af08a6cffbb434f3c8a2795a579e092792fd/README.md) +* [https://github.com/github/codeql/blob/**b212af08a6cffbb434f3c8a2795a579e092792fd**/README.md](https://github.com/github/codeql/blob/b212af08a6cffbb434f3c8a2795a579e092792fd/README.md) -将 `main` 替换为特定的提交 ID,文件内容将不会发生变化。 +replaces `main` with a specific commit id and the file content will not change. -但是,手动查找提交 SHA 比较麻烦,因此可以采用便捷方式,通过键入 y 将 URL 自动更新为永久链接版本。 然后,您可以复制该 URL,以后访问它的任何人都将看到与您所见完全一致的内容。 +Looking up the commit SHA by hand is inconvenient, however, so as a shortcut you can type y to automatically update the URL to the permalink version. Then you can copy the URL knowing that anyone you share it with will see exactly what you saw. {% tip %} -提示:可以将可解析为提交的任何标识符放在 URL 中,包括分支名称、特定提交 SHA 或标记! +**Tip**: You can put any identifier that can be resolved to a commit in the URL, including branch names, specific commit SHAs, or tags! {% endtip %} -## 创建指向代码段的永久链接 +## Creating a permanent link to a code snippet -您可以创建指向特定版本的文件或拉取请求中特定代码行或行范围的永久链接。 有关详细信息,请参阅“[创建代码片段的永久链接](/articles/creating-a-permanent-link-to-a-code-snippet/)”。 +You can create a permanent link to a specific line or range of lines of code in a specific version of a file or pull request. For more information, see "[Creating a permanent link to a code snippet](/articles/creating-a-permanent-link-to-a-code-snippet/)." -## 延伸阅读 +## Further reading -- [存档 GitHub 存储库](/articles/archiving-a-github-repository) +- "[Archiving a GitHub repository](/articles/archiving-a-github-repository)" diff --git a/translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md index 229230ac98..5dd1df54fe 100644 --- a/translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md +++ b/translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md @@ -49,7 +49,7 @@ shortTitle: Working with non-code files ### Viewing images -You can directly browse and view images in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}: +You can directly browse and view images in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}: ![inline image](/assets/images/help/images/view.png) @@ -144,7 +144,7 @@ GitHub supports rendering tabular data in the form of *.csv* (comma-separated) a ![Rendered CSV sample](/assets/images/help/repository/rendered_csv.png) -When viewed, any _.csv_ or _.tsv_ file committed to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} automatically renders as an interactive table, complete with headers and row numbering. By default, we'll always assume the first row is your header row. +When viewed, any _.csv_ or _.tsv_ file committed to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} automatically renders as an interactive table, complete with headers and row numbering. By default, we'll always assume the first row is your header row. You can link to a particular row by clicking the row number, or select multiple rows by holding down the shift key. Just copy the URL and send it to a friend. @@ -327,9 +327,9 @@ It may still be possible to render the data by converting the `.geojson` file to ## Working with Jupyter Notebook files on {% data variables.product.prodname_dotcom %} -When you add Jupyter Notebook or IPython Notebook files with a *.ipynb* extension on {% data variables.product.product_location %}, they will render as static HTML files in your repository. +When you add Jupyter Notebook or IPython Notebook files with a *.ipynb* extension on {% data variables.location.product_location %}, they will render as static HTML files in your repository. -The interactive features of the notebook, such as custom JavaScript plots, will not work in your repository on {% data variables.product.product_location %}. For an example, see [*Linking and Interactions.ipynb*](https://github.com/bokeh/bokeh-notebooks/blob/main/tutorial/06%20-%20Linking%20and%20Interactions.ipynb). +The interactive features of the notebook, such as custom JavaScript plots, will not work in your repository on {% data variables.location.product_location %}. For an example, see [*Linking and Interactions.ipynb*](https://github.com/bokeh/bokeh-notebooks/blob/main/tutorial/06%20-%20Linking%20and%20Interactions.ipynb). To view your Jupyter notebook with JavaScript content rendered or to share your notebook files with others you can use [nbviewer](https://nbviewer.jupyter.org/). For an example, see [*Linking and Interactions.ipynb*](https://nbviewer.jupyter.org/github/bokeh/bokeh-notebooks/blob/main/tutorial/06%20-%20Linking%20and%20Interactions.ipynb) rendered on nbviewer. diff --git a/translations/zh-CN/content/rest/activity/notifications.md b/translations/zh-CN/content/rest/activity/notifications.md index 3636878dcd..1623a3b424 100644 --- a/translations/zh-CN/content/rest/activity/notifications.md +++ b/translations/zh-CN/content/rest/activity/notifications.md @@ -1,6 +1,6 @@ --- -title: 通知 -intro: '使用通知 API 可以管理 {% data variables.product.product_name %} 通知。' +title: Notifications +intro: 'The Notifications API lets you manage {% data variables.product.product_name %} notifications.' versions: fpt: '*' ghes: '*' @@ -9,22 +9,19 @@ versions: topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 2d68f2b563578608ab66eafbb055edbe5d88d172 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147064272' --- -## 关于通知 API -使用通知 API 可以管理 {% data variables.product.product_name %} 通知。 有关通知的详细信息,请参阅“[关于通知](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)”。 +## About the Notifications API -所有通知 API 调用都需要 `notifications` 或 `repo` API 作用域。 这将赋予对某些议题和提交内容的只读权限。 你仍需要 `repo` 作用域才能从相应的端点访问议题和提交。 +{% data reusables.user-settings.notifications-api-classic-pat-only %} -通知以“帖子”的形式返回。 帖子包含当前对议题、拉取请求或提交的讨论信息。 +The Notifications API lets you manage {% data variables.product.product_name %} notifications. For more information about notifications, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." -通知针对使用 `Last-Modified` 标头的轮询进行了优化。 如果没有新的通知,你将看到 `304 Not Modified` 响应,你的当前速率限制不受影响。 还有一个 `X-Poll-Interval` 标头,用于指定允许你轮询的间隔时间(以秒为单位)。 在服务器负载较高时,该时间可能会增加。 请遵循标头指示。 +All Notification API calls require the `notifications` or `repo` API scopes. Doing this will give read-only access to some issue and commit content. You will still need the `repo` scope to access issues and commits from their respective endpoints. + +Notifications come back as "threads". A thread contains information about the current discussion of an issue, pull request, or commit. + +Notifications are optimized for polling with the `Last-Modified` header. If there are no new notifications, you will see a `304 Not Modified` response, leaving your current rate limit untouched. There is an `X-Poll-Interval` header that specifies how often (in seconds) you are allowed to poll. In times of high server load, the time may increase. Please obey the header. ``` shell # Add authentication to your requests @@ -40,27 +37,27 @@ $ -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT" > X-Poll-Interval: 60 ``` -### 关于通知原因 +### About notification reasons -从通知 API 检索响应时,每个有效负载都有一个名为 `reason` 的键。 这些键对应于触发通知的事件。 +When retrieving responses from the Notifications API, each payload has a key titled `reason`. These correspond to events that trigger a notification. -以下是接收通知的可能 `reason`: +These are the potential `reason`s for receiving a notification: -原因名称 | 说明 +Reason Name | Description ------------|------------ -`assign` | 您被分配到议题。 -`author` | 您创建了帖子。 -`comment` | 您评论了帖子。 -`ci_activity` | 当 {% data variables.product.prodname_actions %} 工作流程运行被请求或完成时。 -`invitation` | 您接受了参与仓库的邀请。 -`manual` | 您订阅了帖子(通过议题或拉取请求) -`mention` | 你在内容中被特别 **@mentioned** 。 -`review_requested` | 您或您所属的团队被请求审查拉取请求。{% ifversion fpt or ghec %} -`security_alert` | {% data variables.product.prodname_dotcom %} 在你的存储库中发现了[安全漏洞](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)。{% endif %} -`state_change` | 您更改了帖子主题(例如关闭议题或合并拉取请求)。 -`subscribed` | 您在关注仓库。 -`team_mention` | 您所属的团队被提及。 +`assign` | You were assigned to the issue. +`author` | You created the thread. +`comment` | You commented on the thread. +`ci_activity` | A {% data variables.product.prodname_actions %} workflow run that you triggered was completed. +`invitation` | You accepted an invitation to contribute to the repository. +`manual` | You subscribed to the thread (via an issue or pull request). +`mention` | You were specifically **@mentioned** in the content. +`review_requested` | You, or a team you're a member of, were requested to review a pull request.{% ifversion fpt or ghec %} +`security_alert` | {% data variables.product.prodname_dotcom %} discovered a [security vulnerability](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in your repository.{% endif %} +`state_change` | You changed the thread state (for example, closing an issue or merging a pull request). +`subscribed` | You're watching the repository. +`team_mention` | You were on a team that was mentioned. -请注意,`reason` 根据每个帖子而修改,如果在以后的通知中,`reason` 不同,其值可能会变更。 +Note that the `reason` is modified on a per-thread basis, and can change, if the `reason` on a later notification is different. -例如,如果你是某个议题的作者,则有关该议题的后续通知中,其 `reason` 值为 `author`。 如果后来你在这个议题上被 **@mentioned** ,则你此后收到的通知中,其 `reason` 值为 `mention`。 无论你此后是否被再次提及,`reason` 值将保持 `mention` 不变。 +For example, if you are the author of an issue, subsequent notifications on that issue will have a `reason` of `author`. If you're then **@mentioned** on the same issue, the notifications you fetch thereafter will have a `reason` of `mention`. The `reason` remains as `mention`, regardless of whether you're ever mentioned again. diff --git a/translations/zh-CN/content/rest/apps/oauth-applications.md b/translations/zh-CN/content/rest/apps/oauth-applications.md index 8db0816d87..e964f5eb47 100644 --- a/translations/zh-CN/content/rest/apps/oauth-applications.md +++ b/translations/zh-CN/content/rest/apps/oauth-applications.md @@ -1,5 +1,5 @@ --- -title: OAuth 应用 +title: OAuth Apps allowTitleToDifferFromFilename: true intro: '' topics: @@ -10,13 +10,8 @@ versions: ghes: '*' ghae: '*' ghec: '*' -ms.openlocfilehash: bb80e0627236ff7e045dd72823201b6d8e750445 -ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/12/2022 -ms.locfileid: '147888434' --- -## 关于 {% data variables.product.prodname_oauth_app %} API -可使用此 API 来管理 {% data variables.product.prodname_oauth_app %} 用于访问用户在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的帐户的 OAuth 标记。 +## About the {% data variables.product.prodname_oauth_app %} API + +You can use this API to manage the OAuth tokens an {% data variables.product.prodname_oauth_app %} uses to access people's accounts on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. diff --git a/translations/zh-CN/content/rest/codespaces/codespaces.md b/translations/zh-CN/content/rest/codespaces/codespaces.md index 3eea611e0c..ce37af620a 100644 --- a/translations/zh-CN/content/rest/codespaces/codespaces.md +++ b/translations/zh-CN/content/rest/codespaces/codespaces.md @@ -1,19 +1,14 @@ --- title: Codespaces -intro: Codespaces API 使你能够使用 REST API 管理 codespace。 +intro: The Codespaces API enables you to manage your codespaces using the REST API. versions: fpt: '*' ghec: '*' topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 0108e8ac59714ecea24e1f19d5adf3f2d0371f15 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147110568' --- -## 关于 Codespaces API -{% data variables.product.prodname_github_codespaces %} API 使你能够使用 REST API 管理 {% data variables.product.prodname_codespaces %}。 此 API 适用于经过验证的用户、OAuth 应用和 GitHub 应用。 有关详细信息,请参阅“[{% data variables.product.prodname_codespaces %}](/codespaces)。” +## About the Codespaces API + +The {% data variables.product.prodname_github_codespaces %} API enables you to manage {% data variables.product.prodname_codespaces %} using the REST API. This API is available for authenticated users, {% data variables.product.prodname_oauth_apps %}, and {% data variables.product.prodname_github_apps %}. For more information, see "[{% data variables.product.prodname_codespaces %}](/codespaces)." diff --git a/translations/zh-CN/content/rest/enterprise-admin/admin-stats.md b/translations/zh-CN/content/rest/enterprise-admin/admin-stats.md index 4f0a9705a5..6be1e3b2cf 100644 --- a/translations/zh-CN/content/rest/enterprise-admin/admin-stats.md +++ b/translations/zh-CN/content/rest/enterprise-admin/admin-stats.md @@ -1,6 +1,6 @@ --- -title: 管理统计 -intro: 管理统计 API 提供有关安装设施的各种指标。 +title: Admin stats +intro: The Admin Stats API provides a variety of metrics about your installation. versions: ghes: '*' ghae: '*' @@ -9,11 +9,8 @@ versions: topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: a3330488afc37426ef68231eb8d4fed515dcfe16 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147060041' --- -它仅适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)网站管理员。 如果普通用户尝试访问它,他们将收到 `404` 响应。 + +*It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. + +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} diff --git a/translations/zh-CN/content/rest/enterprise-admin/announcement.md b/translations/zh-CN/content/rest/enterprise-admin/announcement.md index 0ccd1c9da8..d699a2b2f5 100644 --- a/translations/zh-CN/content/rest/enterprise-admin/announcement.md +++ b/translations/zh-CN/content/rest/enterprise-admin/announcement.md @@ -1,19 +1,16 @@ --- -title: 公告 -intro: 公告 API 使你能够管理企业中的全局公告横幅。 +title: Announcement +intro: The Announcement API allows you to manage the global announcement banner in your enterprise. versions: ghes: '*' ghae: '*' topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: e3394dd67e06c362bb26c547f34124e8a7a198af -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147883017' --- -## 公告 -公告 API 允许您管理企业中的全局公告横幅。 有关详细信息,请参阅“[为企业自定义用户消息](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)”。 +## Announcement + +The Announcements API allows you to manage the global announcement banner in your enterprise. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)." + +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} diff --git a/translations/zh-CN/content/rest/enterprise-admin/audit-log.md b/translations/zh-CN/content/rest/enterprise-admin/audit-log.md index b1442b514c..33ca7acbfc 100644 --- a/translations/zh-CN/content/rest/enterprise-admin/audit-log.md +++ b/translations/zh-CN/content/rest/enterprise-admin/audit-log.md @@ -1,5 +1,5 @@ --- -title: 审核日志 +title: Audit log intro: '' versions: ghes: '>=3.3' @@ -8,11 +8,6 @@ versions: topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 171735e6b5c5e9dbf66aa746ffd1b216779f89f6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147060017' --- +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} diff --git a/translations/zh-CN/content/rest/enterprise-admin/billing.md b/translations/zh-CN/content/rest/enterprise-admin/billing.md index ecae02ba68..ff04adef94 100644 --- a/translations/zh-CN/content/rest/enterprise-admin/billing.md +++ b/translations/zh-CN/content/rest/enterprise-admin/billing.md @@ -1,5 +1,5 @@ --- -title: 计费 +title: Billing intro: '' versions: fpt: '*' @@ -8,11 +8,6 @@ versions: topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 81da9a3e3e7dfaf02bf12fd9b67c90048784e834 -ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147060022' --- +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} diff --git a/translations/zh-CN/content/rest/enterprise-admin/global-webhooks.md b/translations/zh-CN/content/rest/enterprise-admin/global-webhooks.md index 5c90ea5f85..d50e201ec0 100644 --- a/translations/zh-CN/content/rest/enterprise-admin/global-webhooks.md +++ b/translations/zh-CN/content/rest/enterprise-admin/global-webhooks.md @@ -1,19 +1,16 @@ --- -title: 全局 Webhook -intro: 全局 Webhook 安装在企业上。 您可以使用全局 web 挂钩来自动监视、响应或实施针对企业上的用户、组织、团队和仓库的规则。 +title: Global Webhooks +intro: 'Global Webhooks are installed on your enterprise. You can use global webhooks to automatically monitor, respond to, or enforce rules for users, organizations, teams, and repositories on your enterprise.' versions: ghes: '*' ghae: '*' topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 66186eeba470274d91b61aaae700e25716c26ef5 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147067224' --- -全局 Webhook 可以订阅[组织](/developers/webhooks-and-events/webhook-events-and-payloads#organization)、[用户](/developers/webhooks-and-events/webhook-events-and-payloads#user)、[存储库](/developers/webhooks-and-events/webhook-events-and-payloads#repository)、[团队](/developers/webhooks-and-events/webhook-events-and-payloads#team)、[成员](/developers/webhooks-and-events/webhook-events-and-payloads#member)、[成员身份](/developers/webhooks-and-events/webhook-events-and-payloads#membership)、[分支](/developers/webhooks-and-events/webhook-events-and-payloads#fork)和 [ping](/developers/webhooks-and-events/about-webhooks#ping-event) 事件类型。 -此 API 仅适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)网站管理员。 如果普通用户尝试访问它,他们将收到 `404` 响应。 若要了解如何配置全局 Webhook,请参阅[关于全局 Webhook](/enterprise/admin/user-management/about-global-webhooks)。 +Global webhooks can subscribe to the [organization](/developers/webhooks-and-events/webhook-events-and-payloads#organization), [user](/developers/webhooks-and-events/webhook-events-and-payloads#user), [repository](/developers/webhooks-and-events/webhook-events-and-payloads#repository), [team](/developers/webhooks-and-events/webhook-events-and-payloads#team), [member](/developers/webhooks-and-events/webhook-events-and-payloads#member), [membership](/developers/webhooks-and-events/webhook-events-and-payloads#membership), [fork](/developers/webhooks-and-events/webhook-events-and-payloads#fork), and [ping](/developers/webhooks-and-events/about-webhooks#ping-event) event types. + +*This API is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. To learn how to configure global webhooks, see [About global webhooks](/enterprise/admin/user-management/about-global-webhooks). + +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} diff --git a/translations/zh-CN/content/rest/enterprise-admin/index.md b/translations/zh-CN/content/rest/enterprise-admin/index.md index cef2d95009..4e9927d3a9 100644 --- a/translations/zh-CN/content/rest/enterprise-admin/index.md +++ b/translations/zh-CN/content/rest/enterprise-admin/index.md @@ -1,6 +1,6 @@ --- -title: GitHub Enterprise 管理 -intro: 可以使用这些终结点来管理企业。 +title: GitHub Enterprise administration +intro: You can use these endpoints to administer your enterprise. allowTitleToDifferFromFilename: true redirect_from: - /v3/enterprise-admin @@ -31,52 +31,54 @@ children: - /repo-pre-receive-hooks - /users - /scim -ms.openlocfilehash: 19688f806101c8022b64dfc21806b79338917353 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147065591' --- + {% ifversion fpt or ghec %} {% note %} -注意:本文章适用于 {% data variables.product.prodname_ghe_cloud %}。 要查看 {% data variables.product.prodname_ghe_managed %} 或 {% data variables.product.prodname_ghe_server %} 版本,请使用 {% data ui.pages.article_version %} 下拉菜单。 +**Note:** This article applies to {% data variables.product.prodname_ghe_cloud %}. To see the {% data variables.product.prodname_ghe_managed %} or {% data variables.product.prodname_ghe_server %} version, use the **{% data ui.pages.article_version %}** drop-down menu. {% endnote %} {% endif %} -### 端点 URL +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} -REST API 终结点{% ifversion ghes %}([管理控制台](#management-console) API 终结点除外){% endif %} 是以下 URL 的前缀: +### Endpoint URLs + +REST API endpoints{% ifversion ghes %}—except [Management Console](#management-console) API endpoints—{% endif %} are prefixed with the following URL: ```shell {% data variables.product.api_url_pre %} ``` -{% ifversion fpt or ghec %} 当终结点包含 `{enterprise}` 时,将 `{enterprise}` 替换为企业帐户的句柄,该句柄包含在企业设置的 URL 中。 例如,如果企业帐户位于 `https://github.com/enterprises/octo-enterprise`,请用 `octo-enterprise` 替换 `{enterprise}`。 +{% ifversion fpt or ghec %} +When endpoints include `{enterprise}`, replace `{enterprise}` with the handle for your enterprise account, which is included in the URL for your enterprise settings. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `{enterprise}` with `octo-enterprise`. {% endif %} -{% ifversion ghes %} [管理控制台](#management-console) API 终结点仅以主机名为前缀: +{% ifversion ghes %} +[Management Console](#management-console) API endpoints are only prefixed with a hostname: ```shell -http(s)://hostname/ +http(s)://HOSTNAME/ ``` -{% endif %} {% ifversion ghae or ghes %} -### 身份验证 +{% endif %} +{% ifversion ghae or ghes %} +### Authentication -{% data variables.product.product_name %} 安装的 API 终结点接受与 GitHub.com API [相同的身份验证方法](/rest/overview/resources-in-the-rest-api#authentication)。 可通过 [OAuth 标记](/apps/building-integrations/setting-up-and-registering-oauth-apps/){% ifversion ghes %}(可使用[授权 API](/rest/reference/oauth-authorizations#create-a-new-authorization) 创建){% endif %}或[基本身份验证](/rest/overview/resources-in-the-rest-api#basic-authentication)自行进行身份验证 。 {% ifversion ghes %} OAuth 标记用于企业特定的终结点时必须具有 `site_admin` [OAuth 范围](/developers/apps/scopes-for-oauth-apps#available-scopes)。{% endif %} +Your {% data variables.product.product_name %} installation's API endpoints accept [the same authentication methods](/rest/overview/resources-in-the-rest-api#authentication) as the GitHub.com API. You can authenticate yourself with **[OAuth tokens](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% ifversion ghes %}(which can be created using the [Authorizations API](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}or **[basic authentication](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% ifversion ghes %} +OAuth tokens must have the `site_admin` [OAuth scope](/developers/apps/scopes-for-oauth-apps#available-scopes) when used with Enterprise-specific endpoints.{% endif %} -企业管理 API 终结点只有经过身份验证的 {% data variables.product.product_name %} 站点管理员{% ifversion ghes %}可以访问,但[管理控制台](#management-console) API 例外,它需要[管理控制台密码](/enterprise/admin/articles/accessing-the-management-console/){% endif %}。 +Enterprise administration API endpoints are only accessible to authenticated {% data variables.product.product_name %} site administrators{% ifversion ghes %}, except for the [Management Console](#management-console) API, which requires the [Management Console password](/enterprise/admin/articles/accessing-the-management-console/){% endif %}. {% endif %} {% ifversion ghae or ghes %} -### 版本信息 +### Version information -企业当前版本在每个 API 的响应头中返回:`X-GitHub-Enterprise-Version: {{currentVersion}}.0` -还可通过调用[元终结点](/rest/reference/meta/)来读取当前版本。 +The current version of your enterprise is returned in the response header of every API: +`X-GitHub-Enterprise-Version: {{currentVersion}}.0` +You can also read the current version by calling the [meta endpoint](/rest/reference/meta/). {% endif %} diff --git a/translations/zh-CN/content/rest/enterprise-admin/ldap.md b/translations/zh-CN/content/rest/enterprise-admin/ldap.md index d420968694..c4727266f5 100644 --- a/translations/zh-CN/content/rest/enterprise-admin/ldap.md +++ b/translations/zh-CN/content/rest/enterprise-admin/ldap.md @@ -1,16 +1,13 @@ --- title: LDAP -intro: '您可以使用 LDAP API 来更新 {% data variables.product.product_name %} 用户或团队与其关联的 LDAP 条目之间的帐户关系,或者排队新同步。' +intro: 'You can use the LDAP API to update account relationships between a {% data variables.product.product_name %} user or team and its linked LDAP entry or queue a new synchronization.' versions: ghes: '*' topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 0948fbf02aea86d01a7034ae6b1836c0f69ca6e2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147065336' --- -通过 LDAP 映射端点,您可以更新用户或团队所映射的识别名称 (DN) 。 请注意,仅当 {% data variables.product.product_name %} 设备 [启用了 LDAP 同步](/enterprise/admin/authentication/using-ldap)时,LDAP 终结点通常才有效。 即使已禁用 LDAP 同步,也可以在启用 LDAP 后使用[为用户更新 LDAP 映射](#update-ldap-mapping-for-a-user)终结点。 + +With the LDAP mapping endpoints, you're able to update the Distinguished Name (DN) that a user or team maps to. Note that the LDAP endpoints are generally only effective if your {% data variables.product.product_name %} appliance has [LDAP Sync enabled](/enterprise/admin/authentication/using-ldap). The [Update LDAP mapping for a user](#update-ldap-mapping-for-a-user) endpoint can be used when LDAP is enabled, even if LDAP Sync is disabled. + +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} diff --git a/translations/zh-CN/content/rest/enterprise-admin/license.md b/translations/zh-CN/content/rest/enterprise-admin/license.md index 82dd5a59cf..6af199deca 100644 --- a/translations/zh-CN/content/rest/enterprise-admin/license.md +++ b/translations/zh-CN/content/rest/enterprise-admin/license.md @@ -1,6 +1,6 @@ --- -title: 许可证 -intro: 许可 API 提供有关企业许可的信息。 +title: License +intro: The License API provides information on your Enterprise license. versions: ghes: '*' ghae: '*' @@ -8,11 +8,8 @@ versions: topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 5d47f972922a44292ffe4b32e4f90aae250e0948 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147572646' --- -它仅适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)网站管理员。 如果普通用户尝试访问它,他们将收到 `404` 响应。 + +*It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. + +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} diff --git a/translations/zh-CN/content/rest/enterprise-admin/management-console.md b/translations/zh-CN/content/rest/enterprise-admin/management-console.md index db362a06d0..8bf82468bd 100644 --- a/translations/zh-CN/content/rest/enterprise-admin/management-console.md +++ b/translations/zh-CN/content/rest/enterprise-admin/management-console.md @@ -1,40 +1,37 @@ --- -title: 管理控制台 -intro: '管理控制台 API 可帮助您管理 {% data variables.product.product_name %} 安装设施。' +title: Management Console +intro: 'The Management Console API helps you manage your {% data variables.product.product_name %} installation.' versions: ghes: '*' topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: da38513a04525b858e041188eec6f691db9be1d9 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147065536' --- + {% tip %} -在对管理控制台进行 API 调用时,必须明确设置端口号。 如果企业启用了 TLS,则端口号为 `8443`;否则,端口号为 `8080`。 +You must explicitly set the port number when making API calls to the Management Console. If TLS is enabled on your enterprise, the port number is `8443`; otherwise, the port number is `8080`. -如果您不想提供端口号,则需要将工具配置为自动遵循重定向。 +If you don't want to provide a port number, you'll need to configure your tool to automatically follow redirects. -使用 `curl` 时可能还需要添加 [`-k` 标志](http://curl.haxx.se/docs/manpage.html#-k),因为在[添加自己的 TLS 证书](/enterprise/admin/guides/installation/configuring-tls/)之前,{% data variables.product.product_name %} 使用自签名证书。 +You may also need to add the [`-k` flag](http://curl.haxx.se/docs/manpage.html#-k) when using `curl`, since {% data variables.product.product_name %} uses a self-signed certificate before you [add your own TLS certificate](/enterprise/admin/guides/installation/configuring-tls/). {% endtip %} -### 身份验证 +### Authentication -需要将[管理控制台密码](/enterprise/admin/articles/accessing-the-management-console/)作为身份验证令牌传递给除 [`/setup/api/start`](#create-a-github-enterprise-server-license) 之外的每个管理控制台 API 终结点。 +You need to pass your [Management Console password](/enterprise/admin/articles/accessing-the-management-console/) as an authentication token to every Management Console API endpoint except [`/setup/api/start`](#create-a-github-enterprise-server-license). -使用 `api_key` 参数在每个请求中发送此令牌。 例如: +Use the `api_key` parameter to send this token with each request. For example: ```shell -$ curl -L 'https://hostname:admin_port/setup/api?api_key=your-amazing-password' +$ curl -L 'https://HOSTNAME:ADMIN-PORT/setup/api?api_key=YOUR_PASSWORD' ``` -还可以使用标准 HTTP 身份验证发送此令牌。 例如: +You can also use standard HTTP authentication to send this token. For example: ```shell -$ curl -L -u "api_key:your-amazing-password" 'https://hostname:admin_port/setup/api' +$ curl -L -u "api_key:YOUR_PASSWORD" 'https://HOSTNAME:ADMIN-PORT/setup/api' ``` + +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} diff --git a/translations/zh-CN/content/rest/enterprise-admin/org-pre-receive-hooks.md b/translations/zh-CN/content/rest/enterprise-admin/org-pre-receive-hooks.md index 5ed0e29c8b..44a2256f6e 100644 --- a/translations/zh-CN/content/rest/enterprise-admin/org-pre-receive-hooks.md +++ b/translations/zh-CN/content/rest/enterprise-admin/org-pre-receive-hooks.md @@ -1,28 +1,25 @@ --- -title: 组织预接收挂钩 -intro: 组织预接收挂钩 API 允许你查看和修改组织可用的预接收挂钩的实施。 +title: Organization Pre-receive Hooks +intro: The Organization Pre-receive Hooks API allows you to view and modify enforcement of the pre-receive hooks that are available to an organization. versions: ghes: '*' topics: - API miniTocMaxHeadingLevel: 3 allowTitleToDifferFromFilename: true -ms.openlocfilehash: 802ed40ac8e42c1f0a9ef3b6bab4a150dd68603c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147063960' --- -### 对象属性 -| 名称 | 类型 | 说明 | +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} + +### Object attributes + +| Name | Type | Description | |----------------------------------|-----------|-----------------------------------------------------------| -| `name` | `string` | 挂钩的名称。 | -| `enforcement` | `string` | 此仓库中挂钩的实施状态。 | -| `allow_downstream_configuration` | `boolean` | 仓库是否可以覆盖实施。 | -| `configuration_url` | `string` | 设置实施的端点 URL。 | +| `name` | `string` | The name of the hook. | +| `enforcement` | `string` | The state of enforcement for the hook on this repository. | +| `allow_downstream_configuration` | `boolean` | Whether repositories can override enforcement. | +| `configuration_url` | `string` | URL for the endpoint where enforcement is set. | -强制执行的可能值为 `enabled`、`disabled` 和 `testing`。 `disabled` 表示预接收挂钩不会运行。 `enabled` 表示它将运行并拒绝任何导致非零状态的推送。 `testing` 表示脚本将运行但不会导致任何推送被拒绝。 +Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected. -`configuration_url` 可能是指向此终结点或此挂钩的全局配置的链接。 只有站点管理员才能访问全局配置。 +`configuration_url` may be a link to this endpoint or this hook's global configuration. Only site admins are able to access the global configuration. diff --git a/translations/zh-CN/content/rest/enterprise-admin/orgs.md b/translations/zh-CN/content/rest/enterprise-admin/orgs.md index d74918c0a9..4f5bfb8d52 100644 --- a/translations/zh-CN/content/rest/enterprise-admin/orgs.md +++ b/translations/zh-CN/content/rest/enterprise-admin/orgs.md @@ -1,6 +1,6 @@ --- -title: 组织 -intro: 组织管理 API 允许您在企业上创建组织。 +title: Organizations +intro: The Organization Administration API allows you to create organizations on your enterprise. versions: ghes: '*' ghae: '*' @@ -8,11 +8,8 @@ topics: - API miniTocMaxHeadingLevel: 3 allowTitleToDifferFromFilename: true -ms.openlocfilehash: dde98174176217083a0c0960a069ed266e5fb413 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147061960' --- -它仅适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)网站管理员。 如果普通用户尝试访问它,他们将收到 `404` 响应。 + +*It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. + +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} diff --git a/translations/zh-CN/content/rest/enterprise-admin/pre-receive-environments.md b/translations/zh-CN/content/rest/enterprise-admin/pre-receive-environments.md index 0bf4f54a05..f03da691ea 100644 --- a/translations/zh-CN/content/rest/enterprise-admin/pre-receive-environments.md +++ b/translations/zh-CN/content/rest/enterprise-admin/pre-receive-environments.md @@ -1,39 +1,36 @@ --- -title: 预接收环境 -intro: 预接收环境 API 允许您创建、列出、更新和删除预接收挂钩的环境。 +title: Pre-receive Environments +intro: 'The Pre-receive Environments API allows you to create, list, update and delete environments for pre-receive hooks.' versions: ghes: '*' ghae: '*' topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 9db8635691ae2f8fcb8649b648948763168081ac -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147883260' --- -它仅适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)网站管理员。 如果普通用户尝试访问它,他们将收到 `404` 响应。 -### 对象属性 +*It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. -#### 预接收环境 +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} -| 名称 | 类型 | 说明 | +### Object attributes + +#### Pre-receive Environment + +| Name | Type | Description | |-----------------------|-----------|----------------------------------------------------------------------------| -| `name` | `string` | UI 中显示的环境名称。 | -| `image_url` | `string` | 将要下载并解压缩的 tarball 的 URL。 | -| `default_environment` | `boolean` | 这是否是 {% data variables.product.product_name %} 附带的默认环境。 | -| `download` | `object` | 此环境的下载状态。 | -| `hooks_count` | `integer` | 使用此环境的预接收挂钩数量。 | +| `name` | `string` | The name of the environment as displayed in the UI. | +| `image_url` | `string` | URL to the tarball that will be downloaded and extracted. | +| `default_environment` | `boolean` | Whether this is the default environment that ships with {% data variables.product.product_name %}. | +| `download` | `object` | This environment's download status. | +| `hooks_count` | `integer` | The number of pre-receive hooks that use this environment. | -#### 预接收环境下载 +#### Pre-receive Environment Download -| 名称 | 类型 | 说明 | +| Name | Type | Description | |-----------------|----------|---------------------------------------------------------| -| `state` | `string` | 最近下载的状态。 | -| `downloaded_at` | `string` | 最近下载开始的时间。 | -| `message` | `string` | 在失败时生成任何错误消息。 | +| `state` | `string` | The state of the most recent download. | +| `downloaded_at` | `string` | The time when the most recent download started. | +| `message` | `string` | On failure, this will have any error messages produced. | -`state` 的可能值为 `not_started`、`in_progress`、`success`、`failed`。 +Possible values for `state` are `not_started`, `in_progress`, `success`, `failed`. diff --git a/translations/zh-CN/content/rest/enterprise-admin/pre-receive-hooks.md b/translations/zh-CN/content/rest/enterprise-admin/pre-receive-hooks.md index 6304bd2467..e9fdf6e4a8 100644 --- a/translations/zh-CN/content/rest/enterprise-admin/pre-receive-hooks.md +++ b/translations/zh-CN/content/rest/enterprise-admin/pre-receive-hooks.md @@ -1,31 +1,29 @@ --- -title: 预接收挂钩 -intro: 预接收挂钩 API 允许您创建、列出、更新和删除预接收挂钩。 +title: Pre-receive Hooks +intro: 'The Pre-receive Hooks API allows you to create, list, update and delete pre-receive hooks.' versions: ghes: '*' topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: dd776e7ec95a970f025d4de1ec03f07b2a7b29f7 -ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '147066152' --- -它仅适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)网站管理员。 如果普通用户尝试访问它,他们将收到 `404` 响应。 -### 对象属性 +*It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. -#### 预接收挂钩 +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} -| 名称 | 类型 | 说明 | +### Object attributes + +#### Pre-receive Hook + +| Name | Type | Description | |----------------------------------|-----------|-----------------------------------------------------------------| -| `name` | `string` | 挂钩的名称。 | -| `script` | `string` | 挂钩运行的脚本。 | -| `script_repository` | `object` | 保存脚本的 GitHub 仓库。 | -| `environment` | `object` | 执行脚本的预接收环境。 | -| `enforcement` | `string` | 此挂钩的实施状态。 | -| `allow_downstream_configuration` | `boolean` | 是否可以在组织或仓库级别上覆盖实施。 | +| `name` | `string` | The name of the hook. | +| `script` | `string` | The script that the hook runs. | +| `script_repository` | `object` | The GitHub repository where the script is kept. | +| `environment` | `object` | The pre-receive environment where the script is executed. | +| `enforcement` | `string` | The state of enforcement for this hook. | +| `allow_downstream_configuration` | `boolean` | Whether enforcement can be overridden at the org or repo level. | -强制执行的可能值为 `enabled`、`disabled` 和 `testing`。 `disabled` 表示预接收挂钩不会运行。 `enabled` 表示它将运行并拒绝任何导致非零状态的推送。 `testing` 表示脚本将运行但不会导致任何推送被拒绝。 +Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject +any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected. diff --git a/translations/zh-CN/content/rest/enterprise-admin/repo-pre-receive-hooks.md b/translations/zh-CN/content/rest/enterprise-admin/repo-pre-receive-hooks.md index 8b82b4caae..cd2153eedf 100644 --- a/translations/zh-CN/content/rest/enterprise-admin/repo-pre-receive-hooks.md +++ b/translations/zh-CN/content/rest/enterprise-admin/repo-pre-receive-hooks.md @@ -1,27 +1,24 @@ --- -title: 存储库预接收挂钩 -intro: 存储库预接收挂钩 API 允许你查看和修改存储库可用的预接收挂钩的强制执行。 +title: Repository Pre-receive Hooks +intro: The Repository Pre-receive Hooks API allows you to view and modify enforcement of the pre-receive hooks that are available to a repository. versions: ghes: '*' topics: - API miniTocMaxHeadingLevel: 3 allowTitleToDifferFromFilename: true -ms.openlocfilehash: 63ba6f4f7d67b43dd39609a6520a0938365cfc12 -ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/12/2022 -ms.locfileid: '147888466' --- -### 对象属性 -| 名称 | 类型 | 说明 | +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} + +### Object attributes + +| Name | Type | Description | |---------------------|----------|-----------------------------------------------------------| -| `name` | `string` | 挂钩的名称。 | -| `enforcement` | `string` | 此仓库中挂钩的实施状态。 | -| `configuration_url` | `string` | 设置实施的端点 URL。 | +| `name` | `string` | The name of the hook. | +| `enforcement` | `string` | The state of enforcement for the hook on this repository. | +| `configuration_url` | `string` | URL for the endpoint where enforcement is set. | -强制执行的可能值为 `enabled`、`disabled` 和 `testing`。 `disabled` 表示预接收挂钩不会运行。 `enabled` 表示它将运行并拒绝任何导致非零状态的推送。 `testing` 表示脚本将运行但不会导致任何推送被拒绝。 +Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected. -`configuration_url` 可能是此存储库、其组织所有者或全局配置的链接。 `configuration_url` 终结点的访问授权在所有者或站点管理员级别确定。 +`configuration_url` may be a link to this repository, it's organization owner or global configuration. Authorization to access the endpoint at `configuration_url` is determined at the owner or site admin level. diff --git a/translations/zh-CN/content/rest/enterprise-admin/scim.md b/translations/zh-CN/content/rest/enterprise-admin/scim.md index a95eb461b5..ae7b44b582 100644 --- a/translations/zh-CN/content/rest/enterprise-admin/scim.md +++ b/translations/zh-CN/content/rest/enterprise-admin/scim.md @@ -14,6 +14,7 @@ miniTocMaxHeadingLevel: 3 {% endnote %} +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} ## About the SCIM API {% data variables.product.product_name %} provides a SCIM API for use by SCIM-enabled Identity Providers (IdPs). An integration on the IdP can use the API to automatically provision, manage, or deprovision user accounts on a {% data variables.product.product_name %} instance that uses SAML single sign-on (SSO) for authentication. For more information about SAML SSO, see "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)." @@ -38,11 +39,11 @@ GET /scim/v2/Users/{scim_user_id} The SCIM integration on the IdP performs actions on behalf of an enterprise owner for the {% data variables.product.product_name %} instance. For more information, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owners)." -To authenticate requests to the API, the person who configures SCIM on the IdP must use a personal access token (classic) with `admin:enterprise` scope, which the IdP must provide in the request's `Authorization` header. For more information about personal access tokens (classic), see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)". +To authenticate requests to the API, the person who configures SCIM on the IdP must use a {% data variables.product.pat_v1 %} with `admin:enterprise` scope, which the IdP must provide in the request's `Authorization` header. For more information about {% data variables.product.pat_v1_plural %}, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)". {% note %} -**Note:** Enterprise owners must generate and use a personal access token (classic) for authentication of requests to the SCIM API. {% ifversion ghes > 3.8 %}Fine-grained personal access tokens and {% endif %}GitHub app callers are not supported at this time. +**Note:** Enterprise owners must generate and use a {% data variables.product.pat_v1 %} for authentication of requests to the SCIM API. {% ifversion ghes > 3.8 %}{% data variables.product.pat_v2_caps %} and {% endif %}GitHub app callers are not supported at this time. {% endnote %} diff --git a/translations/zh-CN/content/rest/enterprise-admin/users.md b/translations/zh-CN/content/rest/enterprise-admin/users.md index f5a68de063..b5548dd5c7 100644 --- a/translations/zh-CN/content/rest/enterprise-admin/users.md +++ b/translations/zh-CN/content/rest/enterprise-admin/users.md @@ -1,17 +1,14 @@ --- -title: 用户 -intro: '用户管理 API 允许您暂停{% ifversion ghes %}、取消暂停、升级和降级{% endif %}{% ifversion ghae %} 以及取消暂停{% endif %} 企业上的用户。' +title: Users +intro: 'The User Administration API allows you to suspend{% ifversion ghes %}, unsuspend, promote, and demote{% endif %}{% ifversion ghae %} and unsuspend{% endif %} users on your enterprise.' versions: ghes: '*' ghae: '*' topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: a483065af09a2baef774cb8ce256350945106faa -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147063168' --- -它仅适用于[经过身份验证的](/rest/overview/resources-in-the-rest-api#authentication)网站管理员。 如果普通用户尝试访问它,他们将收到 `403` 响应。 + +*It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `403` response if they try to access it. + +{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %} diff --git a/translations/zh-CN/content/rest/gitignore.md b/translations/zh-CN/content/rest/gitignore.md index 852802bdb4..374cb4bb75 100644 --- a/translations/zh-CN/content/rest/gitignore.md +++ b/translations/zh-CN/content/rest/gitignore.md @@ -1,6 +1,6 @@ --- title: Gitignore -intro: Gitignore API 提取可用于忽略文件和目录的 `.gitignore` 模板。 +intro: The Gitignore API fetches `.gitignore` templates that can be used to ignore files and directories. versions: fpt: '*' ghes: '*' @@ -11,21 +11,16 @@ topics: miniTocMaxHeadingLevel: 3 redirect_from: - /rest/reference/gitignore -ms.openlocfilehash: 082b626aac4af8dcdf435761447caeb015a608db -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147092884' --- -## 关于 Gitignore API -通过 API 在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上创建新存储库时,可以指定一个 [.gitignore 模板](/github/getting-started-with-github/ignoring-files)在创建后应用于存储库。 .gitignore 模板 API 可列出模板,并从 {% data variables.product.product_name %} [.gitignore 存储库](https://github.com/github/gitignore)中获取模板。 +## About the Gitignore API -### gitignore 的自定义媒体类型 +When you create a new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} via the API, you can specify a [.gitignore template](/github/getting-started-with-github/ignoring-files) to apply to the repository upon creation. The .gitignore templates API lists and fetches templates from the {% data variables.product.product_name %} [.gitignore repository](https://github.com/github/gitignore). -获取 gitignore 模板时,您可以使用以下自定义媒体类型。 +### Custom media types for gitignore + +You can use this custom media type when getting a gitignore template. application/vnd.github.VERSION.raw -有关详细信息,请参阅“[媒体类型](/rest/overview/media-types)”。 +For more information, see "[Media types](/rest/overview/media-types)." diff --git a/translations/zh-CN/content/rest/guides/building-a-ci-server.md b/translations/zh-CN/content/rest/guides/building-a-ci-server.md index 81b1b552bd..afe94b461f 100644 --- a/translations/zh-CN/content/rest/guides/building-a-ci-server.md +++ b/translations/zh-CN/content/rest/guides/building-a-ci-server.md @@ -1,6 +1,6 @@ --- -title: 构建 CI 服务器 -intro: 使用状态 API 构建您自己的 CI 系统。 +title: Building a CI server +intro: Build your own CI system using the Status API. redirect_from: - /guides/building-a-ci-server - /v3/guides/building-a-ci-server @@ -11,31 +11,35 @@ versions: ghec: '*' topics: - API -ms.openlocfilehash: 5c2fcd462e9c07fb9c359525ece7896e10dd9649 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145129064' --- -[状态 API][status API] 负责将提交与测试服务绑定在一起,使你进行的每次推送都可以得到测试并体现在 {% data variables.product.product_name %} 拉取请求中。 -本指南将使用该 API 来演示您可以使用的设置。 -在我们的场景中,我们将: -* 在拉取请求被打开时运行我们的 CI 套件(我们将 CI 状态设置为待处理)。 -* 在 CI 完成后,我们将相应地设置拉取请求的状态。 -我们的 CI 系统和主机服务器将是我们想象中的虚拟物。 它们可能是 Travis、Jenkins 或其他完全不同的工具。 本指南的重点是设置和配置负责管理通信的服务器。 +The [Status API][status API] is responsible for tying together commits with +a testing service, so that every push you make can be tested and represented +in a {% data variables.product.product_name %} pull request. -如果尚未下载,请务必[下载 ngrok][ngrok],并了解如何[使用它][using ngrok]。 我们发现它在暴露本地连接方面是一款非常有用的工具。 +This guide will use that API to demonstrate a setup that you can use. +In our scenario, we will: -注意:可以在 [platform-samples][platform samples] 存储库中下载此项目的完整源代码。 +* Run our CI suite when a Pull Request is opened (we'll set the CI status to pending). +* When the CI is finished, we'll set the Pull Request's status accordingly. -## 编写服务器 +Our CI system and host server will be figments of our imagination. They could be +Travis, Jenkins, or something else entirely. The crux of this guide will be setting up +and configuring the server managing the communication. -我们将编写一个快速的 Sinatra 应用程序,以证明我们的本地连接工作正常。 -首先编写以下代码: +If you haven't already, be sure to [download ngrok][ngrok], and learn how +to [use it][using ngrok]. We find it to be a very useful tool for exposing local +connections. + +Note: you can download the complete source code for this project +[from the platform-samples repo][platform samples]. + +## Writing your server + +We'll write a quick Sinatra app to prove that our local connections are working. +Let's start with this: ``` ruby require 'sinatra' @@ -47,24 +51,29 @@ post '/event_handler' do end ``` -(如果你不熟悉 Sinatra 的工作原理,建议你阅读 [Sinatra 指南][Sinatra]。) +(If you're unfamiliar with how Sinatra works, we recommend [reading the Sinatra guide][Sinatra].) -启动此服务器。 默认情况下,Sinatra 在端口 `4567` 上启动,因此你还需要配置 ngrok 开始监听。 +Start this server up. By default, Sinatra starts on port `4567`, so you'll want +to configure ngrok to start listening for that, too. -为了使此服务器正常工作,我们需要使用 web 挂钩来设置一个仓库。 -Web 挂钩应配置为在创建或合并拉取请求时触发。 -继续创建一个您可以自由支配的仓库。 我们可以推荐 [@octocat 的 Spoon/Knife 存储库](https://github.com/octocat/Spoon-Knife)吗? -之后,你将在自己的存储库中创建新的 web 挂钩,向其馈送 ngrok 给你的 URL,并选择 `application/x-www-form-urlencoded` 作为内容类型: +In order for this server to work, we'll need to set a repository up with a webhook. +The webhook should be configured to fire whenever a Pull Request is created, or merged. +Go ahead and create a repository you're comfortable playing around in. Might we +suggest [@octocat's Spoon/Knife repository](https://github.com/octocat/Spoon-Knife)? +After that, you'll create a new webhook in your repository, feeding it the URL +that ngrok gave you, and choosing `application/x-www-form-urlencoded` as the +content type: -![新的 ngrok URL](/assets/images/webhook_sample_url.png) +![A new ngrok URL](/assets/images/webhook_sample_url.png) -单击“更新 Webhook”。 应该会看到响应 `Well, it worked!`。 -很好! 单击“让我选择单个事件”,然后选择以下项: +Click **Update webhook**. You should see a body response of `Well, it worked!`. +Great! Click on **Let me select individual events**, and select the following: -* 状态 -* 拉取请求 +* Status +* Pull Request -在发生相关操作时,{% data variables.product.product_name %} 会将这些事件发送到我们的服务器。 现在将服务器更新为直接立即处理拉取请求场景: +These are the events {% data variables.product.product_name %} will send to our server whenever the relevant action +occurs. Let's update our server to *just* handle the Pull Request scenario right now: ``` ruby post '/event_handler' do @@ -85,16 +94,26 @@ helpers do end ``` -这是怎么回事? {% data variables.product.product_name %} 发送的每个事件都附有 `X-GitHub-Event` HTTP 标头。 我们现在只关注拉取请求事件。 我们将从其中获取信息的有效负载,并返回标题字段。 在理想情况下,我们的服务器会关注每次更新拉取请求时的情况(而不仅仅是打开时的情况)。 这将确保每个新推送都通过 CI 测试。 -但就此演示而言,我们只需关注它被打开时的情况。 +What's going on? Every event that {% data variables.product.product_name %} sends out attached a `X-GitHub-Event` +HTTP header. We'll only care about the PR events for now. From there, we'll +take the payload of information, and return the title field. In an ideal scenario, +our server would be concerned with every time a pull request is updated, not just +when it's opened. That would make sure that every new push passes the CI tests. +But for this demo, we'll just worry about when it's opened. -要测试此概念验证,请在测试存储库的分支中进行一些更改,然后打开拉取请求。 您的服务器应该会做出相应的响应! +To test out this proof-of-concept, make some changes in a branch in your test +repository, and open a pull request. Your server should respond accordingly! -## 处理状态 +## Working with statuses -服务器就位后,我们就可以开始实现第一个要求,即设置(和更新)CI 状态。 请注意,无论何时更新服务器,都可以单击“重新交付”,发送相同的有效负载。 不需要每次进行更改时都发出新的拉取请求! +With our server in place, we're ready to start our first requirement, which is +setting (and updating) CI statuses. Note that at any time you update your server, +you can click **Redeliver** to send the same payload. There's no need to make a +new pull request every time you make a change! -由于我们在与 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 进行交互,因此我们将使用 [Octokit.rb][octokit.rb] 来管理我们的交互。 我们将使用[个人访问令牌][access token]配置该客户端: +Since we're interacting with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll use [Octokit.rb][octokit.rb] +to manage our interactions. We'll configure that client with +[a {% data variables.product.pat_generic %}][access token]: ``` ruby # !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! @@ -106,7 +125,8 @@ before do end ``` -之后,我们只需要在 {% data variables.product.product_name %} 上更新拉取请求以明确表示我们正在处理 CI: +After that, we'll just need to update the pull request on {% data variables.product.product_name %} to make clear +that we're processing on the CI: ``` ruby def process_pull_request(pull_request) @@ -115,13 +135,16 @@ def process_pull_request(pull_request) end ``` -我们在这里做三件非常基本的事情: +We're doing three very basic things here: -* 查找仓库的全名 -* 查找拉取请求的最后一个 SHA -* 将状态设置为“待处理” +* we're looking up the full name of the repository +* we're looking up the last SHA of the pull request +* we're setting the status to "pending" -就这么简单! 从这里,你可以运行任何需要的进程来执行测试套件。 也许你会将代码传递给 Jenkins,或者通过其 API 调用另一个 Web 服务,例如 [Travis][travis api]。 之后,请务必再次更新状态。 在本示例中,我们只需将其设置为 `"success"`: +That's it! From here, you can run whatever process you need to in order to execute +your test suite. Maybe you're going to pass off your code to Jenkins, or call +on another web service via its API, like [Travis][travis api]. After that, you'd +be sure to update the status once more. In our example, we'll just set it to `"success"`: ``` ruby def process_pull_request(pull_request) @@ -132,18 +155,19 @@ def process_pull_request(pull_request) end ``` -## 结束语 +## Conclusion -在 GitHub,我们多年来一直使用一个 [Janky][janky] 版本来管理 CI。 -基本流程本质上与我们上面构建的服务器完全相同。 -在 GitHub,我们: +At GitHub, we've used a version of [Janky][janky] to manage our CI for years. +The basic flow is essentially the exact same as the server we've built above. +At GitHub, we: -* 在创建或更新(通过 Janky)时触发 Jenkins -* 等待关于 CI 状态的响应 -* 如果代码为绿色,我们将合并拉取请求 +* Fire to Jenkins when a pull request is created or updated (via Janky) +* Wait for a response on the state of the CI +* If the code is green, we merge the pull request -所有这些通信都会流回我们的聊天室。 使用此示例并不需要构建自己的 CI 设置。 -始终可以依赖 [GitHub 集成][integrations]。 +All of this communication is funneled back to our chat rooms. You don't need to +build your own CI setup to use this example. +You can always rely on [GitHub integrations][integrations]. [deploy API]: /rest/reference/repos#deployments [status API]: /rest/reference/commits#commit-statuses diff --git a/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md b/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md index 1380647a41..ed666cdb27 100644 --- a/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md @@ -54,7 +54,7 @@ gh api /octocat --method GET To make a request using JavaScript, you can use Octokit.js. For more information, see [the Octokit.js README](https://github.com/octokit/octokit.js/#readme). -First, create an instance of `Octokit`.{% ifversion ghes or ghae %} Set the base URL to `{% data variables.product.api_url_code %}`. Replace `[hostname]` with the name of {% data variables.product.product_location %}.{% endif %} +First, create an instance of `Octokit`.{% ifversion ghes or ghae %} Set the base URL to `{% data variables.product.api_url_code %}`. Replace `[hostname]` with the name of {% data variables.location.product_location %}.{% endif %} ```javascript const octokit = new Octokit({ {% ifversion ghes or ghae %} @@ -72,7 +72,7 @@ await octokit.request("GET /octocat", {}); {% curl %} -Prepend the base URL for the {% data variables.product.prodname_dotcom %} REST API, `{% data variables.product.api_url_code %}`, to the path to get the full URL: `{% data variables.product.api_url_code %}/octocat`.{% ifversion ghes or ghae %} Replace `[hostname]` with the name of {% data variables.product.product_location %}.{% endif %} +Prepend the base URL for the {% data variables.product.prodname_dotcom %} REST API, `{% data variables.product.api_url_code %}`, to the path to get the full URL: `{% data variables.product.api_url_code %}/octocat`.{% ifversion ghes or ghae %} Replace `[hostname]` with the name of {% data variables.location.product_location %}.{% endif %} Use the `curl` command in your command line. Use the `--request` or `-X` flag followed by the HTTP method. Use the `--url` flag followed by the full URL. @@ -99,7 +99,7 @@ Many operations require authentication or return additional information if you a You can authenticate your request by adding a token. -If you want to use the {% data variables.product.company_short %} REST API for personal use, you can create a personal access token (PAT). The REST API operations used in this article require `repo` scope for personal access tokens. Other operations may require different scopes. For more information about creating a personal access token, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." +If you want to use the {% data variables.product.company_short %} REST API for personal use, you can create a {% data variables.product.pat_generic %}. The REST API operations used in this article require `repo` scope for {% data variables.product.pat_v1_plural %}{% ifversion pat-v2 %} or, unless otherwise noted, read-only access to public repositories for {% data variables.product.pat_v2 %}s{% endif %}. Other operations may require different scopes{% ifversion pat-v2%} or permissions{% endif %}. For more information about creating a {% data variables.product.pat_generic %}, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." If you want to use the API on behalf of an organization or another user, {% data variables.product.company_short %} recommends that you use a {% data variables.product.prodname_github_app %}. If an operation is available to {% data variables.product.prodname_github_apps %}, the REST reference documentation for that operation will say "Works with GitHub Apps." The REST API operations used in this article require `issues` read and write permissions for {% data variables.product.prodname_github_apps %}. Other operations may require different permissions. For more information, see "[Creating a GitHub App](/developers/apps/building-github-apps/creating-a-github-app)", "[Authenticating with GitHub Apps](/developers/apps/building-github-apps/authenticating-with-github-apps), and "[Identifying and authorizing users for GitHub Apps](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps)." @@ -133,7 +133,7 @@ If these options are not possible, consider using another service such as [the 1 {% endwarning %} -To authenticate with the Octokit.js library, you can pass your token when you create an instance of `Octokit`. Replace `YOUR-TOKEN` with your token.{% ifversion ghes or ghae %} Replace `[hostname]` with the name of {% data variables.product.product_location %}.{% endif %} +To authenticate with the Octokit.js library, you can pass your token when you create an instance of `Octokit`. Replace `YOUR-TOKEN` with your token.{% ifversion ghes or ghae %} Replace `[hostname]` with the name of {% data variables.location.product_location %}.{% endif %} ```javascript const octokit = new Octokit({ {% ifversion ghes or ghae %} @@ -340,7 +340,7 @@ Path parameters modify the operation path. For example, the "List repository iss {% ifversion ghes or ghae %} {% note %} -**Note:** In order for this command to work for {% data variables.product.product_location %}, replace `octocat/Spoon-Knife` with a repository owned by {% data variables.product.product_location %}. Otherwise, rerun the `gh auth login` command to authenticate to {% data variables.product.prodname_dotcom_the_website %} instead of {% data variables.product.product_location %}. +**Note:** In order for this command to work for {% data variables.location.product_location %}, replace `octocat/Spoon-Knife` with a repository owned by {% data variables.location.product_location %}. Otherwise, rerun the `gh auth login` command to authenticate to {% data variables.product.prodname_dotcom_the_website %} instead of {% data variables.location.product_location %}. {% endnote %} {% endif %} @@ -358,7 +358,7 @@ gh api --header 'Accept: application/vnd.github+json' --method GET /repos/octoca {% ifversion ghes or ghae %} {% note %} -**Note:** In order for this example to work for {% data variables.product.product_location %}, replace `octocat/Spoon-Knife` with a repository owned by {% data variables.product.product_location %}. Otherwise, create a new `Octokit` instance and do not specify `baseURL`. +**Note:** In order for this example to work for {% data variables.location.product_location %}, replace `octocat/Spoon-Knife` with a repository owned by {% data variables.location.product_location %}. Otherwise, create a new `Octokit` instance and do not specify `baseURL`. {% endnote %} {% endif %} @@ -381,7 +381,7 @@ To get issues from the `octocat/Spoon-Knife` repository, replace `{owner}` with {% ifversion ghes or ghae %} {% note %} -**Note:** If you want to use {% data variables.product.product_location %} instead of {% data variables.product.prodname_dotcom_the_website %}, use `{% data variables.product.api_url_code %}` instead of `https://api.github.com` and replace `[hostname]` with the name of {% data variables.product.product_location %}. Replace `octocat/Spoon-Knife` with a repository owned by {% data variables.product.product_location %}. +**Note:** If you want to use {% data variables.location.product_location %} instead of {% data variables.product.prodname_dotcom_the_website %}, use `{% data variables.product.api_url_code %}` instead of `https://api.github.com` and replace `[hostname]` with the name of {% data variables.location.product_location %}. Replace `octocat/Spoon-Knife` with a repository owned by {% data variables.location.product_location %}. {% endnote %} {% endif %} @@ -474,6 +474,16 @@ gh api --header 'Accept: application/vnd.github+json' --method POST /repos/octoc {% javascript %} +{% ifversion pat-v2 %} + +{% note %} + +If you are using a {% data variables.product.pat_v2 %}, you must replace `octocat/Spoon-Knife` with a repository that you own or that is owned by an organization that you are a member of. Your token must have access to that repository and have read and write permissions for repository issues. For more information about creating a repository, see "[Create a repo](/get-started/quickstart/create-a-repo)." For more information about granting access and permissions to a {% data variables.product.pat_v2 %}, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." + +{% endnote %} + +{% endif %} + When you make a request with Octokit.js, all parameters, including body parameters, are passed in an object as the second argument to the `request` method. ```javascript @@ -489,6 +499,16 @@ await octokit.request("POST /repos/{owner}/{repo}/issues", { {% curl %} +{% ifversion pat-v2 %} + +{% note %} + +If you are using a {% data variables.product.pat_v2 %}, you must replace `octocat/Spoon-Knife` with a repository that you own or that is owned by an organization that you are a member of. Your token must have access to that repository and have read and write permissions for repository issues. For more information about creating a repository, see "[Create a repo](/get-started/quickstart/create-a-repo)." For more information about granting access and permissions to a {% data variables.product.pat_v2 %}, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." + +{% endnote %} + +{% endif %} + For cURL, use the `--data` flag to pass the body parameters in a JSON object. ```shell diff --git a/translations/zh-CN/content/rest/guides/traversing-with-pagination.md b/translations/zh-CN/content/rest/guides/traversing-with-pagination.md index 02f3bbece5..ed7f9b1189 100644 --- a/translations/zh-CN/content/rest/guides/traversing-with-pagination.md +++ b/translations/zh-CN/content/rest/guides/traversing-with-pagination.md @@ -1,6 +1,6 @@ --- -title: 使用分页遍历 -intro: 通过一些使用搜索 API 的示例,探讨如何使用分页来管理响应。 +title: Traversing with pagination +intro: Explore how to use pagination to manage your responses with some examples using the Search API. redirect_from: - /guides/traversing-with-pagination - /v3/guides/traversing-with-pagination @@ -12,83 +12,104 @@ versions: topics: - API shortTitle: Traverse with pagination -ms.openlocfilehash: be0e961847e187b72848eda558636fe3ecb800bd -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145129043' --- -{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 为开发人员提供了丰富的信息供他们使用。 -大多数情况下,甚至可能会发现要求提供的信息太多,为了让服务器满意,API 会自动[对请求的项进行分页](/rest/overview/resources-in-the-rest-api#pagination)。 -在本指南中,我们将对搜索 API 进行一些调用,并使用分页对结果进行迭代。 可以在 [platform-samples][platform samples] 存储库中找到此项目的完整源代码。 +The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API provides a vast wealth of information for developers to consume. +Most of the time, you might even find that you're asking for _too much_ information, +and in order to keep our servers happy, the API will automatically [paginate the requested items](/rest/overview/resources-in-the-rest-api#pagination). + +In this guide, we'll make some calls to the Search API, and iterate over +the results using pagination. You can find the complete source code for this project +in the [platform-samples][platform samples] repository. {% data reusables.rest-api.dotcom-only-guide-note %} -## 分页基础知识 +## Basics of Pagination -首先需要了解有关接收分页条目的一些事实: +To start with, it's important to know a few facts about receiving paginated items: -1. 不同的 API 调用响应具有不同的默认值。 例如,对[列出公共存储库](/rest/reference/repos#list-public-repositories)的调用以 30 个为一组提供分页项,而对 GitHub 搜索 API 的调用以 100 个为一组提供项 -2. 您可以指定要接收的条目数(最多 100 个);但是, -3. 出于技术原因,并非每个端点的行为都相同。 例如,[事件](/rest/reference/activity#events)不允许设置接收项的最大值。 -请务必阅读关于如何处理特定端点分页结果的文档。 +1. Different API calls respond with different defaults. For example, a call to +[List public repositories](/rest/reference/repos#list-public-repositories) +provides paginated items in sets of 30, whereas a call to the GitHub Search API +provides items in sets of 100 +2. You can specify how many items to receive (up to a maximum of 100); but, +3. For technical reasons, not every endpoint behaves the same. For example, +[events](/rest/reference/activity#events) won't let you set a maximum for items to receive. +Be sure to read the documentation on how to handle paginated results for specific endpoints. -API 调用的[链接标头](https://datatracker.ietf.org/doc/html/rfc5988)中提供了有关分页的信息。 例如,我们向搜索 API 发出 curl 请求,以了解 Mozilla 项目使用短语 `addClass` 的次数: +Information about pagination is provided in [the Link header](https://datatracker.ietf.org/doc/html/rfc5988) +of an API call. For example, let's make a curl request to the search API, to find +out how many times Mozilla projects use the phrase `addClass`: ```shell $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla" ``` -`-I` 参数表示仅关注标头,而不关注实际内容。 在检查结果时,你会注意到链接标头中的一些信息如下所示: +The `-I` parameter indicates that we only care about the headers, not the actual +content. In examining the result, you'll notice some information in the Link header +that looks like this: Link: ; rel="next", ; rel="last" -我们来分解说明。 `rel="next"` 表示下一页是 `page=2`。 这是合理的,因为在默认情况下,所有分页查询都是从第 `1.` 页开始,`rel="last"` 提供了更多信息,指示结果的最后一页第 `34` 页。 -因此,还有 33 页关于 `addClass` 的信息可供使用。 -很好! +Let's break that down. `rel="next"` says that the next page is `page=2`. This makes +sense, since by default, all paginated queries start at page `1.` `rel="last"` +provides some more information, stating that the last page of results is on page `34`. +Thus, we have 33 more pages of information about `addClass` that we can consume. +Nice! -始终依赖提供给你的这些链接关系。 不要试图猜测或构建自己的 URL。 +**Always** rely on these link relations provided to you. Don't try to guess or construct your own URL. -### 浏览页面 +### Navigating through the pages -现在你知道要接收多少页面,可以开始浏览页面以使用结果了。 可通过传入 `page` 参数来执行此操作。 默认情况下,`page` 始终从 `1` 开始。 让我们跳到第 14 页,看看会发生什么: +Now that you know how many pages there are to receive, you can start navigating +through the pages to consume the results. You do this by passing in a `page` +parameter. By default, `page` always starts at `1`. Let's jump ahead to page 14 +and see what happens: ```shell $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&page=14" ``` -以下是再次出现的 Link 标头: +Here's the link header once more: Link: ; rel="next", ; rel="last", ; rel="first", ; rel="prev" -正如预期的那样,`rel="next"` 是第 15 页,而 `rel="last"` 仍是第 34 页。 但现在我们得到了更多信息:`rel="first"` 表示第一页的 URL,更重要的是,可通过 `rel="prev"` 知道上一页的页码。 使用此信息,可以构建一些 UI,让用户在 API 调用中的第一个、上一个、下一个或最后一个结果列表之间跳转。 +As expected, `rel="next"` is at 15, and `rel="last"` is still 34. But now we've +got some more information: `rel="first"` indicates the URL for the _first_ page, +and more importantly, `rel="prev"` lets you know the page number of the previous +page. Using this information, you could construct some UI that lets users jump +between the first, previous, next, or last list of results in an API call. -### 更改接收的条目数量 +### Changing the number of items received -通过传递 `per_page` 参数,可以指定希望每个页面返回的项数,最多 100 个项。 让我们尝试询问关于 `addClass` 的 50 个项: +By passing the `per_page` parameter, you can specify how many items you want +each page to return, up to 100 items. Let's try asking for 50 items about `addClass`: ```shell $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&per_page=50" ``` -请注意它对标头响应的影响: +Notice what it does to the header response: Link: ; rel="next", ; rel="last" -你可能已经猜到了,`rel="last"` 信息表示最后一页现在是第 20 页。 这是因为我们要求每页提供有关我们结果的更多信息。 +As you might have guessed, the `rel="last"` information says that the last page +is now 20. This is because we are asking for more information per page about +our results. -## 使用信息 +## Consuming the information -你不希望仅仅为了能够使用分页而进行低级别的 curl 调用,因此让我们编写一个小的 Ruby 脚本,该脚本可完成上面所描述的所有内容。 +You don't want to be making low-level curl calls just to be able to work with +pagination, so let's write a little Ruby script that does everything we've +just described above. -照常,首先需要 [GitHub 的 Octokit.rb][octokit.rb] Ruby 库,并传入[个人访问令牌][personal token]: +As always, first we'll require [GitHub's Octokit.rb][octokit.rb] Ruby library, and +pass in our [{% data variables.product.pat_generic %}][personal token]: ``` ruby require 'octokit' @@ -98,17 +119,26 @@ require 'octokit' client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN'] ``` -接下来,将使用 Octokit 的 `search_code` 方法执行搜索。 与使用 `curl` 不同的是,我们还可以立即检索结果的数量,所以我们输入以下代码: +Next, we'll execute the search, using Octokit's `search_code` method. Unlike +using `curl`, we can also immediately retrieve the number of results, so let's +do that: ``` ruby results = client.search_code('addClass user:mozilla') total_count = results.total_count ``` -现在,我们来获取最后一页的页码,类似于链接标头中的 `page=34>; rel="last"` 信息。 Octokit.rb 通过一个名为“[超媒体链接关系][hypermedia-relations]”的实现来支持分页信息。 -我们不会对这种关系展开详细讨论,只想提醒你,`results` 变量中的每个元素都有一个称为 `rels` 的哈希,它可以包含有关 `:next`、`:last`、`:first` 和 `:prev` 的信息,具体取决于所得到的结果。 这些关系还包含通过调用 `rels[:last].href` 所得 URL 的相关信息。 +Now, let's grab the number of the last page, similar to `page=34>; rel="last"` +information in the link header. Octokit.rb support pagination information through +an implementation called "[Hypermedia link relations][hypermedia-relations]." +We won't go into detail about what that is, but, suffice to say, each element +in the `results` variable has a hash called `rels`, which can contain information +about `:next`, `:last`, `:first`, and `:prev`, depending on which result you're +on. These relations also contain information about the resulting URL, by calling +`rels[:last].href`. -知道了这一点后,我们来获取最后一个结果的页码,并将所有这些信息呈现给用户: +Knowing this, let's grab the page number of the last result, and present all +this information to the user: ``` ruby last_response = client.last_response @@ -117,8 +147,13 @@ number_of_pages = last_response.rels[:last].href.match(/page=(\d+).*$/)[1] puts "There are #{total_count} results, on #{number_of_pages} pages!" ``` -最后,我们来遍历结果。 可使用循环 `for i in 1..number_of_pages.to_i` 来实现此目的,但是,让我们遵循 `rels[:next]` 标头以从每个页面检索信息。 为简单起见,我们只获取每个页面中第一个结果的文件路径。 为此,我们需要一个循环;在每个循环结束时,我们将根据 `rels[:next]` 信息来检索下一页的数据集。 -当没有 `rels[:next]` 信息可供使用(也就是说,我们位于 `rels[:last]`)时,循环将结束。 它应如下所示: +Finally, let's iterate through the results. You could do this with a loop `for i in 1..number_of_pages.to_i`, +but instead, let's follow the `rels[:next]` headers to retrieve information from +each page. For the sake of simplicity, let's just grab the file path of the first +result from each page. To do this, we'll need a loop; and at the end of every loop, +we'll retrieve the data set for the next page by following the `rels[:next]` information. +The loop will finish when there is no `rels[:next]` information to consume (in other +words, we are at `rels[:last]`). It might look something like this: ``` ruby puts last_response.data.items.first.path @@ -128,7 +163,9 @@ until last_response.rels[:next].nil? end ``` -使用 Octokit.rb 更改每页的条目数非常简单。 只需将 `per_page` 选项哈希传递给初始客户端构造。 之后,代码应保持不变: +Changing the number of items per page is extremely simple with Octokit.rb. Simply +pass a `per_page` options hash to the initial client construction. After that, +your code should remain intact: ``` ruby require 'octokit' @@ -155,15 +192,17 @@ until last_response.rels[:next].nil? end ``` -## 构造分页链接 +## Constructing Pagination Links -一般来说,使用分页时,你的目标不是要抓住所有可能的结果,而是要生成一组导航,如下所示: +Normally, with pagination, your goal isn't to concatenate all of the possible +results, but rather, to produce a set of navigation, like this: -![分页链接示例](/assets/images/pagination_sample.png) +![Sample of pagination links](/assets/images/pagination_sample.png) -让我们勾勒出一个可能需要做什么的微观版本。 +Let's sketch out a micro-version of what that might entail. -根据上面的代码,我们已经知道可以从第一次调用中的分页结果中获取 `number_of_pages`: +From the code above, we already know we can get the `number_of_pages` in the +paginated results from the first call: ``` ruby require 'octokit' @@ -182,7 +221,7 @@ puts last_response.rels[:last].href puts "There are #{total_count} results, on #{number_of_pages} pages!" ``` -我们可以从其中构造美观的数字框 ASCII 表示形式: +From there, we can construct a beautiful ASCII representation of the number boxes: ``` ruby numbers = "" for i in 1..number_of_pages.to_i @@ -191,7 +230,8 @@ end puts numbers ``` -我们通过构造一个随机数来模拟用户单击其中一个框: +Let's simulate a user clicking on one of these boxes, by constructing a random +number: ``` ruby random_page = Random.new @@ -200,13 +240,15 @@ random_page = random_page.rand(1..number_of_pages.to_i) puts "A User appeared, and clicked number #{random_page}!" ``` -现在我们有了页码,可通过传递 `:page` 选项,使用 Octokit 显式地检索各个页面: +Now that we have a page number, we can use Octokit to explicitly retrieve that +individual page, by passing the `:page` option: ``` ruby clicked_results = client.search_code('addClass user:mozilla', :page => random_page) ``` -如果想变得复杂一点,还可以抓取前一页和后一页,以便为后退 (`<<`) 和前进 (`>>`) 元素生成链接: +If we wanted to get fancy, we could also grab the previous and next pages, in +order to generate links for back (`<<`) and forward (`>>`) elements: ``` ruby prev_page_href = client.last_response.rels[:prev] ? client.last_response.rels[:prev].href : "(none)" diff --git a/translations/zh-CN/content/rest/guides/working-with-comments.md b/translations/zh-CN/content/rest/guides/working-with-comments.md index 902b7d95c3..201ac1ffe3 100644 --- a/translations/zh-CN/content/rest/guides/working-with-comments.md +++ b/translations/zh-CN/content/rest/guides/working-with-comments.md @@ -1,6 +1,6 @@ --- -title: 处理注释 -intro: 使用 REST API,您可以访问和管理拉取请求、议题或提交中的注释。 +title: Working with comments +intro: 'Using the REST API, you can access and manage comments in your pull requests, issues, or commits.' redirect_from: - /guides/working-with-comments - /v3/guides/working-with-comments @@ -11,26 +11,31 @@ versions: ghec: '*' topics: - API -ms.openlocfilehash: 9b3b768d66199fda62bc5e644da9539d5425215e -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145129040' --- -对于任何拉取请求,{% data variables.product.product_name %} 提供三种类型的注释视图:针对整个拉取请求的[拉取请求注释][PR comment]、针对拉取请求内的[特定行的注释][PR line comment],以及针对拉取请求内的[特定提交的注释][commit comment]。 -每种类型的评论都会经过 API {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} 的不同部分。 -在本指南中,我们将探讨如何访问和处理每种注释。 对于每个示例,我们将使用在“octocat”存储库上[发出的此示例拉取请求][sample PR]。 和往常一样,可以在[平台示例存储库][platform-samples]中找到示例。 -## 拉取请求注释 -若要访问针对拉取请求的注释,请浏览[问题 API][issues]。 -乍一看这似乎不符合直觉。 但是,一旦你理解了拉取请求只是包含代码的问题,使用问题 API 来针对拉取请求创建注释就合情合理了。 +For any Pull Request, {% data variables.product.product_name %} provides three kinds of comment views: +[comments on the Pull Request][PR comment] as a whole, [comments on a specific line][PR line comment] within the Pull Request, +and [comments on a specific commit][commit comment] within the Pull Request. -我们将演示如何使用 [Octokit.rb][octokit.rb] 创建 Ruby 脚本来提取拉取请求注释。 你还需要创建[个人访问令牌][personal token]。 +Each of these types of comments goes through a different portion of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API. +In this guide, we'll explore how you can access and manipulate each one. For every +example, we'll be using [this sample Pull Request made][sample PR] on the "octocat" +repository. As always, samples can be found in [our platform-samples repository][platform-samples]. -以下代码应该可以帮助你开始使用 Octokit.rb 访问拉取请求中的注释: +## Pull Request Comments + +To access comments on a Pull Request, you'll go through [the Issues API][issues]. +This may seem counterintuitive at first. But once you understand that a Pull +Request is just an Issue with code, it makes sense to use the Issues API to +create comments on a Pull Request. + +We'll demonstrate fetching Pull Request comments by creating a Ruby script using +[Octokit.rb][octokit.rb]. You'll also want to create a [{% data variables.product.pat_generic %}][personal token]. + +The following code should help you get started accessing comments from a Pull Request +using Octokit.rb: ``` ruby require 'octokit' @@ -48,13 +53,18 @@ client.issue_comments("octocat/Spoon-Knife", 1176).each do |comment| end ``` -在这里,我们专门调用问题 API 来获取注释 (`issue_comments`),同时提供存储库的名称 (`octocat/Spoon-Knife`),以及我们感兴趣的拉取请求 ID (`1176`)。 之后,只需遍历注释以获取有关每个注释的信息即可。 +Here, we're specifically calling out to the Issues API to get the comments (`issue_comments`), +providing both the repository's name (`octocat/Spoon-Knife`), and the Pull Request ID +we're interested in (`1176`). After that, it's simply a matter of iterating through +the comments to fetch information about each one. -## 拉取请求行注释 +## Pull Request Comments on a Line -在差异视图中,你可以针对在拉取请求中进行的某个更改的特定方面开启讨论。 这些注释出现在已更改文件中的各个行上。 此讨论的终结点 URL 来自[拉取请求评审 API][PR Review API]。 +Within the diff view, you can start a discussion on a particular aspect of a singular +change made within the Pull Request. These comments occur on the individual lines +within a changed file. The endpoint URL for this discussion comes from [the Pull Request Review API][PR Review API]. -以下代码将获取文件中所做的所有拉取请求注释(给定一个拉取请求编号): +The following code fetches all the Pull Request comments made on files, given a single Pull Request number: ``` ruby require 'octokit' @@ -74,15 +84,19 @@ client.pull_request_comments("octocat/Spoon-Knife", 1176).each do |comment| end ``` -您会注意到,它与上面的示例非常相似。 此视图与拉取请求注释之间的不同之处在于对话的焦点。 -对拉取请求的注释应予以保留,以供讨论或就代码的总体方向提出意见。 在拉取请求评审中所做的注释应该以在文件中实施特定更改的方式进行专门处理。 +You'll notice that it's incredibly similar to the example above. The difference +between this view and the Pull Request comment is the focus of the conversation. +A comment made on a Pull Request should be reserved for discussion or ideas on +the overall direction of the code. A comment made as part of a Pull Request review should +deal specifically with the way a particular change was implemented within a file. -## 提交注释 +## Commit Comments -最后一类注释专门针对单个提交。 因此,它们使用[提交注释 API][commit comment API]。 +The last type of comments occur specifically on individual commits. For this reason, +they make use of [the commit comment API][commit comment API]. -要检索对提交的注释,您需要使用该提交的 SHA1。 -换句话说,您不能使用与拉取请求相关的任何标识符。 下面是一个示例: +To retrieve the comments on a commit, you'll want to use the SHA1 of the commit. +In other words, you won't use any identifier related to the Pull Request. Here's an example: ``` ruby require 'octokit' @@ -100,7 +114,8 @@ client.commit_comments("octocat/Spoon-Knife", "cbc28e7c8caee26febc8c013b0adfb97a end ``` -请注意,此 API 调用将检索单行注释以及对整个提交所做的注释。 +Note that this API call will retrieve single line comments, as well as comments made +on the entire commit. [PR comment]: https://github.com/octocat/Spoon-Knife/pull/1176#issuecomment-24114792 [PR line comment]: https://github.com/octocat/Spoon-Knife/pull/1176#discussion_r6252889 diff --git a/translations/zh-CN/content/rest/migrations/source-imports.md b/translations/zh-CN/content/rest/migrations/source-imports.md index 3644b3e9be..0034ccd814 100644 --- a/translations/zh-CN/content/rest/migrations/source-imports.md +++ b/translations/zh-CN/content/rest/migrations/source-imports.md @@ -1,5 +1,5 @@ --- -title: 源导入 +title: Source imports intro: '' versions: fpt: '*' @@ -7,18 +7,15 @@ versions: topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: 339b7f9543e91d2d33566435289b2092ef8c02e8 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147065768' --- -## 关于源导入 API -{% data variables.migrations.source_imports_intro %} 如果导入中存在大型文件,则典型的源导入将开始导入,然后(可选)更新作者和/或更新使用 Git LFS 的首选项。 还可以创建一个用于侦听 [`RepositoryImportEvent`](/developers/webhooks-and-events/webhook-events-and-payloads#repository_import) 的 Webhook 来了解导入状态。 +## About the Source imports API -在此图中可以看到更详细的示例: +{% data reusables.user-settings.imports-api-classic-pat-only %} + +{% data variables.migrations.source_imports_intro %} A typical source import would start the import and then (optionally) update the authors and/or update the preference for using Git LFS if large files exist in the import. You can also create a webhook that listens for the [`RepositoryImportEvent`](/developers/webhooks-and-events/webhook-events-and-payloads#repository_import) to find out the status of the import. + +A more detailed example can be seen in this diagram: ``` +---------+ +--------+ +---------------------+ diff --git a/translations/zh-CN/content/rest/overview/index.md b/translations/zh-CN/content/rest/overview/index.md index 40fe63a15e..a38b94c816 100644 --- a/translations/zh-CN/content/rest/overview/index.md +++ b/translations/zh-CN/content/rest/overview/index.md @@ -18,7 +18,9 @@ children: - /libraries - /openapi-description - /endpoints-available-for-github-apps + - /endpoints-available-for-fine-grained-personal-access-tokens - /permissions-required-for-github-apps + - /permissions-required-for-fine-grained-personal-access-tokens ms.openlocfilehash: 96d6109d1dcd2571ada7e448459980fdf6a92e05 ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a ms.translationtype: HT diff --git a/translations/zh-CN/content/rest/overview/other-authentication-methods.md b/translations/zh-CN/content/rest/overview/other-authentication-methods.md index 9cebcf591a..cd303a1c11 100644 --- a/translations/zh-CN/content/rest/overview/other-authentication-methods.md +++ b/translations/zh-CN/content/rest/overview/other-authentication-methods.md @@ -26,7 +26,7 @@ Instead, they should use the [OAuth web flow](/apps/building-oauth-apps/authoriz {% ifversion ghae %} -To authenticate we recommend using [OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/) tokens, such a personal access token through the [OAuth web flow](/apps/building-oauth-apps/authorizing-oauth-apps/). +To authenticate we recommend using [OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/) tokens, such a {% data variables.product.pat_generic %} through the [OAuth web flow](/apps/building-oauth-apps/authorizing-oauth-apps/). {% endif %} @@ -40,15 +40,15 @@ the existence of user data. Instead, the {% ifversion fpt or ghec %}{% data vari This may cause problems for HTTP libraries that assume a `401 Unauthorized` response. The solution is to manually craft the `Authorization` header. -### Via OAuth and personal access tokens +### Via {% data variables.product.pat_generic %}s -We recommend you use OAuth tokens to authenticate to the GitHub API. OAuth tokens include [personal access tokens][personal-access-tokens] and enable the user to revoke access at any time. +We recommend you use {% ifversion pat-v2%}{% data variables.product.pat_v2 %}s{% else %}{% data variables.product.pat_generic %}s{% endif %} to authenticate to the GitHub API. ```shell $ curl -u USERNAME:TOKEN {% data variables.product.api_url_pre %}/user ``` -This approach is useful if your tools only support Basic Authentication but you want to take advantage of OAuth access token security features. +This approach is useful if your tools only support Basic Authentication but you want to take advantage of {% data variables.product.pat_generic %} security features. ### Via username and password @@ -56,7 +56,7 @@ This approach is useful if your tools only support Basic Authentication but you {% note %} -**Note:** {% data variables.product.prodname_dotcom %} has discontinued password authentication to the API starting on November 13, 2020 for all {% data variables.product.prodname_dotcom_the_website %} accounts, including those on a {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_ghe_cloud %} plan. You must now authenticate to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API with an API token, such as an OAuth access token, GitHub App installation access token, or personal access token, depending on what you need to do with the token. For more information, see "[Troubleshooting](/rest/overview/troubleshooting#basic-authentication-errors)." +**Note:** {% data variables.product.prodname_dotcom %} has discontinued password authentication to the API starting on November 13, 2020 for all {% data variables.product.prodname_dotcom_the_website %} accounts, including those on a {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_ghe_cloud %} plan. You must now authenticate to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API with an API token, such as an OAuth access token, GitHub App installation access token, or {% data variables.product.pat_generic %}, depending on what you need to do with the token. For more information, see "[Troubleshooting](/rest/overview/troubleshooting#basic-authentication-errors)." {% endnote %} @@ -92,7 +92,7 @@ If you have two-factor authentication enabled, make sure you understand how to [ {% endnote %} -If you're using the API to access an organization that enforces [SAML SSO][saml-sso] for authentication, you'll need to create a personal access token (PAT) and [authorize the token][allowlist] for that organization. Visit the URL specified in `X-GitHub-SSO` to authorize the token for the organization. +If you're using the API to access an organization that enforces [SAML SSO][saml-sso] for authentication, you'll need to create a {% data variables.product.pat_generic %} and [authorize the token][allowlist] for that organization. Visit the URL specified in `X-GitHub-SSO` to authorize the token for the organization. ```shell $ curl -v -H "Authorization: Bearer TOKEN" {% data variables.product.api_url_pre %}/repos/octodocs-test/test @@ -104,7 +104,7 @@ $ curl -v -H "Authorization: Bearer TOKEN" {% data variables.product.api_url_pre } ``` -When requesting data that could come from multiple organizations (for example, [requesting a list of issues created by the user][user-issues]), the `X-GitHub-SSO` header indicates which organizations require you to authorize your personal access token: +When requesting data that could come from multiple organizations (for example, [requesting a list of issues created by the user][user-issues]), the `X-GitHub-SSO` header indicates which organizations require you to authorize your {% data variables.product.pat_generic %}: ```shell $ curl -v -H "Authorization: Bearer TOKEN" {% data variables.product.api_url_pre %}/user/issues @@ -112,15 +112,15 @@ $ curl -v -H "Authorization: Bearer TOKEN" {% data variables.product.api_url_pre > X-GitHub-SSO: partial-results; organizations=21955855,20582480 ``` -The value `organizations` is a comma-separated list of organization IDs for organizations require authorization of your personal access token. +The value `organizations` is a comma-separated list of organization IDs for organizations require authorization of your {% data variables.product.pat_generic %}. {% endif %} {% ifversion fpt or ghes or ghec %} ## Working with two-factor authentication -When you have two-factor authentication enabled, [Basic Authentication](#basic-authentication) for _most_ endpoints in the REST API requires that you use a personal access token{% ifversion ghes %} or OAuth token instead of your username and password{% endif %}. +When you have two-factor authentication enabled, [Basic Authentication](#basic-authentication) for _most_ endpoints in the REST API requires that you use a {% data variables.product.pat_generic %}{% ifversion ghes %} or OAuth token instead of your username and password{% endif %}. -You can generate a new personal access token {% ifversion fpt or ghec %}using [{% data variables.product.product_name %} developer settings](https://github.com/settings/tokens/new){% endif %}{% ifversion ghes %} or with the "[Create a new authorization][/rest/reference/oauth-authorizations#create-a-new-authorization]" endpoint in the OAuth Authorizations API to generate a new OAuth token{% endif %}. For more information, see "[Creating a personal access token for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". Then you would use these tokens to [authenticate using OAuth token][oauth-auth] with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.{% ifversion ghes %} The only time you need to authenticate with your username and password is when you create your OAuth token or use the OAuth Authorizations API.{% endif %} +You can generate a new {% data variables.product.pat_generic %} {% ifversion fpt or ghec %}using [{% data variables.product.product_name %} developer settings](https://github.com/settings/tokens/new){% endif %}{% ifversion ghes %} or with the "[Create a new authorization][/rest/reference/oauth-authorizations#create-a-new-authorization]" endpoint in the OAuth Authorizations API to generate a new OAuth token{% endif %}. For more information, see "[Creating a {% data variables.product.pat_generic %} for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". Then you would use these tokens to [authenticate using OAuth token][oauth-auth] with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.{% ifversion ghes %} The only time you need to authenticate with your username and password is when you create your OAuth token or use the OAuth Authorizations API.{% endif %} {% endif %} diff --git a/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md b/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md index 0432d216c9..d0348eb3b4 100644 --- a/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md @@ -362,7 +362,7 @@ If {% data variables.product.prodname_dotcom %} takes more than 10 seconds to pr ## Rate limiting -Different types of API requests to {% data variables.product.product_location %} are subject to different rate limits. +Different types of API requests to {% data variables.location.product_location %} are subject to different rate limits. Additionally, the Search API has dedicated limits. For more information, see "[Search](/rest/reference/search#rate-limit)" in the REST API documentation. @@ -372,7 +372,7 @@ Additionally, the Search API has dedicated limits. For more information, see "[S ### Requests from personal accounts -Direct API requests that you authenticate with a personal access token are user-to-server requests. An OAuth App or GitHub App can also make a user-to-server request on your behalf after you authorize the app. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)," "[Authorizing OAuth Apps](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)," and "[Authorizing GitHub Apps](/authentication/keeping-your-account-and-data-secure/authorizing-github-apps)." +Direct API requests that you authenticate with a {% data variables.product.pat_generic %} are user-to-server requests. An OAuth App or GitHub App can also make a user-to-server request on your behalf after you authorize the app. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)," "[Authorizing OAuth Apps](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)," and "[Authorizing GitHub Apps](/authentication/keeping-your-account-and-data-secure/authorizing-github-apps)." {% data variables.product.product_name %} associates all user-to-server requests with the authenticated user. For OAuth Apps and GitHub Apps, this is the user who authorized the app. All user-to-server requests count toward the authenticated user's rate limit. @@ -398,7 +398,7 @@ Requests from a GitHub App may be either user-to-server or server-to-server requ You can use the built-in `GITHUB_TOKEN` to authenticate requests in GitHub Actions workflows. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." -When using `GITHUB_TOKEN`, the rate limit is 1,000 requests per hour per repository.{% ifversion fpt or ghec %} For requests to resources that belong to an enterprise account on {% data variables.product.product_location %}, {% data variables.product.prodname_ghe_cloud %}'s rate limit applies, and the limit is 15,000 requests per hour per repository.{% endif %} +When using `GITHUB_TOKEN`, the rate limit is 1,000 requests per hour per repository.{% ifversion fpt or ghec %} For requests to resources that belong to an enterprise account on {% data variables.location.product_location %}, {% data variables.product.prodname_ghe_cloud %}'s rate limit applies, and the limit is 15,000 requests per hour per repository.{% endif %} ### Checking your rate limit status diff --git a/translations/zh-CN/content/rest/overview/troubleshooting.md b/translations/zh-CN/content/rest/overview/troubleshooting.md index f08db1b0ad..bcb8e7f189 100644 --- a/translations/zh-CN/content/rest/overview/troubleshooting.md +++ b/translations/zh-CN/content/rest/overview/troubleshooting.md @@ -1,6 +1,6 @@ --- -title: 故障排除 -intro: 学习如何解决用户在 REST API 中遇到的最常见问题。 +title: Troubleshooting +intro: Learn how to resolve the most common problems people encounter in the REST API. redirect_from: - /v3/troubleshooting versions: @@ -10,57 +10,62 @@ versions: ghec: '*' topics: - API -ms.openlocfilehash: 0aa55fae9b33604b95e0eeee78e0712e60aaa5c7 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147717675' --- -如果你在 API 中遇到一些奇怪的问题,下面列出了你可能会遇到的一些问题的解决方案。 -## 现有存储库的 `404` 错误 -一般来说,客户端没有正确通过身份验证时,我们会发送 `404` 错误。 -在这些情况下,你可能会看到 `403 Forbidden`。 但是,由于我们不想提供有关专用存储库的任何信息,API 会改为返回 `404` 错误。 -若要进行故障排除,请确保[正确进行身份验证](/guides/getting-started/)、[OAuth 访问令牌具有所需的范围](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)、[第三方应用程序限制][oap-guide]不会阻止访问,并且[令牌未过期或已吊销](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)。 +If you're encountering some oddities in the API, here's a list of resolutions to +some of the problems you may be experiencing. -## 并非所有结果都返回 +## `404` error for an existing repository -大多数 API 调用访问资源列表(例如,用户、问题等)支持分页 。 如果你发出请求但收到的结果集不完整,你可能只会看到第一页。 为了获得更多结果,你需要请求剩余的页面。 +Typically, we send a `404` error when your client isn't properly authenticated. +You might expect to see a `403 Forbidden` in these cases. However, since we don't +want to provide _any_ information about private repositories, the API returns a +`404` error instead. -请务必不要尝试和猜测分页 URL 的格式。 并非每个 API 调用都使用相同的结构, 而是从[链接标头](/rest#pagination)中提取分页信息,该标头随每个请求一起发送。 +To troubleshoot, ensure [you're authenticating correctly](/guides/getting-started/), [your OAuth access token has the required scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), [third-party application restrictions][oap-guide] are not blocking access, and that [the token has not expired or been revoked](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation). + +## Not all results returned + +Most API calls accessing a list of resources (_e.g._, users, issues, _etc._) support +pagination. If you're making requests and receiving an incomplete set of results, you're +probably only seeing the first page. You'll need to request the remaining pages +in order to get more results. + +It's important to *not* try and guess the format of the pagination URL. Not every +API call uses the same structure. Instead, extract the pagination information from +[the Link Header](/rest#pagination), which is sent with every request. [oap-guide]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ {% ifversion fpt or ghec %} -## 基本身份验证错误 +## Basic authentication errors -从 2020 年 11 月 13 日起,REST API 和 OAuth 授权 API 的用户名和密码身份验证被弃用,不再有效。 +On November 13, 2020 username and password authentication to the REST API and the OAuth Authorizations API were deprecated and no longer work. -### 使用 `username`/`password` 进行基本身份验证 +### Using `username`/`password` for basic authentication -如果使用的是 `username` 和 `password` 进行 API 调用,则它们将无法再进行身份验证。 例如: +If you're using `username` and `password` for API calls, then they are no longer able to authenticate. For example: ```bash curl -u my_user:my_password https://api.github.com/user/repos ``` -而是在测试终结点或执行本地开发时使用 [个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line): +Instead, use a [{% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line) when testing endpoints or doing local development: ```bash curl -H 'Authorization: Bearer my_access_token' https://api.github.com/user/repos ``` -对于 OAuth 应用,应使用 [Web 应用程序流](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) 生成要在 API 调用标头中使用的 OAuth 令牌: +For OAuth Apps, you should use the [web application flow](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to generate an OAuth token to use in the API call's header: ```bash curl -H 'Authorization: Bearer my-oauth-token' https://api.github.com/user/repos ``` -## 超时 +## Timeouts -如果 {% data variables.product.product_name %} 需要超过 10 秒来处理一个 API 请求, {% data variables.product.product_name %} 将会终止请求,并且您将收到超时响应。 +If {% data variables.product.product_name %} takes more than 10 seconds to process an API request, {% data variables.product.product_name %} will terminate the request and you will receive a timeout response. {% endif %} diff --git a/translations/zh-CN/content/rest/packages.md b/translations/zh-CN/content/rest/packages.md index d677790c89..9388be2f7f 100644 --- a/translations/zh-CN/content/rest/packages.md +++ b/translations/zh-CN/content/rest/packages.md @@ -1,6 +1,6 @@ --- -title: 包 -intro: '通过 {% data variables.product.prodname_registry %} API,您可以管理 {% data variables.product.prodname_dotcom %} 仓库和组织的软件包。' +title: Packages +intro: 'With the {% data variables.product.prodname_registry %} API, you can manage packages for your {% data variables.product.prodname_dotcom %} repositories and organizations.' versions: fpt: '*' ghec: '*' @@ -9,22 +9,17 @@ topics: miniTocMaxHeadingLevel: 3 redirect_from: - /rest/reference/packages -ms.openlocfilehash: 5edb7e30b296626a53fdc41806bcfba88718e6b3 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147059920' --- -## 关于 {% data variables.product.prodname_registry %} API -{% data variables.product.prodname_registry %} API 允许您使用 REST API 管理包。 要了解有关还原或删除包的详细信息,请参阅“[还原和删除包](/packages/learn-github-packages/deleting-and-restoring-a-package)”。 +## About the {% data variables.product.prodname_registry %} API -要使用此 API ,您必须使用个人访问令牌进行验证。 - - 要访问包元数据,令牌必须包含 `read:packages` 范围。 - - 要删除包和包版本,令牌必须包含 `read:packages` 和 `delete:packages` 范围。 - - 要还原包和包版本,令牌必须包含 `read:packages` 和 `write:packages` 范围。 +The {% data variables.product.prodname_registry %} API enables you to manage packages using the REST API. To learn more about restoring or deleting packages, see "[Restoring and deleting packages](/packages/learn-github-packages/deleting-and-restoring-a-package)." -如果你的 `package_type` 为 `npm`、`maven`、`rubygems` 或 `nuget`,则令牌还必须包含 `repo` 范围,因为你的包从 {% data variables.product.prodname_dotcom %} 存储库继承权限。 如果包在 {% data variables.product.prodname_container_registry %} 中,则你的 `package_type` 为 `container`,包和令牌不需要 `repo` 范围即可访问或管理此 `package_type`。 `container` 包提供与存储库不同的精细权限。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_registry %} 的权限](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)”。 +To use this API, you must authenticate using a {% data variables.product.pat_v1 %}. + - To access package metadata, your token must include the `read:packages` scope. + - To delete packages and package versions, your token must include the `read:packages` and `delete:packages` scopes. + - To restore packages and package versions, your token must include the `read:packages` and `write:packages` scopes. -如果您想使用 {% data variables.product.prodname_registry %} API 访问已启用 SSO 的组织中的资源,则必须对个人访问令牌启用 SSO。 有关详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[授权个人访问令牌以用于 SAML 单一登录](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}”。{% else %}."{% endif %} +If your `package_type` is `npm`, `maven`, `rubygems`, or `nuget`, then your token must also include the `repo` scope since your package inherits permissions from a {% data variables.product.prodname_dotcom %} repository. If your package is in the {% data variables.product.prodname_container_registry %}, then your `package_type` is `container` and your token does not need the `repo` scope to access or manage this `package_type`. `container` packages offer granular permissions separate from a repository. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)." + +If you want to use the {% data variables.product.prodname_registry %} API to access resources in an organization with SSO enabled, then you must enable SSO for your {% data variables.product.pat_v1 %}. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} diff --git a/translations/zh-CN/content/rest/projects/projects.md b/translations/zh-CN/content/rest/projects/projects.md index 6c2c609ab9..1a6b0a537f 100644 --- a/translations/zh-CN/content/rest/projects/projects.md +++ b/translations/zh-CN/content/rest/projects/projects.md @@ -2,7 +2,7 @@ title: '{% data variables.product.prodname_projects_v1_caps %}' shortTitle: Boards allowTitleToDifferFromFilename: true -intro: '使用 {% data variables.product.prodname_projects_v1 %} API,可以在存储库中创建和管理 {% data variables.projects.projects_v1_boards %}。' +intro: 'The {% data variables.product.prodname_projects_v1 %} API lets you create and manage {% data variables.projects.projects_v1_boards %} in a repository.' versions: fpt: '*' ghes: '*' @@ -11,11 +11,8 @@ versions: topics: - API miniTocMaxHeadingLevel: 3 -ms.openlocfilehash: f5c7d3e39f4de88bd071fecab159b08d540e5055 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147882357' --- + {% data reusables.projects.projects-api %} + +{% data reusables.user-settings.classic-projects-api-classic-pat-only %} diff --git a/translations/zh-CN/content/rest/scim.md b/translations/zh-CN/content/rest/scim.md index b3f75976f1..cc680f5db1 100644 --- a/translations/zh-CN/content/rest/scim.md +++ b/translations/zh-CN/content/rest/scim.md @@ -1,6 +1,6 @@ --- title: SCIM -intro: 可使用 SCIM API 控制和管理 GitHub 组织成员访问权限。 +intro: You can control and manage your GitHub organization members access using SCIM API. versions: ghec: '*' topics: @@ -8,50 +8,45 @@ topics: miniTocMaxHeadingLevel: 3 redirect_from: - /rest/reference/scim -ms.openlocfilehash: 314ed9433ffeb1ef3f189795727a3b654c529c96 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: '147883041' --- -## 关于 SCIM API -### 组织的 SCIM 预配 +## About the SCIM API -SCIM API 由 SCIM 启用的身份提供程序 (IdP) 用来自动预配 {% data variables.product.product_name %} 组织成员身份。 {% ifversion fpt or ghec %} {% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 基于 [ 的 2.0 版 SCIM 标准](http://www.simplecloud.info/)。 IdP 应使用的 {% data variables.product.product_name %} SCIM 终结点是:`{% data variables.product.api_url_code %}/scim/v2/organizations/{org}/`。 +### SCIM Provisioning for Organizations + +The SCIM API is used by SCIM-enabled Identity Providers (IdPs) to automate provisioning of {% data variables.product.product_name %} organization membership. The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API is based on version 2.0 of the [SCIM standard](http://www.simplecloud.info/). The {% data variables.product.product_name %} SCIM endpoint that an IdP should use is: `{% data variables.product.api_url_code %}/scim/v2/organizations/{org}/`. {% note %} -**注意:** - - SCIM API 仅适用于启用了 [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) 的 [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) 使用的个人组织。 有关 SCIM 的详细信息,请参阅“[关于组织的 SCIM](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)”。 - - SCIM API 不能与企业帐户或 {% data variables.product.prodname_emu_org %} 一起使用。 +**Notes:** + - The SCIM API is available only for individual organizations that use [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM for organizations](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)." + - The SCIM API cannot be used with an enterprise account or with an {% data variables.enterprise.prodname_emu_org %}. {% endnote %} -### 向 SCIM API 验证调用 +### Authenticating calls to the SCIM API -您必须验证为 {% data variables.product.product_name %} 组织的所有者才可使用其 SCIM API。 该 API 要求将 [OAuth 2.0 持有者](/developers/apps/authenticating-with-github-apps)令牌包含在 `Authorization` 标头中。 还可以使用个人访问令牌,但必须先[授权它与 SAML SSO 组织一起使用](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)。 +You must authenticate as an owner of a {% data variables.product.product_name %} organization to use its SCIM API. The API expects an [OAuth 2.0 Bearer](/developers/apps/authenticating-with-github-apps) token to be included in the `Authorization` header. If you use a {% data variables.product.pat_v1 %} for authentication, it must have the `admin:org` scope and you must also [authorize it for use with your SAML SSO organization](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on). -### SAML 和 SCIM 数据的映射 +### Mapping of SAML and SCIM data {% data reusables.scim.nameid-and-username-must-match %} -### 支持的 SCIM 用户属性 +### Supported SCIM User attributes -名称 | 类型 | 说明 +Name | Type | Description -----|------|-------------- -`userName`|`string` | 用户的用户名。 -`name.givenName`|`string` | 用户的名字。 -`name.familyName`|`string` | 用户的姓氏。 -`emails` | `array` | 用户电子邮件列表。 -`externalId` | `string` | 此标识符由 SAML 提供程序生成,并且被 SAML 提供程序用作唯一 ID 来匹配 GitHub 用户。 可以在 SAML 提供程序上查找用户的 `externalID`,也可以使用[列出 SCIM 预配的身份](#list-scim-provisioned-identities)终结点并筛选其他已知属性,例如用户的 GitHub 用户名或电子邮件地址。 -`id` | `string` | GitHub SCIM 端点生成的标识符。 -`active` | `boolean` | 用于表示身份是处于活动状态 (true) 还是应解除预配 (false)。 +`userName`|`string` | The username for the user. +`name.givenName`|`string` | The first name of the user. +`name.familyName`|`string` | The last name of the user. +`emails` | `array` | List of user emails. +`externalId` | `string` | This identifier is generated by the SAML provider, and is used as a unique ID by the SAML provider to match against a GitHub user. You can find the `externalID` for a user either at the SAML provider, or using the [List SCIM provisioned identities](#list-scim-provisioned-identities) endpoint and filtering on other known attributes, such as a user's GitHub username or email address. +`id` | `string` | Identifier generated by the GitHub SCIM endpoint. +`active` | `boolean` | Used to indicate whether the identity is active (true) or should be deprovisioned (false). {% note %} -注意:SCIM API 的终结点 URL 区分大小写。 例如,`Users` 终结点中的第一个字母必须大写: +**Note:** Endpoint URLs for the SCIM API are case sensitive. For example, the first letter in the `Users` endpoint must be capitalized: ```shell GET /scim/v2/organizations/{org}/Users/{scim_user_id} diff --git a/translations/zh-CN/content/rest/teams/team-sync.md b/translations/zh-CN/content/rest/teams/team-sync.md index 331f4c7a2a..83a7cfda33 100644 --- a/translations/zh-CN/content/rest/teams/team-sync.md +++ b/translations/zh-CN/content/rest/teams/team-sync.md @@ -1,27 +1,22 @@ --- -title: 团队同步 -intro: '团队同步 API 允许你管理 {% data variables.product.product_name %} 团队与外部标识提供者 (IdP) 组之间的连接。' +title: Team synchronization +intro: 'The Team synchronization API allows you to manage connections between {% data variables.product.product_name %} teams and external identity provider (IdP) groups.' versions: ghec: '*' topics: - API miniTocMaxHeadingLevel: 3 allowTitleToDifferFromFilename: true -ms.openlocfilehash: 6a5d379b1050e10f9e31e14ed2b094a684676737 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147067160' --- -## 关于团队同步 API -要使用此 API,经过身份验证的用户必须是团队维护员或与团队关联的组织的所有者。 用于身份验证的令牌还需要获得授权才能与 IdP (SSO) 提供程序一起使用。 有关详细信息,请参阅“[授权用于 SAML 单一登录组织的个人访问令牌](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)”。 +## About the Team synchronization API -您可以通过 IdP 通过团队同步管理 GitHub 团队成员。 必须启用团队同步才能使用团队同步 API。 有关详细信息,请参阅“[在标识提供者与 GitHub 之间同步团队](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)”。 +To use this API, the authenticated user must be a team maintainer or an owner of the organization associated with the team. The token you use to authenticate will also need to be authorized for use with your IdP (SSO) provider. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with a SAML single sign-on organization](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)." + +You can manage GitHub team members through your IdP with team synchronization. Team synchronization must be enabled to use the Team Synchronization API. For more information, see "[Synchronizing teams between your identity provider and GitHub](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)." {% note %} -注意:团队同步 API 不能与 {% data variables.product.prodname_emus %} 一起使用。 若要详细了解如何管理 {% data variables.product.prodname_emu_org %},请参阅“[外部组 API](/enterprise-cloud@latest/rest/reference/teams#external-groups)”。 +**Note:** The Team Synchronization API cannot be used with {% data variables.product.prodname_emus %}. To learn more about managing an {% data variables.enterprise.prodname_emu_org %}, see "[External groups API](/enterprise-cloud@latest/rest/reference/teams#external-groups)". {% endnote %} diff --git a/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md index c648fce4d5..503c7cbd7a 100644 --- a/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md +++ b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md @@ -1,6 +1,6 @@ --- -title: 关于在 GitHub 上搜索 -intro: '我们的集成搜索涵盖了 {% data variables.product.product_name %} 上的许多仓库、用户和代码行。' +title: About searching on GitHub +intro: 'Our integrated search covers the many repositories, users, and lines of code on {% data variables.product.product_name %}.' redirect_from: - /articles/using-the-command-bar - /articles/github-search-basics @@ -17,76 +17,70 @@ versions: ghec: '*' topics: - GitHub search -ms.openlocfilehash: 875bb9876a36ce7f202d31749771dc147f348524 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146179373' --- {% data reusables.search.you-can-search-globally %} -- 要全局搜索所有 {% data variables.product.product_name %},请在页面顶部的搜索字段中输入您要查找的内容,然后在搜索下拉菜单中选择“所有{% data variables.product.prodname_dotcom %}”。 -- 要在特定存储库或组织中搜索,请导航到该存储库或组织页面,在页面顶部的搜索字段中输入要查找的内容,然后按 Enter。 +- To search globally across all of {% data variables.product.product_name %}, type what you're looking for into the search field at the top of any page, and choose "All {% data variables.product.prodname_dotcom %}" in the search drop-down menu. +- To search within a particular repository or organization, navigate to the repository or organization page, type what you're looking for into the search field at the top of the page, and press **Enter**. {% note %} -**注意:** +**Notes:** {% ifversion fpt or ghes or ghec %} - {% data reusables.search.required_login %}{% endif %} -- {% data variables.product.prodname_pages %} 网站在 {% data variables.product.product_name %} 上不可搜索。 但如果源代码内容存在于仓库的默认分支中,您可以使用代码搜索来搜索。 有关详细信息,请参阅“[搜索代码](/search-github/searching-on-github/searching-code)”。 有关 {% data variables.product.prodname_pages %} 的详细信息,请参阅“[什么是 GitHub 页面?](/articles/what-is-github-pages/)” -- 目前我们的搜索不支持精确匹配。 -- 每当您在代码文件中搜索时,将仅返回每个文件中的前两个结果。 +- {% data variables.product.prodname_pages %} sites are not searchable on {% data variables.product.product_name %}. However you can search the source content if it exists in the default branch of a repository, using code search. For more information, see "[Searching code](/search-github/searching-on-github/searching-code)." For more information about {% data variables.product.prodname_pages %}, see "[What is GitHub Pages?](/articles/what-is-github-pages/)" +- Currently our search doesn't support exact matching. +- Whenever you are searching in code files, only the first two results in each file will be returned. {% endnote %} -在 {% data variables.product.product_name %} 上搜索后,您可以对结果排序,或者单击侧栏中的任一语言进一步改进搜索。 有关详细信息,请参阅“[对搜索结果进行排序](/search-github/getting-started-with-searching-on-github/sorting-search-results)”。 +After running a search on {% data variables.product.product_name %}, you can sort the results, or further refine them by clicking one of the languages in the sidebar. For more information, see "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results)." -每次推送更改到 {% data variables.product.product_name %} 时,{% data variables.product.product_name %} 搜索都会使用 ElasticSearch 群集对项目编制索引。 议题和拉取请求在创建或修改时都会编制索引。 +{% data variables.product.product_name %} search uses an ElasticSearch cluster to index projects every time a change is pushed to {% data variables.product.product_name %}. Issues and pull requests are indexed when they are created or modified. -## {% data variables.product.prodname_dotcom %} 上的搜索类型 +## Types of searches on {% data variables.product.prodname_dotcom %} -您可以在 {% data variables.product.product_location %} 上可以访问的所有仓库中搜索以下信息。 +You can search for the following information across all repositories you can access on {% data variables.location.product_location %}. -- [存储库](/search-github/searching-on-github/searching-for-repositories) -- [主题](/search-github/searching-on-github/searching-topics) -- [问题和拉取请求](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt or ghec %} -- [讨论](/search-github/searching-on-github/searching-discussions){% endif %} -- [代码](/search-github/searching-on-github/searching-code) -- [提交](/search-github/searching-on-github/searching-commits) -- [用户](/search-github/searching-on-github/searching-users) -- [包](/search-github/searching-on-github/searching-for-packages) -- [Wiki](/search-github/searching-on-github/searching-wikis) +- [Repositories](/search-github/searching-on-github/searching-for-repositories) +- [Topics](/search-github/searching-on-github/searching-topics) +- [Issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt or ghec %} +- [Discussions](/search-github/searching-on-github/searching-discussions){% endif %} +- [Code](/search-github/searching-on-github/searching-code) +- [Commits](/search-github/searching-on-github/searching-commits) +- [Users](/search-github/searching-on-github/searching-users) +- [Packages](/search-github/searching-on-github/searching-for-packages) +- [Wikis](/search-github/searching-on-github/searching-wikis) -## 使用可视界面搜索 +## Searching using a visual interface -您可以使用 {% data variables.search.search_page_url %} 或 {% data variables.search.advanced_url %} 搜索 {% data variables.product.product_name %}。 {% ifversion command-palette %}或者,可使用 {% data variables.product.prodname_command_palette %} 中的交互式搜索在 UI、特定用户、存储库或组织中搜索当前位置,并在所有 {% data variables.product.product_name %} 中全局搜索,而无需离开键盘。 有关详细信息,请参阅“[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)”。{% endif %} +You can search {% data variables.product.product_name %} using the {% data variables.search.search_page_url %} or {% data variables.search.advanced_url %}. {% ifversion command-palette %}Alternatively, you can use the interactive search in the {% data variables.product.prodname_command_palette %} to search your current location in the UI, a specific user, repository or organization, and globally across all of {% data variables.product.product_name %}, without leaving the keyboard. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %} -{% data variables.search.advanced_url %} 提供用于构建搜索查询的可视界面。 您可以按各种因素过滤搜索,例如仓库具有的星标数或复刻数。 在填写高级搜索字段时,您的查询将在顶部搜索栏中自动构建。 +The {% data variables.search.advanced_url %} provides a visual interface for constructing search queries. You can filter your searches by a variety of factors, such as the number of stars or number of forks a repository has. As you fill in the advanced search fields, your query will automatically be constructed in the top search bar. -![高级搜索](/assets/images/help/search/advanced_search_demo.gif) +![Advanced Search](/assets/images/help/search/advanced_search_demo.gif) -## 从您的私有企业环境中搜索 {% data variables.product.prodname_dotcom_the_website %} 上的存储库 +## Searching repositories on {% data variables.product.prodname_dotcom_the_website %} from your private enterprise environment {% ifversion fpt or ghec %} -如果你使用 {% data variables.product.prodname_dotcom_the_website %} 和 {% data variables.product.prodname_ghe_server %} 或 {% data variables.product.prodname_ghe_managed %},并且企业所有者已启用 {% data variables.product.prodname_unified_search %},则可以从 {% data variables.product.prodname_ghe_server %} 或 {% data variables.product.prodname_ghe_managed %} 同时搜索这两个环境。 有关详细信息,请参阅 [{% data variables.product.prodname_ghe_server %} 文档](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)或 [{% data variables.product.prodname_ghe_managed %} 文档](/github-ae@latest/search-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)。 +If you use both {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %}, and an enterprise owner has enabled {% data variables.enterprise.prodname_unified_search %}, you can search across both environments at the same time from {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %}. For more information, see [the {% data variables.product.prodname_ghe_server %} documentation](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment) or [the {% data variables.product.prodname_ghe_managed %} documentation](/github-ae@latest/search-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment). {% else %} -如果你使用 {% data variables.product.prodname_dotcom_the_website %} 和 {% data variables.product.product_name %},并且企业所有者已启用 {% data variables.product.prodname_unified_search %},则可以同时从 {% data variables.product.product_name %} 搜索这两个环境。 有关企业所有者如何启用 {% data variables.product.prodname_unified_search %} 的详细信息,请参阅“[为企业启用 {% data variables.product.prodname_unified_search %}](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)”。 +If you use both {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.product_name %}, and an enterprise owner has enabled {% data variables.enterprise.prodname_unified_search %}, you can search across both environments at the same time from {% data variables.product.product_name %}. For more information about how enterprise owners can enable {% data variables.enterprise.prodname_unified_search %}, see "[Enabling {% data variables.enterprise.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)." -{% data variables.product.product_name %} 上的企业所有者可以单独为 {% data variables.product.prodname_dotcom_the_website %} 上的所有公共存储库以及通过 {% data variables.product.prodname_github_connect %} 连接到 {% data variables.product.product_name %} 的 {% data variables.product.prodname_dotcom_the_website %} 上的组织或企业拥有的专用存储库启用 {% data variables.product.prodname_unified_search %}。 +Your enterprise owner on {% data variables.product.product_name %} can separately enable {% data variables.enterprise.prodname_unified_search %} for all public repositories on {% data variables.product.prodname_dotcom_the_website %} and for private repositories owned by the organization or enterprise on {% data variables.product.prodname_dotcom_the_website %} that is connected to {% data variables.product.product_name %} through {% data variables.product.prodname_github_connect %}. -在将 {% data variables.product.prodname_unified_search %} 用于专用存储库之前,必须在 {% data variables.product.prodname_dotcom_the_website %} 和 {% data variables.product.product_name %} 上连接个人帐户。 有关详细信息,请参阅“[在专用企业环境中启用 {% data variables.product.prodname_dotcom_the_website %} 存储库搜索](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)”。 +Before you can use {% data variables.enterprise.prodname_unified_search %} for private repositories, you must connect your personal accounts on {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.product_name %}. For more information, see "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." -从 {% data variables.product.product_name %} 进行搜索时,只有你有权访问且由已连接的组织或企业帐户拥有的专用存储库才会包含在搜索结果中。 你和其他人都无法从 {% data variables.product.product_name %} 搜索 {% data variables.product.prodname_dotcom_the_website %} 上的个人帐户拥有的专用存储库。 +When you search from {% data variables.product.product_name %}, only private repositories that you have access to and that are owned by the connected organization or enterprise account will be included in search results. Neither you nor anyone else will be able to search private repositories owned by your personal account on {% data variables.product.prodname_dotcom_the_website %} from {% data variables.product.product_name %}. -若要将你的搜索限制到一个环境,可以使用 {% data variables.search.advanced_url %} 上的筛选器选项,或者使用 `environment:` 搜索前缀。 若要仅搜索 {% data variables.product.product_name %} 上的内容,请使用搜索语法 `environment:local`。 若要仅搜索 {% data variables.product.prodname_dotcom_the_website %} 上的内容,请使用 `environment:github`。 +To limit your search to one environment, you can use a filter option on the {% data variables.search.advanced_url %} or you can use the `environment:` search prefix. To only search for content on {% data variables.product.product_name %}, use the search syntax `environment:local`. To only search for content on {% data variables.product.prodname_dotcom_the_website %}, use `environment:github`. {% endif %} -## 延伸阅读 +## Further reading -- [了解搜索语法](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) -- [在 GitHub 上搜索](/articles/searching-on-github) +- "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)" +- "[Searching on GitHub](/articles/searching-on-github)" diff --git a/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md index 883d83b758..2c6c969728 100644 --- a/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md +++ b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md @@ -18,11 +18,11 @@ topics: ## About search for {% data variables.product.prodname_dotcom_the_website %} repositories from {% data variables.product.product_name %} -You can search for designated private repositories on {% data variables.product.prodname_ghe_cloud %} from {% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}. For more information about searching across environments, see "[About searching on GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)." +You can search for designated private repositories on {% data variables.product.prodname_ghe_cloud %} from {% data variables.location.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}. For more information about searching across environments, see "[About searching on GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)." ## Prerequisites -An enterprise owner for {% data variables.product.product_name %} must enable {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_unified_search %} for private repositories. For more information, see "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)." +An enterprise owner for {% data variables.product.product_name %} must enable {% data variables.product.prodname_github_connect %} and {% data variables.enterprise.prodname_unified_search %} for private repositories. For more information, see "[Enabling {% data variables.enterprise.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)." ## Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from {% data variables.product.product_name %} diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md b/translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md index 56d3c0f58d..69c5aeed59 100644 --- a/translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md +++ b/translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md @@ -1,6 +1,6 @@ --- -title: 搜索仓库 -intro: '您可以在 {% data variables.product.product_name %} 上搜索仓库,并使用这些仓库搜索限定符的任意组合缩小结果范围。' +title: Searching for repositories +intro: 'You can search for repositories on {% data variables.product.product_name %} and narrow the results using these repository search qualifiers in any combination.' redirect_from: - /articles/searching-repositories - /articles/searching-for-repositories @@ -14,195 +14,193 @@ versions: topics: - GitHub search shortTitle: Search for repositories -ms.openlocfilehash: 9a464fbb327809b8af970c9a62c3a70d81c2c6b9 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147527932' --- -可以在所有 {% data variables.product.product_location %} 内全局搜索存储库,也可以在特定组织内搜索存储库。 有关详细信息,请参阅“[关于在 {% data variables.product.prodname_dotcom %} 中搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。 +You can search for repositories globally across all of {% data variables.location.product_location %}, or search for repositories within a particular organization. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." -若要在搜索结果中包含分支,需要在查询中添加 `fork:true` 或 `fork:only`。 有关详细信息,请参阅“[在分支中搜索](/search-github/searching-on-github/searching-in-forks)”。 +To include forks in the search results, you will need to add `fork:true` or `fork:only` to your query. For more information, see "[Searching in forks](/search-github/searching-on-github/searching-in-forks)." {% data reusables.search.syntax_tips %} -## 按仓库名称、说明或自述文件内容搜索 +## Search by repository name, description, or contents of the README file -通过 `in` 限定符,可将搜索范围限制到存储库名称、存储库说明、存储库主题、自述文件内容或这些项的任意组合。 如果省略此限定符,则仅搜索存储库名称、说明和主题。 +With the `in` qualifier you can restrict your search to the repository name, repository description, repository topics, contents of the README file, or any combination of these. When you omit this qualifier, only the repository name, description, and topics are searched. -| 限定符 | 示例 +| Qualifier | Example | ------------- | ------------- -| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) 匹配名称中带有“jquery”的存储库。 -| `in:description` | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) 匹配名称或说明中带有“jquery”的存储库。 -| `in:topics` | [jquery in:topics](https://github.com/search?q=jquery+in%3Atopics&type=Repositories) 将带“jquery”标签的存储库匹配为主题。 -| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) 匹配自述文件中提及“jquery”的存储库。 -| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) 匹配特定的存储库名称。 +| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) matches repositories with "jquery" in the repository name. +| `in:description` | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) matches repositories with "jquery" in the repository name or description. +| `in:topics` | [**jquery in:topics**](https://github.com/search?q=jquery+in%3Atopics&type=Repositories) matches repositories labeled with "jquery" as a topic. +| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) matches repositories mentioning "jquery" in the repository's README file. +| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) matches a specific repository name. -## 基于仓库的内容搜索 +## Search based on the contents of a repository -可以使用 `in:readme` 限定符,通过搜索存储库自述文件中的内容来查找存储库。 有关详细信息,请参阅“[关于自述文件](/github/creating-cloning-and-archiving-repositories/about-readmes)”。 +You can find a repository by searching for content in the repository's README file using the `in:readme` qualifier. For more information, see "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)." -除了使用 `in:readme`,还可以通过搜索存储库中的特定内容来查找存储库。 要搜索仓库内的特定文件或内容,您可以使用查找器或代码特定的搜索限定符。 有关详细信息,请参阅“[在 {% data variables.product.prodname_dotcom %} 上查找文件](/search-github/searching-on-github/finding-files-on-github)”和“[搜索代码](/search-github/searching-on-github/searching-code)”。 +Besides using `in:readme`, it's not possible to find repositories by searching for specific content within the repository. To search for a specific file or content within a repository, you can use the file finder or code-specific search qualifiers. For more information, see "[Finding files on {% data variables.product.prodname_dotcom %}](/search-github/searching-on-github/finding-files-on-github)" and "[Searching code](/search-github/searching-on-github/searching-code)." -| 限定符 | 示例 +| Qualifier | Example | ------------- | ------------- -| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) 匹配自述文件中提及“octocat”的存储库。 +| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) matches repositories mentioning "octocat" in the repository's README file. -## 在用户或组织的仓库内搜索 +## Search within a user's or organization's repositories -若要在特定用户或组织拥有的所有存储库中搜索,可使用 `user` 或 `org` 限定符。 +To search in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. -| 限定符 | 示例 +| Qualifier | Example | ------------- | ------------- -| user:USERNAME | [**user:defunkt forks:>100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) 匹配来自 @defunkt 且具有超过 100 个分支的存储库。 -| org:ORGNAME | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) 匹配来自 GitHub 的存储库。 +| user:USERNAME | [**user:defunkt forks:>100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) matches repositories from @defunkt that have more than 100 forks. +| org:ORGNAME | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) matches repositories from GitHub. -## 按仓库大小搜索 +## Search by repository size -`size` 限定符使用大于、小于和范围限定符查找与特定大小(以千字节为单位)匹配的存储库。 有关详细信息,请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 +The `size` qualifier finds repositories that match a certain size (in kilobytes), using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." -| 限定符 | 示例 +| Qualifier | Example | ------------- | ------------- -| size:n | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) 匹配正好为 1 MB 的存储库。 -| | [**size:>=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) 匹配至少为 30 MB 的存储库。 -| | [**size:<50**](https://github.com/search?q=size%3A%3C50&type=Repositories) 匹配小于 50 KB 的存储库。 -| | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) 匹配介于 50 KB 至 120 KB 之间的存储库。 +| size:n | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) matches repositories that are 1 MB exactly. +| | [**size:>=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) matches repositories that are at least 30 MB. +| | [**size:<50**](https://github.com/search?q=size%3A%3C50&type=Repositories) matches repositories that are smaller than 50 KB. +| | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) matches repositories that are between 50 KB and 120 KB. -## 按关注者数量搜索 +## Search by number of followers -可以使用 `followers` 限定符以及大于、小于和范围限定符,根据关注存储库的用户数量筛选存储库。 有关详细信息,请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 +You can filter repositories based on the number of users who follow the repositories, using the `followers` qualifier with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." -| 限定符 | 示例 +| Qualifier | Example | ------------- | ------------- -| followers:n | [**node followers:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) 匹配有 10,000 名或更多关注者提及“node”一词的存储库。 -| | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) 匹配有 1 至 10 名关注者提及“styleguide linter”一词的存储库。 +| followers:n | [**node followers:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) matches repositories with 10,000 or more followers mentioning the word "node". +| | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) matches repositories with between 1 and 10 followers, mentioning the word "styleguide linter." -## 按复刻数量搜索 +## Search by number of forks -`forks` 限定符使用大于、小于和范围限定符指定存储库应具有的分支数量。 有关详细信息,请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 +The `forks` qualifier specifies the number of forks a repository should have, using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." -| 限定符 | 示例 +| Qualifier | Example | ------------- | ------------- -| forks:n | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) 匹配只有五个分支的存储库。 -| | [**forks:>=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) 匹配至少有 205 个分支的存储库。 -| | [**forks:<90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) 匹配具有少于 90 个分支的存储库。 -| | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) 匹配具有 10 到 20 个分支的存储库。 +| forks:n | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) matches repositories with only five forks. +| | [**forks:>=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) matches repositories with at least 205 forks. +| | [**forks:<90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) matches repositories with fewer than 90 forks. +| | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) matches repositories with 10 to 20 forks. -## 按星号数量搜索 +## Search by number of stars -您可以使用大于、小于和范围限定符,基于仓库的星标数量来搜索仓库。 有关详细信息,请参阅“[使用星标保存存储库](/github/getting-started-with-github/saving-repositories-with-stars)”和“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 +You can search repositories based on the number of stars the repositories have, using greater than, less than, and range qualifiers. For more information, see "[Saving repositories with stars](/github/getting-started-with-github/saving-repositories-with-stars)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." -| 限定符 | 示例 +| Qualifier | Example | ------------- | ------------- -| stars:n | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) 匹配正好有 500 个星标的存储库。 -| | [stars:10..20 size:<1000](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) 匹配有 10 到 20 个星标、小于 1000 KB 的存储库。 -| | [**stars:>=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) 匹配至少有 500 个星标(包括用 PHP 编写的分支星标)的存储库。 +| stars:n | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) matches repositories with exactly 500 stars. +| | [**stars:10..20 size:<1000**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) matches repositories 10 to 20 stars, that are smaller than 1000 KB. +| | [**stars:>=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) matches repositories with the at least 500 stars, including forked ones, that are written in PHP. -## 按仓库创建或上次更新时间搜索 +## Search by when a repository was created or last updated -您可以基于创建时间或上次更新时间过滤仓库。 对于存储库创建,可以使用 `created` 限定符;要了解存储库的最后更新时间,需要使用 `pushed` 限定符。 `pushed` 限定符将返回存储库列表,按存储库中任意分支上最近进行的提交排序。 +You can filter repositories based on time of creation or time of last update. For repository creation, you can use the `created` qualifier; to find out when a repository was last updated, you'll want to use the `pushed` qualifier. The `pushed` qualifier will return a list of repositories, sorted by the most recent commit made on any branch in the repository. -两者均采用日期作为参数。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} +Both take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} {% data reusables.search.date_gt_lt %} -| 限定符 | 示例 +| Qualifier | Example | ------------- | ------------- -| created:YYYY-MM-DD | [**webos created:<2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) 匹配具有 2011 年之前创建的“webos”一词的存储库。 -| pushed:YYYY-MM-DD | [**css pushed:>2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) 匹配具有在 2013 年 1 月之后推送到其中的“css”一词的存储库。 -| | [**case pushed:>=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) 匹配在 2013 年 3 月 6 日或之后将“case”一词推送到其中的存储库(即分支)。 +| created:YYYY-MM-DD | [**webos created:<2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) matches repositories with the word "webos" that were created before 2011. +| pushed:YYYY-MM-DD | [**css pushed:>2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) matches repositories with the word "css" that were pushed to after January 2013. +| | [**case pushed:>=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) matches repositories with the word "case" that were pushed to on or after March 6th, 2013, and that are forks. -## 按语言搜索 +## Search by language -您可以根据仓库中代码的语言搜索仓库。 +You can search repositories based on the language of the code in the repositories. -| 限定符 | 示例 +| Qualifier | Example | ------------- | ------------- -| language:LANGUAGE | [ **`rails language:javascript`**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) 匹配具有以 JavaScript 编写的“rails”一词的存储库。 +| language:LANGUAGE | [**`rails language:javascript`**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) matches repositories with the word "rails" that are written in JavaScript. -## 按主题搜索 +## Search by topic -您可以找到按特定主题分类的所有仓库。 有关详细信息,请参阅“[按主题对存储库进行分类](/github/administering-a-repository/classifying-your-repository-with-topics)”。 +You can find all of the repositories that are classified with a particular topic. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)." -| 限定符 | 示例 +| Qualifier | Example | ------------- | ------------- -| topic:TOPIC | [ **`topic:jekyll`**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) 匹配按“Jekyll”主题分类的存储库。 +| topic:TOPIC | [**`topic:jekyll`**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) matches repositories that have been classified with the topic "Jekyll." -## 按主题数量搜索 +## Search by number of topics -可以使用 `topics` 限定符以及大于、小于和范围限定符,根据应用于存储库的主题数量来搜索存储库。 有关详细信息,请参阅“[按主题对存储库进行分类](/github/administering-a-repository/classifying-your-repository-with-topics)”和“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 +You can search repositories by the number of topics that have been applied to the repositories, using the `topics` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." -| 限定符 | 示例 +| Qualifier | Example | ------------- | ------------- -| topics:n | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) 匹配具有五个主题的存储库。 -| | [**topics:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) 匹配具有三个以上主题的存储库。 +| topics:n | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) matches repositories that have five topics. +| | [**topics:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) matches repositories that have more than three topics. {% ifversion fpt or ghes or ghec %} -## 按许可搜索 +## Search by license -您可以根据仓库中许可的类型搜索仓库。 您必须使用许可关键字,按特定许可或许可系列来过滤仓库。 有关详细信息,请参阅“[许可存储库](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)”。 +You can search repositories by the type of license in the repositories. You must use a license keyword to filter repositories by a particular license or license family. For more information, see "[Licensing a repository](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)." -| 限定符 | 示例 +| Qualifier | Example | ------------- | ------------- -| license:LICENSE_KEYWORD | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) 匹配根据 Apache 许可证 2.0 许可的存储库。 +| license:LICENSE_KEYWORD | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) matches repositories that are licensed under Apache License 2.0. {% endif %} -## 按仓库可见性搜索 +## Search by repository visibility -您可以根据仓库的可见性过滤搜索。 有关详细信息,请参阅“[关于存储库](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)”。 +You can filter your search based on the visibility of the repositories. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." -| 限定符 | 示例 | ------------- | ------------- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) 匹配由 {% data variables.product.company_short %} 所有的公共存储库。{% endif %}{% ifversion ghes or ghec or ghae %} | `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) 匹配你可以访问且包含“test”一词的内部存储库。{% endif %} | `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) 匹配你可以访问且包含“pages”一词的专用存储库。 +| Qualifier | Example +| ------------- | ------------- |{% ifversion fpt or ghes or ghec %} +| `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) matches public repositories owned by {% data variables.product.company_short %}.{% endif %}{% ifversion ghes or ghec or ghae %} +| `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) matches internal repositories that you can access and contain the word "test".{% endif %} +| `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) matches private repositories that you can access and contain the word "pages." {% ifversion fpt or ghec %} -## 基于仓库是否为镜像搜索 +## Search based on whether a repository is a mirror -您可以根据仓库是否为镜像以及托管于其他位置托管来搜索仓库。 有关详细信息,请参阅“[查找为 {% data variables.product.prodname_dotcom %} 上的开放源代码做贡献的方式](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)”。 +You can search repositories based on whether the repositories are mirrors and hosted elsewhere. For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)." -| 限定符 | 示例 +| Qualifier | Example | ------------- | ------------- -| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) 匹配为镜像且包含“GNOME”一词的存储库。 -| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) 匹配不为镜像且包含“GNOME”一词的存储库。 +| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) matches repositories that are mirrors and contain the word "GNOME." +| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) matches repositories that are not mirrors and contain the word "GNOME." {% endif %} -## 基于仓库是否已存档搜索 +## Search based on whether a repository is archived -您可以基于仓库是否已存档来搜索仓库。 有关详细信息,请参阅“[归档存储库](/repositories/archiving-a-github-repository/archiving-repositories)”。 +You can search repositories based on whether or not the repositories are archived. For more information, see "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)." -| 限定符 | 示例 +| Qualifier | Example | ------------- | ------------- -| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) 匹配已存档且包含“GNOME”一词的存储库。 -| `archived:false` | [](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) 匹配未存档且包含“GNOME”一词的存储库。 +| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) matches repositories that are archived and contain the word "GNOME." +| `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) matches repositories that are not archived and contain the word "GNOME." {% ifversion fpt or ghec %} -## 根据带有 `good first issue` 或 `help wanted` 标签的议题数进行搜索 +## Search based on number of issues with `good first issue` or `help wanted` labels -可以使用限定符 `help-wanted-issues:>n` 和 `good-first-issues:>n` 搜索具有最少标有 `help-wanted` 或 `good-first-issue` 的议题的存储库。 有关详细信息,请参阅“[使用标签鼓励对项目做出有益的贡献](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)”。 +You can search for repositories that have a minimum number of issues labeled `help-wanted` or `good-first-issue` with the qualifiers `help-wanted-issues:>n` and `good-first-issues:>n`. For more information, see "[Encouraging helpful contributions to your project with labels](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)." -| 限定符 | 示例 +| Qualifier | Example | ------------- | ------------- -| `good-first-issues:>n` | [ **`good-first-issues:>2 javascript`**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) 匹配具有两个以上标有 `good-first-issue` 的议题且包含“javascript”一词的存储库。 -| `help-wanted-issues:>n`|[**help-wanted-issues:>4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) 匹配具有四个以上标有 `help-wanted` 的议题且包含“React”一词的存储库。 +| `good-first-issues:>n` | [**`good-first-issues:>2 javascript`**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) matches repositories with more than two issues labeled `good-first-issue` and that contain the word "javascript." +| `help-wanted-issues:>n`|[**help-wanted-issues:>4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) matches repositories with more than four issues labeled `help-wanted` and that contain the word "React." -## 基于赞助能力的搜索 +## Search based on ability to sponsor -可以使用 `is:sponsorable` 限定符搜索其所有者可以在 {% data variables.product.prodname_sponsors %} 上获得赞助的存储库。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)”。 +You can search for repositories whose owners can be sponsored on {% data variables.product.prodname_sponsors %} with the `is:sponsorable` qualifier. For more information, see "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." -可以使用 `has:funding-file` 限定符搜索具有融资文件的存储库。 有关详细信息,请参阅“[关于融资文件](/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository#about-funding-files)”。 +You can search for repositories that have a funding file using the `has:funding-file` qualifier. For more information, see "[About FUNDING files](/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository#about-funding-files)." -| 限定符 | 示例 +| Qualifier | Example | ------------- | ------------- -| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Repositories) 匹配其所有者拥有 {% data variables.product.prodname_sponsors %} 配置文件的存储库。 -| `has:funding-file` | [**has:funding-file**](https://github.com/search?q=has%3Afunding-file&type=Repositories) 匹配具有 FUNDING.yml 文件的存储库。 +| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Repositories) matches repositories whose owners have a {% data variables.product.prodname_sponsors %} profile. +| `has:funding-file` | [**has:funding-file**](https://github.com/search?q=has%3Afunding-file&type=Repositories) matches repositories that have a FUNDING.yml file. {% endif %} -## 延伸阅读 +## Further reading -- “[对搜索结果进行排序](/search-github/getting-started-with-searching-on-github/sorting-search-results/)” -- “[在分支中搜索](/search-github/searching-on-github/searching-in-forks)” +- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" +- "[Searching in forks](/search-github/searching-on-github/searching-in-forks)" diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md index 4e6d036ae3..0054f0a88c 100644 --- a/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md +++ b/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md @@ -20,7 +20,7 @@ You can search for issues and pull requests globally across all of {% data varia {% tip %} **Tips:**{% ifversion ghes or ghae %} - - This article contains example searches on the {% data variables.product.prodname_dotcom %}.com website, but you can use the same search filters on {% data variables.product.product_location %}.{% endif %} + - This article contains example searches on the {% data variables.product.prodname_dotcom %}.com website, but you can use the same search filters on {% data variables.location.product_location %}.{% endif %} - For a list of search syntaxes that you can add to any search qualifier to further improve your results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)". - Use quotations around multi-word search terms. For example, if you want to search for issues with the label "In progress," you'd search for `label:"in progress"`. Search is not case sensitive. - {% data reusables.search.search_issues_and_pull_requests_shortcut %} diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md index 7fff95c1c3..b96b7c361a 100644 --- a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md +++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md @@ -83,7 +83,7 @@ If you choose to receive payouts to a bank account, your bank account can be a d ## Enabling two-factor authentication (2FA) on your {% data variables.product.prodname_dotcom %} account -Before your organization can become a sponsored organization, you must enable 2FA for your account on {% data variables.product.product_location %}. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)." +Before your organization can become a sponsored organization, you must enable 2FA for your account on {% data variables.location.product_location %}. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)." ## Submitting your application to {% data variables.product.prodname_dotcom %} for approval diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md index a5929f0a51..77f5cb9377 100644 --- a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md +++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md @@ -1,6 +1,6 @@ --- title: Setting up GitHub Sponsors for your personal account -intro: 'You can become a sponsored developer by joining {% data variables.product.prodname_sponsors %}, completing your sponsored developer profile, creating sponsorship tiers, submitting your bank and tax information, and enabling two-factor authentication for your account on {% data variables.product.product_location %}.' +intro: 'You can become a sponsored developer by joining {% data variables.product.prodname_sponsors %}, completing your sponsored developer profile, creating sponsorship tiers, submitting your bank and tax information, and enabling two-factor authentication for your account on {% data variables.location.product_location %}.' redirect_from: - /articles/becoming-a-sponsored-developer - /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer @@ -84,7 +84,7 @@ If you choose to receive payouts to a bank account, your region of residence and ## Enabling two-factor authentication (2FA) on your {% data variables.product.prodname_dotcom %} account -Before you can become a sponsored developer, you must enable 2FA for your account on {% data variables.product.product_location %}. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)." +Before you can become a sponsored developer, you must enable 2FA for your account on {% data variables.location.product_location %}. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)." ## Submitting your application to {% data variables.product.prodname_dotcom %} for approval diff --git a/translations/zh-CN/content/support/contacting-github-support/providing-data-to-github-support.md b/translations/zh-CN/content/support/contacting-github-support/providing-data-to-github-support.md index 6421b21464..c2460886cc 100644 --- a/translations/zh-CN/content/support/contacting-github-support/providing-data-to-github-support.md +++ b/translations/zh-CN/content/support/contacting-github-support/providing-data-to-github-support.md @@ -1,6 +1,6 @@ --- -title: 向 GitHub 支持提供数据 -intro: '由于 {% data variables.contact.github_support %} 无法访问环境,因此有时需要你提供一些额外的信息。' +title: Providing data to GitHub Support +intro: 'Since {% data variables.contact.github_support %} doesn''t have access to your environment, we sometimes require some additional information from you.' shortTitle: Providing data versions: ghes: '*' @@ -13,22 +13,17 @@ redirect_from: - /admin/enterprise-support/receiving-help-from-github-support/providing-data-to-github-support topics: - Support -ms.openlocfilehash: 56a90a9449a92577d08e068095e5b0dc5b443bb2 -ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/12/2022 -ms.locfileid: '146331910' --- -## 关于诊断文件和支持包 -{% data variables.contact.github_support %} 可能会要求以清理日志文件的形式提供其他数据。 可能需要提供三种类型的日志文件。 +## About diagnostic files and support bundles -诊断文件包含有关 {% data variables.product.prodname_ghe_server %} 实例的设置和环境的信息,支持包包含过去两天的诊断和日志,而扩展支持包还包含诊断和日志,但仅限于过去七天。 +{% data variables.contact.github_support %} may ask you to provide additional data in the form of sanitized log files. There are three types of log file you may be asked to provide. -## 关于日志文件清理 +Diagnostic files contain information about a {% data variables.product.prodname_ghe_server %} instance's settings and environment, support bundles contain diagnostics and logs from the past two days, and extended support bundles also contain diagnostics and logs but from the past seven days. -身份验证令牌、密钥和机密将从支持包或诊断文件中包含的以下日志目录中的日志文件中删除: +## About log file sanitization + +Authentication tokens, keys, and secrets are removed from log files in the following log directories contained within a support bundle or diagnostics file: * `alambic-logs` * `babeld-logs` @@ -44,136 +39,146 @@ ms.locfileid: '146331910' * `render-logs` * `svn-bridge-logs` -## 创建和共享诊断文件 +## Creating and sharing diagnostic files -诊断文件是 {% data variables.product.prodname_ghe_server %} 实例的设置和环境的概述,其中包含: +Diagnostic files are an overview of a {% data variables.product.prodname_ghe_server %} instance's settings and environment that contains: -- 客户端许可信息,包括公司名称、到期日期和用户许可数量 -- 版本号和 SHA -- VM 架构 -- 主机名、私有模式、SSL 设置 -- 加载和处理列表 -- 网络设置 -- 身份验证方法和详情 -- 仓库、用户和其他安装数据的数量 +- Client license information, including company name, expiration date, and number of user licenses +- Version numbers and SHAs +- VM architecture +- Host name, private mode, SSL settings +- Load and process listings +- Network settings +- Authentication method and details +- Number of repositories, users, and other installation data -可以从 {% data variables.enterprise.management_console %} 或通过运行 `ghe-diagnostics` 命令行实用程序下载实例的诊断。 +You can download the diagnostics for your instance from the {% data variables.enterprise.management_console %} or by running the `ghe-diagnostics` command-line utility. -### 从 {% data variables.enterprise.management_console %} 创建诊断文件 +### Creating a diagnostic file from the {% data variables.enterprise.management_console %} -如果您没有随时可用的 SSH 密钥,则可以使用此方法。 +You can use this method if you don't have your SSH key readily available. -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.type-management-console-password %} {% data reusables.enterprise_management_console.support-link %} -5. 单击“下载诊断信息”。 +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.type-management-console-password %} +{% data reusables.enterprise_management_console.support-link %} +5. Click **Download diagnostics info**. -### 使用 SSH 创建诊断文件 +### Creating a diagnostic file using SSH -您无需登录 {% data variables.enterprise.management_console %} 即可使用此方法。 +You can use this method without signing into the {% data variables.enterprise.management_console %}. -使用 [ghe-diagnostics](/enterprise/admin/guides/installation/command-line-utilities#ghe-diagnostics) 命令行实用程序检索实例的诊断。 +Use the [ghe-diagnostics](/enterprise/admin/guides/installation/command-line-utilities#ghe-diagnostics) command-line utility to retrieve the diagnostics for your instance. ```shell -$ ssh -p122 admin@hostname -- 'ghe-diagnostics' > diagnostics.txt +$ ssh -p122 admin@HOSTNAME -- 'ghe-diagnostics' > diagnostics.txt ``` -## 创建和共享支持包 +## Creating and sharing support bundles -您提交支持请求后,我们可能会要求您与我们团队共享支持包。 支持包是一个 gzip 压缩的 tar 存档,其中包含来自您的实例的诊断和重要日志,例如: +After you submit your support request, we may ask you to share a support bundle with our team. The support bundle is a gzip-compressed tar archive that includes diagnostics and important logs from your instance, such as: -- 在对身份验证错误进行故障排查或者配置 LDAP、CAS 或 SAML 时,与身份验证相关的日志可能会十分有用 -- {% data variables.enterprise.management_console %} 日志 -- `github-logs/exceptions.log`:关于站点上遇到的 500 个错误的信息 -- `github-logs/audit.log`{% data variables.product.prodname_ghe_server %} 审核日志 -- `babeld-logs/babeld.log`:Git 代理日志 -- `system-logs/haproxy.log`:HAProxy 日志 -- `elasticsearch-logs/github-enterprise.log`:Elasticsearch 日志 -- `configuration-logs/ghe-config.log`:{% data variables.product.prodname_ghe_server %} 配置日志 -- `collectd/logs/collectd.log`:收集的日志 -- `mail-logs/mail.log`:SMTP 电子邮件传递日志 +- Authentication-related logs that may be helpful when troubleshooting authentication errors, or configuring LDAP, CAS, or SAML +- {% data variables.enterprise.management_console %} log +- `github-logs/exceptions.log`: Information about 500 errors encountered on the site +- `github-logs/audit.log`: {% data variables.product.prodname_ghe_server %} audit logs +- `babeld-logs/babeld.log`: Git proxy logs +- `system-logs/haproxy.log`: HAProxy logs +- `elasticsearch-logs/github-enterprise.log`: Elasticsearch logs +- `configuration-logs/ghe-config.log`: {% data variables.product.prodname_ghe_server %} configuration logs +- `collectd/logs/collectd.log`: Collectd logs +- `mail-logs/mail.log`: SMTP email delivery logs -有关详细信息,请参阅“[关于你企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)”。 +For more information, see "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)." -支持包包含过去两天的日志。 要获取过去七天的日志,您可以下载扩展支持包。 有关详细信息,请参阅“[创建和共享扩展支持包](#creating-and-sharing-extended-support-bundles)”。 +Support bundles include logs from the past two days. To get logs from the past seven days, you can download an extended support bundle. For more information, see "[Creating and sharing extended support bundles](#creating-and-sharing-extended-support-bundles)." {% tip %} -**提示:** 联系 {% data variables.contact.github_support %} 时,你将收到一封确认电子邮件,其中包含票证参考链接。 如果 {% data variables.contact.github_support %} 要求您上传支持包,则可以使用事件单参考链接来上传支持包。 +**Tip:** When you contact {% data variables.contact.github_support %}, you'll be sent a confirmation email that will contain a ticket reference link. If {% data variables.contact.github_support %} asks you to upload a support bundle, you can use the ticket reference link to upload the support bundle. {% endtip %} -### 从 {% data variables.enterprise.management_console %} 创建支持包 +### Creating a support bundle from the {% data variables.enterprise.management_console %} -如果您可以访问基于 web 的 {% data variables.enterprise.management_console %} 并具有出站互联网访问权限,则可以使用下列步骤来创建和共享支持包。 +You can use these steps to create and share a support bundle if you can access the web-based {% data variables.enterprise.management_console %} and have outbound internet access. -{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.type-management-console-password %} {% data reusables.enterprise_management_console.support-link %} -5. 单击“下载支持包”。 -{% data reusables.enterprise_enterprise_support.sign-in-to-support %} {% data reusables.enterprise_enterprise_support.upload-support-bundle %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.type-management-console-password %} +{% data reusables.enterprise_management_console.support-link %} +5. Click **Download support bundle**. +{% data reusables.enterprise_enterprise_support.sign-in-to-support %} +{% data reusables.enterprise_enterprise_support.upload-support-bundle %} -### 使用 SSH 创建支持包 +### Creating a support bundle using SSH -如果您可以通过 SSH 访问 {% data variables.product.product_location %} 并且拥有出站互联网访问权限,则可以使用下列步骤来创建和共享支持包。 +You can use these steps to create and share a support bundle if you have SSH access to {% data variables.location.product_location %} and have outbound internet access. {% data reusables.enterprise_enterprise_support.use_ghe_cluster_support_bundle %} -1. 通过 SSH 下载支持包: +1. Download the support bundle via SSH: ```shell - $ ssh -p 122 admin@hostname -- 'ghe-support-bundle -o' > support-bundle.tgz + $ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -o' > support-bundle.tgz ``` - 有关 `ghe-support-bundle` 命令的详细信息,请参阅“[命令行实用工具](/enterprise/admin/guides/installation/command-line-utilities#ghe-support-bundle)”。 -{% data reusables.enterprise_enterprise_support.sign-in-to-support %} {% data reusables.enterprise_enterprise_support.upload-support-bundle %} + For more information about the `ghe-support-bundle` command, see "[Command-line utilities](/enterprise/admin/guides/installation/command-line-utilities#ghe-support-bundle)". +{% data reusables.enterprise_enterprise_support.sign-in-to-support %} +{% data reusables.enterprise_enterprise_support.upload-support-bundle %} -### 使用您的企业帐户上传支持包 +### Uploading a support bundle using your enterprise account -{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} -3. 在左侧边栏中,单击“企业许可”。 - ![显示企业帐户设置侧边栏中的“企业许可”链接的屏幕截图。](/assets/images/help/enterprises/enterprise-licensing-tab.png) -4. 在“{% data variables.product.prodname_enterprise %} 帮助”下,单击“上传支持包”。 - ![显示“上传支持包链接”的屏幕截图。](/assets/images/enterprise/support/upload-support-bundle.png) -5. 在“Select an enterprise account(选择企业帐户)”下,从下拉菜单选择支持包的相关帐户。 - ![显示下拉菜单的屏幕截图,用于选择支持包的企业帐户。](/assets/images/enterprise/support/support-bundle-account.png) -6. 在“为 {% data variables.contact.enterprise_support %} 上传支持包”下,选择你的支持包,单击“选择文件”,或将你的支持包文件拖到“选择文件” 。 - ![显示“选择文件”按钮的屏幕截,用于上传支持包文件。](/assets/images/enterprise/support/choose-support-bundle-file.png) -7. 单击“上载” 。 +{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} +{% data reusables.enterprise-accounts.settings-tab %} +3. In the left sidebar, click **Enterprise licensing**. + ![Screenshot showing "Enterprise licensing" link in the enterprise account settings sidebar.](/assets/images/help/enterprises/enterprise-licensing-tab.png) +4. Under "{% data variables.product.prodname_enterprise %} Help", click **Upload a support bundle**. + ![Screenshot showing "Upload a support bundle link".](/assets/images/enterprise/support/upload-support-bundle.png) +5. Under "Select an enterprise account", select the support bundle's associated account from the drop-down menu. + ![Screenshot showing the dropdown menu to select the support bundle's enterprise account.](/assets/images/enterprise/support/support-bundle-account.png) +6. Under "Upload a support bundle for {% data variables.contact.enterprise_support %}", to select your support bundle, click **Choose file**, or drag your support bundle file onto **Choose file**. + ![Screenshot showing the "Choose file" button to upload a support bundle file.](/assets/images/enterprise/support/choose-support-bundle-file.png) +7. Click **Upload**. -### 使用 SSH 直接上传支持包 +### Uploading a support bundle directly using SSH -在以下情况下您可以直接将支持包上传到我们的服务器: -- 您可以通过 SSH 访问 {% data variables.product.product_location %}。 -- 通过 TCP 端口 443 的出站 HTTPS 连接允许从 {% data variables.product.product_location %} 连接到 _enterprise-bundles.github.com_ 和 _esbtoolsproduction.blob.core.windows.net_。 +You can directly upload a support bundle to our server if: +- You have SSH access to {% data variables.location.product_location %}. +- Outbound HTTPS connections over TCP port 443 are allowed from {% data variables.location.product_location %} to _enterprise-bundles.github.com_ and _esbtoolsproduction.blob.core.windows.net_. -1. 将包上传到我们的支持包服务器: +1. Upload the bundle to our support bundle server: ```shell - $ ssh -p122 admin@hostname -- 'ghe-support-bundle -u' + $ ssh -p122 admin@HOSTNAME -- 'ghe-support-bundle -u' ``` -## 创建和共享扩展支持包 +## Creating and sharing extended support bundles -支持包包括过去两天的日志,而扩展支持包包括过去七天的日志。 如果 {% data variables.contact.github_support %} 调查的事件发生在两天之前,我们可能会要求您分享扩展支持包。 需要 SSH 权限才能下载扩展包 - 不能从 {% data variables.enterprise.management_console %} 下载扩展包。 +Support bundles include logs from the past two days, while _extended_ support bundles include logs from the past seven days. If the events that {% data variables.contact.github_support %} is investigating occurred more than two days ago, we may ask you to share an extended support bundle. You will need SSH access to download an extended bundle - you cannot download an extended bundle from the {% data variables.enterprise.management_console %}. -为避免体积变得太大,支持包只包含尚未轮换和压缩的日志。 关于 {% data variables.product.prodname_ghe_server %} 上的日志轮换,可针对不同的日志文件设置不同的频率(每日或每周),具体取决于我们期望的日志大小。 +To prevent bundles from becoming too large, bundles only contain logs that haven't been rotated and compressed. Log rotation on {% data variables.product.prodname_ghe_server %} happens at various frequencies (daily or weekly) for different log files, depending on how large we expect the logs to be. -### 使用 SSH 创建扩展支持包 +### Creating an extended support bundle using SSH -如果您可以通过 SSH 访问 {% data variables.product.product_location %} 并有拥有出站互联网访问权限,则可以使用下列步骤来创建和共享扩展支持包。 +You can use these steps to create and share an extended support bundle if you have SSH access to {% data variables.location.product_location %} and you have outbound internet access. -1. 将 `-x` 标记添加到 `ghe-support-bundle` 命令,通过 SSH 下载扩展支持包: +1. Download the extended support bundle via SSH by adding the `-x` flag to the `ghe-support-bundle` command: ```shell - $ ssh -p 122 admin@hostname -- 'ghe-support-bundle -o -x' > support-bundle.tgz + $ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -o -x' > support-bundle.tgz ``` -{% data reusables.enterprise_enterprise_support.sign-in-to-support %} {% data reusables.enterprise_enterprise_support.upload-support-bundle %} +{% data reusables.enterprise_enterprise_support.sign-in-to-support %} +{% data reusables.enterprise_enterprise_support.upload-support-bundle %} -### 使用 SSH 直接上传扩展支持包 +### Uploading an extended support bundle directly using SSH -在以下情况下您可以直接将支持包上传到我们的服务器: -- 您可以通过 SSH 访问 {% data variables.product.product_location %}。 -- 通过 TCP 端口 443 的出站 HTTPS 连接允许从 {% data variables.product.product_location %} 连接到 _enterprise-bundles.github.com_ 和 _esbtoolsproduction.blob.core.windows.net_。 +You can directly upload a support bundle to our server if: +- You have SSH access to {% data variables.location.product_location %}. +- Outbound HTTPS connections over TCP port 443 are allowed from {% data variables.location.product_location %} to _enterprise-bundles.github.com_ and _esbtoolsproduction.blob.core.windows.net_. -1. 将包上传到我们的支持包服务器: +1. Upload the bundle to our support bundle server: ```shell - $ ssh -p122 admin@hostname -- 'ghe-support-bundle -u -x' + $ ssh -p122 admin@HOSTNAME -- 'ghe-support-bundle -u -x' ``` -## 延伸阅读 +## Further reading -- [关于 GitHub 支持](/support/learning-about-github-support/about-github-support) -- [为企业生成运行状况检查](/enterprise-server@latest/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise) +- "[About GitHub Support](/support/learning-about-github-support/about-github-support)" +- "[Generating a Health Check for your enterprise](/enterprise-server@latest/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise)" diff --git a/translations/zh-CN/content/support/learning-about-github-support/about-github-premium-support.md b/translations/zh-CN/content/support/learning-about-github-support/about-github-premium-support.md index 05b36fceb8..6e5bd60a19 100644 --- a/translations/zh-CN/content/support/learning-about-github-support/about-github-premium-support.md +++ b/translations/zh-CN/content/support/learning-about-github-support/about-github-premium-support.md @@ -1,6 +1,6 @@ --- -title: 关于 GitHub 高级支持 -intro: '{% data variables.contact.premium_support %} 是向 {% data variables.product.prodname_enterprise %} 客户提供的一种付费、补充服务。' +title: About GitHub Premium Support +intro: '{% data variables.contact.premium_support %} is a paid, supplemental support offering for {% data variables.product.prodname_enterprise %} customers.' shortTitle: GitHub Premium Support versions: ghec: '*' @@ -20,130 +20,125 @@ redirect_from: - /support/about-github-support/about-github-premium-support topics: - Support -ms.openlocfilehash: 23504e6554b6dc1dbe0f239d2b73006e588711f9 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147052302' --- + {% note %} -**注意:** +**Notes:** -- {% data variables.contact.premium_support %} 的条款自 2021 年 11 月开始生效,如有变动,恕不另行通知。 +- The terms of {% data variables.contact.premium_support %} are subject to change without notice and are effective as of November 2021. - {% data reusables.support.data-protection-and-privacy %} {% endnote %} -## 关于 {% data variables.contact.premium_support %} +## About {% data variables.contact.premium_support %} {% data reusables.support.premium-support-features %} -## {% data variables.contact.premium_support %} 计划 +## {% data variables.contact.premium_support %} plans -有两个 {% data variables.contact.premium_support %} 计划:Premium 和 Premium Plus / {% data variables.product.microsoft_premium_plus_support_plan %}。 +There are two {% data variables.contact.premium_support %} plans: Premium and Premium Plus / {% data variables.product.microsoft_premium_plus_support_plan %}. | | {% data variables.product.premium_support_plan %} | {% data variables.product.premium_plus_support_plan %} | |---|---|------| -| 营业时间 | 全天候 | 全天候 | -| 初始响应时间 |
  • 30 分钟,{% data variables.product.support_ticket_priority_urgent %}
  • 4 小时,{% data variables.product.support_ticket_priority_high %}
|
  • 30 分钟,{% data variables.product.support_ticket_priority_urgent %}
  • 4 小时,{% data variables.product.support_ticket_priority_high %}
| -| 支持通道 |
  • 在线事件单提交
  • 通过回拨请求提供英语电话支持
  • 针对严重问题的屏幕共享请求
|
  • 在线事件单提交
  • 通过回拨请求提供英语电话支持
  • 针对严重问题的屏幕共享请求
| -| 培训 | 高级内容访问权限 |
  • 高级内容访问权限
  • 每年 1 次虚拟培训课程
| -| 拥有支持权利的成员 | 20 | 20 | -| 资源 | 优先事件单处理 |
  • 优先事件单处理
  • 指定客户可靠性工程师
| -| 运行状况检查 | 无限制的自动运行状况检查报告(请参阅“[为企业生成运行状况检查]({% ifversion not ghes%}/enterprise-server@latest{% endif %}/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise)”) |
  • 无限制的自动运行状况检查报告(请参阅“[为企业生成运行状况检查]({% ifversion not ghes%}/enterprise-server@latest{% endif %}/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise)”)
  • 按季度增强的运行状况检查,包括来自客户可靠性工程师的发现、解释和建议(按请求)
| -| 技术咨询小时| 无 | 每月 4 小时 | -| 应用程序升级帮助 | 无 | 按请求 | -| 云规划 | 无 | 按请求 | +| Hours of operation | 24 x 7 | 24 x 7 | +| Initial response time |
  • 30 minutes for {% data variables.product.support_ticket_priority_urgent %}
  • 4 hours for {% data variables.product.support_ticket_priority_high %}
|
  • 30 minutes for {% data variables.product.support_ticket_priority_urgent %}
  • 4 hours for {% data variables.product.support_ticket_priority_high %}
| +| Support channels |
  • Online ticket submission
  • Phone support in English via callback request
  • Screen share request for critical issues
|
  • Online ticket submission
  • Phone support in English via callback request
  • Screen share request for critical issues
| +| Training | Access to premium content |
  • Access to premium content
  • 1 virtual training class per year
| +| Members with support entitlements | 20 | 20 | +| Resources | Priority ticket handling |
  • Priority ticket handling
  • Named Customer Reliability Engineer
| +| Health Checks | Unlimited automated Health Check reports (see "[Generating a Health Check for your enterprise]({% ifversion not ghes%}/enterprise-server@latest{% endif %}/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise)") |
  • Unlimited automated Health Check reports (see "[Generating a Health Check for your enterprise]({% ifversion not ghes%}/enterprise-server@latest{% endif %}/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise)")
  • Quarterly enhanced Health Checks, with findings, interpretations, and recommendations from a Customer Reliability Engineer (by request)
| +| Technical advisory hours| None | 4 hours per month | +| Application upgrade assistance | None | By request | +| Cloud planning | None | By request | {% note %} - **注意:** - - 企业所有人和帐单管理员自动拥有支持权利。 企业所有者可以向企业帐户拥有的组织成员添加支持权利。 有关详细信息,请参阅[管理企业的支持权利](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)。 - - 对于 {% data variables.product.premium_plus_support_plan %},50% 的未使用管理服务时间滚动到下个月,在季度结束时到期。 + **Notes:** + - Enterprise owners and billing managers automatically have a support entitlement. Enterprise owners can add support entitlements to members of organizations owned by their enterprise account. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)." + - For the {% data variables.product.premium_plus_support_plan %}, 50% of unused Managed Services hours roll over to the next month and expire at the end of the quarter. {% endnote %} -## 注册 {% data variables.contact.premium_support %} +## Signing up for {% data variables.contact.premium_support %} -为注册 {% data variables.contact.premium_support %} 或升级计划,可以[联系我们的客户管理团队](https://enterprise.github.com/contact)或拨打 [+1 (877) 448-4820](tel:+1-877-448-4820)。 +To sign up for {% data variables.contact.premium_support %} or upgrade your plan, you can [contact our account management team](https://enterprise.github.com/contact) or call [+1 (877) 448-4820](tel:+1-877-448-4820). -## 支持范围 +## Scope of support {% data reusables.support.scope-of-support %} -## 联系 {% data variables.contact.premium_support %} +## Contacting {% data variables.contact.premium_support %} -{% data variables.contact.premium_support %} 客户可以使用 {% data variables.contact.contact_landing_page_portal %} 以书面(英文)形式报告问题。 +{% data variables.contact.premium_support %} customers can use the {% data variables.contact.contact_landing_page_portal %} to report issues in writing, in English. -## 营业时间 +## Hours of operation -{% data variables.contact.premium_support %} 全天候提供。 如果您在 2018 年 9 月 17 日之前购买了 {% data variables.contact.premium_support %},则节假日期间的支持有限。 有关 {% data variables.contact.premium_support %} 庆祝节假日的详细信息,请参阅“[关于 {% data variables.contact.github_support %}](/enterprise-server@latest/admin/enterprise-support/overview/about-github-enterprise-support)”中的节假日安排。 +{% data variables.contact.premium_support %} is available 24 hours a day, 7 days per week. If you purchased {% data variables.contact.premium_support %} prior to September 17, 2018, support is limited during holidays. For more information on holidays {% data variables.contact.premium_support %} observes, see the holiday schedule at "[About {% data variables.contact.github_support %}](/enterprise-server@latest/admin/enterprise-support/overview/about-github-enterprise-support)." -## 服务等级协议响应时间 +## Service Level Agreement response times -对于您提交的事件单,我们提供全天候支持。 SLA 保证的初始响应时间取决于事件单的优先级。 响应时间从 {% data variables.contact.premium_support %} 确定事件单的优先级开始计算。 响应并不意味着问题已经得到解决。 +For tickets you submit, support is available 24 hours a day, 7 days per week. The initial response time guaranteed by the SLA is dependent on the priority level of the ticket. Response time begins when {% data variables.contact.premium_support %} sets the priority level of the ticket. A response does not mean the issue has been resolved. -| 事件单优先级 | 初始响应时间 | +| Ticket priority level | Initial response time | | --- | ---| -| {% data variables.product.support_ticket_priority_urgent %} | 30 分钟 | -| {% data variables.product.support_ticket_priority_high %} | 4 小时 | +| {% data variables.product.support_ticket_priority_urgent %} | 30 minutes | +| {% data variables.product.support_ticket_priority_high %} | 4 hours | {% data reusables.enterprise_enterprise_support.installing-releases %} -您必须在下单购买 {% data variables.contact.premium_support %} 后的 90 天内,根据适用许可协议的受支持版本部分,安装 {% data variables.product.prodname_ghe_server %} 的最低支持版本。 +You must install the minimum supported version of {% data variables.product.prodname_ghe_server %} pursuant to the Supported Releases section of your applicable license agreement within 90 days of placing an order for {% data variables.contact.premium_support %}. -## 为支持事件单分配优先级 +## Assigning a priority to a support ticket -联系 {% data variables.contact.premium_support %} 时,可为事件单选择以下四种优先级之一:{% data variables.product.support_ticket_priority_urgent %}、{% data variables.product.support_ticket_priority_high %}、{% data variables.product.support_ticket_priority_normal %} 或 {% data variables.product.support_ticket_priority_low %}。 +When you contact {% data variables.contact.premium_support %}, you can choose one of four priorities for the ticket: {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, or {% data variables.product.support_ticket_priority_low %}. -- [{% data variables.product.prodname_ghe_cloud %} 的工单优先级](#ticket-priorities-for-github-enterprise-cloud) -- [{% data variables.product.prodname_ghe_server %} 的工单优先级](#ticket-priorities-for-github-enterprise-server) +- [Ticket priorities for {% data variables.product.prodname_ghe_cloud %}](#ticket-priorities-for-github-enterprise-cloud) +- [Ticket priorities for {% data variables.product.prodname_ghe_server %}](#ticket-priorities-for-github-enterprise-server) -### {% data variables.product.prodname_ghe_cloud %} 的事件单优先级 +### Ticket priorities for {% data variables.product.prodname_ghe_cloud %} -| 优先级 | 说明 | 示例 | +| Priority | Description | Examples | | :---: | --- | --- | -| {% data variables.product.support_ticket_priority_urgent %} | 在 {% data variables.product.prodname_ghe_cloud %} 上的组织或企业的生产工作流程由于严重服务错误或中断而失败,并且该失败直接影响您的业务运营。 |
  • {% data variables.product.prodname_dotcom_the_website %} 上的错误或中断影响您组织或企业所有成员的核心 Git 或 web 应用程序功能
| -| {% data variables.product.support_ticket_priority_high %} | 在 {% data variables.product.prodname_ghe_cloud %} 上的组织或企业的帐户或安全问题对您的业务产生了有限的影响。 |
  • 组织或企业所有者无意中删除了组织
  • 组织或企业成员在提交、议题、拉取请求或议题附件中上传了敏感数据
| -| {% data variables.product.support_ticket_priority_normal %} | 在 {% data variables.product.prodname_ghe_cloud %} 上的组织或企业成员使用 {% data variables.product.prodname_dotcom_the_website %} 时遇到了有限或普通问题,或者您对于自己的组织或企业有一般性疑虑或问题。 |
  • 有关为组织或企业使用 API 和功能的问题
  • 有关 {% data variables.product.company_short %} 提供的组织数据迁移工具的问题
  • 组织或企业的相关功能未按预期工作
  • 有关组织或企业的一般安全问题
| -| {% data variables.product.support_ticket_priority_low %} | 您对于 {% data variables.product.prodname_ghe_cloud %} 上的组织或企业有问题或建议,但并不紧迫,或者该问题不影响团队的生产力。 |
  • 您的组织或企业过度使用资源
  • 请求状态检查
  • 您的组织或企业在使用 Gist、通知、wiki、{% data variables.product.prodname_pages %}、{% data variables.product.prodname_desktop %}、Atom 或其他外围服务或功能方面需要帮助
  • 功能请求
  • 产品反馈
| +| {% data variables.product.support_ticket_priority_urgent %} | Production workflows for your organization or enterprise on {% data variables.product.prodname_ghe_cloud %} are failing due to critical service errors or outages, and the failure directly impacts the operation of your business. |
  • Errors or outages on {% data variables.product.prodname_dotcom_the_website %} affect core Git or web application functionality for all members of your organization or enterprise
| +| {% data variables.product.support_ticket_priority_high %} | Account or security issues with your organization or enterprise on {% data variables.product.prodname_ghe_cloud %} are causing limited impact to your business. |
  • An organization or enterprise owner has unintentionally deleted an organization
  • An organization or enterprise member has uploaded sensitive data in a commit, issue, pull request, or issue attachment
| +| {% data variables.product.support_ticket_priority_normal %} | Members of your organization or enterprise on {% data variables.product.prodname_ghe_cloud %} are experiencing limited or moderate issues with {% data variables.product.prodname_dotcom_the_website %}, or you have general concerns or questions about your organization or enterprise. |
  • Questions about using APIs and features for your organization or enterprise
  • Issues with tools for organization data migration that {% data variables.product.company_short %} provides
  • Features related to your organization or enterprise not working as expected
  • General security questions about your organization or enterprise
| +| {% data variables.product.support_ticket_priority_low %} | You have a question or suggestion about your organization or enterprise on {% data variables.product.prodname_ghe_cloud %} that is not time-sensitive, or does not otherwise block the productivity of your team. |
  • Excessive resource usage for your organization or enterprise
  • Requests for health checks
  • Help with using Gists, notifications, wikis, {% data variables.product.prodname_pages %}, {% data variables.product.prodname_desktop %}, or other peripheral services or features with your organization or enterprise
  • Feature requests
  • Product feedback
| -### {% data variables.product.prodname_ghe_server %} 的事件单优先级 +### Ticket priorities for {% data variables.product.prodname_ghe_server %} {% data reusables.support.ghes-priorities %} -## 解决和关闭支持事件单 +## Resolving and closing support tickets -{% data variables.contact.premium_support %} 在提供解释、建议、使用说明、变通方法或向您推荐可解决问题的 {% data variables.product.prodname_ghe_server %} 版本后,可能认为事件单已解决。 +{% data variables.contact.premium_support %} may consider a ticket solved after providing an explanation, recommendation, usage instructions, workaround instructions, or by advising you of an available {% data variables.product.prodname_ghe_server %} release that addresses the issue. -如果您使用自定义或不支持的插件、模块或自定义代码,{% data variables.contact.premium_support %} 可能要求您在尝试解决问题时删除不支持的插件、模块或代码。 如果在不受支持的插件、模块或自定义代码删除后问题得以解决,{% data variables.contact.premium_support %} 可能认为事件单已解决。 +If you use a custom or unsupported plug-in, module, or custom code, {% data variables.contact.premium_support %} may ask you to remove the unsupported plug-in, module, or code while attempting to resolve the issue. If the problem is fixed when the unsupported plug-in, module, or custom code is removed, {% data variables.contact.premium_support %} may consider the ticket solved. -如果事件单超出支持范围,或者多次联系您但未获回复,{% data variables.contact.premium_support %} 可能会关闭事件单。 如果 {% data variables.contact.premium_support %} 因为未获回复而关闭事件单,您可以请求 {% data variables.contact.premium_support %} 重新开启事件单。 +{% data variables.contact.premium_support %} may close a ticket if the ticket is outside the scope of support or if multiple attempts to contact you have gone unanswered. If {% data variables.contact.premium_support %} closes a ticket due to lack of response, you can request that {% data variables.contact.premium_support %} reopen the ticket. -## 支持事件单未响应时获取积分 +## Receiving credits for missed responses to support tickets -如果您在 {% data variables.product.company_short %} 财年的特定季度中,有超过四个事件单没有在保证的响应时间内收到初始响应,您将有资格获得积分。 为遵守 SLA,{% data variables.product.company_short %} 将以现金退还 20% 的季度 {% data variables.contact.premium_support %}费用。 为收到退款,您必须提交信用请求。 +If you don't receive an initial response within the guaranteed response time to more than four tickets in a given quarter based on {% data variables.product.company_short %}'s fiscal year, you're eligible for a credit. To honor the SLA, {% data variables.product.company_short %} will refund 20% of the quarterly {% data variables.contact.premium_support %} fee in cash. To receive the refund, you must submit a credit request. -积分申请必须在 {% data variables.contact.premium_support %} 未在指定响应时间内响应事件单的季度结束后的 30 天内提出。 如果过了相应的最后期限,则不受理信用申请。 在相应的最后期限过后,即表示您已放弃为合格的信用要求退款。 +The credit request must be made within 30 days of the end of the quarter during which {% data variables.contact.premium_support %} did not respond to your tickets within the designated response time. Credit requests will not be honored if the respective deadline has passed. Once the respective deadline passes, you have waived the ability to claim a refund for the qualified credit. -为收到退款,必须向 提交完成的信用申请。 要获得资格,信用申请必须: -- 从与在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的帐户关联的电子邮件地址发送 -- 在四个合格信用发生的季度结束后 30 天内由 {% data variables.product.company_short %} 接收 -- 在主题行中包含“积分申请” +To receive a refund, you must submit a completed credit request to . To be eligible, the credit request must: +- Be sent from an email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} +- Be received by {% data variables.product.company_short %} by the end of the 30th day after the quarter in which the four qualifying credits occurred +- Include "Credit Request" in the subject line -以下信息必须包含在信用申请中: -- 日期(日期必须基于 {% data variables.product.company_short %} 的财政年度的季度结束 [1 月 31 日、4 月 30 日、7 月 31 日或 10月 31 日] 后 30 天内。) -- 客户联系(必须同时指定姓名和电子邮件地址。) -- 客户地址 -- 合格信用(必须提供每个合格信用的日期和关联的工单编号。){% ifversion fpt or ghec %} -- {% data variables.product.prodname_ghe_cloud %} 组织的名称{% endif %} -- 工单编号 +The following information **must be included** in your credit request: +- **Date** (The date must be within 30 days after the quarter based on {% data variables.product.company_short %}’s fiscal year end in which the claims occurred [January 31, April 30, July 31, or October 31].) +- **Customer contact** (You must specify both name and email address.) +- **Customer address** +- **Qualifying credits** (You must provide the date of each qualifying credit and the associated ticket number.){% ifversion fpt or ghec %} +- **Name of {% data variables.product.prodname_ghe_cloud %} organization**{% endif %} +- **Ticket numbers** -## 访问高级内容 +## Accessing premium content -可以登录到 {% data variables.contact.contact_landing_page_portal %} 访问高级内容。 +You can access premium content by signing in to the {% data variables.contact.contact_landing_page_portal %}. diff --git a/translations/zh-CN/data/learning-tracks/admin.yml b/translations/zh-CN/data/learning-tracks/admin.yml index b22fecb9ac..6c84460f88 100644 --- a/translations/zh-CN/data/learning-tracks/admin.yml +++ b/translations/zh-CN/data/learning-tracks/admin.yml @@ -1,6 +1,6 @@ get_started_with_github_ae: - title: '{% data variables.product.prodname_ghe_managed %} 入门' - description: '了解 {% data variables.product.prodname_ghe_managed %} 并完成新企业的初始配置。' + title: 'Get started with {% data variables.product.prodname_ghe_managed %}' + description: 'Learn about {% data variables.product.prodname_ghe_managed %} and complete the initial configuration of a new enterprise.' featured_track: true versions: ghae: '*' @@ -13,8 +13,8 @@ get_started_with_github_ae: - /admin/github-actions/getting-started-with-github-actions-for-github-ae deploy_an_instance: - title: '部署实例' - description: '在你选择的平台上安装 {% data variables.product.prodname_ghe_server %} 并配置 SAML 身份验证。' + title: 'Deploy an instance' + description: 'Install {% data variables.product.prodname_ghe_server %} on your platform of choice and configure SAML authentication.' featured_track: true versions: ghes: '*' @@ -27,8 +27,8 @@ deploy_an_instance: - /admin/configuration/site-admin-dashboard upgrade_your_instance: - title: '升级实例' - description: '分阶段测试升级,通知用户维护,并升级实例以获取最新功能和安全更新。' + title: 'Upgrade your instance' + description: 'Test upgrades in staging, notify users of maintenance, and upgrade your instance for the latest features and security updates.' versions: ghes: '*' guides: @@ -40,8 +40,8 @@ upgrade_your_instance: - /admin/enterprise-management/upgrading-github-enterprise-server adopting_github_actions_for_your_enterprise_ghec: - title: '为企业采用 GitHub Actions' - description: '了解如何在企业中计划和实现 {% data variables.product.prodname_actions %} 的推出。' + title: 'Adopt GitHub Actions for your enterprise' + description: 'Learn how to plan and implement a rollout of {% data variables.product.prodname_actions %} in your enterprise.' versions: ghec: '*' guides: @@ -54,8 +54,8 @@ adopting_github_actions_for_your_enterprise_ghec: - /billing/managing-billing-for-github-actions/about-billing-for-github-actions adopting_github_actions_for_your_enterprise_ghes_and_ghae: - title: '为企业采用 GitHub Actions' - description: '了解如何在企业中计划和实现 {% data variables.product.prodname_actions %} 的推出。' + title: 'Adopt GitHub Actions for your enterprise' + description: 'Learn how to plan and implement a rollout of {% data variables.product.prodname_actions %} in your enterprise.' versions: ghes: '*' ghae: '*' @@ -71,8 +71,8 @@ adopting_github_actions_for_your_enterprise_ghes_and_ghae: - /billing/managing-billing-for-github-actions/about-billing-for-github-actions increase_fault_tolerance: - title: '提高实例的容错能力' - description: "备份开发者代码并配置高可用性 (HA),以确保环境中 {% data variables.product.prodname_ghe_server %} 的可靠性。" + title: 'Increase the fault tolerance of your instance' + description: "Back up your developers' code and configure high availability (HA) to ensure the reliability of {% data variables.product.prodname_ghe_server %} in your environment." versions: ghes: '*' guides: @@ -83,8 +83,8 @@ increase_fault_tolerance: - /admin/configuration/using-github-enterprise-server-with-a-load-balancer improve_security_of_your_instance: - title: '提高实例的安全性' - description: "查看网络配置和安全功能,并强化运行 {% data variables.product.prodname_ghe_server %} 的实例,以保护你的企业数据。" + title: 'Improve the security of your instance' + description: "Review network configuration and security features, and harden the instance running {% data variables.product.prodname_ghe_server %} to protect your enterprise's data." versions: ghes: '*' guides: @@ -99,8 +99,8 @@ improve_security_of_your_instance: - /admin/user-management/promoting-or-demoting-a-site-administrator configure_github_actions: - title: '配置 {% data variables.product.prodname_actions %}' - description: '开发者可以使用 {% data variables.product.prodname_actions %} 为 {% data variables.product.product_location %} 创建、自动化、自定义和执行功能强大的软件开发工作流。' + title: 'Configure {% data variables.product.prodname_actions %}' + description: 'Allow your developers to create, automate, customize, and execute powerful software development workflows for {% data variables.location.product_location %} with {% data variables.product.prodname_actions %}.' versions: ghes: '*' guides: @@ -112,8 +112,8 @@ configure_github_actions: - /admin/github-actions/using-a-staging-environment configure_github_advanced_security: - title: '配置 {% data variables.product.prodname_GH_advanced_security %}' - description: "通过 {% data variables.product.prodname_GH_advanced_security %} 提高开发者代码的质量和安全性。" + title: 'Configure {% data variables.product.prodname_GH_advanced_security %}' + description: "Improve the quality and security of your developers' code with {% data variables.product.prodname_GH_advanced_security %}." versions: ghes: '*' guides: @@ -125,8 +125,8 @@ configure_github_advanced_security: - /admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise get_started_with_your_enterprise_account: - title: '开始使用企业帐户' - description: '开始使用企业帐户,在 {% data variables.product.product_name %} 上集中管理多个组织。' + title: 'Get started with your enterprise account' + description: 'Get started with your enterprise account to centrally manage multiple organizations on {% data variables.product.product_name %}.' versions: ghes: '*' ghec: '*' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/0-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/0-rc1.yml index 75612a7f7f..520bfd612f 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/0-rc1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/0-rc1.yml @@ -1,20 +1,20 @@ date: '2021-05-06' release_candidate: true deprecated: true -intro: "如果 {% data variables.product.product_location %} 正在运行候选发布版本,则无法使用热补丁升级。建议仅在测试环境中运行候选发布版本。" +intro: If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. sections: security_fixes: - - '**中** 在某些情况下,从团队或组织中删除的用户可以保留对现有拉取请求打开的分支的写入权限。' - - 包已更新到最新的安全版本。 + - '**MEDIUM** Under certain circumstances, users who were removed from a team or organization could retain write access to branches they had existing pull requests opened for.' + - Packages have been updated to the latest security versions. bugs: - - '按计划执行的清理作业在具有很大的 `check_annotations` 表格的实例中会造成性能降级。' + - 'A scheduled cleanup job can cause performance to degrade on an instance with a very large `check_annotations` table.' changes: - - 超过 4 个月的检查注释将存档。 - - '`firstPatchedVersion` 字段现在可以在 GraphQL API 中的 `SecurityVulability` 对象上使用。' + - Check annotations older than 4 months will be archived. + - 'The `firstPatchedVersion` field is now available on `SecurityVulnerability` objects in the GraphQL API.' known_issues: - - GitHub 包 npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分,我们继续拥有返回时间值所需的所有数据,并将在我们解决现有性能问题后恢复返回这个值。 - - 在新建的没有任何用户的 GitHub Enterprise Server 上,攻击者可以创建第一个管理员用户。 - - 在升级期间不会维护自定义防火墙规则。 - - "Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。" - - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接,则议题无法关闭。 - - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后,私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。 + - The GitHub Packages npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. + - On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. + - Custom firewall rules are not maintained during an upgrade. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. + - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/0-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/0-rc1.yml index 0213319af5..634366e5e1 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/0-rc1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/0-rc1.yml @@ -1,7 +1,7 @@ date: '2021-09-09' release_candidate: true deprecated: true -intro: If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. +intro: If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. sections: features: - heading: Custom patterns for secret scanning @@ -92,7 +92,7 @@ sections: - When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history. # https://github.com/github/releases/issues/1254 - - When a submodule is defined with a relative path in {% data variables.product.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. + - When a submodule is defined with a relative path in {% data variables.location.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. # https://github.com/github/releases/issues/1250 - The web UI can now be used to synchronize an out-of-date branch of a fork with the fork's upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)." diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/0.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/0.yml index ba34f7a61d..708b798394 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/0.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/0.yml @@ -90,7 +90,7 @@ sections: - When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history. # https://github.com/github/releases/issues/1254 - - When a submodule is defined with a relative path in {% data variables.product.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. + - When a submodule is defined with a relative path in {% data variables.location.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. # https://github.com/github/releases/issues/1250 - The web UI can now be used to synchronize an out-of-date branch of a fork with the fork's upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)." diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/0-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/0-rc1.yml index eaa5046942..840bd35324 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/0-rc1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/0-rc1.yml @@ -4,7 +4,7 @@ deprecated: true intro: | {% note %} - **Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. + **Note:** If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. {% endnote %} @@ -31,7 +31,7 @@ sections: - | {% data variables.product.prodname_actions %} now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier. - Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, ephemeral runners are automatically unregistered from {% data variables.product.product_location %}, allowing you to perform any post-job management. + Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, ephemeral runners are automatically unregistered from {% data variables.location.product_location %}, allowing you to perform any post-job management. You can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to {% data variables.product.prodname_actions %} job requests. @@ -289,7 +289,7 @@ sections: - | Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are now deprecated in {% data variables.product.prodname_ghe_server %} 3.3. - Any repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated. + Any repositories that were already present and active on {% data variables.location.product_location %} running version 3.1 or 3.2 will have been automatically updated. Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/0.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/0.yml index f321bb7caa..5aec8eca3f 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/0.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/0.yml @@ -22,7 +22,7 @@ sections: - | {% data variables.product.prodname_actions %} now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier. - Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, ephemeral runners are automatically unregistered from {% data variables.product.product_location %}, allowing you to perform any post-job management. + Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, ephemeral runners are automatically unregistered from {% data variables.location.product_location %}, allowing you to perform any post-job management. You can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to {% data variables.product.prodname_actions %} job requests. @@ -289,7 +289,7 @@ sections: - | Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are now deprecated in {% data variables.product.prodname_ghe_server %} 3.3. - Any repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated. + Any repositories that were already present and active on {% data variables.location.product_location %} running version 3.1 or 3.2 will have been automatically updated. Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-4/0-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-4/0-rc1.yml index f49bb7d8e3..534c6d7f00 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-4/0-rc1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-4/0-rc1.yml @@ -4,7 +4,7 @@ deprecated: true intro: | {% note %} - **Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. + **Note:** If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. {% endnote %} @@ -276,7 +276,7 @@ sections: - | Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards. - Any repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated. + Any repositories that were already present and active on {% data variables.location.product_location %} running version 3.1 or 3.2 will have been automatically updated. Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-4/0.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-4/0.yml index 0ff37f4058..8f3df3ef18 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-4/0.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-4/0.yml @@ -37,7 +37,7 @@ sections: notes: # https://github.com/github/releases/issues/1946 - | - If you use SAML authentication for {% data variables.product.prodname_ghe_server %}, you can now configure encrypted assertions from your IdP to improve security. Encrypted assertions add an additional layer of encryption when your IdP transmits information to {% data variables.product.product_location %}. For more information, see "[Using SAML](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml#enabling-encrypted-assertions)." + If you use SAML authentication for {% data variables.product.prodname_ghe_server %}, you can now configure encrypted assertions from your IdP to improve security. Encrypted assertions add an additional layer of encryption when your IdP transmits information to {% data variables.location.product_location %}. For more information, see "[Using SAML](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml#enabling-encrypted-assertions)." - heading: Edit files within pull requests in GitHub Mobile for iOS notes: @@ -298,7 +298,7 @@ sections: - | Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards. - Any repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated. + Any repositories that were already present and active on {% data variables.location.product_location %} running version 3.1 or 3.2 will have been automatically updated. Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml index 85b5feeb65..c1e26d10e7 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml @@ -95,7 +95,7 @@ sections: - | Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards. - Any repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated. + Any repositories that were already present and active on {% data variables.location.product_location %} running version 3.1 or 3.2 will have been automatically updated. Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-4/2.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-4/2.yml index be2036c2f4..a6e465aae2 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-4/2.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-4/2.yml @@ -71,7 +71,7 @@ sections: - | Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards. - Any repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated. + Any repositories that were already present and active on {% data variables.location.product_location %} running version 3.1 or 3.2 will have been automatically updated. Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml index 378a8b6706..527354bda7 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml @@ -4,7 +4,7 @@ deprecated: true intro: | {% note %} - **Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. + **Note:** If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. {% endnote %} diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-6/0-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-6/0-rc1.yml index fc7707911b..d4c97c5267 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-6/0-rc1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-6/0-rc1.yml @@ -4,7 +4,7 @@ deprecated: true intro: | {% note %} - **Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend that you only run release candidates in a test environment. + **Note:** If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend that you only run release candidates in a test environment. {% endnote %} diff --git a/translations/zh-CN/data/reusables/actions/about-actions-for-enterprises.md b/translations/zh-CN/data/reusables/actions/about-actions-for-enterprises.md index ce6ff86813..ff8b663350 100644 --- a/translations/zh-CN/data/reusables/actions/about-actions-for-enterprises.md +++ b/translations/zh-CN/data/reusables/actions/about-actions-for-enterprises.md @@ -1 +1 @@ -{% data variables.product.prodname_actions %} allows {% ifversion ghec or ghae %}members of your enterprise{% elsif ghes %}people who use {% data variables.product.product_location %}{% endif %} to improve productivity by automating every phase of the software development workflow. +{% data variables.product.prodname_actions %} allows {% ifversion ghec or ghae %}members of your enterprise{% elsif ghes %}people who use {% data variables.location.product_location %}{% endif %} to improve productivity by automating every phase of the software development workflow. diff --git a/translations/zh-CN/data/reusables/actions/cache-default-size.md b/translations/zh-CN/data/reusables/actions/cache-default-size.md index 22ecaa2cb1..c79aef489f 100644 --- a/translations/zh-CN/data/reusables/actions/cache-default-size.md +++ b/translations/zh-CN/data/reusables/actions/cache-default-size.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: ab5272155710feedd08dd5b5e4e0f84eacc36694 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147067408" ---- -默认情况下,{% data variables.product.prodname_actions %} 在 {% data variables.product.product_location %} 的外部存储上使用的总缓存存储限制为每个存储库最多 10 GB,可以为存储库设置的最大允许大小为 25 GB。 +By default, the total cache storage that {% data variables.product.prodname_actions %} uses on the external storage for {% data variables.location.product_location %} is limited to a maximum of 10 GB per repository, and the maximum allowed size that can be set for a repository is 25 GB. diff --git a/translations/zh-CN/data/reusables/actions/disabling-github-actions.md b/translations/zh-CN/data/reusables/actions/disabling-github-actions.md index daa5542888..ef2c62fe2f 100644 --- a/translations/zh-CN/data/reusables/actions/disabling-github-actions.md +++ b/translations/zh-CN/data/reusables/actions/disabling-github-actions.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 3812d31ab730736a7af4ae38c347325f28aeffba -ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147877170" ---- -默认情况下,{% ifversion ghes or ghae %}在 {% data variables.product.product_location %} 上启用 {% data variables.product.prodname_actions %} 之后,它{% elsif fpt or ghec %}{% data variables.product.prodname_actions %}{% endif %}会在所有存储库和组织上启用。 可以选择禁用 {% data variables.product.prodname_actions %} 或将其限制为{% ifversion ghec or ghes or ghae %}企业{% else %}组织{% endif %}中的操作 {% ifversion actions-workflow-policy %}和可重用工作流{% endif %}。 +By default, {% ifversion ghes or ghae %}after {% data variables.product.prodname_actions %} is enabled on {% data variables.location.product_location %}, it{% elsif fpt or ghec %}{% data variables.product.prodname_actions %}{% endif %} is enabled on all repositories and organizations. You can choose to disable {% data variables.product.prodname_actions %} or limit it to actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %} in your {% ifversion ghec or ghes or ghae %}enterprise{% else %}organization{% 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 29433f58a1..b0541a2c44 100644 --- a/translations/zh-CN/data/reusables/actions/enterprise-common-prereqs.md +++ b/translations/zh-CN/data/reusables/actions/enterprise-common-prereqs.md @@ -1,17 +1,9 @@ ---- -ms.openlocfilehash: 9c9f3713944a20dcdac639249d10c0ab8a4f7baf -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145098528" ---- -* 查看 {% 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#review-hardware-considerations)”。 -* 必须为 {% data variables.product.product_location %} 的域配置 TLS。 有关详细信息,请参阅“[配置 TLS](/admin/configuration/configuring-tls)”。 +* 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.location.product_location %}'s domain. For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)." {% note %} - **注意:** {% data reusables.actions.enterprise-self-signed-cert %} + **Note:** {% data reusables.actions.enterprise-self-signed-cert %} {% endnote %} * {% data reusables.actions.enterprise-http-proxy %} diff --git a/translations/zh-CN/data/reusables/actions/enterprise-http-proxy.md b/translations/zh-CN/data/reusables/actions/enterprise-http-proxy.md index e2dc215a84..62d80c0c34 100644 --- a/translations/zh-CN/data/reusables/actions/enterprise-http-proxy.md +++ b/translations/zh-CN/data/reusables/actions/enterprise-http-proxy.md @@ -1,13 +1,5 @@ ---- -ms.openlocfilehash: c61e071aa06bda0d31a1c4578dfe78addb55867e -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147167377" ---- -如果在 {% data variables.product.product_location %} 上配置了 HTTP 代理服务器: - - 必须将 `localhost` 和 `127.0.0.1` 添加到“HTTP 代理排除”列表。 - - 如果 BYOS 桶不可路由,则还必须将桶的 URL 添加到排除列表。 +If you have an **HTTP Proxy Server** configured on {% data variables.location.product_location %}: + - You must add `localhost` and `127.0.0.1` to the **HTTP Proxy Exclusion** list. + - If the BYOS bucket is not routable, then you must also add the bucket's URL to the exclusion list. - 有关更改代理设置的详细信息,请参阅“[配置出站 Web 代理服务器](/admin/configuration/configuring-an-outbound-web-proxy-server)”。 \ No newline at end of file + For more information on changing your proxy settings, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-an-outbound-web-proxy-server)." \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/actions/enterprise-marketplace-actions.md b/translations/zh-CN/data/reusables/actions/enterprise-marketplace-actions.md index bef9aa2b42..44dd8a398e 100644 --- a/translations/zh-CN/data/reusables/actions/enterprise-marketplace-actions.md +++ b/translations/zh-CN/data/reusables/actions/enterprise-marketplace-actions.md @@ -1,16 +1,8 @@ ---- -ms.openlocfilehash: 5e5e40bc161c7779bdfc27931921963c5bf74fc5 -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145098515" ---- {% ifversion ghes %} {% note %} -注意:{% data variables.product.product_location %} 上的 {% data variables.product.prodname_actions %} 对 {% data variables.product.prodname_dotcom_the_website %} 或 {% data variables.product.prodname_marketplace %} 上的操作具有有限的访问权限。 有关详细信息,请参阅“[管理对 {% data variables.product.prodname_dotcom_the_website %} 上操作的访问](/enterprise/admin/github-actions/managing-access-to-actions-from-githubcom)”并联系 {% data variables.product.prodname_enterprise %} 站点管理员。 +**Note:** {% data variables.product.prodname_actions %} on {% data variables.location.product_location %} may have limited access to actions on {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_marketplace %}. For more information, see "[Managing access to actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/managing-access-to-actions-from-githubcom)" and contact your {% data variables.product.prodname_enterprise %} site administrator. {% endnote %} diff --git a/translations/zh-CN/data/reusables/actions/enterprise-postinstall-nextsteps.md b/translations/zh-CN/data/reusables/actions/enterprise-postinstall-nextsteps.md index b26ef071b8..f241306500 100644 --- a/translations/zh-CN/data/reusables/actions/enterprise-postinstall-nextsteps.md +++ b/translations/zh-CN/data/reusables/actions/enterprise-postinstall-nextsteps.md @@ -1,11 +1,3 @@ ---- -ms.openlocfilehash: d1d2813fed8f4ebc9e76856fb6477ab58b3c3657 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145098512" ---- -### 后续步骤 +### Next steps -配置运行成功完成后, {% data variables.product.prodname_actions %} 将在 {% data variables.product.product_location %} 上启用。 有关后续步骤,例如管理 {% data variables.product.prodname_actions %} 访问权限和添加自托管运行器,请返回到“[{% data variables.product.prodname_ghe_server %} 的 {% data variables.product.prodname_actions %} 使用入门](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#enabling-github-actions-with-your-storage-provider)”。 +After the configuration run has successfully completed, {% data variables.product.prodname_actions %} will be enabled on {% data variables.location.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)." diff --git a/translations/zh-CN/data/reusables/actions/github-connect-resolution.md b/translations/zh-CN/data/reusables/actions/github-connect-resolution.md index f8921e72f6..54fa9eebde 100644 --- a/translations/zh-CN/data/reusables/actions/github-connect-resolution.md +++ b/translations/zh-CN/data/reusables/actions/github-connect-resolution.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 1e9105d419c42c1210ebe51b785ef3c36df094f8 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147066080" ---- -当工作流通过引用存储操作的存储库来使用操作时,{% data variables.product.prodname_actions %} 将首先尝试在 {% data variables.product.product_location %} 上查找存储库。 如果 {% data variables.product.product_location %} 上不存在存储库,并且你启用了对 {% data variables.product.prodname_dotcom_the_website %} 的自动访问,{% data variables.product.prodname_actions %} 将尝试在 {% data variables.product.prodname_dotcom_the_website %} 上查找存储库。 +When a workflow uses an action by referencing the repository where the action is stored, {% data variables.product.prodname_actions %} will first try to find the repository on {% data variables.location.product_location %}. If the repository does not exist on {% data variables.location.product_location %}, and if you have automatic access to {% data variables.product.prodname_dotcom_the_website %} enabled, {% data variables.product.prodname_actions %} will try to find the repository on {% data variables.product.prodname_dotcom_the_website %}. diff --git a/translations/zh-CN/data/reusables/actions/self-hosted-runner-management-permissions-required.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-management-permissions-required.md index 85d8a36e54..9c3f42102f 100644 --- a/translations/zh-CN/data/reusables/actions/self-hosted-runner-management-permissions-required.md +++ b/translations/zh-CN/data/reusables/actions/self-hosted-runner-management-permissions-required.md @@ -1,17 +1,9 @@ ---- -ms.openlocfilehash: 324332325762999d6daaf4241ec0f9e291ce98a8 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145065861" ---- -自托管运行器可位于存储库、组织或 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} 上的企业帐户设置{% elsif ghes or ghae %} {% data variables.product.product_location %} 上的企业设置{% endif %}中。 要管理自托管运行器,您必须拥有以下权限,具体取决于添加自托管运行器的位置: -- **用户存储库**:你必须是存储库所有者。 -- **组织**:你必须是组织所有者。 -- **组织存储库**:你必须是组织所有者,或者拥有对存储库的管理员访问权限。 +A self-hosted runner can be located in either your repository, organization, or {% ifversion fpt or ghec %}enterprise account settings on {% data variables.product.prodname_dotcom %}{% elsif ghes or ghae %} enterprise settings on {% data variables.location.product_location %}{% endif %}. To manage a self-hosted runner, you must have the following permissions, depending on where the self-hosted runner was added: +- **User repository**: You must be the repository owner. +- **Organization**: You must be an organization owner. +- **Organization repository**: You must be an organization owner, or have admin access to the repository. {% ifversion ghec %} -- **企业帐户**:你必须是企业所有者。 +- **Enterprise account**: You must be an enterprise owner. {% elsif ghes or ghae %} -- **企业**:你必须是 {% data variables.product.prodname_enterprise %} 站点管理员。 +- **Enterprise**: You must be a {% data variables.product.prodname_enterprise %} site administrator. {% endif %} diff --git a/translations/zh-CN/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md index 2ad9b4d51c..a648712470 100644 --- a/translations/zh-CN/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md +++ b/translations/zh-CN/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: f5a11de0003ae27a2b49233ad5ef8218423b50d2 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147063936" ---- -若要使用 {% data variables.product.prodname_dotcom_the_website %} 中的操作,{% ifversion ghes %}{% data variables.product.product_location %} 和{% endif %}自托管运行器必须能够与 {% data variables.product.prodname_dotcom_the_website %} 建立出站连接。 不需要来自 {% data variables.product.prodname_dotcom_the_website %} 的入站连接。 有关详细信息, 有关详细信息,请参阅[关于自承载运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-betweens-self-hosted-runners-and-githubcom)。 +To use actions from {% data variables.product.prodname_dotcom_the_website %},{% ifversion ghes %} both {% data variables.location.product_location %} and{% endif %} your self-hosted runners must be able to make outbound connections to {% data variables.product.prodname_dotcom_the_website %}. No inbound connections from {% data variables.product.prodname_dotcom_the_website %} are required. For more information. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-betweens-self-hosted-runners-and-githubcom)." diff --git a/translations/zh-CN/data/reusables/actions/self-hosted-runner-ports-protocols.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-ports-protocols.md index f8dafa6872..862638d843 100644 --- a/translations/zh-CN/data/reusables/actions/self-hosted-runner-ports-protocols.md +++ b/translations/zh-CN/data/reusables/actions/self-hosted-runner-ports-protocols.md @@ -1,9 +1,3 @@ ---- -ms.openlocfilehash: 51b563029cedae82f02da31a5d6473274efb8218 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145084827" ---- -{% ifversion ghes or ghae %} 自托管运行器和 {% data variables.product.product_name %} 通过 {% ifversion ghes %} HTTP(端口 80)或 {% endif %} HTTPS(端口 443)建立连接。 {% ifversion ghes %} 若要确保通过 HTTPS 进行连接,请为 {% data variables.product.product_location %} 配置 TLS。 有关详细信息,请参阅“[配置 TLS](/admin/configuration/configuring-network-settings/configuring-tls)”。{% endif %} {% endif %} +{% ifversion ghes or ghae %} +The connection between self-hosted runners and {% data variables.product.product_name %} is over {% ifversion ghes %}HTTP (port 80) or {% endif %}HTTPS (port 443). {% ifversion ghes %}To ensure connectivity over HTTPS, configure TLS for {% data variables.location.product_location %}. For more information, see "[Configuring TLS](/admin/configuration/configuring-network-settings/configuring-tls)."{% endif %} +{% endif %} diff --git a/translations/zh-CN/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md b/translations/zh-CN/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md index 9256498794..1290be8b1c 100644 --- a/translations/zh-CN/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md +++ b/translations/zh-CN/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 48e8bec26155fe30e20642892cad797e869d69bc -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147065040" ---- -如果使用临时运行器并禁用了自动更新,则在升级 {% data variables.product.product_location %} 之前,应首先将自托管运行器升级到升级后的实例将运行的运行器应用程序版本。 在升级临时运行器之前升级 {% data variables.product.product_location %} 可能会导致运行器脱机。 有关详细信息,请参阅“[升级 {% data variables.product.product_name %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)”。 +If you use ephemeral runners and have disabled automatic updates, before you upgrade {% data variables.location.product_location %}, you should first upgrade your self-hosted runners to the version of the runner application that your upgraded instance will run. Upgrading {% data variables.location.product_location %} before you upgrade ephemeral runners may result in your runners going offline. For more information, see "[Upgrading {% data variables.product.product_name %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." diff --git a/translations/zh-CN/data/reusables/actions/workflow-template-overview.md b/translations/zh-CN/data/reusables/actions/workflow-template-overview.md index 24446416ca..bc08e3019b 100644 --- a/translations/zh-CN/data/reusables/actions/workflow-template-overview.md +++ b/translations/zh-CN/data/reusables/actions/workflow-template-overview.md @@ -1,3 +1,3 @@ {% data variables.product.prodname_dotcom %} provides preconfigured starter workflows that you can customize to create your own continuous integration workflow. {% data variables.product.product_name %} analyzes your code and shows you CI starter workflows that might be useful for your repository. For example, if your repository contains Node.js code, you'll see suggestions for Node.js projects. You can use starter workflows as a starting place to build your custom workflow or use them as-is. -You can browse the full list of starter workflows in the {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}. +You can browse the full list of starter workflows in the {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` repository on {% data variables.location.product_location %}{% endif %}. diff --git a/translations/zh-CN/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md b/translations/zh-CN/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md index 8df494a991..6f3376cb84 100644 --- a/translations/zh-CN/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md +++ b/translations/zh-CN/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md @@ -1,22 +1,14 @@ ---- -ms.openlocfilehash: 281a3a039c8a557c209e756d107ac1856a181017 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145084818" ---- -我们在 {% data variables.product.product_location %} 上记录并显示 {% data variables.product.prodname_GH_advanced_security %} 的两名提交者: +We record and display two numbers of committers for {% data variables.product.prodname_GH_advanced_security %} on {% data variables.location.product_location %}: -- “提交者数”是指在组织中参与至少一个 {% ifversion fpt or ghec %} 专用{% endif %}存储库,并在你的企业许可中使用一个席位的提交者数量。 也就是说,他们也是组织成员、外部协作者,或者具有待处理的企业帐户中组织加入邀请。 -- “是此存储库/组织唯一”是指仅向此存储库或此组织中的存储库作出贡献的提交者数量。 此数字显示您可以通过禁用该仓库或组织的 {% data variables.product.prodname_GH_advanced_security %} 来释放多少许可证席位。 +- **Committers** is the number of committers who contributed to at least one {% ifversion fpt or ghec %}private {% endif %}repository in an organization and who use a seat in your enterprise license. That is, they are also an organization member, an external collaborator, or have a pending invitation to join an organization in your enterprise. +- **Unique to this repository/organization** is the number of committers who contributed only to this repository, or to repositories in this organization. This number shows how many license seats you can free up by disabling {% data variables.product.prodname_GH_advanced_security %} for that repository or organization. -如果没有唯一的提交者,则意味着所有活跃的提交者也参与其他使用 {% data variables.product.prodname_GH_advanced_security %} 的仓库或组织。 禁用该仓库或组织的功能将不会在您的许可证上腾出任何席位。 +If there are no unique committers, all active committers also contribute to other repositories or organizations that use {% data variables.product.prodname_GH_advanced_security %}. Disabling the feature for that repository or organization would not free any seats on your license. -从企业帐户中删除用户后,用户的许可证在 24 小时内被释放。 +When you remove a user from your enterprise account, the user's license is freed within 24 hours. {% note %} -注意:用户可以参与多个存储库或组织。 使用数是在整个企业帐户中计量的,确保每个成员使用一个席位,无论该用户参与多少个仓库或组织。 +**Note:** Users can contribute to multiple repositories or organizations. Usage is measured across the whole enterprise account to ensure that each member uses one seat regardless of how many repositories or organizations the user contributes to. {% endnote %} diff --git a/translations/zh-CN/data/reusables/apps/user-to-server-rate-limits.md b/translations/zh-CN/data/reusables/apps/user-to-server-rate-limits.md index a5261ef4de..f56f5c3e0c 100644 --- a/translations/zh-CN/data/reusables/apps/user-to-server-rate-limits.md +++ b/translations/zh-CN/data/reusables/apps/user-to-server-rate-limits.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 3bc47303cbc18b4d40a76fd12e6f692990f66c54 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145098339" ---- -{% ifversion ghes %}默认情况下,用户到服务器{% else %}用户到服务器{% endif %}请求的速率限制为每个经验证的用户每小时最多发送 {% ifversion ghae %}15,000{% elsif fpt or ghec or ghes %}5,000{% endif %} 个请求。 来自用户授权的 OAuth 应用程序或用户拥有的个人访问令牌的所有请求,以及以及使用任何用户的身份验证凭据进行身份验证的请求,都共享该用户每小时 {% ifversion ghae %}15,000{% elsif fpt or ghec or ghes %}5,000{% endif %} 个请求的配额。 +{% ifversion ghes %}By default, user-to-server{% else %}User-to-server{% endif %} requests are limited to {% ifversion ghae %}15,000{% elsif fpt or ghec or ghes %}5,000{% endif %} requests per hour and per authenticated user. All requests from OAuth applications authorized by a user or a {% data variables.product.pat_generic %} owned by the user, and requests authenticated with any of the user's authentication credentials, share the same quota of {% ifversion ghae %}15,000{% elsif fpt or ghec or ghes %}5,000{% endif %} requests per hour for that user. diff --git a/translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md b/translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md index 14edc219c9..a135b85355 100644 --- a/translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md +++ b/translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md @@ -1,113 +1,193 @@ ---- -ms.openlocfilehash: 5cb0c8cc93347c8da7c37bfe1082fc933f677288 -ms.sourcegitcommit: 6edb015070d3f0fda4525c6c931f1324626345dc -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/12/2022 -ms.locfileid: "147887348" ---- -| 类别名称 | 说明 +| Category name | Description |------------------|------------------- -{%- ifversion fpt or ghec %} | `account` | 包含与组织帐户相关的活动。 -| `advisory_credit` | 包含与 {% data variables.product.prodname_advisory_database %} 中安全通告的贡献者积分相关的活动。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_dotcom %} 安全通知](/github/managing-security-vulnerabilities/about-github-security-advisories)”。 -{%- endif %} | `artifact` | 包含与 {% data variables.product.prodname_actions %} 工作流运行工件相关的活动。 -{%- ifversion audit-log-streaming %} | `audit_log_streaming` | 包含与企业帐户中组织的流式审核日志相关的活动。 -{%- endif %} {%- ifversion fpt or ghec %} | `billing` | 包含与组织计费相关的活动。 -{%- endif %} {%- ifversion ghec or ghes or ghae %} | `business` | 包含与企业的业务设置相关的活动。 -{%- endif %} {%- ifversion ghec or ghes or ghae %} | `business` | 包含与企业的业务设置相关的活动。 -{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `business_secret_scanning_custom_pattern` | 包含与企业中机密扫描的自定义模式相关的活动。 -{%- endif %} | `checks` | 包含与检查套件和运行相关的活动。 -{%- ifversion fpt or ghec %} | `codespaces` | 包含与组织的 codespaces 相关的活动。 -{%- endif %} | `commit_comment` | 包含与更新或删除提交评论相关的活动。 -{%- ifversion ghes %} | `config_entry` | 包含与配置设置相关的活动。 这些事件仅在站点管理员审核日志中可见。 -{%- endif %} {%- ifversion fpt or ghec or ghes > 3.2 or ghae %} | | `dependabot_alerts` | 包含现有存储库中 {% data variables.product.prodname_dependabot_alerts %} 的组织级配置活动。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)”。 -| `dependabot_alerts_new_repos` | 包含组织新建存储库中 {% data variables.product.prodname_dependabot_alerts %} 的组织级配置活动。 -| `dependabot_repository_access` | 包含与允许 {% data variables.product.prodname_dependabot %} 访问组织中哪些专用存储库相关的活动。 -{%- endif %} {%- ifversion fpt or ghec or ghes > 3.2 %} | `dependabot_security_updates` | 包含现有存储库中 {% data variables.product.prodname_dependabot_security_updates %} 的组织级配置活动。 有关详细信息,请参阅“[配置 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)”。 -| `dependabot_security_updates_new_repos` | 包含组织新建存储库中 {% data variables.product.prodname_dependabot_security_updates %} 的组织级配置活动。 -{%- endif %} | `dependency_graph` | 包含存储库依赖项关系图的组织级配置活动。 有关详细信息,请参阅“[关于依赖项关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。 -| `dependency_graph_new_repos` | 包含组织新建存储库的组织级配置活动。 -{%- ifversion fpt or ghec %} | `discussion` | 包含与团队讨论相关的活动。 -| `discussion_comment` | 包含与发布到团队页的讨论中的评论相关的活动。 -| `discussion_post` | 包含与发布到团队页的讨论相关的活动。 -| `discussion_post_reply` | 包含与发布到团队页的讨论回复相关的活动。 -{%- endif %} {%- ifversion ghec or ghes %} | `dotcom_connection` | 包含与 {% data variables.product.prodname_github_connect %} 相关的活动。 -| `enterprise` | 包含与企业设置相关的活动。 -{%- endif %} {%- ifversion ghec %} | `enterprise_domain` | 包含与已验证的企业域相关的活动。 -| `enterprise_installation` | 包含与和 {% data variables.product.prodname_github_connect %} 企业连接关联的 {% data variables.product.prodname_github_app %} 相关的活动。 -{%- endif %} {%- ifversion fpt or ghec %} | `environment` | 包含与 {% data variables.product.prodname_actions %} 环境相关的活动。 -{%- endif %} {%- ifversion ghae %} | `external_group` | 包含与 Okta 组相关的活动。 -| `external_identity` | 包含与 Okta 组中的用户相关的活动。 -{%- endif %} | `gist` | 包含与 Gists 相关的活动。 -| `hook` | 包含与 Webhook 相关的活动。 -| `integration` | 包含与帐户中的集成相关的活动。 -| `integration_installation` | 包含与帐户中安装的集成相关的活动。 -| `integration_installation_request` | 包含与组织成员请求所有者批准在组织中使用的集成相关的活动。 -{%- ifversion ghec or ghae %} | `ip_allow_list` | 包含与为组织启用或禁用 IP 允许列表相关的活动。 -| `ip_allow_list_entry` | 包含与为组织创建、删除和编辑 IP 允许列表条目相关的活动。 -{%- endif %} | `issue` | 包含与固定、转移或删除存储库中问题相关的活动。 -| `issue_comment` | 包含与固定、转移或删除问题评论相关的活动。 -| `issues` | 包含与为组织启用或禁用问题创建相关的活动。 -{%- ifversion fpt or ghec %} | `marketplace_agreement_signature` | 包含与签署 {% data variables.product.prodname_marketplace %} 开发者协议相关的活动。 -| `marketplace_listing` | 包含与 {% data variables.product.prodname_marketplace %} 中列出的应用相关的活动。 -{%- endif %} | `members_can_create_pages` | 包含与管理组织存储库的 {% data variables.product.prodname_pages %} 站点发布相关的活动。 有关详细信息,请参阅“[为组织管理 {% data variables.product.prodname_pages %} 站点的发布](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)”。 -| `members_can_create_private_pages` | 包含与管理组织存储库的专用 {% data variables.product.prodname_pages %} 站点发布相关的活动。 -| `members_can_create_public_pages` | 包含与管理组织存储库的公共 {% data variables.product.prodname_pages %} 站点发布相关的活动。 -{%- ifversion ghec or ghes or ghae %} | `members_can_delete_repos` | 包含与为组织启用或禁用存储库创建相关的活动。 -{%- endif %} {%- ifversion fpt or ghec %} | `members_can_view_dependency_insights` | 包含允许组织成员查看依赖项见解的组织级配置活动。 -| `migration` | 包含与将数据从源位置(例如 {% data variables.product.prodname_dotcom_the_website %} 组织或 {% data variables.product.prodname_ghe_server %} 实例)传输到目标 {% data variables.product.prodname_ghe_server %} 实例相关的活动 。 -{%- endif %} | `oauth_access` | 包含与 OAuth 访问令牌相关的活动。 -| `oauth_application` | 包含与 OAuth 应用相关的活动。 -{%- ifversion fpt or ghec %} | `oauth_authorization` | 包含与授权 OAuth 应用相关的活动。 -{%- endif %} | `org` | 包含与组织成员身份相关的活动。 -{%- ifversion ghec or ghes or ghae %} | `org_credential_authorization` | 包含与授权凭据以用于 SAML 单一登录相关的活动。 -{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `org_secret_scanning_custom_pattern` | 包含与组织中机密扫描的自定义模式相关的活动。 有关详细信息,请参阅“[为机密扫描定义自定义模式](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)”。 -| `org.secret_scanning_push_protection` | 包含与组织中的机密扫描自定义模式相关的活动。 有关详细信息,请参阅“[使用机密扫描保护推送](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)”。 -{%- endif %} | `organization_default_label` | 包含与组织中存储库的默认标签相关的活动。 -{%- ifversion fpt or ghec or ghes %} | `organization_domain` | 包含与已验证的组织域相关的活动。 -| `organization_projects_change` | 包含与企业中组织范围的项目板相关的活动。 -{%- endif %} {%- ifversion fpt or ghec %} | `pages_protected_domain` | 包含与 {% data variables.product.prodname_pages %} 的已验证自定义域相关的活动。 -| `payment_method` | 包含与组织如何支付 {% data variables.product.prodname_dotcom %} 相关的活动。 -| `prebuild_configuration` | 包含与 {% data variables.product.prodname_github_codespaces %} 的预生成配置相关的活动。 -{%- endif %} {%- ifversion ghes %} | `pre_receive_environment` | 包含与预接收挂钩环境相关的活动。 -| `pre_receive_hook` | 包含与预接收挂钩相关的活动。 -{%- endif %} {%- ifversion ghes %} | `private_instance_encryption` | 包含与为企业启用专用模式相关的活动。 -{%- endif %} | `private_repository_forking` | 包含与允许存储库、组织或企业的专用和内部存储库分支相关的活动。 -{%- ifversion fpt or ghec %} | `profile_picture` | 包含与组织的配置文件图片相关的活动。 -{%- endif %} | `project` | 包含与项目板相关的活动。 -| `project_field` | 包含与项目板中的字段创建和删除相关的活动。 -| `project_view` | 包含与项目板中的视图创建和删除相关的活动。 -| `protected_branch` | 包含与受保护分支相关的活动。 -| `public_key` | 包含与 SSH 密钥和部署密钥相关的活动。 -| `pull_request` | 包含与拉取请求评审相关的活动。 -| `pull_request_review` | 包含与拉取请求评审相关的活动。 -| `pull_request_review_comment` | 包含与拉取请求评审评论相关的活动。 -| `repo` | 包含与组织拥有的存储库相关的活动。 -{%- ifversion fpt or ghec %} | `repository_advisory` | 包含与 {% data variables.product.prodname_advisory_database %} 中的安全通告相关的存储库级活动。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_dotcom %} 安全通知](/github/managing-security-vulnerabilities/about-github-security-advisories)”。 -| `repository_content_analysis` | 包含与[为专用存储库启用或禁用数据使用](/articles/about-github-s-use-of-your-data)相关的活动。 -| `repository_dependency_graph` | 包含与为{% ifversion fpt or ghec %}专用{% endif %}存储库启用或禁用依赖项关系图相关的存储库级活动。 有关详细信息,请参阅“[关于依赖项关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。 -{%- endif %} | `repository_image` | 包含与存储库映像相关的活动。 -| `repository_invitation` | 包含与邀请加入存储库相关的活动。 -| `repository_projects_change` | 包含与为存储库或组织中的所有存储库启用项目相关的活动。 -{%- ifversion ghec or ghes or ghae %} | `repository_secret_scanning` | 包含与机密扫描相关的存储库级活动。 有关详细信息,请参阅“[关于机密扫描](/github/administering-a-repository/about-secret-scanning)”。 -{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `repository_secret_scanning_custom_pattern` | 包含与存储库中的机密扫描自定义模式相关的活动。 有关详细信息,请参阅“[为机密扫描定义自定义模式](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)”。 {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %} | `repository_secret_scanning_push_protection` | 包含与存储库中的机密扫描自定义模式相关的活动。 有关详细信息,请参阅“[使用机密扫描保护推送](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)”。 -{%- endif %} {%- ifversion fpt or ghec %} | `repository_visibility_change` | 包含与允许组织成员更改组织的存储库可见性相关的活动。 -{%- endif %} | `repository_vulnerability_alert` | 包含与 [{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts) 相关的活动。 -{%- ifversion fpt or ghec %} | `repository_vulnerability_alerts` | 包含 {% data variables.product.prodname_dependabot_alerts %} 的存储库级配置活动。 -| `required_status_check` | 包含与受保护分支所需的状态检查相关的活动。 -{%- endif %} {%- ifversion ghec or ghes %} | `restrict_notification_delivery` | 包含与将电子邮件通知限制为企业的已批准或已验证域相关的活动。 -{%- endif %} {%- ifversion custom-repository-roles %} | `role` | 包含与[自定义存储库角色](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)相关的活动。 -{%- endif %} {%- ifversion ghec or ghes or ghae %} | `secret_scanning` | 包含现有存储库中机密扫描的组织级配置活动。 有关详细信息,请参阅“[关于机密扫描](/github/administering-a-repository/about-secret-scanning)”。 -| `secret_scanning_new_repos` | 包含组织新建存储库中机密扫描的组织级配置活动。 -{%- endif %} {%- ifversion ghec or ghes or ghae %} | `security_key` | 包含与安全密钥注册和删除相关的活动。 -{%- endif %} {%- ifversion fpt or ghec %} | `sponsors` | 包含与赞助按钮相关的事件(请参阅“[在存储库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”)。 -{%- endif %} {%- ifversion ghec or ghes or ghae %} | `ssh_certificate_authority` | 包含与组织或企业中的 SSH 证书颁发机构相关的活动。 -| `ssh_certificate_requirement` | 包含与要求成员使用 SSH 证书访问组织资源相关的活动。 -{%- endif %} | `staff` | 包含与执行操作的站点管理员相关的活动。 -| `team` | 包含与组织中的团队相关的活动。 -| `team_discussions` | 包含与管理组织的团队讨论相关的活动。 -{%- ifversion ghec %} | `team_sync_tenant` | 包含与企业或组织的 IdP 进行团队同步相关的活动。 -{%- endif %} {%- ifversion fpt or ghes %} | `two_factor_authentication` | 包含与双因素身份验证相关的活动。 -{%- endif %} | `user` | 包含与企业或组织中的用户相关的活动。 -{%- ifversion ghec or ghes %} | `user_license` | 包含与占用企业许可席位并身为企业成员的用户相关的活动。 -{%- endif %} | `workflows` | 包含与 {% data variables.product.prodname_actions %} 工作流相关的活动。 +{%- ifversion fpt or ghec %} +| `account` | Contains activities related to an organization account. +| `advisory_credit` | Contains activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." +{%- endif %} +| `artifact` | Contains activities related to {% data variables.product.prodname_actions %} workflow run artifacts. +{%- ifversion audit-log-streaming %} +| `audit_log_streaming` | Contains activities related to streaming audit logs for organizations in an enterprise account. +{%- endif %} +{%- ifversion fpt or ghec %} +| `billing` | Contains activities related to an organization's billing. +{%- endif %} +{%- ifversion ghec or ghes or ghae %} +| `business` | Contains activities related to business settings for an enterprise. +{%- endif %} +{%- ifversion code-security-audit-log-events %} +| `business_advanced_security` | Contains activities related to {% data variables.product.prodname_GH_advanced_security %} in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_secret_scanning` | Contains activities related to {% data variables.product.prodname_secret_scanning %} in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +{%- endif %} +{%- ifversion secret-scanning-audit-log-custom-patterns %} +| `business_secret_scanning_custom_pattern` | Contains activities related to custom patterns for {% data variables.product.prodname_secret_scanning %} in an enterprise. +{%- endif %} +{%- ifversion code-security-audit-log-events %} +| `business_secret_scanning_push_protection` | Contains activities related to the push protection feature of {% data variables.product.prodname_secret_scanning %} in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +| `business_secret_scanning_push_protection_custom_message` | Contains activities related to the custom message displayed when push protection is triggered in an enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)." +{%- endif %} +| `checks` | Contains activities related to check suites and runs. +{%- ifversion fpt or ghec %} +| `codespaces` | Contains activities related to an organization's codespaces. +{%- endif %} +| `commit_comment` | Contains activities related to updating or deleting commit comments. +{%- ifversion ghes %} +| `config_entry` | Contains activities related to configuration settings. These events are only visible in the site admin audit log. +{%- endif %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} | +| `dependabot_alerts` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." +| `dependabot_alerts_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization. +| `dependabot_repository_access` | Contains activities related to which private repositories in an organization {% data variables.product.prodname_dependabot %} is allowed to access. +{%- endif %} +{%- ifversion fpt or ghec or ghes > 3.2 %} +| `dependabot_security_updates` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." +| `dependabot_security_updates_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization. +{%- endif %} +| `dependency_graph` | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." +| `dependency_graph_new_repos` | Contains organization-level configuration activities for new repositories created in the organization. +{%- ifversion fpt or ghec %} +| `discussion` | Contains activities related to team discussions. +| `discussion_comment` | Contains activities related to comments posted in discussions on a team page. +| `discussion_post` | Contains activities related to discussions posted to a team page. +| `discussion_post_reply` | Contains activities related to replies to discussions posted to a team page. +{%- endif %} +{%- ifversion ghec or ghes %} +| `dotcom_connection` | Contains activities related to {% data variables.product.prodname_github_connect %}. +| `enterprise` | Contains activities related to enterprise settings. +{%- endif %} +{%- ifversion ghec %} +| `enterprise_domain` | Contains activities related to verified enterprise domains. +| `enterprise_installation` | Contains activities related to {% data variables.product.prodname_github_app %}s associated with an {% data variables.product.prodname_github_connect %} enterprise connection. +{%- endif %} +{%- ifversion fpt or ghec %} +| `environment` | Contains activities related to {% data variables.product.prodname_actions %} environments. +{%- endif %} +{%- ifversion ghae %} +| `external_group` | Contains activities related to Okta groups. +| `external_identity` | Contains activities related to a user in an Okta group. +{%- endif %} +| `gist` | Contains activities related to Gists. +| `hook` | Contains activities related to webhooks. +| `integration` | Contains activities related to integrations in an account. +| `integration_installation` | Contains activities related to integrations installed in an account. +| `integration_installation_request` | Contains activities related to organization member requests for owners to approve integrations for use in the organization. +{%- ifversion ghec or ghae %} +| `ip_allow_list` | Contains activities related to enabling or disabling the IP allow list for an organization. +| `ip_allow_list_entry` | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization. +{%- endif %} +| `issue` | Contains activities related to pinning, transferring, or deleting an issue in a repository. +| `issue_comment` | Contains activities related to pinning, transferring, or deleting issue comments. +| `issues` | Contains activities related to enabling or disabling issue creation for an organization. +{%- ifversion fpt or ghec %} +| `marketplace_agreement_signature` | Contains activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement. +| `marketplace_listing` | Contains activities related to listing apps in {% data variables.product.prodname_marketplace %}. +{%- endif %} +| `members_can_create_pages` | Contains activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." +| `members_can_create_private_pages` | Contains activities related to managing the publication of private {% data variables.product.prodname_pages %} sites for repositories in the organization. +| `members_can_create_public_pages` | Contains activities related to managing the publication of public {% data variables.product.prodname_pages %} sites for repositories in the organization. +{%- ifversion ghec or ghes or ghae %} +| `members_can_delete_repos` | Contains activities related to enabling or disabling repository creation for an organization. +{%- endif %} +{%- ifversion fpt or ghec %} +| `members_can_view_dependency_insights` | Contains organization-level configuration activities allowing organization members to view dependency insights. +| `migration` | Contains activities related to transferring data from a *source* location (such as a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance. +{%- endif %} +| `oauth_access` | Contains activities related to OAuth access tokens. +| `oauth_application` | Contains activities related to OAuth Apps. +{%- ifversion fpt or ghec %} +| `oauth_authorization` | Contains activities related to authorizing OAuth Apps. +{%- endif %} +| `org` | Contains activities related to organization membership. +{%- ifversion ghec or ghes or ghae %} +| `org_credential_authorization` | Contains activities related to authorizing credentials for use with SAML single sign-on. +{%- endif %} +{%- ifversion secret-scanning-audit-log-custom-patterns %} +| `org_secret_scanning_custom_pattern` | Contains activities related to custom patterns for secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." +| `org.secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in an organization. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." +{%- endif %} +| `organization_default_label` | Contains activities related to default labels for repositories in an organization. +{%- ifversion fpt or ghec or ghes %} +| `organization_domain` | Contains activities related to verified organization domains. +| `organization_projects_change` | Contains activities related to organization-wide project boards in an enterprise. +{%- endif %} +{%- ifversion fpt or ghec %} +| `pages_protected_domain` | Contains activities related to verified custom domains for {% data variables.product.prodname_pages %}. +| `payment_method` | Contains activities related to how an organization pays for {% data variables.product.prodname_dotcom %}. +| `prebuild_configuration` | Contains activities related to prebuild configurations for {% data variables.product.prodname_github_codespaces %}. +{%- endif %} +{%- ifversion ghes %} +| `pre_receive_environment` | Contains activities related to pre-receive hook environments. +| `pre_receive_hook` | Contains activities related to pre-receive hooks. +{%- endif %} +{%- ifversion ghes %} +| `private_instance_encryption` | Contains activities related to enabling private mode for an enterprise. +{%- endif %} +| `private_repository_forking` | Contains activities related to allowing forks of private and internal repositories, for a repository, organization or enterprise. +{%- ifversion fpt or ghec %} +| `profile_picture` | Contains activities related to an organization's profile picture. +{%- endif %} +| `project` | Contains activities related to project boards. +| `project_field` | Contains activities related to field creation and deletion in a project board. +| `project_view` | Contains activities related to view creation and deletion in a project board. +| `protected_branch` | Contains activities related to protected branches. +| `public_key` | Contains activities related to SSH keys and deploy keys. +| `pull_request` | Contains activities related to pull requests. +| `pull_request_review` | Contains activities related to pull request reviews. +| `pull_request_review_comment` | Contains activities related to pull request review comments. +| `repo` | Contains activities related to the repositories owned by an organization. +{%- ifversion fpt or ghec %} +| `repository_advisory` | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." +| `repository_content_analysis` | Contains activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data). +| `repository_dependency_graph` | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." +{%- endif %} +| `repository_image` | Contains activities related to images for a repository. +| `repository_invitation` | Contains activities related to invitations to join a repository. +| `repository_projects_change` | Contains activities related to enabling projects for a repository or for all repositories in an organization. +{%- ifversion ghec or ghes or ghae %} +| `repository_secret_scanning` | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." +{%- endif %} +{%- ifversion secret-scanning-audit-log-custom-patterns %} +| `repository_secret_scanning_custom_pattern` | Contains activities related to secret scanning custom patterns in a repository. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %} +| `repository_secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." +{%- endif %} +{%- ifversion fpt or ghec %} +| `repository_visibility_change` | Contains activities related to allowing organization members to change repository visibilities for the organization. +{%- endif %} +| `repository_vulnerability_alert` | Contains activities related to [{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts). +{%- ifversion fpt or ghec %} +| `repository_vulnerability_alerts` | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}. +| `required_status_check` | Contains activities related to required status checks for protected branches. +{%- endif %} +{%- ifversion ghec or ghes %} +| `restrict_notification_delivery` | Contains activities related to the restriction of email notifications to approved or verified domains for an enterprise. +{%- endif %} +{%- ifversion custom-repository-roles %} +| `role` | Contains activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization). +{%- endif %} +{%- ifversion ghec or ghes or ghae %} +| `secret_scanning` | Contains organization-level configuration activities for secret scanning in existing repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." +| `secret_scanning_new_repos` | Contains organization-level configuration activities for secret scanning for new repositories created in the organization. +{%- endif %} +{%- ifversion ghec or ghes or ghae %} +| `security_key` | Contains activities related to security keys registration and removal. +{%- endif %} +{%- ifversion fpt or ghec %} +| `sponsors` | Contains events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"). +{%- endif %} +{%- ifversion ghec or ghes or ghae %} +| `ssh_certificate_authority` | Contains activities related to a SSH certificate authority in an organization or enterprise. +| `ssh_certificate_requirement` | Contains activities related to requiring members use SSH certificates to access organization resources. +{%- endif %} +| `staff` | Contains activities related to a site admin performing an action. +| `team` | Contains activities related to teams in an organization. +| `team_discussions` | Contains activities related to managing team discussions for an organization. +{%- ifversion ghec %} +| `team_sync_tenant` | Contains activities related to team synchronization with an IdP for an enterprise or organization. +{%- endif %} +{%- ifversion fpt or ghes %} +| `two_factor_authentication` | Contains activities related to two-factor authentication. +{%- endif %} +| `user` | Contains activities related to users in an enterprise or organization. +{%- ifversion ghec or ghes %} +| `user_license` | Contains activities related to a user occupying a licensed seat in, and being a member of, an enterprise. +{%- endif %} +| `workflows` | Contains activities related to {% data variables.product.prodname_actions %} workflows. diff --git a/translations/zh-CN/data/reusables/branches/new-repo-default-branch.md b/translations/zh-CN/data/reusables/branches/new-repo-default-branch.md index 0b75c9b69a..17f774ac0d 100644 --- a/translations/zh-CN/data/reusables/branches/new-repo-default-branch.md +++ b/translations/zh-CN/data/reusables/branches/new-repo-default-branch.md @@ -1,10 +1,2 @@ ---- -ms.openlocfilehash: 9cc8fc34ada2e8d2831de2f62005f139ebcc7cfe -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145098859" ---- -在 {% data variables.product.product_location %}和 {% data variables.product.product_name %} 上创建一个有内容的仓库时,将创建包含单一分支的仓库。 仓库中的第一个分支是默认分支。 +When you create a repository with content on {% data variables.location.product_location %}, {% data variables.product.product_name %} creates the repository with a single branch. This first branch in the repository is the default branch. diff --git a/translations/zh-CN/data/reusables/classroom/about-autograding.md b/translations/zh-CN/data/reusables/classroom/about-autograding.md index 8c8b6fd8d4..29cde59f64 100644 --- a/translations/zh-CN/data/reusables/classroom/about-autograding.md +++ b/translations/zh-CN/data/reusables/classroom/about-autograding.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 861671360dc3718c5d796e9d07924952e221cbb7 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145098288" ---- -您可以使用自动评分来自动检查学生在 {% data variables.product.prodname_classroom %} 上的工作。 您可以为作业配置测试,每次学生推送到 {% data variables.product.product_location %} 上的作业库时,测试就会立即运行。 学生可以查看测试结果,进行更改,并推送以查看新结果。 +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.location.product_location %}. The student can view the test results, make changes, and push to see new results. diff --git a/translations/zh-CN/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md b/translations/zh-CN/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md index 960f7add38..9a06bcca8f 100644 --- a/translations/zh-CN/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md +++ b/translations/zh-CN/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 4a60a2f573a8aebe309f1db397e38cd41ef8eeac -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145098221" ---- -您可以使用 {% data variables.product.prodname_actions %} 在 {% data variables.product.product_name %} 内运行 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 。 或者,如果您使用第三方持续集成或持续交付/部署 (CI/CD) 系统,您可以在现有系统中运行 {% data variables.product.prodname_codeql %} 分析并将结果上传到 {% data variables.product.product_location %}。 +You can run {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %} using {% data variables.product.prodname_actions %}. Alternatively, if you use a third-party continuous integration or continuous delivery/deployment (CI/CD) system, you can run {% data variables.product.prodname_codeql %} analysis in your existing system and upload the results to {% data variables.location.product_location %}. diff --git a/translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md b/translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md index f625baf952..df8cfa6027 100644 --- a/translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md +++ b/translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md @@ -1,16 +1,8 @@ ---- -ms.openlocfilehash: e28e49974140b810496d7ca2af2d8ac07d30b754 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145098212" ---- {% ifversion ghes %} {% note %} -**注意:** 网站管理员必须为 {% data variables.product.product_location %} 启用 {% data variables.product.prodname_code_scanning %},然后你才能使用此功能。 如果要使用 {% data variables.product.prodname_actions %} 扫描代码,站点管理员还必须启用 {% data variables.product.prodname_actions %} 并设置所需的基础结构。 有关详细信息,请参阅“[为设备配置 {% data variables.product.prodname_code_scanning %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance)”。 +**Note:** Your site administrator must enable {% data variables.product.prodname_code_scanning %} for {% data variables.location.product_location %} before you can use this feature. If you want to use {% data variables.product.prodname_actions %} to scan your code, the site administrator must also enable {% data variables.product.prodname_actions %} and set up the infrastructure required. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance)." {% endnote %} diff --git a/translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning.md b/translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning.md index 0216539bcb..700cd26b27 100644 --- a/translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning.md +++ b/translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning.md @@ -2,7 +2,7 @@ {% note %} -**Note:** Your site administrator must enable {% data variables.product.prodname_code_scanning %} for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance)." +**Note:** Your site administrator must enable {% data variables.product.prodname_code_scanning %} for {% data variables.location.product_location %} before you can use this feature. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance)." {% ifversion security-feature-enablement-policies %} You may not be able to enable or disable {% data variables.product.prodname_code_scanning %} if an enterprise owner has set a policy at the enterprise level. For more information, see "[Enforcing policies for code security and analysis for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise)."{% endif %} diff --git a/translations/zh-CN/data/reusables/code-scanning/what-is-codeql-cli.md b/translations/zh-CN/data/reusables/code-scanning/what-is-codeql-cli.md index f90d3356a1..2d4e1c65b1 100644 --- a/translations/zh-CN/data/reusables/code-scanning/what-is-codeql-cli.md +++ b/translations/zh-CN/data/reusables/code-scanning/what-is-codeql-cli.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: ec454deef6771dc385435a4148e5e095acfc1659 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145098765" ---- -{% data variables.product.prodname_codeql_cli %} 是一个可用来分析代码的独立产品。 其主要用途是生成代码空间的数据库表示形式,即 {% data variables.product.prodname_codeql %} 数据库。 数据库准备就绪后,您可以进行交互式查询,或者运行一系列查询以生成一组 SARIF 格式的结果,然后将结果上传到 {% data variables.product.product_location %}。 +The {% data variables.product.prodname_codeql_cli %} is a standalone product that you can use to analyze code. Its main purpose is to generate a database representation of a codebase, a {% data variables.product.prodname_codeql %} database. Once the database is ready, you can query it interactively, or run a suite of queries to generate a set of results in SARIF format and upload the results to {% data variables.location.product_location %}. diff --git a/translations/zh-CN/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/translations/zh-CN/data/reusables/codespaces/creating-a-codespace-in-vscode.md index 545324000c..1039481541 100644 --- a/translations/zh-CN/data/reusables/codespaces/creating-a-codespace-in-vscode.md +++ b/translations/zh-CN/data/reusables/codespaces/creating-a-codespace-in-vscode.md @@ -1,4 +1,4 @@ -After you connect your account on {% data variables.product.product_location %} to the {% data variables.product.prodname_github_codespaces %} extension, you can create a new codespace. For more information about the {% data variables.product.prodname_github_codespaces %} extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). +After you connect your account on {% data variables.location.product_location %} to the {% data variables.product.prodname_github_codespaces %} extension, you can create a new codespace. For more information about the {% data variables.product.prodname_github_codespaces %} extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 2. Click the Add icon: {% octicon "plus" aria-label="The plus icon" %}. diff --git a/translations/zh-CN/data/reusables/command_line/provide-an-access-token.md b/translations/zh-CN/data/reusables/command_line/provide-an-access-token.md index d54a71437c..f2a89e69b4 100644 --- a/translations/zh-CN/data/reusables/command_line/provide-an-access-token.md +++ b/translations/zh-CN/data/reusables/command_line/provide-an-access-token.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 0eae1b9c546c076ca089090e61080750f91e9dce -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145129947" ---- -{% ifversion fpt or ghec %}如果要访问使用 SAML SSO 的组织,在进行身份验证之前,还必须授权个人访问令牌访问该组织。 有关详细信息,请参阅“[关于使用 SAML 单一登录进行身份验证](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)”和“[授权用于 SAML 单一登录的个人访问令牌](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)。”{% endif %} +{% ifversion fpt or ghec %}If you are accessing an organization that uses SAML SSO{% ifversion pat-v2%} and you are using a {% data variables.product.pat_v1 %}{% endif %}, you must also authorize your {% data variables.product.pat_generic %} to access the organization before you authenticate. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" and "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."{% endif %} diff --git a/translations/zh-CN/data/reusables/dependabot/enterprise-enable-dependabot.md b/translations/zh-CN/data/reusables/dependabot/enterprise-enable-dependabot.md index a74ef3620a..844b35d9ea 100644 --- a/translations/zh-CN/data/reusables/dependabot/enterprise-enable-dependabot.md +++ b/translations/zh-CN/data/reusables/dependabot/enterprise-enable-dependabot.md @@ -2,7 +2,7 @@ {% note %} -**Note:** Your site administrator must set up {% data variables.product.prodname_dependabot_updates %} for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." +**Note:** Your site administrator must set up {% data variables.product.prodname_dependabot_updates %} for {% data variables.location.product_location %} before you can use this feature. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% ifversion security-feature-enablement-policies %} You may not be able to enable or disable {% data variables.product.prodname_dependabot_updates %} if an enterprise owner has set a policy at the enterprise level. For more information, see "[Enforcing policies for code security and analysis for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise)."{% endif %} diff --git a/translations/zh-CN/data/reusables/desktop/get-an-account.md b/translations/zh-CN/data/reusables/desktop/get-an-account.md index 008c0c1c8d..545cc0f5b9 100644 --- a/translations/zh-CN/data/reusables/desktop/get-an-account.md +++ b/translations/zh-CN/data/reusables/desktop/get-an-account.md @@ -1,12 +1,4 @@ ---- -ms.openlocfilehash: 41049556184008283745fe15886e9667774ec424 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145129775" ---- -你必须在 {% data variables.product.product_location %} 上拥有帐户。 +you must already have an account on {% data variables.location.product_location %}. -- 有关在 {% data variables.product.product_location %} 帐户上创建帐户的更多信息,请参阅“[注册新 {% data variables.product.prodname_dotcom %} 帐户](/articles/signing-up-for-a-new-github-account/)”。 -- 对于 {% data variables.product.prodname_enterprise %} 帐户,请联系您的 {% data variables.product.prodname_enterprise %} 网站管理员。 +- For more information on creating an account on {% data variables.location.product_location %} account, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account/)". +- For a {% data variables.product.prodname_enterprise %} account, contact your {% data variables.product.prodname_enterprise %} site administrator. diff --git a/translations/zh-CN/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md b/translations/zh-CN/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md index 70b44db1f8..e80cf9e28e 100644 --- a/translations/zh-CN/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md +++ b/translations/zh-CN/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md @@ -1,15 +1,8 @@ ---- -ms.openlocfilehash: f3a872ceadabe044524f906f9c713c2682e0ab88 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145129690" ---- -1. 在 {% data variables.product.product_location %} 上,导航到组织的主页。 -1. 在组织名称下,单击 {% octicon "gear" aria-label="The gear icon" %}“设置”。 -![组织设置按钮](/assets/images/help/discussions/org-settings.png) -1. 在“讨论”下,选择“为此组织启用团队讨论”。 -1. 选择一个存储库作为组织讨论的源存储库。 - ![用于为组织启用讨论的设置](/assets/images/help/discussions/enable-org-discussions.png) -1. 单击“保存” 。 +1. On {% data variables.location.product_location %}, navigate to the main page of your organization. +1. Under your organization name, click {% octicon "gear" aria-label="The gear icon" %} +**Settings**. +![Organization settings button](/assets/images/help/discussions/org-settings.png) +1. Under "Discussions", select **Enable discussions for this organization**. +1. Select a repository to use as the source repository for your organization discussions. + ![Settings to enable discussions for an organization](/assets/images/help/discussions/enable-org-discussions.png) +1. Click **Save**. diff --git a/translations/zh-CN/data/reusables/discussions/navigate-to-repo-or-org.md b/translations/zh-CN/data/reusables/discussions/navigate-to-repo-or-org.md index 3d630bbded..17ca81827c 100644 --- a/translations/zh-CN/data/reusables/discussions/navigate-to-repo-or-org.md +++ b/translations/zh-CN/data/reusables/discussions/navigate-to-repo-or-org.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 5d42e411b239f760ca058d6082557918f9fe9eee -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145129686" ---- -1. 在 {% data variables.product.product_location %} 上,导航到存储库或组织的主页。 +1. On {% data variables.location.product_location %}, navigate to the main page of the repository or organization. diff --git a/translations/zh-CN/data/reusables/discussions/starting-a-discussion.md b/translations/zh-CN/data/reusables/discussions/starting-a-discussion.md index 10e973607b..fb8a039155 100644 --- a/translations/zh-CN/data/reusables/discussions/starting-a-discussion.md +++ b/translations/zh-CN/data/reusables/discussions/starting-a-discussion.md @@ -1,18 +1,10 @@ ---- -ms.openlocfilehash: 4a1af9bdfa8fa3b86b2d64706d24a9dd1d33fd6f -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145129675" ---- -1. 在 {% data variables.product.product_location %} 上,导航到要在其中开始讨论的存储库或组织的主页。 +1. On {% data variables.location.product_location %}, navigate to the main page of the repository or organization where you want to start a discussion. {% data reusables.discussions.discussions-tab %} -1. 单击“新建讨论”。 - ![存储库“讨论”选项卡中的“新建讨论”按钮](/assets/images/help/discussions/new-discussion-button.png) -1. 选择“选择类别”下拉菜单,然后单击某个类别进行讨论。 - ![“选择类别”下拉菜单和存储库中可用类别的列表](/assets/images/help/discussions/new-discussion-select-category-dropdown-menu.png) -1. 输入讨论的标题和正文。 - ![新讨论标题和正文的文本字段](/assets/images/help/discussions/new-discussion-title-and-body-fields.png) -1. 单击“开始讨论”。 - ![“开始讨论”按钮](/assets/images/help/discussions/new-discussion-start-discussion-button.png) +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) diff --git a/translations/zh-CN/data/reusables/dotcom_billing/view-all-subscriptions.md b/translations/zh-CN/data/reusables/dotcom_billing/view-all-subscriptions.md index 29ed94b4d5..8403ca7ead 100644 --- a/translations/zh-CN/data/reusables/dotcom_billing/view-all-subscriptions.md +++ b/translations/zh-CN/data/reusables/dotcom_billing/view-all-subscriptions.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 24174465a9f462c750d0d51635133501fd1174ce -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145100974" ---- -要查看帐户在 {% data variables.product.product_location %} 上的所有订阅,请参阅“[查看订阅和计费日期](/articles/viewing-your-subscriptions-and-billing-date)”。 +To view all the subscriptions for your account on {% data variables.location.product_location %}, see "[Viewing your subscriptions and billing date](/articles/viewing-your-subscriptions-and-billing-date)." diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity.md b/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity.md index 8ff7e4ac60..80878d1726 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity.md @@ -1,31 +1,23 @@ ---- -ms.openlocfilehash: f89c8ea56df60e14b5735d160104d332ff1e804b -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "146680979" ---- -如果用户在 {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} 上执行了以下任何活动,则用户被视为处于活动状态。 +A user is considered active if the user has performed any of the following activities on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. -- 登录到 {% data variables.product.product_location %} -- 创建仓库 -- 推送到存储库 -- 被添加到存储库 -- 更改存储库的可见性 -- 创建议题或拉取请求 -- 评论问题或拉取请求 -- 关闭或重新打开问题或拉取请求 -- 将标签应用于问题或拉取请求,或删除标签 -- 分配或取消分配问题或拉取请求 -- 请求对拉取请求进行评审或删除评审请求 -- 在拉取请求评审中创建或编辑评论 -- 在拉取请求中消除评论 -- 同步拉取请求 -- 对提交进行评论 -- 发布版本 -- 推送到 Wiki -- 关注仓库 -- 对仓库标星 -- 删除仓库 -- 使用个人访问令牌或 SSH 密钥访问资源 +- Signing into {% data variables.location.product_location %} +- Creating a repository +- Pushing to a repository +- Being added to a repository +- Changing the visibility of a repository +- Creating an issue or pull request +- Commenting on an issue or pull request +- Closing or reopening an issue or pull request +- Applying a label to an issue or pull request, or removing a label +- Assigning or unassigning an issue or pull request +- Requesting a review of a pull request, or removing a review request +- Creating or editing a comment in a pull request review +- Dismissing a comment in a pull request +- Synchronizing a pull request +- Commenting on a commit +- Publishing a release +- Pushing to a wiki +- Watching a repository +- Starring a repository +- Deleting a repository +- Accessing resources by using a {% data variables.product.pat_generic %} or SSH key diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-cap-validates.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-cap-validates.md index c8c15da78b..f362c9b0ab 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/emu-cap-validates.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-cap-validates.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 583dd6201d170a08509a815a61c854c411e4938f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147067864" ---- -企业使用 OIDC SSO 时,{% data variables.product.prodname_dotcom %} 将自动使用 IdP 的条件访问策略 (CAP) IP 条件来验证用户与 {% data variables.product.prodname_dotcom %} 的交互,当成员更改 IP 地址时,每次使用个人访问令牌或 SSH 密钥时。 +When your enterprise uses OIDC SSO, {% data variables.product.prodname_dotcom %} will automatically use your IdP's conditional access policy (CAP) IP conditions to validate user interactions with {% data variables.product.prodname_dotcom %}, when members change IP addresses, and each time a {% data variables.product.pat_generic %} or SSH key is used. diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-forks.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-forks.md index 28ba30be8a..f78720f3bc 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/emu-forks.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-forks.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 559e156a8e9660bf4a720567d579eccc032c5573 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145109451" ---- -{% data variables.product.prodname_managed_users_caps %} 无法为企业外部的存储库创建分支,也无法为内部存储库创建分支。 {% data variables.product.prodname_managed_users_caps %} 可以将企业中组织拥有的专用存储库分叉到企业拥有的其他组织中,或者分叉为 {% data variables.product.prodname_managed_user %} 拥有的分支。 +{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise or fork internal repositories. {% data variables.enterprise.prodname_managed_users_caps %} can fork private repositories owned by organizations in the enterprise into other organizations owned by the enterprise, or as a fork owned by the {% data variables.enterprise.prodname_managed_user %}. diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-follow.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-follow.md index a584241423..a27bed899e 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-follow.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-follow.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: e49bce0aba4ff19dac4d6e1910be7301618c8640 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145066974" ---- -{% ifversion ghec %} {% data variables.product.prodname_emu_enterprise %} 的成员只能关注企业内的其他成员。 {% endif %} +{% ifversion ghec %} Members of an {% data variables.enterprise.prodname_emu_enterprise %} can only follow other members of their enterprise. {% endif %} diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-fork.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-fork.md index 34c066e245..c3bf0cb89e 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-fork.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-fork.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: e9c13cc91ec4d3ab498ad3d826e59c17f6881619 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145066971" ---- -{% ifversion ghec %}{% data variables.product.prodname_emu_enterprise %} 的成员无法从企业外部或分支内部存储库为存储库创建分支。{% endif %} +{% ifversion ghec %}Members of an {% data variables.enterprise.prodname_emu_enterprise %} cannot fork repositories from outside of the enterprise or fork internal repositories.{% endif %} diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-gist.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-gist.md index 7a4d0ec340..5093627199 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-gist.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-gist.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 4bf5ce9ef547b95c4f5ef6c4a9ff71ed553aa4b5 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145066959" ---- -{% ifversion ghec %}{% data variables.product.prodname_emu_enterprise %} 的成员无法创建 Gist,并且对 Gist 具有只读访问权限。{% endif %} +{% ifversion ghec %}Members of an {% data variables.enterprise.prodname_emu_enterprise %} cannot create gists and have read-only access to gists.{% endif %} diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-interact.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-interact.md index 3ff56d6be4..b2162ba7e2 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-interact.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-interact.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 7311dd81bdd55f580a1173cac98382c66fc7e86e -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145066950" ---- -{% ifversion ghec %} {% data variables.product.prodname_emu_enterprise %} 的成员只能与其企业内的存储库进行交互。 {% endif %} +{% ifversion ghec %} Members of an {% data variables.enterprise.prodname_emu_enterprise %} can only interact with repositories within their enterprise. {% endif %} diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-propose.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-propose.md index afdbc32eb4..2c473bfaa3 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-propose.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-propose.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 83895ddc4e2fc636d89d9715fee0d8890a3acfb6 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145066947" ---- -{% ifversion ghec %}{% data variables.product.prodname_emu_enterprise %} 的成员只能在属于其企业的存储库中提出更改。 {% endif %} +{% ifversion ghec %} Members of an {% data variables.enterprise.prodname_emu_enterprise %} can only propose changes in repositories that are part of their enterprise. {% endif %} diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-repo.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-repo.md index f21f8624c4..4112f4ef25 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-repo.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-repo.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 8d1b7b8fcff29aeef03dce23e62448db69266940 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145066946" ---- -{% ifversion ghec %} {% data variables.product.prodname_emu_enterprise %} 的成员只能在属于其企业的存储库中进行更改。 {% endif %} +{% ifversion ghec %} Members of an {% data variables.enterprise.prodname_emu_enterprise %} can only make changes in repositories that are part of their enterprise. {% endif %} diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-short-summary.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-short-summary.md index 3a875e07f0..c80082fe07 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/emu-short-summary.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-short-summary.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 57efd141644710352395659515a7215b723055f0 -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147876146" ---- -{% data variables.product.prodname_emus %} 是 {% data variables.product.prodname_ghe_cloud %} 的一项功能,可更好地控制企业成员和资源。 使用 {% data variables.product.prodname_emus %} 时,所有成员都通过标识提供者 (IdP) 进行预配和管理,而不是用户在 {% data variables.product.product_name %} 上创建自己的帐户。 可以使用 IdP 上的组管理团队成员身份。 {% data variables.product.prodname_managed_users_caps %} 仅限于其企业,无法推送代码、协作或与企业外部的用户、存储库和组织交互。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}”。{% endif %} +{% data variables.product.prodname_emus %} is a feature of {% data variables.product.prodname_ghe_cloud %} that provides even greater control over enterprise members and resources. With {% data variables.product.prodname_emus %}, all members are provisioned and managed through your identity provider (IdP) instead of users creating their own accounts on {% data variables.product.product_name %}. Team membership can be managed using groups on your IdP. {% data variables.enterprise.prodname_managed_users_caps %} are restricted to their enterprise and are unable to push code, collaborate, or interact with users, repositories, and organizations outside of their enterprise. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/oidc-gei-warning.md b/translations/zh-CN/data/reusables/enterprise-accounts/oidc-gei-warning.md index 0d315ba876..5ec0d137b6 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/oidc-gei-warning.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/oidc-gei-warning.md @@ -1,13 +1,5 @@ ---- -ms.openlocfilehash: ca435f630177ca47e4e7f733a7219a7c00a36292 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147066792" ---- {% warning %} -警告:如果使用 {% data variables.product.prodname_importer_proper_name %} 从 {% data variables.product.product_location_enterprise %} 迁移组织,请确保使用一个豁免于 Azure AD CAP 的服务帐户,否则迁移可能会被阻止。 +**Warning:** If you use {% data variables.product.prodname_importer_proper_name %} to migrate an organization from {% data variables.location.product_location_enterprise %}, make sure to use a service account that is exempt from Azure AD's CAP otherwise your migration may be blocked. {% endwarning %} diff --git a/translations/zh-CN/data/reusables/enterprise/apply-configuration.md b/translations/zh-CN/data/reusables/enterprise/apply-configuration.md index aa4484738b..7af7ba5163 100644 --- a/translations/zh-CN/data/reusables/enterprise/apply-configuration.md +++ b/translations/zh-CN/data/reusables/enterprise/apply-configuration.md @@ -1,20 +1,12 @@ ---- -ms.openlocfilehash: a7fec31cb255bd626918fd4bf9a2337debb259ae -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147883252" ---- -1. 若要应用配置,请输入以下命令。 +1. To apply the configuration, enter the following command. {% note %} - 注意:在配置运行过程中,{% data variables.product.product_location %} 上的服务可能会重启,这可能会导致用户短暂停机。 + **Note**: During a configuration run, services on {% data variables.location.product_location %} may restart, which can cause brief downtime for users. {% endnote %} ```shell ghe-config-apply ``` -1. 等待配置运行完毕。 +1. Wait for the configuration run to complete. diff --git a/translations/zh-CN/data/reusables/enterprise/rate_limit.md b/translations/zh-CN/data/reusables/enterprise/rate_limit.md index becffb4d30..e6863783bd 100644 --- a/translations/zh-CN/data/reusables/enterprise/rate_limit.md +++ b/translations/zh-CN/data/reusables/enterprise/rate_limit.md @@ -1,16 +1,8 @@ ---- -ms.openlocfilehash: 9c3f4f2a11f84313dc59d7b42db0e5da7f947753 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145097870" ---- {% ifversion ghes %} {% note %} -注意:以下速率限制是 {% data variables.product.product_name %} 的默认速率限制。 请与站点管理员联系,以确认 {% data variables.product.product_location %} 的速率限制。 +**Note**: The following rate limits are the default rate limits for {% data variables.product.product_name %}. Contact your site administrator to confirm the rate limits for {% data variables.location.product_location %}. {% endnote %} diff --git a/translations/zh-CN/data/reusables/enterprise/test-in-staging.md b/translations/zh-CN/data/reusables/enterprise/test-in-staging.md index 54c0baac64..43fe854c49 100644 --- a/translations/zh-CN/data/reusables/enterprise/test-in-staging.md +++ b/translations/zh-CN/data/reusables/enterprise/test-in-staging.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: a852bf18992b237fa442a0d24363787b1cf22a64 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145097867" ---- -{% data variables.product.company_short %} 强烈建议在过渡环境中验证任何用于身份验证的新配置。 不正确的配置可能会导致 {% data variables.product.product_location %} 产生故障时间。 有关详细信息,请参阅“[设置暂存实例](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)”。 +{% data variables.product.company_short %} strongly recommends that you verify any new configuration for authentication in a staging environment. An incorrect configuration could result in downtime for {% data variables.location.product_location %}. For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)." diff --git a/translations/zh-CN/data/reusables/enterprise_enterprise_support/installing-releases.md b/translations/zh-CN/data/reusables/enterprise_enterprise_support/installing-releases.md index 142eefc78c..444818f8fe 100644 --- a/translations/zh-CN/data/reusables/enterprise_enterprise_support/installing-releases.md +++ b/translations/zh-CN/data/reusables/enterprise_enterprise_support/installing-releases.md @@ -2,6 +2,6 @@ ## Installing {% data variables.product.prodname_ghe_server %} releases -To ensure that {% data variables.product.product_location %} is stable, you must install and implement {% data variables.product.prodname_ghe_server %} releases. Installing {% data variables.product.prodname_ghe_server %} releases ensures that you have the latest features, modifications, and enhancements as well as any updates to features, code corrections, patches or other general updates and fixes to {% data variables.product.prodname_ghe_server %}. +To ensure that {% data variables.location.product_location %} is stable, you must install and implement {% data variables.product.prodname_ghe_server %} releases. Installing {% data variables.product.prodname_ghe_server %} releases ensures that you have the latest features, modifications, and enhancements as well as any updates to features, code corrections, patches or other general updates and fixes to {% data variables.product.prodname_ghe_server %}. {% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise_installation/download-package.md b/translations/zh-CN/data/reusables/enterprise_installation/download-package.md index 14c61489dc..6dd8199681 100644 --- a/translations/zh-CN/data/reusables/enterprise_installation/download-package.md +++ b/translations/zh-CN/data/reusables/enterprise_installation/download-package.md @@ -1,12 +1,4 @@ ---- -ms.openlocfilehash: 0aa4c7abc78f6d80d30aeb21763b404b98d87301 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147883802" ---- -1. 使用 `curl ` 将升级包下载到 {% data variables.product.product_location %}: +1. Download the upgrade package to {% data variables.location.product_location %} using `curl `: ```shell -admin@HOSTNAME:~$ curl -L -O UPGRADE-PKG-URL +admin@HOSTNAME:~$ curl -L -O UPGRADE-PKG-URL ``` 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 d80b50bb47..1d514c4aae 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,18 +1,10 @@ ---- -ms.openlocfilehash: 7de065c9dec15e3b92cabf5d3fa711c7d88249ba -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147882785" ---- -- [最低要求](#minimum-requirements) -- [存储](#storage) -- [CPU 和内存](#cpu-and-memory) +- [Minimum requirements](#minimum-requirements) +- [Storage](#storage) +- [CPU and memory](#cpu-and-memory) -### 最低要求 +### Minimum requirements -建议根据 {% data variables.product.product_location %} 的用户许可数选择不同的硬件配置。 如果预配的资源超过最低要求,您的实例将表现出更好的性能和扩展。 +We recommend different hardware configurations depending on the number of user licenses for {% data variables.location.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 %} @@ -20,27 +12,27 @@ ms.locfileid: "147882785" {% data reusables.enterprise_installation.about-adjusting-resources %} -### 存储 +### Storage -我们建议为 {% data variables.product.prodname_ghe_server %} 配置具有高每秒输入/输出操作数 (IOPS) 和低延迟的高性能 SSD。 工作负载是 I/O 密集型的。 如果使用裸机管理程序,建议直接连接磁盘或使用存储区域网络 (SAN) 中的磁盘。 +We recommend a high-performance SSD with high input/output operations per second (IOPS) and low latency for {% data variables.product.prodname_ghe_server %}. Workloads are I/O intensive. If you use a bare metal hypervisor, we recommend directly attaching the disk or using a disk from a storage area network (SAN). -您的实例需要一个独立于根磁盘的持久数据磁盘。 有关详细信息,请参阅[系统概述](/enterprise/admin/guides/installation/system-overview)。 +Your instance requires a persistent data disk separate from the root disk. For more information, see "[System overview](/enterprise/admin/guides/installation/system-overview)." {% ifversion ghes %} -若要配置 {% data variables.product.prodname_actions %},必须提供外部 Blob 存储。 更多信息请参阅“[{% data variables.product.prodname_ghe_server %} 的 {% data variables.product.prodname_actions %} 使用入门](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server##external-storage-requirements)”。 +To configure {% 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##external-storage-requirements)." {% endif %} -根文件系统上的可用空间将占磁盘总大小的 50%。 您可以通过构建一个新实例或使用现有实例来调整实例的根磁盘大小。 有关详细信息,请参阅“[系统概述](/enterprise/admin/guides/installation/system-overview#storage-architecture)”和“[增加存储容量](/enterprise/admin/guides/installation/increasing-storage-capacity)”。 +The available space on the root filesystem will be 50% of the total disk size. You can resize your instance's root disk by building a new instance or using an existing instance. For more information, see "[System overview](/enterprise/admin/guides/installation/system-overview#storage-architecture)" and "[Increasing storage capacity](/enterprise/admin/guides/installation/increasing-storage-capacity)." -### CPU 和内存 +### CPU and memory -{% 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. {% ifversion ghes %} -如果计划为 {% data variables.product.prodname_ghe_server %} 实例的用户启用 {% data variables.product.prodname_actions %},则可能需要为实例预配额外的 CPU 和内存资源。 更多信息请参阅“[{% data variables.product.prodname_ghe_server %} 的 {% data variables.product.prodname_actions %} 使用入门](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)”。 +If you plan to enable {% data variables.product.prodname_actions %} for the users of your {% data variables.product.prodname_ghe_server %} instance, you may need to provision additional CPU and memory resources for your instance. 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)." {% endif %} @@ -48,10 +40,10 @@ ms.locfileid: "147882785" {% warning %} -警告:建议用户配置 Web 挂钩事件来通知外部系统有关 {% data variables.product.prodname_ghe_server %} 上的活动。 自动检查更改或轮询将对实例的性能和可扩展性产生不利影响。 有关详细信息,请参阅“[关于更新](/github/extending-github/about-webhooks)”。 +**Warning:** We recommend that users configure webhook events to notify external systems of activity on {% data variables.product.prodname_ghe_server %}. Automated checks for changes, or _polling_, will negatively impact the performance and scalability of your instance. For more information, see "[About webhooks](/github/extending-github/about-webhooks)." {% endwarning %} -有关监视 {% data variables.product.prodname_ghe_server %} 的容量和性能的详细信息,请参阅“[监视设备](/admin/enterprise-management/monitoring-your-appliance)”。 +For more information about monitoring the capacity and performance of {% data variables.product.prodname_ghe_server %}, see "[Monitoring your appliance](/admin/enterprise-management/monitoring-your-appliance)." -您可以增加实例的 CPU 或内存资源。 有关详细信息,请参阅“[增加 CPU 或内存资源](/enterprise/admin/installation/increasing-cpu-or-memory-resources)”。 +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)." diff --git a/translations/zh-CN/data/reusables/enterprise_installation/hotpatching-explanation.md b/translations/zh-CN/data/reusables/enterprise_installation/hotpatching-explanation.md index 076badfeae..84970a0e35 100644 --- a/translations/zh-CN/data/reusables/enterprise_installation/hotpatching-explanation.md +++ b/translations/zh-CN/data/reusables/enterprise_installation/hotpatching-explanation.md @@ -4,4 +4,4 @@ You can use hotpatching to upgrade to a newer patch release, but not a feature r Hotpatches do not generally require a reboot. If a hotpatch does require a reboot, the {% data variables.product.product_name %} release notes will indicate the requirement. -Hotpatches require a configuration run, which can cause a brief period of errors or unresponsiveness for some or all services on {% data variables.product.product_location %}. You are not required to enable maintenance mode during installation of a hotpatch, but doing so will guarantee that users see a maintenance page instead of errors or timeouts. For more information, see "[Enabling and scheduling maintenance mode](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)." +Hotpatches require a configuration run, which can cause a brief period of errors or unresponsiveness for some or all services on {% data variables.location.product_location %}. You are not required to enable maintenance mode during installation of a hotpatch, but doing so will guarantee that users see a maintenance page instead of errors or timeouts. For more information, see "[Enabling and scheduling maintenance mode](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)." diff --git a/translations/zh-CN/data/reusables/enterprise_installation/image-urls-viewable-warning.md b/translations/zh-CN/data/reusables/enterprise_installation/image-urls-viewable-warning.md index 5fdc8061bb..ecff795df4 100644 --- a/translations/zh-CN/data/reusables/enterprise_installation/image-urls-viewable-warning.md +++ b/translations/zh-CN/data/reusables/enterprise_installation/image-urls-viewable-warning.md @@ -1,13 +1,5 @@ ---- -ms.openlocfilehash: 7f6ced813ea6d819b42c469ae1f285f6732ceeb4 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145097789" ---- {% warning %} -警告:如果你在拉取请求或议题评论中添加了图像附件,则任何人都可以查看匿名图像 URL,无需身份验证{% ifversion ghes %},即使该拉取请求位于专用存储库中或者启用了专用模式。 为防止未经授权而访问映像,请确保限制从网络访问提供映像的系统,包括 {% data variables.product.product_location %}{% endif %}。{% ifversion ghae %} 为防止未经授权而访问 {% data variables.product.product_name %} 上的映像 URL,请考虑限制到企业的网络流量。 有关详细信息,请参阅“[限制到企业的网络流量](/admin/configuration/restricting-network-traffic-to-your-enterprise)”。{% endif %} +**Warning:** If you add an image attachment to a pull request or issue comment, anyone can view the anonymized image URL without authentication{% ifversion ghes %}, 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.location.product_location %}{% endif %}.{% ifversion ghae %} 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 %} {% endwarning %} diff --git a/translations/zh-CN/data/reusables/enterprise_installation/ssh-into-instance.md b/translations/zh-CN/data/reusables/enterprise_installation/ssh-into-instance.md index 424bd4e6a5..86f7f9ac05 100644 --- a/translations/zh-CN/data/reusables/enterprise_installation/ssh-into-instance.md +++ b/translations/zh-CN/data/reusables/enterprise_installation/ssh-into-instance.md @@ -1,13 +1,5 @@ ---- -ms.openlocfilehash: 56d00170560f72e7e4fad39972422cf301b377be -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147876171" ---- -1. SSH 连接到 {% data variables.product.product_location %}。 如果实例包含多个节点,例如,如果配置了高可用性或异地复制,则通过 SSH 连接到主节点。 如果使用群集,则可以通过 SSH 连接到任何节点。 有关 SSH 访问的详细信息,请参阅“[访问管理 shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)”。 +1. SSH into {% data variables.location.product_location %}. If your instance comprises multiple nodes, for example if high availability or geo-replication are configured, SSH into the primary node. If you use a cluster, you can SSH into any node. For more information about SSH access, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)." ```shell - $ ssh -p 122 admin@HOSTNAME + $ ssh -p 122 admin@HOSTNAME ``` diff --git a/translations/zh-CN/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md index 667ae25e4d..4ab76aace6 100644 --- a/translations/zh-CN/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md +++ b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: ac036166292f405220029fb6290b1e0a1a278ecb -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145097693" ---- -休眠阈值是指用户必须多久不活动才被视为休眠。 默认休眠阈值是 90 天,但可以自定义 {% data variables.product.product_location %} 的休眠阈值。 +The dormancy threshold is the length of time a user must be inactive to be considered dormant. The default dormancy threshold is 90 days, however you can customize the dormancy threshold for {% data variables.location.product_location %}. diff --git a/translations/zh-CN/data/reusables/enterprise_site_admin_settings/sign-in.md b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/sign-in.md index 6d58a7d273..404565e28e 100644 --- a/translations/zh-CN/data/reusables/enterprise_site_admin_settings/sign-in.md +++ b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/sign-in.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 0370abebda6c2219a6ef19851958c45d7e4f595f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145097674" ---- -1. 在 `http(s)://HOSTNAME/login` 上登录 {% data variables.product.product_location %}。 +1. Sign in to {% data variables.location.product_location %} at `http(s)://HOSTNAME/login`. diff --git a/translations/zh-CN/data/reusables/enterprise_site_admin_settings/tls-downtime.md b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/tls-downtime.md index aff2378918..06f181e152 100644 --- a/translations/zh-CN/data/reusables/enterprise_site_admin_settings/tls-downtime.md +++ b/translations/zh-CN/data/reusables/enterprise_site_admin_settings/tls-downtime.md @@ -1,13 +1,5 @@ ---- -ms.openlocfilehash: 63560a19f1dc683ba1f02c35f0487aec236217a6 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147885754" ---- {% warning %} -**警告:** 配置 TLS 会导致 {% data variables.product.product_location %} 出现短暂停机。 +**Warning:** Configuring TLS causes a small amount of downtime for {% data variables.location.product_location %}. {% endwarning %} diff --git a/translations/zh-CN/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md b/translations/zh-CN/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md index 64dc2db166..a8ccf8f70b 100644 --- a/translations/zh-CN/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md +++ b/translations/zh-CN/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 6b4a4fbf8ba73127abab49f8fefc25e1a2d3fbca -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145065780" ---- -也可为 {% data variables.product.product_location %} 配置外部身份验证。 如果使用外部身份验证,则必须邀请用户通过身份验证提供程序使用实例。 有关详细信息,请参阅“[关于企业身份验证](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)”。 +Alternatively, you can configure external authentication for {% data variables.location.product_location %}. If you use external authentication, you must invite people to use your instance through your authentication provider. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)." diff --git a/translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md b/translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md index 791bac4670..d1c1d86a0d 100644 --- a/translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md +++ b/translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 0e38b9097fcac8c9c60b2b2056000e50f96a0c25 -ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147883591" ---- -当你对 {% data variables.product.product_location %} 使用内置身份验证时,每个人都会从邀请中或通过注册来创建个人帐户。 +When you use built-in authentication for {% data variables.location.product_location %}, each person creates a personal account from an invitation or by signing up. diff --git a/translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentication.md b/translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentication.md index 3fdb355bd2..49151a385f 100644 --- a/translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentication.md +++ b/translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentication.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: d50bb457fe9b5d4daee819a2597f573692aeaa12 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145097666" ---- -如果想要允许对某些在你的外部验证提供程序上无帐户的人员进行身份验证,则可以允许对 {% data variables.product.product_location %} 上的本地帐户进行回退身份验证。 有关详细信息,请参阅“[允许对提供程序外部的用户进行内置身份验证](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)”。 +If you want to allow authentication for some people who don't have an account on your external authentication provider, you can allow fallback authentication to local accounts on {% data variables.location.product_location %}. For more information, see "[Allowing built-in authentication for users outside your provider](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)." diff --git a/translations/zh-CN/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md b/translations/zh-CN/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md index b0b6058e83..c52e1e5433 100644 --- a/translations/zh-CN/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md +++ b/translations/zh-CN/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 68778a5aac47ae812ce7fca5219ce8f7e416b1af -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145065777" ---- -{% data variables.product.product_name %} 规范化 {% ifversion ghec or ghae %}IdP{% elsif ghes %}外部身份验证提供程序{% endif %} 中的值,以确定 {% ifversion ghae %}{% data variables.product.product_name %} 上{% elsif ghec %}企业中 {% data variables.product.product_location %} 上{% elsif ghes %} {% data variables.product.product_location %} 上{% endif %} 每个新个人帐户的用户名。 +{% data variables.product.product_name %} normalizes a value from your {% ifversion ghec or ghae %}IdP{% elsif ghes %}external authentication provider{% endif %} to determine the username for each new personal account {% ifversion ghae %}on {% data variables.product.product_name %}{% elsif ghec %}in your enterprise on {% data variables.location.product_location %}{% elsif ghes %}on {% data variables.location.product_location %}{% endif %}. diff --git a/translations/zh-CN/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md b/translations/zh-CN/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md index bd3b8727a2..7e914e8766 100644 --- a/translations/zh-CN/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md +++ b/translations/zh-CN/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md @@ -1,17 +1,9 @@ ---- -ms.openlocfilehash: b757e88a4ac3718fff996837dd8e00714f0cd7ad -ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147883583" ---- {% warning %} -警告: +**Warnings:** -- Git 协议未经身份验证且未加密。 攻击者可以拦截使用此协议通过连接传输的存储库数据。 -- 如果启用匿名 Git 读取访问,你将对此功能的所有访问和使用负责。 {% data variables.product.company_short %} 对功能的任何非预期访问、安全风险或误用概不负责。 -- 使用此功能不得违反 {% data variables.product.company_short %} 的许可,包括对 {% data variables.product.product_location %} 用户许可数的限制。 +- The Git protocol is unauthenticated and unencrypted. An attacker could intercept repository data transferred over connections using this protocol. +- If you enable anonymous Git read access, you're responsible for all access and use of the feature. {% data variables.product.company_short %} is not responsible for any unintended access, security risks, or misuse of the feature. +- You may not use this feature to violate your license from {% data variables.product.company_short %}, including the limit on the number of user licenses for {% data variables.location.product_location %}. {% endwarning %} diff --git a/translations/zh-CN/data/reusables/files/choose-commit-email.md b/translations/zh-CN/data/reusables/files/choose-commit-email.md index d89b89a3b1..e8e07c32bf 100644 --- a/translations/zh-CN/data/reusables/files/choose-commit-email.md +++ b/translations/zh-CN/data/reusables/files/choose-commit-email.md @@ -1,11 +1,4 @@ ---- -ms.openlocfilehash: e786a92aa48e8c2cb737f766aa20050c2fd94851 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145097653" ---- {% ifversion fpt or ghec %} -1. 如果在 {% data variables.product.product_location %} 上有多个电子邮件地址与你的帐户关联,请单击电子邮件地址下拉菜单,然后选择要用作 Git 作者电子邮件地址的电子邮件地址。 只有经过验证的电子邮件地址才会出现在此下拉菜单中。 如果启用了电子邮件地址隐私,则 `@users.noreply.github.com` 是默认提交作者的电子邮件地址。 有关详细信息,请参阅“[设置提交电子邮件地址](/articles/setting-your-commit-email-address)”。 -![选择提交电子邮件地址](/assets/images/help/repository/choose-commit-email-address.png) {% endif %} +1. If you have more than one email address associated with your account on {% data variables.location.product_location %}, click the email address drop-down menu and select the email address to use as the Git author email address. Only verified email addresses appear in this drop-down menu. If you enabled email address privacy, then `@users.noreply.github.com` is the default commit author email address. For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)." +![Choose commit email addresses](/assets/images/help/repository/choose-commit-email-address.png) +{% endif %} diff --git a/translations/zh-CN/data/reusables/getting-started/actions.md b/translations/zh-CN/data/reusables/getting-started/actions.md index b6a4d5eeec..c655219426 100644 --- a/translations/zh-CN/data/reusables/getting-started/actions.md +++ b/translations/zh-CN/data/reusables/getting-started/actions.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: aec556bebd25dc78544f0ed8250442014a4eba71 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147882093" ---- -使用 {% data variables.product.prodname_actions %},可以在 {% data variables.product.product_name %} 上自动执行和自定义 {% data variables.product.product_location %} 的开发工作流。 您可以创建自己的操作,以及使用和自定义 {% data variables.product.prodname_dotcom %} 社区分享的操作。 有关详细信息,请参阅“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。 +With {% data variables.product.prodname_actions %}, you can automate and customize {% data variables.location.product_location %}'s development workflow on {% data variables.product.product_name %}. You can create your own actions, and use and customize actions shared by the {% data variables.product.prodname_dotcom %} community. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." diff --git a/translations/zh-CN/data/reusables/getting-started/adding-members-to-organizations.md b/translations/zh-CN/data/reusables/getting-started/adding-members-to-organizations.md index 13a6478ca0..42d5f43d6f 100644 --- a/translations/zh-CN/data/reusables/getting-started/adding-members-to-organizations.md +++ b/translations/zh-CN/data/reusables/getting-started/adding-members-to-organizations.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 3b4d678bc4a5a023d7fbcced5c68a6ee5e66fc54 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145097543" ---- -只要是要管理的组织中的组织所有者,就可以将成员添加到 {% data variables.product.product_location %} 中的组织。 还可以配置组织成员身份的可见性。 有关详细信息,请参阅“[将人员添加到组织](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)”和“[配置组织成员身份的可见性](/admin/user-management/managing-organizations-in-your-enterprise/configuring-visibility-for-organization-membership)”。 +You can add members to organizations in {% data variables.location.product_location %} as long as you are an organization owner in the organizations you want to manage. You can also configure visibility of organization membership. For more information, see "[Adding people to your organization](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)" and "[Configuring visibility for organization membership](/admin/user-management/managing-organizations-in-your-enterprise/configuring-visibility-for-organization-membership)." diff --git a/translations/zh-CN/data/reusables/getting-started/configuring-security-features.md b/translations/zh-CN/data/reusables/getting-started/configuring-security-features.md index 218be199ab..be2ff1bb50 100644 --- a/translations/zh-CN/data/reusables/getting-started/configuring-security-features.md +++ b/translations/zh-CN/data/reusables/getting-started/configuring-security-features.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 8657ff2b842e749aa9fff25434a5587acf0ec448 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145097538" ---- -为了确保 {% ifversion ghes or ghae %} {% data variables.product.product_location %}{% else %}你的组织{% endif %} 中的组织安全,你可以使用各种 {% data variables.product.prodname_dotcom %} 安全功能,包括安全策略、依赖项图、机密扫描以及 Dependabot 安全和版本更新。 有关详细信息,请参阅“[保护组织](/code-security/getting-started/securing-your-organization)”和“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 +To keep {% ifversion ghes or ghae %}the organizations in {% data variables.location.product_location %}{% else %}your organization{% endif %} secure, you can use a variety of {% data variables.product.prodname_dotcom %} security features, including security policies, dependency graphs, secret scanning and Dependabot security and version updates. For more information, see "[Securing your organization](/code-security/getting-started/securing-your-organization)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." diff --git a/translations/zh-CN/data/reusables/getting-started/creating-organizations.md b/translations/zh-CN/data/reusables/getting-started/creating-organizations.md index 9bcd89ac6b..70551a4383 100644 --- a/translations/zh-CN/data/reusables/getting-started/creating-organizations.md +++ b/translations/zh-CN/data/reusables/getting-started/creating-organizations.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: ec82fc3572981a7f9fd81165c8fc40056bc56824 -ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147875993" ---- -可以在 {% data variables.product.product_location %} 中创建新组织以反映公司或组的结构。 有关详细信息,请参阅“[从头开始创建新组织](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)”。 +You can create new organizations in {% data variables.location.product_location %} to reflect your company or group's structure. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." diff --git a/translations/zh-CN/data/reusables/getting-started/enforcing-repo-management-policies.md b/translations/zh-CN/data/reusables/getting-started/enforcing-repo-management-policies.md index 8c1f70aa33..a684eecaa6 100644 --- a/translations/zh-CN/data/reusables/getting-started/enforcing-repo-management-policies.md +++ b/translations/zh-CN/data/reusables/getting-started/enforcing-repo-management-policies.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 01211e69f9b41fd5ca1af8bffc9bb73669dba023 -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147880354" ---- -作为企业所有者,你可以在 {% data variables.product.product_location %} 中为所有组织设置存储库管理策略,或者允许在每个组织中单独设置策略。 有关详细信息,请参阅“[在企业中实施存储库管理策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)”。 +As an enterprise owner, you can set repository management policies for all organizations in {% data variables.location.product_location %}, or allow policies to be set separately in each organization. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)." diff --git a/translations/zh-CN/data/reusables/getting-started/managing-enterprise-members.md b/translations/zh-CN/data/reusables/getting-started/managing-enterprise-members.md index 4f9373b0ac..7c74a811a0 100644 --- a/translations/zh-CN/data/reusables/getting-started/managing-enterprise-members.md +++ b/translations/zh-CN/data/reusables/getting-started/managing-enterprise-members.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: ab49c1d935838b59ead4931c40f837f331cc59eb -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145097507" ---- -你可以管理 {% data variables.product.product_location %} 成员的设置和审核活动。 你可以将企业成员 {% ifversion ghes %}提升为站点管理员、{% endif %}管理休眠用户、查看用户活动的审核日志以及自定义企业成员将看到的消息。 有关详细信息,请参阅“[管理企业中的用户](/admin/user-management/managing-users-in-your-enterprise)”。 +You can manage settings and audit activity for the members of {% data variables.location.product_location %}. You can {% ifversion ghes %}promote an enterprise member to be a site administrator, {% endif %}manage dormant users, view the audit log for user activity, and customize messages that enterprise members will see. For more information, see "[Managing users in your enterprise](/admin/user-management/managing-users-in-your-enterprise)." diff --git a/translations/zh-CN/data/reusables/git/git-push.md b/translations/zh-CN/data/reusables/git/git-push.md index 56f5a4deff..58c2a216e0 100644 --- a/translations/zh-CN/data/reusables/git/git-push.md +++ b/translations/zh-CN/data/reusables/git/git-push.md @@ -1,13 +1,5 @@ ---- -ms.openlocfilehash: a13765e853c204f45f461ecbfcf22ba168e8966a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145097469" ---- -1. [将本地存储库中的更改推送](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)到 {% data variables.product.product_location %}。 +1. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.location.product_location %}. ```shell - $ git push origin your-branch + $ git push origin YOUR_BRANCH # Pushes the changes in your local repository up to the remote repository you specified as the origin ``` diff --git a/translations/zh-CN/data/reusables/large_files/storage_assets_location.md b/translations/zh-CN/data/reusables/large_files/storage_assets_location.md index 6bf1983055..cfc3b76dfa 100644 --- a/translations/zh-CN/data/reusables/large_files/storage_assets_location.md +++ b/translations/zh-CN/data/reusables/large_files/storage_assets_location.md @@ -1,10 +1,3 @@ ---- -ms.openlocfilehash: eaee6a93767f4fb3a9f254f56d797f65d67129d5 -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147880346" ---- -{% ifversion ghes %} 默认情况下,{% data variables.large_files.product_name_long %} 客户端将大型资产存储在托管 Git 存储库的同一服务器上。 在 {% data variables.product.product_location %} 上启用 {% data variables.large_files.product_name_short %} 后,大型资产存储在 `/data/user/storage` 的数据分区中。 +{% ifversion ghes %} +By default, the {% data variables.large_files.product_name_long %} client stores large assets on the same server that hosts the Git repository. When {% data variables.large_files.product_name_short %} is enabled on {% data variables.location.product_location %}, large assets are stored on the data partition in `/data/user/storage`. {% endif %} diff --git a/translations/zh-CN/data/reusables/large_files/use_lfs_tip.md b/translations/zh-CN/data/reusables/large_files/use_lfs_tip.md index 382ae0c2bb..5c45786e34 100644 --- a/translations/zh-CN/data/reusables/large_files/use_lfs_tip.md +++ b/translations/zh-CN/data/reusables/large_files/use_lfs_tip.md @@ -1,13 +1,5 @@ ---- -ms.openlocfilehash: 3357b686e01b80c0148b2f7c4614718a550982aa -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145100741" ---- {% tip %} -提示:如果经常推送大型文件到 {% data variables.product.product_location %},请考虑使用 {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %})。 有关详细信息,请参阅“[大型文件版本控制](/articles/versioning-large-files)”。 +**Tip:** If you regularly push large files to {% data variables.location.product_location %}, consider using {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). For more information, see "[Versioning large files](/articles/versioning-large-files)." {% endtip %} diff --git a/translations/zh-CN/data/reusables/notifications/outbound_email_tip.md b/translations/zh-CN/data/reusables/notifications/outbound_email_tip.md index 5cc9237aec..e8f714d69a 100644 --- a/translations/zh-CN/data/reusables/notifications/outbound_email_tip.md +++ b/translations/zh-CN/data/reusables/notifications/outbound_email_tip.md @@ -1,13 +1,7 @@ ---- -ms.openlocfilehash: ce7f7a00c03950eff6f829e4715ba3aac0606ad6 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147884363" ---- -{% ifversion ghes or ghae %} {% note %} +{% ifversion ghes or ghae %} +{% note %} -注意:只有在 {% data variables.product.product_location %} 上启用出站电子邮件支持时,才会收到电子邮件通知。 更多信息请联系站点管理员。 +**Note**: You'll only receive email notifications if outbound email support is enabled on {% data variables.location.product_location %}. For more information, contact your site administrator. -{% endnote %} {% endif %} +{% endnote %} +{% endif %} diff --git a/translations/zh-CN/data/reusables/notifications/shared_state.md b/translations/zh-CN/data/reusables/notifications/shared_state.md index dc4a2f89dd..76f7bb93f6 100644 --- a/translations/zh-CN/data/reusables/notifications/shared_state.md +++ b/translations/zh-CN/data/reusables/notifications/shared_state.md @@ -1,5 +1,5 @@ {% tip %} -**Tip:** If you receive both web and email notifications, you can automatically sync the read or unread status of the notification so that web notifications are automatically marked as read once you've read the corresponding email notification. To enable this sync, your email client must be able to view images from {% ifversion fpt or ghec %}`notifications@github.com`{% else %}the `no-reply` email address {% ifversion ghae %}for your {% data variables.product.product_name %} hostname{% elsif ghes %}for {% data variables.product.product_location %}, which your site administrator configures{% endif %}{% endif %}. +**Tip:** If you receive both web and email notifications, you can automatically sync the read or unread status of the notification so that web notifications are automatically marked as read once you've read the corresponding email notification. To enable this sync, your email client must be able to view images from {% ifversion fpt or ghec %}`notifications@github.com`{% else %}the `no-reply` email address {% ifversion ghae %}for your {% data variables.product.product_name %} hostname{% elsif ghes %}for {% data variables.location.product_location %}, which your site administrator configures{% endif %}{% endif %}. {% endtip %} diff --git a/translations/zh-CN/data/reusables/organizations/navigate-to-org.md b/translations/zh-CN/data/reusables/organizations/navigate-to-org.md index cedfc07ef4..ef3f95d2c2 100644 --- a/translations/zh-CN/data/reusables/organizations/navigate-to-org.md +++ b/translations/zh-CN/data/reusables/organizations/navigate-to-org.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: fbf26f7ab8e188cea909554cba9edd5d6ab4ca6c -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145100551" ---- -1. 在 {% data variables.product.product_location %} 上,导航到组织的主页。 +1. On {% data variables.location.product_location %}, navigate to the main page of the organization. diff --git a/translations/zh-CN/data/reusables/package_registry/authenticate-packages.md b/translations/zh-CN/data/reusables/package_registry/authenticate-packages.md index 1f0dfef4e3..bc3e424d23 100644 --- a/translations/zh-CN/data/reusables/package_registry/authenticate-packages.md +++ b/translations/zh-CN/data/reusables/package_registry/authenticate-packages.md @@ -1,15 +1,9 @@ ---- -ms.openlocfilehash: fd3590bb212b7c9521cb447ca012b19270469a8c -ms.sourcegitcommit: 22d665055b1bee7a5df630385e734e3a149fc720 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 07/13/2022 -ms.locfileid: "145100405" ---- -需要访问令牌才能发布、安装和删除包。 +{% data reusables.package_registry.packages-classic-pat-only %} -可使用个人访问令牌 (PAT) 向 {% data variables.product.prodname_registry %} 或 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 进行身份验证。 创建个人访问令牌时,可根据需要为令牌分配不同的作用域。 有关 PAT 的包相关范围的详细信息,请参阅“[关于 GitHub Packages 的权限](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)”。 +You need an access token to publish, install, and delete private, internal, and public packages. -要在 {% data variables.product.prodname_actions %} 工作流程内向 {% data variables.product.prodname_registry %} 注册表验证,您可以使用: -- `GITHUB_TOKEN` 发布与工作流存储库相关联的包。 -- PAT 来安装与其他专用存储库(`GITHUB_TOKEN` 无法访问)相关联的包。 +You can use a {% data variables.product.pat_v1 %} to authenticate to {% data variables.product.prodname_registry %} or the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API. When you create a {% data variables.product.pat_v1 %}, you can assign the token different scopes depending on your needs. For more information about packages-related scopes for a {% data variables.product.pat_v1 %}, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)." + +To authenticate to a {% data variables.product.prodname_registry %} registry within a {% data variables.product.prodname_actions %} workflow, you can use: +- `GITHUB_TOKEN` to publish packages associated with the workflow repository. +- a {% data variables.product.pat_v1 %} with at least `packages:read` scope to install packages associated with other private repositories (which `GITHUB_TOKEN` can't access). diff --git a/translations/zh-CN/data/reusables/package_registry/authenticate-to-container-registry-steps.md b/translations/zh-CN/data/reusables/package_registry/authenticate-to-container-registry-steps.md index 5034e62dd8..cc61c65d06 100644 --- a/translations/zh-CN/data/reusables/package_registry/authenticate-to-container-registry-steps.md +++ b/translations/zh-CN/data/reusables/package_registry/authenticate-to-container-registry-steps.md @@ -1,29 +1,23 @@ ---- -ms.openlocfilehash: 50e7f623d6585c8697d0b1c6c827a855df26c571 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145100394" ---- -1. 针对要完成的任务,新创具有适当作用域的个人访问令牌 (PAT)。 如果您的组织需要 SSO,则必须为新令牌启用 SSO。 +{% data reusables.package_registry.packages-classic-pat-only %} + +1. Create a new {% data variables.product.pat_v1 %} with the appropriate scopes for the tasks you want to accomplish. If your organization requires SSO, you must enable SSO for your new token. {% warning %} - 注意:默认情况下,在用户界面中为个人访问令牌 (PAT) 选择 `write:packages` 范围时,`repo` 范围也将被选中。 `repo` 范围提供了不必要和广泛的访问权限,我们建议你尤其避免使用 GitHub Actions 工作流。 有关详细信息,请参阅“[GitHub Actions 的安全强化](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)”。 解决方法是在以下 URL 的用户界面中为 PAT 选择 `write:packages` 范围:`https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/settings/tokens/new?scopes=write:packages`。 + **Note:** By default, when you select the `write:packages` scope for your {% data variables.product.pat_v1 %} in the user interface, the `repo` scope will also be selected. The `repo` scope offers unnecessary and broad access, which we recommend you avoid using for {% data variables.product.prodname_actions %} workflows in particular. For more information, see "[Security hardening for GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)." As a workaround, you can select just the `write:packages` scope for your {% data variables.product.pat_v1 %} in the user interface with this url: `https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/settings/tokens/new?scopes=write:packages`. {% endwarning %} - - 选择 `read:packages` 范围以下载容器映像并读取其元数据。 - - 选择 `write:packages` 范围以下载和上传容器映像并读写其元数据。 - - 选择 `delete:packages` 范围以删除容器映像。 + - Select the `read:packages` scope to download container images and read their metadata. + - Select the `write:packages` scope to download and upload container images and read and write their metadata. + - Select the `delete:packages` scope to delete container images. - 有关详细信息,请参阅“[为命令行创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)”。 + For more information, see "[Creating a {% data variables.product.pat_generic %} for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)." -2. 保存您的 PAT。 我们建议将 PAT 保存为环境变量。 +2. Save your {% data variables.product.pat_v1 %}. We recommend saving your token as an environment variable. ```shell $ export CR_PAT=YOUR_TOKEN ``` -3. 使用容器类型的 CLI,登录到 `{% data reusables.package_registry.container-registry-hostname %}` 上的 {% data variables.product.prodname_container_registry %} 服务。 +3. Using the CLI for your container type, sign in to the {% data variables.product.prodname_container_registry %} service at `{% data reusables.package_registry.container-registry-hostname %}`. {% raw %} ```shell $ echo $CR_PAT | docker login {% endraw %}{% data reusables.package_registry.container-registry-hostname %}{% raw %} -u USERNAME --password-stdin diff --git a/translations/zh-CN/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md b/translations/zh-CN/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md index 9b27c02af4..7a5938bed8 100644 --- a/translations/zh-CN/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md +++ b/translations/zh-CN/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md @@ -1,11 +1,3 @@ ---- -ms.openlocfilehash: 41b658e6f15ac145ddb7637a1d0ae328b50b8af2 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145100373" ---- -作为下一步,您可以自定义您想要提供给最终用户的 {% data variables.product.product_location %} 软件包生态系统。 有关详细信息,请参阅“[为企业配置包生态系统支持](/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)”。 +As a next step, you can customize which package ecosystems you would like to make available to end users on {% data variables.location.product_location %}. For more information, see "[Configuring package ecosystem support for your enterprise](/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." -有关在 {% data variables.product.prodname_dotcom %} 上使用 {% data variables.product.prodname_registry %} 的概述,请参阅“[开始为你的企业使用 GitHub Packages](/admin/packages/getting-started-with-github-packages-for-your-enterprise)”。 +For an overview of getting started with {% data variables.product.prodname_registry %} on {% data variables.product.prodname_dotcom %}, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." diff --git a/translations/zh-CN/data/reusables/package_registry/package-registry-with-github-tokens.md b/translations/zh-CN/data/reusables/package_registry/package-registry-with-github-tokens.md index 4cc3fa2cb3..e6f45e55dd 100644 --- a/translations/zh-CN/data/reusables/package_registry/package-registry-with-github-tokens.md +++ b/translations/zh-CN/data/reusables/package_registry/package-registry-with-github-tokens.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 12305a068862ac705c591ff473e7170dd8b9e3f5 -ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/12/2022 -ms.locfileid: "145100371" ---- -如果使用的是 {% data variables.product.prodname_actions %} 工作流,可使用 `GITHUB_TOKEN` 发布和使用 {% data variables.product.prodname_registry %} 中的包,而无需存储和管理个人访问令牌。 有关详细信息,请参阅“[使用 `GITHUB_TOKEN` 进行身份验证](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)”。 +If you are using a {% data variables.product.prodname_actions %} workflow, you can use a `GITHUB_TOKEN` to publish and consume packages in {% data variables.product.prodname_registry %} without needing to store and manage a {% data variables.product.pat_generic %}. For more information, see "[Authenticating with the `GITHUB_TOKEN`](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." diff --git a/translations/zh-CN/data/reusables/package_registry/packages-billing.md b/translations/zh-CN/data/reusables/package_registry/packages-billing.md index c878f11167..07e599fb33 100644 --- a/translations/zh-CN/data/reusables/package_registry/packages-billing.md +++ b/translations/zh-CN/data/reusables/package_registry/packages-billing.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: ac24f76da582d8aaa7f7a0cbba7d15ab80f95629 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147883778" ---- -公共包免费使用 {% data variables.product.prodname_registry %}。 对于专用包,每个 {% data variables.product.product_location %} 帐户可获得一定数量的免费存储和数据传输,具体取决于帐户所使用的产品。 超出包含数量的任何使用量都由支出限制控制。 +{% data variables.product.prodname_registry %} usage is free for public packages. For private packages, each account on {% data variables.location.product_location %} receives a certain amount of free storage and data transfer, depending on the product used with the account. Any usage beyond the included amounts is controlled by spending limits. diff --git a/translations/zh-CN/data/reusables/package_registry/required-scopes.md b/translations/zh-CN/data/reusables/package_registry/required-scopes.md index ce01ed8fd3..9a69fbda9b 100644 --- a/translations/zh-CN/data/reusables/package_registry/required-scopes.md +++ b/translations/zh-CN/data/reusables/package_registry/required-scopes.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 63e116796a07c20d4a6bbb14cfd493f3c2bc09fe -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145100350" ---- -您必须使用具有适当范围的个人访问令牌才可在 {% data variables.product.prodname_registry %} 中发布和安装。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-github-packages#authenticating-to-github-packages)”。 +You must use a {% data variables.product.pat_v1 %} with the appropriate scopes to publish and install packages in {% data variables.product.prodname_registry %}. For more information, see "[About {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-github-packages#authenticating-to-github-packages)." diff --git a/translations/zh-CN/data/reusables/pages/build-failure-email-server.md b/translations/zh-CN/data/reusables/pages/build-failure-email-server.md index c87d2b049e..89e9253b46 100644 --- a/translations/zh-CN/data/reusables/pages/build-failure-email-server.md +++ b/translations/zh-CN/data/reusables/pages/build-failure-email-server.md @@ -1,13 +1,7 @@ ---- -ms.openlocfilehash: f206838932fe094447f63dd9005f14252f3c8439 -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147876077" ---- -{% ifversion ghes or ghae %} {% tip %} +{% ifversion ghes or ghae %} + {% tip %} - 只有在 {% data variables.product.product_location %} 上启用出站电子邮件支持时,才会收到电子邮件。 更多信息请联系站点管理员。 + You will only receive an email if outbound email support is enabled on {% data variables.location.product_location %}. For more information, contact your site administrator. - {% endtip %} {% endif %} + {% endtip %} +{% endif %} diff --git a/translations/zh-CN/data/reusables/pages/emu-org-only.md b/translations/zh-CN/data/reusables/pages/emu-org-only.md index 6700ef03b8..fb1844ee17 100644 --- a/translations/zh-CN/data/reusables/pages/emu-org-only.md +++ b/translations/zh-CN/data/reusables/pages/emu-org-only.md @@ -1,13 +1,7 @@ ---- -ms.openlocfilehash: 25b8700240c49223cdd987beb555e15102d41844 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147061000" ---- -{% ifversion ghec %} {% note %} +{% ifversion ghec %} +{% note %} -注意:如果你是 {% data variables.product.prodname_managed_user %},将只能从组织拥有的存储库发布 {% data variables.product.prodname_pages %} 站点。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)”。 +**Note:** If you're a {% data variables.enterprise.prodname_managed_user %}, you can only publish {% data variables.product.prodname_pages %} sites from repositories owned by organizations. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)." -{% endnote %} {% endif %} +{% endnote %} +{% endif %} diff --git a/translations/zh-CN/data/reusables/projects/enable-basic-workflow.md b/translations/zh-CN/data/reusables/projects/enable-basic-workflow.md index 15ba6f8114..715219b099 100644 --- a/translations/zh-CN/data/reusables/projects/enable-basic-workflow.md +++ b/translations/zh-CN/data/reusables/projects/enable-basic-workflow.md @@ -1,21 +1,17 @@ ---- -ms.openlocfilehash: 0c55df675453a0707e8695cbca9087c5b585c438 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147423658" ---- -1. 导航到你的项目。 -1. 在右上角,单击 {% octicon "kebab-horizontal" aria-label="The menu icon" %} 以打开菜单。 - ![显示菜单图标的屏幕截图](/assets/images/help/projects-v2/open-menu.png) -1. 在菜单中,单击“{% octicon "workflow" aria-label="The workflow icon" %} 工作流”。 - ![显示“工作流”菜单项的屏幕截图](/assets/images/help/projects-v2/workflows-menu-item.png) -1. 在“默认工作流”下,单击要编辑的工作流。 - ![显示默认工作流的屏幕截图](/assets/images/help/projects-v2/default-workflows.png) -1. 如果工作流可以同时应用于议题和拉取请求,请在“何时”旁边检查要处理的项类型。 - ![显示工作流的“何时”配置的屏幕截图](/assets/images/help/projects-v2/workflow-when.png) -1. 在“设置”旁边,选择要将状态设置为的值。 - ![显示工作流的“设置”配置的屏幕截图](/assets/images/help/projects-v2/workflow-set.png) -1. 如果已禁用工作流,请单击“已禁用”旁边的开关以启用工作流。 - ![显示工作流的“启用”控件的屏幕截图](/assets/images/help/projects-v2/workflow-enable.png) +{% data reusables.projects.access-workflows %} +1. Under **Default workflows**, click on the workflow that you want to edit. + + ![Screenshot showing default workflows](/assets/images/help/projects-v2/default-workflows.png) + +2. If the workflow can apply to both issues and pull requests, next to **When**, check the item type(s) that you want to act on. + + ![Screenshot showing the "when" configuration for a workflow](/assets/images/help/projects-v2/workflow-when.png) + +3. Next to **Set**, choose the value that you want to set the status to. + + ![Screenshot showing the "set" configuration for a workflow](/assets/images/help/projects-v2/workflow-set.png) + +4. If the workflow is disabled, click the toggle next to **Off** to enable the workflow. + + ![Screenshot showing the "On/Off" control for a workflow](/assets/images/help/projects-v2/workflow-enable.png) + diff --git a/translations/zh-CN/data/reusables/pull_requests/configure_pull_request_merges_intro.md b/translations/zh-CN/data/reusables/pull_requests/configure_pull_request_merges_intro.md index be7784445e..48ec676b37 100644 --- a/translations/zh-CN/data/reusables/pull_requests/configure_pull_request_merges_intro.md +++ b/translations/zh-CN/data/reusables/pull_requests/configure_pull_request_merges_intro.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: d9e267c4a5a718fd45107ff259dd9499560d158e -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/09/2022 -ms.locfileid: "147876050" ---- -您可以在 {% data variables.product.product_location %} 上配置拉取请求合并选项,以满足您的工作流程需要和用于管理 Git 历史记录的首选项。 有关详细信息,请参阅“[配置拉取请求合并](/articles/configuring-pull-request-merges)”。 +You can configure pull request merge options on {% data variables.location.product_location %} to meet your workflow needs and preferences for managing Git history. For more information, see "[Configuring pull request merges](/articles/configuring-pull-request-merges)." diff --git a/translations/zh-CN/data/reusables/pull_requests/default_merge_option.md b/translations/zh-CN/data/reusables/pull_requests/default_merge_option.md index 46ab31a218..7336d235d6 100644 --- a/translations/zh-CN/data/reusables/pull_requests/default_merge_option.md +++ b/translations/zh-CN/data/reusables/pull_requests/default_merge_option.md @@ -1,13 +1,5 @@ ---- -ms.openlocfilehash: 592835351230fe7a5587c0212811899ab496e84d -ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147872778" ---- -在 {% data variables.product.product_location %} 上的拉取请求上单击默认的“合并拉取请求”选项时,来自功能分支的所有提交都会在合并提交中添加到基础分支。 使用[ `--no-ff` 选项](https://git-scm.com/docs/git-merge#_fast_forward_merge)合并拉取请求。 +When you click the default **Merge pull request** option on a pull request on {% data variables.location.product_location %}, all commits from the feature branch are added to the base branch in a merge commit. The pull request is merged using [the `--no-ff` option](https://git-scm.com/docs/git-merge#_fast_forward_merge). -若要合并拉取请求,必须在存储库中拥有[写入权限](/articles/repository-permission-levels-for-an-organization/)。 +To merge pull requests, you must have [write permissions](/articles/repository-permission-levels-for-an-organization/) in the repository. ![standard-merge-commit-diagram](/assets/images/help/pull_requests/standard-merge-commit-diagram.png) diff --git a/translations/zh-CN/data/reusables/pull_requests/pull_request_merges_and_contributions.md b/translations/zh-CN/data/reusables/pull_requests/pull_request_merges_and_contributions.md index 6a3f43ed38..e157092539 100644 --- a/translations/zh-CN/data/reusables/pull_requests/pull_request_merges_and_contributions.md +++ b/translations/zh-CN/data/reusables/pull_requests/pull_request_merges_and_contributions.md @@ -1,15 +1,7 @@ ---- -ms.openlocfilehash: fdea0ab10c821f00e16a11eb57a49415b4f5c908 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147882961" ---- {% note %} -注意:{% ifversion ghes or ghae %} -- 要显示在您的个人资料贡献图中,合作提交必须符合与只有一个作者的提交相同的条件。{% endif %} -- 在变基提交时,提交的原作者和提交的变基者(无论是在命令行还是 {% data variables.product.product_location %} 上)都会获得贡献积分。 +**Notes:**{% ifversion ghes or ghae %} +- To appear on your profile contributions graph, co-authored commits must meet the same criteria as commits with one author.{% endif %} +- When rebasing commits, the original authors of the commit and the person who rebased the commits, whether on the command line or on {% data variables.location.product_location %}, receive contribution credit. {% endnote %} 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 c684efad52..93a7e1e17f 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 @@ -1,15 +1,7 @@ ---- -ms.openlocfilehash: 371057b7fbe8e92b564e8729b11442bdbf2c1a56 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147882793" ---- -在 {% data variables.product.product_location %} 上的拉取请求中选择“变基并合并”选项时,来自主题分支(或头部分支)的所有提交都会单独添加到基分支,而无需合并提交。 这样,通过维护线性项目历史记录,变基和合并行为类似于[快进合并](https://git-scm.com/docs/git-merge#_fast_forward_merge)。 但是,变基是通过在基分支上用新的提交重写提交历史记录来实现的。 +When you select the **Rebase and merge** option on a pull request on {% data variables.location.product_location %}, all commits from the topic branch (or head branch) are added onto the base branch individually without a merge commit. In that way, the rebase and merge behavior resembles a [fast-forward merge](https://git-scm.com/docs/git-merge#_fast_forward_merge) by maintaining a linear project history. However, rebasing achieves this by re-writing the commit history on the base branch with new commits. -{% data variables.product.product_name %} 上的变基和合并行为与 `git rebase` 略有偏差。 {% data variables.product.prodname_dotcom %} 上的变基和合并始终会更新提交者信息并创建新的提交 SHA,而 {% data variables.product.prodname_dotcom %} 外部的 `git rebase` 在提交原型上发生变基时不改变提交者信息。 有关 `git rebase` 的详细信息,请参阅 Git 文档中的 [git-revert](https://git-scm.com/docs/git-rebase)。 +The rebase and merge behavior on {% data variables.product.product_name %} deviates slightly from `git rebase`. Rebase and merge on {% data variables.product.prodname_dotcom %} will always update the committer information and create new commit SHAs, whereas `git rebase` outside of {% data variables.product.prodname_dotcom %} does not change the committer information when the rebase happens on top of an ancestor commit. For more information about `git rebase`, see [git-rebase](https://git-scm.com/docs/git-rebase) in the Git documentation. -若要变基并合并拉取请求,必须在存储库中具有[写入权限](/articles/repository-permission-levels-for-an-organization/),并且存储库必须[允许变基合并](/articles/configuring-commit-rebasing-for-pull-requests/)。 +To rebase and merge pull requests, you must have [write permissions](/articles/repository-permission-levels-for-an-organization/) in the repository, and the repository must [allow rebase merging](/articles/configuring-commit-rebasing-for-pull-requests/). -有关 `git rebase` 的可视化表示形式,请参阅[《Pro Git》一书中的“Git 分支 - 变基”章节](https://git-scm.com/book/en/Git-Branching-Rebasing)。 +For a visual representation of `git rebase`, see [The "Git Branching - Rebasing" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Branching-Rebasing). diff --git a/translations/zh-CN/data/reusables/pull_requests/squash_and_merge_summary.md b/translations/zh-CN/data/reusables/pull_requests/squash_and_merge_summary.md index 52379c1d54..b0f3fc47cc 100644 --- a/translations/zh-CN/data/reusables/pull_requests/squash_and_merge_summary.md +++ b/translations/zh-CN/data/reusables/pull_requests/squash_and_merge_summary.md @@ -1,15 +1,7 @@ ---- -ms.openlocfilehash: c7eea7975ef49a5a6e3deed2ade3cb6bb5543ac0 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145099524" ---- -对 {% data variables.product.product_location %} 上的拉取请求选择“压缩并合并”选项时,拉取请求的提交会压缩为单一提交。 不是从主题分支查看所有贡献者的个别提交,而是所有提交合并成一个提交并合并到默认分支。 使用[快进选项](https://git-scm.com/docs/git-merge#_fast_forward_merge)合并包含已压缩提交的拉取请求。 +When you select the **Squash and merge** option on a pull request on {% data variables.location.product_location %}, the pull request's commits are squashed into a single commit. Instead of seeing all of a contributor's individual commits from a topic branch, the commits are combined into one commit and merged into the default branch. Pull requests with squashed commits are merged using the [fast-forward option](https://git-scm.com/docs/git-merge#_fast_forward_merge). -若要压缩并合并拉取请求,必须在存储库中具有[写入权限](/articles/repository-permission-levels-for-an-organization/),并且存储库必须[允许压缩合并](/articles/configuring-commit-squashing-for-pull-requests/)。 +To squash and merge pull requests, you must have [write permissions](/articles/repository-permission-levels-for-an-organization/) in the repository, and the repository must [allow squash merging](/articles/configuring-commit-squashing-for-pull-requests/). ![commit-squashing-diagram](/assets/images/help/pull_requests/commit-squashing-diagram.png) -您可以使用压缩并合并在仓库中创建更简化的 Git 历史记录。 在功能分支上工作时,提交正在进行的工作会有帮助,但它们不一定必须留在 Git 历史记录中。 如果在合并到默认分支时将这些提交压缩到一个提交中,您可以保留原来的更改并清除 Git 历史记录。 +You can use squash and merge to create a more streamlined Git history in your repository. Work-in-progress commits are helpful when working on a feature branch, but they aren’t necessarily important to retain in the Git history. If you squash these commits into one commit while merging to the default branch, you can retain the original changes with a clear Git history. diff --git a/translations/zh-CN/data/reusables/repositories/deploy-keys.md b/translations/zh-CN/data/reusables/repositories/deploy-keys.md index 14800aa694..595c8025c5 100644 --- a/translations/zh-CN/data/reusables/repositories/deploy-keys.md +++ b/translations/zh-CN/data/reusables/repositories/deploy-keys.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: f4ea2cee931b8d44b44f0febba3304f41bac404c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145086843" ---- -可以使用部署密钥(即授予对单个存储库的访问权限的 SSH 密钥)从 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的存储库启动项目到服务器。 {% data variables.product.product_name %} 将密钥的公共部分直接附加到存储库而不是个人帐户,密钥的私有部分仍保留在服务器上。 有关详细信息,请参阅“[传递部署](/rest/guides/delivering-deployments)”。 +You can launch projects from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} to your server by using a deploy key, which is an SSH key that grants access to a single repository. {% data variables.product.product_name %} attaches the public part of the key directly to your repository instead of a personal account, and the private part of the key remains on your server. For more information, see "[Delivering deployments](/rest/guides/delivering-deployments)." diff --git a/translations/zh-CN/data/reusables/repositories/enable-security-alerts.md b/translations/zh-CN/data/reusables/repositories/enable-security-alerts.md index 582377494b..ff83465bcd 100644 --- a/translations/zh-CN/data/reusables/repositories/enable-security-alerts.md +++ b/translations/zh-CN/data/reusables/repositories/enable-security-alerts.md @@ -1,10 +1,3 @@ ---- -ms.openlocfilehash: 6151a441ef782d82bde352a9761dbd19b239447c -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "146455699" ---- -{% ifversion ghes or ghae %} 企业所有者必须对 {% data variables.product.product_location %} 启用 {% data variables.product.prodname_dependabot_alerts %},然后才能使用此功能。 有关详细信息,请参阅“[对企业启用 {% data variables.product.prodname_dependabot %}](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)”。 +{% ifversion ghes or ghae %} +Enterprise owners must enable {% data variables.product.prodname_dependabot_alerts %} for {% data variables.location.product_location %} before you can use this feature. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% endif %} diff --git a/translations/zh-CN/data/reusables/repositories/navigate-to-repo.md b/translations/zh-CN/data/reusables/repositories/navigate-to-repo.md index e42a71fee7..6069ceab1f 100644 --- a/translations/zh-CN/data/reusables/repositories/navigate-to-repo.md +++ b/translations/zh-CN/data/reusables/repositories/navigate-to-repo.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: c76385e14b4b841b3e24342316a3026b3cd025d8 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145086804" ---- -1. 在 {% data variables.product.product_location %} 上,导航到存储库的主页。 +1. On {% data variables.location.product_location %}, navigate to the main page of the repository. diff --git a/translations/zh-CN/data/reusables/repositories/you-can-fork.md b/translations/zh-CN/data/reusables/repositories/you-can-fork.md index 65fe735433..a38402202e 100644 --- a/translations/zh-CN/data/reusables/repositories/you-can-fork.md +++ b/translations/zh-CN/data/reusables/repositories/you-can-fork.md @@ -1,14 +1,9 @@ ---- -ms.openlocfilehash: 7ab0c705855f1bd271c17eacc9a2533184d1b5f1 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145099344" ---- -{% ifversion ghae %} 如果企业的策略允许为专用和内部存储库创建分支,可以将存储库分支创建到个人帐户或你拥有存储库创建权限的组织。 有关详细信息,请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。 +{% ifversion ghae %} +If the policies for your enterprise permit forking private and internal repositories, you can fork a repository to your personal account or an organization where you have repository creation permissions. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." -{% elsif ghes or ghec %} 如果存储库和企业策略设置允许创建分支,可以将专用或内部存储库分支创建到个人帐户或 {% data variables.product.product_location %} 上你拥有存储库创建权限的组织。 +{% elsif ghes or ghec %} +You can fork a private or internal repository to your personal account or an organization on {% data variables.location.product_location %} where you have repository creation permissions, if settings for the repository and your enterprise policies allow forking. -{% elsif fpt %} 如果有权访问专用存储库并且所有者允许创建分支,可以将存储库分支创建到个人帐户,或 {% data variables.product.prodname_team %} 上你拥有存储库创建权限的组织。 不能使用 {% data variables.product.prodname_free_team %} 将专用存储库分支创建到组织。 有关详细信息,请参阅“[GitHub 的产品](/articles/githubs-products)”。 +{% elsif fpt %} +If you have access to a private repository and the owner permits forking, you can fork the repository to your personal account, or an organization on {% data variables.product.prodname_team %} where you have repository creation permissions. You cannot fork a private repository to an organization using {% data variables.product.prodname_free_team %}. For more information, see "[GitHub's products](/articles/githubs-products)." {% endif %} diff --git a/translations/zh-CN/data/reusables/rest-api/dotcom-only-guide-note.md b/translations/zh-CN/data/reusables/rest-api/dotcom-only-guide-note.md index ae83ed9519..86e1a648f1 100644 --- a/translations/zh-CN/data/reusables/rest-api/dotcom-only-guide-note.md +++ b/translations/zh-CN/data/reusables/rest-api/dotcom-only-guide-note.md @@ -1,20 +1,12 @@ ---- -ms.openlocfilehash: 5cbc48e80c619e40633c439535319ebf617c7d04 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145099339" ---- {% ifversion not fpt or ghec %} {% note %} -**注意**:以下指南对 {% data variables.product.prodname_dotcom_the_website %} 使用 REST API。 +**Note**: The following guide uses the REST API for {% data variables.product.prodname_dotcom_the_website %}. -- 使用 {% data variables.product.api_url_pre %} 访问 {% data variables.product.product_name %} 的 API。 +- Use {% data variables.product.api_url_pre %} to access the API for {% data variables.product.product_name %}. -- 指南指定了可能在 {% data variables.product.product_location %} 上不存在的用户名和仓库。 您可能需要使用不同的名称才能看到类似的输出。 +- The guide specifies usernames and repositories that may not exist on {% data variables.location.product_location %}. You may need to use different names to see similar output. {% endnote %} diff --git a/translations/zh-CN/data/reusables/saml/about-authorized-credentials.md b/translations/zh-CN/data/reusables/saml/about-authorized-credentials.md index c529c5ae78..87664ef3bc 100644 --- a/translations/zh-CN/data/reusables/saml/about-authorized-credentials.md +++ b/translations/zh-CN/data/reusables/saml/about-authorized-credentials.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: ac85c101df8f64a7d5e69202cd0c5280bb956b96 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145129616" ---- -您可以看到被授权进行 API 和 Git 访问的每个个人访问令牌和 SSH 密钥。 每个令牌或密钥只有最后几个字符可见。 如有必要,与该成员合作确定您应撤销哪些凭据。 +You can see each {% data variables.product.pat_generic %} and SSH key that a member has authorized for API and Git access. Only the last several characters of each token or key are visible. If necessary, work with the member to determine which credentials you should revoke. diff --git a/translations/zh-CN/data/reusables/saml/about-linked-identities.md b/translations/zh-CN/data/reusables/saml/about-linked-identities.md index cf495adf08..e1a8512bad 100644 --- a/translations/zh-CN/data/reusables/saml/about-linked-identities.md +++ b/translations/zh-CN/data/reusables/saml/about-linked-identities.md @@ -1,11 +1,3 @@ ---- -ms.openlocfilehash: bb556d0f51869d61db7d0aa1fcaa4c294303581d -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145099333" ---- -可查看成员已关联到其 {% data variables.product.product_location %} 帐户的单一登录标识。 +You can view the single sign-on identity that a member has linked to their account on {% data variables.location.product_location %}. -如果成员将错误的标识关联到其 {% data variables.product.product_location %} 帐户,你可以撤销关联的标识以允许该成员重试。 +If a member links the wrong identity to their account on {% data variables.location.product_location %}, you can revoke the linked identity to allow the member to try again. diff --git a/translations/zh-CN/data/reusables/saml/about-saml-access-enterprise-account.md b/translations/zh-CN/data/reusables/saml/about-saml-access-enterprise-account.md index d062a4b1ec..08cacea2fa 100644 --- a/translations/zh-CN/data/reusables/saml/about-saml-access-enterprise-account.md +++ b/translations/zh-CN/data/reusables/saml/about-saml-access-enterprise-account.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 94a2fb153d6929e6e319a10b95dfb4fb99ab949d -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145129615" ---- -要在 {% data variables.product.product_name %} 上访问每个组织的资源,成员必须在其浏览器中启动 SAML 会话。 要使用 API 和 Git 访问每个组织的受保护资源,成员必须使用被授权在组织中使用的个人访问令牌或 SSH 密钥。 企业所有者可以随时查看和撤销成员链接的身份、活动的会话或授权的凭据。 +To access each organization's resources on {% data variables.product.product_name %}, the member must have an active SAML session in their browser. To access each organization's protected resources using the API and Git, the member must use a {% data variables.product.pat_generic %} or SSH key that the member has authorized for use with the organization. Enterprise owners can view and revoke a member's linked identity, active sessions, or authorized credentials at any time. diff --git a/translations/zh-CN/data/reusables/saml/authorized-creds-info.md b/translations/zh-CN/data/reusables/saml/authorized-creds-info.md index aad0ed9a17..5f5411ce06 100644 --- a/translations/zh-CN/data/reusables/saml/authorized-creds-info.md +++ b/translations/zh-CN/data/reusables/saml/authorized-creds-info.md @@ -1,15 +1,7 @@ ---- -ms.openlocfilehash: 4055717eec0cdd95951ec6fb5bdea20efaed1948 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147573375" ---- -在可以授权个人访问令牌或 SSH 密钥之前,必须拥有一个链接的 SAML 标识。 如果你是已启用 SAML SSO 的组织的成员,则可以至少通过使用 IdP 向组织进行一次身份验证来创建链接标识。 有关详细信息,请参阅“[关于通过 SAML 单一登录进行身份验证](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)”。 +Before you can authorize a {% data variables.product.pat_generic %} or SSH key, you must have a linked SAML identity. If you're a member of an organization where SAML SSO is enabled, you can create a linked identity by authenticating to your organization with your IdP at least once. For more information, see "[About authentication with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)." -授予个人访问令牌或 SSH 密钥后,令牌或密钥将保持授权状态,直到以下列方式之一吊销。 -- 组织或企业所有者撤销授权。 -- 你已从组织中移除。 -- 已编辑个人访问令牌中的范围,或重新生成令牌。 -- 创建期间定义的个人访问令牌已过期。 +After you authorize a {% data variables.product.pat_generic %} or SSH key, the token or key will stay authorized until revoked in one of the following ways. +- An organization or enterprise owner revokes the authorization. +- You are removed from the organization. +- The scopes in a {% data variables.product.pat_generic %} are edited, or the token is regenerated. +- The {% data variables.product.pat_generic %} expired as defined during creation. diff --git a/translations/zh-CN/data/reusables/saml/must-authorize-linked-identity.md b/translations/zh-CN/data/reusables/saml/must-authorize-linked-identity.md index 72fbebcde0..5854c09d77 100644 --- a/translations/zh-CN/data/reusables/saml/must-authorize-linked-identity.md +++ b/translations/zh-CN/data/reusables/saml/must-authorize-linked-identity.md @@ -1,13 +1,5 @@ ---- -ms.openlocfilehash: 46bffdc7594863d282ba171fc258f4104a0a09b4 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147067848" ---- {% note %} -注意:如果你拥有某一组织的链接标识,则只能通过该组织使用授权的个人访问令牌和 SSH 密钥,即使未强制执行 SAML 也是如此。 如果已通过 SAML SSO 对某一组织进行了身份验证,你则拥有该组织的链接标识,除非组织或企业所有者后来撤销了该链接标识。 有关撤销链接标识的详细信息,请参阅“[查看和管理成员对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)”和“[查看和管理用户对企业的 SAML 访问](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)”。 +**Note:** If you have a linked identity for an organization, you can only use authorized {% data variables.product.pat_generic %}s and SSH keys with that organization, even if SAML is not enforced. You have a linked identity for an organization if you've ever authenticated via SAML SSO for that organization, unless an organization or enterprise owner later revoked the linked identity. For more information about revoking linked identities, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" and "[Viewing and managing a user's SAML access to your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)." {% endnote %} diff --git a/translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md b/translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md index da3e05cc5c..7d345990f4 100644 --- a/translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md +++ b/translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md @@ -1 +1 @@ -You must periodically authenticate with your SAML IdP to authenticate and gain access to {% ifversion fpt or ghec %}the organization's resources on {% data variables.product.prodname_dotcom_the_website %}{% elsif ghae %}{% data variables.product.product_location %}{% endif %}. The duration of this login period is specified by your IdP and is generally 24 hours. This periodic login requirement limits the length of access and requires you to re-identify yourself to continue. {% ifversion fpt or ghec %}You can view and manage your active SAML sessions in your security settings. For more information, see "[Viewing and managing your active SAML sessions](/articles/viewing-and-managing-your-active-saml-sessions)."{% endif %} +You must periodically authenticate with your SAML IdP to authenticate and gain access to {% ifversion fpt or ghec %}the organization's resources on {% data variables.product.prodname_dotcom_the_website %}{% elsif ghae %}{% data variables.location.product_location %}{% endif %}. The duration of this login period is specified by your IdP and is generally 24 hours. This periodic login requirement limits the length of access and requires you to re-identify yourself to continue. {% ifversion fpt or ghec %}You can view and manage your active SAML sessions in your security settings. For more information, see "[Viewing and managing your active SAML sessions](/articles/viewing-and-managing-your-active-saml-sessions)."{% endif %} diff --git a/translations/zh-CN/data/reusables/scim/enterprise-account-scim.md b/translations/zh-CN/data/reusables/scim/enterprise-account-scim.md index 37d48598e2..ac08a28b7d 100644 --- a/translations/zh-CN/data/reusables/scim/enterprise-account-scim.md +++ b/translations/zh-CN/data/reusables/scim/enterprise-account-scim.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: e53e61c7e5f6b12e9510b78251b68dea902eac9d -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147876121" ---- -不能将此 SCIM 的实现与企业帐户或 {% data variables.product.prodname_emu_org %} 一起使用。 如果为企业启用 {% data variables.product.prodname_emus %},则必须使用不同的 SCIM 实现。 否则,SCIM 在企业级别不可用。 有关详细信息,请参阅“[为 {% data variables.product.prodname_emus %} 配置 SCIM 预配](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)”。 +You cannot use this implementation of SCIM with an enterprise account or with an {% data variables.enterprise.prodname_emu_org %}. If your enterprise is enabled for {% data variables.product.prodname_emus %}, you must use a different implementation of SCIM. Otherwise, SCIM is not available at the enterprise level. For more information, see "[Configuring SCIM provisioning for {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)." diff --git a/translations/zh-CN/data/reusables/scim/supported-idps.md b/translations/zh-CN/data/reusables/scim/supported-idps.md index 59738e9774..1243cee7b5 100644 --- a/translations/zh-CN/data/reusables/scim/supported-idps.md +++ b/translations/zh-CN/data/reusables/scim/supported-idps.md @@ -1,13 +1,6 @@ ---- -ms.openlocfilehash: 4dfd2a37e834cd7331131d655545160b8ff2ef7f -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145127310" ---- -下面的 IdP 可以使用 SCM 在 {% data variables.product.product_location %} 上预配或解除预配用户帐户。 +The following IdPs can provision or deprovision user accounts on {% data variables.location.product_location %} using SCIM. {% ifversion ghae %} - Azure AD -- Okta(当前为 beta 版本){% endif %} +- Okta (currently in beta) +{% endif %} diff --git a/translations/zh-CN/data/reusables/search/syntax_tips.md b/translations/zh-CN/data/reusables/search/syntax_tips.md index f7f72677e0..8eedc169a7 100644 --- a/translations/zh-CN/data/reusables/search/syntax_tips.md +++ b/translations/zh-CN/data/reusables/search/syntax_tips.md @@ -1,16 +1,8 @@ ---- -ms.openlocfilehash: b3ef2ec170753526500b4aab081227267c2dcd3d -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "147876120" ---- {% tip %} -提示:{% ifversion ghes or ghae %} - - 本文章包含 {% data variables.product.prodname_dotcom_the_website %} 网站上示例搜索的链接,但您可以对 {% data variables.product.product_name %} 使用相同的搜索过滤器。 在链接的示例搜索中,将 `github.com` 替换为 {% data variables.product.product_location %} 的主机名。{% endif %} - - 有关可以添加到任何搜索限定符以进一步改善结果的搜索语法列表,请参阅“[了解搜索语法](/articles/understanding-the-search-syntax)”。 - - 对多个字词的搜索词使用引号。 例如,如果要搜索具有标签“In progress”的问题,可搜索 `label:"in progress"`。 搜索不区分大小写。 +**Tips:**{% ifversion ghes or ghae %} + - This article contains links to example searches on the {% data variables.product.prodname_dotcom_the_website %} website, but you can use the same search filters with {% data variables.product.product_name %}. In the linked example searches, replace `github.com` with the hostname for {% data variables.location.product_location %}.{% endif %} + - For a list of search syntaxes that you can add to any search qualifier to further improve your results, see "[Understanding the search syntax](/articles/understanding-the-search-syntax)". + - Use quotations around multi-word search terms. For example, if you want to search for issues with the label "In progress," you'd search for `label:"in progress"`. Search is not case sensitive. {% endtip %} diff --git a/translations/zh-CN/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md b/translations/zh-CN/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md index 7f1c750998..e4513c6c98 100644 --- a/translations/zh-CN/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md +++ b/translations/zh-CN/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md @@ -2,7 +2,7 @@ {% note %} -**Note:** Your site administrator must enable {% data variables.product.prodname_secret_scanning %} for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/enterprise/admin/configuration/configuring-secret-scanning-for-your-appliance)." +**Note:** Your site administrator must enable {% data variables.product.prodname_secret_scanning %} for {% data variables.location.product_location %} before you can use this feature. For more information, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/enterprise/admin/configuration/configuring-secret-scanning-for-your-appliance)." {% ifversion security-feature-enablement-policies %} You may not be able to enable or disable {% data variables.product.prodname_secret_scanning %}, if an enterprise owner has set a policy at the enterprise level. For more information, see "[Enforcing policies for code security and analysis for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise)."{% endif %} {% endnote %} diff --git a/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md index f70ad1c9c4..eb5a2953b2 100644 --- a/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -17,8 +17,12 @@ Atlassian | Atlassian JSON Web Token | atlassian_jwt Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} Azure | Azure Active Directory Application Secret | azure_active_directory_application_secret{% endif %} +{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %} +Azure | Azure Batch Key Identifiable | azure_batch_key_identifiable{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} Azure | Azure Cache for Redis Access Key | azure_cache_for_redis_access_key{% endif %} +{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %} +Azure | Azure CosmosDB Key Identifiable | azure_cosmosdb_key_identifiable{% endif %} Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token {%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %} Azure | Azure ML Studio (classic) Web Service Key | azure_ml_studio_classic_web_service_key{% endif %} diff --git a/translations/zh-CN/data/reusables/secret-scanning/secret-list-private-push-protection.md b/translations/zh-CN/data/reusables/secret-scanning/secret-list-private-push-protection.md index e73196547f..a2a86f557f 100644 --- a/translations/zh-CN/data/reusables/secret-scanning/secret-list-private-push-protection.md +++ b/translations/zh-CN/data/reusables/secret-scanning/secret-list-private-push-protection.md @@ -8,7 +8,11 @@ Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary A Asana | Asana Personal Access Token | asana_personal_access_token Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token Azure | Azure Active Directory Application Secret | azure_active_directory_application_secret +{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %} +Azure | Azure Batch Key Identifiable | azure_batch_key_identifiable{% endif %} Azure | Azure Cache for Redis Access Key | azure_cache_for_redis_access_key +{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %} +Azure | Azure CosmosDB Key Identifiable | azure_cosmosdb_key_identifiable{% endif %} Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token {%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %} Azure | Azure ML Studio (classic) Web Service Key | azure_ml_studio_classic_web_service_key{% endif %} diff --git a/translations/zh-CN/data/reusables/shortdesc/rate_limits_github_apps.md b/translations/zh-CN/data/reusables/shortdesc/rate_limits_github_apps.md index 8bfea16fcd..499de3d2f5 100644 --- a/translations/zh-CN/data/reusables/shortdesc/rate_limits_github_apps.md +++ b/translations/zh-CN/data/reusables/shortdesc/rate_limits_github_apps.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 5a00eb01f4e2c9ec707f5bbc7c5794c8108220e4 -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "145130189" ---- -{% data variables.product.prodname_github_apps %} 和 {% data variables.product.prodname_oauth_apps %} 的速率限制有助于控制到 {% data variables.product.product_location %} 的流量速率。 +Rate limits for {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} help control the rate of traffic to {% data variables.location.product_location %}. diff --git a/translations/zh-CN/data/reusables/sponsors/select-sponsorship-billing.md b/translations/zh-CN/data/reusables/sponsors/select-sponsorship-billing.md index 999f26ae0b..26b44ffe79 100644 --- a/translations/zh-CN/data/reusables/sponsors/select-sponsorship-billing.md +++ b/translations/zh-CN/data/reusables/sponsors/select-sponsorship-billing.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: aa5db374baed1496a9aa74205d7d19aabd75179d -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145130153" ---- -4. 在“Billing information(帐单信息)”下,查看您的付款详细信息。 或者,要更改 {% data variables.product.product_location %} 上整个帐户的付款详细信息,请单击“编辑”。 然后,按照提示填写付款表单。 +4. Under "Billing information", review your payment details. Optionally, to change the payment details for your entire account on {% data variables.location.product_location %}, click **Edit**. Then, follow the prompts to complete the payment form. diff --git a/translations/zh-CN/data/reusables/ssh/about-ssh.md b/translations/zh-CN/data/reusables/ssh/about-ssh.md index 48b431f7ac..95040d6fd3 100644 --- a/translations/zh-CN/data/reusables/ssh/about-ssh.md +++ b/translations/zh-CN/data/reusables/ssh/about-ssh.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: d7184796459936c64db3513a123f383c43caf4b6 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147409779" ---- -可以使用 SSH(安全外壳协议)访问和写入 {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} 上的存储库中的数据。 通过 SSH 进行连接时,使用本地计算机上的私钥文件进行身份验证。 +You can access and write data in repositories on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} using SSH (Secure Shell Protocol). When you connect via SSH, you authenticate using a private key file on your local machine. diff --git a/translations/zh-CN/data/reusables/ssh/key-type-support.md b/translations/zh-CN/data/reusables/ssh/key-type-support.md index 50d25540b6..324873282a 100644 --- a/translations/zh-CN/data/reusables/ssh/key-type-support.md +++ b/translations/zh-CN/data/reusables/ssh/key-type-support.md @@ -1,18 +1,11 @@ ---- -ms.openlocfilehash: 621dfdbcdc0585f51536c924e1e5d0d9a140ff26 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147410649" ---- -{% ifversion fpt or ghec %} {% note %} +{% ifversion fpt or ghec %} +{% note %} -注意:{% data variables.product.company_short %} 通过在 2022 年 3 月 15 日删除旧的、不安全的密钥类型来提高安全性。 +**Note:** {% data variables.product.company_short %} improved security by dropping older, insecure key types on March 15, 2022. -自该日期起,不再支持 DSA 密钥 (`ssh-dss`)。 无法在 {% data variables.product.product_location %} 上向个人帐户添加新的 DSA 密钥。 +As of that date, DSA keys (`ssh-dss`) are no longer supported. You cannot add new DSA keys to your personal account on {% data variables.location.product_location %}. -2021 年 11 月 2 日之前带有 `valid_after` 的 RSA 密钥 (`ssh-rsa`) 可以继续使用任何签名算法。 在该日期之后生成的 RSA 密钥必须使用 SHA-2 签名算法。 一些较旧的客户端可能需要升级才能使用 SHA-2 签名。 +RSA keys (`ssh-rsa`) with a `valid_after` before November 2, 2021 may continue to use any signature algorithm. RSA keys generated after that date must use a SHA-2 signature algorithm. Some older clients may need to be upgraded in order to use SHA-2 signatures. {% endnote %} @@ -20,15 +13,15 @@ ms.locfileid: "147410649" {% note %} -注意:默认情况下,若使用 {% data variables.product.product_name %} 3.6 及更高版本,则截至 2022 年 8 月 1 日午夜 (UTC),同时满足以下两个条件的 SSH 连接将失败 。 +**Note**: By default with {% data variables.product.product_name %} 3.6 and later, as of the cutoff date of midnight UTC on August 1, 2022, SSH connections that satisfy **both** of the following conditions will fail.
{% data reusables.ssh.rsa-sha-1-connection-failure-criteria %} -{% data variables.product.product_name %} 3.6 及更高版本也不支持使用 DSA、HMAC-SHA-1 或 CBC 密码的 SSH 连接。 只要密钥保持有效,在截止日期之前上传的 RSA SSH 密钥便可以继续使用 SHA-1 哈希函数进行身份验证。 有关查找所使用的 {% data variables.product.product_name %} 版本的详细信息,请参阅“[关于 {% data variables.product.prodname_docs %} 的版本](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)”。 +{% data variables.product.product_name %} 3.6 and later also does not support SSH connections that use DSA, HMAC-SHA-1, or CBC ciphers. RSA SSH keys uploaded before the cutoff date can continue to authenticate using the SHA-1 hash function as long as the key remains valid. For more information about finding the version of {% data variables.product.product_name %} that you use, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)." -站点管理员可以使用 RSA-SHA-1 调整连接的截止日期,也可以使用 RSA-SHA-1 阻止所有连接。 有关详细信息,请联系站点管理员,或参阅“[配置与实例的 SSH 连接](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)”。 +Your site administrator can adjust the cutoff date for connections using RSA-SHA-1, and may block all connections using RSA-SHA-1. For more information, contact your site administrator or see "[Configuring SSH connections to your instance](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)." {% endnote %} diff --git a/translations/zh-CN/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md b/translations/zh-CN/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md index 5ec5f530f4..b08eeab7b8 100644 --- a/translations/zh-CN/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md +++ b/translations/zh-CN/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md @@ -1,10 +1,2 @@ ---- -ms.openlocfilehash: 51813ab823a86fe6428d31b3fd4f80f81458dc23 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147409778" ---- -- RSA 密钥在 2022 年 8 月 1 日午夜 UTC 截止日期之后添加到 {% data variables.product.product_location %} 上的用户帐户。 -- SSH 客户端使用 SHA-1 哈希函数对连接尝试进行签名。 +- The RSA key was added to a user account on {% data variables.location.product_location %} after the cutoff date of midnight UTC on August 1, 2022. +- The SSH client signs the connection attempt with the SHA-1 hash function. diff --git a/translations/zh-CN/data/reusables/support/submit-a-ticket.md b/translations/zh-CN/data/reusables/support/submit-a-ticket.md index d128b09c53..e9b27b7fc5 100644 --- a/translations/zh-CN/data/reusables/support/submit-a-ticket.md +++ b/translations/zh-CN/data/reusables/support/submit-a-ticket.md @@ -1,44 +1,45 @@ ---- -ms.openlocfilehash: b7f16729209b711d9ea95d059f5868ae867fa040 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147419879" ---- -1. 选择“帐户或组织”下拉菜单,然后单击你的支持票证所涉及的帐户名称。 -![“帐户或组织”下拉菜单的屏幕截图。](/assets/images/help/support/account-field.png) -1. 选择“发件人”下拉菜单并单击你希望 {% data variables.contact.github_support %} 联系的电子邮件地址。 -![“发件人”下拉菜单的屏幕截图。](/assets/images/help/support/from-field.png) +1. Select the **Account or organization** dropdown menu and click the name of the account your support ticket is regarding. +![Screenshot of the "Account or organization" dropdown menu.](/assets/images/help/support/account-field.png) +1. Select the **From** drop-down menu and click the email address you'd like {% data variables.contact.github_support %} to contact. +![Screenshot of the "From" dropdown menu.](/assets/images/help/support/from-field.png) {%- ifversion ghec or ghes %} -1. 选择“产品”下拉菜单并单击 {% ifversion ghes %}GitHub Enterprise Server(自托管){% else %}GitHub Enterprise Cloud{% endif %} 。 -{% ifversion ghec %}![“产品”下拉菜单的屏幕截图。](/assets/images/help/support/product-field-ghec.png){% else %}![“产品”下拉菜单的屏幕截图。](/assets/images/help/support/product-field.png){% endif %} {%- endif %} {%- ifversion ghes %} -1. 如果出现提示,请选择“服务器安装”下拉菜单,然后单击支持票证所涉及的安装。 如果安装未列出,请单击“其他”。 -![“服务器安装”下拉菜单的屏幕截图](/assets/images/help/support/installation-field.png) {%- endif %} {%- ifversion ghes %} -1. 选择“发布系列”下拉菜单并单击发布 {% data variables.product.product_location_enterprise %} 正在运行。 -![发布系列”下拉菜单的屏幕截图](/assets/images/help/support/release-field.png) {%- endif %} {%- ifversion ghes or ghec %} -1. 选择“优先级”下拉菜单并单击适当的紧迫性。 有关详细信息,请参阅“[关于票证优先级](/support/learning-about-github-support/about-ticket-priority)。” - ![“优先级”下拉菜单的屏幕截图。](/assets/images/help/support/priority-field.png) -{%- endif %} {%- ifversion ghes %} - - 选择 {% data variables.product.support_ticket_priority_urgent %} 以报告 {% ifversion fpt or ghec %}严重系统故障{% else %} 致命系统故障、影响关键系统操作、安全事件和过期许可证的中断{% endif %}。 - - 选择 {% data variables.product.support_ticket_priority_high %} 报告影响业务运营的问题,包括 {% ifversion fpt or ghec %}从你自己的帐户和组织还原中删除敏感数据(提交、议题、拉取请求、上传的附件){% else %}系统性能问题{% endif %},或报告严重错误。 - - 选择 {% data variables.product.support_ticket_priority_normal %} 以 {% ifversion fpt or ghec %}请求帐户恢复或垃圾邮件取消标识、报告用户登录问题{% else %}发出技术请求,如配置更改和第三方集成{% endif %},以及报告非关键 bug。 - - 选择 {% data variables.product.support_ticket_priority_low %} 以提出一般问题和提交有关新功能、购买、培训或状态检查的请求。 -{%- endif %} {%- ifversion ghes or ghec %} -1. 或者,如果帐户包含 {% data variables.contact.premium_support %} 并且票证优先级为{% ifversion ghes %}紧急或高{% elsif ghec %}高{% endif %},则可以用英语请求回叫。 选择“从 GitHub 支持请求回叫”,选择“国家代码”下拉菜单以选择国家,然后输入电话号码。 -![“请求回叫”复选框、“国家/地区代码”下拉菜单和“电话号码”文本框的屏幕截图。](/assets/images/help/support/request-callback.png) +1. Select the **Product** dropdown menu and click {% ifversion ghes %}**GitHub Enterprise Server (self-hosted)**{% else %}**GitHub Enterprise Cloud**{% endif %}. +{% ifversion ghec %}![Screenshot of the "Product" dropdown menu.](/assets/images/help/support/product-field-ghec.png){% else %}![Screenshot of the "Product" dropdown menu.](/assets/images/help/support/product-field.png){% endif %} {%- endif %} -1. 在“Subject(主题)”下,为您遇到的问题输入描述性标题。 -![主题”文本框的屏幕截图。](/assets/images/help/support/subject-field.png) -1. 在“How can we help(我们如何提供帮助)”下,提供将帮助支持团队对问题进行故障排除的任何其他信息。 你可以使用 Markdown 格式化消息。 - ![“如何帮助”文本区域的屏幕截图。](/assets/images/help/support/how-can-we-help-field.png) - 有用的信息可能包括: - - 重现问题的步骤 - - 与问题发现有关的任何特殊情况(例如,第一次出现或特定事件之后出现、出现频率、问题的业务影响和建议的紧急级别) - - 错误消息的准确表述 {% indented_data_reference reusables.repositories.anyone-can-view-anonymized-url spaces=3 %} +{%- ifversion ghes %} +1. If prompted, select the **Server installation** dropdown menu and click the installation your support ticket is regarding. If the installation is not listed, click **Other**. +![Screenshot of the "Server Installation" dropdown menu](/assets/images/help/support/installation-field.png) +{%- endif %} +{%- ifversion ghes %} +1. Select the **Release series** dropdown menu and click the release {% data variables.location.product_location_enterprise %} is running. +![Screenshot of the "Release series" dropdown menu](/assets/images/help/support/release-field.png) +{%- endif %} +{%- ifversion ghes or ghec %} +1. Select the **Priority** dropdown menu and click the appropriate urgency. For more information, see "[About ticket priority](/support/learning-about-github-support/about-ticket-priority)." + ![Screenshot of the "Priority" dropdown menu.](/assets/images/help/support/priority-field.png) +{%- endif %} +{%- ifversion ghes %} + - Choose **{% data variables.product.support_ticket_priority_urgent %}** to report {% ifversion fpt or ghec %}critical system failure{% else %}fatal system failures, outages impacting critical system operations, security incidents, and expired licenses{% endif %}. + - Choose **{% data variables.product.support_ticket_priority_high %}** to report issues impacting business operations, including {% ifversion fpt or ghec %}removing sensitive data (commits, issues, pull requests, uploaded attachments) from your own accounts and organization restorations{% else %}system performance issues{% endif %}, or to report critical bugs. + - Choose **{% data variables.product.support_ticket_priority_normal %}** to {% ifversion fpt or ghec %}request account recovery or spam unflagging, report user login issues{% else %}make technical requests like configuration changes and third-party integrations{% endif %}, and to report non-critical bugs. + - Choose **{% data variables.product.support_ticket_priority_low %}** to ask general questions and submit requests for new features, purchases, training, or health checks. +{%- endif %} +{%- ifversion ghes or ghec %} +1. Optionally, if your account includes {% data variables.contact.premium_support %} and your ticket is {% ifversion ghes %}urgent or high{% elsif ghec %}high{% endif %} priority, you can request a callback in English. Select **Request a callback from GitHub Support**, select the country code dropdown menu to choose your country, and enter your phone number. +![Screenshot of the "Request callback" checkbox, "Country code" dropdown menu, and "Phone number" text box.](/assets/images/help/support/request-callback.png) +{%- endif %} +1. Under "Subject", type a descriptive title for the issue you're having. +![Screenshot of the "Subject" text box.](/assets/images/help/support/subject-field.png) +1. Under "How can we help", provide any additional information that will help the Support team troubleshoot the problem. You can use markdown to format your message. + ![Screenshot of the "How can we help" text area.](/assets/images/help/support/how-can-we-help-field.png) + Helpful information may include: + - Steps to reproduce the issue + - Any special circumstances surrounding the discovery of the issue (for example, the first occurrence or occurrence after a specific event, frequency of occurrence, business impact of the problem, and suggested urgency) + - Exact wording of error messages +{% indented_data_reference reusables.repositories.anyone-can-view-anonymized-url spaces=3 %} {%- ifversion ghes %} -1. 或者,通过拖放、上传或从剪贴板粘贴来附加诊断文件和其他文件。 +1. Optionally, attach diagnostics files and other files by dragging and dropping, uploading, or pasting from the clipboard. {%- endif %} -1. 单击“发送请求”。 -![“发送请求”按钮的屏幕截图。](/assets/images/help/support/send-request-button.png) +1. Click **Send request**. +![Screenshot of the "Send request" button.](/assets/images/help/support/send-request-button.png) diff --git a/translations/zh-CN/data/reusables/user-settings/password-authentication-deprecation.md b/translations/zh-CN/data/reusables/user-settings/password-authentication-deprecation.md index e67cf67ef6..04a4cbd48e 100644 --- a/translations/zh-CN/data/reusables/user-settings/password-authentication-deprecation.md +++ b/translations/zh-CN/data/reusables/user-settings/password-authentication-deprecation.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: 57b54e908b908c3bd26cf35158442ec9a59b96d8 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "145065717" ---- -当 Git 提示输入密码时,请输入个人访问令牌 (PAT)。 或者,可以使用 [Git 凭据管理器](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md)等凭据帮助程序。{% ifversion not ghae %} Git 的基于密码的身份验证已被删除,以支持更安全的身份验证方法。{% endif %} 有关详细信息,请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 +When Git prompts you for your password, enter your {% data variables.product.pat_generic %}. Alternatively, you can use a credential helper like [Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md).{% ifversion not ghae %} Password-based authentication for Git has been removed in favor of more secure authentication methods.{% endif %} For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." diff --git a/translations/zh-CN/data/reusables/user-settings/personal_access_tokens.md b/translations/zh-CN/data/reusables/user-settings/personal_access_tokens.md index dc5586262e..0a2887b96d 100644 --- a/translations/zh-CN/data/reusables/user-settings/personal_access_tokens.md +++ b/translations/zh-CN/data/reusables/user-settings/personal_access_tokens.md @@ -1,10 +1,2 @@ ---- -ms.openlocfilehash: ab6ddc3736dea3b8c865ae9047373c1de4d1311f -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: "145065714" ---- -1. 在左侧边栏中,单击“个人访问令牌”。 -![个人访问令牌](/assets/images/help/settings/personal_access_tokens_tab.png) +1. In the left sidebar, click **{% data variables.product.pat_generic_caps %}s**. +![{% data variables.product.pat_generic_caps %}s](/assets/images/help/settings/personal_access_tokens_tab.png) diff --git a/translations/zh-CN/data/reusables/user-settings/removes-personal-access-tokens.md b/translations/zh-CN/data/reusables/user-settings/removes-personal-access-tokens.md index e75c9bf7bd..3840329b4c 100644 --- a/translations/zh-CN/data/reusables/user-settings/removes-personal-access-tokens.md +++ b/translations/zh-CN/data/reusables/user-settings/removes-personal-access-tokens.md @@ -1,9 +1 @@ ---- -ms.openlocfilehash: a435a91a41d6097a0613eb77253bf4381a75e8c0 -ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147065992" ---- -作为安全预防措施,{% data variables.product.company_short %} 会自动删除一年内未使用过的个人访问令牌。 为了提供进一步的安全性,强烈建议将过期时间添加到个人访问令牌。 +As a security precaution, {% data variables.product.company_short %} automatically removes {% data variables.product.pat_generic %}s that haven't been used in a year. To provide additional security, we highly recommend adding an expiration to your {% data variables.product.pat_generic %}s. diff --git a/translations/zh-CN/data/variables/product.yml b/translations/zh-CN/data/variables/product.yml index 769d6949b3..903b4ee61b 100644 --- a/translations/zh-CN/data/variables/product.yml +++ b/translations/zh-CN/data/variables/product.yml @@ -24,14 +24,6 @@ prodname_ghe_managed: 'GitHub AE' prodname_ghe_one: 'GitHub One' prodname_docs: 'GitHub Docs' -## Use these variables when referring specifically to a location within a product -product_location: >- - {% ifversion ghes %}your GitHub Enterprise Server instance{% elsif ghae %}your enterprise{% else %}GitHub.com{% endif %} - -# Used ONLY when you need to refer to a GHES instance in an article that is versioned for non-GHES versions. -# Do not use in other situations! -product_location_enterprise: 'your GitHub Enterprise Server instance' - prodname_free_user: 'GitHub Free' prodname_pro: 'GitHub Pro' prodname_team: 'GitHub Team' @@ -40,10 +32,7 @@ prodname_free_team: 'GitHub Free' prodname_enterprise_backup_utilities: 'GitHub Enterprise Server Backup Utilities' # GitHub Connect (enterprise accounts, other unified features) -## Phrase content so that the uncapitalized unified contributions or unified search variables are not used at the start of a sentence. prodname_github_connect: 'GitHub Connect' -prodname_unified_contributions: 'unified contributions' -prodname_unified_search: 'unified search' # GitHub Enterprise migration tool prodname_importer_proper_name: 'GitHub Enterprise Importer' @@ -96,6 +85,20 @@ prodname_project_v1: >- prodname_project_v1_caps: >- {% ifversion ghes or ghae %}Project board{% else %}Project (classic){% endif %} +# Personal access tokens +pat_generic: 'personal access token' +pat_generic_caps: 'Personal access token' +pat_v2: 'fine-grained personal access token' +pat_v2_caps: 'Fine-grained personal access token' +pat_v1: >- + {% ifversion pat-v2 %}personal access token (classic){% else %}personal access token{% endif %} +pat_v1_plural: >- + {% ifversion pat-v2 %}personal access tokens (classic){% else %}personal access tokens{% endif %} +pat_v1_caps: >- + {% ifversion pat-v2 %}Personal access token (classic){% else %}Personal access token{% endif %} +pat_v1_caps_plural: >- + {% ifversion pat-v2 %}Personal access tokens (classic){% else %}Personal access tokens{% endif %} + # Apps, GitHub Marketplace, and integrations prodname_marketplace: 'GitHub Marketplace' prodname_github_app: 'GitHub App' @@ -124,11 +127,6 @@ prodname_discussions: 'GitHub Discussions' prodname_emu_idp_application: 'GitHub Enterprise Managed User' prodname_emu_idp_oidc_application: 'GitHub Enterprise Managed User (OIDC)' prodname_emus: 'Enterprise Managed Users' -prodname_managed_user: 'managed user account' -prodname_managed_users: 'managed user accounts' -prodname_managed_users_caps: 'Managed user accounts' -prodname_emu_enterprise: 'enterprise with managed users' -prodname_emu_org: 'organization with managed users' # GitHub Issues prodname_github_issues: 'GitHub Issues' @@ -238,14 +236,14 @@ prodname_server_statistics: 'Server Statistics' # Links product_url: >- - {% ifversion fpt or ghec %}github.com{% else %}[hostname]{% endif %} + {% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %} pricing_url: 'https://github.com/pricing' signin_link: >- - {% ifversion fpt or ghec %}[Sign in](https://github.com/login){% else %}Sign in (`https://[hostname]/login`){% endif %} + {% ifversion fpt or ghec %}[Sign in](https://github.com/login){% else %}Sign in (`https://HOSTNAME/login`){% endif %} signout_link: >- - {% ifversion fpt or ghec %}[Sign out](https://github.com/logout){% else %}Sign out (`https://[hostname]/logout`){% endif %} + {% ifversion fpt or ghec %}[Sign out](https://github.com/logout){% else %}Sign out (`https://HOSTNAME/logout`){% endif %} raw_github_com: >- - {% ifversion fpt or ghec %}raw.githubusercontent.com{% else %}[hostname]/user/repo/raw{% endif %} + {% ifversion fpt or ghec %}raw.githubusercontent.com{% else %}HOSTNAME/user/repo/raw{% endif %} # GitHub Enterprise Server past versions current-340-version: '11.10.354' @@ -255,25 +253,25 @@ doc_url_pre: >- {% ifversion fpt or ghec %}https://docs.github.com/rest{% elsif ghes %}https://docs.github.com/enterprise/{{ currentVersion | version_num }}/rest{% elsif ghae %}https://docs.github.com/github-ae@latest/rest{% endif %} # Use this inside command-line code blocks api_url_pre: >- - {% ifversion fpt or ghec %}https://api.github.com{% elsif ghes %}http(s)://[hostname]/api/v3{% elsif ghae %}https://[hostname]/api/v3{% endif %} + {% ifversion fpt or ghec %}https://api.github.com{% elsif ghes %}http(s)://HOSTNAME/api/v3{% elsif ghae %}https://HOSTNAME/api/v3{% endif %} # Use this inside command-line code blocks # Enterprise OAuth paths that don't include "/graphql" or "/api/v3" oauth_host_code: >- - {% ifversion fpt or ghec %}https://github.com{% else %}http(s)://[hostname]{% endif %} + {% ifversion fpt or ghec %}https://github.com{% else %}http(s)://HOSTNAME{% endif %} device_authorization_url: >- {%- ifversion fpt or ghec %} [`https://github.com/login/device`](https://github.com/login/device) {%- elsif ghes %} - `http(s)://[hostname]/login/device` + `http(s)://HOSTNAME/login/device` {%- elsif ghae %} - `https://[hostname]/login/device` + `https://HOSTNAME/login/device` {%- endif %} # Use this all other code blocks api_url_code: >- - {% ifversion fpt or ghec %}https://api.github.com{% elsif ghes %}http(s)://[hostname]/api/v3{% elsif ghae %}https://[hostname]/api/v3{% endif %} + {% ifversion fpt or ghec %}https://api.github.com{% elsif ghes %}http(s)://HOSTNAME/api/v3{% elsif ghae %}https://HOSTNAME/api/v3{% endif %} # Use this inside command-line code blocks graphql_url_pre: >- - {% ifversion fpt or ghec %}https://api.github.com/graphql{% elsif ghes %}http(s)://[hostname]/api/graphql{% elsif ghae %}https://[hostname]/api/graphql{% endif %} + {% ifversion fpt or ghec %}https://api.github.com/graphql{% elsif ghes %}http(s)://HOSTNAME/api/graphql{% elsif ghae %}https://HOSTNAME/api/graphql{% endif %} # Use this all other code blocks graphql_url_code: >- - {% ifversion fpt or ghec %}https://api.github.com/graphql{% elsif ghes %}http(s)://[hostname]/api/graphql{% elsif ghae %}https://[hostname]/api/graphql{% endif %} + {% ifversion fpt or ghec %}https://api.github.com/graphql{% elsif ghes %}http(s)://HOSTNAME/api/graphql{% elsif ghae %}https://HOSTNAME/api/graphql{% endif %}
-当仓库中的拉取请求标记为“准备审核”时,此工作流程将运行。 +This workflow runs whenever a pull request in the repository is marked as "ready for review".
-仅限 {% data variables.product.prodname_github_app %}: +{% data variables.product.prodname_github_app %} only: ```yaml - name: Generate token @@ -321,20 +317,20 @@ on: -使用 tibdex/github-app-token 操作从应用 ID 和私钥为应用生成安装访问令牌。 稍后在工作流中以 {% raw %}${{ steps.generate_token.outputs.token }}{% endraw %} 的形式访问安装访问令牌。 +Uses the tibdex/github-app-token action to generate an installation access token for your app from the app ID and private key. The installation access token is accessed later in the workflow as {% raw %}${{ steps.generate_token.outputs.token }}{% endraw %}.

-将 APP_ID 替换为包含应用 ID 的机密的名称。 +Replace APP_ID with the name of the secret that contains your app ID.

-将 APP_PEM 替换为包含应用私钥的机密的名称。 +Replace APP_PEM with the name of the secret that contains your app private key.
-{% data variables.product.prodname_github_app %}: +{% data variables.product.prodname_github_app %}: ```yaml env: @@ -343,7 +339,7 @@ env: PROJECT_NUMBER: YOUR_PROJECT_NUMBER ``` -个人访问令牌: +{% data variables.product.pat_generic_caps %}: ```yaml env: @@ -354,16 +350,16 @@ env: -为此步骤设置环境变量。 +Sets environment variables for this step.

-如果使用个人访问令牌,请将 YOUR_TOKEN 替换为包含个人访问令牌的机密的名称。 +If you are using a {% data variables.product.pat_generic %}, replace YOUR_TOKEN with the name of the secret that contains your {% data variables.product.pat_generic %}.

-将 YOUR_ORGANIZATION 替换为组织的名称。 例如,octo-org。 +Replace YOUR_ORGANIZATION with the name of your organization. For example, octo-org.

-将 YOUR_PROJECT_NUMBER 替换为项目编号。 要查找项目编号,请查看项目 URL。 例如,https://github.com/orgs/octo-org/projects/5 的项目编号为 5。 +Replace YOUR_PROJECT_NUMBER with your project number. To find the project number, look at the project URL. For example, https://github.com/orgs/octo-org/projects/5 has a project number of 5.
-

使用 {% data variables.product.prodname_cli %} 查询项目的 ID 的 API,并返回项目中前 20 个字段的名称和 ID。 fields 会返回一个联合,查询使用内联片段 (... on) 返回任何 ProjectV2FieldProjectV2SingleSelectField 字段的相关信息。

+

Uses {% data variables.product.prodname_cli %} to query the API for the ID of the project and return the name and ID of the first 20 fields in the project. fields returns a union and the query uses inline fragments (... on) to return information about any ProjectV2Field and ProjectV2SingleSelectField fields.

-

响应存储在名为 project_data.json 的文件中。

+

The response is stored in a file called project_data.json.

-解析 API 查询的响应,并将相关 ID 存储为环境变量。 修改此选项以获取不同字段或选项的 ID。 例如: +Parses the response from the API query and stores the relevant IDs as environment variables. Modify this to get the ID for different fields or options. For example:
    -
  • 若要获取名为 Team 的字段的 ID,请添加 echo 'TEAM_FIELD_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Team") | .id' project_data.json) >> $GITHUB_ENV
  • -
  • 若要获取 Team 单选字段的名为 Octoteam 的选项的 ID,请添加 echo 'OCTOTEAM_OPTION_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Team") |.options[] | select(.name=="Octoteam") |.id' project_data.json) >> $GITHUB_ENV
  • -
注意:此工作流程假定你有一个项目,其中包含一个名为“状态”的单选字段、一个名为“待办”的选项和一个名为“发布日期”的日期字段 -。 您必须修改此部分以匹配表中存在的字段。 +
  • To get the ID of a field called Team, add echo 'TEAM_FIELD_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Team") | .id' project_data.json) >> $GITHUB_ENV.
  • +
  • To get the ID of an option called Octoteam for the Team single select field, add echo 'OCTOTEAM_OPTION_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Team") |.options[] | select(.name=="Octoteam") |.id' project_data.json) >> $GITHUB_ENV
  • + +Note: This workflow assumes that you have a project with a single select field called "Status" that includes an option called "Todo" and a date field called "Date posted". You must modify this section to match the fields that are present in your table.
    -{% data variables.product.prodname_github_app %}: +{% data variables.product.prodname_github_app %}: ```yaml env: @@ -437,7 +433,7 @@ env: PR_ID: {% raw %}${{ github.event.pull_request.node_id }}{% endraw %} ``` -个人访问令牌: +{% data variables.product.pat_generic_caps %}: ```yaml env: @@ -447,7 +443,7 @@ env: -为此步骤设置环境变量。 GITHUB_TOKEN 如上所述。 PR_ID 是触发此工作流的拉取请求的 ID。 +Sets environment variables for this step. GITHUB_TOKEN is described above. PR_ID is the ID of the pull request that triggered this workflow.
    -使用 {% data variables.product.prodname_cli %} 和 API 将触发此工作流的拉取请求添加到项目。 jq 标志解析响应以获取所创建项目的 ID。 +Uses {% data variables.product.prodname_cli %} and the API to add the pull request that triggered this workflow to the project. The jq flag parses the response to get the ID of the created item.
    -将已创建项的 ID 存储为环境变量。 +Stores the ID of the created item as an environment variable.
    -以 yyyy-mm-dd 格式将当前日期保存为环境变量。 +Saves the current date as an environment variable in yyyy-mm-dd format.
    -{% data variables.product.prodname_github_app %}: +{% data variables.product.prodname_github_app %}: ```yaml env: GITHUB_TOKEN: {% raw %}${{ steps.generate_token.outputs.token }}{% endraw %} ``` -个人访问令牌: +{% data variables.product.pat_generic_caps %}: ```yaml env: @@ -517,7 +513,7 @@ env: -为此步骤设置环境变量。 GITHUB_TOKEN 如上所述。 +Sets environment variables for this step. GITHUB_TOKEN is described above.
    -将 Status 字段的值设置为 Todo。 设置 Date posted 字段的值。 +Sets the value of the Status field to Todo. Sets the value of the Date posted field.